Mode-switching in ultra mobile devices

Arrangements for managing displays of ultra-mobile devices (UMD's). Automatically or manually, a small-mode interface on a UMD screen, wherein one application window is visible, is switched to a large-mode interface.

FIELD OF THE INVENTION

The present invention relates to ultra-mobile devices (UMD's) and their displays, and to arrangements for managing the displays.

BACKGROUND OF THE INVENTION

The terms “laptop”, “laptop computer”, “notebook” and “notebook computer”, as broadly employed herein, should be understood to be interchangeable with one another and to broadly relate to essentially any type of portable computer as commonly understood in connection with any or all of those four terms.

Ultra-mobile devices (UMD's) have proliferated in recent years and have taken on many forms. Generally they refer to any smaller, portable computing device that has a host of capabilities normally found in a desktop or laptop computer, such as (but by no means limited to): internet access, word processing, and image display and management. Indeed, UMD's often have at least as much computing power as a typical laptop.

Because of their smaller size, however, UMD's have tended to suffer from several user interface issues. In many cases, the user interface is a scaled-down version of a full-sized user interface (such as “WINDOWS EXPLORER”) and the small screen involved does not at all lend itself easily to the consumption or creation of data, or to general navigation and use. Also, UMD's tend to require an excess of gross motor movements when being navigated, especially in proportion to laptops and desktops; further, the motor movements involved are necessarily more intricate and exacting, and can often present great discomfort.

Another problem has been encountered in that UMD's enjoy only a relatively short battery life when compared to laptops. Given that UMD's are for many consumers replacing laptops, this deficiency has been seen to warrant improvement.

In view of the foregoing, a need has been recognized in connection with overcoming the shortcomings and disadvantages presented by known arrangements as discussed above.

SUMMARY OF THE INVENTION

In accordance with a preferred embodiment of the present invention, an implementation is made for switching between a large-mode interface (e.g. Windows Explorer) and a small-mode interface in a UMD. The switch between the two interfaces can be brought about automatically or manually.

In an advantageous refinement of the present invention, the aforementioned problem of short battery life can be mitigated by reducing power consumption while a small-mode interface is employed.

In summary, one aspect of the invention provides a method comprising: providing a UMD computer system, the UMD computer system comprising a screen; effecting a small-mode interface on the UMD computer system screen, wherein one application window is visible on the screen; effecting a second interface on the UMD computer system screen; switching between the small-mode interface and the second interface.

Another aspect of the invention provides a UMD computer system comprising: a CPU; a system memory in communication with the CPU; a screen; an arrangement for effecting a small-mode interface on the UMD computer system screen, wherein one application window is visible on the screen; an arrangement for effecting a second interface on the UMD computer system screen; and an arrangement for switching between the small-mode interface and the second interface.

Furthermore, an additional aspect of the invention provides a program storage device readable by machine, tangibly embodying a program of instructions executable by the machine to perform a method comprising: providing a UMD computer system, the UMD computer system comprising a screen; effecting a small-mode interface on the UMD computer system screen, wherein one application window is visible on the screen; effecting a second interface on the UMD computer system screen; switching between the small-mode interface and the second interface.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

Referring now toFIG. 1, there is depicted a block diagram of an illustrative embodiment of a computer system12. The illustrative embodiment depicted inFIG. 1may be a UMD system as broadly contemplated herein.

As shown inFIG. 1, computer system12includes at least one system processor42, which is coupled to a Read-Only Memory (ROM)40and a system memory46by a processor bus44. System processor42is a general-purpose processor that executes boot code41stored within ROM40at power-on and thereafter processes data under the control of operating system and application software stored in system memory46. System processor42is coupled via processor bus44and host bridge48to Peripheral Component Interconnect (PCI) local bus50.

PCI local bus50supports the attachment of a number of devices, including adapters and bridges. Among these devices is network adapter66, which interfaces computer system12to LAN10, and graphics adapter68, which interfaces computer system12to display (or monitor)69. Communication on PCI local bus50is governed by local PCI controller52, which is in turn coupled to non-volatile random access memory (NVRAM)56via memory bus54. Local PCI controller52can be coupled to additional buses and devices via a second host bridge60.

Computer system12further includes Industry Standard Architecture (ISA) bus62, which is coupled to PCI local bus50by ISA bridge64. Coupled to ISA bus62is an input/output (I/O) controller70, which controls communication between computer system12and attached peripheral devices such as a keyboard, mouse, and a disk drive. In addition, I/O controller70supports external communication by computer system12via serial and parallel ports. As known, docking connections enable the computer system12to be docked at a suitable docking station, which itself may provide expanded capabilities such as a large-screen monitor, a keyboard, a mouse and a disk drive.

Indeed, as shown schematically inFIG. 2, a UMD system112(which may include any or all of the aspects of system12shown inFIG. 1) in accordance with a preferred embodiment of the present invention may be configured to mate with a docking station180to take advantage of expanded capabilities.

As known, system112is powered by a rechargeable battery172. An actuator174, to be discussed in more detail herebelow, may be disposed at an external portion of the casing of UMD112. Finally, UMD112preferably includes suitable docking connectors172which will be well known to those of ordinary skill in the art.

For its part, docking station180is configured for physically receiving UMD system112and for functionally connecting therewith in a manner well known to those of ordinary skill in the art. With UMD system112docked in station180, a range of additional components may be availed such as: a large screen monitor182(which can supersede the smaller monitor of UMD system112); a keyboard184(in the absence of any on UMD system112itself) and a mouse186(also not normally present on UMD system112itself). Of course, a large screen monitor182need not necessarily be included in a docking station wherein the (smaller) screen of UMD system112itself might actually be employed when system112is docked.

Other components or capabilities which can be associated with docking station180, and which UMD system112may take advantage of when docked, include, but are by no means limited to: a disk drive188and a supplemental (e.g., AC) power source190.

In accordance with a preferred embodiment of the present invention, an implementation is made for switching between a large-mode interface (e.g. Windows® Explorer, or as may be employed in a large screen monitor182) and a small-mode interface (as may be inherent to UMD system112). Whereas the former interface is normally geared towards the use of a keyboard, mouse, and monitor (such as in a “docked” mode), the latter is much more manageable in the context of no keyboard, and a user who could potentially be moving around while using the device (such as in a “portable” mode, or when UMD system112is not docked at station180).

To elaborate, the large mode interface will preferably be embodied by a standard PC interface known to those of ordinary skill in the art. On the other hand, the small-mode interface could preferably be embodied by an interface similar to any one of several small-device interfaces, such as that found in any of the “NOKIA 770”, “WINDOWS MOBILE” or “PALM OS” systems. The common thread, it is to be understood, in accordance with a preferred embodiment of the present invention, is that the small-mode interface preferably opens only one application window at a time. As such, other applications can be minimized (i.e., “backgrounded”) or even terminated (i.e., “killed” or requested to stop completely) to manage memory consumption. (For its part, program termination need not necessarily take place very frequently; for instance, it could be reserved solely for those processes which only need to run occasionally or which could start themselves back up as needed.) Thus, whereas a large-mode interface is suitable for multitasking, the small-mode interface would be configured more particularly for single-tasking.

FIGS. 3 and 4illustrate fundamental differences between small-mode and large-mode interfaces. As shown inFIG. 3, a large-mode interface—here, a “WINDOWS XP” interface as often employed on conventional UMD's—can include many overlapping windows and menus when in use. Such an interface is often termed a “WIMP” (windows, icons, menus, pointing devices) interface and can be very unwieldy and awkward on the smaller screens of a UMD. As such, WIMP navigation tends to be better geared towards large screen monitors, and more processing power and screen space thus tends to be needed (or at least warranted) in connection with any desired multitasking.

In contrast,FIG. 4shows a small-mode interface as presently used in the “NOKIA 770”. Here, a single application interface is employed, with a more efficient and less crowded use of screen space, and consequently a need for less processing power. Navigation, for its part, is more appropriately suited for a small screen (such as a UMD screen) while easy access can be provided to common applications via icons on the sides of the screen (instead of employing multiple overlapping windows and menus simultaneously as inFIG. 3).

Returning toFIG. 2, there are broadly contemplated herein, in accordance with at least one presently preferred embodiment of the present invention, different mechanisms for affording a switch between a large-mode and a small-mode interface (wherein, preferably, a “small-mode” interface may be regarded as involving the use and appearance of solely one application at a time on the screen). In a first conceivable mechanism, the switch can be brought about automatically based on whether the UMD system12is docked or undocked or, at the very least, on whether a monitor is operatively associated with a larger screen monitor182. In the latter sense, it is conceivable that a larger screen monitor182could in some manner be connected to a UMD system112directly without the intermediary of a docking station180. Appropriate software or mechanical arrangements for detecting such connections are preferably operatively associated with a graphics adapter of a UMD system112to effect the switch into or out of either of the two interfaces. An automatic switch to large-mode interface can also be effected if a keyboard and/or mouse184/186are detected by the UMD, with a switch to small-mode interface made if one or more such components are not detected; again, such components could be detected in conjunction with a docking station180or in accordance with a direct interface of such components with a UMD system112.

On the other hand, a manual arrangement for effecting a switch between a large-mode and small-mode interface is broadly contemplated. For instance, a manual actuator174such as a button or switch, or even a touch screen field or the like, could be selectively actuated by a user to effect a switch from one mode to another.

In an advantageous refinement of the present invention, the problem of short UMD battery life discussed heretofore can be mitigated by reducing power consumption while a small-mode interface is employed; as such, devices and processes can be managed at such times as to reduce power consumption.

More particularly, in order to manage battery power, a UMD system112in accordance with a preferred embodiment of the present invention may employ any or all of the techniques now to be described.

In a first conceivable technique, power consumption of UMD system112could be dropped or reduced by using standard ACPI (Advanced Configuration and Power Interface; www.acpi.info) measures, such as Performance States PO-Pn (i.e., power states “P-zero” through “P-n”, or optional power states that allow device drivers to drop a device's power requirements. For instance, if a CD-ROM drive contains no CD, then clearly the drive has no immediate obligatory tasks to perform, whereupon the device driver could instruct it to “sleep”.)

In another technique, aggressive process management may be brought about. For UMD use, for instance, it can be appreciated that processes such as the following could easily be re-niced (dropped severely in schedule priority) or terminated completely by way of reducing power consumption: non-critical system processes (e.g., network servers and time daemons); and processes that do not have focus (i.e., are not receiving keyboard and/or mouse data at that moment.) Because of the fact that only one application will be in focus at any given time, this is an easy decision to make.

Finally, in another conceivable technique, the UMD screen backlight could be made optional by incorporating a transflective display to take advantage of outside light while in mobile (non-docked) mode.

A very wide variety of other power-saving techniques in the context of a UMD small-mode interface are of course conceivable and are not intended to be limited by the specific examples discussed hereinabove.

If not otherwise stated herein, it is to be assumed that all patents, patent applications, patent publications and other publications (including web-based publications) mentioned and cited herein are hereby fully incorporated by reference herein as if set forth in their entirety herein.