ISO 15118-21:2025

International
Standard
ISO 15118-21
First edition
Road vehicles — Vehicle to grid
2025-09
communication interface —
Part 21:
Common 2nd generation network
layer and application layer
requirements conformance test plan
Véhicules routiers — Interface de communication entre véhicule
et réseau électrique —
Partie 21: Plan de test de conformité aux exigences communes de
la couche réseau et de la couche application de 2ème génération
Reference number
© ISO 2025
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii
Contents Page
Foreword .v
Introduction .vi
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 2
4 Abbreviated terms . 6
5 Conventions . 7
5.1 Requirement structure .7
5.2 Test system (TS) description .8
6 Test architecture reference model . 8
6.1 General information.8
6.2 Platform adapter .8
6.3 SUT adapters .9
6.3.1 General information .9
6.3.2 IEC 61851-1 SUT adapter .9
6.3.3 ISO 15118-20 SUT adapter .10
6.3.4 ISO 15118-3 SUT adapter .11
6.3.5 ISO 15118-8 SUT adapter .11
6.4 Codecs . .11
6.5 Test system (TS) timer handling . 12
6.5.1 Definition of test system (TS) timers and timeouts . 12
6.5.2 Test system timer scenarios for SUT SECC . 13
6.5.3 Test system timer scenarios for SUT EVCC .14
7 Test suite conventions. 17
7.1 General information.17
7.2 Test suite structure (TSS) .17
7.3 Test profiles .18
7.3.1 General information .18
7.3.2 Test configurations .19
7.3.3 Protocol implementation conformance statement (PICS) definition .19
7.3.4 Protocol implementation extra information for testing (PIXIT) definition . 22
7.3.5 Test control .24
7.3.6 TS template messages .24
7.4 Test suite identifiers .24
7.4.1 General information .24
7.4.2 Test case identifiers .24
7.4.3 PICS/PIXIT identifiers . 25
7.4.4 Verdict types . 25
7.5 Test case specification . 26
8 Test case specification for common ISO 15118-20 requirements .27
8.1 General information.27
8.2 Test cases for SUT SECC .27
8.2.1 SECC SDP test case specifications .27
8.2.2 SECC V2GTP test case specifications . 30
8.2.3 SECC common V2G message flow test case specifications . 46
8.3 Test cases for SUT EVCC . 150
8.3.1 EVCC SDP test case specifications . 150
8.3.2 EVCC V2GTP test case specifications . 151
8.3.3 EVCC common V2G message flow test case specifications . 165
Annex A (informative) Test suite coverage .262
Annex B (normative) TS template messages for SUT type EVCC . 299

iii
Annex C (normative) Test system template messages for SUT type SECC .307
Annex D (normative) Test system functions for dynamic data elements in template messages.315
Bibliography .321

iv
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are
members of ISO or IEC participate in the development of International Standards through technical
committees established by the respective organization to deal with particular fields of technical activity.
ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations,
governmental and non-governmental, in liaison with ISO and IEC, also take part in the work.
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 document 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 or www.iec.ch/members_experts/refdocs).
ISO and IEC draw attention to the possibility that the implementation of this document may involve the
use of (a) patent(s). ISO and IEC take no position concerning the evidence, validity or applicability of any
claimed patent rights in respect thereof. As of the date of publication of this document, ISO and IEC had not
received notice of (a) patent(s) which may be required to implement this document. However, implementers
are cautioned that this may not represent the latest information, which may be obtained from the patent
database available at www.iso.org/patents and https://patents.iec.ch. ISO and IEC shall not be held
responsible for identifying any or all such patent rights.
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.
In the IEC, see www.iec.ch/understanding-standards.
This document was prepared jointly by Technical Committee ISO/TC 22, Road vehicles, Subcommittee SC
31, Data communication, and Technical Committee IEC/TC 69, Electrical power/energy transfer systems
for electrically propelled road vehicles and industrial trucks, and with the European Committee for
Standardization (CEN) Technical Committee CEN/TC 301, Road vehicles, in accordance with the Agreement
on technical cooperation between ISO and CEN (Vienna Agreement).
A list of all parts in the ISO 15118 series series can be found on the ISO and IEC websites.
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 and
www.iec.ch/national-committees.

