Edge Computing

The document focuses on a MEC Vehicular-to-Everything (V2X) Information Service (VIS), in order to facilitate V2X interoperability in a multi-vendor, multi-network and multi-access environment. It describes the V2X-related information flows, required information and operations. The document also specifies the necessary API with the data model and data format.

The document describes a MEC service on Fixed Access Information for Fibre (e.g. G-PON, XG-PON, NG-PON2, XGS-PON), Cable (DOCSIS 3.1), xDSL, and Point-to-Point Fibre Ethernet access networks. It describes the information flows, required information, and as applicable, specifies the necessary operations, data model and data format. The present document also specifies the RESTful API.

The document focuses on the WLAN Access Information MEC service. It describes the message flows and the required information. The document also specifies the RESTful API with the data model.

The document provides a specification for end-to-end MEC application mobility support in a multi-access edge system. The document describes information flows, required information and operations. The document also specifies the necessary API with the data model and data format.

The document contains the API definition for the lifecycle management of user applications over the Mx2 reference point between the device application and the User Application LifeCycle Management Proxy (UALCMP) in the MEC system. The document covers the following lifecycle management operations: user application look-up, instantiation and termination. In addition, a mechanism is specified for the exchange of lifecycle management related information between the MEC system and the device application. The intended key audience of the present document are the application developers for the MEC system, since this API provides them with a method to manage their applications.

The document focuses on the Traffic Management multi-access edge service. It describes the related application policy information including authorization and access control, information flows, required information and service aggregation patterns. The document specifies the necessary API with the data model and data format.

The present document focuses on the UE Identity functionality. It describes the related application policy information (including authorization, access control and traffic rule pattern format), information flows, required information and service aggregation patterns. The present document specifies the necessary API, data model and data format, considering existing API(s) if applicable.

The document introduces a number of service scenarios that would benefit from the introduction of Mobile-Edge Computing (MEC) technology. The focus of the document is to introduce or provide a non-exhaustive set of service scenarios. It is not the intent nor does the present document provide any requirements.

The document describes various metrics which can potentially be improved through deploying a service on a MEC platform. Example use cases are used to demonstrate where improvements to a number of key performance indicators can be identified in order to highlight the benefits of deploying MEC for various services and applications. Furthermore, the document describes best practices for measuring such performance metrics and these techniques are further exemplified with use cases. Metrics described in the present document can be taken from service requirements defined by various organizations (e.g. 5G service requirements defined by Next Generation Mobile Networks (NGMN) or 3rd Generation Partnership Project (3GPP)). An informative annex is used to document such desired and/or achieved ranges of performance which could be referenced from the main body of the present document.

This document specifies functional requirements and architecture about the following items for resource interoperability among heterogeneous IoT platforms (e.g., oneM2M, GS1 Oliot, IBM Watson IoT, OCF IoTivity, and FIWARE, etc.) through the conversion of resource identifiers (IDs) and paths (e.g., uniform resource identifier (URI)): Requirements for interoperability of resource IDs in the heterogeneous IoT platforms; Functional architecture for converting IDs and paths of resources on heterogeneous platforms; and, Functional architecture for mapping and managing resource IDs among heterogeneous platforms.

For development of the IEC architecture, there are couple of software-oriented architectural ways to build flexible protocol architecture achieved by deploying and operating the architecture, for instance, an unified software oriented architecture, which is composing logically modular functions to tightly coupled way as a monolithic architecture and microservice architecture which is loosely composing logically or physically separated own processing functions as microservices. Because IEC has developed on different hardware specifications and various functionalities that each business wants, it is standardized based on microservices and used as a reference standard for implementation. As a result of microservices based IEC architecture, it can be continuously developed and operated by updating microservices. This Recommendation specifies signalling architecture, protocol interfaces, protocol procedures and message format for microservices based intelligent edge computing.

This Recommendation describes the requirements for a function which enables the cooperation of multiple edge gateways (CMEG) to complete complex tasks. It also describes the required capabilities and requirements of key components. The CEMG function can support the information exchanging among multiple edge gateways and deal with gateway failure cooperatively. It can also specify the central gateway which is responsible for selecting a cooperative gateway for each gateway, which in turn monitors the status of its partner gateway, and manages the cooperative data and devices.