Database Synchronization Delay in Radio Communication Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In radio communication systems, data synchronization between database copies is problematic due to bandwidth constraints, leading to interference with other applications and inefficient use of devices, especially when performed over radio air interfaces.

Innovation Solution

A user-controlled method allows delaying synchronization operations for a selected period, enabling synchronization to occur during periods of reduced communication activity, such as at night, using a user actuator and delay selector to avoid interfering with other applications and optimize radio communication system usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If synchronization operations are performed immediately when needed, then data consistency between database copies is maintained, but other applications are interfered with and system performance is degraded

Engineering Contradiction:
Improvedata consistencyVSAvoidapplication performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system dynamically adjusts the timing of synchronization operations based on system conditions and user needs. The synchronization is not performed at a fixed schedule but is flexible, allowing users to delay it when applications require optimal performance. This dynamic approach resolves the contradiction by making the system adapt its behavior to current operational requirements.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system performs preliminary actions by preparing synchronization data and identifying changes before actually executing the synchronization transfer. This preliminary preparation allows the system to minimize the actual data transfer time and resource consumption when synchronization does occur, thereby reducing interference with applications while maintaining data consistency.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If synchronization operations are delayed to avoid interfering with applications, then application performance is improved, but data consistency is compromised

Engineering Contradiction:
Improveapplication performanceVSAvoiddata consistency
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary actions by tracking and identifying data changes locally before synchronization is needed. This preliminary tracking ensures that when synchronization does occur, only the necessary updates need to be transferred, maintaining data consistency even with delayed execution.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where the mobile node continuously monitors for data changes and maintains information about what needs to be synchronized. This feedback loop ensures that delayed synchronization operations can still achieve data consistency by using the accumulated change information to guide the synchronization process.

Inventive Principle:
Principle #23Feedback

3Measurement precision

If synchronization is performed frequently to maintain data consistency, then data accuracy is improved, but bandwidth consumption increases and system resources are wasted

Engineering Contradiction:
Improvedata accuracyVSAvoidbandwidth consumption
Core Design Contradiction:
Measurement precisionVSLoss of energy

Solution Approach 1:

The system applies partial action by transferring only the specific data changes that need synchronization rather than performing complete database transfers. This selective synchronization maintains data accuracy while significantly reducing bandwidth consumption compared to full synchronization approaches.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system performs preliminary identification of data changes before synchronization, allowing it to prepare a minimal set of updates that need to be transferred. This preliminary action ensures that synchronization maintains data accuracy while minimizing the actual data transfer volume and associated bandwidth consumption.

Inventive Principle:
Principle #10Preliminary action

4Reliability

If synchronization operations are performed during high-usage periods, then data consistency is maintained, but system usage efficiency is reduced

Engineering Contradiction:
Improvedata consistencyVSAvoidsystem usage efficiency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system dynamically schedules synchronization operations based on system usage conditions. Users can delay synchronization during high-usage periods when applications require optimal performance, and schedule it for later when system resources are more available. This dynamic scheduling maintains data consistency while optimizing system usage efficiency.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system performs preliminary tracking of data changes during high-usage periods without executing the actual synchronization transfer. This preliminary action allows the system to maintain awareness of data consistency requirements while deferring the resource-intensive transfer operation to a more appropriate time when system usage is lower.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS7430426B2Apparatus, and associated method, for selectably delaying synchronization of database copies in a radio communication system
Publication Date: 2008.09.30 MALIKIE INNOVATIONS LTD
  • US7430426B2 patent drawing
  • US7430426B2 patent drawing
  • US7430426B2 patent drawing

AI summary

Apparatus, and an associated method, for selectably delaying performance of synchronization operations in which database copies are placed in match with one another. A user of a mobile node at which a database copy is maintained selectably actuates an actuator to select delay of performance of the synchronization operations. Once selection is made to delay the performance of the synchronization operations, selection is further made by a delay selector of the delay period prior to which synchronization operations are carried out.