opc ua原版完整文件.docx

®FOUNDATIONOPC Unified Architecture SpecificationPart 1:ConceptsVersion 1.00July 28, 2006OPC Unified Architecture, Part 1iiRelease1.00Specification Type:Industry Standard SpecificationComments:Report or view errata:http:/www.opcfoundation.org/errat aTitle:OPC Unified Architecture Part 1 :Concepts Release 1.00 OPC FoundationDate:July 28, 2006Version:Software:MS-WordSource:OPC UA Part 1 - Concepts 1.00Specification.docAuthor:Status:ReleaseOPC Unified Architecture, Part 1viiRelease 1.00CONTENTSPageFOREWORDviAGREEMENT OF USEvi1 Scope12 Reference documents13 Terms, definitions, and abbreviations13.1 OPC UA terms13.1.1 AddressSpace13.1.2 Alarm23.1.3 Attribute23.1.4 Certificate23.1.5 Client23.1.6 Communication Stack23.1.7 Complex Data23.1.8 Event23.1.9 EventNotifier23.1.10 Information Model23.1.11 Message23.1.12 Method23.1.13 MonitoredItem33.1.14 Node33.1.15 NodeClass33.1.16 Notification33.1.17 NotificationMessage33.1.18 Object33.1.19 Object Instance33.1.20 ObjectType.33.1.21 Profile33.1.22 Program33.1.23 Reference33.1.24 ReferenceType43.1.25 RootNode43.1.26 Server43.1.27 Service.43.1.28 Service Set43.1.29 Session43.1.30 Subscription43.1.31 Variable43.1.32 View43.2 Abbreviations and symbols44 Structure of the OPC UA series54.1 Specification Organization54.2 Core Specification Parts54.2.1 Part 1 OPC UA Concepts54.2.2 Part 2 OPC UA Security Model54.2.3 Part 3 OPC UA Address Space Model54.2.4 Part 4 OPC UA Services54.2.5 Part 5 OPC UA Information Model64.2.6 Part 6 OPC UA Service Mappings64.2.7 Part 7 OPC UA Profiles64.3 Access Type Specification Parts64.3.1 Part 8 OPC UA Data Access64.3.2 Part 9 OPC UA Alarms and Conditions64.3.3 Part 10 OPC UA Programs64.3.4 Part 11 OPC UA Historical Access65 Overview65.1 Introduction.65.2 Design goals65.3 Integrated models and services85.3.1 Security model85.3.2 Integrated AddressSpace model95.3.3 Integrated object model95.3.4 Integrated services105.4 Sessions105.5 Redundancy106 Systems concepts116.1 Overview116.2 OPC UA Clients116.3 OPC UA Servers126.3.1 Real objects126.3.2 OPC UA Server application126.3.3 OPC UA AddressSpace126.3.4 Publisher/subscriber entities136.3.5 OPC UA Service Interface136.3.6 Server to Server interactions147 Service Sets157.1 General157.2 SecureChannel Service Set157.3 Session Service Set167.4 NodeManagement Service Set167.5 View Service Set167.6 Attribute Service Set177.7 Method Service Set177.8 MonitoredItem Service Set177.9 Subscription Service Set177.10 Query Service Set18FIGURESFigure 1 OPC UA Specification Organization5Figure 2 OPC UA Target Applications7Figure 3 OPC UA System Architecture11Figure 4 OPC UA Client Architecture11Figure 5 OPC UA Server Architecture12Figure 6 Interactions between Servers14Figure 7 Chained Server Example15Figure 8 SecureChannel and Session Services16OPC FOUNDATIONUNIFIED ARCHITECTURE FOREWORDThis specification is the specification for developers of OPC UA applications. The specification is a result of an analysis and design process to develop a standard interface to facilitate the development of applications by multiple vendors that shall inter-operate seamlessly together.Copyright © 2006, OPC Foundation, Inc.AGREEMENT OF USECOPYRIGHT RESTRICTIONSAny unauthorized use of this specification may violate copyright laws, trademark laws, and communications regulations and statutes. This document contains information which is protected by copyright. All Rights Reserved. No part of this work covered by copyright herein may be reproduced or used in any form or by any means-graphic, electronic, or mechanical, including photocopying, recording, taping, or information storage and retrieval systems-without permission of the copyright owner.OPC Foundation members and non-members are prohibited from copying and redistributing this specification. All copies must be obtained on an individual basis, directly from the OPC Foundation Web site http:/www.opcfoundation.org.PATENTSThe attention of adopters is directed to the possibility that compliance with or adoption of OPC specifications may require use of an invention covered by patent rights. OPC shall not be responsible for identifying patents for which a license may be required by any OPC specification, or for conducting legal inquiries into the legal validity or scope of those patents that are brought to its attention. OPC specifications are prospective and advisory only. Prospective users are responsible for protecting themselves against liability for infringement of patents.WARRANTY AND LIABILITY DISCLAIMERSWHILE THIS PUBLICATION IS BELIEVED TO BE ACCURATE, IT IS PROVIDED "AS IS" AND MAY CONTAIN ERRORS OR MISPRINTS. THE OPC FOUDATION MAKES NO WARRANTY OF ANY KIND, EXPRESSED OR IMPLIED, WITH REGARD TO THIS PUBLICATION, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF TITLE OR OWNERSHIP, IMPLIED WARRANTY OF MERCHANTABILITY OR WARRANTY OF FITNESS FOR A PARTICULAR PURPOSE OR USE. IN NO EVENT SHALL THE OPC FOUNDATION BE LIABLE FOR ERRORS CONTAINED HEREIN OR FOR DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, RELIANCE OR COVER DAMAGES, INCLUDING LOSS OF PROFITS, REVENUE, DATA OR USE, INCURRED BY ANY USER OR ANY THIRD PARTY IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS MATERIAL, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.The entire risk as to the quality and performance of software developed using this specification is borne by you. RESTRICTED RIGHTS LEGENDThis Specification is provided with Restricted Rights. Use, duplication or disclosure by the U.S. government is subject to restrictions as set forth in (a) this Agreement pursuant to DFARs 227.7202-3(a); (b) subparagraph (c)(1)(i) of the Rights in Technical Data and Computer Software clause at DFARs 252.227-7013; or (c) the Commercial Computer Software Restricted Rights clause at FAR 52.227-19 subdivision (c)(1) and (2), as applicable. Contractor / manufacturer are the OPC Foundation,. 16101 N. 82nd Street, Suite 3B, Scottsdale, AZ, 85260-1830COMPLIANCEThe OPC Foundation shall at all times be the sole entity that may authorize developers, suppliers and sellers of hardware and software to use certification marks, trademarks or other special designations to indicate compliance with thesematerials. Products developed using this specification may claim compliance or conformance with this specification if and only if the software satisfactorily meets the certification requirements set by the OPC Foundation. Products that do not meet these requirements may claim only that the product was based on this specification and must not claim compliance or conformance with this specification.TRADEMARKSMost computer and software brand names have trademarks or registered trademarks. The individual trademarks have not been listed here.GENERAL PROVISIONSShould any provision of this Agreement be held to be void, invalid, unenforceable or illegal by a court, the validity and enforceability of the other provisions shall not be affected thereby.This Agreement shall be governed by and construed under the laws of the State of Minnesota, excluding its choice or law rules.This Agreement embodies the entire understanding between the parties with respect to, and supersedes any prior understanding or agreement (oral or written) relating to, this specification.ISSUE REPORTINGThe OPC Foundation strives to maintain the highest quality standards for its published specifications, hence they undergo constant review and refinement. Readers are encouraged to report any issues and view any existing errata here: http:/www.opcfoundation.org/errataOPC Unified Architecture, Part 118Release 1.001 ScopeThis specification presents an overview on the OPC Unified Architecture concepts.2 Reference documentsThe OPC Unified Architecture Specification is organized as a multi-part document. While describing the concepts, this part will refer to these parts of the specification:UA Part 2 OPC UA Specification: Part 2 Security Model, Version 1.0 or later http:/www.opcfoundation.org/UA/Part2/UA Part 3 OPC UA Specification: Part 3 Address Space Model, Version 1.0 or later http:/www.opcfoundation.org/UA/Part3/UA Part 4 OPC UA Specification: Part 4 Services, Version 1.0 or later http:/www.opcfoundation.org/UA/Part4/UA Part 5 OPC UA Specification: Part 5 Information Model, Version 1.0 or later http:/www.opcfoundation.org/UA/Part5/UA Part 6 OPC UA Specification: Part 6 Mappings, Version 1.0 or later http:/www.opcfoundation.org/UA/Part6/UA Part 7 OPC UA Specification: Part 7 Profiles, Version 1.0 or later http:/www.opcfoundation.org/UA/Part7/UA Part 8 OPC UA Specification: Part 8 Data Access, Version 1.0 or later http:/www.opcfoundation.org/UA/Part8/UA Part 9 OPC UA Specification: Part 9 Alarms and Conditions, Version 1.0 or later http:/www.opcfoundation.org/UA/Part9/UA Part 10 OPC UA Specification: Part 10 Programs, Version 1.0 or later http:/www.opcfoundation.org/UA/Part10/UA Part 11 OPC UA Specification: Part 11 Historical Access, Version 1.0 or later http:/www.opcfoundation.org/UA/Part11/3 Terms, definitions, and abbreviationsFor the purposes of this specification, the following definitions apply.3.1 OPC UA terms3.1.1 AddressSpaceThe collection of information that an OPC UA Server makes visible to its Clients. See UA Part 3 for a description of the contents and structure of the Server AddressSpace.3.1.2 AlarmA type of Event associated with a state condition that typically requires acknowledgement. See UA Part 9 for a description of Alarms.3.1.3 AttributeA primitive characteristic of a Node. 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.1.4 CertificateA digitally signed data structure that describes the capabilities of a Client or Server.3.1.5 ClientA software application that sends Messages to OPC UA Servers conforming to the Servicesspecified in this set of specifications.3.1.6 Communication StackA 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.1.7 Complex DataData that is composed of elements or more than one primitive data type, such as a structure.3.1.8 EventA generic term used to describe an occurrence of some significance within a system or system component.3.1.9 EventNotifierA special Attribute of a Node that signifies that a Client may subscribe to that particular Node to receive Notifications of Event occurrences.3.1.10 Information ModelAn organizational framework that defines, characterizes and relates information resources of a given system or set of systems. The core address space model supports the representation of Information Models in the AddressSpace. See UA Part 5 for a description of the base OPC UA Information Model.3.1.11 MessageThe data unit conveyed between Client and Server that represents a specific Service request or response.3.1.12 MethodA callable software function.3.1.13 MonitoredItemA Client-defined entity in the Server used to monitor Attributes or EventNotifiers for new values orEvent occurrences and generate Notifications for them.3.1.14 NodeThe fundamental component of an AddressSpace.3.1.15 NodeClassThe class of a Node in an AddressSpace. NodeClasses define the metadata for the components of the OPC UA Object Model. They also define constructs, such as Views, that are used to organize the AddressSpace.3.1.16 NotificationThe generic term for data that announces the detection of an Event or of a changed Attribute value.Notifications are sent in NotificationMessages.3.1.17 NotificationMessageA Message published from a Subscription that contains one or more Notifications.3.1.18 ObjectA Node that represents a physical or abstract element of a system. 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.1.19 Object InstanceA synonym for Object. Not all Objects are defined by ObjectTypes.3.1.20 ObjectTypeA Node that represents the type definition for an Object.3.1.21 ProfileA specific set of capabilities, defined in UA Part 7, to which a Server may claim conformance. Each Server may claim conformance to more than one Profile.3.1.22 ProgramAn 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.3.1.23 ReferenceAn explicit relationship (a named pointer) from one Node to another. 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.1.24 ReferenceTypeA Node that represents the type definition of a Reference. 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.1.25 RootNodeThe beginning or top Node of a hierarchy. The RootNode of the OPC UA AddressSpace is defined in UA Part 5.3.1.26 ServerA software application that implements and exposes the Services specified in this set of specifications.3.1.27 ServiceA Client-callable operation in an OPC UA Server. Services are defined in UA Part 4. A Service is similar to a method call in a programming language or an operation in a Web services WSDL contract.3.1.28 Service SetA group of related Services.3.1.29 SessionA logical long-running connection between a Client and a Server. A Session maintains state information between Service calls from the Client to the Server.3.1.30 SubscriptionA Client-defined endpoint in the Server, used to return Notifications to the Client. Generic term that describes a set of Nodes selected by the Client (1) that the Server periodically