oSIST prEN ISO 15118-4:2025

Road vehicles - Vehicle to grid communication interface - Part 4: Network and application protocol conformance test (ISO/DIS 15118-4:2024)

ISO 15118-4:2018 specifies conformance tests in the form of an Abstract Test Suite (ATS) for a System Under Test (SUT) implementing an EVCC or SECC according to ISO 15118-2. These conformance tests specify the testing of capabilities and behaviors of an SUT as well as checking what is observed against the conformance requirements specified in ISO 15118-2 and against what the supplier states the SUT implementation's capabilities are.
The capability tests within the ATS check that the observable capabilities of the SUT are in accordance with the static conformance requirements defined in ISO 15118-2. The behavior tests of the ATS examine an implementation as thoroughly as is practical over the full range of dynamic conformance requirements defined in ISO 15118-2 and within the capabilities of the SUT (see NOTE).
A test architecture is described in correspondence to the ATS. The conformance test cases in this document are described leveraging this test architecture and are specified in TTCN-3 Core Language for ISO/OSI Network Layer (Layer 3) and above. The conformance test cases for the Data Link Layer (Layer 2) and Physical Layer (Layer 1) are described in ISO 15118-5. Test cases with overlapping scopes are explicitly detailed.
This document does not include specific tests of other standards referenced within ISO 15118-2, e.g. IETF RFCs. Furthermore, the conformance tests specified in this document do not include the assessment of performance nor robustness or reliability of an implementation. They cannot provide judgments on the physical realization of abstract service primitives, how a system is implemented, how it provides any requested service, nor the environment of the protocol implementation. Furthermore, the test cases defined in this document only consider the communication protocol defined ISO 15118-2. Power flow between the EVSE and the EV is not considered.
NOTE 1    Practical limitations make it impossible to define an exhaustive test suite, and economic considerations can restrict testing even further. Hence, the purpose of this document is to increase the probability that different implementations are able to interwork. This is achieved by verifying them by means of a protocol test suite, thereby increasing the confidence that each implementation conforms to the protocol specification. However, the specified protocol test suite cannot guarantee conformance to the specification since it detects errors rather than their absence. Thus conformance to a test suite alone cannot guarantee interworking. What it does do is give confidence that an implementation has the required capabilities and that its behavior conforms consistently in representative instances of communication.
NOTE 2    This document has some interdependencies to the conformance tests defined in ISO 15118-5 which result from ISO/OSI cross layer dependencies in the underlying protocol specification (e.g. for sleep mode)

Straßenfahrzeuge - Kommunikationsschnittstelle zwischen Fahrzeug und Ladestation - Teil 4: Konformitätsprüfungen für das Netzwerk- und Anwendungsprotokoll (ISO/DIS 15118-4:2024)

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

Le présent document spécifie des tests de conformité sous la forme d'une suite de tests abstraits (ATS) pour un système à tester (SUT) implémentant un EVCC ou un SECC conformément à la norme ISO 15118-2. Ces tests de conformité spécifient le contrôle des capacités et des comportements d'un SUT ainsi que la vérification de ce qui est observé en comparaison des exigences de conformité spécifiées dans la norme ISO 15118-2 et en comparaison des capacités de l'implémentation du SUT formulées par le fournisseur.
Les tests de capacités compris dans l'ATS vérifient que les capacités observables du SUT sont conformes aux exigences de conformité statiques définies dans la norme ISO 15118-2. Les tests de comportement de l'ATS examinent une implémentation de la manière la plus approfondie possible sur l'ensemble de l'éventail des exigences de conformité dynamiques définies dans la norme ISO 15118-2 et dans les limites des capacités du SUT (voir NOTE).
Une architecture de test est décrite en rapport avec l'ATS. Dans le présent document, les cas de test de conformité sont décrits en s'appuyant sur cette architecture de test et sont spécifiés en langage noyau TTCN-3 pour la couche réseau (Couche 3) ISO/OSI et supérieures. Les cas de test de conformité pour la couche liaison de données (Couche 2) et la couche physique (Couche 1) sont décrits dans la norme ISO 15118-5. Des cas de test dont les domaines d'application se recoupent sont détaillés de manière explicite.
Le présent document n'inclut pas les tests spécifiques d'autres normes données en référence dans la norme ISO 15118-2, par ex., les RFC de l'IETF. En outre, les tests de conformité spécifiés dans le présent document n'incluent pas l'évaluation du rendement, de la robustesse ou encore de la fiabilité d'une implémentation. Ils ne peuvent servir à la formulation de jugements sur la réalisation physique de primitives de service abstraites, sur la manière dont un système est implémenté, sur la manière dont il fournit un quelconque service requis, ou sur l'environnement de l'implémentation du protocole. En outre, les cas de test définis dans le présent document prennent uniquement en considération le protocole de communication défini dans la norme ISO 15118-2. Le flux d'énergie entre l'EVSE et l'EV n'est pas pris en compte.
NOTE 1    Les limitations pratiques empêchent la définition d'une suite de tests exhaustive, et des considérations économiques peuvent restreindre le test encore davantage. Par conséquent, le présent document a pour but d'accroître la probabilité d'interopérabilité de différentes implémentations. Cela est réalisé en les vérifiant au moyen d'une suite de tests de protocole qui permet ainsi d'augmenter la certitude selon laquelle chaque implémentation est conforme à la spécification du protocole. Cependant, la suite de tests de protocole spécifiée ne peut garantir une conformité à la spécification étant donné qu'elle détecte les erreurs plutôt que leur absence. Par conséquent, la conformité d'une suite de tests ne peut garantir à elle seule une interopérabilité. En revanche, cela apporte la garantie qu'une implémentation présente les capacités requises et que son comportement est systématiquement conforme dans des instances représentatives de communication.
NOTE 2    Le présent document présente certaines interdépendances avec les tests de conformité définis dans la norme ISO 15118-5 qui découlent de dépendances inter-couches ISO/OSI dans la spécification du protocole sous-jacent

Cestna vozila - Komunikacijski vmesnik med vozilom in omrežjem - 4. del: Preskus skladnosti omrežja in aplikacijskega protokola (ISO/DIS 15118-4:2024)

General Information

• Status: Not Published
• Public Enquiry End Date: 18-Feb-2025
• ICS: 35.100.05 - Multilayer applications
• ICS: 43.040.15 - Car informatics. On board computer systems
• ICS: 43.120 - Electric road vehicles
• Technical Committee: CEV - Electric passenger and commercial vehicles
• Current Stage: 4020 - Public enquire (PE) (Adopted Project)
• Start Date: 18-Dec-2024
• Due Date: 07-May-2025
• Completion Date: 19-Feb-2025
• Directive: 2023/1804 - Regulation (EU) 2023/1804 of the European Parliament and of the Council of 13 September 2023 on the deployment of alternative fuels infrastructure, and repealing Directive 2014/94/EU
• Directive: 2023/1804-1 - Regulation (EU) 2023/1804 of the European Parliament and of the Council of 13 September 2023 on the deployment of alternative fuels infrastructure, and repealing Directive 2014/94/EU
• Mandate: M/581 - Standardisation Request as regards communication exchange, electricity, and hydrogen supply for road, maritime transport and inland navigation in support of Directive 2014/94/EU and its planned revision under the ‘Fit for 55’package
• Ref Project: prEN ISO 15118-4 - Road vehicles - Vehicle to grid communication interface - Part 4: Network and application protocol conformance test (ISO/DIS 15118-4:2024)

Relations

• Revises: SIST EN ISO 15118-4:2019 - Road vehicles - Vehicle to grid communication interface - Part 4: Network and application protocol conformance test (ISO 15118-4:2018)
• Effective Date: 10-Jan-2024

Overview

The oSIST prEN ISO 15118-4:2025 standard, titled Road Vehicles - Vehicle to Grid Communication Interface - Part 4: Network and Application Protocol Conformance Test (ISO/DIS 15118-4:2024), is being developed by CEN to define conformance testing methods for vehicle-to-grid (V2G) communication interfaces. This standard focuses on verifying the network and application layer protocol compliance for electric vehicle communication controllers (EVCC) and supply equipment communication controllers (SECC) as specified in ISO 15118-2.

The conformance tests use an Abstract Test Suite (ATS) to ensure that implementations exhibit capabilities and behaviors that comply with ISO 15118-2 requirements. The document specifies tests primarily at the network and application layers (OSI Layers 3 and above), complementing ISO 15118-5, which covers the data link and physical layers. It aims to increase interoperability confidence among different V2G communication implementations, although it cannot guarantee absolute conformance or system performance.

Key Topics

• Conformance Testing: Provides exhaustive test cases and an abstract test suite methodology to assess EVCC and SECC implementations' compliance with ISO 15118-2 protocol specifications.
• Test Architecture Model: Defines interfaces for system under test (SUT), platform adapters, codecs, and test execution platforms, ensuring modular and standardized testing.
• Protocol Layers Covered: Focuses on network and application protocol conformance testing; excludes physical power flow and lower-layer (data link and physical) tests, which are covered separately.
• TTCN-3 Language Usage: Specifies test cases leveraging the TTCN-3 core language, used for automated protocol testing, enhancing repeatability and accuracy.
• Capability and Behavior Testing: Capability tests verify static conformance requirements, while behavior tests evaluate dynamic protocol behaviors within practical and economic constraints.
• Complementary to ISO 15118-5: Clarifies scope boundaries and overlaps with ISO 15118-5 conformance tests dealing with OSI Layer 1 and 2.
• Limitations: Does not include robustness, performance, reliability, or physical implementation assessments; it addresses protocol conformance on communication layers only.

