WO2015085928A1

WO2015085928A1 - Method and device for message pushing management cross-reference to related applications

Info

Publication number: WO2015085928A1
Application number: PCT/CN2014/093504
Authority: WO
Inventors: Xiaodan LIN
Original assignee: Tencent Technology (Shenzhen) Company Limited
Priority date: 2013-12-13
Filing date: 2014-12-10
Publication date: 2015-06-18
Also published as: CN104717616A

Abstract

A method and a device for pushing pushed messages are provided. In the method: a mobile terminal obtains a super user permission of an operating system in the mobile terminal; scans message pushing environment of the mobile terminal with using the super user permission and then displaying multiple scanning results; detects an operating instruction which is acted on one of the scanning results selected by a user; carries out message pushing management in the mobile terminal according to the detected operating instruction.

Description

METHOD AND DEVICE FOR MESSAGE PUSHING MANAGEMENT CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to Chinese Patent Application No. 201310687892.2, filed on December 13, 2013, which is hereby incorporated by reference in its entirety.

FIELD

The present disclosure relates to the technology field of mobile terminals, and more particularly to a method and a device for message pushing management.

BACKGROUND

At present, applications in mobile terminals mostly provide a message pushing function, and proactively push the updated SMS (short message service) , emails, schedule reminders and the like without users refreshing the applications manually. However, with the increase of the applications installed in the mobile terminals, the message pushing happens more and more frequently, which increases power consumption of mobile terminals, and disturbs users to use mobile terminals normally on the other hand.

At present, if setting the message pushing function of the applications in a mobile terminal is needed, it is necessary to enter the setting center of each application respectively and to complete the operation of disabling or enabling the message pushing function in the setting center, which is cumbersome.

SUMMARY

Embodiments of the present disclosure aim at providing a method for message pushing management, which solves the problem that the operation of disabling or enabling the message pushing function is completed only on condition of entering the setting center of each application respectively in the conventional technology.

In a first aspect, the embodiments of the present disclosure provide a method for message pushing management. The method includes: obtaining a super user permission of an operating system in a mobile terminal； scanning message pushing environment of the mobile terminal with using the super user permission and then displaying multiple scanning results； detecting an operating instruction which is acted on one of the scanning results selected by a user； and carrying out message pushing management in the mobile terminal according to the detected operating instruction.

In a second aspect, the embodiments of the present disclosure provide a device for message pushing management. The device includes a hardware processor and a non-transitory storage medium accessible to the hardware processor, the non-transitory storage medium configured to store units including: an obtaining unit, a scanning unit, a detecting unit, and a managing unit. The obtaining unit is programmed to obtain a super user permission of an operating system in a mobile terminal. The scanning unit is programmed to scan message push environment of the mobile terminal using the super user permission and then displaying multiple scanning results. The detecting unit is programmed to detect an operating instruction which is acted on one of the scanning results selected by a user. The managing unit is programmed to carry out message pushing management in the mobile terminal according to the detected operating instruction.

Based on the super user permissions of the operating systems in the mobile terminals, the embodiments of the present disclosure provide message pushing settings of the applications with a unified management platform, so as to directly manage message pushing environment of the mobile terminals by means of the management platform, which simplifies operation steps of message pushing management and improves operation efficiency of message pushing management.

BRIEF DESCRIPTION OF THE DRAWINGS

To explain the technical solutions of the embodiments of the present disclosure, accompanying drawings used in the embodiments are followed. Apparently, the following drawings merely illustrate some embodiments of the disclosure, but for persons skilled in the art, other drawings can be obtained without creative works according to these drawings.

ig. 1 is an implementing flowchart of a method for message pushing management according to embodiments of the present disclosure； and

Fig. 2 is a structure frame of a device for message pushing management according to embodiments of the present disclosure； and

Fig. 3 is a block diagram of a partial device according to embodiments of the present disclosure.

DETAILED DESCRIPTION OF THE DRAWINGS

Reference throughout this specification to “one embodiment, ” “an embodiment, ” “example embodiment, ” or the like in the singular or plural means that one or more particular features, structures, or characteristics described in connection with an embodiment is included in at least one embodiment of the present disclosure. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment, ” “in an example embodiment, ” or the like in the singular or plural in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

