WO2022052878A1

WO2022052878A1 - Method for managing push message, and related apparatus

Info

Publication number: WO2022052878A1
Application number: PCT/CN2021/116551
Authority: WO
Inventors: 顾启蒙; 黄文�; 朱小陆
Original assignee: 华为技术有限公司
Priority date: 2020-09-14
Filing date: 2021-09-03
Publication date: 2022-03-17
Also published as: CN114268663A

Abstract

Disclosed are a method for managing a push message, and a related apparatus. The method comprises: a terminal device acquiring usage information of a target application within a statistical period; sending the usage information of the target application to a push server; receiving a query message sent by the push server, wherein the query message is used for querying whether a user requires a push message of the target application to be blocked; detecting a first operation of the user for the query message, wherein the first operation is used for determining that the user requires the push message of the target application to be blocked; and in response to the first operation, sending a confirmation message to the push server, wherein the confirmation message is used for indicating that the push server is prohibited from sending the push message of the target application to the terminal device. By means of the embodiments of the present application, user operations can be reduced, an actual requirement of a user can be met, and power consumption can be effectively reduced.

Description

Push message management method and related device

This application claims the priority of the Chinese patent application with the application number of 202010959214.7 and the application title of "Management Method for Pushing Messages and Related Apparatus", which was filed with the China Patent Office on September 14, 2020, the entire contents of which are incorporated herein by reference. middle.

technical field

The present application relates to the field of electronic technologies, and in particular, to a push message management method and related devices.

Background technique

At present, there are more and more mobile phone software, and almost all applications have a message push function. Mobile phones receive push messages frequently, resulting in more and more messages in the mobile phone notification bar. However, many push messages are not of interest to users, so users cannot see them in time. Useful information will also cause the phone to wake up frequently, affecting the power consumption of the phone.

Currently, there are two main methods for managing mobile phone push messages: manual setting and automatic blocking. Manual setting means that in the notification management interface of the mobile phone, the user manually sets each application individually, which is rather cumbersome; automatic blocking means that the mobile phone automatically blocks messages directly according to the system settings. This method is to perform corresponding processing after the mobile phone receives the push message of the application. The mobile phone has received the push message but does not display it, which still affects the power consumption of the mobile phone.

SUMMARY OF THE INVENTION

The embodiments of the present application provide a push message management method and a related device, which can reduce user operations, meet real needs of users, and effectively reduce power consumption.

In a first aspect, the present application provides a push message management method, the method includes: a terminal device obtains usage information of a target application in a statistical period; the terminal device sends the usage information of the target application to a push server; The terminal device receives the inquiry message sent by the push server; wherein, the inquiry message is used to inquire whether the user needs to block the push message of the target application; detect the user's first operation on the inquiry message; wherein, the The first operation is used to determine that the user needs to block the push message of the target application; the terminal device sends a confirmation message to the push server in response to the first operation; wherein the confirmation message is used to indicate the push The server prohibits sending the push message of the target application to the terminal device.

In this embodiment of the present application, by sending the usage information of the target application on the terminal device to the push server, the push server can make a decision on whether to send an inquiry message to the terminal device; the terminal device sends a confirmation message to the push server, so that the push server can directly Block push messages from the target app. It not only reduces user operations, but also satisfies the user's real needs by actively asking the user, and also prevents the terminal device from being frequently woken up, thereby effectively reducing the power consumption of the device.

The target application refers to an application with a message push function, and a push server can be used to push messages.

Based on the first aspect, in a possible embodiment, after the terminal device detects the user's first operation on the query message, the terminal device closes the notification of the target application in the notification management interface.

It can be seen that, in this embodiment of the present application, the user's first operation for the query message is automatically synchronized to the notification management setting interface on the terminal device, so that the user can locally query the push messages of which applications are blocked, reduce user operations, and satisfy the real needs of users.

In a specific embodiment, the usage information of the target application includes one or more of usage duration, usage times, message sending times, message clicks, ratio of message clicks to pushes, or the number of consecutively unclicked messages.

It can be seen that in the embodiment of the present application, the usage information of the target application is designed so that the usage information of the target application can be used to determine whether the target application is an application that is not commonly used, and the terminal device uses the usage information of the target application. It is sent to the push server, so that the push server can make corresponding judgments according to the usage information of the target application, which reduces user operations, meets real needs of users, and reduces power consumption of terminal devices.

In a specific implementation manner, the usage information of the target application includes one or more of usage duration, usage times, message sending times, message clicks, ratio of message clicks to pushes, or the number of consecutively unclicked messages, It also includes the identification of the target application and the identification of the terminal device.

It can be seen that, by designing the usage information of the target application in the embodiment of the present application, the usage information of the target application can be used to judge whether the target application is an application that is not commonly used; by introducing the identifier of the target application and the terminal The identification of the device, so that the usage information of the target application can also be used to distinguish different terminal devices and different applications. It is worth noting that the usage information of the target application can also be used as other judgment basis. The terminal device sends the use information of the target application to the push server, so that the push server can make corresponding judgments according to the use information of the target application, which reduces user operations, meets real needs of users, and reduces power consumption of the terminal device.

Based on the first aspect, in a possible embodiment, after the terminal device sends a confirmation message to the push server, the method further includes: the terminal device detects a second operation performed by the user on the notification management interface; wherein , the second operation is used to determine that the user needs to open the push message of the target application; the terminal device sends an open message to the push server in response to the second operation; wherein the open message is used to indicate The push server allows sending the push message of the target application to the terminal device.

It can be seen that by synchronizing the user's operation of manually setting the application restoration notification on the terminal device to the push server, the user can locally control the push server to restore the application push message, which reduces user operations and meets the user's real needs.

Based on the first aspect, in a possible embodiment, the statistical period is one of a system preset or a user setting.

If the statistical period preset by the system is adopted, the terminal device directly counts the usage information of the target application according to the statistical period; if the statistical period set by the user is adopted, the terminal device first obtains the statistical period input by the user, and then uses the statistical period set by the user in the statistical period set by the user. Inside, the usage information of the target application installed on the terminal device is counted, and then the usage information of the target application is sent to the push server.

For example, if the user inputs a statistical period of one week, the terminal device counts the usage information of the target application within one week, and sends the usage information of the target application to the push server.

It can be seen that the terminal device can perform statistics on usage information based on a statistical period preset by the system or a statistical period set by a user. If the statistical period set by the user is adopted, the user can set it reasonably according to their own needs, and the statistical period is controllable to meet the real needs of the user.

In a second aspect, an embodiment of the present application provides another push message management method, the method includes: a push server receives usage information of a target application from a terminal device; the push server, according to the usage information of the target application, Judging whether it is necessary to send an inquiry message to the terminal device; wherein, the inquiry message is used to inquire whether the user needs to block the push message of the target application; if it is determined that the inquiry message needs to be sent, the push server sends the sending an inquiry message to the terminal device; the push server receives a confirmation message from the terminal device; wherein the confirmation message is used to instruct the push server to prohibit sending the push message of the target application to the terminal device.

In this embodiment of the present application, by receiving the usage information of the target application from the terminal device, the push server can make a decision on whether to send an inquiry message to the terminal device; The push message of the target application described above reduces user operations, meets the real needs of users, and also prevents the terminal device from being frequently woken up, thereby effectively reducing the power consumption of the terminal device.

It can be seen that in the embodiment of the present application, the usage information of the target application is designed so that the usage information of the target application can be used to determine whether the target application is an application that is not commonly used, and the push server receives information from the terminal. The usage information of the target application of the device determines whether an inquiry message needs to be issued according to the usage information of the target application, which reduces user operations, meets real needs of users, and reduces power consumption of the terminal device.

It can be seen that, by designing the usage information of the target application in the embodiment of the present application, the usage information of the target application can be used to determine whether the target application is an uncommon application; by introducing the identifier of the target application and the The identification of the terminal device enables the use information of the target application to be used to distinguish different terminal devices and different target applications. It is worth noting that the usage information of the target application can also be used as other judgment basis. The push server receives the usage information of the target application from the terminal device, and makes corresponding judgments according to the usage information of the target application, which reduces user operations, meets real needs of users, and reduces power consumption of the terminal device.

