Synchronization Protocol Capability Caching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing data synchronization processes, particularly in SyncML, are inefficient due to the frequent and time-consuming device capability negotiation process, which is unnecessary when device capabilities have not changed, and this inefficiency affects the synchronization efficiency and modifies the data synchronization specification frequently.
Innovation Solution
Implement a method where device capability negotiation is skipped if the capability has not changed since the last negotiation, by storing the negotiated device capability or status ID, allowing for independent device capability negotiation and direct synchronization operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If device capability negotiation is performed in every synchronization initialization, then device capability information is ensured to be up-to-date, but synchronization time is increased and synchronization efficiency is reduced
Solution Approach 1:
The patent performs device capability negotiation in advance during initialization, then stores the negotiated capability information for subsequent reuse. This preliminary action eliminates the need for repeated negotiations during regular synchronization operations, thereby reducing synchronization time while maintaining capability information accuracy.
Solution Approach 2:
The patent creates and stores copies of negotiated device capability information in a cache or storage mechanism. These cached copies are reused in subsequent synchronization operations instead of re-negotiating, significantly reducing the time required for regular synchronizations while ensuring capability information remains accurate for unchanged devices.
2Adaptability or versatility
If device capability negotiation is performed frequently, then synchronization protocol completeness is maintained, but synchronization procedure changes frequently requiring specification modifications
Solution Approach 1:
The patent performs device capability negotiation once in advance during initialization, establishing a complete synchronization protocol. The negotiated capability information is then cached and reused, preventing frequent changes to synchronization procedures and reducing the need for specification modifications while maintaining protocol completeness.
Solution Approach 2:
The patent caches copies of negotiated device capability information and uses these copies in subsequent synchronization operations. This approach maintains protocol completeness by preserving the originally negotiated capabilities while avoiding frequent procedure changes and specification modifications.
3Productivity
If device capability negotiation is skipped, then synchronization efficiency is improved, but device capability information may become outdated
Solution Approach 1:
The patent performs device capability negotiation in advance during initialization, storing the results in a cache. This preliminary negotiation provides accurate capability information that can be reused in subsequent operations, improving synchronization efficiency while maintaining information accuracy as long as device capabilities remain unchanged.
Solution Approach 2:
The patent creates cached copies of device capability information from the initial negotiation and reuses these copies in subsequent synchronization operations. This approach improves efficiency by avoiding repeated negotiations while maintaining accuracy through the use of stored capability information, provided device capabilities have not changed.
Data Source
AI summary
Method for device capability negotiation, and method, system and device for synchronization. The synchronization system includes a synchronization server and a synchronization client. The synchronization server or the synchronization client is adapted to skip the device capability negotiation and directly perform a synchronization with the synchronization server and the synchronization client when the negotiated device capability or status ID, or the status ID indicating that the device capability has not been changed and has been stored. The method for device capability negotiation includes receiving an operation request carrying a parameter requesting a device capability negotiation; determining that the session is a device capability negotiation session according to the parameter requesting the device capability negotiation, carried by the request; returning a response and performing the device capability negotiation; storing results of the device capability negotiation. Embodiments of the present invention can improve the synchronization efficiency.