Emergency Vehicle OBE --> ITS Roadway Equipment:
local signal preemption request
Definitions
local signal preemption request (Information Flow): Direct control signal or message to a signalized intersection that results in preemption of the current control plan and grants right-of-way to the requesting vehicle.
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. 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.
ITS Roadway Equipment (Destination Physical Object): 'ITS Roadway Equipment' represents the ITS equipment that is distributed on and along the roadway that monitors and controls traffic and monitors and manages the roadway. This physical object includes traffic detectors, environmental sensors, traffic signals, highway advisory radios, dynamic message signs, CCTV cameras and video image processing systems, grade crossing warning systems, and ramp metering systems. Lane management systems and barrier systems that control access to transportation infrastructure such as roadways, bridges and tunnels are also included. This object also provides environmental monitoring including sensors that measure road conditions, surface weather, and vehicle emissions. Work zone systems including work zone surveillance, traffic control, driver warning, and work crew safety systems are also included.
Included In
This Triple is in the following Service Packages:
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
- EU: Signal Control Messages - G5 TCP (9)
- Proprietary Data - Proprietary Comm (16)
- US: SAE Signal Preemption - LTE-V2X TCP (18)
- US: SAE Signal Preemption - WAVE TCP (20)
Selected Solution
Solution Description
ITS Application Entity
SAE J2735 CEN ISO 19091 ETSI 102 894-2 |
Click gap icons for more info.
|
||
Mgmt
|
Facilities
ETSI 103 301 |
Security
|
|
TransNet
|
|||
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 | Recent |
Spatial Context | Adjacent |
Acknowledgement | False |
Cardinality | Unicast |
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 | High | Moderate | |
Basis | It does not matter if someone is able to eavesdrop on this request. There will be many other more obvious indicators that the request was made, such as sirens and flashing lights on the emergency vehicle. | The system must be able to trust these requests. Emergency Vehicles should be able to send these requests and know that they are being operated on by the receiving system. Additionally, if an unauthorized vehicle is able to send these requests it could bring traffic to a standstill by disrupting signal coordination citywide. | The alternative to this request is existing mechanisms – such as using the sirens to stop traffic. The difference between the emergency signal preemption application and existing practice is not significant enough to justify a HIGH availability requirement. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | False |