Search

Scope: Core (OPC-10000-*) All specs

174 result(s) for Publisher

OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts

2.1.33 Publisher

Publisher entity sending NetworkMessages to a Message Oriented Middleware Note 1 to entry: A Publisher can be a native OPC UA Application or an application that only has knowledge about
OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts

2.1.13 DataSetMessage

NetworkMessage handed off to the Message Oriented Middleware (transport layer) for delivery by the Publisher . The Subscriber receives the DataSetMessage as the payload of a NetworkMessage from the Publisher with
OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts

2.1.22 NetworkMessage

header to facilitate delivery, routing, security, and filtering Note 1 to entry: The Publisher hands off the NetworkMessage to the Message Oriented Middleware (transport layer) to deliver DataSetMessages ... entry: The term message is used with various connotations in the messaging world. The Publisher might like to think of the message as an immutable payload handed
OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts

2.1.30 OPC UA Application

Services , or a Server , which performs those Services , or an OPC UA Publisher or an OPC UA Subscriber
OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts

5.3.7 Server to Server interactions

accomplished using the OPC UA PubSub model where each peer Application is both a Publisher and a Subscriber . Figure 6 extends the previous example and illustrates the chaining of Servers
OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts

5.5 Publish-Subscribe

these queues. The Broker may translate messages from the formal messaging protocol of the Publisher to the formal messaging protocol of the Subscriber . PubSub is used to communicate messages between ... different system components without these components having to know each other's identity. A Publisher is pre-configured with what data to send. There is no connection establishment between Publisher
OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts

5.6 Synergy of models

monitoring. OPC PubSub can easily be integrated into Servers and Clients . Quite typically, a Publisher will be a Server (the owner of information) and a Subscriber is often a Client ... depicts a single OPC UA Application that acts as both a Server and a Publisher . Figure 7 - Integrated ClientServer and PubSub models Nevertheless, the PubSub communication does not require such
OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model

3.1.12 Authentication

process that assures that the identity of an entity such as a Client , Server , Publisher or user can be verified
OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model

4.1 OPC UA security environment

different levels of security and different security infrastructure. For example, both Client - Server and Publisher - Subscriber communication is shown in Figure 1 . OPC UA also defines global services such
OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model

4.3.2.2 Message flooding

malformed Messages . For well-formed Messages , the attacker could be one in which the publisher is not a member of the SecurityGroup and one in which it is a member ... malformed Messages, an attacker could use a malicious Publisher that floods a network with malformed Messages in order to exhaust the system's resources. In general, Message flooding can impair
OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model

4.3.2.3 Resource Exhaustion

PubSub communications since no session or resources are allocated. For PubSub communication, the Publisher is not susceptible. In 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. Although the Publisher and Subscriber are not directly susceptible
OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model

4.3.2.4 Application Crashes

response that would cause the Client to crash. The attacker could also be a Publisher that issues a Message that would cause Subscribers to crash
OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model

4.3.4 Message spoofing

attacker could forge Message s from a Client or a Server or a Publisher where the messages are forged to attempt to appear to be from an application other that ... protocol stack. By spoofing Message s from a Client, a Server or Publisher , attackers can perform unauthorized operations and avoid detection of their activities. Message spoofing impacts Integrity , Authorization
OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model

4.3.11 Rogue Publisher

Rogue Publisher An attacker who builds a malicious OPC UA Publisher or installs an unauthorized instance of a genuine OPC UA Publisher in a system. The rogue Publisher could attempt ... masquerade as a legitimate UA Publisher or it could simply appear as a new Publisher in the system. A rogue Publisher impacts all security objectives except Integrity and Non-Repudiation
OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model

4.5.3.2 Broker-less

Subscribers ) in a SecurityGroup to share information. An SKS could be part of a Publisher or Subscriber . It could also be a centrally managed SKS that is part ... same rights. All applications must trust all other applications in the group. Any application ( Publisher or Subscriber ) in the group can publish a message and any application ( Publisher or Subscriber
OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model

4.6 SecurityPolicies

identified by a specific unique URI. To improve interoperability among vendors' products, Server and Publisher products implement these policies rather than define their own. Clients and Subscribers support the same
OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model

4.13 OPC UA security related Services

messages and also how to obtain the security keys required for message security. The Publisher will utilize the keys provided to secure the message. It will encrypt the body ... number of messages secured with the key. To obtain the required keys, the Publisher or Subscriber make use of Client - Server communication. The keys could also be obtained using session
OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model

5.1.10 Rogue Server or Publisher

Rogue Server or Publisher See 4.3.10 and 4.3.11 for a description of this threat. OPC UA Client applications counter the use of rogue Servers by validating Server ApplicationInstanceCertificates . There would ... messages to the Client . OPC UA Subscriber applications counter the effect of a rogue Publisher by validating the signature on the published messages
OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model

5.2.2 Application Authentication

SecurityKeyService (SKS). Although the application authentication is not directly between the Subscriber and the Publisher, the SKS ensures that only authenticated applications can obtain the keys used by the Publisher
OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model

5.2.4 Authorization

Authorization can be used as part of the key distribution (SKS). This allows the Publisher and SKS to restrict access to specific users
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.1.12 QualifiedName, NodeId and ExpandedNodeId String Encoding

that is used for all exchanges within that Session . Another example, is when a Publisher publishes DataSetMetadata messages, the NamespaceTable is provided as part of the message. However, there
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.4.1 General

ExtensionObject ) or BaseDataType (i.e. Variant ). OPC 10000-14 specifies the behaviour if a Publisher is misconfigured with metadata that uses abstract DataTypes
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services

Annex D Server Capability Identifiers (Normative)

Accepts reverse connect requests as defined in OPC 10000-6 . PUB Supports the Publisher Capabilities defined in OPC 10000-14 . PSC Supports the PubSub Configuration model defined
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

3.1.9 SecurityGroup

SecurityGroup grouping of security settings and security keys used to access messages from a Publisher Note 1 to entry: A SecurityGroup is an abstraction that represents the security settings ... security keys that can be used to access messages from a Publisher . A SecurityGroup is identified with a unique identifier called the SecurityGroupId . The SecurityGroupId is unique within the Security
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

