US: SAE Signal Preemption - LTE-V2X TCP

Description:

This solution is used within the U.S.. It combines standards associated with US: SAE Signal Preemption with those for V-X: LTE-V2X TCP. The US: SAE Signal Preemption standards include upper-layer standards required to implement signal preemption and priority information flows. The V-X: LTE-V2X TCP standards include lower-layer standards that support connection-oriented vehicle-to-any communications using the Transmission Control Protocol (TCP) over Internet Protocol version 6 (IPv6) over C-V2X in the 5.9GHz spectrum.

Comm Profile: V-X: LTE-V2X TCP

Level	Doc #	Standard	Description
Access	Bundle: 3GPP LTE-V2X	3GPP LTE-V2X (PC5)	This proxy standard represents the subset of the 3GPP Release 14 specification (the last version of 4G) in combination with IEEE 1609.3 and SAE 3161 standards that define Cellular Vehicle-to-Everything (C-V2X), which uses device-to-device communication (PC5) at 5.9GHz without requiring the presence of a base station.
Mgmt	3GPP 36.331	3GPP: E-UTRA - Radio Resource Control	The present document specifies the Radio Resource Control protocol for the radio interface between UE and E-UTRAN as well as for the radio interface between RN and E-UTRAN. The scope of the present document also includes: - the radio related information transported in a transparent container between source eNB and target eNB upon inter eNB handover; - the radio related information transported in a transparent container between a source or target eNB and another system upon inter RAT handover.
Mgmt	3GPP 24.301	3GPP: NAS protocol for EPS	The present document specifies the procedures used by the protocols for mobility management and session management between User Equipment (UE) and Mobility Management Entity (MME) in the Evolved Packet System (EPS). These protocols belong to the non-access stratum (NAS). The EPS Mobility Management (EMM) protocol defined in the present document provides procedures for the control of mobility when the User Equipment (UE) is using the Evolved UMTS Terrestrial Radio Access Network (E-UTRAN). The EMM protocol also provides control of security for the NAS protocols. The EPS Session Management (ESM) protocol defined in the present document provides procedures for the handling of EPS bearer contexts. Together with the bearer control provided by the access stratum, this protocol is used for the control of user plane bearers.
Mgmt	SAE J3161	SAE J3161 LTE-V2X Deployment Profiles	This SAE Standard describes a reference system architecture based on LTE-V2X technology defined in ETSI Release 14. It also describes cross-cutting features unique to LTE-V2X PC5 sidelink (mode 4) that can be used by current and future application standards. The audience for this document includes the developers of applications and application specifications, as well as those interested in LTE-V2X system architecture, testing, and certification.
Security		Bundle: IEEE 1609.2	A bundle of standards that groups a set of IEEE security standards together for easy reference.
TransNet		Bundle: IPv6	A bundle of standards (RFCs) that define the requirements of a typical IPv6 implementation. An implementation may need to consider additional RFCs besides the ones shown.
TransNet	IETF RFC 793	IETF RFC 793 TCP	This standard (RFC) defines the main connection-oriented Transport Layer protocol used on Internet-based networks.

Data Profile: US: SAE Signal Preemption

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:

Multiple significant and 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. Some solutions in this category may also be becoming obsolete from an interoperability perspective and if this is the case, then upgrades should be planned as soon as possible. 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.