Type: Resource
Mobile Component Development System
Overview
The system used in a backoffice environment to develop and test the mobile component of the application.
This resource is included in the following applications:
- Advanced Automatic Crash Notification Relay
- Advanced Traveler Information Systems
- Blind Spot Warning + Lane Change Warning
- Border Management Systems
- Connected Eco-Driving
- Container Security
- Container/Chassis Operating Data
- Control Loss Warning
- Cooperative Adaptive Cruise Control
- Core Authorization
- Curve Speed Warning
- Do Not Pass Warning
- Dynamic Eco-Routing
- Dynamic Ridesharing
- Dynamic Transit Operations
- Eco-Approach and Departure at Signalized Intersections
- Eco-Cooperative Adaptive Cruise Control
- Eco-Lanes Management
- Eco-Ramp Metering
- Eco-Speed Harmonization
- Eco-Traffic Signal Timing
- Eco-Transit Signal Priority
- Electric Charging Stations Management
- Electronic Toll Collection
- Emergency Communications and Evacuation
- Emergency Electronic Brake Light
- Emergency Vehicle Alert
- Emergency Vehicle Preemption
- Enhanced Maintenance Decision Support System
- Forward Collision Warning
- Freight Drayage Optimization
- Freight Signal Priority
- Freight-Specific Dynamic Travel Planning
- Incident Scene Pre-Arrival Staging Guidance for Emergency Responders
- Incident Scene Work Zone Alerts for Drivers and Workers
- Integrated Multi-Modal Electronic Payment
- Intelligent Traffic Signal System
- Intermittent Bus Lanes
- Intersection Movement Assist
- Low Emissions Zone Management
- Oversize Vehicle Warning
- Pedestrian in Signalized Crosswalk Warning
- Pedestrian Mobility
- Pre-crash Actions
- Queue Warning
- Railroad Crossing Violation Warning
- Red Light Violation Warning
- Reduced Speed Zone Warning / Lane Closure
- Restricted Lane Warnings
- Road Use Charging
- Road Weather Information and Routing Support for Emergency Responders
- Road Weather Information for Freight Carriers
- Road Weather Information for Maintenance and Fleet Management Systems
- Road Weather Motorist Alert and Warning
- Roadside Lighting
- Route ID for the Visually Impaired
- Situational Awareness
- Smart Park and Ride System
- Smart Roadside Initiative
- Speed Harmonization
- Spot Weather Impact Warning
- Stop Sign Gap Assist
- Stop Sign Violation Warning
- Tailgating Advisory
- Transit Connection Protection
- Transit Pedestrian Indication
- Transit Signal Priority
- Transit Stop Request
- Transit Vehicle at Station/Stop Warnings
- Traveler Information- Smart Parking
- Variable Speed Limits for Weather-Responsive Traffic Management
- Vehicle Data for Traffic Operations
- Vehicle Emergency Response
- Vehicle Turning Right in Front of a Transit Vehicle
- Warnings about Hazards in a Work Zone
- Warnings about Upcoming Work Zone
Coordination
Security
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.