Systems and methods for content and service registration, query and subscription, and notification across local service discovery domains

• US 20040255302A1
• Filed: 06/10/2003
• Published: 12/16/2004
• Est. Priority Date: 06/10/2003
• Status: Abandoned Application

• Current Assignee: Nokia Corporation
• Original Assignee: Nokia Corporation
• Inventors: Trossen, Dirk
• Application Number:
  US10/457,866
• Publication Number:
  US 20040255302A1
• Time in Patent Office: Days
• 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 65/401 wherein the services involve a main real-time session and one or more additional parallel real-time or time sensitive sessions, e.g. white board sharing or spawning of a subconference
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04L 67/53 using third party service providers

Abstract

A system and method are provided for subscribing to an event across a local service discovery domain. The system includes a first network entity capable of transmitting a subscription message subscribing to the event, and including an event package description, an event type description, and a description for a service or a content requested. A local event server is capable of receiving the subscription message, and thereafter transmit a subscription message. A remote event server, located in a different local service discovery domain than the local event server, can receive the subscription message from the local event server, and thereafter send a first notify message to the first network entity and/or the local event server.

Claims

1. A method for subscribing to an event maintained by a remote event server across a local service discovery domain, the method comprising:

receiving, at a local event server from a first network entity, a subscription message subscribing to the event, the message having an event package description, an event type description, and a description for one of a service and a content requested;

transmitting a subscription message to at least one remote event server located in a different local service discovery domain than the local event server, wherein the subscription message includes the event package, the corresponding event type and the one of the service and content requested; and

sending a first notify message to at least one of the local event server and the to first network entity.

2. A method according to claim 1 further comprising checking for a match, at the at least one remote event server, for the event package, the corresponding event type, and the one of the service and content requested after transmitting the subscription message to at least one remote server, wherein sending a first notify message comprises sending a first notify message indicating whether the match was located.

3. A method according to claim 1 further comprising checking for a match, at the local event server, for the event package, the corresponding event type, and the one of the service and content requested, wherein checking for a match occurs before transmitting a subscription message, and wherein transmitting a subscription message comprises transmitting a subscription message when no match is located.

4. A method according to claim 3 further comprising:

checking a cache, at the local event server, for a match for the event package, the corresponding event type, and the one of the service and content requested after checking for and failing to locate a match, at the local event server, for the event package, the corresponding event type, and the one of the service and content requested,

wherein transmitting a subscription message occurs when no match is found in the cache, and wherein sending a first notify message comprises sending a first notify message from the local event server to the first network entity when a match is found in the cache.

5. A method according to claim 1, wherein receiving a subscription message comprises receiving, at the local event server from a requester, a subscription message subscribing to the event, and wherein the message includes an event type description comprising at least one of a registered type and a published type.

6. A method according to claim 5 further comprising:

checking for a match, at the local event server, before transmitting a subscription message, wherein transmitting a subscription message comprises transmitting a subscription message when no match is located, wherein checking for a match comprises;

sending a discovery message to a repository, the discovery message requesting information about at least one provider matching the one of the service and content requested; and

receiving a discovery response from the repository, wherein the discovery response is generated in response to the repository checking for a match for the at least one of the service and content requested, and wherein the discovery response contains one of an indication of a non-existing match and at least one provider at least partially matching the one of service and content requested.

7. A method according to claim 5 further comprising:

receiving, at the remote event server, a register message from a provider, wherein the register message comprises an event package description describing an event package comprising one of a service event package and a content event package, an event type description describing a register event type, and one of service and content capability for the provider;

checking for a service/content match of the one of the service and the content capability information for the provider; and

notifying the requester when a service/content match is located and the service/content match includes at least a partial match with one of the service and the content requested by the requester.

8. A method according to claim 1, wherein receiving a subscription message comprises receiving a subscription message further including an expiration time for expiration of the subscription to the event, and wherein the method further comprises:

receiving a register message, at the remote event server from a second network entity, wherein the register message comprises one of service and content capability information for the second network entity at least partially matching the one of the service and content requested from the first network entity; and

sending a second notify message notifying the first network entity of the match with the one of the service and content capability information for the second network entity when the expiration time has not expired.

9. A method according to claim 1, wherein receiving a subscription message comprises receiving, at the local event server from a requester, a subscription message subscribing to the event, the message having an event type description comprising a de-registered type, the method further comprising:

receiving a register message, at the remote event server from a provider, comprising one of service and content capability information for the provider and an event type description describing a de-register event type, wherein the service and content capability information for the provider matches the service and content requested for the requester;

checking for a service/content match of the one of service and content capability information for the provider; and

notifying the requester of the de-registered state of the provider when the service/content match is located.

10. A method according to claim 9, wherein checking for a service/content match comprises comparing, at the remote event server, the service and content capability information for the provider with a subscription database.

11. A method according to claim 1, wherein receiving a subscription message comprises receiving, at the local event server from a provider, a subscription message subscribing to the event, the message having an event type description comprising a requested type.

12. A method according to claim 11 further comprising:

receiving, at the remote event server from a requester, a subscription message comprising an event package description, an event type description describing one of a registered event type and a published event type, and a description for one of a service and a content requested;

checking for a service/content match of one of the service and the content requested by the requester; and

notifying the provider of the subscription message from the requester when a service/content match is located and the match includes at least a partial match with one of the service and the content requested by the requester.

13. A method according to claim 1, wherein receiving a subscription message comprises receiving, at the local event server from a provider, a subscription message subscribing to the event, the message having an event type description comprising a request_removed type, wherein the method further comprises:

receiving, at the remote event server from a requester, a second subscription message requesting removal of a first subscription request requesting one of the service and the content;

checking for a service/content match of one of the service and the content requested in the first subscription request by the requester; and

notifying the provider of the subscription removal message from the requester when a service/content match is located and the match includes at least a partial match with one of the service and the content requested by the requester.

14. A method according to claim 1, wherein receiving a subscription message comprises receiving, at a session initiation protocol (SIP) local event server, a subscription message comprising a SIP SUBSCRIBE message.

15. A method according to claim 14, wherein sending a first notify message comprises sending a SIP NOTIFY message.

16. A method according to claim 1, wherein receiving a subscription message comprises receiving a subscription message including a description for one of a service and a content requested in at least one of an attribute-based format and a description format.

17. A method according to claim 16, wherein receiving a subscription message including a description for one of a service and a content requested having a format selected from the group consisting of Service Location Protocol (SLP) and Resource Description Framework (RDF).

18. A system for subscribing to an event across a local service discovery domain, the system comprising:

a first network entity capable of transmitting a subscription message subscribing to the event, the message having an event package description, an event type description, and a description for one of a service and a content requested;

a local event server capable of receiving the subscription message, and thereafter transmitting a subscription message, wherein the subscription message includes the event package, the corresponding event type and the one of the service and content requested; and

a remote event server located in a different local service discovery domain than the local event server, wherein the remote event server is capable of receiving the subscription message from the local event server, and sending a first notify message to at least one of the local event server and the first network entity.

19. A system according to claim 18, wherein the remote server is capable of checking for a match for the event package, the corresponding event type, and the one of the service and content requested, and wherein the remote server is capable of sending a first notify message indicating whether the match was located.

20. A system according to claim 18, wherein the local event server is capable of checking for a match for the event package, the corresponding event type, and the one of the service and content requested after receiving the subscription message, and wherein the local event server is capable of transmitting a subscription message when no match is located.

21. A system according to claim 20, wherein the local event server is capable of checking a cache for a match when no match is located for the event package, the corresponding event type, and the one of the service and content requested, wherein the local event server transmits the subscription message when no match is found in the cache, and wherein the local event server is capable of sending a first notify message to the first network entity when a match is found in the cache.

22. A system according to claim 18, wherein the first network entity comprises a requester, and wherein the requester is capable of transmitting a subscription message including an event type description comprising at least one of a registered type and a published type.

23. A system according to claim 22, wherein the local event server is capable of checking for a match before transmitting a subscription message, wherein the local event server is capable of transmitting the subscription message when no match is located, wherein the system further comprises:

a repository capable of receiving, from the local event server, a discovery message requesting information about at least one provider matching the one of the service and content requested, wherein the repository is capable of checking for a match for the at least one of the service and content requested, and thereafter transmitting a discovery response containing one of an indication of a non-existing match and at least one provider at least partially matching the one of service and content requested, and wherein the local event server is capable of receiving the discovery response to thereby check for the match.

24. A system according to claim 22 further comprising:

