IoT Software Update Gateway Differential Data Reconstruction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The increasing number of IoT devices necessitates efficient software updates while minimizing data traffic in networks, as existing methods consume significant network capacity and resources.

Innovation Solution

A software update gateway that connects IoT devices to a software update server, utilizing differential update data to generate full update data, reducing public network traffic by transmitting only necessary data and managing software metadata for version control and rollback capabilities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If full update data is transmitted to each IoT device for software updates, then the update process is simple and reliable, but the data traffic in the network increases significantly

Engineering Contradiction:
Improvesoftware update reliabilityVSAvoiddata traffic
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent segments the update data transmission process into two parts: (1) transmitting only differential update data (the changes) from the server to the gateway, and (2) the gateway reconstructing the full update data locally by combining the differential data with the existing full update data stored in its database. This segmentation reduces network traffic while maintaining update reliability through the gateway's local data reconstruction capability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The gateway pre-stores full update data in its database before actual update requests occur. When an update is needed, the gateway combines this pre-stored full data with newly received differential data to reconstruct complete update packages locally, eliminating the need to transmit large full update data sets over the network during update operations.

Inventive Principle:
Principle #10Preliminary action

2Quantity of substance

If differential update data is used to reduce network traffic, then data transmission is minimized, but the gateway must perform additional processing to generate full update data

Engineering Contradiction:
Improvedata trafficVSAvoidgateway processing complexity
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The gateway acts as an intermediary between the update server and IoT devices. It receives differential update data from the server, combines it with pre-stored full update data from its database, and reconstructs complete update packages locally. This intermediary role simplifies the overall system by centralizing the complex reconstruction logic in the gateway rather than requiring complex processing in each IoT device.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The gateway creates copies of full update data by combining the received differential data with the existing full update data stored in its database. This copying approach allows the gateway to generate complete update packages for multiple devices without repeatedly transmitting the same full data sets over the network.

Inventive Principle:
Principle #26Copying

3Quantity of substance

If the gateway stores full update data in its database, then update data can be reconstructed locally, but the gateway requires more storage capacity

Engineering Contradiction:
Improvenetwork trafficVSAvoidgateway storage volume
Core Design Contradiction:
Quantity of substanceVSVolume of stationary object

Solution Approach 1:

The system changes the storage parameter from storing complete full update data sets for every possible device to storing only the essential full update data in the gateway's database, while keeping differential update data in the server's database. This parameter change optimizes storage distribution across the system.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The gateway stores partial update data (full update data for specific devices) rather than complete update data for all devices. This partial storage approach, combined with differential data reception and local reconstruction, reduces the gateway's storage requirements while maintaining the ability to generate complete updates when needed.

Inventive Principle:
Principle #16Partial or excessive action

4Measurement precision

If software metadata is verified for version compatibility, then update accuracy is improved, but the update process becomes more complex

Engineering Contradiction:
Improveversion compatibility accuracyVSAvoidupdate process complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system implements feedback through software metadata verification. The gateway checks version information, device identifiers, and compatibility data in the software metadata before reconstructing and transmitting update data. This feedback mechanism ensures that only compatible updates are applied, improving accuracy while keeping the process manageable through automated verification.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12073207B2Software update gateway and method for updating software of IoT device
Publication Date: 2024.08.27 LG ELECTRONICS INC
  • US12073207B2 patent drawing
  • US12073207B2 patent drawing
  • US12073207B2 patent drawing

AI summary

A software update gateway for updating a software of an IoT (Internet of Things) device. The gateway includes a transceiver configured to connect to a software update server through a public network, connect to at least one first IoT device through the public network, and connect to at least one second IoT device through a local network of the at least one second IoT device; a software database configured to store a first version of a full update data for a software of the at least one first IoT device; and a processor configured to control the transceiver to receive a software update request from the at least one first IoT device via the public network, control the transceiver to transfer the software update request to the software update server via the public network, control the transceiver to receive differential update data for the software of the at least one first IoT device from the software update server via the public network, generate a second version of the full update data for the software of the at least one first IoT device based on the first version and the differential update data, and control the transceiver to transmit the generated second version of the full update data of the at least one first IoT device to the at least one first IoT device via the public network based on a collected operational status of the software update gateway.