Road vehicles — Vehicle to grid communication interface ... · 147 7.10 Application layer 148 This clause of ISO/IEC DIS 15118-2 is applicable. V2G communication interface for OppCharge,

Version: 1.3.0Date: 2018-09-26

© SIEMENS 2018All rights reserved

Road vehicles — Vehicle to grid communication interface —

Network and application protocol specificationfor Siemens — Volvo OppCharge implementation

Version: 1.3.0

ACD extension for OppCharge on ISO/IEC DIS 15118-2 (2012)

V2G communication interface for OppCharge, V 1.3.0, ACD extension of ISO/IEC DIS 15118-2 (2012)

ii © SIEMENS AG 2018 – All rights reserved

Copyright note1

This document was developed by Siemens Mobility GmbH for the OppCharge community to support2interoperability and can be used by anybody without restrictions.3

4@Siemens Mobility GmbH 20185All rights reserved.6

7


© SIEMENS AG 2018 – All rights reserved iii

Contents Page8

1 Scope ................................................................................................................................................79

2 Normative references .......................................................................................................................710

3 Terms and definitions ......................................................................................................................711

4 Symbols and abbreviated terms ......................................................................................................712

5 Conventions .....................................................................................................................................813

6 Document overview ..........................................................................................................................814

7 Basic requirements for V2G communication ..................................................................................9157.1 General information .........................................................................................................................9167.2 Service primitive concept of OSI layered architecture ...................................................................9177.3 Security concept ..............................................................................................................................9187.4 V2G communication states ..............................................................................................................9197.5 Data link layer ...................................................................................................................................9207.6 Network layer ....................................................................................................................................9217.7 Transport layer .................................................................................................................................9227.8 V2G transfer protocol .......................................................................................................................9237.9 Presentation layer ............................................................................................................................9247.10 Application layer ..............................................................................................................................925

8 Application layer messages ........................................................................................................... 10268.1 General information and definitions .............................................................................................. 10278.2 Protocol handshake definition ....................................................................................................... 10288.3 V2G message definition ................................................................................................................. 12298.4 BodyElement Definitions ............................................................................................................... 12308.4.1 Common messages ........................................................................................................................ 12318.4.2 AC-Messages .................................................................................................................................. 21328.4.3 DC-Messages .................................................................................................................................. 21338.5 Complex data types ........................................................................................................................ 31348.5.1 Overview ......................................................................................................................................... 31358.5.2 Common ......................................................................................................................................... 31368.5.3 AC ................................................................................................................................................... 40378.5.4 DC ................................................................................................................................................... 40388.6 Identification modes and message set definitions ....................................................................... 43398.7 V2G communication timing............................................................................................................ 44408.7.1 Overview ......................................................................................................................................... 44418.7.2 Message sequence and communication session ......................................................................... 44428.7.3 Session setup and ready to charge ............................................................................................... 46438.8 Message Sequencing and Error Handling ..................................................................................... 46448.8.1 Overview ......................................................................................................................................... 46458.8.2 Basic Definitions for Error Handling ............................................................................................. 46468.8.3 ResponseCode handling ................................................................................................................ 46478.8.4 Request-Response Message Sequence Requirements ................................................................ 49488.9 Request-Response Message Sequence Examples ....................................................................... 62498.9.1 AC ................................................................................................................................................... 62508.9.2 DC ................................................................................................................................................... 6251

Annex A (informative) Mapping of Part 1 use case elements .................................................................. 6452A.1 Relation of Identification Modes and Use Case Elements ............................................................ 6453

Annex B (informative) Mapping of ISO 15118 message element names to SAE J2847/2 terms ............. 6554

Annex C (normative) Schema definition ................................................................................................... 6655


iv © SIEMENS AG 2018 – All rights reserved

Annex D (informative) Message examples ............................................................................................... 6756

Annex E (informative) Application of certificates..................................................................................... 6857

Annex F (informative) Security appliances and their associated certificates ......................................... 6958

Annex G (informative) Simplified Certificate Management in Trusted Environment .............................. 7059

Annex H (normative) Certificate profiles .................................................................................................. 7160

Annex I (normative) Using Contract Certificates for XML encryption ..................................................... 7261

Annex J (normative) Use of OEM Provisioning Certificates .................................................................... 7362

Annex K (informative) Summary of requirements .................................................................................... 746364


© SIEMENS AG 2018 – All rights reserved v

Foreword65

This clause of ISO/IEC DIS 15118-2 is applicable.66


vi © SIEMENS AG 2018 – All rights reserved

Introduction67


69


© SIEMENS AG 2018 – All rights reserved 7

Road vehicles — Vehicle to grid communication interface —70

Network and application protocol requirements for OppCharge71

1 Scope72


74

2 Normative references75

This clause of ISO/IEC DIS 15118-2 is applicable except as follows:76

Addition:77

