The app protocol handshake
The two messages that pick DIN SPEC 70121, ISO 15118-2 or ISO 15118-20 for the session, shared by every generation.
How it works
- The car sends supportedAppProtocolReq with 1 to 20 entries: namespace, major and minor version, a SchemaID it assigns, and a priority where 1 is the most preferred (V2G20-167).
- The charger answers with a response code and the SchemaID of the protocol it picked: the highest priority entry it supports (V2G20-169).
- A different minor version still counts as a match (OK_SuccessfulNegotiationWithMinorDeviation); no match gives Failed_NoNegotiation, after which the car must not start a session (V2G20-172, V2G20-173).
- After Failed_NoNegotiation a charger that supports basic charging falls back to it (V2G20-1837).
Namespaces
| Protocol | Namespace | Major version |
|---|---|---|
| DIN SPEC 70121 | urn:din:70121:2012:MsgDef | 2 |
| ISO 15118-2 | urn:iso:15118:2:2013:MsgDef | 2 |
| ISO 15118-20 AC | urn:iso:std:iso:15118:-20:AC | 1 |
| ISO 15118-20 DC | urn:iso:std:iso:15118:-20:DC | 1 |
| ISO 15118-20 ACDP | urn:iso:std:iso:15118:-20:ACDP | 1 |
| ISO 15118-20 WPT | urn:iso:std:iso:15118:-20:WPT | 1 |
The CommonMessages and CommonTypes namespaces of ISO 15118-20 never appear in the list (V2G20-2133). HS-01 checks the list, HS-02 the choice, HS-03 that a protocol which needs TLS is not negotiated without it.
Sources
- ISO 15118-2:2014, supportedAppProtocol
- ISO 15118-20:2022, V2G20-2133