Method for load balancing of requests' processing of diameter servers

• US 8,879,431 B2
• Filed: 05/16/2012
• Issued: 11/04/2014
• Est. Priority Date: 05/16/2011
• Status: Active Grant

• Current Assignee: F5 Networks, Inc. (F5 Incorporated)
• Original Assignee: F5 Networks, Inc. (F5 Incorporated)
• Inventors: Tumarkin, Valentin, Ridel, Leonid
• Primary Examiner(s): Yao, Kwang B
• Assistant Examiner(s): DUDA, ADAM K
• Application Number:
  US13/473,589
• Publication Number:
  US 20130064093A1
• Time in Patent Office: 902 Days
• Field of Search: 370/259, 370/271, 370/270, 370/260
• US Class Current: 370/259
• CPC Class Codes: H04L 47/125 by balancing the load, e.g. traffic engineering
• CPC Class Codes: H04L 47/215 using token-bucket
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 47/741 Holding a request until resources become available
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1012 based on compliance of requirements or conditions with available server resources
• CPC Class Codes: H04L 67/1025 Dynamic adaptation of the criteria on which the server selection is based
• CPC Class Codes: H04L 67/60 Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources admission control or resource allocation H04L47/70

Abstract

A system, computer readable medium and method of load balancing of requests between Diameter-enabled network devices is disclosed. Processing occurs at a signal controller in communication with a first Diameter-enabled network device and a second Diameter-enabled network device, request handling capacity of at least the second Diameter-enabled network device. One or more tokens are allocated for inbound requests from the first Diameter-enabled network device to the second Diameter-enabled network device. The second Diameter-enabled network device is notified of the one or more allocated tokens for handling a corresponding number of requests from the first Diameter-enabled network device. Transmission of the corresponding number of requests from the first Diameter-enabled network device to the second Diameter-enabled network device is coordinated by the signal controller.

Claims

1. A method of load balancing of requests between Diameter-enabled network devices, the method comprising:

processing, at a signal controller in communication with a first Diameter-enabled network device and a second Diameter-enabled network device, request handling capacity of at least the second Diameter-enabled network device;

allocating, at the signal controller, one or more tokens for inbound requests from the first Diameter-enabled network device to the second Diameter-enabled network device;

notifying the second Diameter-enabled network device of the one or more allocated tokens for handling a corresponding number of requests from the first Diameter-enabled network device;

coordinating, at the signal controller, transmission of the corresponding number of requests from the first Diameter-enabled network device to the second Diameter-enabled network device via the signal controller;

detecting, at the second Diameter-enabled network device, an overload condition in the second Diameter-enabled network device; and

notifying the signal controller to allocate zero tokens to the second Diameter-enabled network device, wherein the signal controller does not send any further requests to the second Diameter-enabled network device.

2. A non-transitory computer readable medium having stored thereon instructions for load balancing of requests between Diameter-enabled network devices, comprising machine executable code which when executed by at least one processor in a signal controller in communication with a first Diameter-enabled network device and a second Diameter-enabled network device, causes the processor to:

determine request handling capacity of at least the second Diameter-enabled network device;

allocate one or more tokens for inbound requests from the first Diameter-enabled network device to the second Diameter-enabled network device;

notify the second Diameter-enabled network device of the one or more allocated tokens for handling a corresponding number of requests from the first Diameter-enabled network device;

coordinate transmission of the corresponding number of requests from the first Diameter-enabled network device to the second Diameter-enabled network device;

receive a notification from the second Diameter-enabled network device that has detected an overload condition, the notification indicating to allocate zero tokens to the first Diameter-enabled network device; and

not sending any further requests from the first Diameter-enabled network device to the second Diameter-enabled network device.

3. A signal controller in communication with a first Diameter-enabled network device and a second Diameter-enabled network device, the signal controller comprising:

a network interface configured to be capable of receiving and transmitting network data packets over one or more networks;

a memory configured to store executable programming instructions; and

a processor configured executing the stored programming instructions, which when executed result in actions being performed that include;

processing request handling capacity of at least the second Diameter-enabled network device;

allocating one or more tokens for inbound requests from the first Diameter-enabled network device to the second Diameter-enabled network device;

notifying the second Diameter-enabled network device of the one or more allocated tokens for handling a corresponding number of requests from the first Diameter-enabled network device; and

coordinating transmission of the corresponding number of requests from the first Diameter-enabled network device to the second Diameter-enabled network device, wherein the signal controller receives a notification from the second Diameter-enabled network device that has detected an overload condition, the notification indicating to allocate zero tokens to the first Diameter-enabled network device; and

does not send any further requests from the first Diameter-enabled network device to the second Diameter-enabled network device.

4. A system comprising:

a first Diameter-enabled network device connected to a network;

a second Diameter-enabled network device connected to the network;

a signal controller in communication with the first Diameter-enabled network device and the second Diameter-enabled network device via the network, the signal controller comprising;

a network interface configured to be capable of receiving and transmitting network data packets over one or more networks;

a memory configured to store executable programming instructions; and

a processor configured to execute the stored programming instructions, which causes the processor to;

process request handling capacity of at least the second Diameter-enabled network device;

allocate one or more tokens for inbound requests from the first Diameter-enabled network device to the second Diameter-enabled network device;

notify the second Diameter-enabled network device of the one or more allocated tokens for handling a corresponding number of requests from the first Diameter-enabled network device; and

coordinate transmission of the corresponding number of requests from the first Diameter-enabled network device to the second Diameter-enabled network device via the signal controller, wherein the signal controller receives a notification from the second Diameter-enabled network device that has detected an overload condition, the notification indicating to allocate zero tokens to the first Diameter-enabled network device; and

does not send any further requests from the first Diameter-enabled network device to the second Diameter-enabled network device.

