Equipment collaboration method and related device

Abstract

The invention discloses an equipment collaboration method and a related device, which are applied to first electronic equipment, the method comprises the following steps: displaying a first user interface, the first user interface comprising a first icon of the first electronic equipment and an icon of at least one detected candidate equipment, the icon of the at least one candidate device comprises a second icon of a second electronic device; the second electronic equipment supports at least two collaborative capabilities, and the at least two collaborative capabilities comprise the first capability; receiving a first input operation for selecting the first capability; receiving a second input operation; and in response to the second input operation, establishing cooperative connection supporting the first capability with the second electronic equipment. Therefore, for each candidate device which can be cooperatively connected, the capability of the user intending to be cooperatively connected can be selected in a targeted manner, and the cooperative connection with the candidate device can be established, so that the capability of each candidate device can be fully applied in a targeted manner on the first electronic device, and the user experience is improved.

Description

[0001] This application is a divisional application. The application number of the original application is 202210191311.5, and the original application date is February 28, 2022. The entire contents of the original application are incorporated into this application by reference. Technical Field

[0002] The present application relates to the field of electronic technology, and in particular to a device coordination method and related apparatus. Background Art

[0003] With the development of wireless communication technology, terminals such as smartphones and tablets have begun to support users to share pictures, documents and other data with other devices, improving users' office efficiency and experience.

[0004] Due to the limitations of their own hardware structure and system performance, different types of devices usually have different capabilities and advantages. For example, a TV has a large display screen but does not have a portable camera and microphone, while a mobile phone does not have a large display screen but has a portable camera and microphone. Although existing technologies support the sharing of pictures, videos, music, documents and other data between different devices through data transmission, they cannot support the sharing of various capabilities supported by the device between different devices, and the capabilities and advantages of each device cannot be fully utilized. When users want to use the capabilities of different devices, they need to switch devices, which results in a poor user experience. Summary of the invention

[0005] The present application provides a device collaboration method and related apparatus. For each candidate device detected that can be collaboratively connected, a first electronic device can specifically select the capability that the user intends to collaboratively connect with, and establish a collaborative connection with the candidate device, so that the capabilities of each candidate device can be effectively and fully applied on the first electronic device, thereby improving the user experience.

[0006] In a first aspect, the present application provides a device collaboration method, applied to a first electronic device, the method comprising: displaying a first user interface, the first user interface including a first icon of the first electronic device and an icon of at least one detected candidate device, the icon of the at least one candidate device including a second icon of a second electronic device; the second electronic device supports at least two collaborative capabilities, the at least two collaborative capabilities including a first capability; receiving a first input operation for selecting the first capability; receiving a second input operation; and in response to the second input operation, establishing a collaborative connection supporting the first capability with the second electronic device.

[0007] In implementing the embodiment of the present application, when the second electronic device has multiple collaborative capabilities, the user can select any of the multiple collaborative capabilities through the first electronic device to establish a collaborative connection with the second electronic device; after the collaborative connection for the first capability is successful, the user can call the first capability of the second electronic device through the first electronic device. In this way, for each candidate device that can be collaboratively connected that is currently detected, the capability that the user intends to collaboratively connect can be selected in a targeted manner, and a collaborative connection can be established with the candidate device, so that the capabilities of each candidate device can be targeted and fully applied on the first electronic device, giving full play to the capability advantages of each candidate device and improving the user's experience.

[0008] In one implementation, the first user interface also includes: capability superscripts corresponding to collaborative capabilities supported by the second electronic device; capability superscripts corresponding to collaborative capabilities supported by the second electronic device include first capability superscripts corresponding to the first capability, and the first input operation acts on the first capability superscript. Exemplarily, in the first user interface, capability superscripts corresponding to collaborative capabilities supported by the second electronic device are displayed in an area surrounding the second icon. In implementing the embodiments of the present application, through the capability superscripts corresponding to the collaborative capabilities supported by the second electronic device in the first user interface, the user can intuitively see which capabilities the second electronic device can collaborate with, and then can select the capabilities corresponding to the specified capability superscripts as the capabilities to be collaborated.

[0009] In one implementation, before receiving the first input operation for selecting the first capability, the method further includes: receiving a third input operation acting on the second icon; and in response to the third input operation, displaying the capability badge corresponding to the collaborative capability supported by the second electronic device in the first user interface. In implementing the embodiment of the present application, by performing the third input operation on the icon of the candidate device, the user can see the capability badge corresponding to the collaborative capability of the candidate device.

[0010] In one implementation, the method further includes: in response to the first input operation, additionally displaying a first capability badge on the second icon. In implementing the embodiment of the present application, a user can select an additional capability badge to be displayed for the icon of the candidate device, and the first electronic device can establish a collaborative connection for the capability corresponding to the additional capability badge.

[0011] In one implementation, the first input operation includes an operation acting on the first capability badge; the second input operation includes: dragging the second icon toward the first icon until the second icon contacts the area where the first icon is located; or, dragging the second icon toward the first icon until the distance between the second icon and the first icon is less than or equal to a preset threshold; or, dragging the first icon toward the second icon until the first icon contacts the area where the second icon is located; or, dragging the first icon toward the second icon until the distance between the first icon and the second icon is less than or equal to a preset threshold.

[0012] In one implementation, the second input operation acts on the first capability badge. By implementing the embodiment of the present application, a collaborative connection supporting the first capability can be established by the input operation acting on the first capability badge.

[0013] In one implementation, the first input operation includes an operation acting on the first capability badge; the second input operation includes: dragging the first capability badge toward the first icon until the first capability badge contacts the area where the first icon is located; or, dragging the first capability badge toward the first icon until the distance between the first capability badge and the first icon is less than or equal to a preset threshold.

[0014] In one implementation, the at least two collaborative capabilities also include a second capability; after successfully establishing a collaborative connection supporting the first capability with the second electronic device, the method further includes: receiving a fifth input operation acting on the second icon; in response to the fifth input operation, displaying capability superscripts corresponding to the collaborative capabilities supported by the second electronic device, the capability superscripts corresponding to the collaborative capabilities supported by the second electronic device include a first capability superscript corresponding to the first capability, and a second capability superscript corresponding to the second capability; receiving a sixth input operation acting on the second capability superscript; in response to the sixth input operation, establishing a collaborative connection supporting the second capability with the second electronic device. In implementing the embodiment of the present application, when a collaborative connection for the first capability has been established with the second electronic device, by selecting the second capability superscript in the capability superscript corresponding to the collaborative capabilities of the second electronic device, a collaborative connection supporting the second capability can also be established with the second electronic device.

[0015] In one implementation, the at least two collaborative capabilities also include a second capability; and in response to the second input operation, establishing a collaborative connection with the second electronic device that supports the first capability specifically includes: in response to the second input operation, establishing a collaborative connection with the second electronic device that supports the first capability and the second capability. By implementing the embodiment of the present application, a collaborative connection that supports multiple capabilities can be established with the second electronic device.

[0016] In one implementation, when receiving the second input operation, the second icon is additionally displayed with a first capability badge corresponding to the first capability and a second capability badge corresponding to the second capability. In implementing the embodiment of the present application, based on the multiple capability badges additionally displayed on the second icon, a collaborative connection supporting multiple capabilities corresponding to the multiple capability badges can be established with the second electronic device.

[0017] In one implementation, after successfully establishing a collaborative connection supporting a first capability and a second capability with a second electronic device, the method further includes: receiving a seventh input operation acting on a second icon; in response to the seventh input operation, displaying capability badges corresponding to the collaborative capabilities supported by the second electronic device, wherein the capability badges corresponding to the collaborative capabilities supported by the second electronic device include a first capability badge corresponding to the first capability, and a second capability badge corresponding to the second capability; receiving an eighth input operation acting on the first capability badge; in response to the eighth input operation, canceling the collaborative connection supporting the first capability with the second electronic device. In implementing the embodiment of the present application, after the first electronic device and the second electronic device establish a collaborative connection supporting multiple capabilities, the collaborative connection for any of the multiple capabilities that have been coordinated can be canceled through the capability badge of the capability; in this way, it is convenient for the user to selectively cancel the collaborative connection of the specified capability, thereby improving the user's experience.

[0018] In one implementation, the first user interface also includes capability badges corresponding to at least two capabilities; the at least two capabilities include all collaborative capabilities supported by the at least one candidate device, the capability badges corresponding to the at least two capabilities include a first capability badge corresponding to the first capability, and the first input operation acts on the first capability badge. By implementing the embodiment of the present application, capability badges corresponding to all collaborative capabilities of all candidate devices can be displayed, and users can specifically select capabilities that they intend to collaborate with, as well as candidate devices that they intend to connect to collaboratively. In this way, the capabilities of each candidate device can be fully and specifically applied on the device, giving full play to the strengths of each candidate device and improving the user experience.

[0019] In one implementation, before receiving the first input operation for selecting the first capability, the method further includes: receiving a ninth input operation acting on the first icon; and in response to the ninth input operation, displaying capability badges corresponding to the at least two capabilities in the first user interface. In implementing the embodiment of the present application, by performing the ninth input operation on the icon of the first electronic device (i.e., the present device), the user can see the capability badges corresponding to the collaborative capabilities of all candidate devices.

[0020] In one implementation, the method further includes: in response to a first input operation, additionally displaying a first capability badge on the first icon.

[0021] In one implementation, the method further includes: in response to the first input operation, stopping displaying the icons of the candidate devices that cannot be coordinated with the first capability in the first user interface. In implementing the embodiment of the present application, when the user selects the capability to be coordinated as the first capability through the first capability badge, the icons of the candidate devices that cannot be coordinated with the first capability are stopped from being displayed, so that the user can subsequently select the candidate devices that can be coordinated with the first capability.

[0022] In one implementation, among the capability badges displayed around the second icon, the capability badge that is attached to the second icon is presented as a selected state, and the capability badge that is not attached to the second icon is presented as an unselected state; the method also includes: in response to a first input operation, switching the first capability badge displayed around the second icon from an unselected state to a selected state; the method also includes: in response to a fourth input operation, switching the second capability badge displayed around the second icon from a selected state to an unselected state.

[0023] In one implementation, the method also includes: when a collaborative connection supporting the first capability is successfully established with a second electronic device, the second icon switches from a non-collaborated state to a collaborative state, and the second icon is additionally displayed with a first capability superscript corresponding to the first capability; when a collaborative connection supporting the first capability fails to be established with the second electronic device, the second icon remains in a non-collaborated state.

[0024] In one implementation, before receiving the second input operation, the first icon is displayed in the first preset area, and the icon of the at least one candidate device is displayed in the second preset area; the uncoordinated state of the second icon is presented as being displayed in the second preset area in the first state; the coordinated state of the second icon is presented as being adsorbed on the first icon in the second state and displayed in the first preset area, or the coordinated state of the second icon is presented as being displayed in the second state in the second preset area. For example, the first state and the second state refer to different icon colors.

[0025] In one implementation, after the first electronic device executes the step of "establishing a collaborative connection with the second electronic device that supports the first capability and the second capability", when a collaborative connection supporting the first capability and the second capability is successfully established with the second electronic device, the second icon switches from a non-collaborated state to a collaborative state, and the second icon is additionally displayed with the first capability superscript and the second capability superscript; when a collaborative connection supporting the first capability is successfully established with the second electronic device, and the collaborative connection does not support the second capability, the second icon switches from a non-collaborated state to a collaborative state, and the second icon is additionally displayed with the first capability superscript, and the second capability superscript is not additionally displayed.

[0026] In one implementation, in response to the seventh input operation, among the capability badges displayed around the second icon, the capability badges corresponding to the capabilities supported by the collaborative connection established with the second electronic device (i.e., the first capability badge and the second capability badge) are presented as selected, and the capability badges corresponding to the capabilities not supported by the collaborative connection established with the second electronic device are presented as unselected.

[0027] In one implementation, after successfully establishing a collaborative connection supporting the first capability and the second capability with the second electronic device, the method further includes: receiving a tenth input operation acting on the second icon; and in response to the tenth input operation, canceling the collaborative connection with the second electronic device for any capability.

[0028] In one implementation, in response to a third input operation, a capability badge corresponding to a collaborative capability supported by the second electronic device is displayed in the first area; the at least two collaborative capabilities also include a second capability, and when receiving the third input operation acting on the second icon, the second icon is additionally displayed with a second capability badge corresponding to the second capability; after receiving the third input operation acting on the second icon, it also includes: receiving a fourth input operation acting on the second capability badge in the first area; in response to the fourth input operation, stopping the additional display of the second capability badge on the second icon.

[0029] In a second aspect, the present application also provides a device collaboration method, applied to a first electronic device, the method comprising: displaying a first user interface, the first user interface including a first icon of the first electronic device and an icon of at least one detected candidate device, the icon of the at least one candidate device including a second icon of the second electronic device; the second electronic device supports at least two collaborative capabilities, the at least two collaborative capabilities including the first capability; receiving an eleventh input operation; in response to the eleventh input operation, establishing a collaborative connection supporting the first capability with the second electronic device based on the collaborative state of the first application most recently running in the foreground and / or the second electronic device.

[0030] By implementing the embodiments of the present application, the first electronic device can adaptively select one or more capabilities for collaborative connection based on the current application scenario (i.e., the collaborative status of the first application and / or the second electronic device that was most recently running in the foreground), so that the capabilities of each candidate device can be fully utilized on the first electronic device, thereby giving full play to the capability advantages of each candidate device and improving the user experience.

[0031] In one implementation, the collaborative state of the second electronic device includes one or more of the following: the number of collaborative connections of each capability that the first electronic device and the second electronic device have collaboratively connected, the capability of the first electronic device and the second electronic device most recently collaboratively connected, and the priority of each collaborative capability of the second electronic device. The embodiment of the present application does not specifically limit the collaborative state of the second electronic device.

[0032] In one implementation, the establishing of a collaborative connection for the first capability of the second electronic device based on the collaborative state of the first application and / or the second electronic device that was most recently running in the foreground includes: when the collaborative capability of the second electronic device includes the first capability required by the first application, establishing a collaborative connection for the first capability of the second electronic device. In implementing the embodiment of the present application, the first electronic device can adaptively select the capability to be coordinated based on the capability required by the first application that was most recently running in the foreground, thereby effectively improving the user experience.

[0033] In one implementation, the establishing of a collaborative connection with the first capability of the second electronic device based on the collaborative state of the first application and / or the second electronic device that was recently run in the foreground includes: establishing a collaborative connection with the first capability that has been collaboratively connected the most times among the capabilities that have been collaboratively connected with the second electronic device; or, establishing a collaborative connection with the first capability that has been collaboratively connected with the second electronic device the most recently; or, establishing a collaborative connection with the first capability that has the highest priority among the collaborative capabilities of the second electronic device. In implementing the embodiments of the present application, the first electronic device can adaptively select the capability to be collaborative based on the collaborative state of the collaborative capabilities of the second electronic device, thereby effectively improving the user experience.

[0034] In a third aspect, the present application provides an electronic device, comprising one or more processors and one or more memories. The one or more memories are coupled to the one or more processors, and the one or more memories are used to store computer program codes, and the computer program codes include computer instructions, and when the one or more processors execute the computer instructions, the electronic device executes the device collaboration method in any possible implementation of any of the above aspects.

[0035] In a fourth aspect, an embodiment of the present application provides a computer storage medium, including computer instructions, which, when executed on an electronic device, enables the electronic device to execute a device collaboration method in any possible implementation of any of the above aspects.

[0036] In a fifth aspect, an embodiment of the present application provides a computer program product, which, when executed on a computer, enables the computer to execute a device collaboration method in any possible implementation of any of the above aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Figure 1A A schematic diagram of the system architecture of a communication system provided in an embodiment of the present application;

[0038] Figure 1B A schematic diagram of a collaborative connection system provided in an embodiment of the present application;

[0039] Figure 2 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application;

[0040] FIG. 3A to FIG. 3D A method of calling up the collaborative connection interface provided in an embodiment of the present application;

[0041] 4A to 4D Another method of calling up the collaborative connection interface provided in the embodiment of the present application;

[0042] FIG. 5A to FIG. 5D Another method of calling up the collaborative connection interface provided in the embodiment of the present application;

[0043] FIG. 6A to FIG. 6E A user interface related to collaborative connection in case 1 provided in an embodiment of the present application;

[0044] 7A to 7C A user interface related to collaborative connection in case 1 provided in an embodiment of the present application;

[0045] FIG. 8A to FIG. 8G A user interface related to the switching capability badge of situation 1 provided in an embodiment of the present application;

[0046] 9A to 9C A user interface related to collaborative connection in case 1 provided in an embodiment of the present application;

[0047] FIG. 10A to FIG. 10F A user interface related to collaborative connection in case 1 provided in an embodiment of the present application;

[0048] FIG. 11A to FIG. 11D A user interface related to canceling a collaborative connection provided in an embodiment of the present application;

[0049] FIG. 12A to FIG. 12G A user interface related to the switching capability badge of situation 2 provided in an embodiment of the present application;

[0050] FIG. 13A to FIG. 13J A user interface related to collaborative connection in situation 2 provided in an embodiment of the present application;

[0051] FIG. 14A to FIG. 14E A user interface related to collaborative connection in situation 2 provided in an embodiment of the present application;

[0052] FIG. 15A to FIG. 15D A user interface related to canceling a collaborative connection in situation 2 provided in an embodiment of the present application;

[0053] FIG. 16A to FIG. 16D A user interface for establishing a collaborative connection between two devices provided in an embodiment of the present application;

[0054] FIG. 17A to FIG. 17F A user interface related to the switching capability badge of situation three provided in an embodiment of the present application;

[0055] 18A to 18C A user interface related to collaborative connection in situation three provided in an embodiment of the present application;

