WO2017114393A1 - Procédé et dispositif de transmission de contenu multimédia de diffusion en continu http - Google Patents

Procédé et dispositif de transmission de contenu multimédia de diffusion en continu http Download PDF

Info

Publication number
WO2017114393A1
WO2017114393A1 PCT/CN2016/112430 CN2016112430W WO2017114393A1 WO 2017114393 A1 WO2017114393 A1 WO 2017114393A1 CN 2016112430 W CN2016112430 W CN 2016112430W WO 2017114393 A1 WO2017114393 A1 WO 2017114393A1
Authority
WO
WIPO (PCT)
Prior art keywords
push
media data
server
stream
client
Prior art date
Application number
PCT/CN2016/112430
Other languages
English (en)
Chinese (zh)
Inventor
黄成�
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2017114393A1 publication Critical patent/WO2017114393A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/65—Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/55—Push-based network services

Definitions

  • the present invention relates to the field of communications, and in particular to an HTTP streaming media transmission method and apparatus.
  • HTTP streaming media 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 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.
  • URL Uniform Resource Locator
  • the client 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.
  • 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;
  • CDN Content Delivery Network
  • 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.
  • HTTP 2.0 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.
  • Push Strategy media segment push strategy
  • 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.
  • an HTTP streaming media transmission method including:
  • 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.
  • the method further includes:
  • 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.
  • the method 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.
  • the method before the sending a flow termination command to the server, the method further includes:
  • 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.
  • an HTTP streaming media transmission method including:
  • the method further includes:
  • 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:
  • the second media data is pushed in the push stream, and then the push stream is terminated.
  • an HTTP streaming media transmission method including:
  • the method further includes:
  • the method further includes:
  • an HTTP streaming media transmission method including:
  • the stream termination command is used to terminate the reserved push stream of the second media data.
  • the method further includes:
  • 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.
  • the method further includes:
  • 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:
  • 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.
  • 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 ;
  • 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.
  • 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;
  • 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.
  • 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.
  • 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.
  • 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.
  • 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;
  • 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.
  • 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;
  • 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.
  • 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.
  • 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.
  • 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.
  • 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;
  • 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.
  • 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;
  • 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.
  • 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.
  • 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.
  • 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.
  • FIG. 1 is a schematic diagram of PULL mode transmission according to the related art HTTP streaming technology
  • FIG. 2 is a schematic diagram of PUSH mode transmission in an HTTP streaming media technology according to the related art
  • FIG. 3 is a flow chart 1 of HTTP streaming media transmission according to an embodiment of the present invention.
  • FIG. 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.
  • FIG. 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. 11 is a structural block diagram 5 of an HTTP streaming media transmission apparatus according to an embodiment of the present invention.
  • FIG. 12 is a structural block diagram 6 of an HTTP streaming media transmission apparatus according to an embodiment of the present invention.
  • 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. 15 is a structural block diagram IX of an HTTP streaming media transmission apparatus according to an embodiment of the present invention.
  • FIG. 16 is a structural block diagram of an HTTP streaming media transmission apparatus according to an embodiment of the present invention.
  • FIG. 17 is a structural block diagram 11 of an HTTP streaming media transmission apparatus according to an embodiment of the present invention.
  • 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. 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.
  • FIG. 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
  • FIG. 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. 25 is a structural block diagram of an HTTP streaming media transmission apparatus according to an embodiment of the present invention.
  • 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.
  • the method after receiving the push commitment of the second media data sent by the server according to the push response, the method further includes:
  • 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.
  • 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.
  • 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.
  • 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.
  • the second media data is pushed to the client according to the push commitment
  • the pushing the flow of the second media data reserved according to the push commitment according to the flow termination command comprises:
  • the second media data is pushed in the push stream, and then the push stream is terminated.
  • 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.
  • 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.
  • 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.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • 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.
  • FIG. 8 is a block diagram of a structure of an HTTP streaming media transmission apparatus according to an embodiment of the present invention.
  • 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.
  • FIG. 9 is a structural block diagram 3 of an HTTP streaming media transmission apparatus according to an embodiment of the present invention.
  • 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.
  • FIG. 10 is a structural block diagram 4 of an HTTP streaming media transmission apparatus according to an embodiment of the present invention.
  • 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.
  • 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.
  • 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.
  • FIG. 14 is a structural block diagram of an HTTP streaming media transmission apparatus according to an embodiment of the present invention.
  • 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.
  • FIG. 15 is a structural block diagram 9 of an HTTP streaming media transmission apparatus according to an embodiment of the present invention.
  • 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.
  • FIG. 17 is a structural block diagram of an HTTP streaming media transmission apparatus according to an embodiment of the present invention.
  • 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.
  • 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.
  • 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.
  • 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.
  • FIG. 19 is a schematic diagram of an HTTP streaming media transmission system architecture according to an embodiment of the present invention.
  • 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.
  • the server 500 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.
  • 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.
  • XDSL Digital Subscriber Line
  • FTTx fiber-optic access
  • cable communication cable and the like
  • Wi-Fi network a wireless communication network such as 2G, 3G, and Long Term Evolution (LTE).
  • LTE Long Term Evolution
  • 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.
  • 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.
  • 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.
  • DASH Dynamic Adaptive Streaming over HTTP
  • 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.
  • 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.
  • FIG. 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;
  • step 5 the client sends a media segment cancel (segment_cancel) command to the server to request to update the HTTP streaming push session.
  • 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 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:
  • 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.
  • PushParams a push parameter carrying the push parameter value of the pushed media segment in the "push policy”.
  • 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.
  • Push response 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.
  • 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.
  • HTTP/ push commitment message
  • 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 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.
  • Flag immediateate flag
  • 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.
  • the server 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.
  • 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.
  • the server will also send a push commitment (PUSH_PROMISE) for the new media segment that needs to be pushed.
  • FIG. 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.
  • 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).
  • 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.
  • PushParams a push parameter 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.
  • 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.
  • 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.
  • 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.
  • 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)”.
  • RST_STREAM stream reset
  • Error Code error code carried in the frame to “CANCEL (0x8)”.
  • 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 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.
  • 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 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.
  • 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".
  • RST_STREAM stream reset
  • 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.
  • 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.
  • 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).
  • 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.
  • each of the above modules may be implemented by software or hardware.
  • 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.
  • the storage medium may be configured to store program code for performing the method steps of the above embodiment:
  • the storage medium is further arranged to store program code for performing the method steps described above:
  • 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.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • a mobile hard disk e.g., a hard disk
  • magnetic memory e.g., a hard disk
  • the processor performs the method steps of the foregoing embodiments according to the stored program code in the storage medium.
  • 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.
  • the invention is not limited to any specific combination of hardware and software.
  • 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.