Based on the second aspect, in a possible embodiment, after the push server receives the confirmation message from the terminal device, the method further includes: according to the confirmation message, the push server adds the pre-established whitelist to the The target application is deleted; wherein, the pre-established whitelist is a set of applications that are allowed to send push messages, including the mapping relationship between the terminal device and the application.

It can be seen that, through the confirmation message, the user's first operation on the query message is synchronized to the push server, and the push server deletes the target application in the pre-established white list, and then executes the application according to the modified white list. The list determines whether to allow the sending of push messages of the application, which reduces user operations, meets the real needs of users, and reduces the power consumption of terminal devices.

Based on the second aspect, in a possible embodiment, after the push server deletes the target application in the pre-established whitelist according to the confirmation message, the method further includes: the push server receives an application from an application The push message of the server; determine whether the application corresponding to the push message is in the white list; if the application corresponding to the push message is in the white list, send the push message to the terminal device; If the application corresponding to the push message is not in the white list, the push message is not sent to the terminal device.

It can be seen that, after receiving the push message from the application server, the push server decides whether to send the push message of the application to the terminal device according to whether the application corresponding to the push message is included in the whitelist, which reduces user operations and satisfies the user's reality. requirements to reduce the power consumption of terminal equipment.

Based on the second aspect, in a possible embodiment, after the push server receives the confirmation message from the terminal device, the method further includes: the push server adds to a pre-established blacklist according to the confirmation message The target application is added; wherein, the pre-established blacklist is a set of applications prohibited from sending push messages, including the mapping relationship between the terminal device and the application.

It can be seen that, through the confirmation message, the user's first operation on the query message is synchronized to the push server, and the push server adds the target application to the pre-established blacklist, and then according to the modified blacklist It is judged whether to prohibit sending push messages of the application, which reduces user operations, meets real needs of users, and reduces power consumption of terminal devices.

Based on the second aspect, in a possible embodiment, after the push server adds the target application to a pre-established blacklist according to the confirmation message, the method further includes: the push server receives data from the application server the push message; determine whether the application corresponding to the push message is in the blacklist; if the application corresponding to the push message is in the blacklist, the push message is not sent to the terminal device; If the application corresponding to the push message is not in the blacklist, the push message is sent to the terminal device.

It can be seen that, after receiving the push message from the application server, the push server decides whether to send the push message of the application to the terminal device according to whether the blacklist contains the application corresponding to the push message, which reduces user operations and satisfies the user's reality. requirements to reduce the power consumption of terminal equipment.

Based on the second aspect, in a possible embodiment, the push server determines whether it is necessary to send an inquiry message to the terminal device according to the usage information of the target application, including: when one or more of the following conditions are satisfied Next, it is determined that an inquiry message needs to be sent to the terminal device:

The usage duration of the target application is less than or equal to the usage duration threshold; or, the usage count of the target application is less than or equal to the usage count threshold; or, the message sending count of the target application is greater than the message sending count threshold; or, the The number of message clicks of the target application is less than or equal to the threshold of the number of message clicks; or, the ratio of the message clicks to the push volume of the target application is less than or equal to the threshold of the ratio of the message clicks to the push volume; The number of clicked messages is greater than the consecutive unclicked messages threshold.

It can be seen that by designing a method for judging whether to send an inquiry message, the push server can make a judgment based on the usage information of the target application, and when the conditions are met, send an inquiry message to the terminal device, reducing the need for User operation, meet the real needs of users, and reduce the power consumption of terminal equipment.

In a third aspect, an embodiment of the present application provides a terminal device, where the terminal device includes: an acquisition module for acquiring usage information of a target application in a statistical period; a sending module for sending the usage information of the target application to a push server; a receiving module, configured to receive an inquiry message sent by the push server; wherein the inquiry message is used to inquire whether the user needs to block the push message of the target application; a detection module is used to detect the user’s response to the inquiry The first operation of the message; wherein, the first operation is used to determine that the user needs to block the push message of the target application; the sending module is further configured to, in response to the first operation, send a confirmation message to the push The server; wherein the confirmation message is used to instruct the push server to prohibit sending the push message of the target application to the terminal device.

Each module of the shown terminal device is specifically used to implement the method described in the first aspect.

In a fourth aspect, an embodiment of the present application provides an apparatus, the apparatus includes: a receiving module for receiving usage information of a target application from a terminal device; a determining module for determining according to the usage information of the target application Whether it is necessary to send an inquiry message to the terminal device; wherein, the inquiry message is used to inquire whether the user needs to block the push message of the target application; the sending module is used to send the inquiry when it is determined to send the inquiry message message to the terminal device; the receiving module is further configured to receive a confirmation message from the terminal device; wherein the confirmation message is used to instruct the apparatus to prohibit sending the push of the target application to the terminal device information.

Each module of the shown device is specifically used to implement the method described in the second aspect.

In a fifth aspect, the embodiments of the present application provide another apparatus, the apparatus includes: a processor, a memory, and a transceiver; the processor, the memory, and the transceiver may be connected to each other through a bus, or may be integrated together. The processor is configured to read the program code stored in the memory, and execute the method described in any one of the embodiments of the first aspect.

In a sixth aspect, the embodiments of the present application provide yet another apparatus, the apparatus includes: a processor, a memory, and a transceiver; the processor, the memory, and the transceiver may be connected to each other through a bus, or may be integrated together. The processor is configured to read the program code stored in the memory, and execute the method described in any one of the embodiments of the second aspect.

In a seventh aspect, the embodiments of the present application provide yet another apparatus, the apparatus has a function of implementing the behavior of the terminal device in the above method aspect, and includes components for performing the steps or functions described in the above method aspect. The steps or functions can be implemented by software, or by hardware (eg, circuits), or by a combination of hardware and software.

In an eighth aspect, the embodiments of the present application provide another apparatus, the apparatus has the function of implementing the push server behavior in the above method aspect, and includes components for performing the steps or functions described in the above method aspect. The steps or functions can be implemented by software, or by hardware (eg, circuits), or by a combination of hardware and software.

In a ninth aspect, an embodiment of the present application provides a non-volatile computer-readable storage medium; the computer-readable storage medium is used to store an implementation code of any method of the first aspect or the second aspect.

In a tenth aspect, an embodiment of the present application provides a computer program product; the computer program product includes program instructions, and when the computer program product is executed by a computing device, executes any of the embodiments described in the first aspect or the second aspect. method. The computer program product may be a software installation package, and the computer program product may be downloaded and executed on the controller to implement the method described in any embodiment of the first aspect or the second aspect.

It should be understood that any of the above-mentioned aspects can be implemented together with any other aspect or aspects, and can also be implemented independently.

It can be seen that, in this embodiment of the present application, by sending the usage information of the target application on the terminal device to the push server, the push server can make a decision on whether to send an inquiry message to the terminal device; the push server sends an inquiry message to the terminal device to inquire Whether the user needs to block the push messages of the target application; the terminal device sends a confirmation message to the push server, so that the push server can directly block the push messages of the target application. Moreover, the embodiment of the present application uploads the opening message to the push server by detecting the user's operation of enabling the application notification on the terminal device, so that the user can control the push server to restore the push message of the application on the terminal device. It not only reduces user operations, but also meets the real needs of users, and can effectively reduce the power consumption of terminal equipment.

Description of drawings

1a-1e are schematic diagrams of a group of interfaces involved in the manual setting method provided by the embodiment of the present application;

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

3 is a schematic diagram of a software architecture provided by an embodiment of the present application;

4 is a schematic diagram of an interface provided by an embodiment of the present application;

5a-5c are schematic diagrams of a method for establishing an application list according to an embodiment of the present application;

6 is a schematic flowchart of a method for managing push messages according to an embodiment of the present application;

7 is a schematic flowchart of another push message management method provided by an embodiment of the present application;

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

FIG. 9 is a schematic structural diagram of a device provided by an embodiment of the present application;

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

FIG. 11 is a schematic structural diagram of an apparatus provided by an embodiment of the present application.

