Application circulation method and electronic device

Abstract

The present application provides an application flow method and an electronic device, the method comprising: the electronic device displays a first flow interface and realizes the application interface following hand effect in response to receiving a three-finger swipe-up operation of the user on the application interface. After the electronic device detects that the application interface slides a specified distance, the second flow interface is displayed, and the second flow interface provides the user with an electronic device icon to be transferred, and the user can select the target device by dragging the application icon. The electronic device transfers the application to the target device based on the user operation. The present application provides a simple and convenient application flow triggering method, and the user can realize the flow of the application through simple operations.

Description

[0001] This application is a divisional application. The application number of the original application is 202211465509.4, and the original application date is November 22, 2022. The entire contents of the original application are incorporated into this application by reference. Technical Field

[0002] The present application relates to the field of terminals, and in particular to an application circulation method and an electronic device. Background Art

[0003] With the development of terminal technology, terminal applications are becoming more and more abundant, and the usage scenarios are becoming more and more extensive. Currently, when a user uses an application on a single device, if the user needs to switch devices to continue using the application, the user needs to download and start the application on another terminal. During the startup process, operations such as logging in to the application are also required so that the application can obtain the user's historical data so that the application can continue to be used on the terminal. However, this method requires manually restoring the previous application usage status through historical records, which is cumbersome and time-consuming, affecting the user experience. Summary of the invention

[0004] This application provides an application circulation method, which is convenient to operate and takes less time, thereby improving the user experience.

[0005] In a first aspect, the present application provides an application flow method. The method includes: the electronic device responds to a received three-finger swipe operation on a first application interface, and detects whether the moving speed of the three-finger swipe operation is greater than or equal to a first threshold. Wherein, the first application content of the first application is displayed on the first application interface. The electronic device detects that the moving speed of the three-finger swipe operation is less than the first threshold, moves the first application interface following the three-finger swipe operation, and gradually reduces the first application interface as the sliding distance of the three-finger swipe operation increases; and displays the first flow interface. Wherein, the first flow interface is lined with the lower layer of the first application interface; when the sliding distance of the three-finger swipe operation is greater than or equal to the second threshold, the electronic device displays the second flow interface. Wherein, the second flow interface includes a first application icon, an electronic device icon, and an icon of at least one other electronic device. The electronic device moves the first application icon in response to the received drag operation on the first application icon. The electronic device detects that the first application icon moves to the icon of the target device, and flows the first application to the target device, so that the target device displays the first application interface, and the first application interface continues to display the first application content on the target device. In this way, the present application can trigger the application flow function through a specific gesture, and realize the animation effect of starting the application flow function. In addition, the present application can trigger the application flow function through simple operations, effectively reducing the operation time, thereby improving the user experience.

[0006] Exemplarily, the first flow interface is the flow transition interface in this application. The second flow interface is the task flow interface in this application.

[0007] In a possible implementation, the electronic device detects whether the moving speed of the three-finger swipe operation is greater than or equal to a first threshold in response to a received three-finger swipe operation on a first application interface, including: the electronic device determines to trigger the application flow function in response to the received three-finger swipe operation on the first application interface; the electronic device draws the first flow interface, and the electronic device draws the second flow interface, and the electronic device detects whether the moving speed of the three-finger swipe operation is greater than or equal to the first threshold. In this way, the electronic device can determine the corresponding function to be activated based on a specific gesture. For example, in this application, the function corresponding to the three-finger swipe finger is the application flow function. The electronic device can start the application flow process after recognizing the three-finger swipe gesture. In addition, in this application, the electronic device can determine whether to adopt the application interface follow-up method based on the sliding speed of the three-finger slide. In one example, if the three-finger sliding speed is less than the threshold, the application interface follow-up display method can be executed. In another example, if the three-finger sliding speed is greater than or equal to the threshold, the automatic transformation method of the application interface can be executed.

[0008] In a possible implementation, the electronic device detects that the moving speed of the three-finger swipe-up operation is less than a first threshold, moves the first application interface following the three-finger swipe-up operation, and gradually shrinks the first application interface as the swipe-up distance of the three-finger swipe-up operation increases, including: the electronic device determines the position of the first application icon in the second flow interface based on the three-finger swipe-up operation. In this way, in the process of implementing the application interface following the hand, the second flow interface can be synchronously drawn, so that when the display conditions of the second flow interface are met, the second flow interface is called, thereby preventing the interface from freezing.

[0009] In a possible implementation, when the sliding distance of the three-finger swipe-up operation is greater than or equal to the second threshold, the electronic device displays the second flow interface, including: the electronic device detects that the sliding distance of the three-finger swipe-up operation is greater than or equal to the second threshold, determines that the display conditions of the second flow interface are met, and displays the latest drawn second flow interface; wherein the first position of the first application icon in the latest drawn second flow interface corresponds to the current touch position of the three-finger swipe-up operation. In this way, the present application updates the position of the application icon in the second flow interface at any time based on the gesture position, so that when the second flow interface is displayed, the application icon appears at the touch position of the gesture, so as to achieve the display continuity between the application interface and the application icon when switching between the first flow interface and the second flow interface, thereby improving the user experience.

[0010] In a possible implementation, the drag operation and the three-finger swipe operation are non-continuous operations, and when the swipe distance of the three-finger swipe operation is greater than or equal to the second threshold, the electronic device displays the second flow interface, including: after the electronic device displays the second flow interface, it detects a hand-raising operation, and absorbs the first application icon from the first position to a preset position on the second flow interface; wherein the preset position is within the preset range of the electronic device icon. In this way, the present application also provides a two-stage triggering method, that is, after the user swipes three fingers to trigger the second flow interface, he can raise his hand and then drag the application icon to select the target device.

[0011] In a possible implementation, the drag operation and the three-finger swipe up operation are continuous operations, and the user does not lift his hand between the drag operation and the three-finger swipe up operation.

[0012] In a possible implementation, when the sliding distance of the three-finger sliding operation is greater than or equal to the second threshold, the electronic device displays the second flow interface, including: the electronic device displays the second flow interface according to the preset animation. In this way, the present application can enrich the effect of the second flow interface entering the scene by setting the preset animation, and improve the user experience.

[0013] In a possible implementation, when the sliding distance of the three-finger sliding operation is greater than or equal to the second threshold, the electronic device displays the second flow interface, including: the electronic device cancels display of the first flow interface. Optionally, the electronic device may hide the first flow interface.

[0014] In a possible implementation, before the electronic device responds to receiving the three-finger swipe-up operation, the first application interface is displayed in full screen on the display screen of the electronic device. Optionally, the first application interface can also be displayed in a floating window or split screen.

[0015] In a possible implementation, the first application interface is moved following the three-finger swipe up operation, and the first application interface is gradually reduced as the swipe up distance of the three-finger swipe up operation increases, including: the four sides of the first application interface are proportionally reduced. In this way, the first application interface can follow the user's gesture and be proportionally reduced until it is reduced to a preset size, such as a capsule size. Then it is converted from the capsule size to an application icon to enhance the animation display effect and further improve the user experience.

[0016] In a second aspect, the present application provides an electronic device. The electronic device includes one or more processors, a memory; and one or more computer programs, wherein the one or more computer programs are stored in the memory, and when the computer programs are executed by the one or more processors, the electronic device performs the following steps: in response to a received three-finger swipe-up operation on a first application interface, detecting whether the moving speed of the three-finger swipe-up operation is greater than or equal to a first threshold; wherein the first application content of the first application is displayed on the first application interface; when it is detected that the moving speed of the three-finger swipe-up operation is less than the first threshold, the first application interface is moved following the three-finger swipe-up operation, and as the swipe distance of the three-finger swipe-up operation increases, the first application interface moves. The first application interface is enlarged and gradually reduced; and the first flow interface is displayed; wherein the first flow interface is arranged under the first application interface; when the sliding distance of the three-finger sliding operation is greater than or equal to the second threshold, the second flow interface is displayed; wherein the second flow interface includes the first application icon, the electronic device icon and the icon of at least one other electronic device; in response to receiving a drag operation on the first application icon, the first application icon is moved; upon detecting that the first application icon moves to the icon of the target device, the first application is transferred to the target device, so that the target device displays the first application interface, and the first application interface continues to display the first application content on the target device.

[0017] In one possible implementation, when the computer program is executed by the one or more processors, the electronic device performs the following steps: in response to a three-finger swipe-up operation received on a first application interface, determining that an application flow function is triggered; drawing a first flow interface, and the electronic device draws a second flow interface, and the electronic device detects whether the moving speed of the three-finger swipe-up operation is greater than or equal to a first threshold.

[0018] In a possible implementation, when the computer program is executed by the one or more processors, the electronic device performs the following steps: based on a three-finger swipe-up operation, determining a position of the first application icon in the second flow interface.

[0019] In one possible implementation, when the computer program is executed by the one or more processors, the electronic device performs the following steps: detecting that the swipe distance of the three-finger swipe operation is greater than or equal to a second threshold, determining that the display conditions of the second flow interface are met, and displaying the latest drawn second flow interface; wherein the first position of the first application icon in the latest drawn second flow interface corresponds to the current touch position of the three-finger swipe operation.

[0020] In one possible implementation, when the computer program is executed by the one or more processors, the electronic device performs the following steps: after displaying the second flow interface, detecting a hand-raising operation, and adsorbing the first application icon from the first position to a preset position on the second flow interface; wherein the preset position is within a preset range of the electronic device icon.

[0021] In a possible implementation, the drag operation and the three-finger swipe up operation are continuous operations, and the user does not lift his hand between the drag operation and the three-finger swipe up operation.

[0022] In a possible implementation, when the computer program is executed by the one or more processors, the electronic device executes the following steps: displaying a second flow interface according to a preset animation.

[0023] In a possible implementation, when the computer program is executed by the one or more processors, the electronic device executes the following steps: canceling the display of the first flow interface.

[0024] In one possible implementation, when the computer program is executed by the one or more processors, the electronic device performs the following steps: before responding to receiving a three-finger swipe-up operation, the first application interface is displayed in full screen on the display screen of the electronic device.

[0025] In a possible implementation, when the computer program is executed by the one or more processors, the electronic device executes the following steps: four sides of the first application interface are reduced in equal proportion.

[0026] In a third aspect, an embodiment of the present application provides a computer-readable medium for storing a computer program, wherein the computer program includes instructions for executing the method in the first aspect or any possible implementation of the first aspect.

[0027] In a fourth aspect, an embodiment of the present application provides a computer program, which includes instructions for executing the method in the first aspect or any possible implementation of the first aspect.

