Vehicle

This subsystem resides in a vehicle (usually in an automobile, but any vehicle not covered by particular vehicle subsystem) and provides the sensory, processing, storage, and communications functions necessary to support efficient, safe, and convenient travel. These functions reside in general vehicles including personal automobiles, commercial vehicles, emergency vehicles, transit vehicles, maintenance vehicles or other vehicle types. Information services provide the driver with current travel and weather conditions and the availability of services along the route and at the destination. Both one-way and two-way communications options support a spectrum of information services from low-cost broadcast services to advanced, pay for use personalized information services. Route guidance capabilities assist in formulation of an optimal route and step by step guidance along the travel route. Advanced sensors, processors, enhanced driver interfaces, and actuators complement the driver information services so that, in addition to making informed mode and route selections, the driver travels these routes in a safer and more consistent manner. Initial collision avoidance functions provide “vigilant co-pilot” driver warning capabilities. More advanced functions assume limited control of the vehicle to maintain safe headway. Ultimately, this subsystem supports completely automated vehicle operation through advanced communications with other vehicles in the vicinity and in coordination with supporting infrastructure subsystems. Pre-collision safety systems are deployed and emergency notification messages are issued when unavoidable collisions do occur. While the majority of the systems described above apply to automobiles, some of the systems can apply to other forms of vehicles such as motorcycles and even bicycles.

Security Considerations

The primary security consideration for the Vehicle Subsystem relates to the security of the basic vehicle and the driver and passengers in the vehicle. A vehicle Mayday capability might allow the driver or passengers to provide centre subsystems with information about security threats or incidents. Various safety systems in the vehicle might protect the occupants from some security hazards. The electronic toll and parking payment capabilities expose the financial information of the owner to certain risks of unauthorized disclosure. The vehicle may anonymously broadcast its location and key sensor readings and receive critical safety information from roadside equipment. In general, the Vehicle Subsystem needs to have a relatively high degree of confidentiality in order to safeguard transmitted information.

Functionality: Equipment Packages and PSpecs

• Basic Vehicle Reception
  
  • 6.7.3.2 - Provide Driver with Personal Travel Information
  • 6.7.3.3 - Provide Driver Information Interface
  
  
• Driver Safety Monitoring System
  
  • 3.1.2 - Carry-out Safety Analysis
  • 3.1.3 - Process Vehicle On-board Data
  • 6.7.3.3 - Provide Driver Information Interface
  
  
• Driver Visibility Improvement System
  
  • 3.4 - Enhance Driver's Vision
  • 6.7.3.3 - Provide Driver Information Interface
  
  
• Interactive Vehicle Reception
  
  • 6.7.3.1 - Get Driver Personal Request
  • 6.7.3.2 - Provide Driver with Personal Travel Information
  • 6.7.3.3 - Provide Driver Information Interface
  • 6.7.3.4 - Update Driver Display Map Data
  
  
• Vehicle Automated Operations
  
  • 3.1.3 - Process Vehicle On-board Data
  • 3.2.1 - Provide Driver Interface
  • 3.2.2 - Provide Automatic Vehicle Operations Control
  • 3.2.3.2 - Manage Platoon Following
  • 3.2.3.3 - Process data for Vehicle Actuators
  • 3.2.4 - Process Sensor Data for Automatic Vehicle Operations
  • 6.7.3.3 - Provide Driver Information Interface
  
  
• Vehicle Autonomous Route Guidance
  
  • 6.7.1.1.3 - Provide Autonomous In-Vehicle Guidance
  • 6.7.1.2 - Provide Driver Guidance Interface
  • 6.7.1.4 - Update Vehicle Navigable Map Database
  
  
• Vehicle Environmental Probe Support
  
  • 3.1.3 - Process Vehicle On-board Data
  
  
• Vehicle Intersection Control
  
  • 3.1.1 - Produce Collision and Crash Avoidance Data
  • 3.1.3 - Process Vehicle On-board Data
  • 3.2.3.3 - Process data for Vehicle Actuators
  • 6.7.3.3 - Provide Driver Information Interface
  
  
