IoT Gateway Policy Configuration for Flexible Data Transmission

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing IoT gateways require source code modifications to adapt to changing application scenarios, posing challenges in system maintenance and flexibility.

Innovation Solution

An IoT gateway with configurable data transmission mode, utilizing adjustable data policies for the data collector, capturer, and uploader, allowing flexible data handling without modifying source codes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If source code modifications are made to adapt to changing application scenarios, then the system can handle different data transmission requirements, but system maintenance complexity and development time increase

Engineering Contradiction:
Improveadaptability to changing application scenariosVSAvoidsystem maintenance complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements dynamic configuration capabilities where data collection frequency, upload triggers, and transmission parameters can be adjusted in real-time through configuration files rather than code modifications. The system transitions from static hard-coded behavior to dynamic configurable behavior, allowing adaptation to different scenarios without changing source code.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes operational parameters such as data gathering intervals, upload thresholds, and transmission timing through configuration settings rather than modifying the core system code. This allows the same software to adapt to different application requirements by simply changing parameters like collection frequency or upload triggers.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If separate configuration settings are used for data collector and uploader, then flexibility in data handling is improved, but system complexity increases

Engineering Contradiction:
Improveflexibility in data handlingVSAvoidsystem structure complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges the configuration management functionality into a unified policy framework that handles both data collection and upload operations through a single policy engine. Instead of separate configuration systems, a integrated policy management approach coordinates both collector and uploader settings through common configuration mechanisms.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent creates a universal policy management system that serves multiple functions: configuring data collection intervals, setting upload triggers, defining transmission parameters, and managing error handling all through a single configurable framework. This multi-functional approach reduces overall system complexity despite providing flexible data handling capabilities.

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

Data Source

PatentEP4030737B1IoT gateway with configurable data transmission mode
Publication Date: 2025.12.24 MOXA INC
  • EP4030737B1 patent drawingFigure 1
  • EP4030737B1 patent drawingFigure 2
  • EP4030737B1 patent drawingFigure 3

AI summary

An IoT gateway (300, 400) with configurable data transmission mode includes a data collector (30), a data capturer (40, 40_1, 40_2) and a data uploader (50, 50_1, 50_2). The data collector (30) is configured to collect the data provided by a data provider (10, 10_1, 10_2, 10_3) based on a first data policy (S1). The data capturer (40, 40_1, 40_2) is configured to capture the data collected by the data collector (30) based on a second data policy (S2). The data uploader (50, 50_1, 50_2) is configured to handle the data captured by the data capturer (40, 40_1, 40_2) based on a third data policy (S3). The first data policy (S1), the second data policy (S2) and the third data policy (S3) may be configured separately according to different IoT applications.