Traffic and Travel Information - TTI
Traffic and Travel Information standards go hand in hand with Intelligent Transport System standards, working together to further the goal of seamless integration between devices and data manipulation for integrated transport information, management, and control. Developed by SAE International and the International Organization for Standardization (ISO), these standards strive for interoperability across the world.
ISO 14819-3:2021
Intelligent transport systems - Traffic and travel information messages via traffic message coding - Part 3: Location referencing for Radio Data System-Traffic Message Channel (RDS-TMC) using ALERT-C
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.
ISO 14823:2017
Intelligent transport systems - Graphic data dictionary
ISO14823:2017 specifies a graphic data dictionary, a system of standardized codes for existing road traffic signs and pictograms used to deliver Traffic and Traveller Information (TTI). The coding system can be used in the formation of messages within intelligent transport systems.
ISO/TS 16951:2021
Road vehicles - Ergonomic aspects of transport information and control systems (TICS) - Procedures for determining priority of on-board messages presented to drivers
This document provides formal procedures and two, alternative, methods (users are advised to choose whichever of the two suits their individual requirements) for determining the priority of on-board messages presented to drivers of road vehicles by transport information and control systems (TICS) and other systems. It is applicable to the whole range of TICS in-vehicle messages, including traveller information, navigation, travel and traffic advisories, “yellow pages†information, warnings, systems status, emergency calling system information, and electronic toll/fee collection, as well as to messages from non-TICS sources such as telephone, warnings and telltales. Although applicable to systems that allow the free generation of messages, it neither provides guidance on how to use the messages deriving from its procedures nor is it applicable to mandatory or legally required messages.
SAE J 2540-2-2009 (SAE J2540-2-2009)
ITIS Phrase Lists (International Traveler Information Systems)
This standard provides a table of textual messages meeting the requirements for expressing 'International Traveler Information Systems' (ITIS) phrases commonly used in the ITS industry. The tables provided herein follow the rules of SAE J2540 and therefore allow a local representation in various different languages, media expressions etc. to allow true international use of these phrases. The phrases are predominantly intended for use in the description of traffic related events of interest to travelers and other traffic practitioners. Other phrases exit for other specific specialty areas of ITS, and all such phrases follow a set of encoding and decoding rules outlined in SAE J2540 to ensure that the use of these phrases in messages remain interoperable between disparate types of user equipment. Implementers are cautioned to obtain the most recent set of tables by means of the ITS data registry, a process which involves the SAE and other standards setting organizations and which is intended to maintain and enhance the level of harmonization among ITS standards set by each of the organizations. This standard SHALL define the normative index values to be used to provide phrases needed by ITS practitioners. This standard provides non-normative textual phrases which MAY be used by implementers to ensure intelligible results. This standard SHALL follow the formats and rules established in SAE J2540 in the expressions, manipulations, and use of such tables. It should be pointed out that within the rules established by this standard a variety of final tables are all considered 'compliant' with the standard, and may vary as fits the needs of implementers.
SAE J 2630-2003 (SAE J2630-2003)
Converting ATIS Message Standards from ASN.1 to XML
?This SAE Standard presents a set of rules for transforming an Abstract Syntax Notation (ASN.1) message set definition into an eXtensible Markup Language (XML) schema. The result is intended to be a stand-alone XML Schema that is fully consistent with an existing ASN.1 information model. This is a different goal from other related work by other standards bodies developing a set of XML encoding rules for ASN.1 or ASN.1 encodings for XML Schema. These rules were initially developed in order to produce an XML schema for the SAE ATIS standard. While other standards may also choose to use these rules, the rules may not be applicable for all environments. The goal for these transformation rules is twofold. The first goal is to provide a uniform set of such rules that all interested parties can use. The second goal is to use such rules to define an adopted schema for traveler information that reflects the preferred translation of ASN.1 message sets to XML for use by ITS system implementers. The first goal is met by this document. The second goal is met by employing this document to produce XML information as part of the periodic re-balloting of the SAE ATIS standard. This is a parallel standards effort with this document. These rules were developed as part of the process to draft an XML version of the ATIS data element and message set standards. The original effort focused upon the needs found in the currently adopted October 2000 SAE J2354 standard for ATIS message sets. SAE J2354 makes extensive use of elements from the ITETMDD work and from ITE-TCIP work. In addition, the draft ?Event Report Message? (ERM) portion of the Message Sets for External Traffic Management Center Communication (MS/ETMCC) standard was also examined and translated. Message and data elements from the IEEE Incident Management standard (IEEE 1512-2000) were also examined. By this effort, every major message set of ITS was considered to some degree to ensure that the resulting translations could be successfully employed by others toward a common result. It is intended that the resulting ATIS schema will be voted on as an SAE ATIS standard. Other standards-developing organizations may also choose to use these rules; however, it is recognized that translations may not be necessary in some environments and that these rules may not be applicable to all environments within ITS. It is left to each standards-development organization to make such determinations for their specific environments. Section 4 is the complete set of conversion rules. An example of use for each rule is given, showing an original ASN.1 definition, the resulting XML schema definition, and a sample XML document element where applicable. Section 5 of this document discusses the background of some non-obvious conversion rules presented in Section 4.2 These include methods of handling the XML representation of enumerations, octet strings, and bit strings. Section 5 also describes how XML namespaces can be used to point to types defined in the Traffic Management Data Dictionary (TMDD), the Transit Communications Interface Profiles (TCIP) standard, the Location Reference Message Set (LRMS), or the International Traveler Information Systems (ITIS) phrase lists. It also discusses additional translation refinements proposed for the conversion of the ATIS message standard. Some omissions in the SAE standards required new types to be defined in order to have a valid XML schema. In addition, some new types must be defined to implement the representation of octet strings and bit strings. These changes are documented in Section 6. In the currently adopted revision of the standard the use of inline definitions rather than the more proper use of formal Type Definitions is also a challenge for conversion. Section 6 also documents a number of common types that were defined globally at the start of the schema rather than being redefined identically, in-line multiple times in the schema. Section 7 presents a sizable sample ASN.1 definition and the corresponding XML schema. The sample illustrates a large number of the conversion rules.
