Search Results

This SAE Information Report describes results of testing of the SAE J1746 ISP-Vehicle Standard for the communication of spatial data references between central sites and mobile vehicles on roads. Testing was performed by the Oak Ridge National Laboratory and its contractors, resulting in a document from which this Information Report has been extracted. Tests were performed by computer analysis and corroborated by field tests with a mobile vehicle.

This SAE Recommended Practice describes the power mode requirements for in-vehicle networks that conform to the Automotive Multimedia Interface Collaboration (AMI-C) specifications. These networks include, but are not limited to, the IDB-C (SAE J2366), IDB-1394, and MOST. This version of the document covers primarily IDB-C and may be revised when the PMODE requirements for the other networks are more fully developed by AMI-C.

This SAE Standard describes the interface between an on-vehicle Mayday detection, reporting system and the off-vehicle response center that will manage the response to the vehicle's call for assistance. The automatic detection and reporting by either the intelligent vehicle itself or by the intelligent roadway of a vehicle that is disabled or involved in an accident, [referred to as Automatic Mayday], is one of the key services identified by the ITS America program plan road map. This effort has been identified, as STD SAE J2313 in recent DOT-FHWA efforts to advance needed National standards. This document primarily addresses the responsibilities of a vehicle in detecting and reporting such an event. Equipment suites on each vehicle will vary widely, as will the communications channel employed to report the incident.

This SAE Information Report describes requirements gathering workshops for Public Sector use of ITS Referencing Datums.

The LRMS is intended to provide a practical approach to standardization for location referencing within a mixed data set environment, i.e., where more than one kind of spatial data set exists, and where spatial references between these data sets must be made. Although some ITS applications in local areas may be satisfied by having one common data set— for which location references may be implemented in any number of ways— many ITS applications will have broad interoperability requirements within the nation or a region. For example, a vehicle driven from California to Florida in the U.S. should be able to receive and understand spatial references for traffic information or routing instructions throughout the trip. Similarly, information sent from a vehicle to a central site should be understood in any city regardless of the kinds of data sets in use, whether they are public or private, or how locations are referenced internally to particular data sets.

This SAE Recommended Practice details the Link Layer of the Intelligent Transportation Systems (ITS) Data Bus, which is generally intended for in-vehicle use. The ITS Data Bus (IDB) is a non-proprietary token passing bus, designed to allow disparate consumer, vehicle, and commercial electronic components to communicate and share information across a standard, open data bus. This first version of the IDB is called IDB-C. This Recommended Practice describes the Link Layer of the IDB-C, as shown in Section 1. Below the Link Layer of the IDB-C is the CAN 2.0B Link Layer. The Physical Layer of the IDB-C incorporates the Physical Layer as specified by SAE J2366-1 and J2590. The IDB-C Link Layer is logically divided into two functional sub-layers, viz., Logical Link Control (LLC) and Media Access Control (MAC). However, these are logical groupings that re-use some of the same bits within the CAN 2.0B frame for efficiency.

This SAE Recommended Practice details the Thin Transport Layer of the Intelligent Transportation Systems (ITS) Data Bus, which is generally intended for in-vehicle use. The Thin Transport Layer sits between SAE J2366-2 and J2366-7. It provides the handling of such activities as the packetizing of long messages and message reassembly. Design of the messages and headers has stressed economy, in terms of bits within a CAN 2.0B frame. The ITS Data Bus (IDB) is a non-proprietary virtual token passing bus, designed to allow disparate consumer, vehicle, and commercial electronic components to communicate and share information across a standard, open data bus. This document describes the Thin Transport Layer of the IDB, as shown in Figure 1.

This SAE Standard outlines the US standard for sending Advanced Traveler Information Services (ATIS) messages over various Bandwidth Reduced Media (BRM). It specifies the “over the air” format and method for such data messages at a bit level. The methodology allows a cooperative sharing of the media’s total bandwidth with other non-ATIS data services. It allows for further expansion to other ATIS messages such as transit schedules and weather use. It uses a common directory of messages to divide out those messages which are the subject of this specification from others. It is built upon the concept of “waveform neutrality” in that it can be hosted by a wide variety of media often found in the delivery of wireless data services (although it is also useful for wire line applications). This message set is incorporated into each medium (“host medium”) by a formatting process specific to each media. A graphical overview ofthis process is shown in Figure 1.

NOTE— SAE J2366-7LX—ITS Data Bus Application Message Layer Lexicon is now combined (as an appendix) with SAE J2366-7 to provide for a quicker revision process in the future. This SAE Surface Vehicle Recommended Practice defines an Application Message Layer, which may be used as part of a complete protocol stack with the other protocol layers in the SAE J2366 family. The Application Message Layer provides application message support for devices that are interconnected via a bus or network. Design of the messages and headers has stressed flexibility, expandability, economy (in terms of octets on the bus), and reusability. The Application Message Layer is independent of the underlying network used, and may be used on any network. Sections of this document make specific reference to the use of SAE J2366-7 with other layers of the SAE J2366 family of protocols, and may not apply when SAE J2366-7 is used with other networks.

This SAE Information Report is a summary of information obtained by way of survey conducted during the 2Q and 3Q of 1997 of MAYDAY system manufacturers. The data represented here has been condensed from the original survey that was conducted by telephone interviews and faxes. The information contained within is limited to technical data as it pertains to vehicle and on-board MAYDAY system operations. It does not contain business, marketing, or any proprietary technical information. The complete survey results are in the possession of the SAE. The purpose of this survey was to determine whether the general concept and architecture on which the SAE J2313 MAYDAY Message Set was being developed is consistent with those of current MAYDAY system hardware manufacturers. The survey was not intended for MAYDAY service providers or public service answer points and emergency service providers.

This SAE Information Report describes a reference model for an in-vehicle data bus for Intelligent Transportation Systems (ITS). It introduces the ITS Data Bus (IDB) reference model and describes overall IDB concepts.

This SAE Recommended Practice details the Physical Layer of the Intelligent Transportation Systems (ITS) Data Bus on CAN (IDB-C), which is generally intended for in-vehicle use. It has been developed by the ITS Data Bus (IDB) Physical Layer Subcommittee of the IDB Committee. The objectives of the subcommittee are to develop information reports, recommended practices and standards concerned with the requirements, design, and usage of devices that communicate electronic signals and control information among ITS related components within the vehicle environment. The IDB-C is a non-proprietary virtual-token passing bus, designed to allow disparate consumer, vehicle, and commercial electronic components to communicate and share information across a standard, open data bus. This document describes the Physical Layer of the IDB-C, as shown in Figure 1. The Physical Layer of the IDB-C incorporates the CAN 2.0B specification per SAE J2284-2, with modifications as noted in this document.

This SAE Information Report represents an information report on a conceptual ITS architecture and its accompanying protocols from the perspective of Advanced Traveller Information Systems providers and users. While a specific logical and physical architecture for ITS is still in the development stages, this conceptual architecture provides a robust general view of ITS functions and interfaces.

This SAE Information Report defines consistent terminology for Intelligent Transportation Systems (ITS). The list of defined terms is followed by a list of acronyms. Certain criteria were used in selecting terms for this document. Terms in widespread use in the ITS community covering significant services, technologies, and applications were chosen. This document focuses on terms used in the United States, although it covers aspects of worldwide ITS deployment. This document focuses on automotive applications, which include interfaces to and from the automobile. Later versions may include a wider scope. ITS includes a wide array of services, applications, and technologies. The Department of Transportation ITS National Program Plan divides ITS into 29 User Services, which are included in this glossary. The User Services range from Pre-Trip Travel Planning to Fully Automated Highway Systems.