Memory system, operating method thereof and data processing system

The memory system addresses redundant data management inefficiencies by using a controller to manage duplicate physical addresses, reducing duplicate data storage and improving memory management efficiency.

KR103047693B1Active Publication Date: 2026-11-11SK HYNIX INC
View PDF 11 Cites 0 Cited by

Patent Information

Application Number
KR1020210155867
Authority / Receiving Office
KR · KR
Patent Type
Patents
Current Assignee / Owner
Filing Date
2021-11-12
Publication Date
2026-11-11
Estimated Expiration
2041-11-12

AI Technical Summary

Technical Problem

Existing memory systems face inefficiencies in managing redundant data, leading to unnecessary storage of duplicate data and inefficient management operations.

Method used

A memory system with a non-volatile memory device and a controller that determines duplicate physical addresses based on logical addresses and duplicate counts, selectively mapping logical addresses to physical addresses to manage redundant data efficiently.

Benefits of technology

The system effectively reduces redundant data storage, optimizing memory management operations such as garbage collection by minimizing duplicate data, thereby enhancing operational efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 112021130873324-PAT00001_ABST
    Figure 112021130873324-PAT00001_ABST
Patent Text Reader

Abstract

A memory system includes a non-volatile memory device comprising memory regions; and a controller configured to determine a duplicate physical address mapped to the second logical address in response to a first write request comprising a first logical address and a second logical address, and to selectively map the first logical address to the duplicate physical address based on the result of referencing a duplicate count corresponding to the duplicate physical address.
Need to check novelty before this filing date? Find Prior Art

Description

Technology Field

[0001] The present invention relates to a memory system and a data processing system, and more specifically, to a memory system and a data processing system including a non-volatile memory device. Background Technology

[0002] The memory system may be configured to store data provided by the host device in response to a write request from the host device. Additionally, the memory system may be configured to provide the stored data to the host device in response to a read request from the host device. The host device is an electronic device capable of processing data and may include a computer, a digital camera, or a mobile phone. The memory system may operate by being embedded in the host device or by being manufactured in a detachable form and connected to the host device. The problem to be solved

[0003] An embodiment of the present invention provides a memory system that efficiently manages redundant data, a method of operation thereof, and a data processing system. means of solving the problem

[0004] A memory system according to an embodiment of the present invention may include a non-volatile memory device comprising memory regions; and a controller configured to determine a duplicate physical address mapped to the second logical address in response to a first write request comprising a first logical address and a second logical address, and to selectively map the first logical address to the duplicate physical address according to the result of referencing a duplicate count corresponding to the duplicate physical address.

[0005] A method of operation of a memory system according to an embodiment of the present invention may include: receiving a first write request including a current logical address and a duplicate logical address; determining a duplicate physical address mapped to the duplicate logical address in response to the first write request; and determining whether to map the current logical address to the duplicate physical address based on the result of referencing a duplicate count corresponding to the duplicate physical address.

[0006] A data processing system according to an embodiment of the present invention may include: a host device configured to generate a first write request including a current logical address and a duplicate logical address; and a memory system configured to receive the first write request from the host device, determine a duplicate physical address mapped to the duplicate logical address, and selectively map the current logical address to the duplicate physical address based on the result of referencing a duplicate count corresponding to the duplicate physical address. Effects of the invention

[0007] A memory system, its method of operation, and a data processing system according to an embodiment of the present invention can efficiently manage redundant data. Brief explanation of the drawing

[0008] FIG. 1 is a block diagram illustrating a data processing system according to an embodiment of the present invention. FIGS. 2A and FIGS. 2B are drawings illustrating a method of operation of a controller according to an embodiment of the present invention. FIG. 3 is a drawing illustrating the operation method of a controller according to an embodiment of the present invention. FIGS. 4a and FIGS. 4b are drawings illustrating a method of operation of a controller according to an embodiment of the present invention. FIG. 5 is a flowchart illustrating the operation method of a memory system according to an embodiment of the present invention. FIG. 6 is a flowchart illustrating the operation method of a memory system according to an embodiment of the present invention. FIG. 7 is a drawing exemplarily illustrating a data processing system including a solid-state drive (SSD) according to an embodiment of the present invention, FIG. 8 is a drawing exemplarily illustrating a data processing system including a memory system according to an embodiment of the present invention, FIG. 9 is a drawing exemplarily illustrating a data processing system including a memory system according to an embodiment of the present invention. FIG. 10 is a drawing exemplarily illustrating a network system including a memory system according to an embodiment of the present invention, FIG. 11 is a block diagram illustrating, by way of example, a non-volatile memory device included in a memory system according to an embodiment of the present invention. Specific details for implementing the invention

[0009] The advantages and features of the present invention and the methods for achieving them will be explained in detail through the embodiments described below in conjunction with the accompanying drawings. However, the present invention is not limited to the embodiments described herein and may be embodied in other forms. These embodiments are provided merely to explain in detail enough to enable those skilled in the art to easily implement the technical concept of the present invention.

[0010] In the drawings, embodiments of the invention are not limited to the specific forms depicted and are exaggerated for clarity. Specific terms have been used herein, but are used for the purpose of describing the invention and are not intended to limit the meaning or the scope of the invention as defined in the claims.

[0011] In this specification, the expression "and / or" is used to mean including at least one of the components listed before and after it. Additionally, the expression "connected / combined" is used to mean being directly connected to another component or being indirectly connected through another component. In this specification, the singular form includes the plural form unless specifically stated otherwise in the text. Furthermore, components, steps, actions, and elements referred to as "include" or "comprising" in this specification signify the presence or addition of one or more other components, steps, actions, and elements.

[0012] Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

[0013] FIG. 1 is a block diagram illustrating a data processing system (100) according to an embodiment of the present invention.

[0014] The data processing system (100) may include a host device (110) and a memory system (120).

[0015] The host device (110) is an electronic device capable of processing data and may include a computer, a digital camera, or a mobile phone. The host device (110) may control the memory system (120) to store data in the memory system (120) and to read data from the memory system (120). The host device (110) may generate a first write request (WRITE1) including a first logical address, i.e., a current logical address (W-LBA), and a second logical address, i.e., a duplicate logical address (D-LBA), and transmit the first write request (WRITE1) to the memory system (120).

[0016] According to an embodiment, the host device (110) may generate a first write request (WRITE1) for the first data (DATA1) when copying the first data (DATA1). The duplicate logical address (D-LBA) is a logical address that was assigned to the first data (DATA1), and the current logical address (W-LBA) may be a logical address newly assigned to the copied first data (DATA1). Both the current logical address (W-LBA) and the duplicate logical address (D-LBA) may be in a state where they are effectively assigned to the first data (DATA1).

[0017] The memory system (120) may include a PCMCIA (Personal Computer Memory Card International Association) card, a CF (Compact Flash) card, a smart media card, a memory stick, various multimedia cards (MMC, eMMC, RS-MMC, MMC-micro), an SD (Secure Digital) card (SD, Mini-SD, Micro-SD), a UFS (Universal Flash Storage), or an SSD (Solid State Drive).

[0018] The memory system (120) may include a controller (121) and a non-volatile memory device (122).

[0019] The controller (121) can control the general operations of the memory system (120). The controller (121) can control the non-volatile memory device (122) to perform foreground operations in accordance with the instructions of the host device (110). The foreground operations may include writing data to the non-volatile memory device (122) and reading data from the non-volatile memory device (122) in accordance with the write request and read request of the host device (110).

[0020] Additionally, the controller (121) can control the non-volatile memory device (122) to perform necessary background operations internally independently of the host device (110). The background operations may include at least one of wear leveling operations, garbage collection operations, erase operations, read reclaim operations, and refresh operations for the non-volatile memory device (122). The background operations may include operations to write data to the non-volatile memory device (122) and to read data from the non-volatile memory device (122), similar to foreground operations.

[0021] The controller (121) may receive a first write request (WRITE1) from the host device (110). In response to the first write request (WRITE1), the controller (121) may determine a physical address (hereinafter referred to as a duplicate physical address) mapped to a duplicate logical address (D-LBA) and, based on the result of referencing a duplicate count corresponding to the duplicate physical address, may selectively map a current logical address (W-LBA) to the duplicate physical address.

[0022] Specifically, when the duplicate count corresponding to the duplicate physical address is less than a threshold, the controller (121) may increase the duplicate count corresponding to the duplicate physical address and map the current logical address (W-LBA) to the duplicate physical address. In this case, the controller (121) may not perform the operation of storing the first data (DATA1) in the non-volatile memory device (122) in response to the first write request (WRITE1).

[0023] On the other hand, when the duplicate count corresponding to the duplicate physical address is equal to the threshold, the controller (121) can store the first data (DATA1) corresponding to the first write request (WRITE1) in a selected memory area among the memory areas (MR) of the non-volatile memory device (122) and map the current logical address (W-LBA) to the physical address of the selected memory area. The host device (110) can transmit the first data (DATA1) along with the first write request (WRITE1) to the controller (121), and the controller (121) can store the first data (DATA1) transmitted from the host device (110) in a selected memory area of ​​the non-volatile memory device (122). According to an embodiment, the first write request (WRITE1) may not include the first data (DATA1), and the controller (121) may read the first data (DATA1) from a memory area of ​​a duplicate physical address in a non-volatile memory device (122) and store the read first data (DATA1) in a selected memory area.

[0024] According to an embodiment, when the controller (121) stores the first data (DATA1) in a selected memory area of ​​a non-volatile memory device (122), it may store a duplicate count corresponding to the physical address of the selected memory area as 0.

[0025] According to an embodiment, the host device (110) may transmit a second write request (not shown) to the controller (121) that includes a current logical address (W-LBA) but does not include a duplicate logical address (D-LBA). In response to the second write request, the controller (121) may store the second data corresponding to the second write request in a selected memory area among the memory areas (MR) of the non-volatile memory device (122) and map the current logical address (W-LBA) to a physical address in the selected memory area. According to an embodiment, the controller (121) may determine the previous physical address that was mapped to the current logical address (W-LBA) in response to the second write request and decrease the duplicate count corresponding to the previous physical address when the duplicate count corresponding to the previous physical address is greater than 0. According to an embodiment, when storing the second data in the selected memory area, the controller (121) may store the duplicate count corresponding to the physical address of the selected memory area as 0.