The terminology used in the description of the disclosure herein is for the purpose of describing particular examples only and is not intended to be limiting of the disclosure. As used in the description of the disclosure and the appended claims, the singular forms “a, ” “an, ” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. Also, as used in the description herein and throughout the claims that follow, the meaning of “in” includes “in” and “on” unless the context clearly dictates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “may include, ” “including, ” “comprises, ” and/or “comprising, ” when used in this specification, specify the presence of stated features, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, operations, elements, components, and/or groups thereof.

As used herein, the term “module” or “unit” may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC) ； an electronic circuit； a combinational logic circuit； a field programmable gate array (FPGA) ； a processor (shared, dedicated, or group) that executes code； other suitable hardware components that provide the described functionality； or a combination of some or all of the above, such as in a system-on-chip. The term module or unit may include memory (shared, dedicated, or group) that stores code executed by the processor.

The exemplary environment may include a server, a client, and a communication network. The server and the client may be coupled through the communication network for information exchange, such as sending/receiving identification information, sending/receiving data files such as splash screen images, etc. Although only one client and one server are displayed in the environment, any number of terminals or servers may be included, and other devices may also be included.

The communication network may include any appropriate type of communication network for providing network connections to the server and client or among multiple servers or clients. For example, communication network may include the Internet or other types of computer networks or telecommunication networks, either wired or wireless. In a certain embodiment, the disclosed methods and apparatus may be implemented, for example, in a wireless network that includes at least one client.

In some cases, the client may refer to any appropriate user terminal with certain computing capabilities, such as a personal computer (PC) , a work station computer, a server computer, a hand-held computing device (tablet) , a smart phone or mobile phone, or any other user-side computing device. In various embodiments, the client may include a network access device. The client may be stationary or mobile.

A server, as used herein, may refer to one or more server computers configured to provide certain server functionalities, such as database management and search engines. A server may also include one or more processors to execute computer programs in parallel.

A user, as used herein, may refer to one or more persons or things that control a client. The user may control more than one clients or other devices.

Referring to Figures, wherein the same component labels represent the same component. The principle of this disclosure is illustrated by being executed in an appropriate operation environment. The description followed is based on the specific embodiments illustrated in this disclosure, and is not intended to limit the present disclosure.

To make the purpose, technical proposals and advantages of the present disclosure more clear, the following explanations on the present disclosure provide a more detailed description associating with the drawings and embodiments as well. It is to be understood that the embodiments described here is merely to explain the present disclosure, but not to limit the present disclosure.

The embodiments of the present disclosure are implemented based on the super user permissions of the operating systems in the mobile terminals, and provide message pushing settings of the applications with a unified management platform, so as to directly manage message pushing environment of the mobile terminals by means of the management platform, which simplifies operation steps of message pushing management and improves operation efficiency of message pushing management.

Fig. 1shows the implementing process of the method for message pushing management according to an embodiment of the present disclosure, which is described thereinafter:

step S101: obtaining a super user permission of an operating system in a mobile terminal.

The super user permission, is namely a root privilege, wherein the root is the super administrator user account in the Linux system and Unix system. The account has the supremacy in the entire system, and all the objects (such as application installation, message pushing reminders and the like in a mobile terminal) are able to be operated by the root account. Therefore, once an executor obtains the root privilege, the executor obtains the top permission of the operating system in the mobile terminal based on Linux system development or Unix system development, thus the executor can perform any operations including addition, deletion, modification, query and the like on any files, processes and even hardware in the mobile terminal.

In the present embodiment, a root privilege is obtained by means of the specialized rootsoftware. When the executive body in the embodiment of the present disclosure is third-party management software such as QQSecure, Mobile Phone Optimizer and the like in a mobile terminal, the third-party management software can be authorized by the root account so as to obtain the root privilege.

step S102: scanning message pushing environment of the mobile terminal with using the super user permission and then displaying multiple scanning results.

In the present embodiment, after obtaining a root privilege of an operating system in a mobile terminal, the executor can scan message pushing environment based on the root privilege, and display multiple scanning results.

