oSIST prEN ISO 15118-9:2023

SLOVENSKI STANDARD
oSIST prEN ISO 15118-9:2023
01-september-2023
Cestna vozila - Komunikacijski vmesnik med vozilom in omrežjem - 9. del: Preskus
skladnosti fizične in podatkovne povezovalne plasti za brezžično komunikacijsko
omrežje (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-9:2022)
Straßenfahrzeuge - Kommunikationsschnittstelle zwischen Fahrzeug und Ladestation -
Teil 9: Konformitätsprüfungen für die Bitübertragungs- und Sicherungsschicht für
drahtlose Kommunikation (ISO 15118-9:2022)
Véhicules routiers - Interface de communication entre véhicule et réseau électrique -
Partie 9: Essai de conformité relatif à la couche physique et à la couche liaison de
données pour la communication sans-fil (ISO 15118-9:2022)
Ta slovenski standard je istoveten z: prEN ISO 15118-9
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
oSIST prEN ISO 15118-9:2023 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------
oSIST prEN ISO 15118-9:2023

---------------------- Page: 2 ----------------------
oSIST prEN ISO 15118-9:2023
INTERNATIONAL ISO
STANDARD 15118-9
First edition
2022-11
Road vehicles — Vehicle to grid
communication interface —
Part 9:
Physical and data link layer
conformance test for wireless
communication
Véhicules routiers — Interface de communication entre véhicule et
réseau électrique —
Partie 9: Essai de conformité relatif à la couche physique et à la
couche liaison de données pour la communication sans-fil
Reference number
ISO 15118-9:2022(E)
© ISO 2022

---------------------- Page: 3 ----------------------
oSIST prEN ISO 15118-9:2023
ISO 15118-9:2022(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO 2022
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
  © ISO 2022 – All rights reserved

---------------------- Page: 4 ----------------------
oSIST prEN ISO 15118-9:2023
ISO 15118-9:2022(E)
Contents Page
Foreword .iv
Introduction .v
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 description . . 8
6 Test architecture reference model . 8
6.1 General information. 8
6.2 Platform adapter interface . 8
6.3 SUT adapter interfaces . 9
6.4 Codecs . . 9
7 Test suite conventions.10
7.1 General information. 10
7.2 Test suite structure (TSS) . 10
7.3 Test profiles . 11
7.3.1 Test configurations .12
7.3.2 Components and ports .12
7.3.3 Protocol implementation conformance statement (PICS) definition . 14
7.3.4 Protocol implementation extra information for testing (PIXIT) definition . 14
7.3.5 Test control . 15
7.4 Test suite identifiers . 15
7.4.1 Module identifiers .15
7.4.2 Test case identifiers . 16
7.4.3 Template identifiers . 16
7.4.4 Function identifiers . 17
7.4.5 Timer identifiers . 18
7.4.6 PICS/PIXIT identifiers . 18
7.4.7 Verdict identifiers . 19
7.5 Test suite coverage . 19
7.6 Test case description .22
8 Test case descriptions for ISO 15118-8 requirements .23
8.1 General information.23
8.2 SECC test cases . 23
8.3 EVCC test cases . 43
Bibliography .72
iii
© ISO 2022 – All rights reserved

---------------------- Page: 5 ----------------------
oSIST prEN ISO 15118-9:2023
ISO 15118-9:2022(E)
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).
Attention is drawn to the possibility that some of the elements of this document may be the subject
of patent rights. ISO and IEC 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) or the IEC
list of patent declarations received (see https://patents.iec.ch).
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.
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 and
www.iec.ch/national-committees.
iv
  © ISO 2022 – All rights reserved

---------------------- Page: 6 ----------------------
oSIST prEN ISO 15118-9:2023
ISO 15118-9:2022(E)
Introduction
Resulting from the wireless physical and data link layer requirements defined in ISO 15118-8, a
corresponding set of abstract test cases is necessary to verify the conformance of implementations.
This document, therefore, defines a conformance test suite for the wireless physical and data link layer
protocols in order 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.
Hence, this document focuses on the interface aspects and the corresponding requirements given in
ISO 15118-8 only.
v
© ISO 2022 – All rights reserved

---------------------- Page: 7 ----------------------
oSIST prEN ISO 15118-9:2023

---------------------- Page: 8 ----------------------
oSIST prEN ISO 15118-9:2023
INTERNATIONAL STANDARD ISO 15118-9:2022(E)
Road vehicles — Vehicle to grid communication
interface —
Part 9:
Physical and data link layer conformance test for wireless
communication
1 Scope
This document specifies conformance tests in the form of an abstract test suite (ATS) for a system under
test (SUT) implementing an electric-vehicle or supply-equipment communication controller (EVCC or
SECC) with support for WLAN-based high-level communication (HLC) according to ISO 15118-8 and
against the background of ISO 15118-1. 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-8 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 defined in ISO 15118-8. The behaviour tests of the ATS
examine an implementation as thoroughly as practical over the full range of dynamic conformance
requirements defined in ISO 15118-8 and within the capabilities of the SUT (see NOTE below).
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 for the
ISO/OSI physical and data link layers (layers 1 and 2).
In terms of coverage, this document only covers normative sections and requirements in ISO 15118-8.
This document can additionally refer to specific tests for requirements on referenced standards (e.g.
IEEE, or industry consortia standards, like WiFi Alliance) as long as they are relevant in terms of
conformance for implementations according to ISO 15118-8. 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-8. 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 abstract test cases defined in this document only
consider the communication protocol and the system's behaviour defined ISO 15118-8. The power flow
between the EVSE and the EV is not considered.
NOTE 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. Instead, it gives
confidence that an implementation has the required capabilities and that its behaviour conforms consistently in
representative instances of communication.
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.
1
© ISO 2022 – All rights reserved

---------------------- Page: 9 ----------------------
oSIST prEN ISO 15118-9:2023
ISO 15118-9:2022(E)
ISO 15118-1, Road vehicles — Vehicle to grid communication interface — Part 1: General information and
use-case definition
ISO 15118-2, Road vehicles — Vehicle-to-Grid Communication Interface — Part 2: Network and application
protocol requirements
ISO 15118-8:2020, Road vehicles — Vehicle to grid communication interface — Part 8: Physical layer and
data link layer requirements for wireless communication
ISO 15118-20, Road vehicles — Vehicle to grid communication interface — Part 20: 2nd generation network
layer and application layer requirements
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)
IEEE 802.11-2012, IEEE Standard for Information technology — Telecommunications and information
exchange between systems — Local and metropolitan area networks — specific requirements: Part 11:
Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 15118-1, ISO 15118-2,
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),
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 optionally involves one or more consecutive or concurrent
connections
Note 1 to entry: The specification should be 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 2 to entry: The specification should be independent in the sense that it should be possible to execute the
derived executable test case (3.7) in isolation from other such test cases (i.e. the specification should always
include the possibility of starting and finishing in the 'idle' state).
[SOURCE: ITU-T X.290:1995, 3.3.3].
3.2
ATS
abstract test suite
test suite composed of abstract test cases (3.1)
[SOURCE: ITU-T X.290:1995, 3.3.6]
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.
2
  © ISO 2022 – All rights reserved

---------------------- Page: 10 ----------------------
oSIST prEN ISO 15118-9:2023
ISO 15118-9:2022(E)
3.3
APUT
access point under test
ISO/OSI layer 1 and 2 component of the SECC [system under test (SUT) (3.19)] for establishing a wireless
communication connection
3.4
black box test
method of testing that examines the behaviour of a system under test (SUT) (3.19) without considering
the internal implementation and structure of the SUT, thus relying on the SUT's open interface for
testing
3.5
conformance requirement
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 behaviour 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 conformance tests defined in this document,
include requirements and transfer syntax requirements as far as they can be validated by black box tests (3.4).
Note 2 to entry: See also static conformance requirement (3.17) and dynamic conformance requirement (3.6).
3.6
dynamic conformance requirement
one of the requirements which specifies what observable behaviour is permitted by the relevant
specification(s) in instances of communication
Note 1 to entry: The requirements for this conformance specification are defined in ISO 15118-8.
[SOURCE: ITU-T X.290:1995, 3.3.29, modified — Note 1 to entry has been added.]
3.7
executable test case
realization of an abstract test case (3.1)
[SOURCE: ITU-T X.290:1995, 3.3.31]
3.8
expected behaviour
exact response of the system under test (SUT) (3.19) according to the underlying protocol specification
to the stimulus defined in the test behaviour (3.20)
3.9
ICS
implementation conformance statement
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: The given specification for this conformance specification is ISO 15118-8.
[SOURCE: ITU-T X.290:1995, 3.3.39, modified — "The ICS can take several forms: protocol ICS, profile
ICS, profile specific ICS, and information object ICS." has been removed from the definition and Note 1
to entry has been added.]
3
© ISO 2022 – All rights reserved

---------------------- Page: 11 ----------------------
oSIST prEN ISO 15118-9:2023
ISO 15118-9:2022(E)
3.10
IXIT
implementation extra information for testing
statement made by a supplier or implementer of a system under test (SUT) (3.19) which contains or
references all of the information [in addition to that given in the implementation conformance statement
(ICS) (3.9)] related to the SUT and its testing environment, which will enable the test laboratory to run
an appropriate test suite against the SUT
[SOURCE: ITU-T X.290:1995, 3.3.41, modified — "An IXIT can take several forms: protocol IXIT, profile
IXIT, profile specific IXIT, and information object IXIT, TMP implementation statement." removed from
the defintiion and IUT replaced by SUT.]
3.11
MTC
main test component
single test component (3.21) in a test component configuration responsible for creating and controlling
parallel test components (3.12) and computing and assigning the test verdict (3.29)
[SOURCE: ITU-T X.292:2002, 3.6.43]
3.12
parallel test component
PTC
test component (3.21) created by the main test component (3.11)
[SOURCE: ITU-T X.292:2002, 3.6.53]
3.13
post-condition
test steps needed to define the path from the end of the test behaviour (3.20) up to the finishing stable
state for the test case
3.14
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 bevaviour (3.20) will start
3.15
PICS
protocol implementation conformance statement
implementation conformance statement (ICS) (3.9) for an implementation or system claimed to conform
to a given protocol specification
Note 1 to entry: The given protocol specification for this conformance specification is ISO 15118-8.
[SOURCE: ITU-T X.290:1995, 3.3.80, modified — Note 1 to entry has been added.]
3.16
PIXIT
protocol implementation extra information for testing
implementation extra information for testing (IXIT) (3.10) related to testing for conformance to a given
protocol specification
Note 1 to entry: The given protocol specification for this conformance specification is ISO 15118-8.
[SOURCE: ITU-T X.290:1995, 3.3.81, modified — Note 1 to entry has been added.]
4
  © ISO 2022 – All rights reserved

---------------------- Page: 12 ----------------------
oSIST prEN ISO 15118-9:2023
ISO 15118-9:2022(E)
3.17
static conformance requirement
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)
[SOURCE: ITU-T X.290:1995, 3.3.95]
3.18
STAUT
station under test
ISO/OSI layer 1 and 2 component of the EVCC [system under test (SUT) (3.19)] for establishing a wireless
communication connection
3.19
SUT
system under test
real open system in which the implementation of one or more OSI protocols in an adjacent user/provider
relationship are to be studied by testing.
Note 1 to entry: Adapted from ITU-T X.290:1995, 3.3.103 and 3.3.43.
3.20
test behaviour
set of test steps (test body) which are essential in order to achieve the test purpose (3.25) and assign
verdicts to the possible outcomes
3.21
test component
named subdivision of a concurrent test case capable of being executed in parallel and declared as having
a fixed number of points of control and observation and a fixed or maximal number of co-ordination
points
[SOURCE: ITU-T X.292:2002, 3.6.72, modified — "in parallel with other test components" has been
replaced by "in parallel".]
3.22
TCI
TTCN-3 control interfaces
four interfaces that define the interaction of the TTCN-3 Executable with the test management, the
coding and decoding, the test component (3.21) handling and the logging in a test system (3.27)
[SOURCE: ETSI ES 201 873-6 V4.13.1:2022, 3.1]
3.23
test execution
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.
3.24
test framework
entity to perform all actions of test cases or functions
Note 1 to entry: The test framework interacts with the test management, system under test (SUT) (3.19) adaptor
and platform adaptor entities via TTCN-3 control interfaces (TCI) (3.22) and test runtime interface (TRI) (3.26)
and additionally manages the executable test suite and encoding/decoding system entities. It initializes adaptors
as well as 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 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.
5
© ISO 2022 – All rights reserved

---------------------- Page: 13 ----------------------
oSIST prEN ISO 15118-9:2023
ISO 15118-9:2022(E)
Note 2 to entry: In this document, the 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 conformance requirement
(3.5) or a set of related conformance requirements as specified in the appropriate OSI specification
EXAMPLE Verifying the support of a specific value of a specific parameter.
[SOURCE: ITU-T X.290:1995, 3.3.118]
3.26
TRI
test runtime interface
two interfaces that define the interaction of the TTCN-3 executable between the system under test (SUT)
(3.19) and the platform adapter (PA) and the system adapter (SA) in a test system (3.27)
[SOURCE: ETSI ES 201 873-5 V4.9.1:2022, 3.1, modified — The term was originally TTCN-3 runtime
interface.]
3.27
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: Typically, also containing a common runtime environment based on an operating system.
3.28
TSI
test system interface
test component (3.21) that provides a mapping of the ports available in the (abstract) TTCN-3 test system
(3.27) to those offered by a real test system
[SOURCE: ETSI ES 201 873-5 V4.9.1:2022, 3.1]
3.29
test verdict
statement of 'pass', 'fail' or 'inconclusive', as specified in an abstract test case (3.1), concerning
conformance of a system under test (SUT) (3.19) with respect to that test case when it is executed
[SOURCE: ITU-T X.290:1995, 3.3.124, modified — IUT was replaced by SUT.]
4 Abbreviated terms
For the purposes of this document, the following abbreviated terms apply:
AP (wireless) access point
APU
...