Abstract

L'invention concerne un procédé et un dispositif de transmission de contenu multimédia de diffusion en continu HTTP. Le procédé comprend les étapes suivantes : envoyer une requête d'acquisition de premières données multimédias à un serveur, la requête d'acquisition transportant une instruction de pousser de secondes données multimédias; recevoir les premières données multimédias renvoyées par le serveur, une réponse de pousser des secondes données multimédias, et un engagement de pousser des secondes données multimédias envoyé par le serveur selon la réponse de pousser; et envoyer une instruction de terminaison de flux au serveur, l'instruction de terminaison de flux étant utilisée pour terminer un flux de pousser des secondes données multimédias réservées par le serveur selon l'engagement de pousser, de telle sorte que le mécanisme de mise à jour de pousser dans une session de transmission de contenu multimédia de diffusion en continu HTTP est amélioré. Le problème selon lequel il n'y a pas de solution efficace pour une mise à jour de pousser de contenu multimédia de diffusion en continu HTTP est résolu.
PCT/CN2016/112430 2015-12-31 2016-12-27 Procédé et dispositif de transmission de contenu multimédia de diffusion en continu http WO2017114393A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201511033565.0 2015-12-31
CN201511033565.0A CN106936808B (zh) 2015-12-31 2015-12-31 Http流媒体传输方法及装置

Publications (1)

Publication Number Publication Date
WO2017114393A1 true WO2017114393A1 (fr) 2017-07-06

Family

ID=59224571

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/112430 WO2017114393A1 (fr) 2015-12-31 2016-12-27 Procédé et dispositif de transmission de contenu multimédia de diffusion en continu http

Country Status (2)

Country Link
CN (1) CN106936808B (fr)
WO (1) WO2017114393A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111654725B (zh) * 2019-03-04 2021-12-21 北京开广信息技术有限公司 媒体流的实时接收方法及客户端

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150032804A1 (en) * 2013-07-26 2015-01-29 Canon Kabushiki Kaisha Method and server device for exchanging information items with a plurality of client entities
GB2517060A (en) * 2013-07-12 2015-02-11 Canon Kk Adaptive data streaming method with push messages control
CN104408132A (zh) * 2014-11-28 2015-03-11 北京京东尚科信息技术有限公司 数据推送方法和系统
CN104704485A (zh) * 2012-07-19 2015-06-10 格兰斯电讯网络有限公司 协同浏览与其他形式的信息共享的集成
GB2527149A (en) * 2014-06-12 2015-12-16 Canon Kk Improved adaptative persistent push

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2784233C (fr) * 2010-01-18 2017-05-16 Telefonaktiebolaget L M Ericsson (Publ) Procedes et agencements pour distribution de flux multimedia http
US9813515B2 (en) * 2013-10-04 2017-11-07 Akamai Technologies, Inc. Systems and methods for caching content with notification-based invalidation with extension to clients
CN103716371A (zh) * 2013-10-31 2014-04-09 国家电网公司 一种Web实时数据主动推送方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104704485A (zh) * 2012-07-19 2015-06-10 格兰斯电讯网络有限公司 协同浏览与其他形式的信息共享的集成
GB2517060A (en) * 2013-07-12 2015-02-11 Canon Kk Adaptive data streaming method with push messages control
US20150032804A1 (en) * 2013-07-26 2015-01-29 Canon Kabushiki Kaisha Method and server device for exchanging information items with a plurality of client entities
GB2527149A (en) * 2014-06-12 2015-12-16 Canon Kk Improved adaptative persistent push
CN104408132A (zh) * 2014-11-28 2015-03-11 北京京东尚科信息技术有限公司 数据推送方法和系统

Also Published As

Publication number Publication date
CN106936808B (zh) 2021-01-26
CN106936808A (zh) 2017-07-07

Similar Documents

Publication Publication Date Title
EP2797287B1 (fr) Procédé et appareil de support de lecture à décalage temporel dans une solution de transmission en continu HTTP adaptative
US10263875B2 (en) Real-time processing capability based quality adaptation
US8516144B2 (en) Startup bitrate in adaptive bitrate streaming
US9596522B2 (en) Fragmented file structure for live media stream delivery
US20140032777A1 (en) Method, apparatus, and system for transmitting and processing media content
US20130013803A1 (en) Method for recovering content streamed into chunk
CN108063769B (zh) 一种内容服务的实现方法、装置及内容分发网络节点
CN107124668B (zh) 流式传输装置及方法、流式传输服务系统及记录介质
CN107819809B (zh) 对内容进行同步操作的方法及装置
EP2493191B1 (fr) Procédé, dispositif et système permettant de réaliser une demande hiérarchique de contenu dans un système de diffusion http
CN109587514B (zh) 一种视频播放方法、介质和相关装置
US10958972B2 (en) Channel change method and apparatus
BR112014013006B1 (pt) Dispositivo e método para obter conteúdo por pelo menos dois protocolos de transporte tendo diferentes requisitos em termos de largura de banda de rede disponível
JP6436772B2 (ja) 受信ビットレートの動的適応方法および関連する受信機
EP3047627B1 (fr) Adaptations de représentations dash dans des réseaux
US20110299586A1 (en) Quality adjustment using a fragmented media stream
KR20130005873A (ko) 방송 시스템에서 컨텐츠 수신 방법 및 장치
WO2017063574A1 (fr) Procédé et dispositif de transmission adaptative de données multimédias diffusées en continu
JP6359539B2 (ja) レンダリング時の制御
EP3391652A1 (fr) Commande d'extraction dans une diffusion en continu adaptative
KR20170141677A (ko) 수신 장치, 송신 장치 및 데이터 처리 방법
EP2477397A1 (fr) Gestion de l'initialisation d'une diffusion en flux HTTP de fichiers multimédia par des connexions TCP parallèles
JP2014090419A (ja) 通信パラメータに従ってコンテンツをダウンロードするための方法、および、関連するコンテンツ受信機
WO2012041039A1 (fr) Procédé, équipement corrélatif et système d'accès par un terminal de télévision numérique à la vidéo sur internet
WO2017114393A1 (fr) Procédé et dispositif de transmission de contenu multimédia de diffusion en continu http

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16881182

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16881182

Country of ref document: EP

Kind code of ref document: A1