METHODS, SYSTEMS, AND COMPUTER READABLE MEDIA FOR SOURCE PEER CAPACITY-BASED DIAMETER LOAD SHARING

• US 20110202604A1
• Filed: 02/11/2011
• Published: 08/18/2011
• Est. Priority Date: 02/12/2010
• Status: Active Grant

• Current Assignee: Tekelec
• Original Assignee: Tekelec
• Inventors: Kanode, Mark Edward, Craig, Jeffrey Alan, Wallace, Donald E., Marsico, Peter Joseph, Sprague, David Michael
• Granted Patent: US 8,601,073 B2
• Time in Patent Office: Days
• US Class Current: 709/205
• CPC Class Codes: H04L 43/0805 by checking availability
• CPC Class Codes: H04L 45/028 Dynamic adaptation of the update intervals, e.g. event-triggered updates
• CPC Class Codes: H04L 45/28 using route fault recovery
• CPC Class Codes: H04L 45/304 Route determination for signalling traffic
• CPC Class Codes: H04L 45/34 Source routing
• CPC Class Codes: H04L 45/60 Router architectures
• CPC Class Codes: H04L 63/0892 by using authentication-authorization-accounting [AAA] servers or protocols
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion

Abstract

Methods, systems, and computer readable media for source peer capacity-based Diameter load sharing are disclosed. According to one aspect, the subject matter described herein includes a method for source peer capacity-based Diameter load sharing. A network element for processing Diameter messages received from a Diameter peer requests information regarding a Diameter message capacity requirement of the Diameter peer, receives information regarding the Diameter message capacity requirement of the Diameter peer, and uses the received information to load share the processing. In one embodiment, the network element is a Diameter signaling router having multiple message processors for processing Diameter messages, and the information regarding the Diameter message capacity requirement of the Diameter peer is used to load share Diameter message processing and/or Diameter connections among the multiple message processors.

Claims

1. A method for source peer capacity-based Diameter load sharing, the method comprising:

at a network element for processing Diameter messages received from a Diameter peer;

requesting information regarding a Diameter message capacity requirement of the Diameter peer;

receiving information regarding the Diameter message capacity requirement of the Diameter peer; and

using the received information to load share the processing.

2. The method of claim 1 wherein the network element comprises a Diameter signaling router.

3. The method of claim 1 wherein requesting information regarding a Diameter message capacity requirement of the Diameter peer includes requesting information in response to receiving a Diameter connection request message from the Diameter peer.

4. The method of claim 1 wherein the information regarding a Diameter message capacity requirement includes a Diameter transaction rate capacity.

5. The method of claim 4 wherein the Diameter transaction rate capacity includes a value indicating Diameter transactions per second (TPS).

6. The method of claim 1 wherein the Diameter message capacity requirement of the Diameter peer is statically provisioned.

7. The method of claim 1 wherein the Diameter message capacity requirement of the Diameter peer is dynamically provisioned.

8. The method of claim 7 wherein requesting information regarding a Diameter message capacity requirement includes using a Diameter capabilities exchange request (CER) message.

9. The method of claim 7 wherein receiving information regarding the Diameter message capacity requirement includes receiving a Diameter capabilities exchange answer (CEA) message.

10. The method of claim 1 wherein the Diameter message capacity requirement includes at least one of a Diameter message sourcing capacity and a Diameter message receipt capacity.

11. The method of claim 1 wherein using the received information to load share the processing includes using the received information to load share Diameter message traffic.

12. The method of claim 11 wherein using the received information to load share Diameter message traffic includes using the information to at least one of load share Diameter connection requests and load share Diameter connections.

13. The method of claim 1 wherein using the received information to load share the processing includes using information stored in a peer capacity table (PCT) for maintaining, for each Diameter peer in communication with the network element, a Diameter message capacity requirement of the respective Diameter peer.

14. The method of claim 1 wherein the Diameter message capacity requirement comprises a Diameter message handling capacity associated with an application and wherein using the received information to load share the processing includes using the received information to load share the processing among a plurality of instances of the application.

15. The method of claim 12 wherein using the received information to load share the processing among a plurality of instances of the application includes:

using the received information to select an application from the plurality of applications; and

directing Diameter message traffic to the selected application.

16. The method of claim 1 wherein the network element includes a plurality of message processors for processing Diameter messages and wherein using the received information to load share the processing includes using the received information to load share the processing among the plurality of message processors.

17. The method of claim 16 wherein using the received information to load share, among the plurality of message processors, Diameter message traffic received from the Diameter peer includes:

using the received information to select a message processor from the plurality of message processors; and

