Remote device task display and control system and method

Abstract

The invention provides a remote device task display and control system and method, the system comprises N devices, the N devices comprise a first terminal and a second terminal, icons of the N devices and at least one task card are displayed in a nearest task interface of the first terminal, a user can carry out various convenient operations on any card, and the user experience is improved. According to the method, migration of the task cards and running of the applications corresponding to the task cards on different devices are achieved, the method can be suitable for various different user requirements and can be suitable for almost all the applications, the task cards can be flexibly arranged on the first terminal, the task cards of the different devices can be displayed on the first terminal, the applications do not need to be adapted, and user experience is improved. And the requirement of the user for managing and controlling the multi-equipment task is met. Moreover, the user operation process during task migration is simplified, the user operation is simplified, and the user experience is improved.

Description

[0001] This application is a divisional application. The international application number of the original application is PCT / CN2022 / 117047, the national application number of the original application is 202280060850.3, and the original application date is September 5, 2022. The entire contents of the original application are incorporated into this application by reference. Technical Field

[0002] The present application relates to the field of terminal technology, and in particular to a system and method for displaying and controlling remote device tasks. Background Art

[0003] For the mobile phone, tablet and other terminals currently used by the user, the user can usually enter the recent task interface of the terminal by swiping up from the bottom of the touch screen of the terminal or clicking the "multi-task" button. In the recent task interface, the user can query and manage the applications recently used by the terminal and other terminals to achieve cross-device migration of applications.

[0004] However, in the process of managing the recently used applications of a terminal and other terminals on the recent task interface of a certain device, different cross-device operation methods (or cross-device entrances) are provided for different applications (APPs), which need to be adapted by the applications, resulting in a variety of cross-device entrances, difficulty in adapting third-party applications, high adaptation costs, and, for applications that need to be migrated, user operations are complicated during the migration process, resulting in poor user experience. Summary of the invention

[0005] This application provides a system and method for displaying and controlling remote device tasks, which can facilitate users to view and manage historical tasks of other devices on one device. It can be applied to almost all applications, and can flexibly layout task cards and display task cards of different devices without the need for application adaptation, meeting the user's needs for managing and controlling multi-device tasks. In addition, it simplifies the user operation process during task migration, simplifies user operations, and improves user experience.

[0006] In a first aspect, a method for displaying and controlling tasks of a remote device is provided, the method being applied in a communication system, the communication system comprising N devices, the N devices comprising a first terminal and a second terminal, the method comprising: the first terminal displays a recent task interface, the recent task interface displaying icons of the N devices and at least one task card; when displaying the task card of the second terminal in the recent task interface of the first terminal, the task card of the second terminal is arranged in the recent task interface of the first terminal according to the user's usage status of the second terminal; wherein the user's usage status of the second terminal comprises: any one of a horizontal screen usage status, a vertical screen usage status, a folded screen vertical screen usage status, a folded screen horizontal screen usage status, and a folded screen vertical screen usage status.

[0007] The method for displaying and controlling remote device tasks provided in the first aspect utilizes the user's usage status of the second terminal, the user's usage status of the first terminal, and the screen size of the first terminal to display the task cards of the second terminal in a single row or multiple rows in the recent task interface of the first terminal, which can improve the efficiency of displaying the task cards of the second terminal, facilitate users to view and manage historical tasks of other devices on one device, and improve user experience.

[0008] Exemplarily, the N devices may include: mobile phones, large-screen devices, tablet computers, PCs, car computers, folding-screen devices, etc.

[0009] In a possible implementation of the first aspect, the first terminal displays the task cards of the second terminal in a single row or multiple rows in the recent task interface of the first terminal according to any one of the following situations: when the second terminal is used in landscape mode, when the second terminal is used in portrait mode, when the folding screen is used in portrait mode in an unfolded state, when the folding screen is used in landscape mode in an unfolded state, when the folding screen is used in landscape mode in an unfolded state, when the folding screen is used in landscape mode in an unfolded state, and when the folding screen is used in portrait mode in an unfolded state. In the implementation, the task cards of the second terminal are displayed in a single row or multiple rows in the recent task interface of the first terminal according to the user's use status of the second terminal, the user's use status of the first terminal, and the screen size of the first terminal, so as to improve the efficiency of the task card display of the second terminal, facilitate users to view and manage historical tasks of other devices on one device, and improve user experience.

[0010] In a possible implementation of the first aspect, when a task card of the second terminal is displayed in a recent task interface of the first terminal, the task card of the second terminal includes a task card of a first screen snapshot of the desktop of the second terminal. In this implementation, the desktop snapshot of the second terminal can be displayed in the recent task interface of the first terminal, which is convenient for the user to view and improves the user experience.

[0011] In a possible implementation of the first aspect, the method further includes: the first terminal receives a first operation of a user on a task card of a first screenshot of a desktop of the second terminal; and the first terminal displays the task card of the second screenshot of the desktop of the second terminal in a recent task interface of the first terminal according to the first operation of the user. In this implementation, the user can view snapshots of different desktops of the second terminal, thereby improving the user experience.

[0012] In a possible implementation of the first aspect, the method further includes: the first terminal receives a second operation of the user on a task card of a first screen snapshot of the desktop of the second terminal or a task card of a second screen snapshot of the desktop of the second terminal; the first terminal displays the interface of the first screen of the desktop of the second terminal or the interface of the first screen of the desktop of the second terminal on the first terminal according to the second operation, or runs an application on the first screen interface of the desktop of the second terminal or an application on the second screen interface of the desktop of the second terminal on the first terminal. In this implementation, the user can operate the application of different desktop snapshots of the second terminal to quickly display or open the application on the local machine, which is simple to operate and improves the user experience.

[0013] In a possible implementation of the first aspect, at least one of a FA card, a floating window, and a floating ball exists on a task card of the first screenshot of the desktop of the second terminal and / or on a task card of the second screenshot of the desktop of the second terminal. In this implementation, a FA card, a floating window, or a floating ball can be displayed on the desktop snapshot of the second terminal, and different methods can be flexibly used to display the task card of the second terminal in the recent task interface of the first terminal, thereby improving the user experience.

[0014] In a possible implementation of the first aspect, the method further includes: the first terminal receives a third operation of the user on the FA card, floating window, or floating ball; the first terminal displays the first screen interface of the second terminal desktop or the first screen interface of the second terminal desktop on the first terminal according to the third operation, or runs the application corresponding to the FA card, the floating window, or the floating ball on the first terminal. In this implementation, the user can operate the FA card, floating window, or floating ball on the second terminal desktop snapshot to quickly display or open the application on the local machine, which is simple to operate and improves the user experience.

[0015] In a possible implementation of the first aspect, when a task card of a second terminal is displayed in a recent task interface of a first terminal, the task card of the second terminal includes a snapshot of a control device for controlling the second terminal. In this implementation, task cards related to the second terminal can be flexibly displayed in the recent task interface of the first terminal, thereby improving user experience.

[0016] In a possible implementation of the first aspect, the method further includes: the first terminal receives a fourth operation of the user on the snapshot of the control device; the first terminal displays a detail interface of the control device on the first terminal, or remotely controls the second terminal according to the fourth operation. In this implementation, the user can view a task card of the control device for controlling the second device on the first terminal, and can operate the task card to quickly control the second terminal device on the local device, which is simple to operate and improves the user experience.

[0017] For example, the second terminal is a large-screen device, and the control device is a remote controller.

[0018] In a possible implementation manner of the first aspect, when a task card of the second terminal is displayed in a recent task interface of the first terminal, the task card of the second terminal includes: a task card of a desktop application of the second terminal.

[0019] In a possible implementation of the first aspect, the method further includes: the first terminal receives a fifth operation of the user on the application on the task card of the second terminal desktop application; the first terminal manages the second terminal desktop application on the first terminal according to the fifth operation. In this implementation, the user can view the desktop application icon of the second terminal on the first terminal, and can operate the desktop application icon to help the second terminal manage the application (sort, create folders, delete, etc.), so as to quickly help the second terminal manage the application on the local machine, simplify the operation, and improve the user experience.

[0020] In a possible implementation of the first aspect, the N devices include light devices, and the light devices include wearable devices and smart home devices used by users. When task cards of the light devices are displayed in the recent task interface of the first terminal, the task cards of the light devices include task cards corresponding to different tasks being run by the light devices. In this implementation, the task cards of the light devices can be displayed in the recent task interface of the first terminal, which enriches the types of task cards displayed in the recent task interface of the first terminal and is user-friendly.

[0021] Exemplarily, light devices are a general term for IoT devices, wearable devices, smart home devices, etc. For example, light devices may include: smart refrigerators, smart air conditioners, smart cooking pots, smart range hoods, smart speakers, smart watches, etc.

[0022] In a possible implementation of the first aspect, the method further includes: the first terminal receives a sixth operation of the user on the task card of the device; the first terminal displays a detail interface of the task being run by the light device on the first terminal, or remotely controls the task being run by the light device according to the sixth operation. In this implementation, the user can view the task card corresponding to the task being run by the associated light device on the first terminal, and can operate the card corresponding to the task being run by the light device, so as to remotely control the task being run by the light device, which is simple to operate and improves the user experience.

[0023] In a possible implementation of the first aspect, the N devices include a third terminal, and the method further includes: the first terminal receives a seventh operation of a user on a task card of the light device; the first terminal shares the task card of the light device to the third terminal according to the seventh operation; and the third terminal displays the task card of the light device in a recent task interface. In this implementation, the task card of the light device can be pushed to the third terminal for display, so that the user can control the task being run by the light device on the third terminal, thereby improving the user experience.

[0024] In a possible implementation of the first aspect, the method further includes: displaying a task card corresponding to the task being run by the second light device on a display interface of the first light device, the light device including the first light device and the second light device; the first light device receiving an eighth operation of the user on the task card corresponding to the task being run by the second light device; and the first light device remotely controlling the task being run by the second light device according to the eighth operation. In this implementation, the user can remotely control the tasks being run by other light devices on the light device, the operation is simple, and the user experience is improved.

[0025] In a possible implementation of the first aspect, the method further includes: verifying the identity of the user through the first light device, and / or a device associated with the first light device; after the user's identity authentication is passed, displaying the task card of the first terminal and / or the second terminal on the display interface of the first light device.

[0026] In a possible implementation of the first aspect, the method further includes: the first light device receives a ninth operation of the user on the task card of the first terminal and / or the second terminal; and the first light device remotely controls the application corresponding to the task card of the first terminal and / or the second terminal according to the ninth operation. In this implementation, the user can remotely control the historical task cards and foreground task cards of other smart terminals on the light device, which is simple to operate and improves the user experience.

[0027] In a possible implementation of the first aspect, the method further includes: when displaying a task card of the second terminal in the recent task interface of the first terminal, receiving a tenth operation of the user on a first task card in the task card of the second terminal, the tenth operation being used to pull up a first application corresponding to the first task card on the first terminal; the first terminal runs the first application on the first terminal according to the tenth operation; the first terminal and the second terminal determine the running status of the first application according to different modes in which the first application migrates to the first terminal. In this implementation, after pulling up applications of other terminals, the first terminal can determine and display the running status of the application on the first terminal according to different modes in which the application migrates to the first terminal, thereby ensuring the efficiency with which the application can run on the first terminal, thereby improving the user experience.

[0028] In a possible implementation of the first aspect, the first terminal and the second terminal determine the running status of the first application according to different modes of migrating the first application to the first terminal, including: when the first application is migrated to the first terminal using a copy mode, the first terminal and the second terminal respectively and independently run the first application, synchronize data of the first application on the first terminal and the second terminal, synchronize operation status, and the first terminal and the second terminal respectively display the first application according to their respective screen adaptations.

[0029] In a possible implementation of the first aspect, the method further includes: the second terminal receives an eleventh operation of the user on the first application, and the eleventh operation is used to pull back the first application from the first terminal; after the second terminal receives the eleventh operation, the first terminal continues to run the first application. In this implementation, the normal operation of the first application can be guaranteed.

[0030] In a possible implementation of the first aspect, the first terminal and the second terminal determine the running status of the first application according to different modes of migrating the first application to the first terminal, including: when the first application is migrated to the first terminal in a migration mode using window projection technology, and the first application supports multiple instances, the first terminal and the second terminal respectively and independently run the first application, the data of the first application on the first terminal and the second terminal are synchronized, the operation status is not synchronized, and the first terminal and the second terminal respectively display the first application according to their respective screen adaptations.

[0031] In a possible implementation of the first aspect, the method further includes: the second terminal receives a twelfth operation of the user on the first application, the twelfth operation is used to pull back the first application from the first terminal; after the second terminal receives the twelfth operation, the first terminal continues to run the first application.

[0032] In a possible implementation of the first aspect, the first terminal and the second terminal determine the running status of the first application according to different modes of migration of the first application to the first terminal, including: when the first application is migrated to the first terminal in a migration mode using window projection technology, and the first application does not support multiple instances, the first terminal or the second terminal runs the first application in the same time period.

[0033] In a possible implementation of the first aspect, the method further includes: the second terminal receives a thirteenth operation of the user on the first application, the thirteenth operation is used to pull back the first application from the first terminal; after the second terminal receives the thirteenth operation, the first terminal exits the first application, and the second terminal runs the first application. For example, the description corresponding to Example 15 can be referred to, and for the sake of brevity, it is not repeated here.

[0034] In a possible implementation of the first aspect, the first terminal and the second terminal determine the running status of the first application according to different modes of migration of the first application to the first terminal, including: when the first application is migrated to the first terminal using the migration mode of FA technology, before the first terminal runs the first application, the first terminal installs the first application or the FA of the first application; the first terminal and the second terminal independently run the first application, the data of the first application on the first terminal and the second terminal are synchronized, the operation status is not synchronized, and the first terminal and the second terminal respectively display the first application according to their respective screen adaptations.

[0035] In a possible implementation of the first aspect, the method further includes: the second terminal receives a fourteenth operation of the user on the first application, the fourteenth operation is used to pull back the first application from the first terminal; after the second terminal receives the fourteenth operation, the first terminal continues to run the first application. In this implementation, the normal operation of the first application can be guaranteed, and the user experience can be improved.

[0036] In a possible implementation of the first aspect, the area of ​​the screen of the first terminal is larger than the area of ​​the screen of the second terminal, and after the first application is pulled up on the first terminal, the first application is run on the first terminal, including: automatically displaying and running the first application in a floating window or full screen mode on the first terminal. In this implementation, the first application can be displayed and run in a floating window or full screen mode on the first terminal to improve user experience. For example, the first terminal can be a PC device.

[0037] In a possible implementation of the first aspect, the area of ​​the screen of the first terminal is larger than the area of ​​the screen of the second terminal. After the first application is launched on the first terminal, the method further includes: displaying a prompt message on the interface of the first terminal, the prompt message is used to prompt the user to display the first application in a floating window or full screen; the first terminal displays the first application in a floating window or full screen on the first terminal according to the user's choice. In this implementation, the first application can be displayed and run in a floating window or full screen on the first terminal according to the user's choice, thereby improving the user experience. For example, the first terminal can be a PC device.

[0038] In a possible implementation of the first aspect, after the first application is pulled up on the first terminal, the method further includes: when the screen width of the first terminal is greater than the screen width of the second terminal, the first application is displayed on the first terminal in a parallel view mode, and the first application is displayed on the second terminal in a non-parallel view mode; or, when the screen width of the first terminal is less than the screen width of the second terminal, the first application is displayed on the first terminal in a non-parallel view mode, and the first application is displayed on the second terminal in a parallel view mode; or, when the first application is displayed in a horizontal screen on the second terminal, the first application is displayed in a horizontal screen mode on the first terminal; or, when the first application is displayed in a vertical screen on the second terminal, the first application is displayed in a vertical screen mode on the second terminal. In this implementation, the first application can be flexibly displayed and run in different forms according to the screen sizes of the first terminal and the second terminal to improve the user experience.

[0039] In a possible implementation of the first aspect, during the process of running the first application on the first terminal, the method further includes: after the distance between the first terminal and the second terminal is greater than a preset first distance, displaying first prompt information and second prompt information on the interface of the first terminal, the first prompt information prompting the user that the first terminal and the second terminal will disconnect the communication connection, and the second prompt information prompting the user that the first application originates from the second terminal. In this implementation, by displaying the prompt information to the user, the user can be informed of the communication connection status, thereby improving the user experience.

[0040] In a possible implementation of the first aspect, during the process of running the first application on the first terminal, the method also includes: after the communication connection between the first terminal and the second terminal is disconnected, the first terminal uses a mask to display the first application, and an instruction among a third prompt information, a fourth prompt information and a fifth prompt information is displayed on the interface of the first terminal; wherein the third prompt information prompts the user that the first terminal and the second terminal have disconnected the communication connection, the fourth prompt information prompts the user to exit the first application, and the fifth prompt information prompts the user to reconnect.

[0041] In a possible implementation of the first aspect, the method further includes: after the first terminal and the second terminal meet a preset condition, the first terminal and the second terminal are automatically reconnected; after the reconnection is successful, the first terminal resumes normal display and runs the first application. In this implementation, by displaying connection status prompt information, automatic reconnection prompt information, and application exit prompt information to the user, and automatically reconnecting after the conditions are met, the sequential operation of task migration is guaranteed, thereby improving the user experience.

[0042] In a possible implementation of the first aspect, the method further includes: the first terminal receives a fifteenth operation of the user on a second task card in a recent task interface of the first terminal, the fifteenth operation is used to migrate a second application corresponding to the second task card to a target device for operation, the N devices including the target device; the first terminal determines the target device according to the fifteenth operation; the target device runs the second application. In this implementation, the user can conveniently determine the target device to which the task card needs to be migrated, the operation is simple and easy to implement, thereby improving the user experience.

[0043] In a possible implementation of the first aspect, the first terminal determines the target device according to the fifteenth operation, including: when the user long presses the second task card, the recent task interface of the first terminal hides the task cards other than the second task card and the icon of the device that cannot run the second application; the first terminal determines the target device from the device icons displayed in the recent task interface of the first terminal according to the user's operation. In this implementation, by hiding the icons of unavailable devices and other task cards, it is convenient for the user to determine the target device that the task card needs to be migrated, thereby improving the efficiency of the user in determining the target device.

[0044] In a possible implementation of the first aspect, the first terminal determines the target device according to the fifteenth operation, including: when the user drags the second task card and the second task card overlaps with the identification of the fourth terminal, determining that the fourth terminal is the target device, and the N devices include the fourth terminal.

[0045] In a possible implementation of the first aspect, the first terminal determines the target device according to the fifteenth operation, including: when the user drags the second task card, and the second task card overlaps with the fourth terminal and the fifth terminal, the terminal device indicated by the device icon with the largest overlapping area is determined as the target device, and the N devices include the fourth terminal and the fifth terminal. In this implementation, the operation is simple and easy to implement, and the accuracy of determining the target device can be improved.

[0046] In a possible implementation of the first aspect, the first terminal determines the target device according to the fifteenth operation, including: when the user drags the second task card upward, and the distance moved by the second task card is greater than a preset distance, determining that the device indicated by the device icon directly above the second task card is the target device. In this implementation, the operation is simple and easy to implement, and the accuracy of determining the target device can be improved.

[0047] In a possible implementation of the first aspect, the first terminal determines the target device according to the fifteenth operation, including: when the user drags the second task card upward, and the distance between the second task card and the top of the first terminal screen is less than a preset distance, determining that the device indicated by the device icon directly above the second task card is the target device. In this implementation, the operation is simple, easy to implement, and the accuracy of determining the target device can be improved.

[0048] In a possible implementation of the first aspect, after the target device is determined, when the user drags the second task card to the target device, as the distance between the second task card and the icon of the target device decreases, the area of ​​the second task card decreases. In this implementation, the operation is simple, easy to implement, and the accuracy of determining the target device can be improved.

[0049] In a possible implementation of the first aspect, after determining the target device, the method further includes: when the second task card does not overlap with the icon of the target device, the icon of the target device moves downward by a preset distance, or the display state of the icon of the target device changes to a selected state. In this implementation, it is convenient for the user to view the selected target device, thereby improving the user experience.

[0050] In a possible implementation of the first aspect, after the target device is determined, the method further includes: when the user drags the second task card and the icon of the target device does not overlap, the user lets go, and the second task card automatically migrates to the target device; the target device runs the second application. In this implementation, after the target device has been determined, but the task card has not yet reached the icon hotspot of the target device, if the user lets go at this time, the task card automatically flies to the device icon, completing the cross-device interaction, thereby improving the efficiency of the task cross-device interaction.

[0051] In a possible implementation of the first aspect, after determining the target device, the method further includes: the first terminal receives a sixteenth operation of the user on the second task card in the recent task interface of the first terminal, and the sixteenth operation is used to select a new target device. In this implementation, the selected target device is changed by the user's operation on the task card, thereby improving the efficiency of changing the target device.

[0052] In a possible implementation of the first aspect, when the target device has a black screen, before the target device runs the second application, the method further includes: the target device automatically turns on the screen; after the target device automatically turns on the screen, an unlocking interface is displayed; and the target device receives an unlocking operation by the user. In this implementation, the target device automatically turns on the screen, and after the screen turns on, unlocking is triggered, and then the user manually unlocks, thereby ensuring that the target device can run the migrated task normally and ensuring the efficiency of task migration.

[0053] In a possible implementation of the first aspect, when the target device has a black screen, before the target device runs the second application, the method further includes: the target device automatically turns on the screen and displays an unlocking interface; and the target device receives an unlocking operation by the user. In this implementation, the target device automatically turns on the screen, and after the screen turns on, the user is automatically triggered to manually unlock the screen, thereby improving the efficiency of task migration while ensuring that the target device can run the migrated task normally.

[0054] In a possible implementation of the first aspect, when the target device has a black screen, before the target device runs the second application, the method further includes: the target device automatically lights up the screen and automatically unlocks the device. In this implementation, the target device automatically lights up the screen and automatically unlocks the device, thereby improving the efficiency of task migration while ensuring that the target device can normally run the migrated task.

[0055] In a possible implementation of the first aspect, the source device corresponding to the second application is the first terminal, and the target device runs the second application, including: the target device uses the hardware capabilities of the first terminal to run the second application on the target device; or the target device uses the hardware capabilities of the first terminal and the target device to run the second application on the target device; or the target device uses the hardware capabilities of the target device to run the second application on the target device, and the first terminal releases the hardware capabilities occupied by the second application; or the target device uses the hardware capabilities of the target device to run the second application on the target device, and the first terminal does not release the hardware capabilities occupied by the second application. In this implementation, by different allocation rules for the hardware capabilities of the first terminal and the target device, it is ensured that the migrated task can run normally on the target device, thereby improving the efficiency of task migration.

[0056] In a possible implementation of the first aspect, the method further includes: during the process of the target device using the hardware capabilities of the target device to run the second application, the target device receives an instruction to run the third application, and there is a conflict between the hardware capabilities used to run the third application on the target device and the hardware capabilities used to run the second application; the target device uses the hardware capabilities of the target device to run the third application; the second application switches back to the first terminal device and continues to run the second application using the hardware capabilities of the first terminal. In this implementation, after the task is migrated from the source device to the target device, when a new task from the target device preempts the hardware, the source end hardware capabilities can be coordinated to ensure that the target device's tasks are executed first, which can ensure that the target device's tasks are executed first.

[0057] In a possible implementation of the first aspect, the method further includes: during the process of the target device using the hardware capabilities of the target device to run the second application, the target device receives an instruction to run the third application, and the hardware capabilities used to run the third application on the target device conflict with the hardware capabilities to run the second application; the target device uses the hardware capabilities of the target terminal to run the second application and the third application at the same time. In this implementation, after the task is migrated from the source device to the target device, when a new task from the target device preempts the hardware, the hardware capabilities of the target device can be separated according to the tasks, and multiple tasks can be supported at the same time, which can ensure that the tasks on the target device and the migrated tasks can run normally, thereby improving the efficiency of the target device task operation.

[0058] In a possible implementation of the first aspect, the method further includes: during the process of the target device running the second application using the hardware capabilities of the first terminal, the first terminal receives an instruction to run the fourth application, and there is a conflict between the hardware capabilities used to run the second application on the target device and the hardware capabilities used to run the fourth application on the first terminal; the target device suspends running the second application; the first terminal runs the fourth application using the hardware capabilities of the first terminal; after the first terminal finishes running the fourth application, the target device continues to run the second application using the hardware capabilities of the first terminal. In this implementation, after the task is migrated from the source device to the target device, when a new task from the source device preempts the hardware, the migrated task on the target device is suspended, and after the new task is finished on the source device, the migrated task on the target device automatically continues, which can ensure that the new task on the source device is executed first.

[0059] In a possible implementation of the first aspect, the method further includes: during the process of the target device running the second application using the hardware capabilities of the first terminal, the first terminal receives an instruction to run the fourth application, and there is a conflict between the hardware capabilities used to run the second application on the target device and the hardware capabilities used to run the fourth application on the first terminal; the target device switches to continue running the second application using the hardware capabilities of the target device, and the first terminal runs the fourth application using the hardware capabilities of the first terminal. In this implementation, after the task is migrated from the source device to the target device, when a new task from the source device preempts the hardware, the source device uses its own hardware capabilities to execute the new task, and the target device uses its own hardware capabilities to execute the task migrated from the source device, which can ensure that both the task on the source device and the migrated task can run normally, thereby improving the efficiency of task operation.

[0060] In a possible implementation of the first aspect, the method further includes: during the process of the target device running the second application using the hardware capabilities of the first terminal, the first terminal receives an instruction to run the fourth application, and there is a conflict between the hardware capabilities used to run the second application on the target device and the hardware capabilities used to run the fourth application on the first terminal; the target device continues to run the second application using the hardware capabilities of the first terminal, and the first terminal runs the fourth application using the hardware capabilities of the first terminal. In this implementation, after the task is migrated from the source device to the target device, when facing the new task from the source device occupying the hardware, the hardware capabilities of the source device can be separated according to the tasks, and multiple tasks can be supported at the same time, which can ensure that the tasks on the source device and the migrated tasks can run normally, thereby improving the efficiency of task running on the source device.

