Method, system and computer program to enable semantic mediation for SIP events through support of dynamically binding to and changing of application semantics of SIP events

• US 20100205298A1
• Filed: 04/21/2010
• Published: 08/12/2010
• Est. Priority Date: 06/07/2004
• Status: Abandoned Application

• Current Assignee: Nokia Corporation
• Original Assignee: Nokia Corporation
• Inventors: Pavel, Dana, TROSSEN, Dirk
• Application Number:
  US12/764,864
• Publication Number:
  US 20100205298A1
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: G06Q 10/109 Time management, e.g. calendars, reminders, meetings or time accounting
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services

Abstract

An event notification system includes a data communications network (18), at least one event server (20) coupled to the data communications network and at least one subscriber (12) coupled to the data communications network. The subscriber is operable to send a subscribe message to the event server, the subscribe message containing information for specifying at least one application semantic. The event server is operable to generate a first notification to the subscriber upon the at least one application semantic being satisfied and to generate a second notification to the subscriber upon a change in the specified application semantic, thereby enabling an occurrence of a substitution of the specified application semantic with another application semantic.

Claims

1. A method to subscribe to an event server to be notified of an occurrence of an event through a data communications network, comprising:

sending a subscribe message from a subscriber to the event server, the subscribe message comprising information for specifying at least one application semantic;

generating a first notification to the subscriber in response to the at least one application semantic being satisfied; and

generating a second notification to the subscriber in response to a change in the specified application semantic, enabling a substitution of the specified application semantic with another application semantic.

2. A method as in claim 1, where the information comprises an application semantic description for enabling the event server to extract ontology information.

3. A method as in claim 1, where the information comprises an address of an ontology server from which ontology information can be retrieved.

4. A method as in claim 1, where the subscribe message employs a “

bind”

event package-template for associating a particular application semantic with a particular event package.

5. A method as in claim 1, where the subscribe message employs a “

generic-bind”

event package-template for dynamically creating at the event server a desired event package with event type information, further comprising extracting information from the message that specifies the desired event package and event type information.

6. A method as in claim 1, where the second notification is generated only if a duration associated with the subscribe message is non-zero.

7. A method as in claim 4, further comprising sending a message to the subscriber from the event server that includes a locally unique identifier that is used by the event server to relate the subscription to the application semantic.

8. A method as in claim 5, further comprising sending a message to the subscriber from the event server that includes a description of the dynamically created event package.

9. A method as in claim 4, where for a case where a duration associated with the subscribe message is one of zero or non-zero the method further comprises storing with the event server a locally unique identifier, associated with the subscriber, in association with subscription information so as to link the subscription of the particular event package to a previously bound application semantic.

10. A method as in claim 1, where the information comprises an address from which ontology information can be retrieved using a content indirection procedure.

11. A method as in claim 1, where said second notification is sent in response to the event server determining a change in the description of the application semantic.

12. A method as in claim 1, where the second notification comprises a description of the changed application semantic.

13. A method as in claim 1, where the second notification comprises an address of a server from which a description of the changed application semantic can be retrieved using a content indirection procedure.

14. A method as in claim 1, where the event server comprises a Session Initiation Protocol (SIP) event server.

15. An event notification system comprising a data communications network, at least one event server coupled to the data communications network, and at least one subscriber coupled to the data communications network, where said subscriber is operable to send a subscribe message to the event server, the subscribe message comprising information for specifying at least one application semantic;

and

where said event server is operable to generate a first notification to the subscriber in response to the at least one application semantic being satisfied and to generate a second notification to the subscriber in response to a change in the specified application semantic, enabling an occurrence of a substitution of the specified application semantic with another application semantic.

16. An event notification system as in claim 15, where the information comprises an application semantic description for enabling the event server to extract ontology information.

17. An event notification system as in claim 15, further comprising at least one ontology server coupled to the data communications network, where the information comprises an address of said ontology server from which ontology information can be retrieved.

18. An event notification system as in claim 15, where the subscribe message employs a “

bind”

event package-template for associating a particular application semantic with a particular event package.

19. An event notification system as in claim 15, where the subscribe message employs a “

generic-bind”

event package-template for dynamically creating at the event server a desired event package with event type information, said event server being further operable to extract information from the message that specifies the desired event package and event type information.

20. An event notification system as in claim 15, where the second notification is generated only if a duration associated with the subscribe message is non-zero.