Connected Vehicle Roadside Equipment --> ITS Roadway Equipment:
signal priority service request
Definitions
signal priority service request (Information Flow): A service request for vehicle priority issued to a traffic signal controller that results in green extension or other accommodation for the priority vehicle, within the current signal timing plan. The request includes the priority level, the desired time and duration of service, and the intended travel path through the intersection. This flow also allows the RSE to cancel a previously issued request for priority.
Connected Vehicle Roadside Equipment (Source Physical Object): 'Connected Vehicle Roadside Equipment' (CV RSE) represents the Connected Vehicle roadside devices (i.e., Roadside Units (RSUs)) equipped with short range wireless (SRW) communications technology, as well as any other supporting equipment that leverage the RSU and are not described by other objects (e.g., a local roadside processor). CVRSE are used to send messages to, and receive messages from, nearby vehicles and personal devices equipped with compatible communications technology. Communications with adjacent field equipment and back office centers that monitor and control the RSE are also supported. This device operates from a fixed position and may be permanently deployed or a portable device that is located temporarily in the vicinity of a traffic incident, road construction, or a special event. It includes a processor, data storage, and communications capabilities that support secure communications with passing vehicles, other field equipment, and centers.
ITS Roadway Equipment (Destination 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.
Included In
This Triple is in the following Service Packages:
- CVO06: Freight Signal Priority
- MC11: Maintenance and Construction Signal Priority
- PT09: Transit Signal Priority
This triple is associated with the following Functional Objects:
This Triple is described by the following Functional View Data Flows:
- indicator_monitoring_suspend_for_priority
- indicator_priority_for_highways
- indicator_priority_for_roads
This Triple has the following triple relationships:
| Relationship | Source | Destination | Flow |
|---|---|---|---|
| Interactive | ITS Roadway Equipment | Connected Vehicle Roadside Equipment | intersection control status |
| Depends On | Maint and Constr Vehicle OBE | Connected Vehicle Roadside Equipment | local signal priority request |
| Depends On | Transit Vehicle OBE | Connected Vehicle Roadside Equipment | local signal priority request |
Communication Solutions
-
US: NTCIP Signal Priority - SNMPv3/TLS (5)
-
(None-Data) - Secure Internet (ITS) (43)
Selected Solution
US: NTCIP Signal Priority - SNMPv3/TLSSolution Description
|
ITS Application Entity
NTCIP 1202  NTCIP 1211 |
Click gap icons for more info.
|
||
|
Mgmt
|
Facilities
|
Security
IETF RFC 6353 IETF RFC 9456 |
|
|
TransNet
|
|||
|
Access
|
|||
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 | Adjacent |
| 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 | Not Applicable | Moderate | Low | |
| Basis | There is no sensitive or confidential information within this messages. Additionally, it could be inferred by observing either the presence of a transit vehicle near an intersection, or the effect on the timing of the intersection. This is also transmitted as a result of broadcast data. | The RSE is transmitting a request to the ITS RE on behalf of a transit vehicle. It should only be making requests on behalf of an approved vehicle. A corrupted request may lead to a transit vehicle not receiving a green light after requesting it. In this case, this may lead to traffic delays. If an unapproved vehicle is able to forge these requests, they may cause larger scale traffic delays. | If the ITS RE does not receive any requests, the vehicle may not receive the priority it requested. In the worst case scenario the transit vehicle would be forced to wait at some lights until they turned green. It would be more useful for a device to support this application, and only have some messages received, than to not support this application at all. | |
| Security Characteristics | Value |
|---|---|
| Authenticable | True |
| Encrypt | False |