Standard

IEC 62541-100:2015 is an extension of the overall OPC Unified Architecture standard series and defines the information model associated with Devices. This part of IEC 62541 describes three models which build upon each other: - the (base) Device Model intended to provide a unified view of devices; - the Device Communication Model which adds Network and Connection information elements so that communication topologies can be created; - the Device Integration Host Model finally which adds additional elements and rules required for host systems to manage integration for a complete system. It allows reflecting the topology of the automation system with the devices as well as the connecting communication networks.

IEC 62541-10:2020 RLV contains both the official IEC International Standard and its Redline version. The Redline version is available in English only and provides you with a quick and easy way to compare all the changes between the official IEC Standard and its previous edition. IEC 62541-10:2020 defines the information model associated with Programs in the OPC Unified Architecture. This includes the description of the NodeClasses, standard Properties, Methods and Events and associated behaviour and information for Programs. The complete Address Space model including all NodeClasses and Attributes is specified in IEC 62541-3. The Services such as those used to invoke the Methods used to manage Programs are specified in IEC 62541 4. This third edition cancels and replaces the second edition published in 2015. This edition includes several clarifications and in addition the following significant technical changes with respect to the previous edition: a) Changed ProgramType to ProgramStateMachineType. This is in line with the NodeSet (and thus implementations). In ProgramDiagnosticDataType: changed the definition of lastInputArguments and lastOutputArguments and added two additional fields for the argument values. Also changed StatusResult into StatusCode. Created new version of the type to ProgramDiagnostic2DataType. b) Changed Optional modelling rule to OptionalPlaceHolder for Program control Methods. Following the clarification in IEC 62541-3, this now allows subtypes (or instances) to add arguments.

IPSO Smart Object Guidelines provide a common design pattern, an object model, that can effectively use the IETF CoAP protocol to provide high level interoperability between Smart Object devices and connected software applications on other devices and services.

The IPSO Smart Object Registry registry is intended for developers that are building products based on IPSO Objects, it is not intended to be used at runtime by applications.

SG20 develops international standards to enable the coordinated development of IoT technologies, including machine-to-machine communications and ubiquitous sensor networks. A central part of this study is the standardization of end-to-end architectures for IoT, and mechanisms for the interoperability of IoT applications and datasets employed by various vertically oriented industry sectors.

Recommendation ITU-T H.644.4 specifies a functional architecture for mobile/multi-access edge computing (MEC) enabled content delivery network (MEC-CDN). The functions and functional blocks within this functional architecture and the related reference points are specified in this Recommendation for matching the requirements in Recommendation ITU-T F.743.10. Particularly, this Recommendation also provides the deployment of virtualized content delivery network (CDN) service and the interworking between virtualized CDN functionalities and MEC management system, within a MEC-CDN ecosystem. In addition, a containerized solution of MEC-CDN is given in this Recommendation, followed by the basic information flows.

Recommendation ITU-T Q.5003 describes signalling requirements and architecture for federated multiaccess edge computing (MEC). This Recommendation specifies signalling requirements, signalling architecture with reference points and security considerations for federated MEC.

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.

Architecture for edge computing platform supporting a video surveillance system

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.

This Recommendation specifies the requirements and architecture about ICN-enabled edge network in IMT-2020. 1) From the service and network operation point of view, it discusses detailed requirements of ICN-enabled Edge network in IMT-2020. 2) It provides architecture of ICN-enabled edge network. 3) It describes the key functions and interfaces to satisfy the requirements of ICN-enabled edge network.

IEC 62714-2:2015 specifies normative as well as informative AML role class libraries for the modelling of engineering information for the exchange between engineering tools in the plant automation area by means of AML. Moreover, it presents additional user defined libraries as an example. Its provisions apply to the export/import applications of related tools.