0004244: Part 14 PubSub - Section 5.4 should describe Configuration Services. - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update

0004244	10000-014: PubSub	Api Change	public	2018-04-14 21:01	2021-03-30 16:27

Reporter	Mariusz Postol	Assigned To	Matthias Damm
Priority	low	Severity	major	Reproducibility	N/A
Status	closed	Resolution	fixed
Platform	Any	OS	ANy	OS Version	Any

Summary	0004244: Part 14 PubSub - Section 5.4 should describe Configuration Services.
Description	The mentioned section describes the following active actors called Entities (?): Publisher Subscriber Security Key Service It should also describe the Configuration Services called also Configuration Tool. The terminology should be harmonized. It is also not clear the relationship between the OPC UA Information Model definition and the place where the services are implemented. For example, the Publisher can be OPC UA Server or Client. In both scenarios, the model has to be different - what is the behaviour of the SetSecurityKeys methods if the model is exposed by an external OPC UA Server. The specification has to define clearly the relationship between these Services and the underlying Session-oriented OPC UA connectivity. The section must not define the passive Message Oriented Middleware used just as messages transport infrastructure. It is not the active actor managing the messages exchange process.
Tags	No tags attached.

Commit Version
Fix Due Date

Matthias Damm 2021-03-03 14:31 developer ~0013928	5 PubSub Concepts 5.1 General Added "Configuration Tool" to overview figure 2. Added following text: Publishers and Subscribers are typically configured through a configuration tool. The configuration can be done through a generic OPC UA PubSub configuration tool using the PubSub configuration Information Model defined in Clause 9 or through product-specific configuration tools. To support the PubSub configuration Information Model, Publishers and Subscribers must be also OPC UA Server. Added: 5.4.3 Configuration Tool OPC UA Application can be pre-configured to send messages as Publisher but commonly there is the requirement to configure the information to be included into messages and also the frequency the messages are sent. Subscribers can use discovery mechanisms to find Publishers and to get the DataSetMetaData necessary to understand the messages. One example are HMI applications where the configuration can be done inside the Subscriber. But if the Subscriber is a device, it is expected that a configuration tool is required to configure the Subscriber functionality in the device. The PubSubConfigurationDataType and the other configuration Structures defined in Clause 6 can be used to prepare a offline PubSub configuration that can be stored in a binary file using the UABinaryFileDataType. Such a configuration can be used to configure Publishers and Suscribers if they do not have a online configuration interface or the are configured through product-specific configuration tools. If Publishers and Suscribers are also OPC UA Servers, they can provide the PubSub configuration Information Model defined in Clause 9. This model can be used by generic PubSub configuration tools. A typical use case is controller to controller or machine to machine communication where both communication partners have a pre-configured list of input and output data Variables and a generic 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 the target Variables in the Subscriber. Added in OPC 10000-14 - UA Specification Part 14 - PubSub 1.05.0 Draft31.docx

Jim Luth 2021-03-30 16:27 administrator ~0014136	Agreed to changes edited in telecon.

Date Modified	Username	Field	Change
2018-04-14 21:01	Mariusz Postol	New Issue
2018-04-24 14:18	Jim Luth	Project	UA => 10000-014: PubSub
2018-04-24 14:18	Jim Luth	Category	Documentation Errata => Api Change
2018-08-28 16:23	Jim Luth	Assigned To	=> Matthias Damm
2018-08-28 16:23	Jim Luth	Status	new => assigned
2021-03-03 14:31	Matthias Damm	Status	assigned => resolved
2021-03-03 14:31	Matthias Damm	Resolution	open => fixed
2021-03-03 14:31	Matthias Damm	Note Added: 0013928
2021-03-30 16:27	Jim Luth	Status	resolved => closed
2021-03-30 16:27	Jim Luth	Fixed in Version	=> 1.05
2021-03-30 16:27	Jim Luth	Note Added: 0014136