WO2018028986A1 - Diffusion en continu à débit binaire adaptatif amélioré de contenu en direct - Google Patents

Diffusion en continu à débit binaire adaptatif amélioré de contenu en direct Download PDF

Info

Publication number
WO2018028986A1
WO2018028986A1 PCT/EP2017/068868 EP2017068868W WO2018028986A1 WO 2018028986 A1 WO2018028986 A1 WO 2018028986A1 EP 2017068868 W EP2017068868 W EP 2017068868W WO 2018028986 A1 WO2018028986 A1 WO 2018028986A1
Authority
WO
WIPO (PCT)
Prior art keywords
manifest
file
client device
segment
update hint
Prior art date
Application number
PCT/EP2017/068868
Other languages
English (en)
Inventor
Anthony Jones
Chris Phillips
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to DK17745318.0T priority Critical patent/DK3497831T3/da
Priority to EP17745318.0A priority patent/EP3497831B1/fr
Priority to EP21192201.8A priority patent/EP3930234B1/fr
Priority to ES17745318T priority patent/ES2896803T3/es
Priority to US16/324,465 priority patent/US10911508B2/en
Publication of WO2018028986A1 publication Critical patent/WO2018028986A1/fr
Priority to US17/144,440 priority patent/US11283849B2/en
Priority to US17/683,710 priority patent/US11778012B2/en

Links

Classifications

    • 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/75—Media network packet handling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0015—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the adaptation strategy
    • H04L1/0017—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the adaptation strategy where the mode-switching is based on Quality of Service requirement
    • H04L1/0018—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the adaptation strategy where the mode-switching is based on Quality of Service requirement based on latency requirement
    • 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/10—Architectures or entities
    • H04L65/1059—End-user terminal functionalities specially adapted for real-time communication
    • 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/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
    • H04L65/612—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
    • 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/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
    • H04L65/613—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for the control of the source by the destination
    • 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
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/70—Media network packetisation
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0014—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the source coding

Definitions

  • the present application relates to a client device, a method in a client device, a server, a method in a server, an encoder, a method of operating an encoder, a packager, a method of operating a packager, an apparatus for receiving a live adaptive bitrate stream, an apparatus for delivering a live adaptive bitrate stream, and a computer-readable medium.
  • Adaptive bitrate (ABR) streaming has become an important technology for delivering video content over an internet connection.
  • This technology allows for a variation in bandwidth which is typical for a home internet connection. This variation may be due to local contention with other devices and users in the home using the same modem connection for other purposes.
  • a further cause for the variation in available bandwidth is local loop contention where the bandwidth between a plurality of modems in a neighborhood must be shared between a respective plurality of homes.
  • ABR streaming allows for a variation in bandwidth by measuring the available bandwidth between a streaming device and a server that is sending the streamed video content, and providing the video stream at a bit rate that maximizes the use of the available bandwidth.
  • a server that uses ABR will make the streamed video available in a series of segments, with each segment available in multiple versions, each version encoded at a different bit rate.
  • the ABR streaming client in the streaming device selects the appropriate segments.
  • the available bit rates are normally fixed.
  • the server makes a manifest file available to ABR streaming clients.
  • the manifest file lists the segments of the video stream that the server has available for download.
  • a streaming client must first download the manifest file before it can identify which segments to download.
  • the streaming client requests the appropriate segments and once it receives these it can begin decoding and presenting the content.
  • Adaptive Bit Rate (ABR) streaming using HTTP Adaptive Streaming (HAS) is increasingly used as a format for live operation. That is, delivery of live video content. Live content may be defined as 'not pre-recorded'. Live content can be considered to be content that is generated and substantially immediately distributed to a client device.
  • HTTP Adaptive Streaming was developed originally with on-demand content in mind, where all the segments are known before streaming begins. This means that all manifests, which describe the segments of a piece of content, are available for a client to download when streaming of that piece of content begins. When a client requests a manifest related to on-demand content, that manifest will be available for that client.
  • manifest files must be created as the segments related to the live content are created. If a client requests an updated manifest file before it has been created, it will not receive the file, and will have to re- request it a short time later. However, the client has no way of knowing when the updated manifest file will be available. For example, in live operation, HAS manifest files are updated each time a new complete segment of media data is available. The time interval between new segments becoming available is unlikely to be constant as it will depend on the content and encoding complexity.
  • the client polls the server to download the server's current manifest. If a poll comes in immediately before the manifest is updated, so the poll just misses the update, then the client will have to wait until the next poll to receive the new manifest. This results in a significant and variable latency between the availability of new media segments and when the client is aware of them. This latency can be up to a complete poll interval (typically several seconds). This in turn leads to more difficult buffering and in the presence of congestion or limited bandwidth can lead to client playback stalling or excessively changing bit rates. When the segment sizes are widely variable (for example due to advertising), the impairments are even more significant.
  • the updated manifest will likely include segments that were listed on the previous manifest, hence it is aptly referred to as an update. However, in practice this is a new file, and so the updated manifest can be referred to as a new manifest file, or a new manifest. Herein it will be referred to as an updated manifest.
  • a client device arranged to receive a live adaptive bitrate stream, the client device further arranged to: request a manifest file; and request a manifest update hint.
  • the client device further arranged to receive a manifest update hint, the manifest update hint including an indication of when the manifest will be updated; and request an updated manifest file at a time indicated by the manifest update hint.
  • the manifest update hint indicates to the client device when it can expect a manifest update to occur.
  • the client device uses this hint to time when it requests an updated manifest file. Operating in this way, the client device is less likely to request a manifest file prematurely; such requests are unnecessary signaling overhead. Furthermore, the client device will consistently download an updated manifest file promptly after it is made available, allowing for better buffering and smoother playback of live content received via the streaming service.
  • the time indicated by the manifest update hint may be a time interval or specific time mentioned in the manifest update hint, plus a delay.
  • the delay may be selected by the client device.
  • a splice point may occur in the content stream at a point requiring a shorter than usual segment. For example: consider an encoder configured to generate 10 second segments; a splice point notice is received resulting in the encoder generating a shorter segment, such as 4 seconds. The client has been polling at appropriately timed 10 second intervals. The shorter segment means that now the polling has an offset from both the segment generation and when the updated manifest is created.
  • the manifest update hint described herein allows the client to keep in sync with the segmenter even when segment lengths change.
  • a splice point may be indicated by an SCTE 35 message.
  • ANSI/SCTE 35 2013 is a joint ANSI/Society of Cable and Telecommunications Engineers standard that describes the inline insertion of cue tones in mpeg transport streams. This is used in broadcasting to insert a local advert or news segment into a nationally broadcast stream.
  • the live adaptive bitrate stream contains live content.
  • Live content is content that is received at the streaming system shortly before being sent to clients. A delay may occur, resulting from the time taken to process incoming data into a form ready for live adaptive bitrate streaming.
  • the live adaptive bitrate stream may comprise video content.
  • the manifest update hint may be contained within the manifest file.
  • the client device is arranged to receive a live adaptive bitrate stream, the client device further arranged to: request a manifest file; receive a manifest update hint, the manifest update hint including an indication of when the manifest will be updated; and request an updated manifest file at a time indicated by the manifest update hint.
  • a method in a client device arranged to receive a live adaptive bitrate stream comprising: requesting a manifest file; and requesting a manifest update hint.
  • the method further comprises receiving a manifest update hint, the manifest update hint including an indication of when the manifest will be updated; and requesting an updated manifest file at a time indicated by the manifest update hint.
  • the manifest update hint indicates to the client device when it can expect a manifest update to occur.
  • the client device uses this hint to schedule when it requests an updated manifest file. Operating in this way, the client device is less likely to request a manifest file prematurely; such premature requests are unnecessary signaling overhead.
  • the client device will consistently download an updated manifest file promptly after it is made available, allowing for better buffering and smoother playback of live content received via the streaming service.
  • the time indicated by the manifest update hint may be a time interval or specific time mentioned in the manifest update hint, plus a delay.
  • the method may further comprise selecting the delay.
  • a server arranged to deliver a live adaptive bitrate stream, the server arranged to: receive a video stream and generate adaptive bitrate segments for delivery to at least one client device; and calculate the size of a segment being generated before the segment is completed.
  • the server is further arranged to create a manifest update hint file on the basis of the calculated size of the next segment; and send the manifest update hint file in response to a request for such from a client device.
  • a server that is encoding live content for delivery by adaptive bitrate streaming will determine the size of a segment early on in the encoding of such a segment.
  • the length of the segment determines when it will be ready for download by a client device, and accordingly when the manifest file will be updated to reflect that the segment is ready for download.
  • the server can generate a manifest update hint file in advance of the new manifest file being available, the manifest update hint file giving a useful indication to client devices of when the manifest file will be updated.
  • the server may be arranged to: receive a request for a manifest file from the client device; and send the current manifest file to the client device.
  • the server will receive a request for the updated manifest file, that request may be timed by the client device to arrive at the server at a time soon after the manifest file has been updated, that time determined from the indication given in the manifest update hint file.
  • the server sends the currently available manifest file to the client device.
  • a server that is encoding live content for delivery by adaptive bitrate streaming will determine the size of a segment early on in the encoding of such a segment.
  • the length of the segment determines when it will be ready for download by a client device, and accordingly when the manifest file will be updated to reflect that the segment is ready for download.
  • the server can generate a manifest update hint file in advance of the new manifest file being available, the manifest update hint file giving a useful indication to client devices of when the manifest file will be updated.
  • the method may further comprise: receiving a request for a manifest file from the client device; and sending the current manifest file to the client device.
  • the server will receive a request for the updated manifest file, that request may be timed by the client device to arrive at the server at a time soon after the manifest file has been updated, that time determined from the indication given in the manifest update hint file.
  • the server sends the currently available manifest file to the client device.
  • an encoder arranged to: receive a video stream and generate adaptive bitrate segments for delivery to at least one client; and output the size of a segment being generated once this is determined and before the segment is completed.
  • a server arranged to deliver a live adaptive bitrate stream may comprise an encoder and a packager.
  • the encoder is arranged to encode the incoming content stream. Due to buffering inside of the encoder, the encoder has knowledge of the segment size before the segment has been generated. Thus the encoder can issue a notification of how large the next segment will be before that segment is generated. That indication is used to generate a manifest update hint file to indicate to client devices when the manifest file will be updated.
  • a method of operating an encoder comprising: receiving a video stream and generate adaptive bitrate segments for delivery to at least one client; and outputting the size of a segment being generated once this is determined and before the segment is completed.
  • a packager arranged to: receive adaptive bitrate segments from an adaptive bitrate encoder and to package these for delivery; receive an indication of the size of the next segment from the adaptive bitrate encoder; and create a manifest update hint file on the basis of the size of the next segment.
  • a server arranged to deliver a live adaptive bitrate stream may comprise an encoder and a packager.
  • the packager is responsible for creating downloadable segments from the output of the encoder and for updating the manifest file which lists the available segments.
  • the packager will update the next manifest update time in the Next Manifest Update Hint File in response to the indication of the size of the next segment, where that indication is received from the encoder.
  • the packager may be an adaptive bitrate packager. The size of the next segment is received at the packager before that next segment.
  • a method of operating a packager comprising: receiving an adaptive bitrate segments from an adaptive bitrate encoder and to package these for delivery; receiving an indication of the size of the next segment from the adaptive bitrate encoder; and creating a manifest update hint file on the basis of the size of the next segment.
  • the size of the next segment is received at the packager before that next segment.
  • an apparatus for receiving a live adaptive bitrate stream comprising a processor and a memory, said memory containing instructions executable by said processor whereby said apparatus is operative to: request a manifest file; and request a manifest update hint.
  • the apparatus is further operative to receive a manifest update hint, the manifest update hint including an indication of when the manifest will be updated; and request an updated manifest file at a time indicated by the manifest update hint.
  • an apparatus for delivering a live adaptive bitrate stream comprising a processor and a memory, said memory containing instructions executable by said processor whereby said apparatus is operative to: receive a video stream and generate adaptive bitrate segments for delivery to at least one client device; and calculate the size of a segment being generated before the segment is completed.
  • the apparatus is further operative to create a manifest update hint file on the basis of the size of the next segment; and send the manifest update hint file in response to a request for such from a client device.
  • an apparatus for receiving a live adaptive bitrate stream comprising a processor and a memory, said memory containing instructions executable by said processor whereby said apparatus comprising: a module for requesting a manifest file; and a module for requesting a manifest update hint.
  • the apparatus further comprises a module for receiving a manifest update hint, the manifest update hint including an indication of when the manifest will be updated; and a module for requesting an updated manifest file at a time indicated by the manifest update hint.
  • the time indicated by the manifest update hint may be a time interval or specific time mentioned in the manifest update hint, plus a delay.
  • the delay may be selected by the client device.
  • the live adaptive bitrate stream contains live content.
  • an apparatus for delivering a live adaptive bitrate stream comprising a processor and a memory, said memory containing instructions executable by said processor whereby said apparatus comprising: a module for receiving a video stream and generate adaptive bitrate segments for delivery to at least one client device; and a module for calculating the size of a segment being generated before the segment is completed.
  • the apparatus further comprises a module for creating a manifest update hint file on the basis of the size of the next segment; and a module for sending the manifest update hint file in response to a request for such from a client device.
  • a computer-readable medium carrying instructions, which, when executed by computer logic, causes said computer logic to carry out any of the methods defined herein. Brief description of the dr wings
  • FIG. 1 illustrates a known adaptive bitrate (ABR) streaming system
  • Figure 2 shows a more detailed view of how the ABR stream is created
  • Figure 3 shows how a manifest hint file is generated within a system that generates ABR streams
  • Figure 4 illustrates a method in a client device arranged to receive a live adaptive bitrate stream
  • Figure 5 illustrates a method of operating a server
  • FIG. 6 illustrates the operation of an ABR encoder as described herein
  • FIG. 7 illustrates the operation of an ABR packager presented herein
  • Figure 8 illustrates an apparatus for receiving a live adaptive bitrate stream
  • Figure 9 illustrates an apparatus for delivering a live adaptive bitrate stream
  • Figure 1 illustrates a known adaptive bitrate (ABR) streaming system.
  • the system comprises an origin server 100, an HTTP server 120, which may or may not be physically co-located with the origin server 100, and a client device 150.
  • the origin server 100 creates a set of segments 102 which are made available to the client device 150 via the http server 120.
  • the origin server 100 creates a manifest 110.
  • the client device 150 sends a query to the HTTP server 120, the query requesting a particular live content stream.
  • the HTTP server 120 retrieves a manifest file 110b from the origin server 100 and delivers this to the client device.
  • the client device reads the manifest file 110b, identifies the segment it requires and sends a request for this segment to the HTTP server 120.
  • the HTTP server 120 retrieves the requested segment 102b from the origin sever 100 and delivers this to the client device 150. That segment will comprise perhaps 10 seconds of video content. Before that segment of video content stops playing the client device must have received a subsequent segment. To locate the subsequent segment, the client device requires an updated manifest which reflects the newly available segments.
  • the client device 150 polls the HTTP server 120 to download the current manifest.
  • the client device may attempt to maintain a buffer of several segments, perhaps three 10 second segments. In that case the client device will be attempting to download the fourth segment while the first one is playing so that it can download the fifth segment while the second one is playing, and so on.
  • FIG. 2 shows a more detailed view of how the ABR stream is created.
  • the origin server 200 comprises a live ABR encoder 210, an ABR Packager 220, network storage 230, and an HTTP server 240.
  • the ABR packager 220 comprises a manifest generator 224 which generates and manages the manifest files for the ABR stream.
  • a live video stream 280 is received by the Live ABR Encoder 210.
  • the Live ABR Encoder 210 concurrently encodes the video stream at a plurality of different bitrates.
  • the Live ABR Encoder 210 outputs a plurality of encoded video streams 282, each encoded at a different bitrate.
  • the encoded video streams 282 are received at the ABR Packager 220.
  • the ABR Packager 220 splits each video stream 282 into chunks and packets these to generate ABR segments 284 suitable for download by an ABR client in a client device 150.
  • the ABR Packager 220 further comprises a manifest generator 224 which generates the manifest file(s) 286 that describe the segments 284.
  • Both the manifest files 286 and the segments 284 are stored in a storage component 230, which may be network storage, or a content delivery network (CDN).
  • an HTTP server 240 allows the server 200 to communicate with at least one client device 150. In such an arrangement, a client device 150 must periodically poll the server 240 to see if a new manifest is available.
  • a manifest update hint file is generated.
  • the manifest update hint file provides notification of a future manifest update time based on knowledge provided by an upstream component within the encoder.
  • the encoding process is modified such that a manifest update hint file is output in advance of a new manifest being generated.
  • the manifest update hint file gives a client device an indication of when the manifest will be updated and this allows the client device to request the manifest from the server shortly after the manifest has been updated.
  • the manifest update hint indicates to the client device when it can expect a manifest update to occur.
  • the client device uses this hint to schedule when it requests an updated manifest file. Operating in this way, the client device is less likely to request a manifest file prematurely; such premature requests are unnecessary signaling overhead.
  • the client device will consistently download an updated manifest file promptly after it is made available, allowing for better buffering and smoother playback of live content received via the streaming service.
  • a source transcoder that is acting as the input to the segmenter (and thus providing the real time source of the media segments) feeds advanced notification of when it will be inserting a Boundary Point in the media stream (which is used by the segmenter to divide the stream into segment files).
  • a Boundary Point in the media stream (which is used by the segmenter to divide the stream into segment files).
  • the segmenter then inserts a future update notification entry into the manifest indicating the clock time when the next update can be expected. This enables a client device to acquire the update in a more precise and timely manner, avoiding the possibility of polling for a manifest just before it is updated (and consequently having to wait for the next polling interval before being aware of the update).
  • Figure 3 shows how a manifest hint file is generated within a system that generates ABR streams.
  • the origin server 300 comprises a live ABR encoder 310, an ABR Packager 320, network storage 330, and an HTTP server 340. It should be noted that in practice these component parts may be distributed across any number of physical machines and even geographical locations.
  • the live ABR encoder 310 comprises a manifest update hint generator 312.
  • the ABR packager 320 comprises a manifest generator 324 and a manifest update handler 326.
  • the manifest update handler 326 generates and manages the manifest files for the ABR stream.
  • the manifest update handler 326 receives signals from the manifest update hint generator 312 and outputs a manifest update hint file 388 to the storage component 330.
  • a live video stream 380 is received by the Live ABR Encoder 310.
  • the Live ABR Encoder 310 concurrently encodes the video stream at a plurality of different bitrates.
  • the Live ABR Encoder 310 outputs a plurality of encoded video streams 282, each encoded at a different bitrate.
  • the manifest update hint generator 312 generates a hint 381 which is based on the next segment size or an advertisement insertion splice point in the incoming stream.
  • the encoded video streams 282 are received at the ABR Packager 220.
  • the ABR Packager 220 splits each video stream 282 into chunks and packets these to generate ABR segments 284 suitable for download by an ABR client in a client device 150.
  • the ABR Packager 220 further comprises a manifest generator 224 which generates the manifest file(s) 286 that describe the segments 284.
  • the ABR Packager 320 also receives the hint 381.
  • the manifest update handler 326 within the ABR packager 320 subscribes to the manifest update hint generator 312 and receives a message 381 as soon as the Live ABR encoder 310 determines the size of the next segment.
  • the Live ABR Encoder 310 Due to buffering inside of the Live ABR encoder 310, the Live ABR Encoder 310 has knowledge of the segment size before the segment will be generated. This knowledge is passed from the live ABR encoder 310 to the ABR Packager 320 in the form of a hint or message 381.
  • the manifest update handler 326 within the ABR Packager 320 updates the next manifest update time in the Next Manifest Update Hint File 389.
  • the manifest files 386, the segments 384, and the Next Manifest Update Hint File 389 are stored in a storage component 330, which may be network storage, or a content delivery network (CDN).
  • a storage component 330 which may be network storage, or a content delivery network (CDN).
  • an HTTP server 340 allows the server 300 to communicate with at least one client device 350. When the client device 350 requests an updated manifest, at the same time it will request the Next Manifest Update Hint file 389 to determine when to send its next request for the subsequent manifest.
  • a client device arranged to receive a live adaptive bitrate stream, the client device further arranged to: request a manifest file; and request a manifest update hint.
  • the client device further arranged to receive a manifest update hint, the manifest update hint including an indication of when the manifest will be updated; and request an updated manifest file at a time indicated by the manifest update hint.
  • the manifest update hint may be included in a manifest.
  • a manifest file may include an indication of when another, future, manifest file will become available.
  • the client device is arranged to receive a live adaptive bitrate stream, and to request a manifest file.
  • the client device is further arranged to read a manifest update hint from the manifest file, the manifest update hint including an indication of when the manifest will be updated; and the client device arranged to request an updated manifest file at a time indicated by the manifest update hint.
  • the manifest update hint indicates to the client device when it can expect a manifest update to occur.
  • the client device uses this hint to time when it requests an updated manifest file. Operating in this way, the client device is less likely to request a manifest file prematurely; such requests are unnecessary signaling overhead. Furthermore, the client device will consistently download an updated manifest file promptly after it is made available, allowing for better buffering and smoother playback of live content received via the streaming service.
  • the time indicated by the manifest update hint may be a time interval or specific time mentioned in the manifest update hint, plus a delay. The delay may be selected by the client device. There may be a systematic delay between the new manifest being created by the server from which the client device receives the live adaptive bitrate stream and it being available for download by the client device.
  • a splice point may occur in the content stream at a point requiring a shorter than usual segment. For example: consider an encoder configured to generate 10 second segments; a splice point notice is received resulting in the encoder generating a shorter segment, such as 4 seconds. The client has been polling at appropriately timed 10 second intervals. The shorter segment means that now the polling has an offset from both the segment generation and when the updated manifest is created.
  • the manifest update hint described herein allows the client to keep in sync with the segmenter even when segment lengths change.
  • a splice point may be indicated by an SCTE 35 message.
  • ANSI/SCTE 35 2013 is a joint ANSI/Society of Cable and Telecommunications Engineers standard that describes the inline insertion of cue tones in mpeg transport streams. This is used in broadcasting to insert a local advert or news segment into a nationally broadcast stream.
  • Figure 4 illustrates a method in a client device arranged to receive a live adaptive bitrate stream, the method comprising: requesting 420 a manifest file; and requesting a manifest update hint 430.
  • the method further comprises receiving 440 a manifest update hint, the manifest update hint including an indication of when the manifest will be updated; and requesting 470 an updated manifest file at a time indicated (450, 460) by the manifest update hint.
  • Figure 4 also shows the client device initiating 410 streaming of the live ABR stream. Further, figure 4 gives an example of how the updated manifest file is requested 470 at the time indicated in the manifest update hint file.
  • the client device waits 450 until the time indicated on an internal clock is determined 460 to be the same as the time indicated in the manifest update hint file. Then the client device requests 470 the updated manifest.
  • the manifest update hint indicates to the client device when it can expect a manifest update to occur.
  • the client device uses this hint to time when it requests an updated manifest file. Operating in this way, the client device is less likely to request a manifest file prematurely; such requests are unnecessary signaling overhead. Furthermore, the client device will consistently download an updated manifest file promptly after it is made available, allowing for better buffering and smoother playback of live content received via the streaming service.
  • the manifest update hint may be included in a manifest file, and so retrieved by the client device when it retrieves a manifest file, without the need for a separate request.
  • the time indicated by the manifest update hint may be a time interval or specific time mentioned in the manifest update hint, plus a delay.
  • the method may further comprise selecting the delay.
  • a server arranged to deliver a live adaptive bitrate stream, the server arranged to: receive a video stream and generate adaptive bitrate segments for delivery to at least one client device; and calculate the size of a segment being generated before the segment is completed.
  • the server is further arranged to create a manifest update hint file on the basis of the calculated size of the next segment; and send the manifest update hint file in response to a request for such from a client device.
  • a server that is encoding live content for delivery by adaptive bitrate streaming will determine the size of a segment early on in the encoding of such a segment.
  • the length of the segment determines when it will be ready for download by a client device, and accordingly when the manifest file will be updated to reflect that the segment is ready for download. Accordingly, the server can generate a manifest update hint file in advance of the new manifest file being available, the manifest update hint file giving a useful indication to client devices of when the manifest file will be updated.
  • the server may be arranged to: receive a request for a manifest file from the client device; and send the current manifest file to the client device.
  • the server will receive a request for the updated manifest file, that request may be timed by the client device to arrive at the server at a time soon after the manifest file has been updated, that time determined from the indication given in the manifest update hint file.
  • the server sends the currently available manifest file to the client device.
  • Figure 5 illustrates a method of operating a server, the server arranged to deliver a live adaptive bitrate stream, the method comprising: receiving 510 a video stream and generate 520 adaptive bitrate segments for delivery to at least one client device; and calculating 530 the size of a segment being generated before the segment is completed. The method further comprising: creating 540 a manifest update hint file on the basis of the calculated size of the next segment; and sending 550 the manifest update hint file in response to a request for such from a client device.
  • a server that is encoding live content for delivery by adaptive bitrate streaming will determine the size of a segment early on in the encoding of such a segment.
  • the length of the segment determines when it will be ready for download by a client device, and accordingly when the manifest file will be updated to reflect that the segment is ready for download.
  • the server can generate a manifest update hint file in advance of the new manifest file being available, the manifest update hint file giving a useful indication to client devices of when the manifest file will be updated.
  • the method may further comprise: receiving a request for a manifest file from the client device; and sending the current manifest file to the client device.
  • the server will receive a request for the updated manifest file, that request may be timed by the client device to arrive at the server at a time soon after the manifest file has been updated, that time determined from the indication given in the manifest update hint file.
  • the server sends the currently available manifest file to the client device.
  • an encoder arranged to: receive a video stream and generate adaptive bitrate segments for delivery to at least one client; and output the size of a segment being generated once this is determined and before the segment is completed.
  • a server arranged to deliver a live adaptive bitrate stream may comprise an encoder and a packager.
  • the encoder is arranged to encode the incoming content stream. Due to buffering inside of the encoder, the encoder has knowledge of the segment size before the segment has been generated. Thus, the encoder can issue a notification of how large the next segment will be before that segment is generated. That indication is used to generate a manifest update hint file to indicate to client devices when the manifest file will be updated.
  • a method of operating an encoder comprising: receiving a video stream and generate adaptive bitrate segments for delivery to at least one client; and outputting the size of a segment being generated once this is determined and before the segment is completed.
  • Figure 6 illustrates the operation of an ABR encoder as described herein.
  • the ABR encoder encodes 610 video.
  • the encoder makes a determination 620 as to whether it has received an SCTE 35 message. If the encoder has not received an SCTE 35 message, then it sends an update message of the next manifest update message. If the encoder has received an SCTE 35 message, then the ABR encoder calculates 640 the next segment size, in seconds, and sends 650 an update message of the next manifest update message.
  • a packager arranged to: receive adaptive bitrate segments from an adaptive bitrate encoder and to package these for delivery; receive an indication of the size of the next segment from the adaptive bitrate encoder; and create a manifest update hint file on the basis of the size of the next segment.
  • a server arranged to deliver a live adaptive bitrate stream may comprise an encoder and a packager.
  • the packager is responsible for creating downloadable segments from the output of the encoder and for updating the manifest file which lists the available segments.
  • the packager will update the next manifest update time in the Next Manifest Update Hint File in response to the indication of the size of the next segment, that indication received from the encoder.
  • the packager may be an adaptive bitrate packager. The size of the next segment is received at the packager before that next segment.
  • a method of operating a packager comprising: receiving an adaptive bitrate segments from an adaptive bitrate encoder and to package these for delivery; receiving an indication of the size of the next segment from the adaptive bitrate encoder; and creating a manifest update hint file on the basis of the size of the next segment.
  • the size of the next segment is received at the packager before that next segment.
  • Figure 7 illustrates the operation of an ABR packager presented herein.
  • the ABR Packager subscribes 710 to the hint messages issued by the ABR Encoder.
  • the ABR Packager receives 720 an update message from the ABR encoder, the Packager writes 730 a new next manifest update hint file.
  • Figure 8 illustrates an apparatus for receiving a live adaptive bitrate stream.
  • the apparatus comprises a processor 820 and a memory 825, said memory containing instructions executable by said processor whereby said apparatus is operative to receive a manifest of segments of which the live adaptive bitrate stream is comprised.
  • the apparatus is further operative to request a manifest file; and request a manifest update hint.
  • the apparatus is further operative to receive a manifest update hint, the manifest update hint including an indication of when the manifest will be updated; and request an updated manifest file at a time indicated by the manifest update hint.
  • the apparatus of figure 8 further comprises an output 830 for outputting content to a user.
  • the output 830 may comprise, for example, a screen, a speaker, a headphone socket, or an HDMI port.
  • the apparatus further comprises a transmitter 840 for sending information into a network, and a receiver 850 for receiving information from a network. Transmitter 840 and receiver 850 may use either wired or wireless communication protocols.
  • Figure 9 illustrates an apparatus for delivering a live adaptive bitrate stream.
  • the apparatus comprises a processor 920 and a memory 925, said memory containing instructions executable by said processor 920 whereby said apparatus is operative to: receive a video stream and generate adaptive bitrate segments for delivery to at least one client device; and calculate the size of a segment being generated before the segment is completed.
  • the apparatus is further operative to create a manifest update hint file on the basis of the size of the next segment; and send the manifest update hint file in response to a request for such from a client device.
  • the apparatus of figure 9 further comprises a transmitter 940 for sending information into a network, and a receiver 950 for receiving information from a network.
  • Transmitter 940 and receiver 950 may use either wired or wireless communication protocols.
  • an apparatus for receiving a live adaptive bitrate stream comprising a processor and a memory, said memory containing instructions executable by said processor whereby said apparatus comprising: a module for requesting a manifest file; and a module for requesting a manifest update hint.
  • the apparatus further comprises a module for receiving a manifest update hint, the manifest update hint including an indication of when the manifest will be updated; and a module for requesting an updated manifest file at a time indicated by the manifest update hint.
  • the time indicated by the manifest update hint may be a time interval or specific time mentioned in the manifest update hint, plus a delay.
  • the delay may be selected by the client device.
  • the live adaptive bitrate stream contains live content.
  • an apparatus for delivering a live adaptive bitrate stream comprising a processor and a memory, said memory containing instructions executable by said processor whereby said apparatus comprising: a module for receiving a video stream and generate adaptive bitrate segments for delivery to at least one client device; and a module for calculating the size of a segment being generated before the segment is completed.
  • the apparatus further comprises a module for creating a manifest update hint file on the basis of the size of the next segment; and a module for sending the manifest update hint file in response to a request for such from a client device.
  • the live adaptive bitrate stream contains live content.
  • Live content is content that is received at the streaming system shortly before being sent to clients, any delay resulting from the time taken to process incoming data into a form ready for live adaptive bitrate streaming.
  • the live adaptive bitrate stream may comprise video content.
  • the client device may be a user apparatus.
  • the client device may be any kind of personal computer such as a television, a smart television, a set-top box, a games-console, a home- theatre personal computer, a tablet, a smartphone, a laptop, or even a desktop PC.

Abstract

L'invention concerne un dispositif client conçu pour recevoir un flux de débit binaire adaptatif en direct, le dispositif client étant également conçu pour : demander un fichier manifeste ; et demander un message d'indication de mise à jour de manifeste. Le dispositif client selon l'invention est encore conçu pour recevoir un message d'indication de mise à jour de manifeste, ledit message contenant une indication du moment de la mise à jour du manifeste ; et demander un fichier de manifeste mis à jour à un moment indiqué par le message d'indication de mise à jour de manifeste.
PCT/EP2017/068868 2016-08-11 2017-07-26 Diffusion en continu à débit binaire adaptatif amélioré de contenu en direct WO2018028986A1 (fr)

Priority Applications (7)

Application Number Priority Date Filing Date Title
DK17745318.0T DK3497831T3 (da) 2016-08-11 2017-07-26 Forbedret adaptiv bithastighedsstreaming af live indhold
EP17745318.0A EP3497831B1 (fr) 2016-08-11 2017-07-26 Diffusion en continu à débit binaire adaptatif amélioré de contenu en direct
EP21192201.8A EP3930234B1 (fr) 2016-08-11 2017-07-26 Diffusion en continu à débit binaire adaptatif amélioré de contenu en direct
ES17745318T ES2896803T3 (es) 2016-08-11 2017-07-26 Transmisión con tasa de bits adaptativa mejorada de contenido en vivo
US16/324,465 US10911508B2 (en) 2016-08-11 2017-07-26 Adaptive bitrate streaming of live content
US17/144,440 US11283849B2 (en) 2016-08-11 2021-01-08 Adaptive bitrate streaming of live content
US17/683,710 US11778012B2 (en) 2016-08-11 2022-03-01 Adaptive bitrate streaming of live content

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662373576P 2016-08-11 2016-08-11
US62/373,576 2016-08-11

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US16/324,465 A-371-Of-International US10911508B2 (en) 2016-08-11 2017-07-26 Adaptive bitrate streaming of live content
US17/144,440 Continuation US11283849B2 (en) 2016-08-11 2021-01-08 Adaptive bitrate streaming of live content