• Vehicle Intersection Safety Warning
  
  • 3.1.1 - Produce Collision and Crash Avoidance Data
  • 3.1.3 - Process Vehicle On-board Data
  • 3.2.3.3 - Process data for Vehicle Actuators
  • 3.2.3.5 - Process Vehicle Sensor Data
  • 6.7.3.2 - Provide Driver with Personal Travel Information
  • 6.7.3.3 - Provide Driver Information Interface
  
  
• Vehicle Lateral Control
  
  • 3.1.3 - Process Vehicle On-board Data
  • 3.2.1 - Provide Driver Interface
  • 3.2.3.1 - Provide Command Interface
  • 3.2.3.3 - Process data for Vehicle Actuators
  • 3.2.3.4.3 - Provide Lane Servo Control
  • 3.2.3.4.4 - Provide Change Lane Servo Control
  • 3.2.3.4.5 - Provide Vehicle Control Data Interface
  • 6.7.3.3 - Provide Driver Information Interface
  
  
• Vehicle Lateral Warning System
  
  • 3.1.1 - Produce Collision and Crash Avoidance Data
  • 3.1.3 - Process Vehicle On-board Data
  • 3.2.3.5 - Process Vehicle Sensor Data
  • 6.7.3.3 - Provide Driver Information Interface
  
  
• Vehicle Location Determination
  
  • 6.7.1.3 - Process Vehicle Location Data
  • 6.7.1.4 - Update Vehicle Navigable Map Database
  
  
• Vehicle Longitudinal Control
  
  • 3.1.3 - Process Vehicle On-board Data
  • 3.2.1 - Provide Driver Interface
  • 3.2.3.1 - Provide Command Interface
  • 3.2.3.3 - Process data for Vehicle Actuators
  • 3.2.3.4.1 - Provide Speed Servo Control
  • 3.2.3.4.2 - Provide Headway Servo Control
  • 3.2.3.4.5 - Provide Vehicle Control Data Interface
  • 6.7.3.3 - Provide Driver Information Interface
  
  
• Vehicle Longitudinal Warning System
  
  • 3.1.1 - Produce Collision and Crash Avoidance Data
  • 3.1.3 - Process Vehicle On-board Data
  • 3.2.3.5 - Process Vehicle Sensor Data
  • 6.7.3.3 - Provide Driver Information Interface
  
  
• Vehicle Mayday I/F
  
  • 3.3.1 - Provide Communications Function
  • 3.3.2 - Build Automatic Collision Notification Message
  • 6.7.1.2 - Provide Driver Guidance Interface
  • 6.7.2.1 - Build Driver Personal Security Message
  • 6.7.2.2 - Provide Driver In-vehicle Communications Function
  • 6.7.3.3 - Provide Driver Information Interface
  
  
• Vehicle On-board Diagnostics System
  
  • 3.1.3 - Process Vehicle On-board Data
  • 6.7.3.2 - Provide Driver with Personal Travel Information
  • 6.7.3.3 - Provide Driver Information Interface
  
  
• Vehicle Pre-Crash Safety Systems
  
  • 3.1.1 - Produce Collision and Crash Avoidance Data
  • 3.1.3 - Process Vehicle On-board Data
  • 3.2.3.5 - Process Vehicle Sensor Data
  
  
• Vehicle Safety Monitoring System
  
  • 3.1.2 - Carry-out Safety Analysis
  • 3.1.3 - Process Vehicle On-board Data
  • 6.7.3.3 - Provide Driver Information Interface
  
  
• Vehicle Secure Area Access System
  
  • 3.5 - Generate Vehicle Access Requests
  • 6.7.3.3 - Provide Driver Information Interface
  
  
• Vehicle Short Range Traveller Information Reception
  
  • 6.7.3.2 - Provide Driver with Personal Travel Information
  • 6.7.3.3 - Provide Driver Information Interface
  
  
• Vehicle Toll/Parking Interface
  
  • 7.1.4 - Provide Driver Toll Payment Interface
  • 7.1.7 - Provide Traveller Card Interface for Tolls
  • 7.2.4 - Provide Driver Parking Lot Payment Interface
  • 7.2.7 - Provide Traveller Card Interface for Parking
  • 7.5.1 - Provide Vehicle Traveller Card Interface
  
  
