• 专利附录
  • 专利说明
  • 权利要求
  • 类似技术
  • 同族专利
  • 引用文献
  • 法律状态
  • 优先权
    • 专利摘要:
    method for initializing and method for operating a device having at least two operating system environments various embodiments of the present invention provide a mobile computing device that operates several co-existing and independent operating system environments on a common core. a boot process for starting a multiple operating system environment is also provided. in addition, various embodiments of the present invention include processes for managing a change from one operating system environment to a second operating system environment.
    公开号:BR112012000888B1
    申请号:R112012000888
    申请日:2010-07-20
    公开日:2019-12-17
    发明作者:N Tzakis Andrew；C Carlyle Jeffrey；D Galicia Joshua
    申请人:Google Technology Holdings LLC；Motorola Mobility Llc；Motorola Mobility Inc；
    IPC主号:
    专利说明:

    METHOD FOR INITIALIZING AND METHOD FOR OPERATING A DEVICE WITH AT LEAST TWO OPERATING SYSTEMS ENVIRONMENTS
    FIELD OF THE INVENTION
    The present invention generally relates to operating systems and methods for initiating an operating system boot sequence. More specifically, the present invention relates to multi-environment operating systems and methods for starting multi-environment operating systems.
    BACKGROUND OF THE INVENTION
    Operating systems are designed and generally optimized based on specific applications and the desired user performance. It is often desirable to have features of one type of operating system available for another operating system, as preferred user programs may be operating system dependent.
    General purpose computer operating systems such as Linux TM and Windows TM have an extensive set of features, such as file systems, device drivers, applications, libraries, etc. These operating systems allow the simultaneous execution of several programs, and try to optimize the response time (also known as latency time), and CPU usage, or load, associated with the service of the programs running simultaneously. Unfortunately, however, such operating systems are generally not suitable for embedded real-time applications, such as for mobile computing devices. Under certain circumstances, it would be desirable for a mobile computing device to have the
    Petition 870190105898, of 10/18/2019, p. 8/53 performance associated with a specific mobile embedded operating system and features of a general purpose operating system.
    Linux, for example, is a well-known general-purpose desktop operating system with many desirable features for modern devices, including features of modern operating systems, numerous development tools, networks, etc. However, Linux was not designed to be a real-time or embedded operating system. Many modern devices, such as, without limitation, set top boxes, cell phones and car navigation systems, require not only the functionality of a general-purpose operating system like Linux, but also the functionality of a real-time or embedded, including real-time performance.
    Historically, running multiple operating environments on a single device has been accomplished using virtualization techniques, such as VMware ™, VirtualBox ™, QEMU ™, etc. However, when using virtualization a complete computer is emulated and one or more stacks of software are operated on the emulated computing device. Emulation is done with high overhead costs.
    In view of the above, there is a need for a system implementing a single-core environment that efficiently and conveniently provides the performance and functionality of co-existing, independent operating systems.
    BRIEF SUMMARY OF THE INVENTION
    In accordance with at least one embodiment of the present invention, a method for initializing a device having at least two independent co-existing operating environments is provided. The method includes initiating a start-up boot sequence, initializing a central core, identifying a device mode state, launching services common to a first operating system and a second operating system, selecting a primary operating system based on at least part in the mode state and launching startup scripts of the primary operating system; and launching startup scripts for a secondary operating system.
    In an alternative embodiment, a method for operating a device having several coexisting operating environments is provided. The method includes starting a boot sequence configured to simultaneously launch two operating system environment environments, identifying the device's mode state, and selecting a primary operating environment based at least in part on the mode state.
    In yet another embodiment of the present invention, a mobile device operating system having a central core configured to interface a device hardware component and a middleware component is provided. The system includes at least two co-existing independent middleware operating environments coupled to the central core, the middleware operating environments each having a corresponding application component.
    According to another embodiment of the invention, a mobile computing device having a memory storage unit coupled to a computer processor is provided. The memory storage unit includes computer-executable instructions capable of operating at least two operating system environments on a common core.
    In yet another alternative embodiment, a mobile phone with a graphical user interface configured to receive and transmit multimedia information is provided. The phone includes a computing system with a processor attached to a memory storage unit, and a multi-environment operating system having a common core. The memory storage unit includes executable computer instructions capable of managing resources shared between at least two co-existing independent operating system environments.
    In accordance with an alternative embodiment, the present invention includes a mobile computing device with a computer processor coupled to a computer memory having computer executable instructions configured to start an operating system. The device also includes an operating system configured to run a standard Linux distribution operating system environment and a single core Android ™ operating system environment simultaneously.
    In accordance with yet another alternative embodiment, the invention includes a mobile device operating system having a central core configured to interface a device hardware component and a middleware component. The device also includes a first independent middleware operating environment configured to run JAVA-interpreted applications and attached to the central core, and a second independent middleware operating environment configured to run native applications and attached to the central core.
    BRIEF DESCRIPTION OF THE DRAWINGS
    Figure 1 is an exemplary perspective view of a mobile device;
    Figure 2 is a block diagram representing an exemplary operating system;
    Figure 3 is a block diagram of an exemplary operating system;
    Figure 4 is a block diagram of a runtime coexistence scheme for an exemplary operating system;
    Figure 5 is a block diagram of an inter-environment communication scheme for an exemplary operating system;
    Figure 6 is a flowchart identifying steps in a boot sequence for an exemplary operating system;
    Figure 7 is a flowchart identifying exemplary steps for launching an application in a first operating environment while an exemplary operating system is controlled by a second operating environment;
    Figure 8 is a message sequence graph identifying exemplary steps for launching a second operating environment application while a first operating environment has primary control;
    Figure 9 is a flowchart identifying exemplary steps associated with moving from a first operating environment to a second operating environment;
    Figure 10 is a message sequence graph identifying exemplary steps for moving from a first operating environment to a second operating environment;
    Figure 11 is a message sequence graph identifying exemplary steps for moving from a second operating environment to a first operating environment;
    Figure 12 is a flowchart identifying an exemplary use of an application controlled by a first operating environment while a second operating environment has the primary control of a computing device.
    DETAILED DESCRIPTION
    It is anticipated that it would be advantageous to have an embedded operating system and a Linux-based operating environment communicating directly with a single Linux core running directly on the hardware of a computing device.
    Referring to Figure 1, a mobile phone 10 is provided. The phone 10 includes a graphical interface 12 and a plurality of data entry buttons 14. The mobile device 10 is selected from the group that includes, but is not limited to, a personal mobile computer (PC), a netbook, a telephone mobile, a laptop computer, a laptop computer and a smart phone. Although device 10 is mobile, it is intended to have significant computing power, with a processor speed of more than 500 mHz, although slower processors are not excluded. Considering the computational power, a user can connect device 10 to a variety of peripheral devices (not shown). Peripheral devices are selected from a group that includes, but is not limited to, a computer monitor, a laptop computer, a personal computer, a tablet PC, and a screen projector.
    Now referring to Figure 2, a block diagram of an exemplary operating system (OS) 16 in communication with a core 18 is provided. OS 16 can be a Linux distribution system, a Linux-based operating system, or a non-Linux-based operating system. Device hardware 20 is also in communication with core 18. Operating system 16 includes a first operating system environment 22 and a second operating system environment 24 in communication with a single core
    18. For example, the second middleware operating system environment 24 is a standard Linux distribution and the first middleware operating system environment 22 is an embedded operating system environment for use on mobile devices, such as the Android ™ operating system (Open Handset Alliance, www.openhandsetalliance.com). A Linux 16 distribution is in communication with the Linux 18 core, which is in communication with the device hardware 20. The device hardware 20 can be a memory storage device (not shown), coupled to a processor (not shown) , which stores computer executable instructions that are configured to perform various functions and operations, as described here.
    An exemplary operating system 16 includes Ubuntu ® (Canonical Ltd., www.ubuntu.com) for the Linux 24-based operating system environment. It is specifically intended that multiple middleware operating system environments coexist independently of each other (s). Exemplary environments that can be included in operating system 16 include Android ™, Ubuntu® (Canonical Ltd., www.ubuntu.com), standard Linux-based environments, Symbian (Symbian Foundation Ltd., www.symbian.com), and environments Windows-based. In an alternative modality, it is expected that more than two operating system environments are configured to co-exist independently in the same central core 18.
    Referring to Figure 3, a block diagram of an exemplary operating system is provided. In the present exemplary embodiment, the first operating system environment 22 is an operating environment based on Android ™ and the second OS 24 environment is based on Linux. The first operating system environment 22 includes a portal service module 26, a portal activity module 28, an operating system service module 30 and an operating system application module 32. The second operating system environment 24 includes a resource manager 34, an Android module in a window (AIW) 36, a second operating system application 38 and a second operating system service module 40.
    AIW 36 module is configured to display a first OS 22 application window in GUI 12, while the second operating system 24 is the primary operating environment.
    The portal service module 26 contains a set of instructions configured to enable service for the first operating system 22 and directs all communication with the resource manager 34. While device 10 is operating the portal service module 2 6 is preferably run at all times. In addition, the portal service module 26 is linked to the activity associated with the portal activity module 28, as well as to the transmission events of the first OS 22. The portal activity module 28 is an application, or set of instructions executable by computer, which represents a second OS 24 application located in the first OS 22 stack. For example, if the second operating system 24 is Ubuntu® the portal activity module 28 may represent a specific Ubuntu application, and when the module portal activity 2 8 is focused, Ubuntu is in view through GUI 12. Numerous applications can run simultaneously, also referred to as an application execution stack, within any given operating environment. Logically speaking, the top-level application is considered to be focused.
    Core 18 includes a set of drivers 42 and an AEV 44 module. Included with drivers 42 are input device drivers for hardware components 20. 0 AEV 44 is a core module that takes absolute coordinates and AIW keyboard events 3 6 and passes them to an event hub.
    Co-existing environments within operating system 16 communicate with each other. Resource manager 34, which is part of the second operating system 24, communicates directly with the portal service module 26, which is part of the first operating system 22. In addition, the portal service module 26, which is part of the first operating system 22, communicates directly with resource manager 34. resource manager 34 is a set of instructions configured to manage resources shared by the first operating system 22 and second OS 24. Shared resources include video devices, video devices input, power management services and system status information. In addition, resource manager 34 is configured to control OS 22.24's access to hardware 20. In addition, resource manager 34 identifies and controls which operating system user interface 22.24 is displayed through GUI 12 .
    According to the present modality, portal service 26 is the source of all communications from the first operating system 22 to resource manager 34. In addition, portal service 26 is a place for all callbacks to from resource manager 34 to the first operating system 22. The resource manager provides a discoverable state application programming interface (API) for portal service 26. This API is configured to be called by resource manager 34 a anytime. Resource manager 34 is configured to obtain and process running state, which allows the resource manager to maintain a state machine. For the first OS
    22, portal service 26 provides execution states for processes that require them. Likewise, portal services 26 request and receive status updates for processes that provide state information. Similar communication for the second operating system 24 is controlled by the resource manager 34, which provides the running states for the processes that require them. Resource Manager 34 requests and receives state updates from various processes that provide state information. Device drivers 42 logically associated with core 18 communicate directly with resource manager 34, as well as processes that provide runtime state information. For example, the API arbitrates access to user interface devices, such as screens, touch screens or the GUI 12. Yet another example, the API arbitrates access to power input devices, such as batteries and / or plugs. AC / DC wall
    The first OS 22 and the second OS 24 are independent of each other, and co-exist with respect to each other. Each OS 22, 24 is a fully functional operating system environment, and does not require the other operating system environment to function. Both operating system environments exist on the same device 10 with 100% independence from each other. As identified above, the first and second operating systems 22, 24 do not co-exist in a virtualization or emulation scheme, but actually work in a single core 18. Instead, there is a co-existence of runtime in which both OS 22.24 runs in their respective native environments and no OS 22.24 is recompiled, as there is no need to leverage a common C execution environment. Applications can be accessed by a user that are coded only for one OS or another 22, 24 without interrupting the user's computing experience.
    Referring to Figure 4, a block diagram provides an exemplary co-existence scheme for an Android® 22 OS and an Ubuntu ™ 24 OS. Each OS 22.24 operates in a separate execution environment, which provides software services for programs and / or processes, while device 10 is operating. Android 46 processes and Android 48 libraries access a C Bionic 50 Library, which is optimized and modified specifically for the Android environment. Ubuntu 52 processes and Ubuntu 54 libraries access the C Glibc 56 Library, which is a GNU C library used on many standard Linux-based systems. Each operating system environment runs in its respective C libraries without conflicting with another operating environment.
    Referring to Figure 5, a more detailed communication path between the first operating system 22 and the second OS 24 described in Figure 4 is provided. An interprocess communication system (IPC) is configured to manage the inter-environment communication flow between the first operating system 22 and the second OS 24. Portal service 26 communicates with a DBUS Link 58, which is a software package containing language programming and executable instructions configured to communicate with a DBUS 60 library. Resource manager 34 communicates with a DBUS connection
    Glib 62, which is also a software package containing programming language and executable instructions configured to communicate with a DBUS 64 library configured for the second operating system 24. Both the first OS 22 DBUS library 60 and the second 64 OS library 24 communicate via a DBUS 66 Daemon, which is logically part of the second operating system 24, and acts as the communication link between the two operating environments.
    Referring to Figure 6, a flow chart representing an initialization sequence is provided. The boot sequence includes both the specific and common operating system steps. The current boot sequence is dependent on rules associated with a predetermined device state that determines the boot sequence. For example, if the device is connected to a peripheral device, such as a monitor, the device status is considered to be in docked mode, and according to OS 24 it is the standard primary environment. Alternatively, if device 10 is not connected to a peripheral device, then it is in mobile mode, and the first OS 22 is the standard primary operating environment. However, the secondary operating environment is launched simultaneously with the primary environment, and operates in the background in the event that the state of device 10 changes and the secondary environment is changed to become the primary environment. For example, when device 10 is in docked mode and the peripheral device is turned off, there is an automatic switch to mobile mode, which results in the secondary environment becoming the primary environment, and vice versa.
    The boot sequence starts at step 68, followed by the launch of the central Linux kernel 18 at step 70. A boot loader program starts before the kernel is released. After the Linux kernel 18 is booted, the central kernel launches user space scripts in step 72. Resource manager 34 is launched in step 74, followed by identifying the mode state in step 76. Once the mode state a reference library is identified which is accessed in step 78 to determine the criteria associated with and / or dictated by the mode state that is identified. In step 80, services common to both the first operating system 22 and the second OS 24 are launched. The mode state determined in step 76 is referenced in step 82. If the mobile state is identified, then the first operating system 22 is the primary operating environment, then the first OS startup scripts are launched in step 84, followed by the scripts second operating system bootstrap launched in step 86. If the embedded state is referenced in step 82, then the second OS 24 is the primary operating environment, and then the second OS 24 bootstrap scripts are launched in step 88 followed by launching the first OS 2 2 startup scripts in step 90. Regardless of which environment is the primary, both environments are launched and running before device 10 is operational in step 92. Since the common services are launched in step 80 first, for all purposes and purposes, the primary and secondary environments are launched in parallel. However, specific primary environment services, based on the state of the device, are launched immediately before the specific secondary environment services. By separating the launch of common services with the launch of a specific environment, device 10 can be quickly operational with several co-existing and independent operating environments.
    Referring to Figure 7, a flowchart identifying steps for launching a second OS 24 application while device 10 is in mobile mode 94 and the first OS 22 has primary control. A second OS 24 application, mobile PC, is selected in step 96. Mobile PC is an application in the first OS 22, which provides a complete PC view, alternatively referred to as a netbook view, while device 10 is operating in mode mobile and the first OS 22 is in primary control. In an alternative mode, individual applications from the second OS 24 onwards can be listed in a menu of the first OS 22 and launched individually, which can be similar to a netbook view.
    Portal service 26 sends a status update communication to resource manager 34 in step 98 indicating that portal activity 28 has gained focus. Thereafter, resource manager 34 disables the entry of the first OS 22 and switches a virtual terminal in step 100. The mobile PC application is displayed in GUI 12 in step 102. When operating the mobile PC application, an unsolicited event may occur in the step 104 or a user requested event can occur in step 106. Unsolicited events include time critical and non time critical events. For example, a time-critical unsolicited event includes a scheduled or unscheduled phone call or alarm. In addition, for example, an unsolicited non-time critical event includes an SMS message, an email message or a device update notification. After an event 104,106 occurs, service portal 26 sends a communication to resource manager 34 indicating that portal activity 28 has lost focus in step 108. In step 110, resource manager 34 asks the first operating system 22 to allow the incoming event flow and changes the virtual terminal. For example, the current mode includes separate virtual terminals to switch display control between the first operating system 22 and the second OS 24. In general terms, a virtual terminal is a Linux application that allows a system user to change the display between the Windows-based view and a system console.
    When an unsolicited event occurs or a user selects the Home button in step 112, portal activity 28 is switched to the bottom in step 114 while the unsolicited event continues or the user operates another application from the GUI Home menu 12. Alternatively, if the user selects the Back button in step 112, portal activity 28 exits the application and device 10 reverts to the idle main menu in step 94. User-initiated events, such as selecting the Home button, Back button , or starting a new application are exemplary requested events. When an event occurs a decision is made at step 118, and the first operating system 22 is stopped at step 120 if the event is an unsolicited event. Alternatively, if the event is a requested event, such as the user selecting the Home button, then the device reverts to the idle main menu in step 94. After the OS interruption in step 120, the interrupting application will end and the portal 28 regains focus at step 122 and device 10 reverts to step 98.
    In an alternative mode, the virtual terminal is not used. Rendering a second OS 24 application while in mobile mode it can be done through a VNC type application. The second OS 24 application, such as Ubuntu, can be rendered remotely in the VNC client. In addition, this modality does not take control of the physical display of the first operating system 22.
    In yet another alternative modality, non-critical time notifications generated by the first OS 22 are identified and listed on a panel within the scope of the second OS 24. When listing the notifications on a panel, the status information of the first operating system 22 is integrated with the second OS 24 view when the second operating system 24 is the primary operating system. At the user's leisure, the panel is accessed to reveal notifications of non-critical weather status. When the panel is involved the first operating system 22 becomes the primary operating system and allows notifications to be viewed. For example, the panel can be a push down list that descends from a state area with a slip gesture.
    Referring to Figure 8, a message sequence graph identifying the steps for launching a second OS 24 application while the first operating system 22 has primary control is provided. The sequence graph provides an intelligent step flow, from top to bottom, of the signals transmitted between the portal activity module 28 and the resource manager 34. Portal activity 28 receives a signal 124 for launching the portal and disables the entry. The first operating system 22 has primary control before signal 126 changes the mode state to the second operating system 24 obtaining primary control. Signal 126 is sent from portal activity 28 to resource manager 34, which then generates a responsive signal 128 sent to portal activity 28, indicating that the second OS 24 is the primary OS. Signal 130 is received by portal activity 28 and enables entry. Signal 132 is sent from portal activity 28 to resource manager 34 by changing the mode state from the second OS 24 to the first operating system 22. After receiving signal 132 the resource manager 34 switches the virtual terminal. Resource manager 34 then sends a state update signal 134 to portal activity 28 indicating that the first operating system 22 is primary.
    Doing reference The figure 9, a flow chart identifying steps associated with the change of one first operating environment to a second environment operational is provided. 0 device 10 is inactive at the mobile mode ( lOSL 22), in step 136. In step 138 O device 1 0 is on to a docking station, or connected to a device peripheral. For example, an
    HDMI connection can be established between device 10 and a monitor or television. Resource manager 34 is notified of the updated connection status in step 140 and the first operating system 22 is disabled in step 142 in response to the connection state change. The first OS 22 portal changes the shared memory frame buffer in step 144, followed by resource manager 34 changing the virtual terminal in step 146. If the Mobile PC application is displayed in step 148, then portal activity 26 exits in step 150. Alternatively, if the Mobile PC application is not on display, docked mode is enabled in step 152. In the event that the device state changes in step 154, then resource manager 34 receives a status update status in step 156. For example, the state of the system changes when a user removes an HDMI cable, or similar connector, which is used to connect device 10 to a peripheral device. Following a state update event 156, the first operating system 22 is activated 158 and the device operates in mobile mode. A frame buffer change is requested in step 160 and a virtual terminal change is requested in step 162, both of which are performed by portal activity 26. Following step 162, the device reverts to an idle state in mobile mode 136 .
    Referring to Figure 10, a message sequence graph identifying the steps taken when device 10 transitions from mobile (OSL) to docked (OS2) mode is provided. Device 10 is operating in mobile mode and the first OS 22 is the primary OS.
    A cable signal 164 is received by the resource manager 34, which indicates that an HDMI or alternate wired plug has been connected to device 10. The cable signal 164 is an exemplary state start-up signal. In an alternative embodiment, the plug can be wireless communication between the device 10 and a peripheral device, and disabling the wireless communication would cause a mode change-state signal to be generated. A sequence of signals transiting the device from mobile to docked mode is initiated. Signal 164 is sent from resource manager 34 to portal activity 28 indicating a mode state transition and disabling the main data entry. Portal activity 28 sends signal 168 to resource manager 34 to identify that the second operating system 24 is now primary and switch the virtual terminal. Signal 170 is sent from the resource manager 34 to the portal activity identifying the second operating system 24 as the primary and which has taken over the frame buffer. A mode change confirmation signal 172 is sent from portal activity 28 to resource manager 34 identifying that the device is now in docked mode and that the second OS 24 is the primary OS. A system mode update signal is sent from resource manager 34 to AIW 36.
    Referring to Figure 11, a message sequence graph identifying the steps taken when device 10 transitions from docked (OS2) to mobile (OSL) mode is provided. A cable signal 176 is received by resource manager 34, which indicates that an HDMI or alternate wired plug has been removed from device 10. Removing the plug indicates that a peripheral device (not shown) is no longer communicating with device 10. In an alternative embodiment, the plug may be in wireless communication between device 10 and a peripheral or alternative device (not shown). A sequence of signals transiting the device from docked to mobile mode is initiated. Signal 178 is sent from resource manager 34 to portal activity 28, indicating a mode state transition and enabling the main data entry and the main frame buffer. Portal activity 28 sends signal 180 to resource manager 34 identifying that the first operating system 22 is now primary and switching the virtual terminal. Signal 182 is sent from the resource manager 34 to the portal activity identifying the first operating system 22 as the main one and which has taken over the frame buffer. A mode change confirmation signal 184 is sent from portal activity 28 to resource manager 34 identifying that the device is now in mobile mode and that the first operating system 22 is the primary OS. A system mode update signal is sent from resource manager 34 to AIW 36.
    Referring to Figure 12, device 10 is idle in docked mode and the second operating system 24 is the primary operating environment in step 188. If an unsolicited event occurs in step 190 or the user selects OSI 22 in an application window in step 192, then OSI 22 in a window application is launched in step 194. For example, if Android is the mobile operating environment 22, then an Android window application (AIW) is started. The AIW application allows a user to access Android applications while the device is operating in docked mode. Resource manager 34 is also notified of the status update in step 194. Input to the first operating system 22 is activated in step 196, followed by the transmission of display update notifications from the first OS in step 198. The AIW application is operating and has focus on step 200. If the AIW application is terminated at step 202 or a user removes AIW from focus at step 204, then the first OS 22 entry is disabled at step 206. The first OS 22 display is stopped in step 208. If the AIW application is terminated in step 210, then system 188 reverts to docked idle mode. Alternatively, if the AIW application loses focus, then the application operates in this state, in step 212. In the case of an unsolicited event in step 214 or an interaction requested with the AIW application in step 216, the AIW regains focus in step 218. While the AIW is out of focus a user can select the AIW application and continue interacting with the AIW window, which returns the focus to the AIW and notifies resource manager 34 of the status update. After the AIW regains focus, the entry for the first operating system 22, which is Android for the present mode, is activated in step 220. The first OS 22 display update notifications are transmitted to resource manager 34, in step 222 , followed by the system rollback to step 200, where AIW is activated and in focus. When an application is in focus, this application is at the logical top of a stack of running applications.
    In an alternative embodiment, it is contemplated that the device 10 can transition between states in a mode based on events that do not fit or disengage from device 10. For example, if device 10 is stationary for a predefined period of time, device 10 it can be programmed to operate in the most energy efficient state, regardless of the device state otherwise. In yet another example, a user can transition from docked to mobile, even if the device has a connection to a peripheral device. In addition, the type of peripheral device connected to device 10 can dictate whether an automatic mode change sequence is initiated, or a user is provided with a mode change request. The user, thus, being able to select the state of the mode in which to operate the device 10. In yet another alternative mode, the additional mode states are contemplated based on the use of a particular device 10 and the applications available in the device's memory 20.
    Specifically, it is intended that the present invention is not limited to the modalities and illustrations contained herein, but includes modified forms of these modalities including portions of the modalities and combinations of elements of different modalities, as come within the scope of the following claims.
    权利要求:
    Claims (17)
    [1]
    1. Method for booting a device having at least two independent co-existing operating system environments characterized by the fact that it comprises the following steps:
    start a start-up sequence;
    initialize a central core;
    identification of a device mode state;
    launch services common to a first operating system environment and a second operating system environment, in which the first and second operating systems operate at the central core instead of existing in a virtualization or emulation scheme;
    select a primary operating system environment from the first and second operating system environments based at least in part on the device mode state;
    launch startup scripts from the primary operating system environment, and launch startup scripts from a secondary operating system environment.
    [2]
    2. Method according to claim 1, characterized by the fact that the device boots both operating system environments in a start-up boot sequence, the second operating system environment being the primary operating system environment when the state of mode is personal computer.
    [3]
    3. Method, according to claim 1, characterized by the fact that the device boots at least two operating system environments in one
    Petition 870190105898, of 10/18/2019, p. 9/53 boot sequence, the first operating system environment to boot first when the mode state is identified as a mobile mode.
    [4]
    4. Method for booting an operating system, characterized by the fact that it comprises the following steps:
    initialize an initialization sequence;
    select at least two operating system environments to operate a mobile device, where the at least two operating system environments are configured to be independent and co-exist while the device is operational;
    launch a common core, in which at least two operating system environments operate on the common core instead of existing in a virtualization or emulation scheme;
    launch application services common to a first operating system environment and a second operating system environment from at least two operating system environments;
    select a primary and secondary operating system environment based at least in part on the device mode state, and simultaneously launch startup scripts for the primary and secondary operating system environments.
    [5]
    5. Method, according to claim 4, characterized by the fact that the first operating system environment is the primary environment.
    [6]
    6. Method, according to claim 4, characterized by the fact that the second environment of
    Petition 870190105898, of 10/18/2019, p. 10/53
    operational system is the primary environment. 7. Method, in wake up with the claim 6, characterized by fact that the state so is a way mobile.8. Method, in wake up with the claim 4, characterized by fact that also comprises the stage in start a secondary operating system application. 9. Method, in wake up with the claim 4, characterized by fact that the secondary environment is one
    mobile environment.
    [7]
    10. Method for operating a device having at least two operating system environments, characterized by the fact that it comprises:
    operate at least two operating system environments on a common core;
    where operating system environments do not exist in a virtualization or emulation scheme.
    [8]
    11. Method according to claim 10, characterized by the fact that the at least two operating system environments include a first operating system environment and a second operating system environment.
    [9]
    12. Method, according to claim 11, characterized by the fact that it further comprises:
    launch services common to the first operating system environment and the second operating system environment.
    [10]
    13. Method according to claim 12, characterized by the fact that one of the first and the second operating system environments is a primary operating system environment and the other of the first and
    Petition 870190105898, of 10/18/2019, p. 11/53 the second operating system environment is a secondary operating system environment.
    [11]
    14. Method according to claim 13, characterized in that the first operating system environment or the second operating system environment is the primary operating system environment dependent at least in part on a device mode state.
    [12]
    15. Method, according to claim 14, characterized by the fact that if the mode state of the device is an embedded mode, then the primary operating system environment is the second operating system environment, and in which the state of device mode is a mobile mode, then the primary operating system environment is the first operating system environment.
    [13]
    16. Method according to claim 15, characterized by the fact that specific primary environment services are launched before specific secondary environment services.
    [14]
    17. Method, according to claim 16, characterized by the fact that the launch of services common to the first and second operating system environments occurs separately from the launch of at least part of the primary and secondary specific environment services.
    [15]
    18. Method, according to claim 15, characterized by the fact that when the device is in the docked mode and a peripheral device is disconnected, there is an automatic switching to the mobile mode
    Petition 870190105898, of 10/18/2019, p. 12/53 so that the primary operating system environment becomes the secondary and vice versa operating system environment.
    [16]
    19. Method, according
    5 characterized by the fact of mobile device.
    [17]
    20. Method, according to the fact that with claim 14, that the device is one with claim 12, the at least two operating system environments are co-existent and independent.
    类似技术:
    公开号 | 公开日 | 专利标题
    BR112012000888B1|2019-12-17|method to boot and method to operate a device having at least two operating system environments
    BR112012001228B1|2020-11-03|method of operating a mobile computing device and mobile computing device
    US9348633B2|2016-05-24|Multi-environment operating system
    US9367331B2|2016-06-14|Multi-environment operating system
    US9389877B2|2016-07-12|Multi-environment operating system
    EP2668572B1|2015-12-09|Method and apparatus for locking and unlocking multiple operating system environments with a single gesture input
    US9152582B2|2015-10-06|Auto-configuration of a docked system in a multi-OS environment
    US20120173986A1|2012-07-05|Background synchronization within a multi-environment operating system
    KR101251710B1|2013-04-05|Boot negotiation among multiple boot-capable devices
    US20120174021A1|2012-07-05|Systems and methods for displaying android applications launchers in webtop application tray
    WO2012044557A2|2012-04-05|Auto-configuration of a docked system in a multi-os environment
    WO2011011368A2|2011-01-27|Multi-environment operating system
    Sun et al.2007|Supporting Multiple OSes with OS Switching.
    RU2574205C2|2016-02-10|Multi-environment operating system
    WO2011011365A2|2011-01-27|Multi-environment operating system
    同族专利:
    公开号 | 公开日
    US20110016301A1|2011-01-20|
    BR112012000888A2|2016-02-23|
    EP2457157A2|2012-05-30|
    MY165249A|2018-03-14|
    CN102473102A|2012-05-23|
    CN102473102B|2015-04-22|
    WO2011011356A3|2011-09-01|
    KR101399161B1|2014-05-27|
    WO2011011356A2|2011-01-27|
    KR20120030563A|2012-03-28|
    US9372711B2|2016-06-21|
    引用文献:
    公开号 | 申请日 | 公开日 | 申请人 | 专利标题
    AU578423B2|1983-07-25|1988-10-27|Mead Corporation, The|Thermal developing of microencapsulated photosensitive materials|
    US5191055A|1988-12-22|1993-03-02|Mitsui Toatsu Chemicals, Inc.|Mercapto compound, a high refractive index resin and lens and a process for preparing them|
    US5087758A|1988-12-22|1992-02-11|Mitsui Toatsu Chemicals, Inc.|Mercapto compound, a high refractive index resin and lens and a process for preparing them|
    US5119494A|1990-07-10|1992-06-02|Athenix Corporation|Application address display window mapper for a sharable ms-dos processor|
    US5446904A|1991-05-17|1995-08-29|Zenith Data Systems Corporation|Suspend/resume capability for a protected mode microprocessor|
    AU634932B1|1991-08-08|1993-03-04|Mitsui Chemicals, Inc.|Mercapto compound, its preparation process, and sulfur- containing urethane resins and lenses using the same|
    EP0568386A3|1992-05-01|1995-08-16|R Brent Johnson|Console simulator, multi-console management system, and console management distribution system|
    JPH07121336A|1993-10-27|1995-05-12|Canon Inc|Method and device for display|
    US5608115A|1994-01-26|1997-03-04|Mitsui Toatsu Chemicals, Inc.|Polythiol useful for preparing sulfur-containing urethane-based resin and process for producing the same|
    EP0717344B1|1994-12-13|2001-10-31|Microsoft Corporation|Taskbar with start menu|
    US6363409B1|1995-04-24|2002-03-26|Microsoft Corporation|Automatic client/server translation and execution of non-native applications|
    US6336146B1|1995-12-22|2002-01-01|Sun Microsystems, Inc.|Method and apparatus for docking, launching and running applications in a foreign environment|
    US5828376A|1996-09-23|1998-10-27|J. D. Edwards World Source Company|Menu control in a graphical user interface|
    DE19648422C2|1996-11-22|2000-03-30|Hans Beckhoff|Method and device for implementing a real-time capable control program in a non-real-time capable operating program|
    US6710788B1|1996-12-03|2004-03-23|Texas Instruments Incorporated|Graphical user interface|
    US6170045B1|1997-04-30|2001-01-02|International Business Machines Corporation|Cross-system data piping using an external shared memory|
    US6336120B1|1997-08-26|2002-01-01|International Business Machines Corporation|Method and system for supporting hierarchical storage management file system across multiple platforms|
    US6205452B1|1997-10-29|2001-03-20|R. R. Donnelley & Sons Company|Method of reproducing variable graphics in a variable imaging system|
    US6215490B1|1998-02-02|2001-04-10|International Business Machines Corporation|Task window navigation method and system|
    US6043816A|1998-05-29|2000-03-28|Hewlett-Packard Company|User interface mechanism for maintaning quick access to important information in a windows-based computer environment|
    US6133915A|1998-06-17|2000-10-17|Microsoft Corporation|System and method for customizing controls on a toolbar|
    US6338149B1|1998-07-31|2002-01-08|Westinghouse Electric Company Llc|Change monitoring system for a computer system|
    US6178503B1|1998-09-11|2001-01-23|Powerquest Corporation|Managing multiple operating systems on a single computer|
    US8065504B2|1999-01-28|2011-11-22|Ati International Srl|Using on-chip and off-chip look-up tables indexed by instruction address to control instruction execution in a processor|
    US6691146B1|1999-05-19|2004-02-10|International Business Machines Corporation|Logical partition manager and method|
    JP2000347883A|1999-06-03|2000-12-15|Matsushita Electric Ind Co Ltd|Virtual computer device|
    US6460136B1|1999-07-12|2002-10-01|Hewlett-Packard Co.,|Method and apparatus for loading an operating system kernel from a shared disk memory|
    US6571282B1|1999-08-31|2003-05-27|Accenture Llp|Block-based communication in a communication services patterns environment|
    US6763458B1|1999-09-27|2004-07-13|Captaris, Inc.|System and method for installing and servicing an operating system in a computer or information appliance|
    US6757002B1|1999-11-04|2004-06-29|Hewlett-Packard Development Company, L.P.|Track pad pointing device with areas of specialized function|
    US6756999B2|2000-04-06|2004-06-29|Microsoft Corporation|Method and system for clustering and grouping taskbar buttons|
    GB2369959A|2000-12-08|2002-06-12|Ubinetics Ltd|Holder for connecting a mobile communications device to a screen|
    GB2377518B|2001-02-12|2003-10-22|Altio Ltd|Client software enabling a client to run a network based application|
    US7461144B1|2001-02-16|2008-12-02|Swsoft Holdings, Ltd.|Virtual private server with enhanced security|
    US6765596B2|2001-02-27|2004-07-20|International Business Machines Corporation|Multi-functional application launcher with integrated status|
    US7231531B2|2001-03-16|2007-06-12|Dualcor Technologies, Inc.|Personal electronics device with a dual core processor|
    US20020151334A1|2001-04-11|2002-10-17|Motorola, Inc|Communications device with call frequency analyzer|
    TW502210B|2001-04-19|2002-09-11|Asustek Comp Inc|Computer system capable of switching operating system|
    US20050240763A9|2001-08-06|2005-10-27|Shivaram Bhat|Web based applications single sign on system and method|
    CA2669171C|2001-09-26|2012-05-01|Interact Devices|System and method for communicating media signals|
    US20030065738A1|2001-10-01|2003-04-03|Thumb Logic, Inc.|Wireless information systems and methods|
    JP2003196096A|2001-12-07|2003-07-11|Internatl Business Mach Corp <Ibm>|Computer system, its starting control method and program|
    US7533101B2|2002-03-04|2009-05-12|Microsoft Corporation|Extensible loader|
    EP1347373A3|2002-03-20|2005-02-02|Seiko Epson Corporation|Apparatus for processing instructions of different instruction set architectures|
    US7783665B1|2002-03-27|2010-08-24|Parallels Holdings, Ltd.|Effective file-sharing among virtual environments|
    US7424623B2|2002-03-28|2008-09-09|O2 Micro International Limited|Personal computer integrated with personal digital assistant|
    US20030204708A1|2002-04-24|2003-10-30|Colin Hulme|Portable computer having hierarchical operating systems|
    US20070128899A1|2003-01-12|2007-06-07|Yaron Mayer|System and method for improving the efficiency, comfort, and/or reliability in Operating Systems, such as for example Windows|
    US20050240756A1|2003-01-12|2005-10-27|Yaron Mayer|System and method for improving the efficiency, comfort, and/or reliability in Operating Systems, such as for example Windows.|
    US7111303B2|2002-07-16|2006-09-19|International Business Machines Corporation|Virtual machine operating system LAN|
    JP2004086330A|2002-08-23|2004-03-18|Toshiba Corp|Electronic apparatus|
    TW591398B|2002-09-26|2004-06-11|Tatung Co|Method of implementing a plurality of system tray areas|
    US7913183B2|2002-10-08|2011-03-22|Microsoft Corporation|System and method for managing software applications in a graphical user interface|
    US20040095388A1|2002-11-15|2004-05-20|Rocchetti Robert J.|Method and apparatus for creating user interfaces for computing devices|
    US7254831B2|2002-12-04|2007-08-07|Microsoft Corporation|Sharing a sign-in among software applications having secured features|
    US7114104B1|2003-02-11|2006-09-26|Compuware Corporation|System and method of fault detection in a Unix environment|
    ES2315469T3|2003-04-09|2009-04-01|Virtuallogix Sa|OPERATING SYSTEMS.|
    US20040207508A1|2003-04-16|2004-10-21|Jyh-Han Lin|Method and apparatus for a dynamically customizable smart phonebook|
    US7634770B2|2003-05-19|2009-12-15|Hewlett-Packard Development Company, L.P.|Kernel module interface dependencies|
    WO2005043862A1|2003-10-29|2005-05-12|Qualcomm Incorporated|High data rate interface|
    US7620667B2|2003-11-17|2009-11-17|Microsoft Corporation|Transfer of user profiles using portable storage devices|
    US20050125739A1|2003-11-20|2005-06-09|Thompson Jeffrey W.|Virtual desktop manager system and method|
    US7788487B2|2003-11-28|2010-08-31|Panasonic Corporation|Data processing apparatus|
    JP4617683B2|2004-02-24|2011-01-26|ソニー株式会社|Semiconductor integrated circuit, portable module, and message communication method.|
    GB0407977D0|2004-04-08|2004-05-12|Ibm|Communication between browser windows|
    US7478204B2|2004-04-29|2009-01-13|International Business Machines Corporation|Efficient sharing of memory between applications running under different operating systems on a shared hardware system|
    US7543166B2|2004-05-12|2009-06-02|Intel Corporation|System for managing power states of a virtual machine based on global power management policy and power management command sent by the virtual machine|
    US7590945B2|2004-06-14|2009-09-15|At&T Intellectual Property I, L.P.|Viewing applications from inactive sessions|
    KR101013143B1|2004-06-29|2011-02-10|삼성전자주식회사|Management system of monitor|
    US7996785B2|2004-06-30|2011-08-09|Microsoft Corporation|Systems and methods for integrating application windows in a virtual machine environment|
    US20060010446A1|2004-07-06|2006-01-12|Desai Rajiv S|Method and system for concurrent execution of multiple kernels|
    US7424601B2|2004-07-07|2008-09-09|Yongyong Xu|Methods and systems for running multiple operating systems in a single mobile device|
    US20060046706A1|2004-08-26|2006-03-02|Jiansong Lin|Monitoring and remote control of wireless communication device accessories and functionality|
    US7363128B2|2004-09-28|2008-04-22|Eaton Corporation|Application launcher|
    US7529921B2|2004-12-17|2009-05-05|Cardiac Pacemakers, Inc.|Fast initialization of medical device system having multiple operating systems|
    US7468729B1|2004-12-21|2008-12-23|Aol Llc, A Delaware Limited Liability Company|Using an avatar to generate user profile information|
    US8274518B2|2004-12-30|2012-09-25|Microsoft Corporation|Systems and methods for virtualizing graphics subsystems|
    US20070162298A1|2005-01-18|2007-07-12|Apple Computer, Inc.|Systems and methods for presenting data items|
    US20060225107A1|2005-04-01|2006-10-05|Microsoft Corporation|System for running applications in a resource-constrained set-top box environment|
    US7478339B2|2005-04-01|2009-01-13|Microsoft Corporation|Method and apparatus for application window grouping and management|
    US7565535B2|2005-05-06|2009-07-21|Microsoft Corporation|Systems and methods for demonstrating authenticity of a virtual machine using a security image|
    US7533189B2|2005-06-21|2009-05-12|Microsoft Corporation|Enabling a graphical window modification command to be applied to a remotely generated graphical window|
    US8195624B2|2005-06-30|2012-06-05|Phoenix Technologies Ltd.|Shared file system management between independent operating systems|
    JP4784189B2|2005-07-26|2011-10-05|ソニー株式会社|COMMUNICATION SYSTEM, INFORMATION PROCESSING DEVICE AND INFORMATION PROCESSING METHOD, INFORMATION TERMINAL DEVICE, INFORMATION PROCESSING METHOD, AND PROGRAM|
    US20070050765A1|2005-08-30|2007-03-01|Geisinger Nile J|Programming language abstractions for creating and controlling virtual computers, operating systems and networks|
    US8429630B2|2005-09-15|2013-04-23|Ca, Inc.|Globally distributed utility computing cloud|
    US7779280B2|2005-09-16|2010-08-17|Gary Stephen Shuster|Low power mode for portable computer system|
    US7636586B2|2005-10-12|2009-12-22|Nokia Corporation|Mobile communication terminal|
    US20070135043A1|2005-12-12|2007-06-14|Motorola, Inc.|Method and system for accessible contact information on a locked electronic device|
    US7657849B2|2005-12-23|2010-02-02|Apple Inc.|Unlocking a device by performing gestures on an unlock image|
    WO2007083299A2|2006-01-17|2007-07-26|Kidaro Ltd.|Seamless integration of multiple computing environments|
    US20070174429A1|2006-01-24|2007-07-26|Citrix Systems, Inc.|Methods and servers for establishing a connection between a client system and a virtual machine hosting a requested computing environment|
    US20070180398A1|2006-01-30|2007-08-02|Mcardle James M|Window cleanup via desktop icon|
    JP2007226413A|2006-02-22|2007-09-06|Hitachi Ltd|Memory dump method, memory dump program and computer system|
    US7595810B2|2006-03-22|2009-09-29|Apple Inc.|Methods of manipulating a screen space of a display device|
    US7536537B2|2006-04-20|2009-05-19|Harris Corporation|Simultaneous dual booting of platforms|
    US7987432B1|2006-04-25|2011-07-26|Parallels Holdings, Ltd.|Seamless integration and installation of non-native application into native operating system|
    US20070266231A1|2006-05-15|2007-11-15|Huey-Tyug Chua|Portable Electronic Device and Method for Loading Resource Data of the Portable Electronic Device|
    JP2009537892A|2006-05-18|2009-10-29|サンギュ イ|How to protect clients and servers|
    US20070283147A1|2006-05-30|2007-12-06|Fried Eric P|System and method to manage device access in a software partition|
    US9201703B2|2006-06-07|2015-12-01|International Business Machines Corporation|Sharing kernel services among kernels|
    US8146089B2|2006-06-14|2012-03-27|Intel Corporation|Sharing resources of a partitioned system|
    US20080028326A1|2006-07-26|2008-01-31|Research In Motion Limited|System and method for adaptive theming of a mobile device|
    US8352733B2|2006-08-04|2013-01-08|Apple Inc.|Resource restriction systems and methods|
    US7996789B2|2006-08-04|2011-08-09|Apple Inc.|Methods and apparatuses to control application programs|
    US7689820B2|2006-09-27|2010-03-30|L3 Communications Corporation|Rapid-boot computing device with dual operating systems|
    US20080100568A1|2006-10-30|2008-05-01|Koch Paul B|Electronic device providing tactile feedback|
    US7698660B2|2006-11-13|2010-04-13|Microsoft Corporation|Shared space for communicating information|
    JP4809209B2|2006-12-28|2011-11-09|株式会社日立製作所|System switching method and computer system in server virtualization environment|
    US8046570B2|2007-02-06|2011-10-25|Microsoft Corporation|Supporting multiple operating systems in media devices|
    US20080282205A1|2007-02-06|2008-11-13|Access Systems Americas, Inc.|Unified launcher user interface system and method for integrating multiple disparate environments on an electronic device|
    US20080256468A1|2007-04-11|2008-10-16|Johan Christiaan Peters|Method and apparatus for displaying a user interface on multiple devices simultaneously|
    US20080270910A1|2007-04-30|2008-10-30|Lukasik Derek J|User selection of a remote session|
    WO2008137432A2|2007-05-01|2008-11-13|Dyyno|Sharing of information and formatting information for transmission over a communication network|
    US8677270B2|2007-05-04|2014-03-18|Microsoft Corporation|Live companion user interface|
    CN100470485C|2007-05-09|2009-03-18|浙江大学|Method for realizing multiple operation system synergistic working|
    US8745535B2|2007-06-08|2014-06-03|Apple Inc.|Multi-dimensional desktop|
    US20080307350A1|2007-06-09|2008-12-11|Alessandro Francesco Sabatelli|Method and Apparatus for Improved Desktop Arrangement|
    US7523738B2|2007-06-22|2009-04-28|Gm Global Technology Operations, Inc.|Idle quality by torque smoothing|
    KR101415762B1|2007-07-25|2014-07-08|엘지전자 주식회사|Auxiliary output apparatus, Portable computer having auxiliary output apparatus and Changing method of Operating Systerm thereof|
    TWI362612B|2007-09-05|2012-04-21|Htc Corp|System and electronic device using multiple operating systems and operating method thereof|
    TWI352909B|2007-09-05|2011-11-21|Htc Corp|Method and system for supporting network sharing a|
    WO2009039384A2|2007-09-20|2009-03-26|C & S Operations, Inc.|Computer system with multiple terminals|
    US7840186B2|2007-09-25|2010-11-23|Motorola Mobility, Inc.|Wireless SATA/SAS data transfer system|
    US9003173B2|2007-09-28|2015-04-07|Microsoft Technology Licensing, Llc|Multi-OS boot via mobile device|
    US20090158299A1|2007-10-31|2009-06-18|Carter Ernst B|System for and method of uniform synchronization between multiple kernels running on single computer systems with multiple CPUs installed|
    CN101149685A|2007-11-07|2008-03-26|苏州壹世通科技有限公司|Combined device and method for starting up multiple operation system from mobile memory apparatus|
    JP2009157802A|2007-12-27|2009-07-16|Kyocera Corp|Portable terminal and information processor|
    US9612847B2|2008-02-05|2017-04-04|Microsoft Technology Licensing, Llc|Destination list associated with an application launcher|
    US8151100B2|2008-02-06|2012-04-03|Broadcom Corporation|Operating system for a computing device with handheld and extended computing units|
    US8327286B2|2008-03-13|2012-12-04|Microsoft Corporation|Unifying application launchers and switchers|
    US20090287571A1|2008-03-26|2009-11-19|Robb Fujioka|Hypervisor and virtual machine ware|
    GB2459097B|2008-04-08|2012-03-28|Advanced Risc Mach Ltd|A method and apparatus for processing and displaying secure and non-secure data|
    US8468533B2|2008-04-28|2013-06-18|Panasonic Corporation|Virtual machine control device, method, and program wherein a switching task used to switch to the highest priority virtual machines is the highest priority task in the current virtual machine and the virtual machine that is the switching target|
    CN101615123A|2008-06-26|2009-12-30|比亚迪股份有限公司|A kind of bootstrap technique of mobile terminal operating system and portable terminal|
    US8307177B2|2008-09-05|2012-11-06|Commvault Systems, Inc.|Systems and methods for management of virtualization data|
    US20100064251A1|2008-09-05|2010-03-11|International Business Machines Corporation|Toggling window display state by screen in a multi-screened desktop environment|
    US8694920B2|2008-09-25|2014-04-08|Microsoft Corporation|Displaying application information in an application-switching user interface|
    JP5520305B2|2008-09-29|2014-06-11|フィッシャー−ローズマウントシステムズ，インコーポレイテッド|How to set process control preferences|
    KR101501167B1|2008-10-20|2015-03-10|삼성전자주식회사|Apparatus and method for application of multi operating systems in multi modem mobile communication terminal|
    US8819585B2|2008-10-27|2014-08-26|Microsoft Corporation|Child window surfacing and management|
    US8069247B2|2008-12-03|2011-11-29|Verizon Data Services Llc|Application launcher systems, methods, and apparatuses|
    US9459678B2|2009-01-29|2016-10-04|Hewlett-Packard Development Company, L.P.|Power manager for virtual machines|
    US20100211769A1|2009-02-19|2010-08-19|Subramonian Shankar|Concurrent Execution of a Smartphone Operating System and a Desktop Operating System|
    US7987309B2|2009-02-26|2011-07-26|Broadcom Corporation|Dockable handheld computing device with graphical user interface and methods for use therewith|
    US8566045B2|2009-03-16|2013-10-22|Apple Inc.|Event recognition|
    US8253531B2|2009-03-26|2012-08-28|International Business Machines Corporation|On chip verification and consequent enablement of card OS operation in smart cards|
    US8177554B2|2009-06-02|2012-05-15|Krasner Paul R|Device and method for locating a pulp chamber in a tooth|
    US8621387B2|2009-06-08|2013-12-31|Apple Inc.|User interface for multiple display regions|
    TWI400652B|2009-06-11|2013-07-01|Insyde Software Corp|Dual operating system parallel processing methods, recording media and computer program products|
    US8881047B2|2009-06-19|2014-11-04|Moment Usa, Inc.|Systems and methods for dynamic background user interface|
    US8914511B1|2009-06-26|2014-12-16|VMTurbo, Inc.|Managing resources in virtualization systems|
    US8302094B2|2009-06-26|2012-10-30|Vmware, Inc.|Routing a physical device request using transformer stack to an equivalent physical device in a virtualized mobile device|
    US9367331B2|2009-07-20|2016-06-14|Google Technology Holdings LLC|Multi-environment operating system|
    US8868899B2|2009-07-20|2014-10-21|Motorola Mobility Llc|System and method for switching between environments in a multi-environment operating system|
    US9389877B2|2009-07-20|2016-07-12|Google Technology Holdings LLC|Multi-environment operating system|
    US9348633B2|2009-07-20|2016-05-24|Google Technology Holdings LLC|Multi-environment operating system|
    JP5365399B2|2009-07-27|2013-12-11|富士通株式会社|Screen saver control system, image processing apparatus, image display apparatus, screen saver control method, and computer program|
    CA2675666A1|2009-08-27|2009-11-05|Ibm Canada Limited - Ibm Canada Limitee|Accelerated execution for emulated environments|
    US8341268B2|2009-08-28|2012-12-25|Microsoft Corporation|Resource sharing in multi-principal browser|
    US8607082B2|2009-08-31|2013-12-10|Red Hat Israel, Ltd.|Mechanism for managing power in a virtual machine system|
    US8341558B2|2009-09-16|2012-12-25|Google Inc.|Gesture recognition on computing device correlating input to a template|
    WO2011060382A1|2009-11-13|2011-05-19|Google Inc.|Live wallpaper|
    KR101620058B1|2009-11-23|2016-05-24|삼성전자주식회사|Apparatus for switching screen between virtual machines and method thereof|
    US8769428B2|2009-12-09|2014-07-01|Citrix Systems, Inc.|Methods and systems for generating a combined display of taskbar button group entries generated on a local machine and on a remote machine|
    US8538741B2|2009-12-15|2013-09-17|Ati Technologies Ulc|Apparatus and method for partitioning a display surface into a plurality of virtual display areas|
    US9367341B2|2010-03-30|2016-06-14|Red Hat Israel, Ltd.|Encrypting and decrypting virtual disk content using a single user sign-on|
    US8589952B2|2010-06-30|2013-11-19|Palm, Inc.|Dual operating system operation and configuration|
    CN102971740B|2010-07-01|2016-01-27|惠普发展公司，有限责任合伙企业|The user management framework for multiple environment on computing equipment|
    WO2012012865A1|2010-07-29|2012-02-02|9227-5668 Quebec Inc.|Portable catalytic heating apparatus for drying, curing, polymerization or cross-linking of coatings and compounds|
    EP2416546A1|2010-08-03|2012-02-08|Research In Motion Limited|Method for providing indication of communicatively coupled device|
    TWI520069B|2010-08-11|2016-02-01|緯創資通股份有限公司|Application method for integrating heterogeneous operating systems based on the same system kernel|
    US8620372B2|2010-09-30|2013-12-31|Apple Inc.|Method and apparatus for transport format selection in a mobile wireless device|
    WO2012044539A2|2010-10-01|2012-04-05|Imerj, Llc|Multi-operating system|
    US9152582B2|2010-10-01|2015-10-06|Z124|Auto-configuration of a docked system in a multi-OS environment|
    EP2625816B1|2010-10-08|2017-11-29|Lumi Technologies Limited|Scalable synchronization of events among server and clients with varying lag-times|
    US8983536B2|2010-10-22|2015-03-17|Google Technology Holdings LLC|Resource management in a multi-operating environment|
    US9245047B2|2010-12-10|2016-01-26|Wyse Technology L.L.C.|Methods and systems for facilitating a remote desktop session utilizing a remote desktop client common interface|
    US8874665B2|2010-12-13|2014-10-28|At&T Mobility Ii Llc|Systems, apparatus and methods for facilitating display and management of information for communication devices|
    US20120174021A1|2011-01-04|2012-07-05|Motorola, Inc.|Systems and methods for displaying android applications launchers in webtop application tray|
    US20120173986A1|2011-01-04|2012-07-05|Motorola-Mobility, Inc.|Background synchronization within a multi-environment operating system|
    US8782258B2|2011-01-04|2014-07-15|Motorola Mobility Llc|Transferring web data between operating system environments|
    US20120192100A1|2011-01-25|2012-07-26|Motorola-Mobility, Inc.|Method and apparatus for locking and unlocking multiple operating system environments with a single gesture input|
    US9891939B2|2011-03-03|2018-02-13|Microsoft Technology Licensing, Llc|Application compatibility with library operating systems|
    US8898629B2|2011-04-06|2014-11-25|Media Direct, Inc.|Systems and methods for a mobile application development and deployment platform|
    US9354900B2|2011-04-28|2016-05-31|Google Technology Holdings LLC|Method and apparatus for presenting a window in a system having two operating system environments|
    US20120278747A1|2011-04-28|2012-11-01|Motorola Mobility, Inc.|Method and apparatus for user interface in a system having two operating system environments|
    US9104307B2|2011-05-27|2015-08-11|Microsoft Technology Licensing, Llc|Multi-application environment|
    US20130293573A1|2012-05-02|2013-11-07|Motorola Mobility, Inc.|Method and Apparatus for Displaying Active Operating System Environment Data with a Plurality of Concurrent Operating System Environments|
    US20130298140A1|2012-05-02|2013-11-07|Motorola Mobility, Inc.|Method and Apparatus for Displaying Data from a Plurality of Concurrent Operating System Environments|
    US9342325B2|2012-05-17|2016-05-17|Google Technology Holdings LLC|Synchronizing launch-configuration information between first and second application environments that are operable on a multi-modal device|US9348633B2|2009-07-20|2016-05-24|Google Technology Holdings LLC|Multi-environment operating system|
    US9389877B2|2009-07-20|2016-07-12|Google Technology Holdings LLC|Multi-environment operating system|
    US9367331B2|2009-07-20|2016-06-14|Google Technology Holdings LLC|Multi-environment operating system|
    US8868899B2|2009-07-20|2014-10-21|Motorola Mobility Llc|System and method for switching between environments in a multi-environment operating system|
    US8966379B2|2010-10-01|2015-02-24|Z124|Dynamic cross-environment application configuration/orientation in an active user environment|
    US8933949B2|2010-10-01|2015-01-13|Z124|User interaction across cross-environment applications through an extended graphics context|
    US9052800B2|2010-10-01|2015-06-09|Z124|User interface with stacked application management|
    US9047102B2|2010-10-01|2015-06-02|Z124|Instant remote rendering|
    WO2012044539A2|2010-10-01|2012-04-05|Imerj, Llc|Multi-operating system|
    US8726294B2|2010-10-01|2014-05-13|Z124|Cross-environment communication using application space API|
    US8819705B2|2010-10-01|2014-08-26|Z124|User interaction support across cross-environment applications|
    US9152582B2|2010-10-01|2015-10-06|Z124|Auto-configuration of a docked system in a multi-OS environment|
    US8761831B2|2010-10-15|2014-06-24|Z124|Mirrored remote peripheral interface|
    US8983536B2|2010-10-22|2015-03-17|Google Technology Holdings LLC|Resource management in a multi-operating environment|
    KR101295393B1|2011-01-27|2013-08-09|주식회사 엘지씨엔에스|Smart settop box and operating method for smart service and digital television service using single operating system|
    US9354900B2|2011-04-28|2016-05-31|Google Technology Holdings LLC|Method and apparatus for presenting a window in a system having two operating system environments|
    US8842057B2|2011-09-27|2014-09-23|Z124|Detail on triggers: transitional states|
    US9396041B2|2012-02-01|2016-07-19|Google Technology Holdings LLC|Optimization of resource usage in a multi-environment computing system|
    US8615766B2|2012-05-01|2013-12-24|Concurix Corporation|Hybrid operating system|
    US20130293573A1|2012-05-02|2013-11-07|Motorola Mobility, Inc.|Method and Apparatus for Displaying Active Operating System Environment Data with a Plurality of Concurrent Operating System Environments|
    US9342325B2|2012-05-17|2016-05-17|Google Technology Holdings LLC|Synchronizing launch-configuration information between first and second application environments that are operable on a multi-modal device|
    DE102013212016A1|2013-06-25|2015-01-08|Robert Bosch Gmbh|Method for operating a communication arrangement|
    WO2015139246A1|2014-03-19|2015-09-24|华为终端有限公司|Method and device for synchronizing application data|
    KR101532873B1|2014-04-11|2015-06-30|플러스기술주식회사|Method for running dual operating system of smartphone|
    CN103927260B|2014-04-22|2016-09-14|中国移动（深圳）有限公司|A kind of telecommunication apparatus method of testing and system|
    KR20160006482A|2014-07-09|2016-01-19|에스케이하이닉스 주식회사|Semiconductor device|
    CN105404547A|2014-09-12|2016-03-16|阿里巴巴集团控股有限公司|Fusion method and device of operating system|
    US9628279B2|2014-09-30|2017-04-18|Microsoft Technology Licensing, Llc|Protecting application secrets from operating system attacks|
    US9619242B2|2014-12-23|2017-04-11|Intel Corporation|Methods, systems and apparatus to initialize a platform|
    CN104618596A|2015-01-30|2015-05-13|深圳酷派技术有限公司|System control method and device and terminal|
    US10084867B1|2015-02-10|2018-09-25|Open Invention Network, Llc|Location awareness assistant for switching between a business profile mode and a personal profile mode|
    CN108024002B|2016-10-31|2021-05-07|成都卫士通信息产业股份有限公司|Method for constructing dual-domain mobile phone system based on ROM|
    KR20190085402A|2018-01-10|2019-07-18|삼성전자주식회사|Electronic apparatus and control method thereof|
    CN111796877B|2020-07-14|2021-10-15|北京元心科技有限公司|Starting method of operating system, electronic device and computer readable storage medium|
    法律状态:
    2016-11-16| B25D| Requested change of name of applicant approved|Owner name: MOTOROLA MOBILITY LLC (US) |
    2016-11-29| B25G| Requested change of headquarter approved|Owner name: MOTOROLA MOBILITY LLC (US) |
    2016-12-13| B25A| Requested transfer of rights approved|Owner name: GOOGLE TECHNOLOGY HOLDINGS LLC (US) |
    2019-01-15| B06F| Objections, documents and/or translations needed after an examination request according [chapter 6.6 patent gazette]|
    2019-07-23| B06U| Preliminary requirement: requests with searches performed by other patent offices: procedure suspended [chapter 6.21 patent gazette]|
    2019-11-26| B09A| Decision: intention to grant [chapter 9.1 patent gazette]|
    2019-12-17| B16A| Patent or certificate of addition of invention granted|Free format text: PRAZO DE VALIDADE: 20 (VINTE) ANOS CONTADOS A PARTIR DE 20/07/2010, OBSERVADAS AS CONDICOES LEGAIS. |
    优先权:
    申请号 | 申请日 | 专利标题
    US22697409P| true| 2009-07-20|2009-07-20|
    US12/838,668|US9372711B2|2009-07-20|2010-07-19|System and method for initiating a multi-environment operating system|
    PCT/US2010/042516|WO2011011356A2|2009-07-20|2010-07-20|System and method for initiating a multi-environment operating system|
    [返回顶部]