Emergency Vehicle OBE --> Multi-Access Edge Computing:
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.

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

This Triple is an instantiation of the more general triple:

• Vehicle => Multi-Access Edge Computing: vehicle location and motion

Included In

This Triple is in the following Service Packages:

• PS03: Emergency Vehicle Preemption

This triple is associated with the following Functional Objects:

• MEC Incident Scene Safety
• MEC Intersection Management
• MEC Intersection Safety
• MEC Rail Crossing Warning
• MEC Restricted Lanes Application
• MEC Traveler Information Communications
• MEC Work Zone Safety
• Vehicle Basic Safety Communication
• Vehicle Gap Assist
• Vehicle Rail Crossing Warning
• Vehicle Restricted Lanes Application

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

• None

This Triple has the following triple relationships:

This Triple is an instantiation of the more general triple:

• Vehicle => Multi-Access Edge Computing: vehicle location and motion

Communication Solutions

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

Selected Solution

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

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 (NA)

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.

This Triple is an instantiation of the more general triple:

• Vehicle => Multi-Access Edge Computing: vehicle location and motion

Characteristics

This Triple is an instantiation of the more general triple:

• Vehicle => Multi-Access Edge Computing: vehicle location and motion

Security