IoT Sensor Data Management via Timestamp Conflict Resolution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing IoT systems face challenges in managing sensor data without loss or distortion, particularly due to latency issues that can lead to overwriting of older data.

Innovation Solution

A computer-implemented method and system for managing sensor data in an IoT environment, which involves receiving sensor data, determining conflicts based on reading timestamps, merging data if conflicts exist, and creating new records if no conflicts are found, thereby preventing data loss and distortion.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If newer sensor data is appended to the database, then data continuity is maintained, but data loss occurs due to overwriting of older data

Engineering Contradiction:
Improvedata continuityVSAvoiddata loss
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent segments the data storage approach by maintaining separate records for different time points. Instead of overwriting, the system creates distinct records for older and newer sensor data, each with its own timestamp. This segmentation allows both old and new data to coexist without interference, preventing information loss while maintaining continuity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies preliminary action by checking the timestamp of incoming sensor data before insertion. The system determines whether the new data is stale based on its timestamp comparison with existing records. This preliminary timestamp check prevents premature overwriting and ensures only appropriate data is inserted, maintaining data integrity.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If sensor data is ingested with latency, then network conditions are accommodated, but data distortion occurs due to overwriting

Engineering Contradiction:
Improvelatency toleranceVSAvoiddata distortion
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent implements feedback by continuously monitoring the timestamp of incoming sensor data and comparing it with existing database records. Based on this feedback, the system dynamically decides whether to insert, update, or skip data records. This feedback mechanism ensures that latency variations are accommodated without causing data distortion, as the system adapts its behavior based on timestamp comparisons.

Inventive Principle:
Principle #23Feedback

3Ease of manufacture

If time-series data is stored in conventional databases, then data storage is simplified, but information distortion occurs

Engineering Contradiction:
Improvestorage simplicityVSAvoidinformation distortion
Core Design Contradiction:
Ease of manufactureVSLoss of information

Solution Approach 1:

The patent changes the critical parameter of data storage from simple overwriting to timestamp-based record creation. By introducing and enforcing timestamp as a key parameter, the system transforms the storage mechanism to prevent information distortion. This parameter change maintains storage simplicity while eliminating the distortion problem through structured record management.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS12339830B2System and method for managing sensor data associated with an IoT environment
Publication Date: 2025.06.24 SIEMENS AG
  • US12339830B2 patent drawing
  • US12339830B2 patent drawing
  • US12339830B2 patent drawing

AI summary

A system and method for managing sensor data associated with an Internet-of-Things (IoT) environment is disclosed herein. The method includes receiving, by a processing unit, sensor data from at least one sensing unit in the IoT environment. The sensor data includes at least one sensor reading and a reading timestamp associated with the sensor reading. The method further includes determining whether a conflict exists based on the reading timestamp, wherein the conflict is associated with the sensor data overwriting an existing record in a database. The database is configured for storing the sensor data associated with the at least one sensing unit in time-series format. If the conflict exists, the method further includes merging the sensor data to the record based on an ingestion timestamp associated with the sensor data. Otherwise, a new record is created.