WO2018233492A1

WO2018233492A1 - Method for deleting push message, and related product

Info

Publication number: WO2018233492A1
Application number: PCT/CN2018/090148
Authority: WO
Inventors: 白剑
Original assignee: Oppo广东移动通信有限公司
Priority date: 2017-06-21
Filing date: 2018-06-06
Publication date: 2018-12-27
Also published as: CN107332757A; CN107332757B

Abstract

Disclosed are a method for deleting a push message, and a related product. The method comprises: a mobile terminal acquiring user habit data corresponding to an application that allows message pushing, the user habit data comprising a deletion proportion of a first type of push message of the application, and the first type of push message being any one of all push message types of the application; determining whether the deletion proportion is greater than a pre-set proportion value; and if the deletion proportion is greater than the pre-set proportion value, deleting all the push messages corresponding to the first type currently received by the mobile terminal. In the embodiments of the present invention, an unnecessary push message can be automatically deleted, and a push message required by a user can be retained, thereby improving the user experience.

Description

Method for deleting push messages and related products

Technical field

The present invention relates to the field of mobile communication technologies, and in particular, to a method for deleting a push message and related products.

Background technique

With the increasing use of mobile terminals such as smart phones, people in modern life are basically a mobile phone. A variety of applications (Application, referred to as APP) can be installed on the current mobile phone, and the mobile phone can also receive push messages of various applications. However, when the number of applications on the mobile phone is large, the number of push messages received by the mobile phone per day is large, which causes serious interference to the mobile phone users.

In the prior art, there are generally two ways to clear the push message. The first one is: the user opens the push message notification bar and manually deletes the push message from the notification bar. The second type is: the user manually sets the push message permission of the application, and sets the application push message to be rejected. The first way to clear the push message requires manual operation by the user each time, and the operation is cumbersome; the second method can refuse to receive all the push messages of the application only once the user operates, but for some applications, the user receives the application. The need to push a message, but is unwilling to receive all push messages for the push of the application, directly rejecting the push message or allowing the push message to be received does not meet the user's needs.

Summary of the invention

The embodiment of the invention provides a method for deleting a push message and related products, which can automatically delete unnecessary push messages, retain the push messages required by the user, and improve the user experience.

A first aspect of the embodiments of the present invention provides a method for deleting a push message, including:

Obtaining user habit data corresponding to an application that allows the message to be pushed, the user habit data including a deletion ratio of the first type of push message of the application, the first type of push message being all push messages of the application Any of the types;

Determining whether the deletion ratio is greater than a preset ratio value;

If the deletion ratio is greater than the preset ratio value, all the push messages corresponding to the first type currently received by the mobile terminal are deleted.

A second aspect of the embodiments of the present invention provides a mobile terminal, including:

An acquiring unit, configured to acquire user habit data corresponding to an application that allows a message to be pushed, where the user habit data includes a deletion ratio of the first type of push message of the application, and the first type of push message is the Any of the push message types of the app;

a first determining unit, configured to determine whether the deletion ratio is greater than a preset ratio value;

And a deleting unit, configured to delete all the push messages corresponding to the first type currently received by the mobile terminal when the first determining unit determines that the result is yes.

A third aspect of the embodiments of the present invention provides a mobile terminal, including one or more processors, a memory, a communication unit, and one or more programs, wherein the one or more programs are stored in the memory, and It is configured to be executed by the one or more processors, the program comprising some or all of the steps described in any of the methods of the first aspect of the embodiments of the present invention.

A fourth aspect of embodiments of the present invention provides a computer readable storage medium for storing a computer program for electronic data exchange, wherein the computer program causes a computer to perform a first aspect of an embodiment of the present invention Some or all of the steps described in either method.

A fifth aspect of an embodiment of the present invention provides a computer program product comprising a non-transitory computer readable storage medium storing a computer program, the computer program being operative to cause a computer to perform an embodiment of the present invention Some or all of the steps described in either method.

The method for deleting a push message in the embodiment of the present invention can automatically delete a push message that is not of interest to the user according to user habit data, and retain a push message that is of interest to the user, thereby improving the user experience.

DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description are only It is a certain embodiment of the present invention, and other drawings can be obtained from those skilled in the art without any creative work.

1 is a schematic diagram of a network architecture disclosed in an embodiment of the present invention;

2 is a schematic flowchart of a method for deleting a push message according to an embodiment of the present invention;

3 is a schematic diagram of a push message display interface disclosed in an embodiment of the present invention;

FIG. 4 is a schematic flowchart diagram of another method for deleting a push message according to an embodiment of the present disclosure;

FIG. 5 is a schematic structural diagram of a mobile terminal according to an embodiment of the present invention; FIG.

FIG. 6 is a schematic structural diagram of another mobile terminal according to an embodiment of the present disclosure;

FIG. 7 is a schematic structural diagram of still another mobile terminal according to an embodiment of the present invention.

Detailed ways

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is a partial embodiment of the invention, and not all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

The terms "first", "second" and the like in the specification and claims of the present invention and the above drawings are used to distinguish different objects, and are not intended to describe a specific order. Furthermore, the terms "comprises" and "comprising" and "comprising" are intended to cover a non-exclusive inclusion. For example, a process, method, system, product, or device that comprises a series of steps or units is not limited to the listed steps or units, but optionally also includes steps or units not listed, or, optionally, Other steps or units inherent to these processes, methods, products, or equipment.

References to "an embodiment" herein mean that a particular feature, structure, or characteristic described in connection with the embodiments can be included in at least one embodiment of the invention. The appearances of the phrases in various places in the specification are not necessarily referring to the same embodiments, and are not exclusive or alternative embodiments that are mutually exclusive. Those skilled in the art will understand and implicitly understand that the embodiments described herein can be combined with other embodiments.

The mobile terminal involved in the embodiments of the present invention may include various handheld devices, wireless devices, wearable devices, computing devices, or other processing devices connected to the wireless modem, and various forms of user equipment (User Equipment, UE), mobile station (MS), terminal device, and the like. For convenience of description, the devices mentioned above are collectively referred to as mobile terminals.

The embodiments of the present invention are described in detail below.

For a better understanding of the embodiments of the present invention, the network architecture to which the embodiments of the present invention are applied is first described. Please refer to FIG. 1. FIG. 1 is a schematic diagram of a network architecture disclosed in an embodiment of the present invention. As shown in FIG. 1, the network architecture includes a mobile terminal 11 and an application server 12. The mobile terminal 11 may be a terminal that can install an application such as a mobile phone or a tablet, and the application server 12 may be an application server (The Application Server). One or more applications (Application, APP for short) may be installed on the mobile terminal 11. When the mobile terminal 11 is a mobile phone, the application installed on the mobile phone may also be referred to as a mobile phone client. The application server 12 and the mobile terminal 11 can establish a long connection through a wireless fidelity (WiFi) network or an operator network (for example, a 3G, 4G network), and an application (also referred to as a client) on the mobile terminal 11 can periodically apply to the application. Server 12 sends a heartbeat to maintain a long connection. The application server 12 can push a message to the application installed by the mobile terminal 11 through the established long connection.

Referring to FIG. 2, FIG. 2 is a schematic flowchart of a method for deleting a push message according to an embodiment of the present invention. As shown in FIG. 2, the method for deleting a push message includes the following steps.

201. The mobile terminal acquires user habit data corresponding to an application that allows the message to be pushed. The user habit data includes a deletion ratio of the first type of push message of the application, and the first type of push message is any of the push message types of the application. One.

202. The mobile terminal determines whether the deletion ratio is greater than a preset ratio.

203. If the deletion ratio is greater than the preset ratio, the mobile terminal deletes all the push messages corresponding to the first type currently received by the mobile terminal.

In the embodiment of the present invention, the mobile terminal may install one or more applications. Among all the applications installed by the mobile terminal, some applications allow the mobile terminal to receive the push message, and another part of the application does not allow the mobile terminal to receive the push message. For example, the terminal is installed with 100 applications, of which 60 applications are applications that allow message push, and 40 applications are applications that prohibit message push. The user can turn off or open the message push switch of the application. When the message push switch of an application is turned on, the application is an application that allows the message to be pushed. When the message push switch of an application is closed, the application is an application that prohibits the message push. . Applications that allow message push can receive various types of push messages sent by the application server. For example, if the application A is a news application, the application A can receive the "sports news push message", the "entertainment news push message", the "financial news push message", the "life news push message", etc. pushed by the application server. Various types of push messages.

The corresponding user habit data of the application may be a usage habit of the user for the application that is counted by the mobile terminal in a past period of time (for example, in the past week). For example, for the application A, the number of times the user opens the application A in a preset time period (past time period), the cumulative use time of the application A, and the total number of various types of push messages of the application A can be counted. User-customized data such as the number of views of various types of push messages of application A, the number of deletions of various types of push messages of application A, and the like.

