WO2016054957A1 - 应用程序异常的检测方法、装置和移动终端 - Google Patents

应用程序异常的检测方法、装置和移动终端 Download PDF

Info

Publication number
WO2016054957A1
WO2016054957A1 PCT/CN2015/088885 CN2015088885W WO2016054957A1 WO 2016054957 A1 WO2016054957 A1 WO 2016054957A1 CN 2015088885 W CN2015088885 W CN 2015088885W WO 2016054957 A1 WO2016054957 A1 WO 2016054957A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
detecting
mobile terminal
abnormality
process information
Prior art date
Application number
PCT/CN2015/088885
Other languages
English (en)
French (fr)
Inventor
丁上伦
张康宗
肖超
张亚雄
Original Assignee
北京金山安全软件有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 北京金山安全软件有限公司 filed Critical 北京金山安全软件有限公司
Priority to US15/327,686 priority Critical patent/US10394655B2/en
Publication of WO2016054957A1 publication Critical patent/WO2016054957A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1415—Saving, restoring, recovering or retrying at system level
    • G06F11/1438—Restarting or rejuvenating
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
    • G06F11/0736—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in functional embedded systems, i.e. in a data processing system designed as a combination of hardware and software dedicated to performing a certain function
    • G06F11/0742—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in functional embedded systems, i.e. in a data processing system designed as a combination of hardware and software dedicated to performing a certain function in a data processing system embedded in a mobile device, e.g. mobile phones, handheld devices
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0751—Error or fault detection not based on redundancy
    • G06F11/0754—Error or fault detection not based on redundancy by exceeding limits
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3604—Software analysis for verifying properties of programs
    • G06F11/3612—Software analysis for verifying properties of programs by runtime analysis
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Definitions

  • the present invention relates to the field of mobile terminal technologies, and in particular, to a method, an apparatus, and a mobile terminal for detecting an abnormality of an application.
  • the mobile terminal can detect a newly started process in the mobile terminal by periodically enumerating, thereby detecting an application that is frequently restarted in the mobile terminal.
  • the process initiated by the mobile terminal can be periodically enumerated through the Android process APIgetRunningAppProcesses(), and the process of frequently restarting is determined according to the enumeration result.
  • the speed is slow, which increases the burden on the mobile terminal system
  • Each enumeration requires a certain amount of power, and performing periodic enumeration is a method for greatly consuming the power of the mobile terminal;
  • the present invention aims to solve at least one of the above technical problems.
  • a first object of the present invention is to provide a method for detecting an application abnormality.
  • the method has wide application range for detecting the process, and reduces the energy consumption and resource occupation while improving the detection efficiency of the application abnormality.
  • a second object of the present invention is to provide an apparatus for detecting an abnormality of an application.
  • a third object of the present invention is to provide a mobile terminal.
  • a fourth object of the present invention is to provide a storage medium.
  • a method for detecting an application abnormality includes the steps of: detecting a system event of the mobile terminal; and further reading the process information when the system event is a triggering system event, and Determining, according to the process information, whether there is a restarting process; recording the number of restarts of the restarted process in a preset time; and when the restarting number is greater than a preset threshold, determining that the application corresponding to the process is abnormal.
  • the method for detecting an abnormality of an application in the embodiment of the present invention detects a system event of the mobile terminal, and reads the process information when the trigger system event is detected, and records the restart process within a preset time when the restart process exists.
  • the number of restarts, and the application corresponding to the process whose restart number is greater than the preset threshold is an abnormal application, and the process information is read only when the trigger system event is detected, and is affected by the application environment, attributes, and load of the mobile terminal. Therefore, while improving the detection efficiency of application anomalies, energy consumption and resource consumption are reduced.
  • the native native process can be supported and the scope of detection is broader.
  • an apparatus for detecting an abnormality of an embodiment of the second aspect of the present invention includes: a detecting module, configured to detect a system event of the mobile terminal; and a reading module, configured to: when the system event is a triggering system event Further, the process information is further read; the first determining module is configured to determine, according to the process information, whether there is a restarting process; the recording module is configured to record the number of restarts of the restarted process in a preset time; The determining module is configured to determine that the application corresponding to the process is abnormal when the number of restarts is greater than a preset threshold.
  • the detecting device for detecting an abnormality of the embodiment of the present invention detects the system event of the mobile terminal, and reads the process information when the triggering system event is detected, and records the restarting process within a preset time when the restarting process exists.
  • the number of restarts, and the application corresponding to the process whose restart number is greater than the preset threshold is an abnormal application, and the process information is read only when the trigger system event is detected, and is affected by the application environment, attributes, and load of the mobile terminal. Therefore, while improving the detection efficiency of application anomalies, energy consumption and resource consumption are reduced.
  • the native native process can be supported and the scope of detection is broader.
  • a mobile terminal includes: a housing, a processor, a memory, a circuit board, and a power supply circuit, wherein the circuit board is disposed inside a space enclosed by the housing, The processor and the memory are disposed on the circuit board; the power supply circuit is configured to supply power to each circuit or device of the mobile terminal; the memory is configured to store executable program code; the processor Running a program corresponding to the executable program code by reading executable program code stored in the memory, for: detecting a system event of the mobile terminal; when the system event is a trigger type system event, further The process information is read, and it is determined whether there is a restarted process according to the process information; and the number of restarts of the restarted process in a preset time is recorded; when the restarted number is greater than a preset threshold, the process is determined to be corresponding to The application is abnormal.
  • the mobile terminal in the embodiment of the present invention detects the system event of the mobile terminal, and reads the process information when the trigger system event is detected, and records the restart time of the restart process in the preset time when the restart process exists, and
  • the application corresponding to the process that determines that the number of restarts is greater than the preset threshold is an abnormal application, and the process information is read only when the triggering system event is detected, and is affected by the application environment, attributes, and load of the mobile terminal, and thus is improved.
  • the efficiency of detection of application anomalies reduces energy consumption and resource consumption. It can support native native processes, and the detection scope is wider.
  • a storage medium configured to store an application, and the application is used to execute a method for detecting an abnormality of an application according to the first aspect of the present invention.
  • FIG. 1 is a flow chart of a method for detecting an application anomaly according to an embodiment of the present invention
  • FIG. 2 is a flow chart of a method for detecting an application anomaly according to another embodiment of the present invention.
  • FIG. 3 is a schematic diagram of an interface of an abnormal application detection result according to an embodiment of the present invention.
  • FIG. 4 is a schematic structural diagram of an apparatus for detecting an abnormality of an application according to an embodiment of the present invention.
  • FIG. 5 is a schematic structural diagram of an apparatus for detecting an abnormality of an application according to another embodiment of the present invention.
  • the mobile terminal may be a device having an operating system such as a mobile phone, a notebook computer, a tablet computer, an e-book, a personal digital assistant, or the like.
  • FIG. 1 is a flow chart of a method of detecting an application anomaly in accordance with one embodiment of the present invention. As shown in FIG. 1, the detection method of the application abnormality includes the following steps.
  • any system event in the mobile terminal can be detected, and it is further determined whether the detected system event is a trigger type system event.
  • system event if the system event is one of the following multiple system events, it is determined to trigger a system-like event: a broadcast system event (such as a lock screen broadcast, an unlock broadcast, and other broadcast events, etc.), and a memory.
  • a broadcast system event such as a lock screen broadcast, an unlock broadcast, and other broadcast events, etc.
  • a memory Insufficient alarm system events, application startup system events, or application exception exit system events.
  • the process information can be read by reading process information recorded by the kernel/proc file system in the mobile terminal.
  • the kernel / proc file system is a special file system created by software, the kernel can use it to export information to the outside world. All information about the currently running process is recorded in the kernel/proc file system.
  • the process information can be read by reading the process information recorded by the kernel/proc file system in the mobile terminal.
  • reading the process information directly from the kernel/proc file system eliminates the function operation in the API getRunningAppProcesses(), which can reduce the time for reading the process information. And get complete, comprehensive data on the process.
  • the inventor finds that the time taken to read the information directly from the kernel/proc file system is about 40% of the time taken to read the information by APIgetRunningAppProcesses(), so that the embodiment of the present invention can be seen.
  • the method can greatly reduce the time for reading process information, thereby improving the detection efficiency of application exceptions.
  • the process information may include a process name and a process identifier PID (Process Identifier) corresponding to the process name, and may be recorded according to a process recorded by a kernel/proc file system in the mobile terminal.
  • PID Process Identifier
  • the information determines whether the PID corresponding to the same process name is the same as the PID in the last read progress information; if not, it is determined that the process is restarted.
  • the process information may be read according to a preset frequency within a preset time, and the number of restarts may be recorded according to the change of the process information. For example, each time the information is read, multiple processes and their PIDs can be obtained according to the process information. If the PID of a process changes compared with the last time the process information is read, the process restarts. The number of restarts of the process can be +1. Thus, after the process information is continuously read multiple times according to the preset frequency at the preset time, the number of restarts of each process can be obtained.
  • the preset time and the preset frequency may be default settings.
  • the method for detecting an abnormality of an application in the embodiment of the present invention detects a system event of the mobile terminal, and reads the process information when the trigger system event is detected, and records the restart process within a preset time when the restart process exists.
  • the number of restarts, and the application corresponding to the process whose restart number is greater than the preset threshold is an abnormal application, and the process information is read only when the trigger system event is detected, and is affected by the application environment, attributes, and load of the mobile terminal. Therefore, while improving the detection efficiency of application anomalies, energy consumption and resource consumption are reduced.
  • the native native process can be supported and the scope of detection is broader.
  • the detection method of the application abnormality includes the following steps.
  • the S201-S204 is the same as the S101-S104 in the embodiment shown in FIG. 1, and the embodiment shown in FIG. 1 can be referred to, and details are not described herein again.
  • the manner in which an abnormal application is cleaned may include a forced stop, an automatic restart, an uninstall, an update, and the like.
  • an abnormal application can be provided to a user of the mobile terminal, and the abnormal application can be cleaned according to the user's instruction.
  • the user may be provided with a button for cleaning up the abnormal application, and the user may input an instruction for performing the cleaning by triggering the button.
  • the method may further include: acquiring the restart number of the abnormal application, and providing the restarted number of the abnormal application to the user of the mobile terminal.
  • the number of restarts of the application is the number of restarts of the process corresponding to the application.
  • FIG. 3 is a schematic diagram of an abnormal application detection result interface according to an embodiment of the present invention.
  • two abnormal applications of the 360 clean master and 360 guards detected are displayed, and the respective applications are displayed.
  • the number of restarts are displayed.
  • a "stop" button is provided for each exception application, and when the user clicks on the button, the corresponding application is stopped, ending its frequent restart behavior.
  • the method for detecting an application abnormality in the embodiment of the present invention can clean the abnormal application after determining the abnormal application, and can also provide information such as the number of restarts of the abnormal application to the user, which is convenient for the user. Understand the operation of abnormal applications, and help users to take appropriate solutions to reduce the resources of mobile terminals. Consumption increases the speed of the mobile terminal and improves the user experience.
  • the present invention also proposes an apparatus for detecting an abnormality of an application.
  • the detection device for the application abnormality includes: a detection module 10, a reading module 20, a first determination module 30, a recording module 40, and a second determination module 50.
  • the detecting module 10 is configured to detect a system event of the mobile terminal.
  • the detecting module 10 can detect any system event in the mobile terminal, and further determine whether the detected system event is a triggering system event.
  • system event if the system event is one of the following multiple system events, it is determined to trigger a system-like event: a broadcast system event (such as a lock screen broadcast, an unlock broadcast, and other broadcast events, etc.), and a memory.
  • a broadcast system event such as a lock screen broadcast, an unlock broadcast, and other broadcast events, etc.
  • a memory Insufficient alarm system events, application startup system events, or application exception exit system events.
  • the reading module 20 is configured to further read the process information when the system event is a trigger-like system event.
  • the reading module 20 can read the process information by reading the process information recorded by the kernel/proc file system in the mobile terminal.
  • the kernel / proc file system is a special file system created by software, the kernel can use it to export information to the outside world. All information about the currently running process is recorded in the kernel/proc file system.
  • the process information can be read by reading the process information recorded by the kernel/proc file system in the mobile terminal.
  • reading the process information directly from the kernel/proc file system eliminates the function operation in the API getRunningAppProcesses(), which can reduce the time for reading the process information. And get complete, comprehensive data on the process.
  • the inventor finds that the time taken to read the information directly from the kernel/proc file system is about 40% of the time taken to read the information by APIgetRunningAppProcesses(), so that the embodiment of the present invention can be seen.
  • the method can greatly reduce the time for reading process information, thereby improving the detection efficiency of application exceptions.
  • the first determining module 30 is configured to determine, according to the process information, whether there is a restarting process.
  • the process information may include a process name and a process identifier PID (Process Identifier) corresponding to the process name, and the first determining module 30 may be based on the kernel in the mobile terminal.
  • PID Process Identifier
  • the process information recorded by the proc file system determines whether the PID corresponding to the same process name is the same as the PID in the last read progress information; if not, the process is restarted.
  • the recording module 40 is configured to record the number of restarts of the restarted process within a preset time.
  • the recording module 40 can read the process information according to the preset frequency within a preset time, and record the number of restarts according to the change of the process information. For example, each time the information is read, multiple processes and their PIDs can be obtained according to the process information. If the PID of a process changes compared with the last time the process information is read, Then, the process restarts, and the number of restarts of the process is +1. Thus, after the process information is continuously read multiple times according to the preset frequency at a preset time, the number of restarts of each process can be obtained.
  • the preset time and the preset frequency may be default settings.
  • the second determining module 50 is configured to determine that the application corresponding to the process is abnormal when the number of restarts is greater than a preset threshold.
  • the detecting device for detecting an abnormality of the embodiment of the present invention detects the system event of the mobile terminal, and reads the process information when the triggering system event is detected, and records the restarting process within a preset time when the restarting process exists.
  • the number of restarts, and the application corresponding to the process whose restart number is greater than the preset threshold is an abnormal application, and the process information is read only when the trigger system event is detected, and is affected by the application environment, attributes, and load of the mobile terminal. Therefore, while improving the detection efficiency of application anomalies, energy consumption and resource consumption are reduced.
  • the native native process can be supported and the scope of detection is broader.
  • FIG. 5 is a schematic structural diagram of an apparatus for detecting an abnormality of an application according to another embodiment of the present invention.
  • the detection device of the application abnormality includes: a detection module 10, a reading module 20, a first determination module 30, a recording module 40, a second determination module 50, a cleaning module 60, and an acquisition module 70.
  • the cleaning module 60 is configured to clean the abnormal application after determining that the application corresponding to the process is abnormal.
  • the cleanup module 60 may clean the abnormal application by forced stop, disable automatic restart, uninstall, update, and the like.
  • the cleaning module 60 is specifically configured to: provide an abnormal application to a user of the mobile terminal, and clean up the abnormal application according to the user's instruction. More specifically, the cleanup module 60 can provide the user with a button to clean up the abnormal application, and the user can input an instruction to perform the cleanup by triggering the button.
  • the obtaining module 70 is configured to obtain the number of restarts of the abnormal application after the abnormality of the application corresponding to the process is determined, and provide the user to the mobile terminal.
  • the number of restarts of the application is the number of restarts of the process corresponding to the application.
  • FIG. 3 is a schematic diagram of an abnormal application detection result interface according to an embodiment of the present invention.
  • two abnormal applications of the 360 clean master and 360 guards detected are displayed, and the respective applications are displayed.
  • the number of restarts are displayed.
  • a "stop" button is provided for each exception application, and when the user clicks on the button, the corresponding application is stopped, ending its frequent restart behavior.
  • the device abnormality detecting device in the embodiment of the present invention can clean the abnormal application after determining the abnormal application, and can also provide information such as the number of restarts of the abnormal application to the user, which is convenient for the user. Understand the operation of an abnormal application, which is beneficial to the user to take appropriate measures to reduce the resource consumption of the mobile terminal, improve the running speed of the mobile terminal, and improve the user experience.
  • the present invention proposes a mobile terminal.
  • a mobile terminal includes a casing, a processor, a memory, a circuit board, and a power supply circuit, wherein the circuit board is disposed inside a space enclosed by the casing, the processor and the memory are disposed on the circuit board; and the power circuit For powering various circuits or devices of the mobile terminal;
  • the memory is for storing executable program code;
  • the processor runs the program corresponding to the executable program code by reading the executable program code stored in the memory for:
  • any system event in the mobile terminal can be detected, and it is further determined whether the detected system event is a trigger type system event.
  • system event if the system event is one of the following multiple system events, it is determined to trigger a system-like event: a broadcast system event (such as a lock screen broadcast, an unlock broadcast, and other broadcast events, etc.), and a memory.
  • a broadcast system event such as a lock screen broadcast, an unlock broadcast, and other broadcast events, etc.
  • a memory Insufficient alarm system events, application startup system events, or application exception exit system events.
  • the process information can be read by reading process information recorded by the kernel/proc file system in the mobile terminal.
  • the kernel / proc file system is a special file system created by software, the kernel can use it to export information to the outside world. All information about the currently running process is recorded in the kernel/proc file system.
  • the process information can be read by reading the process information recorded by the kernel/proc file system in the mobile terminal.
  • reading the process information directly from the kernel/proc file system eliminates the function operation in the API getRunningAppProcesses(), which can reduce the time for reading the process information. And get complete, comprehensive data on the process.
  • the inventor finds that the time taken to read the information directly from the kernel/proc file system is about 40% of the time taken to read the information by APIgetRunningAppProcesses(), so that the embodiment of the present invention can be seen.
  • the method can greatly reduce the time for reading process information, thereby improving the detection efficiency of application exceptions.
  • the process information may include a process name and a process identifier PID (Process Identifier) corresponding to the process name, and may be recorded according to a process recorded by a kernel/proc file system in the mobile terminal.
  • PID Process Identifier
  • the information determines whether the PID corresponding to the same process name is the same as the PID in the last read progress information; if not, it is determined that the process is restarted.
  • the process information may be read according to a preset frequency within a preset time, and the number of restarts may be recorded according to the change of the process information. For example, each time the information is read, multiple processes and their PIDs can be obtained according to the process information. If the PID of a process changes compared with the last time the process information is read, the process sends After the restart is initiated, the number of restarts of the process can be +1. Thus, after the process information is continuously read multiple times according to the preset frequency at the preset time, the number of restarts of each process can be obtained.
  • the preset time and the preset frequency may be default settings.
  • the mobile terminal of the embodiment of the present invention records the system event of the mobile terminal, and reads the process information when the triggering system event is detected, and records the restart number of the restart process when the restart process exists in the multiple processes, and
  • the application corresponding to the process that determines that the number of restarts is greater than the preset threshold is an abnormal application, and the current process is read only when the triggering system event is detected, and is affected by the application environment, attributes, and load of the mobile terminal, and thus Improves the detection efficiency of application anomalies while reducing energy consumption and resource consumption.
  • the detection of processes is widely applicable.
  • the processor is further configured to:
  • the manner in which an abnormal application is cleaned may include a forced stop, an automatic restart, an uninstall, an update, and the like.
  • an abnormal application can be provided to a user of the mobile terminal, and the abnormal application can be cleaned according to the user's instruction.
  • the user may be provided with a button for cleaning up the abnormal application, and the user may input an instruction for performing the cleaning by triggering the button.
  • the processor may be further configured to: acquire the restart number of the abnormal application, and provide the restarted number of the abnormal application to the user of the mobile terminal.
  • the number of restarts of the application is the number of restarts of the process corresponding to the application.
  • FIG. 3 is a schematic diagram of an abnormal application detection result interface according to an embodiment of the present invention.
  • two abnormal applications of the 360 clean master and 360 guards detected are displayed, and the respective applications are displayed.
  • the number of restarts are displayed.
  • a "stop" button is provided for each exception application, and when the user clicks on the button, the corresponding application is stopped, ending its frequent restart behavior.
  • the present invention provides a storage medium for storing an application for executing an application abnormality detecting method according to any one of the embodiments of the present invention.
  • portions of the invention may be implemented in hardware, software, firmware or a combination thereof.
  • multiple steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system.
  • a suitable instruction execution system For example, if implemented in hardware, as in another embodiment, it can be implemented by any one or combination of the following techniques well known in the art: having logic gates for implementing logic functions on data signals. Discrete logic circuits, application specific integrated circuits with suitable combinational logic gates, programmable gate arrays (PGAs), field programmable gate arrays (FPGAs), etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Computer Hardware Design (AREA)
  • Telephone Function (AREA)
  • Stored Programmes (AREA)
  • Retry When Errors Occur (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种应用程序异常的检测方法、装置和移动终端。其中，该应用程序异常的检测方法包括以下步骤：检测移动终端的***事件（S101）；当***事件为触发类***事件时，进一步读取进程信息，并根据进程信息判断是否存在有重启的进程（S102）；记录重启的进程在预设时间内的重启次数（S103）；当重启次数大于预设阈值时，判断进程对应的应用程序异常（S104）。该应用程序异常的检测方法，对进程的检测适用范围广，在提高了应用程序异常的检测效率的同时，减少了能耗和资源占用。

Description

应用程序异常的检测方法、装置和移动终端
相关申请的交叉引用
本申请要求北京金山安全软件有限公司于2014年10月10日提交的、发明名称为“应用程序异常的检测方法、装置和移动终端”的、中国专利申请号“201410532339.6”的优先权。
技术领域
本发明涉及移动终端技术领域，尤其涉及一种应用程序异常的检测方法、装置和移动终端。
背景技术
随着移动终端技术的不断发展，移动终端的功能越来越强大，其中安装的应用程序也越来越多。移动终端中的一些应用程序会因运行异常或者其他因素而导致资源过度占用，并引起移动终端卡顿、反应慢、发热等现象，并且会耗费移动终端大量的电量。其中，移动终端的应用程序因运行异常而频繁重启即为导致资源过度占用的情况之一。
目前，移动终端可通过定期枚举的方法检测移动终端中新启动的进程，从而检测出移动终端中频繁重启的应用程序。以安卓Android***的移动终端为例，可通过Android进程APIgetRunningAppProcesses()定期枚举获取移动终端已启动的进程，并根据枚举结果确定频繁重启的进程。
但是，定期枚举的方法存在以下问题：
1、受应用环境、属性、移动终端当前负载等因素的影响，速度慢，加重移动终端***的负担；
2、每次枚举都需要耗费一定的电量，执行定期枚举是对一种极大消耗移动终端的电量方法；
3、不支持native原生进程的重启检测。
发明内容
本发明旨在至少解决上述技术问题之一。
为此，本发明的第一个目的在于提出一种应用程序异常的检测方法。该方法对进程的检测适用范围广，在提高了应用程序异常的检测效率的同时，减少了能耗和资源占用。
本发明的第二个目的在于提出一种应用程序异常的检测装置。
本发明的第三个目的在于提出一种移动终端。
本发明的第四个目的在于提出一种存储介质。
为了实现上述目的，本发明第一方面实施例的应用程序异常的检测方法，包括以下步骤：检测移动终端的***事件；当所述***事件为触发类***事件时，进一步读取进程信息，并根据所述进程信息判断是否存在有重启的进程；记录所述重启的进程在预设时间内的重启次数；当所述重启次数大于预设阈值时，判断所述进程对应的应用程序异常。
本发明实施例的应用程序异常的检测方法，通过检测移动终端的***事件，并在检测到触发类***事件时读取进程信息，并在存在重启进程时，记录重启进程在预设时间内的重启次数，并判断重启次数大于预设阈值的进程对应的应用程序为异常应用程序，仅在检测到触发类***事件时才读取进程信息，并且受到移动终端应用环境、属性以及负载的影响小，因而在提高了应用程序异常的检测效率的同时，减少了能耗和资源占用。此外，可支持native原生进程，检测适用范围更广。
为了实现上述目的，本发明第二方面实施例的应用程序异常的检测装置，包括：检测模块，用于检测移动终端的***事件；读取模块，用于当所述***事件为触发类***事件时，进一步读取进程信息；第一判断模块，用于根据所述进程信息判断是否存在有重启的进程；记录模块，用于记录重启的所述进程在预设时间内的重启次数；第二判断模块，用于当所述重启次数大于预设阈值时，判断所述进程对应的应用程序异常。
本发明实施例的应用程序异常的检测装置，通过检测移动终端的***事件，并在检测到触发类***事件时读取进程信息，并在存在重启进程时，记录重启进程在预设时间内的重启次数，并判断重启次数大于预设阈值的进程对应的应用程序为异常应用程序，仅在检测到触发类***事件时才读取进程信息，并且受到移动终端应用环境、属性以及负载的影响小，因而在提高了应用程序异常的检测效率的同时，减少了能耗和资源占用。此外，可支持native原生进程，检测适用范围更广。
为了实现上述目的，本发明第三方面实施例的移动终端，包括：壳体、处理器、存储器、电路板和电源电路，其中，所述电路板安置在所述壳体围成的空间内部，所述处理器和所述存储器设置在所述电路板上；所述电源电路，用于为所述移动终端的各个电路或器件供电；所述存储器用于存储可执行程序代码；所述处理器通过读取所述存储器中存储的可执行程序代码来运行与所述可执行程序代码对应的程序，以用于：检测移动终端的***事件；当所述***事件为触发类***事件时，进一步读取进程信息，并根据所述进程信息判断是否存在有重启的进程；记录所述重启的进程在预设时间内的重启次数；当所述重启次数大于预设阈值时，判断所述进程对应的应用程序异常。
本发明实施例的移动终端，通过检测移动终端的***事件，并在检测到触发类***事件时读取进程信息，并在存在重启进程时，记录重启进程在预设时间内的重启次数，并判断重启次数大于预设阈值的进程对应的应用程序为异常应用程序，仅在检测到触发类***事件时才读取进程信息，并且受到移动终端应用环境、属性以及负载的影响小，因而在提高了应用程序异常的检测效率的同时，减少了能耗和资源占用。可支持native原生进程，检测适用范围更广。
为了实现上述目的，本发明第四方面实施例的存储介质，用于存储应用程序，所述应用程序用于执行本发明第一方面实施例所述的应用程序异常的检测方法。
本发明附加的方面和优点将在下面的描述中部分给出，部分将从下面的描述中变得明显，或通过本发明的实践了解到。
附图说明
本发明上述的和/或附加的方面和优点从下面结合附图对实施例的描述中将变得明显和容易理解，其中，
图1是根据本发明一个实施例的应用程序异常的检测方法的流程图；
图2是根据本发明另一个实施例的应用程序异常的检测方法的流程图。
图3为根据本发明一个实施例异常应用程序检测结果界面示意图；
图4是根据本发明一个实施例的应用程序异常的检测装置的结构示意图；
图5是根据本发明另一个实施例的应用程序异常的检测装置的结构示意图。
具体实施方式
下面详细描述本发明的实施例，实施例的示例在附图中示出，其中自始至终相同或类似的标号表示相同或类似的元件或具有相同或类似功能的元件。下面通过参考附图描述的实施例是示例性的，仅用于解释本发明，而不能理解为对本发明的限制。相反，本发明的实施例包括落入所附加权利要求书的精神和内涵范围内的所有变化、修改和等同物。
在本发明的描述中，需要理解的是，术语“第一”、“第二”等仅用于描述目的，而不能理解为指示或暗示相对重要性。在本发明的描述中，需要说明的是，除非另有明确的规定和限定，术语“相连”、“连接”应做广义理解，例如，可以是固定连接，也可以是可拆卸连接，或一体地连接；可以是机械连接，也可以是电连接；可以是直接相连，也可以通过中间媒介间接相连。对于本领域的普通技术人员而言，可以具体情况理解上述术语在本发明中的具体含义。此外，在本发明的描述中，除非另有说明，“多个”的含义是两个或两个以上。
流程图中或在此以其他方式描述的任何过程或方法描述可以被理解为，表示包括一个或 更多个用于实现特定逻辑功能或过程的步骤的可执行指令的代码的模块、片段或部分，并且本发明的优选实施方式的范围包括另外的实现，其中可以不按所示出或讨论的顺序，包括根据所涉及的功能按基本同时的方式或按相反的顺序，来执行功能，这应被本发明的实施例所属技术领域的技术人员所理解。
下面参考附图描述根据本发明实施例的应用程序异常的检测方法、装置和移动终端。
应当理解，在本发明的实施例中，移动终端可以是手机、笔记本电脑、平板电脑、电子书、个人数字助理等具有操作***的设备。
图1是根据本发明一个实施例的应用程序异常的检测方法的流程图。如图1所示，该应用程序异常的检测方法包括以下步骤。
S101，检测移动终端的***事件。
在本发明的实施例中，可对移动终端中任意***事件进行检测，并进一步判断检测到的***事件是否为触发类***事件。
在本发明的一个实施例中，如果***事件为如下多个***事件中的一种，则判断为触发类***事件：广播***事件(如锁屏广播、解锁广播以及其他广播事件等)、内存不足报警***事件、应用程序启动***事件或应用程序异常退出***事件等。
S102，当***事件为触发类***事件时，进一步读取进程信息，并根据进程信息判断是否存在有重启的进程。
在本发明的一个实施例中，可通过读取移动终端中内核/proc文件***记录的进程信息以读取进程信息。其中，内核/proc文件***是一种特殊的、由软件创建的文件***，内核可使用它向外界导出信息。内核/proc文件***中记录了当前运行的进程所有信息。因而，可通过读取移动终端中内核/proc文件***记录的进程信息读取进程信息。
另外，相较于传统的通过API getRunningAppProcesses()读取进程的方法，直接从内核/proc文件***读取进程信息免去了API getRunningAppProcesses()中的函数运算，可以降低读取进程信息的时间，并且可获取进程的完整、全面的数据。在本发明的实现过程中，发明人发现直接从内核/proc文件***读取进行信息所用的时间约为通过APIgetRunningAppProcesses()读取进行信息所用时间的40％左右，由此可见本发明实施例的方法可大大降低读取进程信息的时间，进而提高了应用程序异常的检测效率。
具体地，在本发明的一个实施例中，进程信息可包括进程名和与该进程名对应的进程标识符PID(Process Identifier，进程标识符)，可根据移动终端中内核/proc文件***记录的进程信息判断同一进程名对应的PID与上次读取的进行信息中的PID是否相同；若否，则认定该进程重启。
S103，记录重启的进程在预设时间内的重启次数。
在本发明的一个实施例中，可在预设时间内按照预设频率读取进程信息，并根据进程信息的变化情况记录重启次数。举例来说，在每次读取进行信息时，可根据进程信息获取多个进程及其PID，如果一个进程的PID与上一次读取进程信息时相比发生了变化，则该进程发生了重启，可将该进程的重启次数+1，由此，经过在预设时间按照预设频率连续多次读取进程信息后，即可得到每个进程的重启次数。其中，预设时间与预设频率可为默认设定。
S104，当重启次数大于预设阈值时，判断进程对应的应用程序异常。
本发明实施例的应用程序异常的检测方法，通过检测移动终端的***事件，并在检测到触发类***事件时读取进程信息，并在存在重启进程时，记录重启进程在预设时间内的重启次数，并判断重启次数大于预设阈值的进程对应的应用程序为异常应用程序，仅在检测到触发类***事件时才读取进程信息，并且受到移动终端应用环境、属性以及负载的影响小，因而在提高了应用程序异常的检测效率的同时，减少了能耗和资源占用。此外，可支持native原生进程，检测适用范围更广。
图2是根据本发明另一个实施例的应用程序异常的检测方法的流程图。具体地，如图2所示，该应用程序异常的检测方法包括以下步骤。
S201-S204与图1所示实施例中S101-S104相同，可参照图1所示实施例，在此不再赘述。
S205，对异常的应用程序进行清理。
在本发明的实施例中，对异常的应用程序的清理方式可包括强制停止、禁止自动重启、卸载、更新等。
在本发明的一个实施例中，具体地，可将异常的应用程序提供至移动终端的用户，并根据用户的指令对异常的应用程序进行清理。具体地，可为用户提供针对异常的应用程序进行清理的按钮，用户可通过触发该按钮输入用于执行清理的指令。
在本发明的另一个实施例中，在判断进程对应的应用程序异常之后，还可包括：获取异常的应用程序的重启次数，并将异常的应用程序的重启次数提供给移动终端的用户。其中，应用程序的重启次数即为该应用程序对应的进程的重启次数。
举例来说，图3为根据本发明一个实施例异常应用程序检测结果界面示意图，如图3所示，显示了本次检测到的360清理大师和360卫士两个异常应用程序，并且显示了各自的重启次数。另外，针对每个异常应用程序均提供了“停止”按钮，当用户点击该按钮时，相应的应用程序就会被停止，从而结束了其频繁重启的行为。
本发明实施例的应用程序异常的检测方法，在判断出异常的应用程序后，可对异常的应用程序进行清理，此外，还可将异常的应用程序的重启次数等信息提供给用户，便于用户了解异常的应用程序的运行情况，有利于用户采取适当的解决措施，从而减少移动终端的资源 消耗，提升移动终端的运行速度，提升了用户体验。
为了实现上述实施例，本发明还提出一种应用程序异常的检测装置。
图4是根据本发明一个实施例的应用程序异常的检测装置的结构示意图。如图4所示，应用程序异常的检测装置包括：检测模块10、读取模块20、第一判断模块30、记录模块40和第二判断模块50。
具体地，检测模块10用于检测移动终端的***事件。
在本发明的实施例中，检测模块10可对移动终端中任意***事件进行检测，并进一步判断检测到的***事件是否为触发类***事件。
在本发明的一个实施例中，如果***事件为如下多个***事件中的一种，则判断为触发类***事件：广播***事件(如锁屏广播、解锁广播以及其他广播事件等)、内存不足报警***事件、应用程序启动***事件或应用程序异常退出***事件等。
读取模块20用于当***事件为触发类***事件时，进一步读取进程信息。
在本发明的一个实施例中，读取模块20可通过读取移动终端中内核/proc文件***记录的进程信息以读取进程信息。其中，内核/proc文件***是一种特殊的、由软件创建的文件***，内核可使用它向外界导出信息。内核/proc文件***中记录了当前运行的进程所有信息。因而，可通过读取移动终端中内核/proc文件***记录的进程信息读取进程信息。
另外，相较于传统的通过API getRunningAppProcesses()读取进程的方法，直接从内核/proc文件***读取进程信息免去了API getRunningAppProcesses()中的函数运算，可以降低读取进程信息的时间，并且可获取进程的完整、全面的数据。在本发明的实现过程中，发明人发现直接从内核/proc文件***读取进行信息所用的时间约为通过APIgetRunningAppProcesses()读取进行信息所用时间的40％左右，由此可见本发明实施例的方法可大大降低读取进程信息的时间，进而提高了应用程序异常的检测效率。
第一判断模块30用于根据进程信息判断是否存在有重启的进程。
更具体地，在本发明的一个实施例中，进程信息可包括进程名和与该进程名对应的进程标识符PID(Process Identifier，进程标识符)，第一判断模块30可根据移动终端中内核/proc文件***记录的进程信息判断同一进程名对应的PID与上次读取的进行信息中的PID是否相同；若否，则认定该进程重启。
记录模块40用于记录重启的进程在预设时间内的重启次数。
在本发明的一个实施例中，记录模块40可在预设时间内按照预设频率读取进程信息，并根据进程信息的变化情况记录重启次数。举例来说，在每次读取进行信息时，可根据进程信息获取多个进程及其PID，如果一个进程的PID与上一次读取进程信息时相比发生了变化， 则该进程发生了重启，可将该进程的重启次数+1，由此，经过在预设时间按照预设频率连续多次读取进程信息后，即可得到每个进程的重启次数。其中，预设时间与预设频率可为默认设定。
第二判断模块50用于当重启次数大于预设阈值时，判断进程对应的应用程序异常。
本发明实施例的应用程序异常的检测装置，通过检测移动终端的***事件，并在检测到触发类***事件时读取进程信息，并在存在重启进程时，记录重启进程在预设时间内的重启次数，并判断重启次数大于预设阈值的进程对应的应用程序为异常应用程序，仅在检测到触发类***事件时才读取进程信息，并且受到移动终端应用环境、属性以及负载的影响小，因而在提高了应用程序异常的检测效率的同时，减少了能耗和资源占用。此外，可支持native原生进程，检测适用范围更广。
图5是根据本发明另一个实施例的应用程序异常的检测装置的结构示意图。如图5所示，应用程序异常的检测装置包括：检测模块10、读取模块20、第一判断模块30、记录模块40、第二判断模块50、清理模块60和获取模块70。
具体地，清理模块60用于在判断进程对应的应用程序异常之后，对异常的应用程序进行清理。
在本发明的实施例中，清理模块60对异常的应用程序的清理方式可包括强制停止、禁止自动重启、卸载、更新等。
在本发明的一个实施例中，清理模块60具体用于：将异常的应用程序提供至移动终端的用户，并根据用户的指令对异常的应用程序进行清理。更具体地，清理模块60可为用户提供针对异常的应用程序进行清理的按钮，用户可通过触发该按钮输入用于执行清理的指令。
获取模块70用于在判断进程对应的应用程序异常之后，获取异常的应用程序的重启次数，并提供给移动终端的用户。其中，应用程序的重启次数即为该应用程序对应的进程的重启次数。
举例来说，图3为根据本发明一个实施例异常应用程序检测结果界面示意图，如图3所示，显示了本次检测到的360清理大师和360卫士两个异常应用程序，并且显示了各自的重启次数。另外，针对每个异常应用程序均提供了“停止”按钮，当用户点击该按钮时，相应的应用程序就会被停止，从而结束了其频繁重启的行为。
本发明实施例的应用程序异常的检测装置，在判断出异常的应用程序后，可对异常的应用程序进行清理，此外，还可将异常的应用程序的重启次数等信息提供给用户，便于用户了解异常的应用程序的运行情况，有利于用户采取适当的解决措施，从而减少移动终端的资源消耗，提升移动终端的运行速度，提升了用户体验。
为了实现上述实施例，本发明提出一种移动终端。
根据本发明实施例的移动终端，包括壳体、处理器、存储器、电路板和电源电路，其中，电路板安置在壳体围成的空间内部，处理器和存储器设置在电路板上；电源电路，用于为移动终端的各个电路或器件供电；存储器用于存储可执行程序代码；处理器通过读取存储器中存储的可执行程序代码来运行与可执行程序代码对应的程序，以用于：
S101’，检测移动终端的***事件。
在本发明的实施例中，可对移动终端中任意***事件进行检测，并进一步判断检测到的***事件是否为触发类***事件。
在本发明的一个实施例中，如果***事件为如下多个***事件中的一种，则判断为触发类***事件：广播***事件(如锁屏广播、解锁广播以及其他广播事件等)、内存不足报警***事件、应用程序启动***事件或应用程序异常退出***事件等。
S102’，当***事件为触发类***事件时，进一步读取进程信息，并根据进程信息判断是否存在有重启的进程。
在本发明的一个实施例中，可通过读取移动终端中内核/proc文件***记录的进程信息以读取进程信息。其中，内核/proc文件***是一种特殊的、由软件创建的文件***，内核可使用它向外界导出信息。内核/proc文件***中记录了当前运行的进程所有信息。因而，可通过读取移动终端中内核/proc文件***记录的进程信息读取进程信息。
另外，相较于传统的通过API getRunningAppProcesses()读取进程的方法，直接从内核/proc文件***读取进程信息免去了API getRunningAppProcesses()中的函数运算，可以降低读取进程信息的时间，并且可获取进程的完整、全面的数据。在本发明的实现过程中，发明人发现直接从内核/proc文件***读取进行信息所用的时间约为通过APIgetRunningAppProcesses()读取进行信息所用时间的40％左右，由此可见本发明实施例的方法可大大降低读取进程信息的时间，进而提高了应用程序异常的检测效率。
具体地，在本发明的一个实施例中，进程信息可包括进程名和与该进程名对应的进程标识符PID(Process Identifier，进程标识符)，可根据移动终端中内核/proc文件***记录的进程信息判断同一进程名对应的PID与上次读取的进行信息中的PID是否相同；若否，则认定该进程重启。
S103’，记录重启的进程在预设时间内的重启次数。
在本发明的一个实施例中，可在预设时间内按照预设频率读取进程信息，并根据进程信息的变化情况记录重启次数。举例来说，在每次读取进行信息时，可根据进程信息获取多个进程及其PID，如果一个进程的PID与上一次读取进程信息时相比发生了变化，则该进程发 生了重启，可将该进程的重启次数+1，由此，经过在预设时间按照预设频率连续多次读取进程信息后，即可得到每个进程的重启次数。其中，预设时间与预设频率可为默认设定。
S104’，当重启次数大于预设阈值时，判断进程对应的应用程序异常。
本发明实施例的移动终端，通过检测移动终端的***事件，并在检测到触发类***事件时读取进程信息，并在多个进程中的存在重启进程时，记录重启进程的重启次数，并判断重启次数大于预设阈值的进程对应的应用程序为异常应用程序，仅在检测到触发类***事件时才读取当前的进程，并且受到移动终端应用环境、属性以及负载的影响小，因而在提高了应用程序异常的检测效率的同时，减少了能耗和资源占用。此外，对进程的检测适用范围广。
在本发明的一个实施例中，在判断出异常的应用程序之后，处理器还用于：
对异常的应用程序进行清理。
在本发明的实施例中，对异常的应用程序的清理方式可包括强制停止、禁止自动重启、卸载、更新等。
在本发明的一个实施例中，具体地，可将异常的应用程序提供至移动终端的用户，并根据用户的指令对异常的应用程序进行清理。具体地，可为用户提供针对异常的应用程序进行清理的按钮，用户可通过触发该按钮输入用于执行清理的指令。
在本发明的另一个实施例中，在判断进程对应的应用程序异常之后，处理器还可用于：获取异常的应用程序的重启次数，并将异常的应用程序的重启次数提供给移动终端的用户。其中，应用程序的重启次数即为该应用程序对应的进程的重启次数。
举例来说，图3为根据本发明一个实施例异常应用程序检测结果界面示意图，如图3所示，显示了本次检测到的360清理大师和360卫士两个异常应用程序，并且显示了各自的重启次数。另外，针对每个异常应用程序均提供了“停止”按钮，当用户点击该按钮时，相应的应用程序就会被停止，从而结束了其频繁重启的行为。
由此，便于用户了解异常的应用程序的运行情况，有利于用户采取适当的解决措施，从而减少移动终端的资源消耗，提升移动终端的运行速度，提升了用户体验。
为了实现上述实施例，本发明提出一种存储介质，用于存储应用程序，应用程序用于执行本发明任一项实施例所述的应用程序异常的检测方法。
应当理解，本发明的各部分可以用硬件、软件、固件或它们的组合来实现。在上述实施方式中，多个步骤或方法可以用存储在存储器中且由合适的指令执行***执行的软件或固件来实现。例如，如果用硬件来实现，和在另一实施方式中一样，可用本领域公知的下列技术中的任一项或他们的组合来实现：具有用于对数据信号实现逻辑功能的逻辑门电路的离散逻辑电路，具有合适的组合逻辑门电路的专用集成电路，可编程门阵列(PGA)，现场可编程门阵列(FPGA)等。
在本说明书的描述中，参考术语“一个实施例”、“一些实施例”、“示例”、“具体示例”、或“一些示例”等的描述意指结合该实施例或示例描述的具体特征、结构、材料或者特点包含于本发明的至少一个实施例或示例中。在本说明书中，对上述术语的示意性表述不一定指的是相同的实施例或示例。而且，描述的具体特征、结构、材料或者特点可以在任何的一个或多个实施例或示例中以合适的方式结合。
尽管已经示出和描述了本发明的实施例，本领域的普通技术人员可以理解：在不脱离本发明的原理和宗旨的情况下可以对这些实施例进行多种变化、修改、替换和变型，本发明的范围由权利要求及其等同物限定。

Claims (18)

  1. 一种应用程序异常的检测方法，其特征在于，包括以下步骤：
    检测移动终端的***事件；
    当所述***事件为触发类***事件时，进一步读取进程信息，并根据所述进程信息判断是否存在有重启的进程；
    记录所述重启的进程在预设时间内的重启次数；
    当所述重启次数大于预设阈值时，判断所述进程对应的应用程序异常。
  2. 如权利要求1所述的应用程序异常的检测方法，其特征在于，在所述判断所述进程对应的应用程序异常之后，还包括：
    对异常的应用程序进行清理。
  3. 如权利要求1或2所述的应用程序异常的检测方法，其特征在于，通过读取所述移动终端中内核/proc文件***记录的进程信息以读取所进程信息。
  4. 如权利要求1-3任一项所述的应用程序异常的检测方法，其特征在于，如果所述***事件为如下多个***事件中的一种，则判断为触发类***事件：
    广播***事件、内存不足报警***事件、应用程序启动***事件或应用程序异常退出***事件。
  5. 如权利要求3所述的应用程序异常的检测方法，其特征在于，所述进程信息包括进程名和所述进程名对应的进程标识符PID，所述根据所述进程信息判断是否存在有重启的进程具体包括：
    判断同一进程名对应的PID与上次是否相同；
    若否，则认定该进程重启。
  6. 如权利要求2所述的应用程序异常的检测方法，其特征在于，所述对异常的应用程序进行清理具体包括：
    将异常的应用程序提供至所述移动终端的用户；
    根据所述用户的指令对所述异常的应用程序进行清理。
  7. 如权利要求1-6任一项所述的应用程序异常的检测方法，其特征在于，在所述判断所述进程对应的应用程序异常之后，还包括：
    获取所述异常的应用程序的重启次数，并将所述异常的应用程序的重启次数提供给所述移动终端的用户。
  8. 如权利要求1-7任一项所述的应用程序异常的检测方法，其特征在于，所述记录所述重启的进程在预设时间内的重启次数，具体包括：
    在所述预设时间内按照预设频率读取所述进程信息，并根据所述进程信息的变化情况记录所述重启次数。
  9. 一种应用程序异常的检测装置，其特征在于，包括：
    检测模块，用于检测移动终端的***事件；
    读取模块，用于当所述***事件为触发类***事件时，进一步读取进程信息；
    第一判断模块，用于根据所述进程信息判断是否存在有重启的进程；
    记录模块，用于记录重启的所述进程在预设时间内的重启次数；
    第二判断模块，用于当所述重启次数大于预设阈值时，判断所述进程对应的应用程序异常。
  10. 如权利要求9所述的应用程序异常的检测装置，其特征在于，还包括：
    清理模块，用于在所述判断所述进程对应的应用程序异常之后，对异常的应用程序进行清理。
  11. 如权利要求9或10所述的应用程序异常的检测装置，其特征在于，通过读取所述移动终端中内核/proc文件***记录的进程信息以读取所述进程信息。
  12. 如权利要求9-11任一项所述的应用程序异常的检测装置，其特征在于，如果所述***事件为如下多个***事件中的一种，则判断为触发类***事件：
    广播***事件、内存不足报警***事件、应用程序启动***事件或应用程序异常退出***事件。
  13. 如权利要求11所述的应用程序异常的检测装置，其特征在于，所述进程信息包括进程名和所述进程名对应的进程标识符PID，所述第一判断模块具体用于：
    判断同一进程名对应的PID与上次是否相同；
    若否，则认定该进程重启。
  14. 如权利要求10所述的应用程序异常的检测装置，其特征在于，所述清理模块具体用于：
    将异常的应用程序提供至所述移动终端的用户；
    根据所述用户的指令对所述异常的应用程序进行清理。
  15. 如权利要求9-14任一项所述的应用程序异常的检测装置，其特征在于，还包括：
    获取模块，用于在判断所述进程对应的应用程序异常之后，获取所述异常的应用程序的重启次数，并提供给所述移动终端的用户。
  16. 如权利要求9-15任一项所述的应用程序异常的检测装置，其特征在于，所述记录模块具体用于在所述预设时间内按照预设频率读取所述进程信息，并根据所述进 程信息的变化情况记录所述重启次数。
  17. 一种移动终端，其特征在于，包括：壳体、处理器、存储器、电路板和电源电路，其中，所述电路板安置在所述壳体围成的空间内部，所述处理器和所述存储器设置在所述电路板上；所述电源电路，用于为所述移动终端的各个电路或器件供电；所述存储器用于存储可执行程序代码；所述处理器通过读取所述存储器中存储的可执行程序代码来运行与所述可执行程序代码对应的程序，以用于：
    检测移动终端的***事件；
    当所述***事件为触发类***事件时，进一步读取进程信息，并根据所述进程信息判断是否存在有重启的进程；
    记录所述重启的进程在预设时间内的重启次数；
    当所述重启次数大于预设阈值时，判断所述进程对应的应用程序异常。
  18. 一种存储介质，其特征在于，用于存储应用程序，所述应用程序用于执行权利要求1至8中任一项所述的应用程序异常的检测方法。
PCT/CN2015/088885 2014-10-10 2015-09-02 应用程序异常的检测方法、装置和移动终端 WO2016054957A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US15/327,686 US10394655B2 (en) 2014-10-10 2015-09-02 Method for detecting abnormal application and mobile terminal

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410532339.6A CN104331357B (zh) 2014-10-10 2014-10-10 应用程序异常的检测方法、装置和移动终端
CN201410532339.6 2014-10-10

Publications (1)

Publication Number Publication Date
WO2016054957A1 true WO2016054957A1 (zh) 2016-04-14

Family

ID=52406089

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/088885 WO2016054957A1 (zh) 2014-10-10 2015-09-02 应用程序异常的检测方法、装置和移动终端

Country Status (3)

Country Link
US (1) US10394655B2 (zh)
CN (1) CN104331357B (zh)
WO (1) WO2016054957A1 (zh)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108920306A (zh) * 2018-06-29 2018-11-30 努比亚技术有限公司 基于内存管理的重启定位方法、移动终端及可读存储介质
CN109542724A (zh) * 2018-11-14 2019-03-29 北京达佳互联信息技术有限公司 应用程序异常处理方法、装置、电子设备及存储介质
CN110162479A (zh) * 2019-05-29 2019-08-23 Oppo广东移动通信有限公司 异常应用检测方法、装置及终端设备
CN111405546A (zh) * 2020-03-03 2020-07-10 Oppo广东移动通信有限公司 通话异常处理方法和装置
CN111858313A (zh) * 2020-06-24 2020-10-30 厦门亿联网络技术股份有限公司 一种界面卡顿检测方法、装置及存储介质
CN113032183A (zh) * 2021-03-24 2021-06-25 西安闻泰信息技术有限公司 ***管理方法、装置、计算机设备和存储介质

Families Citing this family (42)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104331357B (zh) * 2014-10-10 2018-07-10 北京金山安全软件有限公司 应用程序异常的检测方法、装置和移动终端
CN106256116B (zh) * 2015-04-14 2019-08-13 华为技术有限公司 一种控制应用程序的方法及终端
CN104991802B (zh) * 2015-07-08 2018-07-03 广东欧珀移动通信有限公司 提示卸载应用程序的方法及装置
CN105302637B (zh) * 2015-10-13 2019-04-23 Oppo广东移动通信有限公司 ***进程运行异常引起卡顿的恢复方法、装置及移动终端
CN105320542B (zh) * 2015-11-04 2018-09-14 上海聚力传媒技术有限公司 一种移动终端退出异常界面的方法和装置
CN105487980B (zh) * 2015-12-04 2019-06-07 Tcl集团股份有限公司 修复应用程序运行异常的方法及装置
CN105959462B (zh) * 2016-04-20 2019-09-17 深圳市万普拉斯科技有限公司 异常启动的控制方法及***
CN106055421A (zh) * 2016-05-30 2016-10-26 Tcl海外电子（惠州）有限公司 智能终端及其异常处理方法
CN106685752B (zh) * 2016-06-28 2019-01-04 腾讯科技（深圳）有限公司 一种信息处理方法及终端
CN106295131B (zh) * 2016-07-29 2019-03-19 武汉联影医疗科技有限公司 一种监管软件运行的方法及装置
US10298605B2 (en) * 2016-11-16 2019-05-21 Red Hat, Inc. Multi-tenant cloud security threat detection
CN106789191A (zh) * 2016-12-06 2017-05-31 微梦创科网络科技（中国）有限公司 一种分布式部署服务进程自动重启方法及装置
CN106598771B (zh) * 2016-12-12 2019-11-08 东软集团股份有限公司 一种失效事件抛出方法及装置
CN106792191B (zh) * 2016-12-22 2019-12-03 深圳Tcl数字技术有限公司 智能电视管理方法及装置
CN106781094A (zh) * 2016-12-29 2017-05-31 北京安天网络安全技术有限公司 一种atm***资源异常报警***及方法
CN107195029B (zh) * 2017-05-02 2019-12-13 王力安防科技股份有限公司 一种电子锁复位控制方法及装置
CN109241729B (zh) * 2017-07-10 2022-05-13 阿里巴巴集团控股有限公司 应用程序的检测、处理方法、装置、终端设备及电子设备
CN107391356B (zh) * 2017-07-26 2020-09-25 北京小米移动软件有限公司 卡顿信息获取方法、装置及计算机可读存储介质
CN107451066A (zh) * 2017-08-22 2017-12-08 网易（杭州）网络有限公司 卡顿处理方法和装置、存储介质、终端
US11151017B2 (en) * 2017-10-09 2021-10-19 Huawei Technologies Co., Ltd. Method for processing refresh and display exceptions, and terminal
CN107832190B (zh) * 2017-10-31 2020-09-22 维沃移动通信有限公司 一种耗电异常的诊断方法、移动终端和存储介质
CN108008800B (zh) * 2017-11-29 2022-02-15 锐捷网络股份有限公司 一种复位请求处理方法、装置和设备
CN108279994B (zh) * 2018-01-22 2021-04-16 北京仿真中心 一种连接Citrix已发布应用异常的自动化解决方法
CN108710544B (zh) * 2018-03-20 2022-02-08 青岛海信网络科技股份有限公司 一种数据库***的进程监控方法及轨道交通综合监控***
CN108762981B (zh) * 2018-04-27 2022-03-15 Oppo广东移动通信有限公司 黑屏处理方法及相关装置
CN108874618B (zh) * 2018-05-04 2022-03-18 平安科技（深圳）有限公司 Cognos进程的监控方法、装置、计算机设备和存储介质
CN109117309A (zh) * 2018-07-27 2019-01-01 努比亚技术有限公司 移动终端重启定位方法、移动终端及计算机可读存储介质
CN109376027A (zh) * 2018-09-26 2019-02-22 深圳壹账通智能科技有限公司 一种异常销毁进程的处理方法及终端
CN109522147A (zh) * 2018-11-15 2019-03-26 Oppo广东移动通信有限公司 一种记录开机异常信息的方法、装置、存储介质及终端
CN110083476A (zh) * 2019-04-23 2019-08-02 努比亚技术有限公司 应用程序控制方法、终端及计算机可读存储介质
CN110471784B (zh) * 2019-07-29 2023-03-14 创新先进技术有限公司 基于Electron平台的播放终端异常处理方法及装置
CN112540666A (zh) * 2019-09-20 2021-03-23 中兴通讯股份有限公司 应用解冻方法、终端设备、计算机设备和计算机可读介质
CN110825396B (zh) * 2019-10-31 2023-07-25 Oppo（重庆）智能科技有限公司 异常处理方法及相关设备
CN110825593B (zh) * 2019-11-11 2022-08-23 腾讯科技（深圳）有限公司 一种进程的异常状态检测方法、装置、设备及存储介质
CN111367720A (zh) * 2020-03-04 2020-07-03 北京字节跳动网络技术有限公司 数据保护方法、装置、电子设备及计算机可读存储介质
CN111845452B (zh) * 2020-06-28 2021-09-07 温岭阿凡达机电有限公司 多功能应急电源的供电控制方法及***
CN111984444A (zh) * 2020-07-24 2020-11-24 五八有限公司 一种异常信息的处理方法和装置
CN112612593A (zh) * 2020-12-28 2021-04-06 深圳Tcl新技术有限公司 蓝牙控制方法、装置、终端设备以及计算机可读存储介质
CN114913649A (zh) * 2021-02-09 2022-08-16 腾讯科技（深圳）有限公司 显示状态监控方法、装置、设备及计算机可读存储介质
CN113866651B (zh) * 2021-09-18 2022-08-02 珠海格力电器股份有限公司 遥控器的低电量的检测方法、检测装置和遥控器
CN115344860B (zh) * 2022-07-28 2023-10-10 荣耀终端有限公司 一种管理应用程序的方法和电子设备
CN117234698B (zh) * 2023-11-16 2024-04-26 荣耀终端有限公司 一种程序异常处理方法、电子设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101674465A (zh) * 2009-10-28 2010-03-17 广东威创视讯科技股份有限公司 一种视频多任务监控处理方法及***
JP2013140491A (ja) * 2012-01-05 2013-07-18 Mitsubishi Electric Corp Ｏｓ動作装置及びｏｓ動作プログラム
CN103309668A (zh) * 2013-06-17 2013-09-18 深圳Tcl新技术有限公司 应用程序未截获异常的处理方法及装置
CN104331357A (zh) * 2014-10-10 2015-02-04 北京金山安全软件有限公司 应用程序异常的检测方法、装置和移动终端

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101489301B1 (ko) * 2008-03-20 2015-02-06 삼성전자주식회사 가상환경 시스템 및 그의 구동방법
US8010833B2 (en) * 2009-01-20 2011-08-30 International Business Machines Corporation Software application cluster layout pattern
JP2012069032A (ja) * 2010-09-27 2012-04-05 Hitachi Cable Ltd 情報処理装置
CN102932387A (zh) * 2011-08-10 2013-02-13 北大方正集团有限公司 设备运行的维护方法及装置
CN102968352B (zh) * 2012-12-14 2015-07-22 杨晓松 进程监控及多级恢复***和方法
KR20140111466A (ko) * 2013-03-11 2014-09-19 삼성전자주식회사 프로세스 인증 방법 및 이를 구현하는 전자 장치
US8959530B1 (en) * 2013-05-07 2015-02-17 Sprint Communications Company L.P. Messaging middleware processing thread count based events
US20150312248A1 (en) * 2014-04-25 2015-10-29 Bank Of America Corporation Identity authentication
US9736173B2 (en) * 2014-10-10 2017-08-15 Nec Corporation Differential dependency tracking for attack forensics
US9841986B2 (en) * 2015-10-27 2017-12-12 Vmware, Inc. Policy based application monitoring in virtualized environment

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101674465A (zh) * 2009-10-28 2010-03-17 广东威创视讯科技股份有限公司 一种视频多任务监控处理方法及***
JP2013140491A (ja) * 2012-01-05 2013-07-18 Mitsubishi Electric Corp Ｏｓ動作装置及びｏｓ動作プログラム
CN103309668A (zh) * 2013-06-17 2013-09-18 深圳Tcl新技术有限公司 应用程序未截获异常的处理方法及装置
CN104331357A (zh) * 2014-10-10 2015-02-04 北京金山安全软件有限公司 应用程序异常的检测方法、装置和移动终端

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108920306A (zh) * 2018-06-29 2018-11-30 努比亚技术有限公司 基于内存管理的重启定位方法、移动终端及可读存储介质
CN109542724A (zh) * 2018-11-14 2019-03-29 北京达佳互联信息技术有限公司 应用程序异常处理方法、装置、电子设备及存储介质
CN110162479A (zh) * 2019-05-29 2019-08-23 Oppo广东移动通信有限公司 异常应用检测方法、装置及终端设备
CN110162479B (zh) * 2019-05-29 2023-09-29 Oppo广东移动通信有限公司 异常应用检测方法、装置及终端设备
CN111405546A (zh) * 2020-03-03 2020-07-10 Oppo广东移动通信有限公司 通话异常处理方法和装置
CN111405546B (zh) * 2020-03-03 2023-12-08 Oppo广东移动通信有限公司 通话异常处理方法和装置
CN111858313A (zh) * 2020-06-24 2020-10-30 厦门亿联网络技术股份有限公司 一种界面卡顿检测方法、装置及存储介质
CN113032183A (zh) * 2021-03-24 2021-06-25 西安闻泰信息技术有限公司 ***管理方法、装置、计算机设备和存储介质

Also Published As

Publication number Publication date
US20170212807A1 (en) 2017-07-27
CN104331357A (zh) 2015-02-04
US10394655B2 (en) 2019-08-27
CN104331357B (zh) 2018-07-10

Similar Documents

Publication Publication Date Title
WO2016054957A1 (zh) 应用程序异常的检测方法、装置和移动终端
JP5647645B2 (ja) サスペンドの延期
CN109803359B (zh) 一种唤醒终端***的方法及终端
CN108702421B (zh) 用于控制应用和组件的电子设备和方法
CN104317373B (zh) 一种移动终端降温的方法和装置
WO2014201945A1 (zh) 一种恶意耗电应用的清理方法、装置及用户终端
WO2013013559A1 (zh) 一种屏幕解锁方法及装置
WO2015007247A1 (zh) 耗电异常的应用程序获取方法、装置和移动终端
US9286120B2 (en) Resource management with dynamic resource budgeting
CN106959386B (zh) 一种漏电流检测方法及移动终端
CN112437914B (zh) 一种***恢复方法及装置
WO2017045533A1 (zh) 在应用程序的预设界面显示用户设备状态的方法和装置
WO2015120702A1 (zh) 应用进程的清理方法、装置及移动终端
US9717055B2 (en) Method for performing alarm grouping control of an electronic device with aid of at least one grouping control strategy, and associated apparatus
KR101941761B1 (ko) 소비 전력을 감소하기 위한 방법, 장치 및 모바일 단말기
US11216053B2 (en) Systems, apparatus, and methods for transitioning between multiple operating states
CN106663164A (zh) 用于提高便携式计算设备(pcd)中的处理器的安全性的***和方法
CN105159722B (zh) Rtc唤醒***的方法及计算机
TWI704448B (zh) 控制電源供應單元的方法
TWI557551B (zh) 電子裝置及其喚醒方法
US9208755B2 (en) Low power application execution on a data processing device having low graphics engine utilization
JP2015095219A (ja) 情報処理装置、情報処理方法および記憶媒体
EP2757481B1 (en) Caching method and caching system using dual disks
CN106648916B (zh) 计步器消息的上报方法及装置
TWI656441B (zh) 待機異常耗電偵測系統及方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15848398

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 15327686

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 07/08/17)

122 Ep: pct application non-entry in european phase

Ref document number: 15848398

Country of ref document: EP

Kind code of ref document: A1