Business processing method, device and storage medium

Abstract

The present application provides a business processing method, device and storage medium. The method displays the first interface of a first application on the display screen of a terminal device; when a first waiting node event occurs in the first interface, in the business processing process corresponding to the first waiting node event, in response to the operation acting on the first application, the first application is switched to background operation; in the process of the first application running in the background, a floating ball is displayed on the display screen, and the floating ball displays the business processing progress information corresponding to the first waiting node event and the identification information of the first application where the first waiting node event occurs; in the process of the floating ball being displayed, when an operation acting on the floating ball is received, the first application is switched back to the foreground operation, the first interface of the first application is displayed, and the floating ball is cancelled. Therefore, in the process of the first application being in the background, the user can also accurately know the business processing progress corresponding to the first waiting node event based on the content displayed in the floating ball.

Description

Technical Field

[0001] The present application relates to the field of terminal equipment, and in particular to a service processing method, equipment and storage medium. Background Art

[0002] With the development of intelligent terminal devices, the types of applications (Application, APP) supported on terminal devices are increasing, and the functions are becoming more and more powerful. People can use various APPs installed on terminal devices for work and entertainment.

[0003] However, typically, the terminal device only displays the user interface of the app running in the foreground, while the user interface of the app running in the background is not displayed. As a result, users cannot timely learn the business processing progress of the app running in the background, thus missing important nodes and affecting the user experience. Summary of the Invention

[0004] In order to solve the above technical problems, the present application provides a business processing method, device and storage medium, which aims to enable users to promptly know the business processing progress of applications running in the background, thereby avoiding missing important nodes and improving user experience.

[0005] In the first aspect, the present application provides a business processing method. The method includes: displaying a first interface of a first application on a display screen of a terminal device; when a first waiting node event occurs in the first interface, in the business processing process corresponding to the first waiting node event, in response to the operation acting on the first application, the first application is switched to background operation; wherein, in the business processing process corresponding to the first waiting node event, the first interface only displays the business processing progress information corresponding to the first waiting node event; while the first application is running in the background, a floating ball is displayed on the display screen, and the floating ball displays the business processing progress information corresponding to the first waiting node event and the identification information of the first application where the first waiting node event occurs; during the display of the floating ball, when an operation acting on the floating ball is received, the first application is switched back to the foreground operation, the first interface of the first application is displayed, and the floating ball is canceled.

[0006] For example, the first application may be a gaming application, such as APP1 described below. In a scenario where the first application is a gaming application, the first waiting node event may be, for example, a game character waiting for resurrection event. Accordingly, the first waiting node event may have status information corresponding to different remaining waiting times, such as a waiting for resurrection state within the remaining waiting time and a resurrected state after the remaining waiting time has expired.

[0007] For example, the first application may be a taxi-hailing application, such as APP2 described below. For scenarios where the first application is a taxi-hailing application, the first waiting node event may be, for example, a "waiting for a driver to pick up" event. Accordingly, the first waiting node event may have status information corresponding to different remaining waiting times, such as "waiting for a driver to pick up" within the remaining waiting time and "driver has arrived" after the remaining waiting time has expired.

[0008] Furthermore, during the processing of the business corresponding to the first waiting node event, the first interface only displays the business processing progress information corresponding to the first waiting node event. This means that when the first waiting node event occurs, other operations cannot be performed on the first interface until the first waiting node event is processed. Other operations can only be performed after the first waiting node event is processed. For example, while a game character is waiting to be resurrected, game tasks cannot be performed. Only after the game character is resurrected can the game character be used to perform game tasks.

[0009] Therefore, when the first waiting node event occurs in the first application and switches from the foreground to the background, during the process of processing the business corresponding to the first waiting node event, a floating ball is displayed on the display screen of the terminal device, and the business processing progress information of the first waiting node event of the first application currently running in the background is displayed in the floating ball, and the content displayed in the floating ball is set to change with the processing of the business, so that the user can accurately understand the processing progress of the waiting node event and avoid missing important nodes.

[0010] According to the first aspect, displaying a floating ball on a display screen includes: displaying a floating ball in an expanded state on the display screen, and displaying business processing progress information corresponding to a first waiting node event and identification information of a first application where the first waiting node event occurs on the floating ball in the expanded state; after the floating ball is displayed in an expanded state for a first time period, adjusting the floating ball to a folded state, and displaying identification information of the first application where the first waiting node event occurs on the floating ball in the folded state.

[0011] Therefore, when the first application that triggers the first waiting node event is running in the background, the business processing progress information corresponding to the first waiting node event is displayed in the form of an expanded floating ball on the display screen of the terminal device, and the floating ball is switched from the expanded state to the folded state after displaying the first time length, thereby reducing the obstruction of the current interface content.

[0012] According to the first aspect, or any implementation method of the first aspect above, the business processing progress information includes the remaining waiting time of the first waiting node event and the status information corresponding to the remaining waiting time; after the floating ball is in an expanded state to display the first time, the floating ball is adjusted to a folded state, the method also includes: when the remaining waiting time of the first waiting node event is not greater than the second time, the floating ball is adjusted to an expanded state, and the remaining waiting time of the first waiting node event, the status information corresponding to the remaining waiting time and the identification information of the first application where the first waiting node event occurs are displayed on the expanded floating ball; after the remaining waiting time becomes 0, and / or the status information changes, after the floating ball is in an expanded state to display the third time, the floating ball is adjusted to a folded state, and the identification information of the first application where the first waiting node event occurs is displayed on the folded floating ball.

[0013] Therefore, when the floating ball is in a folded state, when the business processing corresponding to the first waiting node data is about to be completed, or the status is about to change, the floating ball can be set to automatically switch from the folded state to the expanded state at the second time length of the distance change, and the current status information can be displayed in the expanded state, so that the user can know the current status in time when the status changes, so that he can be informed in time and perform corresponding operations.

[0014] In addition, after the remaining waiting time becomes 0 and / or the status information changes, after the floating ball is displayed in the expanded state for the third time, the floating ball is switched from the expanded state to the folded state to reduce the obstruction of the current interface content.

[0015] According to the first aspect, or any implementation of the first aspect above, after the floating ball is displayed in the expanded state for the third time period, the floating ball is adjusted to the folded state, and the method also includes: within the fourth time period when the floating ball is displayed in the folded state, if no operation acting on the floating ball is received, canceling the floating ball.

[0016] Therefore, if the user performs an operation on the floating ball within the fourth time period, the floating ball can be canceled to avoid the thread corresponding to the floating ball from occupying system resources for a long time, thereby reducing the power consumption of the terminal device.

[0017] According to the first aspect, or any implementation method of the first aspect above, during the display of the floating ball, when an operation acting on the floating ball is received, the first application is switched back to the foreground to run, the first interface of the first application is displayed, and the floating ball is canceled, including: during the display of the floating ball in a folded or unfolded state, when an operation acting on the floating ball is received, the first application is switched back to the foreground to run, the first interface of the first application is displayed, and the floating ball is canceled.

[0018] Therefore, there are multiple applications running in the background, and each of them triggers a waiting node event. For example, in the case of the first waiting node event and the second waiting node event, the business processing progress information corresponding to the most recently triggered waiting node event is selected for display, that is, only one floating ball is displayed in the interface of the terminal device, thereby reducing the obstruction of the interface content. At the same time, since only one corresponding thread is responsible for updating the content in the floating ball, multi-thread blocking can be avoided, thereby reducing the power consumption of the terminal device.

[0019] According to the first aspect, or any implementation of the first aspect above, the method also includes: when the first application is running in the background, after displaying a floating ball on the display screen, in response to the operation acting on the second application, the second interface of the second application is displayed on the display screen; when a second waiting node event occurs in the second interface, in the business processing process corresponding to the second waiting node event, in response to the operation acting on the second application, the second application is switched to background operation; wherein, in the business processing process corresponding to the second waiting node event, the second interface is only displayed in the business processing progress information corresponding to the second waiting node event; when the second application is running in the background, the content displayed in the floating ball is adjusted to the business processing progress information corresponding to the second waiting node event and the identification information of the second application where the second waiting node event occurs; when the operation acting on the floating ball is received during the display of the floating ball, the second application is switched back to the foreground operation, the second interface of the second application is displayed, and the floating ball is canceled.

[0020] According to the first aspect, or any implementation method of the first aspect above, the second application is switched back to the foreground to run, the second interface of the second application is displayed, and the floating ball is canceled, including: when the second application is switched to the foreground to run, if the business corresponding to the first waiting node event has not been processed, after the second application is switched back to the foreground to run and the second interface of the second application is displayed, the business processing progress information corresponding to the first waiting node event and the identification information of the first application where the first waiting node event occurred are displayed in the floating ball; if the business corresponding to the first waiting node event has been processed, after the second application is switched back to the foreground to run and the second interface of the second application is displayed, the floating ball is canceled.

[0021] According to the first aspect, or any implementation of the first aspect above, the method further includes:

[0022] When the business corresponding to the first waiting node event has been processed, obtain the time point when the business corresponding to the first waiting node event has been processed; when the time point is not longer than the fourth time point from the current system time point, after switching the second application back to the foreground and displaying the second interface of the second application, display the business processing progress information corresponding to the first waiting node event and the identification information of the first application where the first waiting node event occurred in the floating ball; otherwise, execute the steps of switching the second application back to the foreground, displaying the second interface of the second application, and canceling the floating ball.

[0023] According to the first aspect, or any implementation of the first aspect above, the method also includes: during the process of the first application running in the background, after the floating ball is displayed on the display screen, in response to the operation acting on the second application, the second interface of the second application is displayed on the display screen; when a second waiting node event occurs in the second interface, during the business processing process corresponding to the second waiting node event, in response to the operation acting on the second application, the second application is switched to background operation; wherein, during the business processing process corresponding to the second waiting node event, the second interface only displays the business processing progress information corresponding to the second waiting node event; when the remaining waiting time corresponding to the first waiting node event is not less than the remaining waiting time corresponding to the second waiting node event, during the process of the second application running in the background, the floating ball is displayed on the display screen. The content displayed in the floating ball is adjusted to the business processing progress information corresponding to the second waiting node event and the identification information of the second application where the second waiting node event occurs; during the display of the floating ball, when an operation acting on the floating ball is received, the second application is switched back to the foreground to run, and the second interface of the second application is displayed, and the content displayed in the floating ball is adjusted to display the business processing progress information corresponding to the first waiting node event and the identification information of the first application where the first waiting node event occurs; when the remaining waiting time corresponding to the first waiting node event is less than the remaining waiting time corresponding to the second waiting node event, during the process of the second application running in the background, the floating ball continues to display the business processing progress information corresponding to the first waiting node event and the identification information of the first application where the first waiting node event occurs.

