oSIST prEN ISO 12813:2022
(Main)Electronic fee collection — Compliance check communication for autonomous systems (ISO/DIS 12813:2022)
Electronic fee collection — Compliance check communication for autonomous systems (ISO/DIS 12813:2022)
This document defines requirements for short-range communication for the purposes of compliance checking in autonomous electronic fee collecting systems. Compliance checking communication (CCC) takes place between a road vehicle's on-board equipment (OBE) and an interrogator (roadside mounted equipment, mobile device or hand-held unit), and serves to establish whether the data that are delivered by the OBE correctly reflect the road usage of the corresponding vehicle according to the rules of the pertinent toll regime.
The operator of the compliance checking interrogator is assumed to be part of the toll charging role as defined in ISO 17573-1. The CCC permits identification of the OBE, vehicle and contract, and verification of whether the driver has fulfilled his obligations and the checking status and performance of the OBE. The CCC reads, but does not write, OBE data.
This document is applicable to OBE in an autonomous mode of operation; it is not applicable to compliance checking in dedicated short-range communication (DSRC)-based charging systems.
It defines data syntax and semantics, but not a communication sequence. All the attributes defined herein are required in any OBE claimed to be compliant with this document, even if some values are set to "not defined" in cases where certain functionality is not present in an OBE. The interrogator is free to choose which attributes are read in the data retrieval phase, as well as the sequence in which they are read. In order to achieve compatibility with existing systems, the communication makes use of the attributes defined in ISO 14906 wherever useful.
The CCC is suitable for a range of short-range communication media. Specific definitions are given for the CEN-DSRC as specified in EN 15509, as well as for the use of ISO CALM IR, the Italian DSRC as specified in ETSI ES 200 674-1, ARIB DSRC and WAVE DSRC as alternatives to the CEN-DSRC. The attributes and functions defined are for compliance checking by means of the DSRC communication services provided by DSRC application layer, with the CCC attributes and functions made available to the CCC applications at the roadside equipment (RSE) and OBE. The attributes and functions are defined on the level of application data units (ADU).
The definition of the CCC includes:
— the application interface between OBE and RSE (as depicted in Figure 2);
— use of the generic DSRC application layer as specified in ISO 15628 and EN 12834;
— CCC data type specifications given in Annex A;
— a protocol implementation conformance statement (PICS) proforma is given in Annex B;
— use of the CEN-DSRC stack as specified in EN 15509, or other equivalent DSRC stacks as described in Annex C, Annex D, Annex E and Annex F;
— security services for mutual authentication of the communication partners and for signing of data (see Annex H);
— an example CCC transaction is presented in Annex G;
— the informative Annex I highlights how to use this document for the European electronic toll service (as defined in Commission Decision 2009/750/EC).
Test specifications are not within the scope of this document.
Elektronische Gebührenerhebung - Kommunikation zur Übereinstimmungsprüfung für autonome Systeme (ISO/DIS 12813:2022)
Perception de télépéage - Communication de contrôle de conformité pour systèmes autonomes (ISO/DIS 12813:2022)
Le présent document définit les exigences relatives aux communications à courte portée aux fins de contrôle de conformité dans les systèmes de perception électronique de télépéage autonomes. La communication de contrôle de conformité (CCC, Compliance Checking Communication) survient entre l'équipement embarqué d'un véhicule routier et un interrogateur externe (équipement en bord de route, appareil mobile ou dispositif portable) et permet de déterminer si les données fournies par l'équipement embarqué reflètent correctement l'usage du réseau routier par le véhicule correspondant selon les règles du régime de péage applicable.
L'exploitant de l'interrogateur de contrôle de conformité est supposé participer au rôle Perception du péage défini dans l'ISO 17573-1. L'application CCC permet d'identifier l'équipement embarqué, le véhicule et le contrat, de vérifier que le conducteur a bien rempli ses obligations et de déterminer l'état de fonctionnement et la performance de l'équipement embarqué. L'application CCC lit, mais n'écrit pas les données de l'équipement embarqué.
Le présent document s'applique aux équipements embarqués autonomes; il ne s'applique pas au contrôle de conformité dans les systèmes de taxation reposant sur des communications dédiées à courte portée (DSRC).
Il définit la syntaxe et la sémantique des données, mais ne définit pas de séquence de communication. Tous les attributs qui y sont définis sont exigés dans tout équipement embarqué revendiqué conforme au présent document, même si certaines valeurs sont définies comme étant «non définies» dans les cas où certaines fonctionnalités ne sont pas présentes dans un équipement embarqué donné. L'interrogateur est libre de choisir quels attributs sont lus, ainsi que l'ordre dans lequel ils sont lus. Afin de permettre la compatibilité avec les systèmes existants, la communication utilise les attributs définis dans l'ISO 14906 chaque fois que cela est utile.
L'application CCC est adaptée à toute une variété de supports de communication à courte portée. Des définitions spécifiques sont données pour la pile de communication CEN-DSRC spécifiée dans l'EN 15509, ainsi que pour l'utilisation des piles ISO CALM IR, UNI DSRC (ETSI ES 200 674-1) et ARIB DSRC comme alternatives à CEN-DSRC. Les attributs et fonctions définis sont destinés au contrôle de conformité via les services de communication DSRC fournis par la couche d'application DSRC, à l'aide des attributs et fonctions CCC mis à la disposition des applications CCC sur l'équipement en bord de route (RSE, Road-Side Equipment) et l'équipement embarqué. Les attributs et fonctions sont définis au niveau des unités de données d'application (ADU, Application Data Unit).
La définition de la communication CCC inclut:
— l'interface d'application entre l'équipement embarqué (OBE) et l'équipement en bord de route (RSE) comme décrit en Figure 2;
— l'utilisation de la couche d'application DSRC générique spécifiée dans l'ISO 15628 et l'EN 12834;
— les spécifications de types de données CCC données à l'Annexe A;
— un formulaire de déclaration de conformité d'une mise en œuvre de protocole (PICS, Protocol Implementation Conformance Statement) est fourni à l'Annexe B;
— l'utilisation de la pile CEN-DSRC selon l'EN 15509 ou d'autres piles de communication DSRC équivalentes comme décrit à l'Annexe C, l'Annexe D, l'Annexe E et l'Annexe F;
— des services de sécurité dans le cadre de l'authentification mutuelle des partenaires de communication et de la sig
Elektronsko pobiranje pristojbin - Komunikacija za potrditev skladnosti avtonomnih sistemov (ISO/DIS 12813:2022)
General Information
RELATIONS
Standards Content (sample)
SLOVENSKI STANDARD
oSIST prEN ISO 12813:2022
01-julij-2022
Elektronsko pobiranje pristojbin - Komunikacija za potrditev skladnosti
avtonomnih sistemov (ISO/DIS 12813:2022)
Electronic fee collection — Compliance check communication for autonomous systems
(ISO/DIS 12813:2022)Elektronische Gebührenerhebung - Kommunikation zur Übereinstimmungsprüfung für
autonome Systeme (ISO/DIS 12813:2022)
Perception de télépéage - Communication de contrôle de conformité pour systèmes
autonomes (ISO/DIS 12813:2022)
Ta slovenski standard je istoveten z: prEN ISO 12813
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 12813: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 12813:2022
---------------------- Page: 2 ----------------------
oSIST prEN ISO 12813:2022
DRAFT INTERNATIONAL STANDARD
ISO/DIS 12813
ISO/TC 204 Secretariat: ANSI
Voting begins on: Voting terminates on:
2022-04-26 2022-07-19
Electronic fee collection — Compliance check
communication for autonomous systems
Perception de télépéage — Communication de contrôle de conformité pour systèmes autonomes
ICS: 35.240.60; 03.220.20This 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 12813: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 12813:2022
© ISO 2022 – All rights reserved
ISO/DIS 12813:2022(E)
ISO/TC 204
ISO/DIS 12813:2022(E)
Secretariat: ANSI
Electronic fee collection — Compliance check communication for
autonomous systems
Perception de télépéage — Communication de contrôle de conformité pour systèmes autonomes
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
Published in Switzerland
© ISO 2022 – All rights reserved
---------------------- Page: 4 ----------------------
oSIST prEN ISO 12813:2022
ISO/DIS 12813:2022 (E)
Contents Page
Foreword .......................................................................................................................................................................... v
Introduction ................................................................................................................................................................... vi
1 Scope .................................................................................................................................................................... 1
2 Normative references .................................................................................................................................... 2
3 Terms and definitions ................................................................................................................................... 3
4 Abbreviated terms .......................................................................................................................................... 5
5 Application interface architecture............................................................................................................ 6
5.1 General ................................................................................................................................................................ 6
5.2 Services provided ............................................................................................................................................ 6
5.3 Attributes ........................................................................................................................................................... 6
5.4 Toll context ........................................................................................................................................................ 7
5.5 Use of lower layers .......................................................................................................................................... 7
5.5.1 Supported DSRC communication stacks ................................................................................................. 7
5.5.2 Use of the CEN-DSRC stack ........................................................................................................................... 8
6 Functions ............................................................................................................................................................ 8
6.1 Functions in detail .......................................................................................................................................... 8
6.1.1 General ................................................................................................................................................................ 8
6.1.2 Initialise communication ............................................................................................................................. 8
6.1.3 Data retrieval .................................................................................................................................................... 8
6.1.4 Authenticated data retrieval ....................................................................................................................... 9
6.1.5 Driver notification .......................................................................................................................................... 9
6.1.6 Terminate communication .......................................................................................................................... 9
6.1.7 Test communication ....................................................................................................................................... 9
6.2 Security ............................................................................................................................................................... 9
6.2.1 General ................................................................................................................................................................ 9
6.2.2 Authentication/non-repudiation ........................................................................................................... 10
6.2.3 Access credentials ........................................................................................................................................ 10
7 Attributes ........................................................................................................................................................ 10
7.1 General ............................................................................................................................................................. 10
7.2 Data regarding identification .................................................................................................................. 12
7.3 Data regarding status ................................................................................................................................. 12
7.4 Data regarding vehicle ............................................................................................................................... 20
8 Transaction model ....................................................................................................................................... 22
8.1 General ............................................................................................................................................................. 22
8.2 Initialisation phase ...................................................................................................................................... 22
8.2.1 Initialisation request .................................................................................................................................. 22
8.2.2 CCC application-specific contents of BST ............................................................................................. 23
8.2.3 CCC application-specific contents of VST ............................................................................................. 23
8.3 Transaction phase........................................................................................................................................ 23
Annex A (normative) CCC data type specifications ....................................................................................... 24
Annex B (normative) PICS proforma .................................................................................................................. 25
iii© ISO 2022 – All rights reserved
---------------------- Page: 5 ----------------------
oSIST prEN ISO 12813:2022
ISO/DIS 12813:2022 (E)
Annex C (informative) ETSI ES 200 674-1 communication stack usage for CCC applications ....... 34
Annex D (informative) Using the IR DSRC communication stack (CALM IR) for CCCapplications .................................................................................................................................................... 37
Annex E (informative) Using the ARIB DSRC communication stack for CCC applications ............... 38
Annex F (informative) Using the WAVE communication stack for CCC applications ......................... 40
Annex G (informative) Example CCC transaction ........................................................................................... 43
Annex H (informative) Security considerations ............................................................................................. 46
Annex I (informative) Use of this document for the EETS ........................................................................... 51
Bibliography ................................................................................................................................................................. 53
© ISO 2022 – All rights reserved---------------------- Page: 6 ----------------------
oSIST prEN ISO 12813:2022
ISO/DIS 12813:2022 (E)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national
standards bodies (ISO member bodies). The work of preparing International Standards is normally
carried out through ISO technical committees. Each member body interested in a subject for which a
technical committee has been established has the right to be represented on that committee.
International organizations, governmental and non-governmental, in liaison with ISO, also take part in
the work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all
matters of electrotechnical standardization.The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the
different types of ISO documents should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of
any patent rights identified during the development of the document will be in the Introduction and/or
on the ISO list of patent declarations received (see www.iso.org/patents).Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to the
World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see
www.iso.org/iso/foreword.html.This document was prepared by Technical Committee ISO/TC 204, Intelligent transport systems, in
collaboration with the European Committee for Standardization (CEN) Technical Committee
CEN/TC 278 Intelligent transport systems, in accordance with the Agreement on technical cooperation
between ISO and CEN (Vienna Agreement).This third edition cancels and replaces the second edition (ISO 12813:2019) ), which has been subject
to a minor revision.The main changes compared to the previous edition are as follows:
— 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 2022 – All rights reserved
---------------------- Page: 7 ----------------------
oSIST prEN ISO 12813:2022
ISO/DIS 12813:2022 (E)
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. without relying on dedicated roadside
infrastructure). The OBE will record the amount of road usage in all toll charging systems it passes
through.This document defines requirements for dedicated short-range communication (DSRC) between OBE
and an interrogator for the purpose of checking compliance of road use with a local toll regime. It
assumes an electronic fee collection (EFC) services architecture according to ISO 17573-1. See Figure 1.
Figure 1 — Compliance check communication in EFC architecture according to ISO 17573-1
Toll chargers have the need to check whether the road is used in compliance with the rules in the local
toll regime. One way of checking compliance is to observe a passing vehicle and to interrogate the OBE.
This interrogation happens under control of an entity responsible for toll charging (see Figure 1),
accomplished via short-range communication between an interrogator at roadside or in another vehicle
(operated by a competent enforcement agency) and the OBE. In an interoperable environment, it is
essential that this interrogation communication be standardized such that every operator of compliance
checking equipment can check all passing OBE. For that purpose, this document defines attributes
required on all OBE for reading by an interrogator.This document has been prepared to fulfil the following statements:
a) Collected evidence can be used as court proof. Data is indisputable and secured such that the
operator of the compliance checking interrogator can prove the integrity and authenticity of the
data in case of dispute.b) The data required for compliance checking is read only, since the operator of the interrogator does
not interfere with the working of the OBE.c) All attributes, standardized at the time of personalisation of the OBE, are present in the OBE such
that an operator of an interrogator essentially can read the same data from all OBE independent of
type and make. In case an attribute does not make sense in a certain OBE implementation, a value
© ISO 2022 – All rights reserved---------------------- Page: 8 ----------------------
oSIST prEN ISO 12813:2022
ISO/DIS 12813:2022 (E)
assignment for “not applicable” or “not defined” is provided in each case. An OBE compliant to the
first edition will not answer with such a response for new attributes introduced in the current
edition of this document.d) The attributes, derived from the individual toll regime, are of general importance for all toll system
types (motorway tolling, area tolling, tolls for ferries, bridges, tunnels, cordon pricing, etc.).
e) The attributes apply to all OBE architectures, and especially to both thin (edge-light) and fat (edge
heavy) client architectures. The interrogator is intended to receive essentially the same information
irrespective of the type of OBE.It is assumed that the prime objective of the operator of the compliance checking interrogation is to
check whether the user has fulfilled his obligations, especially:— whether the OBE is mounted in the correct vehicle;
— whether the classification data transmitted by the OBE are correct; and
— whether the OBE is in operational condition, both in a technical and a contractual sense.
Regarding the last point of the above list, on the operational status of OBE, the following model is
assumed.As long as the OBE signals to the user correct operational status (“green”), the service provider takes
full responsibility for the correct operation of the OBE and for the payment by the user. Hence, as long
as the OBE signals “green” and the user fulfils its other obligations (e.g. entering correct classification
data and not tampering with the OBE), the user can expect the OBE to serve as a valid payment means.
As soon as the OBE signals an invalid operational status (“red”) — either set by the central system of the
service provider (e.g. because the user account is negative), by internal mechanisms of the OBE itself
(e.g. because of a detected defect or an outdated data set) or a user manipulation with such result — the
user knows that the OBE is no longer a valid payment means. The user then has to use alternative
means of toll declaration or payment until the problem is remedied and the OBE is “green” again .
Ultimately, the policy of when to signal “green” or “red” is defined by the service provider in accordance
with the requirements defined by the toll charger(s).In the case where the OBE status turns “red”, the user has to take action, declare road usage subject to
fees or pay by some alternative means as soon as practicable. Until he does, the user is in a potentially
non-compliant situation. In order to allow a judgment to be made as to whether or not a user has taken
the appropriate action within an acceptable period of time, information is provided by this document
not only on the “green/red” operational status but also on the length of time that the OBE has been in its
current status.Different toll contexts can overlap geographically. A user could be liable in several toll contexts at once,
e.g. for a nationwide distance-dependent road tax and a local city access pricing scheme — a fact of
which the user might not in all cases be aware. This document builds on the concept that regarding
compliance, there is no notion of toll context as far as possible (see especially 5.4). It is within the
responsibility of the service provider to resolve issues with overlapping toll contexts and to distil all
information into a binary “red/green” message to the user.A secondary objective of the operator of the compliance checking interrogator might be to collect data
on the performance of the OBE, e.g. in order to check for the correct technical functioning. Since
In this case, “red” and “green” are used in the abstract, symbolic sense, and do not imply any physical implementation.
The design of the user interface of the OBE is implementation-dependent, and several methods for signalling “red” or
“green” are conceivable.vii
© ISO 2022 – All rights reserved
---------------------- Page: 9 ----------------------
oSIST prEN ISO 12813:2022
ISO/DIS 12813:2022 (E)
different OBE can work according to quite different principles, the possibilities for doing this in a
standardized way are quite limited. This document contains some provisions for this task (e.g. the
attributes CommunicationStatus, GnssStatus, DistanceRecordingStatus), but otherwise assumes that toll
chargers monitor correct recording by comparing observed traffic (e.g. with cameras) with usage data
received from service providers.This document has been prepared with the intention to be “minimalist” in the sense that it covers what
is required by operational systems and systems planned in the foreseeable future.
A test suite for checking an OBE or RSE implementation for compliance with this document is defined in
the corresponding edition of ISO 13143-1 and ISO 13143-2.viii
© ISO 2022 – All rights reserved
---------------------- Page: 10 ----------------------
oSIST prEN ISO 12813:2022
DRAFT INTERNATIONAL STANDARD ISO/DIS 12813:2022(E)
Electronic fee collection — Compliance check communication for
autonomous systems
1 Scope
This document defines requirements for short-range communication for the purposes of compliance
checking in autonomous electronic fee collecting systems. Compliance checking communication (CCC)
takes place between a road vehicle's on-board equipment (OBE) and an interrogator (roadside mounted
equipment, mobile device or hand-held unit), and serves to establish whether the data that are
delivered by the OBE correctly reflect the road usage of the corresponding vehicle according to the rules
of the pertinent toll regime.The operator of the compliance checking interrogator is assumed to be part of the toll charging role as
defined in ISO 17573-1. The CCC permits identification of the OBE, vehicle and contract, and verification
of whether the driver has fulfilled his obligations and the checking status and performance of the OBE.
The CCC reads, but does not write, OBE data.This document is applicable to OBE in an autonomous mode of operation; it is not applicable to
compliance checking in dedicated short-range communication (DSRC)-based charging systems.
It defines data syntax and semantics, but not a communication sequence. All the attributes defined
herein are required in any OBE claimed to be compliant with this document, even if some values are set
to “not defined” in cases where certain functionality is not present in an OBE. The interrogator is free to
choose which attributes are read in the data retrieval phase, as well as the sequence in which they are
read. In order to achieve compatibility with existing systems, the communication makes use of the
attributes defined in ISO 14906 and the ISO 17573 series (all parts) wherever useful.
The CCC is suitable for a range of short-range communication media. Specific definitions are given for
the CEN-DSRC as specified in EN 15509, as well as for the use of ISO CALM IR, the Italian DSRC as
specified in ETSI ES 200 674-1, ARIB DSRC and WAVE DSRC as alternatives to the CEN-DSRC. The
attributes and functions defined are for compliance checking by means of the DSRC communication
services provided by DSRC application layer, with the CCC attributes and functions made available to
the CCC applications at the roadside equipment (RSE) and OBE. The attributes and functions are defined
on the level of application data units (ADUs).The definition of the CCC includes:
— the application interface between OBE and RSE (as depicted in Figure 2);
— use of the generic DSRC application layer as specified in ISO 15628 and EN 12834;
— CCC data type specifications given in Annex A;— a protocol implementation conformance statement (PICS) proforma is given in Annex B;
— use of the CEN-DSRC stack as specified in EN 15509, or other equivalent DSRC stacks as described
in Annex C, Annex D, Annex E and Annex F;© ISO 2022 – All rights reserved
---------------------- Page: 11 ----------------------
oSIST prEN ISO 12813:2022
ISO/DIS 12813:2022 (E)
— security services for mutual authentication of the communication partners and for signing of data
(see Annex H);— an example CCC transaction is presented in Annex G;
— the informative Annex I highlights how to use this document for the European electronic toll
service (EETS).Test specifications are not within the scope of this document.
NOTE A test suite for checking an OBE or RSE implementation for compliance with this document is defined in
the corresponding edition of ISO 13143-1 and ISO 13143-2.Figure 2 — CCC 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 8824-1:2015, Information technology — Abstract Syntax Notation One (ASN.1): Specification of
basic notation — Part 1©ISO 2022 – All rights reserved
---------------------- Page: 12 ----------------------
oSIST prEN ISO 12813:2022
ISO/DIS 12813:2022 (E)
ISO/IEC 8825-2:2015, Information technology — ASN.1 encoding rules: Specification of Packed Encoding
Rules (PER) — Part 2ISO 12855:2022, Electronic fee collection — Information exchange between service provision and toll
chargingISO/DIS 14906:2022, Electronic fee collection — Application interface definition for dedicated short-
range communicationISO 15628:2013, Intelligent transport systems — Dedicated short range communication (DSRC) — DSRC
application layerEN 12834:2003, Road transport and traffic telematics — Dedicated Short Range Communication
(DSRC) — DSRC application layerFprEN 15509:2022, Electronic fee collection — Interoperability application profile for DSRC
ISO/TS 17573-3:2021, Electronic fee collection — System architecture for vehicle-related tolling — Part
3: Data dictionaryNIMA Technical Report TR8350.2 version 3 — Department of Defense World Geodetic System 1984, Its
Definition and Relationships With Local Geodetic Systems3 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:
— ISO Online browsing platform: available at https://www.iso.org/obp— IEC Electropedia: available at http://www.electropedia.org/
3.1
access credentials
AC_CR
trusted attestation or secure module that establishes the claimed identity of an object or application
[SOURCE: CEN 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: CEN 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]
© ISO 2022 – All rights reserved
---------------------- Page: 13 ----------------------
oSIST prEN ISO 12813:2022
ISO/DIS 12813:2022 (E)
3.4
authenticator
data, possibly encrypted, that is used for authentication
[SOURCE: CEN ISO/TS 17573-2:2020, 3.16]
3.5
data integrity
property that data has not been altered or destroyed in an unauthorized manner
[SOURCE: ISO 7498-2:1989, 3.3.21]
3.6
fixed roadside equipment
roadside equipment located at a fixed position
[SOURCE: CEN ISO/TS 17573-2:2020, 3.81]
3.7
mobile roadside equipment
equipment mounted on a mobile unit or handheld equipment to be used along the road
[SOURCE: CEN ISO/TS 17573-2:2020, 3.119]3.8
on-board equipment
OBE
all required equipment on-board a vehicle for performing required electronic fee collection (EFC)
functions and communication services[SOURCE: CEN ISO/TS 17573-2:2020, 3.126]
3.9
roadside equipment
RSE
fixed or movable electronic fee collection (EFC) equipment located along or on the road
[SOURCE: CEN ISO/TS 17573-2:2020, 3.161]3.10
service primitive
elementary communication service provided by the application layer protocol to the application
processes[SOURCE: CEN ISO/TS 17573-2:2020, 3.173]
3.11
toll context
logical view as defined by attributes and functions of the basic elements of a toll scheme consisting of a
single basic tolling principle, a spatial distribution of the charge objects and a single behaviour of the
related Front End[SOURCE: CEN ISO/TS 17573-2:2020, 3.196]
©ISO 2022 – All rights reserved
---------------------- Page: 14 ----------------------
oSIST prEN ISO 12813:2022
ISO/DIS 12813:2022 (E)
3.12
toll regime
set of rules, including enforcement rules, governing the collection of a toll in a toll domain
[SOURCE: CEN ISO/TS 17573-2:2020, 3.203]3.13
toll service provider
TSP
entity providing toll services in one or more toll domains
[SOURCE: CEN ISO/TS 17573-2:2020, 3.206]
3.14
transaction
whole of the exchange of information between two physically separated communication facilities
[SOURCE: CEN ISO/TS 17573-2:2020, 3.211]4 Abbreviated terms
For the purpose of this document, the following abbreviated terms apply.
AC_CR access credentials
ADU application data uni
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.