[0056] FIG. 19A to FIG. 19J A user interface related to collaborative connection in situation three provided in an embodiment of the present application;

[0057] FIG. 20A to FIG. 20D A user interface related to the switching capability badge of situation 4 provided in an embodiment of the present application;

[0058] FIG. 21A to FIG. 21D A user interface related to collaborative connection in situation 4 provided in an embodiment of the present application;

[0059] FIG. 22A to FIG. 22D A user interface related to collaborative connection in situation 4 provided in an embodiment of the present application;

[0060] FIG. 23A to FIG. 23C A user interface related to collaborative connection in situation 4 provided in an embodiment of the present application;

[0061] FIG. 24A to FIG. 24F A user interface for establishing collaborative connections with multiple devices provided in an embodiment of the present application;

[0062] FIG. 25A to FIG. 25D A user interface related to collaborative connection in situation 5 provided in an embodiment of the present application;

[0063] FIG. 26A to FIG. 26D A user interface related to the application of the collaborative connection capability provided in the embodiment of the present application;

[0064] Fig. 27 A schematic diagram of a software architecture of an electronic device provided in an embodiment of the present application;

[0065] Fig.28 A schematic diagram of the software architecture of another electronic device provided in an embodiment of the present application;

[0066] Fig.29 A schematic diagram of the software architecture of a tablet computer provided in an embodiment of the present application;

[0067] Fig.30 A schematic diagram of the software architecture of a laptop computer provided in an embodiment of the present application;

[0068] Fig.31 A schematic diagram of the software architecture of a printer provided in an embodiment of the present application;

[0069] Fig.32 A flowchart of a device collaboration method provided in an embodiment of the present application. DETAILED DESCRIPTION

[0070] The technical solutions in the embodiments of the present application will be described clearly and in detail below in conjunction with the accompanying drawings. In the description of the embodiments of the present application, unless otherwise specified, " / " means or, for example, A / B can mean A or B; "and / or" in the text is only a description of the association relationship of associated objects, indicating that there can be three relationships, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, "multiple" means two or more than two.

[0071] In the following, the terms "first" and "second" are used for descriptive purposes only and are not to be understood as suggesting or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features, and in the description of the embodiments of the present application, unless otherwise specified, "plurality" means two or more.

[0072] First, the communication system 10 involved in the embodiment of the present application is introduced.

[0073] Figure 1A A schematic diagram of a communication system 10 provided in an embodiment of the present application is exemplarily shown. Figure 1A As shown, the communication system 10 includes an electronic device 100 and one or more candidate devices (eg, candidate device 200 ) that can establish a connection with the electronic device 100 .

[0074] Among them, the electronic device 100 and the candidate device 200 can be a mobile phone, a tablet computer, a desktop computer, a laptop computer, a handheld computer, a notebook computer, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a netbook, and can also be a cellular phone, a personal digital assistant (personal digital assistant, PDA), an augmented reality (augmented reality, AR) device, a virtual reality (virtual reality, VR) device, an artificial intelligence (artificial intelligence, AI) device, a wearable device (smart bracelet), a vehicle-mounted device, a smart home device (smart TV, smart screen, large screen device, etc.) and / or a smart city device. The embodiment of the present application does not impose any special restrictions on the specific type of the electronic device. The candidate device 200 can also be a projector, a speaker, a Bluetooth headset, a display, a mouse, a keyboard, a printer and other devices. The electronic device 100 and the candidate device 200 can be equipped with the same operating system or different operating systems, such as iOS, Android, Microsoft, Hongmeng and other operating systems.

[0075] In an embodiment of the present application, the electronic device 100 can establish a collaborative connection with the capability 1 of the candidate device 200, so that the electronic device 100 can share the capability 1 of the candidate device 200, and the functional module corresponding to the shared capability in the candidate device 200 can be indirectly regarded as the functional module of the electronic device 100. In some embodiments, after the capability 2 of the electronic device 100 and the candidate device 200 are capable of collaboration, the candidate device 200 can also share the capability 2 of the electronic device 100, and the functional module corresponding to the shared capability in the electronic device 100 can also be indirectly regarded as the functional module of the candidate device 200, so as to achieve mutual assistance and resource sharing between the electronic device 100 and the candidate device 200. In this way, the electronic device 100 and the one or more candidate devices mentioned above can be regarded as a distributed collaborative super terminal. For example, the electronic device 100 is a mobile phone, and the user can use the mobile phone to achieve communication connection and capability collaboration with devices such as tablet computers, laptops, projectors, mice, keyboards, printers, speakers, Bluetooth headsets, etc., and the mobile phone can indirectly have the capabilities possessed by other devices.

[0076] The above-mentioned capabilities may refer to hardware functional modules (such as cameras, microphones, speakers, displays, printers, etc.), or software functional modules (such as payment, image processing, wifi connection, screen projection, etc.), or functional modules that combine hardware and software (such as a camera function with image processing, an audio output function with audio processing, an audio input function with audio processing, etc.), and the embodiments of the present application do not make specific limitations on this.

[0077] For example, Figure 1B As shown, in the embodiment of the present application, the user interface (UI) layer of the electronic device 100 can display the icon of the device in the collaborative connection interface, the icons of the detected candidate devices (such as tablet computers, laptop computers, projectors, speakers, headphones, printers, etc.), and can also display the capability badges of the collaborative capabilities supported by the candidate devices (such as cameras, audio output functions, screen projection functions, audio input functions, printing functions, etc.). The user can select a suitable candidate device (such as candidate device 200) from the icons of candidate devices displayed on the electronic device 100 according to his or her own needs, and select the capability badge of the capability to be coordinated (such as capability 1) from the capability badges corresponding to the candidate devices; then After that, the electronic device 100 realizes the collaborative connection of the capability 1 of the candidate device 200 through a preset input operation (for example, dragging the icon of the candidate device 200 close to the icon of the device). After the electronic device 100 detects the above preset input operation, it monitors the connection status of the underlying business; after the electronic device 100 monitors that the capability 1 of the candidate device 200 is successfully collaboratively connected, the display status of the icon of the candidate device 200 is switched to the collaborative state at the UI layer, and the icon of the candidate device 200 is additionally displayed with the capability badge of capability 1; when the business layer needs to call capability 1, it can call capability 1 of the candidate device 200 based on the user's selection. In this way, the electronic device 100 can obtain one or more specified capabilities of the required candidate device 200.

[0078] It should be noted that the candidate device 200 can support at least one capability, and the candidate device 200 or the user can set some or all of the above at least one capability as collaboratively connectable capabilities of the candidate device 200 (may also be referred to as collaborative capabilities in the embodiments of the present application). For example, the candidate device 200 supports capabilities such as camera, audio output function, screen projection function, audio input function, etc. The candidate device 200 can only set the camera and audio output functions as collaborative capabilities of the candidate device 200, while other capabilities are non-collaborative capabilities of the candidate device 200; accordingly, the icon of the candidate device 200 in the UI layer of the above-mentioned electronic device 100 can only be attached with capability badges showing the camera and / or audio output functions, and cannot be attached with capability badges showing other capabilities.

[0079] In some embodiments, the electronic device 100 and the candidate device 200 perform a collaborative connection for capability 1 of the candidate device 200, which means that the electronic device 100 and the candidate device 200 also establish a business connection for capability 1 when establishing a communication connection (i.e., a data connection) or after the communication connection, so that the electronic device 100 obtains the authorization to use capability 1 of the candidate device 200. In the embodiment of the present application, the user can realize the collaborative connection between the electronic device 100 and the candidate device 200 for capability 1 through the collaborative connection interface provided in the embodiment of the present application. It should be noted that if a communication connection has been established between the electronic device 100 and the candidate device 200 when the collaborative connection is established, the above-mentioned collaborative connection may refer to a business connection for capability 1; if a communication connection has not been established between the electronic device 100 and the candidate device 200 when the collaborative connection is established, the above-mentioned collaborative connection may refer to the communication connection between the electronic device 100 and the candidate device 200 and the business connection for capability 1.

[0080] In some embodiments, the electronic device 100 establishes a collaborative connection with the capability 1 of the candidate device 200, which may include: after the electronic device 100 establishes a communication connection with the candidate device 200, the collaborative connection request is sent to the candidate device 200, and the collaborative connection request carries the identification of the capability 1 of the candidate device 200; after the candidate device 200 receives the above collaborative connection request, it determines the capability that the electronic device 100 intends to collaborate with based on the identification of the capability 1, and the candidate device 200 may send a collaborative connection response to the electronic device 100 for agreeing to the collaborative connection of the capability 1. In one implementation, the above collaborative connection response may include the capability parameters of the capability 1 of the candidate device 200; after the collaborative connection is successful, the electronic device 100 may call the capability 1 of the candidate device 200 based on the above capability parameters. It can be understood that in the embodiment of the present application, establishing a collaborative connection with (or with) the capability 1 of the candidate device 200 means establishing a collaborative connection that supports capability 1 with the candidate device 200.

[0081] It should be noted that when the electronic device 100 itself has capability 1, it can also obtain capability 1 of the candidate device 200 through collaborative connection, and process related services through capability 1 of the candidate device 200. For example, if the electronic device 100 has a camera, the electronic device 100 can also obtain the right to use the camera of the candidate device 200 through collaborative connection, and collect images through the camera of the candidate device 200.

[0082] In an embodiment of the present application, the electronic device 100 can be directly connected to the candidate device 200 via a short-range wireless communication connection or a local wired connection. Exemplarily, the electronic device 100 and the candidate device 200 can have one or more short-range communication modules in a wireless fidelity (WiFi) communication module, an ultra wide band (UWB) communication module, a bluetooth communication module, a near field communication (NFC) communication module, and a ZigBee communication module. Taking the electronic device 100 as an example, the electronic device 100 can detect and scan electronic devices near the electronic device 100 by transmitting a signal through a short-range communication module (such as a Bluetooth communication module), so that the electronic device 100 can discover nearby electronic devices (such as candidate devices 200) through a short-range wireless communication protocol, and establish a wireless communication connection with nearby electronic devices, and transmit data to nearby electronic devices.

[0083] In some embodiments, the electronic device 100 and the candidate device 200 can be connected to a local area network (LAN) through the electronic device 300 based on a wired or wireless fidelity (WiFi) connection. For example, the electronic device 300 can be a third-party device such as a router, a gateway, or an intelligent device controller. In some embodiments, the electronic device 100 and the candidate device 200 can also be indirectly connected through at least one electronic device 400 in a wide area network (such as the Internet). For example, the electronic device 400 can be a hardware server or a cloud server implanted in a virtualized environment. It can be understood that through the electronic device 300 and / or the electronic device 400, the electronic device 100 can indirectly connect to the candidate device 200 for wireless communication and data transmission.

[0084] In some embodiments, the electronic device 100 and the candidate device 200 are electronic devices connected to the same local area network. In some embodiments, the electronic device 100 and the candidate device 200 are electronic devices logged into the same account; or, the electronic device 100 and the candidate device 200 are electronic devices logged into different accounts, but the above-mentioned different accounts (such as account 1 and account 2) are in a preset relationship. For example, the above-mentioned preset relationship means that account 1 and account 2 are friends, account 1 has authorization for collaborative connection to account 2, or account 1 and account 2 are in the same family group. The embodiments of the present application do not make specific limitations on this.

[0085] It can be understood that the structure shown in this embodiment does not constitute a specific limitation on the communication system 10. In other embodiments of the present application, the communication system 10 may include more or less devices than those shown in the figure.

[0086] Figure 2 A schematic structural diagram of an electronic device 100 is shown.

[0087] The electronic device 100 may be a mobile phone, a tablet computer (PAD), a desktop computer, a laptop computer, a handheld computer, a notebook computer (Laptop), an ultra-mobile personal computer (UMPC), a netbook, a cellular phone, a personal digital assistant (PDA), an augmented reality (AR) device, a virtual reality (VR) device, an artificial intelligence (AI) device, a wearable device, an in-vehicle device, a smart home device and / or a smart city device. The embodiments of the present application do not impose any special restrictions on the specific type of the electronic device.

[0088] The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

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

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

[0091] The controller can generate operation control signals according to the instruction operation code and timing signal to complete the control of instruction fetching and execution.

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

[0093] In some embodiments, the processor 110 may include one or more interfaces. The interface may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0094] The charging management module 140 is used to receive charging input from a charger. The charger may be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 may receive charging input from a wired charger through the USB interface 130. In some wireless charging embodiments, the charging management module 140 may receive wireless charging input through a wireless charging coil of the electronic device 100. While the charging management module 140 is charging the battery 142, it may also power the electronic device through the power management module 141.

[0095] The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140, and supplies power to the processor 110, the internal memory 121, the display screen 194, the camera 193, and the wireless communication module 160. The power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle number, battery health status (leakage, impedance), etc. In some other embodiments, the power management module 141 can also be set in the processor 110. In other embodiments, the power management module 141 and the charging management module 140 can also be set in the same device.

[0096] The wireless communication function of the electronic device 100 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

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

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

[0099] The modem processor may include a modulator and a demodulator. Among them, 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. After the low-frequency baseband signal is processed by the baseband processor, it is passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to a speaker 170A, a receiver 170B, etc.), or displays an image or video through a display screen 194. In some embodiments, the modem processor may be an independent device. In other embodiments, the modem processor may be independent of the processor 110 and be set in the same device as the mobile communication module 150 or other functional modules.

[0100] The wireless communication module 160 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc., which are applied to the electronic device 100. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, demodulates 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, modulate the frequency, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

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

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

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

[0104] The electronic device 100 can realize the shooting function through ISP, camera 193, video codec, GPU, display screen 194 and application processor.

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

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

[0107] The digital signal processor is used to process digital signals, and can process not only digital image signals but also other digital signals. For example, when the electronic device 100 is selecting a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy.

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

[0109] NPU is a neural network (NN) computing processor. By drawing on the structure of biological neural networks, such as the transmission mode between neurons in the human brain, it can quickly process input information and can also continuously self-learn. Through NPU, applications such as intelligent cognition of electronic device 100 can be realized, such as image recognition, face recognition, voice recognition, text understanding, etc.

[0110] The internal memory 121 may include one or more random access memories (RAM) and one or more non-volatile memories (NVM).

[0111] Random access memory may include static random-access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM, for example, the fifth generation DDR SDRAM is generally referred to as DDR5 SDRAM), etc.; non-volatile memory may include disk storage devices and flash memory.

[0112] Flash memory can be divided into NOR FLASH, NAND FLASH, 3D NAND FLASH, etc. according to the operating principle; single-level cell (SLC), multi-level cell (MLC), triple-level cell (TLC), quad-level cell (QLC), etc. according to the storage unit potential level; universal flash storage (UFS), embedded multi media card (eMMC), etc. according to the storage specification.

[0113] The random access memory can be directly read and written by the processor 110, and can be used to store executable programs (such as machine instructions) of the operating system or other running programs, and can also be used to store user and application data.

[0114] The non-volatile memory may also store executable programs and user and application data, etc., and may be loaded into the random access memory in advance for direct reading and writing by the processor 110 .

[0115] The external memory interface 120 can be used to connect to an external non-volatile memory to expand the storage capacity of the electronic device 100. The external non-volatile memory communicates with the processor 110 through the external memory interface 120 to implement a data storage function. For example, files such as music and videos are stored in the external non-volatile memory.

[0116] The electronic device 100 can implement audio functions such as music playing and recording through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone jack 170D, and the application processor.

[0117] The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals.

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

[0119] The receiver 170B, also called a "earpiece", is used to convert audio electrical signals into sound signals. When the electronic device 100 receives a call or voice message, the voice can be received by placing the receiver 170B close to the human ear.

[0120] Microphone 170C, also called "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or sending a voice message, the user can speak by approaching microphone 170C with his mouth to input the sound signal into microphone 170C. Microphone 170C can be used to collect sound signals, reduce noise, identify sound sources, and perform directional recording.

[0121] The earphone interface 170D is used to connect a wired earphone and can be a USB interface 130 or other standard interfaces.

[0122] The pressure sensor 180A is used to sense the pressure signal and can convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A can be disposed on the display screen 194 .

[0123] The gyro sensor 180B may be used to determine the motion posture of the electronic device 100. In some embodiments, the angular velocity of the electronic device 100 around three axes (ie, x, y, and z axes) may be determined by the gyro sensor 180B.

[0124] The air pressure sensor 180C 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 180C to assist positioning and navigation.

[0125] The acceleration sensor 180E can detect the magnitude of acceleration in various directions (generally three axes) of the electronic device 100. When the electronic device 100 is stationary, the magnitude and direction of gravity can be detected.

[0126] The distance sensor 180F is used to measure the distance. The electronic device 100 can measure the distance by infrared or laser. In some embodiments, when shooting a scene, the electronic device 100 can use the distance sensor 180F to measure the distance to achieve fast focusing.

[0127] The proximity light sensor 180G may include, for example, a light emitting diode (LED) and a light detector such as a photodiode. The light emitting diode may be an infrared light emitting diode. The electronic device 100 emits infrared light to the outside through the light emitting diode.

[0128] The ambient light sensor 180L is used to sense the brightness of the ambient light. The electronic device 100 can adaptively adjust the brightness of the display screen 194 according to the sensed brightness of the ambient light.

[0129] The fingerprint sensor 180H is used to collect fingerprints. The electronic device 100 can use the collected fingerprint characteristics to implement fingerprint unlocking, access application locks, fingerprint photography, fingerprint call answering, etc.

[0130] The temperature sensor 180J is used to detect temperature. In some embodiments, the electronic device 100 uses the temperature detected by the temperature sensor 180J to execute a temperature processing strategy.

