WO2013023440A1 - 一种应用管理方法及设备 - Google Patents

一种应用管理方法及设备 Download PDF

Info

Publication number
WO2013023440A1
WO2013023440A1 PCT/CN2012/001083 CN2012001083W WO2013023440A1 WO 2013023440 A1 WO2013023440 A1 WO 2013023440A1 CN 2012001083 W CN2012001083 W CN 2012001083W WO 2013023440 A1 WO2013023440 A1 WO 2013023440A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
electronic device
list
unit
request
Prior art date
Application number
PCT/CN2012/001083
Other languages
English (en)
French (fr)
Inventor
许威
邓启明
陈冬
王晟
黄世光
刘清
陈燕霞
Original Assignee
联想(北京)有限公司
北京联想软件有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from CN2011102338521A external-priority patent/CN102938703A/zh
Priority claimed from CN2011102607744A external-priority patent/CN102981914A/zh
Priority claimed from CN201110314486.2A external-priority patent/CN103049457B/zh
Priority claimed from CN201110337685.5A external-priority patent/CN103092635B/zh
Priority claimed from CN201110338645.2A external-priority patent/CN103092721B/zh
Application filed by 联想(北京)有限公司, 北京联想软件有限公司 filed Critical 联想(北京)有限公司
Priority to US14/239,186 priority Critical patent/US9779106B2/en
Publication of WO2013023440A1 publication Critical patent/WO2013023440A1/zh

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10File systems; File servers
    • G06F16/17Details of further file system functions
    • G06F16/178Techniques for file synchronisation in file systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/61Installation
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/451Execution arrangements for user interfaces
    • G06F9/452Remote windowing, e.g. X-Window System, desktop virtualisation

