Multicast Session Termination Flag for Wireless Channel Release
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional wireless communication systems face inefficiencies in terminating multicast sessions, particularly for indeterminate sessions like push-to-talk, due to the inability to distinguish between final and non-final multicast messages, leading to unnecessary channel retention and increased overhead.
Innovation Solution
A server inserts a flag into the final multicast message, indicating its status, allowing communication entities to release associated channels promptly, rather than relying on inactivity timers, thereby facilitating timely channel release and improving system efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If inactivity timers are used to determine multicast session termination, then channels are retained to avoid false positives, but channel retention time increases and system efficiency decreases
Solution Approach 1:
The system performs preliminary action by inserting a termination flag into the final multicast message before transmission. This allows the communication entity to proactively identify session termination without waiting for inactivity timers to expire, thereby releasing channels promptly while avoiding false positives.
2Reliability
If inactivity timers are used to determine multicast session termination, then false positives are avoided, but overhead increases due to prolonged channel retention
Solution Approach 1:
The invention extracts the termination indication from the timing mechanism and embeds it directly into the multicast message as a flag. This separates the termination detection function from the channel retention mechanism, allowing accurate detection without the overhead of prolonged channel retention.
3Productivity
If channels are released promptly upon receiving final multicast messages, then bandwidth utilization improves, but the system must reliably distinguish final messages from non-final messages
Solution Approach 1:
The system uses a termination flag as a distinctive marker (analogous to a color change) in the final multicast message. This flag provides a clear, unambiguous signal that distinguishes final messages from non-final messages, enabling reliable identification and prompt channel release with high accuracy.
Data Source
AI summary
A wireless communication system and methods thereof are disclosed. A server (e.g., a push-to-talk (PTT) server) determines a multicast message to be a final multicast message for a multicast session having an indeterminate end time. The server inserts a flag into the multicast message, the inserted flag indicating that the flagged multicast message is a final multicast message for the multicast session. The server sends the flagged multicast message to a communication entity (e.g., a radio access network (RAN), a broadcast serving node (BSN), etc.) supporting the multicast session. The communication entity (e.g., RAN, BSN, etc.) receives the multicast message from the server. The communication entity determines whether the received multicast message includes a flag relating to multicast session termination. The communication entity releases at least one channel associated with the multicast session based on the determining step.