US20200051647A1 - Memory system with memory region read counts and a memory group read count and operating method thereof - Google Patents
Memory system with memory region read counts and a memory group read count and operating method thereof Download PDFInfo
- Publication number
- US20200051647A1 US20200051647A1 US16/221,956 US201816221956A US2020051647A1 US 20200051647 A1 US20200051647 A1 US 20200051647A1 US 201816221956 A US201816221956 A US 201816221956A US 2020051647 A1 US2020051647 A1 US 2020051647A1
- Authority
- US
- United States
- Prior art keywords
- memory
- region
- read
- count
- group
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11C—STATIC STORES
- G11C16/00—Erasable programmable read-only memories
- G11C16/02—Erasable programmable read-only memories electrically programmable
- G11C16/06—Auxiliary circuits, e.g. for writing into memory
- G11C16/34—Determination of programming status, e.g. threshold voltage, overprogramming or underprogramming, retention
- G11C16/3418—Disturbance prevention or evaluation; Refreshing of disturbed memory data
- G11C16/3422—Circuits or methods to evaluate read or write disturbance in nonvolatile memory, without steps to mitigate the problem
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
- G06F12/02—Addressing or allocation; Relocation
- G06F12/0223—User address space allocation, e.g. contiguous or non contiguous base addressing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/08—Error detection or correction by redundancy in data representation, e.g. by using checking codes
- G06F11/10—Adding special bits or symbols to the coded information, e.g. parity check, casting out 9's or 11's
- G06F11/1008—Adding special bits or symbols to the coded information, e.g. parity check, casting out 9's or 11's in individual solid state devices
- G06F11/1072—Adding special bits or symbols to the coded information, e.g. parity check, casting out 9's or 11's in individual solid state devices in multilevel memories
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
- G06F12/02—Addressing or allocation; Relocation
- G06F12/0223—User address space allocation, e.g. contiguous or non contiguous base addressing
- G06F12/023—Free address space management
- G06F12/0238—Memory management in non-volatile memory, e.g. resistive RAM or ferroelectric memory
- G06F12/0246—Memory management in non-volatile memory, e.g. resistive RAM or ferroelectric memory in block erasable memory, e.g. flash memory
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11C—STATIC STORES
- G11C16/00—Erasable programmable read-only memories
- G11C16/02—Erasable programmable read-only memories electrically programmable
- G11C16/06—Auxiliary circuits, e.g. for writing into memory
- G11C16/10—Programming or data input circuits
- G11C16/102—External programming circuits, e.g. EPROM programmers; In-circuit programming or reprogramming; EPROM emulators
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11C—STATIC STORES
- G11C16/00—Erasable programmable read-only memories
- G11C16/02—Erasable programmable read-only memories electrically programmable
- G11C16/06—Auxiliary circuits, e.g. for writing into memory
- G11C16/26—Sensing or reading circuits; Data output circuits
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11C—STATIC STORES
- G11C16/00—Erasable programmable read-only memories
- G11C16/02—Erasable programmable read-only memories electrically programmable
- G11C16/06—Auxiliary circuits, e.g. for writing into memory
- G11C16/34—Determination of programming status, e.g. threshold voltage, overprogramming or underprogramming, retention
- G11C16/3418—Disturbance prevention or evaluation; Refreshing of disturbed memory data
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11C—STATIC STORES
- G11C16/00—Erasable programmable read-only memories
- G11C16/02—Erasable programmable read-only memories electrically programmable
- G11C16/06—Auxiliary circuits, e.g. for writing into memory
- G11C16/34—Determination of programming status, e.g. threshold voltage, overprogramming or underprogramming, retention
- G11C16/349—Arrangements for evaluating degradation, retention or wearout, e.g. by counting erase cycles
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11C—STATIC STORES
- G11C29/00—Checking stores for correct operation ; Subsequent repair; Testing stores during standby or offline operation
- G11C29/02—Detection or location of defective auxiliary circuits, e.g. defective refresh counters
- G11C29/028—Detection or location of defective auxiliary circuits, e.g. defective refresh counters with adaption or trimming of parameters
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2212/00—Indexing scheme relating to accessing, addressing or allocation within memory systems or architectures
- G06F2212/10—Providing a specific technical effect
- G06F2212/1032—Reliability improvement, data loss prevention, degraded operation etc
- G06F2212/1036—Life time enhancement
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2212/00—Indexing scheme relating to accessing, addressing or allocation within memory systems or architectures
- G06F2212/72—Details relating to flash memory management
- G06F2212/7211—Wear leveling
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11C—STATIC STORES
- G11C29/00—Checking stores for correct operation ; Subsequent repair; Testing stores during standby or offline operation
- G11C29/04—Detection or location of defective memory elements, e.g. cell constructio details, timing of test signals
- G11C2029/0409—Online test
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11C—STATIC STORES
- G11C29/00—Checking stores for correct operation ; Subsequent repair; Testing stores during standby or offline operation
- G11C29/04—Detection or location of defective memory elements, e.g. cell constructio details, timing of test signals
- G11C29/08—Functional testing, e.g. testing during refresh, power-on self testing [POST] or distributed testing
- G11C29/12—Built-in arrangements for testing, e.g. built-in self testing [BIST] or interconnection details
- G11C29/38—Response verification devices
- G11C29/42—Response verification devices using error correcting codes [ECC] or parity check
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11C—STATIC STORES
- G11C29/00—Checking stores for correct operation ; Subsequent repair; Testing stores during standby or offline operation
- G11C29/04—Detection or location of defective memory elements, e.g. cell constructio details, timing of test signals
- G11C29/50—Marginal testing, e.g. race, voltage or current testing
- G11C29/50004—Marginal testing, e.g. race, voltage or current testing of threshold voltage
Definitions
- Various embodiments generally relate to a memory system, and, more particularly, to a memory system including a nonvolatile memory device.
- a memory system may be configured to store the data provided from a host device, in response to a write request from the host device. Also, the memory system 100 may be configured to provide stored data to the host device, in response to a read request of the host device.
- the host device may be an electronic device capable of processing data and may include a computer, a digital camera or a mobile phone.
- the memory system may operate by being built in the host device, or may operate by being manufactured in a separable form and being coupled to the host device.
- a memory system may include: a storage medium including a memory region group having a plurality of memory regions; a memory configured to store a plurality of region read counts respectively corresponding to the plurality of memory regions and a group read count corresponding to the memory region group; a count management circuit configured to, when a first memory region among the plurality of memory regions is read-accessed, based on a first region read count corresponding to the first memory region among the plurality of region read counts, increase the group read count and reduce remaining region read counts other than the first region read count among the plurality of region read counts; and a reliability management circuit configured to perform a reliability management operation for the memory region group, based on the group read count.
- a method for operating a memory system may include: read-accessing a first memory region among a plurality of memory regions included in a memory region group; based on a first region read count corresponding to the first memory region among a plurality of region read counts respectively corresponding to the plurality of memory regions, increasing a group read count of the memory region group and reducing remaining region read counts other than the first region read count among the plurality of region read counts; and performing a reliability management operation for the memory region group, based on the group read count.
- a memory system may include: a memory device including at least a memory region group having first and second memory regions; and a controller configured to: increase a group read count for the memory region group by a preset amount while decreasing a second region read count for the second memory region by the preset amount when a first region read count for the first memory region reaches a first threshold due to a read-access to the first memory region; and control the memory device to move valid data of the memory region group into another memory region when the group read count reaches a second threshold.
- FIG. 1 is a block diagram illustrating a memory system in accordance with an embodiment.
- FIG. 2 is a block diagram illustrating the storage medium shown in FIG. 1 .
- FIG. 3 is a flow chart of a method for operating the memory system of FIG. 1 in accordance with an embodiment.
- FIG. 4 is a flow chart of a method for operating the count management circuit of FIG. 1 in accordance with an embodiment.
- FIG. 5 is a diagram illustrating a data processing system including a solid state drive (SSD) in accordance with an embodiment.
- SSD solid state drive
- FIG. 6 is a diagram illustrating a data processing system including a memory system in accordance with an embodiment.
- FIG. 7 is a diagram illustrating a data processing system including a memory system in accordance with an embodiment.
- FIG. 8 is a diagram illustrating a network system including a memory system in accordance with an embodiment.
- FIG. 9 is a block diagram illustrating a nonvolatile memory device included in a memory system in accordance with an embodiment.
- phrases “at least one of . . . and . . . ,” when used herein with a list of items, means a single item from the list or any combination of items in the list.
- “at least one of A, B, and C” means, only A, or only B, or only C, or any combination of A, B, and C.
- FIG. 1 is a block diagram illustrating a memory system 100 in accordance with an embodiment.
- the memory system 100 may be configured to store data provided from an external host device, in response to a write request of the host device. Also, the memory system 100 may be configured to provide stored data to the host device, in response to a read request of the host device.
- the memory system 100 may be configured by a Personal Computer Memory Card International Association (PCMCIA) card, a Compact Flash (CF) card, a smart media card, a memory stick, various multimedia cards (MMC, eMMC, RS-MMC, and MMC-Micro), various secure digital cards (SD, Mini-SD, and Micro-SD), a Universal Flash Storage (UFS), a Solid State Drive (SSD) and the like.
- PCMCIA Personal Computer Memory Card International Association
- CF Compact Flash
- MMC-MMC multimedia cards
- MMC-MMC Secure Digital cards
- SD Secure Digital cards
- UFS Universal Flash Storage
- SSD Solid State Drive
- the memory system 100 may include a controller 110 and a storage medium 120 .
- the controller 110 may control general operations of the memory system 100 .
- the controller 110 may access the storage medium 120 to process a request of the host device. Also, the controller 110 may access the storage medium 120 to perform an internal management operation or a background operation of the memory system 100 regardless of a request of the host device.
- An access to the storage medium 120 may include a write access and a read access. That is, the controller 110 may write-access and read-access the storage medium 120 by controlling a write operation and a read operation of the storage medium 120 .
- the controller 110 may include a count management circuit 111 , a reliability management circuit 112 and a memory 113 .
- the count management circuit 111 may manage region read counts CT 1 to CT 4 and a group read count GCT 1 stored in the memory 113 .
- the group read count GCT 1 may correspond to a memory region group MRG 1 included in the storage medium 120
- the region read counts CT 1 to CT 4 may respectively correspond to memory regions MR 1 to MR 4 included in the memory region group MRG 1 .
- the count management circuit 111 may increase the group read count GCT 1 and may reduce the remaining region read counts CT 2 to CT 4 other than the first region read count CT 1 among the read counts CT 1 to CT 4 , based on the first region read count CT 1 corresponding to the read-access to the first memory region MR 1 .
- the count management circuit 111 may increase the group read count GCT 1 and may reduce the remaining region read counts CT 2 to CT 4 .
- the first threshold value TH 1 may be, for example, the maximum value of each of the region read counts CT 1 to CT 4 depending on a memory capacity allocated to each of the region read counts CT 1 to CT 4 .
- the first threshold value TH 1 may be 7.
- the count management circuit 111 may increase the group read count GCT 1 by an adjustment value and may reduce the remaining region read counts CT 2 to CT 4 by the adjustment value.
- the increase value of the group read count GCT 1 and the reduction value of the remaining region read counts CT 2 to CT 4 may be the same as each other.
- the adjustment value may be 1.
- the adjustment value may be a minimum value other than 0 among the region read counts CT 1 to CT 4 .
- the count management circuit 111 may once reduce all the region read counts CT 1 to CT 4 by the adjustment value and then increase only the first region read count CT 1 by the adjustment value.
- the count management circuit 111 may increase only the first region read count CT 1 .
- the count management circuit 111 may initialize the region read counts CT 1 to CT 4 and the group read count GCT 1 after the reliability management circuit 112 performs a reliability management operation as will be described later.
- the reliability management circuit 112 may perform the reliability management operation for the memory region group MRG 1 , based on the group read count GCT 1 .
- the reliability management circuit 112 may perform the reliability management operation for the memory region group MRG 1 , in the case where the group read count GCT 1 has reached a second threshold value TH 2 .
- the reliability management circuit 112 may move the valid data stored in the memory regions MR 1 to MR 4 to one or more other memory regions (not shown).
- the second threshold value TH 2 may be, for example, the maximum value of the group read count GCT 1 depending on a memory capacity allocated to the group read count GCT 1 .
- the reliability management circuit 112 may recover the reliability of the data by moving the data to another memory region based on a group read count GCT before the data is completely damaged.
- the memory 113 may store the region read counts CT 1 to CT 4 respectively corresponding to the memory regions MR 1 to MR 4 and the group read count GCT 1 corresponding to the memory region group MRG 1 .
- a memory capacity allocated to each of the region read counts CT 1 to CT 4 may be smaller than a memory capacity allocated to the group read count GCT 1 .
- the first threshold value TH 1 and the second threshold value TH 2 may be stored in the memory 113 .
- the memory 113 may include a volatile memory device such as a Static Random Access Memory (SRAM), a Dynamic Random Access Memory (DRAM), and the like. According to an embodiment, the memory 113 may include a memory element such as a register, a flip-flop, a latch and the like.
- SRAM Static Random Access Memory
- DRAM Dynamic Random Access Memory
- the memory 113 may include a memory element such as a register, a flip-flop, a latch and the like.
- the storage medium 120 may store data transmitted from the controller 110 and may read stored data and transmit read data to the controller 110 , under the control of the controller 110 .
- the storage medium 120 may include the memory region group MRG 1 including the memory regions MR 1 to MR 4 .
- FIG. 2 is a block diagram illustrating the storage medium 120 shown in FIG. 1 .
- the storage medium 120 may include nonvolatile memory devices NVM.
- the controller 110 may access in parallel the nonvolatile memory devices NVM.
- Each nonvolatile memory device NVM may include a flash memory, such as a NAND flash or a NOR flash, a Ferroelectrics Random Access Memory (FeRAM), a Phase-Change Random Access Memory (PCRAM), a Magnetoresistive Random Access Memory (MRAM), a Resistive Random Access Memory (ReRAM), and the like.
- a flash memory such as a NAND flash or a NOR flash
- FeRAM Ferroelectrics Random Access Memory
- PCRAM Phase-Change Random Access Memory
- MRAM Magnetoresistive Random Access Memory
- ReRAM Resistive Random Access Memory
- Each nonvolatile memory device NVM may include memory regions MR.
- each memory region MR may be a unit by which each nonvolatile memory device NVM performs an erase operation.
- the data stored in each memory region MR may be erased at once by the erase operation of each nonvolatile memory device NVM.
- each memory region MR may include at least two erase memory units each serving as a unit by which each nonvolatile memory device NVM performs an erase operation.
- Each memory region MR may include a plurality of memory units MU.
- each memory unit MU may be a unit by which each nonvolatile memory device NVM performs a read operation.
- the data stored in each memory unit MU may be read at once by the read operation of each nonvolatile memory device NVM.
- Memory regions MR may be grouped into memory region groups MRG.
- the memory regions MR included in each memory region group MRG may be included in the nonvolatile memory devices NVM, respectively.
- the memory 113 may store region read counts respectively corresponding to the memory regions MR of FIG. 2 and group read counts respectively corresponding to the memory region groups MRG of FIG. 2 , and the count management circuit 111 may manage the region read counts and group read counts stored in the memory 113 in the same manner as described above for the region read counts CT 1 to CT 4 and the group read count GCT 1 with reference to FIG. 1 .
- read-accessing a certain memory region MR may be read-accessing a target memory unit MU included in the corresponding memory region MR.
- the count management circuit 111 may increase the region read count CT of the corresponding memory region MR.
- each memory region group MRG includes four memory regions MR, it is to be noted that the embodiment of the present disclosure is not limited thereto.
- FIG. 3 is a flow chart of a method for operating the memory system 100 of FIG. 1 in accordance with an embodiment.
- the controller 110 may read-access the first memory region MR 1 among the memory regions MR 1 to MR 4 included in the memory region group MRG 1 .
- the count management circuit 111 may determine whether the first region read count CT 1 , which corresponds to the first memory region MR 1 among the region read counts CT 1 to CT 4 corresponding to the memory regions MR 1 to MR 4 , has reached the first threshold value TH 1 . In the case where the first region read count CT 1 has reached the first threshold value TH 1 , the process may proceed to step S 130 . In the case where the first region read count CT 1 has not reached the first threshold value TH 1 , the process may proceed to step S 170 .
- the count management circuit 111 may increase the group read count GCT 1 corresponding to the memory region group MRG 1 and reduce the remaining region read counts CT 2 to CT 4 other than the first region read count CT 1 .
- the count management circuit 111 may increase the group read count GCT 1 by an adjustment value, and may reduce the remaining region read counts CT 2 to CT 4 by the adjustment value.
- the reliability management circuit 112 may determine whether the group read count GCT 1 has reached the second threshold value TH 2 . In the case where the group read count GCT 1 has reached the second threshold value TH 2 , the process may proceed to step S 150 . In the case where the group read count GCT 1 has not reached the second threshold value TH 2 , the process may be ended.
- the reliability management circuit 112 may perform a reliability management operation for the memory region group MRG 1 .
- the reliability management circuit 112 may move the valid data stored in the memory regions MR 1 to MR 4 to one or more other memory regions MR 1 to MR 4 .
- the count management circuit 111 may initialize the region read counts CT 1 to CT 4 and the group read count GCT 1 . Then, the process may be ended.
- the count management circuit 111 may increase the first region read count CT 1 at the step S 170 . Then, the process may be ended.
- FIG. 4 is a flow chart of a method for operating the count management circuit 111 of FIG. 1 in accordance with an embodiment.
- the process of FIG. 4 may be a detailed example of the step S 130 of FIG. 3 .
- the count management circuit 111 may increase the group read count GCT 1 .
- the count management circuit 111 may reduce all the region read counts CT 1 to CT 4 .
- the count management circuit 111 may increase only the first region read count CT 1 .
- the count management circuit 111 may increase the group read count GCT 1 by the adjustment value, may reduce all the region read counts CT 1 to CT 4 by the adjustment value, and may increase only the first region read count CT 1 by the adjustment value.
- the controller 110 may efficiently perform a reliability management operation while managing the region read counts CT 1 to CT 4 with a small memory capacity.
- the region read counts CT 1 to CT 4 are not managed and only the group read count GCT 1 is managed, read accesses to the memory regions MR 1 to MR 4 may not be properly reflected, and a reliability management operation may be performed even in a situation where it is not necessary. For example, in the case where sequential read operations for the memory regions MR 1 to MR 4 are performed, as each of the memory regions MR 1 to MR 4 is read-accessed only once, the group read count GCT 1 may be increased by 4 . Thus, a reliability management operation based on the group read count GCT 1 may be performed too frequently.
- the group read count GCT 1 is not managed and only the region read counts CT 1 to CT 4 of the memory regions MR 1 to MR 4 are managed, a time at which data is damaged may be precisely grasped and a necessary reliability management operation may be performed. However, in this case, it may be necessary to allocate a substantially large memory capacity to the region read counts CT 1 to CT 4 , to ensure that the region read counts CT 1 to CT 4 may be increased to an appropriate maximum value.
- a relatively small memory capacity may be allocated to the region read counts CT 1 to CT 4 of the memory regions MR 1 to MR 4 . That is, the maximum value of each of the region read counts CT 1 to CT 4 may be relatively small. Nevertheless, since the region read counts CT 1 to CT 4 are reduced each time the group read count GCT 1 is increased, no problem may be caused by the fact that the maximum value is small.
- the group read count GCT 1 may be increased in response to a read access to the first memory region MR 1 after all the region read counts CT 1 to CT 4 reach the first threshold value TH 1 . At this time, the region read counts CT 2 to CT 4 of the remaining memory regions MR 2 to MR 4 may be reduced.
- the group read count GCT 1 may be increased in response to a read access to the first memory region MR 1 after read accesses to the remaining memory regions MR 2 to MR 4 are respectively performed. Namely, since the group read count GCT 1 is not increased each time each of the memory regions MR 1 to MR 4 is read-accessed, a reliability management operation based on the group read count GCT 1 may be suppressed from being performed too frequently.
- FIG. 5 is a diagram illustrating a data processing system 1000 including a solid state drive (SSD) 1200 in accordance with an embodiment.
- the data processing system 1000 may include a host device 1100 and the SSD 1200 .
- the SSD 1200 may include a controller 1210 , a buffer memory device 1220 , a plurality of nonvolatile memory devices 1231 to 123 n , a power supply 1240 , a signal connector 1250 , and a power connector 1260 .
- the controller 1210 may control general operations of the SSD 1200 .
- the controller 1210 may include a host interface unit 1211 , a control unit 1212 , a random access memory 1213 , an error correction code (ECC) unit 1214 , and a memory interface unit 1215 .
- ECC error correction code
- the host interface unit 1211 may exchange a signal SGL with the host device 1100 through the signal connector 1250 .
- the signal SGL may include a command, an address, data, and so forth.
- the host interface unit 1211 may interface the host device 1100 and the SSD 1200 according to the protocol of the host device 1100 .
- the host interface unit 1211 may communicate with the host device 1100 through any one of standard interface protocols such as secure digital, universal serial bus (USB), multimedia card (MMC), embedded MMC (eMMC), personal computer memory card international association (PCMCIA), parallel advanced technology attachment (DATA), serial advanced technology attachment (SATA), small computer system interface (SCSI), serial attached SCSI (SAS), peripheral component interconnection (PCI), PCI express (PCI-E) and universal flash storage (UFS).
- standard interface protocols such as secure digital, universal serial bus (USB), multimedia card (MMC), embedded MMC (eMMC), personal computer memory card international association (PCMCIA), parallel advanced technology attachment (DATA), serial advanced technology attachment (SATA), small computer system interface (SCSI), serial attached SCSI (SAS), peripheral component interconnection (PCI), PCI express (PCI-E) and universal flash storage (UFS).
- the control unit 1212 may analyze and process the signal SGL received from the host device 1100 .
- the control unit 1212 may control operations of internal function blocks according to a firmware or a software for driving the SSD 1200 .
- the random access memory 1213 may be used as a working memory for driving such a firmware or software.
- the control unit 1212 may include the count management circuit 111 and the reliability management circuit 112 shown in FIG. 1 .
- the control unit 1212 may operate in the same manner as the count management circuit 111 and the reliability management circuit 112 .
- the ECC unit 1214 may generate the parity data of the count management circuit 111 and the reliability management circuit 112 data to be transmitted to at least one of the nonvolatile memory devices 1231 to 123 n .
- the generated parity data may be stored together with the data in the nonvolatile memory devices 1231 to 123 n .
- the ECC unit 1214 may detect an error of the data read from at least one of the nonvolatile memory devices 1231 to 123 n , based on the parity data. If a detected error is within a correctable range, the ECC unit 1214 may correct the detected error.
- the memory interface unit 1215 may provide control signals such as commands and addresses to at least one of the nonvolatile memory devices 1231 to 123 n , according to control of the control unit 1212 . Moreover, the memory interface unit 1215 may exchange data with at least one of the nonvolatile memory devices 1231 to 123 n , according to control of the control unit 1212 . For example, the memory interface unit 1215 may provide the data stored in the buffer memory device 1220 , to at least one of the nonvolatile memory devices 1231 to 123 n , or provide the data read from at least one of the nonvolatile memory devices 1231 to 123 n , to the buffer memory device 1220 .
- the buffer memory device 1220 may temporarily store data to be stored in at least one of the nonvolatile memory devices 1231 to 123 n . Further, the buffer memory device 1220 may temporarily store the data read from at least one of the nonvolatile memory devices 1231 to 123 n . The data temporarily stored in the buffer memory device 1220 may be transmitted to the host device 1100 or at least one of the nonvolatile memory devices 1231 to 123 n according to control of the controller 1210 .
- the nonvolatile memory devices 1231 to 123 n may be used as storage media of the SSD 1200 .
- the nonvolatile memory devices 1231 to 123 n may be coupled with the controller 1210 through a plurality of channels CH 1 to CHn, respectively.
- One or more nonvolatile memory devices may be coupled to one channel.
- the nonvolatile memory devices coupled to each channel may be coupled to the same signal bus and data bus.
- the power supply 1240 may provide power PWR inputted through the power connector 1260 , to the inside of the SSD 1200 .
- the power supply 1240 may include an auxiliary power supply 1241 .
- the auxiliary power supply 1241 may supply power to allow the SSD 1200 to be normally terminated when a sudden power-off occurs.
- the auxiliary power supply 1241 may include large capacity capacitors.
- the signal connector 1250 may be configured by various types of connectors depending on an interface scheme between the host device 1100 and the SSD 1200 .
- the power connector 1260 may be configured by various types of connectors depending on a power supply scheme of the host device 1100 .
- FIG. 6 is a diagram illustrating a data processing system 2000 including a memory system 2200 in accordance with an embodiment.
- the data processing system 2000 may include a host device 2100 and the memory system 2200 .
- the host device 2100 may be configured in the form of a board such as a printed circuit board. Although not shown, the host device 2100 may include internal function blocks for performing the function of a host device.
- the host device 2100 may include a connection terminal 2110 such as a socket, a slot or a connector.
- the memory system 2200 may be mounted to the connection terminal 2110 .
- the memory system 2200 may be configured in the form of a board such as a printed circuit board.
- the memory system 2200 may be referred to as a memory module or a memory card.
- the memory system 2200 may include a controller 2210 , a buffer memory device 2220 , nonvolatile memory devices 2231 and 2232 , a power management integrated circuit (PMIC) 2240 , and a connection terminal 2250 .
- PMIC power management integrated circuit
- the controller 2210 may control general operations of the memory system 2200 .
- the controller 2210 may be configured in the same manner as the controller 1210 shown in FIG. 5 .
- the buffer memory device 2220 may temporarily store data to be stored in the nonvolatile memory devices 2231 and 2232 . Further, the buffer memory device 2220 may temporarily store the data read from the nonvolatile memory devices 2231 and 2232 . The data temporarily stored in the buffer memory device 2220 may be transmitted to the host device 2100 or the nonvolatile memory devices 2231 and 2232 according to control of the controller 2210 .
- the nonvolatile memory devices 2231 and 2232 may be used as storage media of the memory system 2200 .
- the PMIC 2240 may provide the power inputted through the connection terminal 2250 , to the inside of the memory system 2200 .
- the PMIC 2240 may manage the power of the memory system 2200 according to control of the controller 2210 .
- the connection terminal 2250 may be coupled to the connection terminal 2110 of the host device 2100 . Through the connection terminal 2250 , signals such as commands, addresses, data and so forth and power may be transferred between the host device 2100 and the memory system 2200 .
- the connection terminal 2250 may be configured into various types depending on an interface scheme between the host device 2100 and the memory system 2200 .
- the connection terminal 2250 may be disposed on any one side of the memory system 2200 .
- FIG. 7 is a diagram illustrating a data processing system 3000 including a memory system 3200 in accordance with an embodiment.
- the data processing system 3000 may include a host device 3100 and the memory system 3200 .
- the host device 3100 may be configured in the form of a board such as a printed circuit board. Although not shown, the host device 3100 may include internal function blocks for performing the function of a host device.
- the memory system 3200 may be configured in the form of a surface-mounting type package.
- the memory system 3200 may be mounted to the host device 3100 through solder balls 3250 .
- the memory system 3200 may include a controller 3210 , a buffer memory device 3220 , and a nonvolatile memory device 3230 .
- the controller 3210 may control general operations of the memory system 3200 .
- the controller 3210 may be configured in the same manner as the controller 1210 shown in FIG. 5 .
- the buffer memory device 3220 may temporarily store data to be stored in the nonvolatile memory device 3230 . Further, the buffer memory device 3220 may temporarily store the data read from the nonvolatile memory device 3230 . The data temporarily stored in the buffer memory device 3220 may be transmitted to the host device 3100 or the nonvolatile memory device 3230 according to control of the controller 3210 .
- the nonvolatile memory device 3230 may be used as the storage medium of the memory system 3200 .
- FIG. 8 is a diagram illustrating a network system 4000 including a memory system 4200 in accordance with an embodiment.
- the network system 4000 may include a server system 4300 and a plurality of client systems 4410 to 4430 which are coupled through a network 4500 .
- the server system 4300 may service data in response to requests from the plurality of client systems 4410 to 4430 .
- the server system 4300 may store the data provided from the plurality of client systems 4410 to 4430 .
- the server system 4300 may provide data to the plurality of client systems 4410 to 4430 .
- the server system 4300 may include a host device 4100 and the memory system 4200 .
- the memory system 4200 may be configured by the memory system 100 shown in FIG. 1 , the memory system 1200 shown in FIG. 5 , the memory system 2200 shown in FIG. 6 or the memory system 3200 shown in FIG. 7 .
- FIG. 9 is a block diagram illustrating a nonvolatile memory device 300 included in a memory system in accordance with an embodiment.
- the nonvolatile memory device 300 may include a memory cell array 310 , a row decoder 320 , a data read/write block 330 , a column decoder 340 , a voltage generator 350 , and a control logic 360 .
- the memory cell array 310 may include memory cells MC which are arranged at areas where word lines WL 1 to WLm and bit lines BL 1 to BLn intersect with each other.
- the row decoder 320 may be coupled with the memory cell array 310 through the word lines WL 1 to WLm.
- the row decoder 320 may operate according to control of the control logic 360 .
- the row decoder 320 may decode an address provided from an external device (not shown).
- the row decoder 320 may select and drive the word lines WL 1 to WLm, based on a decoding result. For instance, the row decoder 320 may provide a word line voltage provided from the voltage generator 350 , to the word lines WL 1 to WLm.
- the data read/write block 330 may be coupled with the memory cell array 310 through the bit lines BL 1 to BLn.
- the data read/write block 330 may include read/write circuits RW 1 to RWn respectively corresponding to the bit lines BL 1 to BLn.
- the data read/write block 330 may operate according to control of the control logic 360 .
- the data read/write block 330 may operate as a write driver or a sense amplifier according to an operation mode.
- the data read/write block 330 may operate as a write driver which stores data provided from the external device, in the memory cell array 310 in a write operation.
- the data read/write block 330 may operate as a sense amplifier which reads out data from the memory cell array 310 in a read operation.
- the column decoder 340 may operate according to control of the control logic 360 .
- the column decoder 340 may decode an address provided from the external device.
- the column decoder 340 may couple the read/write circuits RW 1 to RWn of the data read/write block 330 respectively corresponding to the bit lines BL 1 to BLn with data input/output lines or data input/output buffers, based on a decoding result.
- the voltage generator 350 may generate voltages to be used in internal operations of the nonvolatile memory device 300 .
- the voltages generated by the voltage generator 350 may be applied to the memory cells of the memory cell array 310 .
- a program voltage generated in a program operation may be applied to a word line of memory cells for which the program operation is to be performed.
- an erase voltage generated in an erase operation may be applied to a well area of memory cells for which the erase operation is to be performed.
- a read voltage generated in a read operation may be applied to a word line of memory cells for which the read operation is to be performed.
- the control logic 360 may control general operations of the nonvolatile memory device 300 , based on control signals provided from the external device. For example, the control logic 360 may control operations of the nonvolatile memory device 300 such as read, write and erase operations of the nonvolatile memory device 300 .
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Techniques For Improving Reliability Of Storages (AREA)
Abstract
Description
- The present application claims priority under 35 U.S.C. § 119(a) to Korean application number 10-2018-0092542, filed on Aug. 8, 2018, which is incorporated herein by reference in its entirety.
- Various embodiments generally relate to a memory system, and, more particularly, to a memory system including a nonvolatile memory device.
- A memory system may be configured to store the data provided from a host device, in response to a write request from the host device. Also, the
memory system 100 may be configured to provide stored data to the host device, in response to a read request of the host device. The host device may be an electronic device capable of processing data and may include a computer, a digital camera or a mobile phone. The memory system may operate by being built in the host device, or may operate by being manufactured in a separable form and being coupled to the host device. - In an embodiment, a memory system may include: a storage medium including a memory region group having a plurality of memory regions; a memory configured to store a plurality of region read counts respectively corresponding to the plurality of memory regions and a group read count corresponding to the memory region group; a count management circuit configured to, when a first memory region among the plurality of memory regions is read-accessed, based on a first region read count corresponding to the first memory region among the plurality of region read counts, increase the group read count and reduce remaining region read counts other than the first region read count among the plurality of region read counts; and a reliability management circuit configured to perform a reliability management operation for the memory region group, based on the group read count.
- In an embodiment, a method for operating a memory system may include: read-accessing a first memory region among a plurality of memory regions included in a memory region group; based on a first region read count corresponding to the first memory region among a plurality of region read counts respectively corresponding to the plurality of memory regions, increasing a group read count of the memory region group and reducing remaining region read counts other than the first region read count among the plurality of region read counts; and performing a reliability management operation for the memory region group, based on the group read count.
- In an embodiment, a memory system may include: a memory device including at least a memory region group having first and second memory regions; and a controller configured to: increase a group read count for the memory region group by a preset amount while decreasing a second region read count for the second memory region by the preset amount when a first region read count for the first memory region reaches a first threshold due to a read-access to the first memory region; and control the memory device to move valid data of the memory region group into another memory region when the group read count reaches a second threshold.
-
FIG. 1 is a block diagram illustrating a memory system in accordance with an embodiment. -
FIG. 2 is a block diagram illustrating the storage medium shown inFIG. 1 . -
FIG. 3 is a flow chart of a method for operating the memory system ofFIG. 1 in accordance with an embodiment. -
FIG. 4 is a flow chart of a method for operating the count management circuit ofFIG. 1 in accordance with an embodiment. -
FIG. 5 is a diagram illustrating a data processing system including a solid state drive (SSD) in accordance with an embodiment. -
FIG. 6 is a diagram illustrating a data processing system including a memory system in accordance with an embodiment. -
FIG. 7 is a diagram illustrating a data processing system including a memory system in accordance with an embodiment. -
FIG. 8 is a diagram illustrating a network system including a memory system in accordance with an embodiment. -
FIG. 9 is a block diagram illustrating a nonvolatile memory device included in a memory system in accordance with an embodiment. - Hereinafter, a memory system and an operating method thereof according to the present invention will be described with reference to the accompanying drawings through exemplary embodiments of the present invention. The present invention may, however, be embodied in different forms and should not be construed as being limited to the embodiments set forth herein. Rather, these embodiments are provided to describe the present invention in detail to the extent that a person skilled in the art to which the invention pertains can enforce the technical concepts of the present invention.
- It is to be understood that embodiments of the present invention are not limited to the particulars shown in the drawings, that the drawings are not necessarily to scale, and, in some instances, proportions may have been exaggerated in order to more clearly depict certain features of the invention. While particular terminology is used, it is to be appreciated that the terminology used is for describing particular embodiments only and is not intended to limit the scope of the present invention.
- It will be further understood that when an element is referred to as being “connected to”, or “coupled to” another element, it may be directly on, connected to, or coupled to the other element, or one or more intervening elements may be present. In addition, it will also be understood that when an element is referred to as being “between” two elements, it may be the only element between the two elements, or one or more intervening elements may also be present.
- The phrase “at least one of . . . and . . . ,” when used herein with a list of items, means a single item from the list or any combination of items in the list. For example, “at least one of A, B, and C” means, only A, or only B, or only C, or any combination of A, B, and C.
- The term “or” as used herein means either one of two or more alternatives but not both nor any combinations thereof.
- As used herein, singular forms are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes,” and “including” when used in this specification, specify the presence of the stated elements and do not preclude the presence or addition of one or more other elements. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items.
- Unless otherwise defined, all terms including technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the present invention belongs in view of the present disclosure. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the present disclosure and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
- In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. The present invention may be practiced without some or all of these specific details. In other instances, well-known process structures and/or processes have not been described in detail in order not to unnecessarily obscure the present invention.
- It is also noted, that in some instances, as would be apparent to those skilled in the relevant art, an element also referred to as a feature described in connection with one embodiment may be used singly or in combination with other elements of another embodiment, unless specifically indicated otherwise.
- Hereinafter, the various embodiments of the present invention will be described in detail with reference to the attached drawings.
-
FIG. 1 is a block diagram illustrating amemory system 100 in accordance with an embodiment. - The
memory system 100 may be configured to store data provided from an external host device, in response to a write request of the host device. Also, thememory system 100 may be configured to provide stored data to the host device, in response to a read request of the host device. - The
memory system 100 may be configured by a Personal Computer Memory Card International Association (PCMCIA) card, a Compact Flash (CF) card, a smart media card, a memory stick, various multimedia cards (MMC, eMMC, RS-MMC, and MMC-Micro), various secure digital cards (SD, Mini-SD, and Micro-SD), a Universal Flash Storage (UFS), a Solid State Drive (SSD) and the like. - The
memory system 100 may include acontroller 110 and astorage medium 120. - The
controller 110 may control general operations of thememory system 100. Thecontroller 110 may access thestorage medium 120 to process a request of the host device. Also, thecontroller 110 may access thestorage medium 120 to perform an internal management operation or a background operation of thememory system 100 regardless of a request of the host device. An access to thestorage medium 120 may include a write access and a read access. That is, thecontroller 110 may write-access and read-access thestorage medium 120 by controlling a write operation and a read operation of thestorage medium 120. - The
controller 110 may include acount management circuit 111, areliability management circuit 112 and amemory 113. - The
count management circuit 111 may manage region read counts CT1 to CT4 and a group read count GCT1 stored in thememory 113. The group read count GCT1 may correspond to a memory region group MRG1 included in thestorage medium 120, and the region read counts CT1 to CT4 may respectively correspond to memory regions MR1 to MR4 included in the memory region group MRG1. - For example, when a first memory region MR1 among the memory regions MR1 to MR4 is read-accessed, the
count management circuit 111 may increase the group read count GCT1 and may reduce the remaining region read counts CT2 to CT4 other than the first region read count CT1 among the read counts CT1 to CT4, based on the first region read count CT1 corresponding to the read-access to the first memory region MR1. - In detail, when the first memory region MR1 is read-accessed and the first region read count CT1 has reached a first threshold value TH1, the
count management circuit 111 may increase the group read count GCT1 and may reduce the remaining region read counts CT2 to CT4. - The first threshold value TH1 may be, for example, the maximum value of each of the region read counts CT1 to CT4 depending on a memory capacity allocated to each of the region read counts CT1 to CT4. For example, in the case where three bits are allocated to each of the region read counts CT1 to CT4, the first threshold value TH1 may be 7.
- The
count management circuit 111 may increase the group read count GCT1 by an adjustment value and may reduce the remaining region read counts CT2 to CT4 by the adjustment value. In other words, the increase value of the group read count GCT1 and the reduction value of the remaining region read counts CT2 to CT4 may be the same as each other. For example, the adjustment value may be 1. For another example, the adjustment value may be a minimum value other than 0 among the region read counts CT1 to CT4. - According to the embodiment, in order to reduce the remaining region read counts CT2 to CT4, the
count management circuit 111 may once reduce all the region read counts CT1 to CT4 by the adjustment value and then increase only the first region read count CT1 by the adjustment value. - When the first memory region MR1 is read-accessed but the first region read count CT1 has not reached the first threshold value TH1, the
count management circuit 111 may increase only the first region read count CT1. - The
count management circuit 111 may initialize the region read counts CT1 to CT4 and the group read count GCT1 after thereliability management circuit 112 performs a reliability management operation as will be described later. - The
reliability management circuit 112 may perform the reliability management operation for the memory region group MRG1, based on the group read count GCT1. - In detail, the
reliability management circuit 112 may perform the reliability management operation for the memory region group MRG1, in the case where the group read count GCT1 has reached a second threshold value TH2. When performing the reliability management operation, thereliability management circuit 112 may move the valid data stored in the memory regions MR1 to MR4 to one or more other memory regions (not shown). - The second threshold value TH2 may be, for example, the maximum value of the group read count GCT1 depending on a memory capacity allocated to the group read count GCT1.
- Since the data stored in a memory region may be damaged little by little by read accesses to the memory region, the
reliability management circuit 112 may recover the reliability of the data by moving the data to another memory region based on a group read count GCT before the data is completely damaged. - The
memory 113 may store the region read counts CT1 to CT4 respectively corresponding to the memory regions MR1 to MR4 and the group read count GCT1 corresponding to the memory region group MRG1. A memory capacity allocated to each of the region read counts CT1 to CT4 may be smaller than a memory capacity allocated to the group read count GCT1. - According to an embodiment, the first threshold value TH1 and the second threshold value TH2 may be stored in the
memory 113. - The
memory 113 may include a volatile memory device such as a Static Random Access Memory (SRAM), a Dynamic Random Access Memory (DRAM), and the like. According to an embodiment, thememory 113 may include a memory element such as a register, a flip-flop, a latch and the like. - The
storage medium 120 may store data transmitted from thecontroller 110 and may read stored data and transmit read data to thecontroller 110, under the control of thecontroller 110. Thestorage medium 120 may include the memory region group MRG1 including the memory regions MR1 to MR4. -
FIG. 2 is a block diagram illustrating thestorage medium 120 shown inFIG. 1 . - Referring to
FIG. 2 , thestorage medium 120 may include nonvolatile memory devices NVM. Thecontroller 110 may access in parallel the nonvolatile memory devices NVM. - Each nonvolatile memory device NVM may include a flash memory, such as a NAND flash or a NOR flash, a Ferroelectrics Random Access Memory (FeRAM), a Phase-Change Random Access Memory (PCRAM), a Magnetoresistive Random Access Memory (MRAM), a Resistive Random Access Memory (ReRAM), and the like.
- Each nonvolatile memory device NVM may include memory regions MR. For example, each memory region MR may be a unit by which each nonvolatile memory device NVM performs an erase operation. In other words, the data stored in each memory region MR may be erased at once by the erase operation of each nonvolatile memory device NVM. For another example, each memory region MR may include at least two erase memory units each serving as a unit by which each nonvolatile memory device NVM performs an erase operation.
- Each memory region MR may include a plurality of memory units MU. For example, each memory unit MU may be a unit by which each nonvolatile memory device NVM performs a read operation. In other words, the data stored in each memory unit MU may be read at once by the read operation of each nonvolatile memory device NVM.
- Memory regions MR may be grouped into memory region groups MRG. The memory regions MR included in each memory region group MRG may be included in the nonvolatile memory devices NVM, respectively.
- While not shown in
FIG. 1 , thememory 113 may store region read counts respectively corresponding to the memory regions MR ofFIG. 2 and group read counts respectively corresponding to the memory region groups MRG ofFIG. 2 , and thecount management circuit 111 may manage the region read counts and group read counts stored in thememory 113 in the same manner as described above for the region read counts CT1 to CT4 and the group read count GCT1 with reference toFIG. 1 . - In summary, read-accessing a certain memory region MR may be read-accessing a target memory unit MU included in the corresponding memory region MR. When the target memory unit MU is read-accessed, in the case where the region read count CT of the memory region MR including the target memory unit MU has not reached the first threshold value TH1, the
count management circuit 111 may increase the region read count CT of the corresponding memory region MR. - While it is illustrated in
FIG. 2 that four nonvolatile memory devices NVM and four memory region groups MRG are provided and each memory region group MRG includes four memory regions MR, it is to be noted that the embodiment of the present disclosure is not limited thereto. -
FIG. 3 is a flow chart of a method for operating thememory system 100 ofFIG. 1 in accordance with an embodiment. - Referring to
FIG. 3 , at step S110, thecontroller 110 may read-access the first memory region MR1 among the memory regions MR1 to MR4 included in the memory region group MRG1. - At step S120, the
count management circuit 111 may determine whether the first region read count CT1, which corresponds to the first memory region MR1 among the region read counts CT1 to CT4 corresponding to the memory regions MR1 to MR4, has reached the first threshold value TH1. In the case where the first region read count CT1 has reached the first threshold value TH1, the process may proceed to step S130. In the case where the first region read count CT1 has not reached the first threshold value TH1, the process may proceed to step S170. - At the step S130, the
count management circuit 111 may increase the group read count GCT1 corresponding to the memory region group MRG1 and reduce the remaining region read counts CT2 to CT4 other than the first region read count CT1. Thecount management circuit 111 may increase the group read count GCT1 by an adjustment value, and may reduce the remaining region read counts CT2 to CT4 by the adjustment value. - At step S140, the
reliability management circuit 112 may determine whether the group read count GCT1 has reached the second threshold value TH2. In the case where the group read count GCT1 has reached the second threshold value TH2, the process may proceed to step S150. In the case where the group read count GCT1 has not reached the second threshold value TH2, the process may be ended. - At the step S150, the
reliability management circuit 112 may perform a reliability management operation for the memory region group MRG1. When performing the reliability management operation, thereliability management circuit 112 may move the valid data stored in the memory regions MR1 to MR4 to one or more other memory regions MR1 to MR4. - At step S160, the
count management circuit 111 may initialize the region read counts CT1 to CT4 and the group read count GCT1. Then, the process may be ended. - When it is determined at the step S120 that the first region read count CT1 has not reached the first threshold value TH1, the
count management circuit 111 may increase the first region read count CT1 at the step S170. Then, the process may be ended. -
FIG. 4 is a flow chart of a method for operating thecount management circuit 111 ofFIG. 1 in accordance with an embodiment. The process ofFIG. 4 may be a detailed example of the step S130 ofFIG. 3 . - Referring to
FIG. 4 , at step S210, thecount management circuit 111 may increase the group read count GCT1. - At step S220, the
count management circuit 111 may reduce all the region read counts CT1 to CT4. - At step S230, the
count management circuit 111 may increase only the first region read count CT1. - The
count management circuit 111 may increase the group read count GCT1 by the adjustment value, may reduce all the region read counts CT1 to CT4 by the adjustment value, and may increase only the first region read count CT1 by the adjustment value. - In summary, according to the embodiment, the
controller 110 may efficiently perform a reliability management operation while managing the region read counts CT1 to CT4 with a small memory capacity. - For example, if the region read counts CT1 to CT4 are not managed and only the group read count GCT1 is managed, read accesses to the memory regions MR1 to MR4 may not be properly reflected, and a reliability management operation may be performed even in a situation where it is not necessary. For example, in the case where sequential read operations for the memory regions MR1 to MR4 are performed, as each of the memory regions MR1 to MR4 is read-accessed only once, the group read count GCT1 may be increased by 4. Thus, a reliability management operation based on the group read count GCT1 may be performed too frequently.
- Conversely, if the group read count GCT1 is not managed and only the region read counts CT1 to CT4 of the memory regions MR1 to MR4 are managed, a time at which data is damaged may be precisely grasped and a necessary reliability management operation may be performed. However, in this case, it may be necessary to allocate a substantially large memory capacity to the region read counts CT1 to CT4, to ensure that the region read counts CT1 to CT4 may be increased to an appropriate maximum value.
- According to the embodiment of the present disclosure, a relatively small memory capacity may be allocated to the region read counts CT1 to CT4 of the memory regions MR1 to MR4. That is, the maximum value of each of the region read counts CT1 to CT4 may be relatively small. Nevertheless, since the region read counts CT1 to CT4 are reduced each time the group read count GCT1 is increased, no problem may be caused by the fact that the maximum value is small.
- As the region read counts CT1 to CT4 are reduced each time the group read count GCT1 is increased, since an unnecessary increase in the group read count GCT1 is suppressed, it is possible to prevent a reliability management operation from being performed frequently. For example, in the case where sequential read operations for the memory regions MR1 to MR4 are continuously performed, the group read count GCT1 may be increased in response to a read access to the first memory region MR1 after all the region read counts CT1 to CT4 reach the first threshold value TH1. At this time, the region read counts CT2 to CT4 of the remaining memory regions MR2 to MR4 may be reduced. Therefore, the group read count GCT1 may be increased in response to a read access to the first memory region MR1 after read accesses to the remaining memory regions MR2 to MR4 are respectively performed. Namely, since the group read count GCT1 is not increased each time each of the memory regions MR1 to MR4 is read-accessed, a reliability management operation based on the group read count GCT1 may be suppressed from being performed too frequently.
-
FIG. 5 is a diagram illustrating adata processing system 1000 including a solid state drive (SSD) 1200 in accordance with an embodiment. Referring toFIG. 5 , thedata processing system 1000 may include ahost device 1100 and theSSD 1200. - The
SSD 1200 may include acontroller 1210, abuffer memory device 1220, a plurality ofnonvolatile memory devices 1231 to 123 n, apower supply 1240, asignal connector 1250, and apower connector 1260. - The
controller 1210 may control general operations of theSSD 1200. Thecontroller 1210 may include ahost interface unit 1211, acontrol unit 1212, arandom access memory 1213, an error correction code (ECC)unit 1214, and amemory interface unit 1215. - The
host interface unit 1211 may exchange a signal SGL with thehost device 1100 through thesignal connector 1250. The signal SGL may include a command, an address, data, and so forth. Thehost interface unit 1211 may interface thehost device 1100 and theSSD 1200 according to the protocol of thehost device 1100. For example, thehost interface unit 1211 may communicate with thehost device 1100 through any one of standard interface protocols such as secure digital, universal serial bus (USB), multimedia card (MMC), embedded MMC (eMMC), personal computer memory card international association (PCMCIA), parallel advanced technology attachment (DATA), serial advanced technology attachment (SATA), small computer system interface (SCSI), serial attached SCSI (SAS), peripheral component interconnection (PCI), PCI express (PCI-E) and universal flash storage (UFS). - The
control unit 1212 may analyze and process the signal SGL received from thehost device 1100. Thecontrol unit 1212 may control operations of internal function blocks according to a firmware or a software for driving theSSD 1200. Therandom access memory 1213 may be used as a working memory for driving such a firmware or software. - The
control unit 1212 may include thecount management circuit 111 and thereliability management circuit 112 shown inFIG. 1 . Thecontrol unit 1212 may operate in the same manner as thecount management circuit 111 and thereliability management circuit 112. - The
ECC unit 1214 may generate the parity data of thecount management circuit 111 and thereliability management circuit 112 data to be transmitted to at least one of thenonvolatile memory devices 1231 to 123 n. The generated parity data may be stored together with the data in thenonvolatile memory devices 1231 to 123 n. TheECC unit 1214 may detect an error of the data read from at least one of thenonvolatile memory devices 1231 to 123 n, based on the parity data. If a detected error is within a correctable range, theECC unit 1214 may correct the detected error. - The
memory interface unit 1215 may provide control signals such as commands and addresses to at least one of thenonvolatile memory devices 1231 to 123 n, according to control of thecontrol unit 1212. Moreover, thememory interface unit 1215 may exchange data with at least one of thenonvolatile memory devices 1231 to 123 n, according to control of thecontrol unit 1212. For example, thememory interface unit 1215 may provide the data stored in thebuffer memory device 1220, to at least one of thenonvolatile memory devices 1231 to 123 n, or provide the data read from at least one of thenonvolatile memory devices 1231 to 123 n, to thebuffer memory device 1220. - The
buffer memory device 1220 may temporarily store data to be stored in at least one of thenonvolatile memory devices 1231 to 123 n. Further, thebuffer memory device 1220 may temporarily store the data read from at least one of thenonvolatile memory devices 1231 to 123 n. The data temporarily stored in thebuffer memory device 1220 may be transmitted to thehost device 1100 or at least one of thenonvolatile memory devices 1231 to 123 n according to control of thecontroller 1210. - The
nonvolatile memory devices 1231 to 123 n may be used as storage media of theSSD 1200. Thenonvolatile memory devices 1231 to 123 n may be coupled with thecontroller 1210 through a plurality of channels CH1 to CHn, respectively. One or more nonvolatile memory devices may be coupled to one channel. The nonvolatile memory devices coupled to each channel may be coupled to the same signal bus and data bus. - The
power supply 1240 may provide power PWR inputted through thepower connector 1260, to the inside of theSSD 1200. Thepower supply 1240 may include anauxiliary power supply 1241. Theauxiliary power supply 1241 may supply power to allow theSSD 1200 to be normally terminated when a sudden power-off occurs. Theauxiliary power supply 1241 may include large capacity capacitors. - The
signal connector 1250 may be configured by various types of connectors depending on an interface scheme between thehost device 1100 and theSSD 1200. - The
power connector 1260 may be configured by various types of connectors depending on a power supply scheme of thehost device 1100. -
FIG. 6 is a diagram illustrating adata processing system 2000 including amemory system 2200 in accordance with an embodiment. Referring toFIG. 6 , thedata processing system 2000 may include ahost device 2100 and thememory system 2200. - The
host device 2100 may be configured in the form of a board such as a printed circuit board. Although not shown, thehost device 2100 may include internal function blocks for performing the function of a host device. - The
host device 2100 may include aconnection terminal 2110 such as a socket, a slot or a connector. Thememory system 2200 may be mounted to theconnection terminal 2110. - The
memory system 2200 may be configured in the form of a board such as a printed circuit board. Thememory system 2200 may be referred to as a memory module or a memory card. Thememory system 2200 may include acontroller 2210, abuffer memory device 2220,nonvolatile memory devices connection terminal 2250. - The
controller 2210 may control general operations of thememory system 2200. Thecontroller 2210 may be configured in the same manner as thecontroller 1210 shown inFIG. 5 . - The
buffer memory device 2220 may temporarily store data to be stored in thenonvolatile memory devices buffer memory device 2220 may temporarily store the data read from thenonvolatile memory devices buffer memory device 2220 may be transmitted to thehost device 2100 or thenonvolatile memory devices controller 2210. - The
nonvolatile memory devices memory system 2200. - The
PMIC 2240 may provide the power inputted through theconnection terminal 2250, to the inside of thememory system 2200. ThePMIC 2240 may manage the power of thememory system 2200 according to control of thecontroller 2210. - The
connection terminal 2250 may be coupled to theconnection terminal 2110 of thehost device 2100. Through theconnection terminal 2250, signals such as commands, addresses, data and so forth and power may be transferred between thehost device 2100 and thememory system 2200. Theconnection terminal 2250 may be configured into various types depending on an interface scheme between thehost device 2100 and thememory system 2200. Theconnection terminal 2250 may be disposed on any one side of thememory system 2200. -
FIG. 7 is a diagram illustrating adata processing system 3000 including amemory system 3200 in accordance with an embodiment. Referring toFIG. 7 , thedata processing system 3000 may include ahost device 3100 and thememory system 3200. - The
host device 3100 may be configured in the form of a board such as a printed circuit board. Although not shown, thehost device 3100 may include internal function blocks for performing the function of a host device. - The
memory system 3200 may be configured in the form of a surface-mounting type package. Thememory system 3200 may be mounted to thehost device 3100 throughsolder balls 3250. Thememory system 3200 may include acontroller 3210, abuffer memory device 3220, and anonvolatile memory device 3230. - The
controller 3210 may control general operations of thememory system 3200. Thecontroller 3210 may be configured in the same manner as thecontroller 1210 shown inFIG. 5 . - The
buffer memory device 3220 may temporarily store data to be stored in thenonvolatile memory device 3230. Further, thebuffer memory device 3220 may temporarily store the data read from thenonvolatile memory device 3230. The data temporarily stored in thebuffer memory device 3220 may be transmitted to thehost device 3100 or thenonvolatile memory device 3230 according to control of thecontroller 3210. - The
nonvolatile memory device 3230 may be used as the storage medium of thememory system 3200. -
FIG. 8 is a diagram illustrating anetwork system 4000 including amemory system 4200 in accordance with an embodiment. Referring toFIG. 8 , thenetwork system 4000 may include aserver system 4300 and a plurality ofclient systems 4410 to 4430 which are coupled through anetwork 4500. - The
server system 4300 may service data in response to requests from the plurality ofclient systems 4410 to 4430. For example, theserver system 4300 may store the data provided from the plurality ofclient systems 4410 to 4430. For another example, theserver system 4300 may provide data to the plurality ofclient systems 4410 to 4430. - The
server system 4300 may include ahost device 4100 and thememory system 4200. Thememory system 4200 may be configured by thememory system 100 shown inFIG. 1 , thememory system 1200 shown inFIG. 5 , thememory system 2200 shown inFIG. 6 or thememory system 3200 shown inFIG. 7 . -
FIG. 9 is a block diagram illustrating anonvolatile memory device 300 included in a memory system in accordance with an embodiment. Referring toFIG. 9 , thenonvolatile memory device 300 may include amemory cell array 310, arow decoder 320, a data read/write block 330, acolumn decoder 340, avoltage generator 350, and acontrol logic 360. - The
memory cell array 310 may include memory cells MC which are arranged at areas where word lines WL1 to WLm and bit lines BL1 to BLn intersect with each other. - The
row decoder 320 may be coupled with thememory cell array 310 through the word lines WL1 to WLm. Therow decoder 320 may operate according to control of thecontrol logic 360. Therow decoder 320 may decode an address provided from an external device (not shown). Therow decoder 320 may select and drive the word lines WL1 to WLm, based on a decoding result. For instance, therow decoder 320 may provide a word line voltage provided from thevoltage generator 350, to the word lines WL1 to WLm. - The data read/
write block 330 may be coupled with thememory cell array 310 through the bit lines BL1 to BLn. The data read/write block 330 may include read/write circuits RW1 to RWn respectively corresponding to the bit lines BL1 to BLn. The data read/write block 330 may operate according to control of thecontrol logic 360. The data read/write block 330 may operate as a write driver or a sense amplifier according to an operation mode. For example, the data read/write block 330 may operate as a write driver which stores data provided from the external device, in thememory cell array 310 in a write operation. For another example, the data read/write block 330 may operate as a sense amplifier which reads out data from thememory cell array 310 in a read operation. - The
column decoder 340 may operate according to control of thecontrol logic 360. Thecolumn decoder 340 may decode an address provided from the external device. Thecolumn decoder 340 may couple the read/write circuits RW1 to RWn of the data read/write block 330 respectively corresponding to the bit lines BL1 to BLn with data input/output lines or data input/output buffers, based on a decoding result. - The
voltage generator 350 may generate voltages to be used in internal operations of thenonvolatile memory device 300. The voltages generated by thevoltage generator 350 may be applied to the memory cells of thememory cell array 310. For example, a program voltage generated in a program operation may be applied to a word line of memory cells for which the program operation is to be performed. For another example, an erase voltage generated in an erase operation may be applied to a well area of memory cells for which the erase operation is to be performed. For still another example, a read voltage generated in a read operation may be applied to a word line of memory cells for which the read operation is to be performed. - The
control logic 360 may control general operations of thenonvolatile memory device 300, based on control signals provided from the external device. For example, thecontrol logic 360 may control operations of thenonvolatile memory device 300 such as read, write and erase operations of thenonvolatile memory device 300. - While various embodiments have been described above, it will be understood to those skilled in the art that the embodiments described are examples only. Accordingly, the memory system and the operating method thereof described herein should not be limited based on the described embodiments.
Claims (20)
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR1020180092542A KR102668125B1 (en) | 2018-08-08 | 2018-08-08 | Memory system and operating method thereof |
KR10-2018-0092542 | 2018-08-08 |
Publications (2)
Publication Number | Publication Date |
---|---|
US10553292B1 US10553292B1 (en) | 2020-02-04 |
US20200051647A1 true US20200051647A1 (en) | 2020-02-13 |
Family
ID=69230348
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/221,956 Active US10553292B1 (en) | 2018-08-08 | 2018-12-17 | Memory system with memory region read counts and a memory group read count and operating method thereof |
Country Status (3)
Country | Link |
---|---|
US (1) | US10553292B1 (en) |
KR (1) | KR102668125B1 (en) |
CN (1) | CN110825654B (en) |
Family Cites Families (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8074011B2 (en) * | 2006-12-06 | 2011-12-06 | Fusion-Io, Inc. | Apparatus, system, and method for storage space recovery after reaching a read count limit |
CN101499315B (en) * | 2008-01-30 | 2011-11-23 | 群联电子股份有限公司 | Average abrasion method of flash memory and its controller |
US7818525B1 (en) * | 2009-08-12 | 2010-10-19 | Texas Memory Systems, Inc. | Efficient reduction of read disturb errors in NAND FLASH memory |
KR101222063B1 (en) * | 2011-02-28 | 2013-01-15 | 에스케이하이닉스 주식회사 | Non volatile memory device and operating method thereof |
US8811074B2 (en) * | 2012-04-03 | 2014-08-19 | Seagate Technology Llc | Parametric tracking to manage read disturbed data |
US9117533B2 (en) * | 2013-03-13 | 2015-08-25 | Sandisk Technologies Inc. | Tracking erase operations to regions of non-volatile memory |
TWI525635B (en) * | 2013-12-17 | 2016-03-11 | 慧榮科技股份有限公司 | Data storage device and data maintenance method thereof |
US9230689B2 (en) | 2014-03-17 | 2016-01-05 | Sandisk Technologies Inc. | Finding read disturbs on non-volatile memories |
US9678827B2 (en) * | 2014-10-07 | 2017-06-13 | SK Hynix Inc. | Access counts for performing data inspection operations in data storage device |
US9760478B2 (en) * | 2014-12-02 | 2017-09-12 | Macronix International Co., Ltd. | Read leveling method and memory device using the same |
CN105260320B (en) * | 2015-10-12 | 2020-06-16 | 珠海格力电器股份有限公司 | Data processing method and device for FLASH memory |
KR20170086840A (en) * | 2016-01-19 | 2017-07-27 | 에스케이하이닉스 주식회사 | Data storage device and operating method thereof |
KR20180014975A (en) * | 2016-08-02 | 2018-02-12 | 에스케이하이닉스 주식회사 | Data storage device and operating method thereof |
US10340016B2 (en) * | 2017-06-26 | 2019-07-02 | Micron Technology, Inc. | Methods of error-based read disturb mitigation and memory devices utilizing the same |
KR20190001300A (en) * | 2017-06-27 | 2019-01-04 | 에스케이하이닉스 주식회사 | Controller and memory system and operating method of memory system |
KR102549548B1 (en) * | 2018-05-08 | 2023-06-30 | 에스케이하이닉스 주식회사 | Memory system, operating method thereof and electronic device |
-
2018
- 2018-08-08 KR KR1020180092542A patent/KR102668125B1/en active IP Right Grant
- 2018-12-17 US US16/221,956 patent/US10553292B1/en active Active
- 2018-12-27 CN CN201811611423.1A patent/CN110825654B/en active Active
Also Published As
Publication number | Publication date |
---|---|
CN110825654A (en) | 2020-02-21 |
KR20200017220A (en) | 2020-02-18 |
US10553292B1 (en) | 2020-02-04 |
KR102668125B1 (en) | 2024-05-23 |
CN110825654B (en) | 2023-04-07 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11101017B2 (en) | Memory system and test system | |
US20190265907A1 (en) | Electronic device and operating method thereof | |
US20190057049A1 (en) | Memory system and operating method thereof | |
US12026398B2 (en) | Memory system performing flush operation for buffer region | |
US11704048B2 (en) | Electronic device | |
US10747660B2 (en) | Method and system for forming and using memory superblocks based on performance grades | |
US11157201B2 (en) | Memory system and operating method thereof | |
US20200150898A1 (en) | Memory system and operating method thereof | |
US20190057026A1 (en) | Data storage device and operating method thereof | |
US20200125285A1 (en) | Memory system and operating method thereof | |
US11079952B2 (en) | Data storage device performing scan operations on memory regions to move data and operation method thereof | |
US20190179781A1 (en) | Memory system and operating method thereof | |
US11467910B2 (en) | Memory system re-performing access operation and operating method thereof | |
US10776008B2 (en) | Memory system and operating method thereof | |
US10929055B2 (en) | Memory system and operating method thereof | |
US10628067B2 (en) | Memory system and operating method thereof | |
US10553292B1 (en) | Memory system with memory region read counts and a memory group read count and operating method thereof | |
US20190179744A1 (en) | Memory system and operating method thereof | |
KR20200093363A (en) | Memory system | |
US20210223956A1 (en) | Memory system and data processing system including the same | |
US11099742B2 (en) | Electronic device | |
US10643716B2 (en) | Nonvolatile memory device and memory system including the nonvolatile memory device | |
KR20210093610A (en) | Nonvolatile memory device and memory system including the same |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: SK HYNIX INC., KOREA, REPUBLIC OF Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:JUNG, YONG IL;SHIN, DAE SEOK;REEL/FRAME:047794/0453 Effective date: 20181212 |
|
FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |