Search

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

92 result(s) for DataSetMessage

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

2.1.13 DataSetMessage

DataSetMessage payload of a NetworkMessage created from a DataSet Note 1 to entry: The DataSetMessage is an immutable payload of the 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 additional headers that may be supplied by the Message
OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts

2.1.22 NetworkMessage

supplied by the Message Oriented Middleware along the way. To avoid confusion the term DataSetMessage is used to mean the message as supplied by the Publisher for a DataSet ... term NetworkMessage is used to mean the DataSetMessage plus sections for annotation at the head and tail of the DataSetMessage
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

3.1.4 DataSetReader

Oriented Middleware Note 1 to entry: A DataSetReader is the component that extracts a DataSetMessage from a NetworkMessage received from the Message Oriented Middleware and decodes the DataSetMessage
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

3.1.5 DataSetWriter

Message Oriented Middleware Note 1 to entry: A DataSetWriter encodes a DataSet to a DataSetMessage and includes the DataSetMessage into a NetworkMessage for publishing through a Message Oriented Middleware
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.1 General

message security. In addition, the transport may supply security for certain protocol mappings. Each DataSetMessage is created from a DataSet . A component of a Publisher called DataSetWriter generates a continuous
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.2.1 General

content of a DataSet . For publishing, a DataSet will be encoded into a DataSetMessage . One or more DataSetMessages are combined to form the payload of a NetworkMessage . Figure 3 illustrates ... mechanism to encode, secure and transport it. A DataSetWriter handles the creation of a DataSetMessage for a DataSet . The DataSetWriter contains settings for the encoding and transport of a DataSetMessage
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.2.3 DataSetMetaData

Celsius, Range={1,100} Subscribers use the DataSetMetaData for decoding the values of a DataSetMessage to a DataSet . Subscribers may use name and data type for further processing or display ... published data. Each DataSetMessage also includes the version of the DataSetMetaData that it complies with. This allows Subscribers to verify if they have the corresponding DataSetMetaData . The related ConfigurationVersionDataType
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.3.1 General

security-, or encoding-specific data. To avoid confusion, this document formally defines the term DataSetMessage to mean the application data (the payload) supplied by the Publisher and the term NetworkMessage ... definitions are described in 7.3 . Subclauses 5.3.2 to 5.3.4 provide an abstract definition of DataSetMessage and NetworkMessage . The concrete structure depends on the message mapping and is described
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.3.2 DataSetMessage field

DataSetMessage field A DataSetMessage field is the representation of a DataSet field in a DataSetMessage . A DataSet field contains the actual value as well as additional information about the value ... represented as a DataValue , as a Variant or as a RawData in the DataSetMessage field. The representation depends on the DataSetFieldContentMask defined in 6.2.4.2 and the message mappings defined
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.3.3 DataSetMessage

DataSetMessage A DataSetMessage is created from a DataSet . It consists of a header and the encoded fields of the DataSet . Depending on the configured DataSetMessageContentMask , a DataSetMessage may exist ... DataSetWriter and indirectly the PublishedDataSet. Sequence number A number that is incremented for each DataSetMessage . Can be used to verify the ordering and to detect missing messages. Timestamp A timestamp
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.3.4 NetworkMessage

will be encrypted in accordance with the configured message security. Individual fields of a DataSetMessage can be marked as being "promoted fields". Such fields are intended for filtering
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.4.1.2 Message sending

based collection. In the next step, a DataSetWriter takes the DataSet and creates a DataSetMessage . DataSetMessages from DataSetWriters in one WriterGroup can be inserted into a single NetworkMessage . The creation ... DataSetMessage is guided by the following parameters: The DataSetFieldContentMask (see 6.2.4.2 ) controls which attributes of a value shall be encoded. The DataSetMessageContentMask (see 6.3.1.3.2 ) controls which header fields shall
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.4.2.1 General

filtering, decoding and dispatching of NetworkMessages . Figure 7 - Subscriber details To determine for which DataSetMessage s and on which Message Oriented Middleware to subscribe, the Subscriber need to be configured ... keys (see 5.3.5 ) to verify the signature and decrypt the relevant DataSetMessages . Once a DataSetMessage has been selected as relevant, it will be forwarded to the corresponding DataSetReader for decoding
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.4.2.2 Message reception

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 ... DataSetMessage content to a DataSet . The DataSetMetaData in particular provides the complete field syntax including the name, data type, and other relevant Properties like engineering units. Version information that exists
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.4.6.2.2 Broker-less model with OPC UA UDP

