System and method for controlling SIP-specific event notification according to preference of subscriber

Patent metadata

Field	Value
Publication number	US-9553940-B2
Application number	US-19582708-A
Country	US
Kind code	B2
Filing date	Aug 21, 2008
Priority date	Aug 21, 2007
Publication date	Jan 24, 2017
Grant date	Jan 24, 2017

Abstract

Disclosed is a system and method for controlling Session Initiation Protocol (SIP)-specific event notification corresponding to an event subscription according to a preference of a subscriber. The system includes the subscriber requesting an event subscription through an event notification controller; a subscription target for notifying the subscriber of the event through the event notification controller in response to the event subscription request; and the event notification controller for controlling whether the event notification is forwarded to the subscriber according to the preference rules of the subscriber on event notifications. Accordingly, the event notifications to the subscriber can be effectively controlled according to the preference rules of the subscriber on event notifications, and it is possible to prevent the generation of unnecessary event notification that the subscriber does not desire.

First claim

What is claimed is:

1. An event notification controller for controlling Session Initiation Protocol (SIP)-specific event notification according to a preference of a subscriber, the event notification controller comprising:
a transceiver configured to receive an event subscription request from the subscriber; and
a processor configured to control the transceiver to:
forward the event subscription request to a subscription target in a presentity domain when recognizing that the event notification controller is in a different domain than the subscription target,
receive an event notification from the subscription target if preference rules on event notification set by the subscriber allow the event notification, and
forward the event notification received from the subscription target to the subscriber according to the preference rules,
wherein the event notification controller is in a watcher domain, and
wherein if the preference rules do not allow the event notification, the processor is further configured to request the subscription target to hold the event notification.

2. The event notification controller as claimed in claim 1 , wherein the processor is further configured to control the transceiver to receive the event subscription request including the preference rules of the subscriber on the event notifications set by the subscriber, extracts the preference rules of the subscriber from the event subscription request, and stores the extracted preference rules therein.

3. The event notification controller as claimed in claim 1 , wherein the processor is further configured to control the transceiver to receive an SIP PUBLISH including the preference rules of the subscriber on event notifications set by the subscriber, extracts the preference rules of the subscriber from the received SIP PUBLISH, and stores the extracted preference rules therein.

4. The event notification controller as claimed in claim 1 , wherein the processor is further configured to control the transceiver to receive the preference rules of the subscriber on the event notifications forwarded by an eXtensible Markup Language (XML) Document Management Server (XDMS) of the subscriber, and stores the received preference rules therein.

5. The event notification controller as claimed in claim 1 , wherein the event notification controller exists within the subscription target.

6. The event notification controller as claimed in claim 5 , wherein,
when the subscription target generates an event notification, the processor checks the preference rules of the subscriber on the event notifications and notifies the subscriber of an event according to the event notification to the subscription target.

7. The event notification controller as claimed in claim 1 , wherein the event notification controller exists independently of the subscription target.

8. The event notification controller as claimed in claim 7 , wherein the event notification controller operates in one of a proxy mode and a non-proxy mode.

9. The event notification controller as claimed in claim 8 , wherein, if the event notification controller operates in the non-proxy mode, one SIP is established between the subscriber and the subscription target through the event notification controller.

10. The event notification controller as claimed in claim 8 , wherein, if the event notification controller operates in the proxy mode, an SIP is established between the subscriber and the event notification controller, and a separate SIP is established between the event notification controller and the subscription target.

11. The event notification controller as claimed in claim 10 , wherein,
if the preference rules allow the event notification, the processor is further configured to control the transceiver to forward the event notification to the subscriber, and
if the preference rules of do not allow the event notification, the processor is further configured to store the event notification in the event notification controller until the preference rules allow the event notification.

12. The event notification controller as claimed in claim 7 , wherein,
if the preference rules do not allow the event notification, the processor holds the event notification until the preference rules allow the event notification.

13. The event notification controller as claimed in claim 1 , wherein the processor is further configured to control the transceiver to transmit a temporarily unavailable response to the subscription target if the preference rules do not allow the event notification, and check if the preference rules allow the event notification after a predetermined time.

14. The event notification controller as claimed in claim 1 , wherein the event notification is forwarded according to the preference rules.

15. A method for controlling Session Initiation Protocol (SIP)-specific event notification according to a preference of a subscriber by an event notification controller, in a watcher domain, the method comprising:
receiving an event subscription request from the subscriber;
forwarding the event subscription request to a subscription target, in a presentity domain;
receiving an event notification from the subscription target if preference rules on event notification set by the subscriber allow the event notification; and
forwarding the event notification received from the subscription target to the subscriber, and
wherein if the preference rules do not allow the event notification, the processor is further configured to request the subscription target to hold the event notification.

16. The method as claimed in claim 15 , wherein receiving the event subscription request from the subscriber comprises:
receiving the event subscription request including the preference rules of the subscriber on event notifications set by the subscriber;
extracting the preference rules of the subscriber on the event notifications from the event subscription request; and
storing the extracted preference rules in the event notification controller.

17. The method as claimed in claim 15 , wherein receiving the event subscription request from the subscriber comprises:
receiving an SIP PUBLISH including the preference rules of the subscriber on the event notifications set by the subscriber;
extracting the preference rules of the subscriber on the event notifications from the SIP PUBLISH; and
storing the extracted preference rules in the event notification controller.

18. The method as claimed in claim 15 , wherein receiving the event subscription request from the subscriber comprises:
receiving an SIP PUBLISH including the preference rules of the subscriber on the event notifications forwarded by an eXtensible Markup Language (XML) Document Management Server (XDMS) of the subscriber;
extracting the preference rules of the subscriber on the event notifications from the SIP PUBLISH; and
storing the extracted preference rules in the event notification controller.

19. The method as claimed in claim 18 , wherein the preference rules are previously set and stored in the XDMS by an operation according to RFC4825 entitled “the eXtensible Markup Language (XML) Configuration Access Protocol (XCAP)”, which is an XCAP operation, of the subscriber.

20. The method as claimed in claim 15 , wherein, if event notification corresponds to presence event notification, the subscriber corresponds to a watcher, the subscription target corresponds to a presence server, and the event notification controller corresponds to one of the p

Assignees

• Oh Jae-Kwon
• Kim Wuk
• Samsung Electronics Co Ltd

Inventors

• Oh Jae-Kwon
• Kim Wuk

Classifications

• H04L67/327

  Electricity · mapped topic

• H04L67/306 Primary

  User profiles · CPC title

• H04L67/24 Primary

  Electricity · mapped topic

• H04L67/54 Primary

  Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users · CPC title

• H04L67/63

  Routing a service request depending on the request content or context · CPC title