Remote Device Updates with Distributed Rollback Storage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing remote update methods for devices, particularly IoT devices, require substantial memory for storing previous software versions for rollback, which is inefficient for devices with limited memory capacity and necessitates increasing memory capacity as software sizes grow.
Innovation Solution
A method for remotely updating devices in a distributed system where devices share and store defined portions of the software image, allowing rollback from other devices if the update fails, reducing the memory requirement for storing previous versions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the device stores the previous version of software locally for rollback purposes, then rollback reliability is improved, but memory capacity is consumed
Solution Approach 1:
The software image is divided into multiple portions (first portion, second portion, third portion, etc.) that are distributed across multiple devices in the group. Each device stores only a segment of the complete previous version, reducing individual memory requirements while maintaining collective rollback capability.
Solution Approach 2:
Multiple devices are combined into a distributed storage system where each device contributes its stored software image portions to collectively provide the complete previous version for rollback. The devices work together as a unified storage resource.
2Adaptability or versatility
If the device stores complete previous version for rollback, then rollback capability is ensured, but memory usage increases
Solution Approach 1:
The complete software image is segmented into multiple portions that are distributed across different devices. Each device stores only a fraction of the total image, reducing individual memory usage while the collective group maintains complete rollback capability.
Solution Approach 2:
Other devices in the group act as intermediaries that store and provide the portions of the software image that are not stored locally. When rollback is needed, the device requests missing portions from other devices in the group.
3Adaptability or versatility
If memory capacity is increased to handle growing software sizes, then rollback of larger software versions is supported, but device cost and complexity increase
Solution Approach 1:
The group of devices serves multiple functions: each device runs its own software and collectively provides shared storage for software image portions. This multi-functionality allows the system to support rollback of large software versions without increasing individual device memory capacity.
Solution Approach 2:
The solution moves from a single-dimension approach (one device storing all software images) to a multi-dimensional distributed approach across multiple devices. This dimensional change allows the system to handle larger software sizes by distributing the storage burden across the group.
Data Source
Figure 1
Figure 2
Figure 3~5
AI summary
A method for remotely updating a plurality of devices wherein the plurality of devices form a distributed system for memory usage is disclosed. The method comprises selecting (101) a group of devices for an update wherein the devices in the group each comprise a software image of a same current version of software executing in the devices, determining (102) one or more local portions of the software image for a device of the group to store in memory, and transmitting (103) a signal to the device comprising information about the one or more local portions of the software image to store, and executing the determining and the transmitting steps for each device in the group of devices. The method further comprises receiving (104), at a first device of the plurality of devices, a software package for an update from a remote unit, obtaining (105), by the first device, information to store one or more local portions of a software image locally in the first device wherein the one or more local portions each comprises a defined portion of a current version of software executing in the first device, and storing (106), in the first device, the one or more local portions of the software image in memory. Corresponding computer program product and apparatus are also disclosed.