Micromobility Vehicle OBE --> Multi-Access Edge Computing:
personal signal service request

This flow may also be implemented by Micromobility Vehicle OBE --> Connected Vehicle Roadside Equipment: personal signal service request

Definitions

personal signal service request (Information Flow): A request for right of way from a personal device that indicates the type of traveler (pedestrian, special needs pedestrian, bicyclist, etc.), anticipated time of arrival, travel path, and crossing duration.

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.

Multi-Access Edge Computing (Destination 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

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

  • No communications solutions identified.
  • Characteristics

    CharacteristicValue
    Time Context Recent
    Spatial Context Regional
    Acknowledgement True
    CardinalityUnicast
    InitiatorSource
    AuthenticableTrue
    EncryptFalse


    Security

    Information Flow Security
      Confidentiality Integrity Availability
    Security levels have not been defined yet.


    Security CharacteristicsValue
    AuthenticableTrue
    Encrypt False