WO2017114393A1 - Http streaming media transmission method and device - Google Patents

Abstract

Provided are an HTTP streaming media transmission method and device. The method comprises: sending an acquisition request of first media data to a server, the acquisition request carrying a push instruction of second media data; receiving the first media data returned by the server, a push response of the second media data, and a push commitment of the second media data sent by the server according to the push response; and sending a stream termination command to the server, the stream termination command being used for terminating a push stream of the second media data reserved by the server according to the push commitment, so that the push update mechanism in an HTTP streaming media transmission session is improved. The problem that there is no effective solution for an HTTP streaming media push update is solved.

Description

HTTP streaming media transmission method and device Technical field

The present invention relates to the field of communications, and in particular to an HTTP streaming media transmission method and apparatus.

Background technique

In recent years, the content of video transmitted through the Internet has experienced explosive growth, which is due to the increase in access bandwidth, including the scale application of 3G and 4G systems, Digital Subscriber Line (xDSL) and fiber optic connection. A large number of deployments for home users have effectively increased the access bandwidth of the last mile; on the other hand, the progress of video coding has improved the compression ratio of video, H.264/AVC, H.265/HEVC are all aspects of this. representative. According to statistics, in 2014, HTTP video data has accounted for more than 50% of Internet traffic in North America. It is estimated that by 2020, mobile video data traffic will account for more than 70% of mobile data traffic.

Hypertext Transfer Protocol (HTTP) streaming media (HTTP Streaming) has been widely used for its compatibility and scalability, and has become the de facto standard for Internet video transmission. HTTP streaming is a rate-adaptive media transmission technology based on the HTTP protocol, which uses the traditional HTTP web server on the Internet to provide high-quality streaming media content. HTTP streaming divides a video into chunks of files on many small HTTP servers, each of which contains a video content with a shorter playback time. These small video clips may be part of a few hours of movie (on demand) or live video (live) of a sports event. Among them, the video can be encoded into a plurality of video segments of different code rates to cover different network bandwidth requirements. The Media Presentation Description (MPD) defined by the Extensible Markup Language (XML) format provides location information and time information for the client to acquire and play media segments in the video content. The MPD file describes the duration of the media segment, the Uniform Resource Locator (URL), and media properties such as video resolution, adaptation bitrate, and so on. When the client chooses to play a video, it can choose to download according to the information in the MPD file to adapt to the current available. The network bandwidth and the media segment of the terminal decoding and rendering capabilities are played and played.

However, the HTTP protocol was originally designed for file transfer (such as Web pages). It does not consider the real-time transmission characteristics of video, so it cannot meet the requirements of low-latency video transmission: First, HTTP streaming is a unit of media segment (segment). File download technology, a segment contains several seconds of video frames, which will lead to unavoidable media segmentation and encoding delays; secondly, although the Content Delivery Network (CDN) has been widely deployed to provide users with Near access service, but asynchronous data acquisition based on client polling (Poll) will still bring additional delay; FIG. 1 is a schematic diagram of PULL mode transmission according to the related art HTTP streaming technology, as shown in FIG. The HTTP 1.1 protocol provides a pull mode (PULL) transmission mechanism. The client must send an HTTP request for each media segment. The HTTP request has a large overhead and is inversely proportional to the length of the media segment. It is not suitable for resource limitation. Mobile terminal. Therefore, efficient (low latency, reasonable request) video transmission under Internet conditions, especially Live Video applications, is still a huge challenge for HTTP streaming.

Currently, an upgraded version of the HTTP protocol, HTTP 2.0, provides a viable solution. Compared with HTTP 1.1, HTTP 2.0 improves the transmission performance of the protocol, supporting request-response multiplexing, protocol header compression, and server "Server Push" features. 2 is a schematic diagram of PUSH mode transmission in the HTTP streaming technology according to the related art. As shown in FIG. 2, using the HTTP 2.0 server “push”, the server can actively push the latest available fragment to the client without the client. Additional requests. Specifically, after processing a certain media segment HTTP request, the HTTP 2.0 server will agree with the client on the subsequent media segment push strategy (Push Strategy), and actively push the subsequent available K media to the client according to the push policy. A fragment, or a subsequent media segment with a playback time of T seconds, to reduce the live broadcast delay and reduce the request overhead.

In the HTTP streaming media transmission technology based on the "push" feature of the server, the client needs to dynamically update the "pushing policy" of the media segment according to available network bandwidth, player buffer status, etc., that is, requesting the server to change the number of pushed media segments ( Push Sequence) and Representation Switch. However, in the related art, there is currently no valid HTTP. Streaming media push update solution.

Summary of the invention

The embodiment of the invention provides an HTTP streaming media transmission method and device, so as to at least solve the problem that the effective HTTP streaming media push update solution does not exist in the related art.

According to an embodiment of the present invention, an HTTP streaming media transmission method is provided, including:

Sending an acquisition request of the first media data to the server, where the obtaining request carries a push indication of the second media data;

Receiving, by the server, the first media data, a push response of the second media data, and a push commitment of the second media data sent by the server according to the push response;

Sending a flow termination command to the server, the flow termination command is configured to terminate a push flow of the second media data reserved by the server according to the push commitment.

Optionally, after receiving the push commitment of the second media data that is sent by the server according to the push response, the method further includes:

Receiving, by the server, the second media data that is pushed according to the push commitment.

Sending a flow termination command to the server, the flow termination command is configured to terminate a push flow reserved by the server according to the push commitment that has not completed pushing the second media data.

Optionally, before the sending a flow termination command to the server, the method further includes:

An immediate termination flag value is set in the flow termination command, the immediate termination flag is used to instruct the server to immediately stop pushing the second media data in the push flow, and terminate the push flow.

Optionally, before the sending a flow termination command to the server, the method further includes:

And setting an immediate termination flag value in the flow termination command, the immediate termination flag is used to instruct the server to complete pushing the second media data in the push flow, and then terminating the push flow.

According to an embodiment of the present invention, an HTTP streaming media transmission method is further provided, including:

Receiving an acquisition request of the first media data sent by the client, where the obtaining request carries a push indication of the second media data;

Returning a push response of the first media data and the second media data, and sending a push commitment of the second media data to the client according to the push response;

Receiving a stream termination command sent by the client, and terminating, according to the stream termination command, a push stream of the second media data reserved according to the push commitment.

Optionally, after sending the push commitment of the second media data to the client according to the push response, the method further includes:

Pushing the second media data to the client according to the push commitment;

Receiving a flow termination command sent by the client, and terminating, according to the flow termination command, a push flow reserved according to the push commitment that has not completed pushing the second media data.

Optionally, the terminating, according to the flow termination command, the push flow of the second media data that is reserved according to the push commitment includes:

If there is an immediate termination flag in the stream termination command, immediately stopping pushing the second media data in the push stream, and terminating the push stream;

If there is no immediate termination flag in the stream termination command, the second media data is pushed in the push stream, and then the push stream is terminated.

According to another embodiment of the present invention, an HTTP streaming media transmission method is further provided, including:

Sending an acquisition request of the first media data to the server, where the obtaining request carries a push update indication of the second media data;

Receiving, by the server, the first media data returned by the server, and a push update response of the second media data;

Receiving a stream termination command sent by the server, and terminating the receiving station according to the stream termination command Said second media data pushed by the server.

Optionally, after the sending the sending request of the first media data to the server, the method further includes:

Receiving a push commitment of the second media data sent by the server;

Receiving a stream termination command sent by the server, and terminating receiving, according to the stream termination command, the second media data that the server has not completed pushing according to the push commitment.

Optionally, after receiving the push update response of the second media data, the method further includes:

Receiving a push commitment of the third media data sent by the server according to the push update response;

Receiving, by the server, the third media data that is pushed according to the push commitment.

According to another embodiment of the present invention, an HTTP streaming media transmission method is further provided, including:

Receiving an acquisition request of the first media data sent by the client, where the obtaining request carries a push update indication of the second media data;

Returning the first media data, and the push update response of the second media data to the client;

Sending a stream termination command to the client, the stream termination command is used to terminate the reserved push stream of the second media data.

Optionally, after the receiving the first media data sent by the client, the method further includes:

Sending a push commitment of the second media data to the client;

Sending a flow termination command to the client, the flow termination command is configured to terminate a push flow reserved according to the push commitment that has not completed pushing the second media data.

Optionally, after the returning the push update response of the second media data to the client, the method further includes:

Sending a push commitment of the third media data to the client according to the push update response;

Pushing the third media data to the client according to the push commitment.

Optionally, the sending a flow termination command to the client, where the flow termination command is used to terminate the pushed push stream of the second media data includes:

If there is an immediate termination flag in the push update indication, immediately send a stream termination command to the client in the push stream to terminate the push stream;

If the immediate termination flag does not exist in the push update indication, completing the second media data being pushed in the push stream to the client, and then sending a stream termination command to the client in the push stream Ending the push stream.

According to another embodiment of the present invention, there is also provided an HTTP streaming media transmission device, located in the terminal, comprising:

The first sending module is configured to send an acquisition request of the first media data to the server, where the obtaining request carries a push indication of the second media data;

a first receiving module, configured to receive the first media data returned by the server, a push response of the second media data, and a push commitment of the second media data sent by the server according to the push response ;

And a second sending module, configured to send a stream termination command to the server, where the stream termination command is used to terminate the push stream of the second media data reserved by the server according to the push commitment.

Optionally, the device further includes:

The second receiving module is configured to receive, after receiving the push commitment of the second media data sent by the server according to the push response, the second media data that is sent by the server according to the push commitment;

And a third sending module, configured to send a flow termination command to the server, where the flow termination command is used to terminate a push flow reserved by the server according to the push commitment that has not completed pushing the second media data.

Optionally, the device further includes:

a first setting module, configured to set an immediate termination flag value in the flow termination command before the sending a flow termination command to the server, where the immediate termination flag is used to indicate that the server is immediately in the push flow Stop pushing the second media data and terminating the push stream.

Optionally, the device further includes:

a second setting module, configured to set an immediate termination flag value in the flow termination command before the sending a flow termination command to the server, where the immediate termination flag is used to indicate that the server is completed in the push flow Pushing the second media data and then terminating the push stream.

According to another embodiment of the present invention, there is also provided an HTTP streaming media transmission device, located in the server, comprising:

The fourth receiving module is configured to receive a request for acquiring the first media data sent by the client, where the acquiring request carries a push indication of the second media data;

a fourth sending module, configured to return a push response of the first media data and the second media data, and send a push commitment of the second media data to the client according to the push response;

The fifth receiving module is configured to receive a stream termination command sent by the client, and terminate the push stream of the second media data reserved according to the push commitment according to the stream termination command.

Optionally, the device further includes:

The fifth sending module is configured to: after sending the push commitment of the second media data to the client according to the push response, pushing the second media data to the client according to the push commitment;

And a sixth receiving module, configured to receive a flow termination command sent by the client, and terminate, according to the flow termination command, a push flow reserved according to the push commitment that has not completed pushing the second media data.

Optionally, the fifth receiving module includes:

a first termination unit, configured to have an immediate termination flag in the flow termination command, Immediately stopping pushing the second media data in the push stream and terminating the push stream;

And a second terminating unit configured to: if the instant termination flag does not exist in the stream termination command, complete the pushing of the second media data in the push stream, and then terminate the push stream.

According to another embodiment of the present invention, there is also provided an HTTP streaming media transmission device, located in the terminal, comprising:

a sixth sending module, configured to send an acquisition request of the first media data to the server, where the obtaining request carries a push update indication of the second media data;

a seventh receiving module, configured to receive the first media data returned by the server, and a push update response of the second media data;

The eighth receiving module is configured to receive a stream termination command sent by the server, and terminate receiving the second media data pushed by the server according to the stream termination command.

Optionally, the device further includes:

a ninth receiving module, configured to receive a push commitment of the second media data sent by the server, after the sending the sending request of the first media data to the server;

The tenth receiving module is configured to receive a stream termination command sent by the server, and terminate receiving, according to the stream termination command, the second media data that the server has not completed pushing according to the push commitment.

Optionally, the device further includes:

The eleventh receiving module is configured to receive, after receiving the push update response of the second media data, a push commitment of the third media data sent by the server according to the push update response;

The twelfth receiving module is configured to receive the third media data that is pushed by the server according to the push commitment.

According to another embodiment of the present invention, there is also provided an HTTP streaming media transmission device, located in the server, comprising:

a thirteenth receiving module, configured to receive a request for acquiring the first media data sent by the client, where the obtaining request carries a push update indication of the second media data;

a seventh sending module, configured to return the first media data, and a push update response of the second media data to the client;

And an eighth sending module, configured to send a stream termination command to the client, where the stream termination command is used to terminate the reserved push stream of the second media data.

Optionally, the device further includes:

The ninth sending module is configured to send the push commitment of the second media data to the client after receiving the acquiring request of the first media data sent by the client;

And a tenth sending module, configured to send a stream termination command to the client, where the stream termination command is used to terminate the push stream reserved according to the push commitment that has not completed pushing the second media data.

Optionally, the device further includes:

The eleventh sending module is configured to: after the returning the first media data, and the push update response of the second media data to the client, send a push commitment of the third media data according to the push update response To the client;

The twelfth sending module is configured to push the third media data to the client according to the push commitment.

Optionally, the eighth sending module includes:

a third termination unit, configured to immediately send a flow termination command to the client in the push flow to terminate the push flow if an immediate termination flag exists in the push update indication;

a fourth termination unit, configured to: if the immediate termination flag does not exist in the push update indication, complete the second media data being pushed in the push stream to the client, and then send the stream in the push stream Terminating the command to the client, terminating the push stream.

In still another embodiment of the present invention, there is further provided a storage medium configured to store a computer program for performing the HTTP streaming media transmission method described above.

The embodiment of the present invention sends an acquisition request of the first media data to the server, where the acquisition request carries a push indication of the second media data, and receives the first media number returned by the server. And a push response of the second media data, and a push commitment of the second media data sent by the server according to the push response; sending a flow termination command to the server, the flow termination command is used to terminate the server according to the push commitment The reserved push stream of the second media data solves the problem that there is no effective HTTP streaming push update solution, and improves the push update mechanism in the HTTP streaming media transmission session.

DRAWINGS

The drawings described herein are intended to provide a further understanding of the invention, and are intended to be a part of the invention. In the drawing:

FIG. 1 is a schematic diagram of PULL mode transmission according to the related art HTTP streaming technology;

2 is a schematic diagram of PUSH mode transmission in an HTTP streaming media technology according to the related art;

3 is a flow chart 1 of HTTP streaming media transmission according to an embodiment of the present invention;

4 is a flow chart 2 of HTTP streaming media transmission according to an embodiment of the present invention;

FIG. 5 is a flowchart 3 of HTTP streaming media transmission according to an embodiment of the present invention;

6 is a flowchart 4 of HTTP streaming media transmission according to an embodiment of the present invention;

