EN ISO 17575-3:2016

Electronic fee collection - Application interface definition for autonomous systems - Part 3: Context data (ISO 17575-3:2016)

ISO 17575-3:2016 defines the content, semantics and format of the data exchange between a Front End (OBE plus optional proxy) and the corresponding Back End in autonomous toll systems. It defines the data elements used to specify and describe the toll context details. Context data are transmitted from the Back End to the Front End to configure it for the charging processes of the associated toll context.
In ISO 17575, context data is the description of the properties of a single instance of an electronic fee collection (EFC) context. This single instance of an EFC context operates according to one of the basic tolling principles such as
-      road section charging,
-      area charging (according to travelled distance or duration of time), and
-      cordon charging.
EFC context data comprise a set of rules for charging, including the description of the charged network, the charging principles, the liable vehicles and a definition of the required contents of the charge report. This set of rules is defined individually for each EFC context according to local needs.
The following data and associated procedures are defined in this part of ISO 17575:
-      data providing toll context overview information;
-      data providing tariff information (including definitions of required tariff determinants such as vehicle parameters, time classe, etc.);
-      data providing context layout information;
-      data providing reporting rules information.
ISO 17575-3:2016 also provides the required definitions and data specifications to be applied when one single toll context is spilt inot more than one toll context partitions. This is applicable to cases where one EFC scheme and the rules applied cannot be described with a single set of context data.
Annex A provides the data type specification using ASN.1 notation.
The protocol implementation conformity statements (PICS) proforma are provided in Annex B.
Annex C provides a graphical presentation of the structure of the toll context data.
Annexes D, E and F contain further information and descriptions, which may support the understanding and the implementation of the rules specified in this part of ISO 17575.
Annex G provides information how this part of ISO 17575 can be used in a European Electronic Toll Service (EETS) environment, with reference to EU Decision 2009/750.

Elektronische Gebührenerhebung - Definition der Anwendungsschnittstelle für autonome Systeme - Teil 3: Kontextdaten (ISO 17575-3:2016)

Perception du télépéage - Définition de l'interface d'application pour les systèmes autonomes - Partie 3: Données du contexte (ISO 17575-3:2016)

