Managing rich presence collections in a single request
First Claim
1. A computer-implemented method implemented by a presence system for managing one or more presence publications in a publication, data store accessible by a handheld device of a user, comprising:
- receiving a batch publication request having a first presence publication and a second presence publication published by the handheld device, the first presence publication including data indicating a first expire type and a first category, the second presence publication including data indicating a second expire type and a second category, the first expire type being different from the second expire type;
storing the first and second presence publications in the publication data store;
identifying an event associated with the handheld device;
determining whether the event is associated with at least one of the handheld device is offline and the user is offline; and
in response to the determination that the event is associated with at least one of the handheld device is offline and the user is offline;
removing the first presence publication from the publication data store unless the first expire type is a static type or a user type; and
removing the second presence publication from the publication data store unless the second expire type is a static type or a user type.
1 Assignment
0 Petitions
Accused Products
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.
-
Citations
20 Claims
-
1. A computer-implemented method implemented by a presence system for managing one or more presence publications in a publication, data store accessible by a handheld device of a user, comprising:
-
receiving a batch publication request having a first presence publication and a second presence publication published by the handheld device, the first presence publication including data indicating a first expire type and a first category, the second presence publication including data indicating a second expire type and a second category, the first expire type being different from the second expire type; storing the first and second presence publications in the publication data store; identifying an event associated with the handheld device; determining whether the event is associated with at least one of the handheld device is offline and the user is offline; and in response to the determination that the event is associated with at least one of the handheld device is offline and the user is offline; removing the first presence publication from the publication data store unless the first expire type is a static type or a user type; and removing the second presence publication from the publication data store unless the second expire type is a static type or a user type. - View Dependent Claims (2, 3, 4, 12, 13, 18)
-
-
5. A computer-readable storage device containing instructions for managing one or more presence publications in a publication data store accessible by a handheld device of a user, by a method comprising:
-
receiving a batch publication request having a first presence publication and a second presence publication published by the handheld device, the first presence publication including data indicating a first expire type and a first category, the second presence publication including data indicating a second expire type and a second category; storing the first and second presence publications in the publication data store; identifying an event associated with the handheld device; determining whether the event is associated with at least one of the handheld device is offline and the user is offline; and in response to the determination that the event is associated with at least one of the handheld device is offline and the user is offline; removing the first presence publication from the publication data store unless the first expire type indicates the first expire type is a static type or a user type; and removing the second presence publication from the publication data store unless the second expire type is a static type or a user type. - View Dependent Claims (6, 7, 8, 14, 15, 19)
-
-
9. A system for managing one or more presence publications, comprising:
-
a publication data store that; receives a batch publication request having a first presence publication and a second presence publication published by a handheld device of a user, the first presence publication including data indicating a first expire type and a first category, the second presence publication including data indicating a second expire type and a second category; and stores the first and second presence publications in the publication data store; a handheld device capable of accessing the publication data store; and an expire publications component that; identifies an event associated with the handheld device; determines whether an event is associated with at least one of the handheld device is offline and the user is offline; and in response to the determination that the event is associated with at least one of the handheld device is offline and the user is offline; removes the first presence publication from the publication data store unless the first expire type is a static type or a user type; and removes the second presence publication from the publication data store unless the second expire type is a static type or a user type. - View Dependent Claims (10, 11, 16, 17, 20)
-
Specification