sampled data items in the Publisher OPC UA Address Space . For each DataSet a DataSetMessage is created. The DataSetMessages are sent in a NetworkMessage to the IP multicast address ... Applications like HMI applications would use the values of the DataSetMessage that they are interested in. An OPC UA Application that maps data fields from UADP DataSetMessages to internal Variables
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.4.6.3.2 Broker-based model

Variables . Such a configuration is called PublishedDataSet . Each DataSet is sent as a separate DataSetMessage serialized with a format that depends on the DataSetWriter . One DataSetMessage format is the JSON ... DataSet in a format which Subscribers can understand without knowledge of OPC UA. Another DataSetMessage format is the UADP message mapping. Message confidentiality and integrity with the Broker based communication
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.1 PubSubState state machine

DataSetReader , the state shall change to Operational after the first key frame or event DataSetMessage was received. PreOperational Disabled The component was successfully disabled. PreOperational Paused The state
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.3.1 Overview

Overview A PublishedDataSet defines the content of a DataSetMessage and the configuration of the information source for a DataSet . See 5.2 for the introduction to DataSets , 5.3 for the introduction ... different source options and the parameters for sending of DataSetMessages . The content of a DataSetMessage is defined by the DataSetMetaData. This information is required for interoperability between Publisher and Subscriber
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.3.2.4 FieldMetaData

built-in type Variant since they can result in different concrete types in a DataSetMessage . The dataType field may provide additional restrictions e.g. if the abstract type is Number . Abstract ... value in the KeyValuePair structure is the Value of the Property . If the DataSetMessage field has a Variable as source, the NodeId of the source Variable can be included
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.3.2.5 DataSetFieldFlags

header. Setting this flag increases the size of the NetworkMessages since information from the DataSetMessage body is also promoted to the header. Depending on the used security, the header including ... unencrypted. Promoted fields are always included in the header even if the DataSetMessage payload is a delta frame and the DataSet field is not included in the delta frame
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.3.7.1 PublishedData

content of a DataSet created from Variable Values and therefore the content of the DataSetMessage sent by a DataSetWriter . The sources of the DataSet fields are defined through an array
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.4.2 DataSetFieldContentMask

field related information like status and timestamp in addition to the value in the DataSetMessage . The parameter is not relevant for heartbeat messages but should be configured according ... represented as DataValue . StatusCode 0 The DataValue structure field StatusCode is included in the DataSetMessage s. If this bit is set, the fields are represented as DataValue . SourceTimestamp
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.4.3 KeyFrameCount

frame DataSetMessages contains just the changed values. If no changes exist, the delta frame DataSetMessage shall not be sent. If the KeyFrameCount is set to 1, every message contains ... custom sources with CyclicDataSet set to false provide acyclic updates. For a heartbeat DataSetMessage , the value shall
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.4.5.1 DataSetWriterDataType

defined for the transport mapping, the field shall be null. True MessageSettings DataSetWriterMessageDataType DataSetMessage mapping specific DataSetWriter parameters. The abstract base type is defined in 6.2.4.5.3 . The concrete subtypes
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.6.2 PublishingInterval

PublishingInterval . If no new DataSet is available in a PublishingInterval , then either the previous DataSetMessage is resent or no DataSetMessage is sent. In the case non-cyclic PublishedDataSets like Event
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.6.3 KeepAliveTime

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 by a DataSetWriter
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.9.6 MessageReceiveTimeout

when the state of the DataSetReader changes to Operational . If there is no new DataSetMessage received within this period, the DataSetReader State shall be changed to Error until the next ... DataSetMessage is received. The DataSetMessages that reset the period include keep-alive and heartbeat messages. A DataSetMessage is considered new if the sequence number increments or if a new keep
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.10.2.3 FieldTargetDataType

