Content delivery network routing using border gateway protocol

US11729291B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-11729291-B2
Application numberUS-202117499487-A
CountryUS
Kind codeB2
Filing dateOct 12, 2021
Priority dateAug 9, 2011
Publication dateAug 15, 2023
Grant dateAug 15, 2023

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

An announcement protocol may allow disparate, and previously incompatible, content delivery network caches to exchange information and cache content for one another. Announcement data may be stored by the respective caches, and used to determine whether a cache is able to service an incoming request. URL prefixes may be included in the announcements to identify the content, and longest-match lookups may be used to help determine a secondary option when a first cache determines that it lacks a requested content.

First claim

Opening claim text (preview).

The invention claimed is: 1. A method comprising: determining, by a first cache device, a first value indicating a first quantity of one or more cache layers, within a caching system, between the first cache device and a server; receiving, by the first cache device and from a second cache device, information indicating: an identifier associated with a content item, and a second value indicating a second quantity of one or more cache layers, within the caching system, between the second cache device and the server; and routing, by the first cache device and based on a comparison between the first value and the second value, a request associated with the identifier to the second cache device. 2. The method of claim 1 , wherein the identifier comprises an alphanumeric string that is not a fully qualified domain name. 3. The method of claim 1 , further comprising mapping the identifier with a corresponding routable address. 4. The method of claim 1 , wherein the receiving of the information comprises receiving a border gateway protocol (BGP) announcement message that comprises the information, wherein the BGP announcement message further comprises a BGP announcement community tag, and wherein the method further comprises designating, based on the BGP announcement community tag, the second cache device as belonging in a priority group. 5. The method of claim 1 , wherein the routing of the request comprises routing the request based on the comparison, between the first value and the second value, indicating that the second cache device is closer than the first cache device to the server. 6. The method of claim 1 , wherein the information further indicates an address for the second cache device. 7. The method of claim 1 , wherein the caching system comprises a plurality of cache devices having values indicating respective positions relative to the server. 8. The method of claim 1 , wherein the routing of the request comprises: based on the comparison between the first value and the second value, storing the received information; and routing, based on the stored information, the request. 9. A first cache device comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the first cache device to: determine a first value indicating a first quantity of one or more cache layers, within a caching system, between the first cache device and a server; receive, from a second cache device, information indicating: an identifier associated with a content item, and a second value indicating a second quantity of one or more cache layers, within the caching system, between the second cache device and the server; and route, based on a comparison between the first value and the second value, a request associated with the identifier to the second cache device. 10. The first cache device of claim 9 , wherein the identifier comprises an alphanumeric string that is not a fully qualified domain name. 11. The first cache device of claim 9 , wherein the instructions, when executed by the one or more processors, further cause the first cache device to map the identifier with a corresponding routable address. 12. The first cache device of claim 9 , wherein the instructions, when executed by the one or more processors, cause the first cache device to receive the information by receiving a border gateway protocol (BGP) announcement message that comprises the information, wherein the BGP announcement message further comprises a BGP announcement community tag, and wherein the instructions, when executed by the one or more processors, further cause the first cache device to designate, based on the BGP announcement community tag, the second cache device as belonging in a priority group. 13. The first cache device of claim 9 , wherein the instructions, when executed by the one or more processors, cause the first cache device to route the request by routing the request based on the comparison, between the first value and the second value, indicating that the second cache device is closer than the first cache device to the server. 14. The first cache device of claim 9 , wherein the information further indicates an address for the second cache device. 15. The first cache device of claim 9 , wherein the caching system comprises a plurality of cache devices having values indicating respective positions relative to the server. 16. The first cache device of claim 9 , wherein the instructions, when executed by the one or more processors, cause the first cache device to route the request by: based on the comparison between the first value and the second value, storing the received information; and routing, based on the stored information, the request. 17. A non-transitory computer-readable medium storing instructions that, when executed, cause: determining, by a first cache device, a first value indicating a first quantity of one or more cache layers, within a caching system, between the first cache device and a server; receiving, by the first cache device and from a second cache device, information indicating: an identifier associated with a content item, and a second value indicating a second quantity of one or more cache layers, within the caching system, between the second cache device and the server; and routing, by the first cache device and based on a comparison between the first value and the second value, a request associated with the identifier to the second cache device. 18. The non-transitory computer-readable medium of claim 17 , wherein the identifier comprises an alphanumeric string that is not a fully qualified domain name. 19. The non-transitory computer-readable medium of claim 17 , wherein the instructions, when executed, further cause mapping, by the first cache device, the identifier with a corresponding routable address. 20. The non-transitory computer-readable medium of claim 17 , wherein the instructions, when executed, cause the receiving of the information by receiving a border gateway protocol (BGP) announcement message that comprises the information, wherein the BGP announcement message further comprises a BGP announcement community tag, and wherein the instructions, when executed, further cause designating, based on the BGP announcement community tag, the second cache device as belonging in a priority group. 21. The non-transitory computer-readable medium of claim 17 , wherein the instructions, when executed, cause the routing of the request by routing the request based on the comparison, between the first value and the second value, indicating that the second cache device is closer than the first cache device to the server. 22. The non-transitory computer-readable medium of claim 17 , wherein the information further indicates an address for the second cache device. 23. The non-transitory computer-readable medium of claim 17 , wherein the caching system comprises a plurality of cache devices having values indicating respective positions relative to the server. 24. The non-transitory computer-readable medium of claim 17 , wherein the instructions, when executed, cause the routing of the request by: based on the comparison between the first value and the second value, storing the received information; and routing, based on the stored information, the request.

Assignees

Inventors

Classifications

  • H04L67/563Primary

    Data redirection of data network streams · CPC title

  • H04L67/288Primary

    Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level · CPC title

  • Storing data temporarily at an intermediate stage, e.g. caching · CPC title

  • Routing a service request depending on the request content or context · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US11729291B2 cover?
An announcement protocol may allow disparate, and previously incompatible, content delivery network caches to exchange information and cache content for one another. Announcement data may be stored by the respective caches, and used to determine whether a cache is able to service an incoming request. URL prefixes may be included in the announcements to identify the content, and longest-match lo…
Who is the assignee on this patent?
Comcast Cable Comm Llc
What technology area does this patent fall under?
Primary CPC classification H04L67/563. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Aug 15 2023 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).