FIG. 7 is a structural block diagram 1 of an HTTP streaming media transmission apparatus according to an embodiment of the present invention;

FIG. 8 is a structural block diagram 2 of an HTTP streaming media transmission apparatus according to an embodiment of the present invention; FIG.

9 is a structural block diagram 3 of an HTTP streaming media transmission apparatus according to an embodiment of the present invention;

FIG. 10 is a structural block diagram 4 of an HTTP streaming media transmission apparatus according to an embodiment of the present invention; FIG.

FIG. 11 is a structural block diagram 5 of an HTTP streaming media transmission apparatus according to an embodiment of the present invention; FIG.

FIG. 12 is a structural block diagram 6 of an HTTP streaming media transmission apparatus according to an embodiment of the present invention; FIG.

FIG. 13 is a structural block diagram of an HTTP streaming media transmission apparatus according to an embodiment of the present invention. Seven;

FIG. 14 is a structural block diagram of an HTTP streaming media transmission apparatus according to an embodiment of the present invention; FIG.

FIG. 15 is a structural block diagram IX of an HTTP streaming media transmission apparatus according to an embodiment of the present invention; FIG.

FIG. 16 is a structural block diagram of an HTTP streaming media transmission apparatus according to an embodiment of the present invention; FIG.

FIG. 17 is a structural block diagram 11 of an HTTP streaming media transmission apparatus according to an embodiment of the present invention; FIG.

FIG. 18 is a block diagram showing the structure of an HTTP streaming media transmission apparatus according to an embodiment of the present invention; FIG.

FIG. 19 is a schematic diagram of an HTTP streaming media transmission system architecture according to an embodiment of the present invention; FIG.

20 is an interaction flowchart of implementing an HTTP streaming push session update based on a media segment cancel command according to a preferred embodiment of the present invention;

21 is a flow chart 1 of message interaction of an HTTP streaming media transmission method according to a preferred embodiment of the present invention;

22 is an interaction flowchart of implementing an HTTP streaming media push session update based on a media segment update command according to a preferred embodiment of the present invention;

23 is a second flow diagram of message interaction of another HTTP streaming media transmission method according to a preferred embodiment of the present invention;

FIG. 24 is a third flowchart of message interaction of another HTTP streaming media transmission method according to a preferred embodiment of the present invention; FIG.

FIG. 25 is a structural block diagram of an HTTP streaming media transmission apparatus according to an embodiment of the present invention.

detailed description

The invention will be described in detail below with reference to the drawings in conjunction with the embodiments. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict.

It is to be understood that the terms "first", "second" and the like in the specification and claims of the present invention are used to distinguish similar objects, and are not necessarily used to describe a particular order or order.

In this embodiment, an HTTP streaming media transmission method is provided. FIG. 3 is a flowchart 1 of HTTP streaming media transmission according to an embodiment of the present invention. As shown in FIG. 3, the process includes the following steps:

Step S302: Send an acquisition request of the first media data to the server, where the acquisition request carries a push indication of the second media data.

Step S304, receiving the first media data returned by the server, the push response of the second media data, and the push commitment of the second media data sent by the server according to the push response;

Step S306, sending a stream termination command to the server, the stream termination command is used to terminate the push stream of the second media data reserved by the server according to the push commitment.

Through the above steps, the problem that there is no effective HTTP streaming push update solution is solved, and the push update mechanism in the HTTP streaming media transfer session is improved.

In an embodiment of the present invention, after receiving the push commitment of the second media data sent by the server according to the push response, the method further includes:

Receiving the second media data that the server pushes according to the push commitment.

Sending a flow termination command to the server, the flow termination command is used to terminate the push flow reserved by the server according to the push commitment that has not completed pushing the second media data.

In an embodiment of the present invention, before the sending stream terminates the command to the server, setting an immediate termination flag value in the flow termination command, the immediate termination flag is used to instruct the server to immediately stop pushing the second in the push flow. Media data and terminate the push stream.

In an embodiment of the present invention, before the sending stream terminates the command to the server, at the end of the stream An immediate termination flag value is set in the stop command, the immediate termination flag is used to instruct the server to finish pushing the second media data in the push stream, and then terminating the push stream.

In this embodiment, an HTTP streaming media transmission method is also provided. FIG. 4 is a flowchart 2 of HTTP streaming media transmission according to an embodiment of the present invention. As shown in FIG. 4, the process includes the following steps:

Step S402, receiving an acquisition request of the first media data sent by the client, where the acquisition request carries a push indication of the second media data;

Step S404, returning the push response of the first media data and the second media data, and sending a push commitment of the second media data to the client according to the push response;

Step S406, receiving a stream termination command sent by the client, and terminating the push stream of the second media data reserved according to the push commitment according to the stream termination command.

Through the above steps, the problem that there is no effective HTTP streaming push update solution is solved, and the push update mechanism in the HTTP streaming media transfer session is improved.

In an embodiment of the present invention, after the push commitment of the second media data is sent to the client according to the push response, the second media data is pushed to the client according to the push commitment;

Receiving a flow termination command sent by the client, and terminating, according to the flow termination command, a push flow reserved according to the push commitment that has not completed pushing the second media data.

In an embodiment of the present invention, the pushing the flow of the second media data reserved according to the push commitment according to the flow termination command comprises:

If there is an immediate termination flag in the stream termination command, immediately stopping the pushing of the second media data in the push stream, and terminating the push stream;

If there is no immediate termination flag in the stream termination command, the second media data is pushed in the push stream, and then the push stream is terminated.

In this embodiment, an HTTP streaming media transmission method is also provided. FIG. 5 is a flowchart 3 of HTTP streaming media transmission according to an embodiment of the present invention. As shown in FIG. 5, the process includes the following steps:

Step S502: Send an acquisition request of the first media data to the server, where the acquisition request carries a push update indication of the second media data.

Step S504, receiving the first media data returned by the server, and a push update response of the second media data;

Step S506, receiving a stream termination command sent by the server, and terminating receiving the second media data pushed by the server according to the stream termination command.

Through the above steps, the problem that there is no effective HTTP streaming push update solution is solved, and the push update mechanism in the HTTP streaming media transfer session is improved.

In an embodiment of the present invention, after sending the acquisition request of the first media data to the server, receiving a push commitment of the second media data sent by the server;

Receiving a stream termination command sent by the server, and terminating receiving, according to the stream termination command, the second media data that the server has not completed pushing according to the push commitment.

In an embodiment of the present invention, after receiving the push update response of the second media data, receiving a push commitment of the third media data sent by the server according to the push update response;

Receiving the third media data that the server pushes according to the push commitment.

In this embodiment, an HTTP streaming media transmission method is also provided. FIG. 6 is a flowchart 4 of HTTP streaming media transmission according to an embodiment of the present invention. As shown in FIG. 6, the process includes the following steps:

Step S602, receiving an acquisition request of the first media data sent by the client, where the acquisition request carries a push update indication of the second media data;

Step S604, returning the first media data, and the push update response of the second media data to the client;

Step S606, sending a stream termination command to the client, the stream termination command is used to terminate the reserved push stream of the second media data.

Through the above steps, the problem that there is no effective HTTP streaming push update solution is solved, and the push update mechanism in the HTTP streaming media transfer session is improved.

In an embodiment of the present invention, after receiving the acquisition request of the first media data sent by the client, sending a push commitment of the second media data to the client; sending a flow termination command to the client, the flow termination command And a method for terminating a push flow that is reserved according to the push commitment and that has not completed pushing the second media data.

In an embodiment of the present invention, after returning the push update response of the second media data to the client, sending a push commitment of the third media data to the client according to the push update response; and pushing the first according to the push commitment Three media data to the client.

