Object-Oriented Internet
Executive SummarySemantic-Data Processing ArchitectureInternet of Things (IoT) Archetype Reactive Communication
Search…
Executive Summary
Table of Content
Introduction
Introduction to Object-Oriented Internet
Introduction to Complex Data Processing
OPC Unified Architecture
OPC UA Main Technology Features
Semantic-Data Processing
Semantic-Data Processing Architecture
Address Space and Address Space Model
UA Information Model - Concept
Information Models Development
Address Space Management Implementation
Address Space Prototyping Tool (asp.exe)
Internet of Things (IoT) Archetype
Semantic-Data Message Centric Communication
Internet of Things (IoT) Communication
Reactive Communication
UA Part 14: PubSub Main Technology Features
Reactive Networking of Semantic-Data Library
Underlying Transport over UDP
Underlying Transport over MQTT
Underlying Transport over AMQP
Underlying Transport over Ethernet
DataSet and Communication Channel Association
Encoding Library
Getting Started Tutorial
Walk-through ReferenceApplication
Configuration
Configuration - Executive Summary
Global Data Discovery
Concept
Domain Model
References
See also
Powered By GitBook
DataSet and Communication Channel Association
The diagram below provides a very generic overview of the responsibilities that must be implemented by the UA Application:
Architecture
  • UA Data Networking - represents a software exchanging the data using protocol compliant with the UA Part 14 Pub/Sub and binding the data with the underlying process.
  • MessageHandler - represents a selected transport protocol supporting unsolicited data distribution or a middle-ware supporting publication/subscription message exchange communication pattern.
  • DataSet - represents a preselected collection of process data items transmitted by the MessageHandler as one whole and information required to bind with the underlying process.
  • MessageReader - captures functionality necessary to filter out unwanted messages and decode the data according to provided meta-data
  • MessageWriter - captures functionality necessary to address the message (provide globally unique identifier) and encode the data using provided meta-data
  • Association - provides:
    1. 1.
      one to one association between an entity instance derived from MessageHandler and DataSet
    2. 2.
      required addressing information as the PublisherId/DataSetWriterId couple
    3. 3.
      meta-data information used to encode/decode the process data into the messages
Previous
Underlying Transport over Ethernet
Next
Encoding Library
Last modified 4yr ago
Copy link