• Vehicle Traffic Probe Support
  
  • 3.1.3 - Process Vehicle On-board Data
  • 6.7.1.1.2 - Provide Dynamic In-Vehicle Guidance
  • 6.7.3.3 - Provide Driver Information Interface
  
  
• Vehicle Trip Planning and Route Guidance
  
  • 6.7.1.1.1 - Determine In-Vehicle Guidance Method
  • 6.7.1.1.2 - Provide Dynamic In-Vehicle Guidance
  • 6.7.1.2 - Provide Driver Guidance Interface
  • 6.7.1.4 - Update Vehicle Navigable Map Database
  • 6.7.3.1 - Get Driver Personal Request
  
  
• Vehicle Warning System
  
  • 3.1.1 - Produce Collision and Crash Avoidance Data
  • 3.1.3 - Process Vehicle On-board Data
  • 6.7.3.3 - Provide Driver Information Interface
  
  

Inputs/Outputs: Architecture Flows and Data Flows

Basic Vehicle > Vehicle

• basic vehicle measures - Information provided to on-board ITS equipment from the vehicle platform indicating current vehicle status.
  Data Flows:
  • fbv-brake_servo_response
  • fbv-vehicle_motion_data
  • fbv-vehicle_lane_position
  • fbv-vehicle_identity
  • fbv-vehicle_condition
  • fbv-throttle_servo_response
  • fbv-steering_servo_response
  • fbv-driver_safety_status
  • fbv-vehicle_occupants
  • fbv-crash_sensor_data
  • fbv-vehicle_headway
  • fbv-diagnostics_data
  • fbv-vehicle_proximity_data
  • fbv-vehicle_safety_status
  • fbv-vehicle_security_status
  • fbv-vehicle_speed
  • fbv-vehicle_attitude_data
  • fbv-vehicle_on_avo_lane
  
  

Commercial Vehicle Subsystem > Vehicle

• commercial vehicle data - Information about the commercial vehicles cargo, credentials, and payments.
  Data Flows:
  • cv_driver_enrollment_cost
  • processed_cargo_data
  
  

Driver > Vehicle

• driver inputs - Driver input to the vehicle including configuration data, settings and preferences, interactive requests, and control commands.
  Data Flows:
  • fd-activate_vehicle_control
  • fd-request_advisory_information
  • fd-vehicle_display_configuration_setting
  • fd-guidance_route_accepted
  • fd-guidance_data
  • fd-guidance_map_update_request
  • fd-vehicle_display_configuration_override
  
  
• request for service - Driver inputs that summon an emergency response, request a financial transaction, or initiate other services.
  Data Flows:
  • fd-driver_vehicle_access_request
  • fd-other_services_parking_request
  • fd-other_services_toll_request
  • fd-guidance_request
  • fd-emergency_request
  
  

Emergency Management > Vehicle

• emergency acknowledge - Acknowledge request for emergency assistance and provide additional details regarding actions and verification requirements.
  Data Flows:
  • emergency_request_vehicle_acknowledge
  • emergency_request_driver_acknowledge
  
  
• emergency data request - A request for additional information or a control command issued by the emergency response agency in response to an emergency request for assistance from a traveller.
  Data Flows:
  • vehicle_security_system_commands
  • emergency_data_request
  
  

Emergency Vehicle Subsystem > Vehicle

• emergency vehicle alert - Notification to vehicles in the area that an emergency vehicle is in the vicinity. The number of responding vehicles, their status, location, speed, and direction are provided.
  Data Flows:
  • emergency_vehicle_proximity
  
  
• vehicle signage data - In-vehicle signing data that augments regulatory, warning, and informational road signs and signals. The information provided would include static sign information (e.g., stop, curve warning, guide signs, service signs, and directional signs) and dynamic information (e.g., current signal states, grade crossing information, local traffic and road conditions, advisories, and detours).
  Data Flows:
  • em_to_vehicle_incident_scene_information
  
  

