Emergency Vehicle OBE --> Multi-Access Edge Computing:
signal preemption request

Definitions

signal preemption request (Information Flow): Direct request for preemption to a traffic signal controller that results in preemption of the current control plan and grants right-of-way to the requesting vehicle. This flow identifies the required phase and timing of the preemption. This flow may also cancel the preemption request (e.g., when the requesting vehicle clears the intersection).

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.

Multi-Access Edge Computing (Destination Physical Object): 'Multi-Access Edge Computing' ((MEC) previously known as mobile edge computing) represents computing devices that operate and are managed like a cloud server, but are deployed at the edge of a network (typically a cellular network, but it could be any network). While not in strict proximity to the transportation network, these systems do benefit from vastly decreased distances to the roadway compared to central systems, and so can provide lower latency than strictly backoffice systems

Included In

This Triple is in the following Service Packages:

• PS03: Emergency Vehicle Preemption

This triple is associated with the following Functional Objects:

• None

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

• connected_ev_signal_preemption_request

This Triple has the following triple relationships:

Communication Solutions

• (None-Data) - Secure Wireless Internet (EU) (43)

Selected Solution

(None-Data) - Secure Wireless Internet (EU)

Solution Description

ITS Application Entity Development needed			Click gap icons for more info.
Mgmt Bundle: SNMPv3 MIB	Facilities Development needed	Security Secure Session Alternatives
	TransNet IP Alternatives Internet Transport Alternatives
	Access Wireless Internet Alternatives (EU)

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

Security