WO2012089014A1

WO2012089014A1 - Method, device and system for generating media file

Info

Publication number: WO2012089014A1
Application number: PCT/CN2011/083916
Authority: WO
Inventors: 方新; 许磊
Original assignee: 华为技术有限公司
Priority date: 2010-12-31
Filing date: 2011-12-14
Publication date: 2012-07-05
Also published as: CN102143384B; CN102143384A

Abstract

Disclosed are a method, device and system for generating a media file. The solution includes: a video server, for a normal play file with at least one type of code rate in the same content, generating at least one type of speed-multiplied file corresponding to the code rate; the play interval for each fragment of the speed-multiplied file is the same as that for each fragment of the normal speed file corresponding to the code rate; and recording the play duration of the content of each fragment of the speed-multiplied file in the content of the normal speed file. Also disclosed are a video server, a client and a media play system corresponding to the above method. Regarding the implementation of the technical solution in the present invention, in a media play solution based on HTTP adaptive streaming, the video server can provide the client with a speed-multiplied file having fast forward and fast-rewind, thus enabling the fast forward and fast-rewind functions of video play when the client receives a fast forward or fast-rewind order sent by the user.

Description

The invention relates to a Chinese patent application filed on December 31, 2010, the Chinese Patent Office, the application number is 2011 10007856.8, and the invention name is "a media file generation method, device and system". Priority is hereby incorporated by reference in its entirety.

TECHNICAL FIELD The present invention relates to the field of multimedia technologies, and more particularly to a media file generation method, apparatus, and system. BACKGROUND OF THE INVENTION Currently, in the Internet video solution, adaptive streaming (HTTP) based on HTTP (Hypertext Transfer Protocol) is a relatively popular video streaming method. The server provides a plurality of video files with different bit rates for the same video, and can dynamically select a video suitable for the current bit rate to be played to the user according to the capabilities of the user end, the network status, and the like during the video playing process, and bring the user to the user. The best experience. For example: For the same video content, when the mobile phone user plays, it may see a video of 350k code rate or 200k code rate; for broadband users, when the network quality is high, it may be 2M or higher. High-definition video with a bit rate, when the network quality is poor, the user may see a video that is reduced to a code rate of 1.5M or lower.

In the prior art, the normal playback protocol definition and file definition standard for defining live and on-demand content are introduced for the above-mentioned playback functions. For example: The existing Microsoft Silverlight - Smooth Streaming uses the box in the MP4 file format to organize each slice into a file. Each bit rate corresponds to generate an MP4 file, and the corresponding slice in each rate file is in time. With up-alignment, the client can dynamically select the most appropriate slice for playback based on the calculated network bandwidth, CPU processing power, and other factors.

The existing Manifest file in the http live stream is an extended m3u format file, The extended EXT-X-STREAM-INF tag associates the code rate with the playlist corresponding to the code rate. The client obtains the playlist of each bit rate by parsing the m3u file, and after requesting the code rate, requests and plays the video according to the corresponding playlist.

In the existing Adobe http streaming, the manifest file is a f4m file, and the f4m file describes various code rates and corresponding files U RL existing; the bootstrap file is mainly used for quick start, and each segment is given (program chapter). The length of the content corresponding to the fragment (further fragmentation of the chapter) is part of the manifest.

In the current protocol standards introduced by various manufacturers, it is mainly defined by the protocol definition and file definition standard for the normal play of live and on-demand content. The user can only jump the play progress bar forward or backward to realize the current video jump. turn. SUMMARY OF THE INVENTION Embodiments of the present invention provide a method, an apparatus, and a system for generating a media file. By adding a double-speed file with a fast forward and rewind function on the video server, the fast forward or fast reverse function of the video playback can be realized.

The embodiment of the invention provides a method for generating a media file, including:

Generating at least one double speed file corresponding to the code rate for a normal play file of at least one code rate of the same content; a normal rate file corresponding to the code rate for each slice play time interval of the double speed file Each shard plays the same time interval; the duration is long.

The embodiment of the invention provides a video server, including:

a file generating module, configured to generate at least one double speed file corresponding to the code rate for a normal play file of at least one code rate of the same content; each slice play time interval of the double speed file and the code The rate of each of the normal rate files corresponding to the rate is the same; the file management module is configured to record the content of each fragment of the double speed file at the normal rate The length of play in the file content.

