# US 2023/0156078 A1 · System and Method for Active-Active Standby in Phone System Management

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2023/0156078 A1
- Document ID: US20230156078A1
- Status: Published application
- Kind: A1
- Application number: 18/150,300
- Filed: 2023-01-05
- Published: 2023-05-18
- Earliest claimed: 2021-04-29
- Assignees: Zoom Video Communications, Inc.
- Applicants: Zoom Video Communications, Inc.
- Inventors: Yong Yang; Hongjian Zhao; Lei Zheng
- Web page: https://patentgrep.com/patent/US20230156078A1

## CPC

- H04L 67/1004: Server selection for load balancing
- H04L 67/1034: Reaction to server failures by a load balancer
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/568: Storing data temporarily at an intermediate stage, e.g. caching
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Active-active standby is maintained for communication sessions using web connections between two active session zones and a standby session zone, for example, in the event of a failure. A first load balancer directs system management communications of a first datacenter to a first server of the first datacenter. A second load balancer directs the system management communications during a failure event to a second server. A database controller performs a failover based on the failure event.

## Claims

### Claim 1

A system comprising:
a first load balancer associated with a first datacenter, wherein the first load balancer is configured to direct system management communications associated with the first datacenter to a first server associated with the first datacenter;
a second load balancer associated with a second datacenter, wherein the second load balancer is a standby load balancer configured to direct the system management communications during a failure event to a second server associated with the second datacenter, wherein the system management communications are associated with the first datacenter; and
a database controller configured to perform a failover based on the failure event.

### Claim 2 (depends on 1)

The system of claim 1, wherein the database controller is configured to perform the failover from the first datacenter to the second datacenter when the failure event is at the first datacenter.

### Claim 3 (depends on 1)

The system of claim 1, wherein the database controller is configured to perform the failover from the second datacenter to a third datacenter when the failure event is at the second datacenter.

### Claim 4 (depends on 1)

The system of claim 1, further comprising:
a first database comprising first data associated with the first datacenter; and
a second database comprising second data associated with the second datacenter.

### Claim 5 (depends on 1)

The system of claim 1, further comprising:
a first database comprising first data associated with the first datacenter; and
a second database comprising second data associated with the second datacenter, wherein the database controller is configured to synchronize the first data and the second data between the first database and the second database.

### Claim 6 (depends on 1)

The system of claim 1, further comprising:
a first database comprising first data associated with the first datacenter; and
a second database comprising second data associated with the second datacenter, wherein the first database and the second database form a cluster to perform a search across the first database and the second database using a single search request.

### Claim 7 (depends on 1)

The system of claim 1, further comprising:
a first database comprising first data associated with the first datacenter; and
a second database comprising second data associated with the second datacenter, wherein the first database and the second database form an elastic search cluster to perform a search across the first database and the second database using a single search request.

### Claim 8 (depends on 1)

The system of claim 1, further comprising:
a first database comprising first data associated with the first datacenter; and
a second database comprising second data associated with the second datacenter, wherein the first database and the second database form a cluster to perform a search across the first database and the second database using a single search request, wherein data associated with the cluster is synchronized with a third database.

### Claim 9 (depends on 1)

The system of claim 1, further comprising:
a first database comprising first data associated with the first datacenter; and
a second database comprising second data associated with the second datacenter, wherein the first database and the second database form a cluster to perform a search across the first database and the second database using a single search request, wherein data associated with the cluster is synchronized with a third database in near-real time.

### Claim 10 (depends on 1)

The system of claim 1, further comprising:
a first cache associated with the first datacenter;
a second cache associated with the second datacenter; and
a cache controller configured to synchronize the first cache and the second cache.

### Claim 11

A method comprising:
directing, by a first load balancer associated with a first datacenter, system management communications associated with the first datacenter to a first server associated with the first datacenter;
directing, by a second load balancer that is a standby load balancer associated with a second datacenter, the system management communications during a failure event to a second server associated with the second datacenter, wherein the system management communications are associated with the first datacenter; and
performing, by a database controller, a failover based on the failure event.

### Claim 12 (depends on 11)

The method of claim 11, further comprising:
performing the failover from the first datacenter to the second datacenter.

### Claim 13 (depends on 11)

The method of claim 11, further comprising:
performing the failover from the second datacenter to a third datacenter.

### Claim 14 (depends on 11)

The method of claim 11, wherein a first database associated with the first datacenter and a second database associated with the second datacenter form a cluster, the method further comprising:
performing a search across the first database and the second database using a single search request.

### Claim 15 (depends on 11)

The method of claim 11, wherein a first database associated with the first datacenter and a second database associated with the second datacenter form an elastic search cluster, the method further comprising:
performing a search across the first database and the second database using a single search request.

### Claim 16 (depends on 11)

The method of claim 11, wherein a first database associated with the first datacenter and a second database associated with the second datacenter form a cluster, the method further comprising:
performing a search across the first database and the second database using a single search request, wherein data associated with the cluster is synchronized with a third database.

### Claim 17

A non-transitory computer-readable medium comprising instructions that when executed by a processor, cause the processor to:
direct system management communications associated with a first datacenter to a first server associated with the first datacenter;
direct the system management communications during a failure event to a second server associated with a second datacenter, wherein the system management communications are associated with the first datacenter; and
perform a failover based on the failure event.

### Claim 18 (depends on 17)

The non-transitory computer-readable medium of claim 17, wherein the failover of the system management communications associated with the first datacenter is to the second datacenter, wherein the processor is configured to:
detect a failure event at the second datacenter, wherein the second datacenter includes a an active session zone that includes system management communications associated with the second datacenter; and
perform, based on the detected failure event at the second datacenter, a second failover of the system management communications associated with the first datacenter and the system management communications associated with the second datacenter to a third datacenter.

### Claim 19 (depends on 17)

The non-transitory computer-readable medium of claim 17, wherein the failover of the system management communications associated with the first datacenter is to a standby web pod, the processor configured to:
detect a second failure event at the standby web pod; and
perform a second failover of the system management communications associated with the first datacenter,
wherein the second failover is to a second standby web pod when the second standby web pod is available, and
wherein the second failover is to the second datacenter when a standby call switch is not available.

### Claim 20 (depends on 17)

The non-transitory computer-readable medium of claim 17, wherein a first database associated with the first datacenter and a second database associated with the second datacenter form an elastic search cluster, the processor configured to:
perform a search across the first database and the second database using a single search request.