used to provide the metadata for the relation between a field in a DataSetMessage and a target Variable in a DataSetReader . The FieldTargetDataType is formally defined in Table 69 . Table ... scalar value. TargetNodeId NodeId The NodeId of the Variable to which the received DataSetMessage field value is written. AttributeId IntegerId Id of the Attribute to write e.g. the Value Attribute
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.11.1 Published data items

inside a Subscriber . The parameters and behaviour relevant for the encoding of a DataSetMessage on the Publisher side and the decoding of the DataSetMessage on the Subscriber side are defined
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.1.1.3 DataSetOrdering

DataSetMessages are ordered ascending by the value of their corresponding DataSetWriterIds and only one DataSetMessage is sent per NetworkMessage . If DataSetOrdering is Undefined any ordering between DataSets and their distribution
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.1.3.1 General

case the parameters NetworkMessageNumber and DataSetOffset provide information about the static position of the DataSetMessage in a NetworkMessage Subscribers can rely on. If the value
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.1.3.2 DataSetMessageContentMask

DataSetMessageContentMask The DataSetMessageContentMask defines the flags for the content of the DataSetMessage header. The UADP message mapping specific flags are defined by the UadpDataSetMessageContentMask DataType. The UadpDataSetMessageContentMask DataType is formally ... Timestamp 0 If this flag is set, a timestamp shall be included in the DataSetMessage header. PicoSeconds 1 If this flag is set, a PicoSeconds timestamp field shall be included
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.1.3.3 ConfiguredSize

parameter ConfiguredSize with the DataType UInt16 defines the fixed size in bytes a DataSetMessage uses inside a NetworkMessage . The default value is 0 and it indicates a dynamic length ... DataSetMessage would be smaller in size (e.g. because of the current values that are encoded) the DataSetMessage is padded with bytes with value zero. In case it would be larger
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.1.3.4 NetworkMessageNumber

DataType UInt16 is the number of the NetworkMessage inside a PublishingInterval in which this DataSetMessage is published. The default value is 0 and indicates that the number of the NetworkMessage
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.1.3.5 DataSetOffset

DataType UInt16 is the offset in bytes inside a NetworkMessage at which the DataSetMessage is located, relative to the beginning of the NetworkMessage . The default value 0 indicates that ... position of the DataSetMessage in a NetworkMessage is not fixed. If the DataSetWriter is disabled and the DataSetOffset is not 0, the valid flag of the DataSetFlags1 in the DataSetMessage
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.1.4.2 NetworkMessageNumber

DataType UInt16 is the number of the NetworkMessage inside a PublishingInterval in which this DataSetMessage is published. The default value 0 is defined as null value, and means this parameter
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.1.4.3 DataSetOffset

DataSetOffset The parameter DataSetOffset with DataType UInt16 defines the offset in bytes for the DataSetMessage inside the corresponding NetworkMessage relative to the beginning of the NetworkMessage . The default value ... defined as null value, and means that the position of the DataSetMessage in a NetworkMessage is not fixed. This parameter should be set if the PayloadHeader flag in the NetworkMessageContentMask
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.2.1.1 NetworkMessageContentMask

false, bits 3 and 4 shall be 0. DataSetMessageHeader 1 The JSON DataSetMessage header is included in each DataSetMessage . If this bit is false then the DataSetMessage header ... like FieldEncoding1 and FieldEncoding2) are applied. SingleDataSetMessage 2 Each JSON NetworkMessage contains only one DataSetMessage . PublisherId 3 The PublisherId is included in the NetworkMessage s. DataSetClassId 4 The DataSetClassId
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.2.3.1 DataSetMessageContentMask

DataSetMessageContentMask The DataSetMessageContentMask defines the flags for the content of the DataSetMessage header. The JSON message mapping specific flags are defined by the JsonDataSetMessageContentMask DataType. The JsonDataSetMessageContentMask DataType is formally ... DataSetWriterId 0 If this flag is set, a DataSetWriterId shall be included in the DataSetMessage header. MetaDataVersion 1 If this flag is set, the ConfigurationVersion is included in the DataSetMessage
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.2.3.2 JsonDataSetWriterMessageDataType structure

JsonDataSetWriterMessageDataType structure This Structure DataType is used to represent JSON DataSetMessage mapping specific DataSetWriter parameters. It is a subtype of the DataSetWriterMessageDataType defined in 6.2.4.5.3 . The JsonDataSetWriterMessageDataType is formally defined
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.2.4.3 JsonDataSetReaderMessageDataType structure