In an embodiment of the present invention, the sending stream terminates the command to the client, and the stream termination command is used to terminate the reserved push stream of the second media data, including: if the push update indication has an immediate termination flag, Immediately sending a stream termination command to the client in the push stream, terminating the push stream; if there is no immediate termination flag in the push update indication, completing the second media data being pushed in the push stream to the client, and then A stream termination command is sent to the client in the push stream to terminate the push stream.

An HTTP streaming media transmission device is also provided in this embodiment. The device is configured to implement the foregoing embodiments and preferred embodiments, and details are not described herein. As used below, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.

FIG. 7 is a block diagram of a structure of an HTTP streaming media transmission apparatus according to an embodiment of the present invention. As shown in FIG. 7, the apparatus is located in a terminal, and includes:

The first sending module 72 is configured to send an acquisition request of the first media data to the server, where the obtaining request carries a push indication of the second media data;

The first receiving module 74 is configured to receive the first media data returned by the server, a push response of the second media data, and a push commitment of the second media data sent by the server according to the push response;

The second sending module 76 is configured to send a stream termination command to the server, where the stream termination command is used to terminate the push stream of the second media data reserved by the server according to the push commitment.

Through the above device, the problem that there is no effective HTTP streaming push update solution is solved, and the push update mechanism in the HTTP streaming media transmission session is improved.

In the embodiment of the present invention, FIG. 8 is a block diagram of a structure of an HTTP streaming media transmission apparatus according to an embodiment of the present invention. In addition to the first sending module 72 and the first receiving module 74 of FIG. 7, the method further includes:

The second receiving module 82 is configured to receive the second media data that the server pushes according to the push commitment after receiving the push commitment of the second media data sent by the server according to the push response.

The third sending module 84 is configured to send a stream termination command to the server, where the stream termination command is used to terminate the push stream reserved by the server according to the push commitment that has not completed pushing the second media data.

In the embodiment of the present invention, FIG. 9 is a structural block diagram 3 of an HTTP streaming media transmission apparatus according to an embodiment of the present invention. In addition to the module of FIG. 7, the apparatus further includes:

The first setting module 92 is configured to set an immediate termination flag value in the flow termination command before the sending the flow termination command to the server, where the immediate termination flag is used to instruct the server to immediately stop pushing the second in the push flow. Media data and terminate the push stream.

In the embodiment of the present invention, FIG. 10 is a structural block diagram 4 of an HTTP streaming media transmission apparatus according to an embodiment of the present invention. In addition to the module of FIG. 7, the apparatus further includes:

The second setting module 102 is configured to set an immediate termination flag value in the flow termination command before the sending the flow termination command to the server, where the immediate termination flag is used to indicate that the server finishes pushing the second media in the push flow. Data, then terminate the push stream.

FIG. 11 is a block diagram 5 of a structure of an HTTP streaming media transmission apparatus according to an embodiment of the present invention. The device is located in a server, and includes:

The fourth receiving module 112 is configured to receive a request for acquiring the first media data sent by the client, where the obtaining request carries a push indication of the second media data;

The fourth sending module 114 is configured to return the first media data and the second media data. Pushing a response, and sending a push commitment of the second media data to the client according to the push response;

The fifth receiving module 116 is configured to receive a stream termination command sent by the client, and terminate the push stream of the second media data reserved according to the push commitment according to the stream termination command.

FIG. 12 is a structural block diagram 6 of an HTTP streaming media transmission apparatus according to an embodiment of the present invention. In addition to the fourth receiving module 112 and the fourth sending module 114 of FIG. 11, the method further includes:

The fifth sending module 122 is configured to: after sending the push commitment of the second media data to the client according to the push response, pushing the second media data to the client according to the push commitment;

The sixth receiving module 124 is configured to receive a flow termination command sent by the client, and terminate, according to the flow termination command, a push flow reserved according to the push commitment that has not completed pushing the second media data.

In the embodiment of the present invention, the fifth receiving module 116 includes:

a first termination unit, configured to immediately stop pushing the second media data in the push flow if the immediate termination flag exists in the flow termination command, and terminate the push flow;

The second terminating unit is configured to: if the instant termination flag does not exist in the stream termination command, complete the push of the second media data in the push stream, and then terminate the push stream.

FIG. 13 is a block diagram of a structure of an HTTP streaming media transmission apparatus according to an embodiment of the present invention. The device is located in the terminal, and includes:

The sixth sending module 132 is configured to send an acquisition request of the first media data to the server, where the obtaining request carries a push update indication of the second media data;

The seventh receiving module 134 is configured to receive the first media data returned by the server, and a push update response of the second media data;

The eighth receiving module 136 is configured to receive a stream termination command sent by the server, and terminate receiving the second media data pushed by the server according to the stream termination command.

In the embodiment of the present invention, FIG. 14 is a structural block diagram of an HTTP streaming media transmission apparatus according to an embodiment of the present invention. In addition to the sixth sending module 132 of FIG. 13, the method further includes:

The ninth receiving module 142 is configured to send the first media data acquisition request to the server. After receiving a push commitment of the second media data sent by the server;

The tenth receiving module 144 is configured to receive a stream termination command sent by the server, and terminate receiving, according to the stream termination command, the second media data that the server has not completed pushing according to the push commitment.

In the embodiment of the present invention, FIG. 15 is a structural block diagram 9 of an HTTP streaming media transmission apparatus according to an embodiment of the present invention. In addition to the sixth sending module 132 and the seventh receiving module 134 of FIG. 13, the method further includes:

The eleventh receiving module 152 is configured to receive, after receiving the push update response of the second media data, a push commitment of the third media data sent by the server according to the push update response;

The twelfth receiving module 154 is configured to receive the third media data that the server pushes according to the push commitment.

FIG. 16 is a structural block diagram of an HTTP streaming media transmission apparatus according to an embodiment of the present invention. The apparatus is located in a server, and includes:

The thirteenth receiving module 162 is configured to receive an acquisition request of the first media data sent by the client, where the obtaining request carries a push update indication of the second media data;

The seventh sending module 164 is configured to return the first media data, and the push update response of the second media data to the client;

The eighth sending module 166 is configured to send a stream termination command to the client, where the stream termination command is used to terminate the reserved push stream of the second media data.

In the embodiment of the present invention, FIG. 17 is a structural block diagram of an HTTP streaming media transmission apparatus according to an embodiment of the present invention. In addition to the thirteenth receiving module 162 of FIG. 16, the method further includes:

The ninth sending module 172 is configured to send a push commitment of the second media data to the client after receiving the first media data request sent by the receiving client;

The tenth sending module 174 is configured to send a stream termination command to the client, where the stream termination command is used to terminate the pushing of the second media data that is not completed according to the push commitment. flow.

In the embodiment of the present invention, FIG. 18 is a block diagram 12 of a structure of an HTTP streaming media transmission apparatus according to an embodiment of the present invention. In addition to the thirteenth receiving module 162 and the seventh transmitting module 164 of FIG. 16, the method further includes :

The eleventh sending module 182 is configured to: after the returning the first media data, and the push update response of the second media data to the client, send a push commitment of the third media data to the client according to the push update response ;

The twelfth sending module 184 is configured to push the third media data to the client according to the push commitment.

In the embodiment of the present invention, the eighth sending module 166 includes:

a third termination unit, configured to: if an immediate termination flag exists in the push update indication, immediately send a flow termination command to the client in the push flow, and terminate the push flow;

a fourth termination unit, configured to: if the immediate termination flag does not exist in the push update indication, complete the second media data being pushed in the push stream to the client, and then send a stream termination command to the client in the push stream End, terminate the push stream.

The invention will now be described in detail in conjunction with the preferred embodiments and embodiments.

A preferred embodiment of the present invention provides an HTTP streaming media transmission system. FIG. 19 is a schematic diagram of an HTTP streaming media transmission system architecture according to an embodiment of the present invention. As shown in FIG. 19, the terminal 100 includes a streaming media client. 200. The HTTP client 300 and its cache 310, the network 400, and the server 500 include an HTTP server 510 and a content source server 520. The system shown in Fig. 19 will be described below.

The terminal 100 provides a user-side hardware device of the running environment for the streaming media client 200. The deployment example of the terminal 100 may include: a set-top box, a desktop computer, a tablet computer, a smart phone, and the like;

The streaming media client 200 provides access, decoding, caching, and playback control for the streaming media resources in the server 500, including: a code rate adaptation module 210, a media playback engine 220, a push module 230, and a pull module 240.

The streaming client 200 instructs the HTTP client 300 to establish a media transport channel with the server 500, and the server 500 actively pushes streaming media data to the terminal 100 using the media channel. The media channel can be established through an HTTP/1.1 protocol upgrade mechanism. The streaming client 200 transmits a media segment or MPD file access request to the server 500 via the HTTP client 300. The media segment access request may carry a uniform resource identifier URI of the requested media segment and a “push policy” of the subsequent media segment. The "push policy" is used by the streaming client 200 to negotiate with the server 500 for the push mechanism of subsequent media segments. In addition to returning the requested media segment data, after receiving the media segment push request, the server 500 will return a push response according to the availability of the media segment and the local policy, once the streaming media client 200 and the server 500 reach a subsequent media segment "push strategy". Consistently, the server 500 will initiate a media segment push session to actively push subsequent available media segments to the terminal 100. The streaming client 200 can start playing the video content after buffering a sufficient amount of media segment data.

The rate adaptation module 210 detects the current available network bandwidth and the media segment buffer status in the media playback engine 220, performs a code rate adaptation algorithm, and sends a code rate switching indication to the push module 230 and the pull module 240.

The media playback engine 220 decodes the received media segments, media data buffers, and video playback controls.

The push module 230 initiates a session function based on the server supported by the HTTP 2.0 protocol, and requests the server 500 to push the streaming media resource to the terminal 100 through the HTTP client 300.

The pull module 240 requests the downloading of the streaming media resource in the server 500 to the terminal 100 through the HTTP client 300 based on the client initiated session function supported by the HTTP 1.1 protocol or the HTTP 2.0 protocol.

The HTTP client 300 includes: an HTTP/2 client and/or an HTTP/1.1 client. The HTTP client 300 sends an HTTP request to the server 500 according to the media segment access request of the internal push module 230 or the pull module 240 of the streaming media client 200 and the code rate switching instruction, and requests the acquisition of the server 500 that is most suitable for the current network bandwidth and the cache status. Streaming media resources. The cache 310 provides local storage of the media resources downloaded by the HTTP client 300.

The network 400 may include: a digital subscriber line (X Digital Subscriber Line, abbreviated as xDSL), a fiber-optic access (Fiber-to-the-x, referred to as FTTx), a cable communication cable, and the like, and a Wi-Fi network. A wireless communication network such as 2G, 3G, and Long Term Evolution (LTE).

The server 500 completes the generation of the slice of the original video and the generation of the MPD file. The content source 520 is responsible for content source capture, encoding compression, and segmentation processing, and divides the original video content into a plurality of video segments having a fixed time interval. The HTTP server 510 stores each video clip as an HTTP resource that is independently accessible by HTTP requests and responses, that is, a video file, and stores it in a hierarchy of periods, representations, and segments. Upon request, the HTTP server 510 will return the appropriate media shards to the terminal.

The server 500 also provides MPD file storage in dynamic adaptive streaming. The MPD file describes the duration, URL, media attributes of each media segment, such as video resolution, adaptation bit rate, and the like. The MPD file provides enough HTTP-URL information for the DASH client to access the streaming media content resource. When the DASH client starts playing a video, it selects the download according to the information in the MPD file to adapt to the currently available network bandwidth and the terminal. Cache the media clips and play them.

In the embodiment of the present invention, the adaptive streaming media (or dynamic adaptive streaming media) involved may be implemented in various manners, for example, dynamic adaptive streaming over HTTP (Dynamic Adaptive Streaming over HTTP) may be adopted. Referred to as DASH). The following takes DASH as an example to describe the MPD server and the streaming media server. The following embodiments are equally applicable to other adaptive streaming technologies.

In a preferred embodiment of the present invention, the HTTP streaming client sends a media segment cancel command to the HTTP streaming server, requesting the server to terminate pushing the media segment that is no longer needed, thereby implementing HTTP streaming push session update. The command includes two levels of processing: First, after receiving all the required media fragments, the client should first close the Request Stream initiated by it, so that the server does not continue to be in the request stream for those. The required media segment sends a push promise (PUSH_PROMISE); second, the client should also send Push Stream close request, close the push stream reserved by the server for media segments that are no longer needed. In addition, to avoid waste of bandwidth, the client may carry an indicator in the media segment cancel command to indicate whether the server continues to send the media segment that has been pushed when the cancel command is received before terminating the push session.

20 is an interaction flow diagram of implementing an HTTP streaming push session update based on a media segment cancel command in accordance with a preferred embodiment of the present invention. As shown in FIG. 20, the process includes the following steps:

Step 1: The client creates a request stream, and sends a media fragment acquisition request (get_segment) to the server according to the request stream, where the request carries a media fragment uniform resource identifier (segment_uri) parameter, which is used to specify the requested media. a fragment resource, a push-directive parameter, used to negotiate a media segment push policy in an HTTP streaming push session, and a scheme identifier parameter, which is used to identify a version of the scheme;

Step 2: The server returns the requested media segment (segment#i) to the client, and returns a push response (push_ack) parameter, completes the media segment push policy response in the HTTP streaming media push session, and the scheme identification parameter; The server will reserve a push stream for the media segments promised to be pushed in the push response;

Step 3 to step 4, the server pushes each media segment (segment#i+1~#i+j) to the client respectively according to the reserved push stream;

In step 5, the client sends a media segment cancel (segment_cancel) command to the server to request to update the HTTP streaming push session. Optionally, the cancel request carries an immediate parameter, where is used to indicate how the server processes the media segment being transmitted in the push stream when receiving the media segment cancel command;

Step 6. If the immediate parameter value is "true", the server immediately terminates the transmission of the media segment being pushed (segment#i+j+1) and cancels the push session, including: no longer sending the media segment push promise, and closing The push stream has been reserved; if the immediate parameter value is "false", the server will continue to transmit the media segment being pushed (segment#i+j+1), and then cancel the push session (as shown in this embodiment) .

21 is a message of an HTTP streaming media transmission method according to a preferred embodiment of the present invention. Interactive flow chart one.

Step 1: The client sends a first media segment acquisition request to the server using a standard HTTP GET message (a HEADERS frame in the HTTP/2 protocol). The "path" header field in the HTTP GET message is set as the first media segment uniform resource identifier URI, and is used to request the server to obtain the first media segment, that is, the path in the example in step 1: path="../rep1/ Segment1.mp4". In addition, the HTTP GET message also includes an "accept-push-policy" header field for requesting the server to push the second media segment, which is exemplified in step 1:

"accept-push-policy="urn:mpeg:dash:fdh:2015:push-template",

"../rep1/segment$Number$.mp4":{2-6}", which contains at least:

1) Push protocol scheme Uniform resource identifier (SchemeID) field, used to identify the push protocol version;

2) PushDirective, which is used to request the push policy executed in the push session, including:

Push type field, which is used to describe the type of the pushed media segment in the "push policy". For example, "push-next" indicates that a specific number of media segments are requested to be pushed, and "push-time" indicates that the push is requested. A media segment of a specific play time, "push-template" indicates that the media segment explicitly requested in the push template is requested.

And a push parameter (PushParams) field carrying the push parameter value of the pushed media segment in the "push policy".

In this embodiment, the client requests to acquire the "segment1" media segment in the representation "rep1" and requests to push the five media segments of the subsequent numbers "segment2" to "segment6" in "rep1".

Step 2: The server returns an HTTP 200 OK response message (HEADERS frame in the HTTP/2 protocol) as the first media segment acquisition response. The HTTP 200 OK response message includes an "accept-push-policy" header field for returning a second media segment push response, which is an example in the step 2: "accept-push-policy="urn:mpeg:dash:fdh :2015:push-template","../rep1/segment$Number$.mp4": {2-6}", at least:

1) Push protocol scheme Uniform resource identifier (SchemeID) field, used to identify the push protocol version;

