Virtual RDAP Service for Domain Data Aggregation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current RDAP systems face challenges in providing comprehensive domain-related information due to the lack of mandated registrar WHOIS output, leading to difficulties in parsing WHOIS information, especially with thin registries that do not transfer contact information during domain transfers.
Innovation Solution
The implementation of a virtual RDAP (VRDAP) service that identifies and queries other RDAP services to retrieve necessary data, offering thick RDAP capabilities transparently to clients, and providing consolidated responses, thereby alleviating the need for local data storage and compliance with international PII legal requirements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If thin registries are used to reduce operational complexity and costs, then device complexity is reduced, but the ability to provide comprehensive domain-related information deteriorates
Solution Approach 1:
The patent combines thin registry functionality with virtual thick service capabilities by integrating multiple RDAP services (registry RDAP service, registrar information RDAP service, registrar RDAP service) into a unified virtual thick RDAP service. This allows the system to aggregate comprehensive domain information from multiple sources while maintaining the operational simplicity of thin registries.
Solution Approach 2:
The virtual thick RDAP service acts as an intermediary between clients and multiple underlying RDAP services. It receives queries from clients, identifies relevant thick services based on thin data, queries those services for comprehensive information, and consolidates responses into unified answers, thereby bridging the information gap created by thin registry architecture.
2Reliability
If comprehensive domain information is stored locally to ensure data availability, then reliability is improved, but device complexity and storage requirements increase
Solution Approach 1:
The patent extracts the data storage function from the local client and relocates it to external RDAP services. Instead of storing comprehensive domain information locally, the client only stores thin data locally and extracts comprehensive information on-demand by querying external thick services, thereby eliminating the need for large local storage systems while maintaining data availability.
Solution Approach 2:
The system creates virtual copies of thick services through the virtual thick RDAP service that aggregates data from multiple real RDAP services. This allows the client to access comprehensive domain information without maintaining actual copies of large datasets locally, achieving data availability through virtual aggregation rather than physical storage.
3Loss of information
If multiple RDAP services are queried to provide comprehensive information, then information completeness is improved, but processing time and connectivity requirements increase
Solution Approach 1:
The virtual thick RDAP service performs preliminary actions by identifying which thick services need to be queried based on the incoming query and the client's thin data before actually executing the queries. This pre-processing step optimizes the query routing and can consolidate multiple queries into more efficient requests, reducing overall processing time while maintaining information completeness.
Data Source
AI summary
Provided is a method for providing a response to a user query for domain-related information of a domain. The method can include obtaining, at a client over a network, the user query for the domain-related information, and identifying one or more thick services based on thin data for the domain. The method can also include providing, by the client, the user query to the identified one or more thick services and obtaining a first answer to the user query from the one or more thick services. Furthermore, the method can include providing a second answer to a user based on the first answer.