[0061] In a possible implementation of the first aspect, the method further includes: the first terminal receives a seventeenth operation of the user on the fifth task card in the recent task interface of the first terminal, the seventeenth operation is used to install the fifth application corresponding to the fifth task card on the first terminal or other devices among the N devices; the first terminal or other devices among the N devices install the fifth application according to the seventeenth operation. In this implementation, the multi-device task center is used to help other devices or the present device install applications, which is convenient to operate, improves the efficiency of application installation, and improves user experience.

[0062] In a possible implementation of the first aspect, the method also includes: the first terminal receives the user's eighteenth operation on the sixth task card and the seventh task card in the recent task interface of the first terminal, and the eighteenth operation is used to display the applications corresponding to the sixth task card and the seventh task card in the first display mode on the first terminal or other devices among the N devices; the first terminal or other devices among the N devices display the application corresponding to the sixth task card and the application corresponding to the seventh task card in the first display mode.

[0063] Exemplarily, the first display mode is: split screen display mode; or, the application corresponding to the sixth task card is displayed in full screen, and the application corresponding to the seventh task card is displayed in a floating window; or, the application corresponding to the sixth task card is displayed in a floating window, and the application corresponding to the seventh task card is displayed in a floating window. In this implementation, through the multi-device task center, the user can quickly perform local device or create a split screen / floating window across devices. The operation is convenient and it is easy to form a new task card. In addition, the new task card can have different display modes, which improves the diversity and flexibility of the task card.

[0064] In a second aspect, a system for displaying and controlling remote device tasks is provided, the system comprising N devices, the N devices comprising a first terminal and a second terminal, wherein the first terminal is used to display a recent task interface, in which icons of the N devices and at least one task card are displayed; when the task card of the second terminal is displayed in the recent task interface of the first terminal, the first terminal is further used to: display the task card of the second terminal in a single row or in multiple rows in the recent task interface of the first terminal, according to any one of the following: when the second terminal is used in landscape mode, in portrait mode, in a foldable screen in an unfolded portrait mode, in a foldable screen in an unfolded landscape mode, in a folded landscape mode, and in a folded portrait mode.

[0065] The system for displaying and controlling remote device tasks provided in the second aspect utilizes the user's usage status of the second terminal, the user's usage status of the first terminal, and the screen size of the first terminal to display the task cards of the second terminal in a single row or multiple rows in the recent task interface of the first terminal, thereby improving the efficiency of displaying the task cards of the second terminal, making it convenient for users to view and manage historical tasks of other devices on one device, and improving user experience.

[0066] In a possible implementation manner of the second aspect, the task card of the second terminal includes a task card of a first screenshot of the desktop of the second terminal and a task card of a second screenshot of the desktop of the second terminal.

[0067] In a possible implementation of the second aspect, at least one of an interface capability FA card, a floating window, and a floating ball exists on the task card of the first screenshot of the second terminal desktop and / or on the task card of the second screenshot of the second terminal desktop.

[0068] In a possible implementation of the second aspect, the N devices include light devices, which include wearable devices and smart home devices used by users. The first terminal is also used to: display the task card of the light device in the recent task interface of the first terminal, wherein the task card of the light device includes task cards corresponding to different tasks being run by different light devices.

[0069] In a possible implementation of the second aspect, the source device corresponding to the first application is the second terminal. During the process of migrating the first application to the first terminal for operation, the first terminal and the second terminal are also used to: determine the running status of the first application according to different modes of migration of the first application to the first terminal; wherein the different modes of migration of the first application to the first terminal include: a copy mode, a migration mode based on window projection technology, and a migration mode using interface capability FA technology.

[0070] In a possible implementation of the second aspect, the source device corresponding to the second application is the first terminal. During the process of migrating the second application to the second terminal for execution, the second terminal is further used for: the second terminal uses the hardware capabilities of the first terminal to run the second application on the target device; or the second terminal uses the hardware capabilities of the first terminal and the second terminal to run the second application on the second terminal; or the second terminal uses the hardware capabilities of the second terminal to run the second application on the second terminal, and the first terminal releases the hardware capabilities occupied by the second application; or the second terminal uses the hardware capabilities of the second terminal to run the second application on the second terminal, and the first terminal does not release the hardware capabilities occupied by the second application.

[0071] In a third aspect, a method for displaying and controlling remote device tasks is provided, which is applied to a first terminal, and the method includes: the first terminal displays a recent task interface, in which icons of N devices and at least one task card are displayed, and the N devices include a first terminal and a second terminal; when the task card of the second terminal is displayed in the recent task interface of the first terminal, the task card of the second terminal is displayed in a single row or in multiple rows in the recent task interface of the first terminal according to any one of when the second terminal is used in landscape mode, in portrait mode, in a folded screen in an unfolded portrait mode, in a folded screen in an unfolded landscape mode, in a folded screen in a folded landscape mode, and in a folded screen in a folded portrait mode.

[0072] The method for displaying and controlling remote device tasks provided in the third aspect utilizes the user's usage status of the second terminal, the user's usage status of the first terminal, and the screen size of the first terminal to display the task cards of the second terminal in a single row or multiple rows in the recent task interface of the first terminal, which can improve the efficiency of displaying the task cards of the second terminal, facilitate users to view and manage historical tasks of other devices on one device, and improve user experience.

[0073] In a possible implementation manner of the third aspect, the task card of the second terminal includes a task card of the first screenshot of the desktop of the second terminal and a task card of the second screenshot of the desktop of the second terminal.

[0074] In a possible implementation of the third aspect, at least one of an interface capability FA card, a floating window, and a floating ball exists on the task card of the first screenshot of the second terminal desktop and / or on the task card of the second screenshot of the second terminal desktop.

[0075] In a possible implementation manner of the third aspect, the N devices include light devices, and the light devices include wearable devices and smart home devices used by users. The method further includes:

[0076] The task card of the light device is displayed in the recent task interface of the first terminal, wherein the task card of the light device includes task cards corresponding to different tasks being run by the light device.

[0077] In a possible implementation of the third aspect, the source device corresponding to the first application is the second terminal. During the process of migrating the first application to the first terminal for operation, the method also includes: the first terminal determines the running status of the first application according to different modes of migrating the first application to the first terminal; wherein the different modes of migrating the first application to the first terminal include: a copy mode, a migration mode based on window projection technology, and a migration mode utilizing interface capability FA technology.

[0078] In a possible implementation of the third aspect, the source device corresponding to the second application is the first terminal. During the process of migrating the second application to the second terminal for execution, the method further includes: the first terminal releasing the hardware capabilities of the first terminal occupied by the second application; or the first terminal does not release the hardware capabilities of the first terminal occupied by the second application.

[0079] In a fourth aspect, a communication device is provided, which includes a unit for executing each step performed by a first terminal or a second terminal in the above first aspect or any possible implementation method of the first aspect, or the communication device includes a unit for executing each step in the third aspect or any possible implementation method of the third aspect.

[0080] In a fifth aspect, a communication device is provided, which includes at least one processor and a memory, the processor and the memory are coupled, and the memory stores program instructions. When the program instructions stored in the memory are executed by the processor, the various steps performed by the first terminal or the second terminal in the above first aspect or any possible implementation of the first aspect are executed, or the various steps in the above third aspect or any possible implementation of the third aspect are executed.

[0081] In a sixth aspect, a communication device is provided, which includes at least one processor and an interface circuit, and the at least one processor is used to execute: each step performed by the first terminal or the second terminal in the possible implementation of the first aspect or any aspect of the first aspect, or each step in the possible implementation of the third aspect or any aspect of the third aspect.

[0082] In a seventh aspect, a terminal device is provided, which includes any communication device provided in the third aspect, the fourth aspect or the fifth aspect.

[0083] In an eighth aspect, a system for displaying and controlling remote device tasks is provided, the system comprising: the first terminal and the second terminal in the first aspect.

[0084] Optionally, the system may further include the third terminal and the fourth terminal in the above-mentioned first aspect.

[0085] In the ninth aspect, a computer program product is provided, which includes a computer program, which, when executed by a processor, is used to execute the various steps performed by the first terminal or the second terminal in the first aspect or any possible implementation of the first aspect, or to execute the various steps in the third aspect or any possible implementation of the third aspect.

[0086] In the tenth aspect, a computer-readable storage medium is provided, which stores a computer program. When the computer program is executed, it is used to execute the various steps performed by the first terminal or the second terminal in the first aspect or any possible implementation of the first aspect, or to execute the various steps in the third aspect or any possible implementation of the third aspect.

[0087] In the eleventh aspect, a chip is provided, comprising: a processor for calling and running a computer program from a memory, so that a communication device equipped with the chip executes each step performed by a first terminal or a second terminal in the first aspect or any possible implementation method of the first aspect, or executes each step of the third aspect or any possible implementation method of the third aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0088] Figure 1 It is a schematic diagram of a communication system applicable to an embodiment of the present application.

[0089] Figure 2(a)-Figure 2(c) This is a schematic diagram of an interface for displaying a recent task interface and performing sliding operations in the recent task interface provided by the present application.

[0090] Figure 3(a)-Figure 3(b) This is a schematic diagram of an interface for performing touch operations in a recent task interface provided by the present application.

[0091] Figure 3(c)-Figure 3(d) This is a schematic diagram of an interface for establishing a trusted relationship between devices provided by this application.

[0092] Figure 4(a)-Figure 4(b) This is a flow chart of determining the layout of task cards of other terminals displayed in the recent task interface of a first terminal provided by the present application.

[0093] Figure 5(a)-Figure 6(e) This is an interface schematic diagram of displaying different layouts of task cards of other different terminals in the recent task interface of the first terminal provided by the present application.

[0094] Figure 7(a)-Figure 7(q) This is an interface diagram of different contents displayed on the last task card in the recent task interface of the first terminal provided by the present application.

[0095] Figure 7(r)-Figure 7(s) This is a schematic diagram of the interface for displaying task cards of other devices on a light device provided by this application.

[0096] FIG8( a ) is a flowchart of determining the status displayed and the running status of the application when the task card of the remote device is pulled up on the recent task interface of the first terminal based on different migration modes provided by the present application.

[0097] Figure 8(b)-Figure 8(n) This is an interface diagram of the running status of the first application on different devices based on different migration modes provided by the present application.

[0098] Figure 8(o)-Figure 8(p) This is an interface diagram for operating task cards in the recent task interface of the first terminal provided by the present application to help other devices install applications.

[0099] Figure 8(q)-Figure 8(u) This is a schematic diagram of an interface for operating different task cards in the recent task interface of the first terminal provided by the present application, and establishing different display forms of multiple task cards.

[0100] Figure 8(v)-Figure 8(w) This is a schematic diagram of the interface displayed after the connection between the source device and the target device is interrupted after the task migration provided by this application.

[0101] Figure 9(a)-Figure 9(v) This is an interface diagram for operating task cards and migrating task cards in the recent task interface of the first terminal provided by the present application.

[0102] Figure 10(a)-Figure 10(c)This is a schematic diagram of the interface of the target device changing from a black screen state to displaying the application after the application is migrated to the target device, as provided by the present application.

[0103] Figure 11(a)-Figure 11(k) This is a schematic diagram of the interface of the application running after the application is migrated from the source device to the target device according to the different allocation of hardware capabilities involved in the application, as provided by the present application.

[0104] FIG. 12( a ) is a schematic diagram of an interface for displaying a task card of a mobile phone in a recent task interface of a vehicle computer provided by the present application.

[0105] FIG12( b ) is a schematic diagram of an interface for displaying a task card of a PC device in a recent task interface of a vehicle computer provided by the present application.

[0106] FIG12( c ) is a schematic diagram of an interface for displaying a task card of a mobile phone in a recent task interface of a PC device provided by the present application.

[0107] Fig.13 This is an interface schematic diagram provided by the present application for migrating a task card of a first terminal to a third terminal in a recent task interface of a second terminal.

[0108] Figure 14(a)-Figure 14(s) This is a schematic diagram of a super desktop interface displayed on different devices provided by the present application.

[0109] Figure 15(a)-Figure 15(g) This is a schematic diagram of an interface of a super desktop entrance and a super desktop layout displayed on different devices provided by the present application.

[0110] Figure 16(a)-Figure 16(h) This is a schematic diagram of an interface displayed by a terminal device during a temporary component super desktop process provided by the present application.

[0111] Fig.17 It is a structural diagram of a terminal device provided in an embodiment of the present application.

[0112] Fig.18 This is a software structure block diagram of a terminal device provided in an embodiment of the present application.

[0113] Fig.19 It is a flow chart provided in an embodiment of the present application.

[0114] Fig. 20 It is a schematic diagram of a chip system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0115] Currently, users own more and more types of smart terminals, which generates many new user demands.

[0116] For example, when a user uses a mobile phone to play videos or edit documents, it is inconvenient to use because the screen of the mobile phone is small. It is more convenient to play videos or edit documents on a large-screen device. Therefore, it is necessary to seamlessly migrate the video played or the edited document on the mobile phone to another large-screen device.

[0117] For example, users often shop and chat on their phones at the same time, or watch videos and chat at the same time. In the scenario of multitasking on the phone, the screen may be blocked due to multitasking. Therefore, different tasks can be run in parallel on multiple devices used by the user, which can not only keep multitasking in parallel, but also avoid the situation where the screen is blocked due to multitasking.

[0118] For another example, sometimes the device used by the user needs to be charged, but the user wants to continue the unfinished task on the device. In this case, the task on the device can be transferred to another device, so that the user can continue the unfinished task on the device.

[0119] In each of the above scenarios, the migration (or also called continuation) of applications or tasks on different devices is involved.

[0120] Currently, for the migration scheme of applications on different devices, the relevant technologies mention:

[0121] Device 1 and device 2 are logged in with the same account, and the user is running an application (such as application A) on device 1. When device 1 and device 2 are close to each other, there are corresponding prompts on both devices 1 and 2. For example, the icon of device 1 will be displayed in the upper right corner of the icon of application A at the bottom of the Dock of device 2 (such as a personal computer PC), or a prompt will be displayed at the bottom of the multitasking interface of device 1 (such as a mobile phone / tablet): to prompt the user to migrate application A to device 2. The user can open application A on device 2 and continue (handoff) use by clicking the icon of device 1 at the bottom of the Dock on device 2, or clicking the prompt at the bottom of the multitasking interface of device 1.

[0122] However, in the above solution, different cross-device operation methods (or cross-device entrances) are provided for different applications (APPs), which require the applications to adapt. For example: for call and information applications, notification messages are used for migration; for cross-device migration of shooting applications, device icons are used for migration. In addition, the applications that support migration are mainly native applications of the device (for example, office applications, photo editing applications, etc.), resulting in a variety of cross-device entrances, difficulty in adapting third-party applications, and high adaptation costs. In addition, for applications that need to be migrated, user operations are relatively complicated, resulting in a poor user experience.

[0123] In view of this, the present application provides a method for displaying and controlling remote device tasks, which can facilitate users to view and manage historical tasks of other devices on one device. It can be applied to almost all applications without the need for application adaptation, meeting the user's needs for managing and controlling multi-device tasks, and further simplifying the application connection process, simplifying user operations, and improving user experience.

[0124] The following will specifically describe the display and control method of remote device tasks provided by this application.

[0125] Taking the Android system as an example, the system provides a system-level interface to display the recently accessed task list. The user can clean up a recently run application or all recently run applications. In this way, the local application (APP) of the terminal can be cleaned up. In the distributed scenario, it is necessary to further display and clean up the recently used applications of other terminals.

[0126] refer to Figure 1 , Figure 1 It is a schematic diagram of a communication system provided by the present application and applicable to an embodiment of the present application.

[0127] For example, Figure 1 As shown, the communication system 100 may include various terminal devices (in this application, the terminal devices may also be referred to as electronic devices), such as a mobile phone 101, a tablet computer 102, a large screen device 103, etc. Optionally, the communication system 100 may also include smart home devices such as a smart refrigerator 104 and a smart air conditioner 105. When the smart terminal is a smart home device such as a smart refrigerator or an air conditioner, the recently used application may refer to the tasks currently or recently executed by these smart home devices.

[0128] Of course, the communication system 100 may also include other terminal devices, such as: smart speakers, vehicle-mounted devices (also referred to as vehicle computers), laptop computers, ultra-mobile personal computers (UMPCs), handheld computers, netbooks, personal digital assistants (PDAs), wearable electronic devices, virtual reality devices, Internet of Things (IOT) devices, etc. Figure 1 Not shown.

[0129] The embodiments of the present application do not specifically limit the type of terminal device (such as mobile phone 101, tablet computer 102 or large screen device 103). In some embodiments, the terminal device in the embodiments of the present application can be a mobile phone, a wearable device (such as a smart bracelet, a smart watch, a headset, etc.), a tablet computer, a laptop computer, a handheld computer, a notebook computer, an ultra-mobile personal computer (UMPC), a cellular phone, a personal digital assistant (PDA), an augmented reality (AR)\virtual reality (VR) device, etc., and can also be a television, a large screen, a speaker, a television, a refrigerator, an air conditioner, a car-mounted device, a printer, a projector, etc. Exemplary embodiments of electronic devices include but are not limited to devices equipped with Electronic devices running Harmony or other operating systems.

[0130] The terminals in the communication system 100 may be interconnected via a communication network. Exemplarily, the communication network may be a wired network or a wireless network. For example, the communication network may be a local area network (LAN) or a wide area network (WAN), such as the Internet. The above-mentioned communication network can be implemented using any known network communication protocol, and the above-mentioned network communication protocol can be various wired or wireless communication protocols, such as Ethernet, universal serial bus (USB), FIREWIRE, global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), Bluetooth, wireless fidelity (Wi-Fi), NFC, voice over Internet protocol (VoIP), communication protocols supporting network slicing architecture or any other suitable communication protocols.

[0131] That is to say, each terminal in the communication system 100 can form a network (ie, networking) according to a certain communication protocol and networking strategy, so that each terminal in the audio system can communicate with each other.

[0132] For example, each electronic device in the communication system 100 can access a Wi-Fi network provided by an access point (AP) such as a router, so that a Wi-Fi connection is established between each electronic device. For another example, each terminal in the communication system 100 can log in to the same account (such as a Huawei account), and then interconnect through one or more servers.

[0133] The recent task interface is an interface in the system user interface (User Interface, UI) for displaying the terminal's recently run tasks. When the terminal is triggered to open the recent task interface, the terminal's display screen can display the terminal's recently run tasks, or the recently run applications. Among them, for multiple interfaces of the same application, each of the multiple interfaces may be displayed as an independent task in the recent task interface. For example, when two Word documents are opened in the terminal, if the recent task interface is entered, two task cards can be used to display the interfaces corresponding to the two Word documents respectively. For the convenience of explanation, this application does not specifically distinguish between tasks and applications, and this application does not limit whether multiple interfaces of an application are displayed as one task card or multiple task cards.

[0134] As an example, when the user triggers the terminal to open the first application, and returns to the main interface through a gesture or a key, the first application is switched to the background; the user then opens the second application, and triggers the terminal to enter the recent task interface when the second application is running. It can be understood that since the system function of the terminal is currently running the program corresponding to the recent task interface in the foreground, the second application is also switched to the background. In this case, the first application and the second application are both recently run applications, and their information will appear in the recent task interface.

[0135] The recent task interface displays information about multiple recently run applications. Normally, the recent task interface will display the logo and task card corresponding to the application, where the logo of the application can be the application name expressed in words or the application icon (icon), and the task card is a rectangular box, which contains a snapshot of the application. For example, the system will capture the interface when the application is switched to the background as a snapshot. The logo of the application and the task card can be a whole, such as the logo is embedded in the task card as part of the task card; or the logo of the application and the task card are in a separated state, which is not limited in this application. When there are multiple applications running recently on the terminal, there are multiple task cards. Due to the page display or interface settings, some task cards are fully displayed in the recent task interface, some task cards are partially displayed in the recent task interface, and some task cards may be hidden (not displayed) in the recent tasks.

[0136] As shown in Figure 2(a), the user can make an upward swipe gesture from the bottom of the terminal screen on the main interface of the terminal to trigger the terminal's display screen to display the recent task interface. In actual applications, other gestures or other operation methods (such as clicking the "multitasking" button or long pressing the "back" button, etc.) can also be used to trigger the terminal's display screen to display the recent task interface. This application does not limit the method of triggering the terminal to display the recent task interface.

[0137] As shown in Figure 2(b), the display screen of the terminal displays the recent task interface. In the recent task interface, the task card of the first application is fully displayed, while the task card of the second application is partially displayed. The recently run applications also include a third application, and the card of the third application is hidden in the recent task interface. In the recent task interface shown in Figure 2(b), when the user makes a right sliding gesture on the touch screen, the recent task interface displayed on the display screen of the terminal can be switched to the recent task interface shown in Figure 2(c).

[0138] As shown in Figure 2(c), the task card currently fully displayed in the recent task interface is switched from the task card of the first application to the task card of the second application. Before the switch, as shown in Figure 2(b), the task card of the first application is fully displayed in the recent task interface, and the task card of the second application is partially displayed in the recent task interface; after the switch, as shown in Figure 2(c), the task card of the first application is partially displayed in the recent task interface, and the task card of the second application is fully displayed in the recent task interface. And after the switch, as shown in Figure 2(c), the task card of the third application is changed from a hidden state to a partially displayed state in the recent task interface.

[0139] As shown in Figures 2(b) and 2(c), in the case where there are multiple recently run tasks, a task card of a recently run task can be fully displayed in the recent task interface, and the left and / or right parts of the task card of the recently run task that is fully displayed can display task cards of other recently run tasks, and the fully displayed task card and the partially displayed task card are displayed side by side from left to right. In practical applications, the recent task interface can also display task cards in other ways. For example, a task card of a recently run task is fully displayed in the recent task interface, and the upper and / or lower parts of the task card of the recently run task that is fully displayed can display task cards of other recently run tasks, and the fully displayed task card and the partially displayed task card are displayed side by side from top to bottom. The embodiment of the present application does not limit the way in which task cards are displayed in the recent task interface, and the recent task interface can be triggered by operation to switch to display different task cards, and the fully displayed task card exists before and / or after the switch.

[0140] In the recent tasks interface, users can perform different operations to achieve different effects.

[0141] For example, in FIG3( a ), when the user makes a click gesture in an area outside of a task card in the recent task interface, the recent task interface exits, and the display screen of the terminal displays the main interface.

[0142] As shown in Figure 3(b), when the user makes a click gesture in the area corresponding to the task card of the first application, the recent task interface exits, the display screen of the electronic device is used to display the interface of the first application, and the first application switches from the background to the foreground.

[0143] In FIG. 3( a ) and FIG. 3( b ), the terminal's response to the user's gesture is only used as an example. In actual applications, other responses may be possible, and this application does not limit this.

[0144] In addition, in actual applications, referring to Figures 3(a) and 3(b), the recent task interface can also display a space for cleaning up all recently run applications, such as the trash can icon at the bottom of Figures 3(a) and 3(b). The user can close all recently run tasks by clicking on the icon. In specific implementations, other methods can also be used to close all or a certain application running in floating window mode in the recent task interface. As an example, the application can also be closed by swiping up, swiping down, or clicking a specific control in the task card (for example, a close button in the task card).

[0145] The above has introduced the contents and basic operations of the recent task interface. In this application, the recent task interface of a terminal can not only display the applications recently run by the terminal, but also display the applications recently run by other terminals. Furthermore, it is also possible to operate the task cards corresponding to one or some applications to achieve cross-device migration and application operation of applications.

[0146] by Figure 1 The scenario shown is used as an example to illustrate that the first terminal, the second terminal and the third terminal are connected via a network. When the user operates the first terminal to enter the recent task interface, the recent task interface displays not only the applications recently used by the first terminal, but also the applications recently used by the second and third terminals.

[0147] Optionally, before displaying the applications recently used by the second terminal and the third terminal in the recent task interface of the first terminal, the first terminal, the second terminal and the third terminal establish a trusted relationship in advance. That is, the first terminal, the second terminal and the third terminal are bound or a device-level authentication relationship is established. In the embodiment of the present application, the specific process of binding or establishing a device-level authentication relationship between the first terminal, the second terminal and the third terminal is not limited.

[0148] In some embodiments, an electronic device (using mobile phone 101 as an example) can find through a mobile network or the Internet that the account logged in by one or more other devices (including tablet computer 102, large screen device 103, etc.) is the account of mobile phone 101, or the account logged in by the one or more other devices is an associated account of the account logged in by mobile phone 101, then the one or more other devices and mobile phone 101 have a trust relationship. The one or more other devices include tablet computer 102, large screen device 103, smart refrigerator 104, smart air conditioner 105, etc. Devices logged in to the same account or associated accounts can obtain each other's device information and realize data communication. Among them, the associated account can be an account authorized by the same account.

[0149] The above account can be an account provided by the cloud server provider to the user, such as a Huawei account, or an account used to log in to an application, such as an account of various communication software, an account of payment software, etc.

[0150] In some embodiments, a trusted relationship can be established between terminal devices by manually adding, including, for example, touch and scan methods. Exemplarily, as shown in FIG3(c), the user can enter the device management interface 110 from the settings application of the mobile phone 101, and the device management interface 110 may include a list named "My Devices". Among them, "My Devices" includes this machine, the second terminal 102, the third terminal 103, and other smart devices. This machine, the second terminal 102, the third terminal 103, and other smart devices can be devices with the same account (for example, sharing a Huawei account). Alternatively, this machine, the second terminal 102, the third terminal 103, and other smart devices can be devices with different accounts but authenticated and bound.

[0151] Optionally, the device management interface 110 may include a button 111 for binding other devices. In the embodiment of the present application, binding refers to establishing a trusted relationship between two devices, so that operations such as data synchronization between devices can be performed. In response to the user's operation (e.g., a click operation) on the button 111 for binding other devices, the device binding interface 120 shown in FIG. 3( d) is entered. The device binding interface 120 includes a list of scanned addable devices, and the user can select the device to be bound in the list of addable devices. For example, the room TV 121, tablet 122 and smart watch 123 shown in FIG. 3( d) , wherein when the mobile phone 101 wants to establish a binding relationship with the room TV 121 or tablet 122 or smart watch 123, it can directly click the binding button 121A corresponding to the room TV 121 or the binding button 122A corresponding to the tablet 122 or the binding button 123A corresponding to the smart watch 123 to achieve the binding of the room TV 121 or the tablet 122 or the smart watch 123.