[0028] In a fifth aspect, an embodiment of the present application provides a chip, the chip comprising a processing circuit and a transceiver pin, wherein the transceiver pin and the processing circuit communicate with each other through an internal connection path, and the processing circuit executes the method in the first aspect or any possible implementation of the first aspect to control the receiving pin to receive a signal and control the sending pin to send a signal. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1 is a schematic diagram of an exemplary hardware structure of an electronic device;

[0030] Figure 2 is a schematic diagram of an exemplary electronic device software structure;

[0031] Figure 3 A schematic diagram showing an exemplary effect;

[0032] Figure 4 The figure is a flowchart of an exemplary application flow method;

[0033] Figure 5 The figure is a flowchart showing an exemplary triggering task flow function;

[0034] Figure 6 is a schematic diagram of module interaction shown as an example;

[0035] Figure 7 A schematic diagram of an exemplary user interface;

[0036] Figure 8 A schematic diagram of an exemplary user interface;

[0037] Fig. 9 A schematic diagram of an exemplary user interface;

[0038] Fig.10 The task flow interface is shown as an example.

[0039] Fig.11 This is a schematic diagram of an exemplary process of obtaining control authority for a foreground application interface;

[0040] Fig.12 This is a schematic diagram of an exemplary process of obtaining control authority for a foreground application interface;

[0041] Fig.13 The figure is a flowchart of an exemplary application flow method;

[0042] Fig.14 The task flow interface interruption process diagram is shown as an example;

[0043] Fig.15 A schematic diagram of an exemplary user interface;

[0044] Fig.16 The following is a flowchart of the task transfer method in this embodiment;

[0045] Fig.17 The following is a schematic diagram showing the interface changes during the task transfer process on a mobile phone;

[0046] Fig.18 This is an exemplary diagram of a process of a mobile phone recognizing a first gesture;

[0047] Fig.19 Schematic diagram of the structure of the device shown as an example. DETAILED DESCRIPTION

[0048] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0049] The term "and / or" in this article is merely a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone.

[0050] The terms "first" and "second" in the description and claims of the embodiments of the present application are used to distinguish different objects rather than to describe a specific order of objects. For example, a first target object and a second target object are used to distinguish different target objects rather than to describe a specific order of target objects.

[0051] In the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

[0052] In the description of the embodiments of the present application, unless otherwise specified, the meaning of "multiple" refers to two or more than two. For example, multiple processing units refer to two or more processing units; multiple systems refer to two or more systems.

[0053] Figure 1 1 shows a schematic diagram of the structure of the electronic device 100. It should be understood that Figure 1 The illustrated electronic device 100 is merely one example of an electronic device, and the electronic device 100 may have more or fewer components than those shown in the figure, may combine two or more components, or may have a different configuration of components. Figure 1The various components shown in can be implemented in hardware, software, or a combination of hardware and software including one or more signal processing and / or application-specific integrated circuits. In the embodiments of this application, only the application flow between a mobile phone and a tablet is used as an example for explanation. In other embodiments, the application flow method in the embodiments of this application can also be applied to any device such as a mobile phone, a smart wearable device, a smart home device, a car device, a tablet, a computer, etc., and this application does not limit it.

[0054] The electronic device 100 may include: a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, 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, a gyroscope sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, etc.

[0055] 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 memory, 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.

[0056] The controller may be the nerve center and command center of the electronic device 100. The controller may generate an operation control signal according to the instruction operation code and the timing signal to complete the control of fetching and executing instructions.

[0057] The processor 110 may also be provided with a memory for storing instructions and data. In some embodiments, 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.

[0058] 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 embodiments, the charging management module 140 may receive charging input from a wired charger through the USB interface 130. In some wireless charging embodiments, the charging management module 140 may receive wireless charging input through a wireless charging coil of the electronic device 100. While the charging management module 140 is charging the battery 142, it may also power the electronic device through the power management module 141.

[0059] 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 external memory, 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 some other embodiments, the power management module 141 can also be set in the processor 110. In other embodiments, the power management module 141 and the charging management module 140 can also be set in the same device.

[0060] The wireless communication function of the electronic 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.

[0061] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic 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 antennas. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In some other embodiments, the antenna can be used in combination with a tuning switch.

[0062] The mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G, etc., applied to the electronic device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a 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 some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the processor 110. In some embodiments, 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.

[0063] 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 electronic 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.

[0064] In some embodiments, antenna 1 of electronic device 100 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, so that electronic device 100 can communicate with the network and other devices through wireless communication technology.

[0065] The electronic 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.

[0066] The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. In some embodiments, the electronic device 100 may include 1 or N display screens 194, where N is a positive integer greater than 1.

[0067] The electronic device 100 can realize the shooting function through ISP, camera 193, video codec, GPU, display screen 194 and application processor.

[0068] The camera 193 is used to capture still images or videos. The object generates an optical image through the lens and projects it onto the photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, and then passes the electrical signal to the ISP to be converted into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV or other format. In some embodiments, the electronic device 100 may include 1 or N cameras 193, where N is a positive integer greater than 1.

[0069] The internal memory 121 can be used to store computer executable program codes, which include instructions. The processor 110 executes various functional applications and data processing of the electronic device 100 by running the instructions stored in the internal memory 121. 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, an image playback function, etc.), etc. The data storage area may store data created during the use of the electronic device 100 (such as audio data, a phone book, etc.), 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, a universal flash storage (UFS), etc.

[0070] The electronic device 100 can implement audio functions such as music playing and recording through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone jack 170D, and the application processor.

[0071] The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals. The audio module 170 can also be used to encode and decode audio signals. In some embodiments, the audio module 170 can be arranged in the processor 110, or some functional modules of the audio module 170 can be arranged in the processor 110.

[0072] The speaker 170A, also called a "speaker", is used to convert an audio electrical signal into a sound signal. The electronic device 100 can listen to music or listen to a hands-free call through the speaker 170A.

[0073] The receiver 170B, also called a "earpiece", is used to convert audio electrical signals into sound signals. When the electronic device 100 receives a call or voice message, the voice can be received by placing the receiver 170B close to the human ear.

[0074] Microphone 170C, also called "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or sending a voice message, the user can speak by putting their mouth close to microphone 170C to input the sound signal into microphone 170C. The electronic device 100 can be provided with at least one microphone 170C. In other embodiments, the electronic device 100 can be provided with two microphones 170C, which can not only collect sound signals but also realize noise reduction function. In other embodiments, the electronic device 100 can also be provided with three, four or more microphones 170C to collect sound signals, reduce noise, identify the sound source, realize directional recording function, etc.

[0075] The earphone interface 170D is used to connect a wired earphone and can be a USB interface 130 or a 3.5 mm open mobile terminal platform (OMTP) standard interface or a cellular telecommunications industry association of the USA (CTIA) standard interface.

[0076] The touch sensor is also called a "touch panel". The touch sensor can be arranged on the display screen 194, and the touch sensor and the display screen 194 form a touch screen, also called a "touch screen". The touch sensor is used to detect touch operations acting on or near it. The touch sensor can pass the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen 194. In other embodiments, the touch sensor can also be arranged on the surface of the electronic device 100, which is different from the position of the display screen 194.

[0077] The key 190 includes a power key, a volume key, etc. The key 190 may be a mechanical key or a touch key. The electronic device 100 may receive key input and generate key signal input related to user settings and function control of the electronic device 100.

[0078] Motor 191 can generate vibration prompts. Motor 191 can be used for incoming call vibration prompts, and can also be used for touch vibration feedback. Indicator 192 can be an indicator light, which can be used to indicate charging status, power changes, messages, missed calls, notifications, etc.

[0079] The SIM card interface 195 is used to connect a SIM card.

[0080] The software system of the electronic device 100 may adopt a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. The embodiment of the present application takes the Android system of the layered architecture as an example to exemplify the software structure of the electronic device 100.

[0081] Figure 2 It is a software structure block diagram of the electronic device 100 according to an embodiment of the present application.

[0082] The layered architecture of the electronic device 100 divides the software into several layers, each layer has a clear role and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into an application layer, an application framework layer, and a kernel layer from top to bottom.

[0083] Exemplarily, the application layer may include a series of application packages.

[0084] like Figure 2 As shown, the application package may include applications such as video, control center, desktop (Launcher), settings, etc.

[0085] The application framework layer provides an application programming interface (API) and a programming framework for the applications in the application layer. The application framework layer includes some predefined functions.

[0086] like Figure 2 As shown, the application framework layer may include a window manager (Window Manager), a view system, a resource manager, a notification manager, an input manager (Input Manager), an activity manager (Activity Manager), etc.

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

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

[0089] The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, and so on.

[0090] 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. For example, the notification manager is used to notify download completion, message reminders, etc. The notification manager can also be a notification that appears in the system top status bar in the form of a chart 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, a text message is displayed in the status bar, a prompt sound is emitted, an electronic device vibrates, an indicator light flashes, etc.

[0091] The Activity Manager provides Android with system services for managing the running state of Activities, as well as for managing the running state of other components in Android. In addition, the Activity Manager can also be used to manage the life cycle of the display. It determines how to control its logical display according to the currently connected physical display device and / or virtual display device, and sends notifications to the system and applications when the state changes.

[0092] The input manager is used to manage the input part of the entire system, including keyboard, mouse, touch screen, etc.

[0093] The kernel layer is the layer between hardware and software. The kernel layer includes at least display driver, camera driver, audio driver, sensor driver, Wi-Fi driver, etc.

[0094] Understandably, Figure 2 The layers in the software structure shown and the components included in each layer do not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may include more or fewer layers than shown, and each layer may include more or fewer components, which is not limited in the present application.

[0095] The embodiment of the present application provides an application transfer method. In this method, a user can transfer an application running on a first terminal to a second terminal by performing a simple operation on the first terminal. The user can continue to use the application through the second terminal without having to perform processes such as downloading or manual startup, thereby providing an application transfer method that is easy to operate and takes less time, thereby improving the user experience.

[0096] Figure 3 This is a schematic diagram showing an exemplary effect. Figure 3 , the user uses the video application on the mobile phone. That is, the video application runs in the foreground of the mobile phone. The user can trigger the application flow (also known as application task flow) function in the embodiment of the present application to transfer the video application running on the mobile phone to the tablet to continue running. Please refer to Figure 3 , exemplarily, after the application flow is completed, the video application is displayed on the display interface of the tablet, and the data of the video application displayed by the tablet is synchronized with the mobile phone. For example, before the application flow is performed on the mobile phone, the video application is playing the 7th episode of a TV series. After the video application on the mobile phone is transferred to the tablet, the video application displayed on the tablet also displays the screen of the 7th episode of a TV series. In this way, in the embodiment of the present application, the tablet side can automatically restore the historical data of the video application on the mobile phone side to run the video application without manually downloading and starting the video application. It should be noted that in the embodiment of the present application, only the application flow scenario of the video application is used as an example for explanation. In other embodiments, the application flow method in the embodiment of the present application can also be applied to the flow of other applications, and this application will no longer give examples one by one.

