Traffic Management Center --> ITS Roadway Equipment:
video surveillance control
Definitions
video surveillance control (Information Flow): Information used to configure and control video surveillance systems.
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:
- PT10: Intermittent Bus Lanes
- ST07: Eco-Lanes Management
- TM01: Infrastructure-Based Traffic Surveillance
- TM03: Traffic Signal Control
- TM05: Traffic Metering
- TM08: Traffic Incident Management System
- TM12: Dynamic Roadway Warning
- TM16: Reversible Lane Management
- TM19: Roadway Closure Management
- TM20: Variable Speed Limits
- TM22: Dynamic Lane Management and Shoulder Use
- TM24: Tunnel Management
- TM25: Wrong Way Vehicle Detection and Warning
- VS08: Queue Warning
This triple is associated with the following Functional Objects:
- Roadway Basic Surveillance
- Roadway Incident Detection
- Roadway Work Zone Safety
- Roadway Work Zone Traffic Control
- TMC Basic Surveillance
- TMC Incident Detection
- TMC Incident Dispatch Coordination
This Triple is described by the following Functional View Data Flows:
This Triple has the following triple relationships:
Relationship | Source | Destination | Flow |
---|---|---|---|
Interactive | ITS Roadway Equipment | Traffic Management Center | traffic image meta data |
Interactive | ITS Roadway Equipment | Traffic Management Center | traffic images |
Communication Solutions
- EU: UTMC Data - UTMC (3)
- US: NTCIP Video Switches - SNMPv3/TLS (5)
- US: NTCIP Video Switches - SNMPv1/TLS (6)
- (None-Data) - Secure Internet (ITS) (32)
- US: NTCIP Video Switches - SNMPv1 (32)
Selected Solution
Solution Description
ITS Application Entity
NTCIP 1205 NTCIP 1208 |
Click gap icons for more info.
|
||
Mgmt
|
Facilities
|
Security
(None) |
|
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 | Control flows, even for seemingly innocent devices, should be kept confidential to minimize attack vectors. While an individual installation may not be particularly impacted by a cyberattack of its sensor network, another installation might be severely impacted, and different installations are likely to use similar methods, so compromising one leads to compromising all. | Control flows, even for seemingly innocent devices, should have MODERATE integrity at minimum, just to guarantee that intended control messages are received. Incorrect, corrupted, intercepted and modified control messages can or will result in target field devices not behaving according to operator intent. The severity of this depends on the type of device, which is why some devices are set MODERATE and some HIGH. | Control flow availability is related to the criticality of being able to remotely control the device. For most devices, this is MODERATE. For purely passive devices with no incident relationship, this will be LOW. All devices should have default modes that enable them to operate without backhaul connectivity, so no device warrants a HIGH. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |