Link Type: Vehicle On-Board
driver input information (Information Flow): Driver input received from the driver-vehicle interface equipment via the vehicle bus. It includes configuration data, settings and preferences, interactive requests, and control commands for the connected vehicle on-board equipment.
Basic Vehicle (Source 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.
Vehicle OBE (Destination Physical Object): The Vehicle On-Board Equipment (OBE) provides the vehicle-based sensory, processing, storage, and communications functions that support efficient, safe, and convenient travel. The Vehicle OBE includes general capabilities that apply to passenger cars, trucks, and motorcycles. 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 OBE 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 OBE. Both one-way and two-way communications options support a spectrum of information services from basic broadcast to advanced personalized information services. Route guidance capabilities assist in formulation of an optimal route and step by step guidance along the travel route. 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.
This Triple is in the following Service Packages:
- PS04: Mayday Notification
- PS05: Vehicle Emergency Response
- PT10: Intermittent Bus Lanes
- VS01: Autonomous Vehicle Safety Systems
- VS02: V2V Basic Safety
- VS03: Situational Awareness
- VS04: V2V Special Vehicle Alert
- VS05: Curve Speed Warning
- VS07: Road Weather Motorist Alert and Warning
- VS09: Reduced Speed Zone Warning / Lane Closure
- VS10: Restricted Lane Warnings
- VS14: Cooperative Adaptive Cruise Control
- VS15: Infrastructure Enhanced Cooperative Adaptive Cruise Control
- VS16: Automated Vehicle Operations
This Triple is in the following Functional Objects:
- Vehicle Basic Safety Communication
- Vehicle Control Automation
- Vehicle Control Warning
- Vehicle Cooperative Cruise Control
- Vehicle Emergency Notification
- Vehicle Environmental Monitoring
- Vehicle Restricted Lanes Application
- Vehicle Roadside Information Reception
- Vehicle Speed Management Assist
This Triple is described by the following Functional View Data Flows:
Communication SolutionsNo communications solutions identified.
|Information Flow Security|
|Basis||Internal vehicle flow that if reverse engineered could enable third party vehicle control. Largely a competitive question, could be set LOW if manufacturer and operator are not concerned with this type of compromise.||Includes vehicle control commands, which must be timely and accurate to support safe vehicle operation.||Includes vehicle control commands, which must be timely and accurate to support safe vehicle operation.|