Vehicle --> Emergency Vehicle OBE:
vehicle location and motion
Definitions
vehicle location and motion (Information Flow): Data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size.
Vehicle (Source Physical Object): This 'Vehicle' physical object is used to model core capabilities that are common to more than one type of Vehicle. It provides the vehicle-based general sensory, processing, storage, and communications functions that support efficient, safe, and convenient travel. Many of these capabilities (e.g., see the Vehicle Safety service packages) apply to all vehicle types including personal vehicles, commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle includes the common interfaces and functions that apply to all motorized vehicles. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle. Both one-way and two-way communications options support a spectrum of information services from basic broadcast to advanced personalized information services. Advanced sensors, processors, enhanced driver interfaces, and actuators complement the driver information services so that, in addition to making informed mode and route selections, the driver travels these routes in a safer and more consistent manner. This physical object supports all six levels of driving automation as defined in SAE J3016. Initial collision avoidance functions provide 'vigilant co-pilot' driver warning capabilities. More advanced functions assume limited control of the vehicle to maintain lane position and safe headways. In the most advanced implementations, this Physical Object supports full automation of all aspects of the driving task, aided by communications with other vehicles in the vicinity and in coordination with supporting infrastructure subsystems.
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:
- EV On-Board Safety Monitoring
- Vehicle Basic Safety Communication
- Vehicle Gap Assist
- Vehicle Intersection Warning
- Vehicle Rail Crossing Warning
- Vehicle Restricted Lanes Application
This Triple is described by the following Functional View Data Flows:
- vehicle_emv_current_status_data
- vehicle_emv_location_data
- vehicle_emv_size_data
- vehicle_emv_speed_data
This Triple has the following triple relationships:
| None |
Communication Solutions
-
EU: CA Service - BTP/GeoNetworking/G5 (13)
-
US: SAE LTE-V2X BSM - LTE-V2X WSMP (16)
-
US: SAE Basic Safety Messages - WAVE WSMP (18)
Selected Solution
US: SAE LTE-V2X BSM - LTE-V2X WSMPSolution Description
|
ITS Application Entity
 
SAE J2735  SAE J3161/1 |
Click gap icons for more info.
|
||
|
Mgmt
SAE J3161 3GPP 24.301 3GPP 36.331 |
Facilities
SAE J2735 |
Security
|
|
|
TransNet
IEEE 1609.3 |
|||
|
Access
|
|||
Note that some layers might have alternatives, in which case all of the gap icons associated with every alternative may be shown on the diagram, but the solution severity calculations (and resulting ordering of solutions) includes only the issues associated with the default (i.e., best, least severe) alternative.
Characteristics
| Characteristic | Value |
|---|---|
| Time Context | Now |
| Spatial Context | Adjacent |
| Acknowledgement | False |
| Cardinality | Broadcast |
| Initiator | Source |
| Authenticable | True |
| Encrypt | False |
| 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 | Not Applicable | Moderate | Low | |
| Basis | This data is intentionally transmitted to everyone via a broadcast. Much of its information content can also be determined via other visual indicators | False information here could lead to a false warning, or not receiving a warning when an infraction is about to occur. A few false warnings should not have a bad consequence. When an emergency personnel receives a warning they can look around and verify whether or not a vehicle is actually headed towards them. If a warning is not sent due to incorrect data, there are also many other visual indictors that should stop a driver from causing an infraction. | It would be better to receive any messages than to not have this application available due to availability requirements. However, the higher the availability here, the more useful the application will be and the more emergency personnel can rely on it. | |
| Security Characteristics | Value |
|---|---|
| Authenticable | True |
| Encrypt | False |