Patent Description:
A flash memory, which is a non-volatile memory, may retain stored data even when power is cut off. Recently, a storage device including the flash memory such as an embedded multi-media card (eMMC), universal flash storage (UFS), solid state drive (SSD), and a memory card has been widely used for storing or moving a large amount of data. There is a continuing need for methods and devices that may improve the reliability of the storage device.

<CIT> discloses: A memory system includes a plurality of memory blocks, first and second queues, and a controller suitable for queuing first victim blocks whose error information value is equal to or greater than a threshold value among the memory blocks in the first queue, queuing second victim blocks whose read count is equal to or greater than a threshold value in the second queue, rearranging a priority order of the first and second victim blocks queued in the first and second queues based on read reclaim values, and performing a read reclaim operation on the first and second victim blocks based on the priority order.

<CIT> discloses: Methods of operating nonvolatile memory devices include counting a number of consecutive read operations performed on a first memory region within the nonvolatile memory device, and executing a page reclaim operation on the first memory region in response to detecting that a count in the number of consecutive read operations meets or exceeds a threshold count. A page reclaim operation may include checking an error bit level within a page of data stored in a multi-level cell block within the memory device. The page reclaim operation may further include moving page data from the multi-level cell block to a single-level cell block in the memory device and error correcting the page data during the moving.

The inventive concept provides a memory device capable of improving the reliability of a storage device, a storage device including the memory device, and an operating method of the storage device. The invention is defined in the appended independent claims. Further developments of the invention are specified in the dependent claims.

According to an exemplary embodiment of the present invention, an operating method of a storage device includes detecting whether a reclaim event has occurred on a source memory area including a plurality of memory areas, setting a reclaim priority value to each of the plurality of memory areas, and performing a reclaim operation on the source memory area according to the reclaim priority value of each of the plurality of memory areas. The reclaim operation moves data stored in the source memory area to a destination memory area, wherein the setting of the reclaim priority value comprises setting, in response to detecting of the reclaim event having occurred to a first memory area among the plurality of memory areas, a first reclaim priority value to the first memory area; setting, in response to detecting of the reclaim event being expected to occur to a second memory area among the plurality of memory areas based on degradation information stored in a metadata buffer of the storage device, a second reclaim priority value to the second memory area; and setting, in response to detecting of the reclaim event not having occurred to a third memory area and detecting of the reclaim event not being expected to occur to the third memory area, a third reclaim priority value to the third memory area.

According to an exemplary embodiment of the present invention, a storage device includes a nonvolatile memory device, and a controller operatively coupled to the nonvolatile memory device and configured to detect whether a reclaim event has occurred on a source memory area of the nonvolatile memory device, wherein the source memory area including a plurality of memory areas, set a reclaim priority value to each of the plurality of memory areas, and perform a reclaim operation on the source memory area based on the reclaim priority value of each of the plurality of memory areas, wherein the reclaim operation moves data stored in the source memory area to a destination memory area, wherein the setting of the reclaim priority value comprises setting, in response to detecting of the reclaim event having occurred to a first memory area among the plurality of memory areas, a first reclaim priority value to the first memory area; setting, in response to detecting of the reclaim event being expected to occur to a second memory area among the plurality of memory areas based on degradation information stored in a metadata buffer of the storage device, a second reclaim priority value to the second memory area; and setting, in response to detecting of the reclaim event not having occurred to a third memory area and detecting of the reclaim event not being expected to occur to the third memory area, a third reclaim priority value to the third memory area.

<FIG> is a block diagram illustrating a storage system <NUM> according to an embodiment.

The storage system <NUM> may be implemented as, for example, a personal computer (PC), a data server, a network-attached storage (NAS), an Internet of Things (IoT) device, or a portable electronic device. The portable electronic device may include a laptop computer, a mobile phone, a smartphone, a tablet PC, a personal digital assistant (PDA), an enterprise digital assistant (EDA), a digital still camera, a digital video camera, an audio device, a portable multimedia player (PMP), a personal navigation device (PND), an MP3 player, a handheld game console, an e-book, a wearable device, etc..

The storage system <NUM> may include a storage device <NUM> and a host <NUM>. The host <NUM> may control the operation of the storage device <NUM>. In an embodiment, the storage device <NUM> may include one or more solid state drives (SSDs). When the storage device <NUM> includes SSDs, the storage device <NUM> may include a plurality of flash memory devices (e.g., NAND memory devices) that store data.

The storage device <NUM> may include one or more flash memory devices. In an embodiment, the storage device <NUM> may be an embedded memory embedded in the storage system <NUM>. For example, the storage device <NUM> may be an embedded Multi-Media Card (eMMC) or an embedded Universal Flash Storage (UFS) memory device. In an embodiment, the storage device <NUM> may be an external memory detachable from the storage system <NUM>. For example, the storage device <NUM> may be a UFS memory card, a Compact Flash (CF) card, a Secure Digital (SD) card, a Micro Secure Digital (Micro-SD) card, a Mini Secure Digital (Mini-SD) card, extreme Digital (xD), or a memory stick.

Referring to <FIG>, the storage system <NUM> may include the storage device <NUM> and the host <NUM>, and the storage device <NUM> may include a controller <NUM> and a nonvolatile memory <NUM>. The host <NUM> may communicate with the storage device <NUM> through various interfaces, and may transfer a request REQ, such as a read request and a program request, to the storage device <NUM>. In an embodiment, the host <NUM> may be implemented as an application processor (AP) or a system-on-a-chip (SoC).

The controller <NUM> may control the operation of the nonvolatile memory <NUM> through channels CH1~CHn. The controller <NUM> may control the nonvolatile memory <NUM> to read data DATA stored in the nonvolatile memory <NUM> in response to a read request of the host <NUM>, or to program the data DATA to the nonvolatile memory <NUM> in response to a write request of the host <NUM>.

When a reclaim event has occurred, the controller <NUM> may perform a reclaim operation by controlling the nonvolatile memory <NUM>. At this time, the "reclaim operation" refers to an operation of moving data in a source memory area to a destination memory area and reusing the source memory area by erasing the data of the source memory area. Specifically, in the reclaim operation, the controller <NUM> may read valid data stored in the source memory area, and program the read valid data to the destination memory area. Accordingly, an address corresponding to the valid data in a mapping table may be changed from the source memory area to the destination memory area. In an example embodiment, the source memory area may correspond to a memory block having at least one page on which a reclaim event has occurred, and the destination memory area may correspond a free block to store valid data moved from the source memory. The present invention is not limited thereto. In an example embodiment, the source memory area may correspond to part of a memory block, and the destination memory area may correspond to part of a free block. The memory block may be a unit of an erase operation.