2) Push response (PushAck), used to return the push policy received by the server in the push session, and carry the push type field and the push parameter field of the same type as the request.

In the present embodiment, the push response returned by the server indicates that the push commitment can be immediately transmitted for the five media segments of "segment2" to "segment6" in the "rep1" of the push indication requested to be pushed.

Steps 3 to 4: The server sends a push commitment message (HTTP/) based on the push parameter value returned by the push response in step 2 for each of the confirmed media segments (ie, 5 media segments of "segment2" to "segment6"). 2 PUSH_PROMISE frame in the protocol). The server sets the "path" header field in the PUSH_PROMISE frame to each of the acknowledged pushed media segment uniform resource identifier URIs, and transmits the PUSH_PROMISE frame in the request flow initiated by the client in step 1.

Step 5: The server returns the media segment requested by the client, that is, "../rep1/segment1.mp4" in this embodiment.

Steps 6-7: The server initiates a push stream for the media segment numbered "segment2" in "rep1", and pushes the media segment numbered "segment2" in "rep1" to the client.

Steps 8 to 10: The client no longer wishes to receive some media segments that are originally scheduled to be pushed, due to detection of a change in the currently available network bandwidth, or a media playback engine cache state. This embodiment assumes that the client no longer needs the server to push 4 media segments of "segment3" to "segment6". The client sends a stream reset (RST_STREAM) frame to the server for each media segment that no longer needs to be pushed, and sets the error code (Error Code) carried in the frame to "CANCEL (0x8)" to shut down the server. The push streams reserved for the four media segments of "segment3" through "segment6", that is, the push streams numbered Stream4, Stream6, Stream8, and Stream10.

Optionally, the client may set an “immediate” flag (Flag) for the stream reset frame, which is used to indicate how the server processes the push stream in the receive stream when receiving the stream reset frame. Media clips. The "instant" tag is defined as follows:

IMMEDIATE (0x1): Once the 0th bit is set, it indicates that the requester instructs the receiver to immediately close the stream referenced by the stream reset frame, terminating the ongoing data transmission in the stream. Otherwise, the receiver closes the stream after completing the data transfer.

It is assumed that in the embodiment, when the client sends a stream reset frame to the server, the "instant" flag is not set, and the server receives the stream reset frame in the stream stream of the Stream4 push, the server is pushing "segment3" in "rep1". To the client. According to the above description, the server will continue to push the media segment numbered "segment3" in "rep1" to the client in steps 9-10, and then close the push stream of the number Stream4.

Steps 11 to 12: After receiving the flow reset frame sent by the client, the server closes the push streams numbered Stream6, Stream8, and Stream10, and no longer pushes other media fragments to the client.

In a preferred embodiment of the present invention, the HTTP streaming client sends a media segment update command to the HTTP streaming server, requesting to renegotiate the push policy of the media segment, thereby implementing HTTP streaming media push session update. The client sends a media segment update request in the request flow initiated by the client, requesting the server to update the push policy in the push session; according to the renegotiation push policy, the server sends a push stream for the media segment that is no longer needed to be pushed (Push Stream) ) Close the request. At the same time, the server will also send a push commitment (PUSH_PROMISE) for the new media segment that needs to be pushed.

22 is an interaction flow diagram for implementing an HTTP streaming push session update based on a media segment update command in accordance with a preferred embodiment of the present invention. As shown in FIG. 22, the process includes the following steps:

Step 1: The client creates a request stream, and sends a media fragment acquisition request (get_segment) to the server according to the request stream, where the request carries a media fragment uniform resource identifier (segment_uri) parameter, which is used to specify the requested media. a fragment resource, a push-directive parameter, used to negotiate a media segment push policy in an HTTP streaming push session, and a scheme identifier parameter, which is used to identify a version of the scheme;

Step 2: The server returns the requested media segment (segment#i) to the client, and returns a push_ack parameter to complete the media segment in the HTTP streaming push session. Pushing a policy response, and a scenario identification parameter; during which the server will reserve a push stream for the media segment promised to be pushed in the push response;

Step 3 to step 4, the server pushes each media segment (segment#i+1~#i+j) to the client respectively according to the reserved push stream;

Step 5: The client sends a media segment update (segment_update) command to the server to request to update the HTTP streaming push session. Optionally, the cancel request carries an immediate parameter, where is used to indicate how the server processes the media segment being transmitted in the push stream when the media segment update command is received;

Step 6. If the value of the immediate parameter is "true", the server immediately terminates the transmission of the media segment being pushed (segment#i+j+1), and cancels the push session (as shown in this embodiment), including: no longer Send a media clip to push the promise and close the push stream that has been reserved; if the immediate parameter value is "false", the server will continue to transfer the media clip being pushed (segment#i+j+1), then cancel the push session .

FIG. 23 is a second flowchart of message interaction of another HTTP streaming media transmission method according to a preferred embodiment of the present invention.

Steps 1-7: The related execution steps in Figure 21 of the first embodiment are not repeated here.

Step 8: This embodiment assumes that the client requests the push session to push only the "segment2" media segment in "rep1", and does not push the media segments in the "rep1" number "segment3" to "segment6". The client sends a media segment push session update request to the server using a standard HTTP GET message (a HEADERS frame in the HTTP/2 protocol). The value of the "path" header field in the HTTP GET message remains unchanged, and is still the media fragment uniform resource identifier URI that is requested to be obtained, that is, path="../rep1/segment1.mp4" in the example in step 1. In addition, the HTTP GET message also contains an "accept-push-policy" header field for requesting the server to push the second media segment, ie, the example in step 8: "accept-push-policy="urn:mpeg:dash:fdh: 2015: push-update","../rep1/segment$Number$.mp4":{2}", at least:

1) Push Protocol Scheme Uniform Resource Identifier (SchemeID) field for identifying push Protocol version;

2) Push update directive (PushUpdateDirective), used to update the push policy executed in the push session, including:

Push type field, which is used to describe the type of the pushed media segment in the "push policy". For example, "push-next" indicates that a specific number of media segments are requested to be pushed, and "push-time" indicates that the push is requested. A media segment of a specific play time, "push-template" indicates that the media segment explicitly requested in the push template is requested.

And a push parameter (PushParams) field carrying the push parameter value of the pushed media segment in the "push policy".

The push type indicated by the push update indication is consistent with the push type of the push indication in the push session.

Optionally, the client may set an "immediate" field for the "accept-push-policy" header field to indicate how the server processes the media segment being transmitted in the push stream when receiving the push update request. Once the "instant" field is carried, the server should immediately terminate the ongoing data transfer in the push stream and close all push streams; otherwise, the server closes the push stream after completing the data transfer.

Step 9: The server returns an HTTP 200 OK response message (HEADERS frame in the HTTP/2 protocol) as a push session update response for the media segment. The HTTP 200 OK response message includes an "accept-push-policy" header field for returning a second media segment push response, which is an example in step 9: "accept-push-policy="urn:mpeg:dash:fdh :2015:push-update","../rep1/segment$Number$.mp4":{2}", at least:

1) Push protocol scheme Uniform resource identifier (SchemeID) field, used to identify the push protocol version;

