ISO 13141:2024
(Main)Electronic fee collection — Localization augmentation communication for autonomous systems
Electronic fee collection — Localization augmentation communication for autonomous systems
This document establishes requirements for short-range communication for the purposes of augmenting the localization in autonomous electronic fee collection (EFC) systems. Localization augmentation serves to inform on-board equipment (OBE) about geographical location and the identification of a charge object. This document specifies the provision of location and heading information and security means to protect against the manipulation of the OBE with false RSE. The localization augmentation communication (LAC) takes place between an OBE in a vehicle and fixed RSE. This document is applicable to OBE in an autonomous mode of operation. This document specifies attributes and functions for the purpose of localization augmentation, by making use of the dedicated short-range communications (DSRC) communication services provided by DSRC Layer 7, and makes these LAC attributes and functions available to the LAC applications at the RSE and the OBE. Attributes and functions are specified on the level of application data units (ADUs; see Figure 1). As depicted in Figure 1, this document is applicable to: — the application interface definition between OBE and RSE; — the interface to the DSRC application layer, as specified in ISO 15628 and EN 12834; — the use of the DSRC stack. The LAC is suitable for a range of short-range communication media. This document provides specific definitions regarding the CEN-DSRC stack as specified in EN 15509. Annexes C, D, E and H provide for the use of the Italian DSRC as specified in ETSI/ES 200 674-1, ISO CALM IR ARIB DSRC and WAVE DSRC. This document contains a protocol implementation conformance statement (PICS) proforma in Annex B and transaction examples in Annex F. Annex G highlights how to use this document for the European Electronic Toll Service (EETS). Test specifications are not within the scope of this document.
Perception de télépéage — Communications d'augmentation de localisations pour systèmes autonomes
Le présent document définit les exigences pour une communication à courte portée en vue de mettre en place l'augmentation de localisations dans les systèmes de perception de télépéage (EFC) autonomes. L'augmentation de localisations sert à informer les équipements embarqués (OBE) de leur position géographique et à l'identification d'un objet d'imputation. Le présent document spécifie la mise à disposition des informations de localisation et de direction, et constitue une protection contre la manipulation des équipements embarqués par des équipements en bord de route (RSE) frauduleux. Les communications d'augmentation de localisations (LAC, Localization Augmentation Communication) s'effectuent entre l'équipement embarqué sur un véhicule et un équipement en bord de route fixe. Le présent document s'applique aux équipements embarqués autonomes. Le présent document spécifie des attributs et des fonctions pour l'augmentation de localisations au moyen des services de communication à courte portée fournis par la couche DSRC 7 et met ces attributs et ces fonctions LAC à la disposition des applications LAC au niveau des équipements en bord de route et des équipements embarqués. Les attributs et les fonctions sont spécifiés au niveau des unités de données d'application (ADU, application data unit; voir la Figure 1). Comme cela est représenté à la Figure 1, le présent document s'applique: — à la définition de l'interface d'application entre l'équipement embarqué (OBE) et l'équipement en bord de route (RSE); — à l'interface avec la couche d'application DSRC spécifiée dans l'ISO 15628 et l'EN 12834; — à l'utilisation de la pile de communication DSRC. Les communications d'augmentation de localisations (LAC) conviennent à une gamme de supports de communication à courte portée. Le présent document fournit des définitions spécifiques à la pile CEN-DSRC, comme cela est spécifié dans l'EN 15509. Les Annexes C, D, E et H spécifient l'utilisation de la pile UNI DSRC (Italie) conformément à l'ETSI/ES 200 674-1, l'ISO CALM IR, ARIB DSRC et WAVE DSRC. Le présent document fournit un formulaire de déclaration de conformité d'une mise en œuvre de protocole (PICS, Protocol Implementation Conformance Statement) à l'Annexe B, ainsi que des exemples de transactions à l'Annexe F. L'Annexe G souligne comment utiliser le présent document pour le service européen de télépéage (SET). Le présent document ne s'applique pas aux spécifications d'essai.
General Information
Relations
Standards Content (Sample)
International
Standard
ISO 13141
Second edition
Electronic fee collection —
2024-02
Localization augmentation
communication for autonomous
systems
Perception de télépéage — Communications d'augmentation de
localisations pour systèmes autonomes
Reference number
© ISO 2024
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
Contents Page
Foreword .v
Introduction .vi
1 Scope . 1
2 Normative references . 2
3 Terms and definitions . 3
4 Abbreviated terms . 4
5 Application interface architecture . 5
5.1 General .5
5.2 Services provided.5
5.3 Attributes .6
5.4 Contract and toll context .6
5.5 Use of lower layers .6
5.5.1 Supported DSRC communication stacks .6
5.5.2 The use of the CEN DSRC stack .7
6 Conformance . 7
6.1 Conformance requirements .7
6.2 Conformance statement .7
6.3 Conformance evaluation and testing .7
7 Functions . 7
7.1 General .7
7.2 Functional requirements . .7
7.2.1 Minimum supported transaction details .7
7.2.2 Initialising communication .8
7.2.3 Writing of data .8
7.2.4 Termination of communication .8
7.3 Security .8
7.3.1 General .8
7.3.2 Authentication of RSE — Access credentials .9
7.3.3 Authentication of LAC Data .9
8 Attributes . 9
8.1 General .9
8.2 Data regarding location reference .10
8.3 Operational data .11
8.4 OBE contractual data .11
8.5 Security-related data . 12
9 Transaction model .12
9.1 General . 12
9.2 Initialisation phase . 13
9.2.1 General structure . 13
9.2.2 LAC application-specific contents of the BST . 13
9.2.3 LAC application-specific contents of the VST . 13
9.3 Transaction phase. 13
Annex A (normative) LAC data type specifications . 14
Annex B (normative) PICS proforma for the data elements in the attribute .15
Annex C (informative) ETSI/ES 200 674-1 communication stack usage for LAC applications .23
Annex D (informative) IR communication usage for LAC applications .26
Annex E (informative) ARIB DSRC communication stack usage for LAC applications .27
Annex F (informative) LAC transaction example .29
iii
Annex G (informative) Use of this document for the EETS .31
Annex H (informative) Using the WAVE communication stack for LAC applications .32
Bibliography .35
iv
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 document should be noted. This document was drafted in accordance with the editorial rules of the
ISO/IEC Directives, Part 2 (see www.iso.org/directives).
ISO draws attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). ISO takes no position concerning the evidence, validity or applicability of any claimed patent
rights in respect thereof. As of the date of publication of this document, ISO had not received notice of (a)
patent(s) which may be required to implement this document. However, implementers are cautioned that
this may not represent the latest information, which may be obtained from the patent database available at
www.iso.org/patents. ISO shall not be held responsible for identifying any or all such patent rights.
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 second edition cancels and replaces the first edition (ISO 13141:2015), which has been technically
revised. It also incorporates the Amendment ISO 13141:2015/Amd. 1:2017.
The main changes are as follows:
— Clause 6 has been added, concerning conformance requirements;
— Clause 3 has been updated and ISO/TS 17573-2 has been made the primary source for terms and
definitions;
— data definitions in Clause 8 have been updated, including making reference to ISO 17573-3 as the primary
source;
— imported ASN.1 types with successors (i.e. including all future minor versions) have been used;
— Annex G has been revised to align with the evolution of the European Electronic Toll Service
[19],[20],[21]
(EETS);
— various editorial changes have been made to improve readability.
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.
v
Introduction
On-board equipment (OBE) that uses satellite-based positioning technology to collect data required for
charging for the use of roads operates in an "autonomous" way (i.e. generally without relying on dedicated
roadside infrastructure). However, these autonomous systems can, in some places, need some roadside
infrastructure support for proper identification of charge objects. Such assistance can be required at places
where satellite-based localization accuracy or availability is insufficient or at places where the OBE is
directly informed about the identity of the relevant charge object.
In an interoperable environment, it is essential that this localization information be available in a
standardized way. This document specifies requirements for localization augmentation by dedicated
short-range communication (DSRC) between roadside equipment (RSE) and OBE. This document makes no
assumptions about the operator of the RSE in terms of its role according to ISO 17573-1, i.e. whether the RSE
is operated by an entity in the service provision role or in the toll charging role.
This document has been prepared considering the following points.
— The localization augmentation communication (LAC) serves to transmit localization information to
passing OBE without identifying individual OBE.
— The localization information contains both geographical location independent of charging context, and
context-dependent identification of charge objects.
— A single roadside installation is able to provide localization augmentation for several overlapping
electronic fee collection (EFC) contexts.
— This document is based on the EFC architecture specified in ISO 17573-1.
— The communication applies to all OBE architectures.
— This document is applicable to various DSRC media, especially the CEN DSRC stack.
— The communication supports security services for data origin authentication, integrity and non-
repudiation.
This document specifies an attribute, LacData, which is communicated from the RSE to the OBE by means of
an acknowledged writing service, which is implemented through the SET service of DSRC Layer 7 (ISO 15628
and EN 12834). The LAC application is specified as a self-contained DSRC application with its own application
identifier (AID). Regarding the DSRC communications stack, this document provides specific definitions
regarding the CEN DSRC stack as specified in EN 15509. Annexes C, D, E and H provide for use of the Italian
[9] [3] [10] [11]
DSRC as specified in ETSI/ES 200 674-1. ISO CALM IR, ARIB DSRC and WAVE DSRC.
All data relevant for the LAC application have been put into the attribute LacData, to create a single standard
communications content which is transmitted by LAC RSE and always signed as a whole. LacData can
transport both the geographic coordinates (latitude, longitude and altitude) and the identification of a
specific charge object. All elements of LacData are mandatory, but Null values are specified to allow LAC
installations to transmit only a selection of all specified data elements.
Access credentials are mandatory for writing LacData to protect OBE from non-authentic RSE. LacData are
critical for charge determination and for providing evidence. For these purposes, the authenticators which
are specified can be used to provide for data origin authentication, data integrity and non-repudiation for
LacData. There are two separate authenticator fields specified to allow for separate authentication and non-
repudiation, if required by the institutional arrangements of a toll system.
This document is “minimalist” in the sense that it covers what is required for operational systems and
planned systems.
A test suite for checking an OBE or RSE implementation for conformance with ISO 13141:2015 is specified
in ISO 13140-1:2016. This test suite will be updated to reflect the changes incorporated into this second
edition of ISO 13141.
vi
International Standard ISO 13141:2024(en)
Electronic fee collection — Localization augmentation
communication for autonomous systems
1 Scope
This document establishes requirements for short-range communication for the purposes of augmenting
the localization in autonomous electronic fee collection (EFC) systems. Localization augmentation serves to
inform on-board equipment (OBE) about geographical location and the identification of a charge object. This
document specifies the provision of location and heading information and security means to protect against
the manipulation of the OBE with false RSE.
The localization augmentation communication (LAC) takes place between an OBE in a vehicle and fixed RSE.
This document is applicable to OBE in an autonomous mode of operation.
This document specifies attributes and functions for the purpose of localization augmentation, by making
use of the dedicated short-range communications (DSRC) communication services provided by DSRC Layer 7,
and makes these LAC attributes and functions available to the LAC applications at the RSE and the OBE.
Attributes and functions are specified on the level of application data units (ADUs; see Figure 1).
As depicted in Figure 1, this document is applicable to:
— the application interface definition between OBE and RSE;
— the interface to the DSRC application layer, as specified in ISO 15628 and EN 12834;
— the use of the DSRC stack.
The LAC is suitable for a range of short-range communication media. This document provides specific
definitions regarding the CEN-DSRC stack as specified in EN 15509. Annexes C, D, E and H provide for the
[9] [3] [10]
use of the Italian DSRC as specified in ETSI/ES 200 674-1, ISO CALM IR, ARIB DSRC and WAVE DSRC.
[11]
This document contains a protocol implementation conformance statement (PICS) proforma in Annex B and
transaction examples in Annex F. Annex G highlights how to use this document for the European Electronic
Toll Service (EETS).
Test specifications are not within the scope of this document.
Key
AP application process
ADU application data unit
LAC localization augmentation communication
OBE on-board equipment
RSE roadside equipment
Figure 1 — The LAC application interface
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/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 14906:2022, Electronic fee collection — Application interface definition for dedicated short-range
communication
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, Road transport and traffic telematics — Dedicated Short Range Communication (DSRC) — DSRC
application layer
EN 15509:2023, Electronic fee collection — Interoperability application profile for DSRC
ISO 17573-3:2023, Electronic fee collection — System architecture for vehicle-related tolling — Part 3: Data
dictionary
NIMA Technical Report TR8350.2 version 3, Department of Defense World Geodetic System 1984, Its Definition
and Relationships With Local Geodetic Systems
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]
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
authentication
security mechanism allowing verification of the provided identity
[SOURCE: EN 301 175 V1.1.1:1998, 3]
3.4
authenticator
data, possibly encrypted, that is used for authentication (3.3)
[SOURCE: ISO/TS 17573-2:2020, 3.16]
3.5
charge object
geographic or road related object for the use of which a charge is applied
[SOURCE: ISO/TS 17573-2:2020, 3.31]
3.6
data integrity
property that data has not been altered or destroyed in an unauthorized manner
[SOURCE: ISO 7498-2:1989, 3.3.21]
3.7
on-board equipment
all required equipment on-board a vehicle for performing required electronic fee collection (EFC) functions
and communication services
[SOURCE: ISO/TS 17573-2:2020, 3.126]
3.8
roadside equipment
fixed or movable electronic fee collection (EFC) equipment located along or on the road
Note 1 to entry: Movable RSE can be mounted temporarily along the road or in a vehicle.
[SOURCE: ISO/TS 17573-2:2020, 3.161]
3.9
service primitive
elementary communication service provided by the application layer protocol to the application processes
[SOURCE: ISO/TS 17573-2:2020, 3.173]
3.10
toll charger
entity which levies toll for the use of vehicles in a toll domain
[SOURCE: ISO/TS 17573-2:2020, 3.194]
3.11
toll context
logical view as defined by attributes (3.2) and functions of the basic elements of a toll scheme consisting of
a single basic tolling principle, a spatial distribution of the charge objects (3.5) and a single behaviour of the
related front end
[SOURCE: ISO/TS 17573-2:2020, 3.196]
3.12
toll service provider
entity providing toll services in one or more toll domains
[SOURCE: ISO/TS 17573-2:2020, 3.206]
3.13
transaction
whole of the exchange of information between two physically separated communication facilities
[SOURCE: ISO/TS 17573-2:2020, 3.211]
4 Abbreviated terms
For the purposes of this document, the following abbreviated terms apply.
AC-CR access credentials
ADU application data unit
AID application identifier
ASN.1 abstract syntax notation one
BST beacon service table
CCC compliance check communication
DSRC dedicated short-range communication
EID Element identifier
EFC electronic fee collection
ETRF European terrestrial reference frames
IR infrared
ITRF international terrestrial reference frames
IUT implementation under test
LAC localization augmentation communication
MAC message authentication code
OBE on-board equipment
PICS protocol implementation conformance statement
PSC provider service context
RSE roadside equipment
TC toll charger
TSP toll service provider
VST vehicle service table
WGS84 World Geodetic System 1984
5 Application interface architecture
5.1 General
This clause gives an insight into the LAC architecture by identifying the functions, the use of DSRC
communication primitives, and the attributes addressed. A detailed description of the functions is given in
Clause 7, while details of the attributes are in Clause 8.
The LAC application interface has been designed to make use of the CEN DSRC communication stack, via the
application layer as specified in ISO 15628 and EN 12834. For other identified DSRC communication media,
detailed mappings to corresponding services are given in Annexes C, D, E and H.
5.2 Services provided
The LAC application interface offers the following services to LAC applications:
— writing of data in order for the RSE to communicate location data to the OBE;
— authentication of the RSE by the OBE by means of access credentials.
There is no read service provided within the LAC communication. The RSE transmits data to the OBE
using the underlying acknowledged communication services, to verify that the data are indeed properly
transmitted over the DSRC interface.
The above services are realized by means of protocol exchanges performed by means of communication
services and transactions as described in Clause 9.
The services are provided by the following functions:
— the “Initialise communication” function, which shall be used to establish the LAC communication link
between the RSE and OBE;
— the “Write data” function, which shall be used to send LAC attributes to the OBE;
— the “Terminate communication” function, which shall be used to terminate the LAC communication.
5.3 Attributes
There is a single attribute specified for localization augmentation. This attribute contains a set of data
which enables the OBE to determine its location with better accuracy and availability or to directly receive a
charge object identification related to the local toll context. This set of data contains:
— geographic coordinates (latitude, longitude and altitude);
— a charge object reference.
When the RSE sends data to the set [i.e. write value(s) of the addressed attribute(s)] in the OBE, it shall
transmit geographic coordinates or a charge object reference or both.
5.4 Contract and toll context
Regarding LAC, the OBE shall identify itself in the initialisation phase with a single LAC context mark in the
VST. This context mark identifies the user contract in terms of the service provider, type of contract and
version information. This information enables the RSE to decide whether the OBE carries a contract which it
supports, and if so, to choose the corresponding security elements.
An RSE can provide the OBE with localization augmentation for several overlapping contexts simultaneously
by writing the LAC attribute (which includes the applicable toll context) several times in one transaction.
NOTE The LAC operates in a broadcast fashion, where the RSE has only minimal information about the OBE and
is not able to assess the liability of a vehicle for tolls. For this reason, the OBE can receive LAC information which is not
applicable.
5.5 Use of lower layers
5.5.1 Supported DSRC communication stacks
The LAC application interface makes use of the CEN DSRC communication stack as described in Table 1.
Other communication media can be used as listed in Table 1 if an equivalent mapping to corresponding
services is provided. Detailed examples are provided in Annexes C, D, E and H.
Table 1 — Supported short-range communication stacks
Medium Application layer Lower layers Detailed specifications
a
CEN DSRC ISO 15628 EN 12795 and
Specification in 5.5.2
a
and EN 12834 EN 12253
Italian DSRC ES 200 674–1 (2013, ES 200 674–1 (2013,
Clause 11 and Clauses 7 to 10 and Implementation example in Annex C
[9] [9]
Annex D) Annex D)
ISO CALM IR ISO 15628 ISO 21214 Implementation example in Annex D
a
and EN 12834
[10] [10]
ARIB DSRC ARIB STD-T75 ARIB STD-T75 Implementation example in Annex E
[23]
and ISO 15628 ITU-R.M1453–2
[15] [13]
WAVE DSRC IEEE 1609.11 IEEE 1609.3 Implementation example in Annex H
[14]
ISO 15628 IEEE 1609.4
[11]
IEEE 802.11
a [24] [25] [23]
EN 12795 and EN 12253 have been adopted in ITU-R.M 1453–2.
If more than one communication medium is implemented in an OBE, the OBE shall respond to RSE
communications on the same medium as used by the RSE.
5.5.2 The use of the CEN DSRC stack
The LAC application shall be used with the CEN DSRC communication stack in the following ways:
— the OBE shall conform to EN 15509:2023, 6.1.2;
— the RSE shall conform to EN 15509:2023, 6.2.2.
NOTE Conformance with EN 15509 implies conformance of the DSRC stack with ISO 15628 and EN 12834
[24] [25]
regarding the application layer, and EN 12795 and EN 12253 for the lower layers.
6 Conformance
6.1 Conformance requirements
The following requirements apply to OBE and RSE:
— functions (including security functions) shall be as specified in Clause 7;
— application data shall be as specified in Clause 8 and supplemented by Annex A; and
— transaction model shall be as specified in Clause 9.
6.2 Conformance statement
A supplier of OBE that claims conformity of its OBE to the requirements specified in this document shall
provide a statement of conformance by completing the PICS proforma as provided in B.3 and B.4.
A supplier of RSE that claims conformity of its RSE to the requirements specified in this document shall
provide a statement of conformance to this document by completing the PICS proforma as provided in B.3
and B.5.
6.3 Conformance evaluation and testing
Suppliers of OBE or RSE claiming conformity of their equipment to this document for the communication
medium CEN DSRC can perform their conformity tests according to specifications laid down in ISO 13140.
NOTE The use of ISO 13140 implies the use of other underlying test standards for evaluation of conformance to
this document.
7 Functions
7.1 General
In the view of the OBE, the LAC communication is a read-only data exchange. There is neither a request of
OBE capabilities nor feedback from the OBE regarding the received data or commands. Consequently, the
OBE shall support all standardized LAC RSE transaction sequences.
The RSE shall only broadcast, within the context of LAC transactions, attributes specified in this document.
7.2 Functional requirements
7.2.1 Minimum supported transaction details
All functions specified in this subclause shall be available on the OBE.
For CEN DSRC, the functions shall be provided by the DSRC application layer as specified in ISO 15628 and
EN 12834 (services INITIALISATION, SET and RELEASE).
Only the functions for CEN-DSRC are specified in 7.2.2 to 7.2.4. For other supported media according to 5.5.1,
equivalent functionality shall be provided; for ETSI/ES 200 674-1 5,8 GHz microwave DSRC, see Annex C,
for CALM infrared DSRC, see Annex D, for ARIB microwave DSRC, see Annex E, and for WAVE DSRC, see
Annex H.
7.2.2 Initialising communication
Initialisation of the communication between the RSE and the OBE shall be initiated by the RSE, by means of
the invocation of an initialisation request by the RSE. After successful initialisation, the function “Initialise
communication” shall notify the applications on the RSE and OBE.
The initialisation notification on the OBE shall carry at least the identity of the beacon (e.g. the beacon serial
number) and absolute time. The initialisation notification on the RSE shall carry the LAC application identity
and also the data required for the security services (e.g. random number and key identifier).
The function “Initialise communication” shall be provided by the application layer INITIALISATION services,
as specified in ISO 15628 and EN 12834. It is specified in Annex A (see LacInitialiseCommRequst and
LacInitialiseCommResponse).
7.2.3 Writing of data
The function “Write data” shall be provided by the application layer SET service as specified in ISO 15628
and EN 12834. It is specified in Annex A (see LacDataTxRequest and LacDataTxResponse).
NOTE 1 The “mode” parameter in the LacDataTxRequest indicates whether the corresponding response is
expected or not. If mode = false, the response primitive is not used and the reception is only acknowledged by the OBE
on lower layers.
In the SET service primitives, iid shall not be used.
NOTE 2 The invocation of a service primitive by an application process implicitly calls upon and use services
offered by the lower protocol layers.
The SET shall always carry access credentials.
7.2.4 Termination of communication
The RSE may terminate the communication on the application level with the OBE with the function
“Terminate communication”, by means of the invocation of a release request by the RSE.
NOTE A termination of the communication on the link level is outside of the scope of this document.
The function “Terminate communication” shall be provided by the application layer service EVENT-REPORT,
as specified in ISO 15628 and EN 12834. It is specified in Annex A (see LacTerminateComm).
7.3 Security
7.3.1 General
Security is an essential part of LAC applications. This document provides for both communication-
related security services and communication-transparent data elements, which may provide security
characteristics.
This document provides for a “Write data” function and uses access credentials as a mandatory
communication security provision. Access credentials provide for protection against unauthorized
writing of LAC data, and hence for authentication of the LAC RSE and the LAC data to the OBE. The detailed
implementations of the communication security services are media-specific (see 7.3.2 and 7.3.3 for CEN
DSRC and Annexes C, D, E and H for other communication media).
NOTE 1 Authentication of the OBE to the RSE according to ISO 14906 is not supported as the identity of the OBE and
contract are not relevant for the LAC application.
This document provides for data elements, which may provide data origin authentication, data integrity and
non-repudiation characteristics to the LAC data. The LAC application is transparent to these authenticators,
which may be stored together with the other LAC data elements as a data packet, which is either protected
against forgery or protected against repudiation (between the user and the LAC operator, for example) or
protected against both.
NOTE 2 This document does not provide for an encryption service. No privacy-sensitive data are transferred by
LAC.
7.3.2 Authentication of RSE — Access credentials
Access credentials shall be used to manage access to the LAC attribute. Access credentials are mandatory.
The “Write data” function shall always carry access credentials.
The CEN DSRC OBE shall support the calculation of access credentials according to security level 1, as
specified in ISO 14906:2022, 7.1.4.
The CEN DSRC RSE shall be able to calculate access credentials according to security level 1, as specified in
ISO 14906:2022, 7.1.4.
Access credentials are specified as being of ASN.1 type OCTET STRING. This only pertains to the ASN.1 syntax;
the semantics are media-dependent.
7.3.3 Authentication of LAC Data
The data elements macTc and mac2 (see 8.5) may contain authenticators, as well as key references which are
used for the calculation of those authenticators, and are provided to guarantee data origin authentication,
integrity and non-repudiation characteristics to the LAC data.
The two data elements are provided to allow for separate elements for authentication and non-repudiation, if
required. The LAC application is transparent to these authenticators, which implies that it supports various
system security concepts.
The data element macTc shall be of type MacTc.
The data element mac2 shall be of ASN.1 type OCTET STRING. The semantics of the data elements are media-
independent.
8 Attributes
8.1 General
Within the LAC context, the attributes and data elements listed in Table 2 shall be made available.
Table 2 — LAC attributes
a b
AttributeID Attribute Data element Length in Octets Remarks
LacContextMark contractProvider
n.a. 3
typeOfContract
contextVersion
LacData lacOperator
54 3
rseId
latitude
4 in micro degrees
longitude
4 in micro degrees
altitude
2 resolution 0,25 m
tollCharger
chargeObject
distanceToObject
lacTime
macTc
mac2
87-127 ReservedForPrivateUse — —
a
The assignment of attribute IDs is aligned with ISO 17573-3, ISO 14906 and ISO 12813. Attributes 87 to 127 are assigned for
private use. All other remaining IDs are reserved for future use.
b
Including the length determinant as specified in ISO/IEC 8825-2 (packed encoding rules for ASN.1 are used in this document).
In case of discrepancies between the length and the ASN.1 module, the ASN.1 module specified in Annex A shall take precedence.
The data primitive lacContextMark shall be part of ApplicationContextMark as specified in Annex A.
lacContextMark shall be of data type LacContextMark.
NOTE lacContextMark is not an addressable attribute. It is part of the VST and can neither be read nor written
by the RSE as part of the LAC application.
In the following subclauses, LAC attributes and data elements are specified in terms of:
— the names of the data elements forming the LAC attributes;
— the semantic definition of the data element; and
— informative remarks, including references to other standards.
The specification of the corresponding data types in ASN.1 is provided in Annex A.
8.2 Data regarding location reference
To translate longitude, latitude and altitude coordinates to the corresponding real position on Earth or vice
versa, the geodetic datum shall be WGS84(G1150), according to NIMA TR8350.2 version 3, per default unless
another Earth-centred, Earth-fixed polar coordinate geodetic datum is agreed mutually by the toll charger
(TC) and toll service provider (TSP).
Furthermore, by default any Earth-centred, Earth-fixed polar coordinate geodetic datum may be used, as
long as the maximum datum displacement relative to the geodetic datum prescribed is acceptable to the TC
of the related toll domain.
The maximum tolerated datum displacement, also called datum shift, should not exceed 0,4 m.
NOTE 1 The recommended maximum tolerated displacement allows, for example, for using one of the International
Terrestrial Reference Frames (ITRF), the Russian PZ90.2 or one of the European Terrestrial Reference Frames (ETRF)
as geodetic datums alternative to the WGS84.
The calculated datum displacement should be determined according to the definitions in ASME Y14.5 – 2009.
[8]
The data element latitude shall contain the latitudinal coordinate of the centre of the road surface covered
by the specific LAC implementation, value in microdegrees. For values > 0 = north, < 0 = south, absolute
value shall not exceed 90 degrees.
The data element longitude shall contain the longitudinal coordinate of the centre of the road surface
covered by the specific LAC implementation, value in microdegrees. For values > 0 = east, < 0 = west, absolute
value shall not exceed 180 degrees.
The data element altitude shall contain the altitude according to definition of the chosen geodetic model of
the centre of the road surface covered by the specific LAC implementation, where a unit is 0,25 m.
In case no geographic coordinates are provided, a coding of all zero shall be used (latitude, longitude and
altitude equal zero).
NOTE 2 The location indicated by the coding for “no geographic coordinates provided” is not on land surface and
does not need to be supported.
The data element chargeObject shall identify the charge object for which LAC is operated, according to the local
definition of the TC owning the respective toll scheme. The data element contains chargeObjectDesignation
with the same syntax and semantics as in chargeObjectDesignation specified in ISO 17573-3. The second
data element regimeId is kept for backward compatibility and shall no longer be used, i.e. shall be zero.
NOTE 3 The data element tollContext (of type Provider) in tollCharger together with
chargeObjectDesignation from chargeObject provide the information contained in ChargeObjectId as used and
as specified in ISO 17573-3.
In case no TC-dependent information is provided, a coding of all zero shall be used (tollCharger and
chargeObject equal to zero).
NOTE 4 The data element chargeObject in combination with tollCharger can be used to identify any kind of
charge object, e.g. road section, passage of cordon. Identification of lanes can be provided in accordance with the
restrictions of the communication medium.
The data element distanceToObject, shall contain the distance, in metres, to the charge object as identified
by the element chargeObject, from the point of operation of the LAC. Negative values indicate that the charge
object precedes the RSE in the sense of direction of traffic.
NOTE 5 In order to avoid charging errors, it is advisable to not allow vehicles to exit to another road after receiving
the LAC message and without using the charge object.
8.3 Operational data
The data element lacOperator shall identify the organization that operates LAC, i.e. the entity responsible
for data content of the LAC transaction. The data element is as specified in ISO 17573-3. It contains the
country code and the Id of the operator assigned on a national basis.
The data element rseId shall contain an operator-specific identification of the RSE which operates LAC.
The data element tollCharger shall identify the TC which owns the toll scheme for which LAC is operated.
The data element is as specified in ISO 17573-3.
The data element lacTime shall contain the time at which the LAC transaction occurred. The data element is
as specified in ISO 17573-3.
8.4 OBE contractual data
The data element lacContextMark shall identif
...
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...