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 physical object.
This process is associated with the following functional objects:
- Vehicle Basic Safety Communication
- Vehicle Control Warning
- Vehicle Cooperative Cruise Control
- Vehicle Eco-Driving Assist
- Vehicle Emergency Notification
- Vehicle Emissions Monitoring
- Vehicle Environmental Monitoring
- Vehicle Gap Assist
- Vehicle Intersection Warning
- Vehicle Platoon Operations
- Vehicle Queue Warning
- Vehicle Rail Crossing Warning
- Vehicle Restricted Lanes Application
- Vehicle Situation Data Monitoring
- Vehicle Speed Management Assist
- Vehicle System Executive
- Vehicle System Monitoring and Diagnostics
- Vehicle Traveler Information Reception
This process is associated with the following data flows:
- collision_data
- env_sensor_data_from_vehicle
- fbv-brake_servo_response
- fbv-diagnostics_data
- fbv-driver_safety_status
- fbv-vehicle_attitude_data
- fbv-vehicle_driver_inputs
- fbv-vehicle_identity
- fbv-vehicle_motion_data
- fbv-vehicle_occupants
- fbv-vehicle_proximity_data
- fbv-vehicle_safety_status
- fbv-vehicle_security_status
- fbv-vehicle_size
- fbv-vehicle_speed
- fec-service_to_address_code_violation
- fltds-location
- fltds-time
- fpo-physical_presence
- fre-environmental_conditions
- fre-roadway_characteristics:
- fuel_and_charging_status_for_vehicle
- fvru-user_presence_for_vehicles
- fv-vehicle_characteristics
- host_vehicle_details_for_emissions
- host_vehicle_status_for_eco_drive
- intersection_status_data_for_vehicle
- parking_vehicle_payment_number
- roadside_safety_data_to_vehicle
- safety_data
- safety_data_for_mcv
- safety_message_data_for_remote_vehicles
- safety_message_data_from_remote_vehicles
- speed_management_data_to_vehicle
- tbv-vehicle_status_details_for_driver
- toll_vehicle_payment_number
- traffic_situation_data_from_vehicle
- traffic_situation_data_from_vehicle_for_maps
- traffic_situational_data_configuration
- tvsc-vehicle_malfunction_data
- tvsc-vehicle_system_status_for_diagnostics
- tvsc-vehicle_type
- vehicle_characteristics_for_emissions
- vehicle_characteristics_for_roadside
- vehicle_emv_current_status_data
- vehicle_emv_location_data
- vehicle_emv_size_data
- vehicle_emv_speed_data
- vehicle_env_sensor_data
- vehicle_location_for_probe_data
- vehicle_mcv_current_status_data
- vehicle_mcv_location_data
- vehicle_mcv_size_data
- vehicle_mcv_speed_data
- vehicle_ped_current_status_data
- vehicle_ped_device_identity
- vehicle_ped_location_data
- vehicle_ped_size_data
- vehicle_ped_speed_data
- vehicle_ped_time_data
- vehicle_roadside_control_event_data
- vehicle_roadside_current_status_data
- vehicle_roadside_location_data
- vehicle_roadside_size_data
- vehicle_roadside_speed_data
- vehicle_roadside_surveillance_location_data
- vehicle_roadside_surveillance_size_data
- vehicle_roadside_surveillance_speed_data
- vehicle_roadside_surveillance_status_data
- vehicle_status_details_for_broadcast
- vehicle_status_details_for_driver_security
- vehicle_status_details_for_emergencies
- vehicle_status_for_intersection
- vehicle_system_characteristics_for_emissions
- vehicle_system_characteristics_for_roadside
- vehicle_to_transit_current_status_data
- vehicle_to_transit_device_identity
- vehicle_to_transit_location_data
- vehicle_to_transit_size_data
- vehicle_to_transit_speed_data
- vehicle_to_transit_time_data
- vehicle_traffic_situation_data
- vehicle_traffic_situation_data_configuration