WO2024109296A1 - 多设备任务流转方法和相关装置 - Google Patents

多设备任务流转方法和相关装置 Download PDF

Info

Publication number
WO2024109296A1
WO2024109296A1 PCT/CN2023/119815 CN2023119815W WO2024109296A1 WO 2024109296 A1 WO2024109296 A1 WO 2024109296A1 CN 2023119815 W CN2023119815 W CN 2023119815W WO 2024109296 A1 WO2024109296 A1 WO 2024109296A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
interface
page
master device
identifier
Prior art date
Application number
PCT/CN2023/119815
Other languages
English (en)
French (fr)
Inventor
王龙
葛峰
庞昊天
朱斌
Original Assignee
荣耀终端有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 荣耀终端有限公司 filed Critical 荣耀终端有限公司
Publication of WO2024109296A1 publication Critical patent/WO2024109296A1/zh

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
    • G06F3/04842—Selection of displayed objects or displayed text elements
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0487—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser
    • G06F3/0488—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser using a touch-screen or digitiser, e.g. input of commands through traced gestures
    • G06F3/04883—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser using a touch-screen or digitiser, e.g. input of commands through traced gestures for inputting data by handwriting, e.g. gesture or text

Definitions

  • the present application relates to the field of terminal technology, and in particular to a multi-device task transfer method and related apparatus.
  • Multi-device collaboration is a distributed technology applied to multiple electronic devices.
  • two or more electronic devices can collaborate across systems and devices to achieve resource sharing and collaborative operations.
  • Task flow is a technology that enables seamless application continuity between multiple devices.
  • the embodiment of the present application provides a multi-device task transfer method and related apparatus, which are applied to the field of terminal technology.
  • the first application and the second application are respectively transferred to the first slave device through heterogeneous screen projection and connection.
  • Different applications are adapted to different transfer methods to achieve intelligent transfer and improve user experience.
  • an embodiment of the present application proposes a multi-device task flow method.
  • the method includes: the master device displays a first interface, the first interface includes a page of a first application; the master device receives a first operation; in response to the first operation, the master device displays a second interface, the second interface includes a device identifier of the first slave device; the master device receives a second operation for the device identifier of the first slave device; in response to the second operation, the master device displays a third interface, and sends a page of the first application to the first slave device, so that the first slave device displays the page of the first application; the master device receives a third operation, the third operation is a return operation; in response to the third operation, the master device displays a fourth interface, the fourth interface does not include the page of the first application; the master device displays a fifth interface, the fifth interface includes the second application.
  • the master device receives the fourth operation; in response to the fourth operation, the master device displays the sixth interface, which includes the device identification of the first slave device; the master device receives the fifth operation for the device identification of the first slave device; in response to the fifth operation, the master device displays the seventh interface, and sends the content displayed on the page of the second application to the first slave device, so that the first slave device starts the third application, the third application corresponds to the second application, and the content displayed on the page of the third application is the same as the content displayed on the page of the second application; the master device receives the sixth operation, which is a return operation; in response to the sixth operation, the master device displays the eighth interface, which includes the page of the second application.
  • the first interface is an application page, and the first interface may correspond to the interface shown in a of FIG. 6A and a of FIG. 7A.
  • the page of the first application may correspond to the A application page shown in FIG. 6A.
  • the first application may be a video application or other types of applications, which is not limited in the embodiment of the present application.
  • the operation is used to enter the control center page.
  • the first operation can be a quick gesture operation, a voice operation, or other types of operations, which are not limited in the present embodiment.
  • the quick gesture operation can be a gesture operation such as three-finger upward swipe.
  • the second interface is the control center page, which may correspond to the interface shown in b in FIG. 6A and the interface shown in b in FIG. 7A.
  • the form of the device identification of the first slave device can refer to the description of the embodiment part, which will not be repeated here.
  • the second operation is used to select the first slave device. Based on different pages, the selection method may be different, which may be drag selection, or it may be selection by clicking the device identification of the first slave device, etc.
  • the embodiment of the present application does not limit the type of the second operation.
  • the third interface is the control center page after the task flow is successful, which may correspond to the interface shown in e in Figure 6A and e in Figure 7A.
  • the third operation is a return operation.
  • the return operation in the embodiment of the present application refers to the operation of calling the back instruction. Or it can also be understood as the operation of exiting the control center page.
  • the third operation can be a click operation, a shortcut operation, or a voice operation.
  • the embodiment of the present application does not limit the specific type of the third operation.
  • the fourth interface is the interface displayed after exiting the control center, which may correspond to the interface shown in f in Figure 6A and f in Figure 7A. It is understandable that after the main device streams the first application through the heterogeneous screen projection method, the main device closes the first application and does not display the page of the first application.
  • the fifth interface is an application page, and the fifth interface may correspond to the interface shown in a in Figure 6C and a in Figure 7B.
  • the page of the second application may correspond to the B application page shown in Figure 6C.
  • the second application may be a note-taking application or other types of applications, which is not limited in the embodiment of the present application.
  • the fourth operation is used to enter the control center page.
  • the fourth operation may be a quick gesture operation, a voice operation, or other types of operations, which is not limited in the embodiment of the present application.
  • the quick gesture operation may be a gesture operation such as swiping up with three fingers.
  • the sixth interface is the control center page, which may correspond to the interface shown in b in Figure 6C and the interface shown in b in Figure 7B.
  • the fifth operation is used to select the first slave device. Based on different pages, the selection method may be different, which may be drag selection, or selection by clicking on the device logo of the first slave device, etc.
  • the embodiment of the present application does not limit the type of the fifth operation.
  • the seventh interface is the control center page after the task flow is successful, which may correspond to the interface shown in e in Figure 6C and e in Figure 7B.
  • the third application and the second application can be understood as different versions of the same application, for example, a note application on a mobile phone and a note application on a computer.
  • the sixth operation is the return operation.
  • the return operation in the embodiment of the present application refers to the operation of calling the back instruction. Or it can also be understood as the operation of exiting the control center page.
  • the sixth operation can be a click operation, a shortcut operation, or a voice operation.
  • the embodiment of the present application does not limit the specific type of the sixth operation.
  • the eighth interface is the interface displayed after exiting the control center, which can correspond to the interface shown in f in Figure 6C and f in Figure 7B.
  • the first application and the second application are adapted to different methods, and can be respectively transferred to the first slave device through heterogeneous screen projection and connection.
  • the master device can automatically adjust the flow mode according to the application to achieve intelligent flow, without the need for users to find the corresponding flow entrances separately, reducing user memory costs and improving user experience.
  • the second interface also includes the logo of the first application
  • the sixth interface also includes the logo of the second application
  • the second operation is to drag the logo of the first application to the vicinity of the device logo of the first slave device
  • the fifth operation is to drag the logo of the second application to the vicinity of the device logo of the first slave device.
  • the identifier of the first application and the identifier of the second application may both correspond to the task
  • the identifier of the first application may correspond to the A application task identifier
  • the identifier of the second application may correspond to the B application task identifier.
  • the vicinity of the device identifier of the first slave device may be understood as a situation where the distance to the device identifier of the first slave device is less than a second threshold.
  • control center page displays the logo of the corresponding application, which is simple, intuitive, and clear at a glance.
  • the slave device can be selected by dragging the logo of the application to the vicinity of the device logo of the slave device, which is simple to operate and easy to understand.
  • the first operation is the same as the fourth operation, and the first operation is any one of the following operations: a three-finger swipe up operation, a double-click operation, a three-finger swipe down operation, and a triple-click operation.
  • the third operation is a left-swipe operation or a right-swipe operation at the edge of the screen, or a click operation on the first control displayed on the third interface;
  • the sixth operation is a left-swipe operation or a right-swipe operation at the edge of the screen, or a click operation on the first control displayed on the seventh interface.
  • the first control may correspond to an exit control. It is understandable that the master device may exit the control center page by sliding sideways, or by clicking the exit control on the control center page.
  • the third operation and the sixth operation may be the same or different.
  • the master device is any one of a mobile phone, a computer, and a tablet
  • the first slave device is any one of a mobile phone, a computer, and a tablet.
  • the fifth interface and the eighth interface are different interfaces, the fifth interface includes a first page of the second application, the eighth interface includes a second page of the second application, and the first page of the second application is different from the second page of the second application.
  • the fifth interface may correspond to a page being edited, or other pages being modified.
  • the second page exits the page being edited, or exits the page being modified.
  • the master device when the master device performs task flow through the connection, it will exit the editing, modifying and other states, and the content of the interface displayed by the application before and after the task flow will be different.
  • the second application is a note application
  • the first page of the second application is an editing page, and the editing page includes the content of the first note
  • the second page of the second application is a list page, and the list page includes the identifier of the first note.
  • the task flow in the embodiment of the present application can be applicable to the note application, and the content of the interface displayed by the application is different before and after the note application flow.
  • the first interface only includes a page of the first application
  • the fourth interface is the desktop of the main device.
  • the page that only includes the first application may refer to a page that displays the first application in full screen, or may refer to a page that displays the first application in an area other than the status bar area above.
  • the page that only includes the first application may be understood as a page that does not include pages of other applications except the page of the first application. The embodiment of the present application does not specifically limit this.
  • the main device closes the first application and does not display the page of the first application. If the main device only runs the first application in the foreground, after the first application is transferred through the heterogeneous screen projection method, the desktop is displayed.
  • the first interface also includes a page of a fourth application, and the page of the fourth application and the page of the first application are displayed in split screen; the fourth interface includes a page of the fourth application.
  • the fourth application may be a note application or other types of applications, which is not limited in the present embodiment.
  • the fourth application may be the same as the second application or different from the second application.
  • the page of the fourth application is displayed after the first application is transferred through the heterogeneous screen projection method.
  • the fifth interface also includes a page of a fifth application, and the page of the fifth application and the page of the second application are displayed in split screen; the eighth interface also includes a page of the fifth application, and the page of the second application and the page of the fifth application are displayed in split screen.
  • the fifth application may be a video application or other types of applications, which is not limited in the present embodiment.
  • the fifth application may be the same as the first application or different from the first application.
  • the first interface also includes a first floating window, which displays a page of a sixth application; the second interface does not include the logo of the sixth application, and the fourth interface also displays a second control; in response to the user's operation of the second control, the first floating window is displayed on the fourth interface.
  • the application displayed by the floating window may correspond to the small window application mentioned above.
  • the sixth application may be a video application or other types of applications, which is not limited in the embodiments of the present application.
  • the second control may correspond to a reduced small window application, which may also be referred to as a floating ball.
  • the fourth interface may correspond to the interface shown in FIG. 8A or FIG. 8B.
  • the small window application does not perform task transfer. After the task transfer, the small window application shrinks to the edge of the screen. The display of the small window application can be restored through the shrunk small window application.
  • the fifth interface also includes a second floating window, which displays a page of the seventh application; the sixth interface does not include the logo of the seventh application, and the eighth interface also displays a third control; in response to the user's operation on the third control, the second floating window is displayed on the eighth interface.
  • the application displayed through the floating window may correspond to the small window application mentioned above.
  • the seventh application may be a video application or other types of applications, which is not limited in the embodiments of the present application.
  • the third control may correspond to a reduced small window application, which may also be referred to as a floating ball.
  • the eighth interface may correspond to the interface shown in Figure 8A or Figure 8B. It is understandable that the small window application does not perform task transfer. After the task transfer, the small window application shrinks to the edge of the screen. The display of the small window application can be restored through the reduced small window application.
  • the master device is any one of a mobile phone, a computer, and a tablet
  • the first slave device is a large screen
  • the fourth interface includes a page of the first application.
  • the first application transfers tasks by means of same-source screen projection. Before and after the task transfer in same-source screen projection, the application page remains unchanged and the displayed content is the same. The page displayed on the slave device is the same as the page displayed on the master device.
  • the first interface also includes a page of a fourth application.
  • the fourth interface does not include the page of the fourth application.
  • the application page remains unchanged and the displayed content is the same before and after the task flow in the same-source screen projection.
  • the page displayed on the slave device is the same as the page displayed on the master device.
  • the master device is any one of a mobile phone, computer, or tablet
  • the first slave device is a large screen
  • the fifth slave device is a large screen.
  • the page of the second application included in the first interface and the page of the second application included in the eighth interface are the same page.
  • the second application transfers tasks by means of same-source screen projection. Before and after the task transfer in same-source screen projection, the application page remains unchanged and the displayed content is the same. The page displayed on the slave device is the same as the page displayed on the master device.
  • the page of the first application is a page for playing videos.
  • the method also includes: the master device displays a ninth interface, the ninth interface includes a page of an eighth application; the master device receives a seventh operation; in response to the seventh operation, the master device displays a tenth interface, the tenth interface includes a device identifier of the second slave device; the master device receives an eighth operation for the device identifier of the second slave device; in response to the eighth operation, the master device displays an eleventh interface, the eleventh interface includes the device identifier of the master device and the device identifier of the second slave device, wherein the device identifier of the master device is connected to the device identifier of the second slave device.
  • the ninth interface is an application page, which may correspond to the interface shown in a in FIG. 6A or a in FIG. 6C above, or other pages running foreground applications.
  • the seventh operation is similar to the first operation, and specific reference may be made to the description of the first operation, which will not be repeated here.
  • the tenth interface may correspond to a control center page that is not in a collaborative state.
  • the eleventh interface may correspond to a control center page in collaboration.
  • the eighth operation is used to select the device identifier of the second slave device, which may be a click operation or a drag operation. The embodiment of the present application does not limit the specific type of the eighth operation.
  • connected can be connected, can be close to each other (such as next to each other), which is not limited here.
  • control center page can also realize the collaborative connection between the master device and the slave device.
  • the eighth operation is an operation of dragging the device identifier of the second slave device to near the device identifier of the master device.
  • the vicinity of the device identification of the main device can be understood as a situation where the distance to the device identification of the main device is less than the third threshold.
  • the tenth interface also includes the logo of the eighth application, and the eleventh interface does not include the logo of the eighth application.
  • control center page that is not in a collaborative state displays the application logo and can perform task transfer; the control center page in a collaborative state does not display the application logo and cannot perform task transfer.
  • the eleventh interface also includes a first identifier, and the first identifier indicates the collaboration type between the master device and the second slave device.
  • the first identifier can correspond to same-source screen projection, screen extension, screen mirroring, keyboard and mouse sharing, etc.
  • the eleventh interface also includes a second identifier
  • the method also includes: the master device receives a ninth operation for the second identifier; in response to the ninth operation, the master device and the second slave device switch to a collaboration type corresponding to the second identifier.
  • the second identifier may correspond to collaborative types such as same-source screen projection, screen extension, screen mirroring, keyboard and mouse sharing, etc.
  • the ninth operation may be a click operation, a touch operation, etc., and the embodiment of the present application does not limit the ninth operation.
  • the user can adjust the collaboration type between the master device and the slave device through the second identifier, switch the collaboration mode, and improve the user experience.
  • the eleventh interface also includes a fourth control
  • the method also includes: the master device receives a tenth operation for the fourth control; in response to the tenth operation, the master device disconnects from the second slave device; the master device displays a twelfth interface, the twelfth interface includes a device identifier of the master device and a device identifier of the second slave device, and the device identifier of the master device is not connected to the device identifier of the second slave device.
  • the control center page after the twelfth interface is not disconnected from the collaborative connection may correspond to the interface shown in FIG. 11A.
  • the fourth control may correspond to a disconnection control (button).
  • the tenth operation may be a click operation, a touch operation, or other types of operations, which are not specifically limited in the embodiments of the present application.
  • connection between the master device and the slave device can be disconnected through the fourth control, and the collaboration can be disconnected, which is easy to operate.
  • the method also includes: the master device receives an eleventh operation for the device identification of the second slave device on the eleventh interface; in response to the eleventh operation, the master device disconnects from the second slave device; the master device displays a thirteenth interface, the thirteenth interface includes the device identification of the master device and the device identification of the second slave device, and the device identification of the master device is not connected to the device identification of the second slave device.
  • the thirteenth interface is a control center page after the collaborative connection is not disconnected, which may correspond to the interface shown in Figure 11B.
  • the eleventh operation may be a drag operation or other types of operations, which are not specifically limited in the embodiments of the present application.
  • connection between the master device and the slave device can be disconnected by dragging and dropping, and the collaboration is disconnected, which is easy to operate.
  • the eleventh interface also includes the identification of the third slave device, and the device identification of the master device is not connected to the device identification of the third slave device; the method also includes: the master device receives a twelfth operation for the device identification of the third slave device on the eleventh interface; in response to the twelfth operation, the master device disconnects the connection with the second slave device and establishes a connection with the third slave device; the master device displays the fourteenth interface, the fourteenth interface includes the device identification of the master device, the device identification of the second slave device and the identification of the third slave device, the device identification of the master device is connected to the device identification of the third slave device, and the device identification of the master device is not connected to the device identification of the second slave device.
  • the twelfth operation is used to switch the slave device connected to the master device.
  • the twelfth operation can be an operation of dragging the device identifier of the third slave device, or can be other types of operations, which are not limited in the embodiment of the present application.
  • the fourteenth interface can correspond to the interface shown in FIG. 12 .
  • the master device can switch the coordinated slave device to improve the user experience.
  • collaboration type includes any one of the following types: same-source screen projection, screen extension, screen mirroring, and keyboard and mouse sharing.
  • an embodiment of the present application provides an electronic device, the electronic device includes a terminal device, which may also be referred to as a terminal, a user equipment (UE), a mobile station (MS), a mobile terminal (MT), etc.
  • the terminal device may be a mobile phone, a smart TV, a wearable device, a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc.
  • VR virtual reality
  • AR augmented reality
  • the electronic device comprises: a processor and a memory; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory, so that the electronic device executes the method as in the first aspect.
  • an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program.
  • the computer program is executed by a processor, the method of the first aspect is implemented.
  • an embodiment of the present application provides a computer program product, which includes a computer program.
  • the computer program When the computer program is executed, the computer executes the method of the first aspect.
  • an embodiment of the present application provides a chip, the chip includes a processor, the processor is used to call the storage A computer program in a memory to execute the method as described in the first aspect.
  • FIG1 is a schematic diagram of the hardware structure of a terminal device provided in an embodiment of the present application.
  • FIG2 is a schematic diagram of a software structure of a terminal device provided in an embodiment of the present application.
  • FIG3 is a schematic diagram of an interface of a control center page provided in an embodiment of the present application.
  • FIG4A is a schematic diagram of an interface for entering a control center page provided in an embodiment of the present application.
  • FIG4B is a schematic diagram of an interface for hiding a control center card provided in an embodiment of the present application.
  • FIG4C is a schematic diagram of an interface of a control center card provided in an embodiment of the present application.
  • FIG5 is a schematic diagram of another interface for entering a control center page provided in an embodiment of the present application.
  • FIG6A is a schematic diagram of an interface for task transfer provided in an embodiment of the present application.
  • FIG6B is a schematic diagram of an interface of a slave device provided in an embodiment of the present application.
  • FIG6C is a schematic diagram of another interface of task flow provided in an embodiment of the present application.
  • FIG6D is a schematic diagram of an interface of a slave device provided in an embodiment of the present application.
  • FIG6E is a schematic diagram of another interface of task flow provided in an embodiment of the present application.
  • FIG6F is a schematic diagram of an interface of a slave device provided in an embodiment of the present application.
  • FIG7A is a schematic diagram of an interface for task flow during split-screen display provided by an embodiment of the present application.
  • FIG7B is a schematic diagram of another interface for task flow during split-screen display provided by an embodiment of the present application.
  • FIG7C is a schematic diagram of an interface for task transfer during another split-screen display provided by an embodiment of the present application.
  • FIG7D is a schematic diagram of an interface of a slave device provided in an embodiment of the present application.
  • FIG8A is a schematic diagram of an interface for task flow in a small window application provided by an embodiment of the present application.
  • FIG8B is a schematic diagram of an interface for another task flow in a small window application provided by an embodiment of the present application.
  • FIG8C is a schematic diagram of an interface for task flow in another small window application provided by an embodiment of the present application.
  • FIG9 is a schematic diagram of an interface for a task transfer failure provided by an embodiment of the present application.
  • FIG10 is a schematic diagram of an interface for device collaboration provided in an embodiment of the present application.
  • FIG11A is a schematic diagram of an interface for collaborative connection of devices provided in an embodiment of the present application.
  • FIG11B is a schematic diagram of an interface for collaborative disconnection of devices provided in an embodiment of the present application.
  • FIG12 is a schematic diagram of an interface of a switching coordination device provided in an embodiment of the present application.
  • FIG13A is a schematic diagram of an interface of a master device provided in an embodiment of the present application.
  • FIG13B is a schematic diagram of an interface of a master device provided in an embodiment of the present application.
  • FIG14 is a schematic diagram of an interface of a master device provided in an embodiment of the present application.
  • FIG15 is a schematic diagram of a flow chart of a multi-device task transfer method provided in an embodiment of the present application.
  • FIG16 is a schematic diagram of the structure of a multi-device task transfer apparatus provided in an embodiment of the present application.
  • Multi-screen collaboration Project the user interface of electronic device A onto the screen of electronic device B for display, and allow the user to operate the user interface of electronic device A in electronic device B, and transfer files in electronic device B to electronic device A by performing specific operations in electronic device B (for example, dragging files from the user interface of electronic device B to the user interface of electronic device A), so as to realize cross-device operation and cross-device file transfer between electronic devices A and B.
  • the user interface of electronic device A can be displayed in any area of the screen of electronic device B, or in full screen.
  • the multi-screen collaboration in the embodiment of the present application includes: same-source screen projection, screen extension, screen mirroring, keyboard and mouse sharing, etc. At the same time, any two devices use a collaborative mode.
  • Screen expansion Use the screen of electronic device B as the secondary screen of electronic device A.
  • Electronic device A can transfer part of the content it needs to display to the secondary screen for display.
  • the screen of electronic device A and the screen of electronic device B can display content together, thereby expanding the display capability of electronic device A.
  • Electronic device A and electronic device B can share each other's original input devices, such as mouse, keyboard, etc.
  • the input device of electronic device A is shared with electronic device B, and the shared input device can be used for input in both electronic device A and electronic device B.
  • files can be transferred between electronic devices A and B.
  • the interface of electronic device B may prompt the user to open the application running on electronic device A on electronic device B, so as to transfer to electronic device B for the continued operation.
  • the progress of the application on electronic device B is the same as that on electronic device A, that is, electronic device B synchronizes the progress of the application running on electronic device A. For example, watching videos, editing documents, etc.
  • a document application is running on electronic device A, and the document application can be a memo, word, etc. The user is editing a document on electronic device A.
  • a prompt message is displayed on electronic device B, and the user clicks the prompt message on electronic device B.
  • electronic device B opens the document application and displays the location where the user is editing, so as to transfer to electronic device B to continue editing, etc.
  • Single-window application screen projection (heterogeneous screen projection): Electronic device A uses two-way encoding, one of which sends the default interface to the display (i.e., displayed on the display screen of electronic device A). The other encoding sends the standard video stream corresponding to the screen projection application interface rendered on the virtual screen to electronic device B.
  • Same-source screen projection Project the content (e.g., videos, photos, etc.) on the screen of electronic device A to the screen of electronic device B for display.
  • both electronic device A and electronic device B display the interface sent by electronic device A.
  • the interfaces of multiple applications launched on electronic device A are projected to electronic device B in an extended screen manner.
  • electronic device A uses one-way encoding to send the projection application interface rendered on the virtual screen and the video stream corresponding to the default interface to electronic device B, so that the screen can be displayed on electronic device B.
  • the default interface and the interface of one or more screen projection applications started in the form of free floating windows on electronic device A are displayed on the display screen.
  • the default interface can be understood as the interface displayed by electronic device A.
  • electronic device B can reversely control electronic device A.
  • a PC can reversely control a mobile phone.
  • the same-source screen projection method can ensure the continuity of the application; while the different-source screen projection method requires restarting the application when switching between different screens.
  • Task transfer The task is transferred to the slave device, but there is no collaboration between the devices.
  • words such as “first” and “second” are used to distinguish the same or similar items with substantially the same functions and effects.
  • the first chip and the second chip are only used to distinguish different chips, and their order is not limited.
  • words such as “first” and “second” do not limit the quantity and execution order, and words such as “first” and “second” do not necessarily limit them to be different.
  • At least one refers to one or more
  • plural refers to two or more.
  • And/or describes the association relationship of associated objects, indicating that three relationships may exist.
  • a and/or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural.
  • the character “/” generally indicates that the objects associated before and after are in an “or” relationship.
  • At least one of the following” or similar expressions refers to any combination of these items, including any combination of single or plural items.
  • At least one of a, b, or c can represent: a, b, c, a-b, a--c, b-c, or a-b-c, where a, b, c can be single or multiple.
  • the terminal device of the embodiment of the present application may also be any form of electronic device.
  • the electronic device may include a handheld device with image processing function, a vehicle-mounted device, etc.
  • some electronic devices are: mobile phones, tablet computers, PDAs, laptop computers, mobile internet devices (MID), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, etc.
  • the present invention relates to wireless terminals in a smart city, wireless terminals in a smart home, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDA), handheld devices with wireless communication functions, computing devices or other processing devices connected to a wireless modem, vehicle-mounted devices, wearable devices, terminal devices in a 5G network or terminal devices in a future evolved public land mobile network (PLMN), etc.
  • PLMN public land mobile network
  • the electronic device may also be a wearable device.
  • Wearable devices can also be called wearable smart devices. They are a general term for the application of wearable technology to intelligently design and develop wearable devices for daily wear, such as glasses, gloves, watches, clothing and shoes.
  • Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also realize powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-sized, and independent of smartphones to achieve complete or partial functions, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.
  • the electronic device can also be a terminal device in the Internet of Things (IoT) system.
  • IoT Internet of Things
  • Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network that interconnects people and machines and things.
  • the electronic devices in the embodiments of the present application may also be referred to as: terminal equipment, user equipment (UE), mobile station (MS), mobile terminal (MT), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user device, etc.
  • UE user equipment
  • MS mobile station
  • MT mobile terminal
  • access terminal user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user device, etc.
  • the electronic device or each network device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer.
  • the hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and a memory (also called main memory).
  • the operating system can be any one or more computer operating systems that implement business processing through processes, such as Linux operating system, Unix operating system, Android operating system, iOS operating system, or Windows operating system.
  • the application layer includes applications such as browsers, address books, word processing software, and instant messaging software.
  • FIG1 shows a schematic diagram of the structure of a terminal device.
  • the terminal device may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc.
  • SIM subscriber identification module
  • the sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.
  • the structure illustrated in the embodiment of the present invention does not constitute a specific limitation on the terminal device.
  • 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 processor 110 may include one or more processing units.
  • the processor 110 may include an application processor (AP), a modem processor, a graphics processor (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and/or a neural network processor. (neural-network processing unit, NPU), etc.
  • AP application processor
  • GPU graphics processor
  • ISP image signal processor
  • DSP digital signal processor
  • NPU neural-network processing unit
  • different processing units can be independent devices or integrated in one or more processors.
  • the controller can generate operation control signals according to the instruction operation code and timing signal to complete the control of instruction fetching and execution.
  • the processor 110 may also be provided with a memory for storing instructions and data.
  • the memory in the processor 110 is a cache memory.
  • the memory may store instructions or data that the processor 110 has just used or cyclically used. If the processor 110 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 110, and thus improves the efficiency of the system.
  • the processor 110 may include one or more interfaces.
  • the interface may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver/transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input/output (GPIO) interface, a subscriber identity module (SIM) interface, and/or a universal serial bus (USB) interface, etc.
  • I2C inter-integrated circuit
  • I2S inter-integrated circuit sound
  • PCM pulse code modulation
  • UART universal asynchronous receiver/transmitter
  • MIPI mobile industry processor interface
  • GPIO general-purpose input/output
  • SIM subscriber identity module
  • USB universal serial bus
  • the interface connection relationship between the modules illustrated in the embodiment of the present invention is only a schematic illustration and does not constitute a structural limitation on the terminal device.
  • the terminal device may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.
  • the terminal device implements the display function through a GPU, a display screen 194, and an application processor.
  • the GPU is a microprocessor for image processing, which connects the display screen 194 and the application processor.
  • the GPU is used to perform mathematical and geometric calculations for graphics rendering.
  • the processor 110 may include one or more GPUs that execute program instructions to generate or change display information.
  • the terminal device can realize the shooting function through ISP, camera 193, video codec, GPU, display screen 194 and application processor.
  • the external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the terminal device.
  • the external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function. For example, files such as music and videos can be saved in the external memory card.
  • the internal memory 121 can be used to store computer executable program codes, and the executable program codes include instructions.
  • the internal memory 121 may include a program storage area and a data storage area.
  • 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 (such as audio data, a phone book, etc.), etc.
  • the internal memory 121 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 (universal flash storage, UFS), etc.
  • the processor 110 executes various functional applications and data processing of the terminal device by running instructions stored in the internal memory 121 and/or instructions stored in a memory provided in the processor. For example, the multi-device task flow method of the embodiment of the present application may be executed.
  • the structure illustrated in the embodiments of the present application does not constitute a specific limitation on the terminal device.
  • the terminal device 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 hardware, software, or software. And hardware combination.
  • the software system of the terminal device can adopt a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture.
  • the embodiment of the present application takes the Android system of the layered architecture as an example to exemplify the software structure of the terminal device.
  • FIG2 is a software structure block diagram of a terminal device of an embodiment of the present application.
  • the layered architecture divides the software into several layers, each layer has a clear role and division of labor.
  • the layers communicate with each other through software interfaces.
  • the Android system can be divided into four layers, namely, the application layer (applications), the application framework layer (application framework), the Android runtime (Android runtime) and the system library, and the kernel layer (kernel).
  • the application layer can include a series of application packages.
  • the application layer runs applications by calling the application programming interface (API) provided by the application framework layer.
  • API application programming interface
  • the application package can include applications such as camera, calendar, phone, map, phone, music, settings, mailbox, video, social, etc.
  • the application framework layer provides application programming interface (API) and programming framework for the applications in the application layer.
  • API application programming interface
  • the application framework layer includes some predefined functions.
  • the application framework layer may include a window manager, a content provider, a resource manager, a view system, a notification manager, and the like.
  • the window manager is used to manage window programs.
  • the window manager can obtain the display size, determine whether there is a status bar, lock the screen, touch the screen, drag the screen, capture the screen, etc.
  • Content providers are used to store and retrieve data and make it accessible to applications.
  • the data can include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.
  • the view system includes visual controls, such as controls for displaying text, controls for displaying images, etc.
  • the view system can be used to build applications.
  • a display interface can be composed of one or more views.
  • a display interface including a text notification icon can include a view for displaying text and a view for displaying images.
  • the resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, and so on.
  • 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, the terminal device vibrates, the indicator light flashes, etc.
  • Android runtime includes core libraries and virtual machines. Android runtime is responsible for scheduling and management of the Android system.
  • 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.
  • 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.
  • the system library can include multiple functional modules. For example: surface manager, media library, 3D graphics processing library (for example: OpenGL ES), 2D graphics engine (for example: SGL) etc.
  • surface manager for example: surface manager, media library, 3D graphics processing library (for example: OpenGL ES), 2D graphics engine (for example: SGL) etc.
  • 3D graphics processing library for example: OpenGL ES
  • 2D graphics engine for example: SGL
  • the surface manager is used to manage the display subsystem and provide the fusion of 2D and 3D layers for multiple applications.
  • 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.
  • the 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.
  • a 2D graphics engine is a drawing engine for 2D drawings.
  • the kernel layer is the layer between hardware and software.
  • the kernel layer contains at least display driver, camera driver, audio driver, and sensor driver.
  • the layers implementing the same function may be called by other names, or the layers that can implement the functions of multiple layers may be regarded as one layer, or the layers that can implement the functions of multiple layers may be divided into multiple layers.
  • the embodiments of the present application are not limited to this.
  • Multi-device collaboration is a distributed technology applied to multiple electronic devices.
  • two or more electronic devices can collaborate across systems and devices to achieve resource sharing and collaborative operation.
  • Multi-device collaboration can be applied to electronic devices of the same or different types.
  • the types of electronic devices include, but are not limited to, mobile phones, tablet computers, laptops, large-screen devices (e.g., smart TVs, smart screens), personal computers (PCs), handheld computers, netbooks, personal digital assistants (PDAs), wearable electronic devices, vehicle-mounted devices, virtual reality devices, and other devices.
  • the mobile phone in the embodiment of the present application can be a folding screen mobile phone or a non-folding screen mobile phone, which is not limited here.
  • the communication connection can be a wired communication connection or a wireless communication connection.
  • the solution of wired communication connection can include USB On-The-Go (OTG) technology, for example;
  • the solution of wireless communication can include wireless fidelity (Wi-Fi), Wi-Fi Direct (Wi-Fi Direct), Bluetooth (BT), near field communication (NFC), infrared technology (IR), etc.
  • collaboration types also known as collaborative services
  • collaborative services such as screen extension, screen projection, screen mirroring, multi-screen collaboration, keyboard and mouse sharing, super keyboard and mouse, etc.
  • some collaboration types are initiated by the master device (generally the initiator of multi-device collaboration) to the slave device (generally the participant of multi-device collaboration) in response to user operations, so they can be called manual collaboration services or manual collaboration services, such as screen extension, screen projection, screen mirroring, multi-screen collaboration, keyboard and mouse sharing, etc.
  • other collaboration types are automatically triggered when the trigger rules are met when the user turns on the function, so they can be called automatic collaboration services or automatic collaboration services, such as super continuation, etc.
  • the cooperation type they support is generally related to factors such as device type, screen size, device capability, etc. Therefore, two electronic devices may support only one cooperation type or may support multiple cooperation types.
  • the application for task flow in the terminal device is a video application, and the type of application for flow is single.
  • intelligent flow cannot be achieved for different devices, and the user experience is poor.
  • the embodiment of the present application provides a multi-device task transfer method. Based on the type of slave device and application type, different transfer modes are adapted, and intelligent transfer is performed to reduce user memory costs and improve user experience.
  • the embodiments of the present application classify the electronic devices that may be involved in various scenarios of multi-device collaboration, and each electronic device includes but is not limited to being divided into: master devices and slave devices. Among them:
  • Master device includes the device currently held by the user. The user can perform operations on the master device to initiate multi-device collaboration and task transfer to other devices. Therefore, the master device is generally also the device that initiates multi-device collaboration and task transfer.
  • the multi-device task transfer method provided in the embodiment of the present application can be implemented in the master device.
  • Slave devices include devices located near the master device and logged into the same account as the master device.
  • the master device and the slave device are generally electronic devices produced by the same manufacturer.
  • the master device can be a mobile phone produced by manufacturer A
  • the slave device can be a tablet computer, large-screen device, etc. produced by manufacturer A.
  • the accounts logged into the master and slave devices can be the accounts applied by the user from the device manufacturer.
  • the multi-device task transfer method provided in the embodiment of the present application can be implemented in a master device.
  • the master device can execute each step of the multi-device task transfer method in response to one or more operations performed by a user.
  • control center page provided in the embodiment of the present application is described below in conjunction with Figure 3.
  • the example of the control center page shown in Figure 3 is that during the process of the main device running application A, the main device detects the user's preset gesture and displays the control center page shown in Figure 3, and the page shown in Figure 3 includes the logo of application A.
  • the preset gesture can be swiping up with three fingers on the screen, swiping up from the bottom of the screen, etc., which is not limited in this application.
  • the main device detects that the user opens the notification center, such as swiping down from the top to open the drop-down menu of the notification center, and the drop-down menu may include a card for the user to enter the control center.
  • the control center page shown in Figure 3 may be displayed, or another control center page may be displayed, and the other control center page does not include the logo of application A.
  • the control center page includes a device identifier 301 of the master device, a device identifier 302 of the slave device, and a task identifier 303.
  • the device identifier may be a device identifier of a tablet computer, a device identifier of a large-screen device, a device identifier of a PC, a device identifier of a mobile phone, etc.
  • Task identifier 303 indicates the identifier of application A that is being run by the master device.
  • the device identification 301 of the master device and the device identification 302 of the slave device may be graphical identifications, such as icons, or other skeuomorphic elements.
  • the device identification 301 of the master device and the device identification 302 of the slave device can be different colors to facilitate user distinction.
  • the device identification 301 of the master device can be blue, and the device identification 302 of the slave device can be white (or transparent).
  • the device identification 301 of the master device and the device identification 302 of the slave device can be different sizes to facilitate user distinction.
  • the size of the device identification 301 of the master device can be larger than the size of the device identification 302 of the slave device.
  • the control center page may include the device identification 301 of the master device and the device identification 302 of each slave device.
  • the device identification 301 of the master device may be located in the center area of the control center page, for example, in the center or lower area of the control center page 301.
  • the device identification 302 of the slave device can be distributed around the device identification of the master device. In some embodiments, the device identification 302 of the slave device is located below the device identification 301 of the master device.
  • the device identification 301 of the master device is located in the upper center area of the control center page.
  • the device identifications 302 of the slave devices such as the device identification of a tablet computer, the device identification of a large-screen device, the device identification of a PC, and the device identification of a mobile phone, can be evenly distributed in a semicircle below the device identification 301 of the master device.
  • the task identifier 303 may be a graphical identifier, such as an icon, or other skeuomorphic elements, etc.
  • the icon of the application may be used as the task identifier 303, or the application name may be used as the task identifier 303, which is not limited in the embodiment of the present application.
  • the control center page may also include a device name 304 of each slave device, and the device name 304 may be displayed in conjunction with its corresponding device identifier 302, for example, the device name may be displayed above, below, or in other locations of its corresponding device identifier 302.
  • the device name 304 may be the product name of the slave device, such as Honor TV, Honor Pad, Honor Magic Book, etc.
  • the device name 304 may also be a user-defined name, such as Xiao Li's Honor tablet, Honor Smart Screen in the living room, etc., which is not limited in the embodiment of the present application.
  • the task identifier 303 is distributed around the device identifier 301 of the main device, for example, it can be distributed above the device identifier 301 of the main device, or distributed below the device identifier 301 of the main device, etc., and the implementation of this application does not limit this.
  • control center page further includes one or more function buttons, such as a details button 305, an exit button 306, etc.
  • the user can learn how to use the control center page by clicking the details button 305.
  • the user can exit the control center page by clicking the exit button 306.
  • the user can also exit the control center page by a quick operation such as a side swipe operation.
  • the master device when the user drags the device identifier 302 of any slave device to the vicinity of the device identifier 301 of the master device, the master device establishes a connection with the slave device to perform a collaborative connection, etc.; when the user drags the task identifier 303 to the vicinity of the device identifier 302 of any slave device, the master device transfers the application corresponding to the task identifier to the corresponding slave device based on the type of the slave device, the status of the application installed on the slave device, etc.
  • the user can enter the control center page through the control center card in the notification center page, or enter the control center page through a shortcut operation.
  • the shortcut operation can be a three-finger upward swipe, or other types of shortcut operations, which are not limited in the embodiment of the present application.
  • the main device when the user slides down the desktop shown in a of FIG4A, the main device receives an operation to enter the notification center page, and enters the notification center page shown in b of FIG4A.
  • the notification center page includes one or more function switch buttons, such as: WLAN switch button 401, Bluetooth switch button 402, flashlight switch button 403, vibration switch button 404, mute switch button 405, etc.
  • the main device can turn on or off the corresponding function.
  • the notification center page may also include one or more sliding controls, such as a sliding control 406 for adjusting the brightness of the display screen.
  • a sliding control 406 for adjusting the brightness of the display screen.
  • the host device may adjust the brightness of the display screen. adjust.
  • the notification center page may also include a control center card 407, which may include a card name 408 and one or more clickable elements, such as a hidden icon 409 of the control center card 407 and an entry button 410 of the control center card 407.
  • a control center card 407 may include a card name 408 and one or more clickable elements, such as a hidden icon 409 of the control center card 407 and an entry button 410 of the control center card 407.
  • the specific content of the control center card 407 will be described in detail below.
  • the name of the above card is only an example of this application.
  • the function of smart interconnection can also be named by other names, and this application does not limit this.
  • it can be: “Honor Interconnection”, “HyperTerminal”, etc.
  • the card name 408 displayed in the control center card 407 can be "Honor Interconnection”, "HyperTerminal”, etc.
  • the multi-device collaboration main page can also be called the Honor Interconnection main page and the HyperTerminal main page.
  • the master device When the user clicks the entry button 410 on the notification center page, the master device receives the operation of opening the control center and enters the control center page shown in c of Figure 4A.
  • the control center page includes the device identification 301 of the master device and the device identification 302 of the slave device.
  • the notification center page further includes an edit button 411.
  • the user can also display or hide the control center card 407 through the edit button 411.
  • the main device receives an operation to display the edit menu and enters the page shown in a in FIG. 4B .
  • the edit menu on this page includes a hide button 412.
  • the main device receives an operation to hide the control center card and enters the page shown in b in FIG. 4B .
  • the control center card is not displayed on this page.
  • the master device When the user clicks the edit button 411 on the page shown in b of FIG. 4B , the master device receives an operation of displaying the edit menu and enters the page shown in c of FIG. 4B .
  • the edit menu on this page includes a display button 413.
  • the master device receives an operation of displaying the control center card and enters the page shown in b of FIG. 4A .
  • the control center card is displayed on this page.
  • the main device when the user clicks the hide icon 409 on the page shown in b in FIG. 4A , the main device receives an operation to hide the control center card and enters the page shown in b in FIG. 4B .
  • the page shown in b in FIG. 4B further includes a prompt message 414.
  • the prompt message 414 is used to prompt the user to call out the operation mode of the control center card.
  • the prompt message 414 can be a text message, for example, you can click "Show Smart Connect" to restore the card.
  • the prompt message 414 may be displayed in the form of a bubble or a toast message.
  • the specific display form of the prompt message 414 is not limited in the embodiment of the present application.
  • the prompt message 414 may disappear after being displayed for a period of time, or after receiving any operation. In this way, the obstruction of other buttons in the notification center page by the prompt message 414 can be reduced.
  • the embodiment of the present application does not limit the disappearance method of the displayed prompt message 414.
  • the prompt message 414 may be displayed only when the user hides the control center card for the first time by hiding the icon; the prompt message 414 may also be displayed when the control center card is hidden by hiding the icon for the first N times.
  • the embodiment of the present application does not limit the specific display conditions of the prompt message 414.
  • control center card 407 also displays the status of the collaborative function.
  • the master device can directly display the search results in the control center card 407 when displaying the notification center page.
  • the control center card 407 can display the number of slave devices that the master device has searched for (as shown in b in FIG. 4A ). 4A ), the device identification of one or more slave devices that have been searched may also be displayed, and the device name of one or more slave devices that have been searched may also be displayed.
  • the master device displays the control center interface shown in c of FIG. 4A , and the control center interface includes the device identification of a corresponding number of slave devices.
  • the master device may display an interface element indicating the function of the control center in the control center card 407 when displaying the notification center page.
  • the control center card 407 may display a slogan of the control center, such as "Smart Connectivity, Smart Life" (as shown in a of FIG. 4C ).
  • the master device may display an interface element indicating the function of the control center in the control center card 407 when the notification center page is displayed.
  • the control center card 407 may display a slogan of the control center, such as "this device is cooperating" (as shown in b in FIG. 4C ).
  • the control center card 407 does not include the hidden icon 409.
  • the user can also enter the notification center page by sliding down when the main device displays the application page. Accordingly, since the main device runs a foreground application before entering the notification center page, the control center page entered through the notification center page includes a task identifier 303 (for example, as shown in FIG. 3 ).
  • the master device is running a video application and playing a video.
  • the master device determines that the distance corresponding to the swipe up operation exceeds the first threshold, the master device receives an operation to enter the control center page, and the master device enters the control center page shown in b of FIG5 .
  • the control center page includes a device identifier 301 of the master device, a device identifier 302 of the slave device, and a task identifier 303.
  • the master device determines that the distance corresponding to the swipe up operation exceeds the first threshold, the master device receives the operation of entering the control center page. If the master device determines that the distance corresponding to the swipe up operation does not exceed the first threshold, the master device does not receive the operation of entering the control center page, does not enter the control center page, and returns to the interface of running the application.
  • the first threshold may be 20 pixels (px) or any other value, which is not limited here.
  • the master device may display a dynamic special effect based on the three-finger swipe up operation during the process of receiving the three-finger swipe up operation.
  • the dynamic special effect may be a zooming dynamic effect, for example, the page receiving the three-finger swipe up operation is zoomed in a certain proportion until the form shown by the task identifier 303 is displayed, and the device identifiers of the master device and the slave device are displayed. It may also be any other type of dynamic effect. The embodiments of the present application are not limited to this.
  • the main device after receiving the three-finger swipe-up operation, the main device enters the control center page shown in b in FIG. 5 via the page shown in c in FIG. 5 .
  • control center page can include an application identification card.
  • the control center page can include identification cards of the multiple applications.
  • the task flow function of the control center is described below with reference to FIG. 6A to FIG. 6F .
  • control center page may include an identification card of the application to implement task flow.
  • the task transfer modes include: single window screen projection, same source screen projection, continuation, etc.
  • 6A is a schematic diagram of a task flow interface provided by an embodiment of the present application, where the master device is a mobile phone, the slave device is a computer, application A is a video application, and application A is not installed on the slave device.
  • the main device When the main device is displaying the application page corresponding to application A, it receives a three-finger upward swipe operation from the user, and the main device enters the control center page shown in b of FIG. 6A from the page shown in a of FIG. 6A.
  • the control center page includes the device identification 301 of the main device, the identification card 601 of application A, and the device identification 602 of the computer.
  • the user can drag the identification card 601 of application A toward the device identification 602 of the computer.
  • the device identification 602 of the computer automatically absorbs the identification card 601 of application A (as shown in c in FIG. 6A ).
  • the master device When the drag operation ends at a position near the device identifier 602 of the computer, the master device initiates a task flow to the computer, and the master device enters the interface shown in d in Figure 6A. In this interface, the identifier in the device identifier 602 of the computer changes to a connection identifier, so as to visually feedback the status of the ongoing task flow to the user.
  • the device identification 602 of the computer automatically absorbs the identification card 601 of application A.
  • the master device initiates a task flow to the computer.
  • the second threshold value may be 20 pixels (px) or any other value, which is not limited here.
  • the main device projects the content displayed by application A (for example, videos, photos, etc.) to the computer screen for display, thereby realizing single-window application screen projection, that is, heterogeneous screen projection.
  • application A for example, videos, photos, etc.
  • the main device When the task transfer between the main device and the computer is completed, the main device enters the interface shown in Figure 6A e, and the page does not display the identification card 601 of application A. Adaptively, the computer displays a projection window 603, which displays the content of application A (as shown in Figure 6B).
  • the page of application A is not displayed.
  • the main device receives a user click on the exit button 306 on the page shown in e in Figure 6A, the main device enters the page shown in f in Figure 6A from the page shown in e in Figure 6A.
  • the page shown in f in Figure 6A is the desktop of the main device.
  • the main device receives a user side-slide operation on the page shown in e in Figure 6A
  • the main device enters the page shown in f in Figure 6A from the page shown in e in Figure 6A.
  • the page shown in f in Figure 6A is the desktop of the main device.
  • the side-slide operation can be a left-slide operation or a right-slide operation, which is not limited here.
  • 6C is a schematic diagram of a task flow interface provided by an embodiment of the present application.
  • the master device is a mobile phone
  • the slave device is a computer
  • the slave device has application B installed.
  • application B is a note application
  • both the master device and the slave device have the note application installed.
  • the page shown in a of Fig. 6C enters the control center page shown in b of Fig. 6C.
  • the control center page includes the device identification 301 of the main device, the identification card 604 of the B application and the device identification 602 of the computer.
  • the user can drag the identification card 604 of application B toward the device identification 602 of the computer.
  • the device identification 602 of the computer automatically absorbs the identification card 604 of application B (as shown in c in FIG. 6C ).
  • the master device When the drag operation ends at a position near the device identifier 602 of the computer, the master device initiates a task flow to the computer, and the master device enters the interface shown in d of Figure 6C. In this interface, the identifier in the device identifier 602 of the computer changes to a connection identifier, so as to give the user a visual feedback of the ongoing task flow status.
  • the device identification 602 of the computer automatically absorbs the identification card 604 of application B.
  • the main device initiates a task flow to the computer.
  • both the application B installed in the computer and the application B installed on the master device support continuation.
  • the master device exits the editing state of application B and controls the computer to open application B and display the application page corresponding to application B.
  • the progress of the tasks in the application interface corresponding to application B displayed on the computer is the same, so as to achieve the display content continuation.
  • the master device synchronizes the progress or location information of application B running on the master device to the slave device.
  • the slave device opens application B, it can directly display the corresponding progress or location to achieve continuation.
  • the main device exits the editing state of the B application and projects the content displayed by the B application (for example: videos, photos, etc.) to the computer screen for display, so as to realize single-window application screen projection, that is, heterogeneous screen projection.
  • the B application for example: videos, photos, etc.
  • the host device When the task transfer between the host device and the computer is completed, the host device enters the interface shown in Figure 6C e, and the page does not display the identification card 604 of application B. Adaptively, the computer opens application B and displays the application page corresponding to application B (as shown in Figure 6D).
  • the page of application B is displayed.
  • the master device enters the page shown in f in FIG. 6C from the page shown in e in FIG. 6C.
  • the page shown in f in FIG. 6C is the application page corresponding to application B, for example, the main interface of application B.
  • Application B in the master device does not exit the foreground, but the interface displayed according to the logical changes of the application connection.
  • the master device if the master device is in the editing state while the B application is performing the task flow, the master device exits the editing state and then performs the task flow.
  • the main device can exit the control center through the exit button 306 or through a side-slide operation.
  • the embodiment of the present application does not limit the specific operation of exiting the control center.
  • 6E is a schematic diagram of an interface for task transfer provided by an embodiment of the present application. Taking the master device as a mobile phone, the slave device as a large-screen device, and application A as a video application as an example, an example of a task transfer method according to another embodiment of the present application is introduced.
  • the main device When the main device is displaying the application page corresponding to application A, it receives a three-finger upward swipe operation from the user, and the main device enters the control center page shown in b in FIG. 6E from the page shown in a in FIG. 6E.
  • the control center page includes the device identification 301 of the main device, the identification card 601 of application A, and the device identification 605 of the large-screen device.
  • the user can drag the identification card 601 of application A to the device identification 605 of the large screen device. Drag.
  • the device identification 605 of the large-screen device automatically absorbs the identification card 601 of application A (as shown in c in FIG. 6E ).
  • the master device When the drag operation ends near the device identifier 605 of the large-screen device, the master device initiates a task transfer to the large-screen device, and the master device enters the interface shown in d of Figure 6E. In this interface, the identifier in the device identifier 605 of the large-screen device changes to a connection identifier, so as to visually feedback the status of the ongoing task transfer to the user.
  • the device identification 605 of the large-screen device automatically absorbs the identification card 601 of application A.
  • the main device initiates a task flow to the large-screen device.
  • the master device Since the slave device is a large-screen device, the master device projects the content displayed on the master device (for example, videos, photos, etc.) to the screen of the large-screen device for display, thereby realizing same-source screen projection.
  • the main device When the task transfer between the main device and the computer is completed, the main device enters the interface shown in Figure 6E e, and the page does not display the identification card 601 of application A. Adaptively, the content displayed on the large-screen device is the same as the content displayed on the main device (as shown in Figure 6F a).
  • the main device When the main device exits the control center after the transfer is completed, the main device enters the application page of application A shown in f in FIG6E from the page shown in e in FIG6E. Adaptively, the content displayed on the large-screen device is the same as the content displayed on the main device (as shown in b in FIG6F).
  • the main device can exit the control center through the exit button 306 or through a side-slide operation.
  • the embodiment of the present application does not limit the specific operation of exiting the control center.
  • the state of the application performing task flow remains unchanged. For example, taking the note application as an example, if the note application is in the editing state, the main device is still in the editing state after exiting the control center page.
  • FIG7A is a schematic diagram of an interface for task transfer provided by an embodiment of the present application.
  • the master device Take the master device as a mobile phone, the slave device as a computer, application A as a video application, application B as a note application, and the slave device is not installed with application A, but is installed with application B, as an example to illustrate the task transfer method of the embodiment of the present application.
  • the master device is installed with a video application and a note application
  • the slave device is installed with a note application.
  • the control center page includes the device identification 301 of the main device, the identification card 601 of application A, the identification card 604 of application B, and the device identification 602 of the computer.
  • the user can drag the identification card 601 of application A toward the device identification 602 of the computer.
  • the device identification 602 of the computer automatically absorbs the identification card 601 of application A (as shown in c in FIG. 7A ).
  • the master device When the drag operation ends at a position near the device identifier 602 of the computer, the master device initiates a task flow to the computer, and the master device enters the interface shown in d in Figure 7A. In this interface, the identifier in the device identifier 602 of the computer changes to a connection identifier, so as to give the user a visual feedback of the ongoing task flow status.
  • the device identification 602 of the computer automatically absorbs the identification card 601 of application A.
  • the master device initiates task transfer to the computer.
  • the main device projects the content displayed by application A (for example, videos, photos, etc.) to the computer screen for display, thereby realizing single-window application screen projection.
  • application A for example, videos, photos, etc.
  • the main device When the task transfer between the main device and the computer is completed, the main device enters the interface shown in Figure 7A e, and the page does not display the identification card 601 of application A. Adaptively, the computer displays a projection window 703, which displays the content of application A (as shown in Figure 6B).
  • the master device When the master device exits the control center after the transfer is completed, the master device enters the page shown in f in Figure 7A from the page shown in e in Figure 7A. In the page shown in f in Figure 7A, the application page corresponding to the B application is displayed in full screen.
  • the main device can exit the control center through the exit button 306 or through a side-slide operation.
  • the embodiment of the present application does not limit the specific operation of exiting the control center.
  • FIG7B is a schematic diagram of an interface for task transfer provided in an embodiment of the present application.
  • the master device is a mobile phone
  • the slave device is a computer
  • application A is a video application
  • application B is a note application
  • application B is installed on the slave device as an example to illustrate the task transfer method of the embodiment of the present application.
  • the master device is installed with a video application and a note application
  • the slave device is installed with a note application.
  • the control center page includes the device identification 301 of the main device, the identification card 601 of application A, the identification card 604 of application B, and the device identification 602 of the computer.
  • the user can drag the identification card 604 of application B toward the device identification 602 of the computer.
  • the device identification 602 of the computer automatically absorbs the identification card 604 of application B (as shown in c in FIG. 7B ).
  • the master device When the drag operation ends at a position near the device identifier 602 of the computer, the master device initiates a task flow to the computer, and the master device enters the interface shown in d in Figure 7B. In this interface, the identifier in the device identifier 602 of the computer changes to a connection identifier, so as to give the user a visual feedback of the ongoing task flow status.
  • the device identification 602 of the computer automatically absorbs the identification card 604 of application B.
  • the main device initiates a task flow to the computer.
  • both the B application installed in the computer and the B application installed on the main device support continuation.
  • the main device exits the editing state of the B application, and controls the computer to open the B application and display the application page corresponding to the B application to achieve display content continuation.
  • the host device When the task transfer between the host device and the computer is completed, the host device enters the interface shown in Figure 7B e, and the page does not display the identification card 604 of application B. Adaptively, the computer opens application B and displays the application page corresponding to application B (as shown in Figure 6D).
  • the master device When the master device exits the control center after the transfer is completed, the master device enters the page shown in f in FIG. 7B from the page shown in e in FIG. 7B.
  • the page displays the application page corresponding to application A and the application page corresponding to application B in a split screen.
  • application B exits the editing state.
  • the master device if the master device is in the editing state while the B application is performing task flow, the master device exits the editing state.
  • FIG7C is a schematic diagram of an interface for task transfer provided in an embodiment of the present application.
  • the master device as a mobile phone
  • the slave device as a large-screen device
  • application A as a video application
  • application B as a note application
  • a method for task transfer in another embodiment of the present application is introduced.
  • the master device is installed with a video application and a note application.
  • the control center page includes the device identification 301 of the main device, the identification card 601 of application A, and the device identification 605 of the large-screen device.
  • the user can drag the identification card 601 of application A toward the device identification 605 of the large-screen device by dragging.
  • the device identification 605 of the large-screen device automatically absorbs the identification card 601 of application A (as shown in c in FIG. 7C ).
  • the master device When the drag operation ends near the device identifier 605 of the large-screen device, the master device initiates a task transfer to the large-screen device, and the master device enters the interface shown in d in Figure 7C. In this interface, the identifier in the device identifier 605 of the large-screen device changes to a connection identifier, so as to visually feedback the status of the ongoing task transfer to the user.
  • the device identification 605 of the large-screen device automatically absorbs the identification card 601 of application A.
  • the mobile phone initiates a task flow to the large-screen device.
  • the master device Since the slave device is a large-screen device, the master device projects the content displayed by application A (for example, videos, photos, etc.) to the screen of the large-screen device for display, thereby realizing same-source screen projection.
  • application A for example, videos, photos, etc.
  • the main device When the task transfer between the main device and the computer is completed, the main device enters the interface shown in Figure 7C e, and the page does not display the identification card 601 of application A. Adaptively, the content displayed on the large-screen device is the same as that displayed on the main device (as shown in Figure 7D a).
  • the main device When the main device exits the control center after the transfer is completed, the main device enters the application page of application A shown in f in FIG7C from the page shown in e in FIG7C. Adaptively, the content displayed on the large-screen device is the same as the content displayed on the main device (as shown in b in FIG7D).
  • the main device can exit the control center through the exit button 306 or through a side-slide operation.
  • the embodiment of the present application does not limit the specific operation of exiting the control center.
  • the main device splits the screen in an up-down split mode.
  • the main device can also split the screen in a left-right split mode, and the embodiments of the present application do not limit the split mode.
  • the identification cards of the applications displayed from left to right on the control center page correspond to the applications displayed from top to bottom in the split screen interface.
  • the identification cards of the applications displayed from left to right on the control center page correspond to the applications displayed from top to bottom in the split screen interface.
  • 8A is a schematic diagram of an interface for task transfer provided by an embodiment of the present application, taking the main device as a mobile phone, application A as a video application, and the small window application as a note application as an example.
  • the page shown in FIG8A includes: an application page corresponding to application A, and a page 801 corresponding to the small window application.
  • the main device receives a three-finger upward swipe operation from the user, it enters the control center page shown in b in FIG8A.
  • the control center page includes the device identification 301 of the main device, the identification card 601 of application A, the device identification 602 of the computer, and the device identification 605 of the large screen device, but does not include the identification card corresponding to the small window application.
  • the small window application can be any application such as notes, instant messaging, etc., and the embodiment of the present application does not limit this.
  • the user can drag the identification card 601 of application A to the device identification 302 of the slave device (e.g., the device identification 602 of the computer, the device identification 605 of the large-screen device, etc.) to transfer the task.
  • the specific process of task transfer is similar to the process of Figures 6A to 7D above, and will not be repeated here.
  • the page corresponding to the small window application is reduced and located on the side of the main device.
  • the task flow mode is single-window projection; when the main device exits the control center after the task flow is completed, the main device displays the main page and the reduced small window application 802 (as shown in c in Figure 8A).
  • the reduced small window application 802 is located on the side of the main device.
  • the task flow mode is to continue; when the main device exits the control center after the task flow is completed, the main device displays the application page of application A and the reduced small window application 802 (as shown in d in Figure 8A).
  • application A when the master device is performing task flow, application A is in a playing state; after the master device exits the control center page, application A stops playing the video, or exits the video playback page and returns to the play list interface.
  • the main device can exit the control center through the exit button 306 or through a side-slide operation.
  • the embodiment of the present application does not limit the specific operation of exiting the control center.
  • the task transfer mode is same-source screen projection; when the main device exits the control center after the task transfer is completed, the main device displays the main page and the reduced small window application 802 (as shown in d in Figure 8A).
  • the reduced small window application 802 is located on the side of the main device.
  • FIG8B is a schematic diagram of an interface for task transfer provided in an embodiment of the present application.
  • the page shown in FIG8B includes: an application page corresponding to the split-screen display of application A, an application page corresponding to the split-screen display of application C, and a page 801 corresponding to the small window application.
  • the task transfer method of the embodiment of the present application is illustrated by taking the main device as a mobile phone, application A as a video application, application C as a news application, and small window application as a note application as an example.
  • the control center page includes the device identification 301 of the main device, the identification card 601 of application A, the identification card 803 of application C, the device identification 602 of the computer and the device identification 605 of the large-screen device, but does not include the identification card corresponding to the small window application.
  • the user can drag the task identifier 303 (e.g., the identifier card 601 of application A, the identifier card 803 of application B) toward the device identifier 302 of the slave device (e.g., the device identifier 602 of the computer, the device identifier 605 of the large-screen device, etc.) to transfer the task.
  • the task identifier 303 e.g., the identifier card 601 of application A, the identifier card 803 of application B
  • the slave device e.g., the device identifier 602 of the computer, the device identifier 605 of the large-screen device, etc.
  • the page corresponding to the small window application is reduced and located on the side of the main device.
  • the master device displays the page corresponding to application A, the page corresponding to application B, and the reduced small window application 802 (as shown in c in FIG. 8B ).
  • the reduced small window application 802 is located on the side of the master device.
  • the task flow mode is single-window projection; when the main device exits the control center after the task flow is completed, the main device displays the application page of application C and the reduced small window application 802 (as shown in d in Figure 8B).
  • the reduced small window application 802 is located on the side of the main device.
  • the task flow mode is same-source screen projection; when the main device exits the control center after the task flow is completed, the main device displays the page corresponding to application A and the reduced small window application 802 (as shown in e in Figure 8B).
  • the reduced small window application 802 is located on the side of the main device.
  • the main device can exit the control center through the exit button 306 or through a side-slide operation.
  • the embodiment of the present application does not limit the specific operation of exiting the control center.
  • FIG8C is a schematic diagram of an interface for task flow provided in an embodiment of the present application.
  • the page shown in FIG8C includes: a main page, and a page 801 corresponding to the small window application.
  • the main device receives a three-finger swipe up operation from the user, it enters the control center page shown in b in FIG8C.
  • the control center page includes a device identifier 301 of the main device and a device identifier 302 of the slave device, but does not include a task identifier 303.
  • the main device when the main device receives a quick operation, the main device also displays a dynamic special effect.
  • the dynamic special effect can refer to the above related description, which will not be repeated here.
  • the task flow mode between the master device and the slave device is same-source screen projection.
  • the slave device is any one of a mobile phone, PC, or tablet
  • the slave device has the corresponding application installed, and the applications installed on the master and slave devices support continuation, the task flow mode between the master and slave devices is continuation;
  • the slave device is any one of a mobile phone, PC, or tablet, and the slave device does not have the corresponding application installed, the task flow mode between the master and slave devices is heterogeneous screen projection;
  • the slave device is any one of a mobile phone, PC, or tablet, the slave device has the corresponding application installed, and the application installed on any of the master and slave devices does not support continuation, the task flow mode between the master and slave devices is heterogeneous screen projection.
  • the task transfer mode between the master device and the slave device can refer to the following Table 1, which will not be repeated here.
  • task transfer may fail due to various reasons, including but not limited to: the slave device is locked, the slave device is dormant, the slave device does not support transfer, the application does not support transfer, network anomalies, etc.
  • Fig. 9 is a schematic diagram of a page of a control center provided by an embodiment of the present application.
  • the page shown in a in Fig. 9 includes: a device identification 301 of the main device, an identification card 601 of the A application, and a device identification 602 of the computer.
  • the user can drag the identification card 601 of application A toward the device identification 602 of the computer.
  • the device identification 602 of the computer automatically absorbs the identification card 601 of application A (as shown in b in FIG. 9 ).
  • the master device When the drag operation ends at a position near the device identifier 602 of the computer, the master device initiates a task flow to the computer, and the master device enters the interface shown in c in Figure 9. In this interface, the identifier in the device identifier 602 of the computer changes to a connection identifier, so as to visually feedback the status of the ongoing task flow to the user.
  • the device identification 602 of the computer automatically absorbs the identification card 601 of application A.
  • the master device initiates a task flow to the computer.
  • the master device enters the interface shown in Figure 9c and enters the interface shown in Figure 9d.
  • the interface includes: the device identification 301 of the master device, the identification card 601 of the A application and the device identification 602 of the computer.
  • a prompt message may be displayed on the control center page of the master device to prompt the user that the transfer has failed.
  • control center page shown in d in Fig. 9 further includes: a prompt message 901.
  • the prompt message 901 is used to prompt the user that the task transfer fails.
  • the prompt message 901 may be a text message, for example, “Connection failed”.
  • the prompt message 901 may be displayed in the form of a bubble or a toast message.
  • the embodiment of the present application does not limit the specific display form of the prompt message 901.
  • the prompt message 901 may disappear after being displayed for a period of time, or after receiving any operation. In this way, the obstruction of the control center page by the prompt message 901 can be reduced.
  • the embodiment of the present application does not limit the disappearance method of the displayed prompt message 901.
  • the prompt message 901 is also used to prompt the user the reason for the transfer failure. In this way, the user can adjust the slave device based on the failure reason to facilitate task transfer again, thereby improving the user experience.
  • the text corresponding to the prompt message 901 may be: “Connection failed, please unlock the peer end and try again”, “Task transfer to slave device is not supported yet”, “Application transfer to slave device is not supported yet”, “Network connection is unstable, please try again later”, etc.
  • the specific content of prompt message 901 is not limited in the embodiment of the present application.
  • the device coordination function of the control center is described below with reference to FIGS. 10 to 14 .
  • the control center may have the following three situations: the first situation is that the master device has searched for one or more slave devices; the second situation is that the master device has not searched for the slave device; the third situation is that the master device is in collaboration.
  • control center pages corresponding to the three situations are described below in conjunction with FIG. 10 .
  • the first case if the master device has searched for one or more slave devices, the control center page is shown as a in Figure 10.
  • the control center page includes the device identification 301 of the master device and the device identification 302 of the slave device.
  • the position, shape, etc. of the device identification 301 of the master device and the device identification 302 of the slave device can refer to the corresponding description in Figure 3 above, and will not be repeated here.
  • the main device receives an operation to open the control center and enters the control center page shown in a in FIG. 10 .
  • the control center page also displays a prompt message 1001.
  • the prompt message 1001 is used to prompt the user to understand the collaborative function.
  • the prompt message 1001 may disappear after receiving the user operation, or may disappear after a period of time (for example, 15S).
  • the master device may display the prompt message 1001 when entering the control center page for the first N times, or may display the prompt message 1001 only when entering the control center page for the first time.
  • the embodiment of the present application does not specifically limit the display conditions and disappearance conditions of the prompt message 1001.
  • the second situation if the master device fails to search for the slave device, the control center page is shown as b in Figure 10.
  • the control center page includes the device identification 301 of the master device, but does not include the device identification 302 of the slave device.
  • the main device receives an operation to open the control center and enters the control center page shown in b in FIG. 10 .
  • the control center page also displays a prompt message 1002.
  • the prompt message 1002 is used to prompt the user why the slave device is not found. The reasons include but are not limited to: the nearby device is not logged in to the same account and the smart interconnection service is turned on, the nearby device does not turn on Bluetooth and WLAN, the nearby device does not support collaboration with the local device, etc.
  • a prompt message 1002 is displayed; when a slave device is searched and the device identification 302 of the slave device is displayed, the prompt message 1002 disappears.
  • the master device when the master device searches for the slave device, the master device can enter the page shown in a of FIG. 10 from the page shown in b of FIG. 10 .
  • the third case if the master device is in collaboration, the control center page is shown as c in FIG10 .
  • the control center page includes a collaboration indicator 1003 .
  • the collaborative logo 1003 may be a graphical logo, such as an icon, or other skeuomorphic elements, etc.
  • the device logo of the main device and the device logo of the collaborative device may be merged to form the collaborative logo 1003.
  • the embodiment of the present application does not limit the specific shape of the collaborative logo.
  • the control center page also includes a collaboration type card 1004 , and the collaboration type card 1004 includes multiple buttons, for example: a multi-screen collaboration button 1005 and a disconnect button 1006 .
  • buttons displayed on the collaboration type card are consistent with the collaboration types supported between the master device and the slave device.
  • the master device is a mobile phone and the slave device is any device among PC, PAD, and large-screen device
  • the collaboration between the master device and the slave device is the same-source screen projection.
  • the collaboration type card 1004 displayed on the control center page may include a multi-screen collaboration button 1005 and a disconnect button 1006 (as shown in c in Figure 10).
  • the collaboration between the master device and the slave device can be any one of screen extension, screen mirroring, and keyboard and mouse sharing.
  • the collaboration type card 1004 displayed on the control center page may include a screen extension button 1007, a screen mirroring button 1008, a keyboard and mouse sharing button 1009, and a disconnect button 1006 (as shown in d in FIG. 10 ).
  • the collaboration type between the master device and the slave device is switched to screen extension; when the user clicks the screen mirroring button 1008, the collaboration type between the master device and the slave device is switched to screen mirroring; when the user clicks the keyboard and mouse sharing button 1009, the collaboration type between the master device and the slave device is switched to keyboard and mouse sharing.
  • the collaboration types supported between the master device and the slave device may be as shown in Table 2.
  • connection process and disconnection process between the master device and the slave device are described below in conjunction with FIG. 11A and FIG. 11B .
  • the device identifier 301 of the master device automatically absorbs the device identifier 602 of the computer (as shown in b of FIG. 11A).
  • the master device and the computer begin to establish a collaborative connection, and the master device enters the interface shown in c of FIG. 11A.
  • the identifier in the device identifier 602 of the computer becomes a connection identifier, so as to visually feedback the status of the ongoing collaborative connection to the user.
  • the device ID 301 of the main device automatically absorbs the device ID 602 of the computer.
  • the main device and the computer begin to establish a collaborative connection.
  • the third threshold value may be 20 pixels (px) or any other value, which is not limited here.
  • the main device When the collaborative connection between the main device and the computer is established, the main device enters the page shown in d in Figure 11A, which includes a collaborative logo 1003 and a collaborative type card 1004.
  • the computer displays a cooperation window 1101, and the content displayed in the window is the same as that displayed by the main device.
  • the main device enters the page shown in e in FIG. 11A , which includes the device identification 301 of the main device and the device identification 602 of the computer.
  • a prompt message may be displayed on the control center page of the master device to prompt the user that the collaborative connection has failed to be established.
  • the page shown in e in 11A also includes: prompt message 1101.
  • Prompt message 1101 is used to prompt the user that the collaborative connection establishment failed.
  • Prompt message 1101 can be a text message, for example, "Connection failed”.
  • Prompt message 1101 can be displayed in the form of a bubble or in the form of a toast message.
  • the embodiment of the present application does not limit the specific display form of prompt message 1101.
  • the prompt message 1101 may disappear after being displayed for a period of time, or after receiving any operation. In this way, the obstruction of the control center page by the prompt message 1101 can be reduced.
  • the embodiment of the present application does not limit the disappearance method of the displayed prompt message 1101.
  • the prompt message 1101 is also used to prompt the user the reason for the transfer failure. In this way, the user can adjust the slave device based on the failure reason to facilitate task transfer again, thereby improving the user experience.
  • the text corresponding to the prompt message 1101 may be: “Connection failed, please unlock the other end and try again”, “Task transfer to the slave device is not supported temporarily”, “Application transfer to the slave device is not supported temporarily”, “Network connection is unstable, please try again later”, etc.
  • the embodiment of the present application does not limit the specific content of the prompt message 1101.
  • the device identifier 301 of the master device cancels the adsorption of the device identifier 602 of the computer, and the position of the device identifier 602 of the computer is related to the position of the drag operation (as shown in b of FIG. 11B).
  • the master device disconnects the collaborative connection with the computer, and the master device enters the interface shown in c of FIG. 11B, and the device identifier 602 of the computer is at the end of the slave device sequence.
  • the device ID 301 of the main device cancels the adsorption of the device ID 602 of the computer.
  • the main device disconnects the collaborative connection with the computer.
  • the control center page continues to display the collaboration type card 1004 until the collaboration is disconnected. If the user clicks the disconnect button 1006 shown in d in FIG. 11A , the master device disconnects from the computer, and the master device enters the page shown in c in FIG. 11B .
  • the page includes the device identification 301 of the master device and the device identification 602 of the computer.
  • the device identification 602 of the computer is at the end of the slave device sequence.
  • the master device disconnects the collaboration and establishes a collaborative connection with the slave device corresponding to the device identifier of the dragged slave device.
  • the master device disconnects the collaboration with the slave device 2 and establishes collaboration with the slave device 1.
  • the master device enters the page shown in b in Figure 12 from the page shown in a in Figure 12.
  • the control center page displays the collaboration type card 1004, and does not display the task identifier 303 (as shown in b in FIG. 13A).
  • the control center page displays the task identifier 303, as shown in c in FIG. 13A.
  • the master device is in collaboration, the user enters the control center page, and the control center page displays the task identifier 303, as shown in c in FIG. 13A.
  • the master device when the master device is in collaboration, when the master device receives a three-finger upward slide operation in the interface shown in a of FIG13A, the master device enters the page shown in b of FIG16A.
  • the page includes a collaboration type card 1004, but does not include a task identifier 303.
  • the master device displays the page shown in c of FIG13A.
  • the page includes the task identifier 303.
  • the control center page displays a task identifier 303 when a user enters the control center page.
  • the user can drag the device identifier of the slave device to the vicinity of the device identifier of the master device to achieve collaborative connection between the master device and the slave device.
  • the master device when the master device receives a three-finger swipe-up operation in the interface shown in a of FIG13A , the master device enters the page shown in a of FIG13B , which includes the device identifier 301 of the master device, the task identifier 303 and the device identifier 602 of the computer, but does not include the collaboration type card 1004.
  • the device identifier 301 of the master device automatically absorbs the device identifier 602 of the computer.
  • the master device When the drag operation ends at a position near the device identifier 301 of the master device, the master device establishes a collaborative connection with the computer, and the master device enters the page shown in c in FIG. 13B .
  • the master device does not display the task identifier 303 (as shown in b in Figure 13B), and when the master device determines the collaboration mode with the slave device, it does not consider the currently running business, but instead determines the collaboration mode with reference to Table 2 shown above.
  • the main device before the main device enters the control center page, the main device also displays a guide page to prompt the user to agree to the privacy agreement, turn on Bluetooth and WLAN, log in to the account, etc.
  • Fig. 14 is a schematic diagram of a page of a master device provided in an embodiment of the present application, taking the first time the master device enters the control center as an example.
  • the master device if the master device receives a three-finger upward swipe operation by the user, the master device enters the page shown in a of FIG14.
  • the page includes: a guide pop-up window 1701.
  • the master device When the user clicks the consent button 1702, the master device enters the page shown in b of FIG14, which displays a privacy agreement and a consent control 1703.
  • the master device When the user clicks the consent control 1703, the master device enters the page shown in c of FIG14, which includes: a login control.
  • the main device When the user clicks the login control 1704, the main device enters the page shown in d in Figure 14.
  • the page includes an opening control 1705.
  • the opening control 1705 When the user clicks the opening control 1705, the main device enters the control center page.
  • the main device If the main device has turned on Bluetooth and WLAN when the user clicks the login control 1704, the main device enters the control center page and the page shown in d in Figure 14 is not displayed.
  • the above embodiment is described by taking a mobile phone as the main device.
  • the main device may also be a computer, a pad, etc.
  • the task flow mode, interface display, and coordination of other devices such as a computer and a pad as the main device can refer to the above description of the mobile phone as an example, and will not be repeated here.
  • FIG15 is a flowchart of a multi-device task transfer method provided in an embodiment of the present application. The method includes:
  • the main device displays a first interface, where the first interface includes a page of a first application.
  • the first interface is a page of an application, and the first interface may correspond to the interface shown in a in FIG. 6A and a in FIG. 7A.
  • the page of the first application may correspond to the A application page shown in FIG. 6A.
  • the first application may be a video application or other types of applications, which is not limited in the embodiment of the present application.
  • the master device receives a first operation.
  • the first operation is used to enter the control center page.
  • the first operation can be a quick gesture operation, a voice operation, or other types of operations, which are not limited in the present embodiment.
  • the quick gesture operation can be a gesture operation such as sliding up with three fingers.
  • the master device In response to the first operation, the master device displays a second interface, where the second interface includes a device identification of the first slave device.
  • the second interface is a control center page, which may correspond to the interface shown in b of Figure 6A and the interface shown in b of Figure 7A.
  • the form of the device identification of the first slave device may refer to the description of the device identification of the slave device, which will not be repeated here.
  • the master device receives a second operation for the device identification of the first slave device.
  • the second operation is used to select the first slave device. Based on different pages, the selection method can be different, such as drag selection, or clicking the device logo of the first slave device to select, etc.
  • the embodiment of the present application does not limit the type of the second operation.
  • the master device displays the third interface, and sends the page of the first application to the first slave device, so that the first slave device displays the page of the first application.
  • the third interface is the control center page after the task flow is successful, which may correspond to the interface shown in e in FIG. 6A and e in FIG. 7A .
  • S1506 The master device receives the third operation.
  • the third operation is a return operation.
  • the return operation in the embodiment of the present application refers to the operation of calling the back instruction. Or it can also be understood as the operation of exiting the control center page.
  • the third operation can be a click operation, a shortcut operation, or a voice operation.
  • the embodiment of the present application does not limit the specific type of the third operation.
  • the master device displays a fourth interface, which does not include a page of the first application.
  • the fourth interface is the interface displayed after exiting the control center, which may correspond to the interface shown in f in Figure 6A and f in Figure 7A. It is understandable that after the main device streams the first application through the heterogeneous screen projection method, the main device closes the first application and does not display the page of the first application.
  • the main device displays a fifth interface, which includes a page of the second application.
  • the fifth interface is an application page, and the fifth interface may correspond to the interface shown in a in FIG. 6C and a in FIG. 7B.
  • the page of the second application may correspond to the B application page shown in FIG. 6C.
  • the second application may be a note application or other types of applications, which is not limited in the embodiment of the present application.
  • the fourth operation is used to enter the control center page.
  • the fourth operation can be a quick gesture operation, a voice operation, or other types of operations, which are not limited in the present embodiment.
  • the quick gesture operation can be a gesture operation such as sliding up with three fingers.
  • the master device In response to the fourth operation, the master device displays a sixth interface, which includes the device of the first slave device. logo.
  • the sixth interface is the control center page, which may correspond to the interface shown in b in FIG. 6C or the interface shown in b in FIG. 7B .
  • S1511 The master device receives a fifth operation for the device identification of the first slave device.
  • the fifth operation is used to select the first slave device. Based on different pages, the selection method can be different, such as drag selection, or clicking the device logo of the first slave device to select, etc.
  • the embodiment of the present application does not limit the type of the fifth operation.
  • the master device displays the seventh interface and sends the content displayed on the page of the second application to the first slave device, so that the first slave device starts the third application, the third application corresponds to the second application, and the content displayed on the page of the third application is the same as the content displayed on the page of the second application.
  • the seventh interface is the control center page after the task flow is successful, which may correspond to the interface shown in e in Figure 6C and e in Figure 7B.
  • the third application and the second application may be understood as different versions of the same application, for example, a note application on a mobile phone and a note application on a computer.
  • the sixth operation is a return operation.
  • the return operation in the embodiment of the present application refers to the operation of calling the back instruction. Or it can also be understood as the operation of exiting the control center page.
  • the sixth operation can be a click operation, a shortcut operation, or a voice operation.
  • the embodiment of the present application does not limit the specific type of the sixth operation.
  • the master device displays an eighth interface, which includes a page of the second application.
  • the eighth interface is the interface displayed after exiting the control center, which may correspond to the interface shown in f in FIG. 6C and f in FIG. 7B .
  • the first application and the second application are adapted to different methods, and can be respectively transferred to the first slave device through heterogeneous screen projection and connection.
  • the master device can automatically adjust the flow mode according to the application to achieve intelligent flow, without the need for users to find the corresponding flow entrances separately, reducing user memory costs and improving user experience.
  • the second interface also includes the logo of the first application
  • the sixth interface also includes the logo of the second application
  • the second operation is to drag the logo of the first application to the vicinity of the device logo of the first slave device
  • the fifth operation is to drag the logo of the second application to the vicinity of the device logo of the first slave device.
  • the identifier of the first application and the identifier of the second application may both correspond to the task identifier mentioned above, which will not be described in detail here.
  • the identifier of the first application may correspond to the A application task identifier
  • the identifier of the second application may correspond to the B application task identifier.
  • the vicinity of the device identifier of the first slave device may be understood as a situation where the distance to the device identifier of the first slave device is less than a second threshold.
  • control center page displays the logo of the corresponding application, which is simple, intuitive, and clear at a glance.
  • the slave device can be selected by dragging the logo of the application to the vicinity of the device logo of the slave device, which is simple to operate and easy to understand.
  • the first operation is the same as the fourth operation, and the first operation is any one of the following operations: a three-finger swipe up operation, a double-click operation, a three-finger swipe down operation, and a triple-click operation.
  • the third operation is a left-swipe operation or a right-swipe operation at the edge of the screen, or a click operation on the first control displayed on the third interface;
  • the sixth operation is a left-swipe operation or a right-swipe operation at the edge of the screen, or a click operation on the first control displayed on the seventh interface.
  • the first control may correspond to an exit control. It is understandable that the master device may exit the control center page by sliding sideways, or by clicking the exit control on the control center page.
  • the third operation and the sixth operation may be the same or different.
  • the master device is any one of a mobile phone, a computer, and a tablet
  • the first slave device is any one of a mobile phone, a computer, and a tablet.
  • the fifth interface and the eighth interface are different interfaces, the fifth interface includes a first page of the second application, the eighth interface includes a second page of the second application, and the first page of the second application is different from the second page of the second application.
  • the fifth interface may correspond to a page being edited, or other pages being modified.
  • the second page exits the page being edited, or exits the page being modified.
  • the master device when the master device performs task flow through the connection, it will exit the editing, modifying and other states, and the content of the interface displayed by the application before and after the task flow will be different.
  • the second application is a note application
  • the first page of the second application is an editing page, and the editing page includes the content of the first note
  • the second page of the second application is a list page, and the list page includes the identifier of the first note.
  • the task flow in the embodiment of the present application can be applicable to the note application, and the content of the interface displayed by the application is different before and after the note application flow.
  • the first interface only includes a page of the first application
  • the fourth interface is the desktop of the main device.
  • the page that only includes the first application may refer to a page that displays the first application in full screen, or may refer to a page that displays the first application in an area other than the status bar area above.
  • the page that only includes the first application may be understood as a page that does not include pages of other applications except the page of the first application. The embodiment of the present application does not specifically limit this.
  • the main device closes the first application and does not display the page of the first application. If the main device only runs the first application in the foreground, after the first application is transferred through the heterogeneous screen projection method, the desktop is displayed.
  • the first interface also includes a page of a fourth application, and the page of the fourth application and the page of the first application are displayed in split screen; the fourth interface includes a page of the fourth application.
  • the fourth application may be a note application or other types of applications, which is not limited in the present embodiment.
  • the fourth application may be the same as the second application or different from the second application.
  • the page of the fourth application is displayed after the first application is transferred through the heterogeneous screen projection method.
  • the fifth interface also includes a page of a fifth application, and the page of the fifth application and the page of the second application are displayed in split screen; the eighth interface also includes a page of the fifth application, and the page of the second application and the page of the fifth application are displayed in split screen.
  • the fifth application may be a video application or other types of applications, which is not limited in the present embodiment.
  • the fifth application may be the same as the first application or different from the first application.
  • the main device runs the second application and the fifth application in the foreground, the first application is transferred in a continuous manner. After the second application, the page of the second application and the page of the fifth application are displayed.
  • the first interface also includes a first floating window, which displays a page of a sixth application; the second interface does not include the logo of the sixth application, and the fourth interface also displays a second control; in response to the user's operation of the second control, the first floating window is displayed on the fourth interface.
  • the application displayed by the floating window may correspond to the small window application mentioned above.
  • the sixth application may be a video application or other types of applications, which is not limited in the embodiments of the present application.
  • the second control may correspond to a reduced small window application, which may also be referred to as a floating ball.
  • the fourth interface may correspond to the interface shown in FIG. 8A or FIG. 8B.
  • the small window application does not perform task transfer. After the task transfer, the small window application shrinks to the edge of the screen. The display of the small window application can be restored through the shrunk small window application.
  • the fifth interface further includes a second floating window, and the second floating window displays a page of the seventh application; the sixth interface does not include the logo of the seventh application, and the eighth interface further displays a third control; in response to the user's operation on the third control, the second floating window is displayed on the eighth interface.
  • the eighth interface may correspond to the interface shown in FIG. 8A or FIG. 8B.
  • the application displayed through the floating window may correspond to the small window application mentioned above.
  • the seventh application may be a video application or other types of applications, which is not limited in the embodiments of the present application.
  • the third control may correspond to a reduced small window application, which may also be referred to as a floating ball. It is understandable that the small window application does not perform task transfer. After the task transfer, the small window application is reduced to the edge of the screen. The display of the small window application can be restored through the reduced small window application.
  • the master device is any one of a mobile phone, a computer, and a tablet
  • the first slave device is a large screen
  • the fourth interface includes a page of the first application.
  • the first application transfers tasks by means of same-source screen projection. Before and after the task transfer in same-source screen projection, the application page remains unchanged and the displayed content is the same. The page displayed on the slave device is the same as the page displayed on the master device.
  • the first interface also includes a page of a fourth application.
  • the fourth interface does not include the page of the fourth application.
  • the application page remains unchanged and the displayed content is the same before and after the task flow in the same-source screen projection.
  • the page displayed on the slave device is the same as the page displayed on the master device.
  • the master device is any one of a mobile phone, a computer, and a tablet
  • the first slave device is a large screen
  • the page of the second application included in the fifth interface and the page of the second application included in the eighth interface are the same page.
  • the second application transfers tasks by means of same-source screen projection. Before and after the task transfer in same-source screen projection, the application page remains unchanged and the displayed content is the same. The page displayed on the slave device is the same as the page displayed on the master device.
  • the page of the first application is a page for playing videos.
  • the method also includes: the master device displays a ninth interface, the ninth interface includes a page of an eighth application; the master device receives a seventh operation; in response to the seventh operation, the master device displays a tenth interface, the tenth interface includes a device identifier of the second slave device; the master device receives an eighth operation for the device identifier of the second slave device; in response to the eighth operation, the master device displays an eleventh interface, the eleventh interface includes the device identifier of the master device and the device identifier of the second slave device, wherein the device identifier of the master device is connected to the device identifier of the second slave device.
  • the ninth interface is an application page, which may correspond to the interface shown in a in FIG. 6A and a in FIG. 6C above, or other pages running a foreground application.
  • the seventh operation is similar to the first operation, and the specific description of the first operation may be referred to above, which will not be repeated here.
  • the tenth interface may correspond to a control center page that is not in a collaborative state.
  • the eleventh interface may correspond to the control center page in the collaboration.
  • the eighth operation is used to select the device identifier of the second slave device, which may be a click operation or a drag operation.
  • the embodiment of the present application does not limit the specific type of the eighth operation.
  • connected can be connected, can be close to each other (such as next to each other), which is not limited here.
  • control center page can also realize the collaborative connection between the master device and the slave device.
  • the eighth operation is an operation of dragging the device identifier of the second slave device to near the device identifier of the master device.
  • the vicinity of the device identification of the main device may be understood as a situation where the distance to the device identification of the main device is less than a third threshold.
  • the tenth interface also includes the logo of the eighth application, and the eleventh interface does not include the logo of the eighth application.
  • control center page that is not in a collaborative state displays the application logo and can perform task transfer; the control center page in a collaborative state does not display the application logo and cannot perform task transfer.
  • the eleventh interface also includes a first identifier, and the first identifier indicates the collaboration type between the master device and the second slave device.
  • the first identifier can correspond to same-source screen projection, screen extension, screen mirroring, keyboard and mouse sharing, etc.
  • the eleventh interface also includes a second identifier
  • the method also includes: the master device receives a ninth operation for the second identifier; in response to the ninth operation, the master device and the second slave device switch to a collaboration type corresponding to the second identifier.
  • the second identifier may correspond to collaborative types such as same-source screen projection, screen extension, screen mirroring, keyboard and mouse sharing, etc.
  • the ninth operation may be a click operation, a touch operation, etc., and the embodiment of the present application does not limit the ninth operation.
  • the user can adjust the collaboration type between the master device and the slave device through the second identifier, switch the collaboration mode, and improve the user experience.
  • the eleventh interface also includes a fourth control
  • the method also includes: the master device receives a tenth operation for the fourth control; in response to the tenth operation, the master device disconnects from the second slave device; the master device displays a twelfth interface, the twelfth interface includes a device identifier of the master device and a device identifier of the second slave device, and the device identifier of the master device is not connected to the device identifier of the second slave device.
  • the control center page after the twelfth interface is not disconnected from the collaborative connection may correspond to the interface shown in FIG. 11A.
  • the fourth control may correspond to a disconnection control (button).
  • the tenth operation may be a click operation, a touch operation, or other types of operations, which are not specifically limited in the embodiments of the present application.
  • connection between the master device and the slave device can be disconnected through the fourth control, and the collaboration can be disconnected, which is easy to operate.
  • the method also includes: the master device receives an eleventh operation for the device identification of the second slave device on the eleventh interface; in response to the eleventh operation, the master device disconnects from the second slave device; the master device displays a thirteenth interface, the thirteenth interface includes the device identification of the master device and the device identification of the second slave device, and the device identification of the master device is not connected to the device identification of the second slave device.
  • the thirteenth interface is a control center page after the collaborative connection is not disconnected, which may correspond to the interface shown in Figure 11B.
  • the eleventh operation may be a drag operation or other types of operations, which are not specifically limited in the embodiments of the present application.
  • connection between the master device and the slave device can be disconnected by dragging and dropping, and the collaboration is disconnected, which is easy to operate.
  • the eleventh interface further includes an identifier of a third slave device, and the device identifier of the master device is not connected to the device identifier of the third slave device; the method further includes: the master device receives a device identifier for the third slave device at the eleventh interface; The master device displays a fourteenth interface, which includes the device identification of the master device, the device identification of the second slave device, and the identification of the third slave device, the device identification of the master device is connected to the device identification of the third slave device, and the device identification of the master device is not connected to the device identification of the second slave device.
  • the twelfth operation is used to switch the slave device connected to the master device.
  • the twelfth operation can be an operation of dragging the device identifier of the third slave device, or can be other types of operations, which are not limited in the embodiment of the present application.
  • the fourteenth interface can correspond to the interface shown in FIG. 12 .
  • the master device can switch the coordinated slave device to improve the user experience.
  • collaboration type includes any one of the following types: same-source screen projection, screen extension, screen mirroring, and keyboard and mouse sharing.
  • the "at" in the embodiment of the present application can be the instant when a certain situation occurs, or can be a period of time after a certain situation occurs, and the embodiment of the present application does not specifically limit this.
  • the display interface provided in the embodiment of the present application is only an example, and the display interface can also include more or less content.
  • the multi-device task transfer method of the embodiment of the present application has been described above, and the device for executing the multi-device task transfer method provided by the embodiment of the present application is described below. Those skilled in the art can understand that the method and the device can be combined and referenced with each other, and the relevant device provided by the embodiment of the present application can execute the steps in the multi-device task transfer method.
  • Figure 16 is a structural diagram of a multi-device task flow device provided in an embodiment of the present application.
  • the multi-device task flow device can be a terminal device in the embodiment of the present application, or it can be a chip or chip system in the terminal device.
  • a multi-device task transfer apparatus 2100 can be used in a communication device, a circuit, a hardware component or a chip, and the multi-device task transfer apparatus includes: a display unit 2101 and a processing unit 2102.
  • the display unit 2101 is used to support the display step performed by the multi-device task transfer apparatus 2100;
  • the processing unit 2102 is used to support the multi-device task transfer apparatus 2100 to perform information processing steps.
  • the multi-device task transfer apparatus 2100 may also include a communication unit 2103. Specifically, the communication unit is used to support the multi-device task transfer apparatus 2100 to perform the steps of sending and receiving data.
  • the communication unit 2103 may be an input or output interface, a pin or a circuit.
  • the multi-device task flow apparatus may further include: a storage unit 2104.
  • the processing unit 2102 and the storage unit 2104 are connected via a line.
  • the storage unit 2104 may include one or more memories, and the memory may be a device used to store programs or data in one or more devices or circuits.
  • the storage unit 2104 may exist independently and be connected to the processing unit 2102 of the multi-device task flow apparatus via a communication line.
  • the storage unit 2104 may also be integrated with the processing unit 2102.
  • the storage unit 2104 can store computer-executable instructions of the method in the terminal device so that the processing unit 2102 executes the method in the above embodiment.
  • the storage unit 2104 can be a register, a cache, or a RAM, etc.
  • the storage unit 2104 can be integrated with the processing unit 2102.
  • the storage unit 2104 can be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions.
  • the storage unit 2104 can be independent of the processing unit 2102.
  • the multi-device task transfer method provided in the embodiment of the present application can be applied to electronic devices with display functions.
  • the electronic device includes a terminal device.
  • the specific device form of the terminal device can refer to the above-mentioned related descriptions and will not be repeated here.
  • An embodiment of the present application provides an electronic device, which includes: a processor and a memory; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory, so that the electronic device executes the above method.
  • the embodiment of the present application provides a chip.
  • the chip includes a processor, and the processor is used to call a computer program in a memory to execute the technical solution in the above embodiment. Its implementation principle and technical effect are similar to those of the above related embodiments, and will not be repeated here.
  • the embodiments of the present application also provide a computer-readable storage medium.
  • the computer-readable storage medium stores a computer program.
  • the above method is implemented when the computer program is executed by the processor.
  • the method described in the above embodiment can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. If implemented in software, the function can be stored as one or more instructions or codes on a computer-readable medium or transmitted on a computer-readable medium.
  • Computer-readable media can include computer storage media and communication media, and can also include any medium that can transfer a computer program from one place to another.
  • the storage medium can be any target medium that can be accessed by a computer.
  • a computer readable medium may include RAM, ROM, compact disc read-only memory (CD-ROM) or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that is intended to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer.
  • any connection is appropriately referred to as a computer readable medium.
  • the software is transmitted from a website, server or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technologies such as infrared, radio and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwave are included in the definition of medium.
  • DSL digital subscriber line
  • Disk and optical disk as used herein include optical disk, laser disk, optical disk, digital versatile disk (DVD), floppy disk and Blu-ray disk, where disks usually reproduce data magnetically, while optical disks reproduce data optically using lasers. Combinations of the above should also be included in the scope of computer readable media.
  • An embodiment of the present application provides a computer program product, which includes a computer program.
  • the computer program When the computer program is executed, the computer executes the above method.
  • each flow process and/or box in the flow chart and/or block diagram and the combination of the flow chart and/or box in the flow chart and/or block diagram can be realized by computer program instructions.
  • These computer program instructions can be provided to the processing unit of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable device to produce a machine, so that the instructions executed by the processing unit of the computer or other programmable data processing device produce a device for realizing the function specified in one flow chart or multiple flows and/or one box or multiple boxes of the block chart.

