Distributed server architecture for supporting a predictive content pre-fetching service for mobile device users

• US 10,063,653 B2
• Filed: 12/29/2014
• Issued: 08/28/2018
• Est. Priority Date: 12/29/2014
• Status: Active Grant

• Current Assignee: Akamai Technologies, Inc.
• Original Assignee: Akamai Technologies, Inc.
• Inventors: Balakrishnan, Prasandh, Luciani, James V., Aysola, Ravi S., D'Addio, Richard G., Gensch, Lawrence, Shaikh, Ittehad
• Primary Examiner(s): Donabed, Ninos
• Application Number:
  US14/584,820
• Publication Number:
  US 20160191664A1
• Time in Patent Office: 1,338 Days
• Field of Search: 709203
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/5054 Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
• CPC Class Codes: H04L 41/5096 wherein the managed service relates to distributed or central networked applications
• 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/2895 Intermediate processing functionally located close to the data provider application, e.g. reverse proxies
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/55 Push-based network services
• 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/5683 Storage of data provided by user terminals, i.e. reverse caching
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

A content delivery network (CDN) is enhanced to enable mobile network operators (MNOs) to provide their mobile device users with a content prediction and pre-fetching service. Preferably, the CDN enables the service by providing infrastructure support comprising a client application, and a distributed predictive pre-fetching function. The client application executes in the user'"'"'s mobile device and enables the device user to subscribe to content (e.g., video) from different websites, and to input viewing preferences for such content (e.g.: “Sports: MLB: Boston Red Sox”). This user subscription and preference information is sent to the predictive pre-fetching support function that is preferably implemented within or across CDN server clusters. A preferred implementation uses a centralized back-end infrastructure, together with front-end servers positioned in association with the edge server regions located nearby the mobile core network. The predictive pre-fetch service operates on the user'"'"'s behalf in accordance with the user preference information.

Claims

1. Apparatus associated with an overlay network operating as a content delivery network (CDN) on behalf of sites of participating content providers, comprising:

a set of hardware processors;

computer memory associated with each hardware processor; and

computer program instructions stored in computer memory and executed by a hardware processor as;

an instance of a front-end server application configured to execute in association with an CDN edge server located proximal to a mobile network operator (MNO) core network that is distinct from the overlay network, and a back-end server application configured to execute in the CDN to provide support for multiple instances of the front-end server application, wherein bifurcation of functionality provided by the front-end server application instance and the back-end server application improves an operation of the overlay network operating as a CDN;

wherein the back-end server application is operative to (i) receive and store, for each of a set of mobile devices, a set of preferences, the set of preferences including an identification of given content that originates with the CDN participating content providers and that is deliverable over the CDN, and that an end user of a mobile device has provided an indication is desired to be predictively prefetched to the end user mobile device;

(ii) based at least in part on the preferences associated with a particular end user mobile device, predict content of interest, the content of interest being content then available to be delivered from the CDN;

(iii) generate a manifest for the particular end user mobile device identifying the content of interest and its location; and

(iv) provide the manifest to a particular instance of the front-end server application;

wherein the particular instance of the front-end server application is operative to (i) notify the particular end user mobile device of availability of the manifest; and

(ii) responsive to a request, provide the manifest to the particular end user mobile device;

wherein the particular instance of the front-end server application is further operative to wake-up an end user mobile device in response to receiving the manifest from the back-end server application.

2. The apparatus as described in claim 1 wherein the particular instance of the front-end server application provides the manifest for each of a set of mobile devices that are connected to the front-end server application instance.

3. The apparatus as described in claim 2 wherein the back-end server application provides the particular instance of the front-end server application with a manifest for each of the set of mobile devices that are connected to the front-end server application instance.

4. The apparatus as described in claim 1 wherein the back-end server application is further operative identify the content of interest by monitoring changes to one or more content provider sites.

5. The apparatus as described in claim 4 wherein the changes are received by the back-end server application by one of:

crawling the content provider site, receiving a syndication feed from the content provider site, and receiving change notifications published by the content provider site over an application programming interface (API).

6. The apparatus as described in claim 1 wherein the particular instance of the front-end server application further is operative to receive from an end user mobile device consumption information, the consumption information indicating whether the content of interest has been viewed.

7. The apparatus as described in claim 6 wherein the back-end server application is further operative to modify data collected by the overlay network in association with the automated retrieval of the content of interest in accordance with the consumption information.

8. The apparatus as described in claim 1 wherein at least the manifest is provided to the end user mobile device as zero-rated data.

9. The apparatus as described in claim 6 wherein the content of interest also is predicted based at least in part on the consumption information.

10. Apparatus associated with an overlay network operating as a content delivery network (CDN) on behalf of sites of participating content providers, comprising:

a set of hardware processors;

computer memory associated with each hardware processor; and

computer program instructions stored in computer memory and executed by a hardware processor as;

a client application, an instance of a front-end server application configured to execute in association with an CDN edge server located proximal to a mobile network operator (MNO) core network that is distinct from the overlay network, and a back-end server application configured to execute in the CDN to provide support for multiple instances of the front-end server application, wherein bifurcation of functionality provided by the front-end server application instance and the back-end server application improves an operation of the overlay network operating as a CDN;

wherein the back-end server application is operative to (i) receive and store, for each of a set of mobile devices, a set of preferences, the set of preferences including an identification of given content that originates with the CDN participating content providers and that is deliverable over the CDN, and that an end user of a mobile device has provided an indication is desired to be predictively prefetched to the end user mobile device;

(ii) based at least in part on the preferences associated with a particular end user mobile device, predict content of interest, the content of interest being content then available to be delivered from the CDN;

(iii) generate a manifest for the particular end user mobile device identifying the content of interest and its location; and

(iv) provide the manifest to a particular instance of the front-end server application;

wherein the particular instance of the front-end server application is operative to (i) notify the particular end user mobile device of availability of the manifest; and

(ii) responsive to a request, provide the manifest to the particular end user mobile device;

wherein the particular instance of the front-end server application is further operative to wake-up the client application in response to receiving the manifest from the back-end server application;

wherein the client application is operative to (i) provide the set of preferences;

(ii) issue the request;

(iii) receive the manifest; and

(iv) control the end user mobile device to automatically retrieve to the mobile device from the CDN edge server the content of interest.

11. The apparatus as described in claim 10 wherein the particular instance of the front-end server application provides the manifest for each of a set of mobile devices that are connected to the front-end server application instance.

12. The apparatus as described in claim 11 wherein the back-end server application provides the particular instance of the front-end server application with a manifest for each of the set of mobile devices that are connected to the front-end server application instance.

13. The apparatus as described in claim 10 wherein the back-end server application is further operative identify the content of interest by monitoring changes to one or more content provider sites.

14. The apparatus as described in claim 13 wherein the changes are received by the back-end server application by one of:

crawling the content provider site, receiving a syndication feed from the content provider site, and receiving change notifications published by the content provider site over an application programming interface (API).

15. The apparatus as described in claim 10 wherein the particular instance of the front-end server application further is operative to receive from the client application consumption information, the consumption information indicating whether the content of interest has been viewed.

16. The apparatus as described in claim 15 wherein the back-end server application is further operative to modify data collected by the overlay network in association with the automated retrieval of the content of interest in accordance with the consumption information.

17. The apparatus as described in claim 10 wherein at least the manifest is provided to the end user mobile device as zero-rated data.

18. The apparatus as described in claim 15 wherein the content of interest also is predicted based at least in part on the consumption information.