IP Trunk Groups for Scalable VoIP Call Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional network communication systems lack flexibility and scalability when routing Voice over Internet Protocol (VoIP) calls, as they require dedicated edge devices for customer networks, leading to inefficiencies and sensitivity to changes in IP addresses, which can disrupt billing and operations.
Innovation Solution
The definition and use of Internet Protocol (IP) trunk groups, which group IP interconnections with common attributes to route calls efficiently across networks, introducing abstraction between backbone and customer networks, enabling scalable and flexible call routing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If dedicated outbound edge devices are assigned to each customer network, then call routing can be established, but flexibility and scalability are reduced and the system becomes highly sensitive to customer network changes
Solution Approach 1:
The patent segments the routing system into two distinct layers: a control plane that manages routing decisions and a data plane that handles actual call traffic. This segmentation allows the core routing devices to operate independently from customer network changes, while edge devices can be dynamically assigned and reassigned without affecting the core infrastructure. The routing tree structure further segments the customer network hierarchy, enabling independent management of different customer networks.
Solution Approach 2:
The patent introduces an intermediary routing layer with core routing devices that act as mediators between the backbone network and customer edge devices. These core routing devices maintain routing trees that abstract the underlying customer network topology, shielding the backbone network from direct exposure to customer network changes. The intermediary layer translates customer-specific routing requirements into backbone network routing decisions.
2Ease of operation
If core routing devices are programmed with detailed customer network interconnection information, then routing decisions can be made, but processing complexity increases and efficiency decreases
Solution Approach 1:
The patent extracts detailed customer network interconnection information from the core routing devices and places it in the routing trees maintained at edge devices and in the routing database. Core routing devices only retain high-level routing policies and routing tree structures, not the detailed IP address mappings and interconnection topologies. This extraction significantly reduces the processing complexity of core routing devices while preserving full routing capability.
Solution Approach 2:
The patent changes the dimension of routing information storage from a flat, detailed mapping in core routing devices to a hierarchical structure distributed across multiple levels. Routing trees organize customer network information in a tree structure where core routing devices operate at higher levels with aggregated information, while detailed interconnection data resides at lower levels in edge devices and routing databases.
3Reliability
If outbound devices are dedicated to customer networks, then routing can be established, but the system becomes highly sensitive to IP address changes requiring updates across multiple infrastructure levels
Solution Approach 1:
The patent implements preliminary action by maintaining routing trees that are pre-configured with customer network information at edge devices and in routing databases. When IP address changes occur in customer networks, the updates are contained to specific portions of the routing tree at the edge level, without requiring propagation to core routing devices or backbone network infrastructure. This preliminary structuring of routing information isolates change propagation.
Solution Approach 2:
The patent provides beforehand cushioning by creating an abstraction layer through routing trees that cushions the backbone network infrastructure from direct impact of customer network changes. The routing tree structure acts as a buffer that absorbs and localizes the impact of IP address changes, preventing ripple effects through the entire infrastructure. Edge devices and routing databases absorb the shock of changes before they can propagate to core routing devices.
4Adaptability or versatility
If changes to customer network IP addresses are made, then network flexibility is improved, but billing accuracy and operational consistency are compromised due to lack of coordination
Solution Approach 1:
The patent implements feedback mechanisms where routing tree updates and customer network changes are tracked and communicated across the infrastructure. When IP address changes occur, the routing database and edge devices provide feedback about the changes, enabling coordinated updates to billing systems and operations. This feedback loop ensures that billing accuracy is maintained even as network flexibility increases through dynamic IP address assignments.
Data Source
AI summary
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.