Multi-device cooperation method, electronic device and related product

Abstract

The embodiment of the invention provides a multi-device cooperation method, an electronic device and a related product. The method comprises the steps that a first electronic device responds to user operation and displays a first page, and the first page comprises a device identifier of the first electronic device and a device identifier of at least one slave device; the first electronic device establishes multi-device collaboration with the target device based on the first collaboration type in response to the operation of the user on the device identifier of the target device in the first page, and displays a type switching card in the first page; wherein the target device is any one of the at least one slave device, and the type switching card comprises a type identifier of at least one cooperation type supported between the first electronic device and the target device. Thus, a user can perform unified management on multi-device collaboration between the first electronic device and each slave device in the first page, and does not need to search for control entries of various collaboration types in different user interfaces, thereby improving the user experience.

Description

Multi-device collaboration method, electronic device, and related products

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on August 5, 2022, with application number 202210940127.6 and invention name “A multi-device collaboration method, electronic device and related products”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of terminal technology, and in particular to a multi-device collaboration method, electronic equipment, and related products. Background Art

[0003] Multi-device collaboration is a distributed technology applied to multiple electronic devices. It enables two or more electronic devices to collaborate across systems and devices, enabling resource sharing and collaborative operations.

[0004] With the continuous development of terminal technology, multi-device collaboration has produced a variety of different types of collaboration, such as screen projection, multi-screen collaboration, etc. At present, there is no unified control entrance for each type of collaboration in the terminal device, and the control entrances for each type of collaboration are distributed in different user interfaces. For example, the control entrance for screen projection may be located in the playback interface of a video application, and the control entrance for multi-screen collaboration may be located in a sub-page of the system settings application. Therefore, in order to establish different types of multi-device collaboration, users need to find the corresponding control entrances in different user interfaces and perform operations. This requires users to remember the location of the control entrance for each type of multi-screen collaboration, resulting in a high memory cost for users and reducing the user experience.

[0005] Summary of the Invention

[0006] The embodiments of the present application provide a multi-device collaboration method, electronic device, and related products to improve the user experience of multi-device collaboration.

[0007] In the first aspect, an embodiment of the present application provides a multi-device collaboration method, including: a first electronic device displays a first page in response to a user operation, the first page including a device identification of the first electronic device and a device identification of at least one slave device; the first electronic device establishes multi-device collaboration with the first target device based on a first collaboration type in response to the user's operation on the device identification of the first target device in the first page, and displays a type switching card in the first page; wherein the first target device is any one of the at least one slave device, and the type switching card includes a type identification of at least one collaboration type supported between the first electronic device and the first target device.

[0008] In the method provided in the embodiment of the present application, the first page includes the device identifications of each slave device around the first electronic device. In this way, the user can establish multi-device collaboration between the first electronic device and any slave device by operating the device identification of any slave device. The user does not need to search for control entrances of various collaboration types in different user interfaces, thereby improving the user experience.

[0009] In one implementation, the method further includes: the first electronic device switches the collaboration type between the first electronic device and the first target device from the first collaboration type to the second collaboration type in response to the user clicking the type identifier of the second collaboration type in the type switching card; wherein the second collaboration type is any one of at least one collaboration type, and the first collaboration type is different from the second collaboration type. In this way, when the first electronic device and the first target device support multiple collaboration modes, the first electronic device and the first target device can first establish multi-device collaboration based on a preset collaboration type, and then the user can select the collaboration type they want to use on the first electronic device. The first electronic device can switch from the preset collaboration type to the collaboration type the user wants to use based on the user's selection, thereby improving the user experience.

[0010] In one implementation, the method further includes: the first electronic device displays a second page in response to a user operation, the second page including a multi-device collaboration card, wherein if the first electronic device searches for at least one slave device, the multi-device collaboration card includes a device identifier of at least one slave device; the first electronic device initiates multi-device collaboration to a second target device based on a third collaboration type in response to the user's operation in the multi-device collaboration card, the second target device being any one of the at least one slave device; after the first electronic device establishes multi-device collaboration with the second target device, the device identifier of the second target device in the multi-device collaboration card is switched to a collaboration identifier of the third collaboration type. In this way, the user can establish multi-device collaboration with any slave device by clicking on the device identifier of any slave device in the multi-device collaboration card, without the user having to search for control entries of various collaboration types in different user interfaces, thereby improving the user experience.

[0011] In one implementation, the method further includes: the first electronic device terminating the multi-device collaboration between the first electronic device and the second target device in response to the user clicking a collaboration indicator of the third collaboration type in the multi-device collaboration card. In this way, the user can directly terminate the established multi-device collaboration in the multi-device collaboration card without having to search for control entries for various collaboration types in different user interfaces, thereby improving the user experience.

[0012] In one implementation, the method further includes: if the first electronic device has not found a slave device and is currently searching for a slave device, including a first animation identifier in the multi-device collaboration card, the first animation identifier being used to indicate that the first electronic device is searching for a slave device. In this way, the first electronic device can provide feedback to the user that it is searching for a slave device, thereby improving the user experience.

[0013] In one implementation, the method further includes: if the first electronic device has not searched for a slave device and is not currently searching for a slave device, the multi-device collaboration card includes a first button; and the first electronic device searches for a slave device in response to a user clicking the first button. In this way, when the first electronic device has not currently searched for a slave device, the user can manually search for a slave device, thereby improving the user experience.

[0014] In one implementation, the method further includes: before displaying the second page, when the first electronic device determines that the current scene is the first scene, determining whether at least one slave device is searched; if at least one slave device is searched, the second page includes a multi-device collaboration card, and the multi-device collaboration card includes the device identification of at least one slave device; if no slave device is searched, the second page does not include the multi-device collaboration card; wherein the first scene includes at least one of the following: the first electronic device displays the second page for the first time after the operating system is initialized; the first electronic device displays the second page for the first time after the logged-in account changes; the first electronic device displays the second page for the first time after restoring factory settings or clearing data. In this way, when the first electronic device displays the second page for the first time, if no slave device is searched, the multi-device collaboration card may not be displayed, thereby reducing disturbance to the user and improving the user experience.

[0015] In one implementation, the first electronic device displays the first page in response to a user operation, including: the first electronic device displays the first page in response to a user operation in a multi-device collaboration card. In this way, the first electronic device can directly jump from the second page to the first page in response to the user operation, so that the user can perform operations such as switching collaboration types on the first page, thereby improving the user experience.

[0016] In one implementation, the first electronic device displays the first page in response to the user's operation in the multi-device collaborative card, including: the first electronic device displays the first page in response to the user's operation of long pressing the device identifier of any electronic device in the multi-device collaborative card.

[0017] In one implementation, the first electronic device displays the first page in response to the user's operation in the multi-device collaboration card, including: the first electronic device displays the first page in response to the user's operation of long pressing the collaboration identifier of the third collaboration type in the multi-device collaboration card.

[0018] In one implementation, the multi-device collaboration card includes a second button, and the first electronic device displays the first page in response to the user's operation in the multi-device collaboration card, including: the first electronic device displays the first page in response to the user's operation of clicking the second button in the multi-device collaboration card.

[0019] In this way, users can open the first page in multiple ways and manage multi-device collaboration in the first page, which improves the user experience.

[0020] In one implementation, the first electronic device establishes multi-device collaboration with the first target device based on the first collaboration type in response to a user's operation on the device identifier of the first target device in the first page, and displays a type switching card in the first page, including: the first electronic device establishes multi-device collaboration with the first target device based on the first collaboration type in response to the user's operation of dragging the device identifier of the first target device on the first page so that the device identifier of the first target device contacts the device identifier of the first electronic device, and displays a type switching card in the first page.

[0021] In one implementation, the type switching card further includes a third button, and the method further includes: in response to the user clicking the third button, the first electronic device disconnecting the multi-device collaboration between the first electronic device and the first target device. In this way, the user can terminate the multi-device collaboration between the first electronic device and the first target device on the second page, thereby improving the user experience.

[0022] In one implementation, the first page also includes a fourth button, and the method further includes: the first electronic device, in response to a user clicking the fourth button, displays a third page, the third page including a first list, the first list including at least one collaborative type option; the first electronic device, in response to the user clicking the first option, displays a fourth page, the first option being any collaborative type option in the first list, the fourth page including a switch button for the collaborative type corresponding to the first option; and the first electronic device, in response to the user clicking the switch button, turns on or off the collaborative type corresponding to the first option. In this way, the user can control each collaborative type, such as turning it on and off, thereby improving the user experience.

[0023] In one implementation, the method also includes: in a state where the first electronic device and the first slave device have established multi-device collaboration based on the fourth collaboration type, in response to the user's operation on the device identification of the first target device on the first page, a first switching card is generated, wherein the fourth collaboration type does not support three electronic devices being connected at the same time, and the first switching card is used to ask the user whether to switch the collaborative device; the first electronic device ends the multi-device collaboration with the first slave device in response to the user's operation on the first switching card, and establishes multi-device collaboration between the first electronic device and the first target device.

[0024] In one implementation, the method further includes: in a state where the first electronic device and the first slave device have established multi-device collaboration based on the fifth collaboration type, in response to the user's operation on the device identification of the first target device on the first page, adding the first target device to the established multi-device collaboration, wherein the fifth collaboration type supports three electronic devices to be connected at the same time.

[0025] In one implementation, the method also includes: in a state where the first electronic device has established multi-device collaboration with the out-of-loop device, in response to the user's operation on the device identifier of the first target device on the first page, generating a second switch card, the second switch card being used to ask the user whether to switch the collaborative device; the first electronic device ends the multi-device collaboration with the out-of-loop device in response to the user's operation on the second switch card, and establishes multi-device collaboration between the first electronic device and the first target device.

[0026] In one implementation, the method also includes: when the first target device and other slave devices or out-of-loop devices have established multi-device collaboration based on the fourth collaboration type, the first electronic device generates a third switching card in response to the user's operation on the device identification of the first target device on the first page, wherein the fourth collaboration type does not support three electronic devices connected at the same time, and the third switching card is used to ask the user whether to switch the collaborative device; the first electronic device ends the multi-device collaboration established by the first target device in response to the user's operation on the third switching card, and establishes multi-device collaboration between the first electronic device and the first target device.

[0027] In one implementation, the method also includes: when the first target device and other slave devices or out-of-loop devices have established multi-device collaboration based on the fifth collaboration type, the first electronic device joins the multi-device collaboration established by the first target device in response to the user's operation on the device identification of the first target device on the first page, wherein the fifth collaboration type supports three electronic devices to be connected at the same time.

[0028] In one implementation, the method also includes: when the first electronic device and the first target device have both established multi-device collaboration with other slave devices or devices outside the loop, the first electronic device generates a fourth switch card in response to the user's operation on the device identification of the first target device on the first page, and the fourth switch card is used to ask the user whether to switch the collaborative device; the first electronic device ends the multi-device collaboration that has been established between the first electronic device and the first target device in response to the user's operation on the fourth switch card, and establishes multi-device collaboration between the first electronic device and the first target device.

[0029] In one implementation, the method also includes: when the second target device has established multi-device collaboration with other slave devices or out-of-loop devices, the first electronic device generates a fifth switching card in response to the user clicking the device identifier of the second target device on the multi-device collaboration card, and the fifth switching card is used to ask the user whether to switch the collaborative device; the first electronic device ends the multi-device collaboration established by the second target device in response to the user's operation on the fifth switching card, and establishes multi-device collaboration between the first electronic device and the second target device.

[0030] In this way, when the first electronic device and / or the slave device have established multi-device collaboration, the first electronic device can respond to the user's operations in the multi-device collaboration main page and adopt different strategies to add or switch devices participating in the multi-device collaboration according to different scenarios, thereby improving the user experience.

[0031] In the second aspect, an embodiment of the present application also provides a multi-device collaboration device, including: a first display module, used to display a first page in response to user operation, the first page including the device identification of the first electronic device and the device identification of at least one slave device; a second display module, used to establish multi-device collaboration with the target device based on the first collaboration type in response to the user's operation on the device identification of the target device in the first page, and display a type switching card in the first page; wherein the target device is any one of the at least one slave device, and the type switching card includes the type identification of at least one collaboration type supported between the first electronic device and the target device.

[0032] In the apparatus provided in an embodiment of the present application, the first page includes the device identifications of each slave device surrounding the first electronic device. In this way, the user can establish multi-device collaboration between the first electronic device and any slave device by operating the device identification of any slave device. The user does not need to search for control entrances of various collaboration types in different user interfaces, thereby improving the user experience.

[0033] In a third aspect, an embodiment of the present application further provides a computer-readable storage medium, in which instructions are stored. When the computer-readable storage medium is run on a computer, the computer executes the above-mentioned aspects and methods of each implementation thereof.

[0034] In a fourth aspect, an embodiment of the present application further provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the above-mentioned aspects and methods of their respective implementations.

[0035] In a fifth aspect, an embodiment of the present application further provides a chip system, which includes a processor for supporting the above-mentioned terminal device to implement the functions involved in the above-mentioned aspects, for example, generating or processing the information involved in the above-mentioned method. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] FIG1 is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application;

[0037] FIG2 is a software structure block diagram of an electronic device according to an embodiment of the present application;

[0038] FIG3 is a first flow chart of a multi-device collaboration method provided in an embodiment of the present application;

[0039] FIG4A is a first schematic diagram of a control center page provided in an embodiment of the present application;

[0040] FIG4B is a second schematic diagram of the control center page provided in an embodiment of the present application;

[0041] FIG4C is a third schematic diagram of the control center page provided in an embodiment of the present application;

[0042] FIG4D is a fourth schematic diagram of the control center page provided in an embodiment of the present application;

[0043] FIG5 is a first set of interaction example diagrams of a multi-device collaboration method provided in an embodiment of the present application;

[0044] FIG6 is a second set of interaction example diagrams of a multi-device collaboration method provided in an embodiment of the present application;

[0045] FIG7 is a third set of interaction example diagrams of a multi-device collaboration method provided in an embodiment of the present application;

[0046] FIG8 is a second flow chart of a multi-device collaboration method provided in an embodiment of the present application;

[0047] 9A-9D are a fourth set of interaction example diagrams of a multi-device collaboration method provided in an embodiment of the present application;

