PubSubdefines different configuration parameters for the various PubSubcomponents. They define the behaviour of Publisherand Subscriber. The parameters are grouped by component and are partitioned into ‘common’, ’message mapping’, and ‘transport protocol mapping’.

The common parameters are defined in 6.2. The parameters for the different message mappings are defined in 6.3. The parameters for the different transport protocol mappings are defined in 6.4.

The application of communication parameters for concrete message and transport protocol mappings is defined in clause 7.

Configuration of these parameters can be performed through the OPC UA Information Modelfor PubSubconfiguration defined in clause 9or through vendor-specific mechanisms. The parameter groupings in this clause define the parameters and also define Structuresused to represent the parameters of the groupings. These Structuresare used in the PubSubconfiguration model described in clause 9but they can also be used for offline configuration or vendor-specific configuration mechanisms.

Figure 17depicts the different components and their relation to each other. The WriterGroup, DataSetWriterand PublishedDataSetcomponents define the data acquisition for the DataSets, the message generation and the sending on the Publisherside. These parameters need to be known on the Subscriberside to configure DataSetReadersand to filter and process DataSetMessages.


Figure 17– PubSub Component Overview

The figure shows the following components:

The different PubSub mapping specific parameter groupings are shown in Figure 18.


Figure 18– PubSub Mapping Specific Parameters Overview

Transport protocol mapping specific parameters may be defined for the PubSubConnection, the WriterGroupor the DataSetWriter.

Message mapping specific parameters are defined for the NetworkMessageson the WriterGroupand for the DataSetMessageson the DataSetWriter.