Firmware Update Management Object Standardization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current firmware update systems for computing devices lack a uniform scheme for updating firmware across different systems and implementations, leading to complexity due to varying methods and devices, and do not account for underlying differences in firmware update systems.
Innovation Solution
A read-only management object is created to contain information about firmware components, including a component ID, version, and user-friendly name, which is used to generate an update object that includes location information for available firmware component update packages, allowing a centralized update server to manage and distribute updates to mobile computing devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If different firmware update methods and devices are used for different computing devices, then each device can be updated according to its specific requirements, but the overall system complexity increases due to lack of uniformity
Solution Approach 1:
The patent applies universality by creating a standardized firmware update management system that can serve multiple different computing devices through a common interface. The management object model provides universal structures (firmware update objects, device information objects) that work across different device types, allowing a single update mechanism to handle diverse firmware update scenarios without requiring device-specific custom implementations for each device.
Solution Approach 2:
The patent segments the firmware update system into distinct, modular components: management objects that store device information, firmware update objects that contain update data, and a standardized interface layer that coordinates between them. This segmentation allows each component to be developed and maintained independently while working together through well-defined relationships, reducing overall system complexity.
2Device complexity
If a standardized firmware update management system is implemented across all computing devices, then system complexity is reduced and uniformity is achieved, but adaptability to specific device requirements may be limited
Solution Approach 1:
The patent implements dynamics by making the standardized management system flexible and adaptable to different device configurations. The firmware update objects can dynamically contain device-specific information such as device identifiers, firmware versions, and update requirements. The system can adapt its behavior based on the specific device it is updating while maintaining the same standardized interface and data structures.
Solution Approach 2:
The patent uses parameter changes to achieve adaptability within the standardized framework. Different device types are accommodated by varying parameters within the universal object structures, such as device-specific firmware version numbers, update URLs, and configuration parameters. This allows the same management system to handle diverse device requirements by simply changing the parameter values rather than changing the system architecture.
3Adaptability or versatility
If comprehensive device information is stored in management objects for all possible update scenarios, then all update requirements can be met, but the amount of information to be managed increases
Solution Approach 1:
The patent extracts only the essential device information needed for firmware updates into the management objects, rather than storing all possible device data. The firmware update objects contain specifically extracted parameters such as device identifiers, current firmware versions, and update package information. This selective extraction reduces the quantity of managed information while maintaining sufficient data for all update scenarios.
Solution Approach 2:
The patent implements partial action by storing only the necessary subset of device information required for firmware updates in the management objects. Rather than comprehensively storing all device parameters, the system stores exactly what is needed for update management (device ID, firmware version, update location), avoiding unnecessary data overhead while still providing complete update capability.
Data Source
AI summary
A read-only management object is created to contain information relating to firmware components that can be updated. This information includes a component identifier, a component version and a user-friendly name for the component. The information also includes a state identifier that indicates a state of a device that includes firmware components. Information from the management object can be used by other components as part of a firmware update process. An update management object is dynamically created to deliver an update package to the device. The update package can contain updates to multiple firmware components.