Physical Object: Vehicle
Vehicle Basic Safety Communication
Overview
'Vehicle Basic Safety Communication' exchanges current vehicle location and motion information with other vehicles in the vicinity, uses that information to calculate vehicle paths, and warns the driver when the potential for an impending collision is detected. If available, map data is used to filter and interpret the relative location and motion of vehicles in the vicinity. Information from on-board sensors (e.g., radars and image processing) are also used, if available, in combination with the V2V communications to detect non-equipped vehicles and corroborate connected vehicle data. Vehicle location and motion broadcasts are also received by the infrastructure and used by the infrastructure to support a wide range of roadside safety and mobility applications. This object represents a broad range of implementations ranging from basic Vehicle Awareness Devices that only broadcast vehicle location and motion and provide no driver warnings to advanced integrated safety systems that may, in addition to warning the driver, provide collision warning information to support automated control functions that can support control intervention.
This functional object is included in the "Vehicle" physical object.
This functional object is included in the following service packages:
- CVO06: Freight Signal Priority
- MC07: Work Zone Safety Monitoring
- MC11: Maintenance and Construction Signal Priority
- PM01: Parking Space Management
- PM02: Smart Park and Ride System
- PS03: Emergency Vehicle Preemption
- PS07: Incident Scene Safety Monitoring
- PT09: Transit Signal Priority
- PT10: Intermittent Bus Lanes
- PT11: Transit Pedestrian Indication
- PT12: Transit Vehicle at Station/Stop Warnings
- PT13: Vehicle Turning Right in Front of a Transit Vehicle
- ST02: Eco-Traffic Signal Timing
- ST03: Eco-Traffic Metering
- ST04: Roadside Lighting
- ST07: Eco-Lanes Management
- ST08: Eco-Approach and Departure at Signalized Intersections
- ST09: Connected Eco-Driving
- ST10: Low Emissions Zone Management
- TM02: Vehicle-Based Traffic Surveillance
- TM04: Connected Vehicle Traffic Signal System
- TM21: Speed Harmonization
- TM22: Dynamic Lane Management and Shoulder Use
- TM23: Border Management Systems
- TM24: Tunnel Management
- TM25: Wrong Way Vehicle Detection and Warning
- VS02: V2V Basic Safety
- VS03: Situational Awareness
- VS04: V2V Special Vehicle Alert
- VS08: Queue Warning
- VS09: Reduced Speed Zone Warning / Lane Closure
- VS10: Restricted Lane Warnings
- VS12: Vulnerable Road User Safety
- VS13: Intersection Safety Warning and Collision Avoidance
- VS14: Cooperative Adaptive Cruise Control
- VS15: Infrastructure Enhanced Cooperative Adaptive Cruise Control
- VS16: Automated Vehicle Operations
This functional object is mapped to the following Functional View PSpecs:
- 3.1.1: Produce Collision and Crash Avoidance Data
- 3.1.3: Process Vehicle On-board Data
- 3.1.4: Communicate with Remote Vehicles
- 3.1.6: Provide Vehicle Acceleration and Deceleration Inputs
- 3.2.3.2: Manage Platoon Following
- 3.2.3.3: Process Data for Vehicle Actuators
- 3.2.3.5.1: Process General Vehicle Sensor Data
- 3.2.4: Process Sensor Data for Automatic Vehicle Operations
- 6.7.1.3: Process Vehicle Location Data
- 6.7.1.4: Update Vehicle Navigable Map Database
- 6.7.3.2: Provide Driver Information Interface
Requirements
# | Requirement |
---|---|
01 | The vehicle shall collect location and motion data from the vehicle platform. |
02 | The vehicle shall provide its location with lane-level accuracy to on-board applications. |
03 | The vehicle shall provide its location with road-level accuracy to on-board applications. |
04 | The vehicle shall collect road condition data from other vehicles. |
05 | The vehicle shall calculate vehicle paths in order to determine if an impending collision is detected. |
06 | The vehicle shall exchange location and motion information with roadside equipment and nearby vehicles. |
07 | The vehicle shall receive warnings, informational road signs, traffic meters, and signals provided by infrastructure devices. |
08 | The vehicle shall warn the driver of an Emergency Electronic Brake Light (EEBL) Event. |
09 | The vehicle shall determine when its host Vehicle is braking in an emergency fashion and broadcast an Emergency Electronic Brake Light (EEBL) notification. |
10 | The vehicle shall determine the status of host vehicle systems including vehicle speed, heading, yaw, wheelspin, ABS, traction control, and wiper status. |
11 | The vehicle shall determine if vehicle systems status indicates a potentially hazardous road condition. |
12 | The vehicle shall analyze its own applications' performance and enter fail-safe mode (a mode such that the application cannot provide information or perform actions that affect its host) when critical components fail. |
13 | The vehicle shall notify the driver when onboard components or safety applications are offline. |
14 | The vehicle shall determine if road conditions data received from other vehicles represent a potential safety hazard for the vehicle. |
15 | The vehicle shall provide its location to nearby traveler devices. |
Information Flows
Standards
Currently, there are no standards associated with the functional object itself though the interfaces may have standards associated with them.