Standard

The document focuses on identifying the additional support that needs to be provided by MEC when MEC applications run on alternative virtualization technologies, such as containers. The document collects and analyses the use cases relating to the deployment of such alternative virtualization technologies, evaluates the gaps from the currently defined MEC functionalities, and identifies new recommendations. As ETSI NFV is also working on alternative virtualization technologies, the MEC work should be aligned with NFV where applicable. The document also recommends the necessary normative work to close any identified gaps.

The document focuses on identifying the MEC functionalities to support network slicing. It first analyses the relevant network slicing concepts as defined by external organizations. Next, it collects relevant use cases based on the identified network slicing concepts when applied in the context of MEC and it evaluates the gaps from the defined MEC functional elements. When necessary, the document identifies new MEC functionalities or interfaces as well as changes to existing MEC functional elements, interfaces and requirements. It will also recommend the necessary normative work to close these gaps if identified.

The document focuses on identifying the MEC features to support V2X applications. It collects and analyses the relevant V2X use cases (including the findings from external organizations), evaluates the gaps from the defined MEC features and functions, and identifies the new requirements including new features and functions. When necessary, this may include identifying new multi-access edge services or interfaces, as well as changes to existing MEC services or interfaces, data models, application rules and requirements. It will also recommend the necessary normative work to close these gaps if identified.

The document focuses on mobility support provided by Mobile Edge Computing. It documents mobility use cases and end to end information flows to support UE and Application mobility for Mobile Edge Computing. When necessary, the document describes new mobile edge services or interfaces, as well as changes to existing mobile edge services or interfaces, data models, application rules and requirements. The document identifies gaps to support mobility that are not covered by existing WIs, documents these gaps and recommends the necessary normative work to close these gaps.

The document describes solutions that allow the deployment of MEC in an NFV environment. For each solution, it describes the motivation for the solution, its architectural impacts and the necessary work to enable it. The document provides recommendations as for where the specification work needs to be done.

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.

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 lists the functionalities and capabilities required by a MEC compliant implementation. In addition, the document specifies a testing framework defining a methodology for development of interoperability and/or conformance test strategies, test systems and the resulting test specifications for MEC standards. In additional, the testable requirements are listed and prioritized.

Based on the testing methodology guidelines and framework specified in ETSI GR MEC-DEC 025, the document specifies part 2 of a multi-part deliverable test specification for the MEC service APIs (currently ETSI GS MEC 012, ETSI GS MEC 013, ETSI GS MEC 014, ETSI GS MEC 015, ETSI GS MEC 016, ETSI GS MEC 021 and ETSI GS MEC 029) and the MEC Application Enablement API (ETSI GS MEC 011). The document includes the Test Suite Structure (TSS) and Test Purposes (TPs) using the standardized notation Test Description Language - Test Objectives extension (TDL_TO).

Based on the testing methodology guidelines and framework specified in ETSI GR MEC-DEC 025, the document specifies part 1 of a multi-part deliverable test specification. Part 1 (the present document) provides the Test requirements and Implementation Conformance Statement (ICS) for: Application Package Management and Application Lifecyle Management as specified in ETSI GS MEC 10-2; MEC Application Enablement as specified in ETSI GS MEC 011; and the MEC service APIs.

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.