WO2018010507A1

WO2018010507A1 - Awakening monitoring method of terminal system, storage medium, terminal, and electronic device

Info

Publication number: WO2018010507A1
Application number: PCT/CN2017/087625
Authority: WO
Inventors: 熊胤琪
Original assignee: 广东欧珀移动通信有限公司
Priority date: 2016-07-11
Filing date: 2017-06-08
Publication date: 2018-01-18
Also published as: CN106227321A; CN106227321B

Abstract

Disclosed are an awakening monitoring method of a terminal system, a storage medium, a terminal, and an electronic device. The awakening monitoring method of a terminal system comprises: detecting whether the terminal system is awakened by an application by means of a data packet; if yes, counting the awakening frequency of the terminal system awakened by the application by means of data packets; determining whether the awakening frequency is greater than a preset frequency threshold; and if yes, reporting the application to a background management system.

Description

Wake-up monitoring method, storage medium, terminal and electronic device of terminal system

Technical field

The embodiments of the present invention relate to the field of communications technologies, and in particular, to a wakeup monitoring method, a storage medium, a terminal, and an electronic device of a terminal system.

Background technique

With the development of intelligent terminals, more and more applications can be installed on the terminal. At present, after the smart terminal sleeps, the application can wake up the terminal system by: wake-up by the data packet, that is, the application pushes the data packet through the application server to wake up the terminal system.

technical problem

The embodiment of the invention provides a wake-up monitoring method for a terminal system, a storage medium, a terminal, and an electronic device, which can monitor and report an abnormal application program that frequently wakes up the terminal system through the data packet, thereby reducing power consumption of the terminal.

Technical solution

The wake-up monitoring method of the terminal system provided by the embodiment of the present invention includes:

Detecting whether the terminal system is awakened by the application through the data packet;

If yes, counting the wake-up frequency of the terminal system being awake by the application through the data packet;

Determining whether the wake-up frequency is greater than a preset frequency threshold;

If yes, the application is reported to the background management system.

The embodiment of the present invention provides a storage medium, including a computer program, which is implemented by the processor, and implements the steps in the wake-up monitoring method of the terminal system provided by the embodiment of the present invention.

The terminal provided by the embodiment of the present invention includes:

a detecting module, configured to detect whether the terminal system is awakened by the application by the data packet;

a statistic module, configured to: when detecting that the terminal system is awake by the application by the data packet, the waking frequency of the terminal system being awake by the application program through the data packet;

a determining module, configured to determine whether the wake-up frequency is greater than a preset frequency threshold;

The reporting module is configured to report the application to the background management system when the wake-up frequency is greater than the preset frequency threshold.

An embodiment of the present invention provides an electronic device including a memory, a processor, and a computer program stored in the memory and operable in the processor. When the processor executes the computer program, the following steps are implemented. :

Detecting whether the electronic device system is awakened by the application through the data packet;

If yes, counting the wake-up frequency of the electronic device system being awake by the application through the data packet;

If yes, the application is reported to the background management system.

Beneficial effect

DRAWINGS

1 is a schematic flowchart of a wakeup monitoring method of a terminal system according to an embodiment of the present invention.

FIG. 2 is another schematic flowchart of a wakeup monitoring method of a terminal system according to an embodiment of the present invention.

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

FIG. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.

FIG. 5 is another schematic structural diagram of an electronic device according to an embodiment of the present invention.

BEST MODE FOR CARRYING OUT THE INVENTION

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, but not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without any inventive effort are within the scope of the present invention.

Currently, many applications maintain the transmission control protocol between the server and the terminal (Transmission Control). Protocol, TCP) Long connection, will continuously send data packets to the terminal to wake up the terminal system. This will cause the terminal to experience power consumption abnormality during sleep. If these applications cannot be detected and processed in time, the terminal life will be shortened and the endurance will be deteriorated, which will affect the normal use of the user.

