Vehicle --> Basic Vehicle:
driver update information
Definitions
driver update information (Information Flow): Information provided to the driver-vehicle interface to inform the driver about current conditions, potential hazards, and the current status of vehicle on-board equipment. The flow includes the information to be presented to the driver and associated metadata that supports processing, prioritization, and presentation by the DVI as visual displays, audible information and warnings, and/or haptic feedback.
Vehicle (Source Physical Object): This 'Vehicle' physical object is used to model core capabilities that are common to more than one type of Vehicle. It provides the vehicle-based general sensory, processing, storage, and communications functions that support efficient, safe, and convenient travel. Many of these capabilities (e.g., see the Vehicle Safety service packages) apply to all vehicle types including personal vehicles, commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle includes the common interfaces and functions that apply to all motorized vehicles. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle. Both one-way and two-way communications options support a spectrum of information services from basic broadcast to advanced personalized information services. Advanced sensors, processors, enhanced driver interfaces, and actuators complement the driver information services so that, in addition to making informed mode and route selections, the driver travels these routes in a safer and more consistent manner. This physical object supports all six levels of driving automation as defined in SAE J3016. Initial collision avoidance functions provide 'vigilant co-pilot' driver warning capabilities. More advanced functions assume limited control of the vehicle to maintain lane position and safe headways. In the most advanced implementations, this Physical Object supports full automation of all aspects of the driving task, aided by communications with other vehicles in the vicinity and in coordination with supporting infrastructure subsystems.
Basic Vehicle (Destination Physical Object): 'Basic Vehicle' represents a complete operating vehicle. It includes the vehicle platform that interfaces with and hosts ITS electronics and all of the driver convenience and entertainment systems, and other non-ITS electronics on-board the vehicle. Interfaces represent both internal on-board interfaces between ITS equipment and other vehicle systems and other passive and active external interfaces or views of the vehicle that support vehicle/traffic monitoring and management. External interfaces may also represent equipment that is carried into the vehicle (e.g., a smartphone that is brought into the vehicle). Internal interfaces are often implemented through a vehicle databus, which is also included in this object. Note that 'Vehicle' represents the general functions and interfaces that are associated with personal automobiles as well as commercial vehicles, emergency vehicles, transit vehicles, and other specialized vehicles.
Included In
This Triple is in the following Service Packages:
- MC07: Work Zone Safety Monitoring
- PS04: Mayday Notification
- PS05: Vehicle Emergency Response
- PS07: Incident Scene Safety Monitoring
- PT10: Intermittent Bus Lanes
- PT12: Transit Vehicle at Station/Stop Warnings
- VS01: Autonomous Vehicle Safety Systems
- VS02: V2V Basic Safety
- VS03: Situational Awareness
- VS04: V2V Special Vehicle Alert
- VS05: Curve Speed Warning
- VS06: Stop Sign Gap Assist
- VS07: Road Weather Motorist Alert and Warning
- VS08: Queue Warning
- VS09: Reduced Speed Zone Warning / Lane Closure
- VS10: Restricted Lane Warnings
- VS11: Oversize Vehicle Warning
- 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 triple is associated with the following Functional Objects:
- Vehicle Basic Safety Communication
- Vehicle Control Automation
- Vehicle Cooperative Cruise Control
- Vehicle Emergency Notification
- Vehicle Environmental Monitoring
- Vehicle Gap Assist
- Vehicle Intersection Warning
- Vehicle Restricted Lanes Application
- Vehicle Speed Management Assist
- Vehicle Traveler Information Reception
This Triple is described by the following Functional View Data Flows:
- tbv-vehicle_charging_status_details_for_driver
- tbv-vehicle_crash_notification_status_for_driver
- tbv-vehicle_eco_drive_status_for_driver
- tbv-vehicle_status_details_for_driver
This Triple has the following triple relationships:
| Relationship | Source | Destination | Flow |
|---|---|---|---|
| Depends On | Basic Vehicle | Vehicle | host vehicle status |
| Depends On | Connected Vehicle Roadside Equipment | Vehicle | lane closure information |
| Depends On | Connected Vehicle Roadside Equipment | Vehicle | queue warning information |
| Depends On | Connected Vehicle Roadside Equipment | Vehicle | reduced speed notification |
| Depends On | Connected Vehicle Roadside Equipment | Vehicle | vehicle signage data |
| Depends On | Transportation Information Center | Vehicle | lane closure information |
| Depends On | Transportation Information Center | Vehicle | queue warning information |
| Depends On | Transportation Information Center | Vehicle | reduced speed warning info |
Communication Solutions
No communications solutions identified.Characteristics
| Characteristic | Value |
|---|---|
| Time Context | Now |
| Spatial Context | Adjacent |
| Acknowledgement | False |
| Cardinality | Unicast |
| Initiator | Source |
| Authenticable | True |
| Encrypt | False |
| Interoperability | Description |
|---|---|
| Not Applicable | Interoperability ratings don't apply per se to some types of interfaces like human interfaces. These interfaces may still benefit from associated standards (e.g., ergonomic and human factors standards for human interfaces), but the primary motive for these standards is not interoperability. |
Security
| Information Flow Security | ||||
|---|---|---|---|---|
| Confidentiality | Integrity | Availability | ||
| Rating | Low | Moderate | Moderate | |
| Basis | This information is all presented to the vehicle operator. Encrypting this information may make it harder to reverse engineer vehicle systems, and may defeat criminal tracking tools when the vehicle has already been compromised. Unless those scenarios are of concern to the operator or manufacturer, this can safely be set LOW. | Any information presented to the operator of a vehicle should be both accurate and timely. By definition this includes safety information, but given that the driver has other means of learning about most threats, it seems difficult to justify HIGH. If HIGH is warranted, it should apply to both availability and integrity. | Any information presented to the operator of a vehicle should be both accurate and timely. By definition this includes safety information, but given that the driver has other means of learning about most threats, it seems difficult to justify HIGH. If HIGH is warranted, it should apply to both availability and integrity. | |
| Security Characteristics | Value |
|---|---|
| Authenticable | True |
| Encrypt | False |