prEN ISO 15118-2

Road vehicles - Vehicle to grid communication interface - Part 2: Network and application protocol requirements (ISO/DIS 15118-2:2018)

ISO 15118-2:2014 specifies the communication between battery electric vehicles (BEV) or plug-in hybrid electric vehicles (PHEV) and the Electric Vehicle Supply Equipment. The application layer message set defined in ISO 15118-2:2014 is designed to support the energy transfer from an EVSE to an EV. ISO 15118-1 contains additional use case elements describing the bidirectional energy transfer. The implementation of these use cases requires enhancements of the application layer message set defined herein.
The purpose of ISO 15118-2:2014 is to detail the communication between an EV (BEV or a PHEV) and an EVSE. Aspects are specified to detect a vehicle in a communication network and enable an Internet Protocol (IP) based communication between EVCC and SECC.
ISO 15118-2:2014 defines messages, data model, XML/EXI based data representation format, usage of V2GTP, TLS, TCP and IPv6. In addition, it describes how data link layer services can be accessed from a layer 3 perspective. The Data Link Layer and Physical Layer functionality is described in ISO 15118-3.

Straßenfahrzeuge - Kommunikationsschnittstelle zwischen Fahrzeug und Ladestation - Teil 2: Anforderungen an das Netzwerk- und Anwendungsprotokoll (ISO/DIS 15118-2:2018)

Véhicules routiers - Interface de communication entre véhicule et réseau électrique - Partie 2 : Exigences du protocole d'application et du réseau (ISO/DIS 15118-2:2018)

Le présent document spécifie la communication entre les véhicules électriques à batterie (VEB) ou les véhicules électriques hybrides rechargeables (VEHR) et l'infrastructure de recharge pour véhicules électriques. L'ensemble de messages de la couche application défini dans le présent document est conçu pour prendre en charge le transfert d'énergie entre une IRVE et un VE. L'ISO 15118-1 contient des éléments de cas d'utilisation supplémentaires (ID des éléments de cas d'utilisation de la Partie 1 : F4 et F5) décrivant le transfert d'énergie bidirectionnel. L'implémentation de ces cas d'utilisation nécessite des améliorations de l'ensemble de messages de la couche application défini dans le présent document. Les définitions de ces exigences supplémentaires feront l'objet de la prochaine révision du présent document.
Le présent document a pour but de décrire de manière détaillée la communication entre un VE (VEB ou VEHR) et une IRVE. Les aspects spécifiés permettent de détecter un véhicule dans un réseau de communication, et de permettre une communication basée sur le protocole Internet (IP) entre le contrôleur de communication du véhicule électrique (EVCC) et le contrôleur de communication de l'infrastructure de recharge (SECC).
Le présent document définit les messages, le modèle de données, le format de représentation de données basé sur XML/EXI, l'utilisation de V2GTP, TLS, TCP et IPv6. De plus, il décrit comment accéder aux services de la couche liaison de données à partir de la couche 3. La fonctionnalité de la couche liaison de données et de la couche physique est décrite dans l'ISO 15118-3.

Cestna vozila - Komunikacijski vmesnik med vozilom in omrežjem - 2. del: Zahteve za protokol omrežja in uporabe (ISO/DIS 15118-2:2022)

General Information

• Status: Not Published
• Publication Date: 06-Apr-2020
• ICS: 43.040.15 - Car informatics. On board computer systems
• ICS: 43.120 - Electric road vehicles
• Technical Committee: CEN/TC 301 - Electrically propelled road vehicles
• Drafting Committee: CEN/TC 301 - Electrically propelled road vehicles
• Current Stage: 4098 - Decision to abandon - Enquiry
• Start Date: 31-Jan-2019
• Completion Date: 14-Apr-2025
• Ref Project: oSIST prEN ISO 15118-2:2022 - Road vehicles - Vehicle-to-grid communication interface - Part 2: Network and application protocol requirements (ISO/DIS 15118-2:2022)

Relations

• Revises: EN ISO 15118-2:2016 - Road vehicles - Vehicle-to-grid communication Interface - Part 2: Network and application protocol requirements (ISO 15118-2:2014)
• Effective Date: 08-Jun-2022