Embodiments of the present invention provide a method for obtaining a media file, including

After receiving the fast forward or fast reverse command, determining a double speed file corresponding to the command in the content list acquired from the video server; the content list includes at least one of the following information, the information including Corresponding relationship between the at least one code rate and the generated at least one double speed file, the double speed file identifier added for the double speed file, and the playing time of each piece content of the double speed file in the normal rate file content; The position of the slice where the current playback time point is located;

Sending a slice download request to the video server, where the request includes the location of the slice where the current play time point is located.

An embodiment of the present invention provides a client, including

a command execution module, configured to: after receiving the fast forward or fast reverse command, determine a double speed file corresponding to the command in a content list acquired from the video server; the content list records at least one of the following information And the information includes: a correspondence between at least one code rate and the generated at least one double speed file, a double speed file identifier added to the double speed file, and a content determining module, configured to accumulate the each The duration of playback of the fragmented content in the normal rate file content, determining the location of the fragment where the current playback time point is located;

And a content obtaining module, configured to send a fragment download request to the video server, where the request includes a location of a fragment where the current playback time point is located.

The embodiment of the invention provides a media playing system, including:

a video server, configured to generate at least one double speed file corresponding to the code rate for a normal play file of at least one code rate of the same content; each slice play time interval of the double speed file and the code rate The corresponding normal rate file has the same playback interval for each slice; Long

a client, configured to: after receiving a fast forward or rewind command, obtain a content list from the video server, and determine a double speed file corresponding to the command in the content list; by accumulating the fragment of the time point a location; sending a slice download request to the video server, where the request includes a location of a slice at a current playback time point.

As can be seen from the technical solution provided by the foregoing embodiment of the present invention, the video server generates a play duration of at least one of the code rates corresponding to the normal play file of the at least one code rate of the same content. On the basis of the multi-rate file of the video server, the invention aims to increase the multi-speed fast forward and rewind files, and can meet the needs of the client. BRIEF DESCRIPTION OF THE DRAWINGS In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments will be briefly described below. It is obvious that the drawings in the following description are only some implementations of the present invention. For example, other drawings may be obtained from those skilled in the art without any inventive labor.

1 is a flowchart of a method for generating a media file according to an embodiment of the present invention;

2 is a flowchart of a method for acquiring a media file according to an embodiment of the present invention;

3 is a schematic structural diagram of a video server according to an embodiment of the present invention;

4 is a schematic structural diagram of a client according to an embodiment of the present invention;

FIG. 5 is a schematic structural diagram of a media playing system according to an embodiment of the present invention. The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention. Rather than all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

In the protocol standard introduced by the existing media playback solution based on HTTP adaptive streaming, there is no implementation definition and related protocol definition proposed for the fast forward and rewind service, so the user can only drag forward or backward. The method of moving a progress bar to realize the jump of the video content, and the method, device and system for processing the media file, the video server generates a normal play file of at least one code rate of the same content, and generates a code corresponding to the code rate. At least one double speed file; each slice play time interval of the double speed file is the same as each slice play time interval of the normal rate file corresponding to the code rate; and each piece content of the double speed file is recorded The playing time in the normal rate file content. By adding a double-speed file for different code rates on the video server, the technical solution of the embodiment of the present invention is applied to the existing media playback solution, and the fast forward or fast reverse function of the media file can be implemented, thereby improving the user experience.

In order to further understand the technical solutions proposed by the embodiments of the present invention, the following description will be made with reference to the accompanying drawings and specific embodiments.

The technical solution proposed by the embodiment of the present invention is implemented on the basis of a multi-rate file, and can be applied to an application scenario of an HTTP adaptive streaming video streaming mode of an Internet video solution.

As shown in FIG. 1 , the embodiment of the present invention provides a method for generating a media file based on a video server. The technical solution may include:

Step 101: The video server generates at least one double speed file corresponding to the code rate for a normal play file of at least one code rate of the same content; each slice play time interval of the double speed file and the code rate The corresponding normal rate file has the same playback time interval for each slice; the playback duration.

