Storage device for migrating user data stored in unavailable memory die

By grouping memory dies and using flash conversion layer management, data access problems in memory die failures are solved, performance differences between memory die groups are reduced, and system stability and performance are improved.

CN118915958APending Publication Date: 2024-11-08SK HYNIX INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202311441983.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-05-08
Filing Date
2023-12-05
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

In the event of a memory die failure, existing storage devices have difficulty accessing user data stored in an unavailable state, and performance differences between memory die groups lead to a degradation of system performance.

Method used

Design a storage device to migrate user data to a reserved space block group or other memory die group by grouping multiple memory dies into M groups, if one of the memory dies is in an unavailable state and use Flash Transformation Layer (FTL) for data migration and management to reduce performance differences.

Benefits of technology

Access and migration of user data in unavailable memory dies is achieved, performance differences between memory die groups are reduced, and system stability and performance are ensured.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118915958A_ABST
    Figure CN118915958A_ABST
Patent Text Reader

Abstract

A memory device may group a plurality of memory dies into M memory die groups, and when a first memory die in a first memory die group among the M memory die groups is determined to be in an unavailable state, user data stored in the user data block of the first memory die is migrated to the first set of reserved space blocks. The first reserved space block group may include reserved space blocks of memory dies other than the first memory die among the memory dies in the first memory die group.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the priority of Korean Patent Application No. 10-2023-0058957 filed on May 8, 2023, in the Korean Intellectual Property Office, which is incorporated herein by reference in its entirety. Technical Field

[0003] Various embodiments are generally directed to a storage device for migrating user data stored in a memory die that is in an unusable state. Background Art

[0004] The storage device is a device that stores data based on a request of an external device such as a computer, a mobile terminal such as a smartphone or a tablet, or any of various electronic devices.

[0005] The storage device may include a controller for controlling a memory (e.g., a volatile memory / non-volatile memory). The controller may receive a command from an external device, and may execute or control an operation of reading, writing, or erasing data for the memory included in the storage device based on the received command.

[0006] On the other hand, a failure may occur in a specific memory die included in the memory. In this case, the storage device can set the memory die to an unusable state so that a read operation or a write operation is not performed on the memory die. Summary of the invention

[0007] Embodiments of the present disclosure may provide a storage device capable of accessing user data stored in a memory die that is in an unusable state.

[0008] Embodiments of the present disclosure may also provide a memory device capable of reducing performance differences between memory die groups.

[0009] In one aspect, an embodiment of the present disclosure may provide a storage device, the storage device comprising: i) a memory including a plurality of memory dies, each memory die including a plurality of user data blocks and a plurality of reserved space blocks; and ii) a controller configured to group the plurality of memory dies into M (M is a natural number of 2 or greater) memory die groups, and when a first memory die in a first memory die group among the M memory die groups is determined to be in an unavailable state, migrate user data stored in a user data block of the first memory die to a first reserved space block group. In this case, the first reserved space block group includes reserved space blocks of memory dies other than the first memory die among the memory dies in the first memory die group.

[0010] On the other hand, an embodiment of the present disclosure may provide a storage device, comprising: i) a memory, comprising a plurality of memory dies, each memory die comprising a plurality of memory blocks; and ii) a controller, configured to group the plurality of memory dies into M (M is a natural number of 2 or greater) memory die groups, determine that a first memory die included in a first memory die group among the M memory die groups is in an unavailable state, migrate user data stored in the first memory die to a first memory block group including one or more memory blocks included in the first memory die group, and determine whether to migrate a portion of the user data stored in the first memory block group to a second memory block group including one or more memory blocks included in a second memory die group among the M memory die groups.

[0011] On the other hand, an embodiment of the present disclosure may provide a storage device, comprising: i) a memory, comprising a plurality of memory dies, each memory die comprising a plurality of storage blocks; and ii) a controller, configured to group the plurality of memory dies into M (M is a natural number of 2 or greater) memory die groups, determine that a first memory die in a first memory die group among the M memory die groups is in an unavailable state, migrate data corresponding to a target logical address among user data stored in the first memory die to a second memory die group among the M memory die groups, and use a flash translation layer (FTL) corresponding to the second memory die group to control the data corresponding to the target logical address.

[0012] According to an embodiment of the present disclosure, user data stored in a memory die in an unavailable state may be accessed, and performance differences between memory die groups may be reduced. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 A storage device according to an embodiment of the present disclosure is shown.

[0014] Figure 2 Shows Figure 1 of memory.

[0015] Figure 3 A storage device according to an embodiment of the present disclosure is shown.

[0016] Figure 4 A plurality of memory die groups are shown in accordance with embodiments of the present disclosure.

[0017] Figure 5 The operation of the storage device according to the embodiment of the present disclosure migrating user data to a first overprovisioning block group is shown.

[0018] Figure 6 An operation of performing user data correction by a storage device according to an embodiment of the present disclosure is shown.

[0019] Figure 7 An operation of a storage device according to an embodiment of the present disclosure determining whether to migrate a portion of user data stored in a first reserved space block group is shown.

[0020] Figure 8 An operation of a storage device migrating a portion of user data stored in a first reserved space block group according to an embodiment of the present disclosure is shown.

[0021] Fig. 9 The operation of a storage device managing a remapping table according to an embodiment of the present disclosure is shown.

[0022] Fig.10 An operating method of a storage device according to an embodiment of the present disclosure is shown.

[0023] Fig.11 The operation of a storage device migrating a portion of user data according to an embodiment of the present disclosure is shown.

[0024] Fig.12 An operation of a storage device migrating a portion of user data according to another embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0025] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. Throughout the specification, references to "an embodiment," "another embodiment," etc. are not necessarily directed to only one embodiment, and different references to any such phrases are not necessarily limited to the same embodiment. When used herein, the term "embodiment" does not necessarily refer to all embodiments.

[0026] Various embodiments of the present invention are described in more detail below with reference to the accompanying drawings. However, the present invention can be embodied in different forms and variations, and should not be construed as being limited to the embodiments set forth herein. On the contrary, the described embodiments are provided so that the present disclosure will be thorough and complete, and the present invention will be fully conveyed to those skilled in the art to which the present invention belongs. Throughout the disclosure, the same reference numerals represent the same components throughout the various drawings and embodiments of the present invention.

