oSIST prEN ISO 15118-2:2025

SLOVENSKI STANDARD
01-oktober-2025
Cestna vozila - Komunikacijski vmesnik med vozilom in omrežjem - 2. del: Zahteve
za protokol omrežja in uporabe (ISO/DIS 15118-2:2025)
Road vehicles - Vehicle-to-Grid Communication Interface - Part 2: Network and
application protocol requirements (ISO/DIS 15118-2:2025)
Straßenfahrzeuge - Kommunikationsschnittstelle zwischen Fahrzeug und Ladestation -
Teil 2: Anforderungen an das Netzwerk- und Anwendungsprotokoll (ISO/DIS 15118-
2:2025)
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:2025)
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
Road vehicles — Vehicle-to-Grid
Secretariat: DIN
Communication Interface —
Voting begins on:
Part 2: 2025-08-26
Network and application protocol
Voting terminates on:
2025-11-18
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 A DRAFT CIRCULATED
FOR COMMENTS AND APPROVAL. IT
IS THEREFORE SUBJECT TO CHANGE
AND MAY NOT BE REFERRED TO AS AN
INTERNATIONAL STANDARD UNTIL
PUBLISHED AS SUCH.
This document is circulated as received from the committee secretariat.
IN ADDITION TO THEIR EVALUATION AS
BEING ACCEPTABLE FOR INDUSTRIAL,
TECHNOLOGICAL, COMMERCIAL AND
USER PURPOSES, DRAFT INTERNATIONAL
STANDARDS MAY ON OCCASION HAVE TO
ISO/CEN PARALLEL PROCESSING
BE CONSIDERED IN THE LIGHT OF THEIR
POTENTIAL TO BECOME STANDARDS TO
WHICH REFERENCE MAY BE MADE IN
NATIONAL REGULATIONS.
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.
Reference number
ISO/DIS 15118-2:2025(en)
DRAFT
ISO/DIS 15118-2:2025(en)
International
Standard
ISO/DIS 15118-2
ISO/TC 22/SC 31
Road vehicles — Vehicle-to-Grid
Secretariat: DIN
Communication Interface —
Voting begins on:
Part 2:
Network and application protocol
Voting terminates on:
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: ISO ics
THIS DOCUMENT IS A DRAFT CIRCULATED
FOR COMMENTS AND APPROVAL. IT
IS THEREFORE SUBJECT TO CHANGE
AND MAY NOT BE REFERRED TO AS AN
INTERNATIONAL STANDARD UNTIL
PUBLISHED AS SUCH.
This document is circulated as received from the committee secretariat.
IN ADDITION TO THEIR EVALUATION AS
BEING ACCEPTABLE FOR INDUSTRIAL,
© ISO 2025
TECHNOLOGICAL, COMMERCIAL AND
USER PURPOSES, DRAFT INTERNATIONAL
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
STANDARDS MAY ON OCCASION HAVE TO
ISO/CEN PARALLEL PROCESSING
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
BE CONSIDERED IN THE LIGHT OF THEIR
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
POTENTIAL TO BECOME STANDARDS TO
WHICH REFERENCE MAY BE MADE IN
or ISO’s member body in the country of the requester.
NATIONAL REGULATIONS.
ISO copyright office
RECIPIENTS OF THIS DRAFT ARE INVITED
CP 401 • Ch. de Blandonnet 8
TO SUBMIT, WITH THEIR COMMENTS,
CH-1214 Vernier, Geneva
NOTIFICATION OF ANY RELEVANT PATENT
Phone: +41 22 749 01 11
RIGHTS OF WHICH THEY ARE AWARE AND TO
PROVIDE SUPPORTING DOCUMENTATION.
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland Reference number
ISO/DIS 15118-2:2025(en)
ii
ISO/DIS 15118-2:2025(en)
ISO/DIS 15118-2:2025(E)
Contents
Foreword . vii
Introduction . ix
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 3
4 Abbreviated terms . 7
5 Conventions . 8
5.1 Definition of OSI based services . 8
5.2 Requirement structure . 8
5.3 Usage of RFC references. 9
5.4 Notation used for XML schema diagrams . 9
6 Document overview . 9
7 Basic requirements for V2G communication . 11
7.1 General information . 11
7.2 Service primitive concept of OSI layered architecture . 11
7.2.1 Overview . 11
7.2.2 Syntax of service primitives . 12
7.3 Security concept . 12
7.3.1 Call flows (flow charts) . 12
7.3.2 Certificate and key management . 16
7.3.3 Number of root certificates and root validity, certificate depth and size . 18
7.3.4 Support and application of TLS . 19
7.4 V2G communication states and data link handling . 21
7.5 Data link layer . 26
7.6 Network layer . 26
7.6.1 General . 26
7.6.2 Applicable RFCs and limitations and protocol parameter settings . 26
7.6.3 IP addressing . 27
7.7 Transport layer . 28
7.7.1 Transmission control protocol (TCP) . 28
7.7.2 User datagram protocol (UDP) . 29
7.7.3 Transport layer security (TLS) . 29
7.8 V2G transfer protocol . 32
7.8.1 General . 32
7.8.2 Supported ports . 33
7.8.3 Protocol data unit . 34
7.9 Presentation layer . 37
7.9.1 XML and efficient XML interchange (EXI) . 37
7.9.2 Message security . 40
7.10 Application layer . 47
7.10.1 SECC discovery protocol . 47
7.10.2 Vehicle to grid application layer messages . 52
7.10.3 Application layer service primitives . 52
8 Application layer messages . 56
8.1 General . 56
8.2 Protocol handshake definition . 57
8.2.1 Handshake sequence . 57