[0131] The touch sensor 180K is also called a "touch control device". The touch sensor 180K can be set on the display screen 194. The touch sensor 180K and the display screen 194 form a touch screen, also called a "touch control screen". The touch sensor 180K is used to detect a touch operation acting on or near it. The touch sensor can pass the detected touch operation to the application processor to determine the type of touch event.

[0132] Bone conduction sensor 180M can obtain vibration signals.

[0133] The button 190 includes a power button, a volume button, etc. The button 190 may be a mechanical button or a touch button.

[0134] Motor 191 can generate vibration prompts.

[0135] Indicator 192 may be an indicator light, which may be used to indicate charging status, charge change, messages, notifications, etc.

[0136] The SIM card interface 195 is used to connect a SIM card.

[0137] The following introduces the application scenarios of the device collaboration method provided in the embodiments of the present application.

[0138] First, several collaboratively connected user interfaces involved in the embodiments of the present application are introduced.

[0139] For example, FIG. 3A to FIG. 3D A schematic diagram related to calling up a collaborative connection interface of an electronic device 100 is shown.

[0140] Figure 3A The main interface 11 for displaying applications installed on the electronic device 100 is shown. The main interface 11 may include: a status bar 101, a calendar indicator 102, a weather indicator 103, a tray 104 with common application icons, and other application icons 105. Among them:

[0141] The status bar 101 may include: one or more signal strength indicators of mobile communication signals (also referred to as cellular signals), an operator name (e.g., "China Mobile"), one or more signal strength indicators of wireless high-fidelity (Wi-Fi) signals, a battery status indicator, and a time indicator.

[0142] The main interface 11 may also include a page indicator 106. Other application icons may be distributed on multiple pages, and the page indicator 106 may be used to indicate which page the user is currently viewing an application in. The user may slide the area of ​​other application icons left and right to view application icons in other pages.

[0143] like Figure 3A As shown, the electronic device 100 receives a sliding operation performed by the user on the status bar 101, and in response to the sliding operation, the electronic device 100 displays Figure 3B The control center interface 12 shown in the figure includes shortcut icons 201 of multiple commonly used functions (e.g. Figure 3B WLAN icon, Bluetooth icon, NFC icon, brightness adjustment bar, etc.)

[0144] like Figure 3B As shown, the control center interface 12 may also include a collaborative connection card 1, in which a prompt message 202 and a control 203 are displayed. The prompt message 202 may be used to prompt the user that there is no collaboratively connected available device at present, and the user may search for other devices by clicking the control 203.

[0145] In some embodiments, the control 203 may receive an input operation (eg, a click operation) from a user, and in response to the input operation, the electronic device 100 may display a Figure 3C The collaborative connection interface 13 shown. The collaborative connection interface 13 includes an icon 301 of the electronic device 100, icons of candidate devices for collaborative connection detected by the electronic device 100, and names and / or models of the candidate devices. Each candidate device displayed in the collaborative connection interface 13 supports at least one collaborative capability.

