Numeric DNS Grouping for Telephone Number Storage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current domain name system (DNS) technologies face inefficiencies in storing and accessing telephone numbers, leading to significant storage requirements and latency issues due to the use of alphanumeric representations and overhead data, which hinder the performance of voice-over-internet-protocol (VoIP) communications.
Innovation Solution
The proposed solution involves storing telephone numbers as numeric values, grouping multiple telephone numbers within a single database record, and compressing DNS data to reduce storage space and improve access times, using a DNS database with primary and secondary keys for efficient querying and data retrieval.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If telephone numbers are stored as alphanumeric DNS labels, then each digit can be individually searched and maintained conforming to DNS label standards, but storage space increases significantly (2 bytes per digit plus overhead)
Solution Approach 1:
The patent changes the parameter of telephone number representation from alphanumeric characters to numeric values. Each telephone number is stored as a sequence of numeric digits rather than alphabetic characters, reducing storage from 2 bytes per digit to 1 byte per digit. This parameter change maintains search capability while halving the storage requirement for the actual number data.
Solution Approach 2:
The patent merges multiple telephone numbers into a single DNS database record by grouping them under a common parent domain. Instead of creating separate DNS records for each telephone number (which would each require overhead data and NAPTR records), multiple numbers are consolidated into one record structure, eliminating redundant overhead and reducing total storage space.
2Reliability
If each telephone number is stored in a separate DNS record with overhead data and NAPTR records, then complete DNS functionality is maintained, but storage requirements reach 150 bytes per record
Solution Approach 1:
The patent combines multiple telephone number records into a single DNS database record structure. Instead of having separate records for each telephone number (each requiring ~150 bytes including overhead and NAPTR data), multiple numbers are grouped under a common parent domain within one record, reducing storage requirements by eliminating redundant overhead data for each individual number.
Solution Approach 2:
The patent creates a universal parent domain structure that can accommodate multiple telephone numbers with different formats (E.164, national, extension formats). This multi-functional approach allows a single DNS record to serve multiple telephone numbers across different formats and countries, maintaining full DNS functionality while reducing overall storage needs.
3Quantity of substance
If telephone numbers are stored in hard drive database, then storage capacity is sufficient for 200 million numbers, but access time increases significantly compared to local memory
Solution Approach 1:
The patent segments the telephone number database into hierarchical components: parent domains, sub-domains representing number segments, and individual number records. This segmentation allows the database to be organized in a way that fits into local memory caches, reducing access time by enabling faster retrieval of commonly accessed portions of the database while maintaining sufficient total storage capacity.
Solution Approach 2:
The patent introduces a hierarchical dimensional structure to the database organization, using domain name hierarchy (parent domains, sub-domains, labels) as an additional organizational dimension. This multi-dimensional organization allows efficient indexing and retrieval operations that reduce access time while maintaining the ability to store large volumes of telephone number data.
4Adaptability or versatility
If DNS labels are treated as case insensitive alphanumeric, then conformity with DNS standards is maintained, but search operations become more complex and slower
Solution Approach 1:
The patent changes the parameter of data representation from alphabetic DNS labels to numeric telephone number digits. This parameter change enables direct numeric comparison and search operations, which are faster than alphabetic string matching. The numeric representation maintains DNS standard conformity through proper domain name structure while significantly improving search speed through efficient numeric algorithms.
Data Source
AI summary
Systems and methods of storing DNS data associated with a telephone number are presented. These systems and methods can reduce storage space needs, increase access speed and/or result in other benefits, in comparison with the prior art. In some embodiments, DNS data is indexed using a numerical representation of a telephone number rather than an alphanumeric representation. In some embodiments, DNS data associated with several different telephone numbers are grouped together within a single DNS data record and indexed using a secondary key. In some embodiments, DNS data is compressed.