Vehicle --> Emergency Vehicle OBE:
vehicle collision information

Definition
Included In
Communication Solutions
Characteristics
Security

Definitions

vehicle collision information (Information Flow): The current status of the vehicle systems following a collision including air bag deployment, number of passengers, seat belt usage, sensor data that indicates crash severity (e.g., Delta V speed profile during the crash, vehicle damage, number of impacts), and vehicle type/make/model.

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:

PS05: Vehicle Emergency Response

This triple is associated with the following Functional Objects:

This Triple is described by the following Functional View Data Flows:

This Triple has the following triple relationships:

None

Communication Solutions

Solutions are sorted in ascending Gap Severity order. The Gap Severity is the parenthetical number at the end of the solution.

Selected Solution

US: SAE Other J2735 - LTE-V2X WSMP

Solution Description

This solution is used within the U.S.. It combines standards associated with US: SAE Other J2735 with those for V-X: LTE-V2X WSMP. The US: SAE Other J2735 standards include upper-layer standards required to implement V2X information flows that do not yet have fully specified functionality and performance charcateristics. The V-X: LTE-V2X WSMP standards include lower-layer standards that support connectionless, near constant, ultra-low latency vehicle-to-any communications using the WAVE Short Messaging Protocol (WSMP) over 3GPP C-V2X in the 5.9GHz spectrum.

ITS Application Entity SAE J2735			Click gap icons for more info.
Mgmt SAE J3161 3GPP 24.301 3GPP 36.331	Facilities SAE J2735	Security Bundle: IEEE 1609.2
	TransNet IEEE 1609.3
	Access Bundle: 3GPP LTE-V2X

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	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	High	Moderate
Basis	This could contain safety-related information that the occupants of the vehicle would prefer not be distributed to anyone except those responsible for their immediate safety. It is PII, whose compromise could have a significant impact on the originator.	Safety related with a time critical component, needs to be correct or EV operators may be misinformed and not react optimally.	While useful, it is impractical to assume this flow could ever rise above 'medium' in achievable availability, given the relevant application focus on incidents.

Security Characteristics	Value
Authenticable	True
Encrypt	True

Vehicle --> Emergency Vehicle OBE:vehicle collision information