In an embodiment, the controller <NUM> may include a reclaim scheduler <NUM>. The reclaim scheduler <NUM> may set a reclaim priority value of a memory area that is a target of the reclaim operation, and may set an order of memory areas in which the reclaim operation is performed according to the set priority value. The reclaim scheduler <NUM> may schedule the reclaim operation to be performed by priority as the priority value corresponding to the memory area registered in a reclaim queue (e.g., RQ of <FIG>) increases. In an embodiment, the reclaim scheduler <NUM> may set reclaim priority values of reclaim operations of a plurality of pages (e.g., PG1 to PGm of <FIG>) included in a source memory block (e.g., one of BLK1 to BLKn in <FIG>) that is the target of the reclaim operation.

In an embodiment, the reclaim scheduler <NUM> may set the priority of a first value (i.e., a first reclaim priority value) with respect to a memory area where the reclaim event has occurred, set the priority of a second value (i.e., a second reclaim priority value) with respect to a memory area where the reclaim event is expected to occur, and set the priority of a third value (i.e., a third reclaim priority value) with respect to other memory areas. The memory area where the reclaim event is expected to occur may be a previously designated memory area having low data reliability due to a physical structure of the memory area. The previously designate memory area will be described with reference to <FIG> and <FIG>. In a reclaim operation, the first value may be more prioritized than the second value, and the second value may be more prioritized than the third value, but the inventive concept is not limited thereto, and the second value may be more prioritized than the first value, and the first value may be more prioritized than the third value. As the priority value increases, the reclaim operation may be performed earlier on a memory area with a higher value. In an example embodiment, a memory area having the first value may be more prioritized than a memory area having the second and third values in a reclaim operation. In the reclaim operation, data of the memory area having the first value may be firstly moved to a destination area, and data of the memory areas having the second and third values may be later moved to the destination area. Among the memory areas having the second and third values, data of the memory area having the second value is moved to the destination area, and then data of the memory area having the third value is moved to the destination area.

In an embodiment, the nonvolatile memory <NUM> may include a plurality of memory devices NVM1 to NVMi that store data. Each of the plurality of memory devices NVM1 to NV Mi may be a semiconductor chip or a semiconductor die Each of the plurality of memory devices NVM1 to NVMi may be connected to a corresponding channel. For example, the nonvolatile memory <NUM> may include the memory devices NVM1 connected to the controller <NUM> through the first channel CH1, the memory devices NVM2 connected to the controller <NUM> through the second channel CH2, and the memory devices NVMi connected to the controller <NUM> through an i-th channel CHi. At this time, i may be an integer of <NUM> or more. Among the plurality of memory devices NVM1 to NVMi, a group of memory devices connected to the same channel may perform program, read, and erase operations in an interleaving manner.

Each of the plurality of memory devices NVM1 to NVMi may include a memory cell array (e.g., <NUM> of <FIG>). In an embodiment, the memory cell array <NUM> may include flash memory cells. For example, the flash memory cells may be NAND flash memory cells. However, the inventive concept is not limited thereto, and the memory cells may be resistive memory cells, such as resistive RAM (ReRAM) cells, phase-change RAM (PRAM) cells, or magnetic RAM (MRAM) cells.

The storage device <NUM> according to the inventive concept may set a reclaim priority of memory areas that are the target of the reclaim operation in advance, and perform the reclaim operation according to the reclaim priority. The storage device <NUM> may preferentially perform the reclaim operation on the source memory area where the reclaim event has occurred, thereby preventing the reclaim operation on the source memory area from being excessively delayed, even when the request REQ is received from the host <NUM>.

<FIG> is a block diagram illustrating in detail the controller <NUM> included in the storage device <NUM> of <FIG>.

Referring to <FIG> and <FIG>, the controller <NUM> may include a processor <NUM>, a host interface <NUM>, a memory <NUM>, the reclaim scheduler <NUM>, and a nonvolatile memory interface <NUM>, which may communicate with each other via a bus <NUM>. The processor <NUM> may include a central processing unit or a microprocessor, and control all operations of the controller <NUM>. The processor <NUM> may include one or more processor cores capable of executing an instruction set of program code configured to perform a specific operation. For example, the processor <NUM> may execute command code of firmware stored in the memory <NUM>.

The reclaim scheduler <NUM> may set the priority of the reclaim operation of the memory areas that are the target of the reclaim operation, and schedule the reclaim operation to be performed according to a reclaim priority. The reclaim scheduler <NUM> may be implemented with hardware, software or firmware. When the reclaim scheduler <NUM> is implemented with software or firmware, the reclaim scheduler <NUM> may be loaded into the memory <NUM> and operate under the control of the processor <NUM>. The memory <NUM> may be used as an operation memory, a buffer memory, a cache memory, etc., and, for example, implemented as a dynamic random access memory (DRAM), a static random access memory (SRAM), a phase change memory (PRAM) or a flash memory.

A command queue CQ may be implemented as part of the memory <NUM>. Commands according to the request REQ received from the host <NUM> may be enqueued in the command queue CQ. For example, when a write request is received, a write command corresponding to the write request may be enqueued in the command queue CQ, and when a read request is received, a read command corresponding to the read request may be enqueued in the command queue CQ.

A reclaim queue RQ may be implemented as part of the memory <NUM>. In the reclaim queue RQ, information about a memory area where a reclaim event has occurred may be stored, and information about a reclaim priority of the memory area that is a target of the reclaim operation may be stored. That is, in the reclaim queue RQ, an address of the source memory area may be registered, and a value of the reclaim priority corresponding thereto may be stored. For example, the reclaim queue RQ may store priority values indicating the reclaim priority of each of pages in a memory block. Alternatively, for example, the reclaim queue RQ may store priority values indicating the reclaim priority of each of memory blocks.

A metadata buffer MB may be implemented as part of the memory <NUM> or a separate DRAM chip. Metadata stored in the metadata buffer MB may be stored in a meta area of the nonvolatile memory <NUM>, and when power is applied to the storage device <NUM>, may be loaded into the metadata buffer MB in the nonvolatile memory <NUM>.

