Application Server Notification for RCS Message Delivery Failure
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing message retransmission methods in RCS (Rich Communication Suite) systems suffer from duplication of messages, increased latency, and desequencing issues due to the current fallback mechanism, which involves waiting for a configurable timeout before retransmitting messages via SMS when the recipient is unreachable.
Innovation Solution
A method and device that notify the sender of undelivered messages by transmitting a notification message with the message identifier and delivery status, allowing immediate fallback to SMS transmission without waiting for a timeout, and providing a mechanism to cancel stored messages to prevent duplication upon recipient availability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the current fallback mechanism waits for a configurable timeout before retransmitting messages via SMS, then the system maintains stability and avoids premature retransmission, but message delivery latency increases and interactivity is degraded
Solution Approach 1:
The application server sends a notification message to the sender terminal when the recipient terminal becomes unreachable. This feedback mechanism allows the sender to immediately know about the delivery failure and trigger retransmission without waiting for the timeout period, thus reducing latency while maintaining reliability through server-confirmed unreachability detection.
Solution Approach 2:
The system performs preliminary detection of recipient unreachability by the application server before the timeout expires. By detecting unreachability early and notifying the sender, the system enables preliminary retransmission action without waiting for the full timeout period, reducing overall delivery latency while ensuring the recipient is truly unreachable before switching protocols.
2Reliability
If messages are retransmitted via SMS when recipient is unreachable, then message distribution is guaranteed, but message duplication occurs and network load increases
Solution Approach 1:
The sender terminal receives a notification from the application server confirming that the recipient is unreachable. Based on this feedback, the sender makes an informed decision to retransmit via SMS only when necessary, avoiding duplicate transmissions. The sender can also send a cancellation message to prevent retransmission if alternative delivery methods succeed, reducing unnecessary network load.
Solution Approach 2:
The system allows the sender to cancel stored messages that are waiting for retransmission. When the sender receives confirmation that the recipient is unreachable, they can choose to discard the stored message or cancel the retransmission request, preventing duplicate message delivery and reducing network load when alternative delivery succeeds.
3Reliability
If a configurable timeout interval is used before retransmission, then the system avoids premature fallback to SMS, but the interactivity of conversation is degraded
Solution Approach 1:
The application server provides real-time feedback to the sender terminal about recipient unreachability status. This immediate feedback eliminates the need for the sender to wait through the timeout interval, maintaining conversation interactivity while ensuring reliable detection of actual unreachability conditions before triggering SMS fallback.
Data Source
AI summary
A method of notification by an application server of an inability to deliver a message sent by a first terminal destined for a second terminal. The message is transmitted from the first terminal to the second terminal by way of the application server. The application server is configured to store at least one message with a view to a subsequent retransmission when the recipient is not reachable. The method includes: obtaining a message intended for the second terminal, detecting that the second terminal is not reachable, determining an identifier of the sender of the message obtained and of the identifier of the message obtained, and transmitting a notification message to the sender of the message. The message includes at least the identifier of the message obtained and an indication according to which the message obtained has not been delivered.