Since there is no double speed file corresponding to various code rates in the video server, the user can only rely on The content of the video playing content is adjusted by the play progress bar. According to the foregoing solution, in the embodiment of the present invention, a fast forward and rewind file of multiple speeds corresponding to the multi-rate file is added to the video server, so that the client receives the file. When the fast forward or rewind command is sent to the user, the position of the slice at the current play time point can be determined according to the play duration, so that the slice of the current play point can be obtained in the video server and played to the user.

It should be noted that, in an actual application, at least one double speed file may be generated corresponding to the video file of each code rate. When the client receives the fast forward or fast reverse command sent by the user, the client passes the The double-speed file corresponding to the command is obtained from the video server and provided to the user. In addition, among the normal rate files of multiple code rates, several normal rate files may be selected, and the corresponding double-speed file is generated, when the client receives the When the user sends a fast forward or fast reverse request, in the code rate file that has generated the double speed file, the double speed file closest to the current code rate is selected and provided to the client. For example: For a 200k code rate and a 400k code rate, respectively generate a 2x fast forward file and a 4x fast forward file corresponding to a 200k code rate and a 400k code rate, when the client receives the 2x fast forward command, at the current When the code rate is 350k, since the video server side does not generate the double speed file for the 350k code rate, the double speed file generated by the 400k code rate can be provided to the client.

Specifically, for the above solution, at the same code rate, the time interval of each slice playback of the double-speed file corresponding to the code rate is the same as the interval of each slice playback of the normal rate file corresponding to the code rate; for example: The interval between the normal rate file and the 2x rate file is 2 seconds. At the same bit rate, each fragment of the double speed file plays more content than the normal rate file in the same time interval. For example: When the interval between the normal rate file and the 2x rate file is 2 seconds, the content of each slice of the 2x rate file corresponds to 4 seconds in the content of the normal rate file. Therefore, In the embodiment of the present invention, the content of each fragment of the 2x rate file is identified by the duration (4 seconds) of the actual content of each fragment in the normal rate file by the 2x file, so that the client receives the fragment. After the fast forward or rewind command sent by the user, the position of the slice of the current play point can be determined according to the play duration of each slice of the double speed file.

It should be noted that the double speed file involved in the embodiment of the present invention refers to multiple speeds corresponding to multiple speeds. Fast forward or rewind files.

For the foregoing solution, the method may further include:

Adding a double speed file identifier to the double speed file for distinguishing the double speed file from a normal speed file.

For the foregoing solution, the method may further include:

Recording at least one of the following information in the content list, the information including: a correspondence between the at least one code rate and the generated at least one double speed file, adding a double speed file identifier to the double speed file And a playing duration of each of the sliced files in the normal rate file content.

Specifically, the above list of contents refers to the manifest file in the Microsoft Silverlight - Smooth Streaming scheme; the content list in the http live stream is the extended m3u format file; the content list in Adobe http streaming proposed by Adobe is the f4m file.

In the implementation of the existing media play solution, the content list is mostly used to record the correspondence between each media file and various code rates. In the embodiment of the present invention, each of the above code rates and multiple speeds are used. The correspondence relationship of the files, and the playing duration information are recorded in the content list, so that the video server and the client can determine the playing file corresponding to the fast forward or rewind command in time.

For the foregoing solution, the method may further include:

Receiving the content list obtaining request sent by the client;

Sending the content list to the client according to the content list obtaining request, so that the client provides a fast forward and rewind function button on the player when determining that the content list has a double speed file identifier Otherwise, hide the fast forward and rewind function buttons on the player.

For the foregoing solution, the method may further include:

After receiving the fast forward or fast rewind command, the client receives the fragment download request sent by the client, where the request includes the location of the fragment where the current play time point is located, where the The playing time is long, and the position of the slice where the current playing time point is located is determined; and the slice where the current playing time point is located is provided to the client.

Specifically, since the correspondence between each code rate and multiple multiple speed files is recorded in the content list, after receiving the fast forward or fast reverse command, the client needs to determine, in the content list, corresponding to the command. If the current code rate does not exist in the corresponding double speed file, the double speed file corresponding to the code rate file closest to the current code rate is provided to the client.

The method described in the foregoing embodiment of FIG. 1 is applicable to an application scenario of a video playback solution based on HTTP adaptive streaming.

As shown in FIG. 2, based on the method embodiment shown in FIG. 1 above, the embodiment of the present invention provides a method for obtaining a media file based on a client, and the technical solution may include:

Step 201: After receiving the fast forward or fast reverse command, determining a double speed file corresponding to the command in the content list acquired from the video server; and recording at least one of the following information in the content list, The information includes: a correspondence between at least one code rate and the generated at least one double speed file, adding a double speed file identifier to the double speed file, and each fragmented content of the double speed file is in a normal rate file content. Play time;

Step 202: Determine the location of the fragment where the current playback time point is located by accumulating the playing time of the content of each fragment in the normal rate file content.

Step 203: Send a fragment download request to the video server, where the request includes a location of a fragment where the current playback time point is located.

The method may further include:

Obtaining the content list to the video server, so as to provide a fast forward and rewind function button on the player when determining that the content list has a double speed file identifier, otherwise, the fast forward and rewind function buttons on the player hide.

The method described in the foregoing embodiment of FIG. 2 is applicable to an application scenario of a video playback solution based on HTTP adaptive streaming.

It should be noted that the embodiment of the present invention is obtained based on the method of the embodiment of FIG. 1 described above. Therefore, the same or corresponding technical features are included in the method embodiment of FIG. 1. At the same time, a method for implementing media file playback according to the embodiment of the present invention is implemented on the method embodiment shown in FIG. Therefore, refer to the related description in the foregoing embodiment of FIG. 1 for the specific technical solutions involved in the embodiments of the present invention.

As shown in FIG. 3, based on the foregoing method embodiment shown in FIG. 1, the embodiment of the present invention provides a video server, which includes the following functional modules:

a file generating module 31, configured to generate at least one double speed file corresponding to the code rate for a normal play file of at least one code rate of the same content; each slice play time interval of the double speed file and the Each slice playback time interval of the normal rate file corresponding to the code rate is the same; the file management module 32 is configured to record the play duration of each slice content of the double speed file in the normal rate file content.

Further, the server may further include:

The information recording module 33 is configured to add a double speed file identifier to the double speed file, to distinguish the double speed file from the normal speed file, and record at least one of the following information in the content list, where the information includes: Corresponding relationship between the at least one code rate and the generated at least one double speed file, the double speed file identifier added for the double speed file, and the playback of each piece content of the double speed file in the normal rate file content duration.

Further, the server may further include:

The request processing module 34 is configured to receive a content list obtaining request sent by the client, and send the content list to the client, so that when the client determines that the content list has a double speed file identifier, The fast forward and rewind function buttons are provided on the player. Otherwise, the fast forward and rewind function buttons on the player are hidden.

Further, the server may further include:

a file providing module 35, configured to receive a fragment download request sent by the client, where the request includes a location of a fragment where a current playing time point is located, where the client is accumulated The position of the slice where the current playback point is located;

Providing the slice of the current play time point to the client.

The video server described in the foregoing embodiment of FIG. 3 is applicable to an application scenario of a video playback solution based on HTTP adaptive streaming.

It should be noted that, the embodiment of the present invention is a video server obtained by the method according to the foregoing embodiment of FIG. 1 , and therefore includes the same technical features as the method embodiment of FIG. 1 . The related description in the above embodiment of Fig. 1 is not described herein.

As shown in FIG. 4, based on the method embodiment shown in FIG. 2, the embodiment of the present invention provides a client, which includes the following functional modules:

The command execution module 41 is configured to: after receiving the fast forward or fast reverse command, determine, in the content list acquired from the video server, a double speed file corresponding to the command; wherein the content list records the following information At least one of the information includes: a correspondence between at least one code rate and the generated at least one double speed file, a double speed file identifier added to the double speed file, and a content determining module 42, configured to The duration of each slice content in the normal rate file content, determining the location of the slice where the current playback time point is located;

The content obtaining module 43 is configured to send a fragment download request to the video server, where the request includes a location of the fragment where the current playing time point is located.

Further, the client may further include:

