Server-Based Firmware Management Eliminates Local Storage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current firmware management in servers is hindered by difficulties in upgrading or downgrading firmware versions, security risks, increased hardware costs due to the need for nonvolatile memory and security chips, and high maintenance workloads, especially in large-scale cloud deployments.

Innovation Solution

A method and system that allows firmware data to be loaded directly from a second device or a cloud-based firmware resource pool without using local nonvolatile memory, eliminating the need for dedicated storage chips and enabling secure, efficient firmware management through a firmware management platform.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If firmware is stored in local nonvolatile memory (Flash, EEPROM), then firmware can be loaded locally, but firmware upgrade and downgrade operations become difficult and time-consuming

Engineering Contradiction:
Improvefirmware upgrade operationVSAvoidfirmware upgrade time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent extracts firmware storage from local nonvolatile memory and relocates it to a remote server. The server stores multiple versions of firmware, and the device can download and load firmware directly from the server without rewriting local Flash memory, thereby simplifying upgrade operations and reducing time consumption

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent implements preliminary action by pre-storing multiple firmware versions on the server before they are needed. When a firmware upgrade is required, the device can immediately download and load the pre-prepared firmware from the server, eliminating the need for time-consuming local rewriting operations

Inventive Principle:
Principle #10Preliminary action

2Reliability

If dedicated security chips are used to verify firmware security, then security is improved, but hardware cost and startup time increase

Engineering Contradiction:
Improvefirmware securityVSAvoidhardware configuration
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the security verification function from dedicated hardware security chips and relocates it to software-based verification on the server. The server performs security verification on firmware before making it available for download, eliminating the need for additional hardware security chips in the device

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces the server as an intermediary that performs security verification of firmware. Instead of requiring security chips in each device, the server acts as a trusted intermediary that verifies firmware security before distribution, thereby reducing hardware complexity while maintaining security

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If redundant BIOS ROM and security chips are deployed, then security and reliability are improved, but hardware cost increases

Engineering Contradiction:
Improvefirmware securityVSAvoidhardware components
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent merges the functions of multiple hardware components (BIOS ROM, security chips, firmware storage) into a unified server-based firmware management system. The server consolidates firmware storage, security verification, and distribution functions, eliminating the need for redundant hardware components in individual devices

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent implements universality by designing a multi-functional server that performs firmware storage, security verification, version management, and distribution. This single server replaces multiple dedicated hardware components, reducing the quantity of hardware substances required while maintaining or improving reliability

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS20240403434A1Device operation method, firmware management method and firmware management system
Publication Date: 2024.12.05 CLOUD INTELLIGENCE ASSETS HOLDING (SINGAPORE) PTE LTD
  • US20240403434A1 patent drawing
  • US20240403434A1 patent drawing
  • US20240403434A1 patent drawing

AI summary

A device operation method, a firmware management method and a firmware management system are disclosed. First firmware data to be loaded by a chip of a first device is acquired from a second device associated with the first device. And the first firmware data is loaded to the chip without going through a local nonvolatile memory of the first device. Therefore, it is not necessary to install the nonvolatile memory such as a flash on the mainboard of the device to store the firmware, and it is also not necessary to install a security chip for verifying the firmware, thus greatly reducing cost of the device.