IT in general

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-11:2020 which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.</br></br> IEC 62541-11:2020 is part of the OPC Unified Architecture standard series and defines the information model associated with Historical Access (HA). It particularly includes additional and complementary descriptions of the NodeClasses and Attributes needed for Historical Access, additional standard Properties, and other information and behaviour. The complete AddressSpace Model including all NodeClasses and Attributes is specified in IEC 62541-3. The predefined Information Model is defined in IEC 62541-5. The Services to detect and access historical data and events, and description of the ExtensibleParameter types are specified in IEC 62541-4. This document includes functionality to compute and return Aggregates like minimum, maximum, average etc. The Information Model and the concrete working of Aggregates are defined in IEC 62541-13. This third edition cancels and replaces the second edition published in 2015. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: a) a new method for determining the first historical point has been added; b) added clarifications on how to add, insert, modify, and delete annotations.

IEC 62541-13:2020 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-13:2020 is part of the overall OPC Unified Architecture specification series and defines the information model associated with Aggregates. This second edition cancels and replaces the first edition of IEC 62541-13, published in 2015. No technical changes but numerous clarifications. Also some corrections to the examples.

IEC 62541-14:2020 defines the OPC Unified Architecture (OPC UA) PubSub communication model. It defines an OPC UA publish subscribe pattern which complements the client server pattern defined by the Services in IEC 62541-4. IEC TR 62541-1 gives an overview of the two models and their distinct uses. PubSub allows the distribution of data and events from an OPC UA information source to interested observers inside a device network as well as in IT and analytics cloud systems. This document consists of a) a general introduction of the PubSub concepts, b) a definition of the PubSub configuration parameters, c) mapping of PubSub concepts and configuration parameters to messages and transport protocols, and d) a PubSub configuration model. Not all OPC UA Applications will need to implement all defined message and transport protocol mappings. IEC 62541-7 defines the Profile that dictates which mappings need to be implemented in order to be compliant with a particular Profile.

IEC 62541-3: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-3:2020 defines the OPC Unified Architecture (OPC UA) AddressSpace and its Objects. This document is the OPC UA meta model on which OPC UA information models are based. This third edition cancels and replaces the second edition published in 2015. This edition includes the following significant technical changes with respect to the previous edition: a) Added new improved approach for exposing structure definitions. An Attribute on the DataType Node now simply contains a binary description. b) Added new flags for Variables to indicate atomicity when reading or writing. c) Added Roles and Permissions to allow configuration of a role-based authorization. d) Added new data types: 'Union', 'Decimal', 'OptionSet', 'DateString', 'TimeString', 'DurationString', NormalizedString', 'DecimalString', and 'AudioDataType'. e) Added definition on how to use the ModellingRules OptionalPlaceHolder and MandatoryPlaceHolder for Methods. f) Added optional Properties 'MaxCharacters' and 'MaxByteStringLength' to Variable Nodes.

IEC 62541-4: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-4:2020 defines the OPC Unified Architecture (OPC UA) Services. The Services defined are the collection of abstract Remote Procedure Calls (RPC) that are implemented by OPC UA Servers and called by OPC UA Clients. All interactions between OPC UA Clients and Servers occur via these Services. The defined Services are considered abstract because no particular RPC mechanism for implementation is defined in this document. IEC 62541-6 specifies one or more concrete mappings supported for implementation. For example, one mapping in IEC 62541-6 is to XML Web Services. In that case the Services described in this document appear as the Web service methods in the WSDL contract. Not all OPC UA Servers will need to implement all of the defined Services. IEC 62541-7 defines the Profiles that dictate which Services need to be implemented in order to be compliant with a particular Profile This third edition cancels and replaces the second edition published in 2015. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: a) Added ability to resend all data of monitored items in a Subscription using the ResendData Method. b) Added support for durable Subscriptions (lifetime of hours or days). c) Added Register2 and FindServersOnNetwork Services to support network-wide discovery using capability filters. d) Removed definition of software certificates. Will be defined in a future edition. e) Extended and partially revised the redundancy definition. Added sub-range definitions for ServiceLevel and added more terms for redundancy. f) Added a section on how to use Authorization Services to request user access tokens. g) Added JSON Web Tokens (JWTs) as a new user token. h) Added the concept of session-less service invocation. i) Added a generic structure that allows passing any number of attributes to the AddNodes Service. j) Added requirement to protect against user identity token attacks. k) Added new EncryptedSecret format for user identity tokens.

