CN113805771A

CN113805771A - Notification reminding method, terminal equipment and computer readable storage medium

Info

Publication number: CN113805771A
Application number: CN202110947406.0A
Authority: CN
Inventors: 刘帅
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2021-08-17
Filing date: 2021-08-17
Publication date: 2021-12-17
Anticipated expiration: 2041-08-17
Also published as: CN113805771B

Abstract

The application is applicable to the technical field of terminals and provides a notification reminding method, terminal equipment and a computer readable storage medium. The notification reminding method comprises the following steps: in the process of foreground operation of the first application, carrying out notification reminding aiming at a first notification of a second application; stopping the notification reminder when a first operation for the notification reminder is detected; after stopping the notification reminder, the notification reminder is not performed on the second application before the first application exits from the foreground operation. According to the scheme, on one hand, the flexibility of avoiding disturbance of the notification can be improved, on the other hand, the notification reminding function of the second application can be quickly closed by a user in the process of using the first application, and the user operation is simplified.

Description

Notification reminding method, terminal equipment and computer readable storage medium

Technical Field

The present application relates to the field of terminal technologies, and in particular, to a notification reminding method, a terminal device, and a computer-readable storage medium.

Background

With the intelligent development of terminal equipment, the services provided by the terminal equipment are more and more abundant. The notification reminding service is used as a basic service of the terminal device, and can carry out notification reminding on a user when receiving the notification of the application. However, in some application scenarios (e.g., game scenarios), users sometimes (e.g., during critical periods of the game) do not want to be disturbed by the application's notification alerts. Based on this, the prior art further provides a notification disturbance-free function for an application scene, where the notification disturbance-free mode is automatically turned on each time the terminal device enters a target application scene, and in the notification disturbance-free mode, the terminal device does not perform notification reminding on the application or performs notification reminding on the application in a manner (such as vibration) that does not disturb a user.

However, the above-mentioned notification do-not-disturb function always turns on the notification do-not-disturb mode in the whole process from the terminal device entering the target application scenario to the terminal device exiting the target application scenario, and the user sometimes does not want to receive the notification reminder of the application in the whole process (for example, in the whole game process) that the terminal device is in the target application scenario.

Disclosure of Invention

The embodiment of the application provides a notification reminding method, a terminal device and a computer readable storage medium, which can improve the disturbance-free flexibility of notification on one hand, and can enable a user to quickly close the notification reminding function of a second application in the process of using a first application on the other hand, thereby simplifying user operation.

In a first aspect, an embodiment of the present application provides a notification reminding method, including:

in the process of foreground operation of the first application, carrying out notification reminding aiming at a first notification of a second application;

stopping the notification reminder when a first operation for the notification reminder is detected;

after stopping the notification reminder, not performing the notification reminder on the second application before the first application exits from the foreground operation.

The first application and the second application may each be any application installed on the mobile phone. Specifically, the first application and the second application may be a system application, a third party application, or the like. The system application refers to a built-in application directly built in the mobile phone, for example, the system application may be an application developed by a mobile phone manufacturer and directly built in the mobile phone, or an application developed by the mobile phone manufacturer and a third party manufacturer in cooperation and directly built in the mobile phone, and the like. The third-party application refers to an application obtained from the outside of the mobile phone, and may be, for example, an application developed by a third-party manufacturer, obtained by the mobile phone from the third-party manufacturer, and installed in the mobile phone.

The first application and the second application may be the same application or may be different applications.

Specifically, in the process that a first application runs in the foreground, if the terminal device receives a first notification of a second application, whether the second application has a notification permission in a target application scene is judged. And if the second application has the notification authority in the target application scene, the terminal equipment carries out notification reminding on the first notification.

For example, if the terminal device performs notification reminding on the first notification in a form of a banner, the first operation for the notification reminding may be a first touch gesture for the banner. Stopping the notification alert may include: hiding the banner.

According to the scheme, on one hand, the terminal device does not perform notification reminding on the second application when the first application starts to run in the foreground, but performs notification reminding on the first notification of the second application when the first notification of the second application is received, and does not perform notification reminding on the second application after detecting the first operation of the user for the notification reminding, namely the terminal device can perform notification disturbance-free on the second application when the user needs in the process of running the first application in the foreground, so that the flexibility of notification disturbance-free is improved. On the other hand, in the process that the user uses the first application, if the user wants to close the notification reminder of the second application, the user only needs to input the first operation aiming at the notification reminder when the terminal device performs the notification reminder on the second application without exiting the first application, and then enters the notification management interface of the second application to perform the operation, so that the operation of closing the notification reminder function of the application by the user is simplified, and the notification reminder function of the second application can be quickly closed by the user.

In a possible implementation manner of the first aspect, after the not performing the notification alert on the second application, the method further includes:

and after the first application exits from the foreground operation, recovering the notification reminding of the second application.

According to the scheme, the terminal equipment can automatically recover the notification reminding of the second application after the first application exits from the foreground operation of the terminal equipment, so that on one hand, a user does not need to enter the notification management interface of the second application for corresponding operation after the first application exits from the foreground operation of the terminal equipment, and the operation of starting the notification reminding function of the second application by the user is simplified; on the other hand, the terminal device recovers the notification reminding of the second application, so that the user can be prevented from missing the notification of the second application after the first application exits from the foreground operation of the terminal device, namely, the terminal device temporarily implements the notification disturbance-free reminding on the second application only in the process of operating the first application in the foreground at this time, and the terminal device can notify and remind the second application after the first application exits from the foreground operation or when the first application is operated in the foreground again after the terminal device, so that the flexibility of notifying the disturbance-free reminding is improved, and the user experience is improved.

In a possible implementation manner of the first aspect, in a process in which the first application runs in a foreground, performing notification reminding for a first notification of a second application includes:

in the process that a first application runs in a foreground, if a first notification of a second application is received and the second application has a notification permission under a target application scene, performing notification reminding aiming at the first notification, wherein the target application scene is an application scene where a terminal device is located when the first application runs in the foreground.

In a possible implementation manner of the first aspect, the enabling the second application to have the notification permission in the target application scenario includes: and the notification reminding function of the second application is in an open state.

In a possible implementation manner of the first aspect, the enabling the second application to have the notification permission in the target application scenario includes: and the notification reminding function of the second application is in an open state, a first shielding list does not comprise the identifier of the second application, and the first shielding list is used for storing the identifier of the application needing to implement notification without disturbance in the target application scene.

In a possible implementation manner of the first aspect, the method further includes:

in the process that a first application runs in a foreground, if a first notification of a second application is received and the second application does not have notification permission in a target application scene, the first notification is not reminded, and the target application scene is an application scene where terminal equipment is located when the first application runs in the foreground.

In a possible implementation manner of the first aspect, the second application having no notification permission in a target application scenario includes: and the notification reminding function of the second application is in a closed state.

In a possible implementation manner of the first aspect, the second application having no notification permission in a target application scenario includes: and the notification reminding function of the second application is in an open state, a first shielding list comprises the identifier of the second application, and the first shielding list is used for storing the identifier of the application needing to implement notification without disturbance in the target application scene.

In a possible implementation manner of the first aspect, after the detecting the first operation for the notification reminder, the method further includes:

adding the identifier of the second application to the first screening list, and marking the second application in the first screening list;

correspondingly, after stopping the notification reminder and before the first application exits from the foreground operation, not performing the notification reminder on the second application includes:

after stopping the notification reminding, before the first application exits from the foreground operation, if receiving the notification of the second application and detecting that the first shielding list comprises the identifier of the second application, not performing notification reminding on the second application.

In a possible implementation manner of the first aspect, the resuming the notification alert of the second application after the first application exits from the foreground running includes:

and when the first application exits the foreground operation, searching and deleting the marked identifier of the second application from the first shielding list.

when a notification management service is initialized, if the first screening list is detected to include the marked application, the identifier of the marked application in the first screening list is deleted.

adding the identifier of the second application to a second mask list, where the second mask list is used to store the identifier of an application that needs to implement notification without disturbing in a target time period, a start time of the target time period is a time when the first operation is detected, and a termination time of the target time period is a time when the first application exits from the foreground;

correspondingly, the not performing notification reminding on the second application includes:

and if the notification of the second application is received and the second shielding list is detected to comprise the identifier of the second application, not performing notification reminding on the second application.

and deleting the identifiers of all the applications in the second screening list when the first application exits the foreground operation.

when initializing notification management service, if detecting that the second screening list includes at least one application identifier, deleting the at least one application identifier in the second screening list.

In a possible implementation manner of the first aspect, the not performing notification reminding on the second application before the first application exits from the foreground operation after the notification reminding is stopped includes:

and if the first application is a preset application, after stopping the notification reminding, and before the first application exits from the foreground operation, not performing the notification reminding on the second application.

In a second aspect, an embodiment of the present application provides a terminal device, including:

the first notification management unit is used for performing notification reminding aiming at a first notification of a second application in the process that the first application runs in the foreground;

