# US 2025/0053521 A1 · Context-based compression in a memory system

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

- Number: US 2025/0053521 A1
- Document ID: US20250053521A1
- Status: Published application
- Kind: A1
- Application number: 18/786,296
- Filed: 2024-07-26
- Published: 2025-02-13
- Earliest claimed: 2023-08-09
- Assignees: Rambus Inc.
- Applicants: Rambus Inc.
- Inventors: Evan Lawrence Erickson
- Web page: https://patentgrep.com/patent/US20250053521A1

## CPC

- G06F 13/1673: {using buffers}
- G06F 12/0292: {using tables or multilevel address translation means (G06F12/023 takes precedence; address translation in virtual memory systems G06F12/10)}
- G06F 12/04: Addressing variable-length words or parts of words
- G06F 12/1027: using associative or pseudo-associative address translation means, e.g. translation look-aside buffer [TLB]
- G06F 12/109: for multiple virtual address spaces, e.g. segmentation (G06F12/1036 takes precedence)
- G06F 13/4282: {on a serial bus, e.g. I2C bus, SPI bus (on daisy chain buses G06F13/4247)}
- G06F 12/0284: {Multiple user address space allocation, e.g. using different base addresses (interprocessor communication G06F15/163)}
- G06F 12/1009: using page tables, e.g. page table structures
- G06F 2212/1024: Latency reduction
- G06F 2212/401: Compressed data
- G06F 2212/684: TLB miss handling
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A memory system selectively compresses and/or decompresses pages of a memory array based on requests from a host device. Upon performing compression, the memory buffer device returns compression context metadata to the host device for storing in the page table of the host device to enable the host device to subsequently obtain data from the compressed page. The host device may subsequently send a request for the memory buffer device to perform decompression to a free page in the memory array for accessing by the host device, or the host device may directly access the compressed page for local decompression and storage.

## Claims

### Claim 1

A memory buffer device comprising:
a host-side interface to receive a request from a host device to compress a selected page into a compressed page, and to send at least a subset of compression context metadata to the host device that enables the host device to subsequently obtain data from the compressed page;
a memory-side interface to communicate with a memory array; and
a compression controller to determine an address in the memory array for storing the compressed page, to perform compression of the selected page, to facilitate memory operations via the memory-side interface to store the compressed page to the address in the memory array, and to generate the compression context metadata.

### Claim 2 (depends on 1)

The memory buffer device of claim 1, wherein the host-side interface further receives a request from the host device referencing the compressed page, and wherein the compression controller is further configured to facilitate access to the data from the compressed page responsive to the request.

### Claim 3 (depends on 2)

The memory buffer device of claim 2, wherein the compression controller decompresses the compressed page based on the compression context metadata to generate a decompressed page, and enables the host device to access the decompressed page via the host-side interface.

### Claim 4 (depends on 2)

The memory buffer device of claim 2, wherein the compression controller is further configured to receive a memory access from the host device for compressed data of the compressed page and to send the compressed data to the host device via the host-side interface responsive to the memory access.

### Claim 5 (depends on 1)

The memory buffer device of claim 1, wherein the compression context metadata includes a pointer to the compressed page and one or more decompression parameters, and wherein the compression controller stores the one or more decompression parameters in uncompressed form at a physical address of the memory array associated with the compressed page, and wherein the compression controller sends the pointer to the host device via the host-side interface.

### Claim 6 (depends on 5)

The memory buffer device of claim 5, wherein the host-side interface further receives a request from the host device to decompress the compressed page, wherein the request includes the pointer to the compressed page, and wherein the compression controller is further configured to retrieve the one or more decompression parameters in response to the request.

### Claim 7 (depends on 1)

The memory buffer device of claim 1, wherein the memory buffer device is integrated in a serial-attached memory module and wherein the host-side interface comprises a serial communication link.

### Claim 8

A method for managing a compression and decompression of data in a memory array, the method comprising:
receiving, at a host-side interface of a memory buffer device, a request from a host device to compress a selected page into a compressed page;
determining, by the memory buffer device, an address in the memory array for storing the compressed page;
performing, by the memory buffer device, compression of the selected page;
facilitating, by the memory buffer device, one or more memory operations to store the compressed page to the address in the memory array;
generating, by the memory buffer device, compression context metadata that enables the host device to subsequently obtain data from the compressed page; and
sending at least a subset of the compression context metadata to the host device via the host-side interface of the memory buffer device.

### Claim 9 (depends on 8)

The method of claim 8, further comprising:
receiving, at the host-side interface of the memory buffer device, a request from the host device to decompress the compressed page;
decompressing the compressed page based on the compression context metadata to generate a decompressed page accessible to the host device via the host-side interface.

### Claim 10 (depends on 8)

The method of claim 8, further comprising:
receiving, at the host-side interface, a memory access from the host device for compressed data in the compressed page; and
sending the compressed data to the host device via the host-side interface responsive to the memory access.

### Claim 11 (depends on 8)

The method of claim 8, wherein the compression context metadata includes a pointer to the compressed page and one or more decompression parameters, and wherein sending at least the subset of the compression context metadata to the host device comprises:
storing, the decompression parameters in uncompressed form at a physical address of the memory array associated with the compressed page; and
sending the pointer to the host device via the host-side interface.

### Claim 12 (depends on 11)

The method of claim 11, further comprising:
receiving, at the host-side interface, a request from the host device to access the compressed page, the request including the pointer to the compressed page; and
retrieving the one or more decompression parameters in response to the request; and
decompressing the page to a physical address of the memory array based on the decompression parameters.

### Claim 13 (depends on 11)

The method of claim 11, wherein the memory buffer device is integrated in a serial-attached memory module and wherein the host-side interface comprises a serial communication link.

### Claim 14

A method for operating a host device, comprising:
selecting a page of a memory array for compression;
sending a compression request to a memory buffer device to cause the memory buffer device to compress the page into a compressed page and store the compressed page in the memory array;
obtaining, from the memory buffer device, compression context metadata associated with the compressed page that enables the host device to subsequently obtain data from the compressed page; and
storing the compression context metadata to a page table of the host device.

### Claim 15 (depends on 14)

The method of claim 14, further comprising:
obtaining a memory access request associated with a virtual address;
identifying a physical address of the compressed page associated with the virtual address; and
executing a page fault handler to facilitate decompression of the compressed page.

### Claim 16 (depends on 15)

The method of claim 15, wherein executing the page fault handler comprises:
sending a memory access for the compressed page to the memory buffer device;
responsive to the request, reading the compressed page from the memory buffer device; and
performing decompression of the compressed page to a local memory of the host device.

### Claim 17 (depends on 15)

The method of claim 15, wherein executing the page fault handler comprises:
sending a request for the memory buffer device to decompress the compressed page to a decompressed page; and
following decompression, reading the decompressed page from the memory buffer device.

### Claim 18 (depends on 14)

The method of claim 14, wherein obtaining the compression context metadata comprises obtaining a pointer to the compressed page.

### Claim 19 (depends on 14)

The method of claim 14, wherein obtaining the compression context metadata comprises obtaining a pointer to the compressed page and one or more decompression parameters for decompressing the compressed page.

### Claim 20 (depends on 14)

The method of claim 14, wherein the memory buffer device is integrated in a serial-attached memory module and wherein the host device communicates with the memory buffer device over a serial communication link.
