• About
  • Connected Vehicle
  • Architecture
  • Approach
  • Viewpoints
  • Security
• Applications
• Views
  • Enterprise
  • Functional
  • Physical
  • Communications
• Standards
  • CV Standards
  • CV Standards Plan
• Resources
  • Databases
  • Diagrams
  • Documents
  • Presentations
  • Tools
  • Training
• Glossary
  • Acronyms
• Contact Us

6.6.2.1: Calculate Vehicle Route

This process shall calculate trip planning and real-time dynamic guidance routes for all types of vehicles. The route data provided by the process in response to requests from vehicles using infrastructure based in-vehicle guidance shall only contain data necessary for the vehicle to provide guidance (since the data is intended for use by an in-vehicle navigation unit). The route provided for trip planning purposes shall contain data in a form which can be presented to a traveler via display (or alternatively in audio form). The process shall select the route according to the data included in the route request. Data provided by the requesting process includes preferences and constraints. The process shall have the capability of using current and/or predicted conditions of the road network in route calculation. The process shall have the capability of including additional factors such as current or forecasted weather in the calculation of route. If the process cannot find the data it needs in the route_segment_details_data store, it shall request the process responsible for providing route calculation data to obtain it from the appropriate source. The process shall have the capability of outputting routes for special priority vehicles to the Manage Traffic function so that signal preemption could be provided for the special priority vehicle. The process shall send details of logged special vehicle routes including commercial vehicles with hazardous or unusual loads or other special vehicles to the Manage Incidents function within Manage Traffic for monitoring (as a potential incident, or a planned event). Route guidance data and vehicle guidance route requests and acceptances shall be sent to the data archival process.

This process is associated with the Transportation Information Center physical object.

This process is associated with the following application objects:

• TIC Corridor Decision Support System
• TIC Trip Planning

This process is associated with the following data flows:

• cf_route - Out
• cf_route_request - In
• cv_route - Out
• cv_route_request - In
• get_vehicle_route - In
• logged_special_vehicle_route - Out
• map_data_for_route_selection - In
• map_data_for_route_selection - Out
• profiles_for_route_guidance - In
• request_route_segment_data - Out
• route_segment_details - In
• route_segment_details_updated - In
• route_selection_map_data - In
• route_selection_parameters_for_guidance - In
• routes_for_vehicles_data - In
• routes_for_vehicles_data - Out
• special_vehicle_priority_routing - Out
• vehicle_guidance_route - Out
• vehicle_guidance_route_accepted - In
• vehicle_route - Out
• vehicle_route_guidance_data_for_archive - Out
• vehicle_route_request - In
• weather_data_for_route_guidance - In
• weather_data_request_from_route_guidance - Out