EN ISO 14906:2004
(Main)Road transport and traffic telematics - Electronic fee collection - Application interface definition for dedicated short-range communication (ISO 14906:2004)
Road transport and traffic telematics - Electronic fee collection - Application interface definition for dedicated short-range communication (ISO 14906:2004)
ISO 14906:2004 specifies the application interface in the context of Electronic Fee Collection (EFC) systems using the Dedicated Short-Range communication (DSRC). The EFC application interface is the EFC application process interface to the DSRC Application Layer.
ISO 14906:2004 is applicable to the EFC attributes (i.e. EFC application information); the addressing procedures of EFC attributes and (hardware) components (e.g. ICC and MMI); EFC application functions, i.e. further qualification of actions by definitions of the concerned services, assignment of associated ActionType values and content and meaning of action parameters; the EFC transaction model, which defines the common elements and steps of any EFC transaction; the behaviour of the interface so as to ensure interoperability on an EFC-DSRC application interface level.
This is an interface standard, adhering to the open systems interconnection (OSI) philosophy (ISO/IEC 7498-1), and it is, as such, not concerned with the implementation choices to be realised at either side of the interface.
ISO 14906:2004 provides security-specific functionality as place holders (data and functions) to enable the implementation of secure EFC transactions. Yet the specification of the security policy (including specific security algorithms and key management) remains at the discretion and under the control of the EFC operator, and hence is outside the scope of ISO 14906:2004.
Straßenverkehrstelematik - Elektronische Gebührenerfassung (EFC) - Anforderungen an die EFC-Schnittstelle für Fahrzeug-Baken-Kommunikation (ISO 14906:2004)
Télématique de la circulation et du transport routier - Perception du télépéage - Définition de l'interface d'application relative aux communications dédiées à courte portée (ISO 14096:2004)
Cestna transportna in prometna telematika (RTTT) – Elektronsko pobiranje pristojbin – Definicija aplikacijskega vmesnika za posebne komunikacije kratkega dosega (ISO 14906:2004)
General Information
Relations
Standards Content (Sample)
SLOVENSKI STANDARD
01-januar-2005
1DGRPHãþD
SIST ENV ISO 14906:2003
Cestna transportna in prometna telematika (RTTT) – Elektronsko pobiranje
pristojbin – Definicija aplikacijskega vmesnika za posebne komunikacije kratkega
dosega (ISO 14906:2004)
Road transport and traffic telematics - Electronic fee collection - Application interface
definition for dedicated short-range communication (ISO 14906:2004)
Straßenverkehrstelematik - Elektronische Gebührenerfassung (EFC) - Anforderungen an
die EFC-Schnittstelle für Fahrzeug-Baken-Kommunikation (ISO 14906:2004)
Télématique de la circulation et du transport routier - Perception du télépéage - Définition
de l'interface d'application relative aux communications dédiées a courte portée (ISO
14096:2004)
Ta slovenski standard je istoveten z: EN ISO 14906:2004
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
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
EUROPEAN STANDARD
EN ISO 14906
NORME EUROPÉENNE
EUROPÄISCHE NORM
September 2004
ICS 35.240.60 Supersedes ENV ISO 14906:1998
English version
Road transport and traffic telematics - Electronic fee collection -
Application interface definition for dedicated short-range
communication (ISO 14906:2004)
Télématique de la circulation et du transport routier - Straßenverkehrstelematik - Elektronische
Perception du télépéage - Définition de l'interface Gebührenerfassung (EFC) - Anforderungen an die EFC-
d'application relative aux communications dédiées à courte Schnittstelle für Fahrzeug-Baken-Kommunikation (ISO
portée (ISO 14096:2004) 14906:2004)
This European Standard was approved by CEN on 30 April 2004.
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 Central Secretariat 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 Central Secretariat has the same status as the official
versions.
CEN members are the national standards bodies of Austria, Belgium, Cyprus, Czech Republic, Denmark, Estonia, Finland, France,
Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Slovakia,
Slovenia, Spain, Sweden, Switzerland and United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION
EUROPÄISCHES KOMITEE FÜR NORMUNG
Management Centre: rue de Stassart, 36 B-1050 Brussels
© 2004 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN ISO 14906:2004: E
worldwide for CEN national Members.
Contents
page
Foreword.3
Introduction .4
1 Scope.5
2 Normative references.6
3 Terms and definitions .7
4 Abbreviations.9
5 EFC application interface architecture.12
5.1 Relation to the DSRC communication architecture.12
5.2 Usage of DSRC application layer by the EFC application interface .13
5.3 Addressing of EFC attributes .13
5.4 Addressing of components.15
6 EFC Transaction Model.16
6.1 General.16
6.2 Initialisation Phase.16
6.3 Transaction phase.19
7 EFC Functions .21
7.1 Overview and general concepts .21
7.2 EFC functions .25
8 EFC Attributes .42
8.1 General.42
8.2 Data group CONTRACT.44
8.3 Data group RECEIPT .46
8.4 Data group VEHICLE .50
8.5 Data group EQUIPMENT .51
8.6 Data group DRIVER .51
8.7 Data group PAYMENT .52
Annex A (normative) EFC data type specifications .53
Annex B (informative) CARDME transaction .68
Annex C (informative) Examples of EFC transaction types.97
Annex D (informative) Functional requirements .108
Bibliography .115
Foreword
This document (EN ISO 14906:2004) has been prepared by Technical Committee CEN/TC 278 "Road Transport
and Traffic Telematics (RTTT)", the secretariat of which is held by NEN, in collaboration with Technical Committee
ISO/TC 204 “Intelligent Transport Systems (ITS)”.
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 March 2005, and conflicting national standards shall be withdrawn at the latest by
March 2005.
This document supersedes ENV ISO 14906:1998.
In order to facilitate migration from ENV ISO 14906, equipment procured and installed in accordance with ENV ISO
14906 has been considered when drafting this European Standard. Operation of such equipment and procurement
of additional equipment for systems based on such equipment can continue with reference to Directive 93/36/EEG
Article 8 item 3c.
According to the CEN/CENELEC Internal Regulations, the national standards organizations of the following
countries are bound to implement this European Standard: Austria, Belgium, Cyprus, Czech Republic, Denmark,
Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta,
Netherlands, Norway, Poland, Portugal, Slovakia, Slovenia, Spain, Sweden, Switzerland and United Kingdom.
Introduction
This document specifies an application interface for Electronic Fee Collection (EFC) systems, which are based on
the Dedicated Short-Range Communication (DSRC). It supports interoperability between EFC systems on an EFC-
DSRC application interface level.
This document provides specifications for the EFC transaction model, EFC data elements (referred to as attributes)
and functions, from which an EFC transaction can be built. The EFC transaction model provides a mechanism that
allows handling of different versions of EFC transactions and associated contracts. A certain EFC transaction
supports a certain set of EFC attributes and EFC functions as defined in this European Standard. It is not
envisaged that the complete set of EFC attributes and functions is present in each piece of EFC equipment, be on-
board equipment (OBE) or roadside equipment (RSE).
This document provides the basis for agreements between operators, which are needed to achieve interoperability.
Based on the tools specified in this document, interoperability can be reached by operators recognising each
others EFC transactions (including the exchange of security algorithms and keys) and implementing the EFC
transactions in each others RSE, or they may reach an agreement to define a new transaction (and contract) that is
common to both. Considerations should also be made by each operator that the RSE has sufficient resources to
implement such additional EFC transactions.
In order to achieve interoperability, operators should agree on issues like:
— which optional features are actually being implemented and used;
— access rights and ownership of EFC application data in the OBE;
— security policy (including encryption algorithms and key management, if applicable);
— operational issues, such as how many receipts may be stored for privacy reasons, how many receipts are
necessary for operational reasons (e.g. as entry tickets or as proof of payment);
— the agreements needed between operators in order to regulate the handling of different EFC transactions.
This document has the following structure. In the first four clauses the scope, normative references, definitions of
terms and abbreviations are accounted for. Next, in Clause 5, the EFC Application interface architecture is
described in terms of its relation to the DSRC communication architecture, including the addressing of data
attributes and of components. In the following Clause 6, the EFC transaction model is introduced, defining the
common steps of each EFC transaction, in particular the initialisation phase. Clauses 7 and 8 are dedicated to the
detailed specification of the EFC application functions and of the EFC data attributes, respectively. Four annexes
provide:
1. Annex A: the normative ASN.1 specifications of the used data types (EFC action parameters and attributes);
2. Annex B: an informative example of a transaction based on the CARDME specification, including bit-level
specification;
3. Annex C: informative examples of EFC transaction types, using the specified EFC functions and attributes;
4. Annex D: an informative listing of functional requirements, which can be satisfied by using the tools provided by
this document.
1 Scope
This document specifies the application interface in the context of Electronic Fee Collection (EFC) systems using
the Dedicated Short-Range Communication (DSRC).
The EFC application interface is the EFC application process interface to the DSRC Application Layer, as can be
seen in Figure 1 below. The scope of this document comprises specifications of:
— EFC attributes (i.e. EFC application information);
— the addressing procedures of EFC attributes and (hardware) components (e.g. ICC and MMI);
— EFC application functions, i.e. further qualification of actions by definitions of the concerned services,
assignment of associated ActionType values and content and meaning of action parameters;
— the EFC transaction model, which defines the common elements and steps of any EFC transaction;
— the behaviour of the interface so as to ensure interoperability on an EFC-DSRC application interface level.
Figure 1 — The EFC application interface
This is an interface standard, adhering to the open systems interconnection (OSI) philosophy (ISO/IEC 7498-1),
and it is as such not concerned with the implementation choices to be realised at either side of the interface.
This document provides security-specific functionality as place holders (data and functions) to enable the
implementation of secure EFC transactions. Yet the specification of the security policy (including specific security
algorithms and key management) remains at the discretion and under the control of the EFC operator, and hence is
outside the scope of this document.
2 Normative references
The following referenced documents are indispensable for the application of this document. For dated ref
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.