JsonDataSetReaderMessageDataType structure This Structure DataType is used to represent JSON DataSetMessage mapping specific DataSetReader parameters. It is a subtype of the DataSetReaderMessageDataType defined in 6.2.9.13.3 . The JsonDataSetReaderMessageDataType is formally defined
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.1 General

concrete message mappings and transport protocol mappings that can be used to implement them. DataSetMessage mappings, NetworkMessage mappings and transport protocol mappings are combined together to create transport profiles defined
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.2 MessageTypes

defined MessageTypes are listed in Table 151 . Table 151 - PubSub MessageTypes MessageType Description DataSetMessage Application data or events supplied by the Publisher as DataSet . DataSetMetaData Discovery message with content ... semantics of a DataSetMessage ApplicationDescription Discovery message with OPC UA application description and capabilities of the Publisher . ServerEndpoints Discovery message with the OPC UA server endpoints of the Publisher. Status
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.1 General

UADP message mapping defines different optional header fields, variations of field settings and different DataSetMessage types and data encodings. Available layouts with standard settings and the corresponding URI Strings
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.3 Error handling

DataSetMessages on the Subscriber side. The error handling for the status codes in DataSetMessage headers and DataSetMessage fields is defined in 6.2.11 and 6.2.4.2 . This handling of information flows ... messages. The one type of contract is the DataSetMetaData describing the content of a DataSetMessage . The other type of contract provides the communication settings like the DataSetWriterId or offsets inside
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.4.2 NetworkMessage layout

Message shall be one. Bit range 2-4: UADP NetworkMessage type 000 NetworkMessage with DataSetMessage payload defined in 7.2.4.4.4 . If the ExtendedFlags2 field is not provided, this is the default ... NetworkMessage type flags defined in the ExtendedFlags2 bit range 2-4. The default is DataSetMessage if the ExtendedFlags2 field is not enabled. The PayloadHeader shall be omitted
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.4.4 UADP Chunk NetworkMessage

UADP Chunk 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 ... defined in Table 159 . A chunk NetworkMessage can only contain chunked payload of one DataSetMessage . If a NetworkMessage payload with a discovery announcement message has to be split across multiple
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.5.1 General

other parts of the NetworkMessage are shown in Figure 33 . Different types of DataSetMessage can be combined in on NetworkMessage . Figure 33 - UADP DataSet payload
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.5.2 DataSet payload header

Number of DataSetMessages contained in the NetworkMessage . The NetworkMessage shall contain at least one DataSetMessage if the NetworkMessage type is DataSetMessage payload. DataSetWriterIds UInt16 [Count] List of DataSetWriterIds contained
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.5.3 DataSet 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 . This field shall ... count is one or if bit 6 of the UADPFlags is false. DataSetMessages DataSetMessage [Count] DataSetMessages contained in the NetworkMessage . The size of the list is defined by the Count
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.5.4 DataSetMessage header

DataSetMessage header The DataSetMessage header structure and the relation to other parts in a NetworkMessage is shown in Figure 34 . Figure 34 - DataSetMessage header structure The encoding of the DataSetMessage ... flags shall not change until the configuration of the DataSetWriter is changed. Table 162 - DataSetMessage header structure Name Type Description DataSetFlags1 Byte Bit 0: DataSetMessage is valid. If this
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.5.5 Data Key Frame DataSetMessage

Data Key Frame DataSetMessage The data key frame DataSetMessage data and related headers are shown in Figure 35 . Figure 35 - Data Key Frame DataSetMessage data The encoding of the data ... frame DataSetMessage structure is specified in Table 163 . If the key frame is a heartbeat DataSetMessage , only the header is encoded but the following structure shall not be encoded into
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.5.6 Data Delta Frame DataSetMessage

Data Delta Frame DataSetMessage The data delta frame DataSetMessage data and the related headers are shown in Figure 36 . Figure 36 - Data Delta Frame DataSetMessage The information for a single ... larger than a key frame message. The encoding of the data delta frame DataSetMessage structure is specified in Table 164 . Table 164 - Data Delta Frame DataSetMessage structure Name Type Description
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.5.7 Event DataSetMessage

