OOB MCU Provisioning for Low-Power ARM Platform Manageability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
ARM-based platforms lack Embedded Controllers (ECs) or microcontrollers capable of supporting Out-of-Band (OOB) management, which is crucial for remote management and maintenance of Information Handling Systems (IHSs).
Innovation Solution
Integrate an Out-of-Band Microcontroller Unit (MCU) or Embedded Controller (EC) into the heterogeneous computing platform, configured to enable OOB packet sniffing operations, including waking up from a low-power state to manage network devices and check OOB command buffers while the host processor remains in a low-power state, using an RTC timer and always-on voltage bus for wake-up mechanisms.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If ARM-based platforms are used without ECs, then device complexity is reduced, but OOB management capability is lost
Solution Approach 1:
The system separates the OOB management function from the main ARM processor by integrating a dedicated OOB MCU into the heterogeneous computing platform. This segmentation allows the OOB management capabilities to be independent and functional while the main processor can be simplified or powered down.
Solution Approach 2:
The OOB MCU acts as an intermediary component that bridges the gap between the simplified ARM-based platform and the requirement for OOB management. It provides the necessary management functions without requiring a full EC, thus maintaining reduced complexity while enabling OOB capabilities.
2Use of energy by moving object
If the host processor enters low-power state, then energy consumption is reduced, but OOB management operations cannot be performed
Solution Approach 1:
The system divides the processing functions into two separate domains: the main host processor for computational tasks and the OOB MCU for management tasks. This allows the host processor to enter low-power states while the OOB MCU remains operational to handle management operations.
Solution Approach 2:
The OOB MCU changes its operational state based on power availability and management needs. It can operate independently when the host is in low-power mode, and coordinate with the host when full functionality is required, thus adapting its parameters to resolve the contradiction between energy saving and management availability.
3Reliability
If OOB packet sniffing is enabled continuously, then remote management capability is improved, but energy consumption increases
Solution Approach 1:
The OOB MCU performs packet sniffing operations periodically rather than continuously. It can be triggered by RTC wake circuits or other events to check for management packets, thus maintaining remote management capability while significantly reducing energy consumption compared to continuous monitoring.
Solution Approach 2:
The OOB MCU is designed to autonomously perform packet sniffing and management operations without requiring the host processor to be active. It self-manages its operation cycles, enabling remote management while consuming minimal energy independent of the host system's power state.
Data Source
AI summary
Systems and methods for provisioning of Out-of-Band (OOB) manageability features in heterogeneous computing platforms. In some embodiments, an Information Handling System (IHS) may include a heterogeneous computing platform and an OOB Microcontroller Unit (MCU) integrated into the heterogeneous computing platform or an Embedded Controller (EC) integrated into or coupled to the heterogeneous computing platform, where the OOB MCU or EC is configured to, in response to a status of a flag, enable OOB packet sniffing operations.