Degradation information with respect to the memory area of the nonvolatile memory <NUM> may be stored in the metadata buffer MB as the metadata. In an embodiment, the degradation information may be stored for each memory block or for each page. For example, the degradation information indicating a memory area where the reclaim event is expected to occur may be stored in the metadata buffer MB. For example, the degradation information such as indicating a memory area with low data reliability due to a physical structure of the memory area, or indicating a memory area with an erasure count of an erase operation being greater than a reference value may be stored in the metadata buffer MB. The erasure count refers to a number of how many times an erase operation is performed on the memory area. For example, the degradation information may include row addresses of the memory area with the low data reliability or row addresses of the memory array with the erasure count being greater than the reference value. The reclaim scheduler <NUM> may set the reclaim priority of the memory area that is the target of the reclaim operation based on the degradation information stored in the metadata buffer MB.

The host interface <NUM> may provide an interface between the host <NUM> and the controller <NUM>. For example, the host interface <NUM> may provide the interface that is based on a universal serial bus (USB), a multimedia card (MMC), peripheral component interconnect-express (PCI-E), advanced technology attachment (ATA), serial ATA (SATA), parallel-ATA (PATA), a small computer system interface (SCSI), a serial attached SCSI (SAS), an enhanced small device interface (ESDI), and an intelligent drive electronics (IDE) The nonvolatile memory interface <NUM> may provide an interface between the controller <NUM> and the nonvolatile memory <NUM>. For example, the degradation information, the mapping table, the write data, and the read data may be transmitted and received between the controller <NUM> and the nonvolatile memory <NUM> through the nonvolatile memory interface <NUM>.

<FIG> is a flowchart illustrating an operating method of the storage device <NUM> according to an embodiment. The operation method of operations S10 to S30 illustrated in <FIG> may be performed by the storage device <NUM> of <FIG> time-serially.

Referring to <FIG> and <FIG>, in operation S10, the storage device <NUM> may detect the occurrence of a reclaim event. In an embodiment, the storage device <NUM> may read data in a specific memory area and may determine that a reclaim event has occurred when an error bit rate (EBR) of the data is greater than or equal to a reference value. Alternatively, in an embodiment, the storage device <NUM> may execute a recovery code by firmware when a read operation on the specific memory area fails, and determine, in response to when a specific defense code of the recovery code, which are implemented in the firmware, that the reclaim event has occurred in the specific memory area. An algorithm called "defense code" may be implemented in the controller <NUM> of <FIG> to correct or recover read errors. The defense code as the recovery code that copes with the read errors that have already occurred may be implemented in firmware. In an example embodiment, the recovery code may allow a read operation (i.e., a read retry operation) to be repeated using a varying read reference voltage until error correction is completed.

For example, when receiving a read request from the host <NUM>, the storage device <NUM> may read the data DATA from a specific memory area of the nonvolatile memory <NUM> through a host read operation, and determine whether to perform the reclaim operation based on the read data DATA. A detailed example of a method of determining whether to perform the reclaim operation through the host read operation will be described in operation S10 of <FIG> later.

Alternatively, for example, the storage device <NUM> may read data from the specific memory area of the nonvolatile memory <NUM> through a background read operation, and determine whether to perform the reclaim operation based on the read data. The "background read operation" refers to an operation of reading data from the nonvolatile memory <NUM> by issuing a read command by the controller <NUM> itself without receiving a read request from the host <NUM>. A detailed example of a method of determining whether to perform the reclaim operation through the background read operation will be described in operations S10a to S10d of <FIG> later.

In operation S20, the storage device <NUM> may set a reclaim priority of a reclaim operation target. For example, in operation S10, a reclaim priority value may be set to the memory area where the reclaim event has occurred such that the reclaim operation may be performed first, and a reclaim priority value of a posterior order may be set to a memory area where no reclaim event has occurred but which is the reclaim operation target.

In operation S30, the storage device <NUM> may perform the reclaim operation according to the set reclaim priority. For example, in operation S10, the storage device <NUM> may perform the reclaim operation on the memory area where the reclaim event has occurred first, and then subsequently may perform the reclaim operation on the memory area where no reclaim event has occurred but which is the reclaim operation target.

The storage device <NUM> according to the inventive concept may set a priority value of the reclaim operation on the memory area in advance, and perform the reclaim operation according to the set priority value. Accordingly, even when the request REQ is received from the host <NUM>, the storage device <NUM> may prevent the reclaim operation on the memory area where the reclaim event has occurred from being excessively delayed. Data reliability of the nonvolatile memory <NUM> and the storage device <NUM> may be improved.

<FIG> is a block diagram illustrating a memory device 120A included in the nonvolatile memory <NUM> of <FIG>.

Referring to <FIG> and <FIG>, the memory device 120A may include a memory cell array <NUM>, an address decoder <NUM>, a control logic block <NUM>, a page buffer <NUM>, an input/output circuit <NUM>, and a voltage generator <NUM>. Although not shown, the memory device 120A may further include an input/output interface.

The memory cell array <NUM> may be connected to word lines WL, string selection lines SSL, ground selection lines GSL, and bit lines BL. The memory cell array <NUM> may be connected to the address decoder <NUM> through the word lines WL, the string selection lines SSL and the ground selection lines GSL, and may be connected to the page buffer <NUM> through the bit lines BL. The memory cell array <NUM> may include a plurality of memory blocks BLK1 to BLKn.

Each of the memory blocks BLK1 to BLKn may include a plurality of memory cells and a plurality of selection transistors. The memory cells may be connected to the word lines WL, and the selection transistors may be connected to the string selection lines SSL or the ground selection lines GSL. The memory cells of each of the memory blocks BLK1 to BLKn may include single-level cells storing <NUM>-bit data or multi-level cells storing <NUM>-bit or more data.

Each of the plurality of memory blocks BLK1 to BLKn may include a plurality of pages PG1 to PGm. Each of the pages PG1 to PGm may correspond to a program or read unit of data in one memory block. In an embodiment, memory cells included in each of the pages PG1 to PGm may be connected to the same word line.

The address decoder <NUM> may select one of the plurality of memory blocks BLK1 to BLKn of the memory cell array <NUM>, may select one of the word lines WL of the selected memory block, and may select one of the plurality of string selection lines SSL.

The control logic block <NUM> (or a control logic circuit) may output various control signals for performing the program, read, and erase operations on the memory cell array <NUM> based on a command ICMD, an address ADDR, and a control signal CTRL. The control logic block <NUM> may provide a row address X-ADDR to the address decoder <NUM>, provide a column address Y-ADDR to the page buffer <NUM>, and provide a voltage control signal CTRL_Vol to the voltage generator <NUM>.

The control logic block <NUM> may perform an erase operation in units of each of the plurality of memory blocks BLK1 to BLKn. The control logic block <NUM> may perform a read operation or a program operation in units of each of the plurality of pages PG1 to PGm.

