US2018324704A1PendingUtilityA1

Power saving management for mobile devices based on battery charge remaining

Assignee: SEVEN NETWORKS LLCPriority: Jan 8, 2002Filed: Jun 13, 2018Published: Nov 8, 2018
Est. expiryJan 8, 2022(expired)· nominal 20-yr term from priority
H04L 2209/80H04L 9/3226H04L 67/1095H04L 63/029H04W 88/06H04L 63/0464H04W 12/04H04L 63/08H04L 63/0272H04W 76/10H04L 63/0807H04W 4/12H04W 52/0261H04L 63/0471H04L 69/329H04L 67/04H04L 67/14H04L 63/0428H04L 51/22H04L 63/0281H04L 51/58H04W 12/03H04B 7/0617H04B 7/0417Y02D10/00Y02D30/70
68
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

A mobile device includes a memory, a battery, and a processor. The processor is configured for synchronizing data with a host. The synchronization is based on an amount of battery charge remaining for the battery.

Claims

exact text as granted — not AI-modified
1 - 4 . (canceled) 
     
     
         5 . A method comprising:
 in a normal operation mode:
 automatically synchronizing between a mobile device and a client over a network on a periodic basis, wherein synchronization includes sending background application data requests to the client; and 
 receiving data from the network responsive to the sent application data requests; 
   entering a power management mode based on an amount of battery power remaining on the mobile device,
 wherein the power management mode is entered automatically based on the amount of battery power remaining being below a predetermined amount, 
 wherein the predetermined amount is set on the mobile device at each one of a first power remaining threshold and a second power remaining threshold, 
 wherein the power management mode can be enabled at either of the first power remaining threshold or the second power remaining threshold; 
   while in the power management mode:
 adjusting, by the mobile device, the rate of synchronization requests by reducing a rate at which application data requests are sent to the client; and 
 sending transactions between the mobile device and the client over a first connection between the mobile device and the client that is established for sending the transactions; and 
   exiting the power management mode, wherein the power management mode remains exited when the remaining battery charge is above the predetermined amount.   
     
     
         6 . The method of  claim 5 , wherein the client is an application server. 
     
     
         7 . The method of  claim 5 , wherein the amount of battery power remaining and the predetermined amount are expressed as a percentage of the maximum battery power available on the mobile device, wherein the mobile device identifies or determines its remaining battery power. 
     
     
         8 . The method of  claim 5 , further comprising receiving by the mobile device and from an intermediary server, a trigger that notifies the mobile device of new data,
 wherein the trigger causes the mobile device to send an application data request,   wherein the trigger is received over a second connection that is continuously maintained between the mobile device and the intermediary server, wherein the second connection that is continuously maintained is a TCP/IP connection.   
     
     
         9 . The method of  claim 8 , further comprising maintaining the second connection between the client and the intermediary server after the first connection is terminated. 
     
     
         10 . The method of  claim 8 , wherein the trigger includes the notification of new activity, wherein payload associated with the trigger remains at the client until the transactions are sent over the application data connection. 
     
     
         11 . The method of  claim 8 , wherein the first connection is established in response to the trigger. 
     
     
         12 . The method of  claim 8 , wherein the trigger is sent when the new data meets criteria defined by a filter which identifies when a trigger is to be sent. 
     
     
         13 . The method of  claim 12 , wherein the filter is configured at the client. 
     
     
         14 . The method of  claim 8 , wherein the client generates a portion of the data that causes the trigger to be generated. 
     
     
         15 . The method of  claim 8 , wherein the synchronization request is sent from the mobile device to the client when a trigger is received. 
     
     
         16 . The method of  claim 5 , wherein synchronization includes receiving changed data items. 
     
     
         17 . The method of  claim 5 , wherein the mobile device synchronizes at a higher rate when in the normal operation mode. 
     
     
         18 . A mobile device located in a mobile network, comprising:
 a battery;   a processor configured to allow the mobile device to:
 operate within a normal operation mode and a power management mode; 
 wherein in the normal operation mode:
 automatically synchronize between the mobile device and a client over a network on a periodic basis, wherein synchronization includes sending background application data requests to the client; and 
 receiving data from the network responsive to the sent application data requests; 
 
 entering a power management mode based on an amount of battery power remaining on the mobile device, 
 wherein the power management mode is entered automatically based on the amount of battery power remaining being below a predetermined amount, 
 wherein the predetermined amount is set on the mobile device at each one of a first power remaining threshold and a second power remaining threshold, 
 wherein the power management mode can be enabled at either of the first power remaining threshold or the second power remaining threshold; 
 while in the power management mode:
 adjusting, by the mobile device, the rate of synchronization requests by reducing a rate at which application data requests are sent to the client; and 
 sending transactions between the mobile device and the client over a first connection between the mobile device and the client that is established for sending the transactions; and 
 
   exiting the power management mode, wherein the power management mode remains exited when the remaining battery charge is above the predetermined amount.   
     
     
         19 . The mobile device of  claim 18 , wherein the client is an application server. 
     
     
         20 . The mobile device of  claim 18 , wherein the amount of battery power remaining and the predetermined amount are expressed as a percentage of the maximum battery power available on the mobile device, wherein the mobile device identifies or determines its remaining battery power. 
     
     
         21 . The mobile device of  claim 18 , wherein the processor is further configured to allow the mobile device for receiving from an intermediary server, a trigger that notifies the mobile device of new data,
 wherein the trigger causes the mobile device to send an application data request,   wherein the trigger is received over a second connection that is continuously maintained between the mobile device and the intermediary server, wherein the second connection that is continuously maintained is a TCP/IP connection.   
     
     
         22 . The mobile device of  claim 21 , wherein the processor is further configured to allow the mobile device for maintaining the second connection between the client and the intermediary server after the first connection is terminated. 
     
     
         23 . The mobile device of  claim 21 , wherein the trigger includes the notification of new activity, wherein payload associated with the trigger remains at the client until the transactions are sent over the application data connection. 
     
     
         24 . The mobile device of  claim 21 , wherein the first connection is established in response to the trigger. 
     
     
         25 . The mobile device of  claim 21 , wherein the trigger is sent when the new data meets criteria defined by a filter which identifies when a trigger is to be sent. 
     
     
         26 . The mobile device of  claim 25 , wherein the filter is configured at the client. 
     
     
         27 . The mobile device of  claim 21 , wherein the client generates a portion of the data that causes the trigger to be generated. 
     
     
         28 . The mobile device of  claim 21 , wherein the synchronization request is sent from the mobile device to the client when a trigger is received. 
     
     
         29 . The mobile device of  claim 18 , wherein synchronization includes receiving changed data items. 
     
     
         30 . The mobile device of  claim 18 , wherein the processor is further configured to allow the mobile device for synchronizing at a higher rate when in the normal operation mode.

Join the waitlist — get patent alerts

Track US2018324704A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.