Messaging App Sync via Shared Database
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The inefficiency in synchronizing rich media content between a user device and a server in social networks leads to wasted processing resources and network bandwidth, as the server sends duplicate messages that have already been delivered through push notifications, causing delays in presenting the latest chat messages to users.
Innovation Solution
A system that uses a shared synchronization database to identify differences between the user device and the server, only transmitting content that has not been sent to third-party applications, allowing the messaging application to update its state and request missing content from the server, thereby reducing duplicative work.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the server sends all messages to the user device through traditional synchronization, then the user receives complete message content, but network bandwidth is wasted and processing time increases due to duplicate transmissions
Solution Approach 1:
The patent extracts and separates push notification messages from the main synchronization process. The system identifies which messages have already been delivered via push notifications and excludes them from the synchronization data set, transmitting only the remaining messages that need full delivery. This extraction eliminates redundant network transmissions while ensuring complete message delivery.
Solution Approach 2:
The system performs preliminary action by delivering push notifications before the main synchronization process. This preliminary delivery allows the system to identify which messages have already reached the user device, so that subsequent synchronization can skip these messages and only transmit new or missing content, reducing overall bandwidth consumption.
2Reliability
If the server sends all messages through traditional synchronization, then message delivery is complete, but processing time increases due to duplicative work
Solution Approach 1:
The patent extracts push notification message identifiers from the synchronization process and creates a filtered set of messages that need actual transmission. By removing already-delivered messages from the synchronization data set, the system reduces processing time while maintaining complete message delivery reliability.
Solution Approach 2:
The system performs preliminary action by delivering push notifications before synchronization occurs. This allows the system to identify and exclude already-delivered messages from the synchronization process, eliminating duplicative processing work and reducing overall message handling time while ensuring no messages are lost.
3Loss of information
If the system transmits all message content during synchronization, then all users receive complete information, but network bandwidth is wasted on messages already delivered via push notifications
Solution Approach 1:
The patent extracts and removes message identifiers that have already been delivered via push notifications from the synchronization data set. This extraction ensures that only messages needing actual transmission are included, preventing bandwidth waste on duplicate deliveries while maintaining complete information delivery for all users.
Solution Approach 2:
The system performs preliminary push notification delivery to inform users of message arrival before full synchronization occurs. This preliminary action enables the system to identify which messages have already been delivered and exclude them from bandwidth-intensive synchronization transmissions, optimizing network resource usage while ensuring complete information delivery.
Data Source
AI summary
Systems and methods are provided for synchronizing messages. The systems and methods include operations for: identifying a difference between a current state of a messaging application and a shared synchronization database, wherein the shared synchronization database is updated via a third-party application in response to the third-party application receiving, from a server, a notification related to the messaging application, the messaging application and the third-party application being implemented on a client device; retrieving information from the shared synchronization database to update the current state of the messaging application based on the identified difference; and transmitting, to the server by the messaging application, a request for content based on the update to the current state of the messaging application.