Service flowing method, and device and storage medium

Through intelligent sorting and filtering algorithms, business flow between any two devices solves the limitations between devices, improves the convenience of user operation and the availability of devices, and in particular supports the flow of light devices through rich devices, thus improving the user experience.

WO2024230459A1PCT designated stage expired Publication Date: 2024-11-14HUAWEI TECH CO LTD
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2024/088989
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-05
Filing Date
2024-04-20
Publication Date
2024-11-14

AI Technical Summary

Technical Problem

In existing technologies, the business flow function between devices has significant limitations, especially when the device is far from the user, the user operation is cumbersome, resulting in poor usability.

Method used

It enables business flow between any two devices to be triggered by any device, and provides intelligent recommendations by using intelligent sorting and filtering algorithms, reducing the time and effort users spend on selection, and supporting lightweight devices to achieve flow functions through rich devices.

Benefits of technology

It improves the availability and user freedom of business processes between devices, reduces operation time and effort, expands the scope of controllable devices, and enhances the user experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024088989_14112024_PF_FP_ABST
    Figure CN2024088989_14112024_PF_FP_ABST
Patent Text Reader

Abstract

Provided in the present application are a service flowing method, and a device and a storage medium, wherein the method is applied to a first device, and the first device is any device in a communication system. The method comprises: receiving a first operation; displaying a first interface, wherein the first interface comprises options of m second devices in a communication system; receiving an operation for the option of an ith second device among the m second devices; determining the ith second device to be a source device of service flowing; displaying a second interface, wherein the second interface comprises options of n third devices in the communication system; receiving an operation for the option of a jth third device among the n third devices; and determining the jth third device to be a destination device of the service flowing, and triggering the ith second device to flow a first service to the jth third device. By means of the present application, implementation of service flowing between any two devices can be triggered by means of any device in a distributed scenario, thereby solving the problem of the current service flowing being limited, and improving the function availability.
Need to check novelty before this filing date? Find Prior Art

Description

Business flow method, device and storage medium

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on May 5, 2023, with application number 202310498761.3, and priority to the Chinese patent application entitled “Business Flow Method, Device and Storage Medium”, all contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of electronic technology, and in particular to a business flow method, device and storage medium. Background Art

[0003] Currently, devices can provide a service transfer function, that is, services such as video playback on one device can be performed on another device. When a user wants to transfer the service flow of device 1 to device 2, he needs to walk to device 1 or device 2, pick up device 1 or device 2, and perform a series of operations on device 1 or device 2. The user spends a lot of time and energy to achieve service transfer, and there are great limitations, especially when device 1 and / or device 2 are far away from the user. Therefore, the usability of the service transfer function is poor.

[0004] Summary of the Invention

[0005] This application provides a business flow method, device and storage medium, which can trigger any two devices to realize business flow in a distributed scenario through any device, solve the current limitations of business flow and improve functional availability.

[0006] A first aspect provides a business flow method, which is applied to a first device, where the first device is any device in a communication system, and the method includes: receiving a first operation; displaying a first interface, where the first interface includes options for m second devices in the communication system, where m is an integer not less than 1; receiving a second operation for options for the i-th second device among the m second devices, where i is an integer not less than 1 and not greater than m; in response to the second operation, determining that the i-th second device is the source device for business flow; displaying a second interface, where the second interface includes options for n third devices in the communication system, where n is an integer not less than 1; receiving a third operation for options for the j-th third device among the n third devices, where j is an integer not less than 1 and not greater than n; in response to the third operation, determining that the j-th third device is the target device for business flow, and triggering the i-th second device to transfer the first business flow to the j-th third device.

[0007] In some examples, the i-th second device is the first device, or is not the first device.

[0008] In some examples, the j-th third device is the first device, or is not the first device.

[0009] In some examples, the i-th second device and the j-th third device are any two devices in the communication system.

[0010] In the above method, any device in the communication system can receive user operations and trigger any two devices in the communication system to realize business flow, which can solve the limitations of general full-connection scenarios. Even if the second device and the third device are far away from the user or difficult to operate, the user can use any other device (that is, the first device, for example, the first device is closer to the user and / or more convenient to use) to trigger business flow. It can also solve the limitations of some specific full-connection scenarios (such scenarios can be set up with a controller with capabilities and fixed positions for triggering business flow). The user does not need to go to the controller to operate the controller, which reduces the time and energy spent by the user to realize business flow, greatly improves the user's freedom of device use in the full-connection scenario, and improves the availability of the business flow function.

[0011] In one possible implementation, the first interface includes options of the m second devices after sorting, and before displaying the first interface, the method further includes: sorting the m second devices based on a first algorithm; or, sending a first request message to a connected fourth device; receiving a first response message sent by the fourth device, the first response message including information of the m second devices sorted by the fourth device based on the first algorithm; wherein the first algorithm is related to at least one of the following parameters: the business operation status of the device, the number of times the device performs business flow as a source device, the number of flows of the business run by the device, and whether the business flow function is enabled on the device.

[0012] In some examples, sorting the m second devices based on the first algorithm is performed when the first device is a rich device; sending the first request message to the connected fourth device is performed when the first device is a light device and the fourth device is a rich device.

[0013] In the above method, the options of the m second devices that can be used as source devices for business flow displayed on the first interface can be sorted. Specifically, they can be sorted based on the business operation status of the device, the number of times the device performs business flow as a source device, the number of business flows run by the device, etc. The sorting method is based on the actual user experience and provides intelligent recommendations that suit the user's wishes. The user no longer needs to check one by one from a large number of devices in a distributed scenario to select the required source device, which reduces the time and energy spent by the user on selecting the source device, further facilitates the user's use, and improves the user experience.

[0014] In one possible implementation, the m second devices include the kth second device and the tth second device, the kth second device is displayed before the tth second device, k is an integer not less than 1 and not greater than m, and t is an integer not less than 1 and not greater than m, wherein the kth second device is the first device, the tth second device is not the first device, and the first device runs a transferable service; or, the kth second device is the fourth device, the tth second device is not the fourth device, and the first device does not run a transferable service; or, the kth second device runs a transferable service in the foreground, the tth second device runs a transferable service in the background, or the tth second device does not run a transferable service; or, the kth second device runs a transferable service in the background , the t-th second device does not run the transferable service; or, the k-th second device and the t-th second device respectively run the transferable second service and the third service in the foreground, and the number of transfers of the second service is greater than the number of transfers of the third service; or, the k-th second device and the t-th second device respectively run the transferable second service and the third service in the background, and the number of transfers of the second service is greater than the number of transfers of the third service; or, neither the k-th second device nor the t-th second device runs the transferable service, and the number of times the k-th second device performs service transfer as a source device is greater than the number of times the t-th second device performs service transfer as a source device; or, the k-th second device is a device with the service transfer function enabled, and the t-th second device is a device with the service transfer function not enabled.

[0015] In the above method, there can be multiple sorting rules for the second device that can serve as the source device for service flow. For example, the first device (i.e., the control device) that runs a service that can be transferred can be arranged before other devices. For another example, when the first device (i.e., the control device) that is a light device does not run the service that can be transferred, the rich device connected to the first device can be arranged before other devices. For another example, the device that runs a service that can be transferred in the foreground can be arranged before the device that does not run the service that can be transferred in the foreground. For another example, the device that runs a service that can be transferred in the background can be arranged before the device that does not run the service that can be transferred. For another example, when both run the service that can be transferred in the foreground or the background, the greater the number of transfers of the service that the device runs, the higher the priority in the sorting order. For another example, when neither runs the service that can be transferred, the greater the number of times the device performs service flow as a source device, the higher the priority in the sorting order. For another example, the device that has the service flow function enabled can be arranged before the device that has not enabled the service flow function. The sorting rules are diverse and are based on the actual user experience, providing intelligent recommendations that meet the user's needs and further enhance the user experience.

[0016] In one possible implementation, the second interface includes options for the n third devices after sorting. Before displaying the second interface, the method further includes: screening out the n third devices from the communication system based on the information of the first service, and sorting the n third devices based on a second algorithm; or, sending a second request message to the connected fourth device; receiving a second response message sent by the fourth device, the second response message including information of the n third devices sorted by the fourth device based on the second algorithm; wherein the second algorithm is related to at least one of the following parameters: the location of the device, the number of times the device is used, and the frequency of use of the device.

[0017] In some examples, filtering out the n third devices from the communication system based on information of the first service and sorting the n third devices based on a second algorithm is performed when the first device is a rich device; sending a second request message to the connected fourth device is performed when the first device is a light device and the fourth device is a rich device.

[0018] In a possible implementation, the n third devices are devices in the communication system whose device capabilities support performing the first service.

[0019] In the above method, the options of n third devices that can be used as target devices for business flow displayed on the second interface can be filtered and sorted. Users no longer need to check one by one from a large number of devices in a distributed scenario to select the required target device, which reduces the time and energy spent by users on selecting target devices, further facilitates user use, and improves user experience.

[0020] In one possible implementation, the method further includes: in response to the second operation, displaying a third interface, the third interface including options for p transferable services run by the i-th second device, where p is an integer not less than 1; receiving a fourth operation for options for the first service among the p transferable services; the displaying of the second interface includes: in response to the fourth operation, displaying the second interface, the n third devices being related to the first service.

[0021] In the above method, the user can also select the target service for service transfer based on the first device to meet the user's personalized needs when triggering service transfer, further improving the user experience.

[0022] In one possible implementation, the third interface includes options for the p transferable services after sorting. Before displaying the third interface, the method also includes: sorting the p transferable services based on a third algorithm; or, sending a third request message to a connected fourth device; receiving a third response message sent by the fourth device, the third response message including the p transferable services sorted by the fourth device based on the third algorithm; wherein the third algorithm is related to at least one of the following parameters: whether the service is running in the foreground, the time when the service was last used, and the number of times the service is transferred.

[0023] In some examples, the sorting of the p transferable services based on the third algorithm is performed when the first device is a rich device; the sending of the third request message to the connected fourth device is performed when the first device is a light device and the fourth device is a rich device.

[0024] In the above method, the options of p transferable businesses displayed on the third interface that can be used as target businesses for business transfer can be sorted. Specifically, they can be sorted based on information that users care about, such as whether the business is running in the foreground, the time when the business was last used, the number of times the business has been transferred, etc. The sorting method is based on the actual user experience and provides intelligent recommendations that suit the user's wishes, reducing the time and experience spent by the user on selecting the target business, further facilitating the user's use, and improving the user experience.

[0025] In a possible implementation, the first service is determined according to a preset rule. In some examples, the preset rule is that a transferable service running in the foreground of the source device is the target service.

[0026] In the above method, the target business of the business flow can also be determined by the device according to preset rules, without the user having to manually select the target business, reducing user operations and further reducing the time and energy spent by the user to trigger the business flow.

[0027] In one possible implementation, triggering the i-th second device to transfer the first service flow to the j-th third device includes: sending a fourth request message to the i-th second device; receiving a fourth response message sent by the i-th second device, the fourth response message including information about the first service; sending a first indication message to the j-th third device, the first indication message including information about the first service, the first indication message being used to instruct the j-th third device to display the user interface of the first service; or, sending a second indication message to the i-th second device, the second indication message being used for the i-th second device to send a third indication message to the j-th third device, the third indication message including information about the first service, the third indication message being used to instruct the j-th third device to display the user interface of the first service.

[0028] In one possible implementation, the first device is a device having first system capabilities. In some examples, the first device is a rich device.

[0029] In the above method, there may be multiple ways for the first device to trigger the i-th second device to transfer the first service flow to the j-th third device, which can be applied to different scenarios and has wider applicability.

[0030] In one possible implementation, triggering the i-th second device to transfer the first service flow to the j-th third device includes: sending a fourth indication message to a connected fourth device, wherein the fourth indication message is used to instruct the fourth device to trigger the i-th second device to transfer the first service flow to the j-th third device.

[0031] In one possible implementation, the first device is a device that does not have the first system capability, and the fourth device is a device that has the first system capability. In some examples, the first device is a light device, and the fourth device is a rich device.

[0032] In some examples, a device with the first system capability can independently implement at least one of the following: sorting the m second devices based on the first algorithm; screening out the n third devices from the communication system according to the information of the first service, and sorting the n third devices based on the second algorithm; sorting the p transferable services based on the third algorithm; triggering the i-th second device to transfer the first service to the j-th third device.

[0033] In the above method, the light device as the first device can trigger business flow through the connected rich device (i.e., the fourth device). This can be understood as enabling the light device to trigger the business flow function in a distributed scenario, solving the problem that the light device cannot serve as a control device due to weak or missing system capabilities, greatly expanding the range of control devices that users can operate in distributed scenarios, reducing the limitations of business flow functions, and improving user experience.

[0034] In one possible implementation, the method further includes: sending a registration message to the fourth device, the registration message being the input for the fourth device to verify whether the identity of the first device is legal; and when the fourth device determines that the identity of the first device is legal, the fourth device triggers the i-th second device to transfer the first service flow to the j-th third device according to the fourth indication message.

[0035] In some examples, the fourth indication message is used by the fourth device to refuse to trigger the i-th second device to transfer the first service flow to the j-th third device when it determines that the identity of the first device is illegal.

[0036] In the above method, before the fourth device assists the first device in triggering the business flow, it can first verify whether the identity of the first device is legal. Only when it is legal will the business flow be triggered, thereby increasing the security of the business flow function.

[0037] In one possible implementation, the receiving of the first operation includes: when connected to the fourth device, receiving the first operation, and the first interface is displayed based on the information of the m second devices sent by the fourth device; before receiving the first operation, the method also includes: when connected to the fifth device, receiving the fifth operation; displaying the fourth interface, the fourth interface is the same as the first interface; and canceling the display of the fourth interface when the connection with the fifth device is disconnected.

[0038] In some examples, the first device is a light device and the fourth and fifth devices are rich devices.

[0039] In the above method, when the first device and the fifth device are connected, the fourth interface (including the options of m second devices that can serve as source devices for business flow) can be displayed through the fifth device. When the connection is disconnected, the fourth interface is cancelled, which can be understood as the disconnection of the process of triggering business flow (which can be simply referred to as the triggering process). After the first device switches from being connected to the fifth device to being connected to the fourth device, the first interface that is the same as the previous fourth interface can be redisplayed through the fourth device, so that the user can continue the previous triggering process instead of having to restart a new triggering process. In particular, when the user has already made a selection in the previous triggering process, the user does not need to reselect, which further facilitates user use.

[0040] In one possible implementation, the receiving of the first operation includes: when connected to the fourth device, receiving the first operation, and the first interface is displayed based on the information of the m second devices sent by the fourth device; before receiving the first operation, the method also includes: when not connected to the fourth device, receiving a sixth operation, and the sixth operation is the same as the first operation; displaying a fifth interface, and the fifth interface includes a prompt message of business flow failure.

[0041] In the above method, when the first device, which is a light device, is not connected to the rich device, if the sixth operation for triggering business flow is received, a prompt message can be displayed to enable the user to operate the first device to connect with the rich device and then implement the process of triggering business flow through the first device (which can be simply referred to as the triggering process). The user can intuitively obtain the reason why the triggering process cannot be performed and take countermeasures. For example, instead of changing to other devices to implement the triggering process, the user can operate the first device to connect with the rich device, thereby further improving the user experience.

