SDP and V2GTP: finding the charger and framing messages

How the car discovers the charger's address and port over UDP, and the eight byte header in front of every V2G message.

SECC discovery

  • After SLAC and IPv6 link local address setup, the car sends an SDP request to UDP port 15118 at the all nodes multicast address ff02::1 (V2G20-137, V2G20-139).
  • The request has a two byte payload: the requested security (0x00 TLS, 0x10 no TLS) and transport (0x00 TCP) (V2G20-141, Table 21).
  • The charger answers from port 15118 to the port the request came from with 20 bytes: its IPv6 address, TCP port, security and transport (V2G20-149, V2G20-151, V2G20-153).
  • The car waits at least 250 ms for an answer before it repeats, and gives up after 50 requests (V2G20-159, V2G20-161).
  • It then connects to the address and port of the last answer (V2G20-081).

SD-01 to SD-06 check the answer, the retries, the connection target, the TLS choice, the message format and the retry pacing.

The TCP connection

  • The car opens the connection to the address and port from SDP; the charger has to answer the SYN (TC-01).
  • Neither side resets or closes the connection before SessionStopRes (TC-02). A reset that follows a close is how many stacks end a connection and does not count.
  • Retransmissions point at a poor powerline link; more than a few per connection are reported (TC-03).

V2GTP header

BytesField
1Protocol version, 0x01
2Inverse protocol version, 0xFE
3 to 4Payload type, big endian
5 to 8Payload length, big endian

A receiver checks version and inverse first, then the payload type, then the length, and ignores a message with wrong values (V2G20-090 to V2G20-800). VT-01 reports malformed headers.

Sources

  • ISO 15118-2:2014, SDP and V2GTP
  • ISO 15118-20:2022, V2G20-137 to V2G20-161 and Table 14