Multi-Access Edge Computing --> Vehicle:
potential conflict in progress

This flow may also be implemented by Connected Vehicle Roadside Equipment --> Vehicle: potential conflict in progress

Definitions

potential conflict in progress (Information Flow): Information indicating an unusual situation that might indicate potential for a collision.

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

Vehicle (Destination Physical Object): This 'Vehicle' physical object is used to model core capabilities that are common to more than one type of Vehicle. It provides the vehicle-based general sensory, processing, storage, and communications functions that support efficient, safe, and convenient travel. Many of these capabilities (e.g., see the Vehicle Safety service packages) apply to all vehicle types including personal vehicles (including motorcycles), commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle includes the common interfaces and functions that apply to all motorized vehicles. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle. 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, enhanced driver interfaces, and actuators complement the driver information services so that, in addition to making informed mode and route selections, the driver travels these routes in a safer and more consistent manner. This physical object supports all six levels of driving automation as defined in SAE J3016. Initial collision avoidance functions provide 'vigilant co-pilot' driver warning capabilities. More advanced functions assume limited control of the vehicle to maintain lane position and safe headways. In the most advanced implementations, this Physical Object supports full automation of all aspects of the driving task, aided by communications with other vehicles in the vicinity and in coordination with supporting infrastructure subsystems.

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

Communication Solutions

  • No communications solutions identified.

    • 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).

    Security

    Information Flow Security
      Confidentiality Integrity Availability
    Rating Not Applicable High Moderate
    Basis Typically this information should be distributed to all that might be impacted, and so in a given area should be directly observable. Direct safety impact, so must be correct or negative impact on safety and mobility. Ideally this flow is always availalble, but given practical constraints that is impractical, and this flow is also an overlap with other safety-driving functions.


    Security CharacteristicsValue
    AuthenticableTrue
    Encrypt False