Nested Multithread Firmware Push for Blade Server Enclosures

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional systems for managing complex enterprise network infrastructures face challenges such as outdated and incomplete data in vendor databases, manual update processes, and the need for specialized software and hardware, leading to inefficiencies and increased complexity.

Innovation Solution

A multi-threaded approach using nested operations to query and update firmware on remote servers, generating an integrated snapshot view of the network infrastructure, and pushing firmware updates concurrently while collecting hardware information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional vendor maintained databases are used to retrieve operating status of network resources, then data can be obtained through simple queries, but the data may be outdated, incomplete, or contain errors due to the sophisticated nature of enterprise scale networks with multiple geographically dispersed sites, firewalls, and infrastructure entities

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

Solution Approach 1:

The system performs preliminary actions by actively pushing firmware updates and collecting hardware information from network resources before being queried, ensuring data is current and accurate. The multi-threaded architecture proactively gathers and updates network resource status information, eliminating the delay inherent in conventional query-based approaches.

Inventive Principle:
Principle #10Preliminary action

2Ease of operation

If manual separate processes are used for firmware updates and information gathering, then each process can be performed independently, but the overall system efficiency is reduced and manual intervention is required

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

Solution Approach 1:

The system merges firmware update deployment and hardware information gathering into a single integrated multi-threaded process. Child threads simultaneously perform both firmware pushing and information collection activities, eliminating the need for separate manual processes and significantly improving system efficiency while maintaining operational simplicity.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system ensures continuous useful action by having child threads continuously push firmware updates and collect hardware information without interruption. The multi-threaded architecture maintains ongoing operations, eliminating idle time between separate manual processes and ensuring productive work is performed continuously.

Inventive Principle:
Principle #20Continuity of useful action

3Reliability

If specialized software and hardware resources such as web servers and database servers are deployed, then comprehensive information gathering and reporting can be achieved, but the system becomes slow, inefficient, and bulky to maintain

Engineering Contradiction:
Improveinformation completenessVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system extracts the essential functionality of information gathering and firmware management from complex specialized software and hardware infrastructure. The multi-threaded application performs these functions directly, removing the dependency on separate web servers and database servers, thereby reducing system complexity while maintaining information completeness and reliability.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The multi-threaded application serves multiple functions simultaneously - it acts as an information gathering tool, firmware update system, and reporting mechanism all in one. This universal approach replaces multiple specialized components, reducing device complexity while maintaining comprehensive information gathering and reliable operation.

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

4Productivity

If conventional single-threaded or non-nested threading approaches are used, then implementation is simpler, but the ability to push firmware updates and collect information concurrently from multiple network resources is limited

Engineering Contradiction:
Improveupdate speedVSAvoidthreading complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system implements nested threading where child threads are created within parent threads, allowing hierarchical concurrent operations. Parent threads manage high-level coordination while child threads handle specific firmware pushing and information gathering tasks, enabling efficient concurrent operations across multiple network resources while organizing complexity in a manageable hierarchical structure.

Inventive Principle:
Principle #7Nested doll (Nesting)

Solution Approach 2:

The system segments the firmware update and information gathering process into multiple independent child threads that can execute concurrently. Each child thread handles specific network resources independently, allowing parallel processing that dramatically improves update speed and productivity while the parent thread coordinates overall progress.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS20260072678A1Systems and methods for pushing firmware binaries using nested multi-threader operations
Publication Date: 2026.03.12 BANK OF MONTREAL
  • US20260072678A1 patent drawing
  • US20260072678A1 patent drawing
  • US20260072678A1 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.