Multi-Access Edge Computing --> Emergency Vehicle OBE:
incident scene warning notification

This triple is bi-directional. See also Emergency Vehicle OBE --> Multi-Access Edge Computing: incident scene warning notification
This flow may also be implemented by Connected Vehicle Roadside Equipment --> Emergency Vehicle OBE: incident scene warning notification

Definition
Included In
Communication Solutions
Characteristics
Security

Definitions

incident scene warning notification (Information Flow): Notification of an incident scene emergency or safety issue. This flow identifies that an incident scene emergency or safety issue has occurred so that warnings may be generated by more than one system in the work zone.

Multi-Access Edge Computing (Source 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

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:

PS07: Incident Scene Safety Monitoring

This triple is associated with the following Functional Objects:

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

None

This Triple has the following triple relationships:

None

Communication Solutions

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

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

Selected Solution

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

Solution Description

This solution is used within Canada and the U.S.. It combines standards associated with (None-Data) with those for I-M: Secure Wireless Internet (ITS). The (None-Data) standards include an unspecified set of standards at the upper layers. The I-M: Secure Wireless Internet (ITS) standards include lower-layer standards that support secure communications between two entities, either or both of which may be mobile devices, but they must be stationary or only moving within wireless range of a single wireless access point (e.g., a parked car). Security is based on X.509 or IEEE 1609.2 certificates. A non-mobile (if any) endpoint may connect to the service provider using any Internet connection method.

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.

Characteristics

Characteristic	Value
Time Context	Recent
Spatial Context	Adjacent
Acknowledgement	False
Cardinality	Unicast
Initiator	Source
Authenticable	True
Encrypt	True

Interoperability	Description
Local	In cases where an interface is normally encapsulated by a single stakeholder, interoperability is still desirable, but the motive is vendor independence and the efficiencies and choices that an open standards-based interface provides.

Security

Information Flow Security
	Confidentiality	Integrity	Availability
Rating	Moderate	Moderate	Moderate
Basis	Incident scene information intended for incident responders should be concealed, as it may have PII and certainly will have information about where and when responders need to be/are. A hostile individual could use this information to target the first responders.	Incident information needs to be timely and accurate to ensure effective incident response.	Incident information needs to be timely and accurate to ensure effective incident response.

Security Characteristics	Value
Authenticable	True
Encrypt	True

Multi-Access Edge Computing --> Emergency Vehicle OBE:incident scene warning notification