[0048] 10A-10D are a fifth set of interaction example diagrams of a multi-device collaboration method provided in an embodiment of the present application;

[0049] 11A-11D are a sixth set of interaction example diagrams of a multi-device collaboration method provided in an embodiment of the present application;

[0050] 12A-12D are the seventh set of interaction example diagrams of a multi-device collaboration method provided in an embodiment of the present application;

[0051] 13A-13C are exemplary diagrams of methods for enabling and disabling automatic collaborative services according to an embodiment of the present application;

[0052] FIG14 is an example diagram of interaction in scenario 1 of the multi-device collaboration method provided in an embodiment of the present application;

[0053] FIG15 is a first interaction example diagram of sub-scenario 1 of a multi-device collaboration method provided in an embodiment of the present application;

[0054] FIG16 is a second interaction example diagram of sub-scenario 1 of a multi-device collaboration method provided in an embodiment of the present application;

[0055] FIG17 is an example diagram of interaction of sub-scenario 2 of a multi-device collaboration method provided in an embodiment of the present application;

[0056] FIG18 is a first interaction example diagram of scenario three of a multi-device collaboration method provided in an embodiment of the present application;

[0057] FIG19 is a second interaction example diagram of scenario three of a multi-device collaboration method provided in an embodiment of the present application;

[0058] FIG20 is an example diagram of interaction in scenario 4 of a multi-device collaboration method provided in an embodiment of the present application;

[0059] FIG21 is another example diagram of interaction of a multi-device collaboration method provided by an embodiment of the present application;

[0060] FIG22 is another example diagram of interaction of a multi-device collaboration method provided in an embodiment of the present application;

[0061] FIG23 is a schematic diagram of the structure of a multi-device collaboration apparatus provided in an embodiment of the present application;

[0062] Figure 24 is a structural diagram of another multi-device collaboration device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0063] Multi-device collaboration is a distributed technology applied to multiple electronic devices. It enables two or more electronic devices to collaborate across systems and devices, enabling resource sharing and collaborative operations.

[0064] Multi-device collaboration can be applied between electronic devices of the same or different types. These include, but are not limited to, mobile phones, tablets, laptops, large-screen devices (e.g., smart TVs and smart screens), personal computers (PCs), handheld computers, netbooks, personal digital assistants (PDAs), wearable electronic devices, in-vehicle devices, and virtual reality devices.

[0065] Multi-device collaboration needs to be implemented based on communication connections between devices. The communication connection can be a wired communication connection or a wireless communication connection. Among them, the wired communication connection solution can include, for example, USB On-The-Go (OTG) technology; the wireless communication solution can include, for example, wireless fidelity (Wi-Fi), Wi-Fi Direct (Wi-Fi Direct), Bluetooth (BT), near field communication technology (NFC), infrared technology (IR), etc.

[0066] With the continuous development of terminal technology, multi-device collaboration has produced a variety of different types of collaboration (also known as collaborative services), such as screen extension, screen projection, super call, screen mirroring, multi-screen collaboration, super notification, keyboard and mouse sharing, super keyboard and mouse, etc. Among them:

[0067] Screen extension: 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 screens of electronic device A and electronic device B can display content together, expanding the display capabilities of electronic device A.

[0068] Screen casting: Casting the content (e.g., videos, photos, etc.) on the screen of electronic device A to the screen of electronic device B for display. During screen casting, users can select part or all of the content on the screen of electronic device A to be cast to the screen of electronic device B for display. Some screen casting methods also allow users to switch the screen to other pages during casting without affecting the continued playback of the casted content on electronic device B, such as DLNA screen casting.

[0069] Super Call: When electronic device A receives an incoming voice call or video call, the incoming call interface can be displayed on electronic device B at the same time, so that the user can choose to answer or hang up the call on electronic device B.

[0070] Screen mirroring: Mirrors all the content on the screen of electronic device A to the screen of electronic device B. The content displayed on electronic device B is the same as that on electronic device A, and changes as the content displayed on electronic device A changes.

[0071] Multi-screen collaboration: Projecting the user interface of electronic device A onto the screen of electronic device B for display, allowing the user to operate the user interface of electronic device A on electronic device B, and transferring files from electronic device B to electronic device A by performing specific operations on electronic device B (for example, dragging and dropping files from the user interface of electronic device B to the user interface of electronic device A), thereby enabling cross-device operations and cross-device file transfers 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 it can be displayed full screen.

[0072] Super Notification: When electronic device A receives a notification message, the notification message can be displayed synchronously on electronic device B, and the user can also perform operations such as reply, delete, and read on the notification message on electronic device B.

[0073] Keyboard and mouse sharing: Electronic devices A and B can share each other's existing input devices, such as a mouse and keyboard. For example, if electronic device A's input device is shared with electronic device B, the shared input device can be used for input on both electronic devices A and B. Furthermore, with keyboard and mouse sharing, electronic devices A and B can also transfer files.

[0074] Super Continuation: When a user runs an application on electronic device A, the interface of electronic device B may prompt the user to open the application currently running on electronic device A on electronic device B, thereby transferring the user to electronic device B for continued operation, such as watching a video or editing a document. For example, a document application (such as Memo or Word) is running on electronic device A. The user is editing the document on electronic device A. When electronic device B is close to electronic device A, a prompt message is displayed on electronic device B. The user clicks the prompt message on electronic device B. In response to the user's click, electronic device B opens the document application and displays the location where the user is editing, so the user can continue editing on electronic device B.

[0075] Among the multiple collaboration types listed above: 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 expansion, screen projection, screen mirroring, multi-screen collaboration, keyboard and mouse sharing, etc.; other collaboration types are automatically triggered when the triggering 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 call, super notification, super connection, etc.

[0076] For two electronic devices, the collaboration 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 collaboration type or multiple collaboration types.

[0077] Take manual collaboration service as an example:

[0078] If the master device is a mobile phone and the slave device is a tablet computer, the supported collaboration types may include multi-screen collaboration.

[0079] If the master device is a non-foldable phone and the slave device is a PC, the supported collaboration types include Super Keyboard and Mouse and Multi-screen Collaboration. When a non-foldable phone and PC are connected for the first time, the default collaboration type is Multi-screen Collaboration.

[0080] If the master device is a foldable phone and the slave device is a PC, supported collaboration types include Super Keyboard and Mouse, Multi-screen Collaboration, Screen Mirroring, and Screen Extension. When a foldable phone and PC are connected for the first time, the default collaboration type is Multi-screen Collaboration.

[0081] If the master device is a mobile phone and the slave device is a large-screen device, the supported collaboration types may include screen projection.

[0082] If the master device is a tablet computer and the slave device is a mobile phone, the supported collaboration types may include multi-screen collaboration.

[0083] If the master device is a tablet and the slave device is a PC, the supported collaboration types include screen mirroring, screen extension, and super keyboard and mouse. When the tablet and PC are first connected, the default collaboration type is screen mirroring.

[0084] If the master device is a tablet and the slave device is a large-screen device, the supported collaboration types may include screen projection.

[0085] If the master device is a PC and the slave device is a non-foldable phone, the supported collaboration types include Super Keyboard and Mouse and Multi-screen Collaboration. When a PC and a non-foldable phone are connected for the first time, the default collaboration type is Multi-screen Collaboration.

[0086] If the master device is a PC and the slave device is a foldable phone, the supported collaboration types include Super Keyboard and Mouse, Multi-screen Collaboration, Screen Mirroring, and Screen Extension. When the PC and foldable phone are first connected, the default collaboration type is Multi-screen Collaboration.

[0087] If the master device is a PC and the slave device is a tablet, the supported collaboration types include screen mirroring, screen extension, and super keyboard and mouse. When the PC and tablet are first connected, the default collaboration type is screen mirroring.

[0088] If the master device is a PC and the slave device is a large-screen device, the supported collaboration types may include screen projection.

[0089] Take the automatic collaborative service as an example:

[0090] Electronic devices that support super calls may include mobile phones, tablets, PCs, large-screen display devices, etc.

[0091] Electronic devices that support super notifications may include mobile phones, tablets, PCs, etc.

[0092] Electronic devices that support super connection may include mobile phones, tablets, PCs, large-screen display devices, etc.

[0093] In the traditional solution, there is no unified control entrance for each type of collaboration in the terminal device, and the control entrances for each type of collaboration are distributed in different user interfaces. For example, the control entrance for screen projection may be located in the playback interface of a video application, and the control entrance for multi-screen collaboration may be located in a secondary page of the system settings application. Therefore, in order to establish different types of multi-device collaboration, users need to find the corresponding control entrances in different user interfaces and perform operations. This requires users to remember the location of the control entrance for each type of multi-screen collaboration, resulting in a high memory cost for users and reducing the user experience.

[0094] In order to solve the above technical problems, an embodiment of the present application provides a multi-device collaboration method.

[0095] The multi-device collaboration method of the embodiment of the present application can be applied to various types of electronic devices with display functions.

[0096] FIG1 is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application. The device can be used as both a master device and a slave device in a multi-device collaboration. As shown in FIG1 , the electronic device 100 may include a processor 110, a memory 120, a universal serial bus (USB) interface 130, a radio frequency circuit 140, a mobile communication module 150, a wireless communication module 160, a camera 170, a display screen 180, a touch sensor 190, an air pressure sensor 210, and a button 220, etc.

[0097] The processor 110 may include one or more processing units, for example: the processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Among them, different processing units can be independent devices or integrated into one or more processors, for example, integrated into a system on a chip (SoC). A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a high-speed cache memory. The memory can save instructions or data that the processor 110 has just used or recycled.

[0098] In some embodiments, the processor 110 may include one or more interfaces. The interfaces 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.

[0099] The memory 120 can be used to store computer executable program code, and the executable program code includes instructions. The memory 120 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 electronic device 100 (such as audio data, a phone book, etc.), etc. In addition, the memory 120 may include one or more storage units, for example, a volatile memory (volatile memory), such as a dynamic random access memory (DRAM), a static random access memory (SRAM), etc.; and a non-volatile memory (NVM), such as a read-only memory (ROM), a flash memory, etc. The processor 110 executes various functional applications and data processing of the electronic device 100 by running instructions stored in the memory 120 and / or instructions stored in a memory provided in the processor.

[0100] It should be noted here that the operating system referred to in the embodiments of this application includes but is not limited to Android operating system, IOS operating system, iPad OS, HarmonyOS, Windows operating system, Linux operating system, MAC OS operating system, embedded system, etc.

[0101] The wireless communication function of the electronic device 100 can be implemented through the radio frequency circuit 140, the mobile communication module 150, the wireless communication module 160, the modem processor, and the baseband processor.

[0102] The radio frequency circuit 140 may include at least one antenna 141 for transmitting and receiving electromagnetic wave signals. Each antenna in the electronic device 100 may be used to cover a single or multiple communication frequency bands. In some embodiments, the antenna may be used in conjunction with a tuning switch.

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

[0104] The modem processor may include a modulator and a demodulator. The modulator is used to modulate the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After being processed by the baseband processor, the low-frequency baseband signal is passed to the application processor. The application processor outputs a sound signal through an audio device (including but not limited to a speaker, a receiver, etc.) or displays an image or video through the display screen 180. In some embodiments, the modem processor may be an independent device. In other embodiments, the modem processor may be independent of the processor 110 and be set in the same device as the mobile communication module 150 or other functional modules.

[0105] The wireless communication module 160 may include a wireless fidelity (Wi-Fi) module, a Bluetooth (BT) module, a GNSS module, a near field communication (NFC) module, an infrared (IR) module, and the like. The wireless communication module 160 may be one or more devices integrating at least one of the above modules. The wireless communication module 160 receives electromagnetic waves via the antenna 141, modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110. The wireless communication module 160 may also receive signals to be transmitted from the processor 110, modulate the frequencies of the signals, amplify the signals, and convert them into electromagnetic waves for radiation via the antenna 141.

[0106] In the embodiment of the present application, the wireless communication function of the electronic device 100 may include, for example, global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), fifth generation mobile networks new radio (5G NR), BT, GNSS, WLAN, NFC, FM, and / or IR functions. GNSS may include global positioning system (GPS), global navigation satellite system (GLONASS), Beidou navigation satellite system (BDS), quasi-zenith satellite system (QZSS) and / or satellite based augmentation system (SBAS).

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

[0108] The NPU is a neural network (NN) computing processor. Drawing on the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, it rapidly processes input information and can continuously self-learn. The NPU can enable intelligent cognitive applications in electronic device 100, such as image recognition, face recognition, speech recognition, and text comprehension.

[0109] Display screen 180 is used to display images, videos, and the like. Display screen 180 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a MiniLED, a MicroLED, a Micro-OLED, or a quantum dot light-emitting diode (QLED). In some embodiments, electronic device 100 may include one or N display screens 180, where N is a positive integer greater than one.

[0110] Touch sensor 190, also known as a "touch device," can be disposed on display screen 180. The touch sensor 190 and display screen 180 form a touch screen, also known as a "touch screen." Touch sensor 190 is used to detect touch operations applied thereto or in the vicinity thereof. The touch sensor can transmit the detected touch operations to an application processor to determine the type of touch event. Visual output related to the touch operations can be provided via display screen 180. In other embodiments, touch sensor 190 can also be disposed on the surface of electronic device 100, at a location different from that of display screen 180.

[0111] The air pressure sensor 210 is used to measure air pressure. In some embodiments, the electronic device 100 calculates the altitude using the air pressure value measured by the air pressure sensor 210 to assist in positioning and navigation.

[0112] The buttons 220 include a power button, a volume button, etc. The buttons 220 may be mechanical buttons or touch buttons. The electronic device 100 may receive key inputs and generate key signal inputs related to user settings and function control of the electronic device 100.

[0113] It should be understood that the structures illustrated in the embodiments of the present application do not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device may include more or fewer components than shown, or may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0114] The following is an illustrative description of the various steps of the multi-device collaboration method provided in the embodiment of the present application.

[0115] The software system of the electronic device 100 can adopt a layered architecture, an event-driven architecture, a micro-kernel architecture, a micro-service architecture, or a cloud architecture. In the embodiment of the present invention, the Android system with a layered architecture is used as an example to illustrate the software structure of the electronic device 100.

[0116] FIG2 is a block diagram of the software structure of the electronic device 100 according to an embodiment of the present application.