[0027] Method described herein, process and / or operation can be performed by code or instruction to be run by computer, processor, controller or other signal processing device.The computer, processor, controller or other signal processing device can be the element described herein or can be the element except the element described herein.Because the algorithm of the basis of formation method (or the operation of computer, processor, controller or other signal processing device) is described in detail, the code or instruction for realizing the operation of the method embodiment can convert computer, processor, controller or other signal processing device into the special processor for performing the method herein.

[0028] When implemented at least in part in software, controllers, processors, devices, modules, units, multiplexers, logic, interfaces, decoders, drivers, generators, and other signal generation and signal processing features may include, for example, a memory or other storage device for storing code or instructions, such as to be executed by a computer, processor, microprocessor, controller or other signal processing device.

[0029] Figure 1 A storage device 100 according to an embodiment of the present disclosure is shown.

[0030] Reference Figure 1 , the storage device 100 may include a memory 110 that stores data and a controller 120 that controls the memory 110 .

[0031] The memory 110 includes a plurality of memory blocks, and operates under the control of the controller 120. The operation of the memory 110 may include a read operation, a program operation (also referred to as a write operation), and an erase operation.

[0032] The memory 110 may include a memory cell array including a plurality of memory cells (also simply referred to as "cells") storing data. Such a memory cell array may exist in a memory block.

[0033] For example, the memory 110 may be implemented as various types of memories, such as double data rate synchronous dynamic random access memory (DDR SDRAM), fourth generation low power double data rate (LPDDR4) SDRAM, graphic double data rate (GDDR) SDRAM, low power DDR (LPDDR), RDRAM (Rambus dynamic random access memory), NAND flash memory, 3D NAND flash memory, NOR flash memory, resistive random access memory (RRAM), phase change memory (PRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), and spin transfer torque random access memory (STT-RAM).

[0034] The memory 110 may be implemented as a three-dimensional array structure. For example, the embodiments of the present disclosure may be applied to a charge trap flash memory (CTF) in which a charge storage layer is configured by a dielectric layer and a flash memory in which a charge storage layer is configured by a conductive floating gate.

[0035] The memory 110 may receive a command and an address from the controller 120 and may access a region selected by the address in the memory cell array. In other words, the memory 110 may perform an operation indicated by the command on the region selected by the address.

[0036] The memory 110 may perform a programming operation, a reading operation, or an erasing operation. For example, when performing a programming operation, the memory 110 may program data to an area selected by an address. When performing a reading operation, the memory 110 may read data from an area selected by an address. In an erasing operation, the memory 110 may erase data stored in an area selected by an address.

[0037] The controller 120 may control a write (program) operation, a read operation, an erase operation, and a background operation of the memory 110. For example, the background operation may include at least one of a garbage collection (GC) operation, a wear leveling (WL) operation, a read reclaim (RR) operation, a bad block management (BBM) operation, and the like.

[0038] The controller 120 may control the operation of the memory 110 according to a request from a device (eg, a host) located outside the storage device 100. However, the controller 120 may also control the operation of the memory 110 regardless of or in the absence of a request from the host.

[0039] As non-limiting examples, the host may be a computer, an ultra mobile PC (UMPC), a workstation, a personal digital assistant (PDA), a tablet computer, a mobile phone, a smart phone, an e-book, a portable multimedia player (PMP), a portable game console, a navigation device, a black box, a digital camera, a digital multimedia broadcasting (DMB) player, a smart TV, a digital audio recorder, a digital audio player, a digital picture recorder, a digital picture player, a digital video recorder, a digital video player, a storage device configuring a data center, one of various electronic devices configuring a home network, one of various electronic devices configuring a computer network, one of various electronic devices configuring a telematics network, a radio frequency identification (RFID) device, and a mobile device capable of traveling under human control or automatically driving, such as a vehicle, a robot, or a drone. Alternatively, the host may be a virtual reality (VR) device providing a 2D or 3D virtual reality image or an augmented reality (AR) device providing an augmented reality image. The host may be any of various electronic devices that require a storage device 100 capable of storing data.

[0040] The host may include at least one operating system (OS). The operating system may generally manage and control functions and operations of the host, and may provide interoperability between the host and the storage device 100. The operating system may be classified into a general operating system and a mobile operating system according to the mobility of the host.

[0041] The controller 120 and the host may be separate devices from each other, or the controller 120 and the host may be integrated into one device. Hereinafter, for convenience of explanation, the controller 120 and the host are described as separate devices from each other.

[0042] Reference Figure 1 , the controller 120 may include a memory interface 122 and a control circuit 123 , and may further include a host interface 121 .

[0043] The host interface 121 provides an interface for communicating with the host. For example, the host interface 121 provides an interface using at least one of various interface protocols such as the following: Universal Serial Bus (USB) protocol, Multimedia Card (MMC) protocol, Peripheral Component Interconnect (PCI) protocol, High-Speed ​​PCI (PCI-E) protocol, Advanced Technology Attachment (ATA) protocol, Serial ATA protocol, Parallel ATA protocol, Small Computer System Interface (SCSI) protocol, Enhanced Small Disk Interface (ESDI) protocol, Integrated Drive Electronics (IDE) protocol, and proprietary protocol.

[0044] When receiving a command from the host, the control circuit 123 may receive the command through the host interface 121 and may perform an operation of processing the received command.

[0045] The memory interface 122 may be coupled with the memory 110 to provide an interface for communicating with the memory 110. That is, the memory interface 122 may be configured to provide an interface between the memory 110 and the controller 120 in response to the control of the control circuit 123.

[0046] The control circuit 123 performs overall control operations of the controller 120 to control the operation of the memory 110. To this end, the control circuit 123 may include at least one of a processor 124 and a working memory 125, and may optionally include an error detection and correction circuit (ECC circuit) 126, for example.

[0047] The processor 124 may control the overall operation of the controller 120 and may perform logical operations. The processor 124 may communicate with the host through the host interface 121 and may communicate with the memory 110 through the memory interface 122.