[0146] For example, the icon of the electronic device 100 is located in the preset area 1 of the collaborative connection interface 13 (eg Figure 3C The icons of the candidate devices may be located in a preset area 2 surrounding the icons of the electronic device 100 (eg, Figure 3C The shapes and positions of the preset areas 1 and 2 are not specifically limited in the present embodiment of the application. The subsequent embodiments are described by taking the preset area 1 as the circular area shown in the figure and the preset area 2 as the circular area shown in the figure as an example. The icons of the candidate devices may include an icon 302 of a tablet computer of model AAA, an icon 303 of a laptop computer of model YYY, an icon 304 of a speaker of model ZZZ, an icon 305 of a projector of model DDD, and an icon 306 of a printer of model EEE.

[0147] In the embodiment of the present application, before displaying the collaborative connection interface 13, in response to an input operation on the control 203 (such as clicking this operation), the electronic device 100 detects the candidate devices for collaborative connection and obtains the relevant information of each candidate device, which may indicate the collaborative capabilities supported by the candidate device, and part or all of the device identification, device name, device model and device type. The electronic device 100 can determine the icon of the candidate device based on the relevant information of each candidate device, and display it in the collaborative connection interface 13. In one implementation, the electronic device 100 can obtain electronic devices located in the same local area network through signal detection, and use the electronic devices located in the same local area network as candidate devices for collaborative connection. In one implementation, the electronic device 100 can query the server for electronic devices that log in to the same account as the electronic device 100, and use the queried electronic devices as candidate devices for collaborative connection. The relevant information of the candidate device can be obtained by the electronic device 100 after the candidate device is detected this time, or it can be obtained and stored by the electronic device 100 in the previous collaborative connection with the candidate device.

[0148] In some embodiments, a capability badge corresponding to at least one capability that the candidate device can coordinate is additionally displayed on the icon of each candidate device in the collaborative connection interface 13. In one implementation, the relevant information includes the collaborative capabilities that the candidate device can support, and the electronic device 100 can also determine the capability badge additionally displayed on the icon of the candidate device based on the relevant information of the candidate device.

[0149] For example, see Figure 3D In the collaborative connection interface 13 shown, the tablet computer icon 302 is additionally displayed with a capability badge corresponding to the camera, the laptop computer icon 303 is additionally displayed with a capability badge corresponding to the audio input function, the speaker icon 304 is additionally displayed with a capability badge corresponding to the audio output function, the projector icon 305 is additionally displayed with a capability badge corresponding to the screen projection function, and the printer icon 306 is additionally displayed with a capability badge corresponding to the printing function.

[0150] In one implementation, the icon of the candidate device in the collaborative connection interface 13 called up by the electronic device 100 only displays one capability badge. If the candidate device supports multiple collaborative capabilities, the capability badge may be a capability badge corresponding to the capability that the candidate device has recently been collaboratively connected to, or may be a capability badge corresponding to the capability that the candidate device has most frequently been collaboratively connected to, which is not specifically limited here.

[0151] In some embodiments, the icons of the candidate devices in the cooperative connection interface 13 rotate slowly relative to the icon of the electronic device 100 .

[0152] In some embodiments, when the electronic device 100 does not detect a candidate device for cooperative connection, Figure 3C and Figure 3D The circular area of ​​the cooperative connection interface 13 shown displays icons of zero candidate devices, and the electronic device 100 can display prompt information in the cooperative connection interface 13 to prompt the user that no candidate device for cooperative connection is detected.

[0153] In the embodiment of the present application, under the same communication environment, the candidate devices displayed in the collaborative connection interface 13 called up in different ways may be different, and the capability badges displayed in addition to the icons of the candidate devices may also be different.

[0154] In some embodiments, when the electronic device 100 runs the application 1 in the foreground, an input operation for calling up the collaborative connection interface 13 is detected; in response to the input operation, the electronic device 100 determines at least one preset capability required by the application 1, detects candidate devices that can cooperate with the preset capability, and displays the icons of the candidate devices that can cooperate with the preset capability on the collaborative connection interface 13. In some embodiments, the icons of the candidate devices in the collaborative connection interface 13 are all attached with capability badges showing the preset capability.

[0155] For example, application 1 is a music application (application, APP), 4A to 4D Another method of calling out the collaborative connection interface 13 is shown.

[0156] Electronic device 100 displays Figure 4A When the music playing interface 14 of the music APP shown in the figure is displayed, a sliding operation acting on the status bar is received; in response to the sliding operation, the electronic device 100 displays Figure 4B The control center interface 12 shown in the figure; an input operation for the control 203 in the control center interface 12 is detected; in response to the input operation, the electronic device 100 determines that the capabilities required by the music APP include an audio output function, and the electronic device 100 detects a candidate device that can cooperate with the audio output function, and Figure 4C or Figure 4D The collaborative connection interface 13 shown in FIG. 1 displays icons of the candidate devices that can collaborate with the audio output function. Figure 4D , the icons of candidate devices are all attached with a capability badge showing the audio output function. For example, the electronic device 100 detects that the devices under the same local area network include: a tablet computer of model AAA, a laptop computer of model YYY, a speaker of model ZZZ, a projector of model DDD, and a printer of model EEE; among them, the tablet computer, the laptop computer, and the speaker support the collaborative connection of the audio output function, while other devices do not support the collaborative connection of the audio output function; Figure 4C or Figure 4D The collaborative connection interface 13 shown includes an icon 302 of a tablet computer, an icon 303 of a laptop computer, and an icon 304 of a speaker.

[0157] Understandably, 4A to 4D In the example, the input operation of calling out the collaborative connection interface 13 may include: a sliding operation of calling out the control center interface 12 , and a click operation acting on the control 203 in the control center interface 12 .

[0158] In some embodiments, the electronic device 100 runs application 1 in the foreground, and the user interface 1 of application 1 includes control 1, which is used to call the preset capability of the available device that has been coordinated. An input operation (such as a click operation) acting on control 1 is detected; if there is currently no available device that has coordinated the preset capability, in response to the above input operation, the electronic device 100 displays control 2; when an input operation (such as a click operation) acting on control 2 is detected, the electronic device 100 detects candidate devices that can coordinate the above preset capability, and displays the icons of candidate devices that can coordinate the above preset capability in the collaborative connection interface 13. In some embodiments, the icons of candidate devices in the above collaborative connection interface 13 are all attached with capability badges showing the above preset capability. It can be understood that the above input operation for calling up the collaborative connection interface 13 may include: the above input operation acting on control 1, and the above input operation acting on control 2.

[0159] For example, application 1 is a music APP. FIG. 5A to FIG. 5D Another method of calling out the collaborative connection interface 13 is shown. The user interface 1 is Figure 5A The music playing interface 14 shown in the figure, control 1 is a switching control 311 in the music playing interface 14, the switching control 311 is used to call the audio output function of the coordinated available device, and control 2 is Figure 5B Control 312 is shown.

[0160] Electronic device 100 displays Figure 5A The music playing interface 14 of the music application shown in the figure includes a switching control 311; the electronic device 100 detects an input operation acting on the switching control 311; if there is currently no available device with a coordinated audio output function, in response to the above input operation, the electronic device 100 displays a card 2 for a coordinated connection; card 2 includes a control 312 and a prompt message 313, and the prompt message 313 is used to prompt that there is currently no available device with a coordinated audio output function, and the user can search for other devices. An input operation for the above control 312 is detected; in response to the above input operation, the electronic device 100 detects candidate devices that can coordinate the audio output function, and displays a card 2 for a coordinated connection. Card 2 includes a control 312 and a prompt message 313, and the prompt message 313 is used to prompt that there is currently no available device with a coordinated audio output function, and the user can search for other devices. Figure 5C or Figure 5DThe collaborative connection interface 13 shown in FIG. 1 displays icons of candidate devices that can collaborate with the audio output function. Figure 5D , the icons of candidate devices are all attached with a capability badge indicating the audio output function.

[0161] In some embodiments, the electronic device 100 runs application 1 in the foreground; detects the user's input operation on application 1, which is used to execute the preset capability of application 1; if the electronic device 100 does not have the above preset capability, in response to the above input operation, the electronic device 100 displays control 2; detects the input operation (such as a click operation) on control 2, the electronic device 100 detects candidate devices that can cooperate with the above preset capability, and displays the icons of candidate devices that can cooperate with the above preset capability in the collaborative connection interface 13. In some embodiments, the icons of candidate devices in the above collaborative connection interface 13 are all attached with capability badges showing the above preset capability. It can be understood that the above input operation for calling up the collaborative connection interface 13 may include: the above input operation on application 1, and the above input operation on control 2.

[0162] For example, the application 1 is a Word APP, and the above-mentioned preset capability is a printing function. If the electronic device 100 detects an input operation to call the printing function of the Word APP, the electronic device 100 can display a card for collaborative connection after determining that the device does not have the printing function, and call out the collaborative connection interface 13 through the card. For details, refer to the above-mentioned embodiment, which will not be repeated here.

[0163] It should be noted that FIG. 3A to FIG. 5D Several methods of calling out the collaborative connection interface 13 are introduced as examples, but are not limited to the above-mentioned calling out methods. The embodiment of the present application can also call out the collaborative connection interface 13 in other ways, which are not specifically limited here. In addition, FIG. 3A to FIG. 5D The collaborative connection interface 13 involved is an exemplary description of the embodiment of the present application and should not constitute a limitation on the present application.

[0164] The following describes how to achieve collaborative connection between devices for specified capabilities through the collaborative connection interface.

[0165] The embodiments of the present application provide five situations for realizing collaborative connection.

[0166] Case 1: Only one capability is supported for collaborative connection between two electronic devices; the candidate device 200 supports at least one capability that can be collaborative, and the icon of the candidate device 200 can be attached with a capability badge that displays any one of the at least one capability (e.g., capability 1). When the icon of the candidate device 200 additionally displays the capability badge corresponding to capability 1, dragging the icon of the candidate device 200 close to the icon of the electronic device 100 or dragging the icon of the electronic device 100 close to the icon of the candidate device 200 can realize the collaborative connection of the electronic device 100 to the capability 1 of the candidate device 200.

[0167] For example, Fig. 6A Taking the collaborative connection interface 13 shown as an example, 6A to 7C The relevant user interface of the collaborative connection of case 1 is shown.

[0168] like Fig. 6A and Figure 6B As shown, the tablet computer icon 302 in the collaborative connection interface 13 is additionally provided with a capability badge 501 corresponding to the camera, and the tablet computer icon 302 can receive a sliding operation by the user, the sliding direction of the sliding operation points to the icon 301 of the electronic device 100; in response to the sliding operation, the electronic device 100 moves the tablet computer icon 302 toward the icon 301 of the electronic device 100. Figure 6B As shown, when it is detected that icon 302 is dragged to the area where icon 301 is located, in response to the above sliding operation, electronic device 100 displays prompt information 401 and performs a collaborative connection with the camera of the tablet computer. Prompt information 401 is used to prompt the collaborative connection between the device and the camera of the tablet computer. In the embodiment of the present application, electronic device 100 can display prompt information 401 and perform a collaborative connection when it is detected that icon 302 contacts preset area 1 where icon 301 is located, or it can trigger the display of prompt information 401 and perform a collaborative connection when it is detected that icon 302 contacts icon 301, which is not specifically limited here.

[0169] In some embodiments, the electronic device 100 performs a collaborative connection with a camera of a tablet computer, including: sending a collaborative connection request for the camera to the tablet computer, where the collaborative connection request may include an identifier of the electronic device 100 and an identifier of the camera.

[0170] In some embodiments, Figure 6C As shown, after receiving the collaborative connection request sent by the electronic device 100, the tablet computer displays a selection box, which includes prompt information 402, a confirmation control 403 and a rejection control 404. The prompt information 402 is used to prompt that the collaborative connection request for the camera from the electronic device 100 is received.

[0171] like Figure 6CAs shown, the confirmation control 403 can receive the user's input operation. In response to the above input operation, the tablet computer sends a collaborative connection response 1 to the electronic device 100 agreeing to the collaborative connection. After the electronic device 100 receives the collaborative connection response 1 sent by the tablet computer, it displays Fig.6D The prompt information 404 shown in the figure changes the display state of the tablet computer icon from the non-cooperative state to the cooperative state. The prompt information 404 is used to prompt that the device has established a cooperative connection with the camera of the tablet computer. Fig.6D The coordinated state shown means that the color of the tablet computer icon 302 is darkened and attached to the device icon 301. In the embodiment of the present application, the non-coordinated state and the coordinated state of the candidate device icon are not specifically limited.

[0172] In some embodiments, the capability badges displayed in addition to the icons of the candidate devices also include the uncoordinated state and the coordinated state. Fig. 6A As shown, before the camera is successfully connected, the camera capability badge 501 is in an uncoordinated state (for example, not displayed in a darkened state); Fig.6D As shown, after the camera is successfully connected, the camera capability badge 501 shows a coordinated state (for example, a darkened display). In the embodiment of the present application, the uncoordinated state and the coordinated state of the capability badge are not specifically limited.

[0173] In some embodiments, reference Fig. 6E In the control center interface 12 shown, after establishing a collaborative connection with the camera of the tablet computer, the electronic device 100 displays icons of available devices that have been collaboratively connected (such as the tablet computer icon 412) in the collaboratively connected card 1, and may also display icons of candidate devices that have not been collaboratively connected (such as the laptop icon 413, the speaker icon 414, and the projector icon 415). Among them, the icon 412 of the available device is attached with a capability badge corresponding to the collaborative capability (i.e., the camera). In the embodiment of the present application, the display status of the icon 412 (such as a darkened display) and / or the prompt information 416 (such as the text "collaborated") can be used to indicate that the electronic device corresponding to the icon is a collaborative available device; the capability of the tablet computer is indicated by the capability badge attached to the icon 412. In addition, Fig. 6E The card 1 shown may also include a control 411, through which the user can call up Fig.6D The collaborative connection interface 13 is shown.

[0174] like Fig. 7A As shown, the rejection control 404 can receive the user's input operation. In response to the above input operation, the tablet computer sends a collaborative connection response 2 to the electronic device 100 to reject the collaborative connection. Based on the collaborative connection response 2, after confirming that the collaborative connection fails, the electronic device 100 displays Figure 7BThe prompt message 405 shown in the figure bounces the tablet computer icon 301 back to the preset area 2 (i.e., the annular area) where the candidate device is located. The above prompt message 405 is used to prompt that the cooperative connection between the device and the tablet computer camera has failed. In some embodiments, reference Figure 7C In the control center interface 12 shown, after the collaborative connection with the tablet computer fails, the electronic device 100 displays the icons of the detected candidate devices in the collaborative connection card 1, so that the user can know which candidate devices are currently available for collaborative connection.

[0175] It should be noted that in the embodiments of the present application, the collaborative connection failure is not limited to the user's input operation of rejecting the collaborative connection, but may also be caused by other reasons, which are not specifically limited here. In one implementation, when the electronic device 100 does not receive the collaborative connection response 1 within a preset time after sending the collaborative connection request, the electronic device 100 determines that the collaborative connection has failed and displays Figure 7B The collaborative connection interface 13 is shown.

[0176] In some embodiments, before the collaborative connection interface 13 receives a sliding operation of the user dragging the icon, the icons of the candidate devices (for example, icon 302) all rotate slowly around the icon 301 of the device itself; when the collaborative connection interface 13 receives a sliding operation of the user dragging the icon, the icons of the candidate devices stop rotating slowly; during the process of the electronic device 100 executing the collaborative connection, the electronic device 100 can also play a connection animation; after determining that the collaborative connection is successful or failed, the electronic device 100 can terminate the above-mentioned connection animation, and the icons of each candidate device resume rotating.

[0177] In some embodiments, after receiving the collaborative connection request from the electronic device 100, the tablet computer can decide whether to agree to the collaborative connection request from the electronic device 100 based on a preset method, without displaying the collaborative connection request. Figure 6CThe selection box shown. The embodiment of the present application does not specifically limit the above-mentioned preset method. In one implementation, before the electronic device 100 sends a collaborative connection request to the tablet computer, a verification information input box is also displayed. The verification information input box is used to input the verification information (such as a password) of the collaborative connection of the tablet computer. The above-mentioned collaborative connection request can carry the verification information entered by the user in the verification information input box; when the tablet computer determines that the above-mentioned verification information is correct, it agrees to the collaborative connection request of the electronic device 100, otherwise, the collaborative connection request of the electronic device 100 is rejected. In one implementation, when the tablet computer determines that the same account as the electronic device 100 is logged in, it agrees to the collaborative connection request of the electronic device 100, otherwise, the collaborative connection request of the electronic device 100 is rejected. In one implementation, when the tablet computer determines that it is located in the same local area network as the electronic device 100, it agrees to the collaborative connection request of the electronic device 100, otherwise, the collaborative connection request of the electronic device 100 is rejected.

[0178] In the embodiment of the present application, the user can switch the capability badge displayed in addition to the icon of the candidate device, and then establish a collaborative connection based on the switched capability badge.

[0179] For example, FIG. 8A to FIG. 8D A user interface for switching the capability badge additionally displayed on the tablet computer icon 302 is shown.

[0180] like Fig. 8A and Figure 8B As shown, the icon of the candidate device in the collaborative connection interface 13 (e.g., the icon 302 of the tablet computer) additionally displays the capability badge 501 corresponding to the camera, and the icon 302 can receive the user's input operation (e.g., a click operation). In response to the above input operation, the electronic device 100 displays the capability badges corresponding to the collaborative capabilities other than the camera supported by the tablet computer around the icon 302, such as the capability badge 502 corresponding to the audio input function and the capability badge 503 corresponding to the audio output function. It can be understood that if the collaborative capabilities supported by the tablet computer only include the camera, when the user clicks the icon 302, no other capability badges can be displayed around the icon 302.

[0181] like Figure 8B and Figure 8C As shown, capability badge 502 can receive user input operations (such as click operations). In response to the above operations, capability badge 501 additionally displayed on tablet computer icon 302 is switched to capability badge 502, and capability badge 501 corresponding to the camera is displayed around icon 302. Figure 8C and Fig.8D As shown, after the tablet computer icon 302 receives a user input operation (eg, a touch operation), the electronic device 100 stops displaying the capability badge around the icon 302. In some embodiments, Figure 8B After receiving the user's input operation, the electronic device 100 can also directly display Fig.8D The collaborative connection interface 13 shown. It can be understood that Fig.8D The tablet computer icon 302 shown in the figure is additionally provided with a capability badge 502 showing the audio input function. When the user drags the icon 302 to the icon 301 of the device, the audio input function of the tablet computer can be collaboratively connected. Figure 8B and Figure 8C As shown, for the same capability badge (eg, capability badge 501 ), the sizes of the capability badge 501 displayed around the icon 302 and the capability badge 501 additionally displayed on the icon 302 may be different.

[0182] For example, FIG. 8E to FIG. 8G Another user interface for switching the tablet computer icon 302 to display a capability badge in addition is shown.

[0183] In response to Fig. 8A The electronic device 100 displays an input operation (eg, a click operation) of the tablet computer icon 302. Fig. 8E The collaborative connection interface 13 shown, that is, the capability badges corresponding to all the collaborative capabilities supported by the tablet computer are displayed around the icon 302, and the capability badge currently displayed by the icon 302 is indicated by the selected state. Fig. 8E As shown, the capability badge 501 currently displayed in addition to the icon 302 is shown in a selected state (eg, displayed in a darker manner), and the capability badge 502 currently not displayed in addition to the icon 302 is shown in an unselected state (eg, displayed in a non-darkened manner).

[0184] like Fig. 8E and Fig.8F As shown, capability badge 502 can receive a user input operation (such as a click operation). In response to the above operation, capability badge 501 switches from a selected state to an unselected state, and capability badge 502 switches from an unselected state to a selected state, that is, capability badge 501 additionally displayed on tablet computer icon 302 is switched to capability badge 502. Fig.8F and Figure 8G As shown, after the tablet computer icon 302 receives a user input operation (eg, a touch operation), the electronic device 100 stops displaying the capability badge around the icon 302. In some embodiments, Fig. 8E After receiving the user's input operation, the electronic device 100 can also directly display Figure 8G The collaborative connection interface 13 is shown.

[0185] In the embodiment of the present application, the user can also achieve collaborative connection of the capability corresponding to the capability badge by dragging the capability badge around the icon 302 to the area where the icon 301 of the electronic device 100 is located.

[0186] For example, Fig.9A Take the collaborative connection interface 13 shown in FIG. Fig.9A and Fig. 9B As shown, the user drags the audio input function capability badge 502 to the area where the icon 301 is located (ie, the aforementioned preset area 1, or the display area of ​​the icon 301) by sliding operation and then releases the hand; Fig. 9C As shown, in response to a sliding operation on the capability badge 502, the electronic device 100 moves the capability badge 502 along the sliding direction of the sliding operation; Fig. 9C As shown, when the capability badge 502 is detected to be dragged to the area where the icon 301 is located and the user's finger leaves the screen, the electronic device 100 displays the tablet computer icon 302 with the capability badge 502 attached in the preset area 1 (i.e., the aforementioned circular area), as well as the prompt message 406. The prompt message 406 is used to prompt that the device is in a collaborative connection with the audio input function of the tablet computer. For details, please refer to FIG. 6B to FIG. 7C The related contents of the collaborative connection described are not repeated here.

[0187] In addition, for FIG. 3A to FIG. 5D The collaborative connection interface 13 shown in FIG. 1 is not provided with a capability badge. The user can also select a capability badge to be displayed for the icon of the candidate device. For details, please refer to FIG. 8A to FIG. 8F Related description: How to achieve collaborative connection after the candidate device icon is attached with the displayed capability badge, please refer to 6A to 7C as well as 9A to 9C The relevant descriptions will not be repeated here.

[0188] In some embodiments, the collaborative connection of the capabilities corresponding to the capability badges additionally displayed on the candidate device 200 can also be achieved by dragging the icon 301 of the present device to the area where the icon of the candidate device 200 is located.

[0189] For example, Fig. 10A Taking the collaborative connection interface 13 shown as an example, FIG. 10A to FIG. 10F The relevant user interface of the collaborative connection in this embodiment is shown.

[0190] like Fig. 10A and Fig. 10BAs shown, the tablet computer icon 302 in the collaborative connection interface 13 is additionally displayed with a capability badge 501 corresponding to the camera. The device icon 301 can receive a sliding operation from the user, and the sliding direction of the sliding operation points to the tablet computer icon 302. In response to the sliding operation, the electronic device 100 moves the icon 301 toward the icon 302. Fig. 10C As shown, when it is detected that icon 301 contacts icon 302, in response to the above sliding operation, electronic device 100 displays prompt information 401 and performs a coordinated connection with the camera of the tablet computer.

[0191] like Fig. 10D As shown, when it is determined that the collaborative connection is successful, the electronic device 100 displays a prompt message 404 and changes the display state of the tablet computer icon from the non-collaborative state to the collaborative state. Fig. 10E The prompt message 405 is shown, and the tablet computer icon 302 is bounced back to the annular area where the candidate devices are located.

[0192] Fig. 10D The coordinated state shown means that the color of the tablet computer icon 302 is darkened and attached to the icon 301 of the device. In the present embodiment of the application, the uncoordinated state and the coordinated state of the icon are not specifically limited. For example, when it is determined that the coordinated connection is successful, the electronic device 100 displays Fig.10F The collaborative connection interface shown, Fig.10F Another coordinated state of icon 302 is shown, that is, the color of icon 302 is darkened and it bounces back to the preset area 2 (that is, the annular area shown in the figure) where the candidate devices are located; the uncoordinated state of other candidate devices in the annular area is shown as the color is not darkened.

[0193] In the embodiment of the present application, after the electronic device 100 establishes a collaborative connection with the capability 1 of the candidate device 200, the user can cancel the collaborative connection with the capability 1 of the candidate device 200.

[0194] The following description takes the camera of a tablet computer as an example. Fig. 10D and Fig.10F , the tablet computer's coordinated state icon 302 is additionally provided with a camera capability badge; the tablet computer's coordinated state icon 302 can receive a user's cancel operation 1; in response to the cancel operation 1, the electronic device 100 can cancel the coordinated connection with the tablet computer's camera and switch the display state of the icon 302 to a non-coordinated state. In the embodiment of the present application, the cancel operation 1 is not specifically limited, and different coordinated states may correspond to different cancel operations 1.

[0195] For example, Fig.11AAs shown, the icon 302 in the coordinated state is attached to the icon 301 of the device, and the cancel operation 1 may include dragging the icon 302 away from the icon 301 of the device through a sliding operation on the icon 302 and then releasing the icon 302. Fig. 11B and Fig. 11C As shown, when the cancellation operation 1 is detected, the electronic device 100 displays a prompt message prompting to cancel the collaborative connection, and cancels the collaborative connection with the camera of the tablet computer. Fig.11D As shown, after canceling the collaborative connection, the display state of the icon 302 is switched from the collaborative state to the non-collaborative state, and the icon 302 is bounced back to the annular area. In one implementation, when it is detected that the user performs the above-mentioned cancel operation 1, the electronic device 100 may also directly display Fig.11D The collaborative connection interface shown does not need to display the above prompt information.

[0196] Exemplary, reference Fig.10F The icon 302 in the coordinated state is shown, and the icon 302 is displayed in the annular area. The cancel operation may include long pressing the icon 302. The cancel operation may also include gestures such as double-clicking, which is not specifically limited in this application.

[0197] In some embodiments, when the collaborative connection interface 13 receives an input operation from the user to cancel the collaborative connection (such as the cancellation operation 1 mentioned above), the icon of the candidate device stops rotating slowly; during the process of the electronic device 100 canceling the collaborative connection, the electronic device 100 can also play a connection cancellation animation; when it is determined that the collaborative connection has been canceled, the electronic device 100 can terminate the connection cancellation animation, and the icons of each candidate device resume rotating.

[0198] Case 2: The electronic device 100 and the candidate device 200 support collaborative connection of multiple capabilities; the candidate device 200 supports at least one capability that can be collaborative, and the icon of the candidate device 200 additionally displays capability badges of one or more capabilities (e.g., capability 1 and capability 2) among the at least one capability. When the icon of the candidate device 200 additionally displays capability badges corresponding to capability 1 and capability 2, dragging the icon of the candidate device 200 close to the icon of the electronic device 100 or dragging the icon of the candidate device 200 close to the icon of the electronic device 100 can realize the collaborative connection of the electronic device 100 to capability 1 and capability 2 of the candidate device 200.

[0199] For the collaborative connection of a capability in case 2, please refer to the above 6A to 7C as well as 9A to 10F The relevant description will not be repeated here.

[0200] For example, Fig. 12A Taking the collaborative connection interface 13 shown as an example, FIG. 12A to FIG. 12G A user interface for adding multiple capability badges is shown.

[0201] In some embodiments, the user can add capability badges corresponding to multiple capabilities on the tablet computer icon 302. Fig. 12A and Fig. 12B As shown, the tablet computer icon 302 in the collaborative connection interface 13 currently displays a capability badge 502 corresponding to the audio output function, and the icon 302 can receive user input operations (such as click operations); in response to the above input operations, the electronic device 100 displays capability badges corresponding to all collaborative capabilities supported by the tablet computer around the icon 302, for example, capability badge 501 corresponding to the camera, capability badge 502 corresponding to the audio input function, and capability badge 503 corresponding to the audio output function. Fig. 12B As shown, the capability badge 502 currently displayed in addition to the icon 302 is shown in a selected state (eg, displayed in a darker manner), and the capability badge 501 currently not displayed in addition to the icon 302 is shown in an unselected state (eg, displayed in a non-darkened manner).

[0202] Users can switch the display status of the capability badge to selected or unselected. Fig. 12B and Fig. 12C As shown, the user can switch the display state of the capability badge 501 to the selected state, and add the capability badge 501 as an additionally displayed capability badge of the icon 302. Fig. 12C and Fig.12D As shown, the user can also switch the display state of the capability badge 503 to a selected state, and add the capability badge 503 as an additionally displayed capability badge of the icon 302. Fig.12D and Fig.12E As shown, the capability badge 502 in the selected state can receive user input operations (such as click operations); in response to the above input operations, the display state of the capability badge 502 is switched to an unselected state, and the capability badge 502 is no longer displayed on the icon 302.

[0203] In some embodiments, Fig.12E and Fig.12F As shown, after the user selects the additionally displayed capability badges (i.e., capability badge 501 and capability badge 503), icon 302 can receive the user's input operation (e.g., touch operation), and in response to the input operation, electronic device 100 stops displaying the capability badges around icon 302.

[0204] In some embodiments, FIG. 12B to FIG. 12E In the process of selecting capability badges, when the user selects a capability badge (i.e., switches the display state of the capability badge to the selected state), icon 302 may not additionally display the capability badge. Fig.12FThe ability badge is only added to the icon 302 in the middle. For example, Figure 12G As shown, when the user selects capability badge 501 and capability badge 503 displayed around icon 302 , the above two capability badges do not need to be additionally displayed on icon 302 .

[0205] For example, FIG. 13A to FIG. 13J The relevant user interface for implementing collaborative connection in case 2 is shown.

[0206] like Fig.13A As shown, the icon 302 with the capability badge 501 and the capability badge 503 can receive a user's sliding operation, and the sliding direction of the sliding operation points to the icon 301 of the electronic device 100; when it is detected that the icon 302 contacts the area where the icon 301 is located, in response to the user's sliding operation, the electronic device 100 displays a prompt message 601 and performs a collaborative connection with the camera and audio output functions of the tablet computer. The prompt message 601 is used to prompt that the device is in a collaborative connection with the camera and audio output functions of the tablet computer.

[0207] In some embodiments, the electronic device 100 performs a collaborative connection for the camera and audio output functions of the tablet computer, which may include: the electronic device 100 sends a collaborative connection request for the camera and audio output functions to the tablet computer.

[0208] In some embodiments, Fig. 13B As shown, after receiving the collaborative connection request sent by the electronic device 100, the tablet computer displays a selection box, which includes prompt information 602, a camera selection control 603, an audio output function selection control 604, a confirmation control 605, and a rejection control 606. The prompt information 602 is used to prompt that the collaborative connection request for the camera and audio output functions of the electronic device 100 is received.

[0209] like Fig. 13C As shown, after the camera selection control 603 and the audio output function selection control 604 receive the user's selection operation (such as a click operation), the confirmation control 605 can receive the user's input operation. In response to the above input operation, the tablet computer sends a collaborative connection response 3 to the electronic device 100. The collaborative connection response 3 is used to indicate that the collaborative connection of the camera and audio output functions is approved. After the electronic device 100 receives the collaborative connection response 3 sent by the tablet computer, it displays Fig.13D The prompt information 607 shown in the figure changes the display state of the tablet computer icon from the non-coordinated state to the coordinated state. The capability subscript indicator and the prompt information 607 additionally displayed on the coordinated state icon 412 are used to prompt that the device has established a coordinated connection with the camera of the tablet computer and has established a coordinated connection with the audio output function of the tablet computer.

[0210] In some embodiments, reference Fig.13E In the control center interface 12 shown, after a collaborative connection is established for the camera and audio output functions of the tablet computer, the electronic device 100 displays the icons of the available devices that have been coordinated (for example, the tablet computer icon 412) in the collaboratively connected card 1, and the tablet computer icon 412 additionally displays the capability badges corresponding to the camera and audio output functions; the capability badges additionally displayed by the icon 412 indicate that a collaborative connection has been established with the camera and audio output functions of the tablet computer.

[0211] In some embodiments, Fig.13F As shown, after the camera selection control 603 receives the user's selection operation (such as a click operation), the confirmation control 605 can receive the user's input operation. In response to the above input operation, the tablet computer sends a collaborative connection response 4 to the electronic device 100. The collaborative connection response 4 is used to indicate that the collaborative connection of the camera is approved and the collaborative connection of the audio output function is rejected. After the electronic device 100 receives the collaborative connection response 4, it displays Figure 13G The prompt information 608 shown changes the display state of the tablet computer icon 302 from the uncoordinated state to the coordinated state, and stops attaching the capability badge of the audio output function to the icon 302. The prompt information 607 is used to prompt that the device has established a coordinated connection with the camera of the tablet computer, and that the coordinated connection with the audio output function of the tablet computer has failed.

[0212] Compared to Fig.13E In the collaborative connection card 1 shown, the camera collaborative connection is successful, but the audio output function collaborative connection fails. Fig.13H In the collaborative connection card 1 shown, the icon 412 of the collaborative tablet computer is only attached with a capability badge corresponding to the camera.

[0213] like Fig.13I As shown, the rejection control 404 can receive the user's input operation. In response to the above input operation, the tablet computer sends a collaborative connection response 5 rejecting the collaborative connection to the electronic device 100. After the electronic device 100 receives the collaborative connection response 5 sent by the tablet computer, it displays Fig.13J The prompt information 609 shown in the figure bounces the tablet computer icon 301 back to the annular area where the candidate device is located. The above prompt information 609 is used to prompt that the camera and audio output functions of the device and the tablet computer have failed to be connected in a coordinated manner.

[0214] In some embodiments, after the electronic device 100 establishes a collaborative connection with at least one capability of the candidate device 200 (eg, a tablet computer), the user may also select other capabilities of the candidate device for collaborative connection.

[0215] For example, FIG. 14A to FIG. 14E A related user interface of the coordinated tablet computer continuing the coordinated connection is shown.

[0216] like Fig.14A As shown, the electronic device 100 has currently established a collaborative connection with the audio input function of the tablet computer, and the icon 302 of the tablet computer in the collaborative state additionally displays a capability badge 502 corresponding to the audio input function. Fig.14A and Fig. 14B As shown, icon 302 can receive user input operations (such as click operations). In response to the above input operations, the electronic device 100 displays around the icon 302, capability badges corresponding to the collaborative capabilities supported by the tablet computer, such as capability badge 502 corresponding to the audio output function and capability badge 501 corresponding to the camera.

[0217] like Fig. 14B and Fig. 14C As shown, taking capability badge 501 as an example, capability badge 501 can receive a user input operation (e.g., a click operation); in response to the above input operation, electronic device 100 stops displaying capability badges around icon 302, displays prompt information 610 indicating that a collaborative connection is in progress, and performs a collaborative connection to the camera of the tablet computer. In some embodiments, Fig. 14C As shown, in response to the above input operation, the electronic device 100 also adds a camera capability badge 501 to the icon 302 .

[0218] like Fig.14D As shown, after the electronic device 100 determines that the collaborative connection is successful, it displays a prompt message 611 indicating that the collaborative connection is successful. Fig. 14C As shown, before the camera collaborative connection is successful, the camera capability badge 501 displayed in the icon 302 is in an uncoordinated state (eg, not displayed in a darkened state); Fig.14D As shown, after determining that the camera collaborative connection is successful, the electronic device 100 also switches the camera capability badge 501 to a collaborative state (eg, deepened display).

[0219] like Fig.14E As shown, after the electronic device 100 determines that the collaborative connection of the camera has failed, it displays a prompt message 612 indicating the collaborative connection failure, and stops attaching the camera capability badge 501 to the collaborative state icon 302 .

[0220] In some embodiments, when the icon of the candidate device 200 in the annular area (for example, the tablet computer icon 302) additionally displays multiple capability badges, the capabilities corresponding to the multiple capability badges can also be collaboratively connected by dragging the icon 301 of the device to the area where the icon of the candidate device 200 is located. FIG. 10A to FIG. 10F The relevant description will not be repeated here.

[0221] In the embodiment of the present application, after the electronic device 100 establishes a collaborative connection with multiple capabilities (such as capability 1 and capability 2) of the candidate device 200, the user can cancel the collaborative connection with the multiple capabilities or one of the multiple capabilities of the candidate device 200. The following is an example of a tablet computer.

[0222] In some embodiments, see Fig.14D , the tablet computer's coordinated state icon 302 is additionally provided with capability badges showing the camera and audio output functions. The tablet computer's coordinated state icon 302 can receive a user's cancel operation 1; in response to the above cancel operation 1, the electronic device 100 can cancel the coordinated connection of all coordinated capabilities of the tablet computer (i.e., the camera and audio output functions), and switch the display state of the icon 302 to a non-coordinated state. The cancel operation 1 can refer to the relevant description in the first case, which will not be repeated here.

[0223] In some embodiments, the tablet computer's coordinated state icon 302 is attached with multiple capability badges, and the user can individually cancel the coordinated connection of a capability among the multiple coordinated capabilities. Fig.15A Take the coordinated state shown as an example. FIG. 15A to FIG. 15D A related user interface for individually canceling the coordinated connection of the tablet computer's camera is shown.

[0224] like Fig.15A As shown, the tablet computer's collaborative state icon 302 can also receive a user's input operation (eg, a click operation); Fig. 15B As shown, in response to the above input operation, the capability badges corresponding to all the coordinated capabilities of the tablet computer are displayed. The capability badges corresponding to all the coordinated capabilities include capability badges corresponding to coordinated capabilities (such as capability badge 501 for the camera and capability badge 502 for the audio input function) and capability badges corresponding to uncoordinated capabilities (such as capability badge 503 for the audio output function). The capability badges corresponding to the coordinated capabilities (such as capability badge 501) are displayed as selected, and the capability badges corresponding to the uncoordinated capabilities (such as capability badge 503) are displayed as unselected. Fig. 15C As shown, the capability badge 501 can receive a user input operation (such as a click operation). In response to the input operation, the electronic device 100 can cancel the collaborative connection with the camera of the tablet computer and display a prompt message to cancel the collaborative connection; Fig.15D As shown, after canceling the cooperative connection with the camera of the tablet computer, the icon of the tablet computer in the cooperative state stops attaching the camera capability badge 501 .

[0225] In the embodiment of the present application, in the aforementioned situation 1 and situation 2, the electronic device 100 can support establishing collaborative connections with multiple devices at the same time.

[0226] For example, FIG. 16A to FIG. 16D The relevant user interface of the electronic device 100 establishing a cooperative connection with two devices is shown.

[0227] In some embodiments, the electronic device 100 may simultaneously establish collaborative connections with the same capability of multiple candidate devices.

[0228] like Fig.16A and Fig. 16B As shown, the electronic device 100 has established a collaborative connection with the audio output function and camera of the tablet computer; the icon 303 of the laptop computer is additionally provided with a capability badge 501 corresponding to the camera, and the user can drag the icon 303 to the area where the icon 301 of the electronic device 100 is located by sliding; when it is detected that the icon 302 is dragged to the area where the icon 301 is located, in response to the above sliding operation, the electronic device 100 displays a prompt message 616 indicating that a collaborative connection is being made, and executes a collaborative connection with the camera of the laptop computer.

[0229] like Fig. 16C As shown, when it is determined that the collaborative connection to the camera of the laptop computer is successful, a prompt message 617 indicating the successful collaborative connection is displayed, and the display state of the icon 303 of the laptop computer is changed from a non-collaborative state to a collaborative state; as shown in FIG. Fig.16D As shown, when it is determined that the collaborative connection to the camera of the notebook computer fails, a prompt message 618 indicating the collaborative connection failure is displayed, and the icon 303 of the notebook computer is bounced back to the annular area where the candidate device is located.

[0230] For details, please refer to 6A to 7C The relevant description will not be repeated here.

[0231] In some embodiments, for the same capability, the electronic device 100 establishes a collaborative connection with at most one device. Fig.16D The reason for the failure of the collaborative connection may be that the cameras of multiple devices cannot be collaboratively connected at the same time. The electronic device 100 may Fig.16D The prompt message 618 indicates that the cameras of multiple devices cannot be connected simultaneously.

[0232] Case 3: The electronic device 100 and the candidate device 200 support at most one capability of collaborative connection; the candidate device 200 supports at least one capability that can be collaborative, and the icon of the electronic device 100 can be attached with a capability badge showing any one of the at least one capability (e.g., capability 1). In some embodiments, when the icon of the electronic device 100 is attached with a capability badge corresponding to capability 1, dragging the icon of the candidate device 200 close to the icon of the electronic device 100 or dragging the icon of the electronic device 100 close to the icon of the candidate device 200 can realize the collaborative connection of the electronic device 100 with capability 1 of the candidate device 200.

[0233] For example, Fig.17A Taking the collaborative connection interface 13 shown as an example, FIG. 17A to FIG. 17B A related user interface is shown for adding a capability badge to the icon 301 of the electronic device 100 .

[0234] like Fig.17A and Fig. 17B As shown, the icon 301 of the electronic device 100 can receive an input operation (e.g., a click operation) from the user. In response to the input operation, the electronic device 100 displays at least one capability badge around the icon 301. In one implementation, the at least one capability badge includes the collaborative capabilities supported by all candidate devices displayed in the collaborative connection interface 13. Fig. 17B As shown, the at least one capability badge includes a camera capability badge 501, an audio output function capability badge 503, an audio input function capability badge 502, a screen projection capability badge 504 and a printing function capability badge 505.

[0235] In some embodiments, Fig. 17B As shown, the capability badge 503 corresponding to the audio output function can receive a user input operation (eg, a click operation); Fig. 17C As shown, in response to the above input operation, the electronic device 100 switches the display state of the capability badge 503 to a selected state, and additionally displays the capability badge 503 on the icon 301 . Fig. 17C The icon 301 shown can receive the user's input operation; Fig.17D As shown, in response to the above input operation, the electronic device 100 stops displaying the capability badge around the icon 301. In one implementation, in response to the input operation for Fig. 17B The electronic device 100 can directly display the input operation of the capability badge 503 shown in FIG. Fig.17D The collaborative connection interface 13 is shown.

[0236] In some embodiments, the user clicks Fig. 17BAfter the capability badge 503 is shown, the electronic device 100 can only display candidate device icons that can cooperate with the capability corresponding to the capability badge in the circular area. For example, the printer and the projector do not support the audio output function that can be cooperated; Fig.17E As shown, different from Fig. 17C In the collaborative connection interface 13 shown in FIG. 1 , in response to an input operation on the capability badge 503, the electronic device 100 stops displaying the printer icon 306 and the projector icon 305 in the circular area. Fig.17E and Fig.17F As shown, icon 301 can receive an input operation from a user. In response to the input operation, electronic device 100 stops displaying capability badges around icon 301. Fig. 17B The electronic device 100 may also directly display the input operation of the capability badge 503 shown. Fig.17F The collaborative connection interface 13 is shown.

[0237] In case 3, how to switch the additional display capability badge of the electronic device 100 can be referred to FIG. 8A to FIG. 8G The implementation method of the switching capability badge is not described here.

[0238] For example, Fig.18A Taking the collaborative connection interface 13 shown as an example, 18A to 18C The relevant user interface of the collaborative connection of a capability in case three is shown.

[0239] like Fig.18A As shown, after the user adds a capability badge 503 to the icon 301 of the device, the user can drag the icon 302 to the area where the icon 301 is located by sliding; when it is detected that the icon 302 contacts the icon 301 or the preset area 1 where the icon 301 is located, in response to the above sliding operation, the electronic device 100 displays a prompt message 701 indicating that a collaborative connection is in progress, and performs a collaborative connection with the audio output function of the tablet computer.

[0240] like Fig.18B As shown, when it is determined that the audio output function collaborative connection is successful, the electronic device 100 displays a prompt message 702 indicating the collaborative connection is successful, switches the icon 302 from the non-collaborative state to the collaborative state, and adds a capability badge 503 showing the audio output function to the icon 302. In one implementation, as Fig.18B As shown, after the collaborative connection is successful, the electronic device 100 stops attaching the display capability badge 503 to the icon 301 of the device itself, and displays all detected non-collaborative candidate devices in the circular area of ​​the candidate devices.

[0241] like Fig.18CAs shown, when it is determined that the collaborative connection of the audio output function fails, the electronic device 100 displays a prompt message 703 indicating the collaborative connection failure, and bounces the icon 302 back to the annular area where the candidate device is located.

[0242] In addition, how to cancel the collaborative connection of the collaborative capability in situation three can refer to the relevant description in situation one, which will not be repeated here. It should be noted that, taking the camera of a tablet computer as an example, if the collaborative connection of the camera of the tablet computer is canceled in situation three, after the collaborative connection is canceled, the icon 302 of the tablet computer will no longer be attached with the capability badge of the camera.

[0243] In some embodiments, the collaborative connection of the capabilities corresponding to the capability badges additionally displayed on the icon 302 can also be achieved by dragging the icon 301 of the device to the area where the icon 302 of the tablet computer is located.

[0244] For example, Fig.19A Taking the collaborative connection interface 13 shown as an example, FIG. 19A to FIG. 19E The relevant user interface of the collaborative connection in this embodiment is shown.

[0245] like Fig.19A and Fig.19B As shown, the user can drag the icon 301 of the present device to the icon 302 of the tablet computer through a sliding operation; when it is detected that the icon 301 contacts the icon 302, in response to the above sliding operation, the electronic device 100 displays a prompt message 701 indicating that a collaborative connection is being made, and performs a collaborative connection with the audio output function of the tablet computer.

[0246] like Fig.19C As shown, when it is determined that the audio output function collaborative connection is successful, the electronic device 100 displays a prompt message 702 indicating the successful collaborative connection, switches the tablet computer icon 302 from a non-collaborative state to a collaborative state, adds a capability badge 503 showing the audio output function to the icon 302, and bounces the device's icon 301 back to the circular area. Fig.19D FIG. 2 shows another coordinated state of an icon 302 provided in an embodiment of the present application, such as Fig.19D As shown, the icon 302 in the coordinated state is displayed darker and bounces back to the circular area together with the icon 301 of the device. Fig.19C and Fig.19D As shown, after icon 301 bounces back to the circular area, the additional display capability badge stops.

[0247] like Fig.19EAs shown, when it is determined that the collaborative connection of the audio output function fails, the electronic device 100 displays a prompt message 703 indicating the collaborative connection failure, and bounces the icon 301 of the device back to the circular area. The icon 301 can continue to be attached with the capability badge 503 showing the audio output function.

[0248] Similar to 9A to 9C In case three, the user can also drag the capability badge (such as capability badge 503) displayed around the icon 301 of the device to the icon 302 of the tablet computer to achieve a collaborative connection with the audio output function corresponding to the capability badge 503.

[0249] For example, Fig.19F and Figure 19G As shown, the user can drag the capability badge 503 to the tablet computer icon 302 through a sliding operation; Fig.19H As shown, when it is detected that the capability badge 503 contacts the icon 302 and the user releases the icon, in response to the above sliding operation, the electronic device 100 displays Fig.19H The prompt information 701 shown in the figure performs a collaborative connection with the audio output function of the tablet computer.

[0250] like Fig.19I As shown, when it is determined that the audio output function collaborative connection is successful, the electronic device 100 displays a prompt message 702 indicating the successful collaborative connection, switches the tablet computer icon 302 from a non-collaborative state to a collaborative state, and adds a capability badge 503 of the audio output function to the icon 302.

[0251] like Fig.19J As shown, when it is determined that the collaborative connection of the audio output function fails, the electronic device 100 displays a prompt message 703 indicating the collaborative connection failure, and the icon 301 can be additionally provided with a capability badge 503 indicating the audio output function.

[0252] Case 4: The electronic device 100 and the candidate device 200 support collaborative connection of multiple capabilities; the candidate device 200 supports at least one collaborative capability, and the icon of the electronic device 100 can be additionally displayed with capability badges of one or more capabilities (for example, capability 1 and capability 2) among the at least one capability.

[0253] In some embodiments, when the icon of electronic device 100 is attached with capability superscripts corresponding to capability 1 and capability 2, dragging the icon of candidate device 200 close to the icon of electronic device 100 or dragging the icon of electronic device 100 close to the icon of candidate device 200 can realize the collaborative connection of electronic device 100 to capability 1 and capability 2 of candidate device 200.

[0254] For the collaborative connection of a capability in case 4, please refer to the above FIG. 18A to FIG. 19JThe relevant description will not be repeated here.

[0255] For example, Fig. 20A Taking the collaborative connection interface 13 shown as an example, FIG. 20A to FIG. 20D A related user interface is shown in which two capability badges are additionally displayed for the icon 302 of the electronic device 100 .

[0256] like Fig. 20A and Fig. 20B As shown, the icon 301 of the electronic device 100 additionally displays a capability badge 503 of the audio output function; the icon 301 can receive a user input operation (such as a click operation), and in response to the input operation, the electronic device 100 displays at least one capability badge around the icon 301. In one implementation, the at least one capability badge includes the collaborative capabilities supported by the candidate device currently displayed in the collaborative connection interface 13. Fig. 17B , Fig. 20B The candidate device does not support the printing function, and the at least one capability badge does not include the capability badge 505 of the printing function.

[0257] In some embodiments, Fig. 20B As shown, the capability badge 501 corresponding to the camera can receive user input operations (such as click operations); Fig. 20C As shown, in response to the above input operation, the electronic device 100 adds the capability badge 501 as a capability badge additionally displayed in the icon 301 of the device. In one implementation, in response to the above input operation, the electronic device 100 also stops displaying the icons of candidate devices that do not support the camera corresponding to the capability badge 501 (e.g., the speaker icon 304), and / or switches the capability badges 501 displayed around from an unselected state to a selected state. Fig. 20C The icon 301 shown can receive a user input operation (eg, a click operation); Fig.20D As shown, in response to the above input operation, the electronic device 100 stops displaying the above at least one capability badge around the icon 301. In one implementation, in response to the above input operation, the electronic device 100 stops displaying the above at least one capability badge around the icon 301. Fig. 20B The electronic device 100 can directly display the input operation of the capability badge 503 shown in FIG. Fig.20D The collaborative connection interface 13 is shown.

[0258] In case 4, how to switch the capability badge attached to the electronic device 100 can also be referred to FIG. 12A to FIG. 12F The implementation method of the capability badge attached to the icon 302 for switching the tablet computer is not described in detail here.

[0259] For example, Fig.21A Taking the collaborative connection interface 13 shown as an example, FIG. 21A to FIG. 21DThe relevant user interface of the collaborative connection of two capabilities in case four is shown.

[0260] like Fig.21A As shown, after the user adds capability badge 503 and capability badge 501 to the icon 301 of the device, the user can drag the icon 302 to the area where the icon 301 is located by sliding; when it is detected that the icon 302 contacts the icon 301 or the preset area 1 where the icon 301 is located, the electronic device 100 displays a prompt message 711 indicating that a collaborative connection is in progress, and executes a collaborative connection with the audio output function and the camera of the tablet computer.

[0261] like Fig. 21B As shown, when it is determined that both the audio output function and the camera are successfully connected in a collaborative manner, the electronic device 100 displays a prompt message 712 indicating that the collaborative connection is successful, switches the icon 302 from a non-collaborative state to a collaborative state, and adds a camera capability badge 501 and an audio output function capability badge 503 to the icon 302. In one implementation, after the collaborative connection is successful, the icon 301 of the device stops adding the audio output function icon 503 and the camera icon 501, and displays all detected non-collaborative candidate devices in the circular area. Fig. 21B As shown, the electronic device 100 displays the speaker icon 304 , the projector icon 305 , and the printer icon 306 in the circular area again.

[0262] like Fig. 21C As shown, when it is determined that the camera collaborative connection is successful and the audio output function collaborative connection fails, the electronic device 100 displays a prompt message 713, switches the icon 302 from a non-collaborative state to a collaborative state, and adds a camera capability badge 501 to the icon 302. Prompt message 713 is used to prompt that the collaborative connection with the tablet computer's camera is successful, and the collaborative connection with the tablet computer's audio output function has failed. In one implementation, after the camera collaborative connection is successful and the audio output function collaborative connection fails, the icon 301 of the device stops attaching the camera icon 501, and displays the detected non-collaborative candidate devices that support the audio output function in the circular area. As shown in FIG. Fig. 21C As shown, the electronic device 100 displays the speaker icon 304 in the circular area again.

[0263] like Fig.21D As shown, when it is determined that both the audio output function and the camera have failed to be connected collaboratively, the electronic device 100 displays a prompt message 714 indicating that the collaborative connection has failed, and bounces the icon 302 back to the annular area where the candidate device is located.

[0264] Similar to FIG. 15A to FIG. 15DIn case 4, when the icon 301 of the device additionally displays multiple capability badges, the capabilities corresponding to the multiple capability badges can also be collaboratively connected by dragging the icon 301 of the device to the area where the icon of the candidate device 200 is located. FIG. 19A to FIG. 19E The relevant description will not be repeated here.

[0265] In some embodiments, after the electronic device 100 establishes a collaborative connection with at least one capability of the candidate device 200 (eg, a tablet computer), the user may also select other capabilities of the candidate device for collaborative connection.

[0266] For example, FIG. 22A to FIG. 23C A related user interface of the coordinated tablet computer continuing the coordinated connection is shown.

[0267] like Fig.22A As shown, the electronic device 100 has currently established a collaborative connection with the audio output function of the tablet computer. Fig. 22B , Fig. 22C and Fig.22D As shown, taking capability badge 501 as an example, the user can select capability badge 501 and add capability badge 501 as an additional capability badge displayed by icon 301. FIG. 20B to FIG. 20D The relevant description will not be repeated here.

[0268] like Fig.22D and Fig.23A As shown, after the user adds a capability badge 501 to the icon 301 of the device, the user can drag the icon 301 of the device to the area where the icon 302 is located by sliding; when it is detected that the icon 301 contacts the icon 302, the electronic device 100 displays a prompt message 721 in the collaborative connection prompt, and executes a collaborative connection with the camera of the tablet computer.

[0269] like Fig. 23B As shown, when it is determined that the collaborative connection is successful, the electronic device 100 displays a prompt message 722 indicating that the collaborative connection is successful, adds a camera capability badge 501 to the collaborative icon 302, and pops the icon 301 of the device back into the circular area 1.

[0270] like Fig.23C As shown, after the electronic device 100 determines that the collaborative connection of the camera has failed, it displays a prompt message 723 indicating the collaborative connection failure and bounces the icon 301 of the device back into the circular area.

[0271] For details, please refer to FIG. 19A to FIG. 19E The relevant description will not be repeated here.

[0272] In addition, how to cancel the collaborative connection of the collaborative capability in situation 4 can refer to the relevant description in situation 2, which will not be repeated here. It should be noted that, taking the camera of the tablet computer as an example, if the collaborative connection of the camera of the tablet computer is canceled in situation 4, after the collaborative connection is canceled, the icon 302 of the tablet computer will no longer be attached with the capability badge of the camera.

[0273] In the embodiment of the present application, in the aforementioned situations three and four, for the same capability, the electronic device 100 can establish a collaborative connection with multiple devices at the same time, or establish a collaborative connection with at most one device, which is not specifically limited here.

[0274] For example, FIG. 24A to FIG. 24E The relevant user interface of the electronic device 100 establishing a cooperative connection with two devices is shown.

[0275] like Fig.24A , Fig. 24B and Fig.24C As shown, the electronic device 100 has established a collaborative connection with the audio output function and camera of the tablet computer; the user can add at least one capability badge corresponding to the collaborative capability of the candidate device (for example, capability badge 503 corresponding to the audio output function) to the icon 301 of the device. Fig.24C and Fig.24D As shown, the user can drag the icon 301 of the device to the area where the icon 303 of the laptop is located through a sliding operation; in response to the above sliding operation, the electronic device 100 performs a collaborative connection with the audio output function of the laptop. Fig.24E As shown, when it is determined that the collaborative connection with the camera of the laptop is successful, the display state of the laptop icon 303 is changed from the un-collaborated state to the coordinated state, a capability badge 503 showing the audio output function is added to the icon 303, and the icon 301 is bounced back to the circular area. Fig.24F As shown, when it is determined that the cooperative connection to the camera of the laptop computer fails, the icon 301 is bounced back to the circular area.

[0276] For details, please refer to 17A to 18C The relevant description will not be repeated here.

[0277] Case 5: The user does not select an additional capability badge for the candidate device 200 or the electronic device 100, and the electronic device 100 can automatically select the capability for collaborative connection based on the current application scenario.

[0278] In the above-mentioned situations one and three, only one collaborative capability is supported between the electronic device 100 and the candidate device 200. If the user does not select an additional capability badge to be displayed for the candidate device 200 or the electronic device 100, and drags the icon of the candidate device 200 close to the icon of the electronic device 100 or drags the icon of the electronic device 100 close to the icon of the candidate device, the electronic device 100 can automatically select a capability from the collaborative capabilities supported by the candidate device 200 for a collaborative connection based on the current application scenario.

[0279] In the above-mentioned situations 2 and 4, the electronic device 100 and the candidate device 200 support at least one collaborative capability. If the user does not select an additional capability badge to be displayed for the candidate device 200 or the electronic device 100, and drags the icon of the candidate device 200 close to the icon of the electronic device 100 or drags the icon of the electronic device 100 close to the icon of the candidate device, the electronic device 100 can automatically select at least one capability from the collaborative capabilities supported by the candidate device 200 for a collaborative connection based on the current application scenario.

[0280] In some embodiments, the candidate device 200 in the collaborative connection interface 13 supports at least one collaborative capability, and when neither the icons 301 of the candidate device 200 nor the electronic device 100 are attached with a capability badge, the user drags the icon of the candidate device 200 close to the icon of the electronic device 100 or drags the icon of the electronic device 100 close to the icon of the candidate device through a sliding operation; in response to the above-mentioned sliding operation, the electronic device 100 automatically selects at least one capability (for example, capability 1) from the collaborative capabilities of the candidate device 200 for collaborative connection based on one or more of the application 1 that was most recently run in the foreground, the ranking of the number of times each capability has been collaboratively connected with the candidate device 200, the capability that was most recently collaboratively connected with the candidate device 200, the priority of each collaborative capability of the candidate device 200, etc.

[0281] In one implementation, first, the electronic device 100 determines the capability (e.g., capability 1) required by the application 1 that is recently running in the foreground, and automatically selects capability 1 from the collaborative capabilities of the candidate device 200 for collaborative connection; when the collaborative capabilities of the candidate device 200 do not include the capability required by the application 1, the electronic device 100 automatically selects at least one capability (e.g., capability 1) from the collaborative capabilities of the candidate device 200 for collaborative connection based on one or more of the ranking of the number of times each capability has been collaboratively connected with the candidate device 200, the capability that has been recently collaboratively connected with the candidate device 200, and the priority of each collaborative capability of the candidate device 200. In one implementation, the electronic device 100 selects at least one capability (e.g., capability 1) that ranks high among the capabilities that have been collaboratively connected with the candidate device 200 for collaborative connection; wherein the above ranking of the number of times may refer to the ranking of the number of collaborative connections of each capability within a recent preset time period (e.g., the last week), or the ranking of the number of collaborative connections of each capability within a recent preset total number of connections (e.g., the last 10 times). In one implementation, the electronic device 100 selects at least one capability that has been most recently collaboratively connected with the candidate device 200 for collaborative connection. In one implementation, the electronic device 100 selects at least one capability with the highest priority among the capabilities that can be collaboratively connected with the candidate device 200 for collaborative connection; wherein the priority of each capability may be preset by the electronic device 100 or by the user, which is not specifically limited here.

[0282] In some embodiments, the capabilities required by application 1 include capability 1. When application 1 is running in the foreground on electronic device 100, collaborative connection interface 13 is called up; candidate devices (for example, candidate device 200) in collaborative connection interface 13 all support capability 1, and when neither the icons 301 of candidate device 200 and electronic device 100 are attached with capability badges, the user drags the icon of candidate device 200 close to the icon of electronic device 100 or drags the icon of electronic device 100 close to the icon of candidate device 200 through a sliding operation; in response to the above sliding operation, electronic device 100 automatically selects the capability required by application 1 (for example, capability 1) from the capabilities supported by candidate device 200 for collaborative connection.

[0283] For example, FIG. 25A to FIG. 25D A user interface is shown for determining the capabilities of a collaborative connection based on a current application scenario.

[0284] like Fig.25A and Fig.25B As shown, taking the music APP as an example, when the electronic device 100 runs the music APP in the foreground, in response to the user's input operation, the collaborative connection interface 13 is displayed; the capabilities required by the music APP include the audio output function, and the candidate devices displayed in the circular area in the collaborative connection interface 13 all support the audio output function. Fig.25B and Fig.25C As shown, in the collaborative connection interface 13, neither the tablet computer icon 302 nor the electronic device 100 icon 301 is attached with a capability badge. The user drags the tablet computer icon 301 close to the device icon 301 through a sliding operation. In response to the sliding operation, the capability required by the music APP (such as the audio output function) is selected from the capabilities that the tablet computer can collaborate with for collaborative connection. Fig.25D As shown, when it is determined that the cooperative connection with the audio output function of the tablet computer is successful, the icon 302 of the tablet computer is switched to a cooperative state, and a capability badge 503 showing the audio output function is added to the icon 302 .

[0285] In the embodiment of the present application, in the aforementioned situation five, the electronic device 100 can also support establishing collaborative connections with multiple devices at the same time, which will not be repeated here.

[0286] The following is an exemplary introduction to the application of capabilities after collaborative connection is achieved in the embodiments of the present application.

[0287] For example, Fig.26A The collaborative connection interface 13 shown in FIG. Fig.26A As shown, according to the capability badges additionally displayed on the available devices that have been collaboratively connected, it can be seen that the audio output function and camera of the tablet computer, the audio output function of the laptop computer, and the printing function of the printer have established a collaborative connection with the electronic device 100.

[0288] For example, Fig.26B and Fig.26C As shown, after the user clicks the switch control 311 in the music playback interface 14, the electronic device 100 displays a selection box, which includes options for available devices that currently have coordinated audio output functions (i.e., option 801 for a tablet computer and option 802 for a laptop computer), as well as a confirmation control 803 and a rejection control 804. Fig.26D As shown, after the user selects at least one available device option (e.g., option 801 for a laptop), an input operation (e.g., a click operation) acting on a confirmation control 803 is detected. In response to the input operation, the electronic device 100 can call the audio output function of the laptop to play music. The rejection control 804 can receive the user's input operation (e.g., a click operation). In response to the input operation, the electronic device 100 stops displaying the selection box.

[0289] In some embodiments, the electronic device 100 can collaboratively connect to the same capability (e.g., capability 1) of multiple devices. In one implementation, for capabilities 1 of multiple collaborative available devices, the electronic device 100 only supports calling capability 1 of one available device at a time. In one implementation, for capabilities 1 of multiple collaborative available devices, the electronic device 100 supports calling capabilities 1 of multiple available devices at the same time. For example, the user selects Fig.26D After selecting the tablet option 801 and the laptop option 802, the electronic device 100 detects an input operation acting on the control 803; in response to the input operation, the electronic device 100 can simultaneously call the audio output function of the tablet computer and the laptop computer to play music.

[0290] In some embodiments, when the electronic device 100 needs to call the capability 1 of the available device, it is not necessary to display the options of the available devices that have been collaboratively connected for the user to select. The electronic device 100 can automatically select at least one available device from the available devices that have been collaboratively connected, and call the capability 1 of the at least one available device. For example, Fig.26B As shown, in response to the input operation for the switching control 311, the electronic device 100 can automatically select an available device with execution capability 1 from the available devices that have coordinated the audio output function (i.e., tablet computers and laptop computers); for example, the electronic device 100 automatically selects an available device with a large number of coordinated connections for the audio output function, or an available device that has recently coordinated the audio output function. The selection strategy of the electronic device 100 is not specifically limited here.

[0291] In some embodiments, if the electronic device 100 is only collaboratively connected to the capability 1 of one available device, when the electronic device 100 needs to call the capability 1 of other devices, there is no need to display options of the collaboratively connected available devices for the user to select, and the electronic device 100 can directly call the capability 1 of the collaboratively available device.

[0292] It should be noted that FIG. 26A to FIG. 26D It is an exemplary description of the application of the capabilities of the available coordinated devices in the embodiments of the present application and should not constitute a limitation on the embodiments of the present application.

[0293] With reference to the aforementioned collaborative connection interface 13, it can be seen that the collaborative connection interface 13 provided in the embodiment of the present application adopts a two-layer ring layout design. First, the first-layer ring layout reflects the association relationship between other devices and this device, that is, the first-layer ring displays the icons of the collaborative candidate devices detected by this machine, and the collaborative state (non-collaborative state or collaborative state) of the icon of the candidate device can indicate whether the capabilities of this device and the candidate device have established a collaborative connection. In this way, through the first-layer ring layout, the user can intuitively see one or more candidate devices that can currently be collaboratively connected with this device, as well as the collaborative state of the candidate device, so that the user can select the candidate device to be collaborative. Secondly, the second-layer ring layout reflects the collaborative capabilities supported by the candidate device, that is, the capability badge corresponding to the collaborative capability is displayed. In this way, through the second-layer ring layout, the user can intuitively see the various capabilities that the candidate device can collaborate with. The user can select and switch the capability badge displayed in the icon of the candidate device through the capability badge displayed in the second-layer ring, thereby realizing the selection and switching of the capability of the collaborative connection. After establishing a collaborative connection with capability 1 of the candidate device 200 , a capability badge is additionally displayed on the icon of the candidate device 200 in the collaborative state, which can also intuitively indicate to the user the collaborative capability of the candidate device 200 .

[0294] In the embodiment of the present application, the page style of the two-layer ring layout design in the collaborative connection interface 13 is coordinated and unified, and the visual effect is good. The interface interaction of the user selecting the capability to be coordinated, implementing the collaborative connection, and canceling the collaborative connection is highly playable and interesting, which effectively improves the user experience.

[0295] In some embodiments, the electronic device 100 supports at least one capability that can be coordinated, and the icon additionally displayed on the electronic device 100 is the capability badge of any capability (e.g., capability 1) of the at least one capability of the electronic device 100. The user can achieve a coordinated connection between the candidate device 200 and capability 1 of the electronic device 100 by sliding the icon of the candidate device 200 close to the icon of the electronic device 100 or by dragging the icon of the electronic device 100 close to the icon of the candidate device; after the coordinated connection is successful, the candidate device 200 can call capability 1 of the electronic device 100.

[0296] Exemplary, reference Fig.17A and Fig. 17B , the user clicks the icon 301 of the electronic device 100, and the electronic device 100 can display the capability badge of at least one capability of the electronic device 100 that can be coordinated around the icon 301; FIG. 17B to FIG. 17D, the user can select one or more capability badges to be displayed for icon 301. The user drags the icon of the candidate device 200 (e.g., the tablet icon 302) to icon 301 by performing a sliding operation; in response to the sliding operation, the electronic device 100 executes the collaborative connection process of the candidate device 200 to the capability 1 of the electronic device 100; after the collaborative connection is successful, the electronic device 100 can switch the display state of the candidate device 200 to the collaborative state.

[0297] In one implementation, the electronic device 100 executes a collaborative connection process of the candidate device 200 for the capability 1 of the electronic device 100, which may include: the electronic device 100 sends a collaborative connection request 5 to the candidate device 200, the collaborative connection request is used to request the candidate device 1 to perform a collaborative connection with the capability 1 of the electronic device 100, and the collaborative connection request 5 may carry collaborative connection parameters of the capability 1 of the electronic device 100; the candidate device 200 may establish a collaborative connection with the capability 1 of the electronic device 100 based on the above-mentioned collaborative connection parameters, and send a collaborative connection response indicating a successful collaborative connection to the electronic device 100.

[0298] In some embodiments, if the electronic device 100 is collaboratively connected to the capability 1 of the candidate device 200, the icon of the candidate device 200 in the collaborative connection interface is presented as the collaborative state 1; when the candidate device 200 is collaboratively connected to the capability 1 of the electronic device 100, the icon of the candidate device 200 in the collaborative connection interface is presented as the collaborative state 2; the collaborative state 1 is different from the collaborative state 2. For example, Fig.19D The coordinated state 1 of the icon 302 of the tablet computer is shown. Fig.19C The coordinated state 2 of the icon 302 of the tablet computer is shown.

[0299] The software system of the electronic device 100 can adopt a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. The embodiment of the present application takes the Android system of the layered architecture as an example to illustrate the software structure of the electronic device 100. Of course, in other operating systems, as long as the functions implemented by each functional module are similar to the embodiments of the present application.

[0300] Fig. 27 It is a software structure block diagram of the electronic device 100 according to an embodiment of the present application.

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

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

[0303] like Fig. 27 As shown, in the application layer, you can install games, cameras, navigation, calendars, galleries, Bluetooth, music, text messages, Word and other APPs (applications).

[0304] It should be noted that when the electronic device 100 runs an application installed in the application layer, it may need to call specific capabilities. For example, when a music APP plays music, it needs to call the audio output function, when a camera APP takes a photo, it needs to call the camera, and when a Word APP prints a word document, it needs to call the print function.

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

[0306] like Fig. 27 As shown, the application framework layer may include a window manager, a display module, a content provider, a view system, a resource manager, a notification manager, and the like.

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

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

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

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

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

[0312] like Fig. 27 As shown, in some embodiments, the application framework layer may also include an audio playback module and an image acquisition module.

[0313] Exemplarily, the audio player can be a player such as AudioTrack or MediaPlayer. When the audio APP needs to play audio, the audio player can be called to input the corresponding audio data into the audio player. For example, the audio APP can input the original audio data into the audio player, and the audio player parses, decapsulates or decodes the original audio data to obtain frames of PCM (pulse code modulation) data. Alternatively, the audio APP can also directly output PCM data to the audio player. The audio player is used to call the speaker to output audio.

[0314] When the camera APP needs to collect images, it can call the image acquisition module and input the image acquisition instruction to the image acquisition module. The image acquisition module is used to call the camera to collect images.

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

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

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

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

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

[0320] 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.

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

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

[0323] like Fig. 27 As shown, a HAL (hardware abstraction layer) may also be included between the application framework layer and the kernel layer of the Android system. The HAL is responsible for interacting with the various hardware devices of the electronic device 100. On the one hand, the HAL hides the implementation details of each hardware device, and on the other hand, it can provide the Android system with an interface for calling each hardware device. The HAL provides HALs corresponding to different hardware devices, such as audio (Audio) HAL, camera (Camera) HAL, display (Display) HAL, etc.

[0324] 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.

[0325] The audio playback module can call the audio HAL, send the audio data to the audio HAL, and the audio HAL calls the audio driver of the kernel layer to send the audio data to the audio output device of the device (such as a speaker) to drive the audio output device of the device to play the above audio data. The image acquisition module can call the camera HAL, send the image acquisition instruction to the camera HAL, and the camera HAL drives the camera of the device to acquire images by calling the camera driver of the kernel layer.

[0326] In some embodiments, Fig.28As shown, a device virtualization (DeviceVirtualization) APP for realizing capability collaboration can be installed in the application layer of the electronic device 100, which may be referred to as DV APP later. The DV APP can be resident in the electronic device 100 and run as a system application. Alternatively, the capability collaboration realized by the DV APP can also be resident in the electronic device 100 and run in the form of a system service. When the electronic device 100 is successfully connected to the capability 1 (such as audio output function, camera, etc.) of the candidate device 200, the electronic device 100 obtains the capability parameters of the capability 1 of the candidate device 200, and the DV APP can create a virtual device corresponding to the candidate device 200 in the electronic device 100 according to the capability parameters of the capability 1 of the candidate device 200, and the virtual device has capability 1; in this way, the electronic device 100 can call the capability 1 of the candidate device 200 through the virtual device.

[0327] For example, taking the candidate device 200 as a tablet computer, Fig.28 The HAL layers shown also include the tablet DV HAL created by the DV APP. FIG. 6A to FIG. 6D When the electronic device 100 detects that the electronic device 100 and the tablet computer's camera are successfully connected, the DV APP obtains the tablet computer's related information (such as the collaborative capabilities, device identification, device name, device model and device type, etc.) and the tablet computer's camera capability parameters, and creates a calling interface for the virtual device corresponding to the tablet computer in the HAL layer (for ease of description, the calling interface is referred to as the tablet computer DV HAL); the tablet computer DV HAL includes the camera HAL corresponding to the tablet computer. FIG. 14A to FIG. 14D After the electronic device 100 successfully connects with the camera of the tablet computer, when the electronic device 100 detects that the electronic device 100 successfully connects with other capabilities of the tablet computer (such as audio output function), the DV APP obtains the capability parameters of the audio output function of the tablet computer (such as playback delay, audio sampling rate, etc.), and creates an audio HAL corresponding to the tablet computer in the tablet computer DV HAL based on the capability parameters. After the electronic device 100 detects the user's input operation of calling the tablet computer's camera, the camera APP sends instruction 2 to the image acquisition module, and instruction 2 is used to instruct to call the tablet computer's camera to capture images; the image acquisition module sends a camera call request to the tablet computer by calling the camera HAL in the tablet computer DV HAL.

[0328] See also Fig.29, a collaborative APP for realizing capability collaboration can be installed in the application layer of the tablet computer. When the electronic device 100 establishes a collaborative connection with the camera of the tablet computer, the capability parameters of the camera of the tablet computer can be obtained from the collaborative APP of the tablet computer. After the collaborative connection is successful, the collaborative APP can receive the camera call request sent by the tablet computer; in response to the above call request, the collaborative APP can send an instruction to the image acquisition module of the application framework layer of the tablet computer to instruct the image acquisition module to capture the image by calling the camera HAL of the HAL layer of the tablet computer; the camera HAL can call the camera driver to drive the camera of the tablet computer to capture image 1; the collaborative APP obtains the above image 1 and sends the image 1 to the camera APP of the electronic device 100; the camera APP can display the above image 1 in the image preview area of ​​the shooting interface 15.

[0329] For example, taking the candidate device 200 as a laptop computer YYY, Fig.28 The HAL layers shown also include the laptop DV HAL created by the DV APP. FIG. 16A to FIG. 16C When the electronic device 100 detects that the electronic device 100 is successfully connected to the audio output function of the laptop computer, the DV APP obtains the relevant information of the laptop computer and the capability parameters of the audio output function of the laptop computer, and creates a calling interface of the virtual device corresponding to the laptop computer in the HAL layer based on the relevant information of the laptop computer and the capability parameters of the audio output function of the laptop computer (for the convenience of description, the calling interface is referred to as the laptop computer DV HAL); the laptop computer DV HAL includes an audio HAL generated based on the capability parameters of the above audio output function. After the electronic device 100 detects the user's input operation of calling the audio output function of the laptop computer, the music APP sends instruction 1 and audio data 1 to the audio playback module, and instruction 1 is used to instruct to call the audio output function of the laptop computer to play audio data 1; the audio playback module sends a call request for the audio output function to the laptop computer by calling the audio HAL in the laptop computer DV HAL, and the call request includes audio data 1.

[0330] See also Fig.30, a collaborative APP can also be installed in the application layer of the laptop. When the electronic device 100 establishes a collaborative connection with the audio output function of the laptop, the capability parameters of the audio output function can be obtained from the collaborative APP of the laptop. After the collaborative connection is successful, the collaborative APP can receive a call request for the audio output function sent by the electronic device 100; in response to the above call request, the collaborative APP can send an instruction to the audio playback module of the application framework layer of the laptop to instruct the audio playback module to play audio data 1 by calling the audio HAL of the HAL layer of the laptop; the camera HAL can call the audio driver to drive the speaker of the tablet to play audio data 1.

[0331] For example, taking the candidate device 200 as a printer EEE, Fig.28 The HAL layer shown also includes a printer DV HAL created by the DV APP. When the electronic device 100 detects that the electronic device 100 is successfully connected to the printing function of the printer, the DV APP obtains the relevant information of the printer and the capability parameters of the printing function, and creates a calling interface of the virtual device corresponding to the printer in the HAL layer (for the convenience of description, the calling interface is referred to as the printer DV HAL); the printer DV HAL includes a printing HAL generated based on the capability parameters of the above printing function. The application framework layer of the electronic device 100 may also include a printing management module. After the electronic device 100 detects the user's input operation to call the printer's printing function, the Word APP sends an instruction 3 and document data 1 to the printing management module, and the instruction 3 is used to instruct the printer's printing function to print document data 1; the printing management module sends a printing function call request to the printer by calling the printing HAL in the printer DV HAL, and the call request includes document data 1.

[0332] See also Fig.31 , a collaborative APP can also be installed in the application layer of the printer. When the electronic device 100 establishes a collaborative connection with the printing function of the printer, the capability parameters of the printing function can be obtained from the collaborative APP of the printer. After the collaborative connection is successful, the collaborative APP can receive a call request for the printing function sent by the electronic device 100; in response to the above call request, the collaborative APP can send an instruction to the printing management module of the application framework layer of the printer to instruct the printing management module to print document data 1 by calling the printing HAL of the HAL layer of the printer.

[0333] Based on the above Figures 1A to 31 The embodiments described above will now introduce the device collaboration method provided by the present application.

[0334] For example, Fig.32: is a flow chart of a device collaboration method provided in an embodiment of the present application, the method is applied to a first electronic device, and the method includes:

[0335] S101. Display a first user interface; the first user interface includes a first icon of a first electronic device and an icon of at least one detected candidate device, the icon of the at least one candidate device includes a second icon of a second electronic device, the second electronic device supports at least two collaborative capabilities, and the at least two collaborative capabilities include the first capability.

[0336] Among them, the first electronic device may be the electronic device 100 described in the aforementioned embodiment, and the second electronic device may be the candidate device 200 (for example, a tablet computer) described in the aforementioned embodiment; the first user interface may be the collaborative connection interface 13 described in the aforementioned embodiment, the first icon may be the icon 301 in the collaborative connection interface 13, and the second icon may be the icon 302 in the collaborative connection interface 13.

[0337] Exemplarily, the second electronic device is the tablet computer described in the above embodiment, and the collaborative capabilities of the tablet computer include supporting a camera, an audio input function, and an audio output function. The first capability may be any one of the collaborative capabilities of the above tablet computer.

[0338] S102: Receive a first input operation for selecting the first capability.

[0339] S103: Receive a second input operation.

[0340] S104: In response to the second input operation, establish a collaborative connection supporting the first capability with the second electronic device.

[0341] In some embodiments, the first user interface further includes: capability badges corresponding to the collaborative capabilities supported by the second electronic device; the capability badges corresponding to the collaborative capabilities supported by the second electronic device include a first capability badge corresponding to the first capability, and the first input operation acts on the first capability badge. In one implementation, in the first user interface, capability badges corresponding to the collaborative capabilities supported by the second electronic device are displayed in an area around the second icon.

[0342] Exemplary, reference Figure 8B , Fig. 8E , Fig.9A and Fig. 12B The area around the icon 302 in the collaborative connection interface 13 displays the capability corner marks corresponding to the collaborative capabilities of the tablet computer. Figure 8B , Fig. 8E and Fig.9AAs shown, the first capability badge may be a capability badge 502 corresponding to the audio input function, and the first input operation for selecting the audio input function acts on the capability badge 502 .

[0343] In some embodiments, before receiving the first input operation for selecting the first capability, the method also includes: receiving a third input operation acting on the second icon; and in response to the third input operation, displaying the capability badge corresponding to the collaborative capability supported by the second electronic device in the first user interface.

[0344] Exemplary, reference FIG. 8A to FIG. 8G as well as FIG. 12A to FIG. 12F Related descriptions, such as Fig. 8A and Fig. 12A As shown, the third input operation may include an input operation (eg, a click operation) acting on the icon 302. It is understood that after the user clicks the tablet computer icon 302, the electronic device 100 displays the capability badges corresponding to the tablet computer's collaborative capabilities in the collaborative connection interface 13.

[0345] In some embodiments, the method further includes: in response to the first input operation, additionally displaying a first capability badge on the second icon.

[0346] Exemplary, reference FIG. 8A to FIG. 8G , after the user selects the capability badge 502, that is, after the electronic device 100 receives the first input operation acting on the capability badge 502, the capability badge 502 is additionally displayed on the icon 302. FIG. 12A to FIG. 12D As described above, after the user selects capability badge 501 (or capability badge 503), that is, after the electronic device 100 receives the first input operation acting on capability badge 501 (or capability badge 503), capability badge 501 (or capability badge 503) is additionally displayed on icon 302.

[0347] In some embodiments, in response to a third input operation, a capability badge corresponding to a collaborative capability supported by the second electronic device is displayed in the first area; the at least two collaborative capabilities also include a second capability, and when receiving the third input operation acting on the second icon, the second icon is additionally displayed with a second capability badge corresponding to the second capability; after receiving the third input operation acting on the second icon, it also includes: receiving a fourth input operation acting on the second capability badge in the first area; in response to the fourth input operation, stopping displaying the second capability badge on the second icon.

[0348] Exemplary, reference FIG. 12A to FIG. 12F Related descriptions, such as Fig. 12A As shown, when receiving the third input operation acting on the icon 302, the icon 302 is attached with a display capability badge 502; Fig.12DAs shown, a fourth input operation (eg, a touch operation) acting on the capability badge 502 in the first area (eg, the surrounding area near the icon 302) is received; as shown Fig.12E As shown, in response to the fourth input operation, the capability badge 502 is stopped from being attached to the icon 302 .

[0349] In some embodiments, among the capability badges displayed around the second icon, the capability badge that is attached to the second icon is presented as a selected state, and the capability badge that is not attached to the second icon is presented as an unselected state; the method also includes: in response to a first input operation, switching the first capability badge displayed around the second icon from an unselected state to a selected state; the method also includes: in response to a fourth input operation, switching the second capability badge displayed around the second icon from a selected state to an unselected state.

[0350] Exemplary, reference FIG. 12A to FIG. 12F Related descriptions, such as FIG. 12B to FIG. 12E As shown, the icon 302 with the additional displayed capability badge is displayed as selected, and the icon 302 without the additional displayed capability badge is displayed as unselected; Fig. 12B and Fig. 12C As shown, in response to the first input operation acting on the capability badge 501, the capability badge 501 displayed around the icon 302 is switched from an unselected state to a selected state; Fig.12D and Fig.12E As shown, in response to the fourth input operation acting on the capability badge 502, the capability badge 502 displayed around the icon 302 is switched from a selected state to an unselected state.

[0351] In some embodiments, the first input operation includes an operation acting on the first capability badge; the second input operation includes: dragging the second icon toward the first icon until the second icon contacts the area where the first icon is located; or, dragging the second icon toward the first icon until the distance between the second icon and the first icon is less than or equal to a preset threshold; or, dragging the first icon toward the second icon until the first icon contacts the area where the second icon is located; or, dragging the first icon toward the second icon until the distance between the first icon and the second icon is less than or equal to a preset threshold.

[0352] Exemplary, reference FIG. 6A to FIG. 6D , the second input operation may include: dragging icon 302 toward icon 301 until icon 302 contacts the area where icon 301 is located; or, dragging icon 302 toward icon 301 until the distance between icon 302 and icon 301 is less than or equal to a preset threshold. FIG. 10A to FIG. 10D, the second input operation may include: dragging icon 301 toward icon 302 until icon 301 contacts the area where icon 302 is located; or dragging icon 301 toward icon 302 until the distance between icon 302 and icon 301 is less than or equal to a preset threshold. For example, the preset threshold is a length of 5 pixels.

[0353] In some embodiments, the second input operation acts on the first capability badge.

[0354] In some embodiments, the first input operation includes an operation on the first capability badge; the second input operation includes: dragging the first capability badge toward the first icon until the first capability badge touches the area where the first icon is located; or, dragging the first capability badge toward the first icon until the distance between the first capability badge and the first icon is less than or equal to a preset threshold. For example, the first capability badge is capability badge 502.

[0355] Exemplary, reference 9A to 9C , the first input operation and the second input operation both act on the capability badge 502. For example, the first input operation includes a touch operation on the capability badge 502; the second input operation includes: dragging the capability badge 502 toward the icon 301 until the capability badge 502 contacts the area where the icon 301 is located; or, dragging the capability badge 502 toward the icon 301 until the distance between the capability badge 502 and the icon 301 is less than or equal to a preset threshold. For example, the preset threshold is a length of 5 pixels.

[0356] In some embodiments, the at least two collaborative capabilities also include a second capability; after successfully establishing a collaborative connection supporting the first capability with the second electronic device, the method also includes: receiving a fifth input operation acting on the second icon; in response to the fifth input operation, displaying capability badges corresponding to the collaborative capabilities supported by the second electronic device, the capability badges corresponding to the collaborative capabilities supported by the second electronic device include a first capability badge corresponding to the first capability, and a second capability badge corresponding to the second capability; receiving a sixth input operation acting on the second capability badge; in response to the sixth input operation, establishing a collaborative connection supporting the second capability with the second electronic device.

[0357] Exemplary, reference FIG. 14A to FIG. 14E Related descriptions, such as Fig.14A As shown, after the electronic device 100 establishes a collaborative connection with the candidate device 200 (eg, a tablet computer) that supports the audio input function (ie, the first capability), it receives a fifth input operation (eg, a touch operation) acting on the icon 302; Fig. 14BAs shown, in response to the fifth input operation, the capability badges corresponding to the collaborative capabilities supported by the tablet computer are displayed, such as the capability badge 501 corresponding to the camera (ie, the second capability badge corresponding to the second capability); Fig. 14B As shown, a sixth input operation (eg, a touch operation) acting on the capability badge 501 is received; as shown Fig. 14C and Fig.14D As shown, in response to the sixth input operation, a collaborative connection supporting a camera is established with the tablet computer.

[0358] In some embodiments, the at least two collaborative capabilities also include a second capability; and establishing a collaborative connection with the second electronic device that supports the first capability in response to the second input operation specifically includes: establishing a collaborative connection with the second electronic device that supports the first capability and the second capability in response to the second input operation.

[0359] Exemplary, reference FIG. 13A to FIG. 13D According to the relevant description, the collaborative capabilities of the tablet computer include camera and audio output functions (i.e., the first capability and the second capability). In response to the second input operation acting on icon 302 (for example, dragging from icon 301 to icon 302), the electronic device 100 and the tablet computer establish a collaborative connection that supports the camera and audio output functions.

[0360] In some embodiments, when the second input operation is received, the second icon is additionally displayed with a first capability superscript corresponding to the first capability and a second capability superscript corresponding to the second capability.

[0361] Exemplary, reference FIG. 13A to FIG. 13D As described above, when a second input operation acting on icon 302 (for example, dragging icon 301 to icon 302) is received, icon 302 is additionally displayed with a capability badge 501 corresponding to the camera and a capability badge 503 corresponding to the audio output function.

[0362] In some embodiments, after successfully establishing a collaborative connection supporting the first capability and the second capability with the second electronic device, the method also includes: receiving a seventh input operation acting on the second icon; in response to the seventh input operation, displaying capability badges corresponding to the collaborative capabilities supported by the second electronic device, the capability badges corresponding to the collaborative capabilities supported by the second electronic device include a first capability badge corresponding to the first capability, and a second capability badge corresponding to the second capability; receiving an eighth input operation acting on the first capability badge; in response to the eighth input operation, canceling the collaborative connection supporting the first capability with the second electronic device.

[0363] Exemplary, reference FIG. 15A to FIG. 15D Related descriptions, such as Fig.15AAs shown, after the electronic device 100 establishes a collaborative connection with the tablet computer that supports camera and audio input functions, the icon 302 can receive the seventh input operation (eg, touch operation) of the user; Fig. 15B As shown, in response to the seventh input operation, the capability badges corresponding to the collaborative capabilities supported by the tablet computer are displayed in the collaborative connection interface 13, including the capability badge 501 corresponding to the collaborative camera and the capability badge 502 corresponding to the collaborative audio input function; Fig. 15B As shown, an eighth input operation (eg, a touch operation) acting on the capability badge 501 is received; as Fig. 15C and Fig.15D As shown, in response to the eighth input operation, the cooperative connection with the supporting camera of the tablet computer is cancelled.

[0364] In some embodiments, in response to the seventh input operation, among the capability badges displayed around the second icon, the capability badges corresponding to the capabilities supported by the collaborative connection established with the second electronic device (i.e., the first capability badge and the second capability badge) are presented as selected, and the capability badges corresponding to the capabilities not supported by the collaborative connection established with the second electronic device are presented as unselected.

[0365] Exemplary, reference FIG. 15A to FIG. 15D Related descriptions, such as Fig. 15B As shown, after the electronic device 100 establishes a collaborative connection with the tablet computer that supports the camera and audio input functions, among the capability badges displayed around the collaborative icon 302, the capability badge 501 corresponding to the collaborative camera and the capability badge 502 corresponding to the audio input function appear as selected, and the capability badge 503 corresponding to the uncoordinated audio output function appears as unselected.

[0366] In some embodiments, after successfully establishing a collaborative connection supporting the first capability and the second capability with the second electronic device, the method further includes: receiving a tenth input operation acting on the second icon; and in response to the tenth input operation, canceling the collaborative connection with the second electronic device for any capability. For example, the tenth input operation is the cancel operation 1 described in the above embodiment.

[0367] Exemplary, reference FIG. 11A to FIG. 11D Related descriptions, such as Fig. 11B As shown, after the electronic device 100 establishes a collaborative connection with the tablet computer, it receives a tenth input operation acting on the icon 301 (for example, an input operation of dragging the icon 302 away from the icon 301); in response to the tenth input operation, the collaborative connection with the tablet computer for any capability is canceled.

[0368] In some embodiments, the first user interface also includes capability badges corresponding to at least two capabilities; the at least two capabilities include all collaborative capabilities supported by the at least one candidate device, the capability badges corresponding to the at least two capabilities include a first capability badge corresponding to the first capability, and the first input operation acts on the first capability badge.

[0369] Exemplary, reference Fig. 17B and Fig.19F , capability badges corresponding to all collaborative capabilities supported by all detected candidate devices are displayed around the icon 301 in the collaborative connection interface 13. The first capability badge may be a capability badge 503 corresponding to the audio output function. The first input operation for selecting the audio output function acts on the capability badge 503.

[0370] In some embodiments, before receiving the first input operation for selecting the first capability, the method further includes: receiving a ninth input operation acting on the first icon; and in response to the ninth input operation, displaying capability badges corresponding to the at least two capabilities in the first user interface. In one implementation, in the first user interface, capability badges corresponding to the collaborative capabilities supported by the second electronic device are displayed in an area around the first icon.

[0371] Exemplary, reference Fig.17A and Fig. 17B As described above, after receiving the ninth input operation (such as a click operation) acting on icon 301, electronic device 100 displays capability badges corresponding to all collaborative capabilities supported by all detected candidate devices around icon 301.

[0372] In some embodiments, the method further includes: in response to the first input operation, additionally displaying a first capability badge on the first icon. For example, the first capability badge is a capability badge 503 corresponding to the audio output function.

[0373] Exemplary, reference 17A to 17D As described above, after the user selects capability badge 503 , that is, after electronic device 100 receives the first input operation acting on capability badge 503 , capability badge 503 is additionally displayed on icon 301 .

[0374] In some embodiments, the method further includes: in response to the first input operation, stopping displaying the icons of the candidate devices that are not capable of cooperating with the first capability in the first user interface.

[0375] Exemplary, reference Fig. 17B and Fig.17EAs described in the related description, after the user selects the capability badge 503 corresponding to the audio output function, the electronic device 100 stops displaying the icons of candidate devices that cannot cooperate with the audio output function in the collaborative connection interface 13.

[0376] In some embodiments, the method also includes: when a collaborative connection supporting the first capability is successfully established with the second electronic device, the second icon switches from a non-collaborated state to a collaborative state, and the second icon is additionally displayed with a first capability badge corresponding to the first capability; when a collaborative connection supporting the first capability fails to be established with the second electronic device, the second icon remains in a non-collaborated state.

[0377] Exemplary, reference FIG. 6A to FIG. 6D , FIG. 10A to FIG. 10F , when the collaborative connection with the tablet computer supporting the camera is successfully established, the icon 302 switches from the uncollaborated state to the coordinated state, and the icon 302 is additionally displayed with the capability badge 501 corresponding to the camera. FIG. 18A to FIG. 18B , 19A to 19D As described above, when a collaborative connection supporting the audio output function is successfully established with the tablet computer, the icon 302 is switched from a non-collaborative state to a collaborative state, and the icon 302 is additionally displayed with a capability badge 503 corresponding to the audio output function.

[0378] In some embodiments, before receiving the second input operation, the first icon is displayed in the first preset area, and the icon of the at least one candidate device is displayed in the second preset area; the uncoordinated state of the second icon is presented as being displayed in the second preset area in the first state; the coordinated state of the second icon is presented as being adsorbed on the first icon in the second state and displayed in the first preset area, or the coordinated state of the second icon is presented as being displayed in the second preset area in the second state. For example, the first state and the second state refer to different icon colors.

[0379] For example, referring to the related description of the above embodiments, Figure 3C As shown, before the collaborative connection is performed, the icon 301 is displayed in the first preset area (such as the preset area 1 mentioned above), and the icon of the candidate device is displayed in the second preset area (such as the preset area 2 mentioned above); Figure 3C As shown, the uncoordinated state of icon 302 is presented as being displayed in the preset area 2 in a first state (eg, a light-colored icon); Fig.6D , Fig. 10D , Fig.18B and Fig.19D As shown, the coordinated state of icon 302 is presented as being adsorbed on icon 301 in a second state (eg, a dark icon) and displayed in the preset area 1; or Fig.10F and Fig.19CAs shown, the coordinated state of icon 302 is presented as being displayed in the second state (eg, a dark icon) in the preset area 2. The embodiment of the present application does not specifically limit the coordinated state, the uncoordinated state, the first state, and the second state.

[0380] In some embodiments, after the first electronic device executes the step of "establishing a collaborative connection with the second electronic device that supports the first capability and the second capability", when a collaborative connection supporting the first capability and the second capability is successfully established with the second electronic device, the second icon switches from a non-collaborated state to a collaborative state, and the second icon is additionally displayed with the first capability superscript and the second capability superscript; when a collaborative connection supporting the first capability is successfully established with the second electronic device, and the collaborative connection does not support the second capability, the second icon switches from a non-collaborated state to a collaborative state, and the second icon is additionally displayed with the first capability superscript, and the second capability superscript is not additionally displayed.

[0381] Exemplary, reference FIG. 13A to FIG. 13J , the electronic device 100 establishes a collaborative connection with the tablet computer that supports camera and audio output functions; Fig.13D As shown, when a collaborative connection supporting camera and audio output functions is successfully established with the tablet computer, icon 302 switches from a non-collaborative state to a collaborative state, and icon 302 is additionally displayed with a capability subscript 501 corresponding to the camera and a capability subscript 503 corresponding to the audio output function; Figure 13G As shown, when a collaborative connection supporting a camera is successfully established with a tablet computer, and the collaborative connection does not support the audio output function, the icon 302 switches from a non-collaborative state to a collaborative state, and the icon 302 is additionally displayed with a capability badge 501, and is not additionally displayed with a capability badge 503; Fig.13J As shown, when the collaborative connection with the tablet computer is not successfully established, the icon 302 remains in the un-collaborated state.

[0382] The present application also provides a device collaboration method, applied to a first electronic device, the method comprising: displaying a first user interface, the first user interface including a first icon of the first electronic device and an icon of at least one detected candidate device, the icon of the at least one candidate device including a second icon of a second electronic device; the second electronic device supports at least two collaborative capabilities, the at least two collaborative capabilities including the first capability; receiving an eleventh input operation; in response to the eleventh input operation, establishing a collaborative connection supporting the first capability with the second electronic device based on the collaborative state of the first application most recently running in the foreground and / or the second electronic device.

[0383] Among them, the first electronic device may be the electronic device 100 described in the aforementioned embodiment, and the second electronic device may be the candidate device 200 (for example, a tablet computer) described in the aforementioned embodiment; the first user interface may be the collaborative connection interface 13 described in the aforementioned embodiment, the first icon may be the icon 301 in the collaborative connection interface 13, and the second icon may be the icon 302 in the collaborative connection interface 13.

[0384] The first capability may be any one of the above-mentioned capabilities that can be coordinated with the tablet computer.

[0385] Exemplary, reference FIG. 25A to FIG. 25D Related descriptions, such as Fig.25B As shown, the eleventh input operation may include an input operation of dragging icon 302 toward icon 301 .

[0386] In some embodiments, the collaborative state of the second electronic device includes one or more of the following: the number of collaborative connections of each capability that the first electronic device and the second electronic device have collaboratively connected, the capability of the first electronic device and the second electronic device that was most recently collaboratively connected, and the priority of each collaborative capability of the second electronic device. The embodiments of the present application do not specifically limit the collaborative state of the second electronic device.

[0387] In some embodiments, the establishing of a collaborative connection to the first capability of the second electronic device based on the collaborative state of the first application and / or the second electronic device most recently running in the foreground includes: when the collaborative capabilities of the second electronic device include the first capability required by the first application, establishing a collaborative connection to the first capability of the second electronic device.

[0388] Exemplary, reference FIG. 25A to FIG. 25D According to the relevant description, the first application is a music APP, and the collaborative capabilities of the tablet computer include the audio output capability required by the music APP; the electronic device 100 and the tablet computer establish a collaborative connection that supports the audio output capability.

[0389] In some embodiments, the establishing of a collaborative connection with the first capability of the second electronic device based on the collaborative state of the first application and / or the second electronic device most recently running in the foreground includes: establishing a collaborative connection with the first capability with the greatest number of collaborative connections among the capabilities that have been collaboratively connected with the second electronic device; or, establishing a collaborative connection with the first capability with which the second electronic device was most recently collaboratively connected; or, establishing a collaborative connection with the first capability with the highest priority among the collaborative capabilities of the second electronic device.

[0390] The various implementation modes of the present application can be combined arbitrarily to achieve different technical effects.

[0391] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, computer, server or data center to another website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) mode. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state disk (SSD)), etc.