In an embodiment, the control logic block <NUM> may perform a reclaim operation in units of each of the plurality of memory blocks BLK1 to BLKn. For example, the control logic block <NUM> may perform the reclaim operation by reading data in units of pages included in the second memory block BLK2, which is a source memory block where a reclaim event has occurred among the plurality of memory blocks BLK1 to BLKn, programming data in units of pages to a destination memory block among the plurality of memory blocks BLK1 to BLKn, and erasing the second memory block BLK2.

In an embodiment, the control logic block <NUM> may preferentially perform the reclaim operation on the second page PG2, the fourth page PG4, and an (m-<NUM>)th page PG(m-<NUM>)th where the reclaim event has occurred when performing the reclaim operation on the second memory block BLK2. Therefore, the control logic block <NUM> may not perform the reclaim operation on the second memory block BLK2 in the order of the row address X-ADDR. For example, when performing the reclaim operation on the second memory block BLK2, the control logic block <NUM> may preferentially perform the reclaim operation on the second page PG2, the fourth page PG4, and an (m-<NUM>)th page PG(m-<NUM>)th, and then perform the reclaim operation on the remaining pages in the order of bottom to top from the first page PG1 to an mth page PGm of the second memory block BLK2 or in the order of top to bottom from the mth page PGm to the first page PG1.

The page buffer <NUM> may operate as a write driver or a sense amplifier depending on an operation mode. During the read operation, the page buffer <NUM> may sense the bit line BL of the selected memory cell under the control of the control logic block <NUM>. The sensed data may be stored in latches provided inside the page buffer <NUM>. The page buffer <NUM> may dump the data stored in the latches to the input/output circuit <NUM> under the control of the control logic block <NUM>.

The input/output circuit <NUM> may temporarily store the command ICMD, the addresses ADDR, the control signal CTRL, and data DATA that are provided through an input/output line I/O from the outside of the memory device 120A. The input/output circuit <NUM> may temporarily store read data of the memory device 120A and output the read data to the outside through the input/output line I/O at a designated time.

The voltage generator <NUM> may generate various types of voltages for performing program, read, and erase operations on the memory cell array <NUM> based on the voltage control signal CTRL_Vol. Specifically, the voltage generator <NUM> may generate a word line voltage VWL, a program voltage, a read voltage, a pass voltage, an erase verification voltage, or a program verification voltage, for example. Also, the voltage generator <NUM> may generate a string selection line voltage and a ground selection line voltage based on the voltage control signal CTRL_Vol. Also, the voltage generator <NUM> may generate an erase voltage to be provided to the memory cell array <NUM>.

<FIG> is an equivalent circuit diagram of a memory block BLK included in the memory cell array <NUM> of the memory device 120A according to an embodiment. In <FIG>, the equivalent circuit diagram of a NAND flash memory device having a vertical channel structure formed on a substrate is illustrated.

Referring to <FIG>, the memory block BLK included in the memory cell array <NUM> may include a plurality of memory cell strings MS. The memory block BLK may include a plurality of bit lines BL (for example, BL1 to BLk), a plurality of word lines WL (for example, WL1 to WLn), a plurality of string selection lines SSL (for example, SSL1 to SSLk), and at least one ground selection line GSL, and a common source line CSL. A plurality of memory cell strings MS may be formed between the plurality of bit lines BL1 to BLk and the common source line CSL.

Each of the plurality of memory cell strings MS may include a string selection transistor SST, a ground selection transistor GST, and a plurality of memory cells MC1 to MCm. A drain area of the string selection transistor SST may be connected to the bit lines BL, and a source area of the ground selection transistor GST may be connected to the common source line CSL. The common source line CSL may be a area in which the source areas of the plurality of ground selection transistors GST are commonly connected.

In order to independently control the plurality of memory cell strings MS, the string selection transistors SST included in each of the plurality of memory cell strings MS may be connected to the different string selection lines SSL. For example, the string selection transistor SST may be connected to the string selection line (e.g., one of SSL1, SSL2, and SSL3).

The ground selection transistor GST may be connected to the ground selection line GSL. In an embodiment, the different ground selection transistors GST included in the plurality of memory cell strings MS of the memory block BLK may be connected to the same ground selection line GSL, but are not limited thereto and may be connected to different ground selection lines GSL.

The plurality of memory cells MC1 to MCm constituting the memory cell string MS in the memory block BLK may have a structure connected in series in the Z-axis direction perpendicular to a main surface of a substrate. In the memory block BLK, the plurality of word lines WL may extend in the X-axis direction, and the plurality of bit lines BL may extend in the Y-axis direction.

The memory cells MC1 to MCm of the memory cell string MS may be connected to the plurality of word lines WL, respectively. Each of the plurality of memory cells MC1 to MCm may store one bit of data or two or more bits of data. In an embodiment, some of the plurality of memory cells MC1 to MCm may be single-level cells, and the others of the plurality of memory cells MC1 to MCm may be multi-level cells. For example, the first memory cells MC1 among the plurality of memory cells MC1 to MCm formed on the lowermost layer and connected to the first word line WL1 may be single-level cells. Also, for example, the mth memory cells MCm among the plurality of memory cells MC1 to MCm formed on the uppermost layer among the plurality of memory cells MC1 to MCm and connected to the mth word line WLm may be single-level cells. Memory cells among the plurality of memory cells MC1 to MCm formed on the uppermost layer and the lowermost layer, for example, the first memory cells MC1 and the mth memory cells MCm may be formed as single-level cells, and thus the data reliability may be improved.

In the plurality of memory cell strings MS, program and read operations may be performed in units of pages. The page may be one row of memory cells connected to one word line. In an example embodiment, each of the plurality of memory cells MC1 to MCm may be selected in units of pages by a corresponding one of the plurality of word lines WL.

<FIG> and <FIG> are diagrams illustrating a reclaim operation of the storage device <NUM> according to an embodiment.

Referring to <FIG> and <FIG>, the second memory block BLK2 in which a reclaim event has occurred according to operation S10 of <FIG> may be registered in the reclaim queue RQ as a source block. Information about the second memory block BLK2 may be stored in the reclaim queue RQ. In an embodiment, a reclaim priority value may be stored in the reclaim queue RQ for each physical address of the plurality of pages PG1 to PGm included in the second memory block BLK2. For example, in the reclaim queue RQ, a reclaim priority of a first value PV1 corresponding to the fourth page PG4 may be set, and a reclaim priority of a second value PV2 corresponding to the (m-<NUM>)th page PG(m-<NUM>)th may be set, and a reclaim priority of a third value PV3 corresponding to the other pages may be set.

