Other Micromobility Vehicle OBEs --> Micromobility Vehicle OBE:
MMV profile
This triple is bi-directional. See also
Micromobility Vehicle OBE --> Other Micromobility Vehicle OBEs: MMV profile
Definitions
MMV profile (Information Flow): Information about the micromobility vehicle such as type of micromobility vehicle, size and weight, vehicle performance (acceleration, top speed, turning radius) or other data that can be used to classify vehicle eligibility for access to specific lanes or road segments, or its projected path trajectory.
Other Micromobility Vehicle OBEs (Source 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.
Micromobility Vehicle OBE (Destination 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.
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
- US: SAE J3067 (J2735 SE) - LTE-V2X WSMP (20)
- US: SAE J3067 (J2735 SE) - WAVE WSMP (22)
- (None-Data) - BTP/GeoNetworking/G5 (42)
Selected Solution
Solution Description
ITS Application Entity
SAE J3067 |
Click gap icons for more info.
|
||
Mgmt
Addressed Elsewhere |
Facilities
SAE J2945 |
Security
|
|
TransNet
IEEE 1609.3 |
|||
Access
|
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 | Not Applicable | Moderate | Moderate | |
Basis | Information is partially observable, and is unlikely to compromise the vehicle user in any sense. | Some level of assurance that the information is correct is necessary as the information may be used to grant access to limited-access pathways. | Limited access pathways dedicated to particular types of MMVs should be generally available so as to ensure use of the asset. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | False |