Definitions

  • the present application relates to the field of communications technologies, and in particular, to an application management method and device. Furthermore, the present law relates to the field of electronic devices, and more particularly, to a synchronization method and an electronic device. Furthermore, the invention relates to an associated method, an electronic device and a hybrid system. Furthermore, the present invention relates to an application backup method, an electronic device and a system. Background technique
  • Hybrid system which means that two (including two) systems are combined, for example, based on an existing system, embedded in at least one other system (including another PC system or embedded system, etc.) Different systems can work together, share information and equipment, and take advantage of their respective advantages.
  • client softwares for electronic devices such as computers and mobile phones.
  • client software For electronic devices such as computers and mobile phones.
  • users need to back up certain applications of a certain client software, they can first install the client software on the electronic device, such as Android, and then find the applications in the software that need to be backed up, and then back up the applications to the local device. .
  • the embodiment of the present application provides an application management method and device, which solves the problem that the existing hybrid system portable terminal is difficult to call the slave system application under the control of the main system, resulting in a decrease in user experience.
  • An application management method is applied to a first device connected to a second device, where the method includes: mapping at least one application in the second device to obtain a corresponding At least one application identifier; detecting the first operation; determining, when the first operation meets the first preset condition, the application identifier of the first application from the at least one application identifier; detecting the second operation; and when the second operation satisfies the second preset
  • the condition is obtained, the corresponding application management command is obtained according to the second operation, and the application management command is sent to the second device, so that the second device manages the first application according to the application management command.
  • An application management device where the application management device is connected to the second device, the first device includes: a mapping unit, configured to map at least one application in the second device, to obtain a corresponding at least one application identifier; a detecting unit, configured to detect a first operation, where the determining unit is configured to determine an application identifier of the first application from the at least one application identifier when the first operation meets the first preset condition, and the second detecting unit is configured to detect And a management unit, configured to: when the second operation meets the second preset condition, obtain a corresponding application management command according to the second operation, and send an application management command to the second device, so that the second device is configured according to the application management command. , managing the first application.
  • the first device is connected to the second device, and the first device maps the at least one application in the second device to obtain the corresponding at least one application identifier, and detects the first operation, when the first device is used.
  • the application identifier of the first application is determined from the at least one application identifier, and the second operation is detected.
  • the second operation meets the second preset condition, the corresponding application management command is obtained according to the second operation. And sending an application management command to the second device, so that The second device manages the first application according to the application management command.
  • the application in the second device can be managed by the first device.
  • the application in the second device When the two devices work together, when the application in the second device is to be used, there is no need to switch to the second device separately. In the working state, the application of the second device can be managed in the first device, so that switching between applications of different devices can be realized, and the user experience of the portable terminal user using the hybrid system is improved.
  • mapping at least one of the second devices may include: detecting a data connection with the second electronic device, obtaining a detection result; and when the detection result indicates the first electronic device
  • mapping at least one of the second devices may include: detecting a data connection with the second electronic device, obtaining a detection result; and when the detection result indicates the first electronic device
  • the application list includes an application installed in the at least one second electronic device; and creating at least one corresponding to an application in the application list according to the application list
  • the application identifier where the application identifier is triggered, the application corresponding to the application identifier can be started in the second electronic device.
  • the electronic device may further include: a detecting unit configured to detect a data connection with the second electronic device to obtain a detection result; the mapping unit includes the following unit: the acquiring unit configured to indicate the electronic when the detection result When the data connection between the device and the second electronic device is successful, obtaining an application list from the second electronic device, the application list includes an application installed in the at least one second electronic device; and creating a unit configured to create at least one application according to the application list An application identifier corresponding to an application in the list, where the application identifier is triggered, and the application corresponding to the application identifier can be started in the second electronic device.
  • the application list of the application installed on the other electronic device can be conveniently obtained, and the application identifier corresponding to the application is created, so that the application installed on the other electronic device can be conveniently started.
  • the method further includes: according to the application list, the first electronic device associating the application in the application list with the corresponding file type in the first storage unit and/or the second storage unit file.
  • the method further includes: displaying a graphical user interface including an identifier corresponding to an application of the activatable file when the file stored in the first storage unit and the second storage unit is activated,
  • the application in which the file can be activated includes an application installed locally by the first electronic device and an application installed in the second electronic device.
  • the second electronic device includes a second storage unit, the electronic device further includes: a first storage unit configured to store various users and files; an association unit configured to associate according to the application list Application in the application list and first storage unit and / or second A file of the corresponding file type in the storage unit.
  • An electronic device further includes: a display unit configured to display a graphical user interface including an identifier corresponding to an application of the activatable file when the file stored in the first storage unit and the second storage unit is activated
  • the application in which the file can be activated includes an application installed locally by the electronic device and an application installed in the second electronic device.
  • a hybrid system including a first electronic device including a first hardware system having a first operating system, and a second electronic device including a second a second hardware system of the operating system, wherein the second electronic device comprises: a second storage unit configured to store various users and files, the first electronic device comprising: a first storage unit configured to store various users and files; a unit, configured to obtain a detection result, and an acquiring unit configured to obtain an application list from the second electronic device when the detection result satisfies a predetermined condition, the application list includes an application in the at least one second electronic device, and the second electronic device includes And a linking unit configured to associate the application in the application list with the file of the corresponding file type in the first storage unit and/or the second storage unit according to the application list.
  • the application management method further includes: receiving, by the second electronic device, a backup request sent by the first electronic device by using the communication port, where the backup request includes application information of the second client software that requests the backup;
  • the second electronic device searches for the application of the second client software that is requested to be backed up; the second electronic device sends the found application of the second client software to the first electronic device through the communication port, so that the first electronic device performs backup.
  • the electronic device further includes: a request receiving unit, configured to receive a first backup request sent by another electronic device through the communication port, where the first backup request includes a client in the electronic device requesting the backup Application information of the end software; an application search unit, configured to search for an application of the client software in the electronic device requested for backup; and an application sending unit, configured to send the found application to another electronic device through the communication port, so as to make another The electronic device is backed up.
  • an application backup system including: a first electronic device and a second electronic device, where the first electronic device is installed with the first client software, and the second electronic device The second client device is connected to the second electronic device, and the second electronic device is configured to receive a backup request sent by the first electronic device through the communication port, where the backup request includes requesting backup.
  • Application information of the second client software Finding an application of the second client software that is requested to be backed up; sending the found application of the second client software to the first electronic device through the communication port, so that the first electronic device performs backup.
  • the backup of the application between different client softwares can be directly completed without installing the entire client software. Quickly implement application backup, simplifying the operation process and improving backup efficiency.
  • the second electronic device has a display screen
  • the application management method may further include: when detecting that the first electronic device is connected to the second electronic device, transmitting, to the first electronic device, the connection indicating a first message: after receiving the first message, the first electronic device sets an attribute of the pre-installed application to be installable in a system interface with respect to the first electronic device; and the first electronic device receives the installed application from the user After the first operation command of the program, sending the application and the second command indicating the installation application to the second electronic device; after receiving the second command and the application, the second electronic device installs the application, and includes Transmitting, to the first electronic device, a second message for generating information of the icon of the application; after receiving the second message, the first electronic device generates an icon of the application on a display screen of the second electronic device, and the application is The properties of the icon are set to be runable and unloadable in the system interface.
  • an electronic device further includes: an embedded controller that, when detecting a connection with another electronic device, generates a first message indicating the connection and transmits an indication to the other electronic device a controller, configured to: after receiving the first message, set a property of the pre-installed application to be installable in the system interface with respect to the electronic device; receive a first operational command to install the application from the user Afterwards, the application and the second command indicating the installation of the application are sent to another electronic device; the second message containing the information for generating the icon of the application is received from the other electronic device; after receiving the second message, An icon of the application is generated on the display of another electronic device, and the properties of the icon of the application are set to be runable and unloadable in the system interface.
  • an electronic device further includes: a controller that receives a first message indicating a connection with another electronic device from an embedded controller of another electronic device; and receives an application from another electronic device a program and a second command instructing to install the application, wherein the property of the application is set to be installable in the system interface relative to another electronic device; after receiving the second command and the application, installing the application, and Sending a second message containing information for generating an icon of the application to another electronic device; wherein the other first electronic device is receiving the second consumer After the message, an icon of the application is generated on the display of the second electronic device, and the attributes of the icon of the application are set to be executable and unloadable in the system interface.
  • the installation, operation, and uninstallation of the application that needs to be installed in the second electronic device can be directly completed in the system interface of the operating system of the first electronic device, thereby improving the user's Convenience.
  • FIG. 1 is a flow chart of a first embodiment of an application management method of the present application
  • FIG. 2 is a flowchart of a second embodiment of an application management method according to the present application.
  • FIG. 3 is a flowchart of a third embodiment of an application management method of the present application.
  • FIG. 4 is a flowchart of a fourth embodiment of an application management method according to the present application.
  • FIG. 5 is a block diagram of a first embodiment of an application management device of the present application.
  • FIG. 6 is a block diagram of a second embodiment of an application management device of the present application.
  • FIG. 7 is a flowchart illustrating a synchronization method according to an embodiment of the present invention.
  • FIG. 8 is a block diagram illustrating a configuration of an electronic device according to an embodiment of the present invention.
  • FIG. 9 is a flow chart describing an association method in accordance with one embodiment of the present invention.
  • FIG. 10 is a block diagram depicting an electronic device in accordance with one embodiment of the present invention.
  • FIG. 11 is a flow chart describing an association method according to another embodiment of the present invention.
  • FIG. 12 is a block diagram depicting an electronic device in accordance with another embodiment of the present invention.
  • Figure 13 is a block diagram depicting a hybrid system in accordance with one embodiment of the present invention.
  • 16 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.
  • FIG. 17 is a schematic structural diagram of another electronic device according to an embodiment of the present invention.
  • FIG. 18 is a schematic structural diagram of an application backup system according to an embodiment of the present invention.
  • FIG. 19 is a schematic flowchart showing an operation method according to an embodiment of the present invention.
  • FIG. 20 is a schematic block diagram showing an electronic device according to an embodiment of the present invention
  • FIG. 21 is a schematic block diagram showing another electronic device according to an embodiment of the present invention. detailed description
  • the following embodiments of the present invention provide an application management method and device. These embodiments are applied in a first device connected to a second device.
  • a flow chart of a first embodiment of an application management method of the present application is as follows:
  • Step 101 Map at least one application in the second device to obtain a corresponding at least one application identifier.
  • the first device sends a request for acquiring the running application in the second device to the second device, and receives an application list returned by the second device according to the request, where the application list includes an application identifier of the running application of the second device; Or the first device sends a request for acquiring an application that is not running in the second device to the second device, and receives an application list that is returned by the second device according to the request, where the application list includes an application identifier of the second device that is not running the application; or The first device may also send a request for acquiring all applications in the second device to the second device, and receive a list of applications returned by the second device according to the request, where each application identifier in the application list may further include whether the corresponding application is Information that has been activated.
  • Step 102 Detect the first operation.
  • the first operation may be specifically an input operation performed by an input device, and the input device may include a mouse, a keyboard, a touchpad, etc., wherein the touchpad may be separately set or overlapped with the display unit to form a touch display.
  • Step 103 Determine, when the first operation meets the first preset condition, the application identifier of the first application from the at least one application identifier.
  • the first operation meets the first preset condition, and the operation target that is executed by the input device is the application identifier of the at least one application identifier, and the application identifier corresponding to the first operation is determined as the application identifier of the first application.
  • Step 104 Detect the second operation.
  • the second operation may be specifically an operation of applying an identifier of the first application by the input device, that is, an operation performed on the application identifier of the first application determined in the foregoing.
  • the input device can include a mouse, A keyboard, a touchpad, etc., wherein the touchpad can be set separately or overlapped with the display unit to form a touchscreen display.
  • Step 105 When the second operation satisfies the second preset condition, obtaining a corresponding application management command according to the second operation.
  • the second operation satisfies the second preset condition
  • the operation of the application identifier for the first application is an operation corresponding to the preset management command.
  • the management command may include, but is not limited to, a handover command, a shutdown command, a startup command, and the like corresponding to the first application.
  • Step 106 Send the application management command to the second device, so that the second device manages the first application according to the application management command.
  • the sending the application management command to the second device may include: sending, to the second device, a handover command to switch to the second state, to enable the second device to execute the first application in the second state; or sending the second device to the second device a closing command of the first application, so that the second device ends the process of the first application; or sending a startup command to start the first application to the second device, so that the second device starts the first application.
  • the application management method embodiment of the present application can be applied to the first device, and the first device is connected to the second device, such as a connected smart phone and a notebook computer; preferably, the connected two devices can form a dual-system portable terminal.
  • the first device includes a first hardware system, such as a hardware system based on an X86 architecture or an ARM architecture processor, running a first operating system, such as a desktop operating system (such as Windows, Linux, or MacOS) or a portable device operating system.
  • the second device includes a second hardware system, such as a hardware system based on an X86 architecture or an ARM architecture processor, running a second operating system, such as a desktop operating system (such as Windows, Linux or MacOS) Etc.) or a portable device operating system (such as Android, Symbian or iOS, etc.), wherein at least one application is installed in the second operating system of the second device.
  • a second hardware system such as a hardware system based on an X86 architecture or an ARM architecture processor
  • running a second operating system such as a desktop operating system (such as Windows, Linux or MacOS) Etc.) or a portable device operating system (such as Android, Symbian or iOS, etc.)
  • a portable device operating system such as Android, Symbian or iOS, etc.
  • the first device is a device based on an X86 architecture processor and running a Windows operating system
  • the second device is a device based on an ARM architecture processor and running an Android operating system
  • the first device is an X86-based processor and runs Windows operations.
  • the device of the system, the second device is a device based on an ARM architecture processor and running a Windows operating system (such as Windows 8).
  • the first device and the second device may be based on importance or priority or processing power or work
  • the difference between the two devices for example, the first device has high importance, high priority, high processing power, or high power consumption, and the second device is opposite to the above; or the second device corresponds to high importance and priority
  • High, high processing power or high power consumption, and the first device is the opposite of the above it can also be just for the distinction of naming, not limiting the importance or priority of the system or processing power or power consumption.
  • the first device further includes a display unit, the display unit displays a state in which the first operating system is running as a first state of the first device, and the display unit displays a state in which the second operating system is running as the first The second state of the device.
  • the first device is preferably a device including a host (including a first processing unit, such as an X86 processor) and a display screen, and may also be referred to as a BASE device, which is generally seen.
  • the notebook or the integrated machine has the same appearance, and the second device may preferably be a board integrated with an independent operating system (including a second processing unit, such as an ARM processor), which may also be called a PAD device, and the board passes the first a slot provided in the device, inserted into the slot, combined with the first device as a dual-system portable terminal;
  • the second device is preferably a display-free host device (including a second processor, such as an X86 processor), and the first device is preferably a touch display device (including a first processor, For example, the ARM processor), the second device is installed with the second operating system, the first device is installed with the first operating system, the first device is integrated with the display screen, and the first device and the second device are connected together to form a dual-system portable terminal, A device and a second device can be used separately or in combination.
  • a second device can be used separately or in combination.
  • FIG. 2 it is a flowchart of a second embodiment of an application management method according to the present application.
  • the embodiment shows an application management process for sending a handover command to a second device:
  • Step 201 The first device sends, in the first state, a request for acquiring an application that has been run in the second device to the second device.
  • the first device may send a request for acquiring the executed application in the second device to the second device by means of a wired (such as a data bus (USB/UART)) or a wireless (such as WIFI).
  • a wired such as a data bus (USB/UART)
  • a wireless such as WIFI
  • the BASE device may send a request to the second device by using a preset process (for example, a Hybrid Process).
  • Step 202 Receive an application list returned by the second device according to the request, where the application list includes an application identifier of the running application in the second device.
  • the second device After receiving the request, the second device can search for each application that has already run, and obtain a list of applications of the executed applications.
  • the PAD device can obtain a list of applications containing the application identifier of the running application through a preset process (for example, the PadAcitiManager process), and then return the application list to the BASE device by wire or wirelessly.
  • the BASE device may obtain the application list in the wired or wireless manner through the preset process to the PAD device.
  • the first device may display the application identifiers of all applications in the application list in a shortcut manner on the desktop corresponding to the first operating system, or list the applications.
  • the app IDs for all apps in it are saved separately under a folder (for example, a folder named PADApp) for users to view.
  • Step 203 Detect an input operation performed by the input device.
  • the input device may include a mouse, a keyboard, a touchpad, etc., wherein the touchpad may be separately set or may be overlapped with the display unit to form a touchscreen display.
  • Step 204 Determine, when the operation object of the first operation is the application identifier in the at least one application identifier, the application identifier of the first application from the at least one application identifier.
  • the display unit displays the running status of the first operating system.
  • the application identifier may be determined to be corresponding to the application identifier.
  • the application is the first application, that is, the management operation of the first application in the opened application in the second device is currently performed.
  • Step 205 Detect an operation of the application identifier of the first application by the input device.
  • the input device may include a mouse, a keyboard, a touchpad, etc., wherein the touchpad may be separately set or may be overlapped with the display unit to form a touchscreen display.
  • Step 206 When the second operation is a switching operation corresponding to the preset management command, the corresponding switching command is obtained.
  • the second operation is an operation of the application identification of the first application
  • Step 207 Send a handover command to the second device to switch to the second device, so that the second device executes the first application in the second state.
  • the first device may send the application name of the first application and the switching command to the second device by using a wired or wireless manner. For example, when the BASE device as the first device transmits a handover command to the PAD device as the second device, the PAD device can activate the second operating system, in the The second application continues to execute the first application, and activates the first application to the foreground of the display window for the user to view.
  • Step 208 The control display unit is switched to be controlled by the second device.
  • the first device can also control the display unit to switch to control by the second device.
  • FIG. 3 a flowchart of a third embodiment of the application management method of the present application is as follows:
  • Step 301 The first device sends, in the first state, a request for acquiring an application that has been run in the second device to the second device.
  • the first device may send a request for acquiring the executed application in the second device to the second device by means of a wired (such as a data bus (USB/UART)) or a wireless (such as WIFI).
  • a wired such as a data bus (USB/UART)
  • a wireless such as WIFI
  • the BASE device may send a request to the second device by using a preset process (for example, a Hybrid process).
  • Step 302 Receive an application list returned by the second device according to the request, where the application list includes an application identifier of the running application in the second device.
  • the second device can search for each application that has already run to obtain a list of applications of the executed applications.
  • the PAD device may obtain a list of applications including the application identifier of the executed application through a preset process (for example, a PadAct ivi tyManager process), and then pass the application list through Return to the BASE device either wired or wireless.
  • the BASE device may obtain the application list in a wired or wireless manner to the PAD device through a preset process.
  • the first device may display the application identifiers of all applications in the application list in a shortcut manner on the desktop corresponding to the first operating system, or list the applications.
  • the app IDs for all apps in it are saved separately under a folder (for example, a folder named PADApp) for users to view.
  • Step 303 Detect an input operation performed by the input device.
  • the input device may include a mouse, a keyboard, a touchpad, etc., wherein the touchpad may be separately set or may be overlapped with the display unit to form a touchscreen display.
  • Step 304 Determine, when the operation object of the first operation is the application identifier in the at least one application identifier, the application identifier of the first application from the at least one application identifier.
  • the display unit Since the current state is in the first state, the display unit displays the operating state of the first operating system, In the first state, when the operation object of the first operation is detected, the application corresponding to the application identifier is determined to be the first application, that is, the application that is currently open to the second device is determined. The first application in the management operation.
  • Step 305 Detect an operation of the application identifier of the first application by the input device.
  • the input device may include a mouse, a keyboard, a touchpad, etc., wherein the touchpad may be separately set or may be overlapped with the display unit to form a touchscreen display.
  • Step 306 When the second operation is a shutdown operation corresponding to the preset management command, the corresponding shutdown management command is obtained.
  • the second operation is an operation of the application identification of the first application
  • Step 307 Send a shutdown command to close the first application to the second device, so that the second device ends the process of the first application.
  • the first device may send the application name of the first application and the shutdown command to the second device by using a wired or wireless manner. For example, when the BASE device as the first device transmits a close command to the PAD device as the second device, the PAD device can perform the operation of closing the first application in the background.
  • the second device may further notify the first device of the closed result, and the first device may delete the first application in the opened application list or mark the first application as closed.
  • FIG. 4 a flowchart of a fourth embodiment of the application management method of the present application is as follows:
  • Step 401 The first device sends, in the first state, a request for acquiring an application that is not running in the second device to the second device.
  • the first device When the first device is connected to the second device, the first device can be wired (data bus)
  • USB/UART USB/UART
  • WIFI wireless
  • the BASE device can send a request to the second device by using a preset process (for example, a Hybrid Service process).
  • Step 402 Receive an application list returned by the second device according to the request, where the application list includes an application identifier of the second device that is not running the application.
  • the second device can search for various applications that are not running but can be run. Take a list of apps that are not running apps.
  • the PAD device may obtain a list of applications including an application identifier of the non-running application through a preset process (for example, a PadAc tivi tyManager process), and then pass the application list through Return to the BASE device either wired or wireless.
  • the BASE device may obtain the application list in the wired or wireless manner through the preset process to the PAD device.
  • the first device may display the application identifiers of all applications in the application list in a shortcut manner on the desktop corresponding to the first operating system, or list the applications.
  • the app IDs for all apps in it are saved separately under a folder (for example, a folder named PADApp) for users to view.
  • Step 403 Detect an input operation performed by the input device.
  • the input device may include a mouse, a keyboard, a touchpad, etc., wherein the touchpad may be separately set or may be overlapped with the display unit to form a touchscreen display.
  • Step 404 Determine, when the operation object of the first operation is the application identifier in the at least one application identifier, the application identifier of the first application from the at least one application identifier.
  • the display unit displays the running status of the first operating system.
  • the application identifier may be determined to be corresponding to the application identifier.
  • the application is a first application, that is, a management operation is currently performed on the first application in the application that is not activated in the second device.
  • Step 405 Detect an operation of the application identifier of the first application by the input device.
  • the input device may include a mouse, a keyboard, a touchpad, etc., wherein the touchpad may be separately set or may be overlapped with the display unit to form a touchscreen display.
  • Step 406 When the second operation is a startup operation corresponding to the preset management command, the corresponding startup management command is obtained.
  • the second operation is an operation of the application identification of the first application
  • Step 407 Send a start command to start the first application to the second device, and control the display unit to switch to control by the second device.
  • the first device may send the first application to the second device by using a wired or wireless manner.
  • the app name and the start command For example, when the BASE device as the first device sends a startup command to the PAD device as the second device, the PAD device can activate the second operating system, start the first application and execute the first application under the second operating system. And activate the first application to the foreground of the display window for the user to view. Further, for a portable terminal having dual systems, the first device can also control the display unit to switch to control by the second device.
  • Step 408 After the first application is started, the first device switches from the first state to the second state. After the first application is started, the first device controls the display unit to display the state in which the second operating system is running, and the first device switches to the second device.
  • Step 409 The first device updates the application identifier of the first application to the activated application identifier.
  • the first device may mark the application identifier of the first application in the application list, and mark the application as the activated application.
  • the first device may separately generate the activated application list, and the first application may never start the application.
  • the list is removed and added to the list of launched apps.
  • the first device may add the first application to the task bar of the first operating system. If the user exits the first application in the second state, the second device may send an exit command to the first device, so that the first device exits the first application from the task bar; the user may also operate the shortcut key or physical Pressing the button from the second state to the first state, and exiting the first application in the task bar of the first operating system, and then notifying the second device that the first application has been closed, and the second device is turned off by the second operating system. After the first application, or switching back to the first state, by clicking the first application in the task bar, switching back to the second state again, and executing the first application in the second system.
  • the application further provides an embodiment of an application management device, which is a first device and is connected to the second device.
  • FIG. 5 it is a block diagram of a first embodiment of an application management device of the present application:
  • the application management device includes:
  • the mapping unit 51 0 is configured to map at least one application in the second device, to obtain a corresponding at least one application identifier
  • the first detecting unit 520 is configured to detect the first operation
  • the determining unit 530 is configured to determine, when the first operation meets the first preset condition, an application identifier of the first application from the at least one application identifier;
  • a second detecting unit 540 configured to detect a second operation
  • the management unit 550 is configured to: when the second operation meets the second preset condition, according to the first The second operation obtains the corresponding application management command, and sends the application management command to the second device, so that the second device manages the first application according to the application management command.
  • the first operation includes: an input operation performed by the input device; the first operation satisfying the first preset condition includes: the operation object of the first operation is in the at least one application identifier Application identifier
  • the second operation includes: an operation of the application identifier of the first application by the input device; and the second operation satisfying the second preset condition includes: the second operation is an operation corresponding to the preset management command .
  • FIG. 6 a block diagram of a second embodiment of an application management device of the present application is as follows:
  • the application management device includes:
  • the mapping unit 61 0 is configured to map at least one application in the second device, to obtain a corresponding at least one application identifier
  • the first detecting unit 620 is configured to detect the first operation
  • a determining unit 630 configured to determine, when the first operation meets the first preset condition, an application identifier of the first application from the at least one application identifier;
  • a second detecting unit 640 configured to detect a second operation
  • the management unit 650 is configured to: when the second operation meets the second preset condition, obtain a corresponding application management command according to the second operation, and send the application management command to the second device, so as to enable the The second device manages the first application according to the application management command.
  • the first device runs the first operating system
  • the second device runs the second operating system
  • the at least one application is installed in the second operating system
  • the first device further includes:
  • the display unit 660 displays the first operating state of the first operating system as the first state of the first device, and the display unit displays the second operating state of the second operating system.
  • mapping unit 61 0 may include at least one of the following units (not shown in FIG. 6):
  • a first mapping unit configured to send, to the second device, a request for acquiring an application that has been run in the second device, and receive an application list that is returned by the second device according to the request, where the application list includes An application identifier of an application that has been run in the second device;
  • a second mapping unit configured to send, to the second device, a request for acquiring an application that is not running in the second device, and receive an application list that is returned by the second device according to the request, where the application column
  • the table includes an application identifier of the second device that is not running the application.
  • the management unit 650 can include (not shown in Figure 6):
  • a switching management unit configured to: when the first device sends a request for acquiring an application in the second device by using the first mapping unit to the second device in the first state, The second device sends a handover command to switch to the second state, so that the second device executes the first application in the second state.
  • the management unit 650 can include (not shown in Figure 6):
  • a management unit configured to: when the first device is in the first state, when the first mapping unit sends a request for acquiring an application in the second device to the second device, The second device sends a close command to close the first application, so that the second device ends the process of the first application.
  • the management unit 650 can include (not shown in Figure 6):
  • a startup management unit configured to: when the first device is in the first state, when the second mapping unit sends a request to the second device to obtain an application that is not running in the second device, The second device sends a start command to start the first application.
  • the device may further include:
  • the switching unit 670 is configured to switch, when the first application is started, the first device from the first state to the second state.
  • the updating unit 680 is configured to: after the first application is started, the first device updates the application identifier of the first application to the activated application identifier.
  • the application management device may further include:
  • the control unit 690 is configured to control, when the first device is in the first state, to switch the display unit to be controlled by the second device.
  • the first operation includes: an input operation performed by the input device; the first operation satisfying the first preset condition includes: the operation object of the first operation is in the at least one application identifier Application identifier
  • the second operation includes: an operation of applying an application identifier of the first application by an input device;
  • the second operation satisfying the second preset condition includes: the second operation is an operation corresponding to a preset management command.
  • the first device is connected to the second device in the embodiment of the present application, and the first device maps at least one application in the second device to obtain a corresponding at least one application identifier, and detects the first operation.
  • the first operation meets the first preset condition, determining an application identifier of the first application from the at least one application identifier, detecting the second operation, and obtaining a corresponding operation according to the second operation when the second operation meets the second preset condition
  • Applying the management command and sending an application management command to the second device, so that the second device manages the first application according to the application management command.
  • the application in the second device can be managed by the first device.
  • the application in the second device When the two devices work together, when the application in the second device is to be used, there is no need to switch to the second device separately. In the working state, the application of the second device can be managed in the first device, so that switching between applications of different devices can be realized, and the user experience of the portable terminal user using the hybrid system is improved.
  • the embodiment of the present invention may be applied to a hybrid system composed of a first electronic device and a second electronic device, where the hybrid architecture system may be a combination of two independent electronic devices, or may include the first electronic device.
  • a portable electronic device of the device and the second electronic device can consist of a single, single-system laptop and a smartphone, or a laptop with a hybrid architecture system.
  • the first electronic device can include a first hardware system, such as a system based on an X86 architecture or an ARM architecture processor.
  • the second electronic device can include a second hardware system, such as a system based on an X86 architecture or an ARM architecture processor. That is, the first electronic device and the second electronic device may be based on the same hardware architecture or may be based on different hardware architectures.
  • the first electronic device may include a first hardware system having a first operating system, such as a desktop operating system (such as Windows, Linux or MacOS) or a portable device operating system (such as Android, Symbian or iOS).
  • the first hardware system may include a second hardware system having a second operating system, such as a second device installed with a desktop operating system (such as Windows, Linux or MacOS) or a portable device operating system (such as Android, Symbian or iOS) Hardware system. That is, the first operating system and the second operating system may be the same or different, as long as they can run on the corresponding hardware system.
  • the first electronic device is based on an X86 architecture processor, a system installed with a desktop operating system, and a second An electronic device is a system with an ARM architecture processor installed with a portable device operating system.
  • a synchronization method according to an embodiment of the present invention will be described with reference to FIG.
  • FIG. 7 is a flow chart illustrating a synchronization method according to an embodiment of the present invention. The synchronization method according to the embodiment of the present invention is applied to a first electronic device (for example, a host) for synchronizing with a second electronic device (for example, a Pad) to obtain an application list of an application installed on the second electronic device.
  • a first electronic device for example, a host
  • a second electronic device for example, a Pad
  • Step S701 Detect a data connection with the second electronic device, and obtain a detection result.
  • the first electronic device detects whether the data connection with the second electronic device is successful by various means, and obtains the detection result.
  • the first electronic device can detect the status of the data connection with the second electronic device by means such as polling, triggering, etc., and obtain the detection result.
  • Step S702 When the detection result indicates that the data connection between the first electronic device and the second electronic device is successful, obtaining an application list from the second electronic device, where the application list includes at least one of the second An application installed in an electronic device.
  • the first electronic device may acquire the application list of the second electronic device from the second electronic device.
  • the application list includes at least one application installed in the second electronic device.
  • the first electronic device may send the second electronic device for acquiring a request for an application list of an application installed in the second electronic device, and then receiving an application list sent by the second electronic device in response to the request.
  • the first electronic device actively sends a request for acquiring the application list of the second electronic device to the second electronic device, and after receiving the request, the second electronic device starts to obtain the information of the locally installed application, and then The application list of the locally installed application is sent to the first electronic device through the established data connection channel.
  • the second electronic device may automatically transmit the application list.
  • the first electronic device may not send a request for acquiring the application list of the second electronic device to the second electronic device, instead, The second electronic device can automatically send the application list, An electronic device can directly receive a list of applications transmitted by the second electronic device including applications installed in the second electronic device.
  • the second electronic device may package the local application list and send it to the first electronic device in the form of an XML file, where the XML file includes information such as a startup manner, an icon, and the like of each application.
  • the first electronic device may obtain, from the second electronic device, an application list including all applications in the second electronic device. That is to say, the first electronic device directly acquires an application list including all applications in the second electronic device regardless of whether the application in the second electronic device already exists locally.
  • the first electronic device may obtain, from the second electronic device, a list of applications including a specified one of the second electronic devices. That is, the first electronic device can specify that certain applications in the second electronic device are to be acquired, for example, by specifying an application name, and obtaining a list of applications including the application from the second electronic device. Alternatively, the application list of all applications included in the folder is obtained from the second electronic device by specifying the folder name.
  • the first electronic device can obtain the application list including the specific application from the second electronic device, so as to The particular application is run on the second electronic device.
  • the first electronic device may obtain a list of applications including the same application from the second electronic device to select to run the same application on the second electronic device.
  • the first electronic device may be from the specific application that can only be run on the operating system on the second electronic device.
  • the second electronic device obtains a list of applications including the specific application.
  • the method of designation is not limited to this, and the user can specify his/her desired application by any means.
  • the first electronic device obtains an application list including the updated application from the second electronic device, wherein the last transmitted application list has been stored in the second electronic device. That is, in the second electronic device, the application list that has been sent last time may be stored by, for example, a log file, and the next time the application list is to be sent, the second electronic device may refer to the already stored application column.
  • the table only sends the application list including the updated application to the first electronic device.
  • the first electronic device may send an application list including an application corresponding to the existing application identifier to the second electronic device, and obtain an application list including the updated application from the second electronic device, where the second The list of applications that were last sent is not stored in the electronic device.
  • the first electronic device may send the application list including the application corresponding to the locally existing application identifier to the second electronic device, After receiving the application list, the two electronic devices compare with the local application, and then only send the application list including the updated application to the first electronic device.
  • the second electronic device does not need to send the application list of all applications installed locally to the first electronic device, but may selectively send the application list of a part of the application to the first electronic device according to the situation, so that Reduce the amount of data for communication.
  • Step S703 Create, according to the application list, at least one application identifier corresponding to one application in the application list, where the application identifier is triggered, and the application identifier can be started in the second electronic device.
  • the corresponding application is a registered application in the application list.
  • the first electronic device may locally create at least one application identifier corresponding to one application in the application list according to the application list. That is, the first electronic device locally creates a corresponding application identifier, such as a startup icon, a shortcut, and the like, for each application included in the application list according to the received application list. And after the application identifier is triggered, the application corresponding to the application identifier can be started in the second electronic device. That is, after the application identifier created on the first electronic device is triggered, the application corresponding to the application identifier in the second electronic device is in an activatable state. Then, the application is started, for example, by the user's reconfirmation or the like.
  • the application corresponding to the application identifier in the second electronic device can be started immediately without requiring the user to re-confirm.
  • the first electronic device includes a display unit
  • the method further includes: displaying an operation of the second electronic device on the display unit when the application corresponding to the application identifier is activated in the second electronic device interface. That is, in this step, when the application corresponding to the application identifier is activated in the second electronic device, an operation interface of the second electronic device should be displayed on the display unit.
  • the content originally displayed on the display unit may or may not be maintained.
  • the operation interface of the second electronic device can be simultaneously displayed by techniques such as split screen display, picture-in-picture display, and the like. Or, in the office In a case where the content originally displayed on the display unit is not maintained, the entire display screen of the display unit may be switched to the operation interface of the second electronic device.
  • an application running window corresponding to the application identifier may be displayed.
  • the application runs in the background in the second electronic device, does not display its running window, but only displays the corresponding identifier (such as displaying an identifier indicating the application in the status bar or any column).
  • the application runs in the background in the second electronic device, does not display any content related to the application, and the like.
  • a trigger unit such as a hardware unit such as a button, a button, or the like, or a software unit corresponding to a predetermined command, such as an icon, a shortcut, or the like, may be disposed on the first electronic device, and then activated according to the user's operation on the trigger unit.
  • Wireless connection of the second electronic device such as Bluetooth, WiFi, wireless local area network connection, and the like.
  • some physical interfaces may be disposed on the first electronic device, and when physically connected to the second electronic device through the physical interface, starting and A data connection of the second electronic device.
  • the created application identifier can be automatically deleted. Of course, you can also not delete the created app ID.
  • the first electronic device needs to create a plurality of application identifiers corresponding to all applications in the received application list. For example, when the received application list includes the application 1, the application 2, and the application 3, the first electronic device creates an application identifier 1, an application identifier 2, and an application identifier 3 corresponding to the application 1, the application 2, and the application 3. .
  • the first electronic device may correspond all the applications in the received application list to the locally existing application identifier.
  • the application is compared, and an application identifier corresponding to the updated application is created and/or deleted based on the comparison result. For example, when the application list, the application 2, and the application 4 are included in the received application list, since the application identifier 1, the application identifier 2, and the application identifier 3 have been created last time, the first electronic device will receive the application list.
  • the application 1, the application 2, and the application 4, and the existing application identifier 1, the application identifier 2, and the application 1, the application 2, and the application 3 are compared, and it is determined that the application 3 is currently deleted in the second electronic device. And added the application 4. Therefore, the first electronic device deletes the created application identifier 3 corresponding to the application 3, and simultaneously creates and applies the application 4. Corresponding application identifier 4.
  • an update request unit such as a hardware unit such as a button, a button, or the like, or a software unit corresponding to a predetermined command such as an icon, a shortcut, or the like may be provided on the first electronic device.
  • the data connection of the first electronic device and the second electronic device is in a connection unsuccessful state, recording the update request in a recording unit (such as a memory) of the first electronic device, and in the first electronic
  • a recording unit such as a memory
  • an application identifier corresponding to the updated application may be created and/or deleted according to the received application list.
  • the user can manually initiate synchronization with the second electronic device as needed during use.
  • the electronic device 800 includes:
  • the detecting unit 801 is configured to detect a data connection with the second electronic device to obtain a detection result
  • the obtaining unit 802 is configured to: when the detection result indicates that the data connection between the electronic device and the second electronic device is successful, Obtaining, by the second electronic device, an application list, where the application list includes at least one application installed in the second electronic device;
  • the creating unit 803 is configured to: create, according to the application list, at least one application identifier corresponding to one application in the application list, where the application identifier is triggered, and the device can be started in the second electronic device The application corresponding to the application identifier.
  • the application corresponding to the application identifier is started in the second electronic device.
  • the electronic device 800 further includes a display unit 804 configured to display an operation interface of the second electronic device when the application corresponding to the application identifier is activated in the second electronic device.
  • the obtaining unit 802 sends the second electronic device to acquire the second a request for an application list of an application installed in the child device, and then receiving a list of applications sent by the second electronic device in response to the request; or when the detection result indicates the electronic device 800 and the second electronic device When the data connection is successful, the obtaining unit 802 receives the application list automatically sent by the second electronic device.
  • the electronic device 800 further includes a triggering unit 805 configured to initiate a wireless connection with the second electronic device according to an operation of the triggering unit by a user, where the triggering unit 805 is a button set on the electronic device Or an identifier corresponding to a predetermined command.
  • the electronic device 800 also includes a physical interface 806 configured to initiate a data connection with the second electronic device when the electronic device is physically connected through the physical interface 106 and the second electronic device.
  • the obtaining unit 802 is further configured to: obtain an application list including all applications in the second electronic device from the second electronic device; or obtain from the second electronic device, including the second electronic device Specifying an application list of the application; or obtaining an application list including the updated application from the second electronic device, where the last transmitted application list is stored in the second electronic device; or the sending includes the existing application identifier
  • the application list of the application is sent to the second electronic device, and the application list including the updated application is obtained from the second electronic device, wherein the last transmitted application list is not stored in the second electronic device.
  • the electronic device 800 further includes a deleting unit 807 configured to delete the created application identifier when the electronic device is disconnected from the second electronic device.
  • the creating unit 802 is further configured to: when the electronic device 800 is deleted from the second electronic device, delete the created application identifier, and create multiple corresponding to all applications in the application list. An application identifier; or an application corresponding to an existing application identifier in a case where the created application identifier is not deleted when the electronic device 800 is disconnected from the second electronic device The application identifier corresponding to the updated application is created and/or deleted according to the comparison result.
  • the electronic device further includes an update request unit 808 configured to be in a case where the user operates the update request unit 808, wherein the update request unit 808 is a button set on the electronic device or corresponds to a predetermined command Logo.
  • the The update request is recorded in the recording unit 809 of the child device, and when the data connection of the electronic device 800 and the second electronic device is successful, the update request recorded in the recording unit 809 is read and sent to the location Said second electronic device.
  • the creating unit 809 is further configured to: if the second electronic device detects the updated application in response to the update request, receive an application list including the updated application sent from the second electronic device, and create according to the received application list And/or delete the application ID corresponding to the updated application.
  • the electronic device 800 also includes a control unit 810 that controls the operation of the various units.
  • the embodiment of the present invention may be applied to a hybrid system composed of a first electronic device and a second electronic device, where the hybrid architecture system may be a combination of two independent electronic devices, or A portable electronic device including a first electronic device and a second electronic device.
  • a hybrid architecture system can consist of a single, single-system notebook computer and a smart phone, or a notebook computer with a hybrid architecture system.
  • the first electronic device can include a first hardware system, such as a system based on an X86 architecture or an ARM architecture processor.
  • the second electronic device can include a second hardware system, such as a system based on an X86 architecture or an ARM architecture processor. That is, the first electronic device and the second electronic device may be based on the same hardware architecture or may be based on different hardware architectures.
  • the first electronic device may include a first hardware system having a first operating system, such as a desktop operating system (such as Windows, Linux or MacOS) or a portable device operating system (such as Android, Symbian or iOS).
  • the first hardware system may include a second hardware system having a second operating system, such as a second device installed with a desktop operating system (such as Windows, Linux or MacOS) or a portable device operating system (such as Android, Symbian or iOS) Hardware system. That is, the first operating system and the second operating system may be the same or different, as long as they can run on the corresponding hardware system.
  • the first electronic device is based on an X86 architecture processor, a system installed with a desktop operating system
  • the second electronic device is a system with an ARM architecture processor installed with a portable device operating system.
  • An association method according to an embodiment of the present invention will be described with reference to FIG.
  • FIG. 9 is a flow chart illustrating an association method according to an embodiment of the present invention.
  • An association method according to an embodiment of the present invention is applied to a first electronic device (for example, a host) for acquiring an application list of an application installed on a second electronic device (for example, a Pad), and the acquired application and the first electronic device and A file of a corresponding file type on a storage unit of the second electronic device is associated.
  • the first electronic device has a first storage unit in which various types of data such as images, movies, documents, forms, games, and the like can be stored.
  • the second electronic device has a second storage unit in which various data identical to the first storage unit can be stored. After the first electronic device is connected to the second electronic device, the first electronic device can directly access the second storage unit of the second electronic device.
  • association method is applied to a first electronic device having a first storage unit and a second electronic device having a second storage unit.
  • S901 The first electronic device obtains a detection result.
  • the first electronic device can detect whether the data connection with the second electronic device is successful in various ways, and obtain the detection result.
  • the first electronic device can detect the status of the data connection with the second electronic device by means of, for example, polling, triggering, etc., and obtain the detection result.
  • the first electronic device obtains an application list from the second electronic device, where the application list includes an application in at least one of the second electronic devices.
  • step S901 first determining whether the detection result in step S901 satisfies a predetermined condition, and then, when the predetermined condition is met, obtaining an application list from the second electronic device, the application list including at least one of the second electronic devices Application in .
  • the predetermined condition may be that the detection result indicates that the data connection between the first electronic device and the second electronic device is successful. That is, in this case, when the data connection of the first electronic device and the second electronic device is successful, the application list is automatically obtained from the second electronic device.
  • the predetermined condition may be that the detection result indicates that the data connection between the first electronic device and the second electronic device is successful, and the request unit on the first electronic device is operated, and the request unit is a button disposed on the first electronic device or an identifier corresponding to a predetermined command, And a method for sending a request for acquiring the application list to the second electronic device. That is, in this case, when the data connection of the first electronic device and the second electronic device is successful, the application list is not automatically obtained from the second electronic device, but the user operates the first electronic device. And when the request unit is set, sending a request for acquiring the application list to the second electronic device, and then obtaining an application list from the second electronic device.
  • the condition to be satisfied is that the data connection of the first electronic device and the second electronic device is successful, and the user operation request unit manually requests the application list from the second electronic device.
  • the manner in which the manual request obtains the application list does not operate when the connection is just established, so that power can be saved.
  • the first electronic device may send the second electronic device for acquiring a request for an application list of an application installed in the second electronic device, and then receiving an application list sent by the second electronic device in response to the request.
  • the first electronic device actively sends a request for acquiring the application list of the second electronic device to the second electronic device, and after receiving the request, the second electronic device starts to obtain the information of the locally installed application, and then The application list of the locally installed application is sent to the first electronic device through the established data connection channel.
  • the second electronic device may automatically transmit the application list.
  • the first electronic device may not send a request for acquiring the application list of the second electronic device to the second electronic device, instead, The second electronic device may automatically send the application list, and the first electronic device may directly receive the application list sent by the second electronic device including the application installed in the second electronic device.
  • the second electronic device may package the local application list and send it to the first electronic device in the form of an XML file, where the XML file includes information such as a startup mode, an icon, and a list of associated file types for each application.
  • the first electronic device may obtain, from the second electronic device, an application list including all applications in the second electronic device. That is to say, the first electronic device directly acquires an application list including all applications in the second electronic device regardless of whether the application in the second electronic device already exists locally.
  • the first electronic device may obtain an application list including the specified application in the second electronic device from the second electronic device. That is, the first electronic device may specify that some applications in the second electronic device are to be acquired, for example, by specifying an application name, and obtaining a list of applications including the application from the second electronic device.
  • the application list of all the applications included in the folder is obtained from the second electronic device by specifying the folder name.
  • the first electronic device can obtain the application list including the specific application from the second electronic device, so as to The particular application is run on the second electronic device.
  • the first electronic device may obtain a list of applications including the same application from the second electronic device to select to run the same application on the second electronic device.
  • the first electronic device may be from the specific application that can only be run on the operating system on the second electronic device.
  • the second electronic device obtains a list of applications including the specific application.
  • the manner of designation is not limited to this, and the user can specify his/her desired application by any means.
  • the first electronic device obtains from the second electronic device an application list including the updated application, wherein the last transmitted application list has been stored in the second electronic device. That is to say, in the second electronic device, the application list that has been sent last time can be stored by, for example, a log file.
  • the second electronic device can refer to the already stored application list, and only includes the already-included The application list of the updated application is sent to the first electronic device.
  • the first electronic device may send an application list including an application corresponding to the existing application identifier to the second electronic device, and obtain an application list including the updated application from the second electronic device, where the second The list of applications that were last sent is not stored in the electronic device.
  • the first electronic device may send the application list including the application corresponding to the locally existing application identifier to the second electronic device, After receiving the application list, the two electronic devices compare with the local application, and then only send the application list including the updated application to the first electronic device.
  • the second electronic device does not need to send the application list of all applications installed locally to the first electronic device, but may According to circumstances, a part of the application list of the application is selectively transmitted to the first electronic device, so that the amount of data of the communication can be reduced.
  • the first electronic device associates the application in the application list with a file of a corresponding file type in the first storage unit and/or the second storage unit according to the application list.
  • the first electronic device can directly access the second electronic device.
  • the second storage unit Therefore, according to the application list, the first electronic device associates an application in the application list with a file of a corresponding file type in the first storage unit and/or the second storage unit.
  • the files in the first storage unit and the second storage unit may be opened using an application installed in the first electronic device, or may be opened using an application installed in the second electronic device.
  • the first electronic device may directly access the storage in the storage unit of the second electronic device file.
  • the user wishes to play the movie file A.avi with the Pad video player.
  • the user has two options: 1) first manually switch to the Pad side, then open the video player, and select the movie file A.avi to play; 2) click the video player icon on the host side desktop, The system automatically switches to the Pad side and opens the video player, and then the user selects the movie file A.avi to play.
  • Such an operation is complicated and the user experience is poor.
  • the user can display a graphical user interface such as a pop-up menu when the movie file A.avi is activated, and In the pop-up menu, the option "Play with MediaPaplay on Pad” is displayed.
  • the user can automatically change to Pad and play the movie file A.avi with MediaPlayer on the Pad by selecting "Play with MediaPlayer on Pad". User experience.
  • a trigger unit such as a hardware unit such as a button, a button, or the like, or a software unit corresponding to a predetermined command, such as an icon, a shortcut, or the like, may be disposed on the first electronic device, and then activated according to the user's operation on the trigger unit.
  • Wireless connection of the second electronic device such as Bluetooth, WiFi, wireless local area network connection, and the like.
  • some physical interfaces may be disposed on the first electronic device, and when physically connected to the second electronic device through the physical interface, starting and A data connection of the second electronic device.
  • the first electronic device may also locally create at least one application identifier corresponding to one of the applications in the application list.
  • the created application identifier may be automatically deleted. Of course, you can also not delete the created app ID.
  • the application in the application list and the file of the corresponding file type in the first storage unit and the second storage unit may be unlinked.
  • an update request unit such as a hardware unit such as a button, a button, or the like, or a software unit corresponding to a predetermined command such as an icon, a shortcut, or the like may be provided on the first electronic device.
  • the data connection of the first electronic device and the second electronic device is in a connection unsuccessful state, recording the update request in a recording unit (such as a memory) of the first electronic device, and in the first electronic
  • a recording unit such as a memory
  • the second electronic device After receiving the update request, if the second electronic device detects the updated application in response to the update request, receiving an application list including the updated application sent from the second electronic device, and correlating and/or according to the received application list Disassociate the file corresponding to the file type of the updated application.
  • the user can manually initiate synchronization with the second electronic device as needed during use, and according to the synchronization result, the application and the storage unit on the second electronic device
  • the file is associated.
  • the association relationship between the application and the file may be saved in a system of the first electronic device. For example, a log file can be used in the operating system of the first electronic device to record the association relationship between the application and the file.
  • association relationship between the application and the file saved in the system of the second electronic device can also be used by the user's switching operation.
  • the configuration of the electronic device 1000 according to an embodiment of the present invention will be described below with reference to FIG.
  • the electronic device 1000 according to the embodiment includes:
  • the first storage unit 1010 is configured to store various users and files
  • the detecting unit 1020 is configured to obtain a detection result
  • the obtaining unit 1030 is configured to obtain, from the second electronic device, an application list when the detection result satisfies a predetermined condition, where the application list includes at least one application in the second electronic device, and the second electronic device includes Two storage units;
  • the associating unit 1040 is configured to associate, according to the application list, an application in the application list and a file of a corresponding file type in the first storage unit and/or the second storage unit.
  • the predetermined conditions include:
  • the detection result indicates that the data connection between the first electronic device and the second electronic device is successful
  • the detection result indicates that the data connection between the first electronic device and the second electronic device is successful, and the request unit on the first electronic device is operated, and the request unit is a button set on the first electronic device Or an identifier corresponding to the predetermined command, configured to send a request for acquiring the application list to the second electronic device.
  • the obtaining unit 1030 is further configured to:
  • the electronic device 1000 may further include a triggering unit 1050 configured to initiate a wireless connection with the second electronic device according to an operation of the triggering unit 1050 by a user, where the triggering unit 1050 is configured on the electronic device The button or the identifier corresponding to the predetermined command.
  • the electronic device 1000 can also include a physical interface 1060 configured to initiate a data connection with the second electronic device when physically connecting through the physical interface 1060 and the physical interface of the second electronic device.
  • the obtaining unit 1030 can also be configured to:
  • the electronic device 1000 may further include an application identifier creating unit 1070 configured to create at least one application identifier corresponding to one of the application lists.
  • the electronic device 1000 may further include an application identifier deleting unit 1080 configured to delete the created application identifier when the electronic device 1000 is disconnected from the second electronic device.
  • the electronic device 1000 may further include a disassociation unit 1090 configured to disassociate the application in the application list and the first storage unit 1010 when the electronic device 100 is disconnected from the second electronic device. a file of a corresponding file type in the second storage unit.
  • the electronic device 1000 may further include an update request unit 1100 configured to be in a case where the user operates the update request unit 1100, wherein the update request unit 110 is a button set on the electronic device or corresponds to a predetermined The identifier of the command,
  • the update request is recorded in the recording unit 1110 of the electronic device 1000, and the data connection between the electronic device 1000 and the second electronic device Upon success, the update request recorded in the recording unit 1110 is read and sent to the second electronic device.
  • the application identifier creating unit 1070 and/or the application identifier deleting unit 1080 may also be configured to: Receiving, by the second electronic device, the updated application, including the updated application, sent from the second electronic device, and associating and/or disassociating the update corresponding to the updated application list according to the received application list The file type of the applied file.
  • an association relationship between the application and the file may be saved in a system of the electronic device 1000.
  • association relationship between the application and the file saved in the system of the second electronic device can also be used by the user's switching operation.
  • the first electronic device can include a control unit 1120 for integrally controlling the various units.
  • association method and the electronic device it is possible to conveniently acquire an application list of an application installed on another electronic device, and associate an application in the application list with the first storage unit and the first A file of a corresponding file type in the two storage units, thereby conveniently selecting an application to open the file using the first electronic device or the second electronic device, improving the user experience.
  • steps S 1101 and S 1101 of the association method according to another embodiment of the present invention are the same as steps S901 and S902 of the association method according to an embodiment, and a detailed description thereof is omitted herein.
  • Step 1103 When activating a file stored in the first storage unit and the second storage unit, displaying a graphical user interface including an identifier corresponding to an application that can activate the file, wherein the file can be activated
  • the application includes an application installed locally by the first electronic device and an application installed in the second electronic device.
  • a graphical user interface including an identification corresponding to the application that can activate the file is displayed, such as a pop-up menu.
  • the locally installed application of the first electronic device capable of opening the file and the identification of an application installed in the second electronic device, such as a shortcut or an icon, etc., may be displayed in the graphical user interface.
  • a graphical user interface such as a popup menu may be displayed, and The pop-up menu displays the options of "Playing with the host-side WindowPlayer", “Playing with the host-side MediaPlayer”, “Playing with the Pad-side WindowPlayer”, “Playing with the Pad-side MediaPlayer”, etc., and the user can select "Play with the MediaPlayer on the Pad”. , automatically switch to Pad and play the movie file A.avi with MediaPlayer on the Pad, so that you can easily select the desired application activation file.
  • the configuration of the electronic device 1200 will be described below with reference to FIG.
  • the electronic device 1200 includes:
  • the first storage unit 1201 is configured to store various users and files
  • the detecting unit 1202 is configured to obtain a detection result
  • the obtaining unit 1203 is configured to: when the detection result meets the predetermined condition, obtain an application list from the second electronic device, where the application list includes at least one application in the second electronic device, and the second electronic device includes Two storage units;
  • the display unit 1204 is configured to display, when the files stored in the first storage unit and the second storage unit are activated, a graphic user including the identifier corresponding to the application that can activate the file, in the second electronic device Installed apps.
  • the predetermined condition may include:
  • the detection result indicates that the data connection between the electronic device and the second electronic device is successful
  • the detection result indicates that the data connection between the electronic device and the second electronic device is successful, and the request unit on the electronic device is operated, and the request unit is a button set on the electronic device or corresponds to a predetermined command.
  • an identifier configured to send, to the second electronic device, a request for acquiring the application list.
  • the first electronic device can include a control unit 1205 for integrally controlling the various units.
  • the first electronic device 1200 can also include a first electronic device in accordance with an embodiment.
  • the other functional units of 1000 are the same functional unit, and the description thereof is omitted here.
  • association method and the electronic device it is possible to conveniently acquire an application list of an application installed on another electronic device, and display a graphical user interface including an identifier corresponding to an application that can activate the file,
  • the application that can activate the file includes an application installed locally by the first electronic device and an application installed in the second electronic device, thereby conveniently selecting an application that uses the first electronic device or the second electronic device to open Files that improve the user experience.
  • Hybrid system 1300 in accordance with one embodiment of the present invention includes:
  • a first electronic device 1340 comprising a first hardware system having a first operating system and a second electronic device 1350 comprising a second hardware system having a second operating system , among them
  • the second electronic device 1350 includes:
  • a second storage unit 1351 configured to store various users and files
  • the first electronic device 1340 includes:
  • a first storage unit 1341 configured to store various users and files
  • the detecting unit 1342 is configured to obtain a detection result
  • the obtaining unit 1343 is configured to obtain, from the second electronic device 1350, an application list when the detection result satisfies a predetermined condition, where the application list includes at least one application in the second electronic device 1350;
  • the associating unit 1344 is configured to associate the application in the application list with the file of the corresponding file type in the first storage unit 1341 and/or the second storage unit 1351 according to the application list.
  • the first electronic device 1340 can include a control unit 1345 for controlling the various units.
  • the second electronic device 1350 can include a control unit 1352 for controlling the various units.
  • the first electronic device 1340 can be an electronic device 1000 in accordance with one embodiment.
  • the first electronic device can conveniently acquire an application list of applications installed on the second electronic device, and associate the application in the application list with the first storage unit and/or The file of the corresponding file type in the second storage unit, thereby conveniently selecting an application to open the file using the first electronic device or the second electronic device, improves the user experience.
  • FIG. 14 is a flowchart of an application backup method according to an embodiment of the present invention.
  • the backup method of the application can be applied to a system including at least a first electronic device and a second electronic device, for example, a system formed by a base end (host device) and a pad end (tablet computer), and some electronic devices pass some kind of
  • the communication port is connected to enable communication between two electronic devices, for example, through a Hybrid port connection and communication.
  • the first client device is installed with the first client software
  • the second client device is installed with the second client software.
  • the two client softwares are not identical, and at least the applications are not identical.
  • the backup method may include:
  • Step 1401 The second electronic device receives a backup request sent by the first electronic device through the communication port.
  • the first electronic device sends a backup request to the second electronic device through the communication port, where the backup request includes application information of the second client software in the second electronic device that requests the backup,
  • the information of one application or multiple applications may be included, and the information may include the name of the application, the version number, and the like, as long as the application to be backed up can be identified.
  • the backup request may be triggered by the user operating the first electronic device, or the trigger condition may be preset in the first electronic device. When the running or storage state of the first electronic device reaches the trigger condition, the trigger is automatically triggered.
  • the second electronic device sends a backup request.
  • Step 1402 The second electronic device searches for an application of the second client software that is requested to be backed up. After receiving the backup request sent by the first electronic device, the second electronic device parses the request, obtains information of the application that needs to be backed up, such as the identification information such as the name and the version number, and then stores the second information locally stored in the second electronic device. Find the application you need in the client software.
  • the identification information list of all applications of the second client software may be pre-stored in the second electronic device, where the second electronic device first searches for the application required by the first electronic device in the list, if not And feeding back the search result to the first electronic device, and then terminating the backup process, and if present, further extracting all information of the required application, such as an installer and the like.
  • Step 1403 The second electronic device sends the found application of the second client software to the first electronic device through the communication port, so that the first electronic device performs backup.
  • the second electronic device After finding the information about the application required by the first electronic device, the second electronic device sends the information to the first electronic device through the communication port, and after receiving the first electronic device, the first electronic device performs backup, and the device can be directly installed and operated. It is also possible to store the received information locally on the first electronic device and to run it during use. If the first electronic device locally stores the identification information list of all applications of the first client software, the list may be updated at the same time, and the identification information of the backed up application is added to the list.
  • the first electronic device and the second electronic device may first send a list of the identification information of the respective stored applications to the other party through the communication port, so that the two electronic devices are in accordance with the list. Determining the application that can be backed up, and then sending the backup.
  • “first" and “second” are relatively speaking, not specifically or limited, as long as the backup process is applied between the two electronic devices. It can be implemented by the above method, and is within the protection scope of the present application.
  • the communication between the two electronic devices is performed through the communication port, and the backup of the application between different client softwares is directly completed, and the installation of the entire client software is not required.
  • the method quickly realizes the application backup and simplifies the operation. Process, improving backup efficiency.
  • FIG. 15 is a flowchart of another application backup method according to an embodiment of the present invention.
  • the first electronic device is used as the base end, and the second electronic device is described by taking the pad end as an example.
  • the base end and the pad end are connected and communicated through the Hybrid port.
  • the first client software is installed on the base end, and the second client software is installed on the pad side.
  • the applications in the two client softwares are not identical.
  • the backup method can include:
  • Step 1501 The base end and the pad end are connected through a Hybrid port.
  • Step 1502 The base end generates a backup request, and sends the backup request to the pad end through the Hybrid port.
  • the base end When the base end detects that it is connected to the pad end through the Hybrid port, it can trigger the desktop to generate a desktop shortcut on the base side, and the shortcut includes a backup function item to trigger the application backup.
  • the base end receives the backup instruction triggered by the user operating the backup function item in the desktop shortcut, a backup request is generated, and the backup request is sent to the pad end through the communication port.
  • the backup request includes application identification information of the second client software in the pad end that requests the backup, and the application identification information may be a backup directory preset by the user at the base end.
  • the above process is not limited to backup between the base and pad ends, but can also be used for backup between any other two electronic devices that can communicate.
  • Step 1503 When the pad end is in the sleep state, the Hybrid port sends a wake-up command to wake up the pad end.
  • the Hybrid port needs to first perform a wake-up operation on the pad end. Specifically, the Hybrid port sends a wake-up instruction to the pad end, and after the pad end is woken up to enter the working state, the Hybrid is sent to the Hybrid. The port feedback enters the working state information, and then the Hybrid port sends a backup request of the base end to the pad end.
  • Step 1504 After the pad end wakes up, it receives the backup request of the base end sent by the Hybrid port.
  • Step 1505 The pad side searches for an application that requests backup, and packages the found application.
  • Pad side parses the backup request and obtains the application identification information of the required backup, it can locally find relevant information of the required application, such as an installer, and then package all the found applications.
  • Step 1506 The pad end sends the packaged application to the base end through the Hybrid port.
  • the base end stores the packaged application and stores it locally.
  • a similar step process can be performed for backup. After the backup of the application between different client softwares is completed, and the installation of the entire client software is not required, the method quickly implements the application backup, simplifies the operation process, and improves the backup efficiency.
  • FIG. 16 a schematic structural diagram of an electronic device according to an embodiment of the present invention is shown.
  • the electronic device is equipped with client software, which is connected to another electronic device through a communication port, and another client device is installed in the other electronic device.
  • the electronic device can include:
  • the request receiving unit 1601 is configured to receive a first backup request sent by another electronic device by using a communication port, where the first backup request includes application information of the client software in the electronic device that is requested to be backed up;
  • the application searching unit 1602 is configured to search for an application of the client software in the electronic device that is requested to be backed up;
  • the application sending unit 1603 is configured to send the found application to another electronic device through the communication port, so that another electronic device performs backup.
  • the request receiving unit 1601 of the electronic device receives, by using the communication port, a backup request sent by another electronic device, where the backup request includes application information of the client software in the electronic device that is requested to be backed up, where the application may include one application or multiple applications.
  • the information may include the name of the application, the version number, and the like, as long as the application to be backed up can be identified.
  • the application searching unit 1602 parses the request, obtains information of the application that needs to be backed up, such as name, version number, and the like, and then searches for the locally stored client software. Required application. After finding information about an application required by another electronic device, the application transmitting unit 1603 transmits to another electronic device through the communication port.
  • the electronic device may further include a state switching unit, configured to use the communication port according to the communication port The wake-up command sent, enters the working state.
  • the electronic device directly completes the backup of the application between different client softwares through the foregoing unit, and does not need to install the entire client software on another electronic device, and the method quickly realizes the application backup, which simplifies. The operation process improves the backup efficiency.
  • FIG. 17 a schematic structural diagram of another electronic device according to an embodiment of the present invention is shown.
  • the electronic device may include a request receiving unit 1701, an application searching unit 1702, and an application sending unit 1703 to receive a first backup request of another electronic device, and before backing up the application to another electronic device,
  • the following units are included to send a second backup request to other electronic devices to obtain an application backup on other electronic devices:
  • the creating unit 1704 is configured to generate a desktop shortcut that includes a backup function item when detecting that the electronic device is connected through the communication port;
  • the request triggering unit 1705 is configured to receive a backup instruction triggered by the user operating the backup function item, and generate a second backup request.
  • the request sending unit 1706 is configured to send a second backup request to another electronic device through the communication port.
  • the electronic device directly completes the backup of the application between different client softwares through the foregoing unit, and does not need to install the entire client software on the electronic device, the method quickly realizes the application backup, and simplifies the operation. Process, improving backup efficiency.
  • the electronic device may specifically be a Base end or a Pad end.
  • FIG. 18 it is a schematic structural diagram of an application backup system according to an embodiment of the present invention.
  • the system may include a first electronic device 1801 and a second electronic device 1802, wherein the first electronic device 1801 is installed with the first client software, and the second electronic device 1802 is installed with the second client software, the first electronic device The 1801 is connected to the second electronic device 1802 via a communication port.
  • the second electronic device 1802 is configured to receive a backup request sent by the first electronic device 1801 through the communication port, where the backup request includes application information of the second client software that requests backup; and the second client software that searches for the requested backup The application of the found second client software is sent to the first electronic device 1801 through the communication port, so that the first electronic device 1801 performs backup.
  • the first electronic device 1801 is specifically configured to: when detecting that the second electronic device 1802 is connected through the communication port, generate a desktop shortcut that includes a backup function item; and receive the user operation backup function item triggered The backup command generates a backup request; the backup request is sent to the second electronic device 1801 through the communication port.
  • the second electronic device 1802 can also be configured to enter an active state according to the wake-up command sent by the communication port.
  • the first electronic device is a base end
  • the second electronic device is a Pad end
  • the first electronic device is a Pad end
  • the second electronic device is a Base end.
  • the communication port can be a Hybrid port.
  • an operation method is provided, which is applied to a first electronic device and a second electronic device, the second electronic device having a display screen, the method comprising: when detecting the When the first electronic device is connected to the second electronic device, sending, to the first electronic device, a first message indicating the connection; after receiving the first message, the first electronic device, the pre-installed application The attribute is set to be installable in the system interface with respect to the first electronic device; the first electronic device installs the application and the indication after receiving the first operation command to install the application from the user Sending, by the second electronic device, the second command to the second electronic device; after receiving the second command and the application, the second electronic device installs the application, and includes Sending a second message of the information of the icon of the application to the first electronic device; after receiving the second message, the first electronic device Generating an icon of the application on a display screen of the second electronic device, and property settings icon of the application program to be run and unload the system interface.
  • the user can install the application for the second electronic device in the system interface of the first electronic device, and after the application is installed, can be run and uninstalled in the system interface of the first electronic device.
  • the application thus increases user convenience.
  • FIG. 19 is a schematic flow chart showing an operation method according to an embodiment of the present invention.
  • an operation method according to an embodiment of the present invention is applied to a first electronic device and a second electronic device, and the second electronic device has a display screen, and the method includes: S1901, when detecting the first electronic device and the second When the electronic device is connected, sending a first message indicating the connection to the first electronic device; S1902, after receiving the first message, the first electronic device sets the attribute of the pre-installed application to be relative to the first electronic device S1903: After receiving the first operation command for installing the application from the user, sending, by the first electronic device, the application and the second command indicating that the application is installed to the second electronic device; S1904 After receiving the second command and the application, the second electronic device installs the application, and sends a second message including information for generating an icon of the application to the first electronic device; S1905, the first electronic device After receiving the second message, the device generates an icon of the application on the display screen of the second message, the
  • the downloaded application package of the second electronic device is first required. Copy to the shared storage area, and manually switch to the second electronic device side, then find the program in the file browser and install it, the user's operation is very cumbersome.
  • some tools are applied to one end of the first electronic device, such as a pea clip mobile assistant, or an itunes-like auxiliary tool for installing the application, the above auxiliary tool needs to be started to install the corresponding application.
  • additional processes such as connecting the second electronic device and pairing may be required, which may require installation of the device driver and a relatively time consuming connection pairing process.
  • the user's file of the application to be installed in the interface of the first electronic device is actually not installable, and the icon of the installed application is in the first
  • the attributes in the interface of an electronic device are also non-operational and non-unloadable.
  • the application package of the application to be installed is installable in the system interface, for example, the user can directly install by double-clicking the application package, or the user right clicks on the application.
  • the option to install the application package appears in the right-click menu.
  • the user may need to use a file browser or the like to find the application package and install it, but with the prior art The difference is that users do not need to use specialized tools to install the application package.
  • the second electronic device synchronizes the icon of the application to the first electronic device.
  • the first electronic device uses the display screen of the second electronic device as its own display screen, and the display on the display screen of the second electronic device is actually A display interface of an operating system of the first electronic device.
  • the first electronic device cannot see the application on its operation interface, and in order to enable the user to see the application in the first electronic device. , you need to synchronize the icon of the application to the first electronic device.
  • the icon of the application installed in the second electronic device is also synchronized to one end of the first electronic device, and the user can view and operate through the auxiliary tool.
  • the application is installed in the second electronic device, and will be included for generating the application.
  • the first electronic device After the message of the information of the icon of the program is sent to the first electronic device, the first electronic device directly generates an icon of the application on the display screen of the second electronic device, and sets the attribute of the icon of the application to the system interface. It can be run and can be uninstalled. In this way, the user can directly see the application in the system interface of the operating system of the first electronic device without special auxiliary tools, and directly perform operations on the system interface to run or uninstall the application, which can be significant Improve the convenience of users when using.
  • the method further includes: after the first electronic device receives a third command to uninstall the application from the user, sending a fourth command to uninstall the application to the second electronic device; After receiving the fourth command, the second electronic device uninstalls the application, and sends a third message indicating that the application has been uninstalled to the first electronic device; the first electronic device After receiving the third message, deleting an icon of the application on a display screen of the second electronic device.
  • the user may uninstall the application installed in the second electronic device in the system interface of the operating system of the first electronic device, at this time, the first electronic device and the second electronic device
  • the device can automatically perform the uninstallation of the application in the second electronic device and the deletion of the icon of the application in the interface of the first electronic device.
  • the display screen of the second electronic device actually displays the interface of the operating system of the first electronic device, and thus when from the first electronic device After the icon of the application is deleted on the interface, the user naturally no longer sees the icon of the application on the display of the second electronic device.
  • the first electronic device and the second electronic device use different operating systems.
  • the first electronic device may be a Windows operating system
  • the second electronic device may be an Android operating system.
  • the first electronic device and the second electronic device may also use other devices.
  • the operating system, the embodiments of the present invention are not intended to impose any limitation on this.
  • the first electronic device sets an attribute of the application to an icon that can be installed and used in the system interface by modifying a registry of an operating system of the first electronic device.
  • the properties are set to be runable and unloadable in the system interface.
  • the user can directly perform the above operation in the system interface of the operating system of the first electronic device.
  • the first electronic device can be modified by modifying the system registry The way to set the application's properties to installable, and set the properties of the application's icons to be runnable and unloadable.
  • the first electronic device can also perform other functions in other ways, and the embodiments of the present invention are not intended to limit the same.
  • the first electronic device and the second electronic device communicate via a hybrid connection.
  • a hybrid connection is usually used to communicate between the first electronic device and the second electronic device. Therefore, in the embodiment of the present invention, The transmission of commands and data between an electronic device and the second electronic device is also performed by means of the above-described hybrid connection.
  • the sending the application and the second command indicating that the application is installed to the second electronic device is specifically: sending the application to a cache area of the second electronic device.
  • the second electronic device when the application is sent to the second electronic device, the second electronic device needs to store the application, and then install the application in the second electronic device, so that the second electronic device needs Pre-set the area where the application is stored.
  • the application is stored in the cache area of the second electronic device. Since the cache area generally has a faster access speed, the speed at which the second electronic device installs the application can be relatively increased. Thereby improving the convenience of the user.
  • the application can also be stored in other storage areas of the second electronic device, such as a hard disk.
  • the above-described operation method according to the embodiment of the present invention installation, operation, and uninstallation of an application that needs to be installed in the second electronic device can be directly performed in an interface of an operating system of the first electronic device, and
  • the above processes are all performed in the background by the first electronic device and the second electronic device through communication with each other, and the user does not feel the above process.
  • the first electronic device may also display a message indicating the progress of the above process on the interface of the operating system, thereby facilitating the user to understand the installation progress of the application.
  • the most time-consuming is mainly two parts, that is, the application is sent to the second electronic device and the application is installed in the second electronic device, and the first electronic device can be in the operating system.
  • the two processes are combined to display the progress of installing the application, and can also be displayed separately.
  • those skilled in the art can understand that when the first electronic device needs to display and install the application
  • the message about the installation progress of the application needs to be transmitted to the first electronic device, for example, the first electronic device and the second electronic device may also be used. The way the hybrid connection between devices is carried out.
  • an electronic device connectable to another electronic device having a display screen
  • the electronic device comprising: an embedded controller, when detecting the other electronic device When connecting, generating a first message indicating the connection and transmitting the indication to the another electronic device; the controller, configured to, after receiving the first message, pre-installed application An attribute is set to be installable in a system interface with respect to the electronic device; after receiving a first operational command to install the application from a user, transmitting the application and a second command indicating installation of the application Receiving, from the another electronic device, a second message including information for generating an icon of the application; after receiving the second message, at the other electronic device
  • the icon of the application is generated on the display screen, and the properties of the icon of the application are set to be executable and unloadable in the system interface.
  • FIG. 20 is a schematic block diagram showing an electronic device corresponding to the above-described operation method according to an embodiment of the present invention.
  • the electronic device 2000 can be connected to another electronic device having a display screen.
  • the electronic device 2000 includes: an embedded controller 2001, when detecting a connection with another electronic device, generating a first indication of the connection Transmitting and transmitting the first message to another electronic device; the controller 2002, configured to: after receiving the first message, set an attribute of the pre-installed application to be installable in the system interface with respect to the electronic device 2000; After receiving the first operational command to install the application from the user, transmitting the application and a second command indicating the installation of the application to the another electronic device; receiving, from the other electronic device, the icon containing the icon for generating the application a second message of information; after receiving the second message, generating an icon of the application on a display screen of another electronic device, and setting an attribute of the icon of the application to be operable and configurable in the system interface Uninstall.
  • the above-mentioned electronic device 2000 is the host end in the hybrid system, that is, the Base end, and the user actually uses the hybrid system to implement the above functions by operating the electronic device 2000.
  • the connection of the first electronic device and the second electronic device is generally detected by the embedded controller of the first electronic device.
  • the embodiment of the present invention is not limited thereto, and in other cases, it may also be by other controllers of the first electronic device or controllers of the second electronic device. A connection of the first electronic device and the second electronic device is detected.
  • an electronic device having a display screen and being connectable to another electronic device, the electronic device comprising: a controller, an embedded controller from the another electronic device Receiving a first message indicating a connection with the another electronic device; receiving an application from the another electronic device and a second command indicating installation of the application, wherein an attribute of the application is set to Installable in the system interface relative to the other electronic device; after receiving the second command and the application, installing the application and including information for generating an icon of the application Transmitting the second message to the another electronic device; wherein, after receiving the second message, the another first electronic device generates the application on a display screen of the second electronic device Icon, and set the properties of the application's icon to be runnable and unloadable in the system interface.
  • FIG. 21 is a schematic block diagram showing another electronic device according to an embodiment of the present invention.
  • the electronic device 2100 has a display 2101 and can be connected to another electronic device.
  • the electronic device 2100 includes: a controller 2102, which receives an indication of connection with another electronic device from an embedded controller of another electronic device.
  • a first message receiving an application from another electronic device and a second command indicating installation of the application, wherein an attribute of the application is set to be installable in a system interface with respect to another electronic device; After the second command and the application, installing the application, and transmitting a second message containing information for generating an icon of the application to another electronic device; wherein the another first electronic device is receiving After the second message, an icon of the application is generated on the display of the second electronic device, and the properties of the icon of the application are set to be runable and unloadable in the system interface.
  • the electronic device 2100 is a tablet terminal in a hybrid system, that is, a Pad terminal.
  • the Base terminal uses the display of the Pad terminal as a display of the hybrid system for display. Therefore, what is displayed on the display screen 2101 of the electronic device 2100 is actually an interface of the operating system at the base end.
  • an attach message is sent by the Embedded Controller.
  • the AppInstallService on the Base side obtains the message inserted on the Pad, the operating system registry is modified. Way, automatically add in the right-click menu of the file type of the Pad program (such as the installer of the Android system for the apk file) Add the "Install to Pad” option and set it to the default open mode.
  • the AppInstallService sends the installer command to the Pad, and sends the entire package to the cache area of the Pad through the hybrid connection in the form of a data stream.
  • the Pad terminal After receiving the command and program data package, the Pad terminal automatically installs the package, and sends the application name, package name, icon, and the like to the base end through the hybrid connection in XML format.
  • the AppInstallService on the base side will generate the shortcut icon of the above Pad program, and add the "Delete program on the Pad side" option in the right-click menu of the icon.
  • the user selects the "Delete program on the Pad side” option in the right-click menu of the icon, and the AppInstallService sends a command to delete the program to the Pad side through the hybrid connection.
  • the Pad After receiving the command, the Pad automatically deletes the corresponding package and replies to the message through the hybrid connection. After receiving the reply, the Base automatically deletes the shortcut icon of the Pad program.
  • the user does not need to install additional auxiliary tools, and does not need to perform connection pairing between the Base end and the Pad end, all data transmission is completed through the hybrid connection, and the user does not need to manually switch to the Pad end.
  • Installation and uninstallation of the program all steps can be completed on the Base side.
  • the corresponding program icon is automatically synchronized on the Base side, which is convenient for users to run and uninstall.
  • the installation, operation, and uninstallation of the application that needs to be installed in the second electronic device can be directly completed in the system interface of the operating system of the first electronic device, thereby improving the user's Convenience.
  • the computer software product can be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, a network device, etc.) to execute.
  • a computer device which can be a personal computer, a server, a network device, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Stored Programmes (AREA)

