IoT Gateway Data Flow Rules for Network Congestion Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Industrial Internet of Things (IIoT) systems face challenges in managing and controlling data flows efficiently, leading to potential network congestion and data transfer disruptions due to the vast amount of data being transmitted from connected devices.

Innovation Solution

Implementing data flow rules that determine which data to send and when, using a hierarchical architecture with global cloud, enterprise, and device levels, where equipment models and data flow rules are defined to manage data transmission and conversion across different nodes and devices, enabling centralized management and edge computing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data transmission from all connected devices is allowed without control, then complete information exchange is achieved, but network congestion and data transfer disruptions occur

Engineering Contradiction:
Improvedata transfer reliabilityVSAvoiddata transmission efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments data flows into different categories (upstream, downstream, peer-to-peer) and applies specific rules to each type. Data flow rules are divided into sending rules and receiving rules, allowing granular control over different data transmission scenarios while maintaining overall system reliability

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces data flow rules as intermediary mechanisms that mediate between data sources and destinations. These rules act as filters and controllers that determine which data packets are transmitted, preventing network congestion while ensuring reliable delivery of authorized data

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If data flow control rules are implemented, then network congestion is reduced, but data transmission complexity increases

Engineering Contradiction:
Improvedata transmission efficiencyVSAvoiddata flow management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent creates universal data flow rule templates that can be applied across multiple devices and scenarios. Equipment models serve as reusable blueprints that define data flow characteristics, allowing the same rule structures to manage diverse data transmission needs without creating unique complexity for each case

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

Solution Approach 2:

The patent manages complexity by parameterizing data flow rules with configurable attributes such as data types, transmission directions, frequencies, and conditions. This allows flexible adaptation to different scenarios through parameter adjustment rather than structural redesign, simplifying overall system management

Inventive Principle:
Principle #35Parameter changes

3Loss of information

If all data is transmitted without filtering, then complete information availability is achieved, but network resources are wasted

Engineering Contradiction:
Improveinformation completenessVSAvoidnetwork resource consumption
Core Design Contradiction:
Loss of informationVSLoss of energy

Solution Approach 1:

The patent extracts and transmits only the essential and relevant data packets based on predefined rules, filtering out redundant or low-priority information. This extraction approach ensures that critical information is delivered while unnecessary data transmission is eliminated, conserving network resources

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies partial action by transmitting only the necessary subset of data rather than all available data. Data flow rules determine the optimal level of data transmission needed for each scenario, avoiding excessive transmission that would waste network resources while maintaining sufficient information completeness

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS11233769B2Rule-based information exchange in internet of things
Publication Date: 2022.01.25 ABB (SCHWEIZ) AG
  • US11233769B2 patent drawing
  • US11233769B2 patent drawing
  • US11233769B2 patent drawing

AI summary

For data flow traffic in an IoTSP system, for example, a gateway is provided with data flow rules, one or more of the data flow rules being a receiving rule defining at least what incoming data will be accepted and one or more of the data flow rules being a publishing rule defining at least what data to send to one or more other computing devices acting as gateways in the system. The one or more receiving rules are applied to incoming data, and the one or more publishing rules to stored and processed data to cause sending one or more pieces of the data in response to a condition in a publishing rule being fulfilled.