iii
ISO/DIS 15118-2:2025(en)
ISO/DIS 15118-2:2025(E)
8.2.2 Message definition supportedAppProtocolReq and supportedAppProtocolRes . 58
8.2.3 Semantics description supportedAppProtocol messages . 59
8.2.4 Message examples . 60
8.3 V2G message definition . 61
8.3.1 General . 61
8.3.2 Message definition . 61
8.3.3 Message header definition . 62
8.3.4 Message body definition . 63
8.4 V2G communication session and BodyElement definitions . 64
8.4.1 General . 64
8.4.2 Session handling . 65
8.4.3 Common messages . 68
8.4.4 AC messages . 99
8.4.5 DC messages . 102
8.5 Complex data types . 111
8.5.1 Overview . 111
8.5.2 Common . 111
8.5.3 AC . 140
8.5.4 DC . 144
8.6 Identification modes and message set definitions . 152
8.6.1 Overview . 152
8.6.2 Supported message sets . 154
8.6.3 Selection of message sets . 180
8.7 V2G communication timing . 185
8.7.1 Overview . 185
8.7.2 Message sequence and communication session . 186
8.7.3 Session setup and ready to charge . 191
8.7.4 V2G message synchronization with IEC 61851-1 signalling . 200
8.8 Message sequencing and error handling . 220
8.8.1 Overview . 220
8.8.2 Basic Definitions for Error Handling . 221
8.8.3 ResponseCode handling . 222
8.8.4 Request-response message sequence requirements . 227
8.9 Request-response message sequence examples . 276
8.9.1 AC . 276
8.9.2 DC . 279
Annex A (normative) Schema definition . 286
A.1 Overview . 286
A.2 V2G_CI_AppProtocol.xsd . 287
A.3 V2G_CI_MsgDef.xsd . 287
A.4 V2G_CI_MsgHeader.xsd . 288
A.5 V2G_CI_MsgBody.xsd . 288
A.6 V2G_CI_MsgDataTypes.xsd . 296
A.7 xmldsig-core-schema.xsd . 305
Annex B (normative) Certificate profiles . 310
Annex C (normative) Specification of identifiers . 318
C.1 e-Mobility authentication identifier (EMAID) . 318
C.1.1 EMAID syntax . 318

iv © ISO 2025 – All rights reserved
iv
ISO/DIS 15118-2:2025(en)
ISO/DIS 15118-2:2025(E)
C.1.2 EMAID Semantics . 318
C.1.3 Calculation of the check digit . 319
C.2 Electric vehicle supply equipment ID (EVSEID) . 319
C.2.1 EVSEID syntax . 319
C.2.2 EVSEID semantics . 320
Annex D (informative) Mapping of ISO 15118-1 use case elements . 321
D.1 Relation of identification modes and use case elements . 321
Annex E (informative) Message examples . 376
E.1 Value added service selection . 376
E.2 EXI encoded message examples. 378
E.2.1 SessionSetupRes message . 378
E.2.2 ChargeParameterDiscoveryReq message (AC-based). 379
E.2.3 CurrentDemandReq message . 379
E.3 Schedules and tariff information . 380
E.3.1 Overview . 380
E.3.2 Dynamic GridSchedule w/o SalesTariff over ISO 15118 V2G CI . 380
E.3.3 “Time Of Use”-based SalesTariff with constant value for GridSchedule . 382
E.3.4 “Time Of Use”-based SalesTariff with dynamic GridSchedule . 383
E.3.5 “Consumption”-based SalesTariff with constant value for GridSchedule . 385
E.3.6 Multiple SalesTariffs with different demand Limits in GridSchedule . 386
E.3.7 Time of Use-based SalesTariffs including relativePricePercentage . 388
Annex F (informative) Application of certificates . 397
F.1 General information . 397
F.1.1 Overview . 397
F.1.2 Demands of the OEM . 398
F.1.3 Demands of the secondary actors . 398
F.1.4 Rationale for decisions in this document . 399
F.1.5 Overview of the resulting certificate structure . 401
F.2 Simplified certificate management in private environment . 402
F.2.1 Overview (motivation) . 402
F.2.2 Solution for private environments . 402
F.2.2.1 General . 402
F.2.2.2 Installation of a private root certificate into a vehicle . 403
F.2.2.3 Charging in a private environment . 403
F.2.2.4 Compromised certificate of a wall box . 403
F.3 Use of OEM provisioning certificates . 404
F.3.1 Introduction . 404

