ENUM Database Referral Domain for Ported Number Resolution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current telecommunications networks face challenges in identifying the destination domain for a telephone number, especially when the number has been ported, leading to difficulties in establishing direct connections and requiring complex ad-hoc mechanisms, which are costly and inefficient.
Innovation Solution
An ENUM database using CNAME or DNAME records to redirect DNS requests and provide a referral domain for ported telephone numbers, allowing for the association of the number with its current domain without altering DNS logic or requiring common naming conventions between operators.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional ENUM databases are used to resolve telephone numbers, then direct connection establishment is enabled, but the system becomes complex and requires ad-hoc mechanisms for ported numbers
Solution Approach 1:
The patent introduces a referral domain as an intermediary element between the calling domain and the destination domain. When a telephone number is ported, the ENUM database stores a referral domain instead of directly storing the destination domain. This referral domain acts as a mediator that redirects the resolution process to the correct destination domain, simplifying the overall system architecture while maintaining reliable connection establishment.
2Measurement precision
If ad-hoc mechanisms are implemented for ported numbers, then resolution accuracy is improved, but operational cost increases
Solution Approach 1:
The patent makes the ENUM database universal by enabling it to handle both traditional number resolution and ported number resolution through a single mechanism. The referral domain approach allows the same ENUM database structure to serve multiple purposes: resolving numbers that have not been ported and resolving numbers that have been ported, eliminating the need for separate ad-hoc mechanisms and reducing operational costs.
3Adaptability or versatility
If DNS logic is altered to handle ported numbers, then resolution capability is improved, but system stability deteriorates
Solution Approach 1:
The patent segments the DNS resolution process into distinct phases: the ENUM database stores referral domain information, and the actual destination domain resolution occurs in a subsequent phase. This segmentation allows the system to handle ported numbers without altering the core DNS logic, as the referral domain mechanism operates transparently within the existing DNS framework, maintaining stability while improving adaptability.
4Adaptability or versatility
If common naming conventions are required between operators, then interoperability is improved, but system flexibility deteriorates
Solution Approach 1:
The referral domain serves as a universal intermediary that translates between different operator-specific naming conventions. Each operator can maintain their own naming conventions for storing referral domain information in their ENUM databases, while the referral mechanism itself provides a standardized approach to resolution. This eliminates the need for operators to adopt common naming conventions while ensuring interoperability.
Data Source
AI summary
A method of resolving by an original network/domain of a telephone number of a called party, belonging to a recipient network/domain. The method includes: a) a calling party, belonging to the original domain dispatches a message using the telephone number of the called party as routing identifier; b) a server of the original domain in charge of routing the message, or a DNS server, produces an interrogation key dependent on the telephone number and on a penultimate domain name; c) a DNS request is sent to a DNS server associated with the penultimate domain; d) the DNS server associated with the penultimate domain performs, by using the interrogation key, a search in a database ENUM associated therewith; e) the search provides at least one record containing a return network/domain including the recipient domain; and f) a DNS request is sent to the return domain.


