Multi-System Set Configuration for Utility Node Firmware Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Updating software and firmware on utility node devices, such as smart utility meters and control devices, is complex and time-consuming due to different versions and types of devices requiring different update files, leading to inefficient transmission and installation processes.
Innovation Solution
The use of an update package that includes delta files containing differences between software or firmware versions, allowing devices to selectively install only the necessary updates, and a multi-system set configuration where idle system sets can be updated without disrupting active operations, enabling efficient transmission and maintenance of device functionality during updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If full software/firmware update files are transmitted to utility node devices, then complete updates can be performed, but transmission time and update time increase substantially
Solution Approach 1:
The update package is segmented into multiple delta files, where each delta file contains only the differences between software/firmware versions. This segmentation allows devices to receive and apply only the necessary update portions rather than complete update images, significantly reducing transmission time and update duration while maintaining complete update functionality.
Solution Approach 2:
The patent extracts only the essential update information (differences between versions) from complete update files. By using delta files that contain only the changes needed rather than full software/firmware images, the system removes unnecessary data transmission and processing overhead while preserving the ability to perform complete updates.
2Ease of operation
If update files are transmitted wirelessly to utility node devices, then remote updates are enabled, but transmission time increases substantially due to file size
Solution Approach 1:
The update package is divided into multiple smaller delta files that can be transmitted wirelessly in segments. This segmentation reduces the burden on wireless communication channels, enabling remote updates to proceed faster and more efficiently while maintaining the capability to update devices remotely without physical access.
3Device complexity
If a single system set is updated, then the update process is simple, but device operation is disrupted during the update
Solution Approach 1:
The system dynamically manages multiple system sets (active, idle, and fail-safe) and can switch between them during updates. This dynamic configuration allows the device to maintain operational continuity by keeping the active system set running while updating idle system sets, and can switch to fail-safe modes if needed, thereby maintaining productivity without significantly increasing update process complexity.
Solution Approach 2:
The system prepares multiple system sets in advance (active, idle, and fail-safe configurations) so that updates can be performed on idle system sets while the active system set continues to operate. This preliminary preparation of redundant system sets enables seamless updates without disrupting device operation.
4Reliability
If different update files are used for different device versions and types, then accurate updates are provided, but update complexity increases
Solution Approach 1:
The update package structure is designed to be universal and adaptable to different device versions and types. The delta file format and package organization can accommodate various software/firmware versions and device configurations through a consistent framework, reducing update management complexity while maintaining accurate updates for diverse devices.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A system set of a utility node device, such as a kernel and/or root file system, may be updated by utilizing a multi-system set configuration. For example, the multi¬ system set configuration may include a first system set that is generally configured to act as an "active" set, a second system set (e.g., "idle" set) that is configured to operate when the first system set is non-operational or in an "idle" state, and a third system set that is configured to operate when the first and second system sets are non- operational. During an update of a system set, an update package may be applied to the second "idle" system set, while the first "active" system set remains operational. The utility node device may comprise a smart utility meter, sensor, control device, transformer, switch, relay, or the like.