Multi-tiered Caches for Seamless Mobile Data Scrolling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Mobile devices face challenges in displaying large data reports due to screen size limitations, requiring users to browse through data page by page, which is inefficient and resource-intensive, and conventional technologies do not allow seamless scrolling or efficient bandwidth utilization.
Innovation Solution
Implementing multi-tiered caches that render and store data in segments, allowing seamless scrolling by using a first tier cache for the currently displayed data and a second tier cache for data fields that straddle sections, reducing the need to regenerate data and minimizing bandwidth usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If data is retrieved and displayed page by page using conventional technologies, then memory usage is reduced, but scrolling smoothness and user experience deteriorate
Solution Approach 1:
The patent divides the data display into multiple tiers: first tier caches contain display buffers for currently visible data sections, while second tier caches store rendered data fields that straddle section boundaries. This segmentation allows seamless scrolling within each buffer while managing memory efficiently by only loading necessary data segments.
Solution Approach 2:
The system performs preliminary rendering of data fields that may straddle section boundaries before actual scrolling occurs. By pre-rendering these boundary data fields and storing them in second tier caches, the system ensures smooth transitions occur automatically without requiring full page reloads, thus maintaining scrolling smoothness while controlling memory usage.
2Ease of operation
If the entire data report is formatted and stored in memory, then scrolling smoothness is improved, but computing resources and memory consumption worsen
Solution Approach 1:
The patent segments the data formatting process by maintaining first tier caches with display buffers for specific data sections and second tier caches for rendered data fields. This allows the system to format and store only the necessary portions of data in memory rather than the entire report, reducing computing resource consumption while maintaining scrolling smoothness through efficient cache management.
Solution Approach 2:
The system applies different caching strategies to different parts of the data: first tier caches hold display buffers for currently visible sections, while second tier caches store pre-rendered data fields that straddle boundaries. This local differentiation optimizes memory usage by storing detailed rendered data only where needed for smooth transitions, rather than uniformly caching all data.
3Loss of energy
If data is retrieved in segments from remote data store, then bandwidth utilization is improved, but data continuity and scrolling smoothness worsen
Solution Approach 1:
The system performs preliminary retrieval and rendering of data fields that straddle section boundaries, storing them in second tier caches before actual scrolling occurs. This preliminary action ensures that when users scroll through segmented data, transitions between sections are smooth and continuous, eliminating gaps that would otherwise occur with simple segmented data retrieval.
Solution Approach 2:
The patent introduces second tier caches as an intermediary layer between the segmented data retrieval from remote stores and the display buffers in first tier caches. This intermediary stores pre-rendered data fields that bridge section boundaries, ensuring data continuity and scrolling smoothness while allowing the system to retrieve data in efficient segments from remote data stores.
Data Source
AI summary
Methods, program products, and systems for rendering data using multi-tiered caches are described. A system can render a first section of data and store the rendered first section of data in a first tier cache. The system can determine that a data field, when rendered, straddles the rendering of the first section of data and a rendering of a second section of data. The system can generate a rendering of the data field and store the rendering of the data field in a second tier cache. When rendering the second section of data, the system can use the rendered data field stored in the second tier cache instead of regenerating the rendering of the data field.