The information obtaining module 44 is configured to obtain the content list from the video server, and the function providing module 45 is configured to: when determining that the content list has a double speed file identifier, provide a fast forward and rewind function button on the player, Otherwise, hide the fast forward and rewind function buttons on the player.

The client described in the foregoing embodiment of FIG. 4 is applicable to an application scenario of a video playback solution based on HTTP adaptive streaming. It should be noted that, the embodiment of the present invention is based on the foregoing method of the embodiment of FIG. 2, and includes the same technical features as the method embodiment of FIG. 2, and the specific technical solution involved in the embodiment of the present invention may be referred to. The related description in the above embodiment of Fig. 2 is not described here.

As shown in FIG. 5, based on the method embodiment shown in FIG. 1, the embodiment of the present invention provides a media playing system, including:

a video server 51, as shown in FIG. 3, configured to generate at least one double speed file corresponding to the code rate for a normal play file of at least one code rate of the same content; each slice play of the double speed file The time interval is the same as each slice play time interval of the normal rate file corresponding to the code rate; and the play duration of each slice content of the fast forward rewind file in the normal rate file content is recorded;

The client 52 is configured to obtain a content list from the video server after receiving the fast forward or fast reverse command, and determine a double speed file corresponding to the command in the content list; The location of the slice at the time point; sending a slice download request to the video server, where the request includes the location of the slice where the current play time point is located.

It should be noted that, as the embodiment of the present invention includes the same technical features as the video server shown in FIG. 3 and the client shown in FIG. 4, the specific technical solution involved in the embodiment of the present invention may be referred to the foregoing embodiment. The relevant description, do not do this - repeat.

To illustrate the technical solution proposed by the embodiment of the present invention, the following is an example of improvement of three adaptive streaming video playback solutions.

Embodiment 1 of the present invention:

The technical solution of the embodiment of the present invention is described by taking the technical solution of the existing Microsoft Silverlight-Smooth Streaming in the HTTP adaptive streaming video streaming mode as an example.

(1) The video server generates a normal play file for at least one code rate of the same content. At least one double speed file corresponding to the code rate; each slice play time interval of the double speed file is the same as each slice play time interval of the normal rate file corresponding to the code rate;

An example of a double speed file format is as follows:

NBA_50000_F2.ismv: 2x fast forward (for fast forward files with a rate of 50000k) NBA _50000_F4.ismv: 4x fast forward (for fast forward files with a rate of 50000k) NBA _50000_B1.ismv: 1x fast rewind (representing a 1x fast rewind file with a code rate of 50000k)

NBA _50000_B2.ismv: 2x fast rewind (representing a 2x fast rewind file with a code rate of 50000k)

(2) adding a double speed file identifier to the double speed file, and recording a play duration of each fragment content of the double speed file in the normal rate file content;

(3) recording a correspondence between the at least one code rate and the generated at least one double speed file in a content list;

In the embodiment of the present invention, the content list is a manifest file. Usually a silverlight video file consists of:

Msmv: used to represent video and audio files of different code rates, or only video;

Msma: an audio file used to represent different bit rates;

*.ism: Server (server) manifest file: XML format, used to describe the correspondence between media files and code rate, used only by the server;

*.ismc: Client (client) manifest file: XML format, used to describe the media information that the client can request, including: code rate, resolution, codec type, etc. When the client implements the playback function, it needs to request the file first. .

In the embodiment of the present invention, a double-speed file identifier is added to the double-speed file, specifically, a description of the double-speed file is added in *.ism, and a modetype identifier may be used to represent the playback rate. The modetype describes the playback rate of the double-speed file. If the identifier does not exist, the media file is a normal rate media file:

For example: <video src=" NBA_50000.ismv " systemBitrate="50000"> (The media file does not have a modetype identifier, so the file is a normal rate media file)

</video>

