Micromobility Vehicle OBE --> Other Micromobility Vehicle OBEs:
VRU cluster information

This triple is bi-directional. See also Other Micromobility Vehicle OBEs --> Micromobility Vehicle OBE: VRU cluster information

Definitions

VRU cluster information (Information Flow): Information indicating the formation and management of strings of VRUs and micromobility vehicles, which includes human powered vehicles such as bicycles, that may follow each other towards a common destination. This flow also supports identification of the lead MMV in the string so other MMVs can opt-in to join the string. The indication of participating in a string provides better predicted path trajectory prediction for all participating MMVs, enhancing safety. This flow also supports dissolution of MMV strings as MMVs depart from the string.

Micromobility Vehicle OBE (Source Physical Object): The Micromobility Vehicle On-Board Equipment (MMV OBE) provides the vehicle-based sensory, processing, storage, and communications functions that support efficient, safe, and convenient travel. The MMV OBE includes general capabilities that apply to bicycles and other low-powered mobility devices such as e-scooters, powered wheelchairs, and power assisted bicycles. The MMV OBE includes the common interfaces and functions that could apply to any low-powered mobility device. The radio(s) supporting V2V and V2I communications are a key component of the MMV OBE. Both one-way and two-way communications options support a spectrum of information services from basic broadcast to advanced personalized information services. Advanced sensors, processors, and enhanced traveler interfaces (through PIDs), complement traveler information services so that, in addition to making informed mode and route selections, the vulnerable road user travels these routes in a safer and more consistent manner.

Other Micromobility Vehicle OBEs (Destination Physical Object): 'Other Micromobility Vehicle OBEs' represents other connected low-powered mobility devices that are communicating with a host micromobility vehicle OBE. This includes all connected PIDs, personnel devices, and micromobility vehicles that supports communications among vulnerable road users (P2P). This object provides a source and destination for information transfers between connected vulnerable road users. The host micromobility vehicle OBE sends information to, and receives information from the micromobility vehicle OBE to model communications between connected micromobility vehicles in ARC-IT.

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:

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

(None-Data) - WAVE WSMP

Solution Description

This solution is used within the U.S.. It combines standards associated with (None-Data) with those for V-X: WAVE WSMP. The (None-Data) standards include an unspecified set of standards at the upper layers. The V-X: WAVE WSMP standards include lower-layer standards that support connectionless, near constant, ultra-low latency vehicle-to-any communications within ~300m using the WAVE Short Messaging Protocol (WSMP) over IEEE WAVE in the 5.9GHz spectrum. The broadcast mode is interoperable with M5 FNTP.

ITS Application Entity
Mind the gap

Development needed
Click gap icons for more info.

Mgmt

Addressed Elsewhere
Facilities

Development needed
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 Recent
Spatial Context Regional
Acknowledgement True
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 Low High Moderate
Basis Information intentionally shared with surrounding users that might cooperate. Initial use cases suggest broadcast-mode communications, and no presumption of obfuscation. MMV clustering applications need timeliness and protection of data to ensure that platooning-like operations happen without incident. Data integrity protections rated higher than availability because incorrect/modified data could lead to catastrophic consequences given the lack of protection that most MMVs offer, and the fact that they operate in close proximity to pedestrians. MMV clustering applications need timeliness and protection of data to ensure that platooning-like operations happen without incident. Data integrity protections rated higher than availability because incorrect/modified data could lead to catastrophic consequences given the lack of protection that most MMVs offer, and the fact that they operate in close proximity to pedestrians.


Security Characteristics Value
Authenticable True
Encrypt False