The first type of push message in step 201 is any of the push message types of the application. In step 201, the mobile terminal may only obtain the deletion ratio of a certain type of push message of the application in a preset time period (for example, a past week), and the mobile terminal may separately obtain all types of push messages of the application. The deletion ratio. The deletion ratio of the above-mentioned first type of push message can be understood as the ratio of the number of deletions of the first type of push message of the application to the total number of push messages of the first type of the application. For example, if application A is a news application, in the past week, if the total number of push messages of the first type of application A (for example, sports news feed messages) is 20, the number of articles viewed is 2 The number of deleted items is 3, and the number of unchecked items is 15. The deletion ratio of the first type of push message of application A is 3/20=15%. Push messages can have three states: "Not Viewed," "Viewed," "Deleted." When a push message is pushed to the mobile terminal, the initial state is "unviewed". If the user views the push message, the status of the push message changes to "viewed". If the user deletes the push message, the user The status of the push message changes to "Deleted". If the user does not do any processing on the push message, the status of the push message remains "Not Viewed". It is generally believed that if the status of a push message changes from "unviewed" to "viewed", the user is interested in this push message; if the status of a push message changes from "unviewed" to "deleted", it indicates The user is not interested in this push message.

It can be understood that if a push message is viewed, the push message does not exist, and the push message is automatically deleted from the push notification bar. However, the push message is viewed differently than the push message is deleted. When the push message is viewed, the status of the message is marked as "viewed". After the user clicks the push message, the mobile terminal enters the display interface corresponding to the push message. When the push message is deleted, the status of the message is marked as "deleted", and the mobile terminal directly deletes the push message and does not enter the display interface corresponding to the push message. It can be seen that the push message is deleted means that the push message is not viewed and deleted from the push notification bar. The push message being viewed means that the push message is viewed and automatically deleted from the push notification bar.

The preset scale value of step 202 can be set in advance, for example, can be set to 5%, 10%, 15%, 20%, 30%, 50%, and the like. If the deletion ratio of the first type of push message of the application A is 15% and the preset ratio is 10%, the mobile terminal considers that the user is not interested in the first type of push message of the application A, and the mobile terminal deletes the current reception of the mobile terminal. The first type corresponds to all push messages.

For example, if application A is a news application, in the past week, if the total number of push messages of the first type of application A (for example, sports news push messages) is 20, the number of articles viewed is 0, the number of deletions is 3 (the number of the first type of push messages of the application A currently received by the mobile terminal is 17), and the deletion ratio of the first type of push messages acquired by the mobile terminal to the application A is 3 /20=15%, and it is determined that the deletion ratio of the first type of push message of the application A is greater than the preset ratio value (for example, the preset ratio value is 10%), the mobile terminal deletes the first of the currently received application A. All push messages of type (17).

In an application scenario, when the mobile terminal detects that a push message of the first type is deleted, the mobile terminal starts performing steps 201 to 203. Specifically, when the mobile terminal detects that the first type of push message of the application is deleted, the mobile terminal acquires the deletion ratio of the first type of push message of the application; when it is determined that the first type of the push message of the application is deleted When the ratio is greater than the preset ratio value, the mobile terminal deletes all the push messages corresponding to the currently received first type. Please refer to FIG. 3. FIG. 3 is a schematic diagram of a push message display interface according to an embodiment of the present invention. The pull-down push notification column of the mobile terminal 100 in the left diagram (a) in FIG. 3 displays a total of 12 push messages for receiving an application, wherein the number of the first type of push messages is 9, the second type The number of push messages is two, and the number of push messages of the third type is one. As shown in the figure (a) on the left side of FIG. 3, when the right hand of the user slides to the right in the display area of the first type of push message A, the first type of push message A is deleted, at this time, the mobile terminal detects the first The deletion ratio of a type of push message is 1/9>10% (preset ratio value), that is, the mobile terminal deletes all the push messages corresponding to the currently received first type, and the effect after the deletion is as shown in the right diagram of FIG. 3 ( b) shown.

In the above embodiment, whether the deletion ratio is greater than the preset ratio value is used as the criterion for determining. Of course, the embodiment of the present invention may further determine whether the number of deletions is greater than a preset number. For example, when the terminal detects that the number of deletions of the first type of push message of the application reaches twice, the mobile terminal deletes all the push messages corresponding to the currently received first type. The embodiment of the present invention may further determine whether the number of consecutive deletions is greater than a preset number. For example, when the terminal detects that two consecutive types of push messages of the application are deleted, the mobile terminal deletes all the push messages corresponding to the currently received first type.

Further, if the terminal detects that the number of executions of step 203 reaches a preset number of times (for example, 2 times, 3 times, 4 times, etc.), that is, when the user is not interested in the first type of push message of the application multiple times, the terminal rejects Receiving the first type of push message of the application, that is, the subsequent application server no longer pushes the first type of push message of the application to the terminal. After implementing the solution, the mobile terminal may refuse to receive a certain type of push message of the application when detecting that the user is not interested in a certain type of application of the application, and may refuse to receive the push message that the user is not interested according to the user's habit, further improving user experience.

