US20190205038A1 - Data storage apparatus, operating method thereof, and data processing system including the same - Google Patents
Data storage apparatus, operating method thereof, and data processing system including the same Download PDFInfo
- Publication number
- US20190205038A1 US20190205038A1 US16/052,234 US201816052234A US2019205038A1 US 20190205038 A1 US20190205038 A1 US 20190205038A1 US 201816052234 A US201816052234 A US 201816052234A US 2019205038 A1 US2019205038 A1 US 2019205038A1
- Authority
- US
- United States
- Prior art keywords
- open
- blocks
- die
- flush
- super
- 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
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/14—Handling requests for interconnection or transfer
- G06F13/16—Handling requests for interconnection or transfer for access to memory bus
- G06F13/1668—Details of memory controller
- G06F13/1673—Details of memory controller using buffers
-
- 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
- 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/08—Addressing or allocation; Relocation in hierarchically structured memory systems, e.g. virtual memory systems
- G06F12/0802—Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches
- G06F12/0891—Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches using clearing, invalidating or resetting means
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/0604—Improving or facilitating administration, e.g. storage management
- G06F3/0607—Improving or facilitating administration, e.g. storage management by facilitating the process of upgrading existing storage systems, e.g. for improving compatibility between host and storage device
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/061—Improving I/O performance
- G06F3/0613—Improving I/O performance in relation to throughput
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0638—Organizing or formatting or addressing of data
- G06F3/064—Management of blocks
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0646—Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems
- G06F3/0652—Erasing, e.g. deleting, data cleaning, moving of data to a wastebasket
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0655—Vertical data movement, i.e. input-output transfer; data movement between one or more hosts and one or more storage devices
- G06F3/0656—Data buffering arrangements
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0655—Vertical data movement, i.e. input-output transfer; data movement between one or more hosts and one or more storage devices
- G06F3/0659—Command handling arrangements, e.g. command buffers, queues, command scheduling
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
- G06F3/0671—In-line storage system
- G06F3/0673—Single storage device
- G06F3/0679—Non-volatile semiconductor memory device, e.g. flash memory, one time programmable memory [OTP]
-
- 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/08—Addressing or allocation; Relocation in hierarchically structured memory systems, e.g. virtual memory systems
- G06F12/0802—Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches
- G06F12/0866—Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches for peripheral storage systems, e.g. disk cache
- G06F12/0868—Data transfer between cache memory and other subsystems, e.g. storage devices or host systems
-
- 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/1016—Performance improvement
-
- 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
-
- 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/20—Employing a main memory using a specific memory technology
- G06F2212/202—Non-volatile memory
- G06F2212/2022—Flash memory
-
- 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/21—Employing a record carrier using a specific recording technology
- G06F2212/214—Solid state disk
-
- 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/7202—Allocation control and policies
-
- 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/7203—Temporary buffering, e.g. using volatile buffer or dedicated buffer blocks
-
- 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/7204—Capacity control, e.g. partitioning, end-of-life degradation
-
- 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/7208—Multiple device management, e.g. distributing data over multiple flash devices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
- G06F3/0671—In-line storage system
- G06F3/0673—Single storage device
Definitions
- Various embodiments may generally relate to a semiconductor apparatus, and more particularly, to a data storage apparatus, an operating method thereof, and a data processing system including the same.
- portable electronic apparatuses such as a mobile phone, a digital camera, and a laptop computer has been increasing rapidly.
- portable electronic apparatuses use data storage apparatuses that employ memory devices. Data storage apparatuses may be used to store data used in the portable electronic apparatuses.
- Data storage apparatuses using memory devices have no mechanical driving units and exhibit good stability and endurance, fast information access rate, and low power consumption.
- Such data storage apparatuses may include a universal serial bus (USB) memory device, a memory card having various interfaces, a universal flash storage (UFS) device, a solid-state drive (SSD), and the like.
- USB universal serial bus
- UFS universal flash storage
- SSD solid-state drive
- Embodiments of the present invention are directed to a data storage apparatus with improved write performance, an operating method thereof, and a data processing system including the same.
- a data storage apparatus may include: a nonvolatile memory device including a plurality of dies each die comprising a plurality of memory blocks with the memory blocks being configured as a plurality of super blocks and a plurality of flush buffer blocks; a random-access memory including an open super block manager configured to manage an index of one open super block allocated among the plurality of super blocks and a location into which data is to be written in the allocated one open super block and an open flush buffer block manager configured to manage indexes of a plurality of open flush buffer blocks allocated to the dies and locations into which data is to be written in the allocated open flush buffer blocks; and a processor configured to identify a first die in which a normal write operation is being performed and a second die next to the first die using the open super block manager when a flush write request is received from a host apparatus, select at least one open flush buffer block included in dies other than the first die and the second die using the open flush buffer block manager, and control the nonvolatile memory device to perform a flush write
- an operating method of a data storage apparatus may include: identifying a first die in which a normal write operation is currently performed and a second die next to the first die when a flush write request is received from a host apparatus; selecting at least one open flush buffer block included in dies other than the first die and the second die; and controlling a nonvolatile memory device to perform a flush write operation on the selected open flush buffer block.
- a data processing system may include: a host apparatus configured to transfer a flush write request; and a data storage apparatus including a nonvolatile memory device configured to include a plurality of dies configured as a plurality of super blocks and a plurality of flush buffer blocks and a controller configured to control the nonvolatile memory device.
- the controller may include: a random-access memory including an open super block manager configured to manage an index of one open super block allocated among the plurality of super blocks and a location into which data is to be written in the allocated open super block and an open flush buffer block manager configured to manage indexes of a plurality of open flush buffer blocks allocated to the plurality of dies and locations into which data is to be written in the allocated open flush buffer blocks; and a processor configured to identify a first die in which a normal write operation is being performed and a second die next to the first die using the open super block manager when the flush write request is received from the host apparatus, select at least one open flush buffer block included in dies other than the first die and the second die using the open flush buffer block manager, and control the nonvolatile memory device to perform a flush write operation on the selected open flush buffer block.
- a random-access memory including an open super block manager configured to manage an index of one open super block allocated among the plurality of super blocks and a location into which data is to be written in the allocated open super block and an open
- a memory system may include: a memory device including dies each including element memory blocks of super blocks and including one or more flush buffer blocks; and a controller suitable for managing an information of a second die subsequent to a first die in an order of a super block write operation currently being performed to the first die among the dies, and controlling, in response to a flush operation, the memory device to perform a flush operation to one of the flush buffer blocks included in a die other than the first and second dies among the dies.
- a memory block of a die other than a die to which a normal write data storing operation is interrupted and a die to which the normal write data storing operation is to be resumed may be selected as a flush buffer block.
- the flush write data may be securely stored while securing an interleaving scheme for a normal write operation of the normal write data.
- FIG. 1 is a block diagram illustrating a configuration example of a data storage apparatus, in accordance with an embodiment of the present disclosure
- FIG. 2 is a diagram illustrating a configuration example of a nonvolatile memory device of FIG. 1 ;
- FIG. 3A is a diagram explaining a configuration example of a super block and a write operation sequence, in accordance with an embodiment of the present disclosure
- FIG. 3B is a diagram illustrating a configuration example of a super block pool, in accordance with an embodiment of the present disclosure
- FIG. 3C is a diagram illustrating an example of an information table for an allocated super block, in accordance with an embodiment of the present disclosure
- FIG. 4A is a diagram illustrating a configuration example of a flush buffer block group, in accordance with an embodiment of the present disclosure
- FIG. 4B is a diagram illustrating a configuration example of a flush buffer block pool, in accordance with an embodiment of the present disclosure
- FIG. 4C is a diagram illustrating an example of an information table for allocated flush buffer blocks, in accordance with an embodiment of the present disclosure
- FIG. 5 is a diagram illustrating an example that a flush write request is generated during a normal write operation, in accordance with an embodiment of the present disclosure
- FIG. 6 is a flowchart illustrating an operating method of a data storage apparatus, in accordance with an embodiment of the present disclosure
- FIG. 7 is a diagram illustrating an example of a data processing system including a solid-state drive, in accordance with an embodiment of the present disclosure
- FIG. 8 is a diagram illustrating an example of a controller illustrated in FIG. 7 , in accordance with an embodiment of the present invention disclosure
- FIG. 9 is a diagram illustrating an example of a data processing system including a data storage apparatus, in accordance with an embodiment of the present disclosure.
- FIG. 10 is a diagram illustrating an example of a data processing system including a data storage apparatus, in accordance with an embodiment of the present disclosure
- FIG. 11 is a diagram illustrating an example of a network system including a data storage apparatus, in accordance with an embodiment of the present disclosure.
- FIG. 12 is a block diagram illustrating an example of a nonvolatile memory device included in a data storage apparatus, in accordance with an embodiment of the present disclosure.
- 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 data storage apparatus 10 in accordance with an embodiment.
- the data storage apparatus 10 in accordance with an embodiment may store data to be accessed by a host apparatus (not shown).
- the host apparatus may be a device such as a mobile phone, an MP3 player, a laptop computer, a desktop computer, a game player, a television (TV), an in-vehicle infotainment system, and the like.
- the data storage apparatus 10 may also be referred to as a memory system.
- the data storage apparatus 10 may be manufactured as any one among various types of storage apparatuses and may be operatively coupled according to a host interface transfer protocol with a host apparatus (not shown).
- the data storage apparatus 10 may be configured as any one of various types of storage apparatuses, such as a solid-state drive (SSD), a multimedia card in the form of an MMC, an eMMC, an RS-MMC, and a micro-MMC, a secure digital card in the form of an SD, a mini-SD, and a 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 interconnection (PCI) card type storage device, a PCI-express (PCI-E) card type storage device, a compact flash (CF) card, a smart media card, a memory stick, and the like.
- SSD solid-state drive
- MMC multimedia card in the form of an MMC
- the data storage apparatus 10 may be manufactured as any one among various types of packages.
- the data storage apparatus 10 may be manufactured as any one of various types of packages, such 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 fabricated package (WFP), and a wafer-level stack package (WSP).
- POP package on package
- SIP system in package
- SOC system on chip
- MCP multi-chip package
- COB chip on board
- WFP wafer-level fabricated package
- WSP wafer-level stack package
- the data storage apparatus 10 may include a nonvolatile memory device 100 and a controller 200 operatively coupled via one or more communication channels CH.
- the nonvolatile memory device 100 may be operated as a storage medium of the data storage apparatus 10 .
- the nonvolatile memory device 100 may include any one of various types of nonvolatile memory devices, such as a NAND flash memory device, a NOR flash memory device, a ferroelectric random-access memory (FRAM) using a ferroelectric capacitor, a magnetic random-access memory (MRAM) using a tunneling magneto-resistive (TMR) layer, a phase-change random-access memory (PRAM) using a chalcogenide alloy, and a resistive random-access memory (RERAM) using a transition metal compound.
- a NAND flash memory device a NOR flash memory device
- FRAM ferroelectric random-access memory
- MRAM magnetic random-access memory
- TMR tunneling magneto-resistive
- PRAM phase-change random-access memory
- RERAM resistive random-access memory
- the nonvolatile memory device 100 may include a plurality of dies, each die including a plurality of memory blocks.
- the nonvolatile memory device 100 may include a memory cell array including a plurality of memory cells (not shown) arranged in regions in which a plurality of word lines (not shown) and a plurality of bit lines (not shown) cross each other.
- the memory cell array may include a plurality of memory blocks and each of the plurality of memory blocks may include a plurality of pages.
- each of the memory cells in the memory cell array may be at least one among a single level cell (SLC) in which a single bit data (for example, 1-bit data) is stored, a multilevel cell (MLC) in which 2-bit data is stored, a triple level cell (TLC) in which 3-bit data is stored, and a quad level cell QLC in which 4-bit data is stored.
- the memory cell array may include at least one or more cells among the SLC, the MLC, the TLC, and the QLC.
- the memory cell array may include memory cells arranged in a two-dimensional (2D) horizontal structure or memory cells having a 3D vertical structure.
- the controller 200 may include a host interface 210 , a processor 220 , a random-access memory (RAM) 230 , and a memory interface 240 .
- the host interface 210 may perform interfacing between a host apparatus (not shown) and the data storage device 10 .
- the host interface 210 may communicate with the host apparatus through any one among standard transfer protocols such as a USB protocol, a UFS protocol, an MMC protocol, a parallel advanced technology attachment (PATA) protocol, a serial advanced technology attachment (SATA) protocol, a small computer system interface (SCSI) protocol, a serial attached SCSI (SAS) protocol, a PCI protocol, and a PCI-E protocol.
- standard transfer protocols such as a USB protocol, a UFS protocol, an MMC protocol, a parallel advanced technology attachment (PATA) protocol, a serial advanced technology attachment (SATA) protocol, a small computer system interface (SCSI) protocol, a serial attached SCSI (SAS) protocol, a PCI protocol, and a PCI-E protocol.
- the processor 220 may be configured as a micro control unit (MCU) or a central processing unit (CPU).
- the processor 220 may process a request (for example, read request and write request) transmitted from the host apparatus.
- the processor 220 may drive a code-type instruction or algorithm (e.g., software) which is loaded into the RAM 230 for controlling internal function blocks and/or the nonvolatile memory device 100 .
- the RAM 230 may be configured as a random-access memory, such as a dynamic RAM (DRAM) or a static RAM (SRAM).
- the RAM 230 may store software driven through the processor 220 .
- the RAM 230 may store data required for the driving of the software.
- the RAM 230 may be operated as a working memory of the processor 220 .
- the processor 220 may control an internal operation of the nonvolatile memory device 100 and drive software known as a flash translation layer (FTL) to provide device compatibility to a host apparatus.
- FTL flash translation layer
- the host apparatus may use the data storage apparatus 10 by recognizing the data storage apparatus 10 as a general data storage apparatus such as a hard disc.
- the flash translation layer may be loaded into the RAM 230 and may include modules configured to perform various functions and metadata required for the driving of the modules.
- the flash translation layer (FTL) may include a ware-leveling module, a bad block management module, a garbage collection module, an interleaving module, a sudden power-off management module, an address map, and the like, however, the configuration of the flash translation layer (FTL) is not limited thereto.
- the RAM 230 may temporarily store data which is to be transmitted to the nonvolatile memory device 100 from a host apparatus or data which is read from the nonvolatile memory device 100 and is to be transmitted to the host apparatus.
- the RAM 230 may be operated as a buffer memory of the processor 220 .
- the RAM 230 may include a super block pool SBP, an open super block manager OSBM, a flush buffer block pool FBP, and an open flush buffer block manager OFBM.
- the super block pool SBP may be configured to include information such as allocation/free and an erase/write (E/W) count for each of super blocks included in the nonvolatile memory device 100 .
- E/W erase/write
- the open super block manager OSBM may be configured to manage information such as an index of an open super block and a location into which data is to be written in the open super block allocated among a plurality of super blocks included in the nonvolatile memory device 100 .
- the location into which data is to be written may represent a page number (for example, page address) and a sector number in the allocated open super block.
- the open super block manager OSBM may update the index of the open super block due to the newly allocated open super block.
- the open super block manager OSBM may update the location into which data is to be written, for example, the page number and the sector number in the open super block.
- the flush buffer block pool FBP may be configured to include information such as allocation/free and an E/W count for each of flush buffer blocks included in the nonvolatile memory device 100 .
- the flush buffer block and the flush buffer block pool FBP will be described later in detail with reference to the related drawings.
- the open flush buffer block manager OFBM may be configured to manage information such as indexes of open flush buffer blocks and locations into which data is to be written in the open flush buffer blocks allocated among a plurality of plush buffer blocks included in the nonvolatile memory device 100 .
- a single memory block may be allocated as the flush buffer block for each die (see D 1 to Di of FIG. 2 ). Accordingly, the open flush buffer block manager OFBM may manage information for the same number of open flush buffer blocks as the number (for example, the number of ‘i’) of dies.
- the location into which data is to be written may include a page number (for example, page address) and a sector number in the allocated open flush buffer blocks.
- the open flush buffer block manager OFBM may update the index of the open flush buffer block corresponding to each die D 1 to Di due to the newly allocated open flush buffer block.
- the open flush buffer block manager OFBM may update the location into which data is to be written for each open flush buffer block, for example, the page number and the sector number in the open flush buffer block.
- FIG. 2 is a diagram illustrating a configuration example of the nonvolatile memory device 100 of FIG. 1 .
- the nonvolatile memory device 100 may include the plurality of dies D 1 to Di.
- Each of the plurality of dies D 1 to Di may include a plurality of memory blocks B 1 to Bk.
- each of the dies D 1 to Di may include a plurality of planes including a plurality of memory blocks.
- each of the dies D 1 to Di includes one plane.
- the same memory blocks in the dies D 1 to Di may be grouped into one memory block group.
- the one memory block group that the same memory blocks in the dies D 1 to Di are grouped may also be referred to as a super block.
- the first memory blocks B 1 in the dies D 1 to Di may be grouped into and used as a first super block SB 1 .
- the controller 200 may operate the i first memory blocks B 1 included in the first super block SB 1 in parallel. For example, the controller 200 may control the nonvolatile memory device 100 to simultaneously perform an operation such as a read or write operation on the i first memory blocks B 1 included in the first super block SB 1 simultaneously.
- the number of super blocks SB included in the nonvolatile memory device 100 may be smaller than the number of memory blocks B 1 to Bk included in each of the dies D 1 to Di.
- the first memory blocks B 1 to j-th memory blocks Bj of the dies D 1 to Di may be grouped into and used as the first super block SB 1 to a j-th super block SBj.
- k and j may be an integer of 1 or more and j may be smaller than k.
- Other memory blocks for example, j+1-th memory blocks Bj+1 to k-th memory blocks Bk in the dies D 1 to Di other than the memory blocks B 1 to Bk included in the super blocks SB 1 to SBj may not be grouped into super blocks and may be used as unit memory blocks.
- a portion of or all the memory blocks among the j+1-th to k-th memory blocks Bj+1 to Bk may be designated as flush buffer blocks FB.
- the flush buffer blocks FB may be a space configured to temporarily store data stored in a data buffer (not shown) when the flush request is received from a host apparatus or sudden power-off occurs.
- the controller 200 may include a data buffer configured to temporarily store write data received from a host apparatus. Whenever the write request and the write data are received from the host apparatus in a normal state, the processor 220 may not instantly store the write data in the nonvolatile memory device 100 but may temporarily buffer the write data in the data buffer until the buffered write data has a preset size. When a size of the write data stored in the data buffer is larger than a preset size, the processor 220 may control the nonvolatile memory device 100 to store the write data stored in the data buffer in an allocated open super block.
- the preset size may refer to a minimum size sufficient to perform a write operation. When the size of the write data stored in the data buffer reaches the minimum size sufficient to perform the write operation, the processor 220 may control the nonvolatile memory device 100 to store the corresponding write data in an open super block.
- the processor 220 may select one flush buffer block among a plurality of designated flush buffer blocks and control the nonvolatile memory device 100 to store the write data which are stored in the data buffer in the selected flush buffer block.
- the data stored in the flush buffer block may be stored in the data buffer again through control of the processor 220 and then stored in an allocated open super block along with the write data transferred from the host apparatus when the size of the data in the data buffer becomes larger than the preset size.
- FIG. 3A is a diagram explaining a configuration example of a super block and a write operation sequence in accordance with an embodiment of the present disclosure
- FIG. 3B is a diagram illustrating a configuration example of the super block pool SBP in accordance with an embodiment of the present disclosure
- FIG. 3C is a diagram illustrating a configuration example of an information table managed by the open super block manager OSBM in accordance with an embodiment of the present disclosure.
- one super block SB may include the memory blocks (for example, first memory blocks B 1 ) selected from the dies D 1 to Di, respectively.
- Each of the plurality of first memory blocks B 1 may include a plurality of pages P 1 to Pn and each of the pages P 1 to Pn may include a plurality of sectors S 1 to S 4 , S 5 to S 8 , and Sm- 3 to Sm.
- S 1 to S 4 the number of sectors included in one page is not limited thereto.
- the sectors S 1 to Sm may be storage units in the nonvolatile memory device 100 for the write data received from a host apparatus. For example, when one sector is 4 Kbyte and the write data received from the host apparatus is 40 Kbyte, the write data may be written in ten sectors.
- the write operation for one super block SB may be performed based on a sequence represented with ⁇ circle around ( 1 ) ⁇ to ⁇ circle around (n) ⁇ indicated by dotted arrows in FIG. 3A .
- the write operation for the super block SB may start from the first super page P 1 and may be terminated in the n-th super page Pn.
- the write operation may start from the first sector S 1 and may be terminated to the m-th sector Sm.
- the write operation for a single super block SB may be sequentially performed in order of dies, pages, and sectors in the single super block SB.
- the processor 220 may allocate a super block SB, for example, an open super block to store normal write data.
- the normal write data may refer to write data having a size sufficient to perform a write operation.
- the processor 220 may allocate a free super block having the smallest E/W count among a plurality of free super blocks as the open super block with reference to the supper block pool SBP illustrated in FIG. 3B .
- the super block pool SBP may be configured to include information such as allocation/free and the E/W counts for all the super blocks (for example, first to j-th super blocks of FIG. 2 ) included in the nonvolatile memory device 100 .
- FIG. 3B illustrates an example that the first super block SB 1 is allocated as the open super block.
- the processor 220 may manage an index (for example, ‘1’) of the allocated open super block and a page number (for example, ‘1’) and a sector number (for example, ‘1’) into which data is to be written in the allocated open super block using the open super block manager OSBM as illustrated in FIG. 3C .
- the state that both the page number and the sector are ‘1’ may refer to an initial state that the write data is not stored.
- the page number and the sector number are respectively ‘2’ and ‘7’ in the table managed by the open super block manager OSBM may represent that the location in which the normal write data is to be stored is the seventh sector S 7 of the second page P 2 in the second die D 2 as illustrated in FIG. 3 A.
- FIG. 4A is a diagram illustrating a configuration example of a flush buffer block group FBG in accordance with an embodiment of the present disclosure
- FIG. 4B is a diagram illustrating a configuration example of the flush buffer block pool FBP in accordance with an embodiment of the present disclosure
- FIG. 4C is a diagram illustrating a configuration example of an information table managed by the open flush buffer block manager OFBM in accordance with an embodiment of the present disclosure.
- the flush buffer block group FBG may include a plurality of memory blocks. It has been illustrated in FIG. 4A that the flush buffer block group FBG includes all memory blocks other than the memory blocks included in the super blocks of FIG. 2 , however this is merely exemplary and this is not limited thereto.
- the j+1-th memory blocks Bj+1 to the k-th memory blocks Bk of the dies D 1 to Di included in the flush buffer block group FBG may be separately allocated and managed.
- Each memory block of the flush buffer block group FBG may include n pages, each page including four sectors like the memory blocks which are included in the super block.
- the processor 220 may allocate the flush buffer block FB, for example, open flush buffer blocks to store flush write data.
- the flush write data may refer to write data having a preset size or less stored in the data buffer (not shown) when a flush request is received from a host apparatus or a sudden power-off occurs.
- the processor 220 may select free flush buffer blocks having the smallest E/W count in the die D 1 to Di one by one with reference to the flush buffer block pool FBP illustrated in FIG. 4B .
- the processor 220 may allocate the selected free flush buffer blocks as a plurality of open flush buffer blocks.
- the flush buffer block pool FBP may be configured to include information such as allocation/free and the E/W count for each of the first to the h-th flush buffer blocks FB 1 to FBh in the dies D 1 to Di.
- the example that the first flush buffer block FB 1 of the first die D 1 , the second flush buffer block FB 2 of the second die D 2 , the first flush buffer block FB 1 of the i-th die Di, and the like are allocated as the open flush buffer blocks is illustrated in FIG. 4B .
- the processor 220 may manage the indexes (for example, ‘1’, ‘2’, ‘1’) of the allocated open flush buffer blocks and page numbers (for example, ‘1’, ‘1’) and the sector numbers (for example, ‘1’, ‘1’, ‘1’), into which data is to be written in the open flush buffer blocks allocated in the dies D 1 to Di using the open flush buffer block manager OFBM as illustrated in FIG. 4C .
- the state that all the page numbers and the sector numbers are ‘1’ may refer to an initial state that the flush write data is not stored.
- the indexes 1 to i of the dies D 1 to Di may be fixed and whenever the open flush buffer blocks in the dies are newly allocated, the indexes of the corresponding open flush buffer blocks may be updated.
- the page numbers and sector numbers corresponding to the open flush buffer blocks may be updated.
- the point of time at which the flush write data is stored into the allocated open flush buffer blocks may be randomized. For example, when a flush request is received or a sudden power-off occurs during an operation of storing the normal write data in the super block SB, the operation of storing the normal write data is immediately interrupted and the flush write data is stored.
- a program time interval t PROG for the normal write data and a program time interval t PROG for the flush write data in the same die may overlap each other and thus the data may be corrupted. Accordingly, a die other than the die for which the normal write data storing operation is interrupted and the die for which the normal write data storing operation is to be resumed may be selected as a die that the flush write data is to be stored.
- the flush write data may be securely stored while securing an interleaving scheme for a normal write operation of the normal write data.
- FIG. 5 is a diagram illustrating an example that a flush write operation is performed during a normal write operation in accordance with an embodiment of the present disclosure.
- the processor 220 may identify a die that the normal write operation is currently performed and a die that the normal write operation is to be subsequently performed using the open super block manager OSBM. For example, FIG. 5 illustrates that the die currently performing the normal write operation is the fourth die D 4 and that the normal write operation is to be subsequently performed in the fifth die D 5 .
- the processor 220 may select open flush buffer blocks included in dies other than the die (e.g., a fourth die D 4 ) to which the normal write operation is currently performed and the die (e.g., a fifth die D 5 ) to which the normal write operation is to be subsequently performed using the open flush buffer block manager OFBM.
- the open flush buffer blocks FB 1 and FB 2 of the first die D 1 and the second die D 2 are selected as illustrated in FIG. 5 .
- the processor 220 may control the nonvolatile memory device 100 to perform the flush write operation on the selected open flush buffer blocks FB 1 and FB 2 of the first die D 1 and the second die D 2 .
- the processor 220 may control the nonvolatile memory device 100 to resume the normal write operation to the die (i.e., the fifth die D 5 ) to which the normal write operation is supposed to be subsequently performed before the flush write operation is completed.
- the memory interface 240 may control the nonvolatile memory device 100 according to control of the processor 220 .
- the memory interface 240 may also be referred to as a memory controller.
- the memory interface 240 may provide control signals to the nonvolatile memory device 100 .
- the control signals may include a command, an address, and the like for controlling the nonvolatile memory device 100 .
- the memory interface 240 may provide data to the nonvolatile memory device 100 or receive data from the nonvolatile memory device 100 .
- the memory interface 240 may be coupled to the nonvolatile memory device 100 through a channel CH.
- the channel may include one or more signal lines.
- FIG. 6 is a flowchart of an operating method of a data storage apparatus in accordance with an embodiment of the present disclosure. The operating method of a data storage apparatus in accordance with an embodiment will be described with reference to FIG. 6 with FIGS. 1 to 5 .
- a processor (see 220 of FIG. 1 ) of the controller (see 200 of FIG. 1 ) may determine whether a flush write request is received from a host apparatus. When the flush write request is received, the processor may proceed to operation S 620 .
- the processor 220 may identify a die (for example, fourth die D 4 of FIG. 5 ) that a normal write operation is currently performed and a die (for example, fifth die D 5 of FIG. 5 ) that the normal write operation is to be subsequently performed using the open super block manager OSBM.
- the processor 220 may select open flush buffer blocks (see FB 1 and FB 2 of FIG. 5 ) included in dies (for example, first and second dies D 1 and D 2 of FIG. 5 ) other than the fourth die D 4 , to which the normal write data storing operation is interrupted, and the fifth die D 5 , to which the normal write data storing operation is to be resumed, using the open flush buffer block manager OFBM.
- the processor 220 may control the nonvolatile memory device 100 to perform the flush write operation on the selected open flush buffer blocks FB 1 and FB 2 .
- FIG. 7 is a diagram illustrating an example of a data processing system including a solid-state drive (SSD) in accordance with an embodiment.
- a data processing system 2000 may include a host apparatus 2100 and an SSD 2200 .
- the SSD 2200 may include a controller 2210 , a buffer memory device 2220 , nonvolatile memory devices 2231 to 223 n , a power supply 2240 , a signal connector 2250 , and a power connector 2260 .
- the controller 2210 may control an overall operation of the SSD 2220 .
- the buffer memory device 2220 may temporarily store data to be stored in the nonvolatile memory devices 2231 to 223 n .
- the buffer memory device 2220 may temporarily store data read from the nonvolatile memory devices 2231 to 223 n .
- the data temporarily stored in the buffer memory device 2220 may be transmitted to the host apparatus 2100 or the nonvolatile memory devices 2231 to 223 n in accordance with control of the controller 2210 .
- the nonvolatile memory devices 2231 to 223 n may be used as a storage medium of the SSD 2200 .
- the nonvolatile memory devices 2231 to 223 n may be coupled to the controller 2210 through a plurality of channels CH 1 to CHn.
- One or more nonvolatile memory devices may be coupled to one channel.
- the nonvolatile memory devices coupled to the one channel may be coupled to the same signal bus and the same data bus.
- the power supply 2240 may provide power PWR input through the power connector 2260 to the inside of the SSD 2200 .
- the power supply 2240 may include an auxiliary power supply 2241 .
- the auxiliary power supply 2241 may supply the power so that the SSD 2200 is normally terminated even when sudden power-off occurs.
- the auxiliary power supply 2241 may include large capacity capacitors capable of charging the power PWR.
- the controller 2210 may exchange a signal SGL with the host apparatus 2100 through the signal connector 2250 .
- the signal SGL may include a command, an address, data, and the like.
- the signal connector 2250 may be configured of various types of connectors according to an interfacing method between the host apparatus 2100 and the SSD 2200 .
- FIG. 8 is a diagram illustrating an example of the controller 2210 of FIG. 7 .
- the controller 2210 may include a host interface unit 2211 , a control unit 2212 , a random-access memory (RAM) 2213 , an error correction code (ECC) unit 2214 , and a memory interface unit 2215 .
- RAM random-access memory
- ECC error correction code
- the host interface unit 2211 may perform interfacing between the host apparatus 2100 and the SSD 2200 according to a protocol of the host apparatus 2100 .
- the host interface unit 2211 may communicate with the host apparatus 2100 through any one among a secure digital protocol, a universal serial bus (USB) protocol, a multimedia card (MMC) protocol, an embedded MMC (eMMC) protocol, a personal computer memory card international association (PCMCIA) protocol, a parallel advanced technology attachment (PATA) protocol, a serial advanced technology attachment (SATA) protocol, a small computer system interface (SCSI) protocol, a serial attached SCSI (SAS) protocol, a peripheral component interconnection (PCI) protocol, a PCI Express (PCI-E) protocol, and a universal flash storage (UFS) protocol.
- the host interface unit 2211 may perform a disc emulation function that the host apparatus 2100 recognizes the SSD 2200 as a general-purpose data storage apparatus, for example, a hard disc drive HDD.
- the control unit 2212 may analyze and process the signal SGL input from the host apparatus 2100 .
- the control unit 2212 may control operations of internal functional blocks according to firmware and/or software for driving the SDD 2200 .
- the RAM 2213 may be operated as a working memory for driving the firmware or software.
- the ECC unit 2214 may generate parity data for the data to be transferred to the nonvolatile memory devices 2231 to 223 n .
- the generated parity data may be stored in the nonvolatile memory devices 2231 to 223 n together with the data.
- the ECC unit 2214 may detect errors for data read from the nonvolatile memory devices 2231 to 223 n based on the parity data. When detected errors are within a correctable range, the ECC unit 2214 may correct the detected errors.
- the memory interface unit 2215 may provide a control signal such as a command and an address to the nonvolatile memory devices 2231 to 223 n according to control of the control unit 2212 .
- the memory interface unit 2215 may exchange data with the nonvolatile memory devices 2231 to 223 n according to control of the control unit 2212 .
- the memory interface unit 2215 may provide data stored in the buffer memory device 2220 to the nonvolatile memory devices 2231 to 223 n or provide data read from the nonvolatile memory devices 2231 to 223 n to the buffer memory device 2220 .
- the random-access memory 2213 may be configured as the RAM 230 of FIG. 1 .
- FIG. 9 is a diagram illustrating an example of a data processing system including a data storage apparatus in accordance with an embodiment.
- a data processing system 3000 may include a host apparatus 3100 and a data storage apparatus 3200 .
- the host apparatus 3100 may be configured in a board form such as a printed circuit board (PCB). Although not shown in FIG. 9 , the host apparatus 3100 may include internal functional blocks configured to perform functions of the host apparatus 3100 .
- PCB printed circuit board
- the host apparatus 3100 may include a connection terminal 3110 such as a socket, a slot, or a connector.
- the data storage apparatus 3200 may be mounted on the connection terminal 3110 .
- the data storage apparatus 3200 may be configured in a board form such as a PCB.
- the data storage apparatus 3200 may refer to a memory module or a memory card.
- the data storage apparatus 3200 may include a controller 3210 , a buffer memory device 3220 , nonvolatile memory devices 3231 to 3232 , a power management integrated circuit (PMIC) 3240 , and a connection terminal 3250 .
- PMIC power management integrated circuit
- the controller 210 may control an overall operation of the data storage apparatus 3200 .
- the controller 3210 may be configured to have the same configuration as the controller 2210 illustrated in FIG. 8 .
- the buffer memory device 3220 may temporarily store data to be stored in the nonvolatile memory devices 3231 and 3232 .
- the buffer memory device 3220 may temporarily store data read from the nonvolatile memory devices 3231 and 3232 .
- the data temporarily stored in the buffer memory device 3220 may be transmitted to the host apparatus 3100 or the nonvolatile memory devices 3231 and 3232 according to control of the controller 3210 .
- the nonvolatile memory devices 3231 and 3232 may be used as a storage medium of the data storage apparatus 3200 .
- the PMIC 3240 may provide power input through the connection terminal 3250 to the inside of the data storage apparatus 3200 .
- the PMIC 3240 may manage the power of the data storage apparatus 3200 according to control of the controller 3210 .
- the connection terminal 3250 may be coupled to the connection terminal 3110 of the host apparatus 3100 .
- a signal such as a command, an address, and data and power may be transmitted between the host apparatus 3100 and the data storage apparatus 3200 through the connection terminal 3250 .
- the connection terminal 3250 may be configured in various forms according to an interfacing method between the host apparatus 3100 and the data storage apparatus 3200 .
- the connection terminal 3250 may be arranged in any one side of the data storage apparatus 3200 .
- FIG. 10 is a diagram illustrating an example of a data processing system including a data storage apparatus in accordance with an embodiment.
- a data processing system 4000 may include a host apparatus 4100 and a data storage apparatus 4200 .
- the host apparatus 4100 may be configured in a board form such as a PCB. Although not shown in FIG. 10 , the host apparatus 4100 may include internal functional blocks configured to perform functions of the host apparatus 4100 .
- the data storage apparatus 4200 may be configured in a surface mounting packaging form.
- the data storage apparatus 4200 may be mounted on the host apparatus 4100 through solder balls 4250 .
- the data storage apparatus 4200 may include a controller 4210 , a buffer memory device 4220 , and a nonvolatile memory device 4230 .
- the controller 4210 may control an overall operation of the data storage apparatus 4200 .
- the controller 4210 may be configured to have the same configuration as the controller 2210 illustrated in FIG. 8 .
- the buffer memory device 4220 may temporarily store data to be stored in the nonvolatile memory device 4230 .
- the buffer memory device 4220 may temporarily store data read from the nonvolatile memory device 4230 .
- the data temporarily stored in the buffer memory device 4220 may be transmitted to the host apparatus 4100 or the nonvolatile memory device 4230 through control of the controller 4210 .
- the nonvolatile memory device 4230 may be used as a storage medium of the data storage apparatus 4200 .
- FIG. 11 is a diagram illustrating an example of a network system 5000 including a data storage apparatus in accordance with an embodiment.
- the network system 5000 may include a server system 5300 and a plurality of client systems 5410 to 5430 which are coupled through a network 5500 .
- the server system 5300 may serve data in response to requests of the plurality of client systems 5410 to 5430 .
- the server system 5300 may store data provided from the plurality of client systems 5410 to 5430 .
- the server system 5300 may provide data to the plurality of client systems 5410 to 5430 .
- the server system 5300 may include a host apparatus 5100 and a data storage apparatus 5200 .
- the data storage apparatus 5200 may be configured of the data storage apparatus 10 of FIG. 1 , the data storage apparatus 2200 of FIG. 7 , the data storage apparatus 3200 of FIG. 9 , or the data storage apparatus 4200 of FIG. 10 .
- FIG. 12 is a block diagram illustrating an example of a nonvolatile memory device included in a data storage apparatus in accordance with an embodiment.
- a nonvolatile memory device 100 may include a memory cell array 110 , a row decoder 120 , a column decoder 140 , a data read/write block 130 , a voltage generator 150 , and a control logic 160 .
- the memory cell array 110 may include memory cells MC arranged in regions in which word lines WL 1 to WLm and bit lines BL 1 to BLn cross to each other.
- the row decoder 120 may be coupled to the memory cell array 110 through the word lines WL 1 to WLm.
- the row decoder 120 may operate through control of the control logic 160 .
- the row decoder 120 may decode an address provided from an external apparatus (not shown).
- the row decoder 120 may select and drive the word lines WL 1 to WLm based on a decoding result. For example, the row decoder 120 may provide a word line voltage provided from the voltage generator 150 to the word lines WL 1 to WLm.
- the data read/write block 130 may be coupled to the memory cell array 110 through the bit lines BL 1 to BLn.
- the data read/write block 130 may include read/write circuits RW 1 to RWn corresponding to the bit lines BL 1 to BLn.
- the data read/write block 130 may operate according to control of the control logic 160 .
- the data read/write block 130 may operate as a write driver or a sense amplifier according to an operation mode.
- the data read/write block 130 may operate as the write driver configured to store data provided from an external apparatus in the memory cell array 110 in a write operation.
- the data read/write block 130 may operate as the sense amplifier configured to read data from the memory cell array 110 in a read operation.
- the column decoder 140 may operate through control of the control logic 160 .
- the column decoder 140 may decode an address provided from an external apparatus (not shown).
- the column decoder 140 may couple the read/write circuits RW 1 to RWn of the data read/write block 130 corresponding to the bit lines BL 1 to BLn and data input/output (I/O) lines (or data I/O buffers) based on a decoding result.
- the voltage generator 150 may generate voltages used for an internal operation of the nonvolatile memory device 100 .
- the voltages generated through the voltage generator 150 may be applied to the memory cells of the memory cell array 110 .
- a program voltage generated in a program operation may be applied to word lines of memory cells in which the program operation is to be performed.
- an erase voltage generated in an erase operation may be applied to well regions of memory cells in which the erase operation is to be performed.
- a read voltage generated in a read operation may be applied to word lines of memory cells in which the read operation is to be performed.
- the control logic 160 may control an overall operation of the nonvolatile memory device 100 based on a control signal provided from an external apparatus. For example, the control logic 160 may control an operation of the nonvolatile memory device 100 such as a read operation, a write operation, an erase operation of the nonvolatile memory device 100 .
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Techniques For Improving Reliability Of Storages (AREA)
- Memory System (AREA)
Abstract
Description
- The present application claims priority under 35 U.S.C. § 119(a) to Korean patent application number 10-2018-0000732, filed on Jan. 3, 2018, which is incorporated herein by reference in its entirety.
- Various embodiments may generally relate to a semiconductor apparatus, and more particularly, to a data storage apparatus, an operating method thereof, and a data processing system including the same.
- In recent years, the paradigm for computer environments changed to ubiquitous computing which may use computer systems every time everywhere. As a result, use of portable electronic apparatuses such as a mobile phone, a digital camera, and a laptop computer has been increasing rapidly. Generally, portable electronic apparatuses use data storage apparatuses that employ memory devices. Data storage apparatuses may be used to store data used in the portable electronic apparatuses.
- Data storage apparatuses using memory devices have no mechanical driving units and exhibit good stability and endurance, fast information access rate, and low power consumption. Such data storage apparatuses may include a universal serial bus (USB) memory device, a memory card having various interfaces, a universal flash storage (UFS) device, a solid-state drive (SSD), and the like.
- Embodiments of the present invention are directed to a data storage apparatus with improved write performance, an operating method thereof, and a data processing system including the same.
- In an embodiment of the present disclosure, a data storage apparatus may include: a nonvolatile memory device including a plurality of dies each die comprising a plurality of memory blocks with the memory blocks being configured as a plurality of super blocks and a plurality of flush buffer blocks; a random-access memory including an open super block manager configured to manage an index of one open super block allocated among the plurality of super blocks and a location into which data is to be written in the allocated one open super block and an open flush buffer block manager configured to manage indexes of a plurality of open flush buffer blocks allocated to the dies and locations into which data is to be written in the allocated open flush buffer blocks; and a processor configured to identify a first die in which a normal write operation is being performed and a second die next to the first die using the open super block manager when a flush write request is received from a host apparatus, select at least one open flush buffer block included in dies other than the first die and the second die using the open flush buffer block manager, and control the nonvolatile memory device to perform a flush write operation on the selected open flush buffer block.
- In an embodiment of the present disclosure, an operating method of a data storage apparatus may include: identifying a first die in which a normal write operation is currently performed and a second die next to the first die when a flush write request is received from a host apparatus; selecting at least one open flush buffer block included in dies other than the first die and the second die; and controlling a nonvolatile memory device to perform a flush write operation on the selected open flush buffer block.
- In an embodiment of the present disclosure, a data processing system may include: a host apparatus configured to transfer a flush write request; and a data storage apparatus including a nonvolatile memory device configured to include a plurality of dies configured as a plurality of super blocks and a plurality of flush buffer blocks and a controller configured to control the nonvolatile memory device. The controller may include: a random-access memory including an open super block manager configured to manage an index of one open super block allocated among the plurality of super blocks and a location into which data is to be written in the allocated open super block and an open flush buffer block manager configured to manage indexes of a plurality of open flush buffer blocks allocated to the plurality of dies and locations into which data is to be written in the allocated open flush buffer blocks; and a processor configured to identify a first die in which a normal write operation is being performed and a second die next to the first die using the open super block manager when the flush write request is received from the host apparatus, select at least one open flush buffer block included in dies other than the first die and the second die using the open flush buffer block manager, and control the nonvolatile memory device to perform a flush write operation on the selected open flush buffer block.
- In an embodiment of the present disclosure, a memory system may include: a memory device including dies each including element memory blocks of super blocks and including one or more flush buffer blocks; and a controller suitable for managing an information of a second die subsequent to a first die in an order of a super block write operation currently being performed to the first die among the dies, and controlling, in response to a flush operation, the memory device to perform a flush operation to one of the flush buffer blocks included in a die other than the first and second dies among the dies.
- In accordance with various embodiments of the invention, as normal write data is stored in units of super blocks and flush write data is stored in units of memory blocks of respective dies, a memory block of a die other than a die to which a normal write data storing operation is interrupted and a die to which the normal write data storing operation is to be resumed may be selected as a flush buffer block.
- Accordingly, the flush write data may be securely stored while securing an interleaving scheme for a normal write operation of the normal write data.
- The above and other aspects, features and advantages of the subject matter of the present disclosure will be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings, in which:
-
FIG. 1 is a block diagram illustrating a configuration example of a data storage apparatus, in accordance with an embodiment of the present disclosure; -
FIG. 2 is a diagram illustrating a configuration example of a nonvolatile memory device ofFIG. 1 ; -
FIG. 3A is a diagram explaining a configuration example of a super block and a write operation sequence, in accordance with an embodiment of the present disclosure; -
FIG. 3B is a diagram illustrating a configuration example of a super block pool, in accordance with an embodiment of the present disclosure; -
FIG. 3C is a diagram illustrating an example of an information table for an allocated super block, in accordance with an embodiment of the present disclosure; -
FIG. 4A is a diagram illustrating a configuration example of a flush buffer block group, in accordance with an embodiment of the present disclosure; -
FIG. 4B is a diagram illustrating a configuration example of a flush buffer block pool, in accordance with an embodiment of the present disclosure; -
FIG. 4C is a diagram illustrating an example of an information table for allocated flush buffer blocks, in accordance with an embodiment of the present disclosure; -
FIG. 5 is a diagram illustrating an example that a flush write request is generated during a normal write operation, in accordance with an embodiment of the present disclosure; -
FIG. 6 is a flowchart illustrating an operating method of a data storage apparatus, in accordance with an embodiment of the present disclosure; -
FIG. 7 is a diagram illustrating an example of a data processing system including a solid-state drive, in accordance with an embodiment of the present disclosure; -
FIG. 8 is a diagram illustrating an example of a controller illustrated inFIG. 7 , in accordance with an embodiment of the present invention disclosure; -
FIG. 9 is a diagram illustrating an example of a data processing system including a data storage apparatus, in accordance with an embodiment of the present disclosure; -
FIG. 10 is a diagram illustrating an example of a data processing system including a data storage apparatus, in accordance with an embodiment of the present disclosure; -
FIG. 11 is a diagram illustrating an example of a network system including a data storage apparatus, in accordance with an embodiment of the present disclosure; and -
FIG. 12 is a block diagram illustrating an example of a nonvolatile memory device included in a data storage apparatus, in accordance with an embodiment of the present disclosure. - Various embodiments of the present invention will be described in greater detail with reference to the accompanying drawings. It is noted that the drawings are simplified schematic illustrations of various embodiments (and intermediate configurations) of the invention. As such, variations from the configurations and shapes of the illustrations as a result, for example, of manufacturing techniques and/or tolerances, are to be expected. Thus, the described embodiments should not be construed as being limited to the particular configurations and shapes illustrated herein however may include deviations in configurations and shapes which do not depart from the spirit and scope of the present invention as defined in the appended claims.
- The present invention is described herein with reference to cross-section and/or plan illustrations of idealized embodiments of the present invention. However, embodiments of the present invention should not be construed as limiting the inventive concept. Although a few embodiments of the present invention will be shown and described, it will be appreciated by those of ordinary skill in the art that other embodiments and changes thereof may be made without departing from the principles, spirit or 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 however not both nor any combinations thereof.
- As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items.
- 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 “includes,” and “including” are used interchangeably in this specification with the open-ended terms “comprises,” and “comprising,” to specify the presence of any stated elements and to not preclude the presence or addition of one or more other non-stated elements.
- 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 to 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, an embodiment of the present disclosure will be described in detail with reference to the accompanying drawings.
-
FIG. 1 is a block diagram illustrating adata storage apparatus 10 in accordance with an embodiment. Thedata storage apparatus 10 in accordance with an embodiment may store data to be accessed by a host apparatus (not shown). The host apparatus may be a device such as a mobile phone, an MP3 player, a laptop computer, a desktop computer, a game player, a television (TV), an in-vehicle infotainment system, and the like. Thedata storage apparatus 10 may also be referred to as a memory system. - The
data storage apparatus 10 may be manufactured as any one among various types of storage apparatuses and may be operatively coupled according to a host interface transfer protocol with a host apparatus (not shown). For example, thedata storage apparatus 10 may be configured as any one of various types of storage apparatuses, such as a solid-state drive (SSD), a multimedia card in the form of an MMC, an eMMC, an RS-MMC, and a micro-MMC, a secure digital card in the form of an SD, a mini-SD, and a 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 interconnection (PCI) card type storage device, a PCI-express (PCI-E) card type storage device, a compact flash (CF) card, a smart media card, a memory stick, and the like. - The
data storage apparatus 10 may be manufactured as any one among various types of packages. For example, thedata storage apparatus 10 may be manufactured as any one of various types of packages, such 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 fabricated package (WFP), and a wafer-level stack package (WSP). - Referring to
FIG. 1 , thedata storage apparatus 10 may include anonvolatile memory device 100 and acontroller 200 operatively coupled via one or more communication channels CH. - The
nonvolatile memory device 100 may be operated as a storage medium of thedata storage apparatus 10. Thenonvolatile memory device 100 may include any one of various types of nonvolatile memory devices, such as a NAND flash memory device, a NOR flash memory device, a ferroelectric random-access memory (FRAM) using a ferroelectric capacitor, a magnetic random-access memory (MRAM) using a tunneling magneto-resistive (TMR) layer, a phase-change random-access memory (PRAM) using a chalcogenide alloy, and a resistive random-access memory (RERAM) using a transition metal compound. - Although the
nonvolatile memory device 100 is illustrated as one block inFIG. 1 , thenonvolatile memory device 100 may include a plurality of dies, each die including a plurality of memory blocks. - The
nonvolatile memory device 100 may include a memory cell array including a plurality of memory cells (not shown) arranged in regions in which a plurality of word lines (not shown) and a plurality of bit lines (not shown) cross each other. The memory cell array may include a plurality of memory blocks and each of the plurality of memory blocks may include a plurality of pages. - For example, each of the memory cells in the memory cell array may be at least one among a single level cell (SLC) in which a single bit data (for example, 1-bit data) is stored, a multilevel cell (MLC) in which 2-bit data is stored, a triple level cell (TLC) in which 3-bit data is stored, and a quad level cell QLC in which 4-bit data is stored. The memory cell array may include at least one or more cells among the SLC, the MLC, the TLC, and the QLC. The memory cell array may include memory cells arranged in a two-dimensional (2D) horizontal structure or memory cells having a 3D vertical structure.
- The
controller 200 may include ahost interface 210, aprocessor 220, a random-access memory (RAM) 230, and amemory interface 240. - The
host interface 210 may perform interfacing between a host apparatus (not shown) and thedata storage device 10. For example, thehost interface 210 may communicate with the host apparatus through any one among standard transfer protocols such as a USB protocol, a UFS protocol, an MMC protocol, a parallel advanced technology attachment (PATA) protocol, a serial advanced technology attachment (SATA) protocol, a small computer system interface (SCSI) protocol, a serial attached SCSI (SAS) protocol, a PCI protocol, and a PCI-E protocol. - The
processor 220 may be configured as a micro control unit (MCU) or a central processing unit (CPU). Theprocessor 220 may process a request (for example, read request and write request) transmitted from the host apparatus. Theprocessor 220 may drive a code-type instruction or algorithm (e.g., software) which is loaded into theRAM 230 for controlling internal function blocks and/or thenonvolatile memory device 100. - The
RAM 230 may be configured as a random-access memory, such as a dynamic RAM (DRAM) or a static RAM (SRAM). TheRAM 230 may store software driven through theprocessor 220. TheRAM 230 may store data required for the driving of the software. For example, theRAM 230 may be operated as a working memory of theprocessor 220. - When the
nonvolatile memory device 100 is configured as a flash memory device, theprocessor 220 may control an internal operation of thenonvolatile memory device 100 and drive software known as a flash translation layer (FTL) to provide device compatibility to a host apparatus. Hence, through the driving of the flash translation layer (FTL), the host apparatus may use thedata storage apparatus 10 by recognizing thedata storage apparatus 10 as a general data storage apparatus such as a hard disc. - The flash translation layer (FTL) may be loaded into the
RAM 230 and may include modules configured to perform various functions and metadata required for the driving of the modules. For example, the flash translation layer (FTL) may include a ware-leveling module, a bad block management module, a garbage collection module, an interleaving module, a sudden power-off management module, an address map, and the like, however, the configuration of the flash translation layer (FTL) is not limited thereto. - The
RAM 230 may temporarily store data which is to be transmitted to thenonvolatile memory device 100 from a host apparatus or data which is read from thenonvolatile memory device 100 and is to be transmitted to the host apparatus. For example, theRAM 230 may be operated as a buffer memory of theprocessor 220. - Referring to
FIG. 1 , theRAM 230 may include a super block pool SBP, an open super block manager OSBM, a flush buffer block pool FBP, and an open flush buffer block manager OFBM. - The super block pool SBP may be configured to include information such as allocation/free and an erase/write (E/W) count for each of super blocks included in the
nonvolatile memory device 100. The super block and the super block pool SBP will be described later in detail with reference to the related drawings. - The open super block manager OSBM may be configured to manage information such as an index of an open super block and a location into which data is to be written in the open super block allocated among a plurality of super blocks included in the
nonvolatile memory device 100. The location into which data is to be written may represent a page number (for example, page address) and a sector number in the allocated open super block. Whenever an open super block is newly allocated, the open super block manager OSBM may update the index of the open super block due to the newly allocated open super block. Whenever the write operation for the open super block is completed, the open super block manager OSBM may update the location into which data is to be written, for example, the page number and the sector number in the open super block. - The flush buffer block pool FBP may be configured to include information such as allocation/free and an E/W count for each of flush buffer blocks included in the
nonvolatile memory device 100. The flush buffer block and the flush buffer block pool FBP will be described later in detail with reference to the related drawings. - The open flush buffer block manager OFBM may be configured to manage information such as indexes of open flush buffer blocks and locations into which data is to be written in the open flush buffer blocks allocated among a plurality of plush buffer blocks included in the
nonvolatile memory device 100. A single memory block may be allocated as the flush buffer block for each die (see D1 to Di ofFIG. 2 ). Accordingly, the open flush buffer block manager OFBM may manage information for the same number of open flush buffer blocks as the number (for example, the number of ‘i’) of dies. The location into which data is to be written may include a page number (for example, page address) and a sector number in the allocated open flush buffer blocks. - Whenever an open flush buffer block for each die D1 to Di is newly allocated, the open flush buffer block manager OFBM may update the index of the open flush buffer block corresponding to each die D1 to Di due to the newly allocated open flush buffer block. Whenever the write operation for each open flush buffer block is completed, the open flush buffer block manager OFBM may update the location into which data is to be written for each open flush buffer block, for example, the page number and the sector number in the open flush buffer block.
-
FIG. 2 is a diagram illustrating a configuration example of thenonvolatile memory device 100 ofFIG. 1 . - The
nonvolatile memory device 100 may include the plurality of dies D1 to Di. Each of the plurality of dies D1 to Di may include a plurality of memory blocks B1 to Bk. Although not specifically shown inFIG. 2 , each of the dies D1 to Di may include a plurality of planes including a plurality of memory blocks. For simplification of the drawings and convenience of the description, in the example ofFIG. 2 , each of the dies D1 to Di includes one plane. - Referring to
FIG. 2 , the same memory blocks in the dies D1 to Di may be grouped into one memory block group. The one memory block group that the same memory blocks in the dies D1 to Di are grouped may also be referred to as a super block. The first memory blocks B1 in the dies D1 to Di may be grouped into and used as a first super block SB1. Thecontroller 200 may operate the i first memory blocks B1 included in the first super block SB1 in parallel. For example, thecontroller 200 may control thenonvolatile memory device 100 to simultaneously perform an operation such as a read or write operation on the i first memory blocks B1 included in the first super block SB1 simultaneously. - The number of super blocks SB included in the
nonvolatile memory device 100 may be smaller than the number of memory blocks B1 to Bk included in each of the dies D1 to Di. For example, when each die D1 to D1 includes k memory blocks B1 to Bk as illustrated inFIG. 2 , the first memory blocks B1 to j-th memory blocks Bj of the dies D1 to Di may be grouped into and used as the first super block SB1 to a j-th super block SBj. Here, k and j may be an integer of 1 or more and j may be smaller than k. Other memory blocks, for example, j+1-th memory blocks Bj+1 to k-th memory blocks Bk in the dies D1 to Di other than the memory blocks B1 to Bk included in the super blocks SB1 to SBj may not be grouped into super blocks and may be used as unit memory blocks. - A portion of or all the memory blocks among the j+1-th to k-th memory blocks Bj+1 to Bk may be designated as flush buffer blocks FB. The flush buffer blocks FB may be a space configured to temporarily store data stored in a data buffer (not shown) when the flush request is received from a host apparatus or sudden power-off occurs.
- Although not shown in
FIG. 1 , thecontroller 200 may include a data buffer configured to temporarily store write data received from a host apparatus. Whenever the write request and the write data are received from the host apparatus in a normal state, theprocessor 220 may not instantly store the write data in thenonvolatile memory device 100 but may temporarily buffer the write data in the data buffer until the buffered write data has a preset size. When a size of the write data stored in the data buffer is larger than a preset size, theprocessor 220 may control thenonvolatile memory device 100 to store the write data stored in the data buffer in an allocated open super block. Here, the preset size may refer to a minimum size sufficient to perform a write operation. When the size of the write data stored in the data buffer reaches the minimum size sufficient to perform the write operation, theprocessor 220 may control thenonvolatile memory device 100 to store the corresponding write data in an open super block. - When the flush request is received from a host apparatus or a sudden power-off occurs when the size of the data buffered in the data buffer is equal to or smaller than the preset size, the
processor 220 may select one flush buffer block among a plurality of designated flush buffer blocks and control thenonvolatile memory device 100 to store the write data which are stored in the data buffer in the selected flush buffer block. - The data stored in the flush buffer block may be stored in the data buffer again through control of the
processor 220 and then stored in an allocated open super block along with the write data transferred from the host apparatus when the size of the data in the data buffer becomes larger than the preset size. -
FIG. 3A is a diagram explaining a configuration example of a super block and a write operation sequence in accordance with an embodiment of the present disclosure,FIG. 3B is a diagram illustrating a configuration example of the super block pool SBP in accordance with an embodiment of the present disclosure, andFIG. 3C is a diagram illustrating a configuration example of an information table managed by the open super block manager OSBM in accordance with an embodiment of the present disclosure. - As illustrated in
FIG. 3A , one super block SB may include the memory blocks (for example, first memory blocks B1) selected from the dies D1 to Di, respectively. Each of the plurality of first memory blocks B1 may include a plurality of pages P1 to Pn and each of the pages P1 to Pn may include a plurality of sectors S1 to S4, S5 to S8, and Sm-3 to Sm. By way of example and not limitation, it is illustrated inFIG. 3A that four sectors are included in one page, however, the number of sectors included in one page is not limited thereto. - The sectors S1 to Sm may be storage units in the
nonvolatile memory device 100 for the write data received from a host apparatus. For example, when one sector is 4 Kbyte and the write data received from the host apparatus is 40 Kbyte, the write data may be written in ten sectors. - The write operation for one super block SB may be performed based on a sequence represented with {circle around (1)} to {circle around (n)} indicated by dotted arrows in
FIG. 3A . When the first pages P1 to the n-th pages Pn of the super block SB refer to a first super page to an n-th super page of the super block SB, the write operation for the super block SB may start from the first super page P1 and may be terminated in the n-th super page Pn. In each of the super pages P1 to Pn, the write operation may start from the first sector S1 and may be terminated to the m-th sector Sm. The write operation for a single super block SB may be sequentially performed in order of dies, pages, and sectors in the single super block SB. - The
processor 220 may allocate a super block SB, for example, an open super block to store normal write data. The normal write data may refer to write data having a size sufficient to perform a write operation. Theprocessor 220 may allocate a free super block having the smallest E/W count among a plurality of free super blocks as the open super block with reference to the supper block pool SBP illustrated inFIG. 3B . The super block pool SBP may be configured to include information such as allocation/free and the E/W counts for all the super blocks (for example, first to j-th super blocks ofFIG. 2 ) included in thenonvolatile memory device 100.FIG. 3B illustrates an example that the first super block SB1 is allocated as the open super block. - When an open super block is allocated, the
processor 220 may manage an index (for example, ‘1’) of the allocated open super block and a page number (for example, ‘1’) and a sector number (for example, ‘1’) into which data is to be written in the allocated open super block using the open super block manager OSBM as illustrated inFIG. 3C . As illustrated inFIG. 3C , the state that both the page number and the sector are ‘1’ may refer to an initial state that the write data is not stored. For example, the page number and the sector number are respectively ‘2’ and ‘7’ in the table managed by the open super block manager OSBM may represent that the location in which the normal write data is to be stored is the seventh sector S7 of the second page P2 in the second die D2 as illustrated in FIG. 3A. -
FIG. 4A is a diagram illustrating a configuration example of a flush buffer block group FBG in accordance with an embodiment of the present disclosure,FIG. 4B is a diagram illustrating a configuration example of the flush buffer block pool FBP in accordance with an embodiment of the present disclosure, andFIG. 4C is a diagram illustrating a configuration example of an information table managed by the open flush buffer block manager OFBM in accordance with an embodiment of the present disclosure. - As illustrated in
FIG. 4A , the flush buffer block group FBG may include a plurality of memory blocks. It has been illustrated inFIG. 4A that the flush buffer block group FBG includes all memory blocks other than the memory blocks included in the super blocks ofFIG. 2 , however this is merely exemplary and this is not limited thereto. The j+1-th memory blocks Bj+1 to the k-th memory blocks Bk of the dies D1 to Di included in the flush buffer block group FBG may be separately allocated and managed. Each memory block of the flush buffer block group FBG may include n pages, each page including four sectors like the memory blocks which are included in the super block. - The
processor 220 may allocate the flush buffer block FB, for example, open flush buffer blocks to store flush write data. As described above, the flush write data may refer to write data having a preset size or less stored in the data buffer (not shown) when a flush request is received from a host apparatus or a sudden power-off occurs. Theprocessor 220 may select free flush buffer blocks having the smallest E/W count in the die D1 to Di one by one with reference to the flush buffer block pool FBP illustrated inFIG. 4B . Theprocessor 220 may allocate the selected free flush buffer blocks as a plurality of open flush buffer blocks. - For clarity, the flush buffer blocks included in the dies D1 to Di are indicated as first to h-th flush buffer blocks FB1 to FBh in
FIG. 4B . The flush buffer block pool FBP may be configured to include information such as allocation/free and the E/W count for each of the first to the h-th flush buffer blocks FB1 to FBh in the dies D1 to Di. The example that the first flush buffer block FB1 of the first die D1, the second flush buffer block FB2 of the second die D2, the first flush buffer block FB1 of the i-th die Di, and the like are allocated as the open flush buffer blocks is illustrated inFIG. 4B . - When open flush buffer blocks are allocated, the
processor 220 may manage the indexes (for example, ‘1’, ‘2’, ‘1’) of the allocated open flush buffer blocks and page numbers (for example, ‘1’, ‘1’) and the sector numbers (for example, ‘1’, ‘1’, ‘1’), into which data is to be written in the open flush buffer blocks allocated in the dies D1 to Di using the open flush buffer block manager OFBM as illustrated inFIG. 4C . As illustrated inFIG. 4C , the state that all the page numbers and the sector numbers are ‘1’ may refer to an initial state that the flush write data is not stored. - In the open flush buffer block manager OFBM, the
indexes 1 to i of the dies D1 to Di may be fixed and whenever the open flush buffer blocks in the dies are newly allocated, the indexes of the corresponding open flush buffer blocks may be updated. Whenever the flush write data are stored in the open flush buffer blocks, the page numbers and sector numbers corresponding to the open flush buffer blocks may be updated. - The point of time at which the flush write data is stored into the allocated open flush buffer blocks may be randomized. For example, when a flush request is received or a sudden power-off occurs during an operation of storing the normal write data in the super block SB, the operation of storing the normal write data is immediately interrupted and the flush write data is stored. When the die to which the normal write data storing operation is interrupted is the same as the die that the flush write data is stored, a program time interval tPROG for the normal write data and a program time interval tPROG for the flush write data in the same die may overlap each other and thus the data may be corrupted. Accordingly, a die other than the die for which the normal write data storing operation is interrupted and the die for which the normal write data storing operation is to be resumed may be selected as a die that the flush write data is to be stored.
- In accordance with the embodiment, as the normal write data is stored in units of the super blocks SB and the flush write data is stored in units of memory blocks of the respective dies, a memory block of a die other than the die to which the normal write data storing operation is interrupted and the die to which the normal write data storing operation is to be resumed may be selected as the flush buffer block. Accordingly, the flush write data may be securely stored while securing an interleaving scheme for a normal write operation of the normal write data.
-
FIG. 5 is a diagram illustrating an example that a flush write operation is performed during a normal write operation in accordance with an embodiment of the present disclosure. - Referring to
FIG. 5 , when a flush write request is received from a host apparatus at a time t2 after the normal write operation of storing the normal write data starts at a time t1, theprocessor 220 may identify a die that the normal write operation is currently performed and a die that the normal write operation is to be subsequently performed using the open super block manager OSBM. For example,FIG. 5 illustrates that the die currently performing the normal write operation is the fourth die D4 and that the normal write operation is to be subsequently performed in the fifth die D5. - The
processor 220 may select open flush buffer blocks included in dies other than the die (e.g., a fourth die D4) to which the normal write operation is currently performed and the die (e.g., a fifth die D5) to which the normal write operation is to be subsequently performed using the open flush buffer block manager OFBM. In the described example, the open flush buffer blocks FB1 and FB2 of the first die D1 and the second die D2 are selected as illustrated inFIG. 5 . - The
processor 220 may control thenonvolatile memory device 100 to perform the flush write operation on the selected open flush buffer blocks FB1 and FB2 of the first die D1 and the second die D2. Theprocessor 220 may control thenonvolatile memory device 100 to resume the normal write operation to the die (i.e., the fifth die D5) to which the normal write operation is supposed to be subsequently performed before the flush write operation is completed. - The
memory interface 240 may control thenonvolatile memory device 100 according to control of theprocessor 220. Thememory interface 240 may also be referred to as a memory controller. Thememory interface 240 may provide control signals to thenonvolatile memory device 100. The control signals may include a command, an address, and the like for controlling thenonvolatile memory device 100. Thememory interface 240 may provide data to thenonvolatile memory device 100 or receive data from thenonvolatile memory device 100. Thememory interface 240 may be coupled to thenonvolatile memory device 100 through a channel CH. The channel may include one or more signal lines. -
FIG. 6 is a flowchart of an operating method of a data storage apparatus in accordance with an embodiment of the present disclosure. The operating method of a data storage apparatus in accordance with an embodiment will be described with reference toFIG. 6 withFIGS. 1 to 5 . - In operation S610, a processor (see 220 of
FIG. 1 ) of the controller (see 200 ofFIG. 1 ) may determine whether a flush write request is received from a host apparatus. When the flush write request is received, the processor may proceed to operation S620. - In operation S620, the
processor 220 may identify a die (for example, fourth die D4 ofFIG. 5 ) that a normal write operation is currently performed and a die (for example, fifth die D5 ofFIG. 5 ) that the normal write operation is to be subsequently performed using the open super block manager OSBM. - In operation S630, the
processor 220 may select open flush buffer blocks (see FB1 and FB2 ofFIG. 5 ) included in dies (for example, first and second dies D1 and D2 ofFIG. 5 ) other than the fourth die D4, to which the normal write data storing operation is interrupted, and the fifth die D5, to which the normal write data storing operation is to be resumed, using the open flush buffer block manager OFBM. - In operation S640, the
processor 220 may control thenonvolatile memory device 100 to perform the flush write operation on the selected open flush buffer blocks FB1 and FB2. -
FIG. 7 is a diagram illustrating an example of a data processing system including a solid-state drive (SSD) in accordance with an embodiment. Referring toFIG. 7 , adata processing system 2000 may include ahost apparatus 2100 and anSSD 2200. - The
SSD 2200 may include acontroller 2210, abuffer memory device 2220,nonvolatile memory devices 2231 to 223 n, apower supply 2240, asignal connector 2250, and apower connector 2260. - The
controller 2210 may control an overall operation of theSSD 2220. - The
buffer memory device 2220 may temporarily store data to be stored in thenonvolatile memory devices 2231 to 223 n. Thebuffer memory device 2220 may temporarily store data read from thenonvolatile memory devices 2231 to 223 n. The data temporarily stored in thebuffer memory device 2220 may be transmitted to thehost apparatus 2100 or thenonvolatile memory devices 2231 to 223 n in accordance with control of thecontroller 2210. - The
nonvolatile memory devices 2231 to 223 n may be used as a storage medium of theSSD 2200. Thenonvolatile memory devices 2231 to 223 n may be coupled to thecontroller 2210 through a plurality of channels CH1 to CHn. One or more nonvolatile memory devices may be coupled to one channel. The nonvolatile memory devices coupled to the one channel may be coupled to the same signal bus and the same data bus. - The
power supply 2240 may provide power PWR input through thepower connector 2260 to the inside of theSSD 2200. Thepower supply 2240 may include anauxiliary power supply 2241. Theauxiliary power supply 2241 may supply the power so that theSSD 2200 is normally terminated even when sudden power-off occurs. Theauxiliary power supply 2241 may include large capacity capacitors capable of charging the power PWR. - The
controller 2210 may exchange a signal SGL with thehost apparatus 2100 through thesignal connector 2250. The signal SGL may include a command, an address, data, and the like. Thesignal connector 2250 may be configured of various types of connectors according to an interfacing method between thehost apparatus 2100 and theSSD 2200. -
FIG. 8 is a diagram illustrating an example of thecontroller 2210 ofFIG. 7 . Referring toFIG. 8 , thecontroller 2210 may include ahost interface unit 2211, acontrol unit 2212, a random-access memory (RAM) 2213, an error correction code (ECC)unit 2214, and amemory interface unit 2215. - The
host interface unit 2211 may perform interfacing between thehost apparatus 2100 and theSSD 2200 according to a protocol of thehost apparatus 2100. For example, thehost interface unit 2211 may communicate with thehost apparatus 2100 through any one among a secure digital protocol, a universal serial bus (USB) protocol, a multimedia card (MMC) protocol, an embedded MMC (eMMC) protocol, a personal computer memory card international association (PCMCIA) protocol, a parallel advanced technology attachment (PATA) protocol, a serial advanced technology attachment (SATA) protocol, a small computer system interface (SCSI) protocol, a serial attached SCSI (SAS) protocol, a peripheral component interconnection (PCI) protocol, a PCI Express (PCI-E) protocol, and a universal flash storage (UFS) protocol. Thehost interface unit 2211 may perform a disc emulation function that thehost apparatus 2100 recognizes theSSD 2200 as a general-purpose data storage apparatus, for example, a hard disc drive HDD. - The
control unit 2212 may analyze and process the signal SGL input from thehost apparatus 2100. Thecontrol unit 2212 may control operations of internal functional blocks according to firmware and/or software for driving theSDD 2200. TheRAM 2213 may be operated as a working memory for driving the firmware or software. - The
ECC unit 2214 may generate parity data for the data to be transferred to thenonvolatile memory devices 2231 to 223 n. The generated parity data may be stored in thenonvolatile memory devices 2231 to 223 n together with the data. TheECC unit 2214 may detect errors for data read from thenonvolatile memory devices 2231 to 223 n based on the parity data. When detected errors are within a correctable range, theECC unit 2214 may correct the detected errors. - The
memory interface unit 2215 may provide a control signal such as a command and an address to thenonvolatile memory devices 2231 to 223 n according to control of thecontrol unit 2212. Thememory interface unit 2215 may exchange data with thenonvolatile memory devices 2231 to 223 n according to control of thecontrol unit 2212. For example, thememory interface unit 2215 may provide data stored in thebuffer memory device 2220 to thenonvolatile memory devices 2231 to 223 n or provide data read from thenonvolatile memory devices 2231 to 223 n to thebuffer memory device 2220. - The random-
access memory 2213 may be configured as theRAM 230 ofFIG. 1 . -
FIG. 9 is a diagram illustrating an example of a data processing system including a data storage apparatus in accordance with an embodiment. Referring toFIG. 9 , adata processing system 3000 may include ahost apparatus 3100 and adata storage apparatus 3200. - The
host apparatus 3100 may be configured in a board form such as a printed circuit board (PCB). Although not shown inFIG. 9 , thehost apparatus 3100 may include internal functional blocks configured to perform functions of thehost apparatus 3100. - The
host apparatus 3100 may include aconnection terminal 3110 such as a socket, a slot, or a connector. Thedata storage apparatus 3200 may be mounted on theconnection terminal 3110. - The
data storage apparatus 3200 may be configured in a board form such as a PCB. Thedata storage apparatus 3200 may refer to a memory module or a memory card. Thedata storage apparatus 3200 may include acontroller 3210, abuffer memory device 3220,nonvolatile memory devices 3231 to 3232, a power management integrated circuit (PMIC) 3240, and aconnection terminal 3250. - The
controller 210 may control an overall operation of thedata storage apparatus 3200. Thecontroller 3210 may be configured to have the same configuration as thecontroller 2210 illustrated inFIG. 8 . - The
buffer memory device 3220 may temporarily store data to be stored in thenonvolatile memory devices buffer memory device 3220 may temporarily store data read from thenonvolatile memory devices buffer memory device 3220 may be transmitted to thehost apparatus 3100 or thenonvolatile memory devices controller 3210. - The
nonvolatile memory devices data storage apparatus 3200. - The
PMIC 3240 may provide power input through theconnection terminal 3250 to the inside of thedata storage apparatus 3200. ThePMIC 3240 may manage the power of thedata storage apparatus 3200 according to control of thecontroller 3210. - The
connection terminal 3250 may be coupled to theconnection terminal 3110 of thehost apparatus 3100. A signal such as a command, an address, and data and power may be transmitted between thehost apparatus 3100 and thedata storage apparatus 3200 through theconnection terminal 3250. Theconnection terminal 3250 may be configured in various forms according to an interfacing method between thehost apparatus 3100 and thedata storage apparatus 3200. Theconnection terminal 3250 may be arranged in any one side of thedata storage apparatus 3200. -
FIG. 10 is a diagram illustrating an example of a data processing system including a data storage apparatus in accordance with an embodiment. Referring toFIG. 10 , adata processing system 4000 may include ahost apparatus 4100 and adata storage apparatus 4200. - The
host apparatus 4100 may be configured in a board form such as a PCB. Although not shown inFIG. 10 , thehost apparatus 4100 may include internal functional blocks configured to perform functions of thehost apparatus 4100. - The
data storage apparatus 4200 may be configured in a surface mounting packaging form. Thedata storage apparatus 4200 may be mounted on thehost apparatus 4100 throughsolder balls 4250. Thedata storage apparatus 4200 may include acontroller 4210, abuffer memory device 4220, and anonvolatile memory device 4230. - The
controller 4210 may control an overall operation of thedata storage apparatus 4200. Thecontroller 4210 may be configured to have the same configuration as thecontroller 2210 illustrated inFIG. 8 . - The
buffer memory device 4220 may temporarily store data to be stored in thenonvolatile memory device 4230. Thebuffer memory device 4220 may temporarily store data read from thenonvolatile memory device 4230. The data temporarily stored in thebuffer memory device 4220 may be transmitted to thehost apparatus 4100 or thenonvolatile memory device 4230 through control of thecontroller 4210. - The
nonvolatile memory device 4230 may be used as a storage medium of thedata storage apparatus 4200. -
FIG. 11 is a diagram illustrating an example of anetwork system 5000 including a data storage apparatus in accordance with an embodiment. Referring toFIG. 11 , thenetwork system 5000 may include aserver system 5300 and a plurality ofclient systems 5410 to 5430 which are coupled through anetwork 5500. - The
server system 5300 may serve data in response to requests of the plurality ofclient systems 5410 to 5430. For example, theserver system 5300 may store data provided from the plurality ofclient systems 5410 to 5430. In another example, theserver system 5300 may provide data to the plurality ofclient systems 5410 to 5430. - The
server system 5300 may include ahost apparatus 5100 and adata storage apparatus 5200. Thedata storage apparatus 5200 may be configured of thedata storage apparatus 10 ofFIG. 1 , thedata storage apparatus 2200 ofFIG. 7 , thedata storage apparatus 3200 ofFIG. 9 , or thedata storage apparatus 4200 ofFIG. 10 . -
FIG. 12 is a block diagram illustrating an example of a nonvolatile memory device included in a data storage apparatus in accordance with an embodiment. Referring toFIG. 12 , anonvolatile memory device 100 may include amemory cell array 110, arow decoder 120, acolumn decoder 140, a data read/write block 130, avoltage generator 150, and acontrol logic 160. - The
memory cell array 110 may include memory cells MC arranged in regions in which word lines WL1 to WLm and bit lines BL1 to BLn cross to each other. - The
row decoder 120 may be coupled to thememory cell array 110 through the word lines WL1 to WLm. Therow decoder 120 may operate through control of thecontrol logic 160. Therow decoder 120 may decode an address provided from an external apparatus (not shown). Therow decoder 120 may select and drive the word lines WL1 to WLm based on a decoding result. For example, therow decoder 120 may provide a word line voltage provided from thevoltage generator 150 to the word lines WL1 to WLm. - The data read/
write block 130 may be coupled to thememory cell array 110 through the bit lines BL1 to BLn. The data read/write block 130 may include read/write circuits RW1 to RWn corresponding to the bit lines BL1 to BLn. The data read/write block 130 may operate according to control of thecontrol logic 160. The data read/write block 130 may operate as a write driver or a sense amplifier according to an operation mode. For example, the data read/write block 130 may operate as the write driver configured to store data provided from an external apparatus in thememory cell array 110 in a write operation. In another example, the data read/write block 130 may operate as the sense amplifier configured to read data from thememory cell array 110 in a read operation. - The
column decoder 140 may operate through control of thecontrol logic 160. Thecolumn decoder 140 may decode an address provided from an external apparatus (not shown). Thecolumn decoder 140 may couple the read/write circuits RW1 to RWn of the data read/write block 130 corresponding to the bit lines BL1 to BLn and data input/output (I/O) lines (or data I/O buffers) based on a decoding result. - The
voltage generator 150 may generate voltages used for an internal operation of thenonvolatile memory device 100. The voltages generated through thevoltage generator 150 may be applied to the memory cells of thememory cell array 110. For example, a program voltage generated in a program operation may be applied to word lines of memory cells in which the program operation is to be performed. In another example, an erase voltage generated in an erase operation may be applied to well regions of memory cells in which the erase operation is to be performed. In another example, a read voltage generated in a read operation may be applied to word lines of memory cells in which the read operation is to be performed. - The
control logic 160 may control an overall operation of thenonvolatile memory device 100 based on a control signal provided from an external apparatus. For example, thecontrol logic 160 may control an operation of thenonvolatile memory device 100 such as a read operation, a write operation, an erase operation of thenonvolatile memory device 100. - The above described embodiments of the present invention are intended to illustrate and not to limit the present invention. Various alternatives and equivalents are possible. The invention is not limited by the embodiments described herein. Nor is the invention limited to any specific type of semiconductor device. Other additions, subtractions, or modifications are obvious in view of the present disclosure and are intended to fall within the scope of the appended claims.
Claims (15)
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR10-2018-0000732 | 2018-01-03 | ||
KR1020180000732A KR20190083148A (en) | 2018-01-03 | 2018-01-03 | Data storage device and operating method thereof and data process system containing the same |
Publications (2)
Publication Number | Publication Date |
---|---|
US20190205038A1 true US20190205038A1 (en) | 2019-07-04 |
US11150811B2 US11150811B2 (en) | 2021-10-19 |
Family
ID=67057641
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/052,234 Active 2039-05-09 US11150811B2 (en) | 2018-01-03 | 2018-08-01 | Data storage apparatus performing flush write operation, operating method thereof, and data processing system including the same |
Country Status (3)
Country | Link |
---|---|
US (1) | US11150811B2 (en) |
KR (1) | KR20190083148A (en) |
CN (1) | CN109992202B (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10852971B2 (en) * | 2018-02-14 | 2020-12-01 | SK Hynix Inc. | Memory controller and memory system having the same |
US20220113900A1 (en) * | 2020-10-13 | 2022-04-14 | SK Hynix Inc. | Storage device and method of operating the same |
US11640254B2 (en) | 2021-08-25 | 2023-05-02 | Western Digital Technologies, Inc. | Controlled imbalance in super block allocation in ZNS SSD |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11287989B2 (en) * | 2020-03-24 | 2022-03-29 | Western Digital Technologies, Inc. | Dynamic allocation of sub blocks |
KR20220058224A (en) | 2020-10-30 | 2022-05-09 | 에스케이하이닉스 주식회사 | Memory system and operating method of memory controller included therein |
KR20220107392A (en) | 2021-01-25 | 2022-08-02 | 에스케이하이닉스 주식회사 | Data Storage Apparatus and Operation Method Thereof |
CN116303118B (en) * | 2023-05-18 | 2023-09-05 | 合肥康芯威存储技术有限公司 | Storage device and control method thereof |
Family Cites Families (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN100440171C (en) * | 2004-02-24 | 2008-12-03 | 中国科学院声学研究所 | File system in device of recording and playing back sounds and images under embedded type environment |
KR100951099B1 (en) | 2008-07-24 | 2010-04-07 | 인하대학교 산학협력단 | Method for storing and managing of data, and record media recoded program for implement thereof |
US8239614B2 (en) * | 2009-03-04 | 2012-08-07 | Micron Technology, Inc. | Memory super block allocation |
US8769190B1 (en) * | 2010-09-15 | 2014-07-01 | Western Digital Technologies, Inc. | System and method for reducing contentions in solid-state memory access |
US9361044B2 (en) * | 2011-03-28 | 2016-06-07 | Western Digital Technologies, Inc. | Power-safe data management system |
JP2013061799A (en) * | 2011-09-13 | 2013-04-04 | Toshiba Corp | Memory device, control method for memory device and controller |
US8819380B2 (en) * | 2012-03-21 | 2014-08-26 | International Business Machines Corporation | Consideration of adjacent track interference and wide area adjacent track erasure during block allocation |
US8862810B2 (en) * | 2012-09-27 | 2014-10-14 | Arkologic Limited | Solid state device write operation management system |
US9478292B2 (en) * | 2013-10-27 | 2016-10-25 | Sandisk Technologies Llc | Read operation for a non-volatile memory |
US9213634B2 (en) * | 2013-11-22 | 2015-12-15 | Apple Inc. | Efficient reuse of segments in nonoverwrite storage systems |
US9329799B2 (en) * | 2014-03-04 | 2016-05-03 | Netapp, Inc. | Background checking for lost writes and data corruption |
KR102295223B1 (en) | 2015-01-13 | 2021-09-01 | 삼성전자주식회사 | Storage device and user device including speed mode manager |
US10228862B2 (en) * | 2017-03-15 | 2019-03-12 | Western Digital Technologies, Inc. | Capacity-aware wear leveling in solid-state storage devices |
US20190188156A1 (en) * | 2017-12-19 | 2019-06-20 | Seagate Technology Llc | Stripe aligned cache flush |
-
2018
- 2018-01-03 KR KR1020180000732A patent/KR20190083148A/en unknown
- 2018-08-01 US US16/052,234 patent/US11150811B2/en active Active
- 2018-09-27 CN CN201811132249.2A patent/CN109992202B/en active Active
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10852971B2 (en) * | 2018-02-14 | 2020-12-01 | SK Hynix Inc. | Memory controller and memory system having the same |
US20220113900A1 (en) * | 2020-10-13 | 2022-04-14 | SK Hynix Inc. | Storage device and method of operating the same |
US11693589B2 (en) * | 2020-10-13 | 2023-07-04 | SK Hynix Inc. | Storage device using cache buffer and method of operating the same |
US11640254B2 (en) | 2021-08-25 | 2023-05-02 | Western Digital Technologies, Inc. | Controlled imbalance in super block allocation in ZNS SSD |
Also Published As
Publication number | Publication date |
---|---|
KR20190083148A (en) | 2019-07-11 |
US11150811B2 (en) | 2021-10-19 |
CN109992202A (en) | 2019-07-09 |
CN109992202B (en) | 2022-06-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10664409B2 (en) | Data storage apparatus utilizing sequential map entry for responding to read request and operating method thereof | |
US11150811B2 (en) | Data storage apparatus performing flush write operation, operating method thereof, and data processing system including the same | |
US10838653B2 (en) | Electronic device and operating method thereof | |
US11275678B2 (en) | Data storage device with spare blocks for replacing bad block in super block and operating method thereof | |
US20200241956A1 (en) | Memory system and operating method thereof | |
US10922000B2 (en) | Controller, operating method thereof, and memory system including the same | |
US20200218653A1 (en) | Controller, data storage device, and operating method thereof | |
US11030099B2 (en) | Data storage apparatus and operating method thereof | |
US10360984B2 (en) | Data storage device and method of operating the same | |
US20190205059A1 (en) | Data storage apparatus and operating method thereof | |
US20200105351A1 (en) | Memory system and operating method thereof | |
US20180239557A1 (en) | Nonvolatile memory device, data storage device including the same, and operating method of data storage device | |
US10754768B2 (en) | Memory system using descriptor lookup tables to access setting information for a non-volatile memory, and an operating method thereof | |
US20210397364A1 (en) | Storage device and operating method thereof | |
US11379363B2 (en) | Controller, memory system, and operating methods thereof | |
US20210064542A1 (en) | Memory controller, storage device including memory controller, and operating method of memory controller | |
US10817192B2 (en) | Data storage apparatus selecting memory block group based on interleaving index and operating method thereof | |
US11232023B2 (en) | Controller and memory system including the same | |
US11157401B2 (en) | Data storage device and operating method thereof performing a block scan operation for checking for valid page counts | |
US11194512B2 (en) | Data storage device which selectively performs a cache read or a normal read operation depending on work load and operating method thereof | |
US20200409848A1 (en) | Controller, memory system, and operating methods thereof | |
US10515693B1 (en) | Data storage apparatus and operating method thereof | |
US10657046B2 (en) | Data storage device and operating method thereof | |
US20200250082A1 (en) | Controller, memory system, and operating method thereof | |
US9966148B1 (en) | Data storage device and operating method thereof |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: SK HYNIX INC., KOREA, REPUBLIC OF Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:LEE, JOO YOUNG;REEL/FRAME:046709/0932 Effective date: 20180726 |
|
FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE AFTER FINAL ACTION FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |