Virtual BMC in System Management Mode for Platform Control

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing remote platform management approaches for computing devices are costly, resource-intensive, and lack comprehensive system information access, often requiring additional hardware and complex handoffs between firmware and operating systems, which can impact performance and reliability.

Innovation Solution

A virtual Baseboard Management Controller (vBMC) is implemented within the System Management Mode (SMM) using standard hardware, enabling direct access to system resources and utilizing SMBus and network controllers for remote management without dedicated hardware, allowing continuous monitoring and data transfer through in-memory mailboxes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a physical Baseboard Management Controller (BMC) is used for remote platform management, then comprehensive system management capabilities are provided, but device complexity and cost increase due to dedicated hardware requirements

Engineering Contradiction:

Improvesystem management capabilitiesVSAvoidhardware complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a virtual BMC (vBMC) that copies the functionality of a physical BMC using software running in System Management Mode (SMM) on the CPU. The vBMC emulates BMC operations including sensor monitoring, event logging, and network communication through standard hardware interfaces, eliminating the need for dedicated BMC hardware while maintaining comprehensive system management capabilities.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The vBMC leverages existing universal hardware components (CPU with SMM support, SMBus controller, network interface) to perform multiple BMC functions. By making standard hardware components serve dual purposes (operating system operations and firmware-based management), the system achieves BMC functionality without dedicated hardware, reducing complexity while maintaining versatility.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Reliability

If a physical BMC with dedicated network interface is deployed, then reliable remote management is achieved, but resource usage and cost increase

Engineering Contradiction:

Improveremote management reliabilityVSAvoidhardware resources

Core Design Contradiction:

ReliabilityVSQuantity of substance

Solution Approach 1:

The patent shares the system's network interface controller between operating system operations and vBMC remote management functions. The vBMC uses standard network protocols through the existing NIC, allowing the same hardware resource to serve multiple purposes without requiring dedicated BMC network hardware, thus reducing resource consumption while maintaining reliability.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The vBMC copies BMC management functions including network communication capabilities through software implementation in SMM. By emulating BMC operations using standard hardware interfaces rather than dedicated hardware, the system achieves reliable remote management with reduced hardware resource requirements.

Inventive Principle:

Principle #26Copying

3Device complexity

If firmware-based virtual BMC is implemented using standard hardware, then cost and complexity are reduced, but access to system information may be limited

Engineering Contradiction:

Improvehardware complexityVSAvoidsystem information access

Core Design Contradiction:

Device complexityVSLoss of information

Solution Approach 1:

The vBMC dynamically accesses system information through SMM by interacting with hardware components via standard interfaces (SMBus, memory-mapped I/O). This dynamic access mechanism allows the virtual BMC to read sensor data, register values, and system state information on-demand without requiring dedicated hardware channels, maintaining comprehensive information access while reducing hardware complexity.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The vBMC uses SMM as an intermediary execution environment that mediates between the operating system and hardware components. Through SMM, the vBMC can access system information that would otherwise be inaccessible to user-mode software, bridging the gap between reduced hardware complexity and maintained information accessibility.

Inventive Principle:

Principle #24Intermediary (Mediator)

4Adaptability or versatility

If handoff mechanisms between firmware and operating system are implemented, then platform management functionality is achieved, but performance and reliability may be impacted

Engineering Contradiction:

Improveplatform management functionalityVSAvoidsystem performance

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent merges platform management functionality directly into the firmware execution context (SMM) rather than implementing separate handoff mechanisms between firmware and operating system. By combining management operations with the existing firmware execution flow and using SMM for direct hardware access, the system eliminates performance-impacting handoffs while maintaining full platform management functionality.

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS9298524B2Virtual baseboard management controller

Publication Date: 2016.03.29 INSYDE SOFTWARE CORP

AI summary

A system firmware agent providing the capabilities of a Baseboard Management Controller (BMC) from within System Management Mode (SMM) is discussed. A virtual BMC provides dedicated communication channels for system firmware, other BMCs in the platform and remote management agents. The virtual BMC may monitor the status of the system, record system events, and control the system state.