the second notification management unit is used for stopping the notification reminder when detecting a first operation aiming at the notification reminder;

and the third notification management unit is used for not performing notification reminding on the second application after stopping the notification reminding and before the first application exits from the foreground operation.

In a possible implementation manner of the second aspect, the terminal device further includes:

and the fourth notification management unit is used for recovering the notification reminding of the second application after the first application exits from the foreground operation.

In a possible implementation manner of the second aspect, the first notification management unit specifically includes:

the first notification reminding unit is used for carrying out notification reminding aiming at a first notification if the first notification of a second application is received and the second application has a notification authority under a target application scene in the process that the first application runs in the foreground, wherein the target application scene is an application scene where terminal equipment is located when the first application runs in the foreground.

In a possible implementation manner of the second aspect, the enabling the second application to have the notification permission in the target application scenario includes: and the notification reminding function of the second application is in an open state.

In a possible implementation manner of the second aspect, the enabling the second application to have the notification permission in the target application scenario includes: and the notification reminding function of the second application is in an open state, a first shielding list does not comprise the identifier of the second application, and the first shielding list is used for storing the identifier of the application needing to implement notification without disturbance in the target application scene.

In a possible implementation manner of the second aspect, the first notification management unit is further configured to:

In a possible implementation manner of the second aspect, the second application having no notification permission in a target application scenario includes: and the notification reminding function of the second application is in a closed state.

In a possible implementation manner of the second aspect, the second application having no notification permission in a target application scenario includes: and the notification reminding function of the second application is in an open state, a first shielding list comprises the identifier of the second application, and the first shielding list is used for storing the identifier of the application needing to implement notification without disturbance in the target application scene.

the first application management unit is used for adding the identifier of the second application to the first shielding list and marking the second application in the first shielding list;

correspondingly, the third notification management unit is specifically configured to:

Correspondingly, the fourth notification management unit is specifically configured to:

Correspondingly, the first application management unit is further configured to:

a second application management unit, configured to add an identifier of the second application to a second mask list, where the second mask list is used to store an identifier of an application that needs to implement notification without disturbing in a target time period, a start time of the target time period is a time when the first operation is detected, and a termination time of the target time period is a time when the first application exits from the foreground;

Correspondingly, the second application management unit is further configured to:

In a possible implementation manner of the second aspect, the third notification management unit is specifically configured to:

In a third aspect, an embodiment of the present application provides a terminal device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the computer program, the method according to any one of the first aspect is implemented.

In a fourth aspect, embodiments of the present application provide a computer-readable storage medium, in which a computer program is stored, and the computer program, when executed by a processor, implements the method according to any one of the above first aspects.

In a fifth aspect, embodiments of the present application provide a chip system, where the chip system includes a processor, and the processor is coupled with a memory, and executes a computer program stored in the memory to implement the method according to any one of the above first aspects. The chip system can be a single chip or a chip module consisting of a plurality of chips.

In a sixth aspect, embodiments of the present application provide a computer program product, which, when run on a terminal device, causes the terminal device to perform the method of any one of the first aspect.

It is understood that the beneficial effects of the second to sixth aspects can be seen from the description of the first aspect, and are not described herein again.

Drawings

Fig. 1 is a schematic view of a user interface in a game scene according to an embodiment of the present disclosure;

fig. 2 is a schematic view of a user interface in a video scene according to an embodiment of the present disclosure;

FIG. 3 is a schematic diagram of a notification management interface of an application according to an embodiment of the present application;

fig. 4 is a schematic structural diagram of a terminal device according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of another terminal device provided in an embodiment of the present application;

fig. 6 is a schematic view of a user interface that may be involved when a mobile phone performs notification reminding in a banner format and an operation gesture performed by a user according to an embodiment of the present disclosure;

FIG. 7 is a schematic view of a user interface when the mobile phone detects a first operation of a notification reminder for a first notification;

FIG. 8 is a schematic view of a user interface involved in a third operation performed by the user on the notification alert of the first notification;

FIG. 9 is a schematic view of a user interface involved in a fourth operation performed by the user on the notification alert of the first notification;

FIG. 10 is a schematic flow chart diagram of a notification alert method according to an embodiment of the present application;

FIG. 11 is a schematic flow chart diagram of another notification alert method provided by an embodiment of the present application;

fig. 12 is a schematic structural diagram of another terminal device according to an embodiment of the present application.

Detailed Description

It is noted that the terminology used in the description of the embodiments of the present application is for the purpose of describing particular embodiments of the present application only and is not intended to be limiting of the present application. In the description of the embodiments of the present application, "/" means "or" unless otherwise specified, for example, a/B may mean a or B; "and/or" herein is merely an associative relationship describing an association, meaning that there may be three relationships, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of the present application, "a plurality" means two or more, and "at least one", "one or more" means one, two or more, unless otherwise specified.

In the following, the terms "first", "second" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a definition of "a first" or "a second" feature may explicitly or implicitly include one or more of the features.

Reference throughout this specification to "one embodiment" or "some embodiments," or the like, means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the present application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," or the like, in various places throughout this specification are not necessarily all referring to the same embodiment, but rather "one or more but not all embodiments" unless specifically stated otherwise. The terms "comprising," "including," "having," and variations thereof mean "including, but not limited to," unless expressly specified otherwise.

With the intelligent development of the terminal device, a user can install various applications (such as social applications, media applications or game applications) on the terminal device to meet daily life and work needs. Services that can be provided by the terminal device are also increasingly rich, wherein the notification reminding service is a basic service of the terminal device, and can remind an application of notification when receiving notification (such as a new message notification or an audio-video call invitation notification) of the application.

However, in some application scenarios, a user sometimes does not want to be disturbed by an applied notification alert, and some application scenarios in which a user does not want to be disturbed by an applied notification alert are exemplarily described below with reference to the accompanying drawings:

the application scene one: game scene

Taking the game application as an example, when the game application is running in the foreground of the terminal device (i.e. the terminal device is in a game scene), if the game application is currently in a critical period of the game, such as a group battle period of a multiplayer game or a sprint period of a single-player game, the user does not want to be disturbed by the notification reminder of the application at this time, so as to avoid affecting the normal progress of the game.

Illustratively, as shown in fig. 1, a schematic diagram of a user interface of a terminal device in a game scene is shown. Specifically, as shown in (a) of fig. 1, in the user interface of the game application a, during the game, a plurality of notes 111 are dropped on each note channel 11 of the user interface continuously along with the fluctuation of the music rhythm, and when a note 111 drops to a note touch area 112 at the bottom end of the note channel 11, the user can obtain a score by tapping the corresponding note 112 in the note touch area 112. That is, during the game, the user needs to not only keep track of the notes 111 falling on each note channel 11, but also switch the fingers of the user back and forth between different note touch areas 112, which requires high attention, response speed, finger moving speed, and the like. For example, if during the game, the terminal device receives a notification of the weilink application, the terminal device may remind the notification in the form of a banner 12 (i.e., display the notification floating at the top of the screen) as shown in fig. 1 (b). However, the notification reminder may block the note 111 on the upper portion of the note channel 11, so that the user cannot predict the note 111 falling off the note channel 11, and the user may miss the chance of hitting the corresponding note and lose the score, and even may fail the entire game, and the game experience of the user is reduced.

Application scenario two: video scenes

Taking the video application as an example, when the video application runs in the foreground of the terminal device (that is, the terminal device is in a video scene), if the user selects to play the video in a full-screen manner, the user usually does not want to be disturbed by the notification reminder of the application at this time, so as to avoid affecting the normal playing of the video.

Illustratively, as shown in fig. 2, a schematic diagram of a user interface of a terminal device in a video scene is shown. Specifically, as shown in (a) of fig. 2, if the terminal device is playing the video "courageously strides" in full screen and the user opens the bullet screen 21, in the process, if the terminal device receives the notification of the weilink application, as shown in (b) of fig. 2, the terminal device may prompt the notification in the form of a banner 22 (or in combination with a prompt tone). However, when the terminal device reminds the notification in the form of the banner 22, the banner 22 may block part of the barrage in the video interface; when the terminal equipment notifies and reminds the notification through the prompt tone, the volume of the prompt tone may cover part of the volume of the video, so that the volume of the video is reduced, and the watching experience of a user is influenced.

Based on this, the prior art provides some means for notifying the user of the non-disturbance, which mainly includes the following two types:

mode 1 provides a notification management function for each application, and allows a user to turn on or off a notification reminder function of an application. Illustratively, as shown in FIG. 3, is a schematic view of a notification management interface for an application. Taking the WeLink application as an example, when the user wants to close the notification reminder of the WeLink application, as shown in (a) of fig. 3, the user may enter into the notification management interface of the WeLink application, and close the notification reminder function of the WeLink application by adjusting the switch control 31 of the "allow notification" column to the close gear. When the notification reminding function of the WeLink application is in a closed state, the terminal equipment does not remind the WeLink application of notification when receiving any notification of the WeLink application. When the user wants to turn on the notification reminder of the WeLink application, as shown in (b) of fig. 3, the user can enter the notification management interface of the WeLink application, and turn on the notification reminder function of the WeLink application by adjusting the switch control 31 of the "allow notification" column in the notification management interface to the on-gear.

