US: SAE Signal Preemption - LTE-V2X TCP

Description:

This solution is used within Canada and 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:

Comm Profile: V-X: LTE-V2X TCP

Comm Class: LAN - Local Area Network

Standards in Profile:
LevelStandard
Access3GPP LTE-V2X (PC5)
Mgmt3GPP: E-UTRA - Radio Resource Control
Mgmt3GPP: NAS protocol for EPS
MgmtSAE J3161 LTE-V2X Deployment Profiles
SecurityBundle: IEEE 1609.2
TransNetBundle: IPv6
TransNetIETF RFC 9293 TCP

Data Profile: US: SAE Signal Preemption

Standards in Profile:
LevelStandard
FacilitiesSAE J2735 DSRC Message Set
FacilitiesSAE J2945 DSRC Common Design Elements
ITS Application EntityCTI 4501 CI Implementation Guide
ITS Application EntityISO 19091 V2I for signalized intersections
ITS Application EntitySAE J2735 DSRC Message Set
ITS Application EntitySAE J2945/B Signal Intersection Applications

Solution Issues Severity: 10

The severity issue score calculation only includes issues associated with standards that are included by default.

Solution Issues:

DefaultSeverityNameTypeDescription
TrueLowData not defined in standard formatITS Info GapThe definition of data concepts should conform to ISO 14817-1 to promote reuse among ITS.
TrueLowNot a standard (minor)Standardization GapThe document is publicly available and widely used but it is not currently a formal standard.
TrueLowOverlap of standards (Minor)OverlapMultiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. However, as this information transfer is infrastructure-based, agencies can deploy a solution throughout their jurisdiction with minimal downside and can use gateways to connect to other technologies.
TrueLowTime synchronizationPerformance / Applicability GapThe standard requires a highly accurate time shared between participants.
TrueMediumNot a standardStandardization GapThe 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.
TrueMediumUncertainty about trust revocation mechanismSecurity GapThe mechanisms used to prevent bad actors from sending authorized messages is unproven.

Solution to Triples

SourceFlowDestination
[Error] - Triple (Src=42,Dst=11,Flow=303) Not found in physical DB. [Error] - Triple (Src=42,Dst=11,Flow=303) Not found in physical DB. [Error] - Triple (Src=42,Dst=11,Flow=303) Not found in physical DB.
[Error] - Triple (Src=42,Dst=9,Flow=303) Not found in physical DB. [Error] - Triple (Src=42,Dst=9,Flow=303) Not found in physical DB. [Error] - Triple (Src=42,Dst=9,Flow=303) Not found in physical DB.
Commercial Vehicle OBE local signal priority request Connected Vehicle Roadside Equipment
Maint and Constr Vehicle OBE local signal priority request Connected Vehicle Roadside Equipment
Maint and Constr Vehicle OBE local signal priority request ITS Roadway Equipment
Transit Vehicle OBE local signal priority request Connected Vehicle Roadside Equipment
Transit Vehicle OBE local signal priority request ITS Roadway Equipment