Private Gateway Bridge Mode Switching for Network Continuity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The complexity and diversity of private gateways make it difficult and costly to implement new service features, and service providers face challenges in updating services without disrupting connectivity when the private gateway and server gateway disconnect, leading to service losses.
Innovation Solution
A method and system that monitor the connection between the private and server gateways, switching the private gateway from a bridge operation mode to a minimal service mode in case of disconnection, allowing basic services to continue, and synchronizing registers to ensure minimal operation, with an alternative connection established through other user equipment devices if needed.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If the private gateway is simplified to act only as a bridge, then device complexity is reduced and service updates become easier, but service availability is lost when connection to server gateway is disrupted
Solution Approach 1:
The private gateway dynamically switches between bridge mode (normal operation) and router mode (fallback operation) based on connection status to server gateway. This dynamic adaptation allows the system to maintain simplified architecture during normal operation while automatically gaining full routing capabilities when connection is lost, resolving the contradiction between simplicity and reliability.
Solution Approach 2:
The system changes operational parameters (IP addressing mode, routing table activation, NAT function) based on connection status. When connected, the gateway operates in bridge mode with centralized routing; when disconnected, it transitions to router mode with local routing tables and IP configuration, maintaining service availability while keeping the device structurally simple.
2Ease of manufacture
If service functions are virtualized and moved to server gateway, then ease of service updates is improved, but reliability deteriorates as services depend on continuous connection
Solution Approach 1:
The private gateway pre-loads essential routing information and maintains the capability to function as a router even in bridge mode. This preliminary preparation ensures that when connection to server gateway is lost, the gateway can immediately switch to local routing without service interruption, maintaining reliability while allowing virtualization benefits during normal operation.
Solution Approach 2:
The system maintains fallback routing capabilities and local IP addressing functionality as a cushion against connection loss. This redundancy ensures that even though services are virtualized on the server gateway, the private gateway can independently handle local traffic routing, preventing service disruption.
3Reliability
If the private gateway maintains full routing functionality locally, then service availability is improved during disconnection, but device complexity and cost increase
Solution Approach 1:
The private gateway dynamically activates full routing functionality only when needed (during connection loss) and deactivates it during normal operation. This dynamic behavior allows the gateway to maintain service availability during disconnection while keeping device complexity low during normal operation, as the full routing capability is already present but dormant.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Method for managing network traffic between one or more user equipment devices in a private network and a server outside the private network via a private gateway, a server gateway and a connection therebetween, wherein the server gateway acts as a router and the private gateway acts as a bridge, comprising: (i) monitoring the connection between the private gateway and the server gateway; (ii) in the event of loss of connection, switching the private gateway from a bridge operation mode to a minimal service mode, which provides minimal routing services to allow data traffic in the private network to continue; (iii) repeating the method from step (i); (iv) in case of retrieved connection, switching the private gateway from the minimal service mode back to the bridge operation mode; and (v) repeating the method from step (i).