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

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

Definitions

signal service request (Information Flow): A call for service or extension for a signal control phase that is issued by the RSE for connected vehicles approaching an intersection and/or pedestrians at a crosswalk. This flow identifies the desired phase and service time.

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:

This Triple has the following triple relationships:

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

US: CTI NTCIP Signal Priority - Wireless SNMPv3/TLS

Solution Description

This solution is used within Canada and the U.S.. It combines standards associated with US: CTI NTCIP Signal Priority with those for I-M: Wireless SNMPv3/TLS. The US: CTI NTCIP Signal Priority standards include upper-layer standards required to implement field-to-field traffic signal control priority communications (e.g., for buses and emergency vehicles). The I-M: Wireless SNMPv3/TLS standards include lower-layer standards that support secure infrastructure-to-mobile communications using simple network management protocol (SNMPv3).

ITS Application Entity

NTCIP 1202
NTCIP 1211
CTI 4001
Click gap icons for more info.

Mgmt

NTCIP 1201
Bundle: SNMPv3 MIB
Facilities

NTCIP 1202
NTCIP 1211
ISO 15784-2
Security
Mind the gapMind the gap

IETF RFC 6353
IETF RFC 9456
TransNet
Access
Mind the gapMind the gapMind the gapMind the gap
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

CharacteristicValue
Time Context Recent
Spatial Context Adjacent
Acknowledgement False
CardinalityUnicast
InitiatorSource
AuthenticableTrue
EncryptFalse


InteroperabilityDescription
LocalIn 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 info is not confidential and could be exposed with little harm to participants; however, all communications between field infrastructure should be protected from viewing to prevent attackers from analyzing traffic and developing attack methods. requests should be accurate and not tampered with, otherwise incorrect or malicious requests could be granted which could lead to delays requests should be timely and available immediately but availability cannot be guaranteed over a wireless medium; also worst case scenario is the vehicle or pedestrian has to wait for the appropriate signal


Security CharacteristicsValue
AuthenticableTrue
Encrypt False