Cloud and Edge Computing

Decentralized services (e.g., enabled by distributed ledger technologies, DLT) for IoT devices can be deployed in local area networks (e.g., in IoT devices or in local IoT gateways for constrained IoT devices) or in clouds (e.g., in remote IoT gateways or in cloud systems). When deployed in local area networks, the decentralized services will be affected by the local storage capability of peers and their computation capability and communication latency among peers. When deployed in clouds, the decentralized services will be affected by speed and efficiency of data access. With the popularization of the use of edge computing, part or whole of functionalities of DLT-based decentralized services can be deployed in edge nodes. This draft Recommendation introduces decentralized service by using DLT and edge computing technologies, which is an intermediate supporting service between decentralized services in local area networks and that in clouds. Decentralized service by using DLT and edge computing technologies is deployed in edge nodes and can facilitate interaction among peers of decentralized services, no matter where the peers are deployed (e.g., in local areas or in clouds). This draft Recommendation analyses characteristics and general requirements of decentralized service by using DLT and edge computing technologies, and provides its functional framework and relevant common capabilities, functionalities and general procedures.

This Recommendation describes the requirements for a function which enables the cooperation of multiple edge gateways (CMEG) to complete complex tasks. It also describes the required capabilities and requirements of key components. The CEMG function can support the information exchanging among multiple edge gateways and deal with gateway failure cooperatively. It can also specify the central gateway which is responsible for selecting a cooperative gateway for each gateway, which in turn monitors the status of its partner gateway, and manages the cooperative data and devices.

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

The OASIS AMQP TC advances a vendor-neutral and platform-agnostic protocol that offers organizations an easier, more secure approach to passing real-time data streams and business transactions. The goal of AMQP is to ensure information is safely and efficiently transported between applications, among organizations, across distributed cloud computing environments, and within mobile infrastructures. AMQP avoids proprietary technologies, offering the potential to lower the cost of enterprise middleware software integrations through open interoperability. By enabling a commoditized, multi-vendor ecosystem, AMQP seeks to create opportunities for transforming the way business is done in the Cloud and over the Internet.

This draft Recommendation aims to describe the framework of Multi-access Edge Computing for fixed? mobile and satellite convergence (FMSC) in IMT-2020 networks and beyond. This recommendation covers the following issues, but not limited to: o Requirements of Multi-access Edge Computing for supporting fixed, mobile and satellite convergence in IMT-2020 networks; o The architecture of Multi-access Edge Computing for fixed, mobile and satellite convergence; o Information flows of Multi-access Edge Computing for fixed, mobile and satellite convergence.

This draft Recommendation specifies the framework of capability exposure function (CEF) in edge computing for IMT-2020 networks and beyond. The scope of this document includes: - Requirements of capability exposure function in edge computing; - Framework of capability exposure function in edge computing; - Functionalities and reference points of capability exposure function in edge computing; - Procedures of capability exposure function in edge computing.

The draft Recommendation describes the requirements, architecture, functional entities, reference points and information flows of local shunting for multi-access edge computing in IMT-2020 networks.

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.

For development of the IEC architecture, there are couple of software-oriented architectural ways to build flexible protocol architecture achieved by deploying and operating the architecture, for instance, an unified software oriented architecture, which is composing logically modular functions to tightly coupled way as a monolithic architecture and microservice architecture which is loosely composing logically or physically separated own processing functions as microservices. Because IEC has developed on different hardware specifications and various functionalities that each business wants, it is standardized based on microservices and used as a reference standard for implementation. As a result of microservices based IEC architecture, it can be continuously developed and operated by updating microservices. This Recommendation specifies signalling architecture, protocol interfaces, protocol procedures and message format for microservices based intelligent edge computing.

Some of the capabilities offered by the Internet of thing (IoT), e.g., capabilities for computing, storage and analytics, are evolving in closer proximity to IoT data sources. Recommendation ITU-T Y.4208 provides an overview of related challenges faced by the IoT and describes how IoT-supporting edge computing (EC) may address these challenges. From the edge-computing deployment perspective, service requirements for support of EC capabilities in the IoT are identified, as well as related functional requirements. As an example, scenarios of EC deployment in different application domains, EC scenarios for vehicle-to-everything (V2X) and for smart manufacturing are provided in an appendix.

The gateway is an important component of Internet of things (IoT) systems, enabling IoT devices to connect to communication networks. Edge computing technologies can benefit the IoT, providing computation, storage, networking and intelligence in proximity to IoT devices. Compared with the common gateway [ITU-T Y.4101], the edge-computing-enabled gateway in the IoT (EC-enabled IoT gateway) has additional capabilities supporting service layer interworking, and application layer interworking between IoT devices, IoT platforms and IoT application servers. In addition, the EC-enabled IoT gateway supports data transmission capabilities for IoT applications sensitive to time, latency, jitter and packet loss. Based on the common requirements and capabilities of a gateway for IoT applications [ITU-T Y.4101] and IoT requirements for support of edge computing [ITU-T Y.4208], additional capabilities and capability framework of the edge-computing-enabled gateway in the IoT are specified. Examples of applicability of the edge-computing-enabled gateway in the IoT are also given.