transit_vehicle_roadway_priorities
This data flow is sent from the Manage Transit function to the Manage Traffic function and contains data necessary for an individual transit vehicle to be given priority at traffic signal controllers. This will be at the controller for a particular road intersection, pedestrian crossing, or highway entrance ramp. The data is sent directly from the transit vehicle to the next controller along its route and therefore is not subject to any centralized coordination. Local coordination may be provided if there are links between adjacent controllers. The data flow is sent directly from the vehicle to devices near one or more intersection controllers, which is assumed to be capable of giving priority to the correct phase(s) for any received priority request. It consists of the following items each of which is defined in its own DDE:
signal_priority_request
+ vehicle_identity
+ date
+ time
+ location_identity
+ route_point
+ vehicle_path_prediction_data
+ transit_vehicle_intersection_priority
+ transit_vehicle_pedestrian_priority
+ transit_vehicle_ramp_priority
+ transit_vehicle_sign_priority
Sub Data Flows
- date
- location_identity
- route_point
- signal_priority_request
- time
- transit_vehicle_intersection_priority
- transit_vehicle_pedestrian_priority
- transit_vehicle_ramp_priority
- transit_vehicle_sign_priority
- vehicle_identity
- vehicle_path_prediction_data
Parent Data Flows
Associated PSpecs/Terminators
- 1.2.7.3.4 - Manage Connected Signal Priority and Preemption Requests
- 4.1.2 - Determine Transit Vehicle Service Status
Parent Information Flows