Content distribution system cache management
US-2017026286-A1 · Jan 26, 2017 · US
US10313415B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10313415-B2 |
| Application number | US-201514640634-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 6, 2015 |
| Priority date | Jul 18, 2014 |
| Publication date | Jun 4, 2019 |
| Grant date | Jun 4, 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.
According to one aspect, a method includes obtaining a packet at a network endpoint from a client via a first segment. The packet has a segment routing header that includes a list of addresses attached to a chunk entry, and is configured to identify at least a first chunk requested by the client. The method also includes identifying, at the network endpoint, the at least first chunk using the packet, and determining at the network endpoint if the network endpoint has the first chunk. If it is determined that the network endpoint has the first chunk, the first chunk is provided from the network endpoint to the client. Alternatively, if it is determined that the network endpoint does not have the first chunk, the packet is provided to a second segment.
Opening claim text (preview).
What is claimed is: 1. A method comprising: obtaining a packet at a network endpoint, the packet being obtained from a client via a first segment, the packet having a segment routing header, the segment routing header including a list of addresses attached to a chunk entry, wherein the packet is configured to identify at least a first chunk requested by the client, wherein the list of addresses includes a plurality of addresses, and wherein a first chunk address corresponding to the at least first chunk is a last address included in the list of addresses, the last address being a V6 content descriptor (v6CD) that identifies the first chunk, and wherein other addresses in the list of addresses identify endpoints that may be asked for the first chunk; identifying, at the network endpoint, the at least first chunk using the packet; determining at the network endpoint if the network endpoint has the first chunk; providing the first chunk from the network endpoint to the client if it is determined that the network endpoint has the first chunk; and providing the packet to at least a second segment if it is determined that the network endpoint does not have the first chunk. 2. The method of claim 1 wherein the first chunk is a chunk of video, and wherein the segment routing header is configured to identify at least the first chunk requested by the client. 3. The method of claim 1 wherein the first chunk is a chunk of audio. 4. The method of claim 1 wherein the packet is included in traffic, and wherein the method further includes: terminating the traffic if it is determined that the network endpoint has the first chunk. 5. A tangible, non-transitory computer-readable medium comprising computer program code, the computer program code, when executed, configured to: obtain a packet at a network endpoint, the packet being obtained from a client via a first segment, the packet having a segment routing header, the segment routing header including a list of addresses attached to a chunk entry, the list of addresses including a plurality of addresses, wherein the packet is configured to identify at least a first chunk requested by the client, wherein a first chunk address corresponding to the at least first chunk is a last address included in the list of addresses, the computer program code configured to identify the at least first chunk using the packet being further configured to obtain the first chunk address from the list of addresses, wherein the last address is a V6 content descriptor (v6CD) that identifies the first chunk, and wherein other addresses in the list of addresses identify endpoints that may be asked for the first chunk; identify, at the network endpoint, the at least first chunk using the packet; determine at the network endpoint if the network endpoint has the first chunk; provide the first chunk from the network endpoint to the client if it is determined that the network endpoint has the first chunk; and provide the packet to at least a second segment if it is determined that the network endpoint does not have the first chunk. 6. The tangible, non-transitory computer-readable medium of claim 5 wherein the first chunk is a chunk of video, and wherein the segment routing header is configured to identify at least the first chunk requested by the client. 7. The tangible, non-transitory computer-readable medium of claim 5 wherein the first chunk is a chunk of audio. 8. The tangible, non-transitory computer-readable medium of claim 5 wherein the packet is included in traffic, and wherein the computer program code is further configured to: terminate the traffic if it is determined that the network endpoint has the first chunk. 9. An apparatus comprising: a processor; a data storage arrangement, the data storage arrangement configured to store a set of chunks; an input/output (I/O) interface, the I/O interface arranged to obtain a packet from a client via a first network segment, the packet including a segment routing header having a list of addresses including a first chunk address arranged to identify a first chunk requested by the client; and logic arranged to be executed by the processor, the logic being configured to identify the first chunk using the packet and to determine if the first chunk is included in the set of chunks, wherein the logic is further configured to provide the first chunk to the client if it is determined that the first chunk is included in the set of chunks and to cause the I/O interface to provide the packet to at least a second segment if it is determined that the first chunk is not included in the set of chunks, wherein the first chunk address is a last address included in the list of addresses, the list of addresses including a plurality of addresses, the last address being a V6 content descriptor (v6CD) that identifies the first chunk, and wherein other addresses in the list of addresses identify endpoints that may be asked for the first chunk. 10. A method comprising: obtaining a packet at a network endpoint, the packet being obtained from a client via a first segment, the packet having a segment routing header, the segment routing header including a list of addresses attached to a chunk entry, wherein the packet is configured to identify at least a first chunk requested by the client, wherein the first chunk is a chunk of video, and wherein the segment routing header is configured to identify at least the first chunk requested by the client; identifying, at the network endpoint, the at least first chunk using the packet; determining at the network endpoint if the network endpoint has the first chunk; providing the first chunk from the network endpoint to the client if it is determined that the network endpoint has the first chunk; and providing the packet to at least a second segment if it is determined that the network endpoint does not have the first chunk, wherein the list of addresses includes a plurality of addresses, and wherein a last address in the list of addresses is a content identifier corresponding to the at least first chunk, the CID being an address in which content information is included, the content information including at least one selected from a group including a format, a resolution, a quality, and a time code.
Information retrieval; Database structures therefor; File system structures therefor · CPC title
using information identifiers, e.g. uniform resource locators [URL] · CPC title
involving handling client requests (scheduling or organising the servicing of application requests H04L67/60) · CPC title
Reference data, e.g. a movie identifier for ordering a movie or a product identifier in a home shopping application · CPC title
Address processing for routing · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.