Search Results

This SAE Information Report provides a comparative summary between the various messages found in the SAE ATIS standards work (notably SAE J2313, J2353, J2354, J2369 and J2374) and that found in the GATS standard (Global Automotive Telematics Standard). GATS is a message set meant to be deployed on mobile phone systems based on the GSM (Global System for Mobile Communication) phone system which is being deployed in European markets and which the SAE may need to harmonize with as part of the World Standards activities of TC204. This document provides an overview of the various types of supported messages and how they compare with US terms and messages. Some selected features of the GATS work are recommended for assimilation into the next revision of ATIS standards. No attempt at determining a U.S. policy in this regard is provided. This document seeks to provide the reader familiar with SAE ATIS with a high level overview of technical knowledge of the GATS approach in similar areas.

This SAE Information Report provides a comparative summary between the various messages found in the SAE ATIS standards work (notably SAE J2313, J2353, J2354, J2369 and J2374) and that found in the GATS standard (Global Automotive Telematics Standard). GATS is a message set meant to be deployed on mobile phone systems based on the GSM (Global System for Mobile Communication) phone system which is being deployed in European markets and which the SAE may need to harmonize with as part of the World Standards activities of TC204. This document provides an overview of the various types of supported messages and how they compare with US terms and messages. Some selected features of the GATS work are recommended for assimilation into the next revision of ATIS standards. No attempt at determining a U.S. policy in this regard is provided. This document seeks to provide the reader familiar with SAE ATIS with a high level overview of technical knowledge of the GATS approach in similar areas.

This SAE Recommended Practice provides a set of core data elements needed by information service providers for Advanced Traveler Information Systems (ATIS). The data dictionary herein provides the foundation for ATIS message sets for all stages of travel (pre-trip and en route), all types of travelers (drivers, passengers), all categories of information, and all platforms for delivery of information (in-vehicle, portable devices, kiosks, etc.). The elements of this document are the basis for the SAE ATIS Message Set Standard J2354 and are entered into the SAE Data Registry for ITS wide coordination.

This SAE Recommended Practice provides a set of core data elements needed by information service providers for Advanced Traveler Information Systems (ATIS). The data dictionary herein provides the foundation for ATIS message sets for all stages of travel (pre-trip and en route), all types of travelers (drivers, passengers), all categories of information, and all platforms for delivery of information (in-vehicle, portable devices, kiosks, etc.). The elements of this document are the basis for the SAE ATIS Message Set Standard J2354 and are entered into the SAE Data Registry for ITS wide coordination.

This SAE Standard serves as the guidance document for the J2945/x family of standards as illustrated in Figure 7. It contains cross-cutting material which applies to the other J2945/x standards, including recommended practice for the use of Systems Engineering (SE) and generic DSRC interface requirements content. The scope for the DSRC system environment is to provide for the information exchange between a host vehicle and another DSRC enabled device, a device worn by or otherwise attached to a traveler, a roadside device, or a management center, to address safety, mobility, and environmental system needs. The audience for this document includes the technical teams of developers of the J2945/x documents and the implementers of the applications which are based on the J2945/x documents.

This SAE Recommended Practice is intended as a guide toward standard practice and is subject to change to keep pace with experience and technical advances. This SAE Recommended Practice specifies standard message sets, data frames and data elements for use by applications intended to utilize the 5.9 GHz Dedicated Short Range Communications for Wireless Access in Vehicular Environments (DSRC/WAVE, referenced in this document simply as “DSRC”), communications systems. The scope is limited to specifying initial representative message structure and providing sufficient background information to allow readers to properly interpret the DSRC standards and message definitions from the point of view of an application developer.

The Location Referencing Message Specification (LRMS) standardizes location referencing for ITS applications that require the communication of spatial data references between databases. ITS databases may reside in central sites, vehicles, or devices on or off roads or other transportation links. The LRMS is applicable to both homogeneous (same database) and mixed database environments that may be implemented on wireless or landline networks. While developed for ITS applications, the LRMS may be used for non-ITS applications as well within the field of geographic information processing.

The Location Referencing Message Specification (LRMS) standardizes location referencing for ITS applications that require the communication of spatial data references between databases. ITS databases may reside in central sites, vehicles, or devices on or off roads or other transportation links. The LRMS is applicable to both homogeneous (same database) and mixed database environments that may be implemented on wireless or landline networks. While developed for ITS applications, the LRMS may be used for non-ITS applications as well within the field of geographic information processing.

This SAE Standard describes standardized medium-independent messages needed by information service providers for Advanced Traveler Information Systems (ATIS). The messages contained herein address all stages of travel (pre-trip and en-route), all types of travelers (drivers, passengers), all categories of information, and all platforms for delivery of information (in-vehicle, portable devices, kiosks, etc.).

This SAE Standard describes standardized medium-independent messages needed by information service providers for Advanced Traveler Information Systems (ATIS). The messages contained herein address all stages of travel (informational, pre-trip and en route), all types of travelers (drivers, passengers, personal devices, computers, other servers), all categories of information, and all platforms for delivery of information (in-vehicle, portable devices, kiosks, etc.).