[0024] Therefore, there are multiple applications running in the background, and each of them triggers a waiting node event. For example, in the case of the first waiting node event and the second waiting node event, the business processing progress information corresponding to the waiting node event with the shortest waiting time is selected for display, that is, only one floating ball is displayed in the interface of the terminal device, thereby reducing the obstruction of the interface content. At the same time, since only one corresponding thread is responsible for updating the content in the floating ball, multi-thread blocking can be avoided, thereby reducing the power consumption of the terminal device.

[0025] According to the first aspect, or any implementation method of the first aspect above, after adjusting the content displayed in the floating ball to the business processing progress information corresponding to the second waiting node event and the identification information of the second application where the second waiting node event occurs, the method also includes: when the business corresponding to the second waiting node event has been processed, the floating ball is displayed within the fourth time length, if no operation acting on the floating ball is received, and the remaining waiting time corresponding to the first waiting node event is not 0, or the business corresponding to the first waiting node event has been processed, but the time point of processing is not more than the fourth time length from the current system time, the content displayed in the floating ball is adjusted to the business processing progress information corresponding to the first waiting node event and the identification information of the first application where the first waiting node event occurs.

[0026] According to the first aspect, or any implementation method of the first aspect above, after the floating ball continues to display the business processing progress information corresponding to the first waiting node event and the identification information of the first application where the first waiting node event occurs, the method also includes: when the business corresponding to the first waiting node event has been processed, and the floating ball is displayed within the fourth time length, if no operation acting on the floating ball is received, the business corresponding to the second waiting node event has been processed, but the time point of processing is not more than the fourth time length from the current system time, the content displayed in the floating ball is adjusted to the business processing progress information corresponding to the second waiting node event and the identification information of the second application where the second waiting node event occurs.

[0027] In a second aspect, the present application provides a terminal device. The terminal device includes: a memory and a processor, the memory and the processor being coupled; the memory storing program instructions, which, when executed by the processor, cause the terminal device to execute instructions of the method of the first aspect or any possible implementation of the first aspect.

[0028] The second aspect and any implementation of the second aspect correspond to the first aspect and any implementation of the first aspect, respectively. The technical effects corresponding to the second aspect and any implementation of the second aspect can be referred to the technical effects corresponding to the first aspect and any implementation of the first aspect, and will not be repeated here.

[0029] In a third aspect, 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.

[0030] The third aspect and any implementation of the third aspect correspond to the first aspect and any implementation of the first aspect, respectively. The technical effects corresponding to the third aspect and any implementation of the third aspect can be referred to the technical effects corresponding to the first aspect and any implementation of the first aspect, and will not be repeated here.

[0031] In a fourth aspect, the present application provides a computer program comprising instructions for executing the method in the first aspect or any possible implementation of the first aspect.

[0032] The fourth aspect and any implementation of the fourth aspect correspond to the first aspect and any implementation of the first aspect, respectively. The technical effects corresponding to the fourth aspect and any implementation of the fourth aspect can be referred to the technical effects corresponding to the first aspect and any implementation of the first aspect, and will not be repeated here.

[0033] In a fifth aspect, the present application provides a chip comprising a processing circuit and a transceiver pin. The transceiver pin and the processing circuit communicate with each other via an internal connection path, and the processing circuit executes the method of the first aspect or any possible implementation of the first aspect to control the receive pin to receive a signal and to control the transmit pin to send a signal.

[0034] The fifth aspect and any implementation of the fifth aspect correspond to the first aspect and any implementation of the first aspect, respectively. The technical effects corresponding to the fifth aspect and any implementation of the fifth aspect can be referred to the technical effects corresponding to the first aspect and any implementation of the first aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] Figure 1 This is a schematic diagram of an interface illustrating an exemplary scenario;

[0036] Figure 2 This is a schematic diagram of an interface for another exemplary scenario;

[0037] Figure 3 Schematic diagram of the hardware structure of a terminal device shown as an example;

[0038] Figure 4 A schematic diagram of the software structure of a terminal device is shown as an example;

[0039] Figure 5 This is a schematic diagram of an interface illustrating a scenario implemented based on the business processing method provided in an embodiment of the present application;

[0040] Figure 6This is a schematic diagram of an interface illustrating another scenario implemented based on the business processing method provided in an embodiment of the present application;

[0041] Figure 7 is a schematic diagram of module interaction shown as an example;

[0042] Figure 8 A flowchart illustrating a business processing method provided by an embodiment of the present application;

[0043] Figure 9 This is a schematic diagram of the processing logic of the business processing module when an event fence is triggered;

[0044] Figure 10 This is a schematic diagram of the processing logic of the business processing module when an application switching background event fence is triggered;

[0045] Figure 11 This is a schematic diagram of the processing logic of the business processing module when the fence of the application switching foreground event is triggered;

[0046] Figure 12 This is one of the schematic diagrams of the interface when only one application is in the background;

[0047] Figure 13 This is a second schematic diagram of an interface when only one application is in the background;

[0048] Figure 14 is another schematic diagram of module interaction shown as an example;

[0049] Figure 15 This is another flowchart illustrating a business processing method provided by an embodiment of the present application;

[0050] Figure 16 This is one of the schematic diagrams of the interface when two applications are in the background;

[0051] Figure 17 The second interface diagram is an example of an interface diagram showing two applications running in the background. DETAILED DESCRIPTION

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

[0053] The term "and / or" in this article is merely a description of the association relationship between 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.

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

[0055] In the embodiments of this 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 this application should not be interpreted as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0056] In the description of the embodiments of this application, unless otherwise specified, "multiple" means two or more. For example, "multiple processing units" means two or more processing units; "multiple systems" means two or more systems.

[0057] In order to better understand the technical solutions provided by the embodiments of the present application, before describing the technical solutions of the embodiments of the present application, the applicable scenarios of the embodiments of the present application are first described with reference to the accompanying drawings.

[0058] For example, in the process of a user using an APP installed in a terminal device, there may be a situation where the current service corresponding to the APP is a waiting node event. During the processing of the waiting node event, the user may leave the interface of the APP and go to the interface of other APPs, that is, the APP providing the waiting node event is switched from the foreground to the background. Because under normal circumstances, the interface of the terminal device can only display the user interface of the APP running in the foreground, and the user interface of the APP running in the background is not displayed. Therefore, when the APP providing the waiting node event switches from the foreground to the background, the user cannot promptly know the processing progress of the service corresponding to the waiting node event, and thus cannot accurately understand the status corresponding to the waiting node event, which will cause the user to miss important nodes, thereby affecting the user experience.

[0059] For example, regarding the above-mentioned scenario, for example, a game scenario. For example, there is a type of game APP on the market. When a game character dies during a battle, it will be resurrected somewhere after a period of time so that the player can continue the game. However, as the length of the entire game increases and the number of deaths of the game character increases, the waiting time for the game character to be resurrected will become longer and longer. Figure 1 As shown in (1), when a user plays a game and the game character dies and enters the resurrection waiting state, the waiting node event mentioned above is triggered. Since the business processing progress corresponding to the waiting node event needs to be completed after 44 seconds, that is, the game character can be resurrected after 44 seconds, in order to kill the boring resurrection waiting time, the player may switch out of the game after the game character dies. Figure 1 The interface shown in (1) (hereinafter referred to as the interface of APP1) is used to operate other APPs, such as Figure 1 As shown in (2), the interface of the chat application is switched to (hereinafter referred to as the interface of APP3). Since APP1 is switched to the background, the business processing progress corresponding to the waiting node event (the event of waiting for the game character to be resurrected) is no longer displayed, such as how long it will take for the game character to be resurrected. Therefore, when the player is chatting with friend A in the interface of APP3, he may miss the resurrection moment of the game character in APP1, thereby losing the advantage in the game and affecting the gaming experience.

[0060] For example, regarding the above-mentioned scenario, another example is a taxi-hailing scenario. For example, in order to facilitate users' travel, there are various taxi-hailing apps on the market. When a user uses a taxi-hailing app to initiate a taxi request and a driver accepts the order, in order to facilitate the user to know the distance between the driver and the driver and the estimated time required to reach the driver's location, a waiting interface will be displayed after the order is accepted, such as Figure 2 (1) shows the distance between the driver and the user, the estimated time to reach the driver's location, and the current location of the driver and the user. Figure 2 In order to kill the boring waiting time, the user may switch out of the 5 minutes shown in (1) while waiting for the driver to arrive. Figure 2 (1) shown in the interface (hereinafter referred to as the interface of APP2), and to operate other APPs, such as Figure 2In the interface of APP3 shown in (2), the user chats with friend A. Since APP2 is switched to the background, it no longer displays the business processing progress corresponding to the waiting node event (the event of waiting for the driver to arrive), such as how long it will take for the driver to arrive at the north gate of community A. Therefore, while the user is chatting with friend A in the interface of APP3, he may miss the moment when the driver arrives at the north gate of community A in APP2. As a result, the user has not noticed that the driver has arrived at the north gate of community A, resulting in both the driver and the user waiting for each other, affecting the travel experience.

[0061] For example, the above-mentioned scenario can also be taken as an example of an item delivery scenario. For example, to facilitate users' online shopping, there are various shopping apps currently on the market. After a user purchases an item using a shopping app, during the item delivery phase, the shopping app's delivery interface will display the item's distance from the user and the estimated time required to reach the address entered by the user. Due to the long waiting time, in order to kill the tedious waiting time, while waiting for the delivery person to deliver the item, the user may switch out of the shopping app's delivery interface and operate other apps, such as chatting with friend A in the interface of APP3. Since the shopping app is switched to the background, the business processing progress corresponding to the waiting node event (the event of waiting for the delivery person to arrive) is no longer displayed. Therefore, while the user is chatting with friend A in the interface of APP3, they may miss the moment when the delivery person arrives at the destination in the shopping app. As a result, when the delivery person arrives, the user may not feel the destination, or may ignore the delivery person's call while doing other things, resulting in the user not being able to get the item in time, affecting the user experience.

[0062] It should be understood that the above description is only an example for better understanding the technical solution of this embodiment and is not intended to be the sole limitation of this embodiment. In practical applications, any application involving waiting for node events may encounter the above problem when it is running in the background.

[0063] In view of this, the present application provides a business processing method, which aims to allow users to promptly know the business processing progress of applications running in the background, so as to avoid missing important nodes and improve user experience.

[0064] In order to better understand the technical solution provided by this application, before describing the technical solution of this application, the hardware structure of the terminal device (such as a mobile phone, a tablet computer, a touch-screen PC, etc.) to which the technical solution of this application is applicable is first described in conjunction with the accompanying drawings.

[0065] like Figure 3As shown, exemplarily, the terminal 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.

[0066] Exemplarily, in some implementations, 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., which are not listed one by one here and are not limited in this application.

[0067] In addition, it should be noted that the processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU). Different processing units may be independent devices or integrated into one or more processors.

[0068] It is understandable that the controller can be the nerve center and command center of the terminal device 100. In actual applications, the controller can generate operation control signals according to instruction operation codes and timing signals to complete the control of instruction fetching and execution.

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

[0070] For example, in some implementations, the processor 110 may include one or more interfaces. The interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface.

[0071] Continue to see Figure 3 Exemplarily, the charging management module 140 is configured to receive charging input from a charger. The charger may be a wireless charger or a wired charger. In some wired charging implementations, the charging management module 140 may receive charging input from the wired charger via the USB interface 130. In some wireless charging implementations, the charging management module 140 may receive wireless charging input via a wireless charging coil of the terminal device 100. While the charging management module 140 is charging the battery 142, it may also provide power to the terminal device via the power management module 141.

[0072] Continue to see Figure 3Exemplarily, the power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140, and provides power to the processor 110, the internal memory 121, the external memory, the display 194, the camera 193, and the wireless communication module 160. The power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle number, battery health status (leakage, impedance), etc. In some other implementations, the power management module 141 can also be set in the processor 110. In other implementations, the power management module 141 and the charging management module 140 can also be set in the same device.

[0073] Continue to see Figure 3 For example, the wireless communication function of the terminal device 100 can be implemented through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor.

[0074] It should be noted that antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in terminal device 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In some other implementations, the antennas can be used in conjunction with a tuning switch.

[0075] Continue to see Figure 3 For example, the mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G applied to the terminal 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 perform filtering, amplification, and other processing on 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 implementations, at least some functional modules of the mobile communication module 150 can be set in the processor 110. In some implementations, at least some functional modules of the mobile communication module 150 can be set in the same device as at least some modules of the processor 110.

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

[0077] Continue to see Figure 3 Exemplarily, 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., applied to the terminal 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, frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

[0078] It should also be noted that the terminal device 100 implements its display functionality through a GPU, display screen 194, and an application processor. The GPU is a microprocessor for image processing that 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 modify display information.

[0079] Continue to see Figure 3Exemplarily, the display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode or an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a MiniLED, a MicroLed, a Micro-oLed, a quantum dot light-emitting diode (QLED), etc. In some implementations, the terminal device 100 may include one or N display screens 194, where N is a positive integer greater than 1.

[0080] In addition, it should be noted that the terminal device 100 can realize the shooting function through the ISP, camera 193, video codec, GPU, display screen 194 and application processor.

[0081] Furthermore, it should be noted that the ISP is used to process data fed back by camera 193. For example, when taking a photo, the shutter is opened, and light is transmitted through the lens to the camera's photosensitive element. The light signal is converted into an electrical signal, which is then transmitted to the ISP for processing and converted into an image visible to the naked eye. The ISP can also perform algorithmic optimization on image noise, brightness, and skin color. The ISP can also optimize parameters such as exposure and color temperature of the captured scene. In some implementations, the ISP can be located in camera 193.

[0082] In addition, it should be noted that 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 light signal into an electrical signal, and then passes the electrical signal to the ISP for conversion 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 implementations, the terminal device 100 may include 1 or N cameras 193, where N is a positive integer greater than 1.

[0083] Furthermore, it should be noted that the digital signal processor is used to process digital signals, and in addition to processing digital image signals, it can also process other digital signals. For example, when the terminal device 100 selects a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy.

[0084] Furthermore, it should be noted that video codecs are used to compress or decompress digital video. Terminal device 100 may support one or more video codecs. Thus, terminal device 100 can play or record videos in various encoding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, and MPEG4.

[0085] Continue to see Figure 3 For example, the external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the terminal device 100. The external memory card communicates with the processor 110 via the external memory interface 120 to implement data storage. For example, files such as music and videos can be stored in the external memory card.

[0086] Continue to see Figure 3 Exemplarily, 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 terminal 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 can 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 can store data created during the use of the terminal 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.

[0087] Specifically, in the technical solution provided in the embodiment of the present application, when the business progress of the application running in the background is displayed in the current user interface, the display status and display duration of the floating ball control can be pre-set and stored in the internal memory 121.

[0088] For example, when there are multiple running applications in the background that need to display their business progress, display strategies, such as displaying the most recently received one, or displaying the shortest time first and then the longest time, can also be pre-stored in the internal memory 121 .

[0089] In addition, it should be noted that the terminal device 100 can implement audio functions such as music playback and recording through the audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, and application processor.

[0090] In addition, it should be noted that 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 implementations, the audio module 170 can be provided in the processor 110, or some functional modules of the audio module 170 can be provided in the processor 110.

[0091] Continue to see Figure 3 For example, the buttons 190 include a power button, a volume button, etc. The buttons 190 may be mechanical buttons or touch buttons. The terminal device 100 may receive key inputs and generate key signal inputs related to user settings and function control of the terminal device 100.

[0092] Continue to see Figure 3 , exemplarily, the motor 191 can generate a vibration prompt. The motor 191 can be used for incoming call vibration prompts, and can also be used for touch vibration feedback. For example, touch operations acting on different applications (such as taking pictures, audio playback, etc.) can correspond to different vibration feedback effects. For touch operations acting on different areas of the display screen 194, the motor 191 can also correspond to different vibration feedback effects. Different application scenarios (for example: time reminders, receiving messages, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also support customization.

[0093] Continue to see Figure 3 For example, the indicator 192 may be an indicator light, which may be used to indicate charging status, power changes, messages, missed calls, notifications, and the like.

[0094] This concludes the introduction to the hardware structure of the terminal device 100. It should be understood that: Figure 3 The terminal device 100 shown is only an example. In a specific implementation, the terminal 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 component configuration. Figure 3 The various components shown in the drawings may be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application specific integrated circuits.

[0095] For a better understanding Figure 3The software structure of the terminal device 100 is shown in FIG. The software structure of the terminal device 100 is described below. Before describing the software structure of the terminal device 100, the architecture that can be adopted by the software system of the terminal device 100 is first described.

[0096] Specifically, in actual applications, the software system of the terminal device 100 can adopt a layered architecture, an event-driven architecture, a micro-kernel architecture, a micro-service architecture, or a cloud architecture.

[0097] In addition, it is understandable that the software systems currently used by mainstream terminal devices include but are not limited to Windows systems, Android systems, and iOS systems. For ease of explanation, the embodiment of the present application takes the layered architecture Android system as an example to exemplify the software structure of the terminal device 100.

[0098] In addition, the subsequent business processing solutions provided in the embodiments of this application are also applicable to other systems in specific implementations.

[0099] See also Figure 4 , which is a software structure block diagram of the terminal device 100 according to an embodiment of the present application.

[0100] like Figure 4 As shown, the layered architecture of the terminal device 100 divides the software into several layers, each with a clear role and division of labor. Layers communicate with each other via software interfaces. In some implementations, the Android system is divided into four layers: from top to bottom, the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer.

[0101] The application layer can include a series of application packages. Figure 4 As shown, the application package may include games, settings, text messages, email, browsers, videos and other applications, which are not listed here one by one and are not limited in this application.

[0102] The application framework layer provides application programming interfaces (APIs) and programming frameworks for applications in the application layer. In some implementations, these programming interfaces and programming frameworks can be described as functions. Figure 4 As shown, the application framework layer may include functions such as activity manager, business processing module, view system, business presentation module, context awareness module, etc., which are not listed here one by one and are not limited in this application.

[0103] Exemplarily, in this embodiment, the context awareness module is used to form a waiting node event fence when the event transmitted from the application in the application layer is the event corresponding to the waiting node mentioned above (hereinafter referred to as: waiting node event), and send the waiting node event fence notification to the business processing module that subscribes to the fence.

[0104] In addition, the context awareness module is further configured to form an application switching event fence upon receiving an application switching operation performed by a user, and notify the application switching event fence to the service processing module subscribed to the fence.

[0105] Exemplarily, in this embodiment, the business processing module is used to subscribe to fences to the context awareness module, such as waiting node event fences, application switching event fences, etc., and receive fence notifications of corresponding events sent by the context awareness module, and then perform analysis and processing to instruct the business presentation module to perform presentation in different ways.

[0106] Exemplarily, the analysis and processing performed by the business processing module is, for example, determining the location of the application that provides the event corresponding to the fence notification based on the received fence notification.

[0107] Accordingly, when the application (which triggers the waiting node event) is located in the background, the business presentation module is instructed to display the business progress information corresponding to the waiting node event in the form of a floating ball (floating capsule), such as the remaining time, current status, etc. On the contrary, if the application is located in the foreground, the application switching event fence is subscribed to the scenario perception module, so that when the application currently in the foreground is switched to the background, the scenario perception module can form an application switching event fence and send the application switching event fence notification to the business processing module. In this way, the business processing module can determine that the application that triggered the waiting node event is currently switched to the background based on the received application switching event fence notification, and at this time, the business presentation module can be instructed to display the business progress information corresponding to the waiting node event in the form of a floating ball.

[0108] For example, in this embodiment, the activity manager is used to manage the lifecycle of each application and the navigation back function. It is responsible for creating the Android main thread and maintaining the lifecycle of each application. In other words, when the service processing module determines the location of the currently running application (foreground or background), it specifically determines it based on the information managed by the activity manager.

[0109] Illustratively, in this embodiment, the service presentation module is configured to display service progress information corresponding to the waiting node event in the form of a floating ball according to the instruction of the service processing module.

[0110] It should be understood that the above description is merely an example listed for a better understanding of the technical solution of this embodiment, and is not intended to be the sole limitation on this embodiment.

[0111] In addition, it is understood that the division of the above functional modules is only an example for better understanding the technical solution of this embodiment and is not the only limitation to this embodiment. In actual applications, the above functions can also be integrated into one functional module, and this embodiment does not limit this.

[0112] In addition, it should be noted that, in actual applications, in order to enable the application that triggers the waiting node event to be switched to the background operation, to be able to display the processing progress of the business corresponding to the waiting stage time on the interface of the terminal device through the interactive processing of the above-mentioned scenario perception module, business processing module, and business presentation module, a software development kit (SDK) can be provided. For example, when the application that integrates the SDK triggers the waiting node event, it will send the event to the scenario perception module through the interface provided by the SDK, thereby triggering the business processing flow provided by the embodiment of the present application. Finally, after analysis and processing by the business processing module, when it is determined that the application is switched to the back-end operation and the waiting node event has not been completed, the business program module is instructed to display the business progress information corresponding to the waiting node event in the form of a floating ball.

[0113] In addition, it should be noted that in actual applications, for applications that have not integrated the above SDK, when an event triggered by the application is monitored, while responding to the event, the event can also be intercepted to determine whether the event is a waiting node event or an application switching event.

[0114] Correspondingly, when the intercepted event is a waiting node event or an application switching event, the event is sent to the context awareness module, thereby triggering the business processing flow provided in the embodiment of the present application.

[0115] It should be understood that the above description is merely an example listed for a better understanding of the technical solution of this embodiment, and is not intended to be the sole limitation on this embodiment.

[0116] Furthermore, it should be noted that the view system located in the application framework layer includes visual controls, such as controls for displaying text and images. 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 containing a text notification icon can include a view for displaying text and a view for displaying images.

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

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

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

[0120] The system library can include multiple functional modules, such as a surface manager, media libraries, a 3D graphics processing library (e.g., OpenGL ES), and a 2D graphics engine (e.g., SGL).

[0121] The surface manager is used to manage the display subsystem and provide fusion of 2D and 3D layers for multiple applications.

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

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

[0124] It is understandable that the 2D graphics engine mentioned above is a drawing engine for 2D drawing.

[0125] In addition, it is understandable that the kernel layer in the Android system is a layer between hardware and software. The kernel layer includes at least a display driver, a camera driver, an audio driver, a sensor driver, a Bluetooth driver, etc. Exemplarily, the sensor driver can be used to output a detection signal of a sensor (such as a touch sensor) to the view system, so that the view system displays the corresponding application interface in response to the detection signal. For example, when a user operation, such as a click operation, is detected on the floating ball used to display the business progress of the background application on the current interface, the interface of the application running in the background can be switched back to the foreground display in response to the operation behavior.

[0126] This concludes the introduction to the software structure of the terminal device 100. It is understood that Figure 4The layers in the illustrated software structure and the components contained in each layer do not constitute a specific limitation on the terminal device 100. In other embodiments of the present application, the terminal device 100 may include more or fewer layers than shown in the figure, and each layer may include more or fewer components, which is not limited in the present application.

[0127] Based on the above hardware structure and software structure, the following describes the changes in the interface display content after the business processing method provided in the embodiment of the present application is applied to the above-mentioned game scenario and taxi-hailing scenario in combination with the accompanying drawings.

[0128] See also Figure 5 In (1), for example, when a user is playing a game and the game character dies, the game character enters the resurrection waiting state, which triggers the waiting node event. Since the business processing progress corresponding to the waiting node event needs to be completed after 44 seconds, the game character can be resurrected after 44 seconds. In order to kill the boring resurrection waiting time, the player switches out of the game after the game character dies. Figure 5 The interface of APP1 shown in (1) is that APP1 is switched from the foreground to the background, and after APP1 is switched to the background, APP3 is started and the chat interface with friend A is entered, as shown in FIG. Figure 5 As shown in (2).

[0129] For example, from the above description of the software structure of the terminal device, it can be seen that based on the business processing method provided in the embodiment of the present application, after APP1 triggers a waiting node event, the scenario perception module perceives the event, forms a waiting node event fence, and sends the waiting node event fence notification to the business processing module. After receiving the fence notification, the business processing module subscribes to the application switching event fence to the scenario perception module.

[0130] Accordingly, when the context awareness module senses the application switching event, that is, APP1 switches to the background, it will form an application switching event fence and send the application switching event fence notification to the business processing module. The business processing module determines that APP1 has switched to the background according to the fence notification, and the waiting node event has not been processed yet, then it will instruct the business presentation module to display the floating ball in the current interface, such as Figure 5 In (2), the chat interface provided by APP3 with friend A displays the business processing progress information of the waiting node event corresponding to APP1.

[0131] See also Figure 5In (2), for example, the business progress will be displayed in the floating ball 20, such as the remaining waiting time for the game character to be resurrected "00:00:42", that is, 42s, and status information, such as "waiting for resurrection", and information of the APP corresponding to the business, such as directly displaying the icon of APP1, or the name of APP1, or a picture of the game character waiting for resurrection, etc., which will not be listed one by one here, and this implementation does not limit this.

[0132] In addition, it is understandable that when APP1 switches to background operation and waits for the business processing corresponding to the node event, that is, when the game character waits for resurrection, the remaining waiting time displayed in the floating ball 20 can be updated in real time so that the user can accurately know the progress of the business.

[0133] Exemplarily, regarding the update of the remaining waiting time, in some implementations, for example, when APP1 switches to background operation, a timer of a corresponding duration (remaining waiting time) is started. In this way, when APP1 is running in the background, the change of the timing time corresponding to the timer can facilitate the resurrection status of the game character.

[0134] Continue to see Figure 5 In (2), for example, if the user operates the floating ball 20 during the process of displaying the remaining time waiting for resurrection, such as clicking, the sensor in the terminal device detects the user operation and sends the corresponding detection signal to the view system. In response to the operation, the APP1 running in the background can be directly switched back to the foreground, that is, the content displayed on the interface of the terminal device will be changed from Figure 5 The chat interface provided by APP3 shown in (2) with user A is switched to Figure 5 (3) shows the waiting interface for APP1 to be revived.

[0135] See also Figure 5 In (3), for example, when APP1 switches back to the foreground from the background, the floating ball 20 disappears automatically because the current interface can directly display the business processing progress corresponding to the waiting node event, such as the waiting resurrection time.

[0136] For example, if Figure 5 After the interface shown in (3) stays for a few seconds, and the game character has not yet been resurrected, the user switches APP1 to the background again and goes to the chat interface with user A provided by APP3. Based on the above processing logic, the floating ball 20 appears again and displays the latest business processing progress and status information.

[0137] For example, if the game character is resurrected successfully while APP1 is running in the background, the content displayed in the floating ball 20 will be updated as follows: Figure 5In (4), if the user operates the floating ball 20 again, the APP 1 can be directly switched back to the foreground from the background, thereby quickly entering the game using the resurrected game character.

[0138] Therefore, when a gaming APP triggers a waiting node event and switches from the foreground to the background, while the business corresponding to the waiting node event is being processed, based on the business processing method provided in the embodiment of the present application, a floating ball is displayed on the interface of the terminal device (regardless of whether there are other APPs running in the foreground), and the business processing progress information of the waiting node event of the gaming APP currently running in the background is displayed in the floating ball, and the content displayed in the floating ball is set to change with the processing of the business, so that the user can accurately understand the processing progress of the waiting node event and avoid missing important nodes.

[0139] It should be understood that the above description is merely an example listed for a better understanding of the technical solution of this embodiment, and is not intended to be the sole limitation on this embodiment.

[0140] See also Figure 6 In (1), for example, when a user initiates a taxi request through a taxi APP and a driver accepts the order, while waiting for the driver to arrive, a waiting node event is triggered. Since the business processing progress corresponding to the waiting node event needs to be completed after 5 minutes, that is, the driver can arrive at the north gate of community A after 5 minutes, in order to kill the boring waiting time, the user switches out of the waiting node while waiting for the driver to arrive. Figure 6 The interface of APP2 shown in (1) is to switch APP2 from the foreground to the background, and after APP2 switches to the background, start APP3 and enter the chat interface with friend A, as shown in the figure below. Figure 6 As shown in (2). Based on the business processing method provided in the embodiment of the present application, the floating ball 20 will also be displayed on the chat interface with friend A provided by APP3.

[0141] See also Figure 6 In (2), for example, if APP2 is currently running in the background and the triggered waiting node event is the waiting driver pick-up event, the business progress displayed in the floating ball 20 is the remaining waiting time for the driver to arrive, such as "00:04:35", which means that the driver is expected to arrive at the north gate of Community A in 4 minutes and 35 seconds. Since the driver has not arrived yet, the displayed status information may be "waiting for pick-up". Correspondingly, if the driver has arrived, it may be "driver has arrived". The information about the APP displayed is the icon of APP2 or the name of APP2, etc., which will not be listed here one by one. This implementation does not impose any restrictions on this.

[0142] Continue to see Figure 6In (2), for example, if the user operates the floating ball 20 during the process of displaying the remaining time waiting for the driver to arrive, such as clicking, the sensor in the terminal device detects the user operation and sends the corresponding detection signal to the viewing system. In response to the operation, the APP2 running in the background can be directly switched back to the foreground, that is, the content displayed on the terminal device interface will be changed from Figure 6 The chat interface provided by APP3 shown in (2) with user A is switched to Figure 6 (3) shows the waiting interface of APP2.

[0143] See also Figure 6 In (3), for example, when APP2 switches back to the foreground from the background, the floating ball 20 disappears automatically because the current interface can directly display the business processing progress corresponding to the waiting node event, such as the estimated waiting time (3 minutes).

[0144] For example, if Figure 6 After the interface shown in (3) stays for a few seconds, and the driver who accepts the order has not yet arrived at the north gate of Community A, the user switches APP2 to the background again and goes to the chat interface with User A provided by APP3. Based on the above processing logic, the floating ball 20 appears again and displays the latest business processing progress and status information.

[0145] For example, if the driver arrives at the north gate of community A while APP2 is running in the background, the content displayed in the floating ball 20 will be updated as follows: Figure 6 In (4), if the user operates the floating ball 20 again, the user can directly switch the APP2 from the background back to the foreground, and then quickly go to the designated location according to the map instructions to find the vehicle driven by the driver who accepted the order.

[0146] For example, in some implementations, for a taxi-hailing scenario, when the content displayed on the floating ball 20 is updated to "The driver has arrived", the license plate number of the vehicle driven by the driver who accepts the order can also be displayed in the floating ball 20, so that the user can directly find the vehicle driven by the driver who accepts the order based on the displayed license plate number, providing a better user experience.

[0147] For example, in other implementations, for taxi-hailing scenarios, when the content displayed on the floating ball 20 is updated to "Driver has arrived", a virtual phone number of the driver who accepted the order can also be displayed in the floating ball 20. When the phone number displayed in the floating ball 20 is clicked, it is set to jump directly to the call interface, allowing the user to call the driver and communicate with the driver about the specific pickup location. This implementation is also applicable to the above-mentioned item delivery scenario, and the specific implementation details are not repeated here.

[0148] Therefore, when a taxi-hailing APP triggers a waiting node event and switches from the foreground to the background, during the process of the business corresponding to the waiting node event being processed, based on the business processing method provided in the embodiment of the present application, a floating ball is displayed on the interface of the terminal device (regardless of whether there are other APPs running in the foreground), and the business processing progress information of the waiting node event of the taxi-hailing APP currently running in the background is displayed in the floating ball, and the content displayed in the floating ball is set to change with the processing of the business, so that the user can accurately understand the processing progress of the waiting node event and avoid missing important nodes.

[0149] It should be understood that the above description is merely an example listed for a better understanding of the technical solution of this embodiment, and is not intended to be the sole limitation on this embodiment.

[0150] Regarding other scenarios, based on the business processing method provided in the embodiment of the present application, the implementation method of displaying the business processing progress information corresponding to the waiting node event in the form of a floating ball on the terminal device interface when the application that triggers the waiting node event switches to background operation is similar to the above scenario and will not be repeated here. The following is an introduction to the overall implementation process and logic of the business processing method provided in the embodiment of the present application in conjunction with the accompanying drawings.

[0151] See also Figure 7 , exemplarily illustrating the interaction process between APP1, which integrates the SDK for sending events mentioned above, and the context awareness module, business processing module, and business presentation module in the application framework layer when implementing the business processing method provided in an embodiment of the present application.

[0152] Specifically, the service processing method provided in the embodiment of the present application may include three stages, namely, the waiting node event fence subscription stage (this stage includes Figure 7 "1. Subscribe to wait node event fence" operation), wait for APP to send events and process received events (this stage includes Figure 7 The corresponding operations of 2.1 to 2.5 in the above), the corresponding processing stage when the APP that sends the waiting node event is switched to the background (this stage includes Figure 7 3.1, 3.2, and corresponding operations in 2.5).

[0153] The node event fence subscription phase is specifically performed when the terminal device is started and the installed application is loaded, for example Figure 7 When the APP that integrates the above SDK is APP1, when the terminal device starts loading APP1, the business processing module will call the fence subscription function ( Figure 7Fence subscription / trigger processing in the context awareness module), subscribe to the waiting node event fence for APP1, that is, execute Figure 7 "1. Subscribe to the wait node event fence" operation.

[0154] Continue to see Figure 7 For example, when APP1 triggers an event, it will send the event to the permission verification function in the business processing module based on the interface provided by the SDK ( Figure 7 In "2.1, Events"), the permission check determines whether the event from APP1 is a waiting node event. Accordingly, if it is a waiting node event, the waiting node event is transmitted to the context perception module ( Figure 7 2.2 in the above), since the context awareness module has received the request for the waiting node event fence of APP1 that the business processing module subscribed to during the terminal device startup phase, it will form the waiting node event fence corresponding to APP1 after receiving the waiting node awareness event, and send the formed waiting node event fence notification corresponding to APP1 to the function in the business processing module for processing the subscribed fence ( Figure 7 (The corresponding operation in 2.3) is processed.

[0155] For example, if the business processing module determines that APP1 is currently running in the foreground based on the information provided by the activity manager, in order to display the above-mentioned floating ball 20 when APP1 switches to the background, the business processing module will subscribe to the application switching event fence for APP1 from the context awareness module ( Figure 7 (The corresponding operation in 2.4).

[0156] For example, if the service processing module determines that APP1 is currently running in the background according to the information provided by the activity manager, it directly instructs the service presentation module to display the remaining waiting time of the waiting node event of APP1 in the form of a floating ball 20 ( Figure 7 (The corresponding operation in 2.5).

[0157] It is understandable that, from the above scenario description, information of APP1, such as an icon or name, and status information, can also be displayed in the floating ball 20.

[0158] Continue to see Figure 7 For example, if the business processing module determines that APP1 is currently running in the foreground based on the information provided by the activity manager, and subscribes to the application switching event fence for APP1 with the context awareness module, it detects that APP1 is switched to the background ( Figure 7The context-aware module senses the switching operation and forms an application switching event fence (which can indicate which APP is switched to the background, here APP1), and sends the application switching event fence notification of APP1 to the function for fence subscription / trigger processing in the business processing module ( Figure 7 (The corresponding operation in 3.2).

[0159] Accordingly, the service processing module determines that APP1 is switched to the background according to the application switching event fence notification of APP1, and then instructs the service presentation module to remind in the form of a floating ball 20, such as displaying the remaining waiting time of the waiting node event of APP1 ( Figure 7 (The corresponding operation in 2.5).

[0160] It should be understood that Figure 7 What is shown is only an example of the interaction of functional modules involved in implementing the business processing method provided in the embodiment of the present application. In actual applications, other processing can also be introduced. For example, when an event is triggered, the waiting time of the waiting node event, the status information corresponding to different times, etc. are obtained, and the information is encapsulated in the formed fence notification. This embodiment does not limit this.

[0161] Based on the above interaction logic, see Figure 8 , exemplarily illustrating a specific implementation process of a business processing method, including:

[0162] S101, displaying a first interface of a first application on a display screen of a terminal device.

[0163] Taking the first application as APP1 in this application as an example, the first interface is an interface for users to use game characters to perform game tasks, such as Figure 13 Take (3) as an example.

[0164] S102: When a first waiting node event occurs in the first interface, in a business processing process corresponding to the first waiting node event, in response to an operation acting on the first application, the first application is switched to background operation.

[0165] Take the first waiting node event as an example, which is the game character's death and waiting for resurrection.

[0166] S103 , while the first application is running in the background, a floating ball is displayed on the display screen, where the floating ball displays business processing progress information corresponding to the first waiting node event and identification information of the first application where the first waiting node event occurs.

[0167] The service processing progress information corresponding to the first waiting node event includes, for example, the remaining waiting time of the first waiting node event and status information corresponding to the remaining waiting time.

[0168] S104: During the process of displaying the floating ball, when an operation acting on the floating ball is received, the first application is switched back to the foreground, the first interface of the first application is displayed, and the floating ball is canceled.

[0169] It should be noted that in actual applications, when the terminal device starts loading an application that integrates the above SDK, the events subscribed to by the business processing module are not limited to waiting for node events. Considering that users can also perform other operations when using the application to trigger other events, they can directly subscribe to events. That is, after any event sent by calling the SDK interface is verified by the permission verification function and sent to the context perception module, an event fence notification will be generated, and then the event fence notification will be sent to the business processing, and the business processing module will determine the event type of the current event. When the event fence is triggered, the processing logic of the business processing module is as follows: Figure 9 shown.

[0170] S201: After receiving an event, determine the event type.

[0171] For example, since the business processing corresponding to different events requires calling different application programming interfaces (APIs), the event type corresponding to the current event fence can be determined based on the API interface information carried in the event fence notification.

[0172] Exemplarily, this embodiment divides event types into scenario types and system types, wherein scenario types may include wait node events and cancel events, and system types may include application exit events.

[0173] It is understandable that in this embodiment, the cancel event is specifically used to terminate the processing of the waiting node event, and the application exit event is used to close the application that provides the event, specifically, it can be to kill the thread corresponding to the application.

[0174] S202, the event is a scene type event (wait node event and cancel event).

[0175] S203: Is it a waiting node event?

[0176] Exemplarily, when it is determined that the currently received event is a scene type event, it is further determined whether the scene type event is a waiting node event.

[0177] Accordingly, when the scene event is a wait node event, step S204 is executed; otherwise, it indicates that the scene type event is a cancel event, and step S209 is executed.

[0178] S204, saving the waiting node event.

[0179] For example, when the currently received event is a waiting node event, the business processing module will save the waiting node event, so that the content that needs to be displayed in the floating ball on the display screen later can be associated with the saved waiting node event.

[0180] S205: Check whether the application providing the event is in the foreground.

[0181] Exemplarily, if it is determined through judgment that the application providing the wait node event is running in the foreground, the application switching event fence is subscribed to the context awareness module.

[0182] It is understandable that, since the application is currently in the foreground, the subscribed application switching event fence is specifically the application switching background event fence, that is, step S206 is executed. The logic of subscribing to the application switching event fence in other embodiments of the present application is the same.

[0183] Exemplarily, if it is determined through judgment that the application providing the waiting node event is running in the background, the service presentation module is notified to display a floating ball, and the application switching event fence is subscribed to the context awareness module.

[0184] It is understandable that, since the application is currently in the background, the subscribed application switching event fence is specifically the application switching foreground event fence, that is, step S207 is executed. The logic of subscribing to the application switching event fence in other embodiments of the present application is the same.

[0185] S206: Subscribe to the background event fence of the application switching.

[0186] S207: Notify the service presentation module to display a floating ball and subscribe to the application switching foreground event fence.

[0187] S208: The event is a system type event (application exit event).

[0188] For example, if the only system-type event is an exit event, then when it is determined that the received event is a system-type event, it can be determined that the event is actually an application exit event. If the event is an application exit event, before exiting the current application, it is necessary to further determine whether there are currently any unfinished waiting node events, that is, to execute step S209.

[0189] S209: Whether there is any unfinished waiting node event.

[0190] That is, whether there is any business corresponding to the previously received waiting node event that has not been processed yet.

[0191] Accordingly, if it exists, step S210 is executed; otherwise, in response to the application exit event, the application is exited directly.

[0192] S210: Delete the saved waiting node event and notify the service presentation module to cancel the floating ball.

[0193] Since the application is about to exit, the main process will be killed. Therefore, in order to avoid resource occupation, it is necessary to delete the unprocessed waiting node events in the business processing module and notify the business presentation module to cancel the floating ball.

[0194] From the above description, we can see that the application switching event fence is divided into the application switching foreground event fence and the application switching background event fence. Regarding the application switching background event fence, the processing logic of the business processing module is as follows Figure 10 As shown; when the application switches to the foreground event fence, the processing logic of the business processing module is as follows Figure 11 shown.

[0195] See also Figure 10 When the application switches the background event fence, the processing logic of the business processing module is as follows:

[0196] S301: Is there any unfinished waiting node event?

[0197] For example, if there is an unfinished waiting node event, the business processing module notifies the business presentation module to display a floating ball and displays the business processing progress information corresponding to the unfinished waiting node event, and at the same time provides the application of the unfinished waiting node event to switch to the background operation. The business processing module also needs to subscribe to the application switching foreground event fence to the scenario perception module, that is, execute step S302, so that after receiving the application switching foreground event fence notification, when the application is switched from the background back to the foreground operation, the business presentation module is notified to cancel the display of the floating ball.

[0198] For example, if there is no unfinished waiting node event, that is, there is no need to notify the business presentation module to display the floating ball when the application is running in the background, so the business processing module can send a message to the context perception module to unsubscribe from the application switching background event fence, that is, execute step S303, to further reduce the occupation of system resources.

[0199] S302: Notify the service presentation module to display a floating ball and subscribe to the application switching foreground event fence.

[0200] S303: Unsubscribe the application switching background event fence.

[0201] See also Figure 11 When the application switches the foreground event fence, the processing logic of the business processing module is as follows:

[0202] S401, whether there is a suspended ball.

[0203] Exemplarily, the business processing module determines whether the business presentation module is operating, that is, the floating ball is displayed on the display screen. If the floating ball is not displayed, when the application switches back to the foreground from the background, there is no need to notify the business presentation module to cancel the floating ball (the floating ball itself does not exist). Therefore, the business processing module needs to send an unsubscribed application switching foreground event fence to the context perception module, that is, execute step S402 to further reduce the occupation of system resources.

[0204] For example, if there is a floating ball currently, the business presentation module is notified to cancel the floating ball. At the same time, in response to the switching event, the application is switched back to the foreground from the background. Since the application is already in the foreground, there is no need to subscribe to the application switching foreground event fence. The business processing module needs to send the unsubscribed application switching foreground event fence to the context perception module, that is, execute step S403 to further reduce the occupation of system resources.

[0205] S402: Unsubscribe the application switching foreground event fence.

[0206] S403: Notify the service presentation module to cancel the floating ball and unsubscribe the application switching foreground event fence.

[0207] This concludes the introduction to the processing logic of the business processing module when different event fences are triggered. The following describes a schematic diagram of the interface changes of a terminal device when the business processing method provided in this embodiment is applied to an actual scenario, in conjunction with the accompanying drawings.

[0208] See also Figure 12 and Figure 13 , which exemplarily shows a schematic diagram of the interface changes of the terminal device when the above-mentioned business processing method is applied to the game scenario.

[0209] See also Figure 12 In (1), the example line is still taken as an example, in the process of the game, the game character dies and enters the waiting state for resurrection (it takes 44 seconds to resurrect). After the waiting node event (waiting for the game character to be resurrected) is triggered, APP1 sends the event to the business processing module through the interface provided by the above SDK. The business processing module performs permission verification on the received event, determines that the event is a waiting node event, and sends the waiting node event to the context perception module. The context perception module forms a waiting node event fence corresponding to the waiting node event, and sends the waiting node event fence notification to the business processing module. The business processing module subscribes to the application switching event fence of APP1 to the context perception module.

[0210] Accordingly, when the user changes APP1 from Figure 12After the interface shown in (1) switches to the background, the context perception module senses that APP1 has been switched to the background, forms an application switching event fence for APP1, and sends an application switching event fence notification for APP1 to the business processing module. Based on the received fence notification, the business processing module determines that APP1 has switched from the foreground to the background, and notifies the business presentation module to display the business processing progress information of the waiting node event corresponding to APP1 in an expanded floating ball, for example Figure 12 As shown in (2).

[0211] It is understandable that the interface displayed by the terminal device when the floating ball is displayed can be any interface other than the interface provided by APP1, such as the desktop, or the interface of other APPs. Figure 12 In (2), the chat interface with friend A provided by APP3 is taken as an example.

[0212] For example, in Figure 12 In the interface shown in (2), after the expanded suspended ball is displayed, the suspended ball can remain in the expanded state for a first period of time, such as 5 seconds, and the remaining time of the information displayed therein changes in real time, such as Figure 12 As shown in (3). After the first time, the suspended ball can be switched from the unfolded state to the folded state, i.e. Figure 12 As shown in (4). Thus, when the application that triggers the waiting node event is running in the background, the business processing progress information corresponding to the waiting node event is displayed in the form of a floating ball on the interface of the terminal device, and the floating ball is switched from the expanded state to the collapsed state after the first display time, thereby reducing the obstruction of the current interface content.

[0213] For example, when the floating ball becomes folded, since the area where content can be displayed becomes smaller, in some implementations, only APP information, such as an icon or name, can be displayed, as well as an indication that the floating ball currently displays business processing progress information corresponding to the waiting node event for the APP, such as APP1.

[0214] For example, when the floating ball is in the folded state, the business of waiting for the node event is still being processed, such as the remaining time of waiting for resurrection is still counting down. When the remaining time is about to end and the status information corresponding to the waiting node event is about to change from "waiting for resurrection" to "reviewed", the floating ball can be switched from the folded state to the expanded state when the second time length is left, such as 5 seconds, and the current business progress and status information are displayed in the floating ball, such as Figure 12As shown in (5). In this way, the user can know in advance that the game character in APP1 will be resurrected in 5 seconds, so that the user can switch APP1 from the background to the foreground in advance by clicking the floating ball, wait for the game character to be resurrected in the waiting resurrection interface of APP1, and then immediately use the resurrected game character to perform the game task. That is, when the floating ball is in the folded state, when the business processing corresponding to the waiting node data is about to be completed, or the state is about to change, the floating ball can be set to automatically switch from the folded state to the expanded state at the second time length of the distance change, and the current state information can be displayed in the expanded state, so that the user can know the current state in time when the state changes, and perform corresponding operations.

[0215] For example, the suspended ball is in Figure 12 After the state shown in (5), if no operation is received from the user on the floating ball, after the waiting time for resurrection is over, that is, after the game character is resurrected, the content displayed in the floating ball can be changed to Figure 12 Medium (6) / Figure 13 In (1), the user clicks the floating ball to switch APP1 from the background back to the foreground. Figure 13 (3), so that users can use the resurrected game characters to perform game tasks.

[0216] For example, the suspended ball is in Figure 12 Medium (6) / Figure 13 In the state shown in (1), in the third time ( Figure 13 T3 in the figure), if within 5 seconds, if no user click operation on the floating ball is received, the floating ball can be switched to the folded state, such as Figure 13 Chinese (2).

[0217] For example, see Figure 13 In (2), when the user is in the fourth time length ( Figure 13 In T4), if the floating ball is clicked within 2 minutes, the terminal device will respond to the click operation and switch APP1 back to the foreground from the background. Figure 13 In (3), the user can use the resurrected game character to complete the game task. That is, at any time when the floating ball is displayed, in any state (folded or expanded), as long as the floating ball is clicked once, the APP1 can be switched from the background to the foreground, which is simple for the user to operate and provides a better experience.

[0218] For example, see Figure 13In (2), when the user has not clicked on the floating ball within the fourth time period, considering the actual usage scenario, the user may not use APP1 for a period of time in the next period of time. In order to avoid the thread corresponding to the floating ball occupying system resources for a long time, the thread can be killed after the fourth time period, thereby canceling the floating ball displayed on the current interface, such as Figure 13 Chinese (4).

[0219] In addition, it should be noted that the settings of the first, second, and third durations mentioned above can be set according to the overall waiting time corresponding to the waiting node event. For example, if the waiting time is short, the first duration can be set as the waiting time. In this way, the floating ball is displayed in an expanded state throughout the waiting process, ensuring that the user can be informed of the business processing progress in a timely and accurate manner and avoid missing important nodes.

[0220] Regarding the setting of the fourth time period, it can be set according to the maximum time allowed to stay in the background after the waiting stage event processing is completed. For example, after the game character is resurrected, he must return to the game to perform the game task within 2 minutes, otherwise the game will end directly. In this case, the fourth time period can be set to 2 minutes.

[0221] It should be understood that the above description is merely an example listed for a better understanding of the technical solution of this embodiment, and is not intended to be the sole limitation on this embodiment.

[0222] See also Figure 14 , exemplarily illustrating the interaction process between APP1 and APP2 of the SDK for sending events mentioned above, and the context perception module and the business processing module in the application framework layer when implementing the business processing method provided in an embodiment of the present application.

[0223] For example, Figure 14 Taking the example of APP1 and APP2 installed in the terminal device and integrating the above SDK, for the scenario where there are multiple APPs that can trigger the business processing method provided by the embodiment of the present application (this embodiment takes 2 as an example), when the terminal device starts loading APP1 and APP2, the business processing module will call the fence subscription function ( Figure 14 Fence subscription / trigger processing in), subscribe to the waiting node event fence for APP1 and the waiting node event fence for APP2 to the context awareness module.

[0224] Continue to see Figure 14For example, when APP1 triggers an event, it will send the event to the permission verification function in the business processing module based on the interface provided by the SDK. The permission verification function determines whether the current event from APP1 is a waiting node event. Accordingly, if it is a waiting node event, the waiting node event is transmitted to the context perception module. Since the context perception module has received the request for the waiting node event fence of APP1 subscribed by the business processing module during the startup phase of the terminal device, it will form the waiting node event fence corresponding to APP1 after receiving the waiting node perception event, and send the formed waiting node event fence notification corresponding to APP1 to the function in the business processing module for processing the subscribed fence.

[0225] Similarly, for APP2, when APP2 triggers an event, it will send the event to the permission verification function in the business processing module based on the interface provided by the SDK. The permission verification will determine whether the current event from APP2 is a waiting node event. Accordingly, if it is a waiting node event, the waiting node event will be transmitted to the scenario perception module. Since the scenario perception module has received the request for the waiting node event fence of APP2 subscribed by the business processing module during the startup phase of the terminal device, it will form the waiting node event fence corresponding to APP2 after receiving the waiting node perception event, and send the formed waiting node event fence notification corresponding to APP2 to the function in the business processing module for processing the subscribed fence.

[0226] In addition, it should be understood that for each APP, such as APP1 and APP2, after the context perception module forms the corresponding waiting node event fence and sends the corresponding waiting node event fence notification to the business processing module, the business processing module will send the application switching event fence that subscribes to the APP corresponding to the waiting node event to the context perception module, and when it is determined that the corresponding APP is switched to the background, the business processing progress information of the waiting node event corresponding to the APP is displayed on the current interface of the terminal device. The specific implementation process is similar to the above embodiment and will not be repeated here.

[0227] It should be understood that Figure 14 What is shown is only an example of the interaction of functional modules involved in implementing the business processing method provided in the embodiment of the present application. In actual applications, other processing can also be introduced. For example, when an event is triggered, the waiting time of the waiting node event, the status information corresponding to different times, etc. are obtained, and the information is encapsulated in the formed fence notification. This embodiment does not limit this.

[0228] Based on the above interaction logic, see Figure 15 , exemplarily illustrating a specific implementation process of a business processing method, including:

[0229] S501: Display a first interface of a first application on a display screen of a terminal device.

[0230] S502: When a first waiting node event occurs in the first interface, in the business processing process corresponding to the first waiting node event, in response to the operation acting on the first application, the first application is switched to background operation.

[0231] S503 : While the first application is running in the background, a floating ball is displayed on the display screen, where the floating ball displays the business processing progress information corresponding to the first waiting node event and the identification information of the first application where the first waiting node event occurs.

[0232] It is not difficult to find that steps S501 to S503 are substantially the same as steps S101 to S103 in the above embodiment. The specific implementation details can be found above and will not be repeated here.

[0233] S504 , while the first application is running in the background, after the floating ball is displayed on the display screen, in response to an operation performed on the second application, a second interface of the second application is displayed on the display screen.

[0234] S505 , when a second waiting node event occurs in the second interface, in the business processing process corresponding to the second waiting node event, in response to the operation acting on the second application, the second application is switched to background operation.

[0235] S506 , while the second application is running in the background, adjusting the content displayed in the floating ball to the business processing progress information corresponding to the second waiting node event and the identification information of the second application where the second waiting node event occurs.

[0236] S507, during the display of the floating ball, when an operation acting on the floating ball is received, if the business corresponding to the first waiting node event has not been processed, after switching the second application back to the foreground and displaying the second interface of the second application, the business processing progress information corresponding to the first waiting node event and the identification information of the first application where the first waiting node event occurred are displayed in the floating ball.

[0237] In addition, it should be noted that if the business corresponding to the first waiting node event has been processed, the floating ball is cancelled after the second application is switched back to the foreground and the second interface of the second application is displayed.

[0238] Furthermore, considering that in the above embodiment, after the service corresponding to the first waiting node event has been processed, within the fourth time period T, if the first application is still running in the background, the floating ball can continue to display the service processing progress information corresponding to the first waiting node event. Therefore, after the service corresponding to the first waiting node event has been processed, after switching the second application back to the foreground and displaying the second interface of the second application, before canceling the floating ball, the time point when the service corresponding to the first waiting node event has been processed can be obtained.

[0239] Correspondingly, when the time point is no more than the fourth time length away from the current system time point, after switching the second application back to the foreground and displaying the second interface of the second application, the business processing progress information corresponding to the first waiting node event and the identification information of the first application where the first waiting node event occurs are displayed in the floating ball; otherwise, the floating ball is cancelled.

[0240] It should be understood that the technical solution provided by this embodiment is that when there are multiple applications running in the background, the display order of the business processing progress information corresponding to the waiting node event generated by each application running in the background follows the most recently received display in the floating ball. When the application corresponding to the business processing progress information displayed by the floating ball is switched back to the foreground, if there is still a waiting node event generated by an application that meets the above conditions in the background, the content displayed in the floating ball is adjusted to the business processing progress information corresponding to the waiting node event generated by the application that meets the above conditions. Therefore, only one floating ball is displayed on the interface of the terminal device, which can reduce the obstruction of the display screen content and reduce the occupation of system resources, thereby reducing the power consumption of the terminal device.

[0241] For example, in other implementations, when multiple applications are running in the background, the order in which the business processing progress information corresponding to the waiting node events generated by each of the background applications can be displayed in the floating ball is such that the one with the shortest remaining waiting time is displayed first. In other words, after completing step S505 above, the remaining waiting time corresponding to the first waiting node event and the second waiting node event can be determined.

[0242] Accordingly, when the remaining waiting time corresponding to the first waiting node event is not less than the remaining waiting time corresponding to the second waiting node event, while the second application is running in the background, the content displayed in the floating ball is adjusted to the business processing progress information corresponding to the second waiting node event and the identification information of the second application where the second waiting node event occurs; when the remaining waiting time corresponding to the first waiting node event is less than the remaining waiting time corresponding to the second waiting node event, while the second application is running in the background, the floating ball continues to display the business processing progress information corresponding to the first waiting node event and the identification information of the first application where the first waiting node event occurs.

[0243] In addition, it can be understood that after the content displayed in the floating ball is adjusted to the business processing progress information corresponding to the second waiting node event and the identification information of the second application where the second waiting node event occurs, during the display of the floating ball, when an operation acting on the floating ball is received, the second application is switched back to the foreground to run, and the second interface of the second application is displayed, and the content displayed in the floating ball is adjusted to display the business processing progress information corresponding to the first waiting node event and the identification information of the first application where the first waiting node event occurs.

[0244] In addition, it can also be understood that after the content displayed in the floating ball is adjusted to the business processing progress information corresponding to the second waiting node event and the identification information of the second application where the second waiting node event occurs, the business corresponding to the second waiting node event has been processed, and the floating ball is displayed within the fourth time length. If no operation acting on the floating ball is received, and the remaining waiting time corresponding to the first waiting node event is not 0, or the business corresponding to the first waiting node event has been processed, but the time point of completion is not more than the fourth time length from the current system time, the content displayed in the floating ball is adjusted to the business processing progress information corresponding to the first waiting node event and the identification information of the first application where the first waiting node event occurs.

[0245] In addition, it can also be understood that after the floating ball continues to display the business processing progress information corresponding to the first waiting node event and the identification information of the first application where the first waiting node event occurs, the business corresponding to the first waiting node event has been processed, and the floating ball displays within the fourth time length, if no operation acting on the floating ball is received, the business corresponding to the second waiting node event has been processed, but the time point of processing is not more than the fourth time length from the current system time, the content displayed in the floating ball is adjusted to the business processing progress information corresponding to the second waiting node event and the identification information of the second application where the second waiting node event occurs.

[0246] When the floating ball displays the business processing progress information corresponding to each waiting node event triggered by an application, the state changes of the floating ball and the changes in the displayed content are similar to those described in the above embodiment. For the content not recorded in detail in this embodiment, please refer to the above embodiment and will not be repeated here.

[0247] See also Figure 16 and Figure 17 , which exemplarily shows a schematic diagram of the interface changes of the terminal device when the above-mentioned business processing method is applied to the game scenario and the taxi-hailing scenario.

[0248] For example, the APP currently running in the foreground is APP2, and the user initiates a taxi request through the taxi APP, and a driver accepts the order, that is, in Figure 16When the waiting node event of "waiting for the driver to arrive" is displayed in the waiting node interface shown in (1), APP2 sends the waiting node event of "waiting for the driver to arrive" to the business processing module through the interface provided by the above SDK. The business processing module performs permission verification on the received event, determines that the event is the waiting node event of APP2, and sends the waiting node event of APP2 to the context perception module. The context perception module forms a waiting node event fence corresponding to the waiting node event of APP2, and sends the waiting node event fence notification of APP2 to the business processing module. The business processing module subscribes to the application switching event fence of APP2 to the context perception module.

[0249] Accordingly, when the user changes APP2 from Figure 16 After the interface shown in (1) switches to the background, the context perception module senses that APP2 has been switched to the background, forms an application switching event fence for APP2, and sends an application switching event fence notification for APP2 to the business processing module. Based on the received fence notification, the business processing module determines that APP2 has switched from the foreground to the background, and notifies the business presentation module to display the business processing progress information of the waiting node event corresponding to APP2 with an expanded floating ball, for example Figure 16 As shown in (2).

[0250] It is understandable that the interface displayed by the terminal device when the floating ball is displayed can be any interface other than the interface provided by APP2, such as the desktop, or the interface of other APPs. Figure 16 In (2), APP1 provides a game interface as an example. That is, after the user switches APP2 to the background, APP1 is started to use the game character to perform the game task.

[0251] For example, in Figure 16 In the interface shown in (2), after the expanded suspended ball is displayed, the suspended ball can remain in the expanded state for a first period of time, such as 5 seconds, and the remaining time of the information displayed therein changes in real time, such as Figure 16 As shown in (3). After the first time, the suspended ball can be switched from the unfolded state to the folded state, i.e. Figure 16 As shown in (4). Thus, when the application that triggers the waiting node event is running in the background, the business processing progress information corresponding to the waiting node event is displayed in the form of a floating ball on the interface of the terminal device, and the floating ball is switched from the expanded state to the collapsed state after the first display time, thereby reducing the obstruction of the current interface content.

[0252] For example, in the process of displaying any state of the floating ball (expanded or retracted) in the game interface provided by APP1, if the game character dies and enters the waiting state for resurrection (it takes 44 seconds to resurrect), Figure 16As shown in (4). After the waiting node event (waiting for the game character to be resurrected) is triggered, APP1 sends the event to the business processing module through the interface provided by the SDK. The business processing module performs permission verification on the received event, determines that the event is a waiting node event, and sends the waiting node event to the context perception module. The context perception module forms a waiting node event fence corresponding to the waiting node event and sends the waiting node event fence notification to the business processing module. The business processing module subscribes to the context perception module for the application switching event fence of APP1.

[0253] For example, when APP1 is running in the foreground, the floating ball still displays the business processing progress information of the waiting node event corresponding to APP2. Figure 16 After the interface shown in (4) switches to the background, the context perception module senses that APP1 is switched to the background, forms an application switching event fence for APP1, and sends an application switching event fence notification for APP1 to the business processing module. The business processing module determines that APP1 switches from the foreground to the background based on the received fence notification. In a feasible implementation, for example, when the floating ball always displays the business processing progress information corresponding to the latest / most recently received waiting node event, since the waiting node event corresponding to APP1 is triggered later than the waiting node event corresponding to APP2, that is, the latest received waiting node event is APP1, the business processing module will notify the business presentation module to display the business processing progress information of the waiting node event corresponding to APP1 with an expanded floating ball, for example Figure 16 As shown in (5).

[0254] For example, in another feasible implementation, based on the waiting times corresponding to multiple waiting node events, the one with the shortest waiting time, that is, the waiting node event that was first processed by the service, can be selected as the waiting node event to be displayed in the floating ball. Accordingly, after the processing of this event is completed, if there are other waiting node events that have not been processed, another waiting stage event with the shortest remaining waiting time is selected for display.

[0255] It should be understood that the above description is only an example for better understanding the technical solution of this embodiment and is not the only limitation of this embodiment. This embodiment takes the implementation method of always displaying the latest / most recently received waiting node event corresponding to the business processing progress information as an example.

[0256] It is understandable that the interface displayed by the terminal device when the floating ball is displayed can be any interface other than the interface provided by APP1, such as the desktop, or the interface of other APPs. Figure 16 In (5), the chat interface with friend A provided by APP3 is taken as an example.

[0257] For example, in Figure 16 In the interface shown in (5), after the expanded floating ball is displayed, the floating ball can remain in the expanded state for a first duration, such as 5 seconds, and the remaining time of the information displayed therein changes in real time. After the first duration, the floating ball can be switched from the expanded state to the folded state. Thus, when the application that triggers the waiting node event is running in the background, the business processing progress information corresponding to the waiting node event is displayed in the form of a floating ball on the interface of the terminal device, and the floating ball is switched from the expanded state to the folded state after the first duration is displayed, thereby reducing the obstruction of the current interface content.

[0258] Regarding the logic followed by the suspension ball switching from the expanded state to the folded state, and from the folded state to the expanded state, please refer to other embodiments and will not be repeated here.

[0259] For example, the suspended ball is in Figure 17 In the state shown in (1), in the third time ( Figure 17 T3 in the figure), if within 5 seconds, if no user click operation on the floating ball is received, the floating ball can be switched to the folded state, such as Figure 17 Chinese (2).

[0260] For example, when the user is in the fourth time period ( Figure 17 In the middle of the process (T4), if the floating ball is not clicked within 2 minutes, considering the actual usage scenario, the user may not use APP1 for a period of time in the next period of time. In order to ensure that the user can know the business processing progress information of the waiting node event corresponding to APP2, when the waiting node event of APP2 has not been processed, the business processing progress information corresponding to the waiting node event of APP2 can be displayed in the floating ball after the fourth period of time.

[0261] For example, in some implementations, if the business corresponding to the waiting node event of APP2 still needs a long time to complete, then after the fourth time period, the floating ball can be folded to display the business processing progress information corresponding to the waiting node event of APP2, such as Figure 17 As shown in (3), only the icon or name of APP2 is displayed to inform the user that APP2 can be directly switched back to the foreground from the background when operating the floating ball.

[0262] For example, when the floating ball is in the folded state, the business of the waiting node event is still being processed, such as the remaining time of waiting for the pick-up is still counting down. When the remaining time is about to end and the status information corresponding to the waiting node event is about to change from "waiting for the pick-up" to "the driver has arrived", the floating ball can be switched from the folded state to the expanded state when the second time length is left, such as 5 seconds, and the current business progress and status information are displayed in the floating ball, such as Figure 17 As shown in (4). In this way, the user can know in advance that the driver who accepts the order in APP2 will arrive at the north gate of Community A in 5 seconds, so that the user can switch APP2 from the background to the foreground in advance by clicking the floating ball and view the relevant information of the driver who accepts the order, such as the virtual phone number, the license plate number of the vehicle being driven, etc. Similarly, within the fourth time period when the floating ball displays the waiting node event corresponding to APP2 as "Driver has arrived", if the user does not click on the floating ball, in order to avoid the thread corresponding to the floating ball occupying system resources for a long time, the thread can be killed after the fourth time period, thereby canceling the floating ball displayed on the current interface.

[0263] For example, in other implementations, if the business corresponding to the waiting node event of APP2 still needs a long time to complete, then after the fourth time period, the floating ball can be expanded to display the business processing progress information corresponding to the waiting node event of APP2, such as Figure 17 As shown in (4) (the waiting time for pick-up is not limited to the figure), the user can directly know the business processing progress of the waiting node event of waiting for pick-up without having to operate the floating ball and switch APP2 back to the front desk to know how long it will take for the driver to arrive at the north gate of community A.

[0264] It should be understood that the above description is merely an example listed for a better understanding of the technical solution of this embodiment, and is not intended to be the sole limitation on this embodiment.

[0265] Therefore, the business processing method provided in this embodiment, when there are multiple applications running in the background and each of them triggers a waiting node event, displays the business processing progress information corresponding to the waiting node event that was triggered most recently or the waiting node event with the shortest waiting time. That is, only one floating ball is displayed in the interface of the terminal device, thereby reducing the obstruction of the interface content. At the same time, since only one corresponding thread is responsible for updating the content in the floating ball, multi-thread blocking can be avoided, thereby reducing the power consumption of the terminal device.

[0266] In addition, it is understood that in order to implement the above functions, the terminal 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 this application.

[0267] In addition, it should be noted that the service processing methods provided in the above embodiments implemented by a terminal device in an actual application scenario can also be executed by a chip system included in the terminal device, wherein the chip system may include a processor. The chip system can be coupled to a memory so that when the chip system is running, it calls a computer program stored in the memory to implement the steps performed by the above terminal device. The processor in the chip system can be an application processor or a processor other than an application processor.

[0268] In addition, an embodiment of the present application also provides a computer-readable storage medium, which stores computer instructions. When the computer instructions are executed on a terminal device, the terminal device executes the above-mentioned related method steps to implement the business processing method in the above-mentioned embodiment.

[0269] In addition, an embodiment of the present application also provides a computer program product. When the computer program product is run on a terminal device, the terminal device executes the above-mentioned related steps to implement the business processing method in the above-mentioned embodiment.

[0270] In addition, an embodiment of the present application also provides a chip (which may also be a component or module), which may include one or more processing circuits and one or more transceiver pins; wherein the transceiver pins and the processing circuit communicate with each other through an internal connection path, and the processing circuit executes the above-mentioned related method steps to implement the business processing method in the above-mentioned embodiment to control the receiving pin to receive the signal, so as to control the transmitting pin to send the signal.

[0271] In addition, it can be seen from the above description that the terminal device, computer-readable storage medium, computer program product or chip provided in the embodiments of the present application are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods provided above, and will not be repeated here.

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

Claims

1. A business processing method, characterized in that: The method comprises: Displaying a first interface of a first application on a display screen of a terminal device; When a first waiting node event occurs in the first interface, during the business processing corresponding to the first waiting node event, in response to an operation performed on the first application, the first application is switched to background operation; wherein, during the business processing corresponding to the first waiting node event, the first interface only displays business processing progress information corresponding to the first waiting node event; During the process of the first application running in the background, a floating ball is displayed on the display screen, where the floating ball displays the business processing progress information corresponding to the first waiting node event and the identification information of the first application in which the first waiting node event occurs; During the display of the floating ball, when an operation acting on the floating ball is received, the first application is switched back to the foreground, the first interface of the first application is displayed, and the floating ball is canceled; The method further comprises: During the process of the first application running in the background, after the floating ball is displayed on the display screen, in response to an operation performed on the second application, a second interface of the second application is displayed on the display screen; When a second waiting node event occurs in the second interface, in the business processing process corresponding to the second waiting node event, in response to an operation acting on the second application, the second application is switched to background operation; When the remaining waiting time corresponding to the first waiting node event is not less than the remaining waiting time corresponding to the second waiting node event, while the second application is running in the background, the content displayed in the floating ball is adjusted to the business processing progress information corresponding to the second waiting node event and the identification information of the second application where the second waiting node event occurs; During the display of the floating ball, when an operation acting on the floating ball is received, the second application is switched back to the foreground to run, and the second interface of the second application is displayed. The content displayed in the floating ball is adjusted to display the business processing progress information corresponding to the first waiting node event and the identification information of the first application in which the first waiting node event occurs; When the remaining waiting time corresponding to the first waiting node event is less than the remaining waiting time corresponding to the second waiting node event, while the second application is running in the background, the floating ball continues to display the business processing progress information corresponding to the first waiting node event and the identification information of the first application where the first waiting node event occurs.

2. The method according to claim 1, characterized in that The method of displaying a suspended ball on the display screen includes: Displaying an expanded floating ball on the display screen, and displaying service processing progress information corresponding to the first waiting node event and identification information of the first application in which the first waiting node event occurs on the expanded floating ball; After the floating ball is displayed in an expanded state for a first time period, the floating ball is adjusted to a folded state, and identification information of the first application in which the first waiting node event occurs is displayed on the floating ball in the folded state.

3. The method according to claim 2, characterized in that The business processing progress information includes the remaining waiting time of the first waiting node event and the status information corresponding to the remaining waiting time; After the floating ball is displayed in the expanded state for a first time period, the floating ball is adjusted to the folded state, and the method further includes: When the remaining waiting time of the first waiting node event is not greater than the second time, adjusting the floating ball to an expanded state, and displaying the remaining waiting time of the first waiting node event, status information corresponding to the remaining waiting time, and identification information of the first application in which the first waiting node event occurs on the expanded floating ball; After the remaining waiting time becomes 0 and / or the status information changes, after the floating ball is displayed in an expanded state for a third time, the floating ball is adjusted to a folded state, and the identification information of the first application in which the first waiting node event occurs is displayed on the folded floating ball.

4. The method according to claim 3, characterized in that After the floating ball is displayed in the expanded state for a third time period, the floating ball is adjusted to the folded state, the method further includes: During the fourth time period when the floating ball is displayed in the folded state, if no operation acting on the floating ball is received, the floating ball is cancelled.

5. The method according to any one of claims 1 to 4, characterized in that The method includes: switching the first application back to the foreground to run, displaying the first interface of the first application, and canceling the floating ball when an operation acting on the floating ball is received during the display of the floating ball, including: When the floating ball is displayed in a folded state or an unfolded state, when an operation acting on the floating ball is received, the first application is switched back to the foreground, the first interface of the first application is displayed, and the floating ball is cancelled.

6. The method according to claim 1, characterized in that After adjusting the content displayed in the floating ball to the business processing progress information corresponding to the second waiting node event and the identification information of the second application in which the second waiting node event occurs, the method further includes: When the business corresponding to the second waiting node event has been processed, the floating ball is displayed within the fourth time period. If no operation acting on the floating ball is received, and the remaining waiting time corresponding to the first waiting node event is not 0, or the business corresponding to the first waiting node event has been processed, but the time point of processing is not more than the fourth time period away from the current system time, the content displayed in the floating ball is adjusted to the business processing progress information corresponding to the first waiting node event and the identification information of the first application where the first waiting node event occurs.

7. The method according to claim 1, characterized in that After the floating ball continues to display the service processing progress information corresponding to the first waiting node event and the identification information of the first application in which the first waiting node event occurs, the method further includes: When the business corresponding to the first waiting node event has been processed, the floating ball is displayed within the fourth time period. If no operation acting on the floating ball is received, the business corresponding to the second waiting node event has been processed, but the time point of processing is not more than the fourth time period from the current system time, the content displayed in the floating ball is adjusted to the business processing progress information corresponding to the second waiting node event and the identification information of the second application where the second waiting node event occurs.

8. A terminal device, characterized in that: The terminal device includes: a memory and a processor, the memory and the processor are coupled; the memory stores program instructions, and when the program instructions are executed by the processor, the terminal device executes the business processing method according to any one of claims 1 to 7.

9. A computer-readable storage medium, characterized in that The method comprises a computer program, which, when executed on a terminal device, enables the terminal device to execute the service processing method according to any one of claims 1 to 7.

Images