Message Store Expiration Control by Recipient Connection State
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing messaging systems fail to effectively manage messages sent in error by allowing recipients to read them before recall requests are processed, leading to incomplete recall functionalities.
Innovation Solution
Implementing a message expiration status based on the connection state of the recipient terminal to the messaging server, allowing for rules to manage message deletion or expiration, including timeouts and recipient terminal actions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the messaging server deletes a message immediately upon receiving a recall request, then the message can be removed from the server, but the recipient may have already read the message before the deletion occurs
Solution Approach 1:
The system checks the recipient's connection status before delivering the message. By performing this check in advance, the message can be prevented from being delivered to an unconnected recipient, or an expiration status can be assigned, thereby ensuring recall effectiveness without requiring immediate deletion after the fact.
Solution Approach 2:
The message status is made dynamic based on the recipient's connection state. Messages can transition between different statuses (delivered, expiring, expired) depending on whether the recipient is connected, allowing flexible management that adapts to real-time conditions rather than following a fixed deletion timeline.
2Ease of operation
If the messaging server waits for a timeout period before deleting the message, then the recipient has time to read the message, but the message remains on the server longer than necessary if the recipient never connects
Solution Approach 1:
The system performs a preliminary check of the recipient's connection status before completing message delivery. This early detection allows the server to assign an expiration status or delete the message immediately, avoiding unnecessary storage time while still allowing access when appropriate.
Solution Approach 2:
Messages are treated as short-lived objects that should be retained only as long as necessary. By using connection status checks, the system ensures messages are kept only when recipients can actually access them, and are promptly removed when recipients are unconnected, optimizing server storage utilization.
3Reliability
If the messaging server implements connection status checking and message expiration management, then message recall and expiration can be effectively managed, but the system complexity increases
Solution Approach 1:
The system implements feedback mechanisms by continuously monitoring recipient connection status and using this information to dynamically adjust message delivery and expiration behavior. This feedback loop enables effective expiration management without requiring overly complex manual intervention systems.
Solution Approach 2:
The messaging server automatically manages message expiration by checking connection status and applying appropriate actions without requiring manual intervention. This self-service approach handles the complexity internally while presenting a simple interface to users, effectively managing expiration through automated processes.
Data Source
Figure 1~2
Figure 3~5
AI summary
The present invention relates to a method for managing a message store transmitted via a communication network. The method is implemented by a messaging server, and comprises the following steps: upon receiving a command for the expiry of a message intended for being received by a destination terminal of said message, detecting whether or not the terminal is connected to the messaging server (T4), and according to said detection, optionally assigning an expiring message status (S3) to said message.