Storage Device Hardware-Life Estimation With Workload Balancing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing storage systems face inefficiencies in managing and optimizing the life and performance of storage devices, particularly in flash-based storage systems, due to unnecessary write operations and lack of centralized control over device management, leading to reduced reliability and increased wear.

Innovation Solution

Implementing a direct-mapped flash storage system where higher-level processes manage data block operations without address translation by storage controllers, utilizing zones and allocation units to optimize wear leveling and reduce redundant writes, and incorporating non-volatile RAM for quick data buffering and power failure protection.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If storage controllers perform address translation for each data block operation, then data access flexibility is improved, but device complexity and wear increase

Engineering Contradiction:
Improvedata access flexibilityVSAvoidstorage controller complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent extracts the address translation function from the storage controller and implements it at the host level through software. This removes the burden of address translation from the storage controller, reducing its complexity while maintaining data access flexibility through software-based management of allocation units and zones.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces allocation units as an intermediary layer between the host and physical data blocks. This intermediary abstraction layer allows the host to manage data placement and address translation logically, while the storage controller simply handles physical block operations, reducing controller complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If storage controllers manage all data block operations including address translation, then data access control is improved, but unnecessary write operations increase

Engineering Contradiction:
Improvedata access controlVSAvoidredundant writes
Core Design Contradiction:
Ease of operationVSLoss of substance

Solution Approach 1:

The patent implements preliminary action by having the host system pre-plan data placement across multiple allocation units and zones before actual write operations. This allows the system to optimize data distribution and avoid redundant writes by determining the final destination of data blocks before writing, rather than making write decisions during the operation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The host system performs self-service by managing its own address translation and data placement logic through software. This eliminates the need for the storage controller to intervene in address translation operations, reducing unnecessary write amplification while maintaining ease of operation through software-based control.

Inventive Principle:
Principle #25Self-service

3Device complexity

If flash storage devices operate without centralized management, then device simplicity is improved, but reliability decreases

Engineering Contradiction:
Improvemanagement structureVSAvoidstorage reliability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent segments the storage system into distinct functional layers: the host handles high-level data management and address translation, while the storage controller handles low-level physical block operations. This segmentation allows centralized management of critical functions at the appropriate level, improving reliability without requiring complex management at every layer.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements beforehand cushioning through software-based redundancy and error handling mechanisms at the host level. By managing data placement across multiple allocation units and implementing software-level checks before write operations, the system cushions against potential failures while maintaining a relatively simple device structure.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

4Speed

If conventional storage systems perform write operations without optimization, then write speed is improved, but device lifespan decreases

Engineering Contradiction:
Improvewrite speedVSAvoidflash storage lifespan
Core Design Contradiction:
SpeedVSDuration of action of stationary object

Solution Approach 1:

The patent changes the parameters of write operations by introducing allocation units and zones that allow data to be distributed across multiple physical blocks. This enables write optimization techniques such as wear leveling and data placement strategies that extend flash storage lifespan while maintaining acceptable write speeds through efficient data management.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The patent implements continuity of useful action by maintaining a mapping structure that tracks data locations across allocation units and zones. This continuous tracking allows the system to optimize subsequent write operations by directing them to appropriate zones with available capacity, extending device lifespan without significantly impacting write speed through intelligent data placement.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS12461803B2Determining remaining hardware life in a storage device
Publication Date: 2025.11.04 PURE STORAGE INC
  • US12461803B2 patent drawing
  • US12461803B2 patent drawing
  • US12461803B2 patent drawing

AI summary

Determining remaining hardware life in a storage system, including: receiving data about a plurality of hardware components including data describing the usage of each hardware component and the state of each hardware component; analyzing the data to determine a remaining hardware life for each hardware component in a group of components; and distributing workloads in order to balance wear amongst the hardware components in the group.