By implementing the method shown in FIG. 2, the mobile terminal can automatically delete the push message that the user is not interested in according to the user's habit data, and retain the push message that the user is interested in, so as to avoid the interference caused by the push message that the user is not interested in, and improve the user experience.

Referring to FIG. 4, FIG. 4 is a schematic flowchart of another method for deleting a push message according to an embodiment of the present invention. As shown in FIG. 4, the method for deleting a push message includes the following steps.

401. The mobile terminal acquires user habit data corresponding to an application that allows the message to be pushed. The user habit data includes a deletion ratio of the first type of push message of the application and a priority of the first type of push message of the application, and the first type of The push message is any of the push message types for the application.

In the embodiment of the present invention, the priority of each type of push message of the application installed by the mobile terminal may be set in advance and stored in the non-volatile memory of the mobile terminal. In general, the higher the priority, the higher the level of interest to the user. For example, for application A, if the priority of the first type of push message is 1, the priority of the second type of push message is 4, and the priority of the third type of push message is 5, if the priority threshold is preset If the value is 2, the priority of the first type of push message is less than the preset priority threshold, indicating that the user is not interested in the first type of push message of the application A, and the mobile terminal deletes all the corresponding types of the currently received application A. forward news.

402. The mobile terminal determines whether the deletion ratio is greater than a preset ratio. If yes, go to step 403. If no, go to step 404.

403. The mobile terminal deletes all push messages corresponding to the first type currently received by the mobile terminal.

404. The mobile terminal determines whether a priority of the first type of push message is less than a preset priority threshold. If yes, go to step 403. If no, go to step 405.

405. The mobile terminal determines, according to a keyword in the push summary of the first push message, a validity period of the first push message, where the first push message is any one of the first type of push messages.

The push summary of the push message refers to the summary displayed by the push message in the push notification column. The purpose of displaying the push summary is to facilitate the user to quickly understand the content of the push message. The push summary is generally the message title, content summary, etc. , generally no more than 30 words. Some push messages are time-sensitive, such as weather push messages, live push messages, coupon push messages, and the like. For example, if the push summary of the push message A is "live XX match", indicating that the push message is a live push message, the push message is valid until the end of the game; if the push summary of the push message A is "today" There is a thunderstorm at 3-5 pm, indicating that the push message is a weather push message, and the push message is valid until 5 pm today. For a time-sensitive push message, if the current time has exceeded the validity period of the push message, the push message has lost the value of its push, so the terminal deletes the push message. In addition, some push messages cannot accurately determine the validity period based on the push summary, and can be set to a preset fixed value, for example, a 72-hour validity period.

406. The mobile terminal determines whether the current time exceeds the validity period. If yes, go to step 407. If no, go to step 408.

407. The mobile terminal deletes the first push message.

408. The mobile terminal determines whether the same non-push message as the first push message is read. If yes, go to step 407. If no, go back to step 406.

A non-push message refers to a message displayed on the display interface of the application. After entering the display interface of an application, the display interface of the application will display a lot of messages. After the user clicks on a certain message, the user will enter the display interface of the message, and the user can read the message. The display interface of the application often displays various types of messages, which is convenient for the user to browse and read. In general, the application server selects some of the popular messages displayed by the application's display interface or messages of interest to the user as push messages to the mobile terminal. For example, if the user of the mobile terminal has read the message A on the display interface of the application, the mobile terminal will not receive the push message of the message A subsequently; if the user of the mobile terminal has already read the display interface of the application Message A, and the message A has been pushed to the mobile terminal as a push message, and the mobile terminal deletes the push message A from the push notification column of the push message. In the embodiment of the present invention, the mobile terminal can determine which messages have been read by the user, and for the already read message, whether it is a push message or a non-push message, the subsequent push is no longer performed. If the non-push message has been read, Delete the same push message as the non-push message, delete the push message that the user has read the same as the non-push message, and prevent the user from repeatedly reading the same push message to improve the user experience.

Optionally, the priority of the first type of push message is determined based on the reading heat of the first type of non-push message of the application and/or the reading heat of the first type of push message of the application.

The reading heat of the first type of non-push message may be determined based on the total number of readings and the total reading time of the first type of non-push messages in a past period of time (for example, within one week). For example, in the past week, the total number of readings of the first type of non-push messages of the application A on the mobile terminal is 10, and the total reading time is 30 minutes, and the reading heat is: 10+30/3=20. The correspondence between reading heat and priority is as follows: reading heat is [0-10) ((0-10) means greater than 0 and less than 10) corresponding priority is 0, reading heat is [10-20) ([10- 20) indicates that the priority is greater than or equal to 10 and less than 20), the corresponding priority is 1, the reading heat is [20-30) ([20-30] indicates greater than or equal to 20 and less than 30), and the corresponding priority is 2, ... This type of push. Therefore, the reading heat has a priority of 2 corresponding to 2.

