Patent Application
20080201724
For computer users, it can seem unmanageable and even frustrating to keep track of the many operational aspects of even a single computer, such as a home computer or laptop. A computer operating system may have various, and often un-related, system tools for computer system management. In addition, there may be separate user interfaces from which to monitor and control the computer system, such as to schedule file backups, defragment a system drive, add or remove a program, restore the system after a failure, and the like. The separate and un-related management tools, programs, utilities, and user interfaces can create an inefficient and cumbersome environment for a user attempting to coordinate and manage a computer system.
This summary is provided to introduce simplified concepts of a computer system events interface, which is further described below in the Detailed Description. This summary is not intended to identify essential features of the claimed subject matter, nor is it intended for use in determining the scope of the claimed subject matter.
In embodiment(s) of a computer system events interface, the computer system events interface includes past event indicators that each indicate a past computer event. A past event indicator is selectable to initiate an information display pertaining to a corresponding past computer event. The computer system events interface can also include future event indicators that each indicate a future computer event. A future event indicator is selectable to initiate a configuration interface from which corresponding future computer events can be modified. The computer system events interface can also include current event indicators that each indicate a current computer event. A current event indicator is also selectable to initiate a configuration interface from which corresponding current computer events can be modified.
In other embodiment(s) of a computer system events interface, a computer system includes multiple computer devices that are network-connected. A computer device of the computer system includes the computer system events interface that displays computer events corresponding to each of the computer devices. The computer events can include past computer events corresponding to each of the computer devices, current computer events corresponding to each of the computer devices, and/or future computer event corresponding to each of the computer devices.
Embodiments of a computer system events interface are described with reference to the following drawings. The same numbers are used throughout the drawings to reference like features and components:
A computer system events interface provides a user one place from which to view, manage, and control multiple and various computer events corresponding to one or several computer devices. A computer system events interface can include different types of information pertaining to past, current, and/or future computer events for the computer device(s). The information pertaining to computer events can include when a past computer event occurred, when a current computer event occurs, when a future computer event is scheduled to occur, a type of the computer event, and where the computer event occurred. For example, a computer event may utilize or involve internal computer drives and/or devices external to a computer device. Further, a computer event may encompass any combination of user-initiated events and files, system-initiated events and files, and/or software program-initiated events and files.
While features and concepts of the described systems and methods for a computer system events interface can be implemented in any number of different computing systems and environments, embodiments of a computer system events interface are described in the context of the following example systems and environments.
The computer-readable media 110 can maintain software applications, such as an operating system 112 and a computer events application 114. Both the operating system 112 and computer events application 114 can be implemented as computer-executable instructions and executed by the processor(s) 108 to implement embodiments of a computer system events interface. Additionally, computer device 106 can include any number and combination of differing components as further described with reference to the example computer device shown in
The computer events application 114 can monitor computer events corresponding to the computer device 106, and generate a computer system events interface 116 for display on display device 104. The computer system events interface 116 displays computer events corresponding to the computer device 106. Computer “events” can include, but are not limited to, any type of past, current, future, and/or scheduled computer-related event, task, update, configuration, system change, user modification, and the like. Some examples of past, current, future, and/or scheduled computer events include backing up files, a file copy or delete operation, a file modification, defragmenting a system drive, adding or removing a program, updating a program or system feature, creating a system restore point, a system failure or crash, software installation, a driver installation, a system update, a network update, a software trial expiration, a virus signature update, etc.
In various embodiments, a computer system events interface 116 can display computer events corresponding to any type of computer or computing-based device, such as computer device 106. For example, a computer device can include, but is not limited to, any one or combination of a computer, server, client device, desktop computer, portable computer, portable computing-based device (such as a cellular phone and/or combination PDA), appliance device, gaming console, television set-top client device, and/or as any other type of computer device.
In another embodiment, a computer system 118 includes a display device 120 and a computer device 122 (shown as a server device in this example). The display device 120 can be any type of display that renders audio, video, and/or image data. As described with reference to computer device 106, computer device 122 includes one or more processor(s) 108 (e.g., any of microprocessors, controllers, and the like) and any type of computer-readable media 110 to maintain operating system 112 and the computer events application 114. Additionally, computer device 122 can include any number and combination of differing components as further described with reference to the example computer device shown in
In computer system 118, the computer events application 114 can monitor computer events corresponding to computer device 122 as well as any number of additional computer devices 124 and/or server devices 126. The computer events application 114 can also generate a computer system events interface 116 for display on display device 120. In computer system 118, the computer system events interface 116 displays computer events corresponding to computer device 122, and displays computer events corresponding to the additional computer devices 124 and/or server devices 126.
In addition to the various components described with reference to computer device 106 and 122, any of the computer devices can include a communication module for network communication. For example, computer device 122 can communicate with the additional computer devices 124 and/or server devices 126 via a communication network 128. The communication network 128 can be any one or combination of a wide area network (e.g., the Internet), a local area network (LAN), an intranet, an IP-based network, a wireless network, or any other type of communication network.
The various event indicators are also associated with the categories 206 of computer events. The categories 206 include a “User” category of user-initiated and/or user-file computer events; a “System” category of system-initiated and/or system-file computer events; and a “Programs” category of program-initiated computer events. An example of a computer event associated with a “User” category is a backup of user files. Examples of computer events associated with a “System” category include a backup of the system files, a system failure or crash, creating a system restore point, and the like. Examples of computer events associated with a “Programs” category include adding, removing, or updating programs (also referred to as “software” or “applications”). The “User”, “System”, and “Programs” categories are merely example classifications and/or groupings of computer events. Any other types of labels, categories, groupings, and/or identifiers may be implemented to associate various computer events on a computer system events interface.
A computer event corresponding to computer device 204 can encompass any one or all of the categories 206. For example, event indicator 208 indicates a computer backup of user files, system files, and the program data to an external DVD drive 212. Event indicator 214 indicates a file backup of user files and system files to a local drive of computer device 204. Event indicator 216 indicates a computer event associated with a program, such as a program update. The computer system events interface 202 also includes a program designation 218 to indicate which computer program has been added, removed, updated, and the like.
The computer system events interface 202 also includes an event sequence 220 to indicate a relationship between past, current, and/or future computer event(s). In this example, the event sequence 220 is ordered by dates, but can be ordered, indexed, or otherwise sequenced by any system, such as by a time sequence, a date and time index, a numeric index, an alphanumeric index, and the like. Past computer events are distinguished from future computer events by a “Today” line 222, or other similar “Now” or “Current” indication that indicates the present date and/or time.
The computer system events interface 202 also includes a computer region 224 that indicates computer events, such as the file backup to a local drive of the computer device 204 indicated by event indicator 214. The computer system events interface 202 also includes an external region 226 (i.e., external to the computer device 204) that indicates computer events, such as a computer backup to an external “Drive (E:)” 228 as indicated by event indicator 230. The external region 226 may also indicate a computer backup to an external volume if storage media is virtualized.
The computer system events interface 202 provides a user one place from which to view, manage, and control multiple and various computer events corresponding to computer device 204. The computer system events interface 202 includes different types of information pertaining to computer events for computer device 204. The information pertaining to computer events can include when a past computer event occurred, when a current computer event occurs, when a future computer event is scheduled to occur, a type of the computer event, and where the computer event occurred (e.g., a user, system, and/or programs category, as well as within the computer device and/or at a device external to the computer device). For example, event indicator 230 indicates a past computer event for a complete computer backup to external drive 228 for each of the user, system, and programs categories on July 16. Further, event indicator 232 indicates a future computer event for a scheduled file backup of only the user files to external “Drive (E:)” 228 on August 14.
An event indicator in the computer system events interface 202 can indicate a result of a corresponding past computer event. For example, event indicator 234 includes an indication that a program update was not successful. Event indicators can also provide a visual indication corresponding to a functional aspect of a computer event. For example, the width of event indicator 230 indicates that the computer backup on July 16 included considerably more computer data than the computer backup on July 2, as indicated by the smaller event indicator 208.
The computer system events interface 202 represents functional properties of computer events (e.g., time, amount, status, etc.) by using visual properties (e.g., position, size, color, etc) of the event indicators. These types of visual representations take advantage of user strengths in pattern recognition and make it easier for a user to comprehend large amounts of information about the computer system. A user can get a quick overview from the computer system events interface 202, as well as determine the differences and interdependencies between various computer events. For example, a computer user or administrator looking at the computer system events interface 202 can quickly determine that a system restore point was created before a program installation. For example, event indicator 236 indicates that a system restore point was created prior to the program update on July 12, as indicated by the event indicator 216. The computer system events interface 202 also indicates whether a computer event such as the system restore point was created by an administrator or user of the computer 204, by the computer system, and/or by an application or program.
The computer system events interface 202 can include event indicators that indicate user-defined events associated with the computer device 204. For example, event indicator 238 has a designation to indicate that a user, “John”, defined the event to note it's occurrence in relation to the other computer events in the event sequence 220. For example, a user of the computer 204 may create an event indicator when another person uses the computer, or for some other reason to note when the computer system may be changed intentionally or unintentionally. The user can diagnose from the event sequence 220 that a problem or change to the computer may have occurred as indicated by the user-defined event indicator 238. The user can then go back to a system restore point as indicated by event indicator 240. In an embodiment, event indicator 238 can be associated with a calendar program on the computer device 204 such that a user of the computer 204 can define the event in the calendar.
The computer system events interface 202 can include any number of various selectable controls to initiate a display change of the computer system events interface. For example, a selectable control 242 can pivot the view of the categories 206 and the computer drives in regions 224, 226. Further, a slider control 244 can be selected to “slide” the event sequence 220 for a view of other event indicators corresponding to past computer events or future computer events. The display range or span of the event sequence 220 may also be adjusted to show any number of months, various selectable points in the sequence, filtered event indicators, and the like.
The computer system events interface 202 can include any number of various selectable controls to filter the event indicators and display particular types of computer events. For example, the categories 206 of “User”, “System”, and “Programs” can be filtered with selectable controls such as 246 to add, select, and/or filter the computer events. Further, the computer system events interface 202 can be filtered to independently display any one or more event indicators of computer events, such as just the computer file backups, program updates, system restore points, and the like. The various selectable controls on the computer system events interface 202 can be implemented as any combination of drop-down menus, slide controls, pivot controls, selectable mouse “right-click” features, scroll bars, zoom in/out, event filtering, and the like.
In another example, event indicator 232 indicates a future computer event and is selectable by a user to initiate configuration interface 304 from which the future computer event can be controlled, rescheduled, and/or modified. An example of a modification to a future computer event includes clicking on a computer drive destination (e.g., “Drive (E:)”, “Local (C:)”, etc.) to change the destination of a scheduled file and/or system backup. A future computer event can also be modified by clicking on a date and/or time field to reschedule or update a planned backup. The future computer event can also be selected and dragged to reposition it in the event sequence 220 to reschedule or update the planned backup.
Alternatively, a user may select or click on a future event indicator to initiate a settings “wizard” which assists the user through a sequence of configuration settings for a computer event. In an embodiment, an event indicator may indicate a group of scheduled computer events combined as one event, such as an event labeled “computer maintenance”. A user can combine computer events as a group which may include a system backup, a drive defragment, a scan for malware, and a computer event to create a system restore point.
In another example, the program update indicated by event indicator 216 is selectable by a user to initiate an information and/or configuration interface 306 from which the corresponding program can be modified, updated, uninstalled, and/or other program actions initiated. In addition, the information and/or configuration interface 306 can include program properties and information such as program installation details, various updates, and usage details. In another embodiment, a program event indicator, such as the event indicator 216, can be selected, dragged, and dropped onto a “Recycle Bin” icon or other similar trash or garbage indicator to uninstall the program associated with the event indicator.
In another embodiment of a computer system events interface 202, a user may select an event indicator that initiates a search for information and/or a connection to an Internet repository or other information exchange. For example, event indicator 234 includes the indication that a program update was not successful. The event indicator 234 is selectable to initiate an Internet search for information pertaining to the failure of the program update.
The computer system events interface 402 includes a representation of each computer device 404(1-4). Each representation of a computer device 404 includes various event indicators and the categories 406 of the corresponding computer events. The computer system events interface 402 also includes an event sequence 408 to indicate a relationship between past, current, and/or future computer event(s). Past computer events are distinguished from future computer events by a “Today” line 410 (or other similar “Now” or “Current” indication) that indicates the present date and/or time across all of the computer device representations.
The representations of the multiple computer devices 404(1-4) provides a visual pattern for a user or system administrator to recognize discrepancies between computer events for the different computer devices. For example, it is easy to determine that computer device 404(2) did not have a computer backup at 412 on July 16 when a backup was initiated for all of the other computer devices. This provides a visual indication utilizing pattern recognition to prompt a user when managing a system of multiple computer devices.
In an embodiment, a future computer event can be defined or scheduled on the computer system events interface 402 at a computer device and then applied to any or all of the other computer devices. For example, a user can define future computer event 414 at computer device 404(1) and then apply the defined computer event at 416 to any one or more of the other computer devices 404(2-4).
The computer system events interface 402 also includes a “Highlight Differences” selectable control 418. When selected, differences between computer events on the multiple computer devices 404(1-4) are highlighted and similarities are masked to distinguish the differences. An example is illustrated in
In this example, the “masked” items are depicted as being thinner, lighter lines when compared to the computer system events interface shown in
The computer system events interface 602 includes a representation of each computer device 604(1-4). Each representation of a computer device 604 includes various event indicators 606(1-4) and 608(1-4), and includes the categories 610 of the corresponding computer events. The computer system events interface 602 also includes an event sequence 612 to indicate a relationship between past, current, and future computer event(s). Past computer events are distinguished from future computer events by a “Now” line 614 (or other similar “Current” indication) that indicates the present time and/or date across all of the computer device representations.
In an embodiment, the event indicators 606(1-4) and 608(1-4) can each indicate a current computer event that is a long-running or extended task at a respective computer device 604(1-4). For example, computer events such as defragmenting a drive or copying large files may run as processes that encompass several minutes and/or hours as indicated by the event sequence 612. Some computer events may also include processes that encompass more than one day. Further, a long-running or extended current task may be indicated as having been partially completed in the “past” and continuing into the “future”, such as event indicators 606(1-4) which cross the “Now” line 614. The computer system events interface 602 can be utilized by a user or administrator as a single viewing source to monitor and manage the progress of several simultaneously running processes, rather than having to monitor multiple, independent progress dialogs for each process.
Generally, any of the functions, methods, and modules described herein can be implemented using hardware, software, firmware (e.g., fixed logic circuitry), manual processing, or any combination thereof. A software implementation of a function, method, or module represents program code that performs specified tasks when executed on a computer processor. Example method 800 described with reference to
At block 802, past event indicators are displayed that each indicate a past computer event. For example, computer system events interface 202 (
At block 804, a past event indicator is displayed to indicate a result of a corresponding past computer event. For example, computer system events interface 202 includes past event indicator 234 that indicates a program update was not successful. Further, the width of event indicator 230 indicates that a computer backup included considerably more computer data than a previous computer backup, as indicated by the smaller event indicator 208. The event indicators can provide a visual indication corresponding to a functional aspect of a computer event.
At block 806, current event indicators are displayed that each indicate a current computer event. For example, computer system events interface 602 includes current event indicators 606(1-4) that each indicate a process running on respective computer devices 604(1-2). A current computer event can be indicated as having been partially completed in the “past” and continuing into the “future”, such as event indicators 606(1-4) which cross the “Now” line 614 of the event sequence 612.
At block 808, future event indicators are displayed that each indicate a future computer event. For example, computer system events interface 202 includes a future event indicator 232 that indicates a future computer event corresponding to computer device 204. In another example, computer system events interface 402 includes future event indicators that each indicate a future computer event corresponding to multiple computer devices 404(1-4).
At block 810, an event sequence is displayed to indicate when a computer event occurs in relation to other computer events. For example, computer system events interface 202 includes event sequence 220 to indicate when the past computer events occurred in relation to each other, and to indicate when the future computer event will occur in relation to additional future computer events. An event sequence can indicate any type of date, time, and/or other relationship between past, current, and/or future computer event(s).
At block 812, one or more categories of related computer events are displayed. For example, computer system events interface 202 includes categories 206. In an embodiment, one of the categories is displayed as a “User” category to indicate user-initiated and/or user-file computer events. Another category is displayed as a “System” category to indicate system-initiated and/or system-file computer events. Another category is displayed as a “Programs” category to indicate program-initiated computer events. The “User”, “System”, and “Programs” categories are merely example classifications and/or groupings of computer events. Any other types of labels, categories, groupings, and/or identifiers may be implemented to associate various computer events on a computer system events interface.
Computer device 900 includes one or more input interface(s) 902 by which any type of data inputs can be received. Computer 900 further includes communication interface(s) 904 which can be implemented as any one or more of a serial and/or parallel interface, a wireless interface, any type of network interface, a modem, and as any other type of communication interface for external communication, such as with networked devices and systems.
Computer device 900 also includes one or more processor(s) 906 (e.g., any of microprocessors, controllers, groups thereof, and the like). The processors 906 process various computer-executable instructions to control the operation of computer 900, to communicate with other electronic and computing devices, and to implement embodiments of a computer system events interface.
Computer device 900 can be implemented with computer-readable media 908, such as one or more memory components, examples of which include random access memory (RAM), non-volatile memory (e.g., any one or more of a read-only memory (ROM), flash memory, EPROM, EEPROM, etc.), and a disk storage device. A disk storage device can include any type of magnetic or optical storage device, such as a hard disk drive, a recordable and/or rewriteable compact disc (CD), a DVD, a DVD+RW, and the like.
Computer-readable media 908 provides data storage mechanisms to store various information and/or data such as software applications and any other types of information and data related to operational aspects of computer device 900. For example, an operating system 910 and/or other application programs 912 can be maintained as software applications with the computer-readable media 908 and executed on processor(s) 906 to implement embodiments of a computer system events interface.
As an application program, computer events application 914 can be maintained with the computer-readable media 908 and executed on processor(s) 906 to implement embodiments of a computer system events interface. In various embodiments, the computer events application 914 monitors, receives, requests, receives, registers, and/or otherwise obtains the information and data from within any one or several computer devices to display the event indicators for computer events on a computer system events interface. Although the computer events application 914 is illustrated and described as a single application, the computer events application 914 can be implemented as several component applications or modules distributed to perform one or more functions of a computer system events interface.
Computer device 900 also includes an audio and/or video output 916 to provide audio and video data to an audio rendering and/or display system 918. The audio rendering and/or display system can include any devices that process, display, and/or otherwise render audio, video, and image data. Video signals and audio signals can be communicated from device 900 to a display device 920 via an RF (radio frequency) link, S-video link, composite video link, component video link, DVI (digital video interface) link, analog audio connection, or other similar communication link. Alternatively, the audio rendering and/or display system 918 are integrated components of the computer device 900.
Although shown separately, some of the components of computer 900 can be implemented in an application specific integrated circuit (ASIC). Additionally, a system bus (not shown) typically connects the various components within computer 900. A system bus can be implemented as one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, or a local bus using any of a variety of bus architectures.
Although embodiments of a computer system events interface have been described in language specific to features and/or methods, it is to be understood that the subject of the appended claims is not necessarily limited to the specific features or methods described. Rather, the specific features and methods are disclosed as example implementations of a computer system events interface.