However, this approach has the following drawbacks: 1. when a user does not want to be disturbed by the notification reminding of an application, the user needs to enter the notification management interface of the application to close the notification reminding function of the application, and the operation is complicated; when the notification reminding function of a certain application is closed, the terminal equipment does not remind any notification of the application under any condition; 2. if the user only wants to temporarily close the notification reminding function of a certain application, for example, the notification reminding function of the WeLink application is closed in the game playing process, the user needs to enter the notification management interface of the WeLink application first to close the notification reminding function of the WeLink application, and after the game is finished, the user needs to enter the notification management interface of the WeLink application again to open the notification reminding function of the WeLink application, so that the operation is complicated; and the situation that the user forgets to start the notification reminding function of the WeLink application after the game is finished easily exists, so that the user cannot receive the notification reminding of the WeLink application after the game is finished.

Mode 2 provides a notification disturbance-free function for an application scenario on the basis of mode 1. The service can enable the terminal device to automatically start the notification disturbance-free mode every time the terminal device enters a target application scene (such as a game scene), and in the notification disturbance-free mode, the terminal device does not perform notification reminding on the notification of the application, or the terminal device performs notification reminding on the notification of the application in a mode (such as vibration) which does not disturb a user. In addition, the service also allows the user to set applications that need to be notified without disturbing in the target application scenario. For example, taking a game scene as an example, if a user starts a notification disturbance-free function for the game scene and applications that the user sets to implement notification disturbance-free in the game scene include a links application, the terminal device does not perform notification reminding on all received notifications of the links application every time the terminal device enters the game scene; or the terminal equipment only carries out notification reminding in a vibration mode when receiving the WeLink application.

However, this approach has the following drawbacks: 1. the notification disturbance-free mode is always in an open state in the whole process from the beginning of entering the target application scene by the terminal device to the end of exiting the target application scene by the terminal device, and the user sometimes does not want to receive the notification reminder of the application in the whole process that the terminal device is in the target application scene (such as in the whole game process), sometimes the user wants to receive the notification reminder of the application in a non-critical period (such as a game preparation stage) in the target application scene, and does not receive the notification reminder of the application in a critical period (such as after the game formally starts) in the target application scene; 2. the notification disturbance-free mode is automatically started after the terminal device enters the target application scene every time, and the user sometimes only wants to start the notification disturbance-free mode when the terminal device enters the target application scene (for example, only in a game), and does not start the notification disturbance-free mode when the terminal device enters the target application scene at other times, so that the notification of the application can be normally notified. As can be seen, the existing notification do-not-disturb function for application scenarios greatly reduces the flexibility of notification do-not-disturb.

Therefore, in the existing notification management mode, when a user has a requirement for temporarily managing the notification reminding function of the application, the user needs to enter the notification management interface corresponding to the application for operation first, and after the requirement is finished, the user needs to enter the notification management interface of the application again for operation, so that the operation is complicated, and the user cannot quickly close or open the notification reminding function of the application; the existing notification do-not-disturb function for an application scenario has low flexibility.

In order to solve the above technical problem, an embodiment of the present application provides a notification reminding method, where in a process of running a first application on a foreground, a terminal device receives a notification of a second application, and performs notification reminding for the notification of the second application; if the user thinks that the notification reminder of the second application interferes with the current use of the first application, the user can input a first operation aiming at the notification reminder when the terminal device performs the notification reminder on the second application, for example, if the terminal device performs the notification reminder on the second application in a banner form, the user can press the banner for a long time, and the operation of pressing the banner for a long time is the first operation aiming at the notification reminder. The terminal device stops the notification reminder, for example, hides the banner, when detecting a first operation of the notification reminder for the second application; and after the terminal equipment stops the notification reminding and before the first application exits from the foreground operation, if the terminal equipment receives the notification of the second application again, the terminal equipment does not perform the notification reminding on the second application any more. According to the scheme, on one hand, the terminal device does not perform notification reminding on the second application when the first application starts to run on the foreground, but performs notification reminding on the second application first, and does not perform notification reminding on the second application after detecting the first operation of the user for the notification reminding, namely, the terminal device can perform notification disturbance-free (namely, close the notification reminding of the second application) on the second application when the user needs in the process of running the first application on the foreground, so that the flexibility of notification disturbance-free is improved. On the other hand, in the process that the user uses the first application, if the user wants to close the notification reminder of the second application, the user only needs to input the first operation aiming at the notification reminder when the terminal device performs the notification reminder on the second application without exiting the first application, and then enters the notification management interface of the second application to perform the operation, so that the operation of closing the notification reminder function of the application by the user is simplified, and the notification reminder function of the second application can be quickly closed by the user.

The notification reminding method provided by the embodiment of the application can be applied to terminal devices such as mobile phones, tablet computers, wearable devices (such as smart watches, smart bracelets, smart glasses or smart jewelry and the like), vehicle-mounted devices, Augmented Reality (AR)/Virtual Reality (VR) devices, notebook computers, ultra-mobile personal computers (UMPCs), netbooks or Personal Digital Assistants (PDAs), and the specific types of the terminal devices are not limited at all.

Exemplarily, as shown in fig. 4, a schematic structural diagram of a terminal device provided in an embodiment of the present application is shown. 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 key 190, a motor 191, an indicator 192, a display 193, and a Subscriber Identification Module (SIM) card interface 194, and the like. The sensor module 180 may include a pressure sensor 180A, a gyro sensor 180B, an acceleration sensor 180C, a fingerprint sensor 180D, a touch sensor 180E, and the like.

It is to be understood that the illustrated structure of the embodiment of the present application does not constitute a specific limitation to the terminal device 100. In other embodiments of the present application, terminal device 100 may include more or fewer components than shown, or combine certain components, or split certain components, or a different arrangement of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

Processor 110 may include one or more processing units, such as: the processor 110 may include an Application Processor (AP), a modem processor, a Graphics Processing Unit (GPU), an Image Signal Processor (ISP), a controller, a video codec, a Digital Signal Processor (DSP), a baseband processor, and/or a neural-Network Processing Unit (NPU), etc. The different processing units may be separate devices or may be integrated into one or more processors.

Among them, the controller may be a neural center and a command center of the mobile terminal 100. The controller can generate an operation control signal according to the instruction operation code and the timing signal to complete the control of instruction fetching and instruction execution.

A memory may also be provided in processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that have just been used or recycled by the processor 110. If the processor 110 needs to reuse the instruction or data, it can be called directly from the memory. Avoiding repeated accesses reduces the latency of the processor 110, thereby increasing the efficiency of the system.

