Firmware Update Management Object for Mobile Devices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for updating mobile device firmware are inefficient, leading to wasteful storage usage and network bottlenecks due to the need for numerous unique update files, especially during peak update periods.
Innovation Solution
Implementing a firmware update management object (FUMO) that specifies multiple update file locations and metadata conditions, allowing mobile devices to fetch necessary files from various sources, reducing the need for pre-generated or on-the-fly unique files and optimizing network usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If unique update files are generated ahead of time for each firmware/hardware permutation, then update readiness is improved, but storage space consumption increases significantly
Solution Approach 1:
The update system is segmented into multiple components: a master update file containing common firmware images, and multiple device-specific configuration files that reference portions of the master file. Each device receives only its specific configuration file rather than a complete unique update package, reducing storage requirements while maintaining update readiness.
Solution Approach 2:
A single master update file serves multiple device permutations by containing firmware images that can be configured for different devices through device-specific configuration files. This universal approach allows one master file to fulfill the update needs of many device variations, eliminating the need to store separate complete update packages for each permutation.
2Quantity of substance
If unique update files are generated on the fly, then storage space is reduced, but network bottlenecks occur during peak update periods
Solution Approach 1:
The master update file is prepared and stored in advance containing all necessary firmware images. Device-specific configuration files are also pre-configured to reference appropriate portions of the master file. When updates are deployed, devices receive their small configuration files immediately without waiting for on-the-fly generation, avoiding network bottlenecks while maintaining low storage requirements.
3Quantity of substance
If a single update file is used for all device permutations, then storage efficiency is improved, but device-specific update accuracy deteriorates
Solution Approach 1:
While the master update file provides a common base for all devices (global efficiency), device-specific configuration files contain localized information tailored to each device's firmware/hardware permutation (local precision). This combination ensures that each device receives the correct device-specific update instructions while benefiting from the storage efficiency of a shared master file.
Data Source
Figure 1
Figure 2~4
Figure 5
AI summary
Updating firmware on mobile devices can be performed during device management (DM) sessions between mobile devices and one or more servers. A server can provide data to at least one node of a firmware update management object (FUMO) stored at a mobile device. The data can indicate a plurality of different update file locations accessible via a network. The mobile device can download a plurality of update files from the plurality of different update file locations via the network in response to receiving the command. From a set of update files, each mobile device can thus obtain its particular firmware update as a subset of the update files as indicated by its FUMO. Metadata may be provided to the FUMO to express one or more conditions that the mobile device must meet in order to download respective update files.