Memory system, memory controller and operation method thereof

By introducing an error correction execution component and a data recovery controller in the memory system, whether to perform a refresh or read recovery operation is determined based on the number of error bits in the read data, the problem of difficult to implement data reading error correction in the prior art is solved. , improves data reliability and system stability.

CN114121106BActive Publication Date: 2024-12-06SK HYNIX INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202110419026.X
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2020-08-28
Filing Date
2021-04-19
Publication Date
2024-12-06
Estimated Expiration
2041-04-19

AI Technical Summary

Technical Problem

It is difficult for existing memory systems to effectively correct errors during data reading, resulting in data degradation and reduced reliability.

Method used

A memory system is designed to correct errors on read data of multiple pages through a memory controller and decide whether to perform refresh or read recycling operations based on the number of error bits to improve data reliability.

Benefits of technology

By correcting error bits in the read data, the system can improve data reliability, reduce data degradation, and ensure the stability and performance of the memory system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114121106B_ABST
    Figure CN114121106B_ABST
Patent Text Reader

Abstract

The present disclosure relates to a memory system, a memory controller and an operation method thereof. The present technology relates to an electronic device. A memory system for improving data reliability includes: a memory device including a plurality of pages; and a memory controller configured to correct errors in read data obtained by reading a selected page among the plurality of pages, and determine whether to perform a refresh operation on the selected page based on the number of error bits included in the read data. The memory controller includes: a normal read operation controller configured to control a read operation on a selected page and determine the number of error bits in the read data; an error correction execution component configured to correct the read data; and a data recovery controller configured to control a refresh operation on the selected page based on the number of error bits in the read data when the error in the read data is corrected.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to an electronic device, and more particularly, to a memory system and an operating method thereof. Background Art

[0002] A storage device (memory system) stores data under the control of a host device such as a computer, a smart phone, or a smart tablet. The storage device may be a type that stores data in a magnetic disk, such as a hard disk drive (HDD), or a type that stores data in a semiconductor memory, such as a solid state drive (SSD) or a memory card (particularly a non-volatile memory).

[0003] The storage device may include a memory device in which data is stored and a memory controller that stores data in the memory device. Generally, there are two types of memory devices: volatile memory devices and non-volatile memory devices. Examples of non-volatile memory devices include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory, phase change RAM (PRAM), magnetic RAM (MRAM), resistive RAM (RRAM), ferroelectric RAM (FRAM), etc. Summary of the invention

[0004] Embodiments of the present disclosure provide a memory system and a method of controlling a memory device to effectively improve data degradation and enhance data reliability.

[0005] A memory system according to an embodiment of the present disclosure may include: a memory device including a plurality of pages; and a memory controller configured to correct errors in read data obtained by reading a selected page among the plurality of pages, and determine whether to perform a refresh operation on the selected page based on the number of error bits in the read data. The memory controller may include: a normal read operation controller configured to control a read operation on the selected page and determine the number of error bits in the read data; an error correction execution component configured to correct the read data; and a data recovery controller configured to control a refresh operation on the selected page based on the number of error bits in the read data when the error in the read data is corrected.

[0006] A method for operating a memory system, the memory system comprising: a memory device, the memory device comprising a plurality of pages; and a memory controller, the memory controller being configured to correct errors in read data obtained by reading a selected page among the plurality of pages, and determine whether to perform a refresh operation on the selected page based on the number of error bits in the read data, the method may include the following steps: reading the selected page to obtain the read data; correcting the errors in the read data; when the correction of the errors in the read data is passed, determining the number of error bits in the read data; and controlling the refresh operation on the selected page based on the number of error bits in the read data.

[0007] A memory controller according to one embodiment of the present disclosure controls a memory device including multiple pages, and the memory controller may include: a normal read operation controller, which is configured to control a read operation on a selected page among the multiple pages and determine the number of error bits in read data read from the memory device during the read operation; an error correction execution component, which is configured to correct errors in the read data; and a data recovery controller, which is configured to control a refresh operation on the selected page based on the number of error bits in the read data when the errors in the read data are corrected.

[0008] An operating method of a controller may include the following steps: providing read data that has been successfully read from a page to a host; and controlling a memory device to selectively perform a refresh operation on the page or a read reclaim operation on a block including the page based on the number of error bits detected in the read data.

[0009] An operating method of a controller may include the following steps: providing a host with first data that has been successfully read from a physical page; controlling a memory device to read second data from a least significant bit page corresponding to the physical page; and based on a difference between the first data and the second data, controlling the memory device to selectively perform a refresh operation on the physical page or a read reclaim operation on a block including the physical page.

[0010] An operating method of a controller may include the following steps: providing read data that has been successfully read from a page to a host; controlling a memory device to read block data from two or more pages in a block including the page; detecting the number of error bits in the block data; and controlling the memory device to selectively perform a refresh operation on the page or a read reclaim operation on the block based on the number of error bits detected in the block data.

[0011] According to the present technology, when error correction is passed, data reliability can be improved by determining whether to perform a refresh operation or a read reclaim operation based on the number of error bits included in read data. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 is a block diagram showing a storage device.

[0013] Figure 2 It is shown Figure 1 A diagram of the structure of a memory device.

[0014] Figure 3 It is shown Figure 2 FIG. 1 is a diagram of one embodiment of a memory cell array.

[0015] Figure 4A and Figure 4B is a diagram illustrating a read retry operation and an e-boost operation performed after an error correction decoding operation fails.

[0016] Figure 5 An operation of a memory controller when an error correction decoding operation is passed according to one embodiment of the present disclosure is shown.

[0017] Figure 6 It is shown based on Figure 5 A diagram of the operations performed in error correction decoding to determine the number of erroneous bits in the data.

[0018] Figure 7 is a diagram illustrating a read reclaim operation.

[0019] Figure 8 is a diagram showing a refresh operation.

[0020] Fig. 9 Operations of the memory controller performed based on data read according to a page read command are shown.

[0021] Fig. 10A and Fig. 10B It is shown by Fig. 9 A diagram of the logical pages read by a page read command.

[0022] Fig.11A and Fig. 11B It is shown based on Fig. 9 A diagram of the number of error bits in the data read while performing an operation of the Page Read command.

[0023] Fig.12 Operations of the memory controller performed based on data read according to a block read command are shown.

[0024] FIG. 13A to FIG. 13D is shown corresponding to Fig.12 A diagram of the operation of a block read command.

[0025] Fig.14 It is shown based on Fig.12A diagram of the Block Read command operation performed while the number of error bits in the read data.

[0026] Fig.15 is a diagram illustrating the operation of a memory controller according to one embodiment of the present disclosure.

[0027] Fig.16 is a diagram illustrating the operation of a memory controller according to one embodiment of the present disclosure.

[0028] Fig.17 is a diagram illustrating the operation of a memory controller according to one embodiment of the present disclosure.

[0029] Fig.18 is a diagram illustrating the operation of a memory controller according to one embodiment of the present disclosure.

[0030] Fig.19 It is shown Figure 1 FIG. 1 is a diagram of another embodiment of a memory controller.

[0031] Fig. 20 is a block diagram illustrating a memory card system to which a storage device is applied according to one embodiment of the present disclosure.

[0032] Fig.21 is a block diagram illustrating a solid state drive (SSD) system to which a storage device is applied according to one embodiment of the present disclosure.

[0033] Fig. 22 is a block diagram illustrating a user system to which a storage device is applied according to one embodiment of the present disclosure. DETAILED DESCRIPTION

[0034] The specific structural description and functional description herein are provided only for describing the embodiments of the present disclosure. However, the present invention can be implemented in various forms and implemented in various ways; therefore, the present invention is not limited to any disclosed embodiments. Throughout the specification, references to "one embodiment" or "another embodiment" and the like do not necessarily refer to only one embodiment, and different references to any such phrases do not necessarily refer to the same embodiment. When the term "embodiment" is used herein, it does not necessarily refer to all embodiments.

[0035] Embodiments of the present disclosure are described in detail below with reference to the accompanying drawings so that those skilled in the art to which the present disclosure belongs can practice and easily implement the present invention.

[0036] Figure 1 is a block diagram showing a storage device.

[0037] Reference Figure 1, the storage device 50 may include a memory device 100 and a memory controller 200 .

[0038] The storage device 50 may store data under the control of a host 300 (eg, a cellular phone, a smart phone, an MP3 player, a laptop computer, a desktop computer, a game console, a television, a tablet PC, or an in-vehicle infotainment system).

[0039] The storage device 50 may be manufactured or configured as any of various types of storage devices according to a host interface as a communication method with the host 300. For example, the storage device 50 may be configured as an SSD, a multimedia card (in the form of MMC, eMMC, RS-MMC, and micro-MMC), a secure digital card (in the form of SD, mini-SD, and micro-SD), a universal serial bus (USB) storage device, a universal flash storage (UFS) device, a personal computer memory card international association (PCMCIA) card type storage device, a peripheral component interconnect (PCI) card type storage device, a PCI Express (PCI-E) card type storage device, a compact flash (CF) card, a smart media card, and / or a memory stick.

[0040] The memory device 50 may be manufactured as any of various types of packages. For example, the memory device 50 may be manufactured as a package-on-package (PoP), a system-in-package (SIP), a system-on-chip (SOC), a multi-chip package (MCP), a chip-on-board (COB), a wafer-level fabrication package (WFP), and / or a wafer-level stacked package (WSP).

[0041] The memory device 100 may store data. The memory device 100 operates in response to the control of the memory controller 200. The memory device 100 may include a memory cell array including a plurality of memory cells storing data. The memory cell array may include a plurality of memory blocks. Each memory block may include a plurality of memory cells that may constitute a plurality of pages. In one embodiment, a page may be a unit for storing data in the memory device 100 or reading data stored in the memory device 100. A memory block may be a unit for erasing data.

[0042] In one implementation, the memory device 100 may include a data reader 170. The data reader 170 may read data of a selected page in response to a read command received from the memory controller 200. The data reader 170 may output read data obtained by reading the data of the selected page to the memory controller 200.

[0043] In one embodiment, the memory device 100 may be a double data rate synchronous dynamic random access memory (DDR SDRAM), a low power double data rate 4 (LPDDR4) SDRAM, a graphic double data rate (GDDR) SDRAM, a low power DDR (LPDDR), a Rambus dynamic random access memory (RDRAM), a NAND flash memory, a vertical NAND flash memory, a NOR flash memory, a resistive random access memory (RRAM), a phase change memory (PRAM), a magnetoresistive random access memory (MRAM), a ferroelectric random access memory (FRAM), or a spin transfer torque random access memory (STT-RAM), etc. In this specification, as an example, it is assumed that the memory device 100 is a NAND flash memory.

[0044] The memory device 100 may be implemented as a two-dimensional array structure or a three-dimensional array structure. Although the various aspects and features of the present invention are described below in the context of a three-dimensional array structure memory device, the present invention is not limited to a three-dimensional array structure. The present disclosure may be applied not only to a flash memory device in which a charge storage layer is composed of a conductive floating gate (FG), but also to a charge trap flash (CTF) in which a charge storage layer is composed of an insulating film.

[0045] In one embodiment, the memory device 100 may operate in a single-level cell (SLC) method of storing one data bit in one memory cell. Alternatively, the memory device 100 may operate in a method of storing at least two data bits in one memory cell. For example, the memory device 100 may operate in a multi-level cell (MLC) method of storing two data bits in one memory cell, a triple-level cell (TLC) method of storing three data bits in one memory cell, or a quad-level cell (QLC) method of storing four data bits in one memory cell.

[0046] The memory device 100 is configured to receive commands and addresses from the memory controller 200, and access the area selected by the address in the memory cell array. That is, the memory device 100 can perform an operation corresponding to the command on the area selected by the address. For example, the memory device 100 can perform a write operation (programming operation), a read operation, or an erase operation according to the received command. For example, when a program command is received, the memory device 100 can program data to the area selected by the address. When a read command is received, the memory device 100 can read data from the area selected by the address. When an erase command is received, the memory device 100 can erase the data stored in the area selected by the address.

[0047] In one embodiment, the memory controller 200 may include a normal read operation controller 210 , an error correction performance component 220 , and a data recovery controller 230 .

[0048] In one embodiment, the normal read operation controller 210 can control the memory device 100 so that the memory device 100 performs a normal read operation. Here, a default read voltage can be used to perform a normal read operation. The default read voltage can be determined by testing during the production process of the memory device 100, and can distinguish between an erase state and each programming state.

[0049] The normal read operation controller 210 may provide a read command and an address for performing a normal read operation to the memory device 100, and obtain data read from the memory device 100. When obtaining the read data from the memory device 100, the normal read operation controller 210 may provide the read data to the error correction execution component 220, and the error correction execution component 220 performs an error correction decoding operation and reports the result to the normal read operation controller 210. Based on the result, the normal read operation controller 210 may determine whether to perform a data recovery operation, and may provide the result of the determination to the data recovery controller 230.

[0050] In one embodiment, the error correction execution component 220 can correct errors in the read data. The error correction decoding operation performed by the error correction execution component 220 can detect and correct error bits in the read data. Here, the maximum number of error bits that can be corrected by the error correction execution component 220 can be predetermined.

