IP Library Granted Patent US 8,341,649
Granted Patent B2
US 8,341,649 · App. 12/648,704 · Granted Dec 25, 2012

System and method for handling an event in a computer system

Assignee: Wontok, Inc.
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,341,649
App. No.
12/648,704
Granted
Dec 25, 2012
Kind
B2
Abstract

Stack-based system for handling an event in a computer system which has a kernel mode and a user-mode, concurrently by one or more user-mode applications. The systems comprise at least one computing device. The computing device is configured to suspend an occurrence of the event in the kernel-mode of an operating system running thereon. The computing device is also configured to cause the event to occur in the user-mode of the operating system. The computing device is further configured to determine if an occurrence of the event in the kernel-mode will compromise the computer system by analyzing the occurrence of the event in the user-mode. If it is determined that the occurrence of the event in the kernel-mode will compromise the computer system, then the computing device executes at least one security measure.

Claims (38)

1. A system for handling an event in a computer system which has a kernel-mode and a user-mode, the system comprising:

at least one computing device configured to:

(a) suspend an occurrence of the event in the kernel-mode of an operating system running on said computing device;

(b) cause the event to occur in the user-mode for one or more clients of the operating system; and

(c) prioritize occurrence of the event among the one or more clients by use of a stack-based dispatcher.

2. The system as claimed in claim 1 , wherein the one or more clients are configured to influence an operation of the computer system based on the occurrence of the event in the user-mode.

3. The system as claimed in claim 2 , wherein the one or more clients are configured to influence an operation of the computer system by preventing the event from occurring in the kernel-mode.

4. The system as claimed in claim 1 , wherein the computing device is further configured to:

run a user-mode software application operative to issue a request for the suspension of the occurrence of the event in the kernel-mode; and

run a first kernel-mode software module operable to use the request in order to activate a second kernel-mode software module operable to effect suspension of a class of events that comprises the event.

5. The system as claimed in claim 4 , wherein the second kernel-mode software module is further operable to interact with the operating system of the computer system in order to effect the suspension.

6. The system as claimed in claim 4 , wherein the first kernel-mode software module is further operable to issue an indication that the suspension has been effected, and the user-mode software application is further operable to use the indication in effecting the occurrence of the event in the user-mode.

7. The system as claimed in claim 6 , wherein the first kernel-mode software module is further operable to use an interprocess communication mechanism to transfer the indication to the user-mode software application, the user-mode software application being operable to use the interprocess communication mechanism to transfer the request to the first kernel-mode software module.

8. The system as claimed in claim 7 , wherein the interprocess communication mechanism uses an Internet protocol.

9. The system as claimed in claim 6 , wherein the first kernel-mode software module and the user-mode software application are operable to respectively format the indication and the request according to a predefined format.

10. The system as claimed in claim 9 , wherein the predefined format accords with a common information model defined by a distributed management task force.

11. The system as claimed claim 10 , wherein the first kernel-mode software module operates in the kernel mode, and the user-mode software application operates in the user-mode.

12. The system as claimed claim 11 , wherein the user-mode software application comprises an anti-virus scan engine.

13. A method of handling an event in a computer system which has a kernel-mode and a user-mode, the method comprising the following steps performed by at least one computing device:

suspending an occurrence of the event in the kernel-mode of an operating system running on said computing device;

causing the event to occur in the user-mode for one or more clients of the operating system; and

prioritizing occurrence of the event among the one or more clients by use of a stack- based dispatcher.

14. The method as claimed in claim 13 , wherein the method further comprises-the step of influencing an operation of the computer system based on the occurrence of the event in the user-mode.

15. The method as claimed in claim 14 , wherein the step of influencing the operation of the computer system comprises preventing the event from occurring in the kernel-mode.

16. The method as claimed in claim 15 , further comprising the steps of:

issuing a request for the suspension of the occurrence of the event in the kernel-mode; and

using the request in order to activate a kernel-mode software module that is operable to effect suspension of a class of events that comprises the event.

17. The method as claimed in claim 16 , further comprising the step of using the kernel-mode software module to interact with the operating system of the computer system in order to effect the suspension.

18. The method as claimed in claim 16 , further comprising the steps of:

issuing an indication that the suspension has been effected; and

using the indication in effecting the occurrence of the event in the user-mode.

19. The method as claimed in claim 18 , further comprising the step of effecting a transfer of the indication to a user-mode software application for use thereby.

20. The method as claimed in claim 19 , wherein the step of effecting the transfer of the indication comprises using an interprocess communication mechanism.

21. The method as claimed in claim 20 , wherein the interprocess communication mechanism uses an Internet protocol.

22. The method as claimed in claim 18 , further comprising the step of formatting the indication and the request according to a predefined format.

23. The method as claimed in claim 22 , wherein the predefined format accords with a common information model defined by a distributed management task force.

24. The system as claimed in claim 1 , wherein the event is selected from the group comprising a file system input/output based event, a network input/output based event, a memory management input/output based event, and a process management based event.

25. The system as claimed in claim 1 , wherein the computing device is further configured to deny an ability to write data to or read data from a file stored in a memory device of the computer system.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 21, 2011
From: SAFECENTRAL, INC.
To: WONTOK, INC.
Reel/Frame 027424/0250 →
CHANGE OF NAME Recorded Nov 16, 2010
From: AUTHENTIUM, INC.
To: SAFECENTRAL, INC.
Reel/Frame 025376/0553 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 26, 2010
From: FREERICKS, HELMUTH; KOUZNETSOV, OLEG
To: AUTHENTIUM, INC.
Reel/Frame 023846/0848 →
Priority Claims (1)
AU 2004903759 · Jul 8, 2004 · national
Continuity (3)
Continuation In Part 11175006 · Jul 5, 2005
Provisional Application 60585520 · Jul 6, 2004
Related Publication 20100138843A1 · Jun 3, 2010