ISO 15118-20: the second generation

The 2022 application layer for conductive, wireless and pantograph charging: services instead of a fixed flow, bidirectional power, two control modes and mandatory TLS 1.3.

What changed from ISO 15118-2

  • Energy transfer is a service the car selects (AC, DC, the bidirectional AC_BPT and DC_BPT, WPT, ACDP), each with parameter sets listed in ServiceDetailRes.
  • Messages are split over five XML schemas: CommonMessages, AC, DC, ACDP and WPT. Each has its own V2GTP payload type.
  • Every message carries its own Header with SessionID and a TimeStamp; there is no V2G_Message wrapper any more.
  • Two control modes: Scheduled (the charger offers schedules with target power, the car commits to a power profile) and Dynamic (the charger steers power during the loop, taking the car's mobility needs into account).
  • TLS 1.3 with mutual authentication is mandatory. The car has its own vehicle certificate; TLS 1.2 and plain TCP only carry ISO 15118-2 or DIN SPEC 70121 (Table 5).
  • Schedule renegotiation can run next to the charge loop on a side stream, so energy transfer does not have to stop.

DC session, message by message

  1. EV: supportedAppProtocolReq, still on payload type 0x8001, for backward compatibility
  2. EV: SessionSetupReq, SessionID all zero, EVCCID
  3. EV: AuthorizationSetupReq, which authorization services the charger offers
  4. EV: AuthorizationReq, EIM, or PnC with the contract certificate chain; may repeat while Ongoing
  5. EV: ServiceDiscoveryReq, energy transfer services and value added services
  6. EV: ServiceDetailReq, optional, once per service: its parameter sets
  7. EV: ServiceSelectionReq, one energy service with a ParameterSetID, optional VAS
  8. EV: DC_ChargeParameterDiscoveryReq
  9. EV: ScheduleExchangeReq, schedules (Scheduled) or departure time and target SOC (Dynamic)
  10. EV: DC_CableCheckReq, insulation check, repeats while Ongoing
  11. EV: DC_PreChargeReq, charger matches the battery voltage
  12. EV: PowerDeliveryReq, ChargeProgress Start, with the EVPowerProfile in Scheduled mode
  13. EV: DC_ChargeLoopReq, repeats for the whole energy transfer
  14. EV: PowerDeliveryReq, ChargeProgress Stop
  15. EV: DC_WeldingDetectionReq
  16. EV: SessionStopReq, ChargingSession Terminate or Pause

Every request is answered by the charger with the matching response. The tool checks the order (SQ-01), that each request is answered (SQ-02), the response codes (SQ-05) and that the Header TimeStamp never runs backwards (IS20-07).

AC session

The AC flow is the same up to the service selection. It then runs AC_ChargeParameterDiscovery and ScheduleExchange, PowerDelivery Start, the AC_ChargeLoop, PowerDelivery Stop and SessionStop. There is no cable check, precharge or welding detection.

Pause, resume and renegotiation

  • Pause: the car sends SessionStopReq with ChargingSession Pause. After an OK response both sides pause the data link and follow the sleep and wake up rules of ISO 15118-3 (V2G20-1227, V2G20-1777). On resume the car reuses the SessionID.
  • The charger can ask for a pause through GoToPause in ScheduleExchangeRes; IS20-06 checks that the session then really ends as a pause.
  • Start with pause: a car can start a session, exchange schedules and pause before any energy flows, then resume later with cable check and precharge.
  • Schedule renegotiation: the car sends PowerDeliveryReq with ChargeProgress ScheduleRenegotiation, runs a new ScheduleExchange and a PowerDelivery Start with the new profile. The charger can ask for it with EVSENotification ScheduleRenegotiation. IS20-09 checks that it runs to its end.
  • After SessionStop with Terminate the charger ends the data link two seconds after its response (V2G20-1776).

Field reports say schedule renegotiation is not yet supported by many chargers. A refused renegotiation is flagged, not treated as a session failure.

Streams and payload types

Payload typeCarries
0x8001ISO 15118-2 and DIN messages, and the app handshake of every generation
0x8002ISO 15118-20 CommonMessages (main stream)
0x8003ISO 15118-20 AC (main stream)
0x8004ISO 15118-20 DC (main stream)
0x8005ISO 15118-20 ACDP (main stream)
0x8006ISO 15118-20 WPT (main stream)
0x8101Side stream: schedule renegotiation
0x8102Side stream: metering confirmation
0x8103Side stream: ACDP system status
0x8104Side stream: parking status

Values from ISO 15118-20 Table 14. Each V2GTP message carries exactly one V2G message (V2G20-1229).

Service identifiers

ServiceIDService
1AC
2DC
3WPT
4DC_ACDP
5AC_BPT
6DC_BPT
7DC_ACDP_BPT

The service identifiers were taken from implementations and the tool's own test vectors, not from the standard text. Verify them against clause 8 before relying on them.

One service can come with several parameter sets (the decoder in this tool reads up to 4 sets of 8 parameters each; a longer list does not decode). Most of their content is fixed by the installation; what the car really chooses is the control mode, who provides the mobility needs (car or charger) and, for AC, the connector. A charger should offer every sensible combination.

What the tool checks

CheckMeaning
IS20-01The messages match the selected energy service
IS20-02The control mode stays the same
IS20-03, IS20-04The charger stays inside its limits and the car's target
IS20-05Power flows back only in a BPT session
IS20-06A requested pause ends as a pause
IS20-07Every message has a header with a clock that does not run backwards
IS20-08The selected service, VAS and parameter set were offered
IS20-09A schedule renegotiation completes
IS20-10An asymmetric AC request is answered per phase
HS-03ISO 15118-20 is only offered and selected over TLS 1.3
TL-05, TL-06The TLS 1.3 handshake follows clause 7.7.3

The timing tables of clause 8.6 are not yet checked against the standard text. The timing checks use the profile values, which are marked for verification.

Sources

  • ISO 15118-20:2022, requirement numbers as cited in the text