[0042] In one possible implementation, receiving the first operation includes: receiving the first operation on the control of the super terminal in the control center interface; or, when displaying the sixth interface of the first application, receiving the first operation on the flow control in the sixth interface; or receiving the first operation for calling the multitasking center.

[0043] In the above method, there can be multiple first operations for triggering business flow, which can be applied to different scenarios. For example, when the first device displays the sixth interface of the first application, the user can directly operate the flow control of the current interface, instead of executing the user operation of the control center interface and then operating the control of the super terminal in the control center interface. It is more widely applicable, further facilitates user use, and improves user experience.

[0044] In one possible implementation, the method further includes: when displaying the seventh interface, receiving a seventh operation on the reflow control in the seventh interface; in response to the seventh operation, triggering the j-th third device to transfer the first business flow back to the i-th second device.

[0045] In the above method, after the first device triggers the i-th second device to transfer the first business flow to the j-th third device, it can also provide a "one-key reflow" function, that is, performing one operation can enable the first device to trigger the j-th third device to transfer the first business flow back to the i-th second device, further facilitating user use and improving user experience.

[0046] The second aspect provides a device including a transceiver, a processor and a memory; the above-mentioned memory is used to store the program, and the above-mentioned processor calls the above-mentioned program to execute the business flow method provided by the first aspect of this application and any implementation method of the first aspect.

[0047] The third aspect provides a storage medium storing a program. When the program is executed by a processor, the business flow method provided by the first aspect of the present application and any implementation method of the first aspect is implemented.

[0048] The fourth aspect provides a program product, which, when running on a device, enables the device to execute the business flow method provided by the first aspect of this application and any implementation of the first aspect.

[0049] A fifth aspect provides a device, which includes a method or apparatus for executing any aspect or embodiment of the present application. The device is, for example, a chip.

[0050] It should be understood that the description of technical features, technical solutions, beneficial effects or similar language in this application does not imply that all features and advantages can be realized in any single embodiment. On the contrary, it is understood that the description of a feature or beneficial effect means that a specific technical feature, technical solution or beneficial effect is included in at least one embodiment. Therefore, the description of a technical feature, technical solution or beneficial effect in this application does not necessarily refer to the same embodiment. Furthermore, the technical features, technical solutions and beneficial effects described in this application can also be combined in any appropriate manner. Those skilled in the art will understand that this application can be implemented without one or more specific technical features, technical solutions or beneficial effects of a specific embodiment. In other embodiments, additional technical features and beneficial effects can also be identified in specific embodiments that do not embody all embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] The following is an introduction to the drawings used in this application.

[0052] FIG1 is a schematic diagram of the architecture of a communication system provided by the present application;

[0053] FIG2 is a schematic diagram of the hardware structure of a device provided by the present application;

[0054] FIG3 is a schematic diagram of the software architecture of a device provided by this application;

[0055] FIG4 is a schematic diagram of the architecture of a device provided by the present application;

[0056] Figures 5A-5D are schematic diagrams of a service flow interface provided by the present application;

[0057] Figures 6A-6E are schematic diagrams of some user interfaces provided in this application;

[0058] Figures 7A and 7B are schematic diagrams of another method of calling up a business flow interface provided by the present application;

[0059] Figures 8A and 8B are schematic diagrams of another method of calling up a business flow interface provided by the present application;

[0060] FIG9A and FIG9B are schematic diagrams of some further user interfaces provided by the present application;

[0061] Figures 10A and 10B are schematic diagrams of another method of calling up a business flow interface provided by the present application;

[0062] FIG10C and FIG10D are schematic diagrams of some further user interfaces provided by the present application;

[0063] Figures 11A and 11B are schematic diagrams of another method of calling up a business flow interface provided by the present application;

[0064] FIG12 is a schematic diagram of a setting interface provided by the present application;

[0065] FIG13 is a flow chart of a business flow method provided by the present application;

[0066] FIG14 is a flow chart of another business flow method provided by the present application;

[0067] FIG15 is a flow chart of a sorting process provided by the present application. DETAILED DESCRIPTION

[0068] The technical solutions in the embodiments of the present application will be described below in conjunction with the accompanying drawings. In the description of the embodiments of the present application, unless otherwise specified, " / " represents or, for example, A / B can represent A or B; "and / or" in the text is merely a description of the association relationship between 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. In addition, in the description of the embodiments of the present application, "multiple" refers to two or more than two.

[0069] In the following, the terms "first" and "second" are used for descriptive purposes only and should not be understood to imply or suggest relative importance or implicitly indicate the number of the technical features indicated. Therefore, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. In the description of the embodiments of this application, unless otherwise specified, "plurality" means two or more.

[0070] First, the communication system 10 involved in the embodiment of the present application is introduced as an example.

[0071] Please refer to FIG1 , which is a schematic diagram of the architecture of a communication system 10 provided in an embodiment of the present application.

[0072] The communication system 10 in the present application may include multiple devices. Taking any one of the multiple devices (referred to as device 100) as an example for illustration, as shown in Figure 1, the device 100 can be connected and communicated with at least one device in the communication system 10 via a wired and / or wireless method. The wired method includes, but is not limited to, a high-definition multimedia interface (HDMI), a universal serial bus (USB), a coaxial cable, an optical fiber, etc., and the wireless method includes, but is not limited to, Bluetooth, wireless fidelity (Wi-Fi), near field communication technology (NFC), ultra wide band (UWB), etc.

[0073] In one embodiment, the device 100 can be directly connected to at least one device in the communication system 10. For example, as shown in FIG1 , the device 100 can be connected to the device 200 via a wireless method such as Bluetooth, Wi-Fi, NFC, or UWB.

[0074] In one embodiment, device 100 may be indirectly connected to at least one device in communication system 10. For example, as shown in FIG1 , device 100 may be connected to device 400 via network 300. Optionally, network 300 may include server 301, which may be a hardware server or a virtual server. Optionally, network 300 may include router 302, etc. Optionally, device 100 and device 400 may be devices connected to the same local area network. In some examples, device 100 and device 400 may have the same application installed (referred to as application A) and may log in to the same account or associated account through application A. Device 100 may communicate with device 400 via server 301 in network 300 (e.g., an application server for providing services for application A). This is not limiting. Alternatively, the device may log in to an account through other means such as a mini-program without installing an application, or may not log in to an account. This application does not limit the specific method of connection and communication via network 300.

[0075] Not limited to the above embodiment, in another embodiment, the device 100 can also obtain information about at least one unconnected device in the communication system 10, and establish a connection with the corresponding device based on the obtained information when a preset condition is met (for example, a user operation for triggering a connection is received). In some examples, the device 100 can discover at least one device and obtain information about these devices through wired and / or wireless means (for example, Bluetooth, Wi-Fi, etc.). Not limited to this, in other examples, the device 100 can obtain information about historically connected devices (for example, this information is stored when connected and can be subsequently obtained from a memory). In other examples, the device 100 can also obtain information about at least one device through the server 301 in the network 300. For example, after the device 100 logs in to account A, it can obtain information about devices that have previously logged in to account A from the server 301. This application does not limit the specific method for the device 100 to obtain information about unconnected devices.

[0076] The form and number of devices shown in Figure 1 are only examples. In specific implementations, they can be devices of other forms. For example, the router 302 can be replaced by a switch. The number of devices can be more or less. For example, the device 100 can be directly connected to multiple devices 200. This application does not limit this.

[0077] In the present application, any device in the communication system 10 (assuming it is device 100) can receive a user operation for triggering business flow (referred to as a trigger operation), and in response to the trigger operation, trigger the implementation of business flow (also referred to as task flow) between any two devices in the communication system 10. For example, device 100 can respond to the user operation to trigger device 200 and device 400 to implement business flow: business 1 performed by device 200 is transferred to device 400. In this business flow scenario, device 100 can be called a control device, device 200 can be called a source device, device 400 can be called a target device, and business 1 can be called a target business. This can solve the limitations of general fully connected scenarios. Even if device 200 and device 400 are far away from the user, the user can use device 100, which is closer and more convenient to use, to trigger business flow. This can also solve the limitations of some specific fully connected scenarios (this scenario can be equipped with a controller with fixed capabilities and positions, and the controller can be used to trigger any two devices in the scenario to achieve business flow). The user does not need to go to the controller to operate the controller (such as a router), which reduces the time and energy spent by the user to achieve business flow, greatly improves the user's freedom to use devices in the fully connected scenario, and improves the availability of the business flow function.

[0078] Among them, the control device operated by the user (such as the above-mentioned device 100) can be a device with strong system capabilities (such as hardware capabilities such as processors, and software capabilities such as supported protocols and supported frameworks) that can independently trigger business flows, and can be called a rich device. The control device operated by the user can also be a device with weak or missing system capabilities that cannot independently trigger business flows, and can be called a lightweight device (referred to as a light device). As a control device, a light device can trigger business flows with the help of connected rich devices. In other words, the range of control devices that can be operated by users is wider, giving users the ability to freely control (to achieve business flows) without moving, which greatly improves the user experience.

[0079] It is understandable that the control device, source device, and target device are all role concepts, not physical concepts. A device can have multiple roles. In some examples, device 100 can trigger a business flow in response to a user operation: Business 2 performed by device 100 flows to device 200. In this business flow scenario, device 100 is both a control device and a source device. Not limited to this, in other examples, device 100 can also trigger a business flow in response to a user operation: Business 3 performed by device 200 flows to device 100. In this case, device 100 is both a control device and a target device. However, the source device and the target device are two different hardware devices.

[0080] The services of any device in the communication system 10 may include services that can be transferred to other devices (referred to as transferable services) and services that cannot be transferred to other devices (referred to as non-transferable services). Transferable services may include but are not limited to audio / video playback, audio / video calls, partial user interfaces of applications (such as product details interface, game interface, etc.), and meta-service (feature ability, FA) cards (such as weather cards, express service cards, etc.).

[0081] Any device in the communication system 10 may not perform / run any business, or may perform / run at least one business. The user-visible and interactive business in the at least one business may be called a foreground business, and the device may display the user interface of the foreground business, which may also be referred to as the device running the business in the foreground; the user-invisible and non-interactive business in the at least one business may be referred to as a background business (the device will not display the user interface of the background business, but will still run the background business, which may also be referred to as the device running the business in the background. It can be understood that foreground business and background business are role concepts, not physical concepts, and a business can be different roles in different scenarios.

[0082] In this application, a device may be a mobile phone, a tablet computer, a handheld computer, a desktop computer, a laptop computer, an ultra-mobile personal computer (UMPC), a netbook, a cellular phone, a personal digital assistant (PDA), as well as smart home devices such as smart TVs and smart cameras, wearable devices such as smart bracelets, smart watches, and smart glasses, extended reality (XR) devices such as augmented reality (AR), virtual reality (VR), and mixed reality (MR), in-vehicle devices, routers, or smart city devices. The embodiments of this application do not impose any special restrictions on the specific type of device.

[0083] FIG2 exemplarily shows a schematic diagram of the hardware structure of the device 100 .

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

[0085] It should be understood that the structures illustrated in the embodiments of the present application do not constitute a specific limitation on the device 100. In other embodiments of the present application, the device 100 may include more or fewer components than shown, or may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

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

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

[0088] Processor 110 may also include a memory for storing instructions and data. In one embodiment, the memory in processor 110 is a cache memory. This memory can store instructions or data that have just been used or are being recycled by processor 110. If processor 110 needs to use the same instruction or data again, it can directly retrieve it from the memory. This avoids duplicate accesses, reduces processor 110 latency, and thus improves system efficiency.

[0089] The charging management module 140 is configured to receive charging input from a charger. The charger can be either a wireless charger or a wired charger. In some wired charging implementations, the charging management module 140 can receive charging input from the wired charger via the USB interface 130. In some wireless charging implementations, the charging management module 140 can receive wireless charging input via the wireless charging coil of the device 100. While charging the battery 142, the charging management module 140 can also provide power to the device 100 via the power management module 141.

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

[0091] The wireless communication function of the device 100 can be implemented by antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor, etc. The device 100 can communicate with any device in the communication system 10 through the wireless communication function.

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

[0093] The mobile communication module 150 can provide wireless communication solutions for the device 100, including second generation (2G), third generation (3G), fourth generation (4G), fifth generation (5G), and sixth generation (6G). The mobile communication module 150 can include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), and the like. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, filter and amplify the received electromagnetic waves, and transmit them to the modem processor for demodulation. The mobile communication module 150 can also amplify the signals modulated by the modem processor and convert them into electromagnetic waves for radiation via the antenna 1. In one embodiment, at least some of the functional modules of the mobile communication module 150 can be located in the processor 110. In another embodiment, at least some of the functional modules of the mobile communication module 150 and at least some of the modules of the processor 110 can be located in the same device.

[0094] The modem processor may include a modulator and a demodulator. The modulator is used to modulate the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After being processed by the baseband processor, the low-frequency baseband signal is passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 170A, the receiver 170B, etc.) or displays an image or video through the display screen 194. In one embodiment, the modem processor may be an independent device. In another embodiment, the modem processor may be independent of the processor 110 and be set in the same device as the mobile communication module 150 or other functional modules.

[0095] The wireless communication module 160 can provide wireless communication solutions applied to the device 100, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc. The wireless communication module 160 can be one or more devices that integrate at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

[0096] Device 100 implements display functionality through a GPU, display screen 194, and an application processor. A GPU is a microprocessor for image processing that connects display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or modify display information.

[0097] The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. In one embodiment, the device 100 may include one or N display screens 194, where N is a positive integer greater than one.

[0098] The device 100 can implement a shooting function through an ISP, a camera 193, a video codec, a GPU, a display 194, and an application processor.

[0099] The ISP is used to process data fed back by the camera 193. For example, when taking a photo, the shutter is opened, and light is transmitted through the lens to the camera's photosensitive element. The light signal is converted into an electrical signal, which is then transmitted to the ISP for processing and converted into an image visible to the naked eye.

[0100] The camera 193 is used to capture still images or videos. In one embodiment, the device 100 may include 1 or N cameras 193, where N is a positive integer greater than 1.

[0101] The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the device 100.

[0102] The internal memory 121 can be used to store executable program code, which includes instructions. The internal memory 121 may include a program storage area and a data storage area. The program storage area may store an operating system, an application required for at least one function (such as a sound playback function), etc. The data storage area may store data (such as audio data) created during the use of the device 100, etc. In addition, the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device. The processor 110 executes various functional applications and data processing of the device 100 by running instructions stored in the internal memory 121 and / or instructions stored in a memory provided in the processor.

[0103] The device 100 can implement audio functions through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone jack 170D, and the application processor.

[0104] The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals. The audio module 170 can also be used to encode and decode audio signals. The speaker 170A, also known as a "speaker", is used to convert audio electrical signals into sound signals. The receiver 170B, also known as a "handset", is used to convert audio electrical signals into sound signals. The microphone 170C, also known as a "microphone" or "microphone", is used to convert sound signals into electrical signals. The headphone jack 170D is used to connect wired headphones. The pressure sensor 180A is used to sense pressure signals and can convert them into electrical signals. The gyroscope sensor 180B can be used to determine the movement posture of the device 100. The air pressure sensor 180C is used to measure air pressure. The magnetic sensor 180D includes a Hall sensor. The acceleration sensor 180E can detect the magnitude of the acceleration of the device 100 in various directions (generally three axes). The distance sensor 180F is used to measure distance. The proximity light sensor 180G may include, for example, a light emitting diode (LED) and a light detector, such as a photodiode. The ambient light sensor 180L is used to sense the brightness of ambient light. The fingerprint sensor 180H is used to collect fingerprints. The temperature sensor 180J is used to detect temperature. The touch sensor 180K is also called a "touch device". The touch sensor 180K can be set on the display screen 194, and the touch sensor 180K and the display screen 194 form a touch screen, also called a "touch screen". The bone conduction sensor 180M can obtain vibration signals. The buttons 190 include a power button, a volume button, etc. The motor 191 can generate vibration prompts. The indicator 192 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 195 is used to connect a SIM card or eSIM.

[0105] The software system of the device 100 can adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. For example, the software system with a layered architecture can be an Android system, a Harmony operating system (OS), or other software systems. The embodiment of the present application takes the Android system with a layered architecture as an example to illustrate the software structure of the device 100.

[0106] FIG3 exemplarily shows a schematic diagram of the software architecture of the device 100 .

[0107] A layered architecture divides software into several layers, each with distinct roles and responsibilities. Layers communicate with each other through software interfaces. In one embodiment, the Android system is divided into four layers: the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer.

[0108] The application layer can include a series of application packages. As shown in Figure 3, the application package may include applications such as camera, video, music, gallery, short message, call, navigation, Bluetooth, browser, etc. The applications in this application can also be replaced by other software such as mini-programs, atomic services / FA cards, etc.

[0109] The application framework layer provides an application programming interface (API) and programming framework for applications in the application layer. The application framework layer includes some predefined functions. As shown in Figure 2, the application framework layer may include a window manager, content provider, view system, telephony manager, resource manager, notification manager, and so on.

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

[0111] Content providers are used to store and retrieve data and make it accessible to applications. The data may include video, images, audio, etc.

[0112] The view system includes visual controls, such as those for displaying text and images. The view system is used to build applications. A display interface can consist of one or more views. For example, a display interface containing a text notification icon might include a view for displaying text and a view for displaying images.

[0113] The phone manager is used to provide communication functions of the device 100, such as management of call status (including answering, hanging up, etc.).

[0114] The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, etc.

[0115] The Notification Manager allows applications to display notifications in the status bar. These messages can be displayed briefly and then disappear automatically, without requiring user interaction. The Notification Manager can also display notifications in the system's top status bar as icons or scrolling text, such as notifications from background applications. It can also display notifications in the form of dialog windows on the screen. Examples include displaying text messages in the status bar and emitting beeping sounds.

[0116] Android Runtime includes core libraries and a virtual machine. Android runtime is responsible for scheduling and management of the Android system.

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

[0118] The application layer and application framework layer run in a virtual machine. The virtual machine executes Java files in the application layer and application framework layer as binary files. The virtual machine manages object lifecycles, stack management, thread management, security and exception management, and garbage collection.

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

[0120] The surface manager is used to manage the display subsystem and provide the fusion of two-dimensional and three-dimensional layers for multiple applications.

[0121] The media library supports playback and recording of a variety of common audio and video formats, as well as static image files. The media library can support a variety of audio and video encoding formats, such as MPEG4, H.264, etc.

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

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

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

[0125] The following describes the workflow of the software and hardware of device 100 in combination with business flow scenarios.

[0126] Assume that the device 100 displays the audio playback interface of the music application in the foreground (also known as running the audio playback service in the foreground). When the touch sensor 180K receives a touch operation, the corresponding hardware interrupt is sent to the kernel layer. The kernel layer processes the touch operation into a raw input event (including touch coordinates, touch operation timestamp and other information). The raw input event is stored in the kernel layer. The application framework layer obtains the raw input event from the kernel layer and identifies the control corresponding to the input event. For example, if the touch operation is a touch single-click operation and the control corresponding to the single-click operation is the flow control of the music application, the music application calls the interface of the application framework layer to obtain the device identifier of the target device that can be used as the audio playback service flow, and then controls the display driver by calling the kernel layer, and displays the obtained device identifier through the display screen 194, so that the user can select the device identifier of the target device for the audio playback service flow from the displayed device identifier. At this time, the device 100 can default the source device to this device and the target service to the foreground service (i.e., the audio playback service).

[0127] FIG4 exemplarily shows a schematic diagram of the architecture of a device 100 .

[0128] As shown in FIG4 , the device 100 may include a distributed information management module 201 , a database 202 , an input module 203 , a source device display module 204 , a source device service display module 205 , a target device display module 206 , and a service flow module 207 , wherein:

[0129] The distributed information management module 201 can be used to obtain and manage device identifications and service information of multiple devices in the communication system 10. The device identification can be information used to distinguish different devices. The device identification can include but is not limited to at least one of the device name, device type, communication address, device capabilities, device identity document (ID) (which can be used to uniquely identify the device), device icon, and device model. The device capabilities can include but are not limited to at least one of hardware capabilities such as display information (e.g., whether a display is included, the number of display screens, etc.) and microphone information, and at least one of software capabilities such as supported protocols and supported software frameworks. Service information can include but is not limited to at least one of a service identification, the type of service performed by the device (e.g., video playback, audio playback, the product details interface of a shopping application, an express service card, etc.), service attributes (e.g., foreground service and background service), whether it is a transferable service, and service usage time (i.e., the time when a user last used the service). The service identification can be information used to distinguish different services. The service identification can include but is not limited to at least one of the service name, the name of the application to which the service belongs, the service icon, and related information about the service (e.g., the audio name and singer name for audio playback services).

[0130] Database 202 can be used to store the service flow counts of multiple devices in communication system 10, as well as the flow counts of multiple service types. The service flow count of a device is the number of times the device performs service flow as a source device, and the flow count of a service type is the number of times a service belonging to that service type performs service flow as a target service. The flow count of subsequent service types can be simply referred to as the service flow count. For example, the flow count of the video playback service can be the sum of the flow count of the video playback service of the video 1 application and the flow count of the video playback service of the video 2 application. In some examples, each time any device in communication system 10 performs a service flow, device 100 can record and update the content stored in database 202.

[0131] The input module 203 can be used to receive user operations. As shown in Figure 4, 1, the input module 203 can receive a user trigger operation (i.e., a user operation for triggering a business flow). In response to the trigger operation, the source device display module 204 can obtain the device identifications of multiple candidate devices that can be used as source devices for business flow from the distributed information management module 201, and can sort these multiple candidate devices according to usage information and current business operation information, and finally display the device identifications of the sorted multiple candidate devices (which can be simply referred to as sorted device identifications). The sorted device identifications can be used by the user to select the source device for this business flow. Among them, the above-mentioned usage information may include the number of business flows and the number of business flows of the candidate device, such as the number read by the source device display module 204 from the database 202, and the above-mentioned current business operation information may include information about the currently transferable business of the candidate device, such as the (business information) obtained by the source device display module 204 from the distributed information management module 201.

[0132] As shown in Figure 4, when the source device display module 204 displays the sorted device identification, the input module 203 can receive an operation for selecting a source device (assuming that it is a user operation for the device identification of device A in the sorted device identification, and device A is the source device selected by the user). In response to the operation, the source device business display module 205 can obtain information about the business performed by device A (for example, including foreground business and background business), such as obtaining business information from the distributed information management module 201, or obtaining business information from device A. Then, the source device business display module 205 can sort the multiple acquired businesses, for example, according to the usage time of the business and / or the number of business transfers read from the database 202, and finally display the business identifications of the sorted multiple businesses (which can be simply referred to as sorted business identifications). The sorted business identifications can be used by the user to select the target business for this business transfer.

[0133] As shown in Figure 4, when the source device service display module 205 displays the sorted service identifiers, the input module 203 can receive an operation for selecting a target service (assuming that it is a user operation for the service identifier of service A in the sorted service identifiers, in which case service A is the target service selected by the user). In response to this operation, the target device display module 206 can obtain the device identifiers of candidate devices that can be used as target devices for service transfer (i.e., target devices to which service A can be transferred). For example, candidate devices that can perform service A are screened out based on the device capabilities obtained from the distributed information management module 201. Then, the target device display module 206 can sort the multiple candidate devices obtained, for example, based on device usage time, device usage frequency, device location (for example, including distance from the source device), etc., and finally display the sorted device identifiers. The sorted device identifiers can be used by the user to select the target device for this service transfer.

[0134] As shown in Figure 4, when the target device display module 206 displays the sorted device identification, the input module 203 can receive an operation for selecting a target device (assuming it is a user operation for the device identification of device B in the above-mentioned sorted device identification, and at this time, device B is the target device selected by the user). In response to the operation, the business flow module 207 can trigger device A and device B to realize business flow: the business A of device A is transferred to device B.

[0135] Not limited to the implementation shown in Figure 4, in another implementation, the device 100 may also default to the device being the source device of this business transfer. In this case, the source device display module 204 may not obtain and display the sorted device identification. In another implementation, when the source device only runs one business (foreground business or background business), the device 100 may also default to the business as the target business of this business transfer, or when the source device runs multiple businesses, the device 100 may also default to the foreground business as the target business of this business transfer. In this case, the source device business display module 205 may not obtain and display the sorted business identification. This application does not limit this.

[0136] Not limited to the implementation shown in Figure 4, in another implementation, any two modules shown in Figure 4 can be integrated together, for example, the distributed information management module 201 and the database 202 can be integrated together. In another implementation, any module shown in Figure 4 can include multiple modules, for example, the source device display module 204 can include a sorting module and a display module. This application does not limit this.

[0137] The following introduces the application scenario of the business flow method provided in the embodiment of the present application and the user interface example in the application scenario.

[0138] 5A to 5D exemplarily show schematic diagrams related to a service flow interface of the calling device 100 .

[0139] As shown in Figure 5A, the device 100 can display a user interface 510, for example, the user interface 510 is a desktop. The user interface 510 may include a status bar 511, icons 512 of multiple applications, and a page indicator 513. The status bar 511 may include at least one of a signal strength indicator for a mobile communication signal (e.g., a 5G signal), a signal strength indicator for a Wi-Fi signal, an indicator for Bluetooth, a battery status indicator, a time indicator, etc. The icons 512 of multiple applications may include, for example, but not limited to, icons for Video 1, Video 2, Music, Calls, Weather, and a browser. The desktop of the device 100 may include multiple pages, and the page indicator 513 may be used to indicate which page the user is currently viewing. In some examples, the device 100 may display other pages in response to user operations (e.g., swiping left or right).

[0140] As shown in Figure 5A, the device 100 can receive a user operation, such as an operation of sliding downward from the upper edge of the screen (such as the location of the status bar 511). In response to the user operation, the device 100 can display the user interface 520 shown in Figure 5B, for example, the user interface 520 is a control center interface.

[0141] As shown in Figure 5B, user interface 520 may include a play card 521, a Wi-Fi control 522, a Bluetooth control 523, icons 524 for multiple common functions, and a hyperterminal card 525. The play card 521 includes the characters "Not Playing," indicating that device 100 is not currently running the video playback service or the audio playback service. The Wi-Fi control 522 includes the characters "Signal Source 1," indicating that device 100 is currently connected to a Wi-Fi signal named "Signal Source 1." The icons 524 for multiple common functions include, but are not limited to, a flashlight icon, a ringtone / mute icon, a screen rotation icon, a share icon, an airplane mode icon, and a brightness adjustment bar. Card 525 may include icons for currently connected devices, as well as the names and / or types of these devices, such as an icon for a watch named AAA (which may be referred to as watch AAA or device AAA; other devices will be described using abbreviated names and will not be detailed here), an icon for a large screen BBB, and also includes control 525A. Without limitation, in other examples, when the device 100 is not connected to any device, a prompt message may be displayed in the card 525 to prompt the user to search for other devices (eg, via the control 525A).

[0142] As shown in Figure 5B, the device 100 can receive a user operation (such as a touch operation) on the control 525A. In response to the user operation, the device 100 can display the user interface 530 shown in Figure 5C. In one embodiment, the user interface 530 can be a business flow interface.

[0143] As shown in Figure 5C, the user interface 530 may include an icon 531 of the device 100, icons of candidate devices detected by the device 100 that can be used as target devices for business flow, the names and / or types of the above-mentioned candidate devices, etc. For example, the icon of the device 100 is located in the preset area 1 shown in the user interface 530 (for example, the circular area shown in Figure 5C), and the icons of the above-mentioned candidate devices may be located in the preset area 2 surrounding the icon 531 of the device 100 (for example, the annular area shown in Figure 5C). The embodiment of the present application does not specifically limit the shape and position of the above-mentioned preset area 1 and preset area 2. The following description will be made by taking the preset area 1 as the circular area shown in Figure 5C and the preset area 2 as the annular area shown in Figure 5C as an example. The icons of the above-mentioned candidate devices may include: an icon 532 of the watch AAA, an icon 533 of the large screen BBB, an icon 534 of the laptop CCC, an icon 535 of the mobile phone DDD, and an icon 536 of the speaker EEE.

[0144] In one embodiment, the display manner of the icons of the candidate devices shown in the user interface 530 can be related to the distance between the candidate device and the device 100. Optionally, the distance between the icon of any candidate device and the icon 531 of the device 100 is proportional to the actual distance between the candidate device and the device. For example, the distance between the icon 532 of the watch AAA shown in Figure 5C and the icon 531 of the device 100 is smaller than the distance between the icon 533 of the large screen BBB shown in Figure 5C and the icon 531 of the device 100. Accordingly, the actual distance between the watch AAA and the device 100 is smaller than the actual distance between the large screen BBB and the device 100.

[0145] As shown in FIG5C , user interface 530 can be used by a user to select a target device for a business flow. The icon of any candidate device shown in user interface 530 can receive a user operation, such as a drag operation toward preset area 1. In response to the user operation, device 100 can determine that the candidate device is the target device for the business flow. In this case, device 100 defaults to the current device as the source device for the business flow. It can be understood that user interface 530 can be a user interface for two-way flow. Two-way flow can be a business flow in which the current device is the default source device and the user selects the target device. However, two-way flow can also be a business flow in which the current device is the default target device and the user selects the source device. Two-way flow in which the current device is the default source device is used as an example for description. In one embodiment, the device 100 may default the foreground business of the device as the target business for business transfer, but is not limited thereto. It may also default a specific type of business as the target business, which is not limited in this application. In another embodiment, after the device 100 determines the target device, for example, in response to the above-mentioned operation of dragging the candidate device to the preset area 1, the service identification performed by the device 100 (i.e., the source device) may be displayed, and the service identification is used by the user to select the target business for business transfer. Among them, the user operation for calling the user interface (e.g., user interface 530) for dual-end transfer may include the operation of sliding downward from the upper edge of the screen as shown in FIG5A, and the user operation on the control 525A as shown in FIG5B.

[0146] As shown in Figure 5C, the user interface 530 also includes a control 537. The device 100 can receive user operations (such as touch operations) on the control 537, and in response to the user operations, display the user interface 540 shown in Figure 5D. In one embodiment, the user interface 540 can be a business flow interface.