detailed description

The embodiments of the present application will be described below with reference to the accompanying drawings.

Currently, there are two common solutions for managing push messages: manual setting and automatic blocking. Manual setting means that in the notification management interface of the terminal device, the user manually sets each application individually; automatic shielding means that the terminal device directly and automatically blocks messages according to the system settings, and the user cannot choose. If the manual setting mode is adopted, the operation process of the terminal device by the user can be exemplarily referred to as FIG. 1a , FIG. 1b , FIG. 1c , FIG. 1d , and FIG. 1e . As shown in FIG. 1a, the terminal device displays an application menu interface 10, wherein the application menu interface 10 includes a setting control 11 and other controls (eg, a gallery control 12, a music control 13, etc.). The terminal device receives the user's input operation 14 (such as clicking) on the setting control 11, and the terminal device displays the setting interface 15 corresponding to the setting control 11. As shown in FIG. 1b, the setting interface 15 corresponding to the setting control includes a notification control 16 and other controls (eg WLAN control 17, mobile network control 18, etc.). The terminal device receives the user's input operation 19 for the notification control 16, and the terminal device displays a notification interface 20 corresponding to the notification control 16, as shown in FIG. Short video application control 21, map application control 22, etc.). Suppose the user wants to close the push message of the short video application, the user clicks the short video application control 21 on the notification interface 20, and the terminal device receives the user's click operation 23 on the short video application control 21, as shown in Figure 1d, the terminal device displays a short video The notification management interface 24 corresponding to the video application control 21 . Notification management interface 24 includes an enable notification control 25A and other controls. The terminal device receives the user's input operation 26 (for example, a click) for the permission notification control 25A, and in response to the input operation 26, the terminal device displays the notification management interface 24 as shown in FIG. Other controls, so far, the terminal device blocks the notification of the short video application.

It can be seen from the manual setting methods shown in Figure 1a, Figure 1b, Figure 1c, Figure 1d, and Figure 1e that if the user needs to block the push message of the application, the user needs to click the setting control first to display the setting interface, and then the user needs to click The notification control is used to display the notification interface, and then the user needs to click the application control corresponding to the application to be blocked to display the notification management interface of the application. Finally, the user needs to click the allow notification control to block the push message of the application. In this way, the user needs to go through multiple steps to close the push message of the application. There are many steps in the whole operation process, and the user has to manually set each application to be blocked separately. The operation process is complicated and affects the user experience.

If the automatic shielding method is adopted, the entire shielding process is performed by the terminal device, and the user cannot participate in the setting. The terminal device automatically determines the push message of the application that needs to be shielded according to the system setting, and then directly shields it, that is, the push message of the application is not displayed. information. In this way, users cannot choose independently, and may not necessarily meet the real needs of users. It should be noted that the two current common solutions of manual setting and automatic blocking are to block push messages on the terminal device. The push server still sends the push message of the application normally. After the terminal device receives the push message of the application, , and then make a corresponding judgment on whether to display the push message. Regardless of whether it is finally displayed, the terminal device will still receive the push message of the application. Frequently receiving push messages and performing the corresponding judgment operation locally will still greatly affect the power consumption of the terminal device. .

In view of the above problems, an embodiment of the present application provides a push message management method. Combined with a push server, the push server directly determines whether to send a push message to a terminal device, which can not only reduce user operations, but also meet the real needs of users, and also effectively Reduce power consumption of end devices.

The following describes a terminal device 100 involved in the embodiments of the present application.

Referring to FIG. 2, FIG. 2 is a schematic structural diagram of a terminal device 100 involved in an embodiment of the present application. The terminal device 100 may be a mobile phone, a tablet computer, a wearable device, a vehicle-mounted device, a notebook computer, etc., and this application does not limit the specific type of the terminal device.

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. Mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, sensor module 180, buttons 190, motor 191, indicator 192, camera 193, display screen 194, And a subscriber identification module (subscriber identification module, SIM) card interface 195 and so on. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a touch sensor 180I, an ambient light sensor 180J, and the like.

It can be understood that the structures illustrated in the embodiments of the present application do not constitute a specific limitation on the terminal device 100 . In other embodiments of the present application, the terminal device 100 may include more or less components than shown, or combine some components, or separate some components, or arrange different components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

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

The controller may be the nerve center and command center of the terminal device 100 . The controller can generate an operation control signal according to the instruction operation code and timing signal, and complete the control of fetching and executing instructions.

A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in processor 110 is cache memory. This memory may hold instructions or data that have just been used or recycled by the processor 110 . If the processor 110 needs to use the instruction or data again, it can be called directly from the memory. Repeated accesses are avoided and the latency of the processor 110 is reduced, thereby increasing the efficiency of the system.

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

It can be understood that the interface connection relationship between the modules illustrated in the embodiments of the present application is only a schematic illustration, and does not constitute a structural limitation of the terminal device 100 . In other embodiments of the present application, the terminal device 100 may also adopt different interface connection manners in the foregoing embodiments, or a combination of multiple interface connection manners.

The charging management module 140 is used to receive charging input from the charger. The charger may be a wireless charger or a wired charger.

The power management module 141 is used for connecting the battery 142 , the charging management module 140 and the processor 110 . The power management module 141 receives input from the battery 142 and/or the charging management module 140, and supplies power to the processor 110, the internal memory 121, the external memory, the display screen 194, the camera 193, and the wireless communication module 160.

The 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, the modulation and demodulation processor, the baseband processor, and the like.

The terminal device 100 implements a display function through a GPU, a display screen 194, an application processor, and the like. The GPU is a microprocessor for image processing, and is connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or alter display information.

Display screen 194 is used to display images, videos, and the like. Display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode or an active-matrix organic light-emitting diode (active-matrix organic light). emitting diode, AMOLED), flexible light-emitting diode (flex light-emitting diode, FLED), Miniled, MicroLed, Micro-oLed, quantum dot light-emitting diode (quantum dot light emitting diodes, QLED) and so on. In some embodiments, the terminal device 100 may include one or N display screens 194 , where N is a positive integer greater than one.

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

The ISP is used to process the data fed back by the camera 193 .

Camera 193 is used to capture still images or video. The object is projected through the lens to generate an optical image onto the photosensitive element. The photosensitive element may be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, and then transmits the electrical signal to the ISP to convert it into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. DSP converts digital image signals into standard RGB, YUV and other formats of image signals.

A digital signal processor is used to process digital signals, in addition to processing digital image signals, it can also process other digital signals. For example, when the terminal device 100 selects a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy, and the like.

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 videos in various encoding formats, such as: moving picture experts group (moving picture experts group, MPEG) 1, MPEG2, MPEG3, MPEG4 and so on.

The NPU is a neural-network (NN) computing processor. By drawing on the structure of biological neural networks, such as the transfer mode between neurons in the human brain, it can quickly process the input information, and can continuously learn by itself. Applications such as intelligent cognition of the terminal device 100 can be implemented through the NPU, such as image recognition, face recognition, speech recognition, text understanding, and the like.

The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the terminal device 100 . The external memory card communicates with the processor 110 through the external memory interface 120 to realize the data storage function.

Internal memory 121 may be used to store computer executable program code, which includes instructions. The processor 110 executes various functional applications and data processing of the terminal device 100 by executing the instructions stored in the internal memory 121 . The internal memory 121 may include a storage program area and a storage data area. The storage program area may store an operating system, an application required for at least one function (such as a fingerprint recognition function, etc.), and the like. The storage data area may store data created during the use of the terminal device 100 (such as usage information data of the target application, fingerprint information template, etc.) and the like. In addition, the internal memory 121 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, universal flash storage (UFS), and the like.

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

The audio module 170 is used for converting digital audio information into analog audio signal output, and also for converting analog audio input into digital audio signal.

Speaker 170A, also referred to as a "speaker", is used to convert audio electrical signals into sound signals.

The receiver 170B, also referred to as "earpiece", is used to convert audio electrical signals into sound signals.

The microphone 170C, also called "microphone" or "microphone", is used to convert sound signals into electrical signals.

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

