Multi-Access Edge Computing --> ITS Roadway Equipment:
signal priority service request

This flow may also be implemented by Connected Vehicle Roadside Equipment --> ITS Roadway Equipment: signal priority service request

Definition
Included In
Communication Solutions
Characteristics
Security

Definitions

signal priority service request (Information Flow): A service request for vehicle priority issued to a traffic signal controller. The request includes the priority level, and may include other parameters such as the desired time and duration of service, and the intended travel path through the intersection. This flow also allows the originator to cancel a previously issued request for priority.

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

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:

None

This Triple has the following triple relationships:

None

Communication Solutions

(None-Data) - Secure Wireless Internet (EU) (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 (EU)

Solution Description

This solution is used within Australia and the E.U.. It combines standards associated with (None-Data) with those for I-M: Secure Wireless Internet (EU). The (None-Data) standards include an unspecified set of standards at the upper layers. The I-M: Secure Wireless Internet (EU) 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 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 (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

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

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	Low
Basis	There is no sensitive or confidential information within this messages. Additionally, it could be inferred by observing either the presence of a priority-requesting vehicle near an intersection, or the effect on the timing of the intersection. This is also transmitted as a result of broadcast data; however, all communications between field infrastructure should be protected from viewing to prevent attackers from analyzing traffic and developing attack methods.	The MEC is transmitting a request to the ITS RE on behalf of a priority-requesting vehicle. It should only be making requests on behalf of an approved vehicle. A corrupted request may lead to a vehicle not receiving a green light after requesting it. In this case, this may lead to traffic delays. If an unapproved vehicle is able to forge these requests, they may cause larger scale traffic delays.	If the ITS RE does not receive any requests, the vehicle may not receive the priority it requested. In the worst case scenario the vehicle would be forced to wait at some lights until they turned green. It would be more useful for a device to support this application, and only have some messages received, than to not support this application at all.

Security Characteristics	Value
Authenticable	True
Encrypt	False

Multi-Access Edge Computing --> ITS Roadway Equipment:signal priority service request