Overview

prEN ISO 15118-2, titled Road Vehicles - Vehicle to Grid Communication Interface - Part 2: Network and Application Protocol Requirements, is a vital standard developed by CEN that specifies the communication protocols between electric vehicles (EVs) and electric vehicle supply equipment (EVSE). Focused on battery electric vehicles (BEVs) and plug-in hybrid electric vehicles (PHEVs), this standard enables seamless information exchange to support efficient energy transfer during charging processes.

The scope of ISO 15118-2 includes defining message sets, data models, and network protocols such as TCP/IP and TLS required for secure, internet protocol (IP)-based communication between an electric vehicle communication controller (EVCC) and supply equipment communication controller (SECC). It leverages XML and Efficient XML Interchange (EXI) formats for data representation and builds upon the OSI layered network architecture to provide reliable vehicle-to-grid (V2G) communication interfaces.

Key Topics

• Network and Application Protocols
  Details the TCP, UDP, IPv6, and TLS transport and network layer technologies that enable robust EV-to-EVSE communication.

• Message Set Definitions
  Defines the application layer messages and data structures to govern charging control, session management, and handshake mechanisms.

• Security Framework
  Specifies certificate management, TLS encryption, and authentication schemes for secure communication and data integrity.

• Communication States
  Outlines the different states and transitions during the V2G charging session, including discovery, handshake, and charging sessions.

• Data Representation
  Uses XML schemas and EXI for structured, efficient data exchange, enhancing interoperability between various manufacturers' systems.

• Protocol Enhancements
  Supports bidirectional energy transfer use cases and extensibility for future V2G functionalities.

Applications

prEN ISO 15118-2 is critical for various stakeholders in the electric mobility ecosystem to ensure standardized communication and interoperability:

• Electric Vehicle Manufacturers
  Integrate communication protocols for smart charging capabilities and secure energy flow control between vehicle and grid.

• Charging Station Providers
  Implement compliance with network and application layer requirements to support diverse EV models and efficient charging sessions.

• Energy Service Providers
  Enable smart grid integration by leveraging bidirectional energy transfer and dynamic load management facilitated by this protocol.

• Software Developers
  Develop EV communication modules that adhere to XML and EXI message formats and handle secure TLS-based data exchanges.

• Regulatory Bodies and Standardization Committees
  Utilize these standards to establish regulatory frameworks for interoperable EV charging infrastructure development.

Related Standards

prEN ISO 15118-2 complements and references several other international standards vital for EV communication:

• ISO 15118-1
  Provides use case definitions and general overview of the vehicle-to-grid communication interface.

• ISO 15118-3
  Details the physical and data link layer requirements underlying the network protocols tackled in Part 2.

• IEC 61851-1
  Defines basic DC and AC charging system requirements, synchronized with V2G communication sessions from ISO 15118-2.

• RFCs Relevant to Networking
  Protocol specifications for TCP, UDP, TLS, and IPv6 that form the backbone of V2G communication networks.

This standard supports the development of smart, interoperable, and secure charging solutions critical for the future of electric mobility and energy management.

---

Keywords: ISO 15118-2, vehicle-to-grid communication, electric vehicle communication protocol, EVSE communication, V2G communication, electric vehicle charging, network protocol, application protocol, EV charging security, TCP/IP EV communication, TLS EVSE, XML EXI data format, electric mobility standards.

Standards Content (Sample)

SLOVENSKI STANDARD
01-december-2022
Cestna vozila - Komunikacijski vmesnik med vozilom in omrežjem - 2. del: Zahteve
za protokol omrežja in uporabe (ISO/DIS 15118-2:2022)
Road vehicles - Vehicle-to-grid communication interface - Part 2: Network and
application protocol requirements (ISO/DIS 15118-2:2022)
Straßenfahrzeuge - Kommunikationsschnittstelle zwischen Fahrzeug und Ladestation -
Teil 2: Anforderungen an das Netzwerk- und Anwendungsprotokoll (ISO/DIS 15118-
2:2022)
Véhicules routiers - Interface de communication entre véhicule et réseau électrique -
Partie 2: Exigences du protocole d'application et du réseau (ISO/DIS 15118-2:2022)
Ta slovenski standard je istoveten z: prEN ISO 15118-2
ICS:
35.100.05 Večslojne uporabniške Multilayer applications
rešitve
43.040.15 Avtomobilska informatika. Car informatics. On board
Vgrajeni računalniški sistemi computer systems
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

