Containerized Management Controller Plugins for Secure Runtime Updates

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing management controllers in information handling systems are monolithic, limiting dynamic feature extension and security, leading to inefficient thermal management and increased power consumption due to unsupported hardware, and lacking real-time update capabilities for advanced functionalities like cloud integration and AI/ML-based anomaly detection.

Innovation Solution

A management controller architecture that allows installation of plugin applications at runtime, with cryptographic verification, sandboxing, and runtime integrity checks to maintain hardware root of trust, enabling secure and efficient integration of unsupported hardware and dynamic feature enhancements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If monolithic firmware image is used, then security is improved through cryptographic signing and hardware root of trust, but adaptability deteriorates as customers cannot dynamically extend features

Engineering Contradiction:

ImprovesecurityVSAvoiddynamic feature extension

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The firmware is segmented into a base monolithic image and separate plugin modules. The base image maintains security through cryptographic signing and hardware root of trust, while plugins provide extendable functionality. This segmentation allows the system to achieve both security (through the signed base image) and adaptability (through loadable plugins).

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Plugins are nested within the firmware architecture as loadable components that can be dynamically loaded onto the management controller. This nested structure allows the monolithic base firmware to contain security-critical code while nested plugins provide feature extensions without compromising the security foundation.

Inventive Principle:

Principle #7Nested doll (Nesting)

2Reliability

If conservative cooling levels are used for unsupported hardware, then system reliability is improved by avoiding thermal throttling, but power consumption increases

Engineering Contradiction:

Improvethermal managementVSAvoidpower consumption

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

Plugins provide thermal management capabilities that allow the system to self-optimize cooling for unsupported hardware. Instead of relying on conservative default settings, the system can load specialized thermal management plugins that understand the specific thermal characteristics of add-on cards, enabling aggressive but safe cooling strategies.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system changes thermal management parameters dynamically by loading different plugins. When unsupported hardware is detected, the system can load a plugin that modifies fan curves, cooling fan speeds, and thermal thresholds to optimize for that specific hardware, rather than using generic conservative parameters.

Inventive Principle:

Principle #35Parameter changes

3Adaptability or versatility

If custom code is written for each unsupported card, then adaptability is improved, but device complexity increases

Engineering Contradiction:

Improvehardware supportVSAvoidcode integration

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

Instead of integrating custom code directly into the monolithic firmware for each hardware type, the code is segmented into separate plugin modules. Each plugin handles a specific hardware type or function, making the system more adaptable to new hardware while reducing the complexity of the base firmware.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The plugin architecture provides a universal interface that allows different plugins to handle various unsupported hardware types through a standardized mechanism. This universal approach reduces complexity by using a single integration framework rather than separate integration methods for each hardware type.

Inventive Principle:

Principle #6Universality (Multi-functionality)

4Ease of manufacture

If monolithic firmware is used, then manufacturing simplicity is improved, but productivity deteriorates due to inability to add features without reflash

Engineering Contradiction:

Improvefirmware deliveryVSAvoidfeature deployment speed

Core Design Contradiction:

Ease of manufactureVSProductivity

Solution Approach 1:

The firmware is segmented into a base image and interchangeable plugins. The base image maintains simple manufacturing and distribution processes, while plugins enable rapid feature deployment without requiring complete firmware reflashes, thus improving productivity.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system transitions from a static monolithic firmware to a dynamic architecture where plugins can be loaded and unloaded at runtime. This dynamic capability allows features to be added or updated without manufacturing changes or complete reflashes, significantly improving deployment speed and productivity.

Inventive Principle:

Principle #15Dynamics

Data Source

PatentUS12450333B2Secure management controller enhancement with containerized applications

Publication Date: 2025.10.21 DELL PROD LP

AI summary

An information handling system may include a host system; and a management controller comprising at least one management controller processor and a management controller storage resource. The management controller may be configured to: install a firmware image onto the management controller storage resource; subsequent to installing the firmware image, receive a plugin application; cryptographically verify a source of the plugin application; install the plugin application onto the management controller storage resource; and execute the plugin application.