CN107332757B - Method for deleting push message and related product - Google Patents
Method for deleting push message and related product Download PDFInfo
- Publication number
- CN107332757B CN107332757B CN201710475904.3A CN201710475904A CN107332757B CN 107332757 B CN107332757 B CN 107332757B CN 201710475904 A CN201710475904 A CN 201710475904A CN 107332757 B CN107332757 B CN 107332757B
- Authority
- CN
- China
- Prior art keywords
- push message
- push
- type
- application
- mobile terminal
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
- H04M1/7243—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/07—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail characterised by the inclusion of specific contents
- H04L51/18—Commands or executable codes
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Human Computer Interaction (AREA)
- Telephone Function (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The embodiment of the invention discloses a method for deleting push messages and a related product, wherein the method comprises the following steps: the method comprises the steps that a mobile terminal obtains user habit data corresponding to an application allowing message pushing, wherein the user habit data comprise a deletion ratio of a first type of pushing message of the application, and the first type of pushing message is any one of all pushing message types of the application; judging whether the deletion proportion is larger than a preset proportion value or not; and if the deletion ratio is larger than the preset ratio value, deleting all push messages corresponding to the first type currently received by the mobile terminal. The embodiment of the invention can automatically delete unnecessary push messages, retain the push messages required by the user and improve the user experience.
Description
Technical Field
The invention relates to the technical field of mobile communication, in particular to a method for deleting push messages and a related product.
Background
With the increasingly wide application of mobile terminals such as smart phones, people in modern life have basically been one mobile phone by one hand. Various applications (APP for short) 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 every day is large, which causes serious interference to the mobile phone user.
In the prior art, there are generally two ways to clear the push message. The first one is: and the user opens the push message notification bar and manually deletes the push message from the notification bar. The second method is as follows: and the user manually sets the push message authority of the application and sets the rejection of the application push message. The first way of clearing the push message requires manual operation of the user each time, and the operation is complicated; in the second method, although the user can refuse to receive all push messages of the application only by one operation, for some applications, the user has a requirement for receiving push messages of the application, but is unwilling to receive all push messages pushed by the application, and the requirement of the user is not met either by directly refuse to receive push messages or allowing to receive push messages.
Disclosure of Invention
The embodiment of the invention provides a method for deleting push messages and a related product, which can automatically delete unnecessary push messages, retain the push messages required by a user and improve the user experience.
A first aspect of an embodiment of the present invention provides a method for deleting a push message, including:
acquiring user habit data corresponding to an application allowing message pushing, wherein the user habit data comprises a deletion proportion of the first type of push message of the application, and the first type of push message is any one of all push message types of the application;
judging whether the deletion proportion is larger than a preset proportion value or not;
and if the deletion proportion is larger than the preset proportion value, deleting all push messages corresponding to the first type currently received by the mobile terminal.
A second aspect of an embodiment of the present invention provides a mobile terminal, including:
an obtaining unit, configured to obtain user habit data corresponding to an application that allows message pushing, 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 one of all push message types of the application;
the first judgment unit is used for judging whether the deletion proportion is larger than a preset proportion value or not;
and the deleting unit is used for deleting all push messages corresponding to the first type currently received by the mobile terminal when the judgment result of the first judging unit is yes.
A third aspect of embodiments of the present invention provides a mobile terminal, including one or more processors, a memory, a communication unit, and one or more programs, where the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the program includes instructions for performing some or all of the steps described in any of the methods of the first aspect of 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 some or all of the steps as described in any one of the methods of the first aspect of embodiments of the present invention.
A fifth aspect of embodiments of the present invention provides a computer program product comprising a non-transitory computer readable storage medium having a computer program stored thereon, the computer program being operable to cause a computer to perform some or all of the steps of a method as described in any one of the first aspects of embodiments of the present invention.
According to the method for deleting the push message, the push message which is not interested by the user can be automatically deleted according to the habit data of the user, the push message which is interested by the user is reserved, and the user experience is improved.
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 description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a schematic diagram of a network architecture according to an embodiment of the present invention;
fig. 2 is a flowchart illustrating a method for deleting a push message according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of a display interface for push messages according to an embodiment of the present invention;
fig. 4 is a flowchart illustrating another method for deleting a push message according to an embodiment of the present invention;
FIG. 5 is a schematic diagram of a mobile terminal according to the present disclosure;
fig. 6 is a schematic structural diagram of another mobile terminal disclosed in the embodiment of the present invention;
fig. 7 is a schematic structural diagram of another mobile terminal disclosed in the embodiment of the present invention.
Detailed Description
In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The terms "first," "second," and the like in the description and claims of the present invention and in the above-described drawings are used for distinguishing between different objects and not for describing a particular order. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the invention. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.
The Mobile terminal according to the embodiment of the present invention may include various handheld devices, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to a wireless modem, and various forms of User Equipment (UE), Mobile Stations (MS), terminal devices (terminal device), and the like, which have wireless communication functions. For convenience of description, the above-mentioned devices are collectively referred to as a mobile terminal.
The following describes embodiments of the present invention in detail.
For better understanding of the embodiments of the present invention, a network architecture to which the embodiments of the present invention are applicable will be described first. Referring to fig. 1, fig. 1 is a schematic diagram of a network architecture according to 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 mobile phone, a tablet computer, or other terminal capable of installing an Application program, and The Application Server 12 may be an Application Server (The Application Server). One or more Applications (APP) may be installed on the mobile terminal 11, and when the mobile terminal 11 is a mobile phone, the applications installed on the mobile phone may also be referred to as a mobile phone client. The application server 12 and the mobile terminal 11 may establish a long connection through a wireless fidelity (WiFi) network or an operator network (e.g., 3G, 4G network), and an application (also referred to as a client) on the mobile terminal 11 may periodically send a heartbeat to the application server 12 to maintain the long connection. The application server 12 may push a message to the application installed by the mobile terminal 11 over the long connection established as described above.
Referring to fig. 2, fig. 2 is a flowchart illustrating a method for deleting a push message according to an embodiment of the present invention, and as shown in fig. 2, the method for deleting a push message includes the following steps.
The mobile terminal obtains user habit data corresponding to an application allowing message pushing, wherein the user habit data comprises a deletion ratio of a first type of pushing message of the application, and the first type of pushing message is any one of all pushing message types of the application.
202, the mobile terminal judges whether the deletion ratio is larger than a preset ratio value.
And 203, if the deletion proportion is larger than the preset proportion value, the mobile terminal deletes all push messages corresponding to the first type currently received by the mobile terminal.
In the embodiment of the invention, the mobile terminal can be provided with one or more applications, one part of the applications installed on the mobile terminal allows the mobile terminal to receive the push message, and the other part of the applications does not allow the mobile terminal to receive the push message. For example, the terminal is installed with 100 applications, 60 of which are applications for allowing message push, and 40 of which are applications for prohibiting message push. The user can close or open the message pushing switch of the application, when the message pushing switch of a certain application is opened, the application is the application allowing message pushing, and when the message pushing switch of a certain application is closed, the application is the application forbidding message pushing. An application that allows message push may receive all kinds of push messages sent by the application server. For example, if the application a is a news application, the application a may receive various types of push messages such as "sports news push message", "entertainment news push message", "financial news push message", "life news push message" and the like pushed by the application server.
The user habit data corresponding to the application can be the usage habit of the user for the application counted by the mobile terminal in the past period of time (for example, in one week). For example, for the application a, user habit data such as the number of times the user opens the application a in a past period of time, the cumulative duration of using the application a, the total number of various types of push messages of the application a, the number of views of various types of push messages of the application a, the number of deletions of various types of push messages of the application a, and the like may be counted.
The first type of push message in step 201 is any of all 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, or the mobile terminal may also respectively obtain the deletion ratios of all types of push messages of the application. The deletion ratio of the first type of push message may be understood as a ratio of the number of deleted pieces of the first type of push message of the application to the total number of the first type of push messages of the application. For example, if the application a is a news-type application, in the past week, if the total number of pieces of the first type of push message (e.g., sports-type news push message) of the application a is 20, the number of viewed pieces is 2, the number of deleted pieces is 3, and the number of unviewed pieces is 15, the deletion ratio of the first type of push message of the application a is 3/20-15%. Push messages may have three states: "not viewed", "deleted". When a push message is pushed to a mobile terminal, the initial state is "not viewed", if the user views the push message, the state of the push message is changed to "viewed", if the user deletes the push message, the state of the push message is changed to "deleted", and if the user does not perform any processing on the push message, the state of the push message is still "not viewed". It is generally considered that if the status of a push message changes from "not viewed" to "viewed", it indicates that the user is interested in the push message; if the status of a push message changes from "not viewed" to "deleted," this indicates that the user is not interested in the push message.
It will be appreciated that a push message, if viewed, is not present and is automatically deleted from the push notification bar. However, the push message being viewed is different from the push message being deleted. When the push message is viewed, the state of the message is marked as viewed, and after the user clicks the push message, the mobile terminal enters a display interface corresponding to the push message. When the push message is deleted, the state of the message is marked as 'deleted', the mobile terminal directly deletes the push message and does not enter a display interface corresponding to the push message. As can be seen, a push message being deleted means that the push message is not viewed and is 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 ratio of step 202 may be preset, for example, may be set to 5%, 10%, 15%, 20%, 30%, 50%, etc. If the deletion proportion of the first type of push message of the application A is 15% and the preset proportion value 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 all push messages corresponding to the first type currently received by the mobile terminal.
For example, if the application a is a news application, within the past week, if the total number of pieces of the first type of push messages of the application a (e.g., sports news push messages) is 20, the number of pieces viewed is 0, and the number of pieces deleted is 3 (the number of pieces of the first type of push messages of the application a currently received by the mobile terminal is 17), the mobile terminal acquires that the deletion ratio of the first type of push messages of the application a is 3/20-15%, and determines that the deletion ratio of the first type of push messages of the application a is greater than a preset ratio value (e.g., the preset ratio value is 10%), the mobile terminal deletes all push messages of the first type of the application a currently received (17).
In an application scenario, when the mobile terminal detects that a push message of the first type is deleted, the mobile terminal starts to execute 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 obtains a deletion ratio of the first type of push message of the application; and when the deletion proportion of the first type of push message of the application is judged to be larger than the preset proportion value, the mobile terminal deletes all push messages corresponding to the currently received first type. Referring to fig. 3, fig. 3 is a schematic view of a display interface for pushing a message according to an embodiment of the present invention. The pull-down push notification bar of the mobile terminal 100 of fig. 3, which is the left side of fig. (a), displays a total of 12 push messages that have received a certain application, where the number of push messages of the first type is 9, the number of push messages of the second type is 2, and the number of push messages of the third type is 1. As shown in the left diagram (a) in 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, i.e., deletes the first type of push message a, at this time, the mobile terminal detects that the deletion proportion of the first type of push message is 1/9> 10% (preset proportion value), i.e., the mobile terminal deletes all push messages corresponding to the currently received first type, and the effect after deletion is shown in the right diagram (b) in fig. 3.
In the above embodiment, whether the deletion ratio is greater than the preset ratio value is used as the determination criterion, and of course, whether the deletion number is greater than the preset number may also be used as the determination criterion in the embodiment of the present invention. For example, when the terminal detects that the deletion number of the first type of push message of the application reaches two times, the mobile terminal deletes all currently received push messages corresponding to the first type. The embodiment of the invention can also take whether the continuous deletion number is larger than the preset number as the judgment standard. For example, when the terminal detects that two consecutive push messages of the first type 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 times of executing step 203 reaches a preset number of times (e.g., 2 times, 3 times, 4 times, etc.), that is, the user does not interest the first type of push message of the application for multiple times, the terminal refuses to receive the first type of push message of the application, that is, the subsequent application server does not push the first type of push message of the application to the terminal any more. By implementing the scheme, the mobile terminal can refuse to receive the certain type of push message of the application when detecting that the user is uninterested in the certain type of application for many times, and can refuse to receive the uninterested push message of the user according to the habit of the user, so that the user experience is further improved.
By implementing the method shown in fig. 2, the mobile terminal can automatically delete the push message which is not interested by the user according to the habit data of the user, retain the push message which is interested by the user, avoid the interference of the push message which is not interested by the user to the user, and improve the user experience.
Referring to fig. 4, fig. 4 is a flowchart illustrating another method for deleting a push message according to an embodiment of the present invention, and as shown in fig. 4, the method for deleting a push message includes the following steps.
401, the mobile terminal obtains user habit data corresponding to an application allowing message pushing, where the user habit data includes a deletion ratio of a 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 push message is any one of all push message types of the application.
In the embodiment of the invention, the priority of each type of push message of the application installed on the mobile terminal can be preset and stored in the nonvolatile memory of the mobile terminal. Generally, a higher priority indicates a higher level of user interest. For example, for the 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, and if the preset priority threshold is 2, the priority of the first type of push message is smaller than the preset priority threshold, which indicates that the user is not interested in the first type of push message of the application a, and the mobile terminal deletes all push messages corresponding to the first type of application a that are currently received.
402, the mobile terminal determines whether the deletion ratio is greater than a preset ratio value. If yes, go to step 403, otherwise go to step 404.
And 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 the priority of the first type of push message is less than a preset priority threshold. If yes, go to step 403, otherwise go to step 405.
405, the mobile terminal determines a validity period of the first push message according to a keyword in a push abstract of the first push message, where the first push message is any one of the first type of push messages.
The push abstract of the push message refers to an abstract displayed in a push notification bar of the push message, the purpose of displaying the push abstract is to facilitate a user to quickly know contents in the push message, and the push abstract is generally a title, a content summary and the like of the message and generally does not exceed 30 words. Some push messages are time sensitive, such as weather push messages, live push messages, coupon push messages, and so on. For example, if the push summary of the push message a is "XX match is being live", indicating that the push message is a live push message, the validity period of the push message is the time point until the match ends; if the push abstract of the push message a is "thunderstorm exists at 3-5 pm today", indicating that the push message is a weather push message, the validity period of the push message is 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 its push value, so the terminal deletes the push message. In addition, if some push messages cannot accurately determine their validity period according to the push abstract, the validity period may be set to a preset fixed value, for example, a validity period of 72 hours.
406, the mobile terminal determines whether the current time exceeds the validity period. If yes, go to step 407, otherwise go to step 408.
The mobile terminal deletes the first push message 407.
408, the mobile terminal determines whether a non-push message identical to the first push message is read. If yes, go to step 407, otherwise, go back to step 406.
A non-push message refers to a message displayed on a display interface of an application. After entering a display interface of an application, the display interface of the application can display a plurality of messages, and after clicking a certain message, a user can enter the display interface of the message, so that the user can read the message. The display interface of the application often displays various types of messages, so that the user can browse and read conveniently. Generally, the application server will select some popular messages among all messages displayed on the display interface of the application or messages of interest to the user to be pushed to the mobile terminal as push messages. 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 subsequently receive the push message of the message a; if the user of the mobile terminal has read message a on the display interface of the application and the message a has been pushed to the mobile terminal as a push message, the mobile terminal deletes the push message a from the push notification bar of the push message. By implementing the embodiment of the invention, the mobile terminal can judge which messages are read by the user, the messages which are read are not pushed any more subsequently no matter the messages are pushed messages or non-pushed messages, if the non-pushed messages are read, the pushed messages which are the same as the non-pushed messages are deleted, the pushed messages which are read by the user and are the same as the non-pushed messages are deleted, the user is prevented from repeatedly reading the same pushed messages, and the user experience is improved.
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 reading bars and the total reading time of the first type of non-push message in a past period (e.g., in a week). For example, in the past week, if the total number of reading pieces of the first type of non-push message of the application a on the mobile terminal is 10 and the total reading time is 30 minutes, the reading heat is: 10+ 30/3-20. The correspondence between the reading heat and the priority is as follows: a reading heat of [0-10 ] ((0-10) meaning greater than 0 and less than 10) corresponds to a priority of 0, a reading heat of [10-20 ] ([10-20) meaning greater than or equal to 10 and less than 20) corresponds to a priority of 1, a reading heat of [20-30 ] ([20-30) meaning greater than or equal to 20 and less than 30) corresponds to a priority of 2, and so on. Therefore, a reading hot of 20 corresponds to a priority of 2.
Implementing the method shown in fig. 4, whether to delete the push message can be determined by determining the deletion ratio of the push message, the priority of the push message, the validity period of the push message, and whether to read the non-push message that is the same as the push message. Various modes of deleting the push messages are considered, the push messages which are not interested by the user, the push messages which are not needed by the user and the push messages which are read by the user are deleted as far as possible, the number of the push messages on the push notification bar is reduced, and the user experience is improved.
The above description has introduced the solution of the embodiment of the present invention mainly from the perspective of the method-side implementation process. It is understood that the mobile terminal includes hardware structures and/or software modules for performing the respective functions in order to implement the above-described functions. Those of skill in the art will readily appreciate that the present invention can be implemented in hardware or a combination of hardware and computer software, with the exemplary elements and algorithm steps described in connection with the embodiments disclosed herein. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The embodiment of the present invention may perform the division of the functional units for the mobile terminal according to the method example described above, for example, each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit. The integrated unit can be realized in a form of hardware, and can also be realized in a 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 logic function division, and there may be another division manner in actual implementation.
Referring to fig. 5, fig. 5 is a schematic structural diagram of a mobile terminal according to the present disclosure, 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:
an obtaining unit 501, configured to obtain user habit data corresponding to an application that allows message pushing, where the user habit data includes a deletion ratio of a first type of push message of the application, and the first type of push message is any one of all types of push messages of the application.
The first determining unit 502 is configured to determine whether the deletion ratio is greater than a preset ratio value.
A deleting unit 503, configured to delete all push messages corresponding to the first type currently received by the mobile terminal when the determination result of the first determining unit 502 is yes.
By implementing the mobile terminal shown in fig. 5, the mobile terminal can automatically delete the push messages which are not interested by the user according to the habit data of the user, retain the push messages which are interested by the user, and improve the user experience.
Optionally, the mobile terminal 500 further includes a second determining unit 504, where:
a second judging unit 504, configured to judge whether the priority is smaller than a preset priority threshold when the judgment result of the first judging unit 502 is negative.
The deleting unit 503 is further configured to delete all push messages corresponding to the first type currently received by the mobile terminal when the second determining unit 504 determines that the push message is a push message.
Optionally, the mobile terminal 500 further includes a determining unit 505 and a third determining unit 506, where:
a determining unit 505, configured to determine, when the second determining unit 504 determines that the first push message is a first type of push message, a validity period of the first push message according to a keyword in a push summary of the first push message.
A third judging unit 506, configured to judge 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:
a fourth judging unit 507, configured to judge whether the non-push message that is the same as the first push message is read or not when the third judging unit 506 judges that the result is negative.
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.
The mobile terminal in the embodiment of the invention can determine whether to delete the push message by judging the deletion proportion of the push message, the priority of the push message, the validity period of the push message and whether the non-push message which is the same as the push message is read. Various modes of deleting the push messages are considered, the push messages which are not interested by the user, the push messages which are not needed by the user and the push messages which are read by the user are deleted as far as possible, the number of the push messages on the push notification bar is reduced, and the user experience is improved.
Referring 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, where the one or more programs are stored in the memory 602 and configured to be executed by the one or more processors 601, the programs including instructions for performing the steps of fig. 2-4 described above. The processor 601, the memory 602, and the communication unit 603 may be connected by a communication bus 604.
The communication unit 603 is configured to establish a communication channel, enable the mobile terminal 600 to connect to a correspondent node or a base station through the communication channel, and exchange data with the correspondent node or the base station through the communication channel. The Communication unit 603 may include a Wireless Local Area Network (Wireless LAN) module, a bluetooth module, Near Field Communication (NFC) module, a baseband (Base Band) module, and other Wireless Communication modules, and a wired Communication module such as an ethernet, a Universal Serial Bus (USB), and a lightning interface. The communication unit 603 is used for communication between each component in the mobile terminal 600 and a communication peer or a base station, and may support Direct Memory Access (Direct Memory Access).
The processor 601 may include only a Central Processing Unit (CPU), or may be a combination of a CPU, a Digital Signal Processor (DSP), a Graphics Processing Unit (GPU), and a control chip (e.g., a baseband chip) in the communication Unit. In the embodiment of the present invention, the CPU may be a single operation core, or may include multiple operation cores.
By implementing the mobile terminal shown in fig. 6, the mobile terminal can automatically delete the push messages which are not interested by the user according to the habit data of the user, retain the push messages which are interested by the user, and improve the user experience.
As shown in fig. 7, for convenience of description, only the parts related to the embodiment of the present invention are shown, and details of the specific technology are not disclosed, please refer to the method part in the embodiment of the present invention. The mobile terminal may be any terminal device including a mobile phone, a tablet computer, a PDA (Personal Digital Assistant), a POS (Point of Sales), a vehicle-mounted computer, and the like, taking the mobile terminal as the mobile phone as an example:
fig. 7 is a block diagram illustrating a partial structure of a mobile phone related to a mobile terminal according to an embodiment of the present invention. Referring to fig. 7, the handset 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, a processor 980, and a power supply 990. Those skilled in the art will appreciate that the handset configuration shown in fig. 7 is not intended to be limiting and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.
The following describes each component of the mobile phone in detail with reference to fig. 7:
The memory 920 may be used to store software programs and modules, and the processor 980 may execute various functional applications and data processing of the mobile phone by operating the software programs and modules stored in the memory 920. The memory 920 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required for at least one function, and the like; the storage data area may store data created according to the use of the mobile phone, and the like. Further, the memory 920 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, or other volatile solid state storage device.
The input unit 930 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the cellular phone. Specifically, the input unit 930 may include a fingerprint recognition module 931, a touch display 932, and other input devices 933. Fingerprint identification module 931, can gather the fingerprint data of user above it. The input unit 930 may include other input devices 932 in addition to the fingerprint recognition module 931. In particular, other input devices 932 may include, but are not limited to, one or more of a touch screen, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like.
The display unit 940 may be used to display information input by the user or information provided to the user and various menus of the mobile phone. The display unit 940 may include a display screen 941, and optionally, the display screen 941 may 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 are shown as two separate components to implement the input and output functions of the mobile phone, in some embodiments, the fingerprint recognition module 931 and the display screen 941 may be integrated to implement the input and output functions of the mobile phone.
The handset may also include at least one 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 ambient light, and the proximity sensor may turn off the display screen 941 and/or the backlight when the mobile phone is moved to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally, three axes), can detect the magnitude and direction of gravity when stationary, and can be used for applications of recognizing the posture of a mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer and tapping), and the like; as for other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor, which can be configured on the mobile phone, further description is omitted here.
WiFi belongs to short-distance wireless transmission technology, and the mobile phone can help a user to receive and send e-mails, browse webpages, access streaming media and the like through the WiFi module 970, and provides wireless broadband Internet access for the user. Although fig. 7 shows the WiFi module 970, it is understood that it does not belong to the essential constitution of the handset, and can be omitted entirely as needed within the scope not changing the essence of the invention.
The processor 980 is a control center of the mobile phone, connects various parts of the entire mobile phone by using various interfaces and lines, and performs various functions of the mobile phone and processes data by operating or executing software programs and/or modules stored in the memory 920 and calling data stored in the memory 920, thereby integrally monitoring the mobile phone. Alternatively, processor 980 may include one or more processing units; preferably, the processor 980 may integrate an application processor, which primarily handles operating systems, user interfaces, applications, etc., and a modem processor, which primarily handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 980.
The handset also includes a power supply 990 (e.g., a battery) for supplying power to the various components, which may preferably be logically connected to the processor 980 via a power management system, thereby providing management of charging, discharging, and power consumption via the power management system.
Although not shown, the mobile phone may further include a camera, a bluetooth module, etc., which are not described herein.
Embodiments of the present invention further provide a computer storage medium, where the computer storage medium stores a computer program for electronic data exchange, and the computer program enables a computer to execute part or all of the steps of any one of the methods for deleting a push message as described in the above method embodiments.
Embodiments of the present invention also provide a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to cause a computer to execute part or all of the steps of any one of the methods for deleting push messages as set forth in the above method embodiments.
It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present invention is not limited by the order of acts, as some steps may occur in other orders or concurrently in accordance with the invention. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required by the invention.
In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus may be implemented in other manners. For example, the above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one type of division of logical functions, and there may be other divisions when actually implementing, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of some interfaces, devices or units, and may be an electric or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a 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 stand-alone product, may be stored in a computer readable memory. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a memory and includes several instructions for causing a computer device (which may be a personal computer, a server, a network device, or the like) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned memory comprises: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.
Those skilled in the art will appreciate that all or part of the steps in the methods of the above embodiments may be implemented by associated hardware instructed by a program, which may be stored in a computer-readable memory, which may include: flash Memory disks, Read-Only memories (ROMs), Random Access Memories (RAMs), magnetic or optical disks, and the like.
The above embodiments of the present invention are described in detail, and the principle and the implementation of the present invention are explained by applying specific embodiments, and the above description of the embodiments is only used to help understanding the method of the present invention and the core idea thereof; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.
Claims (12)
1. A method of deleting push messages, comprising:
when detecting that one push message of a first type is deleted, acquiring user habit data corresponding to an application allowing message pushing, wherein the user habit data comprises a deletion proportion of the first type of push message of the application deleted by the user, the first type of push message is any one of all push message types of the application, and the deletion proportion of the first type of push message deleted by the user comprises a ratio of the number of deleted pieces of the first type of push message of the application deleted by the user to the total number of the first type of push message of the application; the push message comprises a push abstract, and the push abstract comprises a title and a content abstract of the push message;
judging whether the deletion proportion is larger than a preset proportion value or not;
and if the deletion proportion is larger than the preset proportion value, deleting all push messages corresponding to the first type currently received by the mobile terminal.
2. The method of claim 1, wherein the user habit data further comprises a priority of the first type of push message for the application, the method further comprising:
if the deletion proportion is smaller than or equal to the preset proportion value, judging whether the priority is smaller than a preset priority threshold value;
and if the priority is smaller than the preset priority threshold, deleting all push messages corresponding to the first type currently received by the mobile terminal.
3. The method of claim 2, further comprising:
if the priority is greater than or equal to the preset priority threshold, determining the validity period of a first push message according to a keyword in a push abstract of the first push message, wherein the first push message is any one of the first type of push messages;
judging whether the current time exceeds the validity period;
and if the current time exceeds the validity period, deleting the first push message.
4. The method of claim 3, further comprising:
if the current time does not exceed the validity period, judging whether a non-push message which is the same as the first push message is read or not;
deleting the first push message if a non-push message identical to the first push message has been read.
5. The method of any of claims 1-4, wherein the priority of the first type of push message is determined based on a reading hotness of the first type of non-push message of the application and/or a reading hotness of the first type of push message of the application.
6. A mobile terminal, comprising:
an obtaining unit, configured to obtain, when it is detected that a piece of push message of a first type is deleted, user habit data corresponding to an application that allows message pushing, where the user habit data includes a deletion proportion of the push message of the first type of the application deleted by the user, and the push message of the first type is any one of all push message types of the application, and the deletion proportion of the push message of the first type deleted by the user includes a ratio of a number of deleted pieces of the push message of the first type of the application deleted by the user to a total number of push messages of the first type of the application; the push message comprises a push abstract, and the push abstract comprises a title and a content abstract of the push message;
the first judgment unit is used for judging whether the deletion proportion is larger than a preset proportion value or not;
and the deleting unit is used for deleting all push messages corresponding to the first type currently received by the mobile terminal when the judgment result of the first judging unit is yes.
7. The mobile terminal of claim 6, wherein the user habit data further comprises a priority of the first type of push message for the application, the mobile terminal further comprising:
the second judging unit is used for judging whether the priority is smaller than a preset priority threshold or not when the judging result of the first judging unit is negative;
the deleting unit is further configured to delete all push messages corresponding to the first type currently received by the mobile terminal when the determination result of the second determining unit is yes.
8. The mobile terminal of claim 7, wherein the mobile terminal further comprises:
a determining unit, configured to determine, when the second determination unit determines that the first type of push message is a first type of push message, a validity period of the first type of push message according to a keyword in a push summary of the first type of push message;
a third judging unit configured to judge whether or not 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.
9. The mobile terminal of claim 8, wherein the mobile terminal further comprises:
a fourth judging unit, configured to judge whether a non-push message that is the same as the first push message is read or not when the third judging unit judges that the result is negative;
the deleting unit is further configured to delete the first push message when the fourth determining unit determines that the result is yes.
10. The mobile terminal according to any of claims 6-9, wherein 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.
11. A mobile terminal comprising one or more processors, memory, a communications unit, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the programs comprising instructions for performing the steps of the method of any of claims 1-5.
12. A computer-readable storage medium, characterized in that it stores a computer program for electronic data exchange, wherein the computer program causes a computer to perform the method according to any one of claims 1-5, the computer comprising a mobile terminal.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710475904.3A CN107332757B (en) | 2017-06-21 | 2017-06-21 | Method for deleting push message and related product |
| PCT/CN2018/090148 WO2018233492A1 (en) | 2017-06-21 | 2018-06-06 | Method for deleting push message, and related product |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710475904.3A CN107332757B (en) | 2017-06-21 | 2017-06-21 | Method for deleting push message and related product |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107332757A CN107332757A (en) | 2017-11-07 |
| CN107332757B true CN107332757B (en) | 2020-09-22 |
Family
ID=60194004
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710475904.3A Active CN107332757B (en) | 2017-06-21 | 2017-06-21 | Method for deleting push message and related product |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN107332757B (en) |
| WO (1) | WO2018233492A1 (en) |
Families Citing this family (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107332757B (en) * | 2017-06-21 | 2020-09-22 | Oppo广东移动通信有限公司 | Method for deleting push message and related product |
| CN108366167B (en) * | 2018-01-29 | 2020-09-22 | 维沃移动通信有限公司 | Message reminding method and mobile terminal |
| CN108664640A (en) * | 2018-05-16 | 2018-10-16 | 苏州达家迎信息技术有限公司 | Information processing method, storage medium and terminal device |
| CN110971643B (en) * | 2018-09-30 | 2022-07-29 | 北京国双科技有限公司 | Message pushing method and device, storage medium and processor |
| CN109600295A (en) * | 2018-10-23 | 2019-04-09 | 深圳壹账通智能科技有限公司 | Notification bar information push method, device, medium and electronic equipment |
| CN109525672A (en) * | 2018-11-27 | 2019-03-26 | 重庆长安汽车股份有限公司 | Vehicle-mounted content push system, method and computer readable storage medium |
| CN110187893B (en) * | 2019-05-21 | 2023-12-08 | 维沃移动通信有限公司 | Method for deleting application, mobile terminal and computer readable storage medium |
| CN110224925B (en) * | 2019-05-22 | 2022-02-01 | 维沃移动通信有限公司 | Message management and mobile terminal |
| CN112084043A (en) * | 2020-08-10 | 2020-12-15 | 五八有限公司 | Management method and device of push message, electronic equipment and storage medium |
| CN112260936B (en) * | 2020-10-22 | 2022-07-15 | Oppo广东移动通信有限公司 | Notification message management method, device, terminal and storage medium |
| CN113689681A (en) * | 2021-06-28 | 2021-11-23 | 深圳市爱都科技有限公司 | User reminding method and device and wearable device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104158865A (en) * | 2014-08-01 | 2014-11-19 | 北京奇虎科技有限公司 | Method and system for pushing applications to terminal |
| CN105516151A (en) * | 2015-12-15 | 2016-04-20 | 北京奇虎科技有限公司 | Scanning-killing method and device of backdoor file |
| CN106453382A (en) * | 2016-10-28 | 2017-02-22 | 努比亚技术有限公司 | Message pushing method and device |
| CN106815079A (en) * | 2016-12-30 | 2017-06-09 | 广东欧珀移动通信有限公司 | The method and mobile terminal of a kind of popular application control |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103501485B (en) * | 2013-09-22 | 2017-12-29 | 小米科技有限责任公司 | Push the method, apparatus and terminal device of application |
| CN104135424B (en) * | 2014-02-14 | 2015-11-18 | 腾讯科技（深圳）有限公司 | A kind of application message method for pushing, server, terminal and system |
| CN104270429B (en) * | 2014-09-19 | 2017-12-08 | 北京奇虎科技有限公司 | A kind of method and apparatus for pushing VAS application -to-terminal service |
| KR20160035753A (en) * | 2014-09-24 | 2016-04-01 | 삼성전자주식회사 | Method and apparatus for automatically creating message |
| CN105553767B (en) * | 2015-12-15 | 2018-12-25 | 北京奇虎科技有限公司 | Website backdoor file detection method and device |
| CN106227563A (en) * | 2016-07-22 | 2016-12-14 | 北京奇虎科技有限公司 | The data processing method of a kind of application program and relevant device |
| CN106791153A (en) * | 2016-12-30 | 2017-05-31 | 奇酷互联网络科技（深圳）有限公司 | Using PUSH message classifying indication method, device and mobile terminal |
| CN107332757B (en) * | 2017-06-21 | 2020-09-22 | Oppo广东移动通信有限公司 | Method for deleting push message and related product |
-
2017
- 2017-06-21 CN CN201710475904.3A patent/CN107332757B/en active Active
-
2018
- 2018-06-06 WO PCT/CN2018/090148 patent/WO2018233492A1/en active Application Filing
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104158865A (en) * | 2014-08-01 | 2014-11-19 | 北京奇虎科技有限公司 | Method and system for pushing applications to terminal |
| CN105516151A (en) * | 2015-12-15 | 2016-04-20 | 北京奇虎科技有限公司 | Scanning-killing method and device of backdoor file |
| CN106453382A (en) * | 2016-10-28 | 2017-02-22 | 努比亚技术有限公司 | Message pushing method and device |
| CN106815079A (en) * | 2016-12-30 | 2017-06-09 | 广东欧珀移动通信有限公司 | The method and mobile terminal of a kind of popular application control |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107332757A (en) | 2017-11-07 |
| WO2018233492A1 (en) | 2018-12-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107332757B (en) | Method for deleting push message and related product | |
| CN107708168B (en) | SIM card switching method, mobile terminal and computer readable storage medium | |
| CN107277230B (en) | Voice broadcasting method of message and related product | |
| CN107295173B (en) | Method for deleting chat messages and related product | |
| CN107146616B (en) | Equipment control method and related product | |
| CN107272872B (en) | Power saving control method and related product | |
| CN107222914B (en) | Application control method and related product | |
| CN107357833B (en) | Data processing method and related product | |
| CN107480489B (en) | unlocking control method and related product | |
| CN107634952B (en) | Method and device for determining brushing amount resource, service equipment, mobile terminal and storage medium | |
| CN107346397B (en) | Information processing method and related product | |
| CN106776038B (en) | Hot application resource allocation method and mobile terminal | |
| CN110209245B (en) | Face recognition method and related product | |
| CN106528638B (en) | Method for deleting backup data and mobile terminal | |
| CN109922539B (en) | Network connection method and related product | |
| CN111919505B (en) | Data processing method and terminal | |
| CN106851345B (en) | Information pushing method, system and server | |
| CN106714277B (en) | Network connection method and terminal | |
| CN107272985B (en) | Notification message processing method and related product | |
| WO2018233491A1 (en) | Push message management method and related product | |
| CN110428782B (en) | Brightness adjusting method and related product | |
| CN106815079B (en) | Hot application control method and mobile terminal | |
| CN110100424B (en) | Streaming media data processing method and mobile terminal | |
| CN106815078B (en) | Memory control method and equipment | |
| CN112135321B (en) | Channel switching method and related product |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: Changan town in Guangdong province Dongguan 523860 usha Beach Road No. 18 Applicant after: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS Corp.,Ltd. Address before: Changan town in Guangdong province Dongguan 523860 usha Beach Road No. 18 Applicant before: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS Corp.,Ltd. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |