ISO/TR 16401-1:2018

TECHNICAL ISO/TR
REPORT 16401-1
First edition
2018-01
Electronic fee collection — Evaluation
of equipment for conformity to ISO/TS
17575-2 —
Part 1:
Test suite structure and test purposes
Perception du télépéage — Évaluation de conformité de l'équipement
à l'ISO/TS 17575-2 —
Partie 1: Structure de la suite d'essais et objectifs d'essai
Reference number
©
ISO 2018
© ISO 2018, Published in Switzerland
All rights reserved. Unless otherwise specified, 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
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org
www.iso.org
ii © ISO 2018 – All rights reserved

Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms . 4
5 Test Suite Structure . 5
5.1 Structure . 5
5.2 Reference to conformance test specifications . 5
5.3 Test purposes (TP) . 5
5.3.1 TP definition conventions . 5
5.3.2 TP naming conventions . 6
5.4 Protocol Conformance Test Report (PCTR). 7
Annex A (informative) Test purposes (TP) for Front End Communications API.8
Annex B (informative) Test purposes (TP) for Front End Application .137
Annex C (informative) PCTR proforma for Front End Communications API .141
Annex D (informative) PCTR proforma for Front End Application .148
Bibliography .152
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 on 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 the following
URL: www.iso.org/iso/foreword.html.
This document was prepared by Technical Committee ISO/TC 204, Intelligent transport systems.
This edition of ISO/TR 16401-1 cancels and replaces ISO/TS 16401-1:2012, which has been technically
revised.
The main changes compared to the previous edition are as follows:
— the document has been converted from a Technical Specification to a Technical Report;
— the terms and definitions have been revised;
— the test purpose naming convention has been changed, i.e. “/” has been replaced by “_”;
— editorial corrections, as well as changes to improve readability have been made.
A list of all parts in the ISO/TR 16401 series can be found on the ISO website.
iv © ISO 2018 – All rights reserved

Introduction
This document is part of a set of standards that supports interoperability of autonomous electronic fee
collection (EFC) systems. Autonomous systems use satellite positioning, often combined with additional
sensor technologies such as gyroscopes, odometers and accelerometers, to localize the vehicle and to
find its position on a map containing the charged geographic objects, such as charged roads or charged
areas. From the charged objects, the vehicle characteristics, the time of day and other data that are
relevant for describing road use, the tariff and ultimately, the road usage fee is determined.
The ISO/TR 16401 series provides tests to assess the Front End Communications API and Front End
Application behaviours compliancy towards the requirements listed in ISO 17575-2. This document
contains the definition of such tests in the form of test purposes, listing the initial conditions, references
and individual steps in a structured textual manner. ISO/TR 16401-2 contains the identical tests
written in Testing and Test Control Notation version 3 (TTCN v3).
Autonomous on-board equipment (OBE) operates without relying on dedicated roadside infrastructure
by employing wide-area technologies such as Global Navigation Satellite Systems (GNSS) and Cellular
Communications Networks (CN). Therefore, autonomous systems can also be referred to as GNSS/CN
systems.
ISO/TR 16401-1 is based on
— ISO 17575-2, and
— the ISO 9646 family of standards on conformance test methodology.
TECHNICAL REPORT ISO/TR 16401-1:2018(E)
Electronic fee collection — Evaluation of equipment for
conformity to ISO/TS 17575-2 —
Part 1:
Test suite structure and test purposes
1 Scope
This document covers the test purposes for Front End Communications API covering functionalities
related to instance handling, session handling, communication service primitives (i.e.
sending/receiving of ADUs) and visible state transitions. It covers EFC communication services
described in ISO 17575-2:2016, Clause 5 and PICS proforma in ISO 17575-2:2016, B.2. Claims related to
Front End storage capacity are out of scope of this document.
This document covers the test purposes for Front End Application related to session establishment on
Back End request and related to session re-establishment when session requested by Back End failed.
There are no other claims with respect to Front End Application described in ISO 17575-2.
The underlying communication technology requirements for layer 1 to 4 specified in ISO 17575-2:2016,
Clause 6 are out of scope of this document.
Similarly, Back End Communications API is out of scope of this document. According to ISO 17575-2
it is expected that these Front End Communications API will be “reflected” in the BE; however, BE
Communications API is out of scope of ISO 17575-2.
Test purposes have been organized into the test suite groups, designated for the Front End
Communications API and Front End Application, respectively.
Aside from the test purposes, this document also provides proforma conformance test reports
templates for both the Front End and Back End test purposes.
ISO 17575-2 contains more information regarding the requirements against which the conformance is
evaluated in this document.
2 Normative references
There are no normative references in this document.
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
— IEC Electropedia: available at https://www.electropedia.org/
— ISO Online browsing platform: available at https://www.iso.org/obp
3.1
area charging
charging based on road usage within a given area
[SOURCE: ISO 17575-1:2016, 3.1]
3.2
attribute
addressable package of data consisting of a single data element (3.9)or structured sequences of data
elements
[SOURCE: ISO 17575-1:2016, 3.2]
3.3
authenticator
data, possibly encrypted, that is used for authentication
[SOURCE: EN 15509:2014, 3.3]
3.4
Back End
part of a back office system interfacing to one or more Front Ends (3.11)
[SOURCE: ISO 17575-1:2016, 3.4]
3.5
charge object
geographic or road related object for the use of which a charge is applied
[SOURCE: ISO 17575-1:2016, 3.5]
3.6
charge report
information containing road usage and related information originated at the Front End (3.11)
[SOURCE: ISO 17575-1:2016, 3.6]
3.7
cordon
border line of an area
[SOURCE: ISO 17575-1:2016, 3.7]
3.8
cordon charging
charging for the crossing of a cordon (3.7)
[SOURCE: ISO 17575-1:2016, 3.8]
3.9
data element
coded information, which might itself consist of lower level information structures
[SOURCE: ISO 17575-1:2016, 3.9]
3.10
data set
logical set of data elements (3.9) with a semantic relation
[SOURCE: ISO 17575-3:2016, 3.10]
3.11
Front End
part of a tolling system consisting of an OBE (3.14) and possibly a proxy (3.15) where road tolling
information and usage data are collected and processed for delivery to the Back End (3.4)
[SOURCE: ISO/TS 19299:2015, 3.17]
2 © ISO 2018 – All rights reserved