Applications

• Electric Vehicle Charging Systems: Ensures EVCCs (in vehicles) and SECCs (in charging stations) comply with network and application-layer communication protocols for seamless V2G communication.
• Interoperability Validation: Supports manufacturers and testing laboratories in validating that their V2G devices conform to ISO 15118-2 protocols, enhancing cross-vendor compatibility.
• Standardized Test Development: Provides a framework for developing automated conformance tests critical for certification in the electric vehicle infrastructure ecosystem.
• Quality Assurance: Enables suppliers to verify claimed protocol capabilities and behaviors, reducing risks of communication failures during vehicle charging and grid interactions.
• Regulatory Compliance Support: Serves as a reference for national and industry regulations that incorporate conformance to ISO 15118 V2G communication standards.
• V2G Security Assurance: Through protocol layer focus, supports validation of secure communication exchanges as per ISO 15118-2 requirements.

Related Standards

• ISO 15118-2: Core protocol specification defining messages and communication interfaces between EV and EVSE; the fundamental reference for this conformance testing standard.
• ISO 15118-5: Specifies conformance tests for Data Link Layer (Layer 2) and Physical Layer (Layer 1), complementing the scope of ISO 15118-4.
• IETF RFCs: Referenced within ISO 15118-2 for certain network protocols, but are outside the direct test scope of ISO 15118-4.
• IEC Standards on EV Charging: Other relevant IEC standards may define hardware aspects of charging stations and interfaces.
• ISO 15118 Series: The broader set of ISO 15118 parts covering V2G communication, from physical interfaces to high-level application protocols.

---

Keywords: ISO 15118-4, vehicle to grid communication, V2G conformance test, EVCC, SECC, electric vehicle charging, network protocol testing, application protocol testing, TTCN-3, ISO 15118-2 compliance, EVSE communication, V2G interoperability, electric mobility standards, EV charging interface, CEN standards.

Standards Content (Sample)

