ENUM Record Management via Broker-Based Zone Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Domain Name Servers (DNS) systems, such as those using the Berkeley's Internet Name Domain (BIND) protocol, are not scalable and often malfunction when processing more than 10 million ENUM records, necessitating a method and apparatus for efficient ENUM record management in communication systems.
Innovation Solution
A method and apparatus that utilize a broker element to detect and compare Resource Records (RRs) submitted by an IP Multimedia Subsystem (IMS), updating a volatile memory of a Domain Name Server (DNS) responsible for processing ENUM records, stored in an object-oriented data storage format, allowing for efficient management and scalability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If traditional DNS systems (BIND protocol) are used to manage ENUM records, then the system structure is simple and easy to implement, but the system cannot handle more than 10 million records and malfunctions
Solution Approach 1:
The patent divides the ENUM record management system into multiple DNS servers, each handling a specific zone or portion of the ENUM database. This segmentation allows the system to distribute the load across multiple servers, enabling it to handle tens of millions of records without a single point of failure or bottleneck, thus resolving the limitation of traditional single-server BIND systems.
Solution Approach 2:
The patent introduces a hierarchical dimension to ENUM record management by implementing a zone-based structure with master and slave DNS servers. This dimensional organization transforms the flat, single-level BIND system into a multi-layered architecture that can scale horizontally across multiple servers while maintaining manageable complexity through zone delegation.
2Adaptability or versatility
If traditional DNS systems are used, then the implementation is straightforward, but the system lacks scalability for large carriers
Solution Approach 1:
By segmenting the ENUM database into zones and assigning them to different DNS servers, the system achieves scalability without requiring a complete architectural overhaul. Each zone can be independently managed and scaled, allowing the system to adapt to growing carrier requirements while maintaining a familiar DNS-based structure.
Solution Approach 2:
The patent maintains compatibility with existing DNS protocols and standards while extending functionality to handle large-scale ENUM records. The system uses standard DNS query and update mechanisms, allowing it to serve multiple functions: traditional DNS resolution, ENUM record management, and scalable database distribution, thereby achieving versatility without proportionally increasing complexity.
3Speed
If ENUM records are stored in volatile memory of DNS, then access speed is fast, but data loss occurs if the system crashes
Solution Approach 1:
The patent implements local quality by having each DNS server maintain a local volatile memory cache for fast access to frequently queried ENUM records in its zone, while simultaneously relying on the master server's persistent storage for data safety. This localized optimization provides fast access where needed while the distributed architecture ensures data persistence through replication across multiple servers with different storage characteristics.
Solution Approach 2:
The system implements beforehand cushioning by maintaining replicated copies of ENUM records across multiple DNS servers (master and slaves) before any potential data loss scenario. This redundancy ensures that if one server experiences a crash or data loss, other servers with cached copies can immediately serve the requests, cushioning against the impact of volatility.
4Quantity of substance
If a large number of DNS servers are deployed to handle millions of ENUM records, then the system can scale, but hardware and software resource usage becomes inefficient
Solution Approach 1:
The patent merges the functions of multiple DNS servers into a coordinated zone-based architecture where each server handles a specific portion of the ENUM database. This combining approach allows the system to scale to millions of records by distributing work across servers rather than requiring one massive server, improving resource efficiency through load distribution while maintaining the ability to handle large quantities of ENUM records.
Data Source
AI summary
A method and apparatus for managing ENUM records is disclosed. An apparatus that incorporates teachings of the present disclosure may include, for example, a broker having a detection element that detects a Resource Record (RR) submission made by an IP Multimedia Subsystem (IMS), and a comparison element that retrieves from an object-oriented data storage element a zone associated with the RR, identifies a Domain Name Server (DNS) responsible for processing said zone, compares the zone with a volatile memory of the DNS, and updates the volatile memory according to one or more differences detected. Additional embodiments are disclosed.