Methods and apparatus for content delivery via browser cache extension

• US 10,366,137 B2
• Filed: 08/05/2015
• Issued: 07/30/2019
• Est. Priority Date: 08/15/2014
• Status: Active Grant

• Current Assignee: InterDigital Patent Holdings, Inc. (InterDigital, Inc.)
• Original Assignee: InterDigital Patent Holdings, Inc. (InterDigital, Inc.)
• Inventors: Li, Jun, Purkayastha, Debashish, Reznik, Alexander
• Primary Examiner(s): Arjomandi, Noosha
• Application Number:
  US15/503,935
• Publication Number:
  US 20170277805A1
• Time in Patent Office: 1,455 Days
• CPC Class Codes: G06F 12/0615 Address space extension
• CPC Class Codes: G06F 16/183 Provision of network file services by network file servers, e.g. by using NFS, CIFS network file access protocols H04L67/1097
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching

Abstract

Embodiments include methods, systems, and apparatuses for content delivery using shared caching, and more specifically, a browser cache extension (BCE) between a local browser cache and a remote cache located on an edge server. In an embodiment, a remote BCE function on the edge server may create a shared cache folder containing a remote cache and an remote cache index file. A local BCE function in the local browser may be able to access the shared cache folder via a network file system (NFS) protocol. The local BCE function may merge the remote index file with a local index file from the local browser and retrieve the remote cache at the local browser.

Claims

1. A method of content delivery using a shared cache, the method comprising:

receiving access to a read-only shared folder located in a remote cache of an edge server of a small cell network over a network file system (NFS) protocol, wherein the read-only shared folder comprises pre-fetched content retrieved from a content owner, and wherein the pre-fetched content is indicated to the edge server by a mobile-content distribution/delivery network (mobile-CDN) having a first interface with the edge server and a second interface with the content owner;

mounting the read-only shared folder at a local browser cache of a user device using the NFS protocol;

reading a remote index file from the read-only shared folder, wherein the remote index file comprises one or more remote entries indicating the pre-fetched content;

merging the remote index file with a local index file in the local browser cache to create a merged index file, wherein the local index file comprises one or more local entries indicating local content;

checking the merged index file for an entry corresponding to a HTTP/HTTPS request; and

upon determining that content matching the HTTP/HTTPS request is present in the pre-fetched content in the remote cache, reading the requested content over the NFS protocol.

2. The method of claim 1, wherein the mounting the read-only shared folder comprises:

enabling a cache extension in the local browser of the user device;

specifying the NFS protocol;

specifying the location of the read-only shared folder; and

specifying a local mount point.

3. The method of claim 1, wherein the providing the merging the remote index file with the local index file comprises:

creating one or more symbolic links in the local browser cache for each of the one or more remote entries in the remote index file; and

adding the one or more symbolic links to the local index file.

4. The method of claim 1,

wherein the reading the remote index file is performed at a configured update frequency.

5. The method of claim 1, wherein the merging the remote index file with the local index file comprises:

checking a timestamp of one or more remote entries in the remote index file;

comparing the timestamp of the one or more remote entries to a timestamp of one or more local entries in the local index file, wherein the one or more remote entries and the one or more local entries have corresponding keys; and

upon determining that the timestamp of the one or more remote entries is newer than the timestamp of the one or more local entries, replacing the one or more local entries with one or more symbolic links to the one or more remote entries.

6. The method of claim 1,

determining that the requested content is signed by the content owner prior to the using the requested content.

7. The method of claim 1, further comprising:

determining that the remote index file is signed by the mobile-CDN prior to the reading the requested content.

8. A device for receiving content using a shared cache, the device comprising:

a processor, operatively coupled to a transceiver, configured to receive access to a read-only shared folder in a remote cache of an edge server of a small cell network over a network file system (NFS) protocol, wherein the read-only shared folder comprises pre-fetched content retrieved from a content owner, and wherein the pre-fetched content is indicated to the edge server by a mobile-content distribution/delivery network (mobile-CDN) having a first interface with the edge server and a second interface with the content owner;

the processor further configured to mount the read-only shared folder at a local browser cache using the NFS protocol;

the processor further configured to read a remote index file from the read-only shared folder, wherein the remote index file comprises one or more remote entries indicating the pre-fetched content;

the processor further configured to merge the remote index file with a local index file in the local browser cache to create a merged index file, wherein the local index file comprises one or more local entries indicating local content;

the processor further configured to check the merged index file for an entry corresponding to a HTTP/HTTPS request; and

upon determining that content matching the HTTP/HTTPS request is present in the pre-fetched content in the remote cache, the processor further configured to read the requested content over the NFS protocol.

9. The device of claim 8, wherein the processor is further configured to determine that the requested content is signed by the content owner prior to using the requested content.

10. The device of claim 8, wherein the mounting the read-only shared folder comprises:

enabling a cache extension in the local browser of the user device;

specifying the NFS protocol;

specifying the location of the read-only shared folder; and

specifying a local mount point.

11. The device of claim 8, wherein the merging the remote index file with the local index file comprises:

creating one or more symbolic links in the local browser cache for each of the one or more remote entries in the remote index file; and

adding the one or more symbolic links to the local index file.

12. The device of claim 8, wherein the merging the remote index file with the local index file comprises:

checking a timestamp of the one or more remote entries in the remote index file;

comparing the timestamp of the one or more remote entries to a timestamp of one or more local entries in the local index file, wherein the one or more remote entries and the one or more local entries have corresponding keys; and

upon determining that the timestamp of the one or more remote entries is newer than the timestamp of the one or more local entries, replacing the one or more local entries with one or more symbolic links to the one or more remote entries.

13. The device of claim 8, wherein the reading the remote index file is performed at a configured update frequency.

14. The device of claim 8, wherein the processor is further configured to determine that the remote index file is signed by the mobile-CDN prior to using the requested content.