Control method for service circulation between devices and electronic device

Abstract

The invention discloses a method for controlling service circulation between devices and an electronic device, and relates to the technical field of terminals. The method is applied to a first electronic device and comprises the steps that a first interface is displayed, and the first interface comprises a first device identifier and at least two associated device identifiers. And displaying a first service identifier around the first source device identifier based on a first operation of the first interface, the first service identifier indicating a first service provided by the first source device. And in response to an operation of dragging the first service identifier to the first target device identifier, displaying the first service identifier around the first target device identifier. And in response to an operation of dragging the first service identifier around the first target equipment identifier to the second target equipment identifier, displaying the first service identifier around the second target equipment identifier, and canceling the display of the first service identifier around the first target equipment identifier. In this way, the first electronic device can control the first service to quickly and automatically switch and circulate among the multiple target devices.

Description

[0001] This application claims the priority of the Chinese patent application filed with the State Intellectual Property Office on November 3, 2023, with application number 202311466653.4 and invention name “A multi-device collaborative control method and electronic device”, all contents of which are incorporated by reference in this application. Technical Field

[0002] The embodiments of the present application relate to the field of terminal technology, and more particularly to a method for controlling service flow between devices and an electronic device. Background Art

[0003] Electronic devices come in a variety of forms. For example, electronic devices may include mobile phones, tablets, laptops, etc. Each electronic device has its own unique advantages. For example, mobile phones have excellent shooting performance, and laptops have matching mice, keyboards, etc.

[0004] In the prior art, electronic devices can share each other's advantageous services to achieve service transfer between devices (also known as collaboration). For example, electronic devices such as tablets and laptops can share the screen of a mobile phone, thereby achieving the screen transfer of the mobile phone to electronic devices such as tablets and laptops.

[0005] As electronic devices become more and more diverse in form, and each type of electronic device provides more and more advantageous services, how to achieve flexible control over the flow of services has become an urgent problem that needs to be solved. Summary of the invention

[0006] The present application provides a method for controlling the flow of services between devices and an electronic device, which can realize flexible control of the flow of advantageous services provided by each device in the local machine.

[0007] In order to achieve the above objectives, this application adopts the following technical solutions:

[0008] In the first aspect, the present application provides a method for controlling the flow of services between devices, which is applied to a first electronic device (i.e., a control device, such as a mobile phone). Among them, a first interface (i.e., an interface including a control center) is displayed, and the first interface 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 device are devices added to the same trust ring. In response to a first trigger operation based on the first interface, a service identifier of an advantageous service provided by the first source device is displayed around the first source device identifier, such as the first service identifier of the first service (screen sharing, keyboard and mouse sharing, etc. hereinafter). Among them, the first source device identifier indicates the first source device. In response to the operation of dragging the first service identifier around the first source device identifier to the 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 flows to the target device. That is, in response to the user dragging the first service identifier from the first source device identifier 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] Further, in response to the operation of dragging the first service logo around the first target device logo to the second target device logo, the first service logo and the first source device logo are displayed around the second target device logo, but the first service logo and the first source device logo around the first target device logo are canceled, and the second target device logo indicates the second target device. In the case of canceling the display of the first service logo and the first source device logo around the target device logo, the first service provided by the first source device ends the flow to the target device. That is, after the first service is transferred to the first target device, in response to the user continuing to drag the first service logo from the first target device logo to the second target device logo, 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 of ending the flow, and then switch the flow to the second target device based on the user's operation of transferring the first service to the second target device. Thereby, the first service can be quickly and automatically switched between multiple target devices.

[0010] 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. In other words, the first source device, the first target device, and the second target device are three different devices in the same trust ring. It can be seen that the first electronic device can control the flow of services provided by any electronic device in the trust ring to other electronic devices.

[0011] In a possible design of the first aspect, the first source device and the first target device are two of the at least two associated devices indicated by the at least two associated device identifiers. That is, neither the first source device nor the first target device is the first electronic device. It can be seen that the first electronic device can control the service to flow between other electronic devices in the trust ring except the first electronic device.

[0012] In a possible design of the first aspect, in response to the operation of dragging the first service logo around the first target device logo to the second target device logo, the first service logo and the first source device logo are displayed around the second target device logo, including: if the first service belongs to the first category of services, in response to the operation of dragging the first service logo around the first target device logo to the second target device logo, the first service logo and the first source device logo are displayed around the second target device logo.

[0013] Among them, the first category of services are services that can only flow to one target device at the same time. Then, in the case where the first service has flowed to the first target device, if it is detected that the user drags the first service logo from the first target device logo to the second target device logo, the first service can only be switched to flow to the second target device, and it is impossible to further flow to the second target device. Therefore, it can be predicted that the user's intention is to switch the first service from flowing to the first target device to flowing to the second target device. In response to this intention, the first electronic device displays the first service logo and the first source device logo around the second target device logo, and cancels the display of the first service logo and the first source device logo around the first target device logo. In this way, the response of the first electronic device can more accurately match the user's intention.

[0014] In addition, if the first service is a second-category service, and the second-category service is a service that can flow to multiple target devices at the same time, then, when the first service has flowed to the first target device, if it is detected that the user drags the first service logo from the first target device logo to the second target device logo, it may be that the user wants to switch the first service to the second target device, or it may be that the first service is further transferred to the second target device, so the user's intention is difficult to accurately predict. Therefore, if the first service is a second-category service, in response to the user dragging the first service logo around the first target device logo to the second target device logo (i.e., dragging from the first target device logo to the second target device logo), the first electronic device will still keep displaying the first service logo and the first source device logo around the first target device logo, that is, it will not cancel the first service logo and the first source device logo displayed around the first target device logo; and the first electronic device will not display the first service logo and the first source device logo around the second target device logo. In this way, the first electronic device can avoid responding incorrectly.

[0015] In a possible design mode of the first aspect, the method further includes: in response to the operation of dragging the first service logo around the first source device logo to the first target device logo, canceling the display of the first service logo around the first source device logo. In this way, the first electronic device can ensure that after the first service is transferred, the first service logo around the first source device is canceled to avoid interfering with the user's judgment. In addition, after the first service logo and the first source device logo are displayed around the second target device logo, the method further includes: in response to the first trigger operation based on the first interface, the first service logo is displayed around the first source device logo, that is, the service provided by the first source device is displayed again. In response to the operation of dragging the first service logo around the first source device logo to the first target device logo again, the first service logo and the first source device logo are displayed around the first target device logo, and the display of the first service logo and the first source device logo around the second target device logo is canceled. That is, in the case where the first service has been transferred to the second target device, in response to the operation of the user dragging the first service logo around the first source device logo to the first target device logo again, the first electronic device can also realize the switching of the first service from being transferred to the second target device to being transferred to the first target device. This provides a method for quickly and automatically switching the flow of the first service between multiple target devices, without the need for 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 transfer the first service to the first target device.

[0016] In a possible design manner of the first aspect, in response to the operation of dragging the first service logo around the first source device logo to the first target device logo again, the first service logo and the first source device logo are displayed around the first target device logo, and the first service logo and the first source device logo around the second target device logo are canceled, including: if the first service belongs to the first category of services, in response to the operation of dragging the first service logo around the first source device logo to the first target device logo again, the first service logo and the first source device logo are displayed around the first target device logo, and the first service logo and the first source device logo around the second target device logo are canceled.

[0017] In the case where the first service has been transferred to the second target device, if it is detected that the user drags the first service logo from the first source device logo to the first target device logo again, it is generally considered that the user's intention is to further transfer the first service to the first target device. However, since the first category of services are services that can only be transferred to one target device at the same time. Therefore, the user's intention can only be considered to be: to switch the first service from flowing to the second target device to flowing to the first target device. In response to this intention, the first electronic device displays the first service logo and the first source device logo around the first target device logo, and cancels the display of the first service logo and the first source device logo around the second target device logo. Thereby, the first service is switched from flowing to the second target device to flowing to the first target device. In this way, the response of the first electronic device can meet the characteristics of the service.

[0018] In a possible design of the first aspect, the method further includes: if the first service belongs to the second category of services, in response to the operation of dragging the first service logo around the first source device logo to the first target device logo again, the first service logo and the first source device logo are displayed around the first target device logo, and the first service logo and the first source device logo are kept displayed around the second target device logo.

[0019] As analyzed above, when the first service has been transferred to the second target device, if it is detected that the user drags the first service logo from the first source device logo to the first target device logo again, it is generally considered that the user's intention is to further transfer the first service to the first target device. In addition, the second type of service is a service that can be transferred to multiple target devices at the same time, that is, the first service can also be transferred to multiple target devices. Then, it can be determined that the user's intention is 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 logo and the first source device logo around the second target device logo, and further display the first service logo and the first source device logo around the first target device logo. Thereby, the first service is further transferred to the first target device when it is 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 a possible design of the first aspect, in response to the first trigger operation based on the first interface, displaying the first service identifier around the first source device identifier includes: in response to the first trigger operation based on the first interface, displaying at least one target service identifier around the first source device identifier, each target service identifier indicating a service provided by the first source device, and 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 the service identifiers of all services provided by the first source device. Accordingly, in response to the operation of dragging the first service identifier around the first source device identifier to the first target device identifier, before displaying the first service identifier and the first source device identifier around the first target device identifier, the method further includes: in response to the second trigger operation of the first service identifier around the first source device, canceling the display of service identifiers other than the first service identifier in at least one target service identifier, and displaying a prompt to drag the first service identifier to the target device identifier to realize service transfer.

[0021] In this way, when the user is not familiar with the operation of service transfer, such as not knowing that the first service identifier must be dragged to the target device identifier to realize the service transfer, the user can perform a second trigger operation on the first service identifier, such as a click operation, to trigger the first electronic device to prompt the service transfer operation, such as dragging the first service identifier to the target device identifier to realize the service transfer. Thus, the user can be guided to complete the service transfer operation.

[0022] In a 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. In response to an operation of dragging the first service identifier around the first source device identifier to the first target device identifier, the first service identifier and the first source device identifier are displayed around the first target device identifier, including: in response to an operation of dragging the first sub-service identifier around the first source device identifier to the first target device identifier, the first sub-service identifier and the first source device identifier are displayed around the first target device identifier.

[0023] That is to say, for the first service including multiple sub-services, the first electronic device can complete the flow of corresponding sub-services based on the user dragging the sub-service identifiers.

[0024] In a possible design of the first aspect, the first service includes a first sub-service and a second sub-service. After the first service logo and the first source device logo are displayed around the first target device logo in response to the operation of dragging the first service logo around the first source device logo to the first target device logo, the method further includes: in response to a first message, the first sub-service logo and the first source device logo are displayed around the first target device logo, the first message indicates that the first target device selects the first sub-service, and the first sub-service logo indicates the first sub-service.

[0025] Among them, in response to the operation of dragging the first service logo around the first source device logo to the first target device logo, the first electronic device will first send a notification of the flow of the first service to the first target device. In response to the notification of the flow of the first service, the first target device can display options for the first sub-service and options for the second sub-service for the user to select the sub-service that needs to be transferred. In response to the user's selection operation on the option of the first sub-service, the first target device can send a first message to the first electronic device to indicate that the first target device has selected the first sub-service. In this way, the first electronic device can clearly know that the first sub-service needs to be transferred, so the first sub-service logo and the first source device logo are displayed around the first target device logo.

[0026] In a possible design of the first aspect, after the first service identifier and the first source device identifier are displayed around the second target device identifier, the method further includes: when the second electronic device plays audio through headphones, a second interface is displayed, the second interface includes the first device identifier, 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, and 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. When the identifier of the headphones is displayed around the identifier of any electronic device, the audio of the any electronic device is played through the headphones.

[0027] Further, in response to the operation of dragging the earphone logo to the third target device logo, the earphone logo is displayed around the third target device logo, but the earphone logo displayed around the second electronic device is cancelled. The third target device logo indicates the third target device; when the earphone logo around the logo of the second electronic device is cancelled, the audio of the second electronic device is not played through the earphone. The third target device logo is a device logo other than the logo of the second electronic device among the first device logo and at least two associated device logos. In this way, the user can trigger the first electronic device to switch the earphone to play videos of different devices by dragging the earphone logo, such as switching from playing the audio of the second electronic device to playing the audio of the third target device.

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

