Control circuitry for scheduling aspects of use-based interference mitigation based on different external commands
By receiving separate external commands to independently perform internal read and write operations in the memory device, the problem of operation time limitation in the prior art is solved and the performance of the memory device is improved.
Patent Information
- Application Number
- CN202410660610.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2024-04-22
- Filing Date
- 2024-05-27
- Publication Date
- 2024-12-03
AI Technical Summary
When existing memory devices mitigate usage-based interference, internal read and write operations are performed back-to-back, resulting in limited time to correct errors, and pre-charge operation delay increases external pre-charge time and reduces overall performance.
By receiving two external commands separated in time, an internal read command is generated based on the first command, and an internal write command is generated based on the second command, allowing error correction and other tasks to be performed before the write operation, and within the pre-charge time Perform internal write operations to reduce pre-charge time.
The implementation of error correction and other tasks before the internal write operation is achieved, reducing external precharge time and improving the overall performance of the memory device.
Smart Images

Figure CN119065593A_ABST
Abstract
Description
[0001] CROSS REFERENCE TO RELATED APPLICATIONS
[0002] This application claims the benefit of U.S. Provisional Patent Application Serial No. 63 / 504,961, filed on May 30, 2023, the entire disclosure of which is incorporated herein by reference. Technical Field
[0003] The present disclosure relates generally to memory devices, and more particularly, to apparatus and methods for scheduling aspects of usage-based interference mitigation based on different external commands. Background Art
[0004] Computers, smartphones, and other electronic devices rely on processors and memory. The processor executes code based on data to run applications and provide features to users. The processor obtains the code and data from the memory. The memory in an electronic device may include volatile memory (e.g., random access memory (RAM)) and non-volatile memory (e.g., flash memory). Like the power of the processor, the power of the memory may affect the performance of the electronic device. As processors that execute code faster are developed and as applications operate on larger and larger data sets requiring larger memory, this performance impact may increase. Summary of the invention
[0005] One of the embodiments of the present disclosure provides an apparatus comprising a memory device. The memory device comprises: at least one memory bank comprising memory cells, wherein a subset of the memory cells is configured to store data associated with usage-based interference; and a circuit system configured to mitigate usage-based interference within the memory bank based on the data. The memory device is configured to: receive two commands separated in time by a timing offset from a memory controller; generate an internal read command based on a first command of the two commands to cause the memory device to read the data from the subset of the memory cells; and generate an internal write command based on a second command of the two commands to cause the memory device to write modified data generated by the circuit system to the subset of the memory cells.
[0006] Another of the embodiments of the present disclosure provides an apparatus comprising a memory device. The memory device comprises a plurality of memory cells arranged in a row, a subset of the memory cells being configured to store data associated with usage-based interference in the row. The memory device is configured to: receive an activate command from a memory controller; and read the data from the subset of the memory cells based on the activate command.
[0007] Another of the embodiments of the present disclosure provides a method, comprising: receiving a first command by a memory device from a memory controller; executing, by the memory device, an internal read command associated with usage-based interference mitigation based on the first command; receiving a second command by the memory device from the memory controller; and executing, by the memory device, an internal write command associated with usage-based interference mitigation based on the second command. BRIEF DESCRIPTION OF THE DRAWINGS
[0008] The following drawings describe apparatus and techniques for scheduling usage-based interference mitigation based on different external commands. The same numbers are used throughout the drawings to refer to similar features and components:
[0009] Figure 1 An example operating environment illustrating control circuitry that may implement aspects of scheduling usage-based interference mitigation;
[0010] Figure 2 An example computing system illustrating control circuitry that may implement aspects of scheduling usage-based interference mitigation;
[0011] Figure 3 An example memory device illustrating aspects of schedulable usage-based interference mitigation is provided;
[0012] Figure 4 describes an example memory array that is divided into subsets to store different types of data;
[0013] Figure 5 Describing example external and internal commands for scheduling aspects of usage-based interference mitigation;
[0014] Figure 6 illustrating an example sequence of memory operations in which aspects of usage-based interference mitigation are implemented;
[0015] Figure 7 illustrating another example sequence of memory operations in which aspects of usage-based interference mitigation are implemented; and
[0016] Figure 8 , 9 and 10 illustrate example methods for scheduling aspects of usage-based interference mitigation based on different external commands. DETAILED DESCRIPTION
[0017] Overview
[0018] Processors and memory work together to provide features to users of computers and other electronic devices. As processors and memory operate together faster in a complementary manner, electronic devices can provide enhanced features, such as high-resolution graphics and artificial intelligence (AI) analysis. Some applications, such as applications for financial services, medical devices, and advanced driver assistance systems (ADAS), may also require more reliable memory. These applications use increasingly reliable memory to limit errors in financial transactions, medical decisions, and object recognition. However, in some implementations, more reliable memory may sacrifice bit density, power efficiency, and simplicity.
[0019] In order to meet the demand for physically smaller memories, memory devices can be designed to have higher chip density. However, increased chip density can increase electromagnetic coupling (e.g., capacitive coupling) between adjacent or close rows of memory cells, which is at least partially due to the shrinking distance between these rows. With this undesirable coupling, the activation (or charging) of a first row of memory cells can sometimes have a negative impact on a nearby second row of memory cells. In particular, the activation of the first row can produce interference or crosstalk, which causes the second row to experience voltage fluctuations. In some examples, this voltage fluctuation can cause the sense amplifier to incorrectly determine the state (or value) of the memory cell in the second row. Consider an example in which the state of the memory cell in the second row is "1". In this example, the voltage fluctuation can cause the sense amplifier to incorrectly determine the state of the memory cell as "0" instead of "1". If not curbed, this interference can cause memory errors or data loss within the memory device.
[0020] In some cases, a particular row of memory cells is repeatedly activated, either accidentally or intentionally (sometimes maliciously). For example, consider a memory cell in row R that is repeatedly activated, causing one or more memory cells in neighboring rows (e.g., within row R+1, row R+2, row R-1, and / or row R-2) to change state. This effect is known as usage-based disturbance. The occurrence of usage-based disturbance can result in the contents within the affected memory row being corrupted or altered.
[0021] Some memory devices include usage-based interference circuitry that monitors and mitigates usage-based interference within rows of the memory device. The usage-based interference circuitry may include at least one counter circuit for detecting conditions associated with usage-based interference. A subset of memory cells in one or more rows of the memory device may store an activation count referenced by the counter circuit. Using the activation count, the usage-based interference circuitry may monitor (e.g., track) the number of times and / or frequency that one or more rows of the memory device are activated. When a row of the memory device is activated, the memory device reads data from the row and the counter circuit increments the activation count. In some examples, the usage-based interference circuitry may selectively cause one or more rows within the memory device to be refreshed based on the activation count of the row exceeding a threshold. The usage-based interference circuitry may also detect and / or correct bit errors that may be caused by usage-based interference.
[0022] According to some protocols, the memory controller sequentially transmits a precharge command to the memory device before transmitting an activation command associated with a normal read / write operation. The precharge command is separated from the activation command by a timing offset. The precharge command causes the memory device to deactivate or close the currently open row, thereby allowing a new row to be prepared for the read / write operation. After transmitting the precharge command, the memory controller waits for the precharge time and thereafter transmits the activation command associated with the next operation. The activation command is essentially a row access command that causes the memory device to open a new row. The precharge time represents the timing offset or delay between the transmission of the precharge command and the transmission of the activation command. The precharge time is necessary to allow the memory device to complete the deactivation of the open row so that a new row can be opened. Because the activation command causes the memory device to open a new row, the memory device performs a read / write operation in the currently open row during the precharge time before receiving the activation command.
[0023] In some existing usage-based interference mitigation techniques, in response to a precharge command, a usage-based interference mitigation circuit system sequentially performs an internal read operation and an internal write operation. The internal read operation and the internal write operation are different from normal read / write operations. During the internal read operation, the usage-based interference circuit system reads data from the row. During the internal write operation, the usage-based interference circuit system increments the activation count stored in the activation row. Because the activation command causes the memory device to open a new row, the time available for performing usage-based interference mitigation is limited to the precharge time. According to the existing method, in order to allow the memory device to complete the internal read and internal write operations within the precharge time, the two operations are performed back to back without any timing offset between the internal read operation and the internal write operation. For example, in response to a precharge command, the usage-based interference mitigation circuit system generates an internal read command, completes the internal read operation, and immediately thereafter generates an internal write command and completes the internal write operation.
[0024] A disadvantage of the existing approach is that because the internal read and internal write operations are performed back-to-back, there is a limited time to allow additional operations to mitigate usage-based interference before the internal write operation is performed. For example, the internal read operation may require 5 nanoseconds (ns), which may not be sufficient to correct errors caused by usage-based interference.
[0025] Another disadvantage of the prior art methods is that the precharge operation is delayed relative to the precharge command so that the internal read and internal write operations can be performed. The effect of this delay is that the external precharge time, which represents the timing offset between the precharge command and the activate command, increases, thus degrading the overall performance of the memory device.
[0026] In order to solve this and other problems about interference based on use, this document describes a control circuit system that supports interference mitigation based on use in a memory device. Compared with the existing interference mitigation technology based on use, which usually generates both internal read commands and internal write commands based on the same command, the control circuit system described in this document generates an internal read command based on a first command, and generates an internal write command based on a second command. The first and second commands are external commands received from a memory controller. In some example embodiments, the first command is an activation command and / or the second command is a precharge command. In some example embodiments, the internal read operation performed in response to the internal read command and the internal write operation performed in response to the internal write command are not performed back to back. Therefore, there is a timing offset between the two operations, which allows error correction and other tasks associated with interference mitigation based on use to be performed before the internal write operation. In addition, because the internal read operation is not performed during the external precharge time, the time of external precharge can be reduced compared to the existing method, thereby improving the overall performance of the memory device. In addition, because the internal read operation is not performed during the external precharge time, additional time can be allocated for performing the internal write operation during the external precharge time.
[0027] Instance operating environment
[0028] Figure 1 An example operating environment of an apparatus 102 including a control circuit system that may implement aspects of scheduling usage-based interference mitigation is generally illustrated at 100. The apparatus 102 may include various types of electronic devices, including an Internet of Things (IoT) device 102-1, a tablet device 102-2, a smartphone 102-3, a notebook computer 102-4, a passenger car 102-5, a server computer 102-6, and a server cluster 102-7, which may be part of a cloud computing infrastructure, a data center, or a portion thereof (e.g., a printed circuit board (PCB)). Other examples of the apparatus 102 include a wearable device (e.g., a smart watch or smart glasses), an entertainment device (e.g., a set-top box, a video dongle, a smart TV, a gaming device), a desktop computer, a motherboard, a server blade, a consumer appliance, a vehicle, a drone, an industrial equipment, a security device, or a sensor or electronic components thereof. Each type of apparatus may include one or more components to provide computing functionality or features.
[0029] In an example implementation, the apparatus 102 may include at least one host device 104, at least one interconnect 106, and at least one memory device 108. The host device 104 may include at least one processor 110, at least one cache memory 112, and a memory controller 114. The memory device 108, which may also be implemented with a memory module, may include, for example, a dynamic random access memory (DRAM) die or module (e.g., a low power double data rate synchronous DRAM (LPDDR SDRAM)). The DRAM die or module may include a three-dimensional (3D) stacked DRAM device, which may be a high bandwidth memory (HBM) device or a hybrid memory cube (HMC) device. The memory device 108 may operate as a main memory for the apparatus 102. Although not illustrated, the apparatus 102 may also include a storage memory. The storage memory may include, for example, a storage class memory device (e.g., a flash memory, a hard disk drive, a solid state drive, a phase change memory (PCM), or a 3D XPoint TM of memory).
[0030] Processor 110 is operatively coupled to cache 112, which is operatively coupled to memory controller 114. Processor 110 is also coupled directly or indirectly to memory controller 114. Host device 104 may include other components to form, for example, a system on a chip (SoC). Processor 110 may include a general purpose processor, a central processing unit, a graphics processing unit (GPU), a neural network engine or accelerator, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) integrated circuit (IC), or a communication processor (e.g., a modem or baseband processor).
[0031] In operation, the memory controller 114 may provide a high-level or logical interface between the processor 110 and at least one memory (e.g., an external memory). The memory controller 114 may be implemented with any of a variety of suitable memory controllers (e.g., a double data rate (DDR) memory controller that can process requests for data stored on the memory device 108). Although not shown, the host device 104 may include a physical interface (PHY) that transfers data between the memory controller 114 and the memory device 108 through the interconnect 106. For example, the physical interface may be an interface compatible with the DDR PHY interface (DFI) group interface protocol. For example, the memory controller 114 may receive a memory request from the processor 110 and provide the memory request to the external memory with appropriate formatting, timing, and reordering. The memory controller 114 may also forward responses to the memory requests received from the external memory to the processor 110.
[0032] Host device 104 is operatively coupled to memory device 108 via interconnect 106. In some examples, memory device 108 is connected to host device 104 via interconnect 106 with an intermediate buffer or cache. Memory device 108 may be operatively coupled to storage memory (not shown). Host device 104 may also be coupled directly or indirectly to memory device 108 and storage memory via interconnect 106. Interconnect 106 and other interconnects ( Figure 1 The interconnect 106 may transmit data between two or more components of the apparatus 102 (not illustrated). Examples of the interconnect 106 include a bus (e.g., a unidirectional or bidirectional bus), a switching fabric, or one or more conductors that carry voltage or current signals. The interconnect 106 may propagate one or more communications 116 between the host device 104 and the memory device 108. For example, the host device 104 may transmit a memory request to the memory device 108 via the interconnect 106. In addition, the memory device 108 may transmit a corresponding memory response to the host device 104 via the interconnect 106.
[0033] The illustrated components of the apparatus 102 represent an example architecture having a hierarchical memory system. The hierarchical memory system may include different levels of memory, with each level having memory having different speeds or capacities. As illustrated, the cache memory 112 logically couples the processor 110 to the memory device 108. In the illustrated implementation, the cache memory 112 is at a higher level than the memory device 108. The storage memory, in turn, may be at a lower level than the main memory (e.g., the memory device 108). The memory at the lower hierarchical level has a reduced speed but an increased capacity relative to the memory at the higher hierarchical level.
[0034] Device 102 may be implemented in various ways with more, fewer, or different components. For example, host device 104 may include multiple cache memories (e.g., including multiple levels of cache memories) or no cache memories. In other embodiments, host device 104 may omit processor 110 or memory controller 114. Memory (e.g., memory device 108) may have an "internal" or "local" cache memory. As another example, device 102 may include a cache memory between interconnect 106 and memory device 108. Computer engineers may also include any of the illustrated components in a distributed or shared memory system.
[0035] Computer engineers can implement host device 104 and various memories in a variety of ways. In some cases, host device 104 and memory device 108 can be placed on or physically supported by a printed circuit board (e.g., a rigid or flexible motherboard). Host device 104 and memory device 108 can additionally be integrated together on an integrated circuit, or fabricated on separate integrated circuits and packaged together. Memory device 108 can also be coupled to multiple host devices 104 via one or more interconnects 106, and can respond to memory requests from two or more host devices 104. Each host device 104 can include a corresponding memory controller 114, or multiple host devices 104 can share a memory controller 114. This document references Figure 1 An example computing system architecture is described having at least one host device 104 coupled to a memory device 108 .
[0036] Two or more memory components (e.g., modules, dies, banks, or groups of banks) may share an electrical path or coupling of the interconnect 106. The interconnect 106 may include at least one command and address bus (CA bus) and at least one data bus (DQ bus). The command and address bus may transmit addresses and commands from the memory controller 114 of the host device 104 to the memory device 108, which may eliminate the propagation of data. The data bus may propagate data between the memory controller 114 and the memory device 108. The memory device 108 may also be implemented as any suitable memory, including, but not limited to, DRAM, SDRAM, three-dimensional (3D) stacked DRAM, DDR memory, or LPDDR memory (e.g., LPDDR DRAM or LPDDR SDRAM).
[0037] Memory device 108 may form at least part of a main memory of apparatus 102. However, memory device 108 may form at least part of a cache memory, storage memory, or system-on-chip of apparatus 102. Memory device 108 includes control circuitry 120 and usage-based interference circuitry 122 (UBD circuitry 122). Control circuitry 120 may include various components that memory device 108 may use to perform various operations, such as communicating with other devices, managing memory performance, performing refresh operations (e.g., self-refresh operations or auto-refresh operations), and supporting usage-based interference mitigation.
[0038] To support usage-based interference mitigation, the control circuit system 120 generates internal commands based on external commands received from the memory controller 114. In some example embodiments, the control circuit system 120 generates an internal read command based on an external command (also referred to as a first command) and generates an internal write command based on another external command (also referred to as a second command). Thus, the internal read command and the internal write command are generated in response to different external commands. In some example embodiments, the first command is an activate command and / or the second command is a precharge command. These internal commands are executed to support usage-based interference mitigation in the memory device 108. Different external commands may be scheduled sequentially or may be further separated by another external command (e.g., a read or write command). By scheduling internal read and write commands across multiple external commands, the usage-based interference circuit system may perform aspects of usage-based interference mitigation over a longer period of time than the shorter amount of time available when scheduling these commands based on the same external command.
[0039] The usage-based interference circuitry 122 is configured to monitor and mitigate usage-based interference in the memory device 108. In some example implementations, the usage-based interference circuitry 122 includes at least one counter circuit for detecting conditions associated with usage-based interference, at least one queue for mitigating usage-based interference, and at least one error correction code (ECC) circuit for detecting and / or correcting bit errors. The usage-based interference circuitry 122 may be implemented using software, firmware, hardware, fixed logic circuitry, or a combination thereof.
[0040] In some example implementations, the usage-based interference circuitry 122 may include logic to increment an activation count associated with a row of memory cells that are activated. The usage-based interference circuitry 122 may include a dedicated counter circuit ( Figure 1 The usage-based perturbation circuitry 122 may monitor (e.g., track) the number of times and / or frequency that one or more rows of the memory device are activated. When a row of memory devices is activated, the usage-based perturbation circuitry 122 reads data (e.g., an activation count) from the row and causes the memory device 108 to increment a counter circuit. The counter circuit stores an activation count representing the number of times the row has been activated. In some examples, the usage-based perturbation circuitry 122 may selectively cause one or more rows within the memory device to be refreshed based on the activation count of the row exceeding a threshold.
[0041] Figure 2An example computing system 200 is illustrated in which aspects of the control circuitry 120 that supports usage-based interference mitigation may be implemented. In some implementations, the computing system 200 includes at least one memory device 108, at least one interconnect 106, and at least one processor 202. The memory device 108 may include at least one memory array 204, at least one interface 206, and the control circuitry 120 (or peripheral circuitry) operatively coupled to or associated with the memory array 204. The memory array 204 may include an array of memory cells, including, but not limited to, memory cells of DRAM, SDRAM, three-dimensional (3D) stacked DRAM, DDR memory, LPDDR SDRAM, and the like. The memory array 204 and the control circuitry 120 may be components on a single semiconductor die or separate semiconductor dies. The memory array 204 or the control circuitry 120 may also be distributed across multiple dies.
[0042] Array control logic 210 may include circuitry that provides command decoding, address decoding, input / output functions, amplification circuitry, power supply management, power control modes, and other functions. Clock circuitry 212 may synchronize various memory components with one or more external clock signals provided through interconnect 106, including command and address clocks or data clocks. Clock circuitry 212 may also synchronize memory components using internal clock signals, and may provide timer functionality.
[0043] In some aspects, usage-based interference circuitry 122 may be considered part of control circuitry 120. For example, usage-based interference circuitry 122 may be part of array control logic 210. As another example, usage-based interference circuitry 122 may be another circuit of control circuitry 120.
[0044] The interface 206 may couple the control circuitry 120 or the memory array 204 directly or indirectly to the interconnect 106. In some implementations, the usage-based interference circuitry 122, the array control logic 210, and the clock circuitry 212 may be part of a single component (e.g., the control circuitry 120). In other implementations, one or more of the usage-based interference circuitry 122, the array control logic 210, or the clock circuitry 212 may be implemented as separate components that may be provided on a single semiconductor die or disposed across multiple semiconductor dies. These components may be coupled to the interconnect 106 individually or jointly via the interface 206.
[0045] Interconnect 106 may use one or more of a variety of interconnects that communicatively couple various components together and enable commands, addresses, or other information and data to be transferred between two or more components (e.g., between memory device 108 and processor 202). Figure 2 1 and 2 , the interconnect 106 is illustrated with a single line, but the interconnect 106 may include at least one bus, at least one switching configuration, one or more wires or traces carrying voltage or current signals, at least one switch, one or more buffers, etc. Furthermore, the interconnect 106 may be divided into at least a command and address bus and a data bus.
[0046] In some aspects, memory device 108 can be a separate device from host device 104 ( Figure 1 The separate physical components may include a printed circuit board, a memory card, a memory stick, and a memory module (e.g., a single in-line memory module (SIMM) or a dual in-line memory module (DIMM)). Thus, the separate physical components may be located together in the same housing of an electronic device, or may be distributed across a server rack, a data center, etc. Alternatively, the memory device 108 may be integrated with other physical components including the host device 104 or the processor 202 by being combined on a printed circuit board or in a single package or system on a chip.
[0047] As in Figure 2 , processor 202 may include a computer processor 202-1, a baseband processor 202-2, and an application processor 202-3 coupled to a memory device 108 via an interconnect 106. Processor 202 may include or form part of a central processing unit, a graphics processing unit, a system on a chip, an application specific integrated circuit, or a field programmable gate array. In some cases, a single processor may include multiple processing resources, each dedicated to a different function (e.g., modem management, applications, graphics, central processing). In some implementations, baseband processor 202-2 may include a modem ( Figure 2 The modem or baseband processor 202-2 may be coupled to the modem via, for example, a cellular, Near field or another technology or protocol for wireless communication wirelessly couples to the network.
[0048] In some implementations, processors 202 may be directly connected to memory device 108 (e.g., through interconnect 106). In other implementations, one or more of processors 202 may be indirectly connected to memory device 108 (e.g., through a network connection or through one or more other devices).
[0049] Example Technology and Hardware
[0050] Figure 3 An example memory device 108 is illustrated that can schedule aspects of usage-based interference mitigation based on different external commands. The memory device 108 includes a memory module 302, which can include a plurality of dies 304. As illustrated, the memory module 302 includes a first die 304-1, a second die 304-2, a third die 304-3, and a D-th die 304-D, where D represents a positive integer. The memory module 302 can be a SIMM or a DIMM. As another example, the memory module 302 can be interconnected via a bus (e.g., a peripheral component interconnect high speed Bus) to interface with other components. Figure 1 and 2 The memory device 108 illustrated in FIG. 1 may correspond to, for example, a plurality of dies (or dices) 304-1 through 304-D, or a memory module 302 having two or more dies 304. As shown, the memory module 302 may include one or more electrical contacts 306 (e.g., pins) to interface the memory module 302 to other components.
[0051] In some example embodiments, the control circuitry 120 and / or the usage-based interference circuitry 122 may manage usage-based interference mitigation across multiple dies 304. In other example embodiments, the memory module 302 may include multiple instances of the control circuitry 120, each of which is configured to support aspects of usage-based interference in a particular die 304. In yet another example embodiment, the usage-based interference circuitry 122 may be implemented within each die 304, each of which is configured to monitor and mitigate usage-based interference within the particular die 304.
[0052] The memory module 302 may be implemented in a variety of ways. For example, the memory module 302 may include a printed circuit board, and a plurality of dies 304-1 to 304-D may be mounted or otherwise attached to the printed circuit board. The dies 304 (e.g., memory dies) may be arranged in a row or arranged along two or more dimensions (e.g., forming a grid or array). The dies 304 may have similar sizes, or may have different sizes. Each die 304 may be similar to another die 304, or may differ in size, shape, data capacity, or control circuitry. The dies 304 may also be positioned on a single side or multiple sides of the memory module 302. Each die 304 may include a memory array 204, which may store data associated with usage-based interference mitigation, such as information about Figure 4 Further description.
[0053] Figure 4A memory array 204 is illustrated that is divided into subsets storing different types of data. A subset 402 of memory cells of the memory array 204 stores data 404, which may be associated with a read or write operation. Another subset 406 of memory cells of the memory array 204 stores usage-based interference data 408 (UBD data 408), which may be associated with internal read and write operations. The internal read and write operations are performed to support aspects of usage-based interference mitigation. Usage-based interference mitigation may include reading usage-based interference data 408 from the subset 406 of memory cells and / or writing usage-based interference data 408 (e.g., modified or updated usage-based interference data 408) to the subset 406 of memory cells.
[0054] In an example embodiment, the usage-based interference data 408 includes bits representing the number of activations (e.g., activation counts or activity counts) since the last refresh of one or more rows of memory cells. The usage-based interference data 408 may also include parity bits. Figure 4 , the subset 406 of the memory array 204 is illustrated as including the rightmost column of memory cells closest to the right boundary of the memory array 204, but the subset 406 may include the leftmost column of memory cells closest to the left boundary of the memory array 204, or the subset 406 may include a column of memory cells along the middle of the memory array 204. In some example embodiments, each row of the memory array 204 includes memory cells storing usage-based interference data 408 associated with the row. Reading and writing of the usage-based interference data 408 may be performed based on different external commands, such as with respect to Figure 5 Further description.
[0055] Figure 5 An example external command 500 and an internal command 512 are illustrated for scheduling aspects of usage-based interference mitigation 502. In particular, the memory device 108 generates the internal command 512 based on the external command 500. The usage-based interference mitigation 502 may include reading usage-based interference data 408 from and / or writing usage-based interference data 408 to a subset 406 of memory cells of the memory array 204.
[0056] An example external command 500 that causes a memory device 108 to schedule aspects of usage-based interference mitigation 502 includes a first command 500-1 and a second command 500-2. In some example embodiments, the first command 500-1 is an activate command 504 (ACT504), and the second external command 500-2 is a precharge command 508 (PRE 508). The activate (ACT) command 504 and the precharge (PRE) command 508 are transmitted by the memory controller 114 and received by the memory device 108. In response to the activate command 504, the memory device 108 generates an internal read command 506 (iRD 506), and in response to the precharge command 508, the memory device 108 generates an internal write command 510 (iWR 510).
[0057] In some implementations, the memory device 108 may perform a first portion of the usage-based disturb mitigation 502 in response to the activate command 504, and may perform a second portion of the usage-based disturb mitigation 502 in response to the precharge command 508. The first portion of the usage-based disturb mitigation 502 may include generating an internal read command 506 and performing an internal read operation. The second portion of the usage-based disturb mitigation 502 may include generating an internal write command 510 and performing an internal write operation.
[0058] Internal read / write operations are different from normal read / write operations. During internal read operations, the memory device 108 reads usage-based interference data 408 from the subset 406 of memory cells. During internal write operations, the memory device 108 writes modified usage-based interference data 408 to the subset 406 of memory cells. For example, the modified data may include an updated activation count that is used by the memory device 108 to increment a counter that may be stored within the subset 406 of memory cells. In some example embodiments, the usage-based interference circuitry 122 may pass the updated activation count to the write driver circuit ( Figure 5 ), the write driver circuit writes the updated activation count to the subset 406 of memory cells. Figure 6 and 7 The external command 500, internal command 512, and various resulting memory operations are further described.
[0059] Figure 6 An example sequence of memory operations 600 is illustrated in which aspects of usage-based interference mitigation 502 are implemented in response to different external commands 500 from the memory controller 114. More specifically, Figure 6 Aspects of usage-based disturb mitigation 502 are illustrated as being implemented in response to an activate command 504 and a precharge command 508 from the memory controller 114. Time is shown passing from left to right.
[0060] Orientation Figure 6 The top portion of FIG. 1 shows an external command 500 transmitted by the memory controller 114 and received by the memory device 108. Figure 6 The bottom of FIG. 1 shows internal commands 512 generated and executed by the memory device 108. Figure 6 The times between commands are not necessarily drawn to scale.
[0061] At time T1, the memory device 108 receives an activate command 504 (ACT 504) from the memory controller 114. In response, at time T2, the memory device 108 (e.g., the control circuitry 120) generates an internal read command 506 (iRD506) that causes the memory device 108 to perform an internal read operation 600-1. Departing from existing usage-based disturb mitigation techniques in which conventional memory devices generate internal read commands based on precharge commands, in the disclosed embodiments, the internal read command 506 is generated based on the activate command 504.
[0062] At time T3, the memory controller 114 issues a read command 602 (RD602) associated with a normal read operation. The timing offset between the activate command 504 and the read command 602 is represented by tRCD. In some example embodiments, the timing offset tRCD is sufficient to allow the memory device 108 to complete the internal read operation 600-1 before the read command 602. In other example embodiments, the internal read operation 600-1 may partially overlap with the read command 602.
[0063] The memory device 108 performs a normal read operation 600-2 in response to the read command 602. At time T4, the memory controller 114 issues a precharge command 508. In response, the memory device 108 generates an internal write command 510 that causes the memory device 108 to perform an internal write operation 600-3. In some example embodiments, the memory device 108 generates the internal write command 510 immediately upon receiving the precharge command 508.
[0064] Because the precharge command 508 causes the memory device 108 to deactivate the currently open row, the memory controller 114 waits for sufficient time (e.g., until time T4) to issue the precharge command 508 to allow the memory device 108 to complete the normal read operation 600-2. In addition, in order to allow sufficient time to complete the internal write operation 600-3 before deactivating the currently open row, the memory device 108 delays the execution of the precharge command 508 to enable the internal write operation 600-3 to complete. Thus, the memory device 108 issues the internal precharge command 604 (iPRE 604) at time T5. Therefore, the actual precharge operation 600-4 does not start immediately in response to the precharge command 508 at time T4, but is delayed until time T5. Because the next activate command 606 from the memory controller 114 causes the memory device 108 to open a new row, the memory controller 114 waits until time T6 to issue the next activate command 606 so that the precharge operation 600-4 can be completed before the next activate command 606. The timing offset between the precharge command 508 and the next active command 606 is represented by tRP. The timing offset tRP is sufficient to allow the memory device 108 to perform the internal write operation 600-3 and the precharge operation 600-4, while the timing offset tRCD allows the memory device 108 to at least partially perform the internal read operation 600-1.
[0065] Because the internal read operation 600-1 is at least partially performed during the timing offset tRCD, but the internal write operation 600-3 is performed during the timing offset tRP, the memory device 108 has fewer timing constraints to perform the internal read operation 600-1 and the internal write operation 600-3. In addition, in this example, the internal read operation 600-1 and the internal write operation 600-3 are separated by the normal read operation 600-2 (for example, not back-to-back or sequentially performed). Thus, the interference circuit system 122 based on the use can utilize the time associated with the normal read operation 600-2 before the internal write operation 600-3 to perform other interference mitigation tasks based on the use, including error correction. In addition, because the internal read operation 600-1 is not performed during the timing offset tRP, but during the timing offset tRCD, the duration of tRP can be reduced, thereby improving the overall performance of the memory device. In addition, additional time can be allocated for performing the internal write operation 600-3 within the timing offset tRP. In some example embodiments, the memory device 108 may generate the internal read command 506 based on the read command 602. In such embodiments, prior to receiving the precharge command 508 from the memory controller 114, the memory device 108 may perform the internal read operation 600-1.
[0066] In some example embodiments, the memory device 108 may alternatively generate the internal read command 506 based on another external command 500, such as the read command 602. In such embodiments, before receiving the precharge command 508 from the memory controller 114, the memory device 108 may perform the internal read operation 600-1.
[0067] In other example embodiments, the memory device 108 may generate the internal write command 510 based on another external command 500, such as the read command 602. In such embodiments, the memory device 108 may sequentially perform the internal read operation 600-1, the normal read operation 600-2, and the internal write operation 600-3 before receiving the precharge command 508 from the memory controller 114. In general, the internal read command 506 or the internal write command 510 may be generated in response to any external command 500, which allows sufficient time to perform the corresponding operation before the memory device performs the precharge operation 600-4.
[0068] Figure 7 An example sequence of memory operations 700 is illustrated in which aspects of usage-based interference mitigation 502 are implemented in response to different external commands from the memory controller 114. More specifically, Figure 7 Aspects of usage-based disturb mitigation 502 are illustrated as being implemented in response to an activate command 504, a write command 702, and a precharge command 508 from the memory controller 114. Time is shown passing from left to right.
[0069] Orientation Figure 7 The top portion of FIG. 1 shows an external command 500 transmitted by the memory controller 114 and received by the memory device 108. Figure 7 The bottom of FIG. 1 shows internal commands 501 generated and executed by the memory device 108. Figure 7 The times between commands are not necessarily drawn to scale.
[0070] At time T1, the memory controller 114 issues an activate command 504 (ACT 504). In response, at time T2, the memory device 108 (e.g., the control circuit system 120) generates an internal read command 506 (iRD 506) that causes the memory device 108 to perform an internal read operation 700-1. Compared to existing usage-based interference mitigation techniques in which conventional memory devices generate internal read commands based on precharge commands, in the disclosed embodiments, the internal read command 506 is generated based on the activate command 504.
[0071] At time T3, the memory controller 114 issues a write command 702 (WR702) associated with a normal write operation. The timing offset between the activate command 504 and the write command 702 is represented by tRCD. The timing offset tRCD is sufficient to allow the memory device 108 to complete the internal read operation 700-1.
[0072] The memory device 108 performs a normal write operation 700-2 in response to the write command 702. At time T4, the memory controller 114 issues a precharge command 508. In response, the memory device 108 generates an internal write command 510, which causes the memory device 108 to perform an internal write operation 700-3.
[0073] Because the precharge command 508 causes the memory device 108 to deactivate the currently open row, the memory controller 114 waits until time T4 to issue the precharge command 508 to provide the memory device 108 with sufficient time to complete the normal write operation 700-2. In addition, in order to allow the internal write operation 700-3 to be completed before deactivating the currently open row, the execution of the precharge command 508 is delayed until the control circuit system 120 issues the internal precharge command 604 (iPRE 604) at time T5. Therefore, the actual precharge operation 700-4 does not start immediately after the precharge command 508, but is delayed until time T5 relative to time T4. Because the next activate command 606 from the memory controller 114 causes the memory device 108 to open a new row, the memory controller 114 waits until time T6 to allow sufficient time to complete the precharge operation 700-4. The timing offset between the precharge command 508 and the next activate command 606 is represented by tRP. The timing offset tRP is sufficient to complete the internal write operation 700 - 3 and the precharge operation 700 - 4 .
[0074] Because the internal read operation 700-1 is performed during the timing offset tRCD, and the internal write operation 700-3 is performed during the timing offset tRP, the internal read operation 700-1 and the internal write operation 700-3 are not performed back-to-back, which causes a delay between the two operations. Thus, error correction and other tasks can be performed before performing the internal write operation 700-3. In addition, because the internal read operation 700-1 is not performed during the timing offset tRP, but is performed in the timing offset tRCD, the duration of tRP can be reduced, thereby improving the overall performance of the memory device 108.
[0075] In some example embodiments, the memory device 108 may generate the internal read command 506 based on another external command 500, such as the write command 702. In such embodiments, before receiving the precharge command 508 from the memory controller 114, the memory device 108 may perform the internal read operation 700-1.
[0076] In other example embodiments, the memory controller 114 may generate the internal write command 510 based on another external command 500, such as the write command 702. In such embodiments, the memory device 108 may sequentially perform the internal read operation 700-1, the normal write operation 700-2, and the internal write operation 700-3 before receiving the precharge command 508 from the memory controller 114. In general, the internal read command 506 or the internal write command 510 may be generated in response to any external command 500, which allows sufficient time to perform the corresponding operation before the memory device performs the precharge operation 700-4.
[0077] Instance Methods
[0078] References in this section Figure 8 , 9 10 and 11 describe example methods for scheduling usage-based interference mitigation based on different external commands. These descriptions may also be referred to by way of example only. Figures 1 to 7 The components, entities and other aspects depicted in the description are not necessarily limited to being performed by one entity or multiple entities operating on one device.
[0079] Figure 8 Method 800 is described, which includes operations 802 to 804. In one aspect, the operations of method 800 are described by reference Figures 1 to 7 1. The operation includes transmitting two different external commands to the memory device 108 by the memory controller 114. In response to the first external command 500-1, the memory device 108 generates an internal read command 506, and in response to the second external command 500-2, the memory device 108 generates an internal write command 510.
[0080] At 802, the memory controller 114 transmits a first command 500-1 to the memory device 108. The first command 500-1 is an external command 500 received by the memory device 108. The first command 500-1 causes the memory device 108 to generate an internal read command 506, e.g., as in Figure 6 As shown in .
[0081] At 804, the memory controller 114 transmits a second command 500-2 to the memory device 108. The second command 500-2 is an external command 500 received by the memory device 108. The second command 500-2 causes the memory device 108 to generate an internal write command 510. In some example embodiments, the first command 500-1 is an activate command 504, and the second command 500-2 is a precharge command 508.
[0082] Fig. 9 Method 900 is described, which includes operations 902 to 910. In one aspect, the operations of method 900 are described by reference Figures 1 to 7 The method 900 is implemented by or with the memory device 108 described herein. The operation of the method 900 includes receiving two different external commands from the memory controller 114 by the memory device 108. In response to the first external command 500-1, the memory device 108 generates an internal read command 506. In response to the second external command 500-2, the memory device 108 generates an internal write command 510.
[0083] At 902, the memory device 108 receives a first command 500-1 from the memory controller 114. The first command 500-1 causes the memory device 108 to generate an internal read command 506. In some example embodiments, the first command 500-1 is an activate command 504. At 904, the memory device 108 executes the internal read command 506 associated with usage-based interference mitigation based on the first command 500-1. To execute the internal read command 506, the memory device 108 performs an internal read operation 600-1. The internal read operation 600-1 is completed before the memory device 108 receives a second command 500-2 from the memory controller 114. In some example embodiments, the second command 500-2 is a precharge command 508. The first command 500-1 and the second command 500-2 may or may not be sequential commands. In some implementations, the memory device receives a third command, such as a read or write command, between the first command 500-1 and the second command 500-2.
[0084] At 906, the memory device 108 receives the second command 500-2 from the memory controller 114. The second command 500-2 causes the memory device 108 to generate an internal write command 510. The first command 500-1 and the second command 500-2 are separated in time by at least a timing offset that enables the memory device 108 to perform the internal read operation 600-1 prior to the second command 500-2.
[0085] At 908, the memory device 108 executes an internal write command 510 associated with usage-based interference mitigation based on the second command 500-2. To execute the internal write command 510, the memory device performs an internal write operation 600-3. In some example embodiments, at 910, the memory device 108 may optionally perform an internal precharge operation 600-4 after executing the internal write operation 600-3 and before receiving the next activate command 606.
[0086] Fig.10 Method 1000 is described, and includes operations 1002 through 1006. In one aspect, the operations of method 1000 are described by reference to Figures 1 to 7 The operation may be implemented by or with the memory device 108 described herein. The operation includes configuring a subset of memory cells of a row of the memory device 108 to store data associated with usage-based interference, receiving a first command 500-1 from the memory controller 114, and generating an internal read command 506 by the memory device 108 in response to the first command 500-1.
[0087] At 1002, a subset of memory cells of a row of memory devices 108 are configured to store data associated with usage-based interference. At 1004, the memory device 108 receives an activate command 504 from the memory controller 114. In this example, the activate command 504 represents the first command 500-1. At 1006, the memory device 108 generates an internal read command 506 based on the activate command 504. The internal read command 506 causes the memory device 108 to read data from the subset of memory cells.
[0088] For the figures described above, the order in which the operations are shown and / or described is not intended to be construed as limiting. Any number or combination of the described process operations may be combined or rearranged in any order to implement a given method or an alternative method. Operations may also be omitted from or added to the described methods. In addition, the described operations may be implemented in a manner that is fully or partially overlapping.
[0089] Aspects of these methods may be implemented, for example, in hardware (e.g., fixed logic circuitry or a processor in conjunction with a memory), firmware, software, or some combination thereof. These methods may be implemented using Figures 1 to 7 The present invention is implemented by one or more of the devices or components shown in the drawings, and its components can be further divided, combined, rearranged, etc. The devices and components of these drawings generally represent hardware, such as electronic devices, packaged modules, IC chips, or circuits; firmware or its actions; software; or a combination thereof. Therefore, these drawings illustrate some of the many possible systems or devices capable of implementing the described methods.
[0090] Computer-readable media includes both non-transitory computer storage media and communication media, including any media that facilitates the transfer of computer programs (e.g., applications) or data from one entity to another. Non-transitory computer storage media can be any available media that can be accessed by a computer, such as RAM, ROM, flash, EEPROM, optical media, and magnetic media.
[0091] In the following, various examples for scheduling aspects of usage-based interference mitigation based on different external commands are described:
[0092] Example 1: A device comprising:
[0093] A memory device comprising:
[0094] at least one memory bank comprising memory cells, wherein a subset of the memory cells are configured to store data associated with usage-based interference; and
[0095] circuitry configured to mitigate usage-based disturbances within the memory based on the data,
[0096] The memory device is configured to:
[0097] receiving two commands separated in time by a timing offset from a memory controller;
[0098] generating an internal read command based on a first command of the two commands to cause the memory device to read the data from the subset of the memory cells; and
[0099] An internal write command is generated based on a second of the two commands to cause the memory device to write modified data generated by the circuitry to the subset of the memory cells.
[0100] Example 2: The apparatus of example 1 or any other example, wherein the first command received from the memory controller is an activate command.
[0101] Example 3: The apparatus of example 1 or any other example, wherein the second command received from the memory controller is a precharge command.
[0102] Example 4: The apparatus of example 1 or any other example, wherein the memory device is configured to read the data from the subset of the memory cells based on the internal read command prior to receiving the second command.
[0103] Example 5: The apparatus of example 4 or any other example, wherein a timing offset between the first command and the second command comprises at least a row address strobe (RAS) delay and a column address strobe (CAS) delay (tRCD).
[0104] Example 6: The apparatus of example 1 or any other example, wherein the memory device is configured to write the modified data to the subset of the memory cells prior to receiving a subsequent command.
[0105] Example 7: The apparatus of example 6 or any other example, wherein a timing offset between the second command and a subsequent command corresponds to a precharge time (tRP).
[0106] Example 8: The apparatus of example 1 or any other example, wherein the subset represents a subset of the memory cells within each row of the memory bank.
[0107] Example 9: A device comprising:
[0108] a memory device comprising a plurality of memory cells arranged in a row, a subset of the memory cells being configured to store data associated with usage-based interference in the row,
[0109] The memory device is configured to:
[0110] receiving an activate command from a memory controller; and
[0111] The data is read from the subset of the memory cells based on the activate command.
[0112] Example 10: The apparatus of example 9 or any other example, wherein the memory device is configured to:
[0113] receiving a precharge command from the memory controller separated in time from the activate command; and
[0114] Modified data generated based on the data is written to the subset of the memory cells based on the precharge command.
[0115] Example 11: The apparatus of example 10 or any other example, wherein the memory device is configured to read the data from the subset of the memory cells prior to receiving the precharge command.
[0116] Example 12: The apparatus of example 10 or any other example, wherein the memory device is configured to write the modified data to the subset of the memory cells prior to receiving a subsequent command.
[0117] Example 13: The apparatus of example 9 or any other example, wherein:
[0118] each row comprising the subset of the memory cells configured to store the data associated with usage-based interference;
[0119] The activation command is associated with a particular row; and
[0120] The memory device is configured to read the data from the row associated with the activate command.
[0121] Example 14: A method comprising:
[0122] receiving, by the memory device, a first command from a memory controller;
[0123] executing, by the memory device, an internal read command associated with usage-based interference mitigation based on the first command;
[0124] receiving, by the memory device, a second command from the memory controller; and
[0125] An internal write command associated with usage-based disturb mitigation is performed by the memory device based on the second command.
[0126] Example 15: The method of example 14 or any other example, wherein the receiving of the first command comprises receiving an activate command from the memory controller.
[0127] Example 16: The method of example 14 or any other example, wherein the receiving of the second command comprises receiving a precharge command from the memory controller.
[0128] Example 17: The method of example 16 or any other example, further comprising:
[0129] generating, by the memory device, an internal precharge command based on the precharge command; and
[0130] executing the internal precharge command by the memory device,
[0131] Wherein the executing of the internal write command comprises executing the internal write command before executing the internal precharge command.
[0132] Example 18: The method of example 14 or any other example, further comprising:
[0133] receiving, by the memory device, a read command from the memory controller; and
[0134] executing the read command after executing the internal read command but before receiving the second command,
[0135] wherein the receiving of the read command occurs between the receiving of the first command and the receiving of the second command.
[0136] Example 19: The method of example 14 or any other example, further comprising:
[0137] receiving, by the memory device, a write command from the memory controller; and
[0138] executing the write command after executing the internal read command but before receiving the second command,
[0139] wherein the receiving of the write command occurs between the receiving of the first command and the receiving of the second command.
[0140] Example 20: The method of example 14 or any other example, wherein the executing of the internal read command comprises reading, by the memory device and based on the internal read command, data associated with usage-based interference prior to receiving the second command.
[0141] Unless the context dictates otherwise, the use of the word "or" herein may be considered use of an "inclusive or," or a term that allows inclusion or application of one or more items linked by "or" (e.g., the phrase "A or B" may be interpreted as allowing only "A," only "B," or both "A" and "B"). In addition, as used herein, a phrase referring to "at least one of" a list of items refers to any combination of the items, including single members. For example, "at least one of a, b, or c" may encompass a, b, c, ab, ac, bc, and abc, as well as any combination with multiples of the same element (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c). In addition, the items represented in the figures and terms discussed herein may indicate one or more items or terms, and therefore, in this written description, reference may be made to the singular or plural forms of the items and terms interchangeably.
[0142] in conclusion
[0143] Although aspects of implementing control circuitry for scheduling aspects of usage-based interference mitigation based on different external commands have been described in language specific to certain features and / or methods, the subject matter of the appended claims is not necessarily limited to the specific features or methods described. Rather, the specific features and methods are disclosed as various example implementations of aspects of scheduling usage-based interference mitigation based on different external commands.
Claims
1. A device, wherein include: A memory device comprising: at least one memory bank comprising memory cells, wherein a subset of the memory cells are configured to store data associated with usage-based interference; and A circuit system configured to mitigate usage-based interference within the memory based on the data, the memory device configured to: receiving two commands separated in time by a timing offset from a memory controller; generating an internal read command based on a first command of the two commands to cause the memory device to read the data from the subset of the memory cells; and An internal write command is generated based on a second of the two commands to cause the memory device to write modified data generated by the circuitry to the subset of the memory cells. 2 . The apparatus of claim 1 , wherein the first command received from the memory controller is an activate command. 3 . The apparatus of claim 1 , wherein the second command received from the memory controller is a precharge command.
4. The apparatus of claim 1, wherein the memory device is configured to read the data from the subset of the memory cells based on the internal read command prior to receiving the second command.
5. The apparatus of claim 4, wherein a timing offset between the first command and the second command comprises at least a row address strobe (RAS) delay and a column address strobe (CAS) delay (tRCD).
6. The apparatus of claim 1, wherein the memory device is configured to write the modified data to the subset of the memory cells prior to receiving a subsequent command. 7 . The apparatus of claim 6 , wherein a timing offset between the second command and a subsequent command corresponds to a precharge time tRP.
8. The apparatus of claim 1, wherein the subset represents a subset of the memory cells within each row of the memory bank.
9. A device, wherein include: a memory device comprising a plurality of memory cells arranged in a row, a subset of the memory cells being configured to store data associated with usage-based interference in the row, The memory device is configured to: receiving an activate command from a memory controller; as well as The data is read from the subset of the memory cells based on the activate command.
10. The apparatus of claim 9, wherein the memory device is configured to: receiving a precharge command from the memory controller separated in time from the activate command; and Modified data generated based on the data is written to the subset of the memory cells based on the precharge command.
11. The apparatus of claim 10, wherein the memory device is configured to read the data from the subset of the memory cells prior to receiving the precharge command.
12. The apparatus of claim 10, wherein the memory device is configured to write the modified data to the subset of the memory cells prior to receiving a subsequent command.
13. The device according to claim 9, in: each row comprising the subset of the memory cells configured to store the data associated with usage-based interference; The activation command is associated with a particular row; and The memory device is configured to read the data from the row associated with the activate command.
14. A method, wherein include: receiving, by the memory device, a first command from a memory controller; executing, by the memory device, an internal read command associated with usage-based interference mitigation based on the first command; receiving, by the memory device, a second command from the memory controller; as well as An internal write command associated with usage-based disturb mitigation is performed by the memory device based on the second command.
15. The method of claim 14, wherein the receiving of the first command comprises receiving an activate command from the memory controller.
16. The method of claim 14, wherein the receiving of the second command comprises receiving a precharge command from the memory controller.
17. The method according to claim 16, further comprising: include: generating, by the memory device, an internal precharge command based on the precharge command; as well as executing the internal precharge command by the memory device, Wherein the executing of the internal write command comprises executing the internal write command before executing the internal precharge command.
18. The method according to claim 14, further comprising: include: receiving, by the memory device, a read command from the memory controller; as well as executing the read command after executing the internal read command but before receiving the second command, wherein the receiving of the read command occurs between the receiving of the first command and the receiving of the second command.
19. The method according to claim 14, further comprising: include: receiving, by the memory device, a write command from the memory controller; as well as executing the write command after executing the internal read command but before receiving the second command, wherein the receiving of the write command occurs between the receiving of the first command and the receiving of the second command.
20. The method of claim 14, wherein the executing of the internal read command comprises reading, by the memory device and based on the internal read command, data associated with usage-based interference prior to receiving the second command.