The pressure sensor 180A is used to sense pressure signals, and can convert the pressure signals into electrical signals. In some embodiments, the pressure sensor 180A may be provided on the display screen 194 . There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, capacitive pressure sensors, and the like.

The gyro sensor 180B may be used to determine the motion attitude of the terminal device 100 . In some embodiments, the angular velocity of the end device 100 about three axes (ie, the x, y and z axes) may be determined by the gyro sensor 180B.

Proximity light sensor 180G may include, for example, light emitting diodes (LEDs) and light detectors, such as photodiodes. The light emitting diodes may be infrared light emitting diodes.

The ambient light sensor 180J is used to sense ambient light brightness. The terminal device 100 can adaptively adjust the brightness of the display screen 194 according to the perceived ambient light brightness.

The fingerprint sensor 180H is used to collect fingerprints. The terminal device 100 can use the collected fingerprint characteristics to unlock fingerprints, access application locks, answer incoming calls with fingerprints, and the like. Wherein, the fingerprint sensor 180H can be arranged below the touch screen, the terminal device 100 can receive the user's touch operation on the touch screen corresponding to the fingerprint sensor, and the terminal device 100 can collect the fingerprint of the user's finger in response to the touch operation information.

The touch sensor 180I is also called "touch panel". The touch sensor 180I may be disposed on the display screen 194, and the touch sensor 180I and the display screen 194 form a touch screen, also called a "touch screen". The touch sensor 180I is used to detect a touch operation on or near it. The touch sensor can pass the detected touch operation to the application processor to determine the type of touch event. Visual output related to touch operations may be provided through display screen 194 . In other embodiments, the touch sensor 180I may also be disposed on the surface of the terminal device 100, which is different from the position where the display screen 194 is located.

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

The indicator 192 can be an indicator light, which can be used to indicate the charging state, the change of the power, and can also be used to indicate a message, a missed call, a notification, and the like.

The SIM card interface 195 is used to connect a SIM card. The SIM card can be contacted and separated from the terminal device 100 by inserting into the SIM card interface 195 or pulling out from the SIM card interface 195 . In some embodiments, the terminal device 100 adopts an eSIM, that is, an embedded SIM card. The eSIM card can be embedded in the terminal device 100 and cannot be separated from the terminal device 100 .

The software system of the terminal device 100 may adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. The embodiments of the present application take an Android system with a layered architecture as an example to exemplarily describe the software structure of the terminal device 100 .

FIG. 3 is a block diagram of a software structure of a terminal device 100 according to an embodiment of the present application.

The layered architecture divides the software into several layers, and each layer has a clear role and division of labor. Layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, which are, from top to bottom, an application layer, an application framework layer, an Android runtime (Android runtime) and a system library, and a kernel layer.

The application layer can include a series of application packages.

As shown in FIG. 3, the application package may include applications (also referred to as applications) such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, SMS, etc.

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

As shown in Figure 3, the application framework layer may include window managers, content providers, view systems, telephony managers, resource managers, notification managers, and the like.

A window manager is used to manage window programs. The window manager can get the size of the display screen, determine whether there is a status bar, lock the screen, take screenshots, etc.

Content providers are used to store and retrieve data and make these data accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phone book, etc.

The view system includes visual controls, such as controls for displaying text, controls for displaying pictures, and so on. View systems can be used to build applications. A display interface can consist 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 resource manager provides various resources for the application, such as localization strings, icons, pictures, layout files, video files and so on.

The notification manager enables applications to display notification information in the status bar, which can be used to convey notification-type messages, and can automatically disappear after a brief pause without user interaction. For example, the notification manager is used to notify download completion, message reminders, etc. It can also be used to convey a message that prompts the type of operation, and can exist for a long time, waiting to obtain user operations. For example, the notification manager is used to remind the user whether to block the push message of the application, and then obtain the user's action on the inquiry message. The notification manager can also display notifications in the status bar at the top of the system in the form of graphs or scroll bar text, such as notifications from applications running in the background, and can also display notifications on the screen in the form of a dialog interface. For example, text information is prompted in the status bar, a prompt sound is issued, the electronic device vibrates, and the indicator light flashes.

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

The core library consists of two parts: one is the function functions that the java language needs to call, and the other is the core library of Android.

The application layer and the application framework layer run in virtual machines. The virtual machine executes the java files of the application layer and the application framework layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, safety and exception management, and garbage collection.

A system library can include multiple functional modules. For example: surface manager (surface manager), 2D graphics engine (eg: SGL), 3D graphics processing library (eg: OpenGL ES), media library (Media Libraries), etc.

The Surface Manager is used to manage the display subsystem and provides a fusion of 2D and 3D layers for multiple applications.

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

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

The media library supports playback and recording of a variety of commonly used audio and video formats, as well as still image files. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

The kernel layer is the layer between hardware and software. The kernel layer contains at least display drivers, camera drivers, audio drivers, and sensor drivers.

The following describes the display manner and operation manner of the query message in the embodiments of the present application.

In an embodiment of the present application, in order to facilitate determining whether the user needs to block the push message of the application, a query message may be displayed to the user, the query message is used to prompt the user to manage the push message of the application, and then the user's operation on the query message is detected to confirm Whether users need to block push messages from the app. The query message can come from the push server or automatically generated by the terminal device. In the embodiment of the present application, there are multiple possible display modes for the query message, including displaying the query message in the notification bar, and then obtaining the user's operation on the query message, and judging whether the user needs to block the push message of the application. For example, as shown in FIG. 4 , the terminal device displays an inquiry message 402 on the notification bar interface 401 , and the inquiry message 402 includes a control for receiving notification 403 , a control for closing notification 404 and other controls. The terminal device receives the user's input operation 405 (for example, clicking) for closing the notification control 404, and in response to the input operation 405, the terminal device confirms that the user needs to block the push message of the application, sends a confirmation message to the push server, and sends the notification message to the push server on the terminal device. The notification setting of the application is modified to the blocked state (for example, the notification of the application is set to disabled, the notification control will be allowed to be closed, etc.). If the user clicks the receiving notification control 403, it is confirmed that the user does not need to block the push message of this application, and the terminal device does not need to send an inquiry message to the push server.

It should be noted that the above embodiment is only an exemplary display mode and user operation mode of the query message, and does not constitute a limitation to the present application. The query message may also have other display modes and operation modes, such as a pop-up window. The query message is displayed in a way, and then the user's input operation is obtained. It can also be a short message prompt, or the terminal device can turn on the voice assistant, show the content of the query message to the user by voice broadcast, and then obtain the user's voice input to display the content of the query message. Determines whether the user wants to block push messages from the app. In the embodiment of the present application, the display position, display method, display content, etc. of the query message are not limited, and the operation mode for the query message is also not limited.

The following describes the pre-establishment manner of the application list in the embodiment of the present application.

In this embodiment of the present application, in order to facilitate the push server to determine whether the push message of the application needs to be blocked, a corresponding application list may be established for the terminal device in the push server in advance, and the application list may be one or both of a blacklist and a whitelist. kind. The whitelist contains the mapping relationship between terminal devices and applications, and can be designed as a collection of applications that are allowed to send push messages to the terminal device. Similarly, the blacklist includes the mapping relationship between terminal devices and applications, and can be designed as a collection of applications that are prohibited from sending push messages to the terminal device. The whitelist can also be set to a set of terminal devices that are allowed to send push messages of applications, and the blacklist can also be set to a set of terminal devices that are prohibited from sending push messages of applications. This application does not limit the form of the application list.

In order to adopt the push message management method described in the embodiment of the present application, in a possible embodiment, the terminal device first needs to update the system, and the system can support one or more push messages in the embodiment of the present application management method. After completing the system update, the terminal device may send the notification message setting of the local target application to the push server, and the push server then pre-establishes a corresponding notification message for the terminal device according to the notification message setting of the target application list of applications. This application does not limit the system update method and the setting time for sending notification messages.

