Media Channel Management via Transparent Session Setup
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current media session management in unicast-based communications systems is inefficient, leading to long channel switching times due to the need for extensive signaling and new session setups when switching between media channels.
Innovation Solution
A method involving a user terminal and media server that allows for seamless channel switching by using a generic, channel-transparent session setup procedure and RTSP PLAY requests with unique media content resource identifiers, enabling channel switching within an ongoing session without requiring a new session setup, thus reducing round trips and processing delays.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a new RTSP session is started for each channel switch, then the user can select different media channels, but the channel switching time increases significantly due to repeated session setup and buffering
Solution Approach 1:
The patent applies preliminary action by establishing a single RTSP session and buffering media content in advance before the user actually needs to switch channels. The media player pre-loads and buffers content from the selected channel, so when channel switching is requested, the new channel content is already prepared or can be quickly retrieved, eliminating the need for repeated session setup and extensive buffering during channel changes.
Solution Approach 2:
The patent maintains continuity of useful action by keeping the RTSP session alive and continuously buffering media content rather than terminating and restarting sessions. The media player maintains an ongoing buffering process that can be quickly redirected to new channels, ensuring that the streaming action continues without interruption or repeated setup delays.
2Adaptability or versatility
If traditional browser-based channel selection is used, then users can access multiple channels, but the process requires extensive signaling and results in delays of around ten seconds per channel switch
Solution Approach 1:
The patent extracts the channel selection functionality from the browser-based interface and implements it directly within the media player application. By taking out the channel switching logic from the browser and embedding it in the media player, the system eliminates the need for repeated browser interactions, SDP file downloads, and extensive signaling protocols, thereby dramatically reducing channel switching time while maintaining multi-channel access capability.
3Speed
If a generic session setup procedure is used without channel-specific information, then the session can be established quickly, but the media server cannot identify and deliver the correct channel content
Solution Approach 1:
The patent applies preliminary action by including channel identification information (such as URI or other identifiers) in the initial RTSP session setup request. This allows the media server to identify and prepare the correct channel content in advance, so when the user requests channel switching, the server can quickly retrieve and deliver the appropriate content without needing additional signaling or information exchange.
Data Source
Figure 1A
Figure 1B
Figure 2~8
AI summary
The media session management of the invention encompasses a media server (200) having access to multiple unicast-based media channels and a user terminal (100). The user terminal (100) generates and transmits a generic, channel-transparent session request to the server (200). This request initiates a generic, channel-transparent media session setup procedure between the terminal (100) and the server (200). The setup procedure involves exchange of requests and responses but no media channel is yet selected or notified at the server (200). Once the channel-transparent setup has been completed, the user terminal (100) transmits a channel-specific rendering request for a desired media channel to the server (200). In a subsequent channel switch, the terminal (100) simply transmits a new channel-specific request for a new channel to the server (200) during the ongoing session and reusing the negotiated transport parameters of the channel-transparent setup procedure.