EN ISO 14906:2018

SLOVENSKI STANDARD
01-februar-2019
1DGRPHãþD
SIST EN ISO 14906:2011
SIST EN ISO 14906:2011/A1:2015
SIST EN ISO 14906:2011/AC:2014
Elektronsko pobiranje pristojbin - Definicija aplikacijskega vmesnika za posebne
komunikacije kratkega dosega (ISO 14906:2018)
Electronic fee collection - Application interface definition for dedicated short-range
communication (ISO 14906:2018)
Elektronische Gebührenerhebung - Anwendungsschnittstelle zur dezidierten Nahbereich-
Kommunikation (ISO 14906:2018)
Perception du télépéage - Définition de l'interface d'application relative aux
communications dédiées à courte portée (ISO 14906:2018)
Ta slovenski standard je istoveten z: EN ISO 14906:2018
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
December 2018
EUROPÄISCHE NORM
ICS 35.240.60; 03.220.20 Supersedes EN ISO 14906:2011
English Version
Electronic fee collection - Application interface definition
for dedicated short-range communication (ISO
14906:2018)
Perception du 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:2018) Kommunikation (ISO 14906:2018)
This European Standard was approved by CEN on 6 September 2018.

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, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania,
Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland,
Turkey 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
© 2018 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN ISO 14906:2018 E
worldwide for CEN national Members.

Contents Page
European foreword . 3

European foreword
This document (EN ISO 14906:2018) 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 June 2019, and conflicting national standards shall be
withdrawn at the latest by June 2019.
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:2011.
This document has been prepared under a mandate given to CEN by the European Commission and the
European Free Trade Association, and supports essential requirements of EU Directive(s).
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, Former Yugoslav Republic of Macedonia,
France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta,
Netherlands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland,
Turkey and the United Kingdom.
Endorsement notice
The text of ISO 14906:2018 has been approved by CEN as EN ISO 14906:2018 without any modification.

INTERNATIONAL ISO
STANDARD 14906
Third edition
2018-10
Electronic fee collection — Application
interface definition for dedicated
short-range communication
Perception du télépéage — Définition de l'interface d'application
relative aux communications dédiées à courte portée
Reference number
ISO 14906:2018(E)
©
ISO 2018
ISO 14906:2018(E)
© ISO 2018
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
Fax: +41 22 749 09 47
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO 2018 – All rights reserved

ISO 14906:2018(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 . 5
5.1 Relation to the DSRC communication architecture . 5
5.2 Usage of DSRC application layer by the EFC application interface . 7
5.3 Addressing of EFC attributes . 7
5.3.1 Basic mechanism . 7
5.3.2 Role of the EID . 8
5.3.3 Multiple Instances of Attributes . 8
5.4 Addressing of components . 9
6 EFC Transaction Model .10
6.1 General .10
6.2 Initialisation Phase .10
6.2.1 Overview .10
6.2.2 EFC application-specific contents of the BST .11
6.2.3 EFC application-specific contents of the VST .12
6.3 Transaction phase .13
7 EFC functions .14
7.1 Overview and general concepts .14
7.1.1 EFC functions and service primitives .14
7.1.2 Overview of EFC functions .15
7.1.3 Handling of multiple instances .16
7.1.4 Security .18
7.2 EFC functions .21
7.2.1 General.21
7.2.2 GET_STAMPED .21
7.2.3 SET_STAMPED .22
7.2.4 GET_SECURE .23
7.2.5 SET_SECURE .24
7.2.6 GET_INSTANCE .25
7.2.7 SET_INSTANCE . .25
7.2.8 GET_NONCE . .26
7.2.9 SET_NONCE .27
7.2.10 TRANSFER_CHANNEL .27
7.2.11 COPY .28
7.2.12 SET_MMI .29
7.2.13 SUBTRACT .29
7.2.14 ADD . .30
7.2.15 DEBIT .30
7.2.16 CREDIT .31
7.2.17 ECHO .32
8 EFC Attributes .33
8.1 General .33
8.2 Data group CONTRACT .35
8.3 Data group RECEIPT .38
8.4 Data group VEHICLE .44
8.5 Data group EQUIPMENT .51
ISO 14906:2018(E)
8.6 Data group DRIVER .53
8.7 Data group PAYMENT .55
Annex A (normative) EFC data type specifications .57
Annex B (informative) CARDME transaction .58
Annex C (informative) Examples of EFC transaction types .92
Annex D (normative) Mapping table from LatinAlphabetNo2 & 5 to LatinAlphabetNo1 .104
Annex E (informative) Mapping table between EFC Vehicledata attribute and European
registration certificate .105
Annex F (normative) Security calculations for DES .108
Annex G (informative) Security computation examples for DES .113
Annex H (normative) Security calculations for AES .116
Annex I (informative) Security computation examples for AES .121
Bibliography .123
iv © ISO 2018 – All rights reserved

ISO 14906:2018(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 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 third edition cancels and replaces the second edition (ISO 14906:2011), which has been technically
revised. It also incorporates the Corrigendum ISO 14906:2011/Cor1: 2013 and the Amendment
I S O 14906:2011/A md1: 2015 .
The main changes compared to the previous edition are as follows:
— Inclusion of security calculations according to advanced encryption standard, as recommended in
CEN/TR 16968 on security mechanisms (revision of Clause 7 and new Annexes F, G, H and I);
— Update of the normative references, terms and definitions and abbreviated terms clauses and the
Bibliography;
— Conversion of the ASN.1 module into an electronic insert;
— Revision of Annex C;
— Removal of Annex D (informative) on functional requirements.
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.
ISO 14906:2018(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 might 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 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 recognising each others' EFC transactions (including the exchange of security algorithms and
keys) and implementing the EFC transactions in each others' RSEs, 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. This
issue can be managed by using the following:
— EfcModule ASN.1 module, including a version number;
— Efc-ContextMark (incl. the ContextVersion), denoting the implementation version, 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 his capabilty to accept the new features introduced by this
edition of ISO 14906.
Annex A provides the normative ASN.1 specifications of the used data types (EFC action parameters
and attributes).
Annex B presents an informative example of a transaction based on the CARDME specification,
including bit-level specification.
Annex C presents informative examples of EFC transaction types, using the specified EFC functions and
attributes.
Annex D presents an informative mapping table from LatinAlphabetNo2 & 5 to LatinAlphabetNo1 to
ease for a Service Provider the use of LatinAlphabetNo1 to encode an OBE for data available wiitten
with non-Latin1 characters.
vi © ISO 2018 – All rights reserved

ISO 14906:2018(E)
Annex E presents an informative mapping table between EFC vehicle data attributes and European
registration certificates to ease the task of a service provider in the OBE personalisation with vehicle data.
Annex F presents the security calculations according to the data encryption standard (DES). This annex
is based on EN 15509:2014, Annex B.
Annex G presents the security computations examples for DES. This annex is based on EN 15509:2014,
Annex E.
Annex H presents the security calculations for advanced encryption standard (AES). This annex is the
adaptation of EN 15509:2014, Annex B for the case of AES.
Annex I presents the security computations examples for AES. This annex is the adaptation of
EN 15509:2014, Annex E for the case of AES.
This application interface definition can also be used with other DSRC media which do not use a 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 describes in
detail 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.
INTERNATIONAL STANDARD ISO 14906:2018(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 the 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 below. 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. ICC and MMI),
— 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 realised 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:2018(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 codes
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: Specification of Packed Encoding Rules
(PER) — Part 2
ISO/IEC 9797-1:2011, Information technology — Security techniques — Message Authentication Codes
(MACs) — Part 1: Mechanisms using a block cipher
ISO 14816:2005, 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
ISO/IEC 18033-3:2010, Information technology — Security techniques — Encryption algorithms — Part 3:
Block ciphers
EN 12834:2003, 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 terminological databases for use in standardization at the following addresses:
— IEC Electropedia: available at http: //www .electropedia .org/
— ISO Online browsing platform: available at http: //www .iso .org/obp
3.1
access credentials
trusted attestation or secure module that establishes the claimed identity of an object or application
3.2
attribute
addressable package of data consisting of a single data element or structured sequences of data
elements
[SOURCE: ISO 17575-1:2016, definition 3.2]
3.3
authenticator
data, possibly encrypted, that is used for authentication
2 © ISO 2018 – All rights reserved

ISO 14906:2018(E)
3.4
channel
information transfer path
[SOURCE: ISO 7498-2:1989, definition 3.3.13]
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
3.6
data group
class of closely related attributes
[SOURCE: ISO 17575-1:2016, definition 3.10]
3.7
data integrity
property that data has not been altered or destroyed in an unauthorised manner
3.8
Element
DSRC directory containing application information in the form of attributes
3.9
on-board equipment
all required equipment on-board a vehicle for performing required EFC functions and communication
services
3.10
on-board unit
single electronic unit on-board a vehicle for performing specific EFC functions and for communication
with external systems
3.11
roadside equipment
equipment located along the road, either fixed or mobile
3.12
toll charger
entity which levies toll for the use of vehicles in a toll domain
3.13
toll domain
area or part of a road network where a toll regime is applied
[SOURCE: ISO 17573:2010, definition 3.18]
3.14
toll service
service enabling users to pay toll
3.15
toll service provider
entity providing toll services in one or more toll domains
3.16
transaction
whole of the exchange of information between two physically separated communication facilities
[SOURCE: ISO 17575-1:2016, definition 3.21]
ISO 14906:2018(E)
3.17
transaction model
functional model describing the structure of electronic payment transactions
4 Abbreviated terms
For the purposes of this document, the following abbreviated terms apply unless otherwise specified.
AP Application Process
APDU Application Protocol Data Unit
ASN.1 Abstract Syntax Notation One (ISO/IEC 8824-1)
BST Beacon Service Table
CCC Compliance check communication
cf Confirm
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
PDU Protocol Data Unit
PER Packed Encoding Rules (ISO/IEC 8825-2)
4 © ISO 2018 – All rights reserved

ISO 14906:2018(E)
req Request
rs Response
RSE Roadside Equipment
SAM Secure Application Module
T-APDU Transfer-Application Protocol Data Unit
T-ASDU Transfer-Application Service Data Unit
T-Kernel Transfer Kernel
VST Vehicle Service Table
5 EFC application interface architecture
5.1 Relation to the DSRC communication architecture
The DSRC services are provided to an application process 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:2018(E)
Figure 2 — The EFC application process on top of the DSRC communication stack
NOTE The abbreviated terms used in Figure 2 are defined in Clause 4.
The Transfer Kernel of DSRC Application Layer offers the following services to application processes
(see also Figure 2 above):
— 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.
6 © ISO 2018 – All rights reserved

ISO 14906:2018(E)
— INITIALISATION: The invocation of an initialisation service request by RSE results in an attempt to
initialise communication between a 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:
— 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)
are used to realise the EFC-specific initialisation mechanism (see Clause 6);
— 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 realise additional EFC specific functionality needed to support
EFC application processes, such as TRANSFER_CHANNEL, SET_MMI and ECHO (see 7.2).
In the following, 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. It is e.g. 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 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:2018(E)
Figure 3 — Basic addressing mechanism
5.3.2 Role of the EID
In a given OBE, the DSRC-EID (different from 0) is used to address an EFC context, identified by the
EFC-ContextMark (see 6.2.3), in which Attributes can be addressed unambiguously by AttributeIDs
inside an Element of the OBE. In the VST, the OBE specifies one or several of these EFC contexts, each
corresponding to an EFC ContextMark and the EID to be used for addressing the attributes and 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 of
max
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.
8 © ISO 2018 – All rights reserved

ISO 14906:2018(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;
— SAM 1;
— SAM 2;
— ICC;
— Display;
— Buzzer;
— Printer;
— Serial interface;
— Parallel interface;
— 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 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:2018(E)
NOTE In a specific implementation, specific attributes or data elements can activate some MMI function (e.g.
a SET command on the attribute ReceiptText might display the text on a liquid crystal display. A SET command
on the attribute ReceiptServicePart with data element SessionResultOperational other than SessionOK might
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 OBEs
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 (in 6.2) may also be used in an
EFC transaction phase.
6.2 Initialisation Phase
6.2.1 Overview
This clause provides an overview of the functionality of, and the information exchanges in, the
initialisation phase.
The Initialisation procedures, by means of beacon service table (BST) and vehicle service table (VST)
exchanges, are defined in EN 12834/ISO 15628. 6.2.2 and 6.2.3 below account for the EFC application-
specific information that shall be included in the BST and VST, respectively as shown in Figure 6.
NOTE The OBE evaluates the received BST, and selects the applications that it wishes to perform out of the
lists of applications supported by the RSE.
If the OBE does not support any of application(s) supported by the RSE, then the OBE should not exchange
any information with the RSE. If the OBE supports at least one of the application(s) supported by the RSE,
then the OBE should inform the RSE of which application it wishes to execute in its corresponding VST.
10 © ISO 2018 – All rights reserved

ISO 14906:2018(E)
Figure 6 — Initialisation phase: BST - VST exchanges
The Initialisation service associated with the initialisation phase is only used by the Initialisation
Kernel (of EN 12834/ISO 15628), which in its turn is configured by the application(s) wishing to execute
applications over a DSRC link. The Initialisation Kernels of the RSE and of the concerned OBE shall have
been configured, according to EN 12834/ISO 15628, prior to the invocation of the Initialisation service
by the RSE.
6.2.2 EFC application-specific contents of the BST
An RSE supporting EFC shall have configured its Initialisation Kernel to carry the following information
related specifically to the EFC application(s):
— the application identifier (AID) shall be equal to 1 (i.e. the value assigned for EFC);
— the EFC application shall be qualified as a mandatory application;
— EID shall not be transmitted in the BST related to the EFC application;
— no Parameter shall be transmitted in the BST related to the EFC application.
NOTE 1 AID equals to 14 identifies the multi-purpose payment con
...