[0097] Figure 4 This is a flowchart of an exemplary application flow method. Figure 4 The application transfer method in the embodiment of the present application includes but is not limited to the following steps:

[0098] Phase 1: Triggering the task transfer function.

[0099] For example, Figure 3 For example, a video application is running on the mobile phone, for example, the 7th episode of a TV series is being played. The user triggers the task flow function by a preset gesture. It should be noted that the task flow in the embodiments of the present application can be replaced by application task flow, application flow, etc., and this application does not limit it.

[0100] In an embodiment of the present application, the preset gesture for triggering the task flow function may be a three-finger upward swipe, that is, the user may touch the display screen with three fingers and swipe upward from the bottom of the display screen to trigger the task flow function.

[0101] It should be noted that in the embodiment of the present application, the user swipes upward with three fingers to trigger the task flow function as an example. In other embodiments, the task flow function can be triggered by other gestures, such as circling with three fingers, double-clicking the screen with two fingers, or a preset air gesture, which is not limited in the present application.

[0102] Phase 2: Display the task flow interface.

[0103] Exemplarily, the mobile phone responds to the received user operation and determines that the user operation is a preset gesture corresponding to the task flow function, then starts the task flow function. Correspondingly, the mobile phone can display the task flow interface. In an embodiment of the present application, the display of the task flow interface can be further divided into two processes: flow transition interface display and task flow interface display. In the flow transition interface display process, the mobile phone can display the flow transition interface, and in the transition flow interface, the window of the video application (also referred to as the video application interface) moves and changes size according to preset rules. For example, the video application interface can move and change size with user operations. For another example, the video application interface can automatically change according to a preset trajectory and size change method. Specific embodiments will be described in detail in the embodiments below.

[0104] For example, during the display of the flow transition interface, if the mobile phone detects that the display conditions of the task flow interface are met, the mobile phone may display the task flow interface. Specific embodiments will be described in detail below.

[0105] Stage 3: In the task flow interface, select the target device.

[0106] Exemplarily, the mobile phone displays a task transfer interface, which includes but is not limited to an icon of a video application and at least one terminal icon. Exemplarily, the terminal corresponding to the at least one terminal icon can be called a transferable terminal, that is, a terminal that supports application transfer. For example, the terminal can be a terminal with the same account as the local device, such as a tablet, wearable device, smart home device, car-mounted device, etc., which is not limited in this application.

[0107] Exemplarily, the user can select any terminal device as the target device for application flow in the task flow interface.

[0108] Phase 4: Execution of task flow.

[0109] Exemplarily, the mobile phone determines the target device (e.g., tablet) to be streamed in response to the received user operation. The mobile phone can establish a communication connection with the target device to be streamed, and transmit the relevant data of the video application to the tablet. The tablet can display the video application on the interface, and the interface of the video application displayed by the tablet is the interface displayed by the video application before the mobile phone executes the streaming, such as the 7th episode of a TV series.

[0110] The following is a Figure 4 Each process in is described in detail.

[0111] Phase 1: Triggering the task transfer function.

[0112] Figure 5 This is a flowchart showing an exemplary triggering task flow function. Figure 5 , including but not limited to the following steps:

[0113] S501, Launcher sends a gesture event monitoring registration request to Input Manager.

[0114] For example, after the mobile phone is started, the Launcher in the mobile phone sends a request to register gesture event monitoring to the Input Manager. The request is used to register gesture monitoring with the Input Manager. It can be understood that the Launcher expects the Input Manager to feed back the acquired gesture events to the Launcher.

[0115] S502: Input Manager dispatches a gesture event to Launcher.

[0116] Exemplarily, after receiving the registration gesture event monitoring request sent by the Launcher, the Input Manager obtains all gesture events. The way in which the Input Manager obtains gesture events can refer to the existing technical embodiments, and this application does not limit it.

[0117] For example, every time the Input Manager obtains a gesture event, it dispatches the gesture event to the Launcher, which can be understood as sending a gesture event trigger instruction to the Launcher to indicate that there is currently a gesture event acting on the mobile phone screen.

[0118] Figure 6 This is an exemplary diagram of module interaction. Figure 6Exemplarily, the Input Manager includes a gesture event dispatching unit (also referred to as a module or component, which is not limited in this application). Whenever the gesture event dispatching unit obtains a gesture event, it dispatches the gesture event to the gesture recognition component in the Launcher through path 1 to indicate that a gesture event currently exists.

[0119] In the embodiment of the present application, the triggering gesture of the task flow function is a three-finger swipe up as an example for explanation. In other embodiments, it can also be other preset gestures or operations, and this application does not limit it.

[0120] Figure 7 is a schematic diagram of an exemplary user interface. Figure 7 (1), illustratively, a video application interface 702a (also referred to as a video application window or a video application display window, which is not limited in this application) is displayed in the display interface 701 (also referred to as a display window) of the mobile phone. That is, the application running in the foreground of the mobile phone is a video application, for example, the 7th episode of a TV series is being played. The user expects to transfer the video application running on the mobile phone to the tablet side for continued use, that is, to continue playing the 7th episode of the TV series. Exemplarily, the user touches the display interface 701 with three fingers and slides upward from the bottom of the display interface 701 to trigger the task transfer function. When the user touches the display interface 701 with three fingers, the Input Manager can detect the gesture event and dispatch the gesture event to the Launcher.

[0121] It should be noted that the present application embodiment only takes the gesture event of the task flow function as an example for illustration. In fact, in the present application embodiment, the Input Manager detects any gesture event and dispatches the gesture event to the Launcher, and the Launcher detects the corresponding function triggered by the gesture event.

[0122] It should be further noted that the embodiments of the present application are all described by taking the full screen display of the video application interface on the display screen as an example. In other embodiments, the application flow method in the embodiments of the present application can also be applied to the scene where the video application is displayed in a floating window or split screen, and the present application will not illustrate them one by one.

[0123] S503, Launcher recognizes the three-finger swipe-up gesture and obtains the gesture position and distance.

[0124] For example, each time Launcher receives a gesture event dispatched by Input Manager, it identifies the gesture event to determine whether the trigger condition of the corresponding function is met. In the embodiment of the present application, the trigger condition of the task flow function is a three-finger swipe up as an example. Accordingly, Launcher detects whether the current user operation is a three-finger swipe up operation based on the gesture event dispatched by Input Manager.

[0125] Exemplarily, as described above, when the user touches the display screen with three fingers and swipes up, the Input Manager can dispatch a gesture event to the Launcher when the user touches the display screen with three fingers. Based on the received gesture event, the Launcher detects whether the display screen is touched by three fingers. If so, the gesture position and sliding distance can be obtained. In other words, when the Launcher detects the gesture event of the user touching the display screen with three fingers, the task flow function can be triggered, and the second stage can be started.

[0126] Phase 2: Display the task flow interface.

[0127] Fig.10 This is an example of a task flow interface display flow chart. Please refer to Fig.10 In the embodiment of the present application, after the task flow function is started, the Launcher will control the display of related interfaces (also called windows, such as the foreground application interface, the task flow interface, and the flow transition interface), such as the display content, size, and dynamic effects of the control interface. In the prior art, the control of each interface of the mobile phone is in the Window Manager, that is, the Window Manager controls the display mode of each interface, such as size and position.

[0128] like Fig.10 As shown, in the embodiment of the present application, Launcher needs to obtain the control authority of the foreground application interface (such as the video application) and the control authority of the task flow interface before it can execute the subsequent flow transition interface display process and task flow interface display process. For example, please refer to Figure 6 , the Activity Manager can call the Launcher through path 2 to launch the Launcher. And, the Activity Manager can call the Control Center through path 3 to launch the Control Center. After the Launcher and the Control Center are launched, the Launcher and the Window Manager obtain the control authority of the foreground application interface (such as the video application) and the control authority of the task flow interface through path 3.

[0129] It should be noted that in the embodiment of the present application, the process of obtaining the control authority of the foreground application interface (such as the video application) and the process of obtaining the control authority of the task flow interface are executed in parallel. Fig.10 As shown, the mobile phone simultaneously obtains the control authority of the foreground application interface (such as a video application) and obtains the control authority of the task flow interface. After obtaining the control authority of the foreground application interface, the mobile phone can display the flow transition interface. Among them, while the mobile phone is displaying the flow transition interface, the Launcher may have obtained the control authority of the task flow interface, or is still executing the process of obtaining the control authority of the task flow interface, which depends on the execution capability of the mobile phone and is not limited by this application.

[0130] For example, when the mobile phone is displaying the task transition interface, if it is detected that the task transition interface display condition is met and the control authority of the task transition interface has been obtained, the Launcher can display the task transition interface. Specific embodiments will be described in detail below.

[0131] Fig.11 This is a flowchart showing an exemplary method of obtaining control rights for the foreground application interface. Fig.11 , including but not limited to:

[0132] S1101, Launcher sends a request to Activity Manager to start the flow transition interface.

[0133] Exemplarily, after the Launcher determines that the task flow function is triggered, it sends a request to the Activity Manager to apply for starting the flow transition interface, which is used to instruct the Activity Manager that the Launcher will display the flow transition interface. In the embodiment of the present application, during the process of the Launcher displaying the flow transition interface, the Launcher also controls the foreground application interface at the same time. Therefore, when the Launcher displays the flow transition interface, it needs to obtain the control authority of the foreground application interface. Correspondingly, applying for starting the flow transition interface request can also be understood as requesting the Activity Manager for the control authority of the foreground application interface (such as the video application interface).

[0134] Exemplarily, the request may include but is not limited to a registration callback object, wherein the registration callback object is used to indicate that the object of this request callback is the Launcher. Optionally, the registration callback object can be understood as an interface or channel corresponding to the Launcher, and the Activity Manager can call back the Launcher based on the interface or channel indicated by the registration callback object.

[0135] S1102, Activity Manager schedules Launcher to the foreground.

[0136] For example, as described above, the video application is currently running in the foreground of the mobile phone. In response to the received application start flow transition interface request, the Activity Manager moves the Launcher to the foreground to run. For example, the Launcher can be moved to the top of the stack. The specific implementation method can refer to the existing technical embodiments, and this application does not limit it. For example, moving the Launcher to the foreground to run can also be understood as pulling up the Launcher. It should be noted that Figure 5 When the Launcher is performing actions such as recognizing gesture events, the Launcher is running in the background.

[0137] S1103, Launcher draws the flow transition interface.

[0138] Exemplarily, after the Launcher is brought to the foreground, a flow transition interface may be drawn. In the embodiment of the present application, the content in the flow transition interface may be filled with a solid color or other patterns, which may be set according to actual needs and is not limited in the present application.

[0139] In the embodiment of the present application, step S1103 can be executed only once. That is, when the task flow process is executed for the first time after the mobile phone is initialized, the Launcher can draw the flow transition interface. In the subsequent application flow scenario, the Launcher can reuse the already drawn flow transition interface. That is, there is no need to execute S1103, and S1104 can be executed directly.

[0140] S1104, Launcher notifies Window Manager that drawing is complete.

[0141] Exemplarily, after the Launcher completes drawing the flow transition interface, it may send a drawing completion instruction to the Window Manager to notify the Window Manager that the flow transition interface has been drawn.

[0142] S1105, Window Manager generates remote motion effect control parameters.

[0143] Please refer to Figure 6Exemplarily, the Window Manager includes a remote animation unit and a switching control unit. Exemplarily, the remote animation unit generates remote animation control parameters corresponding to the flow transition interface in response to the received drawing completion instruction. In an embodiment of the present application, the remote animation control parameters of the flow transition interface can be understood as encapsulating the flow transition interface drawn by the Launcher into remote animation parameters. Specifically, the Window Manager maintains a window tree, and each window corresponds to a node. The Window Manager generates a new parent node, and the parent node is no longer on the window tree maintained by the WindowManager. The Window Manager hangs the flow transition interface on the newly generated parent node. The parameters corresponding to the parent node are the remote animation parameters of the flow transition interface.

[0144] S1106, Window Manager sends remote motion effect control parameters to Launcher.

[0145] For example, refer to Figure 6 After the remote motion effect unit generates the remote motion effect control parameters, the switching control unit sends the remote motion effect control parameters to the Launcher through path 2 based on the registered callback object to transfer the control authority of the flow transition interface to the Launcher. The Launcher obtains the remote motion effect control parameters, that is, the Launcher obtains the control authority of the flow transition interface. Optionally, there is a data channel between the Window Manager and the Activity Manager, and the WindowManager can obtain the registered callback object from the Activity Manager. The specific interaction method can refer to the existing technical embodiments, and this application does not limit it.

[0146] Fig.12 This is a flowchart showing an exemplary method of obtaining control rights for the foreground application interface. Fig.11 , including but not limited to:

[0147] S1201, Launcher sends a request to Activity Manager to start the task flow interface.

[0148] For example, as described above, Launcher executes Fig.11 During the process shown in the figure, it can be executed simultaneously Fig.12Specifically, Launcher sends a request to Activity Manager to start the task flow interface. The request can be used to request control authority of the task flow interface. Optionally, the request includes but is not limited to: registering a callback object (the concept can be referred to Fig.11 , which will not be repeated here), identification information of the task flow unit, and identification information of the foreground application (such as a video application).

[0149] Exemplarily, the task flow unit is an execution module (or component) in the control center, such as Figure 6 As shown, the task flow unit can be used to perform operations related to the task flow function. Exemplarily, the identification information of the task flow unit can be the package name and Activity name of the task flow unit, etc., which is not limited in this application. The identification information of the foreground application can be the package name of the foreground application, which is not limited in this application.

[0150] S1202, the Activity Manager dispatches the task transfer unit of the control center to the foreground.

[0151] For example, when the Activity Manager receives a request for starting a task flow interface, the Activity Manager can adjust the task flow unit in the control center to the foreground for execution based on the identification information of the task flow unit in the request.

[0152] S1203, the control center draws a task flow interface.

[0153] Exemplarily, after the task flow unit is transferred to the foreground, the task flow interface is drawn. The drawing process of the task flow interface includes but is not limited to: drawing application icons (such as icons of video applications) and other controls (or components) in the task flow interface. The description of the controls will be described in detail below and will not be repeated here.

[0154] S1204, the control center notifies the Window Manager that the drawing is completed.

[0155] Exemplarily, after the control center completes drawing the task flow interface, it may send a drawing completion instruction to the Window Manager to notify the Window Manager that the drawing is completed.

[0156] S1205, Window Manager generates remote motion effect control parameters.

[0157] Exemplarily, the Window Manager generates remote motion effect control parameters corresponding to the task flow interface. For a specific description, please refer to the relevant content of S1105, which will not be repeated here.

[0158] S1206, Window Manager sends remote motion effect control parameters to Launcher.

[0159] For specific details, please refer to the relevant contents of S1106, which will not be repeated here.

[0160] For example, Fig.10 As shown, after the Launcher obtains the control permission of the foreground application, it can execute the process of displaying the flow transition interface and scaling the foreground application interface card.

[0161] Fig.13 This is a flowchart of an exemplary application flow method. Fig.13 , which includes the steps corresponding to Fig.10 There are two process parts in the process, one of which is to display the flow transition interface and zoom the front-end application interface card. The other part is to display the task flow interface. Exemplarily, the process of displaying the flow transition interface and zooming the front-end application interface card includes but is not limited to:

[0162] S1301, Launcher determines whether the finger movement speed reaches a threshold within a preset distance.

[0163] In the embodiment of the present application, the user can quickly slide up from the bottom of the display screen with three fingers (with or without raising the hand) and / or the user slides up from the bottom of the display screen with three fingers for a distance greater than or equal to a threshold (which can be called a distance threshold, which can be set according to actual needs and is not limited in this application) to trigger the mobile phone to display the task flow interface. In other words, the gesture of sliding up a certain distance at a speed less than a preset speed threshold (i.e., the sliding distance reaches the distance threshold) or the gesture of sliding up with three fingers at a speed greater than or equal to the preset speed threshold satisfies the display conditions of the task flow interface.

[0164] The Launcher can slide with three fingers within a preset distance (which can be set according to actual needs and is not limited in this application), and continuously calculate the three-finger sliding speed based on the acquired gesture position and sliding distance. That is to say, within the preset distance of three-finger sliding, the Launcher continuously detects whether the gesture movement speed reaches the threshold. In one example, if within the preset distance of three-finger sliding, it is detected that the three-finger sliding speed is less than the speed threshold, S1302a is executed. In another example, if within the preset distance, it is detected that the three-finger sliding speed is greater than or equal to the speed threshold, S1302b is executed. Exemplarily, during the execution of S1302a, the Launcher still continues to detect the three-finger sliding speed. If within the preset distance of three-finger sliding, the Launcher detects that the three-finger sliding speed is greater than or equal to the speed threshold, S1302b can be executed. If the three-finger sliding distance is greater than the preset distance and the speed threshold has not been reached, there is no need to monitor the three-finger sliding speed, that is, continue to execute according to S1302a.

[0165] It should be noted that, in the embodiment of the present application, the preset distance mentioned above is less than the distance threshold. The preset distance is usually set to a very short distance.

[0166] In an embodiment of the present application, while the user is swiping upward with three fingers, the mobile phone can display a flow transition interface, and the foreground application interface card (such as a video application) can follow the user's finger sliding and change size, or move and change size according to a preset animation to transition the display of the task flow interface, thereby avoiding problems such as screen freezes caused by the task flow interface not being drawn completely.

[0167] S1302a, Launcher controls the foreground application interface card to scale with the hand according to the gesture position and sliding distance, and displays the flow transition interface.

[0168] Exemplarily, as described above, the Launcher has obtained the control authority of the flow transition interface, and the Launcher can control the movement trajectory and size change of the foreground application interface card based on the acquired gesture position and sliding distance.

[0169] Please refer to Figure 7 (2), the user swipes upward with three fingers to trigger the task flow function, and after the Launcher obtains the control authority of the flow transition interface, the Launcher can control the video application interface card 702a to move with the user's fingers (i.e., the finger position obtained by the Launcher) based on the sliding trajectory of the user's three fingers. At the same time, as the user's three fingers move upward, the video application interface card 702a gradually shrinks. In this example, the user's three fingers do not leave the display screen. The scenario where the user's three fingers leave the display screen will be described in detail below.

[0170] Optionally, the reduction range of the video application interface card 702a is proportional to the upward sliding distance of the finger. The specific correspondence between the reduction range and the sliding distance can be set according to actual needs, and this application does not limit it.

[0171] Optionally, in the embodiment of the present application, the video application interface card 702a may be reduced in size in equal proportions on the top, bottom, left, and right sides.

[0172] Optionally, if the user slides downward with three fingers while dragging the video application interface card 702a with three fingers, the video application interface card 702a follows the movement of the user's three fingers, which enlarges the video application interface card 702a.

[0173] Still refer to Figure 7 (2), illustratively, the Launcher displays a transition interface 703. The transition interface 703 is stacked below the video application interface card 702a, that is, the level of the transition interface 703 is lower than the video application interface card 702a. illustratively, as the video application interface card 702a moves and shrinks, more of the transition interface 703 is displayed in the display interface 701.

[0174] In an embodiment of the present application, as described above, when the Launcher executes S1302a, it is still detecting whether the three-finger swipe speed reaches the threshold within the preset distance. For example, if the Launcher detects that the three-finger swipe distance has exceeded the preset distance and has not reached the speed threshold during the execution of S1302a, the speed monitoring is canceled, and the application interface card following process of S1302a is continued. At the same time, the Launcher executes S1303. That is to say, after detecting that the three-finger swipe distance has exceeded the preset distance, the Launcher begins to detect whether the three-finger swipe distance has reached the distance threshold. Among them, as described above, the distance threshold is greater than the preset distance.

[0175] S1302b, Launcher controls the foreground application interface card to automatically scale to a capsule size, and displays a flow transition interface.

[0176] Fig. 9 is a schematic diagram of an exemplary user interface. Fig. 9 (1), illustratively, the user quickly slides upward with three fingers from the bottom of the display interface 901. The Launcher determines, based on the gesture position and the sliding distance, that the upward sliding speed of the three fingers exceeds (i.e., is greater than or equal to) a preset speed threshold, and the Launcher displays the flow transition interface, and the Launcher controls the video application interface card 902a to demonstrate the dynamic effect of the flow transition interface according to the preset movement trajectory and size change amplitude.

[0177] Please refer to Fig. 9 (2) and Fig. 9 (3), for example, after the user quickly slides with three fingers and then lifts his hand, the Launcher gradually moves the video application interface card 902a upwards, and gradually shrinks the video application interface card 902a according to the preset reduction amplitude, until the video application interface card 902a slides to the preset position (which can be set according to actual needs and is not limited by this application), and shrinks to the preset size (for example, the specific size of the capsule can be set according to actual needs and is not limited by this application). And the Launcher displays the flow transition interface 903, the display method can refer to Figure 7 The relevant description in will not be repeated here.

