A method for implementing hls content back-to-source and caching

Abstract

A method for realizing back-to-source and caching of HLS content relates to the field of Internet multimedia technology. In the present invention, after the cache server receives an HLS content request from the client, it will allocate a session object for the client and generate a unique identifier; if the HLS content has been cached locally, it will directly respond to the current and subsequent requests. If it is not cached, the cache server needs to request all index files of the HLS content from the origin site, and modify the addresses in them; after receiving each media segment request from the client, the cache server requests the corresponding origin site, and will When the sub-media fragments are returned to the client, the sub-media fragments are continuously stored in a large file according to the sequence in the index file until all media fragments are stored. The invention can completely track the behavior of the client, and has strong adaptability to the source return process, high docking efficiency with the source station, and high storage utilization efficiency and disk throughput rate.

Description

technical field [0001] The invention relates to the field of Internet multimedia technologies, and specifically relates to a method for realizing back-to-source and caching of HLS content. Background technique [0002] HLS (HTTP Live Streaming) is an HTTP-based multi-bit rate adaptive streaming media specification proposed by Apple. At present, HLS has become the mainstream streaming media playback specification on the Internet and mobile Internet. This specification supports a content with multiple media files with different bit rates, and each bit rate media file is divided into many small files with a duration of about ten seconds. A content has several different bit rates, and which small files a bit rate consists of. These information are organized in several index files. These index files are in M3U8 format, so they are also called M3U8 files. [0003] The process of the client playing HLS content is essentially the process of downloading index files and fragment fil...

AI Technical Summary

Problems solved by technology

However, there are still the following deficiencies: (1) Since the HTTP protocol is stateless, the client's requests for each index file and fragment file of the same HLS content are independent and fragmented, and the cache server cannot complete the request. Track a playback behavior of a client; (2) Since the tail of the HTTP URL is portable? , &, # and other symbols with specific meanings, the current back-to-source method does not define a unified processing rule, which leads to low docking efficiency between the cache node and the source site; Unrelated small files are stored, which will lead to more disk fragments on the cache server, low space utilization, small operation granularity, and low read and write performance. When the file descriptor overhead of the cache server is too large, it will also cause security risks

Images