SLOVENSKI STANDARD
01-februar-2025
Cestna vozila - Komunikacijski vmesnik med vozilom in omrežjem - 4. del: Preskus
skladnosti omrežja in aplikacijskega protokola (ISO/DIS 15118-4:2024)
Road vehicles - Vehicle to grid communication interface - Part 4: Network and
application protocol conformance test (ISO/DIS 15118-4:2024)
Straßenfahrzeuge - Kommunikationsschnittstelle zwischen Fahrzeug und Ladestation -
Teil 4: Konformitätsprüfungen für das Netzwerk- und Anwendungsprotokoll (ISO/DIS
15118-4:2024)
Véhicules routiers - Interface de communication entre véhicule et réseau électrique -
Partie 4: Essai de conformité du protocole d'application et du réseau (ISO/DIS 15118-
4:2024)
Ta slovenski standard je istoveten z: prEN ISO 15118-4
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-4
ISO/TC 22/SC 31
Road vehicles — Vehicle to grid
Secretariat: DIN
communication interface —
Voting begins on:
Part 4: 2024-11-28
Network and application protocol
Voting terminates on:
2025-02-20
conformance test
Véhicules routiers — Interface de communication entre véhicule
et réseau électrique —
Partie 4: Essai de conformité du protocole d'application et du
réseau
ICS: 43.120
THIS DOCUMENT IS A DRAFT CIRCULATED
FOR COMMENTS AND APPROVAL. IT
This document is circulated as received from the committee secretariat. IS THEREFORE SUBJECT TO CHANGE
AND MAY NOT BE REFERRED TO AS AN
INTERNATIONAL STANDARD UNTIL
PUBLISHED AS SUCH.
This draft is submitted to a parallel vote in ISO and in IEC.
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-4:2024(en)
DRAFT
ISO/DIS 15118-4:2024(en)
International
Standard
ISO/DIS 15118-4
ISO/TC 22/SC 31
Road vehicles — Vehicle to grid
Secretariat: DIN
communication interface —
Voting begins on:
Part 4:
Network and application protocol
Voting terminates on:
conformance test
Véhicules routiers — Interface de communication entre véhicule
et réseau électrique —
Partie 4: Essai de conformité 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
This document is circulated as received from the committee secretariat.
AND MAY NOT BE REFERRED TO AS AN
INTERNATIONAL STANDARD UNTIL
PUBLISHED AS SUCH.
This draft is submitted to a parallel vote in ISO and in IEC.
IN ADDITION TO THEIR EVALUATION AS
BEING ACCEPTABLE FOR INDUSTRIAL,
© ISO 2024
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: [phone]
RIGHTS OF WHICH THEY ARE AWARE AND TO
PROVIDE SUPPORTING DOCUMENTATION.
Email: [e-mail]
Website: www.iso.org
Published in Switzerland Reference number
ISO/DIS 15118-4:2024(en)
ii
ISO/DIS 15118-4:2024(en)
Contents Page
1 Scope . 1
2 Normative references . 2
3 Terms and definitions . 2
4 Abbreviated terms . 7
5 Conventions . 8
5.1 Requirement structure . 8
5.2 Test system description . 8
6 Test architecture reference model . 8
6.1 General information . 8
6.2 Platform adapter interface . 9
6.3 SUT adapter interfaces . 9
6.4 Codecs . 12
7 Test suite conventions. 12
7.1 General information . 12
7.2 Test suite structure (TSS) . 13
7.3 Test profiles . 15
7.4 Test suite identifiers . 23
7.5 Test suite coverage . 29
7.6 Test case description . 171
7.7 Test case specification . 172
8 Test case descriptions for 15118-2 V2GTP . 186
8.1 General information . 186
8.2 SECC test cases . 186
8.3 EVCC test cases . 190
9 Test case descriptions for 15118-2 SDP messages . 196
9.1 General information . 196
9.2 SECC test cases . 196
9.3 EVCC test cases . 199
10 Test case descriptions for 15118-2 V2G application layer messages . 234
10.1 General information . 234
10.2 SECC test cases . 234
10.3 EVCC test cases . 412
11 Reliability and Robustness Testing . 682
11.1 General information . 682
11.2 SECC test cases . 682
11.3 EVCC test cases . 685
Annex A (normative) Configuration specifications . 692
A.1 General information . 692
A.2 Parameter configuration . 692
A.3 Timer configuration . 698
A.4 PICS configuration . 699
A.5 PIXIT configuration . 700
Annex B (normative) Test-case specifications for 15118-2 V2GTP . 703
B.1 General information . 703
B.2 SECC test cases . 703
B.3 EVCC test cases . 706
iii
ISO/DIS 15118-4:2024(en)
Annex C (normative) Test-case specifications for 15118-2 SDP messages . 711
C.1 General information . 711
C.2 SECC test cases. 711
C.3 EVCC test cases. 713
Annex D (normative) Test-case specifications for 15118-2 V2G application layer messages . 736
D.1 General information . 736
D.2 SECC test cases. 736
D.3 EVCC test cases. 836
Annex E (normative) Test-case specifications for 15118-2 Reliability and Robustness Testing
................................................................................................................................................. 1005
E.1 General information . 1005
E.2 SECC test cases. 1005
E.3 EVCC test cases. 1009
Annex F (normative) Function specifications for supporting test execution. 1017
F.1 General information . 1017
F.2 Configuration functions . 1017
F.3 Pre-condition functions . 1019
F.4 Post-condition functions . 1051
F.5 Common behavior functions . 1053
F.6 Library functions. 1058
Annex G (normative) Function specifications for 15118-2 V2GTP . 1068
G.1 General information . 1068
G.2 SECC functions . 1068
G.3 EVCC functions . 1070
Annex H (normative) Function specifications for 15118-2 SDP messages . 1074
H.1 General information . 1074
H.2 SECC functions . 1074
H.3 EVCC functions . 1076
Annex I (normative) Function specifications for 15118-2 V2G application layer messages . 1080
I.1 General information . 1080
I.2 SECC functions . 1080
I.3 EVCC functions . 1276
Annex J (normative) Function specifications for 15118-2 Reliability and Robustness Testing 1477
J.1 General information . 1477
J.2 SECC functions . 1477
J.3 EVCC functions . 1483
Annex K (normative) Template specifications for V2G TCP/TLS Port Control . 1510
K.1 General information . 1510
K.2 V2G TCP/TLS port control templates. 1510
Annex L (normative) Template specifications for 15118-2 V2GTP . 1512
L.1 General information . 1512
L.2 Common templates. 1512
Annex M (normative) Template specifications for 15118-2 SDP messages . 1514
M.1 General information . 1514
M.2 Common templates. 1514
Annex N (normative) Template specifications for 15118-2 V2G application layer messages . 1515
N.1 General information . 1515
N.2 Common templates. 1515
N.3 SECC templates . 1527
N.4 EVCC templates . 1539
Annex O (normative) Template specifications for Security . 1568
O.1 General information . 1568
O.2 Common templates. 1568
iv
ISO/DIS 15118-4:2024(en)
Annex P (normative) Data type definitions . 1573
P.1 General information . 1573
P.2 Data types for PICS . 1573
P.3 Data types for PIXIT . 1574
P.4 Data types for V2G TCP/TLS Port Control . 1576
P.5 Data types for V2GTP . 1576
P.6 Data types for SDP messages . 1577
P.7 Data types for V2G messages . 1578
P.8 Data types for Security . 1598
Annex Q (informative) Overview of changed test cases compared to ISO 15118-4:2018 . 1600
Bibliography . 1612

