Search

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

75 result(s) for NetworkMessages

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

2.1.5 Broker

Broker intermediary program module that routes NetworkMessages from Publishers to Subscribers Note 1 to entry: Brokers are building blocks of Message Oriented Middleware
OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts

2.1.19 Message Oriented Middleware

Message Oriented Middleware infrastructure supporting sending and receiving NetworkMessages between distributed systems Note 1 to entry: An OPC UA Application may support different types of Message Oriented Middleware infrastructures
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 ... Message Oriented Middleware and the rules for encoding the NetworkMessages and DataSetMessages
OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts

2.1.42 Subscriber

just knowledge about the Message Oriented Middleware and the rules for decoding the NetworkMessages and DataSetMessages . A Subscription in the OPC UA ClientServer model has a different meaning than
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.1 General

data, and the Message Oriented Middleware . The "messages" in Figure 2 represent NetworkMessages . Each NetworkMessage includes header information (e.g. identification and security data) and one or more DataSetMessages
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.3.1 General

handed off and received from a specific Message Oriented Middleware . DataSetMessages are embedded in NetworkMessages . Figure 4 shows the relationship of these message types. Figure 4 - OPC UA PubSub message
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.3.7 SecurityGroup

abstraction that represents the message security settings and security keys for a subset of NetworkMessages exchanged between Publishers and Subscribers . The security keys are used to encrypt and decrypt NetworkMessages
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.3.8 Topics

string associated with a NetworkMessage that can be used to logically organize NetworkMessages published to a Message Oriented Middleware . Topics are most commonly used with Broker -based middleware where ... example: opcua/json/status/FlowController1 Mappings to different implementation technologies may add additional constraints. A Topic for NetworkMessages containing DataSetMessages is typically used as QueueName for the broker-based communication configuration
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
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.4.2.1 General

General Subscriber s are the consumers of NetworkMessages from the Message Oriented Middleware . They may be OPC UA Clients , OPC UA Servers or applications that are neither Client nor Server ... PubSub messages. Figure 7 illustrates a Subscriber with filtering, decoding and dispatching of NetworkMessages . Figure 7 - Subscriber details To determine for which DataSetMessage s and on which Message Oriented Middleware
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.4.5.1 General

message security that can be used by the Publisher to sign and encrypt NetworkMessages and by the Subscriber to verify the signature of NetworkMessages and to decrypt them ... 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 by the SKS shall
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.4.5.2 SecurityGroup Management

Subscribers is shown in Figure 10 . Figure 10 - SecurityGroup management sequence To secure NetworkMessages , the NetworkMessages shall be secured with keys provided in the context of a SecurityGroup. A SecurityGroup
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.4.6.2.2 Broker-less model with OPC UA UDP

send the complete DataSet in every DataSetMessage or with the option to repeat NetworkMessages . Other transport protocol mappings used with the broker-less model could provide guarantee of timeliness, delivery
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.4.6.3.2 Broker-based model

this model the Message Oriented Middleware will be a Broker that relays NetworkMessages from Publishers to Subscribers . The Broker may also be able to queue messages and send the same
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.4.6.4 QoS configuration

configuration OPC UA Applications may demand Quality of Service (QoS) for the transport of NetworkMessages . These QoS requirements have to be fulfilled by the broker-less Message Oriented Middleware
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.1 Overview

filter settings are on the DataSetReaders . DataSetReader parameters represent settings for filtering of received NetworkMessages and DataSetMessages as well as settings for decoding of the DataSetMessages of interest. SubscribedDataSet parameters ... PubSubConnection , the WriterGroup or the DataSetWriter . Message mapping specific parameters are defined for the NetworkMessages on the WriterGroup and for the DataSetMessages on the DataSetWriter
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.3.2.5 DataSetFieldFlags

Description PromotedField 0 The flag indicates if the field is promoted to the NetworkMessages or transport protocol header. Setting this flag increases the size of the NetworkMessages since information from
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.5.2 SecurityMode