[0178] Exemplarily, the Launcher continues to execute S1305 to display the task flow interface.

[0179] In a possible implementation, as described above, the Launcher continuously detects the speed of the three-finger swipe up within a preset distance. Accordingly, the Launcher may detect that the speed of the three-finger swipe up within a preset distance exceeds the speed threshold during the execution of S1302a, that is, the video application interface card moves and shrinks following the three-finger swipe. Then, the Launcher may continue to demonstrate the preset animation effect from the current position and current size of the video application interface card to move the video application interface card to the preset position and shrink it to the preset size (e.g., capsule size).

[0180] In another possible implementation, the preset position described above can be optionally near the local icon in the task flow interface, or overlap with the local icon. That is, when the mobile phone displays the task flow interface, the video application interface card visually changes from a capsule size to an application icon, and the position remains unchanged, that is, it is displayed on or near the local icon in the task flow interface. The specific details will be explained below.

[0181] S1303, Launcher determines whether the finger sliding distance reaches a threshold.

[0182] Exemplarily, when the Launcher displays the flow transition interface and the video application interface card changes with the hand, the Launcher obtains the gesture position and sliding distance in real time to detect whether the distance the user slides upward with three fingers reaches a threshold (which can be set according to actual needs and is not limited in this application).

[0183] For example, Figure 7As shown in (3), the user slides upward on the interface 701 with three fingers, and the video application interface card 702a follows the movement and gradually becomes smaller in size. In other words, the user drags the video application interface card 702a upward by sliding with three fingers. When the Launcher detects that the user's three-finger sliding distance (referring to the height difference between the current position and the starting position) reaches a threshold (for example, h), the Launcher determines that the display condition of the task flow interface is met. That is, the display condition is that the video application interface card is dragged upward by a distance greater than or equal to the threshold. Accordingly, the Launcher executes S1304.

[0184] In another example, if Launcher detects that the three-finger upward sliding distance does not reach the threshold, it continues to execute S1302, that is, the flow transition interface is still displayed, and the video application interface card 702a changes position and size with the three-finger sliding.

[0185] In one possible implementation, if Launcher detects that the user's finger sliding distance does not reach the threshold and the user raises his hand, it executes Fig.14 The task flow in the interrupt process. The specific details will be explained below.

[0186] S1304, Launcher establishes a connection with the control center and sends the finger position.

[0187] S1305, the control center realizes application icon following the finger according to the finger position.

[0188] In the embodiments of the present application, as described above, Fig.11 and Fig.12 The control authority of the foreground application interface and the control authority of the task flow interface are executed synchronously. Therefore, during the process of Launcher executing S1302b and S1303, that is, before the three-finger swipe distance does not reach the distance threshold, it can also be understood that before the display conditions of the task flow interface are met, the control center has already drawn the task flow interface, and the Launcher obtains the control authority of the task flow interface. Correspondingly, after obtaining the task flow interface authority, the Launcher can execute S1304, establish a connection with the control center, and send the obtained finger position (for example, the center point of the three-finger coordinates) to the control center.

[0189] For example, after the control center obtains the finger position, it can control the video application icon to slide on the task flow interface based on the finger position. This animation is invisible to the user. It can be understood that when the Launcher changes the video application interface card on the flow transition interface based on the finger position and sliding distance following the user's three-finger sliding, the control center also determines the position of the video application icon in the task flow interface based on the obtained finger position and draws it. However, since the Launcher has not yet called the task flow interface, the current drawing result of the control center is not displayed on the display interface of the mobile phone.

[0190] S1306, Launcher displays the task flow interface and hides the transition interface.

[0191] like Figure 6 As shown, the transition interface display unit of the Launcher calls the task flow unit of the control center through path 5, wherein the transition interface display unit can be used to execute the relevant steps of the flow transition interface display of the Launcher above. The task flow unit is used to execute the drawing and other steps of the task flow unit. The specific details can be referred to above and will not be repeated here.

[0192] In the embodiment of the present application, the triggering method of the task flow interface is divided into two methods: sliding three fingers upward without raising the hand (the sliding speed is less than the speed threshold) and quickly sliding three fingers upward and raising the hand (the hand can also be raised).

[0193] In one example, for a method of swiping upward with three fingers without lifting the hand to trigger the task flow interface, the user can continue to drag the application interface card using the three-finger drag method without lifting the hand, such as Figure 7 As shown in (3), when the user drags the video application interface upward with three fingers and the distance reaches the distance threshold, the video application interface card 702a has shrunk to the size of a capsule (it can also be other sizes, which are only illustrative examples and are not limited in this application). Figure 7 As shown in (4), the Launcher determines that the task flow interface display condition is met, and the Launcher displays the task flow interface 704. In this example, the user has not raised his hand.

[0194] For example, Figure 7 As shown in (4), the task flow interface 704 includes but is not limited to: a video application icon 702b, a local icon 705a and other device icons, such as X's TV icon 705b, X's Pad icon 705c, etc.

[0195] It should be noted that, as described above, before executing S1306, the control center has completed the drawing of the task flow interface, and determined the position of the application icon 702b in the task flow interface based on the finger position. Accordingly, in S1306, it can be understood that the Launcher calls the latest task flow interface currently drawn by the control center, and displays the latest task flow interface in the display interface 701, such as the task flow interface 704, and in the latest drawn task flow interface, the position of the application icon 702b is the same as the user's three-finger touch position. That is, the position of the video application icon 702b in the task flow interface 704 is the same as the position of the video application interface card in Figure 7 That is, when the user drags the video application interface card 702a to a preset distance with three fingers, the video application interface card 702a changes from a capsule size to a video application icon 702b. The video application icon 702b is still at the position touched by the user with three fingers. Figure 7 (5) and Figure 7 As shown in (6), the user can drag the video application icon 702b with three fingers to drag the video application icon 702 to the icon corresponding to the target device (e.g., tablet). In response to the received user operation, the mobile phone performs application transfer, that is, transfers the video application on the mobile phone to the tablet.

[0196] In another example, for the method of swiping upward with three fingers without lifting the hand to trigger the task flow interface, the user can continue to drag the application interface card using the three-finger drag method without lifting the hand, and after the task flow interface is triggered, the user can raise the hand. Figure 8 As shown in (3), when the user drags the video application interface upward with three fingers and the distance reaches the threshold, the video application interface card 802a has shrunk to the size of a capsule (it can also be other sizes, which are only illustrative examples and are not limited in this application). The Launcher detects that the task flow interface display condition is met, that is, the three-finger upward sliding distance (or the distance the application interface card moves upward) reaches the distance threshold, and the Launcher displays the task flow interface 804. Figure 8 As shown in (4), Launcher calls the task flow interface 804 drawn by the control center, where the position of the video application icon 802b on the task flow interface corresponds to the position of the user's three-finger touch. For a detailed description, please refer to Figure 7 , no further details are given here. For example, in this embodiment, after the mobile phone displays the task flow interface, the user can raise his hand. Optionally, after the user raises his hand, the application icon can demonstrate the adsorption effect during the display of the task flow interface. Figure 8 (4) and Figure 8As shown in (5), after the user slides with three fingers and raises his hand, the control center moves the video application icon from the position where the user raises his hand to the preset position of the task flow interface (which can be set according to actual needs and is not limited in this application), for example, near or overlapping the local icon 805a. Figure 7 The difference is that Figure 7 When the application icon is displayed on the task flow interface, its position moves with the user's gesture position. Figure 8 In the example, since the user has raised his hand, the adsorption effect can be demonstrated when the application icon is displayed on the task flow interface.

[0197] For example, Figure 8 (5) and Figure 8 As shown in (6), the user can drag the video application icon 802b with any finger (such as the index finger) to drag the video application icon 802b to the target device (such as a tablet) icon. In response to the received user operation, the mobile phone performs application flow, that is, the video application on the mobile phone is transferred to the tablet. It should be noted that Figure 8 (1) and Figure 8 The execution process of (2) can be referred to Figure 7 (1) and Figure 7 (2), that is, Figure 8 Provides a two-stage task flow triggering method. Users can trigger the task flow function by sliding with three fingers and dragging the video application interface card. Figure 7 The difference is that Figure 8 In the method described in the previous section, after the video application interface card is reduced to a capsule size or becomes an application icon, the user can raise his hand and drag the application icon again with the same or different gesture.

[0198] In another example, a method of quickly sliding upward with three fingers to trigger a task flow interface is as follows: Fig. 9 (1) to Fig. 9 As shown in (3), the user quickly slides up with three fingers, and the mobile phone displays the flow transition interface, and the video application interface card 902a moves with the user's three fingers for a distance (the distance is less than the preset distance mentioned above). The Launcher detects that the speed of the three-finger upward sliding reaches the threshold, and then the Launcher can control the video application interface card 902a to move from the current position to the preset position according to the predetermined trajectory, and shrink to the preset size (for example, the size of a capsule) according to the preset shrinking range. Fig. 9As shown in (4), the Launcher detects that the video application interface card 902a moves to the preset position and shrinks to the preset size, and determines that the task flow interface display condition is met. Accordingly, the Launcher calls the task flow interface drawn by the control center, that is, the task flow interface 904 is displayed in the display interface 901. Among them, the application icon 902b can be Figure 7 , that is, the position of the application icon 902b in the interface 901 is the same as the last position before it becomes an icon, that is, in this example, the application icon 902b is at the preset position of the task flow interface 904. Fig. 9 In the method shown, since the Launcher moves and shrinks the video application interface card according to a predetermined trajectory and size, the Launcher no longer needs to obtain the finger position. Accordingly, the control center does not need to determine the position of the video application icon in the task flow interface based on the finger position. In other words, in the task flow interface drawn by the control center, the video application icon is at a preset position in the task flow interface. In response to the received user operation, the mobile phone executes the application flow, that is, the video application on the mobile phone is transferred to the tablet.

[0199] In a possible implementation, after the mobile phone displays the task flow interface, if the user raises his hand before dragging the video application icon to the vicinity of the target device icon, the control center can respond to the received user hand-raising operation and move the video application icon from the current position (i.e., the hand-raising position) to the preset position along a predetermined trajectory. For example, the preset position can be near the local icon or overlap with the local icon, such as Fig. 9 The position shown in (4) can be set according to actual needs and is not limited in this application.

[0200] In another possible implementation, the Launcher calls the task flow interface drawn by the control center to enter the scene, and the Launcher can call the pre-set entry animation to demonstrate the entry animation when the task flow interface enters the scene. For example, the entry animation can be gradually displayed or flashing, etc., which is not limited in this application.

[0201] In another possible implementation, while the Launcher calls the task flow interface to enter, the Launcher controls the flow transition interface to exit. Optionally, the flow transition interface can exit in a hidden manner, etc., which is not limited in this application.

[0202] In another possible implementation, the mobile phone responds to the received user operation and executes the application flow, that is, after the video application is flowed to the tablet, the Launcher determines that the application flow process is over and can notify the WindowManager to reclaim the remote animation parameters, that is, to reclaim the control authority of the application interface and the task flow interface. For details, please refer to Fig.14 S1404 to S1406 in the above description will not be described in detail here.

[0203] In another possible implementation, the control center detects that the video application icon moves to a preset range of the tablet icon (which can be set according to actual needs and is not limited by this application) and stays there for a preset time (which can be set according to actual needs and is not limited by this application), and can determine that the tablet is the device to be streamed, that is, the target device. In another example, the control center detects that the video application icon moves to a preset range of the tablet icon and the user raises his hand, and can determine that the tablet is the target device.

[0204] Fig.14 This is a diagram showing an example of interrupting the task flow interface. Fig.14 , including but not limited to the following steps:

[0205] S1401, Launcher sends a task transfer end instruction to Activity Manager.

[0206] For example, when the Launcher detects that the user's three-finger sliding distance has not reached the threshold and the three-finger sliding speed has not reached the threshold, and the user raises his hand, the Launcher triggers the task flow interface to display the interruption process, that is, the Launcher sends a task flow end instruction to the Activity Manager to indicate the end of the task flow process.

[0207] For example, in one example, if the user slides three fingers on the interface, where the sliding speed is less than a threshold. During the sliding process, the Launcher displays the flow transition interface and the application interface card follows the hand. If the user wants to cancel the application flow operation, that is, does not want to execute the task flow of the video application anymore, the user raises his hand. Among them, the distance (that is, the height difference) between the user's hand raising (that is, the last touch position) and the starting position of the user's three-finger sliding is less than the threshold, and the Launcher detects that the interruption condition is met. That is, the interruption condition is that the user's three-finger sliding distance does not reach the threshold (for example, the distance threshold) and the three-finger sliding speed is less than the threshold (for example, the speed threshold). Accordingly, the Launcher executes S1401.

[0208] S1402, the Activity Manager ends the task transfer unit of the control center.

[0209] Exemplarily, as described above, in S1202, the Activity Manager brings the task flow unit to the foreground. In this example, the Activity Manager determines that the task flow process is finished in response to the received task flow end instruction, and the Activity Manager ends the task flow unit of the control center, that is, puts the task flow unit of the control center in the background.

[0210] S1403, Launcher plays the animation of the foreground application interface card returning to full screen state.

[0211] For example, Launcher restores the video application interface card to full screen display based on the position and size of the video application interface card when the user raises his hand. For an example, please refer to Fig.15 (1), after the user drags the video application interface card 1502a to the current position with three fingers, the user raises his hand. The Launcher detects that the user has raised his hand, and detects that the three-finger sliding distance has not reached the threshold and the three-finger sliding speed has not reached the threshold, and determines that the task flow interruption condition is met. Accordingly, the Launcher demonstrates the restoration effect of the foreground application interface card. Fig.15 (2) and Fig.15 As shown in (3), Launcher removes the video application interface card 1502a from Fig.15 The position of (1) gradually moves toward the center of the interface 1501, and during the movement, the video application interface card 1502a gradually becomes larger until it is as shown in FIG. Fig.15 As shown in (4), the video application interface card 1502a is restored to full screen display (i.e., the interface card size is the same as the display interface 1501 size). In the embodiment of the present application, in the foreground application interface card restoration animation, the card's motion trajectory and size change range can be set according to actual needs, and this application does not limit it.

[0212] S1404, Launcher notifies Window Manager that the remote animation has ended.

[0213] Exemplarily, after the Launcher restores the video application interface card to full screen display, it sends a remote motion effect end instruction to the WindowManager to indicate the end of the application flow process.

[0214] S1405, Window Manager clears remote animation parameters.

[0215] Exemplarily, in response to the received instruction, the Window Manager determines that the application flow process ends, and the Window Manager reclaims the control authority of the application interface, or the control authority of the application interface and the control authority of the task flow interface. It should be noted that, as described above, the acquisition of the control authority of the application interface and the control authority of the task flow interface are executed in parallel. In some embodiments, before the user swipes up with three fingers and raises his hand, the Launcher may not have obtained the authority of the task flow interface. Therefore, in this example, since the Window Manager has not transferred the authority of the task flow interface, the Window Manager does not need to execute the recovery action of the task flow interface.

[0216] In the embodiment of the present application, as described above, the transfer of control authority of the interface can be understood as encapsulating the interface as remote motion effect parameters and sending the remote motion effect parameters to the Launcher. Correspondingly, in the embodiment of the present application, WindowManager's recovery of control authority of the interface can be understood as clearing the remote control parameters corresponding to the interface that needs to be recovered. For example, the Window Manager can move the video application interface from the newly created parent node to the window tree of the Window Manager, and clear the newly created parent node to reclaim the control authority. The task flow interface is similar and will not be repeated here.

[0217] S1406, Activity Manager ends Launcher.

[0218] Exemplarily, the Activity Manager moves the Launcher to the background for execution.

[0219] The embodiment of the present application also provides a gesture recognition method to recognize the three-finger swipe up operation mentioned above. Fig.16 FIG. 1 is a flowchart of the task transfer method in this embodiment. Fig.16 In the embodiment of the present application, the process of the task flow method may include the following steps:

[0220] S1601. Displaying a first interface of a first application in full screen on a screen of an electronic device, where the first application is an application that supports task flow. Task flow refers to switching a task from a current device to another device for continuation.

[0221] In this embodiment, a mobile phone is taken as an example to illustrate the interface change process of the electronic device during the task flow process.

[0222] Fig.17 This is a schematic diagram showing the interface changes during the task transfer process on a mobile phone. Fig.17 ,exist Fig.17In Figure (a), the screen of the mobile phone displays the interface 1 of the application 1 in full screen. Among them, the application 1 supports task flow.

[0223] S1602: A first gesture is received on a first interface, wherein a process of the first gesture includes a first stage and a second stage which are sequentially connected in time.

[0224] In this embodiment, the first gesture may be a multi-finger touch and a continuous sliding of fingers after the multi-finger touch. Here, the multi-finger touch and the continuous sliding of fingers after the multi-finger touch are performed continuously, that is, the action of lifting all fingers cannot occur between the initial touch and the sliding. If the action of lifting all fingers occurs after the multi-finger touch and before the sliding, the first gesture needs to be re-detected.

[0225] Among them, multi-finger touch and continuous finger sliding after multi-finger touch can be, for example, two-finger touch and continuous finger sliding after two-finger touch, three-finger touch and continuous finger sliding after three-finger touch, or four-finger touch and continuous finger sliding after four-finger touch, and so on.

[0226] Here, three-finger touch is used for explanation.

[0227] Please continue to see Fig.17 ,exist Fig.17 In Figure (b), the user touches the screen with three fingers, namely, finger 1, finger 2, and finger 3, on interface 1. Then at time t0, when interface 1 is displayed in full screen on the mobile phone screen, the mobile phone detects that finger 1, finger 2, and finger 3 touch the screen. In response to detecting that finger 1, finger 2, and finger 3 touch the screen on interface 1, the mobile phone displays the touch point icon of finger 1 at the touch point position of finger 1 on the screen, displays the touch point icon of finger 2 at the touch point position of finger 2 on the screen, and displays the touch point icon of finger 3 at the touch point position of finger 3 on the screen.

[0228] Among them, the touch point icon of finger 1, the touch point icon of finger 2, and the touch point icon of finger 3 are located in the upper layer of the layer where interface 1 is located.

[0229] It should be noted that Fig.17 The touch point icons shown in FIG. (b) are only exemplary, and the present embodiment does not limit the shape of the touch point icons. For example, in other embodiments, the touch point icons may also be in the shape of a square or a triangle.

[0230] It should be noted that time t01 may not be the initial touch time of the three fingers, but a certain time after the three fingers touch the screen. For example, assuming that the initial touch time of finger 1 is time t1, the initial touch time of finger 2 is time t2, and the initial touch time of finger 3 is time t3, t1 is earlier than t2, and t2 is earlier than t3 (subsequent examples are based on this assumption), then time t01 can be time t3 or a time after time t3, provided that the three fingers do not move before time t01 after they fall (i.e. touch the screen).

[0231] In response to detecting that finger 1, finger 2, and finger 3 touch the screen on interface 1, the mobile phone can also obtain the touch point position coordinates of finger 1, finger 2, and finger 3. Assume that the initial touch point position coordinates of finger 1 are point P10 (x10, y10), the initial touch point position coordinates of finger 2 are point P20 (x20, y20), and the initial touch point position coordinates of finger 3 are point P30 (x30, y30). Among them, the x direction is the direction parallel to the short side of the mobile phone frame, and the y direction is the direction parallel to the long side of the mobile phone frame.

[0232] The mobile phone can determine the coordinates (x1, y1) of the center point O1 of finger 1, finger 2 and finger 3 at time t01 according to the coordinates of points P10, P20 and P30.

[0233] In one example, x1 may be equal to an average of x10, x20, and x30, and y1 may be equal to an average of y10, y20, and y30.

[0234] It should be noted that, for ease of description, in this embodiment, the entire process of a complete first gesture is divided into a first stage and a second stage, the first stage is earlier than the second stage, and the end time of the first stage is the same as the start time of the second stage. Among them, the first stage refers to the time period from the time when three fingers start to touch the screen (the start time of the first stage) to the time when the capsule is displayed on the screen (the end time of the first stage), and the second stage refers to the time period from the time when the capsule is displayed on the screen (the start time of the second stage) to the time when all fingers are lifted (the end time of the second stage). Lifting a finger means that the finger leaves the screen and is no longer in contact with the screen.

[0235] S1603. In the first stage, a first animation is displayed on the screen. The first animation is an animation in which a window of the first interface is gradually reduced and transitioned to a first capsule corresponding to the first application according to the progress of the first gesture.

[0236] After the user touches the screen with finger 1, finger 2, and finger 3, they begin to slide along the screen. In this embodiment, it is assumed that the sliding direction is upward. In this embodiment, after finger 1, finger 2, and finger 3 touch the screen, they slide upward along the screen and lift all fingers at time t02. Time t02 is later than time t01.