DRAFT INTERNATIONAL STANDARD
ISO/DIS 15118-2
ISO/TC 22/SC 31 Secretariat: DIN
Voting begins on: Voting terminates on:
2022-10-10 2023-01-02
Road vehicles — Vehicle-to-grid communication
interface —
Part 2:
Network and application protocol requirements
Véhicules routiers — Interface de communication entre véhicule et réseau électrique —
Partie 2: Exigences du protocole d'application et du réseau
ICS: 43.120
This document is circulated as received from the committee secretariat.
This draft is submitted to a parallel vote in ISO and in IEC.
THIS DOCUMENT IS A DRAFT CIRCULATED
FOR COMMENT AND APPROVAL. IT IS
ISO/CEN PARALLEL PROCESSING
THEREFORE SUBJECT TO CHANGE AND MAY
NOT BE REFERRED TO AS AN INTERNATIONAL
STANDARD UNTIL PUBLISHED AS SUCH.
IN ADDITION TO THEIR EVALUATION AS
BEING ACCEPTABLE FOR INDUSTRIAL,
TECHNOLOGICAL, COMMERCIAL AND
USER PURPOSES, DRAFT INTERNATIONAL
STANDARDS MAY ON OCCASION HAVE TO
BE CONSIDERED IN THE LIGHT OF THEIR
POTENTIAL TO BECOME STANDARDS TO
WHICH REFERENCE MAY BE MADE IN
Reference number
NATIONAL REGULATIONS.
ISO/DIS 15118-2:2022(E)
RECIPIENTS OF THIS DRAFT ARE INVITED
TO SUBMIT, WITH THEIR COMMENTS,
NOTIFICATION OF ANY RELEVANT PATENT
RIGHTS OF WHICH THEY ARE AWARE AND TO
PROVIDE SUPPORTING DOCUMENTATION. © ISO 2022

ISO/DIS 15118-2:2022(E)
DRAFT INTERNATIONAL STANDARD
ISO/DIS 15118-2
ISO/TC 22/SC 31 Secretariat: DIN
Voting begins on: Voting terminates on:

Road vehicles — Vehicle-to-grid communication
interface —
Part 2:
Network and application protocol requirements
Véhicules routiers — Interface de communication entre véhicule et réseau électrique —
Partie 2: Exigences du protocole d'application et du réseau
ICS: 43.120
This document is circulated as received from the committee secretariat.
This draft is submitted to a parallel vote in ISO and in IEC.
THIS DOCUMENT IS A DRAFT CIRCULATED
FOR COMMENT AND APPROVAL. IT IS
© ISO 2022
ISO/CEN PARALLEL PROCESSING
THEREFORE SUBJECT TO CHANGE AND MAY
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
NOT BE REFERRED TO AS AN INTERNATIONAL
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on STANDARD UNTIL PUBLISHED AS SUCH.
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
IN ADDITION TO THEIR EVALUATION AS
or ISO’s member body in the country of the requester. BEING ACCEPTABLE FOR INDUSTRIAL,
TECHNOLOGICAL, COMMERCIAL AND
ISO copyright office
USER PURPOSES, DRAFT INTERNATIONAL
CP 401 • Ch. de Blandonnet 8
STANDARDS MAY ON OCCASION HAVE TO
BE CONSIDERED IN THE LIGHT OF THEIR
CH-1214 Vernier, Geneva
POTENTIAL TO BECOME STANDARDS TO
Phone: [phone]
WHICH REFERENCE MAY BE MADE IN
Reference number
Email: [e-mail]
NATIONAL REGULATIONS.
Website: www.iso.org ISO/DIS 15118-2:2022(E)
RECIPIENTS OF THIS DRAFT ARE INVITED
Published in Switzerland
TO SUBMIT, WITH THEIR COMMENTS,
NOTIFICATION OF ANY RELEVANT PATENT
RIGHTS OF WHICH THEY ARE AWARE AND TO
ii
PROVIDE SUPPORTING DOCUMENTATION. © ISO 2022

