Hierarchical Data Pre-fetching for Web Interface Efficiency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for accessing database servers via web interfaces are inefficient on slow network connections, either requiring excessive data downloads or burdening network performance with frequent requests, and often waste resources by caching unnecessary data.
Innovation Solution
A method and apparatus that pre-fetch and cache hierarchical data from remote sources based on user access authority, allowing for efficient data retrieval by requesting only the necessary data layers and levels, reducing waiting times and resource waste by maintaining a cached data structure one step ahead of user interactions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If entire data is downloaded immediately based on user access authority, then data availability is improved, but network bandwidth consumption increases and user experience deteriorates on slow connections
Solution Approach 1:
The patent segments data into hierarchical levels (first level data, second level data, etc.) and downloads only the current level and necessary lower levels, rather than downloading all data at once. This segmentation allows the system to maintain data availability for current operations while reducing overall bandwidth consumption by excluding unnecessary higher-level data.
Solution Approach 2:
The system performs preliminary action by downloading and caching data for the current level and lower levels before the user actually needs to access them. The data is pre-fetched based on predicted user behavior and access patterns, so when the user navigates to a page, the data is already available in the cache, improving response time without requiring full data downloads.
2Loss of energy
If data is downloaded only after user specifically requests it, then network bandwidth consumption is reduced, but user waiting time increases
Solution Approach 1:
The system performs preliminary action by pre-downloading and caching data for the current level and lower levels before the user actually needs to access them. The data is pre-fetched based on predicted user behavior and access patterns, so when the user navigates to a page, the data is already available in the cache, eliminating waiting time without significant bandwidth cost.
Solution Approach 2:
The system uses feedback mechanisms to monitor user navigation patterns and adjust the pre-fetching strategy. By analyzing user behavior feedback, the system optimizes which data to pre-download, ensuring that the most likely needed data is cached while avoiding unnecessary downloads, thus balancing waiting time reduction with bandwidth conservation.
3Productivity
If data is cached to improve reading speed, then data retrieval efficiency is improved, but unnecessary data requests and resource waste increase
Solution Approach 1:
The patent segments data into hierarchical levels and implements selective caching at each level. The system caches only the current level data and necessary lower levels in the local cache memory, rather than caching all data. This segmentation allows fast retrieval for current operations while avoiding resource waste from caching irrelevant higher-level data that users never access.
Solution Approach 2:
The system applies local quality by implementing different caching strategies for different data levels. The cache stores data selectively based on local access patterns and usage probability at each hierarchical level, rather than uniformly caching everything. This ensures high retrieval efficiency for actively used data while minimizing resource waste from storing and managing unnecessary data across the entire hierarchy.
Data Source
AI summary
Method and device of presenting data stored at remote source are disclosed. The method includes: receiving first webpage data that is configured to be rendered as a first webpage, the first webpage, when rendered, provides one or more access links each directed to respective second webpage data that is stored at a respective remote source; from the first webpage data, recognizing respective reference data for each of the respective second webpage data; in accordance with the respective reference data, requesting the respective second webpage data from its respective remote source; receiving and storing at least one of the respective second webpage data before detecting the user's selection of the access link; and upon detecting the user's selection of the access link, rendering the stored at least one of the respective second webpage data as a second webpage.