Mobile application traffic optimization

Patent metadata

Field	Value
Publication number	US-9503544-B2
Application number	US-201615132400-A
Country	US
Kind code	B2
Filing date	Apr 19, 2016
Priority date	Jul 26, 2010
Publication date	Nov 22, 2016
Grant date	Nov 22, 2016

Abstract

A system with distributed proxy for reducing traffic to satisfy data requests made in a wireless network is provided. The system includes a mobile device having a local proxy for intercepting a data request made via the mobile device and a proxy server coupled to the mobile device and a content server to which the data request is directed. The proxy server is able to communicate with the local proxy and the local proxy forwards the data request to the proxy server for transmission to the content server for a response to the data request. The proxy server sends the data request to the content server independent of activities on the local proxy and notifies the local proxy when different content on the content server is detected for the data request

First claim

What is claimed is:

1. A mobile device comprising:
a memory;
a radio; and
a processor,
the mobile device is configured for:
determining a predicted launch time of a first application executing in a background of the mobile device, wherein the predicted launch time is based on historical activity related to the first application, wherein the historical activity is related to a time of day when a user has accessed the first application; and
establishing a connection with a server based on the predicted launch time, wherein the connection is established while the first application is executing in the background of the mobile device;
wherein data is fetched for the first application over the connection while the application remains executing in the background before the predicted launch time, wherein the data is provided by a server in communication with the mobile device.

2. The mobile device of claim 1 , wherein the mobile device is further configured for transmitting requests from the first application, after the data is fetched, based on the historical activity related to the first application.

3. The mobile device of claim 1 , wherein the mobile device is further configured for transmitting requests from the first application at a time that is based on a frequency at which a user has accessed the first application.

4. The mobile device of claim 1 , wherein the mobile device is further configured for transmitting requests from the first application based on a time period that the first application is operating in the background.

5. The mobile device of claim 1 , wherein the mobile device is further configured for transmitting requests from the first application at a time based on inactivity of the mobile device, wherein the requests are transmitted less frequently during periods of inactivity of the mobile device.

6. The mobile device of claim 1 , wherein the functionality to fetch data is configured to be enabled and disabled by a user of the mobile device at a user interface of the mobile device.

7. The mobile device of claim 1 , wherein the mobile device is further configured for stopping fetching data for the first application based on a period of time that the first application is in the background.

8. The mobile device of claim 1 , wherein the mobile device is further configured for batching data from requests from the first application and a request from a second application that is also executing in the background for transmission over a wireless network.

9. The mobile device of claim 8 , wherein the requests from the first and second application are batched while a backlight of the mobile device is off.

10. The mobile device of claim 8 , wherein the mobile device is further configured for initiating batching in response to the first application being moved into the background.

11. The mobile device of claim 8 , wherein a timing at which the requests are batched is based on a frequency that a user interacts with the first application.

12. The mobile device of claim 1 , wherein the mobile device is further configured for:
determining timing properties of an application request from the first application; and
adjusting the timing properties of the application requests.

13. The mobile device of claim 12 , wherein adjusting the timing properties of the requests is performed in response to a triggering event, and, wherein the triggering event includes a backlight or screen of the mobile device transitioning between off and on.

14. The mobile device of claim 12 , wherein adjusting the timing properties occurs while a backlight of the mobile device is off.

15. The mobile device of claim 14 , wherein adjusting the timing properties is based on receipt of a message.

16. The mobile device of claim 15 , wherein receipt of the message alters a length of time between the requests to fetch data.

17. The mobile device of claim 15 , wherein a second connection is maintained for receipt of the message, wherein the second connection is different from the connection established based on the predicted launch time.

18. The mobile device of claim 12 , wherein adjusting the timing properties is performed in response to determining that a number of occurrences of events exceeds a threshold, and adjusting the timing properties includes:
determining whether a requested resource has changed within one or more polling intervals;
decreasing a subsequent polling interval in response to determining that the number of occurrences that the resource has changed within the one or more polling intervals exceeds a first threshold; or
increasing the subsequent polling interval in response to determining that the number of occurrences that the resource has not changed within the one or polling intervals exceeds a second threshold.

19. The mobile device of claim 1 , wherein the mobile device is configured for:
determining a first set of timing properties of an application request; and
adjusting a second set of timing properties that are different from the first set of timing properties.

20. The mobile device of claim 19 , wherein adjusting the second set of timing properties occurs while a backlight of the mobile device is off.

21. A method comprising:
determining a predicted launch time of a first application executing in a background of a mobile device, wherein the predicted launch time is based on historical activity related to the first application, wherein the historical activity is related to a time of day when a user has accessed the first application; and
establishing a connection with a server based on the predicted launch time, wherein the connection is established while the first application is executing in the background of the mobile device;
wherein data is fetched for the first application over the connection while the application remains executing in the background before the predicted launch time, wherein the data is provided by a server in communication with the mobile device.

22. The method of claim 21 , further comprising transmitting requests from the first application, based on the historical activity related to the first application.

23. The method of claim 21 , further comprising transmitting requests from the first application at a time that is based on a frequency at which a user has accessed the first application.

24. The method of claim 21 , wherein the functionality to fetch data is enabled and disabled at a user interface of the mobile device.

25. The method of claim 21 , further comprising batching data from requests from the first application and a request from a second application that is also executing in the background for transmission over a wireless network.

26. The method of claim 25 , wherein the requests from the first application and the second application are batched while a backlight of the mobile device is off.

Assignees

• Seven Networks Llc

Inventors

• Luna Michael
• Backholm Ari
• Petersen Steve

Classifications

• H04L67/2885

  Hierarchically arranged intermediate devices, e.g. for hierarchical caching · CPC title

• H04W28/02

  Traffic management, e.g. flow control or congestion control · CPC title

• H04W76/25

  Maintenance of established connections · CPC title

• H04L67/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 title

• H04W4/18 Primary

  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 title