(None-Data) - LTE-V2X TCP

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 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:

• Canada
• United States

Comm Profile: V-X: LTE-V2X TCP

Comm Class: LAN - Local Area Network

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)

None

Solution Issues Severity: 45

Solution Issues:

Default	Severity	Name	Type	Description
True	Low	Overlap of standards (Minor)	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. 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.
True	Low	Time synchronization	Performance / Applicability Gap	The standard requires a highly accurate time shared between participants.
True	Medium	Uncertainty about trust revocation mechanism	Security Gap	The mechanisms used to prevent bad actors from sending authorized messages is unproven.
True	High	Draft not available (Critical)	Standardization Gap	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.
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

Source	Flow	Destination
[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
Connected Vehicle Roadside Equipment	transit stop request	Transit Vehicle OBE
Connected Vehicle Roadside Equipment	access violation notification	Vehicle
Light Vehicle OBE	actuate secure payment	Electric Charging Station
Light Vehicle OBE	actuate secure payment	ITS Roadway Payment Equipment
Light Vehicle OBE	actuate secure payment	Parking Area 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
Personal Information Device	transit stop request	Transit Vehicle OBE
Transit Vehicle OBE	local signal priority request	Connected Vehicle Roadside Equipment
Transit Vehicle OBE	local signal priority request	ITS Roadway Equipment
Vehicle	vehicle situation data	Connected Vehicle Roadside Equipment