3.12
Front End Application
part of the Front End (3.11) above the API
[SOURCE: ISO 17575-2:2016, 3.12]
3.13
layout
technical description of the location of tolled objects including their borders
[SOURCE: ISO 17575-3:2016, 3.12]
3.14
on-board equipment
OBE
all required equipment on-board a vehicle for performing required EFC functions and communication
services
3.15
proxy
optional part of a Front End (3.11) that communicates with external equipment and processes the data
received into an agreed format to be delivered to the Back End (3.4)
[SOURCE: ISO 17575-1:2016, 3.13]
3.16
road section charging
tolling principle where the fee is due if predefined sections of roads are used
[SOURCE: ISO 17575-1:2016, 3.14]
3.17
toll
charge, tax or duty levied in connection to using a vehicle in a toll domain (3.21)
[SOURCE: ISO/TS 19299:2015, 3.42 modified]
3.18
tolled area
geographic area where a toll (3.17) is charged for road usage
[SOURCE: ISO 17575-3:2016, 3.17]
3.19
toll context
logical view as defined by attributes (3.2) and functions of the basic elements of a toll scheme consisting
of a single basic tolling principle, a spatial distribution of the charge objects (3.5) and a single behaviour
of the related Front End (3.11)
[SOURCE: ISO 17575-1:2016, 3.17]
3.20
toll context data
information defined by the responsible Toll Charger necessary to establish the toll (3.17) due for using a
vehicle on a particular toll context (3.19) and to conclude the toll transaction
[SOURCE: ISO 12855:2015, 3.15]
3.21
toll domain
area or part of a road network where a certain toll regime (3.22) is applied
[SOURCE: ISO 17573:2010, 3.18]
3.22
toll regime
set of rules, including enforcement rules, governing the collection of toll (3.17) in a toll domain (3.21)
[SOURCE: ISO 17573:2010, 3.20]
3.23
toll scheme
organizational view of a toll regime (3.22), including the actors and their relationships
[SOURCE: ISO 17575-3:2016, 3.22]
3.24
transaction
whole of the exchange of information between two physically separated communication facil
...