ISO/DIS 15118-2:2022(E)
Contents
Foreword . vii
Introduction . viii
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 3
4 Symbols and abbreviated terms . 6
5 Conventions . 7
5.1 Definition of OSI based services . 7
5.2 Requirement structure . 8
5.3 Usage of RFC references. 8
5.4 Notation used for XML schema diagrams . 8
6 Document overview . 8
7 Basic requirements for V2G communication . 9
7.1 General information . 9
7.2 Service primitive concept of OSI layered architecture . 10
7.2.1 Overview . 10
7.2.2 Syntax of service primitives . 10
7.3 Security concept . 11
7.3.1 Call flows (flow charts) . 11
7.3.2 Certificate and key management . 15
7.3.3 Number of root certificates and root validity, certificate depth and size . 17
7.3.4 Support and application of TLS . 18
7.4 V2G communication states and data link handling . 20
7.5 Data link layer . 25
7.6 Network layer . 25
7.6.1 General . 25
7.6.2 Applicable RFCs and limitations and protocol parameter settings . 25
7.6.3 IP addressing . 26
7.7 Transport layer . 27
7.7.1 Transmission control protocol (TCP) . 27
7.7.2 User datagram protocol (UDP) . 28
7.7.3 Transport layer security (TLS) . 28
7.8 V2G transfer protocol . 31
7.8.1 General . 31
7.8.2 Supported ports . 31
7.8.3 Protocol data unit . 33
7.9 Presentation layer . 36
7.9.1 XML and efficient XML interchange (EXI) . 36
7.9.2 Message security . 39
7.10 Application layer . 46
7.10.1 SECC discovery protocol . 46
7.10.2 Vehicle to grid application layer messages . 51
7.10.3 Application layer service primitives . 51
8 Application layer messages . 55
8.1 General . 55
8.2 Protocol handshake definition . 56
8.2.1 Handshake sequence . 56
ISO/DIS 15118-2:2022(E)
8.2.2 Message definition supportedAppProtocolReq and supportedAppProtocolRes .57
8.2.3 Semantics description supportedAppProtocol messages .57
8.2.4 Message examples .58
8.3 V2G message definition .60
8.3.1 General .60
8.3.2 Message definition .60
8.3.3 Message header definition .61
8.3.4 Message body definition .62
8.4 V2G communication session and BodyElement definitions .63
8.4.1 General .63
8.4.2 Session handling .63
8.4.3 Common messages .66
8.4.4 AC messages .96
8.4.5 DC messages .98
8.5 Complex data types . 107
8.5.1 Overview . 107
8.5.2 Common . 107
8.5.3 AC . 132
8.5.4 DC . 136
8.6 Identification modes and message set definitions . 142
8.6.1 Overview . 142
8.6.2 Supported message sets . 145
8.6.3 Selection of message sets . 172
8.7 V2G communication timing . 177
8.7.1 Overview . 177
8.7.2 Message sequence and communication session . 178
8.7.3 Session setup and ready to charge . 183
8.7.4 V2G message synchronization with IEC 61851-1 signalling . 186
8.8 Message sequencing and error handling . 191
8.8.1 Overview . 191
8.8.2 Basic Definitions for Error Handling . 192
8.8.3 ResponseCode handling . 192
8.8.4 Request-response message sequence requirements . 196
8.9 Request-response message sequence examples . 215
8.9.1 AC . 215
8.9.2 DC . 218
Annex A (normative) Schema definition . 223
A.1 Overview . 223
A.2 V2G_CI_AppProtocol.xsd . 224
A.3 V2G_CI_MsgDef.xsd . 224
A.4 V2G_CI_MsgHeader.xsd . 225
A.5 V2G_CI_MsgBody.xsd . 225
A.6 V2G_CI_MsgDataTypes.xsd . 232
A.7 xmldsig-core-schema.xsd . 242
Annex B (normative) Certificate profiles . 247
B.1 Overview . 247
Annex C (normative) Specification of identifiers . 253
C.1 e-Mobility account identifier (EMAID) . 253
iv © ISO 2022 – All rights reserved

