IP Library Granted Patent US 7,995,561
Granted Patent B2
US 7,995,561 · App. 11/608,061 · Granted Aug 9, 2011

Techniques for implementing logical trunk groups with session initiation protocol (SIP)

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,995,561
App. No.
11/608,061
Granted
Aug 9, 2011
Kind
B2
Abstract

Techniques for implementing logical trunk groups with session initiation protocol (SIP) are disclosed. In one particular exemplary embodiment, the techniques may be realized as an apparatus for implementing logical trunk groups with session initiation protocol (SIP). The apparatus may comprise a first network device and a second network device that are configured to exchange SIP signaling messages. Network traffic between the first network device and the second network device may be segregated into one or more logical groups. The SIP signaling messages associated with each logical group may include a Route header that uniquely identifies the logical group between the first network device and the second network device.

Claims (48)

1. An apparatus for implementing logical trunk groups with session initiation protocol (SIP), the apparatus comprising:

a first internal SIP-enabled network node and a second internal SIP-enabled network node that are configured to exchange SIP signaling messages, wherein the first internal SIP-enabled network node is coupled to at least one ingress trunk group and the second internal SIP-enabled network node is coupled to at least one egress trunk group;

wherein network traffic between the first internal SIP-enabled network node and the second internal SIP-enabled network node is segregated into one or more SIP logical groups;

wherein the SIP signaling messages associated with each logical group include a Route header that uniquely identifies the logical group between the first internal SIP-enabled network node and the second internal SIP-enabled network node; and

wherein the Route header comprises a unique identifier for the logical group disposed adjacent to an IP address associated with an intermediate SIP-enabled network node through which the messages are to be routed.

2. The apparatus according to claim 1 , wherein the first internal SIP-enabled network node is further configured to:

receive voice calls;

segregate the voice calls into the one or more SIP logical groups; and

route the segregated voice calls to the second internal SIP-enabled network node according to their respective logical groups.

3. The apparatus according to claim 2 , wherein the second internal SIP-enabled network node is further configured to process and route the voice calls based on their respective logical groups.

4. The apparatus according to claim 2 , wherein the voice calls are segregated based on one or more parameters selected from a group consisting of: call type, call origin, call destination, carrier identity, caller group, and time division multiplexing (TDM) trunk parameters.

5. The apparatus according to claim 1 , wherein the first internal SIP-enabled network node is further configured to:

receive the network traffic;

segregate the network traffic into the one or more SIP logical groups based on media types; and

route the segregated network traffic to the second internal SIP-enabled network node according to their respective logical groups.

6. The apparatus according to claim 1 , wherein a SIP universal resource identifier (URI) in the Route header comprises a unique identifier for the logical group.

7. A method for implementing logical trunk groups with session initiation protocol (SIP), the method comprising:

configuring a first internal SIP-enabled network node to exchange SIP signaling messages with a second internal SIP-enabled network node, wherein the first internal SIP-enabled network node is coupled to at least one ingress trunk group and the second internal SIP-enabled network node is coupled to at least one egress trunk group;

segregating, via at least one computer processor, network traffic between the first internal SIP-enabled network node and the second internal SIP-enabled network node into one or more SIP logical groups; and

including, in the SIP signaling messages associated with each logical group, a Route header that uniquely identifies the logical group between the first internal SIP-enabled network node and the second internal SIP-enabled network node, wherein the Route header comprises a unique identifier for the logical group disposed adjacent to an IP address associated with an intermediate SIP-enabled network node through which the messages are to be routed.

8. The method according to claim 7 , further comprising configuring the first internal SIP-enabled network node to:

receive voice calls;

segregate the voice calls into the one or more SIP logical groups; and

route the segregated voice calls to the second internal SIP-enabled network node according to their respective logical groups.

9. The method according to claim 8 , further comprising configuring the second internal SIP-enabled network node to process and route the voice calls based on their respective logical groups.

10. The method according to claim 8 , wherein the voice calls are segregated based on one or more parameters selected from a group consisting of: call type, call origin, call destination, carrier identity, caller group, and time division multiplexing (TDM) trunk parameters.

