OOB MCU Interconnect for Waking Devices in Low-Power Platforms
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
ARM-based platforms lack Embedded Controllers (ECs) necessary for Out-of-Band (OOB) management, which is crucial for remote management and control of Information Handling Systems (IHSs).
Innovation Solution
Integrate an Out-of-Band Microcontroller Unit (MCU) into heterogeneous computing platforms to manage devices and transmit commands to selected devices while the host processor is in a low-power state, using an interconnect architecture that supports various devices such as GPUs, audio DSPs, sensor hubs, and AI processors.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Use of energy by moving object
If ARM-based platforms are used without Embedded Controllers, then power consumption is reduced and platform simplicity is improved, but Out-of-Band management capability is lost
Solution Approach 1:
The system segments management functions by integrating a dedicated OOB MCU that operates independently from the host processor. This separate management controller can be powered independently, allowing OOB management to function even when the main processor is in low-power state, thus resolving the contradiction between power savings and management capability.
Solution Approach 2:
The OOB MCU acts as an intermediary between the management interface and the host processor. It can receive and process management commands independently, translating them into appropriate actions without requiring the host processor to be fully operational, thereby maintaining OOB management capability while allowing the main system to remain in low-power mode.
2Use of energy by moving object
If the host processor enters low-power state, then power consumption is reduced, but the ability to receive and process management commands is impaired
Solution Approach 1:
The system dynamically adjusts power distribution to different components. The OOB MCU maintains operational power while the host processor enters low-power state. This dynamic power management allows command processing to continue independently without requiring the main processor to remain fully powered.
Solution Approach 2:
The OOB MCU is pre-configured with the capability to handle management commands independently of the host processor state. It can receive, parse, and execute management commands in advance of any host processor activation, ensuring command processing capability is maintained regardless of host processor power state.
3Reliability
If an OOB MCU is integrated into the heterogeneous computing platform, then Out-of-Band management capability is restored, but device complexity increases
Solution Approach 1:
The OOB MCU is merged with the heterogeneous computing platform as an integrated component rather than a separate external device. This integration shares physical space and resources with existing platform components, minimizing the increase in overall device complexity while restoring OOB management capability.
Solution Approach 2:
The OOB MCU is designed with multi-functionality to handle various management tasks including command reception, processing, and device control. By consolidating multiple management functions into a single integrated controller, the platform avoids the complexity that would arise from adding separate dedicated components for each function.
Data Source
AI summary
Systems and methods for an interconnect architecture for Out-of-Band (OOB) manageability 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) integrated into the heterogeneous computing platform, where the OOB MCU is configured to: receive a command; and transmit the command or an indication of the command to a selected one of the plurality of devices via an interconnect while a host processor is in a low-power state.