[0029] That is to say, the operation of dragging the service identifier of the shared keyboard and / or mouse from the first source device identifier to the first target device identifier can not only trigger the shared keyboard and / or mouse service provided by the first source device to flow to the first target device, so that the first target device can use the keyboard and / or mouse of the first source device; but also trigger the shared keyboard and / or mouse service provided by the first target device to flow to the first source device, so that the first source device can use the keyboard and / or mouse of the first target device. In this way, the exchange of the shared keyboard and / or mouse services of the two devices can be realized quickly.

[0030] In a possible design mode of the first aspect, after the first service identifier and the source device identifier are displayed around the second target device identifier, the method further includes: based on the third trigger operation of the first interface, the second service identifier and the third service identifier are displayed around the second source device identifier, the second service identifier indicates the second service, the third service identifier indicates the third service, and the second service and the third service are two services provided by the second source device indicated by the second source device identifier. In response to the sequential click operation on the second service identifier and the third service identifier, such as first clicking the second service identifier and then quickly clicking the third service identifier, the second service identifier and the third service identifier are merged into the first control. In response to the 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 included around the second service identifier and the third service identifier. The fourth target device identifier indicates the fourth target device, the second source device identifier and the fourth target device identifier are two device identifiers among the first device identifier and the at least two associated device identifiers, and the second source device identifier and the fourth target device identifier are different.

[0031] In the case where any service identifier and the 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 flows to the fourth target device. Then, if the second service identifier and the third service identifier are displayed around the fourth target device identifier, and the second service identifier and the third service identifier are also surrounded by the second source device identifier, it means that both the second service and the third service provided by the second source device flow to the fourth target device.

[0032] That is, the first electronic device can combine the second service identifier and the third service identifier into a first control, and then, in response to the user's dragging operation on the first control, simultaneously transfer the second service and the third service from the second source device to the fourth target device. In this way, multiple services can be transferred simultaneously, thereby improving the efficiency of human-computer interaction.

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

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

[0035] In a possible design of the first aspect, when the third electronic device has been connected to a printer, the at least two associated device identifiers include an identifier of the printer, wherein 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] That is to say, the printer can be added to the trust ring by establishing a connection with the devices in the trust ring. In this way, even printers produced by other manufacturers can be added to the trust ring so that the devices in the trust ring can use the printing service.

[0037] In the second aspect, the present application provides a control method for the flow of services between devices (corresponding to the flow form three below), which is applied to a first electronic device. The method includes: displaying a first interface, the first interface 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 a first electronic device, the first associated device identifier indicates a first associated device, and the second associated device identifier indicates 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, and the first service identifier indicates 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 flows to the second associated device.

[0038] It can be seen that the first electronic device can control the service to flow between other electronic devices (ie, the first associated device and the second associated device) in the trust ring except the first electronic device.

[0039] In a possible design of the second aspect, the method further includes: in response to the operation of dragging the first service logo to the second associated device logo, canceling the first service logo displayed around the first associated device logo. In this way, the first electronic device can ensure that after the first service is transferred, the first service logo around the first source device is canceled to avoid interfering with the user's judgment.

[0040] After the first service logo and the first associated device logo are displayed around the second associated device logo, the method further includes: in response to the first trigger operation based on the first interface, the first service logo is displayed around the first associated device logo. In response to the operation of dragging the first service logo to the first target device logo, the first service logo and the first associated device logo are displayed around the first target device logo, the first service logo and the first associated device logo are kept displayed around the second associated device logo, and the first service provided by the first associated device flows to the second associated device and the first target device. The first target device logo is the first device logo and one of the at least two associated device logos other than the first associated device logo and the second associated device logo, and the first target device logo indicates the first target device.

[0041] In the case where the first service has been transferred to the second associated device, if it is detected that the user drags the first service logo from the first associated device logo to the first target device logo again, it is generally considered that the user intends 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 meet the user's intention.

[0042] In a possible design of the second aspect, in response to the operation of dragging the first service logo to the first target device logo, the first service logo and the first associated device logo are displayed around the first target device logo, and the first service logo and the first associated device logo are kept displayed around the second associated device logo, including: if the first service belongs to the second category of services, in response to the operation of dragging the first service logo to the first target device logo, the first service logo and the first associated device logo are displayed around the first target device logo, and the first service logo and the first associated device logo are kept displayed around the second associated device logo. Wherein, the second category of services are services that can be transferred to multiple devices at the same time.

[0043] As analyzed above, when the first service has been transferred to the second associated device, if it is detected that the user drags the first service logo from the first associated device logo to the first target device logo again, it is generally considered that the user's intention is to further transfer the first service to the first target device. In addition, the second type of service is a service that can be transferred to multiple devices at the same time, that is, the first service can be transferred to multiple devices. Then, it can be determined that the user's intention is 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 logo and the first associated device logo around the second associated device logo, and further display the first service logo and the first associated device logo around the first target device logo. Thereby, the first service is further transferred to the first target device when it is 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 a possible design of the second aspect, the method further includes: if the first service belongs to the first category of services, in response to the operation of dragging the first service logo to the first target device logo, the first service logo and the first associated device logo are displayed around the first target device logo, the first service logo and the first associated device logo are displayed around the second associated device logo, 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 transferring to the first target device. The first category of services are services that can only be transferred to one device at a time.

[0045] In the case where the first service has been transferred to the second associated device, if it is detected that the user drags the first service logo from the first associated device logo to the first target device logo again, it is generally considered that the user's intention is to further transfer the first service to the first target device. However, since the first category of services are services that can only be transferred to one device at the same time. Therefore, the user's intention can only be considered to be: to switch the first service from flowing to the second associated device to flowing to the first target device. In response to this intention, the first electronic device displays the first service logo and the first associated device logo around the first target device logo, and cancels the display of the first service logo and the first associated device logo around the second associated device logo. Thereby, the first service is switched from flowing to the second associated device to flowing to the first target device. In this way, the response of the first electronic device can meet the characteristics of the service.

[0046] In a possible design of the second aspect, in response to a first trigger operation based on a first interface, displaying a first service identifier around a first associated device identifier includes: in response to the first trigger operation based on the first interface, displaying at least one target service identifier around the first associated device identifier, each target service identifier indicating a service provided by the first associated device, and at least one target service identifier including the first 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 the second associated device identifier, the method further includes: in response to a second trigger operation on the first service identifier, canceling the display of service identifiers other than the first service identifier in at least one target service identifier, and displaying a prompt to drag the first service identifier to other device identifiers to realize service transfer.

[0047] In this way, when the user is not familiar with the operation of service transfer, such as not knowing that the first service identifier must be dragged to the target device identifier to realize the service transfer, the user can perform a second trigger operation on the first service identifier, such as a click operation, to trigger the first electronic device to prompt the service transfer operation, such as dragging the first service identifier to another device identifier to realize the service transfer. Thus, the user can be guided to complete the service transfer operation.

[0048] In a possible design of the second aspect, after the first service logo and the first associated device logo are displayed around the second associated device logo, the method further includes: when the second electronic device plays audio through headphones, a second interface is displayed, the second interface includes the first device logo, at least two associated device logos and the logo of the headphones, the logo of the headphones is displayed around the logo of the second electronic device, and 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 logos. In response to the operation of dragging the logo of the headphones to the second target device logo, the logo of the headphones is displayed around the second target device logo, the logo of the headphones displayed around the second electronic device is cancelled, the second target device logo indicates the second target device, the second target device plays audio through the headphones, and the second electronic device does not play audio through the headphones. Wherein, the second target device logo is a device logo other than the logo of the second electronic device among the first device logo and the at least two associated device logos.

[0049] In this way, the user can trigger the first electronic device to switch the earphone to play videos of different devices by dragging the earphone logo, such as switching from playing the audio of the second electronic device to playing the audio of the second target device.

[0050] In a possible design of the second aspect, the first service is a service for sharing a keyboard and / or a mouse, the first associated device includes a keyboard and / or a mouse, and the second associated device includes a keyboard and / or a mouse. The above method further includes: in response to an 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.

[0051] That is to say, the operation of dragging the service identifier of the shared keyboard and / or mouse from the first associated device identifier to the second associated device identifier can not only trigger the shared keyboard and / or mouse service provided by the first associated device to flow to the second associated device, so that the second associated device can use the keyboard and / or mouse of the first associated device; but also trigger the shared keyboard and / or mouse service provided by the second associated device to flow to the first associated device, so that the first associated device can use the keyboard and / or mouse of the second associated device. In this way, the exchange of the shared keyboard and / or mouse services of the two devices can be realized quickly.

[0052] In a possible design mode of the second aspect, after the first service identifier and the first associated device identifier are displayed around the second associated device identifier, the method further includes: in response to a third trigger operation based on the first interface, displaying a second service identifier and a third service identifier around the identifier of the third electronic device, the second service identifier indicates a second service, the third service identifier indicates a third service, the second service and the third service are two services provided by the third electronic device, and 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. In response to a 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 an 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 second service identifier and the third service identifier also include an identifier of the third electronic device around the second service identifier and the third service identifier, the third target device identifier indicates the third target device, the second service and the third service provided by the third electronic device flow to the third target device, and 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.

[0053] That is, the first electronic device can combine the second service identifier and the third service identifier into a first control, and then, in response to the user's dragging operation on the first control, simultaneously transfer the second service and the third service from the third electronic device to the third target device. In this way, multiple services can be transferred simultaneously, thereby improving the efficiency of human-computer interaction.

[0054] For effects not described in detail in the above-mentioned second aspect and possible design methods, please refer to the description in the first aspect and possible design methods, and no further details will be given here.

[0055] In a third aspect, the present application provides a communication system, the communication system comprising a first electronic device and at least two associated devices. The first electronic device is configured to display a first interface, the first interface 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 fourth electronic device is configured to display a third interface, the fourth electronic device is one of the at least two associated devices, and the third interface includes the first device identifier and at least two associated device identifiers. The first electronic device is configured to respond to a first trigger operation based on the first interface, and display a first service identifier around the first source device identifier in the first interface; the first source device identifier indicates the first source device, and the first service identifier indicates the first service provided by the first source device. In response to the operation of dragging the first service identifier around the first source device identifier in the first interface to the 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 the 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 the first service identifier around the first source device identifier in the first interface to the first target device identifier: the first electronic device is configured to display the first service identifier and the first source device identifier around the second target device identifier in the first interface, but cancel the display of the first service identifier and the first source device identifier around the first target device identifier in the first interface; the fourth electronic device is configured to display the first service identifier and the first source device identifier around the second target device identifier in the third interface, but cancel the display of 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; and the first service provided by the first source device ends and flows to the first target device. Among them, 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] In a fourth aspect, the present application further provides an electronic device, the electronic device comprising a display screen, a memory, and one or more processors. The display screen, the memory, and the processor are coupled. The memory is used to store computer program code, the computer program code comprising computer instructions, when the computer instructions are executed by the processor, the electronic device executes the method in the first aspect and any possible design thereof.

[0057] In a fifth aspect, the present application provides a chip system, which is 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 circuit and the processor are interconnected through lines; the interface circuit is used to receive signals from the memory of the electronic device and send signals to the processor, and the signals include computer instructions stored in the memory; when the processor executes the computer instructions, the electronic device executes the method as in the first aspect and any possible design method thereof.

[0058] In a sixth aspect, the present application provides a computer storage medium, which includes computer instructions. When the computer instructions are executed on an electronic device, the electronic device executes the method as in the first aspect and any possible design thereof.

[0059] In a seventh aspect, the present application provides a computer program product, which, when executed on a computer, enables the computer to execute the method of the first aspect and any possible design thereof.

[0060] It can be understood that the beneficial effects that can be achieved by 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 provided above can be referred to the beneficial effects of the first aspect and any possible design method thereof, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0062] Figure 2 A schematic diagram of a service flow process provided in an embodiment of the present application;

[0063] Figure 3 A hardware structure diagram of a mobile phone provided in an embodiment of the present application;

[0064] Figure 4 One of the interface diagrams of the mobile phone provided in the embodiment of the present application;

[0065] Figure 5 The second interface diagram of the mobile phone provided in the embodiment of the present application;

[0066] Figure 6 One of the principle diagrams of the service flow provided in the embodiment of the present application;

[0067] Figure 7 The second schematic diagram of the service flow provided in the embodiment of the present application;

[0068] Figure 8 The third schematic diagram of the service flow provided in the embodiment of the present application;

[0069] Fig. 9 The fourth schematic diagram of the service flow provided in the embodiment of the present application;

