Graceful Connection Cycling for Balanced Diameter Server Connections
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In communication systems with a distributed diameter service using a micro service architecture, connection imbalances occur due to server instance failures or reboots, leading to uneven distribution of connections and potential overload of certain server instances, which degrades system performance.
Innovation Solution
Implementing periodic disconnect peer requests with a graceful connection cycling mechanism, where server instances send disconnect requests with a specific cause value and last hop-by-hop ID, allowing clients to gracefully terminate connections and reestablish them on different server instances, maintaining balanced load distribution.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If connections are maintained indefinitely on server instances, then connection stability is improved, but connection imbalance occurs when server instances fail or reboot, leading to overload on remaining instances
Solution Approach 1:
The patent implements periodic disconnection of connections from server instances at scheduled intervals. This periodic action prevents connections from being permanently bound to specific server instances, allowing the system to redistribute connections evenly across available instances after failures or reboots, thus maintaining both stability and preventing overload
Solution Approach 2:
The patent introduces dynamic connection management where connections are not statically assigned but can be redistributed based on server instance availability. The system dynamically adjusts connection distribution by periodically disconnecting and allowing load balancer reassignment, enabling adaptation to changing server conditions without manual intervention
2Productivity
If connections are periodically disconnected to prevent imbalance, then system performance is improved, but connection continuity is reduced
Solution Approach 1:
The load balancer serves as an intermediary between clients and server instances. It manages the disconnection and reassignment process, absorbing the impact of periodic disconnections on clients while enabling server instances to be replaced or rebalanced. This intermediary role allows connection management without direct client-server disruption
Solution Approach 2:
The system implements feedback mechanisms where the load balancer monitors server instance health and connection distribution. When imbalances are detected or server instances fail, the system responds by redistributing connections, creating a closed-loop control system that maintains performance while managing connection duration
Data Source
AI summary
In some implementations, a network device may establish a connection between a client and a server instance associated with a service. The network device may identify that a timer for transmitting a periodic disconnect peer request has expired. The network device may transmit the periodic disconnect peer request to the client based on an expiry of the timer, wherein the periodic disconnect peer request includes a value for graceful connection cycling, and the graceful connection cycling is to be applied to the connection based on the periodic disconnect peer request.


