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

ProtocolNamespaceMajor version
DIN SPEC 70121urn:din:70121:2012:MsgDef2
ISO 15118-2urn:iso:15118:2:2013:MsgDef2
ISO 15118-20 ACurn:iso:std:iso:15118:-20:AC1
ISO 15118-20 DCurn:iso:std:iso:15118:-20:DC1
ISO 15118-20 ACDPurn:iso:std:iso:15118:-20:ACDP1
ISO 15118-20 WPTurn:iso:std:iso:15118:-20:WPT1

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