Wireless Data Synchronization via Active Agents

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data synchronization systems between handheld and desktop computers are limited, as they often require mechanical and electrical connections, lack active agents on handheld devices, and do not support peer-to-peer synchronization, authentication, or encryption using self-signed certificates, and fail to synchronize email account setup information and certain data types effectively.

Innovation Solution

A software architecture that includes separate components for data retrieval and storage, enabling peer-to-peer synchronization through active agents on both devices, using version identifiers to manage compatibility and synchronization, and allowing selective updating of software components, with support for authentication and encryption.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If mechanical and electrical connection through dock is used for synchronization, then reliable data transfer is achieved, but device portability and ease of operation are reduced

Engineering Contradiction:
Improvedata transfer reliabilityVSAvoiddevice portability
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent replaces the mechanical connection system (physical dock with electrical connectors) with a wireless communication system. The handheld device establishes synchronization through wireless signals (e.g., infrared, radio frequency) without requiring physical docking, thereby maintaining data transfer reliability while significantly improving device portability and ease of operation.

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

2Device complexity

If host computer performs all synchronization operations without active agent on handheld device, then device complexity is reduced, but synchronization reliability and data integrity are compromised

Engineering Contradiction:
Improvehandheld device complexityVSAvoidsynchronization reliability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent implements a self-service model where the handheld device includes its own active synchronization agent that autonomously manages synchronization operations. This agent on the handheld device (not requiring complex host-side control) independently handles data comparison, transfer coordination, and conflict resolution, thereby improving synchronization reliability while keeping the handheld device complexity manageable through modular design.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If separate software components are used for data retrieval and storage, then adaptability and versatility are improved, but device complexity increases

Engineering Contradiction:
Improvesoftware component adaptabilityVSAvoidsoftware architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies segmentation by dividing the synchronization system into separate, independent software components: a data retrieval component, a data storage component, and a synchronization agent. These modular components can be developed, updated, and configured independently, improving adaptability and versatility. The segmentation is managed through standardized interfaces and protocols, preventing uncontrolled complexity increase.

Inventive Principle:
Principle #1Segmentation

4Adaptability or versatility

If version identifiers are used to manage software compatibility, then adaptability is improved, but synchronization time increases

Engineering Contradiction:
Improvesoftware version compatibilityVSAvoidsynchronization time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by having the synchronization agent on the handheld device proactively query the host computer's software version identifiers before initiating synchronization. Version compatibility is determined in advance through version negotiation protocols, allowing the system to pre-determine compatible data formats and synchronization methods. This preliminary version checking prevents time-consuming compatibility issues during actual data transfer.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8886600B2Synchronization methods and systems
Publication Date: 2014.11.11 APPLE INC
  • US8886600B2 patent drawing
  • US8886600B2 patent drawing
  • US8886600B2 patent drawing

AI summary

Synchronization architectures, methods, systems, and computer readable media are described. One exemplary embodiment includes a first software component configured to cause retrieval and storage of structured data for a first data class from a first store on a device, such as a first data processing system, and configured to synchronize structured data for the first data class in the first store with structured data of the first data class in a second store on a host, such as a second data processing system. The first software component is separate from an application software which provides a user interface to allow a user to access and edit the structured data. The first software component synchronizes the structured data through a second software component which interfaces with the host and the device and which controls an order of synchronizing and a plurality of data classes including the first data class.