Wireless Interface Sharing and OOB Packet Routing for ARM Platforms
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
ARM-based platforms lack Embedded Controllers (ECs) necessary for Out-of-Band (OOB) management, which are crucial for remote management of Information Handling Systems (IHSs).
Innovation Solution
Integrate an OOB Microcontroller Unit (MCU) and a network traffic routing controller into heterogeneous computing platforms to manage packet routing between the OOB MCU and host processor, utilizing policies to determine whether packets are OOB or in-band.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Use of energy by moving object
If ARM-based platforms are used, then power efficiency and mobile computing capabilities are improved, but Out-of-Band management capabilities are lost due to lack of Embedded Controllers
Solution Approach 1:
The system separates OOB management functions from the main ARM processor by integrating a dedicated OOB MCU into the heterogeneous computing platform. This segmentation allows the ARM processor to focus on power-efficient mobile computing while the OOB MCU handles remote management tasks independently, resolving the contradiction between power efficiency and OOB management capability
Solution Approach 2:
The OOB MCU is designed with multi-functionality to perform various management tasks including packet routing, command processing, and system monitoring. This universal controller provides complete OOB management capabilities in a single integrated component, enabling ARM-based platforms to achieve enterprise-grade manageability without compromising power efficiency
2Device complexity
If a shared wireless interface is used between host processor and OOB MCU, then device complexity is reduced, but packet routing complexity increases
Solution Approach 1:
The network traffic routing controller acts as an intermediary between the shared wireless interface and the OOB MCU/host processor. It automatically intercepts incoming packets, analyzes their nature (OOB vs. in-band), and routes them to the appropriate destination. This mediator approach maintains low device complexity while systematically managing packet routing complexity through automated classification and forwarding logic
3Reliability
If OOB packets are prioritized over in-band packets, then OOB management reliability is improved, but in-band network performance may deteriorate
Solution Approach 1:
The network traffic routing controller implements dynamic packet scheduling that adjusts prioritization based on packet type and system state. OOB packets receive higher priority for reliable delivery, while in-band packets are scheduled efficiently to maintain network performance. This dynamic approach ensures OOB management reliability without permanently degrading in-band network productivity
Solution Approach 2:
The system applies partial prioritization by giving OOB packets priority only when management operations are in progress or when the system is in low-power states. During normal operation, in-band traffic flows with standard prioritization to maintain performance. This selective prioritization ensures OOB reliability when needed while preserving in-band network productivity during regular operations
Data Source
AI summary
Systems and methods for wireless interface sharing for Out-of-Band (OOB) processors in heterogeneous computing platforms. In some embodiments, an Information Handling System (IHS) may include an OOB Microcontroller Unit (MCU) integrated into a heterogeneous computing platform and a network traffic routing controller integrated into the heterogeneous computing platform, where the network traffic routing controller is coupled to the OOB MCU and to a host processor, and where the network traffic routing controller is configured to determine whether to route a packet to the OOB MCU or to the host processor.