<video src=" NBA_50000_F2.ismv " systemBitrate="50000" modetype="forward2"> (The file has a modetype identifier, and the shell 'J determines that the file is a 2x fast-forward file with a code rate of 50000k)

</video>

In *.ismc, you also need to add a Streamlndex tag to each speed. For example, use the modetype to indicate the playback rate, and the modetype to describe the playback rate of the double-speed file. If the identifier does not exist, the media is at the normal rate. Document

For each slice of the double speed file, each slice is identified by the play duration of each slice content in the normal rate file content, and the duration of each slice content of the double speed file is The normal playback duration of the content in the normal rate file, rather than the actual playback duration of each fragment of the double speed file;

Such as: <Streamlndex Type="video" Subtype="WVC1 " Chunks="149" modetype="forward2"

Url="QualityLevels({bitrate})/Fragments(video={start

Time}/Modetype(forward=2))"> (The file has a Modetype identifier, which is known to be

2x fast forward file)

<QualityLevel Bitrate="500000" FourCC="WVC1 " Width="1280" Height="720"

CodecPrivateData="250000010FD3BE27F1678A27F859E804508253EB E8E6C00000010E5AE7F840"/> <QualityLevel Bitrate="800000"FourCC="WVC1"

Width="1056" Height="592" CodecPrivateData="250000010FD3BE20F1278A20F849E80450823E41 4DD1400000010E5AE7F840" />

(4) The video server receives a request from the client to obtain a manifest file;

(5) The client receives the manifest file sent by the video server, determines whether there is a double speed file identifier in the manifest file to determine whether there is a double speed file, and provides a fast forward fast on the player when the double speed file exists Press the function button, otherwise, hide the fast forward and rewind function buttons on the player;

(6) after the client receives the fast forward or fast reverse command sent by the user, the client determines a Streamlndex of the multiple speed file corresponding to the current code rate in the manifest file, and determines a corresponding to the command. Double speed file

The playback duration in the at least one initial video data corresponding to the code rate is determined in the rewind file. The client obtains the location of the fragment of the current playback time point by accumulating each fragment content of the double speed file, and playing time of the corresponding content in the normal rate file;

(7) The video server receives the fragment download request sent by the client, where the request includes the location of the fragment where the current playback time point is located;

Providing the slice of the current play time point to the client.

Specifically, in the first embodiment of the present invention, the request format of the client video fast forward can be implemented as follows:

Url="*.ism/QualityLevels({bitrate})/Fragments(video={start

Time})/Modetype(forward={times})" The client video rewind request format can be implemented as follows:

Url="*.ism/QualityLevels({bitrate})/Fragments(video={start

Time})/Modetype(backward={times})"

It can be seen from the above embodiment that the technical solution of the embodiment of the present invention is applied to the technical solution of Microsoft Silverlight - Smooth Streaming, which can realize the fast forward or fast reverse function during video playback.

Embodiment 2 of the present invention:

The technical solution of the embodiment of the present invention is described by taking an existing Apple live stream solution as an example.

It should be noted that the content list of the Apple live stream is an extended m3u format file, including a total m3u file and an m3u file corresponding to each rate playlist;

(1) The video server generates at least one double speed file corresponding to the code rate for a normal play file of at least one code rate of the same content; each slice play time interval of the double speed file and the code rate The corresponding normal rate file has the same interval for each slice playback;

(3) a correspondence between the at least one code rate and the generated at least one double speed file

Long, recorded in the content list;

Specifically, in the second embodiment of the present invention, the EXT-X-STREAM-INF tag is extended to identify the double-speed file, which is used to distinguish the normal play rate playlist from the double-speed file playlist, and is specifically implemented as follows:

#EXTM3U

#EXT-X-STREAM-INF: PROGRAM-ID=1, BANDWIDTH=550000

Inlet_550000.m3u8

#EXT-X-STREAM-INF: PROGRAM-ID=1, BANDWIDTH=850000

Inlet 850000. m3u8 #EXT-X-STREAM-INF: PROGRAM-ID=1, BANDWIDTH=2950000 inlet_2950000.m3u8

#EXT-X-STREAM-INF: PROGRAMID=1, BANDWIDTH=550000, FORWA RD=2

Inlet_550000_F2.m3u8 (This flag has been added FORWARD=2, so the file ID

2x fast forward file)

#EXT-X-STREAM-INF: PROGRAM-ID=1, BANDWIDTH=550000, BACKW ARD=2 (The FORWARD=2 is added to the flag, so the file identifies the 2x fast rewind file)

inlet_550000_B2.m3u8