[0152] Optionally, the device binding interface 120 further includes a tap-to-add button 124 and a scan-to-add button 125, which can be used to bind with electronic devices that are not scanned by the mobile phone 101. Exemplarily, in response to a user operation on the tap-to-add button 124, the mobile phone 101 turns on NFC and taps the back of the mobile phone 101 against the ontag label on other devices to implement binding with other devices; in response to a user operation on the scan-to-add button 125, the mobile phone 101 scans the QR code of other devices to implement binding with other devices.

[0153] It should be understood that the positions, names and shapes of the elements (e.g., buttons, icons, text, etc.) in the UI interfaces corresponding to FIG. 3(c) and FIG. 3(d) are not fixed and can be freely combined or designed according to requirements. For example, the button 111 in FIG. 3(c) can be replaced by the buttons 124 and 125 in FIG. 3(d).

[0154] It should be pointed out that the mutual communication between devices to implement the solution of the embodiment of the present application can be based on the same network; it can also be based on the existence of a trust relationship between devices, such as a common account, an associated account, a binding relationship, etc.; it can also be based on the same network and the establishment of a trust relationship, and the present application does not impose any restrictions on this.

[0155] For example, the first terminal, the second terminal and the third terminal can be networked to form a local area network device group, and multiple devices in the local area network device group are trusted devices. In this case, the local area network device composed of the first terminal, the second terminal and the third terminal can be called a "super terminal".

[0156] For another example, the first terminal, the second terminal, and the third terminal are logged into the same account respectively.

[0157] For another example, although the first terminal, the second terminal, and the third terminal are logged into different accounts respectively, these three accounts are mutually trusted associated accounts or family accounts.

[0158] For another example, at least one of the first terminal, the second terminal, and the third terminal has an account logged in, and at least one of the devices does not have an account, and a device-level authentication relationship can also be established between the device with an account and the device without an account. This application does not limit the specific form of establishing a trusted relationship between the first terminal, the second terminal, and the third terminal.

[0159] The recent task interface of the first terminal not only displays the applications recently used by the first terminal, but also displays the applications recently used by the second terminal and the third terminal. When displaying the historical task cards of other devices on the recent task interface of the first terminal, the logos of the first terminal and multiple terminals connected to the first terminal (including the second terminal and the third terminal) can be displayed separately in the recent task interface of the first terminal. When the logo of the first terminal or a terminal connected to the first terminal is selected, the recent task list corresponding to the terminal will be displayed accordingly in the recent task interface.

[0160] In the present application, when the most recently used applications of other terminals are displayed on the recent task interface of the first terminal (or it can also be called displaying the recent task snapshots of other terminals, displaying the recent task cards or historical task cards of other terminals, etc.), the task cards of other terminals can be arranged on the recent task interface of the first terminal according to the commonly used usage status of other terminals. For example, the commonly used usage status of other terminals includes: horizontal screen use, vertical screen use, vertical screen use of the unfolded state of the folding screen, horizontal screen use of the unfolded state of the folding screen, horizontal screen use of the folded state of the folding screen, vertical screen use of the folded state of the folding screen, etc. Alternatively, the task cards of other terminals can also be arranged on the recent task interface of the first terminal according to the usage status of a single user of other terminals. Alternatively, the task cards of other terminals can also be arranged on the recent task interface of the first terminal according to the screen situation (such as size, etc.) and usage (such as horizontal or vertical screen use, etc.) of the first terminal. Alternatively, the task cards of other terminals can also be arranged on the recent task interface of the first terminal according to the settings of the user on the first terminal, etc. This application is not limited here.

[0161] Exemplarily, as a possible implementation, the display layout of the historical task cards of device A on the recent task interface of another device may be determined according to the process shown in FIG. 4( a ) and FIG. 4( b ).

[0162] As shown in FIG4(a), if device A is a foldable screen device (such as a foldable screen mobile phone), based on whether the commonly used state of device A in the previous period of time is the unfolded state: if yes, further determine whether the commonly used state in the period of time is the unfolded state vertical screen use, if yes, then display (or also can be called layout) the historical task cards of device A on the recent task interface of another device according to the unfolded vertical screen mode of device A. If the commonly used state is the unfolded horizontal screen use, then display the historical task cards of device A on the recent task interface of another device according to the unfolded horizontal screen mode of device A.

[0163] If the commonly used state is folded, it is further determined whether the commonly used state is folded vertically during a period of time. If so, the historical task cards of device A are displayed on the recent task interface of another device in the same manner as device A is folded vertically. If the commonly used state is folded horizontally, the historical task cards of device A are displayed on the recent task interface of another device in the same manner as device A is folded horizontally.

[0164] As shown in FIG4(b), if device A is a non-folding screen device (such as a non-folding screen mobile phone or tablet computer, etc.), it is determined whether the common usage state of device A in the previous period of time is the vertical screen mode; if so, the historical task cards of device A are displayed on the recent task interface of another device in the vertical screen mode of device A. If the common usage state is the horizontal screen mode, the historical task cards of device A are displayed on the recent task interface of another device in the horizontal screen mode of device A.

[0165] Optionally, in an embodiment of the present application, when the task cards of the first terminal and other devices are displayed on the first terminal, the user can also select the layout of the task cards. After the user selects the layout, the first terminal can display the task cards of the first terminal and other devices on the first terminal according to the layout selected by the user. For example, the layout forms that the user can select include: horizontal list mode (List), grid mode (Grid), stack mode (Stack), vertical list mode (Vertical list), slim list mode (Slim list), etc. This application does not limit this.

[0166] The following describes each of these with reference to different examples.

[0167] Example 1: Assume that the first terminal is a tablet computer, the second terminal is another tablet computer, the third terminal is a non-folding screen mobile phone, and the fourth terminal is a folding screen mobile phone.

[0168] FIG5(a) shows a schematic diagram of the historical task card of the second terminal displayed on the recent task interface of the first terminal (local machine). As shown in FIG5(a), the layout of the historical task card of the second terminal displayed on the recent task interface of the first terminal is displayed according to the multi-task layout when the tablet computer is used in landscape mode. In FIG5(a), the icons of the first terminal and the multiple terminals connected to the first terminal are respectively displayed in the recent task interface of the first terminal. When the icon of the first terminal or a terminal connected to the first terminal is selected, the historical task card corresponding to the terminal will be displayed in the recent task interface accordingly. As shown in FIG5(a), when the first terminal receives the user's instruction so that the icon of the second terminal (MatePad) is selected, the historical task card of the second terminal is displayed in the recent task interface of the first terminal. When the historical task card of the second terminal (MatePad) is displayed on the recent task interface of the first terminal (local machine), the historical task card of the second terminal is displayed in a single row according to the horizontal screen use of the second terminal (MatePad).

[0169] Optionally, if the screen of the first terminal (the local device) is relatively high, the historical task cards of the second terminal (MatePad) can also be displayed in multiple rows when the second terminal (MatePad) is used in landscape mode. As shown in FIG5(b), when the recent task interface of the first terminal (the local device) displays the historical task cards of the second terminal (MatePad), the historical task cards of the second terminal (MatePad) are displayed in double rows when the second terminal (MatePad) is used in landscape mode.

[0170] FIG5(c) is a schematic diagram of a historical task card of a third terminal (P40) displayed on a recent task interface of a first terminal (this terminal). As shown in FIG5(c), when the historical task card of the third terminal (P40) is displayed on the first terminal (this terminal), the historical task card of the third terminal (P40) is displayed when the third terminal (P40) is used in portrait mode.

[0171] Figure 5(d) is a schematic diagram of the historical task card of the fourth terminal (Mate X2) displayed on the recent task interface of the first terminal (local device). Since the fourth terminal (Mate X2) is a folding screen device. Therefore, as a possible implementation method, as shown in Figure 5(d), when the historical task card of the fourth terminal (Mate X2) is displayed on the first terminal (local device), the historical task cards of the fourth terminal are displayed in a single row when the folding screen of the fourth terminal (Mate X2) is unfolded and used vertically. Optionally, as another possible implementation method: if the screen of the first terminal (local device) is relatively high, the historical task cards of the fourth terminal can also be displayed in multiple rows when the folding screen of the fourth terminal (Mate X2) is unfolded and used vertically.

[0172] Example 2: Assume that the first terminal is a non-folding screen mobile phone, the second terminal is a tablet computer, and the third terminal is a folding screen mobile phone.

[0173] FIG6(a) shows a schematic diagram of a historical task card of a second terminal (MatePad) displayed on the recent task interface of the first terminal (local device). As shown in FIG6(a), when the historical task card of the second terminal (MatePad) is displayed on the first terminal (local device), the historical task card of the second terminal is displayed in double rows when the second terminal (MatePad) is used in landscape mode. Optionally, when the historical task card of the second terminal (MatePad) is displayed on the first terminal (local device), the historical task card of the second terminal can also be displayed in a single row when the second terminal (MatePad) is used in landscape mode.

[0174] Figure 6(b) is a schematic diagram of the historical task card of the third terminal (Mate X2) displayed on the recent task interface of the first terminal. Since the third terminal (Mate X2) is a folding screen device. Therefore, as a possible implementation method, as shown in Figure 6(b), when the historical task card of the third terminal (Mate X2) is displayed on the first terminal (local device), the historical task card of the third terminal (Mate X2) is displayed in a single row when the third terminal (Mate X2) is used in vertical screen in the expanded state. Optionally, if the screen of the first terminal (local device) is relatively high, the historical task cards of the third terminal can also be displayed in multiple rows when the third terminal (Mate X2) is used in vertical screen in the expanded state.

[0175] Example 3: Assume that the first terminal is a non-folding screen mobile phone, the second terminal is a tablet computer, the third terminal is a folding screen mobile phone, and the first terminal is in landscape display state.

[0176] Fig. 6(c) is a schematic diagram of a historical task card of a first terminal (e.g., P40) displayed on a recent task interface of the first terminal (the local device). As shown in Fig. 6(c), since the first terminal is displayed in landscape mode, the historical task card of the first terminal (the local device) is displayed when the first terminal (the local device) is used in landscape mode.

[0177] Figure 6(d) shows a schematic diagram of the historical task card of the second terminal (MatePad) displayed on the recent task interface of the first terminal (local device). As shown in Figure 6(d), since the first terminal is displayed in landscape mode, the historical task card of the second terminal (MatePad) is displayed when the first terminal (local device) is used in landscape mode.

[0178] Figure 6(e) shows a schematic diagram of the historical task card of the third terminal (Mate X2) displayed on the recent task interface of the first terminal (local device). As shown in Figure 6(e), since the first terminal is displayed in landscape mode, the historical task card of the third terminal (Mate X2) is displayed when the first terminal (local device) is used in landscape mode, and the historical task card of the third terminal (Mate X2) is displayed in a single row when the folding screen is unfolded and used in portrait mode. Optionally, the historical task card of the third terminal (Mate X2) can also be displayed in portrait mode in the folded state of the folding screen; or, in landscape mode in the folded state of the folding screen; or, in landscape mode in the unfolded state, etc. This application is not limited here.

[0179] It should be understood that the above examples are merely illustrative and should not impose any restrictions on the layout of the historical task cards of other devices displayed in the recent task interface of the present device. In another embodiment of the present application, a layout different from the above examples can also be used for display, and the present application does not limit this.

[0180] In the embodiment of the present application, when the historical task cards of other devices are displayed on the recent task interface of the first terminal (the local device or the local end device), the last one or more historical task cards of other devices can display: the desktop snapshot of the device (or also called the foreground desktop snapshot); or display the desktop snapshot of the device and the floating ball; or display the desktop snapshot of the device and the floating window; or display the desktop snapshot of the device, and the desktop snapshot displays the task card; or display the remote control for controlling the device, or display the tasks that the device is running (OnGoing), etc. The following is explained with specific examples.

[0181] Example 4: Assuming that the first terminal (local device) is a tablet computer, FIG. 7(a) shows a schematic diagram of viewing the historical task cards of a non-folding screen mobile phone (P40) on the recent task interface of the first terminal. As shown in FIG. 7(a), the last task card in the historical task cards of the mobile phone P40 displays a desktop snapshot of the P40 mobile phone, and there may also be an interface capability (feature ability, FA) card on the desktop snapshot. The FA card may be a card corresponding to an application or a task. The user may click on the "FA card" on the desktop snapshot of the P40 mobile phone. After clicking on the FA card, as a possible implementation method, the application or task corresponding to the FA card will be displayed on the screen of the first terminal, that is, the application or task corresponding to the FA card will be opened on the first terminal. Alternatively, as another possible implementation method, after clicking on the FA card, the desktop of the mobile phone P40 will be displayed on the screen of the first terminal, and the FA card will be displayed on the desktop of the mobile phone P40. The user may click on the FA card, and the application or task corresponding to the FA card will be displayed on the screen of the first terminal.

[0182] Example 5: Assuming that the first terminal (local machine) is a tablet computer, FIG7(b) shows a schematic diagram of viewing the historical task cards of a non-folding screen mobile phone (mobile phone P40) on the recent task interface of the first terminal. As shown in FIG7(b), the last few task cards in the historical task cards of the mobile phone P40 are displayed as snapshots of the first screen of the desktop of the mobile phone P40. When the user makes a left sliding gesture on the snapshot of the first screen of the desktop of the mobile phone P40, the last task card of the recent task interface of the first terminal is switched to a snapshot of the second screen of the desktop of the mobile phone P40, as shown in FIG7(c). Optionally, the user can click on the snapshot of the first screen of the desktop of the P40 mobile phone or the snapshot of the second screen of the desktop, and the snapshot of the first screen of the desktop of the mobile phone P40 or the interface of the second screen of the desktop will be displayed on the first terminal. The user can click on the application icon on the desktop snapshot on the snapshot of the first screen of the desktop of the mobile phone P40 or the snapshot of the second screen to open the application on the local machine. Or, as another possible implementation, as shown in FIG7(c). The user can click on the snapshot of the first screen of the mobile phone P40 desktop or the blank area of ​​the second screen snapshot (the area on the desktop snapshot except the application icon). After clicking, the first screen interface or the second screen desktop of the mobile phone P40 desktop will be displayed on the screen of the first terminal. The user can click on the application icon on the desktop of the mobile phone P40 to open the application on the local machine.

[0183] Example 6: Assuming that the first terminal (the local device) is a tablet computer, FIG. 7(d) shows a schematic diagram of viewing the historical task cards of a non-folding screen mobile phone (e.g., P40) on the recent task interface of the first terminal. As shown in FIG. 7(d), the last task card in the historical task cards of the mobile phone P40 is displayed as a desktop snapshot of the mobile phone P40, and a floating window of a certain task or application is displayed on the desktop snapshot of the mobile phone P40. Optionally, the user can click on the floating window on the desktop snapshot of the mobile phone P40. After clicking on the floating window, as a possible implementation method, the application or task corresponding to the floating window will be displayed on the first terminal, that is, the application or task corresponding to the floating window will be opened on the first terminal. Alternatively, as another possible implementation method, after clicking on the floating window, the interface of the desktop of P40 will be displayed on the first terminal. Optionally, the floating window exists on the interface of the desktop of P40. After the user clicks on the floating window on the desktop of P40, the application or task corresponding to the floating window will be opened on the first terminal.

[0184] Example 7: Assuming that the first terminal (the local device) is a tablet computer, FIG. 7(e) shows a schematic diagram of viewing the historical task cards of a non-folding screen mobile phone (e.g., P40) on the recent task interface of the first terminal. As shown in FIG. 7(e), the last task card in the historical task cards of the P40 mobile phone displays a desktop snapshot of the P40 mobile phone, and a floating ball of a certain task or application is displayed on the desktop snapshot of the P40 mobile phone. Optionally, the user can click on the floating ball on the desktop snapshot of the P40 mobile phone. After clicking on the floating ball, as a possible implementation method, the application or task corresponding to the floating ball will be displayed on the first terminal (e.g., full screen or in the form of a floating window), that is, the application or task corresponding to the floating ball will be opened on the first terminal; or, as another possible implementation method, after the user clicks on the floating ball, the desktop of P40 will be displayed on the first terminal. Optionally, the floating ball exists on the interface of the desktop of P40. After the user clicks on the floating ball on the desktop of P40, the application or task corresponding to the floating ball will be opened on the first terminal.

[0185] Example 8: Assuming that the first terminal (this machine) is a tablet computer, FIG7(f) shows a schematic diagram of viewing the historical task cards of the large-screen device (HUAWEI TV) on the recent task interface of the first terminal, as shown in FIG7(f), wherein the last task card in the historical task cards of the large-screen device displays a snapshot of the remote control of the large-screen device. Optionally, as shown in FIG7(f), the user can click on a blank area on the snapshot of the remote control of the large-screen device (the area on the snapshot of the remote control except for the control buttons), and after clicking, the details of the remote control of the large-screen device will be displayed on the first terminal, and the user can directly control the large-screen device using the remote control of the large-screen device on the first terminal. Alternatively, the user can directly click on the control button on the snapshot of the remote control of the large-screen device to control the large-screen device.

[0186] Example 9: Assuming that the first terminal (the local device) is a mobile phone, FIG7(g) shows a schematic diagram of viewing the historical task cards of other multiple devices in the recent task interface of the first terminal. Among them, the device icon (icon) of one of the multiple devices (for example, the last one) is a device icon of the light device type. Light devices are a general term for devices such as Internet of Things (IOT) devices, wearable devices, and smart home devices. For example, light devices may include: smart refrigerators, smart air conditioners, smart cooking pots, smart range hoods, smart speakers, smart watches, etc. After the user clicks the "light device" icon in FIG7(g), as shown in FIG7(h), the task cards corresponding to the tasks of these light devices (kitchen devices) that are running (OnGoing) can be displayed on one or more task cards in the recent task interface of the first terminal. In FIG7(h), when the user makes a left sliding gesture on the task card of the light device, as shown in FIG7(i), the task cards of the recent task interface of the first terminal display the task cards of other light devices (for example, portable devices).

[0187] exist Figure 7(g) to Figure 7(i) In the example shown, all light devices are integrated together, and all light devices are displayed using a light device icon at the top of the screen. Optionally, in some other embodiments of the present application, each light device may also correspond to its own device icon, which is displayed at the top of the screen, that is, one light device corresponds to one device icon. Alternatively, light devices may be classified, with one type of light device corresponding to one icon, for example: multiple light devices for the kitchen correspond to one device icon, multiple light devices for the living room correspond to one device icon, etc. Alternatively, the user may set it up so that one or several light devices correspond to one device icon, etc., and the present application does not limit this.

[0188] In the interface shown in FIG7(h) and FIG7(i), as a possible implementation method, the user can click on a blank area (i.e., the area on any card except the control button) on any card of any light device shown in FIG7(i) and FIG7(i). For example, as shown in FIG7(j), if the user clicks on a blank area on the smart cooking pot task card, the interface displayed on the first terminal is as shown in FIG7(k). After clicking, the details of the task being run by the smart cooking pot can be displayed on the interface of the first terminal, and the user can remotely control the task on the details interface.

[0189] For another example, as shown in FIG7(l), when a user clicks on a blank area on a task card of a Huawei watch (HUAWEI WATCH GT2), an interface displayed on the first terminal is as shown in FIG7(m). After clicking, details of the task being run by the music player can be viewed on the interface of the first terminal, and the user can remotely control the task on this details interface.

[0190] Optionally, in the interface shown in Figure 7(h) and Figure 7(i), as another possible implementation method, the user can also click on the blank area on any card of any light device shown in Figure 7(i) and Figure 7(j), and after clicking, the details of the smart cooking pot (i.e., the light device) can be viewed on the interface of the first terminal.

[0191] Optionally, in the interfaces shown in FIG. 7(h) and FIG. 7(i), as another possible implementation method, the user can also directly click on the control button on any light device card, that is, the user directly clicks the corresponding control button on the light device card, which can also realize remote task control. For example, as shown in FIG. 7(n), if the user clicks the "Close" button on the task card of the smart cooking pot, the smart cooking pot stops running.

[0192] Optionally, when displaying task cards of other light devices on the recent task interface of the first terminal, if there are relatively few corresponding operations on the light device, a standard device card can be used to display the light device task card. For example, the portable cards corresponding to the smart cooking pot, smart range hood, Huawei watch (HUAWEI WATCH GT2), and smart washing machine shown in Figure 7(h) and Figure 7(i) are all standard device cards.

[0193] Optionally, as another possible implementation, when the task cards of other light devices are displayed in the recent task interface of the first terminal, if there are more corresponding operations on a certain light device, more functions can be displayed on the task card of the light device. For example, assuming that the light device is a smart cooking pot, it can quickly switch to: stewing, stir-frying, adjusting the firepower, or visually seeing the condition of the food in the cooking pot, then the task card corresponding to the light device can be displayed using an immersive task card. For example, as shown in Figure 7 (o), the task cards corresponding to the smart cooking pot and the smart range hood in the recent task interface of the first terminal are immersive task cards.

[0194] Optionally, when the task cards of other light devices are displayed on the recent task interface of the first terminal, the user can also drag the task card of a light device to the icon of other smart devices (such as MatePad, Mate X2) in the recent task interface of the first terminal, and the task card of the light device will be displayed in the recent task interface of the other smart device, or on the desktop of the other smart device. Optionally, after the smart device receives the information of the task card of the light device, the smart device can also add the task card of the light device to the recent task center of the smart device, or add it to the desktop.

[0195] Example 10: Assuming that the first terminal (the local device) is a mobile phone, when the recent task interface of the first terminal displays historical task cards of multiple devices, the last one or more task cards can display a desktop application icon of a certain device. For example, FIG7(p) shows a schematic diagram of displaying historical task cards of mobile phone P40 on the recent task interface of the first terminal, and the last one displays the desktop application icon (icon) of mobile phone P40.

[0196] In the example shown in FIG7(p), as a possible implementation, the user can click on the blank area of ​​the task card, as shown in FIG7(q), so as to display the desktop application of the mobile phone P40 on the first terminal. The user can drag the application icon on the interface shown in FIG7(q) to help the mobile phone P40 manage applications (such as sorting applications, creating folders, deleting applications, etc.).

[0197] In the example shown in Figure 7(p), as another possible implementation method, the user can also perform operations directly on the task card of the mobile phone P40 desktop application, for example, dragging the application icon in the task card of the mobile phone P40 desktop application to help the mobile phone P40 manage the application without first displaying the desktop application of the mobile phone P40 on the first device.

[0198] In an embodiment of the present application, in addition to displaying task cards of other light devices on the recent task interface of the terminal device used by the user, task cards of other smart devices (including other light devices and smart terminals used by the user, such as mobile phones, tablets, etc.) that can have the same account or associated accounts are also viewed on the light device, and the task cards can also be operated on the light device to achieve remote control of other smart terminal devices on the light device.

[0199] For example, on a certain light device, when a user views the task cards of other smart terminals with the same account or associated accounts, the user's identity authentication can be assisted by the sensors, cameras, microphones, etc. of the light device itself, or the sensors, cameras, microphones, etc. of the light device itself and other surrounding devices (such as smart watches carried by users, large-screen devices at home, etc.). After the user's identity authentication is passed, the task cards of other devices displayed on the light device can be viewed, and the task cards can be operated to remotely control other smart terminal devices and other light devices on the light device. This will be explained with specific examples below.

[0200] Example 11: As shown in FIG7(r), assuming that the light device used by the user is a smart range hood, the user clicks the "light device" button on the screen of the smart range hood, and then the task cards of other light devices with the same account or associated account as the range hood that are running (OnGoing) can be displayed on the screen of the smart range hood. As shown in FIG7(r), after the user clicks the "light device" button, the light device task cards displayed include task cards for a smart cooking pot and a smart washing machine. When the task cards of other light devices are displayed on the screen of the smart range hood, they can be displayed according to the screen adaptation of the smart range hood (that is, the task cards are based on the screen responsive layout). When the user slides the task card to the left or right, more task cards of light devices of other accounts or associated accounts can be viewed. In addition, the user can click on the blank area on one of the task cards (the area on the task card except the control button), and the detailed content of the task card will be displayed on the display screen in full screen or according to the screen adaptation, and the user can remotely control the task on the details interface. Alternatively, the user may also directly click on a control button on any light device task card, that is, the user directly clicks on the corresponding control button on the card of the light device, which may also realize remote task control.

[0201] Example 12: As shown in FIG7(s), assuming that the light device used by the user is a smart range hood, the user clicks the "light device" button on the screen of the smart range hood. At this time, the smart range hood can call on its own and other surrounding devices (such as the smart watch carried by the user, the large-screen device at home, etc.) sensors, cameras, microphones, etc. to assist in user identity authentication. After the user's identity authentication is passed, the OnGoing task cards of other light devices with the same account or associated account as the range hood are displayed on the screen of the smart range hood, where one light device can correspond to one OnGoing task card. The user slides the OnGoing task card to the left, and the last few task cards are icons of smart terminals with the same account or associated account as the range hood. As shown in FIG7(s) for terminal 1 and terminal 2, the user selects the icon of the smart terminal to be viewed, assuming it is terminal 1. The user clicks the "terminal 1" icon, and multiple task cards of terminal 1 are displayed on the screen of the smart range hood. Among them, the multiple task cards of terminal 1 include: historical task cards and foreground task cards of terminal 1, and the foreground task card is: the task card corresponding to the application currently displayed on the screen of terminal 1. For example, if a video is playing on the screen of terminal 1, the task card corresponding to the video application is the foreground task card. It should be understood that the task card corresponding to the floating window displayed on the screen of terminal 1 is also the foreground task card of terminal 1, and the historical task card includes the task card corresponding to the application running in the background of terminal 1.