In an embodiment, the fourth page PG4 may be a target memory area where the reclaim event has occurred. In an embodiment, the (m-<NUM>)th page PG(m-<NUM>)th may be a memory area where the reclaim event is expected to occur.

The controller <NUM> may determine the order of reclaim operations of the plurality of pages PG1 to PGm included in the second memory block BLK2 based on the reclaim priority value stored in the reclaim queue RQ. For example, the first value PV1 may be greater than the second value PV2 and the second value PV2 may be greater than the third value PV3. The controller <NUM> may preferentially perform the reclaim operation on a memory area having a relatively large reclaim priority value. In <FIG>, the three different reclaim priority values PV1, PV2, and PV3 are described as an example, but this is for convenience of description, and the reclaim priority value may be variously set.

The controller <NUM> may read data from the fourth page PG4 of the second memory block BLK2 connected to the fourth word line WL4, and then move the read data to the first page PG1 of a destination block DB. Thereafter, the controller <NUM> may read data from the (m-<NUM>)th page PG(m-<NUM>)th of the second memory block BLK2 connected to the (m-<NUM>)th word line WL(m-<NUM>), and then move the read data to the second page PG2 of the destination block DB. The destination block DB may be one of free blocks excluding the second memory block BLK2 from the plurality of memory blocks BLK1 to BLKn.

The controller <NUM> may perform the reclaim operation on pages having the same reclaim priority value in the order of row address. For example, the reclaim operation may be sequentially performed in the order of the first page PG1 of the second memory block BLK2 connected to the first word line WL1, the second page PG2 of the second memory block BLK2 connected to the second word line WL2, the third page PG3 of the second memory block BLK2 connected to the third word line WL3, and the mth page PGm of the second memory block BLK2 connected to the mth word line WLm, and the data may be sequentially programmed in the third to mth pages PG3 to PGm of the destination block DB. However, the storage device <NUM> according to the inventive concept is not limited to programming the data in the destination block DB in the order of the row address of bottom to top. The storage device <NUM> may program the data in the destination block DB in the order of the row address of top to bottom.

Referring to <FIG> and <FIG>, the controller <NUM> may move data programmed in a multi-level cell where <NUM>-bit or more data of the second memory block BLK2, which is a source block, is stored to a single-level cell where <NUM>-bit data of the destination block DB is stored.

For example, the fourth page PG4 and the (m-<NUM>)th page PG(m-<NUM>)th of the second memory block BLK2 may include multi-level cells in which <NUM>-bit data is stored, while the first page PG1 and the second page PG2 of the destination block DB may include single-level cells in which <NUM>-bit data is stored, and the third page PG3 of the destination block DB may include a multi-level cell in which <NUM>-bit data is stored. The controller <NUM> may read the fourth page PG4 of the second memory block BLK2 connected to the fourth word line WL4, and then move the data to the first page PG1 and the second page PG2 of the destination block DB. Thereafter, the controller <NUM> may read the (m-<NUM>)th page PG(m-<NUM>)th of the second memory block BLK2 connected to the (m-<NUM>)th word line WL(m-<NUM>), and then move the data to the third page PG3 of the destination block DB. The above description may also be applied when data is moved from a triple level cell in which <NUM>-bit data is stored to a single level cell, or when data is moved from the triple level cell to a multi-level cell in which <NUM>-bit data is stored. To the contrary, the above description may be applied even when data is moved from a single-level cell to the multi-level cell in which <NUM>-bit or more data is stored.

<FIG> is a diagram illustrating a reclaim operation of the storage device <NUM> according to an embodiment.

Referring to <FIG> and <FIG>, the first memory block BLK1, the third memory block BLK3 and the nth memory block in which a reclaim event has occurred according to operation S10 of <FIG> may be respectively registered as first to third source blocks in the reclaim queue RQ. Physical addresses of the source blocks and reclaim priority values corresponding thereto may be stored in the reclaim queue RQ. For example, in the reclaim queue RQ, the reclaim priority value of the first value PV1 corresponding to the first memory block BLK1 may be set, the reclaim priority value of the second value PV2 corresponding to the nth memory block BLKn may be set, and the reclaim priority value of the third value PV3 corresponding to the third memory block BLK3 may be set.

The controller <NUM> may determine a priority of the reclaim operation between the memory blocks registered in the reclaim queue RQ based on the reclaim priority values stored in the reclaim queue RQ. For example, the first value PV1 may be greater than the second value PV2 and the second value PV2 may be greater than the third value PV3. The controller <NUM> may preferentially perform the reclaim operation on a memory area having a relatively large reclaim priority value.

The controller <NUM> may read data from the first memory block BLK1 as the first source block, move the data to the first destination block DB1, and then erase the first memory block BLK1. Next, the controller <NUM> may read data from the n-th memory block BLKn as the second source block, move the data to the second destination block DB2, and then erase the n-th memory block BLKn. Then, the controller <NUM> may read data from the third memory block BLK3 as the third source block, move the data to the third destination block DB3, and then erase the third memory block BLK3. The first to third destination blocks DB1 to DB3 may be included in free blocks excluding the first memory block BLK1, the third memory block BLK3, and the nth memory block BLKn from the plurality of memory blocks BLK1 to BLKn.

The description provided with reference to <FIG> and <FIG> may be applied to a reclaim operation order between the plurality of pages PG1 to PGm included in each of the first memory block BLK1, the third memory block BLK3, and the nth memory block BLKn when the controller <NUM> performs the reclaim operation on each of the first memory block BLK1, the third memory block BLK3, and the nth memory block BLKn. That is, among the plurality of pages PG1 to PGm included in each of the first memory block BLK1, the third memory block BLK3, and the nth memory block BLKn, the reclaim operation may be preferentially performed on a page in which a reclaim event has occurred. Alternatively, the reclaim operation on the plurality of pages PG1 to PGm included in each of the first memory block BLK1, the third memory block BLK3, and the nth memory block BLKn may be performed in the order of row address of bottom to top or in the order of row address of top to bottom.

<FIG> is a flowchart illustrating an operating method of the storage device <NUM> according to an embodiment, and is an example of operation S20 of <FIG>. Operation S20 may include operations S21 to S25.

Referring to <FIG> and <FIG>, in operation S21, the storage device <NUM> may set a reclaim priority value of a first value with respect to a first memory area where a reclaim event has occurred among reclaim operation targets. In an embodiment, the storage device <NUM> may determine that the reclaim event has occurred in the first memory area when an error bit rate of data read from the first memory area is equal to or greater than a reference value, or specific predetermined defense code is executed for a read retry with respect to the first memory area (to eliminate a data error). The error bit rate may mean a rate of error bits among the read data.

