Adaptive Message Format Switching for RCS Transmission Failures
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing Rich Communications Suite (RCS) message transmission methods, particularly in versions 5.x, face limitations in determining message transmission formats and suffer from conversion failures due to differences in supported file types and sizes between RCS and legacy SMS/MMS formats, leading to incomplete message delivery and error handling issues.
Innovation Solution
An electronic device autonomously determines the message transmission format based on its own RCS capability and converts RCS messages to legacy formats like SMS or MMS when necessary, ensuring message delivery by extracting and reprocessing content to comply with legacy protocol constraints, and providing user interfaces for error handling and resending options.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the transmitting-side electronic device transmits RCS format messages, then message transmission capability is improved, but conversion failure occurs when the receiving device does not support RCS
Solution Approach 1:
The transmitting device dynamically determines the message format based on real-time capability detection of the receiving device. The system switches between RCS format and legacy format (SMS/MMS) depending on whether the receiving device supports RCS, making the transmission format adaptable rather than fixed.
Solution Approach 2:
The transmitting device performs preliminary capability detection by sending a capability inquiry message to the receiving device before actual message transmission. This advance detection allows the system to pre-determine the appropriate message format, preventing conversion failures during transmission.
2Adaptability or versatility
If the server converts RCS messages to legacy formats using IWF, then compatibility with non-RCS devices is improved, but conversion failures occur due to file size and type limitations
Solution Approach 1:
The transmitting device performs preliminary capability detection by sending a capability inquiry message to the receiving device before actual message transmission. This advance detection allows the system to pre-determine the appropriate message format, preventing conversion failures during transmission.
Solution Approach 2:
The system introduces a capability inquiry message as an intermediary communication step between the transmitting and receiving devices. This intermediary mechanism enables both devices to exchange capability information before actual message transmission, allowing the transmitting device to adapt its message format accordingly.
3Device complexity
If the transmitting device depends on server-provided information for transmission format, then device complexity is reduced, but transmission reliability deteriorates due to lack of autonomous error handling
Solution Approach 1:
The transmitting device autonomously performs capability detection and message format determination without relying on the server for transmission format decisions. The device serves itself by independently assessing the receiving device's capabilities and selecting the appropriate message format, thereby gaining autonomous error handling capability.
Solution Approach 2:
The system implements a feedback mechanism where the transmitting device sends capability inquiry messages to the receiving device and uses the received capability information to determine the appropriate message format. This feedback loop enables autonomous adaptation to the receiving device's capabilities.
Data Source
Figure 1A
Figure 1B
Figure 2
AI summary
An electronic device comprising: a communication module; a memory; at least one processor operatively coupled to the memory, configured to: display, on the display, a user interface of a messaging application; detect an input indicating a destination telephone number; transmit, via the communication module, a first message comprising a first content by using the destination telephone number and a first protocol; receive, via the communication module, an error message indicating a transmission failure of the first message; and transmit, via the communication module, a second message comprising a second content at least a part of which is the same as the first content, by using the destination telephone number and a second protocol that is different from the first protocol.