4.1 Fields of application

Publishers and Subscribers are decoupled. The number of Subscribers receiving data from a Publisher does not influence the Publisher . This makes PubSub suitable for applications where location independence and/or scalability
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

4.3 Decoupling by use of middleware

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 ... these queues. The Broker may translate messages from the formal messaging protocol of the Publisher to the formal messaging protocol of the Subscriber
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

4.4 Synergy of models

easily be integrated into OPC UA Servers and OPC UA Clients . Quite typically, a Publisher will be an OPC UA Server (the owner of information) and a Subscriber is often
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.1 General

PubSub concepts. The DataSet constitutes the payload of messages provided by the Publisher and consumed by the Subscriber . The DataSet is described in 5.2 . The mapping to messages is described ... participating entities like Publisher and Subscriber are described in 5.4 . The abstract communication parameters are described in Clause 6 . The mapping of this model to concrete message and transport protocol
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.2.1 General

defined to represent any information, for example, they could be internal Variables in the Publisher , Events from the Publisher or collected by the Publisher , network data, or data from
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.2.2 DataSetClass

DataSetClass DataSets can be individual for a Publisher or they can be derived from a DataSetClass . Such a DataSetClass acts as template declaring the content of a DataSet . The DataSetClass
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.2.3 DataSetMetaData

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 the OPC UA configuration Methods defined ... 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 from the Publisher . The Subscriber
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.3.1 General

defines the term DataSetMessage to mean the application data (the payload) supplied by the Publisher and the term NetworkMessage to mean the message handed off and received from a specific
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.3.3 DataSetMessage

contain any information about the data acquisition or information source in the Publisher . Additional header information includes: DataSetWriterId Identifies the DataSetWriter and indirectly the PublishedDataSet. Sequence number A number that ... time period, a keep alive DataSetMessage is sent to signal the Subscribers that the Publisher is still alive. DataSetMessages are either sent cyclicly or acyclicly in a publishing interval. Acyclic
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.3.4 NetworkMessage

DataSetMessages and includes information shared between DataSetMessages . This information consists of: PublisherId Identifies the Publisher . Security data Only available for encodings that support message security. The relevant information is specified
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.3.5 Message security

encryption Signing and encryption Message security is end-to-end security (from Publisher to Subscriber ) and requires common knowledge of the cryptographic keys necessary to sign and encrypt ... Publisher side as well as validate signature and decrypt on the Subscriber side. The keys used for message security are managed in the context of a SecurityGroup . The basic concepts
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.3.7 SecurityGroup

between Roles and their access Permissions for a SecurityGroup . This mapping defines if a Publisher or Subscriber has access to the security keys of a SecurityGroup . The SKS is described ... with a unique identifier called the SecurityGroupId . It is unique within the SKS. A Publisher for its PublishedDataSets needs to know the SecurityGroupId . For Subscribers the SecurityGroupId is distributed
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 ... weather station, or a stock exchange. Commonly, a Publisher is also an OPC UA Server . For the abstract PubSub concepts, however, it is an arbitrary entity and should
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.4.1.2 Message sending

Message sending Figure 6 illustrates the process inside a Publisher when creating and sending messages and the parameters required to accomplish it. The components, like DataSet collection or DataSetWriter should ... considered abstract. They may not exist in every Publisher as independent entities. However, comparable processes need to exist to generate the OPC UA PubSub messages. Figure 6 - Publisher message sending
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.4.2.2 Message reception

interpreting messages and the parameter model required for accomplishing it. As for the Publisher , the components should be considered abstract. Figure 8 - Subscriber message reception sequence The Subscriber need ... decrypted and decoded. The security parameters are the same as for the Publisher . Each DataSetMessage of interest is passed on to a DataSetReader . Here, the DataSetMetaData is used to decode
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.4.4 Configuration Tool

Tool An OPC UA Application can be pre-configured to send messages as a Publisher but commonly it is required to configure the information to be included into messages ... configuration tool establishes the communication by selecting the Variables to be published in the Publisher and then configures the Subscriber to receive the messages from the Publisher and to select
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.4.5.1 General

Service (SKS) provides keys for message security that can be used by the Publisher to sign and encrypt NetworkMessages and by the Subscriber to verify the signature of NetworkMessages ... specifies the GetSecurityKeys Method . The GetSecurityKeys Method can be implemented by a Publisher or by a central SKS. In both cases, the well-known NodeIds for the PublishSubscribe Object
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.4.5.3 Key acquisition handshakes

acquisition handshakes The Publisher or Subscriber use keys provided by an SKS to secure messages exchanged via the Message Oriented Middleware . The handshake to pull the keys from ... Figure 11 - Handshake used to pull keys from SKS To pull keys, the Publisher or Subscriber creates an encrypted connection and provides credentials that allow it access to the SecurityGroup
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.4.6.2.2 Broker-less model with OPC UA UDP

PublishedDataSet which can be a list of sampled data items in the Publisher OPC UA Address Space . For each DataSet a DataSetMessage is created. The DataSetMessages are sent
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.4.6.3.1 General

broker Advantages of this model (partly depending on used Broker and its configuration) include: Publisher and Subscriber do not have to be directly addressable. They can be anywhere as long ... very large list of Subscribers , multiple networks or even chained Brokers or scalable Brokers . Publisher and Subscriber lifetimes do not have to overlap. The Publisher application can push NetworkMessage
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.4.6.3.2 Broker-based model

terms of the messaging protocols, the Broker is a messaging server (the OPC UA Publisher and the OPC UA Subscriber are messaging clients). The messaging protocols define how to connect ... message influence the Broker functionality. Figure 17 - Broker overview An OPC UA Publisher that publishes data may be configured through the PubSub configuration model. It contains one connection Object
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.1 Overview

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', 'message mapping ... data acquisition for the DataSets , the message generation and the sending on the Publisher side. These parameters need to be known on the Subscriber side to configure DataSetReaders
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.3.1 Overview

DataSetMessage is defined by the DataSetMetaData. This information is required for interoperability between Publisher and Subscriber . See 6.2.3.2 . The information source is only necessary for the configuration of the Publisher
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.3.2.2 DataTypeSchemaHeader

abstract types Number , UInteger , Integer or Enumeration shall be included in the DataSetMetaData . A Publisher should keep the namespaces array in the DataSetMetaData unchanged even if the order of namespaces ... changed in the OPC UA Server of the Publisher . A change of the namespace array in the DataSetMetaData requires a change to the MajorVersion in the DataSetMetaData . The Subscriber must
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.3.2.6 ConfigurationVersionDataType

decoding with a majorVersion that matches the majorVersion in DataSetMessages sent by the Publisher . Removing fields from the DataSet content, reordering fields, adding fields in between other fields ... majorVersion shall be updated. There can be situations where older configurations of a Publisher are loaded and changed with product-specific configuration tools. In this case the majorVersion shall
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.3.3 DataSetClassId

DataSetClassId DataSetMetaData may be specific to a single Publisher and a single selection of information or universal, e.g. defined by a standards organization or by a plant operator
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.3.4 ExtensionFields

with values to be included in the DataSet when the existing AddressSpace of the Publisher does not provide the necessary information. The ExtensionFields are represented as an array of KeyValuePair
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.3.5 PublishedDataSetDataType

human readable name. The name of the PublishedDataSet shall be unique in the Publisher . DataSetFolder String[] Optional path of the DataSet folder used to group PublishedDataSets where each entry
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.3.7.1 PublishedData

Duration A recommended rate of acquiring new values for change or deadband evaluation. A Publisher should use this value as hint for setting the internal sampling rate. The value
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.4.2 DataSetFieldContentMask

PubSub Parameters Discovery The DataSetFieldContentMask defines different options that influence the information flow from Publisher to Subscriber in the case of a Bad Value Status or other error situations. Figure ... parameters and the information flow from DataSet field to DataSetMessage creation on the Publisher side and the decoded DataSet field on the Subscriber side. The DataSetFieldContentMask controls the representation
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.5.4 SecurityKeyServices

message for a WriterGroup , the ApplicationType shall be set to SERVER even if the Publisher is configured for push. GatewayServerUri String Shall be null or empty. DiscoveryProfileUri String Shall
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.6.3 KeepAliveTime

KeepAliveTime The KeepAliveTime with DataType Duration defines the time in milliseconds until the Publisher sends a keep alive DataSetMessage in the case where no DataSetMessage was sent in this period
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.6.4 Priority

relative priority of the WriterGroup to all other WriterGroups across all PubSubConnections of the Publisher . If more than one WriterGroup needs to be processed, the priority number defines the order
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.6.5 LocaleIds

WriterGroup . The first LocaleId in the list has the highest priority. If the Publisher sends a localized String , the Publisher shall send the translation with the highest priority that ... include the LocaleId with the String . If no locale id is configured, the Publisher shall use any that it has. See OPC 10000-3 for more detail on LocaleId
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.7.1 PublisherId

PublisherId The PublisherId is a unique identifier for a Publisher within a Message Oriented Middleware . It can be included in sent NetworkMessage for identification or filtering. The value ... PublisherId is vendor specific. The PublisherId parameter is only relevant for the Publisher functionality inside a PubSubConnection . The filter setting on the Subscriber side is contained in the DataSetReader parameters
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.9.1 PublisherId

PublisherId The parameter PublisherId defines the Publisher to receive NetworkMessages from. If the value is null, the parameter shall be ignored and all received NetworkMessages pass the PublisherId filter. Valid
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.9.3 DataSetWriterId

DataSetWriterId The parameter DataSetWriterId with DataType UInt16 defines the DataSet selected in the Publisher for the DataSetReader. If the value is 0 (null), the parameter shall be ignored
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.9.4 DataSetMetaData

DataSetMetaData The parameter DataSetMetaData provides the information necessary to decode DataSetMessages from the Publisher . If the DataSetMetaData changes in the Publisher and the MajorVersion was changed, the DataSetReader needs
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.9.6 MessageReceiveTimeout

DataSetMessage , each received DataSetMessage is considered new. The MessageReceiveTimeout is related to the Publisher side parameters PublishingInterval , KeepAliveTime and KeyFrameCount
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.10.5 StandaloneSubscribedDataSetDataType

parameter is a null or empty String array. DataSetMetaData DataSetMetaDataType Defined in 6.2.9.4 . A Publisher must be configured to send DataSetMessages that comply with the DataSetMetaData in the standalone subscribed
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.11.1 Published data items

data items The configuration model defines different parameters that influence the information flow from Publisher to Subscriber in the case of a Bad Value Status or other error situations. Figure ... depicts the parameters and the information flow inside a Publisher and inside a Subscriber . The parameters and behaviour relevant for the encoding of a DataSetMessage on the Publisher side
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.12.2 SecurityGroupDataType

lifetime of a key in milliseconds. If the last available key expires and the Publisher does not receive a new key in two times the KeyLifetime it shall go into
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.12.4 PubSubConfiguration2DataType

configuration. The StandaloneSubscribedDataSetDataType is defined in 6.2.10.5 . DataSetClasses DataSetMeta‌DataType[] DataSetClasses supported by the Publisher . DefaultSecurityKeyServices EndpointDescription[] The default SecurityKeyServices used for the PubSub configuration. The value is as default
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.1.1.1 Relationship of Timing parameters

synchronized global clock, this clock shall be used as the time base for the Publisher and Subscriber . The beginning of a PublishingInterval shall be a multiple of the PublishingInterval relative ... select the possible start of a PublishingInterval . Figure 28 - Start of the periodic publisher execution The different timing offsets inside a PublishingInterval cycle on Publisher and Subscriber side are shown
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.1.1.3 DataSetOrdering

distribution even may change between each PublishingInterval . If DataSetOrdering is set to AscendingWriterId, the Publisher shall fill up each NetworkMessage with DataSets with an ascending order of the related DataSetWriterIds
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.1.1.5 SamplingOffset

negative value indicates that the optional parameter is not configured. In this case the Publisher shall calculate the time before the PublishingOffset that is necessary to create the NetworkMessage
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.1.3.1 General

parameters is 0, the position is not guaranteed to be static. NOTE A Publisher can only provide valid values for the parameters NetworkMessageNumber and DataSetOffset if the message mapping allows
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.1.3.3 ConfiguredSize

padded with bytes with value zero. In case it would be larger, the Publisher shall set bit 0 of the DataSetFlags1 to false to indicate that the DataSetMessage
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.1.4.7 PublishingInterval

PublishingInterval The PublishingInterval with DataType Duration indicates the rate the Publisher sends NetworkMessages related to the DataSet . The start time for the periodic execution of the Subscriber shall be calculated
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.1.4.9 ProcessingOffset

application in the Subscriber . The different timing offsets inside a PublishingInterval cycle on the Publisher and Subscriber sides are shown in Figure 29 . Any negative value indicates that the ProcessingOffset
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.4.1.6.4 Topic

parameter with DataType String contains the unique name of the data stream from the Publisher that contains the DataSetMessages of interest for the DataSetReader . The Topic is defined ... Publisher
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.4.2.2.1 ResourceUri

connection. The ResourceUri should uniquely identify a user and broker combination in a Publisher . An example for such a Uri is "mqtts://myuser@mydomain.com:8883". If null or empty
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.4.2.3.1 QueueName

DataType String specifies the queue in the Broker that receives NetworkMessages sent by the Publisher . This could be the name of a queue or topic defined in the Broker
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.4.2.5.1 QueueName

DataType String specifies the queue in the Broker that receives NetworkMessages sent by the Publisher for the DataSetWriter. This could be the name of a queue or topic defined
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.4.2.5.5 MetaDataQueueName

like UADP, the Subscriber needs access to the DataSetMetaData to process received DataSetMessages . The Publisher can provide the DataSetMetaData through a dedicated queue. The parameter MetaDataQueueName with the DataType String ... specifies the Broker queue that receives messages with DataSetMetaData sent by the Publisher for this DataSetWriter . This could be the name of a queue or topic defined in the Broker
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.4.2.6.1 QueueName

where the DataSetReader can receive NetworkMessages with the DataSet of interest sent by the Publisher . This could be the name of a queue or topic defined in the Broker
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.4.2.6.5 MetaDataQueueName

DataType String specifies the Broker queue that provides messages with DataSetMetaData sent by the Publisher for the DataSet of interest. This could be the name of a queue or topic
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.2 MessageTypes

semantics of NetworkMessages . NetworkMessages with different MessageTypes are necessary to support the discovery of Publisher configuration information and the reporting of live data and events. The defined MessageTypes are listed ... Table 151 - PubSub MessageTypes MessageType Description DataSetMessage Application data or events supplied by the Publisher as DataSet . DataSetMetaData Discovery message with content and semantics of a DataSetMessage ApplicationDescription Discovery message
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.1 General

must know the missing information from the DataSetReader configuration. One scenario is that a Publisher is sending NetworkMessages with a fixed layout of the payload. In this case the DataSetWriterId ... should be limited to applications that do not fall into these use cases. A Publisher should support all variations it allows through configuration. The required set of features is defined
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.3 Error handling

communication parameters defined in Clause 6 provide the settings for mapping information from the Publisher into DataSetMessages , settings to send them in NetworkMessages to the Subscribers and settings to process ... This handling of information flows and status codes assumes that the configuration between Publisher and Subscriber is in sync. In several combinations of settings for the DataSetMessages and NetworkMessages
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.4.2 NetworkMessage layout

UADP NetworkMessage is specified in Table 154 . The NetworkMessageContentMask setting of the Publisher controls the flags in the fields UADPFlags and ExtendedFlags1 . The SecurityMode setting of the Publisher controls ... ExtendedFlags1 . The setting of the flags shall not change until the configuration of the Publisher is changed. Table 154 - UADP NetworkMessage Name Type Description UADPVersion Bit[0-3] Bit range
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.4.3.2 AES-CTR

number is reset to 1 after the key and SecurityTokenId are updated in the Publisher . The message encryption and decryption with AES-CTR mode uses a secret and a counter ... specified by the SecurityPolicyUri in OPC 10000-7 . When a Subscriber or a Publisher receives a NetworkMessage , it shall verify the signature before processing the payload. If verification fails
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.5.6 Data Delta Frame DataSetMessage

larger because of the additional index necessary for sending just changed data. The Publisher shall send a key frame message if the delta frame message is larger than ... position in the DataSetMetaData with the configuration version defined in the ConfigurationVersion field. A Publisher shall use an index only once in a DataSetMessage . FieldValue BaseDataType The field values
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.6.1 General

General Discovery announcement messages are sent from the Publisher to the Subscribers and they can be sent through any Message Oriented Middleware and protocol mapping. Discovery announcement messages are used ... inform Subscribers about configuration changes in the Publisher . They are sent by the Publisher in the case of a configuration change. A Publisher can also be configured to send
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.6.2 Discovery scope for Datagram transport protocols

defined in 6.2.7.1 for the following discovery messages. OPC UA Application information announcement Publisher endpoint announcement PubSubConnection configuration announcement These messages use the standard discovery address if defined
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.6.4 DataSetMetaData

ConfigurationVersion in the DataSetMessage header shall match the ConfigurationVersion in the DataSetMetaData . The Publisher shall send this message without a corresponding discovery probe if the DataSetMetaData changed for the DataSet ... DataSetMetaDataType is defined in 6.2.3.2.3 . statusCode StatusCode Status code indicating the capability of the Publisher to provide MetaData for the DataSetWriterId
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.6.6 ServerEndpoints

ServerEndpoints The encoding of the available Server Endpoints of a Publisher is specified in Table 172 . Table 172 - Publisher Endpoints announcement message structure Name Type Description Endpoints EndpointDescription ... Server Endpoints of the Publisher . The EndpointDescription is defined in OPC 10000-4 . The field is encoded as Array with number of elements encoded as Int32 value. statusCode StatusCode Status
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.6.7 Status

Table 173 - ApplicationInformationType status fields Name Type Description IsCyclic Boolean If TRUE the Publisher periodically updates the status. If FALSE the Middleware is responsible for detecting changes to the status ... current state of the PubSubConnection . This value is mandatory. NextReportTime UtcTime When the Publisher expects to send the next update. The field is present if IsCyclic=TRUE. The field
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.6.9 DataSetWriter configuration announcement message