As an embodiment of the present disclosure, in the step S102, the executor can scan the application installation in the current mobile terminal, and judge whether the applications have registered the message pushing events to the operating system by means of reading application configuration files, thereby finding applications which are installed in the mobile terminal and have the message pushing function, outputting the applications as scanning results and displaying the results afterward.

As another embodiment of the present disclosure, in the step S102, the executor can read the messages in a system notification bar of the current mobile terminal, thereby obtaining the pushed messages which have been pushed to the system notification bar of the mobile terminal, outputting the pushed messages as scanning results and displaying the results afterward.

step S103: detecting an operating instruction which is acted on one of the scanning results selected by a user.

step S104: carrying out message pushing management in the mobile terminal according to the detected operating instruction.

By means of displaying multiple scanning results output in the step S102, the user can select the scanning results, which need to be further operated, among the results, and input an corresponding operating instruction. By this token, according to the detected operating instruction input by the user, the executor can further perform the operation on the scanning results selected by the user, thereby implementing the operation of message pushing management in the mobile terminal.

In the present embodiment, since the overall scanning for the message pushing environment of the mobile terminal is based on the root privilege, message pushing of all applications in the mobile terminal can be set according to the scanning results output in the end, which provides message pushing environment settings in the mobile terminal with a unified management platform without entering each application respectively for message pushing settings, thereby simplifying operation steps of message pushing management and improving the operation efficiency of message pushing management.

Associating with the specific message pushing setting scenes, the method for message pushing management according to the embodiments of the present disclosure will be described in detail thereinafter:

first, directing at the situation that the scanning results output in the step S102are the applications which are installed in the mobile terminal and have the message pushing function, embodiments of the present disclosure are described thereinafter:

In the present disclosure, after selecting the scanning results, the user will input an operating instruction which includes intercepting the pushed messages in the step S103； in this case, step S104 is specifically described thereinafter:

enabling or disabling the message pushing function of the applications selected by the user in batches.

In other words, the method according to embodiments may include the following steps: firstly, the user selecting the applications which need message pushing management from the application list output in the step S102, and inputting the operating instruction of enabling the message pushing function or disabling the message pushing function, then enabling or disabling the message pushing function of the applications selected by the user in batches by means of the root privilege after detecting the operating instruction input by the user. It is not necessary for the user to enter the setting centers of the selected applications respectively and to set the message pushing function one by one.

Further, the operating instruction input by the user can also includes presetting system time period, thus the step of enabling or disabling the message pushing function of the applications selected by the user in batches is specifically described thereinafter:

enabling or disabling the message pushing function of the applications selected by the user within the preset system time period.

In other words, the step of enabling or disabling the message pushing function of the applications selected by the user in batches specifically further comprises enabling or disabling the message pushing function of the applications within the preset system time. For example, if not wanting to be disturbed at night rest time by pushed messages, the user can input the operating instruction of disabling the pushing function, and set the system time from 22: 00to 06: 00, so that the message pushing function of the applications selected by the user is disabled at everyday period from 22: 00to 06: 00next morning based on the root privilege, while the message pushing function of the applications is enabled at other time every day, thereby preventing the user from being disturbed by the pushed messages of the applications at night rest time.

In embodiments of the present disclosure, in the step S103, after selecting the scanning results, the user will input an operating instruction which includes setting an upper limit of the quantity of messages to be pushed, and the upper limit of the quantity of messages to be pushed is arranged for limiting the maximum of the messages which are allowed to be pushed by an application in one day. In this case, the step S104 is specifically described thereinafter:

setting the quantity of messages to be pushed by the applications in one day to be no more than the upper limit.

In the present embodiment, the excessive message harassment of applications can be avoided by means of setting an upper limit of the quantity of messages to be pushed. For example, for an application, if the quantity of messages to be pushed in one day is more than ten, one of the messages may be pushed every one or two hours. High pushing frequency easily causes the message harassment, which frequently interrupts normal work, study and leisure life of users. Therefore, by means of setting an upper limit of the quantity of messages to be pushed by the application in one day, the message harassment can be avoided effectively.

As another embodiment of the present disclosure, after selecting the scanning results, the user will input an operating instruction which includes intercepting the pushed messages in the step S103. In this case, the step S104 is specifically described thereinafter:

intercepting pushed messages of the applications selected by the user, so as not to display the pushed messages of the applications in the system notification bar.

In the present embodiment, when detecting the situation that a pushed message is sent from the server side of an application to a mobile terminal, intercept the pushed message at the same time of the application pushing the message, so as not to push the pushed messages to the system notification bar or the main screen of the mobile terminal by the application , and not to cause harassment to the user. If needing to look over the pushed messages which have been intercepted, the user may enter the applications or third-party security software to look over the messages.

Next, directing at the situation that the scanning results output in the step S102 are the pushed messages which have already been pushed to the system notification bar of the mobile terminal, embodiments of the present disclosure are described thereinafter:

as an embodiment of the present disclosure, after selecting the scanning results, the user will input an operating instruction which includes removing the pushed messages in the step S103； in this case, the step S104 is specifically described thereinafter:

removing the pushed messages which are selected by the user and have already been pushed to a system notification bar of the mobile terminal.

In other words, the embodiments include the following steps: firstly, a user selecting the pushed messages which need to be operated from the message pushing list output in the step S102, and inputting the operating instruction of removing the pushed messages, then the operating system notification bar of the mobile terminal being operated by means of the root privilege after detecting the operating instruction input by the user so as to remove the pushed messages selected by the user in batches. It is not necessary to activate the system notification bar of the mobile terminal by means of manual operation and to delete the pushed messages in the system notification bar one by one.

The embodiments may remove the pushed messages in batches, which can reach high operation efficiency under the circumstances that the quantity of the messages which have already been pushed to system notification bar is quite large. At the same time, the pushed messages can also be removed selectively by means of the selecting operation by the user. For example, the messages which have already been pushed to the system notification bar include the to-do item reminder and email reminder. When a new email prompted in the email reminder has been read by the user, the email reminder can be removed by means of the operations above, while the to-do item reminder is kept in the system notification bar, so that the user deal with the to-do items someday.

As another embodiment of the present disclosure, after selecting the scanning results, the user will input an operating instruction which includes displaying the message sources in the step S103. In this case, the step S104 is specifically described thereinafter:

obtaining and displaying message sources of the pushed messages which are selected by the user and have already been pushed to a system notification bar of the mobile terminal.

The embodiments aim at avoiding baleful harassment of the applications. When pushing messages, some applications will not display message sources on purpose, and push the spam to the mobile terminal frequently to harass the user. While in the present embodiment, due to having the root privilege, the executor can trace sources of messages which have already been pushed to the system notification bar, and find the applications which are pushing the messages. Therefore, the user can select the pushed messages whose sources need to be checked from the message pushing list, and input the operating instruction of displaying the message sources, thus the user can find out the applications which are pushing baleful messages, and further uninstall the applications or disable the message pushing function of the applications.

In the present disclosure, if the executive body is third-party security software, the messages pushed to a system notification bar can also been recorded, so that the user can enter the third-party security software later to look over all the pushed historical messages.

Fig. 2shows the structure frame of a device 200 for message pushing management according to embodiments of the present disclosure. The device 200 is programmed to perform the message pushing managing method described in the above embodiments of Fig. 1 in the present disclosure. For facilitating the explanations, only a relevant part of the present embodiment is shown.

Referring to Fig. 2, the device 200 includes a hardware processor 210 and a non-transitory storage medium 220 accessible to the hardware processor 210. The non-transitory storage medium 220 is configured to store units including: an obtaining unit 21, a scanning unit 22, a detecting unit 23, and a managing unit 24.

The obtaining unit 21 is programmed to obtain a super user permission of an operating system in a mobile terminal.

The scanning unit 22 is programmed to scan message push environment of the mobile terminal using the super user permission and then displaying multiple scanning results.

The detecting unit 23 is programmed to detect an operating instruction which is acted on one of the scanning results selected by a user.

The managing unit 24 is programmed to carry out message pushing management in the mobile terminal according to the detected operating instruction.

Alternatively, the scanning unit 22 is programmed to:

scan applications which are installed in the mobile terminal and have message pushing function with using the super user permission.

