A method for controlling inter-device service flow and an electronic device

Abstract

A control method of inter-device service flow transfer and an electronic device, which relate to the technical field of terminals. The method is applied to a first electronic device and includes: displaying a first interface, the first interface including a first device identifier and at least two associated device identifiers. Based on a first operation of the first interface, displaying a first service identifier around the first source device identifier, the first service identifier indicating a first service provided by the first source device. In response to an operation of dragging the first service identifier to a first target device identifier, displaying the first service identifier around the first target device identifier. In response to an operation of dragging the first service identifier around the first target device identifier to a second target device identifier, displaying the first service identifier around the second target device identifier and canceling the display of the first service identifier around the first target device identifier. In this way, the first electronic device can control the quick and automatic switching and flow transfer of the first service among multiple target devices.

Description

[0001] This application is a divisional application. The original application has the application number 202311819078.1 and the original application date is December 26, 2023. The entire contents of the original application are incorporated herein by reference.

[0002] This application claims priority to Chinese Patent Application No. 202311466653.4, filed on November 3, 2023, entitled "A Control Method and Electronic Device for Multi-Device Collaboration", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of terminal technology, and in particular to a control method and electronic device for inter-device service transfer. Background Technology

[0004] Electronic devices come in a variety of forms. For example, they can include mobile phones, tablets, and laptops. Each type of electronic device has its unique advantages. For instance, mobile phones have excellent camera capabilities, while laptops come with accessories such as mice and keyboards.

[0005] In existing technologies, electronic devices can share each other's advantageous services to achieve service transfer (also known as collaboration) between devices. For example, tablets, laptops, and other electronic devices can share the screen of a mobile phone, thereby enabling the screen transfer from the mobile phone to the tablet, laptop, and other electronic devices.

[0006] As electronic devices become increasingly diverse in form and each type of electronic device offers more and more advantageous services, how to achieve flexible control over the flow of services has become an urgent problem to be solved. Summary of the Invention

[0007] This application provides a control method and electronic device for inter-device service transfer, which can realize flexible control of the transfer of advantageous services provided by various devices in the local machine.

[0008] To achieve the above objectives, this application adopts the following technical solution: In a first aspect, this application provides a control method for inter-device service transfer, applied to a first electronic device (i.e., a control device, such as a mobile phone). The method involves displaying a first interface (i.e., an interface including a control center), which includes a first device identifier and at least two associated device identifiers. The first device identifier indicates the first electronic device, and each associated device identifier indicates an associated device. The first device and the associated devices are devices joined in the same trust ring. In response to a first trigger operation based on the first interface, service identifiers of advantageous services provided by the first source device are displayed around the first source device identifier, such as the first service identifier of a first service (hereinafter referred to as screen sharing, keyboard and mouse sharing, etc.). The first source device identifier indicates the first source device. In response to an operation of dragging a first service identifier around the first source device identifier to a first target device identifier, the first service identifier and the first source device identifier are displayed around the first target device identifier, and the first target device identifier indicates the first target device. When the first service identifier and the first source device identifier are displayed around the target device identifier, the first service provided by the first source device is transferred to the target device. In other words, in response to the user dragging the first service identifier from next to the first source device identifier to next to the first target device identifier in the first interface, the first service can be quickly transferred from the first source device to the first target device.

[0009] Furthermore, in response to the operation of dragging a first service identifier around a first target device identifier to a second target device identifier, the first service identifier and the first source device identifier are displayed around the second target device identifier, but the display of the first service identifier and the first source device identifier around the first target device identifier is canceled, and the second target device identifier indicates the second target device. When the display of the first service identifier and the first source device identifier around the target device identifier is canceled, the first service provided by the first source device ends its flow to the target device. That is, after the first service is flowed to the first target device, in response to the user continuing to drag the first service identifier from next to the first target device identifier to next to the second target device identifier, the first electronic device can switch the flow of the first service from the first target device to the second target device. In this way, the first electronic device does not need to first end the flow to the first target device based on the user's operation to end the flow, and then switch the flow to the second target device based on the user's operation to flow the first service to the second target device. This allows for fast and automatic switching of the first service between multiple target devices.

[0010] The aforementioned first source device identifier, first target device identifier, and second target device identifier are three device identifiers selected from the first device identifier and at least two associated device identifiers. The first source device identifier, first target device identifier, and second target device identifier are all different from each other. In other words, the first source device, the first target device, and the second target device are three different devices within the same trust ring. Therefore, the first electronic device can control the flow of services provided by any electronic device within the trust ring to other electronic devices.

[0011] In one possible design of the first aspect, the first source device and the first target device are two of at least two associated devices indicated by at least two associated device identifiers. That is, neither the first source device nor the first target device is the first electronic device. Therefore, the first electronic device can control the flow of services between other electronic devices in the trust loop besides the first electronic device.

[0012] In one possible design of the first aspect, the above-mentioned operation of dragging a first service identifier around a first target device identifier to a second target device identifier, displaying a first service identifier and a first source device identifier around a second target device identifier, in response to the operation of dragging a first service identifier around a first target device identifier to a second target device identifier, includes: if the first service belongs to a first type of service, in response to the operation of dragging a first service identifier around a first target device identifier to a second target device identifier, displaying a first service identifier and a first source device identifier around a second target device identifier.

[0013] The first type of service is one that can only be routed to one target device at a time. Therefore, if a user drags the first service identifier from next to the first target device identifier to next to the second target device identifier when the first service has already been routed to the first target device, the service can only be switched to the second target device; it cannot be routed further to the second target device. Thus, the user's intention can be predicted as: switching the first service from being routed to the first target device to being routed to the second target device. Based on this intention, the first electronic device displays the first service identifier and the first source device identifier around the second target device identifier, and then removes the first service identifier and the first source device identifier from the area surrounding the first target device identifier. In this way, the response of the first electronic device can more accurately match the user's intention.

[0014] Furthermore, if the first service is a type II service—a service that can be simultaneously transferred to multiple target devices—then, if the user drags the first service identifier from next to the first target device identifier to next to the second target device identifier after the first service has already been transferred to the first target device, it could mean either the user wants to switch the first service to the second target device or to further transfer the first service to the second target device. Therefore, the user's intention is difficult to predict accurately. Thus, if the first service is a type II service, in response to the user dragging the first service identifier around the first target device identifier to the second target device identifier (i.e., dragging it from next to the first target device identifier to next to the second target device identifier), the first electronic device will still display the first service identifier and the first source device identifier around the first target device identifier; that is, it will not remove the first service identifier and the first source device identifier from the first target device identifier. Furthermore, the first electronic device will not display the first service identifier and the first source device identifier around the second target device identifier. This way, the first electronic device can avoid response errors.

[0015] In one possible design of the first aspect, the method further includes: in response to an operation of dragging a first service identifier around a first source device identifier to a first target device identifier, canceling the display of the first service identifier around the first source device identifier. This ensures that the first electronic device cancels the display of the first service identifier around the first source device after the first service has been transferred, avoiding interference with the user's judgment. Furthermore, after displaying the first service identifier and the first source device identifier around the second target device identifier, the method further includes: in response to a first trigger operation based on the first interface, displaying the first service identifier around the first source device identifier, i.e., re-displaying the service provided by the first source device. In response to an operation of dragging the first service identifier around the first source device identifier to the first target device identifier again, displaying the first service identifier and the first source device identifier around the first target device identifier, and canceling the display of the first service identifier around the second target device identifier and the first source device identifier. That is, even when the first service has already been transferred to the second target device, in response to the user's operation of dragging the first service identifier around the first source device identifier to the first target device identifier again, the first electronic device can also switch the first service from being transferred to the second target device to being transferred back to the first target device. This provides a way to quickly and automatically switch the first service between multiple target devices, without requiring the first electronic device to first end the flow to the second target device based on the user's operation to end the flow, and then switch the flow to the first target device based on the user's operation to flow the first service to the first target device.

[0016] In one possible design of the first aspect, the above-mentioned response to the operation of dragging the first service identifier around the first source device identifier to the first target device identifier again, displaying the first service identifier and the first source device identifier around the first target device identifier, and de-displaying the first service identifier and the first source device identifier around the second target device identifier, includes: if the first service belongs to a first type of service, in response to the operation of dragging the first service identifier around the first source device identifier to the first target device identifier again, displaying the first service identifier and the first source device identifier around the first target device identifier, and de-displaying the first service identifier and the first source device identifier around the second target device identifier.

[0017] If, after the first service has already been transferred to the second target device, the user is detected dragging the first service identifier from next to the first source device identifier to next to the first target device identifier again, it is generally assumed that the user's intention is to further transfer the first service to the first target device. However, since the first type of service can only be transferred to one target device at a time, the user's intention can only be assumed to be: to switch the first service from being transferred to the second target device to being transferred to the first target device. In response to this intention, the first electronic device displays the first service identifier and the first source device identifier around the first target device identifier, and removes the display of the first service identifier and the first source device identifier around the second target device identifier. This achieves the switch from transferring the first service from the second target device to transferring it to the first target device. In this way, the response of the first electronic device conforms to the characteristics of the service.

[0018] In one possible design of the first aspect, the method further includes: if the first service belongs to the second type of service, in response to the operation of dragging the first service identifier around the first source device identifier to the first target device identifier again, displaying the first service identifier and the first source device identifier around the first target device identifier, and maintaining the display of the first service identifier and the first source device identifier around the second target device identifier.

[0019] As analyzed earlier, if the user drags the first service identifier from the first source device identifier to the first target device identifier again after the first service has already been transferred to the second target device, it is generally assumed that the user's intention is to further transfer the first service to the first target device. Furthermore, the second type of service is one that can be transferred to multiple target devices simultaneously, meaning the first service can also be transferred to multiple target devices. Therefore, the user's intention can be determined as: to further transfer the first service to the first target device. In response to this intention, the first electronic device can maintain the first service identifier and the first source device identifier around the second target device identifier, and further display the first service identifier and the first source device identifier around the first target device identifier. This allows the first service to be further transferred to the first target device even after it has been transferred to the second target device. In this way, the response of the first electronic device can take into account both the user's intention and the characteristics of the service.

[0020] In one possible design of the first aspect, displaying a first service identifier around a first source device identifier in response to a first trigger operation based on a first interface includes: displaying at least one target service identifier around the first source device identifier in response to the first trigger operation based on the first interface, each target service identifier indicating a service provided by the first source device, and the at least one target service identifier including the first service identifier. That is, the first trigger operation can trigger the first electronic device to display service identifiers of all services provided by the first source device. Accordingly, before displaying the first service identifier and the first source device identifier around the first target device identifier in response to the operation of dragging the first service identifier around the first source device identifier to the first target device identifier, the method further includes: in response to a second trigger operation on the first service identifier around the first source device, canceling the display of service identifiers other than the first service identifier among the at least one target service identifiers, and displaying a prompt to drag the first service identifier to the target device identifier to realize service flow.

[0021] In this way, when users are unfamiliar with the service flow operation, such as not knowing that they need to drag the first service identifier to the target device identifier to complete the service flow, the user can perform a second trigger operation on the first service identifier, such as clicking, to trigger the first electronic device to prompt the service flow operation, such as dragging the first service identifier to the target device identifier to complete the service flow. This can guide the user to complete the service flow operation.

[0022] In one possible design of the first aspect, the first service includes a first sub-service and a second sub-service, and the first service identifier includes a first sub-service identifier indicating the first sub-service and a second sub-service identifier indicating the second sub-service. Displaying the first service identifier and the first source device identifier around the first target device identifier in response to an operation of dragging the first service identifier around the first source device identifier to the first target device identifier includes: displaying the first sub-service identifier and the first source device identifier around the first target device identifier in response to an operation of dragging the first sub-service identifier around the first source device identifier to the first target device identifier.

[0023] In other words, for a first service that includes multiple sub-services, the first electronic device can complete the flow of the corresponding sub-services based on the user's dragging and dropping of the sub-service identifier.

[0024] In one possible design of the first aspect, the first service includes a first sub-service and a second sub-service. After displaying the first service identifier and the first source device identifier around the first target device identifier in response to an operation of dragging a first service identifier around the first source device identifier to the first target device identifier, the method further includes: displaying a first sub-service identifier and the first source device identifier around the first target device identifier in response to a first message, the first message instructing the first target device to select the first sub-service, and the first sub-service identifier indicating the first sub-service.

[0025] In response to the operation of dragging a first service identifier around a first source device identifier to a first target device identifier, the first electronic device first sends a notification of first service transfer to the first target device. In response to the notification of first service transfer, the first target device can display options for a first sub-service and a second sub-service, allowing the user to select the sub-service to be transferred. In response to the user's selection of the first sub-service option, the first target device can send a first message to the first electronic device, indicating that the first target device has selected the first sub-service. In this way, the first electronic device can clearly identify that the specific service to be transferred is the first sub-service, and therefore displays the first sub-service identifier and the first source device identifier around the first target device identifier.

[0026] In one possible design of the first aspect, after displaying the first service identifier and the first source device identifier around the second target device identifier, the method further includes: if the second electronic device plays audio via headphones, displaying a second interface, the second interface including the first device identifier, at least two associated device identifiers, and an identifier for the headphones, the identifier for the headphones being displayed around the identifier of the second electronic device, the second electronic device being one of the at least two associated devices indicated by the first electronic device and the at least two associated device identifiers. If the identifier for the headphones is displayed around the identifier of any electronic device, the audio from that electronic device is played via headphones.

[0027] Furthermore, in response to dragging the headphone icon to the third target device icon, the headphone icon is displayed around the third target device icon, but the headphone icon displayed around the second electronic device is deselected. The third target device icon indicates the third target device; when the headphone icon around the second electronic device icon is deselected, the audio from the second electronic device is not played through the headphones. The third target device icon is one of the following device icons: the first device icon and at least two associated device icons, excluding the second electronic device icon. Thus, by dragging the headphone icon, the user can trigger the first electronic device to switch between playing video from different devices, such as switching from playing audio from the second electronic device to playing audio from the third target device.

[0028] In one possible design of the first aspect, the first service is a service for sharing a keyboard and / or mouse, the first source device includes a keyboard and / or mouse, and the first target device includes a keyboard and / or mouse. The method further includes: in response to an operation of dragging a first service identifier surrounding a first source device identifier to a first target device identifier, displaying a first service identifier and a first target device identifier around the first source device identifier; and, when the first service identifier and the first target device identifier are displayed around the first source device identifier, the first service provided by the first target device is transferred to the first source device.

[0029] In other words, dragging the shared keyboard and / or mouse service identifier from the first source device identifier to the first target device identifier not only triggers the shared keyboard and / or mouse service provided by the first source device to flow to the first target device, allowing the first target device to use the keyboard and / or mouse of the first source device; but also triggers the shared keyboard and / or mouse service provided by the first target device to flow to the first source device, allowing the first source device to use the keyboard and / or mouse of the first target device. This allows for quick and easy switching between shared keyboard and / or mouse services between two devices.

[0030] In one possible design of the first aspect, after displaying the first service identifier and the source device identifier around the second target device identifier, the method further includes: based on a third trigger operation of the first interface, displaying a second service identifier and a third service identifier around the second source device identifier, wherein the second service identifier indicates a second service, the third service identifier indicates a third service, and the second and third services are two services provided by the second source device indicated by the second source device identifier. In response to a sequential click operation on the second service identifier and the third service identifier, such as clicking the second service identifier first and then quickly clicking the third service identifier, the second service identifier and the third service identifier are merged into a first control. In response to an operation of dragging the first control to the fourth target device identifier, the second service identifier and the third service identifier are displayed around the fourth target device identifier, and the second source device identifier is also present around the second service identifier and the third service identifier. The fourth target device identifier indicates a fourth target device, and the second source device identifier and the fourth target device identifier are two of the first device identifier and at least two associated device identifiers, wherein the second source device identifier and the fourth target device identifier are different.

[0031] If any service identifier and a second source device identifier are displayed around the fourth target device identifier, the service indicated by any service identifier provided by the second source device is transferred to the fourth target device. Conversely, if a second service identifier and a third service identifier are displayed around the fourth target device identifier, and the second source device identifier is also present around the second and third service identifiers, it indicates that both the second and third services provided by the second source device are transferred to the fourth target device.

[0032] In other words, the first electronic device can merge the second and third service identifiers into a first control, and then, in response to the user's drag operation on the first control, simultaneously transfer the second and third services from the second source device to the fourth target device. This allows for the simultaneous transfer of multiple services, improving the efficiency of human-computer interaction.

[0033] In one possible design approach of the first aspect, the first triggering operation includes a triggering operation on the first source device identifier in the first interface, such as a click operation.

[0034] Alternatively, the first interface may also include a second control. For example, in the first interface, a first electronic device and at least two candidate devices are located on the same ring, with the user identifier of a first user at the center of the ring. The second control may be this user identifier. The first user refers to the user indicated by the same user account logged into by the first electronic device and at least two candidate devices. The first triggering operation includes triggering the second control in the first interface. Specifically, in response to the triggering operation of the second control, the first electronic device may display service identifiers of services provided by all electronic devices in the trust ring, thereby displaying a first service identifier around the first source device identifier.

[0035] In one possible design of the first aspect, where a third electronic device is connected to a printer, at least two associated device identifiers include the printer's identifier. The third electronic device is one of the at least two associated devices indicated by the first electronic device and the at least two associated device identifiers.

[0036] In other words, printers can join the trust ring by establishing a connection with other devices in the trust ring. This allows printers from other manufacturers to join the trust ring so that devices in the trust ring can use the printing service.

[0037] Secondly, this application provides a control method for inter-device service transfer (corresponding to transfer form three below), applied to a first electronic device. The method includes: displaying a first interface, the first interface including a first device identifier and at least two associated device identifiers, the at least two associated device identifiers including a first associated device identifier and a second associated device identifier, the first device identifier indicating a first electronic device, the first associated device identifier indicating a first associated device, and the second associated device identifier indicating a second associated device. In response to a first trigger operation based on the first interface, a first service identifier is displayed around the first associated device identifier, the first service identifier indicating a first service provided by the first associated device. In response to an operation of dragging the first service identifier to the second associated device identifier, the first service identifier and the first associated device identifier are displayed around the second associated device identifier, and the first service provided by the first associated device is transferred to the second associated device.

[0038] It is evident that the first electronic device can control the flow of services between other electronic devices (i.e., the first associated device and the second associated device) in the trust ring, excluding the first electronic device itself.

[0039] In one possible design approach of the second aspect, the method further includes: in response to the operation of dragging the first service identifier to the second associated device identifier, canceling the display of the first service identifier surrounding the first associated device identifier. In this way, the first electronic device can ensure that after the first service is transferred, the first service identifier surrounding the first source device is canceled, avoiding interference with the user's judgment.

[0040] After displaying the first service identifier and the first associated device identifier around the second associated device identifier, the method further includes: displaying the first service identifier around the first associated device identifier in response to a first trigger operation based on the first interface; displaying the first service identifier and the first associated device identifier around the first target device identifier in response to an operation of dragging the first service identifier to the first target device identifier; maintaining the display of the first service identifier and the first associated device identifier around the second associated device identifier; and transferring the first service provided by the first associated device to the second associated device and the first target device. The first target device identifier is one of the first device identifier and at least two associated device identifiers, excluding the first associated device identifier and the second associated device identifier, and the first target device identifier indicates the first target device.

[0041] If, after the first service has already been transferred to the second associated device, the user is detected dragging the first service identifier from next to the first associated device identifier to next to the first target device identifier again, it is generally assumed that the user's intention is to further transfer the first service to the first target device. Therefore, the first electronic device can further transfer the first service to the first target device to match the user's intention.

[0042] In one possible design approach of the second aspect, in response to the operation of dragging a first service identifier to a first target device identifier, displaying the first service identifier and a first associated device identifier around the first target device identifier, and maintaining the display of the first service identifier and the first associated device identifier around a second associated device identifier, includes: if the first service belongs to a second type of service, in response to the operation of dragging the first service identifier to the first target device identifier, displaying the first service identifier and the first associated device identifier around the first target device identifier, and maintaining the display of the first service identifier and the first associated device identifier around the second associated device identifier. Wherein, the second type of service is a service that can be transferred to multiple devices simultaneously.

[0043] As analyzed earlier, if the user drags the first service identifier from next to the first associated device identifier to next to the first target device identifier after the first service has already been transferred to the second associated device, it is generally assumed that the user's intention is to further transfer the first service to the first target device. Furthermore, the second type of service is one that can be transferred to multiple devices simultaneously, meaning the first service can be transferred to multiple devices. Therefore, the user's intention can be determined as: to further transfer the first service to the first target device. In response to this intention, the first electronic device can maintain the first service identifier and the first associated device identifier around the second associated device identifier, and further display the first service identifier and the first associated device identifier around the first target device identifier. This allows the first service to be further transferred to the first target device after it has been transferred to the second associated device. In this way, the response of the first electronic device can take into account both the user's intention and the characteristics of the service.

[0044] In one possible design approach of the second aspect, the method further includes: if the first service belongs to a first type of service, in response to the operation of dragging the first service identifier to the first target device identifier, displaying the first service identifier and the first associated device identifier around the first target device identifier, canceling the display of the first service identifier and the first associated device identifier around the second associated device identifier, transferring the first service provided by the first associated device to the first target device, and transferring the first service provided by the first associated device to the first target device after the first service ends. Here, the first type of service is a service that can only be transferred to one device at a time.

[0045] If, after the first service has already been transferred to the second associated device, the user is detected dragging the first service identifier from next to the first associated device identifier to next to the first target device identifier, it is generally assumed that the user's intention is to further transfer the first service to the first target device. However, since the first type of service can only be transferred to one device at a time, the user's intention can only be assumed to be: to switch the first service from being transferred to the second associated device to being transferred to the first target device. In response to this intention, the first electronic device displays the first service identifier and the first associated device identifier around the first target device identifier, and removes the display of the first service identifier and the first associated device identifier around the second associated device identifier. This achieves the switch of the first service from being transferred to the second associated device to being transferred to the first target device. In this way, the response of the first electronic device conforms to the characteristics of the service.

[0046] In one possible design of the second aspect, displaying a first service identifier around a first associated device identifier in response to a first trigger operation based on a first interface includes: displaying at least one target service identifier around the first associated device identifier in response to the first trigger operation based on the first interface, each target service identifier indicating a service provided by the first associated device, and the first service identifier being included among the at least one target service identifier. Before displaying the first service identifier and the first associated device identifier around the second associated device identifier in response to an operation of dragging the first service identifier to a second associated device identifier, the method further includes: de-displaying service identifiers other than the first service identifier among the at least one target service identifiers in response to a second trigger operation on the first service identifier, and displaying a prompt to drag the first service identifier to another device identifier to achieve service transfer.

[0047] In this way, when users are unfamiliar with the service flow operation, such as not knowing that they need to drag the first service identifier to the target device identifier to complete the service flow, the user can perform a second trigger operation on the first service identifier, such as clicking, to trigger the first electronic device to prompt the service flow operation, such as dragging the first service identifier to another device identifier to complete the service flow. This can guide the user to complete the service flow operation.

[0048] In one possible design of the second aspect, after displaying the first service identifier and the first associated device identifier around the second associated device identifier, the method further includes: when the second electronic device plays audio through headphones, displaying a second interface, the second interface including the first device identifier, at least two associated device identifiers, and a headphone identifier, the headphone identifier being displayed around the identifier of the second electronic device, the second electronic device being one of at least two associated devices indicated by the first electronic device and the at least two associated device identifiers. In response to an operation of dragging the headphone identifier to the second target device identifier, the headphone identifier is displayed around the second target device identifier, the headphone identifier is deselected from the display around the second electronic device, the second target device identifier indicates a second target device, the second target device plays audio through headphones, and the second electronic device does not play audio through headphones. Wherein, the second target device identifier is one of the device identifiers other than the identifier of the second electronic device among the first device identifier and the at least two associated device identifiers.

[0049] In this way, users can trigger the first electronic device to switch the playback of videos from different devices by dragging the headphone icon, such as switching from playing audio from the second electronic device to playing audio from the second target device.

[0050] In one possible design of the second aspect, the first service is a service for sharing a keyboard and / or mouse, the first associated device includes a keyboard and / or mouse, and the second associated device includes a keyboard and / or mouse. The method further includes: in response to an operation of dragging a first service identifier to a second associated device identifier, displaying a first service identifier and a second associated device identifier around the first associated device identifier, and transferring the first service provided by the second associated device to the first associated device.

[0051] In other words, dragging the shared keyboard and / or mouse service identifier from the first associated device identifier to the second associated device identifier not only triggers the shared keyboard and / or mouse service provided by the first associated device to flow to the second associated device, allowing the second associated device to use the keyboard and / or mouse of the first associated device; but also triggers the shared keyboard and / or mouse service provided by the second associated device to flow to the first associated device, allowing the first associated device to use the keyboard and / or mouse of the second associated device. This allows for quick and easy switching between the shared keyboard and / or mouse services of two devices.

[0052] In one possible design of the second aspect, after displaying the first service identifier and the first associated device identifier around the second associated device identifier, the method further includes: in response to a third trigger operation based on the first interface, displaying the second service identifier and the third service identifier around the identifier of the third electronic device, the second service identifier indicating a second service, the third service identifier indicating a third service, the second service and the third service being two services provided by the third electronic device, the third electronic device being one of at least two associated devices indicated by the first electronic device and at least two associated device identifiers. In response to a selection operation of the second service identifier and the third service identifier, merging the second service identifier and the third service identifier into a first control. In response to an operation of dragging the first control to the third target device identifier, displaying the second service identifier and the third service identifier around the third target device identifier, and the second service identifier and the third service identifier also including the identifier of the third electronic device, the third target device identifier indicating the third target device, the second service and the third service provided by the third electronic device flowing to the third target device, the third target device identifier being one of the device identifiers other than the identifier of the third electronic device among the first device identifier and at least two associated device identifiers.

[0053] In other words, the first electronic device can merge the second and third service identifiers into a first control, and then, in response to the user's drag operation on the first control, simultaneously transfer the second and third services from the third electronic device to the third target device. This allows for the simultaneous transfer of multiple services, improving the efficiency of human-computer interaction.

[0054] For the effects not detailed in the second aspect and its possible design methods mentioned above, please refer to the explanation in the first aspect and its possible design methods, which will not be repeated here.

[0055] Thirdly, this application provides a communication system including a first electronic device and at least two associated devices. The first electronic device is configured to display a first interface, which includes a first device identifier and at least two associated device identifiers. The first device identifier indicates the first electronic device, and each associated device identifier indicates an associated device. A fourth electronic device is configured to display a third interface, which is one of the at least two associated devices. The third interface includes a first device identifier and at least two associated device identifiers. The first electronic device is configured to display a first service identifier around a first source device identifier in the first interface in response to a first trigger operation based on the first interface. The first source device identifier indicates a first source device, and the first service identifier indicates a first service provided by the first source device. In response to an operation of dragging the first service identifier around the first source device identifier in the first interface to a first target device identifier: the first electronic device is configured to display the first service identifier and the first source device identifier around the first target device identifier in the first interface, and the fourth electronic device is configured to display the first service identifier and the first source device identifier around the first target device identifier in the third interface. The first target device identifier indicates a first target device, and the first service provided by the first source device flows to the first target device. In response to the operation of dragging a first service identifier around a first source device identifier in a first interface to a first target device identifier: a first electronic device is configured to display the first service identifier and the first source device identifier around a second target device identifier in the first interface, but de-display the first service identifier and the first source device identifier around the first target device identifier in the first interface; a fourth electronic device is configured to display the first service identifier and the first source device identifier around a second target device identifier in a third interface, but de-display the first service identifier and the first source device identifier around the first target device identifier in the third interface; the second target device identifier indicates the second target device; the first service provided by the first source device flows to the second target device; the first service provided by the first source device ends and flows back to the first target device. Wherein, the first source device identifier, the first target device identifier, and the second target device identifier are three device identifiers among the first device identifier and at least two associated device identifiers, and the first source device identifier, the first target device identifier, and the second target device identifier are different from each other.

[0056] Fourthly, this application also provides an electronic device including a display screen, a memory, and one or more processors. The display screen, memory, and processors are coupled. The memory stores computer program code, including computer instructions, which, when executed by the processor, cause the electronic device to perform the methods of the first aspect and any of its possible designs.

[0057] Fifthly, this application provides a chip system applied to an electronic device including a display screen and a memory; the chip system includes one or more interface circuits and one or more processors; the interface circuits and processors are interconnected via lines; the interface circuits are used to receive signals from the memory of the electronic device and send signals to the processor, the signals including computer instructions stored in the memory; when the processor executes the computer instructions, the electronic device performs a method as described in the first aspect and any of its possible design embodiments.

[0058] In a sixth aspect, this application provides a computer storage medium including computer instructions that, when executed on an electronic device, cause the electronic device to perform a method as described in the first aspect and any of its possible design embodiments.

[0059] In a seventh aspect, this application provides a computer program product that, when run on a computer, causes the computer to perform a method as described in the first aspect and any of its possible design methods.

[0060] Understandably, the beneficial effects that the communication system of the third aspect, the electronic device of the fourth aspect, the chip system of the fifth aspect, the computer storage medium of the sixth aspect, and the computer program product of the seventh aspect can achieve can be referred to the beneficial effects of the first aspect and any of its possible design embodiments, which will not be repeated here. Attached Figure Description

[0061] Figure 1 This application provides a schematic diagram of the structure of a communication system according to an embodiment of the present application. Figure 2 A schematic diagram of a service flow provided in an embodiment of this application; Figure 3 A hardware structure diagram of a mobile phone provided in an embodiment of this application; Figure 4 One of the interface diagrams of a mobile phone provided in the embodiments of this application; Figure 5 A second screenshot of a mobile phone interface provided in an embodiment of this application; Figure 6 One of the schematic diagrams of service flow provided in the embodiments of this application; Figure 7The second schematic diagram of the service flow provided in the embodiments of this application; Figure 8 The third schematic diagram of the service flow provided in the embodiments of this application; Figure 9 The fourth schematic diagram of the service flow provided in the embodiments of this application; Figure 10 The fifth schematic diagram of the service flow provided in the embodiments of this application; Figure 11 The sixth schematic diagram of the service flow provided in the embodiments of this application; Figure 12 The seventh schematic diagram of the service flow provided in the embodiments of this application; Figure 13 The eighth schematic diagram of the service flow provided in the embodiments of this application; Figure 14 The ninth schematic diagram of the service flow provided in the embodiments of this application; Figure 15 The tenth schematic diagram of the service flow provided in the embodiments of this application; Figure 16 Schematic diagram eleven of the service flow provided in the embodiments of this application; Figure 17 The twelfth schematic diagram of the service flow provided in the embodiments of this application; Figure 18 The thirteenth schematic diagram of the service flow provided in the embodiments of this application; Figure 19 Fourteenth schematic diagram of the service flow provided in the embodiments of this application; Figure 20 The fifteenth schematic diagram of the service flow provided in the embodiments of this application; Figure 21 The sixteenth schematic diagram of the service flow provided in the embodiments of this application; Figure 22 The seventeenth schematic diagram of the service flow provided in the embodiments of this application; Figure 23 The eighteenth schematic diagram of the service flow provided in the embodiments of this application; Figure 24 The nineteenth schematic diagram of the service flow provided in the embodiments of this application; Figure 25 The twentieth diagram illustrating the service flow provided in the embodiments of this application; Figure 26 Schematic diagram twenty-one of the service flow diagrams provided for the embodiments of this application; Figure 27 Schematic diagram twenty-two illustrating the service flow provided in the embodiments of this application; Figure 28Schematic diagram twenty-three illustrating the service flow provided in the embodiments of this application; Figure 29 Schematic diagram twenty-four of the service flow provided for the embodiments of this application; Figure 30 The twenty-fifth diagram illustrates the service flow provided in the embodiments of this application. Detailed Implementation

[0062] The technical solutions of the embodiments of this application are described below with reference to the accompanying drawings. In the description of the embodiments of this application, the terminology used in the following embodiments is for the purpose of describing specific embodiments only and is not intended to limit the application. As used in the specification and appended claims of this application, the singular expressions "a," "the," "the," "the," and "this" are intended to also include expressions such as "one or more," unless the context clearly indicates otherwise. It should also be understood that in the following embodiments of this application, "at least one" and "one or more" refer to one or more (including two). The term "and / or" is used to describe 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, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship.

[0063] References to "one embodiment" or "some embodiments" in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized. The term "connection" includes direct connections and indirect connections, unless otherwise stated. "First" and "second" 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.

[0064] In the embodiments of this application, the words "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplarily" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design solutions. Specifically, the use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a specific manner.

[0065] The device-to-device service transfer control method provided in this application embodiment can be applied to the communication system provided in this application embodiment. The communication system includes multiple electronic devices. Any electronic device can be a mobile phone, tablet (PAD), large screen (i.e., smart TV, also called a smart screen), etc. It is not limited to these; electronic devices can also be personal computers (PCs), personal digital assistants (PDAs), augmented reality (AR) devices, virtual reality (VR) devices, in-vehicle systems, printers, headphones, and other devices with near-field or far-field communication capabilities. Among them, PCs include desktop computers and laptop computers; the following mainly uses a laptop computer as an example to illustrate the solution of this application.

[0066] by Figure 1 Taking the communication system shown as an example, the communication system includes a mobile phone 110, a PAD 120, a PC 130, and a large screen 140.

[0067] In a communication system, multiple electronic devices may be logged into the same user account (such as an Honor account), or multiple electronic devices may be logged into user accounts that have a trust relationship, such as family accounts or workgroup accounts. The following explanation mainly uses logging into the same user account as an example.

[0068] It is understandable that multiple electronic devices logged into the same user account can join the same trust loop through identity authentication.

[0069] Specifically, for printers, if an electronic device in the trust ring has used the printer, then the printer can also be added to the trust ring after authentication. Furthermore, if the printer is on a whitelist, it can also be authenticated. Figure 1 Taking the communication system shown as an example, if mobile phone 110 has used a printer and the printer is on the whitelist, then the printer can also be added to the whitelist. Figure 1 In the communication system shown, namely and Figure 1 Electronic devices within the same trust ring are all in the same trust ring. This allows printers that cannot be logged into the same user account as mobile phones, tablets, PCs, or other electronic devices to be flexibly added to the trust ring, enabling other electronic devices in the trust ring to use the printer's printing services.

[0070] Specifically, for headphones, if an electronic device in the trust ring is connected to the headphones, then the headphones can also be added to the trust ring. (Continuing with...) Figure 1 Taking the communication system shown as an example, if mobile phone 110 is connected to the headset, then the headset can also be added to the system. Figure 1 In the communication system shown, this allows the headset to be added to the trust loop more easily.

[0071] Multiple electronic devices can communicate through short-range or long-range communication methods, such as identity authentication and data transmission for service transfer.

[0072] Short-range communication can include Bluetooth, Near Field Communication (NFC), and Wireless Local Area Networks (WLAN) (such as Wireless Fidelity (Wi-Fi)). Accordingly, to achieve short-range communication between electronic devices, the corresponding communication switches need to be turned on, such as Bluetooth or WLAN. It's important to note that if only WLAN is turned on, a WLAN network connection is required for communication to occur. Typically, before joining a trust loop, electronic devices may prompt for Bluetooth and WLAN to be turned on, allowing communication via WLAN when connected, and via Bluetooth even without a WLAN network connection. Of course, in some technologies, even with WLAN on but not connected to a WLAN network, electronic devices can still communicate via WLAN Direct.

[0073] Remote communication refers to communication between devices when they are connected to a network (such as 3G, 4G, 5G, 6G mobile networks and / or WLAN networks). Accordingly, to achieve remote communication between electronic devices, the devices need to turn on the corresponding network switches (such as mobile communication switches or WLAN switches) and connect to the network.

[0074] After joining the trust ring, any electronic device within the trust ring can call upon the superior services of other electronic devices, enabling service flow between devices.

[0075] In some implementations, multiple electronic devices in the aforementioned communication system can be controlled on a per-device basis to achieve service flow between devices. Specifically, still taking... Figure 1 Taking the communication system shown as an example, after mobile phone 110, PAD 120, PC 130 and large screen 140 are all added to the same trust ring, the following can be viewed on mobile phone 110: Figure 2 The diagram shows a control center 201 with the mobile phone 110 as the center and PAD 120, PC 130, and large screen 140 as ring devices. In response to a user dragging PAD 120 from the control center 201 to the mobile phone 110, such as dragging in the direction indicated by the dotted arrow, the mobile phone 110 can display... Figure 2The control center 202 is shown. Unlike control center 201, in control center 202, PAD 120 is attached to phone 110. At this time, a service transfer from phone 110 (such as screen sharing) to PAD 120 is established between phone 110 and PAD 120. Furthermore, for a certain period, all services provided by phone 110 and PAD 120, such as "screen sharing," "network sharing," and "file sharing," can be displayed at the bottom of phone 110 for switching services, such as switching from the default "screen sharing" to "network sharing."