SecurityMode The SecurityMode indicates the level of security applied to the NetworkMessages published by a WriterGroup or received by a ReaderGroup . The MessageSecurityMode DataType is defined
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.5.3 SecurityGroupId

security keys used for the NetworkMessage security. The PubSubGroup defines the SecurityMode for the NetworkMessages sent by the group
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.5.5 MaxNetworkMessageSize

MaxNetworkMessageSize The MaxNetworkMessageSize with DataType UInt32 indicates the maximum size in bytes for NetworkMessages created by the WriterGroup . It refers to the size of the complete NetworkMessage including padding ... value for the MaxNetworkMessageSize should be configured in a way that ensures that NetworkMessages together with additional headers added by the transport protocol are still smaller than or equal than
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.6.2 PublishingInterval

PublishingInterval The PublishingInterval with the DataType Duration defines the interval in milliseconds for publishing NetworkMessages and the embedded DataSetMessages created by the related DataSetWriters . Negative values are invalid
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.11.2.2 Action execution sequence

CorrelationData . Each Action request in a single NetworkMessage has a different RequestId . Multiple NetworkMessages with the same RequestorId and CorrelationData may be sent. Multiple Responses may be sent ... corresponding requests have the same RequestorId and CorrelationData . The grouping of requests in NetworkMessages does not affect the grouping of Responses into NetworkMessages . The Action execution sequence for an Action
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.1.1.2 GroupVersion

VersionTime reflects the time of the last layout change of the content of the NetworkMessages published by the WriterGroup . The VersionTime DataType is defined in OPC 10000-4 . The GroupVersion ... WriterGroup ; DataSetWriterId of any DataSetWriter in this WriterGroup . The GroupVersion is valid for all NetworkMessages resulting from this WriterGroup
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.1.1.3 DataSetOrdering

DataSetOrdering The DataSetOrdering defines the ordering of the DataSetMessages in the NetworkMessages . Possible values for DataSetOrdering are described in Table 95 . The default value is Undefined . The DataSetOrderingType ... enumeration that specifies the possible options for the ordering of DataSetMessages inside and across NetworkMessages . The possible enumeration values are described in Table 95 . Table 95 - DataSetOrderingType values Name Value
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.1.1.4 NetworkMessageContentMask

NetworkMessageContentMask The parameter NetworkMessageContentMask defines the optional header fields to be included in the NetworkMessages produced by the WriterGroup . The DataType for the UADP NetworkMessage mapping is UadpNetworkMessageContentMask . The DataType ... included in the NetworkMessage s. GroupHeader 1 The GroupHeader is included in the NetworkMessages . WriterGroupId 2 The WriterGroupId field is included in the GroupHeader . The flag is only valid
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.1.1.6 PublishingOffset

Figure 31 depicts how the different variations of PublishingOffset settings affect sending of multiple NetworkMessages . Figure 31 - PublishingOffset options for multiple NetworkMessages If all DataSets of a group are transferred ... PublishingInterval cycle. If the DataSets of a group are sent in a series of NetworkMessages , the values in the array define the offsets of sending the NetworkMessages relative
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.1.3.1 General

result in a fixed NetworkMessage layout where all DataSets have a static position between NetworkMessages . In this case the parameters NetworkMessageNumber and DataSetOffset provide information about the static position
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.1.3.4 NetworkMessageNumber

first NetworkMessage in a PublishingInterval shall be generated with the value 1, the following NetworkMessages shall be generated with incrementing NetworkMessageNumbers . To avoid a roll-over the number of NetworkMessages
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.1.4.5 Network‌Message‌ContentMask

NetworkMessageContentMask with DataType UadpNetworkMessageContentMask indicates the optional header fields included in the received NetworkMessages . The UadpNetworkMessageContentMask DataType is defined
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.2.1.1 NetworkMessageContentMask