2) Push update response (PushUpdateAck), used to return the push policy updated by the server in the push session, and carry the push type field and push parameter field of the same type as the push update request.

In this embodiment, the push update response returned by the server indicates that the media segment push session can be updated, and only the "segment2" in the "rep1" specified in the update response is pushed to the client.

Steps 10 to 11: The server sends a stream reset (RST_STREAM) frame to the client for each media segment that is no longer needed to be pushed, and sets an error code (Error Code) carried in the frame to “CANCEL (0x8)”. The push stream reserved for the media segments numbered "segment3" through "segment6", that is, the push streams numbered Stream4, Stream6, Stream8, and Stream10.

FIG. 24 is a third flowchart of message interaction of another HTTP streaming media transmission method according to a preferred embodiment of the present invention.

Steps 1-7: The related execution steps in Figure 21 of the first embodiment are not repeated here.

Step 8: This embodiment assumes that the client requests the push session to no longer push other media segments in "rep1", requesting to push the media segments numbered "segment3" to "segment6" in "rep2". The client sends a media segment push session update request to the server using a standard HTTP GET message (a HEADERS frame in the HTTP/2 protocol). The value of the "path" header field in the HTTP GET message remains unchanged, and is still the media fragment uniform resource identifier URI that is requested to be obtained, that is, path="../rep1/segment1.mp4" in the example in step 1. Similarly, the HTTP GET message contains an "accept-push-policy" header field for requesting the server to push the second media segment, ie, the example in step 8: "accept-push-policy="urn:mpeg:dash:fdh: 2015: push-update","../rep2/segment$Number$.mp4":{3-6}".

Optionally, the client may set an "immediate" field for the "accept-push-policy" header field to indicate how the server processes the media segment being transmitted in the push stream when receiving the push update request. Once the "instant" field is carried, the server should immediately terminate the ongoing data transfer in the push stream and close all push streams; otherwise, the server closes the push stream after completing the data transfer.

Step 9: The server returns an HTTP 200 OK response message (HEADERS frame in the HTTP/2 protocol) as a push session update response for the media segment. The HTTP 200 OK response message includes an "accept-push-policy" header for returning a second media segment push response. The domain, which is the example in step 9: "accept-push-policy="urn:mpeg:dash:fdh:2015:push-update","../rep1/segment$Number$.mp4":{2}" .

In this embodiment, the push update response returned by the server indicates that the other media segments in "rep1" are no longer pushed, and the media segments numbered "segment3" through "segment6" in "rep2" are pushed to the client.

Similar to the related steps in Figure 23, the server sends a stream reset (RST_STREAM) frame to the client for each media segment that no longer needs to be pushed, and closes the push stream reserved by the server for other media segments in "rep1".

Steps 10-11: According to the renegotiation push policy, the server sends a media segment push commitment to the client, and pushes the media segment numbered "segment3" to "segment6" in the "rep2" to the client based on the reserved push stream.

FIG. 25 is a structural block diagram of an HTTP streaming media transmission apparatus according to an embodiment of the present invention. As shown in FIG. 25, the apparatus includes an obtaining module 252, a first determining module 254, and a second determining module 256. The description will be made in accordance with the media stream processing device.