5. A method of load balancing of requests between Diameter-enabled network devices, the method comprising:

processing, by a signal controller device in communication between at least a first Diameter-enabled network device and a second Diameter-enabled network device, a request for a handling capacity of at least the second Diameter-enabled network device, wherein the processing comprises detecting when there is an overload condition in the second Diameter-enabled network device;

allocating, by the signal controller device, one or more tokens for inbound requests from the first Diameter-enabled network device to the second Diameter-enabled network device;

notifying, by the signal controller device, the second Diameter-enabled network device when at least one of the one or more tokens are allocated for handling a corresponding number of requests from the first Diameter-enabled network device; and

coordinating, by the signal controller device, transmission of the corresponding number of requests from the first Diameter-enabled network device to the second Diameter-enabled network device, wherein no further requests are sent to the second Diameter-enabled network device when an overload condition is detected.

6. The method according to claim 5, wherein the signal controller device is configured to prioritize token allocation between the first and second Diameter-enabled network device.

7. The method according to claim 5, wherein the request handling capacity further comprises current and projected capacity of the second Diameter-enabled network device.

8. The method according to claim 5, further comprising the signal controller device allocating the one or more tokens at a refill rate based on current and projected capacity of the second Diameter-enabled network device.

9. The method according to claim 5, wherein the allocated tokens are available for a predetermined period of time.

10. A non-transitory computer readable medium having stored thereon instructions for load balancing of requests between Diameter-enabled network devices, comprising machine executable code which when executed by at least one processor, causes the processor to perform steps comprising:

processing communication between at least a first Diameter-enabled network device and a second Diameter-enabled network device;

determining a request handling capacity of at least the second Diameter-enabled network device, wherein the determining comprises detecting when there is an overload condition in the second Diameter-enabled network device;

allocating one or more tokens for inbound requests from the first Diameter-enabled network device to the second Diameter-enabled network device, when no overload condition is detected in the second Diameter-enabled network device;

notifying the second Diameter-enabled network device when at least one of the one or more tokens are allocated for handling a corresponding number of requests from the first Diameter-enabled network device; and

coordinating transmission of the corresponding number of requests from the first Diameter-enabled network device to the second Diameter-enabled network device, wherein no further requests are sent to the second Diameter-enabled network device when an overload condition is detected.

11. The computer readable medium according to claim 10, wherein the processor is configured to prioritize token allocation between the first and second Diameter-enabled network device.

12. The computer readable medium according to claim 10, wherein the request handling capacity further comprises current and projected capacity of the second Diameter-enabled network device.

13. The computer readable medium according to claim 10, wherein the processor is further configured to allocate the one or more tokens at a refill rate based on current and projected capacity of the second Diameter-enabled network device.

14. The computer readable medium according to claim 10, wherein the allocated tokens are available for a predetermined period of time.

15. A signal controller device comprising:

a memory storing programmed instructions; and

a processor coupled to the memory and configured to execute the stored programmed instructions to perform steps comprising;

processing communication between at least a first Diameter-enabled network device and a second Diameter-enabled network device;

determining a request handling capacity of at least the second Diameter-enabled network device, wherein the determining comprises detecting when there is an overload condition in the second Diameter-enabled network device;

allocating one or more tokens for inbound requests from the first Diameter-enabled network device to the second Diameter-enabled network device, when no overload condition is detected in the second Diameter-enabled network device;

notifying the second Diameter-enabled network device when at least one of the one or more tokens are allocated for handling a corresponding number of requests from the first Diameter-enabled network device; and

coordinating transmission of the corresponding number of requests from the first Diameter-enabled network device to the second Diameter-enabled network device, wherein no further requests are sent to the second Diameter-enabled network device when an overload condition is detected.

16. The signal controller device according to claim 15, wherein the signal controller device is configured to prioritize token allocation between the first and second Diameter-enabled network device.

17. The signal controller device according to claim 15, wherein the request handling capacity further comprises current and projected capacity of the second Diameter-enabled network device.

18. The signal controller device according to claim 15, wherein the signal controller device allocates the one or more tokens at a refill rate based on current and projected capacity of the second Diameter-enabled network device.

19. The signal controller device according to claim 15, wherein the allocated tokens are available for a predetermined period of time.

20. A system comprising:

a first Diameter-enabled network device connected to a network;

a second Diameter-enabled network device connected to the network;

a signal controller device comprising;

a memory storing programmed instructions; and

a processor coupled to the memory and configured to execute the stored programmed instructions, which cause the processor to;

process communication between at least a first Diameter-enabled network device and a second Diameter-enabled network device;

determine a request handling capacity of at least the second Diameter-enabled network device, wherein the determining comprises detecting when there is an overload condition in the second Diameter-enabled network device;

allocate one or more tokens for inbound requests from the first Diameter-enabled network device to the second Diameter-enabled network device, when no overload condition is detected in the second Diameter-enabled network device;

notify the second Diameter-enabled network device when at least one of the one or more tokens are allocated for handling a corresponding number of requests from the first Diameter-enabled network device; and

coordinate transmission of the corresponding number of requests from the first Diameter-enabled network device to the second Diameter-enabled network device via the signal controller device, wherein no further requests are sent to the second Diameter-enabled network device when an overload condition is detected.

21. The system according to claim 20, wherein the signal controller device is configured to prioritize token allocation between the first and second Diameter-enabled network device.

22. The system according to claim 20, wherein the request handling capacity further comprises current and projected capacity of the second Diameter-enabled network device.

23. The system according to claim 20, wherein the signal controller device allocates the one or more tokens at a refill rate based on current and projected capacity of the second Diameter-enabled network device.

24. The system according to claim 20, wherein the allocated tokens are available for a predetermined period of time.