The present invention is related to the following copending United States Patent Applications filed concurrently herewith, assigned to the assignee of the present invention, and hereby incorporated by reference in their entireties:
The invention relates generally to computer systems, and more particularly to an improved method and system for activating a computer system.
Computer users typically activate their computers using a combination of a power button and a password. Many users shut down their computers at the end of the day and then must restart them the next morning. Even with improvements in boot time, restarting the computer often takes several minutes.
At the same time, although some contemporary computers provide card key access such as a smartcard, they often require a user to login into accounts using a password. In some cases, users are required to enter two passwords to gain system access. Powering up a computer and then logging in can be a time consuming and cumbersome process.
What is needed is a simplified way to provide secure access and easy activation of a computer.
Briefly, the present invention provides a system and method for improved activation of a personal computer and/or other processing devices where it is desirable to provide secure access and easy activation. Power and security states are combined and further reduced to three activation states which may be operated by a single secure device. The system may include any number of activation states for operating the computer using only the single secure device.
The secure access device of the present invention may handle both security and power management by authenticating physical access to the computer and the identity of the user. For this purpose, an exemplary device containing a biometric reader may be combined with a smart card and the biometric identification used as an authentication code to secure the smartcard. In one exemplary embodiment, the smartcard device is integrated with the biometric thumb sensor as a key which may be inserted into a locking mechanism used by the user to transition between activation states.
In general, a computer user may easily transition the system between activation modes such as On, Standby and Off by using the single secure activation device. Other advantages will become apparent from the following detailed description when taken in conjunction with the drawings, in which:
Exemplary Operating Environment
The invention is operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well known computing systems, environments, and/or configurations that may be suitable for use with the invention include, but are not limited to: personal computers, server computers, hand-held or laptop devices, tablet devices, headless servers, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.
The invention may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, and so forth, which perform particular tasks or implement particular abstract data types. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in local and/or remote computer storage media including memory storage devices.
With reference to
The computer 110 typically includes a variety of computer-readable media. Computer-readable media can be any available media that can be accessed by the computer 110 and includes both volatile and nonvolatile media, and removable and non-removable media. By way of example, and not limitation, computer-readable media may comprise computer storage media. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by the computer 110.
Combinations of the any of the above should also be included within the scope of computer-readable media.
The system memory 130 includes computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) 131 and random access memory (RAM) 132. A basic input/output system 133 (BIOS), containing the basic routines that help to transfer information between elements within computer 110, such as during start-up, is typically stored in ROM 131. RAM 132 typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit 120. By way of example, and not limitation,
The computer 110 may also include other removable/non-removable, volatile/nonvolatile computer storage media. By way of example only,
The drives and their associated computer storage media, discussed above and illustrated in
The computer 110 may operate in a networked environment using logical connections to one or more remote computers, such as a remote computer 180. The remote computer 180 may be a personal computer, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computer 110, although only a memory storage device 181 has been illustrated in
When used in a LAN networking environment, the computer 110 is connected to the LAN 171 through a network interface or adapter 170. When used in a WAN networking environment, the computer 110 typically includes a modem 172 or other means for establishing communications over the WAN 173, such as the Internet. The modem 172, which may be internal or external, may be connected to the system bus 121 via the user input interface 160 or other appropriate mechanism. In a networked environment, program modules depicted relative to the computer 110, or portions thereof, may be stored in the remote memory storage device. By way of example, and not limitation,
System Activation Combining Power and Security
The present invention is generally directed towards activating a computer system with a simplified security and power architecture. To that end, a system and method are described for improved activation of a personal computer and/or other processing devices where it is desirable to provide secure access and simple activation. Power and security states are combined and further reduced to three activation states which may be operated by a single secure device. The system provides three user-perceived activation states for operating the computer using only a single secure device. As will be understood, the various state diagrams, devices and scenarios described herein are only examples, and there are many other scenarios to which the present invention will apply.
Turning to
If a standby event occurs while the system is in the On state 204, the system transitions from the On state 204 to the Standby state 206. For example, a standby event occurs whenever the user signifies the intention to end the user session, such as by pressing the power button while in the On state 204. Alternatively, the user may generate a standby event by turning off the system through the user interface, such as clicking the Turn Off Computer option in the Start menu of the Windows® XP operating system. If computer 110 is a mobile personal computer, then the user may also generate a standby event by closing the lid of the mobile computer. Yet again, the user session timer may expire due to inactivity for a period of time, and thereby generate a standby event.
When the system transitions from the On state 204 to the Standby state 206, the power management routines of the operating system turn off the main monitor, spin down the hard drives, and shut off the system fans. When the system first enters the Standby state 206, it transitions to the Service sub-state 208 for a predetermined period to process any background tasks pending and advantageously allows the user to quickly transition back from the Standby state 206 to the On state 204 in case the user changes his mind. When the predetermined time expires from user inactivity and there are no background tasks to process, a sleep event is generated and the system transitions from the Service sub-state 208 to the Sleep sub-state 210 within the Standby state 206.
Whenever a wake-up event occurs while the system is in the Sleep sub-state 210, the system transitions from the Sleep sub-state 210 back to the Service sub-state 208 within the Standby state 206. Any incoming communications activity that occurs such as a LAN, modem or USB device activity can be a wake-up event. An application or system service request from an auxiliary processor, if present, can also be a wake-up event. As will be appreciated by those skilled in the art, these are illustrative examples of wake-up events and there are other ways of generating a wake-up event such as from operating system timers.
If a hibernate event occurs while the system is in the Service sub-state 208, the system transitions from the Service sub-state 208 to the Hibernate sub-state 212. A hibernate event occurs whenever power is lost, a critical battery alarm occurs for a mobile personal computer, or a hibernate-timer event occurs. When power is restored, the system returns to Service sub-state 208 from Hibernate sub-state 212 and processes any outstanding background events.
While in the Service sub-state 208, the system may perform background processing to monitor and service activities like incoming communications. Phone calls, emails, instant messages and other incoming communications, meeting reminders, system alerts, and information from Internet subscription services may all trigger a wake-up event for service while the system is in Standby state 206. For example, an email program may be executed in the background to process an incoming email message received on a LAN while the system is in Standby state 206. In processing the email, the email program will send a notification that a new email has arrived. This notification may be forwarded for display on an auxiliary display, if present, to notify the user. If there are no further background tasks to process before the inactivity timer expires, the system transitions from Service sub-state 208 to Sleep sub-state 210.
If the user wishes to return to the fully operational system, the user may transition to the On 204 state from any sub-state of the Standby state 206 with the user context preserved. The system transitions from any sub-state of Standby state 206 to the On state 204 whenever a resume event occurs. For example, a resume event occurs whenever the user signifies the intention to return to the user session, such as by pressing the power button while in the Standby state 206. It will be appreciated by those skilled in the art that there are other ways of generating a resume event, such as opening the lid of a mobile computer. When the system transitions into the On state 204, the power management routines of the operating system turn back on the main monitor, spin the hard drives, and turn back on the system fans.
In addition to transitioning from the On state 204 to the Standby state 206 by the occurrence of a standby event already previously described, the system may also transition to the Hibernate sub-state of Standby state 206 if a power loss occurs while in On state 204. Finally, the system may transition from the On state 204 to the Off state 202 upon the occurrence of either a open-chassis event or a shutdown event. An open-chassis event occurs when the processing unit's 120 chassis is opened. A shutdown event may occur whenever the user depresses the power button for several seconds. Alternatively, the user may generate a shutdown event by shutting down the system through the user interface, such as clicking the Turn Off Computer option in the Start menu of the Windows® XP operating system and then selecting the Shut Down option.
In the Off 202 state, the operating system of the computer 110 is shut down and the user context is discarded. When the computer 110 is in the Off 202 state, it is safe for the user to remove power and open the chassis of the computer 110 to upgrade or repair the hardware.
It will be appreciate by those skilled in the art that the state diagram illustrated in
If the user wishes to change the login password, the user may enter into the user interface security dialog by pressing the system Security Button, if present, or may enter into the user interface security dialog through the user interface, such as by choosing the User Accounts menu option from the Control Panel in the Windows® XP operating system. Those skilled in the art will appreciate that more than one logout timer may be used by the present invention. In one such embodiment, there may be a logout timer for the On power state 204 and another for the Standby power state 206.
If the logout timer expires while in the Logged In sub-state 310, the system transitions to the Locked sub-state 312. While in the Locked sub-state 312, the functionality of the computer 110 is unavailable through the main system interfaces except for the login procedure. The system remains in the Locked sub-state 312 until the user presses the Security Button, if present, or any other button which transitions the system to the Login sub-state 308 where the user may enter into the login procedure.
If a shutdown event occurs while the system is in the On state 306, the system will transition to the Off state 302 upon the occurrence of a shutdown event. A shutdown event automatically logs the user off the system. A shutdown event may occur in any of several ways such as whenever the user depresses the power button for several seconds or logs out of the system through the user interface by entering the logout procedure. The user may also enter into the security dialog by pressing the system Security Button, if present, and then enter the logout procedure. Alternatively, the user may generate a shutdown event by shutting down the system through the user interface, such as clicking the Turn Off Computer option in the Start menu of the Windows® XP.
The system may also transition from the On state 306 to the Standby state 304 whenever a standby event occurs. For example, a standby event occurs whenever the user signifies the intention to end the user session, such as by pressing the power button while in the On state 306. Alternatively, the user may generate a standby event by turning off the system through the user interface, such as clicking the Turn off Computer option in the Start menu of the Windows® XP operating system. If the computer 110 is a mobile personal computer, then the user may also generate a standby event by closing the lid of the mobile computer. Yet again, the user session timer may expire due to inactivity for a period of time, and thereby generate a standby event. When the system enters Standby state 304, the power management routines of the operating system turn off the main monitor, spin down the hard drives, and shut off the system fans.
Finally, the system transitions from the Standby state 304 to the On state 306 upon occurrence of a resume event. For example, a resume event occurs whenever the user signifies the intention to return to the user session, such as by pressing the power button while in the Standby state 304. It will be appreciated by those skilled in the art that there are other ways of generating a resume event, such as opening the lid of a mobile computer. When the system transitions into the On state 306, the power management routines of the operating system turn back on the main monitor, spin the hard drives, and turn back on the system fans. If the logout timer is expired when the resume event occurs, the system transitions to Locked sub-state 312 within the On state 306. If, however, the logout timer is not expired or is not set, then the system transitions to the Logged In sub-state 310 of the On state 306 when the resume event occurs.
It will be appreciate by those skilled in the art that the security state diagram illustrated in
While in the Logged On state 402, there may occur a logout event, a logout timer event, a shutdown event or a standby event. The user may generate a logout event by activating the log out procedure to log off the computer. If there is a logout event, then the system transitions to the Standby Out state 412. If there is a logout timer event, then the system transitions to the Locked On state 404. From there the system transitions to the Logon state 406 if the login procedure is available. Otherwise, if the login procedure is not available, the system will transition to the Standby Out state 412 because a standby event will occur as a result of the user session timer expiring due to inactivity. If there is a shutdown event, then the system transitions to the Off state 408. Finally, if the user session timer expires due to inactivity while in Logged On state 402, then the system transitions to Standby In state 410.
If a resume event occurs while the system is in the Standby In state 410, then the system transitions back to the Logged On state 402. If, however, the logout timer event occurs, the system transitions to the Standby Out state 412. The system will remain in Standby Out state 412 until a resume event occurs.
The activation states of
By simplifying the security and power architecture, the present invention provides three user-perceived activation states. Those skilled in the art will appreciate that the present invention may be used to transition the computer to other access modes such as a fourth state such as Do Not Disturb, a state where the computer is fully operational but incoming communications are handled differently, and so forth, as described in the related patent application Ser. No. 10/429,903, entitled “Computer System with Do Not Disturb System and Method,” In simplifying activation and change of modality of computing devices for users, the method and system described herein provides significant advantages and benefits where it is desirable to provide secure access and simple activation.
While the invention is susceptible to various modifications and alternative constructions, certain illustrated embodiments thereof are shown in the drawings and have been described above in detail. It should be understood, however, that there is no intention to limit the invention to the specific forms disclosed, but on the contrary, the intention is to cover all modifications, alternative constructions, and equivalents falling within the spirit and scope of the invention.
Number | Name | Date | Kind |
---|---|---|---|
4860342 | Danner | Aug 1989 | A |
5159445 | Gitlin | Oct 1992 | A |
5412417 | Tozuka | May 1995 | A |
5487181 | Dailey et al. | Jan 1996 | A |
5519722 | Akman | May 1996 | A |
5533115 | Hollenbach | Jul 1996 | A |
5546538 | Cobbley | Aug 1996 | A |
5568540 | Grecko | Oct 1996 | A |
5657414 | Lett | Aug 1997 | A |
5675374 | Kohda | Oct 1997 | A |
5675810 | Sellers | Oct 1997 | A |
5768164 | Hollon | Jun 1998 | A |
5802305 | McKaughan | Sep 1998 | A |
5875345 | Naito et al. | Feb 1999 | A |
5959622 | Greer | Sep 1999 | A |
5999613 | Nabkel et al. | Dec 1999 | A |
6006285 | Jacobs | Dec 1999 | A |
6032256 | Bernard | Feb 2000 | A |
6052442 | Cooper et al. | Apr 2000 | A |
6101610 | Beebe | Aug 2000 | A |
6128744 | Wang | Oct 2000 | A |
6144363 | Alloul | Nov 2000 | A |
6144644 | Bajzath et al. | Nov 2000 | A |
6172703 | Lee | Jan 2001 | B1 |
6208373 | Fong et al. | Mar 2001 | B1 |
6215420 | Harrison et al. | Apr 2001 | B1 |
6237846 | Lowell | May 2001 | B1 |
6240168 | Stanford et al. | May 2001 | B1 |
6260111 | Craig et al. | Jul 2001 | B1 |
6266714 | Jacobs | Jul 2001 | B1 |
6279056 | Jacobs | Aug 2001 | B1 |
6282435 | Wagner et al. | Aug 2001 | B1 |
6346934 | Wugofski | Feb 2002 | B1 |
6362440 | Karidis | Mar 2002 | B1 |
6380968 | Alexander | Apr 2002 | B1 |
6417849 | Lefebvre | Jul 2002 | B2 |
6438585 | Mousseau | Aug 2002 | B2 |
6453027 | Kang | Sep 2002 | B1 |
6483905 | Kikinis | Nov 2002 | B1 |
6507356 | Jackel et al. | Jan 2003 | B1 |
6513128 | Wang | Jan 2003 | B1 |
6518957 | Lehtinen et al. | Feb 2003 | B1 |
6519335 | Bushnell | Feb 2003 | B1 |
6546262 | Freadman | Apr 2003 | B1 |
6603855 | Cannon et al. | Aug 2003 | B1 |
6628194 | Hellebust | Sep 2003 | B1 |
6628267 | Karidis | Sep 2003 | B2 |
6658095 | Yoakum | Dec 2003 | B1 |
6671356 | Lewis | Dec 2003 | B2 |
6671743 | Verity | Dec 2003 | B1 |
6680845 | Agata | Jan 2004 | B2 |
6691233 | Gannage | Feb 2004 | B1 |
6718183 | Blust | Apr 2004 | B1 |
6731316 | Herigstad et al. | May 2004 | B2 |
6741232 | Siedlikowski | May 2004 | B1 |
6757372 | Dunlap et al. | Jun 2004 | B1 |
6806867 | Arruda | Oct 2004 | B1 |
6819961 | Jacobs | Nov 2004 | B2 |
6831657 | Tsutsumi et al. | Dec 2004 | B2 |
6882326 | Hirayama | Apr 2005 | B2 |
6888562 | Rambo et al. | May 2005 | B2 |
6892074 | Tarkiainen | May 2005 | B2 |
6897851 | Carini | May 2005 | B2 |
6902332 | McLoone | Jun 2005 | B2 |
6912283 | Meyerson et al. | Jun 2005 | B2 |
6937950 | Cragun | Aug 2005 | B2 |
6938174 | LeKuch | Aug 2005 | B2 |
6970556 | Wall et al. | Nov 2005 | B2 |
6973167 | Kikinis | Dec 2005 | B2 |
6976216 | Peskin et al. | Dec 2005 | B1 |
6980641 | Stanford et al. | Dec 2005 | B1 |
6996445 | Kamijo | Feb 2006 | B1 |
7036110 | Jeyaraman | Apr 2006 | B2 |
7096391 | Johnson | Aug 2006 | B2 |
7123370 | Watanabe | Oct 2006 | B2 |
7221331 | Bear | May 2007 | B2 |
7231229 | Hawkins | Jun 2007 | B1 |
7240228 | Bear et al. | Jul 2007 | B2 |
7243130 | Horvitz | Jul 2007 | B2 |
7272660 | Powers | Sep 2007 | B1 |
7302637 | Maguire | Nov 2007 | B1 |
20010040551 | Yates et al. | Nov 2001 | A1 |
20020015020 | Mobin | Feb 2002 | A1 |
20020080967 | Abdo | Jun 2002 | A1 |
20020087225 | Howard | Jul 2002 | A1 |
20020126882 | Funahashi | Sep 2002 | A1 |
20020131072 | Jackson | Sep 2002 | A1 |
20020167458 | Baudisch | Nov 2002 | A1 |
20020167460 | Baudisch | Nov 2002 | A1 |
20030021290 | Jones | Jan 2003 | A1 |
20030025674 | Watanabe | Feb 2003 | A1 |
20030037180 | Madineni et al. | Feb 2003 | A1 |
20030069689 | Ihara | Apr 2003 | A1 |
20030074590 | Fogle et al. | Apr 2003 | A1 |
20030112325 | Boyden et al. | Jun 2003 | A1 |
20030122874 | Dieberger | Jul 2003 | A1 |
20030131148 | Kelley et al. | Jul 2003 | A1 |
20030146903 | Yi | Aug 2003 | A1 |
20030159044 | Doyle et al. | Aug 2003 | A1 |
20030188041 | Fillmore | Oct 2003 | A1 |
20030197685 | Yi | Oct 2003 | A1 |
20030227471 | Eglit | Dec 2003 | A1 |
20040114032 | Kakii | Jun 2004 | A1 |
20040135819 | Maa | Jul 2004 | A1 |
20040141012 | Tootill | Jul 2004 | A1 |
20040155956 | Libbey | Aug 2004 | A1 |
20040177361 | Bernhard et al. | Sep 2004 | A1 |
20040222977 | Bear | Nov 2004 | A1 |
20040222978 | Bear | Nov 2004 | A1 |
20040223058 | Richter | Nov 2004 | A1 |
20040223061 | Bear | Nov 2004 | A1 |
20040223599 | Bear | Nov 2004 | A1 |
20040225502 | Bear | Nov 2004 | A1 |
20040225892 | Bear | Nov 2004 | A1 |
20040225901 | Bear | Nov 2004 | A1 |
20040240167 | Ledbetter et al. | Dec 2004 | A1 |
20040240650 | Bear | Dec 2004 | A1 |
20050068423 | Bear | Mar 2005 | A1 |
20050069101 | Bear | Mar 2005 | A1 |
20050071437 | Bear | Mar 2005 | A1 |
20050071626 | Bear | Mar 2005 | A1 |
20050182822 | Daniel | Aug 2005 | A1 |
20050186942 | Griffin | Aug 2005 | A1 |
20050193396 | Stafford-Fraser | Sep 2005 | A1 |
20060007051 | Bear | Jan 2006 | A1 |
20060048062 | Adamson | Mar 2006 | A1 |
20060061516 | Campbell | Mar 2006 | A1 |
20060095525 | Mousseau | May 2006 | A1 |
20060130075 | Rhoten | Jun 2006 | A1 |
20060164324 | Polivy | Jul 2006 | A1 |
20060284787 | Bear | Dec 2006 | A1 |
Number | Date | Country |
---|---|---|
0772327 | May 1997 | EP |
0777394 | Jun 1997 | EP |
000816990 | Jan 1998 | EP |
0838934 | Apr 1998 | EP |
0772327 | Feb 1999 | EP |
WO9602049 | Jan 1996 | WO |
Number | Date | Country | |
---|---|---|---|
20040225892 A1 | Nov 2004 | US |