Intercarrier ENUM Routing via DNS Recursion Zone
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current carrier architectures face challenges in interconnecting IP carriers, as they typically have only one domain configured with the ENUM client, leading to issues with finding matching entries for E.164 numbers intended for other carriers, resulting in failed IP calls.
Innovation Solution
Implementing a dynamic mechanism for carrier ENUM-based routing that modifies the ENUM domain to an intercarrier ENUM apex based domain, allowing queries to be resent to the correct carrier's Tier 2 ENUM for resolving SIP URIs and completing IP calls.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If carriers use a single domain configured with ENUM client, then device complexity is reduced, but call completion reliability deteriorates due to inability to find matching entries for E.164 numbers intended for other carriers
Solution Approach 1:
The patent segments the ENUM client functionality by deploying multiple ENUM clients across different domains (home carrier domain and visited carrier domain) rather than having a single ENUM client. This segmentation allows each domain to independently query and resolve E.164 numbers, ensuring that calls to other carriers can be properly routed without requiring complex inter-domain coordination.
Solution Approach 2:
The patent introduces an intermediary mechanism where the visited carrier's ENUM client acts as a mediator to resolve E.164 numbers for calls originating from home carriers. When a home carrier cannot resolve a number, the request is forwarded to the visited carrier's ENUM client, which then performs the resolution and returns the result, enabling successful call completion across carrier boundaries.
2Reliability
If carriers implement intercarrier ENUM-based routing with domain modification, then call routing reliability improves, but device complexity increases due to multiple domains and query redirection mechanisms
Solution Approach 1:
The patent implements a universal ENUM query mechanism where ENUM clients in both home and visited carrier domains can handle routing queries for any E.164 number regardless of the target carrier. This multi-functionality allows a single ENUM client implementation to serve multiple purposes: resolving numbers within the home carrier, resolving numbers for visited carriers, and cooperating with other carriers' ENUM clients, thereby reducing the need for carrier-specific customization.
Solution Approach 2:
The patent employs preliminary action by pre-configuring multiple domains with ENUM clients and establishing the intercarrier routing framework before actual calls are made. The domain modification mechanism and query redirection paths are set up in advance, allowing rapid call setup without real-time complexity. When a call is initiated, the pre-established routing rules automatically guide the query resolution process.
3Reliability
If multiple ENUM clients are deployed across domains, then E.164 number resolution reliability improves, but network latency increases due to additional query steps
Solution Approach 1:
The patent implements a feedback mechanism where ENUM clients monitor the success and failure of number resolution queries. When a query fails in the home carrier domain, the system automatically feeds back this information and redirects the query to the visited carrier domain's ENUM client. This feedback loop enables dynamic adaptation to routing conditions, ensuring reliable resolution while minimizing unnecessary query attempts that would increase latency.
Solution Approach 2:
The patent applies partial action by implementing ENUM clients in strategic locations (both home and visited carrier domains) rather than uniformly across all possible domains. This selective deployment achieves sufficient number resolution reliability for intercarrier calls without the excessive complexity and latency that would result from deploying ENUM clients in every possible domain. The query redirection mechanism activates only when needed, avoiding unnecessary processing steps.
Data Source
AI summary
Aspects of the subject disclosure may include, for example, a method and system to interconnect a first communications carrier to a second communications carrier by receiving a request to connect a communication from a first carrier to a second carrier; filtering the request to identify a specific name authority pointer (NPA-NXX) number from a plurality of specific name authority pointer (NPA-NXX) numbers; when the filter identifies the specific name authority pointer (NPA-NXX) number, modifying a private ENUM (tElephone NUmber Mapping) domain of the request to include an intercarrier ENUM apex based domain with a DNS (domain name server) recursion zone; retrieving a routing record using a domain name server (DNS) indicated by the intercarrier ENUM apex based domain; and routing the communication to the second carrier using the routing record. Other embodiments are disclosed.