Virtual Firmware Image Distribution for Embedded Controller Testing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Testing multiple versions of embedded controller operating systems and software against a real system is resource-intensive, requiring disruptive installations and recreating failing scenarios, which is time-consuming and costly, especially when hardware reaches end-of-life, necessitating frequent field rolls or pre-emptive hardware replacements.

Innovation Solution

A method for distributing computing tasks across pools of computer systems, selecting suitable systems based on quality of service criteria, using virtual firmware images to connect and test firmware levels, thereby minimizing hardware utilization and enabling efficient testing of multiple firmware versions without disrupting existing hardware.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If firmware testing is performed on real hardware systems, then testing accuracy is improved, but hardware availability and utilization deteriorate due to disruptive installations and time-consuming recreations of failing scenarios

Engineering Contradiction:
Improvetesting accuracyVSAvoidhardware utilization
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The patent creates virtual copies of firmware images that can be tested on real hardware without permanently modifying the physical systems. These virtual firmware images are loaded into memory and executed, allowing multiple test scenarios to be run without disruptive installations. The virtualization approach enables accurate firmware testing while preserving hardware availability, as tests can be initiated and terminated without physical hardware changes.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent extracts the firmware testing function from the physical hardware installation process. By separating firmware execution from permanent hardware installation, the system can load and unload firmware images as needed. This extraction allows testing to occur on real hardware without the disruptive installations that previously reduced hardware utilization, as the firmware can be removed from memory without affecting the underlying hardware system.

Inventive Principle:
Principle #2Taking out (Extraction)

2Adaptability or versatility

If multiple firmware versions are tested on the same hardware, then testing completeness is improved, but time consumption increases due to recreating failing scenarios

Engineering Contradiction:
Improvetesting completenessVSAvoidtime consumption
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-loading multiple firmware images into the system's memory before testing begins. The orchestration unit loads all required firmware versions into memory in advance, so that when testing needs to switch between firmware versions, no time-consuming installation or recreation processes are needed. The system can immediately switch between loaded firmware images, enabling comprehensive multi-version testing without the time loss previously associated with scenario recreation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent ensures continuity of useful action by maintaining firmware images in memory throughout the testing process. Rather than uninstalling and reinstalling firmware between tests, the system keeps multiple firmware versions loaded and ready for immediate execution. This continuous availability of firmware images in memory eliminates interruptions and time losses, allowing the testing process to proceed continuously across multiple firmware versions without recreating failing scenarios.

Inventive Principle:
Principle #20Continuity of useful action

3Reliability

If physical hardware is used for firmware testing, then test validity is improved, but maintenance costs increase when hardware reaches end-of-life

Engineering Contradiction:
Improvetest validityVSAvoidmaintenance costs
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent uses virtual firmware images as copies of the actual firmware that need to be tested. These virtual images can be created, modified, and deleted without affecting physical hardware. When hardware reaches end-of-life, the system can migrate the firmware image testing to different hardware platforms without loss of test validity, as the firmware behavior is captured in the virtual image rather than being permanently tied to specific physical components. This copying approach decouples firmware testing from hardware lifecycle management.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent implements universality by designing a testing system that can execute the same firmware images across multiple different hardware platforms. The orchestration unit and gateway architecture allow firmware images to be tested on various hardware configurations without modification. This multi-functionality means that when specific hardware reaches end-of-life, the same firmware images can be tested on alternative hardware, eliminating the need for expensive field rolls or pre-emptive hardware replacements and reducing overall maintenance costs.

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

Data Source

PatentUS11061666B1Distributing computing tasks to individual computer systems
Publication Date: 2021.07.13 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11061666B1 patent drawing
  • US11061666B1 patent drawing
  • US11061666B1 patent drawing

AI summary

A computer-implemented method for distributing computing tasks to individual computer systems from a first pool of first computer systems, characterized by controllers executing a specific firmware with a gateway to receive commands via a network and an orchestration unit, whereby in response to a request to perform a computing task, an available and suitable first computer system is selected. An available second computer system is selected from a second pool. A firmware image corresponding to a requested controller firmware level is selected, using a gateway connector to send commands to the gateways. A network connection is established between the gateway in the controller of the first computer system and the gateway connector in the second computer system. Execution of the firmware image is triggered.