Scalable, reliable session initiation protocol (SIP) signaling routing node

• US 7,631,093 B2
• Filed: 02/25/2005
• Issued: 12/08/2009
• Est. Priority Date: 05/30/2001
• Status: Expired due to Fees

• Current Assignee: Tekelec, Inc. (Oracle Corporation)
• Original Assignee: Tekelec
• Inventors: Sternagle, Richard Henry
• Primary Examiner(s): Tran; Philip B
• Application Number:
  US11/065,876
• Publication Number:
  US 20050157707A1
• Time in Patent Office: 1,747 Days
• Field of Search: 709223-224, 709/220, 709227-228, 709/230, 718/105
• US Class Current: 709/230
• CPC Class Codes: H04L 45/24 Multipath
• CPC Class Codes: H04L 45/38 Flow based routing
• CPC Class Codes: H04L 47/122 by diverting traffic away from congested entities
• CPC Class Codes: H04L 47/125 by balancing the load, e.g. traffic engineering
• CPC Class Codes: H04L 47/26 using explicit feedback to the source, e.g. choke packets
• CPC Class Codes: H04L 47/30 in combination with information about buffer occupancy at either end or at transit nodes
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A scalable, reliable session initiation protocol (SIP) signaling router includes cluster nodes for performing SIP services. A location server replicates its database of SIP location information to each of the cluster nodes. Because each cluster node maintains its own local copy of the SIP location database, the time for routing SIP signaling messages is decreased. Load sharing is also performed among the cluster nodes by Ethernet switches that connect the cluster nodes to external networks. One Ethernet switch periodically sends messages to each of the cluster nodes to monitor the operational status of the cluster nodes. The Ethernet switch also maintains a connection tuple table containing information regarding active connections to each of the cluster nodes. Load sharing is performed based on the operational status and the connection tuple table.

Claims

1. A method for load sharing among cluster nodes providing session initiation protocol (SIP) services, the method comprising:

(a) providing a plurality of cluster nodes for performing SIP services, wherein the SIP services include SIP proxy services, SIP redirect services, or a combination of SIP proxy/redirect services;

(b) periodically sending messages to each of the cluster nodes to monitor the operational status of each of the cluster nodes;

(c) maintaining a connection tuple table containing active connection information for each of the cluster nodes; and

(d) load sharing between the cluster nodes based on the operational status and the connection tuple table.

2. The method of claim 1 wherein providing a plurality of cluster nodes includes providing a plurality of cluster nodes for performing SIP proxy services.

3. The method of claim 1 wherein providing a plurality of cluster nodes includes providing a plurality of cluster nodes for performing SIP redirect services.

4. The method of claim 1 wherein providing a plurality of cluster nodes includes providing a plurality of cluster nodes for performing SIP proxy and redirect services.

5. The method of claim 1 wherein periodically sending messages to the cluster nodes includes periodically pinging the cluster nodes to determine lower-level protocol stack operational status of each of the cluster nodes.

6. The method of claim 1 wherein periodically sending messages to the cluster nodes includes periodically sending health check messages to the cluster nodes to determine application-level protocol stack operational status of each of the cluster nodes.

7. The method of claim 1 wherein periodically sending messages to the cluster nodes includes periodically pinging and sending health check messages to the cluster nodes to determine lower-level protocol stack and application level operational status of each of the cluster nodes.

8. The method of claim 1 wherein maintaining a connection tuple table for each of the cluster nodes includes maintaining a table containing destination IP address, source IP address, destination port number, originating port number, and MAC address of the cluster node for each connection.

9. The method of claim 1 wherein load sharing based on the operational status and the connection tuple table includes load sharing based each cluster node'"'"'s response time to the messages and the number of active connections for each node stored in the connection tuple table.

10. The method of claim 1 wherein the messages test the functionality of protocol layers 1-3 of each of the cluster nodes.

11. The method of claim 1 wherein the messages test application layer functionality of each of the cluster nodes.

12. The method of claim 1 wherein load sharing between the cluster nodes includes increasing message flow to a cluster node that responds quickly to one of the messages.

13. The method of claim 1 wherein load sharing between the cluster nodes includes increasing message flow to a cluster node that has a small number of connections in its connection table.

14. The method of claim 1 wherein load sharing between the cluster nodes includes increasing message flow to a cluster node that responds quickly to one of the messages and that has a small number of connections in its connection table.

15. The method of claim 1 wherein maintaining the connection tuple table includes maintaining a connection tuple table storing the number of connections maintained by each cluster node and wherein the number of connections maintained by each cluster node is used to perform a load sharing operation.