Internet protocol trunk groups

• US 8,520,667 B2
• Filed: 09/20/2010
• Issued: 08/27/2013
• Est. Priority Date: 08/30/2006
• Status: Active Grant

• Current Assignee: Level 3 Communications LLC (Lumen Technologies, Inc.)
• Original Assignee: Level 3 Communications LLC (Lumen Technologies, Inc.)
• Inventors: Terpstra, Richard, Gualtieri, Greg
• Primary Examiner(s): Nguyen, Joseph J
• Application Number:
  US12/886,450
• Publication Number:
  US 20110007736A1
• Time in Patent Office: 1,072 Days
• Field of Search: 370/352, 370/230, 370/355, 370/356, 370/357, 370/465
• US Class Current: 370/352
• CPC Class Codes: H04L 12/66 Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
• CPC Class Codes: H04L 45/245 Link aggregation, e.g. trunking
• CPC Class Codes: Y02D 30/50 in wire-line communication networks, e.g. low power modes or reduced link rate

Abstract

A system includes a core routing engine operable to receive a call setup request and identify one or more IP trunk groups through which the call setup request can be routed, select one of the one or more identified IP trunk groups and route the call setup request to an internal IP address associated with the selected IP trunk group. The system may further include an IP edge node associated with the internal IP address, the IP edge node in the backbone network and operable to receive the call setup request and route the call setup request to one of a plurality of IP addresses associated with a plurality of carrier edge nodes in the carrier network.

Claims

1. A method for routing an Internet Protocol (IP)-based call through a first IP-based network to a second IP-based network, the method comprising:

receiving an IP-based call request in the first network;

identifying one or more IP trunk groups that can be used to route the call request out of the first network, wherein each of the one or more IP trunk groups represents a logical grouping of one or more IP interconnections between the first IP-based network and the second IP-based network, wherein identifying one or more IP trunk groups comprises accessing one or more IP trunk group definitions;

mapping a route label associated with a called telephone number to a set of the one or more IP trunk group definitions;

selecting one of the one or more IP trunk groups, wherein selecting one of the one or more IP trunk groups comprises selecting the IP trunk group based on an IP trunk group (IPTG) traffic distribution policy specifying how to distribute calls among IPTGs within a set of IPTGs; and

routing the received call request to an IP address associated with the selected IP trunk group.

2. The method as recited in claim 1 wherein at least one of the one or more IP trunk group definitions is associated with more than one route label.

3. The method as recited in claim 1 wherein each of the one or more IP trunk group definitions includes one or more attributes selected from a group consisting of:

an IP trunk group identifier;

an internal IP address associated with the first IP-based network;

a facility name associated with the first IP-based network;

an external IP address associated with the first IP-based network;

an IP address associated with the second IP-based network;

a facility name associated with the second IP-based network;

a group size;

a pseudo carrier code;

an emergency services routing type;

a group route advance profile;

a signaling normalization profile;

a directionality indicator;

a hunt sequence;

regulatory nature data;

a second IP-based network identifier;

an allowable codecs indicator;

a product identifier;

an IP interconnection type associated with the IP trunk group;

a load balancer IP address;

a load balancer type; and

a second IP-based network edge node type.

4. The method as recited in claim 1 wherein the IPTG traffic distribution policy is selected from a group consisting of:

sequential;

round-robin; and

percentage allocation.

5. A method for configuring a Voice over Internet Protocol (VoIP) backbone network to route calls to an IP-based carrier network, the method comprising:

identifying one or more sets of IP interconnections between the VoIP backbone network and the IP-based carrier network that have common attributes;

determining an IP interconnection type for each of the one or more identified sets of IP interconnections;

for each set of IP interconnections, defining an Internet Protocol (IP) trunk group wherein defining comprises associating the common attributes of each identified set of IP interconnections with a unique IP trunk group identifier;

accessing one or more of the defined IP trunk group; and

mapping a route label associated with a called telephone number to a set of the defined IP trunk groups.

6. A system for routing IP-based calls through a backbone network to a carrier network, the system comprising:

a core routing engine operable to receive a call setup request and identify one or more IP trunk groups through which the call setup request can be routed, based at least in part on a telephone number in the call setup request, wherein identifying the one or more IP trunk groups comprises accessing one or more IP trunk group definitions, the core routing engine further operable to map a route label associated with the telephone number to a set of the IP trunk group definitions and select one of the one or more identified IP trunk groups and route the call setup request to an internal IP address associated with the selected IP trunk group;

an IP edge node associated with the internal IP address, the IP edge node in the backbone network and operable to receive the call setup request and route the call setup request to one of a plurality of IP addresses associated with a plurality of carrier edge nodes in the carrier network; and

a redirection device operable to receive the call setup request from the IP edge node and return one or more of the plurality of IP addresses associated with the carrier edge nodes, whereby the IP edge node can select from the one or more IP addresses to which to send the call setup request.

7. The system as recited in claim 6 further comprising a proxy load balancer operable to receive the call setup request from the IP edge node and direct the call setup request to one of the plurality of IP addresses associated with the carrier edge nodes.

8. The system as recited in claim 6 further comprising a redirection device in communication with the plurality of carrier edge nodes and operable to return one or more IP addresses of IP edge nodes on the backbone network, in response to receiving a call setup request from one of the plurality of carrier edge nodes.

9. The system as recited in claim 6 further comprising a memory including a plurality of IP trunk group definitions, wherein the memory is accessible by one or more of the core routing engine and the IP edge node.

10. The system as recited in claim 9 wherein the plurality of IP trunk group definitions includes policies related to one or more of emergency call routing, IP trunk group directionality, and IP trunk group traffic distribution.

11. The system as recited in claim 9 wherein each of the IP trunk group definitions comprises a data structure including the following fields:

a first field designating an IP trunk group identifier;

a second field designating an internal IP address associated with the first IP-based network;

a third field designating a facility name associated with the first IP-based network;

a fourth field designating an external IP address associated with the first IP-based network;

a fifth field designating an IP address associated with the second IP-based network;

a sixth field designating a facility name associated with the second IP-based network;

a seventh field designating a group size;

an eighth field designating a pseudo carrier code;

a ninth field designating an emergency services routing type;

a tenth field designating a group route advance profile;

an eleventh field designating a signaling normalization profile;

a twelfth field designating a directionality indicator;

a thirteenth field designating a hunt sequence;

a fourteenth field designating regulatory nature data;

a fifteenth field designating a second IP-based network identifier;

a sixteenth field designating an allowable codecs indicator;

a seventeenth field designating a product identifier;

an eighteenth field designating an IP interconnection type associated with the IP trunk group;

a nineteenth field designating a load balancer IP address;

a twentieth field designating a load balancer type; and

a twenty-first field designating a second IP-based network edge node type.