M/018 - Road Transport & Traffic Telem

The EFC application interface is the EFC application process interface to the DSRC application layer, as
can be seen in Figure 1 below. This document comprises specifications of:
— EFC attributes (i.e. EFC application information) that can also be used for other applications and/or
interfaces,
— 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 (see ISO/
IEC 7498-1), and it is as such not primarily 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.

This document specifies the application interface in the context of electronic fee collection (EFC) systems using the dedicated short-range communication (DSRC).

This International Standard establishes a  common framework data structure for  unambiguous identification in RTTT/ITS  systems. It excludes any physical aspects  such as interfaces. It is neither frequency-  nor air interface protocol-specific. Data  elements that form part of transmission or  storage protocols such as headers, frame  markers and checksums are thus excluded.  The specifications for protecting against  changes, classifying and qualifying security  aspects of the data structure elements are  not included within this International  Standard. The principles of data element  structure and description determined in  ISO/IEC 8824, ISO/IEC 8825-1 and ISO/IEC  8825-2 have been adopted to provide an  interoperable architecture within a standard  framework according to guidelines from  ISO/TC 204 and CEN/TC 278. This  International Standard defines data  structures based on the ISO/IEC 8824-1  ASN.1 UNIVERSAL CLASS types that may  be directly IMPORTED to other application  standards that would need only subsets of  the full APPLICATION CLASS types. These  UNIVERSAL CLASS and APPLICATION  CLASS types are uniquely defined as an  ASN.1 module in Annex B. This module  may be directly linked into an application  data definition. This International Standard  defines default encoding for simple AVI/AEI  applications where no other relevant  application standard exists. This definition  forms Clause 4.

ISO 14816:2005 establishes a common framework data structure for unambiguous identification in RTTT/ITS systems. It excludes any physical aspects such as interfaces. It is neither frequency- nor air interface protocol-specific.
Data elements that form part of transmission or storage protocols such as headers, frame markers and checksums are thus excluded.
The specifications for protecting against changes, classifying and qualifying security aspects of the data structure elements are not included within ISO 14816:2005.
The principles of data element structure and description determined in ISO/IEC 8824, ISO/IEC 8825-1 and ISO/IEC 8825-2 have been adopted to provide an interoperable architecture within a standard framework according to guidelines from ISO/TC 204 and CEN/TC 278.
ISO 14816:2005 defines data structures based on the ISO/IEC 8824-1 ASN.1 UNIVERSAL CLASS types that may be directly IMPORTED to other application standards that would need only subsets of the full APPLICATION CLASS types. These UNIVERSAL CLASS and APPLICATION CLASS types are uniquely defined as an ASN.1 module in Annex B. This module may be directly linked into an application data definition.
ISO 14816:2005 defines default encoding for simple AVI/AEI applications where no other relevant application standard exists. This definition forms Clause 4.

It is the scope of this Prestandard to define generic AVI/AEI System specification for nominal AVI/AEI to provide an enabling Standard, which, whilst allowing the system specifier to determine the performance levels and operating conditions, provides a framework for nominal interoperability.

ISO 14815:2005 defines a generic Automatic Vehicle Identification/Automatic Equipment Identification (AVI/AEI) System specification for nominal AVI/AEI to provide an enabling International Standard, which, whilst allowing the system specifier to determine the performance levels and operating conditions, provides a framework for nominal interoperability.

The DSRC Standards EN 12253, EN 12795 and EN 12834, which together form a three-layered architecture for DSRC, are designed to encompass a wide range of services for different purposes in order to make the basic DSRC architecture suited for many different applications and for a wide range of possible products and systems.
This document:
-   specifies a physical layer at 5,8 GHz for DSRC as applicable in the field of Road Transport and Traffic Telematics (RTTT).
-   provides requirements for the communication medium to be used for exchange of information between road-side units (RSU) and on-board units (OBU).
-   caters for a communication means to be used by several applications in the RTTT sector.

The DSRC Standards EN 12253, EN 12795 and EN 12834, which together form a three-layered architecture for DSRC, are designed to encompass a wide range of services for different purposes in order to make the basic DSRC architecture suited for many different applications and for a wide range of possible products and systems.
This document:
-   specifies a physical layer at 5,8 GHz for DSRC as applicable in the field of Road Transport and Traffic Telematics (RTTT).
-   provides requirements for the communication medium to be used for exchange of information between road-side units (RSU) and on-board units (OBU).
-   caters for a communication means to be used by several applications in the RTTT sector.

