Predictive fetching of background data request in resource conserving manner

• US 10,299,161 B1
• Filed: 01/25/2019
• Issued: 05/21/2019
• Est. Priority Date: 07/26/2010
• Status: Active Grant

• Current Assignee: Seven Networks LLC (SoftBank Group Corp.)
• Original Assignee: Seven Networks LLC (SoftBank Group Corp.)
• Inventors: Petersen, Steve, Backholm, Ari, Luna, Michael
• Primary Examiner(s): Patel, Ajit
• Application Number:
  US16/258,483
• Publication Number:
  US 20190159062A1
• Time in Patent Office: 116 Days
• Field of Search: None
• CPC Class Codes: H04L 47/122 by diverting traffic away from congested entities
• CPC Class Codes: H04L 47/25 with rate being modified by the source upon detecting a change of network conditions
• CPC Class Codes: H04L 65/65 Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/2885 Hierarchically arranged intermediate devices, e.g. for hierarchical caching
• CPC Class Codes: H04L 67/289 Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/5683 Storage of data provided by user terminals, i.e. reverse caching
• 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
• CPC Class Codes: H04W 28/02 Traffic management, e.g. flow control or congestion control
• CPC Class Codes: H04W 28/0289 Congestion control load shedding arrangements in network planning H04W16/08; performing reselection for handling the traffic H04W36/22; wireless traffic scheduling H04W72/12
• CPC Class Codes: H04W 28/10 Flow control between communication endpoints
• CPC Class Codes: H04W 4/18 Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals
• CPC Class Codes: H04W 76/25 Maintenance of established connections
• CPC Class Codes: H04W 84/042 Public Land Mobile systems, e.g. cellular systems
• CPC Class Codes: H04W 84/12 WLAN [Wireless Local Area Networks]
• CPC Class Codes: H04W 88/182 Network node acting on behalf of an other network entity, e.g. proxy
• CPC Class Codes: Y02D 30/70 in wireless communication networks

Abstract

A mobile device having improved resource management predicts that a user is likely to access an application based on prior application access history while the user of the mobile device is inactive and a screen status of the mobile device is off. The mobile device communicates over an established multiplexed connection and a second connection is established while the established multiplexed connection remains connected. Data for the application is fetched based on the prediction. Data for the application is fetched over the second connection before the application is accessed.

Claims

1. A mobile device having improved resource management, the mobile device comprising:

a memory; and

a processor configured for;

receiving a notification from a remote server directed towards an application indicating new data for receipt by the mobile device, wherein the remote server is an intermediary server that provides connectivity between the mobile device and a first application server and a second application server, wherein the notification is received over an established multiplexed connection;

predicting that a user is likely to access the application based on prior application access history;

wherein the application is in a background of the mobile device,

wherein the user of the mobile device is inactive and a screen status of the mobile device is off;

wherein a second connection is established while the established multiplexed connection remains connected,

wherein the second connection is other than the established multiplexed connection,

wherein data for the application is fetched based on the prediction,

wherein data for the application is fetched over the second connection before the application is accessed,

wherein the fetched data is for background requests made by the application on the mobile device,

wherein the fetched data is delivered to the application; and

disconnecting the second connection.

2. The mobile device of claim 1, wherein prior access history includes time of last access of the application.

3. The mobile device of claim 1, wherein prior access history includes frequency of access of the application.

4. The mobile device of claim 1, wherein the processor is further configured for:

sending a keep-alive message; and

adjusting a rate of sending keep-alive messages to conserve battery and network resources.

5. The mobile device of claim 1, wherein the processor is further configured for executing background data requests.

6. The mobile device of claim 1, wherein the processor is further configured for reducing a rate of background data requests allowed to access a network.

7. A mobile device having improved resource management, the mobile device comprising:

a memory; and

a processor configured for;

executing background data requests;

reducing a rate of background data requests allowed to access a network;

receiving a notification from a remote server directed towards an application indicating new data for receipt by the mobile device, wherein the remote server is an intermediary server that provides connectivity between the mobile device and a first application server and a second application server, wherein the notification is received over an established multiplexed connection;

predicting that a user is likely to access the application based on prior application access history;

wherein the application is in a background of the mobile device,

wherein the user of the mobile device is inactive and a screen status of the mobile device is off;

wherein a second connection is established while the established multiplexed connection remains connected,

wherein the second connection is other than the established multiplexed connection,

wherein data for the application is fetched based on the prediction,

wherein data for the application is fetched over the second connection before the application is accessed,

wherein the fetched data is for background requests made by the application on the mobile device,

wherein the fetched data is delivered to the application; and

disconnecting the second connection.

8. The mobile device of claim 7, wherein prior access history includes time of last access of the application.

9. The mobile device of claim 7, wherein prior access history includes frequency of access of the application.

10. The mobile device of claim 7, wherein the processor is further configured for:

sending a keep-alive message; and

adjusting a rate of sending keep-alive messages to conserve battery and network resources.