# US 2013/0086454 A1 · Adjustable memory allocation based on error correction

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

- Number: US 2013/0086454 A1
- Document ID: US20130086454A1
- Status: Published application
- Kind: A1
- Application number: 13/686,563
- Filed: 2012-11-27
- Published: 2013-04-04
- Earliest claimed: 2010-02-03
- Assignees: Seagate Technology LLC
- Inventors: Bernardo Rub
- Web page: https://patentgrep.com/patent/US20130086454A1

## CPC

- G06F 11/1048: {using arrangements adapted for a specific error detection or correction feature}
- G06F 11/1072: {in multilevel memories}
- G06F 11/1068: {in sector programmable memories, e.g. flash disk (G06F11/1072 takes precedence)}
- G06F 11/1076: {Parity data used in redundant arrays of independent storages, e.g. in RAID systems}
- H03M 13/05: using block codes, i.e. a predetermined number of check bits joined to a predetermined number of information bits {(H03M13/2906 takes precedence)}
- H03M 13/1515: {Reed-Solomon codes}
- H03M 13/152: {Bose-Chaudhuri-Hocquenghem [BCH] codes}
- H03M 13/353: {Adaptation to the channel}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H03M: CODING; DECODING; CODE CONVERSION IN GENERAL (using fluidic means F15C4/00; optical analogue/digital converters G02F7/00; coding, decoding or code conversion, specially adapted for particular applications, see the relevant subclasses, e.g. G01D, G01R, G06F, G06T, G09G, G10L, G11B, G11C, H04B, H04L, H04M, H04N; ciphering or deciphering for cryptography or other purposes involving the need for secrecy G09C)

## Abstract

An apparatus may comprise a memory including a first area of total usable storage capacity of the memory reported to a host device, a second area occupied by error correction code (ECC) appended to data stored in the first area, and a third area of usable data storage capacity not reported to the host device. The apparatus may further comprise a controller configured to balance sizes of the second area and third area to maintain a size of the first area as the length of ECC of data stored in the first area increases. The controller may be further configured to exchange data having an ECC of a controllable length with the memory based on a data storage location, and adjust the controllable length of the ECC based on an error history of the data storage location.

## Claims

### Claim 1

An apparatus comprising:
a memory including:
a first area of total usable storage capacity of the memory reported to a host device;
a second area occupied by error correction code (ECC) appended to data stored in the first area;
a third area of usable data storage capacity not reported to the host device; and
a controller configured to:
balance sizes of the second area and third area to maintain a size of the first area as the length of ECC of data stored in the first area increases.

### Claim 2 (depends on 1)

The apparatus of claim 1, further comprising:
the controller further configured to:
exchange data with the memory based on a target address, the data having an appended ECC of a controllable length; and
adjust the controllable length of the appended ECC based on an error history of the target address.

### Claim 3 (depends on 2)

The apparatus of claim 2, further comprising:
the controller further configured to:
receive a write request including data and the target address;
assign the target address to storage space in the third area;
store data to the target address in the third area and the appended ECC to the second area; and
reassign the storage space with the assigned target address to the first area.

### Claim 4 (depends on 2)

The apparatus of claim 2, further comprising:
the memory includes memory blocks, the target address identifying at least one target memory block;
the controller further configured to:
maintain an ECC length table including ECC lengths for each memory block; and
update the ECC length table based on error histories of each memory block.

### Claim 5 (depends on 4)

The apparatus of claim 4, further comprising:
the controller further configured to:
receive a write request including data and the target address for storing data to the memory;
checking the ECC length table for an ECC length of the target address; and
appending an ECC to the data of the ECC length.

### Claim 6 (depends on 4)

The apparatus of claim 4, further comprising the controller further configured to update the ECC length table for a memory block as part of a block erase operation for the memory block.

### Claim 7 (depends on 4)

The apparatus of claim 4, further comprising the memory includes flash memory.

### Claim 8 (depends on 7)

The apparatus of claim 7, further comprising the third area stores invalid old data, wherein a time between necessary memory block erase cycles decreases as the size of the third area is reduced.

### Claim 9 (depends on 2)

The apparatus of claim 2, further comprising:
the controller further configured to:
read data and the appended ECC from the target address based on a read request; and
update the error history of the target address based on a number of detected errors.

### Claim 10 (depends on 2)

The apparatus of claim 2, further comprising:
the controller further configured to:
adjust the length of the appended ECC of data to a minimal ECC length calculated to maintain a threshold bit error rate (BER) based on the error history of the target address; and
store the data and the appended ECC to the memory based on the target address in a write request.

### Claim 11

A device comprising:
a memory including a first capacity, a second capacity, and a third capacity,
the first capacity including a reported total storage amount,
the second capacity including error correction code (ECC) for data stored in the first capacity,
the third capacity including an overprovisioned storage area not reported as part of the total storage amount;
a controller configured to:
exchange data with the memory based on a data storage location, the data having an ECC of a controllable length; and
adjust the controllable length of the ECC based on an error history of the data storage location.

### Claim 12 (depends on 11)

The device of claim 11, further comprising:
the memory includes memory pages, the data storage location corresponding to at least one memory page; and
an ECC length table storing ECC lengths for each memory page.

### Claim 13 (depends on 12)

The device of claim 12, further comprising:
an ECC length for a memory page in the ECC length table is updated as part of a memory page erase cycle based on the error history of the memory page; and
the controller is further configured to set the length of the ECC for data stored to the memory page based on the ECC length for the memory page stored in the ECC length table.

### Claim 14 (depends on 11)

The apparatus of claim 11, further comprising:
the controller further configured maintain a size of the first capacity by reducing a size of the third capacity and increasing a size of the second capacity as a total ECC length of data stored in the first capacity increases.

### Claim 15 (depends on 14)

The apparatus of claim 14, further comprising:
the memory includes flash memory; and
the third capacity stores invalid old data, wherein a time between necessary memory page erase cycles decreases as the size of the third capacity is reduced.

### Claim 16 (depends on 11)

The apparatus of claim 11, further comprising:
the controller further configured to:
read data and the ECC from the data storage location based on a read request; and
update the error history of the data storage location based on a number of detected errors.

### Claim 17

A method comprising:
dividing a total actual storage capacity of a data storage medium between reported total storage space, unreported overhead storage, and error correction code (ECC) space for ECC of data stored in the reported total storage space; and
maintaining a size of the reported total storage space by balancing sizes of the unreported overhead storage and the ECC space as a total length of ECC of stored data is increased.

### Claim 18 (depends on 17)

The method of claim 17, further comprising:
exchanging data with the data storage medium based on a target address, the data having an appended ECC of a controllable length; and
adjusting the controllable length of the ECC based on an error history of the target address.

### Claim 19 (depends on 18)

The method of claim 18, further comprising:
maintaining an ECC length table of ECC lengths for each memory location; and
updating the ECC length table for the target address when errors are detected during a data read.

### Claim 20 (depends on 19)

The method of claim 19, further comprising:
receiving a write request including data and a target address for storing data to the data storage medium;
checking the ECC length table for an ECC length of the target address; and
appending an ECC to the data of the ECC length.
