Asynchronous Message Recovery Through Retry Database and Editing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Errors in asynchronous message delivery systems prevent messages from being delivered to their intended destinations, leading to operational inefficiencies and incorrect processing by recipient systems, particularly in scenarios where the destination is unreachable or the message is malformed.
Innovation Solution
A message error recovery system that identifies undeliverable messages, adds them to a retry database, and sends edited or original messages back to the delivery system once the error is resolved, using a user interface for editing and retry instructions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a delivery system attempts to deliver asynchronous messages a predefined number of times or for a predefined length of time, then the delivery system can handle temporary network issues or offline destinations, but messages with formatting errors or permanently unreachable destinations will remain undelivered and cause operational issues
Solution Approach 1:
The patent introduces a retry system as an intermediary component between the message source and the message destination. This retry system captures undelivered messages from the delivery system, stores them in a retry database, and re-attempts delivery after error resolution. The intermediary retry system prevents message loss by maintaining a persistent record of failed messages and enabling their re-delivery once the underlying errors are corrected.
Solution Approach 2:
The patent implements preliminary error detection and message capture before final delivery failure occurs. The retry system proactively identifies messages that failed delivery and stores them in advance, allowing for error correction and retry before the messages are permanently lost. This preliminary action prevents the complete loss of message information by preparing retry capability ahead of time.
2Productivity
If the delivery system performs multiple delivery attempts during a prolonged period, then temporary network errors can be recovered from, but messages with persistent errors continue to fail and cause system inefficiencies
Solution Approach 1:
The patent extracts failed messages from the main delivery system and places them into a separate retry database. This extraction removes the burden of handling persistent delivery failures from the primary delivery system, allowing it to focus on successful deliveries and maintain high throughput. The retry system separately handles failed messages, preventing them from blocking or slowing down the main delivery operations.
Solution Approach 2:
The patent segments the message delivery process into two distinct parts: the primary delivery system that handles successful deliveries and maintains high throughput, and the retry system that handles failed deliveries and improves reliability. This segmentation allows each subsystem to be optimized for its specific function without compromising the other.
3Productivity
If asynchronous messages are sent without waiting for confirmation, then elements can operate independently and efficiently, but there is no way to know if the message was received or processed correctly
Solution Approach 1:
The patent implements a feedback mechanism through the retry system that provides indirect confirmation of message delivery status. When messages are successfully delivered to the destination, the delivery system updates its records, and the retry system can detect successful deliveries by checking if messages remain in the retry database. This feedback loop allows sending elements to eventually determine whether their asynchronous messages were received and processed, while maintaining asynchronous operation efficiency.
Data Source
AI summary
An error may prevent a message delivery system from delivering an asynchronous message to a destination, for instance if the message contains an error or the destination is unreachable. When an error prevents the message delivery system from delivering an asynchronous message, a separate message error recovery system may add the message to a retry database. If the message contained the error, the message error recovery system may edit the message to correct the error, for instance based on input received via a user interface. When the error has been resolved, for instance via the editing of the message or because the destination has become reachable, the message error recovery system may send the original or edited message back to the message delivery system as a retry message. Due to the resolution of the error, the message delivery system may succeed in delivering the retry message to the destination.