NetworkMessageContentMask The parameter NetworkMessageContentMask defines the optional header fields to be included in the NetworkMessages produced by the WriterGroup . The DataType for the JSON NetworkMessage mapping is JsonNetworkMessageContentMask . The DataType ... Value Bit No. Description NetworkMessageHeader 0 The JSON NetworkMessage header is included in the NetworkMessages . If this bit is false, bits 3 and 4 shall be 0. DataSetMessageHeader
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.2.4.1 Network‌Message‌ContentMask

NetworkMessageContentMask with DataType JsonNetworkMessageContentMask indicates the optional header fields included in the received NetworkMessages . The JsonNetworkMessageContentMask DataType is defined
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.4.1.2.4 DiscoveryMaxMessageSize

DiscoveryMaxMessageSize The DiscoveryMaxMessageSize with DataType UInt32 indicates the maximum size in bytes for NetworkMessages created for discovery. It refers to the size of the complete NetworkMessage including padding and signature ... value for the DiscoveryMaxMessageSize should be configured in a way that ensures that NetworkMessages together with additional headers added by the transport protocol are still smaller than or equal than
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.4.2.3.1 QueueName

QueueName parameter with 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
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.4.2.3.4 RequestedDeliveryGuarantee

RequestedDeliveryGuarantee parameter with DataType BrokerTransportQualityOfService specifies the delivery guarantees that shall apply to all NetworkMessages published by the WriterGroup unless otherwise specified on the DataSetWriter transport settings. The DataType BrokerTransportQualityOfService
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.4.2.5.1 QueueName

QueueName parameter with 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 ... topic defined in the Broker . This parameter is only valid if the NetworkMessages from the WriterGroup for this DataSetWriter contain only DataSetMessages from this DataSetWriter . If this String
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.4.2.6.1 QueueName

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

7.2.1 General

General Message mappings specify a specific structure and encoding for NetworkMessages . Such a structure represents the payload for transport protocol mappings like UDP, MQTT or Ethernet. Different mappings are defined
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.2 MessageTypes

MessageTypes MessageTypes define the structure and semantics of NetworkMessages . NetworkMessages with different MessageTypes are necessary to support the discovery of Publisher configuration information and the reporting of live data
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.1 General

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 , the offset ... profiles in OPC 10000-7 . A Subscriber shall be able to process all possible NetworkMessages and shall be able to skip information the Subscriber is not interested in. The Subscriber
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.3 Error handling

settings for mapping information from the Publisher into DataSetMessages , settings to send them in NetworkMessages to the Subscribers and settings to process the DataSetMessages on the Subscriber side. The error ... Subscriber is in sync. In several combinations of settings for the DataSetMessages and NetworkMessages , a Subscriber is able to process received messages without further knowledge of the Publisher side configuration
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.4.2 NetworkMessage layout

DataType is indicated by bits 0-2 of the ExtendedFlags1 . A Subscriber can skip NetworkMessages from Publishers it does not expect NetworkMessages from. PublisherIds are only equal if they have ... WriterGroupId UInt16 Unique id for the WriterGroup in the Publisher. A Subscriber can skip NetworkMessages from WriterGroups it does not expect NetworkMessages from. This field shall be omitted
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.4.4 UADP Chunk NetworkMessage

NetworkMessage If a NetworkMessage payload with a DataSetMessage need to be split across multiple NetworkMessages, the chunks are sent in multiple NetworkMessages . The PayloadHeader of each NetworkMessage contains the payload ... NetworkMessage payload with a discovery announcement message has to be split across multiple NetworkMessages the chunks are sent with the payload defined in Table 159 . The payload header is disabled
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.5.3 DataSet payload

header. If the payload size exceeds 65535, the DataSetMessages shall be allocated to separate NetworkMessages . If a single DataSetMessage exceeds the payload size it shall be split into Chunk NetworkMessages
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.6.12.4 Publisher information probe message

WriterGroup and the contained DataSetWriters if only the WriterGroupId is known from NetworkMessages . For WriterGroup configuration probes, the DataSetWriters that belong to the WriterGroup are sent together in one DataSetWriter
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.3 NetworkMessage containing DataSetMessages