v
ISO/DIS 15118-4:2024(en)
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-4:2018), which has been technically
revised.
The main changes are as follows:
— test control section removed to align with more atomic testing approach (7.3.5 in Ed. 1);
— quality and readability of all Figures improved;
— general error corrections and/or improvements for better consistency in test objective descriptions in
Clauses 8, 9 and 10;
— general error corrections and /or improvements for better consistency in TTCN-3 test case specification in
the Annexes;
— new clause on configuration of electrical parameters and power flow related data added (7.7.9)
— new clause on reliability and robustness test cases added (Clause 11 and Annex E);
— complete list of new, removed and updated test cases in this document is provided in Annex Q.
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.
vi
ISO/DIS 15118-4:2024(en)
Introduction
The complexity resulting from the network and application protocol requirements specified in ISO 15118-2 for
the Vehicle-to-Grid Communication Interface (V2G CI) requires a considerable amount of testing to enable
interoperability between electric vehicles and charging stations. This document therefore specifies a
conformance test suite for the network and application layer protocols of the V2G CI to derive a common and
agreed basis for conformance tests. The resulting test suite is a prerequisite for downstream interoperability
tests. Since interoperability furthermore involves the actual application logic of an implementation those tests
are beyond the scope of this document (see NOTE 1). Hence this document focuses on the communication
interface and the corresponding requirements given in ISO 15118-2 only.
NOTE 1 Practical limitations make it impossible to specify an exhaustive test suite, and economic considerations can
restrict testing even further. Hence, the purpose of this document is to increase the probability that different implementations
can interwork. This is achieved by verifying them by means of a protocol test suite, thereby increasing the confidence that
each implementation conforms to the protocol specification. However, the specified protocol test suite cannot guarantee
conformance to the specification since it detects errors rather than their absence. Thus, conformance to a test suite alone
cannot guarantee interworking. What it does do is give confidence that a conforming implementation has the required
capabilities and that its behavior conforms consistently in representative instances of communication.
NOTE 2 This document generally refers to system under test (SUT) instead of implementation under test (IUT), due to
the black box testing paradigm adopted in this document and related certification processes.
NOTE 3 This document has some interdependencies to the conformance tests specified in ISO 15118-5 which result
from ISO/OSI cross layer dependencies in the underlying protocol specification (e.g. for sleep mode).
NOTE 4 Even though ISO 15118-2:2014 references IEC 61851-1:2011 Edition 2, this document references IEC 61851-
1:2017 Edition 3 because of applicability on the market.

vii
DRAFT INTERNATIONAL STANDARD ISO/DIS 15118-4:2024(en)

Road vehicles — Vehicle to grid communication interface —
Part 4: Network and application protocol conformance test
1 Scope
This document specifies conformance tests in the form of an abstract test suite (ATS) for a system under test
(SUT) implementing an EVCC or SECC according to ISO 15118-2. These conformance tests specify the testing
of capabilities and behaviors of an SUT as well as checking what is observed against the conformance
requirements specified in ISO 15118-2 and against what the supplier states the SUT implementation's
capabilities are.
The capability tests within the ATS check that the observable capabilities of the SUT are in accordance with the
static conformance requirements specified in ISO 15118-2. The behavior tests of the ATS examine an
implementation as thoroughly as is practical over the full range of dynamic conformance requirements specified
in ISO 15118-2 and within the capabilities of the SUT.
A test architecture is described in correspondence to the ATS. The conformance test cases in this document
are described leveraging this test architecture and are specified in TTCN-3 core language for ISO/OSI network
layer (layer 3) and above. The conformance test cases for the Data Link Layer (layer 2) and physical layer (layer
1) are described in ISO 15118-5. Test cases with overlapping scopes are explicitly detailed.
This document does not include specific tests of other standards referenced within ISO 15118-2, e.g. IETF
RFCs. Furthermore, the conformance tests specified in this document do not include the assessment of the
performance of an implementation. They cannot provide judgments on the physical realization of abstract
service primitives, how a system is implemented, how it provides any requested service, nor the environment
of the protocol implementation. Furthermore, the abstract test cases specified in this document only consider
the communication protocol specified ISO 15118-2. Power flow between the EVSE and the EV is no prerequisite
for the test cases specified in this document.

