Emergency Vehicle OBE --> Multi-Access Edge Computing:
vehicle location and motion

This flow may also be implemented by Emergency Vehicle OBE --> Connected Vehicle Roadside Equipment: vehicle location and motion

Definitions

vehicle location and motion (Information Flow): Data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size.

Emergency Vehicle OBE (Source Physical Object): The 'Emergency Vehicle On-Board Equipment' (OBE) resides in an emergency vehicle and provides the processing, storage, and communications functions that support public safety-related connected vehicle applications. It represents a range of vehicles including those operated by police, fire, and emergency medical services. In addition, it represents other incident response vehicles including towing and recovery vehicles and freeway service patrols. It includes two-way communications to support coordinated response to emergencies. A separate 'Vehicle OBE' physical object supports the general vehicle safety and driver information capabilities that apply to all vehicles, including emergency vehicles. The Emergency Vehicle OBE supplements these general capabilities with capabilities that are specific to emergency vehicles.

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

This Triple is an instantiation of the more general triple:

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:

  • None

This Triple has the following triple relationships:

None

This Triple is an instantiation of the more general triple:

Communication Solutions

  • No communications solutions identified.

    • This Triple is an instantiation of the more general triple:

    Characteristics

    CharacteristicValue
    Time Context Now
    Spatial Context Adjacent
    Acknowledgement False
    CardinalityUnicast
    InitiatorSource
    AuthenticableTrue
    EncryptFalse


    InteroperabilityDescription
    NationalThis triple should be implemented consistently within the geopolitical region through which movement is essentially free (e.g., the United States, the European Union).

    This Triple is an instantiation of the more general triple:

    Security

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


    Security CharacteristicsValue
    AuthenticableTrue
    Encrypt False