DOCUMENT ON HOLD (2003-02-20) => BT C87/2002 IN COURSE - WAITING FOR GREEN LIGHT FROM PM TO GO ON WITH THE PROCEDURE (cyh)

This European Standard specifies the Application Layer Core which provides communication tools for applications
based on DSRC. These tools consist of Kernels that can be used by application processes via service primitives.
The application processes, including application data and application specific functions, are outside the scope of
this European Standard.
The standard is named 'Application Layer' although
- it does not cover all functionality of OSI Layer 7 and
- it includes functionality from lower layers.
This European Standard uses services provided by DSRC Data Link Layer, [EN 12795], and covers functionality of
intermediate layers of the OSI Basic Reference Model [EN ISO/IEC 7498-1].
Figure 1 illustrates the global data flow between the parts of the DSRC stack (Physical, Data Link and Application
Layers) and the application.
The following subjects are covered by this European Standard:
- application Layer structure and framework;
- services to enable data transfer and remote operations;
- application multiplexing procedure;
- fragmentation procedure;
- concatenation and Chaining procedures;
- common encoding rules to translate data from abstract syntax ASN.1, [ISO/IEC 8824-1], into transfer syntax,
[ISO/IEC 8825-2], and vice versa;
- communication initialisation and release procedures;
- broadcast service support;
- DSRC management support including communication profile handling.
It is outside the scope of this European Standard to define a security policy. Some transport mechanisms for
security related data are provided.
NOTE During the lifetime of ENV 12834:1997, no implementation of the Broadcast Pool functionality has become known.
Broadcast Pool functionality is therefore considered untested and is kept in this European Standard for compatibility with the
ENV only.

This European Standard:
-   defines the Data Link Layer of DSRC;
-   is positioned with respect to other related standards by the layers defined in OSI Basic Reference Model [EN ISO/IEC 7498-1] as adopted for DSRC;
-   supports broadcast and half-duplex transmission modes;
-   supports a variety of fixed equipment configurations. It supports configurations where one fixed equipment communicates with one mobile equipment unit, as well as configurations where one fixed equipment can communicate with several mobile equipment units;
-   takes into account that the mobile equipment communicates with the fixed equipment while passing through a limited communication zone;
-   defines neither any specific configuration nor the layout of the communication zone;
-   does not define to what extent different instances of fixed equipment, operating in the vicinity of each other, need to be synchronised with each other;
-   defines parameters to be used in negotiation procedures taking place between fixed equipment and mobile equipment.
By defining two distinct sublayers, namely the medium access control sublayer and the logical link control sublayer, this standard defines:
a)   medium access control procedures for the shared physical medium;
b)   addressing rules and conventions;
c)   data flow control procedures;
d)   acknowledgement procedures;
e)   error control procedures;
f)   services provided to application layer.
The MAC sublayer is specific to the DSRC. The LLC services offered are unacknowledged and acknowledged connectionless services based on [ISO/IEC 8802-2].

This European Standard:
-   defines the Data Link Layer of DSRC;
-   is positioned with respect to other related standards by the layers defined in OSI Basic Reference Model [EN ISO/IEC 7498-1] as adopted for DSRC;
-   supports broadcast and half-duplex transmission modes;
-   supports a variety of fixed equipment configurations. It supports configurations where one fixed equipment communicates with one mobile equipment unit, as well as configurations where one fixed equipment can communicate with several mobile equipment units;
-   takes into account that the mobile equipment communicates with the fixed equipment while passing through a limited communication zone;
-   defines neither any specific configuration nor the layout of the communication zone;
-   does not define to what extent different instances of fixed equipment, operating in the vicinity of each other, need to be synchronised with each other;
-   defines parameters to be used in negotiation procedures taking place between fixed equipment and mobile equipment.
By defining two distinct sublayers, namely the medium access control sublayer and the logical link control sublayer, this standard defines:
a)   medium access control procedures for the shared physical medium;
b)   addressing rules and conventions;
c)   data flow control procedures;
d)   acknowledgement procedures;
e)   error control procedures;
f)   services provided to application layer.
The MAC sublayer is specific to the DSRC. The LLC services offered are unacknowledged and acknowledged connectionless services based on [ISO/IEC 8802-2].

This part of ISO/TS 14907 specifies the test procedures of EFC roadside equipment (RSE) and on-board equipment (OBE) with regard to the conformance to standards and requirements for type approval and acceptance testing which is within the realm of EFC application specifically.
The scope of this part of ISO/TS 14907 is restricted to systems operating within the radio emission,
electromagnetic compatibility (EMC) regulations, traffic, and other regulations of the countries in
which they are operated.
This part of ISO/TS 14907 identifies a set of suitable parameters and provides test procedures to enable the proof of a complete EFC system, as well as components of an EFC system, e.g. OBE, related to the defined requirements of an application. The defined parameter and tests are assigned to the following groups of parameters:
— functionality;
— quality;
— referenced pre-tests.
An overview of the tests and parameters provided by this part of ISO/TS 14907 is given in 5.1 and 5.2.
This part of ISO/TS 14907 describes procedures, methods and tools, and a test plan which shows the relation between all tests and the sequence of these tests. It lists all tests that are required to measure the performance of EFC equipment. It describes which EFC equipment is covered by the test procedures; the values of the parameters to be tested are not included. It also describes how the tests are to be performed and which tools and prerequisites are necessary before this series of tests can be undertaken. It is assumed that the security of the system is inherent in the communications and EFC functionality tests, therefore they are not addressed here. All tests in this part of ISO/TS 14907 provide instructions to evaluate the test results.
The test procedures can be used for prototype testing, type approvals, test of installations, and periodic inspections. Thus this part of ISO/TS 14907 defines only the test and test procedures, not the benchmark figures that these are to be measured against.
Related to a conceptual model of an EFC system, this part of ISO/TS 14907 relates only to the equipment of the user and the service provider as illustrated in Figure 1. Any other entities are outside the scope of this part of ISO/TS 14907.
EFC systems for DSRC consist, in principle, of a group of technical components, which in combination fulfil the functions required for the collection of fees by electronic automatic means. These components comprise of all, or most, of the following:
— OBE within a vehicle;
— OBE containing the communications and computing sub-functions;
— optional integrated circuit card which may carry electronic money, service rights, and othe r
secured information;
— communication between OBE and RSE based on DSRC;
— equipment for the fee collection at the RSE containing the communications and computing subfunctions;
— equipment for the enforcement at the roadside;
— central equipment for the administration and operation of the system.
The scope of this part of ISO/TS 14907 relates solely to OBE and RSE and the DSRC interface between OBE and RSE including its functions to perform the fee collection as illustrated by Figure 2. All the equipment used for enforcement (e.g. detection, classification, localization, and registration) and central equipment are outside the scope of this part of ISO/TS 14907.

1.1 Amplification: The ALERT Plus function is an extension of the ALERT C function. While ALERT C covers event-orientated information to be conveyed by the RDS medium, ALERT Plus deals with status-orientated information to be conveyed by the same medium. The ALERT Plus function informs motorists about the changes affecting the status of traffic at pre-defined locations.

ISO corrigendum.

ISO 14906:2011 specifies the application interface in the context of electronic fee collection (EFC) systems using the dedicated short-range communication (DSRC).

ISO corrigendum.

ISO 14906:2011 specifies the application interface in the context of electronic fee collection (EFC) systems using the dedicated short-range communication (DSRC).

This part of ISO/TS 17575 defines how to convey all or parts of the data element structure defined in ISO/TS 17575-1 over any communication stack and media suitable for this application. It is focussed on mobile communication links. However, wired links shall use the same methodology. To establish a link to a sequence of service calls initializing the communication channel, addressing the reception of the message and forwarding the payload are required. The required communication medium independent services are part of the definition of this part of ISO/TS 17575, represented by an abstract API. The communication interface shall be implemented as an API in the programming environment of choice for the Front End (FE) system. The definition of this API in concrete terms is outside of the scope of this part of ISO/TS 17575. This part of ISO/TS 17575 specifies an abstract API that defines the semantics of the concrete API. An example concrete API is presented in Annex C. Where no distinction is made between the abstract and concrete communications APIs, the term “communications API” or just “API”, can be used.

This part of ISO/TS 17575 defines how to convey all or parts of the data element structure defined in ISO/TS 17575-1 over any communication stack and media suitable for this application. It is focussed on mobile communication links. However, wired links shall use the same methodology. To establish a link to a sequence of service calls initializing the communication channel, addressing the reception of the message and forwarding the payload are required. The required communication medium independent services are part of the definition of this part of ISO/TS 17575, represented by an abstract API. The communication interface shall be implemented as an API in the programming environment of choice for the Front End (FE) system. The definition of this API in concrete terms is outside of the scope of this part of ISO/TS 17575. This part of ISO/TS 17575 specifies an abstract API that defines the semantics of the concrete API. An example concrete API is presented in Annex C. Where no distinction is made between the abstract and concrete communications APIs, the term “communications API” or just “API”, can be used.

ISO/TS 14907-1:2015 specifies the test procedures of EFC roadside equipment (RSE) and on-board equipment (OBE) with regard to the conformance to standards and requirements for type approval and acceptance testing which is within the realm of EFC application specifically.
ISO/TS 14907-1:2015 is restricted to systems operating within the radio emission, electromagnetic compatibility (EMC) regulations, traffic, and other regulations of the countries in which they are operated.
ISO/TS 14907-1:2015 identifies a set of suitable parameters and provides test procedures to enable the proof of a complete EFC system, as well as components of an EFC system, e.g. OBE, related to the defined requirements of an application. The defined parameter and tests are assigned to the following groups of parameters:
? functionality;
? quality;
? referenced pre-tests.
An overview of the tests and parameters provided by this part of ISO/TS 14907 is given in 5.1 and 5.2.
ISO/TS 14907-1:2015 describes procedures, methods and tools, and a test plan which shows the relation between all tests and the sequence of these tests. It lists all tests that are required to measure the performance of EFC equipment. It describes which EFC equipment is covered by the test procedures; the values of the parameters to be tested are not included. It also describes how the tests are to be performed and which tools and prerequisites are necessary before this series of tests can be undertaken. It is assumed that the security of the system is inherent in the communications and EFC functionality tests, therefore they are not addressed here. All tests in this part of ISO/TS 14907 provide instructions to evaluate the test results.

This part of ISO/TS 17575 defines how to convey all or parts of the data element structure defined in ISO/TS 17575-1 over any communication stack and media suitable for this application. It is focussed on mobile communication links. However, wired links shall use the same methodology. To establish a link to a sequence of service calls initializing the communication channel, addressing the reception of the message and forwarding the payload are required. The required communication medium independent services are part of the definition of this part of ISO/TS 17575, represented by an abstract API. The communication interface shall be implemented as an API in the programming environment of choice for the Front End (FE) system. The definition of this API in concrete terms is outside of the scope of this part of ISO/TS 17575. This part of ISO/TS 17575 specifies an abstract API that defines the semantics of the concrete API. An example concrete API is presented in Annex C. Where no distinction is made between the abstract and concrete communications APIs, the term “communications API” or just “API”, can be used.

