Standards List

This document describes the triggering conditions for a critical driving situation where the Impact Reduction Containers (IRCs) of potential collision opponents shall be exchanged.

This document describes the triggering conditions for the special vehicle warning. The vehicle C-ITS service is divided in the following two sub-services:
• ‘special vehicle warning – emergency, recovery, prioritized vehicle approaching’;
• ‘special vehicle warning – emergency, recovery, prioritized vehicle at a location’;

This document describes the triggering conditions for stationary vehicle warning for the following three vehicle C-ITS service:
• ‘stationary vehicle warning – stopped vehicle’;
• ‘stationary vehicle warning – broken-down vehicle’;
• ‘stationary vehicle warning – post-crash’.

This document describes the triggering conditions for traffic condition warning for the following two vehicle C-ITS services:
• traffic condition – sudden speed drop
• traffic condition – local slow down

This SAE Recommended Practice establishes a uniform, powered vehicle test procedure and minimum performance requirement for lane departure warning systems used in highway trucks and buses greater than 4546 kg (10000 pounds) GVW. Systems similar in function but different in scope and complexity, including Lane Keeping/Lane Assist and Merge Assist, are not included in this document. This document does not apply to trailers, dollies, etc. This document does not intend to exclude any particular system or sensor technology.
The specification will test the functionality of the LDWS (e.g., ability to detect lane presence, and ability to detect an unintended lane departure), its ability to indicate LDWS engagement, its ability to indicate LDWS disengagement, and determine the point at which the LDWS notifies the Human Machine Interface (HMI) or vehicle control system that a lane departure event is detected. Moreover, the specification determines whether a system performs at a minimally acceptable level. The HMI is not addressed herein but is considered in SAE Standard J2808.

This report presents the results of the 5GAA work item Use Case Implementation Description (UCID) [1].
The objectives of the work item are to develop:
• Use Case Implementation Descriptions (UCIDs) that meet/realise the service level requirements (SLRs) [11] for the use cases:
o Cross-Traffic Left-Turn Assist (LTA)
o Emergency Brake Warning (also referred to Electronic Emergency Brake Light Warning or ‘EEBL Warning’)
o Traffic Jam Warning and Route Information
• Overarching application system implementation specifications combining the respective use case implementation specifications, including potential interfaces to the network and security layers. Note that this is also the template and foundation for developing future-oriented use cases (like Group Start) that are developed for example in the context of the NRV2X xWI.

This SAE standard specifies a message set, and its data frames and data elements, for use by applications that use vehicle-to-everything (V2X) communications systems. While the data dictionary was originally designed for use over DSRC, this document is intended to be independent of the underlying communications protocols used to exchange data between participants in V2X applications.

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.

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.

As the first known physical in-vehicle evaluation of C-V2X, the test specification focuses on communications performance. It is presumed that much of the higher-layer research and development for DSRC is directly portable to C-V2X and thus does not require independent validation. For example, the testing described will implement the same or similar message structures and payload - that have been well established for DSRC or ITS-G5 V2X. Whilst conducting the tests for the purpose of comparing C-V2X and 802.11p based V2X-communications, the higher layers will not be changed. This also means that the messages exchanged during the tests are either the Cooperative Awareness Message (for the European ETSI ITS G5 stack) or the Basic Safety Message (for the DSRC used in the United States of America).
In addition to the communications-layer testing, we have included rudimentary application-level testing to provide assurance that C-V2X system functions as intended and to identify unforeseen issues with the higher layer integration. It is expected that through testing, researchers will gain insights into the operations of C-V2X that may guide additional research questions and perhaps suggest required design improvements.
It is also important to note that this test specification does not represent a complete duplication of the entire work performed by CAMP and/or others on the development of DSRC. Rather, this is a targeted effort that reflects a specific set of tests that are believed to be critical towards evaluating the efficacy of C-V2X communication technology within the V2V application space. Within this set of tests, applying identical methods from DSRC to C-V2X may not be feasible in all instances. This will be indicated in the respective description of test procedures. While the first version of this document focuses on V2V testing, upcoming versions will also include V2I, V2P, V2N.