v
ISO/DIS 15118-2:2025(en)
ISO/DIS 15118-2:2025(E)
F.3.2 Processes . 405
F.3.2.1 Vehicle production . 405
F.3.2.2 Vehicle Hand-Over . 406
F.3.2.3 Contract Conclusion . 406
F.3.2.4 Certificate installation . 406
F.3.2.5 Certificate update . 406
F.3.2.6 Component replacement . 406
F.4 Security appliances and their associated certificates . 407
Annex G (informative) Encryption for the distribution of secret keys . 410
G.1 Overview . 410
G.2 Ephemeral-static Diffie-Hellman key agreement . 410
G.3 Key pairs . 411
Annex H (informative) Message sequencing for renegotiation . 412
H.1 Overview . 412
Annex I (informative) Overview on XML signatures . 419
I.1 Overview . 419
I.2 Signature generation . 419
I.3 Signature generation for secondary actors. 422
I.4 Signature validation . 422
Annex J (informative) Summary of requirements . 424
Annex K (informative) Use of Multiple Contracts in ISO 15118-2 . 432
Bibliography . 434

vi © ISO 2025 – All rights reserved
vi
ISO/DIS 15118-2:2025(en)
ISO/DIS 15118-2:2025(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, in collaboration with the European Committee for Standardization (CEN)
Technical Committee CEN/TC 301, Electrically propelled road vehicles, in accordance with the
Agreement on technical cooperation between ISO and CEN (Vienna Agreement).
This second edition cancels and replaces the first edition (ISO 15118-2:2014), which has been
technically revised.
The main changes 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 various Test Symposia);
— Clarification how to properly use the ChargingProfile;
— Clarification of the interaction between ISO 15118-2 and IEC 61851 during the charging
sequence;
— Introduction of a means to activate an ad-hoc charge control with EIM and PnC;
— Clarification of error handling and shutdown scenarios;
— Introduction of a means to stop the V2G communication session before the V2G charge loop
(external trigger by the user or the charging application);
— Clarification how to use multiple Contract Certificates;
— Removal of the definition of certificate lifetimes, because they should be defined by PKI;
— Removal of the general obligation to use TLS with value added services, because whether or not
TLS must be used should be mandated by the specification of the respective value added service;
— Alignment of TCP behaviour (timeouts, retries, …) with ISO 15118-20.

vii
ISO/DIS 15118-2:2025(en)
ISO/DIS 15118-2:2025(E)
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.

