Context sensitive object management

• US 10,623,408 B1
• Filed: 04/02/2012
• Issued: 04/14/2020
• Est. Priority Date: 04/02/2012
• Status: Active Grant

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Marshall, Bradley E., Saraf, Tal, Howard, Craig W., Dunlap, David Alexander, Maniscalco, Nicholas J.
• Primary Examiner(s): Srivastava, Vivek
• Assistant Examiner(s): Raza, Muhammad
• Application Number:
  US13/437,274
• Time in Patent Office: 2,934 Days
• Field of Search: 709226, 709201, 711124
• CPC Class Codes: G06F 2221/2137 Time limited access, e.g. to a computer or data
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

Aspects of the present disclosure relate to the generation and delivery of content including unique and shared components. A content delivery network service provider can obtain requests for content from client computing devices. Based on information provided in the request or otherwise managed by executable code on the client computing device, the CDN service provider obtains one or more pieces of content that may be shared by more than one user or client computing devices. Additionally, the CDN service provider obtains one or more pieces of content that will not be shared by more than one user or more than one client computing device. Responsive to the content request, the CDN service provider can combine the one or more pieces of shared content and the one or more pieces of unique content and deliver the combined content to the requested client computing device.

Claims

1. A method comprising:

obtaining, at content delivery network (CDN) service provider, a request, from a client computing device, for a resource included in a Web page, the resource unique to a user of the client computing device, wherein the resource is associated with expiration criterion and context criteria for the resource, wherein the expiration criterion corresponds to a time to live, wherein the context criteria specifies a user identifier corresponding to the resource, a resource type, and a context value, wherein the resource type includes a dynamic classification of the resource, wherein the resource corresponds to a dynamic resource associated with an account corresponding to the user identifier, and wherein the context value includes timing information for the resource, wherein the timing information associated with the resource is different from the expiration criterion, wherein the timing information associated with the resource includes a threshold related to a number of times the resource is requested or provided, wherein the CDN service provider processes requests for resources on behalf of an original content provider, wherein the request is a domain name system (DNS) query including identification of the resource in a DNS portion of a uniform resource locator (URL) corresponding to the DNS query;

causing storage, from the original content provider, of the resource in a resource cache component of the CDN service provider with the context criteria;

obtaining context change information, the context change information including information for determining an updated number of times the resource is requested or provided;

determining the resource stored in the resource cache component is invalid by comparing the threshold included in the context criteria with the updated number of times the resource is requested or provided; and

causing the resource to no longer be maintained in the resource cache component based on the determination that the resource in the resource cache component is invalid, wherein the expiration criterion associated with the resource has not been satisfied.

2. The method as recited in claim 1, wherein the context criteria correspond to a cookie.

3. A method comprising:

obtaining, at content delivery network (CDN) service provider, a request, from a client computing device, for a resource included in a Web page, the resource unique to a user of the client computing device, wherein the resource is associated with expiration criterion and context criteria, wherein the CDN service provider processes requests for resources on behalf of an original content provider, and wherein the request is a domain name system (DNS) query including identification of the resource in a DNS portion of a uniform resource locator (URL) corresponding to the DNS query;

causing storage, from the original content provider, of the resource in a resource cache component of the CDN service provider with the context criteria;

obtaining context change information, the context change information including information for determining an updated number of times the resource is requested or provided;

determining the resource stored in the resource cache component is invalid by comparing the context criteria with the context change information; and

prior to satisfaction of the expiration criterion, causing the resource to no longer be maintained in the resource cache component based on determination that the resource stored in the resource cache component is invalid,

wherein the expiration criterion corresponds to a maximum amount of time in which the resource is considered to be valid in the resource cache component,

wherein the context criteria includes a user identifier corresponding to the resource, a resource type, and a context value, wherein the resource type includes a dynamic classification of the resource, and wherein the context value includes timing information for the resource and can be utilized to determine whether the resource can be maintained in the resource cache component,

wherein the timing information associated with the resource is different from the expiration criterion,

wherein the timing information associated with the resource includes a threshold related to a number of times the resource is requested or provided, and

wherein the resource corresponds to a dynamic resource associated with an account corresponding to the user identifier.

4. The method as recited in claim 3, wherein determining the resource in the resource cache component is invalid includes processing the context change information responsive to obtaining the context change information.

5. The method as recited in claim 3, wherein determining the resource in the resource cache component is invalid includes processing the context change information responsive to obtaining a subsequent request for the resource.

6. The method as recited in claim 3, further comprising updating the context criteria.

7. The method as recited in claim 3, wherein the resource includes one of an image, a document, video file, or audio file.

8. The method as recited in claim 3 further comprising updating the context criteria with the context change information.

9. The method as recited in claim 3, wherein the resource type includes information relating to different characterizations or functions of information of the user.

10. A system comprising:

memory for storing computer-readable instructions; and

one or more processors of a content delivery network (CDN) service provider that processes resources on behalf of an original content provider, the one or more processors, executing the computer-readable instructions, that cause one or more computing devices associated with the one or more processors to;

obtain a request, from a client computing device, for a resource included in a Web page, the resource unique to a user of the client computing device, wherein the resource is associated with expiration criterion and context criteria, and wherein the request is a domain name system (DNS) query including identification of the resource in a DNS portion of a uniform resource locator (URL) corresponding to the DNS query;

cause storage, from the original content provider, of the resource in a resource cache component of the CDN service provider with the context criteria;

obtain context change information, the context change information corresponding to information associated with a most recent object value for the resource;

determine the resource stored in the resource cache component is invalid by comparing the context criteria with the context change information; and

prior to satisfaction of the expiration criterion, cause the resource to no longer be maintained in the resource cache component based on the determination that the resource stored in the resource cache component is invalid,

wherein the expiration criterion corresponds to a maximum amount of time in which the resource is considered to be valid in the resource cache component,

wherein the context criteria includes a user identifier corresponding to the resource, a resource type, and a context value, wherein the resource type includes a dynamic classification of the resource, and wherein the context value includes timing information for the resource and can be utilized to determine whether the resource can be maintained in a resource cache component,

wherein the timing information associated with the resource is different from the expiration criterion,

wherein the timing information associated with the resource includes a threshold related to a number of times the resource is requested or provided, and

wherein the resource corresponds to a dynamic resource associated with an account corresponding to the user identifier.

11. The system as recited in claim 10, wherein the one or more processors process the context criteria.

12. The system as recited in claim 10, wherein the resource includes one of a document, video file, or audio file.

13. The system as recited in claim 10, wherein the one or more processors update the context criteria with the context change information.

14. The system as recited in claim 10, wherein the one or more processors determine the resource in the resource cache component is invalid based upon receipt of the context change information.

15. The system as recited in claim 10, wherein the one or more processors determine the resource in the resource cache component is invalid based upon receipt of a subsequent request for the resource.