# US 2025/0147892 A1 · Storage controller, storage device including the same, and method of operating storage device

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

- Number: US 2025/0147892 A1
- Document ID: US20250147892A1
- Status: Published application
- Kind: A1
- Application number: 18/819,398
- Filed: 2024-08-29
- Published: 2025-05-08
- Earliest claimed: 2023-11-08
- Assignees: Samsung Electronics Co., Ltd.
- Applicants: Samsung Electronics Co., Ltd.
- Inventors: YEONWOO KIM; SOOJUNG PARK
- Web page: https://patentgrep.com/patent/US20250147892A1

## CPC

- G06F 12/0246: {in block erasable memory, e.g. flash memory}
- G06F 12/0862: with prefetch
- G06F 9/3802: {Instruction prefetching}
- G06F 9/542: {Event management; Broadcasting; Multicasting; Notifications}
- G06F 9/547: {Remote procedure calls [RPC]; Web services}
- G06F 12/0292: {using tables or multilevel address translation means (G06F12/023 takes precedence; address translation in virtual memory systems G06F12/10)}
- G06F 2212/7201: Logical to physical mapping or translation of blocks or pages
- G06F 2212/7203: Temporary buffering, e.g. using volatile buffer or dedicated buffer blocks
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A storage controller, a storage device, and a method of operating the storage device are provided. The storage controller includes a working memory; a processor configured to, in response to an occurrence of an event, execute a first code block and a second code block related to the event, that are loaded into the working memory; a first mapping table that includes first mapping information between the first and second code blocks and the event; and a prefetching memory configured to provide the first code block and the second code block, prefetched based on the first mapping information, to the working memory in a predetermined order.

## Claims

### Claim 1

A storage controller comprising:
a working memory;
a processor configured to, in response to an occurrence of an event, execute a first code block and a second code block related to the event, that are loaded into the working memory;
a first mapping table that includes first mapping information between the first and second code blocks and the event; and
a prefetching memory configured to provide the first code block and the second code block, prefetched based on the first mapping information, to the working memory in a predetermined order.

### Claim 2 (depends on 1)

The storage controller of claim 1, wherein in the working memory, the first code block is overwritten with the second code block, and
wherein the processor is further configured to execute the first code block and then the second code block.

### Claim 3 (depends on 1)

The storage controller of claim 1, wherein the event is based on a request that is provided from an outside.

### Claim 4 (depends on 3)

The storage controller of claim 3, wherein the event is based on a request for modification of a firmware program to be executed in the processor.

### Claim 5 (depends on 1)

The storage controller of claim 1, wherein the event is detected based on internal collected data.

### Claim 6 (depends on 5)

The storage controller of claim 5, wherein the internal collected data is generated based on a count value of a clock signal, and
wherein the event corresponds to an execution of a power management mode by the processor based on the internal collected data.

### Claim 7 (depends on 1)

The storage controller of claim 1, further comprising:
an event trigger module configured to output trigger information based on the occurrence of the event; and
an overlay load manager configured to search for first address data of the first code block and second address data of the second code block, based on the trigger information and the first mapping information.

### Claim 8 (depends on 7)

The storage controller of claim 7, wherein the overlay load manager is further configured to output a read command for the first address data and the second address data to an external non-volatile memory device, based on whether the first code block and the second code block have been prefetched.

### Claim 9 (depends on 7)

The storage controller of claim 7, further comprising:
a tightly coupled memory (TCM), provided to the processor, wherein the event trigger module, the overlay load manager, and the first mapping table are loaded into the TCM.

### Claim 10 (depends on 7)

The storage controller of claim 7, wherein the working memory and the prefetching memory are included in a memory, and
wherein the event trigger module, the overlay load manager, and the first mapping table are loaded into the memory.

### Claim 11 (depends on 7)

The storage controller of claim 7, wherein during a data write operation, the first and second code blocks in the prefetching memory are cleared, and a write command for the write operation is stored in the prefetching memory.

### Claim 12 (depends on 1)

The storage controller of claim 1, wherein the processor is further configured to execute a third code block, the third code block being different from the first code block and the second code block and being related to the event, and
wherein the storage controller further includes a second mapping table that includes second mapping information in association with the event, indicating whether a caching operation on the third code block is to be activated.

### Claim 13 (depends on 12)

The storage controller of claim 12, further comprising:
a caching memory into which the executed third code block is cached.

### Claim 14

A storage device comprising:
a non-volatile memory device configured to store a first code block and a second code block; and
a storage controller including:
a mapping table that includes first mapping information between a first event and the first and second code blocks, the mapping table further including a first address data corresponding to the first code block and a second address data corresponding to the second code block;
a prefetching memory into which the first and second code blocks received from the non-volatile memory device are prefetched; and
a working memory into which the prefetched first and second code blocks are loaded in a predetermined order.

### Claim 15 (depends on 14)

The storage device of claim 14, wherein the mapping table further includes second mapping information between a second event, different from the first event, and the first address data and third address data, the third address data being different from the first and second address data.

### Claim 16 (depends on 14)

The storage device of claim 14, wherein the non-volatile memory device includes a firmware area, in which a firmware to be executed by the storage controller is stored, and a user area, in which data that are input from an outside are stored, and
wherein the firmware area includes a first region in which the first code block is stored, and a second region in which the second code block is stored.

### Claim 17

A method of operating a storage device, the method comprising:
generating a trigger information related to an event, in response to an occurrence of the event;
searching for first address data of a first code block and second address data of a second code block, based on the trigger information, the first and second code blocks being related to the event;
transmitting a read command to a non-volatile memory device based on the first address data and the second address data;
prefetching the first code block and the second code block received from the non-volatile memory device; and
loading the first code block and the second code block into a working memory in a predetermined order.

### Claim 18 (depends on 17)

The method according to claim 17, wherein the generating the trigger information includes receiving an external request corresponding to the event.

### Claim 19 (depends on 17)

The method according to claim 17, further comprising:
transmitting a read command based on third address data of a third code block different from the first and second code blocks.

### Claim 20 (depends on 19)

The method according to claim 19, further comprising:
executing caching on the third code block.

### Claim 21

(canceled)
