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.
IEC 62443-4-2:2019 provides detailed technical control system component requirements (CRs) associated with the seven foundational requirements (FRs) described in IEC TS 62443-1-1 including defining the requirements for control system capability security levels and their components, SL-C (component). As defined in IEC TS 62443-1-1 there are a total of seven foundational requirements (FRs): a) identification and authentication control (IAC), b) use control (UC), c) system integrity (SI), d) data confidentiality (DC), e) restricted data flow (RDF), f) timely response to events (TRE), and g) resource availability (RA). These seven FRs are the foundation for defining control system security capability levels. Defining security capability levels for the control system component is the goal and objective of this document as opposed to SL-T or achieved SLs (SL-A), which are out of scope. Show less
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.
Recommendation X.1643 analyses security threats and challenges on virtualization container in cloud computing environment and specifies a reference framework with security guidelines for virtualization container in cloud.
The scope of this standard is to define an access layer independent protocol for on-board weighing equipment based on the requirements defined in COMMISSION IMPLEMENTING REGULATION (EU) 2019/1213.
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
