Link Type: Human Interface
Emergency Vehicle OBE --> Driver:
driver information
Definitions
driver information (Information Flow): Regulatory, warning, and guidance information provided to the driver while en route to support safe and efficient vehicle operation.
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.
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.
Included In
This Information Flow is in the following Applications:
This Information Flow is in the following Application Objects:
Communication Diagrams
The destination physical object, "Driver", is a human interface and so there is no associated communications diagram for this triple.Characteristics
Architectural:
| None defined |
Security
This information flow triple is in the following applications with the following security levels.
| Information Flow Security | |||||
|---|---|---|---|---|---|
| Application | Confidentiality | Integrity | Availability | ||
| Basis | Basis | Basis | |||
| Incident Scene Work Zone Alerts for Drivers and Workers | Low | Moderate | Moderate | ||
| This data is sent to all drivers. | There are currently other visual and auditory indicators of an incident. Police will park their car with the lights (and possibly siren) on to indicate that a lane is closed. If incorrect information is sent to the driver, they will still have other cues indicating that an incident has occurred. If the current indicators are fully replaced by this system, then this would be raised to a HIGH. | There are currently other visual and auditory indicators of an incident. Police will park their car with the lights (and possibly siren) on to indicate that a lane is closed. If incorrect information is sent to the driver, they will still have other cues indicating that an incident has occurred. If the current indicators are fully replaced by this system, then this would be raised to a HIGH. | |||