[0048] The processor 124 may perform the function of a flash translation layer (FTL). The processor 124 may convert a logical block address (LBA) provided by the host into a physical block address (PBA) through the flash translation layer (FTL). The flash translation layer (FTL) may receive a logical block address (LBA) and convert the logical block address (LBA) into a physical block address (PBA) by using a mapping table.

[0049] The flash translation layer has a variety of address mapping methods according to the mapping unit. Representative address mapping methods include a page mapping method, a block mapping method, and a hybrid mapping method.

[0050] The processor 124 may randomize the data received from the host. For example, the processor 124 may randomize the data received from the host by using a set randomization seed. The randomized data may be provided to the memory 110 and may be programmed into the memory cell array of the memory 110.

[0051] In a read operation, the processor 124 may derandomize the data received from the memory 110. For example, the processor 124 may derandomize the data received from the memory 110 by using a derandomization seed. The derandomized data may be output to the host.

[0052] The processor 124 may run firmware to control the operation of the controller 120. That is, in order to control the overall operation of the controller 120 and perform logical operations, the processor 124 may run (drive) the firmware loaded into the working memory 125 at startup. Hereinafter, the operation of the storage device 100 according to an embodiment of the present disclosure will be described as implementing the processor 124 running the firmware that defines the corresponding operation.

[0053] The firmware, which is a program to be executed in the storage device 100 to drive the storage device 100, may include various functional layers. For example, the firmware may include binary data defining codes for respectively executing the functional layers.

[0054] For example, the firmware may include at least one of a flash translation layer (FTL), a host interface layer (HIL), and a flash interface layer (FIL), wherein the flash translation layer (FTL) performs a conversion function between a logical address requested by the host to the storage device 100 and a physical address of the memory 110, the host interface layer (HIL) is used to analyze a command requested by the host to the storage device 100 as a storage device and transmit the command to the flash translation layer (FTL), and the flash interface layer (FIL) transmits the command indicated by the flash translation layer (FTL) to the memory 110.

[0055] Such firmware may be loaded into the working memory 125 from, for example, the memory 110 or a separate non-volatile memory (e.g., ROM or NOR flash) located outside the memory 110. The processor 124 may first load all or part of the firmware into the working memory 125 when running a startup operation after power-on.

[0056] The processor 124 may execute the logic operation defined in the firmware loaded in the working memory 125 to control the overall operation of the controller 120. The processor 124 may store the result of executing the logic operation defined in the firmware in the working memory 125. The processor 124 may control the controller 120 according to the result of executing the logic operation defined in the firmware so that the controller 120 generates a command or a signal. When a portion of the firmware defining the logic operation to be executed is stored in the memory 110 but is not loaded into the working memory 125, the processor 124 may generate an event (e.g., an interrupt) for loading the corresponding portion of the firmware from the memory 110 into the working memory 125.

[0057] The processor 124 may load metadata required for driving firmware from the memory 110. The metadata, which is data for managing the memory 110, may include management information related to user data stored in the memory 110, for example.

[0058] The firmware may be updated when the storage device 100 is manufactured or while the storage device 100 is operating. The controller 120 may download new firmware from the outside of the storage device 100 and update the existing firmware with the new firmware.

[0059] The working memory 125 may store necessary firmware, program code, commands, and data to drive the controller 120. The working memory 125 may be a volatile memory including, for example, at least one of static RAM (SRAM), dynamic RAM (DRAM), and synchronous DRAM (SDRAM).

[0060] The error detection and correction circuit 126 can detect an error bit of the target data by using an error correction code and correct the detected error bit. The target data may be, for example, data stored in the working memory 125 or data read from the memory 110.

[0061] The error detection and correction circuit 126 can decode the data by using an error correction code. The error detection and correction circuit 126 can be implemented by various code decoders. For example, a decoder that performs non-systematic code decoding or a decoder that performs systematic code decoding can be used.

[0062] For example, when each read data is composed of a plurality of sectors, the error detection and correction circuit 126 can detect error bits in each read data in units of set sectors. A sector can represent a data unit smaller than a page, which is a read unit of a flash memory. The sectors constituting each read data can be matched with each other using addresses.

[0063] The error detection and correction circuit 126 may calculate a bit error rate (BER) and may determine whether the error is correctable in units of sectors. For example, when the bit error rate (BER) is higher than a reference value, the error detection and correction circuit 126 may determine that the corresponding sector is uncorrectable or failed. On the other hand, when the bit error rate (BER) is lower than a reference value, the error detection and correction circuit 126 may determine that the corresponding sector is correctable or passed.

[0064] The error detection and correction circuit 126 may sequentially perform error detection and correction operations on all read data. In the case where a sector included in the read data is correctable, the error detection and correction circuit 126 may omit the error detection and correction operation on the corresponding sector for the next read data. If the error detection and correction operation on all read data is ended in this manner, the error detection and correction circuit 126 may finally detect an uncorrectable sector in the read data. There may be one or more sectors that are determined to be uncorrectable. The error detection and correction circuit 126 may transmit information (e.g., address information) about the sector determined to be uncorrectable to the processor 124.

[0065] The bus 127 may be configured to provide a channel between the components 121, 122, 124, 125, and 126 of the controller 120. For example, the bus 127 may include a control bus for transmitting various control signals, commands, etc., and a data bus for transmitting various data, etc.

[0066] Some of the above components 121, 122, 124, 125, and 126 of the controller 120 may be omitted, or some of the above components 121, 122, 124, 125, and 126 of the controller 120 may be integrated into one component. In addition to the above components 121, 122, 124, 125, and 126 of the controller 120, one or more other components may be added.

[0067] In the following, reference will be made to Figure 2 The memory 110 is described in further detail.

[0068] Figure 2 Shows Figure 1 Memory 110.

[0069] Reference Figure 2 , the memory 110 may include a memory cell array 210 , an address decoder 220 , a read and write circuit 230 , a control logic 240 , and a voltage generation circuit 250 .

[0070] The memory cell array 210 may include a plurality of memory blocks BLK1 to BLKz (where z is a natural number of 2 or more).

[0071] In the plurality of memory blocks BLK1 to BLKz, a plurality of word lines WL and a plurality of bit lines BL may be provided, and a plurality of memory cells (MC) may be arranged.

