Docker Microservice Gateway for IoT Protocol Adaptation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing IoT systems face challenges with high communication infrastructure costs and insufficient bandwidth due to the time-consuming data transfer process from industrial equipment to cloud servers, necessitating a flexible and efficient solution for managing various legacy communication interfaces.

Innovation Solution

A microservice-based device control interface system utilizing a Docker registry server and gateway, where resources are installed and managed using a Docker-based microservice structure, allowing for flexible interface changes and protocol adaptation, enabling efficient communication through a single gateway with edge computing capabilities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If data is transferred from industrial equipment to cloud servers through traditional gateway infrastructure, then data transfer functionality is provided, but communication bandwidth is insufficient and transfer time is excessive

Engineering Contradiction:
Improvedata transfer speedVSAvoiddata transfer time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent segments the monolithic gateway functionality into multiple independent Docker containers, each handling specific communication protocols or data processing tasks. This modular architecture enables parallel data processing across multiple containers, significantly increasing throughput and reducing transfer time compared to traditional sequential processing in single gateway systems.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a new dimensional approach by implementing edge computing capabilities directly within the gateway infrastructure through Docker-based microservices. This allows data processing to occur at the network edge rather than requiring complete transmission to cloud servers, effectively adding a spatial dimension (edge vs. cloud) that reduces transfer time and bandwidth requirements.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Reliability

If traditional gateway infrastructure is used for data transfer, then basic connectivity is established, but communication infrastructure cost is high

Engineering Contradiction:
Improvecommunication connectivityVSAvoidcommunication infrastructure cost
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent creates a universal gateway platform using Docker containers that can handle multiple communication protocols (Modbus, OPC UA, MQTT, etc.) and various data processing functions within a single infrastructure. This multi-functional approach eliminates the need for separate hardware gateways for each protocol, significantly reducing infrastructure costs while maintaining reliable connectivity across diverse industrial equipment.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent uses Docker container technology to create virtual copies of gateway functionality for different protocols and processing requirements. Instead of purchasing and deploying multiple physical gateway devices, the system replicates gateway capabilities through software containers, reducing hardware costs while maintaining the reliability needed for industrial communications.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If multiple gateways or additional modules are deployed to handle various communication protocols, then protocol compatibility is improved, but device complexity increases

Engineering Contradiction:
Improveprotocol compatibilityVSAvoidgateway configuration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a dynamic gateway system where Docker containers can be added, removed, or modified based on real-time communication requirements. This dynamic architecture allows the gateway to adapt to different protocols and devices without requiring complex static configuration, as new capabilities can be introduced by simply deploying new containers rather than reconfiguring existing hardware.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent introduces Docker container technology as an intermediary layer between the physical gateway hardware and the various communication protocols. This intermediary abstraction simplifies protocol compatibility by standardizing how different protocols are handled within containers, reducing the complexity of direct hardware-protocol mappings that would otherwise require complex configuration and multiple specialized modules.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Adaptability or versatility

If legacy communication interfaces are supported through traditional methods, then interface compatibility is maintained, but system flexibility is reduced

Engineering Contradiction:
Improveinterface flexibilityVSAvoidinterface management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments legacy interface support into independent Docker containers, each dedicated to a specific communication protocol or interface type. This segmentation isolates interface management complexity into manageable units that can be configured and maintained independently, while the overall system gains flexibility through the ability to add or remove interface support by deploying or removing specific containers.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11277495B2System and method for providing microservice-based device control interface
Publication Date: 2022.03.15 ELECTRONICS & TELECOMM RES INST
  • US11277495B2 patent drawing
  • US11277495B2 patent drawing
  • US11277495B2 patent drawing

AI summary

Provided are a system and method for providing a microservice-based device control interface. The system for providing a microservice-based device control interface includes a Docker registry server in which resources required for providing a device control interface are located and a gateway which receives and installs resources and provides a device control interface using a Docker-based microservice structure.