Server-Side Adaptive Bitrate Streaming With Encoded Manifests
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing client-side adaptive bitrate streaming technologies struggle with low-latency delivery protocols due to inaccurate bandwidth estimation, as they assume immediate availability of large data segments, which is not valid for micro-burst traffic, leading to inefficient switching between bitrates.
Innovation Solution
Implementing server-side adaptive bitrate streaming with a specially-encoded manifest file that includes bitrate options and segment sizes, using client telemetry to determine bitrate switching, allowing the server to make informed decisions based on actual network conditions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If client-side bandwidth estimation is used for adaptive bitrate streaming, then the system works well for traditional HTTP streaming with large data segments, but it provides inaccurate bandwidth estimation for low-latency protocols that deliver content as micro-bursts of traffic
Solution Approach 1:
The patent inverts the traditional client-side bandwidth estimation approach by implementing server-side bandwidth estimation. Instead of the client estimating bandwidth based on download performance of large segments, the server estimates bandwidth by analyzing the actual micro-burst traffic patterns and network conditions, providing accurate measurements for low-latency protocols
Solution Approach 2:
The patent changes the estimation parameters from client-side download performance metrics to server-side network condition metrics. The server measures bandwidth based on actual micro-burst delivery characteristics, including traffic patterns, network latency, and server-to-client transmission conditions, rather than relying on client-side assumptions about large segment availability
2Loss of information
If multiple manifest files are provided (one per bitrate), then the client has complete information for client-side ABR decisions, but the device complexity and manifest management becomes more complex
Solution Approach 1:
The patent merges multiple bitrate-specific manifest files into a single unified manifest file. This single manifest contains all necessary information about available bitrates, segment characteristics, and delivery options, eliminating the need for the client to manage multiple separate manifest files while maintaining complete information for ABR decisions
Solution Approach 2:
The single manifest file serves multiple functions that previously required separate manifest files. It provides comprehensive information about all available bitrates, segment timelines, and delivery parameters, making it a universal reference that supports both traditional HTTP streaming and low-latency protocol delivery
3Ease of operation
If client-side ABR algorithms are used, then the client can adapt to network conditions, but the algorithm execution and decision-making must be performed on the client device
Solution Approach 1:
The patent inverts the ABR algorithm execution location from client-side to server-side. The server performs bandwidth estimation, segment selection, and bitrate decision-making based on actual network conditions and client telemetry data, then delivers the selected segments to the client without requiring the client to execute complex ABR algorithms
4Reliability
If traditional HTTP streaming assumptions are made (large data segments available immediately), then client-side bandwidth estimation works well, but it does not hold for low-latency protocols that deliver content as micro-bursts
Solution Approach 1:
The patent changes the fundamental delivery model parameters from large immediate segments to micro-burst delivery. The server implements bandwidth estimation and segment selection that accounts for the specific characteristics of low-latency protocol delivery, including smaller micro-burst sizes, timing constraints, and network latency variations
Solution Approach 2:
The patent segments the content delivery into micro-bursts rather than large segments, matching the low-latency protocol delivery pattern. Each micro-burst contains carefully selected segments based on server-side bandwidth estimation, allowing reliable delivery under the constrained delivery model of low-latency protocols
Data Source
AI summary
An enhanced server-side Adaptive Bitrate Streaming (ABR) of source content. The ABR switching logic is located in association with a server, and this logic also receives telemetry data as measured by the client. The client receives a single manifest that comprises a set of encoded entries each associated with a segment of the source content and comprising a first portion encoding, as a set of options, each of the multiple bitrates, and a second portion that, for each of the multiple bitrate options, encodes a size of the segment associated therewith. In operation, the client media player makes a request for a portion of the source content, and that request includes one of the encoded entries. In response, the server-side ABR switching logic determines whether to switch delivery of the source content from an existing first bitrate to a second bitrate. If so, the requested portion is delivered to the client at the second bitrate.