Electronic fee collection - Compliance check communication for autonomous systems (ISO 12813:2019)

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).

Elektronische Gebührenerhebung - Kommunikation zur Übereinstimmungsprüfung für autonome Systeme (ISO 12813:2019)

Perception du télépéage - Communication de contrôle de conformité pour systèmes autonomes (ISO 12813:2019)

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 e

Elektronsko pobiranje pristojbin - Komunikacija za potrditev skladnosti avtonomnih sistemov (ISO 12813:2019)

Ta dokument določa zahteve za komunikacijo kratkega dosega za namene preverjanja skladnosti avtonomnih sistemov za elektronsko pobiranje pristojbin. Komunikacija za preverjanje skladnosti (CCC) poteka med opremo, vgrajeno v cestno vozilo (OBE), in čitalnikom (ob cesti nameščena oprema, mobilna naprava ali ročna enota) ter omogoča preverjanje, ali podatki, dostavljeni v opremo, vgrajeno v cestno vozilo, pravilno odražajo uporabo ceste ustreznega vozila v skladu s pravili pristojnega režima cestninjenja. Upravljavec čitalnika za preverjanje skladnosti se obravnava kot del postopka zaračunavanja cestnine, kot je določeno v standardu ISO 17573-1. Komunikacija za preverjanje skladnosti dovoljuje prepoznavanje opreme, vgrajene v cestno vozilo, vozila in pogodbe ter omogoča preverjanje tega, ali je voznik izpolnil svoje obveznosti, kakšno je stanje preverjanja in ali oprema, vgrajena v vozilo, deluje pravilno. Komunikacija za preverjanje skladnosti omogoča branje, ne pa tudi zapisovanja podatkov opreme, vgrajene v vozilo. Ta dokument se uporablja za opremo, vgrajeno v vozilo, v avtonomnem načinu delovanja; ne uporablja se za preverjanje skladnosti v namenskih sistemih za zaračunavanje na podlagi komunikacije kratkega dosega (DSRC). Določa skladnjo in semantiko podatkov, ne pa komunikacijskega zaporedja. Vsi atributi, določeni v tem dokumentu, so zahtevani za katero koli opremo, vgrajeno v vozilo, ki naj bi bila v skladu s tem dokumentom, tudi če so nekatere vrednosti nastavljene kot »nedoločene« v primerih, ko oprema, vgrajena v vozilo, nima določene funkcionalnosti. Čitalnik lahko poljubno izbere atribute za branje v fazi pridobivanja podatkov in zaporedje, v katerem so prebrani. Za doseganje združljivosti z obstoječimi sistemi komunikacija uporablja atribute, določene v standardu ISO 14906, kjer koli je to uporabno. Komunikacija za preverjanje skladnosti je primerna za nabor medijev za komunikacijo kratkega dosega. Posebne opredelitve so podane za CEN-DSRC, kot je določeno v standardu EN 15509, ter za uporabo standarda ISO CALM IR, italijanskega sistema namenske komunikacije kratkega dosega, kot je določeno v standardih ETSI ES 200 674-1, ARIB DSRC in WAVE DSRC kot alternativah standardu CEN-DSRC. Opredeljeni atributi in funkcije so namenjeni za preverjanje skladnosti s pomočjo komunikacijskih storitev kratkega dosega, ki jih zagotavlja aplikacijski nivo kratkega dosega, pri čemer so atributi in funkcije komunikacije za preverjanje skladnosti dostopni aplikacijam za preverjanje skladnosti pri obcestni opremi (RSE) in opremi, vgrajeni v vozilo. Atributi in funkcije so določeni na ravni aplikacijskih podatkovnih enot (ADU).

General Information

Status
Published
Public Enquiry End Date
29-Nov-2018
Publication Date
03-Feb-2020
Technical Committee
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
12-Dec-2019
Due Date
16-Feb-2020
Completion Date
04-Feb-2020

RELATIONS

Buy Standard

Standard
SIST EN ISO 12813:2020
English language
62 pages
sale 10% off
Preview
sale 10% off
Preview

e-Library read for
1 day

Standards Content (sample)

SLOVENSKI STANDARD
SIST EN ISO 12813:2020
01-marec-2020
Nadomešča:
SIST EN ISO 12813:2016
SIST EN ISO 12813:2016/A1:2017
Elektronsko pobiranje pristojbin - Komunikacija za potrditev skladnosti
avtonomnih sistemov (ISO 12813:2019)

Electronic fee collection - Compliance check communication for autonomous systems

