BATTERY EFFICIENT SYNCHRONIZATION OF COMMUNICATIONS USING A TOKEN BUCKET

• US 20170012918A1
• Filed: 09/22/2016
• Published: 01/12/2017
• Est. Priority Date: 04/14/2014
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Green, Hagen, Morris, Jon, Desai, Anish, McClure, Marc
• Granted Patent: US 10,356,030 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 1/3234 Power saving characterised by the action undertaken
• CPC Class Codes: G06F 1/329 by task scheduling
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]
• CPC Class Codes: H04L 47/215 using token-bucket
• CPC Class Codes: H04L 51/226 Delivery according to priorities
• CPC Class Codes: H04L 51/42 Mailbox-related aspects, e.g. synchronisation of mailboxes
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 67/62 Establishing a time schedule for servicing the requests
• CPC Class Codes: Y02D 10/00 Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

Systems and methods for email synchronization may include a computing device with a token bucket. The token bucket allows for temporary storage of tokens, each token authorizing a synchronization of at least one email application running on the computing device. The device may determine a frequency of received email communications associated with an email account managed by the at least one email application and hosted by an email server. The determining may be based on one or more characteristics associated with the token bucket. The determined frequency may be compared with a threshold value. When the determined frequency is equal to or lower than the threshold value, a push communication channel may be established with the email server, the push communication channel for receiving server-initiated email push communications. The at least one email application may be synchronized with the email account by receiving push communications using the push communication channel.

Claims

1-22. -22. (canceled)

23. A mobile computing device, comprising:

a processor;

a memory; and

a synchronization service with a token bucket, the token bucket allowing for temporary storage of tokens, each token authorizing a synchronization of at least one email application running on the computing device, the synchronization service configured to perform operations for email synchronization, the operations comprising;

resetting the token bucket with an initial set of tokens, wherein each token authorizes a synchronization of the at least one email application running on the computing device with a corresponding email account hosted by an email server;

establishing a push communication channel with the email server, the push communication channel for receiving server-initiated email push communications;

determining whether at least one of the tokens is available in the token bucket; and

when at least one of the tokens is not available in the token bucket, closing the push communication channel.

24. The mobile computing device according to claim 23, the operations further comprising:

if at least one of the tokens is available in the token bucket, synchronizing the at least one email application with the corresponding email account by receiving push email communications using the push communication channel.

25. The mobile computing device according to claim 23, the operations further comprising:

if the push communication channel is closed;

detecting if at least another one of the tokens is available in the token bucket; and

if at least another one of the tokens is available in the token bucket, re-establishing the push communication channel with the email server.

26. The mobile computing device according to claim 24, the operations further comprising:

deducting, for each synchronizing of the push email communications, one token from the tokens stored in the token bucket; and

when the token bucket is empty;

closing the push communication channel; and

synchronizing the at least one email application with the corresponding email account using an email pull request initiated by the computing device.

27. The mobile computing device according to claim 23, wherein resetting the token bucket with an initial set of tokens is performed by selecting one or more of:

an initial token count value, a token bucket size value, a token bucket refill interval value, or a refill token count value associated with the token bucket.

28. The mobile computing device according to claim 27, the operations further comprising:

depositing a number of tokens in the token bucket periodically, at a time interval with duration equal to the token bucket refill interval value, the deposited number of tokens equal to the refill token count value.

29. The mobile computing device according to claim 27, the operations further comprising:

receiving an input selecting one or more of;

the initial token count value, the token bucket size value, the token bucket refill interval value, or the refill token count value, wherein the input is one of an automatic input or a user input.

30. The mobile computing device according to claim 27, wherein the resetting the token bucket is based on at least one of hardware characteristics of the computing device or use statistics associated with the computing device.

31. The mobile computing device according to claim 30, wherein the use statistics comprise at least one of frequency of user interaction with the computing device, a number of received emails during a time period, a number of times a screen of the computing device is turned on, or geo-location of the computing device.

32. A method for email synchronization using a token bucket, the token bucket allowing for temporary storage of tokens, each token authorizing a synchronization of at least one email application running on a computing device, the method comprising:

resetting the token bucket with an initial set of tokens, wherein each token authorizes a synchronization of the at least one email application running on the computing device with a corresponding email account hosted by an email server;

establishing a push communication channel with the email server, the push communication channel for receiving server-initiated email push communications;

determining whether at least one of the tokens is available in the token bucket; and

when at least one of the tokens is not available in the token bucket, closing the push communication channel.

33. The method according to claim 32, comprising:

if at least one of the tokens is available in the token bucket, synchronizing the at least one email application with the corresponding email account by receiving push email communications using the push communication channel.

34. The method according to claim 32, comprising:

if the push communication channel is closed;

detecting if at least another one of the tokens is available in the token bucket; and

if at least another one of the tokens is available in the token bucket, re-establishing the push communication channel with the email server.

35. The method according to claim 33, comprising:

deducting, for each synchronizing of the push email communications, one token from the tokens stored in the token bucket; and

when the token bucket is empty;

closing the push communication channel; and

synchronizing the at least one email application with the corresponding email account using an email pull request initiated by the computing device.

36. The method according to claim 32, wherein resetting the token bucket with an initial set of tokens is performed by selecting one or more of:

an initial token count value, a token bucket size value, a token bucket refill interval value, or a refill token count value associated with the token bucket.

37. The method according to claim 36, comprising:

depositing a number of tokens in the token bucket periodically, at a time interval with duration equal to the token bucket refill interval value, the deposited number of tokens equal to the refill token count value.

38. The method according to claim 36, comprising:

receiving an input selecting one or more of;

the initial token count value, the token bucket size value, the token bucket refill interval value, or the refill token count value, wherein the input is one of an automatic input or a user input.

39. The method according to claim 36, wherein the resetting the token bucket is based on at least one of hardware characteristics of the computing device or use statistics associated with the computing device.

40. The method according to claim 39, wherein the use statistics comprise at least one of frequency of user interaction with the computing device, a number of received emails during a time period, a number of times a screen of the computing device is turned on, or geo-location of the computing device.

41. A computer-readable storage device having stored thereon computer-executable instructions operable to cause a computing device to perform operations for email synchronization using a token bucket, the token bucket allowing for temporary storage of tokens, each token authorizing a synchronization of at least one email application running on the computing device, the operations comprising:

resetting the token bucket with an initial set of tokens, wherein each token authorizes a synchronization of the at least one email application running on the computing device with a corresponding email account hosted by an email server;

establishing a push communication channel with the email server, the push communication channel for receiving server-initiated email push communications;

determining whether at least one of the tokens is available in the token bucket; and

when at least one of the tokens is not available in the token bucket, closing the push communication channel.

42. The computer-readable storage device according to claim 41, the operations further comprising:

if at least one of the tokens is available in the token bucket, synchronizing the at least one email application with the corresponding email account by receiving push email communications using the push communication channel.