A method for a multi-modal device for transferring launch information for a panel and first docking bar in a first application environment to a second application environment for a second docking bar in the second application environment includes detecting a docking of the multi-modal device to a hardware module, and displaying a user interface for the second application environment operating on the multi-modal device on the hardware module. The method includes receiving at the second application environment the launch information for launching launchable objects in the first application environment from the second application environment, and parsing, by the second application environment, the launch information to determine a change to the panel or the first docking bar. The change is in the first application environment. The method includes changing the second docking bar to include the change to the panel or the first docking bar based on parsing the launch information.
|
1. A method operable on a multi-modal device for
transferring launch-configuration information for a set of panels and a first docking bar in a first application environment to a second application environment for a second docking bar in the second application environment, the method comprising:
detecting a docking of the multi-modal device to a hardware module;
displaying, in response to the docking, a user interface for the second application environment operating on the multi-modal device on the hardware module;
receiving, in response to the docking, at the second application environment the launch-configuration information for launching launchable objects in the first application environment from the second application environment on the multi-modal device;
parsing, by the second application environment operating on the multi-modal device docked to the hardware module, the launch-configuration information to determine a change to the set of panels or the first docking bar, wherein the change is in the first application environment operating on the hardware module;
changing the second docking bar to include the change to the set of panels or the first docking bar based on parsing the launch-configuration information;
sending, by the second application environment, a request for the launch-configuration information to the first application environment, wherein the launch-configuration information is received in response to the request; and
subsequent to receiving the launch-configuration information at the second application environment, listening, by the second application environment, for an issued communication from the first application environment for new launch-configuration information that is not synchronized between the first and the second application environments.
9. A non-transitory computer-readable storage medium comprising instructions for transferring launch-configuration information for a set of panels and a first docking bar in a first application environment to a second application environment for a second docking bar in the second application environment, the instructions for configuring a multi-modal device to be operable to:
detect a docking of the multi-modal device to a hardware module;
display, in response to the docking, a user interface for the second application environment operating on the multi-modal device on the hardware module;
receive, in response to the docking, at the second application environment the launch-configuration information for launching launchable objects in the first application environment from the second application environment on the multi-modal device;
parse, by the second application environment operating on the multi-modal device docked to the hardware module, the launch-configuration information to determine a change to the set of panels or the first docking bar, wherein the change is in the first application environment operating on the hardware module;
change the second docking bar to include the change to the set of panels or the first docking bar based on parsing the launch-configuration information;
send, by the second application environment, a request for the launch-configuration information to the first application environment, wherein the launch-configuration information is received in response to the request; and
subsequent to receiving the launch-configuration information at the second application environment, listen, by the second application environment, for an issued communication from the first application environment for new launch-configuration information that is not synchronized between the first and the second application environments.
17. A multi-modal device configured for transferring launch-configuration information for a set of panels and a first docking bar in a first application environment to a second application environment for a second docking bar in the second application environment, the multi-modal device comprising:
a processor for operating the first application environment and the second application environment; and
a computer-readable storage medium comprises instructions for configuring the processors to be operable to:
detect a docking of the multi-modal device to a hardware module;
display, in response to the docking, a user interface for the second application environment operating on the multi-modal device on the hardware module;
receive, in response to the docking, at the second application environment the launch-configuration information for launching launchable objects in the first application environment from the second application environment on the multi-modal device;
parse, by the second application environment operating on the multi-modal device docked to the hardware module, the launch-configuration information to determine a change to the set of panels or the first docking bar, wherein the change is in the first application environment operating on the hardware module;
change the second docking bar to include the change to the set of panels or the first docking bar based on parsing the launch-configuration information;
send, by the second application environment, a request for the launch-configuration information to the first application environment, wherein the launch-configuration information is received in response to the request; and
subsequent to receiving the launch-configuration information at the second application environment, listen, by the second application environment, for an issued communication from the first application environment for new launch-configuration information that is not synchronized between the first and the second application environments.
2. The method of
3. The method of
4. The method of
5. The method of
6. The method of
7. The method of
8. The method of
10. The non-transitory computer-readable storage medium of
11. The non-transitory computer-readable storage medium of
12. The non-transitory computer-readable storage medium of
13. The non-transitory computer-readable storage medium of
14. The non-transitory computer-readable storage medium of
15. The non-transitory computer-readable storage medium of
16. The non-transitory computer-readable storage medium of
18. The multi-modal device of
19. The multi-modal device of
|
|||||||||||||||||||||||
Particular embodiments generally relate to managing applications that operate on a multi-modal device.
Multi-modal devices, such as mobile communication devices, personal digital assistants (PDAs), etc., have relatively powerful computing capability for operating a variety of launchable objects, such as applications, bookmarks, etc. Further, multi-modal devices also have relatively large memories that can store a relatively large number of launchable objects. With the current number of launchable objects that a multi-modal device can store and operate, managing the launchable objects has become a burden for users.
Managing launchable objects on a multi-modal device may include loading the launchable objects onto the multi-modal device, loading updates for the launchable objects, creating favorites lists for the launchable objects, moving launcher object (e.g., icons for launching launchable objects) for launchable objects to selected panels, a docking bar, etc. Multi-modal devices provide tools for managing launchable objects. However, the tools provided by a multi-modal device for managing a launchable object typically require that a user provide numerous inputs to the multi-modal device to manage the launchable object. For example, a user interacting with a touch screen of a multi-modal device may be required to make several gestures (e.g., taps, swipes, etc.) on the touch screen to locate a launcher object for a launchable object and select the launcher object for launching the launchable object. For example, several panels on a multi-modal device may need to be traversed to locate a launcher object, or several menus and sub-menus may need to be traversed to locate the launcher object. Some docking systems for docking a multi-modal device to a hardware module provide for some simplification in managing launchable objects. However, these docking systems still require some user management of the launchable objects to achieve a simplified user interface on the hardware module.
Described herein are techniques for managing launchable objects, such as applications, bookmarks, etc., on multi-modal devices. In the following description, for purposes of explanation, numerous examples and specific details are set forth in order to provide a thorough understanding of embodiments of the present invention. Particular embodiments as defined by the claims may include some or all of the features in these examples alone or in combination with other features described below, and may further include modifications and equivalents of the features and concepts described herein.
According to one embodiment, a method operable on a multi-modal device for transferring launch-configuration information for a set of panels and a first docking bar in a first application environment to a second application environment for a second docking bar in the second application environment includes detecting a docking of the multi-modal device to a hardware module, and displaying, in response to the docking, a user interface for the second application environment operating on the multi-modal device on the hardware module. The method further includes receiving, in response to the docking, at the second application environment the launch-configuration information for launching launchable objects in the first application environment from the second application environment on the multi-modal device. The method further includes parsing, by the second application environment, the launch-configuration information to determine a change to the set of panels or the first docking bar, wherein the change is in the first application environment; and changing the second docking bar to include the change to the set of panels or the first docking bar based on parsing the launch-configuration information.
According to another embodiment, a non-transitory computer-readable storage medium includes instructions for transferring launch-configuration information for a set of panels and a first docking bar in a first application environment to a second application environment for a second docking bar in the second application environment. The instructions are for controlling a multi-modal device to be operable for: detecting a docking of the multi-modal device to a hardware module; displaying, in response to the docking, a user interface for the second application environment operating on the multi-modal device on the hardware module; receiving, in response to the docking, at the second application environment the launch-configuration information for launching launchable objects in the first application environment from the second application environment on the multi-modal device; parsing, by the second application environment, the launch-configuration information to determine a change to the set of panels or the first docking bar, wherein the change is in the first application environment; and changing the second docking bar to include the change to the set of panels or the first docking bar based on parsing the launch-configuration information.
According to another embodiment, a multi-modal device configured for transferring launch-configuration information for a set of panels and a first docking bar in a first application environment to a second application environment for a second docking bar in the second application environment, the multi-modal device includes a processor for operating the first application environment and the second application environment; and a computer-readable storage medium comprises instructions for controlling the processors to be operable for: detecting a docking of the multi-modal device to a hardware module; displaying, in response to the docking, a user interface for the second application environment operating on the multi-modal device on the hardware module; receiving, in response to the docking, at the second application environment the launch-configuration information for launching launchable objects in the first application environment from the second application environment on the multi-modal device; parsing, by the second application environment, the launch-configuration information to determine a change to the set of panels or the first docking bar, wherein the change is in the first application environment; and changing the second docking bar to include the change to the set of panels or the first docking bar based on parsing the launch-configuration information.
According to an alternative embodiment, hardware module 105 may be a computing device, such as a personal computer, a laptop computer, a tablet computer, a server computer operating a server operating system, or the like. According to an embodiment where hardware module 105 is a computing device, the computing device may include an integrated monitor (e.g., a laptop computer, tablet computer, etc.) or a stand-alone monitor, which operates in conjunction with the computing device (e.g., desktop computing device with stand-alone monitor). In
Hardware module 105 includes a display 115 that displays a user interface 120. User interface 120 may display a set of panels 125 (labeled 125a, 125b . . . 125n in
Multi-modal device 100 includes a display 135 that displays a user interface 140. User interface 140 may display a selected panel (e.g., panel 125b) from the set of panels 125. The displayed panel on user interface 140 is sometimes referred to as a home-screen panel. The home-screen panel displayed on user interface 140 may be changed by dragging the displayed home-screen panels with a finger swipe or the like until different home-screen panel is displayed. User interface 140 may also display a docking bar 145.
One or more panels in the set of panels 125 may be associated with a set of launcher objects. The sets of launcher objects are labeled 150a, 150b . . . 150n in
A bookmark may be link. For example, a bookmark may be a link to a website, or the like. A widget includes a graphic on a panel and may provide status information (e.g., clock, calendar, weather, etc.), may provide an option to change a setting (turn Wi-Fi on/off, turn airplane mode on/off, etc.), may add a function to a panel, etc. A folder may be a folder for applications, bookmarks, other folders, etc.
Launcher objects may include icons for launchable objects, such as applications, bookmarks, etc., where an icon may include graphics and/or text, which identify a launchable object associated with the launcher object. A launcher object may be associated with a launchable object identified by the launcher object. For example, a launcher object that includes an application icon may be associated with an application represented by the application icon. According to another example, a launcher object for a bookmark may be associated with the link represented by the bookmark. As is well known in the art, if a launcher object is selected, the launcher object initiates the launch of the launchable object associated with the launcher object. For example, if the launcher object is for an application, selection of the launcher object may initiate the launching of the application.
As described briefly above, user interface 120 may display the set of panels 125 and docking bar 130 if multi-modal device 100 is docked to hardware module 105. According to a further embodiment, if multi-modal device 100 is docked to hardware module 105, manipulation of one or more of panels 125 on one of multi-modal device 100 and hardware module 105, causes the same manipulation to be displayed and on the other of multi-modal device 100 and hardware module 105. For example, if panel 125b (shown as the home screen panel in
According to another example, if panel 125b is manipulated (e.g., added, removed, changed, resized, etc.) on hardware module 105, the same manipulation is displayed on panel 125b on multi-modal device 100. According to a specific example, if a launcher object is added to panel 125b on hardware module 105, the launcher object is added to panel 125b on multi-modal device 100.
According to one embodiment, a manipulation of a launcher object in one or more of panels 125 on multi-modal device 100 causes a corresponding manipulation of the launcher object in docking bar 130 on hardware module 105. For example, if a launcher object is added to a panel included in the set of panels 125 on multi-modal device 100, the launcher object is added to docking bar 130. Alternatively, if a launcher object is removed from a panel included in the set of panels 125 on multi-modal device 100, the launcher object is removed from docking bar 130. Similarly, if a launcher object is modified (e.g., resized, updated to include different graphics or text, etc.) in a panel included in the set of panels 125 on multi-modal device 100, the launcher object is similarly modified in docking bar 130.
According to a further embodiment, a manipulation of a launcher object in docking bar 145 on multi-modal device 100 causes a corresponding manipulation of the launcher object in docking bar 130 on hardware module 105. For example, if a launcher object is added to docking bar 145 on multi-modal device 100, the launcher object is added to docking bar 130. Alternatively, if a launcher object is removed from docking bar 145 on multi-modal device 100, the launcher object is removed from docking bar 130. Similarly, if a launcher object is modified (e.g., resized, updated to include different graphics or text, etc.) in docking bar 145, the launcher object is similarly modified in docking bar 130.
According to one embodiment, docking bar 130 may be modified to include all of the launcher objects on all panels in the set of panels 125 and to include all of the launcher objects in docking bar 145.
First application environment 200 may be a “native” environment of multi-modal device 100, such as a mobile-telephone environment, a PDA environment, or the like. First application environment 200 may operate on multi-modal device 100. First application environment 200 may present user interface 140 on display 135 and may present a selected panel from the set of panels 125 on user interface 140. First application environment 200 may also present docking bar 145 on user interface 140.
Second application environment 205 may be an operating system environment, such as a Linux operating system environment. Second application environment 205 may operate on multi-modal device 100. Second application environment 205 may present user interface 120 on display 115 of hardware module 105 if multi-modal device 100 is docket to hardware module 105. Specifically, second application environment 205 may display image 107 of user interface 120 if multi-modal device 100 is docked to hardware module 105. Second application environment 205 may also displays the set of panels 125 on user interface 120 if multi-modal device 100 is docked to hardware module 105. Second application environment 205 may also display docking bar 130 on user interface 120 if multi-modal device 100 is docked to hardware module 105. Second application environment 205 may not display image 107, the set of panels 125, and docking bar 130 on either of multi-modal device 100 or hardware module 105 if multi-mode device 100 is not docked to hardware module 105.
First application environment 200 may operate a first set of launchable objects 210, and second application environment 205 may operate a second set of launchable objects 215. The first set of launchable objects 210 may be respectively associated with the sets of launcher objects 150a, 150b . . . 150n. The second set of launchable objects 215 may be associated with launcher objects that may be displayed in user interface 120, such as launcher objects 8-10. The sets of launcher objects 150a, 150b . . . 150n displayed by first application environment 200 on user interface 140 may respectively launch the first set of launchable objects 210 in first application environment 200.
The sets of launcher objects 150a, 150b . . . 150n may also be displayed by second application environment 205 on user interface 120 and may launch the first set of launchable objects 210 in first application environment 200. That is, launchable objects operable in the first application environment 200 may be launched via launcher objects from the second application environment 205. Second application environment 205 may collect launch-configuration information 255 from first application environment 200 for the first set of launchable objects 210 so that the first set of launchable objects 210 may be launched from the second application environment. Collection of launch-configuration information 255 by second application environment 205 from first application environment 200 is described in further detail below.
The second set of launchable objects 215 operable in the second application environment 205 on multi-modal device 100 may be launched via launcher objects (e.g., launcher objects 8-10) from the second application environment. It is noted that the first and second sets of launchable objects 215 and 220 may operate on multi-modal device 100 and may not operate on hardware module 105.
As briefly described above, the sets of launcher objects 150a, 150b . . . 150n may be displayed by second application environment 205 on user interface 120. For example, the sets of launcher objects 150a, 150b . . . 150n may be displayed in a launcher-object window on user interface 120 via use selection of a menu option or the like. A launcher-object window may be a distinct window not shown in user interface 120 in
Second application environment 205 may register to receive communications issued by first application environment 200, and thereafter listen for communications issued by first application environment 200 where the communications indicate one or more changes to one or more panels in the set of panels 125 and one or more changes to docking bar 145. A communication issued by first application environment 200 may include panel information 250 for changes to a panel. A communication issued by first application environment 200 may also include launch-configuration information 255 for the sets of launcher objects 150a, 150b . . . 150n where launch-configuration information 255 include various information for launching launchable objects operable in first application environment 200. Launch-configuration information 255 may be used by both first and second application environments 200 and 205 for launching launchable objects in first application environment 200. Communications exchanged by first and second application environments 200 and 205 are described in further detail below.
Transferring Launch-Configuration Information and Panel Information from the First Application Environment to the Second Application Environment
At 405, multi-modal device 100 detects being docked to hardware module 105. Multi-modal device 100 may be docked to hardware module 105 by a variety of docking technologies and docking protocols.
At 410, user interface 120 may be displayed on display 115 of hardware module 105 where user interface 120 is displayed by second application environment 205, which operates on multi-modal device 100. User interface 120 may display the set of panels 125, docking bar 130, and/or image 107 of user interface 140 on hardware module 105 in response the docking or in response to a user selection received via user interface 120.
At 415, second application environment 205 receives panel information 250 for the set of panels 125 from first application environment 200 and receives launch-configuration information 255 for the set of launchable objects 210 according to one embodiment. Panel information 250 may be generated at first application environment 200 based on user input receive via user interface 140 for changes to one or more panels and may be unsynchronized with second application environment 205. A panel may be changed by adding a launcher object to the panel, removing a launcher object from the panel, altering an appearance of an already displayed launcher object on the panel, resizing a launcher object on the panel (e.g., making the launcher object larger or smaller), adding the panel to the set of panels 125, removing the panel form the set of panels 125, rearranging the panel with respect to other panels in the set of panels 125, etc. Panel information 250 may indicate that a launcher object has been changed as described above or that one or more panels in the set of panels 125 have been change as described above.
Second application environment 205 may also store panel information 250 in memory 305 where second application environment 205 may access panel information 250 for displaying launcher objects in user interface 120. The storage of panel information 250 in memory 305 by second application environment 205 is sometimes referred to as storing panel information 250 in the second application environment.
Second application environment 205 may also store launch-configuration information 255 in memory 305 where second application environment 205 may access launch-configuration information 255 for launching launchable objects in first application environment 200. The storage of launch-configuration information 255 in memory 305 by second application environment 205 is sometimes referred to as storing launch-configuration information 255 in the second application environment. With launch-configuration information 255 for the set of launchable objects 215 stored in second application environment 205, second application environment 205 may launch a selected launchable object, for example, via user selection of a selected launcher object for the selected launchable object. A piece of launch-configuration information for each launcher object may be associated a piece of panel information for each launcher object so that selection of a selected launcher object will cause second application environment 205 to launch a selected launchable object associated with the selected launcher object.
At 420, second application environment 205 may parse panel information 250 to determine a change to the set of panels 125 where the change occurred in first application environment 200.
At 425, at least one launcher object is changed on docking bar 130. The change may be made based on parsing panel information 250 at 420 to determine the change in panel information 250 generated by first application environment 200 at 415. The at least one launcher object may be changed on docking bar 130 by: i) adding the at least one launcher object on docking bar 130, ii) removing the at least one launcher object from docking bar 130, iii) altering (e.g., changing a graphic and/or text) the at least one launcher object on docking bar 130, iv) resizing the at least one launcher object from docking bar 130, or the like. At 425, the at least one launcher object is changed on docking bar 130 if the at least one launcher object is correspondingly changed in the set of panels 125 in first application environment 200 or is correspondingly changed in docking bar 145 in first application environment 200. For example, the at least one launcher object may be added to docking bar 130 if the at least one launcher object is added to the set of panels 125 in first application environment 200 or is added to docking bar 145 in first application environment 200. Alternatively, the at least one launcher object may be removed from docking bar 130 if the at least one launcher object is removed from the set of panels 125 in first application environment 200 or is removed from docking bar 145 in first application environment 200. Alternatively, the at least one launcher object may be altered or resized in docking bar 130 if the at least one launcher object is altered or resized in the set of panels 125 in first application environment 200 or is altered or resized in docking bar 145 in first application environment 200. Panel information 250 transferred from the first application environment to the second application environment may indicate the foregoing described changes.
According to one embodiment, one or more of the foregoing described steps are repeated so that new launcher objects added to the set of panels 125 and/or added to docking bar 145 in first application environment 200, are added to docking bar 130 in second application environment 205. That is, second application environment 205 may continue to listen for new communication issued by first application environment 200 after previous communications are issued by the first application environment to the second application environment. Communication between first and second application environments 200 and 205 might cease if multi-modal device 100 is disconnected from hardware device 105.
The launcher objects that a user places on the set of panels 125 and/or docking bar 145 in first application environment 200, may be generally considered a user's “favorite” launcher objects for a user's “favorite” launchable objects. Displaying the launcher objects from the set of panels 125 and/or docking bar 145 from first application environment 200 in second application environment 205 provides that the user's selection of “favorite” launchable objects are represented on docking bar 130 in second application environment 205 for relatively simplified launch. Recall that at 415 and 420 second application environment 205 receives and stores launch-configuration information 255 for launching the launchable objects, which includes the user's favorite launchable objects represented on docking bar 130. Further, because panel information 250 identifies the user's favorite launchable objects to second application environment 205, the user does not have to go through a manual process of placing favorite launcher objects for the user's favorite launchable objects on docking bar 130.
According to one further embodiment, at least one panel in the set of panels 125 is changed on user interface 120 after panel information 250 and launch-configuration information 255 are transferred to second application environment 205 from first application environment 200. The change is made based on parsing panel information 250 at 420 to determine the change in panel information 250 generated by first application environment 200 at 415. According to one embodiment, the change to the at least one panel on user interface 120 includes a change to a launcher object (e.g., add, remove, alter, resize, etc.) in the at least one panel. According to an alternative embodiment, the at least one panel is changed on user interface 120 by removing the at least one panel for the set of panels 125, adding the at least one panel to the set of panels 125, or rearranging the at least one panel with another panel in the set of panels 125.
Referring again to
Second application environment 205 may include a communication manager 350, which may be the Webtop Intent Framework communication manager of Motorola. Second application environment 205 may also include an application tray manger 355 that manages user interface 120. According to one embodiment, when multi-modal device 100 is docked to hardware module 105, communication manager 350 registers with portal service manger 320 to receive communications form portal service manager 320. Subsequent to communication manager 350 registering with portal service manger 320 to receive communications, communication manager 350 listens for communications from portal service manager 320s where the communications may include panel information 250 for changes to the set of panels 125 and may include launch-configuration information 255 for the sets of launchable objects 150a, 150b . . . 150n. The registration for receiving communications may be viewed as a request for panel information 250 and launch-configuration information 255.
As used in the description herein and throughout the claims that follow, “a”, “an”, and “the” includes plural references unless the context clearly dictates otherwise. Also, as used in the description herein and throughout the claims that follow, the meaning of “in” includes “in” and “on” unless the context clearly dictates otherwise.
The above description illustrates various embodiments of the present invention along with examples of how aspects of the present invention may be implemented. The above examples and embodiments should not be deemed to be the only embodiments, and are presented to illustrate the flexibility and advantages of the present invention as defined by the following claims. Based on the above disclosure and the following claims, other arrangements, embodiments, implementations, and equivalents may be employed without departing from the scope of the invention as defined by the claims.
Jung, Ji Hye, Barat, Nirmalya, Dharawat, Parikshit, Gangam, Vamshika R.
| Patent | Priority | Assignee | Title |
| Patent | Priority | Assignee | Title |
| 5119494, | Jul 10 1990 | Athenix Corporation | Application address display window mapper for a sharable MS-DOS processor |
| 5446904, | Aug 30 1991 | NEC Corporation | Suspend/resume capability for a protected mode microprocessor |
| 5592657, | May 01 1992 | JOHNSON, R BRENT | Console simulator, multi-console management system, and console management distribution system |
| 5757371, | Dec 13 1994 | Microsoft Technology Licensing, LLC | Taskbar with start menu |
| 5828376, | Sep 23 1996 | J D EDWARDS WORLD SOURCE COMPANY | Menu control in a graphical user interface |
| 6043816, | May 29 1998 | MICRO FOCUS LLC | User interface mechanism for maintaning quick access to important information in a windows-based computer environment |
| 6133915, | Jun 17 1998 | Microsoft Technology Licensing, LLC | System and method for customizing controls on a toolbar |
| 6167425, | Nov 22 1996 | System for implementing a real time control program in a non-real time operating system using interrupts and enabling a deterministic time charing between the control program and the operating system | |
| 6170045, | Apr 30 1997 | International Business Machines Corporation | Cross-system data piping using an external shared memory |
| 6178503, | Sep 11 1998 | CA, INC | Managing multiple operating systems on a single computer |
| 6205452, | Oct 29 1997 | R R DONNELLEY & SONS COMPANY | Method of reproducing variable graphics in a variable imaging system |
| 6215490, | Feb 02 1998 | International Business Machines Corporation | Task window navigation method and system |
| 6338149, | Jul 31 1998 | WESTINGHOUSE ELECTRIC CO LLC | Change monitoring system for a computer system |
| 6460136, | Jul 12 1999 | HEWLETT-PACKARD DEVELOPMENT COMPANY, L P | Method and apparatus for loading an operating system kernel from a shared disk memory |
| 6691146, | May 19 1999 | International Business Machines Corporation | Logical partition manager and method |
| 6710788, | |||
| 6757002, | Nov 04 1999 | Hewlett-Packard Company | Track pad pointing device with areas of specialized function |
| 6763458, | Sep 27 1999 | OPEN TEXT S A | System and method for installing and servicing an operating system in a computer or information appliance |
| 7114104, | Feb 11 2003 | BMC SOFTWARE, INC | System and method of fault detection in a Unix environment |
| 7328333, | Dec 07 2001 | Lenovo PC International | Apparatus, method and program product for selectively starting one of a plurality of operating systems and secondary storage according to whether or not a predetermined peripheral is connected to the system |
| 7363128, | Sep 28 2004 | EATON INTELLIGENT POWER LIMITED | Application launcher |
| 7424601, | Jul 07 2004 | Intellectual Ventures Holding 81 LLC | Methods and systems for running multiple operating systems in a single mobile device |
| 7424623, | Mar 28 2002 | MAISHI ELECTRONIC SHANGHAI LTD | Personal computer integrated with personal digital assistant |
| 7461144, | Feb 16 2001 | Virtuozzo International GmbH | Virtual private server with enhanced security |
| 7523738, | Jun 22 2007 | GM Global Technology Operations LLC | Idle quality by torque smoothing |
| 7529921, | Dec 17 2004 | Cardiac Pacemakers, Inc | Fast initialization of medical device system having multiple operating systems |
| 7533101, | Mar 04 2002 | Microsoft Technology Licensing, LLC | Extensible loader |
| 7536537, | Apr 20 2006 | HARRIS GLOBAL COMMUNICATIONS, INC | Simultaneous dual booting of platforms |
| 7590945, | Jun 14 2004 | AT&T Intellectual Property I, L P | Viewing applications from inactive sessions |
| 7595810, | Mar 22 2006 | Apple Inc | Methods of manipulating a screen space of a display device |
| 7634770, | May 19 2003 | GOOGLE LLC | Kernel module interface dependencies |
| 7636586, | Oct 12 2005 | CONVERSANT WIRELESS LICENSING S A R L | Mobile communication terminal |
| 7681134, | Apr 25 2006 | Parallels International GmbH | Seamless integration and installation of non-host application into native operating system |
| 7689820, | Sep 27 2006 | L3 Communications Corporation | Rapid-boot computing device with dual operating systems |
| 7783665, | Mar 27 2002 | Virtuozzo International GmbH | Effective file-sharing among virtual environments |
| 7882274, | Sep 20 2007 | FH Innovations, Ltd | Computer system with multiple terminals |
| 7975236, | Apr 25 2006 | Parallels International GmbH | Seamless integration of non-native application into host operating system |
| 8046570, | Feb 06 2007 | Microsoft Technology Licensing, LLC | Supporting multiple operating systems in media devices |
| 8177554, | Jun 02 2009 | Device and method for locating a pulp chamber in a tooth | |
| 8195624, | Jun 30 2005 | Insyde Software Corporation | Shared file system management between independent operating systems |
| 8261231, | Apr 06 2011 | Media Direct, Inc. | Systems and methods for a mobile application development and development platform |
| 8307177, | Sep 05 2008 | Commvault Systems, Inc. | Systems and methods for management of virtualization data |
| 8352733, | Aug 04 2006 | Apple Inc | Resource restriction systems and methods |
| 8392498, | Oct 08 2010 | AUGA TECHNOLOGIES LIMITED | Distribution of content and behavior to disparate platforms |
| 8396807, | Jun 26 2009 | International Business Machines Corporation | Managing resources in virtualization systems |
| 8448251, | Apr 08 2008 | ARM Limited | Method and apparatus for processing and displaying secure and non-secure data |
| 8589952, | Jun 30 2010 | Qualcomm Incorporated | Dual operating system operation and configuration |
| 8868899, | Jul 20 2009 | Google Technology Holdings LLC | System and method for switching between environments in a multi-environment operating system |
| 8983536, | Oct 22 2010 | Google Technology Holdings LLC | Resource management in a multi-operating environment |
| 20010035882, | |||
| 20020078260, | |||
| 20020140742, | |||
| 20020151334, | |||
| 20020157001, | |||
| 20030065738, | |||
| 20030135771, | |||
| 20030204708, | |||
| 20030221087, | |||
| 20040015966, | |||
| 20040039950, | |||
| 20040061723, | |||
| 20040066414, | |||
| 20040095388, | |||
| 20040111644, | |||
| 20040148375, | |||
| 20040205755, | |||
| 20040207508, | |||
| 20050086650, | |||
| 20050108297, | |||
| 20050229188, | |||
| 20050240756, | |||
| 20050240763, | |||
| 20050246505, | |||
| 20060005187, | |||
| 20060010314, | |||
| 20060010446, | |||
| 20060026274, | |||
| 20060046706, | |||
| 20060224989, | |||
| 20060225107, | |||
| 20060253706, | |||
| 20070050765, | |||
| 20070128899, | |||
| 20070135043, | |||
| 20070150842, | |||
| 20070162298, | |||
| 20070180398, | |||
| 20070192329, | |||
| 20070198656, | |||
| 20070226647, | |||
| 20070266231, | |||
| 20070283147, | |||
| 20070288941, | |||
| 20070294689, | |||
| 20080028326, | |||
| 20080082815, | |||
| 20080100568, | |||
| 20080114844, | |||
| 20080162983, | |||
| 20080256468, | |||
| 20080276195, | |||
| 20080282205, | |||
| 20080307350, | |||
| 20080307360, | |||
| 20090031329, | |||
| 20090037909, | |||
| 20090063845, | |||
| 20090064186, | |||
| 20090080562, | |||
| 20090089569, | |||
| 20090158299, | |||
| 20090193074, | |||
| 20090199122, | |||
| 20090199219, | |||
| 20090235200, | |||
| 20090241072, | |||
| 20090276771, | |||
| 20090287571, | |||
| 20090327917, | |||
| 20090328033, | |||
| 20100064251, | |||
| 20100077347, | |||
| 20100097386, | |||
| 20100107115, | |||
| 20100138515, | |||
| 20100211769, | |||
| 20100217912, | |||
| 20100245037, | |||
| 20100313165, | |||
| 20100319008, | |||
| 20100333088, | |||
| 20100333100, | |||
| 20110016299, | |||
| 20110016301, | |||
| 20110054879, | |||
| 20110066984, | |||
| 20110093691, | |||
| 20110093836, | |||
| 20110119610, | |||
| 20110126216, | |||
| 20110138314, | |||
| 20110144970, | |||
| 20110179387, | |||
| 20120036450, | |||
| 20120041570, | |||
| 20120042159, | |||
| 20120081353, | |||
| 20120081380, | |||
| 20120083264, | |||
| 20120084542, | |||
| 20120084791, | |||
| 20120102495, | |||
| 20120150970, | |||
| 20120173986, | |||
| 20120174021, | |||
| 20120192100, | |||
| 20120227058, | |||
| 20120278747, | |||
| 20120278750, | |||
| 20120304092, | |||
| 20130212283, | |||
| 20130293573, | |||
| 20130298140, | |||
| 20130298141, | |||
| CN101025701, | |||
| CN101051282, | |||
| CN101149685, | |||
| CN101382833, | |||
| CN101615123, | |||
| EP1059582, | |||
| EP1688816, | |||
| GB2369959, | |||
| JP2009157802, | |||
| WO2007035611, | |||
| WO2011060382, | |||
| WO2012012865, | |||
| WO2012148881, | |||
| WO2012148885, |
| Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
| May 17 2012 | Google Technology Holdings LLC | (assignment on the face of the patent) | / |
| Date | Maintenance Fee Events |
| Date | Maintenance Schedule |
| Sep 15 2018 | 4 years fee payment window open |
| Mar 15 2019 | 6 months grace period start (w surcharge) |
| Sep 15 2019 | patent expiry (for year 4) |
| Sep 15 2021 | 2 years to revive unintentionally abandoned end. (for year 4) |
| Sep 15 2022 | 8 years fee payment window open |
| Mar 15 2023 | 6 months grace period start (w surcharge) |
| Sep 15 2023 | patent expiry (for year 8) |
| Sep 15 2025 | 2 years to revive unintentionally abandoned end. (for year 8) |
| Sep 15 2026 | 12 years fee payment window open |
| Mar 15 2027 | 6 months grace period start (w surcharge) |
| Sep 15 2027 | patent expiry (for year 12) |
| Sep 15 2029 | 2 years to revive unintentionally abandoned end. (for year 12) |