Event DataSetMessage The Event DataSetMessage data and the related headers are shown in Figure 37 . Figure 37 - Event DataSetMessage The encoding of the Event DataSetMessage structure is specified in Table ... Table 165 - Event DataSetMessage structure Name Type Description FieldCount UInt16 Number of fields of the DataSet contained in the DataSetMessage . DataSetFields BaseDataType [FieldCount] The field values of the DataSet
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.5.9 Action request message

Action request message The encoding of the Action request DataSetMessage structure is specified in Table 166 . Table 166 - Action request message structure Name Type Description ActionTargetId UInt16 The numeric identifier ... defined in 6.2.11.2 . FieldCount UInt16 Number of fields of the DataSet contained in the DataSetMessage . DataSetFields BaseDataType [FieldCount] The field values of the ActionRequest DataSet. The fields of ActionRequest DataSetMessages
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.5.10 Action response message

Action response message The encoding of the Action response DataSetMessage structure is specified in Table 167 . Table 167 - Action response message structure Name Type Description ActionTargetId UInt16 The numeric identifier ... defined in 6.2.11.2 . FieldCount Uint16 Number of fields of the DataSet contained in the DataSetMessage . DataSetFields BaseDataType [FieldCount] The field values of the ActionResponse DataSet. The fields of ActionResponse DataSetMessages
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.5.11 RawData field encoding

RawData field encoding The encoding of the DataSetMessage fields is handled like a Structure DataType where the DataSet fields are handled like Structure fields and fields with Structure DataType ... handling shall be applied to ensure a fixed offset of the fields in the DataSetMessage . If the DataType of a DataSet field or a Structure field is String or ByteString
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.6.4 DataSetMetaData

contains the current layout and DataSetMetaData for the DataSet . The ConfigurationVersion in the DataSetMessage header shall match the ConfigurationVersion in the DataSetMetaData . The Publisher shall send this message without
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.3 NetworkMessage containing DataSetMessages

associated with the DataSetWriters that produced the DataSetMessages. Messages * A JSON array of JSON DataSetMessage s (see 7.2.5.4 ) or a JSON object if SingleDataSetMessage is set. This value is always ... Messages field is an array of content from the Payload field for each DataSetMessage (see 7.2.5.4 ). If the SingleDataSetMessage bit of the NetworkMessageContentMask is set, the content of the Messages
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.4.1 Message content

Message content A DataSetMessage is produced by a DataSetWriter and contains list of name/value pairs which are specified by the PublishedDataSet associated with the DataSetWriter . The contents of the DataSetMessage ... formally described by a DataSetMetaData Object. A DataSetMessage is a JSON object with the fields defined in Table 185 . A key frame DataSetMessage or an event based DataSetMessage contains name
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.4.2 VerboseEncoding

