IEC 62832-2:2020 specifies detailed requirements for model elements of the Digital Factory framework. It defines the nature of the information provided by the model elements, but not the format of this information.
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 Radio Network Information MEC service. It describes the message flows and the required information. The present document also specifies the RESTful API with the data model.
The document focuses on the functionalities enabled via the Mp1 reference point between MEC applications and MEC platform, which allows these applications to interact with the MEC system. Service related functionality includes registration/deregistration, discovery and event notifications. Other functionality includes application availability, traffic rules, DNS and time of day. It describes the information flows, required information, and specifies the necessary operations, data models and API definitions.
The document provides information flows for lifecycle management of applications running on a MEC host, and describes interfaces over the reference points to support application lifecycle management. It also describes application rules and requirements, application-related events, mobility handling and MEC service availability tracking. The document specifies the necessary data model, data format and operation format when applicable.
The document defines the management of the mobile edge system, mobile edge hosts and mobile edge platforms. This includes platform configuration, performance and fault management, application monitoring, remote service configuration and service control, information gathering regarding the platform features, available services, and available virtualised resources.
The document defines design principles for RESTful MEC service APIs, provides guidelines and templates for the documentation of these, and defines patterns of how MEC service APIs use RESTful principles.
The document defines a framework to be used by ETSI ISG MEC to coordinate and promote multivendor Proofs of Concept (PoC) projects and MEC Deployment Trial (MDT) projects illustrating key aspects of MEC technology. Proofs of Concept are an important tool to demonstrate the viability of a new technology during its early days and or pre-standardization phase. MDTs are seen as the next step of PoC to demonstrate the viability of MEC in a commercial trial/deployment and to provide feedback to the standardization work.
The document provides a framework and reference architecture for Multi-access Edge Computing that describes a MEC system that enables MEC applications to run efficiently and seamlessly in a multi-access network. The document also describes the functional elements and the reference points between them, and a number of MEC services that comprise the solution. It finally presents a number of key concepts related to the multi-access edge architecture.
The document specifies the requirements for Multi-access Edge Computing with the aim of promoting interoperability and deployments. It contains normative and informative parts. The document also contains an annex describing example use cases and their technical benefits, for the purpose of deriving requirements.
Recommendation ITU-T X.1602 analyses the maturity levels of software as a service (SaaS) application and proposes security requirements to provide a consistent and secure service execution environment for SaaS applications. These proposed requirements originate from cloud service providers (CSP) and cloud service partners (CSN) as they need a SaaS application environment to meet their demands on security. The requirements are general and independent of any service or scenario specific model (e.g. web services, or representational state transfer (REST)), assumptions or solutions.
The scope of the present document is to provide an overview of the IoT standards landscape: requirements, architecture, protocols, tests, etc. to provide the roadmaps of the IoT standards, when they are available