11. The method according to claim 7 , further comprising configuring the first internal SIP-enabled network node to:

receive the network traffic;

segregate the network traffic into the one or more SIP logical groups based on media types; and

route the segregated network traffic to the second internal SIP-enabled network node according to their respective logical groups.

12. The method according to claim 7 , wherein a SIP universal resource identifier (URI) in the Route header comprises a unique identifier for the logical group.

13. At least one non-transitory processor readable storage medium storing a computer program of instructions configured to be readable by at least one processor for instructing the at least one processor to execute a computer process for performing the method as recited in claim 7 .

14. An apparatus for implementing logical trunk groups with session initiation protocol (SIP), the apparatus comprising:

a communication module;

a processor that is configured to exchange signaling messages, via the communication module, with at least one internal SIP-enabled network node based on SIP, wherein the at least one internal SIP-enabled network node is coupled to at least one ingress trunk group;

wherein network traffic between the processor and the at least one internal SIP-enabled network node are segregated into one or more SIP logical groups;

wherein SIP messages associated with each logical group include a Route header that uniquely identifies the logical group between the processor and the at least one internal SIP-enabled network node; and

wherein the Route header comprises a unique identifier for the logical group disposed adjacent to an IP address associated with an intermediate SIP-enabled network node through which the messages are to be routed.

15. The apparatus according to claim 14 , wherein the processor is further configured to:

receive voice calls;

segregate the voice calls into the one or more SIP logical groups; and

route the segregated voice calls to the at least one internal SIP-enabled network node according to their respective logical groups.

16. The apparatus according to claim 15 , wherein the voice calls are segregated based on one or more parameters selected from a group consisting of: call type, call origin, call destination, carrier identity, caller group, and time division multiplexing (TDM) trunk parameters.

17. The apparatus according to claim 14 , wherein the processor is further configured to:

receive the network traffic;

segregate the network traffic into the one or more SIP logical groups based on media types; and

route the segregated network traffic to the at least one internal SIP-enabled network node according to their respective logical groups.

18. The apparatus according to claim 14 , wherein a SIP universal resource identifier (URI) in the Route header comprises a unique identifier for the logical group.

Assignments (9)
RELEASE OF SECURITY INTEREST Recorded Oct 26, 2020
From: JEFFERIES FINANCE LLC
To: RPX CLEARINGHOUSE LLC
Reel/Frame 054305/0505 →
SECURITY INTEREST Recorded Jun 29, 2018
From: RPX CLEARINGHOUSE LLC
To: JEFFERIES FINANCE LLC
Reel/Frame 046485/0644 →
RELEASE (REEL 038041 / FRAME 0001) Recorded Jan 2, 2018
From: JPMORGAN CHASE BANK, N.A.
To: RPX CORPORATION; RPX CLEARINGHOUSE LLC
Reel/Frame 044970/0030 →
SECURITY AGREEMENT Recorded Mar 9, 2016
From: RPX CORPORATION; RPX CLEARINGHOUSE LLC
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 038041/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 9, 2015
From: ROCKSTAR CONSORTIUM US LP; ROCKSTAR CONSORTIUM LLC; BOCKSTAR TECHNOLOGIES LLC; CONSTELLATION TECHNOLOGIES LLC; MOBILESTAR TECHNOLOGIES LLC; NETSTAR TECHNOLOGIES LLC
To: RPX CLEARINGHOUSE LLC
Reel/Frame 034924/0779 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 5, 2014
From: ROCKSTAR CONSORTIUM US LP
To: CONSTELLATION TECHNOLOGIES LLC
Reel/Frame 032162/0524 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 30, 2014
From: ROCKSTAR BIDCO, LP
To: ROCKSTAR CONSORTIUM US LP
Reel/Frame 032097/0753 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 28, 2011
From: NORTEL NETWORKS LIMITED
To: ROCKSTAR BIDCO, LP
Reel/Frame 027143/0717 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 7, 2006
From: LI, XUEWEN; WANG, XIAOHONG; NAGDI, JUJAR
To: NORTEL NETWORKS LIMITED
Reel/Frame 018598/0506 →