ENUM-Based IP Carrier Peering via Breakout Gateway
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network technologies lack interoperability between telecommunications carriers, preventing subscribers from one carrier from accessing IP-to-IP services with subscribers from another carrier, which limits service quality, revenue, and functionality for both users and businesses.
Innovation Solution
A system and method for enabling IP carrier peering using ENUM-based routing, where an outbound IP call from one carrier is forwarded to a breakout gateway control function, which initiates a modified ENUM query through an internetwork packet exchange partner network, allowing connection to a second carrier's user device even if the first carrier's private ENUM does not have a matching record.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If carriers operate strictly in their own network islands with private ENUM, then each carrier maintains network independence and control, but interoperability between carriers is lost and subscribers cannot access IP-to-IP services across carriers
Solution Approach 1:
The patent introduces a public ENUM infrastructure as an intermediary between carriers with private ENUM systems. When a carrier's private ENUM cannot resolve a number, the query is redirected to the public ENUM system which acts as a mediator to find the destination carrier and enable inter-carrier routing. This allows interoperability while preserving carrier independence.
Solution Approach 2:
The patent creates a universal ENUM resolution system that handles both intra-carrier and inter-carrier queries. The system can query private ENUM first for fast intra-carrier resolution, then fall back to public ENUM for inter-carrier resolution, providing multi-functional capability in a single architecture.
2Productivity
If carriers implement private ENUM for routing, then call routing within the carrier is efficient, but calls to other carriers require additional intervention and complexity
Solution Approach 1:
The patent segments the ENUM resolution process into two distinct phases: first querying the private ENUM for intra-carrier efficiency, then querying the public ENUM for inter-carrier routing. This segmentation allows each phase to be optimized independently while working together to solve the overall routing problem.
Solution Approach 2:
The system performs preliminary action by first querying the private ENUM before attempting public ENUM resolution. This preliminary check enables fast resolution for domestic calls without involving the more complex public ENUM system, reserving public ENUM queries only for cases where private ENUM fails.
3Reliability
If the first carrier's private ENUM is used to forward calls, then the carrier maintains control over call flow, but call termination is delayed due to unnecessary intervention
Solution Approach 1:
The patent applies partial action by having the private ENUM participate only partially in the resolution process - it performs the initial query but does not need to complete the entire resolution chain. The system stops involving the private ENUM once it determines the call is inter-carrier, avoiding excessive intervention while maintaining necessary control.
Data Source
AI summary
A system for providing an architecture for enabling internet protocol (IP) carrier peering is disclosed. The system provides mechanisms for providing carrier telephone number mapping (ENUM)-based routing for subscribers of a first carrier to locate and connect with subscribers of another IP peering carrier. The system may receive an IP call from a first device of a first carrier that is destined for a second device of a second carrier. The call is forwarded to a breakout gateway control function/transit function that initiates a modified ENUM query to an internetwork packet exchange partner (IPX-P) network using an intercarrier ENUM apex domain. To retrieve a record for routing the call, the modified ENUM query is sent to an IPX-P ENUM via a domain name service name server record configuration directing to the IP address of the IPX-P ENUM. Based on the record, the call is then routed to the second device.