Platform Application Continuity Across OS Installations
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Information handling systems face challenges in installing and maintaining platform applications across multiple operating system installations, as existing OS applications may not be adequate for specific hardware characteristics, leading to discontinuity and inefficiency.
Innovation Solution
The system executes IHS firmware from a non-volatile memory medium, retrieves and copies initialization executables to volatile memory, registers subroutines, and stores addresses in data structures compliant with ACPI, enabling platform applications to be installed and reinstalled across different OS installations on various non-volatile media, ensuring continuity and granular control.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If existing OS applications are used, then the system can operate with standard applications, but the applications cannot be adequately tailored to specific hardware characteristics
Solution Approach 1:
The patent segments the application layer into platform applications that are separate from the operating system. These platform applications are stored in a platform application storage area and can be independently managed, allowing them to be customized for specific hardware characteristics without complicating the overall system structure.
Solution Approach 2:
The patent introduces a platform application layer as an intermediary between the operating system and the hardware. This platform application layer acts as a mediator that can be customized for specific hardware characteristics while maintaining compatibility with the underlying operating system, thus improving adaptability without requiring complete application rewriting.
2Stability of the object's composition
If platform applications are installed across multiple OS installations, then continuity is achieved, but the system requires complex memory management and address tracking
Solution Approach 1:
The patent merges the platform application storage with the system's memory management structure by integrating it into the memory map. The platform application storage area is incorporated into the memory map that is generated during system initialization, allowing the system to track and manage platform applications across multiple OS installations through a unified memory management approach.
Solution Approach 2:
The patent performs preliminary registration of platform applications during system initialization. The firmware executes before the operating system and pre-registers platform applications in a data structure, creating a head start for memory management. This preliminary action establishes the foundation for maintaining continuity across OS installations without requiring complex runtime management.
3Stability of the object's composition
If firmware executes before operating system to install platform applications, then continuity across OS installations is enabled, but the process requires multiple execution stages and coordination
Solution Approach 1:
The patent implements a dynamic boot process where the system adapts its execution flow based on the presence of platform applications. The firmware dynamically determines whether to execute the standard boot process or to first register platform applications. This dynamic approach enables continuity across OS installations while managing boot process complexity through adaptive execution paths.
Data Source
AI summary
In one or more embodiments, one or more systems, one or more methods, and/or one or more methods may: register a subroutine configured to store multiple addresses of a volatile memory medium VMM of an information handling system (IHS); for each IHS initialization executable/OS executable pair of multiple IHS initialization executable/OS executable pairs: retrieve, from a first non-volatile memory medium (NVMM), an IHS initialization executable of the IHS initialization executable/OS executable pair; copy, by the IHS initialization executable, an OS executable of the IHS initialization executable/OS executable pair from the first NVMM to the VMM; call, by the IHS initialization executable, the subroutine; store, by the subroutine, an address associated with the OS executable via a data structure stored by the VMM; and copy, by a first OS executable, the OS executable from the VMM to a second NVMM based at least on the address associated with the OS executable.