[0202] Moreover, the user can click on a blank area on a task card, and the detailed content of the task card will be displayed on the display screen of the smart range hood in full screen or according to the screen adaptation, and the user can remotely control the task on the detailed interface. Alternatively, the user can also directly click on the control button on the card of any device, that is, the user directly clicks the corresponding control button on the task card of the device, which can also realize remote task control.

[0203] When the recent task interface of the first terminal (local device) displays the historical task card of another device (remote device), the user can click the task card on the first terminal to display (or run) the task or application corresponding to the task card on the first terminal. This process can be called pulling up the task card of the remote device on the first terminal.

[0204] In the present application, when pulling up the task card of the remote device on the recent task interface of the first terminal, the rule as shown in FIG. 8( a ) may be followed.

[0205] As shown in FIG8(a), if an application of a remote device is migrated to the recent task interface of the first terminal based on the copy mode, that is, a task card on the recent task interface of the first terminal is obtained from an application of the remote device through the copy mode, after the task card is pulled up on the first terminal, the first terminal and the remote device can simultaneously display (or can also be called running) the application. In addition, the status of the application displayed by the first terminal and the remote device is synchronized (for example, both display the same page of the same PPT file), and the data of the application on the first terminal and the remote device are synchronized. When the first terminal and the remote device display the application, they can adapt the display according to the characteristics of their respective screens. In this application, the adaptive display can also be understood that in the process of display, different devices can adjust the size and layout of the application displayed on the screen according to the size of their respective screens, that is, the layout and size of the application displayed on the screen are adjustable (Resizable), for example, one is full-screen display and the other is non-full-screen display; or, one is horizontal screen display and the other is vertical screen display, etc. Clicking the task card of the application on the recent task interface of the remote device, or clicking the application icon on the desktop of the remote device, will not pull the application back. "Pulling back the application" can be understood as: operating on the source device of the application (the remote device in this example) so that the application is migrated back to the source device, and the application will not be displayed on the recent task interface or desktop of other devices, or will not run on other devices.

[0206] If an application of the remote device is not migrated to the recent task interface of the first terminal based on the copy mode, further determine whether the application is displayed on the recent task interface of the first terminal in the migration mode based on the window projection technology. The migration mode based on the window projection technology does not require the first terminal to install the application. If so, continue to determine whether the application supports multiple instances.

[0207] In the case where the application supports multiple instances, the application can be displayed (or can also be called running) on ​​the first terminal and the source device (remote device) at the same time. The data of the application on the first terminal and the remote device are synchronized. When the first terminal and the remote device display the application, the display can be adapted according to the characteristics of their respective screens. However, the status of the application displayed on the first terminal and the remote device may be asynchronous (for example, one device displays the first page of a PPT file, and the other displays the second page of the PPT file). Clicking the task card of the application on the recent tasks interface of the remote device, or clicking the application icon on the desktop of the remote device, will not pull the application back.

[0208] If the application does not support multiple instances, the application cannot be displayed on the first terminal and the remote device at the same time. If the application is the foreground task or foreground application of the remote device (a task or application that is displayed and running on the remote device interface), after the application is migrated to the first terminal, the remote device automatically exits the task and the remote device desktop is displayed on the remote device screen. Clicking the task card of the application on the recent task interface of the remote device, or clicking the application icon on the desktop of the remote device, will pull back the application.

[0209] If an application of the remote device is not displayed on the recent task interface of the first terminal in a migration mode based on the window projection technology, but is displayed on the recent task interface of the first terminal in a migration mode based on the FA technology, the first terminal needs to first install the application or the FA of the application. Only after the installation is complete can the task card of the application be displayed on the recent task interface of the first terminal. After the first terminal installs the application or the FA of the application, the data of the application on the first terminal and the remote device are synchronized. When the first terminal and the remote device display the application, they can adapt the display according to the characteristics of their respective screens. However, the status of the application displayed on the first terminal and the remote device may be out of sync. Clicking the task card of the application on the recent task interface of the remote device, or clicking the application icon on the desktop of the remote device, will not pull back the application.

[0210] The following will be explained with reference to specific examples. Figure 8(b) to Figure 8(n) The example in the figure can be a part of the flowchart shown in 8(a) or an independent solution, and the present application is not limited to this.

[0211] Example 13: Assuming that the first terminal (local device) is a tablet computer, FIG8(b) shows a schematic diagram of viewing the historical task cards of multiple other devices on the recent task interface of the first terminal. As shown in FIG8(b), it is assumed that the magazine lock screen application of the remote device (i.e., the task source device) is displayed on the recent task interface of the first terminal based on the copy mode, that is, the task card of the magazine lock screen application on the recent task interface of the first terminal is obtained from the P40 device through the copy mode. The user clicks on the task card of the magazine lock screen application on the recent task interface of the first terminal, that is, after pulling up the task card on the first terminal, as shown in FIG8(c), the first terminal and P40 can display the magazine lock screen application at the same time. In addition, the status of the application displayed by the first terminal and the remote device is synchronized, and the first terminal and the P40 device both display the picture 3 of the magazine lock screen application. The data of the application on the first terminal and the P40 device are synchronized. For example, if the user edits the picture 3 on the first terminal, the editing status is automatically synchronized to the P40 device. When the first terminal and the P40 device display the magazine lock screen application, the display can be adapted according to the characteristics of their respective screens (for example, the P40 is displayed in portrait mode, the first terminal is displayed in landscape mode, etc.).

[0212] Example 14: Assuming that the first terminal (local device) is a tablet computer, FIG8(d) shows a schematic diagram of viewing the historical task cards of multiple other devices on the recent task interface of the first terminal. As shown in FIG8(d), it is assumed that: the magazine lock screen application of the remote device: is displayed on the recent task interface of the first terminal in a migration mode based on the window projection technology, and the magazine lock screen application supports multiple instances; or, is displayed on the recent task interface of the first terminal in a migration mode based on the FA technology. In both cases, the data of the application on the first terminal and the P40 device are synchronized. The user clicks on the task card of the magazine lock screen application on the recent task interface of the first terminal. Assuming that the user clicks on the picture 2 in the task card of the magazine lock screen application, that is, after pulling up the task card on the first terminal, as shown in FIG8(e), the first terminal displays the picture 2 of the magazine lock screen application, while the P40 device still displays the picture 3 of the magazine lock screen application, that is, the states of the magazine lock screen application displayed by the first terminal and the P40 are not synchronized, and the states of the magazine lock screen application displayed by the two devices do not affect each other. Furthermore, when the first terminal and the P40 device display the magazine lock screen application, they can adapt the display according to the characteristics of their respective screens (for example, the P40 is displayed in portrait mode, the first terminal is displayed in landscape mode, etc.).

[0213] In this application, if the application of the P40 device is displayed on the recent task interface of the first terminal in a migration mode based on FA technology, after the user pulls up the application card on the first terminal, the prompt information of the source device of the application may not be displayed on the first terminal. For example, the prompt "from P40" may not be displayed on the first terminal.

[0214] Example 15: Assuming that the first terminal (local device) is a tablet computer, FIG8(f) shows the interface displayed on the first terminal after the remote device (P40) "Huawei Video" APP is pulled up on the first terminal. The first terminal is playing a video of the P40 device "Huawei Video" APP. Assumption: The Huawei Video application of the P40 device: is displayed on the recent task interface of the first terminal in a migration mode based on the window projection technology, and the Huawei Video application does not support multiple instances. If the user pulls back the application on the P40 device, the user can click the "Huawei Video" icon on the desktop of the P40 device, or select the "Huawei Video" task card of the P40 device in the recent task interface on the P40 device, and click the task card to pull back the Huawei Video application. As shown in Figure 8(f), the user clicks on the "Huawei Video" icon on the desktop of the P40 device. After the user pulls back the Huawei Video application, as shown in Figure 8(g), the first terminal will no longer play the video of the "Huawei Video" APP, and will be displayed as the desktop of the first terminal, while the P40 device will continue to play the video in the same state as the video previously played on the first terminal (for example, before pulling back the "Huawei Video" APP, the first terminal plays a certain video to time t. After pulling back, the P40 device will continue to play the video after time t).

[0215] Example 16: Assuming that the first terminal (local device) is a tablet computer, FIG8(h) shows the interface displayed on the first terminal after the remote device (P40) "Huawei Video" APP is pulled up on the first terminal. The video of the P40 device "Huawei Video" APP is being played on the first terminal. Assume that: the Huawei Video application of the P40 device is displayed on the recent task interface of the first terminal based on the copy mode; or, it is displayed on the recent task interface of the first terminal in the migration mode based on the window projection technology, and the Huawei Video application supports multiple instances; or, it is displayed on the recent task interface of the first terminal in the migration mode based on the FA technology. Then, when the user clicks the "Huawei Video" icon on the desktop of the P40 device, or the user selects the "Huawei Video" task card of the P40 device in the recent task interface on the P40 device, and clicks the task card, the Huawei Video application will not be pulled back. As shown in Figure 8(h), the user clicks the "Huawei Video" icon on the desktop of the P40 device. After the user clicks the "Huawei Video" icon, as shown in Figure 8(i), the "Huawei Video" APP enters a new video selection interface, and the user clicks another video to play it, that is, the user has started a new task on the P40 device, and this new task will not affect the video being played on the P40 device "Huawei Video" APP on the first terminal. As shown in Figure 8(i), the new task run by the user on the P40 device and the video of the "Huawei Video" APP migrated from the P40 device to the first terminal do not affect each other.

[0216] In an embodiment of the present application, if the local device is a small-screen device and the remote device is a large-screen device, after pulling up the task card of the remote device on the local device, the application corresponding to the task card will be displayed on the screen of the local device. During the process of displaying the application on the local device, the application can be displayed on the display screen of the local device according to one of the following rules;

[0217] Rule 1: On the local device, the application is displayed according to the screen size of the local device.

[0218] Optionally, in an embodiment of the present application, if the local device is a wide-screen device and the remote device is a narrow-screen device, after pulling up the task card of the remote device on the local device, the application corresponding to the task card can be displayed on the display screen of the local device according to the following rule 2.

[0219] Rule 2: On the local device, the application is automatically displayed using parallel view.

[0220] Optionally, in an embodiment of the present application, if the local device is a narrow-screen device and the remote device is a wide-screen device, after pulling up the task card of the remote device on the local device, the application corresponding to the task card can be displayed on the display screen of the local device according to the following rule three.

[0221] Rule 3: Automatically close the normal view on the local device and use the screen size of the local device to adapt the display of the application.

[0222] Optionally, in an embodiment of the present application, if the local device is a narrow screen device and the remote device is a wide screen device, after pulling up the task card of the remote device on the local device, the application corresponding to the task card can be displayed on the display screen of the local device according to the following rule 4:

[0223] Rule 4: Display the application in full screen on the local device without switching between horizontal and vertical screens. That is, the application is displayed on the screen of the local device according to the display status of the application on the remote device.

[0224] The following will explain with reference to specific examples.

[0225] Example 17: Assume that the first terminal (local device) is a mobile phone (for example, P40) and the remote device is a tablet computer. After the task card of the magazine lock screen APP of the tablet computer is pulled up on the P40, the magazine lock screen interface corresponding to the task card will be displayed on the P40 screen, as shown in Figure 8(j). The magazine lock screen interface displayed on the tablet computer is displayed in full screen, and on the P40 device, the magazine lock screen interface will also be displayed in full screen.

[0226] As shown in FIG8(j), if a task card of the magazine lock screen APP of the P40 device is pulled up on the tablet computer, the magazine lock screen interface corresponding to the task card will be displayed in full screen on the tablet computer screen.

[0227] Example 18: Assume that the first terminal (local device) is a tablet computer and the remote device is a mobile phone (e.g., P40). The local device is a wide-screen device, while the remote device is a narrow-screen device. After pulling up the task card of the news browsing APP of P40 on the tablet computer, the news browsing interface corresponding to the task card will be displayed on the tablet computer screen, as shown in FIG8(k). The news browsing interface displayed on the tablet computer is automatically parallel horizon display, while the news browsing interface displayed on the P40 screen is automatically closed parallel horizon display, that is, the normal display state.

[0228] As shown in FIG8(k), if a task card of a news browsing APP of a tablet computer is pulled up on the P40, the news browsing interface corresponding to the task card will be displayed on the P40 screen. The news browsing interface displayed on the tablet computer is automatically displayed in parallel view, while the news browsing interface displayed on the P40 screen is automatically displayed in parallel view, which is a normal display state (such as full-screen adaptive display, etc.).

[0229] Example 19: Assume that the first terminal (local device) is a mobile phone (for example, P40) and the remote device is a tablet computer. After the task card of the video APP of the tablet computer is pulled up on the P40, the video corresponding to the task card will be displayed on the P40 screen, as shown in Figure 8 (l). Since the video displayed on the tablet computer is displayed in horizontal screen, the video will also be displayed in horizontal screen on the P40 device, that is, the horizontal and vertical screens will not be switched.

[0230] As shown in FIG8(l), if a task card of a video APP of a P40 device is pulled up on a tablet computer, the video corresponding to the task card will be displayed on the tablet computer screen. Since the video displayed on the P40 device is displayed in horizontal mode, the video will also be displayed in horizontal mode on the tablet computer, i.e., there will be no switching between horizontal and vertical modes.

[0231] Optionally, in the example of the present application, as another possible implementation method, if the local device is a large-screen device and the remote device is a small-screen device, after the local device pulls up the task card of the remote device, the application corresponding to the task card will be displayed on the screen of the local device. In the process of displaying the application, the application corresponding to the task card can also be displayed on the screen of the local device in the form of a floating window. Further, if the local device supports adaptive display, when the application corresponding to the task card is displayed on the screen of the local device in the form of a floating window, the application corresponding to the task card can be displayed in a horizontal or wide floating window; if the local device does not support adaptive display, the application corresponding to the task card can be displayed in a vertical or narrow floating window.

[0232] Optionally, in the example of the present application, as another possible implementation method; if the local device is a PC-type device, after pulling up the task card of an application on the remote device on the local device, the application can be displayed as a hanging window on the local device by default, such as shown in Example 20.

[0233] Example 20: As shown in Figure 8(m), the user clicks on the task card corresponding to APP2 of the P40 device in the recent task interface of the PC device, thereby pulling up the task card on the PC device. When the APP2 is displayed on the PC device, there are two different forms of floating window display, as shown in Figure 8(m), one is a vertical or narrow floating window display, and the other is a horizontal or wide floating window display.

[0234] Optionally, in the example of the present application, as another possible implementation method; if the local device is a PC-type device, after pulling up a task card of an application on the remote device on the local device, when the application is displayed on the local device, a selection interface can be set so that the user can choose to use full-screen display or floating window display. For example, as shown in Example 21.

[0235] Example 21: As shown in Figure 8(n), the user clicks on the task card corresponding to APP2 of the P40 device in the recent task interface of the PC device, thereby pulling up the task card on the PC device. When the APP2 is displayed on the PC device, there are two different floating window display forms, one full screen display and the other floating window display, as shown in Figure 8(n). The user can choose full screen display or floating window display according to his needs. After the user clicks on the corresponding option, the PC device will display the APP2 accordingly according to the user's selection result.

[0236] In the embodiment of the present application, in addition to displaying task cards of other devices and the local device on the recent task interface of the local device used by the user, the user can also operate the task card on the recent task interface to install the application corresponding to the task card on the local device or other devices. This will be explained below with reference to specific examples.

[0237] Example 22: Assuming that the local device (local device) used by the user is a mobile phone (for example, P40), as shown in FIG8 (o), it is a schematic diagram of other device task cards displayed on the recent task interface of P40. In the example shown in FIG8 (o), the user views the task card of tablet computer 1 (MatePad1) on the recent task interface of the local device. The user long presses the task card corresponding to APP2, and a prompt box may pop up: "Download to local device"; "Open in floating window"; "Open in split screen". If the user clicks "Download to local device", the local device P40 may automatically download and install the APP2. Optionally, after installing APP2, the local device automatically opens the APP2. If the user clicks "Open in floating window", the APP2 is opened on the screen of the local device P40 in a floating window manner (that is, after pulling up APP2 on the local device, it is displayed in a floating window manner). If the user clicks "Open in split screen", the APP2 is opened on the screen of the local device P40 in a split screen manner (that is, after pulling up APP2 on the local device, it is displayed in a split screen manner).

[0238] Example 23: Assume that the local device (local device) used by the user is tablet computer 1 (MatePad1). As shown in Figure 8(p), it is a schematic diagram of other device task cards displayed on the recent task interface of MatePad1. In the example shown in Figure 8(p), the user views the task card of P40 on the recent task interface of the local device. The user presses and holds the task card corresponding to APP2 and drags it to the icon position of the Mate X2 device to complete the migration of APP2 from the P40 device to the Mate X2 device. At the same time, a prompt box may pop up on the local device: "Download to Mate X2"; "Open in floating window"; "Open in split screen"; "Open in full screen". If the user clicks "Download to Mate X2", Mate X2 can automatically download and install APP2. Optionally, after installing APP2, MateX2 can automatically open APP2. If the user clicks "Open in floating window", APP2 is opened on the screen of the local device in the form of a floating window (that is, after pulling up APP2 on the local device, it is displayed in the form of a floating window). If the user clicks "Open in Split Screen", the APP2 is opened in split screen mode on the screen of the local device (i.e., after APP2 is pulled up on the local device, it is displayed in split screen mode). If the user clicks "Open in Full Screen", the APP2 is opened in full screen mode on the screen of the local device (i.e., after APP2 is pulled up on the local device, it is displayed in full screen mode).

[0239] In the embodiment of the present application, in the process of displaying task cards of other devices and the local device on the recent task interface of the local device used by the user, the user can also operate multiple task cards of the same device, or operate task cards of different devices, and simultaneously display the applications corresponding to the multiple task cards on the screen of the local device or the remote device in split screen; or display one task in full screen, and other tasks in floating windows or floating balls; or display multiple task cards in floating windows, etc. This will be explained below with reference to specific examples.

[0240] Example 24: Assuming that the local device (machine) used by the user is a mobile phone (for example, P40), as shown in Figure 8(q), it is a schematic diagram of other device task cards displayed on the recent task interface of P40. In the example shown in Figure 8(q), the user views the task card of the machine in the recent task interface of the machine. The user presses the task card corresponding to APP2 of the machine with his left hand, slides the task card to the left with his right hand, switches to the task card corresponding to other applications of the machine and selects it. Assuming that the user selects the task card corresponding to APP5 of the machine, the user presses the task card corresponding to APP5 of the machine with his right hand, drags the task card corresponding to APP5 until it overlaps with the task card corresponding to APP2, and then lets go, so that APP2 and APP5 can be displayed in split screen on the machine.

[0241] Optionally, as another possible implementation, when APP2 and APP5 are displayed on the local device, APP2 is displayed in full screen and APP5 is displayed in a floating window; or APP5 is displayed in full screen and APP2 is displayed in a floating window; or both APP2 and APP5 are displayed in floating windows. This application does not make any limitation here.

[0242] Example 25: Assuming that the local device (machine) used by the user is a mobile phone (for example, P40), as shown in Figure 8(r), it is a schematic diagram of the task cards of other devices displayed on the recent task interface of P40. In the example shown in Figure 8(r), the user views the task card of the machine in the recent task interface of the machine. The user presses the task card corresponding to the machine's APP2 with his left hand, clicks the device icon of MatePad1 with his right hand, switches to the task card of MatePad1, slides the task card of MatePad1 to the left or right with his right hand and makes a selection. Assuming that the user selects the task card corresponding to APP4 of MatePad1, the user presses the task card corresponding to APP4 of MatePad1 with his right hand, drags the task card corresponding to APP4 until it overlaps with the task card corresponding to APP2, and then lets go, so that the local APP2 and MatePad1's APP4 can be displayed in split screen on the machine.

[0243] Optionally, as another possible implementation, when APP2 and APP4 are displayed on the local device, APP2 is displayed in full screen and APP4 is displayed in a floating window; or APP4 is displayed in full screen and APP2 is displayed in a floating window; or both APP2 and APP4 are displayed in floating windows. This application does not make any limitation here.

[0244] Example 26: Assume that the local device (machine) used by the user is a mobile phone (for example, P40). As shown in Figure 8(s), it is a schematic diagram of the task cards of other devices displayed on the recent task interface of P40. In the example shown in Figure 8(s), the user views the task card of the machine on the recent task interface of the machine. The user presses the task card corresponding to APP2 of the machine with his left hand. Click the device icon of MatePad1 with the right hand to switch to the task card of MatePad1, and slide the task card of MatePad1 to the left or right with the right hand and make a selection. Assuming that the user selects the task card corresponding to APP4 of MatePad1, the user presses the task card corresponding to APP4 of MatePad1 with the right hand. At this time, the user can slide the task card corresponding to APP2 and the task card corresponding to APP4 to the icon of the target device (mobile phone P30) together and then let go. Then, APP2 and APP4 can be displayed on the screen of P30, that is, the APPs corresponding to different devices are migrated to the target device at the same time.

[0245] When APP2 and APP4 are displayed on the screen of P30, as shown in FIG8( t ), APP2 and APP4 can be displayed in split screen; or, APP2 is displayed in full screen and APP4 is displayed in a floating window; or, APP4 is displayed in full screen and APP2 is displayed in a floating window; both APP2 and APP4 are displayed in floating windows.

[0246] Optionally, in Example 26, after the user presses and holds the task card corresponding to APP2 of the local device with his left hand, he can slide the task card to the left with his right hand to switch to the task cards corresponding to other applications of the local device and make a selection. After the selection is completed, slide the task card corresponding to APP2 together with the task cards corresponding to other APPs of the local device toward the target device and then release the task card. This will enable the two different APP2s on the local device to be displayed on the target device.

[0247] Example 27: Assuming that the local device (machine) used by the user is a mobile phone (for example, P40), as shown in Figure 8(u), it is a schematic diagram of other device task cards displayed in the recent task interface of P40. In the example shown in Figure 8(u), the user presses the task card corresponding to APP2 of the machine with his left hand, clicks the device icon of MatePad1 with his right hand, switches to the task card of MatePad1, slides the task card of MatePad1 to the left or right and selects it. Assuming that the user selects the task card corresponding to APP4 of MatePad1, the user presses the task card corresponding to APP4 of MatePad1 with his right hand, drags the task card corresponding to APP4 to overlap with the task card corresponding to APP2, and then lets go. In this way, the task card corresponding to APP4 and the task card corresponding to APP2 will form a new task card (split-screen task card) displayed in the recent task interface of the machine. The task card consists of the task card corresponding to APP4 and the task card corresponding to APP2.

[0248] Optionally, in Example 27, after the user presses and holds the task card corresponding to APP2 of the local device with his left hand, he can also slide the task card to the left with his right hand to switch to the task cards corresponding to other applications of the local device and make a selection. After the selection is completed, drag the task card corresponding to other APPs of the local device until it overlaps with the task card corresponding to APP2 and then release it. The task cards corresponding to the two different APPs on the local device will form a new task card and be displayed in the recent task interface of the local device.

[0249] In the example of the present application, after the task (application) of the migration mode based on the window projection technology crosses the device, the distance between the local device (the device that displays the task card of the remote device) and the remote device (the source device of the task card) exceeds the threshold for a while, or the network quality between the local device and the remote device is less than the preset threshold, the communication connection between the local device and the remote device will be interrupted. In this case, a "capsule" prompt may appear on the local device to prompt the user that the local device and the remote device will be disconnected. In addition, the user can operate the "capsule" (such as swiping up or sliding down, etc.), and after operating the "capsule" prompt, the "capsule" prompt can be hidden; or, the "capsule" prompt can be automatically hidden after a preset display time length. After the "capsule" prompt is hidden for a preset time length, if the distance between the local device and the remote device still exceeds the threshold for a while, or the network quality between the local device and the remote device is still less than the preset threshold, the "capsule" prompt can reappear. Optionally, after the "capsule" prompt reappears, it can also be hidden or automatically hidden by the user's operation. In addition, there is a prompt of the source device (remote device) on the local device.

[0250] When the migration mode based on FA technology performs tasks across devices, if the distance between the local device and the remote device exceeds a threshold for a while, or the network quality between the local device and the remote device is less than a preset threshold, the communication connection between the local device and the remote device will be interrupted. In this case, the "capsule" prompt may not appear on the local device, that is, there is no "capsule" prompt on the local device. In addition, the application can be used independently at a distance on the local device, and optionally, there is no prompt of the source device (remote device) on the local device.

[0251] The following will explain with reference to specific examples.

[0252] Example 28: Assuming that the first terminal (local device) is a tablet computer, FIG8(v) shows an interface diagram displayed on the first terminal after the remote device (P40 device) is pulled up on the first terminal and applied on the first terminal. As shown in FIG8(v), it is assumed that the magazine lock screen application of the remote device (the task source device P40) is displayed on the recent task interface of the first terminal in a migration mode based on the window projection technology. In this case, if the distance between the local device and the remote device exceeds a threshold for a while, a "capsule" prompt may appear on the local device to prompt the user: "The distance from P40 is too far and the connection will be disconnected". Optionally, the user can operate the "capsule" (such as swiping up or sliding down, etc.), and after operating the "capsule" prompt, the "capsule" prompt can be hidden; or, the "capsule" prompt can be automatically hidden after a preset display time length. In addition, the prompt of the source device (P40) on the local device: "From P40".

[0253] In this application, when the distance between the local device and the remote device exceeds a threshold for a while, or the network quality between the local device and the remote device is less than a preset threshold, or the remote device exits the hyperterminal, or the remote device changes its login account, etc., in these cases, after the communication connection between the local device and the remote device is interrupted, the application of the remote device pulled up by the local device will be displayed on the local device, and a prompt message will be displayed to the user on the mask display to prompt the user: "Due to XXX reasons, the connection has been disconnected." If the factors causing the disconnection are eliminated within the preset time length (for example: network recovery, returning to a safe distance, or resuming login to the same account or associated account, etc.), the local device will automatically reconnect with the remote device. After the reconnection is successful, the mask display will be exited and the normal task display will be restored.

[0254] Optionally, a button may be displayed on the mask to prompt the user: "Reconnect". The user may manually click the button to reconnect.

[0255] Optionally, a button is displayed on the mask to prompt the user: "Exit application". The user can manually click the button to exit the application and display the desktop of the local device. If the user does not click the button within a preset time (e.g., 15 minutes), the application is automatically exited after the preset time, and the desktop of the local device is displayed.

[0256] If the factors causing the disconnection are eliminated before the user exits the application (for example, network recovery, returning to a safe distance, or resuming login to the same account or an associated account, etc.), the local device will automatically reconnect to the remote device. After the reconnection is successful, the mask display will exit and the normal task display will be restored.

[0257] If the migration of the application to the local device fails due to other abnormal reasons, for example, the application on the remote device is migrated to another device, the mask will still be displayed on the local device, and a button will be displayed to the user on the mask to prompt the user: "Exit application."

[0258] The following will explain with reference to specific examples.

[0259] Example 29: Assuming that the first terminal (local device) is a tablet computer, FIG8(w) shows the interface displayed on the first terminal after the remote device (P40 device) is pulled up on the first terminal to open the "Magazine Lock Screen" application on the first terminal. As shown in FIG8(w), if the distance between the local and remote devices exceeds a threshold for a while, after the communication connection between the local and remote devices is interrupted, the "Magazine Lock Screen" application will be displayed on the local device in a mask. A prompt message will be displayed to the user on the mask display to prompt the user: "The distance is too far and the connection has been disconnected."

[0260] Optionally, as shown in FIG8(w), a button may be displayed on the mask to prompt the user: “Reconnect”. The user may manually click the button to reconnect.

[0261] If the factors causing the disconnection are eliminated within the preset time (for example, returning to a safe distance), the local device will automatically reconnect to the remote device. After the reconnection is successful, the mask display will be exited and the normal task display will be restored.

[0262] Optionally, as shown in FIG8(w), a button is displayed on the mask to prompt the user: "Exit application". The user can manually click the button to exit the application and display the desktop of the local device. If the user does not click the button within a preset time (e.g., 15 minutes), the application is automatically exited after the preset time, and the desktop of the local device is displayed.

[0263] In this application, the local device can also migrate an application recently used by other terminals to the local device and display it in the foreground of the local terminal; or migrate an application recently used by the local device to other terminals and display it in the foreground of other terminals. Or, if there are multiple other terminals (for example, including device B and device C), the local device can also migrate an application recently used by device B to device C and display it in the foreground of device C.

[0264] In the above-mentioned process of the local device migrating the task card of a certain device to other devices for display, the user can long press the task card corresponding to the application on the local device, and other surrounding task cards and unavailable device icons can be hidden. Among them, the unavailable device icon means that the device does not support the application, that is, after the application is migrated to the device, the device will not be able to run the application.

[0265] Furthermore, when the user needs to migrate an application on the local device to another device (i.e., the target device), he can drag the task card corresponding to the application to the icon area of ​​the target device. The local device can automatically determine the target device based on the area of ​​the overlapping area of ​​the task card and each device icon.

[0266] Furthermore, the user may also perform different operations on the task card to determine the target device to which the task card needs to be migrated.

[0267] The following will explain with reference to specific examples.

[0268] Example 30: Assume that the first terminal is a mobile phone (P40), the second terminal is a tablet computer 1 (MatePad1), and the third terminal is a tablet computer 2 (MatePad2). Figure 9 (a) shows a schematic diagram of the historical task cards of the second terminal and the third terminal displayed on the recent task interface of the first terminal (this machine or this end device). Assuming that the user needs to migrate the local APP2 to other devices, the user can long press the task card corresponding to APP2. Assuming that MatePad2 is an unavailable device, the icon of MatePad2 can be hidden. Optionally, in an embodiment of the present application, in addition to hiding the icon of the unavailable device, the icon of the unavailable device can also be displayed to the user in other ways. For example, a text prompt box can be set below the unavailable icon to prompt that the device is an unavailable device, or the icon of the unavailable device can also be displayed as a mask or virtualized. This application is not limited here.

[0269] Example 31: Assume that the first terminal is a mobile phone (P40), the second terminal is a tablet computer 1 (MatePad1), and the third terminal is a tablet computer 2 (MatePad2). Figure 9(b) shows a schematic diagram of the historical task cards of the second terminal and the third terminal displayed on the recent task interface of the first terminal (this machine or this terminal device). Assuming that the user needs to migrate the local APP2 to MatePad1, the user can press and hold the task card corresponding to APP2 and slide up to the icon area of ​​MatePad1. The closer the task card is to the icon area of ​​MatePad1, the smaller the task card becomes. When the task card partially overlaps with the icon area of ​​MatePad1, or the distance between the task card and the icon area of ​​MatePad1 is less than a preset threshold, the user lets go. After letting go, the task card can be automatically migrated to MatePad1 and displayed in the foreground of MatePad1.

[0270] Example 32: Assume that the first terminal is a mobile phone (P40), the second terminal is a tablet computer 1 (MatePad1), and the third terminal is a tablet computer 2 (MatePad2). Figure 9(c) shows a schematic diagram of the historical task cards of the second terminal and the third terminal displayed on the recent task interface of the first terminal (this device or this terminal device). Assuming that the user needs to migrate the local APP2 to other devices, the user can press and hold the task card corresponding to APP2 and slide up to the icon area of ​​the device. The task card overlaps with the icon area of ​​the device, and the icon of the device is determined to be the target device. For example, as shown in Figure 9(c), after the user presses and holds the task card corresponding to APP2 and slides up, the task card overlaps with the icon of the MatePad1 device, and MatePad1 is determined to be the target device. After the user lets go, the task card can be automatically migrated to the target device and displayed in the foreground of the target device.

[0271] Example 33: Assume that the first terminal is a mobile phone (P40), the second terminal is a tablet computer 1 (MatePad1), and the third terminal is a tablet computer 2 (MatePad2). Figure 9 (d) shows a schematic diagram of the historical task cards of the second terminal and the third terminal displayed on the recent task interface of the first terminal (this device or this device). Assuming that the user needs to migrate the local APP2 to other devices, the user can press and hold the task card corresponding to APP2 and slide up to the icon area of ​​the device. If the task card overlaps with the icon areas of multiple devices at the same time, the icon of the device with the largest overlapping area is determined to be the target device. As shown in Figure 9 (d), the task card overlaps with the device icons of MatePad1 and MatePad2 at the same time, and the area of ​​overlap between the task card and the icon of the MatePad1 device is the largest, then MatePad1 is determined to be the target device. After the user lets go, the task card can be migrated to the target device and displayed in the foreground of the target device.

[0272] Example 34: Assume that the first terminal is a mobile phone (P40), the second terminal is a tablet computer 1 (MatePad1), and the third terminal is a tablet computer 2 (MatePad2). Figure 9 (e) shows a schematic diagram of the historical task cards of the second terminal and the third terminal displayed on the recent task interface of the first terminal (this machine or this terminal device). Assuming that the user needs to migrate the local APP2 to other devices, the user can press and hold the task card corresponding to APP2 and slide up. After the distance that the user slides the task card upward (that is, the distance between the position of the user's mobile phone finger touching the screen when not sliding and the position of the user's mobile phone finger touching the screen after sliding) is greater than or equal to the preset distance, the device directly above the task card is the target device. For example, when the user presses and holds the task card corresponding to APP2 without sliding, the interface displayed is shown in Figure 9 (e), and the interface displayed after sliding up is shown in Figure 9 (f). The device directly above the task card is MatePad1, then MatePad1 is determined to be the target device. After the user lets go, the task card can be migrated to the target device and displayed in the foreground of the target device.

[0273] Example 35: Assume that the first terminal is a mobile phone (P40), the second terminal is a tablet computer 1 (MatePad1), and the third terminal is a tablet computer 2 (MatePad2). Figure 9(g) shows a schematic diagram of the historical task cards of the second terminal and the third terminal displayed on the recent task interface of the first terminal (this machine or this terminal device). Assuming that the user needs to migrate the local APP2 to other devices, the user can press and hold the task card corresponding to APP2 and swipe up. After the distance between the user's mobile phone finger touch screen and the top of the screen of the first terminal is less than or equal to the preset distance, the device directly above the task card is the target device. For example, the interface displayed after swiping up is shown in Figure 9(h). The device directly above the task card is MatePad1, then MatePad1 is determined to be the target device. After the user lets go, the task card can be migrated to the target device and displayed in the foreground of the target device.

[0274] In the embodiment of the present application, in addition to using the above method to determine the target device to which the task card needs to be migrated, some preset rules can also be set: for example, the user can long press the task card of other devices in the recent task interface of the local machine, and then release it after long pressing, and the task card will automatically migrate to the local machine, and the application corresponding to the task card will be displayed or run on the local machine. Alternatively, the user can also set the default target device by himself. After the user long presses a task card and releases it, the task card will automatically migrate to the default target device. This application is not limited here.

[0275] After the user selects the target device by operating the task card, as a possible implementation method: the user can continue to press and drag the task card until the task card overlaps with the selected target device icon. At this time, the user lets go, and the task card can be migrated to the target device and displayed in the foreground of the target device, completing the cross-device interaction. As a possible implementation method: After the user selects the target device by operating the task card, although the task card has not overlapped with the selected target device icon, at this time, the user lets go, and the task card can also be migrated to the target device and displayed in the foreground of the target device, completing the cross-device interaction. For example, as shown in Example 36.

[0276] Example 36: Assume that the first terminal is a mobile phone (P40), the second terminal is a tablet computer 1 (MatePad1), and the third terminal is a tablet computer 2 (MatePad2). Figure 9 (i) shows a schematic diagram of the historical task cards of the second terminal and the third terminal displayed on the recent task interface of the first terminal (this machine or this terminal device). Assuming that the user needs to migrate the local APP2 to other devices, after the user determines the target device through any of the above operations, although the task card has not overlapped with the selected target device icon, the user can let go at this time. After the user lets go, the task card can be migrated to the target device and displayed in the foreground of the target device. For example, Figure 9 (i) shows the interface diagram of the target device selected by the user. The target device is MatePad1. At this time, the user lets go, and the displayed interface is shown in Figure 9 (j). The task card can be automatically moved to the icon of the target device (for example, the task card automatically flies to the target device icon), and the migration of the task card to the target device is completed. The task card can be displayed in the foreground of the target device to complete cross-device interaction.

[0277] In the embodiment of the present application, after the user selects the target device by operating the task card, the icon of the target device can also be changed accordingly, for example, the icon of the target device can be moved down a certain distance, or the color of the icon of the target device can be changed, etc., to prompt the user of the selected target device. In addition, the user can also operate the task card to change the selected target device, etc. This will be explained in conjunction with specific examples.

[0278] Example 37: Assume that the first terminal is a mobile phone (P40), the second terminal is a tablet computer 1 (MatePad1), and the third terminal is a tablet computer 2 (MatePad2). Schematic diagram of the historical task cards of the second terminal and the third terminal displayed on the recent task interface of the first terminal (this machine or this terminal device). Assuming that the user needs to migrate the local APP2 to other devices, after the user determines the target device through any of the above operations, the icon of the target device can move down a distance. For example, as shown in Figure 9 (k), the target device selected by the user is MatePad1, then the MatePad1 device icon can move down a certain distance. Or. The color of the target device icon can be changed to the selected color. As shown in Figure 9 (l), the target device selected by the user is MatePad1, then the MatePad1 device icon becomes filled.

[0279] Optionally, in the present application, the selected target device may be identified in other ways, for example, a text prompt box may be used to prompt the user of the selected target device, etc. The present application does not make any limitation thereto.

[0280] In the present application, the correspondence between the position of the task card and the target device can also be preset. After the user presses and holds the task card and drags it to the preset position, the target device corresponding to the area is automatically displayed to the user. As the position of the task card dragged by the user changes, the target device also changes accordingly. After the user determines the target device to be migrated, he can let go, and the task card can be automatically moved to the icon of the target device (for example, the task card automatically flies to the target device icon), and the migration of the task card to the target device is completed. The task card can be displayed in the foreground of the target device to complete cross-device interaction.

[0281] Example 38: Assume that the first terminal is a mobile phone (P40), the second terminal is a tablet computer 1 (MatePad1), and the third terminal is a tablet computer 2 (MatePad2). Schematic diagram of the historical task cards of the second terminal and the third terminal displayed on the recent task interface of the first terminal (this machine or this end device). Assuming that the user needs to migrate the local APP2 to other devices, after the user presses and holds the task card and drags to change the position of the task card, the target device corresponding to the position of the task card will be displayed. For example, referring to Figure 9 (m), the user presses and holds the task card and drags to change the position of the task card, and the displayed target is MatePad1. If the user determines that APP2 needs to be migrated to MatePad1, the user can let go at this time, and the displayed interface is shown in Figure 9 (n). The task card can be automatically moved to the icon of the target device (for example, the task card automatically flies to the target device icon), and the migration of the task card to the target device is completed.

[0282] In the embodiment of the present application, after the user selects the target device by operating the task card, as the user further operates the task card, the selected target device will also change, or the selected target device may be cancelled.

[0283] Example 39: Assume that the first terminal is a mobile phone (P40), the second terminal is a tablet computer 1 (MatePad1), and the third terminal is a tablet computer 2 (MatePad2). Schematic diagram of the historical task cards of the second terminal and the third terminal displayed on the recent task interface of the first terminal (this machine or this terminal device). Assuming that the user needs to migrate the local APP2 to other devices, after the user determines the target device through any of the above operations, for example, referring to Figure 9 (o), assuming that the selected target device is MatePad1, if the user continues to drag the task card to the left or right, the selected target device will switch accordingly. Referring to Figure 9 (p), assuming that the user drags the task card to the right, the changed target device is MatePad2, and the device icon of MatePad2 moves down a distance. The user can let go at this time, and the task card can be automatically moved to the icon of the target device (MatePad2) (for example, the task card automatically flies to the target device icon), and the migration of the task card to the target device is completed.

[0284] Example 40: Assume that the first terminal is a mobile phone (P40), the second terminal is a tablet computer 1 (MatePad1), and the third terminal is a tablet computer 2 (MatePad2). Schematic diagram of the historical task cards of the second terminal and the third terminal displayed on the recent task interface of the first terminal (this machine or this terminal device). Assuming that the user needs to migrate the local APP2 to other devices, after the user determines the target device through any of the above operations, for example, referring to Figure 9 (q), assuming that the selected target device is MatePad1, the device icon of MatePad1 moves down a distance. If the user continues to drag the task card and slide down, after the sliding distance (that is, the distance between the user's mobile phone finger touch screen position when not sliding and the user's mobile phone finger touch screen position after sliding) is greater than or equal to the preset distance, for example, referring to Figure 9 (r), at this time, let go, then cancel the selected target device MatePad1, the device icon of MatePad1 is restored to the previous position, the task card is restored to the state display before the target is selected, and the task card migration is canceled.

[0285] Example 41: Assume that the first terminal is a mobile phone (P40), the second terminal is a tablet computer 1 (MatePad1), and the third terminal is a tablet computer 2 (MatePad2). Schematic diagram of the historical task cards of the second terminal and the third terminal displayed on the recent task interface of the first terminal (this machine or this terminal device). Assuming that the user needs to migrate the local APP2 to other devices, after the user determines the target device through any of the above operations, for example, referring to Figure 9 (s), assuming that the selected target device is MatePad1, the device icon of MatePad1 moves down a distance. If the user continues to drag the task card and slide down, after the sliding distance (the distance between the user's mobile phone finger touch screen position and the top of the screen of the first terminal after sliding) is greater than or equal to the preset distance, for example, referring to Figure 9 (t), let go at this time, then cancel the selected target device MatePad1, the device icon of MatePad1 is restored to the previous position, the task card is restored to the state display before the target is selected, and the task card migration is canceled.

[0286] When the user drags the task card to select a target device or unselect a target device, the user can also drag the task card to the left or right edge of the screen. In this case, the user can continue to drag the task card to the left or right, so that more device icons can be displayed at the top of the screen, and the user can determine the target device from more device icons. In an embodiment of the present application, the more device icons can be displayed in a row, or can be displayed at the top of the device screen in the form of a radar chart. This application is not limited here. For example, Example 42 shows an interface schematic diagram of more device icons arranged in a row.

[0287] Example 42: Assume that the first terminal is a mobile phone (P40), the second terminal is a tablet computer 1 (MatePad1), and the third terminal is a tablet computer 2 (MatePad2). Schematic diagram of the historical task cards of the second terminal and the third terminal displayed on the recent task interface of the first terminal (this machine or local device). Assume that the user needs to migrate the local APP2 to other devices. For example, referring to Figure 9 (u), the user drags the task card and swipes left. After the task card is located at the right edge of the screen, the user continues to drag the task card to the right. The displayed interface is shown in Figure 9 (v). Other device icons (MatePad3 and Mate X2) are displayed at the top of the screen, and multiple device icons displayed at the top of the screen are displayed in a row. The user can continue to operate the task card to determine the target device from the more device icons.

[0288] In the embodiment of the present application, when the local device migrates a task card of a device in the recent task interface to the target device for display or operation, for example, the user migrates the video of the mobile phone to the large-screen device for playback, or migrates the audio of the mobile phone to the speaker for playback, etc., if the target device is in a black screen state, the target device can automatically light up the screen first, and after the screen is lit, the user can manually unlock it to display the application corresponding to the task card; or, the target device can automatically light up the screen first, and automatically trigger unlocking, and the user can manually unlock it to display the application corresponding to the task card; or, the target device can automatically light up the screen first, and automatically unlock it, and after unlocking it, the application corresponding to the task card can be displayed. This will be explained in conjunction with specific examples.

[0289] Example 43: Assume that the first terminal is a tablet computer (MatePad), the second terminal is a mobile phone (P40), and the third terminal is a folding screen mobile phone (Mate X2). A schematic diagram of the historical task cards of the second terminal and the third terminal is displayed on the recent task interface of the first terminal (this machine or this terminal device). Assume that the user needs to migrate the local APP2 to the second terminal, and the second terminal is in a black screen state. After the user migrates the task card corresponding to APP2 to the mobile phone (P40) through any of the methods in the above embodiments, as shown in Figure 10 (a), the mobile phone P40 is in a black screen state. After the mobile phone P40 receives the task information, the mobile phone P40 automatically lights up the screen. After the mobile phone P40 automatically lights up the screen, it triggers the user to manually unlock. After the user manually unlocks, the APP2 can be displayed or run on the mobile phone P40.

[0290] Example 44: Assume that the first terminal is a tablet computer (MatePad), the second terminal is a mobile phone (P40), and the third terminal is a folding screen mobile phone (Mate X2). Schematic diagram of the historical task cards of the second terminal and the third terminal displayed on the recent task interface of the first terminal (this machine or this terminal device). Assume that the user needs to migrate the local APP2 to the second terminal, and the second terminal is in a black screen state. After the user migrates the task card corresponding to APP2 to the mobile phone (P40) through any of the methods in the above embodiments, as shown in Figure 10 (b), the mobile phone (P40) is in a black screen state. After the mobile phone (P40) receives the task information, the mobile phone (P40) automatically lights up the screen and triggers the user to manually unlock it. After the user manually unlocks it, the APP2 can be displayed or run on the mobile phone (P40).

[0291] Example 45: Assume that the first terminal is a tablet computer (MatePad), the second terminal is a mobile phone (P40), and the third terminal is a folding screen mobile phone (Mate X2). Schematic diagram of the historical task cards of the second terminal and the third terminal displayed on the recent task interface of the first terminal (this machine or this terminal device). Assume that the user needs to migrate the local APP2 to the second terminal, and the second terminal is in a black screen state. After the user migrates the task card corresponding to APP2 to the mobile phone (P40) through any of the methods in the above embodiments, as shown in Figure 10 (c), the mobile phone (P40) is in a black screen state. After the mobile phone (P40) receives the task information, the mobile phone (P40) automatically lights up the screen and triggers automatic unlocking. After the user manually unlocks it, the APP2 can be displayed or run on the mobile phone (P40).

[0292] Optionally, in an embodiment of the present application, when the local device migrates a task card of a device in the recent task interface to the target device for display or operation, if the target device is in a black screen state, as a possible implementation method, different rules for triggering the target device to light up the screen and unlock can be set according to the different types of applications that need to be migrated, or the corresponding sensitivity of the applications. For example, for applications with relatively low sensitivity (such as video playback, audio playback, etc.), after migrating to a target device with a black screen, the target device can automatically light up the screen and trigger automatic unlocking, thereby displaying or running the application on the target device. For applications with relatively high sensitivity (such as document editing, photo playback, etc.), after migrating to a target device with a black screen, the target device can automatically light up the screen and trigger the user to manually unlock, thereby displaying or running the application on the target device.

[0293] Optionally, as another possible implementation, different rules for triggering the target device to light up and unlock the screen can be set according to different situations of the target device (for example, target devices with different security levels or security capabilities, target devices of different types, etc.). For example, assuming that the target device is a large-screen device, after the application is migrated to the target device with a black screen, the target device can automatically light up the screen and trigger the user to manually unlock it, so that the application can be displayed or run on the target device. Assuming that the target device is a smart speaker, after the application is migrated to the target device with a black screen, the target device can automatically light up the screen and automatically unlock it, so that the application can be displayed or run on the target device.

[0294] In an embodiment of the present application, when a source device migrates a task card in a recent task interface to a target device to run an application corresponding to the task card, if the application corresponding to the task card involves the hardware capabilities of the device, for example, including: the hardware capabilities of the device such as the camera, microphone, and display screen, after the application is migrated from the source device to the target device, any one of the following rules can be used to use the hardware capabilities of the source device or the target device to run the application on the target device:

[0295] The first rule: After the source device migrates the application to the target device, it does not use the hardware capabilities of the target device. In other words, after the application is migrated to the target device, it continues to use the hardware capabilities of the source device to run the application on the target.

[0296] The second rule: After the source device migrates the application to the target device, it uses part of the hardware capabilities of the target device. In other words, after the application is migrated to the target device, it can use part of the hardware capabilities of the source device and part of the hardware capabilities of the target device at the same time to collaboratively run the application on the target.

[0297] The third rule: After the source device migrates the application to the target device, it uses the hardware capabilities of the target device and releases the hardware capabilities of the source device occupied by the application. In this case, the source device can use its own hardware capabilities to run the new application, that is, the two devices can use their own hardware capabilities to perform different tasks without affecting each other.

[0298] The fourth rule: After the source device migrates the application to the target device, it uses the hardware capabilities of the target device and does not release the hardware capabilities of the source device occupied by the application.

[0299] The following will explain with specific examples:

[0300] Example 46: Assuming that the first terminal is tablet computer 1 (MatePad1), and the second terminal is mobile phone (P40), the historical task cards of the second terminal and other terminals are displayed on the recent task interface of the first terminal (local device or local device). Assuming that the user needs to migrate the video call of mobile phone P40 (source device) to MatePad1 (target device), as shown in Figure 11 (a), the user can click the task card corresponding to the video call in the recent task interface of MatePad1. After clicking, the video call will be run on MatePad1. The video call calls the camera, microphone and speaker of MatePad1 by default, that is, the hardware capabilities of the target device are used, and the hardware capabilities of mobile phone P40 are not used. Optionally, the hardware capabilities of the mobile phone P40 source device occupied by the video call can be released; or, the hardware capabilities of the mobile phone P40 occupied by the video call are not released. If the hardware capabilities of the mobile phone P40 occupied by the video call are not released, the mobile phone P40 cannot use these hardware capabilities to re-initiate a new task.

[0301] Optionally, a prompt box may pop up on MatePad1, for example, the prompt box prompts the user whether to use the hardware capabilities of this device. If the user clicks "Yes", the hardware capabilities of MatePad1 can be used; if the user clicks "No", the hardware capabilities of the source device (mobile P40) are used. The prompt box may disappear automatically after a preset time. If the user does not make a choice within the preset time, the hardware capabilities of MatePad1 are used by default.

[0302] Example 47: Assume that the first terminal is tablet computer 1 (MatePad1), and the second terminal is mobile phone (P40), and the historical task cards of the second terminal and other terminals are displayed in the recent task interface of the first terminal. Assuming that the user needs to migrate the video call of mobile phone P40 (source device) to MatePad1 (target device), as shown in Figure 11(b), the user can click the task card corresponding to the video call in the recent task interface of MatePad1. After clicking, the video call will be run on MatePad1. The video call uses the camera, microphone and speaker of MatePad1 and mobile phone P40 at the same time to collaboratively complete the video call on MatePad1. That is, the hardware capabilities of the target device and the source device are used at the same time to collaboratively complete the running of the application on the target. As shown in Figure 11(b), after the video call is migrated from the mobile phone P40 to the tablet MatePad1, the camera of MatePad1 is used, and the user can choose to open the camera of the mobile phone P40 on MatePad1, and use the camera of MatePad1 and the camera of the mobile phone P40 to make a video call at the same time, and use the microphones and speakers of MatePad1 and mobile phone P40 for receiving and playing sound at the same time.

[0303] Example 48: Assuming that the first terminal is tablet computer 1 (MatePad1), and the second terminal is mobile phone (P40), the historical task cards of the second terminal and other terminals are displayed in the recent task interface of the first terminal. Assuming that the user needs to migrate the video call of mobile phone P40 (source device) to MatePad1 (target device), as shown in Figure 11 (c), the user can click the task card corresponding to the video call in the recent task interface of MatePad1. After clicking, the video call (video call task 1) will be run on MatePad1. The video call calls the camera, microphone and speaker of MatePad1 by default, that is, the hardware capabilities of the target device are used, and the hardware capabilities of the source device (local device) are not used. In addition, after the video task is migrated from mobile phone P40 to MatePad1, another video task (video call task 2) can be performed on mobile phone P40. Both ends of mobile phone P40 and MatePad1 use their own hardware capabilities (camera capabilities, microphones, speaker capabilities, input capabilities, etc.) independently without interfering with each other. In other words, after the P40 mobile phone migrates the video application to the MatePad1, it uses the hardware capabilities of the MatePad1 and releases the hardware capabilities of the P40 mobile phone occupied by the video application. In this case, the P40 mobile phone can use its own hardware capabilities to run the new application, that is, the two devices can use their own hardware capabilities to perform different tasks without affecting each other.

[0304] In an embodiment of the present application, when a task source device is migrated to a target device for operation, and the hardware capabilities of the target device are used during operation, during the operation of the task on the target device, if a new task is run on the target device, and there is a conflict in hardware capabilities between the new task run by the target device and the task migrated from the source device, for example, both need to use the camera, microphone, speaker, etc. of the target device, as a possible implementation method: the task migrated from the source device can be automatically switched to use the hardware capabilities of the source device and continue to run on the source device, while the new task on the target device gives priority to using the hardware capabilities of the target device, that is, ensuring that the task of the target device is executed first. After the new task on the target device is executed, the hardware capabilities of the target device are released, and the task migrated from the source device can be switched to use the hardware capabilities of the target device and continue to run on the target device.

[0305] Optionally, as another possible implementation method: when there is a hardware capability conflict between the new task running on the target device and the task migrated from the source device, the task migrated from the source device can also give priority to using the hardware capabilities of the target device, that is, ensuring that the migrated task continues to be executed on the target device first; after the migrated task is completed on the target device, the new task on the target device can use the hardware capabilities of the target device to execute the new task.

[0306] Optionally, as another possible implementation: when there is a hardware capability conflict between a new task running on the target device and a task migrated from the source device, the hardware capability of the target device can be separated by task, supporting both the new task and the task migrated from the source device. In addition, the target device can also display the new task and the task migrated from the source device in a split screen, that is, displaying the new task and the task migrated from the source device at the same time. This will be explained below with reference to a specific example.

[0307] Example 49: Referring to Figure 11(d), assume that the video playback task on the mobile phone P40 (source device) is migrated to the tablet computer MatePad (target device), and the video playback task is run on the MatePad. During the video playback on the MatePad, the MatePad receives a video call task, and the MatePad can pop up a "Video Call Notification" prompt box to the user. After the user clicks the prompt box, as shown in Figure 11(e), the video call interface is displayed on the MatePad, and the video automatically migrates back to the mobile phone P40 to continue playing. After the video call on the MatePad ends, the video automatically migrates to the MatePad to continue playing.

[0308] Example 50: Referring to Figure 11(f), assuming that the video playback task on the mobile phone P40 (source device) is migrated to the tablet computer MatePad (target device), the video playback task is run on the MatePad. During the video playback on the MatePad, the video call task is received on the MatePad, and a "Video Call Notification" prompt box can pop up to the user on the MatePad. After clicking the prompt box, as shown in Figure 11(g), the MatePad splits the screen to display the video playback and video call, and the hardware capabilities of the MatePad (such as cameras, microphones, speakers, input / output capabilities, etc.) can be separated according to the two tasks of video playback and video calls, while supporting the operation of video playback and video calls.

[0309] In the embodiment of the present application, when a task is migrated from the local device (source device) to the target device for execution and the hardware capability of the source device is used during execution, if a new task is run on the source device during the execution of the task on the target device, and there is a hardware capability conflict between the new task run by the source device and the task migrated from the source device, for example, both need to use the camera, microphone, speaker, etc. of the target device, there are several possible implementations as follows:

[0310] As a possible implementation manner: the task migrated from the source device can be automatically suspended on the target device, and after the new task of the source device is completed, the migrated task can be automatically continued on the target device.

[0311] As another possible implementation method: the target device uses its own hardware capabilities to continue to execute the task migrated from the source device, that is, the source device uses its own hardware capabilities to execute the new task, and the target device uses its own hardware capabilities to execute the task migrated from the source device. After the new task on the source device is completed, the target device can switch to using the hardware capabilities of the source device to execute the task migrated from the source device, or continue to use its own hardware capabilities to execute the task migrated from the source device.

[0312] As another possible implementation manner: the hardware capabilities of the source device may be separated according to tasks, supporting both new tasks and tasks migrated from the source device and executed on the target device.

[0313] The following is an explanation with reference to specific examples.

[0314] Example 51: Referring to FIG11(h), it is assumed that the video playback task on the mobile phone P40 (source device) is migrated to the tablet computer MatePad (target device), and the video playback task is run on the MatePad. The hardware capabilities of the mobile phone P40 are used in the process of running the video playback task on the MatePad. During the process of running the video playback task on the MatePad, the mobile phone P40 receives a new information notification. The mobile phone P40 prompts the user with sound or vibration. Assuming that the hardware capabilities required for sound or vibration do not conflict with the hardware capabilities required for video playback, the video continues to play on the MatePad. The user can click on the notification prompt box that pops up on the mobile phone P40 to view the information on the mobile phone P40. The two tasks of viewing information on the mobile phone P40 and playing videos on the MatePad do not affect each other and are carried out at the same time. The two tasks use the hardware capabilities of the mobile phone P40 at the same time.

[0315] Example 52: Referring to FIG11(i), it is assumed that the video playback task on the mobile phone P40 (source device) is migrated to the tablet computer MatePad (target device), and the video playback task is run on the MatePad. The hardware capabilities (microphone, speaker, etc.) of the mobile phone P40 are used during the video playback task on the MatePad. During the video playback task on the MatePad, the mobile phone P40 receives an incoming call (for example, an operator or VOIP network call, etc.), the incoming call ringtone rings on the mobile phone P40, and the MatePad continues to play the video. As shown in FIG11(j), after the user answers the call by sliding, the call audio is input and output on the mobile phone P40. Since the hardware capabilities used by the MatePad for video playback conflict with the hardware capabilities used by the mobile phone P40 for voice calls, the video playback on the MatePad is automatically paused. After the call on the mobile phone P40 ends, the video on the MatePad automatically continues to play.

[0316] Example 53: Referring to FIG11(i), it is assumed that the video playback task on the mobile phone P40 (source device) is migrated to the tablet computer MatePad (target device), and the video playback task is run on the MatePad. The hardware capabilities (microphone, speaker, etc.) of the mobile phone P40 are used during the video playback task on the MatePad. During the video playback task on the MatePad, the mobile phone P40 receives an incoming call (for example, an operator or VOIP network call, etc.), the incoming call ringtone rings on the mobile phone P40, and the MatePad continues to play the video. As shown in FIG11(k), after the user answers the call by sliding, the call audio is input and output on the mobile phone P40. Since the hardware capabilities used by the MatePad for video playback conflict with the hardware capabilities used by the mobile phone P40 for voice calls, the hardware capabilities of the mobile phone P40 can be separated according to these two tasks (voice calls and video playback), and the video playback on the MatePad continues, and the call on the mobile phone P40 is also carried out at the same time. After the call on the P40 ends, the hardware capabilities occupied by the call on the P40 are automatically occupied by the video playback of the MatePad.

[0317] Alternatively, in Example 53, after the user answers the call by sliding, the call audio is input and output on the mobile phone P40. Since the hardware capabilities used for video playback on the MatePad conflict with the hardware capabilities used for voice calls on the mobile phone P40, the video playback on the MatePad can automatically switch to using the hardware capabilities of the MatePad, that is, the devices at both ends can use their respective hardware capabilities to perform different tasks without affecting each other. The video playback on the MatePad continues. The call on the mobile phone P40 is also ongoing at the same time. After the call on the P40 ends, the video playback task on the MatePad automatically switches to using the hardware capabilities of the mobile phone P40 to continue playing.

[0318] Example 54: FIG. 12(a) is a schematic diagram showing the historical task cards of P40 (source device) used by the user on the vehicle computer (target device). As shown in 12(a), when the layout of the historical task cards of P40 is displayed on the vehicle computer, the multi-task layout is displayed according to the vertical screen use of P40. The user can operate the task card of P40 on the vehicle computer. In the embodiment of the present application, the operation can be any of the operations in the above examples, thereby enabling the user to remotely manage and control the task of P40 on the vehicle computer.

[0319] Optionally, when displaying the historical task cards of P40 on the vehicle computer, any display method or display rule in the above examples may be used, for example: the last task card displays a desktop snapshot of P40, in which a FA card exists; or, the last task card displays a snapshot of the first screen of the P40 desktop, which can be horizontally slid to switch to display a snapshot of the second screen of the P40 desktop, and the user can click the application ICON on the desktop snapshot to open the application on the vehicle computer; or, the last task card displays a P40 desktop snapshot and a floating window; or, the last task card displays a P40 desktop snapshot and a floating ball; or, the last task card displays task cards of multiple light devices controlled by P40 that are running; or, the last task card displays P40 displaying the desktop application ICON of P40; or, the user can pull up the task card of P40 on the vehicle computer; or, the user can create a split screen / floating window across devices on the vehicle computer; or, after the task on P40 is migrated to the vehicle computer, the hardware capabilities can be allocated on the vehicle computer and P40 according to the hardware usage rules in the above examples, etc., and this application is not limited here.

[0320] In the present application, the vehicle computer may include an electronic control unit (ECU), a driving computer, a vehicle computer or a vehicle T-BOX, etc., and the embodiments of the present application are not limited thereto.

[0321] In this application, the smart device used by the user (such as P40) can establish a communication connection with the vehicle computer using Bluetooth (BT) technology, Wi-Fi, NFC, Zigbee, USB, Cellular, etc., establish a trusted relationship and transmit information to each other.

[0322] Example 55: FIG. 12(b) is a schematic diagram showing a historical task card of a PC device (source device) used by a user on a vehicle computer (target device). As shown in FIG. 12(b), a user can operate a task card of a PC device on a vehicle computer. In an embodiment of the present application, the operation can be an operation in any of the above examples, thereby enabling remote task management and control of a PC device by a user on a vehicle computer.

[0323] Optionally, when displaying the historical task cards of P40 on the car computer, any display method or display rule in the above examples can also be used. For example: the last task card displays a desktop snapshot of the PC device, and there is a FA card in the desktop snapshot; or, the last task card displays a desktop snapshot of the PC device and a floating window; or, the last task card displays a desktop snapshot of the PC device and a floating ball; or, the last task card displays task cards of multiple light devices controlled by the PC device; or, the last task card displays the desktop application ICON of the P40 displayed by the PC device; or, the user can pull up the task card of the PC device on the car computer; or, the user can create a split screen / floating window across devices on the car computer; or, after the tasks on the PC device are migrated to the car computer, the hardware capabilities can be allocated on the car computer and the PC device according to the hardware usage rules in the above examples, etc. This application is not limited here.

[0324] Example 56: FIG. 12(c) shows a schematic diagram of displaying the historical task cards of P40 (source device) used by the user on the PC device (target device). As shown in FIG. 12(c), the user can operate the task cards of P40 on the PC device. In the embodiment of the present application, the operation can be any of the operations in the above examples, thereby realizing the remote task management and control of P40 by the user on the PC device.

[0325] Optionally, when displaying the historical task cards of P40 on a PC device, any display method or display rule in the above examples may be used, for example: the last task card displays a desktop snapshot of P40, in which a FA card exists; or, the last task card displays a snapshot of the first screen of the P40 desktop, which can be horizontally slid to switch to display a snapshot of the second screen of the P40 desktop, and the user can click the application ICON on the desktop snapshot to open the application on the PC device; or, the last task card displays a P40 desktop snapshot and a floating window; or, the last task card displays a P40 desktop snapshot and a floating ball; or, the last task card displays task cards of multiple light devices controlled by P40 that are running; or, the last task card displays P40 displaying the desktop application ICON of the P40; or, the user can pull up the task card of P40 on the PC device; or, the user can create a split screen / floating window across devices on the PC device; or, after the tasks on P40 are migrated to the car computer, the hardware capabilities can be allocated on the PC device and P40 according to the hardware usage rules in the above examples, etc., and this application is not limited here.

[0326] Optionally, in the embodiment of the present application, in addition to executing any of the above-mentioned solutions between two devices, remote task management and control can also be performed between more devices (e.g., 3, 4, etc.) using the task cards on the recent task interface. This is explained below with reference to specific examples.

[0327] Example 57: Fig.13 Shown is a schematic diagram of the first terminal (MatePad1) and the historical task card displayed on the recent task interface of the second terminal (P40). Assuming that the user needs to migrate APP2 of P40 to the third terminal (MateX2), the user can press and hold the task card corresponding to APP2 and slide up to the icon area of ​​Mate X2. After the user lets go, the task card can be automatically migrated to the Mate X2 and displayed or run in the foreground of Mate X2. Optionally, when displaying or running the application corresponding to APP2 on Mate X2, or displaying the task card of APP2, the application corresponding to APP2 can be displayed or run on Mate X2, or the task card of APP2 can be displayed in the expanded vertical screen mode, expanded horizontal screen mode, folded vertical screen mode, or folded horizontal screen mode of Mate X2.

[0328] Optionally, when displaying or running the application corresponding to APP2 on the Mate X2, or displaying the task card of APP2, it can be displayed in full screen or floating window.

[0329] Optionally, in Example 57, on the device P40, the user can also press and hold the task card corresponding to APP2 with the left hand, and then slide the task card to the left with the right hand to switch to the task card corresponding to other applications on the native (P40) or (MatePad1) and make a selection. After the selection is completed, slide the task card corresponding to APP2 together with the task cards corresponding to other APPs to Mate X2 and then let go, so that the applications corresponding to two different APPs can be displayed on Mate X2. Optionally, when the applications corresponding to two different APPs, or the task cards corresponding to two different APPs are displayed on MateX2, the two different APPs can be displayed in split screen; or, one APP is displayed in full screen and the other APP is displayed in a floating window; both different APPs are displayed in floating windows.

[0330] In an embodiment of the present application, based on the above three migration modes (copy mode, migration mode based on window projection technology, and migration mode based on FA technology), the application on the source device can be migrated to the target for operation, and various desktop applications on the source device can be viewed and used on the target device, thereby forming a super desktop on the target. In this application, the super desktop can be understood as: if the desktop applications of multiple other devices can be viewed and used on one device, the function of the super desktop is implemented on the device. This will be explained below with specific examples.

[0331] Example 58: In the present application, whether a certain device needs to implement the function of the super desktop can be determined using the situation shown in Figure 14(a). As shown in Figure 14(a), if the car computer and the mobile phone have established a trusted connection relationship, the super desktop can be displayed on the car computer to implement the function of the super desktop. For example, the desktop application of the mobile phone can be viewed and used on the car computer. However, it is not necessary to implement the function of the super desktop on the mobile phone. For example, the desktop application of the car computer does not need to be viewed and used on the mobile phone. In the present application, the car computer can be, for example: a driving computer, a car computer, a car device or a car T-BOX, etc., and the present application does not limit this.

[0332] If a large-screen device (such as a Huawei TV) and a mobile phone have established a trusted connection, the super desktop can be displayed on the large-screen device to implement the super desktop function. However, the super desktop function does not need to be implemented on the mobile phone.

[0333] If a tablet computer and a mobile phone have established a trusted connection, the super desktop can be displayed on the tablet computer to realize the function of the super desktop, while the function of the super desktop does not need to be realized on the mobile phone.

[0334] If a trusted connection is established between a personal PC and a mobile phone, the super desktop can be displayed on the personal PC to realize the function of the super desktop, while the function of the super desktop does not need to be realized on the mobile phone.

[0335] If a large-screen device (such as a Huawei TV) and a tablet computer have established a trusted connection relationship, the super desktop can be displayed on both the large-screen device and the tablet computer to realize the function of the super desktop.

[0336] If a trusted connection relationship is established between the personal PC and the tablet computer, the super desktop can be displayed on both the personal PC and the tablet computer, realizing the function of the super desktop.

[0337] Optionally, as another possible implementation, in each of the above scenarios, no matter which device the mobile phone has established a trusted connection with, the function of the super desktop can also be implemented on the mobile phone, for example, viewing and using desktop applications of other devices on the mobile phone. This application is not limited here.

[0338] In the embodiment of the present application, the layout of the super desktop on different devices can be distinguished based on the physical characteristics of the devices at each end of the trusted connection (such as the size of the screen, etc.), or whether it is easy to interact accurately, etc.

[0339] For devices that are difficult to interact with accurately, such as car computers and large-screen devices, the super desktop applications displayed on these devices are limited. For example, they can be screened by the system or the user and displayed according to the desktop application layout of the target device (i.e., the device that is difficult to interact with accurately);

[0340] For devices that are easy to interact with accurately, such as tablets and personal PCs, as many desktop applications as possible can be displayed. When displaying desktop applications on these devices, the applications can be displayed by default according to the desktop layout of the source device of the desktop application. When the desktop style of the source device is a drawer-style desktop, when displaying desktop applications on these devices, they are uniformly displayed according to the desktop layout of the target device (i.e., the device that is easy to interact with accurately).

[0341] The following is a collection of specific examples to illustrate:

[0342] Example 59: FIG14(b) is a schematic diagram showing a super desktop layout on a vehicle computer. Since the vehicle computer is a device that is difficult to interact with accurately, when displaying the desktop application of the mobile phone P40 on the vehicle computer, it needs to be filtered by the vehicle computer system or the user, and the filtered desktop application of the mobile phone P40 is displayed on the vehicle computer, and the desktop applications of the vehicle computer and the mobile phone P40 are arranged together and displayed in tabs.

[0343] Example 60: FIG14(c) shows a schematic diagram of displaying a super desktop layout on a large-screen device. Since large-screen devices are devices that are difficult to interact with accurately, when displaying the desktop applications of the mobile phone P40 on the large-screen device, they need to be filtered by the large-screen device system or user, and the filtered desktop applications of the mobile phone P40 are displayed on the large-screen device. In addition, the desktop applications of the large-screen device and the mobile phone P40 are arranged together and displayed in tabs.

[0344] Example 61: FIG. 14(d) is a schematic diagram showing a super desktop layout on a tablet computer (e.g., MatePad 1). Since a tablet computer is a device that is easy to interact with accurately, when displaying the desktop application of the mobile phone P40 on the tablet computer, it is not necessary to filter through the tablet computer system or user, and the mobile phone P40 desktop applications can be displayed as much as possible according to the desktop layout of the mobile phone P40. As shown in FIG. 14(d), when the desktop style of the mobile phone P40 is a standard-style desktop, a schematic diagram of displaying the desktop application of the mobile phone P40 on the tablet computer is shown. As shown in FIG. 14(d), the local applications of the tablet computer and the desktop applications of the mobile phone P40 are arranged together and displayed in tabs according to the desktop application layout of the mobile phone P40.

[0345] Example 62: FIG14(e) is a schematic diagram showing a super desktop layout on a tablet computer (e.g., MatePad 1). Since a tablet computer is a device that is easy to interact with accurately, when displaying the desktop application of the mobile phone P40 on the tablet computer, there is no need to filter it by the tablet computer system or user, and as many desktop applications of the mobile phone P40 as possible can be displayed. As shown in FIG14(e), this is a schematic diagram showing the desktop application of the mobile phone P40 on a tablet computer when the desktop style of the mobile phone P40 is a drawer-style desktop. The local applications of the tablet computer and the desktop applications of the mobile phone P40 are arranged together and displayed in tabs according to the desktop layout of the tablet computer.

[0346] Example 63: FIG14(f) is a schematic diagram showing a super desktop layout on a PC. Since a PC is a device that allows for easy and precise interaction, when displaying the desktop applications of the mobile phone P40 on a PC, there is no need for PC system or user screening, and as many desktop applications of the mobile phone P40 as possible can be displayed according to the desktop layout of the mobile phone P40. As shown in FIG14(f), when the desktop style of the mobile phone P40 is a standard-style desktop, the local applications of the tablet computer and the desktop applications of the mobile phone P40 are arranged together and displayed in tabs according to the desktop application layout of the mobile phone P40.

[0347] Example 64: FIG14(g) is a schematic diagram showing a super desktop layout on a PC. Since a PC is a device that allows for easy and precise interaction, when displaying the desktop applications of a mobile phone P40 on a PC, there is no need for PC system or user screening, and as many desktop applications of the mobile phone P40 as possible can be displayed. As shown in FIG14(g), when the desktop style of the mobile phone P40 is a drawer-style desktop, the desktop applications of the PC and the desktop applications of the mobile phone P40 are arranged together and displayed in tabs according to the desktop layout of the PC.

[0348] In the embodiment of the present application, different forms of super desktop entrances are provided for different devices.

[0349] For example, for a device with a drawer-style desktop (such as a car computer, a PC, etc.), the local applications of the device and the super desktop are arranged together and displayed in tabs, as shown in Figures 14(b) and 14(f).

[0350] For devices that do not have a drawer-style desktop (such as tablets, large-screen devices, etc.), slide the desktop of the device to the last screen, and the one displayed alone is the super desktop.

[0351] Another example: a device with a drawer-style desktop provides an "all apps" icon on the Dock. When the user clicks the icon, the user enters the super desktop, where the local applications of the device and the desktop applications of other devices are displayed together in tabs.

[0352] For devices that do not have a drawer-style desktop, an "other terminal application center" icon is provided on the Dock. When the user clicks the icon, they enter the super desktop, where the super desktop displays the desktop applications of other terminal devices. Optionally, the local applications of the device and the desktop applications of other devices are displayed together in tabs.

[0353] The following is an explanation with specific examples:

[0354] Example 65: Figure 14(h) is a schematic diagram of the super desktop entrance form on a tablet computer. Since the tablet computer does not have a drawer-style desktop, the user can slide the tablet computer's desktop, as shown in Figure 14(h). For example, the user can slide the tablet computer's desktop to the left, right, or downward, and the super desktop will be displayed on the last screen of the tablet computer's desktop. As shown in Figure 14(i), the tablet computer's local applications and other device desktop applications are displayed together in tabs.

[0355] Example 66: Figure 14(j) is a schematic diagram of the super desktop entrance form on a large-screen device. Since the large-screen device does not have a drawer-style desktop, as shown in Figure 14(j), for example, after the user flips the page to the left, right or down on the main interface of the large-screen device, the super desktop interface will be displayed on the large-screen device. As shown in Figure 14(k), the local applications of the large-screen device and the desktop applications of other devices are placed together and displayed in tabs.

[0356] Example 67: FIG14(l) is a schematic diagram of the super desktop entrance on a PC device. Since the PC device has a drawer-style desktop, as shown in FIG14(l), an "all applications" icon can be provided on the Dock of the PC device. After the user clicks the icon, the user enters the super desktop. As shown in FIG14(m), in the super desktop displayed by the PC device, the local applications of the PC device and the desktop applications of other devices are displayed together in tabs.

[0357] Example 68: FIG. 14(n) is a schematic diagram of the super desktop entrance on the car computer. Since the car computer has a drawer-style desktop, as shown in FIG. 14(n), an "All Apps" icon can be provided on the Dock of the car computer. After the user clicks the icon, the super desktop is entered. As shown in FIG. 14(o), in the super desktop displayed on the car computer, the local applications on the car computer and the desktop applications of other devices are displayed together in tabs.

[0358] Example 69: FIG. 14(p) is a schematic diagram of the super desktop entrance on a tablet computer. Since a tablet computer does not have a drawer-style desktop, an icon of an "other terminal application center" can be provided on the Dock of the tablet computer. For example, other terminal devices include a mobile phone P40. After the user clicks the icon, he enters the super desktop. As shown in FIG. 14(q), in the super desktop displayed by the tablet computer, the local applications of the tablet computer and the desktop applications of other devices (including the mobile phone P40) are displayed together in tabs.

[0359] Example 70: FIG14(r) is a schematic diagram of the super desktop entrance form on a large-screen device. Since the large-screen device does not have a drawer-style desktop, as shown in FIG14(r), an "other terminal application center" icon can be provided on the Dock of the large-screen device. For example, the other terminal devices include the mobile phone P40. After the user clicks the icon, he enters the super desktop. As shown in FIG14(s), in the super desktop displayed on the large-screen device, the local applications of the large-screen device and the desktop applications of other devices (including the mobile phone P40) are displayed together in tabs.

[0360] In the embodiment of the present application, when the super desktop is displayed on the vehicle computer, the user can click on the application icon of other devices on the super desktop, and after clicking the application icon of other devices, the application can be displayed on the vehicle computer. For example, the application can be displayed on the vehicle computer in a floating window, split screen, full screen, or covering the vehicle computer desktop, which will be explained in conjunction with specific examples below.

[0361] Example 71: Figure 15(a) shows a schematic diagram of the interface before the car computer has established a trusted connection with other devices, and there are no icons of other devices on the car computer's Dock. Figure 15(b) shows a schematic diagram of the interface after the car computer has established a trusted connection with the mobile phone P40, and the icon of the mobile phone P40 is displayed on the car computer's Dock. The user can click on the icon, and the result is shown in Figure 15(c), and the super desktop will be displayed on the car computer. In the super desktop displayed on the car computer, the local applications on the car computer and the desktop applications of other devices are displayed together in tabs.

[0362] Example 72: The user can click on any application on the desktop of the mobile phone P40 in the interface shown in Figure 15(c). Assuming that the application clicked by the user is APP1, after the user clicks the icon of APP1, APP1 will be displayed on the car computer.

[0363] As a possible implementation, in the interface shown in FIG15(c), when the user clicks the icon of APP1, the APP1 will be displayed in the form of a floating window on the vehicle computer, such as shown in FIG15(d). Optionally, there may also be a "full screen button" on the interface displayed in the floating window, and when the user clicks the "full screen button", the APP1 will be displayed in the form of a full screen on the vehicle computer, as shown in FIG15(e).

[0364] As another possible implementation, in the interface shown in FIG15(c), when the user clicks on the icon of an APP (for example, APP1), the APP1 will be displayed in a split screen on the vehicle computer, as shown in FIG15(f). The split screen is a split screen display of APP1 and the desktop of the vehicle computer on the display screen of the vehicle computer. Optionally, there may be a "full screen button" on the split screen display interface of the APP1. After the user clicks the "full screen button", the APP1 will be displayed in a full screen on the vehicle computer, as shown in FIG15(e).

[0365] As another possible implementation, in the interface shown in FIG. 15( c ), when the user clicks the icon of APP1 , APP1 will be displayed in full screen on the vehicle computer, as shown in FIG. 15( e ).

[0366] Example 73: In the interface shown in FIG15(b), the user can click the icon of the mobile phone P40 on the dock of the vehicle computer. After clicking the icon, the display result is shown in FIG15(g), and the super desktop is displayed on the vehicle computer. In the super desktop displayed on the vehicle computer, the display method of the desktop application icons of the mobile phone P40 can be the same as the desktop layout of the mobile phone P40. Optionally, as shown in FIG15(g), the desktop application icons of the mobile phone P40 can be displayed on the display screen of the vehicle computer in a split screen with the desktop of the vehicle computer.

[0367] Optionally, in an embodiment of the present application, on a device that displays applications in full screen by default, after opening an application on the super desktop, the newly opened application is displayed in full screen on the device; under the premise of satisfying the split-screen requirement, open the application on the super desktop and display the newly opened application in split screen on the device.

[0368] Optionally, after opening the super desktop application on a device that displays a floating window by default, such as a computer (such as a PC), the newly opened application is displayed in a floating window on the device, and the floating window adaptation rule of the device is followed to display the new application in a vertical or narrow floating window, or a horizontal or wide floating window. This application is not limited here.

[0369] In the embodiment of the present application, two or more terminal devices with the same or different accounts can form a temporary super desktop by "touch" or "scan", or temporarily disconnect (close) the super desktop, etc. The following will be explained with reference to specific examples.

[0370] Example 74: Assume that a trusted relationship has been established between the mobile phone P40 used by the user and the vehicle computer of the vehicle driven by the user, and a super desktop has been established before. After the user gets in the car and starts the car, the super desktop will be automatically established between the mobile phone P40 and the vehicle computer, as shown in Figure 16 (a), and the super desktop will be displayed on the vehicle computer. In this case, the user can use the mobile phone P40 to temporarily close the super desktop by "touch" or "scan". For example, after "touch" or "scan", as shown in Figure 16 (b), a pop-up prompt "Disconnect sharing" can be displayed on the mobile phone P40. After the user clicks "Disconnect sharing", the mobile phone P40 will disconnect the desktop sharing with the vehicle computer, as shown in Figure 16 (c), and the super desktop will be exited on the vehicle computer. The super desktop will no longer be displayed on the vehicle computer, and the main interface of the vehicle computer will be displayed.

[0371] After the user closes the super desktop, the next time the user gets in the car and starts the car, the super desktop will be automatically established between the mobile phone P40 and the car computer, or the super desktop can be temporarily established by "touch" or "scan". For example, as shown in Figure 16 (d), a pop-up prompt "Start sharing" can be displayed on the mobile phone P40. After the user clicks "Start sharing", the mobile phone P40 will share the desktop with the car computer, and the interface displayed by the car computer will change from the interface shown in Figure 16 (c) to the interface shown in Figure 16 (e), that is, the super desktop is displayed.

[0372] Optionally, in the above process of temporarily setting up and closing the super desktop, the switch of the super desktop in the settings is not affected.

[0373] Optionally, when a user creates a super desktop for the first time or each time a super desktop is created, there may be an application management interface, in which the user can make selections so that certain applications selected by the user can participate in the display of the super desktop, while unselected applications will not appear on the super desktop. This will be explained below with reference to specific examples.

[0374] Example 75: Assume that a mobile phone and a large-screen device, or a mobile phone and a car computer need to form a super desktop. After the user turns on the "super desktop" switch on the mobile phone, the user can search and add trusted devices around him in various ways (for example, by "touch" or "scan"). After the mobile phone searches for the car computer or the large screen, the interface displayed on the mobile phone may be as shown in Figure 16 (f). The user clicks on the device that needs to form a super desktop, for example, selects "Huawei Car Super Desktop". After the user clicks "Huawei Car Super Desktop", the displayed interface is as shown in Figure 16 (g). The user can select applications on this interface, and the applications selected by the user will be displayed on the car computer super desktop.

[0375] Example 76: Assuming that a mobile phone and a tablet computer (such as MatePad), or a mobile phone and a personal PC need to form a super desktop, after the user turns on the "super desktop" switch on the mobile phone, the user can search and add surrounding trusted devices in various ways (such as by "touch" or "scan"). After the mobile phone searches for the car machine or large screen, the interface displayed by the mobile phone can be as shown in Figure 16 (h). In this case, the user does not need to filter the applications, that is, all applications on the mobile phone can be displayed on the super desktop of the personal PC or tablet by default. The user clicks on the device for which the super desktop needs to be formed, for example, selects "MatePad Super Desktop". After the user clicks "MatePad Super Desktop", the super desktop can be displayed on the MatePad, and all applications on the mobile phone can be displayed on the MatePad.

[0376] It should be understood that in this application, the above-mentioned examples and interfaces of the terminal, the user's operations, etc. are merely illustrative and do not constitute specific limitations of the embodiments of this application. For example, in some other embodiments of this application, the icons on the interfaces displayed by the above-mentioned terminals may include more or fewer icons than those displayed on the interfaces shown in any of the above figures, or combine certain icons, or split certain icons, or different icons, etc. The embodiments of this application are not limited here.

[0377] Fig.17 The schematic diagram of the structure of an example terminal device 300 provided in the present application is shown, and the terminal device can be any terminal in the above-mentioned embodiments (for example, a mobile phone, a large-screen device, a tablet computer, a PC, a folding-screen mobile phone, a car machine, a light device, etc.), such as Fig.17 As shown, the device terminal 300 may include a processor 310, an external memory interface 320, an internal memory 321, a universal serial bus (USB) interface 330, an antenna 1, an antenna 2, a mobile communication module 350, a wireless communication module 360, an audio module 370, a speaker 370A, a receiver 170B, a microphone 370C, an earphone interface 370D, a sensor module 380, etc. The terminal device is used to perform the steps performed by any terminal in the above task examples or any interface displayed.

[0378] It is to be understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the terminal device 300. In other embodiments of the present application, the terminal device 300 may include more or fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0379] The processor 310 may include one or more processing units, for example, the processor 310 may include an application processor (AP), a modem processor, a graphics processor (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

[0380] The processor 310 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 310 is a cache memory. The memory may store instructions or data that the processor 310 has just used or cyclically used. If the processor 310 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, reduces the waiting time of the processor 310, and thus improves the efficiency of the system.

[0381] The wireless communication function of the terminal device 300 can be implemented through antenna 1, antenna 2, mobile communication module 350, wireless communication module 360, modem processor and baseband processor.

[0382] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in terminal device 300 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve the utilization of antennas. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In some other embodiments, the antenna can be used in combination with a tuning switch.

[0383] The mobile communication module 350 can provide solutions for wireless communications including 2G / 3G / 4G / 5G applied to the terminal device 300. The mobile communication module 350 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 350 can receive electromagnetic waves from the antenna 1, and filter, amplify, and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 350 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 350 can be set in the processor 310. In some embodiments, at least some of the functional modules of the mobile communication module 350 can be set in the same device as at least some of the modules of the processor 310.

[0384] The wireless communication module 360 ​​can provide wireless communication solutions including wireless local area networks (WLAN) applied on the terminal device 300, such as wireless fidelity (Wi-Fi) network, bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR) and the like. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 360 ​​receives electromagnetic waves via the antenna 2, modulates the electromagnetic wave signal and performs filtering, and sends the processed signal to the processor 310. The wireless communication module 360 ​​can also receive the signal to be sent from the processor 310, modulate the frequency, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