v
Introduction
Resulting from the 2nd generation network layer and application layer requirements for the vehicle to grid
communication interface specified in ISO 15118-20, a corresponding set of abstract test cases is necessary
to verify the conformance of implementations. Hence, this document specifies a conformance test suite for
the 2nd generation network layer and application layer protocols to derive a common basis for conformance
tests. The resulting test suite is a prerequisite for downstream interoperability tests. Since interoperability
tests also involve the actual application logic of an implementation, such tests are beyond the scope of this
document (see NOTE 1). Therefore, this document focuses on the communication interface aspects and the
corresponding requirements given in ISO 15118-20 only.
The layered structure of the conformance test documents with reference to ISO 15118-20 is shown in
Figure 1. The complete set of relevant conformance test documents per charging type is composed of all the
documents within its column according to Figure 1.
Figure 1 — Overview of relevant conformance test plans for ISO 15118-20 per charging type
EXAMPLE For a SUT supporting DC-charging, the following conformance test plan documents apply:
— test plan for common network and application layer requirements (this document);
— test plan for common security requirements;
— test plan for AC-/DC-specific network and application layer requirements (only DC-specific subset applies).
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 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. Instead, it gives confidence that a conforming
implementation has the required capabilities and that its behaviour conforms consistently in representative instances
of communication.
NOTE 2 This document generally refers to SUT instead of implementation under test (IUT), due to the black box
testing paradigm adopted in this document and related certification processes.

vi
NOTE 3 This document has some interdependencies to the conformance tests specified in ISO 15118-5 and ISO 15118-9
which result from ISO/OSI cross layer dependencies in the underlying protocol specification (e.g. for sleep mode).

