Emergency Vehicle OBE --> Connected Vehicle Roadside 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.

Connected Vehicle Roadside Equipment (Destination Physical Object): 'Connected Vehicle Roadside Equipment' (CV RSE) represents the Connected Vehicle roadside devices that are used to send messages to, and receive messages from, nearby vehicles using Dedicated Short Range Communications (DSRC) or other alternative wireless communications technologies. Communications with adjacent field equipment and back office centers that monitor and control the RSE are also supported. This device operates from a fixed position and may be permanently deployed or a portable device that is located temporarily in the vicinity of a traffic incident, road construction, or a special event. It includes a processor, data storage, and communications capabilities that support secure communications with passing vehicles, other field equipment, and centers.

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:

RelationshipSourceDestinationFlow
Interactive Connected Vehicle Roadside Equipment Emergency Vehicle OBE signal priority status

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

EU: Signal Control Messages - G5 TCP

Solution Description

This solution is used within Australia and the E.U.. It combines standards associated with EU: Signal Control Messages with those for V-X: G5 TCP. The EU: Signal Control Messages standards include upper-layer standards required to implement signal control information flows. The V-X: G5 TCP standards include lower-layer standards that support broadcast, near constant, low latency vehicle-to-vehicle and vehicle-to-infrastructure communications using the ETSI GeoNetworking Bundle with TCP/IPv6 over the 5.9GHz spectrum.

ITS Application Entity
Mind the gapMind the gap

SAE J2735
CEN ISO 19091
ETSI 102 894-2
Click gap icons for more info.
Mgmt
Facilities

ETSI 103 301
Security
Mind the gapMind the gap
TransNet
Mind the gap
Access
TransNet TransNet

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Access Access

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

ITS Application ITS Application

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Mgmt Mgmt

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Facility Facility

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Security Security

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

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