ISO 17573-3:2023
(Main)Electronic fee collection — System architecture for vehicle-related tolling — Part 3: Data dictionary
Electronic fee collection — System architecture for vehicle-related tolling — Part 3: Data dictionary
This document specifies the syntax and semantics of data objects in the field of electronic fee collection (EFC). The definitions of data types and assignment of semantics are provided in accordance with the abstract syntax notation one (ASN.1) technique, as specified in ISO/IEC 8824-1. This document defines: — ASN.1 (data) types within the fields of EFC; — ASN.1 (data) types of a more general use that are used more specifically in standards related to EFC. This document does not seek to define ASN.1 (data) types that are primarily related to other fields that operate in conjunction with EFC, such as cooperative intelligent transport systems (C-ITS), the financial sector, etc.
Perception de télépéage — Architecture de systèmes pour le péage lié aux véhicules — Partie 3: Dictionnaire de données
Le présent document spécifie la syntaxe et la sémantique des objets de données dans le domaine de la perception de télépéage (EFC). Les définitions des types de données et l’attribution de la sémantique sont fournis en accord avec la technique de notation de syntaxe abstraite numéro un (ASN.1), comme cela est spécifié dans l’ISO/IEC 8824-1. Ce document définit: — les types (de données) de l’ASN.1 au sein des domaines de la perception de télépéage; — les types (de données) de l’ASN.1 plus généraux employés plus spécifiquement dans les normes relatives à la perception de télépéage. Le présent document ne vise pas à définir les types (de données) de l’ASN.1 qui se rapportent en premier lieu à d’autres domaines opérant en conjonction avec la perception de télépéage, tels que les systèmes de transport intelligents coopératifs (C-ITS), le secteur de la finance, etc.
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO
STANDARD 17573-3
First edition
2023-08
Electronic fee collection — System
architecture for vehicle-related
tolling —
Part 3:
Data dictionary
Perception de télépéage — Architecture de systèmes pour le péage lié
aux véhicules —
Partie 3: Dictionnaire de données
Reference number
© ISO 2023
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 . vi
Introduction .vii
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 2
4 Abbreviated terms . 4
5 EFC common data object definitions . 5
5.1 General . 5
5.2 Subtypes of simple data types . 6
5.2.1 AccountStatus . 6
5.2.2 ActualNumberOfPassengers. 6
5.2.3 Altitude . 6
5.2.4 Axles . 7
5.2.5 CabType . 7
5.2.6 ChassisType . 7
5.2.7 Co2EmissionClass . 8
5.2.8 Co2EmissionValue . 9
5.2.9 Co2EmissionValueLoad . . 9
5.2.10 Co2Scheme . 9
5.2.11 ContractAuthenticator . 9
5.2.12 ContractSerialNumber . 9
5.2.13 CopValue. 10
5.2.14 CountryCode . 10
5.2.15 DetectionMode . 10
5.2.16 EmissionUnit . 11
5.2.17 EngineCharacteristics . 11
5.2.18 EquipmentIccId . 13
5.2.19 EquipmentObuId .13
5.2.20 EquipmentStatus . 14
5.2.21 EuroValue . 14
5.2.22 DistanceUnit . 14
5.2.23 IssuerIdentifier . 15
5.2.24 Latitude. 15
5.2.25 LocalVehicleClassId. 15
5.2.26 LocationClassId .15
5.2.27 Longitude . 16
5.2.28 PaymentSecurityData . 16
5.2.29 PayUnit . 16
5.2.30 PersonalAccountNumber . 17
5.2.31 RearWheelsSteeringType . 17
5.2.32 ReceiptAuthenticator . 18
5.2.33 ReceiptDistance . 18
5.2.34 ResultFin. 18
5.2.35 ReceiptIccId . 19
5.2.36 ReceiptObuId . 19
5.2.37 ResultOp. 19
5.2.38 ReceiptServiceSerialNumber . 21
5.2.39 ReceiptText . 21
5.2.40 StationType . 21
5.2.41 SuspensionType . 21
5.2.42 TariffClassId . 22
5.2.43 Time . 22
iii
5.2.44 TimeClassId . 22
5.2.45 TimeUnit .22
5.2.46 TrailerType . 23
5.2.47 TyreConfiguration . . 23
5.2.48 UserClassId .23
5.2.49 VehicleAuthenticator . 24
5.2.50 VehicleClass . . 24
5.2.51 VehicleCurrentMaxTrainWeight . 24
5.2.52 VehicleTechnicalPermissibleMaxLadenMass . 24
5.2.53 VehicleTotalDistance . 25
5.2.54 VehicleUsageCategoryType . 25
5.2.55 VehicleWeightLaden . 26
5.2.56 WeekDay .26
5.3 Single level data types . 26
5.3.1 AbsolutePosition2d . 26
5.3.2 AbsolutePosition3d . 27
5.3.3 AxleWeightLimit . 27
5.3.4 AxleWeightLimits . 27
5.3.5 DateCompact .28
5.3.6 DieselEmissionValues .28
5.3.7 DriverCharacteristics .28
5.3.8 Distance .28
5.3.9 Duration .29
5.3.10 EngineDetails .29
5.3.11 EuVehicleGroup .29
5.3.12 ExhaustEmissionValues .29
5.3.13 FutureCharacteristics .30
5.3.14 NumberOfAxles . 30
5.3.15 ObeId . 31
5.3.16 Particulate . 31
5.3.17 PassengerCapacity . 31
5.3.18 PaymentFee . . . 31
5.3.19 Period . 32
5.3.20 Provider . 32
5.3.21 RelativePosition3d . 32
5.3.22 SessionClass . 32
5.3.23 SessionLocation.33
5.3.24 SignedValue . 33
5.3.25 SoundLevel . 33
5.3.26 TariffClassDescription . 33
5.3.27 TimeCompact . .34
5.3.28 TrailerDetails .34
5.3.29 WheelsConfiguration .34
5.4 Two-level data types. 35
5.4.1 AxlesWeightLimits . 35
5.4.2 ChargeObjectId . 35
5.4.3 ContractValidity . 35
5.4.4 DateAndTime .36
5.4.5 EnvironmentalCharacteristics .36
5.4.6 InitialVehicleRegistrationDate .36
5.4.7 Lpn . 36
5.4.8 PaymentMeans . 37
5.4.9 PaymentMeansBalance . . .38
5.4.10 Point .38
5.4.11 PurseBalance .38
5.4.12 TrailerCharacteristics.38
5.4.13 ValidityOfContract . 39
5.4.14 VehicleAxlesNumber .39
iv
5.4.15 VehicleDimensions . 39
5.4.16 VehicleIdentificationNumber .39
5.4.17 VehicleWeightLimits .40
5.5 Three-level data types .40
5.5.1 EfcContextMark .40
5.5.2 ReceiptContract .40
5.5.3 ReceiptData . 41
5.5.4 ReceiptFinancialPart . 42
5.5.5 ReceiptServicePart . 42
5.5.6 UserId . 43
5.5.7 VehicleAxles . 43
5.5.8 VehicleSpecificCharacteristics . 43
5.6 Complex data types .44
5.6.1 AggregatedSingleTariffClassSession .44
5.6.2 DetectedChargeObject . 45
5.6.3 VehicleDescription .46
Annex A (normative) EFC common data type definitions .47
Bibliography .48
v
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 first edition cancels and replaces the first edition (ISO/TS 17573-3:2021), which has been
technically revised.
The main changes are as follows:
[15]
— CO emission class data types have been added to underpin the revised Directive 1999/62/EC
(i.e. Eurovignette directive regarding the charging of vehicles for the use of certain infrastructure),
[21]
updated by Directive (EU) 2022/362;
— a second level of version identifier (i.e. minor version) of the abstract syntax notation one (ASN.1)
module has been added to provide enhanced support to standards that import data types from this
document.
A list of all parts in the ISO 17573 series can be found on the ISO website.
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.
vi
Introduction
This document is a part of the ISO 17573 series which defines the system architecture for vehicle-
related tolling. ISO 17573-1 gives a reference model for the system architecture. ISO/TS 17573-2
provides a collection of terms and definitions within the field of electronic fee collection (EFC) and road
user charging that are used in the different documents published in ISO and CEN under the general title,
Electronic fee collection.
This document (ISO 17573-3) provides a data dictionary that contains the definitions of ASN.1 (data)
types and the associated semantics.
The document is intended to be used as a reference by editors of ISO and CEN documents in EFC and in
related areas of standardization (such as Intelligent transport systems, ITS).
It is foreseen that the library of ASN.1 (data) types contained in this document will be augmented with
additional definitions as these become available.
vii
INTERNATIONAL STANDARD ISO 17573-3:2023(E)
Electronic fee collection — System architecture for vehicle-
related tolling —
Part 3:
Data dictionary
1 Scope
This document specifies the syntax and semantics of data objects in the field of electronic fee collection
(EFC). The definitions of data types and assignment of semantics are provided in accordance with the
abstract syntax notation one (ASN.1) technique, as specified in ISO/IEC 8824-1. This document defines:
— ASN.1 (data) types within the fields of EFC;
— ASN.1 (data) types of a more general use that are used more specifically in standards related to EFC.
This document does not seek to define ASN.1 (data) types that are primarily related to other fields
that operate in conjunction with EFC, such as cooperative intelligent transport systems (C-ITS), the
financial sector, etc.
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/TS 17573-2, Electronic fee collection — System architecture for vehicle related tolling — Part 2:
Vocabulary
ISO 612, Road vehicles — Dimensions of motor vehicles and towed vehicles — Terms and definitions
ISO 3166-1, Codes for the representation of names of countries and their subdivisions — Part 1: Country
code
ISO 1176, Road vehicles — Masses — Vocabulary and codes
ISO 4217, Codes for the representation of currencies
ISO/IEC 7812-1, Identification cards — Identification of issuers — Part 1: Numbering system
ISO/IEC 7812-2, Identification cards — Identification of issuers — Part 2: Application and registration
procedures
ISO/IEC 8824-1, Information technology — Abstract Syntax Notation One (ASN.1) — Part 1: Specification
of basic notation
ISO/IEC 8859-1, Information technology — 8-bit single-byte coded graphic character sets — Part 1: Latin
alphabet No. 1
ISO/IEC 8859-2, Information technology — 8-bit single-byte coded graphic character sets — Part 2: Latin
alphabet No. 2
ISO/IEC 8859-3, Information technology — 8-bit single-byte coded graphic character sets — Part 3: Latin
alphabet No. 3
ISO/IEC 8859-4, Information technology — 8-bit single-byte coded graphic character sets — Part 4: Latin
alphabet No. 4
ISO/IEC 8859-5, Information technology — 8-bit single-byte coded graphic character sets — Part 5: Latin/
Cyrillic alphabet
ISO/IEC 8859-6, Information technology — 8-bit single-byte coded graphic character sets — Part 6: Latin/
Arabic alphabet
ISO/IEC 8859-7, Information technology — 8-bit single-byte coded graphic character sets — Part 7: Latin/
Greek alphabet
ISO/IEC 8859-8, Information technology — 8-bit single-byte coded graphic character sets — Part 8: Latin/
Hebrew alphabet
ISO/IEC 8859-9, Information technology — 8-bit single-byte coded graphic character sets — Part 9: Latin
alphabet No. 5
ISO/IEC 8859-10, Information technology — 8-bit single-byte coded graphic character sets — Part 10:
Latin alphabet No. 6
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO/TS 17573-2 and the following
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
BITSTRING
simple type (3.14) whose distinguished values are an ordered sequence of zero, one or more bits
[SOURCE: ISO/IEC 8824-1:2021, 3.8.7, modified — Term modified from "BITSTRING type" to
"BITSTRING" and domain "" added.]
3.2
CHOICE
type defined by referencing a list of distinct types; each value of the choice type is derived from
the value of one of the component types (3.4)
Note 1 to entry: Each value of the choice type is derived from the value of one of the component types.
[SOURCE: ISO/IEC 8824-1:2021, 3.8.14, modified — Term modified from "CHOICE type" to "CHOICE"
and domain "" added. Note 1 to entry also added.]
3.3
complex data type
one type that has more than three levels (3.17)
3.4
component type
one of the types referenced when defining a CHOICE (3.2), SET (3.12), SEQUENCE (3.10), SET OF (3.13), or
SEQUENCE OF (3.11)
[SOURCE: ISO/IEC 8824-1:2021, 3.8.15]
3.5
data type
categorization of an abstract set of possible values, characteristics, and set of operations for an attribute
[SOURCE: ISO/IEC 25012:2008, 4.7 — modified, NOTE removed.]
3.6
INTEGER
simple type (3.14) with distinguished values which are the positive and negative whole numbers,
including zero (as a single value)
[SOURCE: ISO/IEC 8824-1:2021, 3.8.48, modified — Term modified from "INTEGER type" to "INTEGER"
and domain "" added.]
3.7
object
well-defined piece of information, definition or specification which requires a name in order to identify
its use in an instance of communication
[SOURCE: ISO/IEC 8824-1:2021, 3.8.52]
3.8
OCTET STRING
simple type (3.14) whose distinguished values are an ordered sequence of zero, one or more
octets, each octet being an ordered sequence of eight bits
[SOURCE: ISO/IEC 8824-1:2021, 3.8.55, modified — Term modified from "OCTET STRING type" to
"OCTET STRING" and domain "" added.]
3.9
parent type
type that is being constrained when defining a subtype (3.16), and which governs the subtype notation
[SOURCE: ISO/IEC 8824-1:2021, 3.8.58, modified — Term modified from "parent type (of a subtype)" to
"parent type".]
3.10
SEQUENCE
type defined by referencing a fixed, ordered list of types (some of which can be declared to be
optional)
Note 1 to entry: Each value of the SEQUENCE type is an ordered list of values, one from each component type (3.4).
[SOURCE: ISO/IEC 8824-1:2021, 3.8.67, modified — Term modified from "SEQUENCE types" to
"SEQUENCE" and domain "" added. Second part of original definition moved to Note 1 to entry.]
3.11
SEQUENCE-OF
type defined by referencing a single component type (3.4)
Note 1 to entry: Each value in the SEQUENCE-OF type is an ordered list of zero, one or more values of the
component type.
[SOURCE: ISO/IEC 8824-1:2021, 3.8.68, modified — Term modified from "SEQUENCE-OF types" to
"SEQUENCE" and domain "" added. Second part of original definition moved to Note 1 to entry.]
3.12
SET
type defined by referencing a fixed, unordered, list of types (some of which may be declared to
be optional)
Note 1 to entry: Each value in the SET type is an unordered list of values, one from each component type (3.4).
Note 2 to entry: Where a component type is declared to be optional, a value of the SET type need not contain a
value of that component type.
[SOURCE: ISO/IEC 8824-1:2021, 3.8.72, modified — Term modified from "SET types" to "SET" and
domain "" added. Second part of original definition moved to Note 1 to entry. Note 1 to entry
updated as Note 2 to entry.]
3.13
SET-OF
types defined by referencing a single component type (3.4)
Note 1 to entry: Each value in the SET-OF type is an unordered list of zero, one or more values of the component
type.
[SOURCE: ISO/IEC 8824-1:2021, 3.8.73, modified — Term modified from "SET-OF types" to "SET-OF"
and domain "" added. Second part of original definition moved to Note 1 to entry.]
3.14
simple type
type defined by directly specifying the set of their values
[SOURCE: ISO/IEC 8824-1:2021, 3.8.74]
3.15
single-level data type
data type (3.5) which is a SEQUENCE (3.10), or SEQUENCE OF (3.11) defined by referencing a simple type
(3.14) or a subtype (3.16) of a simple type
3.16
subtype
type whose values are a subset (or the complete set) of the values of some other type
(the parent type) (3.9)
[SOURCE: ISO/IEC 8824-1:2021, 3.8.76, modified — Term modified from "subtype (of a parent type)" to
"subtype" and domain "" added.]
3.17
three-level data type
data type (3.5) which is a CHOICE (3.2), SEQUENCE (3.10), or SEQUENCE OF (3.11) defined by referencing a
two-level data type (3.18)
3.18
two-level data type
data type (3.5) which is a CHOICE (3.2), SEQUENCE (3.10), or SEQUENCE OF (3.11) defined by referencing a
single-level data type (3.15)
4 Abbreviated terms
ASN.1 abstract syntax notation one
BCD binary coded decimal
CO carbon monoxide
CO carbon dioxide
DSRC dedicated short-range communication
EFC electronic fee collection
GLONASS global navigation satellite system of the Russian Federation
GNSS global navigation satellite system
GPS global positioning system
GTRF global terrestrial reference system
HC hydrocarbon
ICC integrated circuit(s) card
ITRF international terrestrial reference frame
ITRS international terrestrial reference system
JGS Japan satellite navigation geodetic system
LAC localization augmentation communication
NO nitrogen oxides
X
OBE on-board equipment
OBU on-board unit
QZSS quasi-zenith satellite system
RSE roadside equipment
TSP toll service provider
VAT value-added tax
5 EFC common data object definitions
5.1 General
In this clause, the structure of all EFC common data objects is described. The formal definition provided
in Annex A in terms of data type definitions applies. In addition to the structure description, each data
object is also given a semantics.
Each one of the common data types defined herein is used by more than one document in the suite of
CEN or ISO documents in the field of EFC. These documents may also define their own data types when
no one of the common data types defined herein satisfies their need.
The definitions of the EFC common data types are ordered according to their data type level:
— first subtypes based on simple data types (e.g. INTEGER or OCTET STRING),
— then two-level data types,
— then three-level data types,
— then complex data types.
Data types are ordered alphabetically within each level.
5.2 Subtypes of simple data types
5.2.1 AccountStatus
The data type AccountStatus shall be of the simple type as specified in Table 1.
Table 1 — AccountStatus
Subtype Parent type Semantics
INTEGER
- AccountStatus provides the status of the user’s account. The
following semantics are assigned:
— ok: The amount stored in the account is above or equal to
the predefined threshold;
— low: The amount stored in the account has fallen below a
predefined threshold;
— empty: The amount stored in the account is zero;
— negative: The amount stored in the account has fallen
below zero.
5.2.2 ActualNumberOfPassengers
The data type ActualNumberOfPassengers shall be of the subtype as specified in Table 2.
Table 2 — ActualNumberOfPassengers
Subtype Parent type Semantics
Int1Unsigned
ActualNumberOfPassengers represents the actual number of
passengers (i.e. persons) present in the vehicle, including the
driver.
This information can affect the applicability of tolls or the value
of the tariff to be applied, e.g. in High Occupancy Tolling or High
Occupancy Vehicle lanes.
5.2.3 Altitude
The data type Altitude shall be of the simple type as specified in Table 3.
Table 3 — Altitude
Subtype Parent type Semantics
Int2Signed Altitude provides the ellipsoidal height (in units of 0,25 m)
[5]
above or below the WGS84 ellipsoid of the geographical
point. The range in m is from -8 192,00 to +8 191,75.
[10]
NOTE WGS84 represents a broadly adopted global geodet-
ic reference system for the Earth for practical applications of
mapping, geo-positioning and navigation. Other terrestrial
reference frames exist, notably the International Terrestri-
al Reference Frame (ITRF, the latest edition currently being
ITRF 2020). It is possible to convert between the most com-
monly used terrestrial reference frames and the differences
between them are typically in the order of centimetres. The
international terrestrial reference frame is becoming increas-
ingly recognized and used as the primary reference frame. All
recent and up-to-date Global Navigation Satellite System (GNS-
S)-specific terrestrial reference frames (WGS 84 for GPS, PZ-90
for GLONASS, the GTRF for Galileo, CGCS2000 for BeiDou, and
[11]
the JGS for QZSS) are aligned to a primary ITRS realization,
according to ISO 19161-1:2020, Annex C.
5.2.4 Axles
The data type Axles shall be of the simple type as specified in Table 4.
Table 4 — Axles
Subtype Parent type Semantics
INTEGER
- Axles provides the number of axles of either the tractor or
trailer including drop axles.
5.2.5 CabType
The data type CabType shall be of the simple constrained type as specified in Table 5.
Table 5 — CabType
Subtype Parent type Semantics
- INTEGER CabType provides information about the cabin type of a vehicle
[18]
according to Regulation (EU) 2019/1242, Annex I.
The following semantics are assigned:
— dayCab: A type of cabin that is not a sleeper cabin;
— sleeperCab: A type of cabin that has a compartment
behind the driver’s seat intended to be used for sleeping as
[20]
reported in accordance with Regulation (EU) 2018/956,
Annex I, Part B, Data no. 84.
5.2.6 ChassisType
The data type ChassisType shall be of the simple constrained type as specified in Table 6.
Table 6 — ChassisType
Subtype Parent type Semantics
- INTEGER ChassisType provides information about the type of chassis of
a vehicle according to Regulation (EU) 2019/1242 and Regula-
tion (EU) 2018/858.
The following semantics are assigned:
— rigidLorry: A type of chassis, that is not designed or
constructed for the towing of a semitrailer, as defined in
[18]
Regulation (EU) 2019/1242, Article 3 (6);
— tractor: A type of chassis, that is designed and constructed
exclusively or principally to tow semitrailers, as defined in
[18]
Regulation (EU) 2019/1242, Article 3 (7);
— van: A lorry with the compartment where the driver is
located and cargo area within a single unit, as defined in
[19]
Regulation (EU) 2018/858, Annex I, Part C, 4.2.
5.2.7 Co2EmissionClass
The data type Co2EmissionClass shall be of the simple type as specified in Table 7.
Table 7 — Co2EmissionClass
Subtype Parent type Semantics
INTEGER
- Co2EmissionClass indi
...
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...