# US 2015/0178013 A1 · Systems and methods of compressing data

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

- Number: US 2015/0178013 A1
- Document ID: US20150178013A1
- Status: Published application
- Kind: A1
- Application number: 14/502,554
- Filed: 2014-09-30
- Published: 2015-06-25
- Earliest claimed: 2013-12-20
- Assignees: SanDisk Technologies LLC
- Applicants: Sandisk Technologies Inc.
- Inventors: TAL ROSTOKER; ALON MARCU
- Web page: https://patentgrep.com/patent/US20150178013A1

## CPC

- G06F 3/0644: {Management of space entities, e.g. partitions, extents, pools}
- G06F 3/0608: {Saving storage space on storage systems}
- G06F 3/0656: {Data buffering arrangements}
- G06F 3/0679: {Non-volatile semiconductor memory device, e.g. flash memory, one time programmable memory [OTP]}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A method includes, in response to a first write command corresponding to first data and a first context which is identifiable with a first identifier and to a second write command corresponding to second data and a second context identifiable with a second identifier, determining whether the first identifier of the first context matches the second identifier of the second context. The method also includes, if the first identifier of the first context is determined to match the second identifier of the second context, forming a compression group of data including the first data and the second data, and generating compressed data corresponding to the compression group of data.

## Claims

### Claim 1

A method comprising:
at a data storage device that includes a controller and a memory, performing:
in response to a first write command corresponding to first data and a first context which is identifiable with a first identifier and to a second write command corresponding to second data and a second context identifiable with a second identifier, determining whether the first identifier of the first context matches the second identifier of the second context;
if the first identifier of the first context is determined to match the second identifier of the second context, forming a compression group of data including the first data and the second data; and
generating compressed data corresponding to the compression group of data.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
writing the first data to the memory prior to responding to the second write command; and
after responding to the second write command, if the first identifier matches the second identifier:
reading the first data from the memory;
combining the first data and the second data to form the compression group of data; and
compressing the compression group of data to generate the compressed data.

### Claim 3 (depends on 1)

The method of claim 1, further comprising determining a size of the compression group of data, wherein the compressed data is generated responsive to determining that the size of the compression group of data exceeds a threshold size.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
receiving one or more additional write commands corresponding to additional data before generating the compressed data;
receiving a close context notification associated with a particular context;
after receiving the close context notification, identifying related data received via one or more write commands and associated with the particular context;
determining a size of the related data;
if the size of the related data exceeds a threshold size, dividing the related data into a plurality of sub-groups of data, wherein the compression group of data corresponds to one sub-group of the plurality of sub-groups; and
generating additional compressed data corresponding to other sub-groups of the plurality of sub-groups.

### Claim 5 (depends on 1)

The method of claim 1, wherein the compressed data is generated after receiving data from a host device indicating that the first data and the second data are compressible.

### Claim 6 (depends on 1)

The method of claim 1, wherein the first identifier and the second identifier are context identifiers received from a host device according to an eMMC standard.

### Claim 7 (depends on 1)

The method of claim 1, wherein the first identifier and the second identifier are context identifiers received from a host device according to a Universal Flash Storage (UFS) standard.

### Claim 8 (depends on 1)

The method of claim 1, further comprising:
writing the compressed data to a region of the memory associated with a set of memory addresses of the memory; and
storing mapping information that associates the set of memory addresses with a group identifier of the compression group of data.

### Claim 9 (depends on 8)

The method of claim 8, wherein the set of memory addresses corresponds to a sequential range of logical block addresses.

### Claim 10 (depends on 8)

The method of claim 8, further comprising:
receiving a read command after storing the mapping information, the read command associated with a particular memory address;
determining whether the particular memory address is associated with the group identifier based on the mapping information;
reading each memory address of the set of memory addresses associated with the group identifier if the particular memory address is associated with the group identifier; and
generating decompressed data corresponding to the compression group of data using data read from the set of memory addresses.

### Claim 11 (depends on 8)

The method of claim 8, wherein the group identifier is a context identifier of the first context or of the second context.

### Claim 12 (depends on 8)

The method of claim 8, further comprising assigning the group identifier to the compression group of data, wherein the group identifier is distinct from the first identifier and is distinct from the second identifier.

### Claim 13 (depends on 1)

The method of claim 1, further comprising:
in response to a third write command corresponding to third data and to a third context identifiable with a third identifier, determining whether the third identifier matches the first identifier;
if the third identifier does not match the first identifier, generating second compressed data corresponding to the third data; and
if the third identifier matches the first identifier, adding the third data to the compression group of data before generating the compressed data.

### Claim 14 (depends on 1)

The method of claim 1, wherein the memory has a three-dimensional (3D) memory configuration.

### Claim 15 (depends on 14)

The method of claim 14, wherein the 3D memory configuration is monolithically formed in one or more physical levels of arrays of memory cells of a memory die having an active area above a silicon substrate, and wherein the memory die further includes circuitry associated with operation of the memory cells.

### Claim 16

A data storage device comprising:
a controller; and
a memory coupled to the controller, wherein the controller is configured to:
perform a comparison of a first identifier of a first context associated with a first write command and a second identifier of a second context associated with a second write command; and
generate compressed data based on the comparison, wherein:
if the first identifier matches the second identifier, the compressed data is generated by compressing a compression group of data including first data corresponding to the first write command and second data corresponding to the second write command; and
if the first identifier does not match the second identifier, first compressed data is generated for the first data and second compressed data is generated for the second data.

### Claim 17 (depends on 16)

The data storage device of claim 16, wherein the controller is further configured to:
write the first data to the memory prior to generating the compressed data; and
after performing the comparison, if the first identifier matches the second identifier:
read the first data from the memory; and
combine the first data and the second data to form the compression group of data.

### Claim 18 (depends on 16)

The data storage device of claim 16, wherein the first identifier and the second identifier are context identifiers received from a host device according to an eMMC standard.

### Claim 19 (depends on 16)

The data storage device of claim 16, wherein the first identifier and the second identifier are context identifiers received from a host device according to Universal Flash Storage (UFS) standard.

### Claim 20 (depends on 16)

The data storage device of claim 16, wherein the controller is further configured to, if the first identifier matches the second identifier:
write the compressed data to a set of memory addresses of the memory; and
store mapping information that associates the set of memory addresses with a group identifier associated with the compression group of data.

### Claim 21 (depends on 20)

The data storage device of claim 20, wherein the set of memory addresses corresponds to a sequential range of logical block addresses.

### Claim 22 (depends on 20)

The data storage device of claim 20, wherein the controller is further configured to:
receive a read command after storing the mapping information, the read command associated with a particular memory address;
determine whether the particular memory address is associated with the group identifier based on the mapping information;
read each memory address of the set of memory addresses if the particular memory address is associated with the group identifier; and
generate decompressed data corresponding to the compression group of data using data read from the set of memory addresses.

### Claim 23 (depends on 20)

The data storage device of claim 20, wherein the group identifier is a context identifier of the first context or of the second context.

### Claim 24 (depends on 20)

The data storage device of claim 20, wherein the controller is further configured to assign the group identifier to the compression group of data, wherein the group identifier is distinct from the first identifier and is distinct from the second identifier.

### Claim 25 (depends on 16)

The data storage device of claim 16, wherein the memory has a three-dimensional (3D) memory configuration.

### Claim 26 (depends on 25)

The data storage device of claim 25, wherein the 3D memory configuration is monolithically formed in one or more physical levels of arrays of memory cells of a memory die having an active area above a silicon substrate, and wherein the memory die further includes circuitry associated with operation of the memory cells.

### Claim 27

A method comprising:
at a data storage device that includes a controller and a memory, performing:
in response to a read command associated with a particular memory address, determining, based on mapping information that maps memory addresses of the memory to group identifiers associated with compression groups of data, whether the particular memory address is associated with any of the group identifiers; and
if the particular memory address is associated with a group identifier:
determining a set of memory addresses corresponding to a compression group of data identified by the group identifier, the set of memory addresses including the particular memory address and one or more additional memory addresses;
performing a read operation to read compressed data from a set of storage elements of the memory, the set of storage elements corresponding to the set of memory addresses; and
generating decompressed data corresponding to the compressed data.

### Claim 28 (depends on 27)

The method of claim 27, further comprising, if the particular memory address is not associated with any of the group identifiers, performing a read operation to read data from storage elements of the memory that correspond to the particular memory address.

### Claim 29 (depends on 27)

The method of claim 27, wherein the mapping information is stored in the memory by the controller after the controller forms the compression group of data.

### Claim 30 (depends on 27)

The method of claim 27, wherein the group identifier is assigned to the compression group of data by the controller.