[0076] However, the above Figure 2 The control scheme shown has two limitations. First, it can only establish the flow of default services and cannot directly control the flow of target services. Furthermore, for services provided by two collaborating devices (such as phone 110 and PAD 120), the user cannot specify the service provider when switching between them. For example, if both phone 110 and PAD 120 offer a "screen sharing" service, the user cannot explicitly choose whether to transfer the "screen sharing" from phone 110 to PAD 120 or vice versa. Second, it can only achieve service flow between the local device and devices on the ring, but not between any two devices on the ring.

[0077] It should be noted that, Figure 2 The control centers 201 and 202 shown refer to the content of the phone's display interface. For example, users can pull down the upper right corner of the phone to display the control center interface.

[0078] To address the aforementioned issues, this application provides a method for controlling service flow between devices. This method allows direct control of the flow of a target service provided by one electronic device to another within any of a plurality of electronic devices. Specifically, it allows for the simultaneous identification of the source device providing the service, the target service, and the target device using the service; and it is not limited to service flow between the local device and other electronic devices. This improves the accuracy and flexibility of service flow.

[0079] Taking a trust loop that includes a mobile phone, a tablet, and a PC as an example, if the device is a mobile phone, then the mobile phone can control not only the service flow between the mobile phone and the tablet, and between the mobile phone and the PC, but also the service flow between the tablet and the PC. For example, the keyboard and mouse services of the PC can be transferred to the tablet, allowing the tablet to use the PC's keyboard and mouse as input.

[0080] The following uses a mobile phone as an example to illustrate the hardware structure of any one of multiple electronic devices. For example... Figure 3As shown, a mobile phone may include: a processor 211, an external memory interface 212, an internal memory 221, a universal serial bus (USB) interface 203, a charging management module 240, a power management module 241, a battery 242, an antenna 1, an antenna 2, a mobile communication module 250, a wireless communication module 260, an audio module 270, a speaker 270A, a receiver 270B, a microphone 270C, a headphone jack 270D, a sensor module 280, buttons 290, a motor 291, an indicator 292, a camera 293, a display screen 294, and a subscriber identification module (SIM) card interface 295, etc.

[0081] It is understood that the structure illustrated in this embodiment does not constitute a specific limitation on the mobile phone. In other embodiments, the mobile phone 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.

[0082] Processor 211 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.

[0083] The charging management module 240 receives charging input from a charger, which can be a wireless charger or a wired charger. While charging the battery 242, the charging management module 240 can also supply power to the electronic device via the power management module 241.

[0084] The power management module 241 connects the battery 242, the charging management module 240, and the processor 211. The power management module 241 receives input from the battery 242 and / or the charging management module 240, and supplies power to the processor 211, internal memory 221, external memory, display 294, camera 293, and wireless communication module 260, etc. In some embodiments, the power management module 241 and the charging management module 240 may also be housed in the same device.

[0085] The wireless communication function of a mobile phone can be implemented through antenna 1, antenna 2, mobile communication module 250, wireless communication module 260, modem processor, and baseband processor.

[0086] Mobile communication module 250 can provide wireless communication solutions for mobile phones, including 2G / 3G / 4G / 5G. Wireless communication module 260 can provide wireless communication solutions for mobile phones, including WLAN (such as wireless fidelity, Wi-Fi), Bluetooth, Global Navigation Satellite System (GNSS), Frequency Modulation (FM), Near Field Communication (NFC), Infrared (IR), and other wireless communication technologies.

[0087] In some embodiments, the mobile phone can establish a trust loop and transmit data for service transfer with other electronic devices through the mobile communication module 250 or the wireless communication module 260.

[0088] The mobile phone implements its display function through a GPU, a display screen 294, and an application processor. The GPU is a microprocessor for image processing, connected to the display screen 294 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. The processor 211 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0089] The mobile phone can perform shooting functions through an ISP, camera 293, video codec, GPU, display 294, and application processor. The ISP is used to process the data fed back by the camera 293. The camera 293 is used to capture still images or videos. In some embodiments, the mobile phone may include one or N cameras 293, where N is a positive integer greater than 1.

[0090] The external storage interface 212 can be used to connect an external storage card, such as a Micro SD card, to expand the phone's storage capacity. The external storage card communicates with the processor 211 through the external storage interface 212 to perform data storage functions. For example, music, video, and other files can be saved on the external storage card.

[0091] Internal memory 221 can be used to store computer executable program code, which includes instructions. Processor 211 executes various functions and data processing of the mobile phone by running the instructions stored in internal memory 221. For example, in this embodiment, processor 211 can execute instructions stored in internal memory 221, which may include a program storage area and a data storage area.

[0092] Mobile phones can perform audio functions, such as music playback and recording, through an audio module 270, a speaker 270A, a receiver 270B, a microphone 270C, a headphone jack 270D, and an application processor.

[0093] Buttons 290 include a power button, volume buttons, etc. Buttons 290 can be mechanical buttons or touch-sensitive buttons. Motor 291 can generate vibration alerts. Motor 291 can be used for incoming call vibration alerts or for touch vibration feedback. Indicator 292 can be an indicator light, used to indicate charging status, battery level changes, messages, missed calls, notifications, etc. SIM card interface 295 is used to connect a SIM card. The SIM card can be inserted into or removed from the SIM card interface 295 to achieve contact and separation with the phone. The phone can support one or N SIM card interfaces, where N is a positive integer greater than 1. SIM card interface 295 can support Nano SIM cards, Micro SIM cards, and other SIM cards.

[0094] Furthermore, the software architecture of electronic devices can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This application does not specifically limit this approach.

[0095] The control method for inter-device service flow provided in this application can be executed in a mobile phone with the above-described hardware and software structure. That is, the control device can be a mobile phone. In practice, the control device can also be any device in the trust loop. Unless otherwise specified below, the control device refers to a mobile phone.

[0096] The mobile phone includes a control center for a trust ring, which controls the service flow between multiple electronic devices within the trust ring. In this embodiment, the method of accessing the control center is not specifically limited. Only two exemplary methods for accessing the control center are described below.

[0097] Method 1: The phone can respond to the user's three-finger swipe up gesture on the current screen and display the control center.

[0098] The current interface is Figure 4 Taking interface 401 as an example, interface 401 is the phone's desktop. In response to the user's three-finger swipe-up gesture on interface 401, the phone can display... Figure 4 The interface 402 shown includes a control center 4021.

[0099] Method 2: The phone can respond to the user's swipe down from the top right of the current screen to display a drop-down menu, which includes an entry point to the control center. In response to the user's action of clicking on the control center entry point, the phone will display the control center.

[0100] The current interface is Figure 4 Taking interface 403 as an example, interface 403 is the phone's desktop. In response to the user swiping down from the top right of interface 403, the phone can display... Figure 4 The interface shown is 404, which is a drop-down menu interface. Interface 404 includes an entry point 4041 for the control center. In response to the user's click on the entry point 4041 for the control center, the phone can also display... Figure 4 The interface shown is 402.

[0101] The above Figure 4 Both methods shown assume the current interface is the desktop, but this is not a limitation in practice. For example, the current interface can also be the application interface of chat applications, video applications, or other similar applications.

[0102] The control center includes multiple electronic devices within a trust ring. Figure 4 Taking the control center 4021 in the interface 402 shown as an example, the control center 4021 includes mobile phones, PADs, PCs and large screens.

[0103] In some embodiments, electronic devices logged into the same user account and capable of short-range communication can join the same trust ring. Correspondingly, the multiple electronic devices in the control center include those logged into the same user account and capable of short-range communication, but exclude those capable of remote communication. This allows for service flow between near-field electronic devices within the control center.

[0104] In other embodiments, electronic devices logged into the same user account and capable of near-field and / or remote communication can join the same trust ring. Correspondingly, multiple electronic devices in the control center include those logged into the same user account and capable of near-field and / or remote communication. Thus, service flow between near-field and / or remote electronic devices can be achieved in the control center.

[0105] by Figure 5 Taking the control center 5011 in the interface 501 shown as an example, the control center 5011 includes not only the near-field mobile phone, PAD, PC1, and large screen, which are located on the solid circle in the figure; it also includes the remote PC2, which is located on the dashed circle in the figure. For example, if the mobile phone, PAD, PC1, and large screen are all located at home, and PC2 is located in the office, then, using this embodiment, the mobile phone can control the service flow between the mobile phone, PAD, PC1, and large screen at home, as well as the service flow between the mobile phone, PAD, PC1, large screen, and PC2.

[0106] In the following text, except for embodiments involving services for remote devices (as described below) Figure 6 and Figure 20 Apart from the corresponding embodiments, the present application mainly uses near-field devices as examples to illustrate the solution.

[0107] In a control center, a user can be at the center, with multiple electronic devices (including the device itself and others) located in a ring around this center. A user can refer to a user logged into the same user account across multiple electronic devices, or it can refer to another user operating the electronic device. For example, Figure 4 In the interface 402 shown, the control center 4021 displays mobile phones, tablets, PCs, and large screens on a ring centered on the user's "S". For example, Figure 5 In the interface 501 shown, the control center 5011 displays the mobile phone, PAD, PC1, large screen, and PC2 on a ring centered on the user "S". In other words, the device center in the control center has been removed; it is no longer centered on the local device, such as the mobile phone, but rather on the user.

[0108] It's important to note that although the control center doesn't center on this device, it will still be displayed differently from other devices, such as in color and effects. In this article, the device is filled with black, and other devices are filled with white. For example, Figure 4 In the control center 4021 of the interface 402 shown, the circle for the mobile phone is filled with black, while the circles for the PAD, PC, and large screen are filled with white.

[0109] Each electronic device in the control center can provide its advantageous services, which can be accessed by other electronic devices in the control center. For example, the electronic devices in the control center and their advantageous services are shown in Table 1 below: Table 1

[0110] In the following text, to simplify the accompanying drawings, the control center of the mobile phone interface will be drawn primarily in the drawings, instead of the mobile phone interface including the control center; furthermore, each electronic device in the control center will be represented by text instead of its corresponding icon, such as the mobile phone will be represented by the text "mobile phone" instead of the mobile phone icon.

[0111] In some embodiments, in response to a triggering action, such as a click, on a user icon in the control center, the mobile phone can expand various advantageous services offered by the device. Once expanded, each advantageous service is displayed around the electronic device providing that service.

[0112] In this article, the services of each electronic device are represented by bold circles, and the example is that the services of each electronic device surround the electronic device. In practice, this shape and position are not limited.

[0113] For example, in response to user input Figure 6 The user icon "S" in the control center 601 before expansion, as shown in the image, can be clicked on the phone. Figure 6 The expanded control center 602 is shown below. In control center 602, the mobile phone's advantageous services "Screen Sharing," "Network Sharing," "File Sharing," and "Cross-Platform Calling" are displayed around the mobile phone in bold circles; the PAD's advantageous services "Screen Sharing," "Keyboard and Mouse Sharing," "File Sharing," and "Cross-Platform Calling" are displayed around the PAD in bold circles; the PC1's advantageous services "Screen Sharing," "Keyboard and Mouse Sharing," "File Sharing," and "Cross-Platform Calling" are displayed around the PC1 in bold circles; the PC2's advantageous service "Remote Access" is displayed around the PC2 in bold circles; the printer's advantageous service "Printing" is displayed around the printer in bold circles; and the headset's advantageous service "Audio" is displayed around the headset in bold circles.

[0114] Of course, after being expanded, in response to user actions triggered in the control center, such as clicks, the phone can revert to its state before being expanded, such as displaying... Figure 6 The control center 601 is shown.

[0115] In this way, users in the control center can quickly expand or collapse the advantageous services of various electronic devices on their phones, facilitating a comprehensive understanding of the advantageous services of all electronic devices in the trust ring.

[0116] In other embodiments, in response to a triggering operation, such as a click, on any electronic device in the control center, the mobile phone can display the advantageous services offered by that electronic device in the control center. Taking a mobile phone as an example, in response to a user's action... Figure 7 The touch operations on the mobile phone in the control center 701 before expansion are shown. The mobile phone can display... Figure 7 The expanded control center 702 is shown. In control center 702, the phone's key services "Screen Sharing," "Network Sharing," "File Sharing," and "Cross-device Calling" are displayed around the phone in bold circles.

[0117] Of course, the two embodiments described above for triggering the display of the advantage service can also be used in combination. That is, in some other embodiments, the mobile phone can display the advantage service in response to a trigger operation on the user icon in the control center, or in response to a trigger operation on any electronic device in the control center.

[0118] The following section primarily uses the example of displaying advantageous services in response to a trigger operation on any electronic device in the control center to illustrate the solution of this application.