[0070] Fig.10 The fifth schematic diagram of the service flow provided in the embodiment of the present application;

[0071] Fig.11 The sixth schematic diagram of the service flow provided in the embodiment of the present application;

[0072] Fig.12 The seventh schematic diagram of the service flow provided in the embodiment of the present application;

[0073] Fig.13 The eighth schematic diagram of the service flow provided in the embodiment of the present application;

[0074] Fig.14 The ninth schematic diagram of the service flow provided in the embodiment of the present application;

[0075] Fig.15 The tenth schematic diagram of the service flow provided in the embodiment of the present application;

[0076] Fig.16 The eleventh schematic diagram of the service flow provided in the embodiment of the present application;

[0077] Fig.17 The twelve schematic diagrams of the service flow provided in the embodiments of the present application;

[0078] Fig.18 Thirteenth schematic diagram of the service flow provided in the embodiment of the present application;

[0079] Fig.19 The fourteenth schematic diagram of the service flow provided in the embodiment of the present application;

[0080] Fig. 20 The fifteenth schematic diagram of the service flow provided in the embodiment of the present application;

[0081] Fig.21 The sixteenth schematic diagram of the service flow provided in the embodiment of the present application;

[0082] Fig. 22 The seventeenth schematic diagram of the service flow provided in the embodiment of the present application;

[0083] Fig.23 The eighteenth schematic diagram of the service flow provided in the embodiment of the present application;

[0084] Fig.24 The nineteenth schematic diagram of the service flow provided in the embodiment of the present application;

[0085] Fig.25 Schematic diagram 20 of the service flow provided in the embodiment of the present application;

[0086] Fig.26 Schematic diagram 21 of the service flow provided in the embodiment of the present application;

[0087] Fig. 27 Schematic diagram 22 of the service flow provided in the embodiment of the present application;

[0088] Fig.28 Schematic diagram 23 of the service flow provided in the embodiment of the present application;

[0089] Fig.29 Schematic diagram 24 of the service flow provided in the embodiment of the present application;

[0090] Fig.30 This is the twenty-fifth schematic diagram of the service flow provided for the embodiment of the present application. DETAILED DESCRIPTION

[0091] The technical solutions in the embodiments of the present application are described below in conjunction with the drawings in the embodiments of the present application. Among them, in the description of the embodiments of the present application, the terms used in the following embodiments are only for the purpose of describing specific embodiments, and are not intended to be used as limitations on the present application. As used in the specification and the appended claims of the present application, the singular expressions "a", "said", "above", "the" and "this" are intended to also include expressions such as "one or more", unless there is a clear indication to the contrary in the context. It should also be understood that in the following embodiments of the present application, "at least one", "one or more" refer to one or more (including two). The term "and / or" is used to describe the association relationship of associated objects, indicating that three relationships can exist; for example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the associated objects before and after are in a "or" relationship.

[0092] References to "one embodiment" or "some embodiments" etc. described in this specification mean that one or more embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Thus, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways. The term "connection" includes direct connection and indirect connection, unless otherwise specified. "First" and "second" are used for descriptive purposes only and cannot be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated.

[0093] In the embodiments of the present 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 the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplarily" or "for example" is intended to present related concepts in a specific way.

[0094] The control method for inter-device service flow provided in the embodiment of the present application can be applied to the communication system provided in the embodiment of the present application. The communication system includes multiple electronic devices. Any electronic device can be a mobile phone, a tablet (PAD), a large screen (i.e., a smart TV, also known as a smart screen), etc. Not limited to this, the electronic device can also be a personal computer (personal computer, PC), a personal digital assistant (personal digital assistant, PDA), an augmented reality (augmented reality, AR) device, a virtual reality (virtual reality, VR) device, a car machine, a printer, a headset, and other devices with near-field or far-field communication functions. Among them, PC includes desktop computers and laptop computers. The following mainly takes the PC as a laptop computer as an example to illustrate the present application scheme.

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

[0096] The same user account (such as a Honor account) is logged into multiple electronic devices in the communication system, or user accounts with a trust relationship such as mutual family accounts and mutual workgroup accounts are logged into multiple electronic devices. The following mainly takes logging into the same user account as an example.

[0097] It is understandable that multiple electronic devices logged into the same user account can be added to the same trust ring through identity authentication.

[0098] In particular, for a printer, if an electronic device in the trust circle has used the printer, the printer can also pass identity authentication and join the trust circle. Furthermore, if the printer is in the whitelist, it can pass identity authentication. Figure 1 Taking the communication system shown in FIG. 1 as an example, if the mobile phone 110 has used a printer and the printer is in the white list, the printer can also be added to the Figure 1 In the communication system shown, Figure 1 In this way, even a printer that cannot log in to the same user account as a mobile phone, PAD, PC or other electronic device can be flexibly added to the trust circle so that the electronic devices in the trust circle can use the printing service provided by the printer.

[0099] In particular, for a headset, if an electronic device in the trust ring is connected to the headset, the headset can also be added to the trust ring. Figure 1 As an example of the communication system shown in FIG. 1 , if the mobile phone 110 is connected to the headset, the headset can also be added to the Figure 1 In the communication system shown in FIG. , the headset can be more conveniently added to the trust loop.

[0100] Multiple electronic devices can communicate through short-range communication or long-range communication, such as identity authentication, data transmission for service flow, etc.

[0101] Among them, short-range communication can include Bluetooth communication, Near Field Communication (NFC), wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) network) communication, etc. Correspondingly, if short-range communication between electronic devices is to be achieved, the electronic device needs to turn on the corresponding communication switch, such as turning on the Bluetooth switch, the WLAN switch, etc. It should be noted that if only the WLAN switch is turned on, it is necessary to ensure access to the WLAN network to achieve communication. Normally, before joining the trust ring, the electronic device can prompt to turn on Bluetooth and WLAN, so that when the WLAN network is accessed, the WLAN network can be used for communication, and even if the WLAN network is not accessed, Bluetooth communication can be used. Of course, in some technologies, if the WLAN switch is turned on but the WLAN network is not accessed, the electronic device can also communicate through WLAN direct connection.

[0102] Remote communication refers to communication when each device is connected to a network (such as a 3G, 4G, 5G, 6G, etc. mobile network and / or a WLAN network). Accordingly, if remote communication between electronic devices is to be achieved, the electronic devices need to turn on the corresponding network switch (such as a mobile communication switch, a WLAN switch) and connect to the network.

[0103] After joining the trust ring, any electronic device in the trust ring can call the advantage services of other electronic devices except the electronic device, realizing the service flow between devices.

[0104] In some implementations, multiple electronic devices in the above communication system can be controlled on a device-by-device basis to implement service transfer between devices. Figure 1 Taking the communication system shown in FIG. 1 as an example, after the mobile phone 110, PAD 120, PC 130 and large screen 140 are added to the same trust ring, the mobile phone 110 can view Figure 2 As shown, the local device, i.e., the mobile phone 110, is the center, and the PAD 120, PC 130, and large screen 140 are the control center 201 of the ring devices. In response to the user dragging the PAD 120 in 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 2 The control center 202 shown. The difference from the control center 201 is that the PAD 120 in the control center 202 is adsorbed on the mobile phone 110. At this time, the default service of the mobile phone 110 (such as screen sharing) will be established between the mobile phone 110 and the PAD 120. In addition, all services provided by the mobile phone 110 and the PAD 120, such as "screen sharing", "network sharing", and "file sharing", can be displayed below the mobile phone 110 for a certain period of time, so as to switch the flowing service, such as switching from the default "screen sharing" to "network sharing".

[0105] However, the above Figure 2 The control scheme shown, on the one hand, can only establish the flow of the default service first, and cannot directly control the flow of the target service. Furthermore, for services provided by two collaborative devices (such as mobile phone 110 and PAD120), when the user chooses one of them to switch, he cannot clearly identify the device providing the service. For example, mobile phone 110 and PAD 120 both provide the "screen sharing" service, then the user cannot clearly select "screen sharing" to transfer the "screen sharing" of mobile phone 110 to PAD120, or to transfer the "screen sharing" of PAD120 to mobile phone 110. On the other hand, only the service flow between the local machine and the devices on the ring can be realized, but the service flow between the local machine and any two devices on the ring cannot be realized.

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

[0107] Based on the above problems, the embodiment of the present application provides a control method for the flow of services between devices. In any electronic device among multiple electronic devices, the flow of a target service provided by one electronic device to another electronic device can be directly controlled. That is, the source device providing the service, the target service, and the target device using the service can be clearly defined at the same time; and the flow of services is not limited to the flow between the device and other electronic devices. Thereby, the accuracy and flexibility of service flow can be improved.

[0108] For example, if the trust ring includes a mobile phone, a PAD, and a PC, and the local device is a mobile phone, then in the mobile phone, not only can the service flow between the mobile phone and the PAD, the mobile phone and the PC be controlled, but also the service flow between the PAD and the PC can be controlled. For example, the keyboard and mouse service flow of the PC can be transferred to the PAD, so that the keyboard and mouse of the PC can be used as the input of the PAD.

[0109] The following uses a mobile phone as an example to illustrate the hardware structure of any electronic device among multiple electronic devices. Figure 3 As shown, the 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, an earphone interface 270D, a sensor module 280, a button 290, a motor 291, an indicator 292, a camera 293, a display screen 294, and a subscriber identification module (SIM) card interface 295, etc.

[0110] It is to be 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 shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

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

[0112] The charging management module 240 is used to receive charging input from a charger. The charger can be a wireless charger or a wired charger. While the charging management module 240 charges the battery 242, it can also power the electronic device through the power management module 241.

[0113] The power management module 241 is used to connect 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, the internal memory 221, the external memory, the display screen 294, the camera 293, and the wireless communication module 260. In some embodiments, the power management module 241 and the charging management module 240 can also be set in the same device.

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

[0115] The mobile communication module 250 can provide solutions for wireless communications including 2G / 3G / 4G / 5G, etc., applied on mobile phones. The wireless communication module 260 can provide solutions for wireless communications including WLAN (such as (wireless fidelity, Wi-Fi) network), Bluetooth (bluetooth, BT), global navigation satellite system (global navigation satellite system, GNSS), frequency modulation (frequency modulation, FM), near field communication technology (near field communication, NFC), infrared technology (infrared, IR), etc., applied on mobile phones.

[0116] In some embodiments, the mobile phone can establish a trust ring with other electronic devices, transmit data for service flow, etc. through the mobile communication module 250 or the wireless communication module 260.

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

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

[0119] The external memory interface 212 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the mobile phone. The external memory card communicates with the processor 211 through the external memory interface 212 to implement a data storage function. For example, files such as music and videos can be stored in the external memory card.

[0120] The internal memory 221 may be used to store computer executable program codes, which include instructions. The processor 211 executes various functional applications and data processing of the mobile phone by running the instructions stored in the internal memory 221. For example, in an embodiment of the present application, the processor 211 may execute the instructions stored in the internal memory 221, and the internal memory 221 may include a program storage area and a data storage area.

[0121] The mobile phone can realize audio functions such as music playing and recording through the audio module 270, the speaker 270A, the receiver 270B, the microphone 270C, the earphone interface 270D, and the application processor.

[0122] The button 290 includes a power button, a volume button, etc. The button 290 can be a mechanical button. It can also be a touch button. The motor 291 can generate a vibration prompt. The motor 291 can be used for incoming call vibration prompts, and can also be used for touch vibration feedback. The indicator 292 can be an indicator light, which can be used to indicate the charging status, power changes, messages, missed calls, notifications, etc. The SIM card interface 295 is used to connect the SIM card. The SIM card can be inserted into the SIM card interface 295, or pulled out from the SIM card interface 295 to achieve contact and separation with the mobile phone. The mobile phone can support 1 or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 295 can support Nano SIM cards, Micro SIM cards, SIM cards, etc.

[0123] Furthermore, the software architecture of the electronic device may adopt a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture or a cloud architecture. The embodiments of the present application do not specifically limit this.

[0124] The control method for inter-device service flow provided in the embodiment of the present application can be executed in a mobile phone having the above-mentioned software and hardware structure. That is, the control device can be a mobile phone. In practice, the control device can also be any device in the trust ring. In the following, unless otherwise specified, the control device is a mobile phone.

[0125] The mobile phone includes a control center of the trust ring, and the control center is used to control the service flow between multiple electronic devices in the trust ring. In the embodiment of the present application, the method of entering the control center is not specifically limited. The following only introduces two exemplary methods of entering the control center.

[0126] Method 1: The mobile phone can display the control center in response to the user's three-finger swipe up operation in the current interface.

[0127] The current interface is Figure 4 Taking the interface 401 shown as an example, the interface 401 is the desktop of the mobile phone. In response to the user's three-finger upward swipe operation in the interface 401, the mobile phone can display Figure 4 The interface 402 shown includes a control center 4021 .

[0128] In the second method, the mobile phone can display a drop-down menu interface in response to the user sliding down from the top right side of the current interface, and the drop-down menu interface includes an entrance to the control center. In response to the user triggering operation on the entrance to the control center, such as a click operation, the mobile phone displays the control center.

[0129] The current interface is Figure 4 Take the interface 403 shown in the figure as an example, the interface 403 is the desktop of the mobile phone. In response to the user sliding down from the top right side of the interface 403, the mobile phone can display Figure 4The interface 404 shown is a drop-down menu interface. The interface 404 includes an entry 4041 of the control center. In response to the user clicking the entry 4041 of the control center, the mobile phone can also display Figure 4 Interface 402 is shown.

[0130] Above Figure 4 In the two methods shown, the current interface is taken as an example of a desktop, but it is not limited to this in practice. For example, the current interface can also be an application interface of an application such as a chat application, a video application, etc.

[0131] The control center includes multiple electronic devices in the trust ring. Figure 4 Taking the control center 4021 in the illustrated interface 402 as an example, the control center 4021 includes a mobile phone, a PAD, a PC, and a large screen.

[0132] In some embodiments, electronic devices that log in to the same user account and can achieve short-range communication can be added to the same trust ring. Correspondingly, multiple electronic devices in the control center include electronic devices that log in to the same user account and can achieve short-range communication, but do not include electronic devices for long-range communication. In this way, service flow between electronic devices in the near field can be achieved in the control center.

[0133] In other embodiments, electronic devices that log in to the same user account and can achieve close range communication and / or long-distance communication can all join the same trust ring. Correspondingly, multiple electronic devices in the control center include electronic devices that log in to the same user account and can achieve close range communication and / or long-distance communication. In this way, in the control center, service flow between near-field electronic devices and / or long-distance electronic devices can be achieved.

[0134] by Figure 5 Take the control center 5011 in the interface 501 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, but also the remote PC2, which is located on the dotted circle in the figure. For example, 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, and can also control the service flow between the mobile phone, PAD, PC1, large screen and PC2.

[0135] In the following, except for the embodiments involving services of remote devices (as described below), Figure 6 and Fig. 20 Except for the corresponding embodiments, the present application scheme is mainly explained by taking the near-field device as an example.

[0136] In the control center, the user can be the center, and multiple electronic devices (including the local device and other devices) are located in a ring around the center. The user can refer to the user corresponding to the same user account logged in to multiple electronic devices, or to other users operating electronic devices. For example, Figure 4 In the control center 4021 of the interface 402 shown, the mobile phone, PAD, PC and large screen are all displayed on a ring centered on the user "S". For another example, Figure 5 In the control center 5011 in the interface 501 shown, the mobile phone, PAD, PC1, large screen, and PC2 are all displayed on a ring centered on the user "S". In other words, the device center in the control center is removed, that is, the local device, such as the mobile phone, is no longer the center, but the user is the center.

[0137] It should be noted that in the control center, although the device is not the center, it will still be displayed differently from other devices, such as color and effect. 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 in the interface 402 shown, the circle of the mobile phone is filled with black, and the circles of the PAD, PC, and large screen are filled with white.

[0138] Each electronic device in the control center can provide its advantageous services for other electronic devices in the control center to call. For example, the electronic devices in the control center and the advantageous services they provide are shown in Table 1 below:

[0139] Table 1

[0140]

[0141] In the following, in order to simplify the drawings, the control center in the mobile phone interface will be mainly drawn in the drawings, and the mobile phone interface including the control center will no longer be drawn; and each electronic device in the control center will be represented by text instead of the corresponding icons. For example, a mobile phone will be represented by the text "mobile phone" instead of a mobile phone icon.

[0142] In some embodiments, in response to a trigger operation on a user icon in the control center, such as a click operation, the mobile phone can expand the advantage services provided by each device. After expansion, each advantage service is displayed around the electronic device that provides the service.

[0143] Herein, the services of each electronic device are represented by a bold circle, and the services of each electronic device are illustrated as surrounding the electronic device. In practice, the services are not limited to this form and position.

[0144] Exemplarily, in response to a user's Figure 6By clicking the user icon "S" in the control center 601 before expansion, the mobile phone can display Figure 6 The expanded control center 602 is shown. In the control center 602, the advantageous services "screen sharing", "network sharing", "file sharing" and "cross-end calling" provided by the mobile phone are displayed in a bold circle around the mobile phone; the advantageous services "screen sharing", "keyboard and mouse sharing", "file sharing" and "cross-end calling" provided by the PAD are displayed in a bold circle around the PAD; the advantageous services "screen sharing", "keyboard and mouse sharing", "file sharing" and "cross-end calling" provided by PC1 are displayed in a bold circle around PC1; the advantageous service "remote access" provided by PC2 is displayed in a bold circle around PC2; the advantageous service "printing" provided by the printer is displayed in a bold circle around the printer; the advantageous service "audio" provided by the headset is displayed in a bold circle around the headset.

[0145] Of course, after the expansion, in response to a trigger operation of the user in the control center, such as a click operation, the mobile phone can be restored to the state before the expansion, such as displaying Figure 6 A control center 601 is shown.

[0146] In this way, users in the control center can trigger the mobile phone to quickly expand or collapse the advantageous services of various electronic devices, so as to have a global understanding of the advantageous services of all electronic devices in the trust ring.

[0147] In other embodiments, in response to a trigger operation, such as a click operation, on any electronic device in the control center, the mobile phone can display the advantageous services provided by the electronic device in the control center. Figure 7 The mobile phone can display the following information by clicking the mobile phone in the control center 701 before expansion: Figure 7 The expanded control center 702 is shown. In the control center 702, the advantageous services "screen sharing", "network sharing", "file sharing" and "cross-end calling" provided by the mobile phone are displayed in the form of bold circles around the mobile phone.

[0148] Of course, the above two embodiments of triggering and displaying advantage services can also be used in combination. That is, in other embodiments, in response to a triggering operation on a user icon in the control center, or in response to a triggering operation on any electronic device in the control center, the mobile phone can display advantage services.

[0149] The following mainly describes the present application scheme by taking the example of displaying advantageous services in response to a triggering operation on any electronic device in the control center.

[0150] After displaying the advantage services, users can realize the service flow between devices by operating the advantage service A. Below, taking advantage service A as "screen sharing", the source device of advantage service A as a mobile phone, and the target device as a PAD as an example, the specific operation process of service flow is explained.

[0151] In a specific implementation, the user can drag the "screen sharing" from the mobile phone to the PAD to realize the service flow of the "screen sharing" from the mobile phone to the PAD.

[0152] See also Figure 8 In method 1, in response to the operation of dragging the "Screen Sharing" provided by the mobile phone in the control center 801 to the PAD (as shown in the direction of the dotted arrow), the mobile phone can update the display position of the "Screen Sharing", such as from displaying around the mobile phone in the control center 801 to displaying around the PAD in the control center 802.

[0153] In another specific implementation, the user can click "Screen Sharing" and then drag "Screen Sharing" from the mobile phone to the PAD to realize the service flow of "Screen Sharing" from the mobile phone to the PAD.

[0154] See also Figure 8 In method 2, in response to a click operation on “screen sharing” provided by the mobile phone in the control center 803, the mobile phone can display the control center 804. In the control center 804, other advantageous services provided by the mobile phone are put away, such as “network sharing”, “file sharing” and “cross-end calling”, and only “screen sharing” is displayed. Furthermore, the mobile phone can also prompt the user to drag “screen sharing” to the target device, such as the prompt “Drag the service to the target device to complete the flow” 805. In this way, for users who are not familiar with the flow of services, the mobile phone can guide the user operation very well. Subsequently, in response to the user's operation of dragging “screen sharing” in the control center 804 to the PAD (as shown in the direction of the dotted arrow), the mobile phone can update the display position of “screen sharing”, such as updating from displaying around the mobile phone in the control center 804 to displaying around the PAD in the control center 806.

[0155] Furthermore, after displaying the "screen sharing" provided by the mobile phone around the PAD, in order to make it clear that the source device of the "screen sharing" is the mobile phone, the mobile phone can also display the logo of the mobile phone around the "screen sharing" after the location is updated. Figure 8 In the control center 802 and the control center 806, after updating the position of the "screen sharing" to around the PAD, the mobile phone can also display the "mobile phone" around the "screen sharing".

[0156] Through the above method 1 or method 2, you can realize the "screen sharing" of the mobile phone to the PAD. Figure 8 After the transfer is successful, the dotted ellipse portion of the control center 802 and the control center 806 in FIG. 1 can represent that the mobile phone shares the screen with the PAD. Hereinafter, the transfer of the advantageous service of the source device to the target service is mainly described by taking mode 1 as an example.

[0157] However, there are the following differences for cross-end calls: cross-end calls usually include multiple sub-services, including but not limited to: cross-end scanning, cross-end shooting, cross-end screenshots and cross-end screen recording. That is, the target device can call the source device to scan, shoot, screenshot, and record the screen. After completing these operations, the source device can return the operation results to the target device, such as returning the scanned, shot, screenshot pictures, or recorded videos.

[0158] For cross-end calls, users can transfer a sub-service (referred to as sub-service B) of cross-end calls from the source device to the target device through the following implementation method. Below, taking the sub-services of cross-end calls including cross-end screenshot and cross-end shooting, sub-service B is "cross-end shooting", the source device of sub-service B is a mobile phone, and the target device is a PAD as an example, the specific operation process of service transfer is explained.

[0159] In a specific implementation, the displayed advantageous services include "cross-end screenshot" and "cross-end shooting", but do not include "cross-end call". Later, the user can drag "cross-end shooting" from the mobile phone to the PAD to realize the service flow of "cross-end shooting" from the mobile phone to the PAD.

[0160] See also Fig. 9 In method a, the advantageous services of the mobile phone shown in the control center 901 include "cross-end screenshot" and "cross-end shooting", but not "cross-end call". Subsequently, in response to the operation of dragging "cross-end shooting" in the control center 901 to the PAD (as shown in the direction of the dotted arrow), the mobile phone can update the display position of "cross-end shooting", such as updating from displaying around the mobile phone in the control center 901 to displaying around the PAD in the control center 902.

[0161] In another specific implementation, in the displayed advantage services, "cross-end call", "cross-end screenshot" and "cross-end shooting" are displayed at the same time. Subsequently, the user can drag "cross-end shooting" from the mobile phone to the PAD to realize the service flow of "cross-end shooting" from the mobile phone to the PAD.

[0162] See also Fig. 9In method b, the advantageous services of the mobile phone shown in the control center 903 include "cross-end call", "cross-end screenshot" (shown as "screenshot") and "cross-end shooting" (shown as "shooting" in the figure). Subsequently, in response to the operation of dragging "cross-end shooting" in the control center 903 to the PAD (as shown in the direction of the dotted arrow), the mobile phone can update the display position of "cross-end shooting", such as updating from displaying around the mobile phone in the control center 903 to displaying around the PAD in the control center 904.

[0163] Of course, similar to the above method 2, after the sub-services called across terminals are displayed, the user can also first click "Cross-terminal shooting" in the control center 903, and then drag "Cross-terminal shooting" from the mobile phone to the PAD to realize the service flow of "Cross-terminal shooting" from the mobile phone to the PAD. No further details will be given here.

[0164] In another specific implementation, the displayed advantage services include "cross-end call", but do not include "cross-end screenshot" and "cross-end shooting". The user can drag "cross-end call" from the mobile phone to the PAD. Then, the PAD can provide the options of "cross-end screenshot" and "cross-end shooting" for the user to choose. After the user selects the "cross-end shooting" option, the service flow of "cross-end shooting" from the mobile phone to the PAD can be realized.

[0165] See also Fig.10 In the method c shown, the advantageous services of the mobile phone shown in the control center 1001 include "cross-end call", but do not include "cross-end screenshot" and "cross-end shooting". In response to the operation of dragging the "cross-end call" in the control center 1001 to the PAD (as shown in the direction of the dotted arrow), the mobile phone can update the display position of the "cross-end call", such as updating from displaying around the mobile phone in the control center 1001 to displaying around the PAD in the control center 1002. Subsequently or simultaneously, the PAD can display the interface 1003, which includes "screenshot" 10031 (an option for "cross-end screenshot") and "shooting" 10032 (an option for "cross-end shooting"). Subsequently, in response to the selection operation of "shooting" 10032, the mobile phone can display the control center 1004. Different from the control center 1002, the "cross-end call" displayed around the PAD in the control center 1004 is updated to "cross-end shooting".

[0166] Alternatively, in response to the selection operation of "shoot" 10032, the mobile phone will not display the control center 1004, but will continue to display the control center 1002, and in the PAD, the "cross-end call" can be used as a global service (such as displayed in the PAD in the form of a floating ball). Specifically, users can use "cross-end call" in the process of using various applications in the PAD, thereby taking advantage of the mobile phone's shooting, scanning, screenshot and other advantageous services. Until the user closes the call to the "cross-end call" on the PAD, such as closing the floating ball, the PAD will send a message to the mobile phone to end the call. In response to the message to end the call, the mobile phone will cancel the "cross-end call" around the PAD in the display control center 1002, indicating that the flow of "cross-end call" has been disconnected.

[0167] Through the above method a, method b or method c, you can realize the transfer of the "cross-end shooting" of the mobile phone to the PAD. Fig. 9 Control center 902, control center 904 and Fig.10 In the control center 1004, after the transfer is successful, the dotted ellipse part can indicate: PAD calls the mobile phone to take pictures. Of course, as explained above, it may not be displayed in practice. Fig.10 The control center 1004 shown in the figure, correspondingly, can only express through the control center 1002: the PAD calls the "cross-end call" of the mobile phone. In the following, mainly taking mode b as an example, the flow of the sub-service of the cross-end call of the source device to the target device is explained. Figure 8-Figure 10 In the example, the advantage service of the mobile phone is mainly transferred to other devices (such as PAD) (recorded as transfer form 1), which illustrates the operation process of service transfer. In practice, in the control center, it is also possible to realize the flow of the advantage service of other devices (such as advantage service C) to the mobile phone (recorded as transfer form 2), or to realize the flow of the advantage service of one device in other devices (such as advantage service D) to another device (recorded as transfer form 3).

[0168] The following uses the operation flow shown in the above method 1 as an example to illustrate:

[0169] For example, the source device is a PAD, the target device is a mobile phone, and the advantage service C is "keyboard and mouse sharing". Fig.11In the second form of transfer, in response to the user's click operation on the PAD in the control center 1101, the mobile phone can display the control center 1102. In the control center 1102, the PAD's advantageous services "screen sharing", "keyboard and mouse sharing", "file sharing", and "cross-end calling" are expanded. In response to the operation of dragging the "keyboard and mouse sharing" in the control center 1102 from the PAD to the mobile phone (as shown in the direction of the dotted arrow), the mobile phone can update the display position of the "keyboard and mouse sharing", such as updating from displaying around the PAD in the control center 1101 to displaying around the mobile phone in the control center 1103. Thereby realizing the flow of "keyboard and mouse sharing" from the PAD to the mobile phone.

[0170] For example, the source device is PAD, the target device is PC, and the advantage service D is "keyboard and mouse sharing". Fig.11 In the third form of transfer, in response to the user's click operation on the PAD in the control center 1104, the mobile phone can display the control center 1105. In the control center 1105, the PAD's advantageous services "screen sharing", "keyboard and mouse sharing", "file sharing", and "cross-end calling" are expanded. In response to the operation of dragging the "keyboard and mouse sharing" in the control center 1105 from the PAD to the PC (as shown in the direction of the dotted arrow), the mobile phone can update the display position of the "keyboard and mouse sharing", such as updating from displaying around the PAD in the control center 1105 to displaying around the PC in the control center 1106. Thereby, the transfer of "keyboard and mouse sharing" from the PAD to the PC is realized.

[0171] It should be emphasized here that: by adopting the third transfer form, you can open the control center on the mobile phone to control the service transfer between other devices, so that the flexibility of service transfer can be greatly improved. For example, an adult uses a PAD in the bedroom, and a child uses a mobile phone to watch cartoons in the living room, and there is a large screen in the living room. Then, by adopting the third transfer form: you can control the "screen sharing" of the mobile phone to flow to the large screen in the control center of the PAD, that is, play the animation on the mobile phone on the large screen.

[0172] The present application embodiment here exemplarily introduces the underlying logic of implementing business flow in the above-mentioned flow form 1, flow form 2 and flow form 3:

[0173] The first form of transfer is to transfer the advantage service A provided by the mobile phone to the PAD as an example: in response to the user's operation of dragging the advantage service A of the mobile phone to the PAD, the mobile phone can establish the flow of advantage service A with the PAD based on advantage service A and the PAD, thereby realizing the flow of advantage service A to the PAD.

[0174] The second form of transfer is to transfer the advantage service C provided by the PAD to the mobile phone as an example: in response to the user dragging the advantage service C of the PAD to the mobile phone, the mobile phone can notify the PAD to establish the transfer of the advantage service C with the mobile phone, such as sending the information of the mobile phone and the information of the advantage service C to the PAD. Among them, the information of the mobile phone indicates the target device, and the information of the advantage service C indicates the transferred service. In response to the information of the mobile phone and the information of the advantage service C, the PAD can communicate with the mobile phone to establish the transfer of the advantage service C, and realize the transfer of the advantage service C from the PAD to the mobile phone.

[0175] Flow form three, taking the flow of advantage service D provided by PAD to PC as an example: in response to the user's operation of dragging advantage service D of PAD to PC, the mobile phone can notify PC to establish the flow of advantage service D with PAD, such as sending PC information and advantage service D information to PAD. Among them, the PC information indicates the target device, and the advantage service D information indicates the flow service. In response to the PC information and the advantage service D information, PAD can communicate with PC, establish the flow of advantage service D, and realize the flow of advantage service D from PAD to PC.

[0176] After the service transfer is completed, the mobile phone can display a prompt of successful transfer on the interface of the control center. At the same time, the source device and the target device can also display a prompt of successful transfer on the current interface. The prompt of successful transfer is used to prompt the source device's target service (such as the above-mentioned advantage service A, sub-service B, advantage service C, advantage service D) to successfully transfer to the target device. In practice, the prompt of successful transfer may include text and / or icons, which is not specifically limited in this article. The following mainly uses text as an example.

[0177] Take the example of a mobile phone as the source device, a PAD as the target device, and "screen sharing" as the target service. After transferring the mobile phone's "screen sharing" to the PAD:

[0178] On the one hand, the phone can display Fig.12 The interface 1201 shown includes a control center 12011. The dotted box in the control center 12011 indicates that the screen sharing of the mobile phone has been transferred to the PAD. At the same time, the interface 1201 also includes a prompt 12012, which includes a prompt text "The screen sharing of the mobile phone has been successfully transferred to the PAD".

[0179] On the other hand, PAD can show Fig.12The interface 1202 shown is the desktop of the PAD. The interface 1202 also includes the interface of a mobile phone (represented as "mobile phone interface" in the figure). The interface of the mobile phone displayed on the PAD is the same as the actual interface displayed on the mobile phone, or the interface of the mobile phone displayed on the PAD has a navigation case below in addition to the actual interface displayed on the mobile phone, which means that the mobile phone is sharing the screen; and, the interface 1202 also includes a prompt 12021, and the prompt 12021 includes the prompt text "The mobile phone is sharing the screen".

[0180] In the previous article, the control center is presented from the perspective of the mobile phone. For example, Figure 6-Figure 11 In the figure, the circle where the mobile phone is located is filled with black, indicating that the local device is a mobile phone. It is understandable that when the control center is presented from the perspective of other devices in the trust ring, the presented control center will change. For example, the local device will switch.

[0181] For example, Fig.13 In the perspective of the mobile phone (indicated as "mobile phone side"), the perspective of the PAD (indicated as "PAD side"), and the perspective of the PC (indicated as "PC side"), "screen sharing" is displayed around the PAD, and "mobile phone" is also displayed around "screen sharing", indicating that the "screen sharing" of the mobile phone flows to the PAD. However, from the perspective of the mobile phone, the mobile phone is located at the top of the control center, and the circle where the mobile phone is located is filled with black, indicating that this machine is a mobile phone; from the perspective of the PAD, the PAD is located at the top of the control center, and the circle where the PAD is located is filled with black, indicating that this machine is a PAD; from the perspective of the PC, the PC is located at the top of the control center, and the circle where the PC is located is filled with black, indicating that this machine is a PC.

[0182] The advantage services listed in Table 1 above can be divided into the following two categories: the first category can only flow to one target device at a time; the second category can flow to multiple (two or more) target devices at the same time. The following will explain these two categories of advantage services respectively.

[0183] The first category can only flow to one target device at a time, which is recorded as service E. Service E includes but is not limited to: screen sharing, file sharing, cross-end calling, remote calling, printing and audio.

[0184] That is, service E cannot be transferred to multiple target devices at the same time. That is to say, after transferring service E of the source device to one target device, the service E of the source device can be transferred to another target device only after the transfer of service E of the source device to the target device is terminated, so that service E can only be transferred to one target device at the same time.

[0185] Next, taking the source device of service E as a mobile phone and switching the flow of service E from PAD to PC as an example, the implementation of switching the flow of service E between multiple target devices is explained:

[0186] In a specific implementation, see Fig.14 In the illustrated method 11, the mobile phone can display a control center 1401. In the control center 1401, service E is displayed around the PAD, and a mobile phone is also displayed around service E, indicating that service E provided by the mobile phone is transferred to the PAD. In response to the user dragging service E in the control center 1401 to the PC, the mobile phone can display a control center 1402. Different from the control center 1401, in the control center 1402, service E is displayed around the PC, not around the PAD, indicating that service E provided by the mobile phone is switched from being transferred to the PAD to being transferred to the PC. In this way, the switching of the transfer can be realized quickly.

[0187] In another specific implementation, see Fig.14 In the method 12 shown, the mobile phone can display the control center 1403, which is the same as the control center 1401 in the method 11 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 the control center 1403, the mobile phone can display the control center 1404. Different from the control center 1403: the advantage services provided by the mobile phone in the control center 1404 are expanded. In response to the user's operation of dragging service E among the advantage services expanded in the control center 1404 to the PC, the mobile phone can display the control center 1405. Different from the control center 1404: the advantage services of the mobile phone in the control center 1405 are folded, service E is not displayed around the PAD, but service E is displayed around the PC, and a mobile phone is also displayed around service E, indicating that service E provided by the mobile phone is switched from flowing to the PAD to flowing to the PC.

[0188] In the above-mentioned methods 11 and 12, in response to the operation of switching the flow of service E from PAD to PC, such as the operation of dragging service E in control center 1401 to PC or the operation of dragging service E in advantage services expanded 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 a mobile phone, then in response to the operation of switching the flow of service E from PAD to PC, the mobile phone can notify the source device to disconnect the flow of service E from PAD, and 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 with 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.

[0189] In the following, the above-mentioned method 11 is mainly used as an example to illustrate the flow of service E.

[0190] The following takes service E as screen sharing, file sharing, cross-end calling, remote calling, printing and audio as examples to illustrate the operation process and interface response of service E flow.

[0191] First, screen sharing.

[0192] Example 1: Transfer the "screen sharing" provided by the mobile phone to the car computer.

[0193] See also Fig.15 , the mobile phone can display the control center 1501, and the advantageous services of the mobile phone are displayed around the mobile phone in the control center 1501: "Screen sharing", "Network sharing", "File sharing", and "Cross-end calling". At this time, the car computer displays its own user interface 15011. In response to the user dragging the "Screen sharing" in the control center 1501 to the car computer (represented as "car" in the figure), the mobile phone can display the control center 1502, and the "Screen sharing" in the control center 1502 is displayed around the car computer. That is, the "Screen sharing" of the mobile phone is transferred to the car computer. At this time, the content in the mobile phone will be displayed on the car computer. The content in the mobile phone displayed on the vehicle computer can be in any of the following two forms: Form 1, the user interface of the mobile phone is displayed on the vehicle computer, such as the vehicle computer interface 15021 including the mobile phone interface 15022; Form 2, the applications in the mobile phone are displayed on the vehicle computer, such as the vehicle computer interface 15023 including the area 15024, and the area 15024 displays APP1-APP10 in the mobile phone, and also displays the commonly used APPs in these APPs, such as APP1 and APP5. It can be seen that the screen of the mobile phone is shared with the vehicle computer.