By implementing the method shown in FIG. 4, it is possible to decide whether to delete the push message by judging whether the push message is deleted, the priority of the push message, the validity period of the push message, and whether the same non-push message as the push message is read. Consider various ways to delete push messages, delete push messages that users are not interested in, push messages that users have not needed, push messages that users have read, reduce the number of push messages on the push notification bar, and improve user experience. .

The above description mainly introduces the solution of the embodiment of the present invention from the perspective of the method side execution process. It can be understood that, in order to implement the above functions, the mobile terminal includes corresponding hardware structures and/or software modules for performing various functions. Those skilled in the art will readily appreciate that the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A skilled artisan can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.

The embodiment of the present invention may divide the functional unit into the mobile terminal according to the foregoing method example. For example, each functional unit may be divided according to each function, or two or more functions may be integrated into one processing unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit. It should be noted that the division of the unit in the embodiment of the present invention is schematic, and is only a logical function division, and the actual implementation may have another division manner.

Referring to FIG. 5, FIG. 5 is a schematic structural diagram of a mobile terminal according to an embodiment of the present invention. As shown in FIG. 5, the mobile terminal 500 includes an obtaining unit 501, a first determining unit 502, and a deleting unit 503, where:

The obtaining unit 501 is configured to acquire user habit data corresponding to the application that allows the message to be pushed, where the user habit data includes a deletion ratio of the first type of push message of the application, and the first type of push message is any of the push message types of the application. One.

The first determining unit 502 is configured to determine whether the deletion ratio is greater than a preset ratio value.

The deleting unit 503 is configured to delete all the push messages corresponding to the first type currently received by the mobile terminal when the first determining unit 502 determines that the result is YES.

The mobile terminal shown in FIG. 5 is implemented, and the mobile terminal can automatically delete the push message that the user is not interested in according to the user's habit data, and retain the push message that the user is interested in, thereby improving the user experience.

Optionally, the mobile terminal 500 further includes a second determining unit 504, where:

The second determining unit 504 is configured to determine, when the first determining unit 502 determines that the result is negative, whether the priority is less than a preset priority threshold.

The deleting unit 503 is further configured to delete all the push messages corresponding to the first type currently received by the mobile terminal when the second determining unit 504 determines that the result is YES.

Optionally, the mobile terminal 500 further includes a determining unit 505 and a third determining unit 506, where:

The determining unit 505 is configured to: when the second determining unit 504 determines that the result is no, determine, according to the keyword in the push summary of the first push message, the validity period of the first push message, where the first push message is in the first type of push message. Any one of them.

The third determining unit 506 is configured to determine whether the current time exceeds the validity period.

The deleting unit 503 is further configured to delete the first push message when the third determining unit 506 determines that the result is YES.

Optionally, the mobile terminal 500 further includes a fourth determining unit 507, where:

The fourth determining unit 507 is configured to determine, when the third determining unit 506 determines that the result is no, whether the same non-pushing message as the first push message is read.

The deleting unit 503 is further configured to delete the first push message when the fourth determining unit 507 determines that the result is YES.

Optionally, the mobile terminal 500 further includes a first detecting unit;

a first detecting unit, configured to detect whether the number of deletions of the first type of push messages of the application reaches a preset number;

The deleting unit 503 is further configured to: when the first detecting unit detects that the number of deletions of the first type of push messages reaches a preset number, delete all the push messages corresponding to the first type currently received by the mobile terminal.

Optionally, the mobile terminal 500 further includes a second detecting unit and a processing unit;

a second detecting unit, configured to detect whether the number of times the deleting unit performs the deleting operation reaches a preset number of times;

The processing unit is configured to refuse to receive the first type of push message of the application when the second detecting unit detects that the deleting unit performs the deleting operation for a preset number of times.

The mobile terminal in the embodiment of the present invention may decide whether to delete the push message by determining the deletion ratio of the push message, the priority of the push message, the validity period of the push message, and whether the same non-push message as the push message is read. Consider various ways to delete push messages, delete push messages that users are not interested in, push messages that users have not needed, push messages that users have read, reduce the number of push messages on the push notification bar, and improve user experience. .

Please refer to FIG. 6. FIG. 6 is a schematic structural diagram of another mobile terminal according to an embodiment of the present invention. As shown in FIG. 6, the mobile terminal 600 includes one or more processors 601, a memory 602, a communication unit 603, and one or more programs, wherein one or more programs are stored in the memory 602 and configured by Executed by one or more processors 601, the program includes instructions for performing the steps of Figures 2 through 4 above. The processor 601, the memory 602, and the communication unit 603 can be connected by a communication bus 604.