ISO/DIS 15118-2:2022(E)
C.1.1 EMAID syntax . 253
C.1.2 EMAID Semantics . 253
C.1.3 Calculation of the check digit . 254
C.2 Electric vehicle supply equipment ID (EVSEID) . 254
C.2.1 EVSEID syntax . 254
C.2.2 EVSEID semantics . 254
Annex D (informative) Mapping of ISO 15118-1 use case elements . 256
D.1 Relation of identification modes and use case elements . 256
Annex E (informative) Mapping of ISO 15118 message element names to SAE J2847/2
terms . 309
E.1 SAE J2847/2 status codes . 309
E.2 SAE J2847/2 energy transfer types . 310
E.3 SAE J2847/2 signals . 311
Annex F (informative) Message examples . 313
F.1 Value added service selection . 313
F.2 EXI encoded message examples. 315
F.2.1 SessionSetupRes message . 315
F.2.2 ChargeParameterDiscoveryReq message (AC-based). 315
F.2.3 CurrentDemandReq message . 316
F.3 Schedules and tariff information . 317
F.3.1 Overview . 317
F.3.2 Dynamic GridSchedule w/o SalesTariff over ISO 15118 V2G CI . 317
F.3.3 “Time Of Use”-based SalesTariff with constant value for GridSchedule . 319
F.3.4 “Time Of Use”-based SalesTariff with dynamic GridSchedule . 320
F.3.5 “Consumption”-based SalesTariff with constant value for GridSchedule . 322
F.3.6 Multiple SalesTariffs with different demand Limits in GridSchedule . 323
F.3.7 Time of Use-based SalesTariffs including relativePricePercentage . 325
Annex G (informative) Application of certificates . 333
G.1 General information . 333
G.1.1 Overview . 333
G.1.2 Demands of the OEM . 334
G.1.3 Demands of the secondary actors . 334
G.1.4 Rationale for decisions in this document . 335
G.1.5 Overview of the resulting certificate structure . 337
G.2 Simplified certificate management in private environment . 338
G.2.1 Overview (motivation) . 338
G.2.2 Solution for private environments . 338
ISO/DIS 15118-2:2022(E)
G.2.2.1 General . 338
G.2.2.2 Installation of a private root certificate into a vehicle . 339
G.2.2.3 Charging in a private environment . 339
G.2.2.4 Compromised certificate of a wall box . 339
G.3 Use of OEM provisioning certificates . 340
G.3.1 Introduction . 340
G.3.2 Processes . 341
G.3.2.1 Vehicle production . 341
G.3.2.2 Vehicle Hand-Over . 341
G.3.2.3 Contract Conclusion . 342
G.3.2.4 Certificate installation . 342
G.3.2.5 Certificate update . 342
G.3.2.6 Component replacement . 342
G.4 Security appliances and their associated certificates . 343
Annex H (informative) Encryption for the distribution of secret keys . 346
H.1 Overview . 346
H.2 Ephemeral-static Diffie-Hellman key agreement . 346
H.3 Key pairs . 347
Annex I (informative) Message sequencing for renegotiation. 348
I.1 Overview . 348
I.2 Renegotiation after resuming a V2G communication session . 351
Annex J (informative) Overview on XML signatures . 352
J.1 Overview . 352
J.2 Signature generation . 352
J.3 Signature generation for secondary actors. 355
J.4 Signature validation . 355
Annex K (informative) Summary of requirements . 356
Bibliography . 362

vi © ISO 2022 – All rights reserved