[0117] A layered architecture divides software into several layers, each with distinct roles and responsibilities. Layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers: the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer.

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

[0119] As shown in FIG2 , the application package may include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, and short message.

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

[0121] As shown in FIG2 , the application framework layer may include a window manager, a content provider, a view system, a telephony manager, a resource manager, a notification manager, and the like.

[0122] 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, take screenshots, etc.

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

[0124] The view system includes visual controls, such as those for displaying text and images. The view system is used to build applications. A display interface can consist of one or more views. For example, a display interface containing a text notification icon might include a view for displaying text and a view for displaying images.

[0125] The phone manager is used to provide communication functions of the electronic device 100, such as management of call status (including answering, hanging up, etc.).

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

[0127] The Notification Manager allows applications to display notifications in the status bar. These messages can be displayed briefly and then disappear automatically without user interaction. For example, the Notification Manager is used to notify users of completed downloads and message reminders. The Notification Manager can also display notifications in the top status bar of the system as icons or scrolling text, such as notifications from background applications, or as dialog windows on the screen. Examples include displaying text messages in the status bar, emitting alert sounds, vibrating electronic devices, or flashing indicator lights.

[0128] Android Runtime includes core libraries and a virtual machine. Android Runtime is responsible for scheduling and management of the Android system.

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

[0130] The application layer and application framework layer run in a virtual machine. The virtual machine executes Java files in the application layer and application framework layer as binary files. The virtual machine manages object lifecycles, stack management, thread management, security and exception management, and garbage collection.

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

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

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

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

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

[0136] The kernel layer is the layer between hardware and software. The kernel layer includes at least display driver, camera driver, audio driver, and sensor driver.

[0137] To facilitate those skilled in the art to understand the technical solutions of the embodiments of the present application, the embodiments of the present application classify the electronic devices that may be involved in various scenarios of multi-device collaboration, including but not limited to: master devices, slave devices, and out-of-loop devices. Among them:

[0138] Master device: includes the device currently held by the user. The user can perform operations on the master device to initiate multi-device collaboration with other devices. Therefore, the master device is generally also the device that initiates multi-device collaboration. The multi-device collaboration method provided in the embodiment of the application can be implemented in the master device.

[0139] Slave devices: These devices are located near the master device and are logged into the same account as the master device. The master and slave devices are typically electronic devices manufactured by the same manufacturer. For example, the master device could be a mobile phone from Manufacturer A, and the slave device could be a tablet from Manufacturer A. The accounts used to log into the master and slave devices are the accounts that the user has applied for from the device manufacturer.

[0140] Out-of-loop devices: These include devices manufactured by the same manufacturer as the primary device but not logged into the same account as the primary device; devices manufactured by other specific manufacturers; and specific types of devices manufactured by other manufacturers, such as large-screen devices.

[0141] The multi-device collaboration method provided in the embodiments of the present application can be implemented in a master device. For example, the master device can execute each step of the multi-device collaboration method in response to one or more operations performed by a user.

[0142] FIG3 is a first flowchart of a multi-device collaboration method provided in an embodiment of the present application.

[0143] As shown in FIG3 , in one implementation, the method may include the following steps S101 to S103:

[0144] In step S101 , the master device displays a multi-device collaboration card in response to a user operation, wherein when there is at least one slave device around the master device, the multi-device collaboration card includes a device identification of the at least one slave device.

[0145] In a specific implementation, the multi-device collaboration card can be located in the control center page of the main device, in the negative one screen page of the main device, in the home screen page of the main device, or in other pages. The embodiment of the present application does not specifically limit the location of the multi-device collaboration card.

[0146] Take the multi-device collaboration card located on the control center page of the main device as an example:

[0147] The main device can display the control center page in response to the first operation performed by the user on any page. It will be understood that the present application does not limit the specific method of the first operation. For example: the first operation can be the operation of the user's finger sliding downward at the top edge of the display screen, it can be the operation of the user's finger sliding upward at the bottom edge of the display screen, or other operations. In some other embodiments, when the user's finger slides downward at the top edge of the display screen, if the user's finger slides downward at the left half of the top edge of the display screen, the notification center page will be called out, and if the user's finger slides downward at the right half of the top edge of the display screen, the control center page will be called out. These are all within the scope of protection of the embodiments of the present application.

[0148] In one implementation, in order to determine whether there are slave devices around the master device, before step S101 and / or after step S101, the master device may send a Bluetooth broadcast to the surrounding area at a preset time interval (i.e., a preset period) to search for slave devices that may be present therearound. The Bluetooth broadcast may be a classic Bluetooth broadcast or a Bluetooth Low Energy (BLE) broadcast, which is not limited in the embodiments of the present application. If there are slave devices around the master device, the slave device may send a broadcast message to the master device after receiving the Bluetooth broadcast of the master device. If the master device receives a response message from the slave device, the presence of the slave device can be determined.

[0149] It is understandable that since the master device searches for slave devices intermittently, when the master device displays the control center page in response to a user operation, the search for slave devices may have the following three situations:

[0150] In the first case, the master device has searched for one or more slave devices;

[0151] In the second case, the master device has not found the slave device and is currently searching for the slave device;

[0152] In the third case, the master device has not found any slave device and is not currently searching for a slave device.

[0153] For the above three situations, when the main device displays the control center page in response to the user operation, the content displayed in the multi-device collaboration card may be different, which is exemplified below with reference to the accompanying drawings.

[0154] FIG4A is a first schematic diagram of a control center page provided in an embodiment of the present application.

[0155] As shown in FIG4A , in one implementation, the control center page 200 may include one or more function switch buttons, such as a Wi-Fi switch button 201, a Bluetooth switch button 202, a flashlight switch button 203, a vibration switch button 204, a mute switch button 205, etc. When a user clicks a switch button, the host device may turn on or off the corresponding function.

[0156] The control center page 200 may further include one or more sliding controls, such as a sliding control 206 for adjusting the brightness of the display screen. When the user drags the slider in the sliding control 206, the main device may adjust the brightness of the display screen.

[0157] The control center page 200 may also include a multi-device collaboration card 210. The multi-device collaboration card 210 may include a card name 211 and one or more clickable elements, such as a close icon 212 for the multi-device collaboration card 210 and an entry button 213 for the multi-device collaboration homepage. The specific contents of the multi-device collaboration homepage will be described in detail below.

[0158] Among them, the name of the above card is only an example of this application. The multi-device collaboration function can also be named by other names, and this application does not limit this. For example, it can be: "Honor Internet", "Hyper Terminal", etc. Therefore, the card name 211 displayed in the multi-device collaboration card 210 can be "Honor Internet", "Hyper Terminal", etc. Correspondingly, the multi-device collaboration homepage can also be called the Honor Internet homepage or the Hyper Terminal homepage.

[0159] As further shown in FIG4A , for the first case mentioned above, if the master device has searched for one or more slave devices when displaying the control center page 200, then the master device can directly display the search results in the multi-device collaboration card 210 when displaying the control center page 200. For example, the multi-device collaboration card 210 may include the device identification 214 of one or more slave devices that the master device has searched for. The device identification 214 of the slave device may be a graphical identification, such as an icon, or other realistic elements. For example, the icon of the slave device may be used as the device identification 214 of the slave device, or a bubble-shaped element that wraps the slave device icon may be used as the device identification 214 of the slave device. This embodiment of the present application does not limit this.

[0160] By displaying the slave device's device identifier 214 in the multi-device collaboration card 210, the user can understand which slave devices are around the current master device that can perform multi-device collaboration, as well as the types of each slave device. For example, if the slave device identifier 214 is a tablet icon, the user can understand that the slave device is a tablet; if the slave device identifier 214 is a large-screen device icon, the user can understand that the slave device is a large-screen device; if the slave device identifier 214 is a mobile phone icon, the user can understand that the slave device is a mobile phone.

[0161] The multi-device collaboration card 210 may also include the device name 215 of each slave device. The device name can be displayed in conjunction with its corresponding device identifier 214. For example, the device name 215 can be displayed above, below, or in other locations above its corresponding device identifier 214. In the embodiment of the present application, the device name 215 can be the product name of the slave device, such as Honor Smart TV, Honor Pad, Honor Magic Book, etc. The device name 215 can also be a user-defined name, such as Xiao Li's Honor tablet, Honor Smart Screen in the living room, etc. This embodiment of the present application does not limit this.

[0162] FIG4B is a second schematic diagram of the control center page provided in an embodiment of the present application.

[0163] As shown in FIG4B , for the second scenario described above, if the master device has not found any slave devices when displaying the control center page 200 and is currently searching for slave devices, the master device may display a page element indicating that it is searching for slave devices in the multi-device collaboration card 210 when displaying the control center page 200. For example, the multi-device collaboration card 210 may include an animated logo with a search pattern 216, which skeuomorphically represents the state of the master device searching for slave devices.

[0164] Afterwards, if the master device searches for a slave device, the device identification and device name of the slave device can be displayed in the multi-device collaboration card 210. At this time, the multi-device collaboration card 210 will be displayed in the style shown in FIG. 4A.

[0165] It is understandable that when there are multiple slave devices around the master device, the master device may search for different slave devices one after another. In this case, the master device may display the device identification and device name of each slave device it searches for in the multi-device collaboration card 210. When multiple slave devices are searched for one after another, the device identifications of the multiple slave devices may be arranged in the order in which they were searched. In addition, when the master device searches for a slave device, if it searches for a certain slave device, it may not display the device identification and device name of the slave device immediately, but wait until the search ends (for example, the search times out) before displaying the device identifications and device names of all the slave devices it searches for in the multi-device collaboration card 210.

[0166] FIG4C is a third schematic diagram of the control center page provided in an embodiment of the present application.

[0167] As shown in FIG4C , for the third scenario described above, if the master device does not search for a slave device when displaying the control center page 200 and is not currently searching for a slave device, the master device may display page elements in the multi-device collaboration card 210 when displaying the control center page 200 to guide the user to actively search for a slave device. For example, the multi-device collaboration card 210 may include a search button 217 and a prompt 218 to guide the user to click the search button 217 to actively search for a slave device.

[0168] When the master device detects that the user clicks the search button 11, it can start searching for slave devices in response to the user's click operation, such as sending a Bluetooth broadcast to the surrounding area and listening for response messages from the slave devices to the Bluetooth broadcast. After the master device starts searching for slave devices, the multi-device collaboration card 210 can be changed to the style of Figure 4B.

[0169] Afterwards, if the master device searches for a slave device, the device identification and device name of the slave device can be displayed in the multi-device collaboration card 210. At this time, the multi-device collaboration card 210 will be displayed in the style shown in FIG. 4A.

[0170] FIG4D is a fourth schematic diagram of the control center page provided in an embodiment of the present application.

[0171] As shown in page (a) of FIG4D , in one implementation, if the master device does not search for a slave device when displaying the control center page 200, and the master device is currently displaying the control center page 200 for the first time, then the master device may not display the multi-device collaboration card 210 when initially displaying the control center page 200. The first time the master device displays the control center page 200 includes, but is not limited to, the following scenarios:

[0172] Scenario 1: After the operating system of the master device is initialized, the control center page 200 is displayed for the first time. For example, the master device is a brand new device. After the master device is powered on for the first time, the user initializes the master device. After the initialization is complete, the user operates the master device to display the control center page 200 for the first time.

[0173] Scenario 2: The primary device displays the control center page 200 for the first time after the logged-in account changes. For example, user A logs out of the primary device and gives the primary device to user B. User B then logs in to a new account on the primary device. After logging in with the new account, user B operates the primary device to display the control center page 200 for the first time.

[0174] Scenario 3: The primary device displays the control center page 200 for the first time after restoring factory settings or clearing data.

[0175] As shown in page (a) of Figure 4D, in one implementation, when the control center page 200 does not include the multi-device collaboration card 210, it may include one or more function switch buttons, such as a Wi-Fi switch button 201, a Bluetooth switch button 202, a flashlight switch button 203, a vibration switch button 204, a mute switch button 205, etc. When the user clicks a switch button, the host device can turn the corresponding function on or off. The control center page 200 may also include one or more sliding controls, such as a sliding control 206 for adjusting the display brightness.

[0176] As shown in page (a) of Figure 4D, in one implementation, if the master device does not search for a slave device thereafter, it means that the user's current environment may not have the conditions for multi-device collaboration, and the user may not be a potential user of multi-device collaboration. Therefore, the master device can continue not to display the multi-device collaboration card 210, so that cards that the user does not need will not appear in the control center page 200, thereby avoiding disturbing the user.

[0177] As shown in page (b) of Figure 4D, in one implementation, if the master device subsequently searches for a slave device, it means that the user's current environment has the conditions for multi-device collaboration, and the user may be a potential user of multi-device collaboration. Therefore, the master device can display a multi-device collaboration card 210 in the control center page 200. The multi-device collaboration card 210 may include a card name 211, and one or more clickable elements, such as: a close icon 212 of the multi-device collaboration card 210, and an entry button 213 of the multi-device collaboration main page.

[0178] If the master device displays the multi-device collaboration card 210 in the control center page 200 for the first time, the master device can directly display the multi-device collaboration card 210 the next time it displays the control center page 200. According to the three states of the master device searching for the slave device, the multi-device collaboration card 210 can be one of the styles in Figures 4A-4C.

[0179] As shown in FIG4D , in one implementation, the master device may also close the multi-device collaboration card 210 in response to a user clicking the close icon 212 in the multi-device collaboration card 210. If the user closes the multi-device collaboration card 210, the master device may not display the multi-device collaboration card 210 the next time it displays the control center page 200. Alternatively, the master device may determine whether the number of times the user has closed the multi-device collaboration card 210 consecutively within a preset time period is greater than or equal to a first threshold. If the number of times the user has closed the multi-device collaboration card 210 consecutively within a preset time period is greater than or equal to the first threshold, the master device may not display the multi-device collaboration card 210 the next time it displays the control center page 200. If the number of times the user has closed the multi-device collaboration card 210 consecutively within a preset time period is greater than or equal to the first threshold, the master device may not display the multi-device collaboration card 210 the next time it displays the control center page 200. If the number of times the user has closed the multi-device collaboration card 210 consecutively within a preset time period is less than the first threshold, the master device may continue to display the multi-device collaboration card 210 the next time it displays the control center page 200. For example, if the preset time period is 24 hours (one day) and the first threshold is two times, if the user closes the multi-device collaboration card 210 twice within 24 hours, the master device may not display the multi-device collaboration card 210 the next time it displays the control center page 200.