Abstract

本申请实施例公开了一种应用管理方法及设备,应用于与第二设备连接的第一设备,该方法包括:映射所述第二设备中的至少一个应用,获得对应的至少一个应用标识;检测第一操作;当所述第一操作满足第一预设条件时,从所述至少一个应用标识中确定第一应用的应用标识;检测第二操作;当所述第二操作满足第二预设条件时,依据所述第二操作获得对应的应用管理命令,并向所述第二设备发送所述应用管理命令,以使所述第二设备依据所述应用管理命令,管理所述第一应用。应用本申请实施例可以在第一设备中管理第二设备的应用,因此可以实现在不同设备的应用之间进行切换,提高了使用混合系统便携终端用户的用户体验。

Description

一种应用管理方法及设备
技术领域
本申请涉及通信技术领域,特别是涉及一种应用管理方法及设备。此外, 本法还涉及电子设备的领域, 更具体地, 本发明还涉及一种同步方法和电子 设备。 此外, 本发明还涉及一种关联方法、 电子设备和混合系统。 此外, 本 发明还涉及一种应用备份方法、 电子设备及系统。 背景技术
混合架构 (Hybrid ) 系统, 是指 2个(含 2个) 以上系统组成在一起, 例如在现有的一个系统的基础上, 嵌入其它至少另一个系统(包括另一个 PC系统或者嵌入式系统等)不同系统之间可以融合工作, 共享信息和设备, 发挥各自优势。
发明人在对现有技术的研究过程中发现,由于混合架构系统具有各自独 立的操作系统, 因此其中任意一个操作系统无法调用和管理另一个操作系统 中的应用, 因此影响了使用混合系统便携终端用户的用户体验。
此外, 近年来, 已经出现各种能够记录数据的电子设备, 用户可能使用 不同的电子设备记录相同类型的数据。 例如, 用户可能使用手机的电话簿来 记录一部分电话号码, 同时可能使用电脑来记录另外的一部分电话号码。 因 此, 将各种电子设备上记录的各种数据进行同步是非常有必要的。
在现有技术的同步方法中, 只存在将两个设备用数据线进行连接,从而 将特定数据同步以维持两者的特定数据的一致性。 然而, 这样的同步方法过 于简单, 不能够满足目前用户的各种复杂的需求。
此外, 近年来, 已经出现各种能够记录和再现内容的电子设备, 用户可 能使用不同的电子设备记录和再现相同类型的内容。 例如, 用户可能使用 Pad来记录和再现电影, 同时可能使用台式电脑来记录和再现相同的电影。 但是, Pad和台式电脑的功耗以及性能显然是不同的, 因此, 根据不同场合 的需要, 用户可能想要选择不同的电子设备来记录和再现内容。
在现有技术的方法中, 只存在将两个设备用数据线进行连接, 然后从一 个电子设备上手动运行另一个电子设备上的应用程序, 然后通过该应用程序 打开另一个电子设备上的内容的方式。 然而, 这样的方式是不方便的, 带给 用户的体验较差。
此外, 随着软件技术的不断发展, 各种应用于电脑、 手机等电子设备的 客户端软件越来越多。 当用户需要备份某一客户端软件的某些应用时, 可以 首先在电子设备上安装该客户端软件, 例如 Android, 然后再查找该软件中 需备份的应用, 再将这些应用备份到电子设备本地。
上述通过安装客户端软件实现应用备份的方法不仅操作过程繁瑣,效率 低。 发明内容
本申请实施例提供了一种应用管理方法及设备,以解决现有混合系统便 携终端难以在主系统控制下调用从系统应用, 导致用户体验下降的问题。
为了解决上述技术问题, 本申请实施例公开了如下技术方案: 一种应用管理方法, 应用于与第二设备连接的第一设备, 方法包括: 映 射第二设备中的至少一个应用, 获得对应的至少一个应用标识; 检测第一操 作; 当第一操作满足第一预设条件时, 从至少一个应用标识中确定第一应用 的应用标识; 检测第二操作; 当第二操作满足第二预设条件时, 依据第二操 作获得对应的应用管理命令, 并向第二设备发送应用管理命令, 以使第二设 备依据应用管理命令, 管理第一应用。
一种应用管理设备, 应用管理设备作为第一设备, 与第二设备连接, 第 一设备包括: 映射单元, 用于映射第二设备中的至少一个应用, 获得对应的 至少一个应用标识; 第一检测单元, 用于检测第一操作; 确定单元, 用于当 第一操作满足第一预设条件时,从至少一个应用标识中确定第一应用的应用 标识; 第二检测单元, 用于检测第二操作; 管理单元, 用于当第二操作满足 第二预设条件时, 依据第二操作获得对应的应用管理命令, 并向第二设备发 送应用管理命令, 以使第二设备依据应用管理命令, 管理第一应用。
由上述实施例可以看出, 本申请实施例中第一设备连接第二设备, 第一 设备映射第二设备中的至少一个应用, 获得对应的至少一个应用标识, 检测 第一操作, 当第一操作满足第一预设条件时, 从至少一个应用标识中确定第 一应用的应用标识, 检测第二操作, 当第二操作满足第二预设条件时, 依据 第二操作获得对应的应用管理命令, 并向第二设备发送应用管理命令, 以使 第二设备依据该应用管理命令管理第一应用。 应用本申请实施例, 可以实现 通过第一设备对第二设备中的应用进行管理, 当两个设备结合在一起工作 时, 要使用第二设备中的应用时, 无需要切换到第二设备单独工作的状态, 可以在第一设备中管理第二设备的应用, 因此可以实现在不同设备的应用之 间进行切换, 提高了使用混合系统便携终端用户的用户体验。
此外,根据本发明的另一实施例的应用管理方法中, 映射第二设备中的 至少一个应用可包括: 检测与第二电子设备的数据连接, 获得检测结果; 当 检测结果表明第一电子设备与第二电子设备的数据连接成功时,从第二电子 设备获得应用列表, 应用列表包括至少一个第二电子设备中安装的应用; 以 及根据应用列表, 创建至少一个与应用列表中的一个应用对应的应用标识, 其中,应用标识被触发后,能够在第二电子设备中启动应用标识对应的应用。
根据本发明另一实施例的电子设备还可包括: 检测单元, 配置为检测与 第二电子设备的数据连接, 获得检测结果; 映射单元包括下述单元: 获取单 元, 配置为当检测结果表明电子设备与第二电子设备的数据连接成功时, 从 第二电子设备获得应用列表,应用列表包括至少一个第二电子设备中安装的 应用; 以及创建单元, 配置为根据应用列表, 创建至少一个与应用列表中的 一个应用对应的应用标识, 其中, 应用标识被触发后, 能够在第二电子设备 中启动应用标识对应的应用。
通过根据本实施例的方法和电子设备,可以方便地获取另一电子设备上 安装的应用的应用列表, 并创建与应用对应的应用标识, 从而可以方便地启 动另一电子设备上安装的应用。
在根据本发明的另一实施例的应用管理方法中,还包括:根据应用列表, 第一电子设备关联应用列表中的应用和第一存储单元和 /或第二存储单元中 的对应文件类型的文件。
在根据本发明另一实施例的应用管理方法中,还包括: 在激活第一存储 单元和第二存储单元中存储的文件时, 显示包括与可激活文件的应用对应的 标识的图形用户界面, 其中可激活文件的应用包括第一电子设备本地安装的 应用和第二电子设备中安装的应用。
根据本发明另一实施例的电子设备其中第二电子设备包括第二存储单 元, 电子设备还包括: 第一存储单元, 配置为存储各种用户和文件; 关联单 元,配置为根据应用列表, 关联应用列表中的应用和第一存储单元和 /或第二 存储单元中的对应文件类型的文件。
根据本发明另一实施例的电子设备还包括: 显示单元, 配置为在激活第 一存储单元和第二存储单元中存储的文件时,显示包括与可激活文件的应用 对应的标识的图形用户界面, 其中可激活文件的应用包括电子设备本地安装 的应用和第二电子设备中安装的应用。
根据本发明另一实施例,提供了一种混合系统, 包括第一电子设备和第 二电子设备, 第一电子设备包括具有第一操作系统的第一硬件系统, 第二电 子设备包括具有第二操作系统的第二硬件系统, 其中第二电子设备包括: 第 二存储单元, 配置为存储各种用户和文件, 第一电子设备包括: 第一存储单 元, 配置为存储各种用户和文件; 检测单元, 配置为获得一检测结果; 获取 单元, 配置为当检测结果满足预定条件时, 从第二电子设备获得应用列表, 应用列表包括至少一个第二电子设备中的应用, 第二电子设备包括第二存储 单元; 以及关联单元, 配置为根据应用列表, 关联应用列表中的应用和第一 存储单元和 /或第二存储单元中的对应文件类型的文件。
利用根据本实施例的方法、 电子设备和混合系统, 其能够关联不同设备 上的应用和文件, 从而方便地打开文件。
此外,根据本发明的另一实施例的应用管理方法还包括: 第二电子设备 接收第一电子设备通过通信端口发送的备份请求,备份请求中包括请求备份 的第二客户端软件的应用信息; 第二电子设备查找所请求备份的第二客户端 软件的应用; 第二电子设备通过通信端口向第一电子设备发送查找到的第二 客户端软件的应用, 以使第一电子设备进行备份。
此外, 根据本发明的另一实施例的电子设备还包括: 请求接收单元, 用 于接收另一电子设备通过通信端口发送的第一备份请求, 第一备份请求中包 括请求备份的电子设备中客户端软件的应用信息; 应用查找单元, 用于查找 所请求备份的电子设备中客户端软件的应用; 应用发送单元, 用于通过通信 端口向另一电子设备发送查找到的应用, 以使另一电子设备进行备份。
此外, 根据本发明的另一实施例, 提供了一种应用备份系统, 其特征在 于, 包括第一电子设备和第二电子设备, 第一电子设备上安装有第一客户端 软件, 第二电子设备上安装有第二客户端软件, 第一电子设备与第二电子设 备通过通信端口连接, 第二电子设备, 用于接收第一电子设备通过通信端口 发送的备份请求, 备份请求中包括请求备份的第二客户端软件的应用信息; 查找所请求备份的第二客户端软件的应用; 通过通信端口向第一电子设备发 送查找到的第二客户端软件的应用, 以使第一电子设备进行备份。
通过本的方法、 以及相应的电子设备及系统, 在两电子设备之间通过通 信端口进行通信时, 可直接完成了不同客户端软件之间应用的备份, 而无需 进行整个客户端软件的安装, 快速实现了应用备份, 简化了操作过程, 提高 了备份效率。
此外, 根据本发明另一实施例, 第二电子设备具有显示屏, 应用管理方 法还可包括: 当检测到第一电子设备与第二电子设备连接时, 向第一电子设 备发送指示该连接的第一消息; 第一电子设备在接收到第一消息后, 将预安 装的应用程序的属性设置为相对于第一电子设备在系统界面中可安装; 第一 电子设备在从用户接收到安装应用程序的第一操作命令后,将应用程序和指 示安装应用程序的第二命令发送到第二电子设备; 第二电子设备在接收到第 二命令和应用程序之后, 安装应用程序, 并将包含用于生成应用程序的图标 的信息的第二消息发送到第一电子设备; 第一电子设备在接收到第二消息之 后, 在第二电子设备的显示屏上生成应用程序的图标, 并将应用程序的图标 的属性设置为在系统界面中可运行和可卸载。
此外, 根据本发明的另一实施例的电子设备还包括: 嵌入控制器, 当检 测到与另一电子设备的连接时, 生成指示该连接的第一消息并向另一电子设 备发送指示第一消息; 控制器, 被配置为在接收到第一消息后, 将预安装的 应用程序的属性设置为相对于电子设备在系统界面中可安装; 在从用户接收 到安装应用程序的第一操作命令后,将应用程序和指示安装应用程序的第二 命令发送到另一电子设备; 从另一电子设备接收包含用于生成应用程序的图 标的信息的第二消息; 在接收到第二消息之后, 在另一电子设备的显示屏上 生成应用程序的图标, 并将应用程序的图标的属性设置为在系统界面中可运 行和可卸载。
此外, 根据本发明的另一实施例的电子设备还包括: 控制器, 从另一电 子设备的嵌入控制器接收指示与另一电子设备的连接的第一消息; 从另一电 子设备接收一应用程序和指示安装应用程序的第二命令, 其中, 应用程序的 属性被设置为相对于另一电子设备在系统界面中可安装; 在接收到第二命令 和应用程序之后, 安装应用程序, 并将包含用于生成应用程序的图标的信息 的第二消息发送到另一电子设备; 其中, 另一第一电子设备在接收到第二消 息之后, 在第二电子设备的显示屏上生成应用程序的图标, 并将应用程序的 图标的属性设置为在系统界面中可运行和可卸载。
通过根据本发明实施例的操作方法和电子设备,可以直接在第一电子设 备的操作系统的系统界面中完成需要在第二电子设备中安装的应用程序的 安装、 运行和卸载, 从而提高用户的便利度。 附图说明
为了更清楚地说明本申请实施例或现有技术中的技术方案,下面将对实 施例或现有技术描述中所需要使用的附图作简单地介绍, 显而易见地, 对于 本领域普通技术人员而言, 在不付出创造性劳动性的前提下, 还可以根据这 些附图获得其他的附图。
图 1为本申请应用管理方法的第一实施例流程图;
图 2为本申请应用管理方法的第二实施例流程图;
图 3为本申请应用管理方法的第三实施例流程图;
图 4为本申请应用管理方法的第四实施例流程图;
图 5为本申请应用管理设备的第一实施例框图;
图 6为本申请应用管理设备的第二实施例框图;
图 7是图示根据本发明实施例的同步方法的流程图;
图 8是图示根据本发明实施例的电子设备的配置的框图;
图 9是描述根据本发明一个实施例的关联方法的流程图;
图 10是描述根据本发明一个实施例的电子设备的框图;
图 11是描述根据本发明另一实施例的关联方法的流程图;
图 12是描述根据本发明另一实施例的电子设备的框图;
图 13是描述根据本发明一个实施例的混合系统的框图;
图 14是本发明实施例的一种应用备份方法流程图;
图 15是本发明实施例的另一种应用备份方法的流程图;
图 16是本发明实施例的一种电子设备的结构示意图;
图 17是本发明实施例的另一种电子设备的结构示意图;
图 18是本发明实施例的一种应用备份系统的结构示意图;
图 19是示出根据本发明实施例的操作方法的示意性流程图;
图 20是示出根据本发明实施例的电子设备的示意性框图; 图 21是示出根据本发明实施例的另一电子设备的示意性框图。 具体实施方式
本发明如下实施例提供了一种应用管理方法及设备。这些实施例应用在 与第二设备连接的第一设备中。
为了使本技术领域的人员更好地理解本发明实施例中的技术方案 ,并使 本发明实施例的上述目的、 特征和优点能够更加明显易懂, 下面结合附图对 本发明实施例中技术方案作进一步详细的说明。
参见图 1 , 为本申请应用管理方法的第一实施例流程图:
步骤 101 : 映射第二设备中的至少一个应用, 获得对应的至少一个应用 标识。
具体的, 第一设备向第二设备发送获取第二设备中已运行应用的请求, 接收第二设备根据该请求返回的应用列表, 该应用列表中包含第二设备中已 运行应用的应用标识; 或者, 第一设备向第二设备发送获取第二设备中未运 行应用的请求, 接收第二设备根据该请求返回的应用列表, 该应用列表中包 含第二设备中未运行应用的应用标识; 或者, 第一设备也可以向第二设备发 送获取第二设备中所有应用的请求, 并接收第二设备根据该请求返回的应用 列表, 该应用列表中的每个应用标识可以进一步包含对应的应用是否已经启 动的信息。
步骤 102: 检测第一操作。
该第一操作可以具体为通过输入设备执行的输入操作,输入设备可以包 括鼠标、 键盘、 触摸板等, 其中触摸板可以单独设置, 也可以与显示单元重 叠设置组成触摸显示屏。
步骤 103: 当第一操作满足第一预设条件时, 从至少一个应用标识中确 定第一应用的应用标识。
第一操作满足第一预设条件可以具体为通过输入设备执行第一操作的 操作对象是至少一个应用标识中的应用标识,将第一操作对应的应用标识确 定为第一应用的应用标识。
步骤 104: 检测第二操作。
第二操作可以具体为通过输入设备对第一应用的应用标识的操作,即对 前述确定的第一应用的应用标识进行的操作。通常,输入设备可以包括鼠标、 键盘、 触摸板等, 其中触摸板可以单独设置, 也可以与显示单元重叠设置组 成触摸显示屏。
步骤 105 : 当第二操作满足第二预设条件时, 依据第二操作获得对应的 应用管理命令。
第二操作满足第二预设条件可以具体为对该第一应用的应用标识的操 作是与预设的管理命令对应的操作。 其中, 管理命令可以包括但不限于对应 于第一应用的切换命令、 关闭命令、 启动命令等。
步骤 106 : 向第二设备发送该应用管理命令, 以使第二设备依据该应用 管理命令管理第一应用。
其中, 向第二设备发送应用管理命令可以包括: 向第二设备发送切换到 第二状态的切换命令, 以使第二设备在第二状态下执行第一应用; 或者, 向 第二设备发送关闭第一应用的关闭命令, 以使第二设备结束第一应用的进 程; 或者, 向第二设备发送启动第一应用的启动命令, 以使第二设备启动该 第一应用。
本申请应用管理方法实施例可以应用在第一设备中,第一设备与第二设 备连接, 比如连接的智能手机和笔记本计算机; 优选的, 连接的两个设备可 组成双系统的便携终端。 其中, 第一设备包括第一硬件系统, 比如基于 X86 架构或 ARM架构处理器的硬件系统, 运行第一操作系统, 比如桌面设备操作 系统(如 Windows , L inux或 MacOS等)或便携设备操作系统(如 Android , Symbian或 iOS等), 第二设备包括第二硬件系统, 比如基于 X86架构或 ARM 架构处理器的硬件系统, 运行第二操作系统, 比如桌面设备操作系统(如 Windows , Linux或 MacOS等 )或便携设备操作系统 (如 Android, Symbian 或 iOS等), 其中第二设备的第二操作系统中安装至少一个应用。 可见第一 硬件系统和第二硬件系统可以基于相同的架构, 也可以基于不同的架构; 第 一操作系统和第二操作系统可以是相同类型的操作系统也可以是不同类型 的操作系统。 比如, 第一设备为基于 X86架构处理器且运行 Windows操作系 统的设备,第二设备为基于 ARM架构处理器且运行 Android操作系统的设备; 或者第一设备为基于 X86架构处理器且运行 Windows操作系统的设备, 第二 设备为基于 ARM架构处理器且运行 Windows操作系统(比如 Windows 8 )的设 备。
此外,第一设备和第二设备可以是依据重要性或优先级或处理能力或功 耗对两个设备进行的区分(例如, 第一设备对应重要性高、 优先级高、 处理 能力强或功耗大, 而第二设备与上述相反; 或者第二设备对应重要性高、 优 先级高、 处理能力强或功耗大, 而第一设备与上述相反), 也可以仅仅是为 了命名的区分, 并非限定系统的重要性或优先级或处理能力或功耗。
在组成的双系统便携终端中, 第一设备还包括显示单元, 该显示单元显 示第一操作系统运行的状态为第一设备的第一状态,显示单元显示第二操作 系统运行的状态为第一设备的第二状态。
在一个具体的应用实例中, 该第一设备优选的, 为包括主机(含第一处 理单元, 比如 X86处理器)和显示屏的设备, 也可称为 BASE设备, 该设备 与通常所见的笔记本电脑或一体机外形一致, 第二设备可以优选的为一集成 了独立操作系统的板卡(含第二处理单元, 比如 ARM处理器), 也可称为 PAD 设备, 该板卡通过第一设备上设置的插槽, 插入该插槽中, 与第一设备结合 为双系统的便携终端;
在另一个具体的应用实例中,该第二设备优选的为不含显示屏主机设备 (含第二处理器, 比如 X86处理器), 第一设备优选为触摸显示设备(含第 一处理器, 比如 ARM处理器), 第二设备内安装第二操作系统, 第一设备内 安装第一操作系统, 第一设备集成显示屏, 第一设备和第二设备连接在一起 组成双系统便携终端, 第一设备和第二设备可以分离使用或组合使用。
参见图 2 , 为本申请应用管理方法的第二实施例流程图, 该实施例示出 了向第二设备发送切换命令的应用管理过程:
步骤 201 : 第一设备在第一状态下, 向第二设备发送获取第二设备中已 运行应用的请求。
当第一设备连接第二设备时, 第一设备可以通过有线(比如数据总线 ( USB/UART ) )或无线(比如 WIFI ) 的方式向第二设备发送获取第二设备中 已运行应用的请求。 其中, 当第一设备为双系统便携终端的 BASE设备时, BASE设备可以通过预设进程(例如, Hybr idServ i ce进程)向第二设备发送 请求。
步骤 202 : 接收第二设备根据该请求返回的应用列表, 该应用列表中包 含第二设备中已运行应用的应用标识。
第二设备接收到请求后, 可以查找已经运行的各个应用, 获取这些已运 行应用的应用列表。 其中, 当第二设备为双系统便携终端的 PAD设备时, 该 PAD设备可以通过预设进程(例如, PadAc t iv i tyManager进程)获取包含已 运行应用的应用标识的应用列表, 然后将该应用列表通过有线或无线方式返 回给 BASE设备。 或者, 也可以由 BASE设备通过预设进程按照有线或无线方 式到 PAD设备内获取该应用列表。
当第一设备接收到第二设备根据该请求返回的应用列表后,该第一设备 可以将应用列表中所有应用的应用标识以快捷方式显示在第一操作系统对 应的桌面上, 或者将应用列表中所有应用的应用标识单独保存在某个文件夹 下 (例如, 名称为 PADApp的文件夹), 以供用户查看。
步骤 203: 检测通过输入设备执行的输入操作。
输入设备可以包括鼠标、 键盘、 触摸板等, 其中触摸板可以单独设置, 也可以与显示单元重叠设置组成触摸显示屏。
步骤 204:当第一操作的操作对象是至少一个应用标识中的应用标识时, 从至少一个应用标识中确定第一应用的应用标识。
由于当前处于第一状态, 因此显示单元显示第一操作系统的运行状态, 在第一状态下当检测到第一操作的操作对象是应用列表中的某个应用标识 时, 可以确定该应用标识对应的应用为第一应用, 即当前要对第二设备中已 开启的应用中的第一应用进行管理操作。
步骤 205 : 检测通过输入设备对该第一应用的应用标识的操作。
输入设备可以包括鼠标、 键盘、 触摸板等, 其中触摸板可以单独设置, 也可以与显示单元重叠设置组成触摸显示屏。
步骤 206 : 当第二操作是与预设的管理命令对应的切换操作时, 获得对 应的切换命令。
当确定了第二操作是对第一应用的应用标识的操作时 ,可以根据用户选 择进一步确定对该第一应用需要进行何种管理。 例如, 对于已生成的第一应 用的应用标识的快捷方式, 当用户对该快捷方式选择切换选项时, 则生成对 应的切换命令, 以触发后续切换到第二状态的切换过程。
步骤 207 : 向第二设备发送切换到第二状态的切换命令, 以使第二设备 在第二状态下执行所述第一应用。
其中,第一设备可以通过有线或无线的方式向第二设备发送该第一应用 的应用名称和该切换命令。 例如, 当作为第一设备的 BASE设备将切换命令 发送给作为第二设备的 PAD设备时, PAD设备可以激活第二操作系统, 在第 二操作系统下继续执行该第一应用, 并将该第一应用激活到显示窗口的前 台, 供用户查看。
步骤 208: 控制显示单元切换到由第二设备进行控制。
对于具有双系统的便携终端来说,第一设备还可以控制显示单元切换到 由第二设备进行控制。
参见图 3 , 为本申请应用管理方法的第三实施例流程图:
步骤 301 : 第一设备在第一状态下, 向第二设备发送获取第二设备中已 运行应用的请求。
当第一设备连接第二设备时, 第一设备可以通过有线(比如数据总线 ( USB/UART ) )或无线(比如 WIFI ) 的方式向第二设备发送获取第二设备中 已运行应用的请求。 其中, 当第一设备为双系统便携终端的 BASE设备时, BASE设备可以通过预设进程(例如, Hybr idServi ce进程)向第二设备发送 请求。
步骤 302: 接收第二设备根据该请求返回的应用列表, 该应用列表中包 含第二设备中已运行应用的应用标识。
第二设备接收到请求后, 可以查找已经运行的各个应用, 获取这些已运 行应用的应用列表。 其中, 当第二设备为双系统便携终端的 PAD设备时, 该 PAD设备可以通过预设进程(例如, PadAct ivi tyManager进程)获取包含已 运行应用的应用标识的应用列表, 然后将该应用列表通过有线或无线方式返 回给 BASE设备。 或者, 也可以由 BASE设备通过预设进程按照有线或无线方 式到 PAD设备内获取该应用列表。
当第一设备接收到第二设备根据该请求返回的应用列表后,该第一设备 可以将应用列表中所有应用的应用标识以快捷方式显示在第一操作系统对 应的桌面上, 或者将应用列表中所有应用的应用标识单独保存在某个文件夹 下 (例如, 名称为 PADApp的文件夹), 以供用户查看。
步骤 303: 检测通过输入设备执行的输入操作。
输入设备可以包括鼠标、 键盘、 触摸板等, 其中触摸板可以单独设置, 也可以与显示单元重叠设置组成触摸显示屏。
步骤 304:当第一操作的操作对象是至少一个应用标识中的应用标识时, 从至少一个应用标识中确定第一应用的应用标识。
由于当前处于第一状态, 因此显示单元显示第一操作系统的运行状态 , 在第一状态下当检测到第一操作的操作对象是应用列表中的某个应用标识 时, 可以确定该应用标识对应的应用为第一应用, 即当前要对第二设备中已 开启的应用中的第一应用进行管理操作。
步骤 305: 检测通过输入设备对该第一应用的应用标识的操作。
输入设备可以包括鼠标、 键盘、 触摸板等, 其中触摸板可以单独设置, 也可以与显示单元重叠设置组成触摸显示屏。
步骤 306: 当第二操作是与预设的管理命令对应的关闭操作时, 获得对 应的关闭管理命令。
当确定了第二操作是对第一应用的应用标识的操作时 ,可以根据用户选 择进一步确定对该第一应用需要进行何种管理。 例如, 对于已生成的第一应 用的应用标识的快捷方式, 当用户对该快捷方式选择关闭选项时, 则生成对 应的关闭命令, 以触发后续关闭该第一应用的关闭过程。
步骤 307: 向第二设备发送关闭第一应用的关闭命令, 以使第二设备结 束第一应用的进程。
其中,第一设备可以通过有线或无线的方式向第二设备发送该第一应用 的应用名称和该关闭命令。 例如, 当作为第一设备的 BASE设备将关闭命令 发送给作为第二设备的 PAD设备时, PAD设备可以在后台执行关闭该第一应 用的操作。
当第一应用关闭后, 第二设备可以进一步将已关闭的结果通知第一设 备, 第一设备可以在已开启的应用列表中删除该第一应用, 或者标记该第一 应用为已关闭。
参见图 4 , 为本申请应用管理方法的第四实施例流程图:
步骤 401 : 第一设备在第一状态下, 向第二设备发送获取第二设备中未 运行应用的请求。
当第一设备连接第二设备时, 第一设备可以通过有线(数据总线
( USB/UART ) )或无线(WIFI ) 的方式向第二设备发送获取第二设备中未运 行应用的请求。 其中, 当第一设备为双系统便携终端的 BASE设备时, BASE 设备可以通过预设进程 (例如, Hybr idService进程 )向第二设备发送请求。
步骤 402: 接收第二设备根据该请求返回的应用列表, 该应用列表中包 含第二设备中未运行应用的应用标识。
第二设备接收到请求后, 可以查找未运行, 但可以运行的各个应用, 获 取这些未运行应用的应用列表。 其中, 当第二设备为双系统便携终端的 PAD 设备时, 该 PAD设备可以通过预设进程(例如, PadAc t i v i tyManager进程) 获取包含未运行应用的应用标识的应用列表, 然后将该应用列表通过有线或 无线方式返回给 BASE设备。 或者, 也可以由 BASE设备通过预设进程按照有 线或无线方式到 PAD设备内获取该应用列表。
当第一设备接收到第二设备根据该请求返回的应用列表后,该第一设备 可以将应用列表中所有应用的应用标识以快捷方式显示在第一操作系统对 应的桌面上, 或者将应用列表中所有应用的应用标识单独保存在某个文件夹 下 (例如, 名称为 PADApp的文件夹), 以供用户查看。
步骤 403: 检测通过输入设备执行的输入操作。
输入设备可以包括鼠标、 键盘、 触摸板等, 其中触摸板可以单独设置, 也可以与显示单元重叠设置组成触摸显示屏。
步骤 404:当第一操作的操作对象是至少一个应用标识中的应用标识时, 从至少一个应用标识中确定第一应用的应用标识。
由于当前处于第一状态, 因此显示单元显示第一操作系统的运行状态, 在第一状态下当检测到第一操作的操作对象是应用列表中的某个应用标识 时, 可以确定该应用标识对应的应用为第一应用, 即当前要对第二设备中未 启动的应用中的第一应用进行管理操作。
步骤 405 : 检测通过输入设备对该第一应用的应用标识的操作。
输入设备可以包括鼠标、 键盘、 触摸板等, 其中触摸板可以单独设置, 也可以与显示单元重叠设置组成触摸显示屏。
步骤 406 : 当第二操作是与预设的管理命令对应的启动操作时, 获得对 应的启动管理命令。
当确定了第二操作是对第一应用的应用标识的操作时 ,可以根据用户选 择进一步确定对该第一应用需要进行何种管理。 例如, 对于已生成的第一应 用的应用标识的快捷方式, 当用户对该快捷方式选择启动选项, 或者双机该 快捷方式触发启动时, 则生成对应的启动命令, 以触发后续启动该第一应用 的过程。
步骤 407 : 向第二设备发送启动第一应用的启动命令, 控制显示单元切 换到由第二设备进行控制。
其中,第一设备可以通过有线或无线的方式向第二设备发送该第一应用 的应用名称和该启动命令。 例如, 当作为第一设备的 BASE设备将启动命令 发送给作为第二设备的 PAD设备时, PAD设备可以激活第二操作系统, 在第 二操作系统下启动该第一应用并执行该第一应用, 并将该第一应用激活到显 示窗口的前台, 供用户查看。 进一步, 对于具有双系统的便携终端来说, 第 一设备还可以控制显示单元切换到由第二设备进行控制。
步骤 408 : 当第一应用启动后, 第一设备从第一状态切换到第二状态。 当第一应用启动后,第一设备控制显示单元显示第二操作系统运行的状 态, 此时第一设备切换到第二设备。
步骤 409 : 第一设备更新第一应用的应用标识为已启动的应用标识。 其中, 第一设备可以对应用列表中的第一应用的应用标识进行标记, 标 记其为已启动的应用; 或者, 第一设备也可以单独生成已启动应用列表, 将 第一应用从未启动应用列表中删除, 同时添加到该已启动应用列表中。
上述实施例中, 当第一应用启动后, 第一设备可以将第一应用添加到第 一操作系统的任务栏中。 如果用户在第二状态下退出该第一应用, 则第二设 备可以向第一设备发送退出命令, 使第一设备将该第一应用从任务栏中退 出; 用户也可以通过操作快捷键或者物理按键从第二状态切换回第一状态, 并在第一操作系统的任务栏中退出该第一应用, 然后通知第二设备第一应用 已经关闭, 由第二设备在第二操作系统下关闭该第一应用, 或者切换回第一 状态后, 通过点击任务栏中的该第一应用, 再次切换回第二状态, 并在第二 系统下执行该第一应用。
与本申请应用管理方法的实施例相对应,本申请还提供了应用管理设备 的实施例, 该应用管理设备作为第一设备, 与第二设备连接。
参见图 5 , 为本申请应用管理设备的第一实施例框图:
该应用管理设备包括:
映射单元 51 0 , 用于映射第二设备中的至少一个应用, 获得对应的至少 一个应用标识;
第一检测单元 520 , 用于检测第一操作;
确定单元 530 , 用于当所述第一操作满足第一预设条件时, 从所述至少 一个应用标识中确定第一应用的应用标识;
第二检测单元 540 , 用于检测第二操作;
管理单元 550 , 用于当所述第二操作满足第二预设条件时, 依据所述第 二操作获得对应的应用管理命令, 并向所述第二设备发送所述应用管理命 令, 以使所述第二设备依据所述应用管理命令, 管理所述第一应用。
上述实施例中, 所述第一操作包括: 通过输入设备执行的输入操作; 所述第一操作满足第一预设条件包括:所述第一操作的操作对象是所述 至少一个应用标识中的应用标识;
所述第二操作包括: 通过输入设备对所述第一应用的应用标识的操作; 所述第二操作满足第二预设条件包括:所述第二操作是与预设的管理命 令对应的操作。
参见图 6 , 为本申请应用管理设备的第二实施例框图:
该应用管理设备包括:
映射单元 61 0 , 用于映射第二设备中的至少一个应用, 获得对应的至少 一个应用标识;
第一检测单元 620 , 用于检测第一操作;
确定单元 630 , 用于当所述第一操作满足第一预设条件时, 从所述至少 一个应用标识中确定第一应用的应用标识;
第二检测单元 640 , 用于检测第二操作;
管理单元 650 , 用于当所述第二操作满足第二预设条件时, 依据所述第 二操作获得对应的应用管理命令, 并向所述第二设备发送所述应用管理命 令, 以使所述第二设备依据所述应用管理命令, 管理所述第一应用。
进一步,所述第一设备运行第一操作系统,第二设备运行第二操作系统, 所述至少一个应用安装在所述第二操作系统中; 所述第一设备还包括:
显示单元 660 , 所述显示单元 660显示第一操作系统运行的状态为第一 设备的第一状态, 所述显示单元显示第二操作系统运行的状态为第一设备的 第二状态。
在一个实施例中, 映射单元 61 0可以包括至少一个下述单元(图 6中未 示出 ):
第一映射单元,用于向所述第二设备发送获取所述第二设备中已运行应 用的请求, 并接收所述第二设备根据所述请求返回的应用列表, 所述应用列 表中包含所述第二设备中已运行应用的应用标识;
第二映射单元,用于向所述第二设备发送获取所述第二设备中未运行应 用的请求, 并接收所述第二设备根据所述请求返回的应用列表, 所述应用列 表中包含所述第二设备中未运行应用的应用标识。
在管理单元 650的第一个实施例中, 该管理单元 650可以包括(图 6中 未示出 ):
切换管理单元, 用于当所述第一设备在所述第一状态下, 由所述第一映 射单元向所述第二设备发送获取所述第二设备中已运行应用的请求时, 向所 述第二设备发送切换到所述第二状态的切换命令, 以使所述第二设备在所述 第二状态下执行所述第一应用。
在管理单元 650的第二个实施例中, 所述管理单元 650可以包括(图 6 中未示出 ):
关闭管理单元, 用于当所述第一设备在所述第一状态下, 由所述第一映 射单元向所述第二设备发送获取所述第二设备中已运行应用的请求时, 向所 述第二设备发送关闭所述第一应用的关闭命令, 以使所述第二设备结束所述 第一应用的进程。
在管理单元 650的第三个实施例中, 所述管理单元 650可以包括(图 6 中未示出):
启动管理单元, 用于当所述第一设备在所述第一状态下, 由所述第二映 射单元向所述第二设备发送获取所述第二设备中未运行应用的请求时, 向所 述第二设备发送启动所述第一应用的启动命令。
进一步, 该设备还可以包括:
切换单元 670 , 用于当所述第一应用启动后, 所述第一设备从所述第一 状态切换到所述第二状态。
更新单元 680 , 用于当所述第一应用启动后, 所述第一设备将所述第一 应用的应用标识更新为已启动的应用标识。
当应用上述管理单元 650的第一个实施例和第三个实施例时,该应用管 理设备还可以包括:
控制单元 690 , 用于当所述第一设备在所述第一状态下, 控制所述显示 单元切换到由所述第二设备控制。
上述实施例中, 所述第一操作包括: 通过输入设备执行的输入操作; 所述第一操作满足第一预设条件包括:所述第一操作的操作对象是所述 至少一个应用标识中的应用标识;
所述第二操作包括: 通过输入设备对所述第一应用的应用标识的操作; 所述第二操作满足第二预设条件包括:所述第二操作是与预设的管理命 令对应的操作。
通过对以上实施方式的描述可知 ,本申请实施例中第一设备连接第二设 备, 第一设备映射所述第二设备中的至少一个应用, 获得对应的至少一个应 用标识, 检测第一操作, 当第一操作满足第一预设条件时, 从至少一个应用 标识中确定第一应用的应用标识, 检测第二操作, 当第二操作满足第二预设 条件时, 依据第二操作获得对应的应用管理命令, 并向第二设备发送应用管 理命令, 以使第二设备依据该应用管理命令管理第一应用。 应用本申请实施 例, 可以实现通过第一设备对第二设备中的应用进行管理, 当两个设备结合 在一起工作时, 要使用第二设备中的应用时, 无需要切换到第二设备单独工 作的状态, 可以在第一设备中管理第二设备的应用, 因此可以实现在不同设 备的应用之间进行切换, 提高了使用混合系统便携终端用户的用户体验。
本发明实施例可以应用在由第一电子设备和第二电子设备组成的混合 架构 (hybrid ) 系统中, 其中, 混合架构系统可以是两个独立的电子设备组 合而成, 也可以包含第一电子设备和第二电子设备的一个便携电子设备。 比 如混合架构系统可以由一台独立单一系统的笔记本计算机和一台智能手机 组成, 也可以是具有混合架构系统的笔记本计算机。
如上所述, 第一电子设备可以包括第一硬件系统, 比如基于 X86架构或 ARM架构处理器的系统。 第二电子设备可以包括第二硬件系统, 比如基于 X86架构或 ARM架构处理器的系统。 即第一电子设备和第二电子设备可以 基于相同的硬件架构, 也可以依据不同的硬件架构。
进一步, 第一电子设备可以包括具有第一操作系统的第一硬件系统, 比 如安装有桌面设备操作系统(比如 Windows, Linux或 MacOS )或安装有便 携设备操作系统(比如 Android, Symbian或 iOS )的第一硬件系统。 第二电 子设备可以包括具有第二操作系统的第二硬件系统, 比如安装有桌面设备操 作系统(比如 Windows, Linux或 MacOS )或安装有便携设备操作系统(比 如 Android, Symbian或 iOS )的第二硬件系统。 即第一操作系统和第二操作 系统可以相同也可以不同, 只要可以运行在相应的硬件系统即可。 优选地, 第一电子设备是基于 X86架构处理器的,安装有桌面操作系统的系统, 第二 电子设备^^于 ARM架构处理器的, 安装有便携设备操作系统的系统。 将参考图 7描述根据本发明实施例的同步方法。图 7是图示根据本发明 实施例的同步方法的流程图。才艮据本发明实施例的同步方法应用于第一电子 设备(例如主机) 中, 用于与第二电子设备(例如 Pad )进行同步, 获取第 二电子设备上安装的应用的应用列表。
根据本发明实施例的同步方法包括:
步骤 S701 : 检测与第二电子设备的数据连接, 获得检测结果。
在该步骤中,第一电子设备通过各种方式检测与第二电子设备之间的数 据连接是否成功,并且获得检测结果。例如,第一电子设备可以通过如轮询, 触发等方式, 检测与第二电子设备之间的数据连接的状态, 并且获得检测结 果。
步骤 S702: 当所述检测结果表明所述第一电子设备与所述第二电子设 备的数据连接成功时, 从所述第二电子设备获得应用列表, 所述应用列表包 括至少一个所述第二电子设备中安装的应用。
在该步骤中, 当在步骤 S701中获得的检测结果指示第一电子设备和第 二电子设备之间的数据连接成功时, 第一电子设备可以从第二电子设备获取 第二电子设备的应用列表, 所述应用列表包括至少一个所述第二电子设备中 安装的应用。
进一步地, 例如, 当在步骤 S701中获得的检测结果指示第一电子设备 和第二电子设备之间的数据连接成功时, 所述第一电子设备可以向所述第二 电子设备发送用于获取所述第二电子设备中安装的应用的应用列表的请求, 然后接收所述第二电子设备响应于所述请求而发送的应用列表。在该处理过 程中, 由第一电子设备主动发送获取第二电子设备的应用列表的请求到第二 电子设备, 第二电子设备接收该请求之后, 开始获取本地已安装的应用的信 息, 然后将本地已安装的应用的应用列表通过已经建立的数据连接通道发送 给第一电子设备。
可替代地, 例如, 当在步骤 S701中获得的检测结果指示第一电子设备 和第二电子设备之间的数据连接成功时, 所述第二电子设备可以自动发送所 述应用列表。 在该处理过程中, 当第一电子设备和第二电子设备之间的数据 连接成功时, 第一电子设备可以不用发送获取第二电子设备的应用列表的请 求到第二电子设备, 相反, 由第二电子设备可以自动发送所述应用列表, 第 一电子设备可以直接接收由第二电子设备发送的包括所述第二电子设备中 安装的应用的应用列表。
此外, 例如第二电子设备可以将本地应用列表打包, 以 XML文件形式 发送给第一电子设备, 其中该 XML文件中包含每个应用的启动方式、 图标 等信息。
进一步地,第一电子设备可以从所述第二电子设备获得包括所述第二电 子设备中的所有应用的应用列表。 也就是说, 第一电子设备不管现在本地是 否已经存在关于第二电子设备中的应用, 直接获取包括所述第二电子设备中 的所有应用的应用列表。
可替代地,第一电子设备可以从所述第二电子设备获得包括所述第二电 子设备中的指定应用的应用列表。 也就是说, 第一电子设备可以指定要获取 第二电子设备中的某些应用, 例如, 通过指定应用名称, 从第二电子设备获 取包括该应用的应用列表。 或者, 通过指定文件夹名称, 从第二电子设备获 取包括在该文件夹中的所有应用的应用列表。 或者, 在第一电子设备上的操 作系统和第二电子设备上的操作系统为相同的操作系统的情况下,如果特定 应用在第一电子设备上运行时, 占用第一电子设备的 CPU资源为 5 % , 而该 特定应用在第二电子设备上运行时, 占用第二电子设备的 CPU资源为 3 % , 则第一电子设备可以从第二电子设备获取包括该特定应用的应用列表, 以便 在第二电子设备上运行该特定应用。 或者, 在第一电子设备上的操作系统和 第二电子设备上的操作系统为相同的操作系统的情况下,如果第一电子设备 的功耗远远高于第二电子设备的功耗, 则对于第一电子设备和第二电子设备 上相同的应用, 第一电子设备可以从第二电子设备获取包括该相同的应用的 应用列表, 以便选择在第二电子设备上运行该相同的应用。 或者, 在第一电 子设备上的操作系统和第二电子设备上的操作系统不同的情况下,对于只能 在第二电子设备上的操作系统上运行的特定应用, 第一电子设备可以从第二 电子设备获取包括该特定应用的应用列表。 当然, 指定的方式不限于此, 用 户可以通过任意方式指定他 /她期望的应用。
可替代地,第一电子设备从所述第二电子设备获得包括更新的应用的应 用列表, 其中所述第二电子设备中已存储上次发送的应用列表。 也就是说, 在第二电子设备中可以通过如日志文件等存储上次已经发送的应用列表,在 下一次要发送应用列表时, 第二电子设备可以通过参考已经存储的应用列 表, 仅仅将包括已经更新的应用的应用列表发送给第一电子设备。
可替代地,第一电子设备可以发送包括已有的应用标识所对应的应用的 应用列表给所述第二电子设备,从第二电子设备获得包括更新的应用的应用 列表, 其中所述第二电子设备中不存储上次发送的应用列表。 也就是说, 第 二电子设备中不存在上次发送的应用列表的情况下, 第一电子设备可以发送 包括本地已有的应用标识所对应的应用的应用列表给所述第二电子设备, 第 二电子设备在接收该应用列表后, 与本地应用进行比较, 然后仅仅将包括已 经更新的应用的应用列表发送给第一电子设备。 也就是说, 第二电子设备不 必要将本地已安装的所有应用的应用列表发送给第一电子设备, 而是可以根 据情况, 选择性地发送一部分应用的应用列表给第一电子设备, 从而可以减 少通信的数据量。
步骤 S703 : 根据所述应用列表, 创建至少一个与所述应用列表中的一 个应用对应的应用标识, 其中, 所述应用标识被触发后, 能够在所述第二电 子设备中启动所述应用标识对应的应用。
在该步骤中, 第一电子设备在接收所述应用列表后, 可以根据所述应用 列表, 在本地创建至少一个与所述应用列表中的一个应用对应的应用标识。 也就是说, 第一电子设备根据接收的应用列表, 在本地为应用列表中包括的 每一个应用创建对应的应用标识, 例如启动图标、 快捷方式等等。 并且, 在 所述应用标识被触发后, 能够在所述第二电子设备中启动所述应用标识对应 的应用。 也就是说, 在触发第一电子设备上创建的应用标识后, 第二电子设 备中与该应用标识对应的应用处于可激活状态。 然后, 例如通过用户的再次 确认等, 启动该应用。
进一步地, 在触发第一电子设备上创建的应用标识后, 第二电子设备中 与该应用标识对应的应用可以立即启动, 而不需要用户的再次确认。
进一步地, 第一电子设备包括显示单元, 所述方法还包括: 在所述第二 电子设备中启动所述应用标识对应的应用时,在所述显示单元上显示所述第 二电子设备的运行界面。 也就是说, 在该步骤中, 当在所述第二电子设备中 启动所述应用标识对应的应用时,在所述显示单元上应当显示第二电子设备 的运行界面。 此外, 所述显示单元上原始显示的内容可以保持或者不保持。 例如, 在所述显示单元上原始显示的内容保持的情况下, 可以通过例如分屏 显示、 画中画显示等技术, 同时显示第二电子设备的运行界面。 或者, 在所 述显示单元上原始显示的内容不保持的情况下, 可以将所述显示单元的整个 显示屏幕切换为第二电子设备的运行界面。
此外, 在显示第二电子设备的运行界面时, 可以显示包括所述应用标识 对应的应用运行窗口。 或者, 所述应用在第二电子设备中后台运行, 不显示 其运行窗口, 而只显示与其对应的标识(如在状态栏或任何栏中显示指示所 述应用的标识)。 或者, 所述应用在第二电子设备中后台运行, 不显示与所 述应用有关的任何内容等等。
另夕卜,对于启动第一电子设备与第二电子设备的数据连接的方式可以有 多种方式。 例如, 可以在第一电子设备上设置触发单元, 如按键、 按钮等的 硬件单元或如图标、 快捷方式等的对应于预定命令的软件单元, 然后根据用 户对所述触发单元的操作,启动与所述第二电子设备的无线连接,例如蓝牙、 WiFi、 无线局域网连接等等。
可替代地, 可在第一电子设备上设置一些物理接口 (如 USB接口、 网 络接口、 HDMI接口等), 当通过所述物理接口和所述第二电子设备进行物 理连接时, 启动与所述第二电子设备的数据连接。
最后, 在所述第一电子设备与所述第二电子设备断开时, 可以自动删除 已创建的应用标识。 当然, 也可以不删除已创建的应用标识。
在所述电子设备与所述第二电子设备断开时删除已创建的应用标识的 情况下, 第一电子设备需要创建与接收的应用列表中的所有应用——对应的 多个应用标识。 举例来说, 当接收的应用列表中包括应用 1、 应用 2和应用 3时, 第一电子设备创建与应用 1、 应用 2和应用 3——对应的应用标识 1、 应用标识 2和应用标识 3。
在所述电子设备与所述第二电子设备断开时不删除已创建的应用标识 的情况下, 第一电子设备可以将接收的应用列表中的所有应用与本地已有的 应用标识所对应的应用比较,并且根据比较结果创建和 /或删除对应于更新的 应用的应用标识。 举例来说, 当接收的应用列表中包括应用 1、 应用 2和应 用 4时, 由于在上一次已经创建应用标识 1、 应用标识 2和应用标识 3 , 因 此第一电子设备将接收的应用列表中包括的应用 1、 应用 2和应用 4和已有 的应用标识 1、 应用标识 2和应用标识 3对应的应用 1、 应用 2和应用 3进 行比较,确定在第二电子设备中当前删除了应用 3并且增加了应用 4。 因此, 第一电子设备删除已创建的与应用 3对应的应用标识 3 , 同时创建与应用 4 对应的应用标识 4。
此外, 可以在所述第一电子设备上设置更新请求单元, 如按键、 按钮等 的硬件单元或如图标、 快捷方式等的对应于预定命令的软件单元。
在用户对所述更新请求单元进行操作的情况下,此时如果所述第一电子 设备和第二电子设备的数据连接处于连接成功状态, 则发送更新请求到所述 第二电子设备。
如果所述第一电子设备和第二电子设备的数据连接处于连接不成功状 态, 则在所述第一电子设备的记录单元(如存储器) 中记录所述更新请求, 并且在所述第一电子设备和第二电子设备的数据连接处于连接成功状态时, 读取在所述记录单元中记录的更新请求并将其发送到所述第二电子设备。
在接收更新请求后 ,如果第二电子设备响应于所述更新请求检测到本地 存在更新的应用, 则发送包括更新的应用的应用列表到第一电子设备, 第一 电子设备在接收到该应用列表后,可以根据接收的应用列表创建和 /或删除对 应于更新的应用的应用标识。
因此, 通过在所述第一电子设备上设置更新单元, 用户可以在使用过程 中根据需要手动启动与第二电子设备的同步。
下面参考图 8描述根据本实施例的电子设备的配置的框图。
根据本实施例的电子设备 800包括:
检测单元 801 ,配置为检测与第二电子设备的数据连接,获得检测结果; 获取单元 802, 配置为当所述检测结果表明所述电子设备与所述第二电 子设备的数据连接成功时, 从所述第二电子设备获得应用列表, 所述应用列 表包括至少一个所述第二电子设备中安装的应用; 以及
创建单元 803 , 配置为根据所述应用列表, 创建至少一个与所述应用列 表中的一个应用对应的应用标识, 其中, 所述应用标识被触发后, 能够在所 述第二电子设备中启动所述应用标识对应的应用。
在所述应用标识被触发后 ,在所述第二电子设备中启动所述应用标识对 应的应用。
所述电子设备 800还包括显示单元 804 , 配置为在所述第二电子设备中 启动所述应用标识对应的应用时, 显示所述第二电子设备的运行界面。
当所述检测结果表明所述电子设备 800 与所述第二电子设备的数据连 接成功时, 所述获取单元 802向所述第二电子设备发送用于获取所述第二电 子设备中安装的应用的应用列表的请求, 然后接收所述第二电子设备响应于 所述请求而发送的应用列表; 或者当所述检测结果表明所述电子设备 800与 所述第二电子设备的数据连接成功时, 所述获取单元 802接收所述第二电子 设备自动发送的所述应用列表。
所述电子设备 800还包括触发单元 805 , 配置为根据用户对所述触发单 元的操作, 启动与所述第二电子设备的无线连接, 其中所述触发单元 805是 所述电子设备上设置的按键或对应于预定命令的标识。
所述电子设备 800还包括物理接口 806 , 配置为当所述电子设备通过所 述物理接口 106和所述第二电子设备进行物理连接时, 启动与所述第二电子 设备的数据连接。
所述获取单元 802还配置为:从所述第二电子设备获得包括所述第二电 子设备中的所有应用的应用列表; 或者从所述第二电子设备获得包括所述第 二电子设备中的指定应用的应用列表; 或者从所述第二电子设备获得包括更 新的应用的应用列表, 其中所述第二电子设备中已存储上次发送的应用列 表; 或者发送包括已有的应用标识所对应的应用的应用列表给所述第二电子 设备, 从第二电子设备获得包括更新的应用的应用列表, 其中所述第二电子 设备中不存储上次发送的应用列表。
所述电子设备 800还包括删除单元 807 , 配置为在所述电子设备与所述 第二电子设备断开时, 删除已创建的应用标识。
所述创建单元 802还配置为:在所述电子设备 800与所述第二电子设备 断开时删除已创建的应用标识的情况下,创建与所述应用列表中的所有应用 分别对应的多个应用标识; 或者在所述电子设备 800与所述第二电子设备断 开时不删除已创建的应用标识的情况下,将所述应用列表中的所有应用与已 有的应用标识所对应的应用比较,并且根据比较结果创建和 /或删除对应于更 新的应用的应用标识。
所述电子设备还包括更新请求单元 808 , 配置为在用户对所述更新请求 单元 808进行操作的情况下, 其中所述更新请求单元 808是所述电子设备上 设置的按键或对应于预定命令的标识。
如果所述电子设备 800和第二电子设备的数据连接成功,则发送更新请 求到所述第二电子设备。
如果所述电子设备 800和第二电子设备的数据连接不成功,则在所述电 子设备的记录单元 809中记录所述更新请求, 并且在所述电子设备 800和第 二电子设备的数据连接成功时,读取在所述记录单元 809中记录的更新请求 并将其发送到所述第二电子设备。
所述创建单元 809还配置为:如果第二电子设备响应于所述更新请求检 测到更新的应用, 则接收从第二电子设备发送的包括更新的应用的应用列 表, 并且根据接收的应用列表创建和 /或删除对应于更新的应用的应用标识。
电子设备 800还包括控制单元 810, 其控制各个单元的操作。
通过根据本发明的同步方法和电子设备,能够方便地获取另一电子设备 上安装的应用的应用列表, 并创建与所述应用对应的应用标识, 从而可以方 便地启动另一电子设备上安装的应用。
如上所述, 本发明实施例可以应用在由第一电子设备和第二电子设备组 成的混合架构 (hybrid ) 系统中, 其中, 混合架构系统可以是两个独立的电 子设备组合而成,也可以包含第一电子设备和第二电子设备的一个便携电子 设备。 比如混合架构系统可以由一台独立单一系统的笔记本计算机和一台智 能手机组成, 也可以是具有混合架构系统的笔记本计算机。
第一电子设备可以包括第一硬件系统, 比如基于 X86架构或 ARM架构 处理器的系统。第二电子设备可以包括第二硬件系统, 比如基于 X86架构或 ARM架构处理器的系统。 即第一电子设备和第二电子设备可以基于相同的 硬件架构, 也可以依据不同的硬件架构。
进一步, 第一电子设备可以包括具有第一操作系统的第一硬件系统, 比 如安装有桌面设备操作系统(比如 Windows, Linux或 MacOS )或安装有便 携设备操作系统(比如 Android, Symbian或 iOS )的第一硬件系统。 第二电 子设备可以包括具有第二操作系统的第二硬件系统, 比如安装有桌面设备操 作系统(比如 Windows, Linux或 MacOS )或安装有便携设备操作系统(比 如 Android, Symbian或 iOS )的第二硬件系统。 即第一操作系统和第二操作 系统可以相同也可以不同, 只要可以运行在相应的硬件系统即可。 优选地, 第一电子设备是基于 X86架构处理器的,安装有桌面操作系统的系统, 第二 电子设备^^于 ARM架构处理器的, 安装有便携设备操作系统的系统。 将参考图 9描述根据本发明实施例的关联方法。图 9是图示根据本发明 实施例的关联方法的流程图。根据本发明实施例的关联方法应用于第一电子 设备(例如主机) 中, 用于获取第二电子设备(例如 Pad )上安装的应用的 应用列表, 并且将获取的应用与第一电子设备和第二电子设备的存储单元上 的对应文件类型的文件进行关联。 第一电子设备具有第一存储单元, 其中可 以存储各种类型的数据, 例如图像、 电影、 文档、 表格、 游戏等等。 第二电 子设备具有第二存储单元, 其中可以存储与第一存储单元相同的各种数据。 其中, 第一电子设备连接第二电子设备后, 第一电子设备可以直接访问第二 电子设备的第二储存单元。
将参照图 9描述根据本发明一个实施例的关联方法。该关联方法应用于 第一电子设备和第二电子设备, 所述第一电子设备具有第一存储单元, 所述 第二电子设备具有第二储存单元。
根据本发明第一实施例的关联方法包括:
S901 : 所述第一电子设备获得一检测结果。
在该步骤中,第一电子设备可以通过各种方式检测与第二电子设备之间 的数据连接是否成功, 并且获得检测结果。 例如, 第一电子设备可以通过如 轮询, 触发等方式, 检测与第二电子设备之间的数据连接的状态, 并且获得 检测结果。
S902: 当所述检测结果满足预定条件时, 所述第一电子设备从所述第二 电子设备获得应用列表, 所述应用列表包括至少一个所述第二电子设备中的 应用。
在该步骤中, 首先判断在步骤 S901 中的检测结果是否满足预定条件, 然后, 满足预定条件时, 从所述第二电子设备获得应用列表, 所述应用列表 包括至少一个所述第二电子设备中的应用。
例如,所述预定条件可以是所述检测结果表明所述第一电子设备与所述 第二电子设备的数据连接成功。 也就是说, 在该情况下, 当第一电子设备和 所述第二电子设备的数据连接成功时, 自动地从所述第二电子设备获得应用 列表。
例如,所述预定条件也可以是所述检测结果表明所述第一电子设备与所 述第二电子设备的数据连接成功, 并且第一电子设备上的请求单元被操作, 所述请求单元是所述第一电子设备上设置的按键或对应于预定命令的标识, 用于向所述第二电子设备发送用于获取所述应用列表的请求。 也就是说, 在 该情况下, 当第一电子设备和所述第二电子设备的数据连接成功时, 不自动 地从所述第二电子设备获得应用列表, 而是在用户操作第一电子设备上设置 的请求单元时, 向所述第二电子设备发送用于获取所述应用列表的请求, 然 后从所述第二电子设备获得应用列表。 在该情况下, 需要满足的条件是第一 电子设备和所述第二电子设备的数据连接成功, 并且用户操作请求单元手动 请求从所述第二电子设备获得应用列表。 与自动获得应用列表的情况下相 比, 该手动请求获得应用列表的方式在刚建立连接时不进行操作, 从而可以 节省功率。
进一步地, 例如, 当在步骤 S901中获得的检测结果指示第一电子设备 和第二电子设备之间的数据连接成功时, 所述第一电子设备可以向所述第二 电子设备发送用于获取所述第二电子设备中安装的应用的应用列表的请求, 然后接收所述第二电子设备响应于所述请求而发送的应用列表。在该处理过 程中, 由第一电子设备主动发送获取第二电子设备的应用列表的请求到第二 电子设备, 第二电子设备接收该请求之后, 开始获取本地已安装的应用的信 息, 然后将本地已安装的应用的应用列表通过已经建立的数据连接通道发送 给第一电子设备。
可替代地, 例如, 当在步骤 S901中获得的检测结果指示第一电子设备 和第二电子设备之间的数据连接成功时, 所述第二电子设备可以自动发送所 述应用列表。 在该处理过程中, 当第一电子设备和第二电子设备之间的数据 连接成功时, 第一电子设备可以不用发送获取第二电子设备的应用列表的请 求到第二电子设备, 相反, 由第二电子设备可以自动发送所述应用列表, 第 一电子设备可以直接接收由第二电子设备发送的包括所述第二电子设备中 安装的应用的应用列表。
此外, 例如第二电子设备可以将本地应用列表打包, 以 XML文件形式 发送给第一电子设备,其中该 XML文件中包含每个应用的启动方式、 图标、 以及关联文件类型列表等信息。
进一步地,第一电子设备可以从所述第二电子设备获得包括所述第二电 子设备中的所有应用的应用列表。 也就是说, 第一电子设备不管现在本地是 否已经存在关于第二电子设备中的应用, 直接获取包括所述第二电子设备中 的所有应用的应用列表。 可替代地,第一电子设备可以从所述第二电子设备获得包括所述第二电 子设备中的指定应用的应用列表。 也就是说, 第一电子设备可以指定要获取 第二电子设备中的某些应用, 例如, 通过指定应用名称, 从第二电子设备获 取包括该应用的应用列表。 或者, 通过指定文件夹名称, 从第二电子设备获 取包括在该文件夹中的所有应用的应用列表。 或者, 在第一电子设备上的操 作系统和第二电子设备上的操作系统为相同的操作系统的情况下,如果特定 应用在第一电子设备上运行时, 占用第一电子设备的 CPU资源为 5 % , 而该 特定应用在第二电子设备上运行时, 占用第二电子设备的 CPU资源为 3 % , 则第一电子设备可以从第二电子设备获取包括该特定应用的应用列表, 以便 在第二电子设备上运行该特定应用。 或者, 在第一电子设备上的操作系统和 第二电子设备上的操作系统为相同的操作系统的情况下,如果第一电子设备 的功耗远远高于第二电子设备的功耗, 则对于第一电子设备和第二电子设备 上相同的应用, 第一电子设备可以从第二电子设备获取包括该相同的应用的 应用列表, 以便选择在第二电子设备上运行该相同的应用。 或者, 在第一电 子设备上的操作系统和第二电子设备上的操作系统不同的情况下,对于只能 在第二电子设备上的操作系统上运行的特定应用, 第一电子设备可以从第二 电子设备获取包括该特定应用的应用列表。 当然, 指定的方式不限于此, 用 户可以通过任意方式指定他 /她期望的应用。
可替代地,第一电子设备从所述第二电子设备获得包括更新的应用的应 用列表, 其中所述第二电子设备中已存储上次发送的应用列表。 也就是说, 在第二电子设备中可以通过如日志文件等存储上次已经发送的应用列表,在 下一次要发送应用列表时, 第二电子设备可以通过参考已经存储的应用列 表, 仅仅将包括已经更新的应用的应用列表发送给第一电子设备。
可替代地,第一电子设备可以发送包括已有的应用标识所对应的应用的 应用列表给所述第二电子设备,从第二电子设备获得包括更新的应用的应用 列表, 其中所述第二电子设备中不存储上次发送的应用列表。 也就是说, 第 二电子设备中不存在上次发送的应用列表的情况下, 第一电子设备可以发送 包括本地已有的应用标识所对应的应用的应用列表给所述第二电子设备, 第 二电子设备在接收该应用列表后, 与本地应用进行比较, 然后仅仅将包括已 经更新的应用的应用列表发送给第一电子设备。 也就是说, 第二电子设备不 必要将本地已安装的所有应用的应用列表发送给第一电子设备, 而是可以根 据情况, 选择性地发送一部分应用的应用列表给第一电子设备, 从而可以减 少通信的数据量。
S903 : 根据所述应用列表, 所述第一电子设备关联所述应用列表中的应 用和所述第一存储单元和 /或所述第二存储单元中的对应文件类型的文件。
在该步骤中, 由于当第一电子设备和第二电子设备连接后, 第二电子设 备的第二存储单元已经成为第一电子设备的一个存储单元, 第一电子设备可 以直接访问第二电子设备的第二储存单元。 因此, 根据所述应用列表, 第一 电子设备关联所述应用列表中的应用和所述第一存储单元和 /或所述第二存 储单元中的对应文件类型的文件。 此时, 第一存储单元和第二存储单元中的 文件可以使用第一电子设备中安装的应用打开,也可以使用第二电子设备中 安装的应用打开。
此时, 可能存在以下几种情况:
1 ) 当文件存储在第二电子设备的存储单元中, 且第二电子设备的存储 单元作为第一电子设备的共享单元时, 第一电子设备可以直接访问第二电子 设备的存储单元中存储的文件。
2 ) 当文件存储在第一电子设备的存储单元中, 且第二电子设备无法访 问时, 将该文件复制到第一电子设备的共享存储单元中。
3 )如果第一电子设备和第二电子设备的存储单元都是透明的, 则不需 要判断和复制, 第一电子设备和第二电子设备可以直接访问各存储单元中存 储的文件。
例如, 在主机的存储单元中存储了一个电影文件 A.avi的情况下, 当主 机和 Pad连接后, 由于 Pad比主机省电, 用户希望用 Pad的视频播放器播放 该电影文件 A.avi,根据现有技术,用户有两种方案: 1 )首先手动切换到 Pad 端, 然后打开视频播放器, 并且选择该电影文件 A.avi进行播放; 2 )在主机 端桌面上点击视频播放器图标, 系统自动切换到 Pad端并打开视频播放器, 然后用户再选择该电影文件 A.avi进行播放。 这样的操作比较复杂, 用户的 体验较差。 然而, 根据本实施例的关联方法, 由于 Pad上的应用已经和主机 的存储单元上的文件实现关联, 因此用户在激活该电影文件 A.avi时, 可以 显示如弹出菜单的图形用户界面, 并且在该弹出菜单中显示 "用 Pad 端 MediaPlayer播放"的选项,用户可以通过选择 "用 Pad端 MediaPlayer播放", 自动切换到 Pad并用 Pad上的 MediaPlayer播放该电影文件 A.avi,从而改进 用户的体验。
另夕卜,对于启动第一电子设备与第二电子设备的数据连接的方式可以有 多种方式。 例如, 可以在第一电子设备上设置触发单元, 如按键、 按钮等的 硬件单元或如图标、 快捷方式等的对应于预定命令的软件单元, 然后根据用 户对所述触发单元的操作,启动与所述第二电子设备的无线连接,例如蓝牙、 WiFi、 无线局域网连接等等。
可替代地, 可在第一电子设备上设置一些物理接口 (如 USB接口、 网 络接口、 HDMI接口等), 当通过所述物理接口和所述第二电子设备进行物 理连接时, 启动与所述第二电子设备的数据连接。
此外,第一电子设备也可以在本地创建至少一个与所述应用列表中的一 个应用对应的应用标识。
此外, 在所述第一电子设备与所述第二电子设备断开时, 可以自动删除 已创建的应用标识。 当然, 也可以不删除已创建的应用标识。
此外, 在所述电子设备与所述第二电子设备断开时, 可以解除关联所述 应用列表中的应用和所述第一存储单元和所述第二存储单元中的对应文件 类型的文件。 当然, 也可以不解除关联。
此外, 可以在所述第一电子设备上设置更新请求单元, 如按键、 按钮等 的硬件单元或如图标、 快捷方式等的对应于预定命令的软件单元。
在用户对所述更新请求单元进行操作的情况下,此时如果所述第一电子 设备和第二电子设备的数据连接处于连接成功状态, 则发送更新请求到所述 第二电子设备。
如果所述第一电子设备和第二电子设备的数据连接处于连接不成功状 态, 则在所述第一电子设备的记录单元(如存储器) 中记录所述更新请求, 并且在所述第一电子设备和第二电子设备的数据连接处于连接成功状态时, 读取在所述记录单元中记录的更新请求并将其发送到所述第二电子设备。
在接收更新请求后,如果第二电子设备响应于所述更新请求检测到更新 的应用, 则接收从第二电子设备发送的包括更新的应用的应用列表, 并且根 据接收的应用列表关联和 /或解除关联对应于更新的应用的文件类型的文件。
因此, 通过在所述第一电子设备上设置更新单元, 用户可以在使用过程 中根据需要手动启动与第二电子设备的同步, 并且根据同步结果将第二电子 设备上的应用和存储单元中的文件进行关联。 此外,可以在第一电子设备的系统中保存所述应用和所述文件的关联关 系。 例如, 可以在第一电子设备的操作系统中使用日志文件来记录应用和文 件的关联关系。
此外,还可以通过用户的切换操作, 使用在第二电子设备的系统中保存 的所述应用和所述文件的关联关系。
下面参考图 10描述根据本发明的一个实施例的电子设备 1000的配置。 根据本实施例的电子设备 1000包括:
第一存储单元 1010, 配置为存储各种用户和文件;
检测单元 1020, 配置为获得一检测结果;
获取单元 1030, 配置为当所述检测结果满足预定条件时, 从第二电子 设备获得应用列表, 所述应用列表包括至少一个所述第二电子设备中的应 用, 所述第二电子设备包括第二存储单元; 以及
关联单元 1040, 配置为根据所述应用列表, 关联所述应用列表中的应 用和所述第一存储单元和 /或所述第二存储单元中的对应文件类型的文件。
所述预定条件包括:
所述检测结果表明所述第一电子设备与所述第二电子设备的数据连接 成功; 或者
所述检测结果表明所述第一电子设备与所述第二电子设备的数据连接 成功, 并且第一电子设备上的请求单元被操作, 所述请求单元是所述第一电 子设备上设置的按键或对应于预定命令的标识, 用于向所述第二电子设备发 送用于获取所述应用列表的请求。
所述获取单元 1030还配置为:
当所述检测结果表明所述第一电子设备与所述第二电子设备的数据连 接成功时, 向所述第二电子设备发送用于获取所述第二电子设备中安装的应 用的应用列表的请求, 然后接收所述第二电子设备响应于所述请求而发送的 应用列表; 或者
当所述检测结果表明所述第一电子设备与所述第二电子设备的数据连 接成功时, 接收所述第二电子设备自动发送的所述应用列表。
所述电子设备 1000还可以包括触发单元 1050, 配置为根据用户对所述 触发单元 1050的操作, 启动与所述第二电子设备的无线连接, 其中所述触 发单元 1050是所述电子设备上设置的按键或对应于预定命令的标识。 所述电子设备 1000还可以包括物理接口 1060, 配置为当通过所述物理 接口 1060和所述第二电子设备的物理接口进行物理连接时, 启动与所述第 二电子设备的数据连接。
所述获取单元 1030还可以配置为:
从所述第二电子设备获得包括所述第二电子设备中的所有应用的应用 列表; 或者
从所述第二电子设备获得包括所述第二电子设备中的指定应用的应用 列表; 或者
从所述第二电子设备获得包括更新的应用的应用列表,其中所述第二电 子设备中已存储上次发送的应用列表; 或者
发送包括已有的应用标识所对应的应用的应用列表给所述第二电子设 备, 从第二电子设备获得包括更新的应用的应用列表, 其中所述第二电子设 备中不存储上次发送的应用列表。
所述电子设备 1000还可以包括应用标识创建单元 1070 , 配置为创建至 少一个与所述应用列表中的一个应用对应的应用标识。
所述电子设备 1000还可以包括应用标识删除单元 1080, 配置为在所述 电子设备 1000与所述第二电子设备断开时, 删除已创建的应用标识。
所述电子设备 1000还可以包括解除关联单元 1090, 配置为在所述电子 设备 100与所述第二电子设备断开时, 解除关联所述应用列表中的应用和所 述第一存储单元 1010和所述第二存储单元中的对应文件类型的文件。
所述电子设备 1000还可以包括更新请求单元 1100, 配置为在用户对所 述更新请求单元 1100进行操作的情况下, 其中所述更新请求单元 110是所 述电子设备上设置的按键或对应于预定命令的标识,
如果所述电子设备 1000和第二电子设备的数据连接成功, 则发送更新 请求到所述第二电子设备; 以及
如果所述电子设备 1000和第二电子设备的数据连接不成功, 则在所述 电子设备 1000的记录单元 1110中记录所述更新请求, 并且在所述电子设备 1000和第二电子设备的数据连接成功时, 读取在所述记录单元 1110中记录 的更新请求并将其发送到所述第二电子设备。
所述应用标识创建单元 1070和 /或应用标识删除单元 1080还可以配置 为: 如果第二电子设备响应于所述更新请求检测到更新的应用,则接收从第 二电子设备发送的包括更新的应用的应用列表, 并且根据接收的应用列表关 联和 /或解除关联对应于更新的应用的文件类型的文件。
此外, 可以在所述电子设备 1000的系统中保存所述应用和所述文件的 关联关系。
此外,还可以通过用户的切换操作, 使用在第二电子设备的系统中保存 的所述应用和所述文件的关联关系。
第一电子设备可包括控制单元 1120 , 用于整体地控制各个单元。
通过根据本发明一个实施例的关联方法和电子设备,能够方便地获取另 一电子设备上安装的应用的应用列表, 并关联所述应用列表中的应用和所述 第一存储单元和所述第二存储单元中的对应文件类型的文件,从而方便地选 择使用第一电子设备或第二电子设备的应用打开文件, 改善了用户的体验。
接着, 将参照图 11描述根据本发明另一实施例的关联方法。
根据本发明另一实施例的关联方法的步骤 S 1101和 S 1101与根据一个实 施例的关联方法的步骤 S901和 S902相同, 在此省略其详细描述。
步骤 1103: 在激活所述第一存储单元和所述第二存储单元中存储的文 件时, 显示包括与可激活所述文件的应用对应的标识的图形用户界面, 其中 所述可激活所述文件的应用包括所述第一电子设备本地安装的应用和所述 第二电子设备中安装的应用。
在该步骤中,当用户激活所述第一存储单元和所述第二存储单元中存储 的文件时, 将显示包括与可激活所述文件的应用对应的标识的图形用户界 面, 如弹出菜单。 在该图形用户界面中可以显示能够打开所述文件的所述第 一电子设备本地安装的应用和所述第二电子设备中安装的应用的标识, 例如 快捷方式或图标等。
例如, 在主机的存储单元中存储了一个电影文件 A.avi的情况下, 当主 机和 Pad连接后, 当用户激活该电影文件 A.avi时, 可以显示如弹出菜单的 图形用户界面, 并且在该弹出菜单中显示 "用主机端 WindowPlayer播放"、 "用主机端 MediaPlayer播放" "用 Pad端 WindowPlayer播放"、 "用 Pad端 MediaPlayer播放" 等的选项, 用户可以通过选择 "用 Pad端 MediaPlayer播 放", 自动切换到 Pad并用 Pad上的 MediaPlayer播放该电影文件 A.avi, 从 而可以方便地选择期望的应用激活文件。 下面参考图 12描述根据本发明实施例的电子设备 1200的配置。
根据本实施例的电子设备 1200包括:
第一存储单元 1201 , 配置为存储各种用户和文件;
检测单元 1202, 配置为获得一检测结果;
获取单元 1203 , 配置为当所述检测结果满足预定条件时, 从第二电子 设备获得应用列表, 所述应用列表包括至少一个所述第二电子设备中的应 用, 所述第二电子设备包括第二存储单元; 以及
显示单元 1204, 配置为在激活所述第一存储单元和所述第二存储单元 中存储的文件时,显示包括与可激活所述文件的应用对应的标识的图形用户 所述第二电子设备中安装的应用。
所述预定条件可以包括:
所述检测结果表明所述电子设备与所述第二电子设备的数据连接成功; 或者
所述检测结果表明所述电子设备与所述第二电子设备的数据连接成功, 并且电子设备上的请求单元被操作, 所述请求单元是所述电子设备上设置的 按键或对应于预定命令的标识, 用于向所述第二电子设备发送用于获取所述 应用列表的请求。
第一电子设备可包括控制单元 1205 , 用于整体地控制各个单元。
此外, 第一电子设备 1200也可包括与根据一个实施例的第一电子设备
1000的其它功能单元相同的功能单元, 在此省略其描述。
通过根据本发明另一实施例的关联方法和电子设备,能够方便地获取另 一电子设备上安装的应用的应用列表, 并显示包括与可激活所述文件的应用 对应的标识的图形用户界面, 其中所述可激活所述文件的应用包括所述第一 电子设备本地安装的应用和所述第二电子设备中安装的应用,从而方便地选 择使用第一电子设备或第二电子设备的应用打开文件, 改善了用户的体验。
接着, 将参照图 13描述根据本发明一个实施例的混合系统。
根据本发明一个实施例的混合系统 1300包括:
包括第一电子设备 1340和第二电子设备 1350,所述第一电子设备 1340 包括具有第一操作系统的第一硬件系统, 所述第二电子设备 1350 包括具有 第二操作系统的第二硬件系统, 其中 第二电子设备 1350包括:
第二存储单元 1351 , 配置为存储各种用户和文件,
第一电子设备 1340包括:
第一存储单元 1341 , 配置为存储各种用户和文件;
检测单元 1342, 配置为获得一检测结果;
获取单元 1343 , 配置为当所述检测结果满足预定条件时, 从第二电子 设备 1350 获得应用列表, 所述应用列表包括至少一个所述第二电子设备 1350中的应用; 以及
关联单元 1344, 配置为根据所述应用列表, 关联所述应用列表中的应 用和所述第一存储单元 1341和 /或所述第二存储单元 1351中的对应文件类型 的文件。
同样,第一电子设备 1340可以包括控制单元 1345 ,用于控制各个单元。 第二电子设备 1350可以包括控制单元 1352, 用于控制各个单元。
例如, 第一电子设备 1340可以是根据一个实施例的电子设备 1000。 通过根据本发明一个实施例的混合系统,第一电子设备能够方便地获取 第二电子设备上安装的应用的应用列表, 并关联所述应用列表中的应用和所 述第一存储单元和 /或所述第二存储单元中的对应文件类型的文件,从而方便 地选择使用第一电子设备或第二电子设备的应用打开文件, 改善了用户的体 验。
图 14为本发明实施例的一种应用备份方法流程图。
该应用的备份方法可以应用于一至少包括第一电子设备和第二电子设 备的系统, 例如由 base端 (主机设备 )和 pad端 (平板电脑)形成的系统, 两电子设备之间通过某种通信端口连接, 能实现两电子设备间的通信, 例如 通过 Hybrid端口连接、 通信。 其中, 第一电子设备上安装有第一客户端软 件, 第二电子设备上安装有第二客户端软件, 两客户端软件不完全相同, 至 少其中的应用不完全相同。 当需要在第一电子设备上备份第二电子设备上的 某些应用时, 该备份方法可以包括:
步骤 1401 , 第二电子设备接收第一电子设备通过通信端口发送的备份 请求。
首先, 第一电子设备通过通信端口向第二电子设备发送备份请求, 该备 份请求中包括请求备份的第二电子设备中第二客户端软件的应用信息, 其 中, 可以包括一个应用或多个应用的信息, 该信息可以包括应用的名称、 版 本号等等, 只要可以标识待备份的应用即可。
该备份请求可以是由用户通过操作第一电子设备触发的,也可以在第一 电子设备中预设触发条件, 当第一电子设备的运行或存储等状态达到该触发 条件时, 自动触发向第二电子设备发送备份请求。
步骤 1402, 第二电子设备查找所请求备份的第二客户端软件的应用。 第二电子设备在接收到第一电子设备发送的备份请求后, 解析该请求, 获得其中需要备份的应用的信息, 如名称、 版本号等标识信息, 然后在第二 电子设备本地存储的第二客户端软件中查找所需的应用。
具体的,可以在第二电子设备中预先存储有第二客户端软件的所有应用 的标识信息列表, 第二电子设备首先在该列表中查找是否存在第一电子设备 所需的应用, 如果不存在, 则向第一电子设备反馈查找结果, 然后终止备份 流程,如果存在,则进一步提取该所需应用的所有信息,例如安装程序等等。
步骤 1403 , 第二电子设备通过通信端口向第一电子设备发送查找到的 第二客户端软件的应用, 以使第一电子设备进行备份。
第二电子设备在查找到第一电子设备所需的应用的相关信息后,通过通 信端口向第一电子设备发送, 第一电子设备在接收到后, 进行备份, 具体的 可以直接进行安装运行,也可以只是将接收到的信息在第一电子设备本地进 行存储, 在使用时在安装运行。 若第一电子设备本地也存储有第一客户端软 件的所有应用的标识信息列表, 则同时可以更新该列表, 在该列表中增加所 备份的应用的标识信息。
在另一实施例中, 在执行步骤 1401之前, 第一电子设备、 第二电子设 备之间还可以首先通过通信端口向对方发送各自存储的应用的标识信息列 表, 以便两电子设备之间根据列表确定可以备份的应用, 然后再发送备份请 本发明实施例中, "第一"、 "第二" 均是相对而言, 并非特指或限定, 只要是两电子设备之间应用的备份过程均可以釆用上述方法实现,且均在本 申请的保护范围内。
本发明实施例在两电子设备之间通过通信端口进行通信,直接完成了不 同客户端软件之间应用的备份, 而无需进行整个客户端软件的安装, 该方法 快速实现了应用备份, 简化了操作过程, 提高了备份效率。 参见图 15 , 为本发明实施例的另一种应用备份方法的流程图。
本实施例中, 以第一电子设备为 base端, 第二电子设备以 pad端为例 进行说明, base端和 pad端通过 Hybrid端口连接、 通信。 base端上安装有 第一客户端软件, pad端上安装有第二客户端软件, 两客户端软件中的应用 不完全相同。 当 base端需要备份 pad端上的某些应用时, 该备份方法可以包 括:
步骤 1501 , base端与 Pad端通过 Hybrid端口连接。
步骤 1502, base端生成备份请求, 并通过 Hybrid端口向 pad端发送该 备份请求。
当 base端在检测到与 pad端通过该 Hybrid端口连接后,可以触发在 base 端的桌面生成桌面快捷方式, 该快捷方式中包含备份的功能项, 以便于触发 应用备份。当 base端接收到用户操作该桌面快捷方式中的备份功能项所触发 的备份指令时, 生成备份请求, 并通过通信端口向 pad端发送该备份请求。 其中,备份请求中包括请求备份的 pad端中第二客户端软件的应用标识信息, 这些应用标识信息可以是由用户在 base端预先设定的备份目录。
以上过程不仅限于 base端和 pad端之间的备份, 还可以用于其它任意 可以通信的两电子设备之间的备份。
步骤 1503 , 当 pad端处于休眠状态时, Hybrid端口发送唤醒指令, 以 唤醒 pad端。
在本实施例中, 如果 pad端处于休眠状态, 则 Hybrid端口需要首先对 pad端执行唤醒操作, 具体的, 由 Hybrid端口向 pad端发送唤醒指令, pad 端在被唤醒进入工作状态后, 向 Hybrid端口反馈进入工作状态的信息, 然 后由 Hybrid端口向 pad端发送 base端的备份请求。
步骤 1504, pad端被唤醒后, 接收 Hybrid端口发送的 base端的备份请 求。
步骤 1505 , pad端查找请求备份的应用, 并将查找到的应用打包。
Pad端解析备份请求并获取其中所需备份的应用标识信息后, 在本地查 找所需应用的相关信息, 例如安装程序等, 然后将所查找到的所有应用进行 打包。
步骤 1506, pad端将打包后的应用通过 Hybrid端口向 base端发送。 步骤 1507 , base端接收到打包后的应用后存储在本地。 在另一实施例中, 如果是 pad端需要备份 base端上的应用, 则可以执 行类似的步骤流程进行备份。 接完成了不同客户端软件之间应用的备份, 而无需进行整个客户端软件的安 装, 该方法快速实现了应用备份, 简化了操作过程, 提高了备份效率。
以上是对本发明方法实施例的描述,下面对实现上述方法的系统进行介 绍。
参见图 16, 为本发明实施例的一种电子设备的结构示意图。
该电子设备中安装有客户端软件, 它通过通信端口与另一电子设备连 接, 该另一电子设备中安装有另一客户端软件。
该电子设备可以包括:
请求接收单元 1601 , 用于接收另一电子设备通过通信端口发送的第一 备份请求, 该第一备份请求中包括请求备份的所述电子设备中客户端软件的 应用信息;
应用查找单元 1602 , 用于查找所请求备份的电子设备中客户端软件的 应用;
应用发送单元 1603 , 用于通过通信端口向另一电子设备发送查找到的 应用, 以使另一电子设备进行备份。
该电子设备的请求接收单元 1601通过通信端口接收另一电子设备发送 的备份请求, 该备份请求中包括请求备份的该电子设备中客户端软件的应用 信息, 其中, 可以包括一个应用或多个应用的信息, 该信息可以包括应用的 名称、 版本号等等, 只要可以标识待备份的应用即可。 在接收到另一电子设 备发送的备份请求后, 应用查找单元 1602解析该请求, 获得其中需要备份 的应用的信息, 如名称、 版本号等标识信息, 然后在本地存储的客户端软件 中查找所需的应用。 在查找到另一电子设备所需的应用的相关信息后, 应用 发送单元 1603通过通信端口向另一电子设备发送。
在另一实施例中,若在接收另一电子设备通过通信端口发送的第一备份 请求之前, 该电子设备处于休眠状态, 则该电子设备还可以包括状态切换单 元, 用于根据所述通信端口发送的唤醒指令, 进入工作状态。 本发明实施例中该电子设备通过上述单元直接完成了不同客户端软件 之间应用的备份, 而无需在另一电子设备上进行整个客户端软件的安装, 该 方法快速实现了应用备份, 简化了操作过程, 提高了备份效率。
参见图 17 , 为本发明实施例另一种电子设备的结构示意图。
本实施例中, 该电子设备除了可以包括请求接收单元 1701、 应用查找 单元 1702、 应用发送单元 1703 , 以接收另一电子设备的第一备份请求, 将 应用备份到另一电子设备之前, 还可以包括以下单元, 以向其它电子设备发 送第二备份请求, 以获得其它电子设备上的应用备份:
创建单元 1704, 用于在检测到与另一电子设备通过通信端口连接时, 生成包含备份功能项的桌面快捷方式;
请求触发单元 1705 , 用于接收用户操作备份功能项触发的备份指令, 生成第二备份请求;
请求发送单元 1706 , 用于通过通信端口向另一电子设备发送第二备份 请求。
本发明实施例中该电子设备通过上述单元直接完成了不同客户端软件 之间应用的备份, 而无需在本电子设备上进行整个客户端软件的安装, 该方 法快速实现了应用备份, 简化了操作过程, 提高了备份效率。
以上实施例中, 该电子设备具体可以是 Base端或 Pad端。
参见图 18, 为本发明实施例一种的应用备份系统的结构示意图。
该系统可以包括第一电子设备 1801和第二电子设备 1802, 其中, 第一 电子设备 1801上安装有第一客户端软件, 第二电子设备 1802上安装有第二 客户端软件, 第一电子设备 1801与第二电子设备 1802通过通信端口连接。
第二电子设备 1802, 用于接收第一电子设备 1801通过通信端口发送的 备份请求, 备份请求中包括请求备份的所述第二客户端软件的应用信息; 查 找所请求备份的第二客户端软件的应用;通过通信端口向第一电子设备 1801 发送查找到的第二客户端软件的应用, 以使第一电子设备 1801进行备份。
在另一实例中, 该第一电子设备 1801 , 具体可以用于当检测到与第二 电子设备 1802通过通信端口连接时, 生成包含备份功能项的桌面快捷方式; 接收用户操作备份功能项触发的备份指令, 生成备份请求; 通过通信端口向 第二电子设备 1801发送该备份请求。 第二电子设备 1802 , 还可以用于根据通信端口发送的唤醒指令, 进入 工作状态。
本实施例中, 第一电子设备可以为 Base端, 第二电子设备为 Pad端, 或者, 第一电子设备为 Pad端, 第二电子设备为 Base端。 通信端口可以为 Hybrid端口。
此外, 根据本发明的另一实施例, 提供了一种操作方法, 应用于第一电 子设备和第二电子设备, 所述第二电子设备具有显示屏, 所述方法包括: 当 检测到所述第一电子设备与第二电子设备连接时, 向所述第一电子设备发送 指示该连接的第一消息; 所述第一电子设备在接收到所述第一消息后, 将预 安装的应用程序的属性设置为相对于所述第一电子设备在系统界面中可安 装; 所述第一电子设备在从用户接收到安装所述应用程序的第一操作命令 后,将所述应用程序和指示安装所述应用程序的第二命令发送到所述第二电 子设备; 所述第二电子设备在接收到所述第二命令和所述应用程序之后, 安 装所述应用程序, 并将包含用于生成所述应用程序的图标的信息的第二消息 发送到所述第一电子设备; 所述第一电子设备在接收到所述第二消息之后, 在所述第二电子设备的显示屏上生成所述应用程序的图标, 并将所述应用程 序的图标的属性设置为在系统界面中可运行和可卸载。
通过上述操作方法 ,使得用户可以在第一电子设备的系统界面中安装用 于第二电子设备的应用程序, 并在安装好该应用程序之后, 可在第一电子设 备的系统界面中运行和卸载该应用程序, 从而增加了用户的便利性。
图 19是示出根据本发明实施例的操作方法的示意性流程图。如图 19所 示, 根据本发明实施例的操作方法应用于第一电子设备和第二电子设备, 第 二电子设备具有显示屏, 该方法包括: S1901 , 当检测到第一电子设备与第 二电子设备连接时, 向第一电子设备发送指示该连接的第一消息; S1902, 第一电子设备在接收到该第一消息后, 将预安装的应用程序的属性设置为相 对于第一电子设备在系统界面中可安装; S1903 , 第一电子设备在从用户接 收到安装该应用程序的第一操作命令后,将应用程序和指示安装该应用程序 的第二命令发送到第二电子设备; S1904, 第二电子设备在接收到第二命令 和应用程序之后, 安装该应用程序, 并将包含用于生成该应用程序的图标的 信息的第二消息发送到第一电子设备; S1905 , 第一电子设备在接收到第二 消息之后, 在第二电子设备的显示屏上生成应用程序的图标, 并将该应用程 序的图标的属性设置为在系统界面中可运行和可卸载。
在上文中已经提到, 在现有的混合系统中, 当要在第一电子设备的系统 界面下将应用程序安装到第二电子设备时, 需要首先将下载的第二电子设备 的应用程序包拷贝到共享存储区, 并手动切换到第二电子设备一端, 然后在 文件浏览器中找到该程序并进行安装, 用户的操作很繁瑣。 此外, 如果在第 一电子设备一端应用某些工具, 比如豌豆夹手机助手, 或者 itunes—类的辅 助工具来进行应用程序的安装, 则需要启动上述辅助工具来安装相应的应用 程序, 在这个过程中, 可能还需要连接第二电子设备并配对等额外的过程, 从而可能需要安装设备驱动, 并进行相对耗时的连接配对过程。 对于这种情 况, 用户除了需要额外安装这种辅助工具之外, 所要安装的应用程序的文件 在第一电子设备的界面中的属性实际上是不可安装, 并且安装好的应用程序 的图标在第一电子设备的界面中的属性也是不可运行和不可卸载的。 当用户 需要安装、 运行或卸载时, 都需要另外打开这类辅助工具的界面并进行相应 操作, 这也会给用户带来不便。
而在本发明的实施例中,该要安装的应用程序的应用程序包是在系统界 面中可安装的, 例如, 用户可以直接通过双击该应用程序包来进行安装, 或 者用户通过右键点击该应用程序包, 则在右键的菜单当中会出现安装该应用 程序包的选项。 在操作第一电子设备时, 如果该应用程序包不在第一电子设 备的操作系统的桌面上, 用户可能需要使用文件浏览器等来找到该应用程序 包并进行安装, 但是, 与现有技术中不同的是, 用户并不需要使用专门的辅 助工具来进行应用程序包的安装。 同样, 当在第二电子设备中安装了该应用 程序之后, 第二电子设备会将该应用程序的图标同步到第一电子设备。 具体 地说, 由于第二电子设备和第一电子设备连接之后, 第一电子设备使用第二 电子设备的显示屏作为其自己的显示屏,在第二电子设备的显示屏上显示的 实际上是第一电子设备的操作系统的显示界面。 而在第二电子设备上完成了 该应用程序的安装之后, 第一电子设备在其操作界面上是无法看到该应用程 序的, 而为了使得用户可以在第一电子设备中看到该应用程序, 则需要将该 应用程序的图标同步到第一电子设备。 在如上所述的现有的辅助工具当中, 也会将在第二电子设备中安装好的应用程序的图标同步到第一电子设备一 端,并且用户可通过该辅助工具来进行查看和操作。但在本发明的实施例中, 如上所述, 在将第二电子设备安装了该应用程序, 并将包含用于生成该应用 程序的图标的信息的消息发送到第一电子设备之后, 第一电子设备直接在第 二电子设备的显示屏上生成该应用程序的图标, 并将该应用程序的图标的属 性设置为在系统界面中可运行和可卸载。 这样, 用户可以不需要专门的辅助 工具, 直接在第一电子设备的操作系统的系统界面中看到该应用程序, 并且 直接在该系统界面上执行运行或卸载该应用程序的操作, 这可以显著地提高 用户在使用时的便利。
在上述操作方法中, 进一步包括: 当所述第一电子设备从用户接收到卸 载所述应用程序的第三命令后,将卸载所述应用程序的第四命令发送到所述 第二电子设备; 所述第二电子设备在接收到所述第四命令之后, 卸载所述应 用程序, 并将指示已经卸载所述应用程序的第三消息发送到所述第一电子设 备; 所述第一电子设备在接收到所述第三消息之后, 在所述第二电子设备的 显示屏上删除所述应用程序的图标。
如上所述, 在本发明的实施例中, 用户可以在第一电子设备的操作系统 的系统界面中卸载该安装在第二电子设备中的应用程序, 此时, 第一电子设 备和第二电子设备可以自动执行该应用程序在第二电子设备中的卸载和该 应用程序的图标在第一电子设备的界面中的删除。 如上所述, 在第一电子设 备和第二电子设备连接的情况下, 第二电子设备的显示屏上实际上显示的是 第一电子设备的操作系统的界面, 因此当从第一电子设备的界面上删除了该 应用程序的图标之后, 用户自然就不会再在第二电子设备的显示屏上看到该 应用程序的图标了。
在上述操作方法中, 第一电子设备和第二电子设备釆用不同操作系统。 例如, 如上所述, 第一电子设备可以是 Windows操作系统, 而第二电子设备 可以是 Android操作系统, 当然, 本领域技术人员可以理解, 第一电子设备 和第二电子设备也可以釆用其它的操作系统, 本发明的实施例并不意在对此 进行任何限制。
在上述操作方法中,所述第一电子设备通过修改所述第一电子设备的操 作系统的注册表而将所述应用程序的属性设置为在系统界面中可安装和将 所述应用程序的图标的属性设置为在系统界面中可运行和可卸载。
在本发明的实施例中,代替使用专门的辅助工具来进行应用程序包的安 装以及应用程序的运行和卸载, 用户可以在第一电子设备的操作系统的系统 界面中直接进行上述操作。 这里, 第一电子设备可以通过修改系统注册表的 方式来将该应用程序的属性设置为可安装的, 并将该应用程序的图标的属性 设置为可运行和可卸载的。 当然, 本领域技术人员可以理解, 第一电子设备 也可以釆用其它的方式来完成上述功能, 本发明的实施例并不意在对此进行 限制。
在上述操作方法中,所述第一电子设备和所述第二电子设备之间通过混 合连接进行通信。 这里, 在现有的混合系统技术当中, 通常釆用混合连接 ( Hybrid Connection ) 的方式来在第一电子设备和第二电子设备之间进行通 信, 因此, 在本发明的实施例中, 在第一电子设备和第二电子设备之间命令 和数据的传递也均是通过上述混合连接的方式来进行的。
在上述操作方法中,将所述应用程序和指示安装所述应用程序的第二命 令发送到所述第二电子设备具体为: 将所述应用程序发送到所述第二电子设 备的緩存区域。
在本发明的实施例中, 当将应用程序发送到第二电子设备时, 第二电子 设备需要存储该应用程序, 然后在第二电子设备中安装该应用程序, 因此, 第二电子设备中需要预先设置存储该应用程序的区域。 当然, 本领域技术人 员可以理解, 将该应用程序存储在第二电子设备的緩存区域中, 由于緩存区 域通常具有较快的存取速度, 可以相对提高第二电子设备安装该应用程序的 速度, 从而提高用户的便利。 但是, 如果基于其它考虑, 例如需要安装的应 用程序包很大等, 也可以将该应用程序存储在第二电子设备的其它存储区 域, 例如硬盘中。
如上所述, 通过上述根据本发明实施例的操作方法, 可以直接在第一电 子设备的操作系统的界面中完成需要在第二电子设备中安装的应用程序的 安装、 运行和卸载, 并且, 在基于本发明实施例的操作方法中, 上述过程均 是由第一电子设备和第二电子设备通过彼此之间的通信在后台完成的, 用户 不会感觉到上述过程。当然,为了用户可以清楚地了解应用程序的安装进程, 第一电子设备也可以在其操作系统的界面上显示指示有关上述过程的进度 的消息, 从而便于用户了解该应用程序的安装进度。 这里, 上述操作方法的 过程中, 最耗时的主要是两个部分, 即, 将应用程序发送到第二电子设备和 在第二电子设备中安装该应用程序, 第一电子设备可以在操作系统的界面上 将这两个过程合并显示为安装应用程序的进度, 也可以进行分开的显示。 并 且, 这里本领域技术人员可以理解, 当第一电子设备需要显示安装该应用程 序的进度时, 第二电子设备在安装应用程序时, 也就需要将关于该应用程序 的安装进度的消息传递给第一电子设备, 例如, 这也可以是通过第一电子设 备和第二电子设备之间的混合连接的方式进行的。
根据本发明实施例的另一方面,提供了一种电子设备, 可与具有显示屏 的另一电子设备连接, 所述电子设备包括: 嵌入控制器, 当检测到与所述另 一电子设备的连接时, 生成指示该连接的第一消息并向所述另一电子设备发 送指示所述第一消息; 控制器, 被配置为在接收到所述第一消息后, 将预安 装的应用程序的属性设置为相对于所述电子设备在系统界面中可安装; 在从 用户接收到安装所述应用程序的第一操作命令后,将所述应用程序和指示安 装所述应用程序的第二命令发送到所述另一电子设备; 从所述另一电子设备 接收包含用于生成所述应用程序的图标的信息的第二消息; 在接收到所述第 二消息之后, 在所述另一电子设备的显示屏上生成所述应用程序的图标, 并 将所述应用程序的图标的属性设置为在系统界面中可运行和可卸载。
图 20是示出根据本发明实施例的与上述操作方法相应的电子设备的示 意性框图。 如图 20所示, 电子设备 2000可与具有显示屏的另一电子设备连 接, 电子设备 2000包括: 嵌入控制器 2001 , 当检测到与另一电子设备的连 接时, 生成指示该连接的第一消息并向另一电子设备发送该第一消息; 控制 器 2002, 配置为在接收到第一消息后,将预安装的应用程序的属性设置为相 对于电子设备 2000在系统界面中可安装; 在从用户接收到安装应用程序的 第一操作命令后,将应用程序和指示安装应用程序的第二命令发送到该另一 电子设备; 从另一电子设备接收包含用于生成该应用程序的图标的信息的第 二消息; 在接收到该第二消息之后, 在另一电子设备的显示屏上生成该应用 程序的图标, 并将该应用程序的图标的属性设置为在系统界面中可运行和可 卸载。
这里, 本领域技术人员可以理解, 上述电子设备 2000是混合系统中的 主机端, 即 Base端, 用户在使用该混合系统中, 实际上是通过操作该电子 设备 2000来实现上述功能。
并且, 在现有的混合系统中, 当第一电子设备和第二电子设备连接时, 通常由第一电子设备的嵌入控制器来检测第一电子设备和第二电子设备的 连接。 但是, 本领域技术人员可以理解, 本发明的实施例不限于此, 在其它 情况下,也可能由第一电子设备的其它控制器或者第二电子设备的控制器来 检测第一电子设备和第二电子设备的连接。
根据本发明实施例的又一方面, 提供了一种电子设备, 具有显示屏, 并 可与另一电子设备连接, 所述电子设备包括: 控制器, 从所述另一电子设备 的嵌入控制器接收指示与所述另一电子设备的连接的第一消息; 从所述另一 电子设备接收一应用程序和指示安装所述应用程序的第二命令, 其中, 所述 应用程序的属性被设置为相对于所述另一电子设备在系统界面中可安装; 在 接收到所述第二命令和所述应用程序之后, 安装所述应用程序, 并将包含用 于生成所述应用程序的图标的信息的第二消息发送到所述另一电子设备; 其 中, 所述另一第一电子设备在接收到所述第二消息之后, 在所述第二电子设 备的显示屏上生成所述应用程序的图标, 并将所述应用程序的图标的属性设 置为在系统界面中可运行和可卸载。
图 21是示出根据本发明实施例的另一电子设备的示意性框图。 如图 21 所示, 电子设备 2100具有显示屏 2101 , 并可与另一电子设备连接, 电子设 备 2100包括: 控制器 2102 , 从另一电子设备的嵌入控制器接收指示与另一 电子设备的连接的第一消息; 从另一电子设备接收一应用程序和指示安装该 应用程序的第二命令, 其中, 该应用程序的属性被设置为相对于另一电子设 备在系统界面中可安装; 在接收到该第二命令和应用程序之后, 安装该应用 程序, 并将包含用于生成该应用程序的图标的信息的第二消息发送到另一电 子设备; 其中, 该另一第一电子设备在接收到第二消息之后, 在第二电子设 备的显示屏上生成该应用程序的图标, 并将该应用程序的图标的属性设置为 在系统界面中可运行和可卸载。
同样, 本领域技术人员可以理解, 上述电子设备 2100是混合系统中的 平板电脑端, 即 Pad端, 当用户在使用混合系统时, Base端利用 Pad端的显 示屏作为混合系统的显示器来进行显示, 因此, 在该电子设备 2100的显示 屏 2101上显示的实际上是 Base端的操作系统的界面。
下面, 将以第一电子设备为 base, 且第二电子设备为 Pad为例, 对根据 本发明实施例的操作方法的一个具体示例进行描述。
当 Pad端插上 Base端的时候, 由嵌入控制器( Embedded Controller )发 送出附加( attach )消息, 当 Base端的 AppInstallService (应用程序安装服务) 获得 Pad端插上的消息后, 通过修改操作系统注册表的方式, 在 Pad程序的 文件类型 (比如 Android系统的安装程序为 apk文件 ) 的右键菜单中自动添 加 "安装至 Pad端"选项, 并设置为默认打开方式。 用户双击 Pad程序包后, AppInstallService向 Pad端发送安装程序的命令, 同时将整个程序包以数据 流的形式通过混合连接发送至 Pad端的緩存区域。 Pad端接收到命令及程序 数据包后, 自动安装该程序包, 并将该应用程序名、 包名、 图标等信息以 XML格式通过混合连接发送给 Base端。 Base端的 AppInstallService将生成 上述 Pad程序的快捷图标,并在图标的右键菜单中添加 "在 Pad端删除程序 " 选项。 当用户需要删除该应用程序时, 用户选择图标右键菜单的 "在 Pad端 删除程序" 选项, AppInstallService通过混合连接向 Pad端发送删除程序的 命令。 Pad端接收到命令后, 自动删除相应程序包, 并通过混合连接回复消 息。 Base端接收到回复后, 自动删除 Pad程序的快捷图标。
在上述操作方法中,用户不需要安装额外的辅助工具,也不用进行 Base 端和 Pad端之间的连接配对, 所有数据传输均通过混合连接来完成, 并且, 用户不需要手动切换来进行 Pad端程序的安装与卸载, 所有步骤均在 Base 端就可完成。 此外, 在完成在 Pad端的程序安装后, 自动在 Base端同步相 应的程序图标, 方便用户运行与卸载。
通过根据本发明实施例的操作方法和电子设备,可以直接在第一电子设 备的操作系统的系统界面中完成需要在第二电子设备中安装的应用程序的 安装、 运行和卸载, 从而提高用户的便利度。
本发明以上实施例中的各个方案既可以独立使用, 也可以结合使用。 需要说明的是, 在本说明书中, 术语 "包括"、 "包含" 或者其任何其他 变体意在涵盖非排他性的包含, 从而使得包括一系列要素的过程、 方法、 物 品或者设备不仅包括那些要素, 而且还包括没有明确列出的其他要素, 或者 是还包括为这种过程、 方法、 物品或者设备所固有的要素。 在没有更多限制 的情况下, 由语句 "包括一个 ... ... " 限定的要素, 并不排除在包括所述要素 的过程、 方法、 物品或者设备中还存在另外的相同要素。
最后,还需要说明的是, 上述一系列处理不仅包括以这里所述的顺序按 时间序列执行的处理, 而且包括并行或分别地、 而不是按时间顺序执行的处 理。
本领域的技术人员可以清楚地了解到本发明实施例中的技术可借助软 件加必需的通用硬件平台的方式来实现。 基于这样的理解, 本发明实施例中 的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形 式体现出来, 该计算机软件产品可以存储在存储介质中, 如 R0M/RAM、磁碟、 光盘等, 包括若干指令用以使得一台计算机设备(可以是个人计算机, 服务 器, 或者网络设备等)执行本发明各个实施例或者实施例的某些部分所述的 方法。
本说明书中的各个实施例均釆用递进的方式描述,各个实施例之间相同 相似的部分互相参见即可,每个实施例重点说明的都是与其他实施例的不同 之处。 尤其, 对于系统实施例而言, 由于其基本相似于方法实施例, 所以描 述的比较简单, 相关之处参见方法实施例的部分说明即可。
以上所述的本发明实施方式, 并不构成对本发明保护范围的限定。任何 在本发明的精神和原则之内所作的修改、 等同替换和改进等, 均应包含在本 发明的保护范围之内。

Claims

权利要求书
1、 一种应用管理方法, 应用于与第二设备连接的第一设备, 所述方法 包括:
映射所述第二设备中的至少一个应用, 获得对应的至少一个应用标识; 检测第一操作;
当所述第一操作满足第一预设条件时,从所述至少一个应用标识中确定 第一应用的应用标识;
检测第二操作;
当所述第二操作满足第二预设条件时,依据所述第二操作获得对应的应 用管理命令, 并向所述第二设备发送所述应用管理命令, 以使所述第二设备 依据所述应用管理命令, 管理所述第一应用。
2、 根据权利要求 1所述的方法, 其中所述映射所述第二设备中的至少 一个应用包括:
第一设备向所述第二设备发送获取所述第二设备中已运行应用的请求; 接收所述第二设备根据所述请求返回的应用列表,所述应用列表中包含 所述第二设备中已运行应用的应用标识;
或者,
第一设备向所述第二设备发送获取所述第二设备中未运行应用的请求; 接收所述第二设备根据所述请求返回的应用列表,所述应用列表中包含 所述第二设备中未运行应用的应用标识。
3、根据权利要求 2所述的方法, 其中所述第一设备运行第一操作系统, 第二设备运行第二操作系统, 所述至少一个应用安装在所述第二操作系统 中;
所述第一设备包括显示单元,所述显示单元显示所述第一操作系统运行 的状态为所述第一设备的第一状态, 所述显示单元显示所述第二操作系统运 行的状态为所述第一设备的第二状态。
4、 根据权利要求 3所述的方法, 其中当第一设备向所述第二设备发送 获取所述第二设备中已运行应用的请求时, 所述向所述第二设备发送应用管 理命令包括:
所述第一设备在所述第一状态下, 向所述第二设备发送切换到所述第二 状态的切换命令, 以使所述第二设备在所述第二状态下执行所述第一应用, 或者
所述第一设备在所述第一状态下,向所述第二设备发送关闭所述第一应 用的关闭命令, 以使所述第二设备结束所述第一应用的进程, 或者
所述第一设备在所述第一状态下,向所述第二设备发送启动所述第一应 用的启动命令。
5. 根据权利要求 1所述的方法, 其中所述映射所述第二设备中的至少 一个应用包括:
检测与第二电子设备的数据连接, 获得检测结果;
当所述检测结果表明所述第一电子设备与所述第二电子设备的数据连 接成功时, 从所述第二电子设备获得应用列表, 所述应用列表包括所述至少 一个应用; 以及
根据所述应用列表,创建至少一个与所述应用列表中的一个应用对应的 应用标识, 其中, 所述应用标识被触发后, 能够在所述第二电子设备中启动 所述应用标识对应的应用。
6. 如权利要求 5所述的同步方法, 其中, 所述第一电子设备包括显示 单元, 所述方法还包括:
在所述第二电子设备中启动所述应用标识对应的应用时,在所述显示单 元上显示所述第二电子设备的运行界面。
7. 如权利要求 5所述的同步方法, 其中从所述第二电子设备获得应用 列表包括:
当所述检测结果表明所述第一电子设备与所述第二电子设备的数据连 接成功时, 向所述第二电子设备发送用于获取所述第二电子设备中安装的应 用的应用列表的请求, 然后接收所述第二电子设备响应于所述请求而发送的 应用列表; 或者
当所述检测结果表明所述第一电子设备与所述第二电子设备的数据连 接成功时, 接收所述第二电子设备自动发送的所述应用列表。
8. 如权利要求 5所述的同步方法, 其中从所述第二电子设备获得应用 列表包括:
从所述第二电子设备获得包括所述第二电子设备中的所有应用的应用 列表; 或者 从所述第二电子设备获得包括所述第二电子设备中的指定应用的应用 列表; 或者
从所述第二电子设备获得包括更新的应用的应用列表,其中所述第二电 子设备中已存储上次发送的应用列表; 或者
发送包括已有的应用标识所对应的应用的应用列表给所述第二电子设 备, 从第二电子设备获得包括更新的应用的应用列表, 其中所述第二电子设 备中不存储上次发送的应用列表。
9. 如权利要求 5所述的同步方法, 其中根据所述应用列表, 创建至少 一个与所述应用列表中的一个应用对应的应用标识包括:
在所述电子设备与所述第二电子设备断开时删除已创建的应用标识的 情况下, 创建与所述应用列表中的所有应用分别对应的多个应用标识; 或者 在所述电子设备与所述第二电子设备断开时不删除已创建的应用标识 的情况下,将所述应用列表中的所有应用与已有的应用标识所对应的应用比 较, 并且根据比较结果创建和 /或删除对应于更新的应用的应用标识。
10. 如权利要求 5所述的同步方法, 还包括:
在用户对所述第一电子设备上的更新请求单元进行操作的情况下,其中 所述更新请求单元是所述第一电子设备上设置的按键或对应于预定命令的 标识,
如果所述第一电子设备和第二电子设备的数据连接成功,则发送更新请 求到所述第二电子设备; 以及
如果所述第一电子设备和第二电子设备的数据连接不成功,则在所述第 一电子设备的记录单元中记录所述更新请求, 并且在所述第一电子设备和第 二电子设备的数据连接成功时,读取在所述记录单元中记录的更新请求并将 其发送到所述第二电子设备。
11. 如权利要求 10所述的同步方法, 还包括:
如果第二电子设备响应于所述更新请求检测到更新的应用,则接收从第 二电子设备发送的包括更新的应用的应用列表, 并且根据接收的应用列表创 建和 /或删除对应于更新的应用的应用标识。
12. 根据权利要求 5所述的方法, 还包括:
根据所述应用列表,所述第一电子设备关联所述应用列表中的应用和所 述第一存储单元和 /或所述第二存储单元中的对应文件类型的文件。
13. 如权利要求 12所述的关联方法, 其中所述预定条件包括: 所述检测结果表明所述第一电子设备与所述第二电子设备的数据连接 成功; 或者
所述检测结果表明所述第一电子设备与所述第二电子设备的数据连接 成功, 并且第一电子设备上的请求单元被操作, 所述请求单元是所述第一电 子设备上设置的按键或对应于预定命令的标识, 用于向所述第二电子设备发 送用于获取所述应用列表的请求。
14. 如权利要求 12所述的关联方法, 还包括:
在所述电子设备与所述第二电子设备断开时,解除关联所述应用列表中 的应用和所述第一存储单元和所述第二存储单元中的对应文件类型的文件。
15. 如权利要求 12所述的关联方法, 其中在第一电子设备的系统中保 存所述应用和所述文件的关联关系。
16. 如权利要求 15所述的关联方法, 其中通过用户的切换操作, 使用 在第二电子设备的系统中保存的所述应用和所述文件的关联关系。
17. 根据权利要求 5所述的方法, 还包括:
在激活所述第一存储单元和所述第二存储单元中存储的文件时,显示包 括与可激活所述文件的应用对应的标识的图形用户界面, 其中所述可激活所 述文件的应用包括所述第一电子设备本地安装的应用和所述第二电子设备 中安装的应用。
18、 根据权利要求 1所述的方法, 还包括:
所述第二电子设备接收所述第一电子设备通过所述通信端口发送的备 份请求, 所述备份请求中包括请求备份的所述第二客户端软件的应用信息; 所述第二电子设备查找所请求备份的所述第二客户端软件的应用; 所述第二电子设备通过所述通信端口向所述第一电子设备发送查找到 的所述第二客户端软件的应用, 以使所述第一电子设备进行备份。
19、 根据权利要求 18所述的方法, 其中
所述应用标识包含备份功能项;
在所述第二电子设备接收所述第一电子设备通过所述通信端口发送的 备份请求之前, 所述方法还包括:
所述第一电子设备接收用户操作所述备份功能项触发的备份指令, 生成备份请求; 所述第一电子设备通过所述通信端口向所述第二电子设备发送所 述备份请求。
20. 根据权利要求 1所述的方法, 其中所述第二电子设备具有显示屏, 所述方法还包括:
当检测到所述第一电子设备与第二电子设备连接时,向所述第一电子设 备发送指示该连接的第一消息;
所述第一电子设备在接收到所述第一消息后,将预安装的应用程序的属 性设置为相对于所述第一电子设备在系统界面中可安装;
所述第一电子设备在从用户接收到安装所述应用程序的第一操作命令 后,将所述应用程序和指示安装所述应用程序的第二命令发送到所述第二电 子设备;
所述第二电子设备在接收到所述第二命令和所述应用程序之后,安装所 述应用程序, 并将包含用于生成所述应用程序的图标的信息的第二消息发送 到所述第一电子设备;
所述第一电子设备在接收到所述第二消息之后,在所述第二电子设备的 显示屏上生成所述应用程序的图标, 并将所述应用程序的图标的属性设置为 在系统界面中可运行和可卸载。
21. 如权利要求 20所述的操作方法, 进一步包括:
当所述第一电子设备从用户接收到卸载所述应用程序的第三命令后,将 卸载所述应用程序的第四命令发送到所述第二电子设备;
所述第二电子设备在接收到所述第四命令之后, 卸载所述应用程序, 并 将指示已经卸载所述应用程序的第三消息发送到所述第一电子设备;
所述第一电子设备在接收到所述第三消息之后,在所述第二电子设备的 显示屏上删除所述应用程序的图标。
22、 一种应用管理设备, 所述应用管理设备作为第一设备, 与第二设备 连接, 所述第一设备包括:
映射单元, 用于映射第二设备中的至少一个应用, 获得对应的至少一个 应用标识;
第一检测单元, 用于检测第一操作;
确定单元, 用于当所述第一操作满足第一预设条件时, 从所述至少一个 应用标识中确定第一应用的应用标识; 第二检测单元, 用于检测第二操作;
管理单元, 用于当所述第二操作满足第二预设条件时,依据所述第二操 作获得对应的应用管理命令, 并向所述第二设备发送所述应用管理命令, 以 使所述第二设备依据所述应用管理命令, 管理所述第一应用。
23、 根据权利要求 22所述的设备, 所述映射单元包括至少一个下述单 元:
第一映射单元,用于向所述第二设备发送获取所述第二设备中已运行应 用的请求, 并接收所述第二设备根据所述请求返回的应用列表, 所述应用列 表中包含所述第二设备中已运行应用的应用标识;
第二映射单元,用于向所述第二设备发送获取所述第二设备中未运行应 用的请求, 并接收所述第二设备根据所述请求返回的应用列表, 所述应用列 表中包含所述第二设备中未运行应用的应用标识。
24、 根据权利要求 23所述的设备, 其中
所述第一设备运行第一操作系统, 第二设备运行第二操作系统, 所述至 少一个应用安装在所述第二操作系统中;
所述第一设备还包括:
显示单元,所述显示单元显示所述第一操作系统运行的状态为所述第一 设备的第一状态, 所述显示单元显示所述第二操作系统运行的状态为所述第 一设备的第二状态。
25、 根据权利要求 24所述的设备, 其中所述管理单元包括:
切换管理单元, 用于当所述第一设备在所述第一状态下, 由所述第一映 射单元向所述第二设备发送获取所述第二设备中已运行应用的请求时, 向所 述第二设备发送切换到所述第二状态的切换命令, 以使所述第二设备在所述 第二状态下执行所述第一应用, 或者
关闭管理单元, 用于当所述第一设备在所述第一状态下, 由所述第一映 射单元向所述第二设备发送获取所述第二设备中已运行应用的请求时, 向所 述第二设备发送关闭所述第一应用的关闭命令, 以使所述第二设备结束所述 第一应用的进程, 或者
启动管理单元, 用于当所述第一设备在所述第一状态下, 由所述第二映 射单元向所述第二设备发送获取所述第二设备中未运行应用的请求时, 向所 述第二设备发送启动所述第一应用的启动命令。
26. 根据权利要求 22所述的设备, 还包括:
连接检测单元,配置为检测与第二电子设备的数据连接,获得检测结果; 所述映射单元包括下述单元:
获取单元,配置为当所述检测结果表明所述电子设备与所述第二电 子设备的数据连接成功时, 从所述第二电子设备获得应用列表, 所述应用列 表包括至少一个所述第二电子设备中安装的应用; 以及
创建单元, 配置为根据所述应用列表, 创建至少一个与所述应用列 表中的一个应用对应的应用标识, 其中, 所述应用标识被触发后, 能够在所 述第二电子设备中启动所述应用标识对应的应用。
27. 如权利要求 26所述的设备, 还包括显示单元, 配置为在所述第二 电子设备中启动所述应用标识对应的应用时,显示所述第二电子设备的运行 界面。
28. 如权利要求 26所述的设备, 其中所述获取单元还配置为: 从所述第二电子设备获得包括所述第二电子设备中的所有应用的应用 列表; 或者
从所述第二电子设备获得包括所述第二电子设备中的指定应用的应用 列表; 或者
从所述第二电子设备获得包括更新的应用的应用列表,其中所述第二电 子设备中已存储上次发送的应用列表; 或者
发送包括已有的应用标识所对应的应用的应用列表给所述第二电子设 备, 从第二电子设备获得包括更新的应用的应用列表, 其中所述第二电子设 备中不存储上次发送的应用列表。
29. 如权利要求 26所述的设备, 其中所述创建单元还配置为: 在所述电子设备与所述第二电子设备断开时删除已创建的应用标识的 情况下, 创建与所述应用列表中的所有应用分别对应的多个应用标识; 或者 在所述电子设备与所述第二电子设备断开时不删除已创建的应用标识 的情况下,将所述应用列表中的所有应用与已有的应用标识所对应的应用比 较, 并且根据比较结果创建和 /或删除对应于更新的应用的应用标识。
30. 如权利要求 29所述的设备, 其中所述创建单元还配置为: 如果第二电子设备响应于所述更新请求检测到更新的应用,则接收从第 二电子设备发送的包括更新的应用的应用列表, 并且根据接收的应用列表创 建和 /或删除对应于更新的应用的应用标识。
31. 根据权利要求 26所述的设备, 其中所述第二电子设备包括第二存 储单元, 所述设备还包括:
第一存储单元, 配置为存储各种用户和文件;
关联单元, 配置为根据所述应用列表, 关联所述应用列表中的应用和所 述第一存储单元和 /或所述第二存储单元中的对应文件类型的文件。
32. 如权利要求 31所述的设备, 其中所述预定条件包括:
所述检测结果表明所述第一电子设备与所述第二电子设备的数据连接 成功; 或者
所述检测结果表明所述第一电子设备与所述第二电子设备的数据连接 成功, 并且第一电子设备上的请求单元被操作, 所述请求单元是所述第一电 子设备上设置的按键或对应于预定命令的标识, 用于向所述第二电子设备发 送用于获取所述应用列表的请求。
33. 如权利要求 31所述的设备, 还包括解除关联单元, 配置为在所述 电子设备与所述第二电子设备断开时, 解除关联所述应用列表中的应用和所 述第一存储单元和所述第二存储单元中的对应文件类型的文件。
34. 如权利要求 31所述的设备, 其中在所述电子设备的系统中保存所 述应用和所述文件的关联关系。
35. 如权利要求 34所述的设备, 其中通过用户的切换操作, 使用在第 二电子设备的系统中保存的所述应用和所述文件的关联关系。
36. 如权利要求 26所述的设备, 还包括:
显示单元,配置为在激活所述第一存储单元和所述第二存储单元中存储 的文件时, 显示包括与可激活所述文件的应用对应的标识的图形用户界面, 第二电子设备中安装的应用。
37. 根据权利要求 22所述的设备, 还包括:
请求接收单元,用于接收所述另一电子设备通过所述通信端口发送的第 一备份请求, 所述第一备份请求中包括请求备份的所述电子设备中客户端软 件的应用信息;
应用查找单元,用于查找所请求备份的所述电子设备中客户端软件的应 用; 应用发送单元,用于通过所述通信端口向所述另一电子设备发送查找到 的应用, 以使所述另一电子设备进行备份。
38、 根据权利要求 37所述的设备, 其中
所述应用标识包含备份功能项;
所述电子设备还包括:
请求触发单元, 用于接收用户操作所述备份功能项触发的备份指 令, 生成第二备份请求;
请求发送单元,用于通过所述通信端口向所述另一电子设备发送所 述第二备份请求。
39. 如权利要求 22所述的应用管理设备, 还包括:
嵌入控制器, 当检测到与所述另一电子设备的连接时, 生成指示该连接 的第一消息并向所述另一电子设备发送指示所述第一消息;
控制器, 被配置为在接收到所述第一消息后, 将预安装的应用程序的属 性设置为相对于所述电子设备在系统界面中可安装;
在从用户接收到安装所述应用程序的第一操作命令后,将所述应用程序 和指示安装所述应用程序的第二命令发送到所述另一电子设备;
从所述另一电子设备接收包含用于生成所述应用程序的图标的信息的 第二消息;
在接收到所述第二消息之后,在所述另一电子设备的显示屏上生成所述 应用程序的图标, 并将所述应用程序的图标的属性设置为在系统界面中可运 行和可卸载。
40. 如权利要求 22所述的应用管理设备, 还包括:
控制器,从所述另一电子设备的嵌入控制器接收指示与所述另一电子设 备的连接的第一消息;
从所述另一电子设备接收一应用程序和指示安装所述应用程序的第二 命令, 其中, 所述应用程序的属性被设置为相对于所述另一电子设备在系统 界面中可安装;
在接收到所述第二命令和所述应用程序之后, 安装所述应用程序, 并将 包含用于生成所述应用程序的图标的信息的第二消息发送到所述另一电子 设备;
其中, 所述另一第一电子设备在接收到所述第二消息之后, 在所述第二 电子设备的显示屏上生成所述应用程序的图标, 并将所述应用程序的图标的 属性设置为在系统界面中可运行和可卸载。
PCT/CN2012/001083 2011-08-15 2012-08-14 一种应用管理方法及设备 WO2013023440A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US14/239,186 US9779106B2 (en) 2011-08-15 2012-08-14 Application management method and device