In operation S23, the storage device <NUM> may set a reclaim priority value of a second value with respect to a second memory area where the reclaim event is expected to occur among the reclaim operation targets. For example, even when the storage device <NUM> does not determine whether the reclaim event has occurred, the storage device <NUM> may set the reclaim priority value of the second value when the reclaim event is highly likely to occur. In an embodiment, the second memory area where the reclaim event is expected to occur may be a previously designated memory area, or a memory area with low data reliability due to a physical structure. A description of the memory area where the reclaim event is expected to occur is described later with respect to <FIG>, <FIG>.

In operation S25, the storage device <NUM> may set the reclaim priority value of the third value for the third memory area other than the target of the reclaim operation.

After performing operation S20, the storage device <NUM> may perform the reclaim operation on the first memory area, then the storage device <NUM> may perform the reclaim operation on the second memory area, and finally the storage device <NUM> may perform the reclaim operation on a third memory area having the third value. The storage device <NUM> according to the inventive concept may firstly perform the reclaim operation on the memory area where the reclaim event has occurred, and then perform the reclaim operation on the memory area where the reclaim event is expected to occur, thereby preventing data degradation.

<FIG> are diagrams illustrating operation S23 of <FIG>. <FIG> are diagrams illustrating a method of determining a memory area where a reclaim event is expected to occur among a plurality of pages included in a memory block.

Referring to <FIG>, it may be assumed that a read command CMD with respect to the second page PG2 of the memory block BLK2 is issued. At this time, the read command CMD may be issued due to a host read operation, or the read command CMD may be issued due to a background read operation.

A read voltage may be applied to the second word line WL2 connected to the second page PG2 to read the second page PG2. Accordingly, stress may be applied to each of the first word line WL1 and the third word line WL3, which are word lines adjacent to the second word line WL2, and data programmed in the first page PG1 and the third page PG3 respectively connected to the first word line WL1 and the third word line WL3 may be damaged. That is, a read disturb may occur on the first page PG1 and the third page PG3.

Accordingly, the first page PG1 and the third page PG3 connected to word lines adjacent to the second word line WL2 on which the read operation is performed may be separately managed as the memory area where the reclaim event is expected to occur by degradation information stored in the metadata buffer (e.g., MB in <FIG>). In <FIG>, only the first page PG1 and the third page PG3 respectively connected to the first word line WL1 and the third word line WL3 directly adjacent to the second word line WL2 are described but the inventive concept is not limited thereto. The fourth page PG4 connected to the fourth word line WL4 may also be determined as the memory area where the reclaim event is expected to occur.

Referring to <FIG> and <FIG>, when a memory device is implemented to include a NAND flash memory device having a vertical structure, the first to mth word lines WL1 to WLm may be formed to be sequentially stacked in the Z-axis direction with respect to a substrate. The first to m-th pages PG1 to PGm respectively connected to the first to m-th word lines WL1 to WLm may also be formed to be sequentially stacked with respect to the substrate.

The memory block BLK2 may include a bottom layer area BLA close to the substrate, a middle layer area MLA disposed on the bottom layer area BLA, and a top layer area TLA disposed on the middle layer area MLA. For example, the bottom layer area BLA may include the first page PG1 and the second page PG2, and the top layer area TLA may include the (m-<NUM>)th page PG(m-<NUM>)th and the mth page PGm, and the middle layer area MLA may include the remaining pages.

The pages included in the bottom layer area BLA, for example, the first page PG1 and the second page PG2, may have a structurally and relatively low data reliability compared to the middle layer area MLA. In addition, the pages included in the top layer area TLA, for example, the (m-<NUM>)th page PG(m-<NUM>)th and the m page PGm, may have a structurally relatively low data reliability compared to the middle layer area MLA. Accordingly, by the degradation information stored in the metadata buffer (e.g., MB of <FIG>), the pages included in the bottom layer area BLA may be managed as the memory area where the reclaim event is expected to occur, and the pages included in the top layer area TLA may be managed as the memory area where the reclaim event is expected to occur. In an example embodiment, the degradation information may include page addresses of the pages located in the bottom area BLA or page addresses of the pages located in the top layer area TLA. In an example embodiment, the controller <NUM> of <FIG> may treat the page addresses stored as the degradation information as a reclaim event being expected to occur, and check whether a reclaim event has occurred on the pages corresponding to the page addresses stored as the degradation information.

<FIG> are diagrams illustrating operation S23 of <FIG>. <FIG> are diagrams illustrating a method of determining a memory block where a reclaim event is expected to occur among a plurality of memory blocks.

Referring to <FIG> and <FIG>, a memory cell array area MCA and an address decoder area RDA may be arranged side by side in the X-axis direction. The memory cell array <NUM> may be disposed in the memory cell array area MCA, and the address decoder <NUM> may be disposed in the address decoder area RDA.

The memory cell array area MCA may include a center area CA disposed in the center and a first edge area EA1 and a second edge area EA2 disposed in upper and lower sides of the center area CA. A memory block disposed in the first edge area EA1 and the second edge area EA2 may have a structurally and relatively low data reliability compared to a memory block arranged in the center area CA. Therefore, the memory blocks disposed in the first edge area EA1 and the second edge area EA2 may be managed as the memory area where the reclaim event is expected to occur by degradation information stored in the metadata buffer (e.g., MB of <FIG>). In an example embodiment, the degradation information may include row addresses of the pages located in the first edge area EA1 and the second edge area EA2. In an example embodiment, the controller <NUM> of <FIG> may treat the page addresses stored as the degradation information as a reclaim event being expected to occur, and check whether a reclaim event has occurred on the pages corresponding to the page addresses stored as the degradation information.

Referring to <FIG>, degradation information MBLK1 to MBLKn of the plurality of memory blocks BLK1 to BLKn may be stored in the metadata buffer MB. For example, erasure counts EC1 to ECn of the plurality of memory blocks BLK1 to BLKn may be stored in the metadata buffer MB as the degradation information MBLK1 to MBLKn respectively.

As an erasure count increases, a degree of degradation of a corresponding memory block may increase. Memory blocks having an erasure count equal to or greater than a reference value may be separately managed as the memory areas where the reclaim event is expected to occur. The second memory block BLK2 having a high erasure count (e.g., the second erasure count EC2) may be separately managed as the memory area where the reclaim event is expected to occur by the degradation information MBLK1 to MBLKn stored in the metadata buffer MB.