viii © ISO 2025 – All rights reserved
viii
ISO/DIS 15118-2:2025(en)
ISO/DIS 15118-2:2025(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.
ix
ISO/DIS 15118-2:2025(en)
ISO/DIS 15118-2:2025(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
ISO 15118-1, Road vehicles — Vehicle to grid communication interface — Part 1: General information and
use-case definition
ISO 15118-3, Road vehicles — Vehicle to grid communication interface — Part 3: Physical and data link
layer requirements
IEC 61851-1, Electric vehicle conductive charging system ― Part 1: General requirements
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 DC and AC/DC pin
and contact-tube vehicle couplers
W3C EXI 1.0, Efficient XML Interchange (EXI) Format 1.0, W3C Recommendation
ISO/DIS 15118-2:2025(en)
ISO/DIS 15118-2:2025(E)
IETF RFC 768, User Datagram Protocol
IETF RFC 793, Transmission Control Protocol - DARPA Internet Program - Protocol Specification
IETF RFC 1630, Universal Resource Identifiers in WWW
IETF RFC 1981, Path MTU Discovery for IP version 6
IETF RFC 2460, Internet Protocol, Version 6 (IPv6) Specification
IETF RFC 6960:2013, X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP
IETF RFC 3122, Extensions to IPv6 Neighbor Discovery for Inverse Discovery Specification
IETF RFC 3315, Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
IETF RFC 3484, Default Address Selection for Internet Protocol version 6 (IPv6)
IETF RFC 4291, IP Version 6 Addressing Architecture
IETF RFC 4429, Optimistic Duplicate Address Detection (DAD) for IPv6
IETF RFC 4443, Internet Control Message Protocol (ICMP v6) for the Internet Protocol version 6 (IPv6)
specification
IETF RFC 4514:2006, Lightweight Directory Access Protocol (LDAP): String Representation of
Distinguished Names
IETF RFC 4861, Neighbor Discovery for IP version 6 (IPv6)
IETF RFC 4862, IPv6 Stateless Address Autoconfiguration
IETF RFC 5095, Deprecation of Type 0 Routing Headers in IPv6
IETF RFC 5234, Augmented BNF for Syntax Specifications: ABNF
IETF RFC 5246, The Transport Layer Security (TLS) Protocol Version 1.2
IETF RFC 5289, TLS Elliptic Curve Cipher Suites with SHA-256/384 and AES Galois Counter Mode (GCM)
IETF RFC 5480, Elliptic Curve Cryptography Subject Public Key Information
IETF RFC 5722, Handling of Overlapping IPv6 Fragments
IETF RFC 6066, Transport Layer Security (TLS) Extensions: Extension Definitions
IETF RFC 6106, IPv6 Router Advertisement Options for DNS Configuration
IETF RFC 6961, The Transport Layer Security (TLS) Multiple Certificate Status Request Extension
W3C EXI Profile, Efficient XML Interchange (EXI) Profile, W3C Candidate Recommendation
IANA Service&PortRegistry, Service Name and Transport Protocol Port Number Registry
NIST FIPS PUB 180-4, Secure Hash Standard (SHS)
NIST Special Publication 800-56A, Recommendation for Pair-Wise Key Establishment Schemes Using
Discrete Logarithm Cryptography
NIST Special Publication 800-38A, Recommendation for Block Cipher Modes of Operation - Methods and
Techniques
Available from: http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xml
2 © ISO 2022 – All rights reserved
ISO/DIS 15118-2:2025(en)
ISO/DIS 15118-2:2025(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 terminology 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
ad-hoc charging
mode of HLC-C where no power schedule but only one upper power limit is requested by the EVCC
and/or provided by the SECC before HLC-C, and where a renegotiation of the charging limits is
prohibited, and where, any time during the V2G charging loop, the SECC is allowed to reduce ad-hoc its
upper power and/or current limit to a (corresponding) value below the initially provided upper power
limit
3.2
basic charging
BC
energy transfer phase during an AC charging session that is only controlled by control pilot states
according to IEC 61851-1 (Annex A)
3.3
charging
energy transfer, where the direction is restricted to energy transfer from the EVSE to the EV
Note 1 to entry: In this document the term "charging" is used synonymously to the term "energy transfer".
3.4
charging limit
physical constraint (e.g. voltage, current, energy, power) that is negotiated during a V2G Communication
Session (3.36) for a charging session
3.5
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.6
control pilot state
CP state
system state according to IEC 61851-1 (Annex A) signalled on control pilot line
3.7
credentials
anything that provides the basis for confidence, belief, credit, etc.
EXAMPLE Certificates, passwords, user names, etc.
3.8
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 and ISO 15118-3 (i.e. a
CP state BX or CX or DX, where X = 1 or 2); Exit Condition: D-
LINK_READY.indication(DLINKSTATUS=LinkEstablished).
ISO/DIS 15118-2:2025(en)
ISO/DIS 15118-2:2025(E)
3.9
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.10
global address
IP address with unlimited scope
3.11
high level communication charging
HLC-C
energy transfer phase during a charging session controlled by parameters (e.g. charging limits) that are
communicated via digital communication as specified in this document, in addition to the charge
control by control pilot states according to IEC 61851-1 (Annex A)
3.12
link-local address
IP address with link-only scope that can be used to reach neighbouring interfaces attached to the same
link
3.13
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.14
IP address
IP-layer identifier for an interface or a set of interfaces
3.15
maximum transfer unit
MTU
size of the largest protocol data unit (in bytes) that can be communicated in a single network layer
transaction
3.16
message set
set of mandatory V2G messages (3.38) and parameters for the EVCC or SECC covering one or multiple
use case elements
3.17
message timer
timer monitoring the exchange of a request-response-message-pair (3.23)
3.18
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.19
performance time
non-functio
...