Search

194 result(s) for PubSub

• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  2.1.34 PubSub
  PubSub OPC UA variant of the publish subscribe messaging pattern
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  2.1.19 Message Oriented Middleware
  Other types like DDS or XMPP can also be integrated into the OPC UA PubSub model
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  2.1.42 Subscriber
  ClientServer model has a different meaning than the Subscriber in the PubSub model
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  3.2 Specification parts
  Aggregates can be used with current and historical data. Part 14 ( OPC 10000-14 ) - PubSub Part 14 specifies the OPC Unified Architecture (OPC UA) PubSub communication model. The PubSub communication
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  4.2 General
  ClientServer model, OPC UA also supports information transfer from Publishers to Subscribers using the PubSub model
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  4.3 Design goals
  into a single integrated address space with a single set of Services . OPC UA PubSub opens new application fields for OPC UA. The following are some example uses for PubSub ... cloud. For example, backend servers, big data analytics for system optimization and predictive maintenance. PubSub is not bound to a particular messaging system. Rather it can be mapped to various
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  5.3.7 Server to Server interactions
  Servers Similar peer-to-peer interactions can also be accomplished using the OPC UA PubSub model where each peer Application is both a Publisher and a Subscriber . Figure 6 extends
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  5.5 Publish-Subscribe
  Publish-Subscribe The Publish-Subscribe ( PubSub ) communication model in OPC UA offers an alternative to the ClientServer model, enabling efficient and/or decoupled communication. With PubSub,   OPC UA Applications ... this distribution is implemented. To cover a large number of use cases, OPC UA PubSub supports two largely different Message Oriented Middleware variants. These are: A broker-less form, where
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  5.6 Synergy of models
  Synergy of models OPC UA PubSub and ClientServer models are complementary and can be combined and used synergistically. The OPC UA Information Model is the foundation for both. A typical ... scenario involves using ClientServer interactions for configuration, control, and on-demand data access, while PubSub is used for efficient, high-speed dissemination of real-time data. For instance, a Client
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  2 Normative References
  Part 12 - Discovery https://www.opcfoundation.org/UA/Part12/ OPC 10000-14, OPC UA Specification: Part 14 - PubSub https://www.opcfoundation.org/UA/Part14/ OPC 10000-18, OPC UA Specification: Part 18: Role-Based Security
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  3.1.43 SecurityKeyService
  typically used for cryptography operations such as encrypting or decrypting messages sent on a PubSub stream
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.3.2.2 Message flooding
  Server with malformed Message s in order to exhaust the Server 's resources. For PubSub , an attacker can send a large volume of dataset messages with the goal of overwhelming ... conducted at multiple layers including OPC UA, UDP, AMQP, MQTT. As in Client - Server, PubSub message flooding attacks can use both well-formed and malformed Messages . For well-formed Messages
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.3.2.3 Resource Exhaustion
  Server . Resource exhaustion attacks do not occur in the same manner for PubSub communications since no session or resources are allocated. For PubSub communication, the Publisher is not susceptible ... broker-less PubSub communication, the Subscriber can, with the use of filters, bypass any resource exhaustion issues. In broker case, both the Publisher and Subscriber are connected to the broker
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.5.1 Overview
  security architecture - Client / Server OPC UA also supports a Publish - Subscribe communications architecture ( PubSub ) and the security architecture for that communication is illustrated in Figure 3 . Figure
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.5.3.1 Overview
  Overview The PubSub can be deployed in two environments, one in which a broker exists and one which is broker less. OPC 10000-14 defines the details of this model
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.5.3.2 Broker-less
  Broker-less The broker-less PubSub communication model provides Confidentiality and Integrity. This is accomplished using Symmetric Encryption and signature algorithms. The required SymmetricKeys are distributed by a Security
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.5.3.3 Broker
  Broker When using a Broker in the PubSub model, the same shared SymmetricKey concepts as defined in 4.5.3.2 can be used to provide Confidentiality and Integrity. Furthermore, communication ... shared SymmetricKeys eliminates this risk. For complete details on share SymmetricKeys (SKS) and securing PubSub message in Broker based transports see OPC 10000-14 . The model is illustrated in Figure
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.6 SecurityPolicies
  session-less connection it wishes to make. SecurityPolicies are also used with PubSub communication. SecurityPolicies include the following information: algorithms for signing and encryption algorithm for key derivation The choice
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.13 OPC UA security related Services
  Typically for Client Server communication this would be at least every two hours. For PubSub communications, the security related definitions are specified in OPC 10000-14 and provide a description ... also SymmetricKeys and follow the same rules with regard to periodically changing them. Since PubSub communication is usually at a higher rate, the time period for between key changes would
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  5.1.2.2 Message flooding
  Clients also ignore extra responses that could be received and closes the connection. In PubSub , the Subscriber filters messages that it processes based on header information, allowing it to quickly ... eliminate any message that is well formed, but not from the desired SecurityGroup . PubSub can also be configured for unicast instead of multicast, which allows the network infrastructure to block
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  5.1.2.3 Resource exhaustion
  connection attempts that only open a socket. Resource exhaustion attacks do not apply to PubSub Systems, since no sessions or resources are allocated
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  5.1.4 Message spoofing
  predictable number. As specified in OPC 10000-14 , OPC UA PubSub counters Message spoofing threats by providing the ability to sign messages. Messages can also contain a valid PublisherId , DataSetClassId
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  5.1.6 Message replay
  number that are part of all messages and thus cannot be replayed. OPC UA PubSub uses PublisherIds , DataSetWriterIds , Timestamps , network message numbers and sequence numbers in published messages. When Messages ... configured that replay of a message is not possible. It is worth noting that PubSub does allow the disabling of fields in a message. The disabling of the Timestamp , network
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  5.2.4 Authorization
  Authentication error as specified in the status codes defined in OPC 10000-4 . In PubSub interactions user Authorization can be used as part of the key distribution (SKS). This allows
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  5.2.6 Integrity
  SecureChannel establishment. The Symmetric Signatures are applied to all other Message s including PubSub messages. OPC UA relies upon the site CSMS to protect Integrity on the network and system
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.1.9 Variant
  Variants can contain DataValue when used in other contexts such as Method Arguments or PubSub Messages . The Variant in a DataValue cannot, directly or indirectly, contain another DataValue . ExtensionObjects
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.4.1 General
  There are two important use cases for the JSON encoding: cloud applications which consume PubSub messages and JavaScript Clients (JSON is the preferred serialization format for JavaScript). For the cloud ... application use case, the PubSub message is self-contained which implies it cannot contain numeric references to an externally defined namespace table. Cloud applications also often rely on scripting languages
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  1 Scope
  Scope This part of OPC Unified Architecture (OPC UA) defines the PubSub communication model. It defines an OPC UA publish subscribe pattern which complements the client server pattern defined ... 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
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  3.1.1 Action
  entry: An Action is similar to a Method that can be invoked via PubSub
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  4.1 Fields of application
  Fields of application In PubSub the participating OPC UA Applications with their roles as Publishers and Subscribers are decoupled. The number of Subscribers receiving data from a Publisher does ... influence the Publisher . This makes PubSub suitable for applications where location independence and/or scalability are required. The following are some example uses for PubSub : Configurable peer-to-peer communication between
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  4.2 Abstraction layers
  Abstraction layers PubSub is designed to be flexible and is not bound to a particular messaging system. All components and activities are first described abstractly in Clause ... mappings and message mappings are specified in Clause 7 . Defined with these abstraction layers, PubSub can be used to transport different types of information through networks with different characteristics
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  4.3 Decoupling by use of middleware
  Decoupling by use of middleware In PubSub the participating OPC UA Applications can assume the roles Publisher and Subscriber . Publishers are the sources of data, while Subscribers consume that data ... Communication in PubSub is message-based. Publishers send messages to a Message Oriented Middleware , without knowledge of what, if any, Subscribers there may be. Similarly, Subscribers express interest in specific
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  4.4 Synergy of models
  Synergy of models PubSub and Client Server are both based on the OPC UA Information Model . PubSub therefore can easily be integrated into OPC UA Servers and OPC UA Clients ... information) and a Subscriber is often an OPC UA Client . Above all, the PubSub Information Model for configuration (see 9 ) promotes the configuration of Publishers and Subscribers using
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  5.1 General
  General Clause 5 describes the general OPC UA PubSub concepts. The DataSet constitutes the payload of messages provided by the Publisher and consumed by the Subscriber . The DataSet is described ... transport protocol mappings is defined in Clause 7 . The OPC UA Information Model for PubSub configuration in Clause 9 specifies the standard Objects in an OPC UA AddressSpace used
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  5.2.1 General
  data is obtained for publishing can be configured using the PubSub configuration model defined in 8.2 or with vendor-specific configuration tools
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  5.2.3 DataSetMetaData
  Client and is able to get the necessary configuration information from the PubSub configuration model (see 9.1.4.2.1 ) provided by the Publisher or from a configuration server. The Subscriber supports ... configuration Methods defined in the PubSub configuration model. The Subscriber receives the DataSetMetaData as NetworkMessage from the Publisher . This may require an option for the Subscriber to request this NetworkMessage
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  5.3.5 Message security
  Message security Message security in PubSub concerns integrity and confidentiality of the published message payload. The base concepts for OPC UA security are defined in OPC 10000-2 . The level ... These parameters are independent of any Broker level transport security. The message security for PubSub is independent of the transport protocol mapping and is completely defined
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  5.4.1.1 General
  General The Publisher is the PubSub entity that sends NetworkMessages to a Message Oriented Middleware . It represents a certain information source, for example, a control device, a manufacturing process ... stock exchange. Commonly, a Publisher is also an OPC UA Server . For the abstract PubSub concepts, however, it is an arbitrary entity and should not be assumed
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  5.4.1.2 Message sending
  independent entities. However, comparable processes need to exist to generate the OPC UA PubSub messages. Figure 6 - Publisher message sending sequence The sending process is guided by different parameters ... trigger the sending sequence and the encoding and security of the messages. The PubSub communication parameters are defined in Clause 6 . The first step is the collection of data ( DataSet
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  5.4.2.1 General
  that are neither Client nor Server but only understand the structure of OPC UA PubSub messages. Figure 7 illustrates a Subscriber with filtering, decoding and dispatching of NetworkMessages . Figure ... through the OPC UA defined configuration model. The OPC UA Information Model for PubSub configuration is specified in Clause
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  5.4.3 Actions
  Method in an OPC UA Address Space or business logic in an OPC UA PubSub application. The ActionMetaData consists of the DataSetMetaData for the request message, the DataSetMetaData
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  5.4.4 Configuration Tool
  other configuration Structures defined in Clause 6 can be used to prepare an offline PubSub configuration that can be stored in a binary file using the UABinaryFileDataType . Such a configuration ... tools. If Publishers and Subscribers are also OPC UA Servers , they can provide the PubSub configuration Information Model defined in Clause 9 . This model can be used by generic PubSub
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  5.4.5.1 General
  them. The SKS is responsible for managing the keys used to publish or consume PubSub NetworkMessages . Separate keys are associated with each SecurityGroupId in the system. The GetSecurityKeys Method exposed
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  5.4.5.2 SecurityGroup Management
  Publishers and Subscribers , the SecurityGroupId and the SKS EndpointDescriptions are configured in a PubSub group
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  5.4.5.3 Key acquisition handshakes
  Method is defined in 9.1.3.3 . If the initial pull or push fails, the affected PubSub components like WriterGroup or DataSetReader stay in the PreOperational state. If the updates fail ... PubSub components do not have up to date key material, the state of the affected components change to Error . For both pull and push, the Client executing the key exchange
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  5.4.6.1 General
  uses protocols that allow connecting, sending and receiving data. The transport protocol mappings for PubSub are described in 7.3 . This document describes two general types of Message Oriented Middleware
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  5.4.6.2.1 General
  General With this option, OPC UA PubSub relies on the network infrastructure to deliver NetworkMessage s to one or more receivers. Network devices - like network routers, switches, or bridges ... with unicast or multicast messages shown in Figure 14 . Figure 14 - PubSub using network infrastructure Advantages of this model include: Only requires standard network equipment and no additional software components
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  5.4.6.3.2 Broker-based model
  Broker overview An OPC UA Publisher that publishes data may be configured through the PubSub configuration model. It contains one connection Object per Broker . The Broker is configured through
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  5.4.6.4 QoS configuration
  differentiated services (DiffServ). This mapping should be hidden to the application engineer from a PubSub perspective but may be monitored or configurable via the information model ... This list can be extended by specifications built on top of OPC UA PubSub . Each QosCategory will be described in detail by a list of measurable QoS KPIs like assured
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  6.1 Overview
  Overview PubSub defines different configuration parameters for the various PubSub components. They define the behaviour of Publisher and Subscriber . The parameters are grouped by component and are partitioned into 'common ... Configuration of these parameters can be performed through the OPC UA Information Model for PubSub configuration defined in Clause 9 or through vendor-specific mechanisms. The parameter groupings in this
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  6.2.1 PubSubState state machine
  state machine The PubSubState is used to expose and control the operation of a PubSub component. It is an enumeration of the possible states. The enumeration values are described ... Table 1 . Table 1 - PubSubState values Name Value Description Disabled 0 The PubSub component is configured but currently disabled. Paused 1 The PubSub component is enabled but currently paused
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  6.2.2 PubSub configuration properties
  PubSub configuration properties The PubSub components have configuration property lists as KeyValuePair arrays. These optional configuration properties extend the configuration parameters defined for the different PubSub components. The configuration properties ... mainly used as protocol or product specific parameters influencing the behaviour of the PubSub application. These properties may contain information that should not be visible outside the configuration tools
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  6.2.5.4 SecurityKeyServices
  SecurityGroupId and SKS ApplicationUri is the unique key for a SecurityGroup in a PubSub application. Table 40 - SecurityKeyService parameter content Field Type Definition for the values EndpointUrl String Shall ... Method GetSecurityKeys . CLIENT The security keys are pushed from the SKS to the PubSub application using the Method SetSecurityKeys . CLIENTANDSERVER Invalid value. DISCOVERYSERVER Invalid value. If the SKS information
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  6.2.7.2 TransportProfileUri
  possible TransportProfileUri values are defined as URI of the transport protocols defined as PubSub transport Facet
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  6.2.7.4 ConnectionProperties
  ConnectionProperties . Table 47 - ConnectionProperties Key DataType Description 0:SksPullRetryInterval Duration The interval the PubSub application shall use to retry pulling keys after an error appeared. The PubSub application shall have
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  6.2.12.1 PubSubConfigurationDataType
  PubSubConfigurationDataType This Structure DataType is used to represent the PubSub configuration of an OPC UA Application . The PubSubConfigurationDataType is formally defined in Table 86 . Table 86 - PubSubConfigurationDataType structure Name Type ... connection includes WriterGroups and ReaderGroups . Enabled Boolean The enabled state of the PubSub configuration. This Enable state corresponds to the PubSub Status of the PublishSubscribe Object . Its representation
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  6.2.12.2 SecurityGroupDataType
  This Structure DataType is used to represent the configuration of a SecurityGroup in a PubSub configuration of an OPC UA Application . If the SecurityPolicyUri or the KeyLifetime of an existing ... BrowseName SecurityGroupDataType IsAbstract False Subtype of Structure defined in OPC 10000-5 . Conformance Units PubSub Parameters Configuration2
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  6.2.12.3 PubSubKeyPushTargetDataType
  This Structure DataType is used to represent the configuration of a PubSubKeyServicePushTarget in a PubSub configuration of an OPC UA Application . The PubSubKeyPushTargetDataType is formally defined in Table 91 . Table ... BrowseName PubSubKeyPushTargetDataType IsAbstract False Subtype of Structure defined in OPC 10000-5 . Conformance Units PubSub Parameters Configuration2
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  6.2.12.4 PubSubConfiguration2DataType
  PubSubConfiguration2DataType This Structure DataType is used to represent the extended PubSub configuration of an OPC UA Application . It is a subtype of the PubSubConfigurationDataType defined in 6.2.12.1 . The PubSubConfiguration2DataType ... DataSetMeta‌DataType[] DataSetClasses supported by the Publisher . DefaultSecurityKeyServices EndpointDescription[] The default SecurityKeyServices used for the PubSub configuration. The value is as default if not overwritten in the groups or DataSetReaders
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  7.1 General
  General Clause 7 specifies the mapping between the PubSub concepts described in clause 5 and the PubSub configuration parameters defined in clause 6 to concrete message mappings and transport protocol ... mappings are combined together to create transport profiles defined in OPC 10000-7 . All PubSub applications shall implement at least one transport profile
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  7.3.4.8 Message header
  application programs responsible for sending and receiving them. They are used here to specify PubSub properties not directly supported by the MQTT protocol. Table 207 describes how these properties shall
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  8.1 Overview
  PublishSubscribe Object Types overview The PublishSubscribe Object is the root node for all PubSub related configuration Objects . It is an instance of the PubSubKeyServiceType or the PublishSubscribeType and a component ... PublishSubscribe Object if only the Security Key Service functionality is provided. If the PubSub configuration functionality is provided, the PublishSubscribeType is used instead. A SecurityGroup manages keys used for securing
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  8.2 PublishSubscribe Object
  Object To provide interoperability between Publishers, Subscribers, Security Key Services and configuration tools, all PubSub related Objects shall be exposed through an Object called "PublishSubscribe" that ... ComponentOf the Server Object defined in OPC 10000-5 . HasTypeDefinition ObjectType PubSubKeyServiceType Conformance Units PubSub Model
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  8.5.4 AddSecurityGroupFolder Method
  SecurityGroupFolderType Object . The Client shall be authorized to modify the configuration for the PubSub functionality when invoking this Method on the Server . Signature AddSecurityGroupFolder ( [in] String Name, [out] NodeId SecurityGroupFolderNodeId ... ModellingRule HasProperty Variable InputArguments Argument[] PropertyType Mandatory HasProperty Variable OutputArguments Argument[] PropertyType Mandatory ConformanceUnits PubSub Model
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  8.5.5 RemoveSecurityGroupFolder Method
  contained SecurityGroupFolderType Objects . The Client shall be authorized to modify the configuration for the PubSub functionality when invoking this Method on the Server . Signature RemoveSecurityGroupFolder ( [in] NodeId SecurityGroupFolderNodeId ); Argument Description ... RemoveSecurityGroupFolder References NodeClass BrowseName DataType TypeDefinition ModellingRule HasProperty Variable InputArguments Argument[] PropertyType Mandatory ConformanceUnits PubSub Model
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  8.7.4 AddPushTargetFolder Method
  PubSubKeyPushTargetFolderType Object . The Client shall be authorized to modify the configuration for the PubSub functionality when invoking this Method on the Server . Signature AddPushTargetFolder ( [in] String Name, [out] NodeId PushTargetFolderNodeId ... ModellingRule HasProperty Variable InputArguments Argument[] PropertyType Mandatory HasProperty Variable OutputArguments Argument[] PropertyType Mandatory ConformanceUnits PubSub Model SKS Push
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  8.7.5 RemovePushTargetFolder Method
  contained PubSubKeyPushTargetFolderType Objects . The Client shall be authorized to modify the configuration for the PubSub functionality when invoking this Method on the Server . Signature RemovePushTargetFolder ( [in] NodeId PushTargetFolderNodeId ); Argument Description ... RemovePushTargetFolder References NodeClass BrowseName DataType TypeDefinition ModellingRule HasProperty Variable InputArguments Argument[] PropertyType Mandatory ConformanceUnits PubSub Model SKS Push
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  8.8 Security Key Service Roles
  management of SecurityGroups and PushTargets on an SKS. SecurityKeyServerAccess This Role allows a PubSub Application to access an SKS to pull keys. It is the default Role for pull ... different SecurityGroups . SecurityKeyServerPush This Role allows an SKS to push security keys to PubSub Applications . This includes executing methods related to PubSub security
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.1 General
  depicts the ObjectTypes of the message and transport protocol mapping independent part of the PubSub configuration model, their main components and their relations. Figure 42 - PubSub configuration model overview ... instance of the PublishSubscribeType with the name PublishSubscribe represents the root Object for all PubSub related Objects . It manages a list of PubSubConnectionType Objects and the PublishedDataSetType Objects through
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.2 Configuration behaviours
  Server and shall be available after a restart of the OPC UA Server . PubSub components are not persisted, if the component has the optional NotPersisted property set with a value ... true. The PubSub configuration properties are defined in 6.2.2 . Add, modify and remove operations for all PubSub configuration elements including DataSets and security key exchange configuration can be executed
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.3.1 Overview
  PublishSubscribe Object Types overview The PublishSubscribe Object is the root node for all PubSub related configuration Objects . It is an instance of the PublishSubscribeType and a component of the Server ... Object . The PublishSubscribeType contains the entry point for PublishedDataSet configuration, the entry point for PubSub connections. In addition, it provides Methods for connection management
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.3.2 PublishSubscribeType
  PublishSubscribeTypeAn instance of this ObjectType represents the root Object for all PubSub related configuration and metadata Objects . The one instance of this ObjectType that represents the root Object ... HasProperty Variable DefaultSecurityKeyServices Endpoint‌Description[] PropertyType Optional HasProperty Variable ConfigurationProperties KeyValuePair [] PropertyType Optional Conformance Units PubSub Model Base The PublishSubscribeType ObjectType is a concrete type and can be used directly
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.3.4 AddConnection Method (Deprecated)
  PublishSubscribe Object . The Client should be authorized to modify the configuration for the PubSub functionality when invoking this Method on the Server . Signature AddConnection ( [in] PubSubConnectionDataType Configuration, [out] NodeId ConnectionId ... ModellingRule HasProperty Variable InputArguments Argument[] PropertyType Mandatory HasProperty Variable OutputArguments Argument[] PropertyType Mandatory ConformanceUnits PubSub Model Base
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.3.5 RemoveConnection Method (Deprecated)
  Disabled . The Client should be authorized to modify the configuration for the PubSub functionality when invoking this Method on the Server . Signature RemoveConnection ( [in] NodeId ConnectionId ); Argument Description ConnectionId NodeId ... RemoveConnection References NodeClass BrowseName DataType TypeDefinition ModellingRule HasProperty Variable InputArguments Argument[] PropertyType Mandatory ConformanceUnits PubSub Model Base
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.3.7.1 PubSubConfigurationType
  PubSubConfigurationType This ObjectType represents a FileType the can be used to access a PubSub configuration. The PubSubConfigurationType is formally defined in Table 238 . The PubSubConfigurationType file is a UA Binary ... Client opens the file for writing the Server will not actually update the PubSub configuration until the CloseAndUpdate Method is called. Simply calling Close will discard the updates. When
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.3.7.4 PubSubConfigurationValueDataType
  configuration element in the related PubSubConfiguration2DataType Structure. Name String The name of the referenced PubSub configuration element. Identifier BaseDataType The identifier value used for the referenced element in the PubSub ... NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of Structure defined in OPC 10000-5 . ConformanceUnits PubSub Model Base
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.3.7.5 ReserveIds Method
  ReserveIds Method This Method reserves unique WriterGroupIds and DataSetWriterIds to allow PubSub configuration applications to apply unique Ids to new PubSub configuration elements when preparing a update to the PubSub ... Server shall ensure that the IDs returned are not used in the current PubSub configuration or are not reserved yet. When a Client reserves IDs, these reservations are valid while
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.3.7.6 CloseAndUpdate Method
  CloseAndUpdate Method This Method closes the file and applies the changes to the PubSub configuration as defined in the ConfigurationReferences argument. It can only be called if the file ... writing. If the Close Method is called any cached data is discarded and the PubSub configuration is not changed. The file content shall be a UABinaryFileDataType with a PubSubConfiguration2DataType
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.4.2.3 AddExtensionField Method
  Object ExtensionFields . The Client shall be authorized to modify the configuration for the PubSub functionality when invoking this Method on the Server . Signature AddExtensionField ( [in] QualifiedName FieldName, [in] BaseDataType FieldValue ... ModellingRule HasProperty Variable InputArguments Argument[] PropertyType Mandatory HasProperty Variable OutputArguments Argument[] PropertyType Mandatory ConformanceUnits PubSub Model Base
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.4.2.4 RemoveExtensionField Method
  Object ExtensionFields . The Client shall be authorized to modify the configuration for the PubSub functionality when invoking this Method on the Server . Signature RemoveExtensionField ( [in] NodeId FieldId ); Argument Description FieldId ... RemoveExtensionField References NodeClass BrowseName DataType TypeDefinition ModellingRule HasProperty Variable InputArguments Argument[] PropertyType Mandatory ConformanceUnits PubSub Model Base
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.4.3.2 AddVariables Method
  defined in 6.2.3.2.6 . The Client shall be authorized to modify the configuration for the PubSub functionality when invoking this Method on the Server . Signature AddVariables ( [in] ConfigurationVersionDataType ConfigurationVersion, [in] String ... ModellingRule HasProperty Variable InputArguments Argument[] PropertyType Mandatory HasProperty Variable OutputArguments Argument[] PropertyType Mandatory ConformanceUnits PubSub Model PublishedDataSet
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.4.3.3 RemoveVariables Method
  shall be preserved. The Client shall be authorized to modify the configuration for the PubSub functionality when invoking this Method on the Server . Signature RemoveVariables ( [in] ConfigurationVersionDataType ConfigurationVersion, [in] UInt32 ... ModellingRule HasProperty Variable InputArguments Argument[] PropertyType Mandatory HasProperty Variable OutputArguments Argument[] PropertyType Mandatory ConformanceUnits PubSub Model PublishedDataSet
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.4.4.2 ModifyFieldSelection Method
  PublishedEventsType Object . The Client shall be authorized to modify the configuration for the PubSub functionality when invoking this Method on the Server . Signature ModifyFieldSelection ( [in] ConfigurationVersionDataType ConfigurationVersion, [in] String[] FieldNameAliases ... ModellingRule HasProperty Variable InputArguments Argument[] PropertyType Mandatory HasProperty Variable OutputArguments Argument[] PropertyType Mandatory ConformanceUnits PubSub Model PublishedDataSet Events
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.4.5.2 AddPublishedDataItems Method
  FieldNameAliases and FieldFlags . The Client shall be authorized to modify the configuration for the PubSub functionality when invoking this Method on the Server . Signature AddPublishedDataItems ( [in] String Name, [in] String ... ModellingRule HasProperty Variable InputArguments Argument[] PropertyType Mandatory HasProperty Variable OutputArguments Argument[] PropertyType Mandatory ConformanceUnits PubSub Model PublishedDataSet
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.4.5.3 AddPublishedEvents Method
  FieldNameAliases and FieldFlags . The Client shall be authorized to modify the configuration for the PubSub functionality when invoking this Method on the Server . Signature AddPublishedEvents ( [in] String Name, [in] NodeId ... ModellingRule HasProperty Variable InputArguments Argument[] PropertyType Mandatory HasProperty Variable OutputArguments Argument[] PropertyType Mandatory ConformanceUnits PubSub Model PublishedDataSet Events
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.4.5.4 AddPublishedDataItemsTemplate Method
  defined in 9.1.4.2 . The Client shall be authorized to modify the configuration for the PubSub functionality when invoking this Method on the Server . Signature AddPublishedDataItemsTemplate ( [in] String Name, [in] DataSetMetaDataType ... ModellingRule HasProperty Variable InputArguments Argument[] PropertyType Mandatory HasProperty Variable OutputArguments Argument[] PropertyType Mandatory ConformanceUnits PubSub Model PublishedDataSet
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.4.5.5 AddPublishedEventsTemplate Method
  defined in 9.1.4.2 . The Client shall be authorized to modify the configuration for the PubSub functionality when invoking this Method on the Server . Signature AddPublishedEventsTemplate ( [in] String Name, [in] DataSetMetaDataType ... ModellingRule HasProperty Variable InputArguments Argument[] PropertyType Mandatory HasProperty Variable OutputArguments Argument[] PropertyType Mandatory ConformanceUnits PubSub Model PublishedDataSet Events
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.4.5.6 RemovePublishedDataSet Method
  changed to Disabled . The Client shall be authorized to modify the configuration for the PubSub functionality when invoking this Method on the Server . Signature RemovePublishedDataSet ( [in] NodeId DataSetNodeId ); Argument Description ... RemovePublishedDataSet References NodeClass BrowseName DataType TypeDefinition ModellingRule HasProperty Variable InputArguments Argument[] PropertyType Mandatory ConformanceUnits PubSub Model PublishedDataSet
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.4.5.7 AddDataSetFolder Method
  DataSetFolderType Object . The Client shall be authorized to modify the configuration for the PubSub functionality when invoking this Method on the Server . Signature AddDataSetFolder ( [in] String Name, [out] NodeId DataSetFolderNodeId ... ModellingRule HasProperty Variable InputArguments Argument[] PropertyType Mandatory HasProperty Variable OutputArguments Argument[] PropertyType Mandatory ConformanceUnits PubSub Model PublishedDataSet
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.4.5.8 RemoveDataSetFolder Method
  changed to Disabled. The Client shall be authorized to modify the configuration for the PubSub functionality when invoking this Method on the Server . Signature RemoveDataSetFolder ( [in] NodeId DataSetFolderNodeId ); Argument Description ... RemoveDataSetFolder References NodeClass BrowseName DataType TypeDefinition ModellingRule HasProperty Variable InputArguments Argument[] PropertyType Mandatory ConformanceUnits PubSub Model PublishedDataSet
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.5.1 Overview
  Overview Figure 47 depicts the ObjectType for the PubSub connection model and its components and the relations to other parts of the model. Figure 47 - PubSubConnectionType overview
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.5.3 AddWriterGroup Method (Deprecated)
  PubSubConnection . The Client should be authorized to modify the configuration for the PubSub functionality when invoking this Method on the Server . Signature AddWriterGroup ( [in] WriterGroupDataType Configuration, [out] NodeId GroupId ); Argument ... ModellingRule HasProperty Variable InputArguments Argument[] PropertyType Mandatory HasProperty Variable OutputArguments Argument[] PropertyType Mandatory ConformanceUnits PubSub Model Base
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.5.4 AddReaderGroup Method (Deprecated)
  PubSubConnection . The Client should be authorized to modify the configuration for the PubSub functionality when invoking this Method on the Server . Signature AddReaderGroup ( [in] ReaderGroupDataType Configuration, [out] NodeId GroupId ); Argument ... ModellingRule HasProperty Variable InputArguments Argument[] PropertyType Mandatory HasProperty Variable OutputArguments Argument[] PropertyType Mandatory ConformanceUnits PubSub Model Base
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.5.5 RemoveGroup Method (Deprecated)
  Disabled . The Client should be authorized to modify the configuration for the PubSub functionality when invoking this Method on the Server . Signature RemoveGroup ( [in] NodeId GroupId ); Argument Description GroupId NodeId ... RemoveGroup References NodeClass BrowseName DataType TypeDefinition ModellingRule HasProperty Variable InputArguments Argument[] PropertyType Mandatory ConformanceUnits PubSub Model Base
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.6.1 Overview
  Overview Figure 48 depicts the ObjectType for the PubSub group model and its components and the relations to other parts of the model. Figure 48 - PubSubGroupType overview
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.6.2 PubSubGroupType
  PubSubGroupType This ObjectType is the abstract base type for Objects representing communication groupings for PubSub connections. The PubSubGroupType is formally defined in Table 275 . Table 275 - PubSubGroupType definition Attribute Value ... Mandatory HasProperty Variable GroupProperties KeyValuePair[] PropertyType Mandatory HasComponent Object Status PubSubStatusType Mandatory Conformance Units PubSub Model Base The SecurityMode is defined in 6.2.5.2 . The SecurityGroupId is defined
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.6.4 AddDataSetWriter Method (Deprecated)
  created DataSetWriter . The Client should be authorized to modify the configuration for the PubSub functionality when invoking this Method on the Server . Signature AddDataSetWriter ( [in] DataSetWriterDataType Configuration, [out] NodeId DataSetWriterNodeId ... ModellingRule HasProperty Variable InputArguments Argument[] PropertyType Mandatory HasProperty Variable OutputArguments Argument[] PropertyType Mandatory ConformanceUnits PubSub Model Base
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.6.5 RemoveDataSetWriter Method (Deprecated)
  removed DataSetWriter . The Client should be authorized to modify the configuration for the PubSub functionality when invoking this Method on the Server . Signature RemoveDataSetWriter ( [in] NodeId DataSetWriterNodeId ); Argument Description DataSetWriterNodeId ... RemoveDataSetWriter References NodeClass BrowseName DataType TypeDefinition ModellingRule HasProperty Variable InputArguments Argument[] PropertyType Mandatory ConformanceUnits PubSub Model Base
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.6.9 ReaderGroupType
  ReaderGroupType This ObjectType is a concrete type for Objects representing DataSetReader groupings for PubSub connections. The ReaderGroupType is formally defined in Table 282 . Table 282 - ReaderGroupType definition Attribute Value BrowseName ... Optional HasComponent Method RemoveDataSetReader Deprecated Method described in 9.1.6.11 . Optional Conformance Units PubSub Model Base The configured DataSetReaderType Objects are added as components to the instance of the group. DataSetReaderType
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.6.10 AddDataSetReader Method (Deprecated)
  ReaderGroup . The Client should be authorized to modify the configuration for the PubSub functionality when invoking this Method on the Server . Signature AddDataSetReader ( [in] DataSetReaderDataType Configuration, [out] NodeId DataSetReaderNodeId ); Argument ... ModellingRule HasProperty Variable InputArguments Argument[] PropertyType Mandatory HasProperty Variable OutputArguments Argument[] PropertyType Mandatory ConformanceUnits PubSub Model Base
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.6.11 RemoveDataSetReader Method (Deprecated)
  Object is removed. The Client should be authorized to modify the configuration for the PubSub functionality when invoking this Method on the Server . Signature RemoveDataSetReader ( [in] NodeId DataSetReaderNodeId ); Argument Description ... RemoveDataSetReader References NodeClass BrowseName DataType TypeDefinition ModellingRule HasProperty Variable InputArguments Argument[] PropertyType Mandatory ConformanceUnits PubSub Model Base
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.7.1 Overview
  Overview Figure 49 depicts the ObjectType for the PubSub DataSetWriter model and its components and the relations to other parts of the model. Figure 49 - DataSet Writer model overview
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.8.1 Overview
  Overview Figure 50 depicts the ObjectType for the PubSub DataSetReader model and its components and the relations to other parts of the model. Figure 50 - DataSet Reader model overview
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.8.5 CreateTargetVariables Method
  SubscribedDataSetType . The Client shall be authorized to modify the configuration for the PubSub functionality when invoking this Method on the Server . Signature CreateTargetVariables ( [in] ConfigurationVersionDataType ConfigurationVersion, [in] FieldTargetDataType[] TargetVariablesToAdd ... ModellingRule HasProperty Variable InputArguments Argument[] PropertyType Mandatory HasProperty Variable OutputArguments Argument[] PropertyType Mandatory ConformanceUnits PubSub Model SubscribedDataSet
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.8.6 CreateDataSetMirror Method
  SubscribedDataSetMirrorType instance. The Client shall be authorized to modify the configuration for the PubSub functionality when invoking this Method on the Server . Signature CreateDataSetMirror ( [in] String ParentNodeName, [in] RolePermissionType[] RolePermissions ... ModellingRule HasProperty Variable InputArguments Argument[] PropertyType Mandatory HasProperty Variable OutputArguments Argument[] PropertyType Mandatory ConformanceUnits PubSub Model SubscribedDataSet Mirror
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.9.2.2 AddTargetVariables Method
  TargetVariablesType Object . The Client shall be authorized to modify the configuration for the PubSub functionality when invoking this Method on the Server . Signature AddTargetVariables ( [in] ConfigurationVersionDataType ConfigurationVersion, [in] FieldTargetDataType[] TargetVariablesToAdd ... ModellingRule HasProperty Variable InputArguments Argument[] PropertyType Mandatory HasProperty Variable OutputArguments Argument[] PropertyType Mandatory ConformanceUnits PubSub Model SubscribedDataSet
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.9.2.3 RemoveTargetVariables Method
  TargetVariablesType Object . The Client shall be authorized to modify the configuration for the PubSub functionality when invoking this Method on the Server . Signature RemoveTargetVariables ( [in] ConfigurationVersionDataType ConfigurationVersion, [in] UInt32[] TargetsToRemove ... ModellingRule HasProperty Variable InputArguments Argument[] PropertyType Mandatory HasProperty Variable OutputArguments Argument[] PropertyType Mandatory ConformanceUnits PubSub Model SubscribedDataSet
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.9.4.2 AddSubscribedDataSet Method
  DataSet Folder . The Client shall be authorized to modify the configuration for the PubSub functionality when invoking this Method on the Server . Signature AddSubscribedDataSet ( [in] StandaloneSubscribedDataSetDataType SubscribedDataSet, [out] NodeId SubscribedDataSetNodeId ... ModellingRule HasProperty Variable InputArguments Argument[] PropertyType Mandatory HasProperty Variable OutputArguments Argument[] PropertyType Mandatory ConformanceUnits PubSub Model SubscribedDataSet Standalone
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.9.4.3 RemoveSubscribedDataSet Method
  removed too. The Client shall be authorized to modify the configuration for the PubSub functionality when invoking this Method on the Server . Signature RemoveSubscribedDataSet ( [in] NodeId SubscribedDataSetNodeId ); Argument Description SubscribedDataSetNodeId ... RemoveSubscribedDataSet References NodeClass BrowseName DataType TypeDefinition ModellingRule HasProperty Variable InputArguments Argument[] PropertyType Mandatory ConformanceUnits PubSub Model SubscribedDataSet Standalone
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.9.4.4 AddDataSetFolder Method
  SubscribedDataSetFolderType Object . The Client shall be authorized to modify the configuration for the PubSub functionality when invoking this Method on the Server . Signature AddDataSetFolder ( [in] String Name, [out] NodeId DataSetFolderNodeId ... ModellingRule HasProperty Variable InputArguments Argument[] PropertyType Mandatory HasProperty Variable OutputArguments Argument[] PropertyType Mandatory ConformanceUnits PubSub Model SubscribedDataSet Standalone
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.9.4.5 RemoveDataSetFolder Method
  changed to Disabled . The Client shall be authorized to modify the configuration for the PubSub functionality when invoking this Method on the Server . Signature RemoveDataSetFolder ( [in] NodeId DataSetFolderNodeId ); Argument Description ... RemoveDataSetFolder References NodeClass BrowseName DataType TypeDefinition ModellingRule HasProperty Variable InputArguments Argument[] PropertyType Mandatory ConformanceUnits PubSub Model SubscribedDataSet Standalone
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.10.1 PubSubStatusType
  PubSubStatusType This ObjectType is used to indicate and change the status of a PubSub Object like PubSubConnection, DataSetWriter or DataSetReader . The PubSubStatusType is formally defined in Table 307 . Table ... Enable Defined in 9.1.10.2 . Optional HasComponent Method Disable Defined in 9.1.10.3 . Optional Conformance Units PubSub Model Base The State Variable provides the current operational state of the PubSub Object
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.10.2 Enable Method
  Enable Method This Method is used to enable a configured PubSub Object . The related state machine and the transitions triggered by a successful call to this Method are defined ... Disabled . The Client shall be authorized to modify the configuration for the PubSub functionality when invoking this Method on the Server . Signature Enable (); Method Result Codes ResultCode Description Bad_InvalidState
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.10.3 Disable Method
  Disable Method This Method is used to disable a PubSub Object . The related state machine and the transitions triggered by a successful call to this Method are defined ... State is Disabled . The Client shall be authorized to modify the configuration for the PubSub functionality when invoking this Method on the Server . Signature Disable (); Method Result Codes ResultCode Description
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.11.1 General
  General The following types are used to expose diagnostics information in the PubSub information model. Each level of the PubSub hierarchy shall contain its own diagnostics element in a standardized ... overview over the proposed diagnostics architecture is given in Figure 51 . Figure 51 - PubSub Diagnostics overview Figure 52 shows the structure of a Variable which holds a diagnostics counter with
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.11.2 PubSubDiagnosticsType
  BaseDataVariableType Mandatory HasComponent Object Counters BaseObjectType Mandatory HasComponent Object LiveValues BaseObjectType Mandatory Conformance Units PubSub Model Diagnostics The DiagnosticsLevel Variable configures the current diagnostics level used for the Object ... with classification Error . The SubError Variable indicates if any statistics Object of the next PubSub layer Objects shows a value > 0 in TotalError . The Object Counters contains all diagnostics
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.11.3 Reset Method
  initial value. The Client shall be authorized to modify the configuration for the PubSub functionality when invoking this Method on the Server . Signature Reset (); Method Result Codes ResultCode Description ... Reset Method . Table 312 - Reset Method AddressSpace definition Attribute Value BrowseName Reset ConformanceUnits PubSub Model Diagnostics
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.11.4 DiagnosticsLevel
  DiagnosticsLevel PubSub diagnostics are intended to assure users about the correct operation of a PubSub system and to help in the discovery of potential faults. Depending on the situation ... minimum diagnostic feature set that can be expected on any device that supports PubSub diagnostics at all. Advanced 1 Diagnostic objects related to exceptional behaviour are contained in the Advanced
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.12.1 PubSubCapabilitiesType
  PubSubCapabilitiesType This ObjectType is used to indicate the configuration capabilities of the PubSub functionality in the OPC UA Application . The PubSubCapabilitiesType is formally defined in Table 332 . Table 332 - PubSubCapabilitiesType ... HasProperty Variable SupportSecurityKeyPush Boolean PropertyType Optional HasProperty Variable SupportSecurityKeyServer Boolean PropertyType Optional Conformance Units PubSub Model Base The maximum numbers of objects related to configuration capabilities are expected
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.12.2 Supported configuration properties
  Supported configuration properties The PubSub components have KeyValuePair arrays for additional configuration property lists. These optional configuration properties extend the configuration parameters defined for the different PubSub components. A configuration
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  A.2.2.1 Motivation
  A.2.2.1 Motivation In PubSub use cases with dynamically changing message layouts or Event based DataSetMessages, the number and ordering of DataSetMessages within different NetworkMessages can change arbitrarily. The header layouts
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  C.1 Overview
  functionality available in the Client Server communication model with the data distribution mechanism of PubSub . See OPC 10000-1 for an overview of the complete functionality available with the Client
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  C.3 Publish-Subscribe
  Publish-Subscribe With PubSub , OPC UA Applications do not directly exchange requests and responses. Instead, Publishers send messages to a Message Oriented Middleware , without knowledge of what, if any, Subscribers ... forward the data to one or more receivers. Figure C.2 - Publish Subscribe model overview PubSub is used to communicate messages between different system components without these components having to know
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  C.4 Synergy of models
  Synergy of models PubSub and Client Server are both based on the OPC UA Information Model . PubSub therefore can easily be integrated into OPC UA Servers and OPC UA Clients ... information) and a Subscriber is often an OPC UA Client . Above all, the PubSub Information Model for configuration (see 9 ) promotes the configuration of Publishers and Subscribers using
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  4.3 Features
  Runs on top of: OPC UA Client/Server with the Method Service Set . OPC UA PubSub . From an architectural point of view: easy extensibility for other ways of communication. goal
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  5.4 Safety communication layer structure
  communication layer which are specific for the OPC UA communication Service in use, i.e. PubSub or Client/Server . Therefore, the remaining parts of the safety communication layer can be implemented independent ... implemented using an OPC UA Client calling the Method provided by the SafetyProvider . PubSub : The SafetyProvider publishes the ResponseSPDU and subscribes to the RequestSPDU . The SafetyConsumer publishes the RequestSPDU
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  6.2.2.1 SafetyACSet Object
  Client with the OPC UA Service Call . [RQ6.3b] For implementations supporting OPC UA PubSub , the OPC UA Object SafetyPDUs with its Properties RequestSPDU and ResponseSPDU shall be used. RequestSPDU ... response" refer to the behaviour on the layer of this document. Within the PubSub context, both requests and responses are realized by repeatedly publishing and subscribing Messages , see Figure
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  6.2.4 SafetyProvider version
  when using Client/Server communication or RequestSPDUV2DataType and ResponseSPDUV2DataType for the SPDU DataTypes when using PubSub communication), allowing a SafetyProvider to implement multiple versions of this document at the same time
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  6.3.3.3 SPI of SafetyProvider
  indicates whether the SafetyProvider has implemented the necessary publishers and subscribers for OPC UA PubSub communication (see 5.4 ): 1: OPC UA PubSub communication is implemented. 0: OPC UA PubSub communication
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  6.3.4.4 SPI of the SafetyConsumer
  indicates whether the SafetyConsumer has implemented the necessary publishers and subscribers for OPC UA PubSub communication (see 5.4 ): 1: OPC UA PubSub communication is implemented. 0: OPC UA PubSub communication
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  7.2.2.2 SafetyProvider and SafetyConsumer Sequence diagram
  requests and responses with SafetyData for this document using OPC UA Client/Server and PubSub communication mechanisms, respectively. The figures show selected scenarios only and are therefore informative. Figure 13 (informative ... stack (e.g. when using Client/Server , or by choosing a higher update rate for PubSub ). The dashed lines therefore are not part of this document, but rather symbolize the repeated sending
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  7.2.2.3 Duration of demand
  SafetyProvider with ResponseSPDUs which contain the initially returned value. This is the case for PubSub communication and is a choice for Client/Server communication, see RQ7.11. In this case, the SafetyProvider
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  7.2.2.4 SafetyProvider state diagram
  detection of a changed RequestSPDU by the OPC UA Mapper in the case of PubSub communication. In case of several possible transitions, so-called guard conditions (refer
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  10.3 Index of requirements (informative)
  Usage of Call Service for Client/Server 6.2.2.1 SafetyACSet Object RQ6.3b Usage of SafetyPDUs for PubSub 6.2.2.1 SafetyACSet Object RQ6.4 Provide SPDUs for diagnostics in Method ReadSafetyDiagnostics 6.2.2.1 SafetyACSet Object RQ6.5
• OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names
  5 AliasNames Information Model overview
  Annex B . The GDS functionality for AliasNames is formally defined in Annex C . The PubSub Alias Update header layout is formally defined in Annex D . Figure 2 - AliasNames Example
• OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names
  A.2 AliasNames used within a single Server
  available via a standardized naming scheme. The model also includes a configuration for a PubSub DataSet (see OPC 10000-14 ) that provides the Variables defined in the well. The AliasName
• OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names
  D.1.2 PubSub multicast messages
  D.1.2 PubSub multicast messages With this optional extension, the Server shall be configured to be a Publisher with a fixed DataSet message sent to a multicast address. The DataSet shall ... that an aggregating Server or GDS does not rely only on data delta frames, PubSub is not a guaranteed delivery system, so a data delta frame message could be missed
• OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names
  D.1.3 PubSub AliasName Notification Configuration
  D.1.3 PubSub AliasName Notification Configuration The setting for a PubSub AliasName Publisher are fixed as defined in D.2 . Only the following items can be changed as part of configuring ... published messages . This flag can be used to enable the Servers AliasName PubSub Notifications feature. A Server that supports this feature would typically have this feature pre-configured, allowing notification
• OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names
  D.3.1 Overview
  Overview This layout is specially configured for AliasName update messages. For additional detail on PubSub and header layouts
• OPC-10000-18 – OPC Unified Architecture - Part 18: Role-Based Security
  4.4.3 IdentityMappingRuleType
  Token . For example, the Role "subscriber" may only be allowed to access PubSub related Nodes . If the issuedTokenType of the Access Token is " http://opcfoundation.org/UA/UserToken#JWT"
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  4.2 Read Access to the SerializationValue
  generated (serialized) when requested by the Read Service , by a Subscription or in PubSub publishing
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  5.3 Semantic Property handling
  Semantic Property handling Especially in OPC UA PubSub scenarios, the transmission of semantic Properties like "EngineeringUnits", "AccuracyDomain" and "PeMeasurementID" along with actual values ... SemanticsChanged bit in the StatusCodes returned as part of data change Notifications . In PubSub scenarios, if the metadata of the subscribed DataSet changes, the Client receives a new ConfigurationVersion
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  6.3.2 SerializedData Variable
  only generated (serialized) when requested by the Read Service , by a Subscription or in PubSub publishing. The SerializationValue is typically read-only. If the Server supports write access, the Client ... Attribute of the SerializedData Variable shall refer to this new DataType . In case of PubSub , a change of the DataType NodeId causes a change of the metadata. Servers
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  6.3.7 CustomMetaDataProperties Property
  enhancement of the DataSetMetaData if the SerializedData Variable is serialized in a PubSub scenario. If the SerializedData Variable is used in a published DataSet , the KeyValuePairs of the CustomMetaDataProperties Property
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  6.3.8 CustomMetaDataRef Property
  Properties KeyValuePair array in the FieldMetaData Structure . Note: As all metadata created by the PubSub mechanism are omitted, the metadata does not contain type information
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  A.2 RIO Channel Group Configuration
  RawData field encoding (see OPC 10000-14 ) in a PubSub scenario. The Enumeration Values are encoded as string literals as specified in OPC 10000-6 . Figure A.2 - JSON encoding
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  A.3 RIO Channel Process Values
  RawData field encoding (see OPC 10000-14 ) in a PubSub scenario. In Figure A.3 the details of the generated QualifierValueStructureDataType structures are not shown in the table visualizing the nested
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  A.4 Energy Measurement Values
  RawData field encoding (see OPC 10000-14 ) in a PubSub scenario. Figure A.4 - PROFIenergy Energy Measurement Values
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  A.5 Semantic Property Metadata in PubSub Scenarios
  Semantic Property Metadata in PubSub Scenarios Figure A.5 shows how semantic Properties (see 5.3 also) can be added to the FieldMetaData structure (see OPC 10000-14 ) describing the SerializedData Variable ... well as to the MeasurementValueType Variables . The metadata can be conveyed to a PubSub Subscriber by coding this information into the Properties field of the FieldMetaData structure
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  A.7 Combining SerializationScopes
  RawData field encoding (see OPC 10000-14 ) in a PubSub scenario. If the StatusCode of the "MeasurementY1" Variable Value is Good , an empty "Status" is generated
• OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts
  1 Scope
  exchange process and configuration/parameterisation data (non-safety and safety) using OPC UA PubSub in combination with UAFX Connections and basic diagnostics. A future version of the UAFX specifications is expected
• OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts
  5.4.4 Security configuration
  Figure 5 . The security policy contains, amongst others, certificates, roles, and user management. For PubSub , this includes the configuration of the SecurityKeyServer (see OPC 10000-14 ). The Security Administrator might
• OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts
  6.2 UAFX Information Model
  applications. These communication concepts utilise the communication models defined in OPC UA, such as PubSub or Client Server 1 . The UAFX Information Model is based on the basic building blocks ... exchange of event information. Connections are mapped to a communication model such as PubSub or Client Server and different QoS classes in the application configuration. OPC 10000-81 formally describes
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  1 Scope
  complete overview, see OPC 10000-80 . This initial scope includes Controller-to-Controller using PubSub for data exchange. A future release will include Controller-to-Device and Device-to-Device
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.5.3 Establishing and closing Connections
  logical connection, communication model-specific properties for the utilised OPC UA communication model (e.g., PubSub or Client Server [future]). For more details on the ConnectionConfigurationSetType, see 6.8 . For details
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.5.4.2 Operation
  data reception. This revision of the specification supports logical connections that utilise the PubSub communication model and hence builds on the usage of either DataSetMessages or heartbeat messages
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.5.6.1 Overview
  data by utilising OPC UA communication models. This revision of the specification supports the PubSub communication model as defined in OPC 10000-14 . Future revisions will support the Client Server
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.5.6.2.1 Overview
  Overview This clause illustrates how Connections utilise the PubSub communication model, focusing on three use cases relevant in the context of industrial automation and the design of AutomationComponents . These
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.5.6.2.2 Single Connection using unicast network messages
  PubSubConnectionEndpoint (Con_A1 and Con_B1), which references a DataSetReader and a DataSetWriter . The PubSub instances are configured to exchange data between AutomationComponents AC_A and AC_B using unicast
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.5.6.2.3 Multiple Connections using unicast network messages
  DataSetWriter (and DataSetReader) that is located under the same WriterGroup (and ReaderGroup) . The PubSub instances are configured to exchange data between AC_A and AC_B using unicast NetworkMessages . This
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.5.6.2.5 DataSetMetaData
  This can result in misinterpretation of the exchanged data. To prevent this error scenario, PubSub provides the DataSetMetaData . DataSetMetaData describes the content and semantics of a DataSet . In addition
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.2.4.2 EstablishConnections signature
  inconsistent. Bad_ResourceUnavailable The Server does not have enough resources to add the entire PubSub configuration. Bad_InvalidState The current State of the Object does not allow a configuration change
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.2.4.3.4.2 PubSub
  PubSub For a PubSub communication model, a structure of type PubSubReserveCommunicationIds2DataType (see 10.43.4 ) shall be used. The EstablishConnections implementation shall reserve the requested number of IDs for both WriterGroups
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.2.4.3.9.2 PubSub
  PubSub The communication configuration applied in the case of a PubSub communication model is a structure of the type PubSubCommunicationConfigurationDataType (see 10.10.3 ). The result of applying the communication configuration ... case of a PubSub communication model is a structure of the type PubSubCommunicationConfigurationResultDataType (see 10.11.3 ). The EstablishConnections implementation shall process the supplied PubSubConfiguration with RequireCompleteUpdate and ConfigurationReferences in an atomic
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.2.5.2 CloseConnections behaviour
  atomic operation. For additional details on ConnectionEndpoints, see 6.6 , and PubSubConnectionEndpoints , see 6.6.3 . If PubSub is used as the communication model for a ConnectionEndpoint , the Method implementation shall only disable
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.4.4 InputsFolderType
  nested < InputGroup > can be used to help accomplish this. When using PubSub for periodic data with a fixed layout, Strings , ByteStrings, and variable-size arrays can cause problems ... data packet, the fixed size of the data packet cannot be calculated. If using PubSub periodic data with a fixed layout, then the following apply: Any Variables that are included
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.4.5 OutputsFolderType
  nested < OutputGroup > can be used to help accomplish this. When using PubSub for periodic data with a fixed layout, Strings , ByteStrings, and variable-size arrays can cause problems ... data packet, the fixed size of the data packet cannot be calculated. If using PubSub periodic data with a fixed layout, then the following apply: Any Variables that are included
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.5.2 ControlGroupType definition
  part of the FunctionalEntity model and are independent of any communication model ( Client Server , PubSub , etc.). A ControlGroup is used to identify the usage of parts of the FunctionalEntity . ControlGroups
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.6.1 Overview
  communication model used for exchange. Communication models can be Client Server or PubSub . This type specifies the exchanged Variables and contains the status of the Connection . Subtypes of ConnectionEndpointType provide ... PubSubConnectionEndpointType to represent the exchanged Variables , as well as corresponding References to the PubSub Information Model . Figure 28 - Illustration of a Connection between FunctionalEntities
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.6.3 PubSubConnectionEndpointType definition
  extends the abstract ConnectionEndpointType with behaviour that is specific to the OPC UA PubSub communication model. The PubSubConnectionEndpointType is illustrated in Figure 30 . Figure 30 - PubSubConnectionEndpointType illustration The PubSubConnectionEndpointType ... ConnectionEndpointType HasComponent Variable 3:Mode 2:PubSubConnectionEndpointModeEnum 0:BaseDataVariableType M ConformanceUnits UAFX ConnectionEndpoint PubSub Table 76 - PubSubConnectionEndpointType additional References SourceBrowsePath Reference Type IsForward TargetBrowsePath 3:ToDataSetReader True 0:Objects
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.7.3.2 Establishing Connections
  SetCommunicationConfigurationCmd Set communication configuration specific to the communication model utilised for data exchange (e.g., PubSub ). The argument CommunicationConfigurations that is passed for this command is constructed out of the instance
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.7.5.3.1 ActionEstablishConnectionsEnabled / ActionEstablishConnectionsDisabled / ActionEstablishConnections
  state of the configuration elements (e.g., the value of the Enabled flag for PubSub configuration elements), parts of the communication model may be enabled, and others may be disabled. This
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.8.2 ConnectionConfigurationSetType definition
  details, see 6.7.4 ). SecurityKeyServerAddress defines the location of the SKS to be used for PubSub security configuration of this ConnectionConfigurationSet . For a formal definition, see 9.3 . NOTE 1   Depending ... SecurityGroups and PubSubPushKeyTargets define the configuration information to be applied to the SKS for PubSub security configuration of the ConnectionConfigurationSet . NOTE 2   For an overview of how to configure
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.12.2 ConnectionEndpointParameterType definition
  required information related to this preconfigured PublishedDataSet from the UA Publisher's exposed PubSub configuration. The Subscriber does not need to expose or utilise all variables that are being published ... obtain any required information related to this preconfigured StandaloneSubscribedDataSet from the UA Subscribers exposed PubSub configuration. The Publisher is required to provide all data in the StandaloneSubscribedDataSet
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.13.2 CommunicationFlowConfigurationType definition
  PubSubCommunicationFlowConfigurationType Defined in 6.13.3 ConformanceUnits UAFX ConnectionManager Base PubSubCommunicationFlowConfigurationType indicates the usage of PubSub as the communication model for the Connections . It is formally defined in 6.13.3 . ClientServerCommunicationFlowConfigurationType
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.16.1 Overview
  Figure 47 - CommunicationModelConfigurationType illustration PubSubCommunicationModelConfigurationType provides the configuration data specific to the usage of PubSub as the communication model for the Connections . It is formally defined in 6.16.3 . ClientServerCommunicationModelConfigurationType indicates
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.16.3.1 Overview
  Overview The PubSubCommunicationModelConfigurationType defines the communication model-related configuration information for the usage of PubSub as the communication model (see OPC 10000-14 ). The PubSubCommunicationModelConfigurationType is illustrated in Figure
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.16.3.2 PubSubCommunicationModelConfigurationType definition
  PubSubConfigurationValueDataType[] 0:BaseDataVariableType M ConformanceUnits UAFX ConnectionManager PubSubCommunicationModelConfiguration The PubSubConfiguration modifies the existing PubSub configuration on the addressed Server when establishing Connections . The PubSubConfiguration2DataType is defined ... other. It also allows any Client to establish Connections . An AutomationComponent may even receive PubSub configuration (unrelated to OPC UA FX) via the corresponding Methods exposed in the PubSub configuration
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  10.10.3 PubSubCommunicationConfigurationDataType
  PubSubCommunicationConfigurationDataType The PubSubCommunicationConfigurationDataType contains configuration information for the PubSub communication model. It is formally defined in Table 140 . Table 140 - PubSubCommunicationConfigurationDataType structure Name Type Description PubSubCommunicationConfigurationDataType Structure Subtype of CommunicationConfigurationDataType ... False References NodeClass BrowseName IsAbstract Description Subtype of the 2:CommunicationConfigurationDataType ConformanceUnits UAFX AutomationComponent PubSub Connections UAFX ConnectionManager PubSubCommunicationFlowConfiguration
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  10.13.3 PubSubCommunicationLinkConfigurationDataType
  configuration of references between a ConnectionEndpoint and a DataSetReader and/or a DataSetWriter . NOTE   The PubSub configuration elements, including the DataSetReader and/or DataSetWriter to be used for the ConnectionEndpoints, are created ... References NodeClass BrowseName DataType TypeDefinition Other Subtype of the 2:CommunicationLinkConfigurationDataType ConformanceUnits UAFX AutomationComponent PubSub Connections UAFX ConnectionManager Base
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  13.4 ConnectionManager and Security Key Server (SKS)
  Security Key Server (SKS) If a logical connection is configured to use secure PubSub communication, then a Security Key Server is required. An SKS is described in detail
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  C.1 OPC UA Safety Information Model
  Safety defines how to exchange safety data between AutomationComponents using either Client Server or PubSub as the underlying OPC UA communication model. Client Server support for logical connections will ... specified in a future version of this document. The usage of PubSub is assumed for the following text. As defined in OPC 10000-15 , the SafetyProvider (representing the source
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  E.2.1 Overview
  model information targeted for the AutomationComponent (i.e., SecurityGroups and PubSubKeyPushTargets are omitted). If using PubSub , a specific sequence of calls could be required (see E.2.2 ). If Connections require security (authorisation
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  E.2.2.1 For logical connections between two AutomationComponents
  E.2.2.1 For logical connections between two AutomationComponents For PubSub as a communication model, OPC 10000-14 requires certain configuration values (e.g., PublisherId , WriterGroupId , and DataSetWriterId ) to match the Publisher ... generating unique IDs by the AutomationComponent , either by providing a null ID when configuring PubSub or by reserving IDs. Assuming a simple example, where a ConnectionManager processes a ConnectionConfigurationSet containing
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  E.4.1 Overview
  clause describes the configuration settings for the connection types defined in Clause 5.5.1 using PubSub as a communication model. For simplicity, all samples describe a single logical connection contained ... multiple Connections , which could have different connection types. The examples provide illustrations of how PubSub communication can be configured . The configuration contains various settings that have an influence
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  E.4.7 PubSub DataSets
  E.4.7 PubSub DataSets This subclause provides an overview of PubSub communication options and the use of DataSets . For a complete description of PubSub communication, PubSub communication options, DataSets and DataSetMetaData ... please see OPC 10000-14 . PubSub communication has multiple options that are defined by Profiles . To see what is defined in UAFX for a controller or device, see the UAFX
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  E.6.1 Overview
  E.6.1 Overview If using PubSub as a communication model, the ConnectionConfigurationSet contains a PubSubConfiguration Variable for each AutomationComponent's CommunicationModelConfig that has a DataType that is a large structure. This ... EstablishConnections Method to provide the required information to the AutomationComponent to configure PubSub communication on that AutomationComponent . An OPC UA Client could adjust some information that is inside this data
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  F.1.3 ConnectionConfigurationSetConfDataType
  closed. False SecurityKeyServer 4:SecurityKeyServerAddressConfDataType The location of the SKS to be used for PubSub security configuration of this ConnectionConfigurationSet, including SecurityGroups and PubSubKeyPushTargets. If the optional SKS configuration
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  F.1.14 PubSubCommunicationModelConfigurationDataType
  Name Type Description PubSubCommunicationModelConfigurationDataType Structure Subtype of CommunicationModelConfigurationDataType defined in F.1.13 . PubSubConfiguration 0:PubSubConfiguration2DataType PubSub configuration for the addressed Server when establishing Connections. TranslationTable 4:NodeIdTranslationDataType[] NodeIds contained
• OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking
  4 Overview
  application layer model and the use of common UA communication services (e.g., Client Server , PubSub ), which specify mappings to the underlying network layer. The operation of UAFX in an IT/OT
• OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking
  5.3.2 HostName resolution using DNS
  used: with UA Client Server communications, such as during UAFX connection establishment, and PubSub communications to exchange the real-time data for a Connection . Figure 2 illustrates ... issuing the EstablishConnections Method . Figure 3 illustrates the use of DNS in conjunction with PubSub for controller-to-controller communications. Figure 3 - PubSub with DNS resolution In this case
• OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking
  5.6.1 Overview
  different kinds of communications. For example, the exchange of control data via OPC UA PubSub , connection establishment via OPC UA Client   Server , link-local communication, e.g., LLDP ... release , UAFX Stations can use Best Effort or priority-based QoS for OPC UA PubSub traffic. In addition, enhanced priority-based QoS can be achieved in the network using
• OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking
  5.6.2 Traffic Priority
  Network control 2 (gPTP, LLDP, loop prevention) 4 46 Green 4 (UA PubSub, see 6.5.4 ) 3 -1 Reserved 2 16 Connection establishment (UA Client Server 3 ), remote management 2 (NETCONF ... release is expected to allow UA Client Server QoS configuration in addition to UA PubSub. 4 "Green" corresponds to the OPC UA PriorityLabel opc.qos.lbl://green, which this release
• OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking
  5.6.4.5 Connection establishment and operation
  invoking a Method on the ConnectionManager as described in OPC 10000‑81 . Figure 11 - PubSub QoS and addressing configuration variables The ConnectionManager establishes Connections using the Connection configuration ... actual PCP and DSCP priority values to use for the corresponding OPC UA PubSub messages on the wire. Similarly, it uses the Address Variable in the WriterGroup to derive