[0026] The controller (121) may refer to address mapping information (MAP_IF) to determine a physical address mapped to a logical address. Address mapping information (MAP_IF) may include the mapping relationship between the logical addresses used by the host device (110) and the physical addresses of memory regions (MR). Additionally, the controller (121) may refer to duplicate counts corresponding to physical addresses from duplicate count information (DCNT_IF). Duplicate count information (DCNT_IF) may include duplicate counts corresponding to each physical address.

[0027] The non-volatile memory device (122) can store data transmitted from the controller (121) under the control of the controller (121), and read the stored data to transmit it to the controller (121). The non-volatile memory device (122) may include a plurality of memory regions (MR) corresponding to different physical addresses.

[0028] The non-volatile memory device (122) may include a flash memory device such as NAND flash or NOR flash, FeRAM (Ferroelectrics Random Access Memory), PCRAM (Phase-Change Random Access Memory), MRAM (Magnetic Random Access Memory), or ReRAM (Resistive Random Access Memory).

[0029] A non-volatile memory device (122) may include one or more planes, one or more memory chips, one or more memory dies, or one or more memory packages. Meanwhile, FIG. 1 is illustrated as a memory system (120) comprising one non-volatile memory device (122), but the number of non-volatile memory devices included in the memory system (120) is not limited thereto.

[0030] FIG. 2a is a drawing illustrating the operation method of a controller (121) according to an embodiment of the present invention.

[0031] Referring to FIG. 2a, a host device (110) may transmit a first write request (WRITE1) to a controller (121). The first write request (WRITE1) may include a current logical address (W-LBA) (i.e., L2), a duplicate logical address (D-LBA) (i.e., L1), and first data (DATA1). When copying the first data (DATA1), the host device (110) may transmit a first write request (WRITE1) to the controller (121) that includes not only the current logical address (W-LBA) but also the duplicate logical address (D-LBA). The duplicate logical address (D-LBA) is a logical address that was previously assigned to the first data (DATA1), and the current logical address (W-LBA) may be a logical address newly assigned to the copied first data (DATA1). Therefore, the first data (DATA1) included in the first write request (WRITE1) may be duplicate data. Duplicate data can refer to the same data assigned to two or more different logical addresses.

[0032] The controller (121) receives a first write request (WRITE1) and can update the address mapping information (MAP_IF) and duplicate count information (DCNT_IF) as needed based on the first write request (WRITE1). Specifically, the controller (121) can determine the duplicate physical address (P1) mapped to the duplicate logical address (D-LBA) (L1) based on the address mapping information (MAP_IF). Then, the controller (121) can update the address mapping information (MAP_IF) by mapping the current logical address (W-LBA) (L2) to the duplicate physical address (P1). In other words, the controller (121) can update the address mapping information (MAP_IF) by mapping the duplicate logical address (D-LBA) (L1) and the current logical address (W-LBA) (L2) to the duplicate physical address (P1) in the same way. At this time, the controller (121) may not perform the operation of actually storing duplicate data (DATA1) in the memory area of ​​the non-volatile memory device (122) in response to the first write request (WRITE1).

[0033] Address mapping information (MAP_IF) may be composed of, for example, a table indexed by logical addresses (LBA). According to an embodiment, as illustrated in FIG. 2b, address mapping information (MAP_IF_1) may be composed of a table indexed by physical addresses (PBA). The address mapping information (MAP_IF_1) of FIG. 2b may be a multi-mapping method in which one or more logical addresses are mapped to each physical address. In address mapping information (MAP_IF_1), a duplicate physical address (P1) may be simultaneously mapped to a duplicate logical address (D-LBA) (L1) and a current logical address (W-LBA) (L2).

[0034] Referring again to FIG. 2a, the controller (121) can update the duplicate count information (DCNT_IF) by increasing the duplicate count (DCNT) corresponding to the duplicate physical address (P1) by 1. A duplicate count (DCNT) of 1 or more may mean that multiple logical addresses are mapped to the duplicate physical address (P1). For example, a duplicate count (DCNT) of k may mean that k+1 logical addresses are mapped to the duplicate physical address (P1). A duplicate count (DCNT) of 1 or more may mean that duplicate data is stored in the memory area of ​​the duplicate physical address (P1).

[0035] FIG. 3 is a diagram illustrating the operation method of a controller (121) according to an embodiment of the present invention. Unlike the method described with reference to FIG. 2, the controller (121) can further determine whether the duplicate count (DCNT) exceeds a threshold (TH) in response to a first write request (WRITE1) for duplicate data, i.e., first data (DATA1).

[0036] Specifically, with reference to FIG. 3, the host device (110) can transmit a first write request (WRITE1) to the controller (121). The first write request (WRITE1) may include a current logical address (W-LBA) (L2), a duplicate logical address (D-LBA) (L1), and first data (DATA1).

[0037] The controller (121) receives a first write request (WRITE1) and, based on the first write request (WRITE1), can update the address mapping information (MAP_IF) and the duplicate count information (DCNT_IF) as needed. Specifically, the controller (121) can determine the duplicate physical address (P1) mapped to the duplicate logical address (D-LBA) (L1) based on the address mapping information (MAP_IF). The controller (121) may not update the duplicate count information (DCNT_IF) when the duplicate count (DCNT) corresponding to the duplicate physical address (P1) is equal to the threshold value (TH) based on the duplicate count information (DCNT_IF). In other words, the duplicate count (DCNT) corresponding to the duplicate physical address (P1) may remain in a state equal to the threshold value (TH). And the controller (121) can update address mapping information (MAP_IF) by storing the first data (DATA1) in a selected memory area of ​​a non-volatile memory device (122) and mapping the current logical address (W-LBA) (L2) to the physical address (P2) of the selected memory area.

