Selective Data Replication for Mobile Device Storage Optimization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for synchronizing data between network servers and mobile devices often replicate excessive data, overwhelming mobile device storage capacity and slowing application performance, as they fail to efficiently limit data replication to only what is necessary for device operation.
Innovation Solution
A method that associates user roles with data distribution rules, enabling or disabling rules based on device type and user authorization, and applying static or dynamic conditions to selectively replicate data, ensuring only relevant data is transferred, tailored to the mobile device's capacity and user circumstances.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If all data stored on the network server is replicated to the mobile device, then data completeness is improved, but storage capacity requirements and synchronization time increase significantly
Solution Approach 1:
The patent segments data into different types (e.g., calendar items, contacts, emails, attachments) and applies different replication rules to each type. Users can selectively enable or disable replication for specific data types based on their needs and device capacity, rather than replicating all data uniformly.
Solution Approach 2:
The patent enables users to customize replication rules according to local needs and device characteristics. Different users can have different replication configurations tailored to their specific requirements and mobile device storage capacities, allowing optimal data selection for each local context.
2Loss of information
If all data stored on the network server is replicated to the mobile device, then data completeness is improved, but synchronization time increases significantly
Solution Approach 1:
The patent segments data into different types and applies different replication rules to each type. Users can selectively enable or disable replication for specific data types, reducing the total amount of data transferred and synchronization time while maintaining necessary data completeness.
Solution Approach 2:
The patent implements partial replication by allowing users to select only the data types and specific data items that are necessary for mobile device operation, rather than replicating all data. This partial action approach reduces synchronization time while maintaining adequate data completeness for mobile use.
3Loss of information
If more data is replicated to the mobile device, then data availability is improved, but application performance deteriorates due to insufficient free memory
Solution Approach 1:
The patent enables users to customize replication rules according to local needs and device characteristics. Users can configure data replication based on their specific application requirements and device storage capacity, optimizing the balance between data availability and application performance for each local context.
Solution Approach 2:
The patent implements partial replication by allowing users to select only the data types and specific data items that are necessary for mobile device operation. This approach ensures adequate data availability for applications while preserving sufficient free memory to maintain optimal application performance.
Data Source
AI summary
Selectively replicating data from a network server to a mobile device during a synchronization is provided. The system and method of the invention associates mobile device users with roles that include rules. Each of the rules includes one or more conditions that can be either static or dynamic. When a rule is invoked, only those specific instances of data that satisfy the conditions of the rule are replicated to the mobile device. Whether a rule of a role is invoked can be made to depend on a device type of the mobile device. The method can also exclude data from replication where the user lacks an authorization to access a particular data type, even though a valid rule would otherwise permit the data to be synchronized.