OOB Network Interface for Low-Power Remote Management

Resolve Bottlenecks,
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) even in low-power states.

Innovation Solution

A network device integrated into or coupled with the heterogeneous computing platform is configured to wake up from a low-power state and access a cloud service through an OOB channel, enabling OOB command processing while the host processor remains in a low-power state, utilizing an RTC timer and always-on voltage bus to facilitate EC wake-up and command transmission.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Use of energy by moving object

If the host processor remains in low-power state for energy efficiency, then energy consumption is reduced, but the ability to process OOB commands remotely is lost

Engineering Contradiction:

Improveenergy consumptionVSAvoidOOB management capability

Core Design Contradiction:

Use of energy by moving objectVSReliability

Solution Approach 1:

The system separates OOB management functionality from the host processor by integrating it directly into the network device. This segmentation allows the network device to independently handle OOB commands and wake-up events without requiring the host processor to be active, thus maintaining energy efficiency while ensuring reliable remote management capability.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The network device acts as an intermediary between the external management network and the host processor. It can receive, process, and respond to OOB commands independently when the host processor is in low-power state, serving as a mediator that maintains management capability without requiring the main processor to wake up.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If an EC is integrated into the heterogeneous computing platform, then OOB management capability is improved, but device complexity increases

Engineering Contradiction:

ImproveOOB management capabilityVSAvoidplatform complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges the EC functionality directly into the network device, combining what were previously separate components (EC and network device) into a single integrated unit. This reduces overall device complexity by eliminating the need for a separate EC while maintaining full OOB management capability.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The network device is designed to perform multiple functions: it serves as both the network communication interface and the embedded controller for OOB management. This multi-functionality eliminates the need for dedicated EC hardware, reducing platform complexity while maintaining comprehensive management capabilities.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS12468376B2Out-of-band networking for heterogeneous computing platforms in low-power states

Publication Date: 2025.11.11 DELL PROD LP

AI summary

Systems and methods for Out-of-Band (OOB) networking for heterogeneous computing platforms in low-power states. In some embodiments, an Information Handling System (IHS) may include a heterogeneous computing platform and a network device integrated into or coupled to the heterogeneous computing platform, and the network device may be configured to: wake up from a low-power state while a host processor of the heterogeneous computing platform remains in the low-power state, and access a cloud service through an OOB channel to check a status of an OOB command buffer while the host processor remains in the low-power state.