[0180] In one implementation, the control center page 200 may also include an edit icon 207. If the user wishes to restore the display of the multi-device collaboration card 210, the user may click the edit icon 207 in the control center. In response to the user clicking the edit icon 207, the primary device may access the edit page of the control center. In this way, the user can configure the content displayed in the control center on the edit page, for example, restoring the display of the multi-device collaboration card 210.

[0181] In one implementation, after the multi-device collaboration card 210 is closed, if the user closes the control center and then reopens the control center by swiping down from the top edge of the display screen, the master device may restore the multi-device collaboration card 210 if it detects a slave device nearby. If the master device does not find any slave devices, the multi-device collaboration card 210 may remain closed.

[0182] In step S102 , the master device determines a target device from the at least one slave device in response to a user operation in the multi-device collaboration card 210 , and initiates multi-device collaboration to the target device based on a first collaboration type.

[0183] FIG5 is a first set of interaction example diagrams of a multi-device collaboration method provided in an embodiment of the present application.

[0184] As shown in FIG5 , if a user wishes to establish multi-device collaboration between the master device and a searched slave device, the user can perform one or more preset operations on the device identifier of the slave device in the multi-device collaboration card 210, for example, clicking the device identifier 214 of the slave device 12. In response to the user clicking the device identifier 214 of the slave device 12, the master device can identify the slave device as the target device and initiate multi-device collaboration with the target device based on the first collaboration type.

[0185] If only one collaboration type is supported between the master device and the target device, then the collaboration type is the first collaboration type. If multiple collaboration types are supported between the master device and the target device, the first collaboration type may be one of the collaboration types supported between the master device and the target device.

[0186] In one possible implementation, in a scenario where multiple collaboration types are supported between the master device and the target device: if this is the first time that the master device and the target device establish multi-device collaboration, then the first collaboration type may be the default collaboration type between the two devices; if this is not the first time that the master device and the target device establish multi-device collaboration, then the first collaboration type may be the collaboration type adopted by both parties the last time they established multi-device collaboration, or it may be the default collaboration type between the two devices.

[0187] Generally speaking, a default collaboration type can be pre-set between the main device and each type of electronic device, and the default collaboration type between the main device and different types of electronic devices can be different. For example: if the main device is a mobile phone and the target device is a tablet, then the default collaboration type can be multi-screen collaboration; if the main device is a mobile phone and the target device is a large-screen device, then the default collaboration type can be screen projection; if the main device is a PC and the target device is a PC, then the default collaboration type can be screen mirroring. The main device can pre-store the default collaboration type with each type of electronic device, for example: it can be stored locally on the main device or in the cloud.

[0188] Step S103: After the master device establishes multi-device collaboration with the target device, the master device switches the device identifier of the target device to a collaboration identifier of the first collaboration type.

[0189] As shown in FIG5 , the collaboration identifier 219 is similar to the device identifier 214 and can also be a graphical identifier, such as an icon or other skeuomorphic elements. For example, if the master device and the target device have established multi-screen collaboration, the master device can switch the target device's device identifier to a multi-screen collaboration identifier; if the master device and the target device have established screen mirroring, the master device can switch the target device's device identifier to a screen mirroring identifier. In this way, the user can intuitively understand the type of collaboration established between the master device and the target device in the multi-device collaboration card 210.

[0190] In one implementation, after the master device establishes a multi-device collaboration with the target device, the master device may further display a type name 221 of the first collaboration type in the multi-device collaboration card 210. The type name 221 of the first collaboration type may be displayed together with the device name 215 of the target device. For example, the type name 221 of the first collaboration type may be displayed adjacent to the device name 215 of the target device in the same row, or the type name 221 of the first collaboration type may be displayed adjacent to the device name 215 of the target device in the same column.

[0191] As shown in Figure 5, taking the target device as a Honor Notebook and the first collaboration type as multi-screen collaboration as an example, after the primary device establishes multi-screen collaboration with the Honor Notebook, the primary device can switch the Honor Notebook's device identifier in the multi-device collaboration card 210 to a multi-screen collaboration identifier and add the type name "Multi-screen collaboration" below the device name "Honor Notebook." In this way, the user can intuitively understand in the multi-device collaboration card 210 that the primary device has established multi-screen collaboration with the Honor Pad.

[0192] In one implementation, the master device may display the device identifier 214 of each slave device in a preset color, such as a first color, in the multi-device collaboration card 210. If the master device and the target device have established multi-device collaboration based on the first collaboration type, the master device may display the collaboration identifier 219 of the first collaboration type in another preset color, such as a second color, in the multi-device collaboration card 210. This allows the user to distinguish which slave devices have established multi-device collaboration with the master device and which have not established multi-screen collaboration with the master device by using different colors.

[0193] As shown in Figure 5, in one implementation, after establishing multi-device collaboration with a target device, the master device can disconnect the multi-device collaboration with the target device in response to a user clicking on the first collaboration type collaboration identifier 219. After disconnecting the multi-device collaboration with the target device, the master device can switch the first collaboration type collaboration identifier 219 back to the target device identifier. This restores the multi-device collaboration card 210 to its original appearance before establishing the multi-device collaboration.

[0194] The method provided in the embodiment of the present application adds a multi-device collaboration card to the control center page of the master device. The multi-device collaboration card contains the device identifications of each slave device around the master device. In this way, the user can establish multi-device collaboration between the master device and any slave device by clicking the device identification of any slave device. The user does not need to search for control entrances of various collaboration types in different user interfaces, thereby improving the user experience.

[0195] In some embodiments, the master device may also display a multi-device collaboration homepage in response to a user's operation on a multi-device collaboration card. The content contained in the multi-device collaboration homepage may differ depending on whether the master device has established multi-device collaboration with the target device or whether the master device has not established multi-device collaboration with the target device. This is exemplified below with reference to the accompanying figures.

[0196] FIG6 is a second set of interaction example diagrams of a multi-device collaboration method provided in an embodiment of the present application.

[0197] As shown in FIG6 , if the master device and the target device have not established multi-device collaboration, if the user wants to open the multi-device collaboration main page 300, the user can perform a long press 14 operation on the device identifier 214 of any slave device in the multi-device collaboration card 210. The master device can display the multi-device collaboration main page 300 in response to the user performing a long press 14 operation on the device identifier 214 of any slave device.

[0198] As shown in FIG6 , if the master device and the target device have not established multi-device collaboration, if the user wants to open the multi-device collaboration main page 300, they can also click the entry button 213 in the multi-device collaboration card 210. In response to the user clicking the entry button 213, the master device can display the multi-device collaboration main page 300.

[0199] As shown in Figure 6, in the case where the master device and the target device have not established multi-device collaboration, the multi-device collaboration main page 300 may include the master device's device identifier 301 and the device identifiers 214 of each slave device. The master device's device identifier 301 may be located in the center area of ​​the multi-device collaboration main page 300, for example, in the center, below the center, or above the center of the multi-device collaboration main page 300, although this is not a limitation in this application. The slave device identifiers 214 may be distributed around the master device's device identifier 301.

[0200] In one implementation, the device identifier 301 of the master device is located in the lower center area of ​​the multi-device collaboration homepage 300. The device identifiers 214 of each slave device, such as the device identifier of a tablet computer, the device identifier of a large-screen device, the device identifier of a PC, and the device identifier of a mobile phone, can be distributed in a planetary pattern around the device identifier 301 of the master device. In addition, the device identifiers 214 of the slave devices can also be distributed above the device identifier 301 of the master device, or distributed above the device identifier 301 of the master device, etc., and this implementation is not limited to this.

[0201] In one implementation, the device identification in the multi-device collaboration main page 300 and the device identification in the multi-device collaboration card 210 can adopt different visual styles. For example: the device identification in the multi-device collaboration card 210 can be composed of a device icon and a background color, while the device identification in the multi-device collaboration main page 300 can be a bubble element that wraps the device icon, or a bubble element that wraps the device icon, etc. In addition, in the multi-device collaboration main page 300, the device identification 301 of the master device and the device identification 214 of the slave device can be different colors to facilitate user distinction. For example: the device identification 301 of the master device can be a blue bubble element, and the device identification 214 of the slave device can be a white (or transparent) bubble element. In addition, in the multi-device collaboration main page 300, the device identification 301 of the master device and the device identification 214 of the slave device can be different sizes to facilitate user distinction. For example: the size of the device identification 301 of the master device can be larger than the size of the device identification 214 of the slave device.

[0202] In one implementation, the multi-device collaboration main page 300 may further include the device name 215 of each slave device. The device name 215 may be displayed in conjunction with its corresponding device identifier 214. For example, the device name may be displayed above, below, or in other locations above its corresponding device identifier 214. In the embodiment of the present application, the device name 215 may be the product name of the slave device, such as Honor Smart TV, Honor Pad, Honor Magic Book, etc. The device name 215 may also be a user-defined name, such as Xiao Li's Honor tablet, Honor Smart Screen in the living room, etc. This embodiment of the present application does not limit this.

[0203] FIG7 is a third set of interaction example diagrams of a multi-device collaboration method provided in an embodiment of the present application.

[0204] As shown in FIG7 , if a master device and a target device have established multi-device collaboration, if a user wishes to open the multi-device collaboration main page 300, the user may perform a long press 14 on the device identifier 214 of any slave device in the multi-device collaboration card 210. The master device may display the multi-device collaboration main page 300 in response to the user performing a long press 14 on the device identifier 214 of any slave device.

[0205] As shown in FIG7 , if a master device and a target device have established multi-device collaboration, if the user wishes to open the multi-device collaboration main page 300, they can also perform a long press 15 on the collaboration identifier 219 of any collaboration type in the multi-device collaboration card 210. The master device can display the multi-device collaboration main page 300 in response to the user's long press 15 on the collaboration identifier 219 of any collaboration type.

[0206] As shown in FIG7 , if a master device and a target device have established multi-device collaboration, if the user wishes to open the multi-device collaboration homepage 300, the user may click the entry button 213 in the multi-device collaboration card 210. In response to the user clicking the entry button 213, the master device may display the multi-device collaboration homepage 300.

[0207] As shown in Figure 7, for the situation where the master device and the target device have established multi-device collaboration, the entry button multi-device collaboration main page 300 may include a collaboration identifier 219 between the master device and the target device and a device identifier 214 of each slave device. Among them, the collaboration identifier 219 can be located in the central area of ​​the multi-device collaboration main page 300, for example: in the center, the lower center area, the upper center area, etc. of the multi-device collaboration main page 300, and the implementation of this application does not limit this. The device identifier 214 of the slave device can be distributed on the periphery of the collaboration identifier. The adjacent position above or below the collaboration identifier 219 can also include the device name 215 of the target device and the type name 402 of the collaboration type.

[0208] In one implementation, the collaboration logo 219 may be located in the lower center of the multi-device collaboration home page 300. The device logos 214 of the slave devices, such as the device logo of a tablet computer, the device logo of a large-screen device, the device logo of a PC, and the device logo of a mobile phone, may be distributed around the collaboration logo in a planetary pattern.

[0209] In one implementation, the collaboration identifier 219 and the slave device identifier 214 can be different colors to facilitate user differentiation. For example, the collaboration identifier 219 can be a blue bubble element, and the slave device identifier 214 can be a white (or transparent) bubble element. In addition, in the multi-device collaboration homepage 300, the collaboration identifier 219 and the slave device identifier 214 can be different sizes to facilitate user differentiation. For example, the collaboration identifier 219 can be larger than the slave device identifier 214.

[0210] FIG8 is a second flow chart of a multi-device collaboration method provided in an embodiment of the present application.

[0211] Figures 9A-9D are the fourth set of interaction example diagrams of a multi-device collaboration method provided in an embodiment of the present application.

[0212] As shown in FIG8 , in one implementation, the method may include the following steps S201-S203:

[0213] In step S201 , the master device determines a target device in response to an operation performed by a user on a multi-device collaboration main page, and establishes multi-device collaboration with the target device based on a first collaboration type.

[0214] In a specific implementation, as shown in FIG9A , if the master device has not established multi-device collaboration with a slave device, and the user wants to establish multi-device collaboration with the master device, the user can drag 21 the device identifier 214 of the slave device toward the device identifier 301 of the master device on the multi-device collaboration main page 300. In response to the user's dragging operation 211 of the device identifier 214 of the slave device, the master device can determine the slave device as the target device.

[0215] When the user drags the target device's device identifier 214 into contact with the master device's device identifier 301, the master device initiates multi-device collaboration with the target device based on the first collaboration type. Simultaneously, as shown in FIG9B , the master device may display a merging effect of the master device's bubble element and the target device's bubble element on the multi-device collaboration homepage 300, visually conveying the establishment of multi-device collaboration to the user.

[0216] When the master device successfully establishes multi-device collaboration with the target device, as shown in FIG9C , the master device's device identifier 301 on the multi-device collaboration homepage 300 can be switched to a collaboration identifier 401 of the first collaboration type. For example, the master device's bubble element can be merged with the target device's bubble element to form a bubble element of the first collaboration type. Furthermore, the master device can display the target device's device name 215 and the first collaboration type's type name 402 adjacent to or above or below the first collaboration type's collaboration identifier 401.

[0217] Among them: If only one collaboration type is supported between the master device and the target device, then the collaboration type is the first collaboration type. If multiple collaboration types are supported between the master device and the target device, the first collaboration type can be one of the collaboration types supported between the master device and the target device. For example, if the master device and the target device are establishing multi-device collaboration for the first time, then the first collaboration type can be the default collaboration type between the two devices. If this is not the first time that the master device and the target device are establishing multi-device collaboration, then the first collaboration type can be the collaboration type used by both parties the last time they established multi-device collaboration, or it can be the default collaboration type between the two devices.

[0218] In step S202, the master device displays a type switching card on the multi-device collaboration main page.

[0219] Among them, the type switching card 310 can be displayed in an adjacent position such as above or below the collaboration logo 401 of the first collaboration type, and this embodiment of the present application does not limit this.

[0220] It should be noted that in an embodiment of the present application, if the master device establishes multi-device collaboration with the target device based on the first collaboration type, the master device can directly display the type switching card on the multi-device collaboration main page without requiring the user to perform any further operations. For example, the master device can display the type switching card at the same time as successfully establishing multi-device collaboration with the target device; alternatively, the master device can display the type switching card immediately after successfully establishing multi-device collaboration with the target device.

[0221] As shown in FIG9C , the type switching card 310 may include collaboration identifiers for one or more collaboration types supported by the master device and the target device. The master device may display the collaboration identifiers for each collaboration type supported by the master device and the target device in the type switching card 310, or may display the collaboration identifiers for some of the collaboration types supported by the master device and the target device in the type switching card 310, for example, displaying only the collaboration identifier 403 for other collaboration types other than the collaboration identifier 401 for the first collaboration type. This embodiment of the present application is not limited to this.

[0222] As shown in Figure 9C, taking the mobile phone as the main device and the PC as the target device as an example, the collaboration types supported by the mobile phone and PC may include multi-screen collaboration and super keyboard and mouse. Then, after the mobile phone and PC establish multi-screen collaboration, the type switching card 310 may include a multi-screen collaboration identifier and a super keyboard and mouse identifier.

[0223] In one implementation, if the type switching card 310 includes both the collaboration identifier 401 of the first collaboration type and the collaboration identifier 403 of other collaboration types, then the collaboration identifier 401 of the first collaboration type and the collaboration identifier 403 of other collaboration types can be displayed in different colors to facilitate user distinction.

[0224] In one implementation, the type switching card 310 may also include a disconnect button 311. If the user wants to disconnect the multi-device collaboration between the main device and the target device, the user may click 23 the disconnect button 311. In response to the user clicking 23 the disconnect button 311, the main device may disconnect the multi-device collaboration with the target device, restore the collaboration identifier of the first collaboration type to the device identifier 301 of the main device, and restore the device identifier 214 of the target device to its original position. For example, the main device may differentiate the bubble element of the first collaboration type into the bubble element of the main device and the bubble element of the target device, and then move the bubble element of the target device to its original position, thereby restoring the multi-device collaboration main page 300 to the state shown in FIG9A .

[0225] It should be noted here that when only one collaboration type is supported between the main device and the target device, the type switching card 310 may include the type identifier of the supported collaboration type and the disconnect button 311, or it may only include the disconnect button 311. This embodiment of the present application does not limit this.

[0226] Step S203: The master device determines the second collaboration type in response to the user's operation on the type switching card, and switches the collaboration type between the master device and the target device from the first collaboration type to the second collaboration type.

[0227] The second collaboration type may be one of the multiple collaboration types included in the type switching card 310 .

[0228] In a specific implementation, as shown in FIG9C , if the user wants to switch the collaboration type between the master device and the target device from the first collaboration type to another collaboration type, the user can click on the collaboration identifier 403 of any collaboration type in the type switching card 310. In response to the user clicking on the collaboration identifier 403 of any collaboration type, the master device can determine the collaboration type as the second collaboration type and switch the collaboration type between the master device and the target device from the first collaboration type to the second collaboration type.

[0229] In a specific implementation, the master device can directly initiate a switching request to the target device based on the second collaboration type without disconnecting the multi-device collaboration with the target device, so that the master device and the target device switch to the second collaboration type. Furthermore, as shown in FIG9D , after the master device and the target device establish multi-device collaboration based on the second collaboration type, the collaboration identifier 401 of the first collaboration type in the multi-device collaboration main page 300 can be switched to the collaboration identifier 403 of the second collaboration type. In addition, the master device can also first disconnect the multi-device collaboration with the target device, and then, based on the second collaboration type, initiate multi-device collaboration to the target device again, so that the master device and the target device can re-establish multi-device collaboration based on the second collaboration type.

[0230] In one implementation, after displaying the type switching card 310, if the master device detects that the user has not performed any operation on the type switching card 310 within a preset period of time, the type switching card 310 may be closed. The preset period of time may be 3 seconds, 5 seconds, etc., and is not limited in this embodiment of the present application.

[0231] After the main device closes the type switching card 310, if the user wants the main device to redisplay the type switching card 310, the user can click the collaboration logo 401 of the first collaboration type (or the second collaboration type) in the multi-device collaboration main page 300. The main device can redisplay the type switching card 310 in response to the user's click operation.

[0232] According to the method provided in the embodiment of the present application, when the main device and the target device support multiple collaboration types, the main device and the target device can first establish multi-device collaboration based on the preset collaboration type. Then, the user can select the collaboration type that the user wants to use in the control center of the main device. The main device can switch from the preset collaboration type to the collaboration type that the user wants to use based on the user's selection, thereby improving the user experience.

[0233] Figures 10A-10D are the fifth set of interaction example diagrams of a multi-device collaboration method provided in an embodiment of the present application. Below, with reference to Figures 10A-10D, taking a tablet as the master device and a PC as the slave device, the interaction scenarios corresponding to steps S201-S203 of the multi-device collaboration method provided in an embodiment of the present application are exemplarily described.

[0234] As shown in FIG10A , if a user wants to establish multi-device collaboration between a tablet and a PC, they can drag 27 the PC bubble element 431 toward the tablet bubble element 432 on the multi-device collaboration main page 300. When the user drags the PC bubble element 431 until it contacts the tablet bubble element 432, the tablet initiates a default type of multi-device collaboration with the PC, such as screen mirroring. At the same time, as shown in FIG10B , the tablet can display an effect on the multi-device collaboration main page 300 of its bubble element 432 merging with the PC bubble element 431, visually providing the user with feedback on the establishment of multi-device collaboration.

[0235] As shown in FIG10C , when the tablet computer and the PC successfully establish screen mirroring, the bubble element 432 of the tablet computer and the bubble element 431 of the PC can be merged to form a screen mirroring bubble element 433 , and a type switching card 310 is displayed below the screen mirroring bubble element 433 .

[0236] The type switching card 310 may include one or more collaboration identifiers of collaboration types supported by the tablet computer and the PC, such as a screen mirroring identifier 461 , a screen extension identifier 462 , and a super key and mouse identifier 463 .

[0237] If the user wants to switch the collaboration type between the tablet computer and the PC, for example, to switch the collaboration type between the tablet computer and the PC from screen mirroring to super keyboard and mouse, the user can click 28 super keyboard and mouse identifier 463 in the type switching card 310. The tablet computer can respond to the user operation and switch the collaboration type between the tablet computer and the PC from screen mirroring to super keyboard and mouse.

[0238] As shown in FIG10D , after the tablet computer establishes a super keyboard and mouse with the PC, the bubble element 433 of the screen mirroring in the multi-device collaboration main page 300 can be switched to a bubble element 434 of the super keyboard and mouse.

[0239] Figures 11A-11D are the sixth set of interaction example diagrams of a multi-device collaboration method provided in an embodiment of the present application.

[0240] 11A-11D , taking the master device as a PC and the slave device as a tablet as an example, the interaction scenarios corresponding to steps S201-S203 of the multi-device collaboration method provided in an embodiment of the present application are exemplarily described.

[0241] As shown in FIG11A , if a user wants to establish multi-device collaboration between a PC and a tablet, they can drag the tablet's bubble element 441 toward the PC's bubble element 442 on the multi-device collaboration main page 300 using the mouse. When the user drags the tablet's bubble element 441 until it contacts the PC's bubble element 442, the PC initiates a default type of multi-device collaboration, such as screen mirroring, with the tablet. At the same time, as shown in FIG11B , the PC can present an effect on the multi-device collaboration main page 300 of its bubble element 442 merging with the tablet's bubble element 441, visually providing feedback to the user on the status of establishing multi-device collaboration.

[0242] As shown in FIG11C , when the PC and the tablet successfully establish screen mirroring, the bubble element 442 of the PC and the bubble element 441 of the tablet can be merged to form a screen mirroring bubble element 443 , and a type switching card 310 is displayed below the multi-screen collaboration logo 401 .

[0243] The type switching card 310 may include one or more collaboration identifiers of collaboration types supported by the PC and the tablet computer, such as a screen mirroring identifier 461 , a screen extension identifier 462 , and a super key and mouse identifier 463 .

[0244] If the user wants to switch the collaboration type between the PC and the tablet, for example, to switch the collaboration type between the PC and the tablet from multi-screen collaboration to super keyboard and mouse, the user can click 31 super keyboard and mouse identifier 463 in the type switching card 310. The master device can respond to the user operation and switch the collaboration type between the PC and the tablet from screen mirroring to super keyboard and mouse.

[0245] As shown in FIG11D , after the PC and the tablet computer establish a super keyboard and mouse, the bubble element 443 of the screen mirroring in the multi-device collaboration main page 300 can be switched to the bubble element 444 of the super keyboard and mouse.

[0246] Figures 12A-12D are the seventh set of interaction example diagrams of a multi-device collaboration method provided in an embodiment of the present application.

[0247] The following takes the case where the master device is a foldable screen mobile phone and the slave device is a PC as an example to exemplify the interaction scenarios corresponding to steps S201-S203 of the multi-device collaboration method provided in the embodiment of the present application. It should be noted here that foldable screen mobile phones can usually work in two forms, one is the body folding state, and the other is the body unfolding state. Among them, when the foldable screen mobile phone is in the body folding state, it is equivalent to a traditional form of mobile phone, and the type of collaboration supported between it and the PC is the same as that of a traditional form of mobile phone, for example, it may include: multi-screen collaboration and super keyboard and mouse; when the foldable screen mobile phone is in the body unfolding state, it is a new product form relative to the traditional form of mobile phone, and the type of collaboration supported between it and the PC is different from that of a traditional form of mobile phone, for example, it may include: multi-screen collaboration, screen mirroring, screen extension, super keyboard and mouse.

[0248] 12A to 12D , an example explanation will be given below using the interaction scenario when the foldable screen mobile phone is in the unfolded state.

[0249] As shown in Figure 12A, if the user wants to establish multi-device collaboration between a foldable screen mobile phone and a PC, the user can drag 32 the bubble element 451 of the PC toward the bubble element 452 of the foldable screen mobile phone in the multi-device collaboration main page 300. When the user drags the bubble element 451 of the PC to contact the bubble element 452 of the foldable screen mobile phone, the foldable screen mobile phone initiates the default type of multi-device collaboration to the PC, for example: multi-screen collaboration. At the same time, as shown in Figure 12B, the foldable screen mobile phone can present the effect of its bubble element 452 and the bubble element 451 of the PC being merged in the multi-device collaboration main page 300, so as to visually feedback the status of establishing multi-device collaboration to the user.

[0250] As shown in Figure 12C, when the foldable screen mobile phone and the PC successfully establish multi-screen collaboration, the bubble element 452 of the foldable screen mobile phone and the bubble element 451 of the PC can be merged to form a multi-screen collaboration bubble element 453, and the type switching card 310 can be displayed below the multi-screen collaboration logo 401.

[0251] Among them, the type switching card 310 may include one or more collaborative types of collaboration identifiers supported by the foldable screen mobile phone and the PC, such as: screen mirroring identifier 461, screen extension identifier 462, super key and mouse identifier 463, and multi-screen collaboration identifier 464.

[0252] If the user wants to switch the collaboration type between the foldable screen phone and the PC, for example, to switch the collaboration type between the foldable screen phone and the PC from multi-screen collaboration to super keyboard and mouse, the user can click 33 Super Keyboard and Mouse 463 in the type switching card 310. The host device can respond to the user operation and switch the collaboration type between the foldable screen phone and the PC from multi-screen collaboration to super keyboard and mouse.

[0253] As shown in FIG12D , after the foldable screen mobile phone establishes a super keyboard and mouse with the PC, the bubble element 453 of the multi-screen collaboration in the multi-device collaboration main page 300 can be switched to the bubble element 454 of the super keyboard and mouse.

[0254] 13A-13C are example diagrams of how to start and stop the automatic collaborative service according to an embodiment of the present application.

[0255] As shown in Figures 13A and 13B, in one implementation, the multi-device collaboration main page 300 may also include a setting button 302, which can be set at any position of the multi-device collaboration main page 300, such as the upper right corner of the multi-device collaboration main page 300.

[0256] Taking a mobile phone as the master device as an example, if the user wants to set up multi-device collaboration, the user can click 24 setting button 302. In response to the user's click 24 operation, the mobile phone can enter the multi-device collaboration setting page 400, which can include, for example, a collaborative service list 410 and a slave device list 420.

[0257] The collaborative service list 410 may include one or more configurable collaborative service options, such as Super Connection, Super Call, Super Notification, and Super Keyboard and Mouse, as well as the status of each collaborative service, such as Enabled or Disabled. The slave device list may include the names and types of nearby slave devices that the mobile phone has searched for, as well as the names and types of devices that have previously established multiple device collaborations with the mobile phone.

[0258] As shown in Figures 13B and 13C , if the user wants to set the status of a collaborative service, they can click 25 on the collaborative service option in the collaborative service list 410. In response to the user's click 25 , the mobile phone will enter a subpage 500 for the collaborative service, which may include, for example, a toggle button 501 for the collaborative service. The user can then click 26 on the toggle button 501 to turn the collaborative service on or off.

[0259] For example, when a user clicks 25 "Super Call" in collaborative service list 410, the mobile phone may enter a Super Call subpage 500, which may include Super Call function description information 502 and a Super Call switch button 501. When switch button 501 is on, if the user clicks 26 switch button 501, the Super Call service can be turned off. When switch button 501 is off, if the user clicks 26 switch button 501, the Super Call service can be turned on.

[0260] According to the method provided in the embodiment of the present application, the user can directly enter the multi-device collaboration setting page from the multi-device collaboration main page to control the turning on and off of the automatic collaboration service, thereby improving the user experience.

[0261] In a multi-device collaboration scenario, the master device may be in the following three states at a given time:

[0262] State A: The master device has not established multi-device collaboration with other devices (abbreviated as: master device not collaborative);

[0263] State B: The master device and the slave device are performing multi-device collaboration;

[0264] State C: The master device and devices outside the ring are performing multi-device collaboration.

[0265] Among them, state B and state C can be simply referred to as: the master device is not cooperating.

[0266] In a multi-device collaboration scenario, a slave device may be in the following three states at a given time:

[0267] State a: The slave device has not established multi-device collaboration with other devices (abbreviated as: slave device not cooperating);

[0268] State b: The slave device is performing multi-device collaboration with other slave devices;

[0269] State c: The slave device is performing multi-device collaboration with devices outside the ring.

[0270] Among them, state b and state c can be simply referred to as: the slave device is not cooperating.

[0271] Based on the above states, when establishing multi-device collaboration between the master device and the target device, the following four scenarios and eight sub-scenarios may occur:

[0272] Scenario 1: The master device and the target device are not coordinated.

[0273] Scenario 2: The master device cooperates, but the target device does not. Scenario 2 can include the following two sub-scenarios:

[0274] Sub-scenario 1: The master device and other slave devices are performing multi-device collaboration;

[0275] Sub-scenario 2: The master device and an out-of-loop device are performing multi-device collaboration.

[0276] Scenario 3: The master device does not cooperate, but the target device cooperates. Scenario 3 can include the following two sub-scenarios:

[0277] Sub-scenario 3: The target device and other slave devices are performing multi-device collaboration;

[0278] Sub-scenario 4: The target device and an out-of-loop device are performing multi-device collaboration;

[0279] Scenario 4: Master device collaboration and slave device collaboration. Scenario 4 can include the following four sub-scenarios:

[0280] Sub-scenario 5: The master device and other slave devices are performing multi-device collaboration, and the target device and other slave devices are performing multi-device collaboration;

[0281] Sub-scenario 6: The master device and other slave devices are performing multi-device collaboration, and the target device and an out-of-loop device are performing multi-device collaboration;

[0282] Sub-scenario 7: The master device is performing multi-device collaboration with an out-of-ring device, and the target device is performing multi-device collaboration with other slave devices.

[0283] Sub-scenario 8: The master device is performing multi-device collaboration with an out-of-loop device, and the target device is performing multi-device collaboration with an out-of-loop device.

[0284] For different scenarios and sub-scenarios, when a user drags the target device's device identifier so that it touches the primary device's device identifier, the primary and target devices can respond differently. This is explained in detail below with some examples.

[0285] For scenario one, the multi-device collaboration method may include the following steps: the main device responds to the user dragging the device identifier of the target device so that the device identifier of the target device contacts the device identifier of the main device, establishes multi-device collaboration with the target device based on the first collaboration type, and displays the type switching card 310 in the multi-device collaboration main page 300.

[0286] This step may also refer to the above steps S201 and S202 for details.

[0287] FIG14 is an example diagram of interaction of scenario 1 of the multi-device collaboration method provided in an embodiment of the present application.

[0288] As shown in FIG14 , a case where the main device is a mobile phone, the target device is a PC (for example, a Honor notebook), and the first collaboration type is multi-screen collaboration is taken as an example.

[0289] If the user wants to establish multi-device collaboration between the mobile phone and the PC, the bubble element 601 of the PC can be dragged 61 toward the bubble element 602 of the mobile phone in the multi-device collaboration main page. When the user drags 61 the bubble element 601 of the PC until it contacts the bubble element 602 of the mobile phone, and then lifts his finger, the mobile phone initiates multi-screen collaboration to the PC. At the same time, the mobile phone can present the effect of the bubble element 602 of the mobile phone and the bubble element 601 of the PC in a fused state in the multi-device collaboration main page, so as to visually feedback the status of establishing multi-device collaboration to the user. When the mobile phone and the PC successfully establish multi-screen collaboration, the bubble element 602 of the mobile phone is completely integrated with the bubble element 601 of the PC to form a bubble element 603 for multi-screen collaboration. The mobile phone can also display the device name of the PC "Honor Smart Screen" and the collaboration type "Multi-screen Collaboration" above the bubble element 603 of multi-screen collaboration (or other nearby positions). The mobile phone can also display a type switching card 310 below the multi-screen collaborative bubble element 603 (or other nearby positions). For the specific implementation of the type switching card 310, please refer to the content recorded in Figure 9C above, which will not be repeated here.

[0290] For sub-scenario 1 of scenario 2, two situations can be included. The first situation is that the multi-device collaboration being performed by the master device and other slave devices does not support the simultaneous access of three devices, for example, the multi-device collaboration being performed by the master device and other slave devices is a collaboration type other than the super keyboard and mouse; the second situation is that the multi-device collaboration being performed by the master device and other slave devices supports the simultaneous access of three devices, for example: super keyboard and mouse. For the convenience of description below, the collaboration type that does not support the simultaneous access of three devices will be referred to as the third collaboration type, and the multi-device collaboration established based on the third collaboration type will be referred to as the first multi-device collaboration; the collaboration type that supports the simultaneous access of three devices will be referred to as the fourth collaboration type, and the multi-device collaboration established based on the fourth collaboration type will be referred to as the second multi-device collaboration.

[0291] For the first case, the multi-device collaboration method may include the following steps: while the master device and the first slave device are establishing a first multi-device collaboration, in response to a user dragging a device identifier of a target device so that the device identifier of the target device contacts a collaboration identifier of a third collaboration type, displaying a switch inquiry card. The switch inquiry card is used to inquire the user whether to switch collaborative devices.

[0292] FIG15 is a first interaction example diagram of sub-scenario 1 of a multi-device collaboration method provided in an embodiment of the present application.

[0293] As shown in Figure 15, take the master device as a mobile phone, the first slave device as a tablet computer (for example: Honor PAD), the target device as a PC (for example: Honor notebook), and the third collaboration type as multi-screen collaboration as an example. When the mobile phone and the tablet computer establish multi-screen collaboration, the multi-device collaboration main page can display the bubble element 611 of multi-screen collaboration. If the user wants to establish multi-device collaboration between the mobile phone and the PC, the bubble element 612 of the PC can be dragged 62 in the direction of the bubble element 611 of the multi-screen collaboration on the multi-device collaboration main page. When the user drags 62 the bubble element 612 of the PC to contact the bubble element 611 of the multi-screen collaboration, and then lifts his finger, the mobile phone displays the bubble element 612 of the Honor notebook and the bubble element 613 of the mobile phone in a fused state on the multi-device collaboration main page, and displays the switch inquiry card 710.

[0294] As shown in Figure 15, the switching inquiry card 710 may include inquiry information 711 for asking the user whether to switch the collaborative device, such as "Connecting a new device will terminate the current multi-screen collaboration with the Honor PAD, do you want to continue?". In addition, the switching inquiry card also includes an "OK" button 712 and a "Cancel" button 713. If the user clicks 63 "OK" button 712, the mobile phone will end the multi-screen collaboration with the tablet computer and establish multi-device collaboration with the PC based on the default or last used collaboration type. For example: if the mobile phone established multi-screen collaboration with the PC last time, then if the user clicks 63 "OK" button 712, the mobile phone will establish multi-screen collaboration with the PC. If the user clicks the "Cancel" button 713, the mobile phone will continue to maintain multi-screen collaboration with the tablet computer.

[0295] In one implementation, the switching inquiry card may further include a do not disturb option 714, which may include prompt information for guiding the user to select or unselect it, such as "do not prompt again". If the user selects the do not disturb option, the main device will no longer display the switching inquiry card in the same scenario, but will directly respond to the user's operation. For example, if the user drags the bubble element 612 of the PC toward the bubble element 611 of the multi-screen collaboration and contacts the bubble element 611 of the multi-screen collaboration, the mobile phone can directly end the multi-screen collaboration with the tablet and establish multi-device collaboration with the PC.

[0296] For the second case, the multi-device collaboration method may include the following steps: when the master device and the first slave device establish a second multi-device collaboration, in response to the user dragging the device identifier of the target device so that the device identifier of the target device contacts the collaboration identifier of the fourth collaboration type, the target device is added to the second multi-device collaboration.

[0297] FIG16 is a second interaction example diagram of sub-scenario 1 of a multi-device collaboration method provided in an embodiment of the present application.

[0298] As shown in Figure 16, take the master device as a mobile phone, the first slave device as a PC (for example: Honor notebook), the target device as a tablet (for example: Honor PAD), and the fourth collaboration type as a super keyboard and mouse as an example. When the mobile phone and PC have established a super keyboard and mouse, the multi-device collaboration main page can display the bubble element 621 of the super keyboard and mouse. If the user wants to add the tablet to the super keyboard and mouse, the bubble element 622 of the tablet can be dragged 64 toward the bubble element 621 of the super keyboard and mouse in the multi-device collaboration main page. When the user drags 64 the bubble element 622 of the tablet until it contacts the bubble element 621 of the super keyboard and mouse, and then lifts the finger, the mobile phone initiates a super keyboard and mouse to the tablet. At the same time, the mobile phone can present the effect of the super keyboard and mouse bubble element 621 and the tablet bubble element 622 in a fused state in the multi-device collaboration main page, so as to visually feedback the status of establishing multi-device collaboration to the user. When the tablet successfully joins the super keyboard and mouse, the bubble element 622 of the tablet is completely integrated into the bubble element 621 of the super keyboard and mouse. The mobile phone can also add the device name of the tablet computer "Honor PAD" above the bubble element 621 of the super keyboard and mouse (or other nearby positions).

[0299] For sub-scenario 2 of scenario 2, the multi-device collaboration method may include the following steps: while the master device is establishing multi-device collaboration with an out-of-loop device, in response to a user dragging a device identifier of a target device so that the target device identifier contacts the collaboration identifier of the multi-device collaboration, displaying a switch inquiry card. The switch inquiry card is used to inquire whether the user wants to switch collaborative devices.

[0300] FIG17 is an example diagram of interaction of sub-scenario 2 of a multi-device collaboration method provided in an embodiment of the present application.

[0301] As shown in Figure 17, take the main device as a mobile phone, the target device as tablet 1, and the out-of-loop device as tablet 2 as an example. When the mobile phone and tablet 2 establish multi-screen collaboration, the multi-device collaboration main page can display the bubble element 631 of multi-screen collaboration. If the user wants to establish multi-device collaboration between the mobile phone and tablet 1, the bubble element 632 of tablet 1 can be dragged 65 toward the bubble element 631 of multi-screen collaboration on the multi-device collaboration main page. When the user drags 65 the bubble element of tablet 1 until it contacts the bubble element 631 of multi-screen collaboration and then lifts the finger, the mobile phone displays the effect of the bubble element 632 of tablet 1 and the bubble element 633 of the mobile phone in a fused state on the multi-device collaboration main page, and displays a switching inquiry card 720.

[0302] Switching inquiry card 720 is similar to switching inquiry card 710 shown in FIG15 and will not be described in detail here. If the user clicks 66 "OK" button 722, the phone will end the multi-screen collaboration with tablet 2 and establish multi-device collaboration with tablet 1 based on the default or last used collaboration type. For example, if the phone last established multi-screen collaboration with tablet 1, then if the user clicks 66 "OK" button 722, the phone will establish multi-screen collaboration with tablet 1. If the user clicks "Cancel" button 723, the phone will continue to maintain multi-screen collaboration with tablet 2.

[0303] For scenario three, the multi-device collaboration method may include the following steps: when the target device establishes multi-device collaboration with other slave devices, or when the target slave device establishes multi-device collaboration with an out-of-loop device, the master device displays a switch inquiry card in response to a user dragging the device identifier of the target device so that the device identifier of the target device contacts the collaboration identifier of the multi-device collaboration. The switch inquiry card is used to inquire whether the user wants to switch collaborative devices.

[0304] Figure 18 is the first interaction example diagram of scenario three of a multi-device collaboration method provided in an embodiment of the present application.

[0305] As shown in Figure 18, take the master device as a mobile phone and the target device as a PC (for example, Honor notebook) as an example. When the PC establishes multi-device collaboration with other slave devices or devices outside the ring, the mobile phone can add a status identifier 642 to the bubble element 641 of the PC in the multi-device collaboration main page. The status identifier 642 can be, for example, a graphic corner mark located in the lower right corner of the bubble element 641 of the PC (or other locations). In this way, through the status identifier, the user can understand that the PC is currently performing multi-device collaboration with other devices other than the mobile phone.

[0306] If the user wants to establish multi-device collaboration between the mobile phone and the PC, the user can drag 67 the PC bubble element 641 toward the mobile phone bubble element 643 on the multi-device collaboration main page. When the user drags 67 the PC bubble element 641 until it contacts the mobile phone bubble element 643 and then lifts the finger, the mobile phone displays an effect of the PC bubble element 641 and the mobile phone bubble element 643 being merged on the multi-device collaboration main page and displays a switching inquiry card 730.

[0307] The switching inquiry card 730 is similar to the switching inquiry card 710 shown in Figure 15 and will not be repeated here. If the user clicks the "OK" button 732 68, the mobile phone will end the multi-device collaboration between the PC and other slave devices or devices outside the ring, and establish multi-device collaboration with the PC based on the default or last used collaboration type. For example: if the mobile phone established multi-screen collaboration with the PC last time, then if the user clicks the "OK" button 732 68, the mobile phone will establish multi-screen collaboration with the PC and cut the bubble element 643 of the mobile phone into a bubble element 644 of multi-screen collaboration. If the user clicks the "Cancel" button 733, the PC and other slave devices or devices outside the ring will continue to maintain the multi-device collaboration state.

[0308] Figure 19 is the second interaction example diagram of scenario three of a multi-device collaboration method provided in an embodiment of the present application.

[0309] For scenario three, if the collaboration type established between the target device and other slave devices or devices outside the ring supports simultaneous connection of three devices, such as a super keyboard and mouse, and the master device also supports this collaboration type, then the master device can join the multi-device collaboration currently established by the target device in response to the user dragging the device identifier of the target device.

[0310] As shown in Figure 19, take the main device as a mobile phone and the target device as a PC (for example, a Honor notebook) as an example. When a super keyboard and mouse are established between the PC and other devices (for example, an Honor PAD), the mobile phone can add a super keyboard and mouse status identifier 645 to the bubble element 641 of the PC in the multi-device collaboration main page. The status identifier 645 can be, for example, a graphic corner mark located in the lower right corner of the bubble element 641 of the PC (or other locations). In this way, through the status identifier, the user can understand that the PC is currently establishing a super keyboard and mouse with other devices.

[0311] If the user wants to add the mobile phone to the super keyboard and mouse, the user can drag 67 the PC bubble element 641 towards the mobile phone bubble element 643 on the multi-device collaboration main page. When the user drags 67 the PC bubble element 641 until it contacts the mobile phone bubble element 643 and then lifts the finger, the mobile phone displays the PC bubble element 641 and the mobile phone bubble element 643 in a fused state on the multi-device collaboration main page, visually feeding back to the user the status of establishing multi-device collaboration. When the mobile phone successfully joins the super keyboard and mouse, the mobile phone bubble element 643 and the PC bubble element 641 are completely fused to form the super keyboard and mouse bubble element 646.

[0312] For scenario 4, the multi-device collaboration method may include the following steps: when both the master device and the target device have established multi-device collaboration with other slave devices or devices outside the loop, the master device displays a switch inquiry card in response to a user dragging the device identifier of the target device so that the device identifier of the target device contacts the collaboration identifier of the multi-device collaboration. The switch inquiry card is used to inquire whether the user wants to switch the collaborative device.

[0313] Figure 20 is an interaction example diagram of scenario four of a multi-device collaboration method provided in an embodiment of the present application.

[0314] As shown in Figure 20, take the master device as a mobile phone and the target device as a PC (for example, Honor notebook) as an example. When both the mobile phone and the PC establish multi-device collaboration with other slave devices or devices outside the ring, the mobile phone will display the collaboration logo of its currently established multi-device collaboration in the multi-device collaboration main page. For example, if the mobile phone currently establishes multi-screen collaboration with a tablet computer (for example, Honor Pad), then the multi-device collaboration main page can display the bubble element 651 of multi-screen collaboration. In addition, the mobile phone can add a status identifier 642 to the bubble element 652 of the PC in the multi-device collaboration main page. In this way, through the status identifier 642, the user can understand that the PC is currently collaborating with other devices other than the mobile phone for multi-device collaboration.

[0315] If the user wants to establish multi-device collaboration between the mobile phone and the PC, the user can drag 69 the PC bubble element 652 toward the multi-screen collaboration bubble element 651 on the multi-device collaboration main page. When the user drags 69 the PC bubble element 652 until it contacts the multi-screen collaboration bubble element 651 and then lifts the finger, the mobile phone displays an effect of the PC bubble element 652 and the mobile phone bubble element 653 being merged on the multi-device collaboration main page, and displays a switching inquiry card 740.

[0316] The switching inquiry card 740 is similar to the switching inquiry card shown in Figure 15 and will not be repeated here. If the user clicks the "OK" button 742 at 71, the mobile phone will end its multi-device collaboration with other slave devices or devices outside the ring, and will also end the multi-device collaboration of the PC with other slave devices or devices outside the ring, and establish multi-device collaboration with the PC based on the default or last used collaboration type. For example, if the mobile phone established multi-screen collaboration with the PC last time, then if the user clicks the "OK" button 742 at 71, the mobile phone will establish multi-screen collaboration with the PC. If the user clicks the "Cancel" button 743, both the mobile phone and the PC will continue to maintain multi-device collaboration with other slave devices or devices outside the ring.

[0317] According to the method provided in the embodiment of the present application, when the master device and / or the slave device have established multi-device collaboration, the master device can respond to the user's operations in the multi-device collaboration main page and adopt different strategies to add or switch devices participating in the multi-device collaboration according to different scenarios, thereby improving the user experience.

[0318] Figure 21 is another interactive example diagram of a multi-device collaboration method provided in an embodiment of the present application.

[0319] As shown in Figure 21, when a slave device has established multi-device collaboration with other slave devices or devices outside the loop, if the user wants to view which other slave devices or devices outside the loop this slave device is collaborating with, they can click the device identifier 214 of the slave device 81 on the multi-device collaboration main page 300. In response to the user clicking the device identifier 214 of the slave device 81, the master device can display the collaboration status information 810 of the slave device, such as "XXX is collaborating with XXX on multiple screens." This collaboration status information 810 can disappear automatically after being displayed for a period of time, so as not to affect the display of other information on the multi-device collaboration main page 300.

[0320] According to the method provided in the embodiment of the present application, when a slave device has established multi-device collaboration with other slave devices or devices outside the ring, the user can view the multi-device collaboration information of the slave device in the multi-device collaboration main page, thereby improving the user experience.

[0321] Figure 22 is another interaction example diagram of a multi-device collaboration method provided in an embodiment of the present application.

[0322] As shown in Figure 22, if a slave device has established multi-device collaboration with other slave devices or devices outside the loop, the master device can also add a status indicator 642 to the device identifier of this slave device in the multi-device collaboration card 210. This status indicator can be, for example, a graphical corner mark located in the lower right corner of the slave device's device identifier 214 (or other locations). In this way, through the status indicator 642, the user can understand that this slave device is currently in multi-device collaboration with other devices other than the master device. Next, if the user wants to establish multi-device collaboration with the master device, they can click 91 on the slave device's device identifier 214 in the multi-device collaboration card 210. In response to the user device's click 91 operation, the master device displays a switch query card 750 on the control center page 200. The switch query card 750 is similar to the switch query card shown in Figure 15 and will not be repeated here. If the user clicks the "OK" button, the master device will end the multi-device collaboration of this slave device with other slave devices or devices outside the loop and establish multi-device collaboration with this slave device based on the default or last used collaboration type. If the user clicks the "Cancel" button, the slave device and other slave devices or devices outside the ring will continue to maintain the multi-device collaborative state.

[0323] The method provided in the embodiment of the present application allows users to directly add or switch devices participating in the multi-device collaboration in the control center page when the slave device has established multi-device collaboration with other slave devices or devices outside the ring, thereby improving the user experience.

[0324] The embodiments provided in the present application above have introduced the various schemes of the multi-device collaboration method provided in the present application. It is understandable that, in order to realize the above functions, the electronic device includes a hardware structure and / or software module corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0325] Figure 23 is a schematic diagram of the structure of a multi-device collaboration apparatus provided in an embodiment of the present application. In one embodiment, an electronic device, such as a first electronic device, can implement corresponding functions through the hardware device shown in Figure 23. As shown in Figure 23, the multi-device collaboration apparatus may include: a display screen 1001, a memory 1002, a processor 1003, and a communication module 1004. The above-mentioned components can be connected via one or more communication buses 1005.

[0326] In one embodiment, the display screen 1001 may include a display panel 10011 and a touch sensor 10012, wherein the display panel 10011 is used to display images, and the touch sensor 10012 can transmit the detected touch operation to the application processor to determine the type of touch event and provide visual output related to the touch operation through the display panel 10011. The processor 1003 may include one or more processing units, for example: the processor 1003 may include an application processor, a modem processor, a graphics processor, an image signal processor, a controller, a video codec, a digital signal processor, a baseband processor, and / or a neural network processor. The different processing units may be independent devices or integrated into one or more processors. The memory 1002 is coupled to the processor 1003 and is used to store various software programs and / or multiple sets of instructions. The memory 1002 may include volatile memory and / or non-volatile memory.

[0327] When the software program and / or multiple groups of instructions in the memory 1002 are executed by the processor 1003, the first electronic device implements the following method steps: the device displays a first page in response to user operation, and the first page includes the device identification of the first electronic device and the device identification of at least one slave device; in response to the user's operation on the device identification of the first target device in the first page, multi-device collaboration is established with the first target device based on the first collaboration type, and a type switching card is displayed in the first page; wherein the first target device is any one of the at least one slave device, and the type switching card includes the type identification of at least one collaboration type supported between the first electronic device and the first target device.

[0328] In the apparatus provided in an embodiment of the present application, the first page includes the device identifications of each slave device surrounding the first electronic device. In this way, the user can establish multi-device collaboration between the first electronic device and any slave device by operating the device identification of any slave device. The user does not need to search for control entrances of various collaboration types in different user interfaces, thereby improving the user experience.

[0329] When the software program and / or multiple groups of instructions in the memory 1002 are executed by the processor 1003, the first electronic device also implements the following method steps: in response to the user clicking the type identifier of the second collaborative type in the type switching card, the collaborative type between the first electronic device and the first target device is switched from the first collaborative type to the second collaborative type; wherein the second collaborative type is any one of at least one collaborative type, and the first collaborative type is different from the second collaborative type. In this way, when the first electronic device and the first target device support multiple collaborative modes, the first electronic device and the first target device can first establish multi-device collaboration based on the preset collaborative type, and then the user can select the collaborative type they want to use on the first electronic device. The first electronic device can switch from the preset collaborative type to the collaborative type the user wants to use based on the user's selection, thereby improving the user experience.

[0330] When the software program and / or multiple groups of instructions in the memory 1002 are executed by the processor 1003, the first electronic device implements the following method steps: in response to user operation, displaying a second page, the second page includes a multi-device collaboration card, wherein, if the first electronic device searches for at least one slave device, the multi-device collaboration card includes the device identification of at least one slave device; in response to the user's operation in the multi-device collaboration card, initiating multi-device collaboration to the second target device based on the third collaboration type, the second target device is any one of the at least one slave devices; after establishing multi-device collaboration with the second target device, switching the device identification of the second target device in the multi-device collaboration card to a collaboration identification of the third collaboration type.

[0331] In the apparatus provided in the embodiment of the present application, a multi-device collaboration card is added to the second page of the first electronic device. The multi-device collaboration card contains the device identifications of each slave device around the first electronic device. In this way, the user can establish multi-device collaboration between the first electronic device and any slave device by clicking on the device identification of any slave device. The user does not need to search for control entrances of various collaboration types in different user interfaces, thereby improving the user experience.

[0332] In one implementation, when the software program and / or multiple sets of instructions in memory 1002 are executed by processor 1003, the first electronic device further implements the following method steps: in response to a user clicking a collaboration identifier of a third collaboration type in a multi-device collaboration card, terminating the multi-device collaboration between the first electronic device and the second target device. In this way, the user can directly terminate an established multi-device collaboration in the multi-device collaboration card without having to search for control entries for various collaboration types in different user interfaces, thereby improving the user experience.

[0333] In one implementation, when the software program and / or multiple sets of instructions in the memory 1002 are executed by the processor 1003, the first electronic device further implements the following method steps: if no slave device is found and the slave device is currently being searched, the multi-device collaboration card includes a first animation identifier, which is used to indicate that the first electronic device is searching for a slave device. In this way, the first electronic device can provide feedback to the user that it is searching for a slave device, thereby improving the user experience.

[0334] In one implementation, when the software program and / or multiple sets of instructions in memory 1002 are executed by processor 1003, the first electronic device further implements the following method steps: if no slave device is found and no slave device is currently being searched, the multi-device collaboration card includes a first button; and in response to a user clicking the first button, a slave device is searched. In this way, when the first electronic device currently has no slave devices searched, the user can manually search for the slave device, thereby improving the user experience.

[0335] In one implementation, when the software program and / or multiple sets of instructions in the memory 1002 are executed by the processor 1003, the first electronic device further implements the following method steps: before displaying the second page, when the first electronic device determines that the current scene is the first scene, it determines whether at least one slave device is searched; if at least one slave device is searched, the second page includes a multi-device collaboration card, and the multi-device collaboration card includes the device identifier of at least one slave device; if no slave device is searched, the second page does not include the multi-device collaboration card; wherein the first scene includes at least one of the following: the first electronic device displays the second page for the first time after the operating system is initialized; the first electronic device displays the second page for the first time after the logged-in account changes; the first electronic device displays the second page for the first time after restoring factory settings or clearing data. In this way, if the first electronic device does not search for a slave device when displaying the second page for the first time, the multi-device collaboration card may not be displayed, thereby reducing disturbance to the user and improving the user experience.

[0336] In one implementation, when the software program and / or multiple sets of instructions in the memory 1002 are executed by the processor 1003, the first electronic device specifically implements the following method steps: In response to a user operation in a multi-device collaboration card, the first electronic device displays the first page. In this way, the first electronic device can jump directly from the second page to the first page in response to the user operation, allowing the user to perform operations such as switching collaboration types on the first page, thereby improving the user experience.

[0337] In one implementation, when the software program and / or multiple sets of instructions in the memory 1002 are executed by the processor 1003, the first electronic device specifically implements the following method steps: in response to the user's operation of long pressing the device identification of any electronic device in the multi-device collaboration card, the first page is displayed.

[0338] In one implementation, when the software program and / or multiple groups of instructions in the memory 1002 are executed by the processor 1003, the first electronic device specifically implements the following method steps: in response to the user's long press operation of the collaboration identifier of the third collaboration type in the multi-device collaboration card, the first page is displayed.

[0339] In one implementation, when the software program and / or multiple sets of instructions in the memory 1002 are executed by the processor 1003, the first electronic device specifically implements the following method steps: in response to the user clicking the second button in the multi-device collaboration card, the first page is displayed.

[0340] In this way, users can open the first page in multiple ways and manage multi-device collaboration in the first page, which improves the user experience.

[0341] In one implementation, when the software program and / or multiple sets of instructions in the memory 1002 are executed by the processor 1003, the first electronic device specifically implements the following method steps: the device responds to the user dragging the device identifier of the first target device on the first page, so that the device identifier of the first target device contacts the device identifier of the first electronic device, establishes multi-device collaboration with the first target device based on the first collaboration type, and displays a type switching card on the first page.

[0342] In one implementation, the type switching card further includes a third button. When the software program and / or multiple sets of instructions in the memory 1002 are executed by the processor 1003, the first electronic device specifically implements the following method steps: in response to a user clicking the third button, the first electronic device terminates the multi-device collaboration with the first target device. In this way, the user can terminate the multi-device collaboration between the first electronic device and the first target device on the second page, thereby improving the user experience.

[0343] In one implementation, the first page also includes a fourth button. When the software program and / or multiple sets of instructions in the memory 1002 are executed by the processor 1003, the first electronic device specifically implements the following method steps: in response to the user clicking the fourth button, the third page is displayed, the third page includes a first list, and the first list includes at least one collaborative type option; in response to the user clicking the first option, the fourth page is displayed, the first option is any collaborative type option in the first list, and the fourth page includes a switch button for the collaborative type corresponding to the first option; in response to the user clicking the switch button, the collaborative type corresponding to the first option is turned on or off. In this way, the user can control the turning on and off of each collaborative type, thereby improving the user experience.

