Hierarchical Data Browser with On-Demand Node Fetching

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for browsing large hierarchical data sets are inefficient, as they often require fetching and caching the entire dataset, leading to significant lag times when displaying nodes, especially when only a small portion is needed.

Innovation Solution

A system that fetches and displays a subset of nodes on demand, allowing users to scroll or access specific nodes without loading the entire hierarchy, while pre-fetching adjacent nodes for efficient display and caching related data to mimic local storage performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If the entire dataset is fetched and cached at the beginning of browsing, then the browsing speed is improved, but the memory usage increases significantly

Engineering Contradiction:
Improvebrowsing speedVSAvoidmemory usage
Core Design Contradiction:
SpeedVSQuantity of substance

Solution Approach 1:

The patent divides the large hierarchical dataset into smaller manageable segments or pages. Instead of loading the entire dataset at once, only the necessary segments are fetched and cached, allowing efficient browsing while minimizing memory consumption.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by pre-fetching and caching data segments that are likely to be needed soon based on browsing patterns, while avoiding loading the entire dataset. This allows fast access to frequently needed data without overwhelming memory resources.

Inventive Principle:
Principle #10Preliminary action

2Quantity of substance

If only a small portion of the dataset is accessed, then the memory usage is reduced, but the browsing speed deteriorates due to repeated data fetching

Engineering Contradiction:
Improvememory usageVSAvoidbrowsing speed
Core Design Contradiction:
Quantity of substanceVSSpeed

Solution Approach 1:

The system anticipates future browsing needs by pre-fetching data segments that are likely to be accessed next, caching them in advance. This eliminates repeated network fetching operations while maintaining low memory usage by only caching what is needed.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements a scrolling interface that allows users to skip through data segments rapidly. The system fetches and displays data in manageable chunks, enabling fast navigation through large datasets without loading everything into memory.

Inventive Principle:
Principle #21Skipping (Rushing through)

3Quantity of substance

If data is loaded only as the user scrolls down, then the memory usage is optimized, but the response time increases due to sequential loading

Engineering Contradiction:
Improvememory usageVSAvoidresponse time
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

Instead of waiting for user scrolling actions to trigger data loading, the system proactively pre-fetches data segments in advance based on predicted browsing patterns. This reduces the perceived response time while maintaining efficient memory usage.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system maintains continuous data fetching and caching operations in the background, ensuring that data is ready for display without interrupting the user experience. This creates a seamless browsing experience with minimal perceived latency.

Inventive Principle:
Principle #20Continuity of useful action

4Loss of information

If the entire hierarchy is displayed, then the completeness of information is improved, but the device complexity increases for managing large datasets

Engineering Contradiction:
Improveinformation completenessVSAvoidsystem complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent implements a virtual file system that segments the hierarchical dataset into manageable nodes and directories. The system manages these segments efficiently, providing access to the complete hierarchy while keeping the management complexity low through structured organization.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The virtual file system acts as an intermediary layer between the user interface and the underlying data storage. It abstracts the complexity of managing large hierarchical datasets, providing simple file operations while handling the complex tasks of data fetching, caching, and memory management in the background.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP3834099B9Ability to browse and randomly access a large hierarchy in near constant time in a stateless application
Publication Date: 2024.07.03 ORACLE INT CORP
  • EP3834099B9 patent drawingFigure 1A
  • EP3834099B9 patent drawingFigure 1B
  • EP3834099B9 patent drawingFigure 1C

AI summary

A browser is disclosed that provides for browsing a hierarchical dataset including potentially millions of nodes. The hierarchical dataset may be located on a machine that is remote to the machine hosting the browser. Through selective, intelligent fetching and local cache management of sparse portions of the hierarchical dataset, the browser provides consistent and predictable response times for displaying a randomly-selected node in the context of proximate nodes in the hierarchy.