SYSTEM AND METHOD FOR PRESENCE NOTIFICATION BASED ON PRESENCE ATTRIBUTE

• US 20110055369A1
• Filed: 08/14/2007
• Published: 03/03/2011
• Est. Priority Date: 08/14/2006
• Status: Active Grant

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: Samsung Electronics Co. Ltd.
• Inventors: Oh, Jae-Kwon, Patil, Mayuresh Madhukar
• Granted Patent: US 8,849,986 B2
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: H04L 43/10 Active monitoring, e.g. heartbeat, ping or trace-route
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34
• CPC Class Codes: H04L 67/54 Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
• CPC Class Codes: H04M 3/42374 where the information is provided to a monitoring entity such as a potential calling party or a call processing server

Abstract

Provided is a system and method for optimizing the presence notifications. The system includes a presence server which stores the presence subscription and presence information; and a presence XDMS for storing the authorization related information, wherein the presence server store the filtering rule pertaining to presence based notification delivery. The method includes: storing the presence subscription and presence information by a presence server; and storing the authorization related information by a presence XDMS, wherein a filtering rule pertaining to presence based notification delivery is used with the presence server.

Claims

1. A system for presence based presence notification comprising:

a presence server which stores the presence subscription and presence information; and

a presence XDMS for storing the authorization related information,

wherein the presence server stores the filtering rule pertaining to presence based notification delivery.

2. A system as claimed in claim 1, wherein in presence server a Watcher'"'"'s presence based notification blocking filter is stored, where the watcher is authorized to watch presence attributes of a user.

3. A system as claimed in claim 1, wherein when notification is generated to the Watcher the said notification is passed through the Watcher'"'"'s presence based notification blocking filter.

4. A system as claimed in claim 1, wherein the notification is sent to the watcher when the filter allows the said notification.

5. A method for presence based presence notification comprising the steps of:

storing the presence subscription and presence information by a presence server; and

storing the authorization related information by a presence XDMS,

wherein a filtering rule pertaining to presence based notification delivery is used with the presence server.

6. A method as claimed in claim 5, wherein in presence server a Watcher'"'"'s presence based notification blocking filter is stored, where the watcher is authorized to watch presence attributes of a user.

7. A method as claimed in claim 5, wherein when notification is generated to the Watcher the said notification is passed through the Watcher'"'"'s presence based notification blocking filter.

8. A method as claimed in claim 5, wherein the notification is sent to the watcher when the filter allows the said notification.

9. A method as claimed in claim 5, wherein in filtering a Client first constructs a SUBSCRIBE request with the Watcher'"'"'s presence based notification blocking filter body within where the filter contains detailed conditions to be checked before sending the notifications.

10. A method as claimed in claim 9, wherein the presence server receives the SUBSCRIBE request from client and then evaluate the condition.

11. A method as claimed in claim 10, wherein if presence server understands and is able to handle the conditions, then presence server sends a positive response and the subsequent notification with subscription state header and filter with presence attributes.

12. A method as claimed in claim 11, wherein the requested notification blocking filtering is stored into the presence server, and every time when notification is generated, these conditions are checked.

13. A method as claimed in claim 5, wherein network-to-network interfacing is performed between two Presence Server lying in different domain using Route header field.

14-15. -15. (canceled)