CLIENT SIDE INITIATED CACHING CONTROL

• US 20150373140A1
• Filed: 06/20/2013
• Published: 12/24/2015
• Est. Priority Date: 06/26/2012
• Status: Abandoned Application

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.), NDS Limited (Cisco Systems, Inc.)
• Inventors: SANDLER, Leonid, HAENEL, Arie, AVITZUR, Tomer
• Application Number:
  US14/410,571
• Publication Number:
  US 20150373140A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: H04L 2209/72 Signcrypting, i.e. digital signing and encrypting simultaneously
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/5682 Policies or rules for updating, deleting or replacing the stored data
• CPC Class Codes: H04L 9/3247 involving digital signatures

Abstract

A method, system and related apparatus are described, the system comprising a caching-capable element which is part of a data network, which receives a request from a downstream client device, the request including a content request, the content request including a Universal Resource Identifier (URI) and an explicit caching request, the caching request includes a unique content identifier which is independent of the URI, and optional expiration date information, a comparator included at the caching-capable element which compares the caching request against the existing cached content, and if the requested content is cached then the caching-capable element forwards the cached copy of the requested content to the client device, and if the requested content is not cached, then the caching-capable element forwards the request to a further upstream device, and, upon reception of the requested content from the further upstream device, returns the requested content to the requesting downstream device, and caches the requested content for further distribution to other clients. Related methods, systems and apparatus are also described.

Claims

1. A system comprising:

a caching-capable element which is part of a data network, which receives a request from a downstream client device, the request including a content request, the content request comprising a Universal Resource Identifier (URI) and an explicit caching request, the caching request comprises;

a unique content identifier which is independent of the URI; and

optional expiration date information;

a comparator comprised at the caching-capable element which compares the caching request against the existing cached content; and

if the requested content is cached then the caching-capable element forwards the cached copy of the requested content to the client device; and

if the requested content is not cached, then the caching-capable element forwards the request to a further upstream device, and, upon reception of the requested content from the further upstream device, returns the requested content to the requesting downstream device, and caches the requested content for further distribution to other clients.

2. The system according to claim 1 and further comprising:

a cryptographic engine which verifies one of a symmetric cryptographic digital signature or an asymmetric cryptographic digital signature to the caching request; and

the caching-capable element only performs the caching operation if the caching request is properly signed;

otherwise

the caching-capable element either;

forwards the request to the further upstream device and does not perform the caching of the content;

or

denies the request as an invalid request.

3. The system according to claim 1 wherein the caching request refers only to a certain part of the requested content.

4. The system according to claim 3 wherein the content request as accompanied with digitally signed caching request as well as unique cryptographically protected and authenticated access control token confirming that this specific user device is authorized to access the requested content, in which case, the request will be refused if the client failed to present a properly signed access token.

5. A method comprising:

receiving a request from a downstream client device, at a caching-capable element which is part of a data network, the request including a content request, the content request comprising a Universal Resource Identifier (URI) and an explicit caching request, the caching request comprising;

a unique content identifier which is independent of the URI; and

optional expiration date information;

comparing at a comparator comprised at the caching-capable element which compares the caching request against the existing cached content; and

if the requested content is cached then the caching-capable element forwards the cached copy of the requested content to the client device; and

if the requested content is not cached, then the caching-capable element forwards the request to a further upstream device, and, upon reception of the requested content from the further upstream device, returns the requested content to the requesting downstream device, and caches the requested content for further distribution to other clients.

6. The method according to claim 5 and further comprising:

verifying at a cryptographic engine one of a symmetric cryptographic digital signature or an asymmetric cryptographic digital signature to the caching request; and

performing the caching operation by the caching-capable element only if the caching request is properly signed;

otherwise

the caching-capable element performs one of;

forwarding the request to the further upstream device and not performing the caching of the content;

or

denying the request as an invalid request.

7. The method according to claim 5 wherein the caching request refers only to a certain part of the requested content.

8. The method according to claim 7 wherein the content request as accompanied with digitally signed caching request as well as unique cryptographically protected and authenticated access control token confirming that this specific user device is authorized to access the requested content, in which case, the request will be refused if the client failed to present a properly signed access token.