Uniformity of instructions for content requests and responses in a content delivery network

Patent metadata

Field	Value
Publication number	US-11457091-B2
Application number	US-202117362079-A
Country	US
Kind code	B2
Filing date	Jun 29, 2021
Priority date	Feb 24, 2021
Publication date	Sep 27, 2022
Grant date	Sep 27, 2022

Abstract

Examples described herein relate to standardizing content requests and responses in a content delivery network (CDN). An edge node receives a control object including sets of instructions each implementing portions of a customer's business logic. The edge node may receive, from a client, a content request identifying a content item, and may apply a set of the instructions which causes the edge node to (i) determine whether any changes are needed for the benefit of a cache server and whether any changes are need for the benefit of an origin server, and (ii) generate a processed client request identifying the content item and including, if needed, any changes for the benefit of the cache server and the origin server. The edge node transmits the processed client request to the cache server, receives a response from the cache server, and transmits a processed client response to the client.

First claim

What is claimed is:

1. A computer-implemented method for standardizing content requests and responses in a content delivery network (CDN), the computer-implemented method comprising:
receiving, by an edge node, a control object from a central authority, the control object comprising a client request sheet implementing at least a portion of a customer's business logic;
receiving, by the edge node, a content request from a client, the content request identifying a content item;
applying, by the edge node, the client request sheet responsive to the content request, wherein applying the client request sheet includes determining, by the edge node, any change to the content request is needed for the benefit of a cache server and any change to the content request is needed for the benefit of an origin server, (ii) generating, by the edge node, a processed client request identifying the content item and including any changes to the content request for the benefit of the cache server and the origin server, (iii) authenticating, by the edge node, the client, and (iv) indicating in the processed client request, by the edge node, that the client is authenticated;
transmitting, by the edge node, the processed client request to the cache server;
receiving, by the edge node, a response to the processed client request from the cache server;
transmitting, by the edge node, the processed client response to the client;
receiving, by the cache server, the processed client request;
determining, by the cache server, that the cache server stores the content item identified in the processed client request;
based on the cache server determining that it does not store the content item, transmitting a post-cache processed client request to an upstream computer;
receiving, by the upstream computer, the control object from the central authority and the post-cache processed client request from the cache server, the control object further comprising an origin request sheet implementing at least a portion of the customer's business logic;
applying, by the upstream computer, the origin request sheet responsive to the post-cache processed client request, the origin request sheet causing that node to (i) determine any change to the post-cache processed client request is needed for the benefit of the origin server and (ii) generate a processed origin request identifying the content item and including any changes to the post-cache processed client request for the benefit of the origin server; and
transmitting, by the upstream computer, the processed origin request to the origin server, wherein
based on the processed client request indicating that the client is authenticated, neither the cache server nor the origin server performs an additional authentication of the client.

2. The computer-implemented method of claim 1 , wherein the processed origin request is identical to the post-cache processed client request.

3. The computer-implemented method of claim 1 , wherein the processed origin request is identical to the processed client request.

4. The computer-implemented method of claim 1 , wherein the origin server generates an origin response including the content item identified in the processed origin request and transmits the origin response to a downstream computer.

5. The computer-implemented method of claim 4 , the control object further comprising an origin response sheet implementing at least a portion of the customer's business logic, the method further comprising:
receiving, by the downstream computer, the origin response;
applying, by the downstream computer, the origin response sheet responsive to the origin response, the origin response sheet causing that node to (i) determine any change to the origin response is needed for the benefit of the cache server and (ii) generate a processed origin response including the content item and, if needed, any changes to the origin response for the benefit of the cache server.

6. The computer-implemented method of claim 5 , further comprising:
receiving, by the cache server, the processed origin response; and
transmitting to the edge node a cached processed origin response.

7. The computer-implemented method of claim 6 , wherein the cached processed origin response is identical to the processed origin response.

8. The computer-implemented method of claim 6 , wherein:
the control object further comprises a client response sheet implementing at least a portion of the customer's business logic;
the response that the edge node receives to the processed client request comprises the cached processed origin response; and
the method further comprises applying, by the edge node, the client response sheet responsive to the cached processed origin response, the client response sheet causing the edge node to (i) determine any changes to the processed origin response are needed for the benefit of the client and (ii) generate the processed client response including the content item and, if needed, any changes to the processed origin response for the benefit of the client.

9. The computer-implemented method of claim 8 , wherein the processed client response is identical to the cached processed origin response.

10. The computer-implemented method of claim 8 , wherein the processed client response is identical to the processed origin response.

11. The computer-implemented method of claim 8 , wherein the processed client response is identical to the origin response.

12. A computer system comprising a processor, a storage device, and a network interface, the processor being configured to implement operations comprising:
receiving a control object from a central authority via the network interface, the control object comprising client request sheet implementing at least a portion of a customer's business logic;
storing the received control object in the storage device;
receiving a content request from a client, the content request identifying a content item;
applying the client request sheet responsive to the content request, wherein applying the client request sheet includes determining, by the computer system, any change to the content request is needed for the benefit of a cache server and any change to the content request is needed for the benefit of an origin server, (ii) generating, by the computer system, a processed client request identifying the content item and including any changes to the content request for the benefit of the cache server and the origin server, (iii) authenticating, by the computer system, the client, and (iv) indicating in the processed client request, by the computer system, that the client is authenticated;
transmitting the processed client request to the cache server;
receiving a response to the processed client request from the cache server;
transmitting a processed client response to the client;
receiving, by the cache server, the processed client request;
determining, by the cache server, that the cache server stores the content item identified in the processed client request;
based on the cache server determining that it does not store the content item, transmitting a post-cache processed client request to an upstream computer;
receiving, by the upstream computer, the control object from the central authority and the post-cache processed client request from the cache server, the control object further comprising an origin request sheet implementing at least a portion of the customer's business logic;
applying, by the upstream computer, the origin request sheet responsive to the post-cache processed client request, the origin request sheet causing that node to (i) determine any change to the post-cache processed cli

Assignees

• Level 3 Communications Llc

Inventors

• Crowder William
• Jensen Daniel
• Jakobowski Pawel
• Lipstone Laurence
• Power William

Classifications

• G06F15/17331

  Distributed shared memory [DSM], e.g. remote direct memory access [RDMA] · CPC title

• H04L67/568 Primary

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

• H04L63/083

  using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226) · CPC title

• H04L67/10

  in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) · CPC title