The embodiment of the invention provides a wake-up monitoring method for a terminal system, including:

If yes, the application is reported to the background management system.

In an embodiment, the step of detecting whether the terminal system is awakened by the application by the data packet may include:

Detecting, by the listening interface, whether the value of the driving node used to listen to the wakeup of the terminal system by the application packet changes;

If a change occurs, it is determined that the terminal system is woken up by the application through the packet.

In an embodiment, after determining that the terminal system is awake by the application by the data packet, the method may further include:

Obtaining identification information of the application that wakes up the terminal system.

Then, the step of reporting the application to the background management system may include: reporting the identification information of the application to the background management system.

In an embodiment, the step of acquiring the identifier information of the application that wakes up the terminal system may include:

Reading, by using the traffic statistics interface, identifier information of an application whose traffic has increased within a first preset duration before detecting that the terminal system is awake by the application packet;

The identification information of the application holding the wakelock wakelock is removed from the identification information of all the applications read, and the identification information of the remaining applications is the identification information of the application waking up the terminal system.

Obtaining a user identifier of the application that wakes up the terminal system.

Then, the step of reporting the identification information of the application to the background management system may include: reporting the user identifier of the application to the background management system.

In an embodiment, the step of counting the wake-up frequency of the terminal system by the application program to wake up by the data packet may include:

After detecting that the terminal system is awake by the application packet through the data packet, the accumulated terminal duration and the wakeup cumulative number of the terminal system being awake by the application by the data packet are counted;

The wake-up frequency is calculated according to the wake-up accumulation duration and the wake-up accumulation count.

In another embodiment, the step of counting the wake-up frequency of the terminal system by the application program to wake up by the data packet may include:

After detecting that the terminal system is awake by the application by the data packet, the statistic terminal system is accumulated by the application through the wakeup of the data packet;

The wake-up frequency is calculated according to the second preset duration and the wake-up cumulative number.

The wake-up monitoring method of the terminal system provided by the embodiment of the present invention can be applied to a terminal, and the terminal includes, but is not limited to, an electronic device such as a mobile phone or a tablet computer.

As shown in FIG. 1, the wakeup monitoring method of the terminal system provided in this embodiment includes the following steps:

Step 101: Detect whether the terminal system is woken up by the application by the data packet. If yes, execute step 102, otherwise, the processing ends.

Since the wake-up mode of the application wake-up terminal system is two, the wake-up of the data packet and the wake-up by the alarm alarm are used. In this embodiment, the Uevent can be added to the kernel of the terminal for the monitoring application to wake up the wake-up mode of the terminal system through the data packet. The driver node wakeup_reasons, after the terminal enters the sleep state, uses the drive node wakeup_reasons to record the information that the terminal system is awakened by the application through the data packet, and the recorded information may be a numerical value flag, for example, if the terminal system is not monitored by the application program. When the data packet wakes up, the value is marked as 0. When the terminal system is awake by the application through the data packet, the value flag is updated to a value other than 0, for example, 1 or the like, which is not specifically limited herein. Therefore, in this step, it is possible to determine whether the terminal system is awake by the application through the data packet by detecting whether the value of the drive node wakeup_reasons changes.

Step 102: Count a wake-up frequency of the terminal system being awakened by the application by a data packet.

The wake-up frequency can be determined by the wake-up duration and the number of wake-ups.

Step 103: Determine whether the wake-up frequency is greater than a preset frequency threshold. If it is greater, perform step 104, otherwise end the process.

The preset frequency threshold can be set according to actual requirements. If the wake-up frequency is greater than the preset frequency threshold, the application frequently wakes up the terminal system through the data packet, and the application is an abnormal application.

Step 104: Report the application to the background management system.

In an embodiment, the background management system may be a daemon, a background operation system, etc., after the application is reported to the background management system, the background management system may uninstall the application, or set a packet wakeup for the application. Restrictions, etc., to save power consumption of the terminal and ensure the normal use of the user.

In this embodiment, it is possible to detect whether the terminal system is awake by the application program through the data packet. Once it is detected that the terminal system is awakened by the application program through the data packet, the wake-up frequency of the terminal system being awake by the application program through the data packet is counted. If the wakeup frequency is greater than the preset frequency threshold, the application is reported to the background management system. The background management system can timely discover the abnormal application of the terminal system through the data packet and process it according to the report of the terminal, thereby reducing the power consumption of the terminal and ensuring the normal use of the user.

As shown in FIG. 2, the wakeup monitoring method of the terminal system provided in this embodiment may include the following steps:

Step 201: Detect whether the terminal system is woken up by the application by the data packet. If yes, execute step 202, otherwise, the processing ends.

Step 202: Read, by using a traffic statistics interface, identifier information of an application whose traffic is increased within a first preset duration before detecting that the terminal system is awake by the application packet.

In an embodiment, the identification information of the application may be a User IDentity (UID) of the application. UIDs can be used to uniquely identify an application.

It is detected in step 201 that the terminal system is awake by the application through the packet, but does not know which application is actually awake. Therefore, in step 202, the specific application for waking up the terminal system through the packet is determined.

If the application wakes up the terminal system through the data packet, the traffic of the corresponding application increases due to the transmission of the data packet. Therefore, in this embodiment, the traffic statistics interface can be read to detect that the terminal system is passed by the application. In the first preset duration before the packet wakes up, the traffic has an identification information of the application, and the first preset duration may be 1 second, 2 seconds, etc., and may be set according to actual requirements.

Step 203: Remove the identifier information of the application that holds the wakelock wakelock operation, and the identifier information of the remaining application is the identifier information of the application that wakes up the terminal system.

Generally speaking, after the terminal system is woken up by the application, if the application holds the wakelock wakelock, the application is allowed to continue to work. In this case, the wakeup is usually considered as a normal wakeup. Therefore, in this embodiment, it is necessary to remove the identification information of the application holding the wakelock wakelock operation in the identification information of the application whose all traffic has been read, and the identification information of the remaining application is the record to be recorded by the invention. Awakening the identification information of the application of the terminal system.

Step 204: Count the wake-up frequency of the terminal system being awake by the application by the data packet.

In an implementation manner, the wake-up frequency of the wake-up by the application program by the application program may be counted within a second preset duration after the terminal system is detected by the application program to wake up by the data packet, and the second preset duration is It can be set according to actual statistical requirements, for example, set to four hours, eight hours, etc., and is not specifically limited herein. In an embodiment, the wakeup cumulative duration and the wakeup cumulative number that the application system wakes up by the application packet in the second preset duration may be counted, and the wakeup frequency is calculated according to the wakeup cumulative duration and the wakeup cumulative number.

In one embodiment, the method of counting the cumulative duration of wakeup can be as follows:

A timer can be set for each application, and the timer of each application is cleared before starting the statistics. In the process of statistics, after obtaining the identification information of the application that wakes up the terminal system through the data packet, The timer of the application corresponding to the identifier information is started to record the wake-up duration. After the terminal system wakes up once by the application, the terminal system accumulates a wake-up duration, and after reaching the second preset duration, reads the application. The timer value corresponding to the program, that is, the cumulative duration of wakeup corresponding to the application.

In one embodiment, the method of counting the cumulative number of wakeups can be as follows:

A counter can be set for each application, and the counter of each application is cleared before starting the statistics. In the process of statistics, after obtaining the identification information of the application that wakes up the terminal system through the data packet, The counter of the application corresponding to the identifier information is incremented by one. After the terminal system wakes up once by the application packet, the terminal system adds one to the counter, and after reaching the second preset duration, reads the corresponding program. The counter value, that is, the cumulative number of wakeups corresponding to the application.

