Managing contact status updates in a presence management system

• US 9,451,038 B2
• Filed: 10/02/2007
• Issued: 09/20/2016
• Est. Priority Date: 10/02/2007
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Beadle, Gary M., Masterson, Michael L.
• Primary Examiner(s): Tiv, Backhean
• Application Number:
  US11/866,090
• Publication Number:
  US 20090088144A1
• Time in Patent Office: 3,276 Days
• Field of Search: 709/206, 709/207
• US Class Current: 1/1
• CPC Class Codes: G06F 1/329 by task scheduling
• CPC Class Codes: G06F 8/4432 Reducing the energy consumption
• CPC Class Codes: G06F 9/4893 taking into account power or heat criteria power management in computers in general G06F1/3203; thermal management in computers in general G06F1/206
• CPC Class Codes: H04L 43/16 Threshold monitoring
• CPC Class Codes: H04L 67/145 avoiding end of session, e.g. keep-alive, heartbeats, resumption message or wake-up for inactive or interrupted session
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/54 Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
• CPC Class Codes: H04W 52/0296 switching to a backup power supply
• CPC Class Codes: Y02D 30/70 in wireless communication networks

Abstract

Managing online presence information for contacts involves propagating contact status updates from a contact to an interested identity. A contact list may include hundreds to thousands of contacts for an identity. When one of those contacts changes presence status (e.g., from available to do-not-disturb), the change is propagated from a device of the contact, to a server, to one or more devices of the identity maintaining the contact list. Although that single change or status update consumes a small amount of resources, status updates for a larger number of contacts occurring at various times consumes a more substantial amount of resources, including bandwidth and power. Although power consumption may not be a factor for a desktop computer, power consumption for large scale and/or frequent status updates on devices with more limited power sources (e.g., mobile phones, personal data assistants, etc.) may be a significant factor.

Claims

1. A method comprising:

receiving indication of a power event occurring at a first device for an online identity represented by a presence management application, wherein the power event causes a switch to supply power to the first device from an external power source to an internal battery within the first device;

indicating that status updates for a set of one or more online contacts maintained for the online identity are to be held at a second device in response to receiving the indication of occurrence of the power event;

maintaining status of the set of one or more online contacts of the online identity at the second device based, at least in part, on said indicating that the status updates for the set of one or more online contacts maintained for the online identity are to be held at the second device while the presence management application continues to represent that the online identity is online; and

releasing to the first device updates to the status of the set of one or more online contacts after the power event is completed such that power supplied to the first device is switched back to the external power source.

2. The method of claim 1, wherein the power event comprises one of a manual event and an automatic event.

3. The method of claim 1, wherein the released status updates represent net changes to status of the set of one or more online contacts.

4. The method of claim 1 further comprising piggybacking the status updates on other data transmitted to the first device.

5. The method of claim 1, wherein the first device transmits status messages for the presence management application less frequently than before occurrence of the power event was detected.

6. The method of claim 1 further comprising resetting status of the online identity if a keep alive message is not received within a given time period.

7. A method comprising:

updating presence status of an online contact at a first device after receiving an indication that presence status for the online contact has changed;

recording the indication;

receiving a first notification that a power event has occurred at a second device, wherein the power event causes a switch to supply power to the second device from an external power source to an internal battery within the device;

holding, at the first device, the indication in response to receiving the first notification; and

propagating the indication to the second device after receiving a second notification from the second device that the power event is completed such that power supplied to the second device is switched back to the external power source.

8. The method of claim 7, wherein the power event comprises one of a manual event and an automatic event.

9. A non-transitory machine-readable storage medium having stored therein a program product, which when executed a set of one or more processor units causes the set of one or more processors units to perform operations that comprise:

receiving an indication of a power event occurring at a first device for an identity represented by a presence management application as online, wherein the power event causes a switch to supply power to the first device from an external power source to an internal battery within the first device;

indicating that status updates for a set of one or more contacts maintained for the identity are to be held at a second device in response to receiving the indication of occurrence of the power event;

maintaining the status updates at the second device based, at least in part, on said indicating that the status updates are to be held at the second device while the presence management application continues to represent that the identity is online; and

releasing to the first device the status updates after the power event is completed such that power supplied to the device is switched back to the external power source.

10. The non-transitory machine-readable storage medium of claim 9, wherein the power event comprises one of a manual event and an automatic event.

11. The non-transitory machine-readable storage medium of claim 9, wherein the released status updates represent net changes to status of the set of one or more contacts.

12. An apparatus comprising:

a processor;

a network interface coupled with the processor and configured to transmit and receive data; and

a contact list manager configured to,

update presence status of a contact after receiving an indication that presence status for the contact has changed,

record the indication,

determine that a power event has occurred at a device communicatively coupled to the apparatus, wherein the power event is to cause a switch to supply power to the device from an external power source to an internal battery within the device, and

propagate the indication to a device of an identity interested in the contact after receiving notification from the device of the identity that the power event is completed such that power supplied to the device is switched back to the external power source.

13. The apparatus of claim 12, wherein the power event comprises one of a manual event and an automatic event.