The obtaining module 252 is configured to obtain the location information and the time information of the adaptive streaming media carried in the transport stream. The first determining module 254 is connected to the acquiring module 252, and is configured to determine, according to the location information, the need for the adaptive streaming media. Transmitting a time-axis aligned media segment; the second determining module 256 is coupled to the first determining module 254, configured to determine, according to the time information, a media presentation time of the media segment in the adaptive streaming media relative to a time axis of the transport stream Timestamp.

Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation. Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk, CD-ROM, including a number of instructions to make a terminal device (available The method of the various embodiments of the present invention is performed by a mobile phone, a computer, a server, or a network device.

It should be noted that each of the above modules may be implemented by software or hardware. For the latter, the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the modules are located in multiple In the processor.

Embodiments of the present invention also provide a storage medium. Optionally, in the embodiment, the storage medium may be configured to store program code for performing the method steps of the above embodiment:

Optionally, the storage medium is further arranged to store program code for performing the method steps described above:

Optionally, in this embodiment, the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory. A variety of media that can store program code, such as a disc or a disc.

Optionally, in this embodiment, the processor performs the method steps of the foregoing embodiments according to the stored program code in the storage medium.

It will be apparent to those skilled in the art that the various modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.

The above description is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Industrial applicability

As described above, the HTTP streaming media transmission method and apparatus provided by the embodiments of the present invention have the following beneficial effects: solving the problem that an effective HTTP streaming media push update solution does not exist, and perfecting the HTTP streaming media transmission session. Push update mechanism.

Claims (29)

1. An HTTP streaming media transmission method includes:

   Sending an acquisition request of the first media data to the server, where the obtaining request carries a push indication of the second media data;

   Receiving, by the server, the first media data, a push response of the second media data, and a push commitment of the second media data sent by the server according to the push response;

   Sending a flow termination command to the server, the flow termination command is configured to terminate a push flow of the second media data reserved by the server according to the push commitment.
2. The method of claim 1, wherein after receiving the push commitment of the second media data sent by the server according to the push response, the method further comprises:

   Receiving, by the server, the second media data that is pushed according to the push commitment;

   Sending a flow termination command to the server, the flow termination command is configured to terminate a push flow reserved by the server according to the push commitment that has not completed pushing the second media data.
3. The method according to claim 1 or 2, wherein before the sending of the stream termination command to the server, the method further comprises:

   An immediate termination flag value is set in the flow termination command, the immediate termination flag is used to instruct the server to immediately stop pushing the second media data in the push flow, and terminate the push flow.
4. The method according to claim 1 or 2, wherein before the sending of the stream termination command to the server, the method further comprises:

   And setting an immediate termination flag value in the flow termination command, the immediate termination flag is used to instruct the server to complete pushing the second media data in the push flow, and then terminating the push flow.
5. An HTTP streaming media transmission method includes:

   Receiving an acquisition request of the first media data sent by the client, where the obtaining request carries Push indication with second media data;

   Returning a push response of the first media data and the second media data, and sending a push commitment of the second media data to the client according to the push response;

   Receiving a stream termination command sent by the client, and terminating, according to the stream termination command, a push stream of the second media data reserved according to the push commitment.
6. The method of claim 5, wherein after the sending of the push commitment of the second media data to the client according to the push response, the method further comprises:

   Pushing the second media data to the client according to the push commitment;

   Receiving a flow termination command sent by the client, and terminating, according to the flow termination command, a push flow reserved according to the push commitment that has not completed pushing the second media data.
7. The method according to claim 5 or 6, wherein the terminating the push stream of the second media data reserved according to the push commitment according to the stream termination command comprises:

   If there is an immediate termination flag in the stream termination command, immediately stopping pushing the second media data in the push stream, and terminating the push stream;

   If there is no immediate termination flag in the stream termination command, the second media data is pushed in the push stream, and then the push stream is terminated.
8. An HTTP streaming media transmission method includes:

   Sending an acquisition request of the first media data to the server, where the obtaining request carries a push update indication of the second media data;

   Receiving, by the server, the first media data returned by the server, and a push update response of the second media data;

   Receiving a stream termination command sent by the server, and terminating receiving the second media data pushed by the server according to the stream termination command.
9. The method of claim 8, wherein after the sending the acquisition request of the first media data to the server, the method further comprises:

   Receiving a push commitment of the second media data sent by the server;

   Receiving a stream termination command sent by the server, and terminating receiving, according to the stream termination command, the second media data that the server has not completed pushing according to the push commitment.
10. The method of claim 8 or 9, wherein after receiving the push update response of the second media data, the method further comprises:

    Receiving a push commitment of the third media data sent by the server according to the push update response;

    Receiving, by the server, the third media data that is pushed according to the push commitment.
11. An HTTP streaming media transmission method includes:

    Receiving an acquisition request of the first media data sent by the client, where the obtaining request carries a push update indication of the second media data;

    Returning the first media data, and the push update response of the second media data to the client;

    Sending a stream termination command to the client, the stream termination command is used to terminate the reserved push stream of the second media data.
12. The method according to claim 11, wherein after the receiving the acquisition request of the first media data sent by the client, the method further comprises:

    Sending a push commitment of the second media data to the client;

    Sending a flow termination command to the client, the flow termination command is configured to terminate a push flow reserved according to the push commitment that has not completed pushing the second media data.
13. The method according to claim 11 or 12, wherein after the returning the push update response of the second media data to the client, the method further comprises:

    Sending a push commitment of the third media data to the client according to the push update response;

    Pushing the third media data to the client according to the push commitment.
14. The method according to claim 11 or 12, wherein said sending a stream termination command to said client, said stream termination command is for terminating said reserved second number of media The push stream is based on:

    If there is an immediate termination flag in the push update indication, immediately send a stream termination command to the client in the push stream to terminate the push stream;

    If the immediate termination flag does not exist in the push update indication, completing the second media data being pushed in the push stream to the client, and then sending a stream termination command to the client in the push stream Ending the push stream.
15. An HTTP streaming media transmission device is located in the terminal and includes:

    The first sending module is configured to send an acquisition request of the first media data to the server, where the obtaining request carries a push indication of the second media data;

    a first receiving module, configured to receive the first media data returned by the server, a push response of the second media data, and a push commitment of the second media data sent by the server according to the push response ;

    And a second sending module, configured to send a stream termination command to the server, where the stream termination command is used to terminate the push stream of the second media data reserved by the server according to the push commitment.
16. The apparatus of claim 15 wherein said apparatus further comprises:

    The second receiving module is configured to receive, after receiving the push commitment of the second media data sent by the server according to the push response, the second media data that is sent by the server according to the push commitment;

    And a third sending module, configured to send a flow termination command to the server, where the flow termination command is used to terminate a push flow reserved by the server according to the push commitment that has not completed pushing the second media data.
17. The device according to claim 15 or 16, wherein the device further comprises:

    a first setting module, configured to set an immediate termination flag value in the flow termination command before the sending a flow termination command to the server, where the immediate termination flag is used to indicate that the server is immediately in the push flow Stop pushing the second media data and end Stop the push flow.
18. The device according to claim 15 or 16, wherein the device further comprises:

    a second setting module, configured to set an immediate termination flag value in the flow termination command before the sending a flow termination command to the server, where the immediate termination flag is used to indicate that the server is completed in the push flow Pushing the second media data and then terminating the push stream.
19. An HTTP streaming media transmission device, located in a server, comprising:

    The fourth receiving module is configured to receive a request for acquiring the first media data sent by the client, where the acquiring request carries a push indication of the second media data;

    a fourth sending module, configured to return a push response of the first media data and the second media data, and send a push commitment of the second media data to the client according to the push response;

    The fifth receiving module is configured to receive a stream termination command sent by the client, and terminate the push stream of the second media data reserved according to the push commitment according to the stream termination command.
20. The device of claim 19, wherein the device further comprises:

    The fifth sending module is configured to: after sending the push commitment of the second media data to the client according to the push response, pushing the second media data to the client according to the push commitment;

    And a sixth receiving module, configured to receive a flow termination command sent by the client, and terminate, according to the flow termination command, a push flow reserved according to the push commitment that has not completed pushing the second media data.
21. The apparatus according to claim 19 or 20, wherein the fifth receiving module comprises:

    a first termination unit, configured to immediately stop pushing the second media data in the push flow if the immediate termination flag exists in the flow termination command, and terminate the push flow;

    And a second terminating unit configured to: if the instant termination flag does not exist in the stream termination command, complete the pushing of the second media data in the push stream, and then terminate the push stream.
22. An HTTP streaming media transmission device is located in the terminal and includes:

    a sixth sending module, configured to send an acquisition request of the first media data to the server, where the obtaining request carries a push update indication of the second media data;

    a seventh receiving module, configured to receive the first media data returned by the server, and a push update response of the second media data;

    The eighth receiving module is configured to receive a stream termination command sent by the server, and terminate receiving the second media data pushed by the server according to the stream termination command.
23. The device of claim 22, wherein the device further comprises:

    a ninth receiving module, configured to receive a push commitment of the second media data sent by the server, after the sending the sending request of the first media data to the server;

    The tenth receiving module is configured to receive a stream termination command sent by the server, and terminate receiving, according to the stream termination command, the second media data that the server has not completed pushing according to the push commitment.
24. The device according to claim 22 or 23, wherein the device further comprises:

    The eleventh receiving module is configured to receive, after receiving the push update response of the second media data, a push commitment of the third media data sent by the server according to the push update response;

    The twelfth receiving module is configured to receive the third media data that is pushed by the server according to the push commitment.
25. An HTTP streaming media transmission device, located in a server, comprising:

    a thirteenth receiving module, configured to receive a request for acquiring the first media data sent by the client, where the obtaining request carries a push update indication of the second media data;

    a seventh sending module, configured to return the first media data, and the second media Push update response of the volume data to the client;

    And an eighth sending module, configured to send a stream termination command to the client, where the stream termination command is used to terminate the reserved push stream of the second media data.
26. The device of claim 25, wherein the device further comprises:

    The ninth sending module is configured to send the push commitment of the second media data to the client after receiving the acquiring request of the first media data sent by the client;

    And a tenth sending module, configured to send a stream termination command to the client, where the stream termination command is used to terminate the push stream reserved according to the push commitment that has not completed pushing the second media data.
27. The device of claim 25 or 26, wherein the device further comprises:

    The eleventh sending module is configured to: after the returning the first media data, and the push update response of the second media data to the client, send a push commitment of the third media data according to the push update response To the client;

    The twelfth sending module is configured to push the third media data to the client according to the push commitment.
28. The apparatus according to claim 25 or 26, wherein said eighth transmitting module comprises:

    a third termination unit, configured to immediately send a flow termination command to the client in the push flow to terminate the push flow if an immediate termination flag exists in the push update indication;

    a fourth termination unit, configured to: if the immediate termination flag does not exist in the push update indication, complete the second media data being pushed in the push stream to the client, and then send the stream in the push stream Terminating the command to the client, terminating the push stream.
29. A storage medium arranged to store a computer program for performing the HTTP streaming media transmission method according to any one of claims 1 to 14.

Images