ISO/TS 14907-1:2010 specifies the test procedures of EFC road-side equipment (RSE) and on-board equipment (OBE) with regard to the conformance to standards and requirements for type approval and acceptance testing which is within the realm of EFC application specifically.
ISO/TS 14907-1:2010 is restricted to systems operating within the radio emission, EMC regulations, traffic and other regulations of the countries in which they are operated and it is therefore a requirement that all required equipment approvals from an authenticated and accredited test house have been obtained in order to claim compliance.
ISO/TS 14907-1:2010 identifies a set of suitable parameter and provides test procedures to enable the proof of a complete EFC-system as well as components of an EFC-system e.g. OBE related to the defined requirements of an application. The defined parameter and tests are assigned to the following groups of parameters:
— functionality;
— quality;
— referenced pre-tests.
ISO/TS 14907-1:2010 describes procedures, methods and tools, and a test plan which shows the relation between all tests and the sequence of these tests. It lists all tests that are required to measure the performance of EFC equipment. It describes which EFC-equipment is covered by the test procedures; the values of the parameters to be tested are not included. It also describes how the tests are to be performed, and which tools and pre-requisites are necessary before this series of tests can be undertaken. It is assumed that the security of the system is inherent in the communications and EFC functionality tests, therefore they are not addressed here. All tests in ISO/TS 14907-1:2010 provide instructions to evaluate the test results.
The test procedures can be used for prototype testing, type approvals, test of installations and periodic inspections. ISO/TS 14907-1:2010 defines only the test and test procedures, not the benchmark figures that these are to be measured against.
EFC-systems for DSRC consist, in principle, of a group of technical components, which in combination fulfil the functions required for the collection of fees by electronic automatic means. These components comprise all, or most of, the following:
— on-board equipment (OBE) within a vehicle;
— on-board unit containing the communications and computing sub-functions;
— optional integrated circuit card which may carry electronic money, service rights and other secured information;
— communication between OBE and RSE based on DSRC;
— equipment for the fee collection at the road-side (RSE) containing the communications and computing sub-functions;
— equipment for the enforcement at the road-side;
— central equipment for the administration and operation of the system.
ISO/TS 14907-1:2010 relates solely to OBE and RSE and the DSRC interface between OBE and RSE including its functions to perform the fee collection. All the equipment used for enforcement (e.g. detection, classification, localization and registration) and central equipment are outside the scope of ISO/TS 14907-1:2010.

This Technical Specification specifies a system architecture for electronic fee collection (EFC) systems concerning vehicle related transport services such as the use of toll roads, zone access, parking and route guidance.
This Technical Specification does not cover person related transport services such as public transport. However, some of the clauses in this standard may also be applicable for fare collection.
NOTE   Fare collection architecture in public transport is covered by other Working Groups in CEN/TC278 and ISO/TC204, e.g. WG3 Public Transport in CEN/TC278.
This Technical Specification provides the overview of, and inter-relationship among, the set of standards for design, development, testing and operation of applications in the field of EFC.
This Technical Specification is also applicable to the TICS Fundamental Service called Electronic Financial Transactions which is the use of electronic, or 'cashless' payment systems for transportation. Hence, this standard covers toll collection systems, parking fee collection systems, systems for road and congestion pricing and integrated payment systems for transport services.

Migrated from Progress Sheet (TC Comment) (2000-07-10): WIs 129-136 are the result of the splitting of WI 025 (TC Res C 1/2000) (CC/000607).
!!! Resolution BT 19/2002: Finalization of prENV ISO 14821-5 as CEN/TS 14821-5 by CMC under CA7 in English only and submission to the new translation procedure (NT/021014) !!!

Migrated from Progress Sheet (TC Comment) (2000-07-10): WIs 129-136 are the result of the splitting of WI 025 (TC Res C 1/2000) (CC/000607).
!!! Resolution BT 19/2002: Finalization of prENV ISO 14821-6 as CEN/TS 14821-6 by CMC under CA7 in English only and submission to the new translation procedure (NT/021014) !!!

This pre-Standard provides a common message structure for Traffic and Traveller Information messages which are disseminated via dedicated beacon infrastructure (for short-range communications, only).

Migrated from Progress Sheet (TC Comment) (2000-07-10): WIs 129-136 are the result of the splitting of WI 025 (TC Res C 1/2000) (CC/000607).
!!! Resolution BT 19/2002: Finalization of prENV ISO 14821-8 as CEN/TS 14821-8 by CMC under CA7 in English only and submission to the new translation procedure (NT/021014) !!!

Migrated from Progress Sheet (TC Comment) (2000-07-10): WIs 129-136 are the result of the splitting of WI 025 (TC Res C 1/2000) (CC/000607).
!!! Resolution BT 19/2002: Finalization of prENV ISO 14821-1 as CEN/TS 14821-1 by CMC under CA7 in English only and submitted to the new translation procedure (NT/021014) !!!

Migrated from Progress Sheet (TC Comment) (2000-07-10): WIs 129-136 are the result of the splitting of WI 025 (TC Res C 1/2000) CC/000607).
!!! Resolution BT 19/2002: Finalization of prENV ISO 14821-2 as CEN/TS 14821-2 by CMC under CA7 in English only and submission to the new translation procedure (NT/021014) !!!

