driver information Quintuple

Bidirectional?: False

driver information (A-Interconnect): This CVRIA application interconnect encapsulates all of the Layer 2 information flows between the 'EV On-Board Safety Monitoring' application object and the 'Driver' physical object. In this case, there is only a single Layer 2 flow associated with this interconnect, so the Layer 1 application interconnect name and the Layer 2 information flow name are both 'driver information'. This application interconnect is uni-directional since the underlying layer 2 information flows go from 'Emergency Vehicle OBE' to 'Driver'.

Emergency Vehicle OBE (Source Physical Object): The Emergency Vehicle On-Board Equipment (OBE) resides in an emergency vehicle and provides the processing, storage, and communications functions that support public safety-related connected vehicle applications. It represents a range of vehicles including those operated by police, fire, and emergency medical services. In addition, it represents other incident response vehicles including towing and recovery vehicles and freeway service patrols. It includes two-way communications to support coordinated response to emergencies. In CVRIA, a separate 'Vehicle OBE' physical object supports the general V2V and V2I safety applications and other applications that apply to all vehicles, including emergency vehicles. The Emergency Vehicle OBE supplements these general capabilities with capabilities that are specific to emergency vehicles.

EV On-Board Safety Monitoring (Source Application Object): "EV On-Board Safety Monitoring" detects vehicle intrusions in the vicinity of the vehicle and warns emergency personnel of imminent encroachment. Personnel movements in the vicinity of the vehicle are also monitored so that the personnel can be warned of movement beyond a designated safe zone.

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.