[0051] For example, when the number of error bits in the read data exceeds the maximum number of correctable error bits, the error correction execution component 220 can determine that the error correction decoding operation has failed. In addition, when the number of error bits in the read data is equal to or less than the maximum number of correctable error bits, the error correction execution component 220 can correct these errors and determine that the error correction decoding operation has passed. When the error correction decoding operation has passed, the original data can be restored. Conversely, when the error correction decoding operation has failed, the original data may not be restored.

[0052] In one embodiment, the data recovery controller 230 may selectively perform a data recovery operation according to a result of an error correction decoding operation of a normal read operation.

[0053] When the original data cannot be recovered by error correction decoding, this may indicate that the data stored in the memory device 50 is unreliable. Therefore, the memory controller 200 may perform various data recovery operations to recover the original data. Typically, the data recovery operation may include a read retry operation and an e-boost operation.

[0054] The read retry operation may include reading the data stored in the page where the read operation failed again using a set read voltage. In one embodiment, the error correction execution component 220 may perform an error correction decoding operation on the read data according to the read retry operation. When the original data cannot be recovered even through the read retry operation, an e-boost operation may be performed.

[0055] The e-boost operation may include determining an optimal read voltage for reading data stored in a page where the read operation failed, and performing the read operation again using the determined optimal read voltage. When performing the e-boost operation, the data recovery controller 230 may perform multiple read operations to find the optimal read voltage, and may determine the optimal read voltage using data obtained through the multiple read operations. The data recovery controller 230 may use the determined optimal read voltage to read the data stored in the failed page.

[0056] Note that although the read retry operation and the e-boost operation are described as examples of data recovery operations, any of a variety of other data recovery operations may be used instead. Combinations of different data recovery operations may also be used. In this case, one of the data recovery operations other than e-boost may be selected to be performed first; if e-boost is to be performed at all, e-boost is typically performed last.

[0057] However, a previous recovery operation (eg, a read retry operation or an e-boost operation) for recovering data has a problem that many read operations are involved and data may still not be recovered.

[0058] Therefore, according to an embodiment of the present disclosure, even if the error correction decoding operation for a normal read operation passes, the data recovery controller 230 can perform a read reclaim operation or a refresh operation according to the number of error bits in the normal read operation, thereby improving data reliability.

[0059] Details of the data recovery controller 230 performing the read reclaim operation or the refresh operation according to the number of error bits in the normal read operation will be described in more detail below.

[0060] The memory controller 200 may control overall operations of the memory device 50 .

[0061] The memory controller 200 may execute firmware when a power supply voltage is applied to the memory device 50. When the memory device 100 is a flash memory device, the memory controller 200 may operate firmware such as a flash translation layer (FTL) for controlling communication between the host 300 and the memory device 100.

[0062] In one embodiment, the memory controller 200 may include firmware (not shown) that may receive data and a logical block address (LBA) from the host 300 and convert the LBA into a physical block address (PBA) indicating an address of a memory cell included in the memory device 100 in which data is to be stored. In addition, the memory controller 200 may store a logical-physical address mapping table configuring a mapping relationship between the LBA and the PBA in a buffer memory.

[0063] The memory controller 200 may control the memory device 100 to perform a program operation, a read operation, an erase operation, etc. according to a request of the host 300. For example, when a program request is received from the host 300, the memory controller 200 may convert the program request into a program command, and may provide the program command, the PBA, and data to the memory device 100. When a read request together with the LBA is received from the host 300, the memory controller 200 may change the read request into a read command, select the PBA corresponding to the LBA, and then provide the read command and the PBA to the memory device 100. When an erase request together with the LBA is received from the host 300, the memory controller 200 may change the erase request into an erase command, select the PBA corresponding to the LBA, and then provide the erase command and the PBA to the memory device 100.

[0064] In one embodiment, the memory controller 200 may generate and send a program command, address, and data to the memory device 100 without a request from the host 300. For example, the memory controller 200 may provide commands, addresses, and data to the memory device 100 to perform background operations such as a program operation for wear leveling and a program operation for garbage collection.

[0065] In one embodiment, the memory device 50 may further include a buffer memory (not shown). The memory controller 200 may control data exchange between the host 300 and the buffer memory (not shown). Alternatively, the memory controller 200 may temporarily store system data for controlling the memory device 100 in the buffer memory. For example, the memory controller 200 may temporarily store data input from the host 300 in the buffer memory, and then send the data temporarily stored in the buffer memory to the memory device 100.

[0066] In various embodiments, the buffer memory may be used as an operation memory and a cache memory of the memory controller 200. The buffer memory may store codes or commands executed by the memory controller 200. Alternatively, the buffer memory may store data processed by the memory controller 200.

[0067] In one embodiment, the buffer memory may be implemented as a dynamic random access memory (DRAM) (e.g., double data rate synchronous dynamic random access memory (DDR SDRAM), DDR4 SDRAM, low power double data rate 4 (LPDDR4) SDRAM, graphics double data rate (GDDR) SDRAM, low power DDR (LPDDR), or Rambus dynamic random access memory (DRAM)) or a static random access memory (SRAM).

[0068] In various embodiments, the buffer memory may be provided external to and operably coupled to the memory device 50. In this case, one or more external volatile memory devices operably coupled to the memory device 50 may function as the buffer memory.

[0069] In one embodiment, the memory controller 200 may control two or more memory devices. In this case, the memory controller 200 may control the memory devices according to an interleaving method to improve operation performance.

[0070] The host 300 may communicate with the storage device 50 using at least one of various communication methods such as Universal Serial Bus (USB), Serial AT Attachment (SATA), Serial Attached SCSI (SAS), High Speed ​​Inter-Chip (HSIC), Small Computer System Interface (SCSI), Peripheral Component Interconnect (PCI), PCI Express (PCIe), Non-Volatile Memory Express (NVMe), Universal Flash Storage (UFS), Secure Digital (SD), MultiMedia Card (MMC), Embedded MMC (eMMC), Dual In-line Memory Module (DIMM), Registered DIMM (RDIMM) and / or Load Reduced DIMM (LRDIMM).

[0071] Figure 2 It is shown Figure 1 A diagram of the structure of a memory device.

[0072] Reference Figure 2 , the memory device 100 may include a memory cell array 110 , a peripheral circuit 120 , and a control logic 130 .

[0073] The memory cell array 110 includes a plurality of memory blocks BLK1 to BLKz connected to a row decoder 121 through a row line RL. The plurality of memory blocks BLK1 to BLKz may be connected to a page buffer group 123 through bit lines BL1 to BLn. Each of the plurality of memory blocks BLK1 to BLKz includes a plurality of memory cells. In one embodiment, the plurality of memory cells are nonvolatile memory cells. Memory cells connected to the same word line may be defined as a page. Therefore, one memory block may include a plurality of pages.

[0074] The row lines RL may include at least one source select line, a plurality of word lines, and at least one drain select line.

[0075] The peripheral circuit 120 may be configured to perform a program operation, a read operation, or an erase operation on a selected region of the memory cell array 110 under the control of the control logic 130 .

[0076] The peripheral circuit 120 may include a row decoder 121 , a voltage generator 122 , a page buffer group 123 , a column decoder 124 , an input / output circuit 125 , and a sensing circuit 126 .

[0077] The row decoder 121 is connected to the memory cell array 110 through row lines RL. The row lines RL may include at least one source select line, a plurality of word lines, and at least one drain select line.

[0078] The row decoder 121 is configured to decode the row address RADD received from the control logic 130. The row decoder 121 selects at least one memory block among the memory blocks BLK1 to BLKz according to the decoded address. In addition, the row decoder 121 can select at least one word line of the selected memory block according to the decoded address to apply the voltage generated by the voltage generator 122 to the at least one word line WL.

[0079] The voltage generator 122 operates in response to the control of the control logic 130. The voltage generator 122 is configured to generate a plurality of voltages using an external power supply voltage provided to the memory device 100. Specifically, the voltage generator 122 may generate various operation voltages Vop for program operation, read operation, and erase operation in response to the operation signal OPSIG.

[0080] In one embodiment, the voltage generator 122 may generate the internal power supply voltage by regulating the external power supply voltage. The internal power supply voltage generated by the voltage generator 122 is used as an operating voltage of the memory device 100.

[0081] In one embodiment, the voltage generator 122 may generate a plurality of voltages using an external power supply voltage or an internal power supply voltage.

[0082] For example, the voltage generator 122 may include a plurality of pumping capacitors that receive an internal power supply voltage, and may selectively activate the plurality of pumping capacitors in response to the control of the control logic 130 to generate a plurality of voltages.

[0083] The generated plurality of voltages may be provided to the memory cell array 110 by the row decoder 121 .

[0084] The page buffer group 123 includes first to nth page buffers PB1 to PBn connected to the memory cell array 110 through first to nth bit lines BL1 to BLn, respectively. The first to nth page buffers PB1 to PBn operate in response to the control of the control logic 130. Specifically, the first to nth page buffers PB1 to PBn may operate in response to a page buffer control signal PBSIGNALS.

[0085] Specifically, during a program operation, when a program voltage is applied to a selected word line, the first to n-th page buffers PB1 to PBn may transmit data DATA received through the input / output circuit 125 to a selected memory cell through the first to n-th bit lines BL1 to BLn. The memory cells of the selected page are programmed according to the transmitted data DATA. During a program verification operation, the first to n-th page buffers PB1 to PBn may read page data by sensing a voltage or current received from a selected memory cell through the first to n-th bit lines BL1 to BLn.

[0086] During a read operation, the first to nth page buffers PB1 to PBn read data DATA from memory cells of a selected page through the first to nth bit lines BL1 to BLn and output the read data DATA to the input / output circuit 125 under the control of the column decoder 124 .

[0087] During an erase operation, the first to nth page buffers PB1 to PBn may float the first to nth bit lines BL1 to BLn or apply an erase voltage.

[0088] The column decoder 124 may transfer data between the input / output circuit 125 and the page buffer group 123 in response to the column address CADD. For example, the column decoder 124 may exchange data with the first to nth page buffers PB1 to PBn through the data lines DL, or may exchange data with the input / output circuit 125 through the column lines CL.

[0089] The input / output circuit 125 can convert the Figure 1 The memory controller 200 described here transmits the received command CMD and address ADDR to the control logic 130 , or may exchange data DATA with the column decoder 124 .

[0090] The sensing circuit 126 may generate a reference current in response to the permission bit signal VRYBIT during a read operation or a verification operation, and compare a sensing voltage VPB received from the page buffer group 123 with a reference voltage generated by the reference current to output a pass signal PASS or a fail signal FAIL.

[0091] In one embodiment, the sensing circuit 126 may include a current sensing circuit (CSC) and / or a fail bit counter (FBC). The CSC or FBC in the sensing circuit 126 may output a pass signal PASS or a fail signal FAIL based on the number of error bits in the read data.

[0092] In one implementation, the sensing circuit 126 may output a pass signal PASS when the number of error bits in the read data is within a correctable error range, and may output a fail signal FAIL when the number of error bits in the read data is outside the correctable error range.

[0093] When the sensing circuit 126 outputs a pass signal PASS or a fail signal FAIL, the control logic 130 may Figure 1 The memory controller 200 outputs a corresponding signal. Figure 1 The memory controller 200 may determine whether to perform a refresh operation or a read reclaim operation based on the received pass signal PASS or fail signal FAIL.

[0094] Specifically, when the failure signal FAIL is output, Figure 1 The memory controller 200 may determine not to perform any additional operations.

[0095] However, when the output passes the signal PASS, Figure 1 The memory controller 200 may determine to selectively perform any one of a refresh operation and a read reclaim operation according to the number of error bits in read data.

[0096] For example, the memory controller 200 may determine not to perform an additional operation when the number of error bits in the read data is less than a first reference value, to perform a refresh operation when the number of error bits is equal to or greater than the first reference value and less than a second reference value, and to perform a read recovery operation when the number of error bits is equal to or greater than the second reference value.

[0097] In one embodiment, Figure 1 After the memory controller 200 determines to perform a refresh operation, the memory controller 200 may output a refresh command instructing to perform the refresh operation to the memory device 100 .

[0098] Thereafter, the memory device 100 may perform a refresh operation corresponding to the refresh command. Specifically, when refreshing the page data for which the pass signal PASS is output, the page data for which the pass signal PASS is output may be read in response to the refresh command. When the page data for which the pass signal PASS is output is read, the page data may be temporarily stored in the page buffers PB1 to PBn in the memory device 100, the page for which the pass signal PASS is output may be erased, and then the page data for which the pass signal PASS is output may be reprogrammed to the corresponding position. That is, when refreshing the data, the page data for which the pass signal PASS is output may not be output to the memory controller 200, and may be temporarily stored in the page buffers PB1 to PBn, and then may be reprogrammed to the corresponding page.

[0099] In one embodiment, when the pass signal PASS is output, the memory controller 200 may determine to perform a read reclaim operation. After the memory controller 200 determines to perform the read reclaim operation, the memory controller 200 may output a read reclaim command instructing to perform the read reclaim operation to the memory device 100. Thereafter, in response to the read reclaim command, the memory device 100 may move data of a memory block to which a page for which the pass signal PASS is output belongs to another memory block.

