Two-Layer Controller Architecture for Scalable Data Storage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data storage devices face challenges in rapidly and conveniently expanding storage capacity and processor capabilities to meet high-speed data throughput requirements.

Innovation Solution

A data storage device and method utilizing a two-layer controller structure, where the front end communicates with the host and schedules operations, while the back end controls non-volatile memory, allowing for expansion of non-volatile memory controllers without altering the front-end components, maintaining identical controller arrangements and compositions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If the storage capacity and processor capabilities are expanded to meet high-speed data throughput requirements, then the data storage performance is improved, but the device complexity increases

Engineering Contradiction:
Improvedata throughputVSAvoidcontroller structure
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The controller is divided into two independent layers: a front-end controller that interfaces with the host and a back-end controller that manages the non-volatile memory. This segmentation allows the back-end to be scaled independently to increase storage capacity and throughput, while the front-end remains unchanged, thus improving productivity without proportionally increasing overall device complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a two-layer hierarchical structure that adds a dimensional separation between the host interface and memory control functions. By organizing controllers into front-end and back-end layers, the system can expand storage capacity by adding back-end controllers without affecting the front-end architecture, effectively decoupling the complexity growth from the performance improvement.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Quantity of substance

If the amount of non-volatile memory is increased to expand storage capacity, then the storage capacity is improved, but the number of controllers must be increased which complicates the device

Engineering Contradiction:
Improvestorage capacityVSAvoidnumber of controllers
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The controller function is segmented into front-end and back-end portions. The back-end controllers are specifically responsible for managing non-volatile memory, so when storage capacity needs to be increased by adding more memory chips, only the back-end controllers need to be added, not the entire controller system. This reduces the complexity increase proportionally.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The back-end controllers are designed as universal modules that can be replicated and added to handle increased storage capacity. Each back-end controller manages a specific portion of the non-volatile memory, and these modules are identical and interchangeable, simplifying the expansion process compared to designing custom controller configurations for different capacity levels.

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

3Quantity of substance

If additional controllers are added to increase storage capacity, then the storage capacity is improved, but the front end arrangement must be changed which increases design complexity

Engineering Contradiction:
Improvestorage capacityVSAvoiddesign complexity
Core Design Contradiction:
Quantity of substanceVSEase of manufacture

Solution Approach 1:

The controller architecture is segmented such that the front-end arrangement is completely independent of the back-end configuration. The front-end controllers handle host communication and scheduling, while back-end controllers manage memory operations. This segmentation allows the back-end to be expanded by adding more identical modules without changing the front-end design, significantly simplifying manufacturing and reducing design complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The back-end controllers are designed as identical copyable modules that can be replicated to handle increased storage capacity. Since all back-end controllers have the same structure and function, adding more storage capacity simply involves adding more copies of the same module, rather than designing new controller configurations. This copying approach reduces design complexity while maintaining ease of manufacture.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS11099775B2Data storage device and data storage method
Publication Date: 2021.08.24 SILICON MOTION INC
  • US11099775B2 patent drawing
  • US11099775B2 patent drawing
  • US11099775B2 patent drawing

AI summary

A data storage device includes at least one non-volatile memory and a controller with two-layer architecture. The two-layer architecture includes a front end coupled to a host and a back end coupled to the non-volatile memory. The controller includes a command processor and at least one non-volatile memory controller. The command processor is arranged on the front end to communicate with the host, and it schedules the operation of the data storage device based on an external command from the host. The non-volatile memory controller is arranged on the back end, and it controls the non-volatile memory based on the schedule of the command processor. When the non-volatile memory increases, the non-volatile memory controller also increases correspondingly while the amount of command processors remains the same.