# US 9,438,550 B2 · Mobile device power management in data synchronization over a mobile network with or without a trigger notification

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

- Number: US 9,438,550 B2
- Document ID: US9438550B2
- Status: Granted
- Kind: B2
- Application number: 14/873,143
- Filed: 2015-10-01
- Published: 2016-02-04
- Granted: 2016-09-06
- 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/US9438550B2

## 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 method for transferring data between a mobile device and a client includes sending transactions from the mobile device to the client over a first connection and determining how often to receive new data.

## Claims

### Claim 1

A method for transferring data between a mobile device and a host, comprising:
sending, in response to instructions from a processor, application data requests from a mobile device to a host over a first connection at a first frequency;
receiving data from the host responsive to the sent application data requests;
selecting a power management mode, from a plurality of power management modes, based on an amount of battery power remaining on the mobile device, wherein selecting a power management mode is further based on the amount of battery power remaining being below a predetermined amount;
changing the frequency that the application data requests are sent from the first frequency to a second frequency associated with the selected power management mode;
wherein at least two of the power management modes are a low power mode configured to conserve the amount of battery power remaining on the mobile device and a normal operation mode,
wherein the normal operation mode is configured to allow the mobile device to send application data requests more frequently than when the mobile device is in low power mode,
wherein the frequency at which some application data requests are sent is not changed to the second frequency while the mobile device is in the low power mode; and
exiting the low power mode when an amount of battery power remaining is above a predetermined amount.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
receiving a trigger that notifies the mobile device of new data; and
receiving new data from the host,
wherein receiving the new data from the host is at least in part responsive to the trigger,
wherein the new data is of a type for which a trigger is to be sent, and
wherein the trigger causes the mobile device to send at least one data request associated with the trigger.

### Claim 3 (depends on 1)

The method of claim 1, wherein the predetermined amount is 75% of battery charge.

### Claim 4 (depends on 1)

The method of claim 1, wherein the mobile device sends application data requests periodically.

### Claim 5 (depends on 1)

The method of claim 1, further comprising authenticating a user of the mobile device over the first connection, wherein authenticating a user is performed by sending an authentication token.

### Claim 6 (depends on 1)

The method of claim 1, further comprising authenticating a user of the mobile device by sending an authentication token over the first connection, wherein the authentication token is verified against a user database.

### Claim 7 (depends on 6)

The method of claim 6, wherein authenticating the user allows the mobile device to access content at the host.

### Claim 8 (depends on 1)

The method of claim 1, further comprising receiving a notification of new content.

### Claim 9 (depends on 8)

The method of claim 8, wherein the notification is received over a connection that is maintained while the mobile device is in the power management mode.

### Claim 10 (depends on 8)

The method of claim 8, wherein the notification includes a portion of a content that is to be received by the mobile device.

### Claim 11 (depends on 8)

The method of claim 8, wherein the notification includes less than a totality of the content to be received by the mobile device.

### Claim 12 (depends on 8)

The method of claim 8, further comprising establishing a subsequent connection for receipt of the content.

### Claim 13 (depends on 8)

The method of claim 8, wherein the notification includes an identification of a sender of the content.

### Claim 14 (depends on 8)

The method of claim 8, further comprising displaying the notification on the mobile device for viewing by the user.

### Claim 15

A mobile device located in a mobile network, comprising:
a battery;
a processor configured to allow the mobile device to:
send application data requests to a host over a first connection at a first frequency;
receive data from the network responsive to the sent application data requests;
select a power management mode from a plurality of power management modes based on an amount of battery power remaining on the mobile device, wherein the selection of a power management mode is further based on the amount of battery power remaining being below a predetermined amount;
change the frequency that application data requests are sent from the first frequency to a second frequency associated with the selected power management mode;
wherein at least two of the power management modes are a low power mode configured to conserve the amount of battery power remaining on the mobile device and a normal operation mode,
wherein the normal operation mode is configured to allow the mobile device to send application data requests more frequently than when the mobile device is in the low power mode,
wherein the frequency at which some application data requests are sent is not changed to the second frequency while the mobile device is in the low power mode; and
exit the low power mode when an amount of battery power remaining is above a predetermined amount.

### Claim 16 (depends on 15)

The mobile device of claim 15, wherein at least one of the power management modes uses charge gradient levels for determining how often to send application data requests.

### Claim 17 (depends on 15)

The mobile device of claim 15, wherein at least one of the power management modes is configured to allow the mobile device to send application data requests less frequently on weekends than on weekdays.

### Claim 18 (depends on 15)