Information Service Provider > Vehicle

• broadcast traveller information - General traveller information that contains traffic and road conditions, link travel times, incidents, advisories, restrictions, transit service information, weather information, parking information, and other related traveller information.
  Data Flows:
  • vehicle_broadcast_event_information
  • vehicle_broadcast_incident_information
  • vehicle_broadcast_multimodal_data
  • vehicle_broadcast_parking_data
  • vehicle_broadcast_price_data
  • vehicle_broadcast_weather_data
  • link_and_queue_data
  • vehicle_broadcast_transit_data
  • vehicle_broadcast_traffic_data
  • vehicle_broadcast_border_data
  
  
• business directory information - Travel service information and reservations for tourist attractions, lodging, dining, service stations, emergency services, and other services and businesses of interest to the traveller.
  Data Flows:
  • vehicle_transaction_confirmation
  • vehicle_business_directory_service_data
  
  
• emergency traveller information - Public notification of an emergency such as a natural or man-made disaster, civil emergency, or child abduction. This flow also includes evacuation information including evacuation instructions, evacuation zones, recommended evacuation times, tailored evacuation routes and destinations, traffic and road conditions along the evacuation routes, traveller services and shelter information, and reentry times and instructions.
  Data Flows:
  • vehicle_wide_area_alert_information
  • vehicle_emergency_traveller_information
  • vehicle_transportation_system_status
  • vehicle_evacuation_traveller_information
  
  
• interactive traveller information - Traveller information provided in response to a traveller request. The provided information includes traffic and road conditions, advisories, incidents, payment information, transit services, parking information, weather information, and other travel-related data updates and confirmations.
  Data Flows:
  • advanced_tolls_and_fares_response
  • vehicle_interactive_border_data
  • vehicle_interactive_event_information
  • vehicle_interactive_incident_information
  • advanced_fares_and_charges_response
  • vehicle_interactive_parking_data
  • vehicle_interactive_price_data
  • driver_map_update_payment_response
  • driver_display_update_payment_response
  • vehicle_interactive_transit_data
  • vehicle_interactive_traffic_data
  • vehicle_interactive_weather_data
  • vehicle_interactive_multimodal_data
  
  
• traveller alerts - Traveller information alerts reporting congestion, incidents, adverse road or weather conditions, parking availability, transit service delays or interruptions, and other information that may impact the traveller. Relevant alerts are provided based on traveller-supplied profile information including trip characteristics and preferences.
  Data Flows:
  • vehicle_parking_alert
  • vehicle_traffic_alert
  • vehicle_incident_alert
  • vehicle_transit_alert
  • vehicle_multimodal_alert
  • vehicle_border_alert
  • vehicle_event_alert
  • vehicle_weather_alert
  
  
• trip plan - A travel itinerary identifying a route and associated traveller information and instructions identifying recommended modes and transfer information, ride sharing options, and transit and parking reservation information.
  Data Flows:
  • vehicle_trip_information
  • vehicle_guidance_route
  • vehicle_payment_confirmation
  
  

Location Data Source > Vehicle

• position fix - Information which provides a traveller's or vehicle's geographical position.
  Data Flows:
  • From_Location_Data_Source
  
  

Maintenance and Construction Vehicle > Vehicle

• vehicle signage data - In-vehicle signing data that augments regulatory, warning, and informational road signs and signals. The information provided would include static sign information (e.g., stop, curve warning, guide signs, service signs, and directional signs) and dynamic information (e.g., current signal states, grade crossing information, local traffic and road conditions, advisories, and detours).
  Data Flows:
  • work_zone_intrusion_alert_on_board_for_in_vehicle_signing
  
  

Map Update Provider > Vehicle

• map updates - Map update which could include a new underlying static or real-time map or map layer(s) update.
  Data Flows:
  • fmup-vehicle_map_update
  • fmup-driver_display_update
  • fmup-vehicle_map_update_cost
  • fmup-driver_display_update_cost
  
  

Other Vehicle > Vehicle

• vehicle control coordination - Coordination of control commands between leader and follower vehicles allowing vehicles to join and separate from groups of cooperative vehicles, sharing performance capabilities, and coordinating maneuvers between lead and following vehicles.
  Data Flows:
  • fov-platoon_data_from_other_vehicle
  
  
• vehicle intersection safety data - Vehicle path and acceleration data provided by vehicles approaching or occupying an intersection. It identifies the intersection, vehicle position and motion, the anticipated lane and movement that will be used in the intersection, and notification of potential violations or other detected safety hazards.
  Data Flows:
  • fov-safety_status_from_other_vehicle
  
  
• vehicle safety data - Vehicle safety data indicating vehicle location, vehicle motion (speed, heading, acceleration), vehicle control (brakes, steering, throttle, exterior lights), basic vehicle characteristics (length, width). May also include additional vehicle status (e.g., anti-lock brake activation, stability control system activation).
  Data Flows:
  • fov-safety_msg_data_from_other_vehicles
  
  

Parking Management > Vehicle

• vehicle parking information - Parking information for in-vehicle display that is provided to vehicles approaching or in parking facilities. The information provided would include static sign information (e.g., guide signs, service signs, height, width, and weight restrictions, and directional signs) and dynamic information (e.g., current parking availability and locations).
  Data Flows:
  • parking_to_vehicle_local_parking_data
  
  
• vehicle payment request - Request for information supporting toll and parking payments.
  Data Flows:
  • parking_lot_vehicle_payment_data_request
  • parking_lot_payment_request
  
  
• vehicle payment update - Data written to vehicle equipment to support electronic toll collection or parking payment.
  Data Flows:
  • parking_lot_payment_debited
  • parking_lot_vehicle_payment_data_clear
  • parking_lot_vehicle_payment_data_update
  
  

Potential Obstacles > Vehicle

• physical presence - Detection of an obstacle by a vehicle. Obstacle could include animals, other vehicles, pedestrians, rocks in roadway etc.
  Data Flows:
  • From_Potential_Obstacles
  
  

Roadway Environment > Vehicle

• environmental conditions - Current road conditions (e.g., surface temperature, subsurface temperature, moisture, icing, treatment status) and surface weather conditions (e.g., air temperature, wind speed, precipitation, visibility) that are measured by environmental sensors.
  Data Flows:
  • fre-environmental_conditions
  
  
• roadway characteristics - Detectable or measurable road characteristics such as friction coefficient and general surface conditions, road geometry and markings, etc. These characteristics are monitored or measured by ITS sensors and used to support advanced vehicle safety and control and road maintenance capabilities.
  Data Flows:
  • fre-roadway_characteristics
  • fre-roadside_data
  
  

Roadway Subsystem > Vehicle

• access permission - Information returned indicating whether permission for access is granted and instructions for proceeding.
  Data Flows:
  • vehicle_barrier_access_status
  
  
• automated vehicle control data - Instructions and control parameters for automated vehicle operation including current system conditions and advisories, control parameters (e.g., speed and performance profiles, headways), maneuver coordination, and check in/checkout instructions.
  Data Flows:
  • lane_change_details
  • lane_change_strategy
  • avo_check_response
  
  
• broadcast traveller information - General traveller information that contains traffic and road conditions, link travel times, incidents, advisories, restrictions, transit service information, weather information, parking information, and other related traveller information.
  Data Flows:
  • field_to_vehicle_broadcast_price_data
  • field_to_vehicle_broadcast_border_data
  • field_to_vehicle_broadcast_traffic_data
  • field_to_vehicle_broadcast_event_information
  • field_to_vehicle_broadcast_incident_information
  • field_to_vehicle_broadcast_transit_data
  • field_to_vehicle_broadcast_multimodal_data
  • field_to_vehicle_broadcast_parking_data
  • field_to_vehicle_broadcast_weather_data
  
  
• emergency traveller information - Public notification of an emergency such as a natural or man-made disaster, civil emergency, or child abduction. This flow also includes evacuation information including evacuation instructions, evacuation zones, recommended evacuation times, tailored evacuation routes and destinations, traffic and road conditions along the evacuation routes, traveller services and shelter information, and reentry times and instructions.
  Data Flows:
  • field_to_vehicle_evacuation_traveller_information
  • field_to_vehicle_emergency_traveller_information
  • field_to_vehicle_wide_area_alert_information
  • field_to_vehicle_transportation_system_status
  
  
• intersection status - Intersection status including current operational status, signal phase and timing information, intersection geometry, surface conditions, warnings of potential violations or hazardous conditions, and approaching vehicle information. This may include information about the position, velocity, acceleration, and turning status of approaching vehicles.
  Data Flows:
  • intersection_collision_avoidance_data
  • intersection_status_data_for_vehicle
  
  
• roadway safety data - Information about potential safety hazards in the vehicle path such as stalled vehicles, wrong way drivers, debris, or standing water.
  Data Flows:
  • roadside_safety_data_to_vehicle
  
  
• vehicle signage data - In-vehicle signing data that augments regulatory, warning, and informational road signs and signals. The information provided would include static sign information (e.g., stop, curve warning, guide signs, service signs, and directional signs) and dynamic information (e.g., current signal states, grade crossing information, local traffic and road conditions, advisories, and detours).
  Data Flows:
  • intrusion_alert_for_in_vehicle_signing
  • vehicle_signage_data
  • vehicle_env_probe_data_output
  • vehicle_signage_emissions_testing_results
  
  

Toll Collection > Vehicle

• vehicle payment request - Request for information supporting toll and parking payments.
  Data Flows:
  • toll_vehicle_payment_data_request
  • toll_payment_request
  
  
• vehicle payment update - Data written to vehicle equipment to support electronic toll collection or parking payment.
  Data Flows:
  • toll_payment_debited
  • toll_vehicle_payment_data_update
  • toll_vehicle_payment_data_clear
  
  

Transit Vehicle Subsystem > Vehicle

• vehicle signage data - In-vehicle signing data that augments regulatory, warning, and informational road signs and signals. The information provided would include static sign information (e.g., stop, curve warning, guide signs, service signs, and directional signs) and dynamic information (e.g., current signal states, grade crossing information, local traffic and road conditions, advisories, and detours).
  Data Flows:
  • transit_vehicle_status_for_signing
  
  

Traveller Card > Vehicle

• payment - Payment of some kind (e.g., toll, parking, fare) by traveller which, in most cases, can be related to a credit account.
  Data Flows:
  • ftc-driver_vehicle_input_credit_identity
  • ftc-parking_vehicle_payment_data
  • ftc-confirm_payment_at_toll_plaza
  • ftc-confirm_payment_at_parking_lot
  • ftc-toll_vehicle_payment_data
  
  

Vehicle > Basic Vehicle

• vehicle control - Vehicular control commands
  Data Flows:
  • tbv-deploy_crash_restraints
  • tbv-change_brake_setting
  • tbv-vehicle_security_system_commands
  • tbv-change_throttle_setting
  • tbv-steer_left
  • tbv-steer_right
  • tbv-steer_straight
  • tbv-change_direction
  
  

Vehicle > Commercial Vehicle Subsystem

• commercial vehicle data request - Requests from the vehicle for information about the commercial vehicle's cargo, credentials, and payments.
  Data Flows:
  • cargo_data_request
  • cv_driver_credit_identity
  
  

Vehicle > Driver

• driver updates - Information displayed or otherwise conveyed by the vehicle to the driver.
  Data Flows:
  • td-guidance_input_request
  • td-broadcast_information
  • td-driver_vehicle_access_status
  • td-driving_guidance
  • td-guidance_map_update_response
  • td-guidance_route_details
  • td-advisory_information
  • td-vehicle_occupants_detected
  
  
• in-vehicle transaction status - The status of an electronic payment transaction presented to the driver by in-vehicle equipment.
  Data Flows:
  • td-other_services_toll_response
  • td-other_services_parking_response
  
  

Vehicle > Emergency Management

• emergency notification - An emergency request for assistance automatically initiated by a vehicle or originated by a traveller using an in-vehicle or personal device.
  Data Flows:
  • emergency_request_vehicle_details
  • driver_status_update
  • emergency_request_driver_details
  • vehicle_status_update
  • vehicle_security_system_commands_request
  
  

