Systems and methods for event semantic binding in networks

• US 7,293,271 B2
• Filed: 06/19/2003
• Issued: 11/06/2007
• Est. Priority Date: 06/19/2003
• Status: Expired due to Fees

• Current Assignee: Nokia Corporation
• Original Assignee: Nokia Corporation
• Inventors: Trossen, Dirk, Pavel, Dana
• Primary Examiner(s): Lim; Krisna
• Application Number:
  US10/465,455
• Publication Number:
  US 20040260749A1
• Time in Patent Office: 1,601 Days
• Field of Search: 719/318, 719/331, 719/332, 709/224
• US Class Current: 719/318
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• 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: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A system and method are provided for binding a semantic to an event. The system includes a first network entity capable of transmitting a subscription message including an event package and a semantic description describing a semantic associated with the event package. The system also includes an event server capable of receiving the subscription message. The event server is thereafter capable of generating a semantic package identifier associated with the event package and the semantic description to thereby bind the event package to the semantic description. The event server is further capable of sending a first notify message to the first network entity, where the first notify message includes the semantic package identifier.

Claims

1. A method of binding a semantic to an event maintained by an event server, the event at least partially associated with at least one of services and content available within a network, the method comprising:

receiving, at the event server from a first network entity, a subscription message including an event package and a semantic description describing a semantic associated with the event package;

generating a semantic package identifier associated with the event package and the semantic description to thereby bind the event package to the semantic description; and

sending a first notify message to the first network entity, wherein the first notify message includes the semantic package identifier.

2. A method according to claim 1 further comprising determining whether the event server supports binding the semantic description to the event package before generating the semantic package identifier, wherein generating the semantic package identifier and sending the first notify message comprise generating the semantic package identifier and sending the first notify message if the event server supports binding the semantic to the event package.

3. A method according to claim 1, wherein receiving a subscription message comprises receiving a subscription message identifying an unassigned event package and including a semantic description describing a semantic, wherein the method further comprises:

dynamically assigning an event package to the semantic description before generating the semantic package identifier, wherein sending a first notify message comprises sending a first notify message further including the assigned event package.

4. A method according to claim 1, wherein receiving a subscription message comprises receiving a subscription message including an event package and a uniform resource identifier (URI) to an ontology server, wherein the method further comprises:

retrieving at least a portion of the semantic description from the ontology server based upon the event package, and wherein retrieving at least a portion of the semantic description occurs before generating the semantic package identifier.

5. A method according to claim 1 further comprising:

transmitting, from the first network entity to the event server, a subscription message including the semantic package identifier;

retrieving the event package and bound semantic description based upon the semantic package identifier;

checking for a match for the event package based upon the semantic description; and

sending a second notify message to the first network entity, wherein the second notify message indicates whether the match was located.

6. A method according to claim 5, wherein the semantic description includes a description of information capable of satisfying at least a portion of the semantic description, wherein checking for a match comprises:

retrieving information of at least one resource capable of satisfying at least a portion of the semantic description.

7. A method according to claim 6, wherein retrieving information of at least one resource comprises:

polling at least one resource capable of satisfying at least a portion of the semantic description; and

receiving responses from the resources, wherein the responses are generated in response to the resources checking for a match, and wherein the responses contain one of an indication of a non-existing match and information at least partially matching the information capable of satisfying at least a portion of the semantic description.

8. A system for binding a semantic to an event, the event at least partially associated with at least one of services and content available within a network, the system comprising:

a first network entity capable of transmitting a subscription message including an event package and a semantic description describing a semantic associated with the event package; and

an event server capable of receiving the subscription message, and thereafter generating a semantic package identifier associated with the event package and the semantic description to thereby bind the event package to the semantic description, wherein the event server is also capable of sending a first notify message to the first network entity, and wherein the first notify message includes the semantic package identifier.

9. A system according to claim 8, wherein the event server is further capable of determining whether the event server supports binding the semantic description to the event package before generating the semantic package identifier, and wherein the event server is capable of generating the semantic package identifier and sending the first notify message if the event server supports binding the semantic to the event package.

