Native OS Change Management for Automated Firmware Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing information handling systems face challenges in efficiently updating firmware, often requiring rudimentary disk operating system-based utility programs that necessitate a DOS environment, which is inefficient and limited in functionality.

Innovation Solution

A method and apparatus that utilize a native operating system change management program to cooperatively update firmware with a firmware update package, leveraging package management systems and repositories to automate the process, ensuring updates can be managed within the existing running OS environment without requiring a restart or additional execution of the start-up initialization program.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If rudimentary disk operating system-based utility programs are used for firmware updates, then the update process can be executed, but the system requires a DOS environment which is inefficient and limited in functionality

Engineering Contradiction:
Improvefirmware update operationVSAvoidDOS environment requirement
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces a native operating system change management program as an intermediary between the firmware update package and the target firmware. This mediator leverages the existing OS's package management capabilities to handle firmware updates, eliminating the need for separate DOS-based utility programs and their associated environment requirements.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent makes the native operating system's change management program universal by enabling it to handle both standard software package updates and firmware updates through the same mechanism. The firmware update package is structured to be compatible with the OS's existing package management system, allowing one system to serve multiple update functions.

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

2Productivity

If traditional firmware update methods are used, then firmware can be updated, but system downtime increases and complex setup is required

Engineering Contradiction:
Improvefirmware update efficiencyVSAvoidsystem downtime
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent performs preliminary actions by pre-structuring the firmware update package with metadata that describes dependencies, version information, and installation parameters. This preliminary preparation allows the change management program to automatically validate compatibility and plan the update sequence, eliminating the need for complex manual setup and reducing system downtime.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback mechanisms where the change management program queries the firmware inventory to determine current firmware versions, compares them against the update package specifications, and automatically determines the appropriate update path. This feedback loop enables automated decision-making about whether to proceed with the update and what dependencies need to be satisfied first.

Inventive Principle:
Principle #23Feedback

3Extent of automation

If firmware updates are performed without proper version management, then updates can be applied, but compatibility issues arise

Engineering Contradiction:
Improvefirmware update automationVSAvoidfirmware compatibility
Core Design Contradiction:
Extent of automationVSReliability

Solution Approach 1:

The patent performs preliminary validation by including version information and dependency declarations in the firmware update package structure. The change management program reads this metadata before installation and automatically verifies compatibility with the current firmware inventory, preventing incompatible updates from being applied.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent establishes feedback through dependency tracking where the change management program queries the firmware inventory to retrieve current version information, compares it against the update package's version requirements, and automatically determines compatibility. This feedback mechanism ensures that only compatible firmware versions are updated, maintaining system reliability.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8707297B2Apparatus and methods for updating firmware
Publication Date: 2014.04.22 DELL PROD LP
  • US8707297B2 patent drawing
  • US8707297B2 patent drawing
  • US8707297B2 patent drawing

AI summary

A method for updating firmware comprises executing a native operating system change management program that acts cooperatively with a firmware update package to update a firmware program in the information handling system. An apparatus comprises an information handling system running an operating system. An operating system change management program in a memory of the information handling system acts cooperatively with the operating system and a firmware update package to update a firmware program in the information handling system. Another method for updating firmware comprises building a firmware update package that is executable in a change management program running in a native operating system on an information handling system, and storing the firmware update package in a repository available to a user.