UEFI OOB Command Processing for Low-Power Heterogeneous Platforms
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 of Information Handling Systems (IHSs).
Innovation Solution
Implementing an Out-of-Band Microcontroller Unit (MCU), Embedded Controller (EC), or networking device within heterogeneous computing platforms to process OOB commands at the Unified Extensible Firmware Interface (UEFI) level, even when the host processor is in a low-power state, without initializing video devices.
Engineering Contradictions & Design Principles
Engineering 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
Solution Approach 1:
The system separates OOB management functionality from the main host processor by implementing a dedicated OOB processor that can independently handle remote management tasks. This segmentation allows the main processor to focus on primary computing while the OOB processor handles management functions, resolving the contradiction between modern ARM architecture and traditional OOB management capabilities
Solution Approach 2:
A UEFI driver acts as an intermediary layer between the OOB processor and the host system, enabling communication and coordination. The driver facilitates the OOB processor's ability to execute commands and manage the system remotely, bridging the gap between the new ARM-based architecture and established OOB management protocols
2Use of energy by moving object
If the host processor is in low-power state, then power consumption is reduced, but OOB command execution is delayed
Solution Approach 1:
The OOB processor is designed to operate independently and execute commands autonomously without requiring the host processor to be fully active. It can receive and process OOB commands directly while the host processor remains in low-power state, eliminating the time delay while maintaining power efficiency
Solution Approach 2:
The system prepares the OOB processor to be ready for command execution even when the host processor is in low-power state. The OOB processor maintains readiness to execute commands immediately upon receipt, preventing execution delays while the host processor conserves energy
3Adaptability or versatility
If video devices are initialized for UEFI execution, then full system functionality is available, but power consumption increases
Solution Approach 1:
The system implements partial UEFI initialization that provides sufficient functionality for OOB command execution without completing the full initialization sequence. Critical UEFI services are loaded and configured to enable necessary operations, while non-essential components like video devices remain uninitialized, achieving the right balance between functionality and power consumption
Data Source
AI summary
Systems and methods for Unified Extensible Firmware Interface (UEFI)-level processing of Out-of-Band (OOB) commands in heterogeneous computing platforms. In some embodiments, an Information Handling System (IHS) may include: a heterogeneous computing platform having a plurality of devices, and an OOB Microcontroller Unit (MCU), Embedded Controller (EC), or networking device integrated into or coupled to the heterogeneous computing platform and distinct from a host processor of the heterogeneous computing platform, where the OOB MCU, EC, or networking device is configured to: receive an OOB packet while the host processor is in a low-power state, and execute an OOB command contained in the OOB packet, by the host processor, at least in part through initialization of UEFI without initialization of any video device.