[0072] The plurality of memory blocks BLK1 to BLKz may be coupled to the address decoder 220 through a plurality of word lines WL. The plurality of memory blocks BLK1 to BLKz may be coupled to the read and write circuit 230 through a plurality of bit lines BL.

[0073] Each of the plurality of memory blocks BLK1 to BLKz may include a plurality of memory cells. For example, the plurality of memory cells may be nonvolatile memory cells and may be configured of nonvolatile memory cells having a vertical channel structure.

[0074] The memory cell array 210 may be configured by a memory cell array of a two-dimensional structure, or may be configured by a memory cell array of a three-dimensional structure.

[0075] Each of the plurality of memory cells included in the memory cell array 210 may store at least 1 bit of data. For example, each of the plurality of memory cells included in the memory cell array 210 may be a single-layer cell (SLC) storing 1 bit of data. In another example, each of the plurality of memory cells included in the memory cell array 210 may be a multi-layer cell (MLC) storing 2 bits of data. In yet another example, each of the plurality of memory cells included in the memory cell array 210 may be a triple-layer cell (MLC) storing 3 bits of data. In yet another example, each of the plurality of memory cells included in the memory cell array 210 may be a quad-layer cell (QLC) storing 4 bits of data. In other examples, the memory cell array 210 may include a plurality of memory cells, each of which stores 5 or more bits of data.

[0076] The number of bits of data stored in each of the plurality of memory cells can be dynamically determined. For example, a single-layer cell storing 1 bit of data can be changed to a triple-layer cell storing 3 bits of data.

[0077] Reference Figure 2 , the address decoder 220 , the read and write circuit 230 , the control logic 240 , and the voltage generating circuit 250 may operate as peripheral circuits for driving the memory cell array 210 .

[0078] The address decoder 220 may be coupled to the memory cell array 210 through a plurality of word lines WL.

[0079] The address decoder 220 may be configured to operate in response to the control of the control logic 240 .

[0080] The address decoder 220 may receive an address through an input / output buffer in the memory 110. The address decoder 220 may be configured to decode a block address in the received address. The address decoder 220 may select at least one memory block according to the decoded block address.

[0081] The address decoder 220 may receive a read voltage Vread and a pass voltage Vpass from the voltage generating circuit 250 .

[0082] The address decoder 220 may apply a read voltage Vread to a selected word line WL in a selected memory block during a read operation, and may apply a pass voltage Vpass to the remaining unselected word lines WL.

[0083] The address decoder 220 may apply the verification voltage generated in the voltage generation circuit 250 to a selected word line WL in a selected memory block in a program verification operation, and may apply the pass voltage Vpass to the remaining unselected word lines WL.

[0084] The address decoder 220 may be configured to decode the column address in the received address and may transmit the decoded column address to the read and write circuit 230 .

[0085] The read operation and the program operation of the memory 110 may be performed in units of pages. When a read operation or a program operation is requested, the received address may include at least one of a block address, a row address, and a column address.

[0086] The address decoder 220 may select a memory block and a word line according to the block address and the row address. The column address may be decoded by the address decoder 220 and provided to the read and write circuit 230.

[0087] The address decoder 220 may include at least one of a block decoder, a row decoder, a column decoder, and an address buffer.

[0088] The read and write circuit 230 may include a plurality of page buffers PB. The read and write circuit 230 may operate as a read circuit in a read operation of the memory cell array 210, and may operate as a write circuit in a write operation of the memory cell array 210.

[0089] The above-mentioned read and write circuit 230 may also be referred to as a page buffer circuit or a data register circuit including a plurality of page buffers PB. The read and write circuit 230 may include a data buffer responsible for a data processing function, and may further include a cache buffer responsible for a cache function.

[0090] The plurality of page buffers PB may be coupled to the memory cell array 210 through the plurality of bit lines BL. The plurality of page buffers PB may continuously supply a sensing current to the bit lines BL coupled to the memory cells in a read operation and a program verification operation to sense a threshold voltage (Vth) of the memory cells, and may latch sensing data by sensing a change in a current amount depending on a programming state of a corresponding memory cell by a sensing node.

[0091] The read and write circuit 230 may operate in response to a page buffer control signal output from the control logic 240 .

[0092] In a read operation, the read and write circuit 230 temporarily stores the read data by sensing the data of the memory cell and then outputs the data DATA to the input / output buffer of the memory 110. As an exemplary embodiment, the read and write circuit 230 may further include a column selection circuit in addition to the page buffer PB or the page register.

[0093] The control logic 240 may be coupled to the address decoder 220, the read and write circuit 230, and the voltage generating circuit 250. The control logic 240 may receive a command CMD and a control signal CTRL through an input / output buffer of the memory 110.

[0094] The control logic 240 may be configured to control the overall operation of the memory 110 in response to the control signal CTRL. The control logic 240 may output a control signal for adjusting the precharge potential level of the sensing nodes of the plurality of page buffers PB.

[0095] The control logic 240 may control the read and write circuit 230 to perform a read operation of the memory cell array 210. The voltage generation circuit 250 may generate a read voltage Vread and a pass voltage Vpass for a read operation in response to a voltage generation circuit control signal output from the control logic 240.

[0096] Each memory block of the above-described memory 110 may be configured by a plurality of pages corresponding to a plurality of word lines WL and a plurality of strings corresponding to a plurality of bit lines BL.

[0097] In the memory block BLK, a plurality of word lines WL and a plurality of bit lines BL may be arranged to intersect each other. For example, each of the plurality of word lines WL may be arranged along a row direction, and each of the plurality of bit lines BL may be arranged along a column direction. In another example, each of the plurality of word lines WL may be arranged along a column direction, and each of the plurality of bit lines BL may be arranged along a row direction.

[0098] The memory cell may be coupled to one of a plurality of word lines WL and one of a plurality of bit lines BL. A transistor may be provided in each memory cell.

[0099] For example, the transistor provided in each memory cell (MC) may include a drain, a source, and a gate. The drain (or source) of the transistor may be connected to the corresponding bit line BL directly or via another transistor. The source (or drain) of the transistor may be connected to the source line (which may be a ground potential) directly or via another transistor. The gate of the transistor may include a floating gate and a control gate, the floating gate being surrounded by a dielectric, and the gate voltage from the word line WL being applied to the control gate.

