driver interaction Quintuple
Bidirectional?: True
driver interaction (A-Interconnect): This CVRIA application interconnect encapsulates all of the Layer 2 information flows between the 'Vehicle Speed Management Assist' application object and the 'Driver' physical object. This application interconnect is bi-directional since the underlying layer 2 information flows carry data in both directions.
Vehicle OBE (Source 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.
Vehicle Speed Management Assist (Source Application Object): "Vehicle Speed Management Assist" assists the driver in operating the vehicle within the current speed limit. It monitors current vehicle speed and communicates with the infrastructure to receive current speed limits and associated road configuration change notifications. Driver warnings are issued when unsafe or excessive speeds are detected based on the provided speed limits and current conditions.
Driver (Destination 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.