Of course, in another implementation manner, the wakeup accumulation duration of the application may not be counted, and the wakeup cumulative number in the second preset duration may be directly counted, and the wakeup frequency may be calculated according to the second preset duration and the wakeup cumulative number, where No specific restrictions.

Then, in an embodiment, the step of counting the wake-up frequency of the terminal system by the application program to wake up by the data packet in step 204 may also include:

Step 205: Determine whether the wake-up frequency is greater than a preset frequency threshold. If it is greater, perform step 206, otherwise end the process.

The preset frequency threshold may be set according to actual data such as the second preset duration. If the wakeup frequency is greater than the preset frequency threshold, the application frequently wakes up the terminal system through the data packet, and the application is an abnormal application.

Step 206: Report the identification information of the application to the background management system.

The embodiment of the present invention further provides a terminal. As shown in FIG. 3, the terminal in this embodiment may include:

The detecting module 301 is configured to detect whether the terminal system is woken up by the application by the data packet.

The statistic module 302 is configured to count, when the terminal system is awake by the application by the data packet, the wake-up frequency of the terminal system being awake by the application program through the data packet.

The determining module 303 is configured to determine whether the wake-up frequency is greater than a preset frequency threshold.

The reporting module 304 is configured to report the application to the background management system when the wake-up frequency is greater than the preset frequency threshold.

In an embodiment, the detecting module 301 can include:

The detecting submodule is configured to detect, by using the listening interface, whether the value of the driving node used to listen to the wakeup of the terminal system by the application packet changes.

And a determining submodule, configured to determine, when the detecting submodule detects that the value of the driving node changes, to determine that the terminal system is woken up by the application by the data packet.

In an embodiment, the terminal may further include:

And an obtaining module, configured to acquire identification information of the application that wakes up the terminal system.

The reporting module 304 is configured to report the identification information of the application to the background management system.

In an embodiment, the obtaining module may be configured to: obtain a user identifier of the application that wakes up the terminal system.

Then, the reporting module 304 can be configured to: report the user identifier of the application to the background management system.

In an embodiment, the obtaining module may include:

The reading sub-module is configured to read, by using the traffic statistics interface, identifier information of an application whose traffic has increased within a first preset duration before detecting that the terminal system is woken up by the application packet.

And removing the submodule, configured to remove, in the identification information of all the applications that are read, the identification information of the application that holds the wakelock wakelock work, and the identifier information of the remaining applications is the application that wakes up the terminal system Identification information.

In an embodiment, the statistics module 302 can include:

The statistic sub-module is configured to count the accumulated wake-up duration and the wake-up cumulative number of the terminal system by the application wake-up by the application, after detecting that the terminal system is awake by the application by the data packet.

And a calculating submodule, configured to calculate the wakeup frequency according to the wakeup cumulative duration and the wakeup cumulative number.

In another implementation, the statistics module 302 can also be used to:

It should be noted that the steps in the foregoing method and the corresponding beneficial effects in the embodiments may be referred to the corresponding descriptions in the foregoing method embodiments, and details are not described herein again.

In this embodiment, the detecting module may detect whether the terminal system is awake by the application program through the data packet, and once detecting that the terminal system is awake by the application program through the data packet, the statistic module counts the wake-up frequency of the terminal system being awake by the application program through the data packet. . If the determining module determines that the wake-up frequency is greater than the preset frequency threshold, the reporting module reports the application to the background management system. The background management system can timely discover the abnormal application of the terminal system through the data packet and process it according to the report of the terminal, thereby reducing the power consumption of the terminal and ensuring the normal use of the user.

The embodiment of the present invention provides a computer readable storage medium, including a computer program. When the computer program is loaded and executed by a processor, the steps in the wakeup monitoring method of the terminal system provided by the embodiment of the present invention may be implemented.

An embodiment of the present invention further provides an electronic device, including a memory, a processor, and a computer program stored in the memory and operable in the processor, where the processor can implement the computer program The steps in the wakeup monitoring method of the terminal system provided by the embodiment of the invention.

For example, the electronic device can be a mobile terminal device such as a smartphone or tablet. Please refer to FIG. 4. FIG. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present invention. The electronic device 400 can include components such as a memory 401, a processor 402, and a modem module 403. It will be understood by those skilled in the art that the electronic device structure illustrated in FIG. 4 does not constitute a limitation to the electronic device, and may include more or less components than those illustrated, or a combination of certain components, or different component arrangements.

Memory 401 can be used to store applications and data. The application stored in the memory 401 contains executable code. Applications can form various functional modules. The processor 402 executes various functional applications and data processing by running an application stored in the memory 401.

The processor 402 is a control center of the electronic device, and connects various parts of the entire electronic device using various interfaces and lines, executes the electronic device by running or executing an application stored in the memory 401, and calling data stored in the memory 401. The various functions and processing of data to provide overall monitoring of the electronic device.

The modem module 403 is for converting binary digital information into an analog signal that can be transmitted through a common public information system, or converting the received analog signal into a digital signal. In one embodiment, the above functions can be implemented by a dedicated modem.

In this embodiment, the processor 402 in the electronic device loads the executable code corresponding to the process of one or more applications into the memory 401 according to the following instructions, and is executed by the processor 402 to be stored in the memory. The application in 401, thus implementing the steps:

If yes, the application is reported to the background management system.

In an embodiment, when the processor 402 performs the step of detecting whether the electronic device system is awake by the application through the data packet, the following steps may be performed:

Detecting, by the listening interface, whether the value of the driving node for monitoring the electronic device system being awake by the application by the data packet changes;

If there is a change, it is determined that the electronic device system is woken up by the application through the data packet.

In an embodiment, after performing the step of determining that the electronic device system is awake by the application by the data packet, the processor 402 may further perform the step of: acquiring identification information of the application that wakes up the electronic device system. .

Then, when performing the step of reporting the application to the background management system, the processor 402 may perform the following steps: reporting the identification information of the application to the background management system.

In an embodiment, when performing the step of acquiring the identification information of the application that wakes up the electronic device system, the processor 402 may perform the following steps:

Reading, by using the traffic statistics interface, identification information of an application whose traffic has increased within a first preset duration before detecting that the electronic device system is woken up by the application packet;

The identification information of the application holding the wake lock wakelock is removed from the identification information of all the applications read, and the identification information of the remaining applications is the identification information of the application waking up the electronic device system.

In an embodiment, when performing the step of acquiring the identification information of the application that wakes up the electronic device system, the processor 402 may perform the following steps: acquiring the application that wakes up the electronic device system User identifier

Then, when performing the step of reporting the identification information of the application to the background management system, the processor 402 may perform the following steps: reporting the user identifier of the application to the background management system.

In an embodiment, when the processor 402 performs the step of counting the wake-up frequency of the electronic device system being waking up by the application by the data packet, the following steps may be performed:

After detecting that the electronic device system is awake by the application program through the data packet, the accumulated accumulated duration of the wake-up of the electronic device system by the application packet wake-up and the cumulative number of wake-up times are detected;

After detecting that the electronic device system is awake by the application through the data packet, the cumulative number of wakeups that the electronic device system is awake by the application through the data packet is counted;

Referring to FIG. 5, FIG. 5 is another schematic structural diagram of an electronic device according to an embodiment of the present invention. In an embodiment, the electronic device 400 may further include a radio frequency (RF, Radio) Frequency circuit 404, input unit 405, and output unit 406.

The radio frequency circuit 404 can be used for transmitting and receiving information, or receiving and transmitting signals during a call. Specifically, after receiving the downlink information of the base station, the downlink information is processed by one or more processors 402. In addition, the data related to the uplink is sent to the base station. .

