Method and system of partitioning a signaling protocol

• US 20070076855A1
• Filed: 09/15/2006
• Published: 04/05/2007
• Est. Priority Date: 09/16/2005
• Status: Active Grant

• Current Assignee: Acme Packet Incorporated (Oracle Corporation)
• Original Assignee: Acme Packet Incorporated (Oracle Corporation)
• Inventors: Penfield, Robert, MeLampy, Patrick
• Granted Patent: US 8,072,966 B2
• Time in Patent Office: Days
• US Class Current: 379/88.170
• CPC Class Codes: H04L 12/4625 Single bridge functionality, e.g. connection of two networks over a single bridge
• CPC Class Codes: H04L 41/0668 by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 65/103 in the network
• CPC Class Codes: H04L 65/1033 Signalling gateways
• CPC Class Codes: H04L 65/1036 at the edge
• CPC Class Codes: H04L 65/104 in the network
• CPC Class Codes: H04L 65/1043 Gateway controllers, e.g. media gateway control protocol [MGCP] controllers
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 65/65 Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
• CPC Class Codes: H04L 65/80 Responding to QoS
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/101 based on network conditions
• CPC Class Codes: H04L 69/24 Negotiation of communication capabilities
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06
• CPC Class Codes: H04Q 2213/13034 A/D conversion, code compression/expansion
• CPC Class Codes: H04Q 2213/1307 Call setup
• CPC Class Codes: H04Q 2213/13098 : Mobile subscriber
• CPC Class Codes: H04Q 2213/13178 : Control signals
• CPC Class Codes: H04Q 2213/13196 : Connection circuit/link/trunk/junction, bridge, router, gateway
• CPC Class Codes: H04Q 2213/13204 : Protocols
• CPC Class Codes: H04Q 2213/13348 : Channel/line reservation
• CPC Class Codes: H04Q 2213/13389 : LAN, internet

Abstract

Systems and methods for partitioning session initial protocol (SIP) processing among execution units are disclosed. An exemplary device comprises: a plurality of execution units and a plurality of session initiation protocol (SIP) processes. The SIP processes comprise: a SIP transport process; a SIP location server process; and a plurality of SIP core processes. The SIP transport process executes on a first one of the execution units. The SIP location server executes on a second one of the execution units. Each of the SIP core processes executes on a different remaining one of the execution units. An exemplary method comprises: executing a SIP transport process on a first one of the execution units; executing a SIP location server on a second one of the execution units, and executing each of the SIP core processes on a different remaining one of the execution units.

Claims

1. A network device comprising:

a plurality of execution units;

a plurality of session initiation protocol (SIP) processes comprising;

a SIP transport process;

a SIP location server process; and

a plurality of SIP core processes,

the SIP transport process executing on a first one of the execution units,

the SIP location server executing on a second one of the execution units, and

each of the SIP core processes executing on a different remaining one of the execution units.

2. The network device of claim 1, further comprising an auxiliary function called by at least one of the SIP processes, wherein the auxiliary function executes on one of the execution units that is not executing one of the SIP processes.

3. The network device of claim 1, further comprising a plurality of auxiliary functions, each auxiliary function called by at least one of the SIP processes, wherein each of the auxiliary functions executes on a different one of the execution units that is not executing one of the SIP processes.

4. The network device of claim 3, wherein the plurality of auxiliary functions includes at least one of a RADIUS server;

a socket front end; and

a media controller.

5. The network device of claim 1, wherein the processes executing on the execution units communicate through an in-sequence, reliable message service.

6. The network device of claim 1, wherein each of the execution units are coupled to each other via an Ethernet switch.

7. The network device of claim 1, wherein at least one of the execution units is a core of a multi-core microprocessor.

8. A method for partitioning a plurality of session initiation protocol (SIP) processes among a plurality of execution units, the method comprising the steps of:

executing a SIP transport process on a first one of the execution units,

executing a SIP location server on a second one of the execution units, and

executing each of the SIP core processes on a different remaining one of the execution units.

9. The method of claim 8, further comprising the step of:

executing an auxiliary function on one of the execution units that is not executing one of the SIP processes.

10. The method of claim 9, wherein the plurality of auxiliary functions includes at least one of a RADIUS server;

a socket front end; and

a media controller.

11. The method of claim 8, further comprising the step of:

executing a plurality of auxiliary functions, each auxiliary function executing on a different one of the execution units that is not executing one of the SIP processes.

12. The method of claim 8, wherein the processes communicate through an in-sequence, reliable message service.

13. The system of claim 8, wherein each of the execution units is coupled to each other via an Ethernet switch.

14. A system for partitioning a plurality of session initiation protocol (SIP) processes among a plurality of execution units, the system comprising the steps of:

means for executing a SIP transport process on a first one of the execution units,

means for executing a SIP location server on a second one of the execution units, and

means for executing each of the SIP core processes on a different remaining one of the execution units.

15. The system of claim 14, further comprising the step of:

means for executing an auxiliary function on one of the execution units that is not executing one of the SIP processes.

16. The system of claim 15, wherein the plurality of auxiliary functions includes at least one of a RADIUS server;

a socket front end; and

a media controller.

17. The system of claim 14, further comprising the step of:

means for executing a plurality of auxiliary functions, each auxiliary function executing on a different one of the execution units that is not executing one of the SIP processes.

18. The system of claim 14, wherein the processes communicate through an in-sequence, reliable message service.

19. The system of claim 14, wherein each of the means for executing is coupled to each other via an Ethernet switch.

20. The system of claim 14, wherein at least one of the means for executing is a core of a multi-core microprocessor.