ISO/DIS 15118-4:2024(en)
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 15118-1, Road vehicles ― Vehicle to grid communication interface ― Part 1: General information and use-
case definition
ISO 15118-2:2014, Road vehicles ― Vehicle-to-Grid Communication Interface ― Part 2: Network and
application protocol requirements
ISO 15118-3, Road vehicles ― Vehicle-to-Grid Communication Interface ― Part 3: Physical and data link layer
requirements
ISO 15118-5, Road vehicles — Vehicle to grid communication interface — Part 5: Physical layer and data link
layer conformance test
IEC 61851-1:2017, Electric vehicle conductive charging system ― Part 1: General requirements
ETSI ES 201 873-5 V4.6.1, TTCN-3: TTCN-3 Runtime Interface (June 2014)
ETSI ES 201 873-6 V4.6.1, TTCN-3: TTCN-3 Control Interface (June 2014)
3 Terms and definitions
For the purpose of this document, the terms and definitions given in ISO 15118-1, ISO 15118-2, ISO 15118-3
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 https://www.electropedia.org/
3.1
abstract test case
complete and independent specification of the actions required to achieve a specific test purpose (3.24)
Note 1 to entry: See ITU-T X.290.
Note 2 to entry: This specification is defined at the level of abstraction of a particular abstract test method, starting in a
stable testing state and ending in a stable testing state and can involve one or more consecutive or concurrent connections.
Note 3 to entry: The specification is complete in the sense that it is sufficient to enable a test verdict to be assigned
unambiguously to each potentially observable test outcome (i.e. sequence of test events).
Note 4 to entry: The specification is independent in the sense that it is possible to execute the derived executable test
case in isolation from other such test cases (i.e. the specification always includes the possibility of starting and finishing in
the “idle” state).
3.2
abstract test suite
ATS
a collection of abstract test cases (3.1) with reference to a given requirement specification
Note 1 to entry: See ITU-T X.290.
ISO/DIS 15118-4:2024(en)
3.3
black box testing
method of testing that examines the behaviour of a system under test (3.20) without considering the internal
implementation and structure of the system under test, thus relying on the system under test’s open interface
for testing
3.4
conformance requirement
requirement for implementation of a real open system which is claimed to conform to the relevant specification(s)
that can be validated by black box testing (3.3)

Note 1 to entry: The set of conformance requirements together define the behavior of the system and its communication.
Conformance of a real open system is, therefore, expressed at two levels, conformance to each individual requirement
and conformance to the set. In this document, applicable conformance tests include requirements as far as they can be
validated by black box testing (3.3).
Note 2 to entry: See also static conformance requirements (3.20) and dynamic conformance requirements (3.6).
Note 3 to entry: The requirements for this conformance specification are specified in ISO 15118-2.

