Multi-Gateway IoT Network Segmentation and Backup Switching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing multi-gateway networking systems face challenges in efficiently linking a large number of IoT devices across different protocols, and they become unstable when the master gateway fails, leading to disruptions in automation linkages.
Innovation Solution
A multi-gateway networking method and system that includes a first class gateway and multiple second class gateways, where the first class gateway schedules and communicates with second class gateways to manage control instructions between sub-devices, and a third class gateway acts as a backup to seamlessly switch in case of failure.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a single master gateway is used to manage IoT devices, then the device complexity is reduced, but the reliability deteriorates when the master gateway fails
Solution Approach 1:
The gateway system is segmented into multiple independent gateways (first gateway, second gateway, third gateway) with distinct roles. The first gateway manages first protocol devices, the second gateway manages second protocol devices, and the third gateway serves as backup. This segmentation allows the system to maintain functionality even when individual gateways fail, resolving the reliability issue while keeping each gateway's complexity manageable.
Solution Approach 2:
The system changes the operational state parameters of gateways dynamically. Gateways can transition between active and standby states based on system needs. The third gateway is configured to switch from standby to active state when the first or second gateway fails, maintaining system reliability without requiring all gateways to operate at full complexity simultaneously.
2Adaptability or versatility
If multiple gateways are used to support different IoT protocols, then the adaptability improves, but the device complexity increases
Solution Approach 1:
Different protocol support is segmented across multiple specialized gateways rather than consolidating all protocols in a single gateway. The first gateway handles first protocol devices, the second gateway handles second protocol devices, reducing the complexity burden on each individual gateway while maintaining overall system adaptability.
Solution Approach 2:
The gateway system achieves universality through collaboration. While individual gateways specialize in specific protocols, the combined system supports multiple protocols by routing device communications through appropriate gateways. The cloud server coordinates between gateways to provide unified multi-protocol support without requiring each gateway to handle all protocols.
3Productivity
If automation linkage is implemented across devices, then the productivity increases, but the system stability deteriorates when gateways fail
Solution Approach 1:
The system prepares backup gateway configurations in advance before failures occur. The third gateway is pre-configured as a standby unit with the capability to take over automation linkage functions. This prior cushioning ensures that automation linkages can continue without disruption when active gateways fail, maintaining both productivity and stability.
Solution Approach 2:
The cloud server acts as an intermediary that coordinates automation linkage operations across multiple gateways. When gateways fail, the cloud server mediates the switching process and redistributes automation tasks to remaining functional gateways, ensuring continuous operation without breaking the automation flow.
4Speed
If cloud server dependence is reduced for faster response, then the speed improves, but the system complexity increases
Solution Approach 1:
Control functions are segmented and distributed to individual gateways that operate autonomously within their domains. Each gateway can independently manage its connected devices and execute automation linkages without requiring constant cloud server intervention, reducing response time while maintaining manageable complexity through clear functional boundaries.
Solution Approach 2:
Gateways are designed with self-service capabilities to handle local automation decisions independently. When automation linkages are triggered, gateways can autonomously execute control logic and coordinate with other gateways directly, reducing cloud server dependence for routine operations while maintaining system coherence through decentralized intelligence.
Data Source
AI summary
A multi-gateway networking system includes: a first class gateway; and at least one second class gateway connected to the first class gateway, wherein the first class gateway is configured to: schedule the second class gateway and receive, through the second class gateway, first information sent by a first sub-device; and generate a control instruction in response to determining that the first information satisfies a linkage rule, and send the control instruction to a second sub-device through the second class gateway, wherein the second sub-device and the first sub-device are connected to different second class gateways respectively.