ETSI TS 103 327 V1.1.1 (2019-04): Smart Body Area Networks (SmartBAN); Service and application standardized enablers and interfaces, APIs and infrastructure for interoperability management
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 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 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 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 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.
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.
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 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.
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 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.