vii
International Standard ISO 15118-21:2025(en)
Road vehicles — Vehicle to grid communication interface —
Part 21:
Common 2nd generation network layer and application layer
requirements conformance test plan
1 Scope
This document specifies conformance tests in the form of an abstract test suite (ATS) for a system under
test (SUT) that implements an electric-vehicle communication controller (EVCC) or a supply-equipment
communication controller (SECC) for all common requirements specified in ISO 15118-20 that are
independent of a particular charging type (AC, DC, ACD, WPT charging). These conformance tests specify
the testing of capabilities and behaviours of an SUT, as well as checking what is observed against the
conformance requirements specified in ISO 15118-20 and against what the implementer 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-20. The behaviour tests of the ATS examine
an implementation as thoroughly as practical over the full range of dynamic conformance requirements
specified in ISO 15118-20 and within the capabilities of the SUT.
A test architecture is described in correspondence to the ATS. The abstract test cases in this document are
described leveraging this test architecture and are specified in descriptive tabular format covering the ISO/
OSI layer 3 to 7 (network to application layers).
In terms of coverage, this document only covers normative sections and requirements in ISO 15118-20. This
document additionally refers to specific tests for requirements on referenced standards (e.g. IETF RFCs,
W3C Recommendation, etc.) if they are relevant in terms of conformance for implementations according
to ISO 15118-20. However, it is explicitly not intended to widen the scope of this conformance specification
to such external standards, if it is not technically necessary for the purpose of conformance testing for
ISO 15118-20. 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, or the environment of the protocol implementation. Furthermore, the abstract test cases
specified in this document only consider the communication protocol and the system's behaviour specified
in ISO 15118-20. Power flow between the EVSE and the EV is no prerequisite for the test cases specified in
this document.
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-3, Road vehicles — Vehicle to grid communication interface — Part 3: Physical and data link layer
requirements
ISO 15118-5:2018, Road vehicles — Vehicle to grid communication interface — Part 5: Physical layer and data
link layer conformance test
ISO 15118-8, Road vehicles — Vehicle to grid communication interface — Part 8: Physical layer and data link
layer requirements for wireless communication
ISO 15118-9:2022, Road vehicles — Vehicle to grid communication interface — Part 9: Physical and data link
layer conformance test for wireless communication
ISO 15118-20:2022, Road vehicles — Vehicle to grid communication interface — Part 20: 2nd generation
network layer and application layer requirements
IEC 61851-1:2017, Electric vehicle conductive charging system — Part 1: General requirements
IEC 61851-23, Electric vehicle conductive charging system — Part 23: DC electric vehicle charging station
1)
ETSI ES 201 873-5 V4.9.1 , Methods for Testing and Specification (MTS) — The Testing and Test Control
Notation version 3 — Part 5: TTCN-3 Runtime Interface (TRI) (April 2022)
2)
ETSI ES 201 873-6 V4.13.1 , Methods for Testing and Specification (MTS) — The Testing and Test Control
Notation version 3 — Part 6: TTCN-3 Control Interface (TCI) (April 2022)
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 15118-1, ISO 15118-3, ISO 15118-8,
ISO 15118-20 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.25)
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 (3.29) 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 (3.7) 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
collection of abstract test cases (3.1) with reference to a given requirement specification
Note 1 to entry: See ITU-T X.290.
3.3
black box testing
method of testing that examines the behaviour of an system under test (SUT) (3.20) without considering the
internal implementation and structure of the SUT, thus relying on the SUT's open interface for testing
1) Available at https:// www .etsi .org/ deliver/ etsi _es/ 201800 _201899/ 20187305/ 04 .09 .01 _60/ es
_20187305v040901p .pdf.
2) Available at https:// www .etsi .org/ deliver/ etsi _es/ 201800 _201899/ 20187306/ 04 .13 .01 _60/ es
_20187306v041301p .pdf.
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 behaviour 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.
Note 2 to entry: See also static conformance requirements (3.19) and dynamic conformance requirements (3.6).
Note 3 to entry: The requirements for this conformance specification are specified in ISO 15118-20.
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 behaviour 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-20.
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 behaviour
exact response of the system under test (3.20) according to the underlying protocol specification to the
stimulus defined in the test behaviour (3.21)
3.9
implementation conformance statement
ICS
statement made by the supplier of a system under test (3.20) 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-20.
3.10
implementation extra information for testing
IXIT
statement made by a supplier or implementer of a system under test (SUT) (3.20) which contains or references
all information [in addition to that given in the implementation conformance statement (3.9)] related to the SUT
and its testing environment, which enables 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.29)
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 behaviour (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 behaviour (3.21) starts
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-20.
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-20.
3.18
runtime environment
environment that describes the operating system and corresponding platform requirements of a 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-20.
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 behaviour
set of test steps (test body) to achieve the test purpose (3.25) and assign verdicts (3.29) to the possible
outcomes
3.22
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 (3.26)
Note 1 to entry: See ETSI ES 201 873-6 V4.13.1.
3.23
test execution
TE
interpretation or execution of an abstract test suite (3.2)
Note 1 to entry: Conceptually, the test execution can be decomposed into three interacting entities: an executable test
suite, a test framework (3.24) and an optional internal encoding/decoding system entity.
Note 2 to entry: See ETSI ES 201 873-5 V4.9.1.
3.24
test framework
TFW
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 adaptor and platform
adaptor entities via test control interface (3.22) and test runtime interface (3.27). It also manages the executable test suite
(ETS) and the encoding/decoding system (EDS) entities. The test framework initializes adaptors as well as ETS and EDS
entities. This entity performs all the actions necessary to properly start the execution of a test case or function with
parameters in the ETS entity. It queries the test management entity for module parameter values required by the ETS
and sends logging information to it. It also collects and resolves associated verdicts (3.29) returned by the ETS entity.
Note 2 to entry: See also ETSI ES 201 873-5 V4.9.1.
Note 3 to entry: In this document, the test framework TTCN-3 runtime system is used to explain a test framework
functionality.
3.25
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.26
test system
real system combining the test framework (3.24), abstract test suite (3.2), test execution (3.23) and adapters
as well as codecs
Note 1 to entry: The test system typically also contains a common runtime environment (3.18) based on an
operating system.
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.26)
Note 1 to entry: See ETSI ES 201 873-6 V4.13.1.
3.28
test system interface
TSI
test component that provides a mapping of the ports available in the (abstract) TTCN-3 test system (3.26) to
those offered by a real test system
Note 1 to entry: See ETSI ES 201 873-6 V4.13.1.
3.29
verdict
test verdict
statement of “pass”, “fail” or “inconclusive”, as specified in an abstract test case (3.1), concerning conformance
of a 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 purposes of this document, the following abbreviated terms apply:
AP (wireless) access point
APUT access point under test
ATS abstract test suite
CP control pilot
ETT energy transfer types
EV electric vehicle
EVCC electric vehicle communication controller
EVSE electric vehicle supply equipment
EXI efficient XML interchange
HAL hardware abstraction layer
HPGP Homeplug Green PHY
ICS implementation conformance statement
IUT implementation under test
IXIT implementation extra information for testing
MTC main test component
PICS protocol implementation conformance statement
PIXIT protocol implementation extra information for testing
PLC powerline communication
PP proximity pilot
PTC parallel test component
SDP session description protocol
SECC supply equipment communication controller
STA (wireless) station
STAUT station under test
SUT system under test
TC test case
TCI test control interface
TCI-CD TCI-coding and decoding
TE test execution
TRI TTCN-3 runtime interface
TS test system
TSS test suite structure
TTCN-3 testing and test control notation version 3
UDP user data protocol
V2G vehicle-to-grid
WLAN wireless local area network
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 = 21;

