Instant message user management
First Claim
1. A computer-implemented method of managing user information in an instant messaging (“
- IM”
) system, comprising;
using a data structure to record IM activity on behalf of a particular user of the IM system, wherein;
the data structure comprises a plurality of entries, each of the entries corresponding to a selected one of a plurality of other IM users remembered, by the IM system, on behalf of an IM client of the particular user;
each of the entries comprises;
an identifier of the selected one of the plurality of remembered IM users to which the entry corresponds;
a first date indicating when the particular user last sent an instant message to the selected one;
a first time period indicating a first inactivity period allowed before the particular user wants the selected one to be treated as expired, the first inactivity period corresponding to inactivity on outbound instant messages sent from the particular user to the selected one;
a second date indicating when the particular user last received an instant message from the selected one;
a second time period indicating a second inactivity period allowed before the particular user wants the selected one to be treated as expired, the second inactivity period corresponding to inactivity on inbound instant messages received by the particular user from the selected one; and
a current expiration status of the selected one; and
the first time period in at least one of the entries is different from the second time period in that one of the entries;
upon sending an instant message from the particular user to any of the plurality of remembered IM users, automatically updating the first date in the entry corresponding to that remembered IM user to a current date and setting the current expiration status in the entry to indicate that the corresponding one of the remembered users is not yet expired;
upon receiving an instant message by the particular user from any of the plurality of remembered IM users, automatically updating the second date in the entry corresponding to that remembered IM user to the current date and setting the current expiration status in the entry to indicate that the corresponding one of the remembered users is not yet expired;
periodically evaluating the entries in the data structure to determine, for the IM client of the particular user, whether any of the plurality of remembered users should be treated as expired, further comprising, for each of the entries for which the current expiration status indicates that the corresponding one of the remembered users is not yet expired;
adding the first time period from the entry to the first date from the entry, thereby computing an outbound inactivity comparison date;
adding the second time period from the entry to the second date from the entry, thereby computing an inbound inactivity comparison date;
selecting a first-occurring one of the outbound inactivity comparison date and the inbound inactivity comparison date; and
setting the current expiration status in the entry to indicate that the corresponding one of the remembered users is to be treated as expired if the selected first-occurring one is prior to the current date; and
for each one of the plurality of remembered users for whom the current expiration status of the corresponding entry in the data structure indicates that that one of the remembered users is to be treated as expired, omitting this user when performing IM presence management functions of the IM system but not deleting this one of the remembered users from the plurality of users remembered by the IM system on behalf of the IM client.
1 Assignment
0 Petitions
Accused Products
Abstract
Techniques are disclosed for improving management of user information in instant messaging systems. Expiration criteria are defined, whereby one or more users or user groups may be considered as having “expired” from consideration by instant messaging functions such as presence determination. In particular, instant messaging activity is preferably used as an expiration criterion. Absence of inbound or outbound messages for a specified amount of time (or since a particular date/time) can therefore be used as a trigger for treating a user or group of users as expired. As a result, efficiency of an instant messaging system is improved by omitting the expired users and groups from subsequent management operations. Optionally, an expired user or group may be revived upon occurrence of certain events (such as a newly-arriving instant message from, or a change in presence status of, the user or group). “On-demand” expiration and revival are preferably provided as well.
-
Citations
3 Claims
-
1. A computer-implemented method of managing user information in an instant messaging (“
- IM”
) system, comprising;using a data structure to record IM activity on behalf of a particular user of the IM system, wherein; the data structure comprises a plurality of entries, each of the entries corresponding to a selected one of a plurality of other IM users remembered, by the IM system, on behalf of an IM client of the particular user; each of the entries comprises;
an identifier of the selected one of the plurality of remembered IM users to which the entry corresponds;
a first date indicating when the particular user last sent an instant message to the selected one;
a first time period indicating a first inactivity period allowed before the particular user wants the selected one to be treated as expired, the first inactivity period corresponding to inactivity on outbound instant messages sent from the particular user to the selected one;
a second date indicating when the particular user last received an instant message from the selected one;
a second time period indicating a second inactivity period allowed before the particular user wants the selected one to be treated as expired, the second inactivity period corresponding to inactivity on inbound instant messages received by the particular user from the selected one; and
a current expiration status of the selected one; andthe first time period in at least one of the entries is different from the second time period in that one of the entries; upon sending an instant message from the particular user to any of the plurality of remembered IM users, automatically updating the first date in the entry corresponding to that remembered IM user to a current date and setting the current expiration status in the entry to indicate that the corresponding one of the remembered users is not yet expired; upon receiving an instant message by the particular user from any of the plurality of remembered IM users, automatically updating the second date in the entry corresponding to that remembered IM user to the current date and setting the current expiration status in the entry to indicate that the corresponding one of the remembered users is not yet expired; periodically evaluating the entries in the data structure to determine, for the IM client of the particular user, whether any of the plurality of remembered users should be treated as expired, further comprising, for each of the entries for which the current expiration status indicates that the corresponding one of the remembered users is not yet expired; adding the first time period from the entry to the first date from the entry, thereby computing an outbound inactivity comparison date; adding the second time period from the entry to the second date from the entry, thereby computing an inbound inactivity comparison date; selecting a first-occurring one of the outbound inactivity comparison date and the inbound inactivity comparison date; and setting the current expiration status in the entry to indicate that the corresponding one of the remembered users is to be treated as expired if the selected first-occurring one is prior to the current date; and for each one of the plurality of remembered users for whom the current expiration status of the corresponding entry in the data structure indicates that that one of the remembered users is to be treated as expired, omitting this user when performing IM presence management functions of the IM system but not deleting this one of the remembered users from the plurality of users remembered by the IM system on behalf of the IM client. - View Dependent Claims (2, 3)
- IM”
Specification