[0392] Those skilled in the art can understand that to implement all or part of the processes in the above-mentioned embodiments, the processes can be completed by computer programs to instruct related hardware, and the programs can be stored in computer-readable storage media. When the programs are executed, they can include the processes of the above-mentioned method embodiments. The aforementioned storage media include: ROM or random access memory RAM, magnetic disk or optical disk and other media that can store program codes.

[0393] In short, the above is only an embodiment of the technical solution of this application, and is not intended to limit the protection scope of this application. Any modification, equivalent replacement, improvement, etc. made according to the disclosure of this application shall be included in the protection scope of this application.

Claims

1. A device collaboration method, characterized in that: include: The first electronic device displays a first user interface; the first user interface includes a first icon of the first electronic device, a second icon of the second electronic device, and a screen projection icon corresponding to the first electronic device, and the screen projection icon is displayed around the first icon; The first electronic device receives a first user operation of dragging the screen projection icon to the second icon; In response to the first user operation, the first electronic device establishes a collaborative connection for screen projection with the second electronic device, and the screen projection icon is displayed around the second icon.

2. The method according to claim 1, characterized in that The method further comprises: After establishing a collaborative connection for screen projection with the second electronic device, the first electronic device instructs the second electronic device to display the projection screen of the first electronic device.

3. The method according to claim 1 or 2, characterized in that: After establishing a collaborative connection for screen projection with the second electronic device, the screen projection icon is not displayed around the first icon.

