BMC Package Deployment via Read-Write Partitions Without Reboots

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing server management systems face security vulnerabilities due to the oversight of BMC and BIOS firmware during decommissioning, allowing attackers to extract sensitive data, and the lack of efficient, secure methods for managing software updates without system reboots.

Innovation Solution

Implementing a package management service within the BMC that utilizes the REDFISH service to manage software updates through a read-write partition, ensuring secure, asynchronous deployment of software packages with integrity checks and dependency management, and supporting containerization or CHROOT jailed environments for third-party applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If traditional firmware update methods are used requiring system reboots, then software updates can be deployed, but system downtime increases and operational continuity is disrupted

Engineering Contradiction:
Improvesoftware update deployment efficiencyVSAvoidsystem downtime
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent divides the BMC firmware into multiple independent partitions (read-only partition and read-write partition). The read-write partition can be updated independently without affecting the read-only partition, allowing updates to be applied incrementally. This segmentation enables the system to update software components without requiring a full system reboot, thus reducing downtime while maintaining update capability.

Inventive Principle:
Principle #1Segmentation

2Ease of manufacture

If BMC firmware is not properly managed during decommissioning, then device disposal is simplified, but security vulnerabilities arise allowing attackers to extract sensitive data

Engineering Contradiction:
Improvedevice disposal processVSAvoidsecurity vulnerabilities
Core Design Contradiction:
Ease of manufactureVSObject-affected harmful factors

Solution Approach 1:

The patent extracts and isolates sensitive firmware data into specific partitions with controlled access. The read-write partition, which may contain updateable software components, is separated from the read-only partition containing critical system firmware. This extraction and separation mechanism allows for secure management of sensitive data during decommissioning, as the system can selectively clear or secure specific partitions while simplifying the overall disposal process.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent implements preliminary security measures by establishing secure update mechanisms and access controls before decommissioning. The package management service verifies package integrity and authenticity before allowing updates, preventing malicious firmware from being installed. During decommissioning, these pre-established security controls can be leveraged to securely erase or isolate sensitive data partitions, countering potential security threats proactively rather than reactively.

Inventive Principle:
Principle #9Preliminary anti-action

3Reliability

If comprehensive security checks are performed on software packages, then system security is enhanced, but update deployment complexity increases

Engineering Contradiction:
Improvesystem securityVSAvoidupdate deployment process
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent performs security verification and validation of software packages in advance before deployment. The package management service checks package integrity, authenticity, and compatibility before installing updates to the read-write partition. By performing these security checks preliminarily, the system ensures high security reliability while simplifying the actual deployment process, as verified packages can be installed directly without requiring complex runtime validation.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20250217130A1Techniques of package deployment on bmc
Publication Date: 2025.07.03 AMERICAN MEGATRENDS
  • US20250217130A1 patent drawing
  • US20250217130A1 patent drawing
  • US20250217130A1 patent drawing

AI summary

In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus is a BMC. The BMC receives, via an application programming interface (API) at the BMC, a package management request for managing a software component of the BMC. The BMC determines, by a package management service of the BMC, whether a software package for the software component is an updatable package to be stored on a read-write partition of a storage of the BMC. When the software package is the updatable package, the BMC manages the software component according to the package management request.