3.5
conforming implementation
system under test (3.20) which satisfies both static conformance requirements (3.19) and dynamic conformance
requirements (3.6), consistent with the capabilities stated in the protocol implementation conformance
statements (3.16)
Note 1 to entry: See ITU-T X.290.
3.6
dynamic conformance requirement
requirement which specifies what observable behavior is permitted by the relevant specification(s) in instances
of communication
Note 1 to entry: See ITU-T X.290.
Note 2 to entry: The requirements for this conformance specification are specified in ISO 15118-2.
3.7
executable test case
realization of an abstract test case (3.1)
Note 1 to entry: See ITU-T X.290.
3.8
expected behavior
exact response of the SUT (3.20) according to the underlying protocol specification to the stimulus defined in
the test behavior (3.21)
3.9
implementation conformance statement
ICS
statement made by the supplier of an implementation or system claimed to conform to a given specification,
stating which capabilities have been implemented
Note 1 to entry: See ITU-T X.290.
Note 2 to entry: The given document for this conformance specification is ISO 15118-2.
ISO/DIS 15118-4:2024(en)
3.10
implementation extra information for testing
IXIT
statement made by a supplier or implementer of a system under test (3.20) which contains or references all
information [in addition to that given in the implementation conformance statements (3.9)] related to the system
under test and its testing environment, which will enable the test laboratory to run an appropriate test suite
against the SUT
Note 1 to entry: See ITU-T X.290.
3.11
implementation under test
IUT
implementation of one or more open system interconnection protocols in an adjacent user/provider relationship,
being part of a real open system, which is to be studied by testing
Note 1 to entry: See ITU-T X.290.
3.12
main test component
MTC
single test component in a test component configuration responsible for creating and controlling parallel test
components (3.13) and computing and assigning the test verdict (3.30)
Note 1 to entry: See ITU-T X.292.
3.13
parallel test component
PTC
test component created by the main test component (3.12)
Note 1 to entry: See ITU-T X.292.
3.14
post-condition
test steps needed to define the path from the end of the test behavior (3.21) up to the finishing stable state for
the abstract test case (3.1)
3.15
pre-condition
test steps needed to define the path from the starting stable state of the abstract test case (3.1)up to the initial
state from which the test bevavior (3.21) will start
3.16
protocol implementation conformance statement
PICS
implementation conformance statement (3.9) for an implementation or system claimed to conform to a given
protocol specification
Note 1 to entry: See ITU-T X.290.
Note 2 to entry: The given protocol document for this conformance specification is ISO 15118-2.
Note 3 to entry: In the context of this document, PICS specify the configuration of the Test System (e.g. what test cases
need to be executed and what confiugration is required for each testcase)
ISO/DIS 15118-4:2024(en)
3.17
protocol implementation extra information for testing
PIXIT
implementation extra information for testing (3.10) related to testing for conformance to a given protocol
specification
Note 1 to entry: See ITU-T X.290.
Note 2 to entry: The given protocol document for this conformance specification is ISO 15118-2.
Note 3 to entry: In the context of this document, PIXIT specify the configuration of the System under Test (SUT) (e.g.
what protocol options are implemented and what confiugration is required for each testcase)
3.18
runtime environment
environment that describes the operating system and corresponding platform requirements of a system
EXAMPLE Test system.
3.19
static conformance requirement
requirement that specifies the limitations on the combinations of implemented capabilities permitted in a real
open system which is claimed to conform to the relevant specification(s)
Note 1 to entry: See ITU-T X.290.
Note 2 to entry: The requirements for this conformance specification are specified in ISO 15118-2.
3.20
system under test
SUT
real open system in which the implementation under test (3.11) resides
Note 1 to entry: See ITU-T X.290.
3.21
test behavior
set of test steps (test body) which are essential to achieve the test purpose and assign verdicts to the possible
outcomes
3.22
test execution
TE
interpretation or execution of an abstract test suite (3.2)
Note 1 to entry: Conceptually, the TE can be decomposed into three interacting entities: an Executable Test Suite (ETS),
a Test Framework (TFW) and an optional internal Encoding/Decoding System (EDS) entity.
Note 2 to entry: See also ETSI ES 201 873-5 V4.6.1.
3.23
test framework
TFW
an entity to perform all actions of executable test cases (3.7) or functions
Note 1 to entry: The Test Framework interacts with the test management, system under test adapter and platform
adapter entities via test control interface (TCI) and test runtime interface (TRI). It additionally initializes and manages the
executable test suite and encoding/decoding system entities. This entity performs all the actions necessary to properly start
the execution of a test case or function with parameters in the executable test suite entity. It queries the test management
ISO/DIS 15118-4:2024(en)
entity for module parameter values required by the executable test suite and sends logging information to it. It also collects
and resolves associated verdicts returned by the executable test suite entity.
Note 2 to entry: See also ETSI ES 201 873-5 V4.6.1.
Note 3 to entry: In this document, the test framework TTCN-3 runtime system is used to explain a test framework
functionality.
3.24
test purpose
prose description of a well-defined objective of testing, focusing on a single static conformance requirement
(3.19) or dynamic conformance requirement (3.6) or a set as specified in the appropriate OSI specification
Note 1 to entry: See ITU-T X.290.
EXAMPLE Verifying the support of a specific value of a specific parameter.
3.25
test system
real system combining the test framework (3.23), abstract test suite (3.2), test execution (3.22) and adapters as
well as codecs
Note 1 to entry: Typically, also containing a common runtime environment based on an operating system.
3.26
test control interface
TCI
four interfaces that define the interaction of the TTCN-3 executable with the test management, the coding and
decoding, the test component handling and the logging in a test system
Note 1 to entry: See ETSI ES 201 873-6 V4.6.1.
3.27
test runtime interface
TRI
two interfaces that define the interaction of the TTCN-3 executable between the system under test (3.20) and
the platform adapter and the system adapter in a test system (3.25)
Note 1 to entry: See ETSI ES 201 873-6 V4.6.1.
3.28
test system interface
TSI
test component that provides a mapping of the ports available in the (abstract) TTCN-3 test system to those
offered by a real test system
Note 1 to entry: See ETSI ES 201 873-6 V4.6.1.
3.29
valid test behavior
VTB
test steps where the test system sends stimuli to the system under test (3.20) that are valid (syntactically and
semantically) according to the protocol requirements
Note 1 to entry: This type of test behavior is specified in this document.
Note 2 to entry: The protocol requirements for this conformance specification are specified in ISO 15118-2.
ISO/DIS 15118-4:2024(en)
3.30
verdict
test verdict
statement of “pass”, “fail” or “inconclusive”, as specified in an abstract test case (3.1), concerning conformance
of an system under test (3.20) with respect to that test case when it is executed
Note 1 to entry: See ITU-T X.290.
4 Abbreviated terms
For the purpose of this document, the following abbreviations apply:
ALM Application Layer Message
ATS Abstract Test Suite
BEV Battery Electric Vehicle
CA Certificate Authority
CPL Control Pilot Line
CRL Certificate Revocation List
DH Diffie Hellman
DER Distinguished Encoding Rules
ECDSA Elliptic Curve Digital Signature Algorithm
EDS Encoding/Decoding System
EIM External Identification Means
EMAID E-Mobility Account Identifier
ETS Executable Test Suite
EV Electric Vehicle
EVCC Electric Vehicle Communication Controller
EVSE Electric Vehicle Supply Equipment
EXI Efficient XML Interchange
HAL Hardware Abstraction Layer
ICS Implementation Conformance Statement
ID(s) Identifier(s)
IUT Implementation under Test
IXIT Implementation eXtra Information for Testing
OCSP Online Certificate Status Protocol
OEM Original Equipment Manufacturer
PWM Pulse Width Modulation
MTC Main Test Component
NACK Negative Acknowledgement
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
PIXIT Protocol Implementation eXtra Information for Testing
PKI Public Key Infrastructure
PLC Power Line Communication
PnC Plug and Charge
PTC Parallel Test Component
SA Secondary Actor
SDP SECC Discovery Protocol
SECC Supply Equipment Communication Controller
ISO/DIS 15118-4:2024(en)
SLAC Signal Level Attenuation Characterization
SUT System Under Test
TC Test Case (abstract or executable)
TCI Test Control Interface
TCP Transmission Control Protocol
TE Test Execution
TFW Test Framework
TP Test Purpose
TRI Test Runtime Interface
TSI Test System Interface
TSS Test Suite Structure
TTCN-3 Testing and Test Control Notation version 3
V2G Vehicle-to-Grid
V2G CI V2G Communication Interface
V2GTP V2G Transfer Protocol
VTB Valid Test Behavior
UDP User Datagram Protocol
XML Extensible Markup Language
5 Conventions
5.1 Requirement structure
This document uses unique number identifiers for each individual requirement. This requirement structure
allows for easier requirement tracking and management. The following format is used throughout this document:
"[V2G"Y"-"XXX"]" requirement text
Where:
 "V2G" represents the ISO 15118 series,
 "Y" represents the document part of the ISO 15118 series, for this document Y = 4
 "XXX" represents the individual requirement number and
 "requirement text" includes the actual text of the requirement.
