CLC TR 62541-1-2010 OPC unified architecture - Part 1 Overview and concepts《OPC统一架构 第1部分 总论和概念》.pdf

1、raising standards worldwideNO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAWBSI Standards PublicationOPC unified architecturePart 1: Overview and conceptsPD CLC/TR 62541-1:2010National forewordThis Published Document is the UK implementation of CLC/TR 62541-1:2010.It is identica

2、l to IEC/TR 62541-1:2010.The UK participation in its preparation was entrusted to Technical CommitteeAMT/7, Industrial communications: process measurement and control, including fieldbus.A list of organizations represented on this committee can be obtained onrequest to its secretary.This publication

3、 does not purport to include all the necessary provisions of acontract. Users are responsible for its correct application. BSI 2010 ISBN 978 0 580 64157 2 ICS 25.040.40; 35.100.01; 35.200; 35.240.50Compliance with a British Standard cannot confer immunity from legal obligations.This Published Docume

4、nt was published under the authority of the Standards Policy and Strategy Committee on 30 November 2010.Amendments/corrigenda issued since publicationDate Text affectedPUBLISHED DOCUMENTPD CLC/TR 62541-1:2010TECHNICAL REPORT CLC/TR 62541-1 RAPPORT TECHNIQUE TECHNISCHER BERICHT August 2010 CENELEC Eu

5、ropean Committee for Electrotechnical Standardization Comit Europen de Normalisation Electrotechnique Europisches Komitee fr Elektrotechnische Normung Management Centre: Avenue Marnix 17, B - 1000 Brussels 2010 CENELEC - All rights of exploitation in any form and by any means reserved worldwide for

6、CENELEC members. Ref. No. CLC/TR 62541-1:2010 E ICS 25.040.40; 35.100.01 English version OPC unified architecture - Part 1: Overview and concepts (IEC/TR 62541-1:2010) Architecture unifie OPC - Partie 1: Vue densemble et concepts (CEI/TR 62541-1:2010) OPC Unified Architecture - Teil 1: bersicht und

7、Konzepte (IEC/TR 62541-1:2010) This Technical Report was approved by CENELEC on 2010-06-25. CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland,

8、Italy, Latvia, Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and the United Kingdom. CLC/TR 62541-1:2010 - 2 - Foreword The text of the Technical Report IEC/TR 62541-1:2010, prepared by SC 65E, Devices and integration

9、 in enterprise systems, of IEC TC 65, Industrial-process measurement, control and automation, was submitted to vote and was approved by CENELEC as CLC/TR 62541-1 on 2010-06-25. Annex ZA has been added by CENELEC. _ Endorsement notice The text of the Technical Report IEC/TR 62541-1:2010 was approved

10、by CENELEC as a Technical Report without any modification. In the official version, for Bibliography, the following notes have to be added for the standards indicated: IEC/TR 62541-2 NOTE Harmonized as CLC/TR 62541-2. IEC 62541-3 NOTE Harmonized as EN 62541-3. IEC 62541-4 NOTE Harmonized as EN 62541

11、-4. IEC 62541-5 NOTE Harmonized as EN 62541-5. IEC 62541-6 NOTE Harmonized as EN 62541-6. IEC 62541-8 NOTE Harmonized as EN 62541-8. _PD CLC/TR 62541-1:2010- 3 - CLC/TR 62541-1:2010 Annex ZA(normative) Normative references to international publications with their corresponding European publications

12、The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. NOTE When an international publication has been m

13、odified by common modifications, indicated by (mod), the relevant EN/HD applies. Publication Year Title EN/HD Year IEC 62541 Series OPC unified architecture EN 62541 Series PD CLC/TR 62541-1:2010 4 TR 62541-1 IEC:2010(E) CONTENTS INTRODUCTION.6 1 Scope.7 2 Normative references .7 3 Terms, definition

14、s, abbreviations and conventions 7 3.1 Document conventions 7 3.2 Terms and definitions 7 3.3 Abbreviations 11 4 Structure of the OPC UA series 11 4.1 Structure of the IEC 62541 series of standards11 4.2 Core specifications 12 4.3 Access type specification parts12 4.4 Utility specification parts .13

15、 5 IEC 62541 standards Overview13 5.1 UA scope 13 5.2 Introduction .13 5.3 Design goals .13 5.4 Integrated models and services .15 5.4.1 Security model.15 5.4.2 Integrated AddressSpace model 16 5.4.3 Integrated object model .17 5.4.4 Integrated services 17 5.5 Sessions .17 5.6 Redundancy 17 6 System

