IoT Gateway Segmentation for Persistent Connection Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current Internet of Things (IoT) service solutions face high resource overheads and performance degradation due to maintaining persistent network connections between IoT devices and IoT HUBs, leading to excessive memory and heartbeat processing burdens, especially in large-scale scenarios.

Innovation Solution

Implementing a dual-layer IoT gateway architecture where a persistent connection is maintained between a terminal device and a network access stratum device, while a short connection is maintained between the network access stratum device and a message forwarding device, allowing the network access stratum device to manage persistent network connections and decouple message processing from the message forwarding device.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a persistent network connection is maintained between terminal devices and IoT HUB, then message pushing service can be provided, but resource overheads on the server increase excessively

Engineering Contradiction:
Improvemessage pushing serviceVSAvoidresource overhead
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system is segmented into two layers: network access layer devices that maintain persistent connections with terminal devices, and message forwarding layer devices that handle message routing. This segmentation allows the persistent connection maintenance overhead to be distributed to edge devices rather than concentrated on the central IoT HUB server.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Network access layer devices act as intermediaries between terminal devices and the IoT HUB. These intermediaries maintain persistent connections with terminals and forward messages to the HUB only when needed, eliminating the need for the HUB to maintain persistent connections with all terminals directly.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Stability of the object's composition

If persistent network connections are maintained for heartbeat processing, then connection stability is improved, but memory overheads on the server increase

Engineering Contradiction:
Improveconnection stabilityVSAvoidmemory overhead
Core Design Contradiction:
Stability of the object's compositionVSQuantity of substance

Solution Approach 1:

Connection management functions are segmented and distributed to network access layer devices. These devices maintain persistent connections and handle heartbeat processing locally, preventing memory overhead accumulation on the central server while maintaining connection stability at the edge.

Inventive Principle:
Principle #1Segmentation

3Reliability

If persistent connections are maintained for all terminal devices, then message delivery reliability is improved, but system performance deteriorates

Engineering Contradiction:
Improvemessage delivery reliabilityVSAvoidsystem performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system separates connection management responsibilities from message forwarding responsibilities. Network access layer devices handle persistent connections and heartbeats, while the message forwarding layer handles only message routing. This segmentation maintains delivery reliability through persistent connections while preserving system performance by eliminating redundant heartbeat processing at the message forwarding layer.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Network access layer devices serve as intermediaries that absorb the performance cost of maintaining persistent connections and handling heartbeats, allowing the message forwarding layer to operate efficiently without being burdened by connection maintenance overhead.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Device complexity

If the IoT HUB directly manages persistent connections with terminal devices, then message routing is simplified, but device complexity increases

Engineering Contradiction:
Improveconnection management complexityVSAvoidmessage routing
Core Design Contradiction:
Device complexityVSEase of operation

Solution Approach 1:

Connection management and message routing are segmented into different functional layers. The network access layer handles persistent connection management, while the message forwarding layer handles message routing using simple forwarding rules. This segmentation reduces overall system complexity by distributing responsibilities appropriately.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentEP3720094B1Information processing method, apparatus, device and system
Publication Date: 2022.11.30 ADVANCED NEW TECHNOLOGIES CO LTD
  • EP3720094B1 patent drawingFigure 1
  • EP3720094B1 patent drawingFigure 2
  • EP3720094B1 patent drawingFigure 3~4

AI summary

Implementations of the present specification disclose an information processing method, apparatus, device, and system. The method is applied to a network access stratum device, a persistent connection is maintained between the network access stratum device and a terminal device, and a short connection is maintained between the network access stratum device and a message forwarding device. The method includes: receiving an uplink message sent by the terminal device; encapsulating the uplink message and a session identifier of the persistent connection maintained between the network access stratum device and the terminal device into a target message corresponding to a short connection; sending the target message to the message forwarding device, and receiving a downlink message corresponding to the target message and sent by the message forwarding device, where the downlink message includes the session identifier; determining a receiving device of the downlink message based on the session identifier; and sending the downlink message to the terminal device corresponding to the session identifier.