Standard

The document is a technical report capturing the study on application architecture for enabling edge applications over 3GPP networks. The aspects of the study include identifying architecture requirements (e.g. discovery of edge services, authentication of the clients), supporting application layer functional model and corresponding solutions to enable the deployment of applications on the edge of 3GPP networks, with no impact to edge-unaware applications on the UE and minimal impact to edge-aware applications on the UE.

Under development

Recommendation ITU-T F.743.12 defines the requirements for edge computing in video surveillance. Edge computing is a distributed computing paradigm aimed at providing various computing services at the edge of the network, and it brings computation and data storage closer to the data source or the location where it is needed, to improve response time and save bandwidth. By using the edge computing technology, the video surveillance system can perform intelligent video analysis and store data near the network premises units. And the edge computing platform provides the management capabilities of the edge resources and functional components to the video surveillance system. It can improve the video processing efficiency and quality of services and reduce the infrastructure cost of the video surveillance system. This Recommendation describes the application scenarios and requirements for edge computing in the video surveillance system.

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.

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.

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.

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.

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.

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.

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.

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.

The OASIS MQTT TC is producing a standard for the Message Queuing Telemetry Transport Protocol compatible with MQTT V3.1, together with requirements for enhancements, documented usage examples, best practices, and guidance for use of MQTT topics with commonly available registry and discovery mechanisms. The standard supports bi-directional messaging to uniformly handle both signals and commands, deterministic message delivery, basic QoS levels, always/sometimes-connected scenarios, loose coupling, and scalability to support large numbers of devices. Candidates for enhancements include message priority and expiry, message payload typing, request/reply, and subscription expiry.
As an M2M/Internet of Things (IoT) connectivity protocol, MQTT is designed to support messaging transport from remote locations/devices involving small code footprints (e.g., 8-bit, 256KB ram controllers), low power, low bandwidth, high-cost connections, high latency, variable availability, and negotiated delivery guarantees. For example, MQTT is being used in sensors communicating to a broker via satellite links, SCADA, over occasional dial-up connections with healthcare providers (medical devices), and in a range of home automation and small device scenarios. MQTT is also ideal for mobile applications because of its small size, minimized data packets, and efficient distribution of information to one or many receivers (subscribers).
For more information on the MQTT TC, see the TC Charter.