The communication unit 603 is configured to establish a communication channel, to enable the mobile terminal 600 to connect to the communication peer or the base station through the communication channel, and to exchange data with the communication peer or the base station through the communication channel. The communication unit 603 may include a wireless local area network (Wireless Local Area Network) module, a Bluetooth module, a near field communication (NFC), a baseband module, and the like, and a wireless communication module. Serial communication bus (Universal Serial Bus, USB for short), lightning communication interface and other wired communication modules. The communication unit 603 is used for communication between components in the mobile terminal 600 and a communication peer or base station, and can support Direct Memory Access.

The processor 601 may include only a central processing unit (CPU), or may be a CPU, a digital signal processor (DSP), a graphics processing unit (GPU), and a communication unit. A combination of control chips (eg, baseband chips). In the embodiment of the present invention, the CPU may be a single operation core, and may also include a multi-operation core.

The mobile terminal shown in FIG. 6 is implemented, and the mobile terminal can automatically delete the push message that the user is not interested in according to the user's habit data, and retain the push message that the user is interested in, thereby improving the user experience.

The embodiment of the present invention further provides another mobile terminal. As shown in FIG. 7 , for the convenience of description, only the parts related to the embodiment of the present invention are shown. If the specific technical details are not disclosed, refer to the method of the embodiment of the present invention. section. The mobile terminal can be any terminal device including a mobile phone, a tablet computer, a PDA (Personal Digital Assistant), a POS (Point of Sales), an in-vehicle computer, and the mobile terminal is used as a mobile phone as an example:

FIG. 7 is a block diagram showing a partial structure of a mobile phone related to a mobile terminal provided by an embodiment of the present invention. Referring to FIG. 7, the mobile phone includes: a radio frequency (RF) circuit 910, a memory 920, an input unit 930, a display unit 940, a sensor 950, an audio circuit 960, a wireless fidelity (WiFi) module 970, and a processor 980. And power supply 990 and other components. It will be understood by those skilled in the art that the structure of the handset shown in FIG. 7 does not constitute a limitation to the handset, and may include more or less components than those illustrated, or some components may be combined, or different components may be arranged.

The following describes the components of the mobile phone in detail with reference to FIG. 7:

The RF circuit 910 can be used for receiving and transmitting information. Generally, RF circuit 910 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a Low Noise Amplifier (LNA), a duplexer, and the like. In addition, RF circuitry 910 can also communicate with the network and other devices via wireless communication. The above wireless communication may use any communication standard or protocol, including but not limited to Global System of Mobile communication (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (Code Division). Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), E-mail, Short Messaging Service (SMS), and the like.

The memory 920 can be used to store software programs and modules, and the processor 980 executes various functional applications and data processing of the mobile phone by running software programs and modules stored in the memory 920. The memory 920 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application required for at least one function, and the like; the storage data area may store data created according to usage of the mobile phone, and the like. Moreover, memory 920 can include high speed random access memory, and can also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.

The input unit 930 can be configured to receive input numeric or character information and to generate key signal inputs related to user settings and function controls of the handset. Specifically, the input unit 930 can include a fingerprint recognition module 931, a touch display screen 932, and other input devices 933. The fingerprint identification module 931 can collect fingerprint data of the user. In addition to the fingerprint recognition module 931, the input unit 930 may also include other input devices 932. Specifically, other input devices 932 may include, but are not limited to, one or more of a touch screen, a physical keyboard, function keys (such as volume control buttons, switch buttons, etc.), trackballs, mice, joysticks, and the like.

The display unit 940 can be used to display information input by the user or information provided to the user as well as various menus of the mobile phone. The display unit 940 can include a display screen 941. Alternatively, the display screen 941 can be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like. Although in FIG. 7, the fingerprint recognition module 931 and the display screen 941 function as two separate components to implement the input and input functions of the mobile phone, in some embodiments, the fingerprint recognition module 931 and the display screen 941 may be Integrated to achieve the input and playback functions of the phone.

The handset may also include at least one type of sensor 950, such as a light sensor, motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor, wherein the ambient light sensor may adjust the brightness of the display screen 941 according to the brightness of the ambient light, and the proximity sensor may turn off the display screen 941 and/or when the mobile phone moves to the ear. Or backlight. As a kind of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in all directions (usually three axes). When it is stationary, it can detect the magnitude and direction of gravity. It can be used to identify the gesture of the mobile phone (such as horizontal and vertical screen switching, related Game, magnetometer attitude calibration), vibration recognition related functions (such as pedometer, tapping), etc.; as for the mobile phone can also be configured with gyroscopes, barometers, hygrometers, thermometers, infrared sensors and other sensors, no longer Narration.

