Abstract: A system configured to perform operations to receive, via a network communication interface, an indication of a power event occurring at a first device. The first device is for an online identity. The power event causes the first device to switch from an external power source to an internal battery. The first device represents that the online identity is online while the first device receives power from the internal battery. The system is further configured to perform operations to hold, at a second device, at least one status update for an online contact of the online identity while the first device receives power from the internal battery. Furthermore, the system is configured to perform operations to release, for transmission to the first device, the at least one status update in response to determining that the first device switches back to the external power source.

Abstract: A system configured to perform operations to receive, via a network communication interface, an indication of a power event occurring at a first device. The first device is for an online identity. The power event causes the first device to switch from an external power source to an internal battery. The first device represents that the online identity is online while the first device receives power from the internal battery. The system is further configured to perform operations to hold, at a second device, at least one status update for an online contact of the online identity while the first device receives power from the internal battery. Furthermore, the system is configured to perform operations to release, for transmission to the first device, the at least one status update in response to determining that the first device switches back to the external power source.

Abstract: A system configured to perform operations to receive, via a network communication interface, an indication of a power event occurring at a first device. The first device is for an online identity. The power event causes the first device to switch from an external power source to an internal battery. The first device represents that the online identity is online while the first device receives power from the internal battery. The system is further configured to perform operations to hold, at a second device, at least one status update for an online contact of the online identity while the first device receives power from the internal battery. Furthermore, the system is configured to perform operations to release, for transmission to the first device, the at least one status update in response to determining that the first device switches back to the external power source.

Abstract: A system configured to perform operations that receive an indication of a power event occurring at a first device for an online identity. The power event causes the first device to switch from an external power source to an internal battery. The first device represents that the online identity is online while the first device receives power from the internal battery. The operations can further evaluate a priority value of an online contact for the online identity against a threshold value and hold, at a second device, at least one status update for the online contact while the first device receives power from the internal battery in response to evaluation of the priority value against the threshold value. The operations can further release, for transmission to the first device, the at least one status update in response to determination that the first device switches back to the external power source.

Abstract: A system configured to perform operations to receive, via a network communication interface, an indication of a power event occurring at a first device. The first device is for an online identity. The power event causes the first device to switch from an external power source to an internal battery. The first device represents that the online identity is online while the first device receives power from the internal battery. The system is further configured to perform operations to hold, at a second device, at least one status update for an online contact of the online identity while the first device receives power from the internal battery. Furthermore, the system is configured to perform operations to release, for transmission to the first device, the at least one status update in response to determining that the first device switches back to the external power source.

Abstract: A system configured to perform operations to receive, via a network communication interface, an indication of a power event occurring at a first device. The first device is for an online identity. The power event causes the first device to switch from an external power source to an internal battery. The first device represents that the online identity is online while the first device receives power from the internal battery. The system is further configured to perform operations to hold, at a second device, at least one status update for an online contact of the online identity while the first device receives power from the internal battery. Furthermore, the system is configured to perform operations to release, for transmission to the first device, the at least one status update in response to determining that the first device switches back to the external power source.

Abstract: A system configured to perform operations to receive, via a network communication interface, an indication of a power event occurring at a first device. The first device is for an online identity. The power event causes the first device to switch from an external power source to an internal battery. The first device represents that the online identity is online while the first device receives power from the internal battery. The system is further configured to perform operations to hold, at a second device, at least one status update for an online contact of the online identity while the first device receives power from the internal battery. Furthermore, the system is configured to perform operations to release, for transmission to the first device, the at least one status update in response to determining that the first device switches back to the external power source.

Abstract: A system configured to perform operations that receive an indication of a power event occurring at a first device for an online identity. The power event causes the first device to switch from an external power source to an internal battery. The first device represents that the online identity is online while the first device receives power from the internal battery. The operations can further evaluate a priority value of an online contact for the online identity against a threshold value and hold, at a second device, at least one status update for the online contact while the first device receives power from the internal battery in response to evaluation of the priority value against the threshold value. The operations can further release, for transmission to the first device, the at least one status update in response to determination that the first device switches back to the external power source.

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.

Abstract: Communicating information about a contact, such as presence status, may be regulated in accordance with priority values associated with contacts. Various parameters about contacts with respect to a particular environment may be collected and utilized to assign priority values to the contacts. Flow of information about the contacts is regulated based on the assigned priority values. Information about contacts with higher priority values may be communicated more frequently to client devices from one or more servers than those contacts with lower priority values. In addition, information about contacts associated with priority values that satisfy one or more criteria may be prefetched from a server to a client device.

Abstract: A presence management system may communicate contact information with mapped values. Contact information may be stored in a hierarchical, extensible structure (“hierarchical extensible contact structure”). Devices in a presence management system utilize a mapping scheme to map contact values (e.g., e-mail address, phone number, etc.) to the appropriate field of the hierarchical extensible contact structure. When devices in the presence management system communicate information for thousands of contacts, employing mapped values to navigate the hierarchical extensible contact structure reduces the size of the messages, thus reducing resource consumption (e.g., bandwidth), particularly on the scale of an enterprise.

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.

Abstract: A presence management system may communicate contact information with mapped values. Contact information may be stored in a hierarchical, extensible structure (“hierarchical extensible contact structure”). Devices in a presence management system utilize a mapping scheme to map contact values (e.g., e-mail address, phone number, etc.) to the appropriate field of the hierarchical extensible contact structure. When devices in the presence management system communicate information for thousands of contacts, employing mapped values to navigate the hierarchical extensible contact structure reduces the size of the messages, thus reducing resource consumption (e.g., bandwidth), particularly on the scale of an enterprise.

Abstract: Communicating information about a contact, such as presence status, may be regulated in accordance with priority values associated with contacts. Various parameters about contacts with respect to a particular environment may be collected and utilized to assign priority values to the contacts. Flow of information about the contacts is regulated based on the assigned priority values. Information about contacts with higher priority values may be communicated more frequently to client devices from one or more servers than those contacts with lower priority values. In addition, information about contacts associated with priority values that satisfy one or more criteria may be prefetched from a server to a client device.