Firmware Publication of Multiple Binary Images via Segmented Tables
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods, such as the Windows® Platform Binary Table (WPBT), allow only a single binary image to be published by firmware, limiting the deployment of multiple binary images, including those of OEMs and other software agents, in an operating system.
Innovation Solution
An extension to the WPBT is introduced, enabling the publication of multiple binary images during booting, where a manager binary is saved to the file system and executes to deploy secondary binary images, allowing OEMs to include their own images alongside the Absolute® Persistence® Agent.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the Windows Platform Binary Table (WPBT) is used to deploy binary images from firmware, then a single binary image can be published to the operating system, but the ability to deploy multiple binary images (including OEM and other software agents) is limited
Solution Approach 1:
The patent segments the binary table into multiple independent entries, each capable of holding a separate binary image. Instead of a single monolithic binary table structure that accommodates only one image, the system creates a plurality of binary table entries (e.g., first binary table entry, second binary table entry), where each entry independently stores information about a specific binary image including its location, size, and execution parameters. This segmentation enables the firmware to publish multiple binary images to the operating system simultaneously.
2Adaptability or versatility
If only a single binary image is published by firmware using traditional WPBT, then the deployment process is simple, but OEMs cannot include their own binary images alongside the Absolute Persistence Agent
Solution Approach 1:
The patent implements a universal binary table structure that serves multiple functions and multiple parties. Each binary table entry is designed with a standardized format that can accommodate different types of binary images from different sources (Absolute Persistence Agent, OEM software, third-party agents). The structure includes universal fields such as image location, image size, image type identifier, and execution flags that work consistently regardless of the image source. This multi-functionality allows the same firmware mechanism to serve multiple deployment needs simultaneously.
Data Source
AI summary
Multiple binary images stored in the firmware of an electronic device are written to the device's configuration tables during booting of the device, where one of the binary images is a manager binary. During booting, the manager binary is saved to the file system of the operating system such that it automatically executes upon completion of booting. The manager binary then deploys the other binary images.