Segmented Data Storage Reducing Read Latency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data storage systems in memory devices face challenges in efficiently managing user data and redundancy information, leading to increased latency and computational complexity, particularly when error correction is required, due to the separate handling of data and redundancy bits.

Innovation Solution

The system segregates data storage into two distinct areas: one for user data and another for redundancy information, using separate access commands and storage media to optimize storage efficiency and reduce latency by only accessing redundancy data when necessary.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If data and redundancy information are stored together in the same storage area, then storage space utilization is improved, but read latency increases because redundancy data must be accessed even when not needed

Engineering Contradiction:
Improvestorage space utilizationVSAvoidread latency
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

The patent divides the storage system into two separate storage areas: a first storage area for user data and a second storage area for redundancy information. This segmentation allows independent access to each area, enabling the system to retrieve user data without unnecessarily accessing redundancy data, thereby reducing read latency while maintaining efficient storage space utilization.

Inventive Principle:
Principle #1Segmentation

2Reliability

If redundancy information is always accessed and processed during data retrieval, then data reliability is improved, but computational complexity increases

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

Solution Approach 1:

The patent implements a selective redundancy access mechanism where the system evaluates whether redundancy information is actually needed before accessing it. The controller determines if the user data can be reliably retrieved without redundancy processing, and only accesses the second storage area when necessary. This partial action approach maintains data reliability while significantly reducing computational complexity during normal read operations.

Inventive Principle:
Principle #16Partial or excessive action

3Loss of time

If separate storage areas for data and redundancy information are used, then read latency is reduced, but device structure complexity increases

Engineering Contradiction:
Improveread latencyVSAvoiddevice structure complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The patent employs a universal controller that manages both the first storage area for user data and the second storage area for redundancy information through a unified interface and control logic. This multi-functional controller handles data writing, reading, and redundancy management across both storage areas, reducing the need for separate dedicated hardware components and thereby minimizing the increase in device structure complexity while still achieving reduced read latency.

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

Data Source

PatentUS8949684B1Segmented data storage
Publication Date: 2015.02.03 APPLE INC
  • US8949684B1 patent drawing
  • US8949684B1 patent drawing
  • US8949684B1 patent drawing

AI summary

A method for data storage includes assigning in a memory that includes one or more storage devices a first storage area for storage of user data, and a second storage area, which is separate from the first storage area, for storage of redundancy information related to the user data. Input data is processed to produce redundancy data, and the input data is stored in the first storage area using at least one first write command. The redundancy data is stored in the second storage area using at least one second write command, separate from the first write command.