[0100] In each memory block, a first selection line (also called a source selection line or a drain selection line) may be additionally disposed outside a first outermost word line among the two outermost word lines that is closer to the read and write circuit 230, and a second selection line (also called a drain selection line or a source selection line) may be additionally disposed outside a second outermost word line among the two outermost word lines.

[0101] At least one dummy word line may be additionally disposed between the first outermost word line and the first selection line. At least one dummy word line may also be additionally disposed between the second outermost word line and the second selection line.

[0102] The read operation and program operation (write operation) of the above-mentioned memory block may be performed in units of pages, and the erase operation may be performed in units of memory blocks.

[0103] Figure 3 A storage device 100 according to an embodiment of the present disclosure is shown.

[0104] Reference Figure 3 , the storage device 100 may include a memory 110 and a controller 120 .

[0105] The memory 110 may include a plurality of memory dies DIE. Each of the plurality of memory dies DIE may include a plurality of user data blocks USER_BLK and a plurality of over-reserved space blocks OP_BLK. Each memory die DIE may include a plurality of memory blocks, and each of the plurality of memory blocks may be classified as a user data block USER_BLK or an over-reserved space block OP_BLK.

[0106] The user data block USER_BLK is a memory block capable of storing user data requested to be written from outside the memory device 100 , for example, from a host.

[0107] The over-provisioning block OP_BLK is a memory block that may be used to replace a failed user data block or to run background operations such as garbage collection, wear leveling, etc. Some of the memory blocks included in the memory 110 may be allocated as the over-provisioning block OP_BLK.

[0108] In an embodiment of the present disclosure, the controller 120 may group a plurality of memory die DIEs into M (M is a natural number of 2 or more) memory die groups and control the M memory die groups. This will be described in detail below.

[0109] Figure 4 FIG. 2 is a diagram showing a plurality of memory die groups DIE_GRP according to an embodiment of the present disclosure. Figure 3 The storage device 100 is shown to describe Figure 4 Multiple memory die groups DIE_GRP are shown.

[0110] Reference Figure 4 , the controller 120 of the memory device 100 may group the plurality of memory die DIE into M memory die groups DIE_GRP.

[0111] Each of the M memory die groups DIE_GRP may include one or more memory die DIEs. The controller 120 may generate FTL instances corresponding to the M memory die groups DIE_GRPs to respectively run flash translation layer (FTL) functions for the M memory die groups DIE_GRPs. The FTL instances may control operations on the corresponding memory die groups.

[0112] For example, the FTL instance may be a process or a thread. The FTL instances corresponding to the M memory die groups DIE_GRP may be respectively executed by a processor, for example, Figure 1 The different processing cores included in processor 124 are shown to operate.

[0113] On the other hand, in an embodiment of the present disclosure, the controller 120 of the memory device 100 may determine that a specific memory die among the memory dies included in the M memory die groups DIE_GRP is in an unavailable state. The unavailable state may be referred to as an offline state, a bad state, a disabled state, etc. The specific memory die in the unavailable state may be referred to as an unavailable memory die.

[0114] In this case, in order to access the user data stored in the unavailable memory die, the controller 120 may migrate the user data stored in the unavailable memory die to another memory die. Figure 5 This is described in detail.

[0115] Figure 5 FIG. 2 shows an operation of the storage device 100 according to an embodiment of the present disclosure to migrate user data USR_DATA to the first over-provisioning block group OP_BLK_GRP_1. Figure 3 The storage device 100 is shown to describe Figure 5 The operations shown in .

[0116] Reference Figure 5 , the controller 120 of the memory device 100 may determine that the first memory die DIE_1 included in the first memory die group DIE_GRP_1 among the M memory die groups DIE_GRP is in an unusable state. When the first memory die DIE_1 is determined to be in an unusable state, the storage capacity of the first memory die group DIE_GRP_1 may be reduced.

[0117] The condition under which the controller 120 determines that the first memory die DIE_1 is in the unusable state may vary.

[0118] For example, when the number of bad blocks included in the first memory die DIE_1 is greater than or equal to a threshold bad block number, the controller 120 may determine that the first memory die DIE_1 is in an unusable state.

[0119] As another example, when a ratio of failures occurring in read operations executed on the first memory die DIE_1 within a predetermined period of time is greater than or equal to a threshold ratio, the controller 120 may determine that the first memory die DIE_1 is in an unusable state.

[0120] When the first memory die DIE_1 is determined to be in an unusable state, the controller 120 may migrate user data USR_DATA stored in the first memory die DIE_1 to the first over-provisioning block group OP_BLK_GRP_1.

[0121] The first over-provisioning block group OP_BLK_GRP_1 may include over-provisioning blocks OP_BLK included in memory dies other than the first memory die DIE_1 among the memory dies DIE included in the first memory die group DIE_GRP_1. On the other hand, the over-provisioning blocks included in the first memory die DIE_1 may not be included in the first over-provisioning block group OP_BLK_GRP_1.

[0122] Thus, even if the first memory die DIE_1 is determined to be in an unusable state, the controller 120 may access the user data USR_DATA.

[0123] On the other hand, the controller 120 may perform correction on the user data USR_DATA while migrating the user data USR_DATA to the first over-provisioning block group OP_BLK_GRP_1. This is because when the first memory die DIE_1 is determined to be unavailable, a failure may occur in accessing the user data USR_DATA stored in the first memory die DIE_1.

[0124] Will refer to Figure 6 This is described in detail.

[0125] Figure 6 FIG. 2 shows an operation of the memory device 100 to perform correction of the user data USR_DATA according to an embodiment of the present disclosure. Figure 3 The storage device 100 is shown to describe Figure 6 The operations shown in .

[0126] Reference Figure 6When the controller 120 of the storage device 100 migrates the user data USR_DATA to the first over-provisioning block group OP_BLK_GRP_1, the controller 120 may perform correction of the user data USR_DATA based on the parity bits PAR_DATA of the user data USR_DATA. Thereafter, the controller 120 may store the corrected user data USR_DATA in the first over-provisioning block group OP_BLK_GRP_1.