4. The method according to any one of claims 1 to 3, characterized in that: Before the first electronic device displays the first user interface, the method further includes: The first electronic device displays a second user interface; the second user interface includes the first icon of the first electronic device, the third icon of the third electronic device, and the screen projection icon corresponding to the first electronic device, and the screen projection icon is displayed around the first icon; After receiving a second user operation of dragging the screen projection icon to the third icon, a prompt message is displayed, wherein the prompt message is used to prompt that the collaborative connection for the screen projection with the third electronic device has failed to be established.

5. The method according to claim 4, characterized in that When receiving the second user operation, the third electronic device has established a collaborative connection for screen projection with other electronic devices.

6. The method according to claim 4, characterized in that The method further comprises: After the collaborative connection for the screen projection with the third electronic device fails to be established, the screen projection icon is displayed again around the first icon.

7. The method according to any one of claims 1 to 6, characterized in that: The first user interface further includes a fourth icon of a fourth electronic device and an audio output icon corresponding to the first electronic device, and the audio output icon is displayed around the first icon; The method further comprises: receiving a third user operation of dragging the audio output icon to the fourth icon; In response to the third user operation, a collaborative connection for audio output is established with the fourth electronic device, and the audio output icon is displayed around the fourth icon.

8. The method according to claim 7, characterized in that The method further comprises: After establishing a collaborative connection for audio output with the second electronic device, the second electronic device is instructed to play the audio from the first electronic device.