[0038] On the other hand, the controller (121) may operate as described with reference to FIG. 2a when the duplicate count (DCNT) corresponding to the duplicate physical address (P1) is less than the threshold (TH), unlike as illustrated in FIG. 3. That is, the controller (121) may not perform the operation of mapping the current logical address (W-LBA) (L2) to the duplicate physical address (P1) and actually storing the duplicate data (DATA1) in the memory area of ​​the non-volatile memory device (122).

[0039] Meanwhile, the first data (DATA1), which is duplicate data, may be transmitted together with the first write request (WRITE1) as illustrated in FIGS. 2 and 3. According to an embodiment, the first write request (WRITE1) may not include the first data (DATA1), and the controller (121) may read the first data (DATA1) from a memory area corresponding to the duplicate physical address (P1) and store the read first data (DATA1) in a selected memory area of ​​a non-volatile memory device (122).

[0040] According to an embodiment, the controller (121) can update the duplicate count information (DCNT_IF) by storing the duplicate count (DCNT) corresponding to the physical address (P2) as 0. A duplicate count (DCNT) of 0 may mean that only one logical address (i.e., L2) is mapped to the physical address (P2).

[0041] FIGS. 4a and FIGS. 4b are drawings illustrating the operation method of a controller (121) according to an embodiment of the present invention.

[0042] Referring to FIG. 4a, the host device (110) may transmit a second write request (WRITE2) to the controller (121). The second write request (WRITE2) may include a current logical address (W-LBA) (L2) and second data (DATA2). For example, the host device (110) may update the second data (DATA2) that was assigned to the current logical address (W-LBA) (L2), and then assign the current logical address (W-LBA) (L2) to the updated second data (DATA2) in the same way. At this time, the second write request (WRITE2) for the updated second data (DATA2) may not include a duplicate logical address (D-LBA). As another example, the host device (110) may assign the current logical address (W-LBA) (L2) to the newly created second data (DATA2) when the current logical address (W-LBA) (L2) is not assigned to any data. In this case, the second write request (WRITE2) for new data may not include a duplicate logical address (D-LBA).

[0043] The controller (121) receives a second write request (WRITE2) and can update address mapping information (MAP_IF) and duplicate count information (DCNT_IF) as needed based on the second write request (WRITE2). Specifically, the controller (121) can determine the previous physical address (P1) mapped to the current logical address (W-LBA) (L2) based on the address mapping information (MAP_IF). The controller (121) can check the duplicate count (DCNT) corresponding to the previous physical address (P1) based on the duplicate count information (DCNT_IF). A duplicate count (DCNT) of 1 or more may mean that duplicate data is stored in the memory area of ​​the previous physical address (P1). A duplicate count (DCNT) of 1 or more may mean that the previous data of the current logical address (W-LBA) (L2) (i.e., data before being updated to the second data (DATA2)) is duplicate data. Accordingly, the controller (121) can update the duplicate count information (DCNT_IF) by decreasing the duplicate count (DCNT) by 1. And, the controller (121) can update the address mapping information (MAP_IF) by storing the second data (DATA2) in a selected memory area and mapping the current logical address (W-LBA) (L2) to the physical address (P2) of the selected memory area.

[0044] According to an embodiment, the controller (121) can update duplicate count information (DCNT_IF) by storing the duplicate count (DCNT) corresponding to the physical address (P2) as 0. That is, a duplicate count (DCNT) of 0 may mean that only one logical address (i.e., L2) is mapped to the physical address (P2). A duplicate count (DCNT) of 0 may mean that the data stored in the memory area of ​​the physical address (P2) is not duplicate data.

[0045] Referring to FIG. 4b, the case where the duplicate count (DCNT) corresponding to the previous physical address (P1) is 0 is illustrated. A duplicate count (DCNT) of 0 may mean that the data stored in the memory area of ​​the physical address (P1) is not duplicate data. Therefore, the controller (121) will not need to decrease the duplicate count (DCNT) corresponding to the previous physical address (P1), as described with reference to FIG. 4a.

[0046] However, the controller (121) can update the address mapping information (MAP_IF) by storing the second data (DATA2) in a selected memory area as described with reference to FIG. 4a and mapping the current logical address (W-LBA) (L2) to the physical address (P2) of the selected memory area. According to an embodiment, the controller (121) can update the duplicate count information (DCNT_IF) by storing the duplicate count (DCNT) corresponding to the physical address (P2) as 0.

[0047] According to an embodiment, when the second data (DATA2) is newly generated data rather than updated data, the current logical address (W-LBA) (L2) in the address mapping information (MAP_IF) may not be mapped to any physical address. In this case, the operation of referencing the duplicate count information (DCNT_IF) may be omitted.

[0048] According to an embodiment, a write request for duplicate data (e.g., a first write request (WRITE1)) and a write request for updated data (or new data) (e.g., a second write request (WRITE2)) may be transmitted in different formats. Accordingly, the controller (121) may distinguish between a write request for duplicate data and a write request for updated data (or new data) and operate as described with reference to FIGS. 2a through 4b. According to an embodiment, the controller (121) may distinguish between a write request for duplicate data and a write request for updated data (or new data) by determining whether the write request includes or does not include a duplicate logical address (D-LBA).