a provider capable of transmitting, to the remote event server, a register message comprising an event package description describing an event package comprising one of a service event package and a content event package, an event type description describing a register event, and one of service and content capability for the provider,

wherein the remote event server is capable of checking for a service/content match of the one of the service and the content capability information for the provider, and wherein the remote event server is capable of notifying the requester when a service/content match is located and the service/content match includes at least a partial match with one of the service and the content requested by the requester.

25. A system according to claim 18, wherein the first network entity is capable of transmitting a subscription message further including an expiration time for expiration of the subscription to the event, and wherein the remote event server is capable of receiving a register message from a second network entity, wherein the register message comprises one of service and content capability information for the second network entity at least partially matching the one of the service and content requested from the first network entity, and wherein the remote event server is capable of sending a second notify message notifying the first network entity of the match with the one of the service and content capability information for the second network entity when the expiration time has not expired.

26. A system according to claim 18, wherein the first network entity comprises a requester, wherein the requester is capable of transmitting a subscription message having an event type description comprising a de-registered type, the system further comprising:

a provider capable of transmitting, to the remote event server, a register message comprising one of service and content capability information for the provider and an event type description describing a de-register event type, wherein the service and content capability information for the provider matches the service and content requested for the requester,

wherein the remote event server is capable of checking for a service/content match of the one of service and content capability information for the provider, and thereafter notifying the requester of the de-registered state of the provider when the service/content match is located.

27. A system according to claim 26, wherein the remote event server is capable of checking for a service/content match by comparing the service and content capability information for the provider with a subscription database.

28. A system according to claim 18, wherein the first network entity is capable of transmitting a subscription message having an event type description comprising a requested type.

29. A system according to claim 28 further comprising:

a requester capable of transmitting a subscription message to the remote event server, wherein the subscription message comprises an event package description, an event type description describing one of a registered event type and a published event type, and a description for one of a service and a content requested,

wherein the remote event server is capable of checking for a service/content match of one of the service and the content requested by the requester, and wherein the remote event server is capable of notifying the provider of the subscription message from the requester when a service/content match is located and the match includes at least a partial match with one of the service and the content requested by the requester.

30. A system according to claim 18, wherein the first network entity is capable of transmitting a subscription message having an event type description comprising a request_removed type, wherein the system further comprises:

a requester capable of transmitting a second subscription message to the remote event server, wherein the second subscription message requests removal of a first subscription request requesting one of the service and the content,

wherein the remote event server is capable of checking for a service/content match of one of the service and the content requested in the first subscription request by the requester, and wherein the remote event server is capable of notifying the provider of the subscription removal message from the requester when a service/content match is located and the match includes at least a partial match with one of the service and the content requested by the requester.

31. A system according to claim 18, wherein the first network entity is capable of transmitting a session initiation protocol (SIP) SUBSCRIBE message, and wherein the local event server comprises a SIP event server.

32. A system according to claim 31, wherein the remote event server is capable of sending a first notify message comprising a SIP NOTIFY message.

33. A system according to claim 18, wherein the first network entity is capable of transmitting a subscription message including a description for one of a service and a content requested in at least one of an attribute-based format and a description format.

34. A system according to claim 33, wherein the subscription message includes a description for one of a service and a content requested having a format selected from the group consisting of Service Location Protocol (SLP) and Resource Description Framework (RDF).

35. A local event server capable of facilitating subscribing to an event across a local service discovery domain, the event associated with at least one of services and content available within a network, the local event server comprising:

a processor capable of receiving, from a first network entity, a subscription message subscribing to the event, the message having an event package description, an event type description, and a description for one of a service and a content requested, wherein the processor is capable of checking for a match for the event package, the corresponding event type, and the one of the service and content requested, and wherein the processor is also capable of transmitting a subscription message to at least one remote event server when no match is located such that the remote event server can send a first notify message to at least one of the local event server and the first network entity.

36. A local event server according to claim 35 further comprising:

a cache capable of storing at least one listing for an event package, a corresponding event type, and a corresponding one of the service and content,

wherein the processor is capable of checking the cache for a match when no match is located for the event package, the corresponding event type, and the one of the service and content requested, wherein the processor is capable of transmitting the subscription message when no match is found in the cache, and wherein the processor is capable of sending a first notify message to the first network entity when a match is found in the cache.