always present. MessageType String This value shall be "ua-data" for NetworkMessages containing DataSetMessages . This value is always present. PublisherId String A unique identifier for the Publisher
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.3.2.1 General

simple UDP based protocol that is used to transport UADP NetworkMessages . A PubSubConnection for UDP shall have a unique Address across all PubSubConnections of an OPC UA Application ... number of frames used for a UADP NetworkMessage influences the probability that UADP NetworkMessages get lost. Note: The MaxNetworkMessageSize that fits into one MTU is maximum 1472 Byte for IPv4
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.3.2.2 UDP multicast and broadcast

field in the Address is used as destination address for NetworkMessages sent as UDP datagram. The Address is also used to receive UDP datagrams from the multicast IP address ... snooping" whereby the switch listens to IGMP messages and only sends the multicast NetworkMessages to ports that have joined the multicast group. The corresponding protocol for IPv6
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.3.2.3 UDP unicast

PubSubConnection . The Address parameter for a PubSubConnection is defined in 6.2.7.3 . All NetworkMessages for one port are received through one PubSubConnection. The filtering and assignment of NetworkMessages for the Subscriber
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.3.3 OPC UA Ethernet

simple Ethernet based protocol using EtherType 0xB62C that is used to transport UADP NetworkMessages as payload of the Ethernet II frame without IP or UDP headers. The syntax
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.3.4.1 General

advance with knowledge of the expected encoding. As a consequence, Publishers should only publish NetworkMessages using a single encoding to a unique MQTT topic name. MQTT version 5.0 adds ... that require end-to-end message security with MQTT need to use the UADP NetworkMessages and binary message encoding defined in 7.2.3 . JSON encoded message bodies need to rely
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

8.1 Overview

part of a Publisher to manage the keys for the NetworkMessages sent by this Publisher . Figure 41 depicts the ObjectTypes and their components used to represent the SKS functionality ... provided, the PublishSubscribeType is used instead. A SecurityGroup manages keys used for securing PubSub NetworkMessages . The SecurityGroups are organized by the SecurityGroupFolderType and represented by instances of the SecurityGroupType
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

8.3.2 GetSecurityKeys Method

keys for several Publishers , a Subscriber needs to expect some overlap time where NetworkMessages are received that are using the previous or the next key. TimeToNextKey and KeyLifetime are also
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

8.4.1 SecurityGroupType definition

historical keys are necessary to allow Subscribers to request keys for older NetworkMessages
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.1 General

DataSetWriter Objects that share settings such as security configuration, encoding or timing of NetworkMessages . A group manages a list of DataSetWriterType Objects that define the payload of the NetworkMessages created ... group settings. DataSetWriters represent the configuration necessary to create DataSetMessages contained as payload in NetworkMessages . DataSetReaders represent the configuration necessary to receive and process DataSetMessages on the Subscriber side. NetworkMessages
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.3.3 SetSecurityKeys

keys for several Publishers , a Subscriber needs to expect some overlap time where NetworkMessages are received that are using the previous or the next key. KeyLifetime The lifetime
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.3.7.4 PubSubConfigurationValueDataType

element. Identifier BaseDataType The identifier value used for the referenced element in the PubSub NetworkMessages . The value is only provided if the element is a PubSubConneciton , WriterGroup or DataSetWriter
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.8.2 DataSetReaderType

PubSub Model Base The Properties PublisherId, WriterGroupId, DataSetWriterId and DataSetClassId define filters for received NetworkMessages . If the value of the Property is set, it is used as filter
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.11.9 PubSubDiagnosticsWriterGroupType

Rule Diagnostics Level Class Description Inherited counters from PubSubDiagnosticsType SentNetworkMessages Mandatory Basic Information Sent NetworkMessages FailedTransmissions Mandatory Basic Error Error on NetworkMessage transmission EncryptionErrors Optional Advanced Error Error on signing
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.11.10 PubSubDiagnosticsReaderGroupType

