Road vehicles - Vehicle to grid communication interface - Part 4: Network and application protocol conformance test

No scope available yet

Straßenfahrzeuge - Kommunikationsschnittstelle zwischen Fahrzeug und Ladestation - Teil 4: Konformitätsprüfungen für das Netzwerk- und Anwendungsprotokoll

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

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

General Information

Status
Not Published
Publication Date
23-Oct-2023
Current Stage
0098 - Decision to abandon - Definition of new project
Start Date
08-Aug-2017
Completion Date
14-Apr-2025
Draft
prEN ISO 15118-4:2021
English language
1584 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (Sample)


SLOVENSKI STANDARD
01-november-2021
Cestna vozila - Komunikacijski vmesnik med vozilom in omrežjem - 4. del: Preskus
skladnosti omrežja in aplikacijskega protokola (ISO/DIS 15118-4:2021)
Road vehicles - Vehicle to grid communication interface - Part 4: Network and application
protocol conformance test (ISO/DIS 15118-4:2021)
Straßenfahrzeuge - Kommunikationsschnittstelle zwischen Fahrzeug und Ladestation -
Teil 4: Konformitätsprüfungen für das Netzwerk- und Anwendungsprotokoll (ISO/DIS
15118-4:2021)
Véhicules routiers - Interface de communication entre véhicule et réseau électrique -
Partie 4: Test de conformité du protocole d'application et du réseau (ISO/DIS 15118-
4:2021)
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 Secretariat: DIN
Voting begins on: Voting terminates on:
2021-09-29 2021-12-22
Road vehicles — Vehicle to grid communication
interface —
Part 4:
Network and application protocol conformance test
Véhicules routiers — Interface de communication entre véhicule et réseau électrique —
Partie 4: Test de conformité du protocole d'application et du réseau
ICS: 43.120
Member bodies are requested to consult relevant national interests in IEC/TC
69 before casting their ballot to the e-Balloting application.
This document is circulated as received from the committee secretariat.
THIS DOCUMENT IS A DRAFT CIRCULATED
FOR COMMENT AND APPROVAL. IT IS
ISO/CEN PARALLEL PROCESSING
THEREFORE SUBJECT TO CHANGE AND MAY
NOT BE REFERRED TO AS AN INTERNATIONAL
STANDARD UNTIL PUBLISHED AS SUCH.
IN ADDITION TO THEIR EVALUATION AS
IMPORTANT — Please use this updated version dated 2020-09-23, and
BEING ACCEPTABLE FOR INDUSTRIAL,
discard any previous version of this DIS. Note that the IEC logo has been
TECHNOLOGICAL, COMMERCIAL AND
added.
USER PURPOSES, DRAFT INTERNATIONAL
STANDARDS MAY ON OCCASION HAVE TO
BE CONSIDERED IN THE LIGHT OF THEIR
POTENTIAL TO BECOME STANDARDS TO
WHICH REFERENCE MAY BE MADE IN
Reference number
NATIONAL REGULATIONS.
ISO/DIS 15118-4:2021(E)
RECIPIENTS OF THIS DRAFT ARE INVITED
TO SUBMIT, WITH THEIR COMMENTS,
NOTIFICATION OF ANY RELEVANT PATENT
RIGHTS OF WHICH THEY ARE AWARE AND TO
PROVIDE SUPPORTING DOCUMENTATION. © ISO 2021

ISO/DIS 15118-4:2021(E)
ISO/DIS 15118-4:2021(E)
Contents Page
Foreword . vi
Introduction . vii
1 Scope . 1
2 Normative references . 2
3 Terms and definitions . 2
4 Symbols (and 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 . 10
7 Test suite conventions. 11
7.1 General information . 11
7.2 Test suite structure (TSS) . 11
7.3 Test profiles . 14
7.4 Test suite identifiers . 21
7.5 Test suite coverage . 28
7.6 Test case description . 169
7.7 Test case specification . 171
8 Test case descriptions for 15118-2 V2GTP . 186
8.1 General information . 186
8.2 SECC test cases . 187
8.3 EVCC test cases . 191
9 Test case descriptions for 15118-2 SDP messages . 195
9.1 General information . 195
9.2 SECC test cases . 196
9.3 EVCC test cases . 198
10 Test case descriptions for 15118-2 V2G application layer messages . 217
10.1 General information . 217
10.2 SECC test cases . 217
10.3 EVCC test cases . 398
11 Reliability and robustness resting . 673
11.1 General information . 673
11.2 SECC test cases . 673
11.3 EVCC test cases . 676
Annex A (normative) Configuration specifications . 683
A.1 Timer configuration . 683
© ISO 2021
A.2 PICS configuration . 684
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
A.3 PIXIT configuration . 685
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting
Annex B (normative) Test-case specifications for 15118-2 V2GTP . 688
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.
B.1 SECC test cases . 688
B.2 EVCC test cases . 691
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Fax: +41 22 749 09 47
Email: copyright@iso.org
iii
Website: www.iso.org
Published in Switzerland
ii © ISO 2021 – All rights reserved

ISO/DIS 15118-4:2021(E)
Contents Page
Foreword . vi
Introduction . vii
1 Scope . 1
2 Normative references . 2
3 Terms and definitions . 2
4 Symbols (and 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 . 10
7 Test suite conventions. 11
7.1 General information . 11
7.2 Test suite structure (TSS) . 11
7.3 Test profiles . 14
7.4 Test suite identifiers . 21
7.5 Test suite coverage . 28
7.6 Test case description . 169
7.7 Test case specification . 171
8 Test case descriptions for 15118-2 V2GTP . 186
8.1 General information . 186
8.2 SECC test cases . 187
8.3 EVCC test cases . 191
9 Test case descriptions for 15118-2 SDP messages . 195
9.1 General information . 195
9.2 SECC test cases . 196
9.3 EVCC test cases . 198
10 Test case descriptions for 15118-2 V2G application layer messages . 217
10.1 General information . 217
10.2 SECC test cases . 217
10.3 EVCC test cases . 398
11 Reliability and robustness resting . 673
11.1 General information . 673
11.2 SECC test cases . 673
11.3 EVCC test cases . 676
Annex A (normative) Configuration specifications . 683
A.1 Timer configuration . 683
A.2 PICS configuration . 684
A.3 PIXIT configuration . 685
Annex B (normative) Test-case specifications for 15118-2 V2GTP . 688
B.1 SECC test cases . 688
B.2 EVCC test cases . 691
iii
ISO/DIS 15118-4:2021(E)
Annex C (normative) Test-case specifications for 15118-2 SDP messages . 696
C.1 SECC test cases. 696
C.2 EVCC test cases. 698
Annex D (normative) Test-case specifications for ISO 15118-2 V2G application layer messages
................................................................................................................................................... 721
D.1 SECC test cases. 721
D.2 EVCC test cases. 820
Annex E (normative) Test-case specifications for ISO 15118-2 reliability and robustness testing
................................................................................................................................................... 990
E.1 SECC test cases. 990
E.2 EVCC test cases. 994
Annex F (normative) Function specifications for supporting test execution. 1002
F.1 Configuration functions . 1002
F.2 Pre-condition functions . 1004
F.3 Post-condition functions . 1035
F.4 Common behavior functions . 1037
F.5 Library functions. 1042
Annex G (normative) Function specifications for ISO 15118-2 V2GTP . 1051
G.1 SECC functions . 1051
G.2 EVCC functions . 1053
Annex H (normative) Function specifications for ISO 15118-2 SDP messages . 1057
H.1 SECC functions . 1057
H.2 EVCC functions . 1059
Annex I (normative) Function specifications for ISO 15118-2 V2G application layer messages
................................................................................................................................................. 1062
I.1 SECC functions . 1062
I.2 EVCC functions . 1254
Annex J (normative) Function specifications for ISO 15118-2 reliability and robustness testing
................................................................................................................................................. 1449
J.1 SECC functions . 1449
J.2 EVCC functions . 1455
Annex K (normative) Template specifications for V2G TCP/TLS port control . 1481
Annex L (normative) Template specifications for 15118-2 V2GTP . 1483
L.1 Common templates. 1483
Annex M (normative) Template specifications for ISO 15118-2 SDP messages . 1485
M.1 Common templates. 1485
Annex N (normative) Template specifications for 15118-2 V2G application layer messages . 1486
N.1 Common templates. 1486
N.2 SECC templates . 1498
N.3 EVCC templates . 1510
Annex O (normative) Template specifications for security . 1546
O.1 Common templates. 1546
Annex P (normative) Data type definitions . 1551
P.1 Data types for PICS. 1551
P.2 Data types for PIXIT . 1552
P.3 Data types for V2G TCP/TLS Port Control . 1553
P.4 Data types for V2GTP . 1554
P.5 Data types for SDP messages . 1555
P.6 Data types for V2G messages . 1556
P.7 Data types for Security . 1576
Bibliography . 1577
iv
ISO/DIS 15118-4:2021(E)
v
ISO/DIS 15118-4:2021(E)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies
(ISO member bodies). The work of preparing International Standards is normally carried out through ISO
technical committees. Each member body interested in a subject for which a technical committee has been
established has the right to be represented on that committee. International organizations, governmental and
non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the International
Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are described in
the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types of ISO
documents should be noted. This document was drafted in accordance with the editorial rules of the ISO/IEC
Directives, Part 2 (see www.iso.org/directives).
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of any patent rights
identified during the development of the document will be in the Introduction and/or on the ISO list of patent
declarations received (see www.iso.org/patents).
Any trade name used in this document is information given for the convenience of users and does not constitute
an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions
related to conformity assessment, as well as information about ISO's adherence to the World Trade
Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www.iso.org/iso/foreword.html.
This document was prepared by Technical Committee ISO/TC 22, Road vehicles, Subcommittee SC 31, Data
communication.
This second edition cancels and replaces the first edition (ISO 15118-4:2018), which has been technically
revised.
The main changes compared to the previous edition 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 reliability and robustness test cases added (Clause 11 and Annex 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.
vi
ISO/DIS 15118-4:2021(E)
Introduction
The first three parts of ISO 15118 describe the use cases and the technical specification of the vehicle-to-grid
communication Interface which is intended for the optimized use of energy resources so that electric road
vehicles can recharge in the most economic or most energy efficient way. It is furthermore required to develop
efficient and convenient billing systems in order 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.
The complexity resulting from the network and application protocol requirements defined in the second part of
the standard requires a considerable amount of testing in order to enable interoperability between independent
implementations. This part of the standard therefore defines a conformance test suite for the network and
application layer protocols in order to derive a common and agreed basis for conformance tests. The resulting
test suite is a necessary prerequisite for downstream interoperability tests. Since interoperability furthermore
involves the actual application logic of an implementation those tests are beyond the scope of this standard.
Hence this standard focuses on the interface aspects and the corresponding requirements given in part two
only.
vii
DRAFT INTERNATIONAL STANDARD ISO/DIS 15118-4:2021(E)

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 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 part of the
standard 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 Part 5 of this standard. 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 International Standard 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 standard 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 may
restrict testing even further. Hence, the purpose of this part 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 an implementation has the required capabilities and
that its behavior conforms consistently in representative instances of communication.
NOTE 2 This standard 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)

ISO/DIS 15118-4:2021(E)
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-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
IEC 61851-1:2017, Electric vehicle conductive charging system ― Part 1: General requirements (Ed 3.0, 2017)
ITU-T X.290, OSI conformance testing methodology and framework for protocol Recommendations for ITU-T
applications ― General concepts (April 1995)
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)
NOTE 1 Even though the technical specification ISO 15118-2:2014, which is the baseline for this conformance test
document, explicitly references IEC 61851-1:2011 Edition 2, this document references IEC 61851-1:2017 Edition 3 because
of applicability on the market.
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 terminological databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https://www.iso.org/obp
— IEC Electropedia: available at http://www.electropedia.org/
3.1
abstract test case
complete and independent specification of the actions required to achieve a specific test purpose
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 may involve one or more consecutive or concurrent connections.
Note 3 to entry: The specification should be 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 should be independent in the sense that it should be possible to execute the derived
executable test case in isolation from other such test cases (i.e. the specification should always include the possibility of
starting and finishing in the “idle” state).
3.2
abstract test suite
ATS
test suite composed of abstract test cases
Note 1 to entry: See ITU-T X.290.
2 © ISO 2021 – All rights reserved

ISO/DIS 15118-4:2021(E)
3.3
black box testing
method of testing that examines the behavior of an SUT without considering the internal implementation and
structure of the SUT, thus relying on the SUT's open interface for testing
3.4
conformance requirements
conformance of a real system consisting of conformance to each requirement and conformance to the set
Note 1 to entry: Set of interrelated requirements which together define the behavior of the system and its
communication. Conformance of a real system will, therefore, be expressed at two levels, conformance to each individual
requirement and conformance to the set. Applicable ISO 15118-4 conformance tests include requirements and transfer
syntax requirements as far as they can be validated by black box testing.
Note 2 to entry: See also static conformance requirements (3.4) and dynamic conformance requirements (3.6).
3.5
conforming implementation
IUT which satisfies both static and dynamic conformance requirements, consistent with the capabilities stated
in the PICS(s)
Note 1 to entry: See ITU-T X.290.
3.6
dynamic conformance requirements
one of the requirements 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 defined in ISO 15118-2.
3.7
executable test case
realization of an abstract test case
Note 1 to entry: See ITU-T X.290.
3.8
expected behavior
exact response of the SUT according to the underlying protocol specification to the stimulus defined in the test
behavior
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.
3.10
implementation extra information for testing
IXIT
statement made by a supplier or implementer of an IUT which contains or references all information (in addition
to that given in the ICS) related to the IUT and its testing environment, which will enable the test laboratory to
run an appropriate test suite against the IUT
ISO/DIS 15118-4:2021(E)
Note 1 to entry: See ITU-T X.290.
3.11
implementation under test
IUT
implementation of one or more OSI 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 and computing and assigning the test verdict
Note 1 to entry: See ITU-T X.292.
3.13
parallel test component
PTC
test component created by the main test component
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 up to the finishing stable state for the test
case
Note 1 to entry: See also test behavior (3.23).
3.15
pre-condition
test steps needed to define the path from the starting stable state of the test case up to the initial state from
which the test bevavior will start
Note 1 to entry: See also test behavior (3.23).
3.16
protocol implementation conformance statements
PICS
ICS 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.
3.17
protocol implementation extra information for testing
PIXIT
IXIT 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.
4 © ISO 2021 – All rights reserved

ISO/DIS 15118-4:2021(E)
3.18
runtime environment
an environment that describes the operating system and corresponding platform requirements of a system
EXAMPLE Test system.
3.19
semantically invalid test behavior
SemITB
test steps where the test system sends stimuli to the SUT that are semantically invalid according to the protocol
requirements
Note 1 to entry: This type of test behavior is defined in this conformance standard and explicitly includes requirements
which define the appropriate error handling of the SUT.
3.20
static conformance requirements
one of the requirements that specify 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.
3.21
system under test
SUT
real open system in which the IUT resides
Note 1 to entry: See ITU-T X.290.
3.22
syntactically invalid test behavior
SynITB
test steps where the test system sends stimuli to the SUT that are syntactically invalid according to the protocol
requirements
Note 1 to entry: This type of test behavior is not defined in this conformance standard, see codec requirements.
3.23
test behavior
set of test steps (test body) which are essential in order to achieve the test purpose and assign verdicts to the
possible outcomes
3.24
test execution
interpretation or execution of an abstract test suite
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.25
test framework
TFW
an entity to perform all actions of test cases or functions
Note 1 to entry: The Test Framework interacts with the test management (TM), SUT adaptor (SA) and platform adaptor
(PA) entities via test control interface (TCI) and test runtime interface (TRI) and additionally manages the executable test
suite (ETS) and encoding/decoding system (EDS) entities. It initializes adaptors as well as ETS and EDS entities. This entity
ISO/DIS 15118-4:2021(E)
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 TM entity for module parameter values required by the ETS and sends logging information to it. It also collects
and resolves associated verdicts returned by the ETS 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 dystem (T3RTS) is used to explain a test
framework functionality.
3.26
test purpose
prose description of a well-defined objective of testing, focusing on a single conformance requirement or a set
of related conformance requirements 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.27
test system
real system combining the test framework, abstract test suite, test execution and adapters as well as codecs
Note 1 to entry: Typically also containing a common runtime environment based on an operating system
3.28
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.29
test runtime interface
TRI
two interfaces that define the interaction of the TTCN-3 executable between the SUT and the platform adapter
(PA) and the system adapter (SA) in a test system
Note 1 to entry: See ETSI ES 201 873-6 V4.6.1.
3.30
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.31
valid test behavior
VTB
test steps where the test system sends stimuli to the SUT that are valid (syntactically and semantically)
according to the protocol requirements
Note 1 to entry: This type of test behavior is defined in this conformance standard.
Note 2 to entry: The protocol requirements for this conformance specification are defined in ISO 15118-2.
6 © ISO 2021 – All rights reserved

ISO/DIS 15118-4:2021(E)
3.32
verdict
test verdict
statement of “pass”, “fail” or “inconclusive”, as specified in an abstract test case, concerning conformance of an
IUT with respect to that test case when it is executed
Note 1 to entry: See ITU-T X.290.
4 Symbols (and 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
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 Dis
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.