SIST-TS CEN/TS 16331:2012

SLOVENSKI STANDARD
SIST-TS CEN/TS 16331:2012
01-maj-2012
Elektronsko pobiranje pristojbin - Interoperabilni profili aplikacije za avtonomne
sisteme
Electronic fee collection - Interoperable application profiles for autonomous systems
Elektronische Gebührenerhebung - Interoperable Anwendungsprofile für unabhängige
Systeme
Perception du télépéage - Profil d'application d'interopérabilité pour les systèmes
autonomes
Ta slovenski standard je istoveten z: CEN/TS 16331:2012
ICS:
03.220.20 Cestni transport Road transport
35.240.60 Uporabniške rešitve IT v IT applications in transport
transportu in trgovini and trade
SIST-TS CEN/TS 16331:2012 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST-TS CEN/TS 16331:2012

---------------------- Page: 2 ----------------------

SIST-TS CEN/TS 16331:2012


TECHNICAL SPECIFICATION
CEN/TS 16331

SPÉCIFICATION TECHNIQUE

TECHNISCHE SPEZIFIKATION
March 2012
ICS 03.220.20; 35.240.60
English Version
Electronic fee collection - Interoperable application profiles for
autonomous systems
Perception du télépéage - Profil d'application Elektronische Gebührenerhebung - Interoperable
d'interopérabilité pour les systèmes autonomes Anwendungsprofile für unabhängige Systeme
This Technical Specification (CEN/TS) was approved by CEN on 8 January 2012 for provisional application.

The period of validity of this CEN/TS is limited initially to three years. After two years the members of CEN will be requested to submit their
comments, particularly on the question whether the CEN/TS can be converted into a European Standard.

CEN members are required to announce the existence of this CEN/TS in the same way as for an EN and to make the CEN/TS available
promptly at national level in an appropriate form. It is permissible to keep conflicting national standards in force (in parallel to the CEN/TS)
until the final decision about the possible conversion of the CEN/TS into an EN is reached.

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

Management Centre: Avenue Marnix 17, B-1000 Brussels
© 2012 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN/TS 16331:2012: E
worldwide for CEN national Members.

---------------------- Page: 3 ----------------------

SIST-TS CEN/TS 16331:2012
CEN/TS 16331:2012(E)
Contents Page
Foreword .5
Introduction .6
1 Scope .8
2 Normative references .9
3 Terms and definitions . 10
4 Abbreviations . 11
5 General profile independent IAP requirements . 12
5.1 The principle defining EFC cluster supported regime characteristics using profiles . 12
5.2 Toll Charger requirements . 12
5.2.1 General . 12
5.2.2 Toll Charge Back End requirements . 13
5.3 Toll Charger RSE requirements . 13
5.4 Service Provider requirements . 13
5.4.1 General . 13
5.4.2 Service Provider Back End Requirements . 14
5.4.3 Front End specific requirements . 14
6 The use of conditional requirements . 16
7 Standardised profiles . 16
7.1 General . 16
7.2 How to use standardised profiles . 21
7.2.1 General . 21
7.2.2 SR (Sectioned Roads tolling) . 21
7.2.3 SD (Sectioned Roads tolling or Distance based Area pricing) . 21
7.2.4 OSD (Overlapping Sectioned Roads tolling or Distance based Area pricing) . 22
7.2.5 OSDT (Overlapping Sectioned Roads tolling or Distance or Time based Area pricing) . 22
7.2.6 OSDTC (Overlapping Sectioned Roads tolling or Distance or Time based Area or Cordon
pricing) . 22
7.3 Front End classes selection . 22
Annex A (normative) Conditional profile requirements . 23
A.1 General . 23
A.2 Conditional requirements to be observed by the Toll Charger . 23
A.2.1 When using contextInterrelations . 23
A.2.2 When using roadSectionPricing . 23
A.2.3 When using arePricingDistance . 23
A.2.4 When using roadNetworks . 23
A.2.5 When using arePricingTime . 23
A.2.6 When using cordonPricing . 23
A.2.7 When using agnssGDFLayout or tollContextLayout . 24
A.2.8 When using tariffTable . 24
A.2.9 When using tariffClassDefinition . 24
A.2.10 When using localVehicleClassDefinition . 24
A.2.11 When using timeClassDefinition . 24
A.2.12 When using relativeTimePeriods . 24
A.2.13 When using classesSetExternally. 25
A.2.14 When using userClassdefinition . 25
A.2.15 When using actualNumberOfPassengers . 25
A.2.16 When using SectionLayout . 25
A.2.17 When using AreaLayout . 25
A.2.18 When using roadNetwork . 25
2

---------------------- Page: 4 ----------------------

SIST-TS CEN/TS 16331:2012
CEN/TS 16331:2012(E)
A.2.19 When using chargeReportingEvents . 25
A.2.20 When using chargeReportConfiguration . 25
A.3 Conditional requirements to be observed by the Service Provider . 27
A.3.1 When using tollDeclarationADU . 27
A.3.2 When using combinedChargeReportContexts. 28
A.3.3 When using precedenceLevel . 28
A.3.4 When using roadSectionPricing . 28
A.3.5 When using areaPricingDistance . 29
A.3.6 When using areaPricingDistance.roadNetworks . 29
A.3.7 When using areaPricingTime . 29
A.3.8 When using cordonPricing . 29
A.3.9 When using tariffTable . 29
A.3.10 When using tariffClassDefinition . 29
A.3.11 When using localVehiceClasses . 29
A.3.12 When using timeClasses . 29
A.3.13 When using timeClasses.ordinalElements.relativeTimeClasses . 30
A.3.14 When using timeClasses.nominalElements.classesSetEexternally . 30
A.3.15 When using userClasses . 30
A.3.16 When using tollContextLayout. 30
A.3.17 When using chargeReportingEvents . 30
A.3.18 When using chargeReportConfiguration . 30
A.4 Conditional requirements to be observed by the Front End . 30
A.4.1 When using in the ChargeReport all other elements than usageStatement . 30
A.4.2 When using in the ChargeReport the usageStatementList . 31
A.4.3 When using aggregatedFee. 31
A.4.4 When using aggregatedSingleTariffClassSession . 31
A.4.5 When using listOfChargeObjects . 31
A.4.6 When using listOfRawUsageData . 31
Annex B (normative) The use of identifiers . 32
B.1 General . 32
B.2 Identifiers specified in CEN ISO/TS 13141 . 36
B.3 Identifiers specified in CEN ISO/TS 17575-1 . 36
B.4 Identifiers specified in CEN ISO/TS 17575-3 . 38
B.5 Identifiers specified in CEN ISO/TS 17575-4 . 39
B.6 Identifiers specified in CEN ISO/TS 12813 . 39
B.7 Identifiers specified in EN ISO 12855 . 39
Annex C (normative) Protocol Implementation Conformance Statement . 41
C.1 Guidance for completing the PICS proforma . 41
C.1.1 Purposes and structure . 41
C.1.2 Abbreviations and conventions . 41
C.1.3 Instructions for completing the PICS proforma . 43
C.2 PICS proforma for the Toll Charger’s Back-end . 43
C.2.1 Identification of the implementation . 43
C.2.2 Identification of the protocol . 46
C.2.3 Global statement of conformance . 46
C.2.4 Profiles. 46
C.2.5 EN ISO 12855 . 46
C.3 PICS proforma for the Toll Charger RSE . 50
C.3.1 Identification of the implementation . 50
C.3.2 Identification of the protocol . 52
C.3.3 Global statement of conformance . 52
C.3.4 Support for CCC and LAC Applications . 52
C.4 PICS proforma for the Service Provider Back-end . 54
C.4.1 Identification of the implementation . 54
C.4.2 Identification of the protocol . 56
C.4.3 Global statement of conformance . 56
C.4.4 Profiles. 57
C.4.5 EN ISO 12855 . 57
3