[0100] The control logic 130 may output an operation signal OPSIG, a row address RADD, a page buffer control signal PBSIGNALS, and an enable bit VRYBIT in response to a command CMD and an address ADDR to control the peripheral circuit 120. For example, the control logic 130 may control a read operation of a selected memory block in response to a sub-block read command and an address. In addition, the control logic 130 may control an erase operation of a selected sub-block included in a selected memory block in response to a sub-block erase command and an address. In addition, the control logic 130 may determine whether a verification operation is passed or failed in response to a pass signal PASS or a fail signal FAIL.

[0101] In one embodiment, the control logic 130 may include a data reader 170. The data reader 170 may be responsive to a Figure 1 The memory controller 200 receives a read command and reads data.

[0102] The data reader 170 may output read data to the memory controller 200 according to whether a command received from the memory controller 200 is a normal read command, a page read command, or a block read command.

[0103] In one embodiment, when the command received from the memory controller 200 is a normal read command, the data reader 170 may output read data obtained by reading a selected page to the memory controller 200 .

[0104] In one embodiment, when the command received from the memory controller 200 is a page read command, read data obtained by reading a least significant bit (LSB) page or an LSB page and a mid-significant bit (CSB) page may be output to the memory controller 200 .

[0105] In one embodiment, when Figure 1 When the command received by the memory controller 200 is a block read command, read data obtained by reading all pages, odd pages, even pages, or a set number of pages in the memory block may be output to the memory controller 200 .

[0106] Figure 3 It is shown Figure 2 FIG. 1 is a diagram of one embodiment of a memory cell array.

[0107] Reference Figure 2 and Figure 3 , Figure 3 It is shown that the Figure 2 A circuit diagram of any one memory block BLKa among a plurality of memory blocks BLK1 to BLKz in a memory cell array 110.

[0108] The first selection line, the word line, and the second selection line arranged in parallel with each other may be connected to the memory block BLKa. For example, the word line may be arranged in parallel with each other between the first selection line and the second selection line. Here, the first selection line may be a source selection line SSL, and the second selection line may be a drain selection line DSL.

[0109] More specifically, the memory block BLKa may include a plurality of strings connected between the bit lines BL1 to BLn and the source line SL. The bit lines BL1 to BLn may be connected to the respective strings, respectively, and the source line SL may be connected to the respective strings in common. Since the respective strings may be configured to be identical to each other, the string ST connected to the first bit line BL1 is specifically described as an example.

[0110] The string ST may include a source selection transistor SST, a plurality of memory cells F1 to F16, and a drain selection transistor DST connected in series between a source line SL and a first bit line BL1. One string ST may include one or more of the source selection transistor SST and the drain selection transistor DST, and may include more than 16 memory cells F1 to F16 shown in the drawings.

[0111] The source of the source select transistor SST may be connected to the source line SL, and the drain of the drain select transistor DST may be connected to the first bit line BL1. The memory cells F1 to F16 may be connected in series between the source select transistor SST and the drain select transistor DST. The gates of the source select transistors SST included in different strings may be connected to the source select line SSL, the gates of the drain select transistors DST may be connected to the drain select line DSL, and the gates of the memory cells F1 to F16 may be connected to a plurality of word lines WL1 to WL16, respectively. A group of memory cells connected to the same word line among the memory cells included in different strings may be referred to as a physical page PPG. Therefore, the memory block BLKa may include a physical page PPG of the number of word lines WL1 to WL16.

[0112] One memory cell can store one bit of data. This is generally referred to as a single-layer cell (SLC). In this case, one physical page PPG can store one logical page (LPG) of data. One logical page (LPG) of data can include the number of data bits of the memory cells included in one physical page PPG. In addition, one memory cell can store two or more bits of data. This is generally referred to as a multi-layer cell (MLC). In this case, one physical page PPG can store two or more logical pages (LPG) of data.

[0113] Although MLC generally refers to a memory cell capable of storing two or more bits of data, as the capacity of the memory cell increases, MLC sometimes more specifically refers to a memory cell storing two bits of data. In this case, a memory cell storing three or more bits of data is referred to as a triple-level cell (TLC), and a memory cell storing four or more bits of data is referred to as a quad-level cell (QLC). In general, the present invention can be applied to a memory device 100 having memory cells each capable of storing two or more bits of data.

[0114] In another embodiment, the memory block may have a three-dimensional structure. Each memory block includes a plurality of memory cells stacked on a substrate. Such a plurality of memory cells are arranged along the +X direction, the +Y direction, and the +Z direction.

[0115] Figure 4A and Figure 4Bis a diagram illustrating a read retry operation and an e-boost operation performed after an error correction decoding operation fails.

[0116] Reference Figure 4A and Figure 4B , Figure 4A shows a read retry operation, and Figure 4B The e-boost operation is shown.

[0117] Reference Figure 4A and Figure 4B , Figure 4A and Figure 4B Adjacent ones of the threshold voltage distributions of the memory cells are shown. Figure 4A and Figure 4B The horizontal axis represents the magnitude Vth of the threshold voltage of the memory cell, and Figure 4A and Figure 4B The vertical axis represents the serial number of the memory cell.

[0118] In one embodiment, when the memory device 100 performs a program operation in a multi-level cell (MLC) method, Figure 4A and Figure 4B is a threshold voltage distribution of memory cells that may be in the erase state E and the first program state P1, the first program state P1 and the second program state P2, or the second program state P2 and the third program state P3 (ie, two adjacent states).

[0119] Assumptions Figure 4A and Figure 4B Threshold voltage distributions of memory cells in a first programming state P1 and a second programming state P2 are shown.

[0120] In one embodiment, the memory device 100 may perform a normal read operation using the RH voltage as a default read voltage corresponding to a normal read command received from the memory controller 200. Thereafter, the memory controller 200 may receive data read using the RH voltage and perform an error correction decoding operation to correct errors included in the read data.

[0121] In one embodiment, when the number of error bits included in the read data exceeds the number of correctable bits, the error correction decoding operation may fail. In this case, a recovery operation for recovering the original data may be performed.

[0122] Reference Figure 4A The read retry operation may be a read operation performed using a read voltage adjacent to the RH voltage used to perform the read operation. The read retry operation may be performed according to the priority of the read voltage. Specifically, the read retry operation may be performed with reference to a read retry table.

[0123] Reference Figure 4A The first read retry voltage RR1 and the second read retry voltage RR2 may distinguish the first program state P1 from the second program state P2. RR1 and RR2 may be included in the read retry table. That is, at least two read retry voltages may be included in the read retry table.

[0124] In one embodiment, a first read operation 1 may be performed using a first read retry voltage RR1. st READ, and then a second read operation 2 may be performed using a second read retry voltage RR2. nd READ. Depending on the set priority, the second read operation can be nd READ first performs the first read operation 1 st READ.

[0125] In one embodiment, the first read retry voltage RR1 may be a voltage obtained by adding a first offset OFFSET1 to the RH voltage (RH+OFFSET1), and the second read retry voltage RR2 may be a voltage obtained by adding an offset OFFSET2 to the RH voltage (RH+OFFSET2).

[0126] In another embodiment, the read retry table may further include various voltages in addition to the first read retry voltage RR1 and the second read retry voltage RR2 for distinguishing the first program state P1 from the second program state P2. Any suitable number of read voltages may be included in the read retry table.

[0127] Reference Figure 4B , the e-boost operation may be an operation of determining an optimal read voltage based on a read result using a read voltage determined based on an ideal threshold voltage distribution of memory cells.

[0128] exist Figure 4B In the embodiment, assuming that the threshold voltage distribution of the memory cells is ideal, that is, the number of memory cells corresponding to each of the erased state and each of the programmed states is equally distributed, the first e-boost read voltage RB1 can be determined as an optimal read voltage as a result of reading using a plurality of read voltages. When the optimal read voltage is determined, an error correction decoding operation can be performed on data read using the optimal read voltage.

[0129] In one embodiment, after an error correction decoding operation fails, it may be selectively determined that Figure 4A Read retry operations and Figure 4BThat is, the e-boost operation may be performed after the read retry operation, or the read retry operation may be performed after the e-boost operation is performed.

[0130] However, as described above, after error correction decoding fails, simply performing multiple read operations to try to recover the original data is not particularly effective or efficient. Performing such read operations may take a long time, and even if these operations are performed, the original data may still not be recoverable.

[0131] Therefore, in one embodiment of the present disclosure, a method is proposed for ensuring data reliability by performing a read recovery operation or a refresh operation according to the number of error bits in the read data during a normal read operation even if an error correction decoding operation on the read data is passed during a normal read operation.

[0132] Figure 5 The operation of the memory controller according to one embodiment of the present disclosure is shown when an error correction decoding operation is passed.

[0133] Reference Figure 5 , Figure 5 The memory controller (or Figure 1 200) may include a normal read operation controller 210, an error correction execution component 220 and a data recovery controller 230. In addition, Figure 5 The data recovery controller 230 may include an operation execution determiner 231 , a refresh operation execution component 233 , and a read reclaim operation execution component 235 .

[0134] In one embodiment, according to a read request from the host 300, the normal read operation controller 210 may output a normal read command NREAD_CMD and a normal read address NREAD_ADDR to the memory device 100 to read data stored in the memory device 100. The memory device 100 may output read data READ_DATA obtained by reading data corresponding to the normal read address NREAD_ADDR in the memory device 100 to the normal read operation controller 210 in response to the normal read command NREAD_CMD.

[0135] The normal read operation controller 210 may provide the error correction execution component 220 with the read data READ_DATA received from the memory device 100. The error correction execution component 220 may perform error correction on the read data READ_DATA. For example, the error correction execution component 220 may detect an error bit included in the read data READ_DATA and perform an error correction decoding operation to correct the detected error bit.

[0136] Data read from the memory device 100 may contain one or more error bits due to retention or disturbance. Error bits may also appear in the read data as a result of reading data from the memory device 100. The error correction execution component 220 may perform error correction decoding operations to correct error bits in the read data.

[0137] The error correction decoding operation may pass or fail as a result of the error correction decoding operation being performed by the error correction execution component 220. The passing of the error correction decoding operation may indicate that the read operation passed, and the failure of the error correction decoding operation may indicate that the read operation failed.

[0138] For example, when the error correction decoding operation is passed, the error correction execution component 220 may output the error correction decoding data DEC_DATA to the host 300. Accordingly, the operation corresponding to the read request received from the host 300 may be completed.

[0139] For example, when the error correction decoding operation fails, the error correction execution component 220 may perform a recovery operation for recovering the original data. The operation for recovering the original data may include: Figure 4A Read retry operations and Figure 4B e-boost operation.

[0140] In one embodiment, when the error correction decoding operation fails, Figure 4A Read retry operations and Figure 4B In the e-boost operation, multiple read operations can be performed to recover the original data. However, a lot of time may be consumed when performing multiple read operations, so the overall efficiency of the read operation may be reduced. In addition, even if multiple read operations are performed, the original data may not be recovered.

[0141] Therefore, in one embodiment of the present disclosure, a method is provided to improve data reliability by performing a refresh operation or a read reclaim operation on a page on which a read operation is performed when an error correction decoding operation is passed.

[0142] In this drawing, it is assumed that the error correction decoding operation is passed.

[0143] Therefore, since the error correction decoding operation is passed, the error correction execution component 220 can provide the error correction decoding data DEC_DATA to the host 300 and the normal read operation controller 210. The normal read operation controller 210 can determine the number of error bits in the read data READ_DATA based on the error correction decoding data DEC_DATA. For example, the normal read operation controller 210 can determine the number of error bits included in the read data READ_DATA according to the decoding information received using the error correction decoding data DEC_DATA from the error correction execution component 220. In this article, the decoding information indicates the number of error bits detected during the error correction decoding operation. For example, the normal read operation controller 210 can determine the number of error bits included in the read data READ_DATA by comparing the read data READ_DATA received from the memory device 100 with the error correction decoding data DEC_DATA received from the error correction execution component 220. Specifically, the normal read operation controller 210 can determine the number of error bits included in the read data READ_DATA based on the number of bits that have changed among the bits included in the read data READ_DATA compared to the bits included in the error correction decoding data DEC_DATA.

[0144] The normal read operation controller 210 may determine the number of error bits in the read data READ_DATA and output error bit information ERR_BIT_INF indicating the number of error bits in the read data READ_DATA to the data recovery controller 230 .

[0145] In one embodiment, the operation execution determiner 231 included in the data recovery controller 230 may receive error bit information ERR_BIT_INF from the normal read operation controller 210. Thereafter, the operation execution determiner 231 may determine whether to perform a refresh operation or a read reclaim operation based on the error bit information ERR_BIT_INF.

[0146] For example, when the error bit information ERR_BIT_INF is less than the first reference value, the operation execution determiner 231 may determine not to perform any further operation, when the error bit information ERR_BIT_INF is equal to or greater than the first reference value and less than the second reference value, the operation execution determiner 231 may determine to perform a refresh operation, and when the error bit information ERR_BIT_INF is equal to or greater than the second reference value, the operation execution determiner 231 may determine to perform a read recovery operation. Here, the first reference value and the second reference value may be preset, and the second reference value may be greater than the first reference value.

