Quick Erase on Storage Devices
By encrypting and decrypting the written data in the memory system, the problems of clearing operation delay and insufficient data security in the prior art are solved, and a safer and more efficient data removal process is achieved.
Patent Information
- Application Number
- CN202010880571.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2019-08-29
- Filing Date
- 2020-08-27
- Publication Date
- 2024-11-05
- Estimated Expiration
- 2040-08-27
AI Technical Summary
When existing memory systems perform clearing operations, the lengthy erase process results in data removal delays and lack effective security mechanisms to prevent hosts from accessing clearing data.
By encrypting the written data in the memory control unit and decrypting only the data not stored in the clear area during reading, it ensures that the host cannot access the clear data and avoids lengthy erasing operations.
Simplifies clearing operations, reduces data removal delays, and improves data security, preventing hosts from accessing unauthorized data.
Smart Images

Figure CN112446036B_ABST
Abstract
Description
Technical Field
[0001] Embodiments of the present disclosure relate to managed memory devices, and more particularly, to improvements to clear operations performed on managed memory devices. Background Art
[0002] Memory devices are typically provided as internal semiconductor integrated circuits in computers or other electronic devices. There are many different types of memory, including volatile and non-volatile memory. Volatile memory may require power to maintain data, and includes random access memory (RAM), dynamic random access memory (DRAM), and synchronous dynamic random access memory (SDRAM), etc. Non-volatile memory can provide persistent data by retaining stored data when power is not supplied, and may include NAND flash memory, NOR flash memory, read-only memory (ROM), electrically erasable programmable ROM (EEPROM), erasable programmable ROM (EPROM), and resistance variable memory, such as phase change random access memory (PCRAM), resistive random access memory (RRAM), and magnetoresistive random access memory (MRAM), 3D XPointTM memory, etc.
[0003] Memory cells are typically arranged in a matrix or array. Multiple matrices or arrays may be combined into a memory device, and multiple devices are combined to form a storage volume of a memory system, such as a solid-state drive (SSD), a universal flash memory (UFS™) device, a multimedia card (MMC) solid-state memory device, an embedded MMC device (eMMC™), etc., as will be discussed further later herein.
[0004] Some memory systems encrypt data stored in the system to provide enhanced data security. However, there is still room for improvement in the operation and / or interoperability of currently known systems. Summary of the invention
[0005] One aspect of the present disclosure provides a memory device, wherein the memory device includes: a memory array including memory cells; a communication interface to a host device; a memory control unit operably coupled to the memory array and the communication interface and configured to: encrypt write data received via the communication interface to generate encrypted data; program selected memory cells of the memory array with the encrypted data; read the encrypted data from a portion of the memory cells in response to a memory read request; and decrypt the read encrypted data to generate read decrypted data only for a portion of the read encrypted data that is not stored in a clear area of the memory array.
[0006] Another aspect of the present disclosure provides a method of operating a memory, wherein the method includes: receiving data to be written to a portion of memory cells of a memory array of the memory; encrypting the data to be written; programming the memory cells with the encrypted data; reading the encrypted data from the memory cells; and decrypting the read encrypted data to generate read decrypted data only for the portion of the read encrypted data that is not stored in a clear area of the memory array.
[0007] Another aspect of the present disclosure provides a memory system, wherein the memory system includes: a host device; and a memory device, the memory device including a memory control unit configured to: receive data to be written to a portion of memory cells of a memory array of the memory device from the host device; encrypt the data to be written; program the memory cells with the encrypted data; read the encrypted data from the portion of the memory cells; and decrypt the read encrypted data to generate read decrypted data only for the portion of the read encrypted data that is not stored in the clear area of the memory array; and transmit the read decrypted data to the host device. BRIEF DESCRIPTION OF THE DRAWINGS
[0008] In the drawings, which are not necessarily drawn to scale, like numbers may describe similar components in different views. Like numbers with different letter suffixes may represent different instances of similar components. The drawings generally illustrate various embodiments discussed in this document by way of example and not limitation.
[0009] Figure 1 An example system including a host and a memory device is described.
[0010] Figure 2 is a block diagram of an apparatus in the form of a memory device including non-volatile memory cells.
[0011] Figure 3 is a description representing an example of an area of physical memory in a memory array.
[0012] Figure 4 is a flow chart of a method of operating a memory device to perform a clear operation.
[0013] Figure 5 is a block diagram of a portion of an example of a memory device.
[0014] Fig. 6A is a block diagram of a memory device showing a write data path.
[0015] Figure 6B is a block diagram of a memory device showing a read data path.
[0016] Figure 7 is an instance of a table that can be used to track unmapped logical addresses.
[0017] Figure 8 is a block diagram of a memory device showing an alternative write path or read path.
[0018] Fig. 9 A block diagram illustrating an example machine according to some embodiments described herein. DETAILED DESCRIPTION
[0019] Memory devices, particularly NVM devices (e.g., NAND flash devices, etc.), may include arrays of multi-level memory cells. Memory devices may perform erase, discard, and clear operations on the array. A discard operation is a non-secure variation of an erase operation. A clear operation requires removing data from an unmapped memory space in a more secure manner. In conventional methods, information is removed by physically erasing the data using a NAND erase operation. Depending on the number of unmapped areas, their size, and location, the clear operation may be very lengthy.
[0020] A memory device includes an individual memory die, which may, for example, include a storage area including one or more memory cell arrays that implement one (or more) selected storage technologies. This memory die will typically include support circuitry for operating the memory array. Other examples, sometimes commonly referred to as "managed memory devices," include an assembly of one or more memory dies associated with controller functionality that is configured to control the operation of the one or more memory dies. This controller functionality can simplify interoperability with external devices such as "hosts," as discussed later herein. In such managed memory devices, the controller functionality may be implemented on one or more dies that are also incorporated into the memory array or on a separate die. In other examples, one or more memory devices may be combined with controller functionality to form a solid-state drive (SSD) storage volume.
[0021] Embodiments of the present disclosure are described in the example of managed memory devices implementing NAND flash memory cells (referred to as "managed NAND" devices). However, these examples do not limit the scope of the present disclosure, which may be implemented in other forms of memory devices and / or with other forms of storage technology.
[0022] Both NOR and NAND flash architecture semiconductor memory arrays are accessed through a decoder that activates a particular memory cell by selecting a word line coupled to the gate of the memory cell. In a NOR architecture semiconductor memory array, once activated, the selected memory cell places its data value on the bit line, causing different currents to flow depending on the state in which the particular cell is programmed. In a NAND architecture semiconductor memory array, a high bias voltage is applied to the drain side select gate (SGD) line. The word line coupled to the gates of the unselected memory cells of each group is driven with a specified pass voltage (e.g., Vpass) to operate the unselected memory cells of each group as pass transistors (e.g., to pass current in a manner that is not constrained by their stored data values). Current then flows from the source line to the bit line through each series-coupled group, constrained only by the selected memory cells of each group, placing the currently encoded data value of the selected memory cell on the bit line.
[0023] Each flash memory cell in a NOR or NAND architecture semiconductor memory array can be programmed individually or collectively to one or more programming states. For example, a single-level cell (SLC) can represent one of two programming states (e.g., 1 or 0), which represents one data bit. Flash memory cells can also represent more than two programming states, allowing higher density memories to be manufactured without increasing the number of memory cells, because each cell can represent more than one binary digit (e.g., more than one bit). Such cells may be referred to as multi-state memory cells, multi-digit cells, or multi-level cells (MLC). In some examples, MLC may refer to a memory cell that can store two data bits per cell (e.g., one of four programming states), a three-level cell (TLC) may refer to a memory cell that can store three data bits per cell (e.g., one of eight programming states), and a four-level cell (QLC) can store four data bits per cell. MLC is used herein in its broader context to refer to any memory cell that can store more than one data bit per cell (i.e., it can represent more than two programming states).
[0024] The managed memory devices may be configured and operated according to recognized industry standards. For example, the managed NAND device may be, as a non-limiting example, a Universal Flash Storage (UFS™) device or an embedded MMC device (eMMC™), etc. For example, in the case of the above example, the UFS device may be configured according to a Joint Electronic Device Engineering Council (JEDEC) standard (e.g., JEDEC standard JESD223D entitled JEDEC UFS Flash Storage 3.0, etc. and / or an update or subsequent version of this standard). Similarly, the identified eMMC device may also be configured according to JEDEC standard JESD84-A51 entitled "JEDEC eMMC standard 5.1" and / or an update or subsequent version of this standard.
[0025] SSDs are particularly useful as primary storage devices for computers, outperforming traditional hard disk drives with moving parts in terms of, for example, performance, size, weight, ruggedness, operating temperature range, and power consumption. For example, SSDs can reduce seek times, latency, or other delays associated with magnetic disk drives (e.g., electromechanical, etc.). SSDs use non-volatile memory cells (e.g., flash memory cells) to eliminate internal battery power requirements, thus allowing the drives to be more versatile and compact. Managed memory devices (e.g., managed NAND devices) can be used as primary or secondary storage in the form of various electronic devices, and are often used in mobile devices.
[0026] Both SSDs and managed memory devices may include several memory devices, which include several dies or logical units (e.g., logical unit numbers or LUNs), and may include one or more processors or other controllers that perform the logic functions required to operate the memory devices or interface with external systems. Such SSDs and managed memory devices may include one or more flash memory dies, on which several memory arrays and peripheral circuitry are included. The flash memory array may include several blocks of memory cells organized into several physical pages. In some examples, the SSD may also include DRAM or SRAM (or other forms of memory dies or other memory structures). Similarly, managed NAND devices may include one or more arrays of volatile and / or non-volatile memory separate from the NAND memory arrays and within or separate from the controller. Both the SSD and the managed NAND device can receive commands associated with memory operations (such as read or write operations) from the host, such as read or write operations used to transfer data (such as user data and associated integrity data, such as error data and address data, etc.) between the memory device and the host, or erase operations used to erase data from the memory device.
[0027] Figure 1 An example system 100 is illustrated that includes a host 105 and a memory device 110. The host 105 may include a host processor, a central processing unit, or one or more other devices, processors, or controllers. The memory device 110 may include a universal flash storage (UFS) device, an embedded MMC (eMMC™) device, or one or more other memory devices. The host 105 and the memory device 110 may communicate using a communication interface (I / F) 115 (e.g., a bidirectional parallel or serial communication interface).
[0028] In an example, the memory device 110 may include a UFS device, and the communication interface 115 may include a serial bidirectional interface, such as defined in one or more Joint Electronic Device Engineering Council (JEDEC) standards (e.g., JEDEC Standard D223D (JESD223D), commonly referred to as JEDEC UFS Host Controller Interface (UFSHCI) 3.0, etc.). In another example, the memory device 110 may include an eMMC TM The device and the communication interface 115 may include a number of parallel bidirectional data lines (e.g., DAT[7:0]) and one or more command lines, such as defined in one or more JEDEC standards (e.g., JEDEC Standard D84-B51 (JESD84-A51), commonly referred to as JEDEC eMMC Standard 5.1, etc.). In other examples, depending on the host 105 and the memory device 110, the memory device 110 may include one or more other memory devices, or the communication interface 115 may include one or more other interfaces. The identified standards are provided merely as example environments in which the described methods and structures may be utilized; however, such methods and structures may be utilized in a variety of environments outside of the identified standards (or any actual or proposed standards).
[0029] Each of the host 105 and the memory device 110 may include a number of receiver or driver circuits configured to send or receive signals through the communication interface 115, or interface circuits, such as a data control unit, a sampling circuit, or other intermediate circuits, configured to process data communicated through the communication interface 115, or otherwise process data received from the communication interface 115 for use by the host 105, the memory device 110, or one or more circuits or devices.
[0030] The memory device 110 may include a memory array (e.g., one or more memory cell arrays, such as a NAND flash array, or one or more other memory arrays), a memory control unit, and, in some instances, an interface circuit between the memory array and the memory control unit. In some embodiments, the memory array may include several memory dies, each having control logic separate from the memory control unit. The memory control unit may include an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or one or more other processing circuits that are arranged or programmed to manage data transfers or operations to, from, or within the memory array.
[0031] Figure 2 Display suitable for use as Figure 1 1 . A block diagram of an example memory device 200 of the memory device 110 in FIG. 1 . According to some embodiments described herein, a memory device may include nonvolatile memory cells having mixed memory cell types integrated in the same integrated circuit (IC) chip. The memory device 200 may include a memory array (or multiple memory arrays) 201 containing memory cells 210 and 285. In the physical structure of the memory device 200, the memory cells 210 and 285 may be arranged vertically (e.g., stacked on top of each other) above a substrate of the memory cell 200 (e.g., a semiconductor substrate of an IC chip including the memory device 200). The memory cells 210 and 285 may include nonvolatile cells. The memory cells 210 and 285 may have different nonvolatile memory cell types. For example, the memory cell 210 may include a floating gate memory cell, a charge trap memory cell, or other types of nonvolatile memory cells. The memory cell 285 may include a ferroelectric memory cell, a phase change memory cell, a resistive memory cell, a conductive bridge memory cell, and a spin transfer torque magnetic random access memory (STT-MRAM) cell, or other types of non-volatile memory cells.
[0032] like Figure 2 , memory cells 210 and 285 are arranged in blocks (memory cell blocks), such as blocks 290 and 291. Each of blocks 290 and 291 may include sub-blocks. For example, block 290 may include sub-blocks 2900 and 290 n , and block 291 may include sub-blocks 2910 and 291 n . Sub-blocks 2900, 290 n , 2910 and 291 n Each of may include a combination of memory cells 210 and 285. As an example, Figure 2Shown is having two blocks 290 and 291 and two sub-blocks in each of the blocks. Memory device 200 may have more than two blocks and more than two sub-blocks in each of the blocks.
[0033] like Figure 2 , memory device 200 may include access lines (which may include word lines) 250 and data lines (which may include bit lines) 270. Access lines 250 may carry signals (e.g., word line signals) WL0 to WLm. Data lines 270 may carry signals (e.g., bit line signals) BL0 to BLn. Memory device 200 may use access lines 250 to selectively access sub-blocks 2900, 2900 of blocks 290 and 291. n , 2910 and 291 n And data line 270 is used to selectively exchange information (eg, data) with memory cells 210 of blocks 290 and 291 .
[0034] The memory device 200 may include an address register 207 to receive address information (e.g., address signals) ADDR on lines (e.g., address lines) 203. The memory device 200 may include row access circuitry 208 and column access circuitry 209 that decode the address information from the address register 207. Based on the decoded address information, the memory device 200 may determine which memory cells 210 in which sub-blocks of blocks 290 and 291 will be accessed during a memory operation. The memory device 200 may perform a read operation to read (e.g., sense) information (e.g., previously stored information) in the memory cells 210, or perform a write (e.g., program) operation to store (e.g., program) information in the memory cells 210. The memory device 200 may use data lines 270 associated with signals BL0 to BLn to provide information to be stored in the memory cells 210, or to obtain information read (e.g., sensed) from the memory cells 210. Memory device 200 may also perform an erase operation to erase information from some or all of memory cells 210 of blocks 290 and 291 .
[0035] The memory device 200 may include a memory control unit 218 (which may include components such as a state machine (e.g., a finite state machine), register circuits, and other components) that is configured to control memory operations (e.g., read, write, and erase operations) of the memory device 200 based on control signals on lines 204. Examples of control signals on lines 204 include one or more clock signals and other signals (e.g., chip enable signal CE#, write enable signal WE#) to indicate which operation (e.g., read, write, or erase operation) the memory device 200 may perform.
[0036] Memory device 200 may include sensing and buffering circuitry 220, which may include components such as sense amplifiers and page buffer circuits (e.g., data latches). Sensing and buffering circuitry 220 may be responsive to signals BL_SEL0 to BL_SELn from column access circuitry 209. Sensing and buffering circuitry 220 may be configured to determine (e.g., by sensing) the value of information read from memory cells 210 of blocks 290 and 291 (e.g., during a read operation) and provide the value of the information to line (e.g., global data line) 275. Sensing and buffering circuitry 220 may also be configured to use the signal on line 275 to determine the value of information to be stored (e.g., programmed) in memory cells 210 of blocks 290 and 291 (e.g., during a write operation) based on the value (e.g., voltage value) of the signal on line 275 (e.g., during a write operation).
[0037] Memory device 200 may include input / output (I / O) circuitry 217 to exchange information between memory cells 210 of blocks 290 and 291 and lines (e.g., I / O lines) 205. Signals DQ0 through DQN on lines 205 may represent information read from or stored in memory cells 210 of blocks 290 and 291. Lines 205 may include nodes within memory device 200 or pins (or solder balls) on a package in which memory device 200 may reside. Other devices external to memory device 200 (e.g., a memory controller, a memory control unit, or a processor) may communicate with memory device 200 through lines 203, 204, and 205.
[0038] The memory device 200 may receive supply voltages, including supply voltages Vcc and Vss. The supply voltage Vss may operate at ground potential (e.g., having a value of approximately zero volts). The supply voltage Vcc may include an external voltage supplied to the memory device 200 from an external power source such as a battery or an alternating current to direct current (AC-DC) converter circuitry.
[0039] Each of the memory cells 210 may be individually or collectively programmed to one or more programming states. For example, a single-level cell (SLC) may represent one of two programming states (e.g., 1 or 0), which represents one bit of data. However, a flash memory cell may also represent one of more than two programming states, thereby allowing a higher density memory to be manufactured without increasing the number of memory cells, because each cell may represent more than one binary digit (e.g., more than one bit). Such cells may be referred to as multi-state memory cells, multi-digit cells, or multi-level cells (MLC). In some examples, an MLC may refer to a memory cell that can store two bits of data per cell (e.g., one of four programming states), a three-level cell (TLC) may refer to a memory cell that can store three bits of data per cell (e.g., one of eight programming states), and a four-level cell (QLC) may store four bits of data per cell. MLC is used herein in its broader context to refer to any memory cell that can store more than one bit of data per cell (i.e., it can represent more than two programming states).
[0040] In another example, each of the memory cells 210 can be programmed to store information representing a value for a plurality of bits, such as one of four possible values "00", "01", "10", and "11" for two bits, one of eight possible values "000", "001", "010", "011", "100", "101", "110", and "111" for three bits, or one of other values for another number of plurality of bits. Cells having the ability to store multiple bits are sometimes referred to as multi-level cells (or multi-state cells).
[0041] The memory device 200 may include a nonvolatile memory device such that the memory cells 210 and 285 may retain information stored thereon when power (e.g., voltages Vcc, Vss, or both) is disconnected from the memory device 200. For example, the memory device 200 may be a flash memory device such as a NAND flash (e.g., 3-dimensional (3-D) NAND) or a NOR flash memory device, or another type of memory device such as a variable resistance memory device (e.g., a phase change memory device or a resistive RAM (random access memory) device). One of ordinary skill in the art may recognize that the memory device 200 may include a nonvolatile memory device such as a phase change memory device or a resistive RAM (random access memory) device. Figure 2 Other components are not shown in the figure so as not to obscure the example embodiments described herein.
[0042] In addition to the erase operation, the memory device 200 can also perform discard and clear operations. The discard operation is a non-secure variation of the erase function. The memory control unit 218 can map virtual memory addresses to physical memory cells of the memory array. The discard operation does not map virtual memory from physical memory. Figure 3It means that it is applicable to Figure 2 2. An example of an area of physical memory in the memory array 201 described above. Areas U1, U2, U3, and U4 are unmapped using a discard operation. Other areas of the memory array contain host data. The difference between discard and erase is the behavior of the memory device. In discard, the memory device is not required to guarantee that the host will not retrieve original data from one or more logical block addresses (LBAs) marked as discard when a read operation is directed to the LBA.
[0043] The clear operation operates on the unmapped address space and results in the removal of all data from the unmapped address space. This is done according to a parameter value set internally to the memory device. This parameter value may be set to reflect that the information will be removed using a vendor defined mechanism (e.g., an erase mechanism). The clear operation may be a very lengthy process, depending on the number of unmapped regions, their size, and their location. To simplify the description, Figure 3 The example of includes only four unmapped areas. Unlike discard operations where the device must ensure that the host does not retrieve the original data from one or more LBAs marked as discarded when a read operation is directed to the LBA, the purge operation requires removing data from the unmap space in a more secure manner. In conventional methods, information is removed by physically erasing the data using a NAND erase operation. An improved method for the purge operation is to use encryption / decryption to ensure that the host has no access to the purge data while eliminating the delay caused by the removal of the data.
[0044] Figure 4 For example, by Figure 1 The memory device 110 described or as relative to Figure 2 1 and 2. The method 400 of operating a memory device to perform a clear operation using the memory device 200 described above is described. At 405, data is received at the memory device for writing to a memory cell of a memory array. At 410, the data to be written is encrypted, and at 415, the encrypted data is programmed into the memory cell. When a read request to read the written encrypted data is received, the encrypted data is read from the memory at 420 and the read encrypted data is decrypted at 425 to be sent to the requesting device (e.g., Figure 1 The encrypted read data is decrypted only when the read data is not stored in the clear area of the memory array.
[0045] If the portion of memory cells being read is contained in the cleared portion of the memory array, decryption is omitted when generating the read data. Encrypted data that cannot be used by the requesting device may be sent to the requesting device. Thus, the new clearing method complies with the definition of a clearing operation by preventing the requesting device from retrieving the original data, but the clearing operation does not involve a lengthy erase operation.
[0046] Figure 5 Suitable for use as Figure 1 The memory device 110 or Figure 2 5. A block diagram of a portion of an example of a memory device of the memory device 200 in FIG. 5. The memory device includes a memory array 501, a memory control unit 518, and a communication interface 515 to operably couple the memory control unit 518 and the host device 505. The memory control unit 518 encrypts write data received via the communication interface. The memory control unit 518 also initiates programming of the physical memory cells with the encrypted data. The memory control unit 518 may include an encryption engine 522. "Engine" refers to a block of logic circuitry of the memory control unit 518 that is dedicated to performing encryption functions. In this way, the encryption of data is deterministic because the number of clock cycles required to encrypt the data is always the same and does not vary with the load on other circuitry (e.g., processing circuitry) of the memory control unit 518.
[0047] Fig. 6A is a diagram showing the write data path 630 Figure 5 501 . Data may be received from a host device at a communication interface into a buffer 526 of a memory control unit. The data is encrypted by an encryption engine 522. The encryption engine may be configured to encrypt the data using symmetric key encryption, such as the Advanced Encryption Standard (AES). In some embodiments, the encryption engine 522 encrypts the data on the fly using a content encryption key (CEK). The memory control unit 518 may include other logic circuitry 528 (e.g., flash control logic circuitry) to write the encrypted data to the memory array 501. The logic circuitry 528 may perform functions related to distributing data among the memory cells.
[0048] For example, in response to a read request from a host application or host device, the memory control unit 518 reads encrypted data from the memory array as part of a read operation. When the encrypted data is read, it is decrypted to generate read data. The memory control unit 518 may include a decryption engine 524 to perform the decryption function. The read data is then provided to the requesting device. Figure 6B is to show the read data path 632 Figure 5In some embodiments, after receiving a read operation from a host device, the memory control unit 518 will read data from the memory array 501 and decrypt the data using the same CEK used to encrypt the data, and send the decrypted data to the host as read data.
[0049] As previously explained, the memory control unit 518 performs the discard operation.The memory control unit 518 may generate a reference structure (eg, a data structure such as a table in memory) to track the unmapped portions of the memory array. Figure 7 is an example of a reference structure inside a memory array that is suitable for use with Figure 2 The example memory array 201 is used with or with Figure 2 518 to track unmapped LBAs when a discard command or other discard indication is received by the memory control unit 518. The entries in the reference structure are Figure 3 To simplify the diagram, only four unmap regions are shown.
[0050] When receiving a memory clear command or other clear indication, the memory control unit 518 repeatedly checks the reference structure of the unmapped area and marks the reference structure entry as cleared according to the memory clear command. This indicates an area of the unmapped memory that the host should not access. When the host attempts to read data from the clear area of the memory array, the memory control unit 518 decrypts the encrypted data. In some embodiments, when the read data is included in the table entry indicating the cleared LBA, the memory control unit 518 transmits the encrypted data via the communication interface. The host does not have decryption information (e.g., CEK), so the encrypted data cannot be used by the host device. In some embodiments, when the portion of the memory cells containing the read data is a cleared portion of the memory cells of the memory array, the memory control unit 518 transmits the designated "clear data" instead of the read data (encrypted or unencrypted) to the host via the communication interface. For example, the memory control unit 518 may transmit "dummy data" that does not represent substantial data (e.g., all zeros, all 1s, or other bit sequences) to the host as designated clear data.
[0051] Figure 8 is to show an alternative write path or read path Figure 510. Block diagram of an example memory device of FIG. 10. This write / read path bypasses the encryption and decryption engine of the memory control unit. Not all data to be written to the memory is encrypted. For example, firmware code and some data management tables are data types that may not be encrypted when written, and this unencrypted memory data does not undergo decryption when read. The memory control unit 518 can exclude data from encryption / decryption by determining the address of the data. For example, the firmware code can be contained in a reserved address space.
[0052] If the encrypted data is cleared, the encrypted data can be provided back to the host device using a direct write / read path to and from the memory cell, or specified clear data can be provided to the host device. Sending encrypted data or specifying clear data still follows the definition of preventing the host from retrieving the clear data. The original data written to the NAND flash is now encrypted, and the memory control unit 518 will not send valid decrypted data to the host. If the host (or an attacker) attempts to bypass the memory control unit and read the data directly from the NAND flash, it will still only be able to read an encrypted copy of the data, which will be unusable.
[0053] The methods and devices described herein improve latency of clear operations.The memory device ensures that a host device does not retrieve usable raw data from one or more LBAs marked as clear when directing a read operation to the LBA without performing an erase operation to remove the data.
[0054] Fig. 9 A block diagram illustrating an example machine 900 that may include, for example, Figure 1 The host device and memory device described herein can perform one or more of the techniques (e.g., methods) discussed herein, such as (for example) the described discard and clear operations. In alternative embodiments, the machine 900 can operate as a standalone device, or can be connected (e.g., networked) to other machines. In a networked deployment, the machine 900 can operate as a server machine, a client machine, or both in a server-client network environment. In an example, the machine 900 can act as a peer machine in a peer-to-peer (P2P) (or other distributed) network environment. The machine 900 can be a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a mobile phone, a network appliance, an IoT device, an automotive system, or any machine capable of executing instructions (sequentially or otherwise) specifying actions to be taken by the machine. In addition, although only a single machine is described, the term "machine" should also be considered to include any collection of machines that individually or collectively execute a set (or multiple sets) of instructions to perform one or more of the methods discussed herein, such as cloud computing, software as a service (SaaS), and other computer cluster configurations.
[0055] As described herein, embodiments and examples may include logic, components, devices, packages, or mechanisms, or may be operated by them. A circuit system is a collection (e.g., a group) of circuits implemented in a tangible entity including hardware (e.g., simple circuits, gates, logic, etc.). Circuit system membership may be flexible over time and with underlying hardware variability. A circuit system includes members that can perform specific tasks individually or in combination when in operation. In an example, the hardware of the circuit system may be designed invariably to perform specific operations (e.g., hardwired). In an example, the hardware of the circuit system may include variably connected physical components (e.g., execution units, transistors, simple circuits, etc.), which include physically modified (e.g., magnetically, electrically, removably placed particles of constant mass, etc.) computer-readable media to encode instructions for specific operations. For example, when connecting physical components, the underlying electrical properties of the hardware composition may change from an insulator to a conductor, or vice versa. Instructions enable participating hardware (e.g., execution units or loading mechanisms) to create components of the circuit system in hardware via variable connections to perform parts of specific tasks when in operation. Thus, when the device is operating, the computer-readable medium is communicatively coupled to other components of the circuit system. In an example, any of the physical components may be used in more than one component of more than one circuit system. For example, under operation, an execution unit may be used in a first circuit in a first circuit system at one point in time and may be reused by a second circuit in the first circuit system or a third circuit in the second circuit system at a different time.
[0056] Machine (eg, computer system) 900 (eg, Figure 1 The host 105, memory device 110, etc.) may include a processing device 902 (e.g., a hardware processor, a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof, such as a memory control unit of the memory device 110, etc.), a main memory 904 (e.g., a read-only memory (ROM), a flash memory, a dynamic random access memory (DRAM) (e.g., a synchronous DRAM (SDRAM) or a Rambus DRAM (RDRAM)), etc.), a static memory 906 (e.g., a flash memory, a static random access memory (SRAM)), etc.), and a data storage system 918, some or all of which may communicate with each other via an interconnection link (e.g., a bus) 930.
[0057] The processing device 902 may represent one or more general purpose processing devices, such as a microprocessor, a central processing unit, or the like. More specifically, the processing device 902 may be a complex instruction set computing (CISC) microprocessor, a reduced instruction set computing (RISC) microprocessor, a very long instruction word (VLIW) microprocessor, or a processor implementing other instruction sets or a processor implementing a combination of instruction sets. The processing device 902 may also be one or more special purpose processing devices, such as an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a digital signal processor (DSP), a network processor, or the like. The processing device 902 may be configured to execute instructions 926 for performing the operations and steps discussed herein. The machine 900 may further include a network interface device 908 to communicate over a network 920.
[0058] The data storage system 918 may include a machine-readable storage medium 924 (also referred to as a computer-readable medium) on which is stored one or more sets of instructions 926 or software embodying any one or more of the methodologies or functions described herein. During execution of the instructions 926 by the machine 900, the instructions 926 may also reside, in whole or in part, within the main memory 904 or within the processing device 902, the main memory 904 and the processing device 902 also constituting machine-readable storage media. The machine-readable storage medium 924, the data storage system 918, or the main memory 904 may correspond to Figure 1 In one embodiment, the instructions 926 include instructions 911 to implement a corresponding clear operation (e.g., Figure 4 functionality of the clear operation).
[0059] Although the machine-readable storage medium 924 is illustrated as a single medium in the example implementation, the term "machine-readable storage medium" should be considered to include a single medium or multiple media storing one or more sets of instructions. The term "machine-readable storage medium" should also be considered to include any medium capable of storing or encoding a set of instructions for execution by a machine and causing the machine to perform any one or more of the methods of the present disclosure. Therefore, the term "machine-readable storage medium" should be considered to include (but not limited to) solid-state memory, optical media, and magnetic media. In an example, a large-capacity machine-readable medium includes a machine-readable medium with multiple particles having a constant (e.g., stationary) mass. Therefore, a large-capacity machine-readable medium is not a transient propagating signal. Specific examples of large-capacity machine-readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.
[0060] The machine 900 may further include a display unit, an alphanumeric input device (e.g., a keyboard), and a user interface (UI) navigation device (e.g., a mouse). In an example, one or more of the display unit, input device, or UI navigation device may be a touch screen display. The machine 900 may include a signal generating device (e.g., a speaker) or one or more sensors, such as a global positioning system (GPS) sensor, a compass, an accelerometer, or one or more other sensors. The machine 900 may include an output controller, such as a serial (e.g., universal serial bus (USB), parallel or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., printer, card reader, etc.).
[0061] Instructions 926 (e.g., software, programs, operating systems (OS), etc.) or other data stored on the data storage device 918 may be accessed by the main memory 904 for use by the processing device 902. The main memory 904 (e.g., DRAM) is typically fast but volatile, and thus, unlike the storage type of the data storage device 918 (e.g., SSD), the data storage device 918 is suitable for long-term storage, including storage in a "power-off" condition. Instructions 926 or data used by a user or machine 900 are typically loaded into the main memory 904 for use by the processing device 902. When the main memory 904 is full, virtual space from the data storage device 918 may be allocated to supplement the main memory 904; however, since the data storage device 918 device is typically slower than the main memory 904, and the write speed is typically at least two times slower than the read speed, the use of virtual memory may greatly reduce the user experience due to memory device latency (compared to the main memory 904, such as DRAM). In addition, using the data storage device 918 for virtual memory may greatly reduce the usable life of the data storage device 918.
[0062] Compared with virtual memory, virtual memory compression (for example, Linux TM The kernel feature "ZRAM") uses portions of memory stored as compressed blocks to avoid paging to the data storage device 918. Paging occurs in compressed blocks until the data needs to be written to the data storage device 918. Virtual memory compression increases the available size of the main memory 904 while reducing the wear and tear on the data storage device 918.
[0063] Memory devices optimized for mobile electronic devices or mobile storage traditionally include MMC solid-state storage devices (e.g., micro secure digital (microSDTM) cards, etc.). MMC devices include several parallel interfaces (e.g., 8-bit parallel interfaces) with a host (e.g., a host device), and are typically removable and separate components from the host. In contrast, eMMCTM devices are attached to a circuit board and are considered to be components of the host, with read speeds comparable to SSD devices based on Serial ATATM (Serial AT (Advanced Technology) Attachment or SATA). However, the demand for mobile device performance continues to increase, such as to fully enable virtual devices or augmented reality devices, take advantage of increasing network speeds, etc. In response to this demand, memory devices have been transformed from parallel communication interfaces to serial communication interfaces. Universal Flash Storage (UFS) devices (including controllers and firmware) use a low voltage differential signal (LVDS) serial interface with a dedicated read / write path to communicate with the host, thereby further improving read / write speeds.
[0064] The instructions 924 may further be transmitted or received over the network 920 using a transmission medium via the network interface device 908 using any of a number of transmission protocols (e.g., frame relay, Internet Protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), a mobile telephone network (e.g., a cellular network), a plain old telephone (POTS) network, and a wireless data network (e.g., the Institute of Electrical and Electronics Engineers (IEEE) 802.11 series of standards, known as IEEE 802.16 series of standards, known as ), IEEE 802.15.4 family of standards, peer-to-peer (P2P) networks, etc. In an example, the network interface device 908 may include one or more physical jacks (e.g., Ethernet, coaxial, or telephone jacks) or one or more antennas to connect to the network 920. In an example, the network interface device 908 may include multiple antennas to communicate wirelessly using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) technology. The term "transmission media" should be taken to include any intangible medium capable of storing, encoding, or carrying instructions executed by the machine 900, and includes digital or analog communication signals or other intangible media to facilitate communication of such software.
[0065] The above detailed description includes references to the drawings that form a part of the detailed description. The drawings show, by way of illustration, specific embodiments in which the present invention can be practiced. These embodiments are also referred to herein as "examples". Such examples may include elements other than those shown or described. However, the inventors also contemplate examples in which only those elements shown or described are provided. In addition, the inventors also contemplate examples using any combination or arrangement of those elements shown or described (or one or more aspects thereof), with respect to specific examples (or one or more aspects thereof), or with respect to other examples shown or described herein (or one or more aspects thereof).
[0066] In this document, the term "one" includes one or more than one as commonly used in patent documents, independent of any other examples or usages of "at least one" or "one or more". In this document, unless otherwise specified, the term "or" is used to refer to a non-exclusive or, so that "A or B" may include "A but not B", "B but not A" and "A and B", unless otherwise indicated. In the appended claims, the terms "including" and "in which" are used as the common English equivalents of the corresponding terms "including" and "wherein". In addition, in the appended claims, the terms "including" and "including" are open. Systems, devices, articles or processes that include elements other than those listed after this term in the claims are still considered to fall within the scope of the claims. In addition, in the appended claims, the terms "first", "second" and "third" etc. are used only as labels, and it is not desired to impose numerical requirements on their objects.
[0067] In various examples, the components, controllers, processors, units, engines, or tables described herein may include, among other things, physical circuitry or firmware stored on a physical device. As used herein, "processor" means any type of computing circuit, such as, but not limited to, a microprocessor, a microcontroller, a graphics processor, a digital signal processor (DSP), or any other type of processor or processing circuit, including groups of processors or multi-core devices.
[0068] As used herein, operating a memory cell includes reading from the memory cell, writing to the memory cell, or erasing the memory cell. The operation of placing a memory cell in a desired state is referred to herein as "programming" and may include writing to a memory cell or erasing from a memory cell (e.g., a memory cell may be programmed to an erased state).
[0069] According to one or more embodiments of the present disclosure, a memory controller (e.g., a processor, a controller, firmware, etc.) located inside or outside a memory device is capable of determining (e.g., selecting, setting, adjusting, calculating, changing, clearing, communicating, adapting, deriving, defining, utilizing, modifying, applying, etc.) a certain number of wear cycles or wear states (e.g., recording wear cycles, counting operations of the memory device (when they occur), tracking operations of the memory device (when it is started), evaluating memory device characteristics corresponding to the wear state, etc.)
[0070] According to one or more embodiments of the present disclosure, a memory access device may be configured to provide wear cycle information to the memory device with each memory operation. The memory device control circuit system (e.g., control logic) may be programmed to compensate for memory device performance changes corresponding to the wear cycle information. The memory device may receive the wear cycle information and determine one or more operating parameters (e.g., values, characteristics) in response to the wear cycle information.
[0071] The method examples described herein may be at least partially machine, device, or computer-implemented. Some examples may include a computer-readable medium, a device-readable medium, or a machine-readable medium encoded with instructions that are operable to configure an electronic device to perform a method as described in the above examples. Implementations of such methods may include code, such as microcode, assembly language code, high-level language code, or the like. Such code may include computer-readable instructions for performing various methods. The code may form part of a computer program product. In addition, the code may be tangibly stored on one or more volatile or non-volatile tangible computer-readable media, such as during execution or at other times. Examples of these tangible computer-readable media may include, but are not limited to, a hard disk, a removable disk, a removable optical disk (e.g., an optical disk and a digital video disk), a cassette, a memory card or stick, a random access memory (RAM), a read-only memory (ROM), a solid-state drive (SSD), a universal flash storage (UFS) device, an embedded MMC (eMMC) device, and the like.
[0072] Additional description and examples
[0073] Example 1 includes subject matter (e.g., a memory device) comprising: a memory array including memory cells; a communication interface to a host device; a memory control unit operably coupled to the memory array and the communication interface. The memory control unit is configured to: encrypt write data received via the communication interface to generate encrypted data; program a portion of the memory cells of the memory array with the encrypted data; read the encrypted data from a portion of the memory cells in response to a memory read request; decrypt the read encrypted data to generate read data only for a portion of the read encrypted data that is not stored in a clear area of the memory array.
[0074] In Example 2, the subject matter of Example 1 optionally includes a memory control unit configured to transmit encrypted data via the communication interface for read encrypted data stored in the clear area of the memory array.
[0075] In Example 3, the subject matter of one or both of Examples 1 and 2 optionally includes a memory control unit configured to transmit designated clear data via the communication interface in place of the read encrypted data stored in the clear area of the memory array.
[0076] In Example 4, the subject matter of one or any combination of Examples 1 to 3 optionally includes a memory control unit configured to: map a virtual memory address to the memory cells of the memory array; unmap a portion of the memory cells of the memory array based on a memory discard indication received via the communication interface; and change the unmapped portion of the memory cells to a cleared portion of the memory cells based on a memory clear indication received via the communication interface.
[0077] In Example 5, the subject matter of one or any combination of Examples 1 to 4 optionally includes a memory control unit configured to generate a reference structure indicating a cleared portion of a memory cell; and when the reference structure indicates that an address of the read encrypted data is included in the cleared portion of the memory cell, omitting decrypting the read encrypted data.
[0078] In Example 6, the subject matter of Example 5 optionally includes a memory control unit configured to generate a reference structure of an unmapped portion of the memory cell based on a memory discard indication received via the communication interface; receive a memory clear indication via the communication interface; and generate the reference structure indicating the cleared portion of the memory cell by indicating the unmapped portion of the memory cell as the cleared portion of the memory cell based on the memory clear indication.
[0079] In Example 7, the subject matter of one or any combination of Examples 1-6 optionally includes a memory control unit configured to exclude from encryption specified types of write data received via the communication interface.
[0080] In Example 8, the subject matter of one or any combination of Examples 1-7 optionally includes a memory control unit configured to exclude data to be written to a specified memory address from encryption.
[0081] In Example 9, the subject matter of one or any combination of Examples 1-8 optionally includes a memory array having NAND-type flash memory cells.
[0082] Example 10 includes subject matter such as a method of programming multi-level memory cells of a memory array, or may optionally be combined with one or any combination of Examples 1 to 9 to include such subject matter, comprising: receiving data to be written to a portion of memory cells of a memory array of the memory; encrypting the data to be written; programming the memory cells with the encrypted data; reading the encrypted data from the memory cells; decrypting the read encrypted data to produce read decrypted data only for the portion of the read encrypted data that is not stored in a clear area of the memory array.
[0083] In Example 11, the subject matter of Example 10 optionally includes receiving data to be written from a host device, and transmitting encrypted data to the host device as the read data that is part of the read encrypted data stored in the cleared portion of the memory array.
[0084] In Example 12, the subject matter of Example 10 optionally includes receiving data to be written from a host device, and transmitting designated clear data to the host device in place of the read encrypted data stored in the clear area of the memory array.
[0085] In Example 13, the subject matter of one or any combination of Examples 10-12 optionally includes mapping virtual memory addresses to memory cells of the memory array; unmapping a portion of the memory cells of the memory array in response to a memory discard command; and including the unmapped portion of the memory cells in the clear region of the memory array in response to a memory clear command.
[0086] In Example 14, the subject matter of one or any combination of Examples 10-13 optionally includes generating a table indicating a cleared portion of memory cells; and when the table indicates that an address of the read data is included in the cleared portion of memory cells, omitting the decrypting.
[0087] In Example 15, the subject matter of Example 14 optionally includes: generating a table of unmapped portions of the memory cells in response to a memory discard command; and changing the unmapped portions to clear portions in response to a memory purge command.
[0088] In Example 16, the subject matter of one or any combination of Examples 10-15 optionally includes encrypting only specified types of data to be written, and excluding different types of data from the encryption.
[0089] Example 17 includes subject matter, such as a memory system, or can be optionally combined with one or more of Examples 1-16 to include such subject matter, comprising a host device and a memory device. The memory device includes a memory control unit configured to: receive data to be written to a portion of memory cells of a memory array of the memory device; encrypt the data to be written; program the memory cells with the encrypted data; read the encrypted data from the portion of the memory cells; decrypt the read encrypted data to generate read decrypted data only for the portion of the read encrypted data not stored in the clear area of the memory array; and transmit the read decrypted data to the host device.
[0090] In Example 18, the subject matter of Example 17 optionally includes a memory control unit configured to receive data to be written from the host device and to transmit encrypted data to the host device as the read encrypted data.
[0091] In Example 19, the subject matter of one or both of Examples 17 and 18 optionally includes a memory control unit configured to receive the data to be written from the host device and to transmit designated clear data to the host device in place of the read encrypted data stored in the clear area of the memory array.
[0092] In Example 20, the subject matter of one or any combination of Examples 17-19 optionally includes a memory control unit configured to: map a virtual memory address to a memory cell of the memory array; unmap a portion of the memory cells of the memory array in response to receiving a memory discard command; and change the unmapped portion of the memory cells to a cleared portion of the memory cells in response to receiving a memory clear command.
[0093] These non-limiting examples can be combined in any arrangement or combination. The above description is intended to be illustrative and not restrictive. For example, the examples described above (or one or more aspects thereof) can be used in combination with each other. After reviewing the above description, other embodiments can be used by a person of ordinary skill in the art, for example. It should be understood when submitting that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the above specific embodiments, various features can be grouped together to simplify the present disclosure. This should not be interpreted as wishing that the disclosed features are not claimed to be essential for any claim. Instead, the subject matter of the invention may be less than all the features of a specific disclosed embodiment. Therefore, the attached claims are hereby incorporated into the specific embodiments, wherein each claim is independently used as a separate embodiment, and it is expected that such embodiments can be combined with each other in various combinations or arrangements. The scope of the present invention should be determined with reference to the attached claims and the full range of equivalents to which the claims are assigned.
Claims
1. A memory device, include: a memory array comprising memory cells; a communications interface to a host device; a memory control unit operatively coupled to the memory array and the communication interface and configured to: encrypting write data received via the communication interface to generate encrypted data; programming selected memory cells of the memory array with the encrypted data; designating one or more regions of the memory array as one or more purge regions of the memory array in response to a memory purge indication received via the communication interface; reading the encrypted data from the memory unit in response to a memory read request; decrypting the read encrypted data to generate read decrypted data when the memory read request is for data not stored in the one or more clear regions of the memory array; and When the read request is for data stored in the one or more clear areas of the memory array, decryption of the read encrypted data is omitted.
2. The memory device of claim 1, wherein the memory control unit is configured to transmit encrypted data via the communication interface for the portion of the read encrypted data stored in the clear area of the memory array.
3. The memory device of claim 1, wherein the memory control unit is configured to transmit designated clear data via the communication interface in place of read encrypted data stored in the clear area of the memory array.
4. The memory device of claim 1 , wherein the memory control unit is configured to: mapping a virtual memory address to the memory cell of the memory array; unmapping a portion of the memory cells of the memory array in accordance with a memory discard indication received via the communication interface; and The unmapped portion of the memory unit is changed to a cleared portion of the memory unit in accordance with a memory clear indication received via the communication interface.
5. The memory device of claim 1 , wherein the memory control unit is configured to: generating a reference structure indicative of an erased portion of a memory cell; and When the reference structure indicates that the address of the read encrypted data is included in the cleared portion of the memory cell, decrypting the read encrypted data is omitted.
6. The memory device of claim 5, wherein the memory control unit is configured to: generating a reference structure of an unmapped portion of the memory unit in response to a memory discard indication received via the communication interface; receiving a memory clear instruction via the communication interface; and The reference structure indicating the cleared portion of the memory cell is generated by indicating the unmapped portion of the memory cell as the cleared portion of the memory cell according to the memory clear indication.
7. The memory device of claim 1, wherein the memory control unit is configured to exclude from encryption a specified type of write data received via the communication interface.
8. The memory device of claim 1, wherein the memory control unit is configured to exclude data to be written to a specified memory address from encryption.
9. The memory device of claim 1, wherein the memory cells comprise NAND-type flash memory cells.
10. A method for operating a memory, the method include: receiving data to be written to a portion of memory cells of a memory array of the memory; encrypting the data to be written; programming the memory cells with encrypted data; designating one or more regions of the memory array as clear regions of the memory array according to a memory clear command; reading the encrypted data from the memory unit in response to a memory read request; decrypting the read encrypted data to generate read decrypted data when the memory read request is for data not stored in a clear area of the memory array; and When the memory read request is for data stored in the clear area of the memory array, decryption of the read encrypted data is omitted.
11. The method of claim 10, wherein receiving data to be written comprises receiving data from a host device, and the method further comprises transmitting encrypted data to the host device as the read encrypted data that is part of the read encrypted data stored in the clear area of the memory array.
12. The method of claim 10, wherein receiving data to be written comprises receiving data from a host device, and the method further comprises transmitting designated clear data to the host device in place of the read encrypted data stored in the clear area of the memory array.
13. The method according to claim 10, comprising: mapping virtual memory addresses to memory cells of the memory array; unmapping the portion of the memory cells of the memory array in response to a memory discard command; and An unmapped portion of the memory cells is included in the clear region of the memory array in response to a memory clear command.
14. The method according to claim 10, comprising: generating a reference structure indicative of an erased portion of a memory cell; and When the reference structure indicates that the address of the read data is contained in the cleared portion of the memory cell, the decryption is omitted.
15. The method according to claim 14, comprising: wherein generating the reference structure indicating a cleared portion of memory cells comprises generating a reference structure indicating an unmapped portion of the memory cells in response to a memory discard command; and The unmap portion is changed to a clear portion in response to a memory clear command.
16. The method of claim 10, wherein encrypting data to be written comprises encrypting only data of a specified type to be written, and excluding data of a different type from the encryption.
17. A memory system, wherein include: Host device; and A memory device, the memory device comprising a memory control unit configured to: receiving, from the host device, data to be written to a portion of memory cells of a memory array of the memory device; encrypting the data to be written; programming the memory cells with encrypted data; designating one or more regions of the memory array as one or more clear regions of the memory array; reading the encrypted data from the portion of the memory cell in response to a read operation; and decrypting the read encrypted data to generate read decrypted data when the memory read operation is for data not stored in one or more clear regions of the memory array; transmitting the read decrypted data to the host device; and When the read request is for data stored in the one or more clear areas of the memory array, the decryption of the read encrypted data is omitted.
18. The memory system of claim 17, wherein the memory control unit is configured to receive the data to be written from the host device and transmit encrypted data to the host device as the read encrypted data.
19. The memory system of claim 17, wherein the memory control unit is configured to receive the data to be written from the host device and to transmit designated clear data to the host device in place of the read encrypted data stored in the clear area of the memory array.
20. The memory system of claim 17, wherein the memory control unit is configured to: mapping virtual memory addresses to memory cells of the memory array; unmapping the portion of the memory cells of the memory array in response to receiving a memory discard command; and The unmapped portion of the memory cell is changed to a cleared portion of the memory cell in response to receiving a memory clear command.
Citation Information
Patent Citations
Flash memory-interface
CN102103566A
Memory instruction including parameter to affect operating condition of memory
CN102543154A
Apparatuses and methods for parallel writing to multiple memory device locations
CN107408405A
Memory controller, nonvolatile memory system, and operating method thereof
US20180052768A1
