Register clustering in a sip-based network

• US 7,970,916 B2
• Filed: 07/25/2007
• Issued: 06/28/2011
• Est. Priority Date: 07/25/2007
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Shanmugham, Saravanan
• Primary Examiner(s): Joo; Joshua
• Application Number:
  US11/828,046
• Publication Number:
  US 20090031032A1
• Time in Patent Office: 1,434 Days
• Field of Search: 709201-203, 709227-229, 709/238, 370/352
• US Class Current: 709/229
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 65/1073 Registration or de-registration
• 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/288 Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/563 Data redirection of data network streams

Abstract

In one embodiment, a method can include: receiving a request for service in a first edge proxy; applying a hash function to a source address of an endpoint; and forwarding the request to a second edge proxy in response to a first result of the hash function, or servicing the request in the first edge proxy in response to a second result of the hash function.

Claims

1. A method, comprising:

receiving in a first edge proxy, a registration request for service from an endpoint;

applying a hash function to a source address of the endpoint by performing a lookup of a hash table in the first edge proxy;

forwarding the registration request from the first edge proxy to a second edge proxy in response to occurrence of a first output result of the hash function indicating that the second edge proxy is provisioned to service the registration request; and

servicing the registration request including registering the source address of the endpoint in the first edge proxy in response to occurrence of a second output result of the hash function indicating that the first edge proxy is provisioned to service the registration request, wherein the second edge proxy is also configured with the hash function for registration requests.

2. The method of claim 1, wherein the registration request comprises a session initiation protocol (SIP) REGISTER message.

3. The method of claim 1, further comprising sending the registration request to a service controller when the registration request comprises a SIP INVITE message.

4. The method of claim 1, wherein the hash function comprises a consistent hash function.

5. The method of claim 1, further comprising updating the hash table in the first edge proxy in response to a failure of a third edge proxy.

6. The method of claim 5, wherein a hash table in the second edge proxy is also updated in response to the failure of the third edge proxy.

7. The method of claim 1, further comprising periodically updating the hash table in the first edge proxy.

8. The method of claim 7, wherein a hash table in the second edge proxy is also periodically updated.

9. The method of claim 1, wherein the first and second edge proxies comprise SIP edge proxies.

10. A method, comprising:

sending a lookup request from an endpoint to a domain name system (DNS) server;

receiving a response from the DNS server, the response including a prioritized list of edge proxies for servicing a registration request from the endpoint;

sending the registration request from the endpoint to a first edge proxy in the prioritized list, wherein the first edge proxy is selected by the endpoint from among any proxies in the prioritized list; and

receiving an acknowledgement from the first edge proxy or a second edge proxy in response to hash function result in the first edge proxy, the hash function result being determined by hashing a source address of the endpoint using a hash table in the first edge proxy, wherein the hash function result indicates which of the first and second edge proxies is provisioned to service the registration request from the endpoint, wherein the registration request is serviced by registering the source address of the endpoint in the first edge proxy or the second edge proxy in response to the hash function result, the second edge proxy also being configured to provide the hash function result for registration requests.

11. The method of claim 10, wherein the registration request comprises a session initiation protocol (SIP) REGISTER message.

12. The method of claim 10, wherein the hash function result comprises use of a consistent hash function, the consistent hash function being configured to map buckets to nodes.

13. The method of claim 10, further comprising updating the hash table in response to a failure of a third edge proxy.

14. The method of claim 10, further comprising periodically updating the hash table.

15. An apparatus, comprising:

one or more processors; and

logic encoded in one or more tangible media for execution by the one or more processors, and when executed operable to;

receive in a first edge proxy, a registration request for service from an endpoint;

apply a hash function to a source address of the endpoint by performing a lookup of a hash table in the first edge proxy;

forward the registration request from the first edge proxy to a second edge proxy in response to occurrence of a first output result of the hash function indicating that the second edge proxy is provisioned to service the registration request; and

servicing the registration request including registering the source address of the endpoint in the first edge proxy in response to occurrence of a second output result of the hash function indicating that the first edge proxy is provisioned to service the registration request, wherein the second edge proxy is also configured with the hash function for registration requests.

16. The apparatus of claim 15, wherein the logic when executed is further operable to:

send the registration request to a service controller when the registration request comprises a session initiation protocol (SIP) INVITE message.

17. The apparatus of claim 15, wherein the logic when executed is further operable to:

update the hash table in the first edge proxy in response to a failure of a third edge proxy.

18. An apparatus, comprising:

one or more processors; and

logic encoded in one or more tangible media for execution by the one or more processors, and when executed operable to;

send a lookup request from an endpoint to a domain name system (DNS) server;

receive a response from the DNS server, the response including a prioritized list of edge proxies for servicing a registration request from the endpoint;

send the registration request from the endpoint to a first edge proxy in the prioritized list, wherein the first edge proxy is selected by the endpoint from among any proxies in the prioritized list; and

receive an acknowledgment from the first edge proxy or a second edge proxy in response to a hash function result in the first edge proxy, the hash function result being determined by hashing a source address of the endpoint using a hash table in the first edge proxy, wherein the hash function result indicates which of the first and second edge proxies is provisioned to service the registration request from the endpoint, wherein the registration request is service by registering the source address of the endpoint in the first edge proxy or the second edge proxy in response to the hash function result, the second edge proxy also being configured to provide the hash function result for registration requests.

19. The apparatus of claim 18, wherein the logic when executed is further operable to:

update the hash table in response to a failure of a third edge proxy.

20. The apparatus of claim 18, wherein the logic when executed is further operable to:

periodically update the hash table.