Migrated from Progress Sheet (TC Comment) (2000-07-10): WIs 129-136 are the result of the splitting of WI 025 (TC Res C 1/2000) (CC/000607).
!!! Resolution BT 19/2002: Finalization of prENV ISO 14821-7 as CEN/TS 14821-7 by CMC under CA7 in English only and submission to the new translation procedure (NT/021014) !!!

A Centrally Determined Route Guidance (CDRG) system using Dedicated Short Range Communication (DSRC) is based on infrastructure and equipped vehicles. The Route Guidance Information (RGI) is generated by a Central Office (CO) and distributed via DSRC to the equipped vehicles. To enable dynamic RGI the Central Office needs real time traffic flow data. This data is provided through the system itself using vehicles as probes.

Migrated from Progress Sheet (TC Comment) (2000-07-10): WIs 129-136 are the result of the splitting of WI 025 (TC Res C 1/2000) (CC/000607).
!!! Resolution BT 19/2002: Finalization of prENV ISO 14821-3 as CEN/TS 14821-3 by CMC under CA7 in English only and submission to the new translation procedure (NT/021014) !!!

Migrated from Progress Sheet (TC Comment) (2000-07-10): WIs 129-136 are the result of the splitting of WI 025 (TC Res C 1/2000) (CC/000607).
!!! Resolution BT 19/2002: Finalization of prENV ISO 14821-4 as CEN/TS 14821-4 by CMC under CA7 in English only and submission to the new translation procedure (NT/021014) !!!

This CEN/TS defines the specific interfaces and functionality of traffic telematics (TT) services based on the use of cellular networks. Device manufacturers are enabled to develop terminal equipment compatible to services based on this CEN/TS. This will allow for interoperability of different terminal equipment and service providers which allows competition between service providers and terminal manufacturers. Furthermore it sets the scene for international availability of these services.
This CEN/TS specifies
-   TT-specific interfaces between terminal and service centre. This especially incorporates the message sets of the application data protocols and the service-independent communication handling (including conditional access and transport protocols).
-   Functionality, procedures and requirements of basic terminal components as well as their interaction with the service centre. This especially comprises conditional access and security mechanisms.
-   Service Specifications, which are essential to ensure consistent behaviour of terminal and service centre.
The services incorporated within this issue comprise:
-   breakdown and emergency services
-   interactive traffic information services
-   broadcast traffic information services
-   navigation services (route assistance, route advice, homing)
-   operator services
-   general information services
-   floating car data collection
It is envisaged that future research and development will lead to improvements on the services listed above as well as to the creation of new services. Nevertheless this CEN/TS provides the framework for seamless integration of new features and services into the existing architecture.

This Technical Specification  defines the specific interfaces and functionality of traffic telematics (TT) services based on the use of cellular networks. Device manufacturers are enabled to develop terminal equipment compatible to services based on this Technical Specification. This will allow for interoperability of different terminal equipment and service providers which allows competition between service providers and terminal manufacturers. Furthermore it sets the scene for international availability of these services.
This Technical Specification  specifies
-   TT-specific interfaces between terminal and service centre. This especially incorporates the message sets of the application data protocols and the service-independent communication handling (including conditional access and transport protocols).
-   Functionality, procedures and requirements of basic terminal components as well as their interaction with the service centre. This especially comprises conditional access and security mechanisms.
-   Service Specifications, which are essential to ensure consistent behaviour of terminal and service centre.
The services incorporated within this issue comprise:
-   breakdown and emergency services
-   interactive traffic information services
-   broadcast traffic information services
-   navigation services (route assistance, route advice, homing)
-   operator services
-   general information services
-   floating car data collection
It is envisaged that future research and development will lead to improvements on the services listed above as well as to the creation of new services. Nevertheless this Technical Specification provides the framework for seamless integration of new features and services into the existing architecture.

