Basic Emergency Vehicle --> Emergency Vehicle OBE:
host emergency vehicle status
Definitions
host emergency vehicle status (Information Flow): Information provided to the ITS on-board equipment from other systems on the Emergency Vehicle Platform.
Basic Emergency Vehicle (Source Physical Object): The 'Basic Emergency Vehicle' represents the interfaces with on-board equipment on a public safety vehicle. It includes a specialized databus that may be subject to different vehicle databus standards and hosts a broad range of components that are specific to emergency vehicles including the lightbar/siren and on-board apparatus that supports law enforcement, firefighting, emergency medical services, and towing/recovery.
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:
- PS06: Incident Scene Pre-Arrival Staging Guidance for Emergency Responders
- PS07: Incident Scene Safety Monitoring
This Triple is described by the following Functional View Functional Objects:
This Triple is described by the following Functional View Data Flows:
- fbev-brake_servo_response
- fbev-crash_sensor_data
- fbev-diagnostics_data
- fbev-driver_safety_status
- fbev-steering_servo_response
- fbev-throttle_servo_response
- fbev-vehicle_attitude_data
- fbev-vehicle_condition
- fbev-vehicle_driver_inputs
- fbev-vehicle_headway
- fbev-vehicle_identity
- fbev-vehicle_lane_position
- fbev-vehicle_motion_data
- fbev-vehicle_occupants
- fbev-vehicle_on_avo_lane
- fbev-vehicle_proximity_data
- fbev-vehicle_safety_status
- fbev-vehicle_security_status
- fbev-vehicle_size
- fbev-vehicle_speed
This Triple has the following triple relationships:
| None |
Communication Solutions
No communications solutions identified.Characteristics
| Characteristic | Value |
|---|---|
| Time Context | Now |
| Spatial Context | Adjacent |
| Acknowledgement | False |
| Cardinality | Unicast |
| Initiator | Source |
| Authenticable | True |
| Encrypt | True |
| Interoperability | Description |
|---|---|
| Local | In cases where an interface is normally encapsulated by a single stakeholder, interoperability is still desirable, but the motive is vendor independence and the efficiencies and choices that an open standards-based interface provides. |
Security
| Information Flow Security | ||||
|---|---|---|---|---|
| Confidentiality | Integrity | Availability | ||
| Rating | Moderate | Moderate | Moderate | |
| Basis | This could contain sensitive or proprietary information. | This is where the Emergency Vehicle OBE acquires GPS information, etc. This information is used elsewhere, leading to this rating. | This information needs to be mostly available to the system for this application to work. | |
| Security Characteristics | Value |
|---|---|
| Authenticable | True |
| Encrypt | True |