[0385] In some embodiments, the antenna 1 of the terminal device 300 is coupled to the mobile communication module 350, and the antenna 2 is coupled to the wireless communication module 360, so that the terminal device 300 can communicate with the network and other devices through wireless communication technology. The wireless communication technology may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time division code division multiple access (TD-SCDMA), LTE, BT, GNSS, WLAN, NFC, FM, and / or IR technology, etc. The GNSS may include global positioning system (GPS), global navigation satellite system (GLONASS), Beidou navigation satellite system (BDS), quasi-zenith satellite system (QZSS) and / or satellite-based augmentation system (SBAS).

[0386] The terminal device 300 implements the display function through a GPU, a display screen 394, and an application processor. The GPU is a microprocessor for image processing, which connects the display screen 394 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 310 may include one or more GPUs, which execute program instructions to generate or change display information.

[0387] The display screen 394 is used to display images, videos, etc. The display screen 394 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode or an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), Miniled, MicroLed, Micro-oLed, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the terminal device 300 may include 1 or N display screens 394, where N is a positive integer greater than 1.

[0388] The terminal device 300 can realize the shooting function through ISP, camera 393, video codec, GPU, display screen 394 and application processor.

[0389] The ISP is used to process the data fed back by the camera 393. For example, when taking a photo, the shutter is opened, and the light is transmitted to the camera photosensitive element through the lens. The light signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to the ISP for processing and converts it into an image visible to the naked eye. The ISP can also perform algorithm optimization on the noise, brightness, and skin color of the image. The ISP can also optimize the exposure, color temperature and other parameters of the shooting scene. In some embodiments, the ISP can be set in the camera 393.

[0390] The camera 393 is used to capture still images or videos. The object generates an optical image through the lens and projects it onto the photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, and then passes the electrical signal to the ISP to be converted into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV or other format. In some embodiments, the terminal device 300 may include 1 or N cameras 393, where N is a positive integer greater than 1.

[0391] The digital signal processor is used to process digital signals. In addition to processing digital image signals, it can also process other digital signals. For example, when the terminal device 300 is performing frequency selection, the digital signal processor is used to perform Fourier transform on the frequency energy.

[0392] Video codecs are used to compress or decompress digital videos. The terminal device 300 may support one or more video codecs. Thus, the terminal device 300 may play or record videos in multiple coding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

[0393] The external memory interface 320 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the terminal device 300. The external memory card communicates with the processor 310 through the external memory interface 320 to implement a data storage function. For example, files such as music and videos can be stored in the external memory card.

[0394] The internal memory 321 can be used to store computer executable program codes, which include instructions. The processor 310 executes various functional applications and data processing of the terminal device 300 by running the instructions stored in the internal memory 321. The internal memory 321 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area may store data created during the use of the terminal device 300 (such as audio data, a phone book, etc.), etc. In addition, the internal memory 321 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc.

[0395] The terminal device 300 can implement audio functions such as music playing and recording through the audio module 370, the speaker 370A, the receiver 370B, the microphone 370C, the earphone interface 370D, and the application processor.

[0396] The audio module 370 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signal. The audio module 370 can also be used to encode and decode audio signals. In some embodiments, the audio module 370 can be arranged in the processor 310, or some functional modules of the audio module 370 can be arranged in the processor 310.

[0397] The speaker 370A, also called a "speaker", is used to convert an audio electrical signal into a sound signal. The terminal device 300 can listen to music or listen to a hands-free call through the speaker 370A.

[0398] The receiver 370B, also called a "handset", is used to convert audio electrical signals into sound signals. When the terminal device 300 receives a call or voice message, the voice can be received by placing the receiver 170B close to the ear.

[0399] Microphone 370C, also called "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or sending a voice message, the user can make a sound by putting his mouth close to the microphone 370C to input the sound signal into the microphone 370C. The terminal device 300 can be provided with at least one microphone 370C. In other embodiments, the terminal device 300 can be provided with two microphones 370C, which can not only collect sound signals but also realize noise reduction function. In other embodiments, the terminal device 300 can also be provided with three, four or more microphones 370C to realize the collection of sound signals, noise reduction, identification of sound sources, realization of directional recording function, etc.

[0400] The earphone interface 370D is used to connect a wired earphone and can be a USB interface 330 or a 3.5 mm open mobile terminal platform (OMTP) standard interface or a cellular telecommunications industry association of the USA (CTIA) standard interface.

[0401] The sensor module 380 may include a pressure sensor, a gyroscope sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, and the like.

[0402] Of course, the terminal device 300 may also include a charging management module, a power management module, a battery, buttons, indicators, and one or more SIM card interfaces, etc., and the embodiments of the present application do not impose any restrictions on this.

[0403] Fig.18 A software structure block diagram of a terminal device according to an embodiment of the present application is shown.

[0404] The layered architecture divides the software into several layers, each with a clear role and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into five layers, from top to bottom: application layer, application framework layer, Android runtime and system library, hardware abstraction layer (HAL) ( Fig.18 Not shown in the figure), and the kernel layer.

[0405] The application layer can include a series of application packages.

[0406] like Fig.18 As shown, the application package may include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, game, shopping, travel, instant messaging (such as short message), etc. In addition, the application package may also include: main screen (i.e. desktop), negative one screen, control center, notification center and other system applications. In the embodiment of the present application, the application package may also include a super collection application, which may be a system application or a third-party application. The application package may also include an application of a task flow manager for calling and managing the task flow manager.

[0407] The Super Collection application provides a service or function that can support terminal devices to collect task data to a distributed database, and other electronic devices synchronize the task data to their own local task flow database based on the distributed database.

[0408] The application framework layer provides an application programming interface (API) and a programming framework for the applications in the application layer. The application framework layer includes some predefined functions.

[0409] like Fig.18 As shown, the application framework layer may include a task flow manager, a database management system DBMS, a local task flow database, a distributed database, a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, and the like.

[0410] The Task Flow Manager is used to manage the task flows in various applications, generate task data and publish tasks.

[0411] Database management system DBMS is a kind of software that manipulates and manages databases (including local task flow databases, distributed databases, etc.). It is used to establish, use and maintain databases, including interfaces for calling databases. DBMS manages and controls databases in a unified manner to ensure the security and integrity of the database. Users access data in the database through DBMS, and database administrators also perform database maintenance work through DBMS. DBMS provides a variety of functions that allow multiple applications and users to establish, modify and query databases at the same time or at different times using different methods. DBMS enables users to easily define and manipulate data, maintain data security and integrity, and perform concurrent control and database recovery under multiple users.

[0412] The local task flow database is used to store local task data.

[0413] A distributed database is a logically unified database formed by connecting multiple physically dispersed database units using a computer network. Each connected database unit is called a site or node. A distributed database has a unified database management system to manage it, which is called a distributed database management system.

[0414] In some embodiments, the distributed database is an optional module in the terminal device, and the distributed database of the terminal device can be installed on other servers or in the cloud.

[0415] In the embodiment of the present application, the super collection application of the terminal device calls the client of the task flow manager (the application of the task flow manager) to register the task monitoring service with the local task flow database. The client of the task flow manager calls the interface of the database management system DBMS to register the task monitoring service with the task flow manager. The task monitoring service is used when the task flow manager detects that there is a change in the task data in the local task flow database (such as addition, deletion, modification), and the task flow manager synchronizes the changed task data to the super collection application.

[0416] The input manager is used to receive instructions or requests reported by lower layers such as the kernel layer and the hardware abstraction layer.

[0417] The window manager is used to manage window programs. The window manager can obtain the display screen size, determine whether there is a status bar, lock the screen, capture the screen, etc.

[0418] The activity manager is used to manage the activities running in the system, including processes, applications, services, tasks, etc.

[0419] Content providers are used to store and retrieve data and make it accessible to applications. The data may include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

[0420] The view system includes visual controls, such as controls for displaying text and controls for displaying images. The view system can be used to build applications. The display interface of an application can be composed of one or more views. For example, the display interface of a text notification icon can include a view for displaying text and a view for displaying images.

[0421] The display manager is used to transmit display content to the kernel layer.

[0422] The phone manager is used to provide communication functions for terminal devices, such as the management of call status (including answering, hanging up, etc.).

[0423] The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, and so on.

[0424] The notification manager enables applications to display notification information in the status bar. It can be used to convey notification-type messages and can disappear automatically after a short stay without user interaction. For example, the notification manager is used to notify download completion, message reminders, etc. The notification manager can also be a notification that appears in the system top status bar in the form of a chart or scroll bar text, such as notifications of applications running in the background, or a notification that appears on the screen in the form of a dialog window. For example, a text message is displayed in the status bar, a prompt sound is emitted, an electronic device vibrates, an indicator light flashes, etc.

[0425] Android Runtime includes core libraries and virtual machines. Android runtime is responsible for scheduling and management of the Android system.

[0426] The core library consists of two parts: one part is the function that needs to be called by the Java language, and the other part is the Android core library.

[0427] The application layer and the application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and the application framework layer as binary files. The virtual machine is used to perform functions such as object life cycle management, stack management, thread management, security and exception management, and garbage collection.

[0428] The system library may include multiple functional modules, such as surface manager, media libraries, 3D graphics processing library (such as OpenGL ES), 2D graphics engine (such as SGL), etc.

[0429] The surface manager is used to manage the display subsystem and provide the fusion of 2D and 3D layers for multiple applications.

[0430] The media library supports playback and recording of a variety of commonly used audio and video formats, as well as static image files, etc. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

[0431] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0432] A 2D graphics engine is a drawing engine for 2D drawings.

[0433] The hardware abstraction layer HAL layer is the interface layer between the operating system software and the hardware components, which provides an interface for the interaction between the upper-layer software and the lower-layer hardware. The HAL layer abstracts the underlying hardware into software containing the corresponding hardware interface. By accessing the HAL layer, the settings of the underlying hardware devices can be realized, for example, the related hardware components can be enabled or disabled at the HAL layer. In some embodiments, the core architecture of the HAL layer is composed of at least one of C++ or C.

[0434] The kernel layer is the layer between hardware and software. The kernel layer includes at least display driver, camera driver, audio driver, sensor driver, touch chip driver and input system. For the sake of explanation, Fig.17 In the embodiment, the kernel layer is illustrated by taking the input system, the driver of the touch chip, the display driver and the storage driver as an example. The display driver and the storage driver can be set together in the driver module.

[0435] It is to be understood that the structure illustrated in the present application does not constitute a specific limitation on the terminal device. In other embodiments, the terminal device may include more or fewer components than shown in the figure, or combine certain components, or split certain components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware. The present application does not limit this.

[0436] Based on the above application scenarios and Figure 1 The system architecture shown in the figure and the above examples are described below. The steps of the display and control method of the remote device task provided by the present application are described below. Fig.19 , Fig.19 A flowchart of a method for displaying and controlling a remote device task provided by the present application is shown, wherein the devices involved in the flowchart of the method include a first terminal and a second terminal, and the first terminal and the second terminal are mutually trusted devices.

[0437] like Fig.19 As shown, this embodiment includes the following steps:

[0438] S1010: The first terminal displays a recent task interface, where icons of N devices and at least one task card are displayed, and the N devices include the first terminal and the second terminal.

[0439] S1020: When displaying the task cards of the second terminal in the recent task interface of the first terminal, according to the user's usage status of the second terminal, the task cards of the second terminal are arranged in the recent task interface of the first terminal.

[0440] Optionally, the user's usage status of the second terminal includes: landscape screen usage status, portrait screen usage status, expanded portrait screen usage status of the foldable screen, expanded landscape screen usage status of the foldable screen, folded landscape screen usage status of the folded screen, and folded portrait screen usage status.

[0441] In a possible implementation, the first terminal displays the task cards of the second terminal in a single row or multiple rows in the recent task interface of the first terminal according to any one of the following: when the second terminal is used in landscape mode, when the second terminal is used in portrait mode, when the folding screen is used in a vertical state, when the folding screen is used in a horizontal state, when the folding screen is used in a horizontal state, and when the folding screen is used in a vertical state. For example, the specific descriptions corresponding to Figures 4(a), 4(b), and Example 1 (Figure 5(a)) to Example 3 (Figure 6(e)) can be referred to, and for the sake of brevity, they are not repeated here. In this implementation, the task cards of the second terminal are displayed in a single row or multiple rows in the recent task interface of the first terminal by utilizing the user's usage status of the second terminal, the user's usage status of the first terminal, and the screen size of the first terminal, so as to improve the efficiency of the display of the task cards of the second terminal, facilitate users to view and manage historical tasks of other devices on one device, and improve user experience.

[0442] In a possible implementation, when a task card of the second terminal is displayed in the recent task interface of the first terminal, the task card of the second terminal includes a task card of the first screen snapshot of the desktop of the second terminal. In this implementation, the desktop snapshot of the second terminal can be displayed in the recent task interface of the first terminal, which is convenient for the user to view and improves the user experience.

[0443] In a possible implementation, the method further includes: the first terminal receives a first operation of a user on a task card of a first screenshot of the desktop of the second terminal; and the first terminal displays the task card of the second screenshot of the desktop of the second terminal in a recent task interface of the first terminal according to the first operation of the user. For example, the specific description corresponding to Example 5 can be referred to, and for the sake of brevity, it is not repeated here. In this implementation, the user can view snapshots of different desktops of the second terminal to improve the user experience.

[0444] In a possible implementation, the method further includes: the first terminal receives a second operation of the user on a task card of a first screen snapshot of the desktop of the second terminal or a task card of a second screen snapshot of the desktop of the second terminal; the first terminal displays the interface of the first screen of the desktop of the second terminal or the interface of the first screen of the desktop of the second terminal on the first terminal according to the second operation, or runs an application on the first screen interface of the desktop of the second terminal or an application on the second screen interface of the desktop of the second terminal on the first terminal. For example, the specific description corresponding to Example 5 can be referred to. In this implementation, the user can operate the application of different desktop snapshots of the second terminal to quickly display or open the application on the local machine, which is simple to operate and improves the user experience.

[0445] In a possible implementation, at least one of a FA card, a floating window, and a floating ball exists on the task card of the first screenshot of the desktop of the second terminal and / or on the task card of the second screenshot of the desktop of the second terminal. For example: you can refer to the specific descriptions corresponding to Example 4, Example 6, and Example 7, which will not be repeated here for the sake of brevity. In this implementation, a FA card, a floating window, or a floating ball can be displayed on the desktop snapshot of the second terminal, and the task card of the second terminal can be flexibly displayed in the recent task interface of the first terminal in different ways, thereby improving the user experience.

[0446] In a possible implementation, the method further includes: the first terminal receives a third operation of the user on the FA card, floating window, or floating ball; the first terminal displays the first screen interface of the second terminal desktop or the first screen interface of the second terminal desktop on the first terminal according to the third operation, or runs the application corresponding to the FA card, the floating window, or the floating ball on the first terminal. In this implementation, the user can operate the FA card, floating window, or floating ball on the second terminal desktop snapshot to quickly display or open the application on the local computer, which is simple to operate and improves the user experience.

[0447] In a possible implementation, when a task card of a second terminal is displayed in a recent task interface of a first terminal, the task card of the second terminal includes a snapshot of a control device for controlling the second terminal. In this implementation, task cards related to the second terminal can be flexibly displayed in the recent task interface of the first terminal, thereby improving user experience.

[0448] In a possible implementation, the method further includes: the first terminal receives a fourth operation of the user on the snapshot of the control device; the first terminal displays the detail interface of the control device on the first terminal, or remotely controls the second terminal according to the fourth operation. For example: refer to the specific description shown in Example 8, which will not be repeated here for the sake of brevity. In this implementation, the user can view the task card of the control device that controls the second device on the first terminal, and can operate the task card to quickly control the second terminal device on the local machine, which is simple to operate and improves the user experience.

[0449] For example, the second terminal is a large-screen device, and the control device is a remote controller.

[0450] In a possible implementation, when the task card of the second terminal is displayed in the recent task interface of the first terminal, the task card of the second terminal includes: a task card of a desktop application of the second terminal.

[0451] In a possible implementation, the method further includes: the first terminal receives a fifth operation of the user on the application on the task card of the desktop application of the second terminal; the first terminal manages the desktop application of the second terminal on the first terminal according to the fifth operation. For example: the specific description shown in Example 10 can be referred to, and for the sake of brevity, it is not repeated here. In this implementation, the user can view the desktop application icon of the second terminal on the first terminal, and can operate the desktop application icon to help the second terminal manage the application (sort, create folders, delete, etc.), so as to quickly help the second terminal manage the application on the local machine, with simple operation and improved user experience.

[0452] In a possible implementation, the N devices include light devices, and the light devices include wearable devices and smart home devices used by users. When the task cards of the light devices are displayed in the recent task interface of the first terminal, the task cards of the light devices include task cards corresponding to the tasks being run by different light devices. In this implementation, the task cards of the light devices can be displayed in the recent task interface of the first terminal, which enriches the types of task cards displayed in the recent task interface of the first terminal and is more user-friendly.

[0453] Exemplarily, light devices are a general term for IoT devices, wearable devices, smart home devices, etc. For example, light devices may include: smart refrigerators, smart air conditioners, smart cooking pots, smart range hoods, smart speakers, smart watches, etc.

[0454] In a possible implementation, the method further includes: the first terminal receives a sixth operation of the user on the task card of the device; the first terminal displays a detailed interface of the task being run by the light device on the first terminal according to the sixth operation, or remotely controls the task being run by the light device. Figure 7(g) to Figure 7(o) In the implementation mode, the user can view the task card corresponding to the task being run by the associated light device on the first terminal, and can operate the card corresponding to the task being run by the light device, so as to remotely control the task being run by the light device, which is simple to operate and improves the user experience.

[0455] In a possible implementation, the N devices include a third terminal, and the method further includes: the first terminal receives the seventh operation of the user on the task card of the light device; the first terminal shares the task card of the light device to the third terminal according to the seventh operation; and the third terminal displays the task card of the light device in the recent task interface. In this implementation, the task card of the light device can be pushed to the third terminal for display, which is convenient for the user to control the task being run by the light device on the third terminal, and the user experience can be improved.

[0456] In a possible implementation, the method further includes: displaying a task card corresponding to the task being run by the second light device on the display interface of the first light device, the light device including the first light device and the second light device; the first light device receives the eighth operation of the user on the task card corresponding to the task being run by the second light device; the first light device remotely controls the task being run by the second light device according to the eighth operation. For example, please refer to the specific description shown in Example 11, which will not be repeated here for the sake of brevity. In this implementation, users can remotely control the tasks being run by other light devices on the light device, which is simple to operate and improves the user experience.

[0457] In a possible implementation, the method further includes: verifying the identity of the user through the first light device, and / or a device associated with the first light device; after the user's identity authentication is passed, displaying the task card of the first terminal and / or the second terminal on the display interface of the first light device.

[0458] In a possible implementation, the method further includes: the first light device receives the ninth operation of the user on the task card of the first terminal and / or the second terminal; the first light device remotely controls the application corresponding to the task card of the first terminal and / or the second terminal according to the ninth operation. For example, you can refer to the specific description shown in Example 12, which will not be repeated here for the sake of brevity. In this implementation, the user can remotely control the historical task cards and foreground task cards of other smart terminals on the light device, which is simple to operate and improves the user experience.

