Device collaboration method and apparatus, chip, and computer readable storage medium

Abstract

The present application provides a device collaboration method and apparatus, a chip, and a computer readable storage medium. The method comprises: in response to a first user operation, sending a detection request, wherein the first user operation is used for enabling a device collaboration function; on the basis of at least one received detection response for the detection request, determining at least one second electronic device, wherein a first electronic device and the at least one second electronic device belong to a same communication group; and displaying a first control representing the first electronic device and a second control representing the second electronic device. When the first electronic device enables the device collaboration function, the first electronic device can automatically find at least one second electronic device in the same communication group, for example, a second electronic device corresponding to a different account and a second electronic device corresponding to a same account, thereby expanding the automatic discovery range of the device, and enhancing the automatic discovery capability of the first electronic device. The present application solves the problem in the prior art of impacting the user experience as a result of the discovery range of the solution of automatically finding a device being limited.

Description

A device collaboration method, apparatus, chip, and computer-readable storage medium

[0001] This application claims priority to Chinese Patent Application No. 202410231464.7, filed on February 29, 2024, entitled "A Device Collaboration Method, Apparatus, Chip and Computer-Readable Storage Medium", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of terminals, and more particularly to a device coordination method, apparatus, chip, and computer-readable storage medium. Background Technology

[0003] With the rapid development of technology, smart devices have become an important part of our daily lives. Examples of smart devices include speakers, smart screens, and headphones. Among related technologies, the HarmonyOS distributed operating system, based on distributed soft bus technology, can automatically discover smart devices under the same account, allowing users to select the appropriate smart device from the automatically discovered list for functional flow based on their needs.

[0004] However, due to account privacy restrictions, automatic discovery of smart devices can only be achieved under the same account, which limits the scope of automatic discovery of smart devices and thus affects the user experience.

[0005] Summary of the Invention

[0006] This application provides a device collaboration method, apparatus, chip, and computer-readable storage medium, in which a first electronic device can automatically discover at least one second electronic device in the same communication group, thereby expanding the scope of automatic discovery of smart devices and improving user experience.

[0007] In a first aspect, a device collaboration method is provided, comprising: sending a probe request in response to a first user operation, wherein the first user operation is used to initiate a device collaboration function; receiving at least one probe response to the probe request; determining at least one second electronic device based on the at least one probe response, wherein the first electronic device and the at least one second electronic device belong to the same communication group, and the accounts corresponding to some or all of the at least one second electronic device are different from the accounts corresponding to the first electronic device, the probe response being used to indicate that the first electronic device and the second electronic device belong to the same communication group; and displaying a first control and at least one second control, wherein the first control represents the first electronic device, and the second control represents the second electronic device. Different second controls represent different second electronic devices.

[0008] It should be understood that the device collaboration method provided in the first aspect can be applied to electronic devices, which are called the first electronic devices. Specifically, the first electronic device can be a terminal device with device collaboration function, such as a mobile phone, tablet, computer, etc.

[0009] In this embodiment of the application, after the first electronic device responds to the first user's operation and starts the device collaboration function, it can automatically discover at least one second electronic device corresponding to the same communication group (family group), such as the second electronic device corresponding to the same account and the second electronic device corresponding to different accounts, thus expanding the scope of automatically discovered devices. Subsequently, the user can select the corresponding device from the automatically discovered devices for collaborative work according to their needs, which improves the range of devices that need to be selected when task collaboration or function flow, and improves the user experience.

[0010] The second electronic device can be a smart device, such as a mobile phone, glasses, tablet, personal computer (PC), smart screen, watch, speaker, in-vehicle system, or headphones. The first electronic device and at least one second electronic device are on the same network, such as the same local area network or the same wide area network. When the first electronic device and at least one second electronic device are on the same network, they can communicate via Bluetooth or Wi-Fi.

[0011] In one feasible implementation, a first electronic device can broadcast a probe request to detect a second electronic device that is on the same network and in the same communication group as the first electronic device. The device receiving the probe request can determine whether it belongs to the same communication group as the first electronic device based on its stored group information and the information carried in the probe request. If it determines that it belongs to the same communication group as the first electronic device, it sends a probe response to the first electronic device. The first electronic device can then identify the second electronic device based on this probe response. In this way, the first electronic device can self-discover at least one second electronic device based on at least one probe response, achieving self-discovery of devices within the same communication group and expanding the scope of self-discovered devices.

[0012] In this context, at least one second electronic device can be all or some of the devices in the communication group to which the first electronic device belongs, excluding the first electronic device. At least one second electronic device corresponds to an account that does not contain the account corresponding to the first electronic device, meaning at least one second electronic device is a device with a different account; at least one second electronic device corresponds to an account that contains the account corresponding to the first electronic device, meaning at least one second electronic device contains both devices with the same account and devices with different accounts. Specifically, a device with the same account refers to a second electronic device whose account is the same as the account corresponding to the first electronic device; a device with a different account refers to a second electronic device whose account is different from the account corresponding to the first electronic device.

[0013] In one feasible implementation, both the first control and the second control can be presented as icons. For example, the first control can be an icon representing the first electronic device, and the second control can be an icon representing the second electronic device. Users can drag and drop icons to select the corresponding device from the first electronic device and at least one second electronic device for task collaboration, which increases the range of devices that can be selected when task collaboration or function flow, and further improves the user experience.

[0014] In one feasible implementation, the first control and at least one second control can be obtained in at least one of the following ways:

[0015] Method 1: A first electronic device sends a control acquisition request to the server to obtain a first control and at least one second control. The first electronic device can receive the first control and at least one second control sent by the server based on the control acquisition request. The first control and at least one second control can be generated by the server; alternatively, they can be sent to the server by other devices.

[0016] Method 2: The first electronic device may send an acquisition request to the server, wherein the acquisition request is used to acquire first device information and second device information of at least one second electronic device; the first electronic device may receive the first device information and the second device information of at least one second electronic device from the server. The first device information represents the state and / or attributes of the first electronic device; the second device information represents the state and / or attributes of the second electronic device. The acquisition request carries identification information of the first electronic device and identification information of at least one second electronic device.

[0017] Method 3: The first electronic device can determine the control corresponding to the identification information of the first electronic device from a plurality of pre-generated controls to obtain the first control, and determine the control corresponding to the identification information of the second electronic device from a plurality of pre-generated controls to obtain the second control.

[0018] Based on the above scheme, the first electronic device can flexibly choose different acquisition methods to acquire the first control and at least one second control, thereby improving the flexibility of acquiring the first control and at least one second control.

[0019] In one feasible implementation, the probe request carries relevant information about the first electronic device. This information may be at least one of the following: the identification information of the first electronic device, the account corresponding to the first electronic device, and the group identification information corresponding to the first electronic device. Thus, the device receiving the probe request can determine whether it is in the same communication group as the first electronic device based on the relevant information. If it is determined that it is in the same communication group as the first electronic device, it sends a probe response to the first electronic device, so that the first electronic device can automatically discover other devices (second electronic devices) in the same communication group based on the probe response.

[0020] In one feasible implementation, the probe response is sent by the second electronic device after determining that it belongs to the same communication group as the first electronic device based on the probe request and the stored group information corresponding to the second electronic device.

[0021] The group information corresponding to the second electronic device comes from the server. The server maintains group information for multiple communication groups. For each communication group, the server can send group information to multiple devices in the communication group (also referred to as multiple devices corresponding to the communication group), so that after receiving the group information, the multiple devices can realize self-discovery among themselves.

[0022] In one feasible implementation, the probe response carries group identification information of the communication group and identification information of the second electronic device.

[0023] In one feasible implementation, the group information includes at least one of group identification information, group member accounts, and identification information of the electronic devices corresponding to the group member accounts.

[0024] In one feasible implementation, after the first electronic device displays the first control and at least one second control, it may also perform the following steps: in response to a second user operation, it sends a processing request to the server, wherein the processing request is used to establish a device collaboration link between the collaborating device and the device to be collaborated with, the collaborating device and the device to be collaborated with are electronic devices in the first electronic device and at least one second electronic device, and the second user operation is used to associate the collaborating device and the device to be collaborated with.

[0025] In this system, the first electronic device can respond to a second user operation by determining, from the first electronic device and at least one second electronic device, a device to be coordinated and a coordinating device, and generating a processing request to establish a device coordination link between the coordinating device and the device to be coordinated. The first electronic device can act as a device to be coordinated, a coordinating device, or a device solely for forwarding the processing request (i.e., the first electronic device is neither a device to be coordinated nor a coordinating device, but only a device for triggering the establishment of a device coordination link). The second user operation can be a user dragging a control to a designated area corresponding to another control.

[0026] Based on the above scheme, a device collaboration link is established between devices in the communication group, so that devices can coordinate tasks or transfer functions through the device collaboration link, which improves the collaborative work capability and task execution efficiency, better serves users and application scenarios, and further improves the user experience.

[0027] The server receives a processing request from the first electronic device, wherein the processing request is used to establish a device collaboration link between the collaborating device and the device to be collaborated with; the server may send control instructions to the device to be collaborated with based on the processing request, wherein the control instructions are used to control the device to be collaborated with to establish a device collaboration link.

[0028] In one feasible implementation, the first electronic device, acting as a cooperating device, can perform the following operations: receiving a verification request from a device to be cooperated with, wherein the verification request is used to determine whether the device to be cooperated with is a legitimate device, the verification request being sent by the device to be cooperated with based on a control instruction from a server, and the control instruction being sent by the server based on a processing request; and, if the device to be cooperated with is determined to be a legitimate device based on the verification request, sending a verification response to the device to be cooperated with, the verification response being used to determine whether the first electronic device is a legitimate device.

[0029] In the case where the device to be collaborated with is determined to be a legitimate device based on the verification request, a verification response is sent to the device to be collaborated with. This can be achieved in the following way: the verification request is parsed to obtain the identification information and first encrypted information of the device to be collaborated with. The first encrypted information is obtained by encrypting the identification information of the device to be collaborated with based on the group identification key and the user identification key corresponding to the device to be collaborated with. The identification information of the device to be collaborated with is then encrypted based on the group identification key and the user identification key corresponding to the first electronic device to obtain second encrypted information. If the first encrypted information and the second encrypted information match, the device to be collaborated with is determined to be a legitimate device. A verification response is sent to the device to be collaborated with. The verification response carries the identification information of the first electronic device and third encrypted information. The third encrypted information is obtained by encrypting the identification information of the first electronic device based on the group identification key and the user identification key corresponding to the first electronic device.

[0030] Based on the above scheme, when the device to be collaborated with determines that the first electronic device is a legitimate device, a device collaboration link is established between the device and the first electronic device so that task collaboration or function transfer between the first electronic device and the device to be collaborated with can be realized through the device collaboration link, thereby improving the user experience.

[0031] In one feasible implementation, the first electronic device, as the device to be coordinated, can perform the following operations: receiving a control command from the server, wherein the control command is used to control the first electronic device to establish a device coordination link, and the control command is sent by the server based on a processing request; based on the control command, sending a verification request to the coordinating device, wherein the verification request is used to determine whether the first electronic device is a legitimate device; and establishing a device coordination link if the coordinating device is determined to be a legitimate device based on the verification response from the coordinating device, wherein the verification response is sent by the coordinating device if the first electronic device is determined to be a legitimate device.

[0032] In this context, when the collaborative device is determined to be a legitimate device based on the verification response from the collaborative device, the establishment of a device collaboration link can be achieved as follows: The verification response is parsed to obtain the collaborative device's identification information and third encrypted information. The third encrypted information is obtained by encrypting the collaborative device's identification information based on the collaborative device's corresponding group identification key and user identification key. The collaborative device's identification information is then encrypted based on the first electronic device's corresponding group identification key and user identification key to obtain fourth encrypted information. If the third and fourth encrypted information match, the collaborative device is determined to be a legitimate device; and the device collaboration link is established.

[0033] Based on the above scheme, when the first electronic device determines that the collaborating device is a legitimate device, a device collaboration link is established between the first electronic device and the collaborating device so that task collaboration or function transfer between the first electronic device and the collaborating device can be realized through the device collaboration link, thereby improving the user experience.

[0034] Secondly, a device collaboration method is provided, which can be executed by a server, by a component of the server, or by a logic module or software that can implement or partially implement server functions.

[0035] The method includes: receiving an acquisition request from a first electronic device, wherein the acquisition request is used to acquire first device information of the first electronic device and second device information of at least one second electronic device, wherein the first device information represents the state and / or attributes of the first electronic device, the second device information represents the state and / or attributes of the second electronic device, the first electronic device and at least one second electronic device belong to the same communication group, and the account corresponding to some or all of the at least one second electronic device is different from the account corresponding to the first electronic device; sending the first device information and the second device information of at least one second electronic device to the first electronic device, wherein the first device information is used to display a first control representing the first electronic device, and the second device information is used to display a second control representing the second electronic device.

[0036] In one feasible implementation, the first device information includes at least one of the following: model information, configuration information, status information, size information, and an image of the first electronic device. The second device information may include at least one of the following: model information, configuration information, status information, size information, and an image of the second electronic device.

[0037] In one feasible implementation, the method further includes: receiving a processing request from a first electronic device, wherein the processing request is used to establish a device collaboration link between the collaborating device and the device to be collaborated with; and sending a control command to the device to be collaborated with based on the processing request, wherein the control command is used to control the device to be collaborated with to establish the device collaboration link.

[0038] In one feasible implementation, the method further includes: sending group information of the communication group to multiple electronic devices in the communication group, wherein the group information is used by the electronic devices to determine whether they are in the same communication group as other electronic devices, and the multiple electronic devices include a first electronic device and at least one second electronic device.

[0039] In one feasible implementation, the group information includes at least one of group identification information, group member accounts, and identification information of the electronic devices corresponding to the group member accounts.

[0040] The beneficial effects of each implementation method in the second aspect can be found in the description of the first aspect, and will not be repeated here.

[0041] Thirdly, a device collaboration method is provided, which can be executed by a second electronic device, or by a component of the second electronic device (such as a processor, chip, or chip system), or by a logic module or software capable of implementing all or part of the functions of the second electronic device.

[0042] The method includes: receiving a probe request from a first electronic device; and, if it is determined from the probe request that the first electronic device belongs to the same communication group, sending a probe response to the first electronic device, wherein the probe response is used to indicate that the first electronic device and the second electronic device belong to the same communication group, and at least some of the electronic devices in the communication group have different accounts.

[0043] The probe request carries information about the first electronic device, such as at least one of the identification information of the first electronic device, the account corresponding to the first electronic device, and the group identification information corresponding to the first electronic device.

[0044] In one feasible implementation, the method includes: determining whether a first electronic device and a second electronic device belong to the same communication group based on a probe request and stored group information corresponding to a second electronic device; and if the first electronic device and the second electronic device belong to the same communication group, sending a probe response to the first electronic device.

[0045] In one feasible implementation, the probe response carries group identification information of the communication group and identification information of the second electronic device.

[0046] In one feasible implementation, group information can be obtained by receiving group information from a server, wherein the group information includes at least one of group identification information, group member accounts, and identification information of electronic devices corresponding to group member accounts.

[0047] In one feasible implementation, the second electronic device can act as a cooperating device and can perform the following operations: receiving a verification request from a device to be cooperated with, wherein the verification request is used to determine whether the device to be cooperated with is a legitimate device, and the verification request is sent by the device to be cooperated with based on a control command from a server; if the device to be cooperated with is determined to be a legitimate device based on the verification request, sending a verification response to the device to be cooperated with, wherein the verification response is used to determine whether the second electronic device is a legitimate device.

[0048] In the case where the device to be collaborated with is determined to be a legitimate device based on the verification request, a verification response is sent to the device to be collaborated with. This can be achieved in the following way: The verification request is parsed to obtain the identification information and first encrypted information of the device to be collaborated with. The first encrypted information is obtained by encrypting the identification information of the device to be collaborated with based on the group identification key and the user identification key corresponding to the device to be collaborated with. The identification information of the device to be collaborated with is then encrypted based on the group identification key and the user identification key corresponding to the second electronic device to obtain second encrypted information. If the first encrypted information and the second encrypted information match, the device to be collaborated with is determined to be a legitimate device. A verification response is sent to the device to be collaborated with. The verification response carries the identification information of the second electronic device and third encrypted information. The third encrypted information is obtained by encrypting the identification information of the second electronic device based on the group identification key and the user identification key corresponding to the second electronic device.