<FIG> is a flowchart illustrating an operating method of the storage device <NUM> according to an embodiment, and is an example of operation S30 of <FIG>. Operation S30 may include operations S31 to S37. In an example embodiment, the operation S30 of <FIG> is part of a reclaim operation performed on the source memory area including the first memory area where a reclaim event has occurred.

Referring to <FIG> and <FIG>, in operation S31, the storage device <NUM> may perform a reclaim operation on a first memory area where a reclaim event has occurred. For example, the storage device <NUM> may perform the reclaim operation on the first memory area having a reclaim priority value of a first value. In operation S31, the storage device <NUM> may further perform the reclaim operation on a second memory area (e.g., a memory area having a reclaim priority value of a second value) where the reclaim event is expected to occur.

In operation S33, the storage device <NUM> may determine whether there is a command enqueued in the command queue (e.g., CQ of <FIG>). When the request REQ is received from the host <NUM>, a command corresponding to the request REQ may be enqueued in the command queue CQ. If there is no command enqueued in the command queue CQ, in operation S37, the storage device <NUM> may perform the reclaim operation on another memory area (e.g., a memory area where the reclaim event has not occurred) to complete the reclaim operation on the source memory area.

If there is a command enqueued in the command queue CQ, the storage device <NUM> may perform an operation according to the enqueued command in operation S35. For example, when a read request is received from the host <NUM> and thus a read command is enqueued in the command queue CQ, the storage device <NUM> may perform a read operation before completing the reclaim operation on another memory area of the source memory area (e.g., a memory area where the reclaim event has not occurred). Alternatively, for example, when a write request is received from the host <NUM> and thus, a write command is enqueued in the command queue CQ, the storage device <NUM> may perform a write operation before completing the reclaim operation on another memory area of the source memory area (e.g., a memory area where the reclaim event has not occurred).

When the operation according to the request REQ of the host <NUM> is completed in operation S35, in operation S37, the storage device <NUM> may perform the reclaim operation on the other memory area, a third memory area where the reclaim event has not occurred (e.g., a memory area having a third value of a reclaim priority value).

The storage device <NUM> according to the inventive concept may preferentially perform the reclaim operation on the memory area where the reclaim event has occurred, then perform the operation according to the request REQ of the host <NUM>, and after the operation according to the request REQ of the host <NUM>, perform the reclaim operation on the remaining memory area where the reclaim event has not occurred to complete the reclaim operation on the source memory area. The present invention is not limited thereto. In an example embodiment, the storage device <NUM> may preferentially perform the reclaim operation on the memory area where the reclaim event has occurred and the memory area where the reclaim event is expected to occur, then perform the operation according to the request REQ of the host <NUM>, and after completing the operation according to the request REQ of the host <NUM>, perform the reclaim operation on the remaining memory area where the reclaim event has not occurred to complete the reclaim operation on the source memory area. Therefore, the storage device <NUM> may prevent data from being degraded by the delay in the reclaim operation of the memory area where the reclaim event has occurred, and simultaneously prevent the processing of the request REQ of the host <NUM> from being delayed.

In the description of <FIG>, an embodiment in which a command according to the request REQ of the host <NUM> is performed after performing the reclaim operation on the first memory area and the second memory area is described, but the storage device <NUM> according to the inventive concept is not limited thereto. In an embodiment, the storage device <NUM> may process the command according to the request REQ of the host <NUM> after performing the reclaim operation on the first memory area where the reclaim event has occurred. Subsequently, the storage device <NUM> may the reclaim operation on the second memory area where the reclaim event is expected to occur.

<FIG> is a flowchart illustrating an operating method of the storage device <NUM> according to an embodiment, and is an example of operations S10 and S20 of <FIG>.

Referring to <FIG>, in operation S100, the host <NUM> may transmit a read request to the storage device <NUM>.

The operation S10 of <FIG> may include operations S11 to S13. In operation S11, the storage device <NUM> may read data in response to the read request.

In operation S13, the storage device <NUM> may check an error of the read data to determine whether a reclaim event has occurred. In an embodiment, the storage device <NUM> may determine that the reclaim event has occurred when an error bit rate of the read data is greater than or equal to a reference value. Alternatively, in an embodiment, the storage device <NUM> may execute defense code by firmware to perform a read retry due to the error in the read data, and determine that the reclaim event has occurred when executing previously designated specific defense code.

In operation S20', the storage device <NUM> may set a reclaim priority value of a memory area corresponding to the read request. For example, when it is determined that the reclaim event has occurred in operation S13, the storage device <NUM> may set a priority value (e.g., a first value) of a prior order such that the reclaim operation is preferentially performed on the memory area associated with the read request. Otherwise, when it is determined that the reclaim event has not occurred, the storage device <NUM> may set a priority value (e.g., a third value) of a posterior order to the memory area corresponding to the read request.

<FIG> are flowcharts illustrating an operating method of the storage device <NUM> according to an embodiment, and are examples of operations S10 and S20 of <FIG>. <FIG> are diagrams illustrating an embodiment in which the storage device <NUM> performs a background read operation. Each of operations described with respect to <FIG> may be periodically performed. In <FIG>, redundant descriptions of the same reference numerals as in <FIG> will be omitted.

Referring to <FIG> and <FIG>, operation S10a may include operations S11a and S13. In operation S11a, the storage device <NUM> may read data in a memory area connected to an adjacent word line of a word line on which the read operation (background read operation) is performed. When the read operation is performed, a read voltage may be applied to a specific word line, and stress may be generated (a read disturb) on word lines adjacent to the specific word line. Accordingly, the storage device <NUM> may determine whether a reclaim event has occurred by reading the memory area connected to the adjacent word line of the word line on which the read operation is performed. In operation S13, the storage device <NUM> may check an error in data to determine whether the reclaim event has occurred.

In operation S20a, the storage device <NUM> may set a reclaim priority value of the memory area connected to the adjacent word line. For example, when it is determined that the reclaim event has occurred in operation S13, the storage device <NUM> may set a priority value (e.g., a first value) of a prior order such that the reclaim operation is preferentially performed on the memory area connected to the adjacent word line. Otherwise, when it is determined that the reclaim event has not occurred, the storage device <NUM> may set a priority value (e.g., a third value) of a posterior order to the memory area connected to the adjacent word line.

