The present technique relates generally to computer systems and, more particularly, to display configuration systems. The present technique provides a system and method for automatically switching in real-time between multiple display profiles in response to a system event, such as a dock/undock event.
This section is intended to introduce the reader to various aspects of art which may be related to various aspects of the present invention which are described and/or claimed below. This discussion is believed to be helpful in providing the reader with background information to facilitate a better understanding of the various aspects of the present invention. Accordingly, it should be understood that these statements are to be read in this light, and not as admissions of prior art.
Computer systems and other electronics often have monitors or displays, which have a fixed viewing orientation. For example, conventional monitors mount on a desktop in a landscape orientation. The bulk of these monitors generally precludes rotation of the monitor between multiple viewing orientations. In contrast, flat-panel displays and portable electronics having flat-panel displays may be rotated between multiple viewing orientations, such as the conventional landscape orientation and a portrait orientation (i.e., a 90 degree rotation of the display). After physically rotating the display, the user must manually change the viewing orientation of the display by interacting with software on the electronic/computing device coupled to the display. For example, the manual change in viewing orientations may be executed by Nview, which is a software application provided by Nvidia Corporation of Santa Clara, Calif.
Exemplary embodiments will hereafter be described with reference to the accompanying drawings, wherein life reference numerals denote like elements, and:
One or more specific embodiments of the present invention will be described below. In an effort to provide a concise description of these embodiments, not all features of an actual implementation are described in the specification. It should be appreciated that in the development of any such actual implementation, as in any engineering or design project, numerous implementation-specific decisions must be made to achieve the developers' specific goals, such as compliance with system-related and business-related constraints, which may vary from one implementation to another. Moreover, it should be appreciated that such a development effort might be complex and time consuming, but would nevertheless be a routine undertaking of design, fabrication, and manufacture for those of ordinary skill having the benefit of this disclosure.
The present technique provides a system and method for responding to system event, such as a hardware reconfiguration, in real-time to reconfigure a computer system automatically in response to the system event. For example, the present technique may detect an installation, removal, connection, disconnection, or reconfiguration of a hardware component during operation of the computer system. Based on the detected event, the present technique identifies the hardware configuration of the computer system and automatically reconfigures the computer system to accommodate the hardware configuration in real-time. The system event may be a physical rotation of a display between landscape and portrait orientations or between viewing and writing orientations. The system event also may be a physical docking or undocking of a first computing device with a second device in a variety of mounting positions. The present technique is responsive to the system event in real-time, providing a real-time adaptation of the computer system to the new system configuration.
In an exemplary embodiment, the present technique provides a plurality of viewing/display profiles for various different configurations of the computer system. Each viewing/display profile may have a variety of viewing/display settings, such as color depth, display resolution, screen orientation, primary or secondary screens of multi-display system, background image, color scheme and layout for applications, user settings, active applications, and various other settings. If an event is detected at boot-up or during operation of the computer system, then the appropriate viewing/display profile is used to reconfigure or reinitialize the system to adapt to the new system configuration. Advantageously, the present technique may perform the reconfiguration in real-time to provide automatic adaptation to the new system configuration. For example, the operating system may originally configure the hardware and software resources in a default profile, which may be subsequently reconfigured or switched with another profile during operation of the computer system in response to the system event.
As illustrated, the tablet computing device 12 has a housing 20, which has a display screen assembly 22 disposed in a top side 24 of the housing 20, a plurality of computing components and circuitry disposed within the housing 20, and the multi-attachable keyboard 14 removably coupled to a bottom side 26 of the housing 20. The display screen assembly 22 may comprise any suitable flat panel display screen technology, including a variety of screen enhancement, antireflective, protective, and other layers. The display screen assembly 22 also may have touch panel technology, digitizer panel technology, and/or various other user-interactive screen technologies. As discussed in detail below, the digitizing pointing device 16 interacts with a digitizing panel 136 (e.g., see
The computing components disposed within the tablet style housing 20 may comprise a processor, a motherboard, volatile and nonvolatile memory (e.g., a hard drive, RAM, ROM, flash memory, cache memory, etc.), network circuitry (e.g., a modem, a network card, etc.), wireless communications circuitry (e.g., IR, RF, optical, blue tooth, and other technologies), input/output ports, audio/video circuitry, and various other circuitry, components, and component receptacles/bays. For example, the tablet computing device 12 and the multi-attachable keyboard 14, may comprise wireless communications circuitry, such as RF circuitry, such that the tablet computing device 12 may be used for wireless interaction with a wireless LAN or any other desired wireless input/output device remote from the tablet computing device 12. Moreover, the tablet computing system 10 may comprise a wireless microphone or wireless voice recognition headset to facilitate wireless user-interaction.
The multi-attachable keyboard 14 is attachable/detachable to the tablet computing device 12 in a variety of operable and storage locations, such as the storage location illustrated by
The tablet computing device 12 and the multi-attachable keyboard 14 may be jointly or separately attachable to the multi-configurable docking assembly 18 at a support section 28, which is movably coupled to a base section 30. As described below, the support section 28 may be movable to a variety of angles, elevations, and orientations to enhance the user's interaction with the tablet computing device 12. For example, the support section 28 may be rotatable between portrait and landscape orientations and between horizontal and upright orientations. The tablet computer system 10 also may comprise a screen orientation switching mechanism, which may operate automatically or manually to switch the display orientation of the display screen assembly 22 between portrait and landscape orientations. Accordingly, as discussed in further detail below, the multi-configurable docking assembly 18 may trigger an automatic change in the viewing orientation upon moving the support section 28 between the portrait and landscape orientations, while the tablet computing device 12 is disposed in the docked configuration. This automatic switching mechanism reduces the user's tasks and ensures that text/images are always displayed in an upright/readable orientation for the user regardless of the physical orientation of the tablet computing device 12.
The tablet computing device 12 is further illustrated with reference to
As mentioned above, the tablet computing device 12 is configured for a stand-alone or a docked configuration in a plurality of orientations, such as portrait and landscape orientations in various angles relative to a support surface. For example, the computing device 12 may comprise a plurality of feet to mount the tablet computing device 12 onto a desired surface, such as a desktop, a wall, a user's lap, or any other support surface. In this exemplary embodiment, the tablet computing device 12 includes rubber feel 48 and 50 and adjustable feet 52 and 54, which may comprise any suitable height adjustment and locking mechanism (e.g., a flip-up mechanism with a slot-tab securement structure). For a docked configuration, the tablet computing device 12 comprises a docking connector 56 and a docking latch structure 58, which are intercoupleable with mating connector and latch structures on the multi-configurable docking assembly 18. As noted above, the tablet computing device 12 also may comprise one or more mounting alignment structures, such as docking alignment slots 60 and 62, which are intercoupleable in a single alignment orientation with mating alignment structures on the multi-configurable docking assembly 18. Similarly, alignment structures 64 and 66 may be disposed on the bottom side 26 of the tablet computing device 12 to align the keyboard 14, or other face-mountable devices, in a proper mount orientation with the tablet computing device 12. Moreover, the keyboard 14 or other face-mountable devices may be removably intercoupled with the bottom side 26 via the docking latch structure 58 or an edge-based latch mechanism.
One or more input/output ports also may be provided on the tablet computing device 12 to facilitate data exchange and communication with external devices or networks. For example, the tablet computing device 12 may have a communications port 78 in an accessible position relative to the external device mount structures 68 and 70. Accordingly, an external device mounted to the tablet computing device 12 is able to communicate with the tablet computing device 12 via the communications port 78, which may comprise any suitable port. For example, the port 78 may be a serial port, a parallel port, a USB port, a wireless port, an optical port, or any other desired port. The port 78 also may comprise hot-plugging technology to facilitate attachment and detachment during operation of the tablet computing device 12.
Security features also may be provided on various components of the tablet computer system 10. The system 10 may have one or more Kensington locks or other physical securement mechanisms for physically securing the various components to a desired fixture. For example, each of the components illustrated by
As illustrated by
The tablet computing device 12 also may have one or more communications port panels, which may be exposed or concealable by a removable port panel cover. For example, as illustrated by
As illustrated by
Power control and management features also may be provided in the tablet computing device 12. As illustrated by
As mentioned above, a user may interact with the tablet computing device 12 without a conventional keyboard or mouse. As illustrated by
In this exemplary embodiment, one of the functional buttons 110-116 triggers a personal information manager, while another one of the functional buttons 110-116 triggers a quick utilities menu. The personal information manager may comprise a variety of user information and user settings, such as a personal calendar, a phone/address book, an e-mail system and log, a phone system and log, user configuration settings, a user document folder, a personal diary, and any other default or user-selected personal information. The quick utilities menu (i.e., “Q” Utilities) provides access to a variety of sort ware and hardware settings in a quick, or short, menu-based format. Accordingly, the quick utilities menu may list hardware and software items, such as wireless functionality, video output, volume control, mute control, brightness control, contrast control, display orientation functionality (e.g., option to switch between portrait and landscape orientations), power properties, quick menu properties, properties of the tablet computing device 12, properties of the keyboard 14, properties of the digitizing pointing device 16, properties of the docking assembly 18, and a variety of functional buttons, such as PrintScreen, Alt+PrintScreen, and Clt+Alt+Del. The foregoing personal information manager and quick utilities menu also may be triggered by an icon displayed on the display screen assembly 22, by one of the digitizer buttons described below, by a button on the digitizing pointing device 16, by a button on the keyboard 14, by wireless control, by voice commands, or by any other suitable user interaction mechanism.
As illustrated by
The digitizing pointing device 16 interacts with the digitizer panel 132 throughout the dimensions of the display screen assembly 22 for coordination, selection, writing, and other user-interaction with software displayed on the display screen assembly 22. The digitizer panel 136 and the digitizing pointing device 16 may comprise any suitable digitizer technology, such as electric field, ultrasonic, radio frequency, infrared, electrostatic, electromagnetic, or any other existing or emerging technologies. The digitizer panel 136 and the digitizing pointing device 16 may operate by one-way or two-way signal transmissions, in either direction, between the digitizer panel 136 and the digitizing pointing device 16. In this exemplary embodiment, the digitizing pointing device 16 may transmit a wireless signal, which is sensed by the digitizer panel 136 to coordinate the location of the digitizing pointing device 16. The digitizing pointing device 16 also may transmit one or more secondary signals to trigger a select function or any other desired function. For example, a click of the tip 132 or the button 134 may transmit a secondary signal, which triggers a desired function. Alternatively, the present technique may use touch screen technology, which would facilitate user interaction via a standard pen, a finger, or any suitable pointing item.
The digitizer-activated buttons 126, 128, and 130 are provided in a peripheral region 138 of the digitizer panel 136, which has active button regions 140, 142, 144 defined for each of the buttons 126, 128, and 130, respectively. Each of these active button regions 140, 142, and 144 is associated with a desired hardware/software function, such as a default or user-defined function. The digitizer-activated buttons 126, 128, and 130 also may comprise indicators, such as LEDs 146, 148, and 150, which may be illuminated upon triggering or close proximity of the digitizing pointing device 16. For example, one of the LEDs 146-150 may light up when the tip 132 of the digitizing pointing device 16 is near a desired one of the active button regions 140-144, such that a subsequent triggering event will activate the desired button. The digitizer panel 136 and the indicators 146-150 communicate with a motherboard 152 of the tablet computing device 12 via connectors 154 and 156, respectively.
In operation, the digitizing pointing device 16 may trigger one of the digitizer-activated buttons 126, 128, and 130 by touching the top side 24 of the housing 20 above the desired active button region. Again, the indicators 146-150 may light up when the digitizing pointing device is close enough to activate the desired button. Alternatively, the desired active button region may be selected by engaging a switch mechanism in the tip 132 of the digitizing pointing device 16 (e.g., by tapping the tip 132), while the tip 132 is disposed above the desired active button region. The desired active button region also may be triggered by depressing a button, such as button 134, on the digitizing pointing device 16. The digitizing pointing device 16 also may have a separate button for each of the digitizer activated buttons 126, 128, and 130, such that the desired button may be activated remotely simply by depressing the appropriate button on the pointing device 16. Any other suitable triggering mechanism is also within the scope of the present technique.
As described above, the functional components of the digitizer-activated buttons 126, 128, and 130 are disposed within the housing 20, such that the triggering mechanism is entirely remote from such functional components. As such, the digitizer-activated buttons 126, 128, and 130 are more durable than conventional buttons, which require physical contact directly on the buttons. Moreover, the digitizer-activated buttons 126, 128, and 130 are not subject to accidental activation by a user, such as with conventional physical buttons or touch panel buttons.
In this exemplary embodiment, the digitizing pointing device 16 generates a signal that is received and processed by the digitizer panel 136. For example, the digitizing pointing device 16 may be a digitizer pen produced by FinePoint Innovations, Inc. of Tempo, Ariz. In operation, the signal transmitted from the digitizing pointing device 16 identifies the location of the tip 132 relative to the display screen assembly 22 (and subsurface digitizer panel 136), thereby facilitating pointer movement and drawing functions on the display screen. The digitizing pointing device 16 also may be used to select items, to interact with system software, to activate virtual buttons on the screen, to activate digitizer buttons, or to perform a variety of other functions. For example, one or more special signals may be transmitted from the digitizing pointing device 16 upon activating the switch 176 or the spring-loaded switch 178. Although the illustrated digitizing pointing device 16 is described as a signal-generating digitizer device, any suitable pen and panel digitizer system is within the scope of the present technique. For example, the signal may arise in the digitizer panel 136 rather than the digitizing pointing device 16. The present technique also may use touch screen technology and provide the digitizing pointing device 16 as a “dumb” pointing device.
As illustrated by
In response to a dock/undock event or a physical rotation of the tablet computing device 12, the present technique may initiate a real-time automatic change of the display, viewing, and operational configuration of the computer system 200. For example, the present technique may change display settings, application settings, and a variety of other system settings for the display screen 22 and/or the video display 204. The computer system 200 may detect the dock/undock event or the physical rotation by any suitable hardware or software detection mechanism. For example, the operating system may monitor the connection state of a docking connector between the tablet computing device 12 and the multi-positionable docking station 202. In one exemplary embodiment, a hardware signal may be checked by BIOS to determine the viewing orientation (i.e., portrait or landscape), the user interaction orientation (i.e., viewing or writing mode), and the docking state of the tablet computing device 12. One or more sensors also may be placed on various surfaces of the tablet computing device 12 and the multi-positionable docking station 202 to sense a particular orientation on the work surface 208. Alternatively, one or more switches may be placed on various surfaces of the tablet computing device 12 and the multi-positionable docking station 202 to initiate a configuration change or profile switch upon placing the tablet computing device 12 on the work surface 208 in a particular orientation.
After detecting a hardware event such as a hardware detection signal/interrupt at block 302, the process 300 evaluates whether the hardware event is a profile change triggering event (block 304). If the particular hardware event is not one of the default or custom triggering events at query block 306, then the process 300 continues to monitor for another hardware event at block 302. If the hardware event is one of the default or custom triggering events at query block 306, then the process 300 proceeds to compare the hardware event against a previous hardware state of the computer system (block 308). At query block 310, the process 300 analyzes whether the profile change is desired based on previous and existing hardware states of the computer system 200. If a profile change is not warranted by the hardware event, then the process 300 continues to monitor for another hardware event at block 302. If a profile change is warranted by the hardware event, then the process 300 proceeds to identify the desired profile based on the current hardware state of the computer system (block 312). The process 300 then automatically reconfigures the operational configuration of the computer system to the desired profile (block 314). Each profile may have a variety of system settings, application settings, display settings, and various other configuration settings. Moreover, each profile may have a number of active applications that are displayed in one or more of the various displays.
The automatic reconfiguration process 300 described above with reference to
The triggering events may occur if the system is in an S0 ACP1 state, if the system is in an S3 or lower state when the hardware event occurs, then the event may be queued for a subsequent profile change when the system is returned to the S0 state. The present technique may prevent undesirable profile changes by saving a previous state before proceeding into the S3 state and the queued state. Upon returning the system into the S0 state, the process 300 evaluates the saved previous state against the returning state. If the states are the same, then the process 300 does not execute a profile change.
The process 400 then analyzes whether the dock/undock event triggers a display profile change of the computer system (block 410). If the particular dock/undock event does not warrant a display profile change at query block 412, then the process 400 continues to monitor for another dock/undock event at block 402. If the dock/undock event is a triggering event for a display profile change, then the process 400 proceeds to identify the desired display profile based on the dock/undock state of the computer system (block 414). The process 400 then automatically reconfigures the display properties/orientation of the computer system to the desired profile (block 416). Each profile may have a variety of system settings, application settings, display settings, and various other settings. Moreover, each profile may have a number of active applications that are displayed in one or more of the various displays.
If the user docks the portable device in an upright position with the stationary device at block 516, then the process 500 detects the upright docked reconfiguration via one or more sensors, switches, or other hardware/software detection mechanisms. The process 500 then proceeds to analyze whether the computer system has multiple displays (block 518). If the computer system does not have multiple displays, then the process 500 proceeds to set the display profile of the computer system as having no display at the stationary device and as having the portable device as the primary display (block 508). If the computer system does have multiple displays, then the process 500 proceeds to set the display profile of the computer system as having the stationary device as the primary display and as having the portable device as the companion display (block 520). As discussed in further detail below with reference to
After setting the display profile at block 508 or block 520, the process 500 proceeds to identify the physical orientation of the portable device at query block 510. If the user has repositioned the portable device in a landscape orientation, then the process 500 detects the landscape reconfiguration via one or more sensors, switches, or other hardware/software detection mechanisms. The process 500 then automatically orients the display view of the portable device in a landscape viewing orientation in real-time (block 512). If the user has repositioned the portable device in a portrait orientation, then the process 500 detects the portrait reconfiguration via one or more sensors, switches, or other hardware/software detection mechanisms. The process 500 then automatically orients the display view of the portable device in a portrait viewing orientation in real-time (block 514). The process 500 also may perform a variety of other automatic system configuration operations in response to the upright dock event 516.
If the user docks the portable device in an inking/writing position with the stationary device at block 522, then the process 500 detects the inking/writing docked reconfiguration via one or more sensors, switches, or other hardware/software detection mechanisms. The process 500 then proceeds to analyze whether the computer system has multiple displays (block 524). If the computer system does not have multiple displays, then the process 500 proceeds to set the display profile of the computer system as having no display at the stationary device and as having the portable device as the primary display (block 508). If the computer system does have multiple displays, then the process 500 proceeds to set the display profile of the computer system as having the stationary device as the primary display and as having the portable device as the inking/writing display (block 526). As discussed in further detail below with reference to
After setting the display profile at block 508 or block 526, the process 500 proceeds to identify the physical orientation of the portable device at query block 510. If the user has repositioned the portable device in a landscape orientation, then the process 500 detects the landscape reconfiguration via one or more sensors, switches, or other hardware/software detection mechanisms. The process 500 then automatically orients the display view of the portable device in a landscape viewing orientation in real-time (block 512). If the user has repositioned the portable device in a portrait orientation, then the process 500 detects the portrait reconfiguration via one or more sensors, switches, or other hardware/software detection mechanisms. The process 500 then automatically orients the display view of the portable device in a portrait viewing orientation in real-time (block 514). The process 500 also may perform a variety of other automatic system configuration operations in response to the inking/writing dock event 522.
Any suitable software or hardware may be implemented to perform the foregoing automatic profile changes, as discussed with reference to
For each profile listed in each of the drop-down menus 602, 604, and 606, the user can edit a variety of display settings, application settings, and various other system settings for each video display in the computer system.
As illustrated, the interface 700 has buttons 708 and 710 to launch one or more custom or existing hardware configuration utilities for configuring display settings and for configuring applications of the computer system, respectively. The interface 700 also may have buttons 712, 714, 716, 718, and 720 for editing a resolution setting 722, a color depth setting 724, a screen orientation 726 (e.g., a portrait or landscape view), a screen background 728, and a screen appearance/theme 730, respectively. Accordingly, the user may edit individual display settings via buttons 712-720 rather than through the general utility launched by button 708. The interface 700 also may provide buttons or options for any other desired display settings.
The interface 700 also may have buttons 732, 734, and 736 for editing application shortcuts 738, for setting active applications 740, and for editing user interaction settings 742, respectively. The user may set up application short cuts, active applications, and various user input devices (e.g., a keyboard, a mouse, the digitizing pointing device 16, etc.) for each display of the computer system 12 in a particular docked or undocked configuration. For example, in an inking/writing position, the active application for the tablet computing device 12 may be an email program, a word processing program, a writing program using the digitizer pointing device 16, a personal information manager, or a variety of other software applications. If the user accepts the existing and/or changed settings to the system profile 702, then the user may click on an OK Button 744. Otherwise, the user may cancel the configuration operation by clicking on a Cancel Button 746. The interface 700 also may provide buttons or options for any other desired application settings.
One or both of the portable device 802 and the docking device 804 also may have variety of components to facilitate the automatic profile switching process described above with reference to
The display settings 902 may comprise any configuration parameters affecting the images and text displayed on a display screen of the device 900. The application settings 904 may comprise any configuration parameters affecting the operation of a particular application, the screen placement of the application, the launching of the application, or any other operational parameters. The device settings 906 relate to various device-specific configuration parameters, applications, and operational characteristics for the device 900. The position settings 908 relate to landscape versus portrait orientations of the display, viewing versus writing orientations of the display, active applications in each of the orientations, and various other positional settings of a display screen of the device 900.
The hardware event detector 918 may comprise a variety of hardware and software modules, which actively or passively monitor or detect hardware changes that may warrant a configuration change of the device 900 or other components in the system 800. The hardware event handler 920 may comprise signaling modules, communication modules, addressing modules, and various other handling mechanisms to receive and notify the system of a particular hardware event. The hardware event analyzer 922 may comprise comparison modules and various other processing modules to determine whether the particular hardware event is a triggering event for a profile change. The system state identifier 924 may comprise a variety of hardware and software mechanisms that identify a pre-existing or current operational and/or physical orientation state of the system and its various devices.
The automatic profile switcher 926 may comprise a variety of programming routines, visual interfaces, and links to other hardware and software to facilitate an automatic reconfiguration of the system and its devices in response to a hardware event. For example, the automatic profile switcher 926 may have links to the profile editor 928, the hardware configuration utilities 930, the device/system profiles 936, and the profile switching trigger events 938. The profile editor 928 may comprise any suitable interface for creating and modifying configuration profiles as discussed with reference to
While the invention may be susceptible to various modifications and alternative forms, specific embodiments have been shown by way of example in the drawings and will be described in detail herein. However, it should be understood that the invention is not intended to be limited to the particular forms disclosed. Rather, the invention is to cover all modifications, equivalents and alternatives falling within the spirit and scope of the invention as defined by the following appended claims. The present technique is applicable to a wide variety of computer systems and connectable electronic devices, which may benefit from having different profile settings for the various configurations. Moreover, the present technique may use any suitable triggering mechanism for an automatic profile change. The various profiles may comprise display settings, hardware settings, software settings, and various other operational settings for the device(s).
This application is a divisional application of U.S. patent application Ser. No. 10/214,818 filed Aug. 8, 2002 now U.S. Pat. No. 7,952,569.
Number | Name | Date | Kind |
---|---|---|---|
4542377 | Hagen et al. | Sep 1985 | A |
4831368 | Masimo et al. | May 1989 | A |
5134390 | Kishimoto et al. | Jul 1992 | A |
5173940 | Lantz et al. | Dec 1992 | A |
D343168 | Morisaki et al. | Jan 1994 | S |
5329289 | Sakamoto et al. | Jul 1994 | A |
5337212 | Bartlett et al. | Aug 1994 | A |
5436792 | Leman et al. | Jul 1995 | A |
5535093 | Noguchi et al. | Jul 1996 | A |
5537531 | Suga et al. | Jul 1996 | A |
5596697 | Foster et al. | Jan 1997 | A |
5640176 | Mundt et al. | Jun 1997 | A |
5682529 | Hendry et al. | Oct 1997 | A |
5708458 | Vrbanac | Jan 1998 | A |
5708561 | Huilgol et al. | Jan 1998 | A |
5774233 | Sakamoto | Jun 1998 | A |
5790120 | Lozares et al. | Aug 1998 | A |
5841424 | Kikinis | Nov 1998 | A |
5845282 | Alley et al. | Dec 1998 | A |
5859628 | Ross et al. | Jan 1999 | A |
5889964 | Cho et al. | Mar 1999 | A |
5899421 | Silverman | May 1999 | A |
5903254 | Mundt et al. | May 1999 | A |
5923528 | Lee | Jul 1999 | A |
5941493 | Cheng | Aug 1999 | A |
5973664 | Badger et al. | Oct 1999 | A |
5991897 | Perugini et al. | Nov 1999 | A |
5995139 | Lee | Nov 1999 | A |
6061104 | Evanicky et al. | May 2000 | A |
6125449 | Taylor et al. | Sep 2000 | A |
6137468 | Martinez et al. | Oct 2000 | A |
6157958 | Armitage et al. | Dec 2000 | A |
6189842 | Bergeron Gull et al. | Feb 2001 | B1 |
6189850 | Liao et al. | Feb 2001 | B1 |
6208996 | Ben-Shachar et al. | Mar 2001 | B1 |
6209088 | Reneris | Mar 2001 | B1 |
6268845 | Pariza et al. | Jul 2001 | B1 |
6275932 | Yamaguchi et al. | Aug 2001 | B1 |
6289466 | Bayramoglu et al. | Sep 2001 | B1 |
6301101 | Anzai et al. | Oct 2001 | B1 |
6326978 | Robbins | Dec 2001 | B1 |
6331867 | Eberhard et al. | Dec 2001 | B1 |
6336142 | Kato et al. | Jan 2002 | B1 |
6343006 | Moscovitch et al. | Jan 2002 | B1 |
6366450 | Janicek | Apr 2002 | B1 |
6385668 | Gaddess et al. | May 2002 | B1 |
6418010 | Sawyer | Jul 2002 | B1 |
6426872 | Sutton et al. | Jul 2002 | B1 |
6437975 | Huang | Aug 2002 | B1 |
6443408 | Hung | Sep 2002 | B1 |
6477588 | Yerazunis et al. | Nov 2002 | B1 |
D469091 | Hasegawa et al. | Jan 2003 | S |
6504710 | Sutton et al. | Jan 2003 | B2 |
6522529 | Huilgol et al. | Feb 2003 | B1 |
6523125 | Kohno et al. | Feb 2003 | B1 |
6567101 | Thomas | May 2003 | B1 |
6583984 | Yin et al. | Jun 2003 | B2 |
6633976 | Stevens | Oct 2003 | B1 |
6639788 | Liao et al. | Oct 2003 | B1 |
6691187 | Schwerin | Feb 2004 | B1 |
6727830 | Lui et al. | Apr 2004 | B2 |
6763458 | Watanabe et al. | Jul 2004 | B1 |
6771494 | Shimano | Aug 2004 | B2 |
6781604 | Poynter | Aug 2004 | B2 |
6788527 | Doczy et al. | Sep 2004 | B2 |
6795966 | Lim et al. | Sep 2004 | B1 |
6856506 | Doherty et al. | Feb 2005 | B2 |
6874744 | Rawlings et al. | Apr 2005 | B2 |
6888532 | Wong et al. | May 2005 | B2 |
6895515 | Yamazaki | May 2005 | B1 |
7025274 | Solomon et al. | Apr 2006 | B2 |
7089487 | Tsai | Aug 2006 | B2 |
7209124 | Hunt et al. | Apr 2007 | B2 |
7542052 | Solomon et al. | Jun 2009 | B2 |
20010011302 | Son | Aug 2001 | A1 |
20010025289 | Jenkins et al. | Sep 2001 | A1 |
20020024499 | Karidis et al. | Feb 2002 | A1 |
20020068558 | Janik | Jun 2002 | A1 |
20020130836 | Ohmori et al. | Sep 2002 | A1 |
20020135977 | Yin et al. | Sep 2002 | A1 |
20020184395 | LeFevre et al. | Dec 2002 | A1 |
20030122882 | Kho | Jul 2003 | A1 |
20030162152 | Lee | Aug 2003 | A1 |
20030222848 | Solomon et al. | Dec 2003 | A1 |
20030234797 | Williams et al. | Dec 2003 | A1 |
20030236935 | Amemiya et al. | Dec 2003 | A1 |
20030236971 | Rothman et al. | Dec 2003 | A1 |
20040017652 | Billington et al. | Jan 2004 | A1 |
20040021678 | Ullah et al. | Feb 2004 | A1 |
20040047505 | Ghassabian | Mar 2004 | A1 |
20040051726 | Martyn | Mar 2004 | A1 |
Entry |
---|
One-Click Mobility Client Overview, Mar. 8, 2002, 2002—Pocket Presence AB, pp. 11. |
Compaq, Aero 1500/2100 Pocket PC Reference Guide, Mar. 2000, pp. 41. |
Document Reference Citation: JP Patent Abstract 2001041690; Japan Servo Co Ltd; 2. |
Document Reference Citation: JP Patent Abstract 62248845; Seiko; 2. |
Number | Date | Country | |
---|---|---|---|
20090187677 A1 | Jul 2009 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 10214818 | Aug 2002 | US |
Child | 12356655 | US |