(None-Data) - LTE-V2X IPv6
Description
This solution is used within Canada and the U.S.. It combines standards associated with (None–Data) with those for V–X: LTE–V2X IPv6. The (None–Data) standards include an unspecified set of standards at the upper layers. The V–X: LTE–V2X IPv6 standards include lower–layer standards that support connectionless vehicle–to–any communications using 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 | Standard(s) need to be developed | One or more standards need to be developed for this subject matter before this is considered a complete solution. | |
| Facilities | Standard(s) need to be developed | One or more standards need to be developed for this subject matter before this is considered a complete solution. | |
| 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 8200 | Internet Protocol, Version 6 | This document specifies version 6 of the Internet Protocol (IPv6). |
| TransNet | IETF RFC 9293 | Transmission Control Protocol | This document specifies the Transmission Control Protocol (TCP). TCP is an important transport–layer protocol in the Internet protocol stack, and it has continuously evolved over decades of use and growth of the Internet. Over this time, a number of changes have been made to TCP as it was specified in RFC 793, though these have only been documented in a piecemeal fashion. This document collects and brings those changes together with the protocol specification from RFC 793. This document obsoletes RFC 793, as well as RFCs 879, 2873, 6093, 6429, 6528, and 6691 that updated parts of RFC 793. It updates RFCs 1011 and 1122, and it should be considered as a replacement for the portions of those documents dealing with TCP requirements. It also updates RFC 5961 by adding a small clarification in reset handling while in the SYN–RECEIVED state. The TCP header control bits from RFC 793 have also been updated based on RFC 3168. |
| 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: Lowest
Readiness Description
Many serious issues. This category includes solutions that have not been standardized, or do not have a basic level of interoperability or security. Consider selecting a different communications solution or if this is not possible (eg. a pilot of a new application that has not been standardized), take additional measures to provide an acceptable level of security or interoperability.
Issues
| Issue | Severity | Description | Associated Standard | Associated Triple |
|---|---|---|---|---|
| Data profile not defined | Ultra | Performance, functionality, and the upper–layers of the OSI stack have not been defined for this information flow. | (None) | (All) |
| Draft not available (Critical) | High | The standards development organization has established a work item for the subject standard but a draft is not available for this critical feature to enable the interface. The draft may be missing due to the work item being new or simply a lack of activity on the work item. | Development needed | (All) |
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Commercial Vehicles=>freight equipment information=>Kansas CVO Check Stations |
| 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) |
| Uncertainty about trust revocation mechanism | Medium | The mechanisms used to prevent bad actors from sending authorized messages is unproven. | Bundle: IEEE 1609.2 | (All) |
Supports Interfaces
| Source | Destination | Flow |
|---|---|---|
| Commercial Vehicles | Kansas CVO Check Stations | freight equipment information |