METHOD AND SYSTEM FOR REDUCING THE NUMBER OF PRESENCE EVENTS WITHIN A NETWORK

• US 20100332597A1
• Filed: 06/30/2009
• Published: 12/30/2010
• Est. Priority Date: 06/30/2009
• Status: Abandoned Application

• Current Assignee: Alcatel-Lucent SA (Nokia Corporation)
• Original Assignee: Alcatel-Lucent USA, Inc. (Nokia Corporation)
• Inventors: Varney, Douglas W.
• Application Number:
  US12/495,308
• Publication Number:
  US 20100332597A1
• Time in Patent Office: Days
• US Class Current: 709/204
• CPC Class Codes: H04L 51/043 using or handling presence information
• CPC Class Codes: H04L 51/214 using selective forwarding
• CPC Class Codes: H04L 51/224 providing notification on incoming messages, e.g. pushed notifications of received messages
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34

Abstract

A method and apparatus for reducing the number of presence events in a network are provided. This is accomplished by segregating close buddies (on a buddy or contact list) from not-so-close buddies (on the list) for purposes of better managing the flow of presence information in a network.

Claims

1. A method for notifying a first user of presence status changes for other users, the method comprising:

detecting a change in presence status for a second user;

determining if the second user is on a first list or a second list;

immediately notifying the first user of the change in presence status if the second user is on the first list; and

,

notifying the first user of the change in presence status upon detection of a predefined event if the second user is on the second list.

2. The method as set forth in claim 1 wherein the first list is a close buddy list.

3. The method as set forth in claim 2 wherein the second list contains identifiers of mobile users not on the close buddy list.

4. The method as set forth in claim 1 wherein the predefined event is the opening of an address book or contact list.

5. The method as set forth in claim 1 further comprising modifying the first and second lists.

6. The method as set forth in claim 1 wherein the first user is a watcher.

7. The method as set forth in claim 1 wherein the second user is a presentity.

8. A system for notifying a first user of presence status changes for other users, the system comprising:

a first client corresponding to the first user;

an XDMS server storing a first list and a second list; and

,

a presence server operative to detect a change in presence status for a second user, determine if the second user is on the first list or the second list, immediately notify the first client of the change in presence status if the second user is on the first list and notify the first client of the change in presence status upon detection of a predefined event if the second user is on the second list.

9. The system as set forth in claim 8 wherein the first list is a close buddy list.

10. The system as set forth in claim 9 wherein the second list contains identifiers of mobile users not on the close buddy list.

11. The system as set forth in claim 8 wherein the predefined event is the opening of an address book or contact list.

12. The system as set forth in claim 8 wherein at least one of the presence server and the first client is further operative to modify the first and second lists.

13. The system as set forth in claim 8 wherein the first client is a watcher.

14. The system as set forth in claim 8 wherein the second user is a presentity.

15. A system for notifying a first user of presence status changes for other users, the system comprising:

means for detecting a change in presence status for a second user;

means for determining if the second user is on a first list or a second list;

means for immediately notifying the first user of the change in presence status if the second user is on the first list; and

,

means for notifying the first mobile user of the change in presence status upon detection of a predefined event if the second user is on the second list.

16. The system as set forth in claim 15 wherein the first list is a close buddy list.

17. The system as set forth in claim 16 wherein the second list contains identifiers of mobile users not on the close buddy list.

18. The system as set forth in claim 15 wherein the predefined event is the opening of an address book or contact list.

19. The system as set forth in claim 15 further comprising modifying the first and second lists.

20. The system as set forth in claim 15 wherein the second user is a presentity.