[0049] According to an embodiment, duplicate count information (DCNT_IF) may be generated for all physical addresses. In this case, a duplicate count (DCNT) corresponding to a physical address being 0 may mean that the data stored in the memory area of ​​that physical address is not duplicate data. A duplicate count (DCNT) corresponding to a physical address being 0 may mean that the memory area of ​​that physical address is an empty memory area. When the duplicate count (DCNT) corresponding to a physical address is k, it may mean that k+1 logical addresses are mapped to that physical address.

[0050] According to an embodiment, duplicate count information (DCNT_IF) may be generated for the physical addresses of memory regions where valid data is stored. In this case, if the duplicate count (DCNT) corresponding to a physical address is 0, it may mean that the data stored in the memory region of that physical address is not duplicate data. If the duplicate count (DCNT) corresponding to a physical address is k, it may mean that k+1 logical addresses are mapped to that physical address. If the memory region of a physical address stores invalid data (e.g., data prior to updated data), the duplicate count (DCNT) of that physical address may be deleted (or removed or invalidated) from the duplicate count information (DCNT_IF). For example, in FIG. 4b, since the memory region of the previous physical address (P1) stores data prior to the second data (DATA2), the duplicate count (DCNT) of the previous physical address (P1) may be deleted (or removed or invalidated) from the duplicate count information (DCNT_IF).

[0051] According to an embodiment, duplicate count information (DCNT_IF) may be generated only for the physical addresses of memory regions where duplicate data is stored. In this case, the minimum value of the duplicate count (DCNT) included in the duplicate count information (DCNT_IF) may be 1. When the duplicate count (DCNT) corresponding to a physical address is k, it may mean that k+1 logical addresses are mapped to that physical address. When a physical address included in the duplicate count information (DCNT_IF) no longer stores duplicate data, the duplicate count (DCNT) of that physical address may be deleted (or removed or invalidated) from the duplicate count information (DCNT_IF).

[0052] According to the present invention, when different logical addresses are commonly assigned to duplicate data, the memory system (120) may not redundantly store the duplicate data. Therefore, since the total amount of valid data is reduced, management operations of the memory system (120), such as garbage collection operations that move valid data to a new memory area, can be performed more efficiently.

[0053] FIG. 5 is a flowchart illustrating the operation method of the memory system (120) of FIG. 1 according to an embodiment of the present invention. In FIG. 5, duplicate count information (DCNT_IF) is assumed to be generated for all physical addresses.

[0054] Referring to FIG. 5, in step (S101), the controller (121) can receive a light request from the host device (110).

[0055] In step (S102), the controller (121) can determine whether the write request contains a duplicate logical address (D-LBA). When it is determined that the write request contains a duplicate logical address (D-LBA), the procedure can proceed to step (S103). When it is determined that the write request does not contain a duplicate logical address (D-LBA), the procedure can proceed to step (S106).

[0056] In step (S103), the controller (121) can determine a duplicate physical address mapped to a duplicate logical address (D-LBA) based on address mapping information (MAP_IF).

[0057] In step (S104), the controller (121) can increase the duplicate count corresponding to the duplicate physical address in the duplicate count information (DCNT_IF) by 1.

[0058] In step (S105), the controller (121) can update the address mapping information (MAP_IF) by mapping the current logical address (W-LBA) to a duplicate physical address.

[0059] In step (S106), the controller (121) can determine the previous physical address mapped to the current logical address (W-LBA) based on the address mapping information (MAP_IF).

[0060] In step (S107), the controller (121) can determine whether the duplicate count corresponding to the previous physical address is greater than 0 based on the duplicate count information (DCNT_IF). When it is determined that the duplicate count is greater than 0, the procedure can proceed to step (S108). When it is determined that the duplicate count is not greater than 0, the procedure can proceed to step (S109).

[0061] In step (S108), the controller (121) can decrease the duplicate count corresponding to the previous physical address in the duplicate count information (DCNT_IF) by 1.

[0062] In step (S109), the controller (121) can update address mapping information (MAP_IF) by storing data corresponding to the write request in a selected memory area and mapping the current logical address (W-LBA) to a physical address in the selected memory area.

[0063] In step (S110), the controller (121) can store the duplicate count corresponding to the physical address of the memory area selected in the duplicate count information (DCNT_IF) as 0.

[0064] FIG. 6 is a flowchart illustrating the operation method of the memory system (120) of FIG. 1 according to an embodiment of the present invention.

[0065] The steps (S201–S210) of FIG. 6 may be similar to the steps (S101–S110) of FIG. 5. Therefore, a detailed description will be omitted.

[0066] In step (S211), the controller (121) can determine whether the duplicate count corresponding to duplicate physical addresses is less than a threshold (TH) based on duplicate count information (DCNT_IF). When it is determined that the duplicate count is less than the threshold (TH), the procedure can proceed to step (S204). When it is determined that the duplicate count is not less than the threshold (TH), the procedure can proceed to step (S209).

[0067] FIG. 7 is a diagram illustrating an exemplary data processing system including a solid state drive (SSD) according to an embodiment of the present invention. Referring to FIG. 7, the data processing system (1000) may include a host device (1100) and a solid state drive (1200) (hereinafter referred to as SSD). The host device (1100) may include the host device (110) of FIG. 1.

[0068] The SSD (1200) may include a controller (1210), a buffer memory device (1220), non-volatile memory devices (1231 to 123n), a power supply (1240), a signal connector (1250), and a power connector (1260).

[0069] The controller (1210) can control the general operations of the SSD (1200). The controller (1210) may include the controller (121) of FIG. 1. The controller (1210) may include a host interface unit (1211), a control unit (1212), a random access memory (1213), an error correction code (ECC) unit (1214), and a memory interface unit (1215).

[0070] The host interface unit (1211) can exchange signals (SGL) with the host device (1100) through the signal connector (1250). Here, the signal (SGL) may include commands, addresses, data, etc. The host interface unit (1211) can interface the host device (1100) with the SSD (1200) according to the protocol of the host device (1100). For example, the host interface unit (1211) can communicate with the host device (1100) through any one of the standard interface protocols such as secure digital, USB (universal serial bus), MMC (multi-media card), eMMC (embedded MMC), PCMCIA (personal computer memory card international association), PATA (parallel advanced technology attachment), SATA (serial advanced technology attachment), SCSI (small computer system interface), SAS (serial attached SCSI), PCI (peripheral component interconnection), PCI-E (PCI Expresss), and UFS (universal flash storage).

[0071] The control unit (1212) can analyze and process a signal (SGL) input from the host device (1100). The control unit (1212) can control the operation of background function blocks according to firmware or software for driving the SSD (1200). Random access memory (1213) can be used as an operating memory for driving such firmware or software.

[0072] The error correction code (ECC) unit (1214) can generate parity data for data to be transmitted to non-volatile memory devices (1231–123n). The generated parity data can be stored in the non-volatile memory devices (1231–123n) along with the data. The error correction code (ECC) unit (1214) can detect errors in the data read from the non-volatile memory devices (1231–123n) based on the parity data. If the detected error is within the correction range, the error correction code (ECC) unit (1214) can correct the detected error.

[0073] The memory interface unit (1215) can provide control signals, such as commands and addresses, to non-volatile memory devices (1231 to 123n) under the control of the control unit (1212). The memory interface unit (1215) can also exchange data with the non-volatile memory devices (1231 to 123n) under the control of the control unit (1212). For example, the memory interface unit (1215) can provide data stored in the buffer memory device (1220) to the non-volatile memory devices (1231 to 123n), or provide data read from the non-volatile memory devices (1231 to 123n) to the buffer memory device (1220).

[0074] The buffer memory device (1220) can temporarily store data to be stored in the non-volatile memory devices (1231–123n). Additionally, the buffer memory device (1220) can temporarily store data read from the non-volatile memory devices (1231–123n). Data temporarily stored in the buffer memory device (1220) can be transferred to the host device (1100) or the non-volatile memory devices (1231–123n) under the control of the controller (1210).

[0075] Non-volatile memory devices (1231–123n) can be used as storage media for the SSD (1200). Each of the non-volatile memory devices (1231–123n) can be connected to the controller (1210) through multiple channels (CH1–CHn). One or more non-volatile memory devices can be connected to a single channel. Non-volatile memory devices connected to a single channel can be connected to the same signal bus and data bus.

[0076] The power supply (1240) can provide power (PWR) input through the power connector (1260) to the SSD (1200) background. The power supply (1240) may include an auxiliary power supply (1241). The auxiliary power supply (1241) can supply power so that the SSD (1200) can shut down normally in the event of a sudden power off. The auxiliary power supply (1241) may include large capacitors.

[0077] The signal connector (1250) can be configured with various types of connectors depending on the interface method between the host device (1100) and the SSD (1200).

[0078] The power connector (1260) can be configured with various types of connectors depending on the power supply method of the host device (1100).

[0079] FIG. 8 is a diagram illustrating an exemplary data processing system including a memory system according to an embodiment of the present invention. Referring to FIG. 8, the data processing system (2000) may include a host device (2100) and a memory system (2200).

[0080] The host device (2100) may be configured in the form of a board, such as a printed circuit board. Although not illustrated, the host device (2100) may include background function blocks to perform the functions of the host device.

[0081] The host device (2100) may include a connection terminal (2110), such as a socket, slot, or connector. The memory system (2200) may be mounted to the connection terminal (2110).

[0082] The memory system (2200) may be configured in the form of a substrate such as a printed circuit board. The memory system (2200) may be referred to as a memory module or a memory card. The memory system (2200) may include a controller (2210), a buffer memory device (2220), non-volatile memory devices (2231–2232), a power management integrated circuit (PMIC) (2240), and a connection terminal (2250).

[0083] The controller (2210) can control the general operations of the memory system (2200). The controller (2210) can be configured in the same way as the controller (1210) shown in FIG. 7.

[0084] The buffer memory device (2220) can temporarily store data to be stored in the non-volatile memory devices (2231–2232). Additionally, the buffer memory device (2220) can temporarily store data read from the non-volatile memory devices (2231–2232). Data temporarily stored in the buffer memory device (2220) can be transferred to the host device (2100) or the non-volatile memory devices (2231–2232) under the control of the controller (2210).

[0085] Non-volatile memory devices (2231–2232) can be used as storage media for the memory system (2200).