[0049] Based on the above scheme, when the second electronic device acts as a collaborating device, the device to be collaborated with can be the first electronic device or at least one other second electronic device besides the first electronic device. When the device to be collaborated determines that the second electronic device is a legitimate device, a device collaboration link can be established between the device to be collaborated with the second electronic device. Subsequently, through the device collaboration link, the second electronic device and the device to be collaborated with can perform task collaboration or function transfer, thereby improving the user experience.

[0050] In one feasible implementation, the second electronic device can act as a device to be coordinated and can perform the following operations: receiving control instructions from the server, wherein the control instructions are used to control the establishment of a device coordination link between the second electronic device and the coordinating device; sending a verification request to the coordinating device based on the control instructions, wherein the verification request is used to determine whether the second electronic device is a legitimate device; and establishing a device coordination link if the coordinating device is determined to be a legitimate device based on the verification response from the coordinating device, wherein the verification response is sent by the coordinating device after determining that the second electronic device is a legitimate device.

[0051] In this context, when the collaborative device is determined to be a legitimate device based on the verification response from the collaborative device, the establishment of a device collaboration link can be achieved as follows: The verification response is parsed to obtain the collaborative device's identification information and third encrypted information. The third encrypted information is obtained by encrypting the collaborative device's identification information based on the collaborative device's corresponding group identification key and user identification key. The collaborative device's identification information is then encrypted based on the second electronic device's corresponding group identification key and user identification key to obtain fourth encrypted information. If the third and fourth encrypted information match, the collaborative device is determined to be a legitimate device; and the device collaboration link is established.

[0052] Based on the above scheme, when the second electronic device is the device to be coordinated, the coordinating device can be the first electronic device or at least one other second electronic device besides the first electronic device. When the second electronic device determines that the coordinating device is a legitimate device, it can establish a device coordination link with the coordinating device. Subsequently, through the device coordination link, the second electronic device and the coordinating device can perform task coordination or function transfer, thereby improving the user experience.

[0053] Fourthly, a device collaboration system is provided, comprising a first electronic device, at least one second electronic device, and a server. The server establishes communication connections with both the first electronic device and the at least one second electronic device. The first electronic device and the at least one second electronic device belong to the same communication group, wherein:

[0054] The server is used to send group information of a communication group to a first electronic device and at least one second electronic device; the first electronic device is used to send a probe request in response to a first user operation, the first user operation being used to activate a device collaboration function; the second electronic device is used to receive the probe request from the first electronic device; if, based on the probe request and the group information from the server, it is determined that it belongs to the same communication group as the first electronic device, the second electronic device sends a probe response to the first electronic device, wherein the probe response is used to indicate that the first electronic device and the second electronic device belong to the same communication group; the first electronic device is also used to determine at least one second electronic device based on at least one probe response, wherein some or all of the accounts corresponding to the at least one second electronic device are different from the accounts corresponding to the first electronic device;

[0055] Fifthly, a device coordination apparatus is provided, comprising a module or unit for performing the method of the first aspect or any possible implementation thereof, a module or unit for performing the method of the second aspect or any possible implementation thereof, or a module or unit for performing the method of the third aspect or any possible implementation thereof.

[0056] In a sixth aspect, a device coordination apparatus is provided, comprising an execution method including a processor coupled to a memory for storing computer programs or instructions, the processor executing the computer programs or instructions stored in the memory to implement the method of the first aspect or any possible implementation thereof, or to implement the method of the second aspect or any possible implementation thereof, or to implement the method of the third aspect or any possible implementation thereof.

[0057] In one possible implementation, the device also includes a memory coupled to the processor.

[0058] In one possible implementation, there are one or more processors, and / or one or more memories.

[0059] In one possible implementation, the memory can be integrated with the processor, or the memory can be set up separately from the processor.

[0060] In one possible implementation, the device also includes a communication interface, to which the processor is coupled.

[0061] In one implementation, the device is a network device. For example, the communication interface may be a transceiver, or an input / output interface.

[0062] In another implementation, the device is a chip within a device collaboration device. For example, the communication interface could be an input / output interface.

[0063] A seventh aspect provides an electronic device including a memory, one or more processors, and one or more programs; wherein the one or more programs are stored in the memory; and when the one or more processors execute the one or more programs, the electronic device causes the electronic device to implement the method of the first aspect or any possible implementation of the first aspect, or to implement the method of the second aspect or any possible implementation of the second aspect, or to implement the method of the third aspect or any possible implementation of the third aspect.

[0064] Eighthly, a processor is provided, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive signals through the input circuit and transmit signals through the output circuit, causing the processor to execute the method of any of the above aspects or any possible implementation thereof.

[0065] In specific implementation, the processor can be a chip, the input circuit can be input pins, the output circuit can be output pins, and the processing circuit can be transistors, gate circuits, flip-flops, and various logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit can be, for example, but not limited to, output to and transmitted by a transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as both the input circuit and the output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.

[0066] Ninthly, a chip is provided, including a processor for calling and running a computer program from a memory, causing a device equipped with the chip to perform the method in any of the above aspects or any possible implementation of any of the above aspects.

[0067] In a tenth aspect, a computer-readable storage medium is provided that stores a computer program (also referred to as code or instructions) that, when run on a computer, causes the computer to perform the methods of any of the above aspects or any possible implementations of any of the above aspects.

[0068] Eleventhly, a computer program product is provided, comprising: a computer program (also referred to as code or instructions) that, when run, causes a computer to perform the methods of any of the above aspects or any possible implementations thereof. Attached Figure Description

[0069] Figure 1 is a schematic diagram of the structure of an electronic device provided in an embodiment of this application;

[0070] Figure 2 is a software structure block diagram of an electronic device 100 provided in an embodiment of this application;

[0071] Figure 3 is a schematic diagram of the super terminal interface of a mobile phone in the related technology provided in the embodiments of this application;

[0072] Figure 4 is a schematic diagram of mutual authentication between a mobile phone and a smart screen in the related technology provided in the embodiments of this application;

[0073] Figure 5 is a schematic diagram of the main interface of the mobile phone in the device collaboration method provided in the embodiment of this application;

[0074] Figure 6 is a schematic diagram of the control center interface of a mobile phone in the device collaboration method provided in the embodiments of this application;

[0075] Figure 7 is a schematic diagram of a super terminal interface in the device collaboration method provided in the embodiments of this application;

[0076] Figure 8 is a schematic diagram of the group information of the communication group sent by the server in the device collaboration method provided in the embodiment of this application;

[0077] Figure 9 is a schematic diagram of the structure of device p1 and device p2 in the device collaboration method provided in the embodiment of this application;

[0078] Figure 10 is a schematic diagram of the UI interface of a mobile phone in the device collaboration method provided in the embodiments of this application;

[0079] Figure 11 is a schematic diagram of the operation interface for adding a member to a communication group (family group) in the device collaboration method provided in the embodiment of this application;

[0080] Figure 12 is a schematic diagram of the process of adding a member to a communication group (family group) in the device collaboration method provided in the embodiment of this application;

[0081] Figure 13 is a schematic diagram of a task collaboration scenario in the device collaboration method provided in the embodiments of this application;

[0082] Figure 14 is a schematic diagram of another task collaboration scenario in the device collaboration method provided in the embodiments of this application;

[0083] Figure 15 is a flowchart illustrating a device collaboration method provided in an embodiment of this application;

[0084] Figure 16 is a flowchart illustrating another device collaboration method provided in an embodiment of this application;

[0085] Figure 17 is a schematic diagram of another super terminal interface in the device collaboration method provided in the embodiments of this application;

[0086] Figure 18 is a flowchart illustrating another device collaboration method provided in an embodiment of this application;

[0087] Figure 19 is a schematic diagram of another super terminal interface in the device collaboration method provided in the embodiments of this application;

[0088] Figure 20 is a flowchart illustrating a device collaboration method according to another embodiment of this application;

[0089] Figure 21 is a schematic diagram of a super terminal interface in a device collaboration method provided in another embodiment of this application;

[0090] Figure 22 is a schematic diagram of the structure of a device collaboration device provided in an embodiment of this application;

[0091] Figure 23 is a schematic diagram of another device collaboration device provided in an embodiment of this application;

[0092] Figure 24 is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0093] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0094] In the description of the embodiments of this application, unless otherwise stated, " / " means "or"; for example, A / B can mean A or B; "and / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist; for example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, in the description of the embodiments of this application, "multiple" refers to two or more.

[0095] Hereinafter, the terms "first," "second," and "third" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first," "second," or "third" may explicitly or implicitly include one or more of that feature.

[0096] This application provides an electronic device for executing the device collaboration method provided in this application. In some embodiments of this application, the electronic device may be a mobile phone, tablet computer, wearable device, in-vehicle device, augmented reality (AR) / virtual reality (VR) device, laptop computer, ultra-mobile personal computer (UMPC), netbook, personal digital assistant (PDA), etc., or may be other devices or apparatuses capable of device collaboration. This application does not limit the specific type of electronic device.

[0097] For example, FIG1 is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application.

[0098] As shown in Figure 1, 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, a headphone jack 170D, a sensor module 180, buttons 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, a barometric pressure sensor 180C, a magnetic sensor 180D, an accelerometer sensor 180E, a distance sensor 180F, a proximity 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.

[0099] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0100] Processor 110 may include one or more processing units, such as: application processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, memory, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

[0101] The controller can be the nerve center and command center of the electronic device 100. The controller can generate operation control signals according to the instruction opcode and timing signals to complete the control of fetching and executing instructions.

[0102] The processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory can store instructions or data that the processor 110 has just used or that are used repeatedly. If the processor 110 needs to use the instruction or data again, it can retrieve it directly from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

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

[0104] The processor 110 and the display screen 194 communicate via a DSI interface to realize the display function of the electronic device 100.

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

[0106] Antennas 1 and 2 are used to transmit and receive electromagnetic wave signals. The structures of antennas 1 and 2 in Figure 1 are merely one example. Each antenna in the electronic device 100 can be used to cover one or more communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with a tuning switch.

[0107] Electronic device 100 implements display functions through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. Processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.

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

[0109] The external storage interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 through the external storage interface 120 to perform data storage functions. For example, music, video, and other files can be saved on the external memory card.

[0110] Pressure sensor 180A is used to sense pressure signals and convert them into electrical signals. In some embodiments, pressure sensor 180A can be disposed on display screen 194. There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, and capacitive pressure sensors. A capacitive pressure sensor may include at least two parallel plates with conductive material. When force is applied to pressure sensor 180A, the capacitance between the electrodes changes. Electronic device 100 determines the pressure intensity based on the change in capacitance. When a touch operation is applied to display screen 194, electronic device 100 detects the touch operation intensity based on pressure sensor 180A. Electronic device 100 can also calculate the touch position based on the detection signal from pressure sensor 180A. In some embodiments, touch operations applied to the same touch position but with different touch operation intensities can correspond to different operation commands. For example: when a touch operation with an intensity less than a first pressure threshold is applied to the SMS application icon, a command to view an SMS is executed. When a touch operation with an intensity greater than or equal to the first pressure threshold is applied to the SMS application icon, a command to create a new SMS is executed.

[0111] Touch sensor 180K, also known as a "touch panel," can be located on display screen 194. The touch sensor 180K and display screen 194 together form a touchscreen, also known as a "touch screen." Touch sensor 180K detects touch operations applied to or near it. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through display screen 194. In other embodiments, touch sensor 180K may also be located on the surface of electronic device 100, in a different position than display screen 194.

[0112] Buttons 190 include a power button, volume buttons, etc. Buttons 190 can be mechanical buttons or touch-sensitive buttons. Electronic device 100 can receive button input and generate key signal inputs related to user settings and function control of electronic device 100.

[0113] The software system of electronic device 100 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This application embodiment uses a layered Android system as an example to illustrate the software structure of electronic device 100.

[0114] Figure 2 is a software structure block diagram of an electronic device 100 according to an embodiment of this application.

[0115] It should be understood that a layered architecture can divide software into several layers, each with a clear role and division of labor; the layers can communicate with each other through software interfaces.

[0116] As shown in Figure 2, the Android system can be divided into four layers: from top to bottom, the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer. The application layer can include a series of application packages.

[0117] As shown in Figure 2, the application package may include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, and SMS.

[0118] The application framework layer provides application programming interfaces (APIs) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions.

[0119] As shown in Figure 2, the application framework layer may include a window manager, content provider, view system, phone manager, resource manager, notification manager, etc.

[0120] The window manager is used to manage windowed applications. It can retrieve screen size, determine the presence of a status bar, lock the screen, and capture screenshots, among other things.

[0121] Content providers store and retrieve data, making that data accessible to applications. This data can include videos, images, audio, phone calls made and received, browsing history and bookmarks, phone books, and more.

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

[0123] The phone manager is used to provide communication functions for electronic device 100. For example, it manages call status (including connection and disconnection).

[0124] The file explorer provides applications with various resources, such as localized strings, icons, images, layout files, video files, and more.

[0125] The notification manager allows applications to display notifications in the status bar. These notifications can be used to deliver informational messages and can disappear automatically after a short pause, requiring no user interaction. For example, the notification manager can be used to notify users of download completion or message alerts. The notification manager can also display notifications as icons or scrolling text in the top status bar, such as notifications from background applications, or as dialog boxes on the screen. Examples include displaying text messages in the status bar, emitting sounds, vibrating the device, and flashing indicator lights.

[0126] The Android runtime consists of core libraries and a virtual machine. The Android runtime is responsible for scheduling and managing the Android system.

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

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

[0129] The system library can include multiple functional modules, such as: surface manager, media libraries, 3D graphics processing libraries (e.g., Open Graphics Library for Embedded Systems, OpenGL ES) and 2D graphics engines (e.g., Skia Graphics Library, SGL).

[0130] The Surface Manager is used to manage the display subsystem and provides the blending of 2D and 3D layers for multiple applications.

[0131] The media library supports playback and recording of various audio and video formats, as well as still image files. It supports multiple audio and video encoding formats, such as MPEG4, H.264, Moving Picture Experts Group Audio Layer III (MP3), Advanced Audio Coding (AAC), Adaptive Multi-rate (AMR), Joint Photographic Experts Group (JPG), and Portable Network Graphics (PNG).

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

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

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

[0135] A user interface (UI) is the medium through which an application (APP) or operating system (OS) interacts and exchanges information with the user. It converts the internal form of information into a form that the user can understand. The user interface is source code written in specific computer languages ​​such as Java or Extensible Markup Language (XML). This source code is parsed and rendered on an electronic device, ultimately presenting content that the user can recognize. A common form of user interface is the graphical user interface (GUI), which refers to a user interface related to computer operation displayed graphically. It can be visible interface elements displayed on the screen of an electronic device, such as text, icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, and widgets.

[0136] A control is an element in a user interface used to receive user input, display information, or perform specific functions.

[0137] Device collaboration refers to a multi-device collaborative working mode that enables collaborative operation and resource sharing across systems and devices.

[0138] The electronic devices shown in Figures 1 and 2 above can be the first electronic device or the second electronic device in the following embodiments. The device collaboration method provided in the embodiments of this application will be explained in detail below with reference to the accompanying drawings and application scenarios.

[0139] HarmonyOS is a distributed operating system designed for the Internet of Things (IoT) era. Based on HarmonyOS, collaborative work between devices is possible, especially in various scenarios (such as smart homes and connected vehicles) for communication and data sharing. A core feature of HarmonyOS is the distributed soft bus, designed to enable seamless connectivity and collaborative work between different devices. Through the distributed soft bus, different devices can connect together to form a virtual distributed bus network. This makes device connections more flexible, thereby providing a richer and more intelligent inter-device interaction experience.

[0140] Currently, leveraging the distributed soft bus capabilities of the HarmonyOS distributed operating system, automatic device discovery and function transfer under the same account (i.e., the same account) can be achieved. When a function or task on one device under the same account requires support from another device, data and functions can be seamlessly transferred between these devices. For example, if a user starts listening to music on one device, the playback can be transferred to another device to continue.