10. A system according to claim 8, wherein the subscription message identifies an unassigned event package and includes the semantic description describing a semantic, wherein the event server is capable of dynamically assigning an event package to the semantic description before generating the semantic package identifier, and wherein the first notify message further includes the assigned event package.

11. A system according to claim 8, wherein the subscription message includes an event package and a uniform resource identifier (URI), wherein the system further comprises:

an ontology server capable of communicating with the event server based upon the URI, wherein the ontology server is capable of transmitting, to the event server, at least a portion of the semantic description based upon the event package, and wherein the event server is capable of generating the semantic package identifier at least partially based upon the portion of the semantic description received from the ontology server.

12. A system according to claim 8, wherein the first network entity is further capable of transmitting a subscription message including the semantic package identifier, wherein the event server is capable of retrieving the event package and the bound semantic description based upon the semantic package identifier, and thereafter checking for a match for the event package based upon the semantic description, wherein the event server is also capable of sending a second notify message to the first network entity, and wherein the second notify message indicates whether the match was located.

13. A system according to claim 12, wherein event server is capable of checking for a match by retrieving information of at least one resource capable of satisfying at least a portion of the semantic description.

14. A system according to claim 13, wherein the semantic description includes a description of information capable of satisfying at least a portion of the semantic description, wherein the system further comprises:

at least one resource capable of providing the information capable of satisfying at least a portion of the semantic description, wherein the event server is capable of retrieving the information by polling the at least one resource, and thereafter receiving at least one response containing one of an indication of a non-existing match and information at least partially matching the information capable of satisfying at least a portion of the semantic description.

15. An event server capable of binding a semantic to an event, the event at least partially associated with at least one of services and content available within a network, the event server comprising:

a processor capable of receiving, from a first network entity, a subscription message including an event package and a semantic description describing a semantic associated with the event package, wherein the processor is also capable of generating a semantic package identifier associated with the event package and the semantic description to thereby bind the event package to the semantic description, and thereafter sending a first notify message to the first network entity, and wherein the first notify message includes the semantic package identifier.

16. An event server according to claim 15, wherein the processor is further capable of determining whether the event server supports binding the semantic description to the event package before generating the semantic package identifier, and wherein the processor is capable of generating the semantic package identifier and sending the first notify message if the event server supports binding the semantic to the event package.

17. An event server according to claim 15, wherein the subscription message identifying an unassigned event package and including a semantic description describing a semantic, and wherein the processor is capable of dynamically assigning an event package to the semantic description before generating the semantic package identifier.

18. An event server according to claim 15, wherein the subscription message includes an event package and a uniform resource identifier (URI) of an ontology server, wherein the processor is further capable of retrieving, from the ontology server, at least a portion of the semantic description based upon the event package, and wherein the processor is capable of generating the semantic package identifier at least partially based upon the portion of the semantic description received from the ontology server.

19. An event server according to claim 15, wherein the processor is capable of receiving, from the first network entity, a subscription message including the semantic package identifier, wherein the processor is capable of retrieving the event package and bound semantic description based upon the semantic package identifier, and thereafter checking for a match for the event package based upon the semantic description, wherein the processor is also capable of sending a second notify message to the first network entity, and wherein the second notify message indicates whether the match was located.

20. An event server according to claim 15, wherein the processor is capable of checking for a match by retrieving information of at least one resource capable of satisfying at least a portion of the semantic description.

21. An event server according to claim 17, wherein the event package description includes a description information capable of satisfying at least a portion of the semantic description, wherein the processor is capable of retrieving information by:

polling at least one resource capable of providing the information capable of satisfying at least a portion of the semantic description; and

receiving responses from the resources, wherein the responses are generated in response to the resources checking for a match, and wherein the discovery responses contain one of an indication of a non-existing match and information at least partially matching the information capable of satisfying at least a portion of the semantic description.