contains the current configuration of the WriterGroup and the DataSetWriter for the DataSet . The Publisher shall send this message without a corresponding discovery probe if the configuration of the WriterGroup ... WriterGroupDataType and DataSetWriterDataType . statusCodes StatusCode[] Status codes indicating the capability of the Publisher to provide configuration information for the DataSetWriterIds . The size of the array shall match the size
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.6.12.1 General

value for the first three bytes plus the PublisherId in the NetworkMessage on the Publisher as receiver. The actual security settings for the NetworkMessage are indicated by the SecurityHeader
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.6.12.2 Traffic reduction

needed announcements are received or denied. The maximum period is Subscriber specific. A Publisher shall delay subsequent announcements for a combination of probe type and identifier like the DataSetWriterId ... Duplicate probes, that have not yet been responded to, shall be discarded by the Publisher . The maximum delay is Publisher specific. If the Publisher receives discovery probes for different DataSetWriters
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.6.12.3 Discovery probe header

ProbeType Byte The following types of discovery probe messages are defined. 0 Reserved 1 Publisher information probe message (see 7.2.4.6.12.4 ) 2 FindApplications probe message. The message type does not have
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.6.12.4 Publisher information probe message

Publisher information probe message The encoding of the Publisher information probe message structure is specified in Table 179 . Table 179 - Publisher information probe message structure Name Type Description InformationType Byte ... following types of Publisher information probes are defined. 0 Reserved 1 Publisher Server Endpoints No additional fields are defined. The information is provided with the Publisher Endpoints announcement message defined
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.3 NetworkMessage containing DataSetMessages

containing DataSetMessages . This value is always present. PublisherId String A unique identifier for the Publisher . It identifies the source of the message. The presence of the value depends
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.4.1 Message content

setting in the JsonDataSetMessageContentMask . It is unique within the scope of a Publisher . DataSetWriterName String The name of the DataSetWriter which created the DataSetMessage . The presence of the value depends ... setting in the JsonDataSetMessageContentMask . PublisherId String A unique identifier for the Publisher . It identifies the source of the message. The presence of the value depends on the setting
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.4.2 VerboseEncoding

payload to OPC UA DataTypes if they have access to the DataSetMetaData of the Publisher . The rules for the special cases are defined in 7.2.5.4.3 . VerboseEncoding is the recommended default
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.4.3 VerboseEncoding and abstract type handling

nested Structure has DataType BaseDataType or AllowSubTypes =TRUE. If RawData =FALSE, then the Publisher always includes the full Variant with the UaType or ExtensionObject with UaTypeId when encoding these fields ... level or within a nested Structure . If RawData =TRUE the Publisher will encode the Variant but not include the UaTypeId and UaType which means OPC UA DataSetReaders are not able
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.5.2 DataSetMetaData

metadata". This value is mandatory. PublisherId String A unique identifier for the Publisher . It identifies the source of the message. This value is mandatory. DataSetWriterId UInt16 An identifier ... DataSetMetaData . This value is mandatory. It is unique within the scope of a Publisher . WriterGroupName String The name of the WriterGroup which created the NetworkMessage . This value is mandatory. DataSetWriterName
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.5.3 ApplicationDescription

value shall be "ua-application". This value is mandatory. PublisherId String The Publisher that sent the message. This value is mandatory. Timestamp UtcTime When the message was first ... ServerCapabilities String [] The set of Server capabilities supported by the Server associated with the Publisher . The set of allowed Server capabilities are defined in OPC 10000-12 . This value
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.5.4 ServerEndpoints

value shall be "ua-endpoints". This value is mandatory. PublisherId String The Publisher that sent the message. This value is mandatory. Timestamp UtcTime When the message was first
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.5.5 Status

value shall be "ua-status". This value is mandatory. PublisherId String The Publisher that sent the message. This value is mandatory. Timestamp UtcTime When the message was sent ... IsCyclic=TRUE. The field is omitted if IsCyclic=FALSE. IsCyclic Boolean If TRUE the Publisher periodically updates the status. If FALSE the Middleware is responsible for detecting changes
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.5.6 PubSubConnection

value shall be "ua-connection". This value is mandatory. PublisherId String The Publisher that sent the message. This value is mandatory. Timestamp UtcTime When the message was first
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.5.7 ActionMetaData

shall be "ua-action-metadata". This value is mandatory. PublisherId String The Publisher that sent the message. This value is mandatory. DataSetWriterId UInt16 An identifier for DataSetWriter which ... metadata. This value is mandatory. It is unique within the scope of a Publisher . DataSetWriterName String The name of the DataSetWriter. This value is optional. The presence of the value
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.5.8 ActionResponder

shall be "ua-action-responder". This value is mandatory. PublisherId String The Publisher that sent the message. This value is mandatory. Timestamp UtcTime When the message was first
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.3.2.1 General

usable network address. OPC 10000-7 defines Profiles for different name resolution protocols that Publisher or Subscriber may support. For OPC UA UDP it is recommended to limit the MaxNetworkMessageSize
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.3.2.2 UDP multicast and broadcast

protocol URL for UDP multicast and broadcast communication is configured on a PubSubConnection for Publisher and Subscriber . The Address parameter for a PubSubConnection is defined in 6.2.7.3 . The Url field
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.3.2.3 UDP unicast

Subscriber is configured on the PubSubConnection and the address information for the Publisher is configured on the WriterGroup . The receive port for UDP unicast communication is configured on a PubSubConnection
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.3.2.4.1 General

