# US 2018/0324278 A1 · Local Cache Bandwidth Matching

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2018/0324278 A1
- Document ID: US20180324278A1
- Status: Published application
- Kind: A1
- Application number: 15/585,590
- Filed: 2017-05-03
- Published: 2018-11-08
- Earliest claimed: 2017-05-03
- Assignees: Comcast Cable Communications, LLC
- Applicants: Comcast Cable Communications, LLC
- Inventors: Richard Fliam; David Arbuckle
- Web page: https://patentgrep.com/patent/US20180324278A1

## CPC

- H04L 65/80: Responding to QoS
- H04L 41/0896: Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities (flow or congestion control using dynamic resource allocation, e.g. in-call renegotiation, H04L47/76)
- H04L 65/612: for unicast
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/55: Push-based network services
- H04L 67/568: Storing data temporarily at an intermediate stage, e.g. caching
- H04L 67/63: Routing a service request depending on the request content or context
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Methods and systems are disclosed herein for managing delivery of content fragments to a device in response to a bandwidth determination. In one implementation of the disclosure, when a content player or device requests a content fragments, a local cache may determine a bandwidth or data rate related to transmission of a content fragment from a source to the cache, and send the fragment to the player at a rate corresponding to the determined bandwidth or data rate.

## Claims

### Claim 1

A method comprising:
receiving, from a content source, a plurality of content fragments and storing them in a cache;
receiving, from a playback device, a request for one of the plurality of content fragments;
determining a length of time associated with receipt of the content fragment from the content source;
determining a bandwidth associated with transmission of the content fragment based on the determined length of time and a size of the content fragment; and
sending, to the playback device, the content fragment at a rate determined in accordance with the determined bandwidth.

### Claim 2 (depends on 1)

The method of claim 1, further comprising determining a playback quality associated with the content fragment based on the determined bandwidth.

### Claim 3 (depends on 1)

The method of claim 1, wherein sending the content fragment at a rate determined in accordance with the determined bandwidth comprises sending the content asset at a rate that does not exceed the determined bandwidth.

### Claim 4 (depends on 1)

The method of claim 1, wherein determining a bandwidth associated with transmission of the content fragment comprises dividing the size of the content fragment by the determined length of time.

### Claim 5 (depends on 1)

The method of claim 1, wherein the content source communicates with the device using HTTP/2 protocol.

### Claim 6 (depends on 5)

The method of claim 5, wherein receiving a plurality of content fragments comprises receiving a push promise message from the content source.

### Claim 7 (depends on 6)

The method of claim 6, wherein the push promise message comprises the size of each of the one or more content fragments.

### Claim 8 (depends on 7)

The method of claim 7, further comprising storing the size of a content fragment as metadata with the corresponding content fragment.

### Claim 9

A method comprising:
receiving, from a playback component of a device, a request for a first content fragment;
sending, to a content source, the request for the first content fragment;
receiving, from the content source, the first content fragment and a second content fragment and storing the first content fragment and the second content fragment in a cache;
determining a first length of time associated with receipt of the first content fragment from the content source and a second length of time associated with receipt of the second content fragment from the content source;
determining a first bandwidth based on the first length of time and a size of the first content fragment and a second bandwidth based on the second length of time and a size of the second content fragment;
sending, to the playback component from the cache, the first content fragment at a rate determined in accordance with the first bandwidth;
receiving, from the playback component, a request for the second content fragment; and
sending, to the playback component from the cache, the second content fragment at a rate determined in accordance with the second bandwidth.

### Claim 10 (depends on 9)

The method of claim 9, wherein receiving the first content fragment and the second content fragment comprises receiving the first content fragment and the second content fragment in response to a determination by the content source that the playback component is likely to request playback of the second content fragment.

### Claim 11 (depends on 10)

The method of claim 10, wherein determining at the content source that the playback component is likely to request playback of the second content fragment comprises determining at the content source that the second content fragment is related to the first content fragment.

### Claim 12 (depends on 9)

The method of claim 9, wherein sending the first content fragment at a rate determined in accordance with the first bandwidth comprises sending the first content asset at a rate that does not exceed the first bandwidth and sending the second content fragment at a rate determined in accordance with the second bandwidth comprises sending the second content asset at a rate that does not exceed the second bandwidth.

### Claim 13 (depends on 9)

The method of claim 9, wherein determining the first bandwidth comprises dividing the size of the first content fragment by the first length of time and determining the second bandwidth comprises dividing the size of the second content fragment by the second length of time.

### Claim 14 (depends on 9)

The method of claim 9, wherein the content source communicates with the device using HTTP/2 protocol.

### Claim 15 (depends on 14)

The method of claim 14, wherein receiving the first content fragment and the second content fragment comprises receiving a push promise message from the content source.

### Claim 16 (depends on 15)

The method of claim 15, wherein the push promise message comprises the size of the first content fragment and the size of the second content fragment.

### Claim 17 (depends on 16)

The method of claim 16, further comprising storing the size of the first content fragment as metadata with the first content fragment and the size of the second content fragment as metadata with the second content fragment.

### Claim 18

A method comprising:
sending, to a cache associated with a device, a request for a content fragment;
receiving, from the cache, the content fragment at a rate determined in accordance with a bandwidth based on a length of time associated with receipt of the content asset from a source and a size of the content fragment; and
initializing playback of the content fragment.

### Claim 19 (depends on 18)

The method of claim 18, wherein the cache communicates with the source using HTTP/2 protocol.

### Claim 20 (depends on 19)

The method of claim 19, wherein the cache receives from the source a push promise message, the push promise message comprising the size of the content fragment.