OppCharge Core Specification, Technical description of the OppCharge interface, Volvo Buses78AB, December 201679(https://www.oppcharge.org/dok/OppCharge_Core_Specification.pdf)80

For detailed information refer to OppCharge web site: https://www.oppcharge.org/81

IEEE/Std 802.11™-2012, IEEEStandard for Information technology ― Telecommunications82and information exchange between systems ― Local and metropolitan area networks ―83specific requirements: Part 11: Wireless LAN Medium Access Control (MAC) and Physical84Layer (PHY) Specifications.85

86

3 Terms and definitions87


Addition:89

automatic connection device90ACD91components supporting the automatic connection and disconnection process for conductive92energy transfer between an EV and EV supply equipment93

pantograph94In context of OppCharge pantograph specifies a so called top-down pantograph. The95pantograph is mounted on a mast of the charging station. For charging the pantograph is96moved down to the counterpart contact interface that is mounted on the roof of the electric97vehicle.98

99

4 Symbols and abbreviated terms100


Addition:102

ACD Automatic connection device103


8 © SIEMENS AG 2018 – All rights reserved

5 Conventions104


Addition:106

The original requirements are quoted in cursive letter and in color blue. Deviations or107Restrictions to original requirements are specified under a new modified requirement number. A108new number is attached to the original number in a schema [“original number”_n]. For example:109[V2G2-OC-000_1], where [V2G-000] is the original requirement number.110

If any mandatory parameter specified by ISO/IEC DIS 15118-2 is not used for OppCharge111communication, a default value is set, “0” for integer type, an empty string “” for string type. In112case of other data types the default value is given at the value definition.113

If the usage of an element in the message is specified as “don’t care”, it is not forbidden to send114the information in this element, but this information may not be used by the receiver and the115sender cannot expect the receiver to act on the sent information. It is compareable to an116optional element, but to state out the difference to the standard “don’t care” is used instead and117can also be applied to elements that are mandatory in ISO/IEC DIS 15118-2 (2012).118

6 Document overview119




7 Basic requirements for V2G communication121

7.1 General information122


7.2 Service primitive concept of OSI layered architecture124


7.3 Security concept126

This clause of ISO/IEC DIS 15118-2 is NOT applicable.127

Restriction:128

In 1st version of OppCharge communication standard TLS, certificate based authentication and129contracts are not supported.130

Communication takes place via WLAN. The WLAN connection is secured by WPA2.131

7.4 V2G communication states132


7.5 Data link layer134

This clause of ISO/IEC DIS 15118-2 is not applicable. Instead of wired communication135OppCharge wireless communication is compliant to IEEE/Std 802.11TM-2012136

7.6 Network layer137


7.7 Transport layer139


Restriction:141

Subclause 7.7.3 and its subclauses are not applicable.142

7.8 V2G transfer protocol143


7.9 Presentation layer145

This clause of ISO/IEC DIS 15118-2 is applicable .146

7.10 Application layer147




8 Application layer messages149

8.1 General information and definitions150


8.2 Protocol handshake definition152


Original requirement:154

[V2G2-166] The EVCC shall initiate the handshake sending a supportedAppProtocolReq155message as depicted in Figure 16 to the SECC. This request message156provides a list of charging protocols supported by the EVCC.157

Addition:158

[V2G2-OC-166_1] The EVCC shall initiate the handshake sending a supportedAppProtocolReq159message only if following conditions are fulfilled:160- WLAN signal strength is not below -75 dBm161


[V2G2-167] Each entry in the list of supported EVCC protocols shall include the163ProtocolNamespace, the VersionNumberMajor and VersionNumberMinor,164the unique SchemaID dynamically assigned by the EVCC and the priority of165the protocol entry. The priority in the EVCC request message enables the166EVCC to announce the preferred application layer protocol where Priority167equal to 1 indicates the highest priority and priority equal to 20 indicates the168lowest priority. The number of protocols included in the request message is169limited to 20.170

Restriction:171

[V2G2-OC-167_1] In context of the OppCharge communication V 1.2.0 only one valid entry is172allowed as defined in Table 22_1.173


[V2G2-170] The SECC shall confirm (positively respond) an EVCC supported protocol175even if the values of the VersionNumberMinor in EVCC request message176does not match with the VersionNumberMinor of an SECC supported177protocol where the VersionNumberMajor matches.178

Deviation:179

[V2G2-OC-170_1] VersionNumberMajor and VersionNumberMinor together with180ProtocolNameSpace are used by SECC to match the protocol that is181supported by both EVCC and SECC. SECC will send182FAILED_NoNegotiation in case one of the criteria does not match. Refere to183in Table 22_2.184


[V2G2-172] Usually it is expected that the SECC is able to support the relevant186application layer protocols indicated by the EVCC. However when none of187



the application layer protocols included in the list received from the EVCC is188supported by the SECC, the ResponseCode in the response message shall189be equal to Failed_NoNegotiation indicating that the protocol negotiation190was not successful. In this error scenario the response message shall not191include a SchemaID.192

Addition:193

[V2G2-OC-172_1] Although a matching protocol version is found, ResponseCode194Failed_NoNeogotiation shall also be used, if SECC is not ready due to195technical reasons. SECC shall set ResponseCode to196Failed_NoNeogotiation, in case of197- Persistent isolation fault198- Positioning sensor error (EV not in position)199- E-Stop active200- Wind speed limit exceeded201- the charging station is in fatal error mode202

Table 22_1 and table 22_2 specifie the usage of supportedAppProtocol in OppCharge. Refer to203the original table 22 for semantics and type definition.204

Table 22_1 — Usage of message elements supportedAppProtocolReq205

Element Name EVCC

ProtocolNamespace "urn:iso:15118:2:2010:MsgDef"

VersionNumberMajor 1

VersionNumberMinor 0

SchemaID 0

Priority Don’t care

206

Table 22_2 — Usage of message elements supportedAppProtocolRes207

Element Name SECC

SchemaID Same as received from EV

ResponseCode

Used ResponseCode:- OK_SuccessfulNegotiation- Failed_NoNegotiation, if protocolmismatch or any HPC failureoccurs; refer to [V2G2-OC-172_1]

208

New requirements:209

[V2G2-OC-725] In case of an active charging session SECC shall not accept new sessions.210SECC shall answer to a SupportedAppProtocol request with211SupportedAppProtocol response with “ResponseCode =212FAILED_NoNegotiation”.213

214



8.3 V2G message definition215


8.4 BodyElement Definitions217

8.4.1 Common messages218

8.4.1.1 Overview219


8.4.1.2 Session Setup221

8.4.1.2.1 General222


8.4.1.2.2 Session Setup Request224



[V2G2-189] The message elements of this message shall be used as defined in Table22726.228

Deviation:229

[V2G2-OC-189_1] Instead of MAC address, EVCCID is a string of length 8, starting with 2230letters representing the vehicle vendor, followed by 6 digits for enumeration231of the specific vehicle. Refere to Table 26_1.232

NOTE: Format if the EVCCID is “VVnnnnnn“, where the two characters VV stand233for the vendor and “nnnnnn” is the specific vehicle number of the operator.234

Table 26_1 specifies the usage of SessionSetupReq in OppCharge. Refer to the original Table23526 for semantics and type definition.236

Table 26_1 — Usage of message elements SessionSetupReq237

Element Name EVCC

EVCCID8 ASCII characters, startingwith 2 letters followed by 6digits.

238

8.4.1.2.3 Session Setup Response239


Comments:241

- Following response codes are used by SECC:242



o OK and OK_NewSessionEstablished if a new session is established243successfully.244

o FAILED_SequenceError if a message is received other than sessionSetupReq.245

o FAILED if any internal error occurs.246

- ResponseCode OK_OldSessionJoined and FAILED_SignatureError are not used.247Refer to [V2G2-OC-461_1], [V2G2-OC-463_1] in subclause 8.8.3248

Table 27_1 specifies the usage of SessionSetupRes in OppCharge. Refer to the original Table24927 for semantics and type definition.250

Table 27_1 — Usage of message elements SessionSetupRes251

Element Name SECC

ResponseCode

Used ResponseCode:- OK- OK_NewSessionEstablished- FAILED- FAILED_SequenceError

EVSEID up to 32 ASCII characters, no predefinedformat

DateTimeNow Don’t care

252

8.4.1.3 Service Discovery253

8.4.1.3.1 Service Discovery handling254


8.4.1.3.2 Service Discovery Request256



[V2G2-194] The message elements of this message shall be used as defined in259Table 28.260

Restrictions:261

[V2G2-OC-194_1] The message elements of ServiceDiscoveryReq are not used by both262EVCC and SECC, refere to Table 28_1.263

Table 28_1 specifies the usage of ServiceDiscoveryReq in OppCharge. Refer to the original264Table 28 for semantics and type definition.265

Table 28_1 — Usage of message elements ServiceDiscoveryReq266

Element Name EVCC

ServiceScope Don’t careServiceCategory Don’t care

267



8.4.1.3.3 ServiceDiscoveryRes268


Comments:270

- Following resonse codes are used by SECC:271

∂ OK if ServiceDiscoveryReq is successfully processed.272

∂ FAILED_SequenceError if a message is received other than ServiceDiscoveryReq.273SessonStopReq is accepted to go to session stop handling.274

∂ FAILED_UnknownSession if SessionID differs from the currently used one.275

∂ FAILED if any internal errors occur.276

- ResponseCode FAILED_SignatureError is not used. Refer to [V2G2-OC-461_1] in277subclause 8.8.3278

- EVCC accepts only PaymentOption = ExternalPayment. Otherwise, it will end charging279session by termination of the session and send SessionStopReq. Refer to [V2G2-OC-280283_1] in subclause 8.5.2.9.281

- SECC sets only one entry in payment option list, paymentOption = ExternalPayment.282Refer to [V2G2-OC-283_1] in subclause 8.5.2.9.283

Table 29_1 specifies the usage of ServiceDiscoveryRes in OppCharge. Refer to the original284Table 29 for semantics and type definition.285

Table 29_1 — Usage of message elements ServiceDiscoveryRes286

Element Name SECC

ResponseCode

Used ResponseCode:- OK- FAILED- FAILED_SequenceError- FAILED_UnknownSession

PaymentOption ExternalPayment. Refer to [V2G2-OC-283_1] in subclause 8.5.2.9

ChargeService Refer to [V2G-OC-270_1] in subclause 8.5.2.3, [V2G-OC-272_1] insubclause 8.5.2.4

ServiceList Don’t care. Refer to subclause 8.5.2.2

287

8.4.1.4 Service Detail288

This clause of ISO/IEC DIS 15118-2 is not applicable.289

8.4.1.5 Service and Payment Selection290

8.4.1.5.1 Service and Payment Selection Handling291




Based on the provided services and the corresponding payment options by the SECC this293message pair allows the transmission of the selected PaymentOption, SelectedServices and294related ParameterSets. Depending on the selected payment additional messages295(PaymentDetails message pair) are exchanged.296

NOTE:297

The feature of Service and Payment Selection is not used. The298ServicePaymentSelectionReq/Res messages are passed through without any functions.299

8.4.1.5.2 Service and Payment Selection Request300




Restriction:305

[V2G2-OC-202_1] The parameters are not used, refere to Table 32_1.306

Table 32_1 specifies the usage of ServicePaymentSelectionReq for OppCharge. Refer to the307original Table 32 for semantics and type definition.308

Table 32_1 — Usage of message elements ServicePaymentSelectionReq309

Element Name EVCC

SelectedPaymentOption Don’t care (default value ExternalPayment )

SelectedServiceList Refer to subclause 8.5.2.24

310

8.4.1.5.3 Service and Payment Selection Response311


Comments:313


∂ OK if ServicePaymentSelectionReq is successfully processed.315

∂ FAILED_SequenceError if a message is received other than316ServicePaymentSelectionReq. SessonStopReq is accepted to go to session stop317handling.318



- FAILED_SignatureError, FAILED_PaymentSelectionInvalid and321FAILED_ServiceSelectionInvalid are not used. Refer to [V2G2-OC-461_1] [V2G2-OC-322465_1] [V2G2-OC-467_1] in subclause 8.8.3323



8.4.1.6 Payment Details324


8.4.1.7 Contract Authentication326

8.4.1.7.1 Contract Authentication Request327


Comment:329

The Contract Authentication request/responce are passed through without loop sequence.330



Restriction:334

[V2G2-OC-211_1] The parameters are not used for OppCharge, refere to Table 36_1.335

Table 36_1 specifies the usage of ContractAuthenticationReq for OppCharge. Refer to the336original Table 36 for semantics and type definition.337

Table 36_1 — Usage of message elements ContractAuthenticationReq338

Element Name EVCC

Id Don’t care

GenChallenge Don’t care

339

8.4.1.7.2 Contract Authentication Response340




Restrictions:345

[V2G2-OC-213_1] EVSEProcessing is not used for OppCharge, refere to Table 37_1.346

Comments:347


∂ OK if ContractAuthenticationReq is successfully processed.349

∂ FAILED_SequenceError if a message is received other than350ContractAuthenticationReq. SessonStopReq is accepted to go to session stop351handling.352





- FAILED_SignatureError and FAILED_CertificateExpired are not used. Refer to [V2G2-355OC-461_1] [V2G2-OC-475_1] in subclause 8.8.3356

Table 37_1 specifies the usage of ContractAuthenticationRes in OppCharge. Refer to the357original Table 37 for semantics and type definition.358

Table 37_1 — Usage of message elements ContractAuthenticationRes359

Element Name SECC

EVSEProcessing Don’t care (default Finished)

ResponseCode

Used ResponseCode:- OK- FAILED- FAILED_SequenceError- FAILED_UnknownSession

360

8.4.1.8 Charge Parameter Discovery361

8.4.1.8.1 Charge Parameter Discovery Handling362


8.4.1.8.2 Charge Parameter Discovery Request364



[V2G2-217] The EVCC shall use the EVRequestedEnergyTransterType as defined in367Table 39.368

Restrictions:369

[V2G2-OC-217_1] The EVCC shall only use DC_extended for370EVRequestedEnergyTransferType as defined in Table 39.371

Table 38_1 specifies the usage of ChargeParamenterDiscoveryReq in OppCharge. Refer to the372original Table 38 for semantics and type definition373

Table 38_1 — Usage of message elements ChargeParameterDiscoveryReq374

Element Name EVCC

EVRequestedEnergyTransferType DC_extended

AC_EVChargeParameter Not applied for OppCharge

DC_EVChargeParameter Refer to subclause 8.5.4.3

375

376



8.4.1.8.3 Charge Parameter Discovery Response377




Restrictions:382

[V2G2-OC-220_1] EVSEProcessing and SAScheduleList are not used for OppCharge,383refere to Table 40_1.384

Comments:385


∂ OK if ChargeParamenterDiscoveryReq is successfully processed.387

∂ FAILED_SequenceError if a message is received other than388ChargeParamenterDiscoveryReq. SessonStopReq is accepted to go to session389stop handling.390


∂ FAILED_WrongChargeParameter if received EVRequestedEnergyTransferType392is other than DC_extended393


- FAILED_SignatureError and FAILED_WrongEnergyTransferType are not used, refer to395[V2G2-OC-461_1] [V2G2-OC-476_1] in subclause 8.8.3.396

- DC_EVSEStatus contained in DC_EVSEChargeParameter is not used, refer to397subclause 8.5.4.1398

Table 40_1 specifies the usage of ChargeParamenterDiscoveryRes in OppCharge. Refer to the399original Table 40 for semantics and type definition.400

Table 40_1 — Usage of message elements ChargeParameterDiscoveryRes401

Element Name SECC

EVSEProcessing Don’t care. (default Finished)

ResponseCode

Used ResponseCode:- OK- FAILED- FAILED_SequenceError- FAILED_UnknownSession- FAILED_WrongChargeParameter

SAScheduleList Don’t care. Refer to subclause 8.5.2.12

AC_EVSEChargeParameter Not applied for OppCharge

DC_EVSEChargeParameter Refer to subclause 8.5.4.4

402NOTE: Reneogotation is not supported.403



8.4.1.9 Power Delivery404

8.4.1.9.1 Power Delivery Handling405


8.4.1.9.2 Power Delivery Request407




Restrictions:412

[V2G2-OC-222_1] ReadyToChargeState parameter is used to request EVSE to start or stop413charging process, refere to Table 41_1414

Table 41_1 specifies the usage of PowerDeliveryReq in OppCharge. Refer to the original Table41541 for semantics and type definition.416

Table 41_1 — Usage of message elements PowerDeliveryReq417

Element Name EVCC

ReadyToChargeState true to start chargingfalse to stop charging

ChargingProfile Don’t care. Refer to subclause8.5.2.10

DC_EVPowerDeliveryParameter Don’t care. Refer to subclause 8.5.4.5

418

8.4.1.9.3 Power Delivery Response419


Comments:421


∂ OK if PowerDeliveryReq is successfully processed.423

∂ FAILED_SequenceError if a message is received other than PowerDeliveryReq.424SessonStopReq is accepted to go to session stop handling.425



- FAILED_SignatureError, FAILED_ChargingProfileInvalid,428FAILED_TariffSelectionInvalid and FAILED_PowerDeliveryNotApplied are not used,429refer to [V2G2-OC-461_1] [V2G2-OC-478_1] [V2G2-OC-479_1] [V2G2-OC-480_1] in430subclause 8.8.3431



Table 42_1 specifies the usage of PowerDeliveryRes in OppCharge. Refer to the original Table43242 for semantics and type definition.433

Table 42_1 — Usage of message elements PowerDeliveryRes434

Element Name SECC

ResponseCode

Used ResponseCode:- OK,- FAILED- FAILED_SequenceError- FAILED_UnknownSession

DC_EVSEStatus Don’t care. Refer to subclause 8.5.4.1

435

8.4.1.10 Certificate Update436

This clause of ISO/IEC DIS 15118-2 is not applicable. Not used in OppCharge V 1.2.0.437

8.4.1.11 Certificate Installation438

This clause of ISO/IEC DIS 15118-2 is not applicable. Not used in OppCharge V 1.2.0.439

8.4.1.12 Session Stop440

8.4.1.12.1 SessionStopReq/Res handling441


Original statement:443

This V2G message pair shall be used for terminating a V2G communication session initated by444preceding SessionSetupReq message.445

Addition:446

Due to the nature of ACD charging, after termination of the charging process the pantograph447has to be raised up at first. The electric vehicle shall be kept immobilized until the pantograph is448in the upper home position. As long as the pantograph is not in the upper home position, the449EVCC shall continuously send SessionStopReq and the SECC shall respond with response450code FAILED. If the pantograph is in the upper home postion, SECC shall send451SessionStopRes with response code OK.452

SessionStopReq can be sent at any communication state by EVCC to request termination of453charging process. The response code FAILED_SequenceError is not applicable in this case.454

The minimum time interval between two SessionStopReq messages shall be larger than 100455ms in order to limit the message load on the system.456

8.4.1.12.2 Session Stop Request457


8.4.1.12.3 Session Stop Response459




Deviations:461

- Following SECC response codes are used :462

∂ OK if SessionStopReq is successfully processed and the pantograph is in upper463home position.464

∂ FAILED if the pantograph is not in the upper home position or any internal errors465occurs. Refer to [V2G2-OC-572_1] in subclause 8.8.4.3.1.466

- In the case of “ResponseCode = FAILED” EVCC shall not terminate the session but467continue to send SessionStopReq. Refer to [V2G2-OC-507_1] in subclause 8.8.4.2.1.468

- In any error situation whether caused by an interrupted v2g communication or a469hardware defect the ACD status is unknown to the EVCC. The EV cannot be released470the regular way. The driver has to double check that the ACD is properly disconnected471and the EV can safely leave the charge point. In that case the driver can abort the472immobilization caused by the EVCC by using OEM specific means. Refer to [V2G2-473OC-507_2] in subclause 8.8.4.2.1.474

Table 47_1 specifies the usage of SessionStopRes in OppCharge. Refer to the original Table47547 for semantics and type definition.476

Table 47_1 — Usage of message elements SessionStopRes477

Element Name SECC

ResponseCode

Used ResponseCode:- OK, if the pantograph is in the upper home position then thevehicle can be released safely.- FAILED, if the pantograph is not in the upper home position.

478

8.4.2 AC-Messages479


8.4.3 DC-Messages481

8.4.3.1 Overview482


8.4.3.2 Cable Check484

8.4.3.2.1 Cable Check Handling485



For a safe DC charging a cable check must be performed.488

Addition:489

For plug in charging the EVSE is connected by wire to the EV all the time from the beginning of490the charge procedure until the end. In contrast to plug in charging the ACD/pantograph is not491



connected at this point of the procedure. Thus the EVSE is not yet connected to the EV492electrically.493

As a precondition for cable check the ACD/pantograph has to be connected to the EV’s494charging interface first. Because of the lack of a corresponding message pair for the connection495process in the underlying version of the ISO standard, the cable check message pair is used to496integrate this process step into the sequences.497

The 1st CableCheckReq message induces the EVSE to move down the pantograph.498CableCheckReq/Res are repeated until the pantograph is connected to the EV’s charging499interface and the CP status changes from A to B. After that the regular cable check sequence500continues.501

8.4.3.2.2 Cable Check Request502



The cable check request asks for the cable check status of the EVSE and e.g. tells the EVSE if505the connector is locked on EV side and if the EV is ready to charge.506

Deviation:507

At first the pantograph will be activated in order to connect the EVSE with the electrical circuits508of the vehicle. As a precondition for this the vehicle needs to be positioned within the ACD509contact area tolerances correctly. The CableCheck message is repeated as long as the510pantograph is moving, contacting and while the insulation test is executed.511



Restrictions:515

[V2G2-OC-250_1] The DC_EVStatus may not be handeled by EVSE, as defined Table51651_1.517

Table 51_1 specifies the usage of CableCheckReq in OppCharge. Refer to the original Table51851 for semantics and type definition.519

Table 51_1 — Usage of message elements CableCheckReq520

Element Name EVCC

DC_EVStatus Don’t care. Refer to subclause 8.5.4.2

521

8.4.3.2.3 Cable Check Response522


524

525



Comments:526

- EVSEProcessing variable is used to indicate whether the cable check has completed.527EVSEProcessing is set to “Finished”, if the pantograph is connected and the isolation528test has finished. Otherwise EVSEProcessing is set to “Ongoing”. Refere to Table52952_1.530


o OK if CableCheckReq is successfully processed.532

o FAILED_SequenceError if a message is received other than CableCheckReq,533or charge control is in a wrong state. SessonStopReq is accepted to go to534session stop handling.535

o FAILED_UnknownSession if SessionID differs from the currently used one.536

o FAILED if any internal errors occur.537

- FAILED_SignatureError is not used, refer to [V2G2-OC-461_1] in subclause 8.8.3.538

- EVSEStatusCode, contained in DC_EVSEStatusType (subclause 8.5.4.1), is used to539indicate the state of the isolation test. In context of ACD DC_EVSEStatusCode is set to540Reserved_8 to indicate the moving state until the pantograph is connected to the EV’s541charging interface. Status code EVSE_IsolationMonitoringActive indicates the542processing of the the isolation monitor, refer to [V2G2-OC-365_1] defined in subclause5438.5.4.1.544

- EVSEIsolationStatus is used to indicate status of the isolation test. It is always set to545Invalid before the isolation test is finished, refer to [V2G2-OC-365_1] defined in546subclause 8.5.4.1.547

- SECC shall carry out following steps as also shown in Figure OC_1:548


[V2G2-OC-701] After receiving the first CableCheckReq, the SECC shall start activation of550the pantograph and respond with CableCheckRes containing551“ResponseCode = OK” and EVSEStatusCode = Reserved_8 and552EVSEIsolationStatus = Invalid and EVSEProcessing = Ongoing within553V2G_SECC_Msg_Performance_Time according to Table 103_1.554

[V2G2-OC-702] If the activation of the pantograph fails, the SECC shall respond with555CableCheckRes containing “ResponseCode = FAILED” and556EVSEStatusCode = EVSE_NotReady and EVSEIsolationStatus = Invalid557and EVSEProcessing = Finished. The allowed next request shall be558SessionStopReq and the V2G_SECC_Sequence_Timeout is set according559to Table 103_1.560

[V2G2-OC-703] While waiting for the pantograph moving down to the end position, the561SECC shall respond with CableCheckRes containing “ResponseCode = OK”562and EVSEStatusCode = Reserved_8 and EVSEIsolationStatus = Invalid563and EVSEProcessing = Ongoing within564V2G_SECC_Msg_Performance_Time according to Table 103_1.565

[V2G2-OC-704] If the pantograph has not reached the end position within566V2G_SECC_ACD_Connection_Timeout according to Table OC_1, the567



SECC shall respond with CableCheckRes containing “ResponseCode =568FAILED” and EVSEStatusCode = EVSE_NotReady and569EVSEIsolationStatus = Invalid and EVSEProcessing = Finished and the570SECC commands the pantograph to its home position. The allowed next571request shall be SessionStopReq and the V2G_SECC_Sequence_Timeout572is set according to Table 103_1.573

[V2G2-OC-705] If the pantograph has reached the end position and the SECC has574measured CP state B with a related CP voltage to be smaller than 10.5 V575and larger or equal than 7.5 V within576V2G_SECC_ACD_Endpostion_to_B_Timeout according to Table OC_1, the577SECC shall respond with CableCheckRes containing “ResponseCode = OK”578and EVSEStatusCode = EVSE_IsolationMonitoringActive and579EVSEIsolationStatus = Invalid and EVSEProcessing = Ongoing within580V2G_SECC_Msg_Performance_Time according to Table 103_1.581

[V2G2-OC-709] If the pantograph has reached the end position and the SECC has582measured CP state to be C or D with a related CP voltage to be smaller583than 7.5 V and larger or equal than 2 V without detecting state B before, the584SECC shall activate the DC-breaker and respond with CableCheckRes585containing “ResponseCode = OK” and EVSEStatusCode =586EVSE_IsolationMonitoringActive and EVSEIsolationStatus = Invalid and587with EVSEProcessing = Ongoing within588V2G_SECC_Msg_Performance_Time according to Table 103_1.589

NOTE In case EVCC reacts very fast on state B and changes control pilot to state590C within a very short time, it is possible that the SECC does not detect state591B but state C when it is waiting for state B. In the case the SECC detects a592direct change from CP state A to C the timer for593V2G_SECC_ACD_Endpostion_to_B_Timeout is not relevant anymore and594therefore reset.595

[V2G2-OC-706] If the pantograph has reached the end position and the SECC has not596measured CP state B, C or D within597V2G_SECC_ACD_Endpostion_to_B_Timeout according to Table OC_1, the598SECC shall respond with CableCheckRes containing “ResponseCode =599FAILED” and EVSEStatusCode = EVSE_NotReady and600EVSEIsolationStatus = Invalid and EVSEProcessing = Finished and the601SECC commands the pantograph to its home position. The allowed next602request shall be SessionStopReq and the V2G_SECC_Sequence_Timeout603is set according to Table 103_1.604

[V2G2-OC-707] If the SECC has measured CP state to be C or D with a related CP voltage605to be smaller than 7.5 V and larger or equal than 2 V within606V2G_SECC_CP_Transition_B_to_C_Timeout according to Table OC_1, the607SECC shall activate the DC-breaker, and respond with CableCheckRes608containing “ResponseCode = OK” and EVSEStatusCode =609EVSE_IsolationMonitoringActive and EVSEIsolationStatus = Invalid and610EVSEProcessing = Ongoing within V2G_SECC_Msg_Performance_Time611according to Table 103_1.612

[V2G2-OC-708] If the pantograph has reached the end position and CP state B is active but613the SECC has not measured CP state to be C or D with a related CP614voltage to be smaller than 7,5 V and larger or equal than 2 V within615V2G_SECC_CP_Transition_B_to_C_Timeout according to Table OC_1, the616SECC shall respond with CableCheckRes containing “ResponseCode =617FAILED” and EVSEStatusCode = EVSE_NotReady and618



EVSEIsolationStatus = Invalid and with EVSEProcessing = Finished and the619SECC commands the pantograph to its home position. The allowed next620request shall be SessionStopReq and the V2G_SECC_Sequence_Timeout621is set according to Table 103_1.622

[V2G2-OC-710] If DC-breaker closed within V2G_SECC_Breaker_Activation_Timeout623according to Table OC_1, the SECC shall start the insulation monitoring and624respond with CableCheckRes containing “ResponseCode = OK” and625EVSEStatusCode = EVSE_IsolationMonitoringActive and626EVSEIsolationStatus = Invalid and EVSEProcessing = Ongoing. The627allowed next request shall be CableCheckReq and the628V2G_SECC_Sequence_Timeout is set according to Table 103_1.629

[V2G2-OC-711] If DC-breaker does not close within630V2G_SECC_Breaker_Activation_Timeout according to Table OC_1, the631SECC shall respond with CableCheckRes containing “ResponseCode =632FAILED” and EVSEStatusCode = EVSE_NotReady and633EVSEIsolationStatus = Invalid and with EVSEProcessing = Finished. The634allowed next request shall be SessionStopReq and the635V2G_SECC_Sequence_Timeout is set according to Table 103_1.636

[V2G2-OC-712] While the isolation test is processing the EVSE shall respond with637CableCheckRes containing “ResponseCode = OK” and EVSEStatusCode =638EVSE_IsolationMonitoringActive and EVSEIsolationStatus = Invalid and639EVSEProcessing = Ongoing within V2G_SECC_Msg_Performance_Time640according to Table 103_1.641

[V2G2-OC-713] If the insulation monitor indicates an insulation error after642V2G_SECC_Isolation_Monitoring_Time according to Table OC_1, the643SECC shall respond with CableCheckRes containing “ResponseCode =644FAILED” and EVSEStatusCode = EVSE_NotReady and645EVSEIsolationStatus = Fault (or Invalid) and with EVSEProcessing =646Finished. The allowed next request shall be SessionStopReq and the647V2G_SECC_Sequence_Timeout is set according to Table 103_1.648

[V2G2-OC-714] As soon as the isolation test has been finished successfully the SECC shall649respond with CableCheckRes containing “ResponseCode = OK” and650EVSEStatusCode = EVSE_Ready and EVSEIsolationStatus = Valid and651EVSEProcessing = Finished. The allowed next request shall be652PreChargeReq and the V2G_SECC_Sequence_Timeout is set according to653Table 103_1.654



655

Figure OC_1 SECC cable check handling656

657



Table OC_1 — timeout value of Cable Check handling658

Name Value [s]

V2G_SECC_ACD_Connection_Timeout 20

V2G_SECC_ACD_Disconnection_Timeout 20

V2G_SECC_ACD_Endpostion_to_B_Timeout 2

V2G_SECC_CP_Transition_B_to_C_Timeout 2

V2G_SECC_Breaker_Activation_Timeout 1

V2G_SECC_Isolation_Monitoring_Time 10

659

NOTE: V2G_SECC_ACD_Endpostion_to_B_Timeout serves for the debouncing of660the CP signal during the contacting process.661

Table 52_1 specifies the usage of CableCheckRes in OppCharge. Refer to the original Table66252 for semantics and type definition.663

Table 52_1 — Usage of message elements CableCheckRes664

Element Name SECC

EVSEProcessing

Indicates if the conection and cable check process is finished.- Finished, if the pantograph is in end position and theisolation test is completed successfully,- Ongoing, if pantograph is moving or isolation test is not yetf inished

ResponseCode

Used ResponseCode:- OK,- FAILED,- FAILED_SequenceError,- FAILED_UnknownSession

DC_EVSEStatus refer to subclause 8.5.4.1

665

8.4.3.3 Pre Charge666

8.4.3.3.1 Pre Charge Handling667


8.4.3.3.2 Pre Charge Request669




Restriction:674

[V2G2-OC-254_1] DC_EVStatus may not be handeled by EVSE, refere to Table 53_1.675

Table 53_1 specifies the usage of PreChargeReq in OppCharge. Refer to the original Table 53676for semantics and type definition.677



Table 53_1 — Usage of message elements PreChargeReq678

Element Name EVCC


EVTargetVoltage Target Voltage requested by EV.

EVTargetCurrent

Current demanded by EV set to 0, but don’t care.Note: the EVSE has to command the appropriate current to theAC/DC converter in oder to support the preCharge function at theleast possible current level.(OEM specific)

679

8.4.3.3.3 Pre Charge Response680




Restriction:685

[V2G2-OC-256_1] DC_EVSEStatus may not be handeled by EVSE, refere to Table 54_1.686

Comments:687


o OK if PreChargeReq is successfully processed.689

o FAILED_SequenceError if a message is received other than PreChargeReq or690charge control is in a wrong state. SessonStopReq is accepted to go to session691stop handling.692




Table 54_1 specifies the usage of PreChargeRes in OppCharge. Refer to the original Table 54696for semantics and type definition.697

Table 54_1 — Usage of message elements PreChargeRes698

Element Name SECC

ResponseCode



EVSEPresentVoltage Present voltage of EVSE. (present EVSEoutput voltage)

699



8.4.3.4 Current Demand700

8.4.3.4.1 Current Demand Handling701


8.4.3.4.2 Current Demand Reqest703


Comment:705

Parameter EVRESSSOC, contained in DC_EVStatus is used to communicate the available706SOC to the SECC which is a fraction of the physical battery SOC and is defined by vehicle707OEM. Refer to subclause 8.5.4.2. Table 55_1 specifies the usage of CurrentDemandReq in708OppCharge. Refer to the original Table 55 for semantics and type definition.709

Table 55_1 — Usage of message elements CurrentDemandReq710

Element Name EVCC

DC_EVStatusOnly EVRESSSOC is used, all otherparameters may not be handeled by EVSE.Refer to subclause 8.5.4.2

EVTargetCurrent BMS current requested by the EV.

EVMaximumVoltageLimit Maximum voltage allowed by the EV.

EVMaximumCurrentLimit Maximum current allowed by the EV.

EVMaximumPowerLimit Maximum power allowed by the EV.

BulkChargingComplete Don’t care

ChargingComple Don’t care

RemainingTimeToFullSoc Don’t care

RemainingTimeToBulkSoC Don’t care

EVTargetVoltage Voltage requested for charging

711

NOTE: EVMaximumPowerLimit is not necessarily the product of712EVMaximumVoltageLimit and EVMaximumCurrentLimit. It is the actual power713limit that can be handled by the EV’s RESS and wiring infrastructure.714

8.4.3.4.3 Current Demand Response715




Restriction:720

[V2G2-OC-260_1] The message elements of this message shall be used as defined in Table72156_1. DC_EVSEStatus is not used.722

723



Comments:724


o OK if CurrentDemandReq is successfully processed.726

o FAILED_SequenceError if a message is received other than727CurrentDemandReq, PowerDeliveryReq or charge control is in a wrong state.728SessonStopReq is accepted to go to session stop handling.729




Table 56_1 specifies the usage of CurrentDemandRes in OppCharge. Refer to the original733Table 56 for semantics and type definition.734

Table 56_1 — Usage of message elements CurrentDemandRes735

Element Name SECC

ResponseCode



EVSEPressentVoltage Present output voltage of the EVSE

EVSEPresentCurrent Present out current of EVSE

EVSECurrentLimitAchieved If set to TRUE, the EVSE has reachedits current limit

EVSEVoltageLimitAchieved If set to TRUE, the EVSE has reachedits voltage limit

EVSEPowerLimitAchieved If set to TRUE, the EVSE has reachedits power limit

EVSEMaximumVoltageLimit

Deviation to standard:Minimum of EVMaximumVoltageLimitand the maximum voltage the EVSE candeliver

EVSEMaximumCurrentLimit

Deviation to standard:Minimum of EVMaximumCurrentLimitand the maximum current the EVSE candeliver

EVSEMaximumPowerLimit Maximum power the EVSE can deliver.

736NOTE: The EVSE sends the minimum of EVMaximumVoltageLimit and the maximum voltage737the EVSE can deliver. The value of EVMaximumVoltageLimit is sent as confirmation that the738limit of the vehicle is accepted and can be provided by the station. Otherwise in case the station739can only provide less voltage than the EVMaximumVoltageLimit, it sends the stations limit740value. The same approach is applied to the MaximumCurrentLimit.741



8.4.3.5 Welding Detection742

This clause of ISO/IEC DIS 15118-2 is not used.743

8.5 Complex data types744

8.5.1 Overview745


8.5.2 Common747

8.5.2.1 ServiceTagType748



[V2G2-266] The message element shall be used as defined in Table 59.751

Restriction:752

[V2G2-OC-266_1] The message element shall be used as defined in Table 59_1.753

Table 59_1 specifies the usage of ServiceTagType in OppCharge. Refer to the original Table75459 for semantics and type definition.755

Table 59_1 — Usage of message element ServiceTagType756

Element Name SECC

ServiceID 1, only DC_extended is supported

ServiceName Optional, recommend to use “OPPCharge”

ServiceCategory recommend to use “EVCharging”

ServiceScope Don’t care

757

8.5.2.2 ServiceTagListType758




Restriction:762


Table 60_1 specifies the usage of ServiceTagListType in OppCharge, contained in764ServiceDiscoveryRes, refer to subclause 8.4.1.3.3. Refer to the original Table 61 for semantics765and type definition.766



Table 60_1 — Usage of message element ServiceTagListType767

Element Name SECC

Service Don’t care. Refer to subclause 8.5.2.3

768

8.5.2.3 ServiceType769




Restriction:773


Table 61_1 specifies the usage of ServiceType for OppCharge, contained in775ServiceDiscoveryRes (subclause 8.4.1.3.3). Refer to the original Table 61 for semantics and776type definition.777

Table 61_1 — Usage of message element ServiceType778

Element Name SECC

ServiceTag Refer to subclause 8.5.2.1

FreeService Don’t care

779

8.5.2.4 ServiceChargeType780




Restriction:784

[V2G2-OC-272_1] The message elements shall be used as defined in Table 62_1.785

Table 62_1 specifies the usage of ServiceChargeType for OppCharge, contained in786ServiceDiscoveryRes (subclause 8.4.1.3.3). Refer to the original Table 62 for semantics and787type definition.788

Table 62_1 — Usage of message elements ServiceChargeType789

Element Name SECC

EnergyTransferType only DC_extended

790



8.5.2.5 CertificateChainType791

This clause of ISO/IEC DIS 15118-2 is not applicable. The messages PaymentDetailsReq,792CertificateUpdateReq/Res and CertificateInstallationRes which contains CertificateChainType793are not used in OppCharge V 1.2.0.794

8.5.2.6 MeterInfoType795

This clause of ISO/IEC DIS 15118-2 is not applicable. The data type is contained in796ChargingStatusRes and MeteringReceiptReq which are not used in OppCharge V 1.2.0.797

8.5.2.7 PhysicalValueType798


8.5.2.8 Notification Type800

This clause of ISO/IEC DIS 15118-2 is is applicable except as follows:801



Restriction:804


Table 67_1 specifies the usage of NotificationType for OppCharge, contained in the V2G806message header. Refer to the original Table 67 for semantics and type definition.807

Table 67_1 — Usage of message elements NotificationType808

Element Name SECC

FaultCode Don’t care.

FaultMsg Don’t care.

809

8.5.2.9 PaymentOptionsType810




Restriction:814

[V2G2-OC-283_1] The list of payment options contains only one entry and only payment option815type “ExternalPayment” is supported, option “Contract” is not used, refere to816Table 68_1.817

Table 68_1 specifies the usage of PaymentOptionsType in OppCharge, contained in818ServiceDiscoveryRes (subclause 8.4.1.3.3). Refer to the original Table 68 for semantics and819type definition.820



Table 68_1 — Usage of message elements PaymentOptionsType821

Element Name SECC

PaymentOption ExternalPayment

822

8.5.2.10 ChargingProfileType823




Restriction:827


Table 69_1 specifies the usage of ChargingProfileType for OppCharge, contained in829PowerDeliveryReq. Refer to the original Table 69 for semantics and type definition.830

Table 69_1 — Usage of message elements ChargingProfileType831

Element Name SECC

SAScheduleTupleID Don’t care.

ProfileEntry Don’t care.

832

8.5.2.11 ProfileEntryType833




Restriction:837


Table 70_1 specifies the usage of PorfileEntryType for OppCharge, contained in839ChargingProfileType in PowerDeliveryReq, refer to subclause 8.4.1.9.2 . Refer to the original840Table 70 for semantics and type definition.841

Table 70_1 — Usage of message elements ProfileEntryType842

Element Name SECC

ChargingProfileEntryStart Don’t care.

ChargingProfileEntryMaxPower Don’t care.

843

8.5.2.12 SAScheduleListType844






Restriction:848


Table 71_1 specifies the usage of SAScheduleListType for OppCharge, contained in850ChargeParameterDiscoveryRes, refer to subclause 8.4.1.8.3. Refer to the original Table 71 for851semantics and type definition.852

Table 71_1 — Usage of message elements SAScheduleListType853

Element Name SECC

SAScheduleTuple Don’t care. Refer to subclause 8.5.2.13

854

8.5.2.13 SAScheduleTupleType855




Restriction:859


Table 72_1 specifies the usage of SAScheduleTupleType for OppCharge, contained in861SAScheduleListType in ChargeParameterDiscoveryRes, refer to subclause 8.4.1.8.3. Refer to862the original Table 72 for semantics and type definition.863

Table 72_1 — Usage of message elements SAScheduleTupleType864

Element Name SECC

SAScheduleTupleID Don’t care.

PMaxSchedule Don’t care. Refer to subclause 8.5.2.14

Sales Tariff Don’t care. Refer to subclause 8.5.2.16

865

8.5.2.14 PMaxScheduleType866




Restriction:870




Table 73_1 specifies the usage of PMaxScheduleType for OppCharge, contained in872SAScheduleTupleType in ChargeParameterDiscoveryRes, refer to subclause 8.4.1.8.3. Refer873to the original Table 73 for semantics and type definition.874

Table 73_1 — Usage of message elements PMaxScheduleType875

Element Name SECC

PMaxScheduleID Don’t care.

PMaxScheduleEntry Don’t care. Refer to subclause 8.5.2.15

876

8.5.2.15 PMaxScheduleEntryType877




Restriction:881


Table 74_1 specifies the usage of PMaxScheduleEntryType for OppCharge, contained in883SAScheduleTupleType in ChargeParameterDiscoveryRes, refer to subclause 8.4.1.8.3. Refer884to the original Table 74 for semantics and type definition.885

Table 74_1 — Usage of message elements PMaxScheduleEntryType886

Element Name SECC

RelativeTimeInterval Don’t care. Refer to subclause 8.5.2.18

PMax Don’t care.

887

8.5.2.16 SalesTariffType888




Restriction:892


Table 75_1 specifies the usage of SalesTariffType for OppCharge, contained in894SAScheduleTupleType in ChargeParameterDiscoveryRes, refer to subclause 8.4.1.8.3. Refer895to the original Table 75 for semantics and type definition.896

897

898



Table 75_1 — Usage of message elements SalesTariffType899

Element Name SECC

SalesTariffID Don’t care.

SalesTariffDescription Don’t care.

NumEPriceLevels Don’t care.

SalesTariffEntry Don’t care. Refer to subclause 8.5.2.17

900

8.5.2.17 SalesTariffEntryType901




Restriction:905


Table 76_1 specifies the usage of SalesTariffEntryType for OppCharge, contained in907SAScheduleTupleType in ChargeParameterDiscoveryRes, refer to subclause 8.4.1.8.3. Refer908to the original Table 76 for semantics and type definition.909

Table 76_1 — Usage of message elements SalesTariffType910

Element Name SECC

RelativeTimeInterval Don’t care. Refer to subclause 8.5.2.18

EPriceLevel Don’t care.

ConsumptionCost Don’t care. Refer to subclause 8.5.2.19

911

8.5.2.18 RelativeTimeIntervalType912




Restriction:916


Table 77_1 specifies the usage of RelativeTimeIntervalType for OppCharge, contained in918PMaxScheduleEntryType in ChargeParameterDiscoveryRes, refer to subclause 8.4.1.8.3.919Refer to the original Table 77 for semantics and type definition.920

921



Table 77_1 — Usage of message elements PMaxScheduleEntryType922

Element Name SECC

duration Don’t care.

start Don’t care.

923

8.5.2.19 ConsumptionCostType924




Restriction:928


Table 78_1 specifies the usage of ConsumptionCostType for OppCharge, contained in930SalesTariffType in ChargeParameterDiscoveryRes, refer to subclause 8.4.1.8.3. Refer to the931original Table 78 for semantics and type definition.932

Table 78_1 — Usage of message elements ConsumptionCostType933

Element Name SECC

Cost Don’t care. Refer to subclause 8.5.2.20

StartValue Don’t care.

934

8.5.2.20 CostType935



[V2G2-616] The message element shall be used as defined in Table 79 and Table 80.938

Restriction:939


Table 79_1 specifies the usage of CostType and CostKindType for OppCharge, contained in941SalesTariffType in ChargeParameterDiscoveryRes, refer to subclause 8.4.1.8.3. Refer to the942original Table 79 for semantics and type definition.943

Table 79_1 — Usage of message elements CostType944

Element Name SECC

amount Don’t care.

amountMultiplier Don’t care.

costKind Don’t care.

945



8.5.2.21 ServiceParameterListType946

This clause of ISO/IEC DIS 15118-2 is not applicable. The data type is contained in947ServiceDetailRes which is not used in OppCharge V 1.2.0948

8.5.2.22 ParameterSetType949

This clause of ISO/IEC DIS 15118-2 is not applicable. The data type is contained in950ServiceParameterListType in ServiceDetailRes which is not used in OppCharge V 1.2.0951

8.5.2.23 ParameterType952

This clause of ISO/IEC DIS 15118-2 is not applicable. The data type is contained in953ParameterSetType in ServiceDetailRes which is not used in OppCharge V 1.2.0954

8.5.2.24 SelectedServiceListType955




Restriction:959


Table 84_1 specifies the usage of SelectedServiceListType in OppCharge, contained in961ServicePaymentSelectionReq (subclause 8.4.1.5.2). Refer to the original Table 84 for962semantics and type definition.963

Table 84_1 — Usage of message elements SelectedServiceListType964

Element Name SECC

SelectedService Refer to subclause 8.5.2.25

965

8.5.2.25 SelectedServiceType966




Restriction:970

[V2G2-OC-352_1] ServiceID is always set to 1, refere to Table 85_1.971

Table 85_1 specifies the usage of SelectedServiceType in OppCharge, contained in972SelectedServiceListType (subclause 8.5.2.24). Refer to the original Table 85 for semantics and973type definition.974



Table 85_1 — Usage of message elements SlectedServiceType975

Element Name SECC

ServiceID 1 (only DC_extended issupported)

ParameterSetID Don’t care

976

8.5.2.26 SubCertificatesType977

This clause of ISO/IEC DIS 15118-2 is not applicable. The data type is contained in978CertificateChainType. The messages PaymentDetailsReq, CertificateUpdateReq/Res and979CertificateInstallationRes which contain this data type are not used in OppCharge V 1.2.0.980

8.5.2.27 ListOfRootCertificateIDsType981

This clause of ISO/IEC DIS 15118-2 is not applicable. The data type is contained in982CertificateUpdateReq and CertificateInstallationReq which are not used in OppCharge V 1.2.0.983

8.5.3 AC984

This clause of ISO/IEC DIS 15118-2 does not apply. OppCharge does not use AC power985transfer.986

8.5.4 DC987

8.5.4.1 DC_EVSEStatusType988




Restriction:992

[V2G2-OC-365_1] The message elements shall be used as defined in Table 91_1.993EVSEIsolationStatus is only used in CableCheckRes to signal if isolation994test is completed. DC_EVSEStatusCode is only used in CableCheckRes to995signal if pantograph is moving and if isolation test is in progress or complete,996as defined in Table 91_1. Also refert to subclause 8.4.3.2.3 for cable check997response.998

Table 91_1 specifies the usage of DC_EVSEStatusType in OppCharge, contained in999DC_EVSEChargeParameter (subclause 8.5.4.4) used by the following messages1000CableCheckRes (subclause 8.4.3.2.3), PreChargeRes (subclause 8.4.3.3.3),1001PowerDeliveryRes (subclause 8.4.1.9.3), CurrentDemandRes (subclause 8.4.3.4.3). Refer to1002the original Table 91 for semantics and type definition.1003

Table 91_1 — Usage of message elements DC_EVSEStatusType1004

Element Name SECC

Notif icationMaxDelay Don’t care



Element Name SECC

EVSENotificationAllowed values:

- None- StopCharging

EVSEIsolationStatus

Used only in CableCheckRes:- Invalid in case of ongoing isolation test- Safe in case of successful isolation test

Note: in the related openV2G implementation “Valid” is usedinstead of “Safe”. This will not contradict interoperability.

DC_EVSEStatusCode

Used only in CableCheckRes:- Reserved_8: until pantograph is in lower position- EVSE_IsolationMonitoringActive: after pantograph is in

lower postion, until isolation test is finished- EVSE_Ready: isolation test is finished.

1005

NOTE: EVSENotification = StopCharging is additionaly used in case of EVSE errors. It1006is expected that EVCC immediatetly aborts the charging process by going to1007session stop process.1008

8.5.4.2 DC_EVStatusType1009




Restriction:1013

[V2G2-OC-368_1] The message element shall be used as defined in Table 93_1. The1014parameter EVRESSSOC is mandatory in CurrentDemandReq, refer to1015subclause 8.4.3.4.21016

Table 93_1 specifies the usage of DC_EVStatusType for OppCharge, contained in1017DC_EVChargeParameter (subclause 8.5.4.3) used in the following messages CableCheckReq1018(subclause 8.4.3.2.2), PreChargeReq (subclause 8.4.3.3.2), CurrentDemandReq (subclause10198.4.3.4.2). Refer to the original Table 93 for semantics and type definition.1020

Table 93_1 — Usage of message elements DC_EVStatusType1021

Element Name EVCC

EVReady Don’t care.(default TRUE)

EVCabinConditioning Don’t care

EVRESSConditioning Don’t care

EVErrorCode Don’t care(default NO_ERROR)

EVRESSSOCavailable SOC, mandatory use inCurrentDemandReq, optional for othermessages, refer to subclause 8.4.3.4.2

1022

NOTE Available SOC is fraction of the physical SOC of the battery and is defined1023by vehicle OEM (subclause 8.4.3.4.2).1024



8.5.4.3 DC_EVChargeParameterType1025




Restriction:1029

[V2G2-OC-371_1] The message element shall be used as defined in Table 95_1.1030DC_EVStatus may not be handeled by EVSE, refer to subclause 8.5.4.2.1031

Table 95_1 specifies the usage of DC_EVChargeParameterType for OppCharge, contained in1032ChargeParameterDiscoveryReq (subclause 8.4.1.8.2). Refer to the original Table 95 for1033semantics and type definition.1034

Table 95_1 — Usage of message elements DC_EVChargeParameterType1035

Element Name EVCC


EVMaximumCurrentLimit Maximum current supported by EV

EVMaximumPowerLimit Maximum power supported by EV

EVMaximumVoltageLimit Maximum voltage supported by EV

EVEnergyCapacity Don’t care

EVEnergyRquest Don’t care

FullSOC Don’t care

BulkSOC Don’t care

1036

8.5.4.4 DC_EVSEChargeParameterType1037




Restriction:1041

[V2G2-OC-373_1] The message element shall be used as defined in Table 96_1.1042DC_EVSEStatus is not used, refer to subclause 8.5.4.1.1043

Table 96_1 specifies the usage of DC_EVSEChargeParameterType for OppCharge, contained1044in ChargeParameterDiscoveryRes (subclause 8.4.1.8.3). Refer to the1045original Table 96 for semantics and type definition.1046

Table 96_1 — Usage of message parameter DC_EVSEChargeParameterType1047

Element Name SECC




Element Name SECC

EVSEMaximumCurrentLimitDeviation to standard:Minimum of EVMaximumCurrentLimit and themaximum current the EVSE can deliver

EVSEMaximumPowerLimit Maximum power EVSE can deliver

EVSEMaximumVoltageLimitDeviation to standard:Minimum of EVMaximumVoltageLimit andthe maximum voltage the EVSE can deliver

EVSEMinimumCurrentLimit Minimum current EVSE can deliver

EVSEMinimumVoltageLimit Minimum voltage EVSE can deliver

EVSECurrentRegulationTolerance Don’t care.

EVSEPeakCurrentRipple Don’t care

EVSEEnergyToBeDelivered Don’t care.

1048

NOTE: The EVSE sends the minimum of EVMaximumVoltageLimit and the maximum1049voltage the EVSE can deliver. The value of EVMaximumVoltageLimit is sent as1050confirmation that the limit of the vehicle is accepted and can be provided by the1051station. Otherwise in case the station can only provide less voltage than the1052EVMaximumVoltageLimit, it sends the stations limit value. The same approach is1053applied to the MaximumCurrentLimit.1054

8.5.4.5 DC_EVPowerDeliveryParameterType1055




Restriction:1059

[V2G2-OC-375_1] The message element shall be used as defined in Table 97_1.1060DC_EVStatus is not used, refer to subclause 8.5.4.1.1061

Table 97_1 specifies the usage of DC_EVPowerDeliveryParameterType for OppCharge,1062contained in PowerDeliveryReq (subclause 8.4.1.9.2). Refer to the original Table 97 for1063semantics and type definition.1064

1065

Table 97_1 — Usage of message parameter DC_EVPowerDeliveryParameterType1066

Element Name EVCC


BulkChargingComplete Don’t care.

ChargingComplete Don’t care.

1067

8.6 Identification modes and message set definitions1068

This clause of ISO/IEC DIS 15118-2 is not applicable. This document defines only messages1069and parameters used in OppCharge V 1.2.0.1070



8.7 V2G communication timing1071

8.7.1 Overview1072



The monitoring of a V2G Communication Session is based on two Timer categories:1075

-- Commnunication Setup Timer: Monitors the time from plug-in until the Session Setup1076 message. It allows deciding if the communication setup was successful.1077

-- Ready to Charge Timer: Monitors the time from plug-in until the first Power Delivery1078 message. It allows deciding if the request for power form the EVCC was successful.1079

Restriction:1080

Since OppCharge is via WLAN communication, the plug-in charging timing is not applicable.1081

In version V 1.2.0 of OppCharge the Communication Setup Timer and Ready to Charge Timer1082are not used.1083

8.7.2 Message sequence and communication session1084

8.7.2.1 Definitions1085


Table 103_1 — EVCC and SECC message sequence and session timing parameter1087values1088

Name MessageType Value [s]

V2G_EVCC_Msg_Timeout

SupportedAppProtocol 2

SessionSetup 2

ServiceDiscovery 2

ServicePaymentSelection 2

PaymentDetails Not applicable

ContractAuthentication2

(not defiened in theoriginal table 103)

ChargeParameterDiscovery 2

ChargingStatus Not applicable

MeteringReceipt Not applicable

PowerDelivery 2

CableCheck2

(deviation to standard)

PreCharge 2(deviation to standard)

CurrentDemand 0,25



Name MessageType Value [s]

WeldingDetection Not applicable

SessionStop 2

Certif icateInstallation Not applicable

Certif icateUpdate Not applicable

V2G_SECC_Msg_Performance_Time

SupportedAppProtocol 1,5

SessionSetup 1,5

ServiceDiscovery 1,5

ServicePaymentSelection 1,5

PaymentDetails Not applicable

ContractAuthentication 1.5

ChargeParameterDiscovery 1,5

ChargingStatus Not applicable

MeteringReceipt Not applicable

PowerDelivery 1,5

CableCheck 20

PreCharge 0,1

CurrentDemand 0,025

WeldingDetection Not applicable

SessionStop 1,5

Certif icateInstallation Not applicable

Certif icateUpdate Not applicable

V2G_EVCC_Sequence_Performance_Time

ChargeParameterDiscovery 10

CableCheck 40

PreCharge 10

PowerDelivery 10

(all other messages) Not used

V2G_SECC_Sequence_TimeoutCurrentDemandReq 10

(all other messages) 60

1089

NOTE: SessionStop, CableCheck, PreCharge, CurrentDemand are looping1090messages and can cause high message load on communication channel, if1091transmission interval is too short. For that reason it is recommended to allow1092up to 10 requests per second.1093

8.7.2.2 EVCC timing for request-response message pairs1094

This clause of ISO/IEC DIS 15118-2 is applicable, refer to Table 103_1 for timeout values for1095each V2G message type.1096

8.7.2.3 SECC timing for response-request message sequence1097

This clause of ISO/IEC DIS 15118-2 is applicable, refer to Table 103_1 for timeout values for1098each V2G message type.1099



8.7.3 Session setup and ready to charge1100

This clause of ISO/IEC DIS 15118-2 is not applicable. Session setup timer and ready to charge1101timer are not used in OppCharge V 1.2.0.1102

8.8 Message Sequencing and Error Handling1103

8.8.1 Overview1104


8.8.2 Basic Definitions for Error Handling1106


8.8.3 ResponseCode handling1108

8.8.3.1 Common requirements1109



[V2G2-461] The response message shall contain the ResponseCode1112'FAILED_SignatureError' if the validation of the Security element in the1113message header failed.1114

Restriction:1115

[V2G2-OC-461_1] ResponseCode 'FAILED_SignatureError' is not used for all messages.1116


[V2G2-463] The message 'SessionSetupRes' shall contain the specific ResponseCode1118'OK_OldSessionJoined' if processing of the SessionSetupReq message1119was successful and the same SessionID as used in the request message is1120contained in the response message.1121

Restriction:1122

[V2G2-OC-463_1] The message 'SessionSetupRes' does not use ResponseCode1123'OK_OldSessionJoined'.1124

NOTE: It is not a usecase for OppCharge to suspend a session and resume it1125afterwards. OppCharge is designed to transfer high energy amounts within1126a short time. Therefore sessions are not suspended, re-negotiation does not1127take place and charge schedules and profiles are not applied.1128


[V2G2-465] The message 'ServicePaymentSelectionRes' shall contain the1130ResponseCode 'FAILED_PaymentSelectionInvalid' if the1131SelectedPaymentOption contained in the ServicePaymentSelectionReq1132message was not part of the offered PaymentOptionList of1133ServiceDiscoveryRes.1134



Restriction:1135

[V2G2-OC-465_1] The message 'ServicePaymentSelectionRes' does not use the1136ResponseCode 'FAILED_PaymentSelectionInvalid'.1137


[V2G2-467] The message 'ServicePaymentSelectionRes' shall contain the1139ResponseCode 'FAILED_ServiceSelectionInvalid' if the SelectedServiceList1140contained in the ServicePaymentSelectionReq message contains a1141ServiceID which was not contained in the offered ServiceList of1142ServiceDiscoveryRes.1143

Restriction:1144

[V2G2-OC-467_1] The message 'ServicePaymentSelectionRes' does not use the1145ResponseCode 'FAILED_ServiceSelectionInvalid'1146


[V2G2-475] The message 'ContractAuthenticationRes' shall contain the ResponseCode1148'FAILED_ChallengeInvalid' if the challenge response contained in the1149ContractAuthenticationReq message in attribute GenChallenge is not valid1150versus the provided GenChallenge in PaymentDetailsRes.1151

Restriction:1152

[V2G2-OC-475_1] The message 'ContractAuthenticationRes' does not use the ResponseCode1153'FAILED_ChallengeInvalid'.1154


[V2G2-476] The message 'ChargeParameterDiscoveryRes' shall contain the1156ResponseCode 'FAILED_WrongEnergyTransferMode' if the content of1157attribute 'RequestedEnergyTransferMode' in the1158ChargeParameterDiscoveryReq message is not valid..1159

Restriction:1160

[V2G2-OC-476_1] The message 'ChargeParameterDiscoveryRes' does not use the1161ResponseCode 'FAILED_WrongEnergyTransferMode'. If the content of1162attribute 'RequestedEnergyTransferMode' in the1163ChargeParameterDiscoveryReq message is not valid, the ResponseCode1164“FAILED_WrongChargeParameter' is used.1165


[V2G2-477] The message 'ChargeParameterDiscoveryRes' shall contain the1167ResponseCode 'FAILED_WrongChargeParameter' if the content of attribute1168'EVChargeParameter' in the ChargeParameterDiscoveryReq message is1169not valid, e.g. wrong parameter set is provided, one or multiple parameters1170can not be interpreted.1171

1172

1173



Restriction:1174

[V2G2-OC-477_1] The message 'ChargeParameterDiscoveryRes' uses the ResponseCode1175'FAILED_WrongChargeParameter' only if the content of attribute1176'RequestedEnergyTransferMode' is not “DC_extended”.1177


[V2G2-478] The message 'PowerDeliveryRes' shall contain the ResponseCode1179'FAILED_ChargingProfileInvalid' if the content of attribute 'ChargingProfile'1180in the PowerDeliveryReq message violates a power limitation provided in1181'ChargeParameterDiscoveryRes'.1182

Restriction:1183

[V2G2-OC-478_1] The message 'PowerDeliveryRes' does not use the ResponseCode1184'FAILED_ChargingProfileInvalid'.1185


[V2G2-479] The message 'PowerDeliveryRes' shall contain the ResponseCode1187'FAILED_TariffSelectionInvalid' if the content of element 'ChargingProfile' in1188the PowerDeliveryReq message contains a SAScheduleTupleID which was1189not contained in the 'SAScheduleList' element provided in1190'ChargeParameterDiscoveryRes'.1191

Restriction:1192

[V2G2-OC-479_1] The message 'PowerDeliveryRes' does not use the ResponseCode1193'FAILED_TariffSelectionInvalid'.1194


[V2G2-480] The message 'PowerDeliveryRes' shall contain the ResponseCode1196'FAILED_PowerDeliveryNotApplied' if the EV supply equipment is not able1197to deliver energy.1198

Restriction:1199

[V2G2-OC-480_1] The message 'PowerDeliveryRes' does not use the ResponseCode1200'FAILED_PowerDeliveryNotApplied'.1201

8.8.3.2 AC Specific Requirements1202

This clause of ISO/IEC DIS 15118-2 does not apply. OppCharge does not use AC power1203transfer.1204

8.8.3.3 DC Specific Requirements1205


Restriction:1207

[V2G2-669] and [V2G2-670] are not applied for OppCharge. Refer to subclause 8.4.3.2.3 for1208related requirements for calble check handling.1209



8.8.4 Request-Response Message Sequence Requirements1210

8.8.4.1 General requirements1211



[V2G2-679] If the parameter EVSENotification in EVSEStatus is equal to StopCharging,1214the EVCC shall stop charging within the value of the parameter1215NotificationMaxDelay is in the EVSEStatus.1216

Deviation:1217

[V2G2-OC-679_1] If the parameter EVSENotification in EVSEStatus is equal to StopCharging,1218the EVCC shall stop charging immediately, thefore the parameter1219NotificationMaxDelay is not used. The next allowed request message is1220SessionStopReq.1221

Restriction:1222

Requirements [V2G2_672] [V2G2_673] [V2G2_674] [V2G2_675] [V2G2_676] [V2G2_680] are1223not applicable for OppCharge.1224

8.8.4.2 EVCC1225


The EVCC behavior defining all valid request-response message sequences for OppCharge is1227shown in1228Figure OC_2.1229

8.8.4.2.1 Common requirements1230



[V2G2-484] The EVCC shall stop the V2G_Communication_Session when1233V2G_EVCC_Msg_Timer is equal or lager than V2G_EVCC_Msg_Timeout1234of ‘supportedAppProtocolRes’ according to Table 103.1235

Deviation:1236

[V2G2-OC-484_1] The EVCC shall stop the V2G communication session when1237V2G_EVCC_Msg_Timer is equal or larger than V2G_EVCC_Msg_Timeout1238of 'supportedAppProtocolRes' according to Table 103_1, or if the response1239message containing a 'ResponseCode = FAILED_NoNegotiation'.1240


[V2G2-488] The EVCC shall stop the V2G_Communication_Session when1242V2G_EVCC_Msg_Timer is equal or lager than V2G_EVCC_Msg_Timeout1243or ‘ResponseCode = FAIL’ of ‘ServiceDiscoveryRes’ according to Table 103.1244

1245



Deviation:1246

[V2G2-OC-488_1] The EVCC shall send a SessionStopReq to stop the1247V2G_Communication_Session, when V2G_EVCC_Msg_Timer is equal or1248lager than V2G_EVCC_Msg_Timeout according to Table 103_1 or1249‘ResponseCode = FAIL’ of ‘ServiceDiscoveryRes’.1250


[V2G2-492] The EVCC shall stop the V2G_Communication_Session when1252V2G_EVCC_Msg_Timer is equal or lager than V2G_EVCC_Msg_Timeout1253or ‘ResponseCode = FAIL’ of ‘ServicePaymentSelectionRes’ according to1254Table 103.1255

Deviation:1256

[V2G2-OC-492_1] The EVCC shall send a SessionStopReq to stop the1257V2G_Communication_Session, when V2G_EVCC_Msg_Timer is equal or1258lager than V2G_EVCC_Msg_Timeout according to Table 103_1 or1259‘ResponseCode = FAIL’ of ‘ServicePaymentSelectionRes’.1260


[V2G2-504] The EVCC shall stop the V2G_Communication_Session when1262V2G_EVCC_Msg_Timer is equal or lager than V2G_EVCC_Msg_Timeout1263or ‘ResponseCode = FAIL’ of ‘ContractAuthenticationRes’ according to1264Table 103.1265

Deviation:1266

[V2G2-OC-504_1] The EVCC shall send a SessionStopReq to stop the1267V2G_Communication_Session, when V2G_EVCC_Msg_Timer is equal or1268lager than V2G_EVCC_Msg_Timeout according to Table 103_1 or1269‘ResponseCode = FAIL’ of ‘ContractAuthenticationRes’.1270


[V2G2-506] The EVCC shall stop the V2G_Communication_Session when1272V2G_EVCC_Msg_Timer is equal or lager than V2G_EVCC_Msg_Timeout1273or ‘ResponseCode = FAIL’ of ‘ChargeParameterDiscoveryRes’ according to1274Table 103.1275

Deviation:1276

[V2G2-OC-506_1] The EVCC shall send a SessionStopReq to stop the1277V2G_Communication_Session, when V2G_EVCC_Msg_Timer is equal or1278lager than V2G_EVCC_Msg_Timeout according to Table 103_1 or1279‘ResponseCode = FAIL’ of ‘ChargeParameterDiscoveryRes’.1280


[V2G2-507] The EVCC shall stop the V2G_Communication_Session when1282V2G_EVCC_Msg_Timer is equal or lager than V2G_EVCC_Msg_Timeout1283or ‘ResponseCode = FAIL’ of ‘SessionStopRes’ according to Table 103.1284

1285



Deviation:1286

[V2G2-OC-507_1] The EVCC shall continue to send a new SessionStopReq, when1287V2G_EVCC_Msg_Timer is equal or lager than V2G_EVCC_Msg_Timeout1288according to Table 103_1 or ‘ResponseCode = FAIL’ of ‘SessionStopRes’1289

[V2G2-OC-507_2] If EVCC does not receive a SessionStop response within1290V2G_EVCC_MSG_Timeout, EVCC shall stop the communication session1291but not release the immobilization.1292


[V2G2-OC-720] After the 1st SessionStop response with ‘ResponseCode = OK’, EVCC may1294send further SessionStop requests with the same session_id. In that case1295the SECC may continue answering with SessionStop response and1296‘ResponseCode = OK’.1297

[V2G2-OC-721] All ResponseCodes of SessionStop response other than “OK” are handled1298like ‘ResponseCode = FAILED’. (e.g. Handling of ResponseCodes1299FAILED_SequenceError).1300

[V2G2-OC-722] If EVCC receives a response message with a different SessionID than the1301SessionID it received in the SessionSetupRes, it shall ignore the message.1302

Restriction:1303

Requirements [V2G2_489] [V2G2_491] [V2G2_493] [V2G2_494] [V2G2_495] [V2G2_496]1304[V2G2_497] [V2G2_498] [V2G2_499] [V2G2_500] [V2G2_501] [V2G2_502] [V2G2_503]1305[V2G2_683] [V2G2_684] [V2G2_685] are not applicable for OppCharge.1306

8.8.4.2.2 AC specific requirements1307

This clause of ISO/IEC DIS 15118-2 does not apply. OppCharge does not use AC power1308transferf.1309

8.8.4.2.3 DC specific requirements1310



[V2G2-524] The EVCC shall stop the V2G_Communication_Session when1313V2G_EVCC_Msg_Timer is equal or lager than V2G_EVCC_Msg_Timeout1314or ‘ResponseCode = FAIL’ of ‘CableCheckRes’ according to Table 103.1315

Deviation:1316

[V2G2-OC-524_1] The EVCC shall send a SessionStopReq to stop the1317V2G_Communication_Session, when V2G_EVCC_Msg_Timer is equal or1318lager than V2G_EVCC_Msg_Timeout according to Table 103_1, or1319‘ResponseCode = FAIL’ of ‘CableCheckRes’, or EVSEProcessing =1320Finished, but EVSEIsolationStatus = Fault.1321

Note [V2G2-OC-713] states out that CableCheckRes sends ‘ResponseCode =1322FAIL’ in case of an isolation fault. It is recommended to use the1323ResponseCode for error handling. That allows a uniform error handling to all1324messages.1325




[V2G2-526] The EVCC shall stop the V2G_Communication_Session when1327V2G_EVCC_Msg_Timer is equal or lager than V2G_EVCC_Msg_Timeout1328or ‘ResponseCode = FAIL’ of ‘PreChargeRes’ according to Table 103.1329

Deviation:1330

[V2G2-OC-526_1] The EVCC shall send a SessionStopReq to stop the1331V2G_Communication_Session, when V2G_EVCC_Msg_Timer is equal or1332lager than V2G_EVCC_Msg_Timeout according to Table 103_1 or1333‘ResponseCode = FAIL’ of ‘PreChargeRes’.1334


[V2G2-529] The EVCC shall stop the V2G_Communication_Session when1336V2G_EVCC_Msg_Timer is equal or lager than V2G_EVCC_Msg_Timeout1337or ‘ResponseCode = FAIL’ of ‘PowerDeliveryRes’ according to Table 103.1338

Deviation:1339

[V2G2-OC-529_1] The EVCC shall send a SessionStopReq to stop the1340V2G_Communication_Session, when V2G_EVCC_Msg_Timer is equal or1341lager than V2G_EVCC_Msg_Timeout according to Table 103_1 or1342‘ResponseCode = FAIL’ of ‘PowerDeliveryRes’.1343


[V2G2-532] The EVCC shall stop the V2G_Communication_Session when1345V2G_EVCC_Msg_Timer is equal or lager than V2G_EVCC_Msg_Timeout1346or ‘ResponseCode = FAIL’ of ‘CurrentDemandRes’ according to Table 103.1347

Deviation:1348

[V2G2-OC-532_1] The EVCC shall send a SessionStopReq to stop the1349V2G_Communication_Session, when V2G_EVCC_Msg_Timer is equal or1350lager than V2G_EVCC_Msg_Timeout according to Table 103_1 or1351‘ResponseCode = FAIL’ of ‘CurrentDemandRes’.1352

Restriction:1353

Requirements [V2G2_533] [V2G2_534] [V2G2_620] [V2G2_535] [V2G2_686] are not1354applicable for OppCharge.1355



Wait for supportedAppProtocolRes

Wait for SessionSetupRes

Wait for ServiceDiscoveryRes

Wait for ServiceAndPaymentSelectionRes

Wait for ContractAuthenticationRes

Wait for ChargeParameterDiscoveryRes

Wait for CableCheckRes

Wait for PreChargeRes

Wait for PowerDeliveryRes

Wait for CurentDemandRes

Wait for SessionStopRes

[V2G2-484]

[V2G2-486]

[V2G2-483]

Initial EVCC side

[V2G2-485]

[V2G2-487]

[V2G2-490]

[V2G2-509]

[V2G2-505]

[V2G2-599]

[V2G2-OC-488_1]

[V2G2-OC-492_1]

[V2G2-OC-504_1]

[V2G2-OC-506_1]

[V2G2-OC-524_1][V2G2-617]

[V2G2-525]

[V2G2-528]

[V2G2-618]

[V2G2-530]

[V2G2-527]

[V2G2-531]

[V2G2-OC-532_1]

[V2G2-OC-526_1]

[V2G2-OC-529_1]

Stop Communication Session

Stop ComFork

SessionStop Fork

[V2G2-507][V2G2-508]

[V2G2-619]

[V2G2-OC-507_1][V2G2-OC-720]

[V2G2-OC-507_2]

1356Figure OC_2 EVCC Communication states for OppCharge V2G messaging1357



8.8.4.3 SECC1358

The SECC behavior defining all valid request-response message sequences for OppCharge is1359shown in Figure_OC_3:1360

8.8.4.3.1 Common requirements1361


V2G2-536] The SECC shall enter a wait state for supportedAppProtocolReq, set the1363timeout V2G_SECC_Sequence_Timeout to the value MessageType as1364defined in Table 103, reset the V2G_SECC_Sequence_Timer and start1365monitoring the V2G_SECC_Sequence_Timer.1366

