Vehicle (Subsystem*)

Subsystem Interfaces Diagram

Terminator Interfaces Diagram

Functionality: Equipment Packages* and PSpecs*

• Basic Vehicle Reception (Equipment Package*)
  PSpecs:
  • 6.7.3.2-Provide Driver with Personal Travel Information
  • 6.7.3.3-Provide Driver Information Interface

• Driver Safety Monitoring System (Equipment Package*)
  PSpecs:
  • 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 (Equipment Package*)
  PSpecs:
  • 3.4-Enhance Driver's Vision
  • 6.7.3.3-Provide Driver Information Interface

• Interactive Vehicle Reception (Equipment Package*)
  PSpecs:
  • 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 (Equipment Package*)
  PSpecs:
  • 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 (Equipment Package*)
  PSpecs:
  • 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 (Equipment Package*)
  PSpecs:
  • 3.1.3-Process Vehicle On-board Data

• Vehicle Intersection Control (Equipment Package*)
  PSpecs:
  • 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 (Equipment Package*)
  PSpecs:
  • 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 (Equipment Package*)
  PSpecs:
  • 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 (Equipment Package*)
  PSpecs:
  • 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 (Equipment Package*)
  PSpecs:
  • 6.7.1.3-Process Vehicle Location Data
  • 6.7.1.4-Update Vehicle Navigable Map Database

• Vehicle Longitudinal Control (Equipment Package*)
  PSpecs:
  • 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 (Equipment Package*)
  PSpecs:
  • 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 (Equipment Package*)
  PSpecs:
  • 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 (Equipment Package*)
  PSpecs:
  • 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 (Equipment Package*)
  PSpecs:
  • 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 (Equipment Package*)
  PSpecs:
  • 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 (Equipment Package*)
  PSpecs:
  • 3.5-Generate Vehicle Access Requests
  • 6.7.3.3-Provide Driver Information Interface

• Vehicle Short Range Traveler Information Reception (Equipment Package*)
  PSpecs:
  • 6.7.3.2-Provide Driver with Personal Travel Information
  • 6.7.3.3-Provide Driver Information Interface

• Vehicle Toll/Parking Interface (Equipment Package*)
  PSpecs:
  • 7.1.4-Provide Driver Toll Payment Interface
  • 7.1.7-Provide Traveler Card Interface for Tolls
  • 7.2.4-Provide Driver Parking Lot Payment Interface
  • 7.2.7-Provide Traveler Card Interface for Parking
  • 7.5.1-Provide Vehicle Traveler Card Interface

• Vehicle Traffic Probe Support (Equipment Package*)
  PSpecs:
  • 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 (Equipment Package*)
  PSpecs:
  • 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 VMT Payment Collection (Equipment Package*)
  PSpecs:
  • 3.1.3-Process Vehicle On-board Data
  • 6.7.3.3-Provide Driver Information Interface
  • 7.6.3-Provide Driver VMT Payment Interface
  • 7.6.4-Provide Traveler Card Interface for VMT

• Vehicle Warning System (Equipment Package*)
  PSpecs:
  • 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 (Architecture Flow*) - Information provided to on-board ITS equipment from the vehicle platform indicating current vehicle status.
  Data Flows*:
  • fbv-brake_servo_response
  • fbv-crash_sensor_data
  • fbv-diagnostics_data
  • fbv-driver_safety_status
  • fbv-steering_servo_response
  • fbv-throttle_servo_response
  • fbv-vehicle_attitude_data
  • fbv-vehicle_condition
  • fbv-vehicle_headway
  • fbv-vehicle_identity
  • fbv-vehicle_lane_position
  • fbv-vehicle_motion_data
  • fbv-vehicle_occupants
  • fbv-vehicle_on_avo_lane
  • fbv-vehicle_proximity_data
  • fbv-vehicle_safety_status
  • fbv-vehicle_security_status
  • fbv-vehicle_speed

Commercial Vehicle Vehicle

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

Driver Vehicle

• driver inputs (Architecture Flow*) - Driver input to the vehicle including configuration data, settings and preferences, interactive requests, and control commands.
  Data Flows*:
  • fd-activate_vehicle_control
  • fd-guidance_data
  • fd-guidance_map_update_request
  • fd-guidance_route_accepted
  • fd-request_advisory_information
  • fd-vehicle_display_configuration_override
  • fd-vehicle_display_configuration_setting

• request for service (Architecture Flow*) - Driver inputs that summon an emergency response, request a financial transaction, or initiate other services.
  Data Flows*:
  • fd-driver_vehicle_access_request
  • fd-emergency_request
  • fd-guidance_request
  • fd-other_services_parking_request
  • fd-other_services_toll_request

Emergency Management Vehicle

• emergency acknowledge (Architecture Flow*) - Acknowledge request for emergency assistance and provide additional details regarding actions and verification requirements.
  Data Flows*:
  • emergency_request_driver_acknowledge
  • emergency_request_vehicle_acknowledge

• emergency data request (Architecture Flow*) - 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 traveler.
  Data Flows*:
  • emergency_data_request
  • vehicle_security_system_commands

Emergency Vehicle Vehicle

• emergency vehicle alert (Architecture Flow*) - 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 (Architecture Flow*) - 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 traveler information (Architecture Flow*) - General traveler information that contains traffic and road conditions, link travel times, incidents, advisories, restrictions, transit service information, weather information, parking information, and other related traveler information.
  Data Flows*:
  • link_and_queue_data
  • vehicle_broadcast_border_data
  • vehicle_broadcast_event_information
  • vehicle_broadcast_incident_information
  • vehicle_broadcast_multimodal_data
  • vehicle_broadcast_parking_data
  • vehicle_broadcast_price_data
  • vehicle_broadcast_traffic_data
  • vehicle_broadcast_transit_data
  • vehicle_broadcast_weather_data

• emergency traveler information (Architecture Flow*) - 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, traveler services and shelter information, and reentry times and instructions.
  Data Flows*:
  • vehicle_emergency_traveler_information
  • vehicle_evacuation_traveler_information
  • vehicle_transportation_system_status
  • vehicle_wide_area_alert_information

• interactive traveler information (Architecture Flow*) - Traveler information provided in response to a traveler 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_fares_and_charges_response
  • advanced_tolls_and_fares_response
  • driver_display_update_payment_response
  • driver_map_update_payment_response
  • vehicle_interactive_border_data
  • vehicle_interactive_event_information
  • vehicle_interactive_incident_information
  • vehicle_interactive_multimodal_data
  • vehicle_interactive_parking_data
  • vehicle_interactive_price_data
  • vehicle_interactive_traffic_data
  • vehicle_interactive_transit_data
  • vehicle_interactive_weather_data

• traffic probe reporting management (Architecture Flow*) - Data used to manage probe data reporting by vehicles. This flow indicates to the vehicle when to report probe data, the type of probe data to send, and thresholds for nominal conditions when sending data can be skipped.
  Data Flows*:
  • traffic_probe_configuration

• travel services information (Architecture Flow*) - Travel service information and reservations for tourist attractions, lodging, dining, service stations, emergency services, and other services and businesses of interest to the traveler.
  Data Flows*:
  • vehicle_transaction_confirmation
  • vehicle_travel_services_provider_data

• traveler alerts (Architecture Flow*) - Traveler information alerts reporting congestion, incidents, adverse road or weather conditions, parking availability, transit service delays or interruptions, and other information that may impact the traveler. Relevant alerts are provided based on traveler-supplied profile information including trip characteristics and preferences.
  Data Flows*:
  • vehicle_border_alert
  • vehicle_event_alert
  • vehicle_incident_alert
  • vehicle_multimodal_alert
  • vehicle_parking_alert
  • vehicle_traffic_alert
  • vehicle_transit_alert
  • vehicle_weather_alert

• trip plan (Architecture Flow*) - A travel itinerary identifying a route and associated traveler information and instructions identifying recommended modes and transfer information, ride sharing options, and transit and parking reservation information.
  Data Flows*:
  • vehicle_guidance_route
  • vehicle_payment_confirmation
  • vehicle_trip_information

Location Data Source Vehicle

• position fix (Architecture Flow*) - Information which provides a traveler's or vehicle's geographical position.
  Data Flows*:
  • From_Location_Data_Source

Maintenance and Construction Vehicle Vehicle

• vehicle signage data (Architecture Flow*) - 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 (Architecture Flow*) - Map update which could include a new underlying static or real-time map or map layer(s) update.
  Data Flows*:
  • fmup-driver_display_update
  • fmup-driver_display_update_cost
  • fmup-vehicle_map_update
  • fmup-vehicle_map_update_cost

Other Vehicle Vehicle

• vehicle control coordination (Architecture Flow*) - 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 (Architecture Flow*) - 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 (Architecture Flow*) - 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 (Architecture Flow*) - 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 (Architecture Flow*) - Request for information supporting toll and parking payments.
  Data Flows*:
  • parking_lot_payment_request
  • parking_lot_vehicle_payment_data_request

• vehicle payment update (Architecture Flow*) - 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

Payment Administration Vehicle

• vehicle payment request (Architecture Flow*) - Request for information supporting toll and parking payments.
  Data Flows*:
  • vmt_payment_request_from_admin
  • vmt_vehicle_payment_data_clear_from_admin

• VMT cost data (Architecture Flow*) - VMT charges per link.
  Data Flows*:
  • vmt_cost_data

Potential Obstacles Vehicle

• physical presence (Architecture Flow*) - Detection of an obstacle. Obstacle could include animals, vehicles, pedestrians, rocks in roadway etc.
  Data Flows*:
  • From_Potential_Obstacles

Roadway Vehicle

• access permission (Architecture Flow*) - Information returned indicating whether permission for access is granted and instructions for proceeding.
  Data Flows*:
  • vehicle_barrier_access_status

• automated vehicle control data (Architecture Flow*) - 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*:
  • avo_check_response
  • lane_change_details
  • lane_change_strategy

• broadcast traveler information (Architecture Flow*) - General traveler information that contains traffic and road conditions, link travel times, incidents, advisories, restrictions, transit service information, weather information, parking information, and other related traveler information.
  Data Flows*:
  • field_to_vehicle_broadcast_border_data
  • field_to_vehicle_broadcast_event_information
  • field_to_vehicle_broadcast_incident_information
  • field_to_vehicle_broadcast_multimodal_data
  • field_to_vehicle_broadcast_parking_data
  • field_to_vehicle_broadcast_price_data
  • field_to_vehicle_broadcast_traffic_data
  • field_to_vehicle_broadcast_transit_data
  • field_to_vehicle_broadcast_weather_data

• emergency traveler information (Architecture Flow*) - 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, traveler services and shelter information, and reentry times and instructions.
  Data Flows*:
  • field_to_vehicle_emergency_traveler_information
  • field_to_vehicle_evacuation_traveler_information
  • field_to_vehicle_transportation_system_status
  • field_to_vehicle_wide_area_alert_information

• intersection status (Architecture Flow*) - 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 (Architecture Flow*) - 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

• traffic probe reporting management (Architecture Flow*) - Data used to manage probe data reporting by vehicles. This flow indicates to the vehicle when to report probe data, the type of probe data to send, and thresholds for nominal conditions when sending data can be skipped.
  Data Flows*:
  • vehicle_traffic_probe_configuration

• vehicle signage data (Architecture Flow*) - 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_env_probe_data_output
  • vehicle_signage_data
  • vehicle_signage_emissions_testing_results

Roadway Environment Vehicle

• environmental conditions (Architecture Flow*) - 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 (Architecture Flow*) - 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-roadside_data
  • fre-roadway_characteristics

Roadway Payment Vehicle

• vehicle payment request (Architecture Flow*) - Request for information supporting toll and parking payments.
  Data Flows*:
  • toll_payment_request
  • toll_vehicle_payment_data_request
  • vmt_payment_request

• vehicle payment update (Architecture Flow*) - Data written to vehicle equipment to support electronic toll collection or parking payment.
  Data Flows*:
  • toll_payment_debited
  • toll_vehicle_payment_data_clear
  • toll_vehicle_payment_data_update
  • vmt_vehicle_payment_data_clear

Transit Vehicle Vehicle

• vehicle signage data (Architecture Flow*) - 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

Traveler Card Vehicle

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

Vehicle Basic Vehicle

• vehicle control (Architecture Flow*) - Vehicular control commands
  Data Flows*:
  • tbv-change_brake_setting
  • tbv-change_direction
  • tbv-change_throttle_setting
  • tbv-deploy_crash_restraints
  • tbv-steer_left
  • tbv-steer_right
  • tbv-steer_straight
  • tbv-vehicle_security_system_commands

Vehicle Commercial Vehicle

• commercial vehicle data request (Architecture Flow*) - 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 (Architecture Flow*) - Information displayed or otherwise conveyed by the vehicle to the driver.
  Data Flows*:
  • td-advisory_information
  • td-broadcast_information
  • td-driver_vehicle_access_status
  • td-driving_guidance
  • td-guidance_input_request
  • td-guidance_map_update_response
  • td-guidance_route_details
  • td-vehicle_occupants_detected

• in-vehicle transaction status (Architecture Flow*) - The status of an electronic payment transaction presented to the driver by in-vehicle equipment.
  Data Flows*:
  • td-other_services_parking_response
  • td-other_services_toll_response
  • td-vmt_cost_data
  • td-vmt_payment_confirmation

Vehicle Emergency Management

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

Vehicle Information Service Provider

• emergency traveler information request (Architecture Flow*) - Request for alerts, evacuation information, and other emergency information provided to the traveling public.
  Data Flows*:
  • vehicle_emergency_information_request

• environmental probe data (Architecture Flow*) - 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 (Architecture Flow*) - 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*:
  • guidance_probe_data_from_vehicle
  • traffic_probe_data_from_vehicle

• travel services request (Architecture Flow*) - 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_travel_services_data_request

• traveler profile (Architecture Flow*) - Information about a traveler including equipment capabilities, personal preferences, and traveler alert subscriptions.
  Data Flows*:
  • vehicle_alert_subscriptions
  • vehicle_profile

• traveler request (Architecture Flow*) - A request for traveler 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*:
  • advanced_fares_and_charges_request
  • advanced_tolls_and_fares_request
  • driver_display_update_payment_request
  • driver_map_update_payment_request
  • vehicle_information_request

• trip confirmation (Architecture Flow*) - Acknowledgement by the driver/traveler of acceptance of a trip plan with associated personal and payment information required to confirm reservations.
  Data Flows*:
  • vehicle_guidance_route_accepted
  • vehicle_payment_information
  • vehicle_payment_information_for_services
  • vehicle_trip_confirmation

• trip request (Architecture Flow*) - 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_route_request
  • vehicle_trip_request

Vehicle Maintenance and Construction Vehicle

• safety system status (Architecture Flow*) - 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 (Architecture Flow*) - Request for a map update which could include a new underlying map or map layer updates.
  Data Flows*:
  • tmup-request_driver_display_update
  • tmup-request_driver_display_update_cost
  • tmup-vehicle_map_update_cost_request
  • tmup-vehicle_map_update_request

Vehicle Other Vehicle

• vehicle control coordination (Architecture Flow*) - 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 (Architecture Flow*) - 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 (Architecture Flow*) - 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 (Architecture Flow*) - 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 Payment Administration

• vehicle payment information (Architecture Flow*) - 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*:
  • vmt_payment_collected_for_admin
  • vmt_payment_confirmation_for_admin

• VMT data (Architecture Flow*) - A vehicle’s road use history that records where the vehicle has traveled over time. Optionally includes vehicle speeds as well as distance traveled for some applications. Information is accurate enough to distinguish between adjacent roads, adjacent lanes, and identify direction of travel on the roads.
  Data Flows*:
  • vehicle_identity_for_vmt
  • vehicle_location_for_vmt
  • vehicle_speed_and_distance_for_vmt

Vehicle Roadway

• access request (Architecture Flow*) - Request for access to an access-controlled transportation facility.
  Data Flows*:
  • vehicle_barrier_access_request

• automated vehicle status (Architecture Flow*) - 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 (Architecture Flow*) - 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 (Architecture Flow*) - 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_guidance_probe_data_for_archive
  • vehicle_traffic_probe_data_for_archive

• traffic probe data (Architecture Flow*) - 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_guidance_probe_data
  • vehicle_traffic_probe_data

• vehicle diagnostics data (Architecture Flow*) - 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 (Architecture Flow*) - 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 (Architecture Flow*) - The number of occupants detected by the vehicle.
  Data Flows*:
  • vehicle_occupants_detected

• vehicle profile (Architecture Flow*) - Information about a vehicle including vehicle type and equipment capabilities.
  Data Flows*:
  • vehicle_characteristics_for_roadway

• vehicle safety data (Architecture Flow*) - 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 Roadway Payment

• vehicle payment information (Architecture Flow*) - 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
  • vmt_payment_collected
  • vmt_payment_confirmation

• VMT data (Architecture Flow*) - A vehicle’s road use history that records where the vehicle has traveled over time. Optionally includes vehicle speeds as well as distance traveled for some applications. Information is accurate enough to distinguish between adjacent roads, adjacent lanes, and identify direction of travel on the roads.
  Data Flows*:
  • vehicle_identity_for_vmt_roadway
  • vehicle_location_for_vmt_roadway
  • vehicle_speed_and_distance_for_vmt_roadway

• VMT equipment status (Architecture Flow*) - Provides an indication of the operational status of the VMT data collection equipment in a vehicle. Also indicates vehicle ID (VIN) so that the registration of the equipment to a specific vehicle can be verified and confirmed by comparison with vehicle characteristics.
  Data Flows*:
  • vmt_equipment_status

Vehicle Traveler Card

• request for payment (Architecture Flow*) - 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-debited_vmt_payment
  • ttc-request_payment_at_parking_lot
  • ttc-request_payment_at_toll_plaza
  • ttc-request_vmt_payment