3.1.1: Produce Collision and Crash Avoidance Data

This process shall be responsible for sensing and evaluating the likelihood of a collision between two vehicles or a vehicle and a stationary object. The process shall base its detection on input from three other processes. One of these processes shall be that which continuously processes sensor inputs on-board the vehicle, including safety messages received from surrounding vehicles and the roadside, the second shall be that which detects collision situations and signal phase and timing data at intersections, and the third input alerts the vehicle of the proximity of emergency vehicles that are responding to an incident. This process may also receive information from the other on-board processes that indicate another vehicle in the vicinity is hard braking or that another vehicle is infringing on an intersection, i.e. crossing the stopbar without stopping or running a red light. This process shall determine whether that other vehicle that is in an emergency braking situation represents a potential hazard. When an event is detected this process shall output the appropriate messages to another process in the vehicle to warn the driver, including positional warnings such as intersection movement assistance (IMA), blind spot (BSW), Control Loss Warnings (CLW), Electronic Emergency Brake Light (EEL), Lane Change Warnings (LCW), Do Not Pass Warnings (DNPW) or forward collision warnings (FCW), including a tailgating warning if the analysis indicates the host vehicle is following too closely to the vehicle in front. If the vehicle is suitably equipped, the process shall initiate the deployment of crash restraint devices in advance of the collision and/or generate data to initiate direct operation of the vehicle to take evasive maneuvers. This process shall provide other processes in the intersection with data on its speed and intended direction as it approaches an intersection. If the collision data input indicates that the vehicle is now braking then this process shall determine whether it is appropriate to cancel the position warnings or vehicle action requests. Should this process determine that the vehicle is about infringe on an intersection, i.e. crossing the stopbar without stopping or running a red light; it shall notify other processes to warn nearby remote vehicles and the infrastructure.

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 Gap Assist
• Vehicle Intersection Warning
• Vehicle Queue Warning
• Vehicle Rail Crossing Warning

This process is associated with the following data flows:

• emergency_vehicle_proximity
• intersection_collision_avoidance_data
• tbv-deploy_crash_restraints
• vehicle_location_in_roadway
• vehicle_actuator_feedback_for_crash_avoidance
• collision_data
• position_warnings
• vehicle_action_requests
• vehicle_intersection_infringement
• intersection_infringement_for_remote_vehicle
• intersection_infringement_from_remote_vehicle
• signal_phase_indication_to_vehicle
• signal_phase_timing_to_vehicle
• signal_phase_response_state_to_vehicle
• stop_sign_gap_data_to_vehicle
• tbv-collision_warning_information
• queue_warning_from_roadside
• personal_mobile_device_identity_for_veh
• personal_mobile_location_data_for_veh
• personal_mobile_time_data_for_veh
• signal_phase_indication_from_center_to_vehicles
• signal_phase_timing_from_center_to_vehicles
• mmv_location_for_vehicles
• queue_warning_from_center