Deviation:1367

[V2G2-OC-536_1] The SECC shall enter a wait state for supportedAppProtocolReq without1368timeout handling. The SECC continuously waits for1369supportedAppProtocolReq.1370


[V2G2-537] The SECC shall Stop the V2G Communication Session when1372V2G_SECC_Sequence_Timer is equal or larger than1373V2G_SECC_Sequence_Timeout according to Table 103.1374

Addition:1375

[V2G2-OC-537_1] When V2G_SECC_Sequence_Timer is equal or larger than1376V2G_SECC_Sequence_Timeout according to Table 103_1 then the SECC1377shall wait for SessionStopReq1378


[V2G2-538] The SECC shall respond with the corresponding response message1380containing a “ResponseCode = FAILED_SequenceError” within1381V2G_SECC_Msg_Performance_Time according to Table 103, if request1382message was received that the SECC does not expect in the wait state.1383

Deviation:1384

[V2G2-OC-538_1] The SECC shall respond with the corresponding response message1385containing a “ResponseCode = FAILED_SequenceError' within1386V2G_SECC_Msg_Performance_Time according to Table 103_1, if request1387message was received that the SECC does not expect in the wait state. The1388SECC shall then wait for SessionStopReq.1389


[V2G2-545] The SECC shall respond with a ServiceDiscoveryRes containing1391“ResponseCode = OK” within V2G_SECC_Msg_Performance_Time1392according to Table 103, if the processing of the information is passed1393successfully. The allowed next request shall be ServiceDetailReq and1394ServiceAndPaymentSelectionReq and the V2G_SECC_Sequence_Timeout1395is set according to Table 103.1396