Vehicle > Information Service Provider

• business directory request - Request for travel service information including tourist attractions, lodging, restaurants, service stations, and emergency services. The request identifies the type of service, the area of interest, optional reservation request information, parameters that are used to prioritize or filter the returned information, and sorting preferences.
  Data Flows:
  • vehicle_transaction_request
  • vehicle_payment_information_for_bd
  • vehicle_business_directory_service_data_request
  
  
• emergency traveller information request - Request for alerts, evacuation information, and other emergency information provided to the traveling public.
  Data Flows:
  • vehicle_emergency_information_request
  
  
• environmental probe data - Data from vehicle safety and convenience systems that can be used to estimate environmental conditions, including measured air temperature, exterior light status, wiper status, sun sensor status, rain sensor status, traction control status, anti-lock brake status, and other collected vehicle system status and sensor information. The collected data is reported along with the location, heading, and time that the data was collected. Both current data and snapshots of recent events (e.g., traction control or anti-lock brake system activations) may be reported.
  Data Flows:
  • env_probe_data_from_vehicle
  
  
• traffic probe data - Vehicle data that is used to determine traffic conditions. In a basic implementation, the data could be limited to time stamped unique identifiers that can be used to measure a vehicle’s progress through the network. In more advanced implementations, the vehicle may report current position, speed, and heading and snapshots of recent events including route information, starts and stops, speed changes, and other information that can be used to estimate traffic conditions.
  Data Flows:
  • traffic_probe_data_from_vehicle
  • guidance_probe_data_from_vehicle
  
  
• traveller profile - Information about a traveller including equipment capabilities, personal preferences, and traveller alert subscriptions.
  Data Flows:
  • vehicle_alert_subscriptions
  • vehicle_profile
  
  
• traveller request - A request for traveller information including traffic, transit, toll, parking, road weather conditions, event, and passenger rail information. The request identifies the type of information, the area of interest, parameters that are used to prioritize or filter the returned information, and sorting preferences.
  Data Flows:
  • vehicle_information_request
  • advanced_tolls_and_fares_request
  • driver_display_update_payment_request
  • advanced_fares_and_charges_request
  • driver_map_update_payment_request
  
  
• trip confirmation - Acknowledgement by the driver/traveller of acceptance of a trip plan with associated personal and payment information required to confirm reservations.
  Data Flows:
  • vehicle_guidance_route_accepted
  • vehicle_trip_confirmation
  • vehicle_payment_information
  
  
• trip request - Request for trip planning services that identifies the trip origin, destination(s), timing, preferences, and constraints. The request may also include a request for transit and parking reservations and ridesharing options associated with the trip.
  Data Flows:
  • vehicle_trip_request
  • vehicle_route_request
  
  

Vehicle > Maintenance and Construction Vehicle

• safety system status - Current vehicle safety system status indicating the operating condition of these systems and the safety status of the vehicle and driver.
  Data Flows:
  • safety_data_for_mcv
  
  

Vehicle > Map Update Provider

• map update request - Request for a map update which could include a new underlying map or map layer updates.
  Data Flows:
  • tmup-vehicle_map_update_cost_request
  • tmup-request_driver_display_update
  • tmup-vehicle_map_update_request
  • tmup-request_driver_display_update_cost
  
  

Vehicle > Other Vehicle

• vehicle control coordination - Coordination of control commands between leader and follower vehicles allowing vehicles to join and separate from groups of cooperative vehicles, sharing performance capabilities, and coordinating maneuvers between lead and following vehicles.
  Data Flows:
  • tov-platoon_data_to_other_vehicle
  
  
• vehicle intersection safety data - Vehicle path and acceleration data provided by vehicles approaching or occupying an intersection. It identifies the intersection, vehicle position and motion, the anticipated lane and movement that will be used in the intersection, and notification of potential violations or other detected safety hazards.
  Data Flows:
  • tov-safety_status_to_other_vehicle
  
  
• vehicle safety data - Vehicle safety data indicating vehicle location, vehicle motion (speed, heading, acceleration), vehicle control (brakes, steering, throttle, exterior lights), basic vehicle characteristics (length, width). May also include additional vehicle status (e.g., anti-lock brake activation, stability control system activation).
  Data Flows:
  • tov-safety_msg_data_to_other_vehicles
  
  

Vehicle > Parking Management

• vehicle payment information - Information provided for payment of tolls and parking fees including identification that can be used to identify the payment account or source and related vehicle and service information that are used to determine the type and price of service requested.
  Data Flows:
  • parking_lot_payment_confirmation
  • parking_lot_vehicle_payment_data_collect
  
  

Vehicle > Roadway Subsystem

• access request - Request for access to an access-controlled transportation facility.
  Data Flows:
  • vehicle_barrier_access_request
  
  
• automated vehicle status - Data provided by an automated vehicle identifying it's current mode and operational status, current position and motion, preferred route, and information provided to support checking/checkout and coordinated maneuvers while on the automated facility.
  Data Flows:
  • avo_route_data
  • avo_vehicle_condition
  
  
• environmental probe data - Data from vehicle safety and convenience systems that can be used to estimate environmental conditions, including measured air temperature, exterior light status, wiper status, sun sensor status, rain sensor status, traction control status, anti-lock brake status, and other collected vehicle system status and sensor information. The collected data is reported along with the location, heading, and time that the data was collected. Both current data and snapshots of recent events (e.g., traction control or anti-lock brake system activations) may be reported.
  Data Flows:
  • vehicle_env_probe_data
  
  
• probe archive data - Probe data that allows calculation of travel times, volumes, and other measures that support transportation planning. Optionally, this flow also includes origin and destination information for vehicles that opt to provide this information.
  Data Flows:
  • vehicle_traffic_probe_data_for_archive
  • vehicle_guidance_probe_data_for_archive
  
  
• traffic probe data - Vehicle data that is used to determine traffic conditions. In a basic implementation, the data could be limited to time stamped unique identifiers that can be used to measure a vehicle’s progress through the network. In more advanced implementations, the vehicle may report current position, speed, and heading and snapshots of recent events including route information, starts and stops, speed changes, and other information that can be used to estimate traffic conditions.
  Data Flows:
  • vehicle_traffic_probe_data
  • vehicle_guidance_probe_data
  
  
• vehicle diagnostics data - Information about the vehicle and its current operational status that supports vehicle performance monitoring, service, and repair. The flow identifies the vehicle and vehicle type and provides information about the vehicle's current operational status, the current performance of engine-related components, and notification of any identified malfunctions.
  Data Flows:
  • vehicle_status_details_for_emissions
  
  
• vehicle intersection safety data - Vehicle path and acceleration data provided by vehicles approaching or occupying an intersection. It identifies the intersection, vehicle position and motion, the anticipated lane and movement that will be used in the intersection, and notification of potential violations or other detected safety hazards.
  Data Flows:
  • vehicle_status_for_intersection
  
  
• vehicle occupancy - The number of occupants detected by the vehicle.
  Data Flows:
  • vehicle_occupants_detected
  
  
• vehicle safety data - Vehicle safety data indicating vehicle location, vehicle motion (speed, heading, acceleration), vehicle control (brakes, steering, throttle, exterior lights), basic vehicle characteristics (length, width). May also include additional vehicle status (e.g., anti-lock brake activation, stability control system activation).
  Data Flows:
  • vehicle_roadside_safety_data
  
  

Vehicle > Toll Collection

• vehicle payment information - Information provided for payment of tolls and parking fees including identification that can be used to identify the payment account or source and related vehicle and service information that are used to determine the type and price of service requested.
  Data Flows:
  • toll_payment_confirmation
  • toll_vehicle_payment_data_collect
  
  

Vehicle > Traveller Card

• request for payment - Request to deduct cost of service from user's payment account.
  Data Flows:
  • ttc-debited_driver_payment_at_vehicle
  • ttc-debited_payment_at_parking_lot
  • ttc-debited_payment_at_toll_plaza
  • ttc-request_payment_at_parking_lot
  • ttc-request_payment_at_toll_plaza