---------------------- Page: 5 ----------------------

SIST-TS CEN/TS 16331:2012
CEN/TS 16331:2012(E)
C.5 PICS proforma for the Service Provider Front End . 61
C.5.1 Identification of the implementation . 61
C.5.2 Identification of the protocol . 63
C.5.3 Global statement of conformance . 63
C.5.4 Front End Class . 64
C.5.5 CEN ISO/TS 17575-1 Charge Report - Usage Statement. 64
C.5.6 CEN ISO/TS 17575-3 –Charge Report Configuration . 64
C.5.7 Support for CCC and LAC Applications . 65
Annex D (informative) IAP taxonomy and numbering . 66
D.1 General . 66
D.2 Taxonomy of Interoperable Application Profiles (IAP) . 66
D.2.1 Specified profiles . 66
D.2.2 Future new profiles . 67
D.3 IAP numbering and referencing . 67
D.3.1 IAP numbering . 67
D.3.2 IAP referencing . 67
Annex E (informative) How to define new profiles - the profile creation principle . 68
Bibliography . 69

4

---------------------- Page: 6 ----------------------

SIST-TS CEN/TS 16331:2012
CEN/TS 16331:2012(E)
Foreword
This document (CEN/TS 16331:2012) has been prepared by Technical Committee CEN/TC 278 “Road
transport and traffic telematics”, the secretariat of which is held by NEN.
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 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 announce this Technical Specification: 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, Romania, Slovakia, Slovenia,
Spain, Sweden, Switzerland, Turkey and the United Kingdom.
5

---------------------- Page: 7 ----------------------

SIST-TS CEN/TS 16331:2012
CEN/TS 16331:2012(E)
Introduction
This Technical Specification should be used by stakeholders of a group of electronic fee collection (EFC)
regimes as a guide when planning to establish or extending an EFC cluster providing interoperability for tolled
vehicles in all participating EFC domains.
The scope of this document covers the tolling principles for autonomous EFC systems.
The goal of an interoperable EFC cluster is to ensure that all tolled vehicles can be charged the due toll
amount in all EFC domains. This can be achieved by requiring that all necessary equipment, whether in the
tolled vehicles, the Toll Service Providers’ central systems, the Toll Chargers’ central systems and along the
roadside in the EFC domains, conform to the same interface standards and to an Interoperable Application
Profile, as defined in this Technical Specification.
The system architecture defined in ISO 17573 is the basis for all standards that relate to Electronic Fee
Collection systems. It specifies the roles and responsibilities needed within an interoperable EFC cluster.
Such a cluster is illustrated in Figure 1, and consists of multiple Toll Service Providers and multiple Toll
Chargers. Each Toll Charger has its own EFC Domain and its own EFC regime. Conversely, each Toll Service
Provider has a number of clients, who own vehicles and may be liable to pay toll in the EFC domains of the
Toll Chargers.

Figure 1 — Actors and interfaces within an interoperable EFC cluster
CEN has produced a set of standards that together specify a basis for EFC systems. This document refers to
these standards as the ‘base standards’. They are necessary to ensure technical interoperability between
different EFC-systems, but in themselves they are not sufficient to achieve this, as they contain a large
number of options and choices to be made in a concrete implementation.
6

---------------------- Page: 8 ----------------------

SIST-TS CEN/TS 16331:2012
CEN/TS 16331:2012(E)
Figure 2 shows the base standards and their relationships.