5.2 Test system description
TTCN-3 is used in this document to specify the test system and the abstract test cases in the abstract test suite.
However, using TTCN-3 is not mandatory for the implementation of conformance tests of ISO 15118-2.
[V2G4-001] The implementers of conformance tests shall verify that all test objectives implemented in their
environment are identical to those described in this document.
6 Test architecture reference model
6.1 General information
Figure 1 provides an overview on the test architecture for this document. Subclauses 6.2, 6.3 and 6.4 specify
the interface requirements in Figure 1 for platform adapters, SUT adapters and all applicable codecs.
ISO/DIS 15118-4:2024(en)
Test case
specification
ISO 15118-4
Test
system
Dynamic Test-PKI
user
ISO 15118-4
Test SyTest system
Test framework
System
Codecs
Test Test logging under
Test suite
V2G-EXI
mgmt. & reporting
test
SDP
(SUT)
TCI
V2GTP
Security
Test execution
TCI
External
functions
Security
ISO 15118-2
Platform
IEC 61851-1 ISO 15118-2
messaging
adapter
SUT adapter SUT adapter
Runtime environment
IEC 61851-1:2017 Annex A
PWM signaling
Figure 1 — Test architecture reference model for testing of ISO 15118-2
For the scope of this document only the "ISO 15118-2 – Messaging" interface to the SUT and its dependencies
to the corresponding "IEC 61851-1:2017, Annex A – PWM Signaling" interface are relevant. This document
therefore limits its scope to the respective SUT adapters and codecs.
6.2 Platform adapter interface
The platform adapter within the test system is responsible for timers and external functions. Besides means for
timers, which are typically provided as part of the test framework and runtime environment, there are external
functions specified for XML security in 7.7.11 and EIM st
...