Active Session Zone Load Balancing for Seamless SIP Failover

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing communication systems, particularly in UCaaS platforms, face challenges with scalability and stability during session failovers, leading to issues like system instability, data loss, and dropped calls due to shared resource management and inadequate active-active standby mechanisms.

Innovation Solution

Implementing active-active standby communication sessions using SIP processes between two active session zones in a first datacenter and a standby session zone in a second datacenter, with synchronized caches and redundant SBCs, load balancers, and call switches to ensure seamless failover in case of failures.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If active-active standby mechanisms are implemented with redundant SBCs, load balancers, and call switches, then system reliability is improved, but device complexity increases

Engineering Contradiction:
Improvesystem reliabilityVSAvoiddevice complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system is divided into multiple independent functional components (SBCs, load balancers, call switches) that can operate independently. Each component is segmented into active and standby instances, allowing failover without affecting the entire system. This segmentation enables redundancy while managing complexity through modular design.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system dynamically changes operational parameters during failover events. When a primary component fails, the system changes the state parameter of standby components from inactive to active, and changes routing parameters to redirect traffic. This parameter-based control manages complexity by using state transitions rather than permanent structural changes.

Inventive Principle:
Principle #35Parameter changes

2Loss of information

If synchronized caches are implemented across active session zones, then loss of information is reduced, but device complexity increases

Engineering Contradiction:
Improvedata lossVSAvoiddevice complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

Multiple cache instances across different active session zones are merged into a synchronized cache system. The caches maintain consistent data through synchronization mechanisms, ensuring that information is preserved during failover. This merging approach reduces data loss by ensuring data availability across zones while managing complexity through unified cache management.

Inventive Principle:
Principle #5Merging (Combining)

3Speed

If active session zones are maintained in the same datacenter, then speed of failover is improved, but object-generated harmful factors increase due to single point of failure

Engineering Contradiction:
Improvefailover speedVSAvoidsingle point of failure
Core Design Contradiction:
SpeedVSObject-generated harmful factors

Solution Approach 1:

The system distributes active session zones across different dimensional aspects - geographically separated datacenters with multiple zones within each. This multi-dimensional distribution allows fast failover within the same datacenter while providing cross-datacenter redundancy to eliminate single points of failure. The solution operates at multiple spatial dimensions simultaneously.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS12445521B2Load balancing using multiple active session zones
Publication Date: 2025.10.14 ZOOM COMMUNICATIONS INC
  • US12445521B2 patent drawing
  • US12445521B2 patent drawing
  • US12445521B2 patent drawing

AI summary

Load balancing is maintained for communication sessions using session initiation protocol (SIP) processes between multiple active session zones in a first datacenter and a standby session zone in a second datacenter. In the event of a failure at a first active session zone at the first datacenter, a failover to the second active session zone at the first datacenter is performed such that there are no interruptions in the active sessions. In the event of a failure at both active session zones at the first datacenter, a failover to the second datacenter is performed.