Personal Information Device --> Micromobility Vehicle OBE:
device configuration coordination

This triple is bi-directional. See also Micromobility Vehicle OBE --> Personal Information Device: device configuration coordination

Definitions

device configuration coordination (Information Flow): A handshake between two different devices in the same vehicle or conveyance so the devices don't interfere with each or send conflicting information. This coordination may result in a personal information device (PID) carried by a traveler not transmitting its current location while on board vehicle, a transit vehicle, or a micromobility vehicle transmitting its vehicle profile and current location. For example, in the carry-in scenario, the personal device might go into a 'quiet' mode when carried into the vehicle that is already equipped with an integrated system that can broadcast safety messages.

Personal Information Device (Source Physical Object): The 'Personal Information Device' provides the capability for travelers to receive formatted traveler information wherever they are. Capabilities include traveler information, trip planning, and route guidance. Frequently a smart phone, the Personal Information Device provides travelers with the capability to receive route planning and other personally focused transportation services from the infrastructure in the field, at home, at work, or while en-route. Personal Information Devices may operate independently or may be linked with vehicle on-board equipment. This subsystem also supports safety related services with the capability to broadcast safety messages and initiate a distress signal or request for help.

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 described by the following Functional View Functional Objects:

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

This Triple has the following triple relationships:

Communication Solutions

  • (None-Data) - Local Unicast Wireless (EU) (38)
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) - Local Unicast Wireless (EU)

Solution Description

This solution is used within Australia and the E.U.. It combines standards associated with (None-Data) with those for V-X: Local Unicast Wireless (EU). The (None-Data) standards include an unspecified set of standards at the upper layers. The V-X: Local Unicast Wireless (EU) standards include lower-layer standards that support local-area unicast wireless solutions applicable to the European Union, such as G5, LTE, Wi-Fi, etc.

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 gapMind 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 Unicast
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 Unlikely that any personal or not observable information is included here. Misconfiguration could cause a malfunction or lead to undesireable vehicle behavior. Will only affect the one vehicle, but could be dangerous to the MMV operator. Service cannot operate without this flow, and there is no alternative integrated solution. Listed as 'MODERATE' and not 'HIGH' only because loss of these services would be inconvenient and disadvantageous, particulary to vulnerable road users, but not catastrophic.


Security Characteristics Value
Authenticable True
Encrypt False