Abstract: Merger and duplicate resolution for contact information across platforms is managed employing contact objects and aggregating the contact objects into contact models. Contact data from internal and/or external data stores may be retrieved and contact objects created for each contact from each contact store. A contact model for each contact entity may be created by aggregating contact data from contact objects across the contact stores. The aggregation may include duplicate resolution through weighting of communication system types, ranking of contact information type, and similar approaches. The contact models may be dynamically updated based on changes to the contact objects.

Abstract: A presence aggregation system provides a presence server that allows users to publish information regarding their availability with the presence server. The presence server maintains a record of each user's published information. When an endpoint publishes information regarding a user's availability at that endpoint with the presence server, the presence server provides all of the user's published information, including the information just published, to each of the user's endpoints, including the endpoint which published the information. This allows each of the user's endpoints to generate an aggregated availability of the user. The presence server may also provide all of the user's published information, including the information just published, to each of the subscribing users' endpoints. This allows the subscribing users to also generate a view of the user's aggregated availability.

Abstract: A presence aggregation system provides a presence server that allows users to publish information regarding their availability with the presence server. The presence server maintains a record of each user's published information. When an endpoint publishes information regarding a user's availability at that endpoint with the presence server, the presence server provides all of the user's published information, including the information just published, to each of the user's endpoints, including the endpoint which published the information. This allows each of the user's endpoints to generate an aggregated availability of the user. The presence server may also provide all of the user's published information, including the information just published, to each of the subscribing users' endpoints. This allows the subscribing users to also generate a view of the user's aggregated availability.

Abstract: A system and method for managing presence information based on a specified presence level between a user and other parties. An interface is provided that allows a user to specify a presence level between the user and one or more other parties. Once a user specifies a presence level, the specified level dictates how an incoming communication request is to be managed in the event that the user is not available to receive the communication. The specified presence level may determine the amount of information disclosed to the other party, the presence that is projected to the other party, and the decision on whether to interrupt the user. In some embodiments, the presence level between the user and other parties is automatically inferred by a relationship engine.

Abstract: A system and method for managing presence information based on a specified presence level between a user and other parties. An interface is provided that allows a user to specify a presence level between the user and one or more other parties. Once a user specifies a presence level, the specified level dictates how an incoming communication request is to be managed in the event that the user is not available to receive the communication. The specified presence level may determine the amount of information disclosed to the other party, the presence that is projected to the other party, and the decision on whether to interrupt the user. In some embodiments, the presence level between the user and other parties is automatically inferred by a relationship engine.

Abstract: A method and system for aggregating capabilities from multiple endpoints associated with a user are provided. The system aggregates the capabilities of the endpoints associated with a user into an aggregate view of available modes of communication for reaching the user. Then, the system publishes the aggregate view so that other users who want to send communications to the user will know the modes of communication available for that user. In addition, the system may designate certain modes of communication as preferred or as capable of reaching the user.

Abstract: A presence aggregation system provides a presence aggregation server that allows for the publication of presence state of a publisher from the publisher's multiple endpoints. A presence state includes an availability value and an activity. An activity may include an activity token and/or a custom string. When any one of the publisher's endpoints makes a presence state publication on the presence aggregation server, the presence aggregation server generates an aggregated state of the publisher (i.e., the availability of the publisher aggregated across all of the publisher's endpoints) and publishes the generated aggregated state to each of the publisher's endpoints. The presence aggregation server may also provide the publisher's aggregated state to the subscribers of the publisher's aggregated state information.

Abstract: A presence aggregation system provides a presence aggregation server that allows for the defining and inclusion of custom presence states that are distinct from a set of default presence states that are provided by the presence aggregation system. When one or more custom presence states are defined and included in the presence aggregation system, a publisher at an endpoint is able to publish any of the defined custom presence states or default presence states as an indication of the publisher's presence. When a publication is made, the presence aggregation server may generate an aggregated availability of the publisher across all of the publisher's endpoints, and publish the aggregated availability to each of the publisher's endpoints. The presence aggregation server may also provide the publisher's aggregated availability to the subscribers of the publisher's availability information.

Abstract: A method and system for increasing the computational and network efficiency of presence servers having collections of publications is provided. The presence system uses several techniques that enable a presence server to provide rich presence information without requiring expensive processing. First, the presence system accepts batches of publication updates in a single presence update request. Similarly, the presence system accepts batches of subscription requests. Next, the presence system supports new expiration types for publication update requests that eliminate the need for a publishing user to continually refresh presence information that has not changed. Finally, the presence system accepts access lists that contain membership groups rather than an individual list of users that are to have access to a particular presence collection.

Abstract: A method and system for presenting a user interface displaying a view of a user's presence aggregated across multiple endpoints is provided. The view provides a visual display of the user's aggregated availability by displaying an indication of the user and an icon that pictorially indicates the aggregated availability of the user. The aggregated availability is the availability of the user aggregated across the user's multiple endpoints. The view may also include a text string describing the user's current aggregated availability or activity. The user interface may also display a view of the user's contacts, which includes an icon that indicates each contact's current aggregated availability.

Abstract: A presence aggregation system provides a presence server that allows users to publish information regarding their availability with the presence server. The presence server maintains a record of each user's published information. When an endpoint publishes information regarding a user's availability at that endpoint with the presence server, the presence server provides all of the user's published information, including the information just published, to each of the user's endpoints, including the endpoint which published the information. This allows each of the user's endpoints to generate an aggregated availability of the user. The presence server may also provide all of the user's published information, including the information just published, to each of the subscribing users' endpoints. This allows the subscribing users to also generate a view of the user's aggregated availability.