Methods, media, and systems for balancing session initiation protocol server load

• US 20080228926A1
• Filed: 03/13/2007
• Published: 09/18/2008
• Est. Priority Date: 03/13/2007
• Status: Abandoned Application

• Current Assignee: Avaya Incorporated
• Original Assignee: Avaya Incorporated
• Inventors: Shiratzky, Asher, Dieugenio, Stephen, Gabai, Yossi, Loeb, Danny
• Application Number:
  US11/717,365
• Publication Number:
  US 20080228926A1
• Time in Patent Office: Days
• US Class Current: 709/228
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1023 based on a hash applied to IP addresses or costs
• CPC Class Codes: H04L 67/1034 Reaction to server failures by a load balancer
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066

Abstract

In some embodiments, methods for balancing SIP server load are provided. In these methods, a message is received and a session identifier and a resource identifier are extracted from the message. The methods search for one or more sessions associated with the resource identifier and, if there is at least one session that is associated with the resource identifier, the methods further determine whether one of the at least one session is associated with the session identifier. If one of the at least one session is determined to be associated with the session identifier, the methods obtain a server identifier associated with the one of the at least one session and forward the message to a server associated with the server identifier.

Claims

1. A method for balancing SIP server load, the method comprising:

receiving a SIP message;

extracting a session identifier and a resource identifier from the message;

searching for one or more sessions that are associated with the resource identifier; and

if there is at least one session that is associated with the resource identifier,

determining whether one of the at least one session is associated with the session identifier; and

if one of the at least one session is determined to be associated with the session identifier,

obtaining a server identifier associated with the one of the at least one session; and

forwarding the message to a server associated with the server identifier.

2. The method of claim 1, further comprising:

if there is no session that is associated with the resource identifier,

selecting a server having resources associated with the resource identifier;

generating a new session;

assigning the new session to the server; and

forwarding the message to the server.

3. The method of claim 2, further comprising registering the new session using the session identifier, the resource identifier, and the server identifier.

4. The method of claim 2, wherein identifying the server comprises hashing the resource identifier.

5. The method of claim 1, further comprising:

if none of the at least one session is determined to be associated with the session identifier,

generating a new session;

assigning the new session to a server associated with the at least one session; and

forwarding the message to the server.

6. The method of claim 5, further comprising registering the new session using the session identifier, the resource identifier, and the server identifier.

7. The method of claim 1, wherein the session identifier comprises a SIP Call-Id header.

8. The method of claim 1, wherein the resource identifier comprises a SIP Request-URI header.

9. The method of claim 1, further comprising:

monitoring the server;

detecting a failure in the server;

identifying sessions that are handled by the server;

selecting a second server having resources for handling the sessions; and

assigning the sessions to the second server.

10. The method of claim 1, further comprising:

receiving an outbound message from one of a plurality of servers;

registering the outbound message using an originating server identifier associated with the one of a plurality of servers and at least one other identifier associated with it; and

sending the outbound message.

11. The method of claim 10, wherein the at least one other identifier comprises one of an outbound session identifier, an outbound resource identifier, and a combination thereof.

12. The method of claim 10, wherein the plurality of servers includes at least one SIP back-to-back user agent.

13. The method of claim 10, wherein the plurality of servers includes at least one event server.

14. The method of claim 10, wherein the outbound message comprises a SIP message.

15. A computer-readable medium containing computer-executable instructions that, when executed by a processor, cause the processor to perform a method for balancing SIP server load, the method comprising:

receiving a SIP message;

extracting a session identifier and a resource identifier from the message;

searching for one or more sessions that are associated with the resource identifier; and

if there is at least one session that is associated with the resource identifier,

determining whether one of the at least one session is associated with the session identifier; and

if one of the at least one session is determined to be associated with the session identifier,

obtaining a server identifier associated with the one of the at least one session; and

forwarding the message to a server associated with the server identifier.

