Balance of load

Patent metadata

Field	Value
Publication number	US-12375552-B2
Application number	US-202217721131-A
Country	US
Kind code	B2
Filing date	Apr 14, 2022
Priority date	May 24, 2021
Publication date	Jul 29, 2025
Grant date	Jul 29, 2025

Abstract

A system is provided that includes: a first load balancing device cluster, the first load balancing device cluster includes a first load balancing device pool and a second load balancing device pool; at least one first switch respectively coupled with each load balancing device in the first load balancing device pool via a routing protocol link; and at least one second switch respectively coupled with each load balancing device in the second load balancing device pool via a routing protocol link, the at least one first switch and the at least one second switch are configured to be able to be connected with the Internet; and one of the first load balancing device pool and the second load balancing device pool is configured as a standby load balancing device pool of the other.

First claim

The invention claimed is:

1. A system, comprising:
a first load balancing device cluster, wherein the first load balancing device cluster comprises a first load balancing device pool and a second load balancing device pool, the first load balancing device pool including at least two load balancing devices and the second load balancing device pool including at least two load balancing devices which are different than the at least two load balancing devices in the first load balancing device pool;
at least one first switch, wherein the at least one first switch is respectively coupled with each load balancing device in the first load balancing device pool via a first routing protocol link; and
at least one second switch, wherein the at least one second switch is respectively coupled with each load balancing device in the second load balancing device pool via a second routing protocol link, wherein:
the at least one first switch and the at least one second switch are configured to be able to be connected with the Internet through a router;
one of the first load balancing device pool and the second load balancing device pool is configured as a standby load balancing device pool of the other one;
the first load balancing device pool and the second load balancing device pool are connected with a same back-end server;
each load balancing device in the first load balancing device pool is configured to upwardly publish first routing information:
each load balancing device in the second load balancing device pool is configured to upwardly publish second routing information different from the first routing information:
the first routing information comprises first Virtual IP (VIP) address information corresponding to the first load balancing device pool as a main load balancing device pool and second Virtual IP (VIP) address information corresponding to the first load balancing device pool as the standby load balancing device pool of the second load balancing device pool;
the second routing information comprises third Virtual IP (VIP) address information corresponding to the second load balancing device pool as a main load balancing device pool and fourth Virtual IP (VIP) address information corresponding to the second load balancing device pool as the standby load balancing device pool of the first load balancing device pool;
the first VIP information corresponds to the fourth Virtual IP (VIP) address information, and the second VIP information corresponds to the third VIP information;
a Prefix value comprised in the first VIP information is 25;
a Prefix value comprised in the fourth VIP information is 24; and
the first VIP information and the fourth VIP information comprise a same first VIP address.

2. The system according to claim 1 , wherein each load balancing device in the first load balancing device pool is respectively communicatively coupled with each of one or more back-end servers; and
each load balancing device in the second load balancing device pool is respectively communicatively coupled with each of the one or more back-end servers.

3. The system according to claim 1 , wherein the first load balancing device pool and the second load balancing device pool are from a same available zone.

4. The system according to claim 1 , wherein the first load balancing device pool and the second load balancing device pool are from different available zones.

5. The system according to claim 1 , wherein a Prefix value comprised in the second VIP information is 24;
a Prefix value comprised in the third VIP information is 25;
the second VIP information and the third VIP information comprise a same second VIP address; and
the second VIP address is different from the first VIP address.

6. The system according to claim 1 , further comprising:
at least one second load balancing device cluster, wherein the at least one second load balancing device cluster comprises a third load balancing device pool and a fourth load balancing device pool;
at least one third switch, wherein the at least one third switch is respectively coupled with each load balancing device in the third load balancing device pool via a third routing protocol link;
at least one fourth switch, wherein the at least one fourth switch is respectively coupled with each load balancing device in the fourth load balancing device pool via a fourth routing protocol link;
the at least one third switch and the at least one fourth switch are configured to be able to be connected with the Internet; and
one of the third load balancing device pool and the fourth load balancing device pool is configured as a standby load balancing device pool of the other one.

7. The system according to claim 1 , wherein the routing protocol link use a Border Gateway Protocol (BGP) or an Open Shortest Path First (OSPF) protocol.

Assignees

• Beijing Baidu Netcom Sci & Tech Co Ltd

Inventors

• Zhang Fenghui
• Wang Feitong
• Jiang Lin
• Liang Aiyi

Classifications

• H04L67/1014

  based on the content of a request · CPC title

• H04L67/1006

  with static server selection, e.g. the same server being selected for a specific client · CPC title

• H04L45/42

  Centralised routing · CPC title

• H04L45/12

  Shortest path evaluation · CPC title

• H04L61/5007

  Internet protocol [IP] addresses · CPC title