Cross-Device Event Data Synchronization Without Server Aggregation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data synchronization technologies fail to maintain user privacy by aggregating user profiles on servers, and they do not effectively propagate deletions across multiple devices, leading to remnants of deleted data remaining on devices.
Innovation Solution
An adaptive, cross-device event data synchronization system that synchronizes user profiles across multiple devices without aggregating them on a server, using a transport mechanism to propagate insertion and deletion records immediately, ensuring that deleted data is removed from all devices, thus maintaining user privacy.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If user profiles are aggregated on servers for synchronization, then data synchronization across devices is achieved, but user privacy is compromised
Solution Approach 1:
The patent extracts only the necessary synchronization information (event data items with timestamps and device identifiers) from user profiles, eliminating the need to aggregate complete user profiles on servers. This allows synchronization to occur without compromising user privacy, as only minimal, anonymized data is transmitted between devices.
Solution Approach 2:
The patent introduces an intermediary mechanism using event data items as placeholders that represent user activity without containing identifiable user information. These event data items serve as mediators that enable synchronization across devices while preserving user privacy by avoiding direct server aggregation of profile data.
2Reliability
If deletion records are not propagated immediately, then device complexity is reduced, but data remnants remain on devices
Solution Approach 1:
The patent implements preliminary action by immediately propagating deletion records to all devices upon detection. When a user deletes data on one device, the system immediately generates and transmits deletion records to other devices before any potential data access or leakage can occur, ensuring complete data removal across the ecosystem.
Solution Approach 2:
The patent employs feedback mechanisms where devices continuously monitor for deletion records and automatically execute deletion operations. This feedback loop ensures that deletion actions taken on one device are immediately reflected across all connected devices, maintaining data consistency and completeness without requiring complex manual coordination.
3Ease of operation
If event data is synchronized in real-time, then user experience is enhanced, but network bandwidth consumption increases
Solution Approach 1:
The patent extracts only the essential synchronization information (event data items containing minimal metadata such as timestamps, device identifiers, and event types) from comprehensive user activity data. This selective extraction enables real-time synchronization with minimal network bandwidth consumption, as only the necessary synchronization packets are transmitted rather than complete user profile data.
Solution Approach 2:
The patent applies partial action by synchronizing only the specific event data items that have changed or been deleted, rather than synchronizing all user profile data continuously. This selective synchronization approach maintains enhanced user experience through real-time updates while significantly reducing network bandwidth consumption compared to full data synchronization.
Data Source
AI summary
A device implementing adaptive, cross-device event data synchronization includes at least one processor to maintain a database on the device, the database storing event data items derived from user data items corresponding to user activity on the device or a second device. The at least one processor periodically transmits, to a server, first insertion records corresponding to new event data items generated at the device, the transmission periodicity based on a frequency at which the new event data items are generated. The at least one processor, upon detecting deletion of one user data item, deletes, from the database, one corresponding event data item, and immediately transmits, to the server for propagation to the second device, a first deletion record for deletion of one corresponding event data item at the second device, the first deletion record being transmitted along with any of the first insertion records awaiting transmission.