This CEN/TS defines the specific interfaces and functionality of traffic telematics (TT) services based on the use of cellular networks. Device manufacturers are enabled to develop terminal equipment compatible to services based on this CEN/TS. This will allow for interoperability of different terminal equipment and service providers which allows competition between service providers and terminal manufacturers. Furthermore it sets the scene for international availability of these services.
This CEN/TS specifies
-   TT-specific interfaces between terminal and service centre. This especially incorporates the message sets of the application data protocols and the service-independent communication handling (including conditional access and transport protocols).
-   Functionality, procedures and requirements of basic terminal components as well as their interaction with the service centre. This especially comprises conditional access and security mechanisms.
-   Service Specifications, which are essential to ensure consistent behaviour of terminal and service centre.
The services incorporated within this issue comprise:
-   breakdown and emergency services
-   interactive traffic information services
-   broadcast traffic information services
-   navigation services (route assistance, route advice, homing)
-   operator services
-   general information services
-   floating car data collection
It is envisaged that future research and development will lead to improvements on the services listed above as well as to the creation of new services. Nevertheless this CEN/TS provides the framework for seamless integration of new features and services into the existing architecture.

This Technical Specification defines the specific interfaces and functionality of traffic telematics (TT) services based on the use of cellular networks. Device manufacturers are enabled to develop terminal equipment compatible to services based on this standard. This will allow for interoperability of different terminal equipment and service providers which allows competition between service providers and terminal manufacturers. Furthermore it sets the scene for international availability of these services.
This Technical Specification specifies
-   TT-specific interfaces between terminal and service centre. This especially incorporates the message sets of the application data protocols and the service-independent communication handling (including conditional access and transport protocols).
-   Functionality, procedures and requirements of basic terminal components as well as their interaction with the service centre. This especially comprises conditional access and security mechanisms.
-   Service Specifications, which are essential to ensure consistent behaviour of terminal and service centre.
The services incorporated within this issue comprise:
-   breakdown and emergency services
-   interactive traffic information services
-   broadcast traffic information services
-   navigation services (route assistance, route advice, homing)
-   operator services
-   general information services
-   floating car data collection
It is envisaged that future research and development will lead to improvements on the services listed above as well as to the creation of new services. Nevertheless this Technical Specification provides the framework for seamless integration of new features and services into the existing architecture.

This technical specification defines the specific interfaces and functionality of traffic telematics (TT) services based on the use of cellular networks. Device manufacturers are enabled to develop terminal equipment compatible to services based on this standard. This will allow for interoperability of different terminal equipment and service providers which allows competition between service providers and terminal manufacturers. Furthermore it sets the scene for international availability of these services.
This technical specification specifies
-   TT-specific interfaces between terminal and service centre. This especially incorporates the message sets of the application data protocols and the service-independent communication handling (including conditional access and transport protocols).
-   Functionality, procedures and requirements of basic terminal components as well as their interaction with the service centre. This especially comprises conditional access and security mechanisms.
-   Service Specifications, which are essential to ensure consistent behaviour of terminal and service centre.
The services incorporated within this issue comprise:
-   breakdown and emergency services
-   interactive traffic information services
-   broadcast traffic information services
-   navigation services (route assistance, route advice, homing)
-   operator services
-   general information services
-   floating car data collection
It is envisaged that future research and development will lead to improvements on the services listed above as well as to the creation of new services. Nevertheless this technical specification provides the framework for seamless integration of new features and services into the existing architecture.

This CEN/TS defines the specific interfaces and functionality of traffic telematics (TT) services based on the use of cellular networks. Device manufacturers are enabled to develop terminal equipment compatible to services based on this technical specification. This will allow for interoperability of different terminal equipment and service providers which allows competition between service providers and terminal manufacturers. Furthermore it sets the scene for international availability of these services.
This technical specification specifies
-   TT-specific interfaces between terminal and service centre. This especially incorporates the message sets of the application data protocols and the service-independent communication handling (including conditional access and transport protocols).
-   Functionality, procedures and requirements of basic terminal components as well as their interaction with the service centre. This especially comprises conditional access and security mechanisms.
-   Service Specifications, which are essential to ensure consistent behaviour of terminal and service centre.
The services incorporated within this issue comprise:
-   breakdown and emergency services
-   interactive traffic information services
-   broadcast traffic information services
-   navigation services (route assistance, route advice, homing)
-   operator services
-   general information services
-   floating car data collection
It is envisaged that future research and development will lead to improvements on the services listed above as well as to the creation of new services. Nevertheless this technical specification provides the framework for seamless integration of new features and services into the existing architecture.

