# US 2021/0278994 A1 · Data storage device and data processing method

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0278994 A1
- Document ID: US20210278994A1
- Status: Published application
- Kind: A1
- Application number: 17/079,503
- Filed: 2020-10-25
- Published: 2021-09-09
- Earliest claimed: 2020-03-09
- Assignees: Silicon Motion, Inc.
- Applicants: Silicon Motion, Inc.
- Inventors: Tzu-Yi Yang
- Web page: https://patentgrep.com/patent/US20210278994A1

## CPC

- G06F 3/0655: {Vertical data movement, i.e. input-output transfer; data movement between one or more hosts and one or more storage devices}
- G06F 3/0604: {Improving or facilitating administration, e.g. storage management}
- G06F 3/0616: {in relation to life time, e.g. increasing Mean Time Between Failures [MTBF]}
- G06F 3/0619: {in relation to data integrity, e.g. data losses, bit errors}
- G06F 3/0649: {Lifecycle management}
- G06F 3/065: {Replication mechanisms}
- G06F 3/0679: {Non-volatile semiconductor memory device, e.g. flash memory, one time programmable memory [OTP]}
- G06F 3/0685: {Hybrid storage combining heterogeneous device types, e.g. hierarchical storage, hybrid arrays}
- G06F 11/0763: {by bit configuration check, e.g. of formats or tags}
- G06F 11/0793: {Remedial or corrective actions (recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40)}
- G06F 11/1448: {Management of the data involved in backup or backup restore}
- G06F 11/1461: {Backup scheduling policy}
- G06F 12/0253: {Garbage collection, i.e. reclamation of unreferenced memory}
- G06F 2201/805: Real-time
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A data storage device includes a memory device and a memory controller. The memory controller configures a first memory block which is a TLC memory blocks as a data buffer, and accordingly configures a plurality of second memory blocks which are SLC memory blocks. The memory controller uses the first memory block to receive data and accordingly store same data in the second memory blocks as backup data. When an amount of available memory space of the first memory block is smaller than or equal to a predetermined amount, the memory controller determines whether any error has occurred in the data stored in the first memory block. When there is any error occurred in the data stored in the first memory block, the memory controller configures a third memory block and move the backup data stored in the second memory block to the third memory block.

## Claims

### Claim 1

A data storage device, comprising:
a memory device, comprising a plurality of memory blocks; and
a memory controller, coupled to the memory device and arranged to access the memory device, wherein the memory controller is further arranged to configure a first memory block as a data buffer to receive data from a host device, and accordingly configure a plurality of second memory blocks, the first memory block is a Triple-Level Cell (TLC) memory block and the second memory blocks are Single-Level Cell (SLC) memory blocks, and
wherein the memory controller is further arranged to use the first memory block to receive the data and accordingly store same data in the second memory blocks as backup data of the data stored in the first memory block,
when an amount of available memory space of the first memory block is smaller than or equal to a predetermined amount, the memory controller is arranged to determine whether any error has occurred in the data stored in the first memory block, and
when there is any error occurred in the data stored in the first memory block, the memory controller is further arranged to configure a third memory block and move the backup data stored in the second memory blocks to the third memory block.

### Claim 2 (depends on 1)

The data storage device of claim 1, wherein when there is any error occurred in the data stored in the first memory block, the memory controller is further arranged to discard all the data stored in the first memory block.

### Claim 3 (depends on 1)

The data storage device of claim 1, wherein the third memory block is a TLC memory block, when the memory controller moves the backup data stored in the second memory blocks to the third memory block, the memory controller is arranged to copy the backup data stored in the second memory blocks and store the copied backup data in the third memory block.

### Claim 4 (depends on 3)

The data storage device of claim 3, wherein after the backup data stored in the second memory blocks has been moved to the third memory block, the memory controller is further arranged to discard all the backup data stored in the second memory blocks.

### Claim 5 (depends on 1)

The data storage device of claim 1, wherein when the memory controller determines that no error has occurred in the data stored in the first memory block the memory controller is further arranged to discard all the backup data stored in the second memory blocks corresponding to the first memory block.

### Claim 6 (depends on 1)

The data storage device of claim 1, wherein the memory controller comprises a buffer memory, when there is any error occurred in the data stored in the first memory block, the memory controller moves the backup data stored in the second memory blocks to the third memory block before updating content of a host-to-flash mapping table stored in the memory device based on content of a current flash-to-host mapping table sored in the buffer memory.

### Claim 7 (depends on 1)

The data storage device of claim 1, wherein the memory controller comprises a buffer memory, when there is any error occurred in the data stored in the first memory block, the memory controller moves the backup data stored in the second memory blocks to the third memory block via a garbage collection procedure performed in background after updating content of a host-to-flash mapping table stored in the memory device based on content of a current flash-to-host mapping table sored in the buffer memory.

### Claim 8 (depends on 1)

The data storage device of claim 1, wherein the memory device is a 3D NAND-type flash memory.

### Claim 9

A data processing method for a data storage device comprising a memory device and a memory controller, wherein the memory device comprises a plurality of memory blocks and the memory controller is coupled to the memory device and arranged to access the memory device, the data processing method is performed by the memory controller and comprises:
configuring a first memory block as a data buffer to receive data from a host device;
configuring a plurality of second memory blocks as backup memory blocks corresponding to the first memory block, wherein the first memory block is a Triple-Level Cell (TLC) memory block and the second memory blocks are Single-Level Cell (SLC) memory blocks;
using the first memory block to receive the data and accordingly storing same data in the second memory blocks as backup data of the data stored in the first memory block;
when an amount of available memory space of the first memory block is smaller than or equal to a predetermined amount, determining whether any error has occurred in the data stored in the first memory block;
configuring a third memory block when determining that there is any error occurred in the data stored in the first memory block; and
moving the backup data stored in the second memory blocks to the third memory block.

### Claim 10 (depends on 9)

The data processing method of claim 9, further comprising:
discarding all the data stored in the first memory block when determining that there is any error occurred in the data stored in the first memory block.

### Claim 11 (depends on 9)

The data processing method of claim 9, wherein the step of moving the backup data stored in the second memory blocks to the third memory block further comprises:
copying the backup data stored in the second memory blocks; and
storing the copied backup data in the third memory block, wherein the third memory block is a TLC memory block.

### Claim 12 (depends on 11)

The data processing method of claim 11, further comprising:
discarding all the backup data stored in the second memory blocks after the backup data stored in the second memory blocks has been moved to the third memory block.

### Claim 13 (depends on 9)

The data processing method of claim 9, further comprising:
discarding all the backup data stored in the second memory blocks corresponding to the first memory block when determining that no error has occurred in the data stored in the first memory block.

### Claim 14 (depends on 9)

The data processing method of claim 9, further comprising:
updating content of a host-to-flash mapping table stored in the memory device based on content of a current flash-to-host mapping table sored in a buffer memory,
wherein the steps of configuring the third memory block and moving the backup data stored in the second memory blocks to the third memory block are performed in foreground before the memory controller updates the content of the host-to-flash mapping table stored in the memory device based on content of the current flash-to-host mapping table sored in the buffer memory.

### Claim 15 (depends on 9)

The data processing method of claim 9, further comprising:
updating content of a host-to-flash mapping table stored in the memory device based on content of a current flash-to-host mapping table sored in a buffer memory,
wherein the steps of configuring the third memory block and moving the backup data stored in the second memory blocks to the third memory block are performed via a garbage collection procedure performed in background after the memory controller has updated the content of the host-to-flash mapping table stored in the memory device based on content of the current flash-to-host mapping table sored in the buffer memory.
