SYSTEM AND METHOD FOR SPECULATIVE REMOTE DISPLAY

• US 20100030842A1
• Filed: 07/30/2007
• Published: 02/04/2010
• Est. Priority Date: 07/30/2007
• Status: Active Grant

• Current Assignee: Northwestern University
• Original Assignee: Northwestern University
• Inventors: Dinda, Peter, Rossoff, Sam
• Granted Patent: US 7,991,831 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: H04L 41/0631 using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
• CPC Class Codes: H04L 67/08 specially adapted for terminal emulation, e.g. Telnet

Abstract

Certain embodiments of the present invention provide for a system and method for network computing. In an embodiment, the system may include a storage unit for archiving historical user events and historical server events. The system may also include a processing unit for receiving a current user event and generating one or more predicted server events. The processing unit may execute a screen update based on the one or more predicted server events. The system may also include a comparison unit having computer software for comparing one or more predicted server events with one or more server-supplied server events. The one or more server-supplied server events may be generated based on the current user event. In an embodiment, the system also includes an undo unit having computer software for executing an undo algorithm. The undo unit alters the non-matching events to match the server-supplied server events.

Claims

1. A system for network computing, said system comprising:

a storage unit for archiving historical user events and historical server events;

a processing unit for receiving a current user event and generating one or more predicted server events, wherein said processing unit executes a screen update based on said one or more predicted server events;

a comparison unit having computer software for comparing said one or more predicted server events with one or more server-supplied server events, wherein said one or more server-supplied server events are generated based on a triggering event.

2. The system of claim 1, wherein said triggering event is said current user event.

3. The system of claim 1, wherein said triggering event is a predetermined interval of time.

4. The system of claim 1, wherein said triggering event is an arrival of a server-supplied server event.

5. The system of claim 1, further comprising an undo unit, wherein if there is a difference between said one or more predicted server events and said one or more server-supplied server events, an undo unit having computer software for executing an undo algorithm alters the non-matching events to match the server-supplied server event.

6. The system of claim 1, further comprising an undo unit, wherein if the difference between said one or more predicted server events and said one or more server-supplied server events is greater than a threshold value, an undo unit having computer software for executing an undo algorithm alters the non-matching events to match the server-supplied server event.

7. The system of claim 1, wherein said storage unit, said processing unit, and said comparison unit are located in an intermediate device.

8. The system of claim 1, wherein said storage unit, said processing unit, and said comparison unit are located in a client.

9. The system of claim 8, wherein a mirror storage unit, mirror processing unit, and mirror comparison unit are located in a server, wherein said server transmits to said client error correction information.

10. A method for network computing, said method comprising:

storing historical user events and historical server events;

receiving a current user event;

generating one or more predicted server events;

executing a screen update based on said one or more predicted server events;

comparing said one or more predicted server events with one or more server-supplied server events, wherein said one or more server-supplied server events are generated based on a triggering event.

undoing one or more of said predicted server events executed as part of said screen update using an undo algorithm if one or more of said predicted server events is different than said one or more server-supplied server events.

11. The method of claim 10, wherein said triggering event is said current user event.

12. The system of claim 10, wherein said triggering event is a predetermined interval of time.

13. The system of claim 10, wherein said triggering event is an arrival of a server-supplied server event.

14. The method of claim 10, wherein said one or more predicted server events are generated according to one or more of the following:

predicted user events, historical user events, historical predicted server events, historical server-supplied server events.

15. The method of claim 10, wherein said undo algorithm is an undo-logging algorithm.

16. The method of claim 10, wherein said undo algorithm is a redo-logging algorithm.

17. The method of claim 10, wherein said undo algorithm requests a refresh of information from a server.

18. The method of claim 17, wherein said undo algorithm requests a refresh of information from a server at periodic intervals for a periodic update.

19. The method of claim 18, wherein said undo algorithm identifies the last periodic update and then executes a redo-logging algorithm.

20. The method of claim 10, wherein said undo algorithm identifies the incorrect region on the display to the user.

21. The method of claim 20, wherein said undo algorithm identifies the incorrect region on the display to the user using an alpha mask.

22. A computer readable medium including a set of instructions for execution by a computer, said set of instructions comprising:

a storage routine for storing historical user events and historical server events;

a receiving routine for receiving a current user event;

a generating routine for generating one or more predicted server events;

an execution routine for executing a screen update based on said one or more predicted server events;

a comparison routine for comparing said one or more predicted server events with one or more server-supplied server events, wherein said one or more server-supplied server event is generated based on a triggering event.

23. The set of instructions of claim 22, wherein said triggering event is said current user event.

24. The set of instructions of claim 22, wherein said triggering event is a predetermined interval of time.

25. The set of instructions of claim 22, wherein said triggering event is an arrival of a server-supplied server event.

26. The set of instructions of claim 22, further comprising an undo routine for executing an undo algorithm if said one or more predicted server events is different than said one or more server-supplied server events.

27. The set of instructions of claim 22, wherein said generating routine receives one or more of the following:

predicted user events, historical user events, historical predicted server events, historical server-supplied server events.

28. The set of instructions of claim 22, wherein said generating routine is using a k-th order state-space-limited Markov model.