This  Technical Specification  defines the specific interfaces and functionality of traffic telematics (TT) services based on the use of cellular networks. Device manufacturers are enabled to develop terminal equipment compatible to services based on this Technical Specification. This will allow for interoperability of different terminal equipment and service providers which allows competition between service providers and terminal manufacturers. Furthermore it sets the scene for international availability of these services.
This Technical Specification  specifies
-   TT-specific interfaces between terminal and service centre. This especially incorporates the message sets of the application data protocols and the service-independent communication handling (including conditional access and transport protocols).
-   Functionality, procedures and requirements of basic terminal components as well as their interaction with the service centre. This especially comprises conditional access and security mechanisms.
-   Service Specifications, which are essential to ensure consistent behaviour of terminal and service centre.
The services incorporated within this issue comprise:
-   breakdown and emergency services
-   interactive traffic information services
-   broadcast traffic information services
-   navigation services (route assistance, route advice, homing)
-   operator services
-   general information services
-   floating car data collection
It is envisaged that future research and development will lead to improvements on the services listed above as well as to the creation of new services. Nevertheless this Technical Specification provides the framework for seamless integration of new features and services into the existing architecture.

This CEN/TS defines the specific interfaces and functionality of traffic telematics (TT) services based on the use of cellular networks. Device manufacturers are enabled to develop terminal equipment compatible to services based on this CEN/TS. This will allow for interoperability of different terminal equipment and service providers which allows competition between service providers and terminal manufacturers. Furthermore it sets the scene for international availability of these services.
This CEN/TS specifies
•   TT-specific interfaces between terminal and service centre. This especially incorporates the message sets of the application data protocols and the service-independent communication handling (including conditional access and transport protocols).
•   Functionality, procedures and requirements of basic terminal components as well as their interaction with the service centre. This especially comprises conditional access and security mechanisms.
•   Service Specifications, which are essential to ensure consistent behaviour of terminal and service centre.
The services incorporated within this issue comprise:
•   breakdown and emergency services
•   interactive traffic information services
•   broadcast traffic information services
•   navigation services (route assistance, route advice, homing)
•   operator services
•   general information services
•   floating car data collection
It is envisaged that future research and development will lead to improvements on the services listed above as well as to the creation of new services. Nevertheless this CEN/TS provides the framework for seamless integration of new features and services into the existing architecture.

This pre-Standard provides a common message structure for Traffic and Traveller Information messages which are disseminated via dedicated beacon infrastructure (for short-range communications, only).

A Centrally Determined Route Guidance (CDRG) system using Dedicated Short Range Communication (DSRC) is based on infrastructure and equipped vehicles. The Route Guidance Information (RGI) is generated by a Central Office (CO) and distributed via DSRC to the equipped vehicles. To enable dynamic RGI the Central Office needs real time traffic flow data. This data is provided through the system itself using vehicles as probes.

This standard primarily addresses the needs of RDS-TMC ALERT-C messages, which are already being implemented. However, the modular approach used here is intended to facilitate future extension of the location referencing rules to other traffic and travel messaging systems.
The location referencing rules defined in this standard address the specific requirements of Traffic Message Channel (TMC) systems, which use abbreviated coding formats to provide TTI messages over mobile bearers (e.g. GSM, DAB) or via exchange protocols like DATEX. In particular, the rules address the Radio Data System - Traffic Message Channel (RDS-TMC), a means of providing digitally-coded traffic and travel information to travellers using a silent data channel (RDS) on FM radio stations, based on the ALERT-C protocol.

ISO 14819-3:2004 primarily addresses the needs of RDS-TMC ALERT-C messages, which are already being implemented. However, the modular approach used here is intended to facilitate future extension of the location referencing rules to other traffic and travel messaging systems.
The location referencing rules defined in ISO 14819-3:2004 address the specific requirements of Traffic Message Channel (TMC) systems, which use abbreviated coding formats to provide TTI messages over mobile bearers (e.g. GSM, DAB) or via exchange protocols like DATEX. In particular, the rules address the Radio Data System-Traffic Message Channel (RDS-TMC), a means of providing digitally-coded traffic and travel information to travellers using a silent data channel (RDS) on FM radio stations, based on the ALERT-C protocol.