Service circulation method and device and storage medium
By triggering business flows between any two devices from any device, the problem of low operational efficiency between devices is solved, and user experience and availability between devices are improved.
Patent Information
- Application Number
- CN202310498761.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-05
- Publication Date
- 2024-11-05
AI Technical Summary
In existing technologies, the business flow function between devices is inefficient when users need to walk to the device to operate it, and its availability is poor, especially when the device is far away from the user.
By triggering service flow between any two devices from any device, and utilizing any device in the communication system to receive user operations, display a device list, and sort and recommend devices, service flow can be achieved.
It improves the availability of business processes between devices, reduces user operation time and effort, and expands users' freedom of device use in fully connected scenarios.
Smart Images

Figure CN118900295A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of electronic technology, and in particular to a business flow method, device and storage medium. Background Art
[0002] At present, devices can provide a service flow 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. Users spend a lot of time and energy to achieve service flow, 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 flow function is poor. Summary of the invention
[0003] The present 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.
[0004] A first aspect provides a service flow method, which is applied to a first device, wherein the first device is any device in a communication system, and the method includes: receiving a first operation; displaying a first interface, wherein the first interface includes options of m second devices in the communication system, where m is an integer not less than 1; receiving a second operation for options of 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 flow; displaying a second interface, wherein the second interface includes options of n third devices in the communication system, where n is an integer not less than 1; receiving a third operation for options of 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, determining that the j-th third device is a target device for service flow, and triggering the i-th second device to transfer the first service flow to the j-th third device.
[0005] In some examples, the i-th second device is the first device, or is not the first device.
[0006] In some examples, the j-th third device is the first device, or is not the first device.
[0007] In some examples, the i-th second device and the j-th third device are any two devices in the communication system.
[0008] 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 fixed capabilities and 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 to use devices in full-connection scenarios, and improves the availability of business flow functions.
[0009] In one possible implementation, the first interface includes options of the m second devices after sorting, and before displaying the first interface, the method also 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 business flows run by the device, and whether the business flow function is enabled for the device.
[0010] 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.
[0011] 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.
[0012] In a possible implementation, 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 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.
[0013] In the above method, there can be multiple sorting rules for the second device that can be used as the source device for service flow. For example, the first device (i.e., the control device) running the 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 running the 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 running the 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 can be transferred by the device, the higher the priority of the sorting order. For another example, when both do not run the service that can be transferred, the greater the number of times the device performs service flow as the source device, the higher the priority of the sorting order. For another example, the device that enables the service flow function can be arranged before the device that does not enable the service flow function. There are various sorting rules, and they are based on the actual user experience, providing intelligent recommendations that meet the user's wishes, further improving the user experience.
[0014] In one possible implementation, the second interface includes options of the n third devices after sorting. Before displaying the second interface, the method also includes: screening out the n third devices from the communication system according to 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, 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.
[0015] In some examples, screening out the n third devices from the communication system according to 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.
[0016] In a possible implementation manner, the n third devices are devices whose device capabilities support performing the first service in the communication system.
[0017] 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.
[0018] In one possible implementation, the method further includes: 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 options of the first service among the p transferable services; displaying the second interface includes: in response to the fourth operation, displaying the second interface, the n third devices being related to the first service.
[0019] 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, thereby further improving the user experience.
[0020] 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.
[0021] In some examples, sorting the p transferable services based on a third algorithm is performed when the first device is a rich device; sending a 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.
[0022] 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 is 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.
[0023] In a possible implementation, the first service is determined according to a preset rule. In some examples, the preset rule is that the transferable service running in the foreground of the source device is the target service.
[0024] In the above method, the target business of the business flow can also be determined by the device according to preset rules, without the need for the user to manually select the target business, thereby reducing user operations and further reducing the time and energy spent by the user to trigger the business flow.
[0025] 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 of the first service; sending a first indication message to the j-th third device, the first indication message including information of 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 of 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.
[0026] In one possible implementation, the first device is a device having first system capabilities. In some examples, the first device is a rich device.
[0027] 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.
[0028] 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.
[0029] In a 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.
[0030] 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 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.
[0031] 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), which 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 be used as a control device due to weak or missing system capabilities, greatly expanding the range of control devices that can be operated by users in distributed scenarios, reducing the limitations of business flow functions, and improving user experience.
[0032] In one possible implementation, the method also includes: sending a registration message to the fourth device, the registration message is 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.
[0033] 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 is determined that the identity of the first device is illegal.
[0034] 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. The business flow will be triggered only if it is legal, thereby increasing the security of the business flow function.
[0035] In one possible implementation, receiving 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; when the connection with the fifth device is disconnected, canceling the display of the fourth interface.
[0036] In some examples, the first device is a light device and the fourth device and the fifth device are rich devices.
[0037] In the above method, when the first device and the fifth device are connected, the fourth interface (including 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 made a selection in the previous triggering process, the user does not need to reselect, which further facilitates user use.
[0038] In one possible implementation, receiving 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 prompt information of business flow failure.
[0039] 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 referred to as the triggering process for short), so that the user can intuitively obtain the reason why the triggering process cannot be performed and take countermeasures, for example, instead of changing 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.
[0040] 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.
[0041] 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 and further facilitates user use, improving user experience.
[0042] In one possible implementation, the method also includes: when displaying the seventh interface, receiving a seventh operation on a reflow control in the seventh interface; in response to the seventh operation, triggering the jth third device to transfer the first business flow back to the i-th second device.
[0043] 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, executing 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.
[0044] The second aspect provides a device including a transceiver, a processor and a memory; the memory is used to store programs, and the processor calls the program to execute the business flow method provided by the first aspect of the present application and any one of the implementation methods of the first aspect.
[0045] The third aspect provides a storage medium, which stores a program. When the program is executed by a processor, it implements the business flow method provided by the first aspect of the present application and any implementation method of the first aspect.
[0046] The fourth aspect provides a program product. When the program product runs on a device, the device executes the business flow method provided by the first aspect of the present application and any one of the implementations of the first aspect.
[0047] A fifth aspect provides a device, the device comprising a method or apparatus for executing any aspect or implementation of the present application. The above device is, for example, a chip.
[0048] 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 features or beneficial effects means that specific technical features, technical solutions or beneficial effects are included in at least one embodiment. Therefore, the description of technical features, technical solutions or beneficial effects 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
[0049] The following is an introduction to the drawings used in this application.
[0050] Figure 1 It is a schematic diagram of the architecture of a communication system provided by the present application;
[0051] Figure 2 It is a schematic diagram of the hardware structure of a device provided by this application;
[0052] Figure 3 It is a schematic diagram of the software architecture of a device provided by this application;
[0053] Figure 4 It is a schematic diagram of the architecture of a device provided by this application;
[0054] Figure 5A-5D This is a schematic diagram of a business flow interface provided by this application;
[0055] Figure 6A-6E is a schematic diagram of some user interfaces provided by this application;
[0056] Fig. 7A , Figure 7B This is another schematic diagram related to calling up a business flow interface provided by this application;
[0057] Fig. 8A , Figure 8B This is another schematic diagram related to calling up a business flow interface provided by this application;
[0058] Fig. 9A , Fig. 9B are schematic diagrams of some further user interfaces provided by this application;
[0059] Fig. 10A , Fig. 10B This is another schematic diagram related to calling up a business flow interface provided by this application;
[0060] Fig. 10C , Fig. 10D are schematic diagrams of some further user interfaces provided by this application;
[0061] Fig.11A , Fig. 11B This is another schematic diagram related to calling up a business flow interface provided by this application;
[0062] Fig.12 is a schematic diagram of a setting interface provided by this application;
[0063] Fig.13 It is a flowchart of a business flow method provided by this application;
[0064] Fig.14 This is a flowchart of another business flow method provided by this application;
[0065] Fig.15 It is a flowchart of a sorting process provided by this application. DETAILED DESCRIPTION
[0066] The technical solution in the embodiment of the present application will be described below in conjunction with the accompanying drawings. In the description of the embodiment of the present application, unless otherwise specified, " / " means or, for example, A / B can mean A or B; "and / or" in the text is only a description of the association relationship of associated objects, indicating that there can be three relationships, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiment of the present application, "multiple" means two or more than two.
[0067] In the following, the terms "first" and "second" are used for descriptive purposes only and are not to be understood as suggesting or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features, and in the description of the embodiments of the present application, unless otherwise specified, "plurality" means two or more.
[0068] First, the communication system 10 involved in the embodiment of the present application is introduced as an example.
[0069] See also Figure 1 , Figure 1 It is a schematic diagram of the architecture of a communication system 10 provided in an embodiment of the present application.
[0070] The communication system 10 in the present application may include multiple devices, and any one of the multiple devices (referred to as device 100) is used as an example for description. Figure 1 As shown, the device 100 can be connected and communicated with at least one device in the communication system 10 via a wired manner and / or a wireless manner. The wired manner includes, for example but not limited to, a high definition multimedia interface (HDMI), a universal serial bus (USB), a coaxial cable, an optical fiber, etc., and the wireless manner includes, for example but not limited to, Bluetooth, wireless fidelity (Wi-Fi), near field communication technology (NFC), ultra wide band (UWB), etc.
[0071] In one embodiment, the device 100 may be directly connected to at least one device in the communication system 10, for example Figure 1As shown, device 100 can be connected to device 200 via wireless methods such as Bluetooth, Wi-Fi, NFC, UWB, etc.
[0072] In one embodiment, the device 100 may be indirectly connected to at least one device in the communication system 10, for example Figure 1 As shown, the device 100 can be connected to the device 400 through the network 300. Optionally, the network 300 may include a server 301. The server 301 may be a hardware server or a virtual server. Optionally, the network 300 may include a router 302, etc. Optionally, the device 100 and the device 400 may be devices connected to the same local area network. In some examples, the device 100 and the device 400 may be installed with the same application (referred to as application A), and may log in to the same account or associated account through application A. The device 100 may communicate with the device 400 through the server 301 in the network 300 (e.g., an application server for providing services for application A). It is not limited thereto. The application may not be installed, and the account may be logged in through other forms such as a mini-program, or the account may not be logged in, etc. The present application does not limit the specific method of connecting and communicating through the network 300.
[0073] Not limited to the above-mentioned embodiments, in another embodiment, the device 100 may also obtain information of 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 may discover at least one device and obtain information of these devices through wired and / or wireless means (for example, Bluetooth, Wi-Fi, etc.). Not limited to this, in other examples, the device 100 may obtain information of historically connected devices (for example, this information may be stored during connection and may be obtained from a memory later). In other examples, the device 100 may also obtain information of at least one device through a server 301 in the network 300. For example, after the device 100 logs in to account A, it may obtain information of devices that have previously logged in to account A from the server 301. The present application does not limit the specific manner in which the device 100 obtains information of unconnected devices.
[0074] Figure 1 The form and quantity of the devices shown are only examples. In a specific implementation, other forms of devices may be used. For example, the router 302 may be replaced by a switch. The number of devices may be more or less. For example, the device 100 may be directly connected to multiple devices 200. This application does not limit this.
[0075] In the present application, any device in the communication system 10 (assuming it is device 100) can receive a user operation for triggering a service flow (referred to as a trigger operation), and in response to the trigger operation, trigger the service flow (also referred to as task flow) between any two devices in the communication system 10. For example, device 100 can trigger device 200 and device 400 to implement service flow in response to the user operation: service 1 performed by device 200 is transferred to device 400. In this service 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 service 1 can be called a target service. This can solve the limitations in 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 in 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 fully-connected scenarios, and improves the availability of business flow functions.
[0076] 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, which 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, which 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.
[0077] It can be understood that the control device, source device, and target device are all role concepts rather than physical concepts. A device can have multiple roles. In some examples, device 100 can trigger business flow in response to user operations: business 2 performed by device 100 is transferred 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 business flow in response to user operations: business 3 performed by device 200 is transferred to device 100. At this time, device 100 is both a control device and a target device. However, the source device and the target device are two different hardware devices.
[0078] 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 (featureability, FA) cards (such as weather cards, express service cards, etc.).
[0079] Any device in the communication system 10 may not perform / run any business, or may perform / run at least one business. The business that is visible and interactive to the user 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 business that is invisible and non-interactive to the user 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 the foreground business and the background business are role concepts, not physical concepts, and a business may be different roles in different scenarios.
[0080] In the present application, the 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 the present application do not impose any special restrictions on the specific types of devices.
[0081] Figure 2 The schematic diagram of the hardware structure of the device 100 is exemplarily shown.
[0082] 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 screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.
[0083] It is to be understood that the structure illustrated in the embodiment of the present application does 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 in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.
[0084] The processor 110 may include one or more processing units, for example, the processor 110 may include an application processor (AP), a modem processor, a graphics processor (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.
[0085] 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.
[0086] The processor 110 may also be provided with a memory for storing instructions and data. In one embodiment, the memory in the processor 110 is a cache memory. The memory may store instructions or data that the processor 110 has just used or cyclically used. If the processor 110 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.
[0087] The charging management module 140 is used to receive charging input from a charger. The charger may be a wireless charger or a wired charger. In some wired charging implementations, the charging management module 140 may receive charging input from a wired charger through the USB interface 130. In some wireless charging implementations, the charging management module 140 may receive wireless charging input through a wireless charging coil of the device 100. While the charging management module 140 is charging the battery 142, it may also power the device 100 through the power management module 141.
[0088] The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140, and supplies power to the processor 110, the internal memory 121, the display screen 194, the camera 193, and the wireless communication module 160. The power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle number, battery health status (leakage, impedance), etc. In 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.
[0089] The wireless communication function of the device 100 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor, etc. The device 100 can communicate with any device in the communication system 10 through the wireless communication function.
[0090] 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 the utilization of the antennas. 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 combination with a tuning switch.
[0091] The mobile communication module 150 can provide wireless communication solutions including second generation (2G) / third generation (3G) / fourth generation (4G) / fifth generation (5G) / sixth generation (6G) applied to the device 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, and filter, amplify and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1. In one embodiment, at least some of the functional modules of the mobile communication module 150 can be set in the processor 110. In one embodiment, at least some of the functional modules of the mobile communication module 150 can be set in the same device as at least some of the modules of the processor 110.
[0092] The modem processor may include a modulator and a demodulator. Among them, the modulator is used to modulate the low-frequency baseband signal to be sent into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After the low-frequency baseband signal is processed by the baseband processor, it is passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to a speaker 170A, a receiver 170B, etc.), or displays an image or video through a display screen 194. In 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.
[0093] The wireless communication module 160 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc., which are applied to the device 100. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, modulates the frequency of the electromagnetic wave signal and performs filtering, and sends the processed signal to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, modulate the frequency of it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.
[0094] The device 100 implements the display function through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, which connects the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs that execute program instructions to generate or change display information.
[0095] 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 1 or N display screens 194, where N is a positive integer greater than 1.
[0096] The device 100 can implement a shooting function through an ISP, a camera 193, a video codec, a GPU, a display screen 194, and an application processor.
[0097] The ISP is used to process data fed back by the camera 193. For example, when taking a photo, the shutter is opened, light is transmitted to the camera photosensitive element through the lens, and the light signal is converted into an electrical signal. The camera photosensitive element transmits the electrical signal to the ISP for processing and converts it into an image visible to the naked eye.
[0098] 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.
[0099] The external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the device 100 .
[0100] The internal memory 121 can be used to store executable program codes, which include instructions. The internal memory 121 may include a program storage area and a data storage area. Among them, 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.
[0101] The device 100 can implement audio functions through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone interface 170D, and the application processor.
[0102] 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 signal. The audio module 170 can also be used to encode and decode audio signals. The speaker 170A, also known as the "speaker", is used to convert audio electrical signals into sound signals. The receiver 170B, also known as the "earpiece", is used to convert audio electrical signals into sound signals. The microphone 170C, also known as the "microphone" and "microphone", is used to convert sound signals into electrical signals. The headphone interface 170D is used to connect wired headphones. The pressure sensor 180A is used to sense the pressure signal and can convert the pressure signal into an electrical signal. The gyroscope sensor 180B can be used to determine the motion posture of the device 100. The air pressure sensor 180C is used to measure the 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 all directions (generally three axes). The distance sensor 180F is used to measure the 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, and can also be used to indicate messages, missed calls, notifications, etc. The SIM card interface 195 is used to connect a SIM card or an eSIM.
[0103] The software system of the device 100 may adopt a layered architecture, an event-driven architecture, a micro-kernel architecture, a micro-service architecture, or a cloud architecture. For example, the software system of the layered architecture may be an Android system, or a Harmony operating system (OS), or other software systems. The embodiment of the present application takes the Android system of the layered architecture as an example to illustrate the software structure of the device 100.
[0104] Figure 3 A schematic diagram of the software architecture of a device 100 is shown as an example.
[0105] The layered architecture divides the software into several layers, each with clear roles and division of labor. The layers communicate with each other through software interfaces. In one embodiment, the Android system is divided into four layers, from top to bottom: the application layer, the application framework layer, the Android runtime and system library, and the kernel layer.
[0106] The application layer can include a series of application packages. Figure 3 As shown, the application package may include applications such as camera, video, music, gallery, short message, call, navigation, Bluetooth, browser, etc. The application in this application may also be replaced by other software such as mini-programs, atomic services / FA cards, etc.
[0107] The application framework layer provides an application programming interface (API) and programming framework for the applications in the application layer. The application framework layer includes some predefined functions. Figure 2 As shown, the application framework layer may include a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, and the like.
[0108] The window manager is used to manage window programs. The window manager can obtain the display screen size, determine whether there is a status bar, lock the screen, capture the screen, etc.
[0109] Content providers are used to store and retrieve data and make it accessible to applications. The data may include video, images, audio, etc.
[0110] The view system includes visual controls, such as controls for displaying text, controls for displaying images, etc. The view system can be used to build applications. A display interface can be composed of one or more views. For example, a display interface including a text notification icon can include a view for displaying text and a view for displaying images.
[0111] The phone manager is used to provide communication functions of the device 100, such as management of call status (including connection, disconnection, etc.).
[0112] The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, etc.
[0113] The notification manager enables applications to display notification information in the status bar. It can be used to convey notification-type messages and can disappear automatically after a short stay without user interaction. The notification manager can also be a notification that appears in the system top status bar in the form of an icon or scroll bar text, such as notifications of applications running in the background, or a notification that appears on the screen in the form of a dialog window. For example, it can prompt text information in the status bar, emit a prompt sound, etc.
[0114] Android Runtime includes core libraries and virtual machines. Android runtime is responsible for scheduling and management of the Android system.
[0115] The core library consists of two parts: one part is the function that needs to be called by the Java language, and the other part is the Android core library.
[0116] The application layer and the application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and the application framework layer as binary files. The virtual machine is used to perform functions such as object life cycle management, stack management, thread management, security and exception management, and garbage collection.
[0117] The system library may include multiple functional modules, such as surface manager, media library, 3D graphics processing library (such as OpenGL ES), 2D graphics engine (such as SGL), etc.
[0118] The surface manager is used to manage the display subsystem and provide the fusion of two-dimensional and three-dimensional layers for multiple applications.
[0119] The media library supports playback and recording of a variety of commonly used audio and video formats, as well as static image files, etc. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, etc.
[0120] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.
[0121] A 2D graphics engine is a drawing engine for 2D drawings.
[0122] The kernel layer is the layer between hardware and software. The kernel layer contains at least display driver, camera driver, audio driver, and sensor driver.
[0123] The following is an illustrative description of the software and hardware workflow of device 100 in conjunction with a business flow scenario.
[0124] Assume that the device 100 displays the audio playback interface of the music application in the foreground (also referred to 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 an original input event (including touch coordinates, timestamp of the touch operation, and other information). The original input event is stored in the kernel layer. The application framework layer obtains the original input event from the kernel layer and identifies the control corresponding to the input event. Taking the touch operation as a touch single-click operation, and the control corresponding to the single-click operation as the flow control of the music application as an example, the music application calls the interface of the application framework layer to obtain the device identification 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 identification through the display screen 194, so that the user can select the device identification of the target device for the audio playback service flow from the displayed device identification. 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).
[0125] Figure 4 A schematic diagram of the architecture of a device 100 is shown as an example.
[0126] like Figure 4 As shown, 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:
[0127] The distributed information management module 201 can be used to obtain and manage the device identification 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 capability, device identity document (ID) (which can be used to uniquely identify the device), device icon, and device model. The device capability can include but is not limited to at least one of hardware capabilities such as display screen information (such as whether a display screen 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. The service information can include but is not limited to at least one of the service identification, the type of service performed by the device (such as video playback, audio playback, product details interface of shopping applications, express service cards, etc.), service attributes (such as foreground services and background services), whether it is a transferable service, and the service usage time (i.e., the time when the 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 relevant information of the service (for example, the relevant information of the audio playback service is the audio name and the singer name).
[0128] The database 202 can be used to store the service flow times of multiple devices in the communication system 10, and the flow times of multiple service types. The service flow times of a device are the times that the device performs service flow as a source device, and the flow times of a service type are the times that services belonging to the service type perform service flow as target services. The flow times of subsequent service types can be referred to as service flow times. For example, the flow times of the video playback service can be the sum of the flow times of the video playback service of the video 1 application and the flow times of the video playback service of the video 2 application. In some examples, each time any device in the communication system 10 performs a service flow, the device 100 can record and update the content stored in the database 202.
[0129] The input module 203 can be used to receive user operations. Figure 4As shown in 1, the input module 203 can receive a user's 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 the multiple candidate devices according to the usage information and the current business operation information, and finally display the device identifications of the sorted multiple candidate devices (which can be referred to as sorted device identifications for short), and 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 of the candidate device and the number of business flows, such as the source device display module 204 reads from the database 202, and the above-mentioned current business operation information may include the information of 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.
[0130] like Figure 4 As shown in 2, 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 at this time). 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 circulations of the business read from the database 202, and finally display the business identifications of the sorted multiple businesses (which can be referred to as sorted business identifications for short), and the sorted business identifications can be used by the user to select the target business for this business circulation.
[0131] like Figure 4As shown in 3, when the source device service display module 205 displays the sorted service identifier, 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 identifier, and service A is the target service selected by the user at this time). In response to the operation, the target device display module 206 can obtain the device identifier of a candidate device that can be used as a target device for service transfer (i.e., a target device 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, according to the device usage time, device usage frequency, device location (for example, including the distance from the source device), etc., and finally display the sorted device identifier, which can be used by the user to select the target device for this service transfer.
[0132] like Figure 4 As shown in 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 sorted device identification, and device B is the target device selected by the user at this time), and in response to the operation, the business flow module 207 can trigger device A and device B to implement business flow: device A's business A flows to device B.
[0133] Not limited to Figure 4 In the embodiment shown, in another embodiment, the device 100 may also default that the device is the source device of this business transfer. At this time, the source device display module 204 may not obtain and display the sorted device identification. In another embodiment, 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. At this time, the source device business display module 205 may not obtain and display the sorted business identification, and this application does not limit this.
[0134] Not limited to Figure 4 In another embodiment, Figure 4 Any two modules shown can be integrated together, for example, the distributed information management module 201 and the database 202 can be integrated together. In another embodiment, Figure 4 Any module shown may include multiple modules. For example, the source device display module 204 may include a sorting module and a display module, which is not limited in the present application.
[0135] 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.
[0136] Figure 5A-5D A schematic diagram of calling out a service flow interface of the device 100 is exemplarily shown.
[0137] like Figure 5A As shown, the device 100 may 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. Among them, the status bar 511 may include at least one of a signal strength indicator of a mobile communication signal (e.g., a 5G signal), a signal strength indicator of a Wi-Fi signal, an indicator of Bluetooth, a battery status indicator, a time indicator, etc. The icons 512 of multiple applications include, for example, but not limited to, icons of video 1, video 2, music, calls, weather, and browsers. 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., sliding left or right).
[0138] like Figure 5A As shown, the device 100 may receive a user operation, such as a downward sliding operation from the top edge of the screen (such as the position of the status bar 511). In response to the user operation, the device 100 may display Figure 5B The user interface 520 shown, for example, is a control center interface.
[0139] like Figure 5BAs shown, the user interface 520 may include a play card 521, a Wi-Fi control 522, a Bluetooth control 523, icons 524 of multiple common functions, and a card 525 of a super terminal. Among them, the play card 521 includes the characters "not playing", indicating that the device 100 is not currently running a video playback service and an audio playback service. The Wi-Fi control 522 includes the characters "signal source 1", indicating that the device 100 is currently connected to a Wi-Fi signal named "signal source 1". The icons 524 of multiple common functions include, for example, but not limited to, a flashlight icon, a ringtone / mute icon, a screen rotation icon, a sharing icon, an airplane mode icon, and a brightness adjustment bar. The card 525 may include icons of currently connected devices, as well as the names and / or types of these devices, such as an icon of a watch named AAA (which may be referred to as watch AAA or device AAA, and other devices will be described in abbreviated form later, and the expressions without abbreviated forms will not be repeated one by one), an icon of a large screen BBB, and a control 525A. Without limitation thereto, in other examples, when device 100 is not connected to any device, a prompt message may be displayed in card 525 to prompt the user to search for other devices (eg, via control 525A).
[0140] like Figure 5B As shown, the device 100 may receive a user operation (eg, a touch operation) for the control 525A, and in response to the user operation, the device 100 may display Figure 5C The user interface 530 shown, in one implementation, may be a business flow interface.
[0141] like Figure 5C As shown, 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, names and / or types of the candidate devices, etc. Exemplarily, the icon of the device 100 is located in a preset area 1 (e.g. Figure 5C The icons of the candidate devices may be located in a preset area 2 (eg, a circular area 531) surrounding the icon 531 of the device 100. Figure 5C The embodiment of the present application does not specifically limit the shapes and positions of the above-mentioned preset area 1 and preset area 2. Figure 5C The circular area shown, the preset area 2 is Figure 5C The icons of the candidate devices may include: icon 532 of watch AAA, icon 533 of large screen BBB, icon 534 of laptop CCC, icon 535 of mobile phone DDD, and icon 536 of speaker EEE.
[0142] In one embodiment, the display mode of the candidate device icons shown in the user interface 530 may 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, Figure 5C The distance between the icon 532 of the watch AAA and the icon 531 of the device 100 is less than, Figure 5C The distance between the icon 533 of the large screen BBB and the icon 531 of the device 100 is shown. 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.
[0143] like Figure 5C As shown, the user interface 530 can be used by the user to select a target device for business flow. The icon of any candidate device shown in the user interface 530 can receive user operations, such as dragging to the preset area 1. In response to the user operation, the device 100 can determine that the candidate device is the target device for business flow. At this time, the device 100 defaults to the device as the source device for business flow. It can be understood that the user interface 530 can be a user interface for two-end flow. The two-end flow can be a business flow in which the device is the source device by default and the user selects the target device. It is not limited to this. The two-end flow can also be a business flow in which the device is the target device by default and the user selects the source device. Here, the two-end flow in which the device is the source device by default is described as an example. In one embodiment, the device 100 may default the foreground business of the device as the target business of the business flow, 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 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 of the business flow. Among them, the user operation for calling the user interface (e.g., user interface 530) for dual-end flow may include Figure 5A The action of sliding down from the top edge of the screen, and Figure 5B User operation on control 525A is shown.
[0144] like Figure 5C As shown, the user interface 530 also includes a control 537. The device 100 can receive a user operation (such as a touch operation) on the control 537, and in response to the user operation, display Figure 5D The user interface 540 shown, in one implementation, may be a business flow interface.
[0145] like Figure 5DAs shown, user interface 540 may include prompt information 541 and device identification 542. Prompt information 541 may include characters "free flow" and "please select source device", indicating that user interface 540 is an interface for selecting a source device for business flow. User interface 540 may be a free flow user interface. Free flow may be a business flow in which a user selects a source device and a target device. Device identification 542 may include controls for candidate devices detected by 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 an icon of the candidate device and a name of the candidate device. The multiple candidate devices shown in 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 watch AAA is set to not be allowed as a source device for free flow (see below for an example of the setting interface). Fig.12 , not described in detail) (it can also be called that the business flow function is not turned on), 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. It is not limited to this. The display mode can also include characteristics 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 the free flow user interface (such as user interface 540) can include Figure 5A The action shown is to swipe down from the top edge of the screen. Figure 5B The user operation shown for control 525A, and Figure 5C User operation on control 537 is shown.
[0146] In one embodiment, the mobile phone FFF, laptop computer CCC, mobile phone DDD, large screen BBB, and speaker EEE shown in device identification 542 are not running any transferable services, and can be considered to belong to the same priority, and these devices are arranged in order from large to small according to the number of service transfers of the devices: mobile phone FFF, laptop computer CCC, mobile phone DDD, large screen BBB, speaker EEE, which is consistent with the display order / arrangement order of 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 service transfers of the devices.
[0147] In another embodiment, the mobile phone FFF, laptop computer CCC, mobile phone DDD, and large screen BBB shown by device identification 542 all have transferable services running in the foreground or background, and the speaker EEE does not run 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 runs the video call service in the background. Since the mobile phone is the currently operated control device and runs the transferable service, it can be considered to be of the first priority; laptop computer CCC runs the video playback service in the foreground. The laptop computer is not a control device but runs the transferable service in the foreground, which can be considered to be of the second priority; mobile phone DDD runs the video playback service in the background, and large screen BBB runs the audio playback service in the background. These two devices are not control devices but run the transferable service in the background (and do not run the transferable service in the foreground), which 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 does not run the transferable service, which can be considered to be of the fourth priority. The device identification 542 can be sorted from high to low according to 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 business transactions. Figure 5D The device identification 542 shown is sorted in this way for example. Not limited to the above example, in other examples, the number of turnovers of the above business can also be replaced by the turnover weight of the business type, and the turnover weight of the business type is the ratio 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 (such as all businesses) counted by the device 100.
[0148] 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 circulations of the video playback service is greater than that of the audio playback service. Therefore, 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.
[0149] It can be understood that the 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 the device 200 or the device 400) receive a user operation for invoking free flow, they can also display Figure 5D The device identification 542 in the user interface 540 shown, ie, the free-flow function provided by each device in the communication system 10 is consistent.
[0150] Figure 5D The user interface 540 shown can be used for user triggering: the business flow between any two devices (including the device 100 itself) detected by the device 100. In one embodiment, the device 100 can receive a request for Figure 5D A user operation (eg, a touch operation) of a control of any one of the device identifiers 542 shown, the user operation being used to select the device as a source device for the business flow.
[0151] In some examples, device 100 receives a user operation on a control of speaker EEE in device identifier 542. In response to the user operation, device 100 may display a prompt message, such as "The current device has no streaming services, please reselect the source device." Subsequently, device 100 may display user interface 540 for the user to select another device as the source device.
[0152] In other examples, device 100 receives a user operation on a control of watch AAA in device identifier 542. In response to the user operation, device 100 may display a prompt message, such as "The current device does not allow business transfer, please reselect the source device." Subsequently, device 100 may display user interface 540 for the user to select another device as the source device.
[0153] In other examples, the device 100 receives a user operation on a control of any one of the devices FFF, CCC, DDD, and BBB (assuming it is the device DDD). In response to the user operation, the device 100 may determine that the device DDD is the source device of the service transfer, and display the service identifier of the transferable service performed by the device DDD (which may be referred to as the service identifier of the device DDD). For specific examples, see the following: Fig. 6A .
[0154] like Fig. 6AAs shown, the device 100 can display a user interface 610, and the user interface 610 can include a prompt message 611 and a service identifier 612. The prompt message 611 can 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 can include controls for multiple transferable services performed by the device DDD, wherein any one of the controls can 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 can 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 (such as the homepage).
[0155] In one embodiment, the audio playback service and weather card of the music application are foreground services, and the video playback service 1, the video playback service 2 and the user interface of the browser application are all background services. Assume that the number of service turnovers counted by the device 100 is, from large to small, video playback service, audio playback service, user interface of the browser application, and weather card. Among them, the use time of the video playback service 1 is later than the use time of the video playback service 2. The sorting method of the service identifier 612 may include: the foreground service is arranged before the background service; for services belonging to the same service attribute (i.e., the foreground service or the background service), the service turnover number is sorted from large to small; for services belonging to the same service attribute and the same type, such as the video playback service 1 and the video playback service 2, which are both background services, the service usage time is sorted from late to early. Not limited to the above examples, in other examples, the number of turnovers of the above services can also be replaced by the turnover weight. In other examples, it can also be that for services belonging to the same service attribute, the service usage time is directly sorted from late to early, and this application does not limit this.
[0156] In one embodiment, the device 100 may receive a request for Fig. 6A In response to the user operation, the service is determined as the target service for service transfer, and the device identifications of candidate devices that can be used as target devices for service transfer are displayed. For specific examples, see the following Figure 6B .
[0157] like Figure 6BAs shown, the device 100 may display a user interface 620, and the user interface 620 may include a prompt message 621 and a device identifier 622. The prompt message 621 may include the characters "Please select a target device", indicating that the user interface 620 is an interface for selecting a target device for business transfer. The device identifier 622 may include controls for candidate devices detected by the device 100 that can be used as target devices for business transfer, wherein any of the controls may include a device identifier of the corresponding candidate device, such as an icon of the candidate device and a name of the candidate device. The multiple candidate devices shown in the device identifier 622 may be screened, for example, from Figure 5C The devices whose device capabilities support the video playback service 1 are selected from the candidate devices detected by the device 100 shown. Assuming that the device capabilities required for the video playback service include a display screen, a speaker, and a software protocol that supports video playback, the device identification 622 (selected 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 screen). The multiple candidate devices shown in the device identification 622 may 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 use time (from late to early) / use frequency (from large to small), etc.
[0158] In one embodiment, the device 100 may receive a request for Figure 6B In the user interface 620 shown, a user operates (e.g., touches) a control on any device (assuming it is device BBB) in the device identifier 622. 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, i.e., the video playback service 1 of device DDD is transferred to device BBB. At this time, device 500 (i.e., target device: device BBB) can display the user interface of video playback service 1, for example, Figure 6C As shown in the user interface 630 , the user interface 630 may include the name 631 of the video being played (ie, “Video A”) and the video screen.
[0159] In some examples, after the service flow is successfully triggered, the device 600 (ie, the source device: device DDD) may display a prompt message, such as Fig.6D The user interface 640 shown in the figure may be an audio playback interface of a music application, and Fig. 6AThe service identifier 612 shown corresponds to the fact that the foreground service performed by the device 600 includes an audio playback service, and the user interface 640 may include a prompt message 641, which 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 service 1) has been transferred to the device BBB. The prompt message 641 may be displayed at the top of the screen for a preset time and then canceled, for example, displayed in other locations such as a list in the notification bar.
[0160] In some examples, after the service flow is successfully triggered, the device 100 may display a prompt message, such as Fig. 6E The user interface 650 shown in FIG. Figure 5A The user interface 510 is similar to the one shown, except that it also includes a prompt message 651 (including the characters "free flow successful"). The prompt message 651 can be displayed at the top of the screen for a preset time and then canceled, for example, displayed in a list in the notification bar or other locations.
[0161] In one implementation, at least one of the device 100 (i.e., the control device), the device 600 (i.e., the source device), and the device 500 (i.e., the target device) may provide a "one-key reflow" function, that is, in response to a user operation, trigger 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, the device 500 may cancel the user interface 630 displaying the video playback service 1, for example, returning to the previous interface (e.g., the desktop). In some examples, such as Figure 6C As shown, the user interface 630 displayed by the device 500 also includes a prompt message 632 (including the characters "Select 'Return' for one-key reflow"). The device 500 can receive a return operation, such as a user operating a return button on a remote control connected to the device 500. In response to the return operation, the current video playback service 1 stream is transferred back to the device 600, that is, the prompt message 632 is used to trigger the one-key reflow. In some examples, such as Fig.6D As shown, the prompt information 641 displayed by the device 600 may also include the characters "double-click for one-key reflow", which can be used to trigger one-key reflow. Fig. 6E As shown, 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.
[0162] Not limited to Figure 5A-5DAs shown in the method of calling up the business flow interface, in another embodiment, the device 100 can run application 1 in the foreground, and the user interface 1 of application 1 includes control 1, and control 1 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 of business flow.
[0163] For example, application 1 is a music application. Figure 7A-7B Another schematic diagram of calling out the service flow interface of the device 100 is shown. The user interface 1 is Fig. 7A The user interface 710 shown, for example, is an audio playback interface, and control 1 is a control 711 in the user interface 710 .
[0164] like Fig. 7A As shown, the device 100 may receive a user operation (eg, a touch operation) on a control 711 in a user interface 710 of a music application, and in response to the user operation, display Figure 7B The user interface 720 shown, in one embodiment, 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.
[0165] like Figure 7B As shown, the user interface 720 and Fig. 7A The user interface 710 shown is similar, except that it also 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 may include the device identifier of the corresponding candidate device), and 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 large screen BBB and watch AAA. The multiple candidate devices shown in the device identifier 722 may be sorted, for example, sorted from small to large according to the distance from the device 100 (i.e., the source device). The device identifier 722 can be used by the user to select the target device for business flow, and the icon of any candidate device shown in the device identifier 722 can receive user operations. In response to the user operation, the device 100 can determine that the candidate device is the target device for business flow, and trigger the audio playback business of the device 100 to flow to the candidate device. Viewing icons of more devices may be used to trigger the display device 100 to display more candidate devices detected by the device 100 for the user to select a target device.
[0166] like Figure 7B As shown, the user interface 720 also includes a control 723. The device 100 can receive a user operation (such as a touch operation) on the control 723, and in response to the user operation, display a free flow user interface for the user to select the source device, target service and target device of the service flow, such as displaying Figure 5D The user interface 540 shown (used by the user to select the source device for business flow transfer), the subsequent process and Figure 6A-6E The examples shown are similar and will not be repeated here.
[0167] Not limited to Figure 5A-5D , Figure 7A-7B In another embodiment, the device 100 may receive a user operation for calling the multitasking center, detect a candidate device for business transfer in response to the user operation, and display the user interface of the multitasking center. In this case, the user interface is also the user interface of the business transfer. Figure 8A-8B Another schematic diagram of calling out the service flow interface of the device 100 is shown.
[0168] like Fig. 8A As shown, the device 100 can display the 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 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 Figure 8B The user interface 820 shown, in one embodiment, 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 current foreground business (i.e., the video playback business 2 of the video 2 application) as the target business of the business flow.
[0169] like Figure 8BAs shown, 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., this device / machine), controls for candidate devices detected by the device 100 that can be used as target devices for service flow (any of which 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 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 screened from the candidate devices detected by the device 100, 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 examples and Figure 7B The description of the device identification 722 shown is similar. The device identification 821 can be used by the user to select a target device for the service flow, and the service identification 822 can be used to select a target service for the service flow. In some examples, the device 100 can receive a user operation on the control of the video playback service 2 in the service identification 822 and the control of the device BBB in the device identification 821. For example, the user operation is to drag the control of the video playback service 2 to the location of the control 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 the target service, and the video playback service 2 of the device 100 is triggered to flow to the device BBB.
[0170] like Figure 8B As shown, the user interface 820 also includes a control 823. The device 100 can receive a user operation (such as a touch operation) on the control 823, and in response to the user operation, display a free flow user interface for the user to select the source device, target service and target device of the service flow, such as displaying Figure 5D The user interface 540 shown (used by the user to select the source device for business flow transfer), the subsequent process and Figure 6A-6E The examples shown are similar and will not be repeated here.
[0171] Not limited to the above implementation, in another implementation, the above-mentioned user interface for dual-end transfer may also be a user interface for free transfer. In some examples, the user interface 530 may also be a user interface for free transfer (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 transfer, and may also include controls for candidate devices that can be used as target devices for business transfer, wherein 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 transfer of device BBB and device DDD. The present application does not limit the specific user operations. The candidate devices that can be used as source devices for business transfer shown in the user interface 530 may be sorted, and the display method of the candidate devices may 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 the 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, Figure 5C The candidate devices shown are those in the top N of the sorting results. The 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 results, where N is a positive integer. Not limited to this, the candidate devices shown in the user interface 530 that can be used as target devices for business flow can also be sorted. The specific example is similar to the above example, and the present application does not limit the display method of the free flow user interface.
[0172] Not limited to the above implementation, in another implementation, the device 100 may also respond to Figure 5B The user operation of the control 525A shown in FIG. 1 shows a free-flowing user interface. In another embodiment, the device 100 may also respond to the user operation of the control 525A. Fig. 7A The user operation of the control 711 is shown to display a free-flowing user interface. In another embodiment, the device 100 may also respond to Fig. 8A The user operation for calling the multitasking center shown in FIG. 1 displays a free-flowing user interface. The free-flowing user interface is, for example, Figure 5D User interface 540 is shown.
[0173] 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.
[0174] Next, a light device such as a watch (also referred to as device 700) is used as an example for explanation.
[0175] In one implementation, when the device 700 is not connected to a rich device, if a user operation for triggering a service transfer is received, a prompt message may be displayed to prompt the user that the service transfer is currently unavailable. Fig. 9A As shown, the device 700 is not connected to a rich device, and the device 700 can display a user interface 910. The user interface 910 can include controls for multiple functions, such as a control for a setting function, a control 911 for a business flow function, and a control for a motion record, etc. The device 700 can receive a user operation (such as a touch operation) for the control 911, and in response to the user operation, display Fig. 9B The user interface 920 shown may include a prompt message “Unable to stream, please connect a mobile phone or other rich device to assist in streaming”.
[0176] In one implementation, 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 dual-end transfer user interface may be displayed for the user to select a target device for service transfer. At this time, device 700 may default to being the source device and the transferable service running in the foreground to being the target service. For example, Fig. 10A As shown, device 700 is connected to device 500, and device 500 can display user interface 1010. For example, user interface 1010 is a desktop. User interface 1010 may include window 1011. Window 1011 may include an icon of the connected device (i.e., device 700) and the name "AAA". Device 700 can display user interface 1020. User interface 1020 may 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 a double-click operation, a long press operation, a sliding operation, etc. In response to the user operation, device 700 may request device 500 to obtain candidate devices that can be used as target devices for service flow, and display the data returned by device 500. Fig. 10B User interface 1030 is shown.
[0177] like Fig. 10BAs shown, the user interface 1030 may include prompt information 1031 and device identification 1032. The prompt information 1031 may include the characters "Please select the target device", indicating that the user interface 1030 is an interface for selecting the target device for business transfer. The device identification 1032 may be displayed by the device 700 according to the data returned by the device 500. The device identification 1032 may include controls of candidate devices detected by the device 500 that can be used as target devices for business transfer, wherein any control 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 candidate device shown in the device identification 1032 may be screened, for example, a device screened from the candidate devices detected by the device 500, whose device capabilities support the foreground business (i.e., video call business) of the device 700, such as a mobile phone FFF, a large screen BBB (i.e., the device 500), and a laptop computer CCC. The multiple devices in the device identification 1032 may be sorted, for example, sorted from small to large according to the distance from the device 700 (i.e., the source device). The icon of any candidate device (assuming it is mobile phone FFF) shown by device identification 1032 can receive user operation. 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 for 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 flow to mobile phone FFF.
[0178] In one implementation, when the video call service of device 700 is transferred to mobile phone FFF (ie, device 100), device 100 (ie, target device) may display a user interface of the video call service, for example, Fig. 10C The user interface 1040 shown in FIG. 1040 may include a prompt message 1041 (including characters “AAA’s video call has been transferred to this device”). The video call interface shown in the user interface 1040 and Fig. 10A The user interface 1020 displayed by the device 700 in the source device is consistent. Optionally, the prompt information 1041 can be canceled after being displayed at the top for a preset time, for example, displayed in other locations such as a list in the notification bar. In one embodiment, the device 700 (i.e., the source device) can also display the prompt information, such as displaying Fig. 10D The user interface 1050 shown in the figure may include a prompt message "The video call has been transferred to FFF". Optionally, the prompt message may be canceled after being displayed for a preset time, for example, the device 700 returns to the display home page. In one embodiment, the device 500 (i.e., the rich device to which the device 700 is connected) may also display a prompt message, such as displaying Fig. 10DThe user interface 1060 shown in FIG. Fig. 10A The user interface 1010 shown is similar, except that the 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 the device FFF.
[0179] In one implementation, at least one of the device 700 (i.e., a light device that serves as a control device and is also a source device), the device 500 (i.e., a rich device connected to the control device), and the device 100 (i.e., a target device) may provide a "one-key reflow" function, that is, it may trigger the video call service to be transferred from the target device back to the source device in response to a user operation. At this time, the device 100 may cancel the user interface 1040 that displays the video call service, for example, returning to the previous interface (e.g., the desktop). In some examples, such as Fig. 10C As shown, the prompt information 1041 displayed by the device 100 (i.e., the target device) also includes the characters "Double-click for one-key reflow". The prompt information 1041 can receive a user operation (e.g., a double-click operation). In response to the user operation, the device 100 can transfer the current video call service flow back to the device 700, i.e., the prompt information 1041 is used to trigger the one-key reflow. In some examples, such as Fig. 10D As shown, the user interface 1050 displayed by the device 700 (i.e., the source device, which is also the control device) also includes a prompt message "Double-click the screen to trigger one-key reflow", which can be used to trigger one-key reflow. Fig. 10D As shown, the window 1011 displayed by the device 500 (ie, the rich device connected to the control device) also includes a control 1062, which can also be used to trigger one-key reflow.
[0180] Not limited to Figure 10A-10B In another embodiment, when the device 700 does not run a transferable service in the foreground but runs a transferable service in the background, if a user operation for triggering service transfer is received, a dual-end transfer user interface (e.g. Fig. 10B As shown in the user interface 1030), the device 700 may default the transferable business performed in the background as the target business.
[0181] In one implementation, when the device 700 is connected to a rich device (assuming that it is the device 500, i.e., the large screen BBB) and does not run a flowable service, if a user operation for triggering service flow is received, a free flow user interface may be displayed. Fig.11A As shown, device 700 is connected to device 500, and device 500 can display Fig. 10A As shown in user interface 1010, device 700 may display Fig. 9AThe device 700 may receive a user operation (e.g., a touch operation) on a control 911 in the user interface 910. In response to the user operation, the device 700 may request the device 500 to obtain a candidate device that can be used as a source device for business flow transfer, and display the data returned by the device 500. Fig. 11B User interface 1110 is shown.
[0182] like Fig. 11B As shown, user interface 1110 may include prompt information 1111 and device identification 1112. Prompt information 1111 may include characters “Please select source device”, indicating that user interface 1110 is an interface for selecting a target device for business flow. 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 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. 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, wherein the rich device connected to device 700 (i.e., device BBB) may be considered to be of the first priority, for example, when device 700 is not running a flowable business, but the rich device is running a flowable business. For examples of sorting methods for other devices, see Figure 5D The ordering method of the device identification 542 shown is not repeated here.
[0183] In one implementation, when the device 700 switches the connected rich device, the order in which the device identification 1112 is displayed may change. For example, the device 700 switches from being connected to the device 500 to being connected to the device 100 (i.e., the device FFF). At this time, in the device identification 1112, the device BBB (i.e., the device 500) is no longer in the first place, but the device FFF is in the first place. The device BBB and other devices are sorted according to the device priority and service status. For an example of a specific sorting method, see Figure 5D In one embodiment, when the service of any device in the communication system changes, the order in which the device identification 1112 is displayed may also change. For specific examples, see Figure 5D An illustration of device identification 542 is shown.
[0184] Fig. 11B The user interface 1110 shown can be used for user triggering: the service 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) can be received by the user. Fig. 11BAny device (assuming that Fig. 11B In response to a user operation (e.g., a touch operation) of a control of a device DDD (not shown), device 700 may determine that device DDD is the source device for the service transfer and send a corresponding notification to device 500. Device 500 may return the sorted service identifiers of multiple transferable services performed by device DDD (which may be referred to as the service identifiers of device DDD) to device 700. Device 700 may display the service identifiers of device DDD for the user to select a target service for the service transfer. Fig. 6A The description is similar and will not be repeated here.
[0185] In one implementation, device 700 may receive a user operation (e.g., a touch operation) for any one of the displayed service identifiers (assuming it is video playback service 2). In response to the user operation, device 700 may determine that video playback service 2 is the target service for service transfer, and send a corresponding notification to device 500. Device 500 may return device identifiers of a plurality of candidate devices that have been screened and / or sorted and can be used as target devices for service transfer (referred to as candidate device identifiers for short) to device 700. Device 700 may display the candidate device identifiers for the user to select the target device for service transfer from them. Specific instructions and Figure 6B , Fig. 10B The description is similar and will not be repeated here.
[0186] In one implementation, 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., the video playback service 2 of device DDD is transferred to device CCC, and at this time, device CCC may display the user interface of video playback service 2, as shown in the specific example and Figure 6C The user interface 630 shown is similar.
[0187] 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-key reflow" function, that is, it may trigger the video playback service 2 to be transferred 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 examples displayed by device 700 and Fig. 10D Similar to the user interface 1050 shown, the interface example displayed by the device 500 is similar to the user interface 1050 shown in FIG. Fig. 10D Similar to the user interface 1060 shown, the interface example displayed by the device DDD is similar to Fig.6D Similar to the user interface 640 shown, the interface example displayed by the device CCC is similar to Figure 6C The user interface 630 shown is similar.
[0188] In one implementation, when a user triggers a service flow process (referred to as a trigger process) through device 700, if device 700 is disconnected from the connected rich device 1, device 700 may display a prompt message, and when device 700 is subsequently connected to rich device 2, device 700 may continue to display the service flow interface, allowing the user to continue the previous trigger process, wherein rich device 2 may be rich device 1 previously connected to device 700, or may be another rich device. In some examples, device 700 displays a user interface for selecting a target device (including a candidate device identifier, such as Fig. 10B If the user interface 1030 shown in FIG. 1 is disconnected from the connected rich device 1, the user interface 1030 shown in FIG. 1 may be displayed. Fig. 9B The user interface 920 shown is used to prompt the user that the current triggering process is terminated. When the device 700 is subsequently connected to the rich device 2, for example, in response to a user operation for triggering a service flow, the device 700 can redisplay the previous user interface for selecting a target device based on the candidate device identifier returned by the rich device 1. If the source device and / or target service have been acquired before the device 700 is disconnected from the rich device 1, for example, a user operation for selecting a source device and / or target service is received, or an active device and / or target service is assumed, the acquired source device and / or target service can be synchronized to the rich device 2. In this way, after the device 700 is connected to the rich device 2, the user can continue the previous triggering process without reselecting the source device and / or target service, thereby ensuring that the service flow triggered by the user will not be interrupted due to switching of the rich device. Optionally, device 700 can respond to a user operation on the device identifier of any candidate device in the user interface, determine that the candidate device is the target device, and send a corresponding notification to rich device 2, so that rich device 2 triggers the business flow between the source device and the target device selected by the user. If rich device 2 cannot trigger the business flow between the source device and the target device selected by the user, for example, rich device 2 cannot communicate with the source device and / or the target device, a corresponding notification can be returned to device 700, and device 700 can display a corresponding prompt message to enable the user to re-trigger the business flow based on device 700 connected to rich device 2.
[0189] 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 identification of 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 identification of multiple candidate devices detected by the rich device 1) displayed when the device 700 is connected to the rich device 1.
[0190] Not limited to the above implementation, in another implementation, when the device 700 is connected to a rich device and runs a transferable service, if a user operation for triggering service transfer is received, a free transfer user interface may also be displayed, for example Fig. 11B User interface 1110 is shown.
[0191] 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.
[0192] In one embodiment, any device in the communication system 10 (using device 100 as an example for illustration) can enable or disable the service transfer function by default. After the service transfer function is enabled, device 100 can perform service transfer as a source device or a target device. In another embodiment, device 100 can enable or disable the service transfer function in response to user operations. For specific examples, see the following. Fig.12 .
[0193] Fig.12 A schematic diagram exemplarily shows a setting interface.
[0194] like Fig.12As shown, the device 100 can display a user interface 1200, and 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 a text description (when turned 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 on a mobile phone on a tablet, and pulling them to the tablet to continue playing (also known as business flow)), and the switch control 1202 can be used to turn the multi-device task center function on or off. The business flow function may include sub-functions: a two-end flow function and a free flow function. The user interface 1200 may also include a description of the two-end flow function ("allowing the business flow of both parties to be triggered on this device and the other device") and a switch control 1203, as well as a description of the free flow function ("allowing the business flow of this device and the other device to be triggered 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-end flow function, and the switch control 1204 may be used to turn on or off the free flow function. Exemplarily, 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, and the user may also independently control the turning on or off of the two-end 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. After the two-end flow function is turned on, the device 100 may be used as a control device to trigger the business flow of this device and other devices. For specific examples, see Figure 5A-5C , Figure 7A-7B , Figure 8A-8B , Figures 10A-10D , or, other devices can act as control devices to trigger the service flow between device 100 and the other devices. At this time, the candidate devices displayed by other devices as target devices for service flow may include device 100. After the free flow function is turned on, any device that discovers and / or connects to device 100 can act as a control device to trigger the service flow between device 100 and other devices. The control device can be device 100 itself or the other device. For specific examples, see Figure 5A-5D , Figure 6A-6E , Figure 11A-11B .
[0195] Not limited to Fig.12 In the embodiment shown, in another embodiment, 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 the user operation. This application does not limit the functions that can be set.
[0196] Based on the above embodiments, the business flow method involved in this application is introduced. This method can be applied to Figure 1 The communication system 10 is shown.
[0197] See also Fig.13 , Fig.13 It is a flowchart of a business flow method provided in an embodiment of the present application. Fig.13 The first device is a control device (rich device), the second device is a source device, and the third device is a target device. The method may include but is not limited to the following steps:
[0198] S101: A first device receives a first operation.
[0199] In one implementation, 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.
[0200] In some examples, the first operation may include Figure 5A The action shown is to swipe down from the top edge of the screen. Figure 5B User operation of control 525A as shown, and optionally, Figure 5C User operation on control 537 is shown.
[0201] In some examples, the first operation may include Fig. 7A User operation of control 711 as shown, optionally and Figure 7B User operation on control 723 is shown.
[0202] In some examples, the first operation may include Fig. 8A The user operation shown for calling up the multitasking center, optionally and Figure 8B User operation on control 823 is shown.
[0203] In some examples, the first operation may include Fig. 10A The user operation on the user interface 1020 is shown (for example, a double-click operation, a long press operation, a sliding operation, etc.).
[0204] In some examples, the first operation may include Fig.11A User operation on control 911 is shown.
[0205] S102: The first device obtains device identifications and service information of multiple first candidate devices.
[0206] 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 log in to the same account as the first device, and use the queried devices as the first candidate devices. It is not limited to this, and it may also be a device that is an associated account with the account logged in by the first device. The present application does not limit the specific manner in which the first device detects the first candidate device.
[0207] In one implementation, after the first device detects multiple first candidate devices, it can obtain the device identification and service information of each first candidate device. For details, see Figure 4 The device identification and business information obtained 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. Without limitation, 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.
[0208] 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.
[0209] In one embodiment, the first device may sort multiple first candidate devices according to usage information and current business operation information, and obtain m device identifiers, and the m device identifiers are the device identifiers of the sorted m 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 about 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 (that is, 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, and 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 found below Fig.15 , which will not be described in detail for the time being, and this application does not limit the specific content of the first algorithm.
[0210] S104: The first device displays m device identifications.
[0211] In one implementation, the first device may display the m device identifiers obtained in S103. For a specific example, see Figure 5D The device identification 542 in the user interface 540 is shown. Fig. 11B Device identification 1112 in user interface 1110 is shown.
[0212] S105: The first device receives a second operation (for selecting a device identifier of a second device from among the m device identifiers), and determines that the second device is a source device for service transfer.
[0213] In one embodiment, the first device can receive a second operation on 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 for this business transfer, and obtain information on the transferable business currently being performed by the second device.
[0214] 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).
[0215] In another implementation, after receiving the second operation, the first device may "actively" obtain information about the currently-performing transferable service from the second device. That is, after S105, the method further includes:
[0216] S106: The first device sends a first request message to the second device.
[0217] 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.
[0218] 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.
[0219] In one implementation, the first device may sort multiple transferable services currently being performed by the second device according to service usage time, and obtain p service identifiers, which are the service identifiers of the p transferable services currently being performed by the second device after sorting.
[0220] In one implementation, the later the service is used, the higher the priority of the arrangement sequence.
[0221] In another embodiment, the first device may sort multiple transferable services currently being performed by the second device according to service attributes (e.g., foreground services and background services) and service usage time, wherein foreground services are sorted before background services, and for services with the same service attributes, the later the service usage time, the higher the priority in the sorting order.
[0222] In another embodiment, the first device may sort multiple transferable services currently being performed by the second device according to service attributes, flow weights of service types, and service usage time, wherein foreground services are arranged before background services, and for services belonging to 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 order, and for services belonging to the same service attributes and the same service type, the later the service usage time, the higher the priority in the arrangement order. The flow weight of the above-mentioned service type is the ratio of the flow times of services of the service type to the total flow times, and the total flow times are 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 may also be replaced by the flow times of the service type, and the present application does not limit the specific content of the second algorithm.
[0223] S109: The first device displays p service identifiers.
[0224] In one implementation, the first device may display the p service identifiers obtained in S108. For a specific example, see Fig. 6A Business identification 612 in user interface 610 is shown.
[0225] 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.
[0226] In an implementation manner, the first device may receive a third operation for the service identifier of the first service among the p service identifiers described in S109, and determine, in response to the third operation, that the first service is the target service of this service transfer.
[0227] 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.
[0228] In one embodiment, after the first device determines that the first business is the target business of this business transfer, it can screen out multiple second candidate devices related to the first business from 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 may be a device whose device capabilities (which may include hardware capabilities and software capabilities) support the first business.
[0229] In one embodiment, the first device may sort multiple second candidate devices according to at least one of device usage time (for example, the time when the device was last used), device usage frequency (for example, the number of times the device is used within a preset time period), and device location (for example, the distance between the device and a source device, or the distance between the device and a control device), and obtain n device identifiers, where the n device identifiers are the device identifiers of the sorted n second candidate devices. Optionally, the longer the device is used, the higher the priority of the arrangement order. Optionally, the greater the frequency of device use, 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.
[0230] S112: The first device displays n device identifications.
[0231] In one implementation, the first device may display the n device identifiers obtained in S111. For a specific example, see Figure 6B Device identification 622 in user interface 620 is shown.
[0232] S113: The first device receives the fourth operation (used to select the device identifier of the third device among the n device identifiers), and determines that the third device is the target device for the service transfer.
[0233] In one implementation, 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 this 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.
[0234] S114: The first device sends a second request message to the second device.
[0235] S115: The second device sends a second response message (including execution information of the first service) to the first device.
[0236] 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.
[0237] S116: The first device sends a first indication message (including execution information of the first service) to the third device.
[0238] In one implementation, the first indication message may be used to instruct the third device to perform the first service.
[0239] S117: The third device displays the interface of the first service according to the first indication message.
[0240] In one implementation, the third device may respond to the instruction of the first instruction message and perform the first service according to the execution information of the first service in the first instruction message. At this time, the user interface of the first service may be displayed. For specific examples, see Figure 6C and Fig. 10C .
[0241] In one implementation, 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.
[0242] Not limited to Fig.13 In the process shown, in other embodiments, S114-S117 can also be replaced by the first device sending a second indication message to the second device, the second indication message can include the service identifier of the first service and the device identifier of the third device, the second indication message can 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 can send a third indication message to the third device, the third indication message can be used to instruct the third device to perform the first service, the third indication message can include the execution information of the first service, and the third device can perform the first service according to the third indication message, that is, not limited to Fig.13 The first device shown as a "transfer device" forwards the execution information of the first service from the second device (source device) to the third device (target device). It can also be that the first device notifies the second device to transfer the service, and then the second device and the third device perform data interaction for the service transfer on their own. It is not limited to the first device notifying the second device (source device) to transfer the service. In other embodiments, the first device can also notify the third device (target device) to transfer the service, and the third device requests the execution information of the first service from the second device on its own. This application does not limit this.
[0243] Fig.13 The control device (first device) and the source device (second device) are different for example. 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 in certain circumstances. For specific examples, see Figure 5A-5C , Figure 7A-7B , Figure 8A-8B ,In other examples, the source device selected by the user is the ,controlling device, e.g. Figure 5C In the illustrated implementation, the device 100 receives a user operation on a control of the device FFF in the device identifier 542. When the control device and the source device are the same, the control device (first device) can directly obtain the information of the transferable service and the execution information of the target service performed by itself without being informed by other devices, for example, S106-S107 and S114-S115 are not executed.
[0244] Fig.13 Taking the control device (first device) and the target device (third device) as an example, 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, Figure 6BIn the illustrated implementation, the device 100 receives a user operation on a control for the device FFF in the device identifier 622. When the control device and the target device are the same, after S115, the first device can directly perform the first service according to the second response message without executing S116-S117.
[0245] exist Fig.13 In the method shown, 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, a 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 (i.e., 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.
[0246] Fig.13 In the service flow method shown, the first device as the control device can be a rich device, the first device can independently receive user operations, and trigger the service flow of the second device and the third device in response to the user operation. In other embodiments, the control device can also be a light device, which can receive user operations and trigger the service flow of the source device and the target device with the help of the connected rich device in response to the user operation. For details, please refer to the following Fig.14 .
[0247] See also Fig.14 , Fig.14 It is a flowchart of a business flow method provided in an embodiment of the present application. Fig.14 The method is described by taking 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. The method may include but is not limited to the following steps:
[0248] S201: The first device receives a fifth operation.
[0249] In one implementation, the fifth operation may be used to trigger a service flow, that is, the first device may 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. Fig.13 An example of the first operation in S101.
[0250] S202: The first device sends a registration message to the fourth device.
[0251] 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 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 of 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 fail to trigger a business flow with the help of the fourth device.
[0252] The order of S201 and S202 is not limited.
[0253] S203: The first device sends a third request message to the fourth device.
[0254] 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.
[0255] S204: The fourth device obtains device identifications and service information of multiple third candidate devices.
[0256] 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, such as 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, such as sending a corresponding notification to the first device.
[0257] In one implementation, 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 be used as the source device for service flow, and obtain the device identification and service information of each third candidate device. For details, see Fig.13 In S102, the first device detects the first candidate device, and the first device obtains the device identification and service information of the first candidate device.
[0258] 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.
[0259] S205 and Fig.13 Similar to S103, please refer to Fig.13 Description of S103.
[0260] 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, and this application does not limit the specific content and form.
[0261] S207: The first device displays f device identifications.
[0262] In one implementation, the first device may display f device identifiers according to the information of f device identifiers sent by the fourth device. The specific examples and Fig.13 The examples of m device identifications in S104 are consistent.
[0263] 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 flow.
[0264] 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 for this business transfer, and obtain information about the currently transferable business performed by the second device, such as executing S209.
[0265] S209: The first device sends a fourth request message to the fourth device.
[0266] In an implementation manner, the fourth request message may be used to request to obtain a service identifier of a target service that can be used as a service flow, and the fourth request message may include a device identifier of the second device.
[0267] S210: The fourth device uses the second algorithm to sort the multiple transferable services of the second device, and obtains 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.
[0268] 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 the information of the currently transferable business of the second device, such as executing S210. If the judgment result is no, the fourth device may not obtain the information of the currently transferable business of the second device, such as sending a corresponding notification to the first device.
[0269] In one implementation, after receiving the fourth request message sent by the first device, the fourth device can obtain information about the transferable service currently being performed by the second device, specifically describing and Fig.13The description of the first device obtaining the information of the transferable service currently being performed by the second device in S105 is similar and will not be repeated. Then, the fourth device can use the second algorithm to sort the obtained multiple transferable services. Fig.13 The description of S108 is similar and will not be repeated here.
[0270] S211: The fourth device sends information of j service identifiers to the first device, wherein the information of j service identifiers is used to represent the j service identifiers, and this application does not limit the specific content and form.
[0271] S212: The first device displays j service identifiers.
[0272] In one implementation, the first device may display j service identifiers according to information of j service identifiers sent by the fourth device. For specific examples, see Fig. 6A Business identification 612 in user interface 610 is shown.
[0273] S213: The first device receives the seventh operation (for selecting the service identifier of the first service among the j service identifiers), and determines that the first service is the target service of the service transfer.
[0274] In an implementation manner, the first device may receive a seventh operation for the service identifier of the first service among the j service identifiers described in S212, and determine, in response to the seventh operation, that the first service is the target service of this service transfer.
[0275] S214: The first device sends a fifth request message to the fourth device.
[0276] In an implementation manner, 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.
[0277] 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, wherein t is equal to f or t is not equal to f.
[0278] 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, such as executing S215. If the judgment result is no, the fourth device may not obtain multiple fourth candidate devices related to the first business, such as sending a corresponding notification to the first device.
[0279] In one implementation, the fourth device may determine that the first service is the target service of the service transfer according to the fifth request message, and then may screen out multiple fourth candidate devices related to the first service from multiple devices detected by the fourth device, and the fourth device may detect multiple devices. Fig.13 The description of the first device detecting the first candidate device in S102 is similar and will not be repeated here. The fourth candidate device may be a device whose device capabilities (including hardware capabilities and software capabilities) support the first service. Then, the fourth device may use the third algorithm to sort the obtained multiple fourth candidate devices. The specific description and Fig.13 The description of the first device sorting multiple second candidate devices in S111 is similar and will not be repeated here.
[0280] S216: The fourth device sends information of t device identifications to the first device, wherein the information of t device identifications is used to represent the t device identifications, and this application does not limit the specific content and form.
[0281] S217: The first device displays t device identifications.
[0282] In one implementation, the first device may display t device identifiers according to the information of t device identifiers sent by the fourth device. For specific examples, see Figure 6B Device identification 622 in user interface 620 is shown.
[0283] S218: The first device receives the eighth operation (used to select 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.
[0284] In one implementation, the first device may receive an eighth operation for 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.
[0285] S219: The first device sends a fourth indication message to the fourth device.
[0286] In one implementation, the fourth indication message may be used to instruct the fourth device to trigger a service transfer: the first service of the second device is transferred to the third device, and the fourth indication message may include a device identifier of the third device.
[0287] S220: The fourth device sends a fifth indication message to the second device.
[0288] In an implementation, the fifth indication message may include a service identifier of the first service and a device identifier of the third device, and the fifth indication message may be used to instruct the second device to transfer the first service to the third device.
[0289] S221: The second device sends a sixth indication message (including execution information of the first service) to the third device.
[0290] In one implementation, the sixth indication message may be used to instruct the third device to perform the first service.
[0291] S222: The third device displays the interface of the first service according to the sixth instruction message.
[0292] In one implementation, the third device may respond to the instruction of the sixth instruction message and perform the first service according to the execution information of the first service in the sixth instruction message. At this time, the user interface of the first service may be displayed. For specific examples, see Figure 6C and Fig. 10C .
[0293] In one implementation, 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.
[0294] Not limited to Fig.14 In the process shown in the figure, 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 service, and the fourth device can send the obtained execution information of the first service to the third device, so that the third device executes S222, and the specific description and Fig.13 S114-S116 are similar and will not be described in detail.
[0295] In one embodiment, Fig.14In the process shown, if the first device switches the connected rich device, for example, from connecting with the fourth device to connecting with the fifth device, the first device and / or the fourth device may send information about the service flow 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. 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 a "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 take over the "one-key reflow" function from the fourth device, that is, the first device, the second device, the third device and the fifth device can provide a "one-key reflow" function.
[0296] Fig.14 The control device (first device) and the source device (second device) are different for example. In other embodiments, the control device and the source device may be the same. For details, see Fig.14 The control device and the source device have the same instructions.
[0297] Fig.14 The control device (first device) and the target device (third device) are different for example. In other embodiments, the control device and the target device may be the same. For details, see Fig.13 The control device and the target device are the same.
[0298] Fig.14 The rich device (fourth device) assisting the control device and the source device (second device) are different as an example for description. In other embodiments, the rich device and the source device may also be the same. For specific description, see Fig.14 The control device and the source device have the same instructions.
[0299] Fig.14 The rich device (fourth device) assisting the control device and the target device (third device) are different as an example for description. In other embodiments, the rich device and the target device may also be the same. For specific description, see Fig.13 The control device and the target device are the same.
[0300] exist Fig.14In the method shown, the light device (i.e., the first device) as a control device can receive user operations, respond to user operations, request the connected rich device, receive feedback from the 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, Fig.14 The method shown solves the problem that light devices cannot be used 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.
[0301] See also Fig.15 , Fig.15 is a flowchart of a sorting process based on the first algorithm provided in an embodiment of the present application. This process can be applied to Fig.13 The first device (as a rich device of the control device) is implemented as shown, for example, the implementation process of S103. The method can also be applied to Fig.14 The fourth device (a rich device that assists in controlling the device) shown is, for example, an implementation process of S205. For the sake of convenience, the process is applied to the first device as an example for illustration. The sorting process may include but is not limited to the following steps:
[0302] S301: The first device obtains devices other than the flow-denying device from a plurality of candidate devices (a first candidate set).
[0303] In one implementation, the first device may filter out devices other than the transfer-denied device from the detected multiple candidate devices (i.e., candidate devices that can be used as source devices for service transfer), and the filtered devices may be collectively referred to as a first candidate set, wherein the transfer-denied device may be set to be a source device that is not allowed to be freely transferred (also referred to as a device that does not have the service transfer function enabled). For specific setting examples, see Fig.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 the subsequent sorting process, which can be understood as setting the flow rejection device to be the last device in the sorting process, for example Figure 5D The watch AAA in the device identification 542 shown is the last one displayed in the device identification 542, and the display method is different from other devices.
[0304] 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 service flow times of the devices, and the sorted multiple devices are the first candidate set.
[0305] 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.
[0306] In one implementation, 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 from the front to the back in order of sorting) according to their service operation conditions:
[0307] The first priority level is that the control device running the transferable service (which can also be understood as the "handheld device" operated by the user) is classified as the first priority level. It can also be understood that when there is no control device running the transferable service, there is no device with the first priority level.
[0308] The second priority level is for devices that run transferable services in the foreground (the transferable services may be run in the background or not in the background) and are classified as the second priority level.
[0309] The third priority level: a device that runs a transferable service in the background and does not run a transferable service in the foreground is classified as the third priority level;
[0310] The fourth priority level is the equipment that is not running any transferable services.
[0311] Not limited to the device priorities in 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 devices 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 classified as a 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.
[0312] In one implementation, 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 respectively. Devices divided into the same priority may be referred to as belonging to the same second candidate set.
[0313] 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.
[0314] It can be understood that for any priority level, if there is no device classified as this priority level, the second candidate set corresponding to this priority level is empty. For example, in the first candidate set of the above example, if the first device does not run a transferable service, the second candidate set corresponding to the first priority level is empty.
[0315] S303: The first device obtains the service flow number of the device.
[0316] In one embodiment, the first device can obtain the service flow count 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 service flow count of multiple detected candidate devices. For example, when any device in the communication system 10 performs service flow as a source device, the first device can update the stored service flow count of the device.
[0317] S304: The first device sorts the second candidate set corresponding to the fourth priority according to the number of service flow of the device.
[0318] 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 flow times of the devices, and a greater number of service flow times leads to a higher priority in the arrangement order.
[0319] It is understandable that if the first candidate set is sorted according to the number of service transfers 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 transfers of the device.
[0320] S305: The first device obtains the number of service transfers.
[0321] 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.
[0322] 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.
[0323] In one implementation, 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 transfers of the transferable services performed by these devices. A specific example is as follows:
[0324] In some examples, the first device may 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 (which may be referred to as service attribute weights) to the foreground service and the background service. The first device may score the flow weight of the transferable service performed by the device and the service attribute weight. The higher the score, the higher the priority of the device. 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 (c is greater than d), respectively, 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, and device 3 is arranged before device 4.
[0325] In other examples, the devices included in the second candidate set all run transferable services with the same service attributes. For example, the second candidate set corresponding to the third priority only includes devices running transferable services in the background. The first devices can be directly sorted according to the transfer weights of the transferable services performed by the devices. The devices with larger transfer weights have higher priority in the arrangement order. Not limited to this, the devices can also be directly sorted according to the number of transfers of the transferable services performed by the devices. The devices with larger transfer times have higher priority in the arrangement order.
[0326] In one embodiment, for any one of the second candidate sets 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 two devices are included: the arrangement order of the two devices obtained according to the above-mentioned sorting method (based on the number of business turnovers) is consistent, then the two devices can be sorted according to the number of business turnovers of the devices, and the device with a larger number of business turnovers 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 turnovers of the devices, then the two devices are directly sorted according to the number of business turnovers 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 turnovers is used first, and the sorting method based on the number of business turnovers of the devices is used secondly.
[0327] 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.
[0328] The order of S304 and S305 is not limited.
[0329] In some examples, Fig.15 for Fig.13 In the implementation process of S103, the m device identifiers in S103 are Fig.15 The device identifiers of the candidate devices in the sorted second candidate set.
[0330] exist Fig.15 In the method shown, the candidate devices that can be used as source devices for business flow can be sorted in combination with the device priority set based on the business operation status of the candidate devices, as well as the user's usage information such as the number of business flows of the device and the number of business flows. The sorted candidate devices can be provided to users for viewing, and intelligent recommendations that are in line with the user's actual experience are provided. In this way, users no longer need to view a large number of devices in distributed scenarios one by one to select the required source device, which reduces the time and energy spent by users on selecting source devices, further facilitates user use, and improves user experience.
[0331] 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 of a specific device). The main device among the 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 the implementation 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 interact with each other. The specific determination method of the main device is not limited in this application.
[0332] The methods provided in the embodiments of the present application may be implemented in whole or in part by 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 process or function described in the embodiments of the present application is generated in whole or in part.
[0333] 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, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.
Claims
1. A business flow method, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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 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, It is 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, It is 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, It is 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, It is 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
Cited By
Connection method between devices, electronic device, computer readable medium and program product
CN120475551A
