Vehicle OBE --> Vehicle Databus:
pre-crash control information

Definitions

pre-crash control information (Information Flow): Notification to vehicle control systems that a crash is imminent, initiating and directing pre-crash actions that may include seatbelt tightening, brake assist, airbag pre-arming, and bumper raising/extension.

Vehicle OBE (Source Physical Object): The Vehicle On-Board Equipment (OBE) provides the vehicle-based processing, storage, and communications functions necessary to support connected vehicle operations. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle OBE. This communication platform is augmented with processing and data storage capability that supports the connected vehicle applications.

In CVRIA, the Vehicle OBE includes the functions and interfaces that support connected vehicle applications for passenger cars, trucks, and motorcycles. Many of these applications (e.g., V2V Safety applications) apply to all vehicle types including personal vehicles, commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle OBE includes the common interfaces and functions that apply to all motorized vehicles.

Vehicle Databus (Destination Physical Object): The 'Vehicle Databus' represents the interface to the vehicle databus (e.g., CAN, LIN, Ethernet/IP, FlexRay, and MOST) that may enable communication between the Vehicle OBE and other vehicle systems to support connected vehicle applications. The vehicle system statuses and/or sensor outputs available on the databus will vary based on the equipment installed on the vehicle and availability on databus. System statuses and sensor outputs may include select vehicle systems and sensors such as accelerometers, yaw rate sensors, and GPS derived location and timing information. In CVRIA, this physical object is used to represent the onboard interactions between the Vehicle OBE and the other systems included in a host vehicle.

Note that the vehicle databus interface is not standardized across all vehicle classes. Also, some Vehicle OBE implementations will not have access to the vehicle databus. See 'Vehicle OBE' for more information.

Included In

This Information Flow is in the following Applications:

• Pre-crash Actions

This Information Flow is in the following Application Objects:

• Vehicle Basic Safety

Communication Diagrams

The communication diagram(s) can be viewed in SVG or PNG format and the current format is SVG. Switch to SVG format. PNG format.

This partial profile, showing only physical objects and flow, describes communications between equipment that reside on the vehicle. The CVRIA does not contain any specific information on standards for on-board vehicle communications.

Characteristics

Architectural:

Security

This information flow triple is in the following applications with the following security levels.