ITS Roadway Equipment --> Multi-Access Edge Computing:
work zone warning notification
This triple is bi-directional. See also
Multi-Access Edge Computing --> ITS Roadway Equipment: work zone warning notification This flow may also be implemented by ITS Roadway Equipment --> Connected Vehicle Roadside Equipment: work zone warning notification
Definitions
work zone warning notification (Information Flow): Notification of a work zone emergency or safety issue. This flow identifies that a work zone 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:
- None
This Triple has the following triple relationships:
| None |
Communication Solutions
-
EU: ETSI data dictionary - Secure Wireless Internet (EU) (19)
-
(None-Data) - Secure Wireless Internet (EU) (43)
-
(None-Data) - Secure Wireless Internet (ITS) (43)
-
(None-Data) - Apache Kafka over Wireless (44)
-
(None-Data) - OMG DDS over Wireless (44)
-
(None-Data) - Eclipse Zenoh over Wireless (44)
-
(None-Data) - OASIS MQTT over Wireless (47)
-
Data for Distribution (TBD) - OASIS AMQP over Wireless (61)
-
(None-Data) - OASIS AMQP over Wireless (61)
Selected Solution
(None-Data) - OMG DDS over WirelessSolution Description
|
ITS Application Entity
![]()
Development needed ![]() |
Click gap icons for more info.
|
||
|
Mgmt
OMG DDS ![]() |
Facilities
![]() ![]()
Development needed ![]() OMG DDS ![]() OMG DDS-RPC ![]() OMG DDSI-RTPS ![]() |
Security
OMG DDS-Security ![]() |
|
|
TransNet
|
|||
|
Access
![]() ![]() ![]()
|
|||
Note that some layers might have alternatives, in which case all of the gap icons associated with every alternative may be shown on the diagram, but the solution severity calculations (and resulting ordering of solutions) includes only the issues associated with the default (i.e., best, least severe) alternative.
Characteristics
| Characteristic | Value |
|---|---|
| Time Context | Recent |
| Spatial Context | Adjacent |
| Acknowledgement | False |
| Cardinality | Unicast |
| Initiator | Source |
| Authenticable | True |
| Encrypt | False |
| Interoperability | Description |
|---|---|
| Local | In cases where an interface is normally encapsulated by a single stakeholder, interoperability is still desirable, but the motive is vendor independence and the efficiencies and choices that an open standards-based interface provides. |
Security
| Information Flow Security | ||||
|---|---|---|---|---|
| Confidentiality | Integrity | Availability | ||
| Rating | Moderate | Moderate | Moderate | |
| Basis | This data is intentionally transmitted to everyone via a broadcast. It can also be determined via other visual indicators; however, all communications between field infrastructure should be protected from viewing to prevent attackers from analyzing traffic and developing attack methods. | This information should be accurate, but an incorrect information should not have a direct impact causing the loss of life or limb. | The system should be able to operate properly if it misses a few messages. If a message is not received, the RSE should know. | |
| Security Characteristics | Value |
|---|---|
| Authenticable | True |
| Encrypt | False |