[0141] However, due to security and privacy concerns, each account typically has its own independent device list and configuration information, and there is a lack of effective communication mechanisms between accounts. Even if near-field communication capabilities exist between devices, they often require manual addition and complex configuration (authentication) operations, making automatic discovery and functional flow impossible.

[0142] For example, a user can click the HyperTerminal function card in the control center interface of the mobile phone. The mobile phone can respond to the user's click operation and display the HyperTerminal interface as shown in Figure 3. As shown in Figure 3, the HyperTerminal interface displays icons 31, 32, and 33; where icon 31 represents the mobile phone (the local device), icon 32 represents the watch, and icon 33 represents the speaker. The account corresponding to the watch, the account corresponding to the speaker, and the account corresponding to the mobile phone are the same; obviously, the mobile phone can only automatically discover devices under the same account and display the icons representing these devices in the HyperTerminal interface.

[0143] When a user wants to transfer content displayed on their phone to a smart screen associated with another account, they need to re-bind the smart screen to the phone's account. Only after this re-binding is complete will the smart screen's icon appear on the SuperTerminal interface, allowing the user to drag and drop the icon to a designated area to transfer the content. During this re-binding process, the user must follow prompts to complete mutual authentication between the phone and the smart screen. For example, a prompt message as shown in Figure 4(a) will appear on the smart screen. After selecting "Trust within one week" or "Trust only this time," a connection code, such as "710827," will be displayed on the smart screen. Then, a prompt box as shown in Figure 4(b) will appear on the phone, requiring the user to manually enter the connection code. After entering the code, the phone can re-bind the smart screen to the phone's account, and the icon representing the smart screen will then appear on the phone's SuperTerminal interface. Clearly, this binding process is complex, time-consuming, and negatively impacts the user experience.

[0144] Therefore, how to achieve automatic discovery between devices corresponding to different accounts (i.e., automatic discovery between devices across accounts) is an urgent problem to be solved.

[0145] Based on this, this application provides a device collaboration method that can be applied to a first electronic device in a device collaboration system. The device collaboration system may include a first electronic device, at least one second electronic device, and a server, wherein the server establishes communication connections with the first electronic device and at least one second electronic device, respectively.

[0146] In this device collaboration method, a first electronic device can respond to a first user operation by sending a probe request, which is used to activate the device collaboration function. The first user operation then receives at least one probe response to the probe request. Based on the at least one probe response, at least one second electronic device is identified. The first electronic device and the at least one second electronic device belong to the same communication group, and some or all of the accounts corresponding to the at least one second electronic device are different from the accounts corresponding to the first electronic device. The probe response indicates that the first and second electronic devices belong to the same communication group. A first control and at least one second control are displayed, where the first control represents the first electronic device and the second control represents the second electronic device. Thus, when the first electronic device (e.g., a mobile phone as in the example above) activates the device collaboration function, it can automatically discover second electronic devices corresponding to different accounts (e.g., smart screens with other accounts as in the example above) and second electronic devices corresponding to the same account (e.g., watches and speakers with the same account as the mobile phone in the example above), expanding the range of automatically discovered devices. Subsequently, users can select appropriate devices from the automatically discovered devices for collaborative work according to their needs, improving the range of devices available for task collaboration or function flow and enhancing the user experience. Users do not need to manually bind second electronic devices with different accounts to the first electronic device, solving the problems of complex operation, wasted time, and negative impact on user experience during the binding process.

[0147] The first electronic device can be a terminal device with device collaboration capabilities, such as a mobile phone, tablet, or computer. The second electronic device is a device automatically discovered by the first electronic device that belongs to the same communication group as the first electronic device; the second electronic device can be a mobile phone, glasses, tablet, personal computer (PC), smart screen, watch, speaker, in-vehicle system, or headphones. The first electronic device and at least one second electronic device are on the same network, such as the same local area network (LAN) or the same wide area network (WAN); when the first electronic device and at least one second electronic device are on the same network, they can communicate via Bluetooth or Wireless Fidelity (WiFi).

[0148] In the embodiments of this application, the following example interfaces are mainly illustrated using a mobile phone as the first electronic device, but this does not constitute a limitation on this application. The HyperTerminal interface is a user interface for device collaboration on a mobile phone. The HyperTerminal interface can adopt different interface layouts and may include more or fewer controls.

[0149] Figure 5 is a schematic diagram of the main interface of a mobile phone. Users can bring up the control center interface through touch operations on the main interface. The touch operation can be a swipe down from the top of the main interface or a swipe up from the bottom of the main interface; the touch operation shown in Figure 5 is a swipe down from the top of the main interface. The control center interface can also be brought up in response to touch operations on other interfaces of the phone; this application embodiment does not limit how the control center interface is brought up.

[0150] Figure 6 is a schematic diagram of the control center interface of a mobile phone. As shown in Figure 6, the control center interface can display multiple functional controls, which can also be called cards or modules. Among these functional controls is the Super Terminal function card 41. As shown in Figure 6, the user can click the device collaboration icon 411 in the Super Terminal function card 41, and the mobile phone can respond to the user's click operation on the device collaboration icon 411 to start the device collaboration function; the first user operation includes the click operation on the device collaboration icon 411. Of course, the first user operation can also be other trigger operations used to start the device collaboration function, and the specific first user operation is not limited in this embodiment.

[0151] The device collaboration method provided in this application enables task collaboration or function transfer not only between the mobile phone and other devices (i.e., devices discovered by the mobile phone that are in the same communication group as the mobile phone), but also between other devices, improving the selectivity and convenience of task collaboration or function transfer. For example, content displayed on the mobile phone can be transferred to a smart screen for display; the account corresponding to the mobile phone and the account corresponding to the smart screen can be the same or different. Similarly, content displayed on a computer can be transferred to a smart screen for display; the account corresponding to the smart screen and the account corresponding to the computer can be the same or different.

[0152] In one feasible implementation, the mobile phone can activate the device collaboration function in response to a user's click on the device collaboration icon. It then broadcasts a detection request using wireless communication to detect devices in the same communication group as the mobile phone. Among the at least one device in the same communication group as the mobile phone, there can be devices belonging to different accounts (i.e., different account devices) and devices belonging to the same account (i.e., same account devices). The detection request carries relevant information about the mobile phone, such as at least one of the following: the phone's identification information, the account corresponding to the phone, and the identification information of the communication group corresponding to the phone. The phone's identification information uniquely identifies the mobile phone, and the identification information of the communication group corresponding to the phone uniquely identifies the communication group to which the phone belongs. When a nearby device (such as a smart screen) receives the detection request, it can determine whether the smart screen and the mobile phone belong to the same communication group. If it is determined that they belong to the same communication group, a detection response can be generated and sent to the mobile phone. This detection response indicates that the smart screen and the mobile phone belong to the same communication group. The mobile phone's identification information can be its universally unique identifier (UUID) or its media storage control address (MAC). The communication group's identification information can be its group identifier (FID).

[0153] The wireless communication function includes, but is not limited to, wireless communication functions implemented by technologies such as WLAN, radio frequency identification (REID), Wi-Fi, P2P, hotspot, infrared, ultrasound, Bluetooth, ZigBee, and ultra-wideband (UWB). This embodiment does not limit the scope of such wireless communication functions.

[0154] Understandably, many wireless communication technologies support positioning functions. Examples include Wi-Fi-based positioning, Bluetooth iBeacon-based positioning, Bluetooth 5.1-based positioning using the angle of arrival (AOA), and UWB-based positioning, etc., which are not limited in this embodiment. Among these, Wi-Fi-based and Bluetooth iBeacon-based positioning functions can measure the distance between the mobile phone and other electronic devices. Bluetooth 5.1-based AOA positioning and UWB-based positioning functions can measure the distance between the mobile phone and other electronic devices, as well as the orientation of other electronic devices relative to the mobile phone.

[0155] After a mobile phone sends a probe request, if multiple devices receive the request, each device can determine whether it belongs to the same communication group as the mobile phone based on the information carried in the probe request. For each device, if it determines that its recording module does not contain any group information, it determines that it and the mobile phone do not belong to the same communication group. If it determines that its recording module contains group information, it can match the information carried in the probe request with the group information to obtain a matching result. If the matching result indicates that the information carried in the probe information matches the group information, it determines that the device and the mobile phone belong to the same communication group, and then it can send a probe response to the mobile phone, indicating that the mobile phone and the device belong to the same communication group. If a device determines that it does not belong to the same communication group as the mobile phone, it does not need to send any information. Alternatively, if a device determines that it does not belong to the same communication group as the mobile phone, it can send a different probe response to the mobile phone, such as indicating that the mobile phone and the device belong to different communication groups.

[0156] The mobile phone can identify at least one device in the vicinity of the mobile phone and in the same communication group as the mobile phone based on at least one received probe response, and display an icon representing the mobile phone and at least one icon representing the at least one device to the user on the HyperTerminal interface.

[0157] For example, the number of at least one detection response received by the mobile phone can be four, and the number of at least one device identified around the mobile phone and in the same communication group as the mobile phone based on the four detection responses can also be four. The account corresponding to the mobile phone can be account m1; the four devices include devices with the same account and devices with different accounts. Devices with the same account can be, for example, a speaker and a watch, that is, the account corresponding to the speaker, the account corresponding to the watch, and the account corresponding to the mobile phone are all account m1. Devices with different accounts can be, for example, headphones and a smart screen; the account corresponding to the headphones, the account corresponding to the smart screen, and the account corresponding to the mobile phone can all be different, for example, the account corresponding to the headphones can be account m2, and the account corresponding to the smart screen can be account m3. As shown in Figure 7, the mobile phone can display an icon 51 representing the mobile phone, an icon 52 representing the watch, an icon 53 representing the speaker, an icon 54 representing the headphones, and an icon 55 representing the smart screen on the super terminal interface. Among them, the group member corresponding to the headphones can be "bb", and the group member corresponding to the smart screen can be "cc". In this way, the mobile phone can automatically discover devices with different accounts and devices with the same account, and can display icons representing devices with different accounts and devices with the same account on the super terminal interface, so that users can establish a device collaboration link between at least two devices among the mobile phone, speaker, headphones, smart screen and watch by operating (such as dragging) the icons shown in Figure 7, so as to realize task collaboration or function transfer between at least two devices.

[0158] The group information stored in the recording module of the aforementioned device is sent to the device by the server. The server stores group information for multiple different communication groups, which can also be referred to as family groups. Communication groups can be created by the server based on a received creation request. The server runs an Internet of Things (IoT) platform, which includes a group management module and a distribution module. The group management module is used for creating, updating, and deleting communication groups; it is also called the family group management module. The group management module is also used to manage the addition and deletion of group members and maintain the group information. Maintaining the group information may include maintaining the relationship between the communication group, group member accounts, and the corresponding device information (such as device identification information).

[0159] For each communication group, the distribution module connects to each device in the communication group to distribute the group information to each device. In other words, multiple devices in the same communication group share the group information.

[0160] The server maintains group information for multiple communication groups. Each communication group contains multiple devices (i.e., the first communication group corresponds to multiple devices), and these devices are the devices (electronic devices) corresponding to the accounts of multiple group members. Each communication group has multiple group members, including group management members and regular group members. A group member uniquely identifies a user; each group member corresponds to one account, which can be referred to as the account corresponding to the group member, the group member's account, or the group member's account. One account corresponds to at least one device.

[0161] In this system, one account corresponds to at least one device. When there is only one such device, it is designated as the first device. When there are multiple such devices, each device includes both the first device and a second device. The first device can be a portable device with real-time communication capabilities, a user interface, push notification services, and device collaboration features. For example, the first device could be a mobile phone or computer associated with the account. The second device can be a device different from the first device.

[0162] For example, depending on the usage scenario, the second device can be office equipment, home equipment, personal equipment, educational equipment, etc. Office equipment includes smart screens, printers, projectors, etc.; home equipment includes televisions, speakers, air conditioners, etc.; personal equipment includes mobile phones, tablets, watches, etc.; and educational equipment includes electronic whiteboards, smart desks, etc.

[0163] Taking a communication group q as an example, this communication group q corresponds to multiple devices. The aforementioned first electronic device and at least one second electronic device both belong to communication group q. The first electronic device and at least one second electronic device may be all the devices in the communication group q, or they may be some of the devices. For example, the first electronic device may be the first device corresponding to a group management member among the multiple devices; of course, the first electronic device may also be the first device corresponding to a regular group member among the multiple devices. Specifically, the first device may be a mobile phone. The second electronic device may be any device among the multiple devices other than the first electronic device. The server can send the group information of the communication group q to the multiple devices in the communication group q; wherein, the group information of the communication group q includes the identification information of the communication group q, the accounts of the group members, and the identification information of each device corresponding to each account. The server can obtain the group information of the communication group q in the following ways: The identification information of each device corresponding to an account can be presented through a device list.

[0164] In one feasible implementation, the server can send a first query request to the first device corresponding to the group management member of the communication group q. The first query request is used to query the account of the group management member and the identification information of each device corresponding to the account. For each ordinary group member of the communication group q, the server can send a second query request to the first device corresponding to the ordinary group member. The second query request is used to query the account of the ordinary group member and the identification information of each device corresponding to the account. Then, the server can combine the information sent by the first device corresponding to the group management member based on the first query request, the information sent by the first device corresponding to the ordinary group member based on the second query request, and the identification information of the communication group q to obtain the group information of the communication group q.

[0165] The first and second query requests can be sent periodically by the server; alternatively, they can be sent when the server detects changes in the group members. This improves the timeliness and effectiveness of the server in obtaining group information.

[0166] As shown in Figure 8, after the server obtains the group information of the communication group, it can send the group information to multiple devices in the communication group in real time or periodically through the distribution module. Figure 8 illustrates an example with two devices in the communication group, namely device p1 and device p2. As shown in Figure 8, device p1 includes a recording module and an authentication module. Device p1 can receive group information from the server and verify the group information through its device profile (DP). When the group information matches the profile definition, it is transmitted to the recording module on device p1, which stores the group information. When device p1 receives a probe request from another device, it can determine whether it is in the same communication group as that other device based on the probe request and the stored group information. Similarly, device p2 also includes a recording module and an authentication module. Device p2 can receive group information from the server and verify the group information through DP on device p2. When the group information matches the profile definition, it is transmitted to the recording module on device p2, which can store the group information. When device p2 receives a probe request from another device, it can determine whether it is in the same communication group as the other device based on the probe request and the group information. In this way, other devices can discover devices p1 and p2.

[0167] As shown in Figure 9, both devices p1 and p2 may also have communication modules. Devices p1 and p2 can network wirelessly, using either Bluetooth or WiFi. Device p1's authentication module stores its corresponding authentication information, and device p2's authentication module stores its corresponding authentication information. When devices p1 and p2 need to perform task collaboration or function transfer, before establishing a collaborative link between them, device p1 can determine whether device p2 is a legitimate device based on its stored authentication information; similarly, device p2 can determine whether device p1 is a legitimate device based on its stored authentication information. If both are legitimate devices, a collaborative link is established. The authentication information for device p1 can be its corresponding key information, including its group identifier key and user identifier key. Similarly, the authentication information for device p2 can be its corresponding key information, including its group identifier key and user identifier key. Device p1 and device p2 belong to the same communication group, and the group identification key corresponding to device p1 is the same as that corresponding to device p2.

[0168] When the group information stored in the server's group management module is updated, an update command is also sent to devices p1 and p2. The recording module in device p1 can update the group information stored in its recording module based on the update command, and the recording module in device p2 can also update the group information stored in its recording module based on the update command. The update command carries the new group information.

[0169] In this embodiment, a device running a smart living app can send a creation request to a server to create a communication group. The server responds to the creation request and creates the communication group. The device running the smart living app can be, for example, a mobile phone. The communication group can be referred to as a family group. After creating the communication group, the device running the smart living app can send a query command to the server to retrieve the group information corresponding to the communication group, thereby obtaining the group information from the server.

[0170] The phone's UI displays an icon for the Smart Life app, as shown in Figure 10. Users can tap this icon, and the phone will launch the app in response. Users can also tap the "Create New Family" card within the Smart Life app's UI. The phone will then generate a creation request and send it to the server. The server can create a family group based on this request. After creating the family group, the server can return a creation response to the phone, indicating successful creation. The phone can then display the created family group to the user based on this response. Users can add or delete family members (i.e., group members) within the Smart Life UI.

[0171] The following, in conjunction with the accompanying drawings, provides an exemplary explanation of adding new members to a family group.

[0172] As shown in Figure 11(a), users can click the "Family Management" card on the UI of the Smart Life APP to enter the family management interface shown in Figure 11(b). As shown in Figure 11(b), the family management interface displays multiple family groups belonging to the account corresponding to the mobile phone. There are three family groups: "AAA's Home," "BBB's Home," and "CCC's Home." Users can select any of these family groups to manage group members. As shown in Figure 11(b), users can click the "AAA's Home" card to enter the "AAA's Home" interface shown in Figure 11(c). As shown in Figure 11(c), the "AAA's Home" interface displays detailed information about "AAA's Home," such as the family name, family location, room and device management, and family members (group members). "AAA's Home" has two family members: the family member "aa" corresponding to the mobile phone and another family member "bb." As shown in Figure 11(c), users can click the "Add Member" card to enter the interface shown in Figure 11(d) where they can choose from various methods to add family members. As shown in Figure 11(d), users can click the "Add Member via Huawei Account" card to add a new member, such as "cc". After successfully adding a member, as shown in Figure 11(e), family members "aa", "bb", and the new family member "cc" will be displayed in the "AAA's Home" family members list. When a group administrator (i.e., the family administrator, such as aa) removes a family member, the member's consent is not required; the removal is done directly. Each family member uniquely identifies a user.

[0173] When a user (represented by the group management member) chooses any method to add member "cc" to "AAA's Home," the first device corresponding to the group management member, such as a mobile phone, responds to the user's addition operation by generating an addition request for family member "cc" and sending the request to the server to add member "cc" to "AAA's Home." The account corresponding to the mobile phone can be account m1, and the account of member cc can be account m3. As shown in Figure 12, the mobile phone can send this addition request to the server. The server can respond to the addition request by generating an invitation message for member cc to join "AAA's Home" through the group management module (family group management module) and sending the invitation message to the first device corresponding to the invited member cc (such as a terminal running the Smart Life APP) via push notification. After receiving the invitation message, the first device corresponding to the invited member cc displays the invitation message. When it detects that the user represented by the invited member cc has confirmed the invitation message, it can generate a confirmation message indicating agreement to join "AAA's Home" and send the confirmation message to the server. After receiving the confirmation message, the server can add the invited member cc to "AAA's Home" and update the group information of "AAA's Home" stored in the group management module. The updated group information includes the identifier of "AAA's Home", member aa's account m1 and the identifier of each device corresponding to account m1, member bb's account m2 and the identifier of each device corresponding to account m2, and member cc's account m3 and the identifier of each device corresponding to account m3.

[0174] For example, member aa's account m1 is bound to 2 devices, member bb's account m2 is bound to 1 device, and member cc's account m3 is bound to 2 devices. That is, the number of devices corresponding to "AAA's home" is 2 + 1 + 2 = 5. The server can send updated group information to each of the 5 devices. After receiving the group information, each device can store the group information in its own recording module so that each device can determine whether it is in the same family group as other devices based on the stored group information and the probe requests sent from other devices, thereby realizing the self-discovery of devices in the same family group.

[0175] In this embodiment of the application, the first electronic device may be a mobile phone. The mobile phone may display an icon representing the mobile phone and an icon representing at least one device around the mobile phone and in the same communication group as the mobile phone on the super terminal interface. The user can select the device to be coordinated and the cooperating device from the mobile phone and at least one device by dragging the icons displayed on the super terminal interface, so as to establish a device coordination link between the device to be coordinated and the cooperating device.

[0176] In this context, the device to be coordinated can be a mobile phone, and the cooperating device can be any of the at least one devices. When there are multiple devices (at least one), both the device to be coordinated and the cooperating device can be any of the at least one devices. Specifically, a user can drag an icon n1 displayed on the HyperTerminal interface to a designated area corresponding to icon n2; or, drag icon n1 to partially or completely overlap with icon n2. The device corresponding to icon n1 can be considered the device to be coordinated, and the device corresponding to icon n2 can be considered the cooperating device. In other words, the device corresponding to the dragged icon is the device to be coordinated.

[0177] In one feasible implementation, the mobile phone can respond to the user's drag-and-drop operation, generate a processing request to establish a device collaboration link between the device to be collaborated with the collaborating device, and send the processing request to the server. Upon receiving the processing request, the server can generate a control command based on the request. This control command is used to control the device to be collaborated with to establish the device collaboration link, and the server sends the control command to the device to be collaborated with. Of course, the control command can also be an instruction used to control the collaborating device to establish the device collaboration link; in this case, the server can send the control command to the collaborating device. The following explanation uses the example of a control command used to control the device to be collaborated with to establish the device collaboration link, with the server sending this control command to the device to be collaborated with.

[0178] The server can send control commands to the device to be collaborated with, which are used to control the device to establish a device collaboration link. Upon receiving the control command, the device to be collaborated with can respond by sending a verification request to the collaborating device. This verification request is used by the collaborating device to determine if the device to be collaborated with is a legitimate device. Upon receiving the verification request, if the collaborating device determines that the device to be collaborated with is a legitimate device, it sends a verification response to the device to be collaborated with. Upon receiving the verification response, if the collaborating device determines that the collaborating device is a legitimate device, the device to be collaborated with can establish a device collaboration link with the collaborating device via a distributed soft bus. Through the device collaboration link, the collaborating device can leverage the capabilities of the device to be collaborated with to transfer tasks to the device to be collaborated with for processing, thereby improving the user experience. The following explanation, combined with application scenarios, provides an exemplary illustration of establishing a device collaboration link between devices to be collaborated with and collaborating with other devices, as well as the task collaboration through this link.

[0179] For task collaboration scenarios between a mobile phone and a speaker: Users can drag icon 53 shown in Figure 7 to partially or completely overlap with icon 51 to establish a device collaboration link between the mobile phone and the speaker; where the speaker is the device to be collaborated with, and the mobile phone is the collaborating device. As shown in Figure 13, the mobile phone is playing song f. After establishing the device collaboration link between the mobile phone and the speaker, the song f playing on the mobile phone can be streamed to the speaker for playback. Of course, users can also drag icon 51 shown in Figure 7 to partially or completely overlap with icon 53 in the mobile phone's super terminal interface to establish a device collaboration link between the mobile phone and the speaker; where the mobile phone is the device to be collaborated with, and the speaker is the collaborating device; for example, if the speaker is playing song g, after establishing the device collaboration link between the mobile phone and the speaker, the song g playing on the speaker can be streamed to the mobile phone for playback.

[0180] For task collaboration scenarios between the watch and the smart screen: Users can drag icon 55 (shown in Figure 7) to partially or completely overlap with icon 52 to establish a device collaboration link between the watch and the smart screen; where the smart screen is the device to be collaborated with, and the watch is the collaborating device. For example, when the watch determines that the user is in a running scenario based on information such as the user's heart rate and blood pressure, the watch can transmit this information to the smart screen for display. As shown in Figure 14, the watch can also determine that the user is in a running scenario based on information such as the user's heart rate and blood pressure, and then link the smart screen to play videos related to the exercise scenario.

[0181] Of course, when a collaborating device doesn't support certain functions, a device collaboration link between the collaborating and non-collaborating devices can be established. This leverages the support of the non-collaborating device to enable functions that the collaborating device cannot support, thus better completing the corresponding business or tasks. This not only improves efficiency in life and work but also enhances user comfort, security, and convenience. For example, in a task collaboration scenario between a mobile phone and a printer, where the collaborating device is the mobile phone and the non-collaborating device is the printer, but the mobile phone doesn't support printing, when the printer icon appears on the terminal interface, the printer icon can be dragged to partially or completely overlap with the mobile phone icon to establish a device collaboration link between the printer and the mobile phone. The mobile phone can then automatically transfer the file to the printer for printing, improving the user experience.

[0182] The above solution establishes a device collaboration link between devices in the same family group by dragging and dropping icons displayed on the HyperTerminal interface. This collaboration link enables task collaboration or function transfer between devices, expanding the range of devices available for task collaboration, increasing device selectivity and flexibility, and improving the user experience. It solves the problems of poor selectivity and low user experience inherent in related technologies that only allow task collaboration or function transfer between devices within the same account.

[0183] When the first electronic device is a collaborating device, it can automatically detect target devices in the current environment. Then, based on user input, it can designate the target device as a collaborating device, enabling task collaboration or functional flow between the collaborating device and the collaborating device. The target device's task processing efficiency may be superior to that of the collaborating device, and this task can be one that the collaborating device is required to handle.

[0184] Figure 15 is a flowchart illustrating a device collaboration method provided in an embodiment of this application. This method is applied to a device collaboration system. The following explanation assumes that there are at least two second electronic devices. As shown in Figure 15, the device collaboration method includes steps S601 to S606; or the device collaboration method includes steps S601 to S605 and S607 to S611. The device collaboration method will now be explained in detail.

[0185] S601, the first electronic device responds to the first user operation by sending a probe request, the first user operation being used to activate the device collaboration function.

[0186] The first electronic device is a device with device collaboration capabilities; the detection request is used to discover devices around the first electronic device.

[0187] In this embodiment, the first user operation is an operation to initiate a device collaboration function. When the first electronic device detects the first user operation, it can initiate the device collaboration function in response to the first user operation and then send the detection request.

[0188] For example, the display interface of the first electronic device displays a HyperTerminal function card, and the first user operation can be a click operation on the HyperTerminal function card or a click operation on the device collaboration icon (card) in the HyperTerminal function card.

[0189] The detection request can be sent via wireless communication and broadcast. Specifically, the detection request can be used to detect devices around the first electronic device that are in the same communication group as the first electronic device; devices around the first electronic device can be understood as those in the same network as the first electronic device, or those that are less than a target distance threshold. For example, the target distance threshold can be 10 meters.

[0190] The probe request carries information about the first electronic device, including at least one of the following: the device's identification information, the account associated with the device, and the group identification information. The identification information uniquely identifies the device; for example, it could be a unique device identifier (UDID) or a MAC address. The group identification information can be understood as the identification information of the communication group to which the device belongs; for example, it could be an FID.

[0191] For example, the first electronic device may be a mobile phone, glasses, tablet, PC, smart screen, watch, speaker, car infotainment system, headphones, printer, projector, robot vacuum cleaner, etc.

[0192] S602, The second electronic device receives a probe request from the first electronic device.

[0193] In this embodiment, the second electronic device can receive the probe request through a listening interface. The second electronic device can then perform the following operations based on the probe request:

[0194] In one feasible implementation, the second electronic device can determine whether to send a first probe response or a second probe response to the first electronic device based on stored group information and the probe request. If the second electronic device determines, based on the probe request, that it belongs to the same communication group as the first electronic device, it can send a first probe response indicating that the first and second electronic devices belong to the same communication group. If the second electronic device determines, based on the stored group information and the probe request, that the first and second electronic devices do not belong to the same communication group, it can send a second probe response indicating that the first and second electronic devices do not belong to the same communication group.

[0195] In another feasible implementation, the second electronic device can send a probe response to the first electronic device based on stored group information and whether the probe request actually belongs to the same communication group as the first electronic device. If the second electronic device determines, based on the probe response, that it belongs to the same communication group as the first electronic device, it can send a probe response to the first electronic device. This probe response indicates that the first and second electronic devices belong to the same communication group; this probe response can be the first probe response described above. If the second electronic device determines, based on the stored group information and the probe request, that it does not belong to the same communication group as the first electronic device, it can choose not to send any information to the first electronic device.

[0196] Specifically, the information carried in the probe request can be matched with stored group information to obtain a matching result. If the matching result indicates that the information carried in the probe request matches the stored group information, it is determined that the second electronic device and the first electronic device belong to the same communication group. The group information includes at least one of the following: the identification information of the communication group corresponding to the second electronic device (i.e., the group identification information corresponding to the second electronic device), the account of the group member of the communication group corresponding to the second electronic device (i.e., the group member account), and the identification information of the electronic device corresponding to the group member's account. The identification information of the communication group corresponding to the second electronic device is used to uniquely identify the communication group corresponding to the second electronic device; for example, the identification information of the communication group corresponding to the second electronic device can be the FID of the communication group corresponding to the second electronic device. The identification information of the electronic device is used to uniquely identify the electronic device; the identification information of the electronic device corresponding to the group member's account can be the UDID of the electronic device. There are multiple group members, and each group member corresponds to one account.

[0197] For example, the group information stored in the second electronic device includes the FID of the communication group corresponding to the second electronic device, the account (e.g., a Huawei account) of the group members of the communication group corresponding to the second electronic device, and the UDID of the electronic device corresponding to the account. There are multiple accounts of the group members. The relevant information of the first electronic device carried in the probe request may be, for example, the UDID of the first electronic device; when the UDID of the first electronic device matches the UDID of the electronic device corresponding to the account of the group member stored in the second electronic device (that is, when the UDID of the first electronic device exists in the UDID of the electronic device corresponding to the group member), it is determined that the first electronic device and the second electronic device belong to the same communication group.

[0198] The group information stored in the second electronic device can be sent to the second electronic device by the server. The server can maintain the group information for each communication group. For each communication group, the server can send the group information of the communication group to each electronic device corresponding to the account of the group member in real time or periodically (also referred to as each electronic device corresponding to the communication group). When a group member joins or leaves the communication group, or when the electronic device corresponding to the account of a group member joins or leaves the communication group, the server can update the group information of the communication group.

[0199] For example, consider a communication group 's' with three members, whose accounts are Huawei account u1, Huawei account u2, and Huawei account u3. Huawei account u1 corresponds to a mobile phone or smart screen; Huawei account u2 corresponds to a watch or speaker; and Huawei account u3 corresponds to headphones or projectors. The server can send the group information corresponding to communication group 's' to the mobile phone, smart screen, watch, speaker, headphones, and projector in real-time or periodically. The group information includes the FID of communication group 's', Huawei account u1, Huawei account u2, Huawei account u3, the UDID of the mobile phone, smart screen, watch, speaker, headphones, and projector. When a new group member needs to be added, the new member's account, such as Huawei account u4, can be added to the group information of communication group 's', and the UDID of each electronic device corresponding to Huawei account u4 can also be added to the group information of communication group 's', thus updating the group information of communication group 's'. When it's necessary to delete a member from a group, such as a Huawei account (u3), the Huawei account (u3), the UDID of the headset corresponding to Huawei account (u3), and the UDID of the projector corresponding to Huawei account (u3) can be deleted from the group information corresponding to communication group (s) to update the group information. The first electronic device can be a mobile phone, and the second electronic device can be a device from a smart screen, watch, speaker, headset, or projector.

[0200] S603. If the second electronic device determines that it belongs to the same communication group as the first electronic device based on the probe request, the second electronic device sends a probe response to the first electronic device.

[0201] The detection response is used to indicate that the first electronic device and the second electronic device belong to the same communication group, and at least some of the electronic devices in the communication group have different accounts.

[0202] The detection response in S603 can be the first detection response in the specific implementation process of S602.

[0203] S604, the first electronic device receives at least one probe response in response to the probe request.

[0204] The probe response in S604 can be the first probe response in the specific implementation process of S602.

[0205] S605, the first electronic device determines at least one second electronic device based on at least one detection response.

[0206] In this scenario, the first electronic device and at least one second electronic device belong to the same communication group, and the account corresponding to some or all of the second electronic devices is different from the account corresponding to the first electronic device. The probe response is used to indicate that the first electronic device and the second electronic device belong to the same communication group. The probe response in S605 can be the first probe response in a specific implementation of S602.

[0207] In one feasible implementation, at least one second electronic device corresponds to an account that is different from the account of the first electronic device, that is, at least one second electronic device is a device with a different account.

[0208] In another feasible implementation, at least one second electronic device has an account corresponding to the first electronic device, as well as an account that is different from the account corresponding to the first electronic device, that is, at least one second electronic device has a device with different accounts and a device with the same account.

[0209] In this embodiment, the number of at least one detection response is the same as the number of at least one second electronic device. A first electronic device can determine a corresponding second electronic device based on a received detection response.

[0210] In one feasible implementation, the detection response includes identification information of the first electronic device and the second electronic device belonging to the same communication group, and identification information of the second electronic device.

[0211] For example, the first electronic device is a mobile phone. When the mobile phone activates the device collaboration function, it will discover devices within the Bluetooth or WiFi range that belong to the same household group as the mobile phone.

[0212] It should be noted that S606 or 607 to S611 can be executed after S605.

[0213] S606, The first electronic device displays a first control and at least one second control.

[0214] In this embodiment, the first electronic device can send a control acquisition request to the server to obtain a first control and at least one second control. The server can acquire the first control and at least one second control based on the control acquisition request and send the first control and at least one second control to the first electronic device. The first control and at least one second control can be generated by the server; alternatively, they can be sent to the server by other devices. The first electronic device can also determine the control corresponding to its identification information from a pre-stored set of controls to obtain the first control; and determine the control corresponding to the identification information of each second electronic device from a pre-stored set of controls to obtain at least one second control.

[0215] After obtaining the first control and the second control, the first electronic device can display the first control and at least one second control on the super terminal interface, so that the user can select the corresponding device for task collaboration or function flow according to the displayed first control and second control, thereby increasing the range of devices that can be selected when task collaboration or function flow and further improving the user experience.

[0216] S607. Send an acquisition request to the server, wherein the acquisition request is used to acquire first device information and second device information of at least one second electronic device.

[0217] The first device information represents the state and / or attributes of the first electronic device; the second device information represents the state and / or attributes of the second electronic device. The acquisition request carries the identification information of the first electronic device and the identification information of at least one second electronic device.

[0218] In one feasible implementation, the first device information includes at least one of the following: model information, configuration information, status information, size information, and an image of the first electronic device. The second device information may include at least one of the following: model information, configuration information, status information, size information, and an image of the second electronic device.

[0219] S608, The server receives an acquisition request from the first electronic device.

[0220] S609. Based on the acquisition request, the server sends first device information and second device information of at least one second electronic device to the first electronic device.

[0221] Wherein, the first device information represents the state and / or attributes of the first electronic device; the second electronic information represents the state and / or attributes of the second electronic device.

[0222] In this embodiment, the server can retrieve the first device information of the first electronic device and the second device information of at least one second electronic device from a stored pool of device information, based on the identification information of the first electronic device and the identification information of at least one second electronic device in the acquisition request. The first device information and the second device information of at least one second electronic device may be sent to the server by other devices or downloaded by the server via the network.

[0223] S610, the first electronic device receives first device information from the server and second device information from at least one second electronic device.

[0224] S611. The first electronic device displays a first control based on the first device information, and displays at least one second control based on the second device information of at least one second electronic device.

[0225] In this embodiment, the first electronic device can generate a first control based on first device information, and for each second electronic device, a second control can be generated based on the second device information of the second electronic device. Alternatively, the first control corresponding to the first device information can be determined from pre-generated controls, and the second control corresponding to each piece of second device information can be determined from pre-generated controls. After obtaining the first control and at least one second control, the first control and at least one second control can be displayed in a terminal interface.

[0226] For example, the first electronic device is a mobile phone. As shown in Figure 7, the first control can be the icon 51 representing a mobile phone in Figure 7. The second control can be an icon representing a device in the same communication group as the mobile phone. The number of at least one second control can be four, and at least one second control can be the icon 52 representing a watch, the icon 53 representing a speaker, the icon 54 representing headphones, and the icon 55 representing a smart screen in Figure 7.

[0227] This application provides a device collaboration method. After a first electronic device activates the device collaboration function, it can automatically discover at least one second electronic device in the same household group, such as a second electronic device corresponding to a different account or a second electronic device corresponding to the same account. This expands the scope of automatically discovered devices and improves the self-discovery capability of the first electronic device. Subsequently, users can select appropriate devices from the automatically discovered devices for task collaboration or function transfer according to their needs, improving the range of available devices and user experience during task collaboration or function transfer. Users do not need to manually bind second electronic devices with different accounts to the first electronic device, avoiding the problems of complex operation, wasted time, and negative impact on user experience associated with the binding process.

[0228] Figure 16 is a flowchart illustrating a device collaboration method provided in an embodiment of this application. This device collaboration method can be applied after displaying a first control and at least one second control. For example, it can be applied after S606 or S611 in the above embodiment, and it can also be applied after displaying a first control and at least one second control using other methods. It should be understood that the device collaboration method provided in Figure 16 is illustrated with the first electronic device as the collaborating device and any one of the at least one second electronic device as the device to be collaborated. This device collaboration method may include S701 to S705, and each step will be explained in detail below.

[0229] S701, the first electronic device responds to the second user's operation by sending a processing request to the server.

[0230] The processing request is used to establish a device collaboration link between the first electronic device and the second electronic device. This device collaboration link is used for task collaboration between the first and second electronic devices. The first electronic device is the collaborating device, and the second electronic device is the device to be collaborated with. The second user operation is used to associate the first and second electronic devices.

[0231] In one feasible implementation, the second user operation can be a user operation applied to a second control. For example, the user presses and holds a second control and drags it closer to a first control, releasing the second control when it reaches a designated area corresponding to the first control. The first control represents a first electronic device, and the second control represents a second electronic device. The dragged first and second controls may partially or completely overlap.

[0232] The first electronic device can be a mobile phone, and the second electronic device can be a smart screen. As shown in Figure 17, the first control can be an icon 81 representing a mobile phone; the second control can be an icon 85 representing a smart screen. The second user operation can be that the user presses and drags icon 85 until it partially overlaps with icon 81. The mobile phone can respond to the user's drag operation, generate a processing request to establish a device collaboration link between the mobile phone and the smart screen, and send the processing request to the server.

[0233] S702, The server receives a processing request from the first electronic device.

[0234] S703. Based on the processing request, the server sends control commands to the second electronic device.

[0235] Among them, the control command is used to control the second electronic device to establish a device collaboration link, and the second electronic device is the device to be collaborated with.

[0236] For example, the first electronic device is a mobile phone, the second electronic device is a smart screen, and the server can generate control instructions for the smart screen. These control instructions are used to control the smart screen to establish a device collaboration link between the smart screen and the mobile phone.

[0237] S704, the second electronic device receives control commands from the server.

[0238] S705, the second electronic device establishes a device collaboration link between the first electronic device and the second electronic device based on control commands.

[0239] In this embodiment, the second electronic device can verify the identity of the first electronic device based on control commands. When the identity verification of the first electronic device is successful, the first electronic device is determined to be a legitimate device, and a device collaboration link between the first electronic device and the second electronic device can be established through a distributed soft bus.

[0240] For example, the first electronic device is a mobile phone, and the second electronic device is a smart screen. The smart screen can verify the identity of the mobile phone based on control commands. If the identity verification of the mobile phone is successful, the mobile phone is determined to be a legitimate device. The smart screen can establish a device collaboration link between the mobile phone and the smart screen through a distributed soft bus.

[0241] S705 can also be implemented through S7051 to S7055:

[0242] S7051, the second electronic device sends a verification request to the first electronic device based on the control command.

[0243] The verification request is used to verify whether the second electronic device is a legitimate device.

[0244] In this embodiment of the application, the second electronic device can generate a verification request based on a control command and send the verification request to the first electronic device, so that after receiving the verification request, the first electronic device can determine whether the second electronic device is a legitimate device based on the verification request.

[0245] In one feasible implementation, the verification request carries identification information of the second electronic device and first encrypted information. The first encrypted information is obtained by encrypting the identification information of the second electronic device based on stored first key information. The identification information of the second electronic device is used to uniquely identify the second electronic device, and the identification information of the second electronic device may be, for example, the UDID or MAC address of the second electronic device.

[0246] The first key information may include a group identifier key corresponding to the second electronic device and a user identifier key corresponding to the second electronic device. The group identifier key corresponding to the second electronic device may be generated based on the identifier information of the communication group to which the second electronic device belongs, and the user identifier key corresponding to the second electronic device may be generated based on the account (i.e., group member account) to which the second electronic device belongs. Specifically, the first encrypted information may be obtained by encrypting the identifier information of the second electronic device using the group identifier key and the user identifier key. When the first electronic device and the second electronic device belong to the same communication group, the group identifier key corresponding to the first electronic device is the same as the group identifier key corresponding to the second electronic device.

[0247] For example, the first electronic device is a mobile phone, and the second electronic device is a smart screen; wherein, the smart screen can use the communication group key and user identification key corresponding to the smart screen to encrypt the UDID of the smart screen to obtain the first encrypted information, generate a verification request based on the UDID of the smart screen and the first encrypted information, and send the verification request to the mobile phone, wherein the verification request carries the UDID of the smart screen and the first encrypted information.

[0248] S7052, The first electronic device receives the verification request.

[0249] S7053. If the first electronic device determines that the second electronic device is a legitimate device based on the verification request, the first electronic device sends a verification response to the second electronic device.

[0250] In this embodiment, the first electronic device can determine whether the second electronic device is a legitimate device based on a verification request; if the second electronic device is determined to be a legitimate device, a verification response is generated and sent to the second electronic device. The verification response is used to determine whether the first electronic device is a legitimate device.

[0251] The first electronic device can determine whether the second electronic device is a legitimate device based on the verification request in the following ways:

[0252] The first electronic device can parse the verification request to obtain first encrypted information and the identification information of the second electronic device. The first electronic device can encrypt the identification information of the second electronic device based on the stored second key information to obtain second encrypted information. The first and second encrypted information can be matched to obtain a matching result. If the matching result indicates that the first and second encrypted information match, the second electronic device is determined to be a legitimate device. The second key information may include a group identification key and a user identification key corresponding to the first electronic device. The group identification key can be generated based on the identification information of the communication group to which the first electronic device belongs, and the user identification key can be generated based on the account (i.e., group member account) to which the first electronic device belongs.

[0253] The above scheme implements the legitimacy verification of the second electronic device by the first electronic device, ensuring that only legitimate devices can establish a collaborative link, thus guaranteeing the security and reliability of subsequent data transmission and operations. This helps prevent malicious devices from launching illegal attacks and protects user privacy and data security.

[0254] For example, the first electronic device is a mobile phone, and the second electronic device is a smart screen. The mobile phone can parse the verification request sent by the smart screen to obtain the smart screen's UDID and first encrypted information. The first encrypted information is obtained by encrypting the smart screen's UDID using the smart screen's corresponding communication group key and user identification key. The mobile phone can encrypt the smart screen's UDID using its own corresponding communication group key and user identification key to obtain second encrypted information. The mobile phone can match the first and second encrypted information to obtain a matching result. If the matching result indicates that the first and second encrypted information match, the mobile phone can determine that the smart screen is a legitimate device. For example, matching the first and second encrypted information can mean that the first and second encrypted information are identical.

[0255] In this embodiment, the verification response carries identification information of the first electronic device and third encryption information. The identification information of the first electronic device is used to uniquely identify the first electronic device; for example, the identification information of the first electronic device may be its UDID. The third encryption information may be obtained by encrypting the identification information of the first electronic device based on the stored second key information.

[0256] S7054, The second electronic device receives the verification response.

[0257] S7055. If the first electronic device is determined to be a legitimate device based on the verification response, the second electronic device establishes a device collaboration link between the first electronic device and the second electronic device.

[0258] In this embodiment, the second electronic device can determine whether the first electronic device is a legitimate device based on the verification response; if the first electronic device is determined to be a legitimate device, the second electronic device can establish a device collaboration link between the first electronic device and the second electronic device through a distributed soft bus.

[0259] The second electronic device can determine whether the first electronic device is a legitimate device based on the verification response in the following ways:

[0260] In one feasible implementation, the second electronic device can parse the verification response to obtain the identification information and third encryption information of the first electronic device; the second electronic device can encrypt the identification information of the first electronic device using the first key information (such as the group identification key corresponding to the second electronic device and the user identification key corresponding to the second electronic device) to obtain the fourth encryption information; the third encryption information and the fourth encryption information can be matched to obtain a matching result; if the matching result indicates that the third encryption information and the fourth encryption information match, the first electronic device is determined to be a legitimate device.

[0261] For example, the first electronic device is a mobile phone, and the second electronic device is a smart screen. The smart screen can receive a verification response sent by the mobile phone, parse the response to obtain the mobile phone's UDID and third encrypted information. The third encrypted information can be obtained by encrypting the mobile phone's UDID using the mobile phone's corresponding communication group key and user identification key. The smart screen can encrypt the mobile phone's UDID using its corresponding communication group key and user identification key to obtain fourth encrypted information. If the third and fourth encrypted information match, the mobile phone is determined to be a legitimate device.

[0262] Based on the above scheme, the mobile phone and the smart screen perform mutual verification. After both verifications are successful, the smart screen can establish a device collaboration link between the mobile phone and the smart screen based on the distributed soft bus, which improves the security and reliability of the established device collaboration link and ensures that the devices can communicate and interact with each other securely and reliably.

[0263] This application provides a device collaboration method. After displaying a first control and at least one second control, a first electronic device, in response to a second user operation, sends a processing request to a server. Based on the processing request, the server sends a control command to the second electronic device. Based on the control command, the second electronic device establishes a device collaboration link between the first and second electronic devices. In this way, it is possible to select appropriate devices from automatically discovered devices in the same family group for task collaboration or function flow according to user needs, thereby improving the range of available devices and user experience when performing task collaboration or function flow.

[0264] Moreover, before the device collaboration link is established, the user is unaware of the authentication process between the first and second electronic devices. Once the authentication is completed, the device collaboration link can be established, and task collaboration or function transfer can be automatically performed through the device collaboration link, which simplifies user operation and improves user experience.

[0265] Figure 18 is a flowchart illustrating another device collaboration method provided in an embodiment of this application. This device collaboration method can be applied after displaying a first control and at least one second control. For example, it can be applied after S606 or S611 in the above embodiment, and it can also be applied after displaying a first control and at least one second control using other methods. It should be understood that the device collaboration method provided in Figure 18 is illustrated with the first electronic device as the device to be collaborated with and one of the at least one second electronic devices as the collaborating device. This device collaboration method may include S901 to S905, and each step will be explained in detail below.

[0266] S901, the first electronic device responds to the second user's operation by sending a processing request to the server.

[0267] The processing request is used to establish a device collaboration link between the first electronic device and the second electronic device. This collaboration link is used for task collaboration between the two devices. The first electronic device is the device to be collaborated with, and the second electronic device is the collaborating device. The second user operation is used to associate the first and second electronic devices.

[0268] In one feasible implementation, the second user operation can be a user operation applied to the first control. For example, the user presses and holds the first control and drags it closer to the second control, releasing the first control when it reaches the designated area corresponding to the second control. The first control represents a first electronic device, and the second control represents a second electronic device. The dragged first and second controls may partially or completely overlap.

[0269] The first electronic device can be a mobile phone, and the second electronic device can be a smart screen. As shown in Figure 19, the first control can be an icon 1001 representing a mobile phone; the second control can be an icon 1005 representing a smart screen; and the second user operation can be the user dragging icon 1001 to partially overlap with icon 1005. The mobile phone can respond to the user's dragging operation, generate a processing request to establish a device collaboration link between the mobile phone and the smart screen, and send the processing request to the server.

[0270] S902, The server receives a processing request from the first electronic device.

[0271] S903. Based on the processing request, the server sends control commands to the first electronic device.

[0272] The control command is used to control the first electronic device to establish a device collaboration link between the first electronic device and the second electronic device. The first electronic device is the device to be collaborated with.

[0273] For example, the first electronic device is a mobile phone, and the second electronic device is a smart screen. The server can generate control instructions for the mobile phone, which are used to control the mobile phone to establish a device collaboration link between the smart screen and the mobile phone.

[0274] S904, The first electronic device receives control commands from the server.

[0275] S905. The first electronic device establishes a device collaboration link between the first electronic device and the second electronic device based on control commands.

[0276] In this embodiment, the first electronic device can verify the identity of the second electronic device based on control commands, and determine the second electronic device as a legitimate device when the identity verification of the second electronic device is successful; the first electronic device can establish a device collaboration link between the first electronic device and the second electronic device through a distributed soft bus.

[0277] For example, the first electronic device is a mobile phone, and the second electronic device is a smart screen. The mobile phone can verify the identity of the smart screen based on control commands. If the identity verification of the smart screen is successful, the smart screen is determined to be a legitimate device. The mobile phone can establish a device collaboration link between the mobile phone and the smart screen through a distributed soft bus.

