WO2024027238A1 - 一种多设备协同方法、电子设备及相关产品 - Google Patents

一种多设备协同方法、电子设备及相关产品 Download PDF

Info

Publication number
WO2024027238A1
WO2024027238A1 PCT/CN2023/091339 CN2023091339W WO2024027238A1 WO 2024027238 A1 WO2024027238 A1 WO 2024027238A1 CN 2023091339 W CN2023091339 W CN 2023091339W WO 2024027238 A1 WO2024027238 A1 WO 2024027238A1
Authority
WO
WIPO (PCT)
Prior art keywords
collaboration
user
page
electronic device
card
Prior art date
Application number
PCT/CN2023/091339
Other languages
English (en)
French (fr)
Inventor
肖亮
秦川
房新凯
Original Assignee
荣耀终端有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 荣耀终端有限公司 filed Critical 荣耀终端有限公司
Publication of WO2024027238A1 publication Critical patent/WO2024027238A1/zh

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/14—Digital output to display device ; Cooperation and interconnection of the display device with other functional units
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/14—Digital output to display device ; Cooperation and interconnection of the display device with other functional units
    • G06F3/1454—Digital output to display device ; Cooperation and interconnection of the display device with other functional units involving copying of the display data of a local workstation or window to a remote workstation or window so that an actual copy of the data is displayed simultaneously on two or more displays, e.g. teledisplay
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72484—User interfaces specially adapted for cordless or mobile telephones wherein functions are triggered by incoming communication events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/001—Synchronization between nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers

Definitions

  • the present application relates to the field of terminal technology, and in particular, to a multi-device collaboration method, electronic devices and related products.
  • Multi-device collaboration is a distributed technology applied to multiple electronic devices.
  • two or more electronic devices can collaborate across systems and devices to achieve resource sharing and collaborative operations.
  • control entrances for each collaboration type are distributed in different user interfaces.
  • the control entrance for screen casting may be located in the playback interface of a video application
  • 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 operate them. This requires users to remember the location of the control entrances for each type of multi-screen collaboration. This results in higher memory costs for users and reduces the user experience.
  • Embodiments of the present application provide a multi-device collaboration method, electronic devices and related products to improve the user experience of multi-device collaboration.
  • embodiments of the present application provide a multi-device collaboration method, including: in response to a user operation, a first electronic device displays a first page, where the first page includes a device identification of the first electronic device and at least one slave device. Device identification; in response to the user's operation on the device identification of the first target device in the first page, the first electronic device establishes multi-device collaboration with the first target device based on the first collaboration type, and displays the type switch in the first page Card; wherein the first target device is any slave device among the at least one slave device, and the type switching card includes a type identifier of at least one collaborative type supported between the first electronic device and the first target device.
  • the first page contains the device identification of each slave device around the first electronic device.
  • the user can make the first electronic device communicate with any slave device by operating the device identification of any slave device.
  • Establishing multi-device collaboration does not require users to search for control entrances of various collaboration types in different user interfaces, which improves the user experience.
  • the method further includes: in response to the user's click operation on the type identifier of the second collaboration type in the type switching card, the first electronic device changes the collaboration between the first electronic device and the first target device.
  • the type is switched from the first collaboration type to the second collaboration type; wherein 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.
  • the first electronic device and the first target device can first establish multi-device collaboration based on the preset collaboration type, and then the user can
  • the first electronic device may select the type of collaboration it desires to use based on the user's selection, Switching from the preset collaboration type to the collaboration type expected by the user improves the user experience.
  • the method further includes: the first electronic device displays a second page in response to a user operation, and the second page includes a multi-device collaboration card, wherein if the first electronic device searches for at least one slave device, the multiple devices
  • the 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, the first electronic device initiates multi-device collaboration to the second target device based on the third collaboration type, and the second target device is at least Any one of the slave devices; after the first electronic device establishes multi-device collaboration with the second target device, switches the device identification of the second target device in the multi-device collaboration card to the collaboration identification of the third collaboration type.
  • the user can click the device identification of any slave device in the multi-device collaboration card to establish multi-device collaboration between the first electronic device and any slave device, without the user having to search for various collaboration types in different user interfaces.
  • the control entrance improves the user experience.
  • the method further includes: the first electronic device responds to the user's operation of clicking the collaboration logo of the third collaboration type in the multi-device collaboration card, ending the multi-device collaboration between the first electronic device and the second target device.
  • Device collaboration In this way, users can directly end the established multi-device collaboration in the multi-device collaboration card, without having to search for control entrances of various collaboration types in different user interfaces, which improves the user experience.
  • the method further includes: if the first electronic device does not search for the slave device and is currently searching for the slave device, the multi-device collaboration card includes a first dynamic effect identifier, and the first dynamic effect identifier is used to indicate The first electronic device is searching for the status of the slave device. In this way, the first electronic device can feed back to the user the status of the slave device being searched, thereby improving the user experience.
  • the method further includes: if the first electronic device does not search for the slave device and is not currently searching for the slave device, the multi-device collaboration card includes a first button; the first electronic device responds to the user clicking the first Button operation to search for slave devices. In this way, when the first electronic device does not currently search for the slave device, the user can manually search for the slave device, which improves the user experience.
  • the method further includes: before displaying the second page, when the first electronic device determines that the current scene is the first scene, determine 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 found, the second page does not include a multi-device collaboration card; wherein the first scenario includes at least one of the following: An 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. Display the second page for the first time. In this way, when the first electronic device displays the second page for the first time, if the slave device is not searched, the multi-device collaboration card may not be displayed, thereby reducing interruption to the user and improving the user experience.
  • the first electronic device displays the first page in response to the user's operation, including: the first electronic device displays the first page in response to the user's operation in the multi-device collaboration card.
  • the first electronic device can directly jump from the second page to the first page in response to the user's operation, so that the user can perform operations such as switching collaboration types on the first page, thereby improving the user experience.
  • 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 responds to the user's long press of any electronic device in the multi-device collaboration card. For device identification operations, the first page is displayed.
  • 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 responds to the user's long press of the third collaboration type in the multi-device collaboration card.
  • the operation of collaborative identification displays the first page.
  • the multi-device collaboration card includes a second button
  • the first electronic device responds to the user's operation in the multi-device collaboration card and displays the first page, including: the first electronic device responds to the user's operation in the multi-device collaboration card. Clicking the second button in the collaboration card displays the first page.
  • the user can open the first page in multiple ways and perform collaborative management of multiple devices on the first page, which improves the user experience.
  • the first electronic device responds to the user's operation on the device identification of the first target device on the first page, establishes multi-device collaboration with the first target device based on the first collaboration type, and displays the Displaying a type switching card in the medium includes: the first electronic device responds to the user dragging the device identification of the first target device on the first page, causing the device identification of the first target device to come into contact with the device identification of the first electronic device, Multi-device collaboration is established with the first target device based on the first collaboration type, and a type switching card is displayed on the first page.
  • the type switching card further includes a third button
  • the method further includes: in response to the user's operation of clicking the third button, the first electronic device disconnects multi-device collaboration with the first target device. In this way, the user can end the multi-device collaboration between the first electronic device and the first target device on the third page, which improves the user experience.
  • the first page also includes a fourth button
  • the method further includes: the first electronic device displays a third page in response to the user's click operation on the fourth button, and the third page includes the first list,
  • the first list includes at least one collaboration type option;
  • the first electronic device displays a fourth page in response to the user's click operation on the first option, the first option is any collaboration type option in the first list, and the fourth
  • the page includes a switch button of 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 the user's click operation on the switch button. In this way, users can control the opening and closing of each collaboration type, which improves the user experience.
  • 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 fourth collaboration type, responding to the user's device identification of the first target device on the first page.
  • the operation generates 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 ask the user whether to switch the collaboration device; the first electronic device responds to the user's response to the first switching card.
  • Operation end multi-device collaboration with the first slave device, and establish multi-device collaboration between the first electronic device and the first target device.
  • 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, responding to the user's device identification of the first target device on the first page.
  • the method further includes: in a state where the first electronic device and the out-of-loop device have established multi-device collaboration, in response to the user's operation on the device identification of the first target device on the first page, generating a second Switch card, the second switching card is used to ask the user whether to switch the collaborative device; the first electronic device responds to the user's operation on the second switching card, ends the multi-device collaboration with the out-of-loop device, and establishes the relationship between the first electronic device and Multi-device collaboration between first target devices.
  • the method further includes: in a state where 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 responds to the user's request on the first page.
  • the operation of the device identification of the first target device generates a third switching card, wherein the fourth collaboration type does not support simultaneous connection of three electronic devices, and the third switching card is used to ask the user whether to switch the collaboration device; the first electronic device responds to The user's operation on the third switching card ends the established multi-device collaboration of the first target device, and establishes the multi-device collaboration between the first electronic device and the first target device.
  • the method further includes: in a state where the first target device has established multi-device collaboration with other slave devices or out-of-loop devices based on the fifth collaboration type, the first electronic device responds to the user's request on the first page.
  • first target device The operation of the device identification is added to the multi-device collaboration established by the first target device, wherein the fifth collaboration type supports simultaneous connection of three electronic devices.
  • the method further includes: in a state where 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 responds to the user's request on the first page.
  • the operation on the device identification of the first target device generates a fourth switching card.
  • the fourth switching card is used to ask the user whether to switch the collaborative device; the first electronic device responds to the user's operation on the fourth switching card and ends the first electronic device.
  • the first target device has established multi-device collaboration respectively, and establishes the multi-device collaboration between the first electronic device and the first target device.
  • the method further includes: when the second target device has established multi-device collaboration with other slave devices or out-of-loop devices, the first electronic device responds to the user clicking on the second target device on the multi-device collaboration card.
  • the operation of the device identification generates a fifth switching card.
  • the fifth switching card is used to ask the user whether to switch the collaborative device; the first electronic device responds to the user's operation of the fifth switching card and ends the multi-device established by the second target device. Collaborate, and establish multi-device collaboration between the first electronic device and the second target device.
  • the first electronic device can respond to the user's operation on the multi-device collaboration main page and adopt different strategies according to different scenarios.
  • Devices participating in multi-device collaboration can be added or switched to improve the user experience.
  • embodiments of the present application further provide a multi-device collaboration device, including: a first display module configured to display a first page in response to a user operation, where the first page includes a device identification of the first electronic device and at least a device identification of the slave device; a second display module, configured to respond to the user's operation on the device identification of the target device on the first page, establish multi-device collaboration with the target device based on the first collaboration type, and display the A type switching card is displayed; wherein the 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 target device.
  • the first page contains the device identification of each slave device around the first electronic device. In this way, the user can make the first electronic device communicate with any slave device by operating the device identification of any slave device. Establishing multi-device collaboration does not require users to search for control entrances of various collaboration types in different user interfaces, which improves the user experience.
  • embodiments of the present application also provide a computer-readable storage medium.
  • the computer-readable storage medium stores instructions that, when run on a computer, cause the computer to execute the above aspects and methods for implementing each of them.
  • embodiments of the present application also provide a computer program product containing instructions, which, when run on a computer, causes the computer to execute the above aspects and the methods for their respective implementations.
  • embodiments of the present application also provide a chip system, which includes a processor to support the above-mentioned terminal device in implementing the functions involved in the above-mentioned aspects, for example, generating or processing information involved in the above-mentioned methods. .
  • Figure 1 is a schematic diagram of the hardware structure of an electronic device provided by an embodiment of the present application.
  • Figure 2 is a software structure block diagram of the electronic device according to the embodiment of the present application.
  • Figure 3 is a first flow chart of a multi-device collaboration method provided by an embodiment of the present application.
  • Figure 4A is the first schematic diagram of the control center page provided by the embodiment of the present application.
  • Figure 4B is a second schematic diagram of the control center page provided by the embodiment of the present application.
  • Figure 4C is the third schematic diagram of the control center page provided by the embodiment of the present application.
  • Figure 4D is the fourth schematic diagram of the control center page provided by the embodiment of the present application.
  • Figure 5 is a first set of interaction example diagrams of a multi-device collaboration method provided by an embodiment of the present application
  • Figure 6 is a second set of interaction example diagrams of a multi-device collaboration method provided by an embodiment of the present application.
  • Figure 7 is a third set of interaction example diagrams of a multi-device collaboration method provided by an embodiment of the present application.
  • Figure 8 is a second flow chart of a multi-device collaboration method provided by an embodiment of the present application.
  • Figures 9A-9D are a fourth set of interaction example diagrams of a multi-device collaboration method provided by embodiments of the present application.
  • Figures 10A-10D are a fifth set of interaction example diagrams of a multi-device collaboration method provided by embodiments of the present application.
  • Figures 11A-11D are a sixth set of interaction example diagrams of a multi-device collaboration method provided by embodiments of the present application.
  • Figures 12A-12D are a seventh set of interaction example diagrams of a multi-device collaboration method provided by embodiments of the present application.
  • Figures 13A-13C are diagrams illustrating the opening and closing methods of the automatic collaborative service according to the embodiment of the present application.
  • Figure 14 is an interactive example diagram of scenario one of the multi-device collaboration method provided by the embodiment of the present application.
  • Figure 15 is a first interactive example diagram of sub-scenario 1 of a multi-device collaboration method provided by the embodiment of the present application;
  • Figure 16 is a second interaction example diagram of sub-scenario 1 of a multi-device collaboration method provided by the embodiment of the present application;
  • Figure 17 is an interactive example diagram of sub-scenario 2 of a multi-device collaboration method provided by the embodiment of the present application;
  • Figure 18 is a first interactive example diagram of scenario three of a multi-device collaboration method provided by an embodiment of the present application.
  • Figure 19 is a second interaction example diagram of scenario three of a multi-device collaboration method provided by the embodiment of the present application.
  • Figure 20 is an interactive example diagram of scenario four of a multi-device collaboration method provided by an embodiment of the present application.
  • Figure 21 is another interactive example diagram of a multi-device collaboration method provided by an embodiment of the present application.
  • Figure 22 is another interactive example diagram of a multi-device collaboration method provided by an embodiment of the present application.
  • Figure 23 is a schematic structural diagram of a multi-device collaboration device provided by an embodiment of the present application.
  • Figure 24 is a schematic structural diagram of another multi-device collaboration device provided by an embodiment of the present application.
  • Multi-device collaboration is a distributed technology applied to multiple electronic devices.
  • two or more electronic devices can collaborate across systems and devices to achieve resource sharing and collaborative operations.
  • Multi-device collaboration can be applied between electronic devices of the same type or different types.
  • the types of electronic devices include but are not limited to mobile phones, tablets, laptops, large-screen devices (such as smart TVs, smart screens), personal computers (PCs), handheld computers, netbooks, and personal digital assistants (personal digital assistants).
  • assistant, PDA personal digital assistants
  • wearable electronic devices vehicle-mounted devices, virtual reality devices and other devices.
  • the communication connection may be a wired communication connection or a wireless communication connection.
  • solutions for wired communication connections may include, for example, USB On-The-Go (OTG) technology
  • solutions for wireless communication may include, for example, wireless fidelity (Wi-Fi), Wi-Fi Direct (Wi-Fi), etc.
  • -Fi Direct wireless fidelity
  • Bluetooth blue, BT
  • near field communication technology near field communication, NFC
  • infrared technology infrared, IR
  • collaboration services also known as: collaboration services
  • screen expansion screen projection
  • super call screen projection
  • screen mirroring multi-screen collaboration
  • super notification key Mouse sharing
  • super keyboard and mouse etc.
  • Screen expansion Use the screen of electronic device B as the secondary screen of electronic device A.
  • Electronic device A can transfer part of the content it needs to display to the secondary screen for display.
  • the screen of electronic device A and the screen of electronic device B can be displayed together. content, extending the display capabilities of electronic device A.
  • Screen casting Cast the content (such as videos, photos, etc.) on the screen of electronic device A to the screen of electronic device B to display.
  • the user can select part or all of the content on the screen of electronic device A to be displayed on the screen of electronic device B.
  • Some screencasting methods also allow the user to switch the screen to other pages during screencasting without affecting electronic device B to continue playing the cast content, such as DLNA screencasting.
  • Screen mirroring Completely mirror and display all the content on the screen of electronic device A on the screen of electronic device B.
  • the content of electronic device A displayed in electronic device B is the same as the content displayed by electronic device A, and changes as the content displayed by electronic device A changes.
  • Multi-screen collaboration Project the user interface of electronic device A to the screen of electronic device B for display, and allow the user to operate the user interface of electronic device A in electronic device B, and perform specific tasks in electronic device B. Operation (for example: drag and drop files from the user interface of electronic device B to the user interface of electronic device A), transfer the files in electronic device B to electronic device A, and realize the communication between electronic device A and electronic device B. Cross-device operations and cross-device file transfers, etc. Among them, the user interface of electronic device A can be displayed in any area on the screen of electronic device B, or can be displayed in full screen.
  • the notification message can be displayed simultaneously on electronic device B, and the user can also perform operations such as replying, deleting, and reading the notification message on electronic device B.
  • Electronic device A and electronic device B can share each other's original input devices, such as mouse, keyboard, etc.
  • the input device of electronic device A is shared with electronic device B.
  • the shared input device can be used for input in electronic device A or electronic device B.
  • file transfer can also be performed between electronic device A and electronic device B.
  • the interface of electronic device B can prompt the user to open the application running on electronic device A on electronic device B, thereby transferring to electronic device B for continued operations, such as watching.
  • a document application is running on electronic device A.
  • the document application can be memo, word, etc., and the user is editing a document on electronic device A.
  • a prompt message is displayed on electronic device B.
  • electronic device B opens the document application and displays the position where the user is editing, thereby transferring to electronic device B to continue editing, etc.
  • collaboration types are initiated by the master device (generally the initiator of multi-device collaboration) in response to user operations to the slave device (generally the participant of multi-device collaboration), so they can It is called manual collaboration service or manual collaboration business, such as: screen expansion, screen casting, screen mirroring, multi-screen collaboration, keyboard and mouse sharing, etc.; other collaboration types are automatically triggered when the trigger rules are met when the user turns on the function. , so it can be called automatic collaborative service or automatic collaborative business, such as: super call, super notification, super connection, etc.
  • two electronic devices For two electronic devices, the type of collaboration they support is generally related to factors such as device type, screen size, and device capabilities. Therefore, two electronic devices may support only one type of cooperation or may support multiple types of cooperation.
  • the supported collaboration types can include multi-screen collaboration.
  • the supported collaboration types can include super keyboard and mouse, and multi-screen collaboration.
  • the default collaboration type can be multi-screen collaboration.
  • the supported collaboration types can include super keyboard and mouse, multi-screen collaboration, screen mirroring and screen expansion.
  • the default collaboration class can be multi-screen collaboration.
  • the supported collaboration types can include screencasting.
  • the supported collaboration types can include multi-screen collaboration.
  • the supported collaboration types can include screen mirroring, screen extension, and super keyboard and mouse.
  • the default collaboration type may be screen mirroring.
  • the supported collaboration types can include screencasting.
  • the supported collaboration types can include super keyboard and mouse, and multi-screen collaboration.
  • the default collaboration type can be multi-screen collaboration.
  • the supported collaboration types can include super keyboard and mouse, multi-screen collaboration, screen mirroring and screen expansion.
  • the default collaboration type can be multi-screen collaboration.
  • the supported collaboration types can include screen mirroring, screen extension, and super keyboard and mouse.
  • the default collaboration type may be screen mirroring.
  • the supported collaboration types can include screencasting.
  • Electronic devices that support super calls can include mobile phones, tablets, PCs, large-screen display devices, etc.
  • Electronic devices that support super notifications can include mobile phones, tablets, PCs, etc.
  • Electronic devices that support super connection can include mobile phones, tablets, PCs, large-screen display devices, etc.
  • each collaboration type does not have a unified control entrance in the terminal device, and the control entrances of each collaboration type are distributed in different user interfaces.
  • the control entrance for screen projection may be located in the playback interface of a video application
  • the control entrance for multi-screen collaboration may be located on 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 operate them. This requires users to remember the location of the control entrances for each type of multi-screen collaboration. This results in higher memory costs for users and reduces the user experience.
  • embodiments of the present application provide a multi-device collaboration method.
  • the multi-device collaboration method in the embodiment of the present application can be applied to various types of electronic devices with display functions.
  • FIG. 1 is a schematic diagram of the hardware structure of an electronic device provided by an embodiment of the present application. This device can be used as a master device in multi-device collaboration or as a slave device in multi-device collaboration.
  • 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, touch sensor 190, air pressure sensor 210 and buttons 220, etc.
  • USB universal serial bus
  • the processor 110 may include one or more processing units.
  • the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processing unit (GPU), and an image signal processor. (image signal processor, ISP), video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural network processor (neural-network processing unit, NPU), etc.
  • different processing units can be independent devices, or they can be integrated in one or more processors, such as integrated in a system on a chip (SoC).
  • SoC system on a chip
  • the processor 110 may also be provided with a memory for storing instructions and data.
  • the memory in processor 110 is cache memory. This memory may hold instructions or data that have been recently used or recycled by processor 110 .
  • processor 110 may include one or more interfaces.
  • Interfaces may include integrated circuits (inter-integrated circuit, I2C) interface, integrated circuit built-in audio (inter-integrated circuit sound, I2S) interface, pulse code modulation (PCM) interface, universal asynchronous receiver/transmitter (UART) ) interface, mobile industry processor interface (MIPI), general-purpose input/output (GPIO) interface, subscriber identity module (SIM) interface, and/or universal serial bus (universal serial bus, USB) interface, etc.
  • I2C integrated circuits
  • I2S integrated circuit built-in audio
  • PCM pulse code modulation
  • UART universal asynchronous receiver/transmitter
  • MIPI mobile industry processor interface
  • GPIO general-purpose input/output
  • SIM subscriber identity module
  • USB universal serial bus
  • Memory 120 may be used to store computer executable program code, which includes instructions.
  • the memory 120 may include a program storage area and a data storage area.
  • the stored program area can store an operating system, at least one application program required for a function (such as a sound playback function, an image playback function, etc.).
  • the storage data area may store data created during use of the electronic device 100 (such as audio data, phone book, etc.).
  • the memory 120 may include one or more storage units, for example, may include volatile memory (volatile memory), such as: dynamic random access memory (dynamic random access memory, DRAM), static random access memory (static random access memory) memory, SRAM), etc.; it can also include non-volatile memory (non-volatile memory, NVM), such as read-only memory (read-only memory, ROM), flash memory (flash memory), etc.
  • volatile memory volatile memory
  • DRAM dynamic random access memory
  • static random access memory static random access memory
  • SRAM static random access memory
  • NVM non-volatile memory
  • the processor 110 executes various functional applications and data processing of the electronic device 100 by executing instructions stored in the memory 120 and/or instructions stored in the memory provided in the processor.
  • the operating systems referred to in the embodiments of this application include but are not limited to Android operating system, IOS operating system, iPad OS, Hongmeng operating system (HarmonyOS), Windows operating system, Linux operating system, MAC OS operation systems, embedded systems, etc.
  • 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, etc.
  • the radio frequency circuit 140 may include at least one antenna 141 for transmitting and receiving electromagnetic wave signals.
  • Each antenna in electronic device 100 may be used to cover a single or multiple communication frequency bands.
  • antennas may be used in conjunction with tuning switches.
  • the mobile communication module 150 can provide solutions for wireless communication including 2G/3G/4G/5G etc. on the electronic device 100 .
  • the mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc.
  • the mobile communication module 150 can receive electromagnetic waves through the antenna 141, perform filtering, amplification and other processing on the received electromagnetic waves, and transmit them to the modem processor for demodulation.
  • the mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves through the antenna 141 for radiation.
  • at least part of the functional modules of the mobile communication module 150 may be disposed in the processor 110 .
  • at least part of the functional modules of the mobile communication module 150 and at least part of the modules of the processor 110 may be provided in the same device.
  • a modem processor may include a modulator and a demodulator.
  • the modulator is used to modulate the low-frequency baseband signal to be sent 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.
  • the application processor outputs sound signals through audio devices (including but not limited to speakers, receivers, etc.), or displays images or videos through the display screen 180 .
  • the modem processor may be a stand-alone device.
  • the modem processor may be independent of the processor 110 and may be provided in the same device as the mobile communication module 150 or other functional modules.
  • 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 (infrared, IR) module, etc.
  • 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 through the antenna 141, frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110.
  • the wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves through the antenna 141 for radiation.
  • 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) 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 communications technology new radio (5th generation mobile networks new radio, 5G NR), BT, GNSS, WLAN, NFC, FM, and/or IR and other functions.
  • GSM global system for mobile communications
  • GPRS general packet radio service
  • CDMA code division multiple access
  • CDMA code division multiple access
  • WCDMA wideband code division multiple access
  • TD-SCDMA time-division code division multiple access
  • LTE long term evolution
  • GNSS can include global positioning system (GPS), global navigation satellite system (GLONASS), Beidou navigation satellite system (BDS), quasi-zenith satellite system (quasi-zenith) satellite system (QZSS) and/or satellite based augmentation systems (SBAS).
  • GPS global positioning system
  • GLONASS global navigation satellite system
  • BDS Beidou navigation satellite system
  • QZSS quasi-zenith satellite system
  • SBAS satellite based augmentation systems
  • Camera 170 is used to capture still images or video.
  • the camera 170 includes a lens and a photosensitive element.
  • the object generates an optical image through the lens and projects it to the photosensitive element.
  • the photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor.
  • CMOS complementary metal-oxide-semiconductor
  • the photosensitive element converts the optical signal into an electrical signal, and then passes the electrical signal to the ISP to convert it into a digital image signal.
  • ISP outputs digital image signals to DSP for processing.
  • DSP converts digital image signals into standard RGB, YUV, RYYB and other format image signals.
  • the electronic device 100 may include 1 or N cameras 170, where N is a positive integer greater than 1.
  • NPU is a neural network (NN) computing processor.
  • NN neural network
  • Applications such as intelligent cognition of the electronic device 100 can be implemented through the NPU, such as image recognition, face recognition, speech recognition, text understanding, etc.
  • the display screen 180 is used to display images, videos, etc.
  • Display 180 includes a display panel.
  • the display panel can use a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active matrix organic light emitting diode or an active matrix organic light emitting diode (active-matrix organic light emitting diode).
  • LCD liquid crystal display
  • OLED organic light-emitting diode
  • AMOLED organic light-emitting diode
  • FLED flexible light-emitting diode
  • MiniLED MicroLED
  • Micro-OLED quantum dot light emitting diode
  • QLED quantum dot light emitting diode
  • the electronic device 100 may include 1 or N display screens 180, where N is a positive integer greater than 1.
  • Touch sensor 190 is also called a "touch device”.
  • the touch sensor 190 can be disposed on the display screen 180.
  • the touch sensor 190 and the display screen 180 form a touch screen, which is also called a "touch screen”.
  • the touch sensor 190 is used to detect touch operations on or near the touch sensor 190 .
  • the touch sensor can pass the detected touch operation to the application processor to determine the touch event type.
  • Visual output related to the touch operation may be provided through the display screen 180 .
  • the touch sensor 190 may also be disposed on the surface of the electronic device 100 in a position different from that of the display screen 180 .
  • the air pressure sensor 210 is used to measure air pressure. In some embodiments, the electronic device 100 calculates the altitude through the air pressure value measured by the air pressure sensor 210 to assist positioning and navigation.
  • the buttons 220 include a power button, a volume button, etc.
  • the key 220 may be a mechanical key. It can also be a touch button.
  • the electronic device 100 may receive key inputs and generate key signals related to user settings and function control of the electronic device 100 enter.
  • the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the electronic device 100 .
  • the electronic device may include more or less components than shown in the figures, or some components may be combined, some components may be separated, or some components may be arranged differently.
  • the components illustrated may be implemented in hardware, software, or a combination of software and hardware.
  • the software system of the electronic device 100 may adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture.
  • This embodiment of the present invention takes the Android system with a layered architecture as an example to illustrate the software structure of the electronic device 100 .
  • FIG. 2 is a software structure block diagram of the electronic device 100 according to the embodiment of the present application.
  • the layered architecture divides the software into several layers, and each layer has clear roles and division of labor.
  • the layers communicate through software interfaces.
  • the Android system is divided into four layers, from top to bottom: application layer, application framework layer, Android runtime and system libraries, and kernel layer.
  • the application layer can include a series of application packages.
  • the application package can include camera, gallery, calendar, calling, map, navigation, WLAN, Bluetooth, music, video, short message and other applications.
  • the application framework layer provides an application programming interface (API) and programming framework for applications in the application layer.
  • API application programming interface
  • the application framework layer includes some predefined functions.
  • the application framework layer can include a window manager, content provider, view system, phone manager, resource manager, notification manager, etc.
  • a 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, capture the screen, etc.
  • Content providers are used to store and retrieve data and make this data accessible to applications.
  • Said data can include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.
  • the view system includes visual controls, such as controls that display text, controls that display pictures, etc.
  • a view system can be used to build applications.
  • the display interface can be composed of one or more views.
  • a display interface including a text message notification icon may include a view for displaying text and a view for displaying pictures.
  • the phone manager is used to provide communication functions of the electronic device 100 .
  • call status management including connected, hung up, etc.
  • the resource manager provides various resources to applications, such as localized strings, icons, pictures, layout files, video files, etc.
  • the notification manager allows applications to display notification information in the status bar, which can be used to convey notification-type messages and can automatically disappear after a short stay without user interaction.
  • the notification manager is used to notify download completion, message reminders, etc.
  • the notification manager can also be notifications that appear in the status bar at the top of the system in the form of charts or scroll bar text, such as notifications for applications running in the background, or notifications that appear on the screen in the form of conversation windows. For example, text information is prompted in the status bar, a beep sounds, the electronic device vibrates, the indicator light flashes, etc.
  • Android Runtime includes core libraries and virtual machines. Android Runtime is responsible for the scheduling and management of the Android system.
  • the core library contains two parts: one is the functional functions that need to be called by the Java language, and the other is the core library of Android.
  • the application layer and application framework layer run in virtual machines.
  • the virtual machine executes the java files of the application layer and application framework layer into binary files.
  • the virtual machine is used to perform object life cycle management, stack management, thread management, security and exception management, and garbage collection and other functions.
  • System libraries can include multiple functional modules. For example: surface manager, media library Libraries), three-dimensional graphics processing libraries (for example: OpenGL ES), two-dimensional graphics engines (for example: SGL), etc.
  • the surface manager is used to manage the display subsystem and provides the fusion of 2D and 3D layers for multiple applications.
  • the media library supports playback and recording of a variety of commonly used audio and video formats, as well as static image files, etc.
  • the media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.
  • the 3D graphics processing library is used to implement 3D graphics drawing, image rendering, composition, and layer processing.
  • 2D Graphics Engine is a drawing engine for 2D drawing.
  • the kernel layer is the layer between hardware and software.
  • the kernel layer contains at least display driver, camera driver, audio driver, and sensor driver.
  • each electronic device includes but is not limited to and can be divided into: main device, slave devices and out-of-loop devices. in:
  • Main device includes the device currently held by the user.
  • the user can perform operations on the main device to initiate multi-device collaboration with other devices. Therefore, the main device is generally also the device that initiates multi-device collaboration.
  • the multi-device collaboration method provided by the embodiment of the present application can be implemented in the main device.
  • Slave devices include devices located near the master device and logged in with the same account as the master device.
  • the master device and the slave device are generally electronic devices produced by the same manufacturer.
  • the master device can be a mobile phone produced by manufacturer A
  • the slave device can be a tablet computer produced by manufacturer A, etc.
  • the account used to log in to the master device and the slave device can be the account applied by the user from the device manufacturer.
  • Out-of-loop devices include devices produced by the same device manufacturer as the main device but not logged into the same account as the main device; also include devices produced by other specific manufacturers; and include specific types of devices produced by other manufacturers, such as: Large screen devices, etc.
  • the multi-device collaboration method provided by the embodiment of the present application can be implemented in the main device.
  • the master device may perform steps of the multi-device collaboration method in response to one or more operations performed by the user.
  • Figure 3 is a first flow chart of a multi-device collaboration method provided by an embodiment of the present application.
  • the method may include the following steps S101-S103:
  • Step S101 In response to user operation, the master device displays a multi-device collaboration card.
  • the multi-device collaboration card includes the device identification of at least one slave device.
  • the multi-device collaboration card can be located on the control center page of the main device, or on the negative screen page of the main device, or on the home screen page of the main device, or on other pages.
  • the embodiment of the present application does not specifically limit the location of the multi-device collaboration card.
  • the main device may display the control center page in response to the first operation performed by the user on any page.
  • the first operation may be an operation of the user's finger sliding down on the top edge of the display screen, an operation of the user's finger sliding upward on the bottom edge of the display screen, or other operations.
  • the notification center page will be called. If the user's finger slides down on the top edge of the display screen, Sliding down the right half of the edge will bring up the control center page, which are all within the protection scope of the embodiments of this application.
  • the master device in order to determine whether there are slave devices around the master device, before step S101 and/or after step S101, can send Bluetooth broadcasts to the surroundings at a preset time interval (ie: a preset cycle). , to search for slave devices that may exist around it.
  • the Bluetooth broadcast can be a classic Bluetooth broadcast or a Bluetooth low energy (Bluetooth Low Energy, BLE) broadcast, which is not limited in the embodiments of this application.
  • BLE Bluetooth Low Energy
  • the slave device can send a broadcast message to the master device after receiving the Bluetooth broadcast from the master device. If the master device receives a response message from the slave device, it can determine the existence of the slave device.
  • the master device has searched for one or more slave devices
  • the master device has not searched for the slave device and is currently searching for the slave device;
  • the master device does not search for the slave device and is not currently searching for the slave device.
  • the main device displays the control center page in response to a user operation
  • the content displayed in the multi-device collaboration card may be different.
  • FIG. 4A is a first schematic diagram of the control center page provided by the embodiment of the present application.
  • control center page 200 may include one or more function switch buttons, such as: Wi-Fi switch button 201, Bluetooth switch button 202, flashlight switch button 203, vibration switch button 204 , mute switch button 205, etc.
  • function switch buttons such as: Wi-Fi switch button 201, Bluetooth switch button 202, flashlight switch button 203, vibration switch button 204 , mute switch button 205, etc.
  • the control center page 200 may also include one or more sliding controls, such as the sliding control 206 for adjusting the brightness of the display screen.
  • the sliding control 206 for adjusting the brightness of the display screen.
  • 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: the close icon 212 of the multi-device collaboration card 210, and the multi-device collaboration card 210. Entry button 213 of the collaboration main page.
  • the specific content of the multi-device collaboration main page will be explained in detail below.
  • the name of the above-mentioned card is just an example of this application.
  • the function of multi-device collaboration can also be named by other names, which is not limited by this application.
  • it can be: "Glory Internet”, “Hyper Terminal”, etc. Therefore, the card name 211 displayed in the multi-device collaboration card 210 may be "Honor Internet”, “Hyper Terminal”, etc.
  • the multi-device collaborative home page can also be called the Honor Internet home page and the Hyper Terminal home page.
  • the master device can directly search for one or more slave devices when displaying the control center page 200.
  • the search results are displayed in the multi-device collaboration card 210 .
  • the multi-device collaboration card 210 may include the device identifiers 214 of one or more slave devices that have been searched by the master device.
  • the device identification 214 of the slave device may be a graphical identification, such as an icon, or other quasi-physical elements.
  • the icon of the slave device may be used as the device identifier 214 of the slave device, or a bubble-shaped element wrapping the icon of the slave device may be used as the device identifier 214 of the slave device. This is not limited in the embodiment of the present application.
  • the user can know which slave devices exist around the current master device that can perform multi-device collaboration, as well as the type of each slave device. For example: if the device identifier 214 of the slave device is a tablet computer icon, the user can understand that the slave device is a tablet computer; if the device identifier 214 of the slave device is a large screen device icon, the user can understand that the slave device is a large screen computer. device; if the device identifier 214 of the slave device is a mobile phone icon, the user can understand that the slave device is a mobile phone.
  • the multi-device collaboration card 210 may also include the device name 215 of each slave device.
  • the device name may be displayed in conjunction with its corresponding device identifier 214.
  • the device name 215 may be displayed above, below, or in other positions of its corresponding device identifier 214.
  • the device name 215 may be the product name of the slave device, for example: 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, the Honor smart screen in the living room, etc. The embodiment of the present application does not limit this.
  • Figure 4B is a second schematic diagram of the control center page provided by the embodiment of the present application.
  • the master device does not search for the slave device when displaying the control center page 200, and is currently searching for the slave device, then when the master device displays the control center page 200, it can
  • the page elements that are searching for slave devices are displayed in the multi-device collaboration card 210 .
  • the multi-device collaboration card 210 may include an animated logo with a search pattern 216, and the animated logo can quasi-physically represent the state that the master device is searching for the slave device.
  • the master device searches for the slave device, it can display the device ID and device name of the searched slave device in the multi-device collaboration card 210.
  • the multi-device collaboration card 210 will be displayed as shown in Figure 4A style.
  • the master device may search for different slave devices one after another.
  • the master device may display the device ID and device name of the slave device in the multi-device collaboration card 210 each time it searches for a slave device.
  • the device identifiers of the multiple slave devices can be arranged in sequence according to the order in which they are searched.
  • the master device searches for a slave device, if it searches for a slave device, it does not need to immediately display the device ID and device name of the slave device. Instead, it waits until the search is completed (for example, the search timeout), and then all searches are The device identification and device name of the obtained slave device are displayed in the multi-device collaboration card 210 .
  • Figure 4C is the third schematic diagram of the control center page provided by the embodiment of the present application.
  • the master device does not search for the slave device when displaying the control center page 200, and is not currently searching for the slave device, then when the master device displays the control center page 200 , page elements for guiding users to actively search for slave devices can be displayed in the multi-device collaboration card 210.
  • the multi-device collaboration card 210 may include a search button 217 and prompt information 218 for guiding the user to click the search button 217 to actively search for slave devices.
  • the master device When the master device detects that the user clicks the 11 search button, it can respond to the user's click operation and start searching for slave devices, such as sending Bluetooth broadcasts to the surroundings, and monitoring the slave devices' response messages to Bluetooth broadcasts. After the master device starts searching for slave devices, the multi-device collaboration card 210 can be changed to the style of Figure 4B.
  • the master device searches for the slave device, it can display the device ID and device name of the searched slave device in the multi-device collaboration card 210.
  • the multi-device collaboration card 210 will be displayed as shown in Figure 4A style.
  • Figure 4D is the fourth schematic diagram of the control center page provided by the embodiment of the present application.
  • the master device does not search for the 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, When the master device initially displays the control center page 200, it may not display the multi-device collaboration card 210. Among them, the main device displays the control center page 200 for the first time, including but not limited to the following scenarios:
  • Scenario 1 After the operating system is initialized, the master device displays the control center page 200 for the first time.
  • the main device is a brand new device.
  • the user After the main device is powered on for the first time, the user will perform initialization settings on the main device. After the initialization settings are completed, the user operates the main device and displays the control center page 200 for the first time.
  • Scenario 2 After the login account changes, the main device displays the control center page 200 for the first time. For example: After user A logs out his account from the main device, he hands the main device to user B. User B logs in a new account on the main device. After logging in with the new account, user B operates the main device first. The Control Center page is displayed 200 times.
  • Scenario 3 After the main device restores factory settings or clears data, the control center page 200 is displayed for the first time.
  • the control center page 200 does not include a multi-device collaboration card.
  • the chip 210 may include one or more function switch buttons, such as: Wi-Fi switch button 201, Bluetooth switch button 202, flashlight switch button 203, vibration switch button 204, mute switch button 205, etc. When the user clicks a switch button, the main device can turn on or off the corresponding function.
  • the control center page 200 may also include one or more sliding controls, such as the sliding control 206 for adjusting the brightness of the display screen.
  • the master device does not search for the 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 A potential user of multi-device collaboration, therefore, the main device can continue not to display the multi-device collaboration card 210, so that cards that are not needed by the user will not appear on the control center page 200 and avoid disturbing the user.
  • the master device can display the multi-device collaboration card 210 in the control center page 200.
  • the multi-device collaboration card 210 can include the card name 211 and one or more clickable elements, for example: multi-device collaboration The close icon 212 of the card 210, and the entry button 213 of the multi-device collaboration main page.
  • the master device displays the multi-device collaboration card 210 in the control center page 200 for the first time, then the master device can directly display the multi-device collaboration card 210 the next time it displays the control center page 200, wherein the slave device is searched according to the master device Of the three states, the multi-device collaboration card 210 may be in one of the styles shown in FIGS. 4A-4C.
  • the main device can also close the multi-device collaboration card 210 in response to the user's operation of clicking the close icon 212 in the multi-device collaboration card 210. If the user closes the multi-device collaboration card 210, the main device may not display the multi-device collaboration card 210 the next time it displays the control center page 200. Alternatively, the main device may determine that the number of times the user continuously closes the multi-device collaboration card 210 within the preset time period is greater than or equal to the first threshold; if it is greater than or equal to the first threshold, the main device will not display the control center page 200 next time.
  • Multi-device collaboration card 210 if it is less than the first threshold, the main device will continue to display the multi-device collaboration card 210 when the control center page 200 is displayed next time. For example: when the preset time is 24 hours (one day) and the first threshold is 2 times, if the user closes the multi-device collaboration card 210 twice within 24 hours, then the main device will display the control center page 200 next time , the multi-device collaboration card 210 is not displayed.
  • control center page 200 may also include an edit icon 207. If the user wants to restore the display of the multi-device collaboration card 210, he or she can click the edit icon 207 in the 18 control center. The main device may enter the editing page of the control center in response to the user's operation of clicking the editing icon 207 18 . In this way, the user can configure the content displayed in the control center on the editing page of the control center, for example, restore the display of the multi-device collaboration card 210, etc.
  • the main The device can resume displaying the multi-device collaboration card 210 when it searches for a slave device in the surrounding area. If the master device does not search for the slave device, the multi-device collaboration card 210 can be kept closed.
  • Step S102 In response to the user's operation in the multi-device collaboration card 210, the master device determines the target device from the at least one slave device, and initiates multi-device collaboration to the target device based on the first collaboration type.
  • Figure 5 is a first set of interaction example diagrams of a multi-device collaboration method provided by an embodiment of the present application.
  • the user wants to establish multi-device collaboration between the master device and a searched slave device, he or she can perform one or more preset steps on the device identification of the slave device in the multi-device collaboration card 210. Operation, for example: click on the device ID 214 of the slave device 12.
  • the master device may respond to the user's operation of clicking 12 on the device identification 214 of the slave device, determine the slave device as the target device, and initiate multi-device collaboration to the target device based on the first collaboration type.
  • 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.
  • the first collaboration type may be the default two The collaboration type of each device; if the master device and the target device are not establishing multi-device collaboration for the first time, the first collaboration type can be the collaboration type used by both parties last time they established multi-device collaboration, or it can be the default two devices. type of collaboration.
  • a default collaboration type can be preset between the main device and each type of electronic device, and the default collaboration types between the main device and different types of electronic devices can be different.
  • the default collaboration type can be multi-screen collaboration
  • the main device is a mobile phone and the target device is a large-screen device
  • the default collaboration type can be screen projection
  • the main device is PC
  • the target device is PC
  • 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.
  • Step S103 After establishing multi-device collaboration with the target device, the master device switches the device identifier of the target device to the collaboration identifier of the first collaboration type.
  • the collaboration logo 219 is similar to the device logo 214, and may also be a graphical logo, such as an icon, or other quasi-physical elements.
  • the main device can switch the device identification of the target device to the multi-screen collaboration identification; if the main device and the target device establish screen mirroring, the main device can switch the target device's device identification to the multi-screen collaboration identification.
  • the device identity switches to the screen mirroring identity. In this way, the user can intuitively understand the established collaboration type between the master device and the target device in the multi-device collaboration card 210 .
  • the type name 221 of the first collaboration type may also be displayed 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.
  • the type name 221 of the first collaboration type may be displayed adjacent to the device name 215 of the target device on the same line, or the first collaboration type
  • the type name 221 may be displayed in the same column adjacent to the device name 215 of the target device.
  • the main device can transfer the information of the Honor notebook in the multi-device collaboration card 210 to The device logo is switched to the multi-screen collaboration logo, and the type name "Multi-screen Collaboration" is added below the device name "Honor Notebook”. In this way, the user can intuitively know in the multi-device collaboration card 210 that the main device has established multi-screen collaboration with the Honor Pad.
  • the master device can display the device identification 214 of each slave device in a preset color, such as the first color, in the multi-device collaboration card 210 . If the master device and the target device establish multi-device collaboration based on the first collaboration type, the master device can display the collaboration logo 219 of the first collaboration type in the multi-device collaboration card 210 as another preset color, such as the second color. In this way, users can distinguish through different colors which slave devices have established multi-device collaboration with the master device and which slave devices have not established multi-screen collaboration with the master device.
  • the master device after the master device establishes multi-device collaboration with the target device, it can also disconnect the multi-device collaboration with the target device in response to the user's operation of clicking the collaboration identifier 219 of the first collaboration type 13. .
  • the collaboration identifier 219 of the first collaboration type can be switched back to the device identifier of the target device. In this way, the multi-device collaboration card 210 can be restored to the form before establishing multi-device collaboration.
  • the method provided by 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 identifiers of each slave device around the master device. In this way, the user can click on any slave device.
  • the operation of the device identification of the device allows the master device to establish multi-device collaboration with any slave device. It does not require the user to search for control entrances of various collaboration types in different user interfaces, which improves the user experience.
  • the main device may also display the multi-device collaboration main page in response to the user's operation on the multi-device collaboration card.
  • the content contained in the multi-device collaboration main page may be different. The following is done with reference to the attached figure. Illustrative illustration.
  • Figure 6 is a second set of interaction example diagrams of a multi-device collaboration method provided by an embodiment of the present application.
  • the user can perform the function on the device identification 214 of any slave device in the multi-device collaboration card 210. Long press 14 to operate.
  • the master device may display the multi-device collaboration main page 300 in response to a long press 14 operation performed by the user on the device identification 214 of any slave device.
  • the user wants to open the multi-device collaboration main page 300 , he can also perform a click operation on the entry button 213 in the multi-device collaboration card 210 .
  • the main device may display the multi-device collaboration main page 300 in response to the user's operation of clicking the 16 entry button 213 .
  • the multi-device collaboration main page 300 may include the device identification 301 of the master device and the device identification 214 of each slave device.
  • the device identification 301 of the main device may be located in the center area of the multi-device collaboration home page 300. For example, it may be located in the center, the lower center area, the center upper area, etc. of the multi-device collaboration home page 300. This application does not do this. limited.
  • the device identification 214 of the slave device may be distributed around the device identification 301 of the master device.
  • the device identification 301 of the main device is located in the lower center area of the multi-device collaboration main page 300 .
  • the device identification 214 of each slave device for example: the device identification of a tablet computer, the device identification of a large-screen device, the device identification of a PC, and the device identification of a mobile phone, may be distributed in a planetary shape around the device identification 301 of the master device.
  • the device identification 214 of the slave device may also be distributed above the device identification 301 of the master device, or distributed above the device identification 301 of the master device, etc. This application does not limit this implementation.
  • the device identification in the multi-device collaboration main page 300 and the device identification in the multi-device collaboration card 210 may adopt different visual styles.
  • the device identification in the multi-device collaboration card 210 may be composed of a device icon and a background color, while the device identification in the multi-device collaboration main page 300 may be a bubble element wrapping the device icon, or a bubble element wrapping the device icon, etc.
  • the device identification 301 of the master device and the device identification 214 of the slave device may be in different colors to facilitate user distinction.
  • the device identification 301 of the master device may be a blue bubble element
  • the device identification 214 of the slave device may be a white (or transparent) bubble element.
  • the device identification 301 of the master device and the device identification 214 of the slave device may be of different sizes to facilitate user distinction.
  • the size of the device identifier 301 of the master device may be larger than the size of the device identifier 214 of the slave device.
  • the multi-device collaboration main page 300 may also include the device name 215 of each slave device.
  • the device name 215 may be displayed in conjunction with its corresponding device identification 214.
  • the device name may be displayed next to its corresponding device identification 214. above, below, or elsewhere.
  • 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 , the Honor smart screen in the living room, etc., the embodiments of this application do not limit this.
  • Figure 7 is a third set of interaction example diagrams of a multi-device collaboration method provided by an embodiment of the present application.
  • the user can perform the function on the device identification 214 of any slave device in the multi-device collaboration card 210 Long press 14 to operate.
  • the master device may display the multi-device collaboration main page 300 in response to a long press 14 operation performed by the user on the device identification 214 of any slave device.
  • the main device and the target device have established multi-device collaboration
  • the user wants to open the multi-device collaboration main page 300, he can also execute the collaboration identifier 219 of any collaboration type in the multi-device collaboration card 210. Press and hold 15 to operate.
  • the main device may display the multi-device collaboration main page 300 in response to a long press 15 operation performed by the user on the collaboration identifier 219 of any collaboration type.
  • the master device and the target device have established multi-device collaboration
  • the user wants to open the multi-device collaboration main page 300 , he can also click the entry button 213 in the multi-device collaboration card 210 .
  • the main device may display the multi-device collaboration main page 300 in response to the user's operation of clicking the 16 entry button 213 .
  • the entry button multi-device collaboration main page 300 may include the collaboration identifier 219 between the master device and the target device and the device identifier 214 of each slave device.
  • the collaboration logo 219 may be located in the central area of the multi-device collaboration main page 300, for example, in the center, lower center area, upper center area, etc. of the multi-device collaboration main page 300. This application does not limit this.
  • the device identification 214 of the slave device may be distributed at the periphery of the collaborative identification.
  • the adjacent position such as above or below the collaboration identifier 219 may also include the device name 215 of the target device and the type name 402 of the collaboration type.
  • the collaboration logo 219 may be located in a lower center area of the multi-device collaboration main page 300 .
  • the device identification 214 of each slave device for example: the device identification of a tablet computer, the device identification of a large-screen device, the device identification of a PC, and the device identification of a mobile phone may be distributed in a planetary shape around the collaborative identification.
  • the collaboration logo 219 and the device logo 214 of the slave device may be in different colors to facilitate user distinction.
  • the collaboration logo 219 may be a blue bubble element
  • the device logo 214 of the slave device may be a white (or transparent) bubble element.
  • the collaboration logo 219 and the device logo 214 of the slave device may be of different sizes to facilitate user distinction.
  • the size of the collaborative identifier 219 may be larger than the size of the device identifier 214 of the slave device.
  • Figure 8 is a second flow chart of a multi-device collaboration method provided by an embodiment of the present application.
  • Figures 9A-9D are a fourth set of interaction example diagrams of a multi-device collaboration method provided by embodiments of the present application.
  • the method may include the following steps S201-S203:
  • Step S201 The master device responds to an operation performed by the user on the multi-device collaboration main page, determines the target device, and establishes multi-device collaboration with the target device based on the first collaboration type.
  • the master device when the master device has not established multi-device collaboration with a slave device, if the user wants to establish multi-device collaboration between the master device and a slave device, he can go to the multi-device collaboration main page 300 , drag 21 the device identification 214 of the slave device toward the device identification 301 of the master device.
  • the master device may determine the slave device as the target device in response to the user's operation of dragging 21 the device identifier 214 of the slave device.
  • the main device When the user drags the device identification 214 of the target device into contact with the device identification 301 of the main device, the main device initiates multi-device collaboration to the target device based on the first collaboration type.
  • the master device can display on the multi-device collaboration main page 300 that the bubble elements of the master device and the bubble elements of the target device are merging, so as to visualize the multi-device collaboration being established. Status feedback to the user.
  • the device identifier 301 of the master device in the multi-device collaboration main page 300 can be switched to the collaboration identifier 401 of the first collaboration type, for example, the master device bubble yuan
  • the element is merged with the bubble element of the target device to form the first synergistic type of bubble element.
  • the master device may also display the device name 215 of the target device and the type name 402 of the first collaboration type at a nearby position such as above or below the collaboration identification 401 of the first collaboration type.
  • 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. For example, if the main device and the target device establish multi-device collaboration for the first time, then the first collaboration type may be the default collaboration type of two devices. If the main device and the target device do not establish multi-device collaboration for the first time, then the first collaboration type may be the default collaboration type of two devices.
  • a collaboration type may be the collaboration type used by both parties when they last established multi-device collaboration, or it may be the default collaboration type of the two devices.
  • Step S202 The master device displays a type switching card on the multi-device collaboration main page.
  • the type switching card 310 may be displayed at an adjacent position such as above or below the collaboration logo 401 of the first collaboration type, which is not limited in the embodiment of the present application.
  • the main device can directly display the type switching card on the multi-device collaboration main page without requiring the user to before performing any operations.
  • the master device can display the type switching card while successfully establishing multi-device collaboration with the target device; or the master device can also display the type switching card immediately after successfully establishing multi-device collaboration with the target device.
  • the type switching card 310 may include collaboration identifiers of one or more collaboration types supported by the master device and the target device.
  • the master device may display the collaboration identifier of each collaboration type supported by the master device and the target device in the type switching card 310, or may display the collaboration identifiers of some of the collaboration types supported by the master device and the target device in the type switching card 310, for example: Only collaboration identifiers 403 of other collaboration types other than the collaboration identifier 401 of the first collaboration type are displayed. The embodiments of the present application do not limit this.
  • the types of collaboration supported by the mobile phone and the PC may include multi-screen collaboration and super keyboard and mouse. Then, after the mobile phone and the PC establish multi-screen collaboration, the type switching card 310 may include the multi-screen collaboration logo and the super keyboard and mouse logo.
  • the type switching card 310 contains both the collaboration identifier 401 of the first collaboration type and the collaboration identifiers 403 of other collaboration types, then the collaboration identifier 401 of the first collaboration type and the collaboration identifiers 403 of other collaboration types
  • the logo 403 can be displayed in different colors to facilitate user distinction.
  • 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, he can click 23 disconnect button 311. The master device may respond to the user's operation of clicking 23 the disconnect button 311, disconnect the multi-device collaboration with the target device, restore the collaboration identity of the first collaboration type to the device identity 301 of the master device, and change the collaboration identity of the target device to the master device's device identity 301. The device identification 214 is restored to its original position.
  • the main device can 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 Figure 9A.
  • the type switching card 310 may include the type identifier of the supported collaboration type and the disconnect button 311, or may only include the disconnect button. 311, the embodiment of this application does not limit this.
  • Step S203 In response to the user's operation on the type switching card, the master device determines the second collaboration type, and switches the collaboration type between the master device and the target device from the first collaboration type to the second collaboration type.
  • the second collaboration type may be one of multiple collaboration types included in the type switching card 310 .
  • the master device may determine this 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 Second type of collaboration.
  • the master device can directly initiate a handover request to the target device based on the second collaboration type without interrupting multi-device collaboration with the target device, so that the master device and the target device switch to 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 of the second collaboration type.
  • the master device can also disconnect multi-device collaboration with the target device first, and then initiate multi-device collaboration with the target device again based on the second collaboration type, so that the master device and the target device can re-establish multi-device collaboration based on the second collaboration type.
  • the main device may close the type switching card 310 if it detects that the user has not performed any operations on the type switching card 310 within a preset period of time.
  • the preset time period may be 3 seconds, 5 seconds, etc., which is not limited in the embodiments of the present application.
  • the main device After the main device closes the type switching card 310, if the user wants the main device to display the type switching card 310 again, he can click the collaboration logo 401 of the first collaboration type (or the second collaboration type) on the multi-device collaboration main page 300, The main device may redisplay the type switching card 310 in response to the user's click operation.
  • the main device and the target device 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, and then the user can select the desired collaboration type in the control center of the main device. Based on the user's selection, the main device can switch from the preset collaboration type to the collaboration type that the user expects to use, which improves the user experience.
  • Figures 10A-10D are a fifth set of interaction example diagrams of a multi-device collaboration method provided by embodiments of the present application. 10A-10D, taking the master device as a tablet and the slave device as a PC as an example, the interaction scenarios corresponding to steps S201-S203 of the multi-device collaboration method provided by the embodiment of the present application will be exemplified.
  • the tablet computer can present the effect that its bubble element 432 is merging with the bubble element 431 of the PC on the multi-device collaboration main page 300 to visualize the status of multi-device collaboration being established. Feedback to users.
  • the type switching card 310 may include collaboration identifiers of one or more collaboration types supported by the tablet computer and the PC, such as: screen mirroring identifier 461, screen extension identifier 462, and super keyboard and mouse identifier 463.
  • the user wants to switch the collaboration type between the tablet and the PC, for example, to switch the collaboration type between the tablet and the PC from screen mirroring to super keyboard and mouse, he can click the 28 super keyboard and mouse logo 463 in the type switching card 310 .
  • the tablet computer can switch the type of collaboration between the tablet computer and the PC from screen mirroring to super keyboard and mouse in response to user operations.
  • the multi-device collaboration main page 300 can be The bubble element 433 of screen mirroring is switched to the bubble element 434 of Super Keyboard and Mouse.
  • 11A-11D are a sixth set of interaction example diagrams of a multi-device collaboration method provided by embodiments of the present application.
  • the user wants to establish multi-device collaboration between the PC and the tablet, he can drag the bubble element 441 of the tablet to the bubble element 442 of the PC on the multi-device collaboration main page 300.
  • Direction drag29 When the user drags the bubble element 441 of the tablet into contact with the bubble element 442 of the PC, the PC initiates a default type of multi-device collaboration, such as screen mirroring, to the tablet.
  • the PC can present the effect that its bubble element 442 is merging with the bubble element 441 of the tablet on the multi-device collaboration main page 300 to visualize the multi-device collaboration status being established. Feedback to users.
  • the bubble element 442 of the PC and the bubble element 441 of the tablet can be fused to form the bubble element 443 of the screen mirroring, and the type switch is displayed below the multi-screen collaboration logo 401 Card 310.
  • the type switching card 310 may include collaboration identifiers of one or more collaboration types supported by the PC and the tablet, such as: screen mirroring identifier 461, screen extension identifier 462, and super keyboard and mouse identifier 463.
  • the user wants to switch the collaboration type between PC and tablet, for example, to switch the collaboration type between PC and tablet from multi-screen collaboration to super keyboard and mouse, he can click the 31 super keyboard and mouse logo in the type switching card 310 463.
  • the main device can switch the type of collaboration between the PC and the tablet from screen mirroring to super keyboard and mouse in response to user operations.
  • the bubble element 443 of the screen mirroring in the multi-device collaboration home page 300 can be switched to the bubble element 444 of the super keyboard and mouse.
  • Figures 12A-12D are a seventh set of interaction example diagrams of a multi-device collaboration method provided by embodiments of the present application.
  • folding screen mobile phones can usually work in two states, one is the body folded state, and the other is the body unfolded state.
  • folding screen mobile phone when the folding screen mobile phone is in the folded state, it is equivalent to a traditional mobile phone.
  • the types of collaboration it supports with the PC are the same as those of traditional mobile phones. For example, they can include: multi-screen collaboration and super keyboard and mouse; When the screen mobile phone is in the unfolded state, it is a new product form compared to the traditional mobile phone.
  • the types of collaboration it supports with the PC are different from the traditional mobile phones. For example, it can include: multi-screen collaboration, screen mirroring, Screen extension, super keyboard and mouse.
  • the folding screen phone can drag 32 the bubble element 451 of the PC toward the bubble element 452 of the folding screen mobile phone on the multi-device collaboration main page 300.
  • the folding screen phone initiates a default type of multi-device collaboration, such as multi-screen collaboration, to the PC.
  • the folding screen mobile phone can show the effect that its bubble element 452 is merging with the bubble element 451 of the PC on the multi-device collaboration home page 300, so as to visualize the multi-device collaboration being established. Status feedback to the user.
  • the bubble element 452 of the folding screen mobile phone and the bubble element 451 of the PC can be merged to form the multi-screen collaboration bubble element 453, and the multi-screen collaboration mark 401
  • a type switching card 310 is displayed below.
  • the type switching card 310 may include collaboration logos of one or more collaboration types supported by folding screen mobile phones and PCs, such as: screen mirroring logo 461, screen extension logo 462, super keyboard and mouse logo 463, multi-screen collaboration logo 464.
  • the user wants to switch the collaboration type between the folding screen mobile phone and the PC, for example, to switch the collaboration type between the folding screen mobile phone and the PC from multi-screen collaboration to super keyboard and mouse, he can click the 33 super key in the type switching card 310 Rat logo 463.
  • the main device can respond to user operations and switch the type of collaboration between the folding screen mobile phone and the PC from multi-screen collaboration to super keyboard and mouse.
  • the multi-screen collaboration bubble element 453 in the multi-device collaboration main page 300 can be switched to the super keyboard and mouse bubble element 454.
  • 13A-13C are diagrams illustrating the opening and closing methods of the automatic collaborative service according to the embodiment of the present application.
  • the multi-device collaboration main page 300 can also include a setting button 302, and the setting button 302 can be set at any position on the multi-device collaboration main page 300, for example, multi-device collaboration The upper right corner of the main page 300.
  • the setting page 400 may include, for example, a collaboration service list 410 and a slave device list 420 .
  • the collaborative service list 410 may include one or more settable collaborative service options, such as super connection, super call, super notification, super keyboard and mouse, etc.; and the status of each collaborative service, such as enabled or closed.
  • the slave device list may include the names and types of nearby slave devices that have been searched by the mobile phone, as well as the names and types of devices that have established too many device collaborations with the mobile phone.
  • the user wants to set the service status of a certain collaborative service, he can click the collaborative service option 25 in the collaborative service list 410.
  • the mobile phone can respond to the user's click 25 operation and enter the sub-page 500 of the collaborative service.
  • the sub-page 500 may include, for example, a switch button 501 of the collaborative service.
  • the user can turn on or off the collaborative service by clicking 26 switch button 501.
  • the mobile phone can enter the sub-page 500 of Super Call.
  • the sub-page 500 of Super Call can include the function description information 502 of Super Call, and the Super Call sub-page 500.
  • the call switch button 501 When the switch button 501 is in the on state, if the user clicks the 26 switch button 501, the super call service can be turned off. When the switch button 501 is in the off state, if the user clicks the 26 switch button 501, the super call service can be turned on.
  • users can directly enter the multi-device collaboration setting page from the multi-device collaboration main page to control the opening and closing of the automatic collaboration service, which improves the user experience.
  • the master device may be in the following three states at a certain time:
  • the master device has not established multi-device collaboration with other devices (abbreviation: the master device has not collaborated);
  • State B The master device and the slave device are performing multi-device collaboration
  • State C The main device and the device outside the ring are performing multi-device collaboration.
  • state B and state C can be abbreviated as: the main device is not coordinated.
  • the slave device may be in the following three states at a certain time:
  • the slave device has not established multi-device collaboration with other devices (abbreviation: the slave device has not collaborated);
  • the slave device is in multi-device collaboration with other slave devices
  • state b and state c can be referred to as: the slave device is not coordinated.
  • Scenario 1 Neither the master device nor the target device cooperates.
  • Scenario 2 The main device is coordinated, but the target device is not coordinated.
  • Scenario 2 can include the following two sub-scenarios:
  • Sub-scenario 1 The master device and other slave devices are performing multi-device collaboration
  • Sub-scenario 2 The main device and the device outside the ring are performing multi-device collaboration.
  • Scenario 3 The main device is not coordinated and the target device is coordinated.
  • Scenario three can include the following two sub-scenarios:
  • Sub-scenario 3 The target device and other slave devices are performing multi-device collaboration
  • Sub-scenario 4 The target device and the device outside the ring are performing multi-device collaboration
  • Scenario 4 Master device collaboration and slave device collaboration.
  • Scenario four can include the following four sub-scenarios:
  • Sub-scenario 5 The master device is performing multi-device collaboration with other slave devices, and the target device is performing multi-device collaboration with other slave devices;
  • Sub-scenario 6 The master device is performing multi-device collaboration with other slave devices, and the target device is performing multi-device collaboration with devices outside the ring;
  • Sub-scenario 7 The master device and the device outside the ring are performing multi-device collaboration, and the target device and other slave devices are performing multi-device collaboration;
  • Sub-scenario 8 The main device and the device outside the ring are performing multi-device collaboration, and the target device and the device outside the ring are performing multi-device collaboration.
  • the main device and the target device can respond in different ways.
  • the following is a detailed explanation with some examples.
  • the multi-device collaboration method may include the following steps: in response to the user dragging the device identification of the target device, the main device causes the device identification of the target device to contact the device identification of the main device, based on the first collaboration type, and The target device establishes multi-device collaboration, and displays the type switching card 310 on the multi-device collaboration main page 300 .
  • Figure 14 is an interactive example diagram of scenario 1 of the multi-device collaboration method provided by the embodiment of the present application.
  • the main device as a mobile phone
  • the target device as a PC (for example: Honor notebook)
  • the first collaboration type as multi-screen collaboration.
  • the user wants to establish multi-device collaboration between the mobile phone and the PC, he can drag 61 the bubble element 601 of the PC toward the bubble element 602 of the mobile phone on the multi-device collaboration main page.
  • the mobile phone initiates multi-screen collaboration to the PC.
  • the mobile phone can present the fusion effect of the bubble element 602 of the mobile phone and the bubble element 601 of the PC on the multi-device collaboration main page, so as to visually feed back to the user the status of multi-device collaboration being established.
  • the bubble element 602 of the mobile phone is completely integrated with the bubble element 601 of the PC to form a multi-screen collaboration bubble element 603.
  • the mobile phone can also display the PC's device name "Honor Smart Screen” and the collaboration type "Multi-screen Collaboration” above the multi-screen collaboration bubble element 603 (or at other nearby locations).
  • the mobile phone can also display the type switching card 310 below (or at other nearby locations) the multi-screen collaborative bubble element 603.
  • the type switching card 310 please refer to the content recorded above with respect to Figure 9C, which will not be repeated here. .
  • the first case is that the ongoing multi-device collaboration between the master device and other slave devices does not support simultaneous access of three devices.
  • the ongoing multi-device collaboration between the master device and other slave devices is other collaboration types except super keyboard and mouse;
  • the second situation is the ongoing multi-device communication between the master device and other slave devices.
  • Device collaboration supports simultaneous access of three devices, such as super keyboard and mouse.
  • the collaboration type that does not support simultaneous access by three devices is called the third collaboration type, and the multi-device collaboration established based on the third collaboration type is called the first multi-device collaboration; the collaboration type that supports simultaneous access by three devices is called the first multi-device collaboration.
  • the entered collaboration type is called the fourth collaboration type, and the multi-device collaboration established based on the fourth collaboration type is called the second multi-device collaboration.
  • the multi-device collaboration method may include the following steps: when the master device and the first slave device establish the first multi-device collaboration, in response to the user dragging the device identification of the target device, the device identification of the target device is aligned with the first slave device. For operations in contact with the collaboration identifier of the third collaboration type, a switching inquiry card is displayed. The switching card is used to ask the user whether to switch the collaborative device.
  • Figure 15 is a first interaction example diagram of sub-scenario 1 of a multi-device collaboration method provided by the embodiment of the present application.
  • the master device as a mobile phone
  • the first slave device as a tablet (for example: Honor PAD)
  • the target device as a PC (for example: Honor notebook)
  • the third collaboration type as multi-screen collaboration.
  • the multi-device collaboration main page can display the multi-screen collaboration bubble element 611. If the user wants to establish multi-device collaboration between a mobile phone and a PC, he or she can drag 62 the bubble element 612 of the PC toward the bubble element 611 of multi-screen collaboration on the multi-device collaboration main page.
  • the mobile phone displays the bubble element 612 of the Honor notebook and the bubble element 613 of the mobile phone on the multi-device collaboration main page.
  • the effect is a fusion state, and the switching inquiry card 710 is displayed.
  • 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?".
  • 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 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 screen collaboration, 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.
  • the switching inquiry card may also include a do not disturb option 714.
  • the do not disturb option 714 may include prompt information for guiding the user to select and uncheck it, such as "Don't 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 directly responds to the user's operation. For example, if the user moves the PC's bubble element 612 to the multi-screen collaboration bubble element 611 By dragging in the direction and making contact with the multi-screen collaboration bubble element 611, the mobile phone can directly end the multi-screen collaboration with the tablet and establish multi-device collaboration with the PC.
  • 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 state, in response to the user dragging the device identification of the target device, the device identification of the target device is aligned with the first slave device. The operation of contacting the collaboration identifier of the fourth collaboration type adds the target device to the second multi-device collaboration.
  • Figure 16 is a second interaction example diagram of sub-scenario 1 of a multi-device collaboration method provided by the embodiment of the present application.
  • 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)
  • the fourth collaboration type as super keyboard and mouse.
  • the multi-device collaboration homepage can display the bubble element 621 of Super Keyboard and Mouse. If the user wants to add the tablet computer to the Super Keyboard and Mouse, he can drag 64 the bubble element 622 of the tablet computer in the direction of the bubble element 621 of the Super Keyboard and Mouse on the multi-device collaboration main page.
  • the mobile phone When the user drags the bubble element 622 of the tablet computer to contact the bubble element 621 of the super keyboard and mouse, and then lifts his finger, the mobile phone initiates the super keyboard and mouse to the tablet computer. At the same time, the mobile phone can present the fusion effect of the bubble element 621 of the super keyboard and mouse and the bubble element 622 of the tablet in the multi-device collaborative home page to form a fusion effect. Visually feed back to the user the status of multi-device collaboration being established. When the tablet computer successfully joins the super keyboard and mouse, the bubble element 622 of the tablet computer 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 "Honor PAD" above the bubble element 621 of the super keyboard and mouse (or at other nearby locations).
  • the multi-device collaboration method may include the following steps: when the master device establishes multi-device collaboration with an out-of-loop device, in response to the user dragging the device identification of the target device, the device identification of the target device is aligned with the device identification of the target device.
  • Multi-device collaboration synergy identifies the contact operation and displays the switching inquiry card. The switching card is used to ask the user whether to switch the collaborative device.
  • Figure 17 is an interaction example diagram of sub-scenario 2 of a multi-device collaboration method provided by the embodiment of the present application.
  • the multi-device collaboration main page may display the multi-screen collaboration bubble element 631.
  • the user wants to establish multi-device collaboration between the mobile phone and tablet 1, he can drag 65 the bubble element 632 of tablet 1 toward the bubble element 631 of multi-screen collaboration on the multi-device collaboration main page.
  • the mobile phone displays the bubble element 632 of tablet 1 and the bubble of the mobile phone on the main page of multi-device collaboration.
  • the element 633 has the effect of a fusion state, and the switching inquiry card 720 is displayed.
  • the switching inquiry card 720 is similar to the switching inquiry card 710 shown in FIG. 15 and will not be described again here. If the user clicks 66 "OK" button 722, the mobile 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 mobile phone last Computer 1 has established multi-screen collaboration. Then, if the user clicks 66 "OK” button 722, the mobile phone will establish multi-screen collaboration with tablet 1. If the user clicks the "Cancel" button 723, the mobile phone will continue to maintain the multi-screen collaboration state with the tablet 2.
  • the multi-device collaboration method may include the following steps: 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 responds to the user dragging the target device
  • the device identification is an operation that brings the device identification of the target device into contact with the collaboration identification of multi-device collaboration, and displays the switching inquiry card.
  • the switching card is used to ask the user whether to switch the collaborative device.
  • Figure 18 is a first interaction example diagram of scenario three of a multi-device collaboration method provided by an embodiment of the present application.
  • the mobile phone can add a status identifier 642 to the PC's bubble element 641 on the multi-device collaboration main page.
  • the status indicator 642 may be, for example, a graphic icon located at the lower right corner of the bubble element 641 of the PC (it may also be at other locations). In this way, through the status identification, the user can know that the PC is currently performing multi-device collaboration with other devices except the mobile phone.
  • the user wants to establish multi-device collaboration between the mobile phone and the PC, he can drag 67 the bubble element 641 of the PC toward the bubble element 643 of the mobile phone on the multi-device collaboration main page.
  • the mobile phone displays the PC's bubble element 641 and the mobile phone's bubble element 643 in a fused state on the multi-device collaboration main page. The effect is, and the switching inquiry card 730 is displayed.
  • the switching inquiry card 730 is similar to the switching inquiry card 710 shown in FIG. 15 and will not be described again here. If the user clicks 68 "OK" button 732, the mobile phone will end the multi-device collaboration between the PC and other slave devices or out-of-loop devices, and establish multi-device collaboration with the PC based on the default or last used collaboration type. For example: if the mobile phone Once multi-screen collaboration is established with the PC, then, if the user clicks 68 the "OK" button 732, the mobile phone will establish multi-screen collaboration with the PC, and cut the mobile phone's bubble element 643 into a multi-screen collaboration bubble element 644. If the user clicks the "Cancel" button 733, the PC and other slave devices or devices outside the ring will continue to maintain a multi-device collaboration state.
  • Figure 19 is a second interaction example diagram of scenario three of a multi-device collaboration method provided by the embodiment of the present application.
  • the master device can respond to The user drags the device identification of the target device to join the multi-device collaboration currently established on the target device.
  • the mobile phone can add a super keyboard and mouse status indicator 645 to the bubble element 641 of the PC in the multi-device collaboration home page.
  • the status indicator 645 may be, for example, a graphic icon located at the lower right corner of the bubble element 641 of the PC (it may also be at other locations). In this way, through the status identification, the user can know that the PC is currently establishing a super keyboard and mouse with other devices.
  • the user wants to add the mobile phone to the super keyboard and mouse he can drag 67 the bubble element 641 of the PC toward the bubble element 643 of the mobile phone on the multi-device collaboration main page.
  • the mobile phone displays the PC's bubble element 641 and the mobile phone's bubble element 643 in a fused state on the multi-device collaboration main page. The effect is to visually feedback to the user the status of multi-device collaboration being established.
  • the bubble element 643 of the mobile phone is completely integrated with the bubble element 641 of the PC to form the bubble element 646 of the super keyboard and mouse.
  • the multi-device collaboration method may include the following steps: When both the master device and the target device establish multi-device collaboration with other slave devices or devices outside the ring, the master device responds to the user dragging the device identifier of the target device, so that the target device When the device identifier of the device is in contact with the collaboration identifier of multi-device collaboration, a switching inquiry card is displayed. The switching card is used to ask the user whether to switch the collaborative device.
  • Figure 20 is an interactive example diagram of scenario four of a multi-device collaboration method provided by an embodiment of the present application.
  • the mobile phone takes the main device as a mobile phone and the target device as a PC (for example: Honor notebook).
  • the mobile phone will display the collaboration identification of its currently established multi-device collaboration on the main multi-device collaboration page. For example, if the mobile phone is currently connected with a tablet ( For example: Honor Pad) establishes multi-screen collaboration, then the bubble element 651 of multi-screen collaboration can be displayed on the main page of multi-device collaboration.
  • 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 performing multi-device collaboration with other devices other than the mobile phone. .
  • the user wants to establish multi-device collaboration between a mobile phone and a PC, he or she can drag 69 the bubble element 652 of the PC toward the bubble element 651 of multi-screen collaboration on the multi-device collaboration main page.
  • the mobile phone displays the PC's bubble element 652 and the mobile phone's bubble element 653 in the multi-device collaboration main page. The effect of the fusion state, and the switch query card 740 is displayed.
  • the switching inquiry card 740 is similar to the switching inquiry card shown in FIG. 15 and will not be described again here. If the user clicks 71 "OK" button 742, 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 between the PC and other slave devices or devices outside the ring. Based on the default or upper The collaboration type used once establishes multi-device collaboration with the PC. For example: if the mobile phone established multi-screen collaboration with the PC last time, then if the user clicks 71 "OK" button 742, 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 a multi-device collaboration state with other slave devices or devices outside the ring.
  • the master device when the master device and/or the slave device have established multi-device collaboration, the master device can respond to the user's operation on the multi-device collaboration main page and adopt different methods according to different scenarios.
  • the policy adds or switches devices participating in multi-device collaboration, improving the user experience.
  • Figure 21 is another interactive example diagram of a multi-device collaboration method provided by an embodiment of the present application.
  • the master device can display collaboration status information 810 of the slave device, such as "XXX is collaborating with XXX on multiple screens.”
  • the collaboration status information 810 can disappear on its own after being displayed for a period of time, thereby not affecting the multi-device collaboration main page 300 displaying other information.
  • the user when the slave device has established multi-device collaboration with other slave devices or out-of-loop devices, the user can view the multi-device collaboration information of the slave device on the multi-device collaboration main page, which improves the user experience. Use experience.
  • Figure 22 is another interactive example diagram of a multi-device collaboration method provided by an embodiment of the present application.
  • the master device can also add a status identifier 642 to the device identifier of the slave device in the multi-device collaboration card 210.
  • the status identifier may be, for example, a graphic icon located at the lower right corner of the device identifier 214 of the slave device (it may also be at other locations). In this way, through the status identifier 642, the user can know that the slave device is currently performing multi-device collaboration with other devices except the master device.
  • the main device displays a switching inquiry card 750 on the control center page 200.
  • the switching inquiry card 750 is similar to the switching inquiry card shown in FIG. 15 and will not be described again here. If the user clicks the "OK" button, the master device will end the multi-device collaboration between the slave device and other slave devices or devices outside the ring, and establish multi-device collaboration with the slave device based on the default or last used collaboration type. If the user clicks the "Cancel" button, this slave device will continue to maintain multi-device collaboration with other slave devices or devices outside the ring.
  • the user when the slave device has established multi-device collaboration with other slave devices or out-of-loop devices, the user can directly add or switch the devices participating in the multi-device collaboration on the control center page, improving improve user experience.
  • the electronic device includes corresponding hardware structures and/or software modules that perform each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is performed by hardware or computer software driving the hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each specific application, but such implementations should not be considered beyond the scope of this application.
  • Figure 23 is a schematic structural diagram of a multi-device collaboration device provided by an embodiment of the present application.
  • the electronic device such as the first electronic device, can implement corresponding functions through the hardware device shown in FIG. 23 .
  • the multi-device collaboration device may include: a display screen 1001, a memory 1002, a processor 1003 and a communication module 1004. Each of the above devices may be connected through one or more communication buses 1005.
  • 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 may pass the detected touch operation to the application processor to determine the touch event type. , providing 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 , baseband processor, and/or Neural network processor, etc. Among them, different processing units can be independent devices or integrated in one or more processors.
  • Memory 1002 is coupled to processor 1003 for storing various software programs and/or sets of instructions. Memory 1002 may include volatile memory and/or non-volatile memory.
  • the first electronic device When the software program and/or multiple sets of instructions in the memory 1002 are executed by the processor 1003, the first electronic device is caused to implement the following method steps: the device displays a first page in response to a user operation, and the first page includes the first electronic device.
  • the device identification 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, establish multi-device collaboration with the first target device based on the first collaboration type, and on the first page
  • a type switching card is displayed in the electronic device; wherein, 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 collaborative type supported between the first electronic device and the first target device.
  • the first page contains the device identification of each slave device around the first electronic device. In this way, the user can make the first electronic device communicate with any slave device by operating the device identification of any slave device. Establishing multi-device collaboration does not require users to search for control entrances of various collaboration types in different user interfaces, which improves the user experience.
  • the first electronic device When the software program and/or the plurality of sets 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's click operation on the type identification of the second collaborative type in the type switching card , switching the collaboration type between the first electronic device and the first target device from the first collaboration type to the second collaboration type; wherein the second collaboration type is any one of at least one collaboration type, and the first collaboration type Different from the second synergy type.
  • the first electronic device and the first target device can first establish multi-device collaboration based on the preset collaboration type, and then the user can By selecting the collaboration type that the user desires to use, the first electronic device can switch from the preset collaboration type to the collaboration type that the user desires to use based on the user's selection, thereby improving the user experience.
  • the first electronic device is caused to implement the following method steps: in response to the user operation, display 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 the at least one slave device; in response to the user's operation in the multi-device collaboration card, initiate a request to the second target device based on the third collaboration type Multi-device collaboration, the second target device is any slave device among at least one slave device; after establishing multi-device collaboration with the second target device, switch the device identification of the second target device in the multi-device collaboration card to the third collaboration Type of collaboration identifier.
  • a multi-device collaboration card is added to the second page of the first electronic device.
  • the multi-device collaboration card contains the device identifiers of each slave device around the first electronic device. In this way, the user can click The operation of the device identification of any slave device enables the first electronic device to establish multi-device collaboration with any slave device, without requiring the user to search for control entrances of various collaboration types in different user interfaces, thereby improving the user experience.
  • the first electronic device 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 response to the user clicking on the third device in the multi-device collaboration card.
  • the operation of the collaboration identifier of the collaboration type ends the multi-device collaboration between the first electronic device and the second target device. In this way, users can directly end the established multi-device collaboration in the multi-device collaboration card, without having to search for control entrances of various collaboration types in different user interfaces, which improves the user experience.
  • the first electronic device 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: if the slave device is not searched and the slave device is currently being searched. device, the multi-device collaboration card includes a first dynamic effect identifier, and the first dynamic effect identifier is used to indicate that the first electronic device is searching for the status of the slave device. In this way, the first electronic device can feed back to the user the status of the slave device that it is searching for, which improves user usage. experience.
  • the first electronic device 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: if the slave device is not searched and the slave device is not currently searched.
  • the device includes a first button in the multi-device collaboration card; in response to the user clicking the first button, search for slave devices. In this way, when the first electronic device does not currently search for the slave device, the user can manually search for the slave device, which improves the user experience.
  • the first electronic device 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: before displaying the second page, the first electronic device determines When the current scene is the first scene, determine 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 not The slave device is searched, and the second page does not include a multi-device collaboration card; wherein 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 after logging in After the account is changed, the second page is displayed for the first time; after the first electronic device is restored to factory settings or cleared of data, the second page is displayed for the first time. In this way, when the first electronic device displays the second page for the first time, if the slave device is not searched, the multi-
  • the first electronic device 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 in the multi-device collaboration card, Display the first page. In this way, the first electronic device can directly jump from the second page to the first page in response to the user's operation, so that the user can perform operations such as switching collaboration types on the first page, thereby improving the user experience.
  • the first electronic device 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 long-pressing any key in the multi-device collaboration card.
  • the operation of device identification of an electronic device displays the first page.
  • the first electronic device 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 long pressing the first electronic device in the multi-device collaboration card. For the operation of collaboration identification of three collaboration types, the first page is displayed.
  • the first electronic device 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 on the second electronic device in the multi-device collaboration card. The operation of the button displays the first page.
  • the user can open the first page in multiple ways and perform collaborative management of multiple devices on the first page, which improves the user experience.
  • the first electronic device 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 first page on the first page.
  • the device identification of the target device the operation of bringing the device identification of the first target device into contact with the device identification of the first electronic device, establishing multi-device collaboration with the first target device based on the first collaboration type, and displaying the type on the first page Switch cards.
  • the type switching card also includes a third button.
  • the first electronic device specifically implements the following method steps: in response to When the user clicks the third button, the multi-device collaboration with the first target device is disconnected. In this way, the user can end the multi-device collaboration between the first electronic device and the first target device on the third page, which improves the user experience.
  • the first page also includes a fourth button.
  • the first electronic device specifically implements the following method steps: in response to The user clicks the fourth button to display a third page.
  • the third page includes a first list.
  • the first list includes at least one collaborative category. type of options; in response to the user's click operation on the first option, a fourth page is displayed, the first option is any one of the collaboration type options in the first list, and the fourth page includes a switch button of the collaboration type corresponding to the first option ; In response to the user's click operation on the switch button, enable or disable the collaboration type corresponding to the first option. In this way, users can control the opening and closing of each collaboration type, which improves the user experience.
  • the first electronic device 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: established with the first slave device based on the fourth collaboration type In the state of multi-device collaboration, 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 simultaneous connection of three electronic devices, and the first switching card Used to ask the user whether to switch collaborative devices; in response to the user's operation on the first switching card, end the multi-device collaboration with the first slave device, and establish multi-device collaboration between the first electronic device and the first target device .
  • the first electronic device 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: established with the first slave device based on the fifth collaboration type In the state of multi-device collaboration, 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 Connect simultaneously.
  • the first electronic device 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 identification of the first target device on the first page, a second switching card is generated, and the second switching card is used to ask the user whether to switch the collaborative device; in response to the user's operation on the second switching card, the end Multi-device collaboration with out-of-loop devices, and establishing multi-device collaboration between the first electronic device and the first target device.
  • the first electronic device 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: the first target device communicates with other slave devices or out-of-loop devices. In a state where multi-device collaboration has been established 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. At the same time, 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 ended, and the first electronic device and the first target device are established. Collaboration between multiple devices.
  • the first electronic device 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: the first target device communicates with other slave devices or out-of-loop devices. In a state where multi-device collaboration has been established 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, join the established multi-device collaboration of the first target device, wherein the fifth collaboration Type supports simultaneous connection of three electronic devices.
  • the first electronic device 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: both the first electronic device and the first target device communicate with other When the slave device or the out-of-loop device has established multi-device collaboration, in response to the user's operation on the device identification of the first target device on the first page, a fourth switching card is generated. The fourth switching card is used to ask the user whether to switch collaboration. Device; in response to the user's operation on the fourth switching card, end the multi-device collaboration established by the first electronic device and the first target device respectively, and establish the multi-device collaboration between the first electronic device and the first target device.
  • the first electronic device 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: the second target device communicates with other slave devices or out-of-loop devices. In the state where multi-device collaboration has been established, in response to the user's operation of clicking the device identification of the second target device on the multi-device collaboration card, a fifth switching card is generated, and the fifth switching card is used to ask the user whether to switch the collaboration device; in response to the user Switch card on fifth The operation of the chip ends the established multi-device collaboration of the second target device, and establishes the multi-device collaboration between the first electronic device and the second target device.
  • the first electronic device can respond to the user's operation on the multi-device collaboration main page and adopt different strategies according to different scenarios.
  • Devices participating in multi-device collaboration can be added or switched to improve the user experience.
  • FIG. 24 is a schematic structural diagram of another multi-device collaboration device provided by an embodiment of the present application.
  • the electronic device such as the first electronic device, can implement corresponding functions through the software device shown in FIG. 24 .
  • the multi-device coordination device may include:
  • the first display module 1101 is used to display a first page in response to a user operation.
  • the first page includes the device identification of the first electronic device and the device identification of at least one slave device; the second display module 1102 is used to respond to the user's operation.
  • the operation of the device identification of the first target device on the first page 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; wherein the first target device is at least one In any one of the slave devices, the type switching card includes a type identifier of at least one cooperative type supported between the first electronic device and the first target device.
  • Embodiments of the present application also provide a computer-readable storage medium.
  • the computer-readable storage medium stores instructions, which when run on a computer, cause the computer to execute the methods of the above aspects.
  • Embodiments of the present application also provide a computer program product containing instructions, which when run on a computer, causes the computer to perform the methods of the above aspects.
  • Embodiments of the present application also provide a chip system.
  • the chip system includes a processor and is used to support the above device in implementing the functions involved in the above aspects, for example, generating or processing information involved in the above methods.
  • the chip system also includes a memory for storing necessary computer instructions and data for the multi-device collaboration device.
  • the chip system may be composed of chips, or may include chips and other discrete devices.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Human Computer Interaction (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Multimedia (AREA)
  • Information Transfer Between Computers (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

本申请实施例提供了一种多设备协同方法、电子设备及相关产品。该方法包括：第一电子设备响应于用户操作，显示第一页面，第一页面包括第一电子设备的设备标识和至少一个从设备的设备标识；第一电子设备响应于用户对第一页面中的目标设备的设备标识的操作，基于第一协同类型与目标设备建立多设备协同，并在第一页面中显示类型切换卡片；其中，目标设备为至少一个从设备中的任意一个从设备，类型切换卡片包括第一电子设备与目标设备之间支持的至少一个协同类型的类型标识。这样，用户可以在第一页面中对第一电子设备与各个从设备之间的多设备协同进行统一管理，不需要在不同的用户界面中去寻找各种协同类型的控制入口，提高了用户使用体验。

Description

一种多设备协同方法、电子设备及相关产品
本申请要求于2022年8月5日提交到国家知识产权局、申请号为202210940127.6、发明名称为“一种多设备协同方法、电子设备及相关产品”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及终端技术领域，尤其涉及一种多设备协同方法、电子设备及相关产品。
背景技术
多设备协同是一种应用于多个电子设备的分布式技术。利用多设备协同技术，两个或者多个电子设备之间可以进行跨系统、跨设备的协同，实现资源共享、协同操作。
随着终端技术的不断发展，多设备协同已经产生了多种不同的协同类型，例如：投屏、多屏协同等。目前，各个的协同类型在终端设备中没有统一的控制入口，各个协同类型的控制入口分布在不同的用户界面中。例如，投屏的控制入口可能位于视频类应用的播放界面中，多屏协同的控制入口可能位于系统设置应用的某个子页面中。因此，用户为了建立不同类型的多设备协同，需要在不同的用户界面中找到相应的控制入口，并进行操作，这就要求用户需要记住每一种多屏协同类型的控制入口所在的位置，导致用户的记忆成本较高，降低了用户使用体验。
发明内容
本申请实施例提供了一种多设备协同方法、电子设备及相关产品，以提高多设备协同的用户使用体验。
第一方面，本申请实施例提供了一种多设备协同方法，包括：第一电子设备响应于用户操作，显示第一页面，第一页面包括第一电子设备的设备标识和至少一个从设备的设备标识；第一电子设备响应于用户对第一页面中的第一目标设备的设备标识的操作，基于第一协同类型与第一目标设备建立多设备协同，并在第一页面中显示类型切换卡片；其中，第一目标设备为至少一个从设备中的任意一个从设备，类型切换卡片包括第一电子设备与第一目标设备之间支持的至少一个协同类型的类型标识。
本申请实施例提供的方法，第一页面包含了第一电子设备周围的各个从设备的设备标识，这样，用户可以通过对任意从设备的设备标识的操作，使第一电子设备与任意从设备建立多设备协同，不需要用户在不同的用户界面中去寻找各种协同类型的控制入口，提高了用户使用体验。
在一种实现方式中，该方法还包括：第一电子设备响应于用户对类型切换卡片中的第二协同类型的类型标识的点击操作，将第一电子设备与第一目标设备之间的协同类型从第一协同类型切换至第二协同类型；其中，第二协同类型是至少一个协同类型中的任意一个协同类型，第一协同类型与第二协同类型不同。这样，当第一电子设备与第一目标设备支持多种协同模式时，第一电子设备与第一目标设备可以先基于预设的协同类型建立多设备协同，然后，用户可以在第一电子设备上选择其期望使用的协同类型，第一电子设备可以基于用户的选择， 从预设的协同类型切换到用户期望使用的协同类型，提高了用户使用体验。
在一种实现方式中，该方法还包括：第一电子设备响应于用户操作，显示第二页面，第二页面包括多设备协同卡片，其中，如果第一电子设备搜索到至少一个从设备，多设备协同卡片中包括至少一个从设备的设备标识；第一电子设备响应于用户在多设备协同卡片中的操作，基于第三协同类型向第二目标设备发起多设备协同，第二目标设备是至少一个从设备中的任意一个从设备；第一电子设备与第二目标设备建立多设备协同之后，将多设备协同卡片中的第二目标设备的设备标识切换为第三协同类型的协同标识。这样，用户可以通过在多设备协同卡片中点击任意从设备的设备标识的操作，使第一电子设备与任意从设备建立多设备协同，不需要用户在不同的用户界面中去寻找各种协同类型的控制入口，提高了用户使用体验。
在一种实现方式中，该方法还包括：第一电子设备响应于用户在多设备协同卡片中点击第三协同类型的协同标识的操作，结束第一电子设备与第二目标设备之间的多设备协同。这样，用户可以在多设备协同卡片中直接结束已建立的多设备协同，不需要在不同的用户界面中去寻找各种协同类型的控制入口，提高了用户使用体验。
在一种实现方式中，该方法还包括：如果第一电子设备未搜索到从设备，并且当前正在搜索从设备，多设备协同卡片中包括第一动效标识，第一动效标识用于指示第一电子设备正在搜索从设备的状态。这样，第一电子设备可以将其正在搜索从设备的状态反馈给用户，提高了用户使用体验。
在一种实现方式中，该方法还包括：如果第一电子设备未搜索到从设备，并且当前未搜索从设备，多设备协同卡片中包括第一按钮；第一电子设备响应于用户点击第一按钮的操作，搜索从设备。这样，在第一电子设备当前未搜索到从设备时，用户可以手动搜索从设备，提高了用户使用体验。
在一种实现方式中，该方法还包括：在显示第二页面前，第一电子设备确定当前场景为第一场景时，判断是否搜索到至少一个从设备；如果搜索到至少一个从设备，第二页面包括多设备协同卡片，多设备协同卡片中包括至少一个从设备的设备标识；如果未搜索到从设备，第二页面不包括多设备协同卡片；其中，第一场景包括以下至少一个：第一电子设备在操作系统初始化之后，第一次显示第二页面；第一电子设备在登录的账号发生变化之后，第一次显示第二页面；第一电子设备在恢复出厂设置或者清空数据之后，第一次显示第二页面。这样，第一电子设备在第一次显示第二页面时，如果未搜索到从设备，可以不显示多设备协同卡片，减少对用户的打扰，提高了用户使用体验。
在一种实现方式中，第一电子设备响应于用户操作，显示第一页面，包括：第一电子设备响应于用户在多设备协同卡片中的操作，显示第一页面。这样，第一电子设备可以响应于用户操作，从第二页面直接跳转到第一页面，以便于用户在第一页面中执行切换协同类型等操作，提高了用户使用体验。
在一种实现方式中，第一电子设备响应于用户在多设备协同卡片中的操作，显示第一页面，包括：第一电子设备响应于用户在多设备协同卡片中长按任意一个电子设备的设备标识的操作，显示第一页面。
在一种实现方式中，第一电子设备响应于用户在多设备协同卡片中的操作，显示第一页面，包括：第一电子设备响应于用户在多设备协同卡片中长按第三协同类型的协同标识的操作，显示第一页面。
在一种实现方式中，多设备协同卡片中包括第二按钮，第一电子设备响应于用户在多设备协同卡片中的操作，显示第一页面，包括：第一电子设备响应于用户在多设备协同卡片中点击第二按钮的操作，显示第一页面。
这样，用户可以通过多种方式打开第一页面，并在第一页面中进行多设备协同的管理，提高了用户使用体验。
在一种实现方式中，第一电子设备响应于用户对第一页面中的第一目标设备的设备标识的操作，基于第一协同类型与第一目标设备建立多设备协同，并在第一页面中显示类型切换卡片，包括：第一电子设备响应于用户在第一页面拖动第一目标设备的设备标识，使第一目标设备的设备标识与第一电子设备的设备标识相接触的操作，基于第一协同类型与第一目标设备建立多设备协同，并在第一页面中显示类型切换卡片。
在一种实现方式中，类型切换卡片中还包括第三按钮，该方法还包括：第一电子设备响应于用户点击第三按钮的操作，断开与第一目标设备之间的多设备协同。这样，用户可以在第而页面结束第一电子设备与第一目标设备的多设备协同，提高了用户使用体验。
在一种实现方式中，第一页面中还包括第四按钮，该方法还包括：第一电子设备响应于用户对第四按钮的点击操作，显示第三页面，第三页面包括第一列表，第一列表包括至少一个的协同类型的选项；第一电子设备响应于用户对第一选项的点击操作，显示第四页面，第一选项是第一列表中的任意一个协同类型的选项，第四页面包括第一选项对应的协同类型的开关按钮；第一电子设备响应于用户对开关按钮的点击操作，开启或者关闭第一选项对应的协同类型。这样，用户可以各个协同类型进行开启和关闭等控制，提高了用户使用体验。
在一种实现方式中，该方法还包括：第一电子设备与第一从设备基于第四协同类型已建立多设备协同的状态下，响应于用户在第一页面对第一目标设备的设备标识的操作，生成第一切换卡片，其中，第四协同类型不支持三个电子设备同时连接，第一切换卡片用于询问用户是否切换协同设备；第一电子设备响应于用户对第一切换卡片的操作，结束与第一从设备之间的多设备协同，并且建立第一电子设备与第一目标设备之间的多设备协同。
在一种实现方式中，该方法还包括：第一电子设备与第一从设备基于第五协同类型已建立多设备协同的状态下，响应于用户在第一页面对第一目标设备的设备标识的操作，将第一目标设备加入到已建立的多设备协同，其中，第五协同类型支持三个电子设备同时连接。
在一种实现方式中，该方法还包括：第一电子设备与环外设备已建立多设备协同的状态下，响应于用户在第一页面对第一目标设备的设备标识的操作，生成第二切换卡片，第二切换卡片用于询问用户是否切换协同设备；第一电子设备响应于用户对第二切换卡片的操作，结束与环外设备之间的多设备协同，并且建立第一电子设备与第一目标设备之间的多设备协同。
在一种实现方式中，该方法还包括：第一目标设备与其他从设备或者环外设备基于第四协同类型已建立多设备协同的状态下，第一电子设备响应于用户在第一页面对第一目标设备的设备标识的操作，生成第三切换卡片，其中，第四协同类型不支持三个电子设备同时连接，第三切换卡片用于询问用户是否切换协同设备；第一电子设备响应于用户对第三切换卡片的操作，结束第一目标设备已建立的多设备协同，并且建立第一电子设备与第一目标设备之间的多设备协同。
在一种实现方式中，该方法还包括：第一目标设备与其他从设备或者环外设备基于第五协同类型已建立多设备协同的状态下，第一电子设备响应于用户在第一页面对第一目标设备 的设备标识的操作，加入到第一目标设备已建立的多设备协同，其中，第五协同类型支持三个电子设备同时连接。
在一种实现方式中，该方法还包括：第一电子设备和第一目标设备均与其他从设备或者环外设备已建立多设备协同的状态下，第一电子设备响应于用户在第一页面对第一目标设备的设备标识的操作，生成第四切换卡片，第四切换卡片用于询问用户是否切换协同设备；第一电子设备响应于用户对第四切换卡片的操作，结束第一电子设备、第一目标设备各自已建立的多设备协同，并且建立第一电子设备与第一目标设备之间的多设备协同。
在一种实现方式中，该方法还包括：第二目标设备与其他从设备或者环外设备已建立多设备协同的状态下，第一电子设备响应于用户在多设备协同卡片点击第二目标设备的设备标识的操作，生成第五切换卡片，第五切换卡片用于询问用户是否切换协同设备；第一电子设备响应于用户对第五切换卡片的操作，结束第二目标设备已建立的多设备协同，并且建立第一电子设备与第二目标设备之间的多设备协同。
这样，在第一电子设备和/或从设备已经建立了多设备协同的情况下，第一电子设备可以响应于用户在多设备协同主页面中的操作，根据不同的场景，采用不同的策略对参与多设备协同的设备进行增加或者切换，提高了用户使用体验。
第二方面，本申请实施例还提供了一种多设备协同装置，包括：第一显示模块，用于响应于用户操作，显示第一页面，第一页面包括第一电子设备的设备标识和至少一个从设备的设备标识；第二显示模块，用于响应于用户对第一页面中的目标设备的设备标识的操作，基于第一协同类型与目标设备建立多设备协同，并在第一页面中显示类型切换卡片；其中，目标设备是至少一个从设备中的任意一个从设备，类型切换卡片包括第一电子设备与目标设备之间支持的至少一个协同类型的类型标识。
本申请实施例提供的装置，第一页面包含了第一电子设备周围的各个从设备的设备标识，这样，用户可以通过对任意从设备的设备标识的操作，使第一电子设备与任意从设备建立多设备协同，不需要用户在不同的用户界面中去寻找各种协同类型的控制入口，提高了用户使用体验。
第三方面，本申请实施例还提供一种计算机可读存储介质，计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述各方面及其各个实现方式的方法。
第四方面，本申请实施例还提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面及其各个实现方式的方法。
第五方面，本申请实施例还提供了一种芯片系统，该芯片系统包括处理器，用于支持上述终端设备实现上述方面中所涉及的功能，例如，生成或处理上述方法中所涉及的信息。
附图说明
图1是本申请实施例提供的电子设备的硬件结构示意图；
图2是本申请实施例的电子设备的软件结构框图；
图3是本申请实施例提供的一种多设备协同方法的第一个流程图；
图4A是本申请实施例提供的控制中心页面的第一个示意图；
图4B是本申请实施例提供的控制中心页面的第二个示意图；
图4C是本申请实施例提供的控制中心页面的第三个示意图；
图4D是本申请实施例提供的控制中心页面的第四个示意图；
图5是本申请实施例提供的一种多设备协同方法的第一组交互示例图；
图6是本申请实施例提供的一种多设备协同方法的第二组交互示例图；
图7是本申请实施例提供的一种多设备协同方法的第三组交互示例图；
图8是本申请实施例提供的一种多设备协同方法的第二个流程图；
图9A-图9D是本申请实施例提供的一种多设备协同方法的第四组交互示例图；
图10A-图10D是本申请实施例提供的一种多设备协同方法的第五组交互示例图；
图11A-图11D是本申请实施例提供的一种多设备协同方法的第六组交互示例图；
图12A-图12D是本申请实施例提供的一种多设备协同方法的第七组交互示例图；
图13A-图13C是本申请实施例示出的自动协同服务的开启和关闭方式的示例图；
图14是本申请实施例提供的多设备协同方法的场景一的交互示例图；
图15是本申请实施例提供的一种多设备协同方法的子场景1的第一个交互示例图；
图16是本申请实施例提供的一种多设备协同方法的子场景1的第二个交互示例图；
图17是本申请实施例提供的一种多设备协同方法的子场景2的交互示例图；
图18是本申请实施例提供的一种多设备协同方法的场景三的第一个交互示例图；
图19是本申请实施例提供的一种多设备协同方法的场景三的第二个交互示例图；
图20是本申请实施例提供的一种多设备协同方法的场景四的交互示例图；
图21是本申请实施例提供的一种多设备协同方法的另一个交互示例图；
图22是本申请实施例提供的一种多设备协同方法的又一个交互示例图；
图23是本申请实施例提供的一种多设备协同装置的结构示意图；
图24是本申请实施例提供的另一种多设备协同装置的结构示意图。
具体实施方式
多设备协同是一种应用于多个电子设备的分布式技术。利用多设备协同技术，两个或者多个电子设备之间可以进行跨系统、跨设备的协同，实现资源共享、协同操作。
多设备协同可以应用于同类型或者不同类型的电子设备之间。其中，电子设备的类型包括但不限于手机、平板电脑、笔记本电脑、大屏设备(例如：智能电视、智慧屏)、个人计算机(persona1computer，PC)、手持计算机、上网本、个人数字助理(personal digital assistant，PDA)、可穿戴电子设备、车载设备、虚拟现实设备等设备。
多设备协同需要基于设备间的通信连接实现。该通信连接可以是有线通信连接，也可以是无线通信连接。其中，有线通信连接的解决方案例如可以包括USB On-The-Go(OTG)技术；无线通信的解决方案例如可以包括如无线保真(wireless fidelity，Wi-Fi)，Wi-Fi直连(Wi-Fi Direct)，蓝牙(bluetooth，BT)，近距离无线通信技术(near field communication，NFC)，红外技术(infrared，IR)等。
随着终端技术的不断发展，多设备协同已经产生了多种不同的协同类型(也称：协同服务)，例如：屏幕扩展、投屏、超级通话、屏幕镜像、多屏协同、超级通知、键鼠共享、超级键鼠等。其中：
屏幕扩展：将电子设备B的屏幕作为电子设备A的副屏，电子设备A可以将其需要显示的一部分内容转移到副屏上进行显示，电子设备A的屏幕与电子设备B的屏幕可以共同显示内容，扩展了电子设备A的显示能力。
投屏：将电子设备A屏幕中的内容(例如：视频、照片等)投送到电子设备B的屏幕中 进行显示。在投屏时，用户可以将选择电子设备A屏幕的部分内容或者全部内容投送到电子设备B的屏幕中进行显示。一些投屏方式还允许用户在投屏期间将屏幕切换至其他页面，而不影响电子设备B继续播放被投送的内容，比如，DLNA投屏。
超级通话：当电子设备A接到语音通话或者视频通话的呼入时，电子设备B上可以同步显示呼入界面，这样，用户可以选择在电子设备B上接听或者挂断通话。
屏幕镜像：将电子设备A屏幕中的所有内容完整地在电子设备B的屏幕中进行镜像显示。电子设备B中显示的电子设备A的内容与电子设备A显示的内容相同，且随着电子设备A显示内容的变化而变化。
多屏协同：将电子设备A的用户界面投影到电子设备B的屏幕中进行显示，并且允许用户在电子设备B中对电子设备A的用户界面进行操作，以及通过在电子设备B中执行特定的操作(例如：从电子设备B的用户界面中向电子设备A的用户界面中拖拽文件)，将电子设备B中的文件传输到电子设备A中，实现电子设备A与电子设备B之间的跨设备操作和跨设备文件传输等。其中，电子设备A的用户界面可以显示在电子设备B屏幕中的任意区域，也可以全屏显示。
超级通知：当电子设备A接收到通知消息时，通知消息可以在电子设备B中同步显示，还可以允许用户在电子设备B中对通知消息执行回复、删除、已读等操作。
键鼠共享：电子设备A与电子设备B可以共享彼此原有的输入设备，例如：鼠标、键盘等。举例来说，电子设备A的输入设备共享给电子设备B，共享的输入设备既可以在电子设备A中进行输入，也可以在电子设备B中进行输入。另外，在键鼠共享类型中，电子设备A与电子设备B之间还可以进行文件传输。
超级接续：用户在电子设备A上运行应用，电子设备B的界面上可以提示用户在电子设备B上打开在电子设备A上正在运行的应用，从而转移到电子设备B上进行接续操作，比如观看视频、编辑文档，等。例如：电子设备A上正在运行文档应用，文档应用可以是备忘录、word等，用户在电子设备A上正在编辑文档，当电子设备B和电子设备A距离较近时，电子设备B上显示提示信息，用户在电子设备B上点击提示信息，响应于用户的点击操作，电子设备B打开文档应用并展示用户正在编辑的位置，从而转移至电子设备B上继续编辑等。
在上述列举出的多个协同类型中：一些协同类型是主设备(一般是多设备协同的发起方)响应于用户操作，向从设备(一般是多设备协同的参与方)发起的，因此可以被称作手动协同服务或手动协同业务，例如：屏幕扩展、投屏、屏幕镜像、多屏协同、键鼠共享等；另一些协同类型是在用户开启功能的状态下，满足触发规则时自动触发的，因此可以被称作自动协同服务或者自动协同业务，例如：超级通话、超级通知、超级接续等。
对于两个电子设备来说，其支持的协同类型一般与设备类型、屏幕尺寸、设备能力等因素有关。因此，两个电子设备可能仅支持一种协同类型，也可能支持多种协同类型。
以手动协同服务为例：
如果主设备为手机，从设备为平板电脑，其支持的协同类型可以包括多屏协同。
如果主设备为手机中的非折叠屏手机，从设备为PC，其支持的协同类型可以包括超级键鼠、多屏协同。其中，非折叠屏手机与PC首次触发连接时，默认的协同类型可以是多屏协同。
如果主设备为手机中的折叠屏手机，从设备为PC，其支持的协同类型可以包括超级键鼠、多屏协同、屏幕镜像和屏幕扩展。其中，折叠屏手机与PC首次触发连接时，默认的协同类 型可以是多屏协同。
如果主设备为手机，从设备为大屏设备，其支持的协同类型可以包括投屏。
如果主设备为平板电脑，从设备为手机，其支持的协同类型可以包括多屏协同。
如果主设备为平板电脑，从设备为PC，其支持的协同类型可以包括屏幕镜像、屏幕扩展、超级键鼠。其中，平板电脑与PC首次触发连接时，默认的协同类型可以是屏幕镜像。
如果主设备为平板电脑，从设备为大屏设备，其支持的协同类型可以包括投屏。
如果主设备为PC，从设备为非折叠屏手机，其支持的协同类型可以包括超级键鼠、多屏协同。其中，PC与非折叠屏手机首次触发连接时，默认的协同类型可以是多屏协同。
如果主设备为PC，从设备为折叠屏手机，其支持的协同类型可以包括超级键鼠、多屏协同、屏幕镜像和屏幕扩展。其中，PC与折叠屏手机首次触发连接时，默认的协同类型可以是多屏协同。
如果主设备为PC，从设备为平板电脑，其支持的协同类型可以包括屏幕镜像、屏幕扩展、超级键鼠。其中，PC与平板电脑首次触发连接时，默认的协同类型可以是屏幕镜像。
如果主设备为PC，从设备为大屏设备，其支持的协同类型可以包括投屏。
以自动协同服务为例：
支持超级通话的电子设备可以包括手机、平板、PC、大屏显示设备等。
支持超级通知的电子设备可以包括手机、平板、PC等。
支持超级接续的电子设备可以包括手机、平板、PC、大屏显示设备等。
在传统的方案中，各个的协同类型在终端设备中没有统一的控制入口，各个协同类型的控制入口分布在不同的用户界面中。例如，投屏的控制入口可能位于视频类应用的播放界面中，多屏协同的控制入口可能位于系统设置应用的某个二级页面中。因此，用户为了建立不同类型的多设备协同，需要在不同的用户界面中找到相应的控制入口，并进行操作，这就要求用户需要记住每一种多屏协同类型的控制入口所在的位置，导致用户的记忆成本较高，降低了用户使用体验。
为了解决上述技术问题，本申请实施例提供的一种多设备协同方法。
本申请实施例的多设备协同方法可以应用于各类型的具有显示功能的电子设备。
图1是本申请实施例提供的电子设备的硬件结构示意图。该设备既可以作为多设备协同中的主设备，也可以作为多设备协同中的从设备。如图1所示，电子设备100可以包括处理器110，存储器120，通用串行总线(universal serial bus，USB)接口130，射频电路140，移动通信模块150，无线通信模块160，摄像头170，显示屏180，触摸传感器190，气压传感器210和按键220等。
处理器110可以包括一个或多个处理单元，例如：处理器110可以包括应用程序处理器(applicationprocessor，AP)，调制解调处理器，图形处理器(graphics processing unit，GPU)，图像信号处理器(image signal processor，ISP)，视频编解码器，数字信号处理器(digital signal processor，DSP)，基带处理器，和/或神经网络处理器(neural-networkprocessing unit，NPU)等。其中，不同的处理单元可以是独立的器件，也可以集成在一个或多个处理器中，例如集成在系统芯片(system on a chip，SoC)中。处理器110中还可以设置存储器，用于存储指令和数据。在一些实施例中，处理器110中的存储器为高速缓冲存储器。该存储器可以保存处理器110刚用过或循环使用的指令或数据。
在一些实施例中，处理器110可以包括一个或多个接口。接口可以包括集成电路 (inter-integrated circuit，I2C)接口，集成电路内置音频(inter-integrated circuit sound，I2S)接口，脉冲编码调制(pulse code modulation，PCM)接口，通用异步收发传输器(universal asynchronous receiver/transmitter，UART)接口，移动产业处理器接口(mobile industryprocessor interface，MIPI)，通用输入输出(general-purpose input/output，GPIO)接口，用户标识模块(subscriber identity module，SIM)接口，和/或通用串行总线(universal serial bus，USB)接口等。
存储器120可以用于存储计算机可执行程序代码，可执行程序代码包括指令。存储器120可以包括存储程序区和存储数据区。其中，存储程序区可存储操作系统、至少一个功能所需的应用程序(比如声音播放功能，图像播放功能等)等。存储数据区可存储电子设备100使用过程中所创建的数据(比如音频数据，电话本等)等。此外，存储器120可以包括一个或者多个存储单元，例如可以包括易失性存储器(volatile memory)，如：动态随机存取存储器(dynamic random access memory，DRAM)、静态随机存取存储器(static random access memory，SRAM)等；还可以包括非易失性存储器(non-volatile memory，NVM)，如：只读存储器(read-only memory，ROM)、闪存(flash memory)等。处理器110通过运行存储在存储器120的指令，和/或存储在设置于处理器中的存储器的指令，执行电子设备100的各种功能应用程序以及数据处理。
这里需要补充说明的是，本申请实施例所指的操作系统，包括但不限于Android操作系统、IOS操作系统、iPad OS、鸿蒙操作系统(HarmonyOS)、Windows操作系统、Linux操作系统、MAC OS操作系统、嵌入式系统等。
电子设备100的无线通信功能可以通过射频电路140、移动通信模块150、无线通信模块160、调制解调处理器以及基带处理器等实现。
射频电路140可以包括至少一个天线141，用于发射和接收电磁波信号。电子设备100中的每个天线可用于覆盖单个或多个通信频带。在一些实施例中，天线可以和调谐开关结合使用。
移动通信模块150可以提供应用程序在电子设备100上的包括2G/3G/4G/5G等无线通信的解决方案。移动通信模块150可以包括至少一个滤波器，开关，功率放大器，低噪声放大器(low noise amplifier，LNA)等。移动通信模块150可以由天线141接收电磁波，并对接收的电磁波进行滤波，放大等处理，传送至调制解调处理器进行解调。移动通信模块150还可以对经调制解调处理器调制后的信号放大，经天线141转为电磁波辐射出去。在一些实施例中，移动通信模块150的至少部分功能模块可以被设置于处理器110中。在一些实施例中，移动通信模块150的至少部分功能模块可以与处理器110的至少部分模块被设置在同一个器件中。
调制解调处理器可以包括调制器和解调器。其中，调制器用于将待发送的低频基带信号调制成中高频信号。解调器用于将接收的电磁波信号解调为低频基带信号。随后解调器将解调得到的低频基带信号传送至基带处理器处理。低频基带信号经基带处理器处理后，被传递给应用程序处理器。应用程序处理器通过音频设备(包括但不限于扬声器，受话器等)输出声音信号，或通过显示屏180显示图像或视频。在一些实施例中，调制解调处理器可以是独立的器件。在另一些实施例中，调制解调处理器可以独立于处理器110，与移动通信模块150或其他功能模块设置在同一个器件中。
无线通信模块160可以包括无线保真(wireless fidelity，Wi-Fi)模块，蓝牙(bluetooth，BT)模块、GNSS模块、近距离无线通信技术(near field communication，NFC)模块、红外 (infrared，IR)模块等。无线通信模块160可以是集成上述至少一个模块的一个或多个器件。无线通信模块160经由天线141接收电磁波，将电磁波信号调频以及滤波处理，将处理后的信号发送到处理器110。无线通信模块160还可以从处理器110接收待发送的信号，对其进行调频，放大，经天线141转为电磁波辐射出去。
本申请实施例中，电子设备100的无线通信功能例如可以包括全球移动通讯系统(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)，第五代移动通信技术新空口(5th generation mobile networks new radio，5G NR)，BT，GNSS，WLAN，NFC，FM，和/或IR等功能。GNSS可以包括全球卫星定位系统(global positioning system，GPS)，全球导航卫星系统(global navigation satellite system，GLONASS)，北斗卫星导航系统(beidou navigation satellite system，BDS)，准天顶卫星系统(quasi-zenith satellite system，QZSS)和/或星基增强系统(satellite based augmentation systems，SBAS)。
摄像头170用于捕获静态图像或视频。摄像头170包括镜头和感光元件，物体通过镜头生成光学图像投射到感光元件。感光元件可以是电荷耦合器件(charge coupled device，CCD)或互补金属氧化物半导体(complementary metal-oxide-semiconductor，CMOS)光电晶体管。感光元件把光信号转换成电信号，之后将电信号传递给ISP转换成数字图像信号。ISP将数字图像信号输出到DSP加工处理。DSP将数字图像信号转换成标准的RGB，YUV，RYYB等格式的图像信号。在一些实施例中，电子设备100可以包括1个或N个摄像头170，N为大于1的正整数。
NPU为神经网络(neural-network，NN)计算处理器，通过借鉴生物神经网络结构，例如借鉴人脑神经元之间传递模式，对输入信息快速处理，还可以不断的自学习。通过NPU可以实现电子设备100的智能认知等应用程序，例如：图像识别，人脸识别，语音识别，文本理解等。
显示屏180用于显示图像，视频等。显示屏180包括显示面板。显示面板可以采用液晶显示屏(liquid crystal display，LCD)，有机发光二极管(organic light-emitting diode，OLED)，有源矩阵有机发光二极体或主动矩阵有机发光二极体(active-matrix organic light emitting diode的，AMOLED)，柔性发光二极管(flex light-emitting diode，FLED)，MiniLED，MicroLED，Micro-OLED，量子点发光二极管(quantum dot light emitting diodes，QLED)等。在一些实施例中，电子设备100可以包括1个或N个显示屏180，N为大于1的正整数。
触摸传感器190，也称“触控器件”。触摸传感器190可以设置于显示屏180，由触摸传感器190与显示屏180组成触摸屏，也称“触控屏”。触摸传感器190用于检测作用于其上或附近的触摸操作。触摸传感器可以将检测到的触摸操作传递给应用程序处理器，以确定触摸事件类型。可以通过显示屏180提供与触摸操作相关的视觉输出。在另一些实施例中，触摸传感器190也可以设置于电子设备100的表面，与显示屏180所处的位置不同。
气压传感器210用于测量气压。在一些实施例中，电子设备100通过气压传感器210测得的气压值计算海拔高度，辅助定位和导航。
按键220包括开机键，音量键等。按键220可以是机械按键。也可以是触摸式按键。电子设备100可以接收按键输入，产生与电子设备100的用户设置以及功能控制有关的键信号 输入。
可以理解的是，本申请实施例示意的结构并不构成对电子设备100的具体限定。在本申请另一些实施例中，电子设备可以包括比图示更多或更少的部件，或者组合某些部件，或者拆分某些部件，或者不同的部件布置。图示的部件可以以硬件，软件或软件和硬件组合实现。
下面对本申请实施例提供的多设备协同方法的各方法步骤进行示例性说明。
电子设备100的软件系统可以采用分层架构，事件驱动架构，微核架构，微服务架构，或云架构。本发明实施例以分层架构的Android系统为例，示例性说明电子设备100的软件结构。
图2是本申请实施例的电子设备100的软件结构框图。
分层架构将软件分成若干个层，每一层都有清晰的角色和分工。层与层之间通过软件接口通信。在一些实施例中，将Android系统分为四层，从上至下分别为应用程序层，应用程序框架层，安卓运行时(Android runtime)和系统库，以及内核层。
应用程序层可以包括一系列应用程序包。
如图2所示，应用程序包可以包括相机，图库，日历，通话，地图，导航，WLAN，蓝牙，音乐，视频，短信息等应用程序。
应用程序框架层为应用程序层的应用程序提供应用编程接口(application programming interface，API)和编程框架。应用程序框架层包括一些预先定义的函数。
如图2所示，应用程序框架层可以包括窗口管理器，内容提供器，视图系统，电话管理器，资源管理器，通知管理器等。
窗口管理器用于管理窗口程序。窗口管理器可以获取显示屏大小，判断是否有状态栏，锁定屏幕，截取屏幕等。
内容提供器用来存放和获取数据，并使这些数据可以被应用程序访问。所述数据可以包括视频，图像，音频，拨打和接听的电话，浏览历史和书签，电话簿等。
视图系统包括可视控件，例如显示文字的控件，显示图片的控件等。视图系统可用于构建应用程序。显示界面可以由一个或多个视图组成的。例如，包括短信通知图标的显示界面，可以包括显示文字的视图以及显示图片的视图。
电话管理器用于提供电子设备100的通信功能。例如通话状态的管理(包括接通，挂断等)。
资源管理器为应用程序提供各种资源，比如本地化字符串，图标，图片，布局文件，视频文件等等。
通知管理器使应用程序可以在状态栏中显示通知信息，可以用于传达告知类型的消息，可以短暂停留后自动消失，无需用户交互。比如通知管理器被用于告知下载完成，消息提醒等。通知管理器还可以是以图表或者滚动条文本形式出现在系统顶部状态栏的通知，例如后台运行的应用程序的通知，还可以是以对话窗口形式出现在屏幕上的通知。例如在状态栏提示文本信息，发出提示音，电子设备振动，指示灯闪烁等。
Android Runtime包括核心库和虚拟机。Android Runtime负责安卓系统的调度和管理。
核心库包含两部分：一部分是java语言需要调用的功能函数，另一部分是安卓的核心库。
应用程序层和应用程序框架层运行在虚拟机中。虚拟机将应用程序层和应用程序框架层的java文件执行为二进制文件。虚拟机用于执行对象生命周期的管理，堆栈管理，线程管理，安全和异常的管理，以及垃圾回收等功能。
系统库可以包括多个功能模块。例如：表面管理器(surface manager)，媒体库(Media  Libraries)，三维图形处理库(例如：OpenGL ES)，二维图形引擎(例如：SGL)等。
表面管理器用于对显示子系统进行管理，并且为多个应用程序提供了2D和3D图层的融合。
媒体库支持多种常用的音频，视频格式回放和录制，以及静态图像文件等。媒体库可以支持多种音视频编码格式，例如:MPEG4，H.264，MP3，AAC，AMR，JPG，PNG等。
三维图形处理库用于实现三维图形绘图，图像渲染，合成，和图层处理等。
二维图形引擎是二维绘图的绘图引擎。
内核层是硬件和软件之间的层。内核层至少包含显示驱动，摄像头驱动，音频驱动，传感器驱动。
为便于本领域技术人员理解本申请实施例的技术方案，本申请实施例对多设备协同的各场景中可能涉及的电子设备进行了分类，各电子设备包括但不限于可以划分为：主设备、从设备和环外设备。其中：
主设备：包括用户当前手持的设备，用户可以在主设备上执行操作，以向其他设备发起多设备协同，因此主设备一般也是发起多设备协同的设备。本申请实施例提供的多设备协同方法可以在主设备中实现。
从设备：包括位于主设备附近的、与主设备登录相同帐号的设备。主设备与从设备一般是同一厂商生产的电子设备。例如：主设备可以是厂商A生产的手机、从设备可以是厂商A生产的平板电脑等。主设备和从设备登录的账号可以是用户从设备制造商申请的账号。
环外设备：包括与主设备为同一设备制造商生产的、但是未登录与主设备相同账号的设备；还包括其他一些特定厂商生产的设备；还包括其他厂商生产的特定类型的设备，例如：大屏设备等。
本申请实施例提供的多设备协同方法可以在主设备中实现。例如，主设备可以响应于用户执行的一个或者多个操作，执行多设备协同方法的各步骤。
图3是本申请实施例提供的一种多设备协同方法的第一个流程图。
如图3所示，在一种实现方式中，该方法可以包括以下步骤S101-S103：
步骤S101，主设备响应于用户操作，显示多设备协同卡片，其中，当主设备周围存在至少一个从设备时，多设备协同卡片中包括至少一个从设备的设备标识。
具体实现中，多设备协同卡片可以位于主设备的控制中心页面中，也可以位于主设备的负一屏页面中，还可以位于主设备的主屏幕页面，或者位于其他页面中。本申请实施例对多设备协同卡片的位置不做具体限定。
以多设备协同卡片位于主设备的控制中心页面中为例：
主设备可以响应于用户在任意页面执行的第一操作，显示控制中心页面。可以理解的是，本申请不限定该第一操作的具体方式。例如：第一操作可以是用户手指在显示屏的顶部边缘向下滑动的操作，可以是用户手指在显示屏的底部边缘向上滑动的操作，或者其他操作。在另外一些实施方式中，当用户手指在显示屏的顶部边缘向下滑动时，如果用户手指在显示屏顶部的左半部分边缘向下滑动，会呼出通知中心页面，如果用户手指在显示屏顶部的右半部分边缘向下滑动，会呼出控制中心页面，这些都在本申请实施例的保护范围内。
在一种实现方式中，为了确定主设备周围是否存在从设备，在步骤S101之前和/或步骤S101之后，主设备可以以预设的时间间隔(即：预设的周期)向周围发送蓝牙广播，以对其中周围可能存在的从设备进行搜索。该蓝牙广播可以是经典蓝牙广播，也可以是蓝牙低功耗 (Bluetooth Low Energy，BLE)广播，本申请实施例对此不做限定。如果主设备的周围存在从设备，那么从设备可以在接收到主设备的蓝牙广播之后，向主设备发送广播消息。主设备如果接收到从设备的响应消息，则可以确定从设备的存在。
可以理解的是，由于主设备的对从设备的搜索是间隔性进行的，因此，在主设备响应于用户操作而显示控制中心页面时，针对从设备的搜索，可能会有以下三种情况：
第一种情况，主设备已经搜索到了一个或者多个从设备；
第二种情况，主设备未搜索到从设备，并且当前正在搜索从设备；
第三种情况，主设备未搜索到从设备，并且当前未进行从设备的搜索。
对于上述三种情况，在主设备响应于用户操作而显示控制中心页面时，多设备协同卡片中显示的内容可能是不同的，下面结合附图进行示例性说明。
图4A是本申请实施例提供的控制中心页面的第一个示意图。
如图4A所示，在一种实现方式中，控制中心页面200可以包括一个或者多个功能开关按钮，例如：Wi-Fi开关按钮201、蓝牙开关按钮202、手电筒开关按钮203、振动开关按钮204、静音开关按钮205等。当用户点击某个开关按钮时，主设备可以开启或者关闭相应的功能。
控制中心页面200还可以包括一个或者多个滑动控件，例如用于调整显示屏亮度的滑动控件206。当用户拖动滑动控件206中的滑块时，主设备可以对显示屏的亮度进行调节。
控制中心页面200还可以包含多设备协同卡片210，多设备协同卡片210中可以包括卡片名称211，以及一个或者多个可点击的元素，例如：多设备协同卡片210的关闭图标212，以及多设备协同主页面的入口按钮213。关于多设备协同主页面的具体内容将在下文做具体展开说明。
其中，上述卡片的名称仅仅是本申请的一个示例，还可以其他名称命名多设备协同这一功能，本申请对此不做限定。例如可以为：“荣耀互联”、“超级终端”等。因此，多设备协同卡片210中显示的卡片名称211可以是“荣耀互联”、“超级终端”等。相应地，多设备协同主页面也可以被称作荣耀互联主页面、超级终端主页面。
进一步如图4A所示，对于上述第一种情况，如果主设备在显示控制中心页面200时，已经搜索到了一个或者多个从设备，那么，主设备在显示控制中心页面200时，可以直接将搜索结果显示在多设备协同卡片210中。例如：多设备协同卡片210中可以包括主设备已经搜索到的一个或者多个从设备的设备标识214。其中，从设备的设备标识214可以是一个图形化标识，例如图标，或者其他拟物化元素等。例如：可以将从设备的图标作为从设备的设备标识214，或者，还可以将包裹从设备图标的水泡形元素作为从设备的设备标识214，本申请实施例对此不做限定。
通过在多设备协同卡片210中显示从设备的设备标识214，用户可以了解当前主设备的周围存在哪些可以进行多设备协同的从设备，以及各个从设备的类型。例如：如果从设备的设备标识214是一个平板电脑图标，用户可以了解这个从设备是一个平板电脑；如果从设备的设备标识214是一个大屏设备图标，用户可以了解这个从设备是一个大屏设备；如果从设备的设备标识214是一个手机图标，用户可以了解这个从设备是一个手机。
多设备协同卡片210还可以包括各个从设备的设备名称215。设备名称可以与其对应的设备标识214协同显示，例如设备名称215可以显示在其对应的设备标识214的上方、下方、或者其他位置。本申请实施例中，设备名称215可以是从设备的产品名称，例如：荣耀Smart  TV、荣耀Pad、荣耀Magic Book等，设备名称215还可以是用户自定义的名称，例如：小李的荣耀平板、客厅的荣耀智慧屏等，本申请实施例对此不做限定。
图4B是本申请实施例提供的控制中心页面的第二个示意图。
如图4B所示，对于上述第二种情况，如果主设备在显示控制中心页面200时，未搜索到从设备，并且当前正在搜索从设备，那么，主设备在显示控制中心页面200时，可以在多设备协同卡片210中显示其正在搜索从设备的页面元素。例如：多设备协同卡片210中可以包括一个带有搜索图案216的动效标识，通过动效标识拟物化地表现主设备正在搜索从设备的状态。
在此之后，主设备如果搜索到了从设备，则可以将搜索到的从设备的设备标识和设备名称显示在多设备协同卡片210中，这时，多设备协同卡片210会显示为图4A所示的样式。
可以理解的是，当主设备周围存在多个从设备时，主设备可能会先后搜索到不同的从设备。在这种情况下，主设备可以每搜到一个从设备，就将这个从设备的设备标识和设备名称显示在多设备协同卡片210中。当先后搜索到多个从设备时，多个从设备的设备标识可以根据搜索到的顺序依次排列。另外，主设备在搜索从设备的过程中，如果搜索到了某个从设备，可以不立刻显示这个从设备的设备标识和设备名称，而是等到搜索结束(例如搜索超时)之后，再将所有搜索到的从设备的设备标识和设备名称显示在多设备协同卡片210中。
图4C是本申请实施例提供的控制中心页面的第三个示意图。
如图4C所示，对于上述第三种情况，如果主设备在显示控制中心页面200时，未搜索到从设备，并且当前未进行从设备的搜索，那么，主设备在显示控制中心页面200时，可以在多设备协同卡片210中显示用于引导用户主动搜索从设备的页面元素。例如：多设备协同卡片210中可以包括搜索按钮217，以及用于引导用户点击搜索按钮217以主动搜索从设备的提示信息218。
主设备检测到用户点击11搜索按钮时，可以响应于用户的点击操作，开始搜索从设备，例如向周围发送蓝牙广播，以及监听从设备的针对蓝牙广播的响应消息等。主设备开始搜索从设备之后，可以将多设备协同卡片210改变为图4B的样式。
在此之后，主设备如果搜索到了从设备，则可以将搜索到的从设备的设备标识和设备名称显示在多设备协同卡片210中，这时，多设备协同卡片210会显示为图4A所示的样式。
图4D是本申请实施例提供的控制中心页面的第四个示意图。
如图4D的页面(a)所示，在一种实现方式中，如果主设备在显示控制中心页面200时未搜索到从设备，并且主设备当前是第一次显示控制中心页面200，那么，主设备在初始显示控制中心页面200时，可以不显示多设备协同卡片210。其中，主设备第一次显示控制中心页面200，包括但不限于发生在以下场景：
场景1：主设备在操作系统初始化之后，第一次显示控制中心页面200。例如：主设备是一个全新的设备，主设备在首次开机之后，用户会对主设备进行初始化设置，在初始化设置完成之后，用户操作主设备第一次显示控制中心页面200。
场景2：主设备在登录的账号发生变化之后，第一次显示控制中心页面200。例如：用户A将其账号从主设备上退出之后，将主设备交给用户B使用，用户B在主设备上登录了一个新的账号，在新的账号登录之后，用户B操作主设备第一次显示控制中心页面200。
场景3：主设备在恢复出厂设置或者清空数据之后，第一次显示控制中心页面200。
如图4D的页面(a)所示，在一种实现方式中，控制中心页面200不包括多设备协同卡 片210时，可以包括一个或者多个功能开关按钮，例如：Wi-Fi开关按钮201、蓝牙开关按钮202、手电筒开关按钮203、振动开关按钮204、静音开关按钮205等。当用户点击某个开关按钮时，主设备可以开启或者关闭相应的功能。控制中心页面200还可以包括一个或者多个滑动控件，例如用于调整显示屏亮度的滑动控件206。
如图4D的页面(a)所示，在一种实现方式中，如果主设备此后没有搜索到从设备，则说明该用户当前所处的环境可能不具备多设备协同的条件，该用户可能不是一个多设备协同的潜在用户，因此，主设备可以继续不显示多设备协同卡片210，使控制中心页面200中不会出现用户不需要的卡片，避免对用户造成打扰。
如图4D的页面(b)所示，在一种实现方式中，如果主设备此后搜索到了从设备，则说明该用户当前所处的环境具备多设备协同的条件，该用户可能是一个多设备协同的潜在用户，因此，主设备可以在控制中心页面200中显示多设备协同卡片210，多设备协同卡片210中可以包括卡片名称211，以及一个或者多个可点击的元素，例如：多设备协同卡片210的关闭图标212，以及多设备协同主页面的入口按钮213。
如果主设备第一次在控制中心页面200中显示了多设备协同卡片210，那么，主设备在下一次显示控制中心页面200时，可以直接显示多设备协同卡片210，其中，根据主设备搜索从设备的三个状态，多设备协同卡片210可以是图4A-图4C中的其中一种样式。
如图4D所示，在一种实现方式中，主设备还可以响应于用户点击17多设备协同卡片210中的关闭图标212的操作，关闭多设备协同卡片210。如果用户关闭了多设备协同卡片210，那么，主设备在下一次显示控制中心页面200时，可以不显示多设备协同卡片210。或者，主设备可以判断用户在预设时长内连续关闭多设备协同卡片210的次数大于或者等于第一阈值；如果大于或者等于第一阈值，则主设备在下一次显示控制中心页面200时，不显示多设备协同卡片210；如果小于第一阈值，则主设备在下一次显示控制中心页面200时，继续显示多设备协同卡片210。例如：当预设时长为24小时(一天)、第一阈值为2次时，如果用户在24小时之内连续2次关闭多设备协同卡片210，那么，主设备在下一次显示控制中心页面200时，不显示多设备协同卡片210。
在一种实现方式中，控制中心页面200还可以包括编辑图标207。如果用户想要将多设备协同卡片210恢复显示，可以点击18控制中心的编辑图标207。主设备可以响应于用户点击18编辑图标207的操作，进入到控制中心的编辑页面。这样，用户可以在控制中心的编辑页面对控制中心所显示的内容进行配置，例如：将多设备协同卡片210恢复显示等。
在一种实现方式中，在多设备协同卡片210关闭之后，如果用户关闭了控制中心，并在此后通过手指在显示屏的顶部边缘向下滑动等操作，再一次打开了控制中心，那么，主设备可以在搜索到周围存在从设备的情况下，将多设备协同卡片210恢复显示。如果主设备没有搜索到从设备，则可以将多设备协同卡片210保持关闭状态。
步骤S102，主设备响应于用户在多设备协同卡片210中的操作，从所述至少一个从设备中确定目标设备，并基于第一协同类型向目标设备发起多设备协同。
图5是本申请实施例提供的一种多设备协同方法的第一组交互示例图。
如图5所示，如果用户想要将主设备与搜索到的某个从设备建立多设备协同，可以在多设备协同卡片210中，对这个从设备的设备标识执行预设的一个或者多个操作，例如：点击12这个从设备的设备标识214。主设备可以响应于用户点击12这个从设备的设备标识214的操作，将这个从设备确定为目标设备，并基于第一协同类型向目标设备发起多设备协同。
其中：如果主设备与目标设备之间仅支持一种的协同类型，那么该协同类型就是第一协同类型。如果主设备与目标设备之间支持多种的协同类型，第一协同类型可以是主设备与目标设备之间支持的协同类型中的其中一个协同类型。
在一种可能的实现方式中，主设备与目标设备之间支持多种协同类型的场景下：如果主设备与目标设备是第一次建立多设备协同，那么第一协同类型可以是默认的两个设备的协同类型；如果主设备与目标设备不是第一次建立多设备协同，那么第一协同类型可以是双方上一次建立多设备协同时所采用的协同类型，也可以是默认的两个设备的协同类型。
一般来说，主设备与每一个类型的电子设备之间都可以预先设置有一个默认协同类型，并且，主设备与不同类型的电子设备之间的默认协同类型可以不同。例如：如果主设备是手机、目标设备是平板电脑，那么默认协同类型可以是多屏协同；如果主设备是手机、目标设备是大屏设备，那么默认协同类型可以是投屏；如果主设备是PC、目标设备是PC，那么默认协同类型可以是屏幕镜像。主设备可以将其与各个类型的电子设备的默认协同类型预先进行存储，例如：可以存储在主设备本地，也可以存储在云端。
步骤S103，主设备与目标设备建立多设备协同之后，将目标设备的设备标识切换为第一协同类型的协同标识。
如图5所示，协同标识219与设备标识214类似，也可以是一个图形化标识，例如图标，或者其他拟物化元素等。例如：如果主设备与目标设备建立了多屏协同，那么主设备可以将目标设备的设备标识切换为多屏协同标识；如果主设备与目标设备建立了屏幕镜像，那么主设备可以将目标设备的设备标识切换为屏幕镜像标识。这样，用户可以在多设备协同卡片210中直观地了解主设备与目标设备之间已建立的协同类型。
在一种实现方式中，主设备与目标设备建立多设备协同之后，还可以在多设备协同卡片210中显示第一协同类型的类型名称221。第一协同类型的类型名称221可以与目标设备的设备名称215集中显示，例如：第一协同类型的类型名称221可以与目标设备的设备名称215相邻显示在同一行，或者，第一协同类型的类型名称221可以与目标设备的设备名称215相邻显示在同一列。
如图5所示，以目标设备为荣耀笔记本、第一协同类型为多屏协同为例，在主设备与荣耀笔记本建立多屏协同之后，主设备可以将多设备协同卡片210中的荣耀笔记本的设备标识切换为多屏协同标识，并且在设备名称“荣耀笔记本”下方增加类型名称“多屏协同”。这样，用户可以在多设备协同卡片210中直观地了解到主设备已经与荣耀Pad建立了多屏协同。
在一种实现方式中，主设备可以在多设备协同卡片210中，将各个从设备的设备标识214显示为一种预设的颜色，例如第一颜色。如果主设备与目标设备基于第一协同类型建立了多设备协同，主设备可以在多设备协同卡片210中，将第一协同类型的协同标识219显示为另一种预设的颜色，例如第二颜色。这样，用户可以通过不同颜色来分辨哪些从设备与主设备建立了多设备协同，哪些从设备未与主设备建立多屏协同。
如图5所示，在一种实现方式中，主设备与目标设备建立多设备协同之后，还可以响应于用户点击13第一协同类型的协同标识219的操作，与目标设备断开多设备协同。主设备与目标设备断开多设备协同之后，可以将第一协同类型的协同标识219切换回目标设备的设备标识。这样，多设备协同卡片210可以恢复到建立多设备协同之前的样式。
本申请实施例提供的方法，在主设备的控制中心页面中增加了多设备协同卡片，多设备协同卡片中包含了主设备周围的各个从设备的设备标识，这样，用户可以通过点击任意从设 备的设备标识的操作，使主设备与任意从设备建立多设备协同，不需要用户在不同的用户界面中去寻找各种协同类型的控制入口，提高了用户使用体验。
在一些实施例中，主设备还可以响应于用户对多设备协同卡片执行的操作，显示多设备协同主页面。其中，对于主设备与目标设备已建立多设备协同，以及，主设备与目标设备未建立多设备协同这两种情形，多设备协同主页面中包含的内容可以是不同的，下面结合附图进行示例性说明。
图6是本申请实施例提供的一种多设备协同方法的第二组交互示例图。
如图6所示，对于主设备与目标设备未建立多设备协同的情形，如果用户想要打开多设备协同主页面300，可以对多设备协同卡片210中的任意从设备的设备标识214执行的长按14操作。主设备可以响应于用户对任意从设备的设备标识214执行的长按14操作，显示多设备协同主页面300。
如图6所示，对于主设备与目标设备未建立多设备协同的情形，如果用户想要打开多设备协同主页面300，还可以对多设备协同卡片210中的入口按钮213执行点击操作。主设备可以响应于用户点击16入口按钮213的操作，显示多设备协同主页面300。
如图6所示，对于主设备与目标设备未建立多设备协同的情形，多设备协同主页面300可以包括主设备的设备标识301以及各个从设备的设备标识214。其中，主设备的设备标识301可以位于多设备协同主页面300的中心区域例如：位于多设备协同主页面300的正中心、中心偏下区域、中心偏上区域等，本申请实施对此不做限定。从设备的设备标识214可以分布在主设备的设备标识301的外围。
在一种实现方式中，主设备的设备标识301位于多设备协同主页面300的中心偏下区域。各个从设备的设备标识214，例如：平板电脑的设备标识、大屏设备的设备标识、PC的设备标识、手机的设备标识可以呈行星状分布在主设备的设备标识301的周围。另外，从设备的设备标识214也可以分布在主设备的设备标识301的上方，或者分布在主设备的设备标识301的上方等，本申请实施对此不做限定。
在一种实现方式中，多设备协同主页面300中的设备标识与多设备协同卡片210中的设备标识可以采用不同的视觉样式。例如：多设备协同卡片210中的设备标识可以由设备图标和背景色组成，而多设备协同主页面300中的设备标识可以是包裹设备图标的水泡元素，或者包裹设备图标的气泡元素等。另外，在多设备协同主页面300中，主设备的设备标识301和从设备的设备标识214可以为不同颜色，以便于用户区分。例如：主设备的设备标识301可以为蓝色的水泡元素，从设备的设备标识214可以为白色(或透明色)的水泡元素。另外，在多设备协同主页面300中，主设备的设备标识301和从设备的设备标识214可以为不同尺寸，以便于用户区分。例如：主设备的设备标识301尺寸可以大于从设备的设备标识214尺寸。
在一种实现方式中，多设备协同主页面300还可以包括各个从设备的设备名称215，设备名称215可以与其对应的设备标识214协同显示，例如设备名称可以显示在其对应的设备标识214的上方，下方，或者其他位置。本申请实施例中，设备名称215可以是从设备的产品名称，例如：荣耀Smart TV、荣耀Pad、荣耀Magic Book等，设备名称215还可以是用户自定义的名称，例如：小李的荣耀平板、客厅的荣耀智慧屏等，本申请实施例对此不做限定。
图7是本申请实施例提供的一种多设备协同方法的第三组交互示例图。
如图7所示，对于主设备与目标设备已建立多设备协同的情形，如果用户想要打开多设备协同主页面300，可以对多设备协同卡片210中的任意从设备的设备标识214执行的长按14操作。主设备可以响应于用户对任意从设备的设备标识214执行的长按14操作，显示多设备协同主页面300。
如图7所示，对于主设备与目标设备已建立多设备协同的情形，如果用户想要打开多设备协同主页面300，还可以对多设备协同卡片210中的任意协同类型的协同标识219执行长按15操作。主设备可以响应于用户对任意协同类型的协同标识219执行的长按15操作，显示多设备协同主页面300。
如图7所示，对于主设备与目标设备已建立多设备协同的情形，如果用户想要打开多设备协同主页面300，还可以对多设备协同卡片210中的入口按钮213执行点击操作。主设备可以响应于用户点击16入口按钮213的操作，显示多设备协同主页面300。
如图7所示，对于主设备与目标设备已建立多设备协同的情形，入口按钮多设备协同主页面300可以包括主设备与目标设备之间的协同标识219以及各个从设备的设备标识214。其中，协同标识219可以位于多设备协同主页面300的中心区域，例如：位于多设备协同主页面300的正中心、中心偏下区域、中心偏上区域等，本申请实施对此不做限定。从设备的设备标识214可以分布在协同标识的外围。协同标识219的上方或者下方等临近位置还可以包括目标设备的设备名称215和协同类型的类型名称402。
在一种实现方式中，协同标识219可以位于多设备协同主页面300的中心偏下区域。各个从设备的设备标识214，例如：平板电脑的设备标识、大屏设备的设备标识、PC的设备标识、手机的设备标识可以呈行星状分布在协同标识的周围。
在一种实现方式中，协同标识219和从设备的设备标识214可以为不同颜色，以便于用户区分。例如：协同标识219可以为蓝色的水泡元素，从设备的设备标识214可以为白色(或透明色)的水泡元素。另外，在多设备协同主页面300中，协同标识219和从设备的设备标识214可以为不同尺寸，以便于用户区分。例如：协同标识219尺寸可以大于从设备的设备标识214尺寸。
图8是本申请实施例提供的一种多设备协同方法的第二个流程图。
图9A-图9D是本申请实施例提供的一种多设备协同方法的第四组交互示例图。
如图8所示，在一种实现方式中，该方法可以包括以下步骤S201-S203：
步骤S201，主设备响应于用户在多设备协同主页面执行的操作，确定目标设备，并基于第一协同类型，与目标设备建立多设备协同。
具体实现中，如图9A所示，在主设备未与从设备建立多设备协同的情况下，用户如果想要将主设备与某个从设备建立多设备协同，可以在多设备协同主页面300中，将这个从设备的设备标识214向主设备的设备标识301方向拖动21。主设备可以响应于用户拖动21从设备的设备标识214的操作，将这个从设备确定为目标设备。
当用户将目标设备的设备标识214拖动至与主设备的设备标识301相接触时，主设备基于第一协同类型，向目标设备发起多设备协同。与此同时，如图9B所示，主设备可以在多设备协同主页面300中呈现出主设备的水泡元素与目标设备的水泡元素正在融合的效果，以形象化地将正在建立多设备协同的状态反馈给用户。
主设备与目标设备成功建立多设备协同时，如图9C所示，可以将多设备协同主页面300中的主设备的设备标识301切换为第一协同类型的协同标识401，例如将出主设备的水泡元 素与目标设备的水泡元素融合形成第一协同类型的水泡元素。另外，主设备还可以在第一协同类型的协同标识401的上方或者下方等临近位置显示目标设备的设备名称215和第一协同类型的类型名称402。
其中：如果主设备与目标设备之间仅支持一种的协同类型，那么该协同类型就是第一协同类型。如果主设备与目标设备之间支持多种的协同类型，第一协同类型可以是主设备与目标设备之间支持的协同类型中的其中一个协同类型。例如，如果主设备与目标设备是第一次建立多设备协同，那么第一协同类型可以是默认的两个设备的协同类型，如果主设备与目标设备不是第一次建立多设备协同，那么第一协同类型可以是双方上一次建立多设备协同时所采用的协同类型，也可以是默认的两个设备的协同类型。
步骤S202，主设备在多设备协同主页面中显示类型切换卡片。
其中，类型切换卡片310可以显示在第一协同类型的协同标识401的上方、下方等相邻位置，本申请实施例对此不做限定。
这里需要补充说明的是，本申请实施例中，如果主设备基于第一协同类型与目标设备建立了多设备协同，主设备可以直接在多设备协同主页面中显示类型切换卡片，而不需要用户再执行任何操作。例如：主设备可以在与目标设备成功建立多设备协同的同时，显示类型切换卡片；或者，主设备也可以在与目标设备成功建立多设备协同之后，立即显示类型切换卡片。
如图9C所示，类型切换卡片310中可以包括主设备与目标设备支持的一个或者多个协同类型的协同标识。其中，主设备可以在类型切换卡片310中显示其与目标设备支持的每一个协同类型的协同标识，也可以在类型切换卡片310中显示其与目标设备支持的部分协同类型的协同标识，例如：仅显示第一协同类型的协同标识401以外的其他协同类型的协同标识403。本申请实施例对此不做限定。
如图9C所示，以主设备为手机、目标设备为PC为例，手机与PC支持的协同类型可以包括多屏协同和超级键鼠。那么，在手机与PC建立多屏协同之后，类型切换卡片310中可以包括多屏协同标识和超级键鼠标识。
在一种实现方式中，如果类型切换卡片310中既包含第一协同类型的协同标识401，也包含其他协同类型的协同标识403，那么，第一协同类型的协同标识401与其他协同类型的协同标识403可以显示为不同的颜色，以便于用户区分。
在一种实现方式中，类型切换卡片310中还可以包括断开连接按钮311。如果用户想断开主设备与目标设备的多设备协同，可以点击23断开连接按钮311。主设备可以响应于用户点击23断开连接按钮311的操作，断开与目标设备之间的多设备协同，将第一协同类型的协同标识恢复为主设备的设备标识301，并将目标设备的设备标识214恢复显示在其原有位置。例如：主设备可以将第一协同类型的水泡元素分化成主设备的水泡元素与目标设备的水泡元素，然后将目标设备的水泡元素移动至其原有位置，从而使多设备协同主页面300恢复到如图9A的状态。
这里需要补充说明的是，当主设备与目标设备之间只支持一个协同类型时，类型切换卡片310可以包括这个支持的协同类型的类型标识和断开连接按钮311，也可以仅包括断开连接按钮311，本申请实施例对此不做限定。
步骤S203，主设备响应于用户对类型切换卡片执行的操作，确定第二协同类型，并将主设备与目标设备之间的协同类型从第一协同类型切换至第二协同类型。
其中，第二协同类型可以是类型切换卡片310中包含的多个协同类型中的一个。
具体实现中，如图9C所示，用户如果想要将主设备与目标设备之间的协同类型从第一协同类型切换为其他的协同类型，可以在类型切换卡片310中点击22任意一个协同类型的协同标识403。主设备可以响应于用户点22击任意一个协同类型的协同标识403的操作，将这个协同类型确定为第二协同类型，并将主设备与目标设备之间的协同类型从第一协同类型切换至第二协同类型。
具体实现中，主设备可以在不断开与目标设备的多设备协同的状态下，直接基于第二协同类型向目标设备发起切换请求，使主设备与目标设备切换至第二协同类型。进一步地，如图9D所示，主设备与目标设备基于第二协同类型建立多设备协同之后，可以将多设备协同主页面300中的第一协同类型的协同标识401切换为第二协同类型的协同标识403。另外，主设备也可以先断开与目标设备的多设备协同，然后基于第二协同类型，再次向目标设备发起多设备协同，以使主设备与目标设备基于第二协同类型重新建立多设备协同。
在一种实现方式中，主设备在显示类型切换卡片310之后，如果检测到用户在此后预设的一段时长内没有对类型切换卡片310进行任何操作，则可以关闭类型切换卡片310。该预设时长可以是3秒、5秒等，本申请实施例对此不做限定。
在主设备关闭类型切换卡片310之后，如果用户想要让主设备重新显示类型切换卡片310，可以在多设备协同主页面300中点击第一协同类型(或第二协同类型)的协同标识401，主设备可以响应于用户的点击操作，重新显示类型切换卡片310。
本申请实施例提供的方法，当主设备与目标设备支持多种协同类型时，主设备与目标设备可以先基于预设的协同类型建立多设备协同，然后，用户可以在主设备的控制中心选择期望使用的协同类型，主设备可以基于用户的选择，从预设的协同类型切换到用户期望使用的协同类型，提高了用户使用体验。
图10A-图10D是本申请实施例提供的一种多设备协同方法的第五组交互示例图。下面结合图10A-图10D，以主设备为平板电脑，从设备为PC为例，对本申请实施例提供的多设备协同方法的步骤S201-S203所对应的交互场景进行示例性说明。
如图10A所示，如果用户想要将平板电脑与PC建立多设备协同，可以在多设备协同主页面300中，将PC的水泡元素431向平板电脑的水泡元素432方向拖动27。当用户将PC的水泡元素431拖动至与平板电脑的水泡元素432相接触时，平板电脑向PC发起默认类型的多设备协同，例如：屏幕镜像。与此同时，如图10B所示，平板电脑可以在多设备协同主页面300中呈现出其水泡元素432与PC的水泡元素431正在融合的效果，以形象化地将正在建立多设备协同的状态反馈给用户。
如图10C所示，平板电脑与PC成功建立屏幕镜像时，可以将平板电脑的水泡元素432与PC的水泡元素431融合形成屏幕镜像的水泡元素433，并且在屏幕镜像的水泡元素433下方显示类型切换卡片310。
其中，类型切换卡片310中可以包括平板电脑与PC支持的一个或者多个协同类型的协同标识，例如：屏幕镜像标识461、屏幕扩展标识462、超级键鼠标识463。
用户如果想要切换平板电脑与PC之间的协同类型，例如：将平板电脑与PC之间的协同类型从屏幕镜像切换为超级键鼠，可以在类型切换卡片310中点击28超级键鼠标识463。平板电脑可以响应于用户操作，将平板电脑与PC之间的协同类型从屏幕镜像切换为超级键鼠。
如图10D所示，平板电脑与PC建立超级键鼠之后，可以将多设备协同主页面300中的 屏幕镜像的水泡元素433切换为超级键鼠的水泡元素434。
图11A-图11D是本申请实施例提供的一种多设备协同方法的第六组交互示例图。
下面结合图11A-图11D，以主设备为PC，从设备为平板电脑为例，对本申请实施例提供的多设备协同方法的步骤S201-S203所对应的交互场景进行示例性说明。
如图11A所示，如果用户想要将PC与平板电脑建立多设备协同，可以在多设备协同主页面300中，通过鼠标的拖拽操作，将平板电脑的水泡元素441向PC的水泡元素442方向拖动29。当用户将平板电脑的水泡元素441拖动至与PC的水泡元素442相接触时，PC向平板电脑发起默认类型的多设备协同，例如：屏幕镜像。与此同时，如图11B所示，PC可以在多设备协同主页面300中呈现出其水泡元素442与平板电脑的水泡元素441正在融合的效果，以形象化地将正在建立多设备协同的状态反馈给用户。
如图11C所示，PC与平板电脑成功建立屏幕镜像时，可以将PC的水泡元素442与平板电脑的水泡元素441融合形成屏幕镜像的水泡元素443，并且在多屏协同标识401下方显示类型切换卡片310。
其中，类型切换卡片310中可以包括PC与平板电脑支持的一个或者多个协同类型的协同标识，例如：屏幕镜像标识461、屏幕扩展标识462、超级键鼠标识463。
用户如果想要切换PC与平板电脑之间的协同类型，例如：将PC与平板电脑之间的协同类型从多屏协同切换为超级键鼠，可以在类型切换卡片310中点击31超级键鼠标识463。主设备可以响应于用户操作，将PC与平板电脑之间的协同类型从屏幕镜像切换为超级键鼠。
如图11D所示，PC与平板电脑建立超级键鼠之后，可以将多设备协同主页面300中的屏幕镜像的水泡元素443切换为超级键鼠的水泡元素444。
图12A-图12D是本申请实施例提供的一种多设备协同方法的第七组交互示例图。
下面以主设备为折叠屏手机，从设备为PC为例，对本申请实施例提供的多设备协同方法的步骤S201-S203所对应的交互场景进行示例性说明。这里需要说明的是，折叠屏手机通常可以工作在两种形态，一种是机身折叠状态，另一种是机身展开状态。其中，折叠屏手机处于机身折叠状态时，相当于一部传统形态的手机，其与PC之间支持的协同类型与传统形态的手机相同，例如可以包括：多屏协同和超级键鼠；折叠屏手机处于机身展开状态时，相对于传统形态的手机是一种新的产品形态，其与PC之间支持的协同类型与传统形态的手机不同，例如可以包括：多屏协同、屏幕镜像、屏幕扩展、超级键鼠。
下面结合图12A-图12D，以折叠屏手机处于机身展开状态时的交互场景进行示例性说明。
如图12A所示，如果用户想要将折叠屏手机与PC建立多设备协同，可以在多设备协同主页面300中，将PC的水泡元素451向折叠屏手机的水泡元素452方向拖动32。当用户将PC的水泡元素451拖动至与折叠屏手机的水泡元素452相接触时，折叠屏手机向PC发起默认类型的多设备协同，例如：多屏协同。与此同时，如图12B所示，折叠屏手机可以在多设备协同主页面300中呈现出其水泡元素452与PC的水泡元素451正在融合的效果，以形象化地将正在建立多设备协同的状态反馈给用户。
如图12C所示，折叠屏手机与PC成功建立多屏协同时，可以将折叠屏手机的水泡元素452与PC的水泡元素451融合形成多屏协同的水泡元素453，并且在多屏协同标识401下方显示类型切换卡片310。
其中，类型切换卡片310中可以包括折叠屏手机与PC支持的一个或者多个协同类型的协同标识，例如：屏幕镜像标识461、屏幕扩展标识462、超级键鼠标识463、多屏协同标识 464。
用户如果想要切换折叠屏手机与PC之间的协同类型，例如：将折叠屏手机与PC之间的协同类型从多屏协同切换为超级键鼠，可以在类型切换卡片310中点击33超级键鼠标识463。主设备可以响应于用户操作，将折叠屏手机与PC之间的协同类型从多屏协同切换为超级键鼠。
如图12D所示，折叠屏手机与PC建立超级键鼠之后，可以将多设备协同主页面300中的多屏协同的水泡元素453切换为超级键鼠的水泡元素454。
图13A-图13C是本申请实施例示出的自动协同服务的开启和关闭方式的示例图。
如图13A和图13B所示，在一种实现方式中，多设备协同主页面300还可以包括设置按钮302，该设置按钮302可以设置在多设备协同主页面300的任意位置，例如多设备协同主页面300的右上角。
以主设备为手机为例，如果用户想要对多设备协同进行设置，则可以点击24设置按钮302。手机可以响应于用户的点击24操作，进入到多设备协同的设置页面400，该设置页面400例如可以包括协同服务列表410，以及，从设备列表420。
协同服务列表410可以包括一个或者多个可设置的协同服务的选项，例如：超级接续、超级通话、超级通知和超级键鼠等；以及每个协同服务状态，例如：已开启或者已关闭。从设备列表可以包括有手机已经搜索到的附近的从设备的名称和类型，以及曾经与手机建立过多设备协同的设备名称和类型。
如图13B和图13C所示，接下来，如果用户想要设置某个协同服务的服务状态，则可以在协同服务列表410中点击25这个协同服务的选项。手机可以响应于用户的点击25操作，进入到这个协同服务的子页面500，该子页面500例如可以包括这个协同服务的开关按钮501。接下来，用户可以通过点击26开关按钮501的方式，开启或关闭这个协同服务。
示例性的，当用户在协同服务列表410中点击25“超级通话”时，手机可以进入到超级通话的子页面500，超级通话的子页面500中可以包括超级通话的功能描述信息502，以及超级通话的开关按钮501。当开关按钮501为开启状态时，如果用户点击26开关按钮501，可以关闭超级通话服务，当开关按钮501为关闭状态时，如果用户点击26开关按钮501，可以开启超级通话服务。
本申请实施例提供的方法，用户可以从多设备协同主页面直接进入到多设备协同的设置页面，以对自动协同服务进行开启和关闭等控制，提高了用户使用体验。
在多设备协同场景中，主设备在某一时间可能会存在以下三种状态：
状态A：主设备未与其他设备建立多设备协同(简称：主设备未协同)；
状态B：主设备与从设备正在进行多设备协同；
状态C：主设备与环外设备正在进行多设备协同。
其中，状态B和状态C可以简称为：主设备未协同。
在多设备协同场景中，从设备在某一时间可能会存在以下三种状态：
状态a：从设备未与其他设备建立多设备协同(简称：从设备未协同)；
状态b：从设备与其他从设备正在进行多设备协同；
状态c：从设备与环外设备正在进行多设备协同。
其中，状态b和状态c可以简称为：从设备未协同。
基于上述各种状态，在建立主设备与目标设备的多设备协同时，可能会出现以下4类场 景和8个子场景：
场景一：主设备、目标设备均未协同。
场景二：主设备协同、目标设备未协同。场景二可以包括以下两个子场景：
子场景1：主设备与其他从设备正在进行多设备协同；
子场景2：主设备与环外设备正在进行多设备协同。
场景三：主设备未协同、目标设备协同。场景三可以包括以下两个子场景：
子场景3：目标设备与其他从设备正在进行多设备协同；
子场景4：目标设备与环外设备正在进行多设备协同；
场景四：主设备协同、从设备协同。场景四可以包括以下四个子场景：
子场景5：主设备与其他从设备正在进行多设备协同，目标设备与其他从设备正在进行多设备协同；
子场景6：主设备与其他从设备正在进行多设备协同，目标设备与环外设备正在进行多设备协同；
子场景7：主设备与环外设备正在进行多设备协同，目标设备与其他从设备正在进行多设备协同；
子场景8：主设备与环外设备正在进行多设备协同，目标设备与环外设备正在进行多设备协同。
对于不同的场景和子场景，当用户拖动目标设备的设备标识，使目标设备的设备标识与主设备的设备标识相接触时，主设备和目标设备可以有不同的响应方式。下面结合一些示例，进行具体说明。
对于场景一，多设备协同方法可以包括以下步骤：主设备响应于用户拖动目标设备的设备标识，使目标设备的设备标识与主设备的设备标识相接触的操作，基于第一协同类型，与目标设备建立多设备协同，并且在多设备协同主页面300中显示类型切换卡片310。
该步骤具体也可以参照上述步骤S201-步骤S202。
图14是本申请实施例提供的多设备协同方法的场景一的交互示例图。
如图14所示，以主设备为手机、目标设备为PC(例如：荣耀笔记本)、第一协同类型为多屏协同为例。
如果用户想要将手机与PC建立多设备协同，可以在多设备协同主页面中将PC的水泡元素601向手机的水泡元素602方向拖动61。当用户将PC的水泡元素601拖动61至与手机的水泡元素602相接触，然后抬起手指时，手机向PC发起多屏协同。与此同时，手机可以在多设备协同主页面中呈现出手机的水泡元素602与PC的水泡元素601呈融合状态的效果，以形象化地将正在建立多设备协同的状态反馈给用户。手机与PC成功建立多屏协同时，手机的水泡元素602与PC的水泡元素601完全融合，形成多屏协同的水泡元素603。手机还可以在多屏协同的水泡元素603的上方(或者其他临近位置)显示PC的设备名称“荣耀智慧屏”和协同类型“多屏协同”。手机还可以在多屏协同的水泡元素603的下方(或者其他临近位置)显示类型切换卡片310，关于类型切换卡片310的具体实现方式，请参照上文针对图9C记载的内容，这里不再赘述。
对于场景二种的子场景1，可以包括两种情况。第一种情况是主设备与其他从设备正在进行的多设备协同不支持三个设备同时接入，例如主设备与其他从设备正在进行的多设备协同为除了超级键鼠以外的其他协同类型；第二种情况是主设备与其他从设备正在进行的多设 备协同支持三个设备同时接入，例如：超级键鼠。以下为便于描述，将不支持三个设备同时接入的协同类型称作第三协同类型，将基于第三协同类型建立的多设备协同称作第一多设备协同；将支持三个设备同时接入的协同类型称作第四协同类型，将基于第四协同类型建立的多设备协同称作第二多设备协同。
对于第一种情况，多设备协同方法可以包括以下步骤：主设备与第一从设备建立第一多设备协同的状态下，响应于用户拖动目标设备的设备标识，使目标设备的设备标识与第三协同类型的协同标识相接触的操作，显示切换询问卡片。其中，该切换卡片用于询问用户是否切换协同设备。
图15是本申请实施例提供的一种多设备协同方法的子场景1的第一个交互示例图。
如图15所示，以主设备为手机、第一从设备为平板电脑(例如：荣耀PAD)、目标设备为PC(例如：荣耀笔记本)、第三协同类型为多屏协同为例。手机与平板电脑建立有多屏协同时，多设备协同主页面可以显示多屏协同的水泡元素611。如果用户想要将手机与PC建立多设备协同，可以在多设备协同主页面中将PC的水泡元素612向多屏协同的水泡元素611方向拖动62。当用户将PC的水泡元素612拖动62至与多屏协同的水泡元素611相接触，然后抬起手指时，手机在多设备协同主页面中显示荣耀笔记本的水泡元素612与手机的水泡元素613呈融合状态的效果，并显示切换询问卡片710。
如图15所示，切换询问卡片710可以包括用于询问用户是否切换协同设备的询问信息711，例如“连接新设备会终止当前与荣耀PAD的多屏协同，是否继续？”。另外，切换询问卡片还包括“确定”按钮712和“取消”按钮713。如果用户点击63“确定”按钮712，手机会结束与平板电脑的多屏协同，并基于默认的或者上一次使用的协同类型与PC建立多设备协同，例如：如果手机上一次与PC建立了多屏协同，那么，如果用户点击63“确定”按钮712，手机会与PC建立多屏协同。如果用户点击“取消”按钮713，手机会继续与平板电脑保持多屏协同状态。
在一种实现方式中，切换询问卡片还可以包括免打扰选项714，该免打扰选项714可以包括用于引导用户对其进行选中和取消选中的提示信息，例如“不再提示”。如果用户选中免打扰选项，主设备此后在相同场景下，不会再显示切换询问卡片，而是直接对用户操作进行响应，例如：如果用户将PC的水泡元素612向多屏协同的水泡元素611方向拖动，并与多屏协同的水泡元素611相接触，手机可以直接结束与平板电脑的多屏协同，并建立与PC的多设备协同。
对于第二种情况，多设备协同方法可以包括以下步骤：主设备与第一从设备建立第二多设备协同的状态下，响应于用户拖动目标设备的设备标识，使目标设备的设备标识与第四协同类型的协同标识相接触的操作，将目标设备加入到第二多设备协同。
图16是本申请实施例提供的一种多设备协同方法的子场景1的第二个交互示例图。
如图16所示，以主设备为手机、第一从设备为PC(例如：荣耀笔记本)、目标设备为平板电脑(例如：荣耀PAD)、第四协同类型为超级键鼠为例。手机与PC建立有超级键鼠时，多设备协同主页面可以显示超级键鼠的水泡元素621。如果用户想要将平板电脑也加入到超级键鼠，可以在多设备协同主页面中将平板电脑的水泡元素622向超级键鼠的水泡元素621方向拖动64。当用户将平板电脑的水泡元素622拖动64至与超级键鼠的水泡元素621相接触，然后抬起手指时，手机向平板电脑发起超级键鼠。与此同时，手机可以在多设备协同主页面中呈现出超级键鼠的水泡元素621与平板电脑的水泡元素622呈融合状态的效果，以形 象化地将正在建立多设备协同的状态反馈给用户。平板电脑成功加入超级键鼠时，平板电脑的水泡元素622完全融合进超级键鼠的水泡元素621中。手机还可以在超级键鼠的水泡元素621的上方(或者其他临近位置)增加平板电脑的设备名称“荣耀PAD”。
对于场景二种的子场景2，多设备协同方法可以包括以下步骤：主设备与环外设备建立多设备协同的状态下，响应于用户拖动目标设备的设备标识，使目标设备的设备标识与多设备协同的协同标识相接触的操作，显示切换询问卡片。其中，该切换卡片用于询问用户是否切换协同设备。
图17是本申请实施例提供的一种多设备协同方法的子场景2的交互示例图。
如图17所示，以主设备为手机、目标设备为平板电脑1、环外设备为平板电脑2为例。手机与平板电脑2建立有多屏协同时，多设备协同主页面可以显示多屏协同的水泡元素631。如果用户想要将手机与平板电脑1建立多设备协同，可以在多设备协同主页面中将平板电脑1的水泡元素632向多屏协同的水泡元素631方向拖动65。当用户将平板电脑1的水泡元素拖动65至与多屏协同的水泡元素631相接触，然后抬起手指时，手机在多设备协同主页面中显示平板电脑1的水泡元素632与手机的水泡元素633呈融合状态的效果，并显示切换询问卡片720。
切换询问卡片720与图15示出切换询问卡片710类似，这里不再赘述。如果用户点击66“确定”按钮722，手机会结束与平板电脑2的多屏协同，并基于默认的或者上一次使用的协同类型与平板电脑1建立多设备协同，例如：如果手机上一次与平板电脑1建立了多屏协同，那么，如果用户点击66“确定”按钮722，手机会与平板电脑1建立多屏协同。如果用户点击“取消”按钮723，手机会继续与平板电脑2保持多屏协同状态。
对于场景三，多设备协同方法可以包括以下步骤：目标设备与其他从设备建立多设备协同，或者，目标从设备与环外设备建立多设备协同的状态下，主设备响应于用户拖动目标设备的设备标识，使目标设备的设备标识与多设备协同的协同标识相接触的操作，显示切换询问卡片。其中，该切换卡片用于询问用户是否切换协同设备。
图18是本申请实施例提供的一种多设备协同方法的场景三的第一个交互示例图。
如图18所示，以主设备为手机、目标设备为PC(例如：荣耀笔记本)为例。PC与其他从设备或者环外设备建立有多设备协同时，手机可以在多设备协同主页面中，为PC的水泡元素641增加一个状态标识642。该状态标识642例如可以是一个位于PC的水泡元素641右下角(也可以是其他位置)的图形角标。这样，通过状态标识，用户就可以了解到PC当前正在与除手机以外的其他设备进行多设备协同。
如果用户想要将手机与PC建立多设备协同，可以在多设备协同主页面中将PC的水泡元素641向手机的水泡元素643方向拖动67。当用户将PC的水泡元素641拖动67至与手机的水泡元素643相接触，然后抬起手指时，手机在多设备协同主页面中显示PC的水泡元素641与手机的水泡元素643呈融合状态的效果，并显示切换询问卡片730。
切换询问卡片730与图15示出切换询问卡片710类似，这里不再赘述。如果用户点击68“确定”按钮732，手机会结束PC与其他从设备或者环外设备的多设备协同，并基于默认的或者上一次使用的协同类型与PC建立多设备协同，例如：如果手机上一次与PC建立了多屏协同，那么，如果用户点击68“确定”按钮732，手机会与PC建立多屏协同，并将手机的水泡元素643切花为多屏协同的水泡元素644。如果用户点击“取消”按钮733，PC与其他从设备或者环外设备会继续保持多设备协同状态。
图19是本申请实施例提供的一种多设备协同方法的场景三的第二个交互示例图。
对于场景三，如果目标设备与其他从设备或者环外设备已建立的协同类型支持三个设备同时连接，例如：超级键鼠，并且主设备也支持这一协同类型，那么，主设备可以响应于用户拖动目标设备的设备标识，加入到目标设备当前已建立的多设备协同中。
如图19所示，以主设备为手机、目标设备为PC(例如：荣耀笔记本)为例。PC与其他设备(例如：荣耀PAD)建立有超级键鼠时，手机可以在多设备协同主页面中，为PC的水泡元素641增加一个超级键鼠的状态标识645。该状态标识645例如可以是一个位于PC的水泡元素641右下角(也可以是其他位置)的图形角标。这样，通过状态标识，用户就可以了解到PC当前正在与其他设备建立了超级键鼠。
如果用户想要将手机也加入到超级键鼠中，可以在多设备协同主页面中将PC的水泡元素641向手机的水泡元素643方向拖动67。当用户将PC的水泡元素641拖动67至与手机的水泡元素643相接触，然后抬起手指时，手机在多设备协同主页面中显示PC的水泡元素641与手机的水泡元素643呈融合状态的效果，以形象化地将正在建立多设备协同的状态反馈给用户。手机成功加入超级键鼠时，手机的水泡元素643与PC的水泡元素641完全融合，形成超级键鼠的水泡元素646。
对于场景四，多设备协同方法可以包括以下步骤：主设备与目标设备均与其他从设备或环外设备建立多设备协同的状态下，主设备响应于用户拖动目标设备的设备标识，使目标设备的设备标识与多设备协同的协同标识相接触的操作，显示切换询问卡片。其中，该切换卡片用于询问用户是否切换协同设备。
图20是本申请实施例提供的一种多设备协同方法的场景四的交互示例图。
如图20所示，以主设备为手机、目标设备为PC(例如：荣耀笔记本)为例。手机和PC均与其他从设备或者环外设备建立有多设备协同时，手机会在多设备协同主页面中显示其当前已建立的多设备协同的协同标识，例如，如果手机当前与平板电脑(例如：荣耀Pad)建立有多屏协同，那么，多设备协同主页面中可以显示多屏协同的水泡元素651。另外，手机可以在多设备协同主页面中，为PC的水泡元素652增加一个状态标识642，这样，通过状态标识642，用户就可以了解到PC当前正在与除手机以外的其他设备进行多设备协同。
如果用户想要将手机与PC建立多设备协同，可以在多设备协同主页面中将PC的水泡元素652向多屏协同的水泡元素651方向拖动69。当用户将PC的水泡元素652拖动69至与多屏协同的水泡元素651相接触，然后抬起手指时，手机在多设备协同主页面中显示PC的水泡元素652与手机的水泡元素653呈融合状态的效果，并显示切换询问卡片740。
切换询问卡片740与图15示出切换询问卡片类似，这里不再赘述。如果用户点击71“确定”按钮742，手机会结束其与其他从设备或者环外设备的多设备协同，还会结束PC与其他从设备或者环外设备的多设备协同，并基于默认的或者上一次使用的协同类型与PC建立多设备协同，例如：如果手机上一次与PC建立了多屏协同，那么，如果用户点击71“确定”按钮742，手机会与PC建立多屏协同。如果用户点击“取消”按钮743，手机和PC均与其他从设备或者环外设备会继续保持多设备协同状态。
本申请实施例提供的方法，在主设备和/或从设备已经建立了多设备协同的情况下，主设备可以响应于用户在多设备协同主页面中的操作，根据不同的场景，采用不同的策略对参与多设备协同的设备进行增加或者切换，提高了用户使用体验。
图21是本申请实施例提供的一种多设备协同方法的另一个交互示例图。
如图21所示，在某个从设备与其他从设备或者环外设备已建立多设备协同的情况下，如果用户想要查看这个从设备与其他哪个从设备或者环外设备正在进行多设备协同，可以在多设备协同主页面300中，点击81这个从设备的设备标识214。主设备可以响应于用户点击81这个从设备的设备标识214的操作，显示这个从设备的协同状态信息810，例如“XXX正在与XXX多屏协同”。该协同状态信息810可以在显示一段时间后，自行消失，从而不会影响到多设备协同主页面300显示其他信息。
本申请实施例提供的方法，在从设备与其他从设备或者环外设备已经建立了多设备协同的情况下，用户可以在多设备协同主页面中查看从设备的多设备协同信息，提高了用户使用体验。
图22是本申请实施例提供的一种多设备协同方法的又一个交互示例图。
如图22所示，如果某个从设备与其他从设备或者环外设备已建立多设备协同，主设备还可以在多设备协同卡片210中，为这个从设备的设备标识添加一个状态标识642。该状态标识例如可以是一个位于从设备的设备标识214右下角(也可以是其他位置)的图形角标。这样，通过状态标识642，用户就可以了解到这个从设备当前正在与除主设备以外的其他设备进行多设备协同。接下来，如果用户想要将主设备与这个从设备建立多设备协同，可以点击在多设备协同卡片210中点击91这个从设备的设备标识214。主设备响应于用户设备的点击91操作，在控制中心页面200显示切换询问卡片750，切换询问卡片750与图15示出切换询问卡片类似，这里不再赘述。如果用户点击“确定”按钮，主设备会结束这个从设备与其他从设备或者环外设备的多设备协同，并基于默认的或者上一次使用的协同类型与这个从设备建立多设备协同。如果用户点击“取消”按钮，这个从设备与其他从设备或者环外设备会继续保持多设备协同状态。
本申请实施例提供的方法，在从设备已经与其他从设备或者环外设备建立了多设备协同的情况下，用户可以在控制中心页面中直接对参与多设备协同的设备进行增加或者切换，提高了用户使用体验。
上述本申请提供的实施例对本申请提供的多设备协同方法的各方案进行了介绍。可以理解的是，电子设备为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
图23是本申请实施例提供的一种多设备协同装置的结构示意图。在一个实施例中，电子设备，例如第一电子设备，可以通过图23所示的硬件装置实现相应的功能。如图23所示，该多设备协同装置可以包括：显示屏1001、存储器1002、处理器1003和通信模块1004。上述各器件可以通过一个或多个通信总线1005连接。
在一个实施例中，显示屏1001可以包括显示面板10011和触摸传感器10012，其中，显示面板10011用于显示图像，触摸传感器10012可以将检测到的触摸操作传递给应用处理器，以确定触摸事件类型，通过显示面板10011提供与触摸操作相关的视觉输出。处理器1003可以包括一个或多个处理单元，例如：处理器1003可以包括应用处理器，调制解调处理器，图形处理器，图像信号处理器，控制器，视频编解码器，数字信号处理器，基带处理器，和/或 神经网络处理器等。其中，不同的处理单元可以是独立的器件，也可以集成在一个或多个处理器中。存储器1002与处理器1003耦合，用于存储各种软件程序和/或多组指令，存储器1002可包括易失性存储器和/或非易失性存储器。
当存储器1002中的软件程序和/或多组指令被处理器1003执行时，使得第一电子设备实现如下方法步骤：设备响应于用户操作，显示第一页面，第一页面包括第一电子设备的设备标识和至少一个从设备的设备标识；响应于用户对第一页面中的第一目标设备的设备标识的操作，基于第一协同类型与第一目标设备建立多设备协同，并在第一页面中显示类型切换卡片；其中，第一目标设备是至少一个从设备中的任意一个从设备，类型切换卡片包括第一电子设备与第一目标设备之间支持的至少一个协同类型的类型标识。
本申请实施例提供的装置，第一页面包含了第一电子设备周围的各个从设备的设备标识，这样，用户可以通过对任意从设备的设备标识的操作，使第一电子设备与任意从设备建立多设备协同，不需要用户在不同的用户界面中去寻找各种协同类型的控制入口，提高了用户使用体验。
当存储器1002中的软件程序和/或多组指令被处理器1003执行时，使得第一电子设备还实现如下方法步骤：响应于用户对类型切换卡片中的第二协同类型的类型标识的点击操作，将第一电子设备与第一目标设备之间的协同类型从第一协同类型切换至第二协同类型；其中，第二协同类型是至少一个协同类型中的任意一个协同类型，第一协同类型与第二协同类型不同。这样，当第一电子设备与第一目标设备支持多种协同模式时，第一电子设备与第一目标设备可以先基于预设的协同类型建立多设备协同，然后，用户可以在第一电子设备上选择其期望使用的协同类型，第一电子设备可以基于用户的选择，从预设的协同类型切换到用户期望使用的协同类型，提高了用户使用体验。
当存储器1002中的软件程序和/或多组指令被处理器1003执行时，使得第一电子设备实现如下方法步骤：响应于用户操作，显示第二页面，第二页面包括多设备协同卡片，其中，如果第一电子设备搜索到至少一个从设备，多设备协同卡片中包括至少一个从设备的设备标识；响应于用户在多设备协同卡片中的操作，基于第三协同类型向第二目标设备发起多设备协同，第二目标设备是至少一个从设备中的任意一个从设备；与第二目标设备建立多设备协同之后，将多设备协同卡片中的第二目标设备的设备标识切换为第三协同类型的协同标识。
本申请实施例提供的装置，第一电子设备的第二页面中增加了多设备协同卡片，多设备协同卡片中包含了第一电子设备周围的各个从设备的设备标识，这样，用户可以通过点击任意从设备的设备标识的操作，使第一电子设备与任意从设备建立多设备协同，不需要用户在不同的用户界面中去寻找各种协同类型的控制入口，提高了用户使用体验。
在一种实现方式中，当存储器1002中的软件程序和/或多组指令被处理器1003执行时，使得第一电子设备还实现如下方法步骤：响应于用户在多设备协同卡片中点击第三协同类型的协同标识的操作，结束第一电子设备与第二目标设备之间的多设备协同。这样，用户可以在多设备协同卡片中直接结束已建立的多设备协同，不需要在不同的用户界面中去寻找各种协同类型的控制入口，提高了用户使用体验。
在一种实现方式中，当存储器1002中的软件程序和/或多组指令被处理器1003执行时，使得第一电子设备还实现如下方法步骤：如果未搜索到从设备，并且当前正在搜索从设备，多设备协同卡片中包括第一动效标识，第一动效标识用于指示第一电子设备正在搜索从设备的状态。这样，第一电子设备可以将其正在搜索从设备的状态反馈给用户，提高了用户使用 体验。
在一种实现方式中，当存储器1002中的软件程序和/或多组指令被处理器1003执行时，使得第一电子设备还实现如下方法步骤：如果未搜索到从设备，并且当前未搜索从设备，多设备协同卡片中包括第一按钮；响应于用户点击第一按钮的操作，搜索从设备。这样，在第一电子设备当前未搜索到从设备时，用户可以手动搜索从设备，提高了用户使用体验。
在一种实现方式中，当存储器1002中的软件程序和/或多组指令被处理器1003执行时，使得第一电子设备还实现如下方法步骤：在显示第二页面前，第一电子设备确定当前场景为第一场景时，判断是否搜索到至少一个从设备；如果搜索到至少一个从设备，第二页面包括多设备协同卡片，多设备协同卡片中包括至少一个从设备的设备标识；如果未搜索到从设备，第二页面不包括多设备协同卡片；其中，第一场景包括以下至少一个：第一电子设备在操作系统初始化之后，第一次显示第二页面；第一电子设备在登录的账号发生变化之后，第一次显示第二页面；第一电子设备在恢复出厂设置或者清空数据之后，第一次显示第二页面。这样，第一电子设备在第一次显示第二页面时，如果未搜索到从设备，可以不显示多设备协同卡片，减少对用户的打扰，提高了用户使用体验。
在一种实现方式中，当存储器1002中的软件程序和/或多组指令被处理器1003执行时，使得第一电子设备具体实现如下方法步骤：响应于用户在多设备协同卡片中的操作，显示第一页面。这样，第一电子设备可以响应于用户操作，从第二页面直接跳转到第一页面，以便于用户在第一页面中执行切换协同类型等操作，提高了用户使用体验。
在一种实现方式中，当存储器1002中的软件程序和/或多组指令被处理器1003执行时，使得第一电子设备具体实现如下方法步骤：响应于用户在多设备协同卡片中长按任意一个电子设备的设备标识的操作，显示第一页面。
在一种实现方式中，当存储器1002中的软件程序和/或多组指令被处理器1003执行时，使得第一电子设备具体实现如下方法步骤：响应于用户在多设备协同卡片中长按第三协同类型的协同标识的操作，显示第一页面。
在一种实现方式中，当存储器1002中的软件程序和/或多组指令被处理器1003执行时，使得第一电子设备具体实现如下方法步骤：响应于用户在多设备协同卡片中点击第二按钮的操作，显示第一页面。
这样，用户可以通过多种方式打开第一页面，并在第一页面中进行多设备协同的管理，提高了用户使用体验。
在一种实现方式中，当存储器1002中的软件程序和/或多组指令被处理器1003执行时，使得第一电子设备具体实现如下方法步骤：设备响应于用户在第一页面拖动第一目标设备的设备标识，使第一目标设备的设备标识与第一电子设备的设备标识相接触的操作，基于第一协同类型与第一目标设备建立多设备协同，并在第一页面中显示类型切换卡片。
在一种实现方式中，类型切换卡片中还包括第三按钮，当存储器1002中的软件程序和/或多组指令被处理器1003执行时，使得第一电子设备具体实现如下方法步骤：响应于用户点击第三按钮的操作，断开与第一目标设备之间的多设备协同。这样，用户可以在第而页面结束第一电子设备与第一目标设备的多设备协同，提高了用户使用体验。
在一种实现方式中，第一页面中还包括第四按钮，当存储器1002中的软件程序和/或多组指令被处理器1003执行时，使得第一电子设备具体实现如下方法步骤：响应于用户对第四按钮的点击操作，显示第三页面，第三页面包括第一列表，第一列表包括至少一个的协同类 型的选项；响应于用户对第一选项的点击操作，显示第四页面，第一选项是第一列表中的任意一个协同类型的选项，第四页面包括第一选项对应的协同类型的开关按钮；响应于用户对开关按钮的点击操作，开启或者关闭第一选项对应的协同类型。这样，用户可以各个协同类型进行开启和关闭等控制，提高了用户使用体验。
在一种实现方式中，当存储器1002中的软件程序和/或多组指令被处理器1003执行时，使得第一电子设备还实现如下方法步骤：与第一从设备基于第四协同类型已建立多设备协同的状态下，响应于用户在第一页面对第一目标设备的设备标识的操作，生成第一切换卡片，其中，第四协同类型不支持三个电子设备同时连接，第一切换卡片用于询问用户是否切换协同设备；响应于用户对第一切换卡片的操作，结束与第一从设备之间的多设备协同，并且建立第一电子设备与第一目标设备之间的多设备协同。
在一种实现方式中，当存储器1002中的软件程序和/或多组指令被处理器1003执行时，使得第一电子设备还实现如下方法步骤：与第一从设备基于第五协同类型已建立多设备协同的状态下，响应于用户在第一页面对第一目标设备的设备标识的操作，将第一目标设备加入到已建立的多设备协同，其中，第五协同类型支持三个电子设备同时连接。
在一种实现方式中，当存储器1002中的软件程序和/或多组指令被处理器1003执行时，使得第一电子设备还实现如下方法步骤：与环外设备已建立多设备协同的状态下，响应于用户在第一页面对第一目标设备的设备标识的操作，生成第二切换卡片，第二切换卡片用于询问用户是否切换协同设备；响应于用户对第二切换卡片的操作，结束与环外设备之间的多设备协同，并且建立第一电子设备与第一目标设备之间的多设备协同。
在一种实现方式中，当存储器1002中的软件程序和/或多组指令被处理器1003执行时，使得第一电子设备还实现如下方法步骤：第一目标设备与其他从设备或者环外设备基于第四协同类型已建立多设备协同的状态下，响应于用户在第一页面对第一目标设备的设备标识的操作，生成第三切换卡片，其中，第四协同类型不支持三个电子设备同时连接，第三切换卡片用于询问用户是否切换协同设备；响应于用户对第三切换卡片的操作，结束第一目标设备已建立的多设备协同，并且建立第一电子设备与第一目标设备之间的多设备协同。
在一种实现方式中，当存储器1002中的软件程序和/或多组指令被处理器1003执行时，使得第一电子设备还实现如下方法步骤：第一目标设备与其他从设备或者环外设备基于第五协同类型已建立多设备协同的状态下，响应于用户在第一页面对第一目标设备的设备标识的操作，加入到第一目标设备已建立的多设备协同，其中，第五协同类型支持三个电子设备同时连接。
在一种实现方式中，当存储器1002中的软件程序和/或多组指令被处理器1003执行时，使得第一电子设备还实现如下方法步骤：第一电子设备和第一目标设备均与其他从设备或者环外设备已建立多设备协同的状态下，响应于用户在第一页面对第一目标设备的设备标识的操作，生成第四切换卡片，第四切换卡片用于询问用户是否切换协同设备；响应于用户对第四切换卡片的操作，结束第一电子设备、第一目标设备各自已建立的多设备协同，并且建立第一电子设备与第一目标设备之间的多设备协同。
在一种实现方式中，当存储器1002中的软件程序和/或多组指令被处理器1003执行时，使得第一电子设备还实现如下方法步骤：第二目标设备与其他从设备或者环外设备已建立多设备协同的状态下，响应于用户在多设备协同卡片点击第二目标设备的设备标识的操作，生成第五切换卡片，第五切换卡片用于询问用户是否切换协同设备；响应于用户对第五切换卡 片的操作，结束第二目标设备已建立的多设备协同，并且建立第一电子设备与第二目标设备之间的多设备协同。
这样，在第一电子设备和/或从设备已经建立了多设备协同的情况下，第一电子设备可以响应于用户在多设备协同主页面中的操作，根据不同的场景，采用不同的策略对参与多设备协同的设备进行增加或者切换，提高了用户使用体验。
图24是本申请实施例提供的另一种多设备协同装置的结构示意图。在一个实施例中，电子设备，例如第一电子设备，可以通过图24所示的软件装置实现相应的功能。如图24所示，该多设备协同装置可以包括：
第一显示模块1101，用于响应于用户操作，显示第一页面，第一页面包括第一电子设备的设备标识和至少一个从设备的设备标识；第二显示模块1102，用于响应于用户对第一页面中的第一目标设备的设备标识的操作，基于第一协同类型与第一目标设备建立多设备协同，并在第一页面中显示类型切换卡片；其中，第一目标设备是至少一个从设备中的任意一个从设备，类型切换卡片包括第一电子设备与第一目标设备之间支持的至少一个协同类型的类型标识。
本申请实施例还提供一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述各方面的方法。
本申请实施例还提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面的方法。
本申请实施例还提供了一种芯片系统，该芯片系统包括处理器，用于支持上述装置实现上述方面中所涉及的功能，例如，生成或处理上述方法中所涉及的信息。在一种可能的设计中，芯片系统还包括存储器，用于保存多设备协同装置必要的计算机指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
以上的具体实施方式，对本申请实施例的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上仅为本申请实施例的具体实施方式而已，并不用于限定本申请实施例的保护范围，凡在本申请实施例的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本申请实施例的保护范围之内。

Claims (23)

  1. 一种多设备协同方法，其特征在于，包括：
    第一电子设备响应于用户操作，显示第一页面，所述第一页面包括所述第一电子设备的设备标识和至少一个从设备的设备标识；
    所述第一电子设备响应于用户对所述第一页面中的第一目标设备的设备标识的操作，基于第一协同类型与所述第一目标设备建立多设备协同，并在所述第一页面中显示类型切换卡片；
    其中，所述第一目标设备是所述至少一个从设备中的任意一个从设备，所述类型切换卡片包括所述第一电子设备与所述第一目标设备之间支持的至少一个协同类型的类型标识。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述第一电子设备响应于用户对所述类型切换卡片中的第二协同类型的类型标识的点击操作，将所述第一电子设备与所述第一目标设备之间的协同类型从所述第一协同类型切换至所述第二协同类型；
    其中，所述第二协同类型是所述至少一个协同类型中的任意一个协同类型，所述第一协同类型与所述第二协同类型不同。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述第一电子设备响应于用户操作，显示第二页面，所述第二页面包括多设备协同卡片，其中，如果所述第一电子设备搜索到至少一个从设备，所述多设备协同卡片中包括所述至少一个从设备的设备标识；
    所述第一电子设备响应于用户在所述多设备协同卡片中的操作，基于所述第三协同类型向第二目标设备发起多设备协同，所述第二目标设备是所述至少一个从设备中的任意一个从设备；
    所述第一电子设备与所述第二目标设备建立多设备协同之后，将所述多设备协同卡片中的所述第二目标设备的设备标识切换为所述第三协同类型的协同标识。
  4. 根据权利要求3所述的方法，其特征在于，所述方法还包括：
    所述第一电子设备响应于用户在所述多设备协同卡片中点击所述第三协同类型的协同标识的操作，结束所述第一电子设备与所述第二目标设备之间的多设备协同。
  5. 根据权利要求3所述的方法，其特征在于，所述方法还包括：
    如果所述第一电子设备未搜索到从设备，并且当前正在搜索从设备，所述多设备协同卡片中包括第一动效标识，所述第一动效标识用于指示所述第一电子设备正在搜索从设备的状态。
  6. 根据权利要求3所述的方法，其特征在于，所述方法还包括：
    如果所述第一电子设备未搜索到从设备，并且当前未搜索从设备，所述多设备协同卡片中包括第一按钮；
    所述第一电子设备响应于用户点击所述第一按钮的操作，搜索从设备。
  7. 根据权利要求3所述的方法，其特征在于，所述方法还包括：
    在显示所述第二页面前，所述第一电子设备确定当前场景为第一场景时，判断是否搜索到至少一个从设备；
    如果搜索到至少一个从设备，所述第二页面包括所述多设备协同卡片，所述多设备协同卡片中包括所述至少一个从设备的设备标识；如果未搜索到从设备，所述第二页面不包括所述多设备协同卡片；
    其中，所述第一场景包括以下至少一个：
    所述第一电子设备在操作系统初始化之后，第一次显示所述第二页面；
    所述第一电子设备在登录的账号发生变化之后，第一次显示所述第二页面；
    所述第一电子设备在恢复出厂设置或者清空数据之后，第一次显示所述第二页面。
  8. 根据权利要求3-7任一项所述的方法，其特征在于，所述第一电子设备响应于用户操作，显示第一页面，包括：所述第一电子设备响应于用户在所述多设备协同卡片中的操作，显示第一页面。
  9. 根据权利要求8所述的方法，其特征在于，所述第一电子设备响应于用户在所述多设备协同卡片中的操作，显示第一页面，包括：所述第一电子设备响应于用户在所述多设备协同卡片中长按任意一个所述电子设备的设备标识的操作，显示第一页面。
  10. 根据权利要求8所述的方法，其特征在于，所述第一电子设备响应于用户在所述多设备协同卡片中的操作，显示第一页面，包括：所述第一电子设备响应于用户在所述多设备协同卡片中长按所述第三协同类型的协同标识的操作，显示第一页面。
  11. 根据权利要求8所述的方法，其特征在于，所述多设备协同卡片中包括第二按钮，所述第一电子设备响应于用户在所述多设备协同卡片中的操作，显示第一页面，包括：所述第一电子设备响应于用户在所述多设备协同卡片中点击所述第二按钮的操作，显示第一页面。
  12. 根据权利要求1-11任一项所述的方法，其特征在于，所述第一电子设备响应于用户对所述第一页面中的第一目标设备的设备标识的操作，基于第一协同类型与所述第一目标设备建立多设备协同，并在所述第一页面中显示类型切换卡片，包括：
    所述第一电子设备响应于用户在所述第一页面拖动所述第一目标设备的设备标识，使所述第一目标设备的设备标识与所述第一电子设备的设备标识相接触的操作，基于第一协同类型与所述第一目标设备建立多设备协同，并在所述第一页面中显示类型切换卡片。
  13. 根据权利要求1-12任一项所述的方法，其特征在于，所述类型切换卡片还包括第三按钮，所述方法还包括：所述第一电子设备响应于用户点击所述第三按钮的操作，断开与所述第一目标设备之间的多设备协同。
  14. 根据权利要求1-13任一项所述的方法，其特征在于，所述第一页面中还包括第四按钮，所述方法还包括：
    所述第一电子设备响应于用户对所述第四按钮的点击操作，显示第三页面，所述第三页面包括第一列表，所述第一列表包括至少一个的协同类型的选项；
    所述第一电子设备响应于用户对第一选项的点击操作，显示第四页面，所述第一选项是所述第一列表中的任意一个协同类型的选项，所述第四页面包括所述第一选项对应的协同类型的开关按钮；
    所述第一电子设备响应于用户对所述开关按钮的点击操作，开启或者关闭所述第一选项对应的协同类型。
  15. 根据权利要求1-14任一项所述的方法，其特征在于，所述方法还包括：
    所述第一电子设备与第一从设备基于第四协同类型已建立多设备协同的状态下，响应于用户在所述第一页面对所述第一目标设备的设备标识的操作，生成第一切换卡片，其中，所述第四协同类型不支持三个电子设备同时连接，所述第一切换卡片用于询问用户是否切换协同设备；
    所述第一电子设备响应于用户对所述第一切换卡片的操作，结束与所述第一从设备之间的多设备协同，并且建立所述第一电子设备与所述第一目标设备之间的多设备协同。
  16. 根据权利要求1-14任一项所述的方法，其特征在于，所述方法还包括：
    所述第一电子设备与第一从设备基于第五协同类型已建立多设备协同的状态下，响应于用户在所述第一页面对所述第一目标设备的设备标识的操作，将所述第一目标设备加入到已建立的多设备协同，其中，所述第五协同类型支持三个电子设备同时连接。
  17. 根据权利要求1-14任一项所述的方法，其特征在于，所述方法还包括：
    所述第一电子设备与环外设备已建立多设备协同的状态下，响应于用户在第一页面对所述第一目标设备的设备标识的操作，生成第二切换卡片，所述第二切换卡片用于询问用户是否切换协同设备；
    所述第一电子设备响应于用户对所述第二切换卡片的操作，结束与环外设备之间的多设备协同，并且建立所述第一电子设备与所述第一目标设备之间的多设备协同。
  18. 根据权利要求1-14任一项所述的方法，其特征在于，所述方法还包括：
    所述第一目标设备与其他从设备或者环外设备基于第四协同类型已建立多设备协同的状态下，所述第一电子设备响应于用户在所述第一页面对所述第一目标设备的设备标识的操作，生成第三切换卡片，其中，所述第四协同类型不支持三个电子设备同时连接，所述第三切换卡片用于询问用户是否切换协同设备；
    所述第一电子设备响应于用户对所述第三切换卡片的操作，结束所述第一目标设备已建立的多设备协同，并且建立所述第一电子设备与所述第一目标设备之间的多设备协同。
  19. 根据权利要求1-14任一项所述的方法，其特征在于，所述方法还包括：
    所述第一目标设备与其他从设备或者环外设备基于第五协同类型已建立多设备协同的状 态下，所述第一电子设备响应于用户在所述第一页面对所述第一目标设备的设备标识的操作，加入到所述第一目标设备已建立的多设备协同，其中，所述第五协同类型支持三个电子设备同时连接。
  20. 根据权利要求1-14任一项所述的方法，其特征在于，所述方法还包括：
    所述第一电子设备和所述第一目标设备均与其他从设备或者环外设备已建立多设备协同的状态下，所述第一电子设备响应于用户在所述第一页面对所述第一目标设备的设备标识的操作，生成第四切换卡片，所述第四切换卡片用于询问用户是否切换协同设备；
    所述第一电子设备响应于用户对所述第四切换卡片的操作，结束所述第一电子设备、所述第一目标设备各自已建立的多设备协同，并且建立第一电子设备与所述第一目标设备之间的多设备协同。
  21. 根据权利要求2-14任一项所述的方法，其特征在于，所述方法还包括：
    所述第二目标设备与其他从设备或者环外设备已建立多设备协同的状态下，所述第一电子设备响应于用户在所述多设备协同卡片点击所述第二目标设备的设备标识的操作，生成第五切换卡片，所述第五切换卡片用于询问用户是否切换协同设备；
    所述第一电子设备响应于用户对所述第五切换卡片的操作，结束所述第二目标设备已建立的多设备协同，并且建立所述第一电子设备与所述第二目标设备之间的多设备协同。
  22. 一种电子设备，其特征在于，包括：处理器、存储器和显示屏；所述存储器存储有程序指令，当所述程序指令被所述处理器执行时，使得所述电子设备执行权利要求1-21任一项所述的方法。
  23. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有指令，当所述指令在计算机上运行时，使得所述计算机执行权利要求1-21任一项所述的方法。
PCT/CN2023/091339 2022-08-05 2023-04-27 一种多设备协同方法、电子设备及相关产品 WO2024027238A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210940127.6 2022-08-05
CN202210940127.6A CN117560792A (zh) 2022-08-05 2022-08-05 一种多设备协同方法、电子设备及相关产品

Publications (1)

Publication Number Publication Date
WO2024027238A1 true WO2024027238A1 (zh) 2024-02-08

Family

ID=89815349

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/091339 WO2024027238A1 (zh) 2022-08-05 2023-04-27 一种多设备协同方法、电子设备及相关产品

Country Status (2)

Country Link
CN (1) CN117560792A (zh)
WO (1) WO2024027238A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112286618A (zh) * 2020-11-16 2021-01-29 Oppo广东移动通信有限公司 设备协作方法、装置、系统、电子设备和存储介质
CN112615960A (zh) * 2019-09-19 2021-04-06 华为技术有限公司 一种设备能力调度方法及电子设备
WO2022089294A1 (zh) * 2020-10-30 2022-05-05 华为技术有限公司 一种设备间屏幕协同方法及设备
CN115002937A (zh) * 2022-07-18 2022-09-02 荣耀终端有限公司 一种多设备协同方法、电子设备及相关产品
CN116156044A (zh) * 2021-11-22 2023-05-23 华为技术有限公司 设备协同方法及相关装置

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112615960A (zh) * 2019-09-19 2021-04-06 华为技术有限公司 一种设备能力调度方法及电子设备
WO2022089294A1 (zh) * 2020-10-30 2022-05-05 华为技术有限公司 一种设备间屏幕协同方法及设备
CN112286618A (zh) * 2020-11-16 2021-01-29 Oppo广东移动通信有限公司 设备协作方法、装置、系统、电子设备和存储介质
CN116156044A (zh) * 2021-11-22 2023-05-23 华为技术有限公司 设备协同方法及相关装置
CN115002937A (zh) * 2022-07-18 2022-09-02 荣耀终端有限公司 一种多设备协同方法、电子设备及相关产品
CN116095881A (zh) * 2022-07-18 2023-05-09 荣耀终端有限公司 一种多设备协同方法、电子设备及相关产品

Also Published As

Publication number Publication date
CN117560792A (zh) 2024-02-13

Similar Documents

Publication Publication Date Title
WO2020233553A1 (zh) 一种拍摄方法及终端
WO2020238774A1 (zh) 一种通知消息的预览方法及电子设备
US11385857B2 (en) Method for displaying UI component and electronic device
WO2020244492A1 (zh) 一种投屏显示方法及电子设备
WO2021013158A1 (zh) 显示方法及相关装置
WO2021078284A1 (zh) 一种内容接续方法及电子设备
US20220300154A1 (en) Split-Screen Display Processing Method and Apparatus, and Electronic Device
WO2024016559A1 (zh) 一种多设备协同方法、电子设备及相关产品
WO2021121052A1 (zh) 一种多屏协同方法、系统及电子设备
WO2021233079A1 (zh) 一种跨设备的内容投射方法及电子设备
CN116360725B (zh) 显示交互系统、显示方法及设备
US20240069850A1 (en) Application Sharing Method, Electronic Device, and Storage Medium
WO2020155875A1 (zh) 电子设备的显示方法、图形用户界面及电子设备
JP2023534182A (ja) ファイルを開く方法およびデバイス
US20230350629A1 (en) Double-Channel Screen Mirroring Method and Electronic Device
WO2023072139A1 (zh) 播放音频的方法、电子设备及系统
US20240143262A1 (en) Splicing Display Method, Electronic Device, and System
WO2023005711A1 (zh) 一种服务的推荐方法及电子设备
WO2024027238A1 (zh) 一种多设备协同方法、电子设备及相关产品
WO2021027727A1 (zh) 信息传输的方法和电子设备
CN116679998B (zh) 多设备协同冲突处理的方法及电子设备
WO2024037332A1 (zh) 投屏方法、电子设备及系统
WO2023241558A1 (zh) 通信方法、通信系统和鼠标
WO2022179371A1 (zh) 一种拼接显示的方法、电子设备和系统
WO2024087807A1 (zh) 协同控制方法、装置、电子设备及可读存储介质

Legal Events

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

Ref document number: 23848949

Country of ref document: EP

Kind code of ref document: A1