Firmware BMC Data Integrity Verification via Checksum Feedback

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The complexity of collecting and transmitting system inventory data in managed computing systems, involving multiple firmware components, leads to error-prone processes and difficulties in identifying and addressing issues within BMC and firmware components.

Innovation Solution

Implementing a data integrity tool that verifies system inventory data through multiple phases, comparing data formats and identifying discrepancies to facilitate modifications in firmware and BMC components, ensuring accurate and efficient data transmission.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple firmware components are used to collect and transmit system inventory data, then the functionality and coverage of data collection is improved, but the complexity of the process and the error rate increase

Engineering Contradiction:
Improvedata collection coverageVSAvoidprocess complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a feedback mechanism where the firmware conversion module generates checksums of the system inventory data in both device instance format and JSON format, and compares these checksums to verify data integrity during transmission. This feedback loop identifies errors caused by the complex multi-component process and enables corrective actions.

Inventive Principle:
Principle #23Feedback

2Adaptability or versatility

If multiple firmware components are used to collect and transmit system inventory data, then the functionality and coverage of data collection is improved, but the difficulty of identifying and addressing errors increases

Engineering Contradiction:
Improvedata collection coverageVSAvoiderror identification difficulty
Core Design Contradiction:
Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent implements a feedback mechanism where the firmware conversion module generates checksums of the system inventory data in both device instance format and JSON format, and compares these checksums to verify data integrity during transmission. This feedback loop identifies errors caused by the complex multi-component process and enables corrective actions.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent introduces checksums as an intermediary verification mechanism between the firmware components. The checksum acts as a mediator that can identify data corruption or transmission errors without requiring direct inspection of the complex multi-component firmware process, thereby simplifying error detection.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If data integrity verification is implemented through multiple phases with checksums, then the reliability of data transmission is improved, but the processing time and computational overhead increase

Engineering Contradiction:
Improvedata transmission reliabilityVSAvoidverification processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies partial verification by computing checksums only for critical portions of the system inventory data rather than verifying every single data element. This selective approach maintains high reliability for essential data while reducing the overall processing time and computational overhead compared to complete verification of all data.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS11645616B1Verifying the integrity of data transmitted between a firmware and a baseboard management controller (BMC)
Publication Date: 2023.05.09 AMERICAN MEGATRENDS
  • US11645616B1 patent drawing
  • US11645616B1 patent drawing
  • US11645616B1 patent drawing

AI summary

Technologies are described for verifying the integrity of data transmitted between a firmware and a baseboard management controller (“BMC”). During a first verification phase, a data integrity tool compares system inventory data provided by firmware protocols to a system inventory module to system inventory data in a device instance format. During a second verification phase, the data integrity tool verifies operation of a firmware conversion module by comparing the system inventory data in the device instance format to the system inventory data in a JavaScript Object Notation (“JSON”) format. During a third verification phase, the data integrity tool retrieves the system inventory data from a management server and compares the system inventory data retrieved from the management server to the system inventory data previously transmitted to the management server. Identified discrepancies can be utilized to modify the system inventory module, the firmware conversion module, or the management server.