[0278] S905 can also be implemented through S9051 to S9055:

[0279] S9051. The first electronic device sends a verification request to the second electronic device based on the control command.

[0280] The verification request is used to verify whether the first electronic device is a legitimate device.

[0281] In this embodiment of the application, the first electronic device can generate a verification request based on a control command and send the verification request to the second electronic device, so that after receiving the verification request, the second electronic device can determine whether the first electronic device is a legitimate device based on the verification request.

[0282] In one feasible implementation, the verification request carries identification information of the first electronic device and first encrypted information. The first encrypted information is obtained by encrypting the identification information of the first electronic device based on stored first key information. The identification information of the first electronic device is used to uniquely identify the first electronic device, and the identification information of the first electronic device may be, for example, the UDID or MAC address of the first electronic device.

[0283] The first key information may include a group identifier key and a user identifier key corresponding to the first electronic device. The group identifier key may be generated based on the identifier information of the communication group to which the first electronic device belongs, and the user identifier key may be generated based on the account (i.e., group member account) to which the first electronic device belongs. Specifically, the first encrypted information may be obtained by encrypting the identifier information of the first electronic device using the group identifier key and the user identifier key. When the first electronic device and the second electronic device belong to the same communication group, the group identifier key of the first electronic device and the group identifier key of the second electronic device are the same.

[0284] For example, the first electronic device is a mobile phone, and the second electronic device is a smart screen; wherein, the mobile phone can use the communication group key and user identification key corresponding to the mobile phone to encrypt the UDID of the mobile phone to obtain the first encrypted information, generate a verification request based on the UDID of the mobile phone and the first encrypted information, and send the verification request to the smart screen, the verification request carrying the UDID of the mobile phone and the first encrypted information.

[0285] S9052, The second electronic device receives the verification request.

[0286] S9053. If the second electronic device determines that the first electronic device is a legitimate device based on the verification request, the second electronic device sends a verification response to the first electronic device.

[0287] In this embodiment, the second electronic device can determine whether the first electronic device is a legitimate device based on a verification request; if the first electronic device is determined to be a legitimate device, a verification response is generated and sent to the first electronic device. The verification response is used to determine whether the second electronic device is a legitimate device.

[0288] The second electronic device can determine whether the first electronic device is a legitimate device based on the verification request in the following ways:

[0289] The second electronic device can parse the verification request to obtain first encrypted information and the identification information of the first electronic device. Based on the stored second key information, the second electronic device can encrypt the identification information of the first electronic device to obtain second encrypted information. The first and second encrypted information can be matched to obtain a matching result. If the matching result indicates that the first and second encrypted information match, the first electronic device is determined to be a legitimate device. The second key information may include a group identification key corresponding to the second electronic device and a user identification key corresponding to the second electronic device. The group identification key corresponding to the second electronic device may be generated based on the identification information of the communication group to which the second electronic device belongs, and the user identification key corresponding to the second electronic device may be generated based on the account (i.e., group member account) to which the second electronic device belongs.

[0290] The above scheme implements the legitimacy verification of the second electronic device by the first electronic device, ensuring that only legitimate devices can establish a collaborative link, thus guaranteeing the security and reliability of subsequent data transmission and operations. This helps prevent malicious devices from launching illegal attacks and protects user privacy and data security.

[0291] For example, the first electronic device is a mobile phone, and the second electronic device is a smart screen. The smart screen can parse the verification request sent by the mobile phone to obtain the mobile phone's UDID and first encrypted information. The first encrypted information is obtained by encrypting the mobile phone's UDID using the mobile phone's corresponding communication group key and user identifier key. The smart screen can encrypt the mobile phone's UDID using its corresponding communication group key and user identifier key to obtain second encrypted information. The smart screen can match the first and second encrypted information to obtain a matching result. If the matching result indicates that the first and second encrypted information match, the smart screen can determine that the mobile phone is a legitimate device. Matching the first and second encrypted information can mean that the first and second encrypted information are identical, or that the similarity between the first and second encrypted information is greater than a preset similarity threshold.

[0292] In this embodiment, the verification response carries identification information of the second electronic device and third encryption information. The identification information of the second electronic device is used to uniquely identify the second electronic device; for example, the identification information of the second electronic device may be its UDID. The third encryption information may be obtained by encrypting the identification information of the second electronic device based on the stored second key information.

[0293] S9054, The first electronic device receives the verification response.

[0294] S9055. If the first electronic device determines that the second electronic device is a legitimate device based on the verification response, the first electronic device shall establish a device collaboration link between the first electronic device and the second electronic device.

[0295] In this embodiment, the first electronic device can determine whether the second electronic device is a legitimate device based on the verification response; if the second electronic device is determined to be a legitimate device, the first electronic device can establish a device collaboration link between the first electronic device and the second electronic device through a distributed soft bus.

[0296] The first electronic device can determine whether the second electronic device is a legitimate device based on the verification response in the following ways:

[0297] In one feasible implementation, the first electronic device can parse the verification response to obtain the identification information and third encrypted information of the second electronic device. The first electronic device can then use first key information (such as the group identification key and user identification key corresponding to the first electronic device) to encrypt the identification information of the second electronic device, obtaining fourth encrypted information. The third and fourth encrypted information can be matched to obtain a matching result. If the matching result indicates that the third and fourth encrypted information match, the second electronic device is determined to be a legitimate device. Matching the third and fourth encrypted information can mean that the third and fourth encrypted information are identical, or that the similarity between the third and fourth encrypted information is greater than a preset similarity threshold.

[0298] For example, the first electronic device is a mobile phone, and the second electronic device is a smart screen. The mobile phone can receive a verification response from the smart screen, parse the response to obtain the smart screen's UDID and third encrypted information. The third encrypted information can be obtained by encrypting the smart screen's UDID using the smart screen's corresponding communication group key and user identification key. The mobile phone can also encrypt the smart screen's UDID using its own corresponding communication group key and user identification key to obtain fourth encrypted information. If the third and fourth encrypted information match, the mobile phone is determined to be a legitimate device.

[0299] Based on the above scheme, the mobile phone and the smart screen perform mutual verification. After both verifications are successful, the smart screen can establish a device collaboration link between the mobile phone and the smart screen based on the distributed soft bus, which improves the security and reliability of the established device collaboration link and ensures that the devices can communicate and interact with each other securely and reliably.

[0300] This application provides a device collaboration method. After displaying a first control and at least one second control, a first electronic device, in response to a second user operation, sends a processing request to a server. Based on the processing request, the server sends a control command to the first electronic device. Based on the control command, the first electronic device establishes a device collaboration link between itself and a second electronic device. In this way, it is possible to select appropriate devices from automatically discovered devices in the same family group for task collaboration or function flow according to user needs, thereby improving the range of available devices and user experience when performing task collaboration or function flow.

[0301] Moreover, before the device collaboration link is established, the user is unaware of the authentication process between the first and second electronic devices. Once the authentication is completed, the device collaboration link can be established, and task collaboration or function transfer can be automatically performed through the device collaboration link, which simplifies user operation and improves user experience.

[0302] Figure 20 is a flowchart illustrating a device collaboration method provided in an embodiment of this application. This device collaboration method can be applied after displaying a first control and at least one second control. For example, it can be applied after S606 or S611 in the above embodiment, and it can also be applied after displaying a first control and at least one second control using other methods. It should be understood that the device collaboration method provided in Figure 20 is illustrated by establishing a device collaboration link between two second electronic devices, with at least one second electronic device as a plurality of examples. The first second electronic device is the device to be collaborated with, and the second second electronic device is the collaborating device. This device collaboration method may include S1101 to S1105, and each step will be explained in detail below.

[0303] S1101, the first electronic device responds to the second user's operation by sending a processing request to the server.

[0304] The processing request is used to establish a device collaboration link between the first and second electronic devices. This collaboration link is used for task collaboration between the two devices. The first electronic device is the device to be collaborated with, and the second electronic device is the collaborating device. The second user operation is used to associate the first and second electronic devices.

[0305] In one feasible implementation, the second user operation can be an operation applied to a second control. For example, a user presses and holds one second control and drags it closer to another second control. The user releases the dragged second control when it reaches a designated area corresponding to the other second control. Different second controls represent different second electronic devices. The two dragged second controls may partially or completely overlap. The device corresponding to the second control dragged by the user is the first second electronic device.

[0306] For example, the first electronic device is a mobile phone, the first second electronic device can be a smart screen, and the second second electronic device can be a watch; as shown in Figure 21, the first control can be an icon 1201 representing a mobile phone; the second control corresponding to the first second electronic device can be an icon 1205 representing a smart screen, and the second control corresponding to the second second electronic device can be an icon 1202 representing a watch. The second user operation can be that the user presses and drags icon 1205 until it partially overlaps with icon 1202. The mobile phone can respond to the user's drag operation, generate a processing request for establishing a device collaboration link between the smart screen and the watch, and send the processing request to the server.

[0307] S1102, The server receives a processing request from the first electronic device.

[0308] S1103. Based on the processing request, the server sends control instructions to the first second electronic device.

[0309] Among them, the control command is used to control the first second electronic device to establish a device collaboration link between the first second electronic device and the second second electronic device.

[0310] For example, the first electronic device is a mobile phone, the first second electronic device is a smart screen, and the second second electronic device is a watch; after receiving the processing request sent by the mobile phone, the server can generate a control instruction for the smart screen, which is used to control the smart screen to establish a device collaboration link between the smart screen and the watch.

[0311] S1104, The first second electronic device receives control commands from the server.

[0312] S1105. The first second electronic device establishes a device collaboration link between the first second electronic device and the second second electronic device based on control commands.

[0313] In this embodiment, the first second electronic device can verify the identity of the second second electronic device based on control commands. When the identity verification of the second second electronic device passes, the second second electronic device is determined to be a legitimate device. The first second electronic device can establish a device collaboration link between the first second electronic device and the second second electronic device through a distributed soft bus.

[0314] For example, the first second electronic device is a smart screen, and the second second electronic device is a watch. The smart screen can verify the identity of the watch based on control commands. If the identity verification of the watch is successful, the watch is determined to be a legitimate device. The smart screen can establish a device collaboration link between the smart screen and the watch through a distributed soft bus.

[0315] S1105 can also be implemented through S11051 to S11055:

[0316] S11051, The first second electronic device sends a verification request to the second second electronic device based on the control command.

[0317] The verification request is used to verify whether the first second electronic device is a legitimate device.

[0318] In this embodiment of the application, the first second electronic device can generate a verification request based on a control command and send the verification request to the second second electronic device, so that after receiving the verification request, the second second electronic device can determine whether the first second electronic device is a legitimate device based on the verification request.

[0319] In one feasible implementation, the verification request carries identification information of the first second electronic device and first encrypted information. The first encrypted information is obtained by encrypting the identification information of the first second electronic device based on stored first key information. The identification information of the first second electronic device is used to uniquely identify the first second electronic device, and the identification information of the first second electronic device may be, for example, the UDID or MAC address of the first second electronic device.

[0320] The first key information may include a group identifier key and a user identifier key corresponding to the first second electronic device. The group identifier key may be generated based on the identifier information of the communication group to which the first second electronic device belongs, and the user identifier key may be generated based on the account (i.e., group member account) to which the first second electronic device belongs. Specifically, the first encrypted information may be obtained by encrypting the identifier information of the first second electronic device using its corresponding group identifier key and user identifier key. When the first and second second electronic devices belong to the same communication group, their corresponding group identifier keys are the same.

[0321] For example, the first second electronic device is a smart screen, and the second second electronic device is a watch; wherein, the smart screen can use the communication group key and user identification key corresponding to the smart screen to encrypt the UDID of the smart screen to obtain the first encrypted information, generate a verification request based on the UDID of the smart screen and the first encrypted information, and send the verification request to the watch, the verification request carrying the UDID of the smart screen and the first encrypted information.

[0322] S11052, The second electronic device receives the verification request.

[0323] S11053. If the second electronic device determines that the first electronic device is a legitimate device based on the verification request, the second electronic device sends a verification response to the first electronic device.

[0324] In this embodiment, the second electronic device can determine whether the first electronic device is a legitimate device based on a verification request; if the first electronic device is determined to be a legitimate device, a verification response is generated and sent to the first electronic device. The verification response is used to determine whether the second electronic device is a legitimate device.

[0325] The second electronic device, based on the verification request, determines whether the first electronic device is a legitimate device in the following ways:

[0326] The second electronic device can parse the verification request to obtain the first encrypted information and the identification information of the first electronic device. Based on the stored second key information, the second electronic device can encrypt the identification information of the first electronic device to obtain the second encrypted information. The second electronic device can match the first and second encrypted information to obtain a matching result. If the matching result indicates that the first and second encrypted information match, the first electronic device is determined to be a legitimate device. The second key information may include a group identification key and a user identification key corresponding to the second electronic device. The group identification key can be generated based on the identification information of the communication group to which the second electronic device belongs, and the user identification key can be generated based on the account (i.e., group member account) to which the second electronic device belongs.

[0327] The above scheme implements the legitimacy verification of the second electronic device by the first second electronic device, ensuring that only legitimate devices can establish a device collaboration link, thus guaranteeing the security and reliability of subsequent data transmission and operations. This helps prevent malicious devices from launching illegal attacks and protects user privacy and data security.

[0328] For example, the first second electronic device is a smart screen, and the second second electronic device is a watch. The watch can parse the verification request sent by the smart screen to obtain the smart screen's UDID and first encrypted information. The first encrypted information is obtained by encrypting the smart screen's UDID using the smart screen's corresponding communication group key and user identification key. The watch can encrypt the smart screen's UDID using its corresponding communication group key and user identification key to obtain second encrypted information. The watch can match the first and second encrypted information to obtain a matching result; if the matching result indicates that the first and second encrypted information match, the watch can determine that the smart screen is a legitimate device.

[0329] In this embodiment, the verification response carries identification information of the second electronic device and third encryption information. The identification information of the second electronic device is used to uniquely identify the second electronic device; for example, the identification information of the second electronic device may be its UDID. The third encryption information may be obtained by encrypting the identification information of the second electronic device based on the stored second key information.

[0330] S11054, The first second electronic device receives the verification response.

[0331] S11055. If the first second electronic device determines that the second second electronic device is a legitimate device based on the verification response, the first second electronic device shall establish a device collaboration link between the first second electronic device and the second second electronic device.

[0332] In this embodiment of the application, the first second electronic device can determine whether the second second electronic device is a legitimate device based on the verification response; if the second second electronic device is determined to be a legitimate device, the first second electronic device can establish a device collaboration link between the first second electronic device and the second second electronic device through a distributed soft bus.

[0333] The determination of whether a second electronic device is a legitimate device based on a verification response can be achieved in the following ways:

[0334] In one feasible implementation, the first second electronic device can parse the verification response to obtain the identification information and third encryption information of the second second electronic device; the first second electronic device can use first key information, such as the group identification key and the user identification key corresponding to the first second electronic device, to encrypt the identification information of the second second electronic device to obtain fourth encryption information; the third encryption information and the fourth encryption information can be matched to obtain a matching result; if the matching result indicates that the third encryption information and the fourth encryption information match, the second second electronic device is determined to be a legitimate device.

[0335] For example, the first second electronic device is a smart screen, and the second second electronic device is a watch. The smart screen can receive a verification response from the watch, parse the response to obtain the watch's UDID and third encrypted information. The third encrypted information can be obtained by encrypting the watch's UDID using the watch's corresponding communication group key and user identification key. The smart screen can also encrypt the watch's UDID using its own corresponding communication group key and user identification key to obtain fourth encrypted information. If the third and fourth encrypted information match, the watch is determined to be a legitimate device.

[0336] Based on the above solution, the smart screen and the watch perform mutual verification. After both verifications are successful, the smart screen can establish a device collaboration link between the smart screen and the watch based on a distributed soft bus. This improves the security and reliability of the established device collaboration link and ensures that the devices can communicate and interact with each other securely and reliably.

[0337] The first and second electronic devices can collaborate on tasks or transfer functions through an established device collaboration link. For example, if the first electronic device is a smart screen and the second is a watch, the watch can transfer its currently displayed content to the smart screen. Alternatively, the watch can determine that the user is running based on information such as heart rate and blood pressure, and then link the smart screen to play videos related to the exercise scenario. The accounts associated with the watch and the display screen can be the same or different.