[0119] After the featured services are displayed, users can perform operations on featured service A to achieve service transfer between devices. Below, using featured service A as "screen sharing," with the source device being a mobile phone and the target device being a tablet, we will illustrate the specific operation process for service transfer.

[0120] In one specific implementation, users can drag the "screen sharing" function from their phone to their tablet to enable the service flow of "screen sharing" from phone to tablet.

[0121] See Figure 8 In Method 1, in response to the operation of dragging the "Screen Sharing" provided by the phone in Control Center 801 to the PAD (as shown by the dotted arrow), the phone can update the display position of "Screen Sharing", such as updating it from being displayed around the phone in Control Center 801 to being displayed around the PAD in Control Center 802.

[0122] In another specific implementation, users can click "Screen Sharing" and then drag "Screen Sharing" from the phone to the PAD to achieve the service flow of "Screen Sharing" from the phone to the PAD.

[0123] See Figure 8In method 2, in response to a click on the "Screen Sharing" function provided by the phone in Control Center 803, the phone can display Control Center 804. In Control Center 804, other advantageous services provided by the phone are hidden, such as "Network Sharing," "File Sharing," and "Cross-device Call," and only "Screen Sharing" is displayed. Furthermore, the phone can prompt the user to drag "Screen Sharing" to the target device, such as prompting "Drag the service to the target device to complete the flow" 805. In this way, the phone can effectively guide users unfamiliar with service flows. Subsequently, in response to the user dragging "Screen Sharing" from Control Center 804 to the PAD (as shown by the dotted arrow), the phone can update the display position of "Screen Sharing," such as changing it from being displayed around the phone in Control Center 804 to being displayed around the PAD in Control Center 806.

[0124] Furthermore, after displaying the "screen sharing" option provided by the phone around the PAD, to clearly identify the phone as the source device for "screen sharing," the phone can also display its own identifier around the updated "screen sharing" location. See also... Figure 8 After the control centers 802 and 806 update the location of "screen sharing" to around the PAD, the phone can also display "phone" around "screen sharing".

[0125] Both method 1 and method 2 described above can be used to transfer the phone's "screen sharing" to the PAD. See also... Figure 8 In the diagram, control centers 802 and 806, after successful transfer, are represented by the dashed ellipse, indicating that the mobile phone shares its screen with the PAD. The following text primarily uses method 1 as an example to illustrate the transfer of the source device's advantageous service to the target service.

[0126] However, cross-device calls differ in the following ways: Cross-device calls typically include multiple sub-services, including but not limited to: cross-device scanning, cross-device photography, cross-device screenshotting, and cross-device screen recording. That is, the target device can invoke the source device to perform scanning, photography, screenshotting, or screen recording. After completing these operations, the source device can return the results to the target device, such as scanned, photographed, or screenshotted images, or recorded videos.

[0127] For cross-platform calls, users can transfer a sub-service (denoted as sub-service B) from the source device to the target device using the following implementation method. Below, we will illustrate the specific operation process of service transfer using an example where the sub-services in the cross-platform call include cross-platform screenshot and cross-platform photography, with sub-service B being "cross-platform photography," the source device of sub-service B being a mobile phone, and the target device being a tablet.

[0128] In one specific implementation, the displayed advantageous services include "cross-device screenshot" and "cross-device shooting," but not "cross-device invocation." Subsequently, users can drag "cross-device shooting" from the phone to the PAD to realize the service flow of "cross-device shooting" from the phone to the PAD.

[0129] See Figure 9 Method a, in the phone's advantageous services shown in Control Center 901, includes "Cross-device screenshot" and "Cross-device shooting," instead of "Cross-device call." Subsequently, in response to the operation of dragging "Cross-device shooting" from Control Center 901 to the PAD (as shown by the dotted arrow), the phone can update the display position of "Cross-device shooting," such as updating it from being displayed around the phone in Control Center 901 to being displayed around the PAD in Control Center 902.

[0130] In another specific implementation, "Cross-device invocation," "Cross-device screenshot," and "Cross-device shooting" are displayed simultaneously among the featured services. Subsequently, users can drag "Cross-device shooting" from their phone to their PAD to enable the service flow of "Cross-device shooting" from the phone to the PAD.

[0131] See Figure 9 Method b, in the advantageous services of the phone shown in Control Center 903, includes "Cross-device Invocation," "Cross-device Screenshot" (displayed as "Screenshot" in the figure), and "Cross-device Shooting" (displayed as "Shooting" in the figure). Subsequently, in response to the operation of dragging "Cross-device Shooting" in Control Center 903 to PAD (as shown by the dotted arrow), the phone can update the display position of "Cross-device Shooting," such as updating from displaying it around the phone in Control Center 903 to displaying it around the PAD in Control Center 904.

[0132] Of course, similar to method 2 above, after displaying the cross-platform sub-service, users can also first click "Cross-platform Shooting" in Control Center 903, and then drag "Cross-platform Shooting" from the phone to the PAD to realize the service flow of "Cross-platform Shooting" from the phone to the PAD. This will not be elaborated further here.

[0133] In another specific implementation, the displayed services include "cross-device invocation," but exclude "cross-device screenshot" and "cross-device shooting." Users can drag "cross-device invocation" from their phone to the PAD. The PAD then offers "cross-device screenshot" and "cross-device shooting" options for the user to choose from. After the user selects the "cross-device shooting" option, the service flow for "cross-device shooting" from the phone to the PAD is realized.

[0134] See Figure 10As shown in method c, the mobile phone's advantageous services in control center 1001 include "Cross-device call," but exclude "Cross-device screenshot" and "Cross-device shooting." In response to dragging "Cross-device call" from control center 1001 to the PAD (as indicated by the dotted arrow), the mobile phone can update the display position of "Cross-device call," such as changing it from being displayed around the mobile phone in control center 1001 to being displayed around the PAD in control center 1002. Subsequently, or simultaneously, the PAD can display interface 1003, which includes "Screenshot" 10031 (an option for "Cross-device screenshot") and "Shoot" 10032 (an option for "Cross-device shooting"). Later, in response to selecting "Shoot" 10032, the mobile phone can display control center 1004. Unlike control center 1002, the "Cross-device call" displayed around the PAD in control center 1004 is updated to "Cross-device shooting."

[0135] Alternatively, in response to the selection operation of "shoot" 10032, the phone will not display the control center 1004, but will still display the control center 1002. Furthermore, within the PAD, "cross-platform call" can be used as a global service (e.g., displayed as a floating ball within the PAD). Specifically, users can use "cross-platform call" while using various applications on the PAD, thereby leveraging the phone's shooting, scanning, and screenshot services. Only when the user closes the "cross-platform call" on the PAD, such as closing the floating ball, will the PAD send a message to the phone to end the call. In response to this message, the phone will cancel the display of "cross-platform calls" around the PAD in the control center 1002, indicating that the "cross-platform call" flow has been disconnected.

[0136] Using methods a, b, or c above, you can achieve the transfer of "cross-device shooting" from your phone to the PAD. See also... Figure 9 Control Center 902, Control Center 904 and Figure 10 In the control center 1004, after successful transfer, the dashed ellipse can represent: the PAD calling the phone to take a picture. Of course, as explained earlier, this may not actually be displayed in practice. Figure 10 As shown in the control center 1004, the corresponding "cross-device call" from the PAD to the mobile phone can only be represented through control center 1002. The following text primarily uses method b as an example to illustrate the flow of sub-services from the source device's cross-device call to the target device.

[0137] The above Figures 8-10The example primarily illustrates the process of transferring a mobile phone's preferred service to other devices (such as a tablet) (referred to as transfer form one). In practice, within the control center, it is also possible to transfer a preferred service from another device (referred to as preferred service C) to a mobile phone (referred to as transfer form two), or to transfer a preferred service from one device (referred to as preferred service D) to another device (referred to as transfer form three).

[0138] The following examples illustrate the operation process shown in Method 1 above: Taking a PAD as the source device, a mobile phone as the target device, and "keyboard and mouse sharing" as the advantageous service C, see [example]. Figure 11 In the second flow pattern, in response to a user's click on the PAD in Control Center 1101, the phone can display Control Center 1102. In Control Center 1102, the PAD's key services "Screen Sharing," "Keyboard and Mouse Sharing," "File Sharing," and "Cross-Platform Calling" are displayed. In response to dragging "Keyboard and Mouse Sharing" from the PAD to the phone in Control Center 1102 (as shown by the dotted arrow), the phone can update the display position of "Keyboard and Mouse Sharing," such as changing it from being displayed around the PAD in Control Center 1101 to being displayed around the phone in Control Center 1103. This achieves the flow of "Keyboard and Mouse Sharing" from the PAD to the phone.

[0139] Taking a PAD as the source device, a PC as the target device, and "keyboard and mouse sharing" as the preferred service D, see [example]. Figure 11 In the third form of the workflow, in response to a user's click on the PAD in Control Center 1104, the phone can display Control Center 1105. In Control Center 1105, the PAD's key services—"Screen Sharing," "Keyboard and Mouse Sharing," "File Sharing," and "Cross-Platform Calling"—are displayed. In response to dragging "Keyboard and Mouse Sharing" from the PAD to the PC in Control Center 1105 (as shown by the dotted arrow), the phone can update the display position of "Keyboard and Mouse Sharing," such as changing it from being displayed around the PAD in Control Center 1105 to being displayed around the PC in Control Center 1106. This achieves the workflow of "Keyboard and Mouse Sharing" from the PAD to the PC.

[0140] It's important to emphasize that using Flow Mode 3 allows for control of service flow between other devices via the control center on the mobile phone. This significantly improves the flexibility of service flow. For example, if an adult uses a tablet in the bedroom and a child uses a mobile phone to watch cartoons in the living room, and there's a large screen in the living room, then using Flow Mode 3, the phone's "screen sharing" can be transferred from the tablet's control center to the large screen, allowing the cartoon to play on the large screen.

[0141] This application embodiment exemplarily describes the underlying logic for implementing business flow in the above-mentioned flow form one, flow form two, and flow form three: In the first form of transfer, taking the transfer of a superior service A provided by the mobile phone to the PAD as an example: In response to the user's operation of dragging the superior service A from the mobile phone to the PAD, the mobile phone can establish a transfer of the superior service A with the PAD based on the superior service A and the PAD, so as to realize the transfer of the superior service A to the PAD.

[0142] The second method of service transfer, taking the transfer of the advantageous service C provided by the PAD to the mobile phone as an example: In response to the user's action of dragging the advantageous service C from the PAD to the mobile phone, the mobile phone can notify the PAD to establish a transfer of the advantageous service C with the mobile phone, such as sending information about the mobile phone and the advantageous service C to the PAD. The mobile phone information indicates the target device, and the advantageous service C information indicates the service being transferred. Responding to the information from the mobile phone and the advantageous service C, the PAD can communicate with the mobile phone to establish a transfer of the advantageous service C, thus realizing the transfer of the advantageous service C from the PAD to the mobile phone.

[0143] The third form of service transfer, taking the transfer of the advantageous service D provided by the PAD to the PC as an example: In response to the user's action of dragging the advantageous service D from the PAD to the PC, the mobile phone can notify the PC to establish a transfer of the advantageous service D with the PAD, such as sending information from the PC and the advantageous service D to the PAD. The PC's information indicates the target device, and the advantageous service D's information indicates the service being transferred. Responding to the PC's information and the advantageous service D's information, the PAD can communicate with the PC to establish the transfer of the advantageous service D, thus realizing the transfer of the advantageous service D from the PAD to the PC.

[0144] After the service transfer is completed, the mobile phone can display a success message on the control center interface. Simultaneously, both the source and target devices can also display success messages on their respective interfaces. The success message indicates that the target service (such as the aforementioned Advantage Service A, Sub-service B, Advantage Service C, and Advantage Service D) has been successfully transferred from the source device to the target device. In practice, the success message may include text and / or an icon; this document does not specify a particular limitation. The following explanation primarily uses text as an example.

[0145] Taking a mobile phone as the source device, a tablet as the target device, and "screen sharing" as the target service as an example, after transferring the "screen sharing" function from the mobile phone to the tablet: On the one hand, the phone can display Figure 12The interface 1201 shown includes a control center 12011, in which a dashed box indicates that screen sharing from the phone has been successfully transferred to the PAD. Simultaneously, interface 1201 also includes a notification 12012, which contains the text "Screen sharing from the phone has been successfully transferred to the PAD".