Deviation:1397

[V2G2-OC-545_1] The SECC shall respond with a ServiceDiscoveryRes containing1398“ResponseCode = OK” within V2G_SECC_Msg_Performance_Time1399according to Table 103_1, if the processing of the information is passed1400successfully. The allowed next request shall be1401ServiceAndPaymentSelectionReq and the V2G_SECC_Sequence_Timeout1402is set according to Table 103_1.1403


[V2G2-546] The SECC shall respond with a ServiceDiscoveryRes containing1405“ResponseCode = FAIL” within V2G_SECC_Msg_Performance_Time1406according to Table 103, if the processing of the information is not1407successfully.1408

Deviation:1409

[V2G2-OC-546_1] The SECC shall respond with a ServiceDiscoveryRes containing1410“ResponseCode = FAIL” within V2G_SECC_Msg_Performance_Time1411according to Table 103_1, if the processing of the information is not1412successfully and then wait for SessionStopReq.1413


[V2G2-551] The SECC shall respond with a ServicePaymentSelectionRes containing1415“ResponseCode = OK” within V2G_SECC_Msg_Performance_Time1416according to Table 103, if the processing of the information is successfully1417passed. The allowed next request shall be PaymentDetailReq,1418CertificateInstallationReq and CertificateUpdateReq if Message Set “AC1419Charging Pnc” is selected and ContractAuthenticationReq if Message Set1420“AC Charging EIM” is selected. V2G_SECC_Sequence_Timeout is set1421according to Table 103.1422