[0127] On the other hand, Figure 6 In the embodiment, the parity bit PAR_DATA is stored in one of the memory dies other than the first memory die DIE_1 in the first memory die group DIE_GRP_1. However, the storage location of the parity bit PAR_DATA is not affected by Figure 6 The embodiment is not limited to the embodiment, but the parity bits PAR_DATA may be stored in the first memory die DIE_1, or in a memory die included in another memory die group other than DIE_GRP_1 in the first memory die group.

[0128] Hereinabove, an operation of migrating the user data USR_DATA stored in the first memory die DIE_1 to the first over-provisioning block group OP_BLK_GRP_1 when the first memory die DIE_1 is determined to be in an unusable state has been described.

[0129] When user data USR_DATA stored in the first memory die DIE_1 is migrated to the first over-provisioning block group OP_BLK_GRP_1, the number of free over-provisioning blocks included in the first over-provisioning block group OP_BLK_GRP_1 may decrease.

[0130] Therefore, a performance deviation may occur between the first memory die group DIE_GRP_1 and other memory die groups among the M memory die groups DIE_GRP, thereby reducing the performance of the memory device 100 .

[0131] Therefore, the storage device 100 can migrate a portion of the user data USR_DATA stored in the first over-provisioning block group OP_BLK_GRP_1 to another memory die group, thereby resolving the performance deviation between the first memory die group DIE_GRP_1 and the other memory die groups. Figure 7 This is described in detail.

[0132] Figure 7FIG. 2 shows an operation of the storage device 100 according to an embodiment of the present disclosure to determine whether to migrate a portion of the user data USR_DATA stored in the first over-provisioning block group OP_BLK_GRP_1. Figure 3 The storage device 100 is shown to describe Figure 7 The operations shown in .

[0133] Reference Figure 7 , the controller 120 of the storage device 100 may monitor the number of free over-provisioning blocks included in the first over-provisioning block group OP_BLK_GRP_1 after migrating the user data USR_DATA to the first over-provisioning block group OP_BLK_GRP_1 (S710). The free over-provisioning blocks are over-provisioning blocks that are in an erased state and thus can store new data.

[0134] For example, the controller 120 may execute a process of monitoring a data storage state of each of the over-provisioning blocks included in the M memory die groups DIE_GRP, and may accordingly monitor the number of free over-provisioning blocks included in the first over-provisioning block group OP_BLK_GRP_1.

[0135] On the other hand, when one or more of the plurality of memory die DIEs are set to an unavailable state, a process of monitoring a data storage state of each of the over-provisioned space blocks included in the M memory die groups DIE_GRPs may be executed.

[0136] Then, the controller 120 may determine whether the number of free over-provisioned space blocks included in the first over-provisioned space block group OP_BLK_GRP_1 is less than or equal to the threshold number of free blocks (S720). Thus, the controller 120 may determine whether there is a large imbalance between the number of free over-provisioned space blocks included in the first memory die group DIE_GRP_1 among the M memory die groups DIE_GRP and the number of free over-provisioned space blocks included in other memory die groups.

[0137] The controller 120 may determine the threshold number of free blocks in various ways.

[0138] For example, the controller 120 may determine the threshold number of free blocks as a predetermined value.

[0139] As another example, the controller 120 may determine the threshold number of free blocks as a value obtained by multiplying the number of over-provisioning blocks included in the memory die group by a predetermined ratio (eg, 10%).

[0140] As another example, the controller 120 may determine the threshold number of free blocks as a value obtained by subtracting a deviation from an average value of the numbers of free over-provisioning blocks respectively included in the M memory die groups DIE_GRP.

[0141] The deviation may be determined in a variety of ways. For example, the deviation may be a predetermined value. As another example, the deviation may be a value set based on a standard deviation of the number of free over-provisioning blocks respectively included in the M memory die groups DIE_GRP.

[0142] When the number of free reserved space blocks included in the first reserved space block group OP_BLK_GRP_1 is less than or equal to the threshold number of free blocks (S720-Yes), the controller 120 may migrate a portion of the user data USR_DATA stored in the first reserved space block group OP_BLK_GRP_1 to the second reserved space block group (S730). In this case, the number of free reserved space blocks included in the second reserved space block group may be greater than or equal to the threshold number of free blocks.

[0143] Thus, the controller 120 can reduce the performance deviation among the M memory die groups DIE_GRP by balancing the number of free over-provisioning blocks respectively included in the M memory die groups DIE_GRP.

[0144] In this case, the second over-provisioning block group may include over-provisioning blocks of memory dies included in the second memory die group DIE_GRP_2 among the M memory die groups DIE_GRP. Figure 8 This is described in detail.

[0145] On the other hand, when the number of free over-provisioning blocks included in the first over-provisioning block group OP_BLK_GRP_1 is greater than the threshold free block number (S720-N), the controller 120 may maintain the user data USR_DATA stored in the first over-provisioning block group OP_BLK_GRP_1 (S740).

[0146] Figure 8 FIG. 2 shows an operation of the storage device 100 according to an embodiment of the present disclosure to migrate a portion of the user data USR_DATA stored in the first over-provisioning block group OP_BLK_GRP_1. Figure 3 The storage device 100 is shown to describe Figure 8 The operations shown in .

[0147] Reference Figure 8, the controller 120 of the storage device 100 may migrate a portion of the user data USR_DATA stored in the first over-provisioning block group OP_BLK_GRP_1 to the second over-provisioning block group OP_BLK_GRP_2. The second over-provisioning block group OP_BLK_GRP_2 may include over-provisioning blocks of the memory dies included in the second memory die group DIE_GRP_2 among the M memory die groups DIE_GRP.

[0148] On the other hand, the controller 120 may generate a process for migrating a portion of the user data USR_DATA stored in the first over-provisioning block group OP_BLK_GRP_1 to the second over-provisioning block group OP_BLK_GRP_2. For example, this process may be executed at a host interface layer (HIL).

[0149] Therefore, among the reserved space blocks included in the first reserved space block group OP_BLK_GRP_1, the reserved space blocks in which the stored user data has been migrated to the second reserved space block group OP_BLK_GRP_2 may be erased and converted into free reserved space blocks. Therefore, the number of free reserved space blocks included in the first reserved space block group OP_BLK_GRP_1 may increase.