Publications (1)

Publication Number Publication Date
WO2018028986A1 true WO2018028986A1 (fr) 2018-02-15

Family

ID=59416690

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2017/068868 WO2018028986A1 (fr) 2016-08-11 2017-07-26 Diffusion en continu à débit binaire adaptatif amélioré de contenu en direct

Country Status (5)

Country Link
US (3) US10911508B2 (fr)
EP (2) EP3497831B1 (fr)
DK (1) DK3497831T3 (fr)
ES (1) ES2896803T3 (fr)
WO (1) WO2018028986A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11259098B2 (en) 2019-08-15 2022-02-22 AMC Network Entertainment LLC Monitoring segmentation messages of video streams

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3497909B1 (fr) * 2016-08-11 2022-06-01 Telefonaktiebolaget LM Ericsson (publ) Transmission en continu améliorée à débit binaire adaptatif de contenu en direct avec notification de poussée de mise à jour de manifeste ou interrogation longue
DK3497831T3 (da) 2016-08-11 2021-10-04 Ericsson Telefon Ab L M Forbedret adaptiv bithastighedsstreaming af live indhold
US10397286B2 (en) * 2017-05-05 2019-08-27 At&T Intellectual Property I, L.P. Estimating network data streaming rate
US11930254B2 (en) * 2020-04-07 2024-03-12 Tencent America LLC Patchable remote element for data manipulation
US11202122B1 (en) * 2020-11-17 2021-12-14 Sling Media Pvt. Ltd. Stale variant handling for adaptive media player

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120042050A1 (en) * 2010-08-10 2012-02-16 Qualcomm Incorporated Representation groups for network streaming of coded multimedia data
US20160112484A1 (en) * 2014-10-21 2016-04-21 Adobe Systems Incorporated Live Manifest Update

