← Back to Patent Explorer
EP0959416A2 Expired / Lapsed EP ⏱️ 0.0 years remaining

Using database query technology for message subscriptions in messaging systems

Assignee: International Business Machines Corp
•
Filing: 1999-04-22
•
Granted: —
•
Expires: 2019-04-22
📄 Original PDF 🌐 Google Patents 🔄 Sync Now

Abstract

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.

Inventors

  • 👤 Frank Dr. Leymann
  • 👤 Dieter Dipl.-Phys. Roller

Bibliographic Details

Application Number —
Jurisdiction EP
Data Source google_patents
Last Synchronized 2026-10-29 06:13
CPC Classifications
G; G06; G06F; G06F16/00; G06F16/20; G06F16/24; G06F16/245; G06F16/2455; G06F16/24568

Claims Analysis

Total Claims: 16
Claim 1
Independent Claim 101 words
A messaging system comprising first receiving means for receiving a message-publication-request comprising a message to be published, and said messaging system comprising a second receiving means for receiving one or a multitude of message-subscription-requests comprising a query on a message qualifying under said query, said messaging system being characterized by comprising a database (301), and wherein said second receiving means treating said message-subscription-request as database data and storing said message-subscription-request to said database (301), and wherein said first receiving means treating said message-publication-request as a database-query (302) and retrieving from said database a collection (303) of message-subscription-requests qualifying under said database-query.
Claim 2
Dependent Claim 19 words
Messaging system according to claim 1, wherein said second receiving means transforming said message-subscription-request into a database data representation.
Claim 3
Dependent Claim 19 words
Messaging system according to any of above claims, wherein said first receiving means transforming said message-publication-request into a database-query.
Claim 4
Dependent Claim 24 words
Messaging system according to any of above claims, wherein said first receiving means store said message into said database or into a separate message-database.
Claim 5
Dependent Claim 26 words
Messaging system according to any of above claims, wherein said messaging system is a message broker and/or wherein said database is part of a message warehouse.
Claim 6
Dependent Claim 20 words
Messaging system according to any of above claims, wherein said database is stored in main memory and/or on persistent memory.
Claim 7
Dependent Claim 31 words
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.
Claim 8
Dependent Claim 23 words
Messaging system according to any of above claims, further comprising sending means for sending said message to subscribers of said collection of message-subscription-requests.
Claim 9
Independent Claim 79 words
A method of processing a message-publication-request comprising a message to be published, and one or a multitude of message-subscription-requests comprising a query on a message qualifying under said query, said method comprising the following steps: a first step of treating said message-subscription-request as database data and storing said message-subscription-request to said database (301), and a second step of treating said message-publication-request as a database-query (302) and retrieving from said database a collection (303) of message-subscription-requests qualifying under said database-query.
Claim 10
Dependent Claim 24 words
Method according to claim 1, wherein said first step is preceded by a subscription-transformation-step wherein said message-subscription-request is transformed into a database data representation.
Claim 11
Dependent Claim 25 words
Method system according to claim 9 or 10, wherein said second step is preceded by a message-transformation-step wherein said message-publication-request is transformed into a database-query.
Claim 12
Dependent Claim 24 words
Method according to any of claims 9 to 11, wherein said first step stores said message into said database or into a separate message-database.
Claim 13
Dependent Claim 28 words
Method according to any of claim 9 to 12, wherein said method is executed by a message broker and/or wherein said database is part of a message warehouse.
Claim 14
Dependent Claim 19 words
Method according to any of claims 9 to 13, storing said database in main memory and/or on persistent memory.
Claim 15
Dependent Claim 30 words
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.
Claim 16
Dependent Claim 25 words
Method according to any of claims 9 to 15, further comprising a third step of sending said message to subscribers of said collection of message-subscription-requests.

References Cited (Backward Citations)

No citation records indexed.

USPTO Annuity & Maintenance Windows

Maintenance schedule is calculated for granted US utility patents.

Assigned Categories & Tags

No categories assigned to this patent yet.

Assign Category Tag