# US 2025/0370656 A1 · Memory system and operation methods thereof

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

- Number: US 2025/0370656 A1
- Document ID: US20250370656A1
- Status: Published application
- Kind: A1
- Application number: 18/731,795
- Filed: 2024-06-03
- Published: 2025-12-04
- Earliest claimed: 2024-05-30
- Assignees: Yangtze Memory Technologies Co., Ltd.
- Applicants: Yangtze Memory Technologies Co., Ltd.
- Inventors: Yue MA
- Web page: https://patentgrep.com/patent/US20250370656A1

## CPC

- G06F 3/0659: {Command handling arrangements, e.g. command buffers, queues, command scheduling}
- G06F 3/0604: {Improving or facilitating administration, e.g. storage management}
- G06F 3/061: {Improving I/O performance}
- G06F 3/064: {Management of blocks}
- G06F 3/0644: {Management of space entities, e.g. partitions, extents, pools}
- 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

In certain aspects, a method of operating a memory system is disclosed. A write command is received, which indicates that a length of data transferred from a host is smaller than a length of a minimal writable data unit of the memory system. Responsive to the write command, the data is stored in the memory device.

## Claims

### Claim 1

A method of operating a memory system, comprising:
receiving a write command that indicates that a length of data transferred from a host is smaller than a length of a minimal writable data unit of the memory system; and
responsive to the write command, store the data in the memory device.

### Claim 2 (depends on 1)

The method of claim 1, wherein the write command comprises an effective length field indicative of the length of the data.

### Claim 3 (depends on 1)

The method of claim 1, wherein the write command further comprises a dummy control field indicative of a location of the data within the minimal writable data unit.

### Claim 4 (depends on 3)

The method of claim 3, wherein the write command further comprises an enable field indicative of whether to enable padding the data with dummy data on the memory system.

### Claim 5 (depends on 4)

The method of claim 4, wherein:
responsive to the enable field having an enabled value, the padding of the data is enabled on the memory system.

### Claim 6 (depends on 5)

The method of claim 5, wherein the write command further comprises a transfer length field indicative of the length of the minimal writable data unit.

### Claim 7 (depends on 6)

The method of claim 6, wherein the write command further comprises a logical block address (LBA) field indicative of a logical location where the data is to be stored in the memory device.

### Claim 8 (depends on 2)

The method of claim 2, wherein the write command is received by a frontend interface of the memory system, and the method further comprises:
receiving, by the frontend interface, the data that has the length indicated by the effective length field from the host.

### Claim 9 (depends on 7)

The method of claim 7, wherein responsive to the write command, store the data in the memory device comprises:
determining an LBA based on the LBA field;
responsive to the enable field having the enabled value, padding the data with the dummy data to generate padded data based on the transfer length field and the dummy control field, wherein a length of the padded data is equal to the length of the minimal writable data unit; and
storing the padded data in the memory device based on the LBA.

### Claim 10 (depends on 9)

The method of claim 9, wherein:
a logical space of the memory device is divided into a plurality of zones; and
each zone includes a plurality of logical blocks corresponding to a plurality of LBAs, and the plurality of logical blocks are written in sequence.

### Claim 11 (depends on 10)

The method of claim 10, wherein:
a logical block indicated by the LBA is a next logical block to be written in a zone of the memory device; and
storing the padded data in the memory device based on the LBA comprises storing the padded data in the memory device such that the data is stored in a physical region corresponding to the logical block indicated by the LBA.

### Claim 12 (depends on 11)

The method of claim 11, wherein the data and other data written in the zone are associated with an identical application.

### Claim 13 (depends on 1)

The method of claim 1, wherein Zoned Namespace (ZNS) is implemented in the memory system.

### Claim 14

A memory system, comprising:
a memory device; and
a memory controller coupled to the memory device, comprising:
a frontend interface configured to receive a write command that indicates that a length of data transferred from a host is smaller than a length of a minimal writable data unit of the memory system; and
a processor coupled to the frontend interface and configured to instruct the memory device to store the data responsive to the write command.

### Claim 15 (depends on 14)

The memory system of claim 14, wherein the write command comprises at least one of:
an effective length field indicative of the length of the data;
a dummy control field indicative of a location of the data within the minimal writable data unit;
an enable field indicative of whether to enable padding the data with dummy data on the memory system;
a transfer length field indicative of the length of the minimal writable data unit; or
a logical block address (LBA) field indicative of a logical location where the data is to be stored in the memory device.

### Claim 16 (depends on 15)

The memory system of claim 15, wherein the frontend interface is further configured to:
receive the data that has the length indicated by the effective length field from the host.

### Claim 17 (depends on 15)

The memory system of claim 15, wherein to instruct the memory device to store the data responsive to the write command, the processor is further configured to:
determine an LBA based on the LBA field;
responsive to the enable field having an enabled value, pad the data with the dummy data to generate padded data based on the transfer length field and the dummy control field, wherein a length of the padded data is equal to the length of the minimal writable data unit; and
instruct the memory device to store the padded data based on the LBA.

### Claim 18 (depends on 17)

The memory system of claim 17, wherein:
a logical space of the memory device is divided into a plurality of zones; and
each zone includes a plurality of logical blocks corresponding to a plurality of LBAs, and the plurality of logical blocks are written in sequence.

### Claim 19 (depends on 18)

The memory system of claim 18, wherein:
a logical block indicated by the LBA is a next logical block to be written in a zone of the memory device; and
to instruct the memory device to store the padded data based on the LBA, the processor is further configured to:
determine a physical region of the memory device corresponding to the logical block indicated by the LBA; and
instruct the memory device to store the padded data in the memory device such that the data is stored in the physical region.

### Claim 20

A host, comprising:
a processor configured to generate a write command that indicates that a length of data to be transferred to a memory system is smaller than a length of a minimal writable data unit of the memory system; and
a storage interface coupled to the processor and configured to send the write command to the memory system.
