Processing

Please wait...

Settings

Settings

Goto Application

1. WO2020222683 - LOAD BALANCING SYSTEMS AND METHODS

Note: Text based on automatic Optical Character Recognition processes. Please use the PDF version for legal matters

[ EN ]

CLAIMS:

1. A method (1200) performed by a load balancing system (102), the method comprising: receiving (si 202) a request (504) sent by a client (152);

selecting (si 204) from a first cluster of serving entities a first main serving entity (154) and a first backup serving entity (156); and

as a result of receiving the request (504) sent by the client (152), sending (sl206) to the client information (506) identifying the selected first main serving entity (154) and the selected first backup serving entity (156).

2. The method of claim 1 , further comprising:

after sending to the client the information identifying the selected first main serving entity and the selected first backup serving entity, receiving a request sent by the first main serving entity;

selecting from a second cluster of serving entities a second main serving entity and a second backup serving entity; and

as a result of receiving the request sent by the first main serving entity, sending to the first main serving entity information identifying the selected second main serving entity and the selected second backup serving entity.

3. The method of any one of claims 1-2, further comprising:

obtaining unavailability information indicating that the first main serving entity or the first backup serving entity is unavailable; and

as a result of obtaining the unavailability information, sending to one or more entities information indicating that the first main serving entity or the first backup serving entity is unavailable.

4. The method of claim 3, further comprising:

as a result of obtaining the unavailability information, selecting an additional backup serving entity from the first cluster of serving entities; and

sending to said one or more entities information identifying the selected additional backup serving entity.

5. The method of any one of claims 1-4, wherein the load balancing system is either centralized or distributed.

6. The method of any one of claims 1-5, further comprising:

obtaining from a service registry information regarding all entities in the first cluster of serving entities, wherein the first cluster of serving entities is associated with one or more particular types of service.

7. A method (1300) performed by a client (152), the method comprising:

sending (si 302) a request (504) to a load balancing system (102);

as a result of sending the request (504) to the load balancing system, receiving (si 304) information (506) identifying a first main serving entity (154) that is a part of a first cluster of serving entities and a first backup serving entity (156) that is a part of the first cluster of serving entities, wherein the information was sent by the load balancing system; and

after receiving the information (506) identifying the first main serving entity and the first backup serving entity, sending (si 306) to the first main serving entity (154) information (510) identifying the first backup serving entity.

8. The method of claim 7, further comprising:

determining whether a connection to the first main serving entity and/or a connection to the first backup serving entity exists;

as a result of determining that the connection to the first main serving entity does not exist, setting up the connection to the first main serving entity; and

as a result of determining that the connection to the first backup serving entity does not exist, setting up the connection to the first backup serving entity.

9. A method (1400) performed by a first main serving entity (154) within a first cluster of serving entities, the method comprising:

receiving (si 402) first identifying information (510) identifying a first backup serving entity (156) within the first cluster of serving entities, wherein the first identifying information was sent by a client (152);

after receiving the first identifying information, sending (si 404) a request (512) to a load balancing system (102);

as a result of sending the request (512) to the load balancing system (102), receiving (sl406) second identifying information (514) identifying a second main serving entity (158) within a second cluster of serving entities and a second backup serving entity (160) within the second cluster of serving entities, wherein the second identifying information was sent by the load balancing system; and

after receiving the second identifying information (514), sending (si 408) to the second main serving entity (158) third identifying information (518) identifying the first main serving entity (154), the first backup serving entity (156), and the second backup serving entity (160).

10. The method of claim 9, further comprising:

sending to the first backup serving entity information identifying the client, the second main serving entity, and the second backup serving entity.

11. The method of any one of claims 9-10, further comprising:

receiving a service request sent by the client;

setting up session data; and

sending the session data to the first backup serving entity.

12. The method of any one of claims 9-11 , further comprising:

receiving unavailability information indicating that the second main serving entity is unavailable, wherein the unavailability information was sent from the load balancing system; and as a result of receiving the unavailability information, sending a session request to the second backup serving entity.

13. The method of any one of claims 9-11 , further comprising:

receiving unavailability information indicating that the second backup serving entity is unavailable, wherein the unavailability information was sent by the load balancing system and the unavailability information further includes information identifying an additional backup serving entity; and

replacing the second backup serving entity with the additional backup serving entity, wherein the additional backup serving entity is selected from the second cluster of serving entities.

14. The method of any one of claims 9-13, wherein when the first main serving entity and/or the first backup serving entity starts up or shuts down, information corresponding to the first main serving entity and/or the first backup serving entity stored in a service registry is updated.

15. A method (1500) performed by a second main serving entity (158), the method comprising:

receiving (si 502) first identifying information (518) identifying the first main serving entity (154), a first backup serving entity (156), and a second backup serving entity (160), wherein the first identifying information (518) was sent by a first main serving entity (154); after receiving the first identifying information (518), sending (si 504) a request (524) to a load balancing system (102);

as a result of sending the request (524) to the load balancing system (102), receiving (si 506) second identifying information (526) identifying a third main entity (162) and a third backup entity (164), wherein the second identifying information was sent by the load balancing system; and

after receiving the second identifying information (526), sending (si 508) to the third main serving entity (162) third identifying information (530) identifying the second main serving entity (158), the second backup serving entity (160), and the third backup serving entity (164), wherein

each of the first main serving entity and the first backup serving entity is selected from a first cluster of serving entities,

each of the second main serving entity and the second backup serving entity is selected from a second cluster of serving entities, and

each of the third main serving entity and the third backup serving entity is selected from a third cluster of serving entities.

16. The method of claim 15, further comprising:

sending to the second backup serving entity information identifying the first main serving entity, the first backup serving entity, the third main serving entity, and the third backup serving entity.

17. The method of claim 16, further comprising:

receiving a session request sent by the first main serving entity;

setting up session data; and

sending the session data to the second backup serving entity.

18. The method of any one of claims 15-17, further comprising:

receiving unavailability information indicating that the first main serving entity or the third main serving entity is unavailable, wherein the unavailability information was sent by the load balancing system;

if the unavailability information indicates that the first main serving entity is unavailable, as a result of receiving the unavailability information, sending a session response to the first backup serving entity; and

if the unavailability information indicates that the third main serving entity is unavailable, as a result of receiving the unavailability information, sending a session request to the third backup serving entity.

19. The method of any one of claims 15-17, further comprising:

receiving unavailability information indicating that the first backup serving entity, the second backup serving entity, or the third backup serving entity is unavailable, wherein the unavailability information was sent by the load balancing system and the unavailability information further includes information identifying an additional backup serving entity;

if the unavailability information indicates that the first backup serving entity is unavailable, replacing the first backup serving entity with the additional backup serving entity, wherein the additional backup serving entity is selected from the first cluster of serving entities; if the unavailability information indicates that the second backup serving entity is unavailable, replacing the second backup serving entity with the additional backup serving entity, wherein the additional backup serving entity is selected from the second cluster of serving entities; and

if the unavailability information indicates that the third backup serving entity is unavailable, replacing the third backup serving entity with the additional backup serving entity, wherein the additional backup serving entity is selected from the third cluster of serving entities.

20. The method of claim 19, further comprising:

if the unavailability information indicates that the second backup serving entity is unavailable, sending to the additional backup serving entity information identifying the first main serving entity, the first backup serving entity, the third main serving entity, and the third backup serving entity.

21. The method of any one of claims 15-17, wherein after the second main serving entity becomes unavailable,

the second backup serving entity is configured to receive unavailability information (a) indicating that the second backup serving entity is unavailable and (b) including information identifying an additional backup serving entity,

the first main serving entity, the first backup serving entity, the third main serving entity, and the third backup serving entity are configured to be updated such that the second backup serving entity becomes a new main serving entity in the second cluster of serving entities, and the second backup serving entity is configured to send to the additional backup serving entity information identifying the first main serving entity, the first backup serving entity, the third main serving entity, and the third backup serving entity.

22. The method of any one of claims 1-19, wherein all entities in the first cluster are capable of performing the same function.

23. The method of any one of claims 2 and claims 9-19, wherein

all entities in the first cluster are capable of performing the first function,

all entities in the second cluster are capable of performing the second function, wherein the first function and the second function are different.

24. A load balancing system (102), the load balancing system being adapted to:

receive (sl202) a request (504) sent by a client (152);

select (si 204) from a first cluster of serving entities a first main serving entity (154) and a first backup serving entity (156); and

as a result of receiving the request (504) sent by the client (152), send (sl206) to the client information (506) identifying the selected first main serving entity (154) and the selected first backup serving entity (156).

25. A client (152), the client being adapted to:

send (sl302) a request (504) to a load balancing system (102);

as a result of sending the request (504) to the load balancing system, receive (si 304) information (506) identifying a first main serving entity (154) that is a part of a first cluster of serving entities and a first backup serving entity (156) that is a part of the first cluster of serving entities, wherein the information was sent by the load balancing system; and

after receiving the information (506) identifying the first main serving entity and the first backup serving entity, send (si 306) to the first main serving entity (154) information (510) identifying the first backup serving entity.

26. A first main serving entity (154) within a first cluster of serving entities, the first main serving entity being adapted to:

receive (si 402) first identifying information (510) identifying a first backup serving entity (156) within the first cluster of serving entities, wherein the first identifying information was sent by a client (152);

after receiving the first identifying information, send (si 404) a request (512) to a load balancing system (102);

as a result of sending the request (512) to the load balancing system (102), receive (si 406) second identifying information (514) identifying a second main serving entity (158) within a second cluster of serving entities and a second backup serving entity (160) within the second cluster of serving entities, wherein the second identifying information was sent by the load balancing system; and

after receiving the second identifying information (514), send (si 408) to the second main serving entity (158) third identifying information (518) identifying the first main serving entity (154), the first backup serving entity (156), and the second backup serving entity (160).

27. A second main serving entity (158), the second main serving entity being adapted to: receive (si 502) first identifying information (518) identifying the first main serving entity (154), a first backup serving entity (156), and a second backup serving entity (160), wherein the first identifying information (518) was sent by a first main serving entity (154); after receiving the first identifying information (518), send (si 504) a request (524) to a load balancing system (102);

as a result of sending the request (524) to the load balancing system (102), receive (si 506) second identifying information (526) identifying a third main entity (162) and a third backup entity (164), wherein the second identifying information was sent by the load balancing system; and

after receiving the second identifying information (526), send (si 508) to the third main serving entity (162) third identifying information (530) identifying the second main serving entity (158), the second backup serving entity (160), and the third backup serving entity (164), wherein

each of the first main serving entity and the first backup serving entity is selected from a first cluster of serving entities,

each of the second main serving entity and the second backup serving entity is selected from a second cluster of serving entities, and

each of the third main serving entity and the third backup serving entity is selected from a third cluster of serving entities.

28. Computer program, comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any one of claims 1-23.

29. A carrier containing the computer program of claim 28, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium.