SIST EN ISO 14906:2023
(Main)Electronic fee collection - Application interface definition for dedicated short-range communication (ISO 14906:2022)
Electronic fee collection - Application interface definition for dedicated short-range communication (ISO 14906:2022)
This document specifies the application interface in the context of electronic fee collection (EFC) systems using dedicated short-range communication (DSRC).
The EFC application interface is the EFC application process interface to the DSRC application layer, as can be seen in Figure 1. This document comprises specifications of:
— EFC attributes (i.e. EFC application information) that can also be used for other applications and/or interfaces;
— the addressing procedures of EFC attributes and (hardware) components (e.g. integrated circuit(s) card);
— EFC application functions, i.e. further qualification of actions by definitions of the concerned services, assignment of associated ActionType values, and content and meaning of action parameters;
— the EFC transaction model, which defines the common elements and steps of any EFC transaction;
— the behaviour of the interface so as to ensure interoperability on an EFC-DSRC application interface level.
This is an interface standard, adhering to the open systems interconnection (OSI) philosophy (see ISO/IEC 7498-1), and it is as such not primarily concerned with the implementation choices to be realized at either side of the interface.
This document provides security-specific functionality as place holders (data and functions) to enable the implementation of secure EFC transactions. Yet the specification of the security policy (including specific security algorithms and key management) remains at the discretion and under the control of the EFC operator, and hence is outside the scope of this document.
Elektronische Gebührenerhebung - Anwendungsschnittstelle zur dezidierten Nahbereich- Kommunikation (ISO 14906:2022)
Perception du télépéage - Définition de l'interface d'application relative aux communications dédiées à courte portée (ISO 14906:2022)
Le présent document spécifie l'interface d'application dans le contexte des installations de perception du télépéage (EFC) utilisant des communications dédiées à courte portée (DSRC).
Cette interface d’application EFC est l’interface du processus d’application EFC avec la couche applicative DSRC, comme le montre la Figure 1 ci-dessous. Le présent document spécifie les éléments suivants:
— les attributs EFC (c’est-à-dire les informations sur l’application EFC) pouvant également être utilisés pour d’autres applications et/ou interfaces;
— les procédures d’adressage des attributs EFC et des composants (matériels) (par exemple, carte à circuits intégrés);
— les fonctions de l’application EFC, c’est-à-dire la qualification ultérieure des actions par la définition des services concernés, l’attribution des valeurs ActionType associées ainsi que le contenu et la signification des paramètres des actions;
— le modèle de transaction EFC, qui définit les éléments et les étapes que toutes les transactions ont en commun;
— le comportement de l’interface qui doit assurer l’interopérabilité à un niveau donné d’interface d’application EFC-DSRC.
Il s’agit d’une interface normalisée répondant à la philosophie de l’interconnexion des systèmes ouverts (OSI) (voir ISO/IEC 7498-1) et qui, en tant que telle, ne dépend pas essentiellement des choix de mise en œuvre réalisés de part et d’autre de l’interface.
Le présent document définit en termes de paramètres fictifs (données et fonctions) la fonctionnalité spécifique permettant d'assurer la sécurité de mise en œuvre des transactions EFC. La spécification de la politique de sécurité (y compris les algorithmes de sécurité particuliers et la gestion des clés) demeure toutefois de la responsabilité de l'opérateur EFC et ne relève donc pas du domaine d'application du présent document.
Elektronsko pobiranje pristojbin - Definicija aplikacijskega vmesnika za posebne komunikacije kratkega dosega (ISO 14906:2022)
Ta dokument določa aplikacijski vmesnik v okviru sistemov za elektronsko pobiranje pristojbin (EFC), ki uporabljajo namensko komunikacijo kratkega dosega (DSRC).
Aplikacijski vmesnik za elektronsko pobiranje pristojbin je aplikacijski postopkovni vmesnik za aplikacijsko raven namenske komunikacije kratkega dosega, kot je prikazano na sliki 1. Ta dokument zajema specifikacije za:
– atribute elektronskega pobiranja pristojbin (tj. informacije sistema elektronskega pobiranja cestnin), ki jih je mogoče uporabiti tudi za druge aplikacije, in/ali vmesnike;
– obravnavane postopke atributov sistema elektronskega pobiranja cestnin in sestavnih delov (strojne opreme) (npr. kartice z integriranim vezjem;
– funkcije sistema elektronskega pobiranja pristojbin, tj. nadaljnja kvalifikacija dejanj z definicijami obravnavanih storitev, dodelitev povezanih vrednosti »ActionType« ter vsebina in pomen parametrov dejanj;
– model transakcije elektronskega pobiranja pristojbin, ki določa skupne elemente in korake katere koli transakcije elektronskega pobiranja pristojbin;
– delovanje vmesnika za zagotavljanje interoperabilnosti na ravni aplikacijskega vmesnika za EFC-DSRC.
To je vmesniški standard, ki se ravna po načelu povezanih odprtih sistemov (OSI) (glej ISO/IEC 7498-1) in kot tak ni primarno povezan z načini izvajanja, ki jih je treba udejanjiti na obeh straneh vmesnika.
Ta dokument zagotavlja varnostno specifično funkcijo označbe mesta (podatki in funkcije), kar omogoča izvajanje varnih transakcij elektronskega pobiranja pristojbin. Vendar pa specifikacija varnostne politike (vključno s specifičnimi varnostnimi algoritmi in upravljanjem ključev) ostaja v presoji in pod nadzorom upravljavca elektronskega pobiranja pristojbin in zato ne spada na področje uporabe tega dokumenta.
General Information
Relations
Standards Content (Sample)
SLOVENSKI STANDARD
01-maj-2023
Nadomešča:
SIST EN ISO 14906:2019
SIST EN ISO 14906:2019/A1:2020
Elektronsko pobiranje pristojbin - Definicija aplikacijskega vmesnika za posebne
komunikacije kratkega dosega (ISO 14906:2022)
Electronic fee collection - Application interface definition for dedicated short-range
communication (ISO 14906:2022)
Elektronische Gebührenerhebung - Anwendungsschnittstelle zur dezidierten
Nahbereich- Kommunikation (ISO 14906:2022)
Perception du télépéage - Définition de l'interface d'application relative aux
communications dédiées à courte portée (ISO 14906:2022)
Ta slovenski standard je istoveten z: EN ISO 14906:2023
ICS:
03.220.20 Cestni transport Road transport
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
EN ISO 14906
EUROPEAN STANDARD
NORME EUROPÉENNE
January 2023
EUROPÄISCHE NORM
ICS 03.220.20; 35.240.60 Supersedes EN ISO 14906:2018, EN ISO
14906:2018/A1:2020
English Version
Electronic fee collection - Application interface definition
for dedicated short-range communication (ISO
14906:2022)
Perception de télépéage - Définition de l'interface Elektronische Gebührenerhebung -
d'application relative aux communications dédiées à Anwendungsschnittstelle zur dezidierten Nahbereich-
courte portée (ISO 14906:2022) Kommunikation (ISO 14906:2022)
This European Standard was approved by CEN on 28 October 2022.
CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this
European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references
concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN
member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by
translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC Management
Centre has the same status as the official versions.
CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway,
Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Türkiye and
United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION
EUROPÄISCHES KOMITEE FÜR NORMUNG
CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2023 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN ISO 14906:2023 E
worldwide for CEN national Members.
Contents Page
European foreword . 3
European foreword
This document (EN ISO 14906:2023) has been prepared by Technical Committee ISO/TC 204
"Intelligent transport systems" in collaboration with Technical Committee CEN/TC 278 “Intelligent
transport systems” the secretariat of which is held by NEN.
This European Standard shall be given the status of a national standard, either by publication of an
identical text or by endorsement, at the latest by July 2023, and conflicting national standards shall be
withdrawn at the latest by July 2023.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CEN shall not be held responsible for identifying any or all such patent rights.
This document supersedes EN ISO 14906:2018, EN ISO 14906:2018/A1:2020.
Any feedback and questions on this document should be directed to the users’ national standards
body/national committee. A complete listing of these bodies can be found on the CEN website.
According to the CEN-CENELEC Internal Regulations, the national standards organizations of the
following countries are bound to implement this European Standard: Austria, Belgium, Bulgaria,
Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland,
Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Republic of
North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Türkiye and the
United Kingdom.
Endorsement notice
The text of ISO 14906:2022 has been approved by CEN as EN ISO 14906:2023 without any modification.
INTERNATIONAL ISO
STANDARD 14906
Fourth edition
2022-12
Electronic fee collection — Application
interface definition for dedicated
short-range communication
Perception de télépéage — Définition de l'interface d'application
relative aux communications dédiées à courte portée
Reference number
ISO 14906:2022(E)
ISO 14906:2022(E)
© 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 14906:2022(E)
Contents Page
Foreword .v
Introduction . vi
1 Scope . 1
2 Normative references . 2
3 Terms and definitions . 2
4 Abbreviated terms . 4
5 EFC application interface architecture . 6
5.1 Relation to the DSRC communication architecture . 6
5.2 Usage of DSRC application layer by the EFC application interface . 8
5.3 Addressing of EFC attributes . 8
5.3.1 Basic mechanism . 8
5.3.2 Role of the Element Identifier (EID) . 9
5.3.3 Multiple instances of Attributes . 9
5.4 Addressing of components . 10
6 EFC transaction model .11
6.1 General . 11
6.2 Initialisation phase . 11
6.2.1 Overview . 11
6.2.2 EFC application-specific contents of the BST .12
6.2.3 EFC application-specific contents of the VST .13
6.3 Transaction phase. 14
7 EFC functions .15
7.1 Overview and general concepts .15
7.1.1 EFC functions and service primitives . 15
7.1.2 Overview of EFC functions . 16
7.1.3 Handling of multiple instances . 17
7.1.4 Security . . . 19
7.2 EFC functions . 22
7.2.1 General .22
7.2.2 GET_STAMPED . 22
7.2.3 SET_STAMPED .23
7.2.4 GET_SECURE . 24
7.2.5 SET_SECURE .25
7.2.6 GET_INSTANCE .25
7.2.7 SET_INSTANCE .26
7.2.8 GET_NONCE . 27
7.2.9 SET_NONCE .28
7.2.10 TRANSFER_CHANNEL .28
7.2.11 COPY .29
7.2.12 SET_MMI . 30
7.2.13 SUBTRACT .30
7.2.14 ADD . . 31
7.2.15 DEBIT . 32
7.2.16 CREDIT . 33
7.2.17 ECHO.34
8 EFC Attributes .34
8.1 General .34
8.2 Data group contract .36
8.3 Data group receipt . 39
8.4 Data group vehicle . 45
8.5 Data group equipment .50
iii
ISO 14906:2022(E)
8.6 Data group driver . 52
8.7 Data group payment .54
Annex A (normative) EFC data type specifications .56
Annex B (informative) CARDME transaction .57
Annex C (informative) Examples of EFC transaction types .89
Annex D (informative) Mapping table from LatinAlphabetNo2, LatinCyrillicAlphabet,
LatinGreekAlphabet and LatinAlphabetNo10 to LatinAlphabetNo1 . 101
Annex E (informative) Mapping table between EFC Vehicledata attribute and European
registration certificate . . 102
Annex F (normative) Security calculations for DES . 105
Annex G (informative) Security computation examples for DES . 111
Annex H (normative) Security calculations for AES .114
Annex I (informative) Security computation examples for AES .119
Bibliography . 121
iv
ISO 14906:2022(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 204, Intelligent transport systems, in
collaboration with the European Committee for Standardization (CEN) Technical Committee CEN/TC
278, Intelligent Transport Systems, in accordance with the Agreement on technical cooperation between
ISO and CEN (Vienna Agreement).
This fourth edition cancels and replaces the third edition (ISO 14906:2018), which has been technically
revised. It also incorporates the Amendment ISO 14906:2018/Amd 1:2020.
The main changes are as follows:
— updating of terms and definitions, including reference to ISO/TS 17573-2 as the primary source;
1)
— updating of data definitions, including reference to ISO 17573-3:— as the primary source;
— addition of a second level of the version identifier (i.e. minor version) of the abstract syntax notation
one (ASN.1) module to provide enhanced support to standards that import data types from this
document;
— introduction of use of imported ASN.1 types with successors (i.e. including all future minor versions).
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.
1) Under preparation. Stage at the time of publication: ISO/DIS 17573-3:2022.
v
ISO 14906:2022(E)
Introduction
This document specifies an application interface for electronic fee collection (EFC) systems, which
is based on dedicated short-range communication (DSRC). It supports interoperability between EFC
systems on an EFC-DSRC application interface level. This document is intended for DSRC charging
applications, but specifically the definition of EFC data elements is valid beyond the use of a DSRC
charging interface and can potentially be used for other DSRC applications (e.g. compliance checking
communication) and/or on other interfaces (e.g. the application interface of autonomous systems).
This document provides specifications for the EFC transaction model, EFC data elements (referred to
as attributes) and functions, from which an EFC transaction can be built. The EFC transaction model
provides a mechanism that allows the handling of different versions of EFC transactions and associated
contracts. A certain EFC transaction supports a certain set of EFC attributes and EFC functions as
defined in this document. It is not envisaged that the complete set of EFC attributes and functions be
present in each piece of EFC equipment, on-board equipment (OBE) or roadside equipment (RSE).
This document provides the basis for agreements between operators, which are needed to achieve
interoperability. Based on the tools specified in this document, interoperability can be reached by
operators recognizing each others' EFC transactions (including the exchange of security algorithms and
keys) and implementing the EFC transactions in each others' RSE, or they can reach an agreement to
define a new transaction (and contract) that is common to both. Considerations should also be made by
each operator so that the RSE has sufficient resources to implement such additional EFC transactions.
In order to achieve interoperability, operators should agree on issues such as:
— which optional features are actually being implemented and used;
— access rights and ownership of EFC application data in the OBE;
— security policy (including encryption algorithms and key management, if applicable);
— operational issues, such as how many receipts may be stored for privacy reasons, how many receipts
are necessary for operational reasons (for example as entry tickets or as proof of payment);
— the agreements needed between operators in order to regulate the handling of different EFC
transactions.
In this edition of this document, users are faced with issues related to backward compatibility. Such
issues can be managed by using the following:
— EfcModule ASN.1 module, including a version number;
— EfcContextMark (incl. the ContextVersion), denoting the implementation version; this provides a
means to ensure co-existence of different implementation versions by means of a look-up table
and associated appropriate transaction processing. This will enable the software of the RSE to
determine the version of the OBE and its capability to accept the new features introduced by this
edition of ISO 14906.
This application interface definition can also be used with other DSRC media which do not use layer 7
according to ISO 15628/EN 12834. Any DSRC medium which provides services to read and write data,
to initialise communication and to perform actions is suitable to be used as a basis for this application
interface. Adaptations are medium-specific and are not further covered here. As Annex B provides a
detailed description of a transaction for central account systems, this document can also be used for
on-board account systems, in conjunction with ISO 25110, which provides examples of systems based
on on-board accounts.
This document also includes:
— Annex A, which provides the normative ASN.1 data type specifications (EFC action parameters and
attributes);
vi
ISO 14906:2022(E)
— Annex B, which presents an example of a transaction based on the CARDME specification, including
bit-level specification;
— Annex C, which presents examples of EFC transaction types, using the specified EFC functions and
attributes;
— Annex D, which presents a mapping table from LatinAlphabetNo2 & 5 to LatinAlphabetNo1 to
facilitate for a service provider the use of LatinAlphabetNo1 to encode an OBE for data available
written with non-Latin1 characters;
— Annex E, which presents a mapping table between EFC vehicle data attributes and European
registration certificates to facilitate the task of a service provider in OBE-personalization with
vehicle data;
— Annex F, which presents the security calculations according to the data encryption standard (DES).
NOTE 1 Annex F is based on EN 15509:2014, Annex B.
— Annex G, which presents security computations examples for DES;
NOTE 2 Annex G is based on EN 15509:2014, Annex E.
— Annex H, which presents the security calculations for advanced encryption standard (AES);
NOTE 3 Annex H is an adaptation of EN 15509:2014, Annex B for the case of AES.
— Annex I, which presents the security computations examples for AES.
NOTE 4 Annex I is an adaptation of EN 15509:2014, Annex E for the case of AES.
vii
INTERNATIONAL STANDARD ISO 14906:2022(E)
Electronic fee collection — Application interface definition
for dedicated short-range communication
1 Scope
This document specifies the application interface in the context of electronic fee collection (EFC)
systems using dedicated short-range communication (DSRC).
The EFC application interface is the EFC application process interface to the DSRC application layer, as
can be seen in Figure 1. This document comprises specifications of:
— EFC attributes (i.e. EFC application information) that can also be used for other applications and/or
interfaces;
— the addressing procedures of EFC attributes and (hardware) components (e.g. integrated circuit(s)
card);
— EFC application functions, i.e. further qualification of actions by definitions of the concerned services,
assignment of associated ActionType values, and content and meaning of action parameters;
— the EFC transaction model, which defines the common elements and steps of any EFC transaction;
— the behaviour of the interface so as to ensure interoperability on an EFC-DSRC application interface
level.
Figure 1 — The EFC application interface
This is an interface standard, adhering to the open systems interconnection (OSI) philosophy (see
ISO/IEC 7498-1), and it is as such not primarily concerned with the implementation choices to be
realized at either side of the interface.
This document provides security-specific functionality as place holders (data and functions) to enable
the implementation of secure EFC transactions. Yet the specification of the security policy (including
specific security algorithms and key management) remains at the discretion and under the control of
the EFC operator, and hence is outside the scope of this document.
ISO 14906:2022(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 612, Road vehicles — Dimensions of motor vehicles and towed vehicles — Terms and definitions
ISO 1176, Road vehicles — Masses — Vocabulary and codes
ISO 3166-1, Codes for the representation of names of countries and their subdivisions — Part 1: Country
code
ISO 3779, Road vehicles — Vehicle identification number (VIN) — Content and structure
ISO 4217, Codes for the representation of currencies
ISO/IEC 7812-1, Identification cards — Identification of issuers — Part 1: Numbering system
ISO/IEC 8825-2, Information technology — ASN.1 encoding rules — Part 2: Specification of Packed
Encoding Rules (PER)
ISO/IEC 9797-1:2011, Information technology — Security techniques — Message Authentication Codes
(MACs) — Part 1: Mechanisms using a block cipher
ISO 14816, Road transport and traffic telematics — Automatic vehicle and equipment identification —
Numbering and data structure
ISO 15628:2013, Intelligent transport systems — Dedicated short range communication (DSRC) — DSRC
application layer
2)
ISO 17573-3:— , Electronic fee collection — System architecture for vehicle-related tolling — Part 3: Data
dictionary
ISO/IEC 18033-3:2010, Information technology — Security techniques — Encryption algorithms — Part 3:
Block ciphers
EN 12834, Road transport and traffic telematics — Dedicated Short Range Communication (DSRC) —
DSRC application layer
3 Terms and definitions
For the purposes of this document, the following terms and definitions 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
access credentials
trusted attestation or secure module that establishes the claimed identity of an object or application
[SOURCE: ISO/TS 17573-2:2020, 3.4]
2) Under preparation. Stage at the time of publication: ISO/DIS 17573-3:2022.
ISO 14906:2022(E)
3.2
attribute
addressable package of data consisting of a single data element or structured sequences of data
elements
[SOURCE: ISO/TS 17573-2:2020, 3.13]
3.3
authenticator
data, possibly encrypted, that is used for authentication
[SOURCE: ISO/TS 17573-2:2020, 3.16]
3.4
channel
information transfer path
[SOURCE: ISO/TS 17573-2:2020, 3.30]
3.5
cryptography
principles, means and methods for the transformation of data in order to hide its information content,
prevent its undetected modification or prevent its unauthorized use
[SOURCE: ISO/TS 17573-2:2020, 3.53]
3.6
data group
class of closely related attributes (3.2)
[SOURCE: ISO/TS 17573-2:2020, 3.55]
3.7
data integrity
information integrity
property that data has not been altered or destroyed in an unauthorized manner
[SOURCE: ISO/TS 17573-2:2020, 3.56]
3.8
Element
DSRC directory containing application information in the form of attributes (3.2)
3.9
on-board equipment
all required equipment on-board a vehicle for performing required EFC functions and communication
services
[SOURCE: ISO/TS 17573-2:2020, 3.126]
3.10
on-board unit
single electronic unit on-board a vehicle for performing specific EFC functions and for communication
with external systems
[SOURCE: ISO/TS 17573-2:2020, 3.127]
ISO 14906:2022(E)
3.11
roadside equipment
fixed or movable electronic fee collection equipment located along or on the road
Note 1 to entry: Roadside equipment (RSE) and roadside unit (RSU) have been used as terms with the same or
similar meaning in the standardization of DSRC and DSRC-based EFC within CEN and ETSI. Previously-developed
relevant standards used the term "RSU" with the meaning "RSE" as defined in this document.
[SOURCE: ISO/TS 17573-2:2020, 3.161]
3.12
toll charger
entity which levies toll for the use of vehicles in a toll domain (3.13)
[SOURCE: ISO/TS 17573-2:2020, 3.194]
3.13
toll domain
area or part of a road network where a toll regime is applied
[SOURCE: ISO/TS 17573-2:2020, 3.201]
3.14
toll service
service enabling users to pay toll
[SOURCE: ISO/TS 17573-2:2020, 3.205]
3.15
toll service provider
entity providing toll services (3.14) in one or more toll domains (3.13)
[SOURCE: ISO/TS 17573-2:2020, 3.206]
3.16
transaction
whole of the exchange of information between two physically separated communication facilities
[SOURCE: ISO/TS 17573-2:2020, 3.211]
3.17
transaction model
functional model describing the structure of electronic payment transactions (3.16)
[SOURCE: ISO/TS 17573-2:2020, 3.213]
4 Abbreviated terms
For the purposes of this document, the following abbreviated terms apply.
ADU application data unit
AES advanced encryption standard
AP application process
APDU application protocol data unit
ASN.1 abstract syntax notation one
BST beacon service table
ISO 14906:2022(E)
CCC compliance check communication
cf confirm
DES data encryption standard
DSRC dedicated short-range communication
EFC electronic fee collection
EID Element Identifier
GNSS global navigation satellite system
ICC integrated circuit(s) card
IID invoker identifier
I-Kernel initialisation kernel
ind indication
L1 layer 1 of DSRC (physical layer)
L2 layer 2 of DSRC (data link layer)
L7 application layer core of DSRC
LAC localisation augmentation communication
LID logical link control identifier
LLC logical link control
LPDU LLC protocol data unit
MAC medium access control
MMI man-machine interface
n.a. not applicable
OBE on-board equipment
OBU on-board unit
PDU protocol data unit
PER packed encoding rules
PPDU physical protocol data unit
req request
rs response
RSE roadside equipment
RSU roadside unit
SAM secure application module
ISO 14906:2022(E)
T-APDU transfer-application protocol data unit
T-ASDU transfer-application service data unit
T-Kernel transfer kernel
TC toll charger
TSP toll service provider
VST vehicle service table
XOR exclusive or (logical operation)
5 EFC application interface architecture
5.1 Relation to the DSRC communication architecture
The DSRC services are provided to an application process (AP) by means of the DSRC application layer
service primitives, which are abstract implementation interactions between a communication service
user and a provider. The services are offered by the DSRC communication entities by means of its DSRC
application layer (EN 12834/ISO 15628) as shown in Figure 2.
ISO 14906:2022(E)
NOTE The abbreviated terms used in Figure 2 are defined in Clause 4.
Figure 2 — The EFC application process on top of the DSRC communication stack
The transfer kernel (T-Kernel)of DSRC application layer offers the following services to application
processes (see Figure 2):
— GET: The invocation of a GET service request results in retrieval (i.e. reading) of application
information (i.e. Attributes) from the peer service user (i.e. the OBE application process). A reply is
always expected.
— SET: The invocation of a SET service request results in modification (i.e. writing) of application
information (i.e. Attributes) of the peer service user (i.e. the OBE application process). This service
may be requested in confirmed or non-confirmed mode. A reply is only expected in the former case.
— ACTION: The invocation of an ACTION service request results in a performance of an action by the
peer service user (i.e. the OBE application process). An action is further qualified by the value of the
ActionType. This service may be requested in confirmed or non-confirmed mode. A reply is only
expected in the former case.
— EVENT-REPORT: The invocation of an EVENT-REPORT service request forwards a notification of an
event to the peer service user.
ISO 14906:2022(E)
— INITIALISATION: The invocation of an initialisation service request by RSE results in an attempt to
initialise communication between an RSE and each OBE that has not yet established communication
with the concerned RSE. The initialisation service is only used by the initialisation kernel as defined
in EN 12834/ISO 15628.
5.2 Usage of DSRC application layer by the EFC application interface
EFC uses the following services offered by DSRC application layer (as defined in ISO 15628):
— The INITIALISATION services (listed below) are used to realize the EFC-specific initialisation
mechanism (see Clause 6):
— Notify Application RSU (at RSE),
— End Application (at RSE),
— Register Application RSU (at RSE),
— Deregister Application (at RSE and OBE),
— Notify Application OBU (at OBE),
— Register Application OBU (at OBE),
— The GET service is used to retrieve EFC attributes (for attribute specifications see Clause 8);
— The SET service is used to set EFC attributes;
— The ACTION services are applied to realize additional EFC specific functionality needed to support
EFC application processes, such as TRANSFER_CHANNEL, SET_MMI and ECHO (see 7.2).
In the following subclauses, the EFC-specific usage of the DSRC Layer 7 services is specified in detail.
NOTE The EVENT-REPORT-service can be implicitly used by EFC application processes. For example,
it is used indirectly as part of an already defined command to release an application process (see EN 12834/
ISO 15628, Ready Application). However, as the EVENT-REPORT-service is not explicitly used by EFC application
processes, this service is not further referred to in this document.
5.3 Addressing of EFC attributes
5.3.1 Basic mechanism
EFC Attributes are used to transfer the EFC application-specific information.
EFC Attributes are composed of one or more data elements of specified abstract syntax notation
one (ASN.1) types. Each data element is associated with, within the context of this document, an
unambiguous name.
To each EFC Attribute, an AttributeID is associated. The AttributeID enables to unambiguously identify
and address an EFC Attribute.
EXAMPLE Figure 3 illustrates the basic addressing mechanism.
ISO 14906:2022(E)
Figure 3 — Basic addressing mechanism
5.3.2 Role of the Element Identifier (EID)
In a given OBE, the DSRC-EID (different from 0) is used to address an EFC context, identified by the
EfcContextMark (see 6.2.3), in which Attributes can be addressed unambiguously by AttributeIDs
inside an Element of the OBE. In the vehicle service table (VST), the OBE transmits one or several of
these EFC contexts, each corresponding to an EFC ContextMark and the EID to be used for addressing
the attributes and each using the EFC functions supported by it.
EXAMPLE Figure 4 illustrates the role of the EID.
Figure 4 — Role of the EID
EID equals 0 shall be used to address application-independent functions and components, e.g. SET_MMI
and TRANSFER_CHANNEL (see 7.2).
5.3.3 Multiple instances of Attributes
There may be n, where n is an INTEGER, instances of an Attribute available in the OBE.
The maximum number of instances, N , of one Attribute may be limited according to the needs
max
of operators and users. The default maximum number of instances is N = 1. The value of N is
max max
determined at the time of OBE configuration.
EXAMPLE Figure 5 illustrates multiple instances (0-2) of attribute 5.
ISO 14906:2022(E)
Figure 5 — Multiple instances (0-2) of attribute 5
The handling of multiple instances and the corresponding addressing mechanism are described
in detail as part of the behaviour specification of the corresponding functions supporting multiple
instances (see 7.2.6 for GET_INSTANCE and 7.2.7 for SET_INSTANCE).
5.4 Addressing of components
Components of an OBE to be addressed via the EFC application interface include for example:
— OBU;
— secure application module (SAM) 1;
— SAM 2;
— ICC;
— display;
— buzzer;
— printer;
— serial interface;
— parallel interface;
— global navigation satellite system (GNSS);
— tachograph;
— bluetooth.
Addressing of these components is enabled on two levels: device-specific and device-independent
addressing.
The device-specific transparent addressing mechanism enables the transfer of information, which
shall be processed by the addressed device (such as an integrated circuit(s) card (ICC)-command). The
addressed device is identified by a channel ID. The EFC function TRANSFER_CHANNEL (see 7.2.10)
supports this functionality.
EXAMPLE 1 Transfer of a bit string to an ICC.
The device-independent addressing mechanism uses a set of commands, which describe a certain
functionality, which can be performed by various OBE components. In this case, the operating system
of the OBE will address the corresponding components. The EFC function SET_MMI supports this
functionality (see 7.2.12).
EXAMPLE 2 Invocation of a SET_MMI(EID=0, ContactOperator) function activates an OBE MMI-device, e.g. a
buzzer or a display.
ISO 14906:2022(E)
NOTE In a specific implementation, specific attributes or data elements can activate some man-machine
interface (MMI) function (e.g. a SET command on the attribute ReceiptText can display the text on a display.
A SET command on the attribute ReceiptServicePart with data element SessionResultOperational other than
SessionOK can activate an alert beep). Proprietary addressing mechanisms are not defined by this document.
6 EFC transaction model
6.1 General
The EFC transaction model related to the EFC application interface for the DSRC comprises two phases:
the initialisation phase and the transaction phase.
NOTE The purpose of the initialisation phase is to set up the communication between the RSE and OBE
that have entered the DSRC zone but have not yet established communication with the RSE, and to notify the
application processes. It provides, amongst others, a multi-application switching mechanism, allowing for
execution of several ITS applications (in parallel) at one RSE station.
The transaction phase can only be reached after completion of the initialisation phase. The EFC
functions, as defined in Clause 7, can be performed in the transaction phase. The GET and SET services
(DSRC application layer functions) as defined in EN 12834/ISO 15628:2013, 6.2, may also be used in an
EFC transaction phase.
6.2 Initialisation phase
6.2.1 Overview
This subclause provides an overview of the functionality of, and the information exchanges in, the
initialisation phase.
The initialisation procedures, by means
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...