[0086] The PMIC (2240) can provide power input through the connection terminal (2250) to the background of the memory system (2200). The PMIC (2240) can manage the power of the memory system (2200) under the control of the controller (2210).

[0087] The connection terminal (2250) can be connected to the connection terminal (2110) of the host device. Through the connection terminal (2250), signals such as commands, addresses, data, and power can be transmitted between the host device (2100) and the memory system (2200). The connection terminal (2250) can be configured in various forms depending on the interface method between the host device (2100) and the memory system (2200). The connection terminal (2250) can be placed on one side of the memory system (2200).

[0088] FIG. 9 is a diagram illustrating an exemplary data processing system including a memory system according to an embodiment of the present invention. Referring to FIG. 9, the data processing system (3000) may include a host device (3100) and a memory system (3200).

[0089] The host device (3100) may be configured in the form of a board, such as a printed circuit board. Although not illustrated, the host device (3100) may include background function blocks to perform the functions of the host device.

[0090] The memory system (3200) may be configured in the form of a surface-mount package. The memory system (3200) may be mounted to a host device (3100) via a solder ball (3250). The memory system (3200) may include a controller (3210), a buffer memory device (3220), and a non-volatile memory device (3230).

[0091] The controller (3210) can control the general operations of the memory system (3200). The controller (3210) can be configured in the same way as the controller (1210) shown in FIG. 7.

[0092] The buffer memory device (3220) can temporarily store data to be stored in the non-volatile memory device (3230). Additionally, the buffer memory device (3220) can temporarily store data read from the non-volatile memory devices (3230). Data temporarily stored in the buffer memory device (3220) can be transferred to the host device (3100) or the non-volatile memory device (3230) under the control of the controller (3210).

[0093] A non-volatile memory device (3230) can be used as a storage medium for a memory system (3200).

[0094] FIG. 10 is a diagram illustrating an exemplary network system including a memory system according to an embodiment of the present invention. Referring to FIG. 10, the network system (4000) may include a server system (4300) and a plurality of client systems (4410 to 4430) connected through a network (4500).

[0095] The server system (4300) can provide data in response to requests from multiple client systems (4410 to 4430). For example, the server system (4300) can store data provided by multiple client systems (4410 to 4430). As another example, the server system (4300) can provide data to multiple client systems (4410 to 4430).

[0096] The server system (4300) may include a host device (4100) and a memory system (4200). The memory system (4200) may be composed of the memory system (120) of FIG. 1, the SSD (1200) of FIG. 7, the memory system (2200) of FIG. 8, and the memory system (3200) of FIG. 9.

[0097] FIG. 11 is a block diagram illustrating, by way of example, a non-volatile memory device included in a memory system according to an embodiment of the present invention. Referring to FIG. 11, the non-volatile memory device (300) may include a memory cell array (310), a row decoder (320), a data read / write block (330), a column decoder (340), a voltage generator (350), and control logic (360).

[0098] The memory cell array (310) may include memory cells (MC) arranged in areas where word lines (WL1~WLm) and bit lines (BL1~BLn) intersect each other.

[0099] The row decoder (320) can be connected to the memory cell array (310) through the word lines (WL1–WLm). The row decoder (320) can operate under the control of the control logic (360). The row decoder (320) can decode an address provided from an external device (not shown). The row decoder (320) can select and drive the word lines (WL1–WLm) based on the decoding result. For example, the row decoder (320) can provide a word line voltage provided from the voltage generator (350) to the word lines (WL1–WLm).

[0100] The data read / write block (330) can be connected to the memory cell array (310) through bit lines (BL1 to BLn). The data read / write block (330) may include read / write circuits (RW1 to RWn) corresponding to each of the bit lines (BL1 to BLn). The data read / write block (330) can operate under the control of the control logic (360). Depending on the operation mode, the data read / write block (330) can operate as a write driver or as a sense amplifier. For example, the data read / write block (330) can operate as a write driver that stores data provided from an external device in the memory cell array (310) during a write operation. As another example, the data read / write block (330) can operate as a sense amplifier that reads data from the memory cell array (310) during a read operation.

[0101] The column decoder (340) can operate under the control of the control logic (360). The column decoder (340) can decode an address provided from an external device. Based on the decoding result, the column decoder (340) can connect the read / write circuits (RW1~RWn) of the data read / write block (330) corresponding to each of the bit lines (BL1~BLn) with the data input / output line (or data input / output buffer).

[0102] The voltage generator (350) can generate a voltage used for background operation of the non-volatile memory device (300). The voltages generated by the voltage generator (350) can be applied to the memory cells of the memory cell array (310). For example, a program voltage generated during a program operation can be applied to the word lines of the memory cells where the program operation is to be performed. As another example, an erase voltage generated during an erase operation can be applied to the well regions of the memory cells where the erase operation is to be performed. As another example, a read voltage generated during a read operation can be applied to the word lines of the memory cells where the read operation is to be performed.

[0103] The control logic (360) can control the general operations of the non-volatile memory device (300) based on a control signal provided from an external device. For example, the control logic (360) can control the read, write, and erase operations of the non-volatile memory device (300).

[0104] A person skilled in the art to which the present invention pertains should understand that the present invention may be implemented in other specific forms without altering its technical concept or essential features, and therefore the embodiments described above should be understood as illustrative in all respects and not restrictive. The scope of the present invention is defined by the claims set forth below rather than by the detailed description above, and all modifications or variations derived from the meaning and scope of the claims and equivalent concepts should be interpreted as being included within the scope of the present invention. Explanation of the symbols