[0459] In a possible implementation, the method further includes: when displaying the task card of the second terminal in the recent task interface of the first terminal, receiving the tenth operation of the user on the first task card in the task card of the second terminal, the tenth operation is used to pull up the first application corresponding to the first task card on the first terminal; the first terminal runs the first application on the first terminal according to the tenth operation; the first terminal and the second terminal determine the running state of the first application according to the different modes of migration of the first application to the first terminal. For example, the specific description corresponding to FIG8(a) can be referred to, and for the sake of brevity, it will not be repeated here. In this implementation, after pulling up the application of other terminals, the first terminal can determine and display the running state of the application on the first terminal according to the different modes of migration of the application to the first terminal, thereby ensuring the efficiency of the application running on the first terminal, thereby improving the user experience.

[0460] In a possible implementation, the first terminal and the second terminal determine the running state of the first application according to different modes of the first application migration to the first terminal, including: when the first application is migrated to the first terminal using the copy mode, the first terminal and the second terminal independently run the first application, the data of the first application on the first terminal and the second terminal are synchronized, the operation state is synchronized, and the first terminal and the second terminal respectively display the first application according to their respective screen adaptations. For example, the specific description corresponding to Example 13 can be referred to, and for the sake of brevity, it will not be repeated here.

[0461] In a possible implementation, the method further includes: the second terminal receives the eleventh operation of the user on the first application, and the eleventh operation is used to pull back the first application from the first terminal; after the second terminal receives the eleventh operation, the first terminal continues to run the first application. For example, the specific description corresponding to Example 16 can be referred to, and for the sake of brevity, it is not repeated here. In this implementation, the normal operation of the first application can be guaranteed.

[0462] In a possible implementation, the first terminal and the second terminal determine the running state of the first application according to different modes of the first application migrating to the first terminal, including: when the first application is migrated to the first terminal using the migration mode of the window projection technology, and the first application supports multiple instances, the first terminal and the second terminal run the first application independently, the data of the first application on the first terminal and the second terminal are synchronized, the operation state is not synchronized, and the first terminal and the second terminal respectively display the first application according to their respective screen adaptations. For example, the specific description corresponding to Example 14 can be referred to, and for the sake of brevity, it will not be repeated here.

[0463] In a possible implementation, the method further includes: the second terminal receives a twelfth operation of the user on the first application, the twelfth operation is used to pull back the first application from the first terminal; after the second terminal receives the twelfth operation, the first terminal continues to run the first application. For example, the description corresponding to Example 15 can be referred to, and for the sake of brevity, it is not repeated here.

[0464] In one possible implementation, the first terminal and the second terminal determine the running status of the first application according to different modes of migration of the first application to the first terminal, including: when the first application is migrated to the first terminal in a migration mode using window projection technology and the first application does not support multiple instances, the first terminal or the second terminal runs the first application in the same time period.

[0465] In a possible implementation, the method further includes: the second terminal receives a thirteenth operation of the user on the first application, the thirteenth operation is used to pull back the first application from the first terminal; after the second terminal receives the thirteenth operation, the first terminal exits the first application, and the second terminal runs the first application. For example, the description corresponding to Example 15 can be referred to, and for the sake of brevity, it is not repeated here.

[0466] In a possible implementation, the first terminal and the second terminal determine the running state of the first application according to different modes of the first application migration to the first terminal, including: when the first application is migrated to the first terminal using the migration mode of FA technology, before the first terminal runs the first application, the first terminal installs the first application or the FA of the first application; the first terminal and the second terminal independently run the first application, the data of the first application on the first terminal and the second terminal are synchronized, the operation state is not synchronized, and the first terminal and the second terminal respectively display the first application according to their respective screen adaptations. For example, the description corresponding to Example 14 can be referred to, and for the sake of brevity, it will not be repeated here.

[0467] In a possible implementation, the method further includes: the second terminal receives the fourteenth operation of the user on the first application, and the fourteenth operation is used to pull back the first application from the first terminal; after the second terminal receives the fourteenth operation, the first terminal continues to run the first application. For example, the description corresponding to Example 16 can be referred to, and for the sake of brevity, it is not repeated here. In this implementation, the normal operation of the first application can be guaranteed and the user experience can be improved.

[0468] In a possible implementation, the area of ​​the screen of the first terminal is larger than the area of ​​the screen of the second terminal. After the first application is pulled up on the first terminal, the first application is run on the first terminal, including: automatically displaying and running the first application in a floating window or full screen on the first terminal. For example, the description corresponding to Example 20 can be referred to, and for the sake of brevity, it is not repeated here. In this implementation, the first application can be displayed and run in a floating window or full screen on the first terminal to improve the user experience. For example, the first terminal can be a PC device.

[0469] In one possible implementation, the area of ​​the screen of the first terminal is larger than the area of ​​the screen of the second terminal. After the first application is pulled up on the first terminal, the method further includes: displaying a prompt message on the interface of the first terminal, the prompt message is used to prompt the user to display the first application in a floating window or full screen; the first terminal displays the first application in a floating window or full screen on the first terminal according to the user's choice. For example, you can refer to the description corresponding to Example 21, which will not be repeated here for the sake of brevity. In this implementation, the first application can be displayed and run in a floating window or full screen on the first terminal according to the user's choice to improve the user experience. For example, the first terminal can be a PC device.

[0470] In a possible implementation, after the first application is pulled up on the first terminal, the method further includes: when the screen width of the first terminal is greater than the screen width of the second terminal, the first application is displayed on the first terminal in a parallel view mode, and the first application is displayed on the second terminal in a non-parallel view mode; or, when the screen width of the first terminal is less than the screen width of the second terminal, the first application is displayed on the first terminal in a non-parallel view mode, and the first application is displayed on the second terminal in a parallel view mode; or, when the first application is displayed on the second terminal in a horizontal screen mode, the first application is displayed on the first terminal in a horizontal screen mode; or, when the first application is displayed on the second terminal in a vertical screen mode, the first application is displayed on the second terminal in a vertical screen mode. For example, the specific descriptions corresponding to Examples 17 to 19 can be referred to, and for the sake of brevity, they are not repeated here. In this implementation, the first application can be flexibly displayed and run in different forms according to the screen size of the first terminal and the second terminal to improve the user experience.

[0471] In a possible implementation, during the process of running the first application on the first terminal, the method further includes: after the distance between the first terminal and the second terminal is greater than a preset first distance, a first prompt message and a second prompt message are displayed on the interface of the first terminal, the first prompt message prompting the user that the first terminal and the second terminal will disconnect the communication connection, and the second prompt message prompting the user that the first application originates from the second terminal. For example, the specific description corresponding to Example 28 can be referred to, and for the sake of brevity, it will not be repeated here. In this implementation, by displaying the prompt message to the user, the user can be informed of the communication connection status, thereby improving the user experience.

[0472] In a possible implementation, during the process of running the first application on the first terminal, the method also includes: after the communication connection between the first terminal and the second terminal is disconnected, the first terminal uses a mask to display the first application, and an instruction among third prompt information, fourth prompt information and fifth prompt information is displayed on the interface of the first terminal; wherein the third prompt information prompts the user that the first terminal and the second terminal have disconnected the communication connection, the fourth prompt information prompts the user to exit the first application, and the fifth prompt information prompts the user to reconnect.

[0473] In a possible implementation, the method further includes: after the first terminal and the second terminal meet a preset condition, the first terminal and the second terminal are automatically reconnected; after the reconnection is successful, the first terminal resumes normal display and runs the first application. For example, you can refer to the specific description corresponding to Example 29, which will not be repeated here for the sake of brevity. In this implementation, by displaying connection status prompt information, automatic reconnection prompt information, and application exit prompt information to the user, and automatically reconnecting after the conditions are met, the sequential operation of task migration is guaranteed, thereby improving the user experience.

[0474] In a possible implementation, the method further includes: the first terminal receives a fifteenth operation of the user on the second task card in the recent task interface of the first terminal, the fifteenth operation is used to migrate the second application corresponding to the second task card to the target device for operation, and the N devices include the target device; the first terminal determines the target device according to the fifteenth operation; and the target device runs the second application. In this implementation, the user can conveniently determine the target device to which the task card needs to be migrated, the operation is simple and easy to implement, thereby improving the user experience.

[0475] In one possible implementation, the first terminal determines the target device according to the fifteenth operation, including: when the user long presses the second task card, the recent task interface of the first terminal hides the task cards other than the second task card and the icons of the device that cannot run the second application; the first terminal determines the target device from the device icons displayed in the recent task interface of the first terminal according to the user's operation. For example, please refer to the specific description corresponding to Example 30, which will not be repeated here for the sake of brevity. In this implementation, by hiding the icons of unavailable devices and other task cards, it is convenient for users to determine the target devices that need to be migrated to the task cards, thereby improving the efficiency of users in determining the target devices.

[0476] In a possible implementation, the first terminal determines the target device according to the fifteenth operation, including: when the user drags the second task card, and the second task card overlaps with the identification of the fourth terminal, determining that the fourth terminal is the target device, and the N devices include the fourth terminal. For example, the specific description corresponding to Example 32 can be referred to, and for the sake of brevity, it is not repeated here.

[0477] In one possible implementation, the first terminal determines the target device according to the fifteenth operation, including: when the user drags the second task card, and the second task card overlaps with the fourth terminal and the fifth terminal, the terminal device indicated by the device icon with the largest overlapping area is determined as the target device, and the N devices include the fourth terminal and the fifth terminal. For example, the specific description corresponding to Example 33 can be referred to, and for the sake of brevity, it will not be repeated here. In this implementation, the operation is simple, easy to implement, and the accuracy of determining the target device can be improved.

[0478] In one possible implementation, the first terminal determines the target device according to the fifteenth operation, including: when the user drags the second task card upward, and the distance moved by the second task card is greater than a preset distance, determining that the device indicated by the device icon directly above the second task card is the target device. For example, the specific description corresponding to Example 34 can be referred to, and for the sake of brevity, it will not be repeated here. In this implementation, the operation is simple, easy to implement, and the accuracy of determining the target device can be improved.

[0479] In one possible implementation, the first terminal determines the target device according to the fifteenth operation, including: when the user drags the second task card upward, and the distance between the second task card and the top of the first terminal screen is less than a preset distance, determining that the device indicated by the device icon directly above the second task card is the target device. For example, the specific description corresponding to Example 35 can be referred to, and for the sake of brevity, it will not be repeated here. In this implementation, the operation is simple, easy to implement, and the accuracy of determining the target device can be improved.

[0480] In one possible implementation, after the target device is determined, when the user drags the second task card to slide to the target device, as the distance between the second task card and the icon of the target device decreases, the area of ​​the second task card decreases. For example, the specific description corresponding to Example 31 can be referred to, and for the sake of brevity, it is not repeated here. In this implementation, the operation is simple, easy to implement, and the accuracy of determining the target device can be improved.

[0481] In one possible implementation, after determining the target device, the method further includes: when the second task card does not overlap with the icon of the target device, the icon of the target device moves downward by a preset distance, or the display state of the icon of the target device changes to a selected state. For example, reference may be made to the specific description corresponding to Example 37, which will not be repeated here for the sake of brevity. In this implementation, it is convenient for the user to view the selected target device, thereby improving the user experience.

[0482] In one possible implementation, after the target device is determined, the method further includes: when the user drags the second task card and the icon of the target device does not overlap, the user lets go, and the second task card automatically migrates to the target device; the target device runs the second application. For example, you can refer to the specific description corresponding to Example 36, which will not be repeated here for the sake of brevity. In this implementation, after the target device has been determined, but the task card has not yet reached the icon hotspot of the target device, if the user lets go at this time, the task card automatically flies to the device icon, completing the cross-device interaction, thereby improving the efficiency of the task cross-device interaction.

[0483] In a possible implementation, after determining the target device, the method further includes: the first terminal receives the user's sixteenth operation on the second task card in the recent task interface of the first terminal, and the sixteenth operation is used to select a new target device. For example, reference may be made to the specific descriptions corresponding to Examples 39 to 42, which will not be repeated here for the sake of brevity. In this implementation, the selected target device is changed by the user's operation on the task card, thereby improving the efficiency of changing the target device.

[0484] In one possible implementation, when the target device has a black screen, before the target device runs the second application, the method further includes: the target device automatically turns on the screen; after the target device automatically turns on the screen, an unlocking interface is displayed; and the target device receives the user's unlocking operation. For example, the specific description corresponding to Example 43 can be referred to, and for the sake of brevity, it will not be repeated here. In this implementation, the target device automatically turns on the screen, and after the screen turns on, unlocking is triggered, and then the user manually unlocks it, which ensures that the target device can run the migrated task normally, and ensures the efficiency of task migration.

[0485] In one possible implementation, when the target device has a black screen, before the target device runs the second application, the method further includes: the target device automatically lights up the screen and displays an unlocking interface; the target device receives the user's unlocking operation. For example, the specific description corresponding to Example 44 can be referred to, and for the sake of brevity, it will not be repeated here. In this implementation, the target device automatically lights up the screen, and after the screen lights up, the user is automatically triggered to manually unlock, thereby improving the efficiency of task migration while ensuring that the target device can run the migrated task normally.

[0486] In one possible implementation, when the target device has a black screen, before the target device runs the second application, the method further includes: the target device automatically lights up the screen and automatically unlocks the device. For example, the specific description corresponding to Example 45 may be referred to, and for the sake of brevity, it is not repeated here. In this implementation, the target device automatically lights up the screen and automatically unlocks the device, thereby improving the efficiency of task migration while ensuring that the target device can run the migrated task normally.

[0487] In a possible implementation, the source device corresponding to the second application is the first terminal, and the target device runs the second application, including: the target device uses the hardware capabilities of the first terminal to run the second application on the target device; or, the target device uses the hardware capabilities of the first terminal and the target device to run the second application on the target device; or, the target device uses the hardware capabilities of the target device to run the second application on the target device, and the first terminal releases the hardware capabilities occupied by the second application; or, the target device uses the hardware capabilities of the target device to run the second application on the target device, and the first terminal does not release the hardware capabilities occupied by the second application. For example, the specific descriptions corresponding to Examples 46 to 48 can be referred to, and for the sake of brevity, they are not repeated here. In this implementation, by different allocation rules for the hardware capabilities of the first terminal and the target device, it is ensured that the migrated tasks can run normally on the target device, thereby improving the efficiency of task migration.

[0488] In one possible implementation, the method further includes: during the process of the target device running the second application using the hardware capabilities of the target device, the target device receives an instruction to run a third application, and there is a conflict between the hardware capabilities used to run the third application on the target device and the hardware capabilities used to run the second application; the target device runs the third application using the hardware capabilities of the target device; the second application switches back to the first terminal device and continues to run the second application using the hardware capabilities of the first terminal. For example, reference may be made to the specific description corresponding to Example 49, which will not be repeated here for the sake of brevity. In this implementation, after the task is migrated from the source device to the target device, when facing the new task from the target device occupying the hardware, the source end hardware capabilities can be coordinated to ensure that the target device task is executed first, which can ensure that the target device task is executed first.

[0489] In one possible implementation, the method further includes: during the process of the target device using the hardware capabilities of the target device to run the second application, the target device receives an instruction to run a third application, and the hardware capabilities used to run the third application on the target device conflict with the hardware capabilities to run the second application; the target device uses the hardware capabilities of the target terminal to run the second application and the third application at the same time. For example, the specific description corresponding to Example 50 can be referred to, and for the sake of brevity, it will not be repeated here. In this implementation, in this implementation, after the task is migrated from the source device to the target device, when facing the new task from the target device occupying the hardware, the hardware capabilities of the target device can be separated according to the task, and multiple tasks can be supported at the same time, which can ensure that the tasks on the target device and the migrated tasks can run normally, thereby improving the efficiency of the task operation of the target device.

[0490] In a possible implementation, the method further includes: during the process of the target device running the second application using the hardware capabilities of the first terminal, the first terminal receives an instruction to run the fourth application, and there is a conflict between the hardware capabilities used to run the second application on the target device and the hardware capabilities used to run the fourth application on the first terminal; the target device suspends running the second application; the first terminal runs the fourth application using the hardware capabilities of the first terminal; after the first terminal finishes running the fourth application, the target device continues to run the second application using the hardware capabilities of the first terminal. For example, please refer to the specific description corresponding to Example 52, which will not be repeated here for the sake of brevity. In this implementation, after the task is migrated from the source device to the target device, when facing a new task from the source device occupying the hardware, the migrated task on the target device is suspended, and after the new task is finished on the source device, the migrated task on the target device automatically continues, which can ensure that the new task on the source device is executed first.

[0491] In a possible implementation, the method further includes: during the process of the target device running the second application using the hardware capabilities of the first terminal, the first terminal receives an instruction to run the fourth application, and there is a conflict between the hardware capabilities used to run the second application on the target device and the hardware capabilities used to run the fourth application by the first terminal; the target device switches to continue running the second application using the hardware capabilities of the target device, and the first terminal runs the fourth application using the hardware capabilities of the first terminal. For example, the specific description corresponding to Example 53 can be referred to, and for the sake of brevity, it will not be repeated here. In this implementation, in this implementation, after the task is migrated from the source device to the target device, when facing a new task from the source device that preempts the hardware, the source device uses its own hardware capabilities to execute the new task, and the target device uses its own hardware capabilities to execute the task migrated from the source device, which can ensure that the tasks on the source device and the migrated tasks can run normally, thereby improving the efficiency of task operation.

[0492] In a possible implementation, the method further includes: during the process of the target device using the hardware capabilities of the first terminal to run the second application, the first terminal receives an instruction to run the fourth application, and there is a conflict between the hardware capabilities used to run the second application on the target device and the hardware capabilities used to run the fourth application by the first terminal; the target device continues to run the second application using the hardware capabilities of the first terminal, and the first terminal uses the hardware capabilities of the first terminal to run the fourth application. For example, the specific description corresponding to Example 53 can be referred to, and for the sake of brevity, it will not be repeated here. In this implementation, in this implementation, after the task is migrated from the source device to the target device, when facing the new task from the source device occupying the hardware, the hardware capabilities of the source device can be separated according to the tasks, and multiple tasks can be supported at the same time, which can ensure that the tasks on the source device and the migrated tasks can run normally, thereby improving the efficiency of task running on the source device.

[0493] In a possible implementation, the method further includes: the first terminal receives the user's seventeenth operation on the fifth task card in the recent task interface of the first terminal, and the seventeenth operation is used to install the fifth application corresponding to the fifth task card on the first terminal or other devices among the N devices; the first terminal or other devices among the N devices install the fifth application according to the seventeenth operation. For example, you can refer to the specific description corresponding to Example 22 and Example 23, which will not be repeated here for the sake of brevity. In this implementation, the multi-device task center is used to help other devices or the current device install applications, which is easy to operate, improves the efficiency of application installation, and improves user experience.

[0494] In a possible implementation, the method also includes: the first terminal receives the user's eighteenth operation on the sixth task card and the seventh task card in the recent task interface of the first terminal, and the eighteenth operation is used to display the applications corresponding to the sixth task card and the seventh task card in the first display mode on the first terminal or other devices among the N devices; the first terminal or other devices among the N devices display the application corresponding to the sixth task card and the application corresponding to the seventh task card in the first display mode.

[0495] Optionally, the first display mode is: split-screen display mode; or, the application corresponding to the sixth task card is displayed in full screen, and the application corresponding to the seventh task card is displayed in a floating window; or, the application corresponding to the sixth task card is displayed in a floating window, and the application corresponding to the seventh task card is displayed in a floating window. For example, you can refer to the specific descriptions corresponding to Examples 24 to 27, which will not be repeated here for the sake of brevity. In this implementation, through the multi-device task center, the user can quickly switch to the local device or create a split-screen / floating window across devices. The operation is convenient and it is easy to form new task cards. In addition, the new task cards can have different display modes, which improves the diversity and flexibility of the task cards.

[0496] It should be understood that the above is only to help those skilled in the art better understand the embodiments of the present application, rather than to limit the scope of the embodiments of the present application. According to the above examples given, those skilled in the art can obviously make various equivalent modifications or changes. For example, some steps in each method of the above method may be unnecessary, or some new steps may be added. Or a combination of any two or any multiple embodiments of the above. Such modifications, changes or combined solutions also fall within the scope of the embodiments of the present application.

[0497] It should also be understood that the parameter codes in the above-mentioned embodiments are merely exemplary and should not impose any restrictions on the parameter code format carried by the information in the embodiments of the p...

Claims

1. A method for displaying and controlling a remote device task, characterized in that: The method is applied to a first terminal, the first terminal is in communication connection with a second terminal, and the method includes: The first terminal receives a first operation of a user, where the first operation is an operation of dragging a first task card; wherein the first task card is a task card corresponding to a first application of the first terminal; After the first operation is completed, the first terminal determines that the second terminal is a target device for migrating the first task card; The first terminal migrates the first task corresponding to the first task card to the second terminal for execution.

2. The method according to claim 1, characterized in that During the dragging process of the first task card, the first terminal displays the first task card and a second task card, where the second task card is a task card corresponding to a second application of the first terminal, and the first application and the second application are different.

3. The method according to claim 1 or 2, characterized in that: The first terminal displays a multitasking interface, wherein a plurality of task cards are displayed in the multitasking interface, wherein the plurality of task cards include the first task card, and the first operation is: an operation on the first task card in the multitasking interface.

4. The method according to any one of claims 1 to 3, characterized in that After the first operation is completed, the first terminal determines that the second device is a target device for migrating the first task card, including: After the first operation is completed, the first terminal receives a second operation of the user on the icon area of ​​the second terminal; In response to the second operation, the first terminal determines that the second terminal is a target device for migrating the first task card.

5. The method according to any one of claims 1 to 3, characterized in that The first operation is: dragging the first task card to an icon area of ​​the second terminal.

6. The method according to any one of claims 1 to 5, characterized in that After the first terminal determines that the second terminal is a target device for migrating the first task card, the state of the icon area of ​​the second terminal changes to a selected state.

7. The method according to any one of claims 1 to 6, characterized in that The first terminal migrating the first task corresponding to the first task card to the second terminal for execution includes: The first terminal synchronizes the running data of the first task in the first terminal to the second terminal, so that the running data of the first task on the second terminal is synchronized with the running data of the first task on the first terminal.

8. The method according to any one of claims 1 to 7, characterized in that The first terminal migrating the first task corresponding to the first task card to the second terminal for execution includes: The first terminal migrates the first task to the second terminal for execution through the window projection technology.

9. The method according to any one of claims 1 to 7, characterized in that The method is also applied to a system including the first terminal and the second terminal, wherein the first terminal migrates the first task corresponding to the first task card to the second terminal for execution, comprising: The second terminal runs a second application, wherein the second application is an application program on the second terminal corresponding to the first application; The second terminal runs the first task in the second application.

10. The method according to claim 9, characterized in that The interface layout of the second application executing the first task is different from the interface layout of the first application executing the first task.

11. The method according to any one of claims 1 to 10, characterized in that: The method is also applied to a system including the first terminal and the second terminal, and the method further includes: The first terminal receives a third operation performed by a user on the first application; In response to the third operation, the first application runs a second task on the first terminal, where the second task is different from the first task; When the first application runs the second task on the first terminal, the second terminal continues to run the first task.

12. The method according to any one of claims 1 to 10, characterized in that: The method is also applied to a system including the first terminal and the second terminal, and the method further includes: The first terminal receives a fourth operation performed by a user on a third application, where the third application is different from the first application; In response to the fourth operation, the third application runs a third task on the first terminal, where the third task is different from the first task; When the third application runs the third task on the first terminal, the second terminal continues to run the first task.

13. The method according to any one of claims 1 to 12, characterized in that: The first task is any one of: video playback, audio playback, picture browsing, video call, or voice call.

14. The method according to any one of claims 1 to 13, characterized in that: The first terminal and the second terminal log in to the same user account.

15. The method according to any one of claims 1 to 14, characterized in that The second terminal uses the hardware capabilities of the second terminal and / or the first terminal to run the first task on the second terminal.

16. The method according to any one of claims 1 to 15, characterized in that: The method is also applied to a system including the first terminal and the second terminal, and the method further includes: The second terminal receives a fifth operation of the user; In response to the fifth operation, migrating the first task from the second terminal to the first terminal for execution; The running data of the first task in the second terminal is synchronized to the first terminal, so that the running data of the first task on the second terminal is synchronized with the running data of the first task on the first terminal.

17. The method according to claim 16, characterized in that The fifth operation includes: An operation of dragging the first task card in the display interface of the second terminal.

18. The method according to any one of claims 1 to 15, characterized in that: The method further comprises: The first terminal receives a sixth operation of the user; In response to the sixth operation, migrating the first task from the second terminal to the first terminal for execution; The running data of the first task in the second terminal is synchronized to the first terminal, so that the running data of the first task on the second terminal is synchronized with the running data of the first task on the first terminal.

19. The method according to claim 18, characterized in that The sixth operation includes: Operation on the first task card in the display interface of the first terminal.

20. A system for displaying and controlling remote device tasks, characterized in that: The system includes N devices, the N devices include a first terminal and a second terminal, the first terminal and the second terminal are communicatively connected, the first terminal is used to execute the method executed by the first terminal as claimed in any one of claims 1 to 19, and the second terminal is used to execute the method executed by the second terminal as claimed in any one of claims 1 to 19.

21. A terminal device, characterized in that: The terminal device comprises a processor and a memory, the memory is used to store instructions, and the processor is used to read the instructions to execute the method executed by the first terminal or the second terminal as claimed in any one of claims 1 to 19.

22. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program includes program instructions, and when the program instructions are executed by a processor, the processor executes the method executed by the first terminal or the second terminal as claimed in any one of claims 1 to 19.

23. A chip, characterized in that: include: A processor, configured to call and run a computer program from a memory, so that a communication device equipped with the chip executes a method executed by the first terminal or the second terminal as claimed in any one of claims 1 to 19.

Images