ITS Roadway Equipment --> Traffic Management Center:
lane management information
Definitions
lane management information (Information Flow): System status of managed lanes including current operational state, violations, and logged information. This includes lane usage information including both traditional traffic flow measures and special information associated with managed lanes such as measured passenger occupancies. It also includes the operational status of the lane management equipment.
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.
Traffic Management Center (Destination 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.
Included In
This Triple is in the following Service Packages:
- PT10: Intermittent Bus Lanes
- ST06: HOV/HOT Lane Management
- ST07: Eco-Lanes Management
- TM16: Reversible Lane Management
- TM22: Dynamic Lane Management and Shoulder Use
- VS10: Restricted Lane Warnings
This triple is associated with the following Functional Objects:
- Roadway Dynamic Lane Management and Shoulder Use
- Roadway HOV Control
- Roadway Reversible Lanes
- TMC Dynamic Lane Management and Shoulder Use
- TMC HOV Lane Management
- TMC Restricted Lanes CV Application
- TMC Reversible Lane Management
This Triple is described by the following Functional View Data Flows:
- dynamic_lane_sensor_data
- hov_lane_data_input
- hov_sensor_data
- hov_sensor_status
- lane_management_device_status
- lane_management_status
- lane_violation_notification_for_traffic
- reversible_lane_control_device_status_from_highways
- reversible_lane_control_device_status_from_roads
- reversible_lane_sensor_status
This Triple has the following triple relationships:
None |
Communication Solutions
- EU: UTMC Data - UTMC (3)
- US: NTCIP Warning Device - SNMPv3/TLS (13)
- US: NTCIP Warning Device - SNMPv1/TLS (14)
- (None-Data) - Secure Internet (ITS) (32)
- Data for Distribution (TBD) - Apache Kafka (36)
- Data for Distribution (TBD) - OMG DDS (36)
- US: NTCIP Warning Device - SNMPv1 (40)
- (None-Data) - OASIS MQTT (42)
- Data for Distribution (TBD) - OASIS MQTT (42)
- Data for Distribution (TBD) - OASIS AMQP (45)
Selected Solution
Solution Description
ITS Application Entity
UTMC TS004.006 |
Click gap icons for more info.
|
||
Mgmt
IETF RFC 1907 |
Facilities
|
Security
IETF RFC 9147 |
|
TransNet
|
|||
Access
Internet Subnet Alternatives |
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 | False |
Cardinality | Unicast |
Initiator | Destination |
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 | May contain PII, may contain source data describing device control and sensed status that if captured could be used in the commission of a crime or breaking of traffic laws or regulations. | Information related to violations must be correct so that incorrect accusations are not made. Information related to device status and control must be correct to avoid wasted maintenance efforts. | More or less important depending on the context. Could even be LOW if areas of minimal import, depending on local policies. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |