InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Event notifications sent on a periodic basis

IP.com Disclosure Number: IPCOM000126405D
Original Publication Date: 2005-Jul-15
Included in the Prior Art Database: 2005-Jul-15
Document File: 2 page(s) / 27K

Publishing Venue



Disclosed is a method to send frequently occurring event notifications in a maximally-useful way for the interested party, while still keeping the number of notifications reasonable. Essentially, this is done by not sending all notifications, but by picking the notifications that ARE sent carefully.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 2

Event notifications sent on a periodic basis

For a given event, a "notification frequency" (referred to below as the "nf") is defined. This value might be based on the expected number of events in a given time (e.g. an event is expected to happen 10 times a second, but we want to only send notifications approximately once per second), or it might be configurable by the interested party (e.g. a given interested party determines they want a notification on every 2 events, while another might only want a notification every 50 events), or it might be a combination of the two (e.g. an interested party will be given by default an "nf" value based on expected events in a given time, but be able to override the nf value if desired).

     The following rules are used to limit the number of the notifications sent, but also keep the interested party informed: - Notifications are only sent every nf events. - A notification is always sent for the first event, no matter the value of nf. This is so that the interested party can know that "work has been started". - If it is known that a given event is the last event, a notification is always sent for the last event, no matter the value of nf. This is so that the interested party is immediately updated when we know there will be no more events that will occur. - If a certain amount of time has gone by without sending any notifications, but there were events that occurred since the last notification, a notification will be sent. If for example, nf=10, and a notification is sent for the 10th event, 5 more events occur (with no notifications sent), then progress is stopped for some reason such that no more events are occurring, when, let's say, 30 seconds goes by since the notification was sent for the 10th event, a notification will be sent for the 15th (latest) event. This is so that the interested party is brought up-to-date in a somewhat timel...