Choreographed caching

• US 9,936,039 B2
• Filed: 09/22/2014
• Issued: 04/03/2018
• Est. Priority Date: 09/22/2014
• Status: Active Grant

• Current Assignee: Belkin International Incorporated (Hon Hai Precision Industry Co., Ltd.)
• Original Assignee: Belkin International Incorporated (Hon Hai Precision Industry Co., Ltd.)
• Inventors: Kim, Ryan Yong
• Primary Examiner(s): Higa, Brendan
• Application Number:
  US14/493,199
• Publication Number:
  US 20160088113A1
• Time in Patent Office: 1,289 Days
• CPC Class Codes: H04L 12/2834 Switching of information between an external network and a home network access arrangements H04L12/2856
• CPC Class Codes: H04L 45/742 Route cache; Operation thereof
• CPC Class Codes: H04L 49/252 Store and forward routing
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/0464 using hop-by-hop encryption, i.e. wherein an intermediate entity decrypts the information and re-encrypts it before forwarding it
• CPC Class Codes: H04L 63/0471 applying encryption by an intermediary, e.g. receiving clear information at the intermediary and encrypting the received information at the intermediary before forwarding
• CPC Class Codes: H04L 63/168 above the transport layer
• 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/2885 Hierarchically arranged intermediate devices, e.g. for hierarchical caching
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/5681 Pre-fetching or pre-delivering data based on network characteristics
• CPC Class Codes: H04L 67/5682 Policies or rules for updating, deleting or replacing the stored data
• CPC Class Codes: H04L 67/60 Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources admission control or resource allocation H04L47/70

Abstract

A routing device capable of performing application layer data caching is described. Application data caching at a routing device can alleviate the bottleneck that an application data host may experience during high demands for application data. Requests for the application data can also be fulfilled faster by eliminating the network delays for communicating with the application data host. The techniques described can also be used to perform analysis of the underlying application data in the network traffic transiting though a routing device.

Claims

1. A computer implemented method comprising:

monitoring, by a computing device, requests received on a plurality of routing devices for application data corresponding to a network resource identifier;

aggregating the requests over a caching time window to derive an aggregated number of requests received on the plurality of routing devices;

determining that the aggregated number of requests received within the caching time window is above a caching threshold;

in response to determining the aggregated number of requests is above the caching threshold, notifying one or more of the plurality of routing devices to cache the application data;

after notifying the one or more of the plurality of routing devices to cache the application data, monitoring subsequent requests received on the plurality of routing devices for the application data;

aggregating the subsequent requests over a de-caching time window to derive an aggregated number of subsequent requests received on the plurality of routing devices;

determining that the aggregated number of subsequent requests received within the de-caching time window is below a de-caching threshold; and

in response to determining the aggregated number of subsequent requests is below the de-caching threshold, notifying the one or more of the plurality of routing devices to de-cache the application data.

2. The method of claim 1, wherein a duration of the caching time window is different than a duration of the de-caching time window.

3. The method of claim 1, wherein the caching threshold is different than the de-caching threshold.

4. The method of claim 1, further comprising:

notifying one or more additional routing devices that have not received a request for the application data to cache the application data.

5. The method of claim 4, further comprising:

instructing one or more of the plurality of routing devices to push the application data to the one or more additional routing devices.

6. The method of claim 1, wherein notifying the one or more of the plurality of routing devices to cache the application data includes notifying each of the one or more of the plurality of routing devices to cache a different portion of the application data.

7. A system, comprising:

one or more data processors; and

a non-transitory computer readable storage medium containing instructions which when executed on the one or more data processors, cause the one or more processors to perform operations including;

monitoring requests received on a plurality of routing devices for application data corresponding to a network resource identifier;

aggregating the requests over a caching time window to derive an aggregated number of requests received on the plurality of routing devices;

determining that the aggregated number of requests received within the caching time window is above a caching threshold;

in response to determining the aggregated number of requests is above the caching threshold, notifying one or more of the plurality of routing devices to cache the application data;

after notifying the one or more of the plurality of routing devices to cache the application data, monitoring subsequent requests received on the plurality of routing devices for the application data;

aggregating the subsequent requests over a de-caching time window to derive an aggregated number of subsequent requests received on the plurality of routing devices;

determining that the aggregated number of subsequent requests received within the de-caching time window is below a de-caching threshold; and

in response to determining the aggregated number of subsequent requests is below the de-caching threshold, notifying the one or more of the plurality of routing devices to de-cache the application data.

8. The system of claim 7, wherein a duration of the caching time window is different than a duration of the de-caching time window.

9. The system of claim 7, wherein the caching threshold is different than the de-caching threshold.

10. The system of claim 7, wherein the operations further include:

notifying one or more additional routing devices that have not received a request for the application data to cache the application data.

11. The system of claim 10, wherein the operations further include:

instructing one or more of the plurality of routing devices to push the application data to the additional routing devices.

12. The system of claim 7, wherein notifying the one or more of the plurality of routing devices to cache the application data includes notifying each of the one or more of the plurality of routing devices to cache a different portion of the application data.

13. A computer-program product tangibly embodied in a non-transitory machine-readable storage medium, including instructions configured to cause a data processing apparatus to perform operations comprising:

monitoring requests received on a plurality of routing devices for application data corresponding to a network resource identifier;

aggregating the requests over a caching time window to derive an aggregated number of requests received on the plurality of routing devices;

determining that the aggregated number of requests received within the caching time window is above a caching threshold;

in response to determining the aggregated number of requests is above the caching threshold, notifying one or more of the plurality of routing devices to cache the application data;

after notifying the one or more of the plurality of routing devices to cache the application data, monitoring subsequent requests received on the plurality of routing devices for the application data;

aggregating the subsequent requests over a de-caching time window to derive an aggregated number of subsequent requests received on the plurality of routing devices;

determining that the aggregated number of subsequent requests received within the de-caching time window is below a de-caching threshold; and

in response to determining the aggregated number of subsequent requests is below the de-caching threshold, notifying the one or more of the plurality of routing devices to de-cache the application data.

14. The computer-program product of claim 13, wherein a duration of the caching time window is different than a duration of the de-caching time window.

15. The computer-program product of claim 13, wherein the caching threshold is different than the de-caching threshold.

16. The computer-program product of claim 13, wherein the operations further include:

notifying one or more addition al routing devices that have not received a request for the application data to cache the application data.

17. The computer-program product of claim 16, wherein the operations further include:

instructing one or more of the plurality of routing devices to push the application data to the additional routing devices.

18. The computer-program product of claim 13, wherein notifying the one or more of the plurality of routing devices to cache the application data includes notifying each of the one or more of the plurality of routing devices to cache a different portion of the application data.