OOB MCU Memory Architecture for Low-Power Remote Management
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 OOB operations, including waking up external memory devices during low-power states and handling OOB packets, even when the host processor is inactive.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If ARM-based platforms are used in IHSs, then processing efficiency and power management are improved, but OOB management capability is lost
Solution Approach 1:
The system is divided into separate functional components: the ARM-based host processor handles computation while a dedicated OOB MCU handles management functions. This segmentation allows each component to be optimized independently - the ARM processor for processing efficiency and the OOB MCU for reliable out-of-band management.
Solution Approach 2:
An OOB MCU is introduced as an intermediary component between the ARM host processor and external management systems. This mediator enables OOB management capabilities without requiring the ARM processor to be active, resolving the contradiction between processing efficiency and management reliability.
2Use of energy by moving object
If host processor is placed in low-power state to save energy, then power consumption is reduced, but OOB management operations cannot be performed
Solution Approach 1:
The system separates power management responsibilities: the ARM host processor enters low-power states to reduce energy consumption, while the dedicated OOB MCU remains awake to handle management operations. This segmentation allows the system to achieve both low power consumption and operational capability.
Solution Approach 2:
The OOB MCU independently performs management operations without requiring the host processor to be active. It self-manages the wake-up of external memory devices and handles OOB packets autonomously, enabling management operations during host processor sleep states.
3Reliability
If external memory device is kept awake to enable OOB operations, then management capability is maintained, but power consumption increases
Solution Approach 1:
Instead of keeping the entire external memory device awake, the system uses a partial wake-up mechanism where only the OOB MCU and necessary memory portions are activated. This selective action maintains OOB management capability while minimizing power consumption compared to full system wake-up.
Solution Approach 2:
The OOB MCU performs preliminary actions by identifying OOB packets and determining wake-up requirements before actually waking up external memory devices. This preliminary processing allows the system to maintain management capability while avoiding unnecessary wake-ups that would increase power consumption.
Data Source
AI summary
Systems and methods for a memory 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: identify a command in an OOB packet received while a host processor is in a low-power state, and determine, based at least in part upon the command, whether to wake up an external memory device coupled to the heterogeneous computing platform.