Device Data Migration via Server Intermediary

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The complexity of managing and servicing client-side computing devices increases due to multiple service-providing entities, and migrating data from one device to another with different configurations is time-consuming and costly, especially when compatibility issues arise.

Innovation Solution

A system comprising a web applications server, an account management server, and a synchronization server provides a suite of services over a wireless network, enabling software downloads, account maintenance, data management, and device migration while ensuring compatibility between different hardware and software configurations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual configuration transfer between devices with different hardware/software configurations is performed, then data migration is achieved, but time consumption and cost increase significantly

Engineering Contradiction:
Improvedata migration compatibilityVSAvoidconfiguration transfer time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent introduces a server as an intermediary between the old and new devices. The server receives configuration data from the old device, stores it in a database, and provides it to the new device. This intermediary approach eliminates direct manual configuration transfer, automatically handling compatibility issues between different device configurations through centralized data management.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements automated copying of configuration data from the old device to the server, and subsequently to the new device. Instead of manual comparison and transfer of each configuration parameter, the system creates and manages copies of the entire configuration set, automatically adapting them to the new device's hardware and software environment.

Inventive Principle:
Principle #26Copying

2Adaptability or versatility

If multiple service-providing entities are introduced to support client device operations, then service functionality increases, but system complexity increases commensurately

Engineering Contradiction:
Improveservice functionalityVSAvoidsystem management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges multiple service-providing entities into a single centralized server system. Instead of having separate entities for software downloads, account management, and data synchronization, the patent combines these services into one server that handles all functions through a unified architecture, reducing the number of interface points and simplifying system management.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The server is designed with universal functionality to provide multiple services through a single platform. It can deliver software updates, manage user accounts, synchronize data, and handle device configurations all through one system, eliminating the need for users to interact with multiple separate service entities.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS9037685B2Intelligent migration between devices having different hardware or software configuration
Publication Date: 2015.05.19 QUALCOMM INC
  • US9037685B2 patent drawing
  • US9037685B2 patent drawing
  • US9037685B2 patent drawing

AI summary

A system (and method) discloses migrating data of a first client device to a second client device. A second client device transmits configuration information of the second client device to a remote server. The remote server compares this data to data from the first client device that was previously sent to the remote server from the first client device. The remote server prepares data that is in a format that is compatible with hardware or software configuration of the second client device and that corresponds to the data from the first client device. Thereafter, the remote server transmits this data to the second client device, which uses it to initialize (e.g., restore or reinitialize) the second client device.