Hybrid SSD Controller Data Segmentation for Latency Optimization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current solid state drive (SSD) systems do not fully exploit internal parallelism, leading to bottlenecks and quality of service issues due to inefficient data mapping and high costs, which can result in suboptimal user experience and the need for conventional magnetic disk technology.

Innovation Solution

A hybrid SSD system that separates data into latency-critical and non-latency-critical categories using storage class memory and NAND flash, with a controller that manages data placement based on host hints and data set management algorithms to optimize data storage and retrieval.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If SSD systems use dynamic mapping mechanism with flash memory packages connected through multiple channels, then data writing and reading speed is improved, but quality of service issues occur due to bottlenecks when multiple read requests target the same die

Engineering Contradiction:
Improvedata writing and reading speedVSAvoidquality of service
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The patent segments the storage system into multiple independent dies (e.g., die 0, die 1, die 2, die 3) that can be accessed in parallel. The mapping mechanism distributes logical blocks across different dies rather than concentrating them on a single die, enabling concurrent read/write operations on multiple channels simultaneously. This segmentation eliminates the bottleneck where multiple requests would queue for the same die, thereby maintaining high speed while improving quality of service through parallel processing.

Inventive Principle:
Principle #1Segmentation

2Productivity

If SSD systems fully exploit internal parallelism across multiple channels, then system efficiency is improved, but device complexity increases

Engineering Contradiction:
Improvesystem efficiencyVSAvoiddevice complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements a universal mapping mechanism that functions across all channels and dies in a standardized manner. The same mapping logic and data structure format are applied uniformly regardless of which channel or die is accessed, allowing the system to exploit parallelism without requiring complex, specialized handling for each individual channel. This multi-functional approach enables efficient parallel operations while keeping the control logic relatively simple and reusable across different parts of the system.

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

3Reliability

If hybrid SSD systems combine storage class memory and NAND flash, then quality of service is improved by separating latency-critical and non-latency-critical data, but manufacturing complexity increases

Engineering Contradiction:
Improvequality of serviceVSAvoidmanufacturing complexity
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The patent segments data into two categories: latency-critical data and non-latency-critical data. Storage class memory is allocated specifically for latency-critical data that requires fast access, while NAND flash is used for non-latency-critical data. The mapping mechanism automatically routes data to the appropriate storage medium based on its latency requirements, ensuring high quality of service for time-sensitive operations while maintaining cost-effective storage for less time-sensitive data. This segmentation approach manages manufacturing complexity by clearly defining separate roles for each storage component.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10430329B2Quality of service aware storage class memory/NAND flash hybrid solid state drive
Publication Date: 2019.10.01 SANDISK TECHNOLOGIES LLC
  • US10430329B2 patent drawing
  • US10430329B2 patent drawing
  • US10430329B2 patent drawing

AI summary

A device having a controller configured to interface with a host, a storage class memory configured to interface with the controller and a flash memory configured to interface with the controller, wherein both the storage class memory and the flash memory are configured to store data, and wherein the controller is configured to separate the data according to latency critical data and non-latency critical data.