ISO/DIS 15118-2:2022(E)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out
through ISO technical committees. Each member body interested in a subject for which a technical
committee has been established has the right to be represented on that committee. International
organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. ISO
collaborates closely with the International Electrotechnical Commission (IEC) on all matters of
electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the
different types of ISO documents should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of any
patent rights identified during the development of the document will be in the Introduction and/or on
the ISO list of patent declarations received (see www.iso.org/patents).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to the World
Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT), see
www.iso.org/iso/foreword.html.
This document was prepared by Technical Committee ISO/TC 22, Road vehicles, Subcommittee SC 31,
Data communication.
This second edition cancels and replaces the first edition (ISO 15118-2:2014), which has been technically
revised.
The main changes compared to the previous edition are as follows:
— General corrections identified and resolved by the “ISO 15118-2 User Group” (most, if not all, of
these corrections are already included in existing implementations in the field, since the underlying
issues were identified during the various Testing Symposium events);
— Clarifications, to make the intended functionality more clear:
— How to properly use the ChargingProfile;
— Interaction between ISO 15118-2 and IEC 61851;
— How to use multiple Contract Certificates.
— Other improvements:
— Remove definition of certificate lifetimes, should be defined by PKI;
— Align TCP behaviour (timeouts, retries, …) with ISO 15118-20.
A list of all parts in the ISO 15118 series can be found on the ISO website.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.
ISO/DIS 15118-2:2022(E)
Introduction
The pending energy crisis and necessity to reduce greenhouse gas emissions has led the vehicle
manufacturers to a very significant effort to reduce the energy consumption of their vehicles. They are
presently developing vehicles partly or completely propelled by electric energy. Those vehicles will
reduce the dependency on oil, improve the global energy efficiency and reduce the total CO emissions
for road transportation if the electricity is produced from renewable sources. To charge the batteries of
such vehicles, specific charging infra-structure is required.
Much of the standardization work on dimensional and electrical specifications of the charging
infrastructure and the vehicle interface is already treated in the relevant ISO or IEC groups. However, the
question of information transfer between the EV and the EVSE has not been treated sufficiently.
Such communication is necessary for the optimization of energy resources and energy production
systems so that vehicles can recharge in the most economical or most energy efficient way. It is also
required to develop efficient and convenient billing systems to cover the resulting micro-payments. The
necessary communication channel may serve in the future to contribute to the stabilization of the
electrical grid as well as to support additional information services required to operate electric vehicles
efficiently and economically.
viii © ISO 2022 – All rights reserved

