ITS Roadway Equipment --> Traffic Management Center:
traffic detector data

Definition
Included In
Communication Solutions
Characteristics
Security

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:

This triple is associated with the following Functional Objects:

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)
US: NTCIP Transportation Sensors - SNMPv1 (32)
(None-Data) - Secure Internet (ITS) (43)
Data for Distribution (TBD) - Apache Kafka (44)
Data for Distribution (TBD) - OMG DDS (44)
(None-Data) - OASIS MQTT (50)
Data for Distribution (TBD) - OASIS MQTT (50)
Data for Distribution (TBD) - OASIS AMQP (61)

Solutions are sorted in ascending Gap Severity order. The Gap Severity is the parenthetical number at the end of the solution.

Selected Solution

US: NTCIP Transportation Sensors - SNMPv1/TLS

Solution Description

This solution is used within Canada and the U.S.. It combines standards associated with US: NTCIP Transportation Sensors with those for I-F: SNMPv1/TLS. The US: NTCIP Transportation Sensors standards include upper-layer standards required to implement center-to-field transportation sensors (e.g., vehicle detectors) communications (e.g., real-time). The I-F: SNMPv1/TLS standards include lower-layer standards that define one way to retrofit basic security into SNMPv1 implementations (mainly in the US); however, this only secures the communications link and does not provide end-application security and is not recommended for new deployments.

ITS Application Entity NTCIP 1209			Click gap icons for more info.
Mgmt NTCIP 1201 Bundle: SNMPv1 MIB	Facilities NTCIP 1209 NTCIP 2301	Security IETF RFC 8446
	TransNet IP Alternatives IETF RFC 9293
	Access Field 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

ITS Roadway Equipment --> Traffic Management Center:traffic detector data