| Name |
Description |
Abstract |
Status |
Publication date |
Edition |
Number of pages |
Technical committee |
ICS |
| ISO/TS 19082:2020 |
Intelligent transport systems — Definition of data elements and data frames between roadside modules and signal controllers for cooperative signal control |
This document specifies data elements and data frames for messages
a) exchanged between roadside modules and:
1) signal controllers,
2) traffic management centres, and/or
3) other roadside modules.
b) exchanged between traffic management centres and signal controllers.
NOTE Roadside modules can generate data based on inputs from vehicle detectors and/or probe data transmitted by vehicles. This document does not address how the roadside module generates the data; it only addresses communication after receiving and processing raw data from one or more sources.
EXAMPLE A roadside module can calculate vehicle volume, average speed, and queue length by utilizing data from vehicle detectors and probe information.
The data structure follows the framework specified in ISO 14817-1, and the data elements and data frames are described by description name, object identifier, definition, and data type following ISO 14817-1. The specifications of this document complement those from ISO/TS 19091 and other standards.
The roadside modules can be constructed in any manner using any architecture including the ITS station as described in ISO 21217, or other hardware and software constructs.
|
Published |
2020-01 |
Edition : 1 |
Number of pages : 21 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 20684-1:2021 |
Intelligent transport systems — Roadside modules SNMP data interface — Part 1: Overview |
Field devices are a key component in intelligent transport systems (ITS). Field devices include traffic signals, message signs, weather stations, traffic sensors, roadside equipment for connected ITS (C-ITS) environments, etc.
The ISO 20684 series defines data that can be used when field devices need to exchange information with other external entities (called “managers” in this document, even if they are other field devices). Field devices can be quite complex, necessitating the standardization of many data concepts for exchange. As such, the ISO 20684 series is divided into several individual parts. This document (Part 1) introduces the ISO 20684 series and provides normative content that applies to all subsequent parts.
|
Published |
2021-04 |
Edition : 1 |
Number of pages : 20 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TR 19083-1:2016 |
Intelligent transport systems — Emergency evacuation and disaster response and recovery — Part 1: Framework and concept of operation |
ISO/TR 19083-1:2016
- defines the framework for the ISO/TR 19083 series of standards related to emergency evacuation and disaster response and recovery,
- establishes the criteria under which public transport should support evacuations and disaster response and recovery based on the magnitude of the disaster and the location as these factors drive the policies, directives and plans for each countries disaster prevention/evacuation systems,
- identifies the types of agencies and organizations involved in a regionally supported evacuation and disaster,
- defines the roles and responsibilities public transport entities should provide in planning, preparing for, and conducting evacuations and disaster response and recovery efforts in support of regional authorities,
- recommends the type of information required and necessary actions to be followed by public transport to ensure efficient and effective transportation in response to recovery from a disaster,
- provides a concept of operation describing the characteristics of the EEDRR Decision Support System from the viewpoint of an individual who will use the system for public transport disaster support, it is the guiding document for public transport services operators who voluntarily wish to develop EEDRR Decision Support Systems, and
- identifies guidelines to improve coordination among regional authorities when public transport disaster support is required.
|
Published |
2016-10 |
Edition : 1 |
Number of pages : 54 |
Technical Committee |
13.200
Accident and disaster control
;
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 19091:2017 |
Intelligent transport systems — Cooperative ITS — Using V2I and I2V communications for applications related to signalized intersections |
ISO/TS 19091:2017 defines the message, data structures, and data elements to support exchanges between the roadside equipment and vehicles to address applications to improve safety, mobility and environmental efficiency. In order to verify that the defined messages will satisfy these applications, a systems engineering process has been employed that traces use cases to requirements and requirements to messages and data concepts.
This document consists of a single document that contains the base specification and a series of annexes. The base specification lists the derived information requirements (labelled informative) and references to other standards for message definitions where available. Annex A contains descriptions of the use cases addressed by this document. Annex B and Annex C contain traceability matrices that relate use cases to requirements and requirements to the message definitions (i.e. data frames and data elements). The next annexes list the base message requirements and application-oriented specific requirements (requirements traceability matrix) that map to the message and data concepts to be implemented. As such, an implementation consists of the base plus an additional group of extensions within this document.
Details on information requirements, for other than SPaT, MAP, SSM, and SRM messages are provided in other International Standards. The focus of this document is to specify the details of the SPaT, MAP, SSM, and SRM supporting the use cases defined in this document. Adoption of these messages varies by region and their adoption may occur over a significant time period.
ISO/TS 19091:2017 covers the interface between roadside equipment and vehicles. Applications, their internal algorithms, and the logical distribution of application functionality over any specific system architecture are outside the scope of this document.
|
Withdrawn |
2017-03 |
Edition : 1 |
Number of pages : 211 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 19091:2019 |
Intelligent transport systems — Cooperative ITS — Using V2I and I2V communications for applications related to signalized intersections |
This document defines the message, data structures, and data elements to support exchanges between the roadside equipment and vehicles to address applications to improve safety, mobility and environmental efficiency. In order to verify that the defined messages will satisfy these applications, a systems engineering process has been employed that traces use cases to requirements and requirements to messages and data concepts.
This document consists of a single document that contains the base specification and a series of annexes. The base specification lists the derived information requirements (labelled informative) and references to other standards for message definitions where available. Annex A contains descriptions of the use cases addressed by this document. Annexes B and C contain traceability matrices that relate use cases to requirements and requirements to the message definitions (i.e. data frames and data elements). The next annexes list the base message requirements and application-oriented specific requirements (requirements traceability matrix) that map to the message and data concepts to be implemented. As such, an implementation consists of the base plus an additional group of extensions within this document.
Details on information requirements, for other than SPaT, MAP, SSM, and SRM messages are provided in other International Standards. The focus of this document is to specify the details of the SPaT, MAP, SSM, and SRM supporting the use cases defined in this document. Adoption of these messages varies by region and their adoption can occur over a significant time period.
This document covers the interface between roadside equipment and vehicles. Applications, their internal algorithms, and the logical distribution of application functionality over any specific system architecture are outside the scope of this document.
|
Published |
2019-06 |
Edition : 2 |
Number of pages : 233 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 19299:2020 |
Electronic fee collection — Security framework |
This document defines an information security framework for all organizational and technical entities of an EFC scheme and for the related interfaces, based on the system architecture defined in ISO 17573-1. The security framework describes a set of security requirements and associated security measures.
Annex D contains a list of potential threats to EFC systems and a possible relation to the defined security requirements. These threats can be used for a threat analysis to identify the relevant security requirements for an EFC system.
The relevant security measures to secure EFC systems can then be derived from the identified security requirements.
|
Published |
2020-08 |
Edition : 1 |
Number of pages : 129 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 19299:2015 |
Electronic fee collection — Security framework |
The overall scope of ISO/TS 19299:2015 is an information security framework for all organizational and technical entities of an EFC scheme and in detail for the interfaces between them, based on the system architecture defined in ISO 17573. The security framework describes a set of requirements and associated security measures for stakeholders to implement and thus ensure a secure operation of their part of an EFC system as required for a trustworthy environment according to its security policy.
The scope of ISO/TS 19299:2015 comprises the following:
definition of a trust model;
Basic assumptions and principles for establishing trust between the stakeholders.
security requirements;
security measures - countermeasures;
Security requirements to support actual EFC system implementations.
security specifications for interface implementation;
These specifications represent an add-on for security to the corresponding standards.
key management;
Covering the (initial) setup of key exchange between stakeholders and several operational procedures like key renewal, certificate revocation, etc.
security profiles;
implementation conformance statement provides a checklist to be used by an equipment supplier, a system implementation, or an actor of a role declaring his conformity to ISO/TS 19299:2015;
general information security objectives of the stakeholders which provide a basic motivation for the security requirements;
threat analysis on the EFC system model and its assets using two different complementary methods, an attack-based analysis, and an asset-based analysis;
security policy examples;
recommendations for privacy-focused implementation;
proposal for end-entity certificates.
|
Withdrawn |
2015-10 |
Edition : 1 |
Number of pages : 137 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/FDIS 39003 |
Road traffic safety (RTS) — Guidance on ethical considerations relating to safety for autonomous vehicles |
|
Under development |
|
Edition : 1 |
Number of pages : 44 |
Technical Committee |
03.220.20
Road transport
|
| ISO/TS 19468:2019 |
Intelligent transport systems — Data interfaces between centres for transport information and control systems — Platform independent model specifications for data exchange protocols for transport information and control systems |
This document defines and specifies component facets supporting the exchange and shared use of data and information in the field of traffic and travel.
The component facets include the framework and context for exchanges, the data content, structure and relationships necessary and the communications specification, in such a way that they are independent from any defined technical platform.
This document establishes specifications for data exchange between any two instances of the following actors:
— Traffic Information Centres (TIC);
— Traffic Control Centres/Traffic Management Centres (TCC/TMC);
— Service Providers (SP).
This document can be applied for use by other actors, e.g. car park operators.
This document includes the following types of information:
— the use cases and associated requirements, and features relative to different exchange situations;
— the different functional exchange profiles;
— the abstract elements for protocols;
— the data model for exchange (informational structures, relationships, roles, attributes and associated data types required).
In order to set up a new technical exchange framework, it is necessary to associate one functional exchange profile with a technical platform providing an interoperability domain where plug-and-play interoperability at technical level can be expected. The definition of such interoperability domains is not part of this document but can be found in other standards or technical specifications, e.g. ISO 14827‑3. This document is restricted to data exchange. Definition of payload content models is beyond the scope of this document.
|
Withdrawn |
2019-10 |
Edition : 1 |
Number of pages : 120 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 19468:2022 |
Intelligent transport systems — Data interfaces between centres for transport information and control systems — Platform-independent model specifications for data exchange protocols for transport information and control systems |
This document defines and specifies component facets supporting the exchange and shared usage of data and information in the field of traffic and travel.
The component facets include the framework and context for exchanges, the data content, structure and relationships necessary and the communications specifications, in such a way that they are independent from any defined technical platform.
This document establishes specifications for data exchange between any two instances of the following actors:
— Traffic information centres (TICs);
— Traffic control centres/Traffic management centres (TCCs/TMCs);
— Service providers (SPs).
This document can also be applied for use by other actors, e.g. car park operators.
This document includes the following types of information:
— use cases and associated requirements, and features relative to different exchange situations;
— different functional exchange profiles;
— abstract elements for protocols;
— data model for exchange (informational structures, relationships, roles, attributes and associated data types required).
In order to set up a new technical exchange framework, it is necessary to associate one functional exchange profile with a technical platform providing an interoperability domain where plug-and-play interoperability at a technical level can be expected. The definition of such interoperability domains is out of scope of this document but can be found in other International Standards or Technical Specifications (e.g. the ISO 14827 series).
This document is restricted to data exchange. Definition of payload content models is out of the scope of this document.
|
Published |
2022-02 |
Edition : 2 |
Number of pages : 139 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 19638:2018 |
Intelligent transport systems — Road boundary departure prevention systems (RBDPS) — Performance requirements and test procedures |
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.
|
Published |
2018-09 |
Edition : 1 |
Number of pages : 19 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TR 19639:2015 |
Electronic fee collection — Investigation of EFC standards for common payment schemes for multi-modal transport services |
Common payment scheme for multi-modal transport services, such as toll roads and public transport, are implemented all over the world. These systems are often based on a common payment medium, e.g. IC cards, for use in more than one transport service. The aim of ISO/TR 19639:2015 is to analyse the existing set of EFC standards for their suitability for using common payment media for multi-modal transport services, where applicable identify standardisation gaps and to make proposals for such EFC standardisation projects. This includes definition of additional information to be exchanged among the related entities and to define the specific requirements for common payment scheme.
The scope of ISO/TR 19639:2015 includes:
investigation of a suitable model for EFC systems and other transport services;
identification of the required interface definitions between the EFC and the public transport services including e-money services;
identification of additional needs for additional EFC related information exchange among the related entities;
provision of guiding information to be considered in revisions of EFC standards.
The scope includes all types of EFC systems, i.e. including both DSRC based EFC and autonomous EFC systems, and both pre-pay type and post-pay type.
Service related information of both public transport and e-money are outside the scope of ISO/TR 19639:2015.
|
Published |
2015-10 |
Edition : 1 |
Number of pages : 35 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 20026:2017 |
Intelligent transport systems — Cooperative ITS — Test architecture |
ISO/TS 20026:2017 specifies an extension of the ETSI C-ITS test architecture for conformance testing of protocols and applications in ITS station units. It specifies usage of the ITS station-internal management communication protocol (IICP) for the purpose of connecting an ITS test system to an implementation under test (IUT) residing in a system under test (SUT).
|
Published |
2017-05 |
Edition : 1 |
Number of pages : 26 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 20524-1:2020 |
Intelligent transport systems — Geographic Data Files (GDF) GDF5.1 — Part 1: Application independent map data shared between multiple sources |
This document specifies the conceptual and logical data model and physical encoding formats for geographic databases for Intelligent Transport Systems (ITS) applications and services. It includes a specification of potential contents of such databases (data dictionaries for Features, Attributes and Relationships), a specification of how these contents shall be represented, and of how relevant information about the database itself may be specified (metadata).
The focus of this document is on ITS applications and services and it emphasizes road and road-related information. ITS applications and services, however, also require information in addition to road and road-related information.
EXAMPLE 1 ITS applications and services need information about addressing systems in order to specify locations and/or destinations. Consequently, information about the administrative and postal subdivisions of an area is essential.
EXAMPLE 2 Map display is an important component of ITS applications and services. For proper map display, the inclusion of contextual information such as land and water cover is essential.
EXAMPLE 3 Point-of-Interest (POI) or service information is a key feature of traveller information. It adds value to end-user ITS applications and services.
Typical ITS applications and services targeted by this document are in-vehicle or portable navigation systems, traffic management centres, or services linked with road management systems, including public transport systems.
The Conceptual Data Model has a broader focus than ITS applications and services. It is application independent, allowing for future harmonization of this document with other geographic database standards.
|
Published |
2020-03 |
Edition : 1 |
Number of pages : 1046 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 20524-2:2020 |
Intelligent transport systems — Geographic Data Files (GDF) GDF5.1 — Part 2: Map data used in automated driving systems, Cooperative ITS, and multi-modal transport |
This document specifies the conceptual and logical data model in addition to the physical encoding formats for geographic databases for Intelligent Transport Systems (ITS) applications and services. This document includes a specification of potential contents of such databases (data dictionaries for Features, Attributes and Relationships), a specification of how these contents are to be represented, and how relevant information about the database itself can be specified (metadata). This document further defines map data used in automated driving systems, Cooperative-ITS, and Multi-modal transport.
The focus of this document is firstly on emerging ITS applications and services, such as Cooperative-ITS and automated driving systems, and it emphasizes road, lane and relevant information on road and lane. However, ITS applications and services also require other information in addition to road and road-related information, which are provided as external databases to connect with GDF and to complement each other. Highly defined public transport databases, for instance, are indispensable in multi-modal transport applications and services in particular. Thus, this document focuses secondly on an expansion of the specification to connect with externally existing databases. It is particularly designed to connect a Transmodel (EN 12896-1 and EN 12896-2) conformant public transport database.
Typical ITS applications and services targeted by this document are in-vehicle or portable navigation systems, traffic management centres, or services linked with road management systems, including public transport systems.
The conceptual data model specified here has a broader focus than ITS applications and services. It is application independent, allowing for future harmonization of this model with other geographic database standards.
|
Published |
2020-11 |
Edition : 1 |
Number of pages : 589 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TR 20529-1:2017 |
Intelligent transport systems — Framework for green ITS (G-ITS) standards — Part 1: General information and use case definitions |
ISO/TR 20529-1:2017 provides the framework guideline for identifying cost-effective technologies and related standards required to deploy, manage and operate sustainable "green" intelligent transport systems (ITS) technologies in surface transportations with eco-mobility. These ITS technologies can increase operational efficiencies and unlock enhanced transportation safety and eco-mobility applications.
The green ITS standard framework builds on the existing standards and best practices of transport operation and management systems, as well as ITS applications, and aims to accommodate to the specific needs of eco-mobility in either mega cities or developing countries.
The G-ITS standards would expect to focus on the use of data exchange interface standards to enable the deployment of cloud-based multi-modal mobility solutions using wireless networks and nomadic devices. These forward-looking solutions are "infrastructure light" and thus can impact developing regions with little or no legacy transportation infrastructure.
The framework described in ISO/TR 20529-1:2017 includes:
- G-ITS standard common framework including gap analysis of existing ITS standards;
- Guidance documents to facilitate the practical implementation of identified standards by policy makers and engineers including related use cases.
ISO/TR 20529-1:2017 includes the identification of existing International Standards for ITS in ISO/TC 204 and existing vehicle communication network access standards.
|
Published |
2017-10 |
Edition : 1 |
Number of pages : 23 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 20529-2:2021 |
Intelligent transport systems — Framework for Green ITS (G-ITS) standards — Part 2: Integrated mobile service applications |
This document provides information and requirements for identifying cost-effective technologies and related standards required to deploy, manage and operate sustainable “green” ITS technologies in surface transportations with eco-mobility. These ITS technologies can increase operational efficiencies and unlock enhanced transportation safety and eco-mobility applications.
The ISO 20529 series builds on the existing standards and best practices of transport operation and management systems, as well as ITS applications, and aims to accommodate the specific needs of eco-mobility.
G-ITS standards are expected to focus on the use of data exchange interface standards to enable the deployment of cloud-based multi-modal mobility solutions using wireless networks and nomadic devices. These forward-looking solutions are “infrastructure light” and can thus impact developing regions with little or no legacy transportation infrastructure.
This document is intended to provide mobility information according to user preference on demand, utilizing a variety of existing apps on nomadic devices related to various means of transport. An integrated mobility information platform is defined in this document as a service methodology to be integrated with a variety of mobile apps with respect to different modes of transport.
The framework described in this document includes:
— Identification of implementation aspects of related standards by means of use case.
— Identification of the multi-modal transport information necessary to support G-ITS.
— Eco-friendly route guidance according to user preference.
— Smart modal choice service based on carbon footprint, fuel efficiency and carbon-free zones for G-ITS.
|
Published |
2021-11 |
Edition : 1 |
Number of pages : 64 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/DIS 20530-2 |
Intelligent transport systems — Information for emergency service support for nomadic and mobile devices — Part 2: Service requirements for vehicle incident notification |
|
Under development |
|
Edition : 1 |
Number of pages : 13 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 6855-3:2012 |
Mopeds — Measurement method for gaseous exhaust emissions and fuel consumption — Part 3: Fuel consumption measurement at a constant speed |
ISO 6855-3 specifies the methods of measurement for fuel consumption at a constant speed on the road and on the chassis dynamometer. It is applicable to mopeds as defined in ISO 3833 equipped with a spark ignition engine (four-stroke engine, two-stroke engine or rotary piston engine).
|
Published |
2012-09 |
Edition : 1 |
Number of pages : 15 |
Technical Committee |
43.140
Motorcycles and mopeds
;
13.040.50
Transport exhaust emissions
|
| ISO/TS 20684-2:2021 |
Intelligent transport systems — Roadside modules SNMP data interface — Part 2: Generalized field device basic management |
Field devices are a key component in intelligent transport systems (ITS). Field devices include traffic signals, message signs, weather stations, traffic sensors, roadside equipment for connected ITS (C-ITS) environments, etc.
Field devices often need to exchange information with other external entities (managers). Field devices can be quite complex necessitating the standardization of many data concepts for exchange. As such, the ISO 20684 series is divided into several individual parts.
This part of the ISO 20684 series identifies basic user needs for the management of virtually any field device and traces these needs to interoperable designs. This includes the ability to identify the device, its capabilities, and its status.
NOTE This document is similar to portions of NTCIP 1103 v03 and NTCIP 1201 v03.
ISO 20684-1 provides additional details about how the ISO 20684 series relates to the overall ITS architecture.
|
Published |
2021-05 |
Edition : 1 |
Number of pages : 40 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 20684-3:2022 |
Intelligent transport systems — Roadside modules SNMP data interface — Part 3: Triggers |
Field devices are a key component in intelligent transport systems (ITS). Field devices include traffic signals, message signs, weather stations, traffic sensors, roadside equipment for connected ITS (C-ITS) environments, etc.
Field devices often need to exchange information with other external entities (managers). Field devices can be quite complex, necessitating the standardization of many data concepts for exchange. As such, the ISO 20684 series is divided several individual parts.
This document specifies the needs, requirements and design for multiple mechanisms to fire triggers, which result in the device attempting to perform an action. Specific types of actions are defined in other documents and can include sending notifications (ISO/TS 20684-4), entering data into a log for later retrieval (ISO/TS 20684-5), and/or initiating SNMP-based requests (ISO/TS 20684-6).
NOTE 1 There are similarities between certain portions of NTCIP 1103 and NTCIP 1201 and this document.
NOTE 2 ISO 20684-1 provides additional details about how the ISO 20684 series relates to the overall ITS architecture.
|
Published |
2022-09 |
Edition : 1 |
Number of pages : 58 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 20684-4:2022 |
Intelligent transport systems — Roadside modules SNMP data interface — Part 4: Notifications |
Field devices are a key component in intelligent transport systems (ITS). Field devices include traffic signals, message signs, weather stations, traffic sensors, roadside equipment for connected ITS (C-ITS) environments, etc.
Field devices often need to exchange information with other external entities (managers). Field devices can be quite complex, necessitating the standardization of many data concepts for exchange. As such, the ISO 20684 series is divided several individual parts.
This document specifies the needs, requirements and design for the field device to send notifications to one or more managers. It relies upon the definition of triggers as defined in ISO/TS 20684-3.
NOTE 1 There are similarities between certain portions of NTCIP 1103 and this document.
NOTE 2 ISO 20684-1 provides additional details about how the ISO 20684 series relates to the overall ITS architecture.
|
Published |
2022-10 |
Edition : 1 |
Number of pages : 28 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 20684-5:2022 |
Intelligent transport systems — Roadside modules SNMP data interface — Part 5: Logs |
Field devices are a key component in intelligent transport systems (ITS). Field devices include traffic signals, message signs, weather stations, traffic sensors, roadside equipment for connected ITS (C-ITS) environments, etc.
Field devices often need to exchange information with other external entities (managers). Field devices can be quite complex, necessitating the standardization of many data concepts for exchange. As such, the ISO 20684 series is divided several individual parts.
This document specifies the user needs, requirements and design elements that are used to record timestamped information in a log for later retrieval. This allows a manager to determine the state of a particular object instance nearly simultaneously when the trigger action occurs without frequent polling.
NOTE 1 There are similarities between certain portions of NTCIP 1103.
NOTE 2 ISO 20684-1 provides additional details about how the ISO 20684 series relates to the overall ITS architecture.
|
Published |
2022-10 |
Edition : 1 |
Number of pages : 22 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 20684-6:2022 |
Intelligent transport systems — Roadside modules SNMP data interface — Part 6: Commands |
Field devices are a key component in intelligent transport systems (ITS). Field devices include traffic signals, message signs, weather stations, traffic sensors, roadside equipment for connected ITS (C-ITS) environments, etc.
Field devices often need to exchange information with other external entities (managers). Field devices can be quite complex, necessitating the standardization of many data concepts for exchange. As such, the ISO 20684 series is divided several individual parts.
This document specifies the user needs, requirements and design elements that are used to issue an SNMP set-request in response to a trigger firing. This allows a manager to configure the field device to implement simple responses to conditions in the field.
NOTE 1 There are similarities between certain portions of the Event MIB defined in IETF RFC 2981 and this document.
NOTE 2 ISO 20684-1 provides additional details about how the ISO 20684 series relates to the overall ITS architecture.
|
Published |
2022-09 |
Edition : 1 |
Number of pages : 16 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 20684-7:2022 |
Intelligent transport systems — Roadside modules SNMP data interface — Part 7: Support features |
Field devices are a key component in intelligent transport systems (ITS). Field devices include traffic signals, message signs, weather stations, traffic sensors, roadside equipment for connected ITS (C-ITS) environments, etc.
Field devices often need to exchange information with other external entities (managers). Field devices can be quite complex, necessitating the standardization of many data concepts for exchange. As such, the ISO 20684 series is divided several individual parts.
This document specifies user needs, requirements and design elements that are normatively used by other parts of the ISO 20684 series. Specifically, it defines an internal field device clock, a mechanism for grouping object values together to provide for more efficient transfer of data, and it provides formal requirements for the SNMP target and target parameters as defined in IETF RFC 3413.
NOTE 1 There are similarities between certain portions of NTCIP 1103 and NTCIP 1201 and this document.
NOTE 2 ISO 20684-1 provides additional details about how the ISO 20684 series relates to the overall ITS architecture.
|
Published |
2022-10 |
Edition : 1 |
Number of pages : 43 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 20684-10:2021 |
Intelligent transport systems — Roadside modules SNMP data interface — Part 10: Variable message signs |
Variable message signs (VMSs) are installed in areas where traffic managers identify a frequent need to convey information to the travelling public, such as upstream from interchanges to alert the public to downstream congestion in time for them to alter their routes. This allows traffic managers to improve the efficiency, safety, and quality of traveller journeys.
In order to manage the operation of a VMS and the messages displayed, information exchange between the management systems and the VMS is needed.
This document identifies basic user needs for the management of light-emitting diode (LED) matrix VMSs and traces these needs to interoperable designs. This includes the ability to identify the device, its capabilities, and its status.
NOTE 1 This document is similar to portions of NTCIP 1203 v03, which defines how to manage VMSs using an older version of SNMP and is a normative reference in this document.
NOTE 2 ISO 20684-1 provides additional details about how this series of standards relates to the overall ITS architecture.
|
Published |
2021-04 |
Edition : 1 |
Number of pages : 27 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 21185:2019 |
Intelligent transport systems — Communication profiles for secure connections between trusted devices |
This document specifies a methodology to define ITS-S communication profiles (ITS-SCPs) based on standardized communication protocols to interconnect trusted devices. These profiles enable secure information exchange between such trusted devices, including secure low-latency information exchange, in different configurations. The present document also normatively specifies some ITS-SCPs based on the methodology, yet without the intent of covering all possible cases, in order to exemplify the methodology.
Configurations of trusted devices for which this document defines ITS-SCPs include:
a) ITS station communication units (ITS-SCU) of the same ITS station unit (ITS-SU), i.e. station-internal communications;
b) an ITS-SU and an external entity such as a sensor and control network (SCN), or a service in the Internet;
c) ITS-SUs.
Other ITS-SCPs can be specified at a later stage.
The specifications given in this document can also be applied to unsecured communications and can be applied to groupcast communications as well.
|
Published |
2019-10 |
Edition : 1 |
Number of pages : 20 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TR 21190:2018 |
Electronic fee collection — Investigation of charging policies and technologies for future standardization |
This document investigates the stemming from requirements of charging policies and corresponding charging technologies in order to propose future standardization theme candidates.
This document reports the findings of the investigation of charging policies and technologies in order to:
— Classify the conventional charging policies and the new charging policies and their functional requirements.
— Classify the existing technologies and the emerging technologies to be used for EFC services or other intelligent transport system (ITS) services.
— Conduct a gap analysis between the needs of the new charging policies and the existing standardized technologies for EFC.
— Recommend development of emerging standards or amendments for existing EFC standards according to the results of the gap analysis.
|
Published |
2018-12 |
Edition : 1 |
Number of pages : 65 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 21192:2019 |
Electronic fee collection — Support for traffic management |
This document identifies the architecture of a toll system environment in which a toll charger (TC) can act to support traffic management with the use of a tariff scheme.
The scope of this document defines:
— the architecture related to the scope;
— a standard framework and data flow model;
— an exchange of information between a TC and a road and traffic manager (RTM), e.g.:
— level of service (LOS);
— tariff scheme;
— data which is needed to support traffic management (vehicle probe and traffic flow data).
This document is a toolbox standard of application protocol data units (APDUs), which can be used for the assigned purpose. The detailed definitions of mandatory and optional elements in real implementation are outside the scope of this document. This document does not define communication stacks or timings.
Data types and associated coding related to the data elements described in Clause 6 are defined in Annex A, using the abstract syntax notation one (ASN.1) according to ISO/IEC 8824-1. This document allows the implementer to define suitable protocol procedures such as basic interaction, protocol mechanism, and choice of transfer protocol.
|
Published |
2019-10 |
Edition : 1 |
Number of pages : 35 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 21193:2019 |
Electronic fee collection — Requirements for EFC application interfaces on common media |
This document defines requirements to support information exchanges among related entities of a common payment scheme. It defines:
a) electronic fee collection (EFC) functional requirements for a common payment medium;
b) an application structure in a common payment medium;
c) EFC application data in a common payment medium.
The following are outside the scope of this document:
— requirements and data definitions for any other transport services such as public transport;
— a complete risk assessment for an EFC system using a common payment medium;
— security issues arising from an EFC application among all transport services;
— the technical trust relationship between a CSRP and a service user;
— concrete implementation specifications for implementation of security for an EFC system;
— detailed specifications required for privacy-friendly EFC implementations;
— any financial transactions of the CSRP.
|
Published |
2019-10 |
Edition : 1 |
Number of pages : 40 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 21202:2020 |
Intelligent transport systems — Partially automated lane change systems (PALS) — Functional / operational requirements and test procedures |
This document contains the basic control strategy, minimum functionality requirements, basic driver interface elements, minimum requirements for reaction to failure, and performance test procedures for PALS.
PALS perform part or all of lane change tasks under the driver's initiation and supervision. PALS are intended to function on roads with visible lane markings, where non-motorized vehicles and pedestrians are prohibited (e.g. access controlled highway), and to perform a lane change into a lane with traffic moving in the same direction. Support on sections of roadway with temporary or irregular lane markings (such as roadwork zones) is not within the scope of this document.
This document does not describe functionalities based on combinations with longitudinal control systems such as those standardized in ISO 22839 (FVCMS) or ISO 15622 (ACC).
The driver always assumes responsibility for this system and the driver's decisions and operations take priority at all times.
Use of PALS is intended for light-duty and heavy-duty vehicles (heavy trucks and buses).
This document does not address any functional or performance requirements for detection sensors, nor any communication links for co-operative solutions.
|
Published |
2020-04 |
Edition : 1 |
Number of pages : 13 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 21219-1:2023 |
Intelligent transport systems — Traffic and travel information (TTI) via transport protocol experts group, generation 2 (TPEG2) — Part 1: Introduction, numbering and versions (TPEG2-INV) |
This document defines an index to the complete set of TPEG Generation 2 toolkit components and applications. New applications are enumerated with an application identification (AID) as they are added to the TPEG applications family.
NOTE 1 This document will be updated when new applications occur in order to indicate the latest status and the inter-working of the various TPEG specifications. This document will be revised as a new edition every time a new issue of any other specification is issued.
NOTE 2 Preliminary AIDs are allocated and managed by TISA and are listed at Reference.
|
Published |
2023-03 |
Edition : 1 |
Number of pages : 9 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 21219-1:2016 |
Intelligent transport systems — Traffic and travel information (TTI) via transport protocol experts group, generation 2 (TPEG2) — Part 1: Introduction, numbering and versions (TPEG2-INV) |
ISO/TS 21219-1:2016 defines an index to the complete set of TPEG Generation 2 toolkit components and applications. New applications are enumerated with an Application Identification (AID) as they are added to the TPEG applications family.
ISO/TS 21219-1:2016 will be updated when such developments occur, to indicate the latest status and the inter-working of the various TPEG specifications. It will be issued as a new editorial version every time a new issue of any other specification is issued. Preliminary AIDs are allocated and managed by TISA and are listed on the TISA homepage www.tisa.org.
|
Withdrawn |
2016-05 |
Edition : 1 |
Number of pages : 9 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 21219-17 |
Intelligent transport systems — Traffic and travel information via transport protocol experts group, generation 2 (TPEG2) — Part 17: Speed information (TPEG2-SPI) |
|
Under development |
2023-05 |
Edition : 1 |
|
Technical Committee |
03.220.01
Transport in general
;
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 21719-3:2021 |
Electronic fee collection — Personalization of on-board equipment (OBE) — Part 3: Using integrated circuit(s) cards |
This document specifies:
personalization interface;
physical systems: on-board equipment (OBE), personalization equipment (PE) and integrated circuit(s) cards (ICCs);
electronic fee collection (EFC) personalization functions between the PE and the OBE in accordance with ISO/TS 21719-1 when using an ICC;
data and security elements that are transferred between the PE and the OBE using the ICC.
It is outside the scope of this document to define:
conformance procedures and test specifications;
setting-up of operating organizations (e.g. toll service provider, personalization agent, trusted third party, etc.);
legal issues;
the exact commands and security functionality within ISO/IEC 7816-4 used by the PE and the OBE, respectively, to interface an ICC.
NOTE Some of the issues that are outside the scope of this document are the subject of separate standards prepared by CEN/TC 278 and ISO/TC 204.
|
Published |
2021-11 |
Edition : 1 |
Number of pages : 16 |
Technical Committee |
03.220.20
Road transport
|
| ISO/CD 21219-21 |
Intelligent transport systems — Traffic and travel information via transport protocol experts group, generation 2 (TPEG2) — Part 21: Geographic location referencing (TPEG-GLR) |
ISO/TS 21219-21:2018 defines a method of using geographic location referencing (GLR) that can be used by relevant TPEG applications. The GLR type is defined in this document. It is used for defining geographic location references (points, polylines, and geographical areas). The GLR method is intended to be one of the methods that can be transported inside a TPEG-location referencing container (TPEG-LRC) for those TPEG applications providing information for primarily geographical locations (e.g. weather).
The GLR specification is kept basic and compact on purpose, such that it can also be employed advantageously in non-navigation devices for simple TPEG services such as weather information, safety alerts, etc. As such, the GLR location referencing method is intended to be complementary to map-related location referencing methods, where the focus rather is on the referencing of man-made artefacts such as roads and highways.
The scope of GLR is limited to geographic locations on the Earth's surface for the above-mentioned rationale.
|
Under development |
|
Edition : 1 |
|
Technical Committee |
03.220.01
Transport in general
;
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TR 21707:2008 |
Intelligent transport systems — Integrated transport information, management and control — Data quality in ITS systems |
ISO/TR 21707:2008 specifies a set of standard terminology for defining the quality of data being exchanged between data suppliers and data consumers in the ITS domain. This applies to Traffic and Travel Information Services and Traffic Management and Control Systems, specifically where open interfaces exist between systems. It may of course be applicable for other types of interfaces, including internal interfaces, but this Technical Report is aimed solely at open interfaces between systems.
ISO/TR 21707:2008 identifies a set of parameters or meta-data such as accuracy, precision and timeliness etc. which can give a measure of the quality of the data exchanged and the overall service on an interface. Data quality is applicable to interfaces between any data supplier and data consumer, but is vitally important on open interfaces. It includes the quality of the service as a whole or any component part of the service that a supplying or publishing system can provide. For instance this may give a measure of the availability and reliability of the data service in terms of uptime against downtime and the responsiveness of the service or it may give a measure of the precision and accuracy of individual attributes in the published data.
It should be noted that in the context of ISO/TR 21707:2008 data may be taken to be either raw data as initially collected, or as processed data, both of which may be made available via an interface to data consumers. The data consumer may be internal or external to the organisation which is making the data available. Additionally the data may be derived from real time data (e.g. live traffic event data, traffic measurement data or live camera images) or may be static data which has been derived and validated off-line (e.g. a location table defining a network). Measurements of data quality are of importance in all such cases.
ISO/TR 21707:2008 is suitable for application to all open ITS interfaces in the Traffic and Travel Information Services domain and the Traffic Management and Control Systems domain.
|
Published |
2008-06 |
Edition : 1 |
Number of pages : 13 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 21717:2018 |
Intelligent transport systems — Partially Automated In-Lane Driving Systems (PADS) — Performance requirements and test procedures |
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 Partially Automated In-Lane Driving Systems (PADS).
This document is applicable to passenger cars, commercial vehicles and buses. It is not applicable to automated driving systems of level 3 or higher (as defined in SAE J3016:2016).
|
Published |
2018-09 |
Edition : 1 |
Number of pages : 11 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 21719-1:2018 |
Electronic fee collection — Personalization of on-board equipment (OBE) — Part 1: Framework |
ISO/TS 21719-1:2018 describes:
- an overall description of the EFC personalization process;
- a description of EFC functionality that can be used for personalization.
The personalization process takes place within the domain of the entity that is responsible for the application in the OBE.
|
Published |
2018-02 |
Edition : 1 |
Number of pages : 9 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 21719-2:2018 |
Electronic fee collection — Personalization of on-board equipment (OBE) — Part 2: Using dedicated short-range communication |
ISO/TS 21719-2:2018 specifies
- personalization interface: dedicated short-range communication (DSRC),
- physical systems: on-board equipment and the personalization equipment,
- DSRC-link requirements,
- EFC personalization functions according to ISO/TS 21719-1 when defined for the DSRC interface, and
- security data elements and mechanisms to be used over the DSRC interface.
Protcol information conformance statement (PICS) proforma is provided in Annex B, whereas security computation examples are provided in Annex E.
|
Withdrawn |
2018-02 |
Edition : 1 |
Number of pages : 39 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 21719-2:2022 |
Electronic fee collection — Personalization of on-board equipment (OBE) — Part 2: Using dedicated short-range communication |
This document defines:
— personalization interface: dedicated short-range communication (DSRC),
— physical systems: on-board equipment and the personalization equipment,
— DSRC-link requirements,
— EFC personalization functions according to ISO/TS 21719-1 when defined for the DSRC interface, and
— security data elements and mechanisms to be used over the DSRC interface.
A protocol information conformance statement (PICS) proforma is provided in Annex B, and security computation examples are provided in Annex E.
It is outside the scope of this document to define:
— conformance procedures and test specifications,
— setting-up of operating organizations (e.g. toll service provider, personalization agent, trusted third party), and
— legal issues.
NOTE Some of these issues are subject to separate standards prepared by ISO/TC 204, CEN/TC 278 or ETSI ERM.
|
Published |
2022-10 |
Edition : 2 |
Number of pages : 37 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TR 21724-1:2020 |
Intelligent transport systems — Common Transport Service Account Systems — Part 1: Framework and use cases |
This document describes the characteristics of a Common Transport Service Account System (CTSA). It presents the common transport service account framework and associated use cases. The objective of the CTSA role model is to cover relevant transport services, the payment methods, the account types where the user of the service is charged for the service and that requires a more overall role and responsibilities model. The model also defines external stakeholders that impact and border the model, that is, the general financial (banking) system. The framework assumes an account-based system where charges for services are calculated and charged in the account system. The main idea behind the CTSA framework is to provide a transport service user with the benefit of seamless acquisition of access rights to multiple transport services by multiple service / operator managers through a common transport account. This framework assumes a technology-agnostic front end with respect to the payment media and reading equipment. The focus of this framework is the back-office / account management system as a vehicle to integrate multiple transport services and managers.
A new set of terms are introduced in this document to distinguish the convergence of a common approach for payment for transportation services from more traditional models using "smart cards" or electronic tickets. The model describes a move towards common or linked mobility accounts for all traveller payment needs, whether for parking, tolls, public transport and other disruptive mode options (e.g., bikeshare, carshare, microtransit, micromobility), inclusive of commercial payment and benefit models.
|
Published |
2020-07 |
Edition : 1 |
Number of pages : 32 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 21734-1:2022 |
Intelligent transport systems — Performance testing for connectivity and safety functions of automated driving buses in public transport — Part 1: General framework |
This document specifies the general framework and the automated driving bus (ADB) system components for operating ADBs in public transport networks, including:
a) the general framework and the operation scheme for public transport systems in cooperation with ADBs;
b) definitions of system components for operating ADBs; and
c) definitions of functions and requirements of each system component for providing transport services with ADBs.
This document is applicable to bodies in public transport systems and services including transportation operators, public transport governing authorities and relevant industries.
|
Published |
2022-11 |
Edition : 1 |
Number of pages : 35 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/CD TR 21734-3 |
Public transport — Performance testing for connectivity and safety functions of automated driving bus — Part 3: Service framework and use cases |
|
Under development |
|
Edition : 1 |
|
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/DTS 22726-1 |
Intelligent transport systems — Dynamic data and map database specification for connected and automated driving system applications — Part 1: Architecture and logical data model for harmonization of static map data |
|
Under development |
|
Edition : 1 |
Number of pages : 146 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/SAE PAS 22736:2021 |
Taxonomy and definitions for terms related to driving automation systems for on-road motor vehicles |
This document describes [motor] vehicle driving automation systems that perform part or all of the dynamic driving task (DDT) on a sustained basis. It provides a taxonomy with detailed definitions for six levels of driving automation, ranging from no driving automation (Level 0) to full driving automation (Level 5), in the context of [motor] vehicles (hereafter also referred to as “vehicle” or “vehicles”) and their operation on roadways:
Level 0: No Driving Automation
Level 1: Driver Assistance
Level 2: Partial Driving Automation
Level 3: Conditional Driving Automation
Level 4: High Driving Automation
Level 5: Full Driving Automation
These level definitions, along with additional supporting terms and definitions provided herein, can be used to describe the full range of driving automation features equipped on [motor] vehicles in a functionally consistent and coherent manner. “On‑road” refers to publicly accessible roadways (including parking areas and private campuses that permit public access) that collectively serve all road users, including cyclists, pedestrians, and users of vehicles with and without driving automation features.
The levels apply to the driving automation feature(s) that are engaged in any given instance of on-road operation of an equipped vehicle. As such, although a given vehicle may be equipped with a driving automation system that is capable of delivering multiple driving automation features that perform at different levels, the level of driving automation exhibited in any given instance is determined by the feature(s) that are engaged.
This document also refers to three primary actors in driving: the (human) user, the driving automation system, and other vehicle systems and components. These other vehicle systems and components (or the vehicle in general terms) do not include the driving automation system in this model, even though as a practical matter a driving automation system may actually share hardware and software components with other vehicle systems, such as a processing module(s) or operating code.
The levels of driving automation are defined by reference to the specific role played by each of the three primary actors in performance of the DDT and/or DDT fallback. “Role” in this context refers to the expected role of a given primary actor, based on the design of the driving automation system in question and not necessarily to the actual performance of a given primary actor. For example, a driver who fails to monitor the roadway during engagement of a Level 1 adaptive cruise control (ACC) system still has the role of driver, even while s/he is neglecting it.
Active safety systems, such as electronic stability control (ESC) and automatic emergency braking (AEB), and certain types of driver assistance systems, such as lane keeping assistance (LKA), are excluded from the scope of this driving automation taxonomy because they do not perform part or all of the DDT on a sustained basis, but rather provide momentary intervention during potentially hazardous situations. Due to the momentary nature of the actions of active safety systems, their intervention does not change or eliminate the role of the driver in performing part or all of the DDT, and thus are not considered to be driving automation, even though they perform automated functions. In addition, systems that inform, alert, or warn the driver about hazards in the driving environment are also outside the scope of this driving automation taxonomy, as they neither automate part or all of the DDT, nor change the driver’s role in performance of the DDT (see 8.13).
It should be noted, however, that crash avoidance features, including intervention-type active safety systems, may be included in vehicles equipped with driving automation systems at any level. For automated driving system (ADS) features (i.e., Levels 3 to 5) that perform the complete DDT, crash mitigation and avoidance capability is part of ADS functionality (see also 8.13).
|
Published |
2021-08 |
Edition : 1 |
Number of pages : 40 |
Technical Committee |
01.040.03
Services. Company organization, management and quality. Administration. Transport. Sociology. (Vocabularies)
;
01.040.35
Information technology (Vocabularies)
;
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 22737:2021 |
Intelligent transport systems — Low-speed automated driving (LSAD) systems for predefined routes — Performance requirements, system requirements and performance test procedures |
This document specifies:
— requirements for the operational design domain,
— system requirements,
— minimum performance requirements, and
— performance test procedures
for the safe operation of low-speed automated driving (LSAD) systems for operation on predefined routes. LSAD systems are designed to operate at Level 4 automation (see ISO/SAE PAS 22736), within specific operational design domains (ODD).
This document applies to automated driving system-dedicated vehicles (ADS-DVs) and can also be utilized by dual-mode vehicles (see ISO/SAE PAS 22736). This document does not specify sensor technology present in vehicles driven by LSAD systems.
|
Published |
2021-07 |
Edition : 1 |
Number of pages : 43 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 22741-1:2022 |
Intelligent transport systems — Roadside modules AP-DATEX data interface — Part 1: Overview |
Field devices are a key component in intelligent transport systems (ITS). Field devices include traffic signals, message signs, weather stations, traffic sensors, roadside equipment for connected ITS (C-ITS) environments, etc.
Field devices often need to exchange information with other external entities. Field devices can be quite complex, necessitating the standardization of many data concepts for exchange. As such, the ISO 22741 series is divided into several individual Parts. This document (Part 1) introduces the ISO 22741 series and provides normative content that applies to the rest of the series.
|
Published |
2022-02 |
Edition : 1 |
Number of pages : 8 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/CD TS 22741-10 |
Intelligent transport systems — Roadside modules AP-DATEX data interface — Part 10: Variable message signs |
|
Under development |
|
Edition : 1 |
|
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TR 23049:2018 |
Road Vehicles — Ergonomic aspects of external visual communication from automated vehicles to other road users |
The purpose of this document is to provide guidance for developers of visual external communication systems for automated vehicles (AV), particularly Automated Driving System ? Dedicated Vehicles (ADS-DV), as defined by SAE J3016.
The main objective of this document is to propose how ADS-DVs could communicate with other road users via an external communication system. It discusses the interaction between humans and ADS-DVs within roadway environments. Recommendations for the type of external visual communication messaging are presented along with the supporting methodological rationale.
This document does not address functionality elements of the ADS-DV external visual communication system itself. Rather, it serves to propose how the system communicates to human users such that it can be learned and understood by society at large.
|
Published |
2018-09 |
Edition : 1 |
Number of pages : 7 |
Technical Committee |
43.020
Road vehicles in general
;
03.220.20
Road transport
|
| ISO/FDIS 23374-1 |
Intelligent transport systems — Automated valet parking systems (AVPS) — Part 1: System framework, requirements for automated driving and for communications interface |
|
Under development |
|
Edition : 1 |
Number of pages : 153 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/DTS 23374-2 |
Intelligent transport systems — Automated valet parking systems (AVPS) — Part 2: Security integration for type 3 AVP |
This document specifies security means and procedures for AVPS Type 3 specified in ISO 23374-1 and focuses on the operation interfaces and management interfaces as defined in ISO 23374-1
|
Under development |
|
Edition : 1 |
|
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 23375:2023 |
Intelligent transport systems — Collision evasive lateral manoeuvre systems (CELM) — Requirements and test procedures |
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 and heavy trucks. Vehicles equipped with trailers are not within the scope of this document.
|
Published |
2023-02 |
Edition : 1 |
Number of pages : 31 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 23792-1 |
Intelligent transport systems — Motorway chauffeur systems (MCS) — Part 1: Framework and general requirements |
|
Under development |
|
Edition : 1 |
|
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/CD 23793-1 |
Intelligent transport systems — Minimal Risk Maneuver (MRM) for automated driving — Part 1: Framework, straight-stop and in-lane stop |
|
Under development |
|
Edition : 1 |
|
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/IEC TS 24192-1:2021 |
Cards and security devices for personal identification — Communication between contactless readers and fare media used in public transport — Part 1: Implementation requirements for ISO/IEC 14443 (all parts) |
This document defines the technical requirements to be met by contactless public transport (PT) devices in order to be able to interface together using the ISO/IEC 14443 (all parts) contactless communications protocol.
This document applies to PT devices:
— PT readers which are contactless fare management system terminals acting as a PCD contactless reader based on ISO/IEC 14443 (all parts);
— PT objects which are contactless fare media acting as a PICC contactless object based on ISO/IEC 14443 (all parts).
This document addresses interoperability of consumer-market NFC mobile devices, compliant to NFC Forum specifications, with above mentioned PT devices, aligns with ISO/IEC 14443 (all parts) and does not seek to limit compliance for PT readers with EMV Contactless Interface Specification.
|
Published |
2021-05 |
Edition : 1 |
Number of pages : 30 |
Technical Committee |
03.220.20
Road transport
;
35.240.15
Identification cards. Chip cards. Biometrics
;
35.240.60
IT applications in transport
|
| ISO/TS 24530-3:2006 |
Traffic and Travel Information (TTI) — TTI via Transport Protocol Experts Group (TPEG) Extensible Markup Language (XML) — Part 3: tpeg-rtmML |
ISO/TS 24530-3:2006 establishes the XML encoding of the method of the Road Traffic Message application.
|
Published |
2006-04 |
Edition : 1 |
Number of pages : 52 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/DTR 5262 |
Motorcycles — Guideline for verification of total running resistance force during mode running on a chassis dynamometer |
|
Under development |
|
Edition : 1 |
Number of pages : 15 |
Technical Committee |
43.140
Motorcycles and mopeds
|
| ISO/IEC TS 24192-2:2021 |
Cards and security devices for personal identification — Communication between contactless readers and fare media used in public transport — Part 2: Test plan for ISO/IEC 14443 (all parts) |
This document lists all the test conditions to be performed on a PT reader or a PT object in order to ensure that all the requirements specified in ISO/IEC TS 24192-1 are met for the PT device under test.
This document applies to PT devices only:
— PT readers which are contactless fare management system terminals acting as a PCD contactless reader based on ISO/IEC 14443 (all parts);
— PT objects which are contactless fare media acting as a PICC contactless object based on ISO/IEC 14443 (all parts).
This document applies solely to the contactless communication layers described in ISO/IEC 14443 (all parts). Application-to-application exchanges executed once contactless communication has been established at RF level fall outside the scope of this document. However, a test application is used to make end-to-end transactions during tests on the RF communication layer.
This document does not duplicate the contents of ISO/IEC 14443 (all parts) or ISO/IEC 10373‑6. It makes reference to the ISO/IEC 10373‑6 applicable test methods, specifies the test conditions to be used and describes the additional specific test conditions that can be run.
|
Published |
2021-05 |
Edition : 1 |
Number of pages : 23 |
Technical Committee |
03.220.20
Road transport
;
35.240.15
Identification cards. Chip cards. Biometrics
;
35.240.60
IT applications in transport
|
| ISO/CD 24298 |
Intelligent transport systems — Public transport — Light emitting diode (LED) destination board system for public transport buses |
|
Under development |
|
Edition : 1 |
|
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/CD 24311 |
Intelligent transport systems — Urban ITS — 'Controlled zone' management for UVARs using C-ITS |
This document provides information and specifications enabling management of road traffic in controlled zones applying geofencing. Specifically, this document provides
— a “Controlled Zone Data Dictionary” (CZDD) for management of controlled zones providing an extendible toolkit that regulators can use e.g. to inform potential CZ users, e.g. vehicles, about
— the CZ area, i.e. the geographical boundaries of the CZ;
— CZ access conditions including exempts;
— time windows indicating when these CZ access conditions are applicable, allowing the potential CZ users to select an appropriate routing, either by pre-trip planning or ad hoc re-routing,
— and illustrations and guidelines on how to use this toolkit.
The toolkit is designed in compliance with the general ITS station and communications architecture specified in ISO 21217 [8], and optionally applicable C-ITS protocols and procedures, e.g. ISO 22418:2018 [10] on “Service Announcement”, EN ISO 18750 on the “Local Dynamic Map”, and EN ISO 17419 [5] on globally unique identifiers.
Enforcement is out of scope of this document.
|
Under development |
|
Edition : 1 |
|
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TR 24529:2008 |
Intelligent transport systems — Systems architecture — Use of unified modelling language (UML) in ITS International Standards and deliverables |
ISO/TR 24529:2008 deals with the use of UML within International Standards, Technical Specifications and Technical Reports and related documents.
It discusses the application of the Unified Modelling Language (UML) to the development of standards within the context of Intelligent Transport Systems (ITS).
|
Published |
2008-04 |
Edition : 1 |
Number of pages : 14 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 24530-1:2006 |
Traffic and Travel Information (TTI) — TTI via Transport Protocol Experts Group (TPEG) Extensible Markup Language (XML) — Part 1: Introduction, common data types and tpegML |
ISO/TS 24530-1:2006 establishes the top-level "containers" for TPEG messages in XML and the common data types that are used by tpegML applications (e.g. tpeg-ptiML). Inherently, tpegML is designed to "map" the TPEG binary (ISO/TS 18234 series), however, additional tags are provided to create a message and message set structure to facilitate internet file delivery.
|
Published |
2006-04 |
Edition : 1 |
Number of pages : 12 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 24530-2:2006 |
Traffic and Travel Information (TTI) — TTI via Transport Protocol Experts Group (TPEG) Extensible Markup Language (XML) — Part 2: tpeg-locML |
ISO/TS 24530-2:2006 establishes the XML encoding of the method of Location Referencing used by TPEG applications.
TPEG applications contain the information required by a client TPEG decoder (i.e. both Location Referencing and event information), to present all the information intended for the end-user when it was originated by the service provider.
Location Referencing requires a service provider to give an impression or image, to the human end-user, of where an event has taken place. This cannot be done easily because the human end-user may or may not be familiar with the location. tpeg-loc has the added challenge of attempting to be as language independent as possible. This is achieved by the use of tpeg-loc tables (essentially word-oriented data object dictionaries).
|
Published |
2006-04 |
Edition : 1 |
Number of pages : 40 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 10054:1998 |
Internal combustion compression-ignition engines — Measurement apparatus for smoke from engines operating under steady-state conditions — Filter-type smokemeter |
|
Published |
1998-09 |
Edition : 1 |
Number of pages : 16 |
Technical Committee |
43.180
Diagnostic, maintenance and test equipment
;
13.040.50
Transport exhaust emissions
|
| ISO/TS 24530-4:2006 |
Traffic and Travel Information (TTI) — TTI via Transport Protocol Experts Group (TPEG) Extensible Markup Language (XML) — Part 4: tpeg-ptiML |
ISO/TS 24530-4:2006 establishes the XML encoding of the method of the Public Transport Information application.
The Public Transport Information application is intended to cover all modes of public (i.e. collective) transport as well as inter-urban and intra-urban travel. The application itself is designed to allow the efficient and language-independent transmission of public transport information either directly to an end-user, be it the public or another service provider, such as broadcasters, service operators or other information disseminating points, or to centres for onward transmission.
|
Published |
2006-04 |
Edition : 1 |
Number of pages : 31 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 24533:2012 |
Intelligent transport systems — Electronic information exchange to facilitate the movement of freight and its intermodal transfer — Road transport information exchange methodology |
ISO/TS 24533:2012 specifies the data concepts applicable to the movement of freight and its intermodal transfer. These data concepts include information entities (data elements), aggregated/associated information entities (groups of data elements) and messages that comprise information exchanges at transport interfaces along the chain of participants responsible for the delivery of goods from the point of origin through to the final recipient. ISO/TS 24533 focuses on a single "thread" of the overall end-to-end supply chain.
|
Published |
2012-07 |
Edition : 1 |
Number of pages : 66 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
;
55.180.01
Freight distribution of goods in general
|
| ISO 24534-1:2010 |
Automatic vehicle and equipment identification — Electronic registration identification (ERI) for vehicles — Part 1: Architecture |
ISO 24534-1:2010 provides requirements for electronic registration identification (ERI) that are based on an identifier assigned to a vehicle (e.g. for recognition by national authorities), suitable to be used for:
electronic identification of local and foreign vehicles by national authorities;
vehicle manufacturing, in-life maintenance and end-of-life identification (vehicle life cycle management);
adaptation of vehicle data (e.g. for international resales);
safety-related purposes;
crime reduction;
commercial services.
It adheres to privacy and data protection regulations.
ISO 24534-1:2010 provides an overview of the ERI system concept, in terms of the onboard vehicle components and the external off-vehicle components required for an operational system. The detailed requirements are defined in Parts 2, 3, 4 and 5 of ISO 24534 and more limited, though relevant, provisions are defined in ISO 24535.
|
Published |
2010-07 |
Edition : 1 |
Number of pages : 8 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 24534-1:2007 |
Automatic vehicle and equipment identification — Electronic Registration Identification (ERI) for vehicles — Part 1: Architecture |
ISO TS 24534-1:2007 provides the requirements for electronic registration that is based on an identifier assigned to a vehicle (e.g. for recognition by national authorities), suitable to be used for :
electronic identification of local and foreign vehicles by national authorities,
vehicle manufacturing, in-life maintenance and end-of-life identification (vehicle life cycle management),
adaptation of vehicle data (e.g. for international resales),
safety-related purposes,
crime reduction, and
commercial services.
It adheres to privacy and data protection regulations
ISO TS 24534-1:2007 provides an overview of the ERI system concept, in terms of the onboard vehicle components and the external off-vehicle components required for an operational system.
|
Withdrawn |
2007-12 |
Edition : 1 |
Number of pages : 9 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 24534-2:2010 |
Automatic vehicle and equipment identification — Electronic registration identification (ERI) for vehicles — Part 2: Operational requirements |
ISO 24534-2:2010 provides requirements for electronic registration identification (ERI) that are based on an identifier assigned to a vehicle (e.g. for recognition by national authorities) suitable to be used for:
electronic identification of local and foreign vehicles by national authorities;
vehicle manufacturing, in-life maintenance and end-of-life identification (vehicle life cycle management);
adaptation of vehicle data (e.g. for international resales);
safety-related purposes;
crime reduction;
commercial services.
It adheres to privacy and data protection regulations.
ISO 24534-2:2010 defines the operational requirements for the remaining parts of ISO 24534 and the more limited but relevant provisions of ISO 24535.
Whilst the definition of the organizational framework required to implement, operate and maintain an ERI system is outside the scope of ISO 24534-2:2010, a list of potential stakeholders in the public and private sector has been included.
|
Published |
2010-07 |
Edition : 1 |
Number of pages : 17 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 789-4:1986 |
Agricultural tractors — Test procedures — Part 4: Measurement of exhaust smoke |
This second edition cancals and replaces the first edition (1982). This part is the fourth of a series of eight. Specifies a method of measuring the smoke emiited by the engines of tractors operating at a steady speed. Annex A gives characteristics of opacimeters; installation and use of theopacimeter is described in annex B; annex C tabulates reference fuel specifications; annex D includes an specimen test report.
|
Published |
1986-10 |
Edition : 2 |
Number of pages : 7 |
Technical Committee |
13.040.50
Transport exhaust emissions
;
65.060.10
Agricultural tractors and trailed vehicles
|
| ISO/TS 24534-2:2007 |
Automatic vehicle and equipment identification — Electronic Registration Identification (ERI) for vehicles — Part 2: Operational requirements |
ISO TS 24534-2:2007 provides the requirements for Electronic registration that are based on an identifier assigned to a vehicle (e.g. for recognition by national authorities), suitable to be used for :
electronic identification of local and foreign vehicles by national authorities,
vehicle manufacturing, in-life-maintenance and end-of-life identification (vehicle life cycle management),
adaptation of vehicle data (e.g. for international resales),
safety-related purposes,
crime reduction, and
commercial services.
It adheres to privacy and data protection regulations.
ISO TS 24534-2:2007 defines the operational requirements for the remaining parts of TS 24534 and the more limited, but relevant provisions of ISO TS 24535.
|
Withdrawn |
2007-12 |
Edition : 1 |
Number of pages : 17 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 24534-3:2010 |
Automatic vehicle and equipment identification — Electronic registration identification (ERI) for vehicles — Part 3: Vehicle data |
ISO 24534-3:2010 provides requirements for electronic registration identification (ERI) that are based on an identifier assigned to a vehicle (e.g. for recognition by national authorities) suitable to be used for:
electronic identification of local and foreign vehicles by national authorities;
vehicle manufacturing, in-life maintenance and end-of-life identification (vehicle life cycle management);
adaptation of vehicle data (e.g. for international resales);
safety-related purposes;
crime reduction;
commercial services.
It adheres to privacy and data protection regulations.
ISO 24534-3:2010 defines the vehicle identification data. This data is called the ERI data and includes
the vehicle identifier, and
possible additional vehicle-related information (as typically included in a vehicle registration certificate).
All additional vehicle data elements are defined as optional. It is left to local legislation and/or the discretion of a registration authority to use or not to use a particular data element. If used, the value is assumed to be the one registered by the registration authority in accordance with local legislation. ISO 24534-3:2010 only provides the syntax for all these data elements.
|
Withdrawn |
2010-07 |
Edition : 1 |
Number of pages : 32 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 24534-3:2008 |
Automatic vehicle and equipment identification — Electronic Registration Identification (ERI) for vehicles — Part 3: Vehicle data |
ISO TS 24534-3:2008 provides the requirements for an Electronic Registration Identification (ERI) that is based on an identifier assigned to a vehicle (e.g. for recognition by national authorities) suitable to be used for :
electronic identification of local and foreign vehicles by national authorities,
vehicle manufacturing, in-life-maintenance and end-of-life identification (vehicle life cycle management),
adaptation of vehicle data, e.g. in case of international re-sales,
safety-related purposes,
crime reduction, and
commercial services.
It adheres to privacy and data protection regulations.
ISO TS 24534-3:2008 defines the vehicle identification data. This data is called the ERI data and includes the vehicle identifier and possible additional vehicle related information (as typically included in a vehicle registration certificate).
|
Withdrawn |
2008-02 |
Edition : 1 |
Number of pages : 32 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 24534-3:2016 |
Intelligent transport systems — Automatic vehicle and equipment identification — Electronic registration identification (ERI) for vehicles — Part 3: Vehicle data |
ISO 24534-3:2016 provides the requirements for an electronic registration identification (ERI) that is based on an identifier assigned to a vehicle (e.g. for recognition by national authorities) suitable to be used for the following:
- electronic identification of local and foreign vehicles by national authorities;
- vehicle manufacturing, in-life-maintenance, and end-of-life identification (vehicle life cycle management);
- adaptation of vehicle data, e.g. in case of international re-sales;
- safety-related purposes;
- crime reduction;
- commercial services;
- adhering to privacy and data protection regulations.
ISO 24534-3:2016 defines the vehicle identification data. This data is called the ERI data and includes the following:
- the vehicle identifier;
- possible additional vehicle-related information (as typically included in a vehicle registration certificate).
All additional vehicle data elements are defined as optional. It is left to local legislation and/or the discretion of a registration authority to use or not to use a particular data element. If used, the value is assumed to be the one registered by the registration authority in accordance with local legislation. This part of ISO 24534 only provides the syntax for all these data elements.
NOTE The secure application layer interfaces for the exchange of ERI data with an ERI reader or writer are specified in ISO 24534‑4 and in ISO 24534‑5.
|
Published |
2016-04 |
Edition : 2 |
Number of pages : 56 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 24534-4:2010 |
Automatic vehicle and equipment identification — Electronic registration identification (ERI) for vehicles — Part 4: Secure communications using asymmetrical techniques |
ISO 24534-4:2010 provides requirements for electronic registration identification (ERI) that are based on an identifier assigned to a vehicle (e.g. for recognition by national authorities) suitable to be used for:
electronic identification of local and foreign vehicles by national authorities;
vehicle manufacturing, in-life maintenance and end-of-life identification (vehicle life cycle management);
adaptation of vehicle data (e.g. for international resales);
safety-related purposes;
crime reduction;
commercial services.
It adheres to privacy and data protection regulations.
ISO 24534-4:2010 specifies the interfaces for a secure exchange of data between an ERT and an ERI reader or ERI writer in or outside the vehicle using asymmetric encryption techniques.
ISO 24534-4:2010 includes:
the application layer interface between an ERT and an onboard ERI reader or writer;
the application layer interface between the onboard ERI equipment and external ERI readers and writers;
security issues related to the communication with the ERT.
|
Published |
2010-07 |
Edition : 1 |
Number of pages : 94 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 24534-4:2008 |
Automatic vehicle and equipment identification — Electronic Registration Identification (ERI) for vehicles — Part 4: Secure communications using asymmetrical techniques |
ISO TS 24534-4:2008 provides the requirements for an Electronic Registration Identification (ERI) that is based on an identifier assigned to a vehicle (e.g. for recognition by national authorities) and suitable to be used for :
electronic identification of local and foreign vehicles by national authorities,
vehicle manufacturing, in-life-maintenance and end-of-life identification (vehicle life cycle management),
adaptation of vehicle data, e.g. in case of international re-sales,
safety related purposes,
crime reduction, and
commercial services.
It adheres to privacy and data protection regulations.
ISO TS 24534-4:2008 specifies the interfaces for a secure exchange of data between an ERT and an ERI reader or ERI writer in or outside the vehicle using asymmetric encryption techniques. It includes:
the application layer interface between an ERT and a onboard ERI reader or writer,
the application layer interface between the onboard ERI equipment and external ERI readers and writers, and
security issues related to the communication with the ERT.
|
Withdrawn |
2008-02 |
Edition : 1 |
Number of pages : 95 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 24534-4:2010/Amd 1:2019 |
Automatic vehicle and equipment identification — Electronic registration identification (ERI) for vehicles — Part 4: Secure communications using asymmetrical techniques — Amendment 1 |
|
Published |
2019-02 |
Edition : 1 |
Number of pages : 12 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 24534-5:2011 |
Intelligent transport systems — Automatic vehicle and equipment identification — Electronic Registration Identification (ERI) for vehicles — Part 5: Secure communications using symmetrical techniques |
ISO 24534 provides the requirements for an electronic registration identification (ERI) using symmetric encryption techniques that are based on an identifier assigned to a vehicle (e.g. for recognition by national authorities) suitable to be used for
electronic identification of local and foreign vehicles by national authorities,
vehicle manufacturing, in-life maintenance and end-of-life identification (vehicle life-cycle management),
adaptation of vehicle data, e.g. in case of international re-sales,
safety related purposes,
crime reduction,
commercial services, and
adhering to privacy and data protection regulations.
ISO 24534-5:2011 specifies the interfaces for a secure exchange of data between the electronic registration tag (ERT), which is the onboard device containing the ERI data, and the ERI reader or ERI writer in or outside the vehicle using symmetric encryption techniques.
Symmetric encryption techniques are based on secret keys shared by a particular community of users, i.e. in closed user groups in which it is trusted that keys are not revealed to outsiders.
It includes
the interface between an ERT and an onboard ERI reader or writer,
the interface between the onboard ERI equipment and (roadside) reading and writing equipment, and
security issues related to the communication with the ERT.
|
Published |
2011-12 |
Edition : 1 |
Number of pages : 39 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 24534-5:2008 |
Automatic vehicle and equipment identification — Electronic Registration Identification (ERI) for vehicles — Part 5: Secure communications using symmetrical techniques |
ISO/TS 24534-5:2008 provides the requirements for an Electronic Registration Identification (ERI) using symmetric encryption techniques that are
based on an identifier assigned to a vehicle (e.g. for recognition by national authorities),
suitable to be used for:
electronic identification of local and foreign vehicles by national authorities;
vehicle manufacturing, in-life maintenance and end-of-life identification (vehicle life-cycle management);
adaptation of vehicle data, e.g. in case of international re-sales;
safety related purposes;
crime reduction;
commercial services, and
adhering to privacy and data protection regulations.
It specifies the interfaces for a secure exchange of data between an electronic registration tag (ERT) and an ERI reader or ERI writer in or outside the vehicle using symmetric encryption techniques.
Symmetric encryption techniques are based on secret keys shared by a particular community of users, i.e. in closed user groups in which it is trusted that keys are not revealed to outsiders.
ISO/TS 24534-5:2008 specifies:
the interface between an ERT and an onboard ERI reader or writer,
the interface between the onboard ERI equipment and (road side) reading and writing equipment,
security issues related to the communication with the ERT.
|
Withdrawn |
2008-02 |
Edition : 1 |
Number of pages : 38 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 24534-5:2011/Amd 1:2019 |
Intelligent transport systems — Automatic vehicle and equipment identification — Electronic Registration Identification (ERI) for vehicles — Part 5: Secure communications using symmetrical techniques — Amendment 1 |
|
Published |
2019-02 |
Edition : 1 |
Number of pages : 4 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 39001:2012 |
Road traffic safety (RTS) management systems — Requirements with guidance for use |
ISO 39001:2012 specifies requirements for a road traffic safety (RTS) management system to enable an organization that interacts with the road traffic system to reduce death and serious injuries related to road traffic crashes which it can influence. The requirements in ISO 39001:2012 include development and implementation of an appropriate RTS policy, development of RTS objectives and action plans, which take into account legal and other requirements to which the organization subscribes, and information about elements and criteria related to RTS that the organization identifies as those which it can control and those which it can influence.
|
Published |
2012-10 |
Edition : 1 |
Number of pages : 37 |
Technical Committee |
03.100.70
Management systems
;
03.220.20
Road transport
|
| ISO/DTR 5340 |
Motorcycles — Consideration for use cases of ISO 26262-12 MSIL classification |
|
Under development |
|
Edition : 1 |
Number of pages : 16 |
Technical Committee |
43.140
Motorcycles and mopeds
|
| ISO 24535:2007 |
Intelligent transport systems — Automatic vehicle identification — Basic electronic registration identification (Basic ERI) |
ISO 24535:2007 supports simple systems for "basic electronic registration identification" ("basic ERI") for use in intelligent road transport applications.
ISO 24535:2007 "basic ERI" defines the: specification of a unique vehicle identifier (using an International Standard, or non-standard, data concept); "basic ERI" functional capabilities, selectable for different "basic ERI" applications; and minimum data interoperability requirements between basic electronic registration tags (ERTs) and electronic registration readers (ERRs).
ISO 24535:2007 allows, but does not require, vehicle-related data storage in addition to the unique vehicle identifier.
ISO 24535:2007 is consistent with the ERI architecture defined in ISO/TS 24534-1 and data concepts defined in ISO/TS 24534-3, but is not necessarily interoperable with, the more capable and "fully featured" ERI communication systems to be defined in ISO/TS 24534-4 or ISO/TS 24534-5.
ISO 24535:2007 defines a "basic ERI" system with security adequate for information that is currently available manually (such as license plate and/or VIN data), but it does not purport to provide the high levels of security required for some administrative requirements. Those requiring high security are advised to follow the relevant parts of ISO/TS 24534.
Although not part of ISO 24535:2007, the employed technologies supporting ISO 24535:2007 may enable additional non-standard security measures to be added for specific applications
It is not the purpose of ISO 24535:2007 to define "basic ERI" applications.
ISO 24535:2007 requires the use of an air interface communication that complies with an international or regional standard whose protocols are publicly defined and available in that standard, but ISO 24535:2007 does not define such an air interface, nor specify which standard air interface is used for any particular implementation.
ISO 24535:2007 limits its scope to: the requirement that a standard air interface with publicly available protocols is used; the use of data concepts consistent with ISO/TS 24534-3; and the ability to additionally use private data concepts.
|
Published |
2007-09 |
Edition : 1 |
Number of pages : 11 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 37158:2019 |
Smart community infrastructures — Smart transportation using battery-powered buses for passenger services |
This document specifies a procedure for the introduction of smart transportation to city centres by means of battery-powered buses. This service contributes to a clean atmosphere and a relatively quiet environment while offering services that provide safe and comfortable rides for citizens.
|
Published |
2019-07 |
Edition : 1 |
Number of pages : 8 |
Technical Committee |
03.220.20
Road transport
;
13.020.20
Environmental economics. Sustainability
|
| ISO 37181:2022 |
Smart community infrastructures — Smart transportation by autonomous vehicles on public roads |
This document describes the concept and goals of smart transportation by autonomous vehicles on public roads. It provides guidelines for the successful introduction and organisation of autonomous vehicles, with the aim of enhancing the safety of public road transportation and addressing the challenges to cities such as an aging population and diverse travel demands.
This document focuses on the deployment of autonomous vehicles as an operational system for actual use on public roads. This document is intended for those in academia, autonomous vehicle developers, policy makers, research institutions, road infrastructure operators, public road administrators, testing inspection and certification bodies, and vehicle manufacturers.
NOTE 1 This document targets autonomous vehicle services except on-demand responsive services with shared vehicles. For on-demand responsive passenger services with shared vehicles, see ISO 37168.
NOTE 2 A bus vehicle is shared by different passenger groups and can be chartered. A taxi vehicle is hired and can, if local regulations permit, be shared by different passenger groups.
|
Published |
2022-06 |
Edition : 1 |
Number of pages : 9 |
Technical Committee |
03.220.20
Road transport
;
13.020.20
Environmental economics. Sustainability
|
| ISO 37182:2022 |
Smart community infrastructures — Smart transportation for fuel efficiency and pollution emission reduction in bus transportation services |
This document describes criteria to organize smart transportation to save fuel in bus transportation services where the reduction of energy consumption is intended. Smart transportation aims not only at fuel efficiency, but at pollutant emission reduction for engine driven buses, as well as the financial stabilization of bus transportation services for citizens and city visitors.
|
Published |
2022-06 |
Edition : 1 |
Number of pages : 11 |
Technical Committee |
03.220.20
Road transport
;
13.020.20
Environmental economics. Sustainability
|
| ISO/DIS 37183 |
Smart community infrastructures — Smart transportation with the use of face recognition payment (f-payment) |
|
Under development |
|
Edition : 1 |
Number of pages : 10 |
Technical Committee |
03.220.20
Road transport
;
13.020.20
Environmental economics. Sustainability
|
| ISO/TS 37444 |
Electronic fee collection — Charging performance framework |
The document defines and specifies the metrics as well as the examination framework for the purpose of evaluation of performance of the charging chain in EFC-systems. It focuses on data used for information exchange over specific interoperable interfaces.
It provides a toolbox for the metrics and examination framework for both involved roles, i.e. toll chargers and the toll service providers.
The following types of EFC systems are considered:
- discrete systems; and
- continuous systems.
The following EFC system technologies are inside the scope of this specification:
- DSRC based systems;
- ANPR (CCTV) based systems; and
- autonomous systems.
The detailed choice of the set of metrics and examination tests to be used depends on the application and the respective context. Compliance with this specification is understood as using the definitions and prescriptions laid out in this specification whenever the respective system aspects are subjected to performance measurements, rather than using other definitions and examination methods than the ones specified in this specification.
The metrics and examination framework are explicitly defined for the two phases of an EFC-system lifetime:
- evaluation phase (e.g. applied in supply selection, commissioning, ram-up of EFC systems); and
- monitoring phase (e.g. applied in SLA measuring in real system operation).
Depending on the individual EFC-system lifetime phase, the system type (discrete or continuous) and technology (DSRC, ANPR, GNSS) the sources of data to be used in the examination will vary. Such variations are considered in the definition of the individual metrics.
Metrics and their examination procedures are defined for different areas or the E2E-data processing chain in an EFC-system, like
- end-to-end;
- user accounts;
- payment claims;
- billing details; and
- toll declarations.
This document covers:
- the explanation of the chosen methodology;
- the definition of charging performance metrics (including their applicability for different system types and different technologies);
- the definition of the examination framework, including supporting elements like sources of data to be used, characteristics of test routes etc;
- the specification and profiling of evaluation tests depending on the respective EFC system technology and system type.
- In addition, the document will provide a template for test documentation as well as statistical considerations in informative annexes.
|
Under development |
|
Edition : 1 |
|
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 6054-2:1986 |
Motorcycle tyres and rims (diameter codes 4 to 12) — Scooter type — Part 2: Rims |
|
Withdrawn |
1986-11 |
Edition : 1 |
|
Technical Committee |
43.140
Motorcycles and mopeds
|
| ISO 3929:1995 |
Road vehicles — Measurement methods for exhaust gas emissions produced during inspection or maintenance |
Establishes the test procedures for direct measurement of the concentration of exhaust gas emissions from road vehicles with a maximum authorized total mass not exceeding 3,5 t, equipped with controlled ignition engines, excluding those which are supplied with fuel/oil mixture. Defines the recommended test procedure for periodic inspections in official garages, official roadside checks (e.g. by police), maintenance and diagnostic operations. These procedures may be used totally or partially.
|
Withdrawn |
1995-02 |
Edition : 2 |
Number of pages : 6 |
Technical Committee |
13.040.50
Transport exhaust emissions
;
43.060.20
Pressure charging and air/exhaust gas ducting systems
|
| ISO 3929:2003 |
Road vehicles — Measurement methods for exhaust gas emissions during inspection or maintenance |
ISO 3929:2003 specifies methods for the direct measurement of the concentration of exhaust gas emissions from road vehicles during inspection or maintenance. It is applicable to vehicles having a maximum authorized total mass (ISO-M08, as defined in ISO 1176) not exceeding 3,5 t, equipped with controlled ignition engines, but excluding those supplied with a fuel/oil mixture (with or without automatic mixer). The methods can be used, either totally or partially, for periodic inspections in official garages, official roadside checks (e.g. by police) and maintenance and diagnostic operations.
|
Published |
2003-09 |
Edition : 3 |
Number of pages : 6 |
Technical Committee |
13.040.50
Transport exhaust emissions
;
43.060.20
Pressure charging and air/exhaust gas ducting systems
|
| ISO 3930:1976 |
Road vehicles — Carbon monoxide analyser equipment — Technical specifications |
|
Withdrawn |
1976-05 |
Edition : 1 |
Number of pages : 2 |
Technical Committee |
43.180
Diagnostic, maintenance and test equipment
;
13.040.50
Transport exhaust emissions
|
| ISO/PAS 3930:2009 |
Instruments for measuring vehicle exhaust emissions — Metrological and technical requirements; Metrological control and performance tests |
ISO/PAS 3930:2009 specifies the metrological and technical requirements and tests for digital measuring instruments that serve to determine the volume fractions of certain components of the exhaust gases emanating from motor vehicles. The conditions with which such instruments shall comply in order to meet any OIML performance requirements are also established.
ISO/PAS 3930:2009 is applicable to instruments, particularly those used according to the procedure defined in ISO 3929, intended for the inspection and maintenance of in-use motor vehicles with spark ignition engines. These instruments are used to determine the volume fraction of one or more of the following exhaust gas components:
carbon monoxide (CO),
carbon dioxide (CO2),
hydrocarbons (HC, in terms of n-hexane), and
oxygen (O2)
at the moisture level of the sample as analysed.
In addition to the measurement of these components, ISO/PAS 3930:2009 specifies the lambda calculation for the instruments provided with a facility to determine the value of air/fuel ratio in the exhaust gases.
ISO/PAS 3930:2009 applies to instruments whose principle of detection is based on infrared absorption in gases for CO, CO2 and HC. Oxygen is generally measured with a fuel cell.
ISO/PAS 3930:2009 does not exclude any other types of instruments that, although based on other principles of detection, meet the specified metrological and technical requirements and satisfy the associated tests.
ISO/PAS 3930:2009 defines three accuracy classes of the instruments: Class 00, Class 0 and Class I.
ISO/PAS 3930:2009 does not apply to equipment for on-board diagnostics incorporated in motor vehicles.
|
Withdrawn |
2009-12 |
Edition : 1 |
Number of pages : 42 |
Technical Committee |
43.180
Diagnostic, maintenance and test equipment
;
13.040.50
Transport exhaust emissions
|
| ISO 3930:1993 |
Road vehicles — Measurement equipment for exhaust gas emissions during inspection or maintenance — Technical specifications |
|
Withdrawn |
1993-10 |
Edition : 2 |
Number of pages : 16 |
Technical Committee |
43.180
Diagnostic, maintenance and test equipment
;
13.040.50
Transport exhaust emissions
|
| ISO 3930:2000 |
Instruments for measuring vehicle exhaust emissions |
|
Withdrawn |
2000-09 |
Edition : 3 |
Number of pages : 27 |
Technical Committee |
43.180
Diagnostic, maintenance and test equipment
;
13.040.50
Transport exhaust emissions
|
| ISO 3930:2000/Amd 1:2004 |
Instruments for measuring vehicle exhaust emissions — Amendment 1 |
|
Withdrawn |
2004-10 |
Edition : 3 |
Number of pages : 1 |
Technical Committee |
43.180
Diagnostic, maintenance and test equipment
;
13.040.50
Transport exhaust emissions
|
| ISO/TR 4011:1976 |
Road vehicles — Apparatus for measurement of the opacity of exhaust gas from diesel engines |
|
Withdrawn |
1976-06 |
Edition : 1 |
Number of pages : 17 |
Technical Committee |
43.180
Diagnostic, maintenance and test equipment
;
13.040.50
Transport exhaust emissions
|
| ISO 6460-1:2007 |
Motorcycles — Measurement method for gaseous exhaust emissions and fuel consumption — Part 1: General test requirements |
ISO 6460-1:2007 specifies the general test requirements for measurement for the gaseous exhaust emissions from motorcycles, and for determining the fuel consumption of motorcycles as defined in ISO 3833. It is applicable to motorcycles equipped with a spark ignition engine (4-stroke engine, 2-stroke engine or rotary piston engine) or a compression ignition engine.
|
Withdrawn |
2007-08 |
Edition : 1 |
Number of pages : 51 |
Technical Committee |
43.140
Motorcycles and mopeds
;
13.040.50
Transport exhaust emissions
|
| ISO 7398:1984 |
Road vehicles — Motorcycles — D.C. flasher units |
|
Withdrawn |
1984-10 |
Edition : 1 |
Number of pages : 6 |
Technical Committee |
43.140
Motorcycles and mopeds
|