ITS Roadway Equipment --> Traffic Management Center:
right-of-way request notification
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:
- CVO06: Freight Signal Priority
- MC11: Maintenance and Construction Signal Priority
- PS03: Emergency Vehicle Preemption
- PT09: Transit Signal Priority
- ST02: Eco-Traffic Signal Timing
- TM03: Traffic Signal Control
- TM04: Connected Vehicle Traffic Signal System
- TM18: Drawbridge Management
This triple is associated with the following Functional Objects:
- Roadway Multimodal Crossing Control
- Roadway Signal Control
- Roadway Signal Preemption
- TMC Multimodal Crossing Management
- TMC Signal Control
This Triple is described by the following Functional View Data Flows:
- multimodal_crossing_sensor_data
- multimodal_crossing_sensor_status
- pedestrian_sensor_data
- pedestrian_sensor_status
- signal_preemption_override
- signal_priority_override
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)
-
(None-Data) - Secure Internet (ITS) (32)
-
US: NTCIP Signal Priority - SNMPv1 (32)
-
EU: OCIT-O Signal Control - ODG-OCIT-O (44)
Selected Solution
EU: UTMC Data - UTMCSolution Description
|
ITS Application Entity
UTMC TS004.006  |
Click gap icons for more info.
|
||
|
Mgmt
IETF RFC 1907 |
Facilities
|
Security
IETF RFC 9147 |
|
|
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 | 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 |