ITS Roadway Equipment --> Multi-Access Edge Computing:
vehicle signage local data
This flow may also be implemented by
ITS Roadway Equipment --> Connected Vehicle Roadside Equipment: vehicle signage local data Definitions
vehicle signage local data (Information Flow): Information provided by adjacent field equipment to support in-vehicle signing of dynamic information that is currently being displayed to passing drivers. This includes the dynamic information (e.g., local traffic and road conditions, work zone information, lane restrictions, detours, closures, advisories, parking availability, etc.) and control parameters that identify the desired timing, duration, and priority of the signage data.
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:
- TM16: Reversible Lane Management
- TM17: Speed Warning and Enforcement
- TM22: Dynamic Lane Management and Shoulder Use
This triple is associated with the following Functional Objects:
- MEC Traveler Information Communications
- Roadway Reversible Lanes
- Roadway Speed Monitoring and Warning
- Roadway Traffic Information Dissemination
This Triple is described by the following Functional View Data Flows:
- None
This Triple has the following triple relationships:
| None |
Communication Solutions
-
US: NTCIP Message Sign - Wireless SNMPv3/TLS (5)
-
(None-Data) - Secure Wireless Internet (EU) (43)
-
(None-Data) - Secure Wireless Internet (ITS) (43)
-
Data for Distribution (TBD) - Apache Kafka over Wireless (44)
-
Data for Distribution (TBD) - OMG DDS over Wireless (44)
-
(None-Data) - Apache Kafka over Wireless (44)
-
(None-Data) - OMG DDS over Wireless (44)
-
Data for Distribution (TBD) - Eclipse Zenoh over Wireless (44)
-
(None-Data) - Eclipse Zenoh over Wireless (44)
-
Data for Distribution (TBD) - OASIS MQTT over Wireless (47)
-
(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
US: NTCIP Message Sign - Wireless SNMPv3/TLSSolution Description
|
ITS Application Entity
NTCIP 1203 ![]() |
Click gap icons for more info.
|
||
|
Mgmt
|
Facilities
|
Security
![]()
IETF RFC 6353 ![]() IETF RFC 9456 ![]() |
|
|
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 | Destination |
| 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 is meant to augment other signage data, and by definition is meant to be shared with everyone; however, all communications between field infrastructure should be protected from viewing to prevent attackers from analyzing traffic and developing attack methods. | These signs are meant to augment other visual cues to the driver. They should be accurate, but any inaccuracies should be corrected for by other means. | These notifications are helpful to a driver, but if the driver does not receive this notification immediately, there should still be other visual cues. | |
| Security Characteristics | Value |
|---|---|
| Authenticable | True |
| Encrypt | False |