ISO/DIS 15118-2:2022(E)
Road vehicles — Vehicle-to-grid communication interface —
Part 2: Network and application protocol requirements
1 Scope
This document specifies the communication between battery electric vehicles (BEV) or plug-in hybrid
electric vehicles (PHEV) and the Electric Vehicle Supply Equipment. The application layer message set
defined in this document is designed to support the energy transfer from an EVSE to an EV. ISO 15118-1
contains additional use case elements (Use Case Element IDs: F4 and F5) describing the bidirectional
energy transfer. The implementation of these use cases requires enhancements of the application layer
message set defined herein.
The purpose of this document is to detail the communication between an EV (BEV or a PHEV) and an
EVSE. Aspects are specified to detect a vehicle in a communication network and enable an Internet
Protocol (IP) based communication between EVCC and SECC.
1 2
Electric Vehicle Supply Equipment
Communication Controller Communication Controller Secondary Actor (SA)
(EVCC) (SECC)
Key
1 In scope of this document
2 Message definition considers use cases defined for communication between SECC to SA
Figure 1 — Communication relationship among EVCC, SECC and secondary actor
This document defines messages, data model, XML/EXI based data representation format, usage of
V2GTP, TLS, TCP and IPv6. In addition, it describes how data link layer services can be accessed from an
OSI-layer 3 perspective.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
ISO 3166-1, Codes for the representation of names of countries and their subdivisions ― Part 1: Country
codes
IEC 61851-1, Electric vehicle conductive charging system ― Part 1: General requirements (Ed 2.0 2010)
IEC 61851-22, Electric vehicle conductive charging system ― Part 22: AC electric vehicle charging station
IEC 61851-23, Electric vehicle conductive charging system - Part 23: D.C. electric vehicle charging station
IEC 62196-2, Plugs, socket-outlets, vehicle connectors and vehicle inlets – Conductive charging of electric
vehicles – Part 2: Dimensional compatibility and interchangeability requirements for A.C. pin and contact-
tube accessories
IEC 62196-3, Plugs, socket-outlets, vehicle connectors and vehicle inlets – Conductive charging of electric
vehicles – Part 3: Dimensional compatibility and interchangeability requirements for D.C. and A.C./D.C. pin
and contact-tube vehicle couplers
W3C EXI 1.0, Efficient XML Interchange (EXI) Format 1.0, W3C Recommendation (March 2011)
IETF RFC 768, User Datagram Protocol (August 1980)
ISO/DIS 15118-2:2022(E)
IETF RFC 793, Transmission Control Protocol - DARPA Internet Program - Protocol Specification
(September 1981)
IETF RFC 1630, Universal Resource Identifiers in WWW (June 1994)
IETF RFC 1981, Path MTU Discovery for IP version 6 (August 1996)
IETF RFC 2460, Internet Protocol, Version 6 (IPv6) Specification (December 1998)
IETF RFC 6960, X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP (June
2013)
IETF RFC 3122, Extensions to IPv6 Neighbor Discovery for Inverse Discovery Specification (June 2001)
IETF RFC 3315, Dynamic Host Configuration Protocol for IPv6 (DHCPv6) (July 2003)
IETF RFC 3484, Default Address Selection for Internet Protocol version 6 (IPv6) (February 2003)
IETF RFC 6582, The NewReno Modification to TCP's Fast Recovery Algorithm (April 2012)
IETF RFC 4050, Using the Elliptic Curve Signature Algorithm (ECDSA) for XML Digital Signatures (April
2005)
IETF RFC 4291, IP Version 6 Addressing Architecture (February 2006)
IETF RFC 4429, Optimistic Duplicate Address Detection (DAD) for IPv6 (April 2006)
IETF RFC 4443, Internet Control Message Protocol (ICMP v6) for the Internet Protocol version 6 (IPv6)
specification (March 2006)
IETF RFC 4514, Lightweight Directory Access Protocol (LDAP): String Representation of Distinguished
Names (June 2006)
IETF RFC 4861, Neighbor Discovery for IP version 6 (IPv6) (September 2007)
IETF RFC 4862, IPv6 Stateless Address Autoconfiguration (September 2007)
IETF RFC 5095, Deprecation of Type 0 Routing Headers in IPv6 (December 2007)
IETF RFC 5234, Augmented BNF for Syntax Specifications: ABNF (January 2008)
IETF RFC 5246, The Transport Layer Security (TLS) Protocol Version 1.2 (August 2008)
IETF RFC 5289, TLS Elliptic Curve Cipher Suites with SHA-256/384 and AES Galois Counter Mode (GCM)
(August 2008)
IETF RFC 5480, Elliptic Curve Cryptography Subject Public Key Information (March 2009)
IETF RFC 5722, Handling of Overlapping IPv6 Fragments (December 2009)
IETF RFC 6066, Transport Layer Security (TLS) Extensions: Extension Definitions (January 2011)
IETF RFC 6106, IPv6 Router Advertisement Options for DNS Configuration (November 2010)
IETF RFC 6961, The Transport Layer Security (TLS) Multiple Certificate Status Request Extension (June
2013)
W3C EXI Profile, Efficient XML Interchange (EXI) Profile, W3C Candidate Recommendation (July 2013)
IANA Service&PortRegistry, Service Name and Transport Protocol Port Number Registry [viewed 2011-
01-16], Available from: http://www.iana.org/assignments/service-names-port-numbers/service-
names-port-numbers.xml
NIST FIPS PUB 180-4, Secure Hash Standard (SHS) (March 2012)
NIST Special Publication 800-56A, Recommendation for Pair-Wise Key Establishment Schemes Using
Discrete Logarithm Cryptography (Revised) (March 2007)
NIST Special Publication 800-38A, Recommendation for Block Cipher Modes of Operation - Methods and
Techniques (2001)
2 © ISO 2022 – All rights reserved

