Power saving management for mobile devices based on battery charge remaining

• US 10,720,974 B2
• Filed: 01/10/2019
• Issued: 07/21/2020
• Est. Priority Date: 01/08/2002
• Status: Expired due to Term

• Current Assignee: Seven Networks LLC (SoftBank Group Corp.)
• Original Assignee: Seven Networks LLC (SoftBank Group Corp.)
• Inventors: Fiatal, Trevor A., Boynton, Lee R., Burke, Scott M, Gustafson, Brian D., Raj, Binu, Alvarado, William, Benitez, Juan, Duncan, Fred J.
• Primary Examiner(s): Casca, Fred A
• Application Number:
  US16/244,149
• Publication Number:
  US 20190149503A1
• Time in Patent Office: 558 Days
• Field of Search: 455574, 455572, 455573, 455522, 455 411, 4553431, 4551271, 4555521, 4553435, 455 111, 455 134
• CPC Class Codes: H04B 7/04 using two or more spaced independent antennas
• CPC Class Codes: H04B 7/0417 Feedback systems
• CPC Class Codes: H04B 7/0617 for beam forming
• CPC Class Codes: H04L 2209/80 Wireless network architectures or network communication protocols for wireless network security H04W12/00
• CPC Class Codes: H04L 51/58 Message adaptation for wireless communication
• CPC Class Codes: H04L 63/0272 Virtual private networks
• CPC Class Codes: H04L 63/0281 Proxies
• CPC Class Codes: H04L 63/029 Firewall traversal, e.g. tunnelling or, creating pinholes
• 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/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/0807 using tickets, e.g. Kerberos cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/3226 using a predetermined code, e.g. password, passphrase or PIN network architectures or network communication protocols for supporting authentication of entities using passwords in a packet data network H04L63/083
• CPC Class Codes: H04W 12/03 Protecting confidentiality, e.g. by encryption
• CPC Class Codes: H04W 12/04 Key management, e.g. using generic bootstrapping architecture [GBA]
• CPC Class Codes: H04W 4/12 : Messaging; Mailboxes; Announcements
• CPC Class Codes: H04W 52/0261 : managing power supply demand, e.g. depending on battery level
• CPC Class Codes: H04W 76/10 : Connection setup
• CPC Class Codes: H04W 88/06 : adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
• CPC Class Codes: Y02D 10/00 : Energy efficient computing, e.g. low power processors, power management or thermal management
• CPC Class Codes: Y02D 30/70 : in wireless communication networks

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

1. A mobile device comprising:

a memory;

a battery; and

a processor, the processor configured for;

sending configuration information that includes login data to authenticate a user of the mobile device;

verifying the login data against a user database;

sending a trigger to the mobile device when new data is available for synchronization;

synchronizing data with a host,

wherein the synchronization is based on an amount of battery charge remaining for the battery,

wherein the mobile device varies how often the mobile device synchronizes with the host based on different gradient levels associated with different amounts of battery charge remaining for the battery.

2. The mobile device of claim 1, wherein the synchronization is further based on a day of the week.

3. The mobile device of claim 1, further configured for determining an amount of battery charge remaining on the mobile device.

5. The mobile device of claim 1, wherein varying how often the mobile device synchronizes with the host based on different gradient levels associated with different amounts of battery charge remaining for the battery includes the mobile device synchronizing with the host according to a first time interval when the battery has more than a first threshold amount of charge remaining, and the mobile device synchronizing with the host according to a second time interval when the battery has more than a second threshold amount of charge remaining and less than the first threshold amount of charge remaining.

6. The mobile device of claim 5, wherein the first threshold is greater than the second threshold, and wherein the first time interval is less than the second time interval.

7. The mobile device of claim 5, wherein the mobile device synchronizes with the host according to a third time interval when the battery has more than a third threshold amount of charge remaining and less than the second threshold amount of charge remaining.

8. The mobile device of claim 7, wherein the second threshold is greater than the third threshold, and wherein the second time interval is less than the third time interval.

4. A system comprising:

a server; and

a mobile device comprising;

a memory;

a battery; and

a processor, the processor configured for;

sending configuration information that includes login data to authenticate a user of the mobile device;

verifying the login data against a user database;

sending a trigger to the mobile device when new data is available for synchronization;

synchronizing data with a host,

wherein the synchronization is based on an amount of battery charge remaining for the battery,

wherein the mobile device varies how often the mobile device synchronizes with the host based on different gradient levels associated with different amounts of battery charge remaining for the battery,

wherein the mobile device synchronizes more frequently when the battery has a relatively large amount of charge remaining and the mobile device synchronizes less frequently when the battery has a relatively small amount of charge remaining.