Kstore event manager using triggers for K
OwnerJane C. Mazzagatti, Tony Phaninventors
Life of this patent
Estimating the term…
Abstract
The KStore or K is a datastore made up of a forest of interconnected, highly unconventional trees of one or more levels. A KStore event manager monitors events and polls for KStore state. When triggered by user-defined conditions or receiving notification that a specified event has occurred, a specified response can be executed. An event/condition/response is defined through a KStore event wizard. When a triggering condition is detected or a notification of an event is received, a user-defined action or sequence of actions is performed automatically, without further user interaction.
Claims20
A system for managing events in a KStore comprising:
- an event manager comprising:
- a wizard or background feature that receives or obtains
- user input specifying a KStore state, a polling interval and a first action to be performed in response to detecting the specified KStore state or
- user input specifying an internal KStore event and a second action to be performed in response to receiving a notification that the internal KStore event has occurred;
- and
- an event processor that executes
- the first action in response to detecting the specified KStore state or
- the second action in response to receiving the notification that the internal KStore event has occurred, wherein the KStore comprises an interlocking trees datastore comprising elemental root nodes, subcomponent nodes and end product nodes linked by asCase and asResult bi-directional links that create asCase and asResult paths within the interlocking trees datastore, wherein an asCase path comprises a sequence of subcomponent nodes linked with bi-directional asCase links ending with an end product node and where each subcomponent node in the asCase path has a bi-directional asResult link to an elemental root node or end product node comprising an asResult tree.
A method for managing events in a KStore comprising:
- receiving user input, the user input comprising a response comprising an action, event, sequence of actions or sequence of events;
- in response to determining that the user input further comprises a user-specified state to be monitored for in the KStore, prompting and receiving a polling interval at which the KStore is polled for the user-specified state and executing the response in response to detecting the user-specified state in the KStore;
- or
- in response to determining that the user input further comprises a user-specified event, directing a K Engine to send a notification to an event manager, prompting for and receiving the user input comprising the response and executing the response in response to receiving the notification, wherein the KStore comprises an interlocking trees datastore comprising elemental root nodes, subcomponent nodes and end product nodes linked by asCase and asResult bi-directional links that create asCase and asResult paths within the interlocking trees datastore, wherein an asCase path comprises a sequence of subcomponent nodes linked with bi-directional asCase links ending with an end product node and where each subcomponent node in the asCase path has a bi-directional asResult link to an elemental root node or end product node comprising an asResult tree.
A computer-readable medium comprising computer-executable instructions that when executed cause a computing environment to:
- receive user input, the user input comprising a response comprising an action, event, sequence of actions or sequence of events;
- in response to determining that the user input further comprises a user-specified state to be monitored for in the KStore, prompt for a polling interval at which the KStore is polled for the user-specified state, wherein the KStore comprises an interlocking trees datastore comprising elemental root nodes, subcomponent nodes and end product nodes linked by asCase and asResult bi-directional links that create asCase and asResult paths within the interlocking trees datastore, wherein an asCase path comprises a sequence of subcomponent nodes linked with bi-directional asCase links ending with an end product node and where each subcomponent node in the asCase path has a bi-directional asResult link to an elemental root node or end product node comprising an asResult tree.
Dependencies are inferred from the claim text.