Deviation:1423

[V2G2-OC-551_1] The SECC shall respond with a ServicePaymentSelectedRes containing1424“ResponseCode = OK” within V2G_SECC_Msg_Performance_Time1425according to Table 103_1, if the processing of the information is1426successfully passed. The allowed next request shall be1427ContractAuthenticationReq and the V2G_SECC_Sequence_Timeout is set1428according to Table 103_1.1429


[V2G2-552] The SECC shall respond with a ServicePaymentSelectionRes containing1431“ResponseCode = FAIL” within V2G_SECC_Msg_Performance_Time1432according to Table 103, if the processing of the information is not1433successfully.1434

Deviation:1435

[V2G2-OC-552_1] The SECC shall respond with a ServicePaymentSelectionRes containing1436“ResponseCode = FAIL” within V2G_SECC_Msg_Performance_Time1437according to Table 103_1, if the processing of the information is not1438successfully and then wait for SessionStopReq.1439




[V2G2-564] The SECC shall respond with ContractAuthenticationRes containing1441“ResponseCode = FAIL” within V2G_SECC_Msg_Performance_Time1442according to Table 103, if the processing of the information is not1443successfully.1444

Deviation:1445

[V2G2-OC-564_1] The SECC shall respond with ContractAuthenticationRes containing1446“ResponseCode = FAIL” within V2G_SECC_Msg_Performance_Time1447according to Table 103_1, if the processing of the information is not1448successfully and then wait for SessionStopReq.1449