16、s concepts 17 6.1 Overview .17 6.2 OPC UA Clients.18 6.3 OPC UA Servers .19 6.3.1 General .19 6.3.2 Real objects 19 6.3.3 OPC UA Server application .19 6.3.4 OPC UA AddressSpace .20 6.3.5 Publisher/subscriber entities20 6.3.6 OPC UA Service interface .20 6.3.7 Server to Server interactions .21 7 Ser

17、vice sets .22 7.1 General .22 7.2 Discovery service set 22 7.3 SecureChannel service set 22 7.4 Session service set .23 7.5 NodeManagement Service Set 23 7.6 View Service Set .24 7.7 Query Service Set .24 7.8 Attribute Service Set .24 7.9 Method Service Set .24 7.10 MonitoredItem Service Set 24 PD C

18、LC/TR 62541-1:2010TR 62541-1 IEC:2010(E) 5 7.11 Subscription Service Set .25 Bibliography26 Figure 1 Organization of the OPC UA series of standards 11 Figure 2 OPC UA target applications14 Figure 3 OPC UA system architecture18 Figure 4 OPC UA Client architecture18 Figure 5 OPC UA server architecture

19、 .19 Figure 6 Peer-to-peer interactions between Servers.21 Figure 7 Chained Server example 22 Figure 8 SecureChannel and Session Services 23 PD CLC/TR 62541-1:2010 6 TR 62541-1 IEC:2010(E) INTRODUCTION This technical report introduces the specification for developers of OPC Unified Architecture appl

20、ications. This technical report and specification are a result of an analysis and design process to develop a standard interface to facilitate the development of applications by multiple vendors that inter-operate seamlessly together. PD CLC/TR 62541-1:2010TR 62541-1 IEC:2010(E) 7 OPC UNIFIED ARCHIT

21、ECTURE Part 1: Overview and Concepts 1 Scope This part of IEC 62541 presents the concepts and overview of the Unified Architecture (OPC UA) specification produced by the OPC Foundation. Reading this report enables the reader to understand the series of IEC 62541 standards. Each of the other parts is

22、 briefly explained along with a suggested reading order. 2 Normative references The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (incl

23、uding any amendments) applies. IEC 62541 (all parts), OPC Unified Architecture 3 Terms, definitions, abbreviations and conventions 3.1 Document conventions Throughout this document and the referenced other Parts of the series, certain document conventions are used. Italics are used to denote a defin

24、ed term or definition that appears in the “Terms and definition” clause in one of the Parts of the series. Italics are also used to denote the name of a service input or output parameter or the name of a structure or element of a structure that are usually defined in tables. The italicized terms and

25、 names are also often written in camel-case (the practice of writing compound words or phrases in which the elements are joined without spaces, with each elements initial letter capitalized within the compound). For example the defined term is AddressSpace instead of Address Space. This makes it eas

26、ier to understand that there is a single definition for AddressSpace, not separate definitions for Address and Space. 3.2 Terms and definitions For the purposes of this document, the following terms and definitions apply. 3.2.1 AddressSpace collection of information that an OPC UA Server makes visib

27、le to its Clients NOTE See IEC 62541-3 for a description of the contents and structure of the Server AddressSpace. 3.2.2 Alarm type of Event associated with a state condition that typically requires acknowledgement NOTE See IEC 62541-9 or a description of Alarms. PD CLC/TR 62541-1:2010 8 TR 62541-1

28、IEC:2010(E) 3.2.3 Attribute primitive characteristic of a Node NOTE All Attributes are defined by OPC UA, and may not be defined by Clients or Servers. Attributes are the only elements in the AddressSpace permitted to have data values. 3.2.4 Certificate digitally signed data structure that describes

29、 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 an Event NOTE A Condition represents the conditions of a system o

30、r one of its components and always exists in some 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 receiv

31、ed 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 UA 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 significa

32、nce 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 Notifications of Event occurrences 3.2.12 Information Model organizational framework that defines, characterizes and relates informat

33、ion resources of a given system or set of systems NOTE The core address space model supports the representation of Information Models in the AddressSpace. See IEC 62541-5 for a description of the base OPC UA Information Model. 3.2.13 Message data unit conveyed between Client and Server that represen

