# US 2025/0156320 A1 · Dynamic single-level cell write through in memory devices

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

- Number: US 2025/0156320 A1
- Document ID: US20250156320A1
- Status: Published application
- Kind: A1
- Application number: 18/388,782
- Filed: 2023-11-10
- Published: 2025-05-15
- Earliest claimed: 2023-11-10
- Assignees: SK Hynix NAND Product Solutions Corp. (dba Solidigm)
- Applicants: SK Hynix NAND Product Solutions Corp. (dba Solidigm)
- Inventors: George KALWITZ
- Web page: https://patentgrep.com/patent/US20250156320A1

## CPC

- G06F 12/0246: {in block erasable memory, e.g. flash memory}
- G06F 12/0802: Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches
- G06F 3/0604: {Improving or facilitating administration, e.g. storage management}
- G06F 3/0655: {Vertical data movement, i.e. input-output transfer; data movement between one or more hosts and one or more storage devices}
- G06F 3/0679: {Non-volatile semiconductor memory device, e.g. flash memory, one time programmable memory [OTP]}
- G11C 11/5628: {Programming or writing circuits; Data input circuits}
- G06F 12/0871: Allocation or management of cache space
- G06F 12/0888: using selective caching, e.g. bypass
- G06F 2212/1016: Performance improvement
- G06F 2212/1044: Space efficiency improvement
- G06F 2212/222: Non-volatile memory
- G06F 2212/313: In storage device
- G06F 2212/502: using adaptive policy
- G06F 2212/60: Details of cache memory
- G06F 2212/7203: Temporary buffering, e.g. using volatile buffer or dedicated buffer blocks
- G06F 2212/7204: Capacity control, e.g. partitioning, end-of-life degradation
- G06F 2212/7206: Reconfiguration of flash memory system
- G06F 2212/7208: Multiple device management, e.g. distributing data over multiple flash devices
- G11C 2211/5641: Multilevel memory having cells with different number of storage levels
- G11C 2211/5643: Multilevel memory comprising cache storage devices
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G11C: STATIC STORES (semiconductor memory devices H10B)

## Abstract

This application is directed to writing data in a memory device supporting multiple bits per cell by dynamically using a y-level cell (YLC) cache. The memory device is coupled into a host device, and includes a plurality of x-level cell (XLC) memory blocks, where x is greater than one and greater than y. The memory device identifies a write shaping status of the host device. Based on the write shaping status, the memory device determines that the host device performs write operations without a memory-based cache. In accordance with a determination that the host device performs write operations without the memory-based cache, a YLC cache is allocated in the memory device to act as the memory-based cache. In response to one or more write requests, the memory device stores data into the plurality of XLC memory blocks via the YLC cache.

## Claims

### Claim 1

A method implemented at an electronic device including a host device and a memory device, comprising:
identifying a write shaping status of the host device, wherein the memory device is coupled to the host device and includes a plurality of x-level cell (XLC) memory blocks, wherein x is greater than one:
based on the write shaping status, determining that the host device performs write operations without a memory-based cache:
in accordance with a determination that the host device performs write operations without the memory-based cache, allocating a y-level cell (YLC) cache in the memory device to act as the memory-based cache, wherein y is less than x; and
in response to one or more write requests, storing data into the plurality of XLC memory blocks via the YLC cache in the memory device.

### Claim 2 (depends on 1)

The method of claim 1, wherein the identifying the write shaping status comprises:
receiving a notification by the memory device from the host device; and
determining the write shaping status of the host device by determining, based on the notification, whether the host device supports write operations via the memory-based cache, wherein the YLC cache is allocated for writing data in the memory device when the host device does not support write operations via the memory-based cache.

### Claim 3 (depends on 3)

The method of claim 3, wherein the notification comprises at least one of:
an identify controller (IDC) command received during device discovery:
a get/set features (GSF) notification:
a write pressure bandwidth requirement;
a write-shaping notification: or a shaping size notification.

### Claim 4 (depends on 1)

The method of claim 1, wherein the identifying the write shaping status comprises:
receiving at least one write command by the memory device from the host device for writing host data:
detecting an input/output (I/O) pattern based on the at least one write command: and
determining the write shaping status of the host device by determining whether the I/O pattern indicates sequential data regions or random data regions with respect to logical block addressing (LBA), wherein the YLC cache is allocated for writing data in the memory device when the I/O pattern indicates random data regions with respect to LBA.

### Claim 5 (depends on 1)

The method of claim 1, wherein the storing data into the plurality of XLC memory blocks comprises:
receiving host data from the host device according to the one or more write requests: and
storing the host data in the memory device by:
writing the host data in a plurality of memory blocks in the YLC cache, wherein each of the plurality of memory blocks is located in a different die of the memory device respectively, and
moving data from the YLC cache to one memory block in the plurality of XLC memory blocks when the YLC cache is full or has enough data to complete a XLC program cycle.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
monitoring write environment information for writing data in the memory device: and
dynamically adjusting a size of the YLC cache based on the write environment information.

### Claim 7 (depends on 6)

The method of claim 6, wherein the write environment information comprises at least one of:
information related to an identify controller (IDC) command received during device discovery:
a write workload detected from the host device:
a write pressure bandwidth requirement: or
a shaping size notification.

### Claim 8 (depends on 6)

The method of claim 6, further comprising:
monitoring a write workload from the host device; and
dynamically adjusting the size of the YLC cache based on the write workload, wherein:
the size of the YLC cache is increased as the write workload becomes higher,
the size of the YLC cache is decreased as the write workload becomes lower.

### Claim 9 (depends on 6)

The method of claim 6, further comprising:
monitoring a degree of data burstiness from the host device: and
dynamically adjusting the size of the YLC cache based on the degree of data burstiness, wherein:
the size of the YLC cache is increased as the degree of data burstiness becomes lower,
the size of the YLC cache is decreased as the degree of data burstiness becomes higher.

### Claim 10 (depends on 6)

The method of claim 6, further comprising:
monitoring a degree of write pressure from the host device; and
dynamically adjusting the size of the YLC cache based on the degree of write pressure, wherein:
the size of the YLC cache is increased when the degree of write pressure becomes higher and is smaller than a predetermined threshold,
the size of the YLC cache is decreased when the degree of write pressure becomes lower and is smaller than the predetermined threshold, and
the YLC cache is disabled and data from the host device is written directly to the plurality of XLC memory blocks when the degree of write pressure is larger than the predetermined threshold.

### Claim 11 (depends on 6)

The method of claim 6, wherein the write environment information is monitored based on a machine learning model or an artificial intelligence (AI) model.

### Claim 12 (depends on 1)

The method of claim 1, further comprising:
initiating the YLC cache with a default size smaller than a predetermined threshold: and
writing data into the plurality of XLC memory blocks via the YLC cache in the memory device as a default mode.

### Claim 13

A memory device, comprising:
a plurality of x-level cell (XLC) memory blocks, wherein x is greater than one:
ay-level cell (YLC) cache, wherein y is less than x; and
a memory controller operable to execute instructions which when executed cause the memory controller to perform operations comprising:
identifying a write shaping status of a host device coupled to the memory device,
based on the write shaping status, determining that the host device performs write operations without a memory-based cache, and
in accordance with a determination that the host device performs write operations without the memory-based cache, storing data into the plurality of XLC memory blocks via the YLC cache in the memory device in response to one or more write requests from the host device.

### Claim 14 (depends on 13)

The memory device of claim 13, wherein the identifying the write shaping status comprises:
receiving a notification from the host device: and
determining the write shaping status of the host device by determining, based on the notification, whether the host device supports write operations via the memory-based cache, wherein the YLC cache is allocated for writing data in the memory device when the host device does not support write operations via the memory-based cache.

### Claim 15 (depends on 14)

The memory device of claim 14, wherein the notification comprises at least one of:
an identify controller (IDC) command received during device discovery:
a get/set features (GSF) notification:
a write pressure bandwidth requirement;
a write-shaping notification: or
a shaping size notification.

### Claim 16 (depends on 13)

The memory device of claim 13, wherein the identifying the write shaping status comprises:
receiving at least one write command from the host device for writing host data:
detecting an input/output (I/O) pattern based on the at least one write command; and
determining the write shaping status of the host device by determining whether the I/O pattern indicates sequential data regions or random data regions with respect to logical block addressing (LBA), wherein the YLC cache is allocated for writing data in the memory device when the I/O pattern indicates random data regions with respect to LBA.

### Claim 17 (depends on 13)

The memory device of claim 13, wherein the storing data into the plurality of XLC memory blocks comprises:
receiving host data from the host device according to the one or more write requests: and
storing the host data in the memory device by:
writing the host data in a plurality of memory blocks in the YLC cache, wherein each of the plurality of memory blocks is located in a different die of the memory device respectively, and
moving data from the YLC cache to one memory block in the plurality of XLC memory blocks when the YLC cache is full or has enough data to complete a XLC program cycle.

### Claim 18 (depends on 13)

The memory device of claim 13, wherein the operations further comprise:
monitoring write environment information for writing data in the memory device; and
dynamically adjusting a size of the YLC cache based on the write environment information.

### Claim 19

An electronic system, comprising:
a host device: and
a memory device coupled to the host device and configured to perform operations comprising:
identifying a write shaping status of the host device, wherein the memory device is coupled to the host device and includes a plurality of x-level cell (XLC) memory blocks, wherein x is greater than one,
based on the write shaping status, determining that the host device performs write operations without a memory-based cache,
in accordance with a determination that the host device performs write operations without the memory-based cache, allocating a y-level cell (YLC) cache in the memory device to act as the memory-based cache, wherein y is less than x, and
in response to one or more write requests, storing data into the plurality of XLC memory blocks via the YLC cache in the memory device.

### Claim 20 (depends on 19)

The electronic system of claim 19, wherein the operations further comprise:
in accordance with a determination that the host device performs write operations via the memory-based cache, writing data from the host device directly to the plurality of XLC memory blocks without going through the YLC cache.