— XXX represents the individual requirement number;
— 'requirement text' includes the actual text of the requirement.
5.2 Test system (TS) description
TTCN-3 is used in this document to specify the TS architecture and the conventions for the abstract test
suite. TTCN-3 is, however, not mandatory for the implementation of a conformance TS according to this
document.
[V2G21-001] The implementers of conformance tests shall verify that the test purposes implemented in
their executable test cases are identical to the abstract test cases described in this document.
NOTE In this document, test cases are not programmatically specified in TTNC-3 core language.
6 Test architecture reference model
6.1 General information
Figure 2 provides an overview of the test architecture for this document. Subclauses 6.2, 6.3 and 6.4 specify
the interface requirements Figure 2 for platform adapters and SUT adapters and all applicable codecs.
Figure 2 — Test architecture reference model
6.2 Platform adapter
The platform adapter within the TS is responsible for timers and external functions. Besides means for
timers, which are typically provided as part of the test framework, no external functions are specified for
this document.
[V2G21-002] The platform adapter of the TS shall follow the principles of the TriPlatformPA and the TriPlat-
formTE interfaces (see TRI in Figure 2) as specified in ETSI ES 201 873-5 V4.9.1:2022, 6.5.3.
6.3 SUT adapters
6.3.1 General information
The SUT adapter within the TS adapts the TTCN-3 communication operations to the SUT based on an
abstract TS interface and implements the real TS interface. It is responsible to propagate message requests
and procedure-based calls from the test execution (see Figure 2) to the SUT, and to notify the test execution
of any received test events.
[V2G21-003] Any SUT adapter of the TS shall implement the TriCommunicationSA and the TriCommunica-
tionTE interfaces (see TRI in Figure 2) as specified in ETSI ES 201 873-5 V4.9.1:2022, 6.5.2.
NOTE The actual implementation of these adapters is beyond the scope of this document.
6.3.2 IEC 61851-1 SUT adapter
The IEC 61851-1 SUT adapter implements a parallel test component (PTC) for the control pilot (CP) and
proximity pilot (PP) signalling specified in IEC 61851-1:2017 Annex A. It continuously controls and/or
observes the positive voltage (state), frequency, duty cycle and the proximity resistor value during the entire
test case execution in accordance with the specified valid range of values as specified in IEC 61851-1:2017,
Annex A.
[V2G21-004] The IEC 61851-1 SUT adapter as shown in Figure 2 shall adapt the functions as specified in
subclauses 6.3.2.1 to 6.3.2.3 to the CP or PP signal
NOTE 1 The IEC 61851-1 SUT adapter involves a hardware component for these adaptations. The corresponding
electrical requirements on the CP or PP line, such as accuracy, resolution, or measurement bandwidth, etc. are beyond
the scope of this document. For further information on such requirements refer to IEC 61851-1:2017 Annex A and
Reference [3].
NOTE 2 For AC charging systems, the underlying application requirements for CP and PP considered in this
document are specified in IEC 61851-1.
NOTE 3 For DC charging systems, the underlying application requirements for CP and PP considered in this
document are specified in IEC 61851-1 and IEC 61851-23.
NOTE 4 Applicability of IEC 61851-1 SUT adapter depends on underlying test configuration as specified in
subclause 7.3.2
6.3.2.1 Requirements of IEC 61851-1 SUT adapter for SECC or EVCC testing
[V2G21-005] The IEC 61851-1 SUT adapter for SECC or EVCC testing shall provide a function to get the
current CP state or associated voltage level.
[V2G21-006] The IEC 61851-1 SUT adapter for SECC or EVCC testing shall provide a call-back function
via the PTC which reports change events of the current CP state or associated voltage level.
[V2G21-007] The IEC 61851-1 SUT adapter for SECC or EVCC testing shall provide a function to set the PP
on the SUT side.
[V2G21-008] The IEC 61851-1 SUT adapter for SECC or EVCC testing shall provide a function to get the PP
resistor value from the SUT side.
[V2G21-009] The IEC 61851-1 SUT adapter for SECC or EVCC testing shall provide a call-back function
via the PTC)which reports change events of the resistor value of the PP from the SUT side.

[V2G21-010] The IEC 61851-1 SUT adapter for SECC or EVCC testing shall provide a function to get the CP
duty cycle in percentage.
[V2G21-011] The IEC 61851-1 SUT adapter for SECC or EVCC testing shall provide a call-back function via
the PTC which reports changes of the CP duty cycle in percentage.
[V2G21-012] The IEC 61851-1 SUT adapter for SECC or EVCC testing shall provide a function to get the CP
frequency in hertz.
[V2G21-013] The IEC 61851-1 SUT adapter for SECC or EVCC testing shall provide a call-back function via
the PTC which reports change events of the CP frequency in hertz.
6.3.2.2 Requirements of IEC 61851-1 SUT adapter for SECC testing
[V2G21-014] The IEC 61851-1 SUT adapter for SECC testing shall provide a function to set the current CP
state or associated voltage level. States B, C and D or the associated voltage level shall be
supported. Other voltage levels are optional.
6.3.2.3 Requirements of IEC 61851-1 SUT adapter for EVCC testing
[V2G21-015] The IEC 61851-1 SUT adapter for EVCC testing shall provide a function to set the current
CP state or associated voltage level. States E and F or the associated voltage level shall be
supported. Other voltage levels are optional.
[V2G21-016] The IEC 61851-1 SUT adapter for EVCC testing shall provide a function to set the current CP
duty cycle in percentage. The values 5 %, and 7 %−98 % shall be supported. Other values
are optional.
[V2G21-017] The IEC 61851-1 SUT adapter for EVCC testing shall provide a function to set current CP fre-
quency in hertz [Hz]. A value of 1 000 Hz ± 5 % shall be supported. Other values are optional.
[V2G21-018] The IEC 61851-1 SUT adapter for EVCC testing shall provide a function to switch on/off the
CP line to simulate an un-plug or plug-in for the SUT. State A or the associated voltage level
shall be supported. Another voltage level is optional.
6.3.3 ISO 15118-20 SUT adapter
[V2G21-019] The ISO 15118-20 SUT adapter as shown in Figure 2 shall send/receive the encoded SDP
requests/responses through UDP messages to/from the SUT as specified in ISO 15118-20.
[V2G21-020] The ISO 15118-20 SUT as shown in Figure 2 adapter shall send/receive the encoded V2G
messages through a TLS connection to/from the SUT as specified in ISO 15118-20.
[V2G21-021] The ISO 15118-20 SUT adapter as shown in Figure 2 shall support internal control messages
for TLS connection management.
NOTE 1 The TCP/TLS connection management includes the following functionalities:
a) control for TCP/TLS port disconnection handling;
b) control for receiving information / status on a given TCP/TLS connection;
c) notification of TCP connection status events;
d) notification of TLS Handshake status events.
[V2G21-022] The ISO 15118-20 SUT adapter as shown in Figure 2 shall provide additional parameters for
TCP and TLS connection configuration.
NOTE 2 The TCP/TLS connection configuration includes the following functionalities:

