Standards List

This document:
— describes the functionality of a 'Local Dynamic Map' (LDM) in the context of the 'Bounded Secured Managed Domain' (BSMD);
— specifies:
— general characteristics of LDM Data Objects (LDM-DOs) that may be stored in an LDM, i.e. information on real objects such as vehicles, road works sections, slow traffic sections, special weather condition sections, etc. which are as a minimum requirement location-referenced and time-referenced;
— service access point functions providing interfaces in an ITS station (ITS-S) to access an LDM for:
— secure add, update and delete access for ITS-S application processes;
— secure read access (query) for ITS-S application processes;
— secure notifications (upon subscription) to ITS-S application processes;
— management access:
— secure registration, de-registration and revocation of ITS-S application processes at LDM;
— secure subscription and cancellation of subscriptions of ITS-S application processes;
— procedures in an LDM considering:
— means to maintain the content and integrity of the data store;
— mechanisms supporting several LDMs in a single ITS station unit.

This document specifies basic control strategies, minimum functional requirements, basic driver interface elements, and test procedures for verifying the system requirements for collision evasive lateral manoeuvre systems (CELM).
A CELM is a safety system aimed at supporting the driver’s vehicle operation by avoiding collisions with objects in the forward path of the vehicle. When a collision is predicted, the CELM controls lateral movement of the vehicle by generating yaw moment.
The lateral control manoeuvres can be performed automatically by CELM or can be initiated by the driver and supported by CELM.
Specific methods for object detection and other environmental perception technologies are not described in this document.
This document applies to light vehicles[1] and heavy trucks.[1] Vehicles equipped with trailers are not within the scope of this document.

ISO 24102-5:2013 specifies procedures and data elements in the ITS station management entity and the ITS station facilities layer of the ITS station reference architecture for advertisement of locally available ITS services. These procedures and data elements constitute the 'Fast Service Advertisement Protocol' (FSAP). Note: Replaced by CEN/ISO 22418:2020

This document 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.

Cooperative Adaptive Cruise Control (CACC) system is an expansion to existing Adaptive Cruise Control (ACC) control strategy by using wireless communication with preceding vehicles (V2V) and/or the infrastructure (I2V). Both multi vehicle V2V data and I2V infrastructure data are within the scope of this document. When V2V data is used CACC can enable shorter time gaps and more accurate gap control, which can help increase traffic throughput and reduce fuel consumption. It can also receive data from the infrastructure, such as recommended speed and time gap setting, to improve traffic flow and safety.
This document addresses two types of Cooperative Adaptive Cruise Control (CACC): V2V, and I2V. Both types of CACC system require active sensing using for example radar, lidar, or camera systems. The combined V2V and I2V CACC is not addressed in this document. The following requirements are addressed in this document:
— classification of the types of CACC;
— definition of the performance requirements for each CACC type;
— CACC state transitions diagram;
— minimum set of wireless data requirements;
— test procedures.
CACC:
— does only longitudinal vehicle speed control;
— uses time gap control strategy similar to ACC;
— has similar engagement criteria as ACC.
Coordinated strategies to control groups of vehicles, such as platooning, in which vehicle controllers base their control actions on how they affect other vehicles, and may have a very short following clearance gap are not within the scope of this document. CACC system operates under driver responsibility and supervision.
This document is applicable to motor vehicles including light vehicles and heavy vehicles.

This document specifies the in-vehicle information (IVI) data structures that are required by different intelligent transport system (ITS) services for exchanging information between ITS Stations (ITS-S). A general, extensible data structure is specified, which is split into structures called containers to accommodate current-day information. Transmitted information includes IVI such as contextual speed, road works warnings, vehicle restrictions, lane restrictions, road hazard warnings, location-based services, re-routing. The information in the containers is organized in sub-structures called data frames and data elements, which are described in terms of its content and its syntax.
The data structures are specified as communications agnostic. This document does not provide the communication protocols. This document provides scenarios for usage of the data structure, e.g. in case of real time, short-range communications.

This Technical Specification 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:
— Communication Profile Handler (CPH);
— Content Subscription Handler (CSH);
— Facilities Services Handler (FSH).
These functionalities are used by ITS-S application processes (ITS-S-AP) to communicate with other ITS-S application processes and share information. These functionalities describe
— how lower-layer communication services assigned to a given data flow are applied to the service data units at the various layers in the communication protocol stack (CPH, see 6.2.3),
— how content from data dictionaries can be published and subscribed to by ITS-S application processes (CSH, see 6.2.5),
— how well-known ITS station facilities layer and management services can be applied to application process data units (FSH, see 6.2.4), relieving (ITS-S) application processes from having to implement these services on their own,
— how service access points (SAP) primitives specified in ISO 24102-3 are used,
— service primitives for the exchange of information between ITS-S application processes and the ITS station facilities layer (FA-SAP), and
— a set of communication requirements and objectives (profiles) using the methods defined in ISO/TS 17423 to select the level of performance (best effort or real-time, etc.), confidence and security (authentication, encryption, etc.) for information exchange between ITS stations, such as data provision, event notification, roadside configuration, map update.

This document contains a detailed description of the (actor invariant) roles (3.22) and responsibilities (3.21) required to deploy and operate Cooperative-ITS (C-ITS) (3.8). 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. This document is presented in terms of an organizational or enterprise viewpoint (3.10) as defined in ISO/IEC 10746-1.
This document is for all types of road traffic of all classes, and for any other actors involved in the provision of applications and services which use C-ITS techniques to achieve service provision. The description of roles is technology agnostic and, in terms of C-ITS, agnostic in respect of communication modes and embraces vehicle-vehicle communications, vehicle-infrastructure communications and infrastructure-infrastructure communications.
This document provides a methodology for the identification of service specific roles and their corresponding responsibilities based on a process oriented approach. Additionally, the methodology is used to identify the roles and responsibilities for C-ITS in general. Both the methodology as well as the roles and responsibilities for C-ITS are deduced from ISO/IEC 10746-1, ISO/IEC 10746-2, ISO/IEC 10746-3, the reference model of Open Distributed Processing. Open Distributed Processing offers five viewpoints of which the enterprise viewpoint corresponds with the organizational architecture and its roles and responsibilities.
To limit the scope of the document to the core of C-ITS, the roles are separated into external and internal. Considered to be internal are all roles that are highly relevant for the purpose of achieving service provision by means of C-ITS. Considered to be external are all roles involved in C-ITS, but not set up only for the purpose of C-ITS.
This document provides a description of a high-level architectural viewpoint on C-ITS. It is designed to be used as a blueprint when implementing service provision systems that use C-ITS, and the corresponding organizational structures. The characteristics of C-ITS entail a huge number of data/ information exchanges. Therefore the implementation stringently respects privacy and data protection as it is defined in ISO/TR 12859 and in national laws and regulations (where instantiated). Privacy and data protection affects all roles defined in this document due to these characteristics and all actors occupying roles in C-ITS respects the corresponding standards and regulations.

This document
— specifies communication service parameters presented by ITS station (ITS-S) application processes to the ITS-S management in support of automatic selection of ITS-S communication profiles in an ITS station unit (ITS-SU),
— 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.

This document
— 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,
— introduces an organizational framework for registration and management of ITS-S objects,
— defines and specifies management procedures at a high functional level,
— is based on the architecture of an ITS station specified in ISO 21217:2014 as a Bounded Secured Managed Domain (BSMD),
— specifies an ASN.1 module for the identifiers, addresses, and registry records identified in this document, and
— specifies an ASN.1 module for a C-ITS Data Dictionary containing ASN.1 type definitions of general interest.