Connected Vehicle Roadside Equipment --> Other Connected Vehicle Roadside Equipment:
detected unequipped vehicles and VRUs

This triple is bi-directional. See also Other Connected Vehicle Roadside Equipment --> Connected Vehicle Roadside Equipment: detected unequipped vehicles and VRUs

Definitions

detected unequipped vehicles and VRUs (Information Flow): Notification of a nearby vehicle (light vehicle, commercial vehicle, MMV etc.) or vulnerable road user that does not appear to be equipped with a short range communications device but is detectable using onboard vehicle or infrastructure sensors. The flow communicates detected vehicle/VRU location, physical characteristics, observable kinematics and confidence in those measures.

Connected Vehicle Roadside Equipment (Source Physical Object): 'Connected Vehicle Roadside Equipment' (CV RSE) represents the Connected Vehicle roadside devices (i.e., Roadside Units (RSUs)) equipped with short range wireless (SRW) communications technology, as well as any other supporting equipment that leverage the RSU and are not described by other objects (e.g., a local roadside processor). CVRSE are used to send messages to, and receive messages from, nearby vehicles and personal devices equipped with compatible communications technology. Communications with adjacent field equipment and back office centers that monitor and control the RSE are also supported. This device operates from a fixed position and may be permanently deployed or a portable device that is located temporarily in the vicinity of a traffic incident, road construction, or a special event. It includes a processor, data storage, and communications capabilities that support secure communications with passing vehicles, other field equipment, and centers.

Other Connected Vehicle Roadside Equipment (Destination Physical Object): Representing another Connected Vehicle Roadside Equipment, 'Other Connected Vehicle Roadside Equipment' supports peer to peer communication and direct coordination between RSEs. It provides a source and destination for information that may be exchanged between RSEs.

Included In

This Triple is in the following Service Packages:

This triple is associated with the following Functional Objects:

This Triple is described by the following Functional View Data Flows:

This Triple has the following triple relationships:

None

Communication Solutions

Solutions are sorted in ascending Gap Severity order. The Gap Severity is the parenthetical number at the end of the solution.

Selected Solution

US: SAE Sensor Data Sharing - LTE-V2X WSMP

Solution Description

This solution is used within Canada and the U.S.. It combines standards associated with US: SAE Sensor Data Sharing with those for V-X: LTE-V2X WSMP. The US: SAE Sensor Data Sharing standards include upper-layer standards required to enable sharing of sensor data between equipped devices. The V-X: LTE-V2X WSMP standards include lower-layer standards that support connectionless, near constant, ultra-low latency vehicle-to-any communications using the WAVE Short Messaging Protocol (WSMP) over 3GPP C-V2X in the 5.9GHz spectrum.

ITS Application Entity
Mind the gap

SAE J2735
SAE J3224
Click gap icons for more info.
Mgmt

SAE J3161
3GPP 24.301
3GPP 36.331
Facilities
Mind the gap

SAE J2735
SAE J2945
Security
Mind the gap
TransNet

IEEE 1609.3
Access
Mind the gapMind the gap
TransNet TransNet

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Access Access

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

ITS Application ITS Application

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Mgmt Mgmt

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Facility Facility

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Security Security

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Note that some layers might have alternatives, in which case all of the gap icons associated with every alternative may be shown on the diagram, but the solution severity calculations (and resulting ordering of solutions) includes only the issues associated with the default (i.e., best, least severe) alternative.

Characteristics

Characteristic Value
Time Context Now
Spatial Context Adjacent
Acknowledgement False
Cardinality Broadcast
Initiator Source
Authenticable True
Encrypt False


Interoperability Description
National This triple should be implemented consistently within the geopolitical region through which movement is essentially free (e.g., the United States, the European Union).

Security

Information Flow Security
  Confidentiality Integrity Availability
Rating Not Applicable High Moderate
Basis This data is intended to be shared with all nearby vehicles, traffic control devices and vulnerable road users; it is essentially public. This data may be used as input to vehicle situational awareness and thus trigger crash-avoidance actions. If manipulated or incorrect, a crash may occur; though vehicles able to use this data also have sensory capabilities, this flow will often contain data describing objects/vehicles/VRUs that are obscured and not observable by on-board sensors. This data may be used as input to vehicle situational awareness and thus trigger crash-avoidance actions. This data enable collision avoidance actions that are impractical without it, as vehicles able to use this data to sense-by-proxy other vehicles/VRUs/obstacles that are obscured by on-board sensors. Considered MODERATE and not HIGH only because the lack of availability reverts to existing operations and does not actively make safety worse.


Security Characteristics Value
Authenticable True
Encrypt False