US: WAVE Tolling - LTE-V2X TCP
Description:
This solution is used within Canada and the U.S.. It combines standards associated with US: WAVE Tolling with those for V-X: LTE-V2X TCP. The US: WAVE Tolling standards include upper-layer standards required to implement V2I tolling 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:
- Canada
- 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: WAVE Tolling
Standards in Profile:
| Level | Standard |
|---|---|
| Facilities | IEEE 1609.11 WAVE - Elec Payment |
| Facilities | ISO 15628 DSRC Application Layer |
| ITS Application Entity | ISO 14906 EFC - DSRC |
Solution Issues Severity: 19
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 may not be fully defined (low) | ITS Info Gap | The information flow is unclear as to what precisely is needed; the standard may not fully support the needs of the information flow, depending on how it is interpreted. |
| 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 | 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 | Uncertainty about trust revocation mechanism | Security Gap | The mechanisms used to prevent bad actors from sending authorized messages is unproven. |
| True | High | Out of date (high) | Standardization Gap | The standard includes normative references to other standards that have been subject to significant changes that can impact interoperability of systems and the industry has not specified if and how these updates should be implemented for deployments of this standard. |