Using database query technology for message subscriptions in messaging systems

• US 6,487,548 B1
• Filed: 05/06/1999
• Issued: 11/26/2002
• Est. Priority Date: 05/08/1998
• Status: Expired due to Term

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Leymann, Frank, Roller, Dieter
• Primary Examiner(s): Breene, John
• Assistant Examiner(s): Ali, Mohammad
• Application Number:
  US09/305,987
• Time in Patent Office: 1,300 Days
• Field of Search: 707/1-10, 707/100-104, 707/200-203, 707/501, 707/205, 345/333, 705/7, 705/9, 705/38, 709/206, 709/217, 709/202, 709/315, 709/229, 709/246
• US Class Current: 707/628
• CPC Class Codes: G06F 16/24568 Data stream processing; Continuous queries
• CPC Class Codes: G06F 16/335 Filtering based on additional data, e.g. user or group profiles filtering in web context G06F16/9535, G06F16/9536
• CPC Class Codes: Y10S 707/954 Relational
• CPC Class Codes: Y10S 707/955 Object-oriented
• CPC Class Codes: Y10S 707/956 Hierarchical
• CPC Class Codes: Y10S 707/959 Network
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching

Abstract

The present invention relates to messaging systems in general and message broker systems in specific. More particularly, the invention relates to means and a method for processing message publication requests and message subscription requests.

The current invention transforms the subscription problem into a database query problem allowing to use query techniques known and optimized for many years. The basic approach of the current invention is to invert the relationship of message publication requests (treated as database data) and message subscription requests (treated as database queries) according the state of the art. Thus the core of the current invention is to treat incoming messages publication requests as database queries and to treat message subscription requests as database queries.

Claims

1. A messaging system comprising:

first receiving means for receiving a message-publication-request comprising a message to be published;

second receiving means for receiving one or more message-subscription-requests comprising a query on a message; and

a database,

said second receiving means treating said message-subscription-request as database data and storing said message-subscription-request to said database, and

said first receiving means treating said message-publication-request as a database-query and retrieving from said database a collection of message-subscription-requests qualifying under said database-query.

2. Messaging system according to claim 1, wherein said second receiving means transforms said message-subscription-request into a database data representation.

3. Messaging system according to claim 1, wherein said first receiving means transforms said message-publication-request into a database-query.

4. Messaging system according to claim 1, wherein said first receiving means stores said message into said database or into a separate message-database.

5. Messaging system according to claim 1, wherein said messaging system is a message broker and/or wherein said database is part of a message warehouse.

6. Messaging system according to claim 1, wherein said database is stored in main memory and/or on persistent memory.

7. Messaging system according to claim 6,

wherein said database is a relational database or a hierarchical database or a network database or an object-oriented database or a collection of flat files.

8. Messaging system according to claim 1, further comprising sending means for sending said message to subscribers of said collection of message-subscription-requests.

17. Messaging system according to claim 2, wherein said first receiving means transforms said message-publication-request into a database-query.

18. Messaging system according to claim 17, further comprising sending means for sending said message to subscribers of said collection of message-subscription-requests.

9. A method of processing a message-publication-request comprising a message to be published, and one or more message-subscription-requests comprising a query on a message, said method comprising the steps of:

treating said message-subscription-request as database data and storing said message-subscription-request to a database; and

treating said message-publication-request as a database-query and retrieving from said database a collection of message-subscription-requests qualifying under said database-query.

10. Method according to claim 9, further comprising a step of transforming said message-subscription-request into a database data representation.

11. Method according to claim 9, further comprising a step of transforming said message-publication-request into a database-query.

12. Method according to claim 9, wherein in said step of treating said message-subscription-request as database data, said message is stored into said database or into a separate message-database.

13. Method according to claim 9, wherein said method is executed by a message broker and/or wherein said database is part of a message warehouse.

14. Method according to claim 9, further comprising a step of storing said database in main memory and/or on persistent memory.

15. Method according to claim 14,

wherein said database is a relational database or a hierarchical database or a network database or an object-oriented database or a collection of flat files.

16. Method according to claim 9, further comprising a step of sending said message to subscribers of said collection of message-subscription-requests.

19. Method according to claim 10, further comprising a step of transforming said message-publication-request into a database-query.

20. Method according to claim 19, further comprising a step of sending said message to subscribers of said collection of message-subscription-requests.