(ISO 12813:2019)
Elektronische Gebührenerhebung - Kommunikation zur Übereinstimmungsprüfung für
autonome Systeme (ISO 12813:2019)
Perception du télépéage - Communication de contrôle de conformité pour systèmes
autonomes (ISO 12813:2019)
Ta slovenski standard je istoveten z: EN ISO 12813:2019
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 12813:2020 en,fr,de

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

---------------------- Page: 1 ----------------------
SIST EN ISO 12813:2020
---------------------- Page: 2 ----------------------
SIST EN ISO 12813:2020
EN ISO 12813
EUROPEAN STANDARD
NORME EUROPÉENNE
December 2019
EUROPÄISCHE NORM
ICS 03.220.20; 35.240.60 Supersedes EN ISO 12813:2015
English Version
Electronic fee collection - Compliance check
communication for autonomous systems (ISO
12813:2019)

Perception de télépéage - Communication de contrôle Elektronische Gebührenerhebung - Kommunikation

de conformité pour systèmes autonomes (ISO zur Übereinstimmungsprüfung für autonome Systeme

12813:2019) (ISO 12813:2019)
This European Standard was approved by CEN on 5 October 2019.

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, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway,

Poland, Portugal, Republic of North Macedonia, Romania, Serbia, 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: Rue de la Science 23, B-1040 Brussels

© 2019 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN ISO 12813:2019 E

worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
SIST EN ISO 12813:2020
EN ISO 12813:2019 (E)
Contents Page

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

---------------------- Page: 4 ----------------------
SIST EN ISO 12813:2020
EN ISO 12813:2019 (E)
European foreword

This document (EN ISO 12813:2019) 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 June 2020, and conflicting national standards shall be

withdrawn at the latest by June 2020.

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

patent rights. CEN shall not be held responsible for identifying any or all such patent rights.

This document supersedes EN ISO 12813:2015.

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, France, Germany, Greece, Hungary, Iceland,

Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Republic of

North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the

United Kingdom.
Endorsement notice

The text of ISO 12813:2019 has been approved by CEN as EN ISO 12813:2019 without any modification.