[0147] The operation execution determiner 231 may provide operation information OP_INF regarding the determined operation to the refresh operation execution component 233 and the read reclaim operation execution component 235 .

[0148] In one embodiment, each of the refresh operation execution component 233 and the read reclaim operation execution component 235 may output a command based on the operation information OP_INF received from the operation execution determiner 231 .

[0149] For example, when the operation information OP_INF includes information about the refresh operation, the refresh operation execution component 233 may output a refresh command REFRESH_CMD to the memory device 100 to perform a refresh operation on the page where the corresponding read operation is performed. The memory device 100 may perform a refresh operation on the page where the read operation is performed in response to the refresh command REFRESH_CMD.

[0150] For example, when the operation information OP_INF includes information about the read reclaim operation, the read reclaim operation execution component 235 may output a read reclaim command RR_CMD to the memory device 100, thereby performing a read reclaim operation on a block including a page on which the corresponding read operation is performed. The memory device 100 may perform a read reclaim operation of moving data of a memory block including a page on which the read operation is performed to another memory block in response to the read reclaim command RR_CMD.

[0151] Figure 6 It is shown based on Figure 5 A diagram of the operations performed in error correction decoding to determine the number of erroneous bits in the data.

[0152] Reference Figure 5 and Figure 6 , Figure 6 The corresponding operation information OP_INF is explained, from Figure 5 The error bit information ERR_BIT_INF output by the controller 210 belongs to different ranges of a normal read operation.

[0153] In one embodiment, when Figure 5 The memory device 100 reads data through an error correction decoding operation, Figure 5 The controller 210 can read the data READ_DATA received from the memory device 100 and the data received from the memory device 100 by comparing the data READ_DATA received from the memory device 100 to the data received from the memory device 100. Figure 5 The error correction execution component 220 compares the received error correction decoded data DEC_DATA to determine the number of error bits in the read data.

[0154] Can be based on Figure 5The controller 210 determines the number of error bits to generate error bit information ERR_BIT_INF. The error bit information ERR_BIT_INF may indicate the number of error bits in the read data READ_DATA.

[0155] In one embodiment, when the error bit information ERR_BIT_INF is less than the first reference value TH1, the error bits in the read data may be very few. Figure 5 The operation execution determiner 231 may determine not to execute any further operation and may not generate the operation information OP_INF.

[0156] In one embodiment, when the error bit information ERR_BIT_INF is equal to or greater than the first reference value TH1 and less than the second reference value TH2, the read data may include some error bits. Figure 5 The operation execution determiner 231 may determine to execute a refresh operation, and may generate operation information OP_INF including information about the refresh operation REFRESH_OP. Thereafter, Figure 5 The refresh operation execution component 233 can send a refresh operation to the refresh operation execution component 233 based on the received operation information OP_INF. Figure 5 The memory device 100 outputs a refresh command REFRESH_CMD, thereby Figure 5 The memory device 100 performs a refresh operation.

[0157] In one embodiment, when the error bit information ERR_BIT_INF is equal to or greater than the second reference value TH2, the read data may include a relatively large number of error bits. Figure 5 The operation execution determiner 231 may determine to perform a read recovery operation, and may generate operation information OP_INF including information about the read recovery operation RR_OP. Thereafter, Figure 5 The read recovery operation execution component 235 can send a read recovery operation to the Figure 5 The memory device 100 outputs a read recovery command RR_CMD, thereby Figure 5 The memory device 100 performs a read reclaim operation.

[0158] Figure 7 is a diagram illustrating a read reclaim operation.

[0159] Figure 7 Shows Figure 2 BLK1 to BLK4 among the plurality of memory blocks BLK1 to BLKz in the memory cell array 110. Figure 7In the embodiment, each of the first to fourth memory blocks BLK1 to BLK4 includes four pages, but any appropriate number of pages may be included in each memory block.

[0160] In one embodiment, the first memory block BLK1 may include pages (1_1) PAGE1_1 to (1_4) PAGE1_4, the second memory block BLK2 may include pages (2_1) PAGE2_1 to (2_4) PAGE2_4, the third memory block BLK3 may include pages (3_1) PAGE3_1 to (3_4) PAGE3_4, and the fourth memory block BLK4 may include pages (4_1) PAGE4_1 to (4_4) PAGE4_4.

[0161] exist Figure 7 In the example, it is assumed that data of the (2_1)th page PAGE2_1 in the second memory block BLK2 is read, and the error correction decoding operation on the data of the (2_1)th page PAGE2_1 passes.

[0162] Reference Figure 5 and Figure 6 , when the number of error bits in the data of the (2_1)th page PAGE2_1 is equal to or greater than the second reference value TH2, it is possible to Figure 5 The read recovery operation execution component 235 outputs the read recovery command RR_CMD, Figure 1 The memory device 100 performs a read reclaim operation.

[0163] For example, based on Figure 1 The normal read command received by the memory controller 200 reads the data programmed to the (2_1)th page PAGE2_1, and then the error correction decoding operation on the read data can pass. After the error correction decoding operation on the read data passes, all the data of the second memory block BLK2 including the (2_1)th page PAGE2_1 on which the read operation is performed can be moved to another memory block (free block) based on the number of error bits in the read data. This is called read recycling. That is, through the read recycling operation, all the data programmed to the memory block including the page passed in the error correction decoding operation can be programmed to another memory block.

[0164] In one embodiment, all data of the second memory block BLK2 including the (2_1)th page PAGE2_1 may be programmed again in the fourth memory block BLK4 instead of the second memory block BLK2. The fourth memory block BLK4 may be a free block.

[0165] Thereafter, when all data of the second memory block BLK2 are programmed to the fourth memory block BLK4 and data of the (2_1)th page PAGE2_1 are programmed to the (4_1)th page PAGE4_1, the read operation to be performed on the (2_1)th page PAGE2_1 may be performed on the (4_1)th page PAGE4_1.

[0166] Figure 8 is a diagram showing a refresh operation.

[0167] Reference Figure 6 and Figure 8 , Figure 8 Shows that when Figure 1 When the number of error bits in the data of the (2_1)th page PAGE2_1 read by the memory device 100 is equal to or greater than the first reference value TH1 and less than the second reference value TH2, based on the Figure 5 The refresh command REFRESH_CMD output by the refresh operation execution component 233 is composed of Figure 1 Here, it is assumed that the error correction decoding operation of the data of the (2_1)th page PAGE2_1 read from the memory device 100 passes.

[0168] Figure 8 FIG. 2 shows an operation corresponding to the refresh command REFRESH_CMD when the second memory block BLK2 including the (2_1)th page PAGE2_1 is a page-based fail candidate. Referring to FIG. Fig.12 A method for determining whether the second memory block BLK2 is a page-based failure candidate or a block-based failure candidate is described in more detail. Here, the page-based failure candidate may indicate that some pages in the second memory block BLK2 have a high probability of failing in a future error correction decoding operation. In addition, the block-based failure candidate may indicate that most pages in the second memory block BLK2 have a high probability of failing in a future error correction decoding operation.

