Finalizing the eMobilty set of BAPs from remaining use cases

With the remaining use cases, and also the alternatives mentioned in these use cases, we finalized (partly 2112

automated) the eMobilty set of BAPs that now extends from 7 to 16 main BAPs. Some information links are 2113

not often used so results in a ‘smaller’ BAP with less information content. Some other links are more 2114

frequently used and results in a BAP which lists a lot of information elements, since these are now 2115

automatically derived from the use cases. 2116

We have included the information from the following use cases: 2117

 WGSP-1100 Uncontrolled charging. 2118

 WGSP-1200 Charging with demand response. 2119

 WGSP-1300 Smart (re- / de) charging. 2120

 WGSP-1400 Ensuring interoperability and settlement. 2121

 WGSP-1500 Manage charge infrastructure. 2122

These use cases lead to the following BAPs in the list bullet below. We listed them with the interface, 2123

protocol choices (then it will be a different (version of the) BAP) and main information elements exchanged. 2124

We made 5 BAPs bold, these are the most used in the different use cases. We copied information elements 2125

from the use cases. 2126

 BAP A: Interface between EV-EMSP 2127

Choose between (BAP A1 A2 A3 A4) 3G to EMSP, 3G via OEM Backend, or via ISO/IEC 15118 etc. 2128

Information element examples: EV charging capabilities, Battery status, State of Charge, EV type 2129

identification. 2130

 BAP B: Interface between EMSP-EP 2131

Choose between: Current electricity Market protocols, … 2132

Information element examples: Supply availability (Energy quantity (kWh), Energy type (RES), Power 2133

quantity (kW), …), Tariff. 2134

 BAP C: Interface between EMSP-DSO 2135

Choose a Smart Grid protocol (e.g. PowerMatcher) or specify one 2136

Information element examples: Customer/EMSP/DSO-optimized charging request, 2137

Calculated customer/EMSP-optimized charge plan, EVSE identification, Acknowledgement/OK, Charge 2138

request information for offerings, EVSE information, 2139

Available capacity in network segment, Other EV identifiers of same EMSP in network segment, … 2140

 BAP D: Interface between EMSP-EVSEO 2141

Choose likely a kind of OCPP or derivative 2142

Information element examples: Charging Details Records (power, time, etc.), Charge request information 2143

for offerings, EVSE identification. 2144

 BAP E: Interface between EVSE-EVSEO 2145

Choose between OCPP (E1), or some alternatives 2146

Information element examples: Release EVSE, Access to EVSE, No Access to EVSE, No heartbeat, 2147

wrong data, Reset (Hard/Soft), Update, who is charging, amount of energy, which EVSE, … 2148

 BAP F: Interface between EVUser-EVSE 2149

Choose e.g. Smart Card with RFID 2150

Information element examples: Charge Card number, Charge Station ID, date, time, Plugout signal, … 2151

 BAP G: Interface between EVSEO-CH 2152

Choose between Clearing House protocols like OCHP. 2153

Information element examples: Charge Card number, Charge Station ID, Transaction ID, time, date, … 2154

 BAP H: Interface between EMSP-EMSP-Other 2155

Choose a special EMSP agreed interface. 2156

Information element examples: Proposal for exchanging / buying charging capacity in specific network 2157

segment. 2158

 BAP I: Interface between EV-EVSE 2159

Choose from and between (can be a combination!):IEC 61851, ISO-IEC 15118, IEC 62196. 2160

Information element examples: electrical mode 3 handshake, … 2161

 BAP J: Interface between EVUser-EMSP 2162

Choose a device e.g. Smart Phone, can be EMSP specific as the user has a ‘flexible’ interface 2163

Information element examples: Offerings, OK, Proposal for an alternative for original charge request, 2164

Settlement data (power, time, tariff etc.), Time of departure, Range / energy demand, Energy type (RES), 2165

Budget, Customer identification information, Transaction data, payment, etc. 2166

 BAP K: Interface between DSO-EVSEO 2167

Choose between a kind of smart grid protocol, likely only that also includes a mode for grid emergency 2168

handling. 2169

Information element examples: Approved charge plan, EVSE identification. 2170

 BAP L: Interface between CH-EMSP 2171

Choose between Clearing House protocols like OCHP. 2172

Information element examples: Transaction ID, time, date, … 2173

 BAP M: Interface between EVSE-EVUser 2174

Choose between different User Interfaces to EVSE, can be partly EVSE specific as the user has a 2175

’flexible’ interface. 2176

Information element examples: Transaction ID, time, date, … 2177

 BAP N: Interface between EVSEO-CIO (ChargeSpot Infrastructure Operator) 2178

Choose between, still open. 2179

Information element examples: Location, Type of Malfunction, asset assignment 2180

 BAP O: Interface between EV-EVSE-EVSEO 2181

This includes plug-out events communication to EVSEO. 2182

Information element examples: Information about charging. 2183

 BAP P: Interface between EVUser-EV 2184

Choose between different User Interfaces to EVSE, can be partly EVSE specific as the user has a flexible 2185

interface. 2186

Information element examples: Charge-Plan (schedule), End charge signal. 2187

Overseeing the list above it becomes very clear that a lot of specification work is still to be done for a 2188

complete set of well described BAPs. Since a BAP is defined as a “selection and interpretation of relevant 2189

parts of the applicable standards and specifications” it means that after this step a study of the different 2190

standards needs to be done, and to be described and specifies what the different BAPs will use of these 2191

standards (or specifications). 2192

2193

12.5.2 Experience and example of creating BAIOPs for testing using the Interoperability Process