Other EV OBEs --> Emergency Vehicle OBE:
incident scene warning notification
This triple is bi-directional. See also
Emergency Vehicle OBE --> Other EV OBEs: incident scene warning notification
Definitions
incident scene warning notification (Information Flow): Notification of an incident scene emergency or safety issue. This flow identifies that an incident scene emergency or safety issue has occurred so that warnings may be generated by more than one system in the work zone.
Other EV OBEs (Source Physical Object): This represents on-board equipment on other emergency (e.g., law enforcement, fire, EMS, towing and recovery) vehicles. It provides a source and destination for ITS information transfers between emergency vehicles. These information transfers allow information to be shared between emergency vehicles arriving, or involved at, an incident. Vehicle to vehicle communications at incident locations facilitates incident coordination and personal safety.
Emergency Vehicle OBE (Destination 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. A separate 'Vehicle OBE' physical object supports the general vehicle safety and driver information capabilities that apply to all vehicles, including emergency vehicles. The Emergency Vehicle OBE supplements these general capabilities with capabilities that are specific to emergency vehicles.
Included In
This Triple is in the following Service Packages:
This Triple is described by the following Functional View Functional Objects:
This Triple is described by the following Functional View Data Flows:
- foev-incident_scene_intrusion_alert_on_board
- foev-incident_scene_intrusion_detection_on_board
- foev-incident_scene_intrusion_warning_to_personnel
- foev-personnel_movements
This Triple has the following triple relationships:
| None |
Communication Solutions
No communications solutions identified.Characteristics
| Characteristic | Value |
|---|---|
| Time Context | Recent |
| Spatial Context | Adjacent |
| Acknowledgement | False |
| Cardinality | Broadcast |
| Initiator | Source |
| Authenticable | True |
| Encrypt | True |
| Interoperability | Description |
|---|---|
| National | This triple should be implemented consistently within the geopolitical region through which movement is essentially free (e.g., the United States, the European Union). |
Security
| Information Flow Security | ||||
|---|---|---|---|---|
| Confidentiality | Integrity | Availability | ||
| Rating | Moderate | Moderate | Moderate | |
| Basis | This information could be of interest to a malicious individual who is attempting to determine the best way to accomplish a crime. As such it would be best to not make it easily accessible. May be LOW in some cases. | If this is compromised, it could send unnecessary maintenance workers, or cause the appearance of non-existant incidents or even hide incident activities. Given that human safety could be involved, this might be HIGH. | Incident status information should be presented in timely fashion as large scale mobility and safety issues are related. There are other mechanisms for reporting this information however, thus MODERATE. | |
| Security Characteristics | Value |
|---|---|
| Authenticable | True |
| Encrypt | True |