Standard

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 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.

This standard defines a protocol and procedures for the transport of timing over bridged and virtual bridged local area networks. It includes the transport of synchronized time, the selection of the timing source (i.e., best master), and the indication of the occurrence and magnitude of timing impairments (i.e., phase and frequency discontinuities). The PDF of this standard is available at the IEEEGET program. The "IEEE Get Program" grants public access to view and download individual PDFs of select standards at no charge. Visit http://standards.ieee.org/about/get/index.html for details.

This document specifies how to map IPv6 over DECT ULE inspired by [RFC4944], [RFC6282], [RFC6775], and [RFC7668].
Digital Enhanced Cordless Telecommunications (DECT) Ultra Low Energy (ULE) is a low-power air interface technology that is proposed by the DECT Forum and is defined and specified by ETSI. The DECT air interface technology has been used worldwide in communication devices for more than 20 years. It has primarily been used to carry voice for cordless telephony but has also been deployed for data-centric services.

ISO/IEC 20005:2013 specifies services and interfaces supporting collaborative information processing (CIP) in intelligent sensor networks which includes:
CIP functionalities and CIP functional model,
common services supporting CIP,
common service interfaces to CIP.

Recommendation ITU-T F.743.10 specifies the general framework, scenarios and requirements for mobile edge computing- (MEC-)enabled content delivery networks (CDNs). Recommendation ITU_T F.743.10 also specifies the requirements for MEC functions on which a CDN edge node relies. The deployment of a CDN edge node with an MEC system is described in the general framework. Several use cases are introduced in Recommendation ITU-T F.743.10 to illustrate the usage of MEC-enabled CDN.

Civilian unmanned aerial vehicle (CUAV) enabled mobile edge computing (MEC) utilizes CUAV as an MEC platform to realize a flexible, efficient and on-demand computing service that can be rapidly deployed and move according to the practical service needs of devices. Recommendation ITU-T F.749.11 describes the framework and specifies requirements for a CUAV-MEC system, including functional, service and security requirements.

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.