[V2G2-566] The SECC shall respond with CharingParameterDiscoveryRes containing1451“ResponseCode = FAIL” within V2G_SECC_Msg_Performance_Time1452according to Table 103, if the processing of the information is not1453successfully.1454

Deviation:1455

[V2G2-OC-566_1] The SECC shall respond with ChargingParameterDiscoveryRes containing1456“ResponseCode = FAIL” within V2G_SECC_Msg_Performance_Time1457according to Table 103_1, if the processing of the information is not1458successfully and then wait for SessionStopReq.1459


[V2G2-572] The SECC shall respond with SessionStopRes containing “ResponseCode1461= FAILED” within V2G_SECC_Msg_Performance_Time according to Table1462103, if the processing of the information is not successful.1463

Addition:1464

[V2G2-OC-572_1] In case of OppCharge the SECC shall respond with SessionStopRes1465containing “ResponseCode = FAILED”, if the pantograph is going to be1466raised and not in the upper home position.1467


[V2G2-OC-723] If SECC does not receive a SessionStop request within1469V2G_SECC_Sequence_Timeout, SECC shall command the ACD to its1470home position (if not already done) and stop the communication session.1471After the ACD has reached its home position SECC shall accept new1472sessions.1473

[V2G2-OC-724] If SECC does not detect ACD in its home position within1474V2G_SECC_ACD_Disconnection_Timeout, it shall change to error mode1475and keep sending SessionStop response with ‘ResponseCode = FAILED’1476when a SessionStop request is received.1477