Level Class Description Inherited counters from PubSubDiagnosticsType ReceivedNetworkMessages Mandatory Basic Information Received and processed NetworkMessages ReceivedInvalidNetwork‌Messages Optional Advanced Error Invalid format of NetworkMessage Header DecryptionErrors Optional Advanced Error Decryption
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.12.1 PubSubCapabilitiesType

Variable defines the maximum number of bytes that can be configured as MaxNetworkMessageSize for NetworkMessages sent or received through datagram transport protocol mappings. A value of 0 indicates that ... Variable defines the maximum number of bytes that can be configured as MaxNetworkMessageSize for NetworkMessages sent or received through broker transport protocol mappings. A value of 0 indicates that
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.13.2 PubSubTransportLimitsExceedEventType

bytes of the actual NetworkMessage . The Maximum Property has the maximum size of NetworkMessages in bytes allowed by the transport
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.1 General

General The header content and message layouts for both NetworkMessages and DataSetMessages in different message mappings were designed to be flexible and to support different use cases by enabling ... disabling individual fields within the headers. The header layouts only apply to NetworkMessages with DataSetMessages . While this flexibility makes it possible to support many different use cases with PubSub
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.2.1 Motivation

message layouts or Event based DataSetMessages, the number and ordering of DataSetMessages within different NetworkMessages can change arbitrarily. The header layouts described in this section are intended for use cases
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

B.2.1 General

partitions, and to store the messages. Kafka producers are used to publish OPC UA NetworkMessages to Kafka topics. Topics must be created in the broker before they can be used ... producers. Kafka consumers are used to subscribe to Kafka topics and receive OPC UA NetworkMessages . Kafka topics are configured throgh QueueNames in WriterGroups , DataSetWriters and DataSetReaders . A Broker may persist
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

B.3.1 General

limit is defined by the AMQP field max-message-size. The mechanism for handling NetworkMessages that exceed the Broker limits depends on the MessageMapping . For MessageMappings that support chunking ... exceed the AMQP max-message-size. For MessageMappings that do not support chunking, the NetworkMessages exceeding the maximum size mut be skipped. Diagnostic information for such error scenarios are provided
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

configured to exchange data between AutomationComponents AC_A and AC_B using unicast NetworkMessages
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

instances are configured to exchange data between AC_A and AC_B using unicast NetworkMessages . This use case is called aggregated because a single NetworkMessage aggregates multiple DataSetMessages
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.13.3.2 PubSubCommunicationFlowConfigurationType definition

optional Address 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 ... optional HeaderLayoutUri specifies the UADP header formats for both NetworkMessages and DataSetMessages . If HeaderLayoutUri is omitted, a fixed layout for periodic data shall be used ( http://opcfoundation.org/UA/PubSub-Layouts/UADP-Periodic-Fixed
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.13.3.3 SubscriberConfigurationType definition

optional Address specifies the network address to be used for the reception of NetworkMessages at the Subscriber of the information flow. This is an abstract type, and a concrete subtype
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.5 Interaction with an SKS

Information Model . A Publisher uses the current key to sign or sign and encrypt NetworkMessages , and Subscriber(s) to authenticate or authenticate and decrypt NetworkMessages. The past key, current
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.6.3 ConnectionConfigurationSet and ReaderGroup

DataSetReaders in a ReaderGroup can extract their DataSetMessages from different NetworkMessages . However, it is recommended that the PubSubConfiguration generated for an AutomationComponent contains a ReaderGroup for each PubSubCommunicationFlowConfiguration. By this
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.7 PubSubCommunicationFlowConfigurationConfDataType

AddressSelectionDataType Address 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 ... modified. True HeaderLayoutUri 0:String Optional HeaderLayoutUri specifies the UADP header formats for both NetworkMessages and DataSetMessages . If HeaderLayoutUri is omitted, a fixed layout for periodic data shall be used
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.8 SubscriberConfigurationConfDataType

AddressSelectionDataType Address specifies the network address to be used for the reception of NetworkMessages at the Subscriber of the information flow. True MessageReceiveTimeout 0:Duration MessageReceiveTimeout specifies the maximum acceptable