Virtual Directory Server Pruned Filters Multi-Source Join
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing virtual directory servers face challenges in processing directory requests when information on an object is split across multiple data sources, as they struggle to accurately retrieve and combine attributes from disparate data sources while avoiding erroneous elimination of entries.
Innovation Solution
A virtual directory server processes directory requests by identifying relevant data sources, forming pruned filters for each source, and joining constituent responses to ensure accurate retrieval of split entries, using techniques such as standard, left outer, and full outer joins to form the final response.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If a virtual directory server retrieves attributes from multiple data sources, then the completeness of search results is improved, but the complexity of processing directory requests increases
Solution Approach 1:
The patent segments the directory request processing into distinct phases: identifying relevant data sources, forming pruned filters for each source, executing constituent requests, and joining responses. This segmentation allows the complex task of retrieving attributes from multiple data sources to be broken down into manageable steps, reducing processing complexity while maintaining search completeness.
Solution Approach 2:
The virtual directory server acts as an intermediary between client systems and multiple source data servers. It receives directory requests, translates them into constituent requests appropriate for each data source, collects responses, and formats final results. This intermediary role simplifies the overall system architecture by centralizing the coordination logic in the VDS while keeping source data servers simple.
2Measurement precision
If a virtual directory server forms pruned filters for each data source, then the accuracy of attribute retrieval is improved, but the time required to process requests increases
Solution Approach 1:
The system performs preliminary actions by pre-identifying which data sources store which attributes and pre-forming pruned filters before executing actual search requests. This setup work is done in advance so that when directory requests arrive, the VDS can directly execute optimized queries against the appropriate data sources without time-consuming on-the-fly filter generation, thus reducing request processing time while maintaining retrieval accuracy.
Solution Approach 2:
The patent applies local quality by tailoring the filter criteria to each specific data source's structure and capabilities. Instead of using a uniform filter approach, the system adapts the pruned filters to match each data source's attribute schema, ensuring accurate attribute retrieval optimized for each source's specific characteristics.
3Quantity of substance
If a virtual directory server joins constituent responses from multiple data sources, then the comprehensiveness of search results is improved, but the data retrieval overhead increases
Solution Approach 1:
The system extracts only the necessary attributes from each data source by forming pruned filters that target specific attributes stored at each source. This selective extraction prevents unnecessary data retrieval, reducing the overhead of collecting and processing responses while still achieving comprehensive search results through the joining of relevant attributes from multiple sources.
Data Source
AI summary
A virtual directory server (VDS) provided according to an aspect of the present disclosure maintains attribute data identifying a corresponding set of stored attributes associated with each data source, with each data source storing values for associated set of stored attributes. Upon receiving a first request based on query attributes, the VDS identifies a set of data sources based on the stored attribute data, with each data source storing values for at least one of the query attributes. The VDS then forms constituent requests, with each constituent request having a corresponding pruned filter suitable for the respective data source. The constituent requests are sent to the respective data sources. The VDS forms a final response from the constituent responses received from the corresponding data sources by joining the constituent entries, and sends the final response to a client system from which the first request is received.