Data Stability Management via Address Row Segmentation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional data recovery methods are inefficient in using memory resources and require multiple backup storage devices, making it difficult to effectively manage data stability across physically and logically divided storage units.

Innovation Solution

A data stability management apparatus that dynamically classifies address rows into protected and non-protected rows, using parity information stored in one storage unit to recover damaged data from another unit, thereby optimizing memory usage and simplifying data recovery processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional data backup methods store both protected data and non-protected data in storage devices, then data recovery is safeguarded, but memory efficiency deteriorates

Engineering Contradiction:

Improvedata recovery capabilityVSAvoidmemory efficiency

Core Design Contradiction:

ReliabilityVSQuantity of substance

Solution Approach 1:

The patent segments storage resources into protected address rows and non-protected address rows. Protected address rows store protected data and its relevance data, while non-protected address rows store non-protected data. This segmentation allows the system to protect only critical data without wasting memory resources on duplicating non-critical data, thereby improving memory efficiency while maintaining data recovery capability for important information.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent changes the parameter of data protection from an all-or-nothing approach to a selective approach based on data importance. By assigning different protection levels (protected vs. non-protected) to different data, the system optimizes memory usage by storing relevance data only for protected data, not for all data in the system.

Inventive Principle:

Principle #35Parameter changes

2Reliability

If distributed storage technology distributes data in a plurality of storage devices, then data recovery is safeguarded, but the number of backup storage devices required increases

Engineering Contradiction:

Improvedata recovery capabilityVSAvoidnumber of backup storage devices

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges multiple storage devices into a unified storage system with a single controller that manages protected and non-protected address rows across the devices. This merging allows the system to achieve data recovery capability with fewer storage devices compared to traditional distributed storage, as the controller can efficiently locate and retrieve protected data and its relevance data from the unified pool of storage resources.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The controller in the patent serves multiple functions: it manages both protected and non-protected address rows, handles data storage and recovery operations, and coordinates across multiple storage devices. This multi-functionality reduces the need for specialized backup devices, allowing the same storage devices to serve both primary storage and backup functions.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Reliability

If relevance data is stored in the same address row of another storage unit, then damaged data can be recovered, but storage configuration complexity increases

Engineering Contradiction:

Improvedata recovery capabilityVSAvoidstorage configuration

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

Instead of storing relevance data in separate backup locations or requiring complex cross-device mappings, the patent inverts the approach by storing relevance data in the same address row of a different storage unit. This inversion simplifies the recovery process, as the controller can retrieve protected data and its relevance data from the same address row location across storage units, reducing configuration complexity.

Inventive Principle:

Principle #13The other way round (Inversion)

4Quantity of substance

If address rows are classified into protected and non-protected rows, then memory usage is optimized, but management complexity increases

Engineering Contradiction:

Improvememory usage efficiencyVSAvoidaddress row management

Core Design Contradiction:

Quantity of substanceVSDevice complexity

Solution Approach 1:

The controller automatically manages the classification and assignment of address rows as protected or non-protected based on data characteristics and system requirements. This self-service capability eliminates the need for manual configuration of address row protection status, reducing management complexity while maintaining optimized memory usage efficiency.

Inventive Principle:

Principle #25Self-service

Data Source

PatentUS8356230B2Apparatus to manage data stability and methods of storing and recovering data

Publication Date: 2013.01.15 SAMSUNG ELECTRONICS CO LTD

AI summary

An apparatus to manage data stability, including a plurality of storage units and a control unit to determine when protected data is stored in a particular address row of at least one of the plurality of storage units, to select another storage unit of the plurality of storage units to store the protected data, and to store relevance data related to the protected data in the same address row of the selected storage unit. Methods of storing and recover data also included.