[0147] As shown in Figure 5D, the user interface 540 may include prompt information 541 and a device identification 542. The prompt information 541 may include the characters "free flow" and "please select the source device", indicating that the user interface 540 is an interface for selecting the source device for business flow. The user interface 540 can be a free flow user interface, and free flow can be a business flow in which the user selects the source device and the target device. The device identification 542 may include controls of candidate devices detected by the device 100 that can be used as source devices for business flow, wherein any one of the controls may include the device identification of the corresponding candidate device, such as the icon of the candidate device and the name of the candidate device. The multiple candidate devices shown in the device identification 542 may be sorted, including from front to back: mobile phone FFF (i.e., device 100 / this device), laptop computer CCC, mobile phone DDD, large screen BBB, speaker EEE, watch AAA, wherein the watch AAA is set to not be allowed to be a source device for free flow (an example of the setting interface can be seen in Figure 12 below, not described in detail for the time being) (it can also be called that the business flow function is not enabled), so the display mode is different from the display mode of other devices in the device identification 542. For example, the background color of the watch AAA is set to dark gray, but not limited to this. The display mode may also include features such as background transparency, font color, size, type, whether to display prompt information, etc. This application does not limit this. Among them, the user operation for calling up the free-flow user interface (such as user interface 540) may include the operation of sliding down from the upper edge of the screen as shown in Figure 5A, the user operation for control 525A as shown in Figure 5B, and the user operation for control 537 as shown in Figure 5C.

[0148] In one embodiment, the mobile phone FFF, laptop computer CCC, mobile phone DDD, large screen BBB, and speaker EEE shown in the device identification 542 are not running any transferable services, and can be considered to belong to the same priority. Moreover, these devices are arranged in descending order according to the number of business flows of the devices: mobile phone FFF, laptop computer CCC, mobile phone DDD, large screen BBB, and speaker EEE, which is consistent with the display order / arrangement order of the device identification 542. It can be understood that for devices that are not running any transferable services, they can be sorted according to the number of business flows of the devices.

[0149] In another embodiment, the mobile phone FFF, laptop computer CCC, mobile phone DDD, and large screen BBB shown in device identification 542 all have transferable services running in the foreground or background, and the speaker EEE is not running any transferable services. Therefore, the display mode of the speaker EEE is different from that of other devices. For example, the background color of the speaker EEE is set to light gray. In some examples, it is assumed that device 100 counts the number of transfers of services (transferable services): 5 times for video call service, 7 times for video playback service, and 6 times for audio playback service. It is assumed that mobile phone FFF is running the video call service in the background. Since the mobile phone is the currently operated control device and is running a transferable service, it can be considered to be of the first priority; laptop computer CCC is running the video playback service in the foreground. The laptop computer is not a control device but is running a transferable service in the foreground, and can be considered to be of the second priority; mobile phone DDD is running the video playback service in the background, and large screen BBB is running the audio playback service in the background. These two devices are not control devices but are running transferable services in the background (and are not running transferable services in the foreground), and can be considered to be of the third priority. The number of transfers of the video playback service is greater than the number of transfers of the audio playback service, so mobile phone DDD can be arranged before large screen BBB; speaker EEE is not running a transferable service and can be considered to be of the fourth priority. The device identification 542 can be sorted from high to low priority (first priority, second priority, third priority, fourth priority), and for devices of the same priority, they can be sorted according to the number of turnovers of the business being carried out. The following description will be given by taking the device identification 542 shown in FIG5D as an example of sorting in this manner. Not limited to the above example, in other examples, the number of turnovers of the above-mentioned business can also be replaced by the turnover weight of the business type, and the turnover weight of the business type is the proportion of the turnover number of the business of the business type to the total turnover number, and the total turnover number can be the sum of the turnover numbers of multiple types of business (for example, all businesses) counted by the device 100.

[0150] In one embodiment, when the service performed by any device in the communication system changes, the order in which the device identification 542 is displayed may also change. In some examples, if the large screen BBB changes to running the audio playback service in the foreground, the priority level changes from the third priority level to the second priority level. At this time, the large screen BBB will be arranged before the mobile phone DDD (which belongs to the third priority level), and the number of flows of the video playback service is greater than the number of flows of the audio playback service, so the large screen BBB is still arranged after the laptop computer CCC (both belong to the second priority level). The relevant examples are similar and will not be repeated here.

[0151] It can be understood that device 100 is any device in the communication system 10. When the devices in the communication system 10 remain unchanged and the services run by the devices remain unchanged, if other devices in the communication system 10 (such as device 200 or device 400) receive a user operation for calling up free flow, the device identifier 542 in the user interface 540 shown in Figure 5D can also be displayed, that is, the free flow function provided by each device in the communication system 10 is consistent.

[0152] The user interface 540 shown in Figure 5D can be used for user triggering: business flow between any two devices (including device 100 itself) detected by device 100. In one embodiment, device 100 can receive user operation (such as touch operation) of the control of any one device in the device identification 542 shown in Figure 5D, and the user operation is used to select the device as the source device of the business flow.

[0153] In some examples, the device 100 receives a user operation on the control of the speaker EEE in the device identifier 542. In response to the user operation, the device 100 can display a prompt message, such as "The current device has no streaming services, please reselect the source device." Subsequently, the device 100 can display the user interface 540 for the user to select another device as the source device.

[0154] In other examples, the device 100 receives a user operation on the control of the watch AAA in the device identifier 542. In response to the user operation, the device 100 can display a prompt message, such as "The current device does not allow business transfer, please reselect the source device." Subsequently, the device 100 can display the user interface 540 for the user to select another device as the source device.

[0155] In other examples, device 100 receives a user operation on a control of any one of device FFF, device CCC, device DDD, and device BBB (assuming it is device DDD). In response to the user operation, device 100 can determine that device DDD is the source device for the business flow, and display the business identifier of the transferable business performed by device DDD (which may be simply referred to as the business identifier of device DDD). For specific examples, please see Figure 6A below.

[0156] As shown in FIG6A , the device 100 may display a user interface 610. The user interface 610 may include a prompt message 611 and a service identifier 612. The prompt message 611 may include the characters “Please select the service to be transferred”, indicating that the user interface 610 is an interface for selecting a target service for service transfer. The service identifier 612 may include controls for multiple transferable services performed by the device DDD, wherein any one of the controls may include a service identifier of the corresponding transferable service, such as the name and icon of the application to which the transferable service belongs. The multiple services shown in the service identifier 612 may be sorted, including, from front to back: the audio playback service of the music application, the weather card, the video playback service of the video 1 application (referred to as video playback service 1), the video playback service of the video 2 application (referred to as video playback service 2), and the user interface of the browser application (e.g., the homepage).

[0157] In one embodiment, the audio playback service and weather card of the music application are foreground services, and the video playback service 1, video playback service 2, and the user interface of the browser application are all background services. Assume that the number of service flows counted by the device 100 is, from largest to smallest, the following: video playback service, audio playback service, user interface of the browser application, and weather card. Among them, the usage time of video playback service 1 is later than the usage time of video playback service 2. The sorting method of service identifier 612 may include: foreground services are arranged before background services; for services belonging to the same service attribute (i.e., foreground services or background services), the services are sorted from largest to smallest according to the number of flows; for services belonging to the same service attribute and the same type, such as video playback service 1 and video playback service 2, which are both background services, the services are sorted from latest to earliest according to their usage time. Not limited to the above example, in other examples, the number of flows of the above services can also be replaced by flow weights. In other examples, services belonging to the same service attribute can also be sorted directly from latest to earliest according to their usage time. This application does not limit this.

[0158] In one embodiment, the device 100 can receive a user operation (e.g., a touch operation) on a control of any one of the services (assuming it is the video playback service 1) in the service identifier 612 of the user interface 610 shown in FIG6A , and in response to the user operation, determine that the service is the target service for service transfer, and display the device identifiers of candidate devices that can be used as target devices for service transfer. For a specific example, see FIG6B below.

[0159] As shown in FIG6B , device 100 may display user interface 620 . User interface 620 may include prompt information 621 and device identification 622 . Prompt information 621 may include the characters “Please select a target device,” indicating that user interface 620 is an interface for selecting a target device for service transfer. Device identification 622 may include controls for candidate devices detected by device 100 that can be used as target devices for service transfer. Any of these controls may include a device identification of the corresponding candidate device, such as an icon and a name of the candidate device. The multiple candidate devices shown in device identification 622 may be screened. For example, devices whose device capabilities support video playback service 1 may be screened from the candidate devices detected by device 100 shown in FIG5C . Assuming that the device capabilities required for the video playback service include a display, speakers, and software protocols that support video playback, device identification 622 (screened devices) may include: laptop computer CCC, large screen BBB, mobile phone FFF (i.e., device 100 / this device), excluding watch AAA (e.g., does not support the software protocol for video playback) and speaker EEE (e.g., does not include a display). The multiple candidate devices shown in the device identification 622 can be sorted, for example, sorted from small to large according to the distance from the device 100 (i.e., the control device) or the device DDD (i.e., the source device), and / or sorted according to the usage time (from late to early) / usage frequency (from large to small) of the device, etc.

[0160] In one embodiment, device 100 can receive a user operation (e.g., a touch operation) on a control of any device (assuming it is device BBB) in the device identifier 622 of the user interface 620 shown in FIG6B . In response to the user operation, the device is determined to be the target device for the service flow, and the selected source device (i.e., device DDD) and the target device (i.e., device BBB) are triggered to flow the selected target service (i.e., video playback service 1) above. That is, the video playback service 1 of device DDD is flowed to device BBB. At this time, device 500 (i.e., target device: device BBB) can display the user interface of video playback service 1, such as user interface 630 shown in FIG6C . User interface 630 may include the name 631 of the video being played (i.e., "Video A") and the video screen.

[0161] In some examples, after the business flow is successfully triggered, the device 600 (i.e., the source device: device DDD) can display a prompt message, such as displaying the user interface 640 shown in Figure 6D. The user interface 640 can be the audio playback interface of the music application, corresponding to the business identifier 612 shown in Figure 6A, indicating that the foreground business performed by the device 600 includes an audio playback business. The user interface 640 may include a prompt message 641. The prompt message 641 may include the characters "Video A of Video 1 has been transferred to BBB", indicating that the video A played by the video 1 application of this device (i.e., the above-mentioned video playback business 1) has been transferred to the device BBB. The prompt message 641 can be displayed at the top of the screen for a preset length of time and then canceled, for example, displayed in other locations such as the list in the notification bar.

[0162] In some examples, after the service flow is successfully triggered, the device 100 may display a prompt message, such as user interface 650 shown in FIG6E . User interface 650 is similar to user interface 510 shown in FIG5A , except that it also includes prompt message 651 (including the text "Free flow successful"). Prompt message 651 may be displayed at the top of the screen for a preset period of time and then be removed, such as being displayed in another location such as a list in the notification bar.

[0163] In one embodiment, at least one of device 100 (i.e., control device), device 600 (i.e., source device), and device 500 (i.e., target device) may provide a "one-key reflow" function, i.e., in response to a user operation, triggering the video playback service 1 to be transferred from the target device back to the source device (also referred to as reverse connection). At this time, device 500 may cancel the user interface 630 displaying the video playback service 1, for example, returning to the previous interface (e.g., desktop). In some examples, as shown in FIG6C , the user interface 630 displayed by device 500 also includes a prompt message 632 (including the characters "Select 'Return' for one-key reflow"). Device 500 may receive a return operation, such as a user operating the return button on a remote control connected to device 500. In response to the return operation, the currently ongoing video playback service 1 is transferred back to device 600, i.e., prompt message 632 is used to trigger one-key reflow. In some examples, as shown in FIG6D , prompt message 641 displayed by device 600 may also include the characters "Double-click for one-key reflow", which may be used to trigger one-key reflow. In some examples, as shown in FIG6E , the prompt information 651 displayed by the device 100 may also include the characters “Double-click for one-key reflow”, which may also be used to trigger one-key reflow.

[0164] Not limited to the method of calling up the business flow interface shown in Figures 5A-5D, in another embodiment, the device 100 can run application 1 in the foreground, and the user interface 1 of application 1 includes control 1, which is used to trigger business flow. The device 100 can respond to user operations on control 1 (such as touch operations), detect candidate devices for business flow, and display the user interface for business flow.

[0165] For example, application 1 is a music application, and Figures 7A-7B show schematic diagrams of another service flow interface for calling device 100. User interface 1 is user interface 710 shown in Figure 7A. For example, user interface 710 is an audio playback interface, and control 1 is control 711 in user interface 710.

[0166] As shown in Figure 7A, the device 100 can receive a user operation (such as a touch operation) on a control 711 in the user interface 710 of the music application, and in response to the user operation, display the user interface 720 shown in Figure 7B. In one embodiment, the user interface 720 can be a two-end flow user interface. At this time, the device 100 defaults to the device as the source device of the business flow, and defaults to the currently ongoing foreground business (i.e., the audio playback business of the music application) as the target business of the business flow.

[0167] As shown in FIG7B , the user interface 720 is similar to the user interface 710 shown in FIG7A , except that it further includes a window 721 , which may include a device identifier 722 , and the device identifier 722 may include controls for candidate devices detected by the device 100 that can be used as target devices for business flow (any of which controls may include the device identifier of the corresponding candidate device), as well as controls for viewing more devices. The multiple candidate devices shown in the device identifier 722 may be screened, for example, devices screened from the candidate devices detected by the device 100, whose device capabilities support the current foreground business of the device 100 (i.e., the audio playback business of the music application), such as the large screen BBB and the watch AAA. The multiple candidate devices shown in the device identifier 722 may be sorted, for example, sorted in ascending order of distance from the device 100 (i.e., the source device). Device identifier 722 allows the user to select a target device for service transfer. The icon of any candidate device shown in device identifier 722 can receive a user action. In response to the action, device 100 can determine that the candidate device is the target device for service transfer and trigger the transfer of audio playback services from device 100 to the candidate device. Viewing more device icons can trigger the display of more candidate devices detected by device 100 for the user to select a target device.

[0168] As shown in Figure 7B, the user interface 720 also includes a control 723. The device 100 can receive user operations (such as touch operations) on the control 723. In response to the user operation, a free-flow user interface is displayed for the user to select the source device, target business and target device of the business flow. For example, the user interface 540 shown in Figure 5D is displayed (for the user to select the source device of the business flow). The subsequent process is similar to the examples shown in Figures 6A-6E and will not be repeated here.

[0169] Not limited to the method of calling up the business flow interface shown in Figures 5A-5D and 7A-7B, in another embodiment, the device 100 can receive a user operation for calling up the multitasking center, and in response to the user operation, detect candidate devices for business flow, and display the user interface of the multitasking center. In this case, the user interface is also the user interface for business flow. For example, Figures 8A-8B show schematic diagrams related to another method of calling up the business flow interface of the device 100.

[0170] As shown in FIG8A , the device 100 can display a user interface 810 of the video 2 application, that is, the video playback service of the video 2 application is running in the foreground. The device 100 can receive a user operation for calling up the multitasking center, for example, the user operation is a three-finger sliding operation, and the three-finger sliding operation is, for example, an operation of sliding upward from the bottom edge of the screen. In response to the user operation, the device 100 can display a user interface 820 shown in FIG8B . In one embodiment, the user interface 820 can be a dual-end flow user interface. At this time, the device 100 defaults to the device as the source device of the service flow, and defaults to the currently ongoing foreground service (i.e., the video playback service 2 of the video 2 application) as the target service of the service flow.

[0171] As shown in FIG8B , the user interface 820 may include a device identifier 821 and a service identifier 822. The device identifier 821 may include controls for the device 100 (i.e., the current device / local device), controls for candidate devices detected by the device 100 that can be used as target devices for service transfer (any of which controls may include the device identifier of the corresponding device), and controls for viewing more devices. The service identifier 822 may include controls for the service currently being performed by the device 100 (any of which controls may include the service identifier of the corresponding service). The device 100 may perform foreground services (i.e., video playback service 2) and background services (e.g., audio call services of call applications and video playback service 1 of video 1 applications). The multiple candidate devices shown in the device identifier 821 may be screened, for example, devices that are screened from the candidate devices detected by the device 100 and whose device capabilities support the current foreground and background services of the device 100, such as large-screen BBB and laptop computer CCC. The multiple candidate devices shown in the device identifier 821 may be sorted, and the specific example is similar to the description of the device identifier 722 shown in FIG7B . The device identifier 821 can be used by the user to select the target device for the service flow, and the service identifier 822 can be used to select the target service for the service flow. In some examples, the device 100 can receive user operations on the controls of the video playback service 2 in the service identifier 822 and the controls of the device BBB in the device identifier 821. For example, the user operation is to drag the controls of the video playback service 2 to the location of the controls of the device BBB. In response to the user operation, the device BBB is determined to be the target device and the video playback service 2 is determined to be the target service, and the video playback service 2 of the device 100 is triggered to flow to the device BBB.

[0172] As shown in Figure 8B, the user interface 820 also includes a control 823. The device 100 can receive user operations (such as touch operations) on the control 823. In response to the user operation, a free-flow user interface is displayed for the user to select the source device, target business and target device of the business flow. For example, the user interface 540 shown in Figure 5D is displayed (for the user to select the source device of the business flow). The subsequent process is similar to the examples shown in Figures 6A-6E and will not be repeated here.

[0173] Not limited to the above embodiment, in another embodiment, the above-mentioned dual-end flow user interface may also be a free-flow user interface. In some examples, the user interface 530 may also be a free-flow user interface (control 537 may not be included in this case). The user interface 530 may include controls for candidate devices that can be used as source devices for business flow, and may also include controls for candidate devices that can be used as target devices for business flow, where any one of the controls may include the business identifier of the corresponding candidate device. Optionally, the controls of any two candidate devices shown in the user interface 530 may receive user operations. For example, the user may drag the control of device BBB to the location of the control of device DDD to realize the business flow of devices BBB and DDD. This application does not limit the specific user operations. The candidate devices shown in user interface 530 that can be used as source devices for business flow transfer can be sorted, and the display method of the candidate devices can be related to the sorting result. For example, the higher the priority of the candidate device, the closer the control of the candidate device is to the icon 531 of device 100. For another example, a superscript is displayed next to the control of the candidate device, and the superscript indicates the corresponding arrangement order. For another example, the candidate device shown in Figure 5C is ranked in the top N in the sorting result. Device 100 can receive a user operation (such as a double-click operation, etc.) and, in response to the user operation, display at least one device after the Nth position in the sorting result, where N is a positive integer. Without limitation, the candidate devices shown in user interface 530 that can be used as target devices for business flow transfer can also be sorted. The specific example is similar to the above example. This application does not limit the display method of the free flow user interface.

[0174] Not limited to the above-mentioned embodiment, in another embodiment, the device 100 may also display a free-flowing user interface in response to a user operation on the control 525A shown in FIG5B . In another embodiment, the device 100 may also display a free-flowing user interface in response to a user operation on the control 711 shown in FIG7A . In another embodiment, the device 100 may also display a free-flowing user interface in response to a user operation for calling up the multitasking center shown in FIG8A . The above-mentioned free-flowing user interface is, for example, the user interface 540 shown in FIG5D .

[0175] The control device (i.e., device 100) shown in the above embodiments is a device that can independently trigger business flow (i.e., a rich device). In other embodiments, the control device may also be a device that cannot independently trigger business flow (i.e., a light device). The light device can trigger business flow with the help of a connected rich device.

[0176] Next, the light device is taken as a watch (also referred to as device 700) as an example for explanation.

[0177] In one embodiment, when the device 700 is not connected to a rich device, if a user operation for triggering a business flow is received, a prompt message may be displayed to prompt the user that the business flow is currently not possible. For example, as shown in FIG9A , the device 700 is not connected to a rich device, and the device 700 may display a user interface 910. The user interface 910 may include controls for multiple functions, such as controls for setting functions, controls 911 for business flow functions, and controls for motion recording, etc. The device 700 may receive a user operation (such as a touch operation) on the control 911, and in response to the user operation, display the user interface 920 shown in FIG9B . The user interface 920 may include a prompt message "Unable to flow, please connect a rich device such as a mobile phone to assist in the flow."

[0178] In one embodiment, when device 700 is connected to a rich device (assuming it is device 500, i.e., a large-screen BBB), and a transferable service is running in the foreground of device 700, if a user operation for triggering service transfer is received, a user interface for dual-end transfer can be displayed for the user to select the target device for service transfer. At this time, device 700 can default to the device itself as the source device and the transferable service running in the foreground as the target service. For example, as shown in FIG10A , device 700 and device 500 are connected, and device 500 can display user interface 1010. For example, user interface 1010 is a desktop. User interface 1010 can include window 1011. Window 1011 can include an icon and the name "AAA" of the connected device (i.e., device 700). Device 700 can display user interface 1020. User interface 1020 can be a user interface for a video call, i.e., the foreground service is a video call service. Device 700 can receive user operations on user interface 1020, such as double-click operations, long press operations, sliding operations, etc. In response to the user operations, device 700 can request device 500 to obtain candidate devices that can be used as target devices for business transfer, and display the user interface 1030 shown in Figure 10B based on the data returned by device 500.

[0179] As shown in FIG10B , user interface 1030 may include prompt information 1031 and device identification 1032. Prompt information 1031 may include the text "Please select a target device," indicating that user interface 1030 is an interface for selecting a target device for service transfer. Device identification 1032 may be displayed by device 700 based on data returned by device 500. Device identification 1032 may include controls for candidate devices detected by device 500 that can be used as target devices for service transfer. Each control may include a device identification for the corresponding candidate device, such as an icon and name of the candidate device. The candidate devices shown in device identification 1032 may be screened, for example, devices selected from the candidate devices detected by device 500 whose device capabilities support the foreground service (i.e., video call service) of device 700, such as mobile phone FFF, large screen BBB (i.e., device 500), and laptop computer CCC. The multiple devices in device identification 1032 may be sorted, for example, in ascending order of distance from device 700 (i.e., source device). The icon of any candidate device (assuming it is mobile phone FFF) shown by device identification 1032 can receive user operations. In response to the user operation, device 700 can determine that the candidate device is the target device for the service flow and send a corresponding notification to device 500. Device 500 can determine that device 700 is the source device of the service flow, the video call service of device 700 is the target service, and mobile phone FFF is the target device, and then trigger the video call service of device 700 to be transferred to mobile phone FFF.

[0180] In one embodiment, when the video call service of device 700 is transferred to mobile phone FFF (i.e., device 100), device 100 (i.e., the target device) may display a user interface for the video call service, such as user interface 1040 shown in FIG10C. User interface 1040 may include prompt message 1041 (including the characters "AAA's video call has been transferred to this device"). The video call interface shown in user interface 1040 is consistent with user interface 1020 displayed by device 700 in FIG10A. Optionally, prompt message 1041 may be displayed at the top for a preset time and then be canceled, such as by being displayed in another location such as a list in the notification bar. In one embodiment, device 700 (i.e., the source device) may also display a prompt message, such as user interface 1050 shown in FIG10D. User interface 1050 may include the prompt message "Video call has been transferred to FFF". Optionally, the prompt message may be displayed for a preset time and then be canceled, such as by device 700 returning to the homepage. In one embodiment, device 500 (i.e., the rich device connected to device 700) may also display prompt information, such as displaying user interface 1060 shown in FIG10D. User interface 1060 is similar to user interface 1010 shown in FIG10A, except that window 1011 also includes prompt information 1061 (including characters "Video call service has been transferred to FFF"), indicating that the video call service of the connected watch AAA has been transferred to device FFF.

[0181] In one embodiment, at least one of device 700 (i.e., a light device acting as a control device and also a source device), device 500 (i.e., a rich device connected to the control device), and device 100 (i.e., a target device) may provide a "one-click reflow" function, i.e., in response to a user action, triggering the video call service to be transferred from the target device back to the source device. In this case, device 100 may cancel the user interface 1040 displaying the video call service, for example, returning to the previous interface (e.g., the desktop). In some examples, as shown in FIG10C , prompt information 1041 displayed by device 100 (i.e., the target device) also includes the text "Double-click for one-click reflow." Prompt information 1041 may receive a user action (e.g., a double-click). In response to the user action, device 100 may transfer the current video call service back to device 700, i.e., prompt information 1041 is used to trigger one-click reflow. In some examples, as shown in FIG10D , user interface 1050 displayed by device 700 (i.e., the source device and also the control device) also includes the prompt "Double-click the screen to trigger one-click reflow," which may be used to trigger one-click reflow. In some examples, as shown in FIG10D , the window 1011 displayed by the device 500 (ie, the rich device connected to the control device) further includes a control 1062 , which can also be used to trigger one-key reflow.

[0182] Not limited to the method of calling up the business flow interface shown in Figures 10A-10B, in another embodiment, when the device 700 does not run a transferable business in the foreground but runs a transferable business in the background, if a user operation for triggering business flow is received, a two-end transfer user interface (such as the user interface 1030 shown in Figure 10B) may also be displayed, and the device 700 may default the transferable business running in the background to the target business.

[0183] In one embodiment, when the device 700 is connected to a rich device (assuming it is the device 500, i.e., the large-screen BBB) and is not running a flowable service, if a user operation for triggering service flow is received, a free flow user interface can be displayed. For example, as shown in FIG11A , the device 700 and the device 500 are connected, the device 500 can display the user interface 1010 shown in FIG10A , and the device 700 can display the user interface 910 shown in FIG9A . The device 700 can receive a user operation (such as a touch operation) on the control 911 in the user interface 910. In response to the user operation, the device 700 can request the device 500 to obtain a candidate device that can be used as a source device for service flow, and display the user interface 1110 shown in FIG11B based on the data returned by the device 500.

[0184] As shown in FIG11B , user interface 1110 may include prompt information 1111 and device identification 1112. Prompt information 1111 may include the characters "Please select a source device," indicating that user interface 1110 is an interface for selecting a target device for service transfer. Device identification 1112 may be displayed by device 700 based on data returned by device 500. Device identification 1112 may include controls for candidate devices detected by device 500 as source devices for service transfer, each of which may include the device identification of the corresponding candidate device. The candidate devices shown in device identification 1112 may be sorted, including, from front to back, device BBB (i.e., device 500), device FFF, and device CCC. The rich device connected to device 700 (i.e., device BBB) may be considered to be of the highest priority. For example, if device 700 is not running a transferable service, but the rich device is running a transferable service, the sorting method for other devices can be found in the sorting method for device identification 542 shown in FIG5D , and will not be further described.

[0185] In one embodiment, when device 700 switches between connected rich devices, the order in which device identifications 1112 are displayed may change. For example, if device 700 switches from connecting to device 500 to connecting to device 100 (i.e., device FFF), in device identification 1112, device BBB (i.e., device 500) is no longer ranked first, but device FFF is ranked first. Device BBB and other devices are sorted according to device priority and service status. For an example of a specific sorting method, see the sorting method of device identification 542 shown in FIG5D. In one embodiment, when the service performed by any device in the communication system changes, the order in which device identifications 1112 are displayed may also change. For a specific example, see the description of device identification 542 shown in FIG5D.

[0186] The user interface 1110 shown in Figure 11B can be used for user triggering: business flow between any two candidate devices (including device 500 and device 700) detected by device 500 (i.e., the rich device connected to device 700). In one embodiment, device 700 can receive user operation (such as touch operation) of the control of any device in the device identification 1112 shown in Figure 11B (assuming it is device DDD not shown in Figure 11B). In response to the user operation, device 700 can determine that device DDD is the source device of the business flow and send a corresponding notification to device 500. Device 500 can return the sorted business identification of multiple transferable businesses performed by device DDD (which can be simply referred to as the business identification of device DDD) to device 700. Device 700 can display the business identification of device DDD for the user to select the target business for business flow. The specific description is similar to that of Figure 6A and will not be repeated here.

[0187] In one embodiment, the device 700 can receive a user operation (such as a touch operation) for any one of the displayed service identifiers (assuming it is the video playback service 2). In response to the user operation, the device 700 can determine that the video playback service 2 is the target service for the service flow, and send a corresponding notification to the device 500. The device 500 can return the device identifiers of multiple candidate devices that have been filtered and / or sorted and can be used as target devices for the service flow (which may be simply referred to as candidate device identifiers) to the device 700. The device 700 can display the candidate device identifier for the user to select the target device for the service flow. The specific description is similar to that of Figures 6B and 10B and will not be repeated here.

[0188] In one embodiment, device 700 may receive a user operation (e.g., a touch operation) on any one of the displayed candidate device identifiers (assuming it is device CCC), and in response to the user operation, determine that the device is the target device for the service flow, and send a corresponding notification to device 500. Device 500 may trigger the selected source device (i.e., device DDD) and target device (i.e., device CCC) to flow the selected target service (i.e., video playback service 2), i.e., video playback service 2 of device DDD is flowed to device CCC. At this time, device CCC may display a user interface for video playback service 2, the specific example of which is similar to user interface 630 shown in FIG6C .

[0189] In some examples, at least one of device 700 (i.e., a light device serving as a control device), device 500 (i.e., a rich device connected to the control device), device DDD (i.e., a source device), and device CCC (i.e., a target device) may provide a "one-click reflow" function, i.e., it may trigger the video playback service 2 to flow from the target device back to the source device in response to a user operation. At this time, device CCC may cancel the user interface displaying the video playback service 2, for example, returning to the previous interface (e.g., the desktop). The interface example displayed by device 700 is similar to user interface 1050 shown in FIG10D , the interface example displayed by device 500 is similar to user interface 1060 shown in FIG10D , the interface example displayed by device DDD is similar to user interface 640 shown in FIG6D , and the interface example displayed by device CCC is similar to user interface 630 shown in FIG6C .

[0190] In one embodiment, when a user triggers a business flow through device 700 (which may be referred to as a triggering process), if device 700 is disconnected from the connected rich device 1, device 700 may display a prompt message. When device 700 subsequently connects to rich device 2, device 700 may continue to display the business flow interface, allowing the user to continue the previous triggering process, wherein rich device 2 may be the rich device 1 previously connected to device 700, or another rich device. In some examples, when device 700 displays a user interface for selecting a target device (including a candidate device identifier, such as user interface 1030 shown in FIG. 10B ), if it is disconnected from the connected rich device 1, user interface 920 shown in FIG. 9B may be displayed to prompt the user that the current triggering process is terminated. When device 700 is subsequently connected to rich device 2, for example, in response to a user operation for triggering a business flow, device 700 may redisplay the previous user interface for selecting a target device based on the candidate device identifier previously returned by rich device 1. If, before device 700 and rich device 1 are disconnected, the source device and / or target service have already been acquired, for example, by a user selecting the source device and / or target service, or by default, the source device and / or target service can be synchronized to rich device 2. Thus, after device 700 and rich device 2 are connected, the user can continue the previous triggering process without having to reselect the source device and / or target service, ensuring that the user-triggered service flow is not interrupted by switching rich devices. Alternatively, device 700 can respond to a user operation on the device identifier of any candidate device in the user interface, determine the candidate device as the target device, and send a corresponding notification to rich device 2, which triggers the service flow between the source device and target device selected by the user. If rich device 2 cannot trigger the service flow between the source device and target device selected by the user, for example, if rich device 2 cannot communicate with the source device and / or target device, a corresponding notification can be returned to device 700, and device 700 can display a corresponding prompt message to encourage the user to re-trigger the service flow based on the device 700 connected to rich device 2.

[0191] Not limited to the above examples, in other examples, when the subsequent device 700 is connected to the rich device 2, the device 700 may also request the rich device 2 to obtain the candidate device identification, and display the user interface for selecting the target device (including the device identifications of the multiple candidate devices detected by the rich device 2) based on the data returned by the rich device 2. The user interface may be different from the user interface for selecting the target device (including the device identifications of the multiple candidate devices detected by the rich device 1) displayed when the device 700 is connected to the rich device 1.

[0192] Not limited to the above embodiment, in another embodiment, when the device 700 is connected to a rich device and is running a flowable service, if a user operation for triggering service flow is received, a free flow user interface may also be displayed, such as the user interface 1110 shown in FIG11B.

[0193] The above examples illustrate that the device / service with a higher priority in the arrangement order is displayed at an upper position. In other examples, the device / service with a higher priority in the arrangement order may be displayed further to the left. In other examples, the device / service with a higher priority in the arrangement order may be displayed in a darker color. This application does not limit the display method for representing the arrangement order.

[0194] In one embodiment, any device in the communication system 10 (using device 100 as an example) can have the service transfer function enabled or disabled by default. After enabling the service transfer function, device 100 can act as a source device or a target device for service transfer. In another embodiment, device 100 can enable or disable the service transfer function in response to user operations. A specific example is shown in FIG12 below.

[0195] FIG12 exemplarily shows a schematic diagram of a setting interface.