Referring to <FIG> and <FIG>, operation S10b may include operations S11b and S13. In operation S11b, the storage device <NUM> may read data from a memory area where old data is stored. The data may degrade over time after the data is programmed. Accordingly, the storage device <NUM> may determine the data as the old data when a reference time or more elapses after the data is programmed, and determine whether the reclaim event has occurred by reading the memory area where the old data is stored. In operation S13, the storage device <NUM> may check an error in the data to determine whether the reclaim event has occurred.

In operation S20b, the storage device <NUM> may set a reclaim priority value of the memory area where the old data is stored. For example, when it is determined that the reclaim event has occurred on the memory area where the old data is stored in operation S13, the storage device <NUM> may set a priority value of a prior order such that the reclaim operation is preferentially performed on the memory area where the old data is stored. Otherwise, when it is determined that the reclaim event has not occurred, the storage device <NUM> may set a priority value of a posterior order to the memory area where the old data is stored.

Referring to <FIG> and <FIG>, operation S10c may include operations S11c and S13. In operation S11c, the storage device <NUM> may read data from a previously designated memory area. The previously designated memory area may be a memory area where data reliability may be low due to a physical structure of the memory cell array (e.g., <NUM> in <FIG>) of a nonvolatile memory. Information about the previously designated memory area may be stored as degradation information in the metadata buffer MB.

For example, as described with respect to <FIG>, the previously designated memory area may be pages included in the bottom layer area BLA or the top layer area TLA of a memory block. Alternatively, for example, as described with reference to <FIG>, the previously designated memory area may be memory blocks disposed in the first edge area EA1 and the second edge area EA2. In operation S13, the storage device <NUM> may check an error in the data read from the bottom layer area BLA or the top layer area TLA to determine whether the reclaim event has occurred.

In operation S20c, the storage device <NUM> may set a reclaim priority value of the previously designated memory area. For example, when it is determined that the reclaim event has occurred in operation S13, the storage device <NUM> may set a priority value of a prior order such that the reclaim operation is preferentially performed on the previously designated memory area. Otherwise, when it is determined that the reclaim event has not occurred, the storage device <NUM> may set a priority value of a posterior order to the previously designated memory area.

Referring to <FIG> and <FIG>, operation S10d may include operations S11d and S13. In operation S11d, the storage device <NUM> may randomly select a memory area from among a plurality of memory areas to read data of selected the memory area. For example, the storage device <NUM> may randomly select the second page PG2 from among the first to mth pages PG1 to PGm of <FIG> to read the data. In operation S13, the storage device <NUM> may check an error in the data to determine whether the reclaim event has occurred.

In operation S20d, the storage device <NUM> may set a reclaim priority value of the selected memory area. For example, when it is determined that the reclaim event has occurred in operation S13, the storage device <NUM> may set a priority value of a prior order such that the reclaim operation is preferentially performed on the selected memory area. Otherwise, when it is determined that the reclaim event has not occurred, the storage device <NUM> may set a priority value of a posterior order to the selected memory area.

<FIG> is a block diagram illustrating grouping of a super block SPB in the nonvolatile memory <NUM> of <FIG> according to an embodiment.

Referring to <FIG> and <FIG>, the memory devices NVM1 that communicate with the controller <NUM> through the first channel CH1 may include first to jth memory devices 120_1 to 120_j (j is an integer greater than or equal to <NUM>). The first to jth memory devices 120_1 to 120_j may respectively include the n memory blocks BLK_11 to BLK_1n, BLK_21 to BLK_2n, and BLK_j <NUM> to BLK_jn.

In the first to jth memory devices 120_1 to 120_j, blocks allocated with the same address (or blocks disposed in the same location) may be grouped into one super block SPB. For example, the second memory blocks BLK_12, BLK_22, and BLK_j2 of the first to jth memory devices 120_1 to 120_j may be grouped into the one super block SPB.

In an embodiment, the storage device <NUM> may perform a reclaim operation in units of the super block SPB. For example, when a reclaim event has occurred in the second, fourth, and (m-<NUM>)th pages PG2, PG4, and PG(m-<NUM>)th included in the second memory block BLK_j2 of the jth memory device 120_j, the second memory blocks BLK_12, BLK_22, and BLK_j2 included in the super block SPB together with the second memory block BLK_j2 of the jth memory device 120_j may be registered in the reclaim queue (e.g., RQ of <FIG>) as source blocks.

As described with respect to <FIG> and <FIG>, a physical address of a source block and a reclaim priority value corresponding thereto may be stored in the reclaim queue RQ. For example, reclaim priority values respectively corresponding to the second memory blocks BLK_12, BLK_22, and BLK_j2 may be set in the reclaim queue RQ. The controller <NUM> may perform a reclaim operation based on the reclaim priority value stored in the reclaim queue RQ.

For example, a reclaim priority value (e.g., the first value PV1) of a prior order may be set to the second memory block BLK_j2 of the jth memory device 120_j in which the reclaim event has occurred, and the reclaim operation may be more preferentially performed on the second memory block BLK_j2 than the other memory blocks of the j-th memory device 120_j. Also, for example, a reclaim priority value of the first value PV1 may be set to the second, fourth, and (m-<NUM>)th pages PG2, PG4, and PG(m-<NUM>)th of the second memory block BLK_j2 of the jth memory device 120_j, and the reclaim operation may be more preferentially performed on the second, fourth, and (m-<NUM>)th pages PG2, PG4, and PG(m-<NUM>)th than the other pages of the second memory block BLK_j2.

For example, a reclaim priority value (e.g., the third value PV3) of a posterior order may be set to the second memory block BLK_12 of the first memory device 120_1 in which the reclaim event has not occurred, and the first memory device 120_1 may perform the reclaim operation after performing an operation according to the request REQ of the host <NUM>.

Claim 1:
An operating method of a storage device (<NUM>) comprising while setting (S20) a reclaim priority value to each of a plurality of memory areas of a source memory area:
detecting (S10) whether a reclaim event has occurred on the source memory and
performing (S30) a reclaim operation on the source memory area according to the reclaim priority value of each of the plurality of memory areas,
wherein the reclaim operation moves data stored in the source memory area to a destination memory area,
characterized in that the setting of the reclaim priority value comprises:
setting, in response to detecting of the reclaim event having occurred to a first memory area among the plurality of memory areas, a first reclaim priority value to the first memory area;
setting, in response to detecting of the reclaim event being expected to occur to a second memory area among the plurality of memory areas based on degradation information stored in a metadata buffer of the storage device, a second reclaim priority value to the second memory area; and
setting, in response to detecting of the reclaim event not having occurred to a third memory area and detecting of the reclaim event not being expected to occur to the third memory area, a third reclaim priority value to the third memory area.