Client HTTP retrieval full-index container format media resource time slice method

Abstract

The invention discloses a client HTTP retrieval full-index container format media resource time slice method, comprising the steps of: analyzing media slice URI, obtaining a primary resource URI and a time interval of the slice; judging whether the slice is in a local HTTP cache; judging whether a service end updates the primary resource of the slice; obtaining a slice resource file from the local HTTP cache, to finish the process; requesting and obtaining a head information of the primary resource from the service end; mapping the time interval of the slice as a primary resource byte range; requesting and obtaining the byte range for the server end; modifying the header information, and synthesizing into the slice resource file with the byte range. The present invention discloses a client HTTP retrieval full-index container format media resource time slice method, can support a W3C media slice URI 1.0 standard, and the client completes the mapping of the time slice URI to the media resource byte scope and obtains the byte range from the traditional server end to generate the section slice file, thus greatly saving communication bandwidth and shorter communication delay.

Description

technical field [0001] The invention relates to the technical field of multimedia communication, in particular to a method for a client HTTP to retrieve a time segment of a media resource in a full index container format. Background technique [0002] As we all know, multimedia resources such as images, audio and video are important information sources on the World Wide Web (Web). In particular, Web 2.0 applications that have emerged in recent years (such as YouTube and Youku for sharing video resources) have spawned a large number of Web social media resources. However, various media resources have always been "second-class citizens" of the Web, because they must be embedded in other Web resources (such as HTML pages), and only after the interaction and decoding of "plugin" software can the audio-visual content be accessed by Web users. Consumption. In order to make multimedia resources a "first-class citizen", the maker of Web infrastructure technical standards - the Wor...

AI Technical Summary

Problems solved by technology

[0017] More recently, some partial support for the HTML5 candidate standard (see "Berjon R, Faulkner S, Leithead T, Doyle Navara E, O'Connor E, Pfeiffer S, Hickson I (Editors).HTML5: A vocabulary and associated APIs for HTML and XHTML[ R / OL]. W3C Candidate Recommendation, 6 August 2013: http: / / www.w3.org / TR / 2013 / CR-html5-20130806 / .”) latest version of the browser (such as: Mozilla Firefox and Google Chrome, etc. ) can partially support the online playback of the time segment identified by the media segment URI1.0. Its disadvantage is that it only partially supports the syntax of the time segment URI1.0, and can only play the time segment online in the browser, and cannot allow customers The terminal extracts and obtains the time segment resource file, so it cannot further support the realization of various segment actual use cases required in the W3C "Media Fragment Use Cases and Requirements (Draft)", including: segment linking, browsing and bookmarking, recomposition, labeling , and the adaptation of media resources, etc.

The main defects of the patented technical solution of this invention include: it does not support W3C's "Media Fragment URI 1.0 (Basic) Standard" at all; it can only play multimedia files online, and cannot enable the client to obtain time fragment resource files; between the client and the server And between the playback unit and the download unit of the client, complex interactions need to be constantly carried out; only the steps of downloading, parsing the header information of the multimedia file and obtaining the download location of the multimedia data are described macroscopically (not enough to explain that its technical solution is suitable for various implementability and practicability of multimedia formats), in particular, did not specifically describe the technical solution for the time segment of media resources in the full index container format, nor did it specifically give the corresponding HTTP request / response protocol steps

Images