9. The method according to any one of claims 1 to 8, characterized in that: Before the first user interface displays the screen projection icon corresponding to the first electronic device, the method further includes: receiving a fourth user operation acting on the first icon; In response to the fourth user operation, the screen projection icon is displayed around the first icon of the first electronic device.

10. The method according to any one of claims 1 to 9, characterized in that: The first user interface further includes a fifth icon of a fifth electronic device and at least one other icon corresponding to the first electronic device, wherein the at least one other icon is displayed around the first icon; The at least one other icon includes some or all of the following: a camera icon, a microphone icon, a speaker icon, a display screen icon, a printer icon, a payment icon, an image processing icon, a WIFI icon, a camera icon, an audio output icon, and an audio input icon; The method further comprises: receiving a fifth user operation of dragging a sixth icon to the fifth icon, wherein the sixth icon is any one of the at least one other icon; In response to the fifth user operation, the first device establishes a collaborative connection with the fifth electronic device, and the sixth icon is displayed around the fifth icon, and the collaborative connection is used to support the collaborative capability associated with the sixth icon.

11. The method according to any one of claims 1 to 10, characterized in that: The first electronic device displays a first user interface, including: In response to a sixth user operation, the first electronic device displays the first user interface; the sixth operation is used to operate the first control on the control center interface, or the switching control in the application interface of the first application.

12. The method according to any one of claims 1 to 11, characterized in that: The first electronic device and the second electronic device are electronic devices logged into the same account, or the login account of the first electronic device and the login account of the second electronic device are in a preset relationship.

13. The method according to any one of claims 1 to 11, characterized in that The first electronic device and the second electronic device communicate via a short-range wireless communication technology, and the short-range wireless communication technology includes any one of the following: Bluetooth, Wireless Fidelity WiFi, Ultra-Wideband UWB, Near Field Communication NFC, ZigBee.

14. An electronic device, characterized in that: The electronic device comprises a memory and a processor, wherein the memory and the processor are electrically coupled, the memory is used to store program instructions, and the processor is configured to call all or part of the program instructions stored in the memory so that the electronic device executes the method according to any one of claims 1 to 13.

15. A computer storage medium, characterized in that: The method comprises computer instructions, which, when executed on an electronic device, cause the electronic device to execute the method according to any one of claims 1 to 13.

16. A computer program product, characterized in that When the computer program product is run on a computer, the computer is caused to perform the method according to any one of claims 1 to 13.

Images