1. Field
A hardware user interface for anti-virus operations.
2. Background
Viruses present a serious threat to data integrity for the information stored on a computer. Current anti-virus software on the market generally does not have a standardized user interface or usage model for anti-virus operations. Unsophisticated users sometimes find it difficult to operate the anti-virus software or know the status of the anti-virus software on their computers.
Moreover, current anti-virus software mostly uses pop-up windows to interact with the users. These pop-up windows often interrupt the ongoing work or entertainment engaged by the users. Further, when a computer system is infected by virus, its display may also be inflected and fail to pop up warning messages. The computer system may even stop taking input from the keyboard or mouse, thus render it unable to receive any user commands.
Embodiments are illustrated by way of example and not by way of limitation in the figures of the accompanying drawings in which like references indicate similar elements. It should be noted that references to “an” or “one” embodiment in this disclosure are not necessarily to the same embodiment, and such references mean at least one.
System 200 may include an input/output (I/O) controller 250 coupled to memory controller 220. I/O controller 250 may provide an interface for the components of system 200 to access I/O devices 260. I/O devices 260 may include Industry Standard Architecture (ISA) devices, Peripheral Component Interconnect (PCI) devices, PCI Express devices, Universal Serial Bus (USB) devices, Small Computer System Interface (SCSI) devices, or other standard or proprietary I/O devices suitable for server or general applications. In one embodiment, I/O devices 260 may include main display 110 and keyboard 160 of
In one embodiment, main memory 230 may store a copy of anti-virus software 280. Anti-virus software 280 may include anti-virus code and its associated database. Processing core 210 may check the status of anti-virus software 280 and executes the software according to a pre-defined schedule or at an occurrence of a pre-defined event, e.g., during boot-up. As a result, processing core 210 may detect that anti-virus software 280 is out-of-date. Alternatively, processing core 210 may detect the presence of a virus. When processing core 210 detects either of the above events, processing core 210 may instruct microcontroller 270 to alert a user via secondary display 132 and virus indicator button 136 of
Virus indicator button 136 may be implemented by a light-emitting diode (LED) that lights up when an alerting event occurs. Virus indicator button 136 may indicates different virus status with different colors. In one embodiment, virus indicator button 136 may be a pressable button. In alternative embodiments, virus indicator button 136 may be activated by a user by any other suitable mechanisms. Virus indicator button 136 may be integrated with a two-state LED that lights up in red when the presence of a virus on computer 100 is detected. Virus indicator button 136 may light up in yellow when anti-virus software 280 is out-of-date. Pressing virus indicator button 136 when it is red triggers processing core 210 to clean the detected virus. During the virus cleaning process, processing core 210 may report its working process to the user on secondary display 132. Pressing virus indicator button 136 when it is yellow triggers processing core 210 to search for the latest patch for anti-virus software 280. When the latest patch is found, processing core 210 may apply the patch to update software 280. The LED light of virus indicator button 136 is off after the virus is cleaned up or software 280 is updated. If the user presses virus indicator button 136 when the LED light is off, a regular hard disk virus scan may be performed. Although red and yellow are disclosed as the color of the two-state LED, it is understood that any other colors may be used to indicate different virus status.
In one embodiment, secondary display 132 may be implemented by a liquid crystal module (LCM), a light emitting diode (LED) display, or any other suitable display mechanisms. Secondary display 132 may present virus information to the user, thus avoiding popping up dialog windows on main display 110. Using secondary display 132 also avoids interruptions to the user's ongoing work on main display 110. Moreover, as there are no software windows on secondary display 132 to cover the virus information, messages on secondary display 132 catch the user's attention more easily than those on main display 110. Unlike conventional I/O devices which are typically susceptible to virus attacks, the virus that inflects conventional I/O devices does not usually affect the separate anti-virus hardware (e.g., microcontroller 270, secondary display 132, user buttons 134, and virus indicator button 136). Thus, the virus usage model described herein is more robust than a conventional software user interface.
Referring also to
In some scenarios, user intervention may be requested to proceed with the anti-virus operation. For example, the user may be requested to determine whether an infected file should be deleted. In one embodiment, microcontroller 270 (
Secondary display 132 may continue to present other virus information and requests until the virus is finally cleaned up from the entire system. Referring to
In addition to virus information, secondary display 132 may be used as a user interface for other system activities that may be of interest to the user. Referring back to
Computing systems that may use the above anti-virus usage module may include personal desktop/laptop computers, servers, personal digital assistants, network processors, or any other suitable wired or wireless systems.
In the foregoing specification, specific embodiments have been described. It will, however, be evident that various modifications and changes can be made thereto without departing from the broader spirit and scope of the appended claims. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense.
Filing Document | Filing Date | Country | Kind | 371c Date |
---|---|---|---|---|
PCT/CN06/01549 | 7/3/2006 | WO | 00 | 9/1/2006 |