The mobile device of claim 15, wherein the processor is further configured to allow the mobile device to:
receive a trigger that notifies the mobile device of new data; and
receive the new data from the host,
wherein receiving the new data from the host is at least in part responsive to the trigger, and wherein the trigger is received by the mobile device when the new data is of a type for which a trigger should be sent, wherein the trigger causes the mobile device to send at least one data request associated with the trigger.

### Claim 19 (depends on 15)

The mobile device of claim 15, wherein the predetermined amount is 75% of battery charge.

### Claim 20 (depends on 15)

The mobile device of claim 15, wherein the sent application data requests occur at a first frequency when the mobile device is in a normal operation mode, and at a second frequency when the mobile device is in the low power mode, wherein the first frequency is higher than the second frequency.

### Claim 21 (depends on 15)

The mobile device of claim 15, wherein the application data requests are sent periodically.

### Claim 22 (depends on 15)

The mobile device of claim 15, wherein the processor is further configured to allow the mobile device to authenticate a user of the mobile device over the first connection by sending an authentication token.

### Claim 23 (depends on 15)

The mobile device of claim 15, wherein the processor is further configured to allow the mobile device to authenticate a user of the mobile device by sending an authentication token over the first connection, wherein the authentication token is verified against a user database.

### Claim 24 (depends on 23)

The mobile device of claim 23, wherein authenticating the user allows the mobile device to access content at the host.

### Claim 25 (depends on 15)

The mobile device of claim 15, wherein the processor is further configured to allow the mobile device to receive a notification of new content.

### Claim 26 (depends on 25)

The mobile device of claim 25, wherein the notification is received over a connection that is maintained while the mobile device is in the power management mode.

### Claim 27 (depends on 25)

The mobile device of claim 25, wherein the notification includes a portion of a content that is to be received by the mobile device.

### Claim 28 (depends on 25)

The mobile device of claim 25, wherein the notification includes less than a totality of the content to be received by the mobile device.

### Claim 29 (depends on 25)

The mobile device of claim 25, wherein the processor is further configured to allow the mobile device to establish a subsequent connection for receipt of the content.

### Claim 30 (depends on 25)

The mobile device of claim 25, wherein the notification includes an identification of a sender of the content.

### Claim 31 (depends on 25)

The mobile device of claim 25, wherein the notification is displayed on the mobile device for viewing by the user.

### Claim 32

A mobile device located in a mobile network, comprising:
a battery;
a processor configured to allow the mobile device to:
monitor a remaining battery level of the battery;
send application data requests to a host over a first connection at a first frequency;
receive data from the host responsive to the sent application data requests;
operate in a normal operations mode when a remaining battery level is above a predetermined amount;
select a low power mode from a plurality of power management modes in order to conserve the remaining battery level when the remaining battery level is below the predetermined amount, wherein the low power mode is based on amount of battery power remaining on the mobile device being below a predetermined amount;
change the frequency that application data requests are sent from the first frequency to a second frequency associated with the low power management mode;
wherein at least two of the power management modes are the low power mode configured to conserve the amount of battery power remaining on the mobile device and the normal operations mode,
wherein the normal operation mode is configured to allow the mobile device to send application data requests more frequently than when the mobile device is in the low power mode,
wherein the frequency at which some application data requests are sent is not changed to the second frequency while the mobile device is in the low power mode;
exit the low power management mode when the remaining battery level is above the predetermined amount; and
receive a trigger that notifies the mobile device of new data, wherein the trigger at least in part causes the mobile device to send application data requests.

### Claim 33 (depends on 32)

The mobile device of claim 32, wherein the processor is configured to allow the mobile device to enter the low power mode when the amount of battery power remaining is below a predetermined amount.

### Claim 34 (depends on 32)

The mobile device of claim 32, wherein the processor is further configured to allow the mobile device to receive a notification of new content.

### Claim 35 (depends on 32)

The mobile device of claim 32, wherein the notification is received over a connection that is maintained while the mobile device is in the power management mode.

### Claim 36 (depends on 34)

The mobile device of claim 34, wherein the notification includes a portion of a content that is to be received by the mobile device.

### Claim 37 (depends on 34)

The mobile device of claim 34, wherein the notification includes less than a totality of the content to be received by the mobile device.

### Claim 38 (depends on 34)

The mobile device of claim 34, wherein the processor is further configured to allow the mobile device to establish a subsequent connection for receipt of the content.

### Claim 39 (depends on 34)

The mobile device of claim 34, wherein the notification includes an identification of a sender of the content.

### Claim 40 (depends on 34)

The mobile device of claim 34, wherein the notification is displayed on the mobile device for viewing by the user.