Containerized BMC Microservices for Faster Service Updates

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing baseboard management controllers (BMCs) have monolithic firmware stacks that require lengthy delays and updates for service changes, limiting agility and flexibility in service modifications.

Innovation Solution

Implementing a containerized, zero trust microservices platform for BMCs, where services are provided as autonomous microservices in software containers, allowing independent modification, validation, and management without waiting for new versions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a monolithic firmware stack is used in BMC, then system stability is maintained, but service modification agility deteriorates due to lengthy update delays

Engineering Contradiction:

Improveservice modification agilityVSAvoidupdate delay

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The monolithic firmware stack is segmented into multiple independent software containers, each providing specific management services. This segmentation allows individual services to be updated independently without requiring full firmware reflash, thereby reducing update time and improving service modification agility while maintaining system stability through the container isolation mechanism.

Inventive Principle:

Principle #1Segmentation

2Adaptability or versatility

If services are provided as independent microservices in containers, then service modification agility is improved, but system complexity increases

Engineering Contradiction:

Improveservice modification agilityVSAvoidsystem architecture complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

A container management engine is introduced as an intermediary layer between the hardware platform and the microservices containers. This engine handles container lifecycle management, resource allocation, and inter-service communication, thereby abstracting the complexity of managing multiple independent services while preserving service modification agility.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Productivity

If traditional firmware updates are implemented, then service changes can be made, but productivity is reduced due to lengthy update cycles

Engineering Contradiction:

Improveservice deployment speedVSAvoidupdate cycle time

Core Design Contradiction:

ProductivityVSDuration of action of moving object

Solution Approach 1:

Service updates are prepared and validated in isolation within container images before being deployed to the running BMC. This preliminary preparation allows extensive testing and validation to occur offline, and once validated, containers can be rapidly swapped in without interrupting BMC operations, thereby significantly reducing update cycle time and improving service deployment speed.

Inventive Principle:

Principle #10Preliminary action

4Adaptability or versatility

If monolithic firmware is used, then ease of operation is maintained, but adaptability to new services deteriorates

Engineering Contradiction:

Improvenew service integrationVSAvoidsystem operation simplicity

Core Design Contradiction:

Adaptability or versatilityVSEase of operation

Solution Approach 1:

The container management engine provides universal functionality for managing diverse microservices containers through standardized interfaces and APIs. This universal management layer maintains operational simplicity by presenting a consistent interface regardless of the specific service being managed, while simultaneously enabling easy integration of new services through the standardized container deployment mechanism.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS20260064822A1Container-based baseboard management controllers

Publication Date: 2026.03.05 HEWLETT PACKARD ENTERPRISE DEV LP

AI summary

A baseboard management controller operates independently from an operating system of a host to manage the host. The baseboard management controller includes a hardware processor. The hardware processor causes the baseboard management controller to provide a plurality of software containers to provide services to manage the host. The hardware processor causes the baseboard management controller to provide an execution control engine to manage lifecycles of the software containers.