In some embodiments, processor 110 may include one or more interfaces. The interface may include an integrated circuit (I2C) interface, an integrated circuit built-in audio (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 SIM interface, and/or a USB interface, etc.

The I2C interface is a bi-directional synchronous serial bus that includes a serial data line (SDA) and a Serial Clock Line (SCL). In some embodiments, processor 110 may include multiple sets of I2C buses. The processor 110 may be coupled to the touch sensor 180E, the charger, the flash, the camera 193, etc. through different I2C bus interfaces, respectively. For example: the processor 110 may be coupled to the touch sensor 180E through an I2C interface, such that the processor 110 and the touch sensor 180E communicate through an I2C bus interface to implement the touch function of the terminal device 100.

The I2S interface may be used for audio communication. In some embodiments, processor 110 may include multiple sets of I2S buses. The processor 110 may be coupled to the audio module 170 via an I2S bus to enable communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 may communicate audio signals to the wireless communication module 160 via the I2S interface, enabling answering of calls via a bluetooth headset.

The PCM interface may also be used for audio communication, sampling, quantizing and encoding analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 may be coupled by a PCM bus interface. In some embodiments, the audio module 170 may also transmit audio signals to the wireless communication module 160 through the PCM interface, so as to implement a function of answering a call through a bluetooth headset. Both the I2S interface and the PCM interface may be used for audio communication.

The UART interface is a universal serial data bus used for asynchronous communications. The bus may be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, a UART interface is generally used to connect the processor 110 with the wireless communication module 160. For example: the processor 110 communicates with a bluetooth module in the wireless communication module 160 through a UART interface to implement a bluetooth function. In some embodiments, the audio module 170 may transmit the audio signal to the wireless communication module 160 through a UART interface, so as to realize the function of playing music through a bluetooth headset.

The MIPI interface may be used to connect the processor 110 with peripheral devices such as a display screen 193, a camera 193, and the like. The MIPI interface includes a Camera Serial Interface (CSI), a Display Serial Interface (DSI), and the like. In some embodiments, processor 110 and camera 193 communicate through a CSI interface to implement the capture function of terminal device 100. The processor 110 and the display screen 193 communicate through the DSI interface to implement the display function of the terminal device 100.

The GPIO interface may be configured by software. The GPIO interface may be configured as a control signal and may also be configured as a data signal. In some embodiments, a GPIO interface may be used to connect the processor 110 with the camera 193, the display 193, the wireless communication module 160, the audio module 170, the sensor module 180, and the like. The GPIO interface may also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, and the like.

The USB interface 130 is an interface conforming to the USB standard specification, and may specifically be a Mini USB interface, a Micro USB interface, a USB Type C interface, or the like. The USB interface 130 may be used to connect a charger to charge the terminal device 100, and may also be used to transmit data between the terminal device 100 and a peripheral device. And the earphone can also be used for connecting an earphone and playing audio through the earphone. The interface may also be used to connect other terminal devices, such as AR devices and the like.

It should be understood that the interface connection relationship between the modules illustrated in the embodiment of the present application is only an exemplary illustration, and does not constitute a limitation on the structure of the terminal device 100. In other embodiments of the present application, the terminal device 100 may also adopt different interface connection manners or a combination of multiple interface connection manners in the above embodiments.

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 embodiments, the charging management module 140 may receive charging input from a wired charger via the USB interface 130. In some wireless charging embodiments, the charging management module 140 may receive a wireless charging input through a wireless charging coil of the terminal device 100. The charging management module 140 may also supply power to the terminal device through the power management module 141 while charging the battery 142.

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 charge management module 140, and supplies power to the processor 110, the internal memory 121, the display 193, the camera 193, the wireless communication module 160, and the like. The power management module 141 may also be used to monitor parameters such as battery capacity, battery cycle count, battery state of health (leakage, impedance), etc. In some other embodiments, the power management module 141 may also be disposed in the processor 110. In other embodiments, the power management module 141 and the charging management module 140 may be disposed in the same device.

The wireless communication function of the terminal device 100 may be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, a modem processor, a baseband processor, and the like.

The antennas 1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in terminal device 100 may be used to cover a single or multiple communication bands. Different antennas can also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may be multiplexed as a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 may provide a solution including 2G/3G/4G/5G wireless communication applied on 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), and the like. The mobile communication module 150 may receive the electromagnetic wave from the antenna 1, filter, amplify, etc. the received electromagnetic wave, and transmit the electromagnetic wave to the modem processor for demodulation. The mobile communication module 150 may also amplify the signal modulated by the modem processor, and convert the signal into electromagnetic wave through the antenna 1 to radiate the electromagnetic wave. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the same device as at least some of the modules of the processor 110.

The modem processor may include a modulator and a demodulator. The modulator is used for modulating a low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then passes the demodulated low frequency baseband signal to a baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and then transferred 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 193. In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be provided in the same device as the mobile communication module 150 or other functional modules, independent of the processor 110.

The wireless communication module 160 may provide a solution for wireless communication applied to the terminal device 100, including Wireless Local Area Networks (WLANs) (e.g., wireless fidelity (Wi-Fi) networks), bluetooth (bluetooth, BT), Global Navigation Satellite System (GNSS), Frequency Modulation (FM), Near Field Communication (NFC), Infrared (IR), and the like. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, performs frequency modulation and filtering processing on electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, perform frequency modulation and amplification on the signal, and convert the signal into electromagnetic waves through the antenna 2 to radiate the electromagnetic waves.

In some embodiments, the antenna 1 of the terminal device 100 is coupled to the mobile communication module 150 and the antenna 2 is coupled to the wireless communication module 160 so that the terminal device 100 can communicate with the network and other devices through wireless communication technology. The wireless communication technology may include global system for mobile communications (GSM), General Packet Radio Service (GPRS), code division multiple access (code division multiple access, CDMA), Wideband Code Division Multiple Access (WCDMA), time-division code division multiple access (time-division code division multiple access, TD-SCDMA), Long Term Evolution (LTE), LTE, BT, GNSS, WLAN, NFC, FM, and/or IR technologies, etc. The GNSS may include a Global Positioning System (GPS), a global navigation satellite system (GLONASS), a beidou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS), and/or a Satellite Based Augmentation System (SBAS).

The terminal device 100 implements a display function by the GPU, the display screen 193, and the application processor, etc. The GPU is a microprocessor for image processing, and is connected to a display screen 193 and an 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 alter display information.

The display screen 193 is used to display images, video, and the like. The display screen 193 includes a display panel. The display panel may adopt a Liquid Crystal Display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (active-matrix organic light-emitting diode, AMOLED), a flexible light-emitting diode (FLED), a miniature, a Micro-oeld, a quantum dot light-emitting diode (QLED), and the like. In some embodiments, the terminal device 100 may include 1 or N display screens 193, where N is a positive integer greater than 1.

The terminal device 100 may implement a video recording or playing function through a video codec.

Video codecs are used to compress or decompress digital video. The terminal device 100 may support one or more video codecs. In this way, the terminal device 100 can play or record video in a plurality of encoding formats, such as: moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, and the like.

The external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to extend the storage capability of the terminal device 100. The external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function. For example, files such as music, video, etc. are saved in an external memory card.

The internal memory 121 may be used to store computer-executable program code, which includes instructions. The internal memory 121 may include a program storage area and a data storage area. The storage program area may store an operating system, an application program (such as a sound playing function, an image playing function, etc.) required by at least one function, and the like. The storage data area may store data (such as audio data, a phonebook, etc.) created during use of the terminal device 100, and the like. In addition, the internal memory 121 may include a high-speed random access memory, and may further include a nonvolatile memory, such as at least one magnetic disk storage device, a flash memory device, a universal flash memory (UFS), and the like. The processor 110 executes various functional applications of the terminal device 100 and data processing by executing instructions stored in the internal memory 121 and/or instructions stored in a memory provided in the processor.

The terminal device 100 may implement an audio function through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the earphone interface 170D, and the application processor. Such as music playing, recording, etc.

The audio module 170 is used to convert digital audio information into an analog audio signal output and also to convert an analog audio input into a digital audio signal. The audio module 170 may also be used to encode and decode audio signals. In some embodiments, the audio module 170 may be disposed in the processor 110, or some functional modules of the audio module 170 may be disposed in the processor 110.

The speaker 170A, also called a "horn", is used to convert the audio electrical signal into an acoustic signal. The terminal device 100 can listen to music through the speaker 170A, or listen to a handsfree call.

The receiver 170B, also called "earpiece", is used to convert the electrical audio signal into an acoustic signal. When the terminal device 100 answers a call or voice information, it is possible to answer a voice by bringing the receiver 170B close to the human ear.

The microphone 170C, also referred to as a "microphone," is used to convert sound signals into electrical signals. When making a call or transmitting voice information, the user can input a voice signal to the microphone 170C by speaking the user's mouth near the microphone 170C. The terminal device 100 may be provided with at least one microphone 170C. In other embodiments, the terminal device 100 may be provided with two microphones 170C, which may implement a noise reduction function in addition to collecting sound signals. In other embodiments, the terminal device 100 may further include three, four or more microphones 170C to collect sound signals, reduce noise, identify sound sources, and implement directional recording functions.

The headphone interface 170D is used to connect a wired headphone. The headset interface 170D may be the USB interface 130, or may be an Open Mobile Terminal Platform (OMTP) standard interface of 3.5mm, or a cellular telecommunications industry association (cellular telecommunications industry association of the USA, CTIA) standard interface.

The pressure sensor 180A is used for sensing a pressure signal, and converting the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A may be disposed on the display screen 193. The pressure sensor 180A can be of a wide variety, such as a resistive pressure sensor, an inductive pressure sensor, a capacitive pressure sensor, and the like. The capacitive pressure sensor may be a sensor comprising at least two parallel plates having an electrically conductive material. When a force acts on the pressure sensor 180A, the capacitance between the electrodes changes. The terminal device 100 determines the intensity of the pressure from the change in the capacitance. When a touch operation is applied to the display screen 193, the terminal device 100 detects the intensity of the touch operation based on the pressure sensor 180A. The terminal device 100 may also calculate the touched position from the detection signal of the pressure sensor 180A. In some embodiments, the touch operations that are applied to the same touch position but different touch operation intensities may correspond to different operation instructions. For example: and when the touch operation with the touch operation intensity smaller than the first pressure threshold value acts on the short message application icon, executing an instruction for viewing the short message. And when the touch operation with the touch operation intensity larger than or equal to the first pressure threshold value acts on the short message application icon, executing an instruction of newly building the short message.

The gyro sensor 180B may be used to determine the motion attitude of the terminal device 100. In some embodiments, the angular velocity of terminal device 100 about three axes (i.e., x, y, and z axes) may be determined by gyroscope sensor 180B. The gyro sensor 180B may be used for photographing anti-shake. Illustratively, when the shutter is pressed, the gyro sensor 180B detects the shake angle of the terminal device 100, calculates the distance to be compensated for by the lens module according to the shake angle, and allows the lens to counteract the shake of the terminal device 100 through a reverse movement, thereby achieving anti-shake. The gyroscope sensor 180B may also be used for navigation, somatosensory gaming scenes.

