ITS Roadway Equipment --> Traffic Management Center:
signal control status

Definition
Included In
Communication Solutions
Characteristics
Security

Definitions

signal control status (Information Flow): Operational and status data of traffic signal control equipment including operating condition and current indications.

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:

None

Communication Solutions

EU: UTMC Data - UTMC (3)
US: NTCIP Traffic Signal - SNMPv3/TLS (5)
US: NTCIP Traffic Signal - SNMPv1/TLS (6)
US: NTCIP Traffic Signal - SNMPv1 (32)
AU: TRAFF - AU TRAFF Comms (36)
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 Traffic Signal - SNMPv1/TLS

Solution Description

This solution is used within the U.S.. It combines standards associated with US: NTCIP Traffic Signal with those for I-F: SNMPv1/TLS. The US: NTCIP Traffic Signal standards include upper-layer standards required to implement center-to-field traffic signal communications. 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 1202			Click gap icons for more info.
Mgmt NTCIP 1201 Bundle: SNMPv1 MIB	Facilities NTCIP 1202 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	High	Moderate
Basis	The current conditions of an ITS RE are completely observable, by design.	This influences the TMC response to a right-of-way request. It should be as accurate as the right-of-way request themselves. For some applications (ISIG) this need only be moderate. Per THEA: info needs to be accurate and should not be tampered to enable effective monitoring and control by the TMC. DISC: THEA believes this to be MODERATE: "info needs to be accurate and should not be tampered to enable effective monitoring and control by the TMC; should be as accurate as the right of way request". NYC:TMC doesn't play an active role in this application, i.e. even if the information contained in this flow were incorrect, it is unlikely to affect the outcome of this application one way or the other. On some applications NYC has this MODERATE though. RES: This value can obviously change a lot depending on the application context.	The TMC will need the current status of the ITS RE in order to make an educated decision. If it is unavailable, the system is unable to operate. However, a few missed messages will not have a catastrophic impact. From NYC: TMC doesn't play an active role in this application, i.e. even if it is unavailable, it is unlikely to affect the outcome of this application one way or the other. RES: This value can change a lot depending on the application context.

Security Characteristics	Value
Authenticable	True
Encrypt	False

ITS Roadway Equipment --> Traffic Management Center:signal control status