On-demand Package Data Access via Sparse File Indexing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Users have to wait for entire ZIP or WIM files to download before accessing their contents, even if they only need a single file, which can be time-consuming due to large file sizes.

Innovation Solution

Implementing a system that allows transparent random access to package contents by using metadata to identify and retrieve specific parts of the package, with components like filter drivers, package handlers, and transport handlers to manage requests and data transfer, enabling just-in-time copying of remote resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the entire package is downloaded before accessing contents, then the package can be fully accessed, but the wait time increases significantly

Engineering Contradiction:
Improvepackage accessibilityVSAvoiddownload wait time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The package is divided into individual files or portions that can be accessed independently. Instead of downloading the entire package at once, the system segments the package into discrete units (files, folders, or data blocks) that can be retrieved on-demand based on user requests, thereby reducing overall download time while maintaining full accessibility.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system creates a local index or metadata structure of the package contents before actual data retrieval. This preliminary action allows the system to know what files are available and their locations without downloading the actual data, enabling fast random access to specific files while minimizing the amount of data that needs to be downloaded.

Inventive Principle:
Principle #10Preliminary action

2Quantity of substance

If the entire package is downloaded, then all contents are available locally, but network traffic increases unnecessarily

Engineering Contradiction:
Improveavailable dataVSAvoidnetwork traffic
Core Design Contradiction:
Quantity of substanceVSLoss of energy

Solution Approach 1:

The system extracts only the necessary metadata or table of contents information from the package to enable indexing and navigation. This extracted metadata allows users to access specific files without transferring the entire package, significantly reducing network traffic while still providing full access to all package contents through the index.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

An intermediary indexing structure or cache is introduced between the remote package and the user's local system. This intermediary stores package metadata and enables the system to serve file requests by retrieving only the specific portions needed, rather than transferring the complete package, thus reducing network traffic while maintaining data availability.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Speed

If random access to package contents is enabled, then file access speed improves, but system complexity increases

Engineering Contradiction:
Improvefile access speedVSAvoidsystem structure
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The system creates a local copy or index of the package's metadata and directory structure without copying the actual file contents. This copied index structure enables fast random access to file information and facilitates on-demand retrieval of specific files, achieving high access speeds while keeping the stored data volume minimal and the system relatively simple.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS8910149B2On-demand or incremental remote data copy
Publication Date: 2014.12.09 ZHIGU HLDG
  • US8910149B2 patent drawing
  • US8910149B2 patent drawing
  • US8910149B2 patent drawing

AI summary

Files, or other data, may be stored in a package, and the contents of the package may be retrieved incrementally and/or on-demand. In one example, files are packaged into a ZIP file or similar type of package. Additionally, metadata is added to the package that describes the contents of the package at the sub-file level, thereby allowing portions of files to be retrieved by appropriately-configured software. When the package is to be used on a local machine, placeholder files may be created on that machine, which are to be populated by the package's contents at a later time. When a request for data in the package is made, if the data does not reside locally, then a request for the specific data (possibly at the sub-file level) is made, and the placeholder files are populated with the actual package data.