IoT Pub-Sub Gateway for OPC UA Protocol Conversion

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Updating OPC UA software on IoT devices, such as industrial robots, can cause downtime and disrupt continuous operations, as existing communication models like client-server limit parallel connections and resource efficiency, especially when transitioning to new pub-sub models.

Innovation Solution

Implementing a publisher computer that converts data from IoT devices using the current client-server model to the anticipated OPC UA pub-sub model, allowing data transmission to the cloud without altering the IoT device's communication software, thereby enabling the benefits of pub-sub communication without downtime.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If OPC UA software is updated on IoT devices to implement pub-sub functionality, then the system gains access to newer communication model benefits, but the devices become non-operational during the update period

Engineering Contradiction:
Improvecommunication model capabilityVSAvoidoperational continuity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system is segmented into two independent parts: the legacy client-server communication stack that remains unchanged on the device, and the new pub-sub functionality that is introduced through a separate gateway component. This segmentation allows the device to maintain its original operational reliability while the gateway provides enhanced communication model capabilities.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A gateway component is introduced as an intermediary between the IoT device and the pub-sub network. The gateway translates client-server communications from the device into pub-sub format, enabling the device to benefit from the new communication model without requiring software updates that would disrupt operations.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If a gateway is introduced to enable pub-sub communication without device software updates, then operational continuity is maintained, but system complexity increases

Engineering Contradiction:
Improveoperational continuityVSAvoidsystem architecture
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The gateway serves as a centralized intermediary that handles all translation and protocol conversion tasks. By concentrating the complexity in a single external component rather than distributing it across multiple devices, the overall system architecture becomes more manageable while maintaining operational continuity.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If client-server model is used for data transmission, then device software remains simple and stable, but resource efficiency and parallel connection capability are limited

Engineering Contradiction:
Improvesoftware stabilityVSAvoidresource efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The communication functionality is segmented into the simple, stable client-server implementation on the device side and the resource-efficient pub-sub implementation on the gateway side. This allows each component to operate in its optimal performance regime without compromising stability or efficiency.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The gateway acts as an intermediary that translates resource-intensive client-server interactions into efficient pub-sub communications. This translation enables the device to maintain simple stable software while the gateway optimizes resource efficiency and parallel connection handling.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11323519B2Internet of things pub-sub data publisher
Publication Date: 2022.05.03 MICROSOFT TECHNOLOGY LICENSING LLC
  • US11323519B2 patent drawing
  • US11323519B2 patent drawing
  • US11323519B2 patent drawing

AI summary

An Internet of Things (IoT) system may include a publisher computer connected to IoT devices. The publisher computer may execute operations to provide data for the IoT devices to a remote computer which may be included in a cloud infrastructure. The publisher computer can receive data from the IoT devices, convert the data to a publisher-subscriber format that conforms to a predetermined specification, and transmit the data to the cloud infrastructure or other remote computers.