Mobile M2M Data Exchange via Local Index Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional mobile M2M communication methods require high bandwidth and online connectivity to function effectively, leading to process interruptions and secondary monitoring damage when connectivity is restricted or missing, resulting in inefficient data transmission and analysis.

Innovation Solution

A method and apparatus for data and message transmission between mobile units and a backend system using local and master indexes for synchronization and replication, enabling data exchange via ad-hoc networks even with restricted connectivity, utilizing local databases and master databases with acknowledgement protocols to minimize data volume and ensure continuous process operation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional online connectivity with high bandwidth is used for data transmission, then data transmission reliability is improved, but adaptability to restricted connectivity conditions deteriorates

Engineering Contradiction:
Improvedata transmission reliabilityVSAvoidadaptability to restricted connectivity
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system dynamically adapts its data transmission behavior based on connectivity conditions. When connectivity is restricted, the system automatically adjusts by using local databases to store and process data locally, only transmitting when connectivity is available. This dynamic adaptation resolves the contradiction by making the system flexible to different connectivity scenarios while maintaining reliability through local data processing capabilities.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

A local database acts as an intermediary between the mobile unit and the backend system. This intermediary stores data locally when connectivity is restricted and synchronizes with the backend when connectivity is available, thereby enabling reliable data transmission across varying connectivity conditions without requiring constant high-bandwidth connection.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If data is continuously transmitted to backend system, then data analysis and process control are improved, but data traffic volume increases

Engineering Contradiction:
Improvedata analysis efficiencyVSAvoiddata traffic volume
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

The system extracts only the essential data that needs to be transmitted to the backend system, storing other data locally in the local database. By selectively transmitting only necessary data rather than all generated data, the system maintains effective data analysis and process control while significantly reducing data traffic volume.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Instead of continuously transmitting all data, the system performs partial transmission by sending only the critical subset of data to the backend. This partial action approach ensures that data analysis and process control remain effective while minimizing the overall data traffic volume consumed by transmissions.

Inventive Principle:
Principle #16Partial or excessive action

3Loss of information

If local database stores all generated data, then data availability for analysis is improved, but storage requirements and data synchronization complexity increase

Engineering Contradiction:
Improvedata availabilityVSAvoidsynchronization complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The system creates a local copy of essential data in the local database rather than storing all generated data. This copying approach ensures data availability for local processing and analysis while reducing the burden of synchronizing massive amounts of data with the backend, thereby lowering synchronization complexity.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system applies local quality by storing different types of data in different locations based on their characteristics. Critical data that needs frequent access is stored locally in the local database, while other data remains at the backend. This differentiated storage strategy improves data availability for essential operations while reducing synchronization complexity by only syncing necessary data.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS9904700B2Method and apparatus for guaranteeing and optimizing data exchange in mobile M2M communication with restricted connectivity
Publication Date: 2018.02.27 DEUTSCHE TELEKOM AG
  • US9904700B2 patent drawing
  • US9904700B2 patent drawing
  • US9904700B2 patent drawing

AI summary

A method for transmitting data from a mobile unit to a backend system includes, when connectivity is present between the mobile unit and the backend system: receiving, by the mobile unit, a master index from the backend system, deleting, by the mobile unit, data of the local database which are contained in the master database based on a comparison of a local index with the master index and updating the local index, transmitting, by the mobile unit, data stored in the local database which are not yet contained in the master database, receiving and storing a new master index from the backend system, and deleting the transmitted data of the local database based on a comparison of the updated local index with the new master index and further updating the local index.