Mesh Network Device OTA Upgrade Recovery via Neighbor Node

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing IoT devices face challenges in efficient memory management during Over-The-Air (OTA) upgrades, requiring additional memory capacity for backup files and potential recovery processes, which increases costs and inefficiencies.

Innovation Solution

Implementing a method where a mesh network device identifies a neighboring device as a recovery node to facilitate upgrades and recoveries, allowing for direct file replacement without retaining a backup copy, and using the neighbor device to provide recovery files if the upgrade fails.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If additional memory capacity is allocated for backup files during OTA upgrades, then device reliability is improved, but device cost and memory efficiency deteriorate

Engineering Contradiction:
Improveupgrade reliabilityVSAvoidmemory capacity
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent merges the backup function with a neighboring device in the mesh network. Instead of allocating separate backup memory within each device, the system combines storage resources across multiple devices, allowing device A to use device B's memory as a backup location during OTA upgrades.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The neighboring device acts as an intermediary for backup operations. It receives and stores backup files from devices performing upgrades, effectively serving as a temporary external storage medium that eliminates the need for dedicated backup memory in each individual device.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If two memory banks are partitioned for upgrade storage, then upgrade reliability is improved, but device complexity increases

Engineering Contradiction:
Improverecovery capabilityVSAvoidmemory management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the backup storage function from the device's internal memory architecture and relocates it to a neighboring device. This eliminates the need for dual memory bank partitioning and associated complex management logic within each device.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The neighboring device serves multiple functions: it acts as a mesh network participant, maintains its own operational files, and simultaneously provides backup storage services to other devices. This multi-functionality reduces overall system complexity by consolidating roles.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Reliability

If backup files are retained in memory during upgrade, then recovery reliability is improved, but memory efficiency deteriorates

Engineering Contradiction:
Improverecovery success rateVSAvoidactive memory usage
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent transitions from one-dimensional internal memory storage to multi-dimensional distributed storage across the mesh network. Backup files are stored in the memory of neighboring devices rather than being confined to the originating device's memory, effectively utilizing external storage resources.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS10735261B2Smart upgrade of connected devices in a mesh network
Publication Date: 2020.08.04 QUALCOMM INC
  • US10735261B2 patent drawing
  • US10735261B2 patent drawing
  • US10735261B2 patent drawing

AI summary

Methods of upgrading a mesh network device reduce the amount of memory required on such devices. A network device may identify a neighbor network device in response to receiving a request to perform an upgrade, and send a message configured to cause the neighbor network device to function as a recovery node. The network device may then perform the upgrade without retaining a backup image in memory. If the neighbor network device determines that the upgrade failed based on messages not received from the mesh network device being upgraded, the neighbor network device may recover the network device being upgraded by providing a file corresponding to the upgrade. The neighbor network device may determine that the upgrade failed if no response is received to a challenge message or if no indication of success is received after a time expires.