IEC TR 62541-1:2010 pdf – oPC Unified Architecture -Part 1: Overview and Concepts.
Attribute
primitive characteristic of a Node
NOTE *a At1,ibut.s are d.fifl.d by OPC UA, and may not be d.hn.d by Cti.rns or S.rv.rs Atlnbut.s are th, only element. In the AddressSpai. permItted to have data values.
3.2.4
Certificate
digitally signed data structure that describes capabilities of a Client or Server
3.2.5
Client
software application that sends Messages to OPC UA Servers conforming to the Services specified in the IEC 62541 serIes of standards
3.2.6
Condition
generic term that is an extension to art Event
NOTE A Condilion represents h. condi1ies of a system or on. 01 S components and ahvays esists in seine state.
3.2.7
Communication Stack
layered set of software modules between the application and the hardware that provides various functions to encode, encrypt and format a Message for sending, and to decode. decrypt and unpack a Message that was received
3.2.8
Complex Data
data that is composed of elements of more than one primitive data type
3.2.9
Discovery
process by which OPC LJA Client obtains information about OPC UA Servers, including endpoint and security information
3.2.10
Event
generic term used to describe an occurrence of some significance within a system or system component
3.2.11
EventNotifier
special Attribute of a Node that signifies that a Client may subscribe to that particular Node to receive Nolificatioos of Event occurrences
3.2.12
Information Mod.l
organizational framework that defines, characterizes and relates information resources of a given system or set of systems
NOTE The coca eddreas space model supports the representatIon 01 lntorm.:Eon Models in the 4ddressSp.ce See IEC 62541-5 br a description 01 the base oc UA Information Model,
3.2.13
Message
data unit conveyed between Client and Server that represents a specific Service request or response
IEC 62541-1 to IEC 62541-7 specify the core capabilities of OPC UA These core capabilities define the structure of the OPC AddressSpace and the Services that operate on it. IEC 62541-8 to IEC 62541-11 apply these core capabilities to specific types of access previously addressed by separate OPC COM specifications, such as Data Access (DA). Alarms and Events (A8E) and Historical Data Access (HDA). lEG 6254 1-12 describes Discovery mechanisms for OPC UA and PEC 62541.13 describes ways of aggregating data.
Readers are encouraged to read lEG 62541-1 to lEG 62541-5 of the core specifications before reading lEG 62541-6 to lEG 6254 1-13. Some parts can be skipped depending on the needs of the reader. For example, a reader interested in Data Access should read IEC 62541- ito IEC 62541-5 and then IEC 6254 1-8.
4.2 Core specifications IECITR 62541-1 — General
Part 1 (this part) presents the concepts and overview of OPC Uk IEC 62541 -2 — Security model
IEC 62541-2 describes the model for securing interactions between OPC UA Clients and OPC UA Servers,
IEC 62541-3 — Address space model
IEC 62541-3 describes the contents and structure of the Server’s AddressSpace.
IEC 62541 -4— Services
IEC 6254 1-4 specifies the Services provided by OPC LJA Servers.
IEC 62541 -5— information model
IEC 6254 1-5 specifies the types and their relationships defined foi OPC UA Servers.
IEC 62541-6 — Mappings
IEC 6254 1-6 specifies the transport mappings and data encodings supported by OPC UA.
IEC 62541-7 — Profll.s
IEC 62541-7 specifies the Profiles that are available for OPC Clients and Servers. These Profiles provide groups of Services or functionality that can be used for conformance level certification, Servers and Clients will be tested against the Profiles.
4.3 Access type specification parts IEC 62541 -8 — Data access
IEC 62541-8 specifies the use of OPC LJA for data access
IEC 62541 -9 — Alarms and conditions
IEC 62541-9 specifies the use of OPC UA support for access to Alarms and Conditions. The base system Includes support for simple Events; this specification extends that support to include support for Alarms and Conditions.