[0150] On the other hand, the controller 120 may determine the portion of the user data USR_DATA to be migrated from the first over-provisioned space group OP_BLK_GRP_1 to the second over-provisioned space block group OP_BLK_GRP_2 in various ways.

[0151] For example, among the user data stored in the first over-reserved space block group OP_BLK_GRP_1, the controller 120 may migrate only a portion of the user data USR_DATA stored in one over-reserved space block to the second over-reserved space block group OP_BLK_GRP_2. After the portion of the user data USR_DATA is migrated to the second over-reserved space block group OP_BLK_GRP_2 and one over-reserved space block to which the portion of the user data USR_DATA has been migrated is erased, the controller 120 may again determine whether the number of free over-reserved space blocks included in the first over-reserved space block group OP_BLK_GRP_1 is less than or equal to a threshold number of free blocks.

[0152] As another example, the controller 120 may migrate a portion of the user data USR_DATA from the first over-provisioning block group OP_BLK_GRP_1 to the second over-provisioning block group OP_BLK_GRP_2 until the number of free over-provisioning blocks included in the first over-provisioning block group OP_BLK_GRP_1 is equal to or greater than a threshold free block number.

[0153] On the other hand, the storage device 100 may record information about the portion of the user data USR_DATA migrated from the first over-provisioning block group OP_BLK_GRP_1 to the second over-provisioning block group OP_BLK_GRP_2 by using a separate data structure. Fig. 9 This is described in detail.

[0154] Fig. 9 FIG. 2 shows an operation of the storage device 100 managing the remapping table REMAP_TBL according to an embodiment of the present disclosure. Figure 3 The storage device 100 is shown to describe Fig. 9 The operations shown in .

[0155] Reference Fig. 9 , among the user data USR_DATA stored in the first over-reserved space block group OP_BLK_GRP_1 included in the first memory die group DIE_GRP_1, the first part and the second part corresponding to the first logical address LA1 and the second logical address LA2, respectively, are migrated to the second over-reserved space block group OP_BLK_GRP_2 included in the second memory die group DIE_GRP_2.

[0156] At this time, the controller 120 of the storage device 100 may record information about the first and second parts of the user data USR_DATA migrated from the first over-provisioning block group OP_BLK_GRP_1 to the second over-provisioning block group OP_BLK_GRP_2 in the remapping table REMAP_TBL.

[0157] exist Fig. 9 , the remapping table REMAP_TABLE may indicate that a first portion of the user data USR_DATA corresponding to the first logical address LA1 is migrated from the first memory die group DIE_GRP_1 to the second memory die group DIE_GRP_2, and may indicate that a second portion of the user data USR_DATA corresponding to the second logical address LA2 is migrated from the first memory die group DIE_GRP_1 to the second memory die group DIE_GRP_2.

[0158] Fig.10 An operating method of the storage device 100 according to an embodiment of the present disclosure is shown.

[0159] Reference Fig.10The operating method of the memory device 100 may include grouping a plurality of memory die DIEs into M (M is a natural number of 2 or greater) memory die groups DIE_GRP (S1010), wherein each memory die DIE includes a plurality of user data blocks USR_BLK and a plurality of over-reserved space blocks OP_BLK.

[0160] The operating method of the memory device 100 may further include determining that a first memory die DIE_1 included in a first memory die group DIE_GRP_1 among the M memory die groups DIE_GRP is in an unusable state ( S1020 ).

[0161] For example, when the number of bad blocks included in the first memory die DIE_1 is greater than or equal to a threshold bad block number, operation S1020 may determine that the first memory die DIE_1 is in an unusable state.

[0162] The operating method of the memory device 100 may further include migrating user data USR_DATA stored in the user data block of the first memory die DIE_1 to the first over-provisioning block group OP_BLK_GRP_1 ( S1030 ).

[0163] The first over-provisioning block group OP_BLK_GRP_1 may include over-provisioning blocks of memory dies except the first memory die DIE_1 among the memory dies included in the first memory die group DIE_GRP_1.

[0164] On the other hand, the operation method of the storage device 100 may further include: i) determining the number of free over-reserved space blocks included in the first over-reserved space block group OP_BLK_GRP_1; and ii) when the number of free over-reserved space blocks included in the first over-reserved space block group OP_BLK_GRP_1 is less than or equal to the threshold number of free blocks, migrating a portion of the user data USR_DATA stored in the first over-reserved space block group OP_BLK_GRP_1 to the second over-reserved space block group OP_BLK_GRP_2. The second over-reserved space block group OP_BLK_GRP_2 may include over-reserved space blocks of the memory die included in the second memory die group DIE_GRP_2 among the M memory die groups DIE_GRP.

[0165] For example, the threshold number of free blocks may be determined as a value obtained by subtracting a deviation from an average value of the numbers of free over-provisioning blocks respectively included in the M memory die groups.

[0166] On the other hand, the operating method of the storage device 100 may further include recording information about a portion of the user data USR_DATA migrated from the first over-provisioning block group OP_BLK_GRP_1 to the second over-provisioning block group OP_BLK_GRP_2 in the remapping table REMAP_TBL.

[0167] Fig.11 FIG. 2 shows an operation of the storage device 100 migrating a portion of the user data USR_DATA according to an embodiment of the present disclosure. Figure 3 The storage device 100 is shown to describe Fig.11 The operations shown in .

[0168] As described above, the controller 120 of the storage device 100 may determine that the first memory die DIE_1 included in the first memory die group DIE_GRP_1 is in an unavailable state. The controller 120 may migrate the user data USR_DATA stored in the first memory die DIE_1 to the first memory block group BLK_GRP_1. The first memory block group BLK_GRP_1 may include one or more memory blocks BLK included in the first memory die group DIE_GRP_1. For example, the first memory block group BLK_GRP_1 may be the above-mentioned first over-reserved space block group OP_BLK_GRP_1.

[0169] The controller 120 may determine whether to migrate a portion of the user data USR_DATA stored in the first memory block group BLK_GRP_1 to the second memory block group BLK_GRP_2. The second memory block group BLK_GRP_2 may include one or more memory blocks BLK included in the second memory die group DIE_GRP_2. For example, the second memory block group BLK_GRP_2 may be the second over-provisioning block group OP_BLK_GRP_2.