a) configuration for IP address and port;
b) configuration for usage of security (TCP/TLS);
c) configuration for cipherSuite;
d) configuration for TLS protocol version;
e) configuration for TLS certificate.
6.3.4 ISO 15118-3 SUT adapter
[V2G21-023] For an HPGP-based SUT the ISO 15118-3 SUT adapter as shown in Figure 2 shall be imple-
mented in accordance with ISO 15118-5:2018, 6.3.
NOTE 1 Applicability of ISO 15118-3 SUT adapter depends on underlying test configuration as specified in
subclause 7.3.2
6.3.5 ISO 15118-8 SUT adapter
[V2G21-024] For a WLAN-based SUT the ISO 15118-8 SUT adapter as shown in Figure 2 shall be imple-
mented in accordance with ISO 15118-9:2022, 6.3.
NOTE 1 Applicability of ISO 15118-8 SUT adapter depends on underlying test configuration as specified in
subclause 7.3.2
6.4 Codecs
A codec is responsible for the external encoding and decoding of the TS’s internal data representation into
bit strings suitable to be sent to the SUT. The test execution (TE) determines which codec shall be used and
passes the TS’s data representation into the appropriate encoder to obtain the encoded data. Received data
is decoded in this entity by using the appropriate decoder, which translates the received data into TS’s data
representation that can be matched against expected values or templates.
[V2G21-025] All codecs in this document shall follow the principles of the TCI-CD interface as specified
in ETSI ES 201 873-6 V4.13.1:2022, 7.3.2.
NOTE 1 For conformance testing in this document, the V2G-EXI, SDP, V2GTP, and security codecs (see Figure 2) are
used to encode or decode messages consumable by the tester into bit strings/signals consumable by the SUT.
NOTE 2 The exact implementation of these codecs is beyond the scope of this document.
[V2G21-026] The V2G-EXI codec shall encode message values of the TS into corresponding EXI streams
in accordance with ISO 15118-20:2022, 7.9.1.
[V2G21-027] The security codec shall encode message values of the TS for X.509 Certificates into a cor-
responding Base64 representation suitable for EXI streams in accordance with ISO 15118-
20:2022, 7.9.2.
[V2G21-028] The V2G-EXI codec shall decode EXI streams in accordance with ISO 15118-20:2022, 7.9.1
into message values of the TS.
[V2G21-029] The V2G-EXI codec shall validate decoded EXI streams for correct grammar according to
the XML schema specified in ISO 15118-20 and indicate a fault if a decoded EXI stream is
not well-formed.
[V2G21-030] The security codec shall decode Base64 representation of X.509 certificates from EXI streams
and decode DER representation in accordance with ISO 15118-20:2022, 7.9.2 into message
values of the TS for X.509 certificates.

---------------------
...