Map Update System --> Multi-Access Edge Computing:
map updates

This flow may also be implemented by Map Update System --> Connected Vehicle Roadside Equipment: map updates

Definitions

map updates (Information Flow): Map update that could include a new underlying static or real-time map or map layer(s) update. Map layers can include highways, major roads, streets, public transport routes, topography, points of interest, and regulatory information including turn restrictions and speed limits.

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:

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

  • No communications solutions identified.
  • Characteristics

    CharacteristicValue
    Time Context Recent
    Spatial Context Regional
    Acknowledgement False
    CardinalityUnicast
    InitiatorDestination
    AuthenticableTrue
    EncryptFalse


    Security

    Information Flow Security
      Confidentiality Integrity Availability
    Security levels have not been defined yet.


    Security CharacteristicsValue
    AuthenticableTrue
    Encrypt False