Traffic Management Center --> ITS Roadway Equipment:
roadway dynamic signage data
Definitions
roadway dynamic signage data (Information Flow): Information used to initialize, configure, and control dynamic message signs. This flow can provide message content and delivery attributes, local message store maintenance requests, control mode commands, status queries, and all other commands and associated parameters that support remote management of these devices.
Traffic Management Center (Source Physical Object): The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters.
ITS Roadway Equipment (Destination 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.
Included In
This Triple is in the following Service Packages:
- CVO05: Commercial Vehicle Parking
- MC06: Work Zone Management
- MC12: One-Way Convoy Driving
- PM04: Regional Parking Management
- PS10: Wide-Area Alert
- PT10: Intermittent Bus Lanes
- ST03: Eco-Traffic Metering
- ST07: Eco-Lanes Management
- ST10: Low Emissions Zone Management
- TI07: In-Vehicle Signage
- TM05: Traffic Metering
- TM06: Traffic Information Dissemination
- TM17: Speed Warning and Enforcement
- TM18: Drawbridge Management
- TM19: Roadway Closure Management
- TM20: Variable Speed Limits
- TM21: Speed Harmonization
- TM22: Dynamic Lane Management and Shoulder Use
- TM24: Tunnel Management
- TM25: Wrong Way Vehicle Detection and Warning
- VS09: Reduced Speed Zone Warning / Lane Closure
- VS10: Restricted Lane Warnings
This triple is associated with the following Functional Objects:
- Roadway Dynamic Lane Management and Shoulder Use
- Roadway Multimodal Crossing Control
- Roadway Speed Monitoring and Warning
- Roadway Traffic Information Dissemination
- Roadway Work Zone Traffic Control
- TMC Multimodal Crossing Management
- TMC Speed Warning
- TMC Traffic Information Dissemination
- TMC Work Zone Traffic Management
This Triple is described by the following Functional View Data Flows:
- dms_control_data
- dms_data
- dms_traffic_metering_data
- dms_variable_speed_limit_data
- dms_wide_area_alert_information
This Triple has the following triple relationships:
Relationship | Source | Destination | Flow |
---|---|---|---|
Interactive | ITS Roadway Equipment | Traffic Management Center | roadway dynamic signage status |
Communication Solutions
- AU: DMS and RWIS data - DMS and RWIS Comms (0)
- EU: UTMC Data - UTMC (3)
- US: NTCIP Message Sign - SNMPv3/TLS (5)
- US: NTCIP Message Sign - SNMPv1/TLS (6)
- US: NTCIP Message Sign - SNMPv1 (32)
Selected Solution
Solution 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 | Local |
Acknowledgement | True |
Cardinality | Unicast |
Initiator | Source |
Authenticable | True |
Encrypt | True |
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 | Device control information should not be available, as those with criminal intent may use this information toward their own ends. | Data is intended to feed dissemination channels, either C-ITS messages or DMS or other channels, so it should generally be correct as it is distributed widely and any forgery or corrupted data will have widespread impact. | Occasional outages of this flow will delay dissemination of the data to travelers (the eventual end user) which could have significant impacts on travel, both safety and mobility impacts. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |