# US 2026/0267658 A1 · Storage management in a firmware framework

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

- Number: US 2026/0267658 A1
- Document ID: US20260267658A1
- Status: Published application
- Kind: A1
- Application number: 19/071,540
- Filed: 2025-03-05
- Published: 2026-09-10
- Earliest claimed: 2025-03-05
- Assignees: Dell Products L.P.
- Applicants: Dell Products L.P.
- Inventors: Ibrahim Sayyed; Daniel L. Hamlin; Amit K. Tiwari
- Web page: https://patentgrep.com/patent/US20260267658A1

## CPC

- G06F 9/4411: {Configuring for operating with peripheral devices; Loading of device drivers}
- G06F 9/44505: {Configuring for program initiating, e.g. using registry, configuration files}
- G06F 9/4405: {Initialisation of multiprocessor systems}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Systems and methods for storage management in a firmware framework are described. In an illustrative, non-limiting embodiment, an Information Handling System (IHS) may include: a controller, where the controller includes firmware that, upon execution by a processing core, causes the processing core to instantiate an orchestrator of a firmware framework; and a plurality of devices coupled to the controller, where each device of the plurality of devices comprises firmware that, upon execution by a corresponding processing core, causes the corresponding processing core to produce a node coupled to the orchestrator via the firmware framework, and where the orchestrator is configured to: receive a storage management policy; and manage a storage capability of at least one of the plurality of devices based, at least in part, upon the storage management policy.

## Claims

### Claim 1

An Information Handling System (IHS), comprising:
a controller, wherein the controller comprises firmware that, upon execution by a processing core, causes the processing core to instantiate an orchestrator of a firmware framework; and
a plurality of devices coupled to the controller, wherein each device of the plurality of devices comprises firmware that, upon execution by a corresponding processing core, causes the corresponding processing core to produce a node coupled to the orchestrator via the firmware framework, and wherein the orchestrator is configured to:
receive a storage management policy; and
manage a storage capability of at least one of the plurality of devices based, at least in part, upon the storage management policy.

### Claim 2 (depends on 1)

The IHS of claim 1, wherein the controller comprises an Embedded Controller (EC) or Baseband Management Controller (BMC).

### Claim 3 (depends on 1)

The IHS of claim 1, wherein the plurality of devices comprises at least one of: a sensor, a sensor hub, a Central Processing Unit (CPU), a Graphical Processing Unit (GPU), an audio Digital Signal Processor (aDSP), a Neural Processing Unit (NPU), a Tensor Processing Unit (TPU), a Neural Network Processor (NNP), an Intelligence Processing Unit (IPU), an Image Signal Processor (ISP), a Video Processing Unit (VPU), a camera controller, an audio controller, a memory, a Universal Serial Bus (USB) device, a Peripheral Component Interconnect express (PCIe) device, or a Trusted Platform Module (TPM).

### Claim 4 (depends on 1)

The IHS of claim 1, wherein at least one of the plurality of devices is coupled to the controller via at least one of: a Systems-on-Chip (SoC) interconnect, a Peripheral Component Interconnect Express (PCIe) bus, or a Universal Serial Bus (USB) port.

### Claim 5 (depends on 4)

The IHS of claim 4, wherein the SoC interconnect comprises at least one of: an Advanced Microcontroller Bus Architecture (AMBA) bus, a QuickPath Interconnect (QPI) bus, or a HyperTransport (HT) bus.

### Claim 6 (depends on 1)

The IHS of claim 1, wherein the storage capability comprises at least one of: a storage location, a type of memory, an amount of available storage space, a duration for which data can be stored, a priority level for data storage, read/write speed, a data encryption capability, an error correction feature, or a redundancy mechanism.

### Claim 7 (depends on 1)

The IHS of claim 1, wherein storage capabilities are advertised by the plurality of devices as exposed services in the firmware framework.

### Claim 8 (depends on 1)

The IHS of claim 1, wherein the storage management policy comprises one or more rules that, upon enforcement by the orchestrator, causes the orchestrator to, in response to a request to store data, select a memory associated with a chosen device among the plurality of devices to store the data based, at least in part, upon the storage capability.

### Claim 9 (depends on 8)

The IHS of claim 8, wherein the request is received by at least one of: a given device in the firmware framework, or a host OS.

### Claim 10 (depends on 9)

The IHS of claim 9, wherein the request is received in response to the given device's performance of a telemetry collection operation.

### Claim 11 (depends on 1)

The IHS of claim 1, wherein the orchestrator is configured to identify, based at least in part upon the storage management policy, at least one of: (a) the chosen device among the plurality of devices; or (b) the selected memory among a plurality of memories available to the chosen device.

### Claim 12 (depends on 11)

The IHS of claim 11, wherein the storage management policy comprises at least one context-based rule that enables the orchestrator to identify at least one of the chosen device or the selected memory based on contextual information.

### Claim 13 (depends on 12)

The IHS of claim 12, wherein the contextual information comprises at least one of: a status of the IHS, failure data, environmental condition, user activity, user presence, IHS posture, geographic location, scheduled maintenance event, or security threat.

### Claim 14 (depends on 12)

The IHS of claim 12, wherein the contextual information comprises at least one of: device usage, memory usage, disk I/O activity, network bandwidth consumption, power consumption, or thermal load.

### Claim 15 (depends on 12)

The IHS of claim 12, wherein the orchestrator is configured to determine that the device usage of the chosen device or selected memory crosses a threshold and, in response to the determination, migrate the data.

### Claim 16 (depends on 12)

The IHS of claim 12, wherein the orchestrator is configured to determine that the chosen device requested release of the selected memory or issue anther request to store other data and, in response to the determination, select another memory associated with another chosen device among the plurality of devices to store the other data.

### Claim 17 (depends on 1)

The IHS of claim 1, wherein the storage management policy is provided by an Information Technology Decision Maker (ITDM) or Original Equipment Manufacturer (OEM).

### Claim 18 (depends on 1)

The IHS of claim 1, wherein the orchestrator is configured to enforce the storage management policy without any involvement by any host Operating System (OS) of the IHS.

### Claim 19

A method, comprising:
producing, by an Embedded Controller (EC) of an Information Handling System (IHS), an orchestrator;
producing, by a plurality of devices coupled to the EC, a plurality of nodes participating with the orchestrator in a firmware framework; and
in response to a request by a given device to store overflow data, selecting a memory associated with a chosen device among the plurality of devices to store the overflow data based, at least in part, upon a storage capability advertised by the chose device as an exposed service in the firmware framework.

### Claim 20

An Embedded Controller (EC) integrated into or coupled to a heterogeneous computing platform of an Information Handling System (IHS), the EC comprising:
a processing core distinct from any host processor of the heterogeneous computing platform; and
a memory coupled to the processing core, the memory having firmware instructions stored thereon that, upon execution by the processing core, cause the EC to:
identify a storage need; and
select a memory associated with a chosen device among the plurality of devices in response to the identification based, at least in part, upon a storage management policy provided by an Information Technology Decision Maker (ITDM) or Original Equipment Manufacturer (OEM).
