Multi-Access Edge Computing --> Micromobility Vehicle OBE:
personal crossing safety information

Definitions

personal crossing safety information (Information Flow): Current crossing status including permission to cross, crossing time remaining, and warnings (e.g., a vehicle's trajectory may impact non-motorized users including pedestrians and cyclists).

Multi-Access Edge Computing (Source Physical Object): 'Multi-Access Edge Computing' ((MEC) previously known as mobile edge computing) represents computing devices that operate and are managed like a cloud server, but are deployed at the edge of a network (typically a cellular network, but it could be any network). While not in strict proximity to the transportation network, these systems do benefit from vastly decreased distances to the roadway compared to central systems, and so can provide lower latency than strictly backoffice systems

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:

• VS12: Vulnerable Road User Safety

This triple is associated with the following Functional Objects:

• None

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

• None

This Triple has the following triple relationships:

Communication Solutions

Characteristics

Security