---------------------- Page: 5 ----------------------
SIST EN ISO 12813:2020
---------------------- Page: 6 ----------------------
SIST EN ISO 12813:2020
INTERNATIONAL ISO
STANDARD 12813
Second edition
2019-11
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
Reference number
ISO 12813:2019(E)
ISO 2019
---------------------- Page: 7 ----------------------
SIST EN ISO 12813:2020
ISO 12813:2019(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO 2019

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
Fax: +41 22 749 09 47
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO 2019 – All rights reserved
---------------------- Page: 8 ----------------------
SIST EN ISO 12813:2020
ISO 12813:2019(E)
Contents Page

Foreword ..........................................................................................................................................................................................................................................v

Introduction ..............................................................................................................................................................................................................................vii

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

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

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

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

5 Application interface architecture ..................................................................................................................................................... 5

5.1 General ........................................................................................................................................................................................................... 5

5.2 Services provided ................................................................................................................................................................................. 5

5.3 Attributes ..................................................................................................................................................................................................... 6

5.4 Toll context ................................................................................................................................................................................................. 6

5.5 Use of lower layers ............................................................................................................................................................................... 6

5.5.1 Supported DSRC communication stacks ..................................................................................................... 6

5.5.2 Use of the CEN-DSRC stack...................................................................................................................................... 7

6 Functions ...................................................................................................................................................................................................................... 7

6.1 Functions in detail ................................................................................................................................................................................ 7

6.1.1 General...................................................................................................................................................................................... 7

6.1.2 Initialise communication .......................................................................................................................................... 7

6.1.3 Data retrieval ...................................................................................................................................................................... 8

6.1.4 Authenticated data retrieval .................................................................................................................................. 8

6.1.5 Driver notification .......................................................................................................................................................... 8

6.1.6 Terminate communication ...................................................................................................................................... 8

6.1.7 Test communication ...................................................................................................................................................... 8

6.2 Security .......................................................................................................................................................................................................... 8

6.2.1 General...................................................................................................................................................................................... 8

6.2.2 Authentication/non-repudiation ....................................................................................................................... 9

6.2.3 Access credentials ........................................................................................................................................................... 9

7 Attributes ..................................................................................................................................................................................................................... 9

7.1 General ........................................................................................................................................................................................................... 9

7.2 Data regarding identification ......... ..........................................................................................................................................11

7.3 Data regarding status .....................................................................................................................................................................11

7.4 Data regarding vehicle ...................................................................................................................................................................18

8 Transaction model ...........................................................................................................................................................................................20

8.1 General ........................................................................................................................................................................................................20

8.2 Initialisation phase ...........................................................................................................................................................................20

8.2.1 Initialisation request .................................................................................................................................................20

8.2.2 CCC application-specific contents of BST ................................................................................................20

8.2.3 CCC application-specific contents of VST.................................................................................................21

8.3 Transaction phase .............................................................................................................................................................................21

Annex A (normative) CCC data type specifications .............................................................................................................................22

Annex B (normative) PICS proforma .................................................................................................................................................................23

Annex C (informative) ETSI ES 200 674-1 communication stack usage for CCC applications ................31

Annex D (informative) Using the IR DSRC communication stack (CALM IR) for CCC applications ...34

Annex E (informative) Using the ARIB DSRC communication stack for CCC applications ..........................35

Annex F (informative) Using the WAVE communication stack for CCC applications .......................................37

Annex G (informative) Example CCC transaction ..................................................................................................................................40

Annex H (informative) Security considerations ....................................................................................................................................42

© ISO 2019 – All rights reserved iii
---------------------- Page: 9 ----------------------
SIST EN ISO 12813:2020
ISO 12813:2019(E)

Annex I (informative) Use of this document for the EETS ...........................................................................................................47

Bibliography .............................................................................................................................................................................................................................49

iv © ISO 2019 – All rights reserved
---------------------- Page: 10 ----------------------
SIST EN ISO 12813:2020
ISO 12813:2019(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.

This second edition cancels and replaces the first edition (ISO 12813:2015), which has been technically

revised. It also incorporates the Amendment ISO 12813:2015/Amd 1:2017.
The main changes compared to the previous edition are as follows:

— inclusion of the changes of ISO 12813:2015/Amd 1:2017(E), i.e. it defines the electronic fee collection

compliance check communication using the WAVE communication stack as defined in IEEE;

— reverting the length of attribute GnssStatus back to 23 octets and removing the data element of type

Altitude;

— allowing a maximum of two instances of AID = 20 in the ApplicationList in the VST;

— adding values goSuspicion (5) and noGoPaymentMeans (4) to the data element statusIndicator as

well as updating and clarifying the semantic definitions of all statuses and when they change;

— updating the OBEStatusHistory – timeWhenChanged and ExtendedOBEStatusHistory

-timeWhenChanged/timeWhenChangedToPrevious based on the updated sematic definition of

statusIndicator;

— clarifing the relationship between the LLLL element in VehicleClass and the LocalVehicleClassId

(imported from ISO 17575-3);

— clarifing that ExtendedOBEStatusHistory - timeWhenChangedToPrevious shall be set to zero in

case no previous value is available;

— clarifing that VehicleWeightHistory – timeWhenChangedToCurrentValue changes not only due to

changes in the attribute VehicleCurrentMaxTrainWeight but also changes in the assignment of the

LocalVehicleClassId or the LLL element within VehicleClass;
© ISO 2019 – All rights reserved v
---------------------- Page: 11 ----------------------
SIST EN ISO 12813:2020
ISO 12813:2019(E)

— adding the EFC attributes ExtendedOBUStatusHistoryPart1, ExtendedOBUStatusHistoryPart2 and

UserConfirmation;
— updating Annex C by adding the attributes VehicleCurrentMaxTrainWeight and

AttributeUpdateInterval to the information in virtual memory according to ETSI ES 200 674-1

communication stack usage for CCC applications.

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 © ISO 2019 – All rights reserved
---------------------- Page: 12 ----------------------
SIST EN ISO 12813:2020
ISO 12813:2019(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, standardised 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

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.
© ISO 2019 – All rights reserved vii
---------------------- Page: 13 ----------------------
SIST EN ISO 12813:2020
ISO 12813:2019(E)

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 interrogator 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

different OBE can work according to quite different principles, the possibilities for doing this in a

standardised 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.

1) 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.
viii © ISO 2019 – All rights reserved
---------------------- Page: 14 ----------------------
SIST EN ISO 12813:2020
ISO 12813:2019(E)

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.
© ISO 2019 – All rights reserved ix
---------------------- Page: 15 ----------------------
SIST EN ISO 12813:2020
---------------------- Page: 16 ----------------------
SIST EN ISO 12813:2020
INTERNATIONAL STANDARD ISO 12813:2019(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 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
...

Questions, Comments and Discussion

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