16. The medium of claim 15, where the method further comprises:

if there is no session that is associated with the resource identifier,

selecting a server having resources associated with the resource identifier;

generating a new session;

assigning the new session to the server; and

forwarding the message to the server.

17. The medium of claim 16, where the method further comprises registering the new session using the session identifier, the resource identifier, and the server identifier.

18. The medium of claim 16, wherein identifying the server comprises hashing the resource identifier.

19. The medium of claim 15, where the method further comprises:

if none of the at least one session is determined to be associated with the session identifier,

generating a new session;

assigning the new session to a server associated with the at least one session; and

forwarding the message to the server.

20. The medium of claim 19, where the method further comprises registering the new session using the session identifier, the resource identifier, and the server identifier.

21. The medium of claim 15, wherein the session identifier comprises a SIP Call-Id header.

22. The medium of claim 15, wherein the resource identifier comprises a SIP Request-URI header.

23. The medium of claim 15, where the method further comprises:

monitoring the server;

detecting a failure in the server;

identifying sessions that are handled by the server;

selecting a second server having resources for handling the sessions; and

assigning the sessions to the second server.

24. The medium of claim 15, where the method further comprises:

receiving an outbound message from one of a plurality of servers;

registering the outbound message using an originating server identifier associated with the one of a plurality of servers and at least one other identifier associated with it; and

sending the outbound message.

25. The medium of claim 24, wherein the at least one other identifier comprises one of an outbound session identifier, an outbound resource identifier, and a combination thereof.

26. The medium of claim 24, wherein the plurality of servers includes at least one SIP back-to-back user agent.

27. The medium of claim 24, wherein the plurality of servers includes at least one event server.

28. The medium of claim 24, wherein the outbound message comprises a SIP message.

29. A device for balancing SIP server load comprising:

an interface for receiving a SIP message; and

a processor that;

extracts a session identifier and a resource identifier from the message;

searches for one or more sessions that are associated with the resource identifier; and

if there is at least one session that is associated with the resource identifier,

determines whether one of the at least one session is associated with the session identifier; and

if one of the at least one session is determined to be associated with the session identifier,

obtains a server identifier associated with the one of the at least one session; and

forwards the message to a server associated with the server identifier.

30. The device of claim 29, where the processor also:

if there is no session that is associated with the resource identifier,

selects a server having resources associated with the resource identifier;

generates a new session;

assigns the new session to the server; and

forwards the message to the server.

31. The device of claim 30, wherein the processor also registers the new session using the session identifier, the resource identifier, and the server identifier.

32. The device of claim 30, wherein identifying the server comprises hashing the resource identifier.

33. The device of claim 29, wherein the processor also:

if none of the at least one session is determined to be associated with the session identifier,

generates a new session;

assigns the new session to a server associated with the at least one session; and

forwards the message to the server.

34. The device of claim 33, wherein the processor also registers the new session using the session identifier, the resource identifier, and the server identifier.

35. The device of claim 29, wherein the session identifier comprises a SIP Call-Id header.

36. The device of claim 29, wherein the resource identifier comprises a SIP Request-URI header.

37. The device of claim 29, wherein the processor also:

monitors the server;

detects a failure in the server;

identifies sessions that are handled by the server;

selects a second server having resources for handling the sessions; and

assigns the sessions to the second server.

38. The device of claim 29, wherein the interface also receiving an outbound message from one of a plurality of servers and the processor also:

registers the outbound message using an originating server identifier associated with the one of a plurality of servers and at least one other identifier associated with it; and

sends the outbound message.

39. The device of claim 38, wherein the at least one other identifier comprises one of an outbound session identifier, an outbound resource identifier, and a combination thereof.

40. The device of claim 38, wherein the plurality of servers includes at least one SIP back-to-back user agent.

41. The device of claim 38, wherein the plurality of servers includes at least one event server.

42. The device of claim 38, wherein the outbound message comprises a SIP message.