avo_route_request
This data flow is sent from the Provide Vehicle Control and Monitoring function to the Provide Driver and Traveler Services function to request a vehicle route that can only be used by vehicles equipped for automatic vehicle operations. Data items such as constraints and preferences that are within the data item shown below will be set up for automated lane operation only. Other data such as vehicle location and vehicle identity being added by the receiving process. It consists of the following data items each of which is defined in its own DDE:
origin
+ destination
+ departure_time
+ desired_arrival_time
+ modes
+ preferred_routes
+ preferred_alternate_routes
+ preferred_route_segments
+ preferred_weather_conditions
+ constraint_on_acceptable_travel_time
+ constraint_on_eta_change
+ constraint_on_special_needs
+ constraint_on_load_classification
+ constraint_on_avo_lanes
+ constraint_on_interstate
+ constraint_on_urban
+ constraint_on_vehicle_type
Sub Data Flows
- constraint_on_acceptable_travel_time
- constraint_on_avo_lanes
- constraint_on_eta_change
- constraint_on_interstate
- constraint_on_load_classification
- constraint_on_special_needs
- constraint_on_urban
- constraint_on_vehicle_type
- departure_time
- desired_arrival_time
- destination
- modes
- origin
- preferred_alternate_routes
- preferred_route_segments
- preferred_routes
- preferred_weather_conditions
Parent Data Flows
Associated PSpecs/Terminators