Type: Resource

Vehicle OBE

Overview

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.

This resource is related to the "Vehicle OBE" physical object.

This resource is included in the following applications:

Coordination

Source Coordination Destination
Device Certification Entity Certifies Vehicle OBE
Device Certification Requirements Constrains Vehicle OBE
Vehicle Includes Vehicle OBE
Vehicle OBE Extends Commercial Vehicle OBE
Vehicle OBE Extends Emergency Vehicle OBE
Vehicle OBE Extends Maint and Constr Vehicle OBE
Vehicle OBE Extends Transit Vehicle OBE
Vehicle OBE Includes Vehicle Basic Safety
Vehicle OBE Includes Vehicle Border Crossing Support
Vehicle OBE Includes Vehicle Communications Support
Vehicle OBE Includes Vehicle Cooperative Cruise Control
Vehicle OBE Includes Vehicle Eco-Driving Assist
Vehicle OBE Includes Vehicle Electric Charging Assist
Vehicle OBE Includes Vehicle Emergency Notification I/F
Vehicle OBE Includes Vehicle Emissions Monitoring
Vehicle OBE Includes Vehicle Environmental Monitoring
Vehicle OBE Includes Vehicle Gap Assist
Vehicle OBE Includes Vehicle Interactive Traveler Information
Vehicle OBE Includes Vehicle Intersection Warning
Vehicle OBE Includes Vehicle Map Management
Vehicle OBE Includes Vehicle Mayday Notification
Vehicle OBE Includes Vehicle Payment Service
Vehicle OBE Includes Vehicle Queue Warning
Vehicle OBE Includes Vehicle Rail Crossing Warning
Vehicle OBE Includes Vehicle Restricted Lanes Application
Vehicle OBE Includes Vehicle Roadside Information Reception
Vehicle OBE Includes Vehicle Situation Data Monitoring
Vehicle OBE Includes Vehicle Speed Management Assist
Vehicle OBE Includes Vehicle Support Services
Vehicle OBE Includes Vehicle Toll/Parking Payment
Vehicle OBE Includes Vehicle Traveler Information Reception
Vehicle OBE Includes Vehicle Trip Planning and Route Guidance
Vehicle OBE Includes Vehicle Trust Management
Vehicle OBE Manufacturer Develops Vehicle OBE
Vehicle OBE Manufacturer Owns Vehicle OBE
Vehicle OBE Owner Owns Vehicle OBE
Vehicle Trip Planning and Route Guidance Installer Installs Vehicle OBE
Vehicle Trip Planning and Route Guidance Maintainer Maintains Vehicle OBE

Security

Interfaces Diagram

Interfaces diagram

Alternative Configurations

Four diagrams below illustrate four different implementations that may be represented by the Vehicle On-Board Equipment: 1) Vehicle Awareness Device, 2) Aftermarket Device, 3) Retrofit Device, or 4) Integrated System. Each diagram shows the subset of interfaces from CVRIA that are relevant to that particular implementation. Note that a V2V safety application is shown, but the four implementation options also provide varied support for other connected vehicle applications. Map provider shown as it is a likely interface for many safety applications, and the different points at which the map hooks in are illustrative of changes in necessary relationships. A fifth diagram covers a scenario where an aftermarket carry-in device is carried in to a vehicle that is already equipped with one of the Vehicle OBE implementations.

1. Vehicle Awareness Device – This is an aftermarket electronic device, installed in a vehicle without connection to vehicle systems, that is only capable of sending the basic safety message over short range communications. Vehicle awareness devices do not issue audible or visual warnings, alerts, or guidance to the driver of the vehicle.

2. Aftermarket Device – This is an aftermarket electronic device, installed in a vehicle, and capable of sending and receiving messages over a wireless communications link. The self-contained device includes GPS, runs connected vehicle applications, and includes an integrated driver interface that issues audible or visual warnings, alerts, and guidance to the driver of the vehicle. The aftermarket device may or may not have access to some vehicle system status.

3. Retrofit Device – This is an OEM authorized electronic device installed in vehicles by an OEM authorized service provider, at a service facility after the vehicle has been built. This type of device provides two-way communications and is connected to a vehicle databus. Depending on implementation, the device may include an integrated driver interface and GPS or integrate with modules on the vehicle databus that provide these services. Depending on implementation, it may only support some of the connected vehicle applications identified in CVRIA and potentially support additional applications that are not identified in CVRIA.

4. Integrated System – This is a system of one or more electronic devices integrated into vehicles during vehicle production. The Integrated System is connected to proprietary data busses to share information with other on-board systems. The Integrated System may be distributed across multiple subsystems and may be configured to support some of the connected vehicle applications identified in CVRIA and potentially support additional applications that are not identified in CVRIA.



In retrofit and integrated implementations, the Vehicle OBE interfaces to other on-board systems through a vehicle databus (e.g., CAN). Represented in CVRIA as the Vehicle Databus, this interface provides access to on-board sensors, monitoring and control systems, and information systems that support connected vehicle applications. The vehicle databus may also be the source for GPS location and time, map data that supports connected vehicle applications, and the access point for the vehicle's driver-vehicle interface.

5. A fifth diagram covers a scenario where an aftermarket carry-in device is carried in to a vehicle that is already equipped with one of the Vehicle OBE implementations. In this scenario, we have two different devices with possibly two different radios and two different user interfaces that must be coordinated to avoid interference or conflicts.