AONT Chunk Encoding With Random Offsets for Dispersed Storage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing dispersed storage networks face challenges in ensuring data integrity and availability across multiple storage units, particularly in scenarios where a significant number of storage units fail, and require robust error correction mechanisms to prevent data loss without relying on redundant copies.

Innovation Solution

The implementation of a dispersed storage network (DSN) that uses error encoding techniques, such as Cauchy Reed-Solomon encoding, to distribute data across multiple storage units, allowing for the reconstruction of data segments even if a threshold number of units fail, and includes a managing unit for vault creation, security, and billing, as well as an integrity processing unit for rebuilding 'bad' or missing encoded data slices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If data is distributed across multiple storage units without redundant copies, then storage efficiency is improved, but data integrity and availability deteriorate when storage units fail

Engineering Contradiction:
Improvestorage efficiencyVSAvoiddata integrity
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The patent segments data into multiple data segments and further divides each segment into multiple slices, distributing them across different storage units. This segmentation allows the system to store more data efficiently while maintaining the ability to reconstruct data even if some storage units fail, as long as the number of failed units does not exceed the error correction capability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent employs error correction codes (such as Reed-Solomon or Cauchy Reed-Solomon coding) that transform the data representation parameters. By encoding data with redundant information in a controlled manner, the system achieves both storage efficiency and data integrity, allowing reconstruction from a subset of stored slices.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If error correction mechanisms are implemented to prevent data loss, then data integrity is improved, but system complexity increases

Engineering Contradiction:
Improvedata integrityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates encoded copies of data segments through error correction coding. Instead of storing simple redundant copies, it generates multiple encoded versions where any sufficient subset can reconstruct the original data. This approach maintains data integrity while managing complexity through standardized encoding algorithms.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The error correction mechanism serves multiple functions simultaneously: it provides data integrity protection, enables recovery from various failure scenarios, and allows flexible data retrieval. The same encoded slices serve both as storage units and as error correction components, reducing overall system complexity.

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

3Reliability

If robust error correction is used to handle significant storage unit failures, then reliability is improved, but storage capacity is reduced

Engineering Contradiction:
Improvefault toleranceVSAvoidstorage capacity
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent implements error correction with a specific redundancy level that provides sufficient fault tolerance for the required reliability target. Rather than over-correcting, the system uses the minimum necessary redundancy to handle the expected failure rate, optimizing the balance between reliability and storage capacity.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system allows dynamic adjustment of error correction parameters (such as the number of parity slices or correction code strength) based on the desired reliability level and available storage resources. This enables optimization of storage capacity while maintaining the required fault tolerance for significant storage unit failures.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10757187B2Streaming all-or-nothing encoding with random offset support
Publication Date: 2020.08.25 PURE STORAGE INC
  • US10757187B2 patent drawing
  • US10757187B2 patent drawing
  • US10757187B2 patent drawing

AI summary

A method comprises dividing a data segment of a data object into a plurality of data chunks. The method continues with all-or-nothing (AONT) encoding each data chunk of the plurality of data chunks to produce a plurality of sets of AONT encoded data pieces. Note a set of AONT encoded data pieces includes T number of AONT encoded data pieces. The method continues by splitting and rearranging the plurality of sets of AONT encoded data pieces to produce the T number of sets of AONT encoded data pieces. The method continues by dispersed storage error encoding the T number of sets of AONT encoded data pieces to produce a set of encoded data slices, which include the T number+an R number of encoded data slices.