Figure 2 — Suite of EFC related standards
NOTE There may be one or more instances of each box representing an actor
This set of base standards includes the CEN ISO/TS 17575-suite, ISO 17573, EN ISO 12855,
CEN ISO/TS 13141 and CEN ISO/TS 12813. These standards have the characteristic of toolbox standards,
specifying messages and data elements, which - if used – are to be used in the prescribed way. However,
these base standards contain many optional features that may or may not be implemented by different Toll
Chargers or Service Providers. Therefore, the base standards alone do not guarantee interoperability between
the systems of different actors without further restrictions of the use of optional features of these base
standards. This is the purpose of this profile standard – to restrict the choices from the above listed set of
base standards.
This Technical Specification defines a number of Interoperable Application Profiles (IAP) for autonomous
Electronic Fee Collection systems, according to the concept of "International Standardised Profiles (ISP)" as
defined in ISO IEC/TR 10000-1. Each profile provides a coherent set of choices from among the options in the
base standards. A profile thus may be used to determine a concrete set of requirements for EFC constituents.
When multiple EFC systems are based on the same profile, the profile will serve as a common technical
platform for EFC interoperability. Which profile should be chosen will depend on the needs of all participants in
this EFC cluster and on the outcome of negotiations between them.
The profiles in this Technical Specification were created in order to meet the requirements of early adoptions
of the general principles of autonomous interoperable EFC clusters, such as the upcoming European
Electronic Toll Service. This Technical Specification specifies also a methodology to define a customised
profile if none of the specified profiles are acceptable to all participants in an interoperable EFC cluster.
7

---------------------- Page: 9 ----------------------

SIST-TS CEN/TS 16331:2012
CEN/TS 16331:2012(E)
Each Toll Service Provider taking part in an EFC cluster should be aware that he needs to implement all the
features of the chosen profile. Therefore, it will generally be in the best interest of the Service Providers to
select the simplest profile that is still acceptable to all Toll Chargers.
Toll Chargers within the same EFC cluster, however, still have the choice to use any of these features or not.
1 Scope
This Technical Specification defines a set of interoperable application profiles suitable to be used defining the
overall functionality of an interoperable EFC cluster using autonomous vehicle equipment. Doing so, it also
defines a way of defining further profiles for future use.
The profiles cover a wide range from simple toll road systems up to very complex tolling principles and tariff
rules. An EFC cluster shall select and use one of these profiles covering the needs of all participating Toll
Chargers.
The scope is limited to those base standards providing data elements or messages to be used specifically
when defining the data exchange for autonomous tolling principles. This covers ISO 17573 and the base
standards CEN ISO/TS 17575 parts 1 to 4, CEN ISO/TS 12813, CEN ISO/TS 13141 and those parts of
EN ISO 12855 specifying messages which are only relevant for autonomous systems.
Figure 3 provides a graphical illustration of the scope of this Interoperable Application Profile which is based
on the ISP concept according to ISO IEC/TR 10000-1.

Figure 3 — The scope of this IAP covers the interfaces within the dotted lined box

8

---------------------- Page: 10 ----------------------

SIST-TS CEN/TS 16331:2012
CEN/TS 16331:2012(E)
For each specified profile, the conditional requirements resulting from the actual use of data elements being
still optional according to this profile are specified in Annex A. A set of rules on how to re-use identifiers of a
specific entity within the full chain of transactions is specified in Annex B and a protocol implementation
conformance statement (PICS) proforma in Annex C.
Outside of the scope are:
 details on how to achieve security using the authenticator data elements of the base standards;
 how to operate the enforcement process;
 commercial aspects and the billing process;
 the handling of DSRC charging transactions;
 system monitoring and performance indicators;
 test standards;
 the initial configuration of the OBE.
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 17573:2010, Electronic fee collection - Systems architecture for vehicle-related tolling
EN ISO 12855:2009, Electronic fee collection – Information exchange between service provision and toll
charging (ISO/DIS 12855:2009)
CEN ISO/TS 12813:2009, Electronic fee collection - Compliance check communication for autonomous
systems (ISO/TS 12813:2009)
CEN ISO/TS 13141:2010, Electronic fee collection - Localisation augmentation communication for
autonomous systems (ISO/TS 13141:2010)
CEN ISO/TS 17575-1:2010, Electronic fee collection - Application interface definition for autonomous systems
- Part 1: Charging (ISO/TS 17575-1:2010)
CEN ISO/TS 17575-2:2010
...