Application Gateway Device Swap Registration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems for replacing wireless devices fail to efficiently transfer user applications and their associated registration information, requiring re-installation and re-registration, which is time-consuming and inconvenient for users.

Innovation Solution

A method and system that automatically registers applications with an application gateway during device transfer by backing up and restoring application data and registration information, using an application gateway to maintain a registration list and update it with new device information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If current backup/restore systems are used to transfer application data, then application data can be transferred from old device to new device, but user applications and application registration information cannot be saved and restored, requiring re-installation and re-registration

Engineering Contradiction:
Improveapplication registration informationVSAvoidtime for re-installation and re-registration
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The system performs preliminary actions by backing up not only application data but also application binaries and registration information before device replacement. This preparation ensures that when the new device is activated, all necessary components are already prepared for immediate restoration, eliminating the need for re-installation and re-registration operations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates complete copies of the application environment including application binaries, data, and registration information from the old device. These copies are transferred and restored to the new device, providing an exact replica of the original application environment without requiring manual re-installation or re-registration processes.

Inventive Principle:
Principle #26Copying

2Ease of operation

If application data is transferred without application binaries and registration information, then transfer process is simpler, but all user-installed applications must be re-installed onto the new device

Engineering Contradiction:
Improvesimplicity of transfer processVSAvoidspeed of application restoration
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The system merges multiple transfer components (application binaries, application data, and registration information) into a single comprehensive backup and restoration process. This unified approach maintains operational simplicity while simultaneously restoring all application elements in one process, eliminating the need for separate re-installation steps.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system performs preliminary actions by collecting and packaging application binaries, data, and registration information together before transfer. This pre-packaging ensures that when restoration occurs, all necessary components are available and can be deployed simultaneously, maximizing restoration speed without complicating the user interface.

Inventive Principle:
Principle #10Preliminary action

3Loss of information

If some systems allow backup of user-installed applications, then applications can be transferred, but applications need to be re-registered with the application mediating service, requiring user or IT administrator intervention

Engineering Contradiction:
Improveapplication registration informationVSAvoiduser intervention required for re-registration
Core Design Contradiction:
Loss of informationVSExtent of automation

Solution Approach 1:

The system implements self-service by automatically handling the re-registration of applications with the mediating service. The restoration process includes automatic detection of the new device identity and autonomous update of registration information in the mediating service, eliminating the need for user or administrator intervention in the re-registration process.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system uses the mediating service as an intermediary to automatically manage application registration. During restoration, the system communicates with the mediating service to update registration records with the new device identity, allowing the intermediary to handle the complex re-registration logic automatically without requiring direct user involvement.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If complete application environment is backed up and restored, then seamless device replacement is achieved, but system complexity increases

Engineering Contradiction:
Improveseamlessness of device replacementVSAvoidcomplexity of backup and restore system
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system achieves universality by creating a multi-functional backup and restoration platform that handles application binaries, application data, registration information, and mediating service updates through a single unified process. This universal approach ensures reliable seamless device replacement while managing complexity through standardized procedures applicable to all application types.

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

Data Source

PatentUSRE44836E1System and method for efficient transfer of applications and data during device swap
Publication Date: 2014.04.08 MALIKIE INNOVATIONS LTD
  • USRE44836E1 patent drawing
  • USRE44836E1 patent drawing
  • USRE44836E1 patent drawing

AI summary

A method for automatically registering the runtime environment and related component applications with an application gateway when transferring the applications from a first wireless device to a second wireless device is provided. Applications installed on the first wireless device are registered with an application gateway, which maintains a registration list of identification information for all registered wireless devices and applications installed thereon. A back-up is created of the applications and registration information for the runtime environment installed on the first wireless device for transfer to a second wireless device. An application container of the second wireless device determining installation and communicating to the application gateway identification information regarding the second wireless device and the restored applications. The application gateway registers the second wireless device by updating the registration list with the identification information for the second wireless device and the applications installed thereon.