Distributed BIOS Dynamic IDM Loading
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current approaches for managing firmware components in information handling systems (IHS) are limited by the inability to dynamically load and authorize independent diagnostics modules (IDMs), leading to inefficiencies in space utilization and security, and the inability to resolve hardware, firmware, and operating system interdependencies.
Innovation Solution
A method and system for performing firmware management operations using a distributed BIOS that dynamically identifies, authenticates, and executes independent diagnostics modules via a diagnostics event manager, allowing for dynamic loading based on IHS health status and hardware capabilities, reducing the need for storing all IDMs in limited SPI memory.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If all independent diagnostics modules are stored in SPI memory, then all IDMs are available for execution, but SPI memory usage increases and memory lifecycle is reduced
Solution Approach 1:
The system dynamically loads and executes IDMs based on detected hardware components and diagnostic needs, rather than statically storing all IDMs in SPI memory. The diagnostics event manager determines which IDMs to load at runtime, enabling flexible adaptation to different hardware configurations while reducing memory consumption.
Solution Approach 2:
The patent extracts the IDM storage function from SPI memory by implementing a file system-based storage mechanism. IDMs are stored as files on the file system and loaded into memory only when needed, separating the storage function from the execution memory to reduce SPI memory usage and extend its lifecycle.
2Adaptability or versatility
If traditional firmware management is used, then firmware components are managed, but dynamic loading and authorization of IDMs is not possible
Solution Approach 1:
The firmware management system is segmented into functional components: a diagnostics event manager that handles event processing, a file system that stores IDMs, and a BIOS that coordinates execution. This segmentation enables dynamic IDM loading while distributing complexity across manageable components rather than concentrating it in a monolithic firmware manager.
Solution Approach 2:
The diagnostics event manager acts as an intermediary between the BIOS and IDMs, coordinating the dynamic loading and execution of diagnostic modules. This intermediary layer simplifies the firmware management complexity by centralizing the coordination logic and providing a standardized interface for IDM management.
3Volume of moving object
If limited SPI memory is used, then device size is reduced, but storage capacity for IDMs is insufficient
Solution Approach 1:
The system transitions from two-dimensional SPI memory storage to three-dimensional hierarchical storage by implementing a file system layer. IDMs are stored as files on the file system (providing extensive capacity) and selectively loaded into SPI memory for execution, adding a dimensional layer that decouples storage capacity from device size.
Data Source
AI summary
A firmware management operation. The firmware management operation includes providing an information handling system with a distributed BIOS; identifying information handling system diagnostics data, the information handling system diagnostics data being associated with an independent diagnostics module; authenticating the independent diagnostics module; and, executing the independent diagnostics module on the information handling system via a diagnostics event manager.