34、ts a specific Service request or response PD CLC/TR 62541-1:2010TR 62541-1 IEC:2010(E) 9 3.2.14 Method callable software function that is a component of an Object 3.2.15 MonitoredItem Client-defined entity in the Server used to monitor Attributes or EventNotifiers for new values or Event occurrences

35、 and that generates Notifications for them 3.2.16 Node fundamental component of an AddressSpace 3.2.17 NodeClass class of a Node in an AddressSpace NOTE NodeClasses define the metadata for the components of the OPC UA Object Model. They also define constructs, such as Views, that are used to organiz

36、e the AddressSpace. 3.2.18 Notification generic term for data that announces the detection of an Event or of a changed Attribute value; Notifications are sent in NotificationMessages 3.2.19 NotificationMessage Message published from a Subscription that contains one or more Notifications 3.2.20 Objec

37、t Node that represents a physical or abstract element of a system NOTE Objects are modelled using the OPC UA Object Model. Systems, subsystems and devices are examples of Objects. An Object may be defined as an instance of an ObjectType. 3.2.21 Object Instance synonym for Object NOTE Not all Objects

38、 are defined by ObjectTypes. 3.2.22 ObjectType Node that represents the type definition for an Object 3.2.23 Profile specific set of capabilities to which a Server may claim conformance; each Server may claim conformance to more than one Profile NOTE The set of capabilities are defined in IEC 62541-

39、7. 3.2.24 Program executable Object that, when invoked, immediately returns a response to indicate that execution has started, and then returns intermediate and final results through Subscriptions identified by the Client during invocation PD CLC/TR 62541-1:2010 10 TR 62541-1 IEC:2010(E) 3.2.25 Refe

40、rence explicit relationship (a named pointer) from one Node to another NOTE The Node that contains the Reference is the source Node, and the referenced Node is the target Node. All References are defined by ReferenceTypes. 3.2.26 ReferenceType Node that represents the type definition of a Reference

41、NOTE The ReferenceType specifies the semantics of a Reference. The name of a ReferenceType identifies how source Nodes are related to target Nodes and generally reflects an operation between the two, such as “A Contains B”. 3.2.27 RootNode beginning or top Node of a hierarchy NOTE The RootNode of th

42、e OPC UA AddressSpace is defined in IEC 62541-5. 3.2.28 Server software application that implements and exposes the Services specified in the IEC 62541 series of standards 3.2.29 Service Client-callable operation in an OPC UA Server NOTE Services are defined in IEC 62541-4. A Service is similar to a

43、 method call in a programming language or an operation in a Web services WSDL contract. 3.2.30 Service Set group of related Services 3.2.31 Session logical long-running connection between a Client and a Server. NOTE A Session maintains state information between Service calls from the Client to the S

44、erver. 3.2.32 Subscription Client-defined endpoint in the Server, used to return Notifications to the Client NOTE ”Subscription” is a generic term that describes a set of Nodes selected by the Client (1) that the Server periodically monitors for the existence of some condition, and (2) for which the

45、 Server sends Notifications to the Client when the condition is detected. 3.2.33 Variable Node that contains a value 3.2.34 View specific subset of the AddressSpace that is of interest to the Client. PD CLC/TR 62541-1:2010TR 62541-1 IEC:2010(E) 11 3.3 Abbreviations A this specification extends that

46、support to include support for Alarms and Conditions. PD CLC/TR 62541-1:2010TR 62541-1 IEC:2010(E) 13 IEC 62541-10 Programs IEC 62541-10 specifies OPC UA support for access to Programs. IEC 62541-11 Historical access IEC 62541-11 specifies use of OPC UA for historical access. This access includes bo

47、th historical data and historical Events. 4.4 Utility specification parts IEC 62541-12 Discovery IEC 62541-12 specifies how Discovery Servers operate in different scenarios and describes how UA Clients and Servers should interact with them. It also defines how UA related information should be access

48、ed using common directory service protocols such as UDDI and LDAP. IEC 62541-13 Aggregates IEC 62541-13 specifies how to compute and return aggregates like minumum, maximum, average etc. Aggregates can be used with base (live) data as well as historical (HDA) data. 5 IEC 62541 standards Overview 5.1

49、 UA scope OPC UA is applicable to manufacturing software in application areas such as Field Devices, Control Systems, Manufacturing Execution Systems and Enterprise Resource Planning Systems. These systems are intended to exchange information and to use command and control for industrial processes. OPC UA defines a common infrastructure model to facilitate this information exchange OPC UA specifies the following: the information model to represent structure, behavio