CertificateManager. Pull Management or Push Management of certificates shall be supported by any Publisher or Subscriber that supports the DTLS Transport (see Part 12 for more information on the CertificateManager ... prior to the PubSub data exchange. In this case either the Subscriber or the Publisher acts as the DTLS Client, with the other one acting as the DTLS Server. Once
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.3.4.1 General

message mapping. No additional information is added to the meta data messages . MQTT Publisher and Subscriber transport profiles for full and minimal support are defined in OPC 10000-7 . Message ... security is primarily provided by a TLS connection between the Publisher or Subscriber and the MQTT server; however, this requires that the MQTT server be trusted. For that reason
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.3.4.7.1 General

published to the Topic as defined in 7.3.4.7.2 ; <PublisherId> uniquely identifies a Publisher within the scope of the prefix; <WriterGroup> is the name of a WriterGroup ... within the Publisher ; <DataSetWriter> is the name of a DataSetWriter within the WriterGroup ; The <Prefix> should be one Topic level, however, system designers may break
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.3.4.7.2 MessageType mapping

responder True Yes Defined in 7.3.4.7.11 . Table 205 - MQTT Topic level access permissions MqttMessageType Publisher Subscriber Description data Write Read Variables and Events from an OPC UA applications acting ... Publisher have RolePermissions . Such RolePermissions have no affect after DataSetMessages are sent to the MQTT broker. It is therefore recommended to synchronize Roles used to configure read permissions
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.3.4.7.3 data Topic level

WriterGroup> Topic level is the name of a WriterGroup within the Publisher . The <DataSetWriter> Topic level is the name of a DataSetWriter within the WriterGroup ... PublisherId>. The PubSubConnection specifies the WriterGroups and DataSetWriters for a Publisher
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.3.4.7.4 metadata Topic level

WriterGroup> Topic level is the name of a WriterGroup within the Publisher. The <DataSetWriter> Topic level the name of a DataSetWriter within the WriterGroup . The metadata Topic ... PublisherId>. The PubSubConnection specifies the WriterGroups and DataSetWriters for a Publisher
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.3.4.7.7 status Topic level

sending the messages. The messages are instances of the Status MessageType (see 7.2.2 ). A Publisher that is exclusively using a PublisherId shall register a Status message as an MQTT Will ... creates the connection to the MQTT Broker . This message is sent automatically if the Publisher loses its connection with the MQTT Broker . The IsCyclic shall be FALSE in this case
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.3.4.7.8 connection Topic level

PubSubConnection provided in the message. The PublisherId in the PubSubConnection uniquely identifies the Publisher within the scope defined by the <Prefix>. The TransportProfileUri in the PubSubConnection specifies
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.3.4.7.11 action-responder Topic level

PubSubConnection provided in the message. The PublisherId in the PubSubConnection uniquely identifies the Publisher within the scope defined by the <Prefix>. If it is a String, it should
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.3.4.7.12 action-metadata Topic level

PublisherId>. The PubSubConnection specifies the WriterGroups and DataSetWriters for a Publisher
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.3.4.8 Message header

Table 208 defines an option to change the RETAIN flag setting for DataSetMessages . A Publisher shall send all RETAIN discovery messages at start up of the Publisher . A Publisher shall ... update affected RETAIN topics if the Publisher configuration changes. A Publisher shall clear RETAIN topics if the discovery element is deleted from the Publisher configuration like reset the metadata topic
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

8.1 Overview

defines the distribution framework for cryptographic keys used for message security. A Publisher or Subscriber can pull the keys from the SKS or the SKS can push the keys ... Publisher or Subscriber . The sequences for pull and push are described in 5.4.5.3 . The SKS can be a network service used to manage keys for all Publishers and Subscribers
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

8.3.2 GetSecurityKeys Method

setting of WriterGroup, ReaderGroup and DataSetReader . The GetSecurityKeys Method can be implemented by a Publisher or by a central SKS. In both cases, the well-known NodeIds for the PublishSubscribe ... related GetSecurityKeys Method are used to call the GetSecurityKeys Method . If the Publisher implements the GetSecurityKeys Method and the related SecurityGroup management, the keys are made invalid immediately after
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

8.6.2 Behaviour

shall call SetSecurityKeys to push the security keys for a SecurityGroup into a Publisher or Subscriber . The SKS shall push the previous security key, the current key, and at least
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.1 General

list of PubSubConnectionType Objects and the PublishedDataSetType Objects through the PublishedDataSets folder. On the Publisher side, a PublishedDataSet represents the information to publish and the DataSetWriter represents the transport settings ... figure are examples for blocks necessary to implement the information flow in a Publisher . Figure 44 - PubSub information flow The PublishedDataSetType represents the selection and configuration of Variables or Events
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.2 Configuration behaviours

Client based configuration tool to configure an OPC UA Server that is a Publisher and/or Subscriber . The latest configuration shall be persisted by the OPC UA Server and shall
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.3.3 SetSecurityKeys

This Method is used to push the security keys for a SecurityGroup into a Publisher or Subscriber . It is used if Publisher or Subscriber have no OPC UA Client functionality ... TimeToNextKey The time, in milliseconds, before the CurrentKey is expected to expire. If a Publisher receives the keys from a SKS through this Method , the TimeToNextKey and KeyLifetime are used
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.4.1 Overview

information necessary for a Subscriber to understand and decode DataSetMessages received from the Publisher for a DataSet and to detect changes of the DataSet semantic and metadata. The types derived
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.4.2.1 PublishedDataSetType

used directly to expose the custom PublishedDataSet in the AddressSpace of the Publisher . If the Variable CyclicDataSet is not present, the custom PublishedDataSet shall create cyclic DataSets . The PublishedDataSetType ... DataSetClassId of the DataSetMetaData is not null. If the DataSetClassId is not null, the Publisher shall reject any configuration changes that change the DataSetMetaData . The Property value shall match
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.4.2.2 ExtensionFieldsType

values to be included in the DataSet in case the existing AddressSpace of the Publisher does not provide the necessary information. Table 248 - ExtensionFieldsType definition Attribute Value BrowseName ExtensionFieldsType IsAbstract
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.4.3.2 AddVariables Method

returned in AddVariables . Otherwise, if the length of the array is dynamic, the Publisher shall insert this status in a DataSet if no data exists within the range. Bad_TooManyVariables ... Publisher has reached its maximum number of items for the PublishedDataItemsType object. Table 254 specifies the AddressSpace representation for the AddVariables Method . Table 254 - AddVariables Method AddressSpace definition Attribute Value
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.4.5.2 AddPublishedDataItems Method

returned in AddVariables . Otherwise if the length of the array is dynamic, the Publisher shall insert this status in a DataSet if no data exists within the range. Bad_TooManyMonitoredItems
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.4.5.4 AddPublishedDataItemsTemplate Method

DataSetMetaData predefined by the caller. The initial setting shall not be changed by the Publisher . If the dataSetClassId of the DataSetMetaData is not null, the DataSetClassId Property of the PublishedDataSetType ... created since the number of items in the PublishedDataSet exceeds the capabilities of the Publisher . Operation Result Codes ResultCode Description Bad_NodeIdInvalid See OPC 10000-4 for the description
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.4.5.5 AddPublishedEventsTemplate Method

DataSetMetaData predefined by the caller. The initial setting shall not be changed by the Publisher . If the dataSetClassId of the DataSetMetaData is not null, the DataSetClassId Property of the PublishedDataSetType
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.8.5 CreateTargetVariables Method

configured yet or the ConfigurationVersion does not match the version in the Publisher . Bad_UserAccessDenied The Session user is not allowed to configure the Object . Operation Result Codes ResultCode Description
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.8.6 CreateDataSetMirror Method

configured yet or the ConfigurationVersion does not match the version in the Publisher . Bad_UserAccessDenied The Session user is not allowed to configure the Object . Table 295 specifies the AddressSpace
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.9.2.2 AddTargetVariables Method

configured yet or the ConfigurationVersion does not match the version in the Publisher . Bad_UserAccessDenied The Session user is not allowed to configure the Object . Operation Result Codes ResultCode Description
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.9.5 StandaloneSubscribedDataSetType

side. A DataSetReader can be configured and connected to the standalone DataSet if a Publisher provides the DataSetMessages defined by the DataSetMetaData in the standalone DataSet . The StandaloneSubscribedDataSetType is formally ... received DataSet in a Subscriber . The DataSetMetaData is defined in 6.2.9.4 . A Publisher must be configured to send DataSetMessages that comply with the DataSetMetaData in the standalone subscribed DataSet
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.1.1 Motivation

every PublishingInterval , and the Subscriber knows this in advance, several optimizations are possible: Both Publisher and the Subscriber can be optimized for sending and receiving messages with a fixed layout
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.1.2 Overview

every PublishingInterval Note: These assumptions have to be fulfilled by appropriate configuration of the Publisher . Subscribers have to know the static message layout in advance. This means all fields
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.2.2 Overview

With the header layout described in this section, the NetworkMessage header only identifies the Publisher and the contained DataSetMessages . In contrast to the fixed layout, more header fields are enabled
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.2.4 Header layout for NetworkMessages

PublisherId the DataType UInt64 was selected because it allows a simple way for a Publisher to generate unique PublisherIds by using the local MAC address (48 bit) as part
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

B.3.1 General

Security with AMQP is primary provided by a TLS connection between the Publisher or Subscriber and the AMQP Broker , however, this requires that the AMQP Broker be trusted. For that
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

B.3.6 Transport Limits and Keep Alive

capabilities of the OS or on the capabilities of the device the Publisher or Subscriber is running on, and can be made configurable through configuration model extensions or by other
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

C.3 Publish-Subscribe

different system components without these components having to know each other's identity. A Publisher is pre-configured with what data to send. There is no connection establishment between Publisher ... published data to the Subscribers is the responsibility of the Message Oriented Middleware . The Publisher does not know or even care if there is one or many Subscribers . Effort
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

C.4 Synergy of models

easily be integrated into OPC UA Servers and OPC UA Clients . Quite typically, a Publisher will be an OPC UA Server (the owner of information) and a Subscriber is often
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

D.1.1 Overview

AliasName definitions. This extension to a Server that supports AliasNames , provides a Publisher capability for the Server (see OPC 10000-14 ). This extension also provides a simple way to determine
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

D.1.2 PubSub multicast messages

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 consist ... removed, resulting in a change in the size of the AliasNameCategory array. This Publisher shall provide a fixed DataSet with a pre-defined DataSetClassId . This Publisher shall generate messages
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 ... Publisher . See OPC 10000-14 for additional details on data key frames, data delta frame, PublishingIntervals and security settings. PublishingInterval that is defined for the published messages. The KeyFrameCount that
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

D.3.2 Header layout for NetworkMessages

PublisherId the DataType UInt64 was selected because it allows a simple way for a Publisher to generate unique PublisherIds by using the local MAC address (48 Bit) as part
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

connection between two FunctionalEntities located on the AutomationComponents A and B, each containing a Publisher , a Subscriber , and a single PubSubConnectionEndpoint . Both FunctionalEntities could be publishing data (bidirectional Connection
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.5.6.2.5 DataSetMetaData

DataSet . In addition, the DataSetMetaData provides the details defining the contract between the Publisher and the Subscriber , including how to encode and decode the DataSetMessage . Thus, Subscribers must know about ... Depending on the chosen UADP header layout, the ConfigurationVersion of an individual Publisher or a GroupVersion combining the ConfigurationVersions of all Publishers belonging to a WriterGroup is transmitted with
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.2 AutomationComponentType definition

Server shall generate GeneralModelChangeEvent to reflect these changes. The optional PublisherCapabilities provide the Publisher capabilities associated with this AutomationComponent . They apply to all instances in the FunctionalEntities Folder . An individual ... FunctionalEntity can further restrict these capabilities. If an AutomationComponent supports being a Publisher as defined in OPC 10000-14 , then an instance of this Object shall be provided. The optional
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.7 PublisherCapabilitiesType

PublisherCapabilitiesType is a subtype of the BaseObjectType . It is used to contain the various Publisher capabilities that can be supported. An instance of this ObjectType groups the capabilities ... PublishedDataSets are defined by this instance. PreconfiguredDataSetOnly , if set to TRUE, indicates that the Publisher supports publishing of preconfigured PublishedDataSets only. If set to FALSE, the Publisher supports publishing
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.4.2 FunctionalEntityType definition

describes the functionality provided by a FunctionalEntity (see 6.4.7 ). The optional PublisherCapabilities provide the Publisher capabilities associated with this FunctionalEntity . They also apply to all sub- FunctionalEntities of this FunctionalEntity
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.4.5 OutputsFolderType

optional PublisherCapabilities shall only be present on OutputData of the FunctionalEntity . It provides the Publisher capabilities associated with the OutputData and describes additional restrictions of the PublisherCapabilities defined
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.4.7 FunctionalEntityCapabilitiesType

autonomous Subscriber . If FeedbackSignalRequired is missing or set to FALSE, the connection types unidirectional Publisher and autonomous Publisher are also supported
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.6.3 PubSubConnectionEndpointType definition

Mode is PublisherSubscriber , a ToDataSetReader and a ToDataSetWriter Reference are required. If Mode is Publisher , a ToDataSetWriter Reference is required; there shall be no ToDataSetReader set. If Mode is Subscriber ... Figure 32 . Figure 32 - Status with Mode of Subscriber For PubSubConnectionEndpoints with Mode of Publisher , the Status shall be determined by the Status of the referenced DataSetWriter according to Figure
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.12.2 ConnectionEndpointParameterType definition

ConnectionManager can obtain any 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 ... information related to this preconfigured StandaloneSubscribedDataSet from the UA Subscribers exposed PubSub configuration. The Publisher is required to provide all data in the StandaloneSubscribedDataSet , but it may include additional data
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.13.3.2 PubSubCommunicationFlowConfigurationType definition

model, the information flow can be linked with ConnectionEndpointConfiguration Objects to explicitly indicate the Publisher and Subscriber (s) of the information flow. The linkage is provided by ToOutboundFlow and ToInboundFlow ... specifies the destination network address to be used for transmission of NetworkMessages by the Publisher of the information flow. This is an abstract type, and a concrete subtype shall
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

10.12 CommunicationFlowQosDataType

effort. False TransmitQos 0:TransmitQosDataType[] The TransmitQos describes QoS category-related parameters for the Publisher . This array shall be null or empty if no QoS-related parameters are required ... Publisher is defined. For the defined parameters, see OPC 10000-14 . True ReceiveQos 0:ReceiveQosDataType[] The ReceiveQos describes QoS category-related parameters for the Subscriber . This array shall be null
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.3.7.5 Using ControlGroups to expose functionality.

bidirectional communication. In this example, Controller B comes with preconfigured DataSets , one for the Publisher and one for the Subscriber . Figure D.31 - ControlGroup cascade Controller example ControlGroup can be created
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.1.2 Single logical connection

Subscriber only, its parent PubSubCommunicationFlowConfigurationType Object contains configuration relevant for both the Publisher and Subscriber . The configuration contained in Flow1 is used for setting up the Publisher on ServerA ... Subscriber on ServerB. Flow2 and SubA are used for setting up the Publisher and Subscriber in the opposite direction. EndpointA and EndpointB are each referenced by an AutomationComponentConfiguration
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.2.2.1 For logical connections between two AutomationComponents

requires certain configuration values (e.g., PublisherId , WriterGroupId , and DataSetWriterId ) to match the Publisher and its corresponding Subscribers . However, unique IDs could be generated by the addressed AutomationComponent
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.4.5 Autonomous publisher

E.4.5 Autonomous publisher The Connection configuration for an autonomous publisher contains the following configuration information (see Figure E.14 ): EndpointA, indicating OutputVariables; Flow1, describing the configuration for the information flow from ... EndpointA to one or more unknown Subscribers. For an autonomous publisher, no SubscriberConfiguration is required (see 6.13.3.2 ). Figure E.14 - Autonomous publisher illustration
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.4.6 Autonomous subscriber

InputVariables, Flow1 and SubA describing the configuration for the information flow from an unknown Publisher to EndpointA. For an autonomous subscriber, no ToOutboundFlow Reference is required. Configuration , which applies only ... Publisher of the information flow, can be omitted, i.e., Address and TransmitQos (see E.4.1 ). Figure E.15 - Autonomous subscriber illustration
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.4.7 PubSub DataSets

time. Figure E.21 illustrates what is defined as part of a DataSet (both Publisher and Subscriber ). Figure E.21 - Dataset definition information Preconfigured DataSets can be provided in UAFX as part ... later version of this document. When establishing communication, the DataSet and the Publisher's DataSetMetaData define what is on the wire. This includes which Nodes are used for the Values
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.5 Interaction with an SKS

configured SecurityGroups . The SKS can expose the SecurityGroups in its Information Model . A Publisher uses the current key to sign or sign and encrypt NetworkMessages , and Subscriber(s) to authenticate ... requested number of future keys are distributed from the SKS to the Publisher and the Subscriber(s) using the push or pull model. How past, current and future keys
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.6.2 ConnectionConfigurationSet and WriterGroup

E.6.2 ConnectionConfigurationSet and WriterGroup As defined in OPC 10000-14 , a WriterGroup defines the Publisher of a NetworkMessage . It is recommended that the PubSubConfiguration contains a WriterGroup for each instance ... value different from null if the translation of Strings will be done by the Publisher . Priority can be used to set the relative priority of the WriterGroup for processing
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.6.5 ConnectionConfigurationSet and DataSetReader

ReserveCommunicationIdsCmd ; see E.2 for details. The values are set to correspond to the Publisher of the DataSetMessage. The ToDataSetReader Reference can be derived from either the PreconfiguredSubscribedDataSet or from ... additional Quality of Services are specified. GroupVersion and PublishingInterval are set corresponding to the Publisher of the DataSetMessage. DataSetClassId can be set to NULL. The DataSetReader element TransportSettings is transport
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.6.6 Loading / Saving ConnectionConfigurationSets

this case, the PublishedDataSet or SubscribedDataSet describes Variables that are on the Publisher or Subscriber Server , which is very likely to be a different Server . Depending on how the ConnectionConfigurationSet
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.7 PubSubCommunicationFlowConfigurationConfDataType

specifies the destination network address to be used for transmission of NetworkMessages by the Publisher of the information flow. True TransportProfileUri 0:String Optional TransportProfileUri specifies the transport protocol mapping
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

6.6.2.3 UAFX AutomationComponent Communication Publisher Facet

UAFX AutomationComponent Communication Publisher Facet Table 17 describes the details of the UAFX AutomationComponent Communication Publisher Facet. This Facet includes the functionality needed for a UAFX Publisher . Table 17 - UAFX ... AutomationComponent Communication Publisher Facet Group Conformance Unit / Profile Title Optional UAFX AutomationComponent UAFX AutomationComponent PublisherCapabilities Base False UAFX AutomationComponent UAFX AutomationComponent PubSub Connections False UAFX AutomationComponent UAFX AutomationComponent PublisherCapabilities Preconfigured