Internet protocol trunk groups
View Patent ↗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.
1. 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, the core routing engine further operable to 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; and
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;
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; and
wherein each of the IP trunk group definitions comprises a data structure comprising:
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 an external IP address associated with the first IP-based network;
a fourth field designating an IP address associated with the second IP-based network;
a fifth field designating a group size;
a sixth field designating a group route advance profile;
an seventh field designating a signaling normalization profile;
a eighth field designating a directionality indicator;
a ninth field designating a hunt sequence; and
a tenth field designating an allowable codecs indicator.
2. A system as recited in claim 1 , wherein the data structures each further comprise an eleventh field designating a facility name associated with the first IP-based network.
3. A system as recited in claim 1 , wherein the data structures each further comprise an eleventh field designating a facility name associated with the second IP-based network.
4. A system as recited in claim 1 wherein, wherein the data structures each further comprise an eleventh field designating a pseudo carrier code.
5. A system as recited in claim 1 wherein, wherein the data structures each further comprise an eleventh field designating an emergency services routing type.
6. A system as recited in claim 1 wherein, wherein the data structures each further comprise an eleventh field designating regulatory nature data.
7. A system as recited in claim 1 , wherein the data structures each further comprise an eleventh field designating a second IP-based network identifier.
8. A system as recited in claim 1 , wherein the data structures each further comprise an eleventh field designating a product identifier.
9. A system as recited in claim 1 , wherein the data structures each further comprise an eleventh field designating an IP interconnection type associated with the IP trunk group.
10. A system as recited in claim 1 , wherein the data structures each further comprise an eleventh field designating a load balancer IP address.
11. A system as recited in claim 1 , wherein the data structures each further comprise an eleventh field designating a load balancer type.
12. A system as recited in claim 1 , wherein the data structures each further comprise an eleventh field designating a second IP-based network edge node type.
13. 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 IP-based network;
identifying one or more IP trunk groups that can be used to route the call request out of the first IP-based 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, wherein each of the IP trunk group definitions comprises a data structure comprising:
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 an external IP address associated with the first IP-based network;
a fourth field designating an IP address associated with the second IP-based network;
a fifth field designating a group size;
a sixth field designating a group route advance profile;
a seventh field designating a signaling normalization profile;
a eighth field designating a directionality indicator;
a ninth field designating a hunt sequence; and
a tenth field designating an allowable codecs indicator;
selecting one of the one or more IP trunk groups; and
routing the received call request to an IP address associated with the selected IP trunk group.
14. A method as recited in claim 13 wherein each of the IP trunk group definitions comprises a data structure including a facility name associated with the first IP-based network.
15. A method as recited in claim 13 wherein each of the IP trunk group definitions comprises a data structure including a facility name associated with the second IP-based network.
16. A method as recited in claim 13 wherein each of the IP trunk group definitions comprises a data structure including a pseudo carrier code.
17. A method as recited in claim 13 wherein each of the IP trunk group definitions comprises a data structure including an emergency services routing type.
18. A method as recited in claim 13 wherein each of the IP trunk group definitions comprises a data structure including a regulatory nature data.
19. A method as recited in claim 13 wherein each of the IP trunk group definitions comprises a data structure including a second IP-based network identifier.
20. A method as recited in claim 13 wherein each of the IP trunk group definitions comprises a data structure including a product identifier.
21. A method as recited in claim 13 wherein each of the IP trunk group definitions comprises a data structure including an IP interconnection type associated with the IP trunk group.
22. A method as recited in claim 13 wherein each of the IP trunk group definitions comprises a data structure including a load balancer IP address.
23. A method as recited in claim 13 wherein each of the IP trunk group definitions comprises a data structure including a load balancer type.
24. A method as recited in claim 13 wherein each of the IP trunk group definitions comprises a data structure including a second IP-based network edge node type.
25. A method as recited in claim 13 further comprising:
selecting one of the one or more IP trunk groups, wherein selecting the one of the one or more IP trunk group is based on an IP trunk group (IPTG) traffic distribution policy specifying how to distribute calls among IPTGs within a set of IPTGs and the IPTG traffic distribution policy is selected from a group consisting of: sequential; round robin; and percentage allocation.