This SAE Standard describes standardized medium-independent messages needed by information service providers for Advanced Traveler Information Systems (ATIS). The messages contained herein address all stages of travel (informational, pre-trip and en route), all types of travelers (drivers, passengers, personal devices, computers, other servers), all categories of information, and all platforms for delivery of information (in-vehicle, portable devices, kiosks, etc.).

This SAE Standard defines methods and messages to efficiently translate sequences of text and other types of data into and out of indexed values and look-up tables for effective transmission. This document defines: a Methods and Data Elements for handling indexes and strings in ATIS applications and message sets b Message Sets to support the delivery and translations of tables used in such strings c Tables of Nationally standardized strings for use in ATIS message descriptions And examples of each in illustrative portions. While developed for ATIS use, the methods defined in this document are useful for any textual strings in any Telematics applications found both in Intelligent Vehicles and elsewhere.

This SAE Standard defines methods and messages to efficiently translate sequences of text and other types of data into and out of indexed values and look-up tables for effective transmission. This document defines: a Methods and Data Elements for handling indexes and strings in ATIS applications and message sets b Message Sets to support the delivery and translations of tables used in such strings c Tables of Nationally standardized strings for use in ATIS message descriptions And examples of each in illustrative portions. While developed for ATIS use, the methods defined in this document are useful for any textual strings in any Telematics applications found both in Intelligent Vehicles and elsewhere.

This report specifies the minimum requirements for the Road Geometry and Attributes (RGA) data set (DS) to support road geometry related motor vehicle safety applications. Contained in this report are a concept of operations, requirements, and design, developed using a detailed systems engineering process. Utilizing the requirements, the RGA DS is defined, which includes the DS Abstract Syntax Notation One (ASN.1) format, data frames, and data element definitions. The requirements are intended to enable the exchange of the messages and their DS information to provide the desired interoperability and data integrity to support the applications considered within this report, as well as other applications which may be able to utilize the DS information. System requirements beyond this are outside the scope of this report.

SAE J2945/A and this Abstract Syntax Notation (ASN.1) file precisely define the structure of the data used to implement applications conformant to the Recommended Practice. Using the ASN.1 specification, a compiler tool can be used to produce encodings using encoding rules identified in J2945/A. Both this ASN.1 file and the SAE J2735 ASN.1 files are necessary to collectively implement the data structures described in the J2945/A. The combined library can be used by any receiving application (along with the additional logic of the application). SAE J2945/A also provides recommendations for the interface for sending and receiving Road Geometry and Attributes (RGA) messages. It provides the information necessary to build interoperable applications that rely on RGA messages.

SAE J2945/A and this Abstract Syntax Notation (ASN.1) file precisely define the structure of the data used to implement applications conformant to the Recommended Practice. Using the ASN.1 specification, a compiler tool can be used to produce encodings using encoding rules identified in J2945/A. Both this ASN.1 file and the SAE J2735 ASN.1 files are necessary to collectively implement the data structures described in the J2945/A. The combined library can be used by any receiving application (along with the additional logic of the application). SAE J2945/A also provides recommendations for the interface for sending and receiving Road Geometry and Attributes (RGA) messages. It provides the information necessary to build interoperable applications that rely on RGA messages.

This SAE Standard provides a table of textual messages meeting the requirements for expressing the names of street and roads and some basic building blocks for phrases commonly used in the ITS industry. The tables provided herein are taken from SAE J2369, and 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 to provide a means to express street names including pre and post fixes ( North Oak Street is an example name with a prefix “North” and main portion “Oak” and a suffix “Street”). Other phrases exist 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.

This SAE Standard provides a table of textual messages meeting the requirements for expressing the names of street and roads and some basic building blocks for phrases commonly used in the ITS industry. The tables provided herein are taken from SAE J2369, and 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 to provide a means to express street names including pre and post fixes ( North Oak Street is an example name with a prefix “North” and main portion “Oak” and a suffix “Street”). Other phrases exist 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.

This SAE Standard provides a table of textual messages meeting the requirements for expressing “Radio Data Systems” (RDS) phrases commonly used in the ITS industry. They can be used both over the RDS subcarrier transmission media as part of a 37-bit long “Group 8a message” as well as being used to provide a common content list of phrases used in a wide number of other media and applications. This document SHALL define the normative index values to be used, extending the CEN established list to provide phrases needed by US practitioners. This standard provides non-normative textual phrases which MAY be used by implementers to ensure intelligible results. This document 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 document a variety of final table are all considered “compliant” with the document, and may vary as fits the needs of implementers.

This SAE Standard provides a table of textual messages meeting the requirements for expressing “Radio Data Systems” (RDS) phrases commonly used in the ITS industry. They can be used both over the RDS subcarrier transmission media as part of a 37-bit long “Group 8a message” as well as being used to provide a common content list of phrases used in a wide number of other media and applications. This document SHALL define the normative index values to be used, extending the CEN established list to provide phrases needed by US practitioners. This standard provides non-normative textual phrases which MAY be used by implementers to ensure intelligible results. This document 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 document a variety of final table are all considered “compliant” with the document, and may vary as fits the needs of implementers.