Standard

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 specifies the requirements for Multi-access Edge Computing with the aim of promoting interoperability and deployments. It contains normative and informative parts. The document also contains an annex describing example use cases and their technical benefits, for the purpose of deriving requirements.

Based on the testing methodology guidelines and framework specified in ETSI GR MEC-DEC 025, the document specifies part 3 of a multi-part deliverable on conformance test specification. Part 3 provides the Abstract Test Suites (ATS) in TTCN-3 and the Robot Framework for the MEC Application Enablement API specified in ETSI GS MEC 011 and the MEC service APIs.

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.

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.

IEC 62832-2:2020 specifies detailed requirements for model elements of the Digital Factory framework. It defines the nature of the information provided by the model elements, but not the format of this information.

IEC TR 62443-2-3:2015(E) describes requirements for asset owners and industrial automation and control system (IACS) product suppliers that have established and are now maintaining an IACS patch management program. This Technical Report recommends a defined format for the distribution of information about security patches from asset owners to IACS product suppliers, a definition of some of the activities associated with the development of the patch information by IACS product suppliers and deployment and installation of the patches by asset owners. The exchange format and activities are defined for use in security related patches; however, it may also be applicable for non-security related patches or updates.