Family Cites Families (56)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050015816A1 (en) * 2002-10-29 2005-01-20 Actv, Inc System and method of providing triggered event commands via digital program insertion splicing
US9384299B2 (en) 2009-09-22 2016-07-05 Thwapr, Inc. Receiving content for mobile media sharing
US9497290B2 (en) 2010-06-14 2016-11-15 Blackberry Limited Media presentation description delta file for HTTP streaming
JP5961174B2 (ja) 2010-11-02 2016-08-02 テレフオンアクチーボラゲット エルエム エリクソン（パブル） メディア記述配信のための方法およびデバイス
US20120207088A1 (en) * 2011-02-11 2012-08-16 Interdigital Patent Holdings, Inc. Method and apparatus for updating metadata
US8489760B2 (en) * 2011-03-31 2013-07-16 Juniper Networks, Inc. Media file storage format and adaptive delivery system
US9838741B2 (en) 2011-08-10 2017-12-05 Lg Electronics Inc. Method for transmitting broadcast service, method for receiving broadcast service, and apparatus for receiving broadcast service
US8751679B2 (en) * 2011-10-07 2014-06-10 Ericsson Television Inc. HTTP adaptive streaming server with automatic rate shaping
US8949307B2 (en) 2011-11-15 2015-02-03 Google Inc. Cloud-to-device messaging for application activation and reporting
US8234350B1 (en) * 2011-12-19 2012-07-31 Seachange International, Inc. Systems and methods for generating targeted manifest files
EP2798816B1 (fr) * 2011-12-29 2016-05-11 Koninklijke KPN N.V. Contrôle de flux de contenu traité initialement sur réseau
US20130312046A1 (en) * 2012-05-15 2013-11-21 Mark Robertson Smart stream delivery server, system and methods for assembling a mix of services to be delivered to a subscriber's premises
US9537920B2 (en) * 2012-05-18 2017-01-03 Google Technology Holdings LLC Enforcement of trick-play disablement in adaptive bit rate video content delivery
US9128892B2 (en) 2012-12-10 2015-09-08 Netflix, Inc. Managing content on an ISP cache
US10439910B2 (en) * 2012-12-21 2019-10-08 Koninklijke Kpn N.V. Low-latency streaming
WO2014121857A1 (fr) * 2013-02-06 2014-08-14 Telefonaktiebolaget L M Ericsson (Publ) Procédé pour détecter un problème de fonctionnalité d'un encodeur
US9654528B1 (en) * 2013-03-11 2017-05-16 Google Inc. Dynamic bitrate selection for streaming media
US8949912B2 (en) 2013-03-12 2015-02-03 Centurylink Intellectual Property Llc ABR live to VOD system and method
EP2954683B1 (fr) 2013-03-15 2018-07-11 ARRIS Enterprises LLC Définition et délivrance de liste de lecture améliorées pour changement de canal rapide avec diffusion en flux adaptative hppt
US9674251B2 (en) 2013-06-17 2017-06-06 Qualcomm Incorporated Mediating content delivery via one or more services
US9124947B2 (en) * 2013-09-04 2015-09-01 Arris Enterprises, Inc. Averting ad skipping in adaptive bit rate systems
US10015222B2 (en) * 2013-09-26 2018-07-03 Arris Canada, Inc. Systems and methods for selective retrieval of adaptive bitrate streaming media
US9253231B2 (en) * 2013-12-19 2016-02-02 Verizon Patent And Licensing Inc. Retrieving and caching adaptive bitrate stream segments based on network congestion
US10123087B1 (en) * 2014-03-12 2018-11-06 Cox Communications, Inc. Channel block switching
US9888047B2 (en) * 2014-04-03 2018-02-06 Cisco Technology, Inc. Efficient on-demand generation of ABR manifests
US10084838B2 (en) * 2014-10-29 2018-09-25 DLVR, Inc. Generating and using manifest files including content delivery network authentication data
US9509742B2 (en) * 2014-10-29 2016-11-29 DLVR, Inc. Configuring manifest files referencing infrastructure service providers for adaptive streaming video
US10142386B2 (en) * 2014-10-29 2018-11-27 DLVR, Inc. Determining manifest file data used in adaptive streaming video delivery
US9674564B2 (en) 2014-12-15 2017-06-06 Arris Enterprises, Inc. System and methods for multicast delivery of internet protocol video content
KR101827277B1 (ko) 2015-03-01 2018-02-08 엘지전자 주식회사 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법
US10432688B2 (en) * 2015-03-13 2019-10-01 Telefonaktiebolaget Lm Ericsson (Publ) System and method for optimized delivery of live ABR media
US20180115796A1 (en) 2015-03-26 2018-04-26 Lg Electronics Inc. Broadcast signal transmitting device, broadcast signal receiving device, broadcast signal transmitting method, and broadcast signal receiving method
US9641578B2 (en) * 2015-04-02 2017-05-02 Arris Enterprises, Inc. Minimizing unicast bandwidth in an adaptive bit rate system
US9276983B2 (en) * 2015-05-01 2016-03-01 Amazon Technologies, Inc. Content delivery network video content invalidation through adaptive bitrate manifest manipulation
US10070174B2 (en) * 2015-06-05 2018-09-04 Apple Inc. Movie package file format to persist HLS onto disk
WO2016200998A1 (fr) * 2015-06-09 2016-12-15 Arris Enterprises Llc Synchronisation de client de diffusion en continu en direct http (hls) de vidéo
US10476926B2 (en) * 2015-06-12 2019-11-12 Telefonaktiebolaget Lm Ericsson (Publ) System and method for managing ABR bitrate delivery responsive to video buffer characteristics of a client
US10277928B1 (en) * 2015-10-06 2019-04-30 Amazon Technologies, Inc. Dynamic manifests for media content playback
US20170123713A1 (en) * 2015-10-30 2017-05-04 Imagine Communications Corp. Device and process for data storage and read/write efficiency
EP3179688A1 (fr) 2015-12-11 2017-06-14 Koninklijke KPN N.V. Mise à jour d'élément d'un fichier manifest sur la base de correctifs
US10009659B2 (en) * 2016-03-31 2018-06-26 Disney Enterprises, Inc. System and method for hybrid push-based streaming
US20170310752A1 (en) 2016-04-21 2017-10-26 Samsung Electronics Company, Ltd. Utilizing a Content Delivery Network as a Notification System
US10178171B2 (en) 2016-04-21 2019-01-08 Samsung Electronics Company, Ltd. Content management system for distribution of content
US10820063B2 (en) * 2016-06-10 2020-10-27 Arris Enterprises Llc Manifest customization in adaptive bitrate streaming
US10516715B2 (en) 2016-06-22 2019-12-24 Telefonaktiebolaget Lm Ericsson (Publ) Network-controlled time-shift live media and advertisement content play for learned ABR video white spot coverage in a streaming network
US10277929B1 (en) * 2016-06-22 2019-04-30 Amazon Technologies, Inc. Live streaming media content using on-demand manifests
US10313408B2 (en) 2016-06-22 2019-06-04 Telefonaktiebolaget Lm Ericsson (Publ) Client-assisted time-shift live media and advertisement content play for learned ABR video white spot coverage in a streaming network
US10313721B1 (en) * 2016-06-22 2019-06-04 Amazon Technologies, Inc. Live streaming media content using on-demand manifests
GB2552220B (en) * 2016-07-15 2018-09-05 Openwave Mobility Inc A method for detecting a live adaptive BIT rate stream
EP3497909B1 (fr) * 2016-08-11 2022-06-01 Telefonaktiebolaget LM Ericsson (publ) Transmission en continu améliorée à débit binaire adaptatif de contenu en direct avec notification de poussée de mise à jour de manifeste ou interrogation longue
DK3497831T3 (da) * 2016-08-11 2021-10-04 Ericsson Telefon Ab L M Forbedret adaptiv bithastighedsstreaming af live indhold
WO2018125269A1 (fr) 2016-12-30 2018-07-05 Google Llc Systèmes et procédés d'interruption de contenu diffusé en continu fourni par le biais d'un protocole de manifeste intangible
US20190342356A1 (en) 2017-01-02 2019-11-07 Koninklijke Kpn N.V. Selectively updating a dynamic manifest file
US10972515B2 (en) 2017-07-31 2021-04-06 Verizon Digital Media Services Inc. Server assisted live stream failover
US10820066B2 (en) 2018-06-20 2020-10-27 Cisco Technology, Inc. Reconciling ABR segments across redundant sites
US11277665B2 (en) * 2018-08-13 2022-03-15 Comcast Cable Communications, Llc Using manifest files to determine events in content items

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120042050A1 (en) * 2010-08-10 2012-02-16 Qualcomm Incorporated Representation groups for network streaming of coded multimedia data
US20160112484A1 (en) * 2014-10-21 2016-04-21 Adobe Systems Incorporated Live Manifest Update

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11259098B2 (en) 2019-08-15 2022-02-22 AMC Network Entertainment LLC Monitoring segmentation messages of video streams
US11716519B2 (en) 2019-08-15 2023-08-01 AMC Network Entertainment LLC Monitoring segmentation messages of video streams