For example, the notification message setting situation of a target application on the terminal device is shown in FIG. 5a, and the notification interface 20 displays the notification message setting situation corresponding to various applications. Referring to Figure 5a, it can be seen that the notification message settings of the applications are as follows: applications such as Find My Mobile, Email, Short Video, Maps, and Mobile Payment are set to enable notifications, and applications such as music, weather, and stocks are set to disable notifications. After completing the system update required by the embodiment of the present application, the terminal device sends the notification message setting status of the above application to the push server. The push server establishes a corresponding application list for the terminal device according to the notification message setting of the application. The application list may be one or both of a white list or a black list. For example, the push server establishes a whitelist for the terminal device. The form of the whitelist can be exemplarily shown in FIG. 5b. The whitelist includes the identifier of the terminal device (for example, the terminal device ID) and the identifier of the application that allows notification, including Find my mobile phone ID, email ID, short video ID, map ID and mobile payment ID, the whitelist corresponds to the terminal device; if the push server establishes a blacklist for the terminal device, the form of the blacklist can be exemplary Referring to FIG. 5c , the blacklist contains the identifiers of the terminal devices (eg, terminal device IDs) and the identifiers of applications for which notification is prohibited, including music IDs, weather IDs, and stock IDs, and the blacklist corresponds to the terminal devices. Then, based on the whitelist or blacklist, the push server determines whether to send the push message of the application to the corresponding terminal device, and modifies the corresponding blacklist or whitelist according to the confirmation message or the opening message sent by the terminal device. The confirmation message is used to instruct the push server to prohibit sending the push message of the target application to the terminal device, and the enable message instructs the push server to allow the push message of the target application to be sent to the push server. The method of judging whether to send a push message and the method of modifying the blacklist/whitelist are described in detail below, and will not be repeated here. It should be noted that the above-mentioned embodiment is one of the possible embodiments of the present application, and is only used to explain the technical solution of the present application and is not a limitation. The blacklist and whitelist may also have other establishment methods and corresponding modifications. It can also contain more information, which is not limited in this application.

Please refer to FIG. 6. FIG. 6 is a schematic flowchart of a method for managing push messages provided by an embodiment of the present application. The method includes but is not limited to the following steps:

S601: The terminal device acquires usage information of the target application.

In this embodiment of the present application, the target application refers to an application with a message push function, and the application may use a push server to push messages. Before acquiring the usage information of the target application, the terminal device may determine in advance which applications installed on the terminal device belong to the target application.

In some embodiments, the usage information of the target application may be designed to include the usage duration, usage times, message sending times, message clicks, consecutive unclicked messages, or message clicks and pushes of the target application in a statistical period. one or more of the ratios.

In still other embodiments, the usage information of the target application may be designed to include the usage duration, usage times, message sending times, message clicks, consecutive unclicked messages, or message clicks and pushes of the target application in a statistical period. One or more of the ratios of the quantities, and also includes the identifier of the target application and the identifier of the terminal device.

In still other embodiments, the statistical period may be preset by the system or set by the user.

For example, the user sets the statistics period to 5 days on the terminal device, and the terminal device starts to collect the usage information of the target application installed on the terminal device within 5 days.

S602: The terminal device sends the usage information of the target application.

Specifically, after the terminal device completes the statistics of the usage information of the target application in this statistical period, it sends the usage information to the push server.

S603: The push server determines whether a query message needs to be sent.

Specifically, the push server judges whether it is necessary to send an inquiry message to the terminal device according to the received usage information of the target application and according to a preset decision algorithm.

In some embodiments, the terminal device determines whether to send an inquiry message according to the usage message of the target application, including:

It is determined that a query message needs to be sent to the user when one or more of the following conditions are met:

For example, the pre-set decision-making algorithm of the push server is: first determine whether the usage duration of the target application is less than or equal to the usage duration threshold; if it is less than or equal to the usage duration threshold, then determine whether the number of message sending times of the target application is greater than the number of message sending thresholds; If it is greater than the threshold of the number of message sending times, it is then judged whether the number of message clicks of the target application is less than or equal to the threshold of the number of message clicks; Wherein, the inquiry message is used to inquire whether the user needs to block the push message of the target application. The terminal device receives the usage information of the target application from the terminal device, the usage information includes the information required by the above decision algorithm, and then the push server uses the above decision algorithm to determine whether to send an inquiry message according to the usage information. It should be noted that the above-mentioned embodiment is one of the possible embodiments of the present application, and is only used to explain the technical solution of the present application and is not limited. There may also be other decision algorithms, which are not limited in this application.

S604: In the case that it is determined in S603 that the inquiry message needs to be sent, the push server sends the inquiry message to the terminal device.

S605: The terminal device determines whether the user needs to block the push message of the application.

Specifically, the terminal device displays the query message, and then obtains the user's operation on the query message, and determines whether the user needs to block the push message of the application. In the embodiment of the present application, the display position and display method of the query message are not limited, and the user does not limit the operation mode of the query message. The display mode of the query message and the user's operation mode in the embodiment of the present application have been described above, and for the sake of brevity of the description, they will not be repeated here.

S606: In the case where it is determined in S605 that the user needs to block the push message of the target application, the terminal device sends a confirmation message to the push server.

In some embodiments, after the terminal device sends the confirmation message to the push server, the setting for the target application in the notification management interface is modified to a state of blocking notifications.

S607: The push server modifies the application list.

Specifically, the push server modifies the application list corresponding to the terminal device according to the confirmation message sent by the terminal device. In some embodiments, the application list includes one or both of a blacklist or a whitelist. The manner of establishing the blacklist/whitelist in the embodiment of the present application has been described above, and will not be repeated here.

In some embodiments, the push server deletes the target application in the pre-established whitelist according to the received confirmation message.

In still other embodiments, the push server adds the target application to a pre-established blacklist according to the received confirmation message.

In still other embodiments, the terminal device detects a second operation performed by the user on the notification management interface; wherein the second operation is used to determine that the user needs to open the push message of the target application; the terminal device responds In the second operation, sending an opening message to the push server; wherein the opening message is used to instruct the push server to allow sending of the push message of the target application to the terminal device; the terminal device according to the opening message message, adding the target application to a pre-established whitelist.

In still other embodiments, the terminal device detects a second operation performed by the user on the notification management interface; wherein the second operation is used to determine that the user needs to open the push message of the target application; the terminal device responds In the second operation, sending an opening message to the push server; wherein the opening message is used to instruct the push server to allow sending of the push message of the target application to the terminal device; the terminal device according to the opening message message to delete the target application in the pre-established blacklist.

In still other embodiments, the terminal device detects a third operation performed by the user on the notification management interface; wherein the third operation is used to determine that the user needs to block the push message of the target application; the terminal device responds In the third operation, send a shutdown message to the push server; wherein the shutdown message is used to instruct the push server to prohibit sending the push message of the target application to the terminal device; the terminal device according to the shutdown message, adding the target application to a pre-established blacklist.

In still other embodiments, the terminal device detects a third operation performed by the user on the notification management interface; wherein the third operation is used to determine that the user needs to block the push message of the target application; the terminal device responds In the third operation, send a shutdown message to the push server; wherein the shutdown message is used to instruct the push server to prohibit sending the push message of the target application to the terminal device; the terminal device according to the shutdown message to delete the target application in the pre-established whitelist.

S608: The application server sends a push message to the push server.

Specifically, the application server invokes the push server interface of the push server to initiate push as required. The push message includes the application identifier and the terminal device identifier.

S609: The push server determines whether the push message of the application needs to be blocked.

In some embodiments, the push server determines whether the application corresponding to the push message is in the whitelist corresponding to the terminal device; if the application corresponding to the push message is in the whitelist, it is not necessary to block the push message of the application ; If the application corresponding to the push message is not in the white list, the push message of the application needs to be shielded.

In still other embodiments, the push server determines whether the application corresponding to the push message is in the blacklist corresponding to the terminal device; if the application corresponding to the push message is in the blacklist, the push message of the application needs to be blocked ; If the application corresponding to the push message is not in the blacklist, it is not necessary to block the push message of the application.

S610: In the case where it is determined in S609 that the push message needs to be blocked, the push server does not send the push message of the application to the terminal device.