[0338] This application provides a device collaboration method. After displaying a first control and at least one second control, the first electronic device, in response to a second user operation, sends a processing request to a server. The second user operation is used to associate a first second electronic device with a second second electronic device. Based on the processing request, the server sends a control command to the first second electronic device. Based on the control command, the first second electronic device establishes a device collaboration link with the second second electronic device, enabling them to collaborate on tasks or perform function transitions through the device collaboration link. This allows for the selection of appropriate devices from automatically discovered devices in the same household group for task collaboration or function transitions based on user needs, improving the range of available devices and user experience during task collaboration or function transitions.

[0339] Moreover, before establishing the device collaboration link, the user is unaware of the authentication process between the first and second electronic devices. Once the authentication is completed, the device collaboration link can be established, and task collaboration or function flow can be automatically performed through the device collaboration link, which simplifies user operation and improves user experience.

[0340] In the above embodiments, among the first control and at least one second control displayed on the first electronic device, the representation of the control corresponding to the same account device and the representation of the control corresponding to the different account device can be different. This makes it easier for users to distinguish which devices are from the same account and which are from different accounts, thereby improving the user experience.

[0341] For example, the first electronic device is a mobile phone, and the number of at least four second electronic devices is four in total. These at least one second electronic device is a watch, a speaker, headphones, and a smart screen. The account corresponding to the mobile phone can be account m1, the account corresponding to the speaker can be account m1, the account corresponding to the watch can be account m1, the account corresponding to the headphones can be account m2, and the account corresponding to the smart screen can be account m3. The icons representing the mobile phone, watch, and speaker displayed on the first electronic device can be the same color. However, their colors are different from the icons representing the headphones and smart screen displayed on the first electronic device. For example, the icons representing the mobile phone, watch, and speaker can all be yellow, while the icon representing the headphones can be green or blue.

[0342] The device collaboration methods provided in the above embodiments automatically discover devices with the same account and devices with different accounts, and can establish device collaboration links between devices across accounts (i.e., devices with different accounts). Through these device collaboration links, task collaboration or function transfer can be performed between devices across accounts, expanding the range of devices that can be selected during task collaboration or function transfer and improving the user experience. Moreover, before establishing a device collaboration link between devices across accounts, the mutual authentication between devices across accounts does not require user awareness, simplifying user operations and further improving the user experience.

[0343] Figure 22 is a schematic block diagram of a device collaboration device provided in an embodiment of this application. As shown in Figure 22, the device collaboration device 13 may include a communication unit 1301 and a processing unit 1302. The communication unit 1301 can implement corresponding communication functions, which can be internal communication within the device collaboration device 13 or communication between the device collaboration device 13 and other devices; the processing unit 1302 can implement corresponding processing functions. The communication unit 1301 may also be referred to as a communication interface or a transceiver unit. Optionally, the device collaboration device 13 may also include a storage unit, which can be used to store instructions and / or data. The processing unit 1302 can read the instructions and / or data in the storage unit to enable the device to implement the aforementioned method embodiment.

[0344] In one possible design, the device coordination device 13 can be the first electronic device in the aforementioned method embodiments, or it can be a module or chip applied to the first electronic device. The device coordination device 13 can be used for the steps or processes performed by the first electronic device in the aforementioned method embodiments.

[0345] Specifically, the communication unit 1301 is configured to send a probe request in response to a first user operation, wherein the first user operation is configured to initiate a device collaboration function; the communication unit 1301 is also configured to receive at least one probe response in response to the probe request; the processing unit 1302 is configured to determine at least one second electronic device based on at least one probe response, wherein the first electronic device and at least one second electronic device belong to the same communication group, and the accounts corresponding to some or all of the at least one second electronic device are different from the accounts corresponding to the first electronic device, and the probe response is configured to indicate that the first electronic device and the second electronic device belong to the same communication group; the processing unit 1302 is also configured to display a first control and at least one second control, wherein the first control represents the first electronic device and the second control represents the second electronic device.

[0346] Optionally, the probe request may carry at least one of the following: the identification information of the first electronic device, the account corresponding to the first electronic device, and the group identification information corresponding to the first electronic device.

[0347] Optionally, the probe response is sent by the second electronic device after determining, based on the probe request and the stored group information corresponding to the second electronic device, that it belongs to the same communication group as the first electronic device.

[0348] Optionally, the detection response may carry group identification information of the communication group and identification information of the second electronic device.

[0349] Optionally, the communication unit 1301 is further configured to send a processing request to the server in response to a second user operation, wherein the processing request is used to establish a device collaboration link between the collaborating device and the device to be collaborated with, wherein the collaborating device and the device to be collaborated with are electronic devices in a first electronic device and at least one second electronic device, and the second user operation is used to associate the collaborating device and the device to be collaborated with.

[0350] Optionally, the communication unit 1301 is further configured to receive a verification request from the device to be collaborated with, wherein the verification request is used to determine whether the device to be collaborated with is a legitimate device, the verification request is sent by the device to be collaborated with based on a control command from the server, and the control command is sent by the server based on a processing request; if the device to be collaborated with is determined to be a legitimate device based on the verification request, a verification response is sent to the device to be collaborated with, the verification response being used to determine whether the first electronic device is a legitimate device.

[0351] Optionally, the processing unit 1302 is further configured to parse the verification request to obtain the identification information of the device to be coordinated and the first encrypted information, wherein the first encrypted information is obtained by encrypting the identification information of the device to be coordinated based on the group identification key corresponding to the device to be coordinated and the user identification key corresponding to the device to be coordinated; the processing unit 1302 is further configured to encrypt the identification information of the device to be coordinated based on the group identification key corresponding to the first electronic device and the user identification key corresponding to the first electronic device to obtain the second encrypted information; the processing unit 1302 is further configured to determine that the device to be coordinated is a legitimate device if the first encrypted information and the second encrypted information match; the communication unit 1301 is further configured to send a verification response to the device to be coordinated, wherein the verification response carries the identification information of the first electronic device and the third encrypted information, wherein the third encrypted information is obtained by encrypting the identification information of the first electronic device based on the group identification key corresponding to the first electronic device and the user identification key corresponding to the first electronic device.

[0352] Optionally, the communication unit 1301 is further configured to receive control instructions from the server, wherein the control instructions are used to control the first electronic device to establish a device cooperative link, and the control instructions are sent by the server based on a processing request; the communication unit 1301 is further configured to send a verification request to the cooperative device based on the control instructions, wherein the verification request is used to determine whether the first electronic device is a legitimate device; the processing unit 1302 is further configured to establish a device cooperative link if the cooperative device is determined to be a legitimate device based on the verification response from the cooperative device, wherein the verification response is sent by the cooperative device if the first electronic device is determined to be a legitimate device.

[0353] Optionally, the processing unit 1302 is specifically used to parse the verification response to obtain the identification information and third encryption information of the collaborative device. The third encryption information is obtained by encrypting the identification information of the collaborative device based on the group identification key and the user identification key corresponding to the collaborative device. The identification information of the collaborative device is then encrypted based on the group identification key and the user identification key corresponding to the first electronic device to obtain fourth encryption information. If the third encryption information and the fourth encryption information match, the collaborative device is determined to be a legitimate device, and a device collaboration link is established.

[0354] Optionally, the communication unit 1301 is further configured to acquire first device information of the first electronic device and second device information of at least one second electronic device, wherein the first device information represents the state and / or attributes of the first electronic device, and the second device information represents the state and / or attributes of the second electronic device; the processing unit 1302 is specifically configured to display a first control based on the first device information; and display at least one second control based on the second device information of at least one second electronic device.

[0355] Optionally, the communication unit 1301 is specifically used to send an acquisition request to the server, wherein the acquisition request is used to acquire first device information and second device information of at least one second electronic device; and to receive first device information and second device information of at least one second electronic device from the server.

[0356] In one possible design, the device coordination device 13 can be the server in the aforementioned method embodiments, or it can be a module or chip applied to the server. The device coordination device 13 can be used for the steps or processes performed by the server in the above method embodiments.

[0357] Specifically, the communication unit 1301 is used to receive an acquisition request from a first electronic device, wherein the acquisition request is used to acquire first device information of the first electronic device and second device information of at least one second electronic device, the first device information representing the state and / or attributes of the first electronic device, the second device information representing the state and / or attributes of the second electronic device, the first electronic device and at least one second electronic device belonging to the same communication group, and the account corresponding to some or all of the at least one second electronic device being different from the account corresponding to the first electronic device; the communication unit 1301 is also used to send the first device information and the second device information of at least one second electronic device to the first electronic device, wherein the first device information is used to display a first control representing the first electronic device, and the second device information is used to display a second control representing the second electronic device.

[0358] Optionally, the communication unit 1301 is further configured to receive a processing request from the first electronic device, wherein the processing request is used to establish a device collaboration link between the collaborating device and the device to be collaborated; the processing unit 1302 is configured to generate a control command based on the processing request; the communication unit 1301 is further configured to send a control command to the device to be collaborated, wherein the control command is used to control the device to be collaborated to establish a device collaboration link.

[0359] Optionally, the communication unit 1301 is further configured to send group information of the communication group to multiple electronic devices in the communication group, wherein the group information is used by the electronic devices to determine whether they are in the same communication group as other electronic devices, and the multiple electronic devices include a first electronic device and at least one second electronic device.

[0360] Optionally, the group information includes at least one of the following: group identification information, group member accounts, and identification information of the electronic devices corresponding to the group member accounts.

[0361] In one possible design, the device coordination device 13 can be a second electronic device in the aforementioned method embodiments, or it can be a module or chip applied to the second electronic device. The device coordination device 13 can be used for the steps or processes performed by the second electronic device in the aforementioned method embodiments.

[0362] Optionally, the communication unit 1301 is configured to receive a probe request from the first electronic device; the communication unit 1301 is also configured to send a probe response to the first electronic device if it is determined based on the probe request that the first electronic device belongs to the same communication group as the first electronic device, wherein the probe response is used to indicate that the first electronic device and the second electronic device belong to the same communication group, and at least some of the electronic devices in the communication group have different accounts.

[0363] Optionally, the probe request may carry at least one of the following: the identification information of the first electronic device, the account corresponding to the first electronic device, and the group identification information corresponding to the first electronic device.

[0364] Optionally, the processing unit 1302 is used to determine whether the first electronic device and the second electronic device belong to the same communication group based on the probe request and the group information corresponding to the stored second electronic device; the communication unit 1301 is used to send a probe response to the first electronic device if the first electronic device and the second electronic device belong to the same communication group.

[0365] Optionally, the detection response may carry group identification information of the communication group and identification information of the second electronic device.

[0366] Optionally, the communication unit 1301 is further configured to receive group information from the server, wherein the group information includes at least one of group identification information, group member accounts, and identification information of electronic devices corresponding to the group member accounts.

[0367] Optionally, the communication unit 1301 is further configured to receive a verification request from the device to be collaborated with, wherein the verification request is used to determine whether the device to be collaborated with is a legitimate device, and the verification request is sent by the device to be collaborated with based on a control command from the server; the communication unit 1301 is further configured to send a verification response to the device to be collaborated with if the device to be collaborated with is determined to be a legitimate device based on the verification request, wherein the verification response is used to determine whether the second electronic device is a legitimate device.

[0368] Optionally, the processing unit 1302 is used to parse the verification request to obtain the identification information of the device to be coordinated and the first encrypted information, wherein the first encrypted information is obtained by encrypting the identification information of the device to be coordinated based on the group identification key and the user identification key corresponding to the device to be coordinated; the identification information of the device to be coordinated is encrypted based on the group identification key and the user identification key corresponding to the second electronic device to obtain the second encrypted information; if the first encrypted information and the second encrypted information match, the device to be coordinated is determined to be a legitimate device; the communication unit 1301 is further used to send a verification response to the device to be coordinated, wherein the verification response carries the identification information of the second electronic device and the third encrypted information, wherein the third encrypted information is obtained by encrypting the identification information of the second electronic device based on the group identification key and the user identification key corresponding to the second electronic device.

[0369] Optionally, the communication unit 1301 is further configured to receive control instructions from the server, wherein the control instructions are used to control the second electronic device and establish a device collaboration link between the second electronic device and the collaborating device; based on the control instructions, send a verification request to the collaborating device, wherein the verification request is used to determine whether the second electronic device is a legitimate device; and the processing unit 1302 establishes a device collaboration link if the collaborating device is determined to be a legitimate device based on the verification response from the collaborating device, wherein the verification response is sent by the collaborating device if the second electronic device is determined to be a legitimate device.

[0370] Optionally, the processing unit 1302 is further configured to parse the verification response to obtain the identification information and third encryption information of the collaborative device. The third encryption information is obtained by encrypting the identification information of the collaborative device based on the group identification key and the user identification key corresponding to the collaborative device. The identification information of the collaborative device is then encrypted based on the group identification key and the user identification key corresponding to the second electronic device to obtain fourth encryption information. If the third encryption information and the fourth encryption information match, the collaborative device is determined to be a legitimate device, and a device collaboration link is established.

[0371] For details on the steps or processes executed by each unit in the equipment coordination device 13, please refer to the descriptions in the corresponding methods; they will not be elaborated here.

[0372] It should be understood that the "unit" in the device coordination device 13 can be implemented in hardware, software, or by hardware executing corresponding software. For example, a "unit" can refer to an application-specific integrated circuit (ASIC), electronic circuitry, a processor (e.g., a shared processor, a proprietary processor, or a group processor) and memory for executing one or more software or firmware programs, combined logic circuitry, and / or other suitable components supporting the described functions. As another example, the communication unit 1301 can be replaced by a transceiver circuit (e.g., it may include receiving and transmitting circuitry), and the processing unit 1302 can be replaced by a processor or processing circuitry.

[0373] Figure 23 shows a schematic block diagram of another device collaboration device 14 provided in an embodiment of this application. This device collaboration device 14 may be a first electronic device, a second electronic device, or a server, or it may be a chip, chip system, or processor that supports the first electronic device, second electronic device, or server in implementing the above methods. This device collaboration device 14 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0374] The device coordination unit 14 may include one or more processors 1401, which can also be called processing units, and can implement certain control functions. The processor 1401 can be a general-purpose processor or a special-purpose processor. For example, it can be a baseband processor or central processing unit (CPU), digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic devices, such as discrete gates, transistor logic devices, or discrete hardware components. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control the device coordination unit (e.g., base station, baseband chip, user chip, DU or CU, etc.), execute software programs, and process data from the software programs.

[0375] In an alternative design, the processor 1401 may also store instructions and / or data, which can be executed by the processor 1401 to cause the device coordination device 14 to perform the methods described in the above method embodiments.

[0376] In another alternative design, the device coordination device 14 may include a communication interface 1402 for implementing receiving and transmitting functions. For example, the communication interface 1402 may be a transceiver circuit, interface, interface circuit, or transceiver. The transceiver circuit, interface, interface circuit, or transceiver for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, interface circuit, or transceiver may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.

[0377] Optionally, the device coordination device 14 may include one or more memories 1403, which may store instructions that can be executed on the processor 1401, causing the device coordination device 14 to perform the methods described in the above method embodiments. Optionally, the memories 1403 may also store data. Optionally, the processor 1401 may also store instructions and / or data. The processor 1401 and the memories 1403 may be provided separately or integrated together.

[0378] Figure 24 is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. The aforementioned device collaboration device 13 or device collaboration device 14 can be configured in the electronic device 15. Alternatively, the device collaboration device 13 or device collaboration device 14 itself can be an electronic device, which can be the first electronic device, the second electronic device, or a server in the above method embodiments. The electronic device 15 can perform the actions performed by the first electronic device, the second electronic device, or the server in the above method embodiments. Optionally, for ease of explanation, Figure 24 only shows the main components of the electronic device.

[0379] In one implementation, the electronic device 15 is a first electronic device, configured to send a probe request in response to a first user operation, wherein the first user operation is used to initiate a device collaboration function; receive at least one probe response to the probe request; determine at least one second electronic device based on the at least one probe response, wherein the first electronic device and at least one second electronic device belong to the same communication group, and the accounts corresponding to some or all of the at least one second electronic device are different from the accounts corresponding to the first electronic device, the probe response being used to indicate that the first electronic device and the second electronic device belong to the same communication group; and display a first control and at least one second control, wherein the first control represents the first electronic device and the second control represents the second electronic device.