Alternatively, the operating instruction includes enabling or disabling the message pushing function, and the managing unit 24 is programmed to:

enable or disable the message pushing function of the applications selected by the user in batches.

Alternatively, the operating instruction further includes presetting system time period, and the managing unit 24 is programmed to:

enable or disable the message pushing function of the applications selected by the user within the preset system time period.

Alternatively, the operating instruction further includes setting an upper limit of the quantity of messages to be pushed, and the managing unit 24 is programmed to:

set the quantity of messages to be pushed by the applications in one day to be no more than the upper limit.

Alternatively, the scanning unit 22 is programmed to:

scan the pushed messages which have already been pushed to a system notification bar of the mobile terminal with using the super user permission.

Alternatively, the operating instruction further includes removing the pushed messages, and the managing unit 24 is programmed to:

remove the pushed messages which are selected by the user and have already been pushed to the system notification bar of the mobile terminal.

Alternatively, the operating instruction further includes displaying the message sources, and the managing unit 24 is programmed to:

obtain and display message sources of the pushed messages which are selected by the user and have already been pushed to the system notification bar of the mobile terminal.

Fig. 3 is a block diagram of a partial device related to a mobile terminal such as a mobile phone. For example, the mobile terminal includes a radio frequency (RF) circuit 510, a memory 520, an input unit 530, a display unit 540, a sensor 550, an audio circuit 560, a wireless fidelity (WiFi) module 570, a processor 580, and a power 590, etc. It’s understood for persons skilled in the art that, the structure of a mobile phone illustrated in Fig. 3 is not limited, some components can be added or omitted, or some combinations or arrangement can be included.

Following is a detailed description of the structure of the mobile terminal by combining with Fig. 3.

The RF circuit 510 is configured to receive and sending signals during calling or process of receiving and sending message. Specially, the RF circuit 510will receive downlink information from the base station and send it to the processor 580； or send uplink data to the base station. Generally, the RF circuit 510 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier (LNA) , a diplexer, and the like. In addition, the RF circuit 40 can communicate with network or other devices by wireless communication. Such wireless communication can use any one communication standard or protocol, which includes, but is not limited to, Global System of Mobile communication (GSM) , (General Packet Radio Service, GPRS) , (Code Division Multiple Access, CDMA) , (Wideband Code Division Multiple Access, WCDMA) , (Long Term Evolution, LTE) , email, or (Short Messaging Service, SMS) .

The memory 520 is configured to store software program and module which will be run by the processor 580, so as to perform multiple functional applications of the mobile phone and data processing. The memory 530 mainly includes storing program area and storing data area. For example, the storing program area can store the operating system, at least one application program with required function (such as sound playing function, image playing function, etc. ) . The storing data area can store data established by mobile phone according to actual using demand (such as audio data, phonebook, etc. ) Furthermore, the memory 520 can be high-speed random access memory, or nonvolatile memory, such as disk storage, flash memory device, or other volatile solid-state memory devices.

The input unit 530 is configured to receive the entered number or character information, and the entered key signal related to user setting and function control of the mobile phone 500. For example, the input unit 530 includes a touch panel 531 or other input devices 532. The touch panel 531 is called as touch screen, which can collect user’s touch operations thereon or nearby (for example the operations generated by fingers of user or stylus pen, and the like, touching on the touch panel 531 or touching near the touch panel 531) , and drive the corresponding connection device according to the preset program. Optionally, the touch panel 531 includes two portions including a touch detection device and a touch controller. Specifically, the touch detection device is configured to detect touch position of the user and detecting signals accordingly, and then sending the signals to the touch controller. Subsequently, the touch controller receives touch information from the touch detection device, and converts it to contact coordinates which are to be sent to the processor 580, and then receives command sent by the processor 580 to perform. In addition, the touch panel 531 can be implemented is forms of resistive type, capacitive type, infrared type and surface acoustic wave type. Besides the touch panel 531, the input unit 530 can include, but is not limited to other input devices 532, such as one or more selected from physical keyboard, function keys (such as volume control keys, switch key-press, etc. ) , a trackball, a mouse, and an operating lever, etc.