Also Published As

Publication number Publication date
US20220182433A1 (en) 2022-06-09
EP3497831A1 (fr) 2019-06-19
EP3930234A1 (fr) 2021-12-29
EP3497831B1 (fr) 2021-09-01
EP3930234B1 (fr) 2023-09-06
DK3497831T3 (da) 2021-10-04
EP3930234C0 (fr) 2023-09-06
US11778012B2 (en) 2023-10-03
US10911508B2 (en) 2021-02-02
US20210211480A1 (en) 2021-07-08
US11283849B2 (en) 2022-03-22
ES2896803T3 (es) 2022-02-25
US20190222622A1 (en) 2019-07-18

Similar Documents

Publication Publication Date Title
US11778012B2 (en) Adaptive bitrate streaming of live content
US11490145B2 (en) Content insertion in streaming media content
US10009659B2 (en) System and method for hybrid push-based streaming
EP2391086B1 (fr) Procédé et appareil pour la lecture d'un contenu en direct
US20170195744A1 (en) Live-stream video advertisement system
US20210250631A1 (en) Adaptive Bitrate Streaming Of Live Content with Manifest Update Push Notification or Long Poll
WO2018122402A1 (fr) Mise à jour sélective d'un fichier de manifeste dynamique
US20150256600A1 (en) Systems and methods for media format substitution
JP2016538754A (ja) コンテンツ配信のための方法及び装置
EP2773078B1 (fr) Procédé, système et dispositifs de distribution de contenu multimédia à l'aide de diffusion en continu adaptative
JP6359539B2 (ja) レンダリング時の制御
JPWO2016174960A1 (ja) 受信装置、送信装置、およびデータ処理方法
US10687106B2 (en) System and method for distributed control of segmented media
CN112243158A (zh) 媒体文件处理方法、装置及电子设备
WO2019193991A1 (fr) Dispositif de distribution, procédé de distribution et programme
WO2016174959A1 (fr) Dispositif de réception, dispositif de transmission et procédé de traitement de données
US20200067850A1 (en) Content supply device, content supply method, program, terminal device, and content supply system
KR20210052345A (ko) 이종 네트워크를 통해 수신한 콘텐츠의 삽입 방법 및 장치

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: 17745318

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017745318

Country of ref document: EP

Effective date: 20190311