Session Mobility in Adaptive Bitrate Streaming
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data streaming systems require significant server memory to store user settings and session information for multiple devices, leading to high memory demands and complex database management, and necessitate proprietary software on client devices for compatibility, which complicates seamless switching between devices.
Innovation Solution
A system and method for session mobility in adaptive bitrate streaming that allows devices to transfer media stream sessions by exchanging context information and replay offsets, enabling seamless switching between devices without the need for extensive server storage or proprietary software, using manifest information to select and request media segments based on available versions and user preferences.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the server stores all user stream settings in server memory, then the user can resume streaming from the same device with settings preserved, but the server memory requirements become extremely large for users with many streams
Solution Approach 1:
The patent extracts session information storage from the server to the client device. Each client device stores its own session information locally, eliminating the need for the server to maintain large amounts of session data for multiple devices. This resolves the contradiction by preserving session continuity reliability while dramatically reducing server memory requirements.
Solution Approach 2:
The patent creates a copy of session information on the client device that mirrors what would otherwise need to be stored on the server. The client stores context information including replay offsets and segment identifiers locally, allowing the system to maintain session state without burdening server memory resources.
2Adaptability or versatility
If proprietary software is installed on client devices for compatibility with the server, then the server can manage session information centrally, but the device complexity and software installation requirements increase
Solution Approach 1:
The patent enables standard HTTP clients to perform session mobility functions without requiring proprietary software. By using universal HTTP protocols and standards-based manifest files, any HTTP-compatible device can participate in the streaming session, eliminating the need for device-specific software installations while maintaining server-client compatibility.
Solution Approach 2:
The client device autonomously manages its own session information locally without requiring complex server-side software agents on each device. The client independently stores and retrieves its session context, reducing the need for proprietary software while maintaining full functionality.
3Ease of operation
If the server stores detailed session information for seamless device switching, then the user experience improves during device transitions, but the database management complexity and memory requirements increase
Solution Approach 1:
The patent extracts session state management from the server database to individual client devices. Each device maintains its own session context locally, eliminating the need for complex server-side database operations to track and retrieve session information during device switches. This simplifies database management while enabling seamless device transitions through context information transfer.
Solution Approach 2:
The manifest file serves as an intermediary that carries session context information between devices and the server. By embedding session state in the manifest that can be transferred and referenced, the system enables smooth device switching without requiring complex database management infrastructure.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A system is provided. The system comprises a server (130), a first device (110) for receiving a first plurality of segments of a media data stream from the server (130), and a second device (120) for receiving a second plurality of segments of the media data stream from the server (130). An interface (111) of the first device (110) is configured to receive manifest information indicating, for each property of one or more properties of the media data stream, a group of two or more available versions of said property of the media data stream. A processor (112) of the first device (110) is configured to select, for each of the one or more properties, one of the two or more available versions of said property as a selected version of said property, to determine context information comprising the selected version of each of the one or more properties. The interface (111) of the first device (110; 710) is configured to request said first plurality of segments of the media data stream depending on the context information. The server (130) is configured to transmit said first plurality of segments to the first device (110). An interface (121) of the second device (120) is configured to receive the context information and information on a replay offset or on the segment being rendered last by the first device (1 10) or on the segment being received last by the first device (110), wherein the replay offset depends on a replay of the media data stream at the first device (110). A processor (122) of the second device (120) is configured to select said second plurality of segments of the media data stream depending on the context information, and depending on the replay offset or on the segment being rendered last by the first device (110) or on the segment being received last by the first device (110). The interface (121) of the second device (120) is configured to request said second plurality of segments from the server (130). The server (130) is configured to transmit said second plurality of segments to the second device (120).