ITS Roadway Equipment --> Traffic Management Center:
traffic detector data
Definitions
traffic detector data (Information Flow): Raw and/or processed traffic detector data which allows derivation of traffic flow variables (e.g., speed, volume, and density measures) and associated information (e.g., congestion, potential incidents). This flow includes the traffic data and the operational status of the traffic detectors
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
- ST02: Eco-Traffic Signal Timing
- ST03: Eco-Traffic Metering
- ST04: Roadside Lighting
- ST06: HOV/HOT Lane Management
- ST07: Eco-Lanes Management
- ST10: Low Emissions Zone Management
- TM01: Infrastructure-Based Traffic Surveillance
- TM03: Traffic Signal Control
- TM04: Connected Vehicle Traffic Signal System
- TM05: Traffic Metering
- TM08: Traffic Incident Management System
- TM12: Dynamic Roadway Warning
- TM16: Reversible Lane 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
- VS08: Queue Warning
- VS15: Infrastructure Enhanced Cooperative Adaptive Cruise Control
- VS16: Automated Vehicle Operations
This triple is associated with the following Functional Objects:
- Roadway Basic Surveillance
- Roadway HOV Control
- Roadway Incident Detection
- Roadway Work Zone Safety
- Roadway Work Zone Traffic Control
- TMC Basic Surveillance
- TMC Incident Detection
- TMC Reversible Lane Management
- TMC Signal Control
This Triple is described by the following Functional View Data Flows:
This Triple has the following triple relationships:
Relationship | Source | Destination | Flow |
---|---|---|---|
Depends On | Vehicle Characteristics | ITS Roadway Equipment | vehicle characteristics |
Communication Solutions
- EU: UTMC Data - UTMC (3)
- US: NTCIP Transportation Sensors - SNMPv3/TLS (5)
- US: NTCIP Transportation Sensors - SNMPv1/TLS (6)
- (None-Data) - Secure Internet (ITS) (32)
- US: NTCIP Transportation Sensors - SNMPv1 (32)
- Data for Distribution (TBD) - Apache Kafka (36)
- Data for Distribution (TBD) - OMG DDS (36)
- (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
Development needed |
Click gap icons for more info.
|
||
Mgmt
OASIS MQTT DMP |
Facilities
OASIS MQTT |
Security
|
|
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 | 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 | Low | Moderate | Moderate | |
Basis | No impact if someone sees the data | Some minimal guarantee of data integrity is necessary for all C-ITS flows. THEA believes this to be LOW.only limited adverse effect if raw/processed traffic detector data is bad/compromised; DISC: WYO believes this to be HIGH | Only limited adverse effect of info is not timely/readily available, however without this information it will be difficult to perform traffic management activities, thus MODERATE. If not used for management, may be LOW. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | False |