ITS Roadway Equipment --> Traffic Management Center:
right-of-way request notification

Definition
Included In
Communication Solutions
Characteristics
Security

Definitions

right-of-way request notification (Information Flow): Notice that a request has occurred for signal prioritization, signal preemption, pedestrian call, multi-modal crossing activation, or other source for right-of-way.

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	Connected Vehicle Roadside Equipment	ITS Roadway Equipment	signal preemption request
Depends On	Connected Vehicle Roadside Equipment	ITS Roadway Equipment	signal priority service request
Depends On	Connected Vehicle Roadside Equipment	ITS Roadway Equipment	signal service request
Depends On	Emergency Vehicle OBE	ITS Roadway Equipment	local signal preemption request
Depends On	Maint and Constr Vehicle OBE	ITS Roadway Equipment	local signal priority request

Communication Solutions

EU: UTMC Data - UTMC (3)
US: NTCIP Signal Priority - SNMPv3/TLS (5)
US: NTCIP Signal Priority - SNMPv1/TLS (6)
US: NTCIP Signal Priority - SNMPv1 (32)
(None-Data) - Secure Internet (ITS) (43)
EU: OCIT-O Signal Control - ODG-OCIT-O (44)

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 Signal Priority - SNMPv1

Solution Description

This solution is used within Canada and the U.S.. It combines standards associated with US: NTCIP Signal Priority with those for I-F: SNMPv1. The US: NTCIP Signal Priority standards include upper-layer standards required to implement center-to-field traffic signal control priority communications (e.g., for busses and emergency vehicles). The I-F: SNMPv1 standards include lower-layer standards that define how SNMPv1, which does not provide any security, is used within some deployments within the ITS industry. This solution is no longer recommended due to known security vulnerabilities.

ITS Application Entity NTCIP 1202 NTCIP 1211			Click gap icons for more info.
Mgmt NTCIP 1201 Bundle: SNMPv1 MIB	Facilities NTCIP 1202 NTCIP 1211 NTCIP 2301	Security (None)
	TransNet Field TransNet Alternatives
	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	Source
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	This can be reasonably guessed based on observing the ITS RE's environment. It is obvious when a bus approaches an intersection.	Invalid messages could lead to an unauthorized user gaining signal priority at an intersection. This could also be used to delay traffic, which could lead to a financial impact on the community. However, the traffic signal will have controls in place to ensure that it does not display an illegal configuration (such as green in every direction).	Even if all of the Right-of-way Requests are not passed along from an ITS RE, the intersection will still operate as normal. There are other existing methods to assist a right-of-way requesting vehicle safely traveling through an intersection, such as lights and sirens, which prevent this from being a HIGH. DISC: THEA and NYC believe this to be LOW: "not necessary for the app to work; can cope with not having immediately available data"

Security Characteristics	Value
Authenticable	True
Encrypt	False

ITS Roadway Equipment --> Traffic Management Center:right-of-way request notification