[0194] In the above example 1, the screen of the mobile phone can be shared with the vehicle computer through the control on the mobile phone, that is, the above transfer form 1 is adopted.

[0195] Example 2: Use the PAD to transfer the "screen sharing" provided by the mobile phone to the large screen. In this example, the control device is the PAD.

[0196] See also Fig.16, the PAD can display a control center 1601, in which the advantageous services of the mobile phone are displayed around the mobile phone: "Screen sharing", "Network sharing", "File sharing", and "Cross-end 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 mobile phone can display a control center 1602, in which "Screen sharing" is displayed around the large screen. That is, the "Screen sharing" of the mobile phone is transferred to the large screen. At this time, the user interface 16021 displayed on the large screen includes the user interface 16022 of the mobile phone. It can be seen that the screen of the mobile phone is shared with the large screen.

[0197] In the above example 2, the screen of the mobile phone can be shared with the large screen by controlling on the PAD, which is the above transfer form 3.

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

[0199] See also Fig.17 , the mobile phone can display the control center 1701, which is the same as the control center 1501 mentioned above and will not be repeated here. At this time, both the PAD and the PC display their respective user interfaces, such as the PAD displays the user interface 17011 and the PC displays the user interface 17012. In response to the user dragging the "Screen Sharing" in the control center 1701 to the PAD, the mobile phone can display the control center 1702, and the "Screen Sharing" in the control center 1702 is displayed around the PAD. That is, the "Screen Sharing" of the mobile phone has been transferred to the PAD. At this time, the PC still displays its own user interface 17023, and the user interface 17021 displayed by the PAD includes the user interface 17022 of the mobile phone. It can be seen that the screen of the mobile phone is shared with the PAD.

[0200] Continue to see Fig.17 In response to the user dragging the "Screen Sharing" around the PAD in the control center 1702 to the PC, the mobile phone can display the control center 1703. The "Screen Sharing" in the control center 1703 is displayed around the PC. That is, the "Screen Sharing" of the mobile phone is transferred to the PC. At this time, the PAD displays its own user interface 17031, but the user interface 17032 displayed by the PC includes the user interface 17033 of the mobile phone. It can be seen that the screen of the mobile phone is shared with the PC.

[0201] In the above example 3, the screen of the mobile phone can be shared with the PAD first and then switched to the PC through the control on the mobile phone, so that the advantageous services of the local device can be transferred and switched to other devices.

[0202] Second, file sharing.

[0203] Take the example of transferring the "file sharing" provided by the mobile phone to the PAD, see Fig.18 , the mobile phone can display control center 1801, which is the same as the control center 1501 mentioned above and will not be repeated here. At this time, the PAD displays interface 18011, such as interface 18011 is the desktop. In response to the user dragging "File Sharing" in control center 1801 to the PAD, the mobile phone can display control center 1802, and "File Sharing" in control center 1802 is displayed around the PAD. That is, the "File Sharing" of the mobile phone has been transferred to the PAD. At this time, interface 18021 will be displayed on the PAD, and interface 18021 is the interface of the file management APP in the PAD; and, interface 18021 includes files in the mobile phone, such as file 1, file 2, file 3, and file 4. It can be seen that the files of the mobile phone are shared with the PAD.

[0204] In the above file sharing example, after the "file sharing" provided by the mobile phone is transferred to the PAD in the control center, the PAD can display the interface of the file management APP and display the files in the mobile phone in the interface, making it easier to operate the files in the mobile phone in the PAD.

[0205] Third, cross-end calls.

[0206] Take the example of transferring the "cross-end shooting" flow in the "cross-end call" provided by the mobile phone to the PAD, see Fig.19 , the mobile phone can display the control center 1901, and the advantageous services of the mobile phone are displayed around the mobile phone in the control center 1901: "Screen sharing", "Network sharing", "File sharing", and "Cross-end calling". Among them, the "Cross-end calling" is further surrounded by two sub-service items: "shooting" (corresponding to the "cross-end shooting" sub-service) and "screenshot" (corresponding to the "cross-end screenshot" sub-service). At this time, the mobile phone displays interface 19011, such as the desktop; the PAD displays interface 19012, such as the document editing interface. In response to the user dragging the "shooting" in the control center 1901 to the PAD, the mobile phone can display the control center 1902, and the "cross-end shooting" in the control center 1902 is displayed around the PAD. That is, the "cross-end shooting" of the mobile phone is transferred to the PAD. At this time, the PAD will display interface 19021, such as still the document editing interface; however, the mobile phone will display the shooting interface 19022. Subsequently, in response to the user's shooting operation in interface 19022, the mobile phone may shoot an image and send the shot image to the PAD, and the PAD may display interface 19031, which includes image 19032 shot by the mobile phone.

[0207] In the above cross-end call example, after the "cross-end shooting" flow 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 finally display the image taken by the mobile phone.

[0208] The above cross-end call is particularly suitable for the use of PAD and PC, such as when inserting images during document editing. In this scenario, the "cross-end call" of the mobile phone can be transferred to the PAD or PC in the control center of the mobile phone, so that the mobile phone can be easily triggered to perform operations such as screenshots and shooting and return the results to the PAD or PC. In this way, the shooting, screenshot and other functions of the mobile phone can be called to obtain images without interrupting the current task in the PAD or PC, such as the task of document editing.

[0209] Fourth, remote access.

[0210] Take the example of transferring the "remote access" provided by the PC to the mobile phone, see Fig. 20 , the mobile phone can display the control center 2001, and the advantageous service "remote access" of PC2 is displayed around PC2 in the control center 2001. At this time, the mobile phone displays interface 20011, such as a desktop. In response to the user dragging "remote access" in the control center 2001 to the mobile phone, the mobile phone can display the control center 2002, and the "remote access" in the control center 2002 is displayed around the mobile phone. That is, the "remote access" of PC2 is transferred to the mobile phone. At this time, the mobile phone will display interface 20021, and interface 20021 includes interface 20022 of PC2. It can be seen that the mobile phone is accessing PC2.

[0211] In the above remote access example, 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.

[0212] Fifth, print.

[0213] Take the example of transferring the "print" flow provided by the printer to the mobile phone, see Fig.21 , the mobile phone can display the control center 2101, and the printer's advantageous service "Print" is displayed around the printer in the control center 2101. At this time, the mobile phone displays interface 21011, such as a document interface. In response to the user dragging "Print" in the control center 2101 to the mobile phone, the mobile phone can display the control center 2102, and "Print" in the control center 2102 is displayed around the mobile phone. That is, the printer's "Print" flows to the mobile phone. At this time, the mobile phone will display interface 21021, and the interface 21021 includes a suspended print control 21022. It can be seen that the printer's "Print" can be used by the mobile phone.

[0214] In the above printing example, after the "print" flow provided by the printer is transferred to the mobile phone in the control center, the mobile phone can print the document through the print control displayed in the floating state.

[0215] Sixth, audio.

[0216] For example, the audio provided by the headset is first transferred to the mobile phone and then switched to the PAD. Fig. 22 , the mobile phone can display the control center 2201, and the advantageous service "audio" is displayed around the earphone in the control center 2201. At this time, the "audio" of the earphone is not transferred to any device, that is, no device uses the earphone, so the earphone does not make any sound. In response to the user dragging the "audio" in the control center 2201 to the mobile phone, the mobile phone can display the control center 2202, and the "audio" in the control center 2202 is displayed around the mobile phone. That is, the "audio" of the earphone is transferred to the mobile phone. At this time, the earphone can play the sound corresponding to the audio data transmitted from the mobile phone. It can be seen that the earphone is playing the audio of the mobile phone.

[0217] Continue to see Fig. 22 In response to the user dragging the "audio" around the mobile phone in the control center 2202 to the PAD, the mobile phone can display the control center 2203. The "audio" in the control center 2203 is displayed around the PAD. That is, the "audio" of the headset is transferred to the PAD. At this time, the headset can play the sound corresponding to the audio data transmitted from the PAD. It can be seen that the headset is playing the audio of the PAD.

[0218] In the above audio example, you can use the controls on the mobile phone to first play the audio of the mobile phone through the headset, and then switch to playing the audio of the PAD.

[0219] In addition, considering that the headset usually only provides audio services, in some embodiments, the headset in the control center can be displayed in the form of services, such as Fig.23 In the control center 2301 shown, the earphones are displayed in a bold circle. When any electronic device in the control center plays audio through the earphones, the earphones can be displayed around the electronic device. Subsequently, in response to the user dragging the earphones around the electronic device to another electronic device in the control center, the mobile phone can display the earphones around the other electronic device, and the earphones can play the audio of the other electronic device. Thus, the "audio" of the earphones is switched from flowing to one electronic device to flowing to another electronic device.

[0220] For example, when multiple electronic devices in the trust ring do not play audio through headphones, the mobile phone can display Fig.23 The control center 2301 is shown. When a mobile phone in the trust ring is connected to a headset and plays audio through the headset, the mobile phone can display Fig.23 The control center 2302 shown in FIG. In the control center 2302, headphones are displayed around the mobile phone, indicating that the mobile phone plays audio through the headphones. Subsequently, in response to the user dragging the headphones in the control center 2302 to the PAD, the mobile phone can display Fig.23 The control center 2303 shown. In the control center 2303, headphones are displayed around the PAD, indicating that the PAD plays audio through the headphones.

[0221] In this embodiment, in the control center, the user can play audio from different devices through the headphones by dragging the headphones.

[0222] In other embodiments, when multiple electronic devices in the control center are not connected to headphones, the control center displayed by the mobile phone may not include headphones. After any electronic device in the control center is connected to headphones, the mobile phone may display headphones around the any electronic device in the control center, indicating that the any electronic device is connected to headphones. Subsequently, in response to the user dragging the headphones around the any electronic device to another electronic device in the control center, the mobile phone may display the headphones around the other electronic device; indicating that the other electronic device is connected to headphones, and the headphones around any electronic device disappear, indicating that any electronic device is disconnected from the headphones. Thereby, the "audio" of the headphones is switched from flowing to one electronic device to flowing to another electronic device.

[0223] The second category can be transferred to multiple target devices at the same time, which is recorded as service F. Service F includes but is not limited to: network sharing and keyboard and mouse sharing.

[0224] That is, service F can be simultaneously transferred to multiple target devices. That is, after the service F of the source device is transferred to one target device, even if the transfer of the service F of the source device to the target device is not terminated, the service F of the source device can be further transferred to another target device, so that service F is transferred to multiple target devices at the same time.

[0225] Below, we take the source device of service F as a mobile phone, and transfer service F to PAD and then to PC as an example to illustrate the implementation of simultaneous transfer of service F between multiple target devices:

[0226] In a specific implementation, see Fig.24In the illustrated method 21, the mobile phone can display a control center 2401. In the control center 2401, service F is displayed around the PAD, and a 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 in the control center 2401 to the PC, the mobile phone can display a control center 2402. Different from the control center 2401, in the 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 flows to the PC on the basis of flowing to the PAD.

[0227] In another specific implementation, see Fig.24 In the method 22 shown, the mobile phone can display a control center 2403, which is the same as the control center 2401 in the 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 the control center 2403, the mobile phone can display a control center 2404. Different from the control center 2403: the advantageous services provided by the mobile phone in the control center 2404 are expanded. In response to the user's operation of dragging service F among the advantageous services expanded in the control center 2404 to the PC, the mobile phone can display a control center 2405. Different from the control center 2404: the advantageous services of the mobile phone in the control center 2405 are folded, and service F is displayed not only around the PAD, but also around the PC, indicating that service F provided by the mobile phone is further transferred to the PC on the basis of being transferred to the PAD.

[0228] In the above-mentioned methods 21 and 22, when the service F is transferred to the PAD, in response to the operation of further transferring the service F to the PC, such as the operation of dragging the service F in the control center 2401 to the PC or the operation of dragging the service F in the advantage service expanded in the control center 2404 to the PC, the mobile phone can further establish the flow of the service F with the PC. It should be noted that if the source device of the service F is not the mobile phone, then in response to the operation of further transferring the service F to the PC, the mobile phone can notify the source device to establish the flow of the service F with the PC. Subsequently, the source device can establish the flow of the service F with the PC in response to the notification of establishing the flow of the service F with the PC.

[0229] At this point, by comparing the previous methods 11 and 21, as well as methods 12 and 22, it can be seen that: when a service has been transferred to a target device, in response to the user dragging the service to another target device, or in response to the user 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 different services. If it is service E, the mobile phone will switch service E to another target device, so that service E can be 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 can be transferred to multiple target devices at the same time.

[0230] However, see Fig.24 , when the mobile phone displays the control center 2401, the user drags the service F in the control center 2401 to the PC, and may want to further transfer the service F to the PC, or may want to switch the service F from flowing to flowing to. In other words, the user's operation intention is unclear, so adopting method 21 may result in a response that does not meet the user's expectations. Based on this, in actual implementation, when the service F is transferred to a target device, in response to the user's operation of dragging the service F around the target device to another target device, the mobile phone may not respond, or may display options of the operation intention (such as the option of switching and the option of further flowing) and respond based on the user's selection.

[0231] In the following, the above-mentioned method 22 is mainly used as an example to illustrate the flow of service F.

[0232] The following takes service F as network sharing and keyboard and mouse sharing as examples to illustrate the operation process and interface response of service F flow.

[0233] First, network sharing.

[0234] Take the example of transferring the "Internet sharing" provided by the mobile phone to the PAD and then transferring the "Internet sharing" of the mobile phone to the PC:

[0235] See also Fig.25 , the mobile phone can display the control center 2501. In the control center 2501, "Network Sharing" is displayed around the PAD, and a mobile phone is displayed around "Network Sharing", indicating that the "Network Sharing" of the mobile phone has been transferred to the PAD. At this time, the PAD can access the network normally, and the PAD can also prompt "Using the network from the mobile phone" 25011 to make it clear that the source device of the network is the mobile phone. However, the PC does not use the mobile phone's network, and the PC has no other network sources, so the PC cannot access the network, which is indicated by "Unable to access the network" in the figure.

[0236] In response to the user's click operation on the mobile phone in the control center 2501, the mobile phone can display Fig.25 The control center 2502 shown in FIG. 2501 is different from the control center 2502 in that the control center 2502 includes the advantageous services of the mobile phone: "screen sharing", "network sharing", "file sharing" and "cross-end call". At this time, the mobile phone network is still used for the PAD, but the PC cannot access the network.

[0237] In response to the user dragging "Network Sharing" in the control center 2502 to the PC, the mobile phone can display Fig.25 The control center 2503 shown in FIG. In the control center 2503, "Network Sharing" is displayed not only around the PAD, but also around the PC, and a mobile phone is displayed around "Network Sharing", indicating that the "Network Sharing" of the mobile phone is further transferred to the PC on the basis of being transferred to the PAD. At this time, not only the PAD can access the network normally, but the PC can also access the network normally, and the PC can also prompt "Using the network from the mobile phone" 25021 to make it clear that the source device of the network is the mobile phone.

[0238] In the above example 3, the mobile phone network can be shared with the PAD first and then with the PC through the operation on the mobile phone, thereby realizing the transfer of the local "network sharing" to multiple target devices.

[0239] Second, keyboard and mouse sharing.

[0240] Take the example of transferring the "keyboard and mouse sharing" provided by the PC to the mobile phone and then transferring the "keyboard and mouse sharing" of the PC to the PAD. In this example, the control device is the PC:

[0241] See also Fig.26 , the PC can display a control center 2601. In the control center 2601, "Keyboard and Mouse Sharing" is displayed around the mobile phone, and a PC is displayed around "Keyboard and Mouse Sharing", indicating that the "Keyboard and Mouse Sharing" of the PC is transferred to the mobile phone. At this time, after the keyboard and mouse of the PC move to the edge of the PC interface, they can continue to move to the mobile phone interface, such as moving from the position of the cursor 26012 in the PC interface 26011 to the position of the cursor 26014 in the mobile phone interface 26013. In this way, the keyboard and mouse of the PC can be used to operate the mobile phone.

[0242] In response to the user's click operation on the PC in the control center 2601, the PC may display Fig.26 The control center 2602 shown in FIG. 2601 is different from the control center 2602 in that the control center 2602 includes the PC's advantageous services: "screen sharing", "keyboard and mouse sharing", "file sharing" and "cross-end call". At this time, the keyboard and mouse of the PC can still be used to operate the mobile phone.

[0243] In response to the user dragging the "Keyboard and Mouse Sharing" in the control center 2602 to the PAD, the PC may display Fig.26 The control center 2603 shown. In the control center 2603, "Keyboard and Mouse Sharing" is displayed not only around the mobile phone, but also around the PAD, and the PC is also displayed around "Keyboard and Mouse Sharing", indicating that the "Keyboard and Mouse Sharing" of the PC has been further transferred to the PAD on the basis of being transferred to the mobile phone. At this time, after the keyboard and mouse of the PC move to the edge of the PC interface, they can continue to move to the interface of the mobile phone and the PAD, such as moving from the position of the cursor 26032 in the interface 26031 of the PC to the position of the cursor 26034 in the interface 26033 of the mobile phone, or from the position of the cursor 26035 in the interface 26031 of the PC to the position of the cursor 26037 in the interface 26036 of the mobile phone. In this way, the keyboard and mouse of the PC can be used to operate the mobile phone and the PAD.

[0244] In the above-mentioned keyboard and mouse sharing, the keyboard and mouse of the PC can be shared to the mobile phone first and then to the PAD through the operation on the PC, thereby realizing the transfer of the "keyboard and mouse sharing" of the local device to multiple target devices.

[0245] In particular, for two electronic devices both provided with "keyboard and mouse sharing", after the "keyboard and mouse sharing" of one electronic device is transferred to another electronic device, the keyboards and mice of the two electronic devices can be shared with each other.

[0246] For example, both PAD and PC provide "keyboard and mouse sharing", see Fig. 27 , the PC can display Fig. 27 The control center 2701 shown in FIG. The control center 2701 includes the PC's advantageous services: "screen sharing", "keyboard and mouse sharing", "file sharing" and "cross-end calling". At this time, there is no service flow between the PC and the PAD, such as the keyboard and mouse of the PC cannot be used to operate the PAD.

[0247] In response to the user dragging the "Keyboard and Mouse Sharing" in the control center 2701 to the PAD, the PC may display Fig. 27The control center 2702 shown. In the 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 "Keyboard and Mouse Sharing" of the PC has been transferred to the PAD. In addition, in the 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 "Keyboard and Mouse Sharing" of the PAD has been transferred to the PC. At this time, the keyboard and mouse of the PC and the keyboard and mouse of the PAD can be shared with each other, such as the keyboard and mouse of the PC moves from the position of the cursor 27022 in the interface 27021 of the PC to the position of the cursor 27024 in the interface 27023 of the PC, or the keyboard and mouse of the PAD moves from the position of the cursor 27024 in the interface 27023 of the PAD to the position of the cursor 27022 in the interface 27021 of the PC.

[0248] In practice, in the control center, the transfer can be completed for multiple services E. Alternatively, the transfer can be completed for multiple services F. Alternatively, the transfer can be completed for at least one service E and at least one service F. Thus, the transfer of multiple services to one or more devices is realized. For details, please refer to the above description of the transfer of service E and service F, which will not be repeated here.

[0249] In particular, in the case where multiple services of one device are transferred to another device, the transfer can be completed in the following manner.

[0250] Take the example of transferring the "keyboard and mouse sharing" and "screen sharing" of the PC to the PAD. In this example, the control device is the PC:

[0251] In a specific implementation, see Fig.28 , the PC can display the control center 2801, which includes the advantageous services provided by the PC: "screen sharing", "keyboard and mouse sharing", "file sharing" and "cross-end call". At this time, there is no service flow between the PC and the PAD. For example, the keyboard and mouse of the PC cannot be used to operate the PAD, and the PC screen will not be shared with the PAD. In response to the user dragging the "keyboard and mouse sharing" in the control center 2801 to the PAD, the PC can display Fig.28 The control center 2802 shown. In the control center 2802, "Keyboard and Mouse Sharing" is displayed around the PAD, and a PC is also displayed around "Keyboard and Mouse Sharing", indicating that the "Keyboard and Mouse Sharing" of the PC has been transferred to the PAD. At this time, after the keyboard and mouse of the PC move to the edge of the PC interface, they can continue to move to the mobile phone interface, such as moving from the position of the cursor 28022 in the PC interface 28021 to the position of the cursor 28024 in the PAD interface 28023. In this way, the keyboard and mouse of the PC can be used to operate the PAD.

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

[0253] That is, multiple services of a source device may be successively dragged to the same target device in the control center of the control device, thereby enabling the transfer of multiple services of one device to another device.

[0254] In another specific implementation, see Fig.29 , the PC can display a control center 2901, which includes the advantageous services provided by the PC: "screen sharing", "keyboard and mouse sharing", "file sharing" and "cross-end calling". At this time, there is no service flow between the PC and the PAD, such as the keyboard and mouse of the PC cannot be used to operate the PAD, and the screen of the PC will not be shared with the PAD. In response to the user's continuous click operations on "keyboard and mouse sharing" and "screen sharing" in the control center 2901, the PC can display a control center 2902. In the control center 2902, the PC's advantageous services "keyboard and mouse sharing" and "screen sharing" are still displayed around the PC, but are glued together. At this time, there is still no service flow between the PC and the PAD. In response to the user's operation of dragging the whole 29021 in which "keyboard and mouse sharing" and "screen sharing" are glued together in the control center 2902 to the PAD, the PC can display a control center 2903. In the control center 2903, "Keyboard and Mouse Sharing" and "Screen Sharing" are displayed around the PAD, and a PC is also displayed around "Keyboard and Mouse Sharing" and "Screen Sharing", indicating that the PC's "Keyboard and Mouse Sharing" and "Screen Sharing" are transferred to the PAD. At this time, after the PC's keyboard and mouse move to the edge of the PC's interface, they can continue to move to the mobile phone's interface, such as moving from the position of cursor 29032 in the PC's interface 29031 to the position of cursor 29034 in the PAD's interface 29033. In this way, the PC's keyboard and mouse can be used to operate the PAD. In addition, the PAD's interface 29033 also includes the PC's interface 29035.

[0255] That is to say, multiple services of a source device can be continuously selected in the control center of the control device, and then the whole formed by gluing multiple services to the target device can be dragged, thereby realizing the rapid flow of multiple services from one device to another device.

[0256] After the service of the source device is transferred to the target device through the above embodiment, in response to the user dragging the service away from the target device, the flow of the service from the source device to the target device can be ended. For example, after the "screen sharing" of the mobile phone is transferred to the PAD, the mobile phone can display Fig.30 The control center 3001 shown in FIG. In the control center 3001, "Screen Sharing" is displayed around the PAD, and "Mobile Phone" is also displayed around "Screen Sharing", indicating that the "Screen Sharing" of the mobile phone is transferred to the PAD. In response to the user dragging the "Screen Sharing" around the PAD in the control center 3001 along the dotted arrow in the direction away from the PAD, the mobile phone can display Fig.30 The control center 3002 shown. In the control center 3002, "screen sharing" is no longer displayed around the PAD, indicating that the transfer of the mobile phone's "screen sharing" to the PAD has ended.

[0257] The present application also provides an electronic device, which may include: a display screen, a memory, and one or more processors (such as a CPU, a GPU, an NPU, etc.). The display screen, the memory, and the processor are coupled. The memory is used to store computer program code, and the computer program code includes computer instructions. When the processor executes the computer instructions, the electronic device may perform each function or step performed by the device in the above method embodiment.