An audio circuit 960, a speaker 961, and a microphone 962 can provide an audio interface between the user and the handset. The audio circuit 960 can transmit the converted electrical data of the received audio data to the speaker 961 for conversion to the sound signal by the speaker 961; on the other hand, the microphone 962 converts the collected sound signal into an electrical signal by the audio circuit 960. After receiving, it is converted into audio data, and then processed by the audio data playback processor 980, sent to the other mobile phone via the RF circuit 910, or played back to the memory 920 for further processing.

WiFi is a short-range wireless transmission technology, and the mobile phone can help users to send and receive emails, browse web pages, and access streaming media through the WiFi module 970, which provides users with wireless broadband Internet access. Although FIG. 7 shows the WiFi module 970, it can be understood that it does not belong to the essential configuration of the mobile phone, and can be omitted as needed within the scope of not changing the essence of the invention.

The processor 980 is the control center of the handset, which connects various portions of the entire handset using various interfaces and lines, by executing or executing software programs and/or modules stored in the memory 920, and invoking data stored in the memory 920, executing The phone's various functions and processing data, so that the overall monitoring of the phone. Optionally, the processor 980 may include one or more processing units; preferably, the processor 980 may integrate an application processor and a modem processor, where the application processor mainly processes an operating system, a user interface, an application, and the like. The modem processor primarily handles wireless communications. It will be appreciated that the above described modem processor may also not be integrated into the processor 980.

The handset also includes a power source 990 (such as a battery) that supplies power to the various components. Preferably, the power source can be logically coupled to the processor 980 through a power management system to manage functions such as charging, discharging, and power management through the power management system.

Although not shown, the mobile phone may further include a camera, a Bluetooth module, and the like, and details are not described herein again.

The embodiment of the present invention further provides a computer storage medium, wherein the computer storage medium stores a computer program for electronic data exchange, the computer program causing the computer to perform any method for deleting a push message as described in the foregoing method embodiment. Part or all of the steps.

Embodiments of the present invention also provide a computer program product comprising a non-transitory computer readable storage medium storing a computer program, the computer program being operative to cause a computer to perform the operations as recited in the above method embodiments Any or all of the steps to delete a push message.

It should be noted that, for the foregoing method embodiments, for the sake of simple description, they are all expressed as a series of action combinations, but those skilled in the art should understand that the present invention is not limited by the described action sequence. Because certain steps may be performed in other sequences or concurrently in accordance with the present invention. In the following, those skilled in the art should also understand that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present invention.

In the above embodiments, the descriptions of the various embodiments are different, and the details that are not detailed in a certain embodiment can be referred to the related descriptions of other embodiments.