The display unit 540 is configured to display information entered by the user or information supplied to the user, and menus of the mobile phone. For example, the display unit 540 includes a display panel 541, such as a Liquid Crystal Display (LCD) , or an Organic Light-Emitting Diode (OLED) . Furthermore, the display panel 541 can be covered by the touch panel 531, after touch operations are detected on or near the touch panel 531, they will be sent to the processor 580to determine the type of the touching event. Subsequently, the processor 580 supplies the corresponding visual output to the display panel 541 according to the type of the touching event. As shown in Fig. 3, the touch panel 531 and the display panel 541 are two individual components to implement input and output of the mobile phone, but they can be integrated together to implement the input and output in some embodiments.

Furthermore, the mobile phone 500 includes at least one sensor 550, such as light sensors, motion sensors, or other sensors. Specifically, the light sensors includes ambient light sensors for adjusting brightness of the display panel 541 according to the ambient light, and proximity sensors for turning off the display panel 541 and/or maintaining backlight when the mobile phone is moved to the ear side. Accelerometer sensor as one of the motion sensors can detect the magnitude of accelerations in every direction (Triaxial, generally) , and detect the magnitude and direction of gravity in an immobile status, which is applicable to applications of identifying attitudes of the mobile (such as switching between horizontal and vertical screens, related games, magnetometer attitude calibration, etc. ), vibration recognition related functions (such as pedometer, percussion, etc. ). And the mobile phone 500 also can configure other sensors (such as gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc. ) whose detailed descriptions are omitted here.

The audio circuit 560, the speaker 561 and the microphone 562 supply an audio interface between the user and the mobile phone. Specifically, the audio data is received and converted to electrical signals by audio circuit 560, and then transmitted to the speaker 561, which are converted to sound signal to output. On the other hand, the sound signal collected by the speaker is then converted to electrical signals which will be received and converted to audio data. Subsequently, the audio data are output to the processor 580 to process, and then sent to another mobile phone via the RF circuit 510, or sent to the memory 520 to process further.

WiFi pertains to short-range wireless transmission technology providing a wireless broadband Internet, by which the mobile phone can help the user to receive and send email, browse web, and access streaming media, etc. Although the WiFi module 570 is illustrated in Fig. 3, it should be understood that, WiFi module 570 is not a necessary for the mobile phone, which can be omitted according the actual demand without changing the essence of the present disclosure.

The processor 580 is a control center of the mobile phone, which connects with every part of the mobile phone by various interfaces or circuits, and performs various functions and processes data by running or performing software program/module stored in the memory 520 or calling data stored in the memory 520, so as to monitor the mobile phone. Optionally, the processor 580 may include one or more processing units. Preferably, the processor 580 can integrate with application processors and modem processors, for example, the application processors include processing operating system, user interface and applications, etc.； the modern processors are used for performing wireless communication. It can be understood that, it’s an option to integrate the modern processors to the processor 580.

Furthermore, the mobile phone 500 may include a power supply (such as battery) supplying power for each component, preferably, the power supply can connect with the processor 580 by power management system, so as to manage charging, discharging and power consuming.

In addition, the mobile phone 500 may include a camera, and a Bluetooth module, etc., which are not illustrated.

Functional units in each embodiment of this disclosure may be all integrated in a processing module, or can be a separated physical one, or two or more of the functional units can be integrated in a module. The above integrated module can be realized as hardware, also can be realized as a software functional module. When being realized as a software functional module and sold or used as an independent product, the integrated module also can be stored in a computer- readable storage medium. The storage medium mentioned above may be RAM, disc, or CD, etc. Each device or system mentioned above is capable of executing the methods in the method embodiments.

The foregoing descriptions are only preferred embodiments of the present disclosure and are not intended to limit the present disclosure. Any modification, equivalent replacement and improvement made under the spirit and principle of the present disclosure should be included in the protection scope thereof. The present disclosure is implemented based on the super user permissions of the operating systems in the mobile terminals, and provides message pushing settings of the applications with a unified management platform, so as to directly manage message pushing environment of the mobile terminals by means of the management platform, which simplifies the operation steps of message pushing management and improves operation efficiency of message pushing management.

