Background Data Synchronization via Push Email Protocols

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data synchronization technologies require user intervention and foreground application operation, leading to battery depletion and performance degradation due to elevated application activity, especially when synchronizing across devices with different operating systems.

Innovation Solution

Implementing a method for application data synchronization through a communication network using Push Email Synchronization protocols, where data is received and formatted based on formatting parameters to facilitate seamless transfer across heterogeneous devices, allowing for background operation and reduced resource utilization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data synchronization is performed using foreground application operation, then synchronization reliability is improved, but battery depletion and device performance degradation occur

Engineering Contradiction:
Improvesynchronization reliabilityVSAvoidbattery depletion
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system enables automatic background synchronization where the synchronization service operates autonomously without requiring foreground application operation. The service automatically detects data changes, formats data according to target device specifications, and transmits data through push email protocols, eliminating the need for users to manually launch applications while maintaining reliable synchronization.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces the mechanical user interaction model (foreground application operation) with an automated background service model. Instead of requiring users to manually open and operate applications for synchronization, the system uses background services that automatically monitor, format, and transmit data, substituting manual mechanical operations with automated system processes.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Reliability

If data synchronization is performed using foreground application operation, then synchronization reliability is improved, but device performance degradation occurs

Engineering Contradiction:
Improvesynchronization reliabilityVSAvoiddevice performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The synchronization service operates autonomously in the background, automatically detecting data changes and executing synchronization without requiring user intervention or foreground application operation. This self-service approach maintains reliable synchronization while preventing performance degradation by eliminating the need for users to manually launch and operate applications.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements periodic background monitoring that automatically detects data changes at scheduled intervals or when changes occur, rather than requiring continuous foreground application operation. This periodic action maintains synchronization reliability while allowing the device to enter low-power states, thereby preserving performance.

Inventive Principle:
Principle #19Periodic action

3Speed

If direct connection between computing devices is used for data synchronization, then synchronization speed is improved, but device complexity and user intervention requirements increase

Engineering Contradiction:
Improvesynchronization speedVSAvoidsystem complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary system (synchronization service server) that mediates between source and target devices. The server receives data from source devices, formats it according to target device specifications, and transmits it through push email protocols. This intermediary approach simplifies the overall system architecture by centralizing synchronization logic and eliminating the need for direct peer-to-peer connections.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system changes the synchronization parameters by using push email protocols instead of direct connections. The formatting parameters are adjusted to match target device specifications (different operating systems), and the transmission mechanism is changed to background push notifications, thereby reducing complexity while maintaining speed.

Inventive Principle:
Principle #35Parameter changes

4Adaptability or versatility

If formatting parameters are adjusted for different operating systems, then adaptability is improved, but data processing time increases

Engineering Contradiction:
Improvecross-platform adaptabilityVSAvoiddata processing time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The synchronization service performs preliminary formatting actions in advance, where data is formatted according to target device specifications before transmission. By pre-formatting the data and preparing it in advance, the system reduces processing time during actual synchronization operations and enables faster data delivery to target devices.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11297135B2Data synchronization
Publication Date: 2022.04.05 TATA CONSULTANCY SERVICES LTD
  • US11297135B2 patent drawing
  • US11297135B2 patent drawing
  • US11297135B2 patent drawing

AI summary

The present subject matter discloses a method for application data synchronization through a communication network. The method includes receiving application data from at least one user device, formatting the application data based on at least one formatting parameter to generate a data file, where the formatting parameter is indicative of a format of the data file, and transmitting the data file to at least one target syncing device through protocols based on Push Email Synchronization.