RCS Capability Discovery Group Messaging Optimization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The current Rich Communication Suite (RCS) standard experiences significant traffic issues when updating RCS capability information across a large number of user equipment (UEs), as the messaging scales linearly with the number of UEs, leading to increased network traffic and inefficiency.
Innovation Solution
A requesting UE configures a capabilities request message to request RCS capability information from a target UE and a set of other UEs, with the target UE determining if it has access to this information and responding with an updated message, and the UE performs a capability refresh operation based on age thresholds to optimize data freshness.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If the current RCS standard uses peer-to-peer SIP OPTIONS messaging for capability discovery, then each UE can obtain capability information from individual target UEs, but the network traffic scales linearly with the number of UEs, leading to increased traffic and inefficiency
Solution Approach 1:
The patent combines multiple capability discovery requests into a single group messaging operation. Instead of sending individual SIP OPTIONS messages to each target UE, the requesting UE sends one group message to a group containing multiple target UEs. The group chat server aggregates capability information from multiple UEs and returns it in a single response, reducing the number of messaging operations from N individual exchanges to 1 group exchange, thereby significantly reducing network traffic while maintaining complete capability information collection
2Reliability
If the system performs capability refresh operations frequently to maintain data freshness, then capability information remains up-to-date, but network traffic and processing overhead increase
Solution Approach 1:
The patent implements periodic capability refresh operations where UEs send group messaging operations at predetermined time intervals (e.g., every 15 minutes, hourly, or daily) to refresh capability information. This periodic approach ensures capability data remains relatively fresh while avoiding continuous or overly frequent refresh operations that would waste network resources. The system balances information freshness with resource conservation by refreshing only when necessary based on the configured periodic schedule
Data Source
Figure 1
Figure 2A
Figure 2B
AI summary
A method of operating a user equipment (UE) configured to implement a rich communication suite (RCS) protocol, comprising: obtaining RCS capability information for a target UE along with an indication of a time when the RCS capability information was validated by the target UE; determining a priority associated with the target UE; identifying an RCS capability information age threshold based on the determined priority; determining whether the time indication is older than the RCS capability information age threshold; and selectively triggering an RCS capability information refresh operation with the target UE based on whether the RCS capability information for the target UE is determined to be older than the RCS capability information age threshold.