Electronic fee collection - Application interface definition for dedicated short-range communication (ISO/DIS 14906:2022)

This document specifies the application interface in the context of electronic fee collection (EFC) systems using the dedicated short-range communication (DSRC).

Elektronische Gebührenerhebung - Anwendungsschnittstelle zur dezidierten Nahbereich- Kommunikation (ISO/DIS 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/DIS 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).

Elektronsko pobiranje pristojbin - Definicija aplikacijskega vmesnika za posebne komunikacije kratkega dosega (ISO/DIS 14906:2022)

General Information

Status
Not Published
Current Stage
4599 - Dispatch of FV draft to CMC - Finalization for Vote
Due Date
08-Jul-2022
Completion Date
08-Jul-2022

RELATIONS

Buy Standard

Draft
prEN ISO 14906:2022
English language
130 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (sample)

SLOVENSKI STANDARD
oSIST prEN ISO 14906:2022
01-marec-2022
Elektronsko pobiranje pristojbin - Definicija aplikacijskega vmesnika za posebne
komunikacije kratkega dosega (ISO/DIS 14906:2022)

Electronic fee collection - Application interface definition for dedicated short-range

communication (ISO/DIS 14906:2022)
Elektronische Gebührenerhebung - Anwendungsschnittstelle zur dezidierten
Nahbereich- Kommunikation (ISO/DIS 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/DIS 14906:2022)
Ta slovenski standard je istoveten z: prEN ISO 14906
ICS:
03.220.20 Cestni transport Road transport
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
oSIST prEN ISO 14906:2022 en,fr,de

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------
oSIST prEN ISO 14906:2022
---------------------- Page: 2 ----------------------
oSIST prEN ISO 14906:2022
DRAFT INTERNATIONAL STANDARD
ISO/DIS 14906
ISO/TC 204 Secretariat: ANSI
Voting begins on: Voting terminates on:
2022-01-10 2022-04-04
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
ICS: 03.220.20; 35.240.60
This document is circulated as received from the committee secretariat.
THIS DOCUMENT IS A DRAFT CIRCULATED
FOR COMMENT AND APPROVAL. IT IS
ISO/CEN PARALLEL PROCESSING
THEREFORE SUBJECT TO CHANGE AND MAY
NOT BE REFERRED TO AS AN INTERNATIONAL
STANDARD UNTIL PUBLISHED AS SUCH.
IN ADDITION TO THEIR EVALUATION AS
BEING ACCEPTABLE FOR INDUSTRIAL,
TECHNOLOGICAL, COMMERCIAL AND
USER PURPOSES, DRAFT INTERNATIONAL
STANDARDS MAY ON OCCASION HAVE TO
BE CONSIDERED IN THE LIGHT OF THEIR
POTENTIAL TO BECOME STANDARDS TO
WHICH REFERENCE MAY BE MADE IN
Reference number
NATIONAL REGULATIONS.
ISO/DIS 14906:2022(E)
RECIPIENTS OF THIS DRAFT ARE INVITED
TO SUBMIT, WITH THEIR COMMENTS,
NOTIFICATION OF ANY RELEVANT PATENT
RIGHTS OF WHICH THEY ARE AWARE AND TO
PROVIDE SUPPORTING DOCUMENTATION. © ISO 2022
---------------------- Page: 3 ----------------------
oSIST prEN ISO 14906:2022
ISO/DIS 14906:2021(E)
ISO/DIS 14906:2022(E)
DRAFT INTERNATIONAL STANDARD
ISO/DIS 14906
Fourth edition
2021-07-01

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
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
© ISO 2021 – All rights reserved i
Published in Switzerland
© ISO 2022 – All rights reserved
---------------------- Page: 4 ----------------------
oSIST prEN ISO 14906:2022
ISO/DIS 14906:2021(E)
Foreword

ISO (the International Organization for Standardization) is a worldwide federation of national standards

bodies (ISO member bodies). The work of preparing International Standards is normally carried out

through ISO technical committees. Each member body interested in a subject for which a technical

committee has been established has the right to be represented on that committee. International

organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. ISO

collaborates closely with the International Electrotechnical Commission (IEC) on all matters of

electrotechnical standardization.

The procedures used to develop this document and those intended for its further maintenance are

described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for the

different types of ISO documents should be noted. This document was drafted in accordance with the

editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).

Attention is drawn to the possibility that some of the elements of this document may be the subject of

patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of any

patent rights identified during the development of the document will be in the Introduction and/or on

the ISO list of patent declarations received (see www.iso.org/patents).

Any trade name used in this document is information given for the convenience of users and does not

constitute an endorsement.

For an explanation 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, 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 subject to a

revision. It also incorporates the the Amendment 14906:2018/Amd 1:2020.
The main changes compared to the previous edition are as follows:
— integration of the ISO 14906:2018/Amd 1:2020;

— minor updating of terms, including the reference to ISO/TS 17573-2 as the primary source;

— minor updating of data definitions, including the reference to ISO/TS 17573-3 as the primary source.

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 2021 – All rights reserved iii
---------------------- Page: 5 ----------------------
oSIST prEN ISO 14906:2022
ISO/DIS 14906:2021(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;

— EFCContextMark (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 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 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.
© ISO 2021 – All rights reserved iv
---------------------- Page: 6 ----------------------
oSIST prEN ISO 14906:2022
FINAL DRAFT INTERNATIONAL STANDARD ISO/DIS 14906:2021(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.
© ISO 2021 – All rights reserved 5
---------------------- Page: 7 ----------------------
oSIST prEN ISO 14906:2022
ISO/DIS 14906:2021(E)

Normative Annex A provides the normative ASN.1 data type specifications (EFC action parameters and

attributes).

Informative Annex B presents an example of a transaction based on the CARDME specification, including

bit-level specification.

Informative Annex C presents examples of EFC transaction types, using the specified EFC functions and

attributes.

Informative Annex D presents a mapping table from LatinAlphabetNo2 & 5 to LatinAlphabetNo1 to ease

for a Service Provider the use of LatinAlphabetNo1 to encode an OBE for data available written with non-

Latin1 characters.

Informative Annex E presents a 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.

Normative Annex F presents the security calculations according to the data encryption standard (DES).

NOTE 1 Annex F is based on EN 15509:2014, Annex B.
Informative Annex G presents security computations examples for DES.
NOTE 2 Annex G is based on EN 15509:2014, Annex E.

Normative Annex H 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.
Informative Annex I 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.

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.
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 2021 – All rights reserved 6
---------------------- Page: 8 ----------------------
oSIST prEN ISO 14906:2022
ISO/DIS 14906:2021(E)

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, 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/TS 17573-3:2021, 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 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

[SOURCE: ISO/TS 17573-2:2020, definition 3.4]
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, definition 3.13]
3.3
authenticator
data, possibly encrypted, that is used for authentication
[SOURCE: ISO/TS 17573-2:2020, definition 3.16]
3.4
channel
information transfer path
[SOURCE: ISO/TS 17573-2:2020, definition 3.30]
© ISO 2021 – All rights reserved 7
---------------------- Page: 9 ----------------------
oSIST prEN ISO 14906:2022
ISO/DIS 14906:2021(E)
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, definition 3.53]
3.6
data group
class of closely related attributes (0)
[SOURCE: ISO/TS 17573-2:2020, definition 3.55]
3.7
data integrity
information integrity
property that data has not been altered or destroyed in an unauthorised manner
[SOURCE: ISO/TS 17573-2:2020, definition 3.56]
3.8
Element
DSRC directory containing application information in the form of attributes
3.9
on-board equipment
OBE

all required equipment on-board a vehicle for performing required EFC functions and communication

services
[SOURCE: ISO/TS 17573-2:2020, definition 3.126]
3.10
on-board unit
OBU

single electronic unit on-board a vehicle for performing specific EFC functions and for communication

with external systems
[SOURCE: ISO/TS 17573-2:2020, definition 3.127]
3.11
roadside equipment
RSE

fixed or movable electronic fee collection equipment located along or on the road

[SOURCE: ISO/TS 17573-2:2020, definition 3.161]
3.12
toll charger
entity which levies toll for the use of vehicles in a toll domain
[SOURCE: ISO/TS 17573-2:2020, definition 3.194]
© ISO 2021 – All rights reserved 8
---------------------- Page: 10 ----------------------
oSIST prEN ISO 14906:2022
ISO/DIS 14906:2021(E)
3.13
toll domain
area or part of a road network where a toll regime is applied
[SOURCE: ISO/TS 17573-2:2020, definition 3.201]
3.14
toll service
service enabling users to pay toll
[SOURCE: ISO/TS 17573-2:2020, definition 3.205]
3.15
toll service provider
TSP
entity providing toll services (3.14) in one or more toll domains (0)
[SOURCE: ISO/TS 17573-2:2020, definition 3.206]
3.16
transaction

whole of the exchange of information between two physically separated communication facilities

[SOURCE: ISO/TS 17573-2:2020, definition 3.211]
3.17
transaction model
functional model describing the structure of electronic payment transactions (0)
[SOURCE: ISO/TS 17573-2:2020, definition 3.213]
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
© ISO 2021 – All rights reserved 9
---------------------- Page: 11 ----------------------
oSIST prEN ISO 14906:2022
ISO/DIS 14906:2021(E)
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)
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 2021 – All rights reserved 10
---------------------- Page: 12 ----------------------
oSIST prEN ISO 14906:2022
ISO/DIS 14906:2021(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.
© ISO 2021 – All rights reserved 11
---------------------- Page: 13 ----------------------
oSIST prEN ISO 14906:2022
ISO/DIS 14906:2021(E)

— EVENT-REPORT: The invocation of an EVENT-REPORT service request forwards a notification of an

event to the peer service user.

— 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 2021 – All rights reserved 12
---------------------- Page: 14 ----------------------
oSIST prEN ISO 14906:2022
ISO/DIS 14906:2021(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

EFCContextMark (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 determined

max max
at the time of OBE configuration.
EXAMPLE Figure 5 illustrates multiple instances (0-2) of attribute 5.
© ISO 2021 – All rights reserved 13
---------------------- Page: 15 ----------------------
oSIST prEN ISO 14906:2022
ISO/DIS 14906:2021(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).
© ISO 2021 – All rights reserved 14
---------------------- Page: 16 ----------------------
oSIST prEN ISO 14906:2022
ISO/DIS 14906:2021(E)

EXAMPLE 2 Invocation of a SET_MMI(EID=0, ContactOperator) function activates an OBE MMI-device, e.g. a

buzzer or a display.

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.

© ISO 2021 – All rights reserved 15
---------------------- Page: 17 ----------------------
oSIST prEN ISO 14906:2022
ISO/DIS 14906:2021(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 conce

...

Questions, Comments and Discussion

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