[0258] The embodiment of the present application also provides a chip system, which includes at least one processor and at least one interface circuit. The processor and the interface circuit can be interconnected by lines. For example, the interface circuit can be used to receive signals from other devices (such as a memory of an electronic device). For another example, the interface circuit can be used to send signals to other devices (such as a 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 various steps in the above embodiments. Of course, the chip system can also include other discrete devices, which are not specifically limited in the embodiment of the present application.

[0259] This embodiment further provides a computer storage medium, in which computer instructions are stored. When the computer instructions are executed on an electronic device, the electronic device executes the above-mentioned related method steps to implement the image processing method in the above-mentioned embodiment.

[0260] This embodiment further provides a computer program product. When the computer program product is run on a computer, the computer is enabled to execute the above-mentioned related steps to implement the image processing method in the above-mentioned embodiment.

[0261] In addition, an embodiment of the present application also provides a device, which can specifically be a chip, component or module, and the device may include a connected processor and memory; wherein the memory is used to store computer-executable instructions, and when the device is running, the processor can execute the computer-executable instructions stored in the memory so that the chip executes the image processing method in the above-mentioned method embodiments.

[0262] Among them, the electronic device, computer storage medium, computer program product or chip provided in this embodiment is used to execute the corresponding method provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding method provided above and will not be repeated here.

[0263] Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned 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.

[0264] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

[0266] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0267] If the integrated unit is implemented in the form of 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 solution of the embodiment of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium, including several instructions to enable a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to perform all or part of the steps of each embodiment method of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program code.

[0268] Finally, it should be noted that the above embodiments are only used to illustrate the technical solution of the present application and are not intended to limit it. Although the present application has been described in detail with reference to the preferred embodiments, a person of ordinary skill in the art should understand that the technical solution of the present application may be modified or replaced by equivalents without departing from the spirit and scope of the technical solution of the present application.

Claims

1. A method for controlling service flow between devices, characterized in that: Applied to a first electronic device, the method includes: Displaying a first interface, wherein the first interface includes a first device identifier and at least two associated device identifiers, wherein the first device identifier indicates the first electronic device, and each associated device identifier indicates an associated device; In response to a first trigger operation based on the first interface, displaying a first service logo around a first source device logo, wherein the first source device logo indicates a first source device, and the first service logo indicates a first service provided by the first source device; In response to an operation of dragging the first service logo around the first source device logo to a first target device logo, the first service logo and the first source device logo are displayed around the first target device logo, the first target device logo indicates a first target device, and the first service provided by the first source device is transferred to the first target device; In response to an operation of dragging the first service logo around the first target device logo to a second target device logo, the first service logo and the first source device logo are displayed around the second target device logo, but the first service logo and the first source device logo around the first target device logo are canceled, the second target device logo indicates a second target device, the first service provided by the first source device flows to the second target device, and the first service provided by the first source device stops flowing to the first target device; 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 the 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.

2. The method according to claim 1, characterized in that The first source device and the first target device are two of the at least two associated devices indicated by the at least two associated device identifiers.

3. The method according to claim 1 or 2, characterized in that: In response to the operation of dragging the first service logo around the first target device logo to the second target device logo, displaying the first service logo and the first source device logo around the second target device logo includes: If the first service belongs to a first category of services, in response to an operation of dragging the first service logo around the first target device logo to the second target device logo, displaying the first service logo and the first source device logo around the second target device logo; The first type of service is a service that can only be transferred to one target device at a time.

4. The method according to any one of claims 1 to 3, characterized in that The method further comprises: In response to the operation of dragging the first service logo around the first source device logo to the first target device logo, canceling the display of the first service logo around the first source device logo; 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 the first trigger operation based on the first interface, displaying the first service logo around the first source device logo; In response to the operation of dragging the first service logo around the first source device logo to the first target device logo, the first service logo and the first source device logo are displayed around the first target device logo, the first service logo and the first source device logo around the second target device logo are canceled, the first service provided by the first source device flows to the first target device, and the first service provided by the first source device stops flowing to the second target device.

5. The method according to claim 4, characterized in that In response to the operation of dragging the first service logo around the first source device logo to the first target device logo, displaying the first service logo and the first source device logo around the first target device logo, and canceling the display of the first service logo and the first source device logo around the second target device logo, comprises: if the first service belongs to a first category of services, in response to an operation of dragging the first service logo around the first source device logo to the first target device logo again, displaying the first service logo and the first source device logo around the first target device logo, and canceling displaying the first service logo and the first source device logo around the second target device logo; The first type of service is a service that can only be transferred to one target device at a time.

6. The method according to claim 5, characterized in that The method further comprises: If the first service belongs to the second category of services, in response to the operation of dragging the first service logo around the first source device logo to the first target device logo again, displaying the first service logo and the first source device logo around the first target device logo, and keeping displaying the first service logo and the first source device logo around the second target device logo; The second type of service is a service that can be transferred to multiple target devices at the same time.

7. The method according to any one of claims 1 to 6, characterized in that The step of displaying a first service logo around a first source device logo 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, displaying at least one target service identifier around the first source device identifier, each of the target service identifiers indicating a service provided by the first source device, and the at least one target service identifier including the first service identifier; In response to the operation of dragging the first service logo around the first source device logo to the first target device logo, before displaying the first service logo and the first source device logo around the first target device logo, the method further includes: In response to a second trigger operation on the first service identifier around the first source device, display of service identifiers other than the first service identifier among the at least one target service identifier is canceled, and a prompt is displayed to drag the first service identifier to a target device identifier to implement service transfer.

8. The method according to any one of claims 1 to 7, characterized in that 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; In response to the operation of dragging the first service logo around the first source device logo to the first target device logo, displaying the first service logo and the first source device logo around the first target device logo includes: In response to an operation of dragging the first sub-service logo around the first source device logo to the first target device logo, the first sub-service logo and the first source device logo are displayed around the first target device logo.

9. The method according to any one of claims 1 to 7, characterized in that: The first service includes a first sub-service and a second sub-service; After the first service logo and the first source device logo are displayed around the first target device logo in response to the operation of dragging the first service logo around the first source device logo to the first target device logo, the method further includes: In response to a first message, a first sub-service identifier and the first source device identifier are displayed around the first target device identifier, the first message indicating that the first target device selects a first sub-service, and the first sub-service identifier indicating the first sub-service.

10. The method according to any one of claims 1 to 9, characterized in that After displaying the first service identifier and the first source device identifier around the second target device identifier, the method further includes: When the second electronic device plays audio through the headset, displaying a second interface, the second interface including the first device identifier, the at least two associated device identifiers and the identifier of the headset, the identifier of the headset being displayed around the identifier of the second electronic device, and 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; In response to the operation of dragging the headset logo to the third target device logo, the headset logo is displayed around the third target device logo, but the headset logo displayed around the second electronic device is cancelled, the third target device logo indicates a third target device, the third target device plays audio through the headset, and the second electronic device does not play audio through the headset; The third target device identifier is a device identifier other than the identifier of the second electronic device among the first device identifier and the at least two associated device identifiers.

11. The method according to any one of claims 1 to 10, characterized in that The first service is a service for sharing a keyboard and / or a mouse, the first source device includes a keyboard and / or a mouse, and the first target device includes a keyboard and / or a mouse; The method further comprises: In response to the operation of dragging the first service logo around the first source device logo to the first target device logo, the first service logo and the first target device logo are displayed around the first source device logo, and the first service provided by the first target device is transferred to the first source device.

12. The method according to any one of claims 1 to 11, characterized in that 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 third trigger operation based on the first interface, displaying a second service logo and a third service logo around a second source device logo, wherein the second service logo indicates a second service, the third service logo indicates a third service, and the second service and the third service are two services provided by the second source device indicated by the second source device logo; In response to a selection operation on 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 a fourth target device identifier, the second service identifier and the third service identifier are displayed around the fourth target device identifier, and the second service identifier and the third service identifier are also surrounded by the second source device identifier, the fourth target device identifier indicates a fourth target device, and the second service and the third service provided by the second source device are transferred to the fourth target device; The second source device identifier and the fourth target device identifier are two device identifiers among the first device identifier and the at least two associated device identifiers, and the second source device identifier and the fourth target device identifier are different.

13. The method according to any one of claims 1 to 12, characterized in that The first trigger operation includes a trigger operation on the first source device identifier in the first interface; or, The first interface also includes a second control, and the first trigger operation includes a trigger operation on the second control in the first interface.

14. The method according to any one of claims 1 to 13, characterized in that In the case where the third electronic device has been connected to a printer, the at least two associated device identifiers include an identifier of the printer; 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.

15. A method for controlling service flow between devices, characterized in that: 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 the 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, displaying a first service logo around a first associated device logo, wherein the first service logo indicates a first service provided by the first associated device; In response to the operation of dragging the first service logo to the second associated device logo, the first service logo and the first associated device logo are displayed around the second associated device logo, and the first service provided by the first associated device flows to the second associated device.

16. The method according to claim 15, characterized in that The method further comprises: In response to the operation of dragging the first service logo to the second associated device logo, canceling the display of the first service logo around the first associated device logo; 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 the first trigger operation based on the first interface, displaying the first service logo around the first associated device logo; In response to the operation of dragging the first service logo to the first target device logo, the first service logo and the first associated device logo are displayed around the first target device logo, the first service logo and the first associated device logo are kept displayed around the second associated device logo, and the first service provided by the first associated device is transferred to the second associated device and the first target device; The first target device identifier is the first device identifier and one of the at least two associated device identifiers except the first associated device identifier and the second associated device identifier, and the first target device identifier indicates the first target device.

17. The method according to claim 16, characterized in that In response to the operation of dragging the first service logo to the first target device logo, displaying the first service logo and the first associated device logo around the first target device logo, and keeping displaying the first service logo and the first associated device logo around the second associated device logo, comprises: If the first service belongs to the second category of services, in response to the operation of dragging the first service logo to the first target device logo, displaying the first service logo and the first associated device logo around the first target device logo, and keeping displaying the first service logo and the first associated device logo around the second associated device logo; The second type of service is a service that can be transferred to multiple devices at the same time.

18. The method according to claim 17, characterized in that The method further comprises: If the first service belongs to the first category of services, in response to the operation of dragging the first service logo to the first target device logo, the first service logo and the first associated device logo are displayed around the first target device logo, the first service logo and the first associated device logo are not displayed around the second associated device logo, the first service provided by the first associated device flows to the first target device, and the first service provided by the first associated device stops flowing to the first target device; The first type of service is a service that can only be transferred to one device at a time.

19. The method according to any one of claims 15 to 18, characterized in that The step of displaying a first service logo around a first associated device logo 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, displaying at least one target service identifier around the first associated device identifier, each of the target service identifiers indicating a service provided by the first associated device, and the at least one target service identifier including the first service identifier; Before displaying the first service logo and the first associated device logo around the second associated device logo in response to the operation of dragging the first service logo to the second associated device logo, the method further includes: In response to a second trigger operation on the first service identifier, display of service identifiers other than the first service identifier in the at least one target service identifier is canceled, and a prompt is displayed to drag the first service identifier to another device identifier to implement service transfer.

20. The method according to any one of claims 15 to 19, 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 the headset, displaying a second interface, the second interface including the first device identifier, the at least two associated device identifiers and the headset identifier, the headset identifier being displayed around the identifier of the second electronic device, and 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; In response to the operation of dragging the headset logo to the second target device logo, the headset logo is displayed around the second target device logo, the headset logo displayed around the second electronic device is cancelled, the second target device logo indicates a second target device, the second target device plays audio through the headset, and the second electronic device does not play audio through the headset; The second target device identifier is a device identifier other than the identifier of the second electronic device among the first device identifier and the at least two associated device identifiers.

21. The method according to any one of claims 15 to 20, characterized in that The first service is a service for sharing a keyboard and / or a mouse, the first associated device includes a keyboard and / or a mouse, and the second associated device includes a keyboard and / or a mouse; The method further comprises: In response to the operation of dragging the first service logo to the second associated device logo, the first service logo and the second associated device logo are displayed around the first associated device logo, and the first service provided by the second associated device flows to the first associated device.

22. The method according to any one of claims 15 to 21, 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 logo and a third service logo are displayed around the logo of the third electronic device, the second service logo indicates a second service, the third service logo indicates a third service, the second service and the third service are two services provided by the third electronic device, and 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 logos; In response to a selection operation on 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 the operation of dragging the first control to a third target device identifier, the second service identifier and the third service identifier are displayed around the third target device identifier, and the second service identifier and the third service identifier are also surrounded by an identifier of the third electronic device, the third target device identifier indicates a third target device, the second service and the third service provided by the third electronic device flow to the third target device, and 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.

23. 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, and the computer program code includes computer instructions, and when the one or more processors execute the computer instructions, the electronic device executes the method described in any one of claims 1-22.

24. A computer-readable storage medium comprising instructions, characterized in that: When the instructions are executed on an electronic device, the electronic device is caused to execute the method as claimed in any one of claims 1 to 22.

Images