Map Update System --> Multi-Access Edge Computing:
intersection geometry

Definitions

intersection geometry (Information Flow): The physical geometry of an intersection covering the location and width of each approaching lane, egress lane, and valid paths between approaches and egresses. This flow also defines the location of stop lines, cross walks, specific traffic law restrictions for the intersection (e.g., turning movement restrictions), and other elements that support calculation of a safe and legal vehicle path through the intersection.

Map Update System (Source Physical Object): The 'Map Update System' represents a provider of map databases used to support ITS services. It supports the provision of the map data that are used directly by vehicles (e.g., roadway and intersection geometry data sets), travelers (e.g., navigable maps used for route guidance and display maps used at traveler information points), system operators (e.g., map data used by Traffic Operators to monitor and manage the road network, and map data used by Fleet Managers to manage a vehicle fleet). It may represent a third-party provider or an internal organization that produces map data for agency use. In the latter case, the 'Map Update System' is typically included as part of the center (e.g., a Traffic Management Center) of the infrastructure owner/operator that manages map data. Products may include simple display maps, map data sets that define detailed road network topology and geometry, or full geographic information system databases that are used to support planning and operations.

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:

• SU04: Map Management

This triple is associated with the following Functional Objects:

• Map Management
• MEC Map Management

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

• None

This Triple has the following triple relationships:

Communication Solutions

• US: SAE Lane-Level Mapping - Secure Wireless Internet (ITS) (4)
• US: SAE Other J2735 - Secure Wireless Internet (ITS) (12)
• EU: Signal Control Messages - Secure Wireless Internet (EU) (16)
• Data for Distribution (TBD) - Apache Kafka over Wireless (44)
• Data for Distribution (TBD) - OMG DDS over Wireless (44)
• Data for Distribution (TBD) - Eclipse Zenoh over Wireless (44)
• Data for Distribution (TBD) - OASIS MQTT over Wireless (47)
• Data for Distribution (TBD) - OASIS AMQP over Wireless (61)

Selected Solution

US: SAE Lane-Level Mapping - Secure Wireless Internet (ITS)

Solution Description

ITS Application Entity SAE J2735 SAE J2945/A			Click gap icons for more info.
Mgmt Bundle: SNMPv3 MIB	Facilities SAE J2945 SAE J2945/A	Security ITS Security Alternatives 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

Security