Criteria

Text:
Display:

Results

Viewing 1 to 27 of 27
CURRENT
2017-12-07
Standard
J2945_201712
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.
2017-06-23
WIP Standard
J2945/3
This effort will serve for the development of a new standard to define requirements to support V2I weather applications interface in a connected vehicle environment. USDOT has provided funding for this standard and has requested that the Technical Committee (TC) approve using the Systems Engineering Process (SEP) as defined in J2945/0. Initial works in the field of road weather applications have been conducted by stakeholders from both the public and private sector. USDOT has offered a high level Concept of Operations for Road Weather Connected Vehicle and Automated Vehicle Applications to the TC as a basis for consideration to initiate the dialog for J2945/3. This Concept of Operations contains 8 Proposed Applications and 13 Operational Scenarios for the TC and V2I TF to consider. The TC also has material in SAE J3067 as a basis for its consideration. The focus is on information exchanges between the infrastructure and connected vehicles.
CURRENT
2017-03-21
Standard
J2945/9_201703
This document provides recommendations of safety message minimum performance requirements between a Vulnerable Road User (VRU) and a vehicle. It addresses the transmission of Personal Safety Messages (PSM) from road user devices carried by pedestrians, bicycle riders and public safety personnel, to provide driver and vehicle system awareness and potentially offer safety alerts to VRUs. This document includes the recommendation of standards profiles, function descriptions and minimum performance requirements for transmitting the SAE J2735-defined PSM [1] over a Dedicated Short Range Communications (DSRC) Wireless communication link as defined in the Institute of Electrical and Electronics Engineers (IEEE) 1609 and the IEEE 802.11 Standards [[1]]-[5]].
2016-09-30
WIP Standard
J2945/4
This standard will serve to re-work and extend the existing SAE J2735 message elements in order to include additional travel and roadway information from the infrastructure to enhance safety awareness and promote the exchange and transfer of such messages types between vehicles and the infrastructure (V2I). Fundamentally this document will outline the needs and detail the system requirements to support a variety of use cases linking to the J2735 effort as other J2945/x documents do. The initial scope will be to revise the structure of the existing “TIM” message to reflect the lessons learned from the various deployment activities such as the BIM developed by an automotive OEM consortium. The objective is to improve the general functionality of the message set in key areas such as message linking, content segmentation, message forwarding within a security framework, and new application areas beyond what is enabled by the TIM.
2016-07-27
WIP Standard
J2945/12
This recommended practice will provide guidance on Traffic Probe Use data to manufacturers that are either Transportation System Management (TSM) core or aligned entities. The recommended practice originates from prior work of the Society of Automotive Engineers (SAE) Dedicated Short Range Communication (DSRC) Technical Committee, as well as existing practices implemented by industry, academia and government. The recommended practice informs manufacturers and practitioners of message use and operation within an automated collection system involved in the orchestration of safe, efficient, and reliable movement of people and goods. The recommended practice for Traffic Probe Use and Operation will support practitioners through the definition of message structure, on-board processing and storage requirements, the operational preservation of vehicle anonymity, and message event management criteria.
2016-04-05
WIP Standard
J2945/11
This effort will be a recommend best practices document outlining how to use the J2735 Signal Request and Signal Status messages in the standard relating to signalized systems status. It primary content will deal with explaining and demonstrating by small working examples how these messages are constructed and used to meet operational needs of user. Particular attention will be paid to the interaction between the SAE work and the relevant NTCIP standards used in the signal control system. [The SAE J2735 document, being a data dictionary and not a guide, allowed only a brief summary of this sort of material.] The intended audience for this effort are those developing new deployment using these messages in connection with intersection safety applications. This will be a recommend practice, not a standard.
2016-04-05
WIP Standard
J2945/10
This effort will be a recommend best practices document outlining how to use the current MAP and SPAT message content found in the recently published J2735. It’s primary content will deal with better explaining and demonstrating by small working examples of how suitable messages are constructed and used to meet operational needs of user. [The SAE J2735 document, being a data dictionary and not a guide, allowed only a briefs summary of this sort of material.] The intended audience for this effort are those developing new deployment using these messages in connection with intersection safety applications. This will be a recommend practice, not a standard.
CURRENT
2016-03-30
Standard
J2735_201603
This SAE Standard specifies a message set, and its data frames and data elements, specifically 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. Although the scope of this Standard is focused on DSRC, this message set, and its data frames and data elements, have been designed, to the extent possible, to be of potential use for applications that may be deployed in conjunction with other wireless communications technologies as well. This Standard therefore specifies the definitive message structure and provides sufficient background information to allow readers to properly interpret the message definitions from the point of view of an application developer implementing the messages according to the DSRC Standards.
CURRENT
2016-03-30
Standard
J2945/1_201603
This standard specifies the system requirements for an on-board vehicle-to-vehicle (V2V) safety communications system for light vehicles1, including standards profiles, functional requirements, and performance requirements. The system is capable of transmitting and receiving the Society of Automotive Engineers (SAE) J2735-defined Basic Safety Message (BSM) [1] over a Dedicated Short Range Communications (DSRC) wireless communications link as defined in the Institute of Electrical and Electronics Engineers (IEEE) 1609 suite and IEEE 802.11 standards [2] – [6].
CURRENT
2016-03-30
Standard
J2735SET_201603
This Abstract Syntax Notation (ASN.1) File is the precise source code used for SAE International Standard J2735. As part of an international treaty, all US ITS standards are expressed in "ASN.1 syntax". ASN.1 Syntax is used to define the messages or "ASN specifications". Using the ASN.1 specification, a compiler tool produces the ASN library which will then be used to produce encodings (The J2735 message set uses UPER encoding). The library is a set of many separate files that collectively implement the encoding and decoding of the standard. The library is then used by any application (along with the additional logic of that application) to manage the messages. The chosen ASN tool is used to produce a new copy of the library when changes are made and it is then linked to the final application being developed. The ASN library manages many of the details associated with ASN syntax, allowing for subtle manipulation to make the best advantage of the encoding style.
CURRENT
2016-03-30
Standard
J2735ASN_201603
This Abstract Syntax Notation (ASN.1) File is the precise source code used for SAE International Standard J2735. As part of an international treaty, all US ITS standards are expressed in "ASN.1 syntax". ASN.1 Syntax is used to define the messages or "ASN specifications". Using the ASN.1 specification, a compiler tool produces the ASN library which will then be used to produce encodings (The J2735 message set uses UPER encoding). The library is a set of many separate files that collectively implement the encoding and decoding of the standard. The library is then used by any application (along with the additional logic of that application) to manage the messages. The chosen ASN tool is used to produce a new copy of the library when changes are made and it is then linked to the final application being developed. The ASN library manages many of the details associated with ASN syntax, allowing for subtle manipulation to make the best advantage of the encoding style.
HISTORICAL
2016-01-19
Standard
J2735_201601
This SAE Standard specifies a message set, and its data frames and data elements, specifically 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. Although the scope of this Standard is focused on DSRC, this message set, and its data frames and data elements, have been designed, to the extent possible, to be of potential use for applications that may be deployed in conjunction with other wireless communications technologies as well. This Standard therefore specifies the definitive message structure and provides sufficient background information to allow readers to properly interpret the message definitions from the point of view of an application developer implementing the messages according to the DSRC Standards.
HISTORICAL
2015-09-02
Standard
J2735_201509
This SAE Standard specifies a message set, and its data frames and data elements specifically 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. Although the scope of this Standard is focused on DSRC, this message set, and its data frames and data elements have been designed, to the extent possible, to also be of potential use for applications that may be deployed in conjunction with other wireless communications technologies. This Standard therefore specifies the definitive message structure and provides sufficient background information to allow readers to properly interpret the message definitions from the point of view of an application developer implementing the messages according to the DSRC Standards.
2015-03-24
WIP Standard
J2945/2
DSRC interface requirements for V2V Safety Awareness applications, including detailed Systems Engineering documentation (needs and requirements mapped to appropriate message exchanges)
2015-01-27
WIP Standard
J2945/6
This document provides recommendations for enhancements to ACC by the addition of wireless communication from relevant vehicles (V2V) and/or the infrastructure (I2V) to augment the ACC active sensing capability. The CACC system operates under driver responsibility and supervision and is limited to the following: • does only longitudinal control of the vehicle. • uses time gap control strategy similar to ACC. Motor vehicles covered in the scope of this document include light and heavy vehicles. The new message elements to realize CACC and platooning is part of the scope. The effort may result in identifying new message, data frames and data elements in SAE J2735. The initial release covers definitions for CACC and platooning and requirements for CACC, while a subsequent release will cover the platooning requirements.
CURRENT
2014-08-26
Standard
J3067_201408
This document is not a standard, it is a candidate for a standard being submitted to SAE for their consideration as a comment to SAE J2735. The term SAE J2735 SE candidate is used within this document to refer to this submission. This document specifies dialogs, messages, and the data frames and data elements that make up the messages specifically 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. Although the scope of this Standard is focused on DSRC, these dialogs, messages, data frames and data elements have been designed, to the extent possible, to be of use for applications that may be deployed in conjunction with other wireless communications technologies.
CURRENT
2009-11-19
Standard
J2540/2_200911
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.
HISTORICAL
2009-11-19
Standard
J2735_200911
This SAE Standard specifies a message set, and its data frames and data elements specifically 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. Although the scope of this Standard is focused on DSRC, this message set, and its data frames and data elements have been designed, to the extent possible, to also be of potential use for applications that may be deployed in conjunction with other wireless communications technologies. This Standard therefore specifies the definitive message structure and provides sufficient background information to allow readers to properly interpret the message definitions from the point of view of an application developer implementing the messages according to the DSRC Standards.
HISTORICAL
2006-12-19
Standard
J2735_200612
This SAE Recommended Practice is intended as a guide toward standard practice and is subject to chagne 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"), communication 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.
CURRENT
2004-10-29
Standard
J2266_200410
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.
CURRENT
2004-02-10
Standard
J2354_200402
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.).
CURRENT
2003-12-02
Standard
J2630_200312
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.
CURRENT
2002-07-25
Standard
J2540_200207
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: Methods and Data Elements for handling indexes and strings in ATIS applications and message sets Message Sets to support the delivery and translations of tables used in such strings 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.
CURRENT
2002-07-25
Standard
J2540/1_200207
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.
CURRENT
2002-02-22
Standard
J2539_200202
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.
CURRENT
2002-01-23
Standard
J2540/3_200201
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.
CURRENT
1999-10-19
Standard
J2353_199910
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.
Viewing 1 to 27 of 27