[0196] As shown in Figure 12, the device 100 can display a user interface 1200. The user interface 1200 may include an explanation 1201 of a function named "Multi-Device Task Center" (which may include the above-mentioned business flow function) and a switch control 1202. The explanation 1201 may include an interface example and text description (after turning on, multiple "My Devices" and bound devices are allowed to view and use each other's historical tasks, such as: accessing videos that have been played historically on a mobile phone on a tablet, and pulling them to the tablet to continue playing (also known as business flow)). The switch control 1202 can be used to turn the multi-device task center function on or off. The service flow function may include sub-functions: a two-way flow function and a free flow function. The user interface 1200 may also include a description of the two-way flow function ("allowing the triggering of service flow between the current device and the remote device") and a switch control 1203, as well as a description of the free flow function ("allowing the triggering of service flow between the current device and the remote device on any device in the network") and a switch control 1204. The switch control 1203 may be used to turn on or off the two-way flow function, and the switch control 1204 may be used to turn on or off the free flow function. For example, when the switch control 1202 in the user interface 1200 is in the on state, the switch control 1203 and the switch control 1204 may be turned on by default. The user may also independently control the turning on or off of the two-way flow function and the free flow function. When the switch control 1203 and the switch control 1204 are both in the off state, the switch control 1202 may be in the off state. When the dual-end transfer function is enabled, device 100 can act as a control device to trigger service transfers between itself and other devices. For specific examples, see Figures 5A-5C, 7A-7B, 8A-8B, and 10A-10D. Alternatively, another device can act as a control device to trigger service transfers between device 100 and the other device. In this case, the candidate devices displayed by the other device as target devices for service transfers may include device 100. When the free transfer function is enabled, any device that discovers and / or connects to device 100 can act as a control device to trigger service transfers between device 100 and other devices. The control device can be device 100 itself or the other device. For specific examples, see Figures 5A-5D, 6A-6E, and 11A-11B.

[0197] Not limited to the implementation shown in Figure 12, in another implementation, the device 100 can also determine whether to allow the device to be the source device of the business flow, or determine whether to allow the device to be the target device of the business flow in response to user operations. This application does not limit the functions that can be set.

[0198] Based on the above embodiments, the service transfer method involved in this application is introduced. The method can be applied to the communication system 10 shown in FIG1 .

[0199] Please refer to Figure 13, which is a flowchart of a service transfer method provided by an embodiment of the present application. Figure 13 is illustrated by taking the first device as the control device (rich device), the second device as the source device, and the third device as the target device as an example. The method may include but is not limited to the following steps:

[0200] S101: A first device receives a first operation.

[0201] In one embodiment, the first operation may be used to trigger business flow, that is, the first device may display a user interface for business flow in response to the first operation, for example, executing S102-S104 to display a user interface for free flow.

[0202] In some examples, the first operation may include the operation of sliding downward from the upper edge of the screen shown in Figure 5A, the user operation on control 525A shown in Figure 5B, and optionally, the user operation on control 537 shown in Figure 5C.

[0203] In some examples, the first operation may include a user operation on control 711 shown in FIG. 7A , and optionally a user operation on control 723 shown in FIG. 7B .

[0204] In some examples, the first operation may include the user operation for calling up the multitasking center shown in FIG. 8A , and optionally, the user operation for control 823 shown in FIG. 8B .

[0205] In some examples, the first operation may include a user operation on the user interface 1020 shown in Figure 10A (eg, a double-click operation, a long press operation, a sliding operation, etc.).

[0206] In some examples, the first operation may include a user operation on control 911 shown in FIG. 11A .

[0207] S102: The first device obtains device identifications and service information of multiple first candidate devices.

[0208] In one embodiment, the first device may detect a first candidate device in the communication system 10 that can be used as a source device for business flow before displaying the user interface for business flow (i.e., before S104), for example, in response to the first operation described in S101. In some examples, the first device may discover and / or connect to at least one device via wireless methods such as Bluetooth, Wi-Fi, NFC, UWB, etc., and use these devices as first candidate devices. In some examples, the first device may obtain devices located in the same local area network through signal detection, and use devices located in the same local area network as first candidate devices. In some examples, the first device may query the server for devices that have the same account as the first device, and use the queried device as the first candidate device. It is not limited to this, and the queried login account may also be a device that is an associated account with the account logged in by the first device. This application does not limit the specific method for the first device to detect the first candidate device.

[0209] In one embodiment, after the first device detects multiple first candidate devices, it can obtain the device identification and business information of each first candidate device. For specific instructions, please refer to the instructions of the device identification and business information in Figure 4. The obtained device identification and business information can be used to implement the sorting process shown in S103. In some examples, the first device can request the detected first candidate device to obtain the device identification and / or business information in response to the first operation. However, it is not limited to this, and the device identification and / or business information of the first candidate device can also be obtained from a server or other device. In some examples, the first device may have obtained the device identification and / or business information of the first candidate device before receiving the first operation. For example, the first device has established a connection with a certain device before, and the device identification of the device has been obtained and stored during the connection.

[0210] S103: The first device uses a first algorithm to sort multiple first candidate devices and obtain m device identifiers, where m is an integer not less than 1.

[0211] In one embodiment, the first device can sort multiple first candidate devices based on usage information and current business operation information, and obtain m device identifiers, which are the device identifiers of the m sorted first candidate devices. The above-mentioned current business operation information may include information about the transferable business currently being performed by each first candidate device, wherein the information of any transferable business may include, but is not limited to, business type, business attributes (such as foreground business and background business), usage time (such as the time when the user last used the business), and the above-mentioned usage information may include, but is not limited to, the number of business flows of the first candidate device (i.e., the number of times the first candidate device performs business flow as a source device) and the number of business flows. The number of business flows is the number of times the current type of business is performed as a target business. The number of business flows in the usage information may include the number of flows of the transferable business performed by the above-mentioned first candidate device. An example of the sorting process can be seen in Figure 15 below, which will not be described in detail. This application does not limit the specific content of the first algorithm.

[0212] S104: The first device displays m device identifications.

[0213] In one implementation, the first device may display the m device identifiers obtained in S103 . For specific examples, see the device identifier 542 in the user interface 540 shown in FIG. 5D and the device identifier 1112 in the user interface 1110 shown in FIG. 11B .

[0214] S105: The first device receives the second operation (for selecting the device identifier of the second device from the m device identifiers), and determines that the second device is the source device of the service transfer.

[0215] In one embodiment, the first device can receive a second operation for the device identifier of the second device among the m device identifiers described in S104, and in response to the second operation, determine that the second device is the source device of this business transfer, and obtain information about the transferable business currently being performed by the second device.

[0216] In one embodiment, the first device can obtain the business information of the transferable business currently being performed by the second device based on the business information obtained in S102. Optionally, when the business of any first candidate device detected by the first device changes, the information of the changed business can be synchronized to the first device, and the first device can "passively" obtain the information of the transferable business currently being performed by the second device (which can also be understood as the "latest" information).

[0217] In another embodiment, after receiving the second operation, the first device may "actively" obtain information about the currently transferable service from the second device. That is, after S105, the method further includes:

[0218] S106: The first device sends a first request message to the second device.

[0219] S107: The second device sends a first response message (including information about the transferable service currently being performed by the second device) to the first device.

[0220] S108: The first device uses the second algorithm to sort the multiple transferable services of the second device, and obtains p service identifiers, where p is an integer not less than 1, and p is equal to m or p is not equal to m.

[0221] In one embodiment, the first device can sort the multiple transferable services currently being performed by the second device according to the usage time of the services, and obtain p service identifiers, which are the service identifiers of the p transferable services currently being performed by the second device after sorting.

[0222] In one embodiment, the later the service is used, the higher the priority in the arrangement order.

[0223] In another embodiment, the first device can sort the multiple transferable services currently being performed by the second device according to the service attributes (such as foreground services and background services) and the usage time of the services, wherein the foreground services are arranged before the background services. For services with the same service attributes, the later the service usage time, the higher the priority of the arrangement order.

[0224] In another embodiment, the first device can sort the multiple transferable services currently being performed by the second device according to the service attributes, the flow weight of the service type and the usage time of the service, wherein the foreground service is arranged before the background service. For services with the same service attributes (e.g., multiple background services), the greater the flow weight of the service type to which the service belongs, the higher the priority in the arrangement. For services with the same service attributes and the same service type, the later the service is used, the higher the priority in the arrangement. The flow weight of the above-mentioned service type is the ratio of the flow times of the service of the service type to the total flow times, and the total flow times is the sum of the flow times of multiple types of services (e.g., all services) counted by the first device. Not limited to the above-mentioned embodiment, in another embodiment, the flow weight of the service type can also be replaced by the flow times of the service type. This application does not limit the specific content of the second algorithm.

[0225] S109: The first device displays p service identifiers.

[0226] In one implementation, the first device may display the p service identifiers obtained in S108 . For a specific example, see the service identifier 612 in the user interface 610 shown in FIG. 6A .

[0227] S110: The first device receives a third operation (for selecting a service identifier of a first service from among p service identifiers), and determines that the first service is a target service for service transfer.

[0228] In one implementation, the first device may receive a third operation on the service identifier of the first service among the p service identifiers in S109 , and determine, in response to the third operation, that the first service is the target service of this service transfer.

[0229] S111: The first device obtains multiple second candidate devices related to the first service, sorts the multiple second candidate devices using a third algorithm, and obtains n device identifiers, where n is an integer not less than 1, and n is equal to m or n is not equal to m.

[0230] In one embodiment, after the first device determines that the first business is the target business of this business transfer, it can filter out multiple second candidate devices related to the first business from the multiple devices detected by the first device. The description of the first device detecting multiple devices is similar to the description of the first device detecting the first candidate device in S102, and will not be repeated. The second candidate device can be a device whose device capabilities (which may include hardware capabilities and software capabilities) support the first business.

[0231] In one embodiment, the first device can sort multiple second candidate devices according to at least one of the device usage time (for example, the time of the last use of the device), the device usage frequency (for example, the number of times the device is used within a preset time period), and the device location (for example, the distance between the device and the source device, or the distance between the device and the control device), and obtain n device identifiers. These n device identifiers are the device identifiers of the sorted n second candidate devices. Optionally, the longer the device usage time, the higher the priority of the arrangement order. Optionally, the greater the device usage frequency, the higher the priority of the arrangement order. Optionally, the smaller the distance from the source device, the higher the priority of the arrangement order. Optionally, the smaller the distance from the control device, the higher the priority of the arrangement order. This application does not limit the specific content of the third algorithm.

[0232] S112: The first device displays n device identifications.

[0233] In one implementation, the first device may display the n device identifications obtained in S111 . For a specific example, see the device identification 622 in the user interface 620 shown in FIG. 6B .

[0234] S113: The first device receives the fourth operation (for selecting the device identifier of the third device from the n device identifiers), and determines that the third device is the target device for the service transfer.

[0235] In one embodiment, the first device may receive a fourth operation for the device identifier of the third device among the n device identifiers described in S112, and in response to the fourth operation, determine that the third device is the target device for the current service transfer. Optionally, the first device may subsequently trigger the transfer of the target service (i.e., the first service) between the source device (i.e., the second device) and the target device (i.e., the third device) determined above, such as the process shown in S114-S117 below.

[0236] S114: The first device sends a second request message to the second device.

[0237] S115: The second device sends a second response message (including execution information of the first service) to the first device.

[0238] In one embodiment, the second request message may include a service identifier of the first service, and the second device may determine the first service based on the second request message, and obtain the execution information of the first service to send to the first device. The execution information of the first service may be used by the device to perform the first service. In some examples, the first service is a video playback service, and the execution information of the first service may include the playback address of the video in the video playback service, so that other devices can perform the video playback service according to the playback address. In other examples, the first service is an audio playback service, and the execution information of the first service may be an audio file in the audio playback service, so that other devices can directly play the audio in the file to perform the audio playback service. This application does not limit the specific content of the execution information of the service.

[0239] S116: The first device sends a first indication message (including execution information of the first service) to the third device.

[0240] In one implementation, the first indication message may be used to instruct the third device to perform the first service.

[0241] S117: The third device displays the interface of the first service according to the first instruction message.

[0242] In one embodiment, the third device may respond to the instruction of the first indication message and perform the first service according to the execution information of the first service in the first indication message. At this time, the user interface of the first service may be displayed. For specific examples, see Figures 6C and 10C.

[0243] In one embodiment, after the second device and the third device successfully implement service transfer, the second device or the third device sends a corresponding notification to the first device.

[0244] Not limited to the process shown in FIG13 , in other embodiments, S114-S117 may also be replaced by the first device sending a second indication message to the second device, the second indication message may include the service identifier of the first service and the device identifier of the third device, the second indication message may be used to instruct the second device to transfer the first service to the third device, after the second device receives the second indication message, it may send a third indication message to the third device, the third indication message may be used to instruct the third device to perform the first service, the third indication message may include the execution information of the first service, and the third device may perform the first service according to the third indication message. In other words, it is not limited to the first device as a "transfer device" as shown in FIG13 forwarding the execution information of the first service from the second device (source device) to the third device (target device), but it may also be that the first device notifies the second device to perform the service transfer and the second and third devices independently perform data exchange for the service transfer. It is not limited to the above-mentioned first device notifying the second device (source device) to perform the service transfer. In other embodiments, the first device may also notify the third device (target device) to perform the service transfer, and the third device may independently request the execution information of the first service from the second device. This application is not limited to this.

[0245] FIG13 illustrates an example in which the control device (first device) and the source device (second device) are different. In other embodiments, the control device and the source device may be the same. In some examples, the control device is the source device by default under certain circumstances. Specific examples can be found in FIG5A-FIG5C, FIG7A-FIG7B, and FIG8A-FIG8B. In other examples, the source device selected by the user is the control device. For example, in the embodiment shown in FIG5C, device 100 receives a user operation on a control for device FFF in device identifier 542. When the control device and the source device are the same, the control device (first device) can directly obtain information about the transferable services it performs and the execution information of the target services without being notified by other devices. For example, steps S106-S107 and S114-S115 are not executed.

[0246] FIG13 illustrates an example in which the control device (first device) and the target device (third device) are different. In other embodiments, the control device and the target device may be the same. In some examples, the control device is the target device by default in certain circumstances. In other examples, the target device selected by the user is the control device. For example, in the embodiment shown in FIG6B , device 100 receives a user operation on a control for device FFF in device identifier 622. If the control device and the target device are the same, after S115 , the first device may directly perform the first service based on the second response message without executing S116-S117.

[0247] In the method shown in Figure 13, the first device can be any device in the communication system 10, and the second device and the third device can also be any two devices in the communication system 10. That is to say, in a distributed scenario, the user can operate any device to trigger the business flow of any two devices, rather than being limited to triggering the business flow of the two through the source device or the target device (that is, the above-mentioned two-end flow), or being limited to triggering the business flow through a fixed controller, which effectively reduces the limitations of the business flow function and greatly facilitates user use.

[0248] In the business flow method shown in Figure 13, the first device serving as the control device may be a rich device, which may independently receive user operations and trigger business flow between the second device and the third device in response to the user operations. In other embodiments, the control device may also be a light device, which may receive user operations and trigger business flow between the source device and the target device with the help of a connected rich device in response to the user operations. For details, please refer to Figure 14 below.

[0249] Please refer to Figure 14, which is a flowchart of a service transfer method provided by an embodiment of the present application. Figure 14 uses the first device as a control device (light device), the fourth device as a rich device connected to the control device, the second device as a source device, and the third device as a target device as an example for explanation. The method may include but is not limited to the following steps:

[0250] S201: The first device receives a fifth operation.

[0251] In one embodiment, the fifth operation can be used to trigger a service flow. That is, the first device can display a user interface for service flow in response to the fifth operation, for example, executing S202-S207 to display a user interface for free flow. An example of the fifth operation can be found in the example of the first operation in S101 of Figure 13.

[0252] S202: The first device sends a registration message to the fourth device.

[0253] In one embodiment, the registration message may include, but is not limited to, the device identification and security information of the first device. The security information may be, for example, but not limited to, information that can identify the identity of the first device or the user of the first device, such as an access password, a user face, a user fingerprint, etc. The fourth device may verify whether the identity of the first device is legal based on the registration message. It can also be said that the registration message is the input for the fourth device to verify whether the identity of the first device is legal. When the verification result is legal, the fourth device may determine that the first device is successfully registered, and the first device may subsequently trigger a business flow with the help of the fourth device. For example, the fourth device triggers the transfer of the first business of the second device to the third device (such as executing S220) based on the fourth indication message described in S219. When the verification result is illegal, the fourth device may determine that the first device is a registered device, and the first device may subsequently be unable to trigger a business flow with the help of the fourth device.

[0254] The order of S201 and S202 is not limited.

[0255] S203: The first device sends a third request message to the fourth device.

[0256] In one implementation, the third request message may be used to request to obtain a device identifier of a candidate device that can be used as a source device for service transfer.

[0257] S204: The fourth device obtains device identifications and service information of multiple third candidate devices.

[0258] In one embodiment, after receiving the third request message sent by the first device, the fourth device can determine whether the first device is a successfully registered device. If the judgment result is yes, the fourth device can obtain the device identification of the source device that can be used as the business flow, for example, executing S204-S205. If the judgment result is no, the fourth device may not obtain the device identification of the source device that can be used as the business flow, for example, sending a corresponding notification to the first device.

[0259] In one embodiment, after receiving the third request message sent by the first device, the fourth device can detect the third candidate device in the communication system 10 that can serve as the source device for business flow, and obtain the device identification and business information of each third candidate device. For details, please refer to the description of the first device detecting the first candidate device and the first device obtaining the device identification and business information of the first candidate device in S102 of Figure 13.

[0260] S205: The fourth device uses the first algorithm to sort the multiple third candidate devices and obtain f device identifiers, where f is an integer not less than 1.

[0261] S205 is similar to S103 in FIG. 13 , and for details, please refer to the description of S103 in FIG. 13 .

[0262] S206: The fourth device sends information of f device identifications to the first device, wherein the information of f device identifications is used to represent the f device identifications. This application does not limit the specific content and form.

[0263] S207: The first device displays f device identifications.

[0264] In one implementation, the first device may display f device identifications based on the information of the f device identifications sent by the fourth device. The specific example is consistent with the example of m device identifications in S104 of FIG. 13 .

[0265] S208: The first device receives the sixth operation (used to select the device identification of the second device from the f device identifications), and determines that the second device is the source device of the service transfer.

[0266] In one embodiment, the first device can receive a sixth operation for the device identifier of the second device among the f device identifiers described in S207, and in response to the sixth operation, determine that the second device is the source device of this business transfer, and obtain information about the transferable business currently being performed by the second device, such as executing S209.

[0267] S209: The first device sends a fourth request message to the fourth device.

[0268] In one implementation, the fourth request message may be used to request acquisition of a service identifier of a target service that can be used as a service transfer, and the fourth request message may include a device identifier of the second device.

[0269] S210: The fourth device uses the second algorithm to sort the multiple transferable services of the second device and obtain j service identifiers, where j is an integer not less than 1, and j is equal to f or j is not equal to f.

[0270] In one embodiment, after receiving the fourth request message sent by the first device, the fourth device can determine whether the first device is a successfully registered device. If the judgment result is yes, the fourth device can obtain information about the transferable services currently being performed by the second device, such as executing S210. If the judgment result is no, the fourth device may not obtain information about the transferable services currently being performed by the second device, such as sending a corresponding notification to the first device.

[0271] In one embodiment, after receiving the fourth request message sent by the first device, the fourth device can obtain information about the transferable services currently being performed by the second device. The specific description is similar to the description of the first device obtaining information about the transferable services currently being performed by the second device in S105 of Figure 13 and will not be repeated here. The fourth device can then use the second algorithm to sort the multiple transferable services obtained. The specific description is similar to the description of S108 of Figure 13 and will not be repeated here.

[0272] S211: The fourth device sends information of j service identifiers to the first device, where the information of j service identifiers is used to represent the j service identifiers. This application does not limit the specific content and form.

[0273] S212: The first device displays j service identifiers.

[0274] In one implementation, the first device may display j service identifiers based on information about the j service identifiers sent by the fourth device. For a specific example, see the service identifier 612 in the user interface 610 shown in FIG. 6A .

[0275] S213: The first device receives the seventh operation (for selecting the service identifier of the first service from the j service identifiers), and determines that the first service is the target service for the service transfer.

[0276] In one implementation, the first device may receive a seventh operation for the service identifier of the first service among the j service identifiers in S212, and determine, in response to the seventh operation, that the first service is the target service of this service transfer.

[0277] S214: The first device sends a fifth request message to the fourth device.

[0278] In one implementation, the fifth request message may be used to request to obtain a device identifier of a candidate device that can be used as a target device for service transfer, and the fifth request message may include a service identifier of the first service.

[0279] S215: The fourth device obtains multiple fourth candidate devices related to the first service, sorts the multiple fourth candidate devices using the third algorithm, and obtains t device identifiers, where t is an integer not less than 1, where t is equal to f or t is not equal to f.

[0280] In one embodiment, after receiving the fifth request message sent by the first device, the fourth device can determine whether the first device is a successfully registered device. If the judgment result is yes, the fourth device can obtain multiple fourth candidate devices related to the first business, for example, execute S215. If the judgment result is no, the fourth device may not obtain multiple fourth candidate devices related to the first business, for example, send a corresponding notification to the first device.

[0281] In one embodiment, the fourth device can determine that the first business is the target business of this business transfer based on the fifth request message, and then filter out multiple fourth candidate devices related to the first business from the multiple devices detected by the fourth device. The description of the fourth device detecting multiple devices is similar to the description of the first device detecting the first candidate device in S102 of Figure 13, and will not be repeated here. The fourth candidate device can be a device whose device capabilities (including hardware capabilities and software capabilities) support the first business. Then, the fourth device can use the third algorithm to sort the multiple fourth candidate devices obtained. The specific description is similar to the description of the first device sorting multiple second candidate devices in S111 of Figure 13, and will not be repeated here.

[0282] S216: The fourth device sends information of t device identifications to the first device, where the information of t device identifications is used to represent the t device identifications. This application does not limit the specific content and form.

[0283] S217: The first device displays t device identifications.

[0284] In one implementation, the first device may display t device identifications based on the information of the t device identifications sent by the fourth device. For a specific example, see the device identification 622 in the user interface 620 shown in FIG. 6B .

[0285] S218: The first device receives the eighth operation (for selecting the device identifier of the third device from the t device identifiers), and determines that the third device is the target device for the service transfer.

[0286] In one implementation, the first device may receive an eighth operation on the device identifier of the third device among the t device identifiers described in S217, and determine, in response to the eighth operation, that the third device is the target device for this service transfer.

[0287] S219: The first device sends a fourth indication message to the fourth device.

[0288] In one implementation, the fourth indication message may be used to instruct the fourth device to trigger service transfer: the first service of the second device is transferred to the third device, and the fourth indication message may include the device identifier of the third device.

[0289] S220: The fourth device sends a fifth indication message to the second device.

[0290] In one implementation, the fifth indication message may include a service identifier of the first service and a device identifier of the third device. The fifth indication message may be used to instruct the second device to transfer the first service to the third device.

[0291] S221: The second device sends a sixth indication message (including execution information of the first service) to the third device.

[0292] In one implementation, the sixth indication message may be used to instruct the third device to perform the first service.

[0293] S222: The third device displays the interface of the first service according to the sixth instruction message.

[0294] In one embodiment, the third device may respond to the instruction of the sixth indication message and perform the first business according to the execution information of the first business in the sixth indication message. At this time, the user interface of the first business may be displayed. For specific examples, see Figures 6C and 10C.

[0295] In one embodiment, after the second device and the third device successfully implement service transfer, the second device or the third device sends a corresponding notification to the fourth device, and the fourth device may also send a corresponding notification to the first device.

[0296] Not limited to the process shown in Figure 14, in other embodiments, S220-S221 can also be replaced by the fourth device requesting the second device to obtain the execution information of the first business, and the fourth device can send the obtained execution information of the first business to the third device to enable the third device to execute S222. The specific instructions are similar to S114-S116 in Figure 13 and will not be repeated here.

[0297] In one embodiment, in the process shown in FIG14 , if the first device switches the connected rich device, for example, switching from connecting to the fourth device to connecting to the fifth device, the first device and / or the fourth device may send information about the service transfer to the fifth device, so that the first device can continue the triggering process previously implemented with the help of the fourth device with the help of the fifth device. In some examples, before S222 , for example, after S207 and before S208 , the rich device switched by the first device is the fifth device, and the first device or the fourth device may send information about f device identifiers to the fifth device. Optionally, the fourth device may send information obtained in S204 to the fifth device. According to the information obtained, after the first device and the fifth device are connected, the first device can continue to execute S207 and subsequent processes. At this time, the fourth device needs to be replaced by the fifth device. In other examples, after S222, the first device, the second device, the third device and the fourth device can provide the "one-key reflow" function. If the rich device switched to be connected by the first device is the fifth device, the first device or the fourth device can send information of the second device and / or the third device to the fifth device, so that the fifth device can replace the fourth device to provide the "one-key reflow" function, that is, the first device, the second device, the third device and the fifth device can provide the "one-key reflow" function.

[0298] FIG14 illustrates an example in which the control device (first device) and the source device (second device) are different. In other embodiments, the control device and the source device may be the same. For specific explanations, please refer to the explanation in FIG14 in which the control device and the source device are the same.

[0299] FIG14 illustrates an example in which the control device (first device) and the target device (third device) are different. In other embodiments, the control device and the target device may be the same. For specific instructions, please refer to the description in FIG13 in which the control device and the target device are the same.

[0300] Figure 14 is used as an example to illustrate that the rich device (fourth device) assisting the control device and the source device (second device) are different. In other embodiments, the rich device and the source device may also be the same. For specific instructions, please refer to the description of the same control device and source device in Figure 14.

[0301] Figure 14 uses the example of the rich device (fourth device) assisting in controlling the device and the target device (third device) being different. In other embodiments, the rich device and the target device may also be the same. For specific instructions, please refer to the description of the control device and the target device being the same in Figure 13.

[0302] In the method shown in Figure 14, the light device (i.e., the first device) serving as a control device can receive user operations, and in response to user operations, request and receive feedback from the connected rich device and display the corresponding feedback results, and trigger the business flow of the source device and the target device through the rich device, thereby enabling the lightweight device to trigger the business flow function in a distributed scenario. In other words, the method shown in Figure 14 solves the problem that light devices cannot serve as control devices due to weak or missing system capabilities, greatly expands the range of control devices that users can operate in distributed scenarios, reduces the limitations of business flow functions, and improves user experience.

[0303] Please refer to Figure 15, which is a flow chart of a sorting process based on a first algorithm provided in an embodiment of the present application. The process can be applied to the first device shown in Figure 13 (a rich device as a control device), for example, the implementation process of S103. The method can also be applied to the fourth device shown in Figure 14 (a rich device that assists in controlling the device), for example, the implementation process of S205. For the sake of convenience, the process is described as being applied to the first device. The sorting process may include but is not limited to the following steps:

[0304] S301: The first device obtains devices other than the transfer-denying device from a plurality of candidate devices (a first candidate set).

[0305] In one embodiment, the first device can filter out devices other than the flow-denied device from multiple detected candidate devices (i.e., candidate devices that can be used as source devices for business flow). The filtered devices can be collectively referred to as a first candidate set, wherein the flow-denied device can be set to not be used as a source device for free flow (also referred to as a device that has not enabled the business flow function). For specific setting examples, see Figure 12, for example, switch control 1202, switch control 1203, or switch control 1204 is in the off state. The first candidate set can be used in a subsequent sorting process, which can be understood as setting the flow-denied device to be the last device in the sorting process, such as the watch AAA in the device identification 542 shown in Figure 5D. The watch AAA is displayed last in the device identification 542 and is displayed differently from other devices.

[0306] In one implementation, the first device may first sort the devices other than the flow-denying device among the multiple candidate devices based on the number of service flows of the devices, and the sorted multiple devices are the first candidate set.

[0307] S302: The first device divides the devices in the first candidate set according to preset device priorities, and obtains at least one second candidate set.

[0308] In one embodiment, the first algorithm may be preset with device priorities, for example, but not limited to, the candidate devices are divided into the following four device priorities (described in descending order according to the order of service operation):

[0309] First priority: Control devices running services that can be transferred (also known as "handheld devices" operated by users) are classified as first priority. This can also be understood as meaning that if there is no control device running services that can be transferred, there is no device with first priority.

[0310] The second priority is for devices that run transferable services in the foreground (the transferable services may be run in the background or not in the background).

[0311] The third priority level is a device that runs a transferable service in the background and does not run a transferable service in the foreground.

[0312] The fourth priority level is for devices that are not running any transferable services.

[0313] The device priority is not limited to the above examples. In other examples, the above-mentioned first priority division method can be applied to the case where the control device is a rich device. When the control device is a light device, the first priority device can be divided according to the situation. For example, if the control device runs a transferable service, the control device can be divided into the first priority. If the control device does not run a transferable service, it is determined whether the rich device connected to the control device runs a transferable service. When the rich device runs a transferable service, the rich device can be divided into the first priority device. When the rich device does not run a transferable service, there may be no first priority device. This application does not limit the specific content of the device priority.

[0314] In one embodiment, the first device may divide the devices in the first candidate set according to the four priorities in the above example, and obtain second candidate sets corresponding to the four priorities. Devices divided into the same priority may be said to belong to the same second candidate set.

[0315] In some examples, the first candidate set includes: a first device (i.e., a control device) running a transferable service, a sixth device and a seventh device running the transferable service in the foreground, an eighth device and a ninth device running the transferable service in the background, and a tenth device and an eleventh device not running the transferable service. Therefore, the first device can obtain four second candidate sets, among which the second candidate set corresponding to the first priority includes the first device, the second candidate set corresponding to the second priority includes the sixth device and the seventh device, the second candidate set corresponding to the third priority includes the eighth device and the ninth device, and the second candidate set corresponding to the fourth priority includes the tenth device and the eleventh device.

[0316] It can be understood that for any priority, if there is no device classified as this priority, the second candidate set corresponding to this priority is empty. For example, in the first candidate set of the above example, the first device does not run the transferable service, then the second candidate set corresponding to the first priority is empty.

[0317] S303: The first device obtains the number of service transactions of the device.

[0318] In one embodiment, the first device can obtain the business flow times of the devices in the second candidate set after determining the second candidate set corresponding to the fourth priority (i.e., after S302). In another embodiment, S303 is executed before S302, and the first device can obtain the business flow times of multiple detected candidate devices. For example, when any device in the communication system 10 performs business flow as a source device, the first device can update the stored business flow times of the device.

[0319] S304: The first device sorts the second candidate set corresponding to the fourth priority according to the number of service transfers of the device.

[0320] In one implementation, for multiple devices in the second candidate set corresponding to the fourth priority, the first device may sort them according to the number of service transactions of the devices. A greater number of service transactions leads to a higher priority in the arrangement order.

[0321] It is understandable that if the first candidate set is sorted according to the number of service transactions of the device, S304 may not be executed, that is, the second candidate set corresponding to the fourth priority is itself sorted according to the number of service transactions of the device.

[0322] S305: The first device obtains the number of service transfers.

[0323] In one embodiment, the first device can obtain the number of transfers of the transferable services performed by the devices in the second candidate set after determining the second candidate set (i.e., after S302). In another embodiment, S305 is executed before S302, and the first device can obtain the number of transfers of the transferable services of any candidate device. For example, when the service of any device in the communication system 10 is transferred, the first device can update the stored number of transfers of the service.

[0324] S306: The first device sorts each second candidate set except the second candidate set corresponding to the fourth priority according to the number of service transfers.

[0325] In one embodiment, for multiple devices included in any one of the second candidate set corresponding to the first priority, the second candidate set corresponding to the second priority, and the second candidate set corresponding to the third priority, the first device may sort them according to the number of times the transferable services are performed by these devices. A specific example is as follows:

[0326] In some examples, the first device can first obtain the flow weight of the transferable service performed by the device, that is, the proportion of the flow times of the service of this service type to the total flow times, and assign different weights to the foreground service and the background service (which can be simply referred to as the service attribute weight). The first device can score the device based on the flow weight of the transferable service performed by the device and the service attribute weight. The device with a higher score has a higher priority in the sorting order. For example, the second candidate set corresponding to the second priority includes device 3 and device 4. Device 3 runs a transferable video service in the foreground and a transferable audio service in the background. Device 4 runs a transferable audio service in the foreground and a transferable video service in the background. Assuming that the flow weights of the audio service and the video service are a and b respectively, and the service attribute weights of the foreground service and the background service are c and d respectively (c is greater than d), therefore, the score of device 3 is S1 = b*c + a*d, and the score of device 4 is S2 = a*c + b*d. S1 is greater than S2, so device 3 is ranked before device 4.

[0327] In other examples, the second candidate set includes devices that all run transferable services with the same service attributes. For example, the second candidate set corresponding to the third priority level only includes devices that run transferable services in the background. The first devices can be directly sorted according to the transfer weight of the transferable services performed by the devices. The device with a larger service transfer weight is ranked higher. Without limitation, the devices can also be directly sorted according to the number of transfers of the transferable services performed by the devices. The device with a larger service transfer weight is ranked higher.

[0328] In one embodiment, for any one of the second candidate set corresponding to the first priority, the second candidate set corresponding to the second priority, and the second candidate set corresponding to the third priority, if it includes two devices: the arrangement order of these two devices obtained according to the above-mentioned sorting method (based on the number of business transactions) is consistent, then the two devices can be sorted according to the number of business transactions of the devices, and the device with a larger number of business transactions has a higher priority in the arrangement order. It can be understood that if the first candidate set is sorted according to the number of business transactions of the devices, then the two devices are directly sorted according to the number of business transactions of the devices. It can be understood that when sorting any of the above-mentioned second candidate sets, the sorting method based on the number of business transactions is used first, and the sorting method based on the number of business transactions of the devices is used secondly.

[0329] It can be understood that when any second candidate set includes only one device or is empty, for example, the second candidate set corresponding to the first priority includes only one device, the second candidate set may not be sorted.

[0330] The order of S304 and S305 is not limited.

[0331] In some examples, FIG15 illustrates the implementation process of S103 of FIG13 , and the m device identifiers described in S103 are the device identifiers of the candidate devices in the sorted second candidate set described in FIG15 .

[0332] In the method shown in Figure 15, the device priority set based on the business operation status of the candidate device, as well as the user's usage information such as the number of business flows of the device and the number of business flows, can be combined to sort the candidate devices that can be used as source devices for business flow. The sorted candidate devices can be provided to the user for viewing, and intelligent recommendations that suit the user's wishes are provided based on the user's actual experience. In this way, the user no longer needs to check one by one from a large number of devices in a distributed scenario to select the required source device, which reduces the time and energy spent by the user on selecting the source device, further facilitates the user's use, and improves the user experience.

[0333] The above embodiments are explained by taking the user performing trigger operations and other user operations on the control device as an example. In other embodiments, the user may not manually operate any device, but trigger the business flow through voice interaction in a distributed scenario. For example, the living room includes multiple devices. When the user is in the living room, he can issue a voice "business flow" (the voice will not indicate which device responds, for example, the voice does not include the wake-up word for a specific device). The main device among these multiple devices can respond to the user's voice input so that the user can trigger the business flow through the main device. The specific implementation is similar to that of the above embodiments. At this time, the control device in the above embodiments can be replaced by the main device. Among them, the main device can be, but is not limited to, the device closest to the user, the device with the strongest system capabilities, or the device with the highest frequency of use. The above multiple devices can determine the main device according to preset rules or by interacting with each other. This application does not limit the specific method of determining the main device.

[0334] The methods provided in the various embodiments of this application may be implemented in whole or in part through software, hardware, firmware, or any combination thereof. When implemented using software, they may be implemented in whole or in part in the form of a program product. The program product includes one or more instructions. When the program instructions are loaded and executed on a device, the processes or functions described in the embodiments of this application are generated in whole or in part.

[0335] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A business flow method, characterized in that: Applied to a first device, where the first device is any device in a communication system, the method includes: receiving a first operation; Displaying a first interface, where the first interface includes options for m second devices in the communication system, where m is an integer not less than 1; receiving a second operation of an option for an i-th second device among the m second devices, where i is an integer not less than 1 and not greater than m; In response to the second operation, determining that the i-th second device is a source device for service transfer; Displaying a second interface, where the second interface includes options for n third devices in the communication system, where n is an integer not less than 1; receiving a third operation of an option for a j-th third device among the n third devices, where j is an integer not less than 1 and not greater than n; In response to the third operation, the j-th third device is determined to be the target device for the service transfer, and the i-th second device is triggered to transfer the first service to the j-th third device.

2. The method according to claim 1, characterized in that The first interface includes the sorted options of the m second devices, and before displaying the first interface, the method further includes: sorting the m second devices based on a first algorithm; or, Sending a first request message to a connected fourth device; receiving a first response message sent by the fourth device, wherein the first response message includes information of the m second devices sorted by the fourth device based on the first algorithm; The first algorithm is related to at least one of the following parameters: the service operation status of the device, the number of times the device performs service flow as a source device, the number of times the service flow of the device is operated, and whether the service flow function of the device is enabled.

3. The method according to claim 2, characterized in that The m second devices include a kth second device and a tth second device, the kth second device is displayed before the tth second device, k is an integer not less than 1 and not greater than m, and t is an integer not less than 1 and not greater than m, wherein, The kth second device is the first device, the tth second device is not the first device, and the first device runs a transferable service; or, The kth second device is the fourth device, the tth second device is not the fourth device, and the first device does not run the transferable service; or, The kth second device runs a transferable service in the foreground, the tth second device runs a transferable service in the background, or the tth second device does not run a transferable service; or, The kth second device runs a transferable service in the background, and the tth second device does not run a transferable service; or, The kth second device and the tth second device respectively run the second service and the third service that can be transferred in the foreground, and the number of transfers of the second service is greater than the number of transfers of the third service; or, The kth second device and the tth second device respectively run a second service and a third service that can be transferred in the background, and the number of transfers of the second service is greater than the number of transfers of the third service; or, The kth second device and the tth second device are not running transferable services, and the number of times the kth second device performs service transfer as a source device is greater than the number of times the tth second device performs service transfer as a source device; or, The kth second device is a device with a service transfer function enabled, and the tth second device is a device with a service transfer function not enabled.

4. The method according to any one of claims 1 to 3, characterized in that: The second interface includes the sorted options of the n third devices, and before displaying the second interface, the method further includes: screening out the n third devices from the communication system according to the information of the first service, and sorting the n third devices based on a second algorithm; or, Sending a second request message to a connected fourth device; receiving a second response message sent by the fourth device, wherein the second response message includes information of the n third devices sorted by the fourth device based on a second algorithm; The second algorithm is related to at least one of the following parameters: the location of the device, the number of times the device is used, and the frequency of use of the device.

5. The method according to claim 4, characterized in that The n third devices are devices in the communication system whose device capabilities support performing the first service.

6. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: In response to the second operation, displaying a third interface, the third interface including options of p transferable services run by the i-th second device, where p is an integer not less than 1; receiving a fourth operation for an option of the first service among the p transferable services; The displaying of the second interface includes: In response to the fourth operation, the second interface is displayed, and the n third devices are related to the first service.

7. The method according to claim 6, characterized in that The third interface includes the sorted options of the p transferable services. Before displaying the third interface, the method further includes: Sort the p transferable services based on a third algorithm; or, Sending a third request message to a connected fourth device; receiving a third response message sent by the fourth device, wherein the third response message includes the p transferable services sorted by the fourth device based on the third algorithm; The third algorithm is related to at least one of the following parameters: whether the service is running in the foreground, the time when the service was last used, and the number of times the service was transferred.

8. The method according to any one of claims 1 to 5, characterized in that: The first service is determined according to a preset rule.

9. The method according to any one of claims 1 to 8, characterized in that The triggering the i-th second device to transfer the first service flow to the j-th third device includes: sending a fourth request message to the i-th second device; receiving a fourth response message sent by the i-th second device, wherein the fourth response message includes information about the first service; sending a first indication message to the j-th third device, wherein the first indication message includes information about the first service, and the first indication message is used to instruct the j-th third device to display a user interface of the first service; or, A second indication message is sent to the i-th second device, wherein the second indication message is used by the i-th second device to send a third indication message to the j-th third device, wherein the third indication message includes information of the first service, and the third indication message is used to instruct the j-th third device to display the user interface of the first service.

10. The method according to any one of claims 1 to 8, characterized in that The triggering the i-th second device to transfer the first service flow to the j-th third device includes: A fourth indication message is sent to a connected fourth device, where the fourth indication message is used to instruct the fourth device to trigger the i-th second device to transfer the first service flow to the j-th third device.

11. The method according to claim 10, characterized in that The first device is a device that does not have the first system capability, and the fourth device is a device that has the first system capability.

12. The method according to claim 10 or 11, characterized in that The method further comprises: A registration message is sent to the fourth device, where the registration message is the input for the fourth device to verify whether the identity of the first device is legal. When the fourth device determines that the identity of the first device is legal, the fourth device triggers the i-th second device to transfer the first service flow to the j-th third device according to the fourth indication message.

13. The method according to any one of claims 10 to 12, characterized in that: The receiving first operation includes: When connected to the fourth device, the first operation is received, and the first interface is displayed according to the information of the m second devices sent by the fourth device; Before receiving the first operation, the method further includes: When connected to a fifth device, receiving a fifth operation; Displaying a fourth interface, wherein the fourth interface is the same as the first interface; When the connection with the fifth device is disconnected, the fourth interface is canceled.

14. The method according to any one of claims 10 to 13, characterized in that: The receiving first operation includes: When connected to the fourth device, the first operation is received, and the first interface is based on the m second The information of the device is displayed; Before receiving the first operation, the method further includes: When not connected to the fourth device, a sixth operation is received, and the sixth operation is the same as the first operation; a fifth interface is displayed, and the fifth interface includes prompt information of business flow failure.

15. The method according to any one of claims 1 to 14, characterized in that: The receiving first operation includes: Receiving a first operation on a control of a hyperterminal in a control center interface; or, When displaying the sixth interface of the first application, receiving the first operation on the flow control in the sixth interface; or, The first operation for invoking the multitasking center is received.

16. The method according to any one of claims 1 to 15, characterized in that: The method further comprises: When the seventh interface is displayed, receiving a seventh operation on the reflow control in the seventh interface; In response to the seventh operation, the j-th third device is triggered to transfer the first service flow back to the i-th second device.

17. A device, characterized in that The method comprises a transceiver, a processor and a memory, wherein the memory is used to store a program, and the processor calls the program to execute the method according to any one of claims 1 to 16.

18. A storage medium, characterized in that: The storage medium stores a program, and when the program is executed by a processor, the method described in any one of claims 1 to 16 is implemented.

Citation Information

Patent Citations

  • Cross-device task processing interaction method, electronic device and storage medium

    CN111240547A

  • Cross-device circulation control method and device for large-screen service

    CN115883893A

  • Multi-tasker

    US20150032889A1

  • Multimedia Data Playing Method and Electronic Device

    US20220004315A1