Static Index Segmentation for Archived Catalog Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Electronic catalog systems face performance issues and increased storage needs due to dynamic indexing, which complicates access to historical updates stored in archive data stores, affecting throughput and requiring larger storage spaces.

Innovation Solution

A system that organizes updates into objects with pointers and keys, allowing for efficient static indexing of archived data, enabling quick access to updates in both live and archive data stores without affecting performance, and includes a dynamic index purging mechanism to manage storage size.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If dynamic indexing is performed on the live data store to facilitate access to updates, then access to updates is improved, but throughput and performance of the electronic catalog system deteriorate

Engineering Contradiction:
Improveaccess to updatesVSAvoidthroughput and performance
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent segments the indexing function into two parts: a static index created offline from archived updates, and a dynamic index for recent updates in the live data store. This segmentation allows the bulk of indexing work to be performed offline, reducing the performance impact on the live system while still enabling efficient access to both historical and recent updates.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary indexing by creating a static index from archived updates before they are needed for queries. This preliminary action eliminates the need to perform dynamic indexing on historical data during system operation, thereby improving throughput and performance while maintaining ease of access to updates.

Inventive Principle:
Principle #10Preliminary action

2Ease of operation

If dynamic indexing is performed on the live data store to facilitate access to updates, then access to updates is improved, but storage space requirements increase

Engineering Contradiction:
Improveaccess to updatesVSAvoidstorage space
Core Design Contradiction:
Ease of operationVSQuantity of substance

Solution Approach 1:

The patent extracts historical update data from the live data store and places it in an archived data store. A static index is then created for the archived data, separating it from the dynamic index needed for live data. This extraction reduces the storage requirements for the dynamic index in the live system while maintaining access capability to historical updates.

Inventive Principle:
Principle #2Taking out (Extraction)

3Ease of manufacture

If updates are archived in an archived data store, then management of large quantities of updates is improved, but access to historical updates becomes more complex

Engineering Contradiction:
Improvemanagement of updatesVSAvoidaccess to historical updates
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The patent introduces a static index as an intermediary between the archived data store and query operations. This static index simplifies access to historical updates by providing a pre-organized structure that can be queried efficiently without directly navigating the archived data store, thereby reducing access complexity while maintaining improved update management.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9846697B2Indexing data updates associated with an electronic catalog system
Publication Date: 2017.12.19 AMAZON TECH INC
  • US9846697B2 patent drawing
  • US9846697B2 patent drawing
  • US9846697B2 patent drawing

AI summary

Systems and methods are provided for efficiently indexing archived objects in an archive data store to allow for efficient and quick access to the archived objects. The systems and methods provided also allow alleviate the strain on a live data store and enable a requester wishing to retrieve updates to do so without knowledge of the location of the stored update on a live or archive data store.