US: SAE Signal Control Messages - WAVE WSMP

Description:

This solution is used within the U.S.. It combines standards associated with US: SAE Signal Control Messages with those for V-X: WAVE WSMP. The US: SAE Signal Control Messages standards include upper-layer standards required to implement signal control information flows. The V-X: WAVE WSMP standards include lower-layer standards that support connectionless, near constant, ultra-low latency vehicle-to-any communications within ~300m using the WAVE Short Messaging Protocol (WSMP) over IEEE WAVE in the 5.9GHz spectrum. The broadcast mode is interoperable with M5 FNTP.

Comm Profile: V-X: WAVE WSMP

Level	Doc #	Standard	Description
Access		Bundle: WAVE - Subnet	A bundle of standards specifying the lower layers of the reference communications model for the US DSRC environment.
Security		Bundle: IEEE 1609.2	A bundle of standards that groups a set of IEEE security standards together for easy reference.
TransNet	IEEE 1609.3	IEEE 1609.3 WAVE - Networking Services	This standard defines the network and transport layer options for the WAVE environment. The standard defines three options: a bandwidth efficient single-hop solution known as WSMP, UDP/IP, and TCP/IP. It has been harmonized with ISO FNTP and FSAP - a common message format specified in ISO 16460.

Data Profile: US: SAE Signal Control Messages

Level	Doc #	Standard	Description
Facilities	SAE J2735	SAE J2735 DSRC Message Set	This standard defines the data and messages for use in DSRC (i.e., V2V, V2I, and V2D) applications. The SAE J2945 series defines additional requirements on how to use these messages.
Facilities	SAE J2945	SAE J2945/0 DSRC Common Design Elements	This standard defines cross-cutting material which applies to the J2945/x series including generic DSRC interface requirements and guidance on Systems Engineering (SE) content.
ITS Application Entity	CEN ISO 19091	ISO 19091 V2I for signalized intersections	This technical specification defines messages and related data structures and data elements for the following exchanges between roadside equipment and vehicles: 1) Definition of the SPaT (signal phase and timing) message transmitted from a traffic controller that describes the state of the signals, signal timing as necessary to support the applications identified herein; 2) definition of the MAP message (which include the definition of motorized lane, vehicles, busses, trams, bicycle, pedestrian crosswalks, etc.); and 3) definition of the messages (SRM, SSM) to be exchanged between an intersection traffic controller and approaching vehicles to support priority treatment as might be expected for emergency response , freight transport, and public transport vehicles to improve safety.
ITS Application Entity	SAE J2735	SAE J2735 DSRC Message Set	This standard defines the data and messages for use in DSRC (i.e., V2V, V2I, and V2D) applications. The SAE J2945 series defines additional requirements on how to use these messages.
ITS Application Entity	SAE J2945/B	SAE J2945/B Signal Intersection Applications	This document provides guidance on usage of SAE J2735 and other related information for signalized intersection applications. The document focuses on how to use SPaT and MAP messages to support signalized-intersection applications. In general, implementation guidance is necessary to achieve interoperability by addressing the requirements for the options for both over the air dialogs and message contents, and to support larger intersection maps This document also addresses using Signal Request & Signal Status messages corresponding to vehicle functionality and approaches to traffic signal priority/pre-emption (TSP), including three different methods for implementing TSP over the air. The project is complementary to the connected intersections project being performed by ITE.

Readiness Description:

Two significant or one significant and several minor issues. For existing deployments, the chosen solution is likely deficient in security or management capabilities and the issues should be reviewed and upgrades developed as needed. For new deployments, the solution may be viable for pilots when applied to the triples it supports; such pilot deployments should consider a path to addressing these issues as a part of their design activities. The solution does not provide sufficient interoperability, management, and security to enable proper, full-scale deployment without additional work.