While the disclosure has been described in connection with what are presently considered to be the preferred embodiments, the present disclosure is not to be limited by the disclosed embodiments, but on the contrary, is intended to cover various modifications, equivalent arrangements and improvement included within the spirit and principle of the disclosure, which pertains to the protection scope of the present disclosure.

Claims

A method for message pushing management, comprising:

obtaining, by a mobile terminal, a super user permission of an operating system in the mobile terminal；

scanning, by the mobile terminal, message pushing environment of the mobile terminal using the super user permission and then displaying multiple scanning results；

detecting, by the mobile terminal, an operating instruction to one of the scanning results selected by a user； and

carrying out, by the mobile terminal, message pushing management in the mobile terminal according to the operating instruction.
The method according to claim 1, wherein scanning message pushing environment of the mobile terminal using the super user permission comprises:

scanning applications which are installed in the mobile terminal and have message pushing function, using the super user permission.
The method according to claim 2, wherein the operating instruction comprises enabling or disabling the message pushing function； and wherein carrying out message pushing management in the mobile terminal according to the operating instruction comprises:

enabling or disabling the message pushing function of applications selected by the user in batches.
The method according to claim 3, wherein the operating instruction further comprises presetting system time period； and wherein enabling or disabling the message pushing function of the applications selected by the user in batches specifically comprises:

enabling or disabling the message pushing function of the applications selected by the user within a preset system time period.
The method according to claim 2, wherein the operating instruction comprises setting an upper limit of a quantity of messages to be pushed； and wherein carrying out message pushing management in the mobile terminal according to the operating instruction comprises:

setting the quantity of messages to be pushed by the applications in one day to be no more than the upper limit.
The method according to claim 1, wherein scanning message pushing environment of the mobile terminal using the super user permission comprises:

scanning the pushed messages which have already been pushed to a system notification bar of the mobile terminal with using the super user permission.
The method according to claim 6, wherein the operating instruction comprises removing pushed messages； and wherein carrying out message pushing management in the mobile terminal according to the operating instruction comprises:

removing the pushed messages which are selected by the user and have already been pushed to the system notification bar of the mobile terminal.
The method according to claim 6, wherein the operating instruction comprises displaying message sources； and wherein carrying out message pushing management in the mobile terminal according to the operating instruction comprises:

obtaining and displaying message sources of the pushed messages which are selected by the user and have already been pushed to the system notification bar of the mobile terminal.
A device for message pushing management, comprising a hardware processor and a non-transitory storage medium accessible to the hardware processor, the non-transitory storage medium configured to store units comprising:

an obtaining unit, arranged for obtaining a super user permission of an operating system in a mobile terminal；

a scanning unit, arranged for scanning message pushing environment of the mobile terminal with using the super user permission and then displaying multiple scanning results；

a detecting unit, arranged for detecting an operating instruction which is acted on one of the scanning results selected by a user； and

a managing unit, arranged for carrying out message pushing management in the mobile terminal according to the detected operating instruction.
The device according to claim 9, wherein the scanning unit is programmed to:

scan applications which are installed in the mobile terminal and have message pushing function with using the super user permission.
The device according to claim 10, wherein the operating instruction comprises enabling or disabling the message pushing function； and the managing unit is programmed to:

enable or disable the message pushing function of applications selected by the user in batches.
The device according to claim 11, wherein the operating instruction further comprises presetting system time period； and the managing unit is programmed to:

enable or disable the message pushing function of applications selected by the user within the preset system time period.
The device according to claim 10, wherein the operating instruction further comprises setting an upper limit of a quantity of messages to be pushed； and the managing unit is programmed to:

set the quantity of messages to be pushed by applications in one day to be no more than the upper limit.
The device according to claim 9, wherein the scanning unit is programmed to:

scan the pushed messages which have already been pushed to a system notification bar of the mobile terminal with using the super user permission.
The device according to claim 14, wherein the operating instruction comprises removing the pushed messages； and the managing unit is programmed to:

remove the pushed messages which are selected by the user and have already been pushed to the system notification bar of the mobile terminal.
The device according to claim 14, wherein the operating instruction comprises displaying message sources； and the managing unit is programmed to:

obtain and display the message sources of the pushed messages which are selected by the user and have already been pushed to the system notification bar of the mobile terminal.