Geographic Trunk Groups for VoIP Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional network communication systems lack flexibility and scalability, particularly in routing VoIP calls across multiple networks, leading to inefficiencies and sensitivity to customer network changes, which affects billing and operations.
Innovation Solution
The implementation of Internet Protocol (IP) trunk groups and geographic trunk groups (GTGs) that define logical interconnections with common attributes, allowing core routing engines to efficiently route calls across networks while insulating backbone infrastructure from customer network changes and enabling scalable traffic distribution.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If outbound edge devices are dedicated to each customer network with hard-coded routing trees, then call routing can be determined efficiently, but the system lacks flexibility and scalability
Solution Approach 1:
The patent segments the routing function by introducing intermediate trunk groups that separate customer-specific routing from backbone infrastructure. Each customer network is assigned a dedicated trunk group identifier, allowing independent routing decisions at the edge while maintaining a simplified, standardized backbone routing structure. This segmentation enables efficient customer-specific routing without hard-coding entire routing trees in backbone devices.
Solution Approach 2:
The patent introduces trunk groups as intermediary logical structures between customer networks and the backbone. These trunk groups act as mediators that translate customer-specific routing requirements into standardized backbone routing decisions. The trunk group identifier serves as an intermediary key that allows core routing devices to route calls efficiently without needing detailed knowledge of customer network topologies.
2Measurement precision
If core routing devices are programmed with detailed customer network interconnection information, then accurate routing can be achieved, but the core routing devices become inefficient due to complex processing requirements
Solution Approach 1:
The patent extracts detailed customer network interconnection information from core routing devices and places it at the edge in trunk group configurations. The trunk groups carry the customer-specific routing details locally, allowing edge devices to make accurate routing decisions without requiring core routing devices to store and process extensive customer network topology information. This extraction simplifies core routing device processing while maintaining routing accuracy.
3Adaptability or versatility
If customer network IP addresses change, then the network can adapt to new configurations, but the changes ripple through the backbone network requiring updates at multiple levels
Solution Approach 1:
The patent segments the network infrastructure into customer-specific trunk groups that are isolated from the backbone routing infrastructure. When customer network IP addresses change, only the trunk group configuration at the edge needs to be updated, not the entire backbone network. This segmentation contains the impact of changes locally at the customer edge while maintaining backbone stability.
Solution Approach 2:
The trunk groups serve as intermediaries that absorb and contain customer network configuration changes. The trunk group identifier acts as a stable reference point that decouples customer network dynamics from backbone routing stability. Changes in customer IP addresses are absorbed within the trunk group layer, preventing ripples through the backbone infrastructure.
4Productivity
If dedicated outbound devices are used for each customer, then routing can be optimized for each customer, but the system becomes highly sensitive to customer network changes
Solution Approach 1:
The patent introduces dynamic configuration capabilities at the trunk group level, allowing routing parameters to be adjusted without affecting the entire backbone network. The trunk group structure enables dynamic customer network changes to be absorbed through localized reconfiguration, maintaining system stability while preserving customer-specific routing optimization. Core routing devices maintain stable, simplified configurations while edge trunk groups adapt dynamically to customer needs.
Data Source
AI summary
Embodiments of the invention include a method for routing an Internet Protocol (IP)-based call through a first IP-based network to a second IP-based network. The method includes receiving an IP-based call request in the first network; identifying one or more geographic trunk groups that can be used to route the call request out of the first network, wherein each of the one or more geographic trunk groups represents a logical grouping of one or more IP trunk groups between the first IP-based network and the second IP-based network; selecting one of the one or more geographic trunk groups; and routing the received call request via the selected geographic trunk group to an IP address associated with the selected geographic trunk group. Other embodiments are also disclosed.