Standards List

This document contains the basic control strategy, minimum functionality requirements, basic driver interface elements, minimum requirements for diagnostics and reaction to failure, and performance test procedures for road boundary departure prevention systems (RBDPS). RBDPS is a driving safety support system which acts on vehicles to prevent road departures. RBDPS is designed to reduce damage and accidents arising from road boundary departures.
This document is intended to be applied to systems that predict road boundary departures and maintain the vehicle within the road boundaries by both lateral acceleration control and longitudinal deceleration control. RBDPS is intended to operate on roads (well-developed and standardized freeways or highways) having solid lane markers. Roadwork zones or roads without visible road boundary markers are not within the scope of this document. RBDPS is intended for light duty passenger vehicles and heavy vehicles. RBDPS is not designed to operate continuously, but to operate automatically only when possible road boundary departures are detected or predicted. However, the driver’s decision and operation takes priority at all times.

This document is a compilation of terms to be contained in a spatio-temporal data dictionary for cooperative-ITS and automated driving systems.
This data dictionary includes static data (e.g. map, road signs and buildings) and dynamic data (e.g. traffic condition, accident reports).
This document is an updated and expanded version of ISO/TR 21718:2017.

This document describes the communications reference architecture of nodes called “ITS station units” designed for deployment in intelligent transport systems (ITS) communication networks. The ITS station reference architecture is described in an abstract manner. While this document describes a number of ITS station elements, whether or not a particular element is implemented in an ITS station unit depends on the specific communication requirements of the implementation.
This document also 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 this document or any other reachable nodes.
This document 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.

This document defines the terms and definitions related to truck platooning systems (TPS), and the mode transitions in the platooning control system (PCS). The PCS is comprised of two main functions: the platooning operation control function (POCF) and the platooning manoeuvre control function (PMCF).
This document specifies:
— POCF and PMCF governing how vehicles join and leave platoons;
— PMCF governing longitudinal and lateral control of each vehicle;
NOTE PMCF makes reference to current International Standards, such as ISO 20035, ISO 11270 and ISO 21717, where appropriate.

— functional evaluation test methods for POCF and PMCF.
This document also describes:
— the data to be communicated for POCF and PMCF in vehicle to vehicle (V2V) messages and optionally in vehicle to infrastructure (V2I) messages, including local roadside and broader network and cloud;
— strategies for forming platoons, such as ad-hoc or planned formation, and types of truck platooning systems, such as top-down management and peer-to-peer.
This document covers:
— platooning of heavy goods vehicles of multiple brands and fleets, operated by on-board drivers. Light trucks, buses and passenger cars are excluded;
— level 1 and 2 driving automation systems, which provide driver support and operate under the continuous supervision of the drivers.
The functions and operations of the back office (BO) are out of scope of this document.

This part of ISO 13185 specifies the communications architecture and generic protocol to provide and maintain ITS services to travellers (including drivers, passengers and pedestrians), using nomadic and portable devices for:
— The mobile device as a mobile router,
— Augmentation of the capabilities of a nomadic device using information from in-vehicle systems,
— Nomadic device acting as a key to personalise the vehicle configuration,
— Using capabilities of a nomadic or mobile device to augment functionality within the vehicle,
— The use of portable nomadic devices within commercial vehicles and public transport,
— Optimising the use of the capabilities in nomadic and mobile devices in the provision of ITS services,
— Harmonization of existing standards to support a single solution access method,
— Applications supporting ITS service provision and multimedia use a common access method to retrieve vehicle data through a vehicle communication interface.

This part of ISO 13185 specifies the requirements of an ASN.1-based protocol between a vehicle-ITS-Station Gateway (V-ITS-SG) and a nomadic and/or mobile device (ND) to easily exchange vehicle information data.
The ASN.1-based protocol has been specified to support a wired or wireless connection between the ND and V-ITS-SG.
The Unified Gateway Protocol (UGP) is used between the V-ITS-SG and the ND. UGP supports several features in order to provide
— authorization (data privacy),
— secured access,
— V-ITS-SG and in-vehicle ECUs identification,
— real-time vehicle data parameters with identifier and type information in ASN.1 format, and
— enhanced vehicle data parameters with identifier and type information in ASN.1 format.

This document specifies the server and client APIs of the Unified Gateway Protocol (UGP). A UGP client application on a P-ITS-S communicates with a UGP server application on a V-ITS-S. The UGP client application implements the UGP client API using ISO 13185-2. The UGP server application implements the UGP server API using ISO 13185-2.

This document specifies a conformance test for a UVIP server and client system developer assessment of self-conformance of the supplier's UVIP server and client system. The conformance test cases follow the use cases definition of ISO 13185-1 and the requirements stated in ISO 13185-2 and ISO 13185-3.
The purpose of this document is to provide information to the UVIP server and client system provider to build and test the UVIP server and client system against the conformance test cases.

This document specifies performance requirements and test procedures for systems capable of warning the subject vehicle driver of a potential crossing-path collision with other vehicles at intersecting road segments.
Vehicle-to-vehicle intersection collision warning systems (VVICW) rely on vehicle-to-vehicle (V2V) communications and relative positioning between the subject vehicle and crossing-path vehicles (remote vehicles). V2V data, such as position, speed and heading are used to evaluate if an intersection collision is imminent between the subject and remote vehicles. The performance requirements laid out in this document specify the warning criteria for these systems.
In addition, VVICW operate in specified subject and remote vehicle speed ranges, road intersection geometries and target vehicle types. Moreover, the requirements for the V2V data will be specified. The scope of this document includes operations on intersecting road segments (physically intersecting roads), and motor vehicles including cars, trucks, buses and motorcycles. Responsibility for the safe operation of the vehicle remains with the driver.

This document provides the results of consideration on potential areas and items of standardization for automated driving systems. In this document, automated driving systems are defined as systems that control longitudinal and lateral motions of the vehicle at the same time.
Potential standardization areas and items are widely extracted and marshalled in a systematic manner to distinguish potential standardization for various automated vehicle systems. When, what, and by whom the standardization activities are actually done are discussed separately.