PREDICATIVE AND PERSISTENT EVENT STREAMS

• US 20110239229A1
• Filed: 03/26/2010
• Published: 09/29/2011
• Est. Priority Date: 03/26/2010
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Beckman, Brian C., Meijer, Henricus Johannes Maria, Manolescu, Dragos A.
• Application Number:
  US12/732,244
• Publication Number:
  US 20110239229A1
• Time in Patent Office: Days
• US Class Current: 719/318
• CPC Class Codes: G06F 9/467 Transactional memory G06F9/528 takes precedence

Abstract

An event driven application may predict a future event and spawn an event stream from the predicted event. The spawned event stream may be performed as a predicted operation until the prediction is confirmed to be correct or incorrect. The predicted operation may generate results that may be present when the prediction is confirmed. In some cases, the results may be used prior to the predicted event, while in other cases, the results may be cached until the prediction is confirmed. In some cases, the predicted operation may be merged with an actual event stream when the predicted event occurs. The prediction mechanism may enhance performance, enable operations that would otherwise be difficult, and may save battery life or energy in some devices.

Claims

1. A method performed on a computer processor, said method comprising:

monitoring an input stream comprising a series of asynchronous events, said monitoring being performed by an observer object, said series of asynchronous events being defined by a collection of asynchronous events, said collection having a data type to which said asynchronous events conform;

determining a history of events from said input stream;

spawning a first event stream in response to a first event in said input event stream, said first event stream comprising a plurality of events;

determining a predicted future event based on said history of events and said current context;

spawning a predicted event stream in response to said predicted future event, said predicted event stream comprising predicted tasks to perform, said predicted tasks being one event on said predicted event stream;

performing a plurality of said predicted tasks in said predicted event stream prior to determining an actual outcome for said future event;

binding said predicted event stream and said first event stream into an output stream; and

dispositioning said predicted task stream based on said actual outcome.

2. The method of claim 1 further comprising:

determining that said actual outcome was equivalent to said predicted event; and

converting said predicted event stream to a regular event stream.

3. The method of claim 2, said predicted event stream comprising events performed at a lower quality of service than said regular event stream.

4. The method of claim 1 further comprising:

determining that said actual outcome was not equivalent to said predicted event and in response;

halting said predicted event stream;

creating an anti-event for each of said predicted tasks performed in said predicted event stream; and

performing each anti-event, said anti-event being bound to said output event stream.

5. The method of claim 1 further comprising:

determining a current context for said series of events; and

said predicted future event being predicted additionally based on said current context.

6. The method of claim 5, said history of events comprising a history from a plurality of input streams each from a different user.

7. The method of claim 6, said context comprising parameters values describing a current situation.

8. The method of claim 1, said predicted event stream comprising terminating said first event stream.

9. The method of claim 8 further comprising:

determining that said actual outcome was not equivalent to said predicted event and resuming said first event stream.

10. The method of claim 1 further comprising:

identifying an expected event in said input stream, said expected event being identified from said history of events;

determining that said expected event has not occurred; and

causing said predicted event to be determined based on said expected event having not occurred.

11. The method of claim 10, said expected event comprising an interruption to said input stream.

12. The method of claim 1, said predicted event stream being buffered from being bound into said output stream until said actual outcome is determined.

13. The method of claim 12 further comprising:

determining that said actual outcome was equivalent to said predicted event and unbuffering said predicted event stream.

14. A system comprising:

a processor;

an input event monitor that monitors an input stream comprising a series of asynchronous events, said monitoring being performed by an observer object, said series of asynchronous events being defined by a collection of asynchronous events, said collection having a data type to which said asynchronous events conform;

an event predictor that;

predicts a future event and launches a predicted event stream comprising a plurality of tasks to execute in response to said future event; and

binds said predicted event stream into an output stream;

an event dispositioner that;

determines an actual outcome for said event; and

disposes said predicted task stream based on said actual outcome.

15. The system of claim 14, said input event monitor that further:

detects that said series of input events has been interrupted; and

causes said event predictor to perform said predicting.

16. The system of claim 14, said event predictor predicting said future event based in part on a history of events collected from said input event monitor.

17. A method performed on a computer processor, said method comprising:

monitoring an input stream comprising a series of asynchronous events, said monitoring being performed by an observer object, said series of asynchronous events being defined by a collection of asynchronous events, said collection having a data type to which said asynchronous events conform;

determining a history of events from said input stream and at least one other event stream;

spawning a first event stream in response to a first event in said input event stream, said first event stream comprising a plurality of events;

determining a current context for said series of events;

determining a predicted future event based on said history of events and said current context;

spawning a first predicted event stream in response to said first predicted future event, said first predicted event stream comprising predicted tasks to perform, said predicted tasks being one event on said predicted event stream;

performing a first predicted task in said predicted event stream prior to determining an actual outcome for said future event;

spawning a second predicted event stream in response to said first predicted task;

binding said first predicted event stream, said second predicted event stream, and said first event stream into an output stream; and

dispositioning said predicted task stream based on said actual outcome.

18. The method of claim 17 further comprising:

determining that said actual outcome was equivalent to said predicted event;

converting said first predicted event stream to a regular event stream; and

converting said second predicted event stream to a regular event stream.

19. The method of claim 18, said first predicted event stream comprising events performed at a lower quality of service than said regular event stream.

20. The method of claim 17 further comprising:

determining that said actual outcome was not equivalent to said predicted event and in response;

halting said predicted event stream;

creating an anti-event for each of said predicted tasks performed in said first predicted event stream and said second predicted event stream; and

performing each anti-event, said anti-event being bound to said output event stream.