[0169] In one embodiment, Figure 8 The following figure shows the case where the number of error bits in the read data READ_DATA read from the (2_1)th page PAGE2_1 is within a specific range (refer to Figure 5 ), when the number of error bits in the page read data PAGER_DATA read from the LSB page among the logical pages of the (2_1)th page PAGE2_1 is within a specific range (refer to Fig. 9), or when the number of error bits in the page read data PAGER_DATA read from the LSB page in PAGE2_1 is equal to or greater than the number of error bits in the PAGER_DATA read from the CSB page in PAGE2_1 (refer to Fig. 9 When any one of these conditions is met, the refresh operation corresponding to the refresh command REFRESH_CMD can be performed.

[0170] When data of a page that has passed the error correction decoding operation is refreshed in response to a refresh command REFRESH_CMD, the data read by the refresh operation may be temporarily stored in Figure 1 In the page buffer of the memory device 100, etc., and can be programmed to the same position again after the corresponding page is erased. That is, when refreshing data, the page data passed in the error correction decoding operation may not be output to Figure 1 The memory controller 200 can be temporarily stored in Figure 1 , and is then programmed again to the corresponding page.

[0171] Reference Figure 8 In response to the refresh command REFRESH_CMD, the data of page (2_1) PAGE2_1 may be temporarily stored in Figure 2 In at least one of the first to nth page buffers PB1 to PBn included in the page buffer group 123 in the memory device 100, and after the (2_1)th page PAGE2_1 is erased, the temporarily stored data may be programmed again to the (2_1)th page PAGE2_1.

[0172] In one embodiment, the page read operation may be performed after the error correction decoding operation is passed. The page read operation may include reading data from an LSB page among logical pages included in the (2_1)th page PAGE2_1, or reading data from both the LSB page and the CSB page.

[0173] Among the logical pages included in the (2_1)th page PAGE2_1, when the number of error bits in the LSB page data belongs to a specific range or the number of error bits in the LSB page data is equal to or greater than the number of error bits in the CSB page data, a refresh operation corresponding to the refresh command REFRESH_CMD can be performed.

[0174] However, among the logical pages included in the (2_1)th page PAGE2_1, when the number of error bits in the LSB page data is equal to or greater than the reference value or the number of error bits in the LSB page data is less than the number of error bits in the CSB page data, the following may be performed: Figure 7 The read reclaim operation is shown.

[0175] In one embodiment, a block read operation may be performed after the error correction decoding operation is passed. During the block read operation, error correction may be performed on data from all pages in the second memory block BLK2, data from odd pages, data from even pages, or data from a set number of pages. The read operation may be performed sequentially or randomly.

[0176] As a result of performing an error correction decoding operation on the block read data, when the number of error bits in the block read data belongs to a specific range corresponding to the page-based failure candidate, a refresh operation may be performed. For example, when the number of error bits in the block read data is equal to or greater than a fifth reference value and less than a sixth reference value, a refresh operation may be performed.

[0177] In addition, as a result of performing an error correction decoding operation on the block read data, when the number of error bits in the block read data is equal to or greater than a specific value, thereby corresponding to a block-based failure candidate, a read recovery operation can be performed. For example, when the number of error bits in the block read data is equal to or greater than a sixth reference value, a read recovery operation can be performed.

[0178] For example, during a block read operation, all pages, odd pages, even pages, or a set number of pages in the second memory block BLK2 may be read, and as a result of the reading, when the number of error bits in the block read data is equal to or greater than the sixth reference value, the memory block including the page on which the read operation is performed may be a block-based failure candidate. As for the block-based failure candidate, the following may be performed: Figure 7 The read reclaim operation is shown.

[0179] Fig. 9 Operations of the memory controller performed based on data read according to a page read command are shown.

[0180] Fig. 9 1 and 2. A process of a refresh operation or a read reclaim operation performed based on data newly obtained from the memory device 100 after an error correction decoding operation on the read data READ_DATA read from the memory device 100 is passed is shown.

[0181] Reference Figure 5 and Fig. 9, until the normal read operation controller 210 receives the read data READ_DATA corresponding to the normal read command NREAD_CMD from the memory device 100 and then outputs the error bit information ERR_BIT_INF, Figure 5 and Fig. 9 The contents are the same, so repeated description is omitted.

[0182] In one embodiment, the normal read operation controller 210 may determine the number of error bits in the read data READ_DATA and output error bit information ERR_BIT_INF indicating the number of error bits in the read data READ_DATA to the data recovery controller 230. Figure 5 Compared with the embodiment of the normal read operation, the controller 210 may output the error correction decoded data DEC_DATA together with the error bit information ERR_BIT_INF to the data recovery controller 230.

[0183] and Figure 5 The difference is, Fig. 9 The data recovery controller 230 may further include a reference data acquisition component 237. In addition, the normal read operation controller 210 may provide the reference data acquisition component 237 with error bit information ERR_BIT_INF and error correction decoding data DEC_DATA.

[0184] In one embodiment, when the reference data acquisition component 237 receives the error bit information ERR_BIT_INF from the normal read operation controller 210, the reference data acquisition component 237 may output to the memory device 100 an indication that the read operation includes the error bit information ERR_BIT_INF in the read page (eg, Figure 7 and Figure 8 In response to the page read command PAGER_CMD, the memory device 100 may output page read data PAGER_DATA obtained by reading data from the LSB page or the LSB page and the CSB page among the logical pages included in the read page to the reference data acquisition component 237.

[0185] Thereafter, the reference data acquisition component 237 may determine the number of error bits in the page read data PAGER_DATA based on the error correction decoding data DEC_DATA and the page read data PAGER_DATA received from the normal read operation controller 210. The reference data acquisition component 237 may generate reference bit information REF_BIT_INF indicating the number of error bits in the page read data PAGER_DATA, and output the reference bit information REF_BIT_INF to the operation execution determiner 231.

[0186] In one embodiment, the operation execution determiner 231 included in the data recovery controller 230 may receive reference bit information REF_BIT_INF from the reference data acquisition component 237. Thereafter, the operation execution determiner 231 may determine whether to perform a refresh operation or a read reclaim operation based on the reference bit information REF_BIT_INF.

[0187] For example, the memory device 100 may read data from an LSB page among logical pages included in the read page in response to a page read command PAGER_CMD. In this case, the reference data acquisition component 237 may compare the error correction decoding data DEC_DATA with the LSB page data to determine the number of error bits in the data of the LSB page, and generate reference bit information REF_BIT_INF indicating the number of error bits.

[0188] As another example, the memory device 100 may read data from the LSB page and the CSB page among the logical pages included in the read page in response to the page read command PAGER_CMD. In this case, the reference data acquisition component 237 may compare the error correction decoding data DEC_DATA, the LSB page data, and the CSB page data to determine the number of error bits in the LSB page data and the number of error bits in the CSB page data, and generate reference bit information REF_BIT_INF indicating the number of error bits.

[0189] In one embodiment, in the case of reading the LSB page from the logical page in the read page, when the reference bit information REF_BIT_INF is less than the third reference value, the operation execution determiner 231 may determine not to perform any further operation, when the error bit information ERR_BIT_INF is equal to or greater than the third reference value and less than the fourth reference value, the operation execution determiner 231 may determine to perform a refresh operation, and when the error bit information ERR_BIT_INF is equal to or greater than the fourth reference value, the operation execution determiner 231 may determine to perform a read recovery operation. Here, the third reference value and the fourth reference value are preset, and the fourth reference value may be greater than the third reference value.

[0190] In one embodiment, in the case where the LSB page and the CSB page are read from among logical pages in the read page, the reference bit information REF_BIT_INF may include information on the number of error bits in the LSB page data and the number of error bits in the CSB page data.

[0191] When the number of error bits in the LSB page data is equal to or greater than the number of error bits in the CSB page data, the operation execution determiner 231 may determine to execute a refresh operation. Conversely, when the number of error bits in the LSB page data is less than the number of error bits in the CSB page data, the operation execution determiner 231 may determine to execute a read reclaim operation.

[0192] The operation execution determiner 231 may provide operation information OP_INF regarding the determined operation to the refresh operation execution component 233 and the read reclaim operation execution component 235 .

[0193] In one embodiment, the refresh operation execution component 233 and the read reclaim operation execution component 235 may output commands based on the operation information OP_INF received from the operation execution determiner 231 .

[0194] For example, when the operation information OP_INF includes information about the refresh operation, the refresh operation execution component 233 may output a refresh command REFRESH_CMD to the memory device 100 to perform a refresh operation on the page from which data is read. The memory device 100 may perform a refresh operation on the page from which the read operation is performed in response to the refresh command REFRESH_CMD.

[0195] For example, when the operation information OP_INF includes information about the read reclaim operation, the read reclaim operation execution component 235 may output a read reclaim command RR_CMD to the memory device 100, thereby performing a read reclaim operation on a block including a page from which data is read. The memory device 100 may perform a read reclaim operation of moving data of a memory block including a page on which the read operation is performed to another memory block in response to the read reclaim command RR_CMD.

[0196] Fig. 10A and Fig. 10B It is shown by Fig. 9 A map of logical pages read by a page read command.

[0197] Reference Fig. 10A and Fig. 10B , Fig. 10A and Fig. 10B Shows when Figure 1 Threshold voltage distributions of memory cells when the memory device 100 performs a programming operation in a triple-level cell (TLC) method. Fig. 10A and Fig. 10B The horizontal axis represents the magnitude Vth of the threshold voltage of the memory cell, and Fig. 10A and Fig. 10B The vertical axis represents the serial number of the memory cell.

[0198] In one embodiment, when Figure 1 When the memory device 100 performs a program operation in the TLC method, the memory cell may have any one of the first to seventh program states PV1 to PV7 and the erase state E.

[0199] In addition, the voltage used to distinguish between the erase state E and the first programming state PV1 may be the first read voltage R1, the voltage used to distinguish between the first programming state PV1 and the second programming state PV2 may be the second read voltage R2, the voltage used to distinguish between the second programming state PV2 and the third programming state PV3 may be the third read voltage R3, the voltage used to distinguish between the third programming state PV3 and the fourth programming state PV4 may be the fourth read voltage R4, the voltage used to distinguish between the fourth programming state PV4 and the fifth programming state PV5 may be the fifth read voltage R5, the voltage used to distinguish between the fifth programming state PV5 and the sixth programming state PV6 may be the sixth read voltage R6, and the voltage used to distinguish between the sixth programming state PV6 and the seventh programming state PV7 may be the seventh read voltage R7.

[0200] exist Fig. 10A and Fig. 10B In the assumption Figure 1 The memory device 100 performs a programming operation in a TLC method, so the memory device 100 includes Figure 1 Each of the plurality of pages in the memory device 100 may include three logical pages. That is, Figure 1 Each of the plurality of pages in the memory device 100 may include a least significant bit (LSB) page, a mid-significant bit (CSB) page, and a most significant bit (MSB) page. In another embodiment, Fig. 10A and Fig. 10B Can be applied to Figure 5 The memory device 100 performs a program operation in a single-level cell (SLC) method, a multi-level cell (MLC) method, or a quad-level cell (QLC) method.

[0201] Reference Fig. 9 , Fig. 10A and Fig. 10B , Fig. 10A Shows the response to Fig. 9 The page read command PAGER_CMD reads the LSB page, and Fig. 10B Shows the response to Fig. 9 The page read command PAGER_CMD reads the LSB page and CSB page.

[0202] Reference Fig. 10A, when the page read command PAGER_CMD indicates to read only the LSB page among the logical pages included in the read page, data stored in the LSB page among the LSB page, the CSB page, and the MSB page can be read. Therefore, the read operation can be performed using the third read voltage R3 and the seventh read voltage R7.

[0203] Afterwards, the read LSB page data can be output to Fig. 9 The reference data acquisition component 237 can perform error correction on the LSB page.

[0204] Reference Fig. 10B , when the page read command PAGER_CMD instructs to read the LSB page and the CSB page among the logical pages included in the read page, data stored in the LSB page and the CSB page among the LSB page, the CSB page, and the MSB page can be read. Therefore, the read operation can be performed using the second read voltage R2, the third read voltage R3, the fourth read voltage R4, the sixth read voltage R6, and the seventh read voltage R7.

[0205] After that, the read LSB page data and CSB page data can be output to Fig. 9 The reference data acquisition component 237 may compare the error correction decoded data DEC_DATA with the LSB page data and the CSB page data to determine the number of error bits in the LSB page data and the CSB page data.

[0206] Fig.11A and Fig. 11B It is shown based on Fig. 9 A diagram of the number of error bits in the data read while performing an operation of the Page Read command.

[0207] Reference Fig. 9 , Fig. 10A , Fig. 10B , Fig.11A and Fig. 11B , Fig.11A shows that when responding to the page read command PAGER_CMD, Fig. 9 The memory device 100 generates operation information OP_INF when reading LSB page data, and Fig. 11B shows that when responding to the page read command PAGER_CMD, Fig. 9 The memory device 100 generates operation information OP_INF when reading LSB page data and CSB page data.

[0208] Reference Fig.11A , Fig. 9 The reference data acquisition component 237 can determine the number of error bits in the LSB page data by comparing the error correction decoded data DEC_DATA with the LSB page data. In addition, Fig. 9 The reference data acquisition component 237 may generate reference bit information REF_BIT_INF indicating the number of error bits based on the determination result. When the number of error bits in the LSB page data is less than the third reference value TH3 (i.e., when the value indicated by the reference bit information REF_BIT_INF is less than the third reference value TH3), the operation execution determiner 231 may determine not to perform any further operation and may not generate the operation information OP_INF.

[0209] When from Fig. 9 When the number of error bits in the LSB page data read by the memory device 100 is equal to or greater than the third reference value TH3 and less than the fourth reference value TH4 (i.e., when the value indicated by the reference bit information REF_BIT_INF is equal to or greater than the third reference value TH3 and less than the fourth reference value TH4), the operation execution determiner 231 can determine to perform the refresh operation REFRESH_OP, and can generate operation information OP_INF including information about the refresh operation REFRESH_OP.

[0210] When from Fig. 9 When the number of error bits in the LSB page data read by the memory device 100 is equal to or greater than the fourth reference value TH4 (i.e., when the value indicated by the reference bit information REF_BIT_INF is equal to or greater than the fourth reference value TH4), the operation execution determiner 231 can determine to perform a read recovery operation RR_OP, and can generate operation information OP_INF including information about the read recovery operation RR_OP.

[0211] Reference Fig. 11B , Fig. 9 The reference data acquisition component 237 can determine the number of error bits in the LSB page data and the CSB page data by comparing the error correction decoded data DEC_DATA, the LSB page data, and the CSB page data. Fig. 9 The reference data acquisition component 237 may generate reference bit information REF_BIT_INF indicating the number of error bits based on the determination result. When the number of error bits in the LSB page data is equal to or greater than the number of error bits in the CSB page data (i.e., when the reference bit information REF_BIT_INF indicates that the number of error bits in the LSB page data is equal to or greater than the number of error bits in the CSB page data), the operation execution determiner 231 may determine to perform a refresh operation REFRESH_OP, and may generate operation information OP_INF including information about the refresh operation REFRESH_OP.

[0212] When from Fig. 9When the number of error bits in the LSB page data read by the memory device 100 is less than the number of error bits in the CSB page data (i.e., when the reference bit information REF_BIT_INF indicates that the number of error bits in the LSB page data is less than the number of error bits included in the CSB page data), the operation execution determiner 231 can determine to perform a read recovery operation RR_OP, and can generate operation information OP_INF including information about the read recovery operation RR_OP.

[0213] Fig.12 Operations of the memory controller performed based on block data read according to a block read command are shown.

[0214] Fig.12 FIG. 1 shows a process of a refresh operation or a read reclaim operation performed based on block data obtained from the memory device 100 after an error correction decoding operation on the read data READ_DATA read from the memory device 100 is passed.

[0215] Reference Fig. 9 and Fig.12 , until the normal read operation controller 210 receives the read data READ_DATA corresponding to the normal read command NREAD_CMD from the memory device 100 and then outputs the error bit information ERR_BIT_INF, Fig. 9 and Fig.12 The contents are the same, so repeated description is omitted.

[0216] In one embodiment, the normal read operation controller 210 may determine the number of error bits in the read data READ_DATA and output error bit information ERR_BIT_INF indicating the number of error bits in the read data READ_DATA to the data recovery controller 230. The normal read operation controller 210 may output the error correction decoded data DEC_DATA together with the error bit information ERR_BIT_INF to the data recovery controller 230.

[0217] In one embodiment, when the reference data acquisition component 237 receives the error bit information ERR_BIT_INF from the normal read operation controller 210, the reference data acquisition component 237 may output to the memory device 100 an indication of the error bit information from the read page (eg, Figure 7 and Figure 8 The block read command BLKR_CMD reads data from all pages, odd pages, even pages, or a set number of pages in the memory block PAGE2_1). The read operation can be performed sequentially or randomly.

[0218] The memory device 100 may read data from a corresponding memory block including a read page in response to a block read command BLKR_CMD and output block read data BLKR_DATA to the reference data acquisition component 237 .

[0219] In one embodiment, the reference data acquisition component 237 may provide the block read data BLKR_DATA to the error correction execution component 220, and the error correction execution component 220 may perform an error correction decoding operation of detecting and correcting an error bit in the block read data BLKR_DATA. Thereafter, when the error correction decoding operation is passed, the error correction execution component 220 may provide the reference data acquisition component 237 with block error correction decoded data BLK_DEC_DATA obtained by correcting the error bit in the block read data BLKR_DATA.

[0220] The reference data acquisition component 237 may compare the block error correction decoded data BLK_DEC_DATA with the block read data BLKR_DATA, and generate reference bit information REF_BIT_INF based on the comparison result. The reference bit information REF_BIT_INF may indicate the number of error bits in the block read data BLKR_DATA. Specifically, the reference data acquisition component 237 may determine the number of error bits included in the block read data BLKR_DATA based on the number of changed bits among the bits included in the block read data BLKR_DATA compared to the bits included in the block error correction decoded data BLK_DEC_DATA.

[0221] In another embodiment, the reference data acquisition component 237 may determine the number of error bits included in the block read data BLKR_DATA according to decoding information received using the block error correction decoding data BLK_DEC_DATA from the error correction execution component 220. Herein, the decoding information indicates the number of error bits detected during the error correction decoding operation.

[0222] In one embodiment, based on the number of error bits in the block read data BLKR_DATA, it can be determined whether the memory block that performs the block read operation corresponding to the block read command BLKR_CMD is a page-based failure candidate or a block-based failure candidate. Here, the page-based failure candidate may indicate that some pages in the memory block may have a higher probability of failing in a future error correction decoding operation. In addition, the block-based failure candidate may indicate that most pages in the memory block may have a higher probability of failing in a future error correction decoding operation.

[0223] For example, when the number of error bits in the block read data BLKR_DATA is less than the fifth reference value, the memory block on which the operation corresponding to the block read command BLKR_CMD is performed may not be a page-based fail candidate or a block-based fail candidate.

[0224] However, when the number of error bits in the block read data BLKR_DATA is equal to or greater than the fifth reference value and less than the sixth reference value, the memory block on which the operation corresponding to the block read command BLKR_CMD is performed may be a page-based failure candidate, and when the number of error bits in the block read data BLKR_DATA is greater than the sixth reference value, the memory block on which the operation corresponding to the block read command BLKR_CMD is performed may be a block-based failure candidate. When the memory block is a page-based failure candidate, an operation corresponding to the refresh command REFRESH_CMD may be performed, and when the memory block is a block-based failure candidate, an operation corresponding to the read recovery command RR_CMD may be performed.

[0225] In one embodiment, the operation execution determiner 231 may receive reference bit information REF_BIT_INF from the reference data acquisition component 237. The reference bit information REF_BIT_INF may indicate the number of error bits in the block read data BLKR_DATA read by the block read operation corresponding to the block read command BLKR_CMD.

[0226] When the reference bit information REF_BIT_INF indicates that the memory block is a page-based fail candidate, the operation execution determiner 231 may determine to execute a refresh operation. Conversely, when the reference bit information REF_BIT_INF indicates that the memory block is a block-based fail candidate, the operation execution determiner 231 may determine to execute a read reclaim operation.

[0227] The operation execution determiner 231 may provide operation information OP_INF regarding the determined operation to the refresh operation execution component 233 and the read reclaim operation execution component 235 .

[0228] In one embodiment, the refresh operation execution component 233 and the read reclaim operation execution component 235 may output commands based on the operation information OP_INF received from the operation execution determiner 231 .

[0229] For example, when the operation information OP_INF includes information about the refresh operation, the refresh operation execution component 233 may output a refresh command REFRESH_CMD to the memory device 100 to refresh the page on which the normal read operation is performed. The memory device 100 may perform a refresh operation on the page on which the normal read operation is performed in response to the refresh command REFRESH_CMD.

[0230] For example, when the operation information OP_INF includes information about the read reclaim operation, the read reclaim operation execution component 235 may output a read reclaim command RR_CMD to the memory device 100, thereby performing a read reclaim operation on the memory block on which the block read operation is performed. The memory device 100 may perform a read reclaim operation of moving data of the memory block on which the block read operation is performed to another memory block in response to the read reclaim command RR_CMD.

[0231] FIG. 13A to FIG. 13D is shown corresponding to Fig.12 A diagram of the operation of a block read command.

[0232] Reference Fig.12 and FIG. 13A to FIG. 13D , FIG. 13A to FIG. 13D Show Fig.12 The second memory block BLK2 among the first to fourth memory blocks BLK1 to BLK4 in the memory cell array 110. FIG. 13A to FIG. 13D , it is assumed that a normal read operation is performed on the (2_1)th page PAGE2_1 among the pages in the second memory block BLK2 in response to the normal read command NREAD_CMD, and an error correction decoding operation of the normal read data is passed.

[0233] Reference Fig.12 and FIG. 13A to FIG. 13D , after the error correction decoding operation on page (2_1) PAGE2_1 is passed, Fig.12 The memory device 100 may be from Fig.12 The reference data acquisition component 237 receives the block read command BLKR_CMD.

[0234] The memory device 100 may be Fig.12 The reference data acquisition component 237 outputs block read data BLKR_DATA obtained by reading all pages, odd pages, even pages, or a set number of pages in the memory block including the (2_1)th page PAGE2_1 on which the normal read operation is performed. The block read command BLKR_CMD may be a command output to determine whether the memory block including the page on which the normal read operation is performed is a block-based failure candidate or a page-based failure candidate.

[0235] Fig.13A Show Fig.12 The memory device 100 reads all pages (ie, the (2_1)th page PAGE2_1 to the (2_4)th page PAGE2_4) in the second memory block BLK2 in response to the block read command BLKR_CMD. Fig.12 The memory device 100 may read the pages sequentially or randomly.

[0236] For example, Fig.12 The memory device 100 may sequentially read from the (2_1)th page PAGE2_1 to the (2_4)th page PAGE2_4, or may randomly read from the (2_1)th page PAGE2_1 to the (2_4)th page PAGE2_4.

[0237] Fig. 13B Show Fig.12 The memory device 100 reads an odd page among all pages in the second memory block BLK2 including the (2_1)th page PAGE2_1 in response to the block read command BLKR_CMD. That is, Fig.12 The memory device 100 may read the (2_1)th page PAGE2_1 and the (2_3)th page PAGE2_3 which are odd pages in response to the block read command BLKR_CMD.

[0238] Fig. 13C Show Fig.12 The memory device 100 reads even pages among all pages in the second memory block BLK2 including the (2_1)th page PAGE2_1 in response to the block read command BLKR_CMD. That is, Fig.12 The memory device 100 may read the (2_2)th page PAGE2_2 and the (2_4)th page PAGE2_4 which are even pages in response to the block read command BLKR_CMD.

[0239] Fig.13D Show Fig.12 The memory device 100 reads a set number of pages among all pages in the second memory block BLK2 including the (2_1)th page PAGE2_1 in response to the block read command BLKR_CMD.

[0240] For example, when the number of pages to be read in response to the block read command BLKR_CMD is set to "2", Fig.12 The memory device 100 can randomly select and read two pages among the pages in the second memory block BLK2. Fig.13D middle, Fig.12 The two pages randomly selected and read by the memory device 100 may be the (2_1)th page PAGE2_1 and the (2_4)th page PAGE2_4.

[0241] As mentioned above, Fig.12 The memory device 100 may be from Fig.12 The reference data acquisition component 237 receives the block read command BLKR_CMD, performs a block read operation in response to the received block read command BLKR_CMD, and sends a block read command to the reference data acquisition component 237. Fig.12The reference data acquisition component 237 outputs block read data BLKR_DATA as a result of performing a block read operation.

[0242] After that, Fig.12 The reference data acquisition component 237 may output the block read data BLKR_DATA to the error correction execution component 220. As a result of performing the error correction decoding operation by outputting the block read data BLKR_DATA to the error correction execution component 220, it may be determined whether the memory block including the page on which the normal read operation was performed is a page-based failure candidate or a block-based failure candidate based on the number of error bits in the block read data BLKR_DATA. The page-based failure candidate may indicate that some pages in the memory block may have a higher probability of failing in a future error correction decoding operation. In addition, the block-based failure candidate may indicate that most pages in the memory block may have a higher probability of failing in a future error correction decoding operation.

[0243] In one embodiment, when a memory block including a page on which a normal read operation is performed is a block-based failure candidate, Fig.12 The memory device 100 may be Figure 7 As shown, a read reclaim operation is performed on the corresponding memory block.

[0244] However, when a memory block including a page on which a normal read operation is performed is a page-based failure candidate, Fig.12 The memory device 100 may be Figure 8 As shown, a refresh operation is performed on the page on which a normal read operation is performed.

[0245] Fig.14 It is shown based on Fig.12 A diagram of the Block Read command operation performed while the number of error bits in the read data.

[0246] Reference Fig.12 and Fig.14 , Fig.14 The first column represents the Fig.12 The reference bit information REF_BIT_INF output by the reference data acquisition component 237 belongs to each range, and Fig.14 The second column represents various operation information OP_INF each aligned with a corresponding range (to which the reference bit information REF_BIT_INF belongs).

[0247] In one embodiment, when the error correction decoding operation of the block read data BLKR_DATA read from the memory device 100 passes, Fig.12 The reference data acquisition component 237 may determine the number of error bits in the block read data BLKR_DATA.

[0248] Can be based on Fig.12 The reference bit information REF_BIT_INF is generated based on the number of error bits determined by the reference data acquisition component 237. The reference bit information REF_BIT_INF may indicate the number of error bits included in the block read data BLKR_DATA.

[0249] In one embodiment, when the reference bit information REF_BIT_INF is less than the fifth reference value TH5, the memory block including the page on which the normal read operation is performed may not be a page-based failure candidate or a block-based failure candidate. Fig.12 The operation execution determiner 231 may determine not to execute any further operation and may not generate the operation information OP_INF.

[0250] In one embodiment, when the reference bit information REF_BIT_INF is equal to or greater than the fifth reference value TH5 and less than the sixth reference value TH6, the memory block including the page on which the normal read operation is performed may be a page-based failure candidate. Fig.12 The operation execution determiner 231 may determine to execute a refresh operation, and may generate operation information OP_INF including information about the refresh operation REFRESH_OP. Thereafter, Fig.12 The refresh operation execution component 233 can send a refresh operation to the refresh operation execution component 233 based on the received operation information OP_INF. Fig.12 The memory device 100 outputs a refresh command REFRESH_CMD, thereby Figure 5 The memory device 100 performs a refresh operation.

[0251] In one embodiment, when the reference bit information REF_BIT_INF is equal to or greater than the sixth reference value TH6, the memory block including the page on which the normal read operation is performed may be a block-based failure candidate. Fig.12 The operation execution determiner 231 may determine to perform a read recovery operation, and may generate operation information OP_INF including information about the read recovery operation RR_OP. Thereafter, Fig.12 The read recovery operation execution component 235 can send a read recovery operation to the Fig.12 The memory device 100 outputs a read recovery command RR_CMD, thereby Figure 5 The memory device 100 performs a read reclaim operation.

[0252] Fig.15 is a diagram illustrating the operation of a memory controller according to one embodiment of the present disclosure.

[0253] Reference Fig.15In operation S1501, the memory controller may perform error correction on data read by a normal read operation performed in response to a normal read command. For example, the memory controller may detect an error bit in the read data and perform an error correction decoding operation on the detected error bit.

[0254] In operation S1503, the memory controller may determine whether the error correction decoding operation passes. When it is determined that the error correction decoding operation passes (yes), the flow may proceed to operation S1505.

[0255] In operation S1505 , the memory controller may output a refresh command or a read reclaim command based on the number of error bits in the read data.

[0256] According to an embodiment of the present disclosure, even if the error correction decoding operation of the normal read operation passes, a read recovery operation or a refresh operation is performed on the page where the normal read operation is performed according to the number of error bits in the normal read operation, thereby improving data reliability.

[0257] Fig.16 is a diagram illustrating the operation of a memory controller according to one embodiment of the present disclosure.

[0258] Fig.16 is a flowchart illustrating operation S1505 in more detail.

[0259] In operation S1601, the memory controller may determine whether the number of error bits in the data read by the normal read operation is less than the first reference value. When the number of error bits in the data read by the normal read operation is not less than the first reference value (No), the operation may proceed to operation S1603.

[0260] In operation S1603 , the memory controller may determine whether the number of error bits in data read through a normal read operation is equal to or greater than a first reference value and less than a second reference value.

[0261] When the number of error bits in the data read by a normal read operation is equal to or greater than the first reference value and less than the second reference value (Yes), the operation can proceed to operation S1605, and when the number of error bits in the data read by a normal read operation is equal to or greater than the first reference value and not less than the second reference value (No) (i.e., equal to or greater than the second reference value), the process can proceed to operation S1607.

[0262] In operation S1605, the memory controller may output a refresh command for refreshing the page on which the normal read operation is performed. In one embodiment, when the number of error bits in the data read by the normal read operation is within a specific range, a refresh operation may be performed on the corresponding page, thereby improving data reliability.

[0263] In operation S1607, the memory controller may output a read recovery command to perform a read recovery operation on a block including a page on which a normal read operation is performed. In one embodiment, when the number of error bits in the data read by the normal read operation is large, a read recovery operation may be performed on a block including a corresponding page, thereby improving data reliability.

[0264] Fig.17 is a diagram illustrating the operation of a memory controller according to one embodiment of the present disclosure.

[0265] Reference Fig.15 and Fig.17 , Fig.17 is a flowchart illustrating operation S1505 in more detail. Fig.17 1 shows an operation after performing a read operation corresponding to a page read command output from a memory controller after an error correction decoding operation for a normal read operation is passed. The page read command may be an instruction to read a page (e.g., Figure 7 and Figure 8 A command to read data from the LSB page or both the LSB page and the CSB page among each logical page in PAGE2_1).

[0266] In operation S1701, it may be determined whether the number of error bits of LSB page data in the memory device is less than the number of error bits of CSB page data.

[0267] When the number of error bits of the LSB page data is not less than the number of error bits of the CSB page data (No) (i.e., when the number of error bits of the LSB page data is equal to or greater than the number of error bits of the CSB page data), the process can proceed to operation S1703, and when the number of error bits of the LSB page data is less than the number of error bits of the CSB page data (Yes), the process can proceed to operation S1705.

[0268] In operation S1703, the memory controller may output a refresh command to the memory device. That is, when the number of error bits of the LSB page data is equal to or greater than the number of error bits of the CSB page data, the memory controller may output a refresh command to the memory device to perform a refresh operation on the page on which the normal read operation is performed.

[0269] In operation S1705, the memory controller may output a read reclaim command to the memory device. That is, when the number of error bits of the LSB page data is less than the number of error bits of the CSB page data, the memory controller may output a read reclaim command to the memory device, thereby performing a read reclaim operation on the block including the page on which the normal read operation is performed.

[0270] Fig.18 is a diagram illustrating the operation of a memory controller according to one embodiment of the present disclosure.

[0271] Reference Fig.15 and Fig.18 , Fig.18 is a flowchart illustrating operation S1505 in more detail. Fig.18 The diagram shows an operation after a block read operation corresponding to a block read command output from a memory controller is performed after an error correction decoding operation for a normal read operation is passed. The block read command may be a command instructing to read all pages, only odd pages, only even pages, or a set number of pages in a memory block including pages that have passed the error correction decoding operation.

[0272] In operation S1801, the memory controller may determine whether the number of error bits in the block read data is less than a fifth reference value. When the number of error bits included in the block read data is not less than the fifth reference value (N), the flow proceeds to operation S1803.

[0273] In operation S1803, the memory controller may determine whether the number of error bits in the block read data is equal to or greater than the fifth reference value and less than the sixth reference value. When the number of error bits in the block read data is equal to or greater than the fifth reference value and less than the sixth reference value (Yes), the process may proceed to operation S1805, and when the number of error bits in the block read data is greater than the fifth reference value and not less than the sixth reference value (No) (i.e., equal to or greater than the sixth reference value), the process may proceed to operation S1809.

[0274] In operation S1805, the memory controller may select a memory block including pages that passed in an error correction decoding operation as a page-based failure candidate. The page-based failure candidate may indicate that some pages in the memory block may have a high probability of failing in future error correction decoding operations.

[0275] In operation S1807 , when a memory block is selected as a page-based fail candidate, the memory controller may output a refresh command to the memory device so as to perform a refresh operation on the page passed in the error correction decoding operation.

[0276] In operation S1809, the memory controller may select a memory block including pages that passed the error correction decoding operation as a block-based failure candidate. The block-based failure candidate may indicate that there is a high probability that most pages in the memory block may fail in future error correction decoding operations.

[0277] In operation S1811 , when a memory block is selected as a block-based fail candidate, the memory controller may output a read reclaim command to the memory device to perform a read reclaim operation on the memory block including the page passed in the error correction decoding operation.

[0278] Fig.19 It is shown Figure 1 FIG. 1 is a diagram of another embodiment of a memory controller.

[0279] The memory controller 1000 is connected to the host and the memory device. The memory controller 1000 is configured to access the memory device in response to a request from the host. For example, the memory controller 1000 is configured to control the write operation, read operation, erase operation and background operation of the memory device. The memory controller 1000 is configured to provide an interface between the memory device and the host. The memory controller 1000 is configured to drive firmware for controlling the memory device.

[0280] Reference Fig.19 , the memory controller 1000 may include a processor 1010 , a memory buffer 1020 , an error correction circuit (ECC) 1030 , a host interface 1040 , a buffer controller (or a buffer control circuit) 1050 , a memory interface 1060 , and a bus 1070 .

[0281] The bus 1070 may be configured to provide a channel between the components of the memory controller 1000 .

[0282] The processor 1010 may control the overall operation of the memory controller 1000 and may perform a logic operation. The processor 1010 may communicate with an external host through a host interface 1040 and communicate with a memory device through a memory interface 1060. In addition, the processor 1010 may communicate with a memory buffer 1020 through a buffer controller 1050. The processor 1010 may control the operation of the memory device using the memory buffer 1020 as an operating memory, a cache memory, or a buffer memory.

[0283] The processor 1010 may perform the function of the FTL. The processor 1010 may convert the LBA provided by the host into the PBA through the FTL. The FTL may receive the LBA and convert the LBA into the PBA using a mapping table. The flash translation layer may perform the conversion using any of various address mapping methods (e.g., page mapping, block mapping, or hybrid mapping). Which method is selected depends on the mapping unit.

[0284] The processor 1010 is configured to randomize data received from the host. For example, the processor 1010 may use a randomization seed to randomize the data received from the host. The randomized data is provided to the memory device as data to be stored and is programmed into the memory cell array.

[0285] The processor 1010 may perform randomization and de-randomization through driver software or firmware.

[0286] The memory buffer 1020 may be used as an operation memory, a cache memory, or a buffer memory of the processor 1010. The memory buffer 1020 may store codes and commands executed by the processor 1010. The memory buffer 1020 may store data processed by the processor 1010. The memory buffer 1020 may include a static RAM (SRAM) or a dynamic RAM (DRAM).

[0287] The error correction circuit 1030 may perform error correction. The error correction circuit 1030 may perform error correction encoding (ECC encoding) based on data to be written to the memory device through the memory interface 1060. The error correction encoded data may be transmitted to the memory device through the memory interface 1060. The error correction circuit 1030 may perform error correction decoding (ECC decoding) on ​​the data received from the memory device through the memory interface 1060. For example, the error correction circuit 1030 may be included in the memory interface 1060 as a component of the memory interface 1060.

[0288] In one embodiment, when Figure 1 When the memory device 100 performs a read operation, the error correction circuit 1030 may Figure 1 The memory device 100 performs an error correction decoding operation on the data read.

[0289] In one embodiment of the present disclosure, even if the error correction decoding operation on the read data passes, a read recovery operation or a refresh operation can be performed according to the number of error bits included in the read data to solve the problem of the recovery operation previously adopted, that is, the recovery operation involves many read operations and the data may still not be recovered.

[0290] For example, the processor 1010 may determine the number of error bits in the data read by the normal read operation based on the error correction decoding data, and may determine to perform a read recovery operation or a refresh operation based on the determination result. Alternatively, the number of error bits may also be determined based on the result of error correction decoding of data read in addition to the data read by the normal read operation, and may determine to perform a read recovery operation or a refresh operation based on the determination result.

[0291] In one embodiment, the processor 1010 may Figure 1 The memory device 100 outputs a read recovery command or a refresh command, thereby Figure 1 The memory device 100 performs the determined operation.

[0292] The host interface 1040 is configured to communicate with an external host under the control of the processor 1010. The host interface 1040 may be configured to perform communication using at least one of various communication methods such as a universal serial bus (USB), a serial AT attachment (SATA), a serial attached SCSI (SAS), a high-speed inter-chip (HSIC), a small computer system interface (SCSI), a peripheral component interconnect (PCI), a non-volatile memory express (NVMe), a universal flash storage (UFS), a secure digital (SD), a multimedia card (MMC), an embedded MMC (eMMC), a dual in-line memory module (DIMM), a registered DIMM (RDIMM), and / or a load reduction DIMM (LRDIMM).

[0293] The buffer controller 1050 is configured to control the memory buffer 1020 under the control of the processor 1010 .

[0294] The memory interface 1060 is configured to communicate with the memory device under the control of the processor 1010. The memory interface 1060 may exchange commands, addresses, and data with the memory device through a channel.

[0295] For example, the memory controller 1000 may not include the memory buffer 1020 and the buffer controller 1050. Instead, the memory buffer 1020 and the buffer controller 1050 may be separate devices or one single integrated device.

[0296] For example, the processor 1010 may use the code to control the operation of the memory controller 1000. The processor 1010 may load the code from a nonvolatile memory device (eg, a read-only memory) provided inside the memory controller 1000. As another example, the processor 1010 may load the code from the memory device through the memory interface 1060.

[0297] For example, the bus 1070 of the memory controller 1000 may be divided into a control bus and a data bus. The data bus may be configured to transmit data within the memory controller 1000, and the control bus may be configured to transmit control information such as commands and addresses within the memory controller 1000. The data bus and the control bus may be separated from each other so as not to interfere or affect each other. The data bus may be connected to the host interface 1040, the buffer controller 1050, the error correction circuit 1030, and the memory interface 1060. The control bus may be connected to the host interface 1040, the processor 1010, the buffer controller 1050, the memory buffer 1020, and the memory interface 1060.

[0298] Fig. 20 is a block diagram illustrating a memory card system to which a storage device is applied according to one embodiment of the present disclosure.

[0299] Reference Fig. 20 , the memory card system 2000 includes a memory controller 2100 , a memory device 2200 , and a connector 2300 .

[0300] The memory controller 2100 is connected to the memory device 2200. The memory controller 2100 is configured to access the memory device 2200. For example, the memory controller 2100 is configured to control the read operation, write operation, erase operation, and background operation of the memory device 2200. The memory controller 2100 is configured to provide an interface between the memory device 2200 and the host. The memory controller 2100 is configured to drive firmware for controlling the memory device 2200. The memory device 2200 may be controlled by Figure 1 The memory device 100 is implemented as shown in FIG.

[0301] For example, the memory controller 2100 may include components such as a random access memory (RAM), a processor, a host interface, a memory interface, and an error correction circuit.

[0302] The memory controller 2100 may communicate with an external device through the connector 2300. The memory controller 2100 may communicate with an external device (e.g., a host) according to a specific communication standard. For example, the memory controller 2100 may be configured to communicate with an external device through at least one of various communication standards such as a universal serial bus (USB), a multimedia card (MMC), an embedded MMC (MCM), a peripheral component interconnect (PCI), PCI Express (PCI-E), an advanced technology attachment (ATA), a serial ATA, a parallel ATA, a small computer system interface (SCSI), an enhanced small disk interface (ESDI), an integrated drive electronics device (IDE), FireWire, a universal flash storage (UFS), Wi-Fi, Bluetooth, and / or NVMe. For example, the connector 2300 may be defined by at least one of the various communication standards described above.

[0303] For example, the memory device 2200 can be implemented as any of a variety of non-volatile memory elements such as electrically erasable and programmable ROM (EEPROM), NAND flash memory, NOR flash memory, phase change RAM (PRAM), resistive RAM (ReRAM), ferroelectric RAM (FRAM) and / or spin transfer torque magnetic RAM (STT-MRAM).

[0304] The memory controller 2100 and the memory device 2200 can be integrated into one semiconductor device to constitute a memory card, such as a PC card (Personal Computer Memory Card International Association (PCMCIA)), a Compact Flash card (CF), a Smart Media Card (SM or SMC), a Memory Stick, a MultiMedia Card (MMC, RS-MMC, MMCmicro or eMMC), an SD card (SD, mini SD, micro SD or SDHC) and / or Universal Flash Storage (UFS).

[0305] In one embodiment, when the memory device 2200 performs a read operation, the memory controller 2100 may perform an error correction decoding operation on data read from the memory device 2200 .

[0306] In one embodiment of the present disclosure, even if the error correction decoding operation on the read data passes, a read recovery operation or a refresh operation may be performed according to the number of error bits in the read data to solve the above-mentioned problem of the recovery operation previously adopted.

[0307] For example, the memory controller 2100 may determine the number of error bits in the data read by the normal read operation based on the error correction decoding data, and may determine to perform a read recovery operation or a refresh operation based on the determination result. Alternatively, the number of error bits may be determined based on the result of error correction decoding of data read in addition to the data read by the normal read operation, and may determine to perform a read recovery operation or a refresh operation based on the determination result.

[0308] In one implementation, the memory controller 2100 may output a read reclaim command or a refresh command to the memory device 2200 , thereby performing the determined operation on the memory device 2200 .

[0309] Fig.21 is a block diagram illustrating a solid state drive (SSD) system to which a storage device is applied according to one embodiment of the present disclosure.

[0310] Reference Fig.21 , the SSD system 3000 includes a host 3100 and an SSD 3200. The SSD 3200 exchanges a signal SIG with the host 3100 through a signal connector 3001, and receives power PWR through a power connector 3002. The SSD 3200 includes an SSD controller 3210, a plurality of flash memories 3221 to 322n, an auxiliary power supply device 3230, and a buffer memory 3240.

[0311] In one embodiment, the SSD controller 3210 may perform Figure 1 The functions of the memory controller 200 are as follows.

[0312] The SSD controller 3210 may control the plurality of flash memories 3221 to 322n in response to a signal SIG received from the host 3100. For example, the signal SIG may be a plurality of signals based on an interface between the host 3100 and the SSD 3200. For example, the signal SIG may be defined by at least one of an interface such as a universal serial bus (USB), a multimedia card (MMC), an embedded MMC (MCM), a peripheral component interconnect (PCI), PCI Express (PCI-E), an advanced technology attachment (ATA), a serial ATA, a parallel ATA, a small computer system interface (SCSI), an enhanced small disk interface (ESDI), an integrated drive electronics (IDE), a firewire, a universal flash storage (UFS), Wi-Fi, Bluetooth, and / or NVMe.

[0313] In one embodiment, when the flash memories 3221 to 322n perform a read operation, the SSD controller 3210 may perform an error correction decoding operation on data read from the flash memories 3221 to 322n.

[0314] In one embodiment of the present disclosure, even if the error correction decoding operation on the read data passes, a read recovery operation or a refresh operation may be performed according to the number of error bits in the read data to solve the above-mentioned problem of the recovery operation previously adopted.

[0315] For example, the SSD controller 3210 may determine the number of error bits in the data read by the normal read operation based on the error correction decoding data, and may determine to perform a read recovery operation or a refresh operation based on the determination result. Alternatively, the number of error bits may be determined based on the result of error correction decoding of data read in addition to the data read by the normal read operation, and may determine to perform a read recovery operation or a refresh operation based on the determination result.

[0316] In one implementation, the SSD controller 3210 may output a read reclaim command or a refresh command to the flash memories 3221 to 322n, thereby performing the determined operation on the flash memories 3221 to 322n.

[0317] The auxiliary power supply device 3230 is connected to the host 3100 through the power connector 3002. The auxiliary power supply device 3230 can receive power PWR from the host 3100 and can charge the power. When the power from the host 3100 is not smoothly supplied, the auxiliary power supply device 3230 can provide power to the SSD 3200. For example, the auxiliary power supply device 3230 can be set inside or outside the SSD 3200. For example, the auxiliary power supply device 3230 can be set on the mainboard and can provide auxiliary power to the SSD 3200.

[0318] The buffer memory 3240 operates as a buffer memory of the SSD 3200. For example, the buffer memory 3240 may temporarily store data received from the host 3100 or data received from the plurality of flash memories 3221 to 322n, or may temporarily store metadata (e.g., a mapping table) of the flash memories 3221 to 322n. The buffer memory 3240 may include a volatile memory such as DRAM, SDRAM, DDR SDRAM, LPDDR SDRAM, and GRAM, or a nonvolatile memory such as FRAM, ReRAM, STT-MRAM, and PRAM.

[0319] Fig. 22 is a block diagram illustrating a user system to which a storage device is applied according to one embodiment of the present disclosure.

[0320] Reference Fig. 22 , the user system 4000 includes an application processor 4100 , a memory module 4200 , a network module 4300 , a storage module 4400 , and a user interface 4500 .

[0321] The application processor 4100 may drive components included in the user system 4000, an operating system (OS), or a user program, etc. For example, the application processor 4100 may include a controller, an interface, and a graphic engine, etc., which control components included in the user system 4000. The application processor 4100 may be provided as a system on chip (SoC).

[0322] The memory module 4200 may operate as a main memory, an operating memory, a buffer memory, or a cache memory of the user system 4000. The memory module 4200 may include a volatile random access memory such as DRAM, SDRAM, DDR SDRAM, DDR2 SDRAM, DDR3 SDRAM, LPDDR SDRAM, LPDDR2 SDRAM, and LPDDR3 SDRAM, or a nonvolatile random access memory such as PRAM, ReRAM, MRAM, and FRAM. For example, the application processor 4100 and the memory module 4200 may be packaged based on a package-on-package (PoP) and provided as one semiconductor package.

[0323] The network module 4300 can communicate with external devices. For example, the network module 4300 can support wireless communications such as code division multiple access (CDMA), global system for mobile communications (GSM), wideband CDMA (WCDMA), CDMA-2000, time division multiple access (TDMA), long term evolution, Wimax, WLAN, UWB, Bluetooth, and Wi-Fi. For example, the network module 4300 may be included in the application processor 4100.

[0324] The storage module 4400 may store data. For example, the storage module 4400 may store data received from the application processor 4100. Alternatively, the storage module 4400 may send the data stored in the storage module 4400 to the application processor 4100. For example, the storage module 4400 may be implemented as a non-volatile semiconductor memory element such as a phase change RAM (PRAM), a magnetic RAM (MRAM), a resistive RAM (RRAM), a NAND flash memory, a NOR flash memory, and a three-dimensional NAND flash memory. For example, the storage module 4400 may be set as a removable storage device (removable drive) such as a memory card, and an external drive of the user system 4000.

[0325] For example, the storage module 4400 may include a plurality of non-volatile memory devices, each of which may be associated with a reference Figure 2 and Figure 3 The storage module 4400 may be similar to the memory device described in the Figure 1 The described storage device 50 operates identically.

[0326] In one implementation, when the storage module 4400 performs a read operation, the application processor 4100 may perform an error correction decoding operation on data read from the storage module 4400 .

[0327] In one embodiment of the present disclosure, even if the error correction decoding operation on the read data passes, a read recovery operation or a refresh operation may be performed according to the number of error bits in the read data to solve the above-mentioned problem of the recovery operation previously adopted.

[0328] For example, the application processor 4100 may determine the number of error bits in the data read by the normal read operation based on the error correction decoding data, and may determine to perform a read recovery operation or a refresh operation based on the determination result. Alternatively, the number of error bits may be determined based on the result of error correction decoding of data read in addition to the data read by the normal read operation, and may determine to perform a read recovery operation or a refresh operation based on the determination result.

[0329] In one implementation, the application processor 4100 may output a read reclaim command or a refresh command to the memory module 4400 , thereby performing the determined operation on the memory module 4400 .

[0330] The user interface 4500 may include an interface for inputting data or instructions to the application processor 4100 or for outputting data to an external device. For example, the user interface 4500 may include a user input interface such as a keyboard, a keypad, a button, a touch panel, a touch screen, a touch pad, a touch ball, a camera, a microphone, a gyro sensor, a vibration sensor, and a piezoelectric element. The user interface 4500 may include a user output interface such as a liquid crystal display (LCD), an organic light emitting diode (OLED) display device, an active matrix OLED (AMOLED) display device, an LED, a speaker, and a monitor.

[0331] Although the present invention has been shown and described for various embodiments, it will be understood by those skilled in the art in view of this disclosure that various changes can be made to any embodiment in the disclosed embodiments within the spirit and scope of the present invention. The present invention encompasses all such changes as long as they fall within the scope of the claims.

[0332] CROSS-REFERENCE TO RELATED APPLICATIONS

[0333] This application claims the priority of Korean Patent Application No. 10-2020-0109099 filed on August 28, 2020, in the Korean Intellectual Property Office, the disclosure of which is incorporated herein by reference in its entirety.

Claims

1. A memory system, comprising: a memory device, the memory device comprising a plurality of pages; as well as a memory controller configured to correct errors in read data obtained by reading a selected page among the plurality of pages, and determine whether to perform a refresh operation on the selected page or a read reclaim operation on a block including the selected page based on a number of error bits in the read data; Wherein, the memory controller comprises: a normal read operation controller configured to control a read operation on the selected page and determine the number of error bits in the read data; an error correction execution component configured to correct the read data; and a data recovery controller configured to control the refresh operation on the selected page based on the number of error bits in the read data when the error in the read data is corrected, wherein the data recovery controller performs the refresh operation when the number of error bits is equal to or greater than a first reference value and less than a second reference value, and performs the read recovery operation when the number of error bits is equal to or greater than the second reference value, and Wherein, the second reference value is greater than the first reference value.

2. The memory system according to claim 1, wherein: The data recovery controller controls the refresh operation on the selected page only when an error correction decoding operation performed by the error correction execution component to correct the error in the read data passes.

3. The memory system according to claim 1, in, The normal read operation controller is further configured to provide the read data to the error correction execution component to correct the error in the read data, wherein the error correction execution component corrects the error in the read data by an error correction decoding operation, and Wherein, the error correction execution component is further configured to generate error correction decoding data when the error correction decoding operation is passed, and provide the error correction decoding data to the normal read operation controller.

4. The memory system according to claim 3, in, The normal read operation controller determines the number of error bits in the read data by comparing the read data with the error correction decoded data, and The normal read operation controller is further configured to output error bit information indicating the number of error bits based on the determined result.

5. The memory system according to claim 1, wherein: The data recovery controller comprises: an operation execution determiner configured to receive error bit information indicating the number of error bits from the normal read operation controller after an error correction decoding operation to correct the error in the read data is passed, determine whether to perform the refresh operation on the selected page or the read reclaim operation on a block including the selected page based on the error bit information, and generate operation information related to the determined operation; a refresh operation execution component configured to output a refresh command based on the operation information, thereby executing the refresh operation on the selected page; and A read reclaim operation execution component is configured to output a read reclaim command based on the operation information, thereby executing the read reclaim operation on the block.

6. The memory system according to claim 5, in, When the error bit information indicates that the number of error bits is equal to or greater than the first reference value and less than the second reference value, the operation performance determiner generates the operation information indicating the refresh operation.

7. The memory system according to claim 6, wherein: When the error bit information indicates that the number of error bits is equal to or greater than the second reference value, the operation performance determiner generates the operation information indicating the read reclaim operation.

8. The memory system according to claim 5, wherein: The data recovery controller also includes a reference data acquisition component, which is configured to control the read operation after receiving the error bit information indicating the number of error bits and error correction decoding data according to the error correction decoding operation from the normal read operation controller when the error correction decoding operation to correct the error in the read data is passed.

9. The memory system according to claim 8, wherein: The reference data acquisition component is further configured to output a page read command to the memory device instructing to read at least one logical page of the selected pages.

10. The memory system according to claim 9, wherein: The reference data acquisition component is further configured to receive least significant bit page data among the respective logical pages in the selected page, the least significant bit page data being output from the memory device in response to the page read command.

11. The memory system according to claim 10, wherein: The reference data acquisition component is further configured to output reference bit information indicating the number of error bits in the least significant bit page data based on a comparison result obtained by comparing the least significant bit page data with the error correction decoded data, and The operation execution determiner determines whether to execute the refresh operation or the read reclaim operation based on the error bit information and the reference bit information.

12. The memory system according to claim 9, wherein: The reference data acquisition component is further configured to receive least significant bit page data and middle significant bit page data among the respective logical pages in the selected pages, the least significant bit page data and the middle significant bit page data being output from the memory device in response to the page read command.

13. The memory system according to claim 12, wherein: The reference data acquisition component is further configured to output reference bit information indicating the number of error bits in the least significant bit page data and the number of error bits in the middle significant bit page data based on a comparison result obtained by comparing the number of error bits in the least significant bit page data with the number of error bits in the middle significant bit page data, and The operation execution determiner determines whether to execute the refresh operation or the read reclaim operation based on the error bit information and the reference bit information.

14. The memory system according to claim 8, wherein: The reference data acquisition component is further configured to output a block read command to the memory device instructing to read at least one page in a memory block including the selected page.

15. The memory system of claim 14, wherein: The reference data acquisition component is further configured to output block read data read in response to the block read command to the error correction execution component, and receive block error correction decoded data obtained by correcting error bits in the block read data from the error correction execution component.

16. The memory system of claim 15, wherein: The reference data acquisition component is further configured to determine the number of error bits in the block read data by comparing the block read data and the block error correction decoded data, and output reference bit information indicating whether the memory block including the selected page is a page-based failure candidate or a block-based failure candidate based on the determined result, and The operation execution determiner determines to execute the refresh operation or the read reclaim operation based on the error bit information and the reference bit information.

17. The memory system of claim 16, wherein: The page-based failure candidates refer to memory block candidates in which pages below a reference value in the memory block including the selected page will fail in future error correction operations, and the block-based failure candidates refer to memory block candidates in which pages above the reference value in the memory block including the selected page will fail in future error correction operations.

18. The memory system of claim 16, wherein: When the reference bit information indicates the page-based fail candidate, the operation execution determiner generates the operation information indicating the refresh operation.

19. The memory system of claim 16, wherein: When the reference bit information indicates the block-based fail candidate, the operation execution determiner generates the operation information indicating the read reclaim operation.

20. A method of operating a memory system, the memory system comprising a memory device and a memory controller, the memory device comprising a plurality of pages, and the memory controller being configured to correct errors in read data obtained by reading a selected page among the plurality of pages, and determine whether to perform a refresh operation on the selected page or a read reclaim operation on a block including the selected page based on the number of error bits in the read data, the method comprising the steps of: reading the selected page to obtain the read data; Correcting the error in the read data; determining the number of the error bits in the read data when correction of the error in the read data passes; When the number of error bits is equal to or greater than a first reference value and less than a second reference value, performing the refresh operation, and The read recovery operation is performed when the number of error bits is equal to or greater than the second reference value, Wherein, the second reference value is greater than the first reference value.

21. A memory controller, the memory controller controlling a memory device including a plurality of pages, the memory controller comprising: a normal read operation controller configured to control a read operation on a selected page among the plurality of pages and determine a number of error bits in read data read from the memory device during the read operation; an error correction execution component configured to correct errors in the read data; as well as a data recovery controller configured to control a refresh operation on the selected page or a read reclaim operation on a block including the selected page based on the number of error bits in the read data when the error in the read data is corrected, wherein the data recovery controller performs the refresh operation when the number of error bits is equal to or greater than a first reference value and less than a second reference value, and performs the read recovery operation when the number of error bits is equal to or greater than the second reference value, and Wherein, the second reference value is greater than the first reference value.

22. A method for operating a controller, the method comprising the following steps: Provide the host with the read data that has been successfully read from the page; controlling a memory device to selectively perform a refresh operation on the page or a read reclaim operation on a block including the page based on the number of error bits detected in the read data; When the number of error bits is equal to or greater than a first reference value and less than a second reference value, performing the refresh operation, and The read recovery operation is performed when the number of error bits is equal to or greater than the second reference value, Wherein, the second reference value is greater than the first reference value.

23. A method for operating a controller, the method comprising the following steps: Provide the host with the read data that has been successfully read from the page; controlling the memory device to read block data from two or more pages in a block including the page; detecting the number of error bits in the block data; controlling the memory device to selectively perform a refresh operation on the page or a read reclaim operation on the block based on the number of the error bits detected in the block data, When the number of error bits is equal to or greater than a first reference value and less than a second reference value, performing the refresh operation, and The read recovery operation is performed when the number of error bits is equal to or greater than the second reference value.