US6910070B1
Expired / Lapsed
US
⏱️ 0.0 years remaining
Methods and systems for asynchronous notification of database events
Assignee: Oracle International Corp
•
Filing: 2000-01-24
•
Granted: 2005-06-21
•
Expires: 2020-01-24
Abstract
Abstract A method for asynchronously notifying an application client of a system or data event of interest within a database includes steps of receiving a subscription to an event name from a logical agent, the event name corresponding to the event of interest, and receiving a registration from the application client, the registration including delivery information indicating at least where and how a notification concerning the event is to be delivered. The occurrence of the event is then detected within the database, whereupon the notification of the detected event is published to a data structure referenced by the event name. The delivery information is then retrieved and the published notification is formatted according to the retrieved delivery information. The formatted notification is then asynchronously delivered to the application client over a network, such as the Internet. The application client may specify a rule, the satisfaction of which is a precondition to the delivery of the notification. The application client, in this manner, receives only the notification for which it has subscribed and receives the notifications substantially contemporaneously with the occurrence of the system or data event.
Inventors
- 👤 Shailendra K. Mishra
- 👤 Lakshminarayanan Chidambaran
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-10-29 12:05
CPC Classifications
G; G06; G06F; G06F9/00; G06F9/06; G06F9/46; G06F9/54; G06F9/542; G06F16/00; G06F16/20; G06F16/24; G06F16/245; G06F16/2455; G06F16/24564; G06F16/24565; H; H04; H04L; H04L67/00; H04L67/14; H04L67/50; H04L67/54; G06F2209/00; G06F2209/54; G06F2209/544; Y; Y10; Y10S; Y10S707/00; Y10S707/99951; Y10S707/99952
Claims Analysis
Total Claims: 45
Claim 1
Independent Claim
132 words
A computer implemented method of asynchronously notifying an application client of an event of interest that occurs within a database, comprising the steps of: receiving a subscription to an event name from a logical agent, the event name corresponding to the event of interest that occurs within the database; receiving a registration from the application client, the registration including delivery information indicating at least where and how a notification concerning the event is to be delivered; detecting an occurrence of the event within the database; publishing the notification to a data structure referenced by the event name upon detecting the occurrence of the event; retrieving the delivery information and formatting the published notification according to the retrieved delivery information, and asynchronously delivering the formatted notification to the application client over a network.
Claim 2
Dependent Claim
132 words
A computer implemented method of asynchronously notifying an application client of an event of interest that occurs within a database, comprising the steps of: receiving a subscription to an event name from a logical agent, the event name corresponding to the event of interest that occurs within the database; receiving a registration from the application client, the registration including delivery information indicating at least where and how a notification concerning the event is to be delivered; detecting an occurrence of the event within the database; publishing the notification to a data structure referenced by the event name upon detecting the occurrence of the event; retrieving the delivery information and formatting the published notification according to the retrieved delivery information, and asynchronously delivering the formatted notification to the application client over a network.
Claim 3
Dependent Claim
30 words
The computer implemented method of claim 1 , wherein the detecting step is carried out by a trigger within the database, the trigger firing upon the occurrence of the event.
Claim 4
Dependent Claim
29 words
The computer implemented method of claim 1 , wherein the delivery information includes an identification of a communication protocol according to which the formatted notification is to be sent.
Claim 5
Dependent Claim
24 words
The computer implemented method of claim 1 , wherein the subscription includes a rule that must be satisfied for the notification to be published.
Claim 6
Dependent Claim
16 words
The computer implemented method of claim 4 , wherein the rule includes database access language statements.
Claim 7
Dependent Claim
25 words
The computer implemented method of claim 1 , wherein the data structure includes a queue, the queue being stored as a table in the database.
Claim 8
Dependent Claim
31 words
The computer implemented method of claim 1 , wherein the retrieving step is carried out by an event monitor, the event monitor communicating with the database through a shared memory space.
Claim 9
Dependent Claim
40 words
The computer implemented method of claim 1 , wherein the delivery information includes indicia of a quality of service specified by the application client, the quality of service indicia indicating whether the notification must be delivered to the application client.
Claim 10
Dependent Claim
49 words
The computer implemented method of claim 8 , wherein a temporarily undeliverable notification may be dropped if the indicia indicates that an unreliable quality of service is specified and wherein the temporarily undeliverable notification must be stored if the indicia indicates that a reliable quality of service is specified.
Claim 11
Dependent Claim
59 words
The computer implemented method of claim 9 , wherein the data structure includes a persistent queue when the indicia indicates that a reliable quality of service is specified, the persistent queue persisting beyond an instance of the database and wherein the data structure includes a non-persistent queue when the indicia indicates that an unreliable quality of service is specified.
Claim 12
Dependent Claim
47 words
The computer implemented method of claim 1 , wherein the formatting step formats the notification according to a protocol selected from a group including Internet Inter-Orb Protocol (iiop), Hypertext Transfer Protocol (http), Simple Mail Transfer Protocol (smtp), File Transfer Protocol (ftp), net8 or Open Financial exchange (OFX).
Claim 13
Dependent Claim
40 words
The computer implemented method of claim 1 , wherein the application client is remote from the database and separated therefrom by a network, and wherein the delivering step delivers the formatted notification to the remote application client over the network.
Claim 14
Dependent Claim
27 words
The computer implemented method of claim 12 , wherein the network includes at least one the Internet, a private network, a public network and a hybrid network.
Claim 15
Dependent Claim
62 words
The computer implemented method of claim 1 , wherein the event of interest includes one of a data event and a system event, the data event signaling a change of interest to the application client in a data resident in the database and the system even signaling a change of interest to the application client within the computerized system storing the database.
Claim 16
Dependent Claim
149 words
A machine-readable medium having data stored thereon representing sequences of instruction which, when executed by a computer, causes said computer to asynchronously notify an application client of an event of interest that occurs within a database by performing the steps of: receiving a subscription to an event name from a logical agent, the event name corresponding to the even of interest that occurs within the database; receiving a registration from the application client, the registration including delivery information indicating at least where and how a notification concerning the event is to be delivered; detecting an occurrence of the even within the database; publishing the notification to a data structure referenced by the event name upon detecting the occurrence of the event; retrieving the delivery information and formatting the published notification according to the retrieved delivery information, and asynchronously delivering the formatted notification to the application client over a network.
Claim 17
Dependent Claim
149 words
A machine-readable medium having data stored thereon representing sequences of instruction which, when executed by a computer, causes said computer to asynchronously notify an application client of an event of interest that occurs within a database by performing the steps of: receiving a subscription to an event name from a logical agent, the event name corresponding to the even of interest that occurs within the database; receiving a registration from the application client, the registration including delivery information indicating at least where and how a notification concerning the event is to be delivered; detecting an occurrence of the even within the database; publishing the notification to a data structure referenced by the event name upon detecting the occurrence of the event; retrieving the delivery information and formatting the published notification according to the retrieved delivery information, and asynchronously delivering the formatted notification to the application client over a network.
Claim 18
Dependent Claim
29 words
The machine-readable medium of claim 15 , wherein the detecting step is carried out by a trigger within the database, the trigger firing upon the occurrence of the event.
Claim 19
Dependent Claim
27 words
The machine-readable of claim 15 , wherein the delivery information includes an identification of a communication protocol according to which the formatted notification is to be sent.
Claim 20
Dependent Claim
23 words
The machine-readable medium of claim 15 , wherein the subscription includes a rule that must be satisfied for the notification to be published.
Claim 21
Dependent Claim
15 words
The machine-readable medium of claim 18 , wherein the rule includes database access language statements.
Claim 22
Dependent Claim
24 words
The machine-readable medium of claim 15 , wherein the data structure includes a queue, the queue being stored as a table in the database.
Claim 23
Dependent Claim
30 words
The machine-readable medium of claim 15 , wherein the retrieving step is carried out by an event monitor, the event monitor communicating with the database through a shared memory space.
Claim 24
Dependent Claim
39 words
The machine-readable medium of claim 15 , wherein the delivery information includes indicia of a quality of service specified by the application client, the quality of service indicia indicating whether the notification must be delivered to the application client.
Claim 25
Dependent Claim
48 words
The machine-readable medium of claim 22 , wherein a temporarily undeliverable notification may be dropped if the indicia indicates that an unreliable quality of service is specified and wherein the temporarily undeliverable notification must be stored if the indicia indicates that a reliable quality of service is specified.
Claim 26
Dependent Claim
58 words
The machine-readable medium of claim 23 , wherein the data structure includes a persistent queue when the indicia indicates that a reliable quality of service is specified, the persistent queue persisting beyond an instance of the database and wherein the data structure includes a non-persistent queue when the indicia indicates that an unreliable quality of service is specified.
Claim 27
Dependent Claim
30 words
The machine-readable medium of claim 15 , wherein the formatting step formats the notification according to a protocol selected from a group including iiop, http, smtp, ftp, Net8 or OFX.
Claim 28
Dependent Claim
39 words
The machine-readable medium of claim 15 , wherein the application client is remote from the database and separated therefrom by a network, and wherein the delivering step delivers the formatted notification to the remote application client over the network.
Claim 29
Dependent Claim
26 words
The machine-readable medium of claim 26 , wherein the network includes a least one the Internet, a private network, a public network and a hybrid network.
Claim 30
Dependent Claim
61 words
The machine-readable medium of claim 15 , wherein the event of interest includes one of a data event and a system event, the data event signaling a change of interest to the application client in a data resident in the database and the system event signaling a change of interest to the application client within the computerized system storing the database.
Claim 31
Dependent Claim
157 words
A computer system for asynchronously notifying an application client of an event of interest that occurs within a database, said computer system comprising: at least one processor; at least one data storage device; a plurality of processes spawned by said at least one processor, the processes including processing logic for; receiving a subscription to an event name from a logical agent, the event name corresponding to the event of interest that occurs within the database; receiving a registration from the application client, the registration including delivery information indicating at least where and how a notification concerning the event is to be delivered; detecting an occurrence of the event within the database; publishing the notification to a data referenced by the event name upon detecting the occurrence of the event; retrieving the delivery information and formatting the published notification according to the retrieved delivery information, and asynchronously delivering the formatted notification to the application client over a network.
Claim 32
Dependent Claim
157 words
A computer system for asynchronously notifying an application client of an event of interest that occurs within a database, said computer system comprising: at least one processor; at least one data storage device; a plurality of processes spawned by said at least one processor, the processes including processing logic for; receiving a subscription to an event name from a logical agent, the event name corresponding to the event of interest that occurs within the database; receiving a registration from the application client, the registration including delivery information indicating at least where and how a notification concerning the event is to be delivered; detecting an occurrence of the event within the database; publishing the notification to a data referenced by the event name upon detecting the occurrence of the event; retrieving the delivery information and formatting the published notification according to the retrieved delivery information, and asynchronously delivering the formatted notification to the application client over a network.
Claim 33
Dependent Claim
29 words
The computer system of claim 29 , wherein the detecting step is carried out by a trigger within the database, the trigger firing upon the occurrence of the event.
Claim 34
Dependent Claim
27 words
The computer system of claim 29 , wherein the subscription includes an identification of a communication protocol according to which the formatted notification is to be sent.
Claim 35
Dependent Claim
24 words
The computer system of claim 29 , wherein the delivery information includes a rule that must be satisfied for the notification to be published.
Claim 36
Dependent Claim
15 words
The computer system of claim 32 , wherein the rule includes database access language statements.
Claim 37
Dependent Claim
24 words
The computer system of claim 29 , wherein the data structure includes a queue, the queue being stored as a table in the database.
Claim 38
Dependent Claim
30 words
The computer system of claim 29 , wherein the retrieving step is carried out by an event monitor, the event monitor communicating with the database through a shared memory space.
Claim 39
Dependent Claim
39 words
The computer system of claim 29 , wherein the delivery information includes indicia of a quality of service specified by the application client, the quality of service indicia indicating whether the notification must be delivered to the application client.
Claim 40
Dependent Claim
48 words
The computer system of claim 36 , wherein a temporarily undeliverable notification may be dropped if the indicia indicates that an unreliable quality of service is specified and wherein the temporarily undeliverable notification must be stored if the indicia indicates that a reliable quality of service is specified.
Claim 41
Dependent Claim
58 words
The computer system of claim 37 , wherein the data structure includes a persistent queue when the indicia indicates that a reliable quality of service is specified, the persistent queue persisting beyond an instance of the database and wherein the data structure includes a non-persistent queue when the indicia indicates that an unreliable quality of service is specified.
Claim 42
Dependent Claim
30 words
The computer system of claim 29 , wherein the formatting step formats the notification according to a protocol selected from a group including iiop, http, smtp, ftp, Net8 or OFX.
Claim 43
Dependent Claim
39 words
The computer system of claim 29 , wherein the application client is remote from the database and separated therefrom by a network, and wherein the delivering step delivers the formatted notification to the remote application client over the network.
Claim 44
Dependent Claim
26 words
The computer system of claim 40 , wherein the network includes at least one the Internet, a private network, a public network and a hybrid network.
Claim 45
Dependent Claim
61 words
The computer system of claim 29 , wherein the event of interest includes one of a data event and a system event, the data event signaling a change of interest to the application client in a data resident in the database and the system event signaling a change of interest to the application client within the computerized system storing the database.
References Cited (Backward Citations)
US6012095A
Cited
US6189038B1
Cited
US6088737A
Cited
US6092102A
Cited
US6343320B1
Cited
US6167448A
Cited
US6505244B1
Cited
US6539427B1
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2008-06-20 | 2008-12-20 | 2009-06-21 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2012-06-20 | 2012-12-20 | 2013-06-21 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2016-06-20 | 2016-12-20 | 2017-06-21 | $7700.00 | Window Closed / Lapsed |