Variants at the top level are collapsed. Therefore the DataSet fields in a DataSetMessage for VerboseEncoding are encoded like the fields of a Structure where the fields are described ... rules of VerboseEncoding defined in OPC 10000-6 apply. The following example shows a DataSetMessage with VerboseEncoding and DataSet fields without field specific status and timestamps. { "PublisherId
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.5.2 DataSetMetaData

data types of the values that shall appear in the Payload of a DataSetMessage. When the DataSetMetaData of a DataSet changes, the DataSetWriter may be configured to publish the updated ... mechanism defined by the transport protocol mapping. The DataSetWriterId and Version fields in a DataSetMessage are used to correlate a DataSetMessage with a DataSetMetaData. A NetworkMessage with MessageType DataSetMetaData
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.6.2 ActionRequest

PublisherId and the DataSetWriterId . DataSetWriterName String The name of the DataSetWriter which created the DataSetMessage . The presence of the value depends on the setting in the JsonDataSetMessageContentMask . WriterGroupName String ... name of the WriterGroup which created the DataSetMessage . The presence of the value depends on the setting in the JsonDataSetMessageContentMask . The value shall be omitted if the WriterGroupName is contained
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.6.3 ActionResponse

PublisherId and the DataSetWriterId . DataSetWriterName String The name of the DataSetWriter which created the DataSetMessage . The presence of the value depends on the setting in the JsonDataSetMessageContentMask . WriterGroupName String ... name of the WriterGroup which created the DataSetMessage . The presence of the value depends on the setting in the JsonDataSetMessageContentMask . The value shall be omitted if the WriterGroupName is contained
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.3.4.1 General

payloads. This document defines two possible encodings for the message body: the binary encoded DataSetMessage defined in 7.2.3 and a JSON encoded DataSetMessage defined in 7.2.4.6.9 . MQTT version 3.1.1 does
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.3.4.8 Message header

assumed to be a MQTT User Property and if the NetworkMessage contains only one DataSetMessage . The MQTT message header shall include additional promoted fields of the DataSet as a list ... UADP NetworkMessage . Promoted fields shall always be included in the header even if the DataSetMessage body is a delta frame and the DataSet field is not included in the delta
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.1 General

snapshot of the Variables comprises a DataSet . A DataSet is the content of a DataSetMessage created by a DataSetWriter . Examples of concrete PublishedDataSetTypes are PublishedEventsType and PublishedDataItemsType . An instance
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.4.1 Overview

Overview A PublishedDataSet defines the content of a DataSetMessage and the configuration of the information source for a DataSet . See 5.2 for the introduction to DataSets , 5.3 for the introduction
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.4.2.1 PublishedDataSetType

based on a DataSetClass . The MajorVersion part of the ConfigurationVersion contained in the DataSetMessage needs to match the ConfigurationVersion of the DataSetMetaData available on the Subscriber side. The DataSetClassId
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.4.2.2 ExtensionFieldsType

BaseDataType The DataSetWriterId from the DataSetWriterTransport Object . MessageSequenceNumber UInt16 The sequence number from the DataSetMessage . If a well-known name is used, the value placed in the message body
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.4.3.2 AddVariables Method

DataSetMetaData . PromotedFields The flags indicating if the corresponding field is promoted to the DataSetMessage header. The size and the order of the array shall match the VariablesToAdd . The flag
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.4.4.2 ModifyFieldSelection Method

DataSetMetaData . PromotedFields The flags indicating if the corresponding field is promoted to the DataSetMessage header. The size and the order of the array shall match the SelectedFields . The flag
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.8.2 DataSetReaderType

metadata for the subscribed DataSet and the information for the processing of a DataSetMessage . The SubscribedDataSetType and the available subtypes are defined in 9.1.9 . If the DataSetReader is configured
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.11.11 PubSubDiagnosticsDataSetWriterType

Modelling Rule Diagnostics Level DataType Description MessageSequenceNumber Optional Info UInt16 Sequence number of last DataSetMessage StatusCode Optional Info StatusCode Status of last DataSetMessage MajorVersion Optional Info UInt32 MajorVersion used
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.11.12 PubSubDiagnosticsDataSetReaderType

BrowseName Modelling Rule Diagnostics Level DataType Description MessageSequenceNumber Optional Info UInt16 SequenceNumber of last DataSetMessage StatusCode Optional Info StatusCode Status of last DataSetMessage MajorVersion Optional Info UInt32 MajorVersion of available
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.1.2 Overview

NetworkMessage is the same in every PublishingInterval The layout of the fields within every DataSetMessage is the same in every PublishingInterval Note: These assumptions have to be fulfilled by appropriate
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.1.7 Header layout for DataSetMessages

A.2.1.7 Header layout for DataSetMessages A UADP DataSetMessage header shall consist of the following fields according to this header layout: DataSetFlags1 DataSetMessageSequenceNumber Status Additional restrictions: Fields within the payload ... RawData Field Encoding Only data key frame DataSetMessages are supported The DataSetMessage header layout is shown in Figure A.4 . Figure A.4 - UADP DataSetMessage header layout Table A.5 shows the configuration
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.1.8 Example fixed message layout without security

DataSetWriter and WriterGroup settings. The configuration has to ensure that the size of each DataSetMessage is constant. This can be achieved by avoiding DataSet fields of types with variable size ... using the parameter ConfiguredSize . In this example it is assumed that DataSetMessage[1] and DataSetMessage[W-1] are using RawData field encoding and all DataSet fields are from constant size
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.2.2 Overview

DataSetMessages . In contrast to the fixed layout, more header fields are enabled in the DataSetMessage header with this header layout but the GroupHeader is deactivated
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.2.7 Header layout for DataSetMessages

A.2.2.7 Header layout for DataSetMessages A UADP DataSetMessage header shall consist of the following fields according to this header layout: DataSetFlags1 DataSetFlags2 DataSetMessageSequenceNumber Timestamp Status MinorVersion Additional remarks: Fields ... types of DataSetMessages (Data Key Frame, Data Delta Frame, Event, etc.) are supported The DataSetMessage header layout is shown in Figure A.10 Figure A.10 - UADP DataSetMessage header layout Table A.11
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.2.8 Example dynamic message layout with different DataSetMessage types

A.2.2.8 Example dynamic message layout with different DataSetMessage types Figure A.11 shows an example for a UADP NetworkMessage with dynamic layout. As defined in A.2.2.3 and A.2.2.7 only the layout ... NetworkMessage header and the DataSetMessage header is fixed. The number, the type, the length, and the order of DataSetMessages can vary from one NetworkMessage to the next. Figure A.11 - Example
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.3.2.1 Motivation

case, the messages that are sent to the message queue can only contain one DataSetMessage and there should be no OPC UA specific information or header. The header layout described
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.3.2.2 Overview

A.3.2.2 Overview A minimal message has the following settings: Each NetworkMessage contains one DataSetMessage The NetworkMessage header is not included The DataSetMessage header is not included The DataSet field encoding
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.3.3.2 Overview

A.3.3.2 Overview A single DataSet message has the following settings: Each NetworkMessage contains one DataSetMessage The NetworkMessage header is not included The DataSetMessage header is included, the header fields
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.3.4.2 Overview

DataSetMessages The NetworkMessage header is included, the header fields can be configured The DataSetMessage header is included, the header fields can be configured The DataSet field encoding can be configured
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

B.3.7 Message header

message-absolute-expiry-time ( Duration ) from the DataSetWriterProperties to the current time of the DataSetMessage creation. Group-id String string reply-to-group-id String string creation-time Boolean timestamp ... creation-time is set to the current time of the DataSetMessage creation if the message-creation-time ( Boolean ) in the DataSetWriterProperties is True, or else if the value is False
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

D.3.4 Header layout for DataSetMessages

D.3.4 Header layout for DataSetMessages A UADP DataSetMessage header shall consist of the following fields according to this header layout: DataSetFlags1 DataSetFlags2 Additional remarks: Field is encoded as a Variant ... DataSetMessages (Data Key Frame, Data Delta Frame, Keep Alive, etc.) are supported The DataSetMessage header layout is shown in Figure D.4 . Figure D.4 - UADP DataSetMessage header layout Table D.7 shows
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

6.3.7 CustomMetaDataProperties Property

semantics of a DataSet . Subscribers use this metadata to interpret the DataSet from the DataSetMessage and can evaluate the Properties field of the FieldMetaData Structure
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.5.6.2.5 DataSetMetaData

contract between the Publisher and the Subscriber , including how to encode and decode the DataSetMessage . Thus, Subscribers must know about the PublishedDataSet's DataSetMetaData . For the concepts of the DataSetMetaData
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.4.7 PubSub DataSets

include information like a timestamp and/or status information (see Figure E.17 ). Figure E.17 - DataSetMessage header The DataSetMessage can use the periodic fixed mapping, depending on the communication options selected ... status) or a DataValue (value, status, and timestamps) encoding. Figure E.18 - Fixed DataSetMessage Other PubSub Profiles can include a dynamic layout. In this case, the DataSetMessage can also
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.6.4 ConnectionConfigurationSet and DataSetWriter

derived from the HeaderLayoutUri . For UADP-Periodic-Fixed ConfiguredSize, NetworkMessageNumber and DataSetOffset of the DataSetMessage are determined by the generator of the PubSubConfiguration . For UADP-Periodic-Fixed, the KeyFrameCount
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.6.5 ConnectionConfigurationSet and DataSetReader

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 a custom SubscribedDataSet within ... derived from the HeaderLayoutUri . For UADP-Periodic-Fixed, the NetworkMessageNumber and DataSetOffset of the DataSetMessage are determined by the generator of the PubSubConfiguration . ReceiveOffset and ProcessingOffset