ITS Roadway Equipment --> Multi-Access Edge Computing:
incident scene warning notification

This triple is bi-directional. See also Multi-Access Edge Computing --> ITS Roadway Equipment: incident scene warning notification
This flow may also be implemented by ITS Roadway Equipment --> Connected Vehicle Roadside Equipment: incident scene warning notification

Definitions

incident scene warning notification (Information Flow): Notification of an incident scene emergency or safety issue. This flow identifies that an incident scene emergency or safety issue has occurred so that warnings may be generated by more than one system in the work zone.

ITS Roadway Equipment (Source Physical Object): 'ITS Roadway Equipment' represents the ITS equipment that is distributed on and along the roadway that monitors and controls traffic and monitors and manages the roadway. This physical object includes traffic detectors, environmental sensors, traffic signals, highway advisory radios, dynamic message signs, CCTV cameras and video image processing systems, grade crossing warning systems, and ramp metering systems. Lane management systems and barrier systems that control access to transportation infrastructure such as roadways, bridges and tunnels are also included. This object also provides environmental monitoring including sensors that measure road conditions, surface weather, and vehicle emissions. Work zone systems including work zone surveillance, traffic control, driver warning, and work crew safety systems are also included.

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 Adjacent
    Acknowledgement True
    CardinalityUnicast
    InitiatorSource
    AuthenticableTrue
    EncryptTrue


    Security

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


    Security CharacteristicsValue
    AuthenticableTrue
    Encrypt True