What it is
ISO 15118-20 specifies the second generation of higher-layer communication between an electric vehicle and charging equipment. The communicating endpoints are the electric vehicle communication controller (EVCC) and the supply equipment communication controller (SECC).
It provides a shared language for discovering services, establishing a session, authorizing access, and coordinating energy transfer. Its scope includes bidirectional power transfer, where a suitably equipped vehicle can also supply energy. Support in the protocol does not establish that a particular vehicle or charger implements every service.
Who it applies to
The standard primarily serves vehicle manufacturers, charging equipment manufacturers, charging communication software suppliers, and their integration teams. It concerns both battery electric vehicles and plug-in hybrids.
Security infrastructure providers also have a stake because certificate-based charging depends on trust and credential management beyond the communication controller itself. Test teams need the selected edition and supported service set to define meaningful acceptance criteria.
For a project, applicability follows the product specification, contractual commitments, and any relevant external requirements. Publication as an ISO standard alone does not make every feature mandatory for every vehicle.
What it covers
The document combines communication infrastructure with charging-specific application behavior.
| Topic | Engineering meaning |
|---|---|
| Network and transport | Establish communication between vehicle and charger using IP-based mechanisms. |
| Application messages | Exchange service choices, charging parameters, and power-transfer control information. |
| Session behavior | Follow defined sequencing, timing, and error-handling rules. |
| Security | Apply secure transport, certificate profiles, key management, and message protection requirements. |
The scope also includes communication for conductive and wireless charging, automatic connection devices, and charging status information. The published contents identify XML-based message definitions and Efficient XML Interchange (EXI) encoding. Published contents preview
How it fits with other documents
Read Part 20 within the wider ISO 15118 family. ISO 15118-2 describes the earlier generation of network and application communication; a project supporting both generations needs explicit protocol selection and separate implementation coverage.
Charging communication must also align with the electrical charging system. The standard addresses synchronization with IEC 61851 signalling for conductive charging and IEC 61980 signalling for wireless power transfer.
For the wiki’s certificates and PKI topic, Part 20 connects trust infrastructure to charging behavior. Plug & Charge needs working certificate provisioning, trust anchors, and protected private keys alongside the protocol implementation. The vehicle-to-charger interface should therefore have clear ownership across software, security, and infrastructure teams.
In practice
Begin by recording the edition, amendments, charging methods, authorization methods, and services required by the product. Turn these choices into an implementation and interoperability matrix shared with suppliers.
A useful integration scenario is a vehicle that connects successfully but cannot authorize charging. Engineers should distinguish discovery and transport failures from certificate validation, authorization, and application-sequence failures. That separation makes logs and fault reports actionable.
Recommended validation includes interrupted sessions, unavailable services, certificate failures, and recovery after communication loss. Exercise these scenarios with representative charging equipment and the vehicle’s energy management functions. For bidirectional operation, verify that communication decisions remain consistent with the power electronics’ capabilities and operating limits.