Nested Multithread Firmware Updates for Blade Server Enclosures

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional systems for monitoring and managing complex enterprise network infrastructures face challenges such as outdated and incomplete data in vendor-maintained databases, manual information retrieval, lack of integrated snapshot views, passive functionality, and the need for specialized software and hardware resources, leading to inefficiencies in updating and managing network resources.

Innovation Solution

A multi-threaded approach using nested operations to query and update firmware on remote servers, generating an integrated snapshot view of network resources, and pushing firmware updates simultaneously, without relying on external databases or agents, utilizing a snapshot view engine that operates in both passive and active modes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional vendor-maintained databases are used to retrieve network resource status, then data can be obtained through existing infrastructure, but the data may be outdated, incomplete, or contain errors due to database update delays and programming bugs

Engineering Contradiction:
Improvedata accuracyVSAvoiddata freshness
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by directly querying network resources before generating reports, ensuring data is current and accurate. The snapshot engine proactively collects hardware information from network resources at the time of report generation rather than relying on pre-stored database entries, eliminating data staleness and errors from vendor-maintained databases.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If multiple separate systems are used for information gathering and firmware updates, then each function can be performed with dedicated tools, but the overall process becomes complex and requires manual coordination

Engineering Contradiction:
Improvefunctional capabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The snapshot engine is designed as a universal multi-functional tool that combines information gathering, report generation, and firmware update capabilities into a single system. It can operate in passive mode for data collection and reporting, and in active mode for pushing firmware updates, eliminating the need for separate specialized tools and manual coordination between systems.

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

Solution Approach 2:

The patent merges previously separate functions of information gathering and firmware management into a single integrated snapshot engine. The system combines passive reporting capabilities with active firmware push functionality, allowing both operations to be performed through one unified interface and process flow.

Inventive Principle:
Principle #5Merging (Combining)

3Adaptability or versatility

If specialized software and hardware resources are deployed for monitoring and firmware updates, then comprehensive functionality can be achieved, but the system becomes bulky and requires additional maintenance resources

Engineering Contradiction:
Improvefunctional capabilityVSAvoidresource requirements
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The snapshot engine serves as a universal platform that replaces multiple specialized software tools and hardware resources. It consolidates web server functionality, database operations, report generation, and firmware management capabilities into a single multi-functional application, reducing the overall resource footprint and maintenance requirements while maintaining comprehensive functionality.

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

4Ease of operation

If firmware updates are performed manually separate from information gathering, then each operation can be controlled independently, but the overall process time increases and efficiency decreases

Engineering Contradiction:
Improveoperational controlVSAvoidupdate efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The system merges information gathering and firmware update operations into a single integrated process. When operating in active mode, the snapshot engine simultaneously collects hardware information from network resources and pushes firmware updates to targeted devices, eliminating the need for separate manual operations and significantly improving overall productivity.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The snapshot engine enables continuous useful action by performing both information collection and firmware deployment in an uninterrupted integrated workflow. The system transitions seamlessly between passive reporting and active update modes, maintaining continuous operational value without idle periods between separate manual processes.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS12481496B2Systems and methods for pushing firmware binaries using nested multi-threader operations
Publication Date: 2025.11.25 BANK OF MONTREAL
  • US12481496B2 patent drawing
  • US12481496B2 patent drawing
  • US12481496B2 patent drawing

AI summary

A computer may receive a request to generate a snapshot view of the enterprise network infrastructure. The computer may implement a multithread process to contemporaneously query a plurality of blade servers and server enclosures within the entire network infrastructure. The computer may contemporaneously receive a plurality of information files from the queried network resources (e.g. the blade servers, server enclosures). In active state modes, the computer may push firmware update binaries to the network resources. In a server processing and an active state mode, the computer may implement a multithreaded process to push the firmware update binaries to standalone servers or blade servers that can be accessed directly. In a blade enclosure processing and an active state mode, the computer may implemented a nested multi-threader, using child threads nested within a parent thread to a blade server enclosure to push firmware update binaries to blade servers in the enclosure.