Unified Data Request Processing System for Domain Name Resolution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems fail to integrate resource location, registration, and search services effectively across multiple naming systems, leading to separate and inefficient processes for valid and fictitious domain names, and lack integration with other request types such as search and registration requests.
Innovation Solution
A method and apparatus that automatically select response types for data requests, integrating processing of fictitious and valid domain names, multilingual names, and keywords with prefixes, spelling, and input history, generating hyperlinks for available domain names, and providing error messages for invalid inputs, while enabling simultaneous registration across multiple naming systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If separate processing systems are used for valid and fictitious domain names, then each system can be optimized for its specific function, but the overall system complexity increases and integration between services becomes difficult
Solution Approach 1:
The patent combines separate processing systems for valid and fictitious domain names into a unified data request processing system. The method receives data requests containing identifiers and request types, then processes them through a single integrated apparatus that automatically selects appropriate response types based on the identifier validity and request type, eliminating the need for separate processing paths while maintaining functional optimization.
Solution Approach 2:
The processing apparatus is designed to handle multiple types of data requests (resolution requests, registration requests, search requests) through a single universal system. The apparatus automatically determines identifier validity and selects appropriate response types based on the combination of identifier and request type, making the system multi-functional rather than requiring specialized separate systems.
2Reliability
If multiple separate services are used for resource location, registration, and search, then each service can be specialized, but the user experience deteriorates due to fragmented results and increased bandwidth consumption
Solution Approach 1:
The patent merges resource location, registration, and search services into a single integrated data request processing method. The system receives a data request with an identifier and request type, processes them together through the same apparatus, and returns unified results. This consolidation provides specialized processing for each service type while delivering integrated results to users, reducing bandwidth consumption by avoiding duplicate identifier validation across separate services.
3Measurement precision
If manual selection of response types is required for data requests, then processing accuracy can be maintained, but processing speed and automation level decrease
Solution Approach 1:
The processing apparatus performs automatic self-determination of identifier validity and automatic selection of response types without manual intervention. The system autonomously analyzes the identifier, determines whether it is valid or fictitious, considers the request type, and selects the appropriate response type automatically. This self-service automation maintains processing accuracy through systematic decision logic while dramatically improving processing speed and eliminating manual selection bottlenecks.
4Stability of the object's composition
If centralized WHOIS cache storage is used, then data consistency is maintained, but bandwidth consumption increases and lookup performance decreases
Solution Approach 1:
The patent segments the centralized WHOIS cache into distributed caches across multiple naming systems. Each naming system maintains its own cache of identifier data, eliminating the need for all systems to continuously synchronize with a central cache. This segmentation reduces bandwidth consumption by eliminating redundant data transmission while maintaining data consistency within each naming system, and improves lookup performance by allowing local cache access without centralized coordination overhead.
Data Source
AI summary
When a one or more identifiers and a plurality of data request types is received, a first data request from the one or more identifiers and from a first data request type can be generated and performed. When at least one first result from the first data request can be received, a second data request from the one or more identifiers and from a second data request type can be generated and performed at any time after receiving the one or more identifiers and the plurality of data request types, and then the at least one second result from the second data request can be retrieved either one of a before, during, and after the at least one first result from the first data request is presented. The correspondence between identifiers and request types may be one-to-one, one-to-many, many-to-one, or many-to-many relationship. A response type may employ a plurality of response methods to access multiple network resources corresponding to any generated and/or selected identifiers and/or request types.