Applications Claiming Priority (10)

Application Number Priority Date Filing Date Title
CN201110233852.1 2011-08-15
CN2011102338521A CN102938703A (zh) 2011-08-15 2011-08-15 一种应用管理方法及设备
CN201110260774.4 2011-09-05
CN2011102607744A CN102981914A (zh) 2011-09-05 2011-09-05 同步方法和电子设备
CN201110314486.2 2011-10-17
CN201110314486.2A CN103049457B (zh) 2011-10-17 2011-10-17 关联方法、电子设备和混合系统
CN201110337685.5A CN103092635B (zh) 2011-10-31 2011-10-31 操作方法和电子设备
CN201110338645.2A CN103092721B (zh) 2011-10-31 2011-10-31 一种应用备份方法、电子设备及系统
CN201110337685.5 2011-10-31
CN201110338645.2 2011-10-31

Publications (1)

Publication Number Publication Date
WO2013023440A1 true WO2013023440A1 (zh) 2013-02-21

Family

ID=47714727

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/001083 WO2013023440A1 (zh) 2011-08-15 2012-08-14 一种应用管理方法及设备

Country Status (2)

Country Link
US (1) US9779106B2 (zh)
WO (1) WO2013023440A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015059585A1 (en) * 2013-10-21 2015-04-30 Yandex Europe Ag Installing applications via restoration of a false backup
WO2022252939A1 (zh) * 2021-05-31 2022-12-08 华为技术有限公司 一种共享桌面的方法和电子设备

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3137981A4 (en) * 2014-04-30 2017-12-06 Hewlett-Packard Development Company, L.P. Multi architecture manager
CN104484229A (zh) * 2014-12-29 2015-04-01 宇龙计算机通信科技(深圳)有限公司 切换操作系统的方法、装置及终端
US10725623B2 (en) 2018-03-28 2020-07-28 International Business Machines Corporation Browsing applications on mobile device via a wearable device
CN110543312B (zh) * 2018-05-29 2022-03-25 华为技术有限公司 一种应用软件安装方法、设备以及服务器
US10890988B2 (en) 2019-02-06 2021-01-12 International Business Machines Corporation Hierarchical menu for application transition
CN112073812B (zh) * 2019-06-10 2022-08-19 聚好看科技股份有限公司 一种智能电视上的应用管理方法及显示设备
CN115657897A (zh) * 2020-06-29 2023-01-31 华为技术有限公司 跨设备桌面管理方法、第一电子设备及第二电子设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101655798A (zh) * 2008-08-18 2010-02-24 联想(北京)有限公司 一种计算机和虚拟机环境中应用程序部署和运行的方法
WO2010052979A1 (ja) * 2008-11-05 2010-05-14 ソニー株式会社 情報処理装置、情報処理方法及びプログラム
CN101938585A (zh) * 2009-06-25 2011-01-05 株式会社理光 图像形成设备和信息处理方法
CN102033591A (zh) * 2009-09-29 2011-04-27 联想(北京)有限公司 便携通信系统、便携设备及其电源管理控制方法

