Distributed Memory Space for OTA Updates in Non-OS IoT Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Non-operating system (non-OS) embedded devices in IoT networks face challenges with scarce storage size and limited memory resources, leading to inefficient and resource-hungry OTA software system update processes, often requiring external storage and repeated transfers due to limited flash memory capacity and potential errors during updates.
Innovation Solution
Implementing a distributed memory space (DMS) where non-OS embedded devices allocate and share memory resources across the network, allowing data to be stored and distributed among devices, reducing the need for individual device storage and enabling efficient, error-resistant OTA updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If OTA software system update is performed on a single device with limited flash memory, then the update process can be executed, but the flash memory is not large enough to store both the existing system and the new update data simultaneously
Solution Approach 1:
The patent merges the memory resources of multiple IoT devices into a unified distributed memory space. When one device needs to perform an OTA update, it can utilize the flash memory of other devices in the network to store the update data, effectively combining the storage capacity of multiple devices to solve the limitation of individual device memory.
Solution Approach 2:
The patent transitions from a single-device memory model to a network-wide distributed memory model. By introducing the network dimension, the system allows devices to access and utilize memory resources across the network rather than being confined to local storage, effectively expanding the available memory space for OTA updates.
2Ease of operation
If a larger external flash is equipped on each device to avoid using additional storing devices, then the OTA update can be performed on a single device, but the external flash is quite slow and expensive
Solution Approach 1:
The patent makes the flash memory of each device serve multiple functions: not only storing the device's own system data but also serving as shared storage for the entire network. This multi-functionality allows any device to contribute its memory capacity to the distributed memory space, eliminating the need for each device to have dedicated large external flash.
Solution Approach 2:
The patent creates a virtual copy of the distributed memory space accessible to all devices. When a device needs to perform an OTA update, it can access the update data stored in the distributed memory space of other devices, effectively copying the data transfer capability without requiring physical external flash on each device.
3Productivity
If the same image is needed by multiple devices in the network, then the OTA software system update transfer is performed repeatedly for each loT device, but this results in inefficient data distribution and increased network traffic
Solution Approach 1:
The patent implements preliminary storage of update images in the distributed memory space before they are needed by individual devices. When an update image is received by one device, it is stored in the network's distributed memory, so that subsequent devices can directly access this pre-stored image without requiring repeated transfers from the source.
Solution Approach 2:
The patent introduces the distributed memory space as an intermediary between the update source and multiple target devices. Instead of direct peer-to-peer updates that require repeated transfers, the distributed memory acts as a central repository that mediates the data distribution, allowing multiple devices to efficiently access the same update image.
Data Source
Figure 1
Figure 2
Figure 2
AI summary
A communication network (401) for operating a distributed memory system (DMS) is described. The communication network (401) comprises a plurality of non-operating system (non-OS) embedded devices having at least one memory (390) wherein the at least one memory (390) of the plurality of non-OS embedded devices is configured to have a first portion of memory (310, 330, 350, 370) reserved for the non-OS embedded device and a second portion of memory (320, 340, 360, 380) reserved and available for at least one other non-OS embedded device from the plurality of non-OS embedded devices within the communication network to use.