ISO 17575-3:2016 définit le contenu, la sémantique et le format de l'échange de données réalisé entre un système frontal (équipement embarqué et proxy facultatif) et le système central associé dans les systèmes autonomes de péage. Elle définit les éléments de données utilisés pour spécifier et décrire le contexte de péage en détail. Les données du contexte sont transmises depuis le système central vers le système frontal, afin de le configurer pour les processus de tarification du contexte de péage associé.
Dans la norme ISO 17575, les données du contexte correspondent à la description des propriétés d'une seule instance d'un contexte de perception électronique de télépéage (EFC). Cette instance unique de perception électronique de télépéage fonctionne selon l'un des principes basiques de tarification:
-      tarification de portion routière,
-      péage de zone (selon la distance parcourue ou le temps passé), et
-      péage de cordon.
Les données du contexte de perception de télépéage incluent un ensemble de règles de tarification, dont une description du réseau facturé, des régimes de tarification, des véhicules concernés et une définition du contenu obligatoire pour générer un rapport d'imputation. Cet ensemble de règles est défini individuellement pour chaque contexte de perception de télépéage selon les exigences locales.
Les données et les procédures associées suivantes sont définies dans la présente partie de l'ISO 17575:
-      données fournissant des informations générales sur le contexte de péage;
-      données fournissant des informations tarifaires (incluant la définition des déterminants de tarif requis, tels que les paramètres des véhicules, les classes temporelles, etc.);
-      données fournissant des informations sur la configuration du contexte;
-      données fournissant des informations sur les règles de génération de rapports.
ISO 17575-3:2016 fournit également les définitions requises et les spécifications de données à appliquer lorsqu'un même contexte de péage est réparti entre une ou plusieurs divisions de contexte de péage. Elle s'applique dans les cas où un plan EFC et les règles appliquées ne peuvent pas être décrits à l'aide d'un ensemble unique de données du contexte.
L'Annexe A donne la spécification du type de données dans la notation ASN.1.
Les formulaires PICS (déclaration de conformité d'implémentation de protocole) sont fournis en Annexe B.
L'Annexe C comprend une représentation graphique de la structure des données de contexte de péage.
Les Annexes D, E et F contiennent des informations et des descriptions supplémentaires pouvant aider à mieux comprendre et implémenter les règles spécifiées dans la présente partie de l'ISO 17575.
L'Annexe G fournit des informations sur la manière dont la présente partie de l'ISO 17575 peut être utilisée dans un environnement de Service Européen de Télépéage (SET), en référence à la Décision de l'UE 2009/750.

Elektronsko pobiranje pristojbin - Definicija aplikacijskega vmesnika za avtonomne sisteme - 3. del: Podatki iz sobesedila (ISO 17575-3:2016)

Ta del standarda ISO 17575 določa vsebino, semantiko in format izmenjave podatkov med čelnim delom (oprema, vgrajena v vozilo, in izbirni strežnik proxy) ter ustreznim zalednim delom v avtonomnih sistemih cestninjenja. Določa podatkovne elemente, ki se uporabljajo za določanje in opisovanje podrobnosti iz sobesedila o cestninah. Podatki iz sobesedila se prenesejo iz zalednega dela v čelni del, kjer se konfigurirajo za postopke zaračunavanja povezanega sobesedila o cestninah.
V standardu ISO 17575 so podatki iz sobesedila opis lastnosti enega primerka sobesedila elektronskega pobiranja pristojbin (EFC). Ta primerek sobesedila EFC deluje skladno z enim od osnovnih
principov cestninjenja, kot so
– zaračunavanje uporabe cestnih odsekov,
– območno zaračunavanje (glede na prevoženo razdaljo ali čas vožnje) in
– »cordon« zaračunavanje.
Podatki iz sobesedila EFC zajemajo nabor pravil za zaračunavanje, vključno z opisom omrežja, za katerega se zaračunavajo pristojbine, principov zaračunavanja, vozil, ki morajo plačani pristojbino, ter definicijo zahtevane vsebine poročila o zaračunavanju.
Ta nabor pravil je določen posamezno za vsako sobesedilo EFC v skladu z lokalnimi potrebami.
Podatki in s tem povezani postopki, ki so določeni v tem delu standarda ISO 17575:
– podatki, ki vsebujejo pregled sobesedila o cestninah;
– podatki, ki vsebujejo informacije o tarifah (vključno z definicijami obveznih determinant za tarife, kot so
parametri vozila, časovni razred itd.);
– podatki, ki vsebujejo informacije o postavitvi sobesedila;
– podatki, ki vsebujejo informacije o pravilih za poročanje.
Ta del standarda ISO 17575 prav tako podaja zahtevane definicije in specifikacije podatkov, ki jih je treba uporabiti, kadar je eno sobesedilo o cestninah razdeljeno v več kot eno particijo sobesedila o cestninah. To velja za primere, v katerih ene ureditve EFC in uporabljenih pravil ni mogoče opisati z enim naborom podatkov iz sobesedila.
Dodatek A vsebuje specifikacijo podatkovne vrste z oznako ASN.1.
Proforma formalne izjave o skladnosti izvedbe protokola (PICS) je podana v dodatku B. Dodatek C vsebuje grafično predstavitev strukture podatkov iz sobesedila o cestninah.
Dodatki D, E in F vsebujejo dodatne informacije in opise, ki so lahko v pomoč pri razumevanju in uveljavitvi pravil iz tega dela standarda ISO 17575.
Dodatek G vsebuje informacije o tem, kako se lahko ta del standarda ISO 17575 uporablja v evropskem sistemu elektronskega cestninjenja (EETS) skladno s Sklepom EU 2009/750.

General Information

• Status: Published
• Publication Date: 23-Feb-2016
• ICS: 03.220.20 - Road transport
• ICS: 35.240.60 - IT applications in transport
• Technical Committee: CEN/TC 278 - Road transport and traffic telematics
• Drafting Committee: CEN/TC 278/WG 1 - Electronic fee collection and access control (EFC)
• Current Stage: 6060 - Definitive text made available (DAV) - Publishing
• Due Date: 24-Feb-2016
• Completion Date: 24-Feb-2016
• Directive: 2004/52/EC - Interoperability of electronic road toll systems in the Community
• Mandate: M/338 - Standardisation mandate to CEN, CENELEC and ETSI in support of interoperabilty of electonic road toll systems in the community
• Ref Project: SIST EN ISO 17575-3:2016 - Electronic fee collection - Application interface definition for autonomous systems - Part 3: Context data (ISO 17575-3:2016)

RELATIONS

• Revised: CEN ISO/TS 17575-3:2011 - Electronic fee collection - Application interface definition for autonomous systems - Part 3: Context data (ISO/TS 17575-3:2011)
• Effective Date: 16-Oct-2013
• Replaces: CEN ISO/TS 17575-3:2011/AC:2013 - Electronic fee collection - Application interface definition for autonomous systems - Part 3: Context data - Technical Corrigendum 1 (ISO/TS 17575-3:2011/Cor 1:2013)
• Effective Date: 02-Mar-2016
• Replaces: CEN ISO/TS 17575-3:2011 - Electronic fee collection - Application interface definition for autonomous systems - Part 3: Context data (ISO/TS 17575-3:2011)
• Effective Date: 02-Mar-2016

Standards Content (sample)

SLOVENSKI STANDARD
SIST EN ISO 17575-3:2016
01-julij-2016
1DGRPHãþD
SIST-TS CEN ISO/TS 17575-3:2011
SIST-TS CEN ISO/TS 17575-3:2011/AC:2014
Elektronsko pobiranje pristojbin - Definicija aplikacijskega vmesnika za
avtonomne sisteme - 3. del: Podatki iz sobesedila (ISO 17575-3:2016)

Electronic fee collection - Application interface definition for autonomous systems - Part

3: Context data (ISO 17575-3:2016)

Elektronische Gebührenerhebung - Definition der Anwendungsschnittstelle für autonome

Systeme - Teil 3: Kontextdaten (ISO 17575-3:2016)

Perception du télépéage - Définition de l'interface d'application pour les systèmes

autonomes - Partie 3: Données du contexte (ISO 17575-3:2016)
Ta slovenski standard je istoveten z: EN ISO 17575-3:2016
ICS:
03.220.20 Cestni transport Road transport
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
SIST EN ISO 17575-3:2016 en,fr,de

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

---------------------- Page: 1 ----------------------
SIST EN ISO 17575-3:2016
---------------------- Page: 2 ----------------------
SIST EN ISO 17575-3:2016
EN ISO 17575-3
EUROPEAN STANDARD
NORME EUROPÉENNE
February 2016
EUROPÄISCHE NORM
ICS 35.240.60; 03.220.20 Supersedes CEN ISO/TS 17575-3:2011
English Version
Electronic fee collection - Application interface definition
for autonomous systems - Part 3: Context data (ISO 17575-
3:2016)

Perception du télépéage - Définition de l'interface Elektronische Gebührenerhebung - Definition der

d'application pour les systèmes autonomes - Partie 3: Anwendungsschnittstelle für autonome Systeme - Teil

Données du contexte (ISO 17575-3:2016) 3: Kontextdaten (ISO 17575-3:2016)
This European Standard was approved by CEN on 11 December 2015.

CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this

European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references

concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN

member.

This European Standard exists in three official versions (English, French, German). A version in any other language made by

translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC Management

Centre has the same status as the official versions.

CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,

Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania,

Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and

United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION
EUROPÄISCHES KOMITEE FÜR NORMUNG
CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels

© 2016 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN ISO 17575-3:2016 E

worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
SIST EN ISO 17575-3:2016
EN ISO 17575-3:2016 (E)
Contents Page

European foreword ....................................................................................................................................................... 3

---------------------- Page: 4 ----------------------
SIST EN ISO 17575-3:2016
EN ISO 17575-3:2016 (E)
European foreword

This document (EN ISO 17575-3:2016) has been prepared by Technical Committee ISO/TC 204

“Intelligent transport systems” in collaboration with Technical Committee CEN/TC 278 “Intelligent

transport systems” the secretariat of which is held by NEN.

This European Standard shall be given the status of a national standard, either by publication of an

identical text or by endorsement, at the latest by August 2016, and conflicting national standards shall

be withdrawn at the latest by August 2016.

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

patent rights. CEN [and/or CENELEC] shall not be held responsible for identifying any or all such patent

rights.
This document supersedes CEN ISO/TS 17575-3:2011.

This document has been prepared under a mandate given to CEN by the European Commission and the

European Free Trade Association.

According to the CEN-CENELEC Internal Regulations, the national standards organizations of the

following countries are bound to implement this European Standard: Austria, Belgium, Bulgaria,

Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia,

France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta,

Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland,

Turkey and the United Kingdom.
Endorsement notice

The text of ISO 17575-3:2016 has been approved by CEN as EN ISO 17575-3:2016 without any

modification.
---------------------- Page: 5 ----------------------
SIST EN ISO 17575-3:2016
---------------------- Page: 6 ----------------------
SIST EN ISO 17575-3:2016
INTERNATIONAL ISO
STANDARD 17575-3
First edition
2016-01-15
Electronic fee collection —
Application interface definition for
autonomous systems —
Part 3:
Context data
Perception du télépéage — Définition de l’interface d’application pour
les systèmes autonomes —
Partie 3: Données du contexte
Reference number
ISO 17575-3:2016(E)
ISO 2016
---------------------- Page: 7 ----------------------
SIST EN ISO 17575-3:2016
ISO 17575-3:2016(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO 2016, Published in Switzerland

All rights reserved. Unless otherwise specified, 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
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. [phone]
Fax [phone]
[e-mail]
www.iso.org
ii © ISO 2016 – All rights reserved
---------------------- Page: 8 ----------------------
SIST EN ISO 17575-3:2016
ISO 17575-3:2016(E)
Contents Page

Foreword ........................................................................................................................................................................................................................................iv

Introduction ................................................................................................................................................................................................................................vi

1 Scope ................................................................................................................................................................................................................................. 1

2 Normative references ...................................................................................................................................................................................... 2

3 Terms and definitions ..................................................................................................................................................................................... 2

4 Abbreviated terms .............................................................................................................................................................................................. 4

5 General concept and overview ............................................................................................................................................................... 5

6 Procedural requirements and encoding rules ...................................................................................................................... 7

6.1 General ........................................................................................................................................................................................................... 7

6.2 Communication services ................................................................................................................................................................ 7

6.3 Version and validity handling..................................................................................................................................................... 7

6.3.1 Protocol versioning........................................................................................................................................................ 7

6.3.2 Context data versioning ............................................................................................................................................. 7

6.4 Encoding rules ......................................................................................................................................................................................... 8

6.5 Acknowledgement and behaviour on errors ................................................................................................................ 8

7 Application data units ..................................................................................................................................................................................... 8

7.1 General ........................................................................................................................................................................................................... 8

7.2 Message authentication (data type Iso17575-3-InformationContent) .................................................. 9

7.3 Application data unit structure (data type Iso17575-3Adu) .......................................................................... 9

7.4 Application data unit header (data type ISO 17575-3AduHeader) ........................................................10

7.5 Application data unit body (data type ISO 17575-3AduBody) ..................................................................11

8 EFC Attributes .......................................................................................................................................................................................................11

8.1 General ........................................................................................................................................................................................................11

8.2 Rules with respect to support of context data ..........................................................................................................12

8.3 Attributes and data sets ...............................................................................................................................................................12

8.4 EFC attributes authentication .................................................................................................................................................12

8.5 EFC attributes data catalogue .................................................................................................................................................13

8.5.1 General...................................................................................................................................................................................13

8.5.2 Requirements with regards to context overview .............................................................................14

8.5.3 Requirements with regards to tariff information .............................................................................17

8.5.4 Requirements with regards to context layout .....................................................................................35

8.5.5 Requirements with regards to reporting rules ...................................................................................45

Annex A (normative) Data type specifications ........................................................................................................................................59

Annex B (normative) Protocol implementation conformance statement (PICS) proforma ....................60

Annex C (informative) Hierarchical data structure illustration ...........................................................................................98

Annex D (informative) How to use context data to define the properties of an EFC regime ................103

Annex E (informative) Guidelines on the use of standardised digital maps in GDF format in

the description of section based toll context layouts ..............................................................................................108

Annex F (informative) Examples using EFC context data for scheme definitions ...........................................111

Annex G (informative) Use of this part of ISO 17575 for the EETS .................................................................................116

Bibliography .........................................................................................................................................................................................................................118

© ISO 2016 – All rights reserved iii
---------------------- Page: 9 ----------------------
SIST EN ISO 17575-3:2016
ISO 17575-3:2016(E)
Foreword

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

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

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

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

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

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

electrotechnical standardization.

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

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

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

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

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

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

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

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

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

constitute an endorsement.

For an explanation on the meaning of ISO specific terms and expressions related to conformity

assessment, as well as information about ISO’s adherence to the WTO principles in the Technical

Barriers to Trade (TBT) see the following URL: Foreword - Supplementary information

The committee responsible for this document is ISO/TC 204, Intelligent transport systems.

This edition of ISO 17575-3 cancels and replaces ISO/TS 17575-3:2011, which has been technically

revised. The following changes have been made:
— conversion from a Technical Specification to an International Standard;

— amendments to reflect changes to the underlying base standards, especially ISO 14906;

— major changes regarding

— integration of functionalities for the support of complex toll domains that consist of more than

one partition from ISO/TS 17575-2:2010,
— changes in the security scheme details,
— introduction of protocol version identification,

— harmonization of the identification of toll contexts amongst the parts of ISO 17575,

— improvement of the possibility to use rounding rules,
— enabling the use of a second alternative currency in tariffs,

— adaptation of the charge reporting configuration to changes in ISO 17575-1:2016,

— enabling the use of toll context partitions which may be present in one single toll context,

— support of optional geographic data files (GDF) based description of toll liable networks

(embracing such data definitions from ISO 12855:2012,
— revised terms and definitions (Clause 3), and
— editorial and formal corrections as well as changes to improve readability.
iv © ISO 2016 – All rights reserved
---------------------- Page: 10 ----------------------
SIST EN ISO 17575-3:2016
ISO 17575-3:2016(E)

ISO 17575 consists of the following parts, under the general title Electronic fee collection — Application

interface definition for autonomous systems:
— Part 1: Charging
— Part 2: Communication and connection to the lower layers
— Part 3: Context data

In this edition of the ISO 17575-series the contents of ISO/TS 17575-4:2011 were incorporated into

ISO 17575-3:2016. ISO/TS 17575-4:2011 will be withdrawn once ISO 17575-3 has been published.

© ISO 2016 – All rights reserved v
---------------------- Page: 11 ----------------------
SIST EN ISO 17575-3:2016
ISO 17575-3:2016(E)
Introduction
0.1 Autonomous systems

ISO 17575 is a series of standards defining the information exchange between the Front End and the

Back End in electronic fee collection (EFC) based on autonomous on-board equipment (OBE). EFC

systems automatically collect charging data for the use of road infrastructure including motorway tolls,

zone-based fees in urban areas, tolls for special infrastructure such as bridges and tunnels, distance-

based charging, and parking fees.

Further introductory explanations of autonomous systems in EFC and, in particular, the considerations

with respect to business and technical architecture that form the base for interfaces within such system

and their interoperable specification are provided in ISO 17575-1:2016.
0.2 Location of the specification interface

In order to abstract from, and become independent of, these architectural implementation choices,

the primary scope of ISO 17575 is the data exchange between Front End and Back End (see the

corresponding vertical line in Figure 1). For every toll scheme, the Back End will send context data, i.e.

a description of the toll scheme in terms of charged objects, charging rules and, if required, the tariff

scheme to the Front End, and will receive usage data from the Front End.

It has to be noted also that the distribution of tasks and responsibilities between service provider and

toll charger will vary individually. Depending on the local legal situation, toll chargers will require

“thinner” or “thicker” data, and might or might not leave certain data processing tasks to service

providers. Hence, the data definitions in ISO 17575 may be useful on several interfaces.

ISO 17575 also provides for basic media-independent communication services that may be used for

communication between Front End and Back End, which might be line-based or an air-link, and can also

be used for the air-link between OBE and central communication server.
Figure 1 — Scope of ISO 17575
vi © ISO 2016 – All rights reserved
---------------------- Page: 12 ----------------------
SIST EN ISO 17575-3:2016
ISO 17575-3:2016(E)
0.3 The parts of ISO 17575

Part 1: Charging, defines the attributes for the transfer of usage data from the Front End to the Back End.

The contents of charge reports might vary between toll regimes, hence, attributes for all requirements

are offered, ranging from attributes for raw localization data, for map-matched geographic objects and

for completely priced toll transactions. A toll regime comprises a set of rules for charging, including the

charged network, the charging principles, the liable vehicles and a definition of the required contents of

the charge report.

Part 2: Communication and connection to lower layers, defines basic communication services for data

transfer over the OBE air-link or between Front End and Back End. The data defined in ISO 17575-1 and

ISO 17575-3 can, but need not be, exchanged using the communication stack as defined in ISO 17575-2.

Part 3: Context data, defines the data to be used for a description of individual charging systems in

terms of charged geographical objects and charging and reporting rules. For every toll charger’s system,

attributes as defined in ISO 17575-3 are used to transfer data to the Front End in order to instruct it on

which data to collect and report.
0.4 Application needs covered by ISO 17575
The ISO 17575-series of standards
— is compliant with the architecture defined in ISO 17573:2010,

— supports charges for use of road sections (including bridges, tunnels, passes, etc.), passage of

cordons (entry/exit), and use of infrastructure within an area (distance, time),

— supports fee collection based on units of distance or duration, and based on occurrence of events,

— supports modulation of fees by vehicle category, road category, time of usage and contract type (e.g.

exempt vehicles, special tariff vehicles, etc.),
— supports limiting of fees by a defined maximum per period of usage,
— supports fees with different legal status (e.g. public tax, private toll),

— supports differing requirements of different toll chargers, especially in terms of

— geographic domain and context descriptions,
— contents and frequency of charge reports,
— feedback to the driver (e.g. green or red light), and

— provision of additional detailed data on request, e.g. for settling of disputes,

— supports overlapping geographic toll domains,
— supports adaptations to changes in
— tolled infrastructure,
— tariffs, and
— participating toll schemes, and

— supports the provision of trust guarantees by the service provider to the toll charger for the data

originated from the Front End.
© ISO 2016 – All rights reserved vii
---------------------- Page: 13 ----------------------
SIST EN ISO 17575-3:2016
---------------------- Page: 14 ----------------------
SIST EN ISO 17575-3:2016
INTERNATIONAL STANDARD ISO 17575-3:2016(E)
Electronic fee collection — Application interface definition
for autonomous systems —
Part 3:
Context data
1 Scope

This part of ISO 17575 defines the content, semantics and format of the data exchange between a Front

End (OBE plus optional proxy) and the corresponding Back End in autonomous toll systems. It defines the

data elements used to specify and describe the toll context details. Context data are transmitted from

the Back End to the Front End to configure it for the charging processes of the associated toll context.

In ISO 17575, context data is the description of the properties of a single instance of an electronic fee

collection (EFC) context. This single instance of an EFC context operates according to one of the basic

tolling principles such as
— road section charging,
— area charging (according to travelled distance or duration of time), and
— cordon charging.

EFC context data comprise a set of rules for charging, including the description of the charged network,

the charging principles, the liable vehicles and a definition of the required contents of the charge report.

This set of rules is defined individually for each EFC context according to local needs.

The following data and associated procedures are defined in this part of ISO 17575:

— data providing toll context overview information;

— data providing tariff information (including definitions of required tariff determinants such as

vehicle parameters, time classe, etc.);
— data providing context layout information;
— data providing reporting rules information.

This part of ISO 17575 also provides the required definitions and data specifications to be applied when

one single toll context is spilt inot more than one toll context partitions. This is applicable to cases

where one EFC scheme and the rules applied cannot be described with a single set of context data.

Annex A provides the data type specification using ASN.1 notation.

The protocol implementation conformity statements (PICS) proforma are provided in Annex B.

Annex C provides a graphical presentation of the structure of the toll context data.

Annexes D, E and F contain further information and descriptions, which may support the understanding

and the implementation of the rules specified in this part of ISO 17575.

Annex G provides information how this part of ISO 17575 can be used in a European Electronic Toll

Service (EETS) environment, with reference to EU Decision 2009/750.
© ISO 2016 – All rights reserved 1
---------------------- Page: 15 ----------------------
SIST EN ISO 17575-3:2016
ISO 17575-3:2016(E)
2 Normative references

The following documents, in whole or in part, are normatively referenced in this document and are

indispensable for its application. For dated references, only the edition cited applies. For undated

references, the latest edition of the referenced document (including any amendments) applies.

ISO 612, Road vehicles — Dimensions of motor vehicles and towed vehicles — Terms and definitions

ISO 1176, Road vehicles — Masses — Vocabulary and codes
ISO 4217, Codes for the representation of currencies and funds

ISO/IEC 8824-1:2008, Information technology — Abstract Syntax Notation One (ASN.1): Specification of

basic notation — Part 1

ISO/IEC 8825-2:2008, Information technology — ASN.1 encoding rules: Specification of Packed Encoding

Rules (PER) — Part 2

ISO 12813:2015, Electronic fee collection — Compliance check communication for autonomous systems

ISO 14906:2011/Amd1:2015, Electronic fee collection — Application interface definition for dedicated

short-range communication

ISO 17575-1:2016, Electronic fee collection — Application interface definition for autonomous systems —

Part 1: Charging

EN 15509:2014, Electronic fee collection — Interoperability application profile for DSRC

NIMA TR8350.2, Third Edition — Amendment 1, January 2000, Department of Defense — World

Geodetic System 1984, Its Definition and Relationships With Local Geodetic Systems, issued by National

Imagery and Mapping Agency (NIMA), US Department of Defense
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1
area charging
charging based on road usage within a given area
[SOURCE: ISO 17575-1:2016, 3.1]
3.2
attribute

addressable package of data consisting of a single data element or structured sequences of data elements

[SOURCE: ISO 17575-1:2016, 3.2]
3.3
authenticator
data, possibly encrypted, that is used for authentication
[SOURCE: EN 15509:2014, 3.3]
3.4
Back End
part of a back office system interfacing to one or more Front Ends (3.11)
[SOURCE: ISO 17575-1:2016, 3.4]
2 © ISO 2016 – All rights reserved
---------------------- Page: 16 ----------------------
SIST EN ISO 17575-3:2016
ISO 17575-3:2016(E)
3.5
charge object
geographic or road related object for the use of which a charge is applied
[SOURCE: ISO 17575-1:2016, 3.5]
3.6
charge report

information containing road usage and related information originated at the Front End (3.11)

[SOURCE: ISO 17575-1:2016, 3.6]
3.7
cordon
border line of an area
[SOURCE: ISO 17575-1:2016, 3.7]
3.8
cordon charging
charging for the crossing of a cordon (3.7)
[SOURCE: ISO 17575-1:2016, 3.8]
3.9
data element

coded information, which might itself consist of lower level information structures

[SOURCE: ISO 17575-1:2016, 3.9]
3.10
data set
logical set of data elements (3.9) with a semantic relation

Note 1 to entry: Data set is used only for better understanding and is fully independent from implementation

solutions.
3.11
Front End

part of a tolling system consisting of an OBE (3.13) and possibly a proxy (3.14) where road tolling

information and usage data are collected and processed for delivery to the Back End (3.4)

[SOURCE: ISO/TS 19299:2015, 3.17]

Note 1 to entry: The Front End comprises the on-board equipment (3.13) and an optional proxy (3.14).

3.12
layout
technical description of the location of tolled objects including their borders
3.13
on-board equipment
OBE

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

communication services
3.14
proxy

optional part of a Front End (3.11) that communicates with external equipment and processes the data

received into an agreed format to be delivered to the Back End (3.4)
[SOURCE: ISO 17575-1:2016, 3.13]
© ISO 2016 – All rights reserved 3
---------------------- Page: 17 ----------------------
SIST EN ISO 17575-3:2016
ISO 17575-3:2016(E)
3.15
road section charging
tolling principle where the fee is due if predefined sections of roads are used
[SOURCE: ISO 17575-1:2016, 3.14]
3.16
toll

charge, tax or duty levied in connection with using a vehicle in a toll domain (3.20)

[SOURCE: ISO/TS 19299:2015, 3.42, modified — “any” has been deleted from before “charge”.]

Note 1 to entry: The definition is the generalization of the classic definition of a toll as a charge, a tax, or a duty

for permission to pass a barrier or to proceed along a road, over a bridge, etc. The definition also includes fees

regarded as an (administrative) obligation, e.g. a tax or a duty.
3.17
tolled area
geographic area where a toll (3.16) is charged for road usage
3.18
toll context
logical view as defined by attributes
...