The scope of this document is limited to the Enabler Release Definition of Gateway Management Object (GwMO v1.1) according to OMA Release process and the Enabler Release specification baseline listed in section 5.
The scope of the Gateway Management Object architecture document is to define the architecture for the DM Gateway Management Object v1.1 enabler. This document fulfills the functional capabilities and information flows needed to support this enabler as described in the Gateway Management Object requirements document [GwMO-RD].
In recent years, there a+E139:I139re more extra-large data centres worldwide. Although these kind of data centres are in strong capability of data processing, it is a little bit difficult to meet the need of data centre application from users. The Edge data centre is established to perfectly solve this problem and let users get better experience of data access. With the huge quantity application and establishment of Edge data centres, the specific requirement of data centre infrastructure, especially in Edge data centre, will be stricter in the future. This Recommendation proposes to establish clear requirements on infrastructure including ICT system, powering system, cooling system, monitoring system etc. to get green, safe, reliable, smart, energy-saving Edge data centre.
Cloud gaming requires high real-time performance, so it needs special hardwares to match the needs of real-time game rendering. This recommendation will describe the detailed infrastructure requirements of cloud gaming and provide reference for infrastructure selection of mobile edge computing in different scenarios. Among the factors that restrict the development of cloud gaming, the long end-to-end delay is the most important one. Mobile Edge computing is an effective way to reduce the end-to-end delay. This recommendation will describe the architecture and interaction process of cloud gaming system optimized for edge computing.
This document describes the problem of distributed data discovery in edge computing, and in particular for computing-in-the-network (COIN), which may require both the marshalling of data at the outset of a computation and the persistence of the resultant data after the computation.
This document discusses some use cases to demonstrate how real
applications can benefit from COIN and to showcase essential requirements that have to be fulfilled by COIN applications.
A use case describing transmission of an application on the Internet that has several unique characteristics of Augmented Reality (AR) applications is presented for the consideration of the Media
Operations (MOPS) Working Group
How Uniform Resource Name (URN) values are allocated in IEEE 802(R) standards is described in this amendment to IEEE Std 802(R)-2014.
A unified and cloud-based edge computing platform allows operators to flexibly deploy network functions and support infrastructure for fixed-mobile network convergence, to provide a unified multi-access edge computing capability for all network access technologies in IMT-2020 networks. This draft Recommendation aims to describe the requirements, architecture and functions of unified multi-access edge computing for supporting fixed mobile convergence (FMC) network.
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.