OOB Power Control via Network Device in ARM Platforms
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 control of Information Handling Systems (IHSs).
Innovation Solution
Implement a network device in a heterogeneous computing platform that includes an Embedded Controller (EC) or Out-of-Band Microcontroller Unit (MCU) to receive and process OOB packets, enabling power state changes by sending commands to voltage regulators, Power Management Integrated Circuits (PMICs), or host Operating System (OS) drivers, depending on the type of command.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Use of energy by moving object
If ARM-based platforms are used to reduce power consumption and improve energy efficiency, then energy efficiency is improved, but the ability to support Out-of-Band (OOB) management is lost
Solution Approach 1:
The system is segmented into multiple processing domains: the main ARM-based processor for energy-efficient computation and a separate EC or OOB MCU for dedicated OOB management functions. This segmentation allows each component to be optimized for its specific purpose while working together in a heterogeneous computing platform.
Solution Approach 2:
An Embedded Controller (EC) or Out-of-Band Microcontroller Unit (MCU) acts as an intermediary component that bridges the ARM-based processor and the OOB management network. This intermediary enables OOB management capabilities by receiving and processing OOB packets independently of the main processor's power state.
2Loss of energy
If the host processor enters low-power states to conserve energy, then energy consumption is reduced, but the system's responsiveness to OOB management commands is degraded
Solution Approach 1:
The system separates OOB management functionality from the main host processor by implementing a dedicated EC or OOB MCU. This segmentation allows the host processor to enter low-power states while the EC/MCU remains operational to handle OOB commands independently, maintaining system responsiveness.
Solution Approach 2:
The EC or OOB MCU is designed to autonomously handle OOB management tasks without requiring the host processor to be active. It can independently process OOB packets, manage power states, and communicate with voltage regulators and PMICs, enabling the system to respond to OOB commands even when the main processor is in a low-power state.
3Reliability
If traditional x86-based platforms with ECs are used to ensure OOB management capability, then OOB management is enabled, but hardware complexity and incompatibility with modern ARM-based architectures increases
Solution Approach 1:
The EC or OOB MCU is designed as a universal component that can function across different processor architectures (x86 and ARM). It provides multi-functional capabilities including OOB management, power state control, and firmware update coordination, making it compatible with modern heterogeneous computing platforms without requiring architecture-specific implementations.
Solution Approach 2:
The system adapts the EC/MCU implementation parameters to match the target architecture. For ARM-based platforms, the EC or OOB MCU is configured with appropriate interfaces and communication protocols compatible with ARM systems, while maintaining the same core OOB management functionality. This parameter adaptation reduces hardware complexity compared to universal x86-based solutions.
Data Source
AI summary
Systems and methods for system-level power control for Out-of-Band (OOB) processors in heterogeneous computing platforms. In some embodiments, a heterogeneous computing platform may include a network device and an Embedded Controller (EC) or OOB Microcontroller Unit (MCU) coupled to the network device, where the network device is configured to: receive an OOB packet comprising a power state change command, and forward the power state change command to the EC or the OOB MCU.