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.
Includes Standards
| Level | DocNum | FullName | Description |
|---|---|---|---|
| Mgmt | 3GPP 24.301 | 3rd Generation Partnership Project;Technical Specification Group Radio Access Network; Non–Access–Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | 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 | LTE Vehicle–to–Everything (LTE–V2X) Deployment Profiles and Radio Parameters for Single Radio Channel Multi–Service Coexistence | 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. |
| Mgmt | 3GPP 36.331 | 3rd Generation Partnership Project;Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E–UTRA); Radio Resource Control (RRC); Protocol specification | 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. |
| Security | IEEE 1609.2 | IEEE Standard for Wireless Access in Vehicular Environments – Security Services for Applications and Management Messages | This standard defines secure message formats and processing for use by Wireless Access in Vehicular Environments (WAVE) devices, including methods to secure WAVE management messages and methods to secure application messages. It also describes administrative functions necessary to support the core security functions. |
| Security | IEEE 1609.2a | IEEE 1609.2a–2017 – IEEE Standard for Wireless Access in Vehicular Environments––Security Services for Applications and Management Messages – Amendment 1 | This standard defines secure message formats and processing for use by Wireless Access in Vehicular Environments (WAVE) devices, including methods to secure WAVE management messages and methods to secure application messages. It also describes administrative functions necessary to support the core security functions. |
| Security | IEEE 1609.2b | IEEE Standard for Wireless Access in Vehicular Environments––Security Services for Applications and Management Messages – Amendment 2––PDU Functional Types and Encryption Key Management | This standard defines secure message formats and processing for use by Wireless Access in Vehicular Environments (WAVE) devices, including methods to secure WAVE management messages and methods to secure application messages. It also describes administrative functions necessary to support the core security functions. |
| ITS Application Entity | CEN ISO 19091 | Intelligent transport systems –– Cooperative ITS –– Using V2I and I2V communications for applications related to 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 | Dedicated Short Range Communications (DSRC) Message Set Dictionary (TM) | 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 | Recommended Practices for Signalized 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. |
| Facilities | SAE J2735 | Dedicated Short Range Communications (DSRC) Message Set Dictionary (TM) | 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 | Dedicated Short Range Communication (DSRC) Systems Engineering Process Guidance for J2945/x Documents and Common Design Concepts | 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. |
| TransNet | IETF RFC 2460 | Internet Protocol, Version 6 (IPv6) Specification | This standard (RFC) specifies version 6 of the Internet Protocol (IPv6), also sometimes referred to as IP Next Generation or IPng. |
| TransNet | IETF RFC 4291 | IP Version 6 Addressing Architecture | This standard (RFC) defines the addressing architecture of the IP Version 6 (IPv6) protocol. It includes the IPv6 addressing model, text representations of IPv6 addresses, definition of IPv6 unicast addresses, anycast addresses, and multicast addresses, and an IPv6 node's required addresses. |
| TransNet | IETF RFC 4443 | Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification | This standard (RFC) defines the control messages to manage IPv6. |
| TransNet | IETF RFC 793 | Transmission Control Protocol | This standard (RFC) defines the main connection–oriented Transport Layer protocol used on Internet–based networks. |
| Access | 3GPP 36.211 | 3rd Generation Partnership Project;Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E–UTRA); Physical channels and modulation | The present document describes the physical channels for evolved UTRA. |
| Access | 3GPP 36.212 | 3rd Generation Partnership Project;Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E–UTRA); Multiplexing and channel coding | The present document specifies the coding, multiplexing and mapping to physical channels for E–UTRA |
| Access | 3GPP 36.213 | 3rd Generation Partnership Project;Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E–UTRA); Physical layer procedures | The present document specifies and establishes the characteristics of the physicals layer procedures in the FDD and TDD modes of E–UTRA. |
| Access | 3GPP 36.214 | 3rd Generation Partnership Project;Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E–UTRA); Physical layer; Measurements | The present document contains the description and definition of the measurements done at the UE and network in order to support operation in idle mode and connected mode. |
| Access | 3GPP 36.300 | 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E–UTRA) and Evolved Universal Terrestrial Radio Access Network (E–UTRAN); Overall description | The present document provides an overview and overall description of the E–UTRAN radio interface protocol architecture. Details of the radio interface protocols are specified in companion specifications of the 36 series. For Multi–Connectivity involving E–URAN, the differences relative to E–UTRA and E–UTRAN are specified in 3GPP TS 37.340. |
| Access | 3GPP 36.321 | 3rd Generation Partnership Project;Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E–UTRA); Medium Access Control (MAC) protocol specification | The objective is to describe the MAC architecture and the MAC entity from a functional point of view. Functionality specified for the UE equally applies to the RN for functionality necessary for the RN. There is also functionality which is only applicable to the RN, in which case the specification denotes the RN instead of the UE. RN–specific behaviour is not applicable to the UE. For TDD operation, UE behaviour follows the TDD UL/DL configuration indicated by tddConfig unless specified otherwise. |
| Access | 3GPP 36.322 | 3rd Generation Partnership Project;Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E–UTRA);Radio Link Control (RLC) protocol specification | The present document specifies the E–UTRA Radio Link Control (RLC) protocol for the UE – E–UTRAN radio interface. |
| Access | 3GPP 36.323 | 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E–UTRA); Packet Data Convergence Protocol (PDCP) specification | The present document describes the functionality of the PDCP. Functionality specified for the UE equally applies to the RN for functionality necessary for the RN. There is also functionality which is only applicable to the RN in its communication with the E–UTRAN, in which case the specification denotes the RN instead of the UE. RN–specific behaviour is not applicable to the UE. The functionality specified for the UE applies to communication on Uu interface and PC5 interface. |
Readiness: Moderate–Low
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.
Issues
| Issue | Severity | Description | Associated Standard | Associated Triple |
|---|---|---|---|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | 3GPP LTE–V2X (PC5) | (All) |
| Regulatory Permission Needed | Medium | Deployment of this standard requires regulatory approval, which is currently subject to significant delays. | 3GPP LTE–V2X (PC5) | (All) |
| Still under development | Medium | A draft of the standard has been developed by the working group, but it was still under development at the time this analysis was performed. | SAE J3161 LTE–V2X Deployment Profiles | (All) |
| Uncertainty about trust revocation mechanism | Medium | The mechanisms used to prevent bad actors from sending authorized messages is unproven. | Bundle: IEEE 1609.2 | (All) |
| Data not defined in standard format | Low | The definition of data concepts should conform to ISO 14817–1 to promote reuse among ITS. | SAE J2735 DSRC Message Set | (All) |
| Guidance document under development | Low | This recommended practice on how to use the related standards is still under development but is not seen as strictly necessary to begin deployment of equipment. | SAE J2945/B Signal Intersection Applications | (All) |
| Not a standard (minor) | Low | The document is publicly available and widely used but it is not currently a formal standard. | ISO 19091 V2I for signalized intersections | (All) |
Supports Interfaces
| Source | Destination | Flow |
|---|---|---|
| BCTA Transit Vehicles | City of Pittsburgh Field Devices | local signal priority request |
| BCTA Transit Vehicles | Municipal Field Devices | local signal priority request |
| Local Fire and EMS Vehicles | City of Pittsburgh Field Devices | local signal preemption request |
| Local Fire and EMS Vehicles | Municipal Field Devices | local signal preemption request |
| PRT Transit Vehicles | City of Pittsburgh Field Devices | local signal priority request |
| PRT Transit Vehicles | Municipal Field Devices | local signal priority request |
| Regional Transit Vehicles | City of Pittsburgh Field Devices | local signal priority request |
| Regional Transit Vehicles | Municipal Field Devices | local signal priority request |