Cloud and Edge Computing

Recommendation ITU-T Y.3109 specifies quality of service (QoS) assurance-related requirements and a framework for virtual reality (VR) delivery using mobile edge computing (MEC) in International Mobile Telecommunications-2020 (IMT-2020). Recommendation ITU-T Y.3109 first provides an introduction to VR delivery using MEC supported by IMT-2020. It then specifies QoS assurance-related function and mechanism requirements and a framework. The QoS planning for VR services, typical VR user cases and guidelines for deployments of VR services are described in appendices.

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.

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.

The purpose of this Recommendation is to guide operator to implement a uniformed security management for multi-vendor environment. This Recommendation analyses main security protection challenges, proposes the collaborative cloud-edge computing security architecture. In addition, this Recommendation describes key technologies and work procedures of the security architecture.

Architecture for edge computing platform supporting a video surveillance system

A huge volume of data has been generated from the various smart things. Lots of smart services have been working based on cloud systems. However, the network bottleneck between terminals and a cloud system has incurred various issues (e.g., data loss, network delay, etc.). An edge computing technology between user equipment and cloud server system is attracted to solve these problems. In addition, applying the intelligent data processing functions by providing AI technologies will provide enhanced networking capabilities for new emerging services and applications.

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 focuses on the MEC Location Service. It describes the related application policy information including authorization and access control, information flows, required information and service aggregation patterns. The document specifies the necessary API with the data model and data format. It is to be noted that the actual data model and data format which is functional for the present API re-uses the definitions in "RESTful Network API for Zonal Presence" and "RESTful Network API for Terminal Location" published by the Open Mobile Alliance.

The present document focuses on the UE Identity functionality. It describes the related application policy information (including authorization, access control and traffic rule pattern format), information flows, required information and service aggregation patterns. The present document specifies the necessary API, data model and data format, considering existing API(s) if applicable.

The document focuses on the Traffic Management multi-access edge service. It describes the related application policy information including authorization and access control, information flows, required information and service aggregation patterns. The document 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.

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.