Landscapes

  • Engineering & Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

本申请实施例提供多设备任务流转方法和相关装置。该方法包括：主设备显示包括第一应用的页面的第一界面；主设备响应于第一操作，显示包括第一从设备的设备标识的第二界面；主设备响应于第二操作，显示第三界面并向第一从设备发送第一应用的页面，第一从设备显示第一应用的页面；主设备显示包括第二应用的页面的第五界面；响应于第四操作，主设备显示包括第一从设备的设备标识的第六界面；主设备响应于第五操作，显示第七界面并向第一从设备发送第二应用的页面上显示的内容，第一从设备启动与第二应用相对应的第三应用。第一应用和第二应用分别通过异源投屏、接续流转至第一从设备，不同应用适配不同流转方式，实现智能流转，提升用户体验。

Description

多设备任务流转方法和相关装置
本申请要求于2022年11月22日提交中国国家知识产权局、申请号为202211474246.3、申请名称为“多设备任务流转方法和相关装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及终端技术领域，尤其涉及多设备任务流转方法和相关装置。
背景技术
多设备协同是一种应用于多个电子设备的分布式技术。利用多设备协同技术，两个或者多个电子设备之间可以进行跨系统、跨设备的协同，实现资源共享、协同操作。任务流转是一种实现应用在多个设备之间无缝接续的技术。
随着终端技术的不断发展，多设备协同已经产生了多种不同的任务流转方式，例如：同源投屏、接续、异源投屏等。
发明内容
本申请实施例提供一种多设备任务流转方法和相关装置，应用于终端技术领域。第一应用和第二应用分别通过异源投屏、接续流转至第一从设备，不同应用适配不同流转方式，实现智能流转，提升用户体验。
第一方面，本申请实施例提出一种多设备任务流转方法。该方法包括：主设备显示第一界面，第一界面包括第一应用的页面；主设备接收到第一操作；响应于第一操作，主设备显示第二界面，第二界面包括第一从设备的设备标识；主设备接收到针对第一从设备的设备标识的第二操作；响应于第二操作，主设备显示第三界面，并向第一从设备发送第一应用的页面，以使第一从设备显示第一应用的页面；主设备接收到第三操作，第三操作为返回操作；响应于第三操作，主设备显示第四界面，第四界面不包括第一应用的页面；主设备显示第五界面，第五界面包括第二应用的页面；主设备接收到第四操作；响应于第四操作，主设备显示第六界面，第六界面包括第一从设备的设备标识；主设备接收到针对第一从设备的设备标识的第五操作；响应于第五操作，主设备显示第七界面，并向第一从设备发送第二应用的页面上显示的内容，以使得第一从设备启动第三应用，第三应用与第二应用相对应，第三应用的页面显示的内容与第二应用的页面上显示的内容相同；主设备接收到第六操作，第六操作为返回操作；响应于第六操作，主设备显示第八界面，第八界面包括第二应用的页面。
本申请实施例中，第一界面为应用的页面，第一界面可以对应于图6A中的a、图7A中的a所示的界面。第一应用的页面可以对应于图6A所示的A应用页面。第一应用可以为视频类应用，也可以为其他类型的应用，本申请实施例对此不作限定。第一 操作用于进入控制中心页面。第一操作可以为快捷手势操作，也可以为语音操作，或其他类型的操作，本申请实施例对此不作限定。快捷手势操作可以为三指上划等手势操作。
第二界面为控制中心页面，可以对应于图6A中的b所示的界面、图7A中的b所示的界面。第一从设备的设备标识的形式可以参照实施例部分的说明，此处不再赘述。本申请实施例中，第二操作用于选取第一从设备。基于不同的页面，选取方式可以不同，可以为拖拽选取，也可以为点击第一从设备的设备标识选取等，本申请实施例对于第二操作的类型不作限定。
第三界面为任务流转成功后的控制中心页面，可以对应于图6A中的e、图7A中的e所示的界面。第三操作为返回操作。本申请实施例中的返回操作是指调用back指令的操作。或者也可以理解为退出控制中心页面的操作。第三操作可以为点击操作，也可以为快捷操作，还可以为语音操作，本申请实施例对于第三操作的具体类型不作限定。
第四界面为退出控制中心后显示的界面，可以对应于图6A中的f、图7A中的f所示的界面。可以理解的是，当主设备通过异源投屏方式流转第一应用后，主设备关闭第一应用，不显示第一应用的页面。
本申请实施例中，第五界面为应用的页面，第五界面可以对应于图6C中的a、图7B中的a所示的界面。第二应用的页面可以对应于图6C所示的B应用页面。第二应用可以为笔记应用，也可以为其他类型的应用，本申请实施例对此不作限定。第四操作用于进入控制中心页面。第四操作可以为快捷手势操作，也可以为语音操作，或其他类型的操作，本申请实施例对此不作限定。快捷手势操作可以为三指上划等手势操作。第六界面为控制中心页面，可以对应于图6C中的b所示的界面、图7B中的b所示的界面。
本申请实施例中，第五操作用于选取第一从设备。基于不同的页面，选取方式可以不同，可以为拖拽选取，也可以为点击第一从设备的设备标识选取等，本申请实施例对于第五操作的类型不作限定。第七界面为任务流转成功后的控制中心页面，可以对应于图6C中的e、图7B中的e所示的界面。第三应用和第二应用可以理解为不同版本的同一应用，例如，手机上的笔记应用，电脑上的笔记应用。
第六操作为返回操作。本申请实施例中的返回操作是指调用back指令的操作。或者也可以理解为退出控制中心页面的操作。第六操作可以为点击操作，也可以为快捷操作，还可以为语音操作，本申请实施例对于第六操作的具体类型不作限定。第八界面为退出控制中心后显示的界面，可以对应于图6C中的f、图7B中的f所示的界面。
这样，第一应用和第二应用适配不同的方式，可以分别通过异源投屏、接续流转至第一从设备。主设备可以根据应用自动调整流转方式，实现智能流转，无需用户分别寻找对应的流转入口减少用户记忆成本，提升用户体验。
可选的，第二界面还包括第一应用的标识，第六界面还包括第二应用的标识；第二操作为拖拽第一应用的标识至第一从设备的设备标识附近的操作；第五操作为拖拽第二应用的标识至第一从设备的设备标识附近的操作。
本申请实施例中，第一应用的标识和第二应用的标识均可以对应于上文中的任务 标识，此处不再赘述。第一应用的标识可以对应于A应用任务标识，第二应用的标识可以对应于B应用任务标识。
第一从设备的设备标识附近可以理解为与第一从设备的设备标识的距离小于第二阈值的情况。
这样，控制中心页面显示对应的应用的标识，简单直观，一目了然。通过拖拽应用的标识至从设备的设备标识附近选取从设备，操作简单，易于理解。
可选的，第一操作和第四操作相同，第一操作为下述操作中的任一个：三指上滑操作、双击操作、三指下滑操作、三击操作。
这样，通过快捷方式进入控制中心页面，操作方便快速，提升用户体验。
可选的，第三操作为在屏幕边缘的左滑操作或右滑操作，或者为针对第三界面显示的第一控件的点击操作；第六操作为在屏幕边缘的左滑操作或右滑操作，或者为针对第七界面显示的第一控件的点击操作。
第一控件可以对应于退出控件。可以理解的是，主设备可以通过侧滑操作退出控制中心页面，也可以通过点击控制中心页面上的退出控件退出控制中心页面。第三操作和第六操作可以相同，也可以不同。
这样，提供多种退出方式，用户可以通过合适的方式退出控制中心页面，提升用户体验。
可选的，主设备为手机、电脑、平板中的任意一种，第一从设备为手机、电脑、平板中的任意一种。
这样，可以适用于多种设备之间的任务流转，覆盖范围广，实用性高，提升用户体验。
可选的，第五界面和第八界面为不同的界面，第五界面包括第二应用的第一页面，第八界面包括第二应用的第二页面，第二应用的第一页面与第二应用的第二页面不同。
可以理解的是，第五界面可以对应于编辑中的页面，或其他修改中的页面。第二页面退出编辑的页面，或退出修改的页面。
这样，主设备在通过接续进行任务流转时，会退出编辑、修改等状态，任务流转前后应用显示的界面的内容不同。
可选的，第二应用为笔记应用；第二应用的第一页面为编辑页面，编辑页面包括第一笔记的内容；第二应用的第二页面为列表页面，列表页面包括第一笔记的标识。
本申请实施例中的任务流转可以适用于笔记应用，笔记应用流转前后应用显示的界面的内容不同。
可选的，第一界面只包括第一应用的页面，第四界面为主设备的桌面。
本申请实施例中的只包括第一应用的页面可以是指全屏显示第一应用的页面，也可以指除了上方的状态栏区域以外的区域显示第一应用的页面。或者只包括第一应用的页面可以理解为，除第一应用的页面不包括其他应用的页面。本申请实施例对此不作具体限定。
可以理解的是，当主设备通过异源投屏方式流转第一应用后，主设备关闭第一应用，不显示第一应用的页面。若主设备在前台仅运行第一应用，通过异源投屏方式流转第一应用后，显示桌面。
可选的，第一界面还包括第四应用的页面，第四应用的页面和第一应用的页面分屏显示；第四界面包括第四应用的页面。
第四应用可以为笔记应用，也可以为其他类型的应用，本申请实施例对此不作限定。第四应用可以与第二应用相同，也可以与第二应用不同。
可以理解的是，若主设备在前台运行第一应用和第四应用，通过异源投屏方式流转第一应用后，显示第四应用的页面。
可选的，第五界面还包括第五应用的页面，第五应用的页面和第二应用的页面分屏显示；第八界面还包括第五应用的页面，第二应用的页面和第五应用的页面分屏显示。
第五应用可以为视频应用，也可以为其他类型的应用，本申请实施例对此不作限定。第五应用可以与第一应用相同，也可以与第一应用不同。
可以理解的是，若主设备在前台运行第二应用和第五应用，通过接续方式流转第二应用后，显示第二应用的页面和第五应用的页面。
可选的，第一界面还包括第一悬浮窗，第一悬浮窗显示有第六应用的页面；第二界面不包括第六应用的标识，第四界面还显示有第二控件；响应于用户对第二控件的操作，在第四界面上显示第一悬浮窗。
通过悬浮窗显示的应用可以对应于上文中的小窗应用。第六应用可以为视频应用，也可以为其他类型的应用，本申请实施例对此不作限定。第二控件可以对应于缩小后的小窗应用，也可以称为悬浮球。第四界面可以对应于图8A或图8B所示的界面。
可以理解的是，小窗应用不进行任务流转。任务流转后，小窗应用缩小至屏幕边缘。通过缩小后的小窗应用可以恢复小窗应用的显示。
可选的，第五界面还包括第二悬浮窗，第二悬浮窗显示有第七应用的页面；第六界面不包括第七应用的标识，第八界面还显示有第三控件；响应于用户对第三控件的操作，在第八界面上显示第二悬浮窗。
通过悬浮窗显示的应用可以对应于上文中的小窗应用。第七应用可以为视频应用，也可以为其他类型的应用，本申请实施例对此不作限定。第三控件可以对应于缩小后的小窗应用，也可以称为悬浮球。第八界面可以对应于图8A或图8B所示的界面。可以理解的是，小窗应用不进行任务流转。任务流转后，小窗应用缩小至屏幕边缘。通过缩小后的小窗应用可以恢复小窗应用的显示。
可选的，主设备为手机、电脑、平板中的任意一种，第一从设备为大屏，第四界面包括第一应用的页面。
当从设备为大屏时，第一应用通过同源投屏的方式进行任务流转。同源投屏中任务流转前后，应用的页面不变，显示的内容相同。从设备显示的页面与主设备显示的页面相同。
可选的，第一界面还包括第四应用的页面，第四应用的页面和第一应用的页面分屏显示时，第四界面不包括第四应用的页面。
分屏显示的场景中，同源投屏中任务流转前后，应用的页面不变，显示的内容相同。从设备显示的页面与主设备显示的页面相同。
可选的，主设备为手机、电脑、平板中的任意一种，第一从设备为大屏，第五界 面包括的第二应用的页面和第八界面包括的第二应用的页面为相同的页面。
当从设备为大屏时，第二应用通过同源投屏的方式进行任务流转。同源投屏中任务流转前后，应用的页面不变，显示的内容相同。从设备显示的页面与主设备显示的页面相同。
可选的，第一应用的页面为播放视频的页面。
可选的，方法还包括：主设备显示第九界面，第九界面包括第八应用的页面；主设备接收到第七操作；响应于第七操作，主设备显示第十界面，第十界面包括第二从设备的设备标识；主设备接收到针对第二从设备的设备标识的第八操作；响应于第八操作，主设备显示第十一界面，第十一界面包括主设备的设备标识和第二从设备的设备标识，其中，主设备的设备标识与第二从设备的设备标识相连。
第九界面为应用的页面，可以对应于上文中图6A中的a、图6C中的a所示的界面，或其他运行有前台应用的页面。第七操作与第一操作类似，具体可以参照上述第一操作的说明，此处不再赘述。第十界面可以对应于未处于协同状态的控制中心页面。第十一界面可以对应于协同中的控制中心页面。第八操作用于选取第二从设备的设备标识，可以为点击操作、拖拽操作，本申请实施例对于第八操作的具体类型不作限定。
本申请实施例中，相连可以为连接，可以为距离较近(紧挨等)，此处不作限定。
这样，控制中心页面还可以实现主设备和从设备之间的协同连接。
可选的，第八操作为拖拽第二从设备的设备标识至主设备的设备标识附近的操作。
这样，主设备的设备标识附近可以理解为与主设备的设备标识的距离小于第三阈值的情况。
这样，通过拖拽从设备的设备标识至主设备的设备标识附近选取与主设备协同的从设备，操作简单，易于理解。
可选的，第十界面还包括第八应用的标识，第十一界面不包括第八应用的标识。
可以理解的是，未处于协同状态的控制中心页面显示有应用的标识，可进行任务流转；协同中的控制中心页面不显示应用的标识，无法进行任务流转。
可选的，第十一界面还包括第一标识，第一标识表示主设备与第二从设备之间的协同类型。
第一标识可以对应于同源投屏、屏幕扩展、屏幕镜像、键鼠共享等。
这样，方便用户确认主设备和从设备的协同类型，提升用户体验。
可选的，第十一界面还包括第二标识，方法还包括：主设备接收针对第二标识的第九操作；响应于第九操作，主设备和第二从设备切换到第二标识对应的协同类型。
第二标识可以对应于为同源投屏、屏幕扩展、屏幕镜像、键鼠共享等协同类型。第九操作可以为点击操作、触摸操作等，本申请实施例对于第九操作不作限定。
这样，用户可以通过第二标识调整主设备和从设备之间的协同类型，切换协同方式，提升用户体验。
可选的，第十一界面还包括第四控件，方法还包括：主设备接收到针对第四控件的第十操作；响应于第十操作，主设备断开与第二从设备的连接；主设备显示第十二界面，第十二界面包括主设备的设备标识和第二从设备的设备标识，主设备的设备标识与第二从设备的设备标识不相连。
第十二界面未断开协同连接后的控制中心页面，可以对应于图11A所示的界面。第四控件可以对应于断开连接控件(按钮)。第十操作可以为点击操作、触摸操作或其他类型的操作，本申请实施例对此不作具体限定。
这样，可以通过第四控件断开主设备与从设备的连接，断开协同，操作简便。
可选的，方法还包括：主设备在第十一界面接收到针对第二从设备的设备标识的第十一操作；响应于第十一操作，主设备断开与第二从设备的连接；主设备显示第十三界面，第十三界面包括主设备的设备标识和第二从设备的设备标识，主设备的设备标识与第二从设备的设备标识不相连。
第十三界面未断开协同连接后的控制中心页面，可以对应于图11B所示的界面。第十一操作可以为拖拽操作或其他类型的操作，本申请实施例对此不作具体限定。
这样，通过拖拽的方式断开主设备与从设备的连接，断开协同，操作简便。
可选的，第十一界面还包括第三从设备的标识，主设备的设备标识与第三从设备的设备标识不相连；方法还包括：主设备在第十一界面接收到针对第三从设备的设备标识的第十二操作；响应于第十二操作，主设备断开与第二从设备的连接，并与第三从设备建立连接；主设备显示第十四界面，第十四界面包括主设备的设备标识、第二从设备的设备标识和第三从设备的标识，主设备的设备标识与第三从设备的设备标识相连，主设备的设备标识与第二从设备的设备标识不相连。
第十二操作用于切换与主设备连接的从设备。第十二操作可以为拖拽第三从设备的设备标识的操作，也可以为其他类型的操作，本申请实施例对此不作限定。第十四界面可以对应于图12所示的界面。
这样，主设备可以切换协同的从设备，提升用户体验。
可选的，协同类型包括以下类型中的任意一种：同源投屏、屏幕扩展、屏幕镜像、键鼠共享。
第二方面，本申请实施例提供一种电子设备，电子设备包括终端设备，终端设备也可以称为终端(terminal)、用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端(mobile terminal，MT)等。终端设备可以是手机(mobile phone)、智能电视、穿戴式设备、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端、无人驾驶(self-driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等等。
该电子设备包括：包括：处理器和存储器；存储器存储计算机执行指令；处理器执行存储器存储的计算机执行指令，使得电子设备执行如第一方面的方法。
第三方面，本申请实施例提供一种计算机可读存储介质，计算机可读存储介质存储有计算机程序。计算机程序被处理器执行时实现如第一方面的方法。
第四方面，本申请实施例提供一种计算机程序产品，计算机程序产品包括计算机程序，当计算机程序被运行时，使得计算机执行如第一方面的方法。
第五方面，本申请实施例提供了一种芯片，芯片包括处理器，处理器用于调用存 储器中的计算机程序，以执行如第一方面所述的方法。
应当理解的是，本申请的第二方面至第五方面与本申请的第一方面的技术方案相对应，各方面及对应的可行实施方式所取得的有益效果相似，不再赘述。
附图说明
图1为本申请实施例提供的一种终端设备的硬件结构示意图；
图2为本申请实施例提供的一种终端设备的软件结构示意图；
图3为本申请实施例提供的一种控制中心页面的界面示意图；
图4A为本申请实施例提供的一种进入控制中心页面的界面示意图；
图4B为本申请实施例提供的一种隐藏控制中心卡片的界面示意图；
图4C为本申请实施例提供的一种控制中心卡片的界面示意图；
图5为本申请实施例提供的另一种进入控制中心页面的界面示意图；
图6A为本申请实施例提供的一种任务流转的界面示意图；
图6B为本申请实施例提供的一种从设备的界面示意图；
图6C为本申请实施例提供的另一种任务流转的界面示意图；
图6D为本申请实施例提供的一种从设备的界面示意图；
图6E为本申请实施例提供的又一种任务流转的界面示意图；
图6F为本申请实施例提供的一种从设备的界面示意图；
图7A为本申请实施例提供的一种分屏显示时任务流转的界面示意图；
图7B为本申请实施例提供的另一种分屏显示时任务流转的界面示意图；
图7C为本申请实施例提供的又一种分屏显示时任务流转的界面示意图；
图7D为本申请实施例提供的一种从设备的界面示意图；
图8A为本申请实施例提供的一种小窗应用时任务流转的界面示意图；
图8B为本申请实施例提供的另一种小窗应用时任务流转的界面示意图；
图8C为本申请实施例提供的又一种小窗应用时任务流转的界面示意图；
图9为本申请实施例提供的一种任务流转失败的界面示意图；
图10为本申请实施例提供的一种设备协同的界面示意图；
图11A为本申请实施例提供的一种设备协同建联的界面示意图；
图11B为本申请实施例提供的一种设备协同断开连接的界面示意图；
图12为本申请实施例提供的一种切换协同的设备的界面示意图；
图13A为本申请实施例提供的一种主设备的界面示意图；
图13B为本申请实施例提供的一种主设备的界面示意图；
图14为本申请实施例提供的一种主设备的界面示意图；
图15为本申请实施例提供的一种多设备任务流转方法的流程示意图；
图16为本申请实施例提供的一种多设备任务流转装置的结构示意图。
具体实施方式
为了便于清楚描述本申请实施例的技术方案，以下，对本申请实施例中所涉及的部分术语和技术进行简单介绍：
1、多屏协同：将电子设备A的用户界面投影到电子设备B的屏幕中进行显示，并且允许用户在电子设备B中对电子设备A的用户界面进行操作，以及通过在电子设备B中执行特定的操作(例如：从电子设备B的用户界面中向电子设备A的用户界面中拖拽文件)，将电子设备B中的文件传输到电子设备A中，实现电子设备A与电子设备B之间的跨设备操作和跨设备文件传输等。其中，电子设备A的用户界面可以显示在电子设备B屏幕中的任意区域，也可以全屏显示。
本申请实施例中的多屏协同包括：同源投屏、屏幕扩展、屏幕镜像、键鼠共享等。同一时刻，任两个设备之间采用一种协同方式。
2、屏幕扩展：将电子设备B的屏幕作为电子设备A的副屏，电子设备A可以将其需要显示的一部分内容转移到副屏上进行显示，电子设备A的屏幕与电子设备B的屏幕可以共同显示内容，扩展了电子设备A的显示能力。
3、屏幕镜像：将电子设备A屏幕中的所有内容完整地在电子设备B的屏幕中进行镜像显示。电子设备B中显示的电子设备A的内容与电子设备A显示的内容相同，且随着电子设备A显示内容的变化而变化。
4、键鼠共享：电子设备A与电子设备B可以共享彼此原有的输入设备，例如：鼠标、键盘等。举例来说，电子设备A的输入设备共享给电子设备B，共享的输入设备既可以在电子设备A中进行输入，也可以在电子设备B中进行输入。另外，在键鼠共享类型中，电子设备A与电子设备B之间还可以进行文件传输。
5、接续：用户在电子设备A上运行应用，电子设备B的界面上可以提示用户在电子设备B上打开在电子设备A上正在运行的应用，从而转移到电子设备B上进行接续操作，或者，用户在电子设备A上运行应用，当用户在电子设备B上打开应用时，电子设备B上的应用进度和电子设备A上的进度相同，也就是说，电子设备B同步了电子设备A运行应用的进度。比如，观看视频、编辑文档，等。例如：电子设备A上正在运行文档应用，文档应用可以是备忘录、word等，用户在电子设备A上正在编辑文档，当电子设备B和电子设备A距离较近时，电子设备B上显示提示信息，用户在电子设备B上点击提示信息，响应于用户的点击操作，电子设备B打开文档应用并展示用户正在编辑的位置，从而转移至电子设备B上继续编辑等。
6、单窗口应用投屏(异源投屏)：电子设备A采用两路编码，其中一路编码将默认界面送显(即在电子设备A显示屏上显示)。另一路编码将虚拟屏幕上渲染的投屏应用界面对应的标准视频流发送至电子设备B。
可以理解的是，以对A应用进行异源投屏为例，用户可以在电子设备B对A应用的窗口进行关闭操作，切换A应用窗口显示的页面等控制，不能对电子设备A中的其他应用进行控制。
7、同源投屏：将电子设备A屏幕中的内容(例如：视频、照片等)投送到电子设备B的屏幕中进行显示。在同源投屏的场景中，电子设备A和电子设备B均显示电子设备A送显的界面。
或者，可以理解为，采取扩展屏幕的方式，将电子设备A上启动的多个应用的界面投屏至电子设备B。在同源投屏方式下，电子设备A采用一路编码向电子设备B发送在虚拟屏幕上渲染的投屏应用界面以及默认界面对应的视频流，以在电子设备B显 示屏上显示默认界面和电子设备A上以自由悬浮窗形式启动的一个或多个投屏应用的界面。其中，默认界面可以理解为电子设备A送显的界面。
一些实施例中，电子设备B可以反向控制电子设备A，示例性的，PC可以反向控制手机。
可以理解的是，同源投屏方式可以保证应用的连续性；而异源投屏方式，在不同屏幕间切换时，需要重新启动应用。
设备协同：主设备和从设备进行协同连接。任务流转：将任务流转至从设备，但不做设备间的协同。
8、其他术语
在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。例如，第一芯片和第二芯片仅仅是为了区分不同的芯片，并不对其先后顺序进行限定。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。
需要说明的是，本申请实施例中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其他实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
本申请实施例中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A，B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b，或c中的至少一项(个)，可以表示：a，b，c，a-b，a--c，b-c，或a-b-c，其中a，b，c可以是单个，也可以是多个。
9、终端设备
本申请实施例的终端设备也可以为任意形式的电子设备，例如，电子设备可以包括具有图像处理功能的手持式设备、车载设备等。例如，一些电子设备为：手机(mobile phone)、平板电脑、掌上电脑、笔记本电脑、移动互联网设备(mobile internet device，MID)、可穿戴设备，虚拟现实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，5G网络中的终端设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端设备等，本申请实施例对此并不限定。
作为示例而非限定，在本申请实施例中，该电子设备还可以是可穿戴设备。可穿 戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
此外，在本申请实施例中，电子设备还可以是物联网(internet of things，IoT)系统中的终端设备，IoT是未来信息技术发展的重要组成部分，其主要技术特点是将物品通过通信技术与网络连接，从而实现人机互连，物物互连的智能化网络。
本申请实施例中的电子设备也可以称为：终端设备、用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端(mobile terminal，MT)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置等。
在本申请实施例中，电子设备或各个网络设备包括硬件层、运行在硬件层之上的操作系统层，以及运行在操作系统层上的应用层。该硬件层包括中央处理器(central processing unit，CPU)、内存管理单元(memory management unit，MMU)和内存(也称为主存)等硬件。该操作系统可以是任意一种或多种通过进程(process)实现业务处理的计算机操作系统，例如，Linux操作系统、Unix操作系统、Android操作系统、iOS操作系统或windows操作系统等。该应用层包含浏览器、通讯录、文字处理软件、即时通信软件等应用。
示例性的，图1示出了终端设备的结构示意图。
终端设备可以包括处理器110，外部存储器接口120，内部存储器121，通用串行总线(universal serial bus，USB)接口130，充电管理模块140，电源管理模块141，电池142，天线1，天线2，移动通信模块150，无线通信模块160，音频模块170，扬声器170A，受话器170B，麦克风170C，耳机接口170D，传感器模块180，按键190，马达191，指示器192，摄像头193，显示屏194，以及用户标识模块(subscriber identification module，SIM)卡接口195等。其中传感器模块180可以包括压力传感器180A，陀螺仪传感器180B，气压传感器180C，磁传感器180D，加速度传感器180E，距离传感器180F，接近光传感器180G，指纹传感器180H，温度传感器180J，触摸传感器180K，环境光传感器180L，骨传导传感器180M等。
可以理解的是，本发明实施例示意的结构并不构成对终端设备的具体限定。在本申请另一些实施例中，终端设备可以包括比图示更多或更少的部件，或者组合某些部件，或者拆分某些部件，或者不同的部件布置。图示的部件可以以硬件，软件或软件和硬件的组合实现。
处理器110可以包括一个或多个处理单元，例如：处理器110可以包括应用处理器(application processor，AP)，调制解调处理器，图形处理器(graphics processing unit，GPU)，图像信号处理器(image signal processor，ISP)，控制器，视频编解码器，数字信号处理器(digital signal processor，DSP)，基带处理器，和/或神经网络处理器 (neural-network processing unit，NPU)等。其中，不同的处理单元可以是独立的器件，也可以集成在一个或多个处理器中。
控制器可以根据指令操作码和时序信号，产生操作控制信号，完成取指令和执行指令的控制。
处理器110中还可以设置存储器，用于存储指令和数据。在一些实施例中，处理器110中的存储器为高速缓冲存储器。该存储器可以保存处理器110刚用过或循环使用的指令或数据。如果处理器110需要再次使用该指令或数据，可从上述存储器中直接调用。避免了重复存取，减少了处理器110的等待时间，因而提高了系统的效率。
在一些实施例中，处理器110可以包括一个或多个接口。接口可以包括集成电路(inter-integrated circuit，I2C)接口，集成电路内置音频(inter-integrated circuit sound，I2S)接口，脉冲编码调制(pulse code modulation，PCM)接口，通用异步收发传输器(universal asynchronous receiver/transmitter，UART)接口，移动产业处理器接口(mobile industry processor interface，MIPI)，通用输入输出(general-purpose input/output，GPIO)接口，用户标识模块(subscriber identity module，SIM)接口，和/或通用串行总线(universal serial bus，USB)接口等。
可以理解的是，本发明实施例示意的各模块间的接口连接关系，只是示意性说明，并不构成对终端设备的结构限定。在本申请另一些实施例中，终端设备也可以采用上述实施例中不同的接口连接方式，或多种接口连接方式的组合。
终端设备通过GPU，显示屏194，以及应用处理器等实现显示功能。GPU为图像处理的微处理器，连接显示屏194和应用处理器。GPU用于执行数学和几何计算，用于图形渲染。处理器110可包括一个或多个GPU，其执行程序指令以生成或改变显示信息。
终端设备可以通过ISP，摄像头193，视频编解码器，GPU，显示屏194以及应用处理器等实现拍摄功能。
外部存储器接口120可以用于连接外部存储卡，例如Micro SD卡，实现扩展终端设备的存储能力。外部存储卡通过外部存储器接口120与处理器110通信，实现数据存储功能。例如将音乐，视频等文件保存在外部存储卡中。
内部存储器121可以用于存储计算机可执行程序代码，可执行程序代码包括指令。内部存储器121可以包括存储程序区和存储数据区。其中，存储程序区可存储操作系统，至少一个功能所需的应用程序(比如声音播放功能，图像播放功能等)等。存储数据区可存储终端设备使用过程中所创建的数据(比如音频数据，电话本等)等。此外，内部存储器121可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件，闪存器件，通用闪存存储器(universal flash storage，UFS)等。处理器110通过运行存储在内部存储器121的指令，和/或存储在设置于处理器中的存储器的指令，执行终端设备的各种功能应用以及数据处理。例如，可以执行本申请实施例的多设备任务流转方法。
可以理解的是，本申请实施例示意的结构并不构成对终端设备的具体限定。在本申请另一些实施例中，终端设备可以包括比图示更多或更少的部件，或者组合某些部件，或者拆分某些部件，或者不同的部件布置。图示的部件可以以硬件，软件或软件 和硬件组合实现。
终端设备的软件系统可以采用分层架构，事件驱动架构，微核架构，微服务架构，或云架构。本申请实施例以分层架构的Android系统为例，示例性说明终端设备的软件结构。
图2是本申请实施例的终端设备的软件结构框图。分层架构将软件分成若干个层，每一层都有清晰的角色和分工。层与层之间通过软件接口通信。在一些实施例中，可以将Android系统分为四层，分别为应用程序层(applications)、应用程序框架层(application framework)、安卓运行时(Android runtime)和系统库、以及内核层(kernel)。
应用层可以包括一系列应用程序包。应用程序层通过调用应用程序框架层所提供的应用程序接口(application programming interface，API)运行应用程序。如图2所示，应用程序包可以包括相机，日历，电话，地图，电话，音乐，设置，邮箱，视频，社交等应用程序。
应用程序框架层为应用程序层的应用程序提供应用编程接口(application programming interface，API)和编程框架。应用程序框架层包括一些预先定义的函数。
如图2所示，应用程序框架层可以包括窗口管理器，内容提供器，资源管理器，视图系统，通知管理器等。
窗口管理器用于管理窗口程序。窗口管理器可以获取显示屏大小，判断是否有状态栏，锁定屏幕，触摸屏幕，拖拽屏幕，截取屏幕等。
内容提供器用来存放和获取数据，并使这些数据可以被应用程序访问。数据可以包括视频，图像，音频，拨打和接听的电话，浏览历史和书签，电话簿等。
视图系统包括可视控件，例如显示文字的控件，显示图片的控件等。视图系统可用于构建应用程序。显示界面可以由一个或多个视图组成的。例如，包括短信通知图标的显示界面，可以包括显示文字的视图以及显示图片的视图。
资源管理器为应用程序提供各种资源，比如本地化字符串，图标，图片，布局文件，视频文件等等。
通知管理器使应用程序可以在状态栏中显示通知信息，可以用于传达告知类型的消息，可以短暂停留后自动消失，无需用户交互。比如通知管理器被用于告知下载完成，消息提醒等。通知管理器还可以是以图表或者滚动条文本形式出现在系统顶部状态栏的通知，例如后台运行的应用程序的通知，还可以是以对话窗口形式出现在屏幕上的通知。例如在状态栏提示文本信息，发出提示音，终端设备振动，指示灯闪烁等。
Android runtime包括核心库和虚拟机。Android runtime负责安卓系统的调度和管理。
核心库包含两部分：一部分是java语言需要调用的功能函数，另一部分是安卓的核心库。
应用程序层和应用程序框架层运行在虚拟机中。虚拟机将应用程序层和应用程序框架层的java文件执行为二进制文件。虚拟机用于执行对象生命周期的管理，堆栈管理，线程管理，安全和异常的管理，以及垃圾回收等功能。
系统库可以包括多个功能模块。例如：表面管理器(surface manager)，媒体库(Media Libraries)，三维图形处理库(例如：OpenGL ES)，2D图形引擎(例如： SGL)等。
表面管理器用于对显示子系统进行管理，并且为多个应用程序提供了2D和3D图层的融合。
媒体库支持多种常用的音频，视频格式回放和录制，以及静态图像文件等。媒体库可以支持多种音视频编码格式，例如:MPEG4，H.264，MP3，AAC，AMR，JPG，PNG等。
三维图形处理库用于实现三维图形绘图，图像渲染，合成，和图层处理等。
2D图形引擎是2D绘图的绘图引擎。
内核层是硬件和软件之间的层。内核层至少包含显示驱动，摄像头驱动，音频驱动，传感器驱动。
应理解，在一些实施例中，可以将实现相同功能的层称为其他名称，或者将能够实现多个层的功能的层作为一层，或者将能够实现多个层的功能的层划分为多层。本申请实施例对此不做限制。
多设备协同是一种应用于多个电子设备的分布式技术。利用多设备协同技术，两个或者多个电子设备之间可以进行跨系统、跨设备的协同，实现资源共享、协同操作。
多设备协同可以应用于同类型或者不同类型的电子设备之间。其中，电子设备的类型包括但不限于手机、平板电脑、笔记本电脑、大屏设备(例如：智能电视、智慧屏)、个人计算机(persona1computer，PC)、手持计算机、上网本、个人数字助理(personal digital assistant，PDA)、可穿戴电子设备、车载设备、虚拟现实设备等设备。本申请实施例中的手机可以为折叠屏手机，也可以为非折叠屏手机，此处不作限定。
多设备协同需要基于设备间的通信连接实现。该通信连接可以是有线通信连接，也可以是无线通信连接。其中，有线通信连接的解决方案例如可以包括USB On-The-Go(OTG)技术；无线通信的解决方案例如可以包括如无线保真(wireless fidelity，Wi-Fi)，Wi-Fi直连(Wi-Fi Direct)，蓝牙(bluetooth，BT)，近距离无线通信技术(near field communication，NFC)，红外技术(infrared，IR)等。
随着终端技术的不断发展，多设备协同已经产生了多种不同的协同类型(也称：协同服务)，例如：屏幕扩展、投屏、屏幕镜像、多屏协同、键鼠共享、超级键鼠等。在上述列举出的多个协同类型中：一些协同类型是主设备(一般是多设备协同的发起方)响应于用户操作，向从设备(一般是多设备协同的参与方)发起的，因此可以被称作手动协同服务或手动协同业务，例如：屏幕扩展、投屏、屏幕镜像、多屏协同、键鼠共享等；另一些协同类型是在用户开启功能的状态下，满足触发规则时自动触发的，因此可以被称作自动协同服务或者自动协同业务，例如：超级接续等。
对于两个电子设备来说，其支持的协同类型一般与设备类型、屏幕尺寸、设备能力等因素有关。因此，两个电子设备可能仅支持一种协同类型，也可能支持多种协同类型。
在传统的方案中，终端设备中进行任务流转的应用为视频类应用，进行流转的应用的类型为单一。此外，在进行任务流转时，针对不同的设备，无法实现智能流转，用户体验不佳。
有鉴于此，本申请实施例提供一种多设备任务流转方法。基于从设备的类型和应用类型，适配不同的流转方式，智能流转，减少用户记忆成本提升用户体验。
为便于本领域技术人员理解本申请实施例的技术方案，本申请实施例对多设备协同的各场景中可能涉及的电子设备进行了分类，各电子设备包括但不限于可以划分为：主设备和从设备。其中：
主设备：包括用户当前手持的设备，用户可以在主设备上执行操作，以向其他设备发起多设备协同，任务流转，因此主设备一般也是发起多设备协同和任务流转的设备。本申请实施例提供的多设备任务流转方法可以在主设备中实现。
从设备：包括位于主设备附近的、与主设备登录相同帐号的设备。主设备与从设备一般是同一厂商生产的电子设备。例如：主设备可以是厂商A生产的手机、从设备可以是厂商A生产的平板电脑，大屏设备等。主设备和从设备登录的账号可以是用户从设备制造商申请的账号。
本申请实施例提供的多设备任务流转方法可以在主设备中实现。例如，主设备可以响应于用户执行的一个或者多个操作，执行多设备任务流转方法的各步骤。
下面通过具体的实施例对本申请实施例的多设备流转方法进行详细说明。下面的实施例可以相互结合或独立实施，对于相同或相似的概念或过程可能在某些实施例中不再赘述。
下面结合图3对本申请实施例提供的控制中心页面进行说明。图3所示的控制中心页面的示例为，在主设备运行A应用的过程中，主设备检测到用户的预设手势，显示如图3所示的控制中心页面，在图3所示的页面中包括A应用的标识。预设手势可以是在屏幕上三指上滑、从屏幕底部上滑等，本申请对此不作限定。或者，在另一种可能的实现方式中，主设备运行A应用的过程中，主设备检测到用户打开通知中心，比如从顶部向下滑动打开通知中心的下拉菜单，下拉菜单中可以包括用户进入控制中心的卡片，在主设备检测到用户点击卡片时，可以显示如图3所示的控制中心页面，或者，也可以显示另一控制中心页面，该另一控制中心页面中不包括A应用的标识。
如图3所示，控制中心页面包括主设备的设备标识301、从设备的设备标识302和任务标识303。设备标识可以为平板电脑的设备标识、大屏设备的设备标识、PC的设备标识、手机的设备标识等。任务标识303表示主设备正在运行的A应用的标识。
其中，主设备的设备标识301和从设备的设备标识302可以是图形化标识，例如图标，或者其他拟物化元素等。
一些实施例中，控制中心页面中，主设备的设备标识301和从设备的设备标识302可以为不同颜色，以便于用户区分。例如：主设备的设备标识301可以为蓝色，从设备的设备标识302可以为白色(或透明色)。另外，在控制中心页面中，主设备的设备标识301和从设备的设备标识302可以为不同尺寸，以便于用户区分。例如：主设备的设备标识301尺寸可以大于从设备的设备标识302尺寸。
对于主设备与从设备未建立多设备协同的场景中，控制中心页面可以包括主设备的设备标识301以及各个从设备的设备标识302。其中，主设备的设备标识301可以位于控制中心页面的中心区域，例如：位于控制中心页面300的正中心、中心偏下区 域、中心偏上区域等，本申请实施对此不做限定。从设备的设备标识302可以分布在主设备的设备标识的外围，一些实施例中，从设备的设备标识302位于主设备的设备标识301的下方。
示例性的，主设备的设备标识301位于控制中心页面的中心偏上区域。各个从设备的设备标识302，例如：平板电脑的设备标识、大屏设备的设备标识、PC的设备标识、手机的设备标识，可以呈半圆形均匀分布在主设备的设备标识301的下方。
对于主设备与从设备建立多设备协同的场景中，可以参照下文协同部分的相关描述，此处不再赘述。
任务标识303可以为一个图形化标识，例如图标，或者其他拟物化元素等。例如：可以将应用的图标作为任务标识303，或者，还可以将应用名称作为任务标识303，本申请实施例对此不做限定。
一些实施例中，控制中心页面还可以包括各个从设备的设备名称304，设备名称304可以与其对应的设备标识302协同显示，例如设备名称可以显示在其对应的设备标识302的上方，下方，或者其他位置。本申请实施例中，设备名称304可以是从设备的产品名称，例如：荣耀TV、荣耀Pad、荣耀Magic Book等，设备名称304还可以是用户自定义的名称，例如：小李的荣耀平板、客厅的荣耀智慧屏等，本申请实施例对此不做限定。
可以理解的是，任务标识303分布在主设备的设备标识301的周围，比如，可以分布在主设备的设备标识301的上方，或者分布在主设备的设备标识301的下方等，本申请实施对此不做限定。
一些实施例中，控制中心页面还包括一个或多个功能按钮，例如，详情按钮305、退出按钮306等。用户可以通过点击详情按钮305了解控制中心页面的使用方式。用户可以通过点击退出按钮306退出控制中心页面。用户还可以通过侧滑操作等快捷操作退出制中心页面。
本申请实施例中，当用户拖动任一从设备的设备标识302至主设备的设备标识301的附近时，主设备与从设备建立连接，进行协同连接等；当用户拖动任务标识303至任一从设备的设备标识302的附近时，主设备基于从设备的类型、从设备安装应用的情况等将任务标识对应的应用流转至相应的从设备。
下面结合图4A至图5对控制中心页面的进入方式进行说明。
本申请实施例中，用户可以通过通知中心页面中的控制中心卡片进入控制中心页面，也可以通过快捷操作进入控制中心页面。快捷操作可以为三指上划，也可以为其他类型的快捷操作，本申请实施例对此不作限定。
示例性的，以主设备为手机为例，如图4A所示，当用户手指在图4A中的a所示的桌面向下滑动时，主设备接收到进入通知中心页面的操作，进入图4A中的b所示的通知中心页面。该通知中心页面包括一个或者多个功能开关按钮，例如：WLAN开关按钮401、蓝牙开关按钮402、手电筒开关按钮403、振动开关按钮404、静音开关按钮405等。当用户点击某个开关按钮时，主设备可以开启或者关闭相应的功能。
通知中心页面还可以包括一个或者多个滑动控件，例如用于调整显示屏亮度的滑动控件406。当用户拖动滑动控件406中的滑块时，主设备可以对显示屏的亮度进行 调节。
通知中心页面还可以包含控制中心卡片407，控制中心卡片407中可以包括卡片名称408以及一个或者多个可点击的元素，例如：控制中心卡片407的隐藏图标409，以及控制中心卡片407的入口按钮410。关于控制中心卡片407的具体内容将在下文做具体展开说明。
其中，上述卡片的名称仅仅是本申请的一个示例，还可以其他名称命名智慧互联这一功能，本申请对此不做限定。例如可以为：“荣耀互联”、“超级终端”等。因此，控制中心卡片407中显示的卡片名称408可以是“荣耀互联”、“超级终端”等。相应地，多设备协同主页面也可以被称作荣耀互联主页面、超级终端主页面。
当用户在通知中心页面点击入口按钮410时，主设备接收到打开控制中心的操作，进入图4A中的c所示的控制中心页面。该控制中心页面包括主设备的设备标识301和从设备的设备标识302。
一些实施例中，通知中心页面还包括编辑按钮411。用户还可以通过编辑按钮411显示或隐藏控制中心卡片407。
示例性的，当用户在图4A中的b所示的页面点击编辑按钮411时，主设备接收到显示编辑菜单的操作，进入图4B中的a所示的页面。该页面中的编辑菜单包括隐藏按钮412。当用户点击隐藏按钮412时，主设备接收到隐藏控制中心卡片的操作，进入图4B中的b所示的页面。该页面中不显示控制中心卡片。
当用户在图4B中的b所示的页面点击编辑按钮411时，主设备接收到显示编辑菜单的操作，进入图4B中的c所示的页面。该页面中的编辑菜单包括显示按钮413。当用户点击显示按钮413时，主设备接收到显示控制中心卡片的操作，进入图4A中的b所示的页面。该页面中显示控制中心卡片。
一些实施例中，当用户在图4A中的b所示的页面点击隐藏图标409时，主设备接收到隐藏控制中心卡片的操作，进入图4B中的b所示的页面。
可能的实现方式中，图4B中的b所示的页面还包括：提示消息414。提示消息414用于提示用户唤出控制中心卡片的操作方式。提示消息414可以为文字消息，例如，可点击“显示智慧互联”恢复卡片。
提示消息414可以以气泡的形式显示，也可以以toast消息的形式显示。本申请实施例对于提示消息414的具体显示形式不做限定。
提示消息414可以在显示一段时间后消失，也可以在接收到任意操作后消失。这样，可以减少提示消息414对通知中心页面中其他按钮的遮挡。本申请实施例对显示提示消息414的消失方式不做限定。
可以理解的是，提示消息414可以仅在用户首次通过隐藏图标隐藏控制中心卡片时显示；提示消息414也可以在前N次通过隐藏图标隐藏控制中心卡片时显示。本申请实施例对于提示消息414的具体显示条件不做限定。
在上述实施例的基础上，控制中心卡片407还显示有协同功能的状态。
如果主设备在显示通知中心页面时，已经搜索到了一个或者多个从设备，那么，主设备在显示通知中心页面时，可以直接将搜索结果显示在控制中心卡片407中。例如：控制中心卡片407中可以显示主设备已经搜索到的从设备的数量(如图4A中的b 所示)，也可以显示已经搜索到的一个或者多个从设备的设备标识，还可以显示已经搜索到的一个或者多个从设备的设备名称。适应性的，用户点击入口按钮410时，主设备显示图4A中的c所示的控制中心界面，控制中心界面包括相应数量的从设备的设备标识。
如果主设备在显示通知中心页面时，未搜索到从设备或者未进行搜索，那么，主设备在显示通知中心页面时，可以在控制中心卡片407中显示用于指示控制中心功能的界面元素。例如：控制中心卡片407中可以显示控制中心的标语，例如，“智慧互联智享生活”(如图4C中的a所示)。
如果主设备在显示通知中心页面时，主设备与从设备正在协同，那么，主设备在显示通知中心页面时，可以在控制中心卡片407中显示用于指示控制中心功能的界面元素。例如：控制中心卡片407中可以显示控制中心的标语，例如，“本机正在协同中”(如图4C中的b所示)。一些实施例中，当主设备正在协同时，控制中心卡片407不包括隐藏图标409。
可以理解的是，上述图4A-图4C所示的实施例中，用户在主设备显示桌面时，通过下滑操作进入通知中心页面。由于进入通知中心页面前主设备未运行有前台应用，通过通知中心页面进入的控制中心页面不包括任务标识303。
用户还可以在主设备显示应用页面时，通过下滑操作进入通知中心页面。相应的，由于进入通知中心页面前主设备运行有前台应用，通过通知中心页面进入的控制中心页面包括任务标识303(例如，如图3所示)。
下面结合图5对控制中心页面的另一种进入方式进行说明。
示例性的，以主设备为手机，且快捷操作为三指上滑为例，如图5所示，主设备正在运行视频应用，播放视频，当用户三个手指在图5中的a所示的页面向上滑动时，若主设备确定上滑操作对应的距离超过第一阈值，主设备接收到进入控制中心页面的操作，主设备进入图5中的b所示的控制中心页面。该控制中心页面包括主设备的设备标识301、从设备的设备标识302和任务标识303。
一些实施例中，若主设备确定上滑操作对应的距离超过第一阈值，主设备接收到进入控制中心页面的操作。若主设备确定上滑操作对应的距离未超过第一阈值，主设备未接收到进入控制中心页面的操作，不进入控制中心页面，返回到运行应用的界面。
本申请实施例中，第一阈值可以为20像素(px)，也可以其他任意数值，此处不作限定。
一些实施例中，主设备可在接收三指上滑操作的过程中，基于三指上滑还显示有动态特效。动态特效可以是缩放动效，例如，将接收到三指上划操作的页面按一定比例进行缩放，直到显示出任务标识303所示的形态，并显示主设备和从设备的设备标识。也可以为其他任意类型的动效本申请实施例对此不作限定。
示例性的，主设备接收到三指上滑操作后，经图5中的c所示的页面，进入图5中的b所示的控制中心页面。
可以理解的是，用户可以在任意界面通过预先设置好的快捷操作进入控制中心页面。上述图5所示的实施例中，由于主设备在进入控制中心页面前，运行有一个前台应用，因此，控制中心页面包括一个应用的标识卡片。若主设备进入控制中心页面前， 运行有多个前台应用，控制中心页面可以包括多个应用的标识卡片。
下面结合图6A-图6F对控制中心的任务流转功能进行说明。
本申请实施例中，若主设备进入控制中心页面前，运行有前台应用，控制中心页面可以包括应用的标识卡片，以实现任务流转。
可以理解的是，由于从设备的类型、任务标识对应的应用等的不同，主设备和从设备实现的任务流转方式不同。任务流转方式包括：单窗口投屏、同源投屏、接续，等。
示例性的，图6A为本申请实施例提供的一种任务流转的界面示意图。以主设备为手机，从设备为电脑，A应用为视频类应用，且从设备未安装有A应用为例。
当主设备在显示A应用对应的应用页面时，接收到用户三指上滑操作，主设备从图6A中的a所示的页面进入图6A中的b所示的控制中心页面。该控制中心页面包括主设备的设备标识301、A应用的标识卡片601和电脑的设备标识602。
用户可以通过拖拽操作将A应用的标识卡片601向电脑的设备标识602方向拖动。当用户拖拽A应用的标识卡片601至电脑的设备标识602的附近时，电脑的设备标识602自动吸附A应用的标识卡片601(如图6A中的c所示)。
当拖拽操作结束时的位置在电脑的设备标识602附近时，主设备向电脑发起任务流转，主设备进入图6A中的d所示的界面。该界面中，电脑的设备标识602中的标识变为连接标识，以形象化地将正在进行任务流转的状态反馈给用户。
示例性的，当用户拖拽A应用的标识卡片601与电脑的设备标识602之间的距离小于第二阈值时，电脑的设备标识602自动吸附A应用的标识卡片601。当拖拽操作结束时的位置与电脑的设备标识602之间的距离小于第二阈值时，主设备向电脑发起任务流转。
本申请实施例中，第二阈值可以为20像素(px)，也可以其他任意数值，此处不作限定。
由于电脑中未安装有A应用，主设备将A应用显示的内容(例如：视频、照片等)投送到电脑的屏幕中显示，以实现单窗口应用投屏，也就是异源投屏。
当主设备与电脑的任务流转完成时，主设备进入图6A中的e所示的界面，该页面中不显示A应用的标识卡片601。适应性的，电脑显示有投屏窗口603，该窗口显示有A应用的内容(如图6B所示)。
当主设备在流转结束后退出控制中心时，不显示A应用的页面。示例性的，主设备在图6A中的e所示的页面接收到用户点击退出按钮306时，主设备从图6A中的e所示的页面进入图6A中的f所示的页面。图6A中的f所示的页面为主设备的桌面。或者，主设备在图6A中的e所示的页面接收到用户侧滑操作时，主设备从图6A中的e所示的页面进入图6A中的f所示的页面。图6A中的f所示的页面为主设备的桌面。侧滑操作可以为左滑操作，也可以为右滑操作，此处不作限定。
示例性的，图6C为本申请实施例提供的一种任务流转的界面示意图。以主设备为手机，从设备为电脑，且从设备安装有B应用为例，举例来说，B应用为笔记应用，主设备和从设备都安装有笔记应用。
当主设备在显示B应用对应的应用页面时，接收到用户三指上滑操作，主设备从 图6C中的a所示的页面进入图6C中的b所示的控制中心页面。该控制中心页面包括主设备的设备标识301、B应用的标识卡片604和电脑的设备标识602。
用户可以通过拖拽操作将B应用的标识卡片604向电脑的设备标识602方向拖动。当用户拖拽B应用的标识卡片604至电脑的设备标识602的附近时，电脑的设备标识602自动吸附B应用的标识卡片604(如图6C中的c所示)。
当拖拽操作结束时的位置在电脑的设备标识602附近时，主设备向电脑发起任务流转，主设备进入图6C中的d所示的界面。该界面中，电脑的设备标识602中的标识变为连接标识，以形象化地将正在进行任务流转的状态反馈给用户。
示例性的，当用户拖拽B应用的标识卡片604与电脑的设备标识602之间的距离小于第一阈值时，电脑的设备标识602自动吸附B应用的标识卡片604。当拖拽操作结束时的位置与电脑的设备标识602之间的距离小于第一阈值时，主设备向电脑发起任务流转。
由于电脑中安装有B应用，电脑中安装的B应用与主设备安装的B应用均支持接续，主设备退出B应用的编辑状态，并控制电脑打开B应用并显示B应用对应的应用页面，电脑显示的B应用对应的应用界面中任务的进度相同，以实现显示内容接续。也就是说，主设备向从设备同步了主设备运行应用B的进度或位置信息，从设备打开应用B时，可以直接显示对应的进度或位置，实现接续。
可以理解的是，若电脑中未安装B应用，或者电脑中安装的B应用不支持接续、或者主设备安装的B应用不支持接续，主设备退出B应用的编辑状态，并将B应用显示的内容(例如：视频、照片等)投送到电脑的屏幕中显示，以实现单窗口应用投屏，也就是异源投屏。
当主设备与电脑的任务流转完成时，主设备进入图6C中的e所示的界面，该页面中不显示B应用的标识卡片604。适应性的，电脑打开B应用，显示有B应用对应的应用页面，(如图6D所示)。
当主设备在流转结束后退出控制中心时，显示B应用的页面。示例性的，当主设备在流转结束后退出控制中心时主设备从图6C中的e所示的页面进入图6C中的f所示的页面。图6C中的f所示的页面为B应用对应的应用页面，比如，B应用的主界面。主设备中的应用B不退出前台，而是根据应用接续的逻辑变化显示的界面。
一些实施例中，若主设备在进行任务流转时，B应用处于编辑状态，主设备退出编辑状态，再进行任务流转。
可以理解的是，主设备可以通过退出按钮306退出控制中心，也可以通过侧滑操作退出控制中心，本申请实施例对于退出控制中心的具体操作不作限定。
示例性的，图6E为本申请实施例提供的一种任务流转的界面示意图。以主设备为手机，从设备为大屏设备，A应用为视频应用为例介绍本申请另一实施例的任务流转方法示例。
当主设备在显示A应用对应的应用页面时，接收到用户三指上滑操作，主设备从图6E中的a所示的页面进入图6E中的b所示的控制中心页面。该控制中心页面包括主设备的设备标识301、A应用的标识卡片601和大屏设备的设备标识605。
用户可以通过拖拽操作将A应用的标识卡片601向大屏设备的设备标识605方向 拖动。当用户拖拽A应用的标识卡片601至大屏设备的设备标识605的附近时，大屏设备的设备标识605自动吸附A应用的标识卡片601(如图6E中的c所示)。
当拖拽操作结束时的位置在大屏设备的设备标识605附近时，主设备向大屏设备发起任务流转，主设备进入图6E中的d所示的界面。该界面中，大屏设备的设备标识605中的标识变为连接标识，以形象化地将正在进行任务流转的状态反馈给用户。
示例性的，当用户拖拽A应用的标识卡片601与大屏设备的设备标识605之间的距离小于第二阈值时，大屏设备的设备标识605自动吸附A应用的标识卡片601。当拖拽操作结束时的位置与大屏设备的设备标识605之间的距离小于第二阈值时，主设备向大屏设备发起任务流转。
由于从设备为大屏设备，主设备将主设备显示的内容(例如：视频、照片等)投送到大屏设备的屏幕中进行显示，以实现同源投屏。
当主设备与电脑的任务流转完成时，主设备进入图6E中的e所示的界面，该页面中不显示A应用的标识卡片601。适应性的，大屏设备显示的内容与主设备的显示内容相同(如图6F中的a所示)。
当主设备在流转结束后退出控制中心时，主设备从图6E中的e所示的页面进入图6E中的f所示的A应用的应用页面。适应性的，大屏设备显示的内容与主设备的显示内容相同(如图6F中的b所示)。
可以理解的是，主设备可以通过退出按钮306退出控制中心，也可以通过侧滑操作退出控制中心，本申请实施例对于退出控制中心的具体操作不作限定。
可以理解的是，主设备与大屏设备进行任务流转时，进行任务流转的应用的状态不变。示例性的，以笔记应用为例，若笔记应用处于编辑态，则主设备在退出控制中心页面后，仍处于编辑态。
可以理解的是，上述图6A-图6F均是以任务流转时前台运行有一个应用为例进行说明的。下面结合图7A-图7D对分屏时进行任务流转的场景进行说明。
示例性的，图7A为本申请实施例提供的一种任务流转的界面示意图。以主设备为手机，从设备为电脑，A应用为视频应用，B应用为笔记应用，且从设备未安装有A应用，安装有B应用为例，来说明本申请实施例的任务流转方法。举例来说，主设备安装有视频应用和笔记应用，从设备安装有笔记应用。
当主设备在分屏显示A应用对应的应用页面和B应用对应的应用页面时，接收到用户三指上滑操作，主设备从图7A中的a所示的页面进入图7A中的b所示的控制中心页面。该控制中心页面包括主设备的设备标识301、A应用的标识卡片601、B应用的标识卡片604和电脑的设备标识602。
用户可以通过拖拽操作将A应用的标识卡片601向电脑的设备标识602方向拖动。当用户拖拽A应用的标识卡片601至电脑的设备标识602的附近时，电脑的设备标识602自动吸附A应用的标识卡片601(如图7A中的c所示)。
当拖拽操作结束时的位置在电脑的设备标识602附近时，主设备向电脑发起任务流转，主设备进入图7A中的d所示的界面。该界面中，电脑的设备标识602中的标识变为连接标识，以形象化地将正在进行任务流转的状态反馈给用户。
示例性的，当用户拖拽A应用的标识卡片601与电脑的设备标识602之间的距离 小于第二阈值时，电脑的设备标识602自动吸附A应用的标识卡片601。当拖拽操作结束时的位置与电脑的设备标识602之间的距离小于第二阈值时，主设备向电脑发起任务流转。
由于电脑中未安装有A应用，主设备将A应用显示的内容(例如：视频、照片等)投送到电脑的屏幕中进行显示，以实现单窗口应用投屏。
当主设备与电脑的任务流转完成时，主设备进入图7A中的e所示的界面，该页面中不显示A应用的标识卡片601。适应性的，电脑显示有投屏窗口703，该窗口显示有A应用的内容(如图6B所示)。
当主设备在流转结束后退出控制中心时，主设备从图7A中的e所示的页面进入图7A中的f所示的页面。图7A中的f所示的页面中，B应用对应的应用页面全屏显示。
可以理解的是，主设备可以通过退出按钮306退出控制中心，也可以通过侧滑操作退出控制中心，本申请实施例对于退出控制中心的具体操作不作限定。
示例性的，图7B为本申请实施例提供的一种任务流转的界面示意图。以主设备为手机，从设备为电脑，A应用为视频应用，B应用为笔记应用，且从设备安装有B应用为例，来说明本申请实施例的任务流转方法。举例来说，主设备安装有视频应用和笔记应用，从设备安装有笔记应用。
当主设备在分屏显示A应用对应的应用页面和B应用对应的应用页面时，接收到用户三指上滑操作，主设备从图7B中的a所示的页面进入图7B中的b所示的控制中心页面。该控制中心页面包括主设备的设备标识301、A应用的标识卡片601、B应用的标识卡片604和电脑的设备标识602。
用户可以通过拖拽操作将B应用的标识卡片604向电脑的设备标识602方向拖动。当用户拖拽B应用的标识卡片604至电脑的设备标识602的附近时，电脑的设备标识602自动吸附B应用的标识卡片604(如图7B中的c所示)。
当拖拽操作结束时的位置在电脑的设备标识602附近时，主设备向电脑发起任务流转，主设备进入图7B中的d所示的界面。该界面中，电脑的设备标识602中的标识变为连接标识，以形象化地将正在进行任务流转的状态反馈给用户。
示例性的，当用户拖拽B应用的标识卡片604与电脑的设备标识602之间的距离小于第一阈值时，电脑的设备标识602自动吸附B应用的标识卡片604。当拖拽操作结束时的位置与电脑的设备标识602之间的距离小于第一阈值时，主设备向电脑发起任务流转。
由于电脑中安装有B应用，电脑中安装的B应用与主设备安装的B应用均支持接续，主设备退出B应用的编辑状态，并控制电脑打开B应用并显示B应用对应的应用页面，以实现显示内容接续。
当主设备与电脑的任务流转完成时，主设备进入图7B中的e所示的界面，该页面中不显示B应用的标识卡片604。适应性的，电脑打开B应用，显示有B应用对应的应用页面，(如图6D所示)。
当主设备在流转结束后退出控制中心时，主设备从图7B中的e所示的页面进入图7B中的f所示的页面。该页面显示分屏显示A应用对应的应用页面和B应用对应的应 用页面。相比较于图7B中的a所示的页面，图7B中的f所示的页面中，B应用退出编辑状态。
一些实施例中，若主设备在进行任务流转时，B应用处于编辑状态，主设备退出编辑状态。
示例性的，图7C为本申请实施例提供的一种任务流转的界面示意图。以主设备为手机，从设备为大屏设备，A应用为视频应用，B应用为笔记应用为例介绍本申请另一实施例的任务流转的方法。举例来说，主设备安装有视频应用和笔记应用。
当主设备在分屏显示A应用对应的应用页面和B应用对应的应用页面时，接收到用户三指上滑操作，主设备从图7C中的a所示的页面进入图7C中的b所示的控制中心页面。该控制中心页面包括主设备的设备标识301、A应用的标识卡片601和大屏设备的设备标识605。
用户可以通过拖拽操作将A应用的标识卡片601向大屏设备的设备标识605方向拖动。当用户拖拽A应用的标识卡片601至大屏设备的设备标识605的附近时，大屏设备的设备标识605自动吸附A应用的标识卡片601(如图7C中的c所示)。
当拖拽操作结束时的位置在大屏设备的设备标识605附近时，主设备向大屏设备发起任务流转，主设备进入图7C中的d所示的界面。该界面中，大屏设备的设备标识605中的标识变为连接标识，以形象化地将正在进行任务流转的状态反馈给用户。
示例性的，当用户拖拽A应用的标识卡片601与大屏设备的设备标识605之间的距离小于第二阈值时，大屏设备的设备标识605自动吸附A应用的标识卡片601。当拖拽操作结束时的位置与大屏设备的设备标识605之间的距离小于第二阈值时，手机向大屏设备发起任务流转。
由于从设备为大屏设备，主设备将A应用显示的内容(例如：视频、照片等)投送到大屏设备的屏幕中进行显示，以实现同源投屏。
当主设备与电脑的任务流转完成时，主设备进入图7C中的e所示的界面，该页面中不显示A应用的标识卡片601。适应性的，大屏设备显示的内容与主设备的显示内容相同(如图7D中的a所示)。
当主设备在流转结束后退出控制中心时，主设备从图7C中的e所示的页面进入图7C中的f所示的A应用的应用页面。适应性的，大屏设备显示的内容与主设备的显示内容相同(如图7D中的b所示)。
可以理解的是，主设备可以通过退出按钮306退出控制中心，也可以通过侧滑操作退出控制中心，本申请实施例对于退出控制中心的具体操作不作限定。
可以理解的是，上述图7A-图7D所示的实施例中主设备采用上下分屏的方式进行分屏。主设备还可以左右分屏的方式进行分屏，本申请实施例对于分屏的方式不作限定。
一些实施例中，当主设备采用上下分屏时，控制中心页面从左至右显示的应用的标识卡片分别与分屏界面中从上至下显示的应用相对应。当主设备采用左右分屏时，控制中心页面从左至右显示的应用的标识卡片分别与分屏界面中从上至下显示的应用相对应。
下面结合图8A-图8C对运行有小窗应用时进行任务流转的场景进行说明。
示例性的，图8A为本申请实施例提供的一种任务流转的界面示意图。以主设备为手机，A应用为视频应用，小窗应用为笔记应用，为例。
图8A所示的页面包括：A应用对应的应用页面，以及小窗应用对应的页面801。当主设备接收到用户三指上滑操作，进入图8A中的b所示的控制中心页面。该控制中心页面包括主设备的设备标识301、A应用的标识卡片601、电脑的设备标识602和大屏设备的设备标识605，不包括小窗应用对应的标识卡片。
本申请实施例中，小窗应用可以为笔记、即时通信等任意应用，本申请实施例对此不做限定。
用户可以通过拖拽操作将A应用的标识卡片601向从设备的设备标识302(例如，电脑的设备标识602、大屏设备的设备标识605等)方向拖动，以进行任务流转。任务流转的具体过程与上述图6A-图7D的流程类似，此处不再赘述。
本申请实施例中，当主设备在任务流转结束后退出控制中心时，小窗应用对应的页面缩小，并位于至主设备的侧边位置。
示例性的，以将A应用对应的页面拖拽至电脑的设备标识602附近为例，若电脑未安装有A应用，则任务流转方式为单窗口投屏；主设备在任务流转结束后退出控制中心时，主设备显示主页面和缩小后的小窗应用802(如图8A中的c所示)。缩小后的小窗应用802位于主设备的侧边位置。
以将A应用对应的页面拖拽至电脑的设备标识602附近为例，若电脑安装A应用，则任务流转方式为接续；主设备在任务流转结束后退出控制中心时，主设备显示A应用的应用页面和缩小后的小窗应用802(如图8A中的d所示)。
一些实施例中，主设备在进行任务流转时，A应用处于播放状态；主设备退出控制中心页面后，A应用停止播放视频，或者退出该视频播放页面，返回播放列表界面。
可以理解的是，主设备可以通过退出按钮306退出控制中心，也可以通过侧滑操作退出控制中心，本申请实施例对于退出控制中心的具体操作不作限定。
以将A应用对应的页面拖拽至大屏设备的设备标识605附近为例，则任务流转方式为同源投屏；主设备在任务流转结束后退出控制中心时，主设备显示主页面和缩小后的小窗应用802(如图8A中的d所示)。缩小后的小窗应用802位于主设备的侧边位置。
示例性的，图8B为本申请实施例提供的一种任务流转的界面示意图。图8B所示的页面包括：分屏显示的A应用对应的应用页面、分屏显示的C应用对应的应用页面，以及小窗应用对应的页面801。以主设备为手机，A应用为视频应用，C应用为新闻应用，小窗应用为笔记应用，为例来说明本申请实施例的任务流转方法。
当主设备接收到用户三指上滑操作，进入图8B中的b所示的控制中心页面。该控制中心页面包括主设备的设备标识301、A应用的标识卡片601、C应用的标识卡片803、电脑的设备标识602和大屏设备的设备标识605，不包括小窗应用对应的标识卡片。
用户可以通过拖拽操作将任务标识303(例如，A应用的标识卡片601、B应用的标识卡片803)向从设备的设备标识302(例如，电脑的设备标识602、大屏设备的设备标识605等)方向拖动，以进行任务流转。任务流转的具体过程与上述图6A-图7D 的流程类似，此处不再赘述。
本申请实施例中，当主设备在任务流转结束后退出控制中心时，小窗应用对应的页面缩小，并位于至主设备的侧边位置。
以将A应用对应的页面拖拽至电脑的设备标识602附近为例，若电脑安装A应用，则任务流转方式为接续；主设备在任务流转结束后退出控制中心时，主设备显示A应用对应的页面、B应用对应的页面和缩小后的小窗应用802(如图8B中的c所示)。缩小后的小窗应用802位于主设备的侧边位置。
示例性的，以将A应用对应的页面拖拽至电脑的设备标识602附近为例，若电脑未安装有A应用，则任务流转方式为单窗口投屏；主设备在任务流转结束后退出控制中心时，主设备显示C应用的应用页面和缩小后的小窗应用802(如图8B中的d所示)。缩小后的小窗应用802位于主设备的侧边位置。
以将A应用对应的页面拖拽至大屏设备的设备标识605附近为例，则任务流转方式为同源投屏；主设备在任务流转结束后退出控制中心时，主设备显示A应用对应的页面和缩小后的小窗应用802(如图8B中的e所示)。缩小后的小窗应用802位于主设备的侧边位置。
可以理解的是，主设备可以通过退出按钮306退出控制中心，也可以通过侧滑操作退出控制中心，本申请实施例对于退出控制中心的具体操作不作限定。
示例性的，图8C为本申请实施例提供的一种任务流转的界面示意图。以主设备为手机，小窗应用为笔记应用，为例。图8C所示的页面包括：主页面，以及小窗应用对应的页面801。当主设备接收到用户三指上滑操作，进入图8C中的b所示的控制中心页面。该控制中心页面包括主设备的设备标识301和从设备的设备标识302，不包括任务标识303。
可以理解的是，在上述图6A-图8C所示的实施例的基础上，当主设备接收到快捷操作时，主设备还显示有动态特效。动态特效可以参照上述相关说明，此处不再赘述。
可以理解的是，当从设备为大屏设备时，主设备与从设备之间的任务流转方式为同源投屏。当从设备为手机、PC、平板中的任一个、从设备安装有相应应用，且主设备和从设备安装的应用均支持接续时，主设备与从设备之间的任务流转方式为接续；当从设备为手机、PC、平板中的任一个、且从设备未安装有相应应用，主设备与从设备之间的任务流转方式为异源投屏；当从设备为手机、PC、平板中的任一个、从设备安装有相应应用，且主设备和从设备中的任一设备安装的应用不支持接续，主设备与从设备之间的任务流转方式为异源投屏。
示例性的，主设备和从设备之间的任务流转方式可以参照下述表1，此处不再赘述。
表1任务流转方式

可以理解的是，任务流转可能由于多种原因失败。原因包括但不限于：从设备锁屏、从设备休眠、从设备不支持流转、应用不支持流转、网络异常等。
示例性的，图9为本申请实施例提供的一种控制中心的页面示意图。如图9所示，在图9中的a所示的页面包括：主设备的设备标识301、A应用的标识卡片601和电脑的设备标识602。
用户可以通过拖拽操作将A应用的标识卡片601向电脑的设备标识602方向拖动。当用户拖拽A应用的标识卡片601至电脑的设备标识602的附近时，电脑的设备标识602自动吸附A应用的标识卡片601(如图9中的b所示)。
当拖拽操作结束时的位置在电脑的设备标识602附近时，主设备向电脑发起任务流转，主设备进入图9中的c所示的界面。该界面中，电脑的设备标识602中的标识变为连接标识，以形象化地将正在进行任务流转的状态反馈给用户。
示例性的，当用户拖拽A应用的标识卡片601与电脑的设备标识602之间的距离小于第二阈值时，电脑的设备标识602自动吸附A应用的标识卡片601。当拖拽操作结束时的位置与电脑的设备标识602之间的距离小于第二阈值时，主设备向电脑发起任务流转。
若任务流转失败，主设备从进入图9中的c所示的界面进入图9中的d所示的界面。该界面中包括：主设备的设备标识301、A应用的标识卡片601和电脑的设备标识602。
在上述实施例的基础上，若任务流转失败，主设备的控制中心页面可以会显示有提示消息，以提示用户流转失败。
示例性的，图9中的d所示的控制中心页面还包括：提示消息901。提示消息901用于提示用户任务流转失败。
提示消息901可以为文字消息，例如，“连接失败”。
提示消息901可以以气泡的形式显示，也可以以toast消息的形式显示。本申请实施例对于提示消息901的具体显示形式不做限定。
提示消息901可以在显示一段时间后消失，也可以在接收到任意操作后消失。这样，可以减少提示消息901对控制中心页面的遮挡。本申请实施例对显示提示消息901的消失方式不做限定。
一些实施例中，提示消息901还用于提示用户流转失败的原因。这样，用户可以基于失败原因调整从设备，方便再次进行任务流转。提升用户体验。
示例性的，提示消息901对应的文字可以为：“连接失败，请解锁对端后重试”、 “暂不支持任务流转至从设备”、“应用暂不支持流转至从设备”、“网络连接不稳定，请稍后重试”等。本申请实施例对于提示消息901的具体内容不做限定。
下面结合图10-图14对控制中心的设备协同功能进行说明。
可以理解的是，主设备通过上述两种方式进入控制中心页面，控制中心可能会有以下三种情况：第一种情况，主设备已经搜索到一个或者多个从设备；第二种情况，主设备未搜索到从设备；第三种情况，主设备正在协同中。
下面结合图10对三种情况对应的控制中心页面进行说明。
第一种情况：若主设备已经搜索到一个或者多个从设备，控制中心页面如图10中的a所示。控制中心页面包括主设备的设备标识301和从设备的设备标识302。主设备的设备标识301和从设备的设备标识302的位置、形状等可以参照上述图3中相应说明，此处不再赘述。
示例性的，当用户在图4A中的b所示的通知中心页面点击入口按钮410时，主设备接收到打开控制中心的操作，进入图10中的a所示的控制中心页面。
在上述实施例的基础上，控制中心页面还显示有提示消息1001。提示消息1001用于提示用户了解协同功能的方式。一些实施例中，提示消息1001可以在接收到用户操作后消失，也可以在一段时间(例如，15S)后消失。
主设备可以在前N次进入控制中心页面时，显示提示消息1001，也可以仅在首次进入控制中心页面时，显示提示消息1001。本申请实施例对于提示消息1001的显示条件和消失条件等均不做具体限定。
第二种情况：若主设备未搜索到从设备，控制中心页面如图10中的b所示。控制中心页面包括主设备的设备标识301，不包括从设备的设备标识302。
示例性的，当用户在图4C中的a所示的通知中心页面点击入口按钮410时，主设备接收到打开控制中心的操作，进入图10中的b所示的控制中心页面。
一些实施例中，控制中心页面还显示有提示消息1002。提示消息1002用于提示用户未发现从设备的原因。原因包括但不限于：附近设备未登录同一账号且开启智慧互联服务、附近设备未打开蓝牙和WLAN、附近设备不支持与本机协同，等。
可能的实现方式中，主设备在显示控制中心页面的预设时长内未搜索到从设备，显示提示消息1002；在搜索到从设备，显示从设备的设备标识302时，提示消息1002消失。
可以理解的是，当主设备搜索到从设备时，主设备可以从图10中的b所示的页面进入到从图10中的a所示的页面。
第三种情况：若主设备正在协同中，控制中心页面如图10中的c所示。控制中心页面包括协同标识1003。
协同标识1003可以是一个图形化标识，例如图标，或者其他拟物化元素等。例如：可以将主设备的设备标识与协同设备的设备标识融合形成协同标识1003，本申请实施例对于协同标识的具体形状等不做限定。
一些实施例中，若主设备正在协同中，控制中心页面还包括协同类型卡片1004，协同类型卡片1004包括多个按钮，例如：多屏协同按钮1005、断开连接按钮1006。
需要说明的是，协同类型卡片显示的按钮与主设备和从设备之间支持的协同类型 相关。示例性的，主设备为手机，从设备为PC、PAD、大屏设备中的任一设备时，主设备与从设备之间的协同均为同源投屏。控制中心页面显示的协同类型卡片1004可以包括多屏协同按钮1005、断开连接按钮1006(如图10中的c所示)。
主设备为PC，从设备为平板时，主设备与从设备之间的协同可以为屏幕扩展、屏幕镜像、键鼠共享中的任一种。控制中心页面显示的协同类型卡片1004可以包括屏幕扩展按钮1007、屏幕镜像按钮1008、键鼠共享按钮1009和断开连接按钮1006(如图10中的d所示)。
当用户点击屏幕扩展按钮1007时，主设备与从设备之间的协同类型切换为屏幕扩展；当用户点击屏幕镜像按钮1008时，主设备与从设备之间的协同类型切换为屏幕镜像；当用户点击键鼠共享按钮1009时，主设备与从设备之间的协同类型切换为键鼠共享。
示例性的，主设备与从设备之间支持的协同类型可以如表2所示。
表2主设备与从设备之间的协同
下面结合图11A和图11B对主设备与从设备之间的连接过程和断开过程进行说明。
示例性的，当用户将图11A中的a所示的页面中电脑的设备标识602拖拽至主设备的设备标识301的附近时，主设备的设备标识301自动吸附电脑的设备标识602(如图11A中的b所示)。当拖拽操作结束时的位置在主设备的设备标识301附近时，主设备与电脑开始建立协同连接，主设备进入图11A中的c所示的界面。该界面中，电脑的设备标识602中的标识变为连接标识，以形象化地将正在进行协同连接的状态反馈给用户。
示例性的，当用户拖拽电脑的设备标识602与主设备的设备标识301之间的距离小于第三阈值时，主设备的设备标识301自动吸附电脑的设备标识602。当拖拽操作结束时的位置与主设备的设备标识301之间的距离小于第三阈值时，主设备与电脑开始建立协同连接。
本申请实施例中，第三阈值可以为20像素(px)，也可以其他任意数值，此处不作限定。
当主设备与电脑的协同连接建立完成时，主设备进入图11A中的d所示的页面，该页面包括协同标识1003和协同类型卡片1004。
若主设备与电脑协同时，电脑显示有协同窗口1101，该窗口显示的内容与主设备显示的内容相同。
若主设备与电脑的协同连接建立失败，主设备进入图11A中的e所示的页面，该页面包括主设备的设备标识301和电脑的设备标识602。
一些实施例中，若协同连接建立失败，主设备的控制中心页面可以会显示有提示消息，以提示用户协同连接建立失败。
示例性的，11A中的e所示的页面还包括：提示消息1101。提示消息1101用于提示用户协同连接建立失败。提示消息1101可以为文字消息，例如，“连接失败”。提示消息1101可以以气泡的形式显示，也可以以toast消息的形式显示。本申请实施例对于提示消息1101的具体显示形式不做限定。
提示消息1101可以在显示一段时间后消失，也可以在接收到任意操作后消失。这样，可以减少提示消息1101对控制中心页面的遮挡。本申请实施例对显示提示消息1101的消失方式不做限定。
一些实施例中，提示消息1101还用于提示用户流转失败的原因。这样，用户可以基于失败原因调整从设备，方便再次进行任务流转。提升用户体验。
示例性的，提示消息1101对应的文字可以为：“连接失败，请解锁对端后重试”、“暂不支持任务流转至从设备”、“应用暂不支持流转至从设备”、“网络连接不稳定，请稍后重试”等。本申请实施例对于提示消息1101的具体内容不做限定。
下面结合图11B对主设备与从设备之间的断开过程进行说明。
一些实施例中，当用户拖动图11B中的a所示的界面中协同标识1003中的电脑的设备标识远离主设备的设备标识301的附近区域时，主设备的设备标识301取消吸附电脑的设备标识602，并且电脑的设备标识602的位置与拖拽操作的位置相关(如图11B中的b所示)。当拖拽操作结束时的位置不在主设备的设备标识301附近时，主设备与电脑断开协同连接，主设备进入图11B中的c所示的界面，电脑的设备标识602位于从设备序列的最后一个。
示例性的，当用户拖拽电脑的设备标识602与主设备的设备标识301之间的距离大于或等于第三阈值时，主设备的设备标识301取消吸附电脑的设备标识602。当拖拽操作结束时的位置与主设备的设备标识301之间的距离大于或等于第三阈值时，主设备与电脑断开协同连接。
可能的实现方式中，主设备协同时，控制中心页面持续显示协同类型卡片1004，直至协同断开。若用户点击图11A中的d所示的断开连接按钮1006时，主设备断开与电脑的连接，主设备进入图11B中的c所示的页面。该页面包括主设备的设备标识301和电脑的设备标识602。电脑的设备标识602位于从设备序列的最后一个。
在上述实施例的基础上，用户可以拖拽底部的从设备的设备标识至协同标识1003的附近时，主设备断开协同，与拖拽的从设备的设备标识对应的从设备建立协同连接。
示例性的，如图12所示，以主设备与从设备2建立协同为例，当用户拖拽从设备1的设备标识1201至协同标识303的附近时，主设备断开从设备2的协同，与从设备1建立协同，主设备从图12中的a所示的页面进入图12中的b所示的页面。
下面结合图13A和图13B对任务流转和协同场景冲突的场景进行说明。
本申请实施例中，当主设备在协同时，接收到用户进入控制中心页面的操作，控制中心页面显示协同类型卡片1004，不显示任务标识303(如图13A中的b所示)。当主设备与从设备的协同连接断开时，控制中心页面显示任务标识303，如图13A中的c所示。当主设备在协同时，接收到用户进入控制中心页面的操作，控制中心页面显示任务标识303，如图13A中的c所示。
示例性的，如图13A所示，主设备在协同时，当主设备在图13A中的a所示的界面接收到三指上滑操作时，主设备进入16A中的b所示的页面。该页面包括协同类型卡片1004，不包括任务标识303。当用户点击断开连接按钮1006时，主设备显示图13A中的c所示的页面。该页面包括任务标识303。
本申请实施例中，当主设备未在协同且运行有前台应用时，接收到用户进入控制中心页面的操作，控制中心页面显示任务标识303。用户可以拖拽操作拖拽从设备的设备标识至主设备的设备标识附近，以实现主设备与从设备的协同连接。
示例性的，如图13B所示，当主设备在图13A中的a所示的界面接收到三指上滑操作时，主设备进入图13B中的a所示的页面，该页面包括主设备的设备标识301、任务标识303和电脑的设备标识602，不包括协同类型卡片1004。当用户拖拽电脑的设备标识602至主设备的设备标识301附近时，主设备的设备标识301自动吸附电脑的设备标识602。
当拖拽操作结束时的位置在主设备的设备标识301附近时，主设备与电脑建立协同连接，主设备进入图13B中的c所示的页面。
一些实施例中，在用户拖拽的过程中，主设备不显示任务标识303(如图13B中的b所示)，并且，在主设备确定和从设备的协同方式时，不考虑当前正在运行的业务，而是参照上文所示的表2确定协同方式。
在上述实施例的基础上，主设备在进入控制中心页面之前，主设备还显示有引导页面，以提示用户进行同意隐私协议、开启蓝牙和WLAN、登录账号等。
示例性的，图14为本申请实施例提供的一种主设备的页面示意图。以主设备首次进入控制中心为例。
如图14所示，若主设备接收到用户三指上滑操作，主设备进入图14中的a所示的页面。该页面包括：引导弹窗1701。当用户点击同意按钮1702时，主设备进入图14中的b所示的页面，该页面显示有隐私协议和同意控件1703。当用户点击同意控件1703时，主设备进入图14中的c所示的页面，该页面包括：登录控件。
当用户点击登录控件1704时，主设备进入图14中的d所示的页面。该页面包括开启控件1705。当用户点击开启控件1705，主设备进入控制中心页面。
若当用户点击登录控件1704时，主设备已开启蓝牙和WLAN，主设备进入控制中心页面，不显示图14中的d所示的页面。
上述实施例是以主设备为手机为例进行说明的。主设备还可以为电脑、pad等。主设备为电脑、pad等其他设备的任务流转方式、界面显示、协同等可以参照上述为手机为例的相关说明，此处不再赘述。
示例性的，图15为本申请实施例提供的一种多设备任务流转方法的流程示意图， 该方法包括：
S1501、主设备显示第一界面，第一界面包括第一应用的页面。
本申请实施例中，第一界面为应用的页面，第一界面可以对应于图6A中的a、图7A中的a所示的界面。第一应用的页面可以对应于图6A所示的A应用页面。第一应用可以为视频类应用，也可以为其他类型的应用，本申请实施例对此不作限定。
S1502、主设备接收到第一操作。
第一操作用于进入控制中心页面。第一操作可以为快捷手势操作，也可以为语音操作，或其他类型的操作，本申请实施例对此不作限定。快捷手势操作可以为三指上滑等手势操作。
S1503、响应于第一操作，主设备显示第二界面，第二界面包括第一从设备的设备标识。
第二界面为控制中心页面，可以对应于图6A中的b所示的界面、图7A中的b所示的界面。第一从设备的设备标识的形式可以参照上述从设备的设备标识的说明，此处不再赘述。
S1504、主设备接收到针对第一从设备的设备标识的第二操作。
本申请实施例中，第二操作用于选取第一从设备。基于不同的页面，选取方式可以不同，可以为拖拽选取，也可以为点击第一从设备的设备标识选取等，本申请实施例对于第二操作的类型不作限定。
S1505、响应于第二操作，主设备显示第三界面，并向第一从设备发送第一应用的页面，以使第一从设备显示第一应用的页面。
第三界面为任务流转成功后的控制中心页面，可以对应于图6A中的e、图7A中的e所示的界面。
S1506、主设备接收到第三操作。
第三操作为返回操作。本申请实施例中的返回操作是指调用back指令的操作。或者也可以理解为退出控制中心页面的操作。第三操作可以为点击操作，也可以为快捷操作，还可以为语音操作，本申请实施例对于第三操作的具体类型不作限定。
S1507、响应于第三操作，主设备显示第四界面，第四界面不包括第一应用的页面。
第四界面为退出控制中心后显示的界面，可以对应于图6A中的f、图7A中的f所示的界面。可以理解的是，当主设备通过异源投屏方式流转第一应用后，主设备关闭第一应用，不显示第一应用的页面。
S1508、主设备显示第五界面，第五界面包括第二应用的页面。
本申请实施例中，第五界面为应用的页面，第五界面可以对应于图6C中的a、图7B中的a所示的界面。第二应用的页面可以对应于图6C所示的B应用页面。第二应用可以为笔记应用，也可以为其他类型的应用，本申请实施例对此不作限定。
S1509、主设备接收到第四操作。
第四操作用于进入控制中心页面。第四操作可以为快捷手势操作，也可以为语音操作，或其他类型的操作，本申请实施例对此不作限定。快捷手势操作可以为三指上滑等手势操作。
S1510、响应于第四操作，主设备显示第六界面，第六界面包括第一从设备的设备 标识。
第六界面为控制中心页面，可以对应于图6C中的b所示的界面、图7B中的b所示的界面。
S1511、主设备接收到针对第一从设备的设备标识的第五操作。
本申请实施例中，第五操作用于选取第一从设备。基于不同的页面，选取方式可以不同，可以为拖拽选取，也可以为点击第一从设备的设备标识选取等，本申请实施例对于第五操作的类型不作限定。
S1512、响应于第五操作，主设备显示第七界面，并向第一从设备发送第二应用的页面上显示的内容，以使得第一从设备启动第三应用，第三应用与第二应用相对应，第三应用的页面显示的内容与第二应用的页面上显示的内容相同。
第七界面为任务流转成功后的控制中心页面，可以对应于图6C中的e、图7B中的e所示的界面。第三应用和第二应用可以理解为不同版本的同一应用，例如，手机上的笔记应用，电脑上的笔记应用。
S1513、主设备接收到第六操作。
第六操作为返回操作。本申请实施例中的返回操作是指调用back指令的操作。或者也可以理解为退出控制中心页面的操作。第六操作可以为点击操作，也可以为快捷操作，还可以为语音操作，本申请实施例对于第六操作的具体类型不作限定。
S1514、响应于第六操作，主设备显示第八界面，第八界面包括第二应用的页面。
第八界面为退出控制中心后显示的界面，可以对应于图6C中的f、图7B中的f所示的界面。
这样，第一应用和第二应用适配不同的方式，可以分别通过异源投屏、接续流转至第一从设备。主设备可以根据应用自动调整流转方式，实现智能流转，无需用户分别寻找对应的流转入口减少用户记忆成本，提升用户体验。
可选的，第二界面还包括第一应用的标识，第六界面还包括第二应用的标识；第二操作为拖拽第一应用的标识至第一从设备的设备标识附近的操作；第五操作为拖拽第二应用的标识至第一从设备的设备标识附近的操作。
本申请实施例中，第一应用的标识和第二应用的标识均可以对应于上文中的任务标识，此处不再赘述。第一应用的标识可以对应于A应用任务标识，第二应用的标识可以对应于B应用任务标识。
第一从设备的设备标识附近可以理解为与第一从设备的设备标识的距离小于第二阈值的情况。
这样，控制中心页面显示对应的应用的标识，简单直观，一目了然。通过拖拽应用的标识至从设备的设备标识附近选取从设备，操作简单，易于理解。
可选的，第一操作和第四操作相同，第一操作为下述操作中的任一个：三指上滑操作、双击操作、三指下滑操作、三击操作。
这样，通过快捷方式进入控制中心页面，操作方便快速，提升用户体验。
可选的，第三操作为在屏幕边缘的左滑操作或右滑操作，或者为针对第三界面显示的第一控件的点击操作；第六操作为在屏幕边缘的左滑操作或右滑操作，或者为针对第七界面显示的第一控件的点击操作。
第一控件可以对应于退出控件。可以理解的是，主设备可以通过侧滑操作退出控制中心页面，也可以通过点击控制中心页面上的退出控件退出控制中心页面。第三操作和第六操作可以相同，也可以不同。
这样，提供多种退出方式，用户可以通过合适的方式退出控制中心页面，提升用户体验。
可选的，主设备为手机、电脑、平板中的任意一种，第一从设备为手机、电脑、平板中的任意一种。
这样，可以适用于多种设备之间的任务流转，覆盖范围广，实用性高，提升用户体验。
可选的，第五界面和第八界面为不同的界面，第五界面包括第二应用的第一页面，第八界面包括第二应用的第二页面，第二应用的第一页面与第二应用的第二页面不同。
可以理解的是，第五界面可以对应于编辑中的页面，或其他修改中的页面。第二页面退出编辑的页面，或退出修改的页面。
这样，主设备在通过接续进行任务流转时，会退出编辑、修改等状态，任务流转前后应用显示的界面的内容不同。
可选的，第二应用为笔记应用；第二应用的第一页面为编辑页面，编辑页面包括第一笔记的内容；第二应用的第二页面为列表页面，列表页面包括第一笔记的标识。
本申请实施例中的任务流转可以适用于笔记应用，笔记应用流转前后应用显示的界面的内容不同。
可选的，第一界面只包括第一应用的页面，第四界面为主设备的桌面。
本申请实施例中的只包括第一应用的页面可以是指全屏显示第一应用的页面，也可以指除了上方的状态栏区域以外的区域显示第一应用的页面。或者只包括第一应用的页面可以理解为，除第一应用的页面不包括其他应用的页面。本申请实施例对此不作具体限定。
可以理解的是，当主设备通过异源投屏方式流转第一应用后，主设备关闭第一应用，不显示第一应用的页面。若主设备在前台仅运行第一应用，通过异源投屏方式流转第一应用后，显示桌面。
可选的，第一界面还包括第四应用的页面，第四应用的页面和第一应用的页面分屏显示；第四界面包括第四应用的页面。
第四应用可以为笔记应用，也可以为其他类型的应用，本申请实施例对此不作限定。第四应用可以与第二应用相同，也可以与第二应用不同。
可以理解的是，若主设备在前台运行第一应用和第四应用，通过异源投屏方式流转第一应用后，显示第四应用的页面。
可选的，第五界面还包括第五应用的页面，第五应用的页面和第二应用的页面分屏显示；第八界面还包括第五应用的页面，第二应用的页面和第五应用的页面分屏显示。
第五应用可以为视频应用，也可以为其他类型的应用，本申请实施例对此不作限定。第五应用可以与第一应用相同，也可以与第一应用不同。
可以理解的是，若主设备在前台运行第二应用和第五应用，通过接续方式流转第 二应用后，显示第二应用的页面和第五应用的页面。
可选的，第一界面还包括第一悬浮窗，第一悬浮窗显示有第六应用的页面；第二界面不包括第六应用的标识，第四界面还显示有第二控件；响应于用户对第二控件的操作，在第四界面上显示第一悬浮窗。
通过悬浮窗显示的应用可以对应于上文中的小窗应用。第六应用可以为视频应用，也可以为其他类型的应用，本申请实施例对此不作限定。第二控件可以对应于缩小后的小窗应用，也可以称为悬浮球。第四界面可以对应于图8A或图8B所示的界面。
可以理解的是，小窗应用不进行任务流转。任务流转后，小窗应用缩小至屏幕边缘。通过缩小后的小窗应用可以恢复小窗应用的显示。
可选的，第五界面还包括第二悬浮窗，第二悬浮窗显示有第七应用的页面；第六界面不包括第七应用的标识，第八界面还显示有第三控件；响应于用户对第三控件的操作，在第八界面上显示第二悬浮窗。第八界面可以对应于图8A或图8B所示的界面。
通过悬浮窗显示的应用可以对应于上文中的小窗应用。第七应用可以为视频应用，也可以为其他类型的应用，本申请实施例对此不作限定。第三控件可以对应于缩小后的小窗应用，也可以称为悬浮球。可以理解的是，小窗应用不进行任务流转。任务流转后，小窗应用缩小至屏幕边缘。通过缩小后的小窗应用可以恢复小窗应用的显示。
可选的，主设备为手机、电脑、平板中的任意一种，第一从设备为大屏，第四界面包括第一应用的页面。
当从设备为大屏时，第一应用通过同源投屏的方式进行任务流转。同源投屏中任务流转前后，应用的页面不变，显示的内容相同。从设备显示的页面与主设备显示的页面相同。
可选的，第一界面还包括第四应用的页面，第四应用的页面和第一应用的页面分屏显示时，第四界面不包括第四应用的页面。
分屏显示的场景中，同源投屏中任务流转前后，应用的页面不变，显示的内容相同。从设备显示的页面与主设备显示的页面相同。
可选的，主设备为手机、电脑、平板中的任意一种，第一从设备为大屏，第五界面包括的第二应用的页面和第八界面包括的第二应用的页面为相同的页面。
当从设备为大屏时，第二应用通过同源投屏的方式进行任务流转。同源投屏中任务流转前后，应用的页面不变，显示的内容相同。从设备显示的页面与主设备显示的页面相同。
可选的，第一应用的页面为播放视频的页面。
可选的，方法还包括：主设备显示第九界面，第九界面包括第八应用的页面；主设备接收到第七操作；响应于第七操作，主设备显示第十界面，第十界面包括第二从设备的设备标识；主设备接收到针对第二从设备的设备标识的第八操作；响应于第八操作，主设备显示第十一界面，第十一界面包括主设备的设备标识和第二从设备的设备标识，其中，主设备的设备标识与第二从设备的设备标识相连。
第九界面为应用的页面，可以对应于上文中图6A中的a、图6C中的a所示的界面，或其他运行有前台应用的页面。第七操作与第一操作类似，具体可以参照上述第一操作的说明，此处不再赘述。第十界面可以对应于未处于协同状态的控制中心页面。 第十一界面可以对应于协同中的控制中心页面。第八操作用于选取第二从设备的设备标识，可以为点击操作、拖拽操作，本申请实施例对于第八操作的具体类型不作限定。
本申请实施例中，相连可以为连接，可以为距离较近(紧挨等)，此处不作限定。
这样，控制中心页面还可以实现主设备和从设备之间的协同连接。
可选的，第八操作为拖拽第二从设备的设备标识至主设备的设备标识附近的操作。
主设备的设备标识附近可以理解为与主设备的设备标识的距离小于第三阈值的情况。
这样，通过拖拽从设备的设备标识至主设备的设备标识附近选取与主设备协同的从设备，操作简单，易于理解。
可选的，第十界面还包括第八应用的标识，第十一界面不包括第八应用的标识。
可以理解的是，未处于协同状态的控制中心页面显示有应用的标识，可进行任务流转；协同中的控制中心页面不显示应用的标识，无法进行任务流转。
可选的，第十一界面还包括第一标识，第一标识表示主设备与第二从设备之间的协同类型。
第一标识可以对应于同源投屏、屏幕扩展、屏幕镜像、键鼠共享等。
这样，方便用户确认主设备和从设备的协同类型，提升用户体验。
可选的，第十一界面还包括第二标识，方法还包括：主设备接收针对第二标识的第九操作；响应于第九操作，主设备和第二从设备切换到第二标识对应的协同类型。
第二标识可以对应于为同源投屏、屏幕扩展、屏幕镜像、键鼠共享等协同类型。第九操作可以为点击操作、触摸操作等，本申请实施例对于第九操作不作限定。
这样，用户可以通过第二标识调整主设备和从设备之间的协同类型，切换协同方式，提升用户体验。
可选的，第十一界面还包括第四控件，方法还包括：主设备接收到针对第四控件的第十操作；响应于第十操作，主设备断开与第二从设备的连接；主设备显示第十二界面，第十二界面包括主设备的设备标识和第二从设备的设备标识，主设备的设备标识与第二从设备的设备标识不相连。
第十二界面未断开协同连接后的控制中心页面，可以对应于图11A所示的界面。第四控件可以对应于断开连接控件(按钮)。第十操作可以为点击操作、触摸操作或其他类型的操作，本申请实施例对此不作具体限定。
这样，可以通过第四控件断开主设备与从设备的连接，断开协同，操作简便。
可选的，方法还包括：主设备在第十一界面接收到针对第二从设备的设备标识的第十一操作；响应于第十一操作，主设备断开与第二从设备的连接；主设备显示第十三界面，第十三界面包括主设备的设备标识和第二从设备的设备标识，主设备的设备标识与第二从设备的设备标识不相连。
第十三界面未断开协同连接后的控制中心页面，可以对应于图11B所示的界面。第十一操作可以为拖拽操作或其他类型的操作，本申请实施例对此不作具体限定。
这样，通过拖拽的方式断开主设备与从设备的连接，断开协同，操作简便。
可选的，第十一界面还包括第三从设备的标识，主设备的设备标识与第三从设备的设备标识不相连；方法还包括：主设备在第十一界面接收到针对第三从设备的设备 标识的第十二操作；响应于第十二操作，主设备断开与第二从设备的连接，并与第三从设备建立连接；主设备显示第十四界面，第十四界面包括主设备的设备标识、第二从设备的设备标识和第三从设备的标识，主设备的设备标识与第三从设备的设备标识相连，主设备的设备标识与第二从设备的设备标识不相连。
第十二操作用于切换与主设备连接的从设备。第十二操作可以为拖拽第三从设备的设备标识的操作，也可以为其他类型的操作，本申请实施例对此不作限定。第十四界面可以对应于图12所示的界面。
这样，主设备可以切换协同的从设备，提升用户体验。
可选的，协同类型包括以下类型中的任意一种：同源投屏、屏幕扩展、屏幕镜像、键鼠共享。
需要说明的是，本申请实施例中的“在……时”，可以为在某种情况发生的瞬时，也可以为在某种情况发生后的一段时间内，本申请实施例对此不作具体限定。此外，本申请实施例提供的显示界面仅作为示例，显示界面还可以包括更多或更少的内容。
上面已对本申请实施例的多设备任务流转方法进行了说明，下面对本申请实施例提供的执行上述多设备任务流转方法的装置进行描述。本领域技术人员可以理解，方法和装置可以相互结合和引用，本申请实施例提供的相关装置可以执行上述多设备任务流转方法中的步骤。
如图16所示，图16为本申请实施例提供的一种多设备任务流转装置的结构示意图，该多设备任务流转装置可以是本申请实施例中的终端设备，也可以是终端设备内的芯片或芯片系统。
如图16所示，多设备任务流转装置2100可以用于通信设备、电路、硬件组件或者芯片中，该多设备任务流转装置包括：显示单元2101、以及处理单元2102。其中，显示单元2101用于支持多设备任务流转装置2100执行的显示的步骤；处理单元2102用于支持多设备任务流转装置2100执行信息处理的步骤。
可能的实现方式中，该多设备任务流转装置2100中也可以包括通信单元2103。具体的，通信单元用于支持多设备任务流转装置2100执行数据的发送以及数据的接收的步骤。其中，该通信单元2103可以是输入或者输出接口、管脚或者电路等。
可能的实施例中，多设备任务流转装置还可以包括：存储单元2104。处理单元2102、存储单元2104通过线路相连。存储单元2104可以包括一个或者多个存储器，存储器可以是一个或者多个设备、电路中用于存储程序或者数据的器件。存储单元2104可以独立存在，通过通信线路与多设备任务流转装置具有的处理单元2102相连。存储单元2104也可以和处理单元2102集成在一起。
存储单元2104可以存储终端设备中的方法的计算机执行指令，以使处理单元2102执行上述实施例中的方法。存储单元2104可以是寄存器、缓存或者RAM等，存储单元2104可以和处理单元2102集成在一起。存储单元2104可以是只读存储器(read-only memory，ROM)或者可存储静态信息和指令的其他类型的静态存储设备，存储单元2104可以与处理单元2102相独立。
本申请实施例提供的多设备任务流转方法，可以应用在具备显示功能的电子设备 中。电子设备包括终端设备，终端设备的具体设备形态等可以参照上述相关说明，此处不再赘述。
本申请实施例提供一种电子设备，该电子设备包括：包括：处理器和存储器；存储器存储计算机执行指令；处理器执行存储器存储的计算机执行指令，使得电子设备执行上述方法。
本申请实施例提供一种芯片。芯片包括处理器，处理器用于调用存储器中的计算机程序，以执行上述实施例中的技术方案。其实现原理和技术效果与上述相关实施例类似，此处不再赘述。
本申请实施例还提供了一种计算机可读存储介质。计算机可读存储介质存储有计算机程序。计算机程序被处理器执行时实现上述方法。上述实施例中描述的方法可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。如果在软件中实现，则功能可以作为一个或多个指令或代码存储在计算机可读介质上或者在计算机可读介质上传输。计算机可读介质可以包括计算机存储介质和通信介质，还可以包括任何可以将计算机程序从一个地方传送到另一个地方的介质。存储介质可以是可由计算机访问的任何目标介质。
一种可能的实现方式中，计算机可读介质可以包括RAM，ROM，只读光盘(compact disc read-only memory，CD-ROM)或其它光盘存储器，磁盘存储器或其它磁存储设备，或目标于承载的任何其它介质或以指令或数据结构的形式存储所需的程序代码，并且可由计算机访问。而且，任何连接被适当地称为计算机可读介质。例如，如果使用同轴电缆，光纤电缆，双绞线，数字用户线(Digital Subscriber Line，DSL)或无线技术(如红外，无线电和微波)从网站，服务器或其它远程源传输软件，则同轴电缆，光纤电缆，双绞线，DSL或诸如红外，无线电和微波之类的无线技术包括在介质的定义中。如本文所使用的磁盘和光盘包括光盘，激光盘，光盘，数字通用光盘(Digital Versatile Disc，DVD)，软盘和蓝光盘，其中磁盘通常以磁性方式再现数据，而光盘利用激光光学地再现数据。上述的组合也应包括在计算机可读介质的范围内。
本申请实施例提供一种计算机程序产品，计算机程序产品包括计算机程序，当计算机程序被运行时，使得计算机执行上述方法。
本申请实施例是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程设备的处理单元以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理单元执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
以上的具体实施方式，对本发明的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上仅为本发明的具体实施方式而已，并不用于限定本发明的保护范围，凡在本发明的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本发明的保护范围之内。

Claims (29)

  1. 一种多设备任务流转方法，其特征在于，包括：
    主设备显示第一界面，所述第一界面包括第一应用的页面；
    所述主设备接收到第一操作；
    响应于所述第一操作，所述主设备显示第二界面，所述第二界面包括第一从设备的设备标识；
    所述主设备接收到针对所述第一从设备的设备标识的第二操作；
    响应于所述第二操作，所述主设备显示第三界面，并向所述第一从设备发送所述第一应用的页面，以使所述第一从设备显示所述第一应用的页面；
    所述主设备接收到第三操作，所述第三操作为返回操作；
    响应于所述第三操作，所述主设备显示第四界面，所述第四界面不包括所述第一应用的页面；
    所述主设备显示第五界面，所述第五界面包括第二应用的页面；
    所述主设备接收到第四操作；
    响应于所述第四操作，所述主设备显示第六界面，所述第六界面包括所述第一从设备的设备标识；
    所述主设备接收到针对所述第一从设备的设备标识的第五操作；
    响应于所述第五操作，所述主设备显示第七界面，并向所述第一从设备发送所述第二应用的页面上显示的内容，以使得所述第一从设备启动第三应用，所述第三应用与所述第二应用相对应，所述第三应用的页面显示的内容与所述第二应用的页面上显示的内容相同；
    所述主设备接收到第六操作，所述第六操作为返回操作；
    响应于所述第六操作，所述主设备显示第八界面，所述第八界面包括所述第二应用的页面。
  2. 根据权利要求1所述的方法，其特征在于，
    所述第二界面还包括所述第一应用的标识，所述第六界面还包括所述第二应用的标识；
    所述第二操作为拖拽所述第一应用的标识至所述第一从设备的设备标识附近的操作；
    所述第五操作为拖拽所述第二应用的标识至所述第一从设备的设备标识附近的操作。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第一操作和所述第四操作相同，所述第一操作为下述操作中的任一个：三指上滑操作、双击操作、三指下滑操作、三击操作。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，
    所述第三操作为在屏幕边缘的左滑操作或右滑操作，或者为针对所述第三界面显示的第一控件的点击操作；
    所述第六操作为在屏幕边缘的左滑操作或右滑操作，或者为针对所述第七界面显示的所述第一控件的点击操作。
  5. 根据权利要求1-4任一项所述的方法，其特征在于，所述主设备为手机、电脑、平板中的任意一种，所述第一从设备为手机、电脑、平板中的任意一种。
  6. 根据权利要求1-5任一项所述的方法，其特征在于，所述第五界面和所述第八界面为不同的界面，所述第五界面包括所述第二应用的第一页面，所述第八界面包括所述第二应用的第二页面，所述第二应用的第一页面与所述第二应用的第二页面不同。
  7. 根据权利要求6所述的方法，其特征在于，所述第二应用为笔记应用；
    所述第二应用的第一页面为编辑页面，所述编辑页面包括第一笔记的内容；
    所述第二应用的第二页面为列表页面，所述列表页面包括所述第一笔记的标识。
  8. 根据权利要求1-7任一项所述的方法，其特征在于，所述第一界面只包括所述第一应用的页面，所述第四界面为所述主设备的桌面。
  9. 根据权利要求1-7任一项所述的方法，其特征在于，所述第一界面还包括第四应用的页面，所述第四应用的页面和所述第一应用的页面分屏显示；
    所述第四界面包括所述第四应用的页面。
  10. 根据权利要求1-7、9任一项所述的方法，其特征在于，所述第五界面还包括第五应用的页面，所述第五应用的页面和所述第二应用的页面分屏显示；
    所述第八界面还包括所述第五应用的页面，所述第二应用的页面和所述第五应用的页面分屏显示。
  11. 根据权利要求1-10任一项所述的方法，其特征在于，所述第一界面还包括第一悬浮窗，所述第一悬浮窗显示有第六应用的页面；
    所述第二界面不包括所述第六应用的标识，所述第四界面还显示有第二控件；
    响应于用户对所述第二控件的操作，在所述第四界面上显示所述第一悬浮窗。
  12. 根据权利要求1-10任一项所述的方法，其特征在于，所述第五界面还包括第二悬浮窗，所述第二悬浮窗显示有第七应用的页面；
    所述第六界面不包括所述第七应用的标识，所述第八界面还显示有第三控件；
    响应于用户对所述第三控件的操作，在所述第八界面上显示所述第二悬浮窗。
  13. 根据权利要求1-4、9任一项所述的方法，其特征在于，所述主设备为手机、电脑、平板中的任意一种，所述第一从设备为大屏，所述第四界面包括所述第一应用的页面。
  14. 根据权利要求13所述的方法，其特征在于，所述第一界面还包括第四应用的页面，所述第四应用的页面和所述第一应用的页面分屏显示时，所述第四界面不包括所述第四应用的页面。
  15. 根据权利要求1-4、10任一项所述的方法，其特征在于，所述主设备为手机、电脑、平板中的任意一种，所述第一从设备为大屏，
    所述第五界面包括的所述第二应用的页面和所述第八界面包括的所述第二应用的页面为相同的页面。
  16. 根据权利要求1-15任一项所述的方法，其特征在于，所述第一应用的页面为播放视频的页面。
  17. 根据权利要求1-16任一项所述的方法，其特征在于，所述方法还包括：
    所述主设备显示第九界面，所述第九界面包括第八应用的页面；
    所述主设备接收到第七操作；
    响应于所述第七操作，所述主设备显示第十界面，所述第十界面包括第二从设备的设备标识；
    所述主设备接收到针对所述第二从设备的设备标识的第八操作；
    响应于所述第八操作，所述主设备显示第十一界面，所述第十一界面包括所述主设备的设备标识和所述第二从设备的设备标识，其中，所述主设备的设备标识与所述第二从设备的设备标识相连。
  18. 根据权利要求17所述的方法，其特征在于，所述第八操作为拖拽所述第二从设备的设备标识至所述主设备的设备标识附近的操作。
  19. 根据权利要求17或18所述的方法，其特征在于，
    所述第十界面还包括所述第八应用的标识，所述第十一界面不包括所述第八应用的标识。
  20. 根据权利要求17-19任一项所述的方法，其特征在于，所述第十一界面还包括第一标识，所述第一标识表示所述主设备与所述第二从设备之间的协同类型。
  21. 根据权利要求20所述的方法，其特征在于，所述第十一界面还包括第二标识，所述方法还包括：
    所述主设备接收针对所述第二标识的第九操作；
    响应于所述第九操作，所述主设备和所述第二从设备切换到所述第二标识对应的协同类型。
  22. 根据权利要求17-21任一项所述的方法，其特征在于，所述第十一界面还包括第四控件，所述方法还包括：
    所述主设备接收到针对所述第四控件的第十操作；
    响应于所述第十操作，所述主设备断开与所述第二从设备的连接；
    所述主设备显示第十二界面，所述第十二界面包括所述主设备的设备标识和所述第二从设备的设备标识，所述主设备的设备标识与所述第二从设备的设备标识不相连。
  23. 根据权利要求17-21任一项所述的方法，其特征在于，所述方法还包括：
    所述主设备在所述第十一界面接收到针对所述第二从设备的设备标识的第十一操作；
    响应于所述第十一操作，所述主设备断开与所述第二从设备的连接；
    所述主设备显示第十三界面，所述第十三界面包括所述主设备的设备标识和所述第二从设备的设备标识，所述主设备的设备标识与所述第二从设备的设备标识不相连。
  24. 根据权利要求17-21任一项所述的方法，其特征在于，所述第十一界面还包括第三从设备的标识，所述主设备的设备标识与所述第三从设备的设备标识不相连；
    所述方法还包括：
    所述主设备在所述第十一界面接收到针对所述第三从设备的设备标识的第十二操作；
    响应于所述第十二操作，所述主设备断开与所述第二从设备的连接，并与所述第三从设备建立连接；
    所述主设备显示第十四界面，所述第十四界面包括所述主设备的设备标识、所述 第二从设备的设备标识和所述第三从设备的标识，所述主设备的设备标识与所述第三从设备的设备标识相连，所述主设备的设备标识与所述第二从设备的设备标识不相连。
  25. 根据权利要求17-24任一项所述的方法，其特征在于，所述协同类型包括以下类型中的任意一种：同源投屏、屏幕扩展、屏幕镜像、键鼠共享。
  26. 根据权利要求16-25任一项所述的方法，其特征在于，
    所述第二从设备为手机、电脑、平板、大屏中的任意一种。
  27. 一种电子设备，其特征在于，包括：处理器和存储器；
    所述存储器存储计算机执行指令；
    所述处理器执行所述存储器存储的计算机执行指令，使得所述电子设备执行如权利要求1-26中任一项所述的方法。
  28. 一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，其特征在于，所述计算机程序被处理器执行时实现如权利要求1-26任一项所述的方法。
  29. 一种计算机程序产品，其特征在于，包括计算机程序，当所述计算机程序被运行时，使得计算机执行如权利要求1-26任一项所述的方法。
PCT/CN2023/119815 2022-11-22 2023-09-19 多设备任务流转方法和相关装置 WO2024109296A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211474246.3 2022-11-22
CN202211474246.3A CN118069021A (zh) 2022-11-22 2022-11-22 多设备任务流转方法和相关装置

Publications (1)

Publication Number Publication Date
WO2024109296A1 true WO2024109296A1 (zh) 2024-05-30

Family

ID=91109725

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/119815 WO2024109296A1 (zh) 2022-11-22 2023-09-19 多设备任务流转方法和相关装置

Country Status (2)

Country Link
CN (1) CN118069021A (zh)
WO (1) WO2024109296A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114691059A (zh) * 2020-12-25 2022-07-01 华为技术有限公司 一种投屏显示方法及电子设备
CN114924671A (zh) * 2022-07-18 2022-08-19 荣耀终端有限公司 应用接续方法和装置
CN115002937A (zh) * 2022-07-18 2022-09-02 荣耀终端有限公司 一种多设备协同方法、电子设备及相关产品
CN115033319A (zh) * 2021-06-08 2022-09-09 华为技术有限公司 一种应用界面的分布式显示方法及终端

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114691059A (zh) * 2020-12-25 2022-07-01 华为技术有限公司 一种投屏显示方法及电子设备
CN115033319A (zh) * 2021-06-08 2022-09-09 华为技术有限公司 一种应用界面的分布式显示方法及终端
CN114924671A (zh) * 2022-07-18 2022-08-19 荣耀终端有限公司 应用接续方法和装置
CN115002937A (zh) * 2022-07-18 2022-09-02 荣耀终端有限公司 一种多设备协同方法、电子设备及相关产品

Also Published As

Publication number Publication date
CN118069021A (zh) 2024-05-24

Similar Documents

Publication Publication Date Title
WO2021227770A1 (zh) 应用窗口显示方法和电子设备
WO2021052147A1 (zh) 一种数据传输的方法及相关设备
KR102350329B1 (ko) 전화 통화 동안의 실시간 공유 기법
WO2021057830A1 (zh) 一种信息处理方法及电子设备
WO2022100305A1 (zh) 画面跨设备显示方法与装置、电子设备
WO2022052671A1 (zh) 一种显示窗口的方法、切换窗口的方法、电子设备和系统
KR102058465B1 (ko) 전자기기 원격제어 시스템 및 이의 운용방법
US20240111473A1 (en) Distributed display method and terminal for application interface
JP2023503679A (ja) マルチウィンドウ表示方法、電子デバイス及びシステム
WO2024016559A1 (zh) 一种多设备协同方法、电子设备及相关产品
CN114244953B (zh) 一种界面显示方法、电子设备及存储介质
CN115516413A (zh) 一种对象拖拽方法及设备
WO2023226455A1 (zh) 应用图标的显示方法、电子设备及可读存储介质
US20240086231A1 (en) Task migration system and method
WO2022089294A1 (zh) 一种设备间屏幕协同方法及设备
WO2021052488A1 (zh) 一种信息处理方法及电子设备
WO2024109296A1 (zh) 多设备任务流转方法和相关装置
WO2023035834A1 (zh) 一种Wi-Fi直连通信方法及装置
WO2021027727A1 (zh) 信息传输的方法和电子设备
CN115408119A (zh) 任务迁移的系统及方法
CN118069081A (zh) 多设备任务流转方法和相关装置
WO2023029993A1 (zh) 一种搜索方法和电子设备
CN118069080A (zh) 多设备任务流转方法和相关装置
CN115941674B (zh) 多设备应用接续方法、设备及存储介质
WO2022228004A1 (zh) 多屏协同过程中恢复窗口的方法、电子设备和系统