Family Cites Families (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6044394A (en) * 1997-07-21 2000-03-28 International Business Machines Corporation Managing independently executing computer tasks that are interrelated by dataflow
JP2000259437A (ja) 1999-03-10 2000-09-22 Nippon Telegr & Teleph Corp <Ntt> ソフトウェアカットスルー方法、オペレーティングシステムを記録した記録媒体及びコンピュータシステム
US20020026507A1 (en) * 2000-08-30 2002-02-28 Sears Brent C. Browser proxy client application service provider (ASP) interface
US20060240806A1 (en) * 2001-07-18 2006-10-26 Saban Demirbasa Data security device
CN101149772B (zh) 2002-04-22 2012-11-14 微软公司 应用程序共享安全
US7188347B2 (en) 2002-05-24 2007-03-06 Nokia Corporation Method, apparatus and system for connecting system-level functionality of domestic OS of a mobile phone to any application operating system
GB2413407B (en) 2004-04-22 2007-11-07 Ibm Method and system for software or data distribution
US7703073B2 (en) 2004-06-08 2010-04-20 Covia Labs, Inc. Device interoperability format rule set and method for assembling interoperability application package
CN1722128A (zh) 2004-07-14 2006-01-18 英华达(上海)电子有限公司 资源共享系统及其操作界面
EP1760584A1 (en) 2005-08-23 2007-03-07 Research In Motion Limited Method and system for transferring an application state from a first electronic device to a second electronic device
US8037473B2 (en) 2006-10-20 2011-10-11 International Business Machines Corporation Method to share licensed applications between virtual machines
US8209615B2 (en) * 2006-11-22 2012-06-26 Qualcomm Incorporated Apparatus and methods of linking to an application on a wireless device
US8645948B2 (en) * 2006-12-12 2014-02-04 Qualcomm Incorporated Apparatus and methods for client-driven server-side installation
US7865571B2 (en) 2007-01-08 2011-01-04 Mspot, Inc. Method and apparatus for transferring digital content from a personal computer to a mobile handset
CN101148772A (zh) 2007-07-24 2008-03-26 哈尔滨工程大学 一种熔盐电解共沉积Mg-Li合金的工艺方法
EP2031912B1 (en) 2007-07-27 2013-01-09 Research In Motion Limited Wireless communication systems
CN101150809B (zh) 2007-11-03 2011-02-02 青岛海信移动通信技术股份有限公司 移动终端处理器串口唤醒与流控的方法
WO2010050927A1 (en) 2008-10-28 2010-05-06 Hewlett-Packard Development Company, L.P. File type association in a remote computing session
CN101727449A (zh) 2008-10-28 2010-06-09 国际商业机器公司 利用远程应用处理本地文件的系统和方法
CN101860591A (zh) 2009-04-08 2010-10-13 北京搜狗科技发展有限公司 一种共享应用程序的方法及装置
US20100262953A1 (en) * 2009-04-14 2010-10-14 Barboni Michael P Systems and methods for automatically enabling and disabling applications and widgets with a computing device based on compatibility and/or user preference
CN101656789B (zh) 2009-07-01 2012-09-05 中兴通讯股份有限公司 手机实现管理应用程序信息的方法及应用程序管理器
US20110137909A1 (en) 2009-12-07 2011-06-09 Sap Ag Location independent execution of user interface operations
US20110247013A1 (en) * 2010-04-01 2011-10-06 Gm Global Technology Operations, Inc. Method for Communicating Between Applications on an External Device and Vehicle Systems
CN101853184A (zh) 2010-05-21 2010-10-06 中兴通讯股份有限公司 应用程序的管理方法和装置、以及终端
CN102033951B (zh) 2010-12-15 2012-09-05 北京新媒传信科技有限公司 Web数据库平台
AU2011202832B2 (en) * 2010-12-21 2013-01-24 Lg Electronics Inc. Mobile terminal and method of controlling a mode switching therein
CN102110031A (zh) 2011-02-23 2011-06-29 宇龙计算机通信科技(深圳)有限公司 基于android系统的应用程序备份与恢复的方法
KR101229752B1 (ko) * 2011-06-01 2013-02-05 엘지전자 주식회사 이동 단말기 및 이동 단말기의 제어 방법

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101655798A (zh) * 2008-08-18 2010-02-24 联想(北京)有限公司 一种计算机和虚拟机环境中应用程序部署和运行的方法
WO2010052979A1 (ja) * 2008-11-05 2010-05-14 ソニー株式会社 情報処理装置、情報処理方法及びプログラム
CN101938585A (zh) * 2009-06-25 2011-01-05 株式会社理光 图像形成设备和信息处理方法
CN102033591A (zh) * 2009-09-29 2011-04-27 联想(北京)有限公司 便携通信系统、便携设备及其电源管理控制方法

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015059585A1 (en) * 2013-10-21 2015-04-30 Yandex Europe Ag Installing applications via restoration of a false backup
WO2022252939A1 (zh) * 2021-05-31 2022-12-08 华为技术有限公司 一种共享桌面的方法和电子设备

Also Published As

Publication number Publication date
US20140351215A1 (en) 2014-11-27
US9779106B2 (en) 2017-10-03

Similar Documents

Publication Publication Date Title
WO2013023440A1 (zh) 一种应用管理方法及设备
JP5851023B2 (ja) 電力状態ベースのバックアップの方法と装置
JP5728130B2 (ja) 多段階多ソースバックアップの方法と装置
JP5819518B2 (ja) 多ソース復元の方法と装置
KR102052977B1 (ko) 다중 입력 제어 방법 및 시스템과 이를 지원하는 전자 장치
US9503520B2 (en) Application synchronization among multiple computing devices
US9384098B1 (en) Portable data archiving device
US20150020013A1 (en) Remote operation of applications using received data
EP3399408B1 (en) Information processing apparatus and computer readable storage medium
WO2014089734A1 (zh) 终端和应用程序恢复方法
JP2022538081A (ja) 画面共有処理方法、装置、機器及び記憶媒体
CN104375857B (zh) 一种应用程序运行多个实例的方法、装置及终端设备
WO2022076049A1 (en) Systems and methods for providing tab previews via an operating system user interface
CN107632872B (zh) 桌面布局处理方法、用户数据处理方法及装置、计算机存储介质
JP5250645B2 (ja) 情報処理装置
WO2019015491A1 (zh) 应用程序的分身方法、装置、设备和介质
WO2019085533A1 (zh) 用于终端设备的应用处理的方法和终端设备
WO2022042233A1 (zh) 应用界面迁移系统、方法及相关设备
WO2014136429A1 (en) Information processing apparatus and method for the same
JP6547531B2 (ja) コンテンツ指定プログラム及び携帯端末
US8862548B2 (en) File system cloning between a target device and a host device
JP5250644B2 (ja) 情報処理装置
CN109597537B (zh) 文件同步方法、装置及设备
WO2022052758A1 (zh) 配网方法及设备
JP7455613B2 (ja) 情報処理装置、その制御方法、並びにプログラム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12824149

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 14239186

Country of ref document: US

122 Ep: pct application non-entry in european phase

Ref document number: 12824149

Country of ref document: EP

Kind code of ref document: A1