IEC 62541-6:2020 which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition. IEC 62541-6:2020 specifies the OPC Unified Architecture (OPC UA) mapping between the security model described in IEC TR 62541-2, the abstract service definitions specified in IEC 62541-4, the data structures defined in IEC 62541-5 and the physical network protocols that can be used to implement the OPC UA specification. This third edition cancels and replaces the second edition published in 2015. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: a) Encodings: - added JSON encoding for PubSub (non-reversible); - added JSON encoding for Client/Server (reversible); - added support for optional fields in structures; - added support for Unions. b) Transport mappings: - added WebSocket secure connection - WSS; - added support for reverse connectivity; - added support for session-less service invocation in HTTPS. c) Deprecated Transport (missing support on most platforms): - SOAP/HTTP with WS-SecureConversation (all encodings). d) Added mapping for JSON Web Token. e) Added support for Unions to NodeSet Schema. f) Added batch operations to add/delete nodes to/from NodeSet Schema. g) Added support for multi-dimensional arrays outside of Variants. h) Added binary representation for Decimal data types. i) Added mapping for an OAuth2 Authorization Framework.

IEC 62541-7:2020 which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition. IEC 62541-7:2020 defines the OPC Unified Architecture (OPC UA) Profiles. The Profiles in this document are used to segregate features with regard to testing of OPC UA products and the nature of the testing (tool based or lab based). This includes the testing performed by the OPC Foundation provided OPC UA CTT (a self-test tool) and by the OPC Foundation provided Independent certification test labs. This could equally as well refer to test tools provided by another organization or a test lab provided by another organization. What is important is the concept of automated tool-based testing versus lab-based testing. The scope of this standard includes defining functionality that can only be tested in a lab and defining the grouping of functionality that is to be used when testing OPC UA products either in a lab or using automated tools. The definition of actual TestCases is not within the scope of this document, but the general categories of TestCases are within the scope of this document. Most OPC UA applications will conform to several, but not all, of the Profiles. This third edition cancels and replaces the second edition published in 2015. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: a) new functional Profiles: - profiles for global discovery and global certificate management; - profiles for global KeyCredential management and global access token management; - facet for durable subscriptions; - standard UA Client Profile; - profiles for administration of user roles and permissions. b) new transport Profiles: - HTTPS with JSON encoding; - secure WebSockets (WSS) with binary or JSON encoding; - reverse connectivity. c) new security Profiles: - transportSecurity - TLS 1.2 with PFS (with perfect forward secrecy); - securityPolicy [A] - Aes128-Sha256-RsaOaep (replaces Base128Rsa15); - securityPolicy - Aes256-Sha256-RsaPss adds perfect forward secrecy for UA TCP); - user Token JWT (Jason Web Token). d) deprecated Security Profiles (due to broken algorithms): - securityPolicy - Basic128Rsa15 (broken algorithm Sha1); - securityPolicy - Basic256 (broken algorithm Sha1); - transportSecurity - TLS 1.0 (broken algorithm RC4); - transportSecurity - TLS 1.1 (broken algorithm RC4). e) deprecated Transport (missing support on most platforms): - SOAP/HTTP with WS-SecureConversation (all encodings).

IEC 62872-1:2019(E) defines the interface, in terms of information flow, between industrial facilities and the 'smart grid'. It identifies, profiles and extends where required, the standards needed to allow the exchange of the information needed to support the planning, management and control of electric energy flow between the industrial facility and the smart grid.<br /> The scope of this document specifically excludes the protocols needed for the direct control of energy resources within a facility where the control and ultimate liability for such control is delegated by the industrial facility to the external entity (e.g. distributed energy resource (DER) control by the electrical grid operator).

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.

The document describes the key issues, solution proposals and recommendations for MEC integration into 3GPP 5G system. The following aspects are addressed: MEC System interactions with the 5G System, including the correspondence of the current MEC procedures to procedures available in 3GPP 5G system specification, options for the functional split between MEC and 5G Common API framework, realization of MEC as 5G Application Function(s). In addition the document addresses the scope and the preferred way of proceeding with the identified future technical work, as well as the identification of any missing 5G system functionality for MEC integration.

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.