Firmware Virtualization Platform for Remote Device Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing firmware update processes for electronic devices are cumbersome, requiring manual intervention, limited by embedded memory size, and inconvenient, especially with the proliferation of network connectivity and cloud-based deployments.
Innovation Solution
A method and apparatus for firmware virtualization that allows user devices to remotely access and execute firmware processes from a cloud-based platform, enabling faster deployment and expansion of firmware capabilities without modifying the embedded firmware.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If firmware is stored in embedded non-volatile memory (ROM, EEPROM, flash memory), then firmware provides persistent control functionality for the device, but firmware updates require manual intervention, physical changing of ROM integrated circuits, or complex reprogramming procedures that interrupt device operation
Solution Approach 1:
The patent segments firmware functionality into two parts: a minimal boot firmware permanently stored in embedded non-volatile memory that provides basic device initialization, and a virtualized firmware layer stored remotely on external storage devices that provides the actual device functionality and can be updated without interrupting operation. This segmentation allows the system to maintain reliable persistent firmware while enabling convenient remote firmware updates.
Solution Approach 2:
The patent introduces a firmware virtualization layer that acts as an intermediary between the embedded boot firmware and the actual device operations. This virtualization layer loads firmware instructions from external storage devices over the network, executes them, and returns results to the boot firmware, thereby enabling remote firmware updates without requiring manual intervention or device interruption.
2Stability of the object's composition
If firmware is permanently installed in embedded memory, then firmware provides stable device control, but firmware capability expansion requires increasing embedded memory size which increases device cost and complexity
Solution Approach 1:
The patent moves firmware storage from the traditional single-dimension embedded memory space to a multi-dimensional architecture where firmware is stored externally on network-accessible storage devices. This dimensional change allows the device to access virtually unlimited firmware capacity over the network while maintaining a small, stable embedded memory footprint for boot operations, thereby enabling firmware capability expansion without increasing device cost or complexity.
3Adaptability or versatility
If firmware updates are deployed via traditional methods, then firmware can be updated with bug fixes and new features, but update deployment is slow and requires manual user initiation and device restarting
Solution Approach 1:
The patent implements a self-service firmware update mechanism where the virtualized firmware layer automatically checks for updates, downloads new firmware versions from remote storage devices over the network, and executes the update process without requiring manual user initiation or device restarting. The system continuously operates with updated firmware while maintaining device functionality, thereby dramatically improving firmware update speed and productivity.
Data Source
AI summary
A system and method operative to virtualize firmware of a user device. The method comprises storing, on a virtualized firmware platform (VFP), a virtualized firmware for being executed on the VFP, the virtualized firmware corresponding to a firmware stored in and for execution on the user device. The method further comprises receiving, on the VFP, firmware data from the firmware in the user device via a network, the firmware data comprising a command for deploying at least one remote process on the VFP. The method further comprises mapping the firmware data to the virtualized firmware, inserting the firmware data into the virtualized firmware, executing the virtualized firmware on the VFP, and deploying the at least one remote process on the VFP as a part of the execution of the virtualized firmware on the VFP.