[0146] On the other hand, the PAD can display Figure 12 The interface 1202 shown is the desktop of the PAD. The interface 1202 also includes the interface of the mobile phone (represented as "mobile phone interface" in the figure). The mobile phone interface displayed on the PAD is the same as the actual interface displayed on the mobile phone, or the mobile phone interface displayed on the PAD has more navigation buttons at the bottom than the actual interface displayed on the mobile phone, which indicates that the mobile phone is sharing the screen. In addition, the interface 1202 also includes a prompt 12021, which includes the prompt text "The mobile phone is sharing the screen".

[0147] The control center has been presented from the perspective of the mobile phone in the preceding text. For example, Figures 6-11 In the diagram, the circle containing the phone is filled with black, indicating that the device in question is the phone. Understandably, the control center will change when viewed from the perspective of other devices in the trust ring. For example, the view of the device itself might switch.

[0148] For example, Figure 13 In the perspectives of the phone (represented as "phone side" in the image), the PAD (represented as "PAD side"), and the PC (represented as "PC side"), "Screen Sharing" is displayed around the PAD, and "Phone" is also displayed around "Screen Sharing," indicating that the phone's "Screen Sharing" has been transferred to the PAD. However, from the phone's perspective, the phone is at the top of the control center, and the circle containing the phone is filled with black, indicating that the device is the phone; from the PAD's perspective, the PAD is at the top of the control center, and the circle containing the PAD is filled with black, indicating that the device is the PAD; from the PC's perspective, the PC is at the top of the control center, and the circle containing the PC is filled with black, indicating that the device is the PC.

[0149] The advantageous services listed in Table 1 above can be divided into two categories: the first category allows only one target device to be accessed at a time; the second category allows access to multiple (two or more) target devices at a time. These two categories of advantageous services will be explained below.

[0150] The first type, which can only be transferred to one target device at a time, is denoted as Service E. Service E includes, but is not limited to: screen sharing, file sharing, cross-platform calls, remote calls, printing, and audio.

[0151] In other words, service E cannot be transferred to multiple target devices simultaneously. That is, after service E from the source device is transferred to a target device, the transfer of service E from the source device to the target device must be terminated before service E from the source device can be transferred to another target device, so that service E is transferred to only one target device at any given time.

[0152] The following example illustrates how service E can be switched between multiple target devices, using a mobile phone as the source device and the process of switching service E from a PAD to a PC: In one specific implementation, see Figure 14 In method 11, the mobile phone can display a control center 1401. In control center 1401, service E is displayed around the PAD, and the mobile phone is also displayed around service E, indicating that service E provided by the mobile phone is flowing to the PAD. In response to the user dragging service E from control center 1401 to the PC, the mobile phone can display a control center 1402. Unlike control center 1401, in control center 1402, service E is displayed around the PC instead of the PAD, indicating that service E provided by the mobile phone is switching from flowing to the PAD to flowing to the PC. This allows for quick switching of service flows.

[0153] In another specific implementation, see Figure 14 In method 12, the mobile phone can display control center 1403, which is the same as control center 1401 in method 11, and will not be described again here. In response to the user's click on the mobile phone (i.e., the source device) in control center 1403, the mobile phone can display control center 1404. Unlike control center 1403, the preferred services provided by the mobile phone in control center 1404 are expanded. In response to the user dragging service E from the expanded preferred services in control center 1404 to the PC, the mobile phone can display control center 1405. Unlike control center 1404, the preferred services of the mobile phone in control center 1405 are collapsed; service E is not displayed around the PAD, but service E is displayed around the PC, and the mobile phone is also displayed around service E, indicating that the service E provided by the mobile phone has switched from flowing to the PAD to flowing to the PC.

[0154] In methods 11 and 12 above, in response to the operation of switching service E from flowing to PAD to flowing to PC, such as dragging service E from control center 1401 to PC or dragging service E from the expanded advantageous services in control center 1404 to PC, the mobile phone can first disconnect the flow of service E from PAD, and then establish the flow of service E with PC. It should be noted that if the source device of service E is not the mobile phone, in response to the operation of switching service E from flowing to PAD to flowing to PC, the mobile phone can notify the source device to disconnect the flow of service E from PAD, and also notify the source device to establish the flow of service E with PC. Subsequently, in response to the notification of disconnecting the flow of service E from PAD, the source device can disconnect the flow of service E from PAD; in response to the notification of establishing the flow of service E with PC, the source device can establish the flow of service E with PC.

[0155] The following text will mainly use method 11 above as an example to illustrate the flow of service E.

[0156] The following sections use service E as an example to illustrate the operation flow and interface response of service E, which includes screen sharing, file sharing, cross-platform calls, remote calls, printing, and audio.

[0157] First, screen sharing.

[0158] Example 1: Transfer the "screen sharing" function provided by the mobile phone to the car's infotainment system.

[0159] See Figure 15 The phone can display Control Center 1501, which displays the phone's key services: "Screen Sharing," "Network Sharing," "File Sharing," and "Cross-device Access." At this time, the vehicle's infotainment system displays its own user interface 15011. In response to the user dragging the "Screen Sharing" option from Control Center 1501 to the vehicle's infotainment system (represented as "the car" in the diagram), the phone can display Control Center 1502, where the "Screen Sharing" option is displayed around the vehicle's infotainment system. That is, the phone's "Screen Sharing" function is transferred to the vehicle's infotainment system. The vehicle's infotainment system will then display the content from the phone. The content displayed on the mobile phone on the vehicle's infotainment system can take one of two forms: Form 1, displaying the phone's user interface, such as the mobile phone's interface 15022 included in the vehicle's interface 15021; Form 2, displaying the applications on the mobile phone, such as area 15024 included in the vehicle's interface 15023, which displays APP1-APP10 on the mobile phone, as well as frequently used apps such as APP1 and APP5. It is clear that the mobile phone's screen is being shared with the vehicle's infotainment system.

[0160] In Example 1 above, the phone screen can be shared with the vehicle's infotainment system via mobile phone control. This utilizes the first flow method described above.

[0161] Example 2: Transferring the phone's "screen sharing" function from the PAD to the large screen. In this example, the control device is the PAD.

[0162] See Figure 16 The PAD can display a control center 1601, which displays the phone's key services around the phone: "Screen Sharing," "Network Sharing," "File Sharing," and "Cross-Platform Calling." At this time, the large screen displays its own user interface 16011. In response to the user dragging "Screen Sharing" to the large screen, the phone can display a control center 1602, where "Screen Sharing" is displayed around the large screen. That is, the phone's "Screen Sharing" has been transferred to the large screen. At this time, the user interface 16021 displayed on the large screen includes the phone's user interface 16022. It is clear that the phone's screen has been shared with the large screen.

[0163] In Example 2 above, the phone screen can be shared with a larger screen via controls on the PAD. This utilizes the third flow method described above.

[0164] Example 3: On the phone, the "screen sharing" function provided by the phone is first transferred to the PAD, and then switched to the PC.

[0165] See Figure 17 The phone can display Control Center 1701, which is the same as Control Center 1501 mentioned earlier, and will not be described again here. At this time, both the PAD and PC display their respective user interfaces, such as user interface 17011 on the PAD and user interface 17012 on the PC. In response to the user dragging the "Screen Sharing" button from Control Center 1701 to the PAD, the phone can display Control Center 1702, with the "Screen Sharing" button displayed around the PAD. That is, the phone's "Screen Sharing" has been transferred to the PAD. At this time, the PC still displays its own user interface 17023, while the user interface 17021 displayed on the PAD includes the phone's user interface 17022. It is clear that the phone's screen has been shared with the PAD.

[0166] See also Figure 17 In response to the user dragging the "Screen Sharing" icon around the PAD in Control Center 1702 to the PC, the phone can display Control Center 1703. The "Screen Sharing" icon is then displayed around the PC in Control Center 1703. That is, the phone's "Screen Sharing" has been transferred to the PC. At this time, the PAD displays its own user interface 17031, but the PC's user interface 17032 includes the phone's user interface 17033. Therefore, the phone's screen has been shared with the PC.

[0167] In Example 3 above, the phone screen can be shared with a tablet first, and then switched to a PC, all through controls on the phone. This allows for the transfer and switching of the phone's advantageous services to other devices.

[0168] Second, file sharing.

[0169] For example, to transfer the "file sharing" function provided by the phone to the PAD, see [link / reference]. Figure 18 The phone can display Control Center 1801, which is the same as Control Center 1501 mentioned earlier, and will not be described again here. At this time, the PAD displays interface 18011, which is the desktop. In response to the user dragging "File Sharing" from Control Center 1801 to the PAD, the phone can display Control Center 1802, and "File Sharing" in Control Center 1802 is displayed around the PAD. That is, the phone's "File Sharing" has been transferred to the PAD. At this time, interface 18021 will be displayed on the PAD. Interface 18021 is the interface of the file management app on the PAD; and interface 18021 includes files on the phone, such as File 1, File 2, File 3, and File 4. It can be seen that the phone's files have been shared with the PAD.

[0170] In the file sharing example above, after the "file sharing" function provided by the phone is transferred to the PAD in the control center, the PAD can display the interface of the file management app and show the files on the phone, making it convenient to operate the files on the phone from the PAD.

[0171] Third, cross-platform calls.

[0172] Taking the "cross-device shooting" function provided by the mobile phone as an example to transfer it to the PAD, see [link / reference]. Figure 19The phone can display Control Center 1901, which displays the phone's main services: "Screen Sharing," "Network Sharing," "File Sharing," and "Cross-Platform Calling." "Cross-Platform Calling" is further surrounded by two sub-services: "Shoot" (corresponding to the "Cross-Platform Shooting" sub-service) and "Screenshot" (corresponding to the "Cross-Platform Screenshot" sub-service). At this time, the phone displays interface 19011, like the desktop; the PAD displays interface 19012, like a document editing interface. Responding to the user dragging "Shoot" from Control Center 1901 to the PAD, the phone can display Control Center 1902, where "Cross-Platform Shooting" is displayed around the PAD. That is, the phone's "Cross-Platform Shooting" function is transferred to the PAD. At this time, the PAD displays interface 19021, still a document editing interface; however, the phone displays the shooting interface 19022. Subsequently, in response to the user's shooting operation on interface 19022, the mobile phone can take a picture and send the picture to the PAD. The PAD can then display interface 19031, which includes the picture 19032 taken by the mobile phone.

[0173] In the example of cross-platform calling above, after the "cross-platform shooting" stream provided by the mobile phone is transferred to the PAD in the control center, the PAD can call the mobile phone to shoot and send back the captured image, so that the PAD can ultimately display the image captured by the mobile phone.

[0174] The aforementioned cross-platform call is particularly suitable for use on tablets and PCs, such as when inserting images while editing a document. In this scenario, the phone's "cross-platform call" can be routed to the tablet or PC via the phone's control center, conveniently triggering the phone to perform operations such as screenshotting or taking a picture and returning the results to the tablet or PC. This allows for image acquisition by utilizing the phone's shooting and screenshot capabilities without interrupting the current task on the tablet or PC, such as document editing.

[0175] Fourth, remote access.

[0176] For example, to transfer the "remote access" provided by a PC to a mobile phone, see [link / reference]. Figure 20The phone can display Control Center 2001, and within Control Center 2001, the "Remote Access" service of PC2 is displayed around PC2. At this time, the phone displays interface 20011, similar to a desktop. In response to the user dragging "Remote Access" from Control Center 2001 to the phone, the phone can display Control Center 2002, with "Remote Access" displayed around the phone. That is, PC2's "Remote Access" has been transferred to the phone. At this time, the phone will display interface 20021, which includes PC2's interface 20022. It is evident that the phone is accessing PC2.

[0177] In the remote access example above, after the "remote access" provided by the PC is transferred to the mobile phone in the control center, the mobile phone can remotely access the PC.

[0178] Fifth, print.

[0179] For example, to transfer the "print" function provided by the printer to the mobile phone, see [link / reference]. Figure 21 The phone can display a control center 2101, in which the printer's "Print" service is displayed around it. At this time, the phone displays interface 21011, similar to a document interface. In response to the user dragging the "Print" button from control center 2101 to the phone, the phone can display a control center 2102, in which the "Print" button is displayed around the phone. That is, the printer's "Print" function is now available on the phone. At this time, interface 21021 is displayed on the phone, including a floating print control 21022. It is clear that the printer's "Print" function is now available on the phone.

[0180] In the printing example above, after the "Print" function provided by the printer is transferred to the mobile phone in the control center, the mobile phone can print the document through the floating print control.

[0181] Sixth, audio.

[0182] Taking the example of first streaming the "audio" provided by the headphones to the phone and then switching to the tablet, see [link / reference]. Figure 22 The phone can display Control Center 2201, with the "Audio" service prominently displayed around the headphones. At this time, the headphones' "audio" is not being transmitted to any device; that is, no device is using the headphones, so the headphones are not producing sound. In response to the user dragging the "Audio" data from Control Center 2201 to the phone, the phone can display Control Center 2202, with the "Audio" data displayed around the phone. That is, the headphones' "audio" is now being transmitted to the phone. At this point, the headphones can play the sound corresponding to the audio data transmitted from the phone. Therefore, the headphones are playing the phone's audio.

[0183] See also Figure 22 In response to the user dragging the "Audio" data around the phone in Control Center 2202 to the PAD, the phone can display Control Center 2203. The "Audio" data is then displayed around the PAD in Control Center 2203. That is, the "Audio" from the headphones has been transferred to the PAD. At this time, the headphones can play the sound corresponding to the audio data transmitted from the PAD. Therefore, it is clear that the headphones are playing audio from the PAD.

[0184] In the audio example above, the audio can be played through the headphones first, and then switched to play the audio from the tablet, all via control on the mobile phone.

[0185] Furthermore, considering that headphones typically only provide audio services, in some embodiments, the headphones in the control center can be displayed as a service, such as... Figure 23 In the control center 2301 shown, the headphones are displayed within a bold circle. When any electronic device in the control center plays audio through the headphones, the headphones can be displayed around that electronic device. Subsequently, in response to the user dragging the headphones from around that electronic device to another electronic device in the control center, the phone can display the headphones around the other electronic device, and the headphones can play audio from that other electronic device. This allows the "audio" from the headphones to switch from flowing to one electronic device to flowing to another electronic device.

[0186] For example, if multiple electronic devices in the trust loop are not playing audio through headphones, the phone can display... Figure 23 The control center 2301 is shown. When a mobile phone in the trust loop is connected to headphones and audio is played through the headphones, the mobile phone can display... Figure 23 The control center 2302 is shown. In control center 2302, headphones are displayed around the phone, indicating that the phone is playing audio through headphones. Subsequently, in response to the user dragging the headphones from control center 2302 to the PAD, the phone can display... Figure 23 The control center 2303 is shown. In control center 2303, headphones are displayed around the PAD, indicating that the PAD is playing audio through the headphones.

[0187] In this embodiment, in the control center, the user can drag the headphones to play audio from different devices.

[0188] In other embodiments, if none of the multiple electronic devices in the control center are connected to headphones, the control center displayed on the phone may not include headphones. After any electronic device in the control center connects to headphones, the phone can display headphones around that electronic device in the control center, indicating that the electronic device is connected to headphones. Subsequently, in response to a user dragging the headphones around that electronic device to another electronic device in the control center, the phone can display headphones around that other electronic device, indicating that the other electronic device is connected to headphones, and the headphones around any other electronic device disappear, indicating that the electronic device is disconnected from the headphones. This allows the "audio" from the headphones to switch from flowing to one electronic device to flowing to another electronic device.

[0189] The second type can be transferred to multiple target devices at the same time, denoted as Service F. Service F includes, but is not limited to: network sharing and keyboard / mouse sharing.

[0190] That is, service F can be transferred to multiple target devices simultaneously. In other words, after service F from the source device is transferred to a target device, even without ending the transfer of service F from the source device to the target device, service F from the source device can be further transferred to another target device, so that service F can be transferred to multiple target devices at the same time.

[0191] The following example, using a mobile phone as the source device for service F, illustrates how service F can be simultaneously transferred between multiple target devices, first to a PAD and then to a PC: In one specific implementation, see Figure 24 In method 21, the mobile phone can display a control center 2401. In control center 2401, service F is displayed around the PAD, and the mobile phone is also displayed around service F, indicating that service F provided by the mobile phone flows to the PAD. In response to the user dragging service F from control center 2401 to the PC, the mobile phone can display a control center 2402. Unlike control center 2401, in control center 2402, service F is displayed not only around the PAD but also around the PC, indicating that service F provided by the mobile phone, after flowing to the PAD, has further flowed to the PC.

[0192] In another specific implementation, see Figure 24In method 22, the mobile phone can display control center 2403, which is the same as control center 2401 in method 21, and will not be described again here. In response to the user's click operation on the mobile phone (i.e., the source device) in control center 2403, the mobile phone can display control center 2404. Unlike control center 2403, the preferred services provided by the mobile phone in control center 2404 are expanded. In response to the user dragging service F from the expanded preferred services in control center 2404 to the PC, the mobile phone can display control center 2405. Unlike control center 2404, the preferred services of the mobile phone in control center 2405 are collapsed, and service F is displayed not only around the PAD but also around the PC, indicating that service F provided by the mobile phone, after flowing to the PAD, is further flowed to the PC.

[0193] In methods 21 and 22 described above, when service F is transferred to the PAD, in response to an operation that further transfers service F to the PC, such as dragging service F from the control center 2401 to the PC or dragging service F from the expanded services in the control center 2404 to the PC, the mobile phone can further establish a service F transfer with the PC. It should be noted that if the source device of service F is not the mobile phone, in response to the operation of further transferring service F to the PC, the mobile phone can notify the source device to establish a service F transfer with the PC. Subsequently, in response to the notification to establish a service F transfer with the PC, the source device can establish a service F transfer with the PC.

[0194] Thus, comparing methods 11 and 21, as well as methods 12 and 22 mentioned above, we can see that when a service has already been transferred to a target device, in response to the user's operation of dragging the service to another target device, or in response to the user's operation of clicking the source device of the service and then dragging the service to another target device, the mobile phone can make different responses based on the different services. For example, if it is service E, the mobile phone will switch service E to another target device, so that service E is transferred to one target device at the same time; if it is service F, the mobile phone will continue to transfer service F to another target device, so that service F is transferred to multiple target devices at the same time.

[0195] However, see continue. Figure 24When the phone displays Control Center 2401, if the user drags service F from Control Center 2401 to the PC, they may want to further transfer service F to the PC, or they may want to switch service F from transfer to a different transfer. In other words, the user's intention is unclear. Therefore, using method 21 may result in a response that does not meet the user's expectations. Based on this, in actual implementation, when transferring service F to a target device, in response to the user's operation of dragging a service F near that target device to another target device, the phone may either not respond, or display options indicating the intention (such as switching options and further transfer options) and respond based on the user's choice.

[0196] The following text will mainly use method 22 mentioned above as an example to illustrate the flow of service F.

[0197] The following sections use service F for network sharing and keyboard / mouse sharing as examples to illustrate the operation process and interface response of service F.

[0198] First, network sharing.

[0199] Taking the example of transferring the phone's "network sharing" function from the phone to the tablet, and then transferring the phone's "network sharing" function to the PC: See Figure 25 The phone can display Control Center 2501. In Control Center 2501, "Network Sharing" is displayed around the PAD, and the phone is displayed around "Network Sharing," indicating that the phone's "Network Sharing" has been transferred to the PAD. At this time, the PAD can access the network normally, and the PAD can also display a message "Using network from phone" 25011, clearly indicating that the source device of the network is the phone. However, the PC is not using the phone's network, and the PC has no other network source; therefore, the PC cannot access the network, which is represented by "Unable to access network" in the diagram.

[0200] In response to the user's click operation on the mobile phone in the control center 2501, the mobile phone can display... Figure 25 The control center shown is 2502. Unlike control center 2501, control center 2502 includes the phone's key services: "screen sharing," "network sharing," "file sharing," and "cross-device access." At this point, the PAD still uses the phone's network, but the PC cannot access the network.

[0201] In response to the user dragging "Network Sharing" from Control Center 2502 to the PC, the phone can display... Figure 25The control center 2503 is shown. In control center 2503, not only is "Network Sharing" displayed around the PAD, but "Network Sharing" is also displayed around the PC. Furthermore, a mobile phone is also displayed around "Network Sharing," indicating that the "Network Sharing" from the mobile phone has been further transferred to the PC after being transferred to the PAD. At this time, not only can the PAD access the network normally, but the PC can also access the network normally. The PC can also display a message "Using network from mobile phone" 25021, clearly indicating that the source device of the network is the mobile phone.

[0202] In Example 3 above, the phone's network can be shared with the tablet first, and then further shared with the PC, through controls on the phone. This enables the "network sharing" from the local device to multiple target devices.

[0203] Second, keyboard and mouse sharing.

[0204] Taking the example of transferring the PC's "keyboard and mouse sharing" function from the PC to the mobile phone, and then transferring the PC's "keyboard and mouse sharing" function to the PAD, in this example, the control device is the PC: See Figure 26 The PC can display Control Center 2601. In Control Center 2601, "Keyboard and Mouse Sharing" is displayed around the phone, and "PC" is displayed around "Keyboard and Mouse Sharing," indicating that the PC's "Keyboard and Mouse Sharing" has been transferred to the phone. At this time, after the PC's keyboard and mouse have moved to the edge of the PC's interface, they can continue to move to the phone's interface, such as moving from the cursor position 26012 on the PC's interface 26011 to the cursor position 26014 on the phone's interface 26013. In this way, the PC's keyboard and mouse can be used to operate the phone.

[0205] In response to a user's click on the PC in the control center 2601, the PC can display... Figure 26 The control center shown is 2602. Unlike control center 2601, control center 2602 includes PC-centric services such as "screen sharing," "keyboard and mouse sharing," "file sharing," and "cross-device access." In this case, the PC's keyboard and mouse can still be used to operate the mobile phone.

[0206] In response to the user dragging "Keyboard and Mouse Sharing" from Control Center 2602 to the PAD, the PC can display... Figure 26The control center 2603 is shown. In control center 2603, "Keyboard and Mouse Sharing" is displayed not only around the phone but also around the tablet. Furthermore, a PC is also displayed around the "Keyboard and Mouse Sharing" icons, indicating that the "Keyboard and Mouse Sharing" from the PC has been further transferred to the tablet after being transferred to the phone. At this point, after the PC's keyboard and mouse have moved to the edge of the PC's interface, they can continue to move to the interfaces of the phone and tablet, such as moving from cursor position 26032 on the PC's interface 26031 to cursor position 26034 on the phone's interface 26033, or from cursor position 26035 on the PC's interface 26031 to cursor position 26037 on the phone's interface 26036. In this way, the PC's keyboard and mouse can be used to operate the phone and tablet.

[0207] In the aforementioned keyboard and mouse sharing configuration, the PC's keyboard and mouse can be shared to a mobile phone first, and then further shared to a tablet, thus enabling the "keyboard and mouse sharing" from the local machine to multiple target devices.

[0208] Specifically, for two electronic devices that both offer "keyboard and mouse sharing", after transferring the "keyboard and mouse sharing" feature from one electronic device to the other, the keyboard and mouse on the two electronic devices can be shared with each other.

[0209] For example, both PADs and PCs offer "keyboard and mouse sharing," see [link / reference]. Figure 27 The PC can display Figure 27 The control center 2701 is shown. Control center 2701 includes PC-centric services such as "screen sharing," "keyboard and mouse sharing," "file sharing," and "cross-device calling." At this time, there is no service flow between the PC and the PAD; for example, the PC's keyboard and mouse cannot be used to operate the PAD.

[0210] In response to the user dragging the "Keyboard and Mouse Sharing" option from the Control Center 2701 to the PAD, the PC can display... Figure 27 The control center 2702 is shown. In control center 2702, "Keyboard and Mouse Sharing" is displayed around the PAD, and the PC is also displayed around "Keyboard and Mouse Sharing," indicating that the PC's "Keyboard and Mouse Sharing" has been transferred to the PAD. Furthermore, in control center 2702, "Keyboard and Mouse Sharing" is displayed around the PC, and the PAD is also displayed around "Keyboard and Mouse Sharing," indicating that the PAD's "Keyboard and Mouse Sharing" has been transferred to the PC. At this time, the PC's keyboard and mouse can be shared with the PAD. For example, the PC's keyboard and mouse can move from cursor 27022 in the PC's interface 27021 to cursor 27024 in the PC's interface 27023, or the PAD's keyboard and mouse can move from cursor 27024 in the PAD's interface 27023 to cursor 27022 in the PC's interface 27021.

[0211] In practice, the control center can handle the flow of multiple services E, or multiple services F, or at least one service E and at least one service F. This allows for the flow of multiple services to one or more devices. For details, please refer to the previous explanation of the flow of services E and F; it will not be repeated here.

[0212] In particular, when multiple services from one device are transferred to another, the transfer can be completed in the following way.

[0213] Taking the example of transferring "keyboard and mouse sharing" and "screen sharing" from a PC to a PAD, in this example, the control device is the PC: In one specific implementation, see Figure 28 The PC can display Control Center 2801, which includes the PC's advantageous services: "Screen Sharing," "Keyboard and Mouse Sharing," "File Sharing," and "Cross-Platform Calling." At this time, there is no service flow between the PC and the PAD; for example, the PC's keyboard and mouse cannot be used to operate the PAD, and the PC's screen will not be shared with the PAD. In response to the user dragging the "Keyboard and Mouse Sharing" option from Control Center 2801 to the PAD, the PC can display... Figure 28 The control center 2802 is shown. In control center 2802, "Keyboard and Mouse Sharing" is displayed around the PAD, and "PC" is also displayed around "Keyboard and Mouse Sharing," indicating that the "Keyboard and Mouse Sharing" from the PC has been transferred to the PAD. At this time, after the PC's keyboard and mouse are moved to the edge of the PC's interface, they can continue to move to the phone's interface, such as moving from the cursor position 28022 in the PC's interface 28021 to the cursor position 28024 in the PAD's interface 28023. In this way, the PC's keyboard and mouse can be used to operate the PAD.

[0214] Subsequently, in response to the user's click operation on the PC in the control center 2802, the PC can display... Figure 28 The control center 2803 is shown. Control center 2803 is the same as control center 2801, and will not be described again here. At this time, the PC's keyboard and mouse can still operate the PAD. In response to the user dragging the "Screen Sharing" option from control center 2803 to the PAD, the PC can display... Figure 28 The control center 2804 is shown. In control center 2804, "Keyboard and Mouse Sharing" and "Screen Sharing" are displayed around the PAD. The PC is also displayed around "Keyboard and Mouse Sharing" and "Screen Sharing," indicating that the PC's "Keyboard and Mouse Sharing" and "Screen Sharing" have been transferred to the PAD. At this time, not only can the PC's keyboard and mouse be used to operate the PAD, but the PAD's interface 28041 also displays the PC's interface 28042.

[0215] In other words, multiple services from a source device can be dragged sequentially to the same target device from the control center of the control device, thereby enabling multiple services from one device to be transferred to another.

[0216] In another specific implementation, see Figure 29 The PC can display Control Center 2901, which includes the PC's premium services: "Screen Sharing," "Keyboard and Mouse Sharing," "File Sharing," and "Cross-Platform Calling." At this time, there is no service flow between the PC and the PAD; for example, the PC's keyboard and mouse cannot be used to operate the PAD, and the PC's screen is not shared with the PAD. In response to the user's consecutive clicks on "Keyboard and Mouse Sharing" and "Screen Sharing" in Control Center 2901, the PC can display Control Center 2902. In Control Center 2902, the PC's premium services "Keyboard and Mouse Sharing" and "Screen Sharing" are still displayed around the PC, but glued together. At this time, there is still no service flow between the PC and the PAD. In response to the user dragging the glued "Keyboard and Mouse Sharing" and "Screen Sharing" combined into a single unit 29021 from Control Center 2902 onto the PAD, the PC can display Control Center 2903. In control center 2903, "Keyboard and Mouse Sharing" and "Screen Sharing" are displayed around the PAD. A PC is also displayed around these, indicating that the PC's "Keyboard and Mouse Sharing" and "Screen Sharing" have been transferred to the PAD. At this time, after moving the PC's keyboard and mouse to the edge of the PC's interface, they can continue to move to the phone's interface, such as moving from cursor position 29032 in the PC's interface 29031 to cursor position 29034 in the PAD's interface 29033. Thus, the PC's keyboard and mouse can be used to operate the PAD. Furthermore, the PAD's interface 29033 also includes the PC's interface 29035.

[0217] In other words, by selecting multiple services from the source device in the control center of the control device, and then dragging the combined services to the target device, multiple services from one device can be quickly transferred to another.

[0218] After the service from the source device to the target device has been transferred through the aforementioned embodiments, the transfer can end when the user drags the service away from the target device. For example, after transferring "screen sharing" from the phone to the PAD, the phone can display... Figure 30The control center 3001 is shown. In control center 3001, "Screen Sharing" is displayed around the PAD, and "Phone" is also displayed around "Screen Sharing," indicating that the phone's "Screen Sharing" has been transferred to the PAD. In response to the user dragging the "Screen Sharing" icon around the PAD in control center 3001 along the dotted arrow away from the PAD, the phone can display... Figure 30 The control center 3002 is shown. In control center 3002, "screen sharing" is no longer displayed around the PAD, indicating that the transfer of "screen sharing" from the phone to the PAD has ended.

[0219] This application also provides an electronic device, which may include a display screen, a memory, and one or more processors (such as a CPU, GPU, NPU, etc.). The display screen, memory, and processor are coupled. The memory is used to store computer program code, which includes computer instructions. When the processor executes the computer instructions, the electronic device can perform various functions or steps performed by the device in the above method embodiments.

[0220] This application also provides a chip system including at least one processor and at least one interface circuit. The processor and the interface circuit are interconnected via lines. For example, the interface circuit can be used to receive signals from other devices (e.g., the memory of an electronic device). As another example, the interface circuit can be used to send signals to other devices (e.g., the processor). Exemplarily, the interface circuit can read instructions stored in the memory and send the instructions to the processor. When the instructions are executed by the processor, the electronic device can perform the steps in the above embodiments. Of course, the chip system may also include other discrete devices, and this application does not specifically limit this.

[0221] This embodiment also provides a computer storage medium storing computer instructions. When the computer instructions are executed on an electronic device, the electronic device performs the aforementioned method steps to implement the image processing method described above.

[0222] This embodiment also provides a computer program product that, when run on a computer, causes the computer to perform the aforementioned steps to implement the image processing method described above.

[0223] In addition, embodiments of this application also provide an apparatus, which may specifically be a chip, component, or module. The apparatus may include a connected processor and a memory; wherein the memory is used to store computer execution instructions, and when the apparatus is running, the processor may execute the computer execution instructions stored in the memory to cause the chip to execute the image processing methods in the above-described method embodiments.

[0224] In this embodiment, the electronic device, computer storage medium, computer program product or chip are all used to execute the corresponding method provided above. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects of the corresponding method provided above, and will not be repeated here.

[0225] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0226] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0227] The unit described as a separate component may or may not be physically separate. The component shown as a unit can be one physical unit or multiple physical units, that is, it can be located in one place or distributed in multiple different places. Some or all of the units can be selected to achieve the purpose of the solution in this embodiment according to actual needs.

[0228] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0229] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, essentially or in other words, the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0230] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application and are not intended to limit it. Although this application has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of this application without departing from the spirit and scope of the technical solutions of this application.

Claims

1. A control method for service flow between devices, characterized in that, Applied to a first electronic device, the method includes: The first interface is displayed, which includes a first device identifier and at least two associated device identifiers. The at least two associated device identifiers include a first associated device identifier and a second associated device identifier. The first device identifier indicates the first electronic device, the first associated device identifier indicates the first associated device, and the second associated device identifier indicates the second associated device. In response to a first trigger operation based on the first interface, a first service identifier is displayed around a first associated device identifier, the first service identifier indicating a first service provided by the first associated device; In response to the operation of dragging the first service identifier to the second associated device identifier, the first service identifier and the first associated device identifier are displayed around the second associated device identifier, and the first service provided by the first associated device is transferred to the second associated device; In response to the first trigger operation based on the first interface, the first service identifier is displayed around the first associated device identifier; In response to the operation of dragging the first service identifier to the first target device identifier, the first service identifier and the first associated device identifier are displayed around the first target device identifier, and the first service identifier and the first associated device identifier are kept displayed around the second associated device identifier, and the first service provided by the first associated device is transferred to the second associated device and the first target device; Wherein, the first target device identifier is one of the first device identifier and the at least two associated device identifiers, excluding the first associated device identifier and the second associated device identifier, and the first target device identifier indicates the first target device.

2. The method according to claim 1, characterized in that, The method further includes: In response to the operation of dragging the first service identifier to the second associated device identifier, the first service identifier surrounding the first associated device identifier is de-displayed.

3. The method according to claim 1 or 2, characterized in that, The step of responding to the operation of dragging the first service identifier to the first target device identifier, displaying the first service identifier and the first associated device identifier around the first target device identifier, and maintaining the display of the first service identifier and the first associated device identifier around the second associated device identifier includes: If the first service belongs to the second type of service, in response to the operation of dragging the first service identifier to the first target device identifier, the first service identifier and the first associated device identifier are displayed around the first target device identifier, and the first service identifier and the first associated device identifier are kept displayed around the second associated device identifier; The second type of service is one that can be transferred to multiple devices at the same time.

4. The method according to claim 3, characterized in that, The method further includes: If the first service belongs to the first type of service, in response to the operation of dragging the first service identifier to the first target device identifier, the first service identifier and the first associated device identifier are displayed around the first target device identifier, the first service identifier and the first associated device identifier are de-displayed around the second associated device identifier, the first service provided by the first associated device is transferred to the first target device, and the first service provided by the first associated device ends and is transferred to the first target device. The first type of service is one that can only be transferred to one device at a time.

5. The method according to any one of claims 1-4, characterized in that, The step of displaying a first service identifier around a first associated device identifier in response to a first trigger operation based on the first interface includes: In response to the first trigger operation based on the first interface, at least one target service identifier is displayed around the first associated device identifier, each target service identifier indicating a service provided by the first associated device, and the first service identifier is included among the at least one target service identifier; Before displaying the first service identifier and the first associated device identifier around the second associated device identifier in response to the operation of dragging the first service identifier to the second associated device identifier, the method further includes: In response to a second triggering operation on the first service identifier, the display of service identifiers other than the first service identifier among the at least one target service identifiers is canceled, and a prompt to drag the first service identifier to another device identifier to achieve service transfer is displayed.

6. The method according to any one of claims 1-5, characterized in that, After displaying the first service identifier and the first associated device identifier around the second associated device identifier, the method further includes: When the second electronic device plays audio through headphones, a second interface is displayed. The second interface includes a first device identifier, the at least two associated device identifiers, and the identifier of the headphones. The identifier of the headphones is displayed around the identifier of the second electronic device. The second electronic device is one of the at least two associated devices indicated by the first electronic device and the at least two associated device identifiers. In response to the operation of dragging the icon of the earphone to the icon of the second target device, the icon of the earphone is displayed around the icon of the second target device, and the icon of the earphone displayed around the second electronic device is canceled. The icon of the second target device indicates the second target device, the second target device plays audio through the earphone, and the second electronic device does not play audio through the earphone. The second target device identifier is one of the device identifiers other than the identifier of the second electronic device among the first device identifier and the at least two associated device identifiers.

7. The method according to any one of claims 1-6, characterized in that, The first service is a service for sharing a keyboard and / or mouse, the first associated device includes a keyboard and / or mouse, and the second associated device includes a keyboard and / or mouse; The method further includes: In response to the operation of dragging the first service identifier to the second associated device identifier, the first service identifier and the second associated device identifier are displayed around the first associated device identifier, and the first service provided by the second associated device is transferred to the first associated device.

8. The method according to any one of claims 1-7, characterized in that, After displaying the first service identifier and the first associated device identifier around the second associated device identifier, the method further includes: In response to a third trigger operation based on the first interface, a second service identifier and a third service identifier are displayed around the identifier of a third electronic device. The second service identifier indicates a second service, and the third service identifier indicates a third service. The second service and the third service are two services provided by the third electronic device, which is one of the at least two associated devices indicated by the first electronic device and the at least two associated device identifiers. In response to the selection operation of the second service identifier and the third service identifier, the second service identifier and the third service identifier are merged into a first control; In response to the operation of dragging the first control to the third target device identifier, the second service identifier and the third service identifier are displayed around the third target device identifier, and the identifier of the third electronic device is also included around the second service identifier and the third service identifier. The third target device identifier indicates the third target device, and the second service and the third service provided by the third electronic device are transferred to the third target device. The third target device identifier is a device identifier other than the identifier of the third electronic device among the first device identifier and the at least two associated device identifiers.

9. An electronic device, characterized in that, The electronic device includes: a display screen, a memory, and one or more processors; the one or more processors are coupled to the display screen and the memory; the memory is used to store computer program code, the computer program code including computer instructions, which, when executed by the one or more processors, cause the electronic device to perform the method as described in any one of claims 1-8.

10. A computer-readable storage medium comprising instructions, characterized in that, When the instructions are executed on an electronic device, the electronic device causes the electronic device to perform the method as described in any one of claims 1-8.

Images