[0380] In one implementation, the electronic device 15 is a server, configured to receive an acquisition request from a first electronic device, wherein the acquisition request is used to acquire first device information of the first electronic device and second device information of at least one second electronic device, the first device information representing the state and / or attributes of the first electronic device, the second device information representing the state and / or attributes of the second electronic device, the first electronic device and at least one second electronic device belonging to the same communication group, and the account corresponding to some or all of the at least one second electronic device being different from the account corresponding to the first electronic device; the server sends the first device information and the second device information of at least one second electronic device to the first electronic device, wherein the first device information is used to display a first control representing the first electronic device, and the second device information is used to display a second control representing the second electronic device.

[0381] In another implementation, the electronic device 15 is a second electronic device, used to receive a probe request from a first electronic device; if it is determined based on the probe request that the first electronic device belongs to the same communication group as the first electronic device, a probe response is sent to the first electronic device, wherein the probe response is used to indicate that the first electronic device and the second electronic device belong to the same communication group, and at least some of the electronic devices in the communication group have different accounts.

[0382] As shown in Figure 24, the electronic device 15 includes one or more processors 1501, which can support the device coordination method in the method embodiment of the electronic device 15. The processor 1501 can be a general-purpose processor or a special-purpose processor. For example, the processor 1501 can be a central processing unit (CPU), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, such as discrete gates, transistor logic devices, or discrete hardware components.

[0383] The processor 1501 can be used to control the electronic device 15, execute software programs, and process data from the software programs. The electronic device 15 may also include a communication unit 1505 for inputting (receiving) and outputting (transmitting) signals.

[0384] For example, electronic device 15 may be a chip, communication unit 1505 may be the input and / or output circuit of the chip, or communication unit 1505 may be the communication interface of the chip, and the chip may be a component of terminal device or other electronic device.

[0385] For example, electronic device 15 can be a terminal device, communication unit 1505 can be the transceiver of the terminal device, or communication unit 1505 can be the transceiver circuit of the terminal device.

[0386] The electronic device 15 may include one or more memories 1502, which store one or more programs 1504. The programs 1504 can be executed by the processor 1501 to generate instructions 1503, causing the processor 1501 to execute the device collaboration method executed by the first electronic device, the device collaboration method executed by the server, and the device collaboration method executed by the second electronic device as described in the above method embodiments according to the instructions 1503.

[0387] Optionally, the memory 1502 may also store data.

[0388] Optionally, the processor 1501 can also read data stored in the memory 1502, which may be stored at the same memory address as the program 1504, or the data may be stored at a different memory address than the program 1504.

[0389] The processor 1501 and memory 1502 can be configured separately or integrated together, for example, integrated on the system on chip (SOC) of the terminal device.

[0390] This application also provides a computer program product that, when executed by processor 1501, implements the device coordination method of any method embodiment in this application.

[0391] The computer program product can be stored in memory 1502, for example, program 1504. Program 1504 is finally converted into an executable object file that can be executed by processor 1501 after processing such as preprocessing, compilation, assembly and linking.

[0392] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a computer, implements the device coordination method of any method embodiment in this application. The computer program may be a high-level language program or an executable object program.

[0393] The computer-readable storage medium is, for example, memory 1502. Memory 1502 can be volatile memory or non-volatile memory, or memory 1502 can include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as 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), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0394] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process and technical effects of the above-described apparatus and equipment can be referred to the corresponding processes and technical effects in the foregoing method embodiments, and will not be repeated here.

[0395] In the several embodiments provided in this application, the systems, apparatuses, and methods disclosed can be implemented in other ways. For example, some features of the method embodiments described above can be ignored or not performed. The apparatus embodiments described above are merely illustrative; the division of units is only a logical functional division, and in actual implementation, there may be other division methods. Multiple units or components can be combined or integrated into another system. Furthermore, the coupling between units or components can be direct coupling or indirect coupling, including electrical, mechanical, or other forms of connection.

[0396] It should be understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0397] Furthermore, the terms "system" and "network" are often used interchangeably in this paper. The term "and / or" in this paper merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. Additionally, the character " / " in this paper generally indicates that the preceding and following related objects have an "or" relationship.

[0398] In summary, the above are merely preferred embodiments of the technical solutions of this application and are not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

[0399] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A device collaboration method, characterized by, Applied to a first electronic device, the method includes: In response to a first user operation, a probe request is sent, wherein the first user operation is used to initiate a device collaboration function; Receive at least one probe response in response to the probe request; At least one second electronic device is determined based on the at least one detection response, wherein the first electronic device and the at least one second electronic device belong to the same communication group, and the accounts corresponding to some or all of the at least one second electronic device are different from the accounts corresponding to the first electronic device. The detection response is used to indicate that the first electronic device and the second electronic device belong to the same communication group. Display a first control and at least one second control, wherein the first control represents the first electronic device and the second control represents the second electronic device.

2. The method of claim 1, wherein, The detection request carries at least one of the following: the identification information of the first electronic device, the account corresponding to the first electronic device, and the group identification information corresponding to the first electronic device.

3. The method according to any one of claims 1 to 2, characterized in that, The detection response is sent by the second electronic device after determining, based on the detection request and the stored group information corresponding to the second electronic device, that it belongs to the same communication group as the first electronic device.

4. The method according to any one of claims 1 to 3, characterized in that, The detection response carries the group identification information of the communication group and the identification information of the second electronic device.

5. The method of claim 3, wherein, The group information comes from the server and includes at least one of the following: group identification information, group member accounts, and identification information of the electronic devices corresponding to the group member accounts.

6. The method according to any one of claims 1 to 5, characterized in that, After displaying the first control and at least one second control, the method further includes: In response to a second user operation, a processing request is sent to the server, wherein the processing request is used to establish a device collaboration link between the collaborating device and the device to be collaborated with, wherein the collaborating device and the device to be collaborated with are electronic devices among the first electronic device and the at least one second electronic device, and the second user operation is used to associate the collaborating device and the device to be collaborated with.

7. The method according to claim 6, characterized in that, The collaborative device is the first electronic device. After responding to the second user's operation and sending a processing request to the server, the method further includes: Receive a verification request from the device to be collaborated with, wherein the verification request is used to determine whether the device to be collaborated with is a legitimate device, and the verification request is sent by the device to be collaborated with based on a control command from the server, and the control command is sent by the server based on the processing request; If the device to be collaborated with is determined to be a legitimate device based on the verification request, a verification response is sent to the device to be collaborated with, the verification response being used to determine whether the first electronic device is a legitimate device.

8. The method of claim 7, wherein, The step of sending a verification response to the device to be collaborated with when the device is determined to be a legitimate device based on the verification request includes: The verification request is parsed to obtain the identification information of the device to be coordinated and the first encryption information. The first encryption information is obtained by encrypting the identification information of the device to be coordinated based on the group identification key corresponding to the device to be coordinated and the user identification key corresponding to the device to be coordinated. Based on the group identifier key and the user identifier key corresponding to the first electronic device, the identifier information of the device to be coordinated is encrypted to obtain the second encrypted information; If the first encrypted information and the second encrypted information match, the device to be cooperated with is determined to be a legitimate device; The verification response is sent to the device to be coordinated. The verification response carries the identification information of the first electronic device and the third encryption information. The third encryption information is obtained by encrypting the identification information of the first electronic device based on the group identification key and the user identification key corresponding to the first electronic device.

9. The method of claim 6, wherein, The device to be coordinated is the first electronic device. After responding to the second user's operation and sending a processing request to the server, the method further includes: Receive control instructions from the server, wherein the control instructions are used to control the first electronic device to establish a... In the aforementioned device collaboration link, the control command is sent by the server based on the processing request; Based on the control command, a verification request is sent to the collaborative device, wherein the verification request is used to determine whether the first electronic device is a legitimate device; If the collaborative device is determined to be a legitimate device based on the verification response from the collaborative device, a device collaboration link is established, wherein the verification response is sent by the collaborative device after determining that the first electronic device is a legitimate device.

10. The method according to claim 9, characterized in that, The step of establishing the device collaboration link when the collaborative device is determined to be a legitimate device based on the verification response from the collaborative device includes: The verification response is parsed to obtain the identification information and third encryption information of the collaborative device. The third encryption information is obtained by encrypting the identification information of the collaborative device based on the group identification key and the user identification key corresponding to the collaborative device. Based on the group identifier key and the user identifier key corresponding to the first electronic device, the identifier information of the collaborative device is encrypted to obtain the fourth encrypted information; If the third encryption information and the fourth encryption information match, the collaborative device is determined to be a legitimate device; Establish the device collaboration link.

11. The method of claim 1, wherein, The display of the first control and at least one second control includes: Obtain first device information of the first electronic device and second device information of the at least one second electronic device, wherein the first device information characterizes the state and / or attributes of the first electronic device, and the second device information characterizes the state and / or attributes of the second electronic device; Based on the first device information, the first control is displayed; The at least one second control is displayed based on the second device information of the at least one second electronic device.

12. The method according to claim 11, characterized in that, The step of obtaining the first device information of the first electronic device and the second device information of the at least one second electronic device includes: Send an acquisition request to the server, wherein the acquisition request is used to acquire the first device information and the second device information of the at least one second electronic device; The system receives the first device information from the server and the second device information from the at least one second electronic device.

13. A device coordination method, characterized in that, Applied to a server, the method includes: A request is received from a first electronic device, wherein the request is used to obtain first device information of the first electronic device and second device information of at least one second electronic device, the first device information characterizing the state and / or attributes of the first electronic device, the second device information characterizing the state and / or attributes of the second electronic device, the first electronic device and the at least one second electronic device belonging to the same communication group, and the accounts corresponding to some or all of the at least one second electronic device being different from the accounts corresponding to the first electronic device. Send the first device information and the second device information of the at least one second electronic device to the first electronic device, wherein the first device information is used to display a first control representing the first electronic device, and the second device information is used to display a second control representing the second electronic device.

14. The method according to claim 13, characterized in that, After sending the first device information and the second device information of the at least one second electronic device to the first electronic device, the method further includes: Receive a processing request from the first electronic device, wherein the processing request is used to establish a device collaboration link between the collaborating device and the device to be collaborated with; Based on the processing request, a control command is sent to the device to be coordinated, wherein the control command is used to control the device to be coordinated to establish the device coordination link.

15. The method according to claim 13, characterized in that, Before receiving the acquisition request from the first electronic device, the method further includes: Group information of the communication group is sent to multiple electronic devices in the communication group, wherein the group information is used by the electronic devices to determine whether they are in the same communication group as other electronic devices, and the multiple electronic devices include the first electronic device and the at least one second electronic device.

16. The method according to claim 15, characterized in that, The group information includes at least one of the following: group identification information, group member accounts, and identification information of the electronic devices corresponding to the group member accounts.

17. A device coordination method, characterized in that, Applied to a second electronic device, the method includes: Receive a probe request from the first electronic device; If, based on the probe request, it is determined that the first electronic device belongs to the same communication group as the first electronic device, a probe response is sent to the first electronic device, wherein the probe response is used to indicate that the first electronic device and the second electronic device belong to the same communication group, and at least some of the electronic devices in the communication group have different accounts.

18. The method according to claim 17, characterized in that, The detection request carries at least one of the following: the identification information of the first electronic device, the account corresponding to the first electronic device, and the group identification information corresponding to the first electronic device.

19. The method according to any one of claims 17-18, characterized in that, The step of sending a probe response to the first electronic device when it is determined, based on the probe request, that the device belongs to the same communication group as the first electronic device includes: Based on the detection request and the stored group information corresponding to the second electronic device, determine whether the first electronic device and the second electronic device belong to the same communication group; If the first electronic device and the second electronic device belong to the same communication group, the detection response is sent to the first electronic device.

20. The method according to any one of claims 17 to 19, characterized in that, The detection response carries the group identification information of the communication group and the identification information of the second electronic device.

21. The method according to claim 19, characterized in that, The group information can be obtained through the following methods: The system receives group information from a server, the group information including at least one of group identification information, group member accounts, and identification information of electronic devices corresponding to the group member accounts.

22. The method according to any one of claims 17 to 21, characterized in that, The second electronic device is a collaborative device. After determining, based on the detection request, that it belongs to the same communication group as the first electronic device, and sending a detection response to the first electronic device, the method further includes: Receive a verification request from the device to be collaborated with, wherein the verification request is used to determine whether the device to be collaborated with is a legitimate device, and the verification request is sent by the device to be collaborated with based on control instructions from the server; If the device to be collaborated with is determined to be a legitimate device based on the verification request, a verification response is sent to the device to be collaborated with, the verification response being used to determine whether the second electronic device is a legitimate device.

23. The method according to claim 22, characterized in that, The step of sending a verification response to the device to be collaborated with when the device is determined to be a legitimate device based on the verification request includes: The verification request is parsed to obtain the identification information of the device to be coordinated and the first encryption information, wherein the first encryption information is obtained by encrypting the identification information of the device to be coordinated based on the group identification key corresponding to the device to be coordinated and the user identification key corresponding to the device to be coordinated; Based on the group identifier key and the user identifier key corresponding to the second electronic device, the identifier information of the device to be coordinated is encrypted to obtain the second encrypted information; If the first encrypted information and the second encrypted information match, the device to be cooperated with is determined to be a legitimate device; The verification response is sent to the device to be coordinated. The verification response carries the identification information of the second electronic device and the third encryption information. The third encryption information is obtained by encrypting the identification information of the second electronic device based on the group identification key and the user identification key corresponding to the second electronic device.

24. The method according to any one of claims 17 to 21, characterized in that, The second electronic device is a device to be coordinated. After determining that it belongs to the same communication group as the first electronic device based on the detection request, the method further includes: Receive control instructions from the server, wherein the control instructions are used to control the establishment of a device collaboration link between the second electronic device and the collaborating device; Based on the control command, a verification request is sent to the collaborative device, wherein the verification request is used to determine whether the second electronic device is a legitimate device; If, based on the verification response from the collaborating device, the collaborating device is determined to be a legitimate device, a device collaboration link is established, wherein the verification response is the response from the collaborating device when it determines that the second electronic device is a legitimate device. It was sent below.

25. The method according to claim 24, characterized in that, The step of establishing the device collaboration link when the collaborative device is determined to be a legitimate device based on the verification response from the collaborative device includes: The verification response is parsed to obtain the identification information and third encryption information of the collaborative device. The third encryption information is obtained by encrypting the identification information of the collaborative device based on the group identification key and the user identification key corresponding to the collaborative device. Based on the group identifier key and the user identifier key corresponding to the second electronic device, the identifier information of the collaborative device is encrypted to obtain the fourth encrypted information; If the third encryption information and the fourth encryption information match, the collaborative device is determined to be a legitimate device; Establish the device collaboration link.

26. A device for coordinating equipment, characterized in that, It includes units for performing the steps of the method as described in any one of claims 1 to 12, or units for performing the steps of the method as described in any one of claims 13 to 16, or units for performing the steps of the method as described in any one of claims 17 to 25.

27. A device for coordinating equipment, characterized in that, include: A processor coupled to a memory for storing a program or instructions which, when executed by the processor, cause the device to perform the method of any one of claims 1 to 12, 13 to 16, or any one of claims 17 to 25.

28. An electronic device, characterized in that, include: A memory, one or more processors, and one or more programs; wherein the one or more programs are stored in the memory; When the one or more processors execute the one or more programs, they cause the electronic device to perform the method of any one of claims 1 to 12, any one of claims 13 to 16, or any one of claims 17 to 25.

29. A chip, characterized in that, include: A processor for retrieving and running a computer program from memory, causing an electronic device having the chip mounted to perform the method of any one of claims 1 to 12, 13 to 16, or any one of 17 to 25.

30. A computer-readable storage medium storing computer programs or instructions thereon, characterized in that, When the computer program or instructions are executed, they cause the computer to perform the method as described in any one of claims 1 to 12, 13 to 16, or 17 to 25.

31. A computer program product, characterized in that, It includes computer program instructions that cause the computer to perform the method as claimed in any one of claims 1 to 12, 13 to 16, or 17 to 25.

Images