For the playlist of the double-speed file, each shard also indicates the playing duration of the corresponding content in the normal rate file. The method for identifying the playing duration in the second embodiment of the present invention is the same as the method in the method embodiment of FIG. ;

E.g:

#EXTM3U

#EXT-X-TARGETDURATION: 10

#EXT-X-MEDIA-SEQUENCE:0

#EXTINF:4, no desc

inlet_550000_F2.ts?start=0&end=2

#EXTINF:4, no desc

inlet_550000_F2.ts?start=2&end=4

#EXTINF:4, no desc

Inlet_550000 — F2.ts?start=4&end=6

#EXTINF:4, no desc

i n let_550000_F2.ts?start=8&end= 10

#EXTINF:4, no desc

inlet_550000_F2.ts?start=10&end=12

(5) The video server receives the m3u file download request sent by the client; (6) The client receives the m3u file sent by the video server, determines whether there is a double speed file identifier in the m3u file to determine whether there is a double speed file, and when there is a double speed file, provides a fast forward and rewind function button on the player. Otherwise, hide the fast forward and rewind function buttons on the player;

(7) When the client receives the fast forward or rewind command sent by the user, the client finds the playlist of the corresponding double speed file according to the current code rate in the obtained m3u file, and determines the playlist corresponding to the command. Calculate the position of the slice at the current time point by accumulating the content duration of each slice;

(8) The video server receives the fragment download request sent by the client, where the request includes the location of the fragment where the current playback time point is located;

Providing the slice of the current play time point to the client.

Embodiment 3 of the present invention:

The technical solution of the embodiment of the present invention will be described by taking Adobe http streaming as an example. It should be noted that in Adobe http streaming, the content list is a f4m file, and the f4m file describes various code rates and corresponding file urls existing; the bootstrap file is mainly used for quick start, which gives each The length of the content corresponding to segment and fragment is part of the manifest.

Specifically, for Adobe http streaming through f4m, by extending the speed of text The modetype (modetype) is used to distinguish between double speed files and normal play files to support fast forward and rewind playback functions, such as:

<media

Streamld="train_2500"

Bitrate="550000"

Url=" train_2500"

Bootstrap Info I d="bootstrap_550000" (This file is a file that is normally played because there is no modetype tag)

>

</media>

<media

Streamld="train_2500_f2"

Bitrate="550000"

Url=" train_2500_f2"

Modetype="forward2"

Bootstraplnfold="bootstrap_550000J2" (The modetype tag is in this file, so it is a 2x fast forward file)

>

</media>

< bootstrap Info

Profile="named"

Id="bootstrap_550000_f2"

Url="train_f2. bootstrap"

/>

In the third embodiment of the present invention, a bootstrap file is separately provided for each speed, and the duration is set. The method for identifying the play duration in the third embodiment of the present invention is the same as the method in the method embodiment of FIG. 1; (4) The video server receives the client f4m file download request;

(5) The client receives the f4m file sent by the video server, determines whether there is a double speed file identifier in the f4m file to determine whether there is a double speed file, and when there is a double speed file, provides a fast forward and rewind function button on the player. Otherwise, hide the fast forward and rewind function buttons on the player;

(6) When the client receives the fast forward and rewind command sent by the user, the client first determines the bootstrap corresponding to the command, and calculates the position of the slice at the current time point by accumulating the duration of each slice. And requesting the fragment from the video server;

(7) The video server provides the shard to the client, so that the user can play the shard to the user.

In summary, the method, device and system for processing a media file proposed by the present invention, the implementation of the technical solution of the present invention, in the application scenario based on the HTTP adaptive streaming video streaming mode, realizing the process of media playing The fast forward and rewind function is an effective complement to the fast forward and rewind services, and increases the ease of use of the HTTP adaptive streaming solution, while also improving the user experience.

A person skilled in the art can understand that all or part of the process of implementing the above embodiment method can be completed by a computer program to instruct related hardware, and the program can be stored in a computer readable storage medium. In execution, the flow of an embodiment of the methods as described above may be included. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

The above is only a preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or within the technical scope disclosed by the present invention. Alternatives are intended to be covered by the scope of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

Rights request

A method for generating a media file, comprising:

