Gateway Redundancy Protocol for Network Availability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current gateway redundancy schemes are inefficient and costly, with high resource wastage and potential service disruptions due to the need for multiple idle backup gateways, and they lack effective mechanisms for handling multiple failures and geographic distribution.
Innovation Solution
A peer-based N:M gateway redundancy protocol that assigns unique priority levels to gateway nodes, allowing them to dynamically switch roles between primary and backup, with geographic distribution and load balancing to ensure efficient and reliable service across multiple sites.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multiple idle backup gateways are deployed to ensure gateway availability, then reliability is improved, but resource wastage and cost increase
Solution Approach 1:
The patent implements an N:M gateway redundancy model where M backup gateways can serve multiple primary gateways simultaneously. A single backup gateway can assume the role of any failed primary gateway, making the backup resource universal and multi-functional. This eliminates the need for dedicated 1:1 backup pairs, reducing the total number of gateways required while maintaining reliability coverage across multiple primary gateways.
Solution Approach 2:
The patent combines multiple backup functions into a single shared backup gateway pool. Instead of having separate backup gateways for each primary gateway, the system merges backup capabilities into a common pool where any backup gateway can take over any primary gateway's function. This consolidation reduces resource duplication and optimizes the use of gateway resources across the network.
2Reliability
If gateway redundancy is implemented to cover outages and maintenance, then reliability is improved, but device complexity increases
Solution Approach 1:
The patent introduces priority levels as a parameter to manage gateway redundancy. Each gateway is assigned a priority value that determines its preference for becoming primary or backup. This parameter-based approach simplifies the complexity of managing N:M relationships by providing a clear, automated mechanism for role assignment and failover decisions, eliminating the need for complex manual configuration and management of redundancy relationships.
Solution Approach 2:
The patent implements automated gateway role assignment and failover based on priority levels and operational status. Gateways automatically determine their own roles (primary or backup) and can autonomously take over failed gateways' functions without manual intervention. This self-service mechanism reduces the operational complexity of managing gateway redundancy, as the system automatically handles failover, role assignment, and resource allocation based on predefined priority parameters.
3Productivity
If frequent transitions between operational and backup gateways occur, then load balancing may be improved, but service stability deteriorates
Solution Approach 1:
The patent applies preliminary anti-action by implementing preemptive failure detection through heartbeat monitoring. Before a gateway actually fails, the system detects the failure condition through missing heartbeats and initiates failover procedures in advance. This prevents service disruptions and avoids the need for reactive transitions that could cause instability. The system also uses priority levels to pre-determine failover targets, ensuring stable and predictable transitions rather than chaotic load redistribution.
Data Source
AI summary
Each of a first group of gateway nodes of a communications network operates as a primary gateway identified by a respective unique gateway identification number (GWID), and each of a second group of gateway nodes operates as a backup gateway. Each gateway node has an assigned backup priority level with respect to each GWID. The gateway nodes are interconnected via a common local network. In the event that a primary gateway node becomes non-operational, the backup gateway that is assigned the highest priority level with respect to the GWID of the non-operational primary gateway assumes operation as the primary gateway identified by that GWID. Upon restoration of the non-operational gateway node, the gateway node operates as a backup gateway in place of the gateway node that assumed its operation as the primary gateway. A gateway node operates as a primary gateway for only one respective GWID at a time.