Link Type: Vehicle On-Board
Vehicle Databus --> Vehicle OBE:
host vehicle status
Definitions
host vehicle status (Information Flow): Information provided to the connected vehicle on-board equipment from other systems on the vehicle platform. This includes data from on-board sensors, the current status of the powertrain, steering, and braking systems, and status of safety and convenience systems. In implementations where GPS is not integrated into the Vehicle On-Board Equipment, the host vehicle is also the source for data describing the vehicle's location in three dimensions (latitude, longitude, elevation) and accurate time that can be used for time synchronization across the Connected Vehicle environment.
Vehicle Databus (Source 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.
Vehicle OBE (Destination 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.
Included In
This Information Flow is in the following Applications:
- Advanced Automatic Crash Notification Relay
- Blind Spot Warning + Lane Change Warning
- Connected Eco-Driving
- Control Loss Warning
- Cooperative Adaptive Cruise Control
- Curve Speed Warning
- Do Not Pass Warning
- Dynamic Eco-Routing
- 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
- Electric Charging Stations Management
- Emergency Electronic Brake Light
- Emergency Vehicle Alert
- Forward Collision Warning
- Incident Scene Work Zone Alerts for Drivers and Workers
- Intelligent Traffic Signal System
- Intermittent Bus Lanes
- Intersection Movement Assist
- Location and Time
- Low Emissions Zone Management
- Motorcycle Approaching Indication
- 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 Weather Motorist Alert and Warning
- Roadside Lighting
- Situational Awareness
- Slow Vehicle Warning
- Speed Harmonization
- Spot Weather Impact Warning
- Stationary Vehicle Warning
- Stop Sign Gap Assist
- Stop Sign Violation Warning
- Tailgating Advisory
- Transit Vehicle at Station/Stop Warnings
- Variable Speed Limits for Weather-Responsive Traffic Management
- Vehicle Data for Traffic Operations
- Vehicle Emergency Response
- Warnings about Hazards in a Work Zone
This Information Flow is in the following Application Objects:
- Vehicle Basic Safety
- Vehicle Electric Charging Assist
- Vehicle Emergency Notification I/F
- Vehicle Emissions Monitoring
- Vehicle Environmental Monitoring
- Vehicle Gap Assist
- Vehicle Intersection Warning
- Vehicle Mayday Notification
- Vehicle Rail Crossing Warning
- Vehicle Restricted Lanes Application
- Vehicle Roadside Information Reception
- Vehicle Speed Management Assist
- Vehicle Support Services
- Vehicle Trip Planning and Route Guidance
Communication Diagrams
The communication diagram(s) can be viewed in SVG or PNG format and the current format is SVG. Switch to PNG format.
Characteristics
Architectural:
None defined |
Security
This information flow triple is in the following applications with the following security levels.
Information Flow Security | |||||
---|---|---|---|---|---|
Application | Confidentiality | Integrity | Availability | ||
Basis | Basis | Basis | |||
Incident Scene Work Zone Alerts for Drivers and Workers | Moderate | Moderate | Moderate | ||
This can include some sensitive data. However, other data, such as vehicle location and motion will then be broadcast. There also may be proprietary information included in this. | This is used later on to determine whether a vehicle is infringing in a work zone. This needs to be correct in order for the application to work correctly. | This information would need to be available immediately for the application to work. Late or missed messages would cause an infringement to go unreported. | |||
Pedestrian in Signalized Crosswalk Warning | Low | Moderate | Moderate | ||
In general this is information that will be broadcast but the information flow may include OEM-proprietary or sensitive information. | At least some data from this information flow is broadcast to other systems, and is then is used in the decision making process. All of the other stages that utilize this data flow have a MEDIUM integrity requirement, which leads to this one having a MEDIUM as well. | The Vehicle OBE relies on this data being available from the Vehicle Platform. If this data is not available, then the other systems cannot function. All of the other systems have a MEDIUM requirement, leading to a MEDIUM here. |