Retransmission Server Fast Channel Switching Scalability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current fast channel switching methods consume resources and suffer from poor scalability due to the need for status maintenance when key information is lost during retransmission.
Innovation Solution
The method involves a retransmission server generating data units with independent sequence numbers for key information, allowing for efficient retransmission without status maintenance, using RTCP RAMS-R and RAMS-I messages to manage fast channel switching requests and responses, and utilizing RTCP NACK messages for lost data units.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the cache server performs status maintenance and determines whether the terminal is a fast channel switching terminal when receiving retransmission requests, then the retransmission accuracy is improved, but the device complexity and resource consumption increase significantly
Solution Approach 1:
The patent segments the retransmission process by introducing a dedicated fast channel switching terminal identification module that extracts terminal identification information from RTCP packets. This separates the complexity of status maintenance from the general retransmission logic, allowing the server to efficiently identify fast channel switching terminals without overhauling the entire system architecture.
Solution Approach 2:
The patent implements preliminary action by pre-establishing a fast channel switching terminal list that stores identification information of fast channel switching terminals before retransmission requests arrive. When a retransmission request is received, the server simply checks whether the terminal's identification information exists in this pre-established list, eliminating the need for complex real-time status maintenance and determination processes.
2Reliability
If the cache server maintains individual channel switching data sources for each terminal sending fast channel switching requests, then the retransmission reliability is improved, but the scalability deteriorates due to high resource consumption
Solution Approach 1:
The patent applies universality by designing a unified fast channel switching terminal list that serves multiple terminals simultaneously. Instead of maintaining separate data sources for each terminal, the server uses a single shared data structure that can efficiently handle retransmission requests from multiple fast channel switching terminals, thereby improving scalability while maintaining reliability.
Solution Approach 2:
The patent uses copying by storing only essential identification information (such as terminal IDs) in the fast channel switching terminal list rather than maintaining complete channel switching data sources for each terminal. This reduced-copy approach allows the server to verify terminal status with minimal resource consumption while still ensuring reliable retransmission to the correct terminals.
3Reliability
If the server determines data to be retransmitted by checking terminal status after receiving retransmission requests, then the retransmission accuracy is improved, but the channel switching time increases
Solution Approach 1:
The patent implements preliminary action by pre-establishing the fast channel switching terminal list and pre-organizing retransmission data according to terminal identification information before actual retransmission requests arrive. When a retransmission request is received, the server can immediately match the terminal ID with the pre-organized data, eliminating the need for time-consuming status determination processes and thus reducing channel switching time while maintaining accuracy.
Data Source
Figure 1~2
Figure 3~4
Figure 5~6
AI summary
Embodiments of the present invention disclose a method, apparatus and system for obtaining key information during fast channel switching. A fast channel switching request sent by a terminal is received; at least one data unit bearing key information is generated according to the fast channel switching request; a fast channel switching response message is sent to the terminal, where the response message carries an identifier of a first data unit bearing the key information and the number of data units bearing the key information; and the at least one data unit bearing the key information is sent to the terminal. When the key information is lost, the key information is retransmitted without a need to perform maintenance, which improves scalability of fast channel switching.