# US 2012/0254549 A1 · Non-Volatile Memory System Allowing Reverse Eviction of Data Updates to Non-Volatile Binary Cache

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2012/0254549 A1
- Document ID: US20120254549A1
- Status: Published application
- Kind: A1
- Application number: 13/074,402
- Filed: 2011-03-29
- Published: 2012-10-04
- Earliest claimed: 2011-03-29
- Assignees: SanDisk Technologies LLC
- Inventors: Neil David Hutchison; Robert George Young
- Web page: https://patentgrep.com/patent/US20120254549A1

## CPC

- G06F 12/0246: {in block erasable memory, e.g. flash memory}
- G06F 2212/7202: Allocation control and policies
- G06F 2212/7203: Temporary buffering, e.g. using volatile buffer or dedicated buffer blocks
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A non-volatile memory system includes a memory section having a non-volatile cache portion storing data in a binary format, a primary user data storage section that stores user data in multi-state format, and an update memory area where the memory system stores data updating user data previously stored in the primary user data. The memory system allows a maximum number of blocks for use in the update memory area. When the memory system receives updated data corresponding to user data already written into the primary user data storage section, it determines whether a block of memory is available in the update memory area. In response to determining that a block of memory is not available in the update memory area, the system determines a block of the update memory to remove from the update memory; copies the data content of the determined update block into the cache portion of the memory section; and subsequently writes the updated data into the update memory.

## Claims

### Claim 1

A method operation a non-volatile memory system, the memory system including a controller circuit and a memory section formed on one or more integrated circuits, the memory section having a non-volatile cache portion storing data in a binary format, a primary user data storage section of flash memory wherein the memory system stores user data in multi-state format, and an update memory area where the memory system stores data updating user data previously stored in the primary user data storage section, wherein the memory system allows a maximum number of blocks of memory cells for use in the update memory area, the method comprising:
receiving at the controller updated data corresponding to user data already written into the primary user data storage section;
determining whether a block of memory is available in the update memory area;
in response to determining that a block of memory is available in the update memory area, writing the updated data to the available block; and
in response to determining that a block of memory is not available in the update memory area:
determining a block of the update memory to remove from the update memory;
copying the data content of the determined update block into the cache portion of the memory section; and
subsequently writing the updated data into the update memory.

### Claim 2 (depends on 1)

The method of claim 1, wherein subsequent to receiving at the controller updated data corresponding to user data already written into the primary user data storage section and prior to determining whether a block of memory is available in the update memory area, the method further comprises:
determining whether the update memory area currently includes a block corresponding to said user data already written into the primary user data storage section,
wherein said determining whether a block of memory is available in the update memory area is performed in response to determining that the update memory area currently does not include a block corresponding to said user data already written into the primary user data storage section.

### Claim 3 (depends on 1)

The method of claim 1, wherein determining whether a block of memory is available comprises determining the number of blocks in use in the update memory area is the maximum allowed number.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
in response to determining that a block of memory is not available in the update memory area:
determining whether to transfer the content of a block from the update memory to the primary user data storage section;
in response to determining to transfer the content of a block from the update memory to the primary user data storage section:
transferring the content of the determined block from the update memory to the primary user data storage section; and
subsequently writing the updated data into the update memory, and
wherein the process of said determining a block of the update memory to remove from the update memory, copying the data content of the determined update block into the cache portion of the memory section, and subsequently writing the updated data into the update memory is performed in response to determining not to transfer the content of a block from the update memory to the primary user data storage section.

### Claim 5 (depends on 4)

The method of claim 4, wherein criteria for determining whether to transfer the content of a block from the update memory to the primary user data storage section includes the amount of space available in the non-volatile cache portion.

### Claim 6 (depends on 4)

The method of claim 4, wherein the block to be transferred to the primary user data storage section is selected based upon the amount of data that would be needed to be copied.

### Claim 7 (depends on 4)

The method of claim 4, wherein the block to be transferred to the primary user data storage section is selected based upon how recently the block has been written.

### Claim 8 (depends on 4)

The method of claim 4, wherein criteria for determining whether to transfer the content of a block from the update memory to the primary user data storage section includes the update memory holding data of a sequential span corresponding to a region of the primary user data storage section.

### Claim 9 (depends on 4)

The method of claim 4, wherein the update memory stores data in a binary format and said transferring the content of the determined block from the update memory to the primary user data storage section includes combining multiple logical pages of data into a multi-state format and subsequently writing the combined logical pages of data in multi-state form in the primary user data storage section.

### Claim 9 (depends on 1)

The method of claim 1, wherein the update memory stores data in a binary format.

### Claim 10 (depends on 1)

The method of claim 1, wherein the update memory stores data in a multi-state format.

### Claim 11 (depends on 10)

The method of claim 10, wherein the update memory stores data with the same number of bits per cell as the primary user data storage section.

### Claim 12 (depends on 1)

The method of claim 1, wherein the criteria for determining which block of the update memory to remove from the update memory includes the amount of valid data contained by the block.

### Claim 13 (depends on 1)

The method of claim 1, wherein criteria for determining which block of the update memory to remove from the update memory includes the frequency with which the block has been written to.

### Claim 14 (depends on 1)

The method of claim 1, wherein criteria for determining which block of the update memory to remove from the update memory includes the number of times a set of data therein has been updated.

### Claim 14 (depends on 1)

The method of claim 1, wherein criteria for determining which block of the update memory to remove from the update memory includes the amount of data written therein.

### Claim 15 (depends on 1)

The method of claim 1, wherein the maximum number of blocks allowed by the memory system for use in the update memory area is determined by the data management structure used by the controller.

### Claim 16 (depends on 1)

The method of claim 1, wherein the maximum number of blocks allowed by the memory system for use in the update memory area is determined by the number of physical data blocks available for use as update memory.

### Claim 17 (depends on 1)

The method of claim 1, wherein determining whether a block of memory is available comprises determining the number of blocks in use in the update memory area is the maximum allowed number, and wherein the maximum number of blocks allowed by the memory system for use in the update memory area is determined by the number of physical data blocks available for use as update memory.
