Cooperative intelligent transport systems (C-ITS)
Cooperative Connected Automated Mobility (CCAM)
Evaluation of standards
Edition 17. April 2024
Note: This web is under construction to add CCAM details to a previous web on C-ITS.
Reload this content in a separate window.
This online guide provides an evaulation of selected SDO deliverables for CCAM and C-ITS. It is the result of many years of standardization and research activities of Dr. Hans-Joachim Fischer at ESF GmbH (until end 2021) and at Engineering Services Fischer.
It serves as a guide for standard developers, system designers, and for deployment.
References to a large choice of standards for are given.
For details on standards you may consult:
This web will continuously be updated to reflect latest developments in standardization and deployment.
Content
1 C-ITS and CCAM - An introduction
2.1 General
2.2 Goals of standardisation
2.3 Releases
2.4 SDOs2.4.1 Overview
2.4.2 Major advocates of ITS
2.4.3 Further advocates active in C-ITS
2.4.4 Secondary SDOs2.5 Standardisation areas
2.6 Categories of SDO deliverables
3 Selected standards for C-ITS
3.1 General
3.2 Overall high-level system architecture and related entities3.2.1 EN 17419 – Globally unique identification
3.2.2 TS 102 940 - Security architecture
3.2.3 ISO 17427-1 – Roles and responsibilities3.3.1 ISO 21217 – Station and communication architecture
3.3.2 ISO 20026 – C-ITS test architecture
3.3.3 EG 202 798 - Framework for conformance and interoperability testing3.4 ITS applications, message sets, messages, data
3.4.1 TR 102 638 - Basic set of applications
3.4.2 TS 102 637-1 - Functional requirements for BSA
3.4.3 ISO 22837 – Reference architecture for probe vehicle systems and data
3.4.4 ISO 25114 – Framework for probe data reporting management
3.4.5 ISO 29284 - Event based probe vehicle data
3.4.6 TS 101 539-1 - Road Hazard Signalling (RHS)
3.4.7 TS 101 539-2 - Intersection collision risk warning
3.4.8 TS 101 539-3 - Longitudinal collision risk warning
3.4.9 ISO 14816 - Numbering and data structure for AVI
3.4.10 ITS 102 894-2 – ETSI common data dictionary
3.4.11 ISO 14906 - Vehicle-related data
3.4.12 EN 16157-1 – DATEX II context and framework
3.4.13 EN 16157-7 DATEX II common data elements3.5.1 ISO 17423 - Application requirements and objectives
3.5.2 ISO 24102-6 – Path and flow management
3.5.3 ISO 24102-1 – Local station management
3.5.4 ISO 24102-2 – Remote station management
3.5.5 ISO 24102-4 - Station-internal management communication
3.5.6 ISO 24102-7 - ITS-S capabilities
3.5.7 ISO 24102-8 - ITS-S application processes
3.5.8 ISO 24102-9 - ITS-S managed entities
3.5.9 ISO 24102-3 - Service access points
3.5.10 TS 102 687- Access layer decentralized congestion control mechanisms
3.5.11 TS 102 792 – DSRC mitigation techniques
3.5.12 TS 103 157 – Cross layer DCC management3.6 Security
3.6.1 TS 102 731 – Security services and architecture
3.6.2 TS 102 941 – Trust and privacy management
3.6.3 TS 102 942 – Access control
3.6.4 TS 102 943 – Confidentiality services
3.6.5 TS 103 097 Security header and certificate formats
3.6.6 IEEE Std. 1609.2 - Security services for applications and management messages
3.6.7 ISO 21177 - Secure sessions with ITS station units3.7.1 ISO 21215 – ITS-M5
3.7.2 ISO 21218 - Access technology support
3.7.3 EN 302 663 – ITS-G5
3.7.4 TS 102 724 - Harmonized channels in the 5 GHz frequency band
3.7.5 IEEE Std. 802.11 - Wireless LAN
3.7.6 EN 301 893 – RLAN essential requirements of article 3.2 of Directive 2014/53/EU
3.7.7 EN 302 571 – C-ITS essential requirements of article 3.2 of Directive 2014/53/EU
3.7.8 ISO 17515-1 – LTE access to Internet3.8 Networking and transport technologies
3.8.1 ISO 29281-1 – Fast networking & transport protocol (FNTP)
3.8.2 ISO 21210 – IPv6 networking for ITS
3.8.3 EN 302 636-4-1 – GeoNetworking – media-independent functionality
3.8.4 TS 302 636-4-2 – GeoNetworking – media-dependent functionality for ITS-G5
3.8.5 EN 302 636-5-1 – Basic transport protocol for GeoNetworking
3.8.6 EN 302 636-6-1 – IPv6 over GeoNetworking
3.8.7 EN 302 931 - Geometrical shapes
3.8.8 TS 103 248 – Port numbers for BTP
3.8.9 ISO 16460 – Harmonized messaging format3.9.1 ISO 19091 – Intersection management SPaT / MAP / SRM / SSM
3.9.2 ISO 19321 – In-vehicle information
3.9.3 ISO 16460 – Harmonized messages for service announcement
3.9.4 ISO 17429 – Generic facilities CPH, CSH, FSH
3.9.5 ISO 18750 - Local dynamic map
3.9.6 ISO 21176 – Position, velocity, time in an ITS-SU
3.9.7 ISO 22418 – Fast service announcement protocol
3.9.8 EN 302 637-2 - Cooperative awareness message
3.9.9 EN 302 637-3 – Decentralized environmental notification message
3.9.10 ISO 21184 – Global transport data management framework
3.9.11 ETSI TS 102 894-1 – Facilities layer structure and functional requirements
3.9.12 ETSI TS 103 301 – Facilities layer requirements for infrastructure services
3.9.13 ITS 17425 - In-vehicle presentation of external road and traffic related data
3.9.14 ITS 17426 - Contextual speeds
3.9.15 EN 16157-2 – DATEX II location referencing
3.9.16 EN 16157-3 – DATEX II situation publication3.10 Protocol stack
3.10.1 CEN TS 17496 – Communication profiles
3.10.2 CEN TS 17182 – eCall in an ITS-SU
3.10.3 SAE J2945/1 – On-board system requirements for V2V safety communications
CCAM is the "political" straight forward continuation of C-ITS. From a technical point of view, CCAM focuses on technical details related to automated driving which complement the C-ITS technical features.
Cooperative Intelligent Transport Systems" (C-ITS) is a subset of standards for "Intelligent Transport Systems" (ITS).
ITS aims on improving surface transportation in respect of
by applying information and communication technologies (ICT).
ITS specifications are in general developed to address a specific ITS service domain such as public transport, road safety, freight and logistics, public emergency, electronic fee collection.
To support interoperability, C-ITS specifications are developed to exchange and share information ITS applications of a given application domain, and even between application domains.
C-ITS services are based on the exchange of data between vehicles of any category (cars, trucks, buses, emergency and specialized vehicles, ...), the roadside and urban infrastructure (traffic lights, road tolls, variable message signs, ...), control and services centres in the cloud (traffic control centre, service providers, map providers, …), and other road users (pedestrians, cyclists, …).
Some ITS services require cooperation by vehicles with their surrounding environment (other vehicles, other road users, roadside and urban infrastructure, …) while other ITS services require connectivity to remote service platforms (road traffic control centres, map providers, service providers, fleet managers, equipment manufacturers, …).
To support
it is necessary to combine multiple access technologies and communication protocols with distinct performance characteristics (communication range, available bandwidth, end-to-end transmission delay, quality of service, security, ...).
Combining multiple access technologies and communication protocols requires a common approach to the way communications and data are managed in a secure way. A functional architecture (“the ITS station architecture”) is thus specified to manage security, communications and data related to C-ITS services.
The ITS station architecture is specified in ISO 21217, see Figure 1, and details of functional building blocks of the ITS station architecture are specified in a set of related standards.
Figure 1 — ITS station architecture with some details (from ISO 21217])
Similar to the ISO Open Systems Interconnection (OSI) 7-layer architecture, the ITS station architecture is designed into three independent communication layers (namely the ITS station access layer, the ITS station networking & transport layer, and the ITS station facilities layer) on top of which the ITS Applications entity is located. Additional cross-layer entities in charge of the management activities (management of ITS station units, communications and security) are supporting communications and applications.
An implementation of this ITS station architecture is referred to as "ITS Station Unit) (ITS-SUs); see ISO 21217. The functionalities available in an ITS station unit can be implemented in one or multiple physical units referred to as "ITS Station Communication Units" (ITS-SCUs); even such that the various ITS-SCUs of one ITS-SU are split over a large geographical area, e.g. along a motorway with several 10kms length.
ITS-SUs compliant with ISO 21217 can be deployed in various environments, including vehicles of any kind (vehicle ITS station), on the roadside infrastructure (roadside ITS station), in the cloud (central ITS station) or in nomadic devices (personal ITS station), as illustrated in Figure 2.
Figure 2 — Peer-to-peer communications between ITS station units
As C-ITS deals with safety of human life and property, ITS station units are designed for supporting secure provision of the C-ITS services and secure allocation of resources with prioritized access. Security means cover the two essential operational modesand station-internal controlled access to data and station functionalities, e.g. authentication (who is allowed to do what, or who is allowed to access which data and how <read / write / delete>?) and prioritization (who is served first?).
NOTE ISO 21217 introduced the reference name "Bounded Secured Managed Entity" (BSME) of the ITS station unit to indicate these and further security features.
NOTE There can be station units for ITS in general, and particularly for C-ITS, that are not conformant with ISO 21217 and the set of related standards from ISO in a strict sense. However, in order to ensure secure communications with ITS-SUs, as a minimum, security means are applied that are conformant with respective security standards.
Due to the diverging requirements from the multiplicity of already known and continuously emerging ITS applications, multiple communication technologies that are fundamentally different can be supported in a specific ITS station unit. Supporting multiple access technologies and communication protocols, also referred to as “hybrid communications”, is a design principle of the ITS station architecture. The ITS station architecture is thus specified with no pre-defined mandatory communication technologies. It can support any type of existing and forthcoming technology to the conditions that
Presently, specifications have been developed to support a number of access technologies, e.g.:
and several flavours of communication protocol suites:
The ITS station architecture actually combines
NOTE Whilst networked communications, e.g. cellular communications and access to Internet, can apply the principle of "Technology Neutrality" (allowing simultaneous usage of a mix of incompatible technologies), localized communication between ITS station units has to be based on a specific access technology per service (or service domain) in order to enable interoperability.
EXAMPLE ITS-M5 (ISO 21215) with FNTP (ISO 29281-1) is an example of a protocol stack for localized communications. Cellular network access to Internet (ISO 17515-1) with IPv6 (ISO 21210) is an example of a protocol stack for networked communications.
Unlike many legacy applications, the choice of the access technology and communication protocol can be made transparent to the applications, i.e. ITS applications are technology-agnostic. This is achieved through a number of functionalities across the ITS station architecture in support of hybrid communications, and is illustrated in Figure 3.
Figure 3 — Path and flow management for technology-agnostic ITS applications
Before transmitting data, applications provide their communication requirements (level of priority, amount of data to be transmitted, expected level of security, expected end-to-end transmission delay, …) to the management entity of the ITS station unit for each type of communication flow. In the meantime, the management entity maintains various information (local regulation enforcing the use of a specific communication profile, existing capabilities of the ITS station unit and their status, characteristics and load of available radio technologies, current load of the ITS station unit, …). Based on the communication requirement and the current view of the management, the uppermost relevant communication profile is selected and ITS station resources are securely committed for identified communication flow.
Standardization activities
C-ITS standards are developed by "Technical Committees" (TCs) of "Standard Development Organizations" (SDOs) dedicated to ITS, e.g.
Particularly relevant standardization activities are conducted within
While all of these groups are developing around the same ITS station architecture, each group has a specific focus.
Supported access technologies and communication protocols are mostly developed within ISO/TC 204/WG 16 and ETSI TC ITS WG3 and WG4. Generic facilities (generic messaging, PVT, global LDM, …) and infrastructure-centric messaging (SPaT / MAP / IVI, …) are developed in ISO/TC 204/WG 18 jointly with CEN/TC 278/WG 16. ETSI TC ITS WG1 is developing vehicle-centric localized messages (CAM, DENM, …) and other vehicle-centric facilities (vehicle-LDM, POTI).
ISO/TC 204, CEN/TC 278 and ETSI TC ITS are also developing standards using building blocks developed by other organizations. For instance,
Pilot deployments of C-ITS services
ISO, CEN and ETSI specifications related to C-ITS have been developed with the strong support of the European Commission since 2006, following its ITS Directive on the framework for the deployment of Intelligent Transport Systems in the field of road transport and for interfaces with other modes of transport, and its 6th and 7th framework research programmes (FP6 / FP7). From 2006 to 2012, the standardization activities at ISO was fuelled by collaborative projects (CVIS, SafeSpot, Coopers, COMeSafety, SeVeCom, Anemone, GeoNet, FOTsis, DriveC2X and ITSSv6) which provided work force and developed proof of concepts and prototypes, in particular CVIS. From 2010 to 2013 the standardization activities were further supported by the Standardization Mandate M/453 given to CEN/TC 278 and ETSI TC ITS to develop C-ITS standards in support of the ITS Directive. A subsequent support was given by the Standardization Mandate M/546 on Urban ITS given to CEN/TC 278.
In the meantime, various national efforts have also been initiated, for instance SCOREF in France and CONVERGE in Germany.
The ITS station architecture serves as a reference for numerous C-ITS services developed around the world, and more particularly in Europe. Early deployments of C-ITS services complying with the ITS station architecture have been initiated in Europe under the framework of the C-ROADS and InterCor initiatives supported by the European Commission. National pilot deployments are underway all across Europe (SCOOP in France, NordicWay in Scandinavia, the C-ITS corridor project between The Netherlands, Germany, and Austria) and in other regions such as Austroads in Australia and New Zealand, and in Israel. These early deployment projects are typically focused on road safety and traffic efficiency services that rely on the exchange of data between vehicles and the roadside infrastructure. Such data exchange is performed through both localized communications and networked communications.
In these European deployments, localized communications, also known as V2X, are performed using the ITS-G5 access technology within the 5.9 GHz frequency band, a WiFi profile designed for vehicular communications, whereas networked communication are typically made through a cellular technology (e.g. LTE). Other technologies can of course be used in the future (e.g. 5G, infra-red, …) as long as they comply with the ITS station architecture and related standards defining technology building blocks.
Early deployments have evidenced the need to deploy C-ITS services using a diversity of access technologies, for instance either ITS-G5 or LTE, or a combination of both. For instance, the French pilot deployment (SCOOP) is using ITS-G5 between vehicle and roadside ITS stations to inform about immediate dangers (CAM, DENM) and LTE is used by patrol vehicles to provide information to road control centres. In Scandinavia, the scarce population has driven NordicWay to deploy roadside ITS stations only at critical locations and to rely on LTE to deliver environmental information (DENM) from road control centres to vehicles.
Further on, at the early stage of deployment of C-ITS services, the density of vehicle ITS stations equipped with ITS-G5 capabilities is scarce, whereas roadside ITS stations are only deployed in critical areas. Similarly, many areas anywhere in the world do not have the benefit of sufficient cellular network coverage. While some time critical road safety C-ITS services are best served by localized communications (e.g. notification of immediate danger requiring emergency breaking), there are not always vehicles equipped with the ITS-G5 technology or roadside equipment in the vicinity able to relay the notification immediately to nearby vehicles. In such a situation, using networked communications (e.g. cellular) to provide the information to road control centres, and then from them back to vehicles in a specific are prevents the successive occurrence of road accidents.
All these experiences, gained through early deployments, demonstrate that it is not possible to provide the same level of services to all vehicles in all locations. The type of service and the performance of the service depends on national decisions, the local road environment, the density of population, the density of vehicles equipped, cellular coverage, and numerous other factors. In addition, and importantly, the roadside infrastructure equipment and vehicles have a life expectancy that far exceeds the innovation cycle of new radio and communication technologies, therefore equipment at the roadside and in vehicles is likely to have to accommodate new communications technologies during its lifetime.
Enhanced functionalities in the ITS station architecture
Flexible and future-proof management of data and messages is a pre-requisite for success of C-ITS. New messages – even if efficiently defined in ASN.1 and encoded with Unaligned Packed Encoding Rules - can be made available during run-time of C-ITS simply by providing message configuration information. This allows for faster introduction of new or modified services and increases communications efficiency. An approach to achieve this is known under the title "Global Transport Data Management" (GTDM) framework with specifications provided in TS 21184.
Many C-ITS services depend on accurate information on the kinematics status, e.g. location and speed of a station at a given time, of the ITS station units. Thus, a general "Position-Velocity-Time" (PVT) service, as specified in TS 21176, is a pre-requisite for successful deployment of such services. The basic estimation technology used for the PVT service is the technology known under the name of "Global Navigation Satellite System" (GNSS), namely GALILEO from the European Union, GPS from the United States of America, GLONAS from the Russian Federation. However, in addition to this basic technology, a large variety of complementary technologies are known to improve accuracy and reliability of the PTV service.
Hybrid communication support in the ITS station architecture
The ITS station architecture specified in ISO 21217 and its functionalities in support for hybrid communications provides an answer to these concerns and enables a future-proof and sustainable deployment of C-ITS services.
Due to the diverging requirements from the multiplicity of already known and continuously emerging ITS applications, different communication technologies are to be supported in a specific ITS station unit. This need was envisioned from the start of the development of the ITS station architecture ISO 21217 back to 2002 when ISO/TC 204/WG 16 was founded. As the diversity of ITS applications (ranged into three categories: “road safety”, “traffic efficiency” and “comfort”) with diverging communication requirements cannot be met by a single type of access technology and communication protocol, the ITS station architecture was designed to combine multiple access technologies and access protocols.
A first proof of concept of this approach was demonstrated as part of the EU funded CVIS project. In 2015, this need was labelled with the term "Hybrid Communication" in the reports of the German CONVERGE project. As of 2019, the need for hybrid communication solutions is expressed in pilot deployment of C-ITS services, particularly in the context of C-Roads in Europe.
Hybrid communications can basically be defined as the composition of multiple access technologies and protocols with different characteristics combined to provide complementary or redundant communication channels. This can arise in multiple situations:
For deployment of ITS, especially C-ITS and the emerging Urban ITS and "Mobility as a Service" (MaaS) paradigms, consistent and complete sets of standards and profiles of standards including necessary parameterisation are necessary in support of the targeted ITS services to be provided by means of ITS applications. Such sets are referred to as "C-ITS Release". This document presents the C-ITS standards landscape, describes a concept of Releases, and exemplifies this concept with a "C-ITS Release 2".
Standardisation in general is the process of generating specifications by a recognized authority, i.e. an SDO, applying the principle of consensus finding in the working groups of an SDO prior to formal approval by voting according to the rules of the SDOs.
Generating specifications outside of SDOs typically is a faster process of generation specifications than the process of standardisation, as the principle of consensus building amongst a group of stakeholders with typically at least slightly diverging interests and business models does not need to be applied. Consequently, standardisation is a somehow slow process that can result in compromises and standards composed of options, such that these standards cannot be used as "blueprints" for the development and production of interoperable equipment.
Regulatory requirements complement standards and specifications, and have to be considered for deployment of equipment and operation of services in the given regulatory domain.
The purpose of standardisation, in general, is to enable or facilitate services of the respective standardisation domain, i.e. C-ITS services provided by ITS applications for the ITS service domains. Particularly, the purpose of standardisation is manifold, aiming on e.g.:
An introduction to C-ITS services is provided in CEN/TR 21186-1.
In order to reach the standardisation goals listed in 2.2, standards are grouped in so-called "Releases" together with information on profiles and parameters. Profiles identify selected mandatory requirements, and parameter information identifies applicable values such that interoperability between equipment provided by different vendors is ensured.
Releases use dated references to standards. A release supports one or several use cases or services.
Clause 3 presents a non-exhaustive snap-shot of SDO deliverables that are considered to be of certain relevance for ITS, especially for C-ITS but also for the Urban ITS paradigm.
CEN/TR 21186-1 explains an approach towards C-ITS releases and provides examples of releases.
Major standard development organisations (SDOs) working on an international or regional level in the domain of C-ITS are illustrated in Figure 4.
Figure 4 — Major SDOs currently being active in C-ITS
Secondary SDOs are working on general purpose specifications that are usually referenced in ITS standards.
For deployment of ITS, regional legislation is to be considered, e.g. in Europe
The main internationally active advocate of ITS is the Technical Committee TC204 "Intelligent Transport Systems" of the International Standards Organisation (ISO), producing standards related to many service domains of ITS. More than 10 ITS service domains are identified so far in ISO/TC 204. ISO/TC 204 was founded in 1993. Currently the work programme of ISO/TC 204 is being updated.
ISO/TC 204 is organised in Working Groups (WG), and cooperates partly with CEN/TC 278 under the Vienna Agreement (VA), see Figure 5. The VA is the tool for getting identical standards in CEN and ISO. Joint working groups typically develop standards under the VA; however, the VA can be applied also without having a joint working group. CEN/TC 278 was founded in 1992 with the original title of "Road Transport Traffic Telematics"; the title was harmonised at a later stage with ISO/TC 204.
The missing WG numbers in Figure 5 are due to the fact that some of the initial working groups in CEN/TC 278 and ISO/TC 204 either are dormant, or merged with others, or already closed.
Figure 5 — Working groups and joint working groups in ISO/TC 204 and CEN/TC 278
It is to be noted that ISO/TC 204 founded a new WG 20 on "Big Data and Artificial Intelligence".
Most relevant for C-ITS, in addition to CEN/TC 278 and ISO/TC 204, are
Further relevant is
ETSI TC ITS was founded as the result of an initiative from the ETSI chair and board to become involved in ITS standardisation. It was formed in cooperation with CEN/TC 278 in respect of determining its remit and scope. ETSI TC ITS had its constitutional meeting in December 2007. From this time on, European car makers were involved in standardization, and significantly influence operations in TC ITS. ETSI TC ITS is organized in five working groups:
As the European Union's mandate M/453 on C-ITS from 6th October 2009 was accepted by CEN/TC 278 and by ETSI TC ITS, CEN and ETSI had to formally cooperate and harmonize their contributions, e.g. with ETSI having a focus on its traditional experience on communications, and CEN having a focus on its traditional experience on services and applications. However, as a matter of fact, ETSI developed data and message specifications and ITS applications in its WG1, and CEN / ISO continued developing also communications standards.
ITU has some activities on ITS in general.
Further SDOs, i.e. secondary SDOs with respect of ITS standardisation, are providing general purpose specifications that are applicable for C-ITS and referenced in C-ITS standards, e.g.:
Standardization activities can be grouped in standardization areas as presented in CEN/TR 21186-1. For the purpose of this document, this grouping follows largely the ITS station architecture specified in ISO 21217 and illustrated in Figure 6.
Figure 6 — Simplified ITS station architecture (ISO 21217)
The "Harmonized Architecture Reference for Technical Standards" (HARTS) project applied the same architectural approach using slightly different terms.
The following standardisation areas are identified and used in this multipart document:
High level system architecture and related issues, i.e. the environment in which ITS-SUs according to Figure 6 operate.
Primarily the general framework illustrated in Figure 6.
Issues related to use cases and related applications (procedural behaviour) and their respective communications (data and messages) that are typically architecturally located in the Applications and Facilities blocks of Figure 6.
Management of issues related to whole ITS-SU covering e.g. local station management and remote station management.
Issues architecturally mainly located in the Security block of Figure 6; these issues include interactions between the Security block and basically all other blocks of Figure 6. Note that security also includes privacy.
Communications issues architecturally located in the Access block of Figure 6, i.e. the functionality of the OSI layers 1 and 2.
Communications issues architecturally located in the Networking & Transport block of Figure 6, i.e. the functionality of the OSI layers 3 and 4.
Issues related to communications and applications, architecturally located in the Facilities block of Figure 6, i.e. the functionality of the OSI layers 5, 6, and 7.
Issues related to a combination of A-6, A-7, and A-8.
Within each standardization area, possible subjects of an SDO deliverable are distinguished by means of categories of SDO deliverables; see 2.6.
The following standards categories, applicable for the various standardisation areas presented in 2.5, are identified and used in this multipart document:
The major topic is the provision of results on investigations aiming on identifying potential future standardisation activities.
The major standardization topic is the provision of functional requirements without going into the details of specifications of e.g. protocols, data, or messages.
The major standardization topic is the provision of use case specifications and related illustrations.
The major standardization topic is the provision of definitions of data, also referred to as "data dictionaries", or the specification of messages, typically based on standardized data.
The major standardization topic is the provision of protocol specifications, e.g. communications protocols and procedural behaviour of applications.
The major standardization topic is the provision of profiles based on existing standards, e.g. a communication profile ISO 21215 (ITS-M5) based on the tool box IEEE 802.11 (WiFi).
The major standardization topic is the provision of test specifications, e.g. conformance test suites. Conformance test suites typically consist of three parts, i.e.
The major topic is the provision of information on applicable regulations. Note that such information usually is not provided in standards, whilst standards (e.g. Harmonized European Norms) are referenced by regulation.
The major topic is the provision of registration information, e.g. a registry of OSI layer port numbers for a specific transport protocol, or a registry for globally unique ITS application identifiers (ITS-AID).
The major topic is the provision of tutorials on technical topics and guidelines on how to apply standards; an example is this multipart document.
The major topic is the provision of non-normative information, and are largely different to tutorials and guides, e.g. validation reports on conformance testing and security analysis (TVRA).
The major topic is the provision of results on scientific research related to potential future standardization.
The major standardization topic is the provision of process specifications, e.g. business processes.
This clause provides a short description of standards that are considered to be relevant for future C-ITS Releases; see CEN/TR 21186-1. It is to be noted that C-ITS Releases dedicated to a specific region can be specified. A grouping is performed according to the standardisation areas defined in 2.5. A classification is indicated according to standard categories defined in 2.6.
The References clause contains informative references to additional deliverables from SDOs.
NOTE Standards described in this sub-clause relate to the standardisation area "System architecture" introduced in 2.5.
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
2 |
None |
CEN ISO |
Published |
Several |
||
Description: |
||||||
Describes and specifies globally unique addresses and identifiers (ITS-S object identifiers) which are both internal and external to ITS stations and are used for ITS station management. Describes how ITS-S object identifiers and related technical parameters are used for classification, registration and management of ITS applications and ITS application classes. Describes how ITS-S object identifiers are used in the ITS communication protocol stack. Specifies an ASN.1 module for the identifiers, addresses, and registry records identified in this document. Specifies an ASN.1 module for a C-ITS data dictionary containing general purpose ASN.1 type definitions. |
||||||
Comments: |
||||||
The actual ASN.1 files
are freely available for download via a hyperlink at https://standards.iso.org/iso/17419/ed-1/en. |
||||||
Testing: |
||||||
Conformance testing is not applicable. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1.3.1 |
|
ETSI |
Published |
|||
Description: |
||||||
Specifies a security architecture for Intelligent Transport System (ITS) communications. Based upon the security services defined in ETSI TS 102 731, it identifies the functional entities required to support security in an ITS environment and the relationships that exist between the entities themselves and the elements of the ITS reference architecture defined in ETSI EN 302 665 / ISO 21217. Identifies the roles and locations of a range of security services for the protection of transmitted information and the management of essential security parameters. These include identifier and certificate management, PKI processes and interfaces as well as basic policies and guidelines for trust establishment. |
||||||
Comments: |
||||||
|
||||||
Testing: |
||||||
Unknown |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1 |
None |
ISO |
Published |
|||
Description: |
||||||
Contains a detailed description of the (actor invariant) ‘Roles and Responsibilities’ required to deploy and operate Cooperative-ITS (C-ITS). The organization / organization of actors / roles described in this document are designed to be appropriate for any fully operational system that uses the C-ITS concepts and techniques in order to achieve its service provision. The ‘Organizational’ or ‘Enterprise’ Viewpoint as defined in ISO/IEC 10746 Open Distributed Processing is applied. |
||||||
Comments: |
||||||
It seems to be that, to date, this business process standard is not actually applied anywhere. |
||||||
Testing: |
||||||
Conformance testing is not applicable. |
NOTE Standards described in this sub-clause relate to the standardisation area "Station architecture" introduced in 2.5.
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
2 |
None |
ISO |
Published |
|||
Description: |
||||||
Describes the communications reference architecture of nodes called "ITS station units" designed for deployment in intelligent transport systems (ITS) communication networks. Describes the various communication modes for peer-to-peer communications over various networks between ITS communication nodes. These nodes can be ITS station units as described in ISO 21217 or any other reachable nodes. Specifies the minimum set of normative requirements for a physical instantiation of the ITS station based on the principles of a bounded secured managed domain. |
||||||
Comments: |
||||||
Edition 2 (2014) includes EN 302 665 [79]. Under revision in 2020 to align with latest developments in C-ITS standardization.. |
||||||
Testing: |
||||||
Conformance testing is not applicable. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1 |
None |
ISO |
Published |
|||
Description: |
||||||
Specifies an extension of the ETSI C-ITS test architecture EG 202 798 for conformance testing of protocols and applications in ITS station units. Specifies usage of the ITS station-internal management communication protocol (IICP) ISO 24102-4 for the purpose of connecting an ITS test system to an implementation under test (IUT) residing in a system under test (SUT). |
||||||
Comments: |
||||||
This standard complements ETSI EG 202 798 |
||||||
Related base standards: |
||||||
Those implemented in an ITS-SU conformant with ISO 24102-4. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1.1.1 |
None |
ETSI |
Published |
|||
Description: |
||||||
Support ITS projects on the development of test specifications for ITS base standards from ETSI, ISO, CEN and other ""Standard Developing Organisations"" (SDOs) by providing:
The testing framework provides guidance for development of conformance and interoperability test strategies, test systems and the resulting test specifications for ITS. |
||||||
Comments: |
||||||
|
||||||
Related base standards: |
||||||
Those implemented in an ITS-SU. |
NOTE Standards described in this sub-clause relate to the standardisation area "ITS applications, messages, data" introduced in 2.5.
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1.1.1 |
None |
ETSI |
Published |
|||
Description: |
||||||
Describes a Basic Set of Applications (BSA) to be specified by Intelligent Transport Systems (ITS) in Release 1 of the ETSI ITS standards set. Defines BSA mainly focusing on V2V, V2I and I2V communications in the V2X dedicated frequency band. Introduces a V2X facilities layer model allowing the identification of the functional elements belonging to the facilities layer. |
||||||
Comments: |
||||||
|
||||||
Testing: |
||||||
Conformance testing is not applicable. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1.1.1 |
None |
ETSI |
Published |
|||
Description: |
||||||
Provides the functional requirements for the applications and their use cases as defined in TR 102 638. |
||||||
Comments: |
||||||
|
||||||
Testing: |
||||||
Conformance testing is not applicable. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1 |
None |
ISO |
Published |
|||
Description: |
||||||
Specifies reference architecture for probe vehicle systems and probe data, which provides a general structure for probe vehicle systems within which a wide range of actual probe vehicle systems can be built whose physical characteristics can differ. Specifies basic data framework for probe data elements and probe data, which defines probe data elements and probe messages. Specifies core data element definitions, which are basic descriptive elements intended to appear in every probe message, i.e. the location and the time at which the probe data was sensed. Specifies initial set of probe data elements, which are commonly used in typical probe data enabled application domains, such as traffic, weather, and safety. Provides example probe messages, which define how probe data elements are combined to convey information to probe processing centres. |
||||||
Comments: |
||||||
|
||||||
Testing: |
||||||
Conformance testing is not applicable. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1 |
None |
ISO |
Published |
|||
Description: |
||||||
Provides a common framework for defining probe data reporting management (PDRM) messages to facilitate the specification and design of probe vehicle systems. Specifies reference architecture for probe vehicle systems and probe data which incorporates PDRM, based on the reference architecture for ISO 22837 [42], and basic data framework for PDRM instructions, which defines specifically necessary conditions for PDRM instructions, and notations of these instructions (in XML). |
||||||
Comments: |
||||||
|
||||||
Testing: |
||||||
Conformance testing is not applicable. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1 |
None |
ISO |
Published |
A-3 |
||
Description: |
||||||
Specifies reference architecture for event-based probe vehicles which encompasses event-based probe data and standard probe data elements (ISO 22837). Specifies basic data framework of event-based probe data reporting, based on ISO 22837. Defines an initial set of event-based probe data elements. |
||||||
Comments: |
||||||
|
||||||
Testing: |
||||||
Conformance testing is not applicable. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1.1.1 |
None |
ETSI |
Published |
|||
Description: |
||||||
Provides the specification of the ITS application Road Hazard Signalling (RHS) service based on the cooperative awareness (CA) basic service and the decentralized environmental notification (DEN) basic service. This includes functional and operational requirements of the RHS application. For the originating side of the RHS application the operational conditions related to the hazard detection and the triggering of the DENM are specified. Considers performance requirements for the generation and transmission of CAMs and DENMs, which enable different levels of RHS, and collision avoidance and collision mitigation applications. |
||||||
Comments: |
||||||
|
||||||
Testing: |
||||||
Unknown |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1.1.1 |
None |
ETSI |
Under development |
|||
Description: |
||||||
Aims to provide a description of the Intersection Collision Risk Warning application, and specifications of the necessary parameters and conditions to operate the application using CAM and DENM. |
||||||
Comments: |
||||||
|
||||||
Testing: |
||||||
Unknown |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1.1.1 |
None |
ETSI |
Published |
|||
Description: |
||||||
Provides a description of the Longitudinal Collision Risk Warning (LCRW) application requirements. Provides the specification of the necessary parameters and conditions to operate the application using CAM and DENM. Provides the specifications of functional requirements and operational requirements of the LCRW application. |
||||||
Comments: |
||||||
|
||||||
Testing: |
||||||
Unknown |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1 |
None |
ISO |
Published |
|||
Description: |
||||||
Establishes a common framework data structure for unambiguous identification in RTTT / ITS systems. |
||||||
Comments: |
||||||
|
||||||
Testing: |
||||||
Conformance testing is not applicable. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1.2.1 |
None |
ETSI |
Published |
|||
Description: |
||||||
Defines a repository of a set of data elements and data element sets, denoted as data frames, that are commonly used in the ITS applications and facilities layer messages. Each data element is defined with a set of attributes, enabling the identification of the data element in question in a number of perspectives, e.g. descriptive name, ASN.1 definition, data definition, minimum data granularity requirement, etc. Focus is on the data elements being used by the Cooperative Awareness basic service as outlined in ETSI EN 302 637-2 and by the Decentralized Environmental Notification basic service as outlined in ETSI EN 302 637-3. |
||||||
Comments: |
||||||
This data dictionary contains the definition of the "ETSI common message header" that encapsulating all messages conveyed over the GeoNetworking protocol. This header provides redundant information on the message type which is already provided in the BTP port numbers; by this it violates the OSI layered model. Further on it contains a station identifier which might be subject to privacy issues; usage of this station identifier is unknown. |
||||||
Testing: |
||||||
Conformance testing is not applicable. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
3 |
None |
ISO |
Published |
|||
Description: |
||||||
Specifies the application interface in the context of electronic fee collection (EFC) systems using the dedicated short-range communication (DSRC), including EFC application information that can also be used for C-ITS applications and services. |
||||||
Comments: |
||||||
Clause 8.4 specifies the semantics of vehicle-related data, whilst Annex A presents the associated syntax notation one (ASN.1) type and value definitions. The actual ASN.1 files
are freely available for download via a hyperlink at
Annex E presents a mapping table between the data elements in ISO 14906 and the vehicle registration elements as defined in defined by European Council Directive 1999/37 and the European Commission Directive 2003/127 amending Council Directive 1999/37/EC on the registration documents for vehicles. |
||||||
Testing: |
||||||
The EN 15876 series defines related conformance tests. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1 |
None |
CEN |
Published |
|||
Description: |
||||||
Specifies the DATEX II Version 3.0 framework of all parts of this European Standard, the context of use and the modelling approach taken and used throughout these European Standard. |
||||||
Comments: |
||||||
CEN is revising the whole suite of TS standards for DATEX II version 2.x into DATEX II version 3.0. The new version 3.0 is not backward compatible with any version 2.x. |
||||||
Testing: |
||||||
Unknown |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1 |
Predecessor TS |
CEN |
Published |
|||
Description: |
||||||
Specifies common informational structures, relationships, roles, attributes and associated data types required for publishing information within the DATEX II framework. |
||||||
Comments: |
||||||
This is the first edition defining DATEX II Version 3.0. |
||||||
Testing: |
||||||
Conformance testing is not applicable. |
NOTE Standards described in this sub-clause relate to the standardisation area "Station management" introduced in 2.5.
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
2 |
None |
ISO |
Published |
|||
Description: |
||||||
Specifies communication service parameters presented by ITS station application processes to the ITS-S management in support of automatic selection of ITS-S communication profiles in an ITS station unit. Specifies related procedures for the static and dynamic ITS-S communication profile selection processes at a high functional level. Provides an illustration of objectives used to estimate an optimum ITS-S communication profile. |
||||||
Comments: |
||||||
This standard complements ISO 24102-6 on path and flow management. These two standards are the core management standards for hybrid communications. The actual ASN.1 file
is freely available for download via a hyperlink at https://standards.iso.org/iso/17423/ed-1/en. |
||||||
Testing: |
||||||
PICS included in an Annex. TSS&TP and ATS not available. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1 |
None |
ISO |
Published |
|||
Description: |
||||||
Specifies parameters and procedures for the ITS station management entity to manage data flows and routing paths associated with available communication resources in an ITS station, and to map data flows to routing paths. |
||||||
Comments: |
||||||
This standard complements ISO 17423 on application requirements for communications. These two standards are the core management standards for management of hybrid communications. The actual ASN.1 file
is freely available for download via a hyperlink at https://standards.iso.org/iso/24102/-6/ed-1/en. |
||||||
Testing: |
||||||
Not available. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
2 |
None |
ISO |
Published |
|||
Description: |
||||||
Provides specifications for local management of ITS station units conformant with the ITS station reference architecture specified in ISO 21217. |
||||||
Comments: |
||||||
This standard is a toolbox including pointers to external management standards. The actual ASN.1 file
is freely available for download via a hyperlink at https://standards.iso.org/iso/24102/-1/ed-2/en. |
||||||
Testing: |
||||||
PICS included in an Annex. TSS&TP in ETSI TS 102 797-2 V1.2.1 - to be revised, and ATS in ETSI TS 102 797-3 V1.2.1 - to be revised. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
2 |
None |
ISO |
Published |
|||
Description: |
||||||
Provides specifications for remote station management of ITS station communication units conformant with the ITS station reference architecture specified in ISO 21217. |
||||||
Comments: |
||||||
This standard provides basic requirements for remote station management whilst enabling - to a large extent - private implementations. The actual ASN.1 file
is freely available for download via a hyperlink at https://standards.iso.org/iso/24102/-2/ed-2/en. |
||||||
Testing: |
||||||
PICS included in an Annex. TSS&TP and ATS not available. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
2 |
None |
ISO |
Published |
|||
Description: |
||||||
Provides specifications for secure ITS station-internal management communications. |
||||||
Comments: |
||||||
This standard is only applicable for ITS-SCUs being part of an ITS-SU consisting of several such physical units. In addition, this standard is also used for conformance testing, see TS 20026. The actual ASN.1 file
is freely available for download via a hyperlink at https://standards.iso.org/iso/24102/-4/ed-2/en. |
||||||
Testing: |
||||||
PICS included in an Annex. TSS&TP in ETSI TS 102 797-2 V1.2.1 - to be revised, and ATS in ETSI TS 102 797-3 V1.2.1 - to be revised. |
Under development; see [49].
Under development; see [50].
Under development; see [51].
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1 |
None |
ISO |
Published |
|||
Description: |
||||||
Specifies the management service access points, i.e. the service access points of
|
||||||
Comments: |
||||||
SAPs are not testable. Note that the ASN.1 specifications of this standard (service primitive specifications) become observable and thus testable in protocol data units specified in ISO 24102-4. The actual ASN.1 files
are freely available for download via a hyperlink at https://standards.iso.org/iso/24102/-3/ed-2/en. |
||||||
Testing: |
||||||
Conformance testing is not applicable. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1.2.1 |
None |
ETSI |
Published |
|||
Description: |
||||||
Specifies the access layer part of the decentralized congestion control mechanism for communications at 5,9 GHz. |
||||||
Comments: |
||||||
Bandwidth limitation is an issue in the 10 MHz wide channels at 5,9 GHz. Thus, specific channel congestion control mechanisms are necessary, and multi-hop forwarding with GeoNetworking is not feasible. See also ETSI TS 103 157. Referenced informatively in ISO 24102-1. |
||||||
Testing: |
||||||
Test suite in ETSI TS 102 917-1, TS 102 917-2, TS 102 917-3. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1.2.1 |
None |
ETSI |
Published |
|||
Description: |
||||||
Specifies requirements to ensure coexistence between ITS stations using the frequency bands ITS-G5 A/B/D and CEN DSRC using the TTT band (5,8 GHz). |
||||||
Comments: |
||||||
Only applicable if CEN DSRC at 5,8 GHz [64], [65], [66] is used in the operational area of C-ITS operating in the 5 GHz band. Note: The technical content of [64], [65], [66] is now to be published in ISO 4426, restricted to the usage for remote interrogation of the European Smart Digital Tachograph. Referenced normatively in ISO 24102-1. |
||||||
Testing: |
||||||
Test suite in ETSI TS 102 916-1, TS 102 916-2, TS 102 916-3. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1.1.1 |
None |
ETSI |
Published |
|||
Description: |
||||||
Specifies the functionality of the decentralized congestion control (DCC) entity residing in the management plane for the ITS-G5A, ITS-G5B, and ITS-G5D radio interfaces, collectively known as the 5 GHz ITS frequency band:
|
||||||
Comments: |
||||||
ISO 24102-1 informatively refers to the ETSI DCC |
||||||
Testing: |
||||||
Test suite in ETSI TS 102 917-1, TS 102 917-2, TS 102 917-3. |
NOTE Standards described in this sub-clause relate to the standardisation area "Security" introduced in 2.5.
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1.1.1 |
None |
ETSI |
Published |
|||
Description: |
||||||
Specifies mechanisms at the stage 2 level defined by ETS 300 387 for secure and privacy-preserving communication in ITS environments. It describes facilities for credential and identity management, privacy and anonymity, integrity protection, authentication and authorization. |
||||||
Comments: |
||||||
|
||||||
Testing: |
||||||
Conformance testing is not applicable. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1.3.1 |
None |
ETSI |
Published |
|||
Description: |
||||||
Specifies the trust and privacy management for Intelligent Transport System (ITS) communications. Based upon the security services defined in TS 102 731 and the security architecture define in TS 102 940, it identifies the trust establishment and privacy management required to support security in an ITS environment and the relationships that exist between the entities themselves and the elements of the ITS reference architecture defined in EN 302 665 / ISO 21217. Identifies and specifies security services for the establishment and maintenance of identities and cryptographic keys in an Intelligent Transport System (ITS). Its purpose is to provide the functions upon which systems of trust and privacy can be built within an ITS. |
||||||
Comments: |
||||||
Under revision for considering hybrid communications. |
||||||
Testing: |
||||||
Unknown |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1.1.1 |
None |
ETSI |
Published |
|||
Description: |
||||||
Specifies authentication and authorization services to avoid unauthorized access to ITS services. |
||||||
Comments: |
||||||
|
||||||
Testing: |
||||||
Unknown |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1.1.1 |
None |
ETSI |
Published |
|||
Description: |
||||||
Specifies services to ensure that that the confidentiality of information sent to and from an ITS station can be maintained at a level that is acceptable to the users of the station. |
||||||
Comments: |
||||||
|
||||||
Testing: |
||||||
Unknown |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1.3.1 |
|
ETSI |
Published |
|||
Description: |
||||||
Specifies the secure data structure including header and certificate formats for Intelligent Transport Systems. |
||||||
Comments: |
||||||
The document is based on the specifications in IEEE Std. 1609.2™: "IEEE Standard for Wireless Access in Vehicular Environments — Security Services for Applications and Management Messages", as amended by IEEE Std. 1609.2a™-2017: "Standard for Wireless Access In Vehicular Environments — Security Services for Applications and Management Messages Amendment 1". |
||||||
Testing: |
||||||
Test suite provided in ETSI TS 103 096-1, TS 103 096-2, TS 103 096-3. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
2016 with amendment 2017 |
None |
IEEE |
Published |
|||
Description: |
||||||
Defines secure message formats and processing for use by Wireless Access in Vehicular Environments (WAVE) devices, including methods to secure WAVE management messages and methods to secure application messages. Describes administrative functions necessary to support the core security functions. |
||||||
Comments: |
||||||
This edition is being complemented by IEEE 1609.2b. |
||||||
Testing: |
||||||
Unknown |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1 |
None |
ISO |
Published |
|||
Description: |
||||||
Contains specifications for a set of ITS station security services required to ensure the authenticity of the source and integrity of information exchanged between trusted devices, i.e. devices operated as bounded secured managed entities specified in ISO 21217 and external entities such as sensor and control networks. These services include authentication and secure session establishment which are required to exchange information in a trusted and secure manner. Such secured services are essential for many ITS applications and services including time-critical safety applications, automated driving, remote management of ITS stations (ISO 24102-2), and roadside / infrastructure related services. |
||||||
Comments: |
||||||
This is also applicable for accessing sensor and control networks, e.g. probe data in vehicles via the CAN bus. The actual ASN.1 files
are freely available for download via a hyperlink at https://standards.iso.org/iso/ts/21177/ed-1/en. Complements to and minor modifications of ISO 21177 are proposed in TR 21186-3, and already processed in the new work item to amend and slightly revise the standard. |
||||||
Testing: |
||||||
Not available |
NOTE Standards described in this sub-clause relate to the standardisation area "Access layer technologies" introduced in 2.5.
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
2 |
None |
ISO |
Published |
|||
Description: |
||||||
Provides specifications of a communication interface (CI) named "ITS-M5" with reference to IEEE Std 802.11™. Specifies the additions to and deviations from IEEE Std 802.11™ required to make ITS-M5 CIs compatible with the ITS station and communication architecture specified in ISO 21217. Supports frequency regulation in all regions, with explicit reference to European frequency regulation (EN 301 893, EN 302 571). Supports both OCB mode and ordinary WiFi mode. |
||||||
Comments: |
||||||
Covers fully ETSI EN 302 663 V1.2.1 with the difference, that EN 302 663 V1.2.1 still uses LPD instead of EPD – although EPS is required in the 2016 edition of the referenced base standard IEEE Std 802.11™, whilst ISO 21215 uses EPD - as US DSRC (WAVE) does. Candidate to replace ETSI EN 302 663, and by this enhance the supported functionality. Includes European usage as specified in the context of EN 302 663. The actual ASN.1 file
are freely available for download via a hyperlink at https://standards.iso.org/iso/21215/ed-2/en. |
||||||
Testing: |
||||||
PICS included in Annex. TSS&TP and ATS not available. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
2 |
None |
ISO |
In publication |
|||
Description: |
||||||
Specifies general technical details related to the access layer of the ITS station reference architecture specified in ISO 21217 including
|
||||||
Comments: |
||||||
This is one of the core standards for hybrid communications. Provides a common communications SAP for all kinds of access technologies, including cellular networks. The actual ASN.1 file
is freely available for download via a hyperlink at https://standards.iso.org/iso/21218/ed-3/en. |
||||||
Testing: |
||||||
PICS included in Annex. TSS&TP and ATS not available. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1.2.1 |
None |
ETSI |
Published |
|||
Description: |
||||||
Specifies a profile of IEEE Std 802.11™ OCB @ 5,9 GHz for Europe. |
||||||
Comments: |
||||||
The functionality of this ETSI standard is fully covered by ISO 21215, including the correct protocol discrimination (EPD), whilst EN 302 663 V1.2.1 still uses LPD which is deprecated by IEEE. |
||||||
Testing: |
||||||
Unknown |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1.1.1 |
None |
ETSI |
Published |
|||
Description: |
||||||
Specifies details of the channel usage in the ITS G5A and ITS G5B bands including multichannel operation support. |
||||||
Comments: |
||||||
This functionality is also supported by ISO 21215 |
||||||
Testing: |
||||||
Unknown |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
2016 |
None |
IEEE |
Published |
|||
Description: |
||||||
Provides one medium access control (MAC) and several physical layer (PHY) specifications for wireless connectivity for fixed, portable, and moving stations (STAs) within a local area. |
||||||
Comments: |
||||||
Included in ISO 21215 by reference. |
||||||
Testing: |
||||||
Unknown |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
2.1.1 |
None |
ETSI |
Published |
|||
Description: |
||||||
Specifies technical characteristics and methods of measurements for 5 GHz wireless access systems (WAS) including RLAN equipment. Describes spectrum access requirements to facilitate spectrum sharing with other equipment. This radio equipment is capable of operating in all or parts of the frequency bands:
Covers the essential requirements of article 3.2 of Directive 2014/53/EU. |
||||||
Comments: |
||||||
This standard can be used in combination with ISO 22418 (service announcement), applying ISO 21215 (OCB mode) with the service announcer being the entity performing the required DFS. |
||||||
Testing: |
||||||
Conformance testing is not applicable. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
2.1.1 |
None |
ETSI |
Published |
|||
Description: |
||||||
Specifies technical characteristics and methods of measurement for radio transmitters and receivers operating in the frequency range 5 855 MHz to 5 925 MHz. The spectrum usage conditions are set out in ECC Decision (08)01 for the frequency range 5 875 MHz to 5 925 MHz (with 5 905 MHz to 5 925 MHz considered as a future ITS extension) and in ECC Recommendation (08)01 for the frequency range 5 855 MHz to 5 875 MHz. The Commission Decision 2008/671/EC mandates a harmonised use of the frequency band 5 875 MHz to 5 905 MHz dedicated to safety-related applications of ITS throughout the member states of the European Union. 5 GHz ITS frequency band segmentation:
Covers the essential requirements of article 3.2 of Directive 2014/53/EU. Interference mitigation techniques in the present document are provided to protect road tolling applications using CEN DSRC or HDR DSRC." |
||||||
Comments: |
||||||
Cited in the Official Journal of the European Union |
||||||
Testing: |
||||||
Conformance testing is not applicable. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
2015 |
None |
ISO |
Published |
|||
Description: |
||||||
Specifies general usage of LTE in an ITS-SU conformant with ISO 21217 and ISO 21218 for access to Internet. |
||||||
Comments: |
||||||
Essential technical specifications for LTE Internet access are provided by 3GPP. This is a "placeholder" for any kind of cellular access to the Internet. For this type of communications, the concept of "neutrality of technologies" applies. |
||||||
Testing: |
||||||
not available |
NOTE Standards described in this sub-clause relate to the standardisation area "Network and transport layer technologies" introduced in 2.5.
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
2 |
None |
ISO |
Under publication |
|||
Description: |
||||||
Specifies the "Fast Networking & Transport Protocol" (FNTP) for efficient localized communications distinguishing networking related features and transport related features. FNTP is extendible in the future without breaking binary backward compatibility. Specifies |
||||||
Comments: |
||||||
Provides broadcast interoperability mode with IEEE 1609.3 WSMP. The actual ASN.1 file
is freely available for download via a hyperlink at https://standards.iso.org/iso/29281/-1/ed-2/en. |
||||||
Testing: |
||||||
PICS contained in an Annex. TSS&TP in ETSI TS 102 985-2 V1.2.1 [157] - to be revised, and ATS in ETSI TS 102 985-3 V1.2.1 [158] - to be revised. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1 plus |
None |
ISO |
Published |
|||
Description: |
||||||
Specifies networking protocol functionalities related to IPv6 networking between two or more ITS stations communicating over the global Internet communication network. |
||||||
Comments: |
||||||
ISO 21210 will be complemented and split into a multi-part document with the new title " Intelligent transport systems - IPv6 networking " and with four parts:
The actual ASN.1 file
is freely available for download via a hyperlink at https://standards.iso.org/iso/21210/. |
||||||
Testing: |
||||||
Not available |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1.3.1 |
None |
ETSI |
Published |
|||
Description: |
||||||
Specifies the media-independent functionality of the GeoNetworking protocol. |
||||||
Comments: |
||||||
It is agreed that the multi-hop forwarding, for which GeoNetworking was designed, is not applicable in the 10 MHz wide channels at 5,9 GHz. Single hop localized communications can be achieved more efficiently by applying the ISO 29281-1 FNTP messaging protocol, which has the broadcast interoperability mode with IEEE 1609.3 WSMP. However GeoNetworking single-hop mode is already supported by all vendors of ITS-SUs. GeoNetworking thus is the recommended protocol for early deployment. Thus coexistence with ISO 29281-1 and a migration towards ISO 29281-1 are recommended. It is to be noted that a TS version of this standard co-exists; it is not obvious whether the EN or the TS version is closer to the implementation reality. |
||||||
Testing: |
||||||
Test suite available in the ETSI series TS 102 871-1, TS 102 871-2, TS 102 871-3. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1.1.3 |
None |
ETSI |
Published |
|||
Description: |
||||||
Specifies the media-dependent functionalities for GeoNetworking over ITS-G5 as a network protocol for ad hoc routing in vehicular environments |
||||||
Comments: |
||||||
See comment on EN 302 636-4-1 in 3.8.3. |
||||||
Testing: |
||||||
Test suite available in the ETSI series TS 102 871-1, TS 102 871-2, TS 102 871-3. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
2.2.1 |
None |
ETSI |
Published |
|||
Description: |
||||||
Specifies the Basic Transport Protocol (BTP) for the transport of packets among ITS stations. It resides on top of the GeoNetworking protocol specified in ETSI EN 302 636-4-1 and ETSI TS 102 636-4-2 and below the ITS-S facilities layer. It provides an end-to-end, connection-less and unreliable transport service. |
||||||
Comments: |
||||||
See comment on ETSI EN 302 636-4-1 in 3.8.3. It is to be noted that a TS version of this standard co-exists; it is not obvious whether the EN or the TS version is closer to the implementation reality. This standard is only needed in combination with EN 302 636-4-x. |
||||||
Testing: |
||||||
Test suite available in the ETSI series TS 102 870-1, TS 102 870-2, TS 102 870-3. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1.2.1 |
None |
ETSI |
Published |
|||
Description: |
||||||
Specifies the transmission of IPv6 packets over the ETSI GeoNetworking protocol as defined in ETSI EN 302 636-4-1 via a protocol adaptation sub-layer referred to as the GN6ASL (GeoNetworking to IPv6 Adaptation Sub-Layer). The scope of the present document is limited to the GN6ASL. |
||||||
Comments: |
||||||
See comment on ETSI EN 302 636-4-1. It is to be noted that a TS version of this standard co-exists; it is not obvious whether the EN or the TS version is closer to the implementation reality. This standard is only needed in combination with EN 302 636-4-x. |
||||||
Testing: |
||||||
Test suite available in the ETSI series TS 102 859-1 [136], TS 102 859-2 [137], TS 102 859-3 [138]TS 102 859-1, TS 102 859-2, TS 102 859-3. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1.1.1 |
|
ETSI |
Published |
|||
Description: |
||||||
Specifies geometrical shapes to be used as geographical area definitions |
||||||
Comments: |
||||||
This is used in GeoNetworking. |
||||||
Testing: |
||||||
Conformance testing is not applicable. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1.1.1 |
None |
ETSI |
Published |
|||
Description: |
||||||
Defines port number values for the Basic Transport Protocol as specified in ETSI EN 302 636-5-1. |
||||||
Comments: |
||||||
As this port number space is dedicated to the GeoNetworking protocol, it is not applicable for other messaging protocols, e.g. FNTP specified in ISO 29281-1 or WSMP specified in IEEE 1609.3. |
||||||
Testing: |
||||||
Conformance testing is not applicable. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1 |
None |
ISO |
Published |
|||
Description: |
||||||
Specifies
Further protocol details are specified in ISO 29281-1. |
||||||
Comments: |
||||||
Harmonized message formats used in ISO 29281-1 and IEEE Std. 1609.3. Specifies also harmonized messages for service announcement; see 3.9.3. The actual ASN.1 files
are freely available for download via a hyperlink at https://standards.iso.org/iso/ts/16460/TS%2016460%20ASN.1%20repository. |
||||||
Testing: |
||||||
Will be tested in the context of the target protocol, e.g. ISO 29281-1. |
NOTE Standards described in this sub-clause relate to the standardisation area A-8 "Facility layer technologies" introduced in 2.5.
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1 |
None |
ISO |
Published |
|||
Description: |
||||||
Defines message, data structures, and data elements in support of exchanges between the roadside equipment (traffic lights) and vehicles. Creates profiles of SAE J2735. |
||||||
Comments: |
||||||
The actual ASN.1 file
is freely available for download via a hyperlink at https://standards.iso.org/iso/ts/19091/ed-2/en. |
||||||
Testing: |
||||||
PICS to be developed in CEN ISO TS 20598. TSS&TP and ATS not available. There is a test suite dedicated to the SAE version of TS 19091 provided in the ETSI series TS 103 191-1, 103 191-2, 103 191-3. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1 |
None |
ISO |
Published |
|||
Description: |
||||||
Specifies in-vehicle information (IVI) data structures that are required by different ITS services (for example, refer to ISO TS 17425 and ISO TS 17426) for exchanging information between ITS Stations. |
||||||
Comments: |
||||||
The actual ASN.1 file
is freely available for download via a hyperlink at https://standards.iso.org/iso/ts/19321/ed-2/en. |
||||||
Testing: |
||||||
PICS to be developed in CEN ISO TS 20597. TSS&TP and ATS not available. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1 |
None |
ISO |
Published |
|||
Description: |
||||||
Specifies
Further protocol details are specified in ISO 22418. |
||||||
Comments: |
||||||
Harmonized message formats used in ISO 22418 and IEEE Std. 1609.3. Specifies also the harmonized messaging format; see 3.8.9. The actual ASN.1 files
are freely available for download via a hyperlink at https://standards.iso.org/iso/ts/16460/TS%2016460%20ASN.1%20repository. |
||||||
Testing: |
||||||
Will be tested in the context of the target protocol, e.g. ISO 22418. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1 |
None |
ISO |
Published |
|||
Description: |
||||||
Specifies generic mechanisms enabling the exchange of information between ITS stations for applications related to Intelligent Transport Systems. It complies with the ITS station reference architecture (ISO 21217) and defines the following ITS station facilities layer functionalities:
|
||||||
Comments: |
||||||
Will be split into a multi-part document with the new title " Cooperative intelligent transport systems (C-ITS) — ITS station facility services" and with three parts:
|
||||||
Testing: |
||||||
PICS to be developed in CEN ISO TS 20594. TSS&TP and ATS not available. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
2 |
None |
ISO |
Published |
|||
Description: |
||||||
Describes the functionality of a "Local Dynamic Map" (LDM) in the context of the "Bounded Secured Managed Domain" (BSMD); Specifies
|
||||||
Comments: |
||||||
This testable standard fully covers the functionality of ETSI EN 302 895, which is not testable. The actual ASN.1 file
is freely available for download via a hyperlink at https://standards.iso.org/iso/18750/ed-1/en. |
||||||
Testing: |
||||||
PICS contained in an Annex. TSS&TP and ATS to be developed. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1 |
None |
ISO |
Published |
|||
Description: |
||||||
Specifies a generic PVT (absolute Position, Velocity and Time) service within the ITS station facilities layer (ISO 21217) and its interface to e.g.
|
||||||
Comments: |
||||||
Provides flexibility for various formats of PVT data. Explicitly refers to the format specifications in ETSI TS 102 894-2. |
||||||
Testing: |
||||||
PICS contained in an Annex. TSS&TP and ATS to be developed. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
2 |
None |
ISO |
Published |
|||
Description: |
||||||
Specifies the "Fast Service Advertisement Protocol" (FSAP) in support of locally advertised ITS services uniquely identified by an ITS application identifier (ITS-AID). Specifies message formats and related basic protocol procedures by reference to ISO 16460, and further related protocol requirements for operation of FSAP in the context of an ITS station specified in ISO 21217. |
||||||
Comments: |
||||||
Provides interoperability mode with IEEE Std 1609.3 WSA.
will become freely available for download via a hyperlink at https://standards.iso.org/iso/22418/ed-2/en. |
||||||
Testing: |
||||||
PICS contained in an Annex. TSS&TP and ATS to be developed. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1.4.1 |
None |
ETSI |
Published |
|||
Description: |
||||||
Provides the specifications of the Cooperative Awareness basic service (CA basic service), which is in support of the BSA road safety application. Specifies the syntax and semantics of the Cooperative Awareness Message (CAM) and and the CAM protocol handling. |
||||||
Comments: |
||||||
There are discussions at ETSI to revise this standard in order to make CAM better fit to cellular network communications. That would break backward compatibility. |
||||||
Testing: |
||||||
Test suite available in ETSI series of TS 102 868-1, TS 102 868-2, TS 102 868-3. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1.3.1 |
None |
ETSI |
Published |
|||
Description: |
||||||
Provides specification of the DEN basic service, which is in support of the RHW application. |
||||||
Comments: |
||||||
There are discussions at ETSI to revise this standard in order to make DENM better fit to cellular network communications. That would break backward compatibility. |
||||||
Testing: |
||||||
Test suite available in ETSI series of TS 102 869-1, TS 102 869-2, TS 102 869-3. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1 |
None |
ISO |
Published |
|||
Description: |
||||||
Contains specifications of the "Global Transport Data Management" (GTDM) framework covering also sensor and control network related information to be made available in a safe and secure manner to ITS applications. Specifies mechanisms how messages are assembled and disassembled, based on configuration definitions. Provides specifications of the process of registering new data objects. These services are essential for many ITS applications and services including time-critical safety applications, automated driving, remote management of ITS stations (ISO 24102-2), and roadside / infrastructure related services. |
||||||
Comments: |
||||||
|
||||||
Testing: |
||||||
Not available |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1.1.1 |
|
ETSI |
Published |
|||
Description: |
||||||
Defines the functional architecture for the facilities layer of the ITS station and provides functional requirements and specifications for main identified facilities in support of the BSA specified in ETSI TR 102 638. |
||||||
Comments: |
||||||
|
||||||
Testing: |
||||||
Conformance testing is not applicable. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1.2.1 |
|
ETSI |
Published |
|||
Description: |
||||||
Provides specifications of infrastructure related ITS services to support communication between infrastructure ITS equipment and traffic participants using ITS equipment (e.g. vehicles, pedestrians). It defines services in the Facilities layer for communication between the infrastructure and traffic participants. The specifications cover the protocol handling for infrastructure-related messages as well as requirements to lower layer protocols and to the security entity. |
||||||
Comments: |
||||||
|
||||||
Testing: |
||||||
|
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1 |
None |
ISO |
Published |
|||
Description: |
||||||
Specifies the In-Vehicle Signage service and application that delivers In-Vehicle Signage information to ITS stations (vehicle ITS stations or personal ITS stations devices) concerning road and traffic conditions, qualified by road authorities/operators, in a consistent way with road authority's/operator's requirements, in the manner that is coherent with the information that would be displayed on a road sign or variable message sign (VMS). |
||||||
Comments: |
||||||
Overlaps with CEN ISO TS 19091. |
||||||
Testing: |
||||||
Unknown |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1 |
None |
ISO |
Published |
|||
Description: |
||||||
Specifies the Contextual Speed Information Service, namely the general requirements regarding the provision of the Contextual Speed Information Service, the data flow supporting the service, and the presentation of the service result. |
||||||
Comments: |
||||||
|
||||||
Testing: |
||||||
PICS specification ISO 21189. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1 |
Predecessor TS |
CEN |
Published |
|||
Description: |
||||||
Specifies the informational structures, relationships, roles, attributes and associated data types, for the implementation of the location referencing systems used in association with the different publications defined in the Datex II framework. |
||||||
Comments: |
||||||
This is the first edition defining DATEX II Version 3.0. |
||||||
Testing: |
||||||
Conformance testing is not applicable. |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1 |
Predecessor TS |
CEN |
Published |
|||
Description: |
||||||
Specifies the informational structures, relationships, roles, attributes and associated data types required for publishing situation traffic and travel information within the DATEX II framework. |
||||||
Comments: |
||||||
This is the first edition defining DATEX II Version 3.0. |
||||||
Testing: |
||||||
Conformance testing is not applicable. |
NOTE Standards described in this sub-clause relate to the standardisation area A-9 "Protocol stack" introduced in 2.5.
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1 |
None |
CEN |
Published |
|||
Description: |
||||||
Contains specifications of the methodology to identify communication profiles based on standardized communication protocols to interconnect ITS station units. Globally unique identifiers of communication profiles are used e.g. in ISO 22418. |
||||||
Comments: |
||||||
An initial Vienna Agreement was cancelled by CEN: almost identical TS at ISO published with slightly different title: ISO/TS 21185 Intelligent transport systems — Communication profiles for secure connections between trusted devices. |
||||||
Testing: |
||||||
Not available |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
1 |
None |
CEN |
Published |
|||
Description: |
||||||
Defines the high-level application protocols, procedures and processes required to provide the eCall service via an ISO 21217 conformant "ITS station unit". |
||||||
Comments: |
||||||
Uses ISO 22418. |
||||||
Testing: |
||||||
Not available |
Reference: |
Latest edition: |
Other editions: |
SDO: |
Status: |
Standard area |
Standard category |
2016 |
None |
SAE |
Published |
|||
Description: |
||||||
Specifies the system requirements for an on-board vehicle-to-vehicle (V2V) safety communications system for light vehicles, including standards profiles, functional requirements, and performance requirements. The system is capable of transmitting and receiving the Society of Automotive Engineers (SAE) J2735-defined Basic Safety Message (BSM) over a Dedicated Short Range Communications (DSRC) wireless communications link as defined in the Institute of Electrical and Electronics Engineers (IEEE) 1609 suite [107, 108, 109, 110] and IEEE 802.11 [112] standards. |
||||||
Comments: |
||||||
This is not just applicable for C-ITS in the USA, but also referenced in the European Union. |
||||||
Testing: |
||||||
Unknown |