Message Synchronization Across Multiple Terminals
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional message service systems only allow for limited message synchronization across multiple mobile terminals registered under a single user account, primarily focusing on retrieving messages from a database server and do not effectively manage message sharing among multiple devices in a multi-device environment.
Innovation Solution
A method and system for synchronizing messages across multiple terminals by using a server with a communication module, storing unit, and controller to manage user accounts and terminal information, enabling message notification and delivery even when terminals are not connected to the server, and equipping terminals with communication and control modules to receive and display messages.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional message sync retrieves messages from database server only when terminal is connected, then message delivery is simple, but messages cannot be delivered to terminals that are not connected to the server
Solution Approach 1:
The system performs preliminary actions by storing message notification information in the database server before the terminal is connected. When a terminal is offline, the server saves the notification data (message ID, sender ID, timestamp) in advance. Once the terminal connects, it retrieves and processes these pre-stored notifications, ensuring no messages are lost during offline periods.
Solution Approach 2:
The database server acts as an intermediary between the sending terminal and the receiving terminal. It stores both the actual message content and notification information, mediating the delivery process. When terminals are offline, the server holds the messages and generates notifications; when terminals come online, the server delivers both messages and notifications, ensuring reliable communication regardless of connection status.
2Reliability
If message notification is sent to all receiving terminals, then all terminals receive messages, but energy is wasted notifying terminals that cannot receive messages
Solution Approach 1:
The system applies local quality by differentiating notification strategies based on terminal connection status. For online terminals, immediate push notifications are sent. For offline terminals, notification information is stored in the database without active notification attempts. This localized approach ensures complete message synchronization while avoiding energy waste on terminals that cannot receive notifications.
Solution Approach 2:
The system performs partial notification actions by only notifying terminals that are currently online or can be reached. Instead of universally notifying all terminals regardless of status, the server selectively sends notifications only to capable terminals, reducing energy consumption while maintaining synchronization completeness for accessible devices.
3Adaptability or versatility
If multiple terminals are mapped to one user account, then message sharing among devices is enabled, but managing message sync across all terminals becomes complex
Solution Approach 1:
The system segments message management by creating separate notification records for each terminal associated with a user account. The database stores terminal-specific notification information including terminal IDs, allowing independent tracking and management of message status for each device. This segmentation simplifies multi-terminal management by treating each terminal's message state independently rather than managing all terminals as a single complex unit.
Solution Approach 2:
The database server provides universal functionality by serving as a centralized message repository and notification manager for all terminals mapped to a user account. It handles message storage, notification generation, and delivery coordination for multiple devices through a single unified system, reducing overall complexity despite supporting multiple terminals.
4Ease of operation
If message notification includes full message content, then user can see message details, but network bandwidth and data transmission increase
Solution Approach 1:
The system extracts only the essential notification elements (message ID, sender ID, timestamp, and a brief preview) from the full message content. The database stores complete message content separately, while notification records contain only the extracted key elements needed to inform users of new messages. Users can view full content by accessing the message through the notification, minimizing data transmission while maintaining ease of operation.
Solution Approach 2:
The system applies partial action by transmitting only partial message information in notifications rather than complete content. Notification records include selective elements (ID, sender, timestamp, preview) sufficient for user awareness, while full content remains in the database. This partial transmission reduces network bandwidth usage and energy consumption while still providing adequate message visibility to users.
Data Source
AI summary
Provided is a method for synchronizing messages among a plurality of terminals, including receiving a communication message from a first sending terminal, sending a message notifying reception of the communication message to a first receiving terminal that is not connected to a server among receiving terminals mapped to a receiving account of the communication message, and sending the communication message to the first receiving terminal, if the first receiving terminal is connected to the server.