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.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: US: SAE Signal Preemption
Standards in Profile:
| Level | Standard |
|---|---|
| Facilities | SAE J2735 DSRC Message Set |
| Facilities | SAE J2945/0 DSRC Common Design Elements |
| ITS Application Entity | CTI 4501 CI Implementation Guide |
| ITS Application Entity | ISO 19091 V2I for signalized intersections |
| ITS Application Entity | SAE J2735 DSRC Message Set |
| ITS Application Entity | SAE J2945/B Signal Intersection Applications |
Solution Issues Severity: 18
The severity issue score calculation only includes issues associated with standards that are included by default.
Solution Issues:
| Default | Severity | Name | Type | Description |
|---|---|---|---|---|
| True | Low | Data not defined in standard format | ITS Info Gap | The definition of data concepts should conform to ISO 14817-1 to promote reuse among ITS. |
| True | Low | Guidance document under development | Standardization Gap | 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. |
| True | Low | Not a standard (minor) | Standardization Gap | The document is publicly available and widely used but it is not currently a formal standard. |
| True | Medium | Not a standard | Standardization Gap | The document may be publicly available but it is not currently available as a formal standard and details may change prior to adoption as a standard. |
| 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. |
Solution to Triples
This solution is used on the following information flow triples: