Driver --> Vehicle:
driver input
Definitions
driver input (Information Flow): Driver input to the vehicle on-board equipment including configuration data, settings and preferences, interactive requests, and control commands.
Driver (Source Physical Object): The 'Driver' represents the person that operates a vehicle on the roadway. Included are operators of private, transit, commercial, and emergency vehicles where the interactions are not particular to the type of vehicle (e.g., interactions supporting vehicle safety applications). The Driver originates driver requests and receives driver information that reflects the interactions which might be useful to all drivers, regardless of vehicle classification. Information and interactions which are unique to drivers of a specific vehicle type (e.g., fleet interactions with transit, commercial, or emergency vehicle drivers) are covered by separate objects.
Vehicle (Destination 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.
Included In
This Triple is in the following Service Packages:
- PM06: Loading Zone Management
- PS04: Mayday Notification
- PS05: Vehicle Emergency Response
- PS09: Transportation Infrastructure Protection
- PT10: Intermittent Bus Lanes
- PT12: Transit Vehicle at Station/Stop Warnings
- ST02: Eco-Traffic Signal Timing
- ST03: Eco-Traffic Metering
- ST07: Eco-Lanes Management
- ST08: Eco-Approach and Departure at Signalized Intersections
- ST09: Connected Eco-Driving
- ST10: Low Emissions Zone Management
- SU12: Vehicle Maintenance
- SU15: Vulnerable Road User Device Transition Support
- TI01: Broadcast Traveler Information
- TI07: In-Vehicle Signage
- TM04: Connected Vehicle Traffic Signal System
- TM16: Reversible Lane Management
- TM17: Speed Warning and Enforcement
- TM21: Speed Harmonization
- TM24: Tunnel Management
- TM25: Wrong Way Vehicle Detection and Warning
- 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
- VS17: Management of Electronic Traffic Regulations (METR)
- WX03: Spot Weather Impact Warning
This triple is associated with the following Functional Objects:
- Vehicle Basic Safety Communication
- Vehicle Control Automation
- Vehicle Control Warning
- Vehicle Cooperative Cruise Control
- Vehicle Device Coordination
- Vehicle Eco-Driving Assist
- Vehicle Emergency Notification
- Vehicle Gap Assist
- Vehicle Loading Zone Access
- Vehicle METR Interpretation
- Vehicle METR Management
- Vehicle Platoon Operations
- Vehicle Queue Warning
- Vehicle Restricted Lanes Application
- Vehicle Secure Area Access System
- Vehicle Speed Management Assist
- Vehicle System Executive
- Vehicle System Monitoring and Diagnostics
- Vehicle Traveler Information Reception
This Triple is described by the following Functional View Data Flows:
- fd-activate_vehicle_control
- fd-vehicle_display_configuration_override
- fd-vehicle_display_configuration_setting
- fd-vulnerability_update
This Triple has the following triple relationships:
| Relationship | Source | Destination | Flow |
|---|---|---|---|
| Interactive | Vehicle | Driver | driver updates |
Communication Solutions
No communications solutions identified.Characteristics
| None defined |
| 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 | Moderate | High | High | |
| Basis | Data included in this flow may include origin and destination information, which should be protected from other's viewing as it may compromise the driver's privacy. | Commands from from the driver to the vehicle must be correct or the vehicle may behave in an unpredictable and possibly unsafe manner | Commands must always be able to be given or the driver has no control. | |