ISO/TC 204/WG 9 - Integrated transport information, management and control

This document defines a platform-specific model (PSM) for data exchange, which specifically uses ASN.1 and TCP/UDP (transmission control protocol/user datagram protocol) datagrams which were defined as “DATEX-ASN” in the first edition of this document for AP-DATEX (application profile-data exchange) and other Internet protocol (IP) networks. A PSM is an actual implementation of a platform-independent model (PIM) for exchange. This document specifies the message rules and procedures for communication between different systems for ITS using TCP/UDP datagrams. This document deals mainly with the communication interfaces. It has been designed to meet the unique requirements of intelligent transport systems (ITS). However, it has also been designed in a generic fashion and thus can be used for other data exchanges as well.

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.

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.

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.

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.

This document, based on ISO/TS 19468, specifies a platform-specific method for implementing data exchange among centres based on simple object access protocol (SOAP), supporting the EN 16157 series (DATEX II) for Push/Pull data delivery and service request/feedback collaborative intelligent transport system (ITS) services. This document defines the message rules and procedures for communication between transport information and control systems using XML (Profile B). This document clarifies how to package end-application messages and relevant data. The payload data definition used in specific end-applications and the exact structure of the content payload delivered in the messages are beyond the scope of this document. Rules and procedures for exchanging data-packets in lower communication layers are also out of the scope of this document. These functionalities can be implemented using generic protocols defined in the industry standards. However, this document does define how to use these protocols.

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.

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.

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.

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.

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.

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.

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.

This document is applicable to data exchange between different systems. This document defines the message rules and procedures for communication between transport information and control systems using XML. This document clarifies how to package end-application messages and relevant data. This document defines the mechanism to request end-application data from the client and to deliver the requested data from the supplier. Several profiles are defined, however only Profile A is defined in this document. Other profiles will be defined in future parts of the ISO 14827 series of standards. A system can be both a client and a supplier of another system simultaneously, using multiple sessions.

ISO 15784-2:2015 specifies a mechanism to exchange data and messages in the following cases: a) between a traffic management centre(s) and roadside modules for traffic management; b) between roadside modules used for traffic management. The scope of this part of ISO 15784-2:2015 does not include the communication between traffic management centre and in-vehicle units, between roadside modules and in-vehicle units, in-vehicle communication, in-cabinet communication, or motion video transmission from a camera or recorded media. ISO 15784-2:2015 is complimentary to ISO 15784-3, but uses a different application layer for the information exchanges to configure, control, and monitor the field traffic control roadside modules. Where ISO 15784-3 is based on the DATEX standards, this part of ISO 15784 uses an alternative approach based on SNMP with an optional extension for more efficient transmission over low bandwidth media. Both of these standards conform to the application profile requirements set forth in ISO 15784-1.

ISO/TR 16786:2015 provides guidelines for disclosing simulation conditions and results when evaluating the performance of signal control methods, focusing on algorithm that establishes signal timings based on traffic conditions. The following are the main aims of the evaluation of signal control systems: a) to evaluate the quality of the algorithm in various traffic conditions; b) to evaluate the validity of the algorithm for specific applications (types of intersection); c) to establish a fair comparison of the algorithm versus other existing algorithms or other types of control systems; d) to evaluate the results of the implementation of a signal control system objectively. When claiming and/or comparing the performance of signal control systems from simulation results, it is necessary to clarify simulation conditions and results so that third parties can objectively judge its fairness and reasonability. ISO/TR 16786:2 describes minimum necessary items of conditions that shall be disclosed to ensure fair evaluation and does not describe maximum possible items.

ISO 10711:2012 defines protocols and message sets between traffic detectors and traffic signal controllers. It is applicable to the various types of traffic detector technologies currently in use for real-time traffic signal controls. It defines message sets that contain data collection and control protocol for three different types of detectors of traffic signal control systems: detectors that deal with occupancy information; detectors that deal with image information; and detectors that deal with vehicle identification. ISO 10711:2012 is limited to parameter generation to be used for traffic signal controls and for the interface between traffic signal controllers and detectors.

ISO 15784-3:2008 defines an application profile referring ISO 14827 and other base standards. The application profile it specifies is used to exchange data and messages between a traffic management centre and roadside modules for traffic management, and between roadside modules used for traffic management. The scope of ISO 15784-3:2008 does not include the communication between roadside modules and in-vehicle units, in-vehicle communication, in-cabinet communication or motion video transmission from a camera or recorded media.

ISO 15784-1:2008 provides principles and documentation rules of application profiles used to exchange data and messages between a traffic management centre and roadside modules used for traffic management. The application profiles it specifies are used to exchange data and messages between a traffic management centre and roadside modules for traffic management and between roadside modules used for traffic management. The scope of ISO 15784-1:2008 does not include the communication between roadside modules and on-board units, in-vehicle communication, in-cabinet communication and motion video transmission from a camera or recorded media.

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.

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.

ISO 14827-1:2005 allows different systems to exchange relevant data. The relevant data will be contained in end-application messages. Each end-application message will be formally defined as either a "subscription" or a "publication", according to the format as specified in ISO 14827-1:2005. DATEX-ASN defines how these end-application messages are packaged to form a complete data packet and also defines the rules and procedures for exchanging these data packets. Systems using DATEX-ASN are free to implement additional end-application functionalities according to the user requirements.

ISO 14827-1:2005 defines the format that should be used to document those end-application messages that are to be exchanged between/among central systems. The format is protocol-independent to the extent practical. For example, this one format can be used to define data exchanges that may apply to DATEX-ASN, CORBA, or other Application Protocols. In general, each system can be viewed as consisting of the following interfaces: Application Interface Operator Interface Communication Interface Database Interface