Data Synchronization by Data Type for Timely and Stable Transfer
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data synchronization methods in distributed communication systems face challenges in ensuring both timeliness and stability, particularly in device-to-cloud and device-to-device synchronization modes, affecting user experience.
Innovation Solution
The method involves separately synchronizing procedural and persistent data based on their data types, using device-to-device synchronization for procedural data and device-to-cloud synchronization for persistent data, with adaptive switching based on network conditions and data requirements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If device-to-cloud synchronization mode is used for all data, then data stability is improved, but data synchronization timeliness deteriorates
Solution Approach 1:
The patent segments data into two categories: procedural data (not saved to storage module) and persistent data (saved to storage module). Different synchronization modes are applied to each type: device-to-device synchronization for procedural data to ensure timeliness, and device-to-cloud synchronization for persistent data to ensure stability. This segmentation resolves the contradiction by matching synchronization strategies to data characteristics.
2Loss of time
If device-to-device synchronization is used for all data, then data synchronization timeliness is improved, but data synchronization stability deteriorates
Solution Approach 1:
The patent divides data into procedural data and persistent data, applying device-to-device synchronization only to procedural data where timeliness is critical. For persistent data, device-to-cloud synchronization is used to ensure stability. This selective application resolves the contradiction between timeliness and stability.
3Device complexity
If a single synchronization mode is used for all data types, then system complexity is reduced, but data synchronization adaptability deteriorates
Solution Approach 1:
The patent applies different synchronization qualities to different data types: device-to-device synchronization for procedural data and device-to-cloud synchronization for persistent data. This local differentiation of synchronization strategies enhances adaptability to different data requirements while maintaining manageable system complexity through clear classification rules.
Data Source
Figure 1~2
Figure 3
Figure 4
AI summary
This application provides a data synchronization method and system, and an electronic device, and relates to the field of terminal technologies. In this application, after generating to-be-synchronized data, the electronic device separately synchronizes procedural data and persistent data based on a data type of the to-be-synchronized data. Therefore, stability of data synchronization is ensured while ensuring timeliness of data synchronization. The method includes: in a process of displaying an interface of a first application, a first electronic device receives a first operation of a user for the first application, and obtains first data and second data that are of the first application and that are generated based on the first operation. The first data is data that is not saved to a storage module of the first electronic device, and the second data is data that has been saved to the storage module of the first electronic device. The first electronic device sends the first data to a second electronic device, and sends the second data to a cloud server.