ISO/DIS 15118-2:2022(E)
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 15118-1 and the following
apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https://www.iso.org/obp
— IEC Electropedia: available at http://www.electropedia.org/
3.1
basic charging
BC
charging phase during a charging session controlled by IEC 61851-1 only
3.1
charging limits
set of physical constraints (e.g. voltage, current, energy, power) that is negotiated during a V2G
Communication Session (3.36) for a charging session
3.2
communication setup timer
timer monitoring the time LINK_READY.indication (DLINKSTATUS=LinkEstablished) until the Session
Setup message
3.3
contract certificate
certificate issued to EVCC either by V2G root CA (3.42) or by Sub-CA (3.29), which is used in XML
signatures in application layer so that SECC or secondary actor can verify the contract issued to the EVCC
and signatures issued by the EVCC
3.4
CP state
control pilot (vehicle) state according to IEC 61851-1 signalled on control pilot line
3.5
credentials
anything that provides the basis for confidence, belief, credit, etc.
EXAMPLE certificates, passwords, user names, etc.
3.6
data link setup
setup phase for establishing the data link
Note 1 to entry: Entry condition: Any valid control pilot signal according to IEC 61851-1; Exit Condition: D-
LINK_READY.indication(DLINKSTATUS=LinkEstablished).
3.7
distinguished encoding rules
DER
method for encoding a data object, such as an X.509 certificate, to be digitally signed or to have its
signature verified
3.8
global address
IP address with unlimited scope
ISO/DIS 15118-2:2022(E)
3.9
high level communication charging
HLC-C
charging phase during a charging session controlled by ISO 15118
3.10
link local address
IP address with link-only scope that can be used to reach neighbouring interfaces attached to the same
link
3.11
identification mode
mandatory and optional messages and parameters with respect to charging scenarios using external
identification means (EIM) and charging scenarios using plug and charge (PnC) for identification
Note 1 to entry: An identification mode covers a set of similar charging scenarios for a specific identification means.
3.12
IP address
IP-layer identifier for an interface or a set of interfaces
3.13
maximum transfer unit
MTU
maximum size (in bytes) of the largest protocol data unit that the data link layer that is passed onwards
3.14
message set
set of mandatory V2G messages (3.38) and parameters for the EVCC or SECC covering one or multiple use
case elements
3.15
message timer
timer monitoring the exchange of a request-response-message-pair (3.23)
3.16
OEM provisioning certificate
certificate issued to the EVCC, so that a contract certificate (3.3) can be securely requested and received
from a secondary actor
3.17
performance time
non-functional timing requirement defining the time a V2G entity (3.37) shall not exceed when executing
or processing certain functionality
Note 1 to entry: This is a fixed time value.
3.18
private environment
area with (physical) access limited to a small number of vehicles (EVs), which may be a private parking
garage or a garage/parking lot of a company with its own EV fleet, where one or several private wall-
box(es) are used instead of public charging stations as EVSE, and where in order to keep the private wall-
box simple and cheap in production and operation it is allowed to stay offline permanently, which allows
a private wall-box to use leaf certificates with a longer maximum validity than allowed for public charging
stations and using a private root certificate which is different to the V2G root certificates (3.43) and which
has to be installed into each EV that is allowed to charge within this specific private environment,
resulting in a limited number of EVs belonging to one private environment, the difference to a “trusted
environment” being that in a (pure; i.e. not additionally “trusted”) private environment TLS and the
corresponding data encryption at connection level is always used, and solely certificate handling is
4 © ISO 2022 – All rights reserved

ISO/DIS 15118-2:2022(E)
simplified for the private wall-box (EVSE) since it may stay offline permanently, resulting in unrestricted
certificate validity periods, shorter certificate chain length, omitting OCSP, and an additional “pairing
mode”
3.19
renegotiation
messaging for updating the agreement on the charging schedule between EV and EVSE during a V2G
communication session (3.36) by retransmitting the parameters SASchedule and ChargingProfile
3.20
request-response message pair
request message and the corresponding response message
3.21
request-response message sequence
predefined sequence of request-response message pairs (3.23)
3.22
SDP client
V2G entity (3.37) that uses the SDP server (3.26) to get configuration information about the SECC to be
able to access the SECC
3.23
SDP server
V2G entity (3.37) providing configuration information for accessing the SECC
3.24
SECC certificate
certificate issued to SECC either by V2G root CA (3.42) or by Sub-CA (3.29), which is used
...