MQTT Out-of-Band Management for Low-Power ARM Platforms

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

ARM-based platforms lack Embedded Controllers (ECs) capable of supporting Out-of-Band (OOB) management, which is crucial for remote management and control of Information Handling Systems (IHSs).

Innovation Solution

Implementing a Message Queuing Telemetry Transport (MQTT) protocol for OOB manageability in heterogeneous computing platforms, utilizing an OOB Microcontroller Unit (MCU), Embedded Controller (EC), or network device to establish a connection with a cloud service even when host processors are in a low-power state, enabling remote management and initialization of BIOS/UEFI without video device initialization, and switching to TCP/IP for larger data transfers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Use of energy by moving object

If ARM-based platforms are used without traditional ECs, then power efficiency and modern architecture are improved, but OOB management capability is lost

Engineering Contradiction:

Improvepower efficiencyVSAvoidOOB management capability

Core Design Contradiction:

Use of energy by moving objectVSReliability

Solution Approach 1:

The system separates management functions from the main host processor by implementing a dedicated OOB MCU that operates independently. This segmentation allows the ARM-based platform to maintain power efficiency while the OOB MCU provides specialized OOB management capabilities without requiring the entire system to wake up.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The OOB MCU acts as an intermediary between the cloud service and the host processor. It establishes and maintains OOB connections independently, retrieving management packets and commands without requiring the host processor to be active, thus preserving both power efficiency and OOB management capability.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Use of energy by moving object

If host processor remains in low-power state, then power consumption is reduced, but remote management operations cannot be performed

Engineering Contradiction:

Improvepower consumptionVSAvoidremote management operations

Core Design Contradiction:

Use of energy by moving objectVSEase of operation

Solution Approach 1:

The OOB MCU is designed to autonomously perform OOB management operations without requiring host processor intervention. It can independently establish connections, retrieve management packets, execute commands, and initialize BIOS/UEFI, enabling remote management while the host processor remains in low-power state.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The OOB MCU performs preliminary actions by pre-retrieving and buffering management packets from the cloud service before the host processor needs to wake up. This allows management operations to be prepared in advance, ensuring ease of operation when the host becomes active.

Inventive Principle:

Principle #10Preliminary action

3Use of energy by moving object

If MQTT protocol is used for OOB connection, then low-power operation is enabled, but large data transfer capability is limited

Engineering Contradiction:

Improvelow-power operationVSAvoiddata transfer volume

Core Design Contradiction:

Use of energy by moving objectVSQuantity of substance

Solution Approach 1:

The system dynamically adapts its communication protocol based on the operation type. MQTT is used for maintaining OOB connections and retrieving small management packets during low-power operation, while TCP/IP is switched to for large data transfers such as firmware updates, optimizing both power efficiency and data transfer capability.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The communication protocol parameters are changed based on the data transfer requirements. The OOB MCU can switch between MQTT (for low-power, small data operations) and TCP/IP (for high-bandwidth, large data operations), allowing the system to optimize the balance between power consumption and data transfer volume.

Inventive Principle:

Principle #35Parameter changes

Data Source

PatentUS12537873B2Message queuing telemetry transport (MQTT) for out-of-band manageability in heterogeneous computing platforms

Publication Date: 2026.01.27 DELL PROD LP

AI summary

Systems and methods for Message Queuing Telemetry Transport (MQTT) for Out-of-Band (OOB) manageability in heterogeneous computing platforms. In some embodiments, an Information Handling System (IHS) may include a heterogeneous computing platform comprising a plurality of devices, and an OOB Microcontroller Unit (MCU), an Embedded Controller (EC), or a network device integrated into or coupled to the heterogeneous computing platform and distinct from any host processor of the heterogeneous computing platform, wherein the OOB MCU, EC, or network device is configured to: establish an OOB connection with a cloud service via a light communication protocol while every host processor of the heterogeneous computing platform is in a low-power state, and retrieve one or more OOB packets from the cloud service via the OOB connection.