FOTA Update Resumption via Server-Side Status Tracking

Solution Overview

Problem

Firmware-over-the-air (FOTA) updates in IoT networks face challenges when wireless devices de-register during the update process, leading to incomplete or interrupted updates, as existing solutions lack effective tracking and resumption mechanisms for maintaining update status and continuity.

Innovation Solution

Implementing a server system that uses read and observe requests to track the firmware version and latest successful update status of wireless devices, allowing for the resumption of updates from the last successful status upon re-registration, and saving update information to a database for efficient tracking and management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If FOTA update is interrupted due to device de-registration, then update completeness deteriorates, but if full package re-download is performed, then time and power consumption increase

Engineering Contradiction:

Improveupdate completenessVSAvoidupdate time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The server system performs preliminary tracking of update status by sending read and observe requests to the device before and during the update process. This preliminary action captures the latest successful update status, enabling resumption rather than restart when interruptions occur, thus reducing time loss while maintaining update completeness.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where the device reports its update status to the server through observe requests. This feedback loop allows the server to track the current firmware version and latest successful update status, enabling intelligent decision-making about whether to resume or restart updates, thereby balancing reliability and time efficiency.

Inventive Principle:

Principle #23Feedback

2Reliability

If FOTA update is interrupted due to device de-registration, then update completeness deteriorates, but if full package re-download is performed, then power consumption increases

Engineering Contradiction:

Improveupdate completenessVSAvoiddevice power consumption

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

The server system performs preliminary tracking of update status by sending read and observe requests to the device before and during the update process. This preliminary action captures the latest successful update status, enabling resumption rather than restart when interruptions occur, thus reducing power consumption while maintaining update completeness.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where the device reports its update status to the server through observe requests. This feedback loop allows the server to track the current firmware version and latest successful update status, enabling intelligent decision-making about whether to resume or restart updates, thereby balancing reliability and power efficiency.

Inventive Principle:

Principle #23Feedback

3Productivity

If tracking mechanism is implemented to resume updates, then system complexity increases, but if no tracking is performed, then update management efficiency deteriorates

Engineering Contradiction:

Improveupdate management efficiencyVSAvoidtracking system complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The server acts as an intermediary that handles the complexity of tracking and status management. Instead of implementing complex tracking systems within each resource-constrained device, the server performs read and observe requests to track update status centrally. This approach improves update management efficiency while minimizing the complexity burden on individual devices.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The device maintains local information about its firmware version and update status, serving its own tracking needs without requiring complex external infrastructure. The simple observe request mechanism allows the device to self-report status to the server, achieving efficient update management with minimal added complexity.

Inventive Principle:

Principle #25Self-service

Data Source

PatentUS20240385827A1Firmware-over-the-air (FOTA) update for wireless devices in an internet of things (IOT) network

Publication Date: 2024.11.21 T MOBILE US INC

AI summary

A server system for updating firmware of a client device in an IoT network receives an indication that the client device has re-registered after being de-registered. The server system determines a current version of firmware and a latest successful status of a FOTA update on the client device. When the current version of the firmware corresponds to a latest version of the firmware available, the server system saves information regarding the latest version of the firmware to its database. When the current version of the client device does not correspond to the latest version of the firmware available, the server system transmits an upgrade package of the FOTA update and an indication of the latest successful status of the FOTA update to the client device. The server system thereby enables the client device to continue the FOTA update from the latest successful status of the FOTA update.