# US 2018/0324704 A1 · Power saving management for mobile devices based on battery charge remaining

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2018/0324704 A1
- Document ID: US20180324704A1
- Status: Published application
- Kind: A1
- Application number: 16/008,014
- Filed: 2018-06-13
- Published: 2018-11-08
- Earliest claimed: 2002-01-08
- Assignees: Seven Networks, LLC
- Applicants: Seven Networks, LLC
- Inventors: Trevor A. Fiatal; Lee R. Boynton; Scott M. Burke; Brian D. Gustafson; Binu Raj; William Alvarado; Juan Benitez; Fred J. Duncan
- Web page: https://patentgrep.com/patent/US20180324704A1

## CPC

- H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload}
- 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)}
- H04L 63/0272: {Virtual private networks}
- H04L 63/029: {Firewall traversal, e.g. tunnelling or, creating pinholes}
- H04L 63/0464: {using hop-by-hop encryption, i.e. wherein an intermediate entity decrypts the information and re-encrypts it before forwarding it}
- 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}
- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- H04L 63/0807: {using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213)}
- H04W 12/03: Protecting confidentiality, e.g. by encryption
- H04B 7/0417: Feedback systems
- H04B 7/0617: {for beam forming}
- H04L 51/58: Message adaptation for wireless communication
- H04L 63/0281: {Proxies}
- H04L 67/04: specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
- H04L 67/1095: Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
- H04L 67/14: Session management (for real-time applications in data packet communications networks H04L65/1066)
- H04L 69/329: in the application layer [OSI layer 7]
- H04L 2209/80: Wireless
- H04W 4/12: Messaging; Mailboxes; Announcements
- H04W 12/04: Key management, e.g. using generic bootstrapping architecture [GBA]
- H04W 52/0261: {managing power supply demand, e.g. depending on battery level}
- H04W 76/10: Connection setup
- H04W 88/06: adapted for operation in multiple networks {or having at least two operational modes}, e.g. multi-mode terminals
- Y02D 10/00: Energy efficient computing, e.g. low power processors, power management or thermal management
- Y02D 30/70: in wireless communication networks
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- H04B: TRANSMISSION
- Y02D: CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE

## 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

### Claim at position 1

1-4. (canceled)

### Claim 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.

### Claim 6 (depends on 5)

The method of claim 5, wherein the client is an application server.

### Claim 7 (depends on 5)

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.

### Claim 8 (depends on 5)

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.

### Claim 9 (depends on 8)

The method of claim 8, further comprising maintaining the second connection between the client and the intermediary server after the first connection is terminated.

### Claim 10 (depends on 8)

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.

### Claim 11 (depends on 8)

The method of claim 8, wherein the first connection is established in response to the trigger.

### Claim 12 (depends on 8)

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.

### Claim 13 (depends on 12)

The method of claim 12, wherein the filter is configured at the client.

### Claim 14 (depends on 8)

The method of claim 8, wherein the client generates a portion of the data that causes the trigger to be generated.

### Claim 15 (depends on 8)

The method of claim 8, wherein the synchronization request is sent from the mobile device to the client when a trigger is received.

### Claim 16 (depends on 5)

The method of claim 5, wherein synchronization includes receiving changed data items.

### Claim 17 (depends on 5)

The method of claim 5, wherein the mobile device synchronizes at a higher rate when in the normal operation mode.

### Claim 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.

### Claim 19 (depends on 18)

The mobile device of claim 18, wherein the client is an application server.

### Claim 20 (depends on 18)

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.

### Claim 21 (depends on 18)

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.

### Claim 22 (depends on 21)

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.

### Claim 23 (depends on 21)

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.

### Claim 24 (depends on 21)

The mobile device of claim 21, wherein the first connection is established in response to the trigger.

### Claim 25 (depends on 21)

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.

### Claim 26 (depends on 25)

The mobile device of claim 25, wherein the filter is configured at the client.

### Claim 27 (depends on 21)

The mobile device of claim 21, wherein the client generates a portion of the data that causes the trigger to be generated.

### Claim 28 (depends on 21)

The mobile device of claim 21, wherein the synchronization request is sent from the mobile device to the client when a trigger is received.

### Claim 29 (depends on 18)

The mobile device of claim 18, wherein synchronization includes receiving changed data items.

### Claim 30 (depends on 18)

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.