The acceleration sensor 180C can detect the magnitude of acceleration of the terminal device 100 in various directions (generally, three axes). The magnitude and direction of gravity can be detected when the terminal device 100 is stationary. The method can also be used for recognizing the posture of the terminal equipment, and is applied to horizontal and vertical screen switching, pedometers and other applications.

The touch sensor 180E is also referred to as a "touch device". The touch sensor 180E may be disposed on the display screen 193, and the touch sensor 180E and the display screen 193 form a touch screen, which is also called a "touch screen". The touch sensor 180E is used to detect a touch operation applied thereto or nearby. The touch sensor can communicate the detected touch operation to the application processor to determine the touch event type. Visual output related to touch operations may be provided through the display 193. In other embodiments, the touch sensor 180E may be disposed on the surface of the terminal device 100 at a different position than the display screen 193.

The keys 190 include a power-on key, a volume key, and the like. The keys 190 may be mechanical keys. Or may be touch keys. The terminal device 100 may receive a key input, and generate a key signal input related to user setting and function control of the terminal device 100.

The motor 191 may generate a vibration cue. The motor 191 may be used for incoming call vibration cues, as well as for touch vibration feedback. For example, touch operations applied to different applications (e.g., photographing, audio playing, etc.) may correspond to different vibration feedback effects. The motor 191 may also respond to different vibration feedback effects for touch operations applied to different areas of the display screen 193. Different application scenarios (e.g. time alert, receiving information, alarm clock, game, etc.) may also correspond to different vibration feedback effects. The touch vibration feedback effect may also support customization.

Indicator 192 may be an indicator light that may be used to indicate a state of charge, a change in charge, or a message, missed call, notification, etc.

The SIM card interface 194 is used to connect a SIM card. The SIM card can be brought into and out of contact with the terminal device 100 by being inserted into the SIM card interface 194 or being pulled out from the SIM card interface 194. The terminal device 100 may support 1 or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 194 may support a Nano SIM card, a Micro SIM card, a SIM card, etc. Multiple cards can be inserted into the same SIM card interface 194 at the same time. The types of the plurality of cards may be the same or different. The SIM card interface 194 may also be compatible with different types of SIM cards. The SIM card interface 194 may also be compatible with an external memory card. The terminal device 100 interacts with the network through the SIM card to implement functions such as communication and data communication. In some embodiments, the terminal device 100 employs eSIM, namely: an embedded SIM card. The eSIM card may be embedded in the terminal device 100 and cannot be separated from the terminal device 100.

It should be understood that the mobile phone, as a terminal device, may include all the hardware structures described above, or include some of the hardware structures above, or have more other hardware structures not listed above, and this is not limited in this embodiment of the application.

It should also be understood that the mobile phone may adopt a software system such as a layered architecture, a dammony system (Harmony OS) architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture as the terminal device.

The above describes the hardware structure that the mobile phone may have, and the mobile phone will be layered

The system is an example for illustration. Fig. 5 is a schematic diagram of a software structure of a terminal device 100 according to an embodiment of the present application. As shown in fig. 5, the layered architecture divides the software into several layers, each layer having a clear role and division of labor. The layers communicate with each other through a software interface.

In some embodiments, the method will comprise

The system is divided into four layers, namely an application program layer, an application program framework layer, an Android runtime (Android runtime) and system library and a kernel layer from top to bottom.

The application layer may include a series of application packages. As shown in fig. 5, the application package may include applications such as camera, gallery, calendar, phone call, map, navigation, WLAN, bluetooth, music, video, short message, etc.

The application framework layer provides an Application Programming Interface (API) and a programming framework for the application program of the application layer. The application framework layer includes a number of predefined functions. As shown in FIG. 5, the application framework layers may include a window manager, content provider, view system, phone manager, resource manager, notification manager, and the like.

The window manager is used for managing window programs. The window manager can obtain the size of the display screen, judge whether a status bar exists, lock the screen, intercept the screen and the like.

The content provider is used to store and retrieve data and make it accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

The view system includes visual controls such as controls to display text, controls to display pictures, and the like. The view system may be used to build applications. The display interface may be composed of one or more views. For example, the display interface including the short message notification icon may include a view for displaying text and a view for displaying pictures.

The phone manager is used to provide the communication function of the terminal device 100. Such as management of call status (including on, off, etc.).

The resource manager provides various resources for the application, such as localized strings, icons, pictures, layout files, video files, and the like.

The notification manager enables applications to display notification information in the status bar, can be used to convey notification-type notifications, can disappear automatically after a short dwell, and does not require user interaction. Such as a notification manager used to inform download completion, notify reminders, etc. The notification manager may also be a notification that appears in the form of a chart or scroll bar text at the top status bar of the system, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialog window. For example, text information is prompted in the status bar, a prompt tone is given, the terminal device vibrates, an indicator light flickers, and the like.

Specifically, when receiving the notification of the second application in the target application scenario, the notification manager may determine whether the second application has the notification permission in the target application scenario. The notification manager may perform notification reminding for the notification of the second application when determining that the second application has the notification right in the target application scenario. And when determining that the second application does not have the notification right under the target application scene, the notification manager does not perform notification reminding on the second application.

After the notification manager performs notification reminding on the second application in the target application scene, a first operation performed on the notification reminding by the user can be detected. The notification manager stops the notification reminder in response to a first operation performed by the user on the notification reminder. After stopping the notification reminder, the notification manager does not perform notification reminder on the second application any more before the mobile phone exits the target application scenario. And after the mobile phone exits the target application scene, the notification manager recovers the notification reminding of the second application.

The operation of detecting whether the mobile phone is in the target application scene can be completed by the application framework layer.

The Android Runtime comprises a core library and a virtual machine. The Android runtime is responsible for scheduling and managing an Android system.

The core library comprises two parts: one part is a function which needs to be called by java language, and the other part is a core library of android.

The application layer and the application framework layer run in a virtual machine. And executing java files of the application program layer and the application program framework layer into a binary file by the virtual machine. The virtual machine is used for performing the functions of object life cycle management, stack management, thread management, safety and exception management, garbage collection and the like.

The system library may include a plurality of functional modules. For example: surface managers (surface managers), Media Libraries (Media Libraries), three-dimensional graphics processing Libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), and the like. The surface manager is used to manage the display subsystem and provide fusion of 2D and 3D layers for multiple applications.

The media library supports a variety of commonly used audio, video format playback and recording, and still image files, among others. The media library may support a variety of audio-video encoding formats, such as MPEG4, h.264, MP3, AAC, AMR, JPG, PNG, and the like.

The three-dimensional graphic processing library is used for realizing three-dimensional graphic drawing, image rendering, synthesis, layer processing and the like.

The 2D graphics engine is a drawing engine for 2D drawing.

The kernel layer is a layer between hardware and software. The inner core layer at least comprises a display driver, a camera driver, an audio driver and a sensor driver.

The notification reminding method provided by the embodiment of the application can be suitable for various application scenes in which the notification reminding function of the application (for example, the notification disturbance-free function is started) needs to be managed flexibly and quickly according to the user requirements, and can be suitable for scenes in which the user needs to close the notification reminding function of the application according to the self requirements in the process of playing games or watching videos through the terminal equipment. The following describes in detail a notification reminding method provided in the embodiments of the present application, taking a game scene as an example.

Taking a terminal device as a mobile phone as an example, in the process that a user uses the mobile phone to play the game application a, if the mobile phone receives a notification (for example, a first notification) of the application B, the mobile phone may first determine whether the application B has a notification permission in a game scene.

In one possible implementation manner, when the mobile phone is provided with only the notification management function for the application, the mobile phone may determine whether the application B has the notification authority in the game scene by detecting the on-off state of the notification alert function of the application B.

In one implementation manner, in one case, when the mobile phone detects that the notification reminding function of the application B is in an on state, the mobile phone determines that the application B has the notification permission in the game scene; in another case, when the mobile phone detects that the notification reminding function of the application B is in the off state, the mobile phone determines that the application B does not have the notification permission in the game scene.

In another possible implementation manner, when the mobile phone is provided with both the notification management function for the application and the notification do-not-disturb function for the game scenario, the mobile phone may determine whether the application B has the notification permission in the game scenario by detecting an on-off state of the notification reminder function of the application B and a list (which may be referred to as a first mask list) of applications that need to implement the notification do-not-disturb function in the game scenario, which is set by a user. The first mask list may be used to store an identifier of an application set by a user and required to implement notification of non-disturbing in a game scenario, for example, a name of the application or a package name of the application.

In one implementation manner, in one case, when the mobile phone detects that the notification reminding function of the application B is in an on state and the first shielding list does not include the identifier of the application B, the mobile phone determines that the application B has the notification permission in the game scene; under another condition, when the mobile phone detects that the notification reminding function of the application B is in an open state and the first shielding list comprises the identifier of the application B, the mobile phone determines that the application B does not have the notification permission in the game scene; in another case, when the mobile phone detects that the notification reminding function of the application B is in the off state, the mobile phone determines that the application B does not have the notification permission in the game scene.

For example, the mobile phone may determine the on-off state of the notification reminder function of the application B by detecting the position of the switch control of the "allow notification" column in the notification management interface of the application B. Taking application B as a weilink application as an example, as shown in (a) in fig. 3, when the mobile phone detects that the switch control 31 of the "allow notification" column in the notification management interface of the weilink application is in the off position, it determines that the notification alert function of the weilink application is in the off state. As shown in (b) in fig. 3, when detecting that the switch control 31 of the "allow notification" column in the notification management interface of the links application is in the on position, the mobile phone determines that the notification alert function of the links application is in the on state.

In one embodiment of the application, if the mobile phone determines that the application B has the notification permission in the game scene, the mobile phone performs notification reminding on the first notification of the application B. After the mobile phone performs notification reminding on the first notification of the application B, if the user thinks that the notification reminding will interfere with the current game playing process, the user may input a first operation for the notification reminding to instruct the mobile phone to stop the notification reminding, and no notification reminding is performed on the application B before the game is finished.

The mobile phone stops the notification reminder of the first notification for the application B in response to the first operation input by the user, and after the notification reminder is stopped, the mobile phone does not perform the notification reminder on the application B if the mobile phone receives the notification (for example, the second notification) of the application B before the game application A exits from the foreground of the mobile phone.

For example, in the process that the application a runs in the foreground of the mobile phone, for the first notification of the application B, the mobile phone may perform notification reminding on the first notification of the application B in the form of a banner, a warning sound, a ringtone, a vibration, or the like.

Wherein, the banner refers to the notification displayed in a floating manner at the top of the screen.

Taking the mobile phone to perform notification reminding on the first notification of the application B in the form of a banner as an example, as shown in fig. 6, the mobile phone is a schematic diagram of a user interface and an operation gesture performed by a user, which may be involved when performing notification reminding in the form of a banner. As shown in fig. 6 (a), the banner 61 for performing notification reminding on the first notification of the application B may include: an icon 611 of application B, a name 612 of application B, and content 613 of the first notification, and the like. In other examples, the receipt time 614 of the first notification may also be included in the banner 61. The time of receipt 614 of the first notification refers to the time when the handset received the first notification.

Correspondingly, when the mobile phone performs notification reminding on the first notification of the application B in the form of a banner, the first operation for the notification reminding may be a first touch gesture for the banner.

For example, the first touch gesture may be set by the user according to the operation habit of the user.

In one example, the first touch gesture may be a long press gesture as shown in (a) of fig. 6.

In yet another example, the first touch gesture may be a circling gesture as shown in fig. 6 (b).

In yet another example, the first touch gesture may be a tick gesture as shown in (c) of fig. 6.

Of course, the first touch gesture may also be other touch gestures, such as a double-tap gesture.

In a possible implementation manner, a touch detection point is set at any position in the area where the banner 61 is located, and a user may implement a first touch gesture at any position in the area where the banner 61 is located. When the mobile phone detects a first touch gesture performed by the user at any position in the area where the banner 61 is located, it is considered that a first operation of a notification reminder for the application B is detected.

In another possible implementation manner, touch detection points are provided in a target area in the area where the banner 61 is located. The user needs to perform a first touch gesture in the target area. When the mobile phone detects a first touch gesture performed by the user in the target area in the area where the banner 61 is located, it is considered that a first operation of a notification reminder for the application B is detected. For example, the target area may be an area where the icon 611 of the application B is located, or may be an area where the name 612 of the application B is located, or may be an area where the content 613 of the first notification is located, and the position of the target area is not particularly limited herein.

When the mobile phone performs notification reminding on the first notification of the application B in the form of a banner, the manner of stopping the notification reminding by the mobile phone may be: and hiding the banner corresponding to the notification reminder.

In another possible implementation manner, in order to prevent the user from performing a misoperation, when the mobile phone detects the first operation of the notification reminder for the first notification of the application B, the mobile phone may further ask the user whether to confirm the notification authority for closing the application B. The mobile phone stops the notification reminding after detecting an instruction which is input by a user and confirms to close the notification authority of the application B, and does not perform notification reminding on the application B any more after stopping the notification reminding and before the application A exits from the foreground operation. After the mobile phone detects the instruction of not closing the notification permission of the application B input by the user, the mobile phone continues to perform notification reminding on the application B.

Illustratively, as shown in fig. 7, a schematic view of a user interface when a first operation of a notification reminder for a first notification is detected for a mobile phone is shown. As shown in (a) of fig. 7, if the mobile phone detects a circling gesture for the banner 61 corresponding to the first notification of the application B, as shown in (B) of fig. 7, the mobile phone may display the query box 71 in the current user interface, for example, the query box 71 may be displayed below the banner 61, or the query box 71 may be displayed over the banner 61, where the display position of the query box 71 is not particularly limited. The query box 71 may include: query information 711, a first control 712, a second control 713, and so on. The first control 712 is used for the user to input an indication of the notification authority for not closing the application B to the mobile phone, and the second control 713 is used for inputting an indication of the notification authority for closing the application B to the mobile phone.

For example, query information 711 may be "do to continue receiving notification alerts for application B? ", the contents of the first control 712 may be" continue to receive ", and the contents of the second control 713 may be" close ". When the user clicks the first control 712, the mobile phone confirms that the indication of the notification permission of not closing the application B input by the user is detected; when the user clicks the second control 713, the handset confirms detection of the user-entered indication of notification permission to close application B.

In another possible implementation manner, after the mobile phone performs the notification reminder on the first notification of the application B, the user may further input another operation for the notification reminder to instruct the mobile phone to perform corresponding other processing on the notification reminder.

In one example, the user may instruct the handset to stop the notification reminder by entering a second operation of the notification reminder for the first notification of application B. For example, when the mobile phone performs notification reminding on the first notification of the application B in the form of a banner, the second operation may be a second touch gesture for the banner. The second touch gesture may also be set by the user according to the operation habit of the user, for example, the second touch gesture may include a left-sliding gesture, a right-sliding gesture, or a top-sliding gesture. Based on this, when the mobile phone detects that the user inputs the second operation in the area where the banner corresponding to the first notification is located, the banner can be hidden.

In another example, the user may instruct the cell phone to display the interface of application B in a floating window form by a third operation of entering a notification reminder for the first notification of application B. For example, when the mobile phone performs notification reminding on the first notification of the application B in the form of a banner, the third operation may be a third touch gesture for the banner. The third touch gesture may also be set by the user according to the operation habit of the user, for example, the third touch gesture may be a slide-down gesture.

Illustratively, as shown in fig. 8, a schematic view of a user interface involved in performing the third operation for the notification reminder of the first notification is shown. As shown in (a) in fig. 8, if the mobile phone detects that the user performs a slide-down gesture in the area where the banner 61 corresponding to the first notification is located, and the application B supports the floating display, as shown in (B) in fig. 8, the mobile phone may hide the banner 61 corresponding to the first notification and display an interface 81 of the application B in the form of a floating window. For example, the interface 81 may be a detail interface corresponding to the first notification in the application B, for example, if the first notification is from the contact a, the interface 81 may be a chat interface corresponding to the contact a. If the application B does not support the floating display, as shown in (c) in fig. 8, the mobile phone may display a prompt box 82 in the current interface, where the prompt box 82 may include first prompt information for prompting the user that the application B does not support the floating display. Illustratively, the first prompt message may be "application B does not support floating display".

In yet another example, the user may instruct the cell phone to display the detailed content of the first notification or instruct the cell phone to open application B by a fourth operation of inputting a notification reminder for the first notification of application B. For example, when the mobile phone performs notification reminding on the first notification of the application B in the form of a banner, the fourth operation may be a fourth touch gesture for the banner. The fourth touch gesture may also be set by the user according to the operation habit of the user, for example, the fourth touch gesture may be a click gesture.

Illustratively, as shown in fig. 9, a schematic view of a user interface involved in performing the fourth operation for the notification reminder of the first notification is shown. As shown in fig. 9 (a), when the cell phone shows the content 613 of the first notification in the banner 61 in a preview form (i.e., displays the preview content of the first notification), a detail indicator 615 may also be included in the banner 61. The user may instruct the handset to display the detailed content of the first notification by clicking on the area where the content 613 of the first notification is located or clicking on the details indicator 615. When the cellular phone detects that the user clicks on the area where the content 613 of the first notification is located or clicks on the detail indicator 615, as shown in (b) of fig. 9, the cellular phone may display the detailed content of the first notification in the banner 61, and at the same time, the cellular phone may turn the pointing direction of the detail indicator 615 to a direction toward the top of the screen. If the mobile phone detects that the user clicks the banner 61 again within a first time period after the detailed content of the first notification is displayed, the mobile phone may exit the application a and open the application B as shown in (c) in fig. 9. Within a first time period after the mobile phone displays the detailed content of the first notification, if no gesture operation is detected, the mobile phone may stop displaying the detailed content of the first notification and continue to display the preview content of the first notification in the banner 61. For example, the first preset time period may be 2 seconds, 3 seconds, 5 seconds, or the like, and is not particularly limited herein.

In another embodiment of the application, if the mobile phone determines that the application B does not have the notification authority in the game scene, the mobile phone does not remind the application B of the first notification.

The notification reminding method provided by the embodiment of the application is introduced in combination with the application scenario and the accompanying drawings. In order to better understand the notification reminding method provided by the embodiment of the application, specific implementation processes thereof are exemplarily described below with reference to the accompanying drawings.

Exemplarily, as shown in fig. 10, a schematic flowchart of a notification reminding method provided in an embodiment of the present application is provided, and an execution subject of each step in the flowchart may be a terminal device in the above embodiment, for example, a mobile phone. Specifically, the notification reminding method may include S1001 to S1003, which are detailed as follows:

s1001: and in the process of foreground running of the first application, carrying out notification reminding aiming at the first notification of the second application.

S1002: stopping the notification reminder when a first operation for the notification reminder is detected.

The first application and the second application may be the same application or may be different applications. Namely, in the process that the mobile phone runs the first application in the foreground, the mobile phone can receive the notification of the first application and carry out notification reminding on the notification of the first application; the mobile phone can also receive the notifications of other applications except the first application and carry out notification reminding on the notifications of the other applications.

In a specific embodiment, in the process that the first application runs in the foreground of the mobile phone, if the mobile phone receives the first notification of the second application, the mobile phone may first determine whether the second application has the notification permission in the target application scene.

The target application scene refers to an application scene where the mobile phone is located when the first application runs in the foreground of the mobile phone. For example, the target application scene corresponding to the game application a when the game application a runs in the foreground of the mobile phone is the game scene, and the target application scene corresponding to the video application C when the video application C runs in the foreground of the mobile phone is the video scene.

It should be noted that, the manner of determining whether the second application has the notification permission in the target application scenario by the mobile phone may specifically refer to the related description of the application scenario introduction part, and details are not described here again. In reference, the first application may correspond to the game application a of the application scenario introduction part, and the second application may correspond to the application B of the application scenario introduction part.

In a possible implementation manner, if the mobile phone determines that the second application has the notification permission in the target application scene, the mobile phone performs notification reminding on the first notification of the second application received by the mobile phone.

Specifically, the mobile phone may perform notification reminding on the first notification based on a preset notification reminding strategy. The preset notification reminding strategy can be set by the user, for example, the preset notification reminding strategy can be: and carrying out notification reminding in a banner form, or carrying out notification reminding in a banner combined with a prompt tone form and the like. The preset notification alert policy is not particularly limited herein.

It should be noted that, the manner in which the mobile phone performs the notification reminder for the first notification of the second application may also refer to the related description of the application scenario introduction part, and details are not repeated here.

In another possible implementation manner, if the mobile phone determines that the second application does not have the notification permission in the target application scenario, the mobile phone does not perform notification reminding on the first notification of the second application.

After the mobile phone performs the notification reminder for the first notification of the second application, if the user does not want to receive the notification of the second application any more, the user may input a first operation of the notification reminder for the first notification. The mobile phone stops the notification reminder for the first notification when detecting a first operation of the notification reminder for the first notification, which is input by a user.

It should be noted that, the specific manner in which the mobile phone stops the notification reminder for the first notification may also refer to the related description of the application scenario introduction part, and details are not described here again.

S1003: after stopping the notification reminder, not performing the notification reminder on the second application before the first application exits from the foreground operation.

After stopping the notification prompt of the first notification and before the first application exits from the foreground operation, the mobile phone does not perform the notification prompt on the second application, and specifically, the notification prompt can be implemented in the following two ways:

in the method 1, after detecting a first operation of a notification reminder for a first notification, the mobile phone adds an identifier of a second application to a first shielding list, and marks the second application in the first shielding list. Wherein the first mask list is used for storing the identification of the application which needs to implement the notification non-disturbing under the target application scene.

Based on this, before the first application exits from the foreground operation, if the mobile phone receives the second notification of the second application, the mobile phone may detect whether the first mask list includes the identifier of the second application. If the mobile phone determines that the first shielding list comprises the identifier of the second application, the mobile phone does not perform notification reminding on the second application; and if the mobile phone determines that the identification of the second application is not included in the screening list, the mobile phone carries out notification reminding aiming at the second notification of the second application.

For example, the notification reminding mode of the mobile phone for the second notification can be the same as the notification reminding mode of the mobile phone for the first notification. For example, the mobile phone may remind the first notification and the second notification of the second application in a banner.

For example, the identifier of the second application may be a name of the second application, or a package name of the second application, etc.

Illustratively, as shown in table 1, at least an identification field and a temporary flag bit field of an application may be included in the first masked list. The value of the temporary flag bit may include a first preset value (e.g., true) and a second preset value (e.g., false). The first preset value is used to indicate that the application is an application that needs to implement the notification do-not-disturb in the target period (i.e., needs to temporarily implement the notification do-not-disturb). The starting time of the target time period may be a time when the mobile phone detects a first operation of the notification reminder for the first notification, and the ending time of the target time period may be a time when the first application exits from a foreground of the mobile phone. The second preset value is used for indicating that the application is an application which needs to implement notification non-disturbance in the whole process that the mobile phone is in the target application scene.

Based on this, the mobile phone marks the second application in the first mask list, which may include: and setting the value of the temporary flag bit of the second application to be a first preset value. For example, if the second application is a weilink application, as shown in table 1, the mobile phone may add its name "weilink" to the first mask list, and set the value of its corresponding temporary flag to true.

TABLE 1

Identification of applications	Temporary markSign position
		Huashi sports	false
……	……
		WeLink	true

For example, the detecting, by the mobile phone, whether the identifier of the second application is included in the first screening list may include: and traversing the identifiers of the applications stored in the first shielding list by the mobile phone. If the identifier of the application stored in the first screening list comprises the identifier of the second application, the mobile phone determines that the first screening list comprises the identifier of the second application; and if the identification of the second application is not included in the identifications of the applications stored in the first screening list, the mobile phone determines that the identification of the second application is not included in the first screening list.

In the method 2, after detecting the first operation of the notification reminder for the first notification, the mobile phone may add the identifier of the second application to the second masked list. Wherein the second masked list is used to store applications that need to be implemented for notification immunity during the target time period (i.e., that need to be implemented temporarily). The starting time of the target time period may be a time when the mobile phone detects a first operation of the notification reminder for the first notification, and the ending time of the target time period may be a time when the first application exits from a foreground of the mobile phone.

For example, the detecting, by the mobile phone, whether the second masked list includes the identifier of the second application may include: and traversing the identifiers of the applications stored in the second shielding list by the mobile phone. If the identifier of the application stored in the second screening list includes the identifier of the second application, the mobile phone determines that the second screening list includes the identifier of the second application; and if the identification of the second application is not included in the identifications of the applications stored in the second screening list, the mobile phone determines that the identification of the second application is not included in the second screening list.

As can be seen from the above, in the notification reminding method provided in this embodiment, on one hand, the terminal device does not perform notification reminding on the second application when the first application starts to run in the foreground, but performs notification reminding on the second application first, and does not perform notification reminding on the second application after detecting the first operation of the user for the notification reminding, that is, the terminal device may perform notification disturbance avoidance on the second application (that is, close the notification reminding of the second application) when the user needs it in the process of running the first application in the foreground, so that the flexibility of notification disturbance avoidance is improved. On the other hand, in the process that the user uses the first application, if the user wants to close the notification reminder of the second application, the user only needs to input the first operation aiming at the notification reminder when the terminal device performs the notification reminder on the second application without exiting the first application, and then enters the notification management interface of the second application to perform the operation, so that the operation of closing the notification reminder function of the application by the user is simplified, and the notification reminder function of the second application can be quickly closed by the user.

In another embodiment of the present application, as shown in fig. 11, after S1003, the notification reminding method may further include S1004, which is detailed as follows:

s1004: and after the first application exits from the foreground operation, recovering the notification reminding of the second application.

Illustratively, the first application exiting the foreground running of the handset may include, but is not limited to, the following two cases:

and in the case 1, the first application is switched from the foreground running of the mobile phone to the background running of the mobile phone.

And 2, the first application is closed by the user and exits from the foreground of the mobile phone.

In a possible implementation manner, if the mobile phone adds the identifier of the second application to the first masked list in the previous step and marks the second application in the first masked list, the recovering, by the mobile phone, the notification alert for the second application may include: and when the first application exits the foreground operation of the mobile phone, searching and deleting the marked identifier of the second application from the first shielding list. In the implementation mode, because the mobile phone deletes the identifier of the second application from the first shielding list when the first application exits from the foreground operation, the mobile phone can automatically recover the notification reminding of the second application after the first application exits from the foreground operation without entering the notification management interface of the second application to start the notification reminding function of the second application, so that the user operation is simplified, and the user can be prevented from missing the notification of the second application after the first application exits from the foreground operation.

In another possible implementation manner, if the mobile phone adds the identifier of the second application to the second masked list in the previous step, the recovering, by the mobile phone, the notification alert for the second application may include: and deleting the identifiers of all the applications in the second screening list when the first application exits from the foreground operation of the mobile phone. In this implementation manner, since the second mask list is only used to store the identifiers of the applications that need to temporarily implement the notification non-disturbing function, the mobile phone may directly delete the identifiers of all the applications in the second mask list after the first application exits from the foreground operation of the mobile phone. Compared with the previous implementation mode, the mobile phone does not need to search the application needing to be deleted in the shielding list, so that the mobile phone can quickly recover the notification reminding of the second application.

Therefore, on one hand, after the first application exits from the foreground of the mobile phone, the mobile phone does not need to enter the notification management interface of the second application for corresponding operation, so that the operation of starting the notification reminding function of the second application by the user is simplified; on the other hand, the mobile phone recovers the notification reminding of the second application, so that the situation that the user misses the notification of the second application after the first application exits from the foreground operation of the mobile phone can be avoided, namely, the mobile phone temporarily implements the notification disturbance-free reminding on the second application only in the process that the first application is operated in the foreground at this time, and the mobile phone can notify and remind the second application after the first application exits from the foreground operation or when the first application is operated in the foreground again after the mobile phone is operated, so that the disturbance-free reminding flexibility is improved, and the improvement of user experience is facilitated.

In a possible implementation manner, when the first application is any application installed on the mobile phone, the mobile phone may perform S1003 to S1004 after performing S1001 and S1002. Namely, the user can quickly start the notification reminding function of the application in the process of using any application installed on the mobile phone.

In another possible implementation manner, when the first application is a preset application, after the mobile phone has executed S1001 and S1002, S1003 to S1004 are executed. When the first application is not the preset application, the mobile phone does not execute S1003 to S1004 after executing S1001 and S1002. That is, the user can quickly close the notification alert function of the application only during the use of the preset application. The preset application may be customized by a user, for example, the preset application may include: game-like applications or video-like applications, etc.

In yet another embodiment of the present application, the first application is forced to exit the foreground due to an abnormal situation that the first application is forced to exit the foreground of the handset, for example, a dead halt of the handset. Therefore, in order to avoid the occurrence of the situation that the user cannot receive the notification reminder of the second application after the first application exits from the foreground operation due to the abnormal situation, in a possible implementation manner, if the mobile phone adds the identifier of the second application to the first mask list in the previous step, the mobile phone may detect whether the first mask list includes the marked application when initiating the notification management service. If the mobile phone detects that the first screening list comprises the marked applications, the mobile phone deletes the identifications of all the marked applications in the first screening list.

In another possible implementation manner, if the mobile phone adds the identifier of the second application to the second masked list in the previous step, the mobile phone may detect whether the identifier of the at least one application is included in the second masked list when the notification management service is initialized. And if the mobile phone detects that the second list comprises the identifier of at least one application, the mobile phone deletes the identifier of the at least one application in the second screening list.

For example, the mobile phone may initialize the notification management service when the mobile phone is powered on or when the mobile phone is restarted.

Therefore, the identifiers of the marked applications in the first shielding list or the identifiers of all the applications in the second shielding list can be deleted when the mobile phone initializes the notification management service every time, so that the situation that the user cannot receive the notification prompt of the second application after the first application exits from the foreground operation due to an abnormal situation can be avoided.

It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

Fig. 12 shows a block diagram of another terminal device provided in the embodiment of the present application, and for convenience of description, only a part related to the embodiment of the present application is shown.

As shown in fig. 12, the terminal device 120 may include: a first notification management unit 121, a second notification management unit 122, and a third notification management unit 123. Wherein:

the first notification management unit 121 is configured to perform notification reminding for a first notification of a second application in a process that a first application runs in the foreground.

The second notification management unit 122 is configured to stop the notification reminder when detecting a first operation for the notification reminder;

the third notification management unit 123 is configured to not perform notification reminding on the second application after stopping the notification reminding and before the first application exits from the foreground operation.

In a possible implementation manner, the terminal device further includes:

In a possible implementation manner, the first notification management unit 121 specifically includes:

In a possible implementation manner, the second application having the notification permission in the target application scenario includes: and the notification reminding function of the second application is in an open state.

In a possible implementation manner, the second application having the notification permission in the target application scenario includes: and the notification reminding function of the second application is in an open state, a first shielding list does not comprise the identifier of the second application, and the first shielding list is used for storing the identifier of the application needing to implement notification without disturbance in the target application scene.

In a possible implementation manner, the first notification management unit 121 is further configured to:

In a possible implementation manner, the second application does not have the notification authority in the target application scenario, including: and the notification reminding function of the second application is in a closed state.

In a possible implementation manner, the second application does not have the notification authority in the target application scenario, including: and the notification reminding function of the second application is in an open state, a first shielding list comprises the identifier of the second application, and the first shielding list is used for storing the identifier of the application needing to implement notification without disturbance in the target application scene.

In a possible implementation manner, the terminal device further includes:

and the first application management unit is used for adding the identifier of the second application to the first shielding list and marking the second application in the first shielding list.

Correspondingly, the third notification management unit 123 is specifically configured to:

In a possible implementation manner, the terminal device further includes:

a second application management unit, configured to add an identifier of the second application to a second mask list, where the second mask list is used to store an identifier of an application that needs to implement notification without disturbing in a target time period, a start time of the target time period is a time when the first operation is detected, and a termination time of the target time period is a time when the first application exits from the foreground operation.

In a possible implementation manner, the third notification management unit 123 is specifically configured to:

It should be noted that, for the information interaction, execution process, and other contents between the above-mentioned devices/units, the specific functions and technical effects thereof are based on the same concept as those of the embodiment of the method of the present application, and specific reference may be made to the part of the embodiment of the method, which is not described herein again.

The embodiments of the present application further provide a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the computer program implements the steps that can be implemented in the above method embodiments.

The embodiments of the present application provide a computer program product, which when running on a terminal device, enables the terminal device to implement the steps in the above method embodiments when executed.

Embodiments of the present application further provide a chip system, where the chip system includes a processor, the processor is coupled with a memory, and the processor executes a computer program stored in the memory to implement the methods according to the above method embodiments. The chip system can be a single chip or a chip module consisting of a plurality of chips.

In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment. It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

Finally, it should be noted that: the above description is only an embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A notification reminding method is characterized by comprising the following steps:

2. The method of claim 1, wherein after the not alerting the second application, the method further comprises:

3. The method according to claim 1 or 2, wherein the first application performs notification reminding for the first notification of the second application in the process of running in the foreground, and the method comprises:

4. The method of claim 3, wherein the second application has notification rights in a target application scenario, comprising:

and the notification reminding function of the second application is in an open state.

5. The method of claim 3, wherein the second application has notification rights in a target application scenario, comprising:

and the notification reminding function of the second application is in an open state, a first shielding list does not comprise the identifier of the second application, and the first shielding list is used for storing the identifier of the application needing to implement notification without disturbance in the target application scene.

6. The method according to any one of claims 1 to 5, further comprising:

7. The method of claim 6, wherein the second application does not have notification authority in a target application scenario, and wherein the notification authority comprises:

and the notification reminding function of the second application is in a closed state.

8. The method of claim 6, wherein the second application does not have notification authority in a target application scenario, and wherein the notification authority comprises:

and the notification reminding function of the second application is in an open state, a first shielding list comprises the identifier of the second application, and the first shielding list is used for storing the identifier of the application needing to implement notification without disturbance in the target application scene.

9. The method of claim 5 or 8, wherein after the detecting the first operation for the notification alert, the method further comprises:

10. The method of claim 9, wherein resuming notification alerts of the second application after the first application exits the foreground operation comprises:

11. The method of claim 5, 8, 9 or 10, further comprising:

12. The method of any of claims 1-4 or 6-7, wherein after the detecting the first operation for the notification alert, the method further comprises:

13. The method of claim 12, wherein resuming notification alerts of the second application after the first application exits the foreground operation comprises:

14. The method according to claim 12 or 13, characterized in that the method further comprises:

15. The method of any of claims 1 to 14, wherein the not alerting the second application after stopping the notification alert and before the first application exits from the foreground running comprises:

16. A terminal device, comprising:

17. A terminal device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the notification alert method according to any one of claims 1 to 15 when executing the computer program.

18. A computer-readable storage medium, in which a computer program is stored, which, when being executed by a processor, implements a notification alert method according to any one of claims 1 to 15.

19. A computer program product, characterized in that when the computer program product is run on a computer, the computer performs the notification alert method according to any one of claims 1 to 15.