Partial Mobile Device Reset Preserving User Data
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
When switching between telecommunications providers, mobile devices typically require a full reset to factory default settings, leading to the loss of user data and applications, which is inconvenient for users and burdensome for providers, as reusable data such as identification numbers and configuration settings are deleted, necessitating reinstallation.
Innovation Solution
A method and system for partially resetting a mobile device by receiving a software payload, parsing it into nodes, accessing and modifying specific files to preserve reusable data while resetting others to factory defaults, allowing the device to switch providers without losing user information or applications, using a multi-step process involving an acquisition engine, parsing engine, and execution engine.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a full reset to factory default settings is performed when switching providers, then the device is properly reconfigured for the new provider, but user data and applications are lost
Solution Approach 1:
The patent segments the device configuration into multiple categories: provider-specific configuration data (resetted), user data (preserved), and application data (preserved). This segmentation allows selective resetting of only the necessary provider-specific files while maintaining user and application data, thereby resolving the contradiction between proper reconfiguration and data preservation
Solution Approach 2:
The patent applies local quality by treating different files and data types differently during the reset process. Specifically, provider-specific configuration files are reset to factory defaults, while user data directories and application data are selectively preserved. This localized differentiation resolves the contradiction by applying the reset operation only where necessary rather than globally
2Adaptability or versatility
If a full reset to factory default settings is performed when switching providers, then the device is properly reconfigured for the new provider, but the process becomes time-consuming and burdensome
Solution Approach 1:
The patent performs preliminary actions by identifying and preserving user data and application data before the reset process begins. The system pre-determines which files should be kept and creates a preservation plan, allowing the reset to proceed quickly without requiring post-reset data restoration. This eliminates the time-consuming reinstallation process while maintaining proper provider reconfiguration
Solution Approach 2:
By segmenting the reset process into selective operations on different file types, the patent avoids the time-consuming full reset. Only provider-specific configuration files are reset, while user and application data are preserved in place, dramatically reducing the time required for provider switching while maintaining reconfiguration capability
3Adaptability or versatility
If provider-specific configuration data is reset, then the device can be properly activated on a new provider, but reusable data such as identification numbers and settings are lost
Solution Approach 1:
The patent applies local quality by precisely targeting only the provider-specific configuration files for resetting, while leaving reusable data such as identification numbers and user settings intact. This selective approach allows proper provider activation while preserving reusable data that is not provider-specific
Solution Approach 2:
The patent extracts and separates provider-specific configuration data from reusable user data and application data. By extracting only the necessary provider-specific files for resetting while leaving other data untouched, the system enables proper provider activation without losing reusable data
Data Source
AI summary
A mobile communications device. The device comprises a memory, a processor; and an application stored in the memory that, when executed by the processor, receives a software payload from a provider, parses the software payload into nodes, accesses the first set of files according to a first set of nodes, changes at least one value within the first set of files, accesses the second set of files according to a second set of nodes, and reconfigures the second set of files, without altering the first set of files.