HTTP Buffer Status Update via Protocol Field Analysis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for determining buffer events in audio and video applications over IP networks, such as seek, pause, and stream switch, are difficult to implement in real-time, especially when data is encrypted or with mass users, as they rely on parsing media files and presentation time stamps, which is challenging and not feasible in all scenarios.
Innovation Solution
An HTTP Protocol-based buffer status updating method that analyzes only the HTTP Protocol field to determine buffer events and update buffer status, triggering events like pause, seek, resume, and stream switch based on HTTP requests, thereby setting buffer states to normal play, play paused, re-buffering, or stream switch states.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If media files are parsed to obtain PTS for determining buffer events, then buffer status can be updated, but real-time implementation becomes extremely difficult or impossible in cases of encrypted data or mass users
Solution Approach 1:
The patent extracts the essential buffer event determination logic from complex media file parsing operations. Instead of parsing entire media files to obtain PTS, the system extracts only the necessary HTTP request field information (such as range headers, timestamp parameters) to trigger buffer events. This extraction approach maintains measurement precision while dramatically improving real-time processing capability by avoiding full media file decryption and parsing.
Solution Approach 2:
The patent segments the buffer status update process into independent HTTP request analysis operations. Each HTTP request is analyzed separately for buffer event triggers without requiring sequential processing of entire media files. This segmentation enables parallel processing of multiple user requests, significantly enhancing productivity in mass user scenarios while maintaining accurate buffer status tracking through focused analysis of critical HTTP fields.
2Productivity
If HTTP Protocol field analysis is used to determine buffer events, then real-time buffer status updates are achieved, but the complexity of implementing multiple buffer event types increases
Solution Approach 1:
The patent implements a universal HTTP request analysis mechanism that handles multiple buffer event types (seek, pause, resume, stream switch) through a single unified process. The same HTTP field analysis logic identifies different event types by detecting specific patterns in the request parameters. This multi-functional approach maintains real-time processing speed while reducing implementation complexity compared to separate handling mechanisms for each event type.
Solution Approach 2:
The patent uses parameter changes in HTTP requests to differentiate between various buffer event types. By monitoring changes in specific HTTP parameters (such as range header values for seek events, timestamp parameters for pause/resume events), the system identifies different buffer events without requiring complex logic. This parameter-based differentiation simplifies the determination logic while maintaining the ability to handle multiple event types in real-time.
Data Source
Figure 1~3
Figure 4
Figure 5
AI summary
A Hypertext Transfer Protocol HTTP-based buffer status updating method is provided, where the method includes: (S11) receiving an HTTP request from a terminal; (S12) triggering a buffer event according to the HTTP request, where the buffer event includes seek, pause, resume, and stream switch; and (S13) updating a buffer status according to the buffer event, where the buffer status includes a normal play state, a play paused state, a re-buffering state, and a stream switch state. According to the buffer status updating method in the embodiments of the present invention, a buffer status is updated based on a buffer event in a manner of analyzing only an HTTP Protocol field, so that a buffer model is closer to a real client buffer situation. An HTTP Protocol-based buffer status updating device and an HTTP Protocol-based buffer status processor are further provided.