S611: In the case where it is determined in S609 that the push message does not need to be blocked, the push server sends the push message of the application to the terminal device.

It can be seen that, in the embodiment of the present application, by sending the usage information of the target application on the terminal device to the push server, the push server can make a decision on whether to send an inquiry message to the terminal device; the push server sends an inquiry message to the terminal device to inquire Whether the user needs to block the push messages of the target application; the terminal device sends a confirmation message to the push server, so that the push server can directly block the push messages of the application. In addition, the embodiment of the present application can upload the opening message to the push server by detecting the user's operation of enabling the application notification on the terminal device, so that the user can control the push server on the terminal device to restore the push message of the application. It not only reduces user operations, but also meets the real needs of users, and can effectively reduce the power consumption of terminal equipment.

In addition, in a possible embodiment, after step S602, the application server sends a request to the push server, requesting the push server to send the application usage information of the terminal device. In response to the request, the push server sends the application usage information to the application server. The application usage information may be sorted application usage information of multiple terminal devices, and the application server may perform corresponding analysis and extract useful information based on the application usage information.

Please refer to FIG. 7. FIG. 7 is a schematic flowchart of another push message management method provided by an embodiment of the present application. The method includes but is not limited to the following steps:

S701: The terminal device acquires usage information of the target application.

For this step, reference may be made to the relevant introduction in the foregoing step S601, and details are not repeated here.

S702: The terminal device judges whether an inquiry message needs to be sent.

Wherein, the inquiry message is used to inquire whether the user needs to block the push message of the target application.

S703: In the case where it is determined in S702 that an inquiry message needs to be sent, the terminal device determines whether the user needs to block the push message of the target application.

Specifically, when it is determined in S702 that an inquiry message needs to be sent, the terminal device automatically generates an inquiry message corresponding to the target application, displays the inquiry message, and then acquires the user's operation on the inquiry message, and determines whether the user needs to block the inquiry message. The push message of the target application.

The embodiment of the present application does not limit the display position, display mode and user operation mode of the query message. The display mode of the query message and the corresponding user operation in the embodiment of the present application have been described above, and will not be repeated here.

S704: In the case where it is determined in S703 that the user needs to block the push message of the target application, the terminal device sends a confirmation message to the push server.

In some embodiments, after the terminal device sends the confirmation message to the push server, the setting for the target application in the notification management interface is modified to a blocked state. For example, setting the app's notifications to disabled, allowing notification controls to be turned off, etc.

S705: The push server modifies the application list.

For this step, reference may be made to the relevant introduction in the foregoing step S607, and details are not repeated here.

S706: The application server sends a push message to the push server.

For this step, reference may be made to the relevant introduction in the foregoing step S608, which will not be repeated here.

S707: The push server determines whether the push message of the application needs to be blocked.

For this step, reference may be made to the relevant introduction in the foregoing step S609, and details are not repeated here.

S708: In the case where it is determined in S707 that the push message needs to be blocked, the push server does not send the push message of the application to the terminal device.

S709: In the case where it is determined in S707 that the push message does not need to be blocked, the push server sends the push message of the application to the terminal device.

It can be seen that in the embodiment of the present application, by acquiring the usage information of the target application on the terminal device, the terminal device can make a decision on whether to send an inquiry message to the user; The message directly blocks the push message of the app. Moreover, the embodiment of the present application can upload the opening message to the push server by detecting the user's operation of opening the application notification on the terminal device, so that the user can control the push server to restore the push message of the application on the terminal device. It not only reduces user operations, but also meets the real needs of users, and can effectively reduce the power consumption of terminal equipment.

It can be understood that, after the terminal device obtains the usage information of the target application, the terminal device can also first determine whether it is currently in a charging state or a fully charged state, and if it is in a charging state or a fully charged state, the terminal device starts. It is judged according to the usage information of the target application whether an inquiry message needs to be sent, that is, S702 is executed, and then other steps corresponding to FIG. 7 are continued to be executed; The usage information is sent to the push server, and the push server makes a corresponding judgment, that is, execute S602, and then continue to execute other steps corresponding to FIG. 6 . It can be seen that by judging whether the terminal device is in a charging state or a sufficient power state, and deciding whether to perform the above judgment steps on the terminal device or the push server, the power consumption of the terminal device can be reduced.

The methods of the embodiments of the present application are described in detail above, and the related apparatuses of the embodiments of the present application are provided below.

Referring to FIG. 8 , FIG. 8 is a structural block diagram of a terminal device 80 provided by an embodiment of the present application. The terminal device 80 may include an acquisition module 801, a transmission module 802, a reception module 803 and a detection module 804. In a specific implementation, the data/programs of these functional modules may be stored in the following memory 1001, and the detection module 804 may be executed In the processor 1002 described below, the functions of the sending module 802 and the receiving module 803 depend on the transceiver 1003 described below to perform signal transmission and reception of the uplink/downlink channel. In yet another specific implementation, the data/programs of these functional modules can be stored in the above-mentioned internal memory 121, the detection module 804 can be executed on the above-mentioned processor 110, and the function implementation of the sending module 802 and the receiving module 803 depends on the above-mentioned The mobile communication module 150 or the wireless communication module 160 performs signal transmission and reception of uplink/downlink channels. in:

an acquisition module 801, configured to acquire usage information of the target application in the statistical period;

A sending module 802, configured to send usage information of the target application to a push server;

A receiving module 803, configured to receive an inquiry message sent by the push server; wherein the inquiry message is used to inquire whether the user needs to block the push message of the target application;

A detection module 804, configured to detect the user's first operation on the query message; wherein, the first operation is used to determine that the user needs to block the push message of the target application;

The sending module 802 is further configured to, in response to the first operation, send a confirmation message to the push server; wherein the confirmation message is used to instruct the push server to prohibit sending the target application to the terminal device push message.

In some feasible embodiments, the terminal device further includes an execution module 805; the execution module 805 is configured to close the notification of the target application in the notification management interface.

In some feasible embodiments, the usage information of the target application includes one or more of usage duration, usage count, message sending count, message click count, ratio of message click count to push count, or number of consecutively unclicked messages .

In some feasible embodiments, the usage information of the target application further includes an identifier of the target application and an identifier of the terminal device.

In some feasible embodiments, the detection module 804 is further configured to detect a second operation performed by the user on the notification management interface; wherein the second operation is used to determine that the user needs to open the push message of the target application; The sending module 802 is further configured to send an opening message to the push server, wherein the opening message is used to instruct the push server to allow sending the push message of the target application to the terminal device.

In some feasible embodiments, the statistical period is one of a system preset or a user setting.

It should be noted that, in the specific embodiment of the present application, the above-mentioned terminal device 80 may be the terminal device in the above-mentioned embodiments of FIG. 6 and FIG. 7 , that is, in the specific implementation, the function implementation of each module of the terminal device 80 may refer to For the description of the relevant method steps in the above-mentioned embodiments, for the sake of brevity of the description, details are not repeated here.

Referring to FIG. 9, FIG. 9 is a structural block diagram of an apparatus 90 provided by an embodiment of the present application. The device 90 may include a receiving module 901, a determining module 902 and a transmitting module 903. In a specific implementation, the data/programs of these functional modules may be stored in the following memory 1101, and the determining module 902 may be executed on the following processor 1102, and the function realization of the receiving module 901 and the sending module 903 depends on the transceiver 1103 described below to perform signal transmission and reception of the uplink/downlink channel. in:

a receiving module 901, configured to receive usage information of a target application from a terminal device;

A determination module 902, configured to determine whether an inquiry message needs to be sent to the terminal device according to the usage information of the target application; wherein, the inquiry message is used to inquire whether the user needs to block the push message of the target application;

a sending module 903, configured to send the query message to the terminal device when it is determined to send the query message;

The receiving module 901 is further configured to receive a confirmation message from the terminal device, wherein the confirmation message is used to instruct the apparatus to prohibit sending the push message of the target application to the terminal device.

In some possible embodiments, the apparatus further includes an execution module 904; the execution module 904 is specifically configured to, according to the confirmation message, delete the target application in the pre-established whitelist; wherein the pre-established whitelist The whitelist is a set of applications that are allowed to send push messages, including the mapping relationship between the terminal device and the application.

