IoT Data Reconciliation via Local Checksum Payloads

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Inconsistent data between IoT devices leads to synchronization mismatches and poor data integrity, particularly in scenarios where multiple devices receive updates at different times, causing issues in failure situations.

Innovation Solution

A computer-implemented method utilizing local IoT devices to reconcile data mismatches by determining if all devices have received an update impulse from a server, retrieving data since the last shared checksum from non-updated devices, packaging this data into a payload, and sending it through a reconciliation channel for synchronization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple IoT devices subscribe to the same hook for updates from a server, then each device can receive notifications independently, but data inconsistency occurs between devices receiving updates at different times

Engineering Contradiction:
Improvedata consistencyVSAvoidsynchronization delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by having the first IoT device proactively detect the update impulse from the server and initiate a data retrieval and sharing process with the second device before the second device would naturally request or receive the update. This preliminary detection and forwarding mechanism ensures the second device receives data without waiting for its own update cycle, thereby maintaining data consistency while minimizing synchronization delay.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If IoT devices retrieve and share data locally to maintain synchronization, then data consistency is improved, but device complexity and communication overhead increase

Engineering Contradiction:
Improvedata integrityVSAvoidsynchronization mechanism complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system introduces an intermediary role where the first IoT device acts as a mediator between the server and the second IoT device. Instead of implementing complex peer-to-peer synchronization protocols between all devices, the first device receives the update impulse from the server and mediates the data transfer to the second device. This intermediary approach simplifies the overall system architecture by centralizing the synchronization logic in one device rather than requiring complex inter-device communication protocols.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11132352B1Utilizing local IoT devices to reconcile data mismatches
Publication Date: 2021.09.28 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11132352B1 patent drawing
  • US11132352B1 patent drawing
  • US11132352B1 patent drawing

AI summary

A computer-implemented method, a computer program product, and a computer system for utilizing local IoT devices to reconcile data mismatch. A first IoT device in a group of IoT devices determines whether all of the IoT devices have received the update impulse from a server, in response to receiving an update impulse from the server. The first IoT device retrieves data since a last checksum shared by the first IoT device and a second IoT device, in response to determining that the second IoT device in the group has not received the update impulse from the server. The first IoT device packages the data since the last checksum into a payload and sends, through a reconciliation channel of the group, the payload to the second IoT device. The second IoT device reconciles a data mismatch, based on the payload.