[0237] In the time period T from time t01 to time t02, the mobile phone detects that a finger is sliding on the screen, and displays touch point icons in real time at the touch point positions of finger 1, finger 2, and finger 3 on interface 1, such as Fig.17 As shown in Figure (c).

[0238] The time period T includes a time period 1 where the first stage of the first gesture is located and a time period 2 where the second stage of the first gesture is located.

[0239] In the time period T, the mobile phone determines the target finger. The target finger is the finger with the earliest initial touch time among the fingers currently touching the screen.

[0240] Method 1 for determining the center point O2 of the target finger and all touching fingers during the sliding process

[0241] If finger 1, finger 2, and finger 3 all touch the screen and do not leave the screen during the process of touching and sliding on the screen, then finger 1 is determined to be the target finger.

[0242] Then, within the time period T, the offset value 1 (offsetX, offsetY) of the finger 1 is determined according to the real-time touch point position of the finger 1.

[0243] Assuming that the real-time touch point position of finger 1 during sliding is P11 (x11, y11), then the offset value 1 (offsetX1, offsetY1) of finger 1 can be determined according to the real-time touch point position P11 (x11, y11) of finger 1 and the initial touch position P10 (x10, y10) of finger 1.

[0244] In one example, offsetX1 is equal to the difference between x11 and x10, and offsetY1 is equal to the difference between y11 and y10.

[0245] After determining the offset value 1 of finger 1, the mobile phone determines the coordinates (x2, y2) of the center point O2 of all touching fingers (including finger 1, finger 2, and finger 3 in this example) during the sliding process based on the coordinates (x1, y1) of the center point O1 and the offset value 1 (offsetX1, offsetY1).

[0246] In one example, x2 is equal to the sum of x1 and offsetX1, and y2 is equal to the sum of y1 and offsetY1.

[0247] If finger 1, finger 2, and finger 3 touch the screen and slide, and finger 2 and finger 3 continue to touch the screen, and finger 1 is lifted at time t4, then the time period T is divided into two parts with time t4 as the dividing point: the first part before time t4 and the second part after time t4.

[0248] In the first part, the target finger and the center point O2 of all touching fingers in the sliding process are determined according to the above-mentioned method 1.

[0249] In the second part, the target finger and the center point O2 of all touching fingers during the sliding process are determined according to the following method 2.

[0250] Method 2 for determining the center point O2 of the target finger and all touching fingers during sliding

[0251] In the time period T after time t4, only finger 2 and finger 3 touch the screen, and finger 1 has been lifted up. At this time, all touching fingers include finger 2 and finger 3.

[0252] Since the initial touch time t2 of finger 2 is earlier than the initial touch time t3 of finger 3, finger 2 is determined to be the target finger.

[0253] Then, the offset value 2 (offsetX2, offsetY2) of the finger 2 may be determined according to the real-time touch point position P21 (x21, y21) of the finger 2 and the initial touch position P20 (x20, y20) of the finger 2.

[0254] In one example, offsetX2 is equal to the difference between x21 and x20, and offsetY2 is equal to the difference between y21 and y20.

[0255] Then, the offset value 2 (offsetX2, offsetY2) is corrected according to the offset value 1 (offsetX1(t5), offsetY1(t5)) of the finger 1 at the end time t5 of the first part.

[0256] In one example, the correction process includes:

[0257] Let beforeoffsetX2 equal to offsetX1(t5), beforeoffsetY2 equal to offsetY1(t5);

[0258] Let adjustX be equal to the difference between beforeoffsetX2 and offsetX2, and adjustY be equal to the difference between beforeoffsetY2 and offsetY2.

[0259] The corrected offset value 2' (offsetX2', offsetY2') of the offset value 2 (offsetX2, offsetY2) is determined according to adjustX, offsetX2, adjustY and offsetY2; wherein offsetX2' is equal to the sum of offsetX2 and adjustX, and offsetY2' is equal to the sum of offsetY2 and adjustY.

[0260] After correcting the offset value of finger 2 and obtaining offset value 2'(offsetX2', offsetY2'), the mobile phone determines the coordinates (x2', y2') of the center point O2' of all touching fingers (including finger 2 and finger 3 in this example) during the sliding process based on the coordinates (x1, y1) of the center point O1 and the offset value 2'(offsetX2', offsetY2').

[0261] In one example, x2' is equal to the sum of x1 and offsetX2', and y2' is equal to the sum of y1 and offsetY2'.

[0262] In this embodiment, when some of the multiple fingers in touch are lifted, the finger with the earliest initial touch time among the fingers still in touch is always used as the target finger, a new offset value is calculated based on the target finger, and the new offset value is corrected. Through the correction, it is ensured that the position of the center point of the multiple fingers calculated based on the corrected offset value is consistent with the position of the center point of the multiple fingers calculated before the fingers are lifted, thereby avoiding the jitter of the animation screen caused by the finger lifting, and improving the user experience.

[0263] In this way, during the operation of the first gesture, this embodiment allows the user to lift one or several fingers, and in this case, the task flow can still be successfully triggered through the first gesture, which reduces the operation difficulty and helps to improve the user experience.

[0264] It should be noted that the offset value only needs to be corrected once each time a finger is lifted. After the correction, the real-time multi-finger center point position in the animation can be determined according to the offset value of the new target finger.

[0265] In one example, if a first ratio of the target offset value to the preset total offset value is equal to a preset ratio threshold, it can be determined that the first stage of the first gesture is completed.

[0266] Among them, the total offset value and the ratio threshold are both preset.

[0267] Here, the method 1 described above is used to determine the target finger and the center point O2 of all touching fingers during the sliding process. The mobile phone detects that finger 1, finger 2, and finger 3 are sliding on the screen. In the first stage, the mobile phone displays animation 1 on the screen. Animation 1 is an animation of gradually shrinking the window of interface 1 according to the progress of the first gesture and transitioning to capsule 1 corresponding to application 1.

[0268] For a frame in animation 1, please refer to Fig.17 Figure (c). Fig.17 In Figure (c), window 1 is the window of interface 1 after it is reduced. The content displayed in window 1 is interface 1. In animation 1, the size of the window of interface 1 is Fig.17 The full screen window shown in (a) is scaled down to Fig.17 (c) The size of window 1 is shown in FIG.

[0269] In one example, the process of displaying animation 1 on the screen may include:

[0270] In animation 1, the center position of window 1 of interface 1 is determined as the second center point O2 (or O2′);

[0271] Determine a first ratio according to the target offset value and a preset total offset value;

[0272] The display size of window 1 of interface 1 in animation 1 is determined according to the initial size, final size and first ratio of window 1 of interface 1 , and the final size of window 1 of interface 1 is equal to the size of capsule 1 .

[0273] The content of window 1 of interface 1 in animation 1 is cropped according to the initial content of window 1 of interface 1 and the first ratio.

[0274] Among them, the total offset value is preset.

[0275] The first ratio may be equal to a quotient obtained by dividing the target offset value by the total offset value.

[0276] The display size of window 1 of interface 1 in animation 1 may be equal to the difference between the initial size of window 1 and the differential size, and the differential size may be equal to the product of the difference between the initial size of window 1 and the final size and the first ratio.

[0277] When the content of window 1 of interface 1 in animation 1 is cropped, the peripheral interface portion of interface 1 may be cropped according to the first ratio.

[0278] In one example, the process of displaying animation 1 on the screen may further include:

[0279] The rounded corners of window 1 of interface 1 in animation 1 are determined according to the initial rounded corners of window 1 of interface 1, the rounded corners of the first capsule, and the first ratio.

[0280] In animation 1 , the rounded corners of window 1 of interface 1 may be equal to the difference between the initial rounded corners of window 1 and the difference rounded corners, and the difference rounded corners may be equal to the product of the difference between the initial rounded corners of window 1 and the rounded corners of the first capsule and the first ratio.

[0281] S1604. In response to the completion of the first stage of the first gesture, the first animation ends, the window of the first interface is released, and the second interface is displayed on the screen, where the second interface includes the first capsule and an alternative destination device icon for the task flow.

[0282] like Fig.17 As shown in Figure (d), at the moment when the first stage of the first gesture is completed, animation 1 ends and is released. Fig.17 Window 1 of interface 1 shown in FIG. (c) displays interface 2 on the screen, and interface 2 includes capsule 1 corresponding to application 1 and an icon of mobile phone B (assuming that the current mobile phone is mobile phone A). Mobile phone B is an alternative destination device for task flow.

[0283] It should be noted that the interface 2 may display icons of multiple candidate destination devices for task transfer, and is not limited to Fig.17 The one shown in Figure (d).

[0284] like Fig.17 As shown in FIG. 5( d ), in this embodiment, the interface 2 may be an interface of a smart interconnection application. The layer where the capsule 1 is located may be located above the layer where the interface of the smart interconnection application is located.

[0285] In this embodiment, the activity manager can generate a window 2 corresponding to the interface of the smart interconnected application at any time after the first gesture starts and before the capsule 1 is displayed on the screen (the content of the window 2 is the interface of the smart interconnected application, and does not include the capsule 1 before the capsule 1 is generated), and set the transparency of the window 2 to 0, so that the window 2 is not displayed before the capsule 1 is displayed on the screen. When the capsule 1 is generated, the mobile phone sets the transparency of the window 2 to the first value (the first value is greater than 0), displays the window 2 on the mobile phone screen, and displays the capsule 1 on the upper layer of the window 2.

[0286] like Fig.17 As shown in FIG. 5( d ) , capsule 1 may include an application icon of application 1 and / or an application name of application 1 (application 1 ).

[0287] S1605. In the second stage, a second animation is displayed on the screen. The second animation is an animation in which the first capsule is controlled to move toward the target device icon according to the progress of the first gesture and disappears when reaching the target device icon. The target device icon is one of the candidate destination device icons.

[0288] like Fig.17 As shown in Figure (d), after the mobile phone screen displays interface 2, the user can continue to slide finger 1, finger 2, and finger 3 on the screen. The mobile phone responds to the continued sliding operation and displays animation 2 on the screen, that is, dragging capsule 1 toward the device icon of mobile phone B and disappearing when it reaches the device icon of mobile phone B.

[0289] It should be noted that, when there are multiple candidate target device icons on the interface 2 , the user can select the target device by dragging the capsule 1 to slide to the target device icon.

[0290] In one example, reaching the target device icon may mean that the capsule 1 partially overlaps with the target device icon.

[0291] In another example, reaching the target device icon may mean that the distance between the center point of the capsule 1 and the center point of the target device icon is less than a preset distance threshold.

[0292] Of course, the “reaching target device icon” may also be defined as other meanings consistent with this embodiment, and this embodiment does not limit this.

[0293] S1606: In response to the second stage of the first gesture being completed, the second animation ends, and the task flow displaying the first interface is transferred to the target device corresponding to the target device icon.

[0294] It should be noted that, for the convenience of description, the interface animation corresponding to the complete first gesture is divided into two animations, Animation 1 and Animation 2. People skilled in the art can understand that Animation 1 and Animation 2 can also be combined into a complete animation. In this case, Animation 1 and Animation 2 can be regarded as components of the complete animation.

[0295] In this embodiment, the mobile phone calls the intelligent interconnection module to complete the flow of display tasks of interface 1. In other embodiments, other applications with task flow functions can also be used to complete the flow of display tasks of interface 1. This embodiment does not limit the specific application of completing task flow.

[0296] Combine the following Figure 2 and Figure 6 The software architecture diagram shown illustrates the process of the mobile phone recognizing the aforementioned three-finger touch and slide (ie, recognizing the first gesture) from the perspective of internal implementation.

[0297] The mobile phone recognizes the first gesture through the Launcher, input manager, window manager, etc. Fig.18 The figure is a diagram showing an exemplary process of a mobile phone recognizing a first gesture. Fig.18 In the example, application 1 is the foreground application. Fig.18, the process of the mobile phone recognizing the first gesture may include:

[0298] S1801. The desktop registers gesture event monitoring with the input manager.

[0299] S1802: The user presses a finger on the screen.

[0300] When the interface 1 of the application 1 is displayed in full screen on the screen, the user presses a finger on the screen.

[0301] S1803: The input manager monitors the operation of a finger pressing on the screen, and dispatches a first gesture event to the desktop.

[0302] The input manager dispatches a first gesture event to a gesture recognition module of the desktop.

[0303] The content of the first gesture event may be finger 1, finger 2, and finger 3 touching the screen.

[0304] S1804: The desktop recognizes that the first gesture event is a three-finger touch, and requests the activity manager to start a foreground window animation. Meanwhile, the desktop also calculates the initial center point positions of the three fingers that are touching.

[0305] This step can be performed by the gesture recognition module of the desktop.

[0306] Here, the foreground window animation can be a complete animation synthesized from the aforementioned animation 1 and animation 2.

[0307] S1805: The activity manager notifies the window manager to prepare foreground window animation.

[0308] S1806. The window manager returns the control right of the foreground task window to the interface control module of the desktop.

[0309] The interface control module uses the control right of the foreground task window to play the foreground window animation on the control screen.

[0310] S1807 . The user moves a finger on interface 1 .

[0311] S1808: The input manager monitors the finger movement and dispatches a second gesture event to the desktop.

[0312] The input manager dispatches the second gesture event to the gesture recognition module of the desktop.

[0313] S1809. The desktop calculates the offset value 1 of finger 1, and calculates the current center point position according to the offset value 1 and the initial center point position.

[0314] S1810: The user lifts finger 1.

[0315] S1811: The input manager detects that finger 1 is lifted, and dispatches a third gesture event to a gesture recognition module on the desktop.

[0316] S1812: If the desktop recognizes that not all three fingers are lifted based on the third gesture event, correct the offset value of finger 2 by 2 to ensure that the current state of the foreground window remains unchanged.

[0317] The current state of the foreground window refers to the current position, size, etc. of the foreground window.

[0318] S1813: The user lifts finger 2 and finger 3.

[0319] S1814: The input manager detects that finger 1 is lifted, and dispatches a fourth gesture event to the gesture recognition module of the desktop.

[0320] S1815: If the desktop recognizes that all three fingers are lifted according to the fourth gesture event, determine whether to return to the initial state of the foreground or enter the task flow process of the smart interconnected application according to the current offset value.

[0321] That is, if the foreground window animation has not yet reached the aforementioned animation 2, and the user lifts all fingers, the desktop interface control module controls interface 1 to return to the initial state of foreground application 1. If the foreground window animation has reached the aforementioned animation 2, the desktop interface control module controls the task flow process of entering the smart interconnected application.

[0322] S1816. The desktop releases control of the foreground task window to the resource manager.

[0323] When it is recognized that all three fingers are lifted up, it means that the first gesture has ended. At this time, the desktop no longer needs to control the animation corresponding to the foreground task window, so the control of the foreground task window can be released.

[0324] In this embodiment, the first gesture is the sum of all gestures corresponding to the first gesture event, the second gesture event, the third gesture event, and the fourth gesture event.

[0325] The above describes the task flow process of the first gesture being completed completely. It should be noted that if the first gesture ends before the first stage of the first gesture is completed, the screen will no longer display the unfinished part of animation 1 after the end time, but the screen at the end time of animation 1 will start to display the reverse animation of the played part of animation 1 until it returns to the initial state of window 1 of interface 1 before displaying animation 1 (the initial state in this example is Fig.17 (a) shows the full screen state).

[0326] It is understandable that, in order to realize the above functions, the electronic device includes hardware and / or software modules corresponding to the execution of each function. In combination with the algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application in combination with the embodiments, but such implementation should not be considered to be beyond the scope of the present application.

[0327] In one example, Fig.16 A schematic block diagram of a device 1600 according to an embodiment of the present application is shown. The device 1600 may include: a processor 1601 and a transceiver / transceiver pin 1602 , and optionally, a memory 1603 .

[0328] The various components of the device 1600 are coupled together via a bus 1604, wherein the bus 1604 includes a power bus, a control bus, and a status signal bus in addition to a data bus. However, for the sake of clarity, various buses are referred to as bus 1604 in the figure.

[0329] Optionally, the memory 1603 may be used for the instructions in the aforementioned method embodiment. The processor 1601 may be used to execute the instructions in the memory 1603, and control the receiving pin to receive a signal, and control the sending pin to send a signal.

[0330] The apparatus 1600 may be the electronic device or a chip of the electronic device in the above method embodiment.

[0331] Among them, all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module, and will not be repeated here.

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

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

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

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

[0336] Through the description of the above implementation methods, technical personnel in the relevant field can understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

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

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

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

[0340] Any content of each embodiment of the present application, as well as any content of the same embodiment, can be freely combined. Any combination of the above content is within the scope of the present application.

[0341] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium, including several instructions to enable a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to perform all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read only memory (ROM), random access memory (RAM), disk or optical disk and other media that can store program code.

[0342] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

[0343] The steps of the method or algorithm described in conjunction with the disclosure of the embodiments of the present application can be implemented in a hardware manner, or can be implemented by a processor executing a software instruction. The software instruction can be composed of corresponding software modules, and the software module can be stored in a random access memory (Random Access Memory, RAM), a flash memory, a read-only memory (Read Only Memory, ROM), an erasable programmable read-only memory (Erasable Programmable ROM, EPROM), an electrically erasable programmable read-only memory (Electrically EPROM, EEPROM), a register, a hard disk, a mobile hard disk, a read-only compact disk (CD-ROM) or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor so that the processor can read information from the storage medium and can write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can be located in an ASIC.

[0344] Those skilled in the art should be aware that in one or more of the above examples, the functions described in the embodiments of the present application can be implemented with hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein the communication media include any media that facilitates the transmission of a computer program from one place to another. The storage medium can be any available medium that a general or special-purpose computer can access.

[0345] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

Claims

1. An application circulation method, characterized in that: include: The electronic device displays a first application interface, wherein the first application content of the first application is displayed on the first application interface; In response to a first swipe-up operation on the first application interface, the first application interface moves following the first swipe-up operation, and the first application interface gradually shrinks into an application card as the swipe-up distance of the first swipe-up operation increases; and, displaying a first flow interface; wherein the first flow interface is arranged at a lower layer of the first application interface; wherein the first swipe-up operation is a three-finger swipe-up operation, and the moving speed of the first swipe-up operation is less than a first threshold; In response to the sliding distance of the first sliding operation reaching a second threshold, a second flow interface is displayed in full screen; wherein the second flow interface includes a first application icon, an electronic device icon, and an icon of at least one other electronic device; wherein the first application icon is in a capsule form, and the second flow interface does not include the application card; In response to a hand-raising operation, adsorbing the first application icon to a preset position on the second flow interface; In response to a drag operation on the first application icon, the first application icon moves to the icon of the target device, and the first application is transferred to the target device, so that the target device displays the first application interface, and the first application interface continues to display the first application content on the target device.

2. The method according to claim 1, characterized in that The method further comprises: After the electronic device displays the first application interface, in response to a second upward sliding operation on the first application interface, the first application interface moves along a preset trajectory and gradually shrinks, and the first flow interface is displayed; wherein the sliding speed of the second upward sliding operation is greater than the first threshold; The first application icon moves to a target position, and the second flow interface is displayed in full screen.

3. The method according to claim 1, characterized in that After the response is applied to the first sliding operation on the first application interface, the method further includes: In response to receiving a first swipe-up operation on the first application interface, determining to trigger an application flow function; The first flow interface is drawn, and the second flow interface is drawn.

4. The method according to claim 3, characterized in that The responding to the first swipe-up operation on the first application interface, wherein the first application interface moves following the first swipe-up operation, includes: Based on the first swipe up operation, a position of the first application icon in the second flow interface is determined.

5. The method according to claim 4, characterized in that The step of displaying a second flow interface in response to the sliding distance of the first sliding operation reaching a second threshold value includes: In response to the swipe up distance of the first swipe up operation reaching a second threshold, it is determined that the display conditions of the second flow interface are met, and the newly drawn second flow interface is displayed; wherein, the first position of the first application icon in the newly drawn second flow interface corresponds to the current touch position of the first swipe up operation.

6. The method according to claim 5, characterized in that The preset position is within a preset range of the electronic device icon.

7. The method according to claim 1, characterized in that The step of displaying a second flow interface in response to the sliding distance of the first sliding operation reaching a second threshold value includes: The second flow interface is displayed according to the preset animation effect.

8. The method according to claim 1, characterized in that The step of displaying a second flow interface in response to the sliding distance of the first sliding operation reaching a second threshold value includes: Cancel displaying the first transfer interface.

9. The method according to claim 1, characterized in that: In response to receiving the first swipe-up operation, the first application interface is displayed in full screen on the display screen.

10. The method according to claim 1, characterized in that The first application interface gradually shrinks as the sliding distance of the first sliding operation increases, including: The four sides of the first application interface are reduced in proportion.

11. An electronic device, characterized in that: include: One or more processors, memory; and one or more computer programs, wherein the one or more computer programs are stored in the memory, and when the computer programs are executed by the one or more processors, the electronic device executes the method according to any one of claims 1 to 10.

12. A computer storage medium, characterized in that: The method comprises computer instructions, and when the computer instructions are executed on an electronic device, the electronic device executes the method according to any one of claims 1 to 10.

Images