Generating at least one double speed file corresponding to the code rate for a normal play file of at least one code rate of the same content; a normal rate file corresponding to the code rate for each slice play time interval of the double speed file Each shard plays the same time interval; long.

The method according to claim 1, wherein the method further comprises: adding a double speed file identifier to the double speed file for distinguishing the double speed file from a normal rate file.

The method according to claim 1 or 2, wherein the method further comprises: recording at least one of the following information in a content list, the information comprising: the at least one code rate Corresponding relationship with the generated at least one double speed file, a double speed file identifier added for the double speed file, and a play duration of each piece content of the double speed file in the normal rate file content.

The method according to claim 3, wherein the method further comprises: receiving a content list acquisition request sent by the client;

The method according to claim 4, wherein the method further comprises: receiving a fragment download request sent by the client, where the request includes a location of a fragment where the current playback time point is located, where Determining, by the client, the location of the fragment of the current playback point by accumulating the playing duration of each fragment content of the double-speed file in the normal rate file content;

Providing the slice of the current play time point to the client.

The method according to claim 1 or 2, wherein the method is applicable to an application scenario of a video playback solution based on HTTP adaptive streaming.

7. A video server, comprising:

a file generating module, configured to generate at least one double speed file corresponding to the code rate for a normal play file of at least one code rate of the same content; each slice play time interval of the double speed file and the code The rate of each of the fragment rate playback time of the normal rate file is the same; the file management module is configured to record the duration of playing of each fragment content of the fast forward and rewind file in the normal rate file content.

8. The video server according to claim 7, wherein the server further comprises:

An information recording module, configured to add a double speed file identifier to the double speed file, to distinguish the double speed file from a normal speed file; and record at least one of the following information in a content list, where the information includes: Corresponding relationship between the at least one code rate and the generated at least one double speed file, the double speed file identifier added for the double speed file, and the playback of each piece content of the double speed file in the normal rate file content duration.

9. The video server according to claim 8, wherein the server further comprises:

a request processing module, configured to receive a content list obtaining request sent by the client, and send the content list to the client according to the content list obtaining request, so that the client determines the content list When there is double file identification, the fast forward and rewind function buttons are provided on the player. Otherwise, the fast forward and rewind function buttons on the player are hidden.

10. The video server according to claim 9, wherein the server further comprises:

a file providing module, configured to receive a fragment download request sent by the client, where the request includes a location of a fragment where the current playing time point is located, where the client adds the The position of the slice where the current playback point is located;

Providing the slice of the current play time point to the client.

1 1. A method for obtaining a media file, characterized in that

After receiving the fast forward or fast reverse command, determining a double speed file corresponding to the command in the content list acquired from the video server; the content list includes at least one of the following information, the information including Corresponding relationship between the at least one code rate and the generated at least one double speed, the double speed file identifier added for the double speed file, and the playing time of each piece content of the double speed file in the normal rate file content; The position of the slice where the playback time is located;

The method according to claim 11, wherein the method further comprises: acquiring the content list from the video server, so as to determine that there is a double speed file identifier in the content list, on the player Provide fast forward and rewind function buttons, otherwise, hide the fast forward and rewind function buttons on the player.

13. A client, characterized in that

a command execution module, configured to: after receiving the fast forward or rewind command, determine a double speed file corresponding to the command in a content list acquired from the video server; and the content list records at least one of the following information The information includes: a correspondence between at least one code rate and the generated at least one double speed file, a double speed file identifier added to the double speed file, and the content determining module, configured to accumulate each of the The playing time of the fragmented content in the normal rate file content, determining the location of the fragment where the current playing time point is located;

The content obtaining module is configured to send a fragment download request to the video server, where the request includes a location of a fragment where the current playback time point is located.

The client according to claim 13, wherein the client further includes: an information acquiring module, configured to acquire the content list from the video server;

The function providing module is configured to provide a fast forward and rewind function button on the player when determining that the content list has a double speed file identifier, otherwise, the fast forward and rewind function buttons on the player are hidden.

15. A media playing system, comprising:

a video server, configured to generate at least one double speed file corresponding to the code rate for a normal play file of at least one code rate of the same content; each slice play time interval of the double speed file and the code rate Each slice playback time interval of the corresponding normal rate file is the same;