[0344] In one implementation, when the software program and / or multiple sets of instructions in the memory 1002 are executed by the processor 1003, the first electronic device also implements the following method steps: in a state where multi-device collaboration has been established with the first slave device based on the fourth collaboration type, in response to the user's operation on the device identification of the first target device on the first page, a first switching card is generated, wherein the fourth collaboration type does not support three electronic devices being connected at the same time, and the first switching card is used to ask the user whether to switch the collaborative device; in response to the user's operation on the first switching card, the multi-device collaboration with the first slave device is terminated, and multi-device collaboration between the first electronic device and the first target device is established.

[0345] In one implementation, when the software program and / or multiple groups of instructions in the memory 1002 are executed by the processor 1003, the first electronic device also implements the following method steps: in a state where multi-device collaboration has been established with the first slave device based on the fifth collaboration type, in response to the user's operation on the device identification of the first target device on the first page, the first target device is added to the established multi-device collaboration, wherein the fifth collaboration type supports three electronic devices to be connected at the same time.

[0346] In one implementation, when the software program and / or multiple sets of instructions in the memory 1002 are executed by the processor 1003, the first electronic device also implements the following method steps: in a state where multi-device collaboration has been established with an out-of-loop device, in response to the user's operation on the device identifier of the first target device on the first page, a second switch card is generated, and the second switch card is used to ask the user whether to switch the collaborative device; in response to the user's operation on the second switch card, the multi-device collaboration with the out-of-loop device is terminated, and multi-device collaboration between the first electronic device and the first target device is established.

[0347] In one implementation, when the software program and / or multiple sets of instructions in the memory 1002 are executed by the processor 1003, the first electronic device also implements the following method steps: when the first target device and other slave devices or out-of-loop devices have established multi-device collaboration based on the fourth collaboration type, in response to the user's operation on the device identification of the first target device on the first page, a third switching card is generated, wherein the fourth collaboration type does not support three electronic devices connected at the same time, and the third switching card is used to ask the user whether to switch the collaborative device; in response to the user's operation on the third switching card, the multi-device collaboration established by the first target device is terminated, and multi-device collaboration between the first electronic device and the first target device is established.

[0348] In one implementation, when the software program and / or multiple groups of instructions in the memory 1002 are executed by the processor 1003, the first electronic device also implements the following method steps: when the first target device and other slave devices or out-of-loop devices have established multi-device collaboration based on the fifth collaboration type, in response to the user's operation on the device identification of the first target device on the first page, the first electronic device joins the multi-device collaboration established by the first target device, wherein the fifth collaboration type supports three electronic devices to be connected at the same time.

[0349] In one implementation, when the software program and / or multiple sets of instructions in the memory 1002 are executed by the processor 1003, the first electronic device also implements the following method steps: when the first electronic device and the first target device have established multi-device collaboration with other slave devices or out-of-loop devices, in response to the user's operation on the device identifier of the first target device on the first page, a fourth switch card is generated, and the fourth switch card is used to ask the user whether to switch the collaborative device; in response to the user's operation on the fourth switch card, the multi-device collaboration established by the first electronic device and the first target device is terminated, and multi-device collaboration between the first electronic device and the first target device is established.

[0350] In one implementation, when the software program and / or multiple groups of instructions in the memory 1002 are executed by the processor 1003, the first electronic device also implements the following method steps: when the second target device has established multi-device collaboration with other slave devices or out-of-loop devices, in response to the user clicking the device identifier of the second target device on the multi-device collaboration card, a fifth switch card is generated, and the fifth switch card is used to ask the user whether to switch the collaborative device; in response to the user's operation on the fifth switch card, the multi-device collaboration established by the second target device is terminated, and multi-device collaboration between the first electronic device and the second target device is established.

[0351] In this way, when the first electronic device and / or the slave device have established multi-device collaboration, the first electronic device can respond to the user's operations in the multi-device collaboration main page and adopt different strategies to add or switch devices participating in the multi-device collaboration according to different scenarios, thereby improving the user experience.

[0352] FIG24 is a schematic diagram of the structure of another multi-device collaboration apparatus provided in an embodiment of the present application. In one embodiment, an electronic device, such as a first electronic device, can implement corresponding functions through the software apparatus shown in FIG24. As shown in FIG24, the multi-device collaboration apparatus may include:

[0353] The first display module 1101 is used to display a first page in response to user operation, where the first page includes a device identification of a first electronic device and a device identification of at least one slave device; the second display module 1102 is used to establish multi-device collaboration with the first target device based on a first collaboration type in response to the user's operation on the device identification of the first target device in the first page, and display a type switching card in the first page; wherein the first target device is any one of the at least one slave device, and the type switching card includes a type identification of at least one collaboration type supported between the first electronic device and the first target device.

[0354] An embodiment of the present application further provides a computer-readable storage medium, which stores instructions. When the computer-readable storage medium is run on a computer, the computer executes the above-mentioned methods.

[0355] The embodiment of the present application also provides a computer program product containing instructions, which, when executed on a computer, enables the computer to execute the above-mentioned methods.

[0356] The present application also provides a chip system, which includes a processor for supporting the above-mentioned apparatus to implement the functions involved in the above-mentioned aspects, such as generating or processing the information involved in the above-mentioned method. In one possible design, the chip system also includes a memory for storing the computer instructions and data necessary for the multi-device collaborative apparatus. The chip system can be composed of a chip or can include a chip and other discrete devices.

[0357] The above specific implementation methods further explain in detail the purpose, technical solutions and beneficial effects of the embodiments of the present application. It should be understood that the above are only specific implementation methods of the embodiments of the present application and are not intended to limit the scope of protection of the embodiments of the present application. Any modifications, equivalent replacements, improvements, etc. made on the basis of the technical solutions of the embodiments of the present application should be included in the scope of protection of the embodiments of the present application.

Claims

1. A multi-device collaboration method, characterized in that: include: The first electronic device displays a first page in response to a user operation, where the first page includes a device identification of the first electronic device and a device identification of at least one slave device; The first electronic device establishes a multi-device collaboration with the first target device based on the first collaboration type in response to a user operation on the device identifier of the first target device on the first page, and displays a type switching card on the first page; The first target device is any one of the at least one slave device, and the type switching card includes a type identifier of at least one collaboration type supported between the first electronic device and the first target device.

2. The method according to claim 1, characterized in that The method further comprises: The first electronic device switches the collaboration type between the first electronic device and the first target device from the first collaboration type to the second collaboration type in response to a user clicking the type identifier of the second collaboration type in the type switching card; The second collaboration type is any one of the at least one collaboration type, and the first collaboration type is different from the second collaboration type.

3. The method according to claim 1 or 2, characterized in that The method further comprises: The first electronic device displays a second page in response to a user operation, the second page including a multi-device collaboration card, wherein if the first electronic device searches for at least one slave device, the multi-device collaboration card includes a device identification of the at least one slave device; The first electronic device initiates multi-device collaboration to a second target device based on the third collaboration type in response to a user operation in the multi-device collaboration card, where the second target device is any one of the at least one slave device; After the first electronic device establishes multi-device collaboration with the second target device, the device identifier of the second target device in the multi-device collaboration card is switched to a collaboration identifier of the third collaboration type.

4. The method according to claim 3, characterized in that The method further comprises: In response to the user clicking the collaboration identifier of the third collaboration type in the multi-device collaboration card, the first electronic device ends the multi-device collaboration between the first electronic device and the second target device.

5. The method according to claim 3, characterized in that The method further comprises: If the first electronic device has not searched for a slave device and is currently searching for a slave device, the multi-device collaboration card includes a first animation identifier, and the first animation identifier is used to indicate that the first electronic device is in a state of searching for a slave device.

6. The method according to claim 3, characterized in that The method further comprises: If the first electronic device has not searched for a slave device and is not currently searching for a slave device, the multi-device collaboration card includes a first button; The first electronic device searches for slave devices in response to a user clicking the first button.

7. The method according to claim 3, characterized in that The method further comprises: Before displaying the second page, when the first electronic device determines that the current scene is the first scene, determining whether at least one slave device is searched; If at least one slave device is found, the second page includes the multi-device collaboration card, and the multi-device collaboration card includes the device identification of the at least one slave device; if no slave device is found, the second page does not include the multi-device collaboration card; The first scenario includes at least one of the following: The first electronic device displays the second page for the first time after the operating system is initialized; The first electronic device displays the second page for the first time after the login account changes; The first electronic device displays the second page for the first time after restoring factory settings or clearing data.

8. The method according to any one of claims 3 to 7, characterized in that: The first electronic device displays the first page in response to the user operation, including: the first electronic device displays the first page in response to the user operation in the multi-device collaborative card.

9. The method according to claim 8, characterized in that The first electronic device displays the first page in response to the user's operation in the multi-device collaborative card, including: the first electronic device displays the first page in response to the user's operation of long pressing the device identification of any one of the electronic devices in the multi-device collaborative card.

10. The method according to claim 8, characterized in that The first electronic device displays the first page in response to the user's operation in the multi-device collaboration card, including: the first electronic device displays the first page in response to the user's operation of long pressing the collaboration identifier of the third collaboration type in the multi-device collaboration card.

11. The method according to claim 8, characterized in that The multi-device collaboration card includes a second button, and the first electronic device displays the first page in response to the user's operation in the multi-device collaboration card, including: the first electronic device displays the first page in response to the user's operation of clicking the second button in the multi-device collaboration card.

12. The method according to any one of claims 1 to 11, characterized in that The first electronic device establishes multi-device collaboration with the first target device based on a first collaboration type in response to a user's operation on a device identifier of the first target device on the first page, and displays a type switching card on the first page, including: In response to the user dragging the device identifier of the first target device on the first page so that the device identifier of the first target device comes into contact with the device identifier of the first electronic device, the first electronic device establishes multi-device collaboration with the first target device based on the first collaboration type and displays a type switching card on the first page.

13. The method according to any one of claims 1 to 12, characterized in that The type switching card further includes a third button, and the method further includes: the first electronic device disconnecting the multi-device collaboration with the first target device in response to the user clicking the third button.

14. The method according to any one of claims 1 to 13, characterized in that The first page further includes a fourth button, and the method further includes: In response to a user clicking operation on the fourth button, the first electronic device displays a third page, wherein the third page includes a first list, and the first list includes at least one option of a collaboration type; The first electronic device displays a fourth page in response to a user clicking on a first option, where the first option is any one of the collaboration types in the first list, and the fourth page includes a switch button for the collaboration type corresponding to the first option; The first electronic device turns on or off the collaboration type corresponding to the first option in response to a user clicking the switch button.

15. The method according to any one of claims 1 to 14, characterized in that The method further comprises: In a state where the first electronic device and the first slave device have established multi-device collaboration based on a fourth collaboration type, in response to a user operating a device identifier of the first target device on the first page, generating a first switching card, wherein the fourth collaboration type does not support simultaneous connection of three electronic devices, and the first switching card is used to inquire the user whether to switch the collaborative device; In response to the user's operation on the first switching card, the first electronic device ends the multi-device collaboration with the first slave device and establishes the multi-device collaboration between the first electronic device and the first target device.

16. The method according to any one of claims 1 to 14, characterized in that The method further comprises: When the first electronic device and the first slave device have established multi-device collaboration based on the fifth collaboration type, in response to the user's operation on the device identification of the first target device on the first page, the first target device is added to the established multi-device collaboration, wherein the fifth collaboration type supports three electronic devices to be connected at the same time.

17. The method according to any one of claims 1 to 14, characterized in that The method further comprises: In a state where multi-device collaboration has been established between the first electronic device and the out-of-loop device, in response to a user operating a device identifier of the first target device on the first page, a second switching card is generated, wherein the second switching card is used to inquire the user whether to switch the collaborative device; In response to the user's operation on the second switching card, the first electronic device ends the multi-device collaboration with the out-of-loop device and establishes the multi-device collaboration between the first electronic device and the first target device.

18. The method according to any one of claims 1 to 14, characterized in that The method further comprises: In a state where multi-device collaboration has been established between the first target device and other slave devices or out-of-loop devices based on a fourth collaboration type, the first electronic device generates a third switching card in response to a user operation on the device identifier of the first target device on the first page, wherein the fourth collaboration type does not support simultaneous connection of three electronic devices, and the third switching card is used to inquire the user whether to switch the collaborative device; In response to the user's operation on the third switching card, the first electronic device ends the multi-device collaboration established with the first target device and establishes the multi-device collaboration between the first electronic device and the first target device.

19. The method according to any one of claims 1 to 14, characterized in that The method further comprises: The first target device and other slave devices or out-of-ring devices have established a multi-device collaboration state based on the fifth collaboration type. In this state, the first electronic device responds to the user's operation on the device identification of the first target device on the first page, and joins the multi-device collaboration established by the first target device, wherein the fifth collaboration type supports three electronic devices to be connected at the same time.

20. The method according to any one of claims 1 to 14, characterized in that The method further comprises: In a state where both the first electronic device and the first target device have established multi-device collaboration with other slave devices or out-of-loop devices, the first electronic device generates a fourth switching card in response to a user operating a device identifier of the first target device on the first page, the fourth switching card being used to inquire the user whether to switch the collaborative device; In response to the user's operation on the fourth switching card, the first electronic device ends the multi-device collaboration established between the first electronic device and the first target device, and establishes the multi-device collaboration between the first electronic device and the first target device.

21. The method according to any one of claims 2 to 14, characterized in that: The method further comprises: In a state where the second target device has established multi-device collaboration with other slave devices or out-of-loop devices, the first electronic device generates a fifth switching card in response to a user clicking a device identifier of the second target device on the multi-device collaboration card, wherein the fifth switching card is used to inquire the user whether to switch the collaborative device; In response to the user's operation on the fifth switching card, the first electronic device ends the multi-device collaboration established by the second target device and establishes the multi-device collaboration between the first electronic device and the second target device.

22. An electronic device, characterized in that: include: processor, memory, and display; The memory stores program instructions, and when the program instructions are executed by the processor, the electronic device executes the method according to any one of claims 1 to 21.

23. A computer-readable storage medium, characterized in that The computer-readable storage medium stores instructions, and when the instructions are executed on a computer, the computer is caused to execute the method according to any one of claims 1 to 21.

Images