[0170] The first memory die group DIE_GRP_1 and the second memory die group DIE_GRP_2 are included in the above-mentioned M memory die groups DIE_GRP.

[0171] For example, when the number of free memory blocks included in the first memory block group BLK_GRP_1 is less than or equal to the threshold number of free blocks, the controller 120 may determine to migrate a portion of the user data USR_DATA stored in the first memory block group BLK_GRP_1 to the second memory block group BLK_GRP_2. The controller 120 may determine the threshold number of free blocks based on an average value of the number of free memory blocks respectively included in the M memory core groups BLK_GRP.

[0172] Fig.12FIG. 1 shows an operation of the storage device 100 migrating a portion of the user data USR_DATA according to another embodiment of the present disclosure. Figure 3 The storage device 100 is shown to describe Fig.12 The operations shown in .

[0173] As described above, the controller 120 of the memory device 100 may determine that the first memory die DIE_1 included in the first memory die group DIE_GRP_1 is in an unavailable state. In this case, the controller 120 may migrate user data corresponding to the target logical address TGT_LA among user data USR_DATA stored in the first memory die DIE_1 to the second memory die group DIE_GRP_2.

[0174] The first memory die group DIE_GRP_1 and the second memory die group DIE_GRP_2 are included in the above-mentioned M memory die groups DIE_GRP.

[0175] As described above, the controller 120 may generate FTL instances FTL_INST corresponding to the M memory die groups DIE_GRP, respectively. Fig.12 , the controller 120 may generate a first FTL instance FTL_INST_1 corresponding to the first memory die group DIE_GRP_1 and a second FTL instance FLT_INST_2 corresponding to the second memory die group DIE_GRP_2.

[0176] The controller 120 may migrate the user data corresponding to the target logical address TGT_LA to the second memory die group DIE_GRP_2 and control the user data corresponding to the target logical address TGT_LA using the second FTL instance FTL_INST_2 corresponding to the second memory die group DIE_GRP_2.

[0177] Although the exemplary embodiments of the present disclosure have been described for illustrative purposes, it will be understood by those skilled in the art that various modifications, additions and substitutions may be made without departing from the scope and spirit of the disclosure. Therefore, the embodiments disclosed above and in the accompanying drawings are considered to be illustrative only and are not intended to limit the technical scope. The technical scope of the present disclosure is not limited by the embodiments and the accompanying drawings. The spirit and scope of the present disclosure should be interpreted in conjunction with the attached claims, and include all equivalent schemes that fall within the scope of the attached claims.

Claims

1. A storage device, comprising: A memory, comprising a plurality of memory dies, each memory die comprising a plurality of user data blocks and a plurality of reserved space blocks; as well as A controller, the controller: grouping the plurality of memory dies into M memory die groups, and When a first memory die in a first memory die group among the M memory die groups is determined to be in an unavailable state, migrating user data stored in a user data block of the first memory die to a first over-provisioning block group, wherein the first over-provisioning block group includes over-provisioning blocks of memory dies other than the first memory die among the memory dies in the first memory die group, and M is a natural number of 2 or greater.

2. The storage device according to claim 1, wherein: The controller further: When the number of bad blocks in the first memory die is greater than or equal to a threshold number of bad blocks, it is determined that the first memory die is in an unusable state.

3. The storage device according to claim 1, wherein: The controller further: When a ratio of failures occurring in read operations performed on the first memory die within a predetermined period of time is greater than or equal to a threshold ratio, it is determined that the first memory die is in an unusable state.

4. The storage device according to claim 1, wherein: The controller further: When migrating the user data to the first reserved space block group, the user data is corrected based on the parity bits of the user data.

5. The storage device according to claim 1, wherein: The controller further: After migrating the user data to the first reserved space block group, when the number of free reserved space blocks in the first reserved space block group is less than or equal to a threshold number of free blocks, migrating a portion of the user data stored in the first reserved space block group to a second reserved space block group, The second over-provisioning block group includes over-provisioning blocks of memory dies in a second memory die group among the M memory die groups.

6. The storage device according to claim 5, wherein: The controller further: The threshold number of free blocks is determined as a value obtained by subtracting a deviation from an average value of the numbers of free over-provisioning blocks respectively included in the M memory die groups.

7. The storage device according to claim 6, wherein: The deviation is a value set based on a standard deviation of the numbers of free over-provisioning blocks respectively included in the M memory die groups.

8. The storage device according to claim 5, wherein: The controller further: Information about the portion of the user data that is migrated from the first reserved space block group to the second reserved space block group is recorded in a remapping table.

9. A storage device, comprising: A memory, the memory comprising a plurality of memory dies, each memory die comprising a plurality of memory blocks; as well as A controller, the controller: grouping the plurality of memory dies into M memory die groups, determining that a first memory die included in a first memory die group among the M memory die groups is in an unusable state, migrating user data stored in the first memory die to a first memory block group, the first memory block group including one or more memory blocks included in the first memory die group, and determining whether to migrate a portion of the user data stored in the first memory die group to a second memory block group, the second memory block group including one or more memory blocks included in a second memory die group among the M memory die groups, Wherein M is a natural number of 2 or greater.

10. The storage device according to claim 9, wherein: The controller further: When the number of free memory blocks in the first memory block group is less than or equal to a threshold number of free blocks, it is determined to migrate the portion of the user data stored in the first memory die group to the second memory block group.

11. The storage device according to claim 10, wherein: The controller further: The threshold number of free blocks is determined based on an average value of numbers of free memory blocks respectively included in the M memory die groups.

12. A storage device, comprising: A memory, the memory comprising a plurality of memory dies, each memory die comprising a plurality of memory blocks; as well as A controller, the controller: grouping the plurality of memory dies into M memory die groups, determining that a first memory die in a first memory die group among the M memory die groups is in an unusable state, Migrating data corresponding to a target logical address among user data stored in the first memory die to a second memory die group among the M memory die groups, and The data corresponding to the target logical address is controlled using a flash translation layer instance (FTL instance) corresponding to the second memory die group, where M is a natural number of 2 or greater.