In some possible embodiments, the receiving module 901 is further configured to receive a push message from an application server; the determining module 902 is further configured to determine whether the application corresponding to the push message is in the whitelist; the The sending module 903 is further configured to, if the application corresponding to the push message is in the white list, send the push message to the terminal device; if the application corresponding to the push message is not in the white list, then The push message is not sent to the terminal device.

In some possible embodiments, the apparatus further includes an execution module 904; the execution module 904 is specifically configured to, according to the confirmation message, add the target application to a pre-established blacklist; wherein the pre-established blacklist The blacklist is a set of applications that are prohibited from sending push messages, including the mapping relationship between the terminal device and the application.

In some possible embodiments, the receiving module 901 is further configured to receive a push message from an application server; the determining module 902 is further configured to determine whether the application corresponding to the push message is in the blacklist; the The sending module 903 is further configured to, if the application corresponding to the push message is in the blacklist, not to send the push message to the terminal device; if the application corresponding to the push message is not in the blacklist, Then send the push message to the terminal device.

In some possible embodiments, the determining module 902 is configured to include: in the case that one or more of the following conditions are satisfied, determine that an inquiry message needs to be sent to the terminal device:

It should be noted that, in the specific embodiment of the present application, the above-mentioned apparatus 90 may be the push server in the above-mentioned embodiments of FIG. 6 and FIG. 7 , that is, in the specific implementation, the function implementation of each module of the apparatus 90 may refer to the above-mentioned implementation. The relevant method steps of the example are described, and for the sake of brevity of the description, they will not be repeated here.

Please refer to FIG. 10 . FIG. 10 is another apparatus 1000 provided by an embodiment of the present application. The apparatus 1000 is, for example, the terminal device described in the embodiment of the present application. The apparatus 1000 includes a processor 1002, a memory 1001 and a transceiver 1003, two or all of the processor 1002, the memory 1001 and the transceiver 1003 may be connected to each other through a bus 1005, or may be integrated together. Optionally, the apparatus 1000 further includes a display, where the display is configured to display a push message and an inquiry message of the application.

The memory 1001 includes but is not limited to random access memory (English: Random Access Memory, referred to as: RAM), read-only memory (English: Read-Only Memory, referred to as: ROM), erasable programmable read-only memory (English: English: Erasable Programmable Read Only Memory, referred to as EPROM), or portable read-only memory (English: Compact Disc Read-Only Memory, referred to as: CD-ROM), the memory 1001 is used for related instructions and data.

The transceiver 1003 is configured to receive data sent by the push server (eg, query message, etc.), or send data to the push server (eg, send usage information, confirmation message, startup message, etc. of the target application).

The processor 1002 may be one or more central processing units (English: Central Processing Unit, CPU for short). When the processor 1002 is a CPU, the CPU may be a single-core CPU or a multi-core CPU. The processor 1002 in the apparatus 1000 may be specifically configured to execute the related methods on the terminal device side in the above-mentioned embodiments of FIG. 6 and FIG. 7 .

Please refer to FIG. 11 . FIG. 11 is another apparatus 1100 provided by an embodiment of the present application. The apparatus 1100 is, for example, the push server described in the embodiment of the present application. The apparatus 1100 includes a processor 1102, a memory 1101, and a transceiver 1103, and two or all of the processor 1102, the memory 1101, and the transceiver 1103 may be connected to each other through a bus 1104, or may be integrated together.

The memory 1101 includes, but is not limited to, random access memory (English: Random Access Memory, referred to as: RAM), read-only memory (English: Read-Only Memory, referred to as: ROM), erasable programmable read-only memory (English: Erasable Programmable Read Only Memory, referred to as EPROM), or portable read-only memory (English: Compact Disc Read-Only Memory, referred to as: CD-ROM), the memory 1101 is used for related instructions and data.

The transceiver 1103 is used to receive data sent by the terminal device (such as usage information of the target application, confirmation message, opening message, etc.), or send data (such as an inquiry message, etc.) to the terminal device.

The processor 1102 may be one or more central processing units (English: Central Processing Unit, CPU for short). When the processor 1102 is a CPU, the CPU may be a single-core CPU or a multi-core CPU.

The processor 1102 in the apparatus 1100 may be specifically configured to execute the related methods on the push server side in the above-mentioned embodiments of FIG. 6 and FIG. 7 .

Based on the same inventive concept, the embodiments of the present application provide another device, and in a specific implementation, the device may be a chip. The apparatus includes a processor and a memory coupled or integrated with the processor. in:

the memory for storing computer program instructions;

The processor is configured to execute the computer program stored in the memory to obtain usage information of the target application in the statistical period; send the usage information of the target application to a push server; receive an inquiry message sent by the push server; The inquiry message is used to inquire whether the user needs to block the push message of the target application; the user's first operation on the inquiry message is detected; wherein the first operation is used to determine that the user needs to block the target application and send a confirmation message to the push server in response to the first operation; wherein the confirmation message is used to instruct the push server to prohibit sending the push message of the target application to the terminal device.

In a possible embodiment, the chip may be coupled with a transceiver. The transceiver can be used to send data to or receive data from the push server; for example, for sending the usage information of the target application to the push server, for example, for receiving the inquiry message sent by the push server; for example, for In response to the first operation, an acknowledgement message is sent to the push server.

In a possible embodiment, the chip can be applied to terminal equipment. For the specific function implementation of the chip, reference may also be made to the description of the relevant functions of the terminal device in the embodiments of FIG. 6 and FIG. 7 , which will not be repeated here.

Based on the same inventive concept, the embodiments of the present application provide another apparatus. In a specific implementation, the apparatus may be a chip, and the apparatus includes a processor and a memory coupled or integrated with the processor. in:

the memory for storing computer program instructions;

The processor is configured to execute the computer program stored in the memory to receive usage information of the target application from the terminal device; according to the usage information of the target application, determine whether to send an inquiry message to the terminal device; Wherein, the inquiry message is used to inquire whether the user needs to block the push message of the target application; if it is determined that the inquiry message needs to be sent, the inquiry message is sent to the terminal device; the confirmation from the terminal device is received. message; wherein the confirmation message is used to instruct the push server to prohibit sending the push message of the target application to the terminal device.

In a possible embodiment, the chip may be coupled with a transceiver. The transceiver can be used to send data to or receive data from the terminal device, such as receiving usage information of the target application from the terminal device; for example, in the case of determining that an inquiry message needs to be sent, send the inquiry message to the terminal device ; for example receiving an acknowledgment message from the terminal device.

In a possible embodiment, the chip can be applied to a push server. For the specific function implementation of the chip, reference may also be made to the description of the relevant functions of the push server in the embodiments of FIG. 6 and FIG. 7 , which will not be repeated here.

Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be implemented by instructing relevant hardware through a computer program, and the program can be stored in a computer-readable storage medium. During execution, the processes of the embodiments of the above-mentioned methods may be included. The storage medium may be a magnetic disk, an optical disk, a read-only memory (Read-Only Memory, ROM), or a random access memory (Random Access Memory, RAM) or the like.

What is disclosed above is only a preferred embodiment of the present application, and of course, it cannot limit the scope of the right of the present application. Those skilled in the art can understand that all or part of the process of implementing the above-mentioned embodiment can be realized according to the right of the present application. The equivalent changes required to be made still belong to the scope covered by the invention.

Claims

A method for managing push messages, characterized in that the method comprises:

The terminal device obtains the usage information of the target application within the statistical period;

The terminal device sends the usage information of the target application to the push server;

The terminal device receives an inquiry message sent by the push server; wherein the inquiry message is used to inquire whether the user needs to block the push message of the target application;

Detecting the user's first operation on the query message; wherein, the first operation is used to determine that the user needs to block the push message of the target application;

The terminal device sends a confirmation message to the push server in response to the first operation; wherein the confirmation message is used to instruct the push server to prohibit sending the push message of the target application to the terminal device.
The method according to claim 1, wherein after detecting the user's first operation on the query message, the method further comprises: the terminal device closing the notification of the target application in the notification management interface.
The method according to claim 1 or 2, wherein the usage information of the target application includes usage duration, usage times, message sending times, message clicks, ratio of message clicks to push amounts, or messages that have not been clicked continuously. one or more of the numbers.
The method according to claim 3, wherein the usage information of the target application further comprises an identifier of the target application and an identifier of the terminal device.
The method according to any one of claims 1-4, wherein after the terminal device sends a confirmation message to the push server, the method further comprises:

The terminal device detects a second operation of the user on the notification management interface; wherein the second operation is used to determine that the user needs to open the push message of the target application;

In response to the second operation, the terminal device sends an opening message to the push server; wherein the opening message is used to instruct the push server to allow sending the push message of the target application to the terminal device.
The method according to any one of claims 1-5, wherein the statistical period is one of a system preset or a user setting.
A method for managing push messages, characterized in that the method comprises:

The push server receives the usage information of the target application from the terminal device;

The push server determines whether it is necessary to send an inquiry message to the terminal device according to the usage information of the target application; wherein, the inquiry message is used to inquire whether the user needs to block the push message of the target application;

In the case that it is determined that an inquiry message needs to be sent, the push server sends the inquiry message to the terminal device;

The push server receives a confirmation message from the terminal device, wherein the confirmation message is used to instruct the push server to prohibit sending the push message of the target application to the terminal device.
The method according to claim 7, wherein the usage information of the target application includes usage duration, usage times, message sending times, message clicks, ratio of message clicks to push amounts, or the number of consecutively unclicked messages. one or more of.
The method according to claim 8, wherein the usage information of the target application further comprises an identifier of the target application and an identifier of the terminal device.
The method according to claim 9, wherein after the push server receives the confirmation message from the terminal device, the method further comprises:

The push server deletes the target application in the pre-established white list according to the confirmation message; wherein, the pre-established white list is a set of applications that are allowed to send push messages, including the terminal device and the application. Mapping relations.
The method according to claim 10, wherein after the push server deletes the target application in the pre-established whitelist according to the confirmation message, the method further comprises:

The push server receives the push message from the application server;

Determine whether the application corresponding to the push message is in the whitelist;

If the application corresponding to the push message is in the whitelist, sending the push message to the terminal device;

If the application corresponding to the push message is not in the white list, the push message is not sent to the terminal device.
The method according to claim 9, wherein after the push server receives the confirmation message from the terminal device, the method further comprises:

The push server adds the target application to a pre-established blacklist according to the confirmation message; wherein, the pre-established blacklist is a set of applications that are prohibited from sending push messages, including the mapping of the terminal device and the application relation.
The method according to claim 12, wherein after the push server adds the target application to a pre-established blacklist according to the confirmation message, the method further comprises:

The push server receives the push message from the application server;

Determine whether the application corresponding to the push message is in the blacklist;

If the application corresponding to the push message is in the blacklist, do not send the push message to the terminal device;

If the application corresponding to the push message is not in the blacklist, the push message is sent to the terminal device.
The method according to any one of claims 8-13, wherein the push server determines whether to send an inquiry message to the terminal device according to the usage information of the target application, comprising:

When one or more of the following conditions are met, it is determined that an inquiry message needs to be sent to the terminal device:

The usage duration of the target application is less than or equal to the usage duration threshold;

Or, the usage count of the target application is less than or equal to the usage count threshold;

Or, the message sending times of the target application is greater than the message sending times threshold;

Or, the number of message clicks of the target application is less than or equal to the threshold of the number of message clicks;

Or, the ratio of the message clicks to the push amount of the target application is less than or equal to the threshold of the ratio of the message clicks to the push amount;

Alternatively, the number of consecutively unclicked messages of the target application is greater than the threshold of the number of consecutively unclicked messages.
A kind of terminal equipment, it is characterized in that, described terminal equipment comprises:

The acquisition module is used to acquire the usage information of the target application in the statistical period;

a sending module, configured to send the usage information of the target application to the push server;

a receiving module, configured to receive an inquiry message sent by the push server; wherein the inquiry message is used to inquire whether the user needs to block the push message of the target application;

a detection module, configured to detect the user's first operation on the query message; wherein, the first operation is used to determine that the user needs to block the push message of the target application;

The sending module is further configured to, in response to the first operation, send a confirmation message to the push server; wherein the confirmation message is used to instruct the push server to forbid sending the target application to the terminal device. forward news.
The terminal device according to claim 15, wherein the terminal device further comprises an execution module;

The execution module is configured to close the notification of the target application in the notification management interface.
The terminal device according to claim 15 or 16, wherein the usage information of the target application includes usage duration, usage times, message sending times, message clicks, ratio of message clicks to push amounts, or continuous unclicked One or more of the number of messages.
The terminal device according to claim 17, wherein the usage information of the target application further comprises an identifier of the target application and an identifier of the terminal device.
The terminal device according to any one of claims 15-18, wherein,

The detection module is further configured to detect the user's second operation on the notification management interface; wherein the second operation is used to determine that the user needs to open the push message of the target application;

The sending module is further configured to send an opening message to the push server; wherein the opening message is used to instruct the push server to allow sending the push message of the target application to the terminal device.
The terminal device according to any one of claims 15-19, wherein the statistical period is one of a system preset or a user setting.
A device, characterized in that the device comprises:

a receiving module for receiving usage information of the target application from the terminal device;

a determining module, configured to determine whether an inquiry message needs to be sent to the terminal device according to the usage information of the target application; wherein, the inquiry message is used to inquire whether the user needs to block the push message of the target application;

a sending module, configured to send the query message to the terminal device when it is determined that the query message needs to be sent;

The receiving module is further configured to receive a confirmation message from the terminal device, wherein the confirmation message is used to instruct the apparatus to prohibit sending the push message of the target application to the terminal device.
The device according to claim 21, wherein the usage information of the target application includes usage duration, usage times, message sending times, message clicks, ratio of message clicks to push amounts, or the number of consecutively unclicked messages. one or more of.
The apparatus according to claim 22, wherein the usage information of the target application further comprises an identifier of the target application and an identifier of the terminal device.
The apparatus according to claim 23, wherein the apparatus further comprises an execution module;

The execution module is configured to delete the target application in the pre-established whitelist according to the confirmation message; wherein, the pre-established whitelist is a set of applications that are allowed to send push messages, including the terminal device and the The mapping relationship of the application.
The apparatus of claim 24, wherein:

The receiving module is further configured to receive push messages from the application server;

The determining module is further configured to determine whether the application corresponding to the push message is in the whitelist;

The sending module is further configured to, if the application corresponding to the push message is in the white list, send the push message to the terminal device; if the application corresponding to the push message is not in the white list, Then the push message is not sent to the terminal device.
The apparatus according to claim 23, wherein the apparatus further comprises an execution module;

The execution module is configured to add the target application to a pre-established blacklist according to the confirmation message; wherein, the pre-established blacklist is a set of applications prohibited from sending push messages, including the terminal device and the application mapping relationship.
The apparatus of claim 26, wherein:

The receiving module is further configured to receive push messages from the application server;

The determining module is further configured to determine whether the application corresponding to the push message is in the blacklist;

The sending module is further configured to, if the application corresponding to the push message is in the blacklist, not to send the push message to the terminal device; if the application corresponding to the push message is not in the blacklist , the push message is sent to the terminal device.
The device according to any one of claims 21-27, wherein the determining module is specifically configured to:

When one or more of the following conditions are met, it is determined that an inquiry message needs to be sent to the terminal device:

The usage duration of the target application is less than or equal to the usage duration threshold;

Or, the usage count of the target application is less than or equal to the usage count threshold;

Or, the message sending times of the target application is greater than the message sending times threshold;

Or, the number of message clicks of the target application is less than or equal to the threshold of the number of message clicks;

Or, the ratio of the message clicks to the push amount of the target application is less than or equal to the threshold of the ratio of the message clicks to the push amount;

Alternatively, the number of consecutively unclicked messages of the target application is greater than the threshold of the number of consecutively unclicked messages.