Contents
StandardISO

ISO 15118-20

Road vehicles — Vehicle to grid communication interface — Part 20: 2nd generation network layer and application layer requirements

ISO 15118-20 defines how an electric vehicle and charging equipment communicate to authorize charging, coordinate power transfer, and support bidirectional energy flow.

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.

What it means for your discipline

  • HPC & application softwareCore

    Implement the charging protocol, message encoding, session state machines, timing, and error handling. Coordinate protocol behavior with the vehicle’s charging and energy management software.

  • CybersecurityCore

    Own certificate handling, trust configuration, secure communication, and private-key protection. Translate Plug & Charge security requirements into provisioning and operational processes.

  • Networks & communicationCore

    Implement and troubleshoot charger discovery and the IP communication path between vehicle and charging equipment. Validate connection establishment and transport behavior under realistic link conditions.

  • E/E architecturePartial

    Allocate responsibilities between the charging controller, energy management functions, security services, and external infrastructure. Define which charging services and protocol generations the vehicle supports.

  • Hardware & siliconPartial

    Provide communication interfaces and key-protection capabilities that support the selected implementation. Coordinate controller resources and physical interfaces with software and network requirements.

  • Functional safetyPartial

    Understand how communication requests and failures interact with charging safety controls. Ensure the system responds safely to missing, inconsistent, or interrupted communication.

  • Diagnostics & lifecyclePartial

    Make charging failures diagnosable through session events, protocol errors, and certificate-validation results. Design useful service information without exposing credentials or sensitive customer data.

No direct stake: Base software · Software update & OTA