ISO 15118-1: the parts and the use cases
The general part of ISO 15118: what the series covers, which part defines which layer, the use cases a charging session can follow (EIM, Plug and Charge, scheduled charging, V2G) and the actors involved.
The parts of ISO 15118
| Part | Subject | Notes |
|---|---|---|
| ISO 15118-1 | General information and use case definition | Second edition absorbed the wireless use cases of part 6 |
| ISO 15118-2 | Network and application protocol requirements | First generation messages, 2014; see its own page |
| ISO 15118-3 | Physical and data link layer requirements | HomePlug Green PHY on the pilot and SLAC |
| ISO 15118-4 | Network and application protocol conformance test | Test cases for part 2 |
| ISO 15118-5 | Physical layer and data link layer conformance test | Test cases for part 3 |
| ISO 15118-6 | General information and use case definition for wireless communication | Withdrawn, merged into part 1 |
| ISO 15118-7 | Network and application protocol requirements for wireless communication | Withdrawn, superseded by part 20 |
| ISO 15118-8 | Physical layer and data link layer requirements for wireless communication | Wi-Fi for wireless power transfer and automated connection devices |
| ISO 15118-9 | Physical and data link layer conformance test for wireless communication | Test cases for part 8 |
| ISO 15118-10 | Physical layer and data link layer requirements for single pair Ethernet | 10BASE-T1S, used by the Megawatt Charging System |
| ISO 15118-20 | 2nd generation network layer and application layer requirements | 2022; conductive, wireless and pantograph charging, bidirectional power |
| ISO 15118-21 | Conformance test for part 20 | Published 2025; parts 22 and 23 follow |
Edition years and the status of parts 6, 7, 10 and 21 change over time. Check the ISO catalogue before quoting them in a report.
Actors
| Actor | Role |
|---|---|
| EV and EVCC | The car and its communication controller, the client of every V2G exchange |
| EVSE and SECC | The charger and its supply equipment communication controller, the server |
| CPO | Charge point operator, runs the charger and its backend (over OCPP) |
| eMSP (MO) | E-mobility service provider or mobility operator, holds the customer contract and its identifier (eMAID) |
| Clearing house | Matches CPOs and eMSPs so a contract of one can be used at the charger of another (roaming) |
| Certificate provisioning service and OEM | Create and install the contract certificate and the vehicle certificates for Plug and Charge |
| V2G root CA | Top of the Plug and Charge trust chain that charger and car both trust |
| DSO and secondary actors | Grid operator and others whose limits reach the car through the charger's schedules |
Only EVCC and SECC appear in a capture. Everything the other actors contribute (authorisation result, schedules, certificates) arrives through the charger's backend and is visible only as the content and timing of the charger's responses, for example an AuthorizationRes that stays Ongoing while the backend decides.
Use cases
| Use case | What happens | What a capture shows |
|---|---|---|
| External identification (EIM) | The driver identifies outside the protocol: RFID card, app, or free charging | PaymentOption ExternalPayment (or EIM in ISO 15118-20); AuthorizationRes Ongoing until the backend accepts |
| Plug and Charge (PnC) | The car proves the contract with a certificate; no card or app | TLS, PaymentOption Contract, PaymentDetailsReq with the contract chain, a signed AuthorizationReq |
| Certificate installation and update | The car obtains or renews its contract certificate through the charger | CertificateInstallationReq or CertificateUpdateReq (ISO 15118-2) |
| Scheduled charging | The charger passes a power schedule from the backend or grid; the car plans within it | SAScheduleList in ChargeParameterDiscoveryRes (ISO 15118-2) or schedules in ScheduleExchangeRes (ISO 15118-20) |
| Dynamic control | The charger steers power during the loop | ISO 15118-20 Dynamic control mode |
| Bidirectional power (V2G) | The car can discharge into the grid under control of the charger | AC_BPT or DC_BPT service in ISO 15118-20; negative current in the charge loop |
| Value added services | Extra services such as internet access or certificate handling offered by the charger | ServiceList in ServiceDiscoveryRes |
| Pause and resume | The session sleeps and wakes with the same SessionID | SessionStopReq Pause, later SessionSetupReq with the old SessionID (SQ-11) |
ISO 15118-1 describes these as use case elements that chain together: start of the process, communication setup, certificate handling, identification and authorisation, target setting and scheduling, charge control and rescheduling, value added services and end of charging. The message flows of part 2 and part 20 follow the same order.
Why a lab reads part 1
Part 1 has no messages and no timers, so no check of the tool cites it. It matters when a test plan is drawn up: it names the use cases a product claims to support, and every test case of parts 4, 5 and 21 traces back to one of them. When a customer says a charger "supports ISO 15118", ask which part, which use cases (EIM only, or Plug and Charge, or V2G) and which energy transfer modes.
Sources
- ISO 15118-1:2019, use case definitions and actors
- ISO 15118 series, titles of the parts