(None-Data) - LTE-V2X TCP
Description:
This solution is used within the U.S.. It combines standards associated with (None-Data) with those for V-X: LTE-V2X TCP. The (None-Data) standards include an unspecified set of standards at the upper layers. 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.Relevant Regions:
- United States
Comm Profile: V-X: LTE-V2X TCP
Comm Class: LAN - Local Area Network
Standards in Profile:
Level | Standard |
---|---|
Access | 3GPP LTE-V2X (PC5) |
Mgmt | 3GPP: E-UTRA - Radio Resource Control |
Mgmt | 3GPP: NAS protocol for EPS |
Mgmt | SAE J3161 LTE-V2X Deployment Profiles |
Security | Bundle: IEEE 1609.2 |
TransNet | Bundle: IPv6 |
TransNet | IETF RFC 9293 TCP |
Data Profile: (None-Data)
Standards in Profile:
- None
Solution Issues Severity: 44
The severity issue score calculation only includes issues associated with standards that are included by default.
Solution Issues:
Default | Severity | Name | Type | Description |
---|---|---|---|---|
True | Medium | Overlap of standards | Overlap | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. |
True | Medium | Regulatory Permission Needed | Standardization Gap | Deployment of this standard requires regulatory approval, which is currently subject to significant delays. |
True | Medium | Still under development | Standardization Gap | 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. |
True | Medium | Uncertainty about trust revocation mechanism | Security Gap | The mechanisms used to prevent bad actors from sending authorized messages is unproven. |
True | Ultra | Data profile not defined | Data Profile Gap | Performance, functionality, and the upper-layers of the OSI stack have not been defined for this information flow. |
Solution to Triples
This solution is used on the following information flow triples: