3.1.3: Process Vehicle On-board Data

This process shall be responsible for processing data received as input to sensors located on-board a vehicle through what is called the Vehicle Databus. These sensors may also be called the Host Vehicle (HV) or simply the Vehicle Platform. This process shall also receive inputs from other surrounding vehicles (also called Remote Vehicles (RV)) and sensors located in the roadway providing intersection geometry or activity in the intersection. The process shall continuously analyze these inputs, along with a precise current time and location of the vehicle provided by the Location and Time Data Source terminator. This process shall periodically transmit safety message data to other (remote) vehicles via another process including position, heading, speed, braking, transmission gear, traction control status. This process shall send collision data to another process to Produce Collision and Crash Avoidance Data when this process determines that a collision is possible based on location and headings of nearby vehicles relative to the Host Vehicle - e.g. Intersection Movement (other vehicles intersecting from the left or right, vehicles in the forward direction, in the blind spot, or in an adjacent lane but represent a hazard if a lane change is attempted, i.e., they are in the vehicle's blind spot). Additionally, the traffic and environmental sensor data can be sent as probe data to processes either at nearby roadside stations or remotely at processing centers. The process may produce data from which safety, environmental, and/or position warnings and actions can be produced by another process. It shall also analyze the data to check for hazardous roadside conditions such as flooding, ice, snow, etc. and if detected shall output this data to processes in the Manage Traffic, Manage Maintenance and Construction, Manage Emergency Services, and Provide Driver and Traveler Services functions. This process shall communicate the status of the safety systems on-board to surrounding vehicles using wireless communications safety messages. For High Occupancy Vehicle lanes, this process shall determine the number of occupants on board from the Vehicle Databus inputs and provide it to the roadside for processing. This process shall calculate vehicle speed and distance traveled, and provide time-stamped data to another process as VMT data for calculation of vehicle road use charges. This process shall read the basic vehicle profile or characteristics such as size and configuration from the vehicle databus and provide that to the safety analysis function.

This process is associated with the Vehicle OBE physical object.

This process is associated with the following application objects:

This process is associated with the following data flows:

collision_data - Out
env_sensor_data_from_vehicle - Out
fuel_and_charging_status_for_vehicle - Out
fvdb-brake_servo_response - In
fvdb-diagnostics_data - In
fvdb-driver_safety_status - In
fvdb-vehicle_attitude_data - In
fvdb-vehicle_charging_capacity - In
fvdb-vehicle_charging_status - In
fvdb-vehicle_driver_inputs - In
fvdb-vehicle_identity - In
fvdb-vehicle_motion_data - In
fvdb-vehicle_occupants - In
fvdb-vehicle_proximity_data - In
fvdb-vehicle_safety_status - In
fvdb-vehicle_security_status - In
fvdb-vehicle_size - In
fvdb-vehicle_speed - In
fvltds-location - In
fvltds-time - In
host_vehicle_details_for_emissions - Out
host_vehicle_status_for_eco_drive - Out
intersection_status_data_for_vehicle - In
parking_vehicle_payment_number - In
roadside_safety_data_to_vehicle - In
safety_data - Out
safety_data_for_mcv - Out
safety_message_data_for_remote_vehicles - Out
safety_message_data_from_remote_vehicles - In
speed_management_data_to_vehicle - In
toll_vehicle_payment_number - In
traffic_situation_data_from_vehicle - Out
traffic_situation_data_from_vehicle_for_maps - Out
traffic_situational_data_configuration - In
tvdb-vehicle_status_details_for_driver - Out
vehicle_characteristics_for_emissions - Out
vehicle_characteristics_for_roadside - Out
vehicle_emv_current_status_data - Out
vehicle_emv_location_data - Out
vehicle_emv_size_data - Out
vehicle_emv_speed_data - Out
vehicle_env_sensor_data - Out
vehicle_identity_for_central_payment_admin - Out
vehicle_identity_for_road_use_payment - Out
vehicle_location_for_central_payment_admin - Out
vehicle_location_for_probe_data - In
vehicle_location_for_road_use_payment - Out
vehicle_location_for_vmt - Out
vehicle_mcv_current_status_data - Out
vehicle_mcv_location_data - Out
vehicle_mcv_size_data - Out
vehicle_mcv_speed_data - Out
vehicle_occupants_detected - Out
vehicle_ped_current_status_data - Out
vehicle_ped_device_identity - Out
vehicle_ped_location_data - Out
vehicle_ped_size_data - Out
vehicle_ped_speed_data - Out
vehicle_ped_time_data - Out
vehicle_roadside_control_event_data - Out
vehicle_roadside_current_status_data - Out
vehicle_roadside_location_data - Out
vehicle_roadside_size_data - Out
vehicle_roadside_speed_data - Out
vehicle_roadside_surveillance_location_data - Out
vehicle_roadside_surveillance_size_data - Out
vehicle_roadside_surveillance_speed_data - Out
vehicle_roadside_surveillance_status_data - Out
vehicle_speed_and_distance_for_central_payment_admin - Out
vehicle_speed_and_distance_for_road_use_payment - Out
vehicle_status_details_for_broadcast - Out
vehicle_status_details_for_driver_security - Out
vehicle_status_details_for_emergencies - Out
vehicle_status_for_intersection - Out
vehicle_system_characteristics_for_emissions - Out
vehicle_system_characteristics_for_roadside - Out
vehicle_to_transit_current_status_data - Out
vehicle_to_transit_device_identity - Out
vehicle_to_transit_location_data - Out
vehicle_to_transit_size_data - Out
vehicle_to_transit_speed_data - Out
vehicle_to_transit_time_data - Out
vehicle_traffic_probe_data_for_archive - Out
vehicle_traffic_situation_data - Out
vehicle_traffic_situation_data_configuration - In