[0105] 100: Data processing unit 110: Host device 120: Memory System 121: Controller 122: Non-volatile memory device MR: Memory regions

Claims

Claim 1 A memory system comprising: a non-volatile memory device including memory regions; and a controller configured to determine a duplicate physical address mapped to the second logical address in response to a first write request including a first logical address and a second logical address, and to selectively map the first logical address to the duplicate physical address according to the result of referencing a duplicate count corresponding to the duplicate physical address. Claim 2 In claim 1, the controller is a memory system that increases the duplicate count and maps the first logical address to the duplicate physical address when the duplicate count is less than a threshold. Claim 3 A memory system according to claim 1, wherein the controller stores first data corresponding to the first write request in a selected memory area among the memory areas when the duplicate count is equal to a threshold value, and maps the first logical address to a physical address of the selected memory area. Claim 4 In paragraph 3, the controller reads the first data from the memory area of ​​the duplicate physical address and stores the read first data in the selected memory area. Claim 5 In paragraph 3, the controller is a memory system that stores a duplicate count corresponding to the physical address of the selected memory area as 0 when storing the first data in the selected memory area. Claim 6 A memory system according to claim 1, wherein the controller responds to a second write request that includes the first logical address but does not include the second logical address, stores second data corresponding to the second write request in a selected memory area among the memory areas, and maps the first logical address to a physical address of the selected memory area. Claim 7 A memory system according to claim 6, wherein the controller, in response to the second write request, determines a previous physical address that was mapped to the first logical address, and decreases the duplicate count corresponding to the previous physical address when the duplicate count corresponding to the previous physical address is greater than 0. Claim 8 A method of operating a memory system comprising: receiving a first write request including a first logical address and a second logical address; determining a duplicate physical address mapped to the second logical address in response to the first write request; and determining whether to map the first logical address to the duplicate physical address based on the result of referencing a duplicate count corresponding to the duplicate physical address. Claim 9 A method of operation of a memory system according to claim 8, wherein the step of determining whether to map the first logical address to the duplicate physical address comprises the step of increasing the duplicate count and determining to map the first logical address to the duplicate physical address when the duplicate count is less than a threshold. Claim 10 A method of operation of a memory system according to claim 8, wherein the step of determining whether to map the first logical address to the duplicate physical address comprises the step of determining to store the first data corresponding to the first write request in a selected memory area among memory areas and to map the first logical address to the physical address of the selected memory area when the duplicate count is equal to a threshold value. Claim 11 A method of operation of a memory system according to claim 8, further comprising: receiving a second write request including the first logical address but not the second logical address; and in response to the second write request, storing second data corresponding to the second write request in a selected memory area among memory areas and mapping the first logical address to a physical address of the selected memory area. Claim 12 A method of operation of a memory system according to claim 11, further comprising: a step of determining a previous physical address that was mapped to the first logical address in response to the second write request; and a step of decreasing the duplicate count corresponding to the previous physical address when the duplicate count corresponding to the previous physical address is greater than 0. Claim 13 A data processing system comprising: a host device configured to generate a first write request including a current logical address and a duplicate logical address; and a memory system configured to receive the first write request from the host device, determine a duplicate physical address mapped to the duplicate logical address, and selectively map the current logical address to the duplicate physical address based on the result of referencing a duplicate count corresponding to the duplicate physical address. Claim 14 In paragraph 13, the host device generates the first write request when copying data, and the duplicate logical address is a logical address that was assigned to the data, and the current logical address is a logical address newly assigned to the copied data, in a data processing system. Claim 15 In paragraph 13, the memory system is a data processing system that, when the duplicate count is less than a threshold, increases the duplicate count and maps the current logical address to the duplicate physical address. Claim 16 In claim 13, the memory system is a data processing system that, when the duplicate count is equal to a threshold value, stores first data corresponding to the first write request in a selected memory area among the memory areas of a non-volatile memory device and maps the current logical address to the physical address of the selected memory area. Claim 17 In claim 16, the memory system reads the first data from the memory area of ​​the duplicate physical address and stores the read first data in the selected memory area. Claim 18 In claim 16, the memory system is a data processing system that stores a duplicate count corresponding to the physical address of the selected memory area as 0 when storing the first data in the selected memory area. Claim 19 In claim 13, the memory system responds to a second write request that includes the current logical address but does not include the duplicate logical address, stores second data corresponding to the second write request in a selected memory area among the memory areas of a non-volatile memory device, and maps the current logical address to a physical address of the selected memory area. Claim 20 In claim 19, the memory system determines a previous physical address that was mapped to the current logical address in response to the second write request, and a data processing system that decreases the duplicate count corresponding to the previous physical address when the duplicate count corresponding to the previous physical address is greater than 0.

Citation Information

Patent Citations

  • Metadata redundancy schemes for non-volatile memories

    KR1020110031130A

  • Storage device, electronic device having the same, and data management methods thereof

    KR1020130081526A

  • Memory system and operating method thereof

    KR1020160114337A

  • Controller and operating method thereof

    KR1020200019431A

  • Apparatus and method for checking valid data in memory system

    KR1020200033625A