1478

1479



Restriction:1480

Requirements [V2G2_547] [V2G2_548] [V2G2_549] [V2G2_553] [V2G2_554] [V2G2_555]1481[V2G2_556] [V2G2_557] [V2G2_558] [V2G2_559] [V2G2_560] [V2G2_561] [V2G2_567]1482[V2G2_568] [V2G2_569] [V2G2_687] [V2G2_688] are not applicable for OppCharge.1483

NOTE: Requirements [V2G2_567], [V2G2_568], [V2G2_569] are applicable for AC, but the1484standard refers it in the common chapter.1485

8.8.4.3.2 AC specific requirements1486

This clause of ISO/IEC DIS 15118-2 does not apply. OppCharge does not use AC power1487transfer .1488

8.8.4.3.3 DC specific requirements1489



[V2G2-582] The SECC shall respond with ChargeParameterDiscoveryRes containing1492“ResponseCode = OK” and "EVSEProcessing=Finished" and a valid1493parameter SASchedule within V2G_SECC_Msg_Performance_Time1494according to Table 103, if the processing of the information is successfully1495passed. The allowed next request shall be CableCheckReq and the1496V2G_SECC_Sequence_Timeout is set according to Table 103.1497

Deviation:1498

[V2G2-OC-582_1] The SECC shall respond with ChargeParameterDiscoveryRes containing1499“ResponseCode = OK” and "EVSEProcessing=Finished" within1500V2G_SECC_Msg_Performance_Time according to Table 103_1, if the1501processing of the information is successfully passed. The allowed next1502request shall be CableCheckReq and the V2G_SECC_Sequence_Timeout1503is set according to Table 103_1.1504


[V2G2-658] The SECC shall measure state C or D as defined in IEC 61851-1 (IO-1506SET_CPSTATE.indication (CPState=C or D)) before receiving a Cable1507Check Request for sending a Cable Check Response Message with1508parameter ResponseCode set to ‘OK’ otherwise it shall send1509ResponseCode set to ‘FAILED’.1510

Restriction:1511

[v2G2-658] is not applied for OppCharge. Refer to subclause 8.4.3.2.3 for related requirements1512for cable check handling.1513


[V2G2-584] The SECC shall respond with CableCheckRes containing ResponseCode =1515OK” and “EVSEProcessing=Finished” within1516V2G_SECC_Msg_Performance_Time according to Table 103, if the1517processing of the information is successfully passed and calble check is1518finished. The allowed next request shall be PreChargeReq and the1519V2G_SECC_Sequence_Timeout is set according to Table 103.1520



Deviation:1521

[V2G2-OC-584_1] The SECC shall respond with CableCheckRes containing ResponseCode =1522OK”, “EVSEProcessing=Finished”, EVSEStatusCode = EVSE_Ready,1523EVSEIsolationStatus = Safe within V2G_SECC_Msg_Performance_Time1524according to Table 103_1, if the processing of the information is1525successfully passed and calble check is finished as defined in subclause15268.4.3.2.3. The allowed next request shall be PreChargeReq and the1527V2G_SECC_Sequence_Timeout is set according to Table 103_1.1528


[V2G2-621] The SECC shall respond with CableCheckRes containing ResponseCode =1530OK” and “EVSEProcessing=Ongoing” within1531V2G_SECC_Msg_Performance_Time according to Table 103, if the1532processing of the information is successfully passed and calble check is1533ongoing. The allowed next request shall be CableCheckReq and the1534V2G_SECC_Sequence_Timeout is set according to Table 103.1535

Deviation:1536

[V2G2-OC-621_1] The SECC shall respond with CableCheckRes containing ResponseCode =1537OK”, “EVSEProcessing=Ongoing”, EVSEStatusCode = Reserved_8,1538EVSEIsolationStatus = Invalid within V2G_SECC_Msg_Performance_Time1539according to Table 103_1, if the processing of the information is1540successfully passed and the pantograph has not reached the end position1541yet as defined in subclause 8.4.3.2.1. The allowed next request shall be1542CableCheckReq and the V2G_SECC_Sequence_Timeout is set according1543to Table 103_1.1544

[V2G2-OC-621_2] The SECC shall respond with CableCheckRes containing ResponseCode =1545OK”, “EVSEProcessing=Ongoing”, EVSEStatusCode =1546EVSE_IsolationMonitoringActive, EVSEIsolationStatus = Invalid within1547V2G_SECC_Msg_Performance_Time according to Table 103_1, if the1548processing of the information is successfully passed and the isolation test1549has not completed yet as defined in subclause 8.4.3.2.1. The allowed next1550request shall be CableCheckReq and the V2G_SECC_Sequence_Timeout1551is set according to Table 103_1.1552


[V2G2-585] The SECC shall respond with CableCheckRes containing “ResponseCode1554= FAIL” within V2G_SECC_Msg_Performance_Time according to Table 103,1555if the processing of the information is not successfully.1556

Deviation:1557

[V2G2-OC-585_1] The SECC shall respond with CableCheckRes containing “ResponseCode1558= FAIL” within V2G_SECC_Msg_Performance_Time according to Table1559103_1, if the processing of the information is not successfully and then wait1560for SessionStopReq.1561

1562

1563




[V2G2-588] The SECC shall respond with PreChargeRes containing “ResponseCode =1565FAIL” within V2G_SECC_Msg_Performance_Time according to Table 103,1566if the processing of the information is not successfully.1567

Deviation:1568

[V2G2-OC-588_1] The SECC shall respond with a PreChargeRes containing “ResponseCode1569= FAIL” within V2G_SECC_Msg_Performance_Time according to Table1570103_1, if the processing of the information is not successfully and then wait1571for SessionStopReq.1572


[V2G2-601] The SECC shall respond with a PowerDeliveryRes containing1574“ResponseCode = OK” within V2G_SECC_Msg_Performance_Time1575according to Table 103, if the processing of the information is successfully1576passed and the request contained “ReadyToCharge = FALSE”. The allowed1577next request shall be ChargeParameterDiscoveryReq and1578WeldingDetectionReq and SessionStopReq and the1579V2G_SECC_Sequence_Timeout is set according to Table 103.1580

Deviation:1581

[V2G2-OC-601_1] The SECC shall respond with a PowerDeliveryRes containing1582“ResponseCode = OK” within V2G_SECC_Msg_Performance_Time1583according to Table 103_1, if the processing of the information is1584successfully passed and the request contained “ReadyToCharge = FALSE”.1585The allowed next request shall be SessionStopReq and the1586V2G_SECC_Sequence_Timeout is set according to Table 103_1.1587


[V2G2-591] The SECC shall respond with PowerDeliveryRes containing1589“ResponseCode = FAIL” within V2G_SECC_Msg_Performance_Time1590according to Table 103, if the processing of the information is not1591successfully.1592

Deviation:1593

[V2G2-OC-591_1] The SECC shall respond with PowerDeliveryRes containing1594“ResponseCode = FAIL” within V2G_SECC_Msg_Performance_Time1595according to Table 103_1, if the processing of the information is not1596successfully and then wait for SessionStopReq.1597


[V2G2-595] The SECC shall respond with CurrentDemandRes containing1599“ResponseCode = FAIL” within V2G_SECC_Msg_Performance_Time1600according to Table 103, if the processing of the information is not1601successfully.1602

1603

1604



Deviation:1605

[V2G2-OC-595_1] The SECC shall respond with a CurrentDemandRes containing1606“ResponseCode = FAIL” within V2G_SECC_Msg_Performance_Time1607according to Table 103_1, if the processing of the information is not1608successfully and then wait for SessionStopReq.1609

Restriction:1610

Requirements [V2G2_596] [V2G2_597] [V2G2_598] are not applicable for OppCharge.1611



Wait state forsupportedAppProtocol

Wait state forSessionSetup

Wait state forServiceDiscoveryor SessionStop

Wait state forServiceAndPaymentSelection

or SessionStop

Wait state forContractAuthentication

or SessionStop

Wait state forChargeParameterDiscovery

or SessionStop

Wait state forCableCheck orSessionStop

Wait state forPreCharge orSessionStop

Wait state forPreCharge or

PowerDelivery orSessoinStop

ProcessCurentDemand

Wait state for SessionStop

[V2G2-538]

[V2G2-536]

Initial EVSE side

[V2G2-540]

[V2G2-541]

[V2G2-542]

[V2G2-543]

[V2G2-544]

[V2G2-OC-545_1]

[V2G2-OC-585_1

[V2G2-OC-551_1]

[V2G2-550]

[V2G2-565]

[V2G2-562]

[V2G2-589]

[V2G2-586]

[V2G2-586][V2G2-OC-588_1]

Stop Communication Session

processsupportedAppProtocol

process SessionSetup

processServiceDiscover

y

processServiceAndPayment

Selection

processContractAuthentication

ProcessChargeParameter

Discovery

ProcessCableCheck

processPreCharge

processPowerDelivery

Wait state forCurrentDemand orPowerDelivery or

SessionStop

ProcessSessionStop

[V2G2-OC-546_1]

[V2G2-OC-552_1]

[V2G2-563]

[V2G2-OC-564_1]

[V2G2-582]

[V2G2-OC-566_1]

[V2G2-583]

[V2G2-OC-621_1]

[V2G2-OC-584_1]

[V2G2-587]

[V2G2-OC-591_1]

[V2G2-589]

[V2G2-590]

[V2G2-592]

[V2G2-593][V2G2-OC-595_1]

[V2G2-OC-601_1]

[V2G2-570]

[V2G2-572][V2G2-571]

[V2G2-OC-538_1]

[V2G2-537]

Stop ComForkSession

Stop Fork

[V2G2-OC-537_1][V2G2-OC-538_1]

[V2G2-OC-537_1][V2G2-OC-538_1]

[V2G2-OC-537_1][V2G2-OC-538_1]

[V2G2-OC-537_1][V2G2-OC-538_1]

[V2G2-OC-537_1][V2G2-OC-538_1]

[V2G2-OC-537_1][V2G2-OC-538_1]

[V2G2-OC-537_1][V2G2-OC-538_1]

[V2G2-OC-537_1][V2G2-OC-538_1]

[V2G2-537]

[V2G2-539]

[V2G2-539]

[V2G2-538][V2G2-537]

[V2G2-OC-572_1]

[V2G2-OC-621_2]

[V2G2-OC-723][V2G2-OC-724]

1612Figure OC_3 SECC Communication states for DC V2G messaging1613



8.9 Request-Response Message Sequence Examples1614

8.9.1 AC1615

This clause of ISO/IEC DIS 15118-2 does not apply. OppCharge does not use AC power1616transfer .1617

8.9.2 DC1618

8.9.2.1 EIM1619

This clause of ISO/IEC DIS 15118-2 is not applicable for OppCharge.1620

8.9.2.2 PnC1621

This clause of ISO/IEC DIS 15118-2 is not applicable for OppCharge.1622

8.9.2.3 OppChage1623

Figure OC_4 depicts an example for a Request-Response Message Sequence for the1624OppCharge without any errors.1625



EVCC

(from Actors)

SECC

(from Actors)

seq Communication Setup

EV controller includingIEC 61581-1 handling

EVSE controller includingIEC 61851-1 handling

StateB()

CableCheckReq()

CableCheckRes()

loop Cable Check

loop PreCharge

PreChargeReq()

PreChargeRes()

StateC()

seq Target Setting and Charge Scheduling

loop Charge Control

StateB()

loop ACD Disconnect

SessionStopRes()

seq EndofChargingProcess

ChargeParameterDiscoveryReq()

1626Figure OC_4 OppCharge V2G message sequence example1627



Annex A1628(informative)1629

1630Mapping of Part 1 use case elements1631

A.1 Relation of Identification Modes and Use Case Elements1632

Table A. 1 of ISO/IEC DIS 15118-2 is not applicable for OppCharge and has not been updated.1633



Annex B1634(informative)1635

1636Mapping of ISO 15118 message element names to1637

SAE J2847/2 terms1638




Annex C1640(normative)1641

1642Schema definition1643




Annex D1645(informative)1646

1647Message examples1648




Annex E1650(informative)1651

1652Application of certificates1653

This clause of ISO/IEC DIS 15118-2 does not apply to OppCharge Data Communication1654InterfaceV 1.2.0.1655

Certificates are not used.1656



Annex F1657(informative)1658

1659Security appliances and their associated certificates1660





Annex G1664(informative)1665

1666Simplified Certificate Management in Trusted Environment1667





Annex H1671(normative)1672

1673Certificate profiles1674





Annex I1678(normative)1679

1680Using Contract Certificates for XML encryption1681





Annex J1685(normative)1686

1687Use of OEM Provisioning Certificates1688





Annex K1692(informative)1693

1694Summary of requirements1695


Deviation:1697

Open Issue: Tabel will be available soon.1698



Bibliography1699


Documents

Road vehicles — Vehicle to grid communication interface ... · 147 7.10 Application layer 148 This clause of ISO/IEC DIS 15118-2 is applicable. V2G communication interface for OppCharge,