directing Diameter message traffic to the selected message processor.

18. The method of claim 16 wherein using the received information to load share the processing includes using the received information at least one of the plurality of message processors.

19. The method of claim 16 wherein using the received information to load share the processing includes using the received information at a load balancing module separate from the plurality of message processors.

20. The method of claim 16 wherein using the received information to load share the processing among the plurality of message processors includes selecting a message processor from the plurality of message processors based on a Diameter message capacity of at least one of the plurality of message processors.

21. The method of claim 16 wherein using the received information to load share load share the processing among the plurality of message processors includes using a message processor capacity table (MCT) for maintaining, for each message processor of the network element, a Diameter message capacity of the respective message processor.

22. A system for source peer capacity-based load sharing of Diameter message processing, the system comprising:

a network element for processing Diameter messages received from a Diameter peer, the network element including at least one message processor for processing the Diameter signaling messages, wherein the network element is configured to;

request information regarding a Diameter message capacity requirement of the Diameter peer;

receive information regarding the Diameter message capacity requirement of the Diameter peer; and

use the received information to load share the processing.

23. The system of claim 22 wherein the network element comprises a Diameter signaling router.

24. The system of claim 22 wherein the network element is configured to request the information regarding a Diameter message capacity requirement of the Diameter peer in response to receiving a Diameter connection request message from the Diameter peer.

25. The system of claim 22 wherein the information regarding a Diameter message capacity requirement of the Diameter peer includes a Diameter transaction rate capacity of the Diameter peer.

26. The system of claim 22 wherein the Diameter transaction rate capacity includes a value indicating Diameter transactions per second (TPS).

27. The system of claim 22 wherein the Diameter message capacity requirement of the Diameter peer is statically provisioned.

28. The system of claim 22 wherein the Diameter message capacity requirement of the Diameter peer is dynamically provisioned.

29. The system of claim 28 wherein requesting information regarding a Diameter message capacity requirement of the Diameter peer includes sending a Diameter capabilities exchange request (CER) message.

30. The system of claim 28 wherein receiving information regarding the Diameter message capacity requirement of the Diameter peer includes receiving a Diameter capabilities exchange answer (CEA) message.

31. The system of claim 22 wherein the Diameter message capacity requirement includes at least one of a Diameter message sourcing capacity and a Diameter message receipt capacity.

32. The system of claim 22 wherein using the received information to load share the processing includes using the received information to load share Diameter message traffic.

33. The system of claim 32 wherein using the received information to load share Diameter message traffic includes using the information to at least one of load share Diameter connection requests and load share Diameter connections.

34. The system of claim 22 wherein the network element includes a peer capacity table (PCT) for maintaining, for each Diameter peer in communication with the network element, a Diameter message capacity requirement of the respective Diameter peer, wherein the network element uses information stored in the PCT to load share the processing.

35. The system of claim 22 wherein the Diameter message capacity requirement comprises a Diameter message handling capacity associated with an application and wherein using the received information to load share the processing includes using the received information to load share the processing among a plurality of instances of the application.

36. The system of claim 35 wherein using the received information to load share the processing among a plurality of instances of the application includes:

using the received information to select an application from the plurality of applications; and

directing Diameter message traffic to the selected application.

37. The system of claim 22 wherein the at least one message processor includes a plurality of message processors for processing Diameter messages and wherein using the received information to load share the processing includes using the received information to load share the processing among the plurality of message processors.

38. The system of claim 37 wherein using the received information to load share the processing among the plurality of message processors includes:

using the received information to select a message processor from the plurality of message processors; and

directing Diameter message traffic to the selected message processor.

39. The system of claim 37 wherein at least one of the plurality of message processors is configured to use the received information to load share the processing.

40. The system of claim 37 wherein the network element includes a load balancing module separate from the plurality of message processors for using the received information to load share the processing.

41. The system of claim 37 wherein using the received information to load share the processing among the plurality of message processors includes selecting a message processor from the plurality of message processors based on a Diameter message capacity of at least one of the plurality of message processors.

42. The system of claim 37 wherein the network element includes a message processor capacity table (MCT) for maintaining, for each message processor of the network element, a Diameter message capacity of the respective message processor, wherein the network element uses information stored in the MCT to load share the processing.

43. A non-transitory computer readable medium having stored thereon executable instructions that when executed by the processor of a computer control the computer to perform steps comprising:

at a network element for processing Diameter messages received from a Diameter peer;

requesting information regarding a Diameter message capacity requirement of the Diameter peer;

receiving information regarding the Diameter message capacity requirement of the Diameter peer; and

using the received information to load share the processing.