In the several embodiments provided herein, it should be understood that the disclosed apparatus may be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or may be Integrate into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be electrical or otherwise.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable memory. Based on such understanding, the technical solution of the present invention may contribute to the prior art or all or part of the technical solution may be embodied in the form of a software product stored in a memory. A number of instructions are included to cause a computer device (which may be a personal computer, server or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention. The foregoing memory includes: a U disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic disk, or an optical disk, and the like, which can store program codes.

A person skilled in the art can understand that all or part of the steps of the foregoing embodiments can be completed by a program to instruct related hardware, and the program can be stored in a computer readable memory, and the memory can include: a flash drive , read-only memory (English: Read-Only Memory, referred to as: ROM), random accessor (English: Random Access Memory, referred to as: RAM), disk or CD.

The embodiments of the present invention have been described in detail above, and the principles and implementations of the present invention are described in detail herein. The description of the above embodiments is only for helping to understand the method of the present invention and its core ideas; It should be understood by those skilled in the art that the present invention is not limited by the scope of the present invention.

Claims

A method for deleting a push message, comprising:

Obtaining user habit data corresponding to an application that allows the message to be pushed, the user habit data including a deletion ratio of the first type of push message of the application, where the first type of push message is in all push message types of the application Any of them;

Determining whether the deletion ratio is greater than a preset ratio value;

If the deletion ratio is greater than the preset ratio value, all the push messages corresponding to the first type currently received by the mobile terminal are deleted.
The method according to claim 1, wherein the user habit data further includes a priority of the first type of push message of the application, the method further comprising:

If the deletion ratio is less than or equal to the preset ratio value, determining whether the priority is less than a preset priority threshold;

If the priority is less than the preset priority threshold, all the push messages corresponding to the first type currently received by the mobile terminal are deleted.
The method of claim 2, wherein the method further comprises:

Determining, by the keyword in the push summary of the first push message, the validity period of the first push message, where the first push message is the first type, if the priority is greater than or equal to the preset priority threshold Any of the push messages;

Determining whether the current time exceeds the validity period;

If the current time has exceeded the validity period, the first push message is deleted.
The method of claim 3, wherein the method further comprises:

If the current time does not exceed the validity period, determine whether the same non-push message as the first push message is read;

If the same non-push message as the first push message has been read, the first push message is deleted.
The method according to any one of claims 1 to 4, wherein the priority of the first type of push message is based on the reading heat and/or the non-push message of the first type of the application The reading heat determination of the first type of push message of the application is determined.
The method of claim 1 further comprising:

Detecting whether the first type of push message is deleted;

When it is detected that the first type of push message is deleted, the step of acquiring the user habit data corresponding to the application that the permission message is pushed is performed.
The method according to claim 1, wherein the user habit data further comprises: a number of times the user opens the application within a preset time period, an accumulated running time of the application in the preset time period, the The total number of all types of push messages of the application in the preset time period, the number of views of all types of push messages of the application in the preset time period, and the application in the preset time period The number of deletes for all types of push messages.
The method of claim 7, wherein the method further comprises:

Detecting whether the number of deletions of the first type of push messages of the application reaches a preset number;

And deleting, when the number of deletions of the first type of push messages reaches the preset number, deleting all push messages corresponding to the first type currently received by the mobile terminal.
The method of claim 1 further comprising:

When it is detected that the execution times of the steps of all the push cancellations corresponding to the first type currently received by the deleting mobile terminal reach a preset number of times, the first type of push message of the application is rejected.
A mobile terminal, comprising:

An acquiring unit, configured to acquire user habit data corresponding to an application that allows a message to be pushed, where the user habit data includes a deletion ratio of a first type of push message of the application, where the first type of push message is the application Any of all push message types;

a first determining unit, configured to determine whether the deletion ratio is greater than a preset ratio value;

And a deleting unit, configured to delete all the push messages corresponding to the first type currently received by the mobile terminal when the first determining unit determines that the result is yes.
The mobile terminal according to claim 10, wherein the user habit data further includes a priority of the first type of push message of the application, and the mobile terminal further comprises:

a second determining unit, configured to determine, when the first determining unit determines that the result is negative, whether the priority is less than a preset priority threshold;

The deleting unit is further configured to: when the second determining unit determines that the result is yes, delete all the push messages corresponding to the first type currently received by the mobile terminal.
The mobile terminal according to claim 11, wherein the mobile terminal further comprises:

a determining unit, configured to determine, according to a keyword in the push summary of the first push message, a validity period of the first push message, where the first push message is the first Any of a type of push message;

a third determining unit, configured to determine whether the current time exceeds the validity period;

The deleting unit is further configured to delete the first push message when the third determining unit determines that the result is yes.
The mobile terminal according to claim 12, wherein the mobile terminal further comprises:

a fourth determining unit, configured to determine, when the third determining unit determines that the result is negative, whether the same non-push message corresponding to the first push message is read;

The deleting unit is further configured to delete the first push message when the fourth determining unit determines that the result is yes.
The mobile terminal according to any one of claims 10 to 13, characterized in that the priority of the first type of push message is based on the reading heat of the first type of non-push message of the application and/or The reading heat of the first type of push message of the application is determined.
The mobile terminal according to claim 10, wherein the user habit data further comprises a number of times the user opens the application within a preset time period, and an accumulated running time of the application in the preset time period, The total number of all types of push messages of the application in the preset time period, the number of views of all types of push messages of the application in the preset time period, and the preset time period The number of deletions of all types of push messages applied.
The mobile terminal according to claim 15, wherein the mobile terminal further comprises a first detecting unit;

The first detecting unit is configured to detect whether the number of deletions of the first type of push messages of the application reaches a preset number;

The deleting unit is further configured to: when the first detecting unit detects that the number of deletions of the first type of push messages reaches the preset number, delete all the first types corresponding to the mobile terminal currently receiving forward news.
The mobile terminal according to claim 10, wherein the mobile terminal further comprises a second detecting unit and a processing unit;

The second detecting unit is configured to detect whether the number of times the deleting unit performs the deleting operation reaches a preset number of times;

The processing unit is configured to refuse to receive the first type of push message of the application when the second detecting unit detects that the number of times the deleting unit performs the deleting operation reaches the preset number of times.
A mobile terminal, comprising: one or more processors, a memory, a communication unit, and one or more programs, wherein the one or more programs are stored in the memory and configured Executed by one or more processors, the program comprising instructions for performing the steps of the method of any of claims 1-9.
A computer readable storage medium storing a computer program for electronic data exchange, wherein the computer program causes a computer to perform the method of any one of claims 1-9, the computer comprising Mobile terminal.
A computer program product, comprising: a non-transitory computer readable storage medium storing a computer program, the computer program being operative to cause a computer to perform as claimed in any one of claims 1-9 The method described.