The input unit 405 can be configured to receive input digits, character information, or user characteristic information (such as fingerprints), and to generate keyboard, mouse, joystick, optical, or trackball signal inputs related to user settings and function controls. In an embodiment, the input unit 405 can include a touch-sensitive surface as well as other input devices. Touch-sensitive surfaces, also known as touch screens or trackpads.

The output unit 406 can be used to display information entered by the user or information provided to the user as well as various graphical user interfaces of the mobile terminal, which can be composed of graphics, text, icons, video, and any combination thereof. For example, output unit 406 can be a display panel.

Although not shown in FIG. 5, the electronic device may further include a camera, a Bluetooth module, a wireless fidelity module, and the like, and details are not described herein again.

In the several embodiments provided by the present application, it should be understood that the division of the module is only a logical function division, and the actual implementation may have another division manner, for example, multiple modules or components may be combined or may be Integrate into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form. The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, each functional module in each embodiment of the present invention may be integrated into one processing module, or each module may exist physically separately, or two or more modules may be integrated into one module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. The integrated modules, if implemented in the form of software functional modules and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, or all or part of the technical solution, may be embodied in the form of a software product stored in a storage medium. A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention. The foregoing storage medium includes: a U disk, a mobile hard disk, a read only memory (ROM, Read-Only) Memory, random access memory (RAM), disk or optical disk, and other media that can store program code.

The above embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to be limiting; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art will understand that The technical solutions described in the embodiments are modified, or the equivalents of the technical features are replaced by the equivalents of the technical solutions of the embodiments of the present invention.

Claims

A wake-up monitoring method for an end system, which includes:

Detecting whether the terminal system is awakened by the application through the data packet;

If yes, counting the wake-up frequency of the terminal system being awake by the application through the data packet;

Determining whether the wake-up frequency is greater than a preset frequency threshold;

If yes, the application is reported to the background management system.
The method of claim 1, wherein the detecting whether the terminal system is awakened by the application by the data packet comprises:

Detecting, by the listening interface, whether the value of the driving node used to listen to the wakeup of the terminal system by the application packet changes;

If a change occurs, it is determined that the terminal system is woken up by the application through the packet.
The method of claim 2, wherein after determining that the terminal system is awake by the application by the data packet, the method further comprises:

Obtaining identification information of the application that wakes up the terminal system;

The reporting the application to the background management system includes:

The identification information of the application is reported to the background management system.
The method according to claim 3, wherein the obtaining the identification information of the application waking up the terminal system comprises:

Reading, by using the traffic statistics interface, identifier information of an application whose traffic has increased within a first preset duration before detecting that the terminal system is awake by the application packet;

The identification information of the application holding the wakelock wakelock is removed from the identification information of all the applications read, and the identification information of the remaining applications is the identification information of the application waking up the terminal system.
The method of claim 3, wherein the obtaining the identification information of the application that wakes up the terminal system comprises:

Obtaining a user identifier of the application waking up the terminal system;

The reporting the identification information of the application to the background management system includes: reporting the user identifier of the application to the background management system.
The method according to claim 1, wherein said waking up frequency of said terminal system being awakened by said application by said data packet comprises:

After detecting that the terminal system is awake by the application packet through the data packet, the accumulated terminal duration and the wakeup cumulative number of the terminal system being awake by the application by the data packet are counted;

The wake-up frequency is calculated according to the wake-up accumulation duration and the wake-up accumulation count.
The method of claim 1, wherein the counting the wake-up frequency of the terminal system by the application to wake up by the data packet comprises:

After detecting that the terminal system is awake by the application by the data packet, the statistic terminal system is accumulated by the application through the wakeup of the data packet;

The wake-up frequency is calculated according to the second preset duration and the wake-up cumulative number.
A storage medium comprising a computer program, wherein the computer program is loaded and executed by a processor, implementing the steps in the wake-up monitoring method of the terminal system according to any one of claims 1 to 7.
A terminal, including:

a detecting module, configured to detect whether the terminal system is awakened by the application by the data packet;

a statistic module, configured to: when detecting that the terminal system is awake by the application by the data packet, the waking frequency of the terminal system being awake by the application program through the data packet;

a determining module, configured to determine whether the wake-up frequency is greater than a preset frequency threshold;

The reporting module is configured to report the application to the background management system when the wake-up frequency is greater than the preset frequency threshold.
The terminal of claim 9, wherein the detecting module comprises:

a detecting submodule, configured to detect, by using the listening interface, whether a value of a driving node used to listen to the wakeup of the terminal system by the application packet is changed;

And a determining submodule, configured to determine, when the detecting submodule detects that the value of the driving node changes, to determine that the terminal system is woken up by the application by the data packet.
The terminal of claim 10, wherein the terminal further comprises:

An obtaining module, configured to acquire identifier information of the application that wakes up the terminal system;

The reporting module is configured to report the identification information of the application to the background management system.
The terminal according to claim 11, wherein the obtaining module comprises:

a reading submodule, configured to read, by using a traffic statistics interface, identifier information of an application whose traffic has increased within a first preset duration before detecting that the terminal system is awake by the application packet;

And removing the submodule, configured to remove, in the identification information of all the applications that are read, the identification information of the application that holds the wakelock wakelock work, and the identifier information of the remaining applications is the application that wakes up the terminal system Identification information.
The terminal according to claim 9, wherein the statistics module comprises:

a statistic sub-module, configured to: in a second preset duration after detecting that the terminal system is awake by the application by the data packet, the cumulative duration of wake-up and wake-up accumulation times of the terminal system being awake by the application by the data packet;

The calculating submodule is configured to calculate a wakeup frequency according to the wakeup cumulative duration and the wakeup cumulative number of times.
An electronic device comprising a memory, a processor, and a computer program stored in the memory and operable in the processor, wherein when the processor executes the computer program, the following steps are implemented:

Detecting whether the electronic device system is awakened by the application through the data packet;

If yes, counting the wake-up frequency of the electronic device system being awake by the application through the data packet;

Determining whether the wake-up frequency is greater than a preset frequency threshold;

If yes, the application is reported to the background management system.
The electronic device of claim 14, wherein the processor is configured to perform the following steps:

Detecting, by the listening interface, whether the value of the driving node for monitoring the electronic device system being awake by the application by the data packet changes;

If there is a change, it is determined that the electronic device system is woken up by the application through the data packet.
The electronic device of claim 15 wherein said processor is operative to perform the steps of:

Obtaining identification information of the application that wakes up the electronic device system;

The identification information of the application is reported to the background management system.
The electronic device of claim 16 wherein said processor is operative to perform the steps of:

Reading, by using the traffic statistics interface, identification information of an application whose traffic has increased within a first preset duration before detecting that the electronic device system is woken up by the application packet;

The identification information of the application holding the wake lock wakelock is removed from the identification information of all the applications read, and the identification information of the remaining applications is the identification information of the application waking up the electronic device system.
The electronic device of claim 16 wherein said processor is operative to perform the steps of:

Obtaining a user identifier of the application waking up the electronic device system;

The user identifier of the application is reported to the background management system.
The electronic device of claim 14, wherein the processor is configured to perform the following steps:

After detecting that the electronic device system is awake by the application program through the data packet, the accumulated accumulated duration of the wake-up of the electronic device system by the application packet wake-up and the cumulative number of wake-up times are detected;

The wake-up frequency is calculated according to the wake-up accumulation duration and the wake-up accumulation count.
The electronic device of claim 14, wherein the processor is configured to perform the following steps:

After detecting that the electronic device system is awake by the application through the data packet, the cumulative number of wakeups that the electronic device system is awake by the application through the data packet is counted;

The wake-up frequency is calculated according to the second preset duration and the wake-up cumulative number.