Controlled streaming of segmented content
US-10225306-B2 · Mar 5, 2019 · US
US10523723B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10523723-B2 |
| Application number | US-201514725649-A |
| Country | US |
| Kind code | B2 |
| Filing date | May 29, 2015 |
| Priority date | Jun 6, 2014 |
| Publication date | Dec 31, 2019 |
| Grant date | Dec 31, 2019 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
The invention relates to a method, a system and various components of such a system for selecting a chunk identifier in a content delivery network. In said network a first and a second chunk are available, belonging to different quality representations of a content item. A client device transmits a first chunk retrieval request for retrieving a first chunk and a further request. In response to said first chunk retrieval request and/or said further request, delivery path information is transmitted. The delivery path information may comprise chunk identifiers and bandwidth indicators. On the basis of the delivery path information the client device determines a chunk identifier to be included in a second chunk retrieval request for retrieving a second chunk.
Opening claim text (preview).
What is claimed is: 1. A method for selecting a chunk identifier referencing a chunk associated with a content item, on the basis of a manifest file, said content item being provided in one or more representations, each representation comprising a plurality of time-sequential chunks, said manifest file comprising at least a first set of chunk identifiers referencing chunks of a first representation, and a second set of chunk identifiers referencing chunks of a second representation; chunks of said first representation being retrievable by a client device via a first delivery path and chunks of said second representation being retrievable by said client device via a second delivery path which is different from the first delivery path, said method comprising: transmitting by said client device over said first delivery path, on the basis of said manifest file, a first chunk retrieval request for retrieving a first chunk of said first representation, said request comprising a first chunk identifier of said first set; transmitting by said client device over said second delivery path, on the basis of said manifest file, a further request comprising a second chunk identifier of said second set, said second chunk identifier referencing a second chunk; receiving by said client device a response message comprising delivery path information in response to said further request, wherein said response message does not comprise said second chunk or part thereof and wherein said delivery path information comprises at least one of: (a) a chunk identifier, referencing a chunk of said second representation currently stored on a network element, said network element being part of said second delivery path; (b) a bandwidth indicator, indicating available bandwidth between said client device and a network element storing said chunk; (c) a chunk enhancement indicator, indicating chunks comprising content enhancements; and (d) a lifetime indicator, indicating a period the delivery path information is assumed to be valid; and selecting by said client device, at least on the basis of said received delivery path information, a chunk identifier, from either said first or second set, for including in a second chunk retrieval request for retrieving a second chunk. 2. The method according to claim 1 , wherein said first and/or said second chunk retrieval request comprises an HTTP GET request; and/or wherein said further request comprises an HTTP HEAD request; and/or wherein said delivery path information is embedded in an HTTP response message. 3. The method according to claim 1 , wherein said second delivery path comprises at least a non-transparent network element and a transparent network element, said further request being addressed to said non-transparent network element and said delivery path information being provided by said transparent network element. 4. The method according to claim 1 , wherein said first and second chunks are retrievable from a content delivery network, said client device being connected to said one or more content delivery networks via a first access network and via a second access network and wherein said first delivery path is associated with the first access network and the second delivery path with the second access network. 5. The method according to claim 1 , wherein transmitting said further request and/or said first chunk retrieval request is triggered by a predefined event, the predefined event being a buffer of said client device being below a predefined buffer threshold. 6. The method according to claim 1 , further comprising transmitting said delivery path information in response to said further request, based on an indicator for allowing said transmission, wherein said indicator is a cookie in a HTTP cookie header or a token in an URL string. 7. The method according to claim 6 , wherein said delivery path information is only transmitted after verifying that said further request comprises or is provided with said indicator. 8. A computer program product comprising software code portions configured for, when run in the memory of a computer, executing the method steps according to claim 1 . 9. A client device for selecting, on the basis of a manifest file, a chunk identifier referencing a chunk associated with a content item, said content item being provided in one or more representations, each representation comprising a plurality of time-sequential chunks, said manifest file comprising at least a first set of chunk identifiers referencing chunks of a first representation, and a second set of chunk identifiers referencing chunks of a second representation; chunks of said first representation being retrievable by said client device via a first delivery path and chunks of said second representation being retrievable by said client device via a second delivery path which is different from the first delivery path, said client device comprising a processor arranged for: transmitting over said first delivery path, on the basis of said manifest file, a first chunk retrieval request for retrieving a first chunk of said first representation, said request comprising a first chunk identifier of said first set; transmitting over said second delivery path, on the basis of said manifest file, a further request comprising a second chunk identifier of said second set, said second chunk identifier referencing a second chunk; receiving a response message comprising delivery path information in response to said further request or said first chunk retrieval request, wherein said response message does not comprise said second chunk or part thereof and wherein said delivery path information comprises at least one of: (a) a chunk identifier, referencing a chunk of said second representation currently stored on a network element, said network element being part of said second delivery path; (b) a bandwidth indicator, indicating available bandwidth between said client device and a network element storing said chunk; (c) a chunk enhancement indicator, indicating chunks comprising content enhancements; and (d) a lifetime indicator, indicating a period the delivery path information is assumed to be valid; and selecting, at least on the basis of said received delivery path information, a chunk identifier from either said first or second set, for including in a second chunk retrieval request for retrieving a second chunk. 10. A non-transitory computer readable storage medium for storing at least part of a manifest file for use by a client device according to claim 9 , said manifest file comprising: one or more chunk identifiers for enabling said client device to generate a chunk retrieval request or a further request for delivery path information; and, at least one of: indicator information for adding an indicator to said first chunk request or said further request, wherein indicator information comprises an indicator for allowing transmission of delivery path information to said client device and/or an indicator instruction for instructing said client device to add said indicator to said request; an access network identifier associated with said one or more chunk identifiers, said identifier being arranged for identifying an access network forming part of a delivery path via which said chunks are retrievable, and optionally causing said client device to connect to said access network for transmission of said further request; a probe priority indicator associated with said one or more chunk identifiers and arranged for indicating an order of transmitting further request. 11. The client device according to claim 9 , wherein said first and/or said second chunk retrieval request comprises an HTTP GET request
by decomposing the content in the time domain, e.g. in time segments · CPC title
Controlling the complexity of the content stream or additional data, e.g. lowering the resolution or bit-rate of the video stream for a mobile client with a small screen (arrangements for using the results of monitoring on user's side in broadcast systems H04H60/65; flow control in packet networks H04L47/10) · CPC title
Retrieving content or additional data from different sources, e.g. from a broadcast channel and the Internet (web site content organization and management for information retrieval from the Internet G06F16/958; transmission by internet of broadcast information H04H60/82; stock exchange data over packet-switching network H04L12/1804; push services including data channel over packet-switching network H04L12/1859) · CPC title
Monitoring of downstream path of the transmission network originating from a server, e.g. bandwidth variations of a wireless network (arrangements for maintenance or administration in data switching networks involving bandwidth and capacity management H04L41/0896) · CPC title
based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.