Content Update System Using Hierarchical File Organization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing methods for updating digital content on personal computing devices are inefficient, particularly when multiple revisions are involved, as they often require downloading unnecessary data, as custom patches are designed for specific version pairs and become cumbersome with increasing versions.

Innovation Solution

A system and method that organizes content files in archives based on when they were last modified, allowing for linear searches to identify and download only the new or modified files between versions, thereby updating content efficiently by providing the differences rather than the entire content.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If custom patches are created for every pair of versions, then content can be updated efficiently between specific versions, but the system becomes inefficient and complex as the number of versions increases

Engineering Contradiction:
Improvecontent update efficiencyVSAvoidpatch management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent creates a universal patch structure where a single patch can serve multiple version pairs. Instead of creating unique patches for each version combination (v1-v2, v1-v3, v2-v3, etc.), the system uses a hierarchical patch design where patches can be applied across multiple version transitions. This reduces the number of patches needed from O(n²) to O(n), where n is the number of versions.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent segments the content update process into modular patches that can be independently managed and applied. Each patch represents a discrete set of changes that can be tracked and applied selectively. This segmentation allows the system to manage updates efficiently by only applying relevant patches rather than managing complex version-specific patch matrices.

Inventive Principle:
Principle #1Segmentation

2Reliability

If the entire content is downloaded for updates, then all changes are ensured, but unnecessary data is downloaded making the process time-consuming for minor changes

Engineering Contradiction:
Improvecontent update completenessVSAvoidupdate download time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts only the changed portions of content from the full content set and packages them as targeted patches. Instead of downloading the entire content archive for updates, the system identifies and extracts only the specific files or sections that have changed between versions. This extraction approach ensures that users receive exactly what they need (maintaining reliability) while minimizing download time and bandwidth usage.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies partial action by downloading and applying only the necessary subset of content changes rather than the full content set. The system determines the minimal set of patches required to achieve the desired version update and applies only those, avoiding the excessive action of downloading entire content archives when minor changes are sufficient.

Inventive Principle:
Principle #16Partial or excessive action

3Quantity of substance

If custom patches are used for specific version pairs, then data transfer is minimized, but unnecessary data is still downloaded when updating across multiple revisions

Engineering Contradiction:
Improvedata transfer volumeVSAvoidupdate process time
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

The patent performs preliminary actions by organizing content into a hierarchical structure with a table of contents and predefined sections before updates are needed. This preliminary organization allows the system to quickly identify which patches are needed and what data must be transferred, avoiding the need to analyze and transfer unnecessary data during the actual update process. The hierarchical structure is prepared in advance to enable efficient patch application across multiple versions.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8370341B1Systems and methods for determining and facilitating content updates for a user device
Publication Date: 2013.02.05 INKLING SYST
  • US8370341B1 patent drawing
  • US8370341B1 patent drawing
  • US8370341B1 patent drawing

AI summary

A system, computer-readable storage medium storing at least one program, and a computer-implemented method for updating content are presented. A first version of content residing on a user device is determined, and a second version of content relating to the first version of content is determined. Version information for each file within a second set of files organized within a second archive of the second version of content is sequentially accessed based on a second order of the second set of files in the second archive, the version information indicating a version of each file. A determination is made of when version information indicating a newer version of content has been accessed from the second archive, and new content associated with the newer version is provided to the user device.