WO2019024646A1 - 应用管控方法、装置及电子设备 - Google Patents

应用管控方法、装置及电子设备 Download PDF

Info

Publication number
WO2019024646A1
WO2019024646A1 PCT/CN2018/094503 CN2018094503W WO2019024646A1 WO 2019024646 A1 WO2019024646 A1 WO 2019024646A1 CN 2018094503 W CN2018094503 W CN 2018094503W WO 2019024646 A1 WO2019024646 A1 WO 2019024646A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
background
fails
match
touch operation
Prior art date
Application number
PCT/CN2018/094503
Other languages
English (en)
French (fr)
Inventor
杜冰
林志泳
张俊
Original Assignee
Oppo广东移动通信有限公司
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 Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Publication of WO2019024646A1 publication Critical patent/WO2019024646A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/461—Saving or restoring of program or task context

Definitions

  • the present application relates to the field of mobile device technologies, and in particular, to an application management method, device, and electronic device.
  • the electronic device side realizes communication, watching video, listening to music, and the like through various applications.
  • the electronic device side realizes communication, watching video, listening to music, and the like through various applications.
  • instant messaging software for video chat.
  • it is implemented by running an application on the electronic device side.
  • the embodiment of the present application provides an application management method, device, and electronic device, which can save power of an electronic device and improve the running speed of the electronic device.
  • an embodiment of the present application provides an application management method, which is applied to an electronic device, where the application management method includes:
  • the first target application in the application launched by the touch operation is excluded from the background application.
  • the embodiment of the present application further provides an application management device, where the application management device includes:
  • a first acquiring module configured to determine an application that is started by a touch operation
  • a second obtaining module configured to determine a background application running in the background
  • a matching module configured to match the background application with the application initiated by the touch operation
  • control module configured to: when the first target application that fails to match in the background application, close the first target application in the application that is started by the touch operation in the background application.
  • the embodiment of the present application further provides an electronic device, where the electronic device includes a processor and a memory, the processor and the memory are electrically connected, and the memory is configured to store instructions and data,
  • the processor is used to perform the following steps:
  • the first target application in the application launched by the touch operation is excluded from the background application.
  • FIG. 1 is a schematic diagram of a scenario of an application management method according to an embodiment of the present disclosure.
  • FIG. 2 is a schematic flowchart diagram of an application management method according to an embodiment of the present application.
  • FIG. 3 is a schematic diagram of a display interface of an electronic device according to an embodiment of the present application.
  • FIG. 4 is a schematic diagram of a first list provided by an embodiment of the present application.
  • FIG. 5 is another schematic diagram of a first list provided by an embodiment of the present application.
  • FIG. 6 is another schematic flowchart of an application management method according to an embodiment of the present disclosure.
  • FIG. 7 is another schematic flowchart of an application management method according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of an application management device according to an embodiment of the present application.
  • FIG. 9 is another schematic structural diagram of an application management device according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of a first acquiring module according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic structural diagram of a second acquiring module according to an embodiment of the present application.
  • FIG. 12 is another schematic structural diagram of an application management device according to an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
  • FIG. 14 is another schematic structural diagram of an electronic device according to an embodiment of the present application.
  • the embodiment of the present application provides an application management method, device, and electronic device.
  • FIG. 1 is a schematic diagram of a scenario of an application management method according to an embodiment of the present application.
  • the scenario may include an electronic device 10, which may include a tablet, a PC (Personal Computer), a mobile phone, etc., and the electronic device 10 is provided with a storage unit and has a microprocessor installed to have computing power.
  • an electronic device 10 which may include a tablet, a PC (Personal Computer), a mobile phone, etc.
  • the electronic device 10 is provided with a storage unit and has a microprocessor installed to have computing power.
  • the electronic device 10 is described by taking a mobile phone as an example.
  • the mobile phone 10 can determine the background application running in the background from the local device, which is defined as the first application 11, and the first application 11 can include multiple, such as iQiyi running in the background. , WeChat, QQ, Baidu browser, 360 security guards and so on.
  • the first application 11 is a background application running in the background.
  • the mobile phone 10 can determine the application launched by the touch operation from the local device, which is defined as the second application 12, and the second application 12 can include multiple, such as Sie Bo, WeChat, QQ, Weibo, QQ mailbox, and the like.
  • the second application 12 can be any application in the mobile phone that is activated by a touch operation.
  • the mobile phone 10 determines the first application 11 and the second application 12
  • the first application 11 and the second application 12 are matched.
  • the first application 11 that fails to match is closed, and the first application 11 can be closed.
  • the scenario may include an application management device 300, which may be specifically integrated in the electronic device 10.
  • the application management device 300 is mainly used to determine an application initiated by a touch operation and determine a background application running in the background; and then, the background application is matched with the application initiated by the touch operation; when there is a matching failure in the background application
  • a target application is closed, the first target application in the application launched by the touch operation is excluded from the background application.
  • an application management device which may be integrated into an electronic device having a storage unit and a microprocessor mounted with a computing capability, such as a tablet, a PC, or a mobile phone.
  • An application management method is applied to an electronic device, which includes:
  • the first target application in the application launched by the touch operation is excluded from the background application.
  • the step of excluding the first target application in the application initiated by the touch operation in the background application is closed, including :
  • the first target application that fails to match has an associated application, the first target application that fails to match and the associated application are closed;
  • the first target application that fails to match does not have an associated application, the first target application that fails to match is placed in the buffer and frozen.
  • the step of placing the matching failed first target application in a buffer and freezing it comprises:
  • the first target application placed in the buffer When the first target application placed in the buffer is not activated by the touch operation within a preset time, the first target application placed in the buffer is closed.
  • the method before the step of determining an application initiated by a touch operation, the method further includes:
  • the method further includes:
  • the step of determining an application initiated by a touch operation includes:
  • the identifiers in the first list form an arrangement with a priority level according to a preset rule.
  • the step of determining a background application running in the background includes:
  • the identifiers in the second list are compared with the identifiers in the first list.
  • the identifiers in the second list form an arrangement with a priority level according to a preset rule.
  • the step of excluding the first target application in the application initiated by the touch operation in the background application is closed, including :
  • the first target application When the first target application is multiple, the first target application forms an arrangement with a priority level according to a preset rule, and closes the first target application whose priority level is lower than a preset threshold.
  • the step of excluding the first target application in the application initiated by the touch operation in the background application is closed, including :
  • a prompt message is sent to prompt the first target application to be an abnormal application.
  • FIG. 2 is a schematic flowchart of an application management method according to an embodiment of the present application.
  • the application management method can include:
  • step S101 an application launched by the touch operation in the electronic device is determined.
  • the application launched by the touch operation in the electronic device is mainly an application launched by clicking in the display interface of the electronic device.
  • An application that is activated by a touch operation in the electronic device may be referred to as a second application, which may be referred to as a plurality of applications.
  • a second application which may be referred to as a plurality of applications.
  • the electronic device can directly determine an application initiated by the touch operation from its local area.
  • FIG. 3 is a schematic diagram of a display interface of an electronic device according to an embodiment of the present application.
  • a plurality of applications are displayed on the display interface 13 of the electronic device 10. All applications in the display interface 13 are activated by a touch operation, such as the application of the Siebel circle 12 by a touch operation.
  • the application launched by the touch operation may be all applications in the electronic device that are activated by a touch operation.
  • the electronic device can always monitor the touch events applied in the display interface, and count all the applications launched by the touch operation in the display interface. Specifically, the electronic device monitors the display interface, and the application in the display interface is started by the touch operation for the first time, and the application that is started by the touch operation for the first time is collected, and the statistical result can be stored in the electronic device. In the memory, until the electronic device determines all the applications initiated by the touch operation, the electronic device can directly obtain the stored statistical results from the memory.
  • the application initiated by the touch operation may also be an application initiated by a touch operation within a preset time period.
  • the preset time period can be one day, one week, one month, two months, and the like.
  • an application that an electronic device launches through a touch operation within one week is not limited to one week.
  • the identification of all applications launched by the touch operation may be obtained according to the above statistical result.
  • the identifier corresponds to all the applications that are activated by the touch operation.
  • the identifier corresponding to the application of the Siebo circle is “Spirit Circle”.
  • the first list is generated according to the identifiers corresponding to the applications that are started by the touch operation, and the identifiers of all the applications that are started by the touch operation are in the first list.
  • FIG. 4 is a schematic diagram of a first list provided by an embodiment of the present application, and FIG. 4 only shows a partial application identifier in the first list.
  • the identifiers corresponding to the applications in the first list 14 are arranged according to different priorities. Different priorities may be formed according to at least one of the usage duration, the usage frequency, the power consumption, and the like applied in the preset time in the first list 14 to form an arrangement having a priority level. For example, the usage durations of the application A, the application B, and the application C are greater than the first duration, and the application A, the application B, and the application C form the first priority 141. A priority level 141 is the highest priority.
  • Application D and application E form a second priority 142; application F and application G form a third priority 143; application H forms a fourth priority 144; application I and application J form a fifth priority 145; application K forms a sixth Priority 146; application L forms a seventh priority 147, which is the lowest priority.
  • the priority levels of the first priority 141, the second priority 142, the third priority 143, the fourth priority 144, the fifth priority 145, the sixth priority 146, and the seventh priority 147 are sequentially lowered. It should be noted that the priority of each application in the embodiment of the present application is not limited to seven, and there may be more or less.
  • FIG. 5 is another schematic diagram of a first list provided by an embodiment of the present application.
  • each application directly forms a priority level according to the length of use, and the application priority level with the longest usage time is set to the highest, and then the priority level is gradually reduced according to the reduction priority of the usage duration.
  • the priority arrangement of the applications shown in FIG. 4 and FIG. 5 may also be formed according to the frequency of use and the amount of power consumption. For details, refer to FIG. 4 and FIG. Narration.
  • determining that the application initiated by the touch operation in the electronic device may first obtain the first list, and then determine an application corresponding to the identifier according to the identifier in the first list.
  • step S102 the electronic device determines a background application that is currently running in the background.
  • the electronic device can directly determine the background application running in the background from the local device.
  • the background application that is currently running in the background can be referred to as the first application, and the background application that is currently running in the background can be referred to as the first application.
  • the electronic device determines that the background application currently running in the background may first obtain an identifier corresponding to the background application running in the background, and then generate a second list according to the identifier.
  • the identifiers corresponding to the applications in the second list may also be arranged according to different priorities. Different priorities may be formed according to at least one of the usage duration, the usage frequency, the power consumption, and the like applied in the preset time in the second list to form a prioritized arrangement. For details, refer to the first list, and details are not described herein again.
  • step S103 the background application running in the background is matched with the application launched by the touch operation.
  • the background application running in the background may be compared with the application launched by the touch operation.
  • the identifier in the second list is compared with the identifier in the first list, and formed. Compare the results, or match the results.
  • the comparison process if the identifier in the second list is not matched in the first list, the matching fails, indicating that the identifier does not exist in the first list; if the identifier in the second list can be in the first list If it matches, the match is successful, indicating that the identifier exists in the first list.
  • step S104 when there is a first target application that fails to match in the background application running in the background, the first target application in the application launched by the touch operation is excluded from the background application.
  • the background application running in the background and the application initiated by the touch operation are matched, when the background application running in the background does not match the corresponding application in the application launched by the touch operation, that is, the background is
  • the running background application has an application that fails to match, and may be defined as a first target application.
  • the first target application may be one or multiple, and the matching failed application is closed, that is, the first target that fails the matching is closed. application. Therefore, the number of background applications running in the background can be reduced, the background application running in the background can be effectively controlled, the running speed of other unclosed applications can be improved, and the power of the electronic device battery can be saved.
  • the embodiment of the present application may also prioritize the first target application according to at least one of the usage duration, the usage frequency, the power consumption, and the like in the preset time. Level, forming a prioritized arrangement, and only closing some of the lower priority first target applications. It should be noted that the priority forming manner of the first target application may be referred to the above content, and the manner of forming the priority is not described herein.
  • a prompt message is sent to prompt the first target application to be an abnormal application, so that the user can understand that there is a background in the electronic device that does not need to run in the background.
  • the background application that is run or maliciously run in the background, so that the user can control, can effectively prevent the background application from malicious behavior.
  • the prompt information may be a prompt message, a prompt voice, or the like.
  • the first target application that fails to match exists only in the background application running in the background, and does not exist in the application initiated by the touch operation, that is, the first target application that fails to be matched is excluded from the touch operation. Start the application outside.
  • FIG. 6 is another schematic flowchart of an application management method according to an embodiment of the present application.
  • the application management method may further include step S105.
  • step S105 when there is a successfully matched application in the background application running in the background, the successfully matched application is normally run.
  • the background application running in the background and the application initiated by the touch operation are matched, when the background application running in the background matches the corresponding application in the application initiated by the touch operation, that is, running in the background
  • the background application has a successfully matched application, and may be defined as a second target application.
  • the second target application may be one or multiple, and the application that successfully matches the normal operation, that is, does not control the second target application. .
  • the background application running in the background of effective control controls the running speed of other unclosed applications, saves the power of the electronic device battery, and improves the security performance.
  • FIG. 7 is another schematic flowchart of an application management method according to an embodiment of the present application.
  • the application management method includes the following steps:
  • step S201 an application launched by the touch operation in the electronic device is determined.
  • the application that is activated by the touch operation in the electronic device is mainly an application that is started by the touch operation in the display interface of the electronic device.
  • An application that is activated by a touch operation in the electronic device may be referred to as a second application, which may be referred to as a plurality of applications.
  • a second application which may be referred to as a plurality of applications.
  • the electronic device can directly determine an application initiated by the touch operation from its local area. Specifically, referring to FIG. 3, a plurality of applications are displayed in the display interface 13 of the electronic device 10, and all applications in the display interface 13 are activated by a touch operation, for example, the application of the Sibo circle 12 is started by a touch operation. .
  • the application launched by the touch operation may be all applications in the electronic device that are activated by a touch operation.
  • the electronic device can always monitor the touch events applied in the display interface, and count all the applications launched by the touch operation in the display interface. Specifically, the electronic device monitors the display interface, and the application in the display interface is started by the touch operation for the first time, and the application that is started by the touch operation for the first time is collected, and the statistical result can be stored in the electronic device. In the memory, until the electronic device determines all the applications initiated by the touch operation, the electronic device can directly obtain the stored statistical results from the memory.
  • the application initiated by the touch operation may also be an application initiated by a touch operation within a preset time period.
  • the preset time period can be one day, one week, one month, two months, and the like.
  • an application that an electronic device launches through a touch operation within one week is not limited to one week.
  • the identification of all applications launched by the touch operation may be obtained according to the above statistical result.
  • the identifier corresponds to all the applications that are activated by the touch operation.
  • the identifier corresponding to the application of the Siebo circle is “Spirit Circle”.
  • the first list is generated according to the identifiers corresponding to the applications that are started by the touch operation, and the identifiers of all the applications that are started by the touch operation are in the first list. Specifically, please refer to Figure 4.
  • the identifiers corresponding to the applications in the first list 14 are arranged according to different priorities. Different priorities may be formed according to at least one of the usage duration, the usage frequency, the power consumption, and the like applied in the preset time in the first list 14 to form an arrangement having a priority level. For example, the usage durations of the application A, the application B, and the application C are greater than the first duration, and the application A, the application B, and the application C form the first priority 141. A priority level 141 is the highest priority.
  • Application D and application E form a second priority 142; application F and application G form a third priority 143; application H forms a fourth priority 144; application I and application J form a fifth priority 145; application K forms a sixth Priority 146; application L forms a seventh priority 147, which is the lowest priority.
  • the priority levels of the first priority 141, the second priority 142, the third priority 143, the fourth priority 144, the fifth priority 145, the sixth priority 146, and the seventh priority 147 are sequentially lowered. It should be noted that the priority of each application in the embodiment of the present application is not limited to seven, and there may be more or less.
  • each application directly forms a priority level according to the length of use, and the application priority level with the longest usage time is set to the highest, and then the priority level is gradually reduced according to the reduction priority of the usage duration.
  • the priority arrangement of the applications shown in FIG. 4 and FIG. 5 may also be formed according to the frequency of use and the amount of power consumption. For details, refer to FIG. 4 and FIG. Narration.
  • determining that the application initiated by the touch operation in the electronic device may first obtain the first list, and then determine an application corresponding to the identifier according to the identifier in the first list.
  • step S202 the electronic device determines a background application that is currently running in the background.
  • the electronic device can directly determine the background application running in the background from the local device.
  • the background application that is currently running in the background can be referred to as the first application, and the background application that is currently running in the background can be referred to as the first application.
  • the electronic device determines that the background application currently running in the background may first obtain an identifier corresponding to the background application running in the background, and then generate a second list according to the identifier.
  • the identifiers corresponding to the applications in the second list may also be arranged according to different priorities. Different priorities may be formed according to at least one of the usage duration, the usage frequency, the power consumption, and the like applied in the preset time in the second list to form a prioritized arrangement. For details, refer to the first list, and details are not described herein again.
  • step S203 the background application running in the background is matched with the application launched by the touch operation.
  • the background application running in the background may be compared with the application launched by the touch operation.
  • the identifier in the second list is compared with the identifier in the first list, and formed. Compare the results, or match the results.
  • the comparison process if the identifier in the second list is not matched in the first list, the matching fails, indicating that the identifier does not exist in the first list; if the identifier in the second list can be in the first list If it matches, the match is successful, indicating that the identifier exists in the first list.
  • step S204 when there is a first target application that fails to match in the background application running in the background, it is determined whether the first target application that fails the matching has an associated application.
  • the associated application has an association relationship with the first target application that fails to match. For example, if the application 1 is started, the application 2 is started according to the startup of the application 1. However, the application 2 is not an application launched by the user, and the user does not need to start the application 2, and the application 2 does not need to run in the background. In particular, some malicious applications are often associated with each other, or are bound to each other and associated with each other. Once one of them is started, the applications with which they are associated can be automatically started and run in the background, while some are running in the background. Unwanted applications or malicious applications, users often can not detect in time, causing great trouble to users. In the embodiment of the present application, if it is determined that the first target application that fails to match has an associated application, the process proceeds to step S205. If it is determined that the first target application whose matching fails has no associated application, then the process proceeds to step S206.
  • step S205 if the first target application that fails the matching has an associated application, the first target application that fails the matching and the associated application are closed.
  • the first target application that fails to match has an associated application
  • the first target application that fails to match and the associated application are closed, thereby preventing the associated application from running in the background, and not only effectively controlling the background application running in the background, Improve the operating speed of electronic devices, reduce the power consumption of electronic devices, and greatly improve the security performance of electronic devices.
  • the background application running in the background and the application initiated by the touch operation are matched, when the background application running in the background does not match the corresponding application in the application launched by the touch operation, that is, the background is
  • the running background application has an application that fails to match, and may be defined as a first target application.
  • the first target application may be one or multiple, and the matching failed application is closed, that is, the first target that fails the matching is closed. application. Therefore, the number of background applications running in the background can be reduced, the background application running in the background can be effectively controlled, the running speed of other unclosed applications can be improved, and the power of the electronic device battery can be saved.
  • the embodiment of the present application may also prioritize the first target application according to at least one of the usage duration, the usage frequency, the power consumption, and the like in the preset time. Level, forming a prioritized arrangement, and only closing some of the lower priority first target applications. It should be noted that the priority forming manner of the first target application may be referred to the above content, and the manner of forming the priority is not described herein.
  • a prompt message is sent to prompt the first target application to be an abnormal application, so that the user can understand that there is a background in the electronic device that does not need to run in the background.
  • Applications or maliciously running applications in the background so that users can control, can effectively prevent applications from malicious behavior.
  • the prompt information may be a prompt message, a prompt voice, or the like.
  • step S206 if the first target application that fails to match does not have an associated application, the first target application that fails the matching is placed in the buffer and frozen.
  • the first target application that fails to match is not a malicious application
  • the first target application is placed in the buffer of the electronic device, and is temporarily frozen, thereby improving the running speed of the electronic device and saving the battery power of the electronic device.
  • the user is also allowed to start the first target application placed in the buffer within a preset time. If the first target application placed in the buffer is not activated by the touch operation within a preset time, the first target application placed in the buffer is closed.
  • step S207 when there is a successfully matched application in the background application running in the background, the successfully matched application is normally run.
  • the background application running in the background and the application that is started by the touch operation are matched, when the background application running in the background matches the corresponding periodic synchronization application in the application initiated by the touch operation, that is,
  • the back-end application running in the background has a successfully matched application, and may be defined as a second target application.
  • the second target application may be one or multiple, and the application that successfully matches the normal operation, that is, the second target application is not applied.
  • Conduct control thus, it can be ensured that the application that the user has used or the security application can operate normally.
  • the background application running in the background of effective control controls the running speed of other unclosed applications, saves the power of the electronic device battery, and improves the security performance.
  • the embodiment of the present application further provides an apparatus based on the application management method.
  • the meaning of the noun is the same as that in the above application management method.
  • An application management device is applied to an electronic device, which includes:
  • a first acquiring module configured to determine an application that is started by a touch operation
  • a second obtaining module configured to determine a background application running in the background
  • a matching module configured to match the background application with the application initiated by the touch operation
  • control module configured to: when the first target application that fails to match in the background application, close the first target application in the application that is started by the touch operation in the background application.
  • the application management device further includes a determining module
  • the determining module is configured to: when there is a first target application that fails to match in the background application, determine whether the first target application that fails to match has an associated application, where the associated application fails with the matching A target application has an association relationship;
  • the control module is further configured to: if the first target application that fails to match has an associated application, close the first target application that fails to match and the associated application;
  • the control module is further configured to: if the first target application that fails to match does not have an associated application, place the first target application that fails to match in a buffer and freeze the same.
  • control module is further configured to: when the first target application placed in the buffer is not activated by a touch operation within a preset time, close the first part placed in the buffer A target application.
  • the application management device further includes:
  • a monitoring module configured to monitor a touch event applied in a display interface of the electronic device
  • a statistics module that collects all applications launched through touch operations.
  • the application management device further includes a third acquisition module and a first generation module, where the first acquisition module includes a first acquisition main module and a first acquisition sub-module;
  • the third obtaining module is configured to obtain an identifier of the application that is started by the touch operation, where the identifier is in one-to-one correspondence with all the applications initiated by the touch operation;
  • the first generating module is configured to generate a first list according to the identifier
  • the first acquiring main module is configured to acquire the first list
  • the first obtaining submodule is configured to determine an application corresponding to the identifier according to the identifier in the first list.
  • the second obtaining module includes a fourth obtaining module and a second generating module:
  • the fourth obtaining module is configured to obtain an identifier that is in one-to-one correspondence with the background application
  • the second generating module is configured to generate a second list according to the identifier that is in one-to-one correspondence with the background application;
  • the matching module is further configured to compare the identifiers in the second list with the identifiers in the first list.
  • FIG. 8 is a schematic structural diagram of an application management device according to an embodiment of the present application.
  • the application management device 300 of the embodiment of the present application includes a first obtaining module 301, a second obtaining module 302, a matching module 303, and a control module 304.
  • the first obtaining module 301 is configured to determine an application that is started by a touch operation in the electronic device.
  • the application that is activated by the touch operation in the electronic device is mainly an application that is touch-operated in the display interface of the electronic device.
  • An application that is activated by a touch operation in the electronic device may be referred to as a second application, which may be referred to as a plurality of applications.
  • a second application which may be referred to as a plurality of applications.
  • the first obtaining module 301 can directly determine an application initiated by the touch operation from the electronic device. Specifically, referring to FIG. 3, a plurality of applications are displayed in the display interface 13 of the electronic device 10, and all applications in the display interface 13 are activated by a touch operation, for example, the application of the Sibo circle 12 is started by a touch operation. .
  • FIG. 9 is another schematic structural diagram of an application management device according to an embodiment of the present application.
  • the application management device 300 can further include a monitoring module 305, a statistics module 306, a third obtaining module 307, and a first generating module 308.
  • the monitoring module 305 is configured to monitor a touch event applied in a display interface of the electronic device.
  • the statistics module 306 is configured to count all applications launched by the touch operation.
  • the third obtaining module 307 is configured to obtain an identifier of all applications that are activated by the touch operation, where the identifier corresponds to all applications that are activated by the touch operation.
  • the first generation module 308 is configured to generate a first list according to the identifier.
  • the application launched by the touch operation may be all applications in the electronic device that are activated by a touch operation.
  • the monitoring module 305 can always monitor the touch events applied in the display interface, and count all the applications in the display interface that are activated by the touch operation. Specifically, the monitoring module 305 monitors the display interface of the electronic device.
  • the statistics module 306 collects the application that is started by the touch operation for the first time, and the statistical result can be obtained.
  • the information is stored in the memory of the electronic device. After the electronic device determines all applications initiated by the touch operation, the first obtaining module 301 can directly obtain the stored statistical result from the memory.
  • the application initiated by the touch operation may also be an application initiated by a touch operation within a preset time period.
  • the preset time period can be one day, one week, one month, two months, and the like.
  • an application that an electronic device launches through a touch operation within one week is not limited to one week.
  • the third obtaining module 307 can obtain the identifiers of all applications launched by the touch operation according to the above statistical result.
  • the identifier corresponds to all the applications that are activated by the touch operation.
  • the identifier corresponding to the application of the Siebo circle is “Spirit Circle”.
  • the first generation module 308 generates a first list according to the identifiers corresponding to the applications initiated by the touch operation, and all the identifiers corresponding to the applications initiated by the touch operation are in the first list. Specifically, please refer to Figure 4.
  • the identifiers corresponding to the applications in the first list 14 are arranged according to different priorities. Different priorities may be formed according to at least one of the usage duration, the usage frequency, the power consumption, and the like applied in the preset time in the first list 14 to form an arrangement having a priority level. For example, the usage durations of the application A, the application B, and the application C are greater than the first duration, and the application A, the application B, and the application C form the first priority 141. A priority level 141 is the highest priority.
  • Application D and application E form a second priority 142; application F and application G form a third priority 143; application H forms a fourth priority 144; application I and application J form a fifth priority 145; application K forms a sixth Priority 146; application L forms a seventh priority 147, which is the lowest priority.
  • the priority levels of the first priority 141, the second priority 142, the third priority 143, the fourth priority 144, the fifth priority 145, the sixth priority 146, and the seventh priority 147 are sequentially lowered. It should be noted that the priority of each application in the embodiment of the present application is not limited to seven, and there may be more or less.
  • each application directly forms a priority level according to the length of use, and the application priority level with the longest usage time is set to the highest, and then the priority level is gradually reduced according to the reduction priority of the usage duration.
  • the priority arrangement of the applications shown in FIG. 4 and FIG. 5 may also be formed according to the frequency of use and the amount of power consumption. For details, refer to FIG. 4 and FIG. Narration.
  • FIG. 10 is a schematic structural diagram of a first acquiring module according to an embodiment of the present application.
  • the first obtaining module 301 includes a first acquiring main module 3011 and a first obtaining sub-module 3012.
  • the first acquiring main module 3011 is configured to acquire the first list.
  • the first obtaining sub-module 3012 is configured to determine an application corresponding to the identifier according to the identifier in the first list.
  • the first obtaining module 301 determines that the application that is started by the touch operation in the electronic device may first obtain the first list by using the first acquiring main module 3011, and then determine, according to the identifier in the first list, by the first obtaining submodule 3012. The application corresponding to the logo.
  • the second obtaining module 302 is configured to determine a background application that is currently running in the background.
  • the second obtaining module 302 can determine, directly from the electronic device, the background application that is currently running in the background, which may be multiple, and may refer to the background application currently running in the background as the first application, and may refer to the above content, and no longer Narration.
  • FIG. 11 is a schematic structural diagram of a second acquiring module according to an embodiment of the present application.
  • the second obtaining module 302 includes a fourth obtaining module 3021 and a second generating module 3022.
  • the fourth obtaining module 3021 is configured to obtain an identifier that is in one-to-one correspondence with the background application running in the background.
  • the second generation module 3022 is configured to generate a second list according to the identifier.
  • the second obtaining module 302 determines that the background application currently running in the background may obtain the identifier corresponding to the background application running in the background by using the fourth obtaining module 3021, and then generate the second identifier according to the identifier by the second generating module 3022.
  • List The identifiers corresponding to the applications in the second list may also be arranged according to different priorities. Different priorities may be formed according to at least one of the usage duration, the usage frequency, the power consumption, and the like applied in the preset time in the second list to form a prioritized arrangement. For details, refer to the first list, and details are not described herein again.
  • the matching module 203 is configured to match the background application running in the background with the application launched by the touch operation.
  • the matching module 203 may compare the background application running in the background with the application launched by the touch operation, and specifically compare the identifier in the second list with the identifier in the first list. And form a comparison result, or a match result. In the comparison process, if the identifier in the second list is not matched in the first list, the matching fails, indicating that the identifier does not exist in the first list; if the identifier in the second list can be in the first list If it matches, the match is successful, indicating that the identifier exists in the first list.
  • the control module 304 is configured to: when there is a first target application that fails to match in the background application running in the background, close the first target application in the application that is started by the touch operation in the background application.
  • the matching module 203 matches the background application running in the background with the application that is started by the touch operation, and when the background application running in the background does not match the corresponding application in the application initiated by the touch operation, That is, the background application running in the background has an application that fails to match, and may be defined as a first target application.
  • the first target application may be one or multiple, and the control module 304 closes the application that fails to match, that is, closes. Match the failed first target application. Therefore, the number of background applications running in the background can be reduced, the background application running in the background can be effectively controlled, the running speed of other unclosed applications can be improved, and the power of the electronic device battery can be saved.
  • the embodiment of the present application may also prioritize the first target application according to at least one of the usage duration, the usage frequency, the power consumption, and the like in the preset time. Level, forming a prioritized arrangement, and only closing some of the lower priority first target applications. It should be noted that the priority forming manner of the first target application may be referred to the above content, and the manner of forming the priority is not described herein.
  • the control module 304 issues a prompt message to prompt the first target application to be an abnormal application, thereby facilitating the user to know that there is no background in the electronic device.
  • the background application running or the background application running maliciously in the background, so that the user can control, can effectively prevent the application from malicious behavior.
  • the prompt information may be a prompt message, a prompt voice, or the like.
  • the first target application that fails to match exists only in the background application running in the background, and does not exist in the application initiated by the touch operation, that is, the first target application that fails to be matched is excluded from the touch operation. Start the application outside.
  • the control module 304 is further configured to normally run the successfully matched application when there is a successfully matched application in the background application running in the background.
  • the matching module 303 matches the background application running in the background with the application initiated by the touch operation, and when the background application running in the background matches the corresponding application in the application initiated by the touch operation,
  • the background application running in the background has an application that is successfully matched, and may be defined as a second target application.
  • the second target application may be one or multiple, and the control module 304 normally runs the successfully matched application, that is, incorrect.
  • the second target application is managed. Thus, it can be ensured that the application that the user has used or the security application can operate normally.
  • the background application running in the background of effective control controls the running speed of other unclosed applications, saves the power of the electronic device battery, and improves the security performance.
  • FIG. 12 is another schematic structural diagram of an application management device according to an embodiment of the present application.
  • the application management device 300 can also include a determination module 309.
  • the determining module 309 is configured to: when there is a first target application that fails to match in the background application running in the background, determine whether the first target application that fails to match has an associated application, where the associated application and the first target that fails to match The application has an association.
  • the associated application has an association relationship with the first target application that fails to match. For example, if the application 1 is started, the application 2 is started according to the startup of the application 1. However, the application 2 is not an application launched by the user, and the user does not need to start the application 2, and the application 2 does not need to run in the background. In particular, some malicious applications are often associated with each other, or are bound to each other and associated with each other. Once one of them is started, the applications with which they are associated can be automatically started and run in the background, while some are running in the background. Unwanted applications or malicious applications, users often can not detect in time, causing great trouble to users.
  • control module 304 is further configured to: if the determining module 309 determines that the first target application that fails to match has an associated application, close the first target application that fails the matching and the associated application.
  • the control module 304 closes the first target application and the associated application that fail to match, thereby preventing the associated application from running in the background, and not only effectively controlling the background running.
  • the background application greatly improves the running speed of the electronic device, reduces the power consumption of the electronic device, and can greatly improve the security performance of the electronic device.
  • control module 304 is further configured to: if the determining module 309 determines that the first target application that fails to match does not have an associated application, placing the first target application that fails the matching in the buffer and freezing the same .
  • the control module 304 places the application in the buffer of the electronic device and temporarily freezes it, thereby improving the running speed of the electronic device and saving the electronic device. Under the premise of the battery power of the device, it is also convenient for the user to start the first target application placed in the buffer within a preset time. If the first target application placed in the buffer is not activated by the touch operation within a preset time, the first target application placed in the buffer is closed.
  • FIG. 13 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure.
  • the electronic device 400 includes a processor 401 and a memory 402.
  • the processor 401 is electrically connected to the memory 402.
  • the processor 401 is a control center of the electronic device 400, and connects various parts of the entire electronic device 400 using various interfaces and lines, by running or loading an application stored in the memory 402, and calling data stored in the memory 402, executing The various functions and processing data of the electronic device 400 enable overall monitoring of the electronic device 400.
  • the processor 401 in the electronic device 400 loads the instructions corresponding to the process of one or more applications into the memory 402 according to the following steps, and is stored and stored in the memory 402 by the processor 401.
  • the application thus implementing various functions:
  • the first target application in the application launched by the touch operation is excluded from the background application.
  • the processor is further configured to:
  • the first target application that fails to match has an associated application, the first target application that fails to match and the associated application are closed;
  • the first target application that fails to match does not have an associated application, the first target application that fails to match is placed in the buffer and frozen.
  • the processor is further configured to:
  • the first target application placed in the buffer When the first target application placed in the buffer is not activated by the touch operation within a preset time, the first target application placed in the buffer is closed.
  • the processor is further configured to:
  • Memory 402 can be used to store applications and data.
  • the application stored in the memory 402 contains instructions executable in the processor 401.
  • Applications can form various functional modules.
  • the processor 401 executes various functional applications and data processing by running an application stored in the memory 402.
  • FIG. 14 is another schematic structural diagram of an electronic device.
  • the electronic device 400 further includes: a radio frequency circuit 403, a display screen 404, a control circuit 405, an input unit 406, and an audio circuit 407. Sensor 408 and power supply 409.
  • the processor 401 is electrically connected to the radio frequency circuit 403, the display screen 404, the control circuit 405, the input unit 406, the audio circuit 407, the sensor 408, and the power source 409, respectively.
  • the radio frequency circuit 403 is configured to transceive radio frequency signals to communicate with a server or other electronic device through a wireless communication network.
  • the display screen 404 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 terminal, which can be composed of images, text, icons, video, and any combination thereof.
  • the control circuit 405 is electrically connected to the display screen 404 for controlling the display screen 404 to display information.
  • the input unit 406 can be configured to receive input digits, character information, or user characteristic information (eg, fingerprints), and to generate keyboard, mouse, joystick, optical, or trackball signal inputs related to user settings and function controls.
  • user characteristic information eg, fingerprints
  • the audio circuit 407 can provide an audio interface between the user and the terminal through a speaker and a microphone.
  • Sensor 408 is used to collect external environmental information.
  • Sensor 408 can include one or more of ambient brightness sensors, acceleration sensors, gyroscopes, and the like.
  • Power source 409 is used to power various components of electronic device 400.
  • the power supply 409 can be logically coupled to the processor 401 through a power management system to enable functions such as managing charging, discharging, and power management through the power management system.
  • the electronic device 400 may further include a camera, a Bluetooth module, and the like, and details are not described herein.
  • the electronic device in the embodiment of the present application can close some background applications that do not need to run in the background, effectively control the background application running in the background, reduce the power consumption of the electronic device, and improve the running speed of the electronic device.
  • the embodiment of the present application further provides a storage medium, where the storage medium stores a plurality of instructions, and the instructions are adapted to be loaded by a processor to execute the application management method described in any one of the foregoing embodiments.
  • the medium may include, but is not limited to, a read only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • User Interface Of Digital Computer (AREA)
  • Telephone Function (AREA)

Abstract

本申请公开了一种应用管控方法、装置及电子设备，应用管控方法包括：确定通过触控操作启动的应用以及确定当前后台运行的后台应用；将后台应用与通过触控操作启动的应用进行匹配；当后台应用中存在匹配失败的第一目标应用时，关闭后台应用中排除通过触控操作启动的应用中的第一目标应用。

Description

应用管控方法、装置及电子设备
本申请要求于2017年07月31日提交中国专利局、申请号为201710643059.6、申请名称为“应用管控方法、装置、存储介质及电子设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及移动设备技术领域，具体涉及一种应用管控方法、装置及电子设备。
背景技术
随着电子设备技术的快速发展，电子设备的功能越来越多。比如，电子设备端通过各种应用实现通信、观看视频、听音乐等。具体比如，使用即时通讯软件进行视频聊天。通常，通过运行电子设备端的应用实现。
发明内容
本申请实施例提供一种应用管控方法、装置及电子设备，可以节省电子设备电量、提升电子设备的运行速度。
第一方面，本申请实施例提供一种应用管控方法，应用于电子设备中，所述应用管控方法包括：
确定通过触控操作启动的应用；
确定当前后台运行的后台应用；
将所述后台应用与所述通过触控操作启动的应用进行匹配；
当所述后台应用中存在匹配失败的第一目标应用时，关闭所述后台应用中排除所述通过触控操作启动的应用中的第一目标应用。
第二方面，本申请实施例还提供一种应用管控装置，所述应用管控装置包括：
第一获取模块，用于确定通过触控操作启动的应用；
第二获取模块，用于确定当前后台运行的后台应用；
匹配模块，用于将所述后台应用与所述通过触控操作启动的应用进行匹配；
管控模块，用于当所述后台应用中存在匹配失败的第一目标应用时，关闭所述后台应用中排除所述通过触控操作启动的应用中的第一目标应用。
申请第三方面，本申请实施例还提供一种电子设备，所述电子设备包括处理器和存储器，所述处理器和所述存储器电性连接，所述存储器用于存储指令和数据，所述处理器用于执行一下步骤：
确定通过触控操作启动的应用；
确定当前后台运行的后台应用；
将所述后台应用与所述通过触控操作启动的应用进行匹配；
当所述后台应用中存在匹配失败的第一目标应用时，关闭所述后台应用中排除所述通过触控操作启动的应用中的第一目标应用。
附图说明
下面结合附图，通过对本申请的具体实施方式详细描述，将使本申请的技术方案及其它有益效果显而易见。
图1为本申请实施例提供的应用管控方法的场景示意图。
图2为本申请实施例提供的应用管控方法的流程示意图。
图3为本申请实施例提供的电子设备的一个显示界面示意图。
图4为本申请实施例提供的第一列表的一种示意图。
图5为本申请实施例提供的第一列表的另一种示意图。
图6为本申请实施例提供的应用管控方法的另一流程示意图。
图7为本申请实施例提供的应用管控方法的另一流程示意图。
图8为本申请实施例提供的应用管控装置的结构示意图。
图9为本申请实施例提供的应用管控装置的另一结构示意图。
图10为本申请实施例提供的第一获取模块的结构示意图。
图11为本申请实施例提供的第二获取模块的结构示意图。
图12为本申请实施例提供的应用管控装置的另一结构示意图。
图13为本申请实施例提供的电子设备的结构示意图。
图14为本申请实施例提供的电子设备的另一结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述。本申请中的术语“第一”和“第二”等是用于区别不同对象，而不是用于描述特定顺序。
本申请实施例提供了一种应用管控方法、装置及电子设备。
请参阅图1，该图1为本申请实施例提供的应用管控方法的场景示意图。该场景可以包括电子设备10，该电子设备10可以包括平板、PC(个人计算机，Personal Computer)、手机等，该电子设备10具备储存单元并安装有微处理器而具有运算能力。
该电子设备10以手机为例进行说明，手机10可以从本地确定当前后台运行的后台应用，在此定义为第一应用11，该第一应用11可以包括多个，比如后台运行的爱奇艺、微信、QQ、百度浏览器、360安全卫士等。该第一应用11为当前后台运行的后台应用。以及手机10可以从本地确定通过触控操作启动的应用，在此定义为第二应用12，该第二应用12可以包括多个，比如思博圈、微信、QQ、微博、QQ邮箱等。该第二应用12可以是手机中所有通过触控操作启动的应用。也可以是手机中的应用在预设时间段内通过触控操作启动的应用，比如，手机在一个月内通过触控操作启动的应用。手机10确定到第一应用11和第二应用12后，将第一应用11与第二应用12进行匹配，当存在匹配失败的第一应用11时，关闭匹配失败的第一应用11，可以关闭一些无需后台运行的后台应用，有效管控后台运行的后台应用，减少电子设备中电池的耗电量，提升电子设备的运行速度。
需要说明的是，该匹配失败的第一应用11仅存在于当前后台运行的后台应用中，而不存在于通过触控操作启动的应用，即匹配失败的第一应用11排除于通过触控操作启动的应用外。
该场景可以包括应用管控装置300，该应用管控装置300具体可以集成在该电子设备10中。该应用管控装置300主要用于确定通过触控操作启动的应用以及确定当前后台运行的后台应用；然后，将后台应用与通过触控操作启动的应用进行匹配；当后台应用中存在匹配失败的第一目标应用时，关闭后台应用中排除通过触控操作启动的应用中的第一目标应用。
在一些实施例中，将从应用管控装置的角度进行描述，该应用管控装置具体可以集成在平板、PC、手机等具备储存单元并安装有微处理器而具有运算能力的电子设备中。
一种应用管控方法，应用于电子设备中，其包括：
确定通过触控操作启动的应用；
确定当前后台运行的后台应用；
将所述后台应用与所述通过触控操作启动的应用进行匹配；
当所述后台应用中存在匹配失败的第一目标应用时，关闭所述后台应用中排除所述通过触控操作启动的应用中的第一目标应用。
在一些实施例中，所述当所述后台应用中存在匹配失败的第一目标应用时，关闭所述后台应用中排除所述通过触控操作启动的应用中的第一目标应用的步骤，包括：
当所述后台应用中存在匹配失败的第一目标应用时，判断所述匹配失败的第一目标应用是否存在关联应用，其中所述关联应用与所述匹配失败的第一目标应用具有关联关系，与所述第一目标应用具有关联关系的关联应用跟随所述第一目标应用的启动而启动；
若所述匹配失败的第一目标应用存在关联应用，则关闭所述匹配失败的第一目标应用以及关联应用；
若所述匹配失败的第一目标应用不存在关联应用，则将所述匹配失败的第一目标应用放置于缓存器中，并将其冻结。
在一些实施例中，所述将所述匹配失败的第一目标应用放置于缓存器中，并将其冻结的步骤，包括：
当放置于所述缓存器中的第一目标应用在预设时间内未通过触控操作启动，则关闭放置于所述缓存器中的第一目标应用。
在一些实施例中，所述确定通过触控操作启动的应用的步骤之前，还包括：
监控电子设备的显示界面中应用的操作事件；
统计所有通过触控操作启动的应用。
在一些实施例中，所述统计所有通过触控操作启动的应用的步骤之后，还包括：
获取所述所有通过触控操作启动的应用的标识，其中所述标识与所述所有通过触控操作启动的应用一一对应；
根据所述标识生成第一列表；
所述确定通过触控操作启动的应用的步骤，包括：
获取所述第一列表；
根据所述第一列表中的标识确定与所述标识对应的应用。
在一些实施例中，所述第一列表中的标识按照预设规则形成具有优先等级的排列方式。
在一些实施例中，所述确定当前后台运行的后台应用的步骤，包括：
获取与所述后台应用一一对应的标识；
根据所述与所述后台应用一一对应的标识生成第二列表；
所述将所述后台应用与所述通过触控操作启动的应用进行匹配的步骤，包括：
将所述第二列表中的标识与所述第一列表中的标识进行比对。
在一些实施例中，所述第二列表中的标识按照预设规则形成具有优先等级的排列方式。
在一些实施例中，所述当所述后台应用中存在匹配失败的第一目标应用时，关闭所述后台应用中排除所述通过触控操作启动的应用中的第一目标应用的步骤，包括：
当第一目标应用为多个时，将所述第一目标应用按照预设规则形成具有优先等级的排列方式，并关闭优先等级低于预设阈值的第一目标应用。
在一些实施例中，所述当所述后台应用中存在匹配失败的第一目标应用时，关闭所述后台应用中排除所述通过触控操作启动的应用中的第一目标应用的步骤，包括：
当后台运行的后台应用中存在匹配失败的第一目标应用，发出提示信息以提示所述第一目标应用为异常应用。
请参阅图2，图2为本申请实施例提供的应用管控方法的流程示意图。该应用管控方法可以包括：
在步骤S101中，确定电子设备中通过触控操作启动的应用。
其中，电子设备中通过触控操作启动的应用，主要是电子设备显示界面中通过点击启动的应用。该电子设备中通过触控操作启动的应用可以简称为第二应用，其可以包括多个，具体可以参阅以上内容，在此不再赘述。
其中，该电子设备可以从其本地直接确定通过触控操作启动的应用。具体的，请参阅图3，图3为本申请实施例提供的电子设备的一个显示界面示意图。该电子设备10的显示界 面13中显示有多个应用，该显示界面13中的所有应用均通过触控操作启动过，比如应用思博圈12通过触控操作启动。
在一些实施例中，该通过触控操作启动的应用可以是电子设备中所有通过触控操作启动的应用。电子设备可以一直监控其显示界面中应用的触控事件，并统计显示界面中所有通过触控操作启动的应用。具体的，从电子设备监控其显示界面开始，每当显示界面中的应用第一次通过触控操作启动，统计该第一次通过触控操作启动的应用，可以将统计结果存储于电子设备的存储器中，至电子设备确定通过触控操作启动的所有应用止，电子设备可以直接从存储器中获取已经存储的统计结果。
需要说明的是，该通过触控操作启动的应用也可以是在预设时间段内通过触控操作启动的应用。该预设时间段可以为一天、一个星期、一个月、两个月等。比如，电子设备在一个星期内通过触控操作启动的应用。
在一些实施例中，可以根据以上统计结果获取所有通过触控操作启动的应用的标识。其中该标识与所有通过触控操作启动的应用一一对应，比如应用思博圈所对应的标识为“思博圈”，具体可以参阅图3。根据各通过触控操作启动的应用所对应的标识生成第一列表，所有通过触控操作启动的应用对应的标识均在第一列表中。具体的，请参阅图4，图4为本申请实施例提供的第一列表的一种示意图，图4中仅示出第一列表中的部分应用标识。
在一些实施例中，第一列表14中应用所对应的标识按照不同的优先级进行排列。可以按照第一列表14中应用在预设时间内的使用时长、使用频率、耗电量等中的至少一个形成不同的优先级，以形成具有优先等级的排列方式。比如：按照在预设时间内的使用时长形成不同的优先级，应用A、应用B和应用C的使用时长大于第一时长，应用A、应用B和应用C形成第一优先级141，该第一优先等级141为最高优先级。应用D和应用E形成第二优先级142；应用F和应用G形成第三优先级143；应用H形成第四优先级144；应用I和应用J形成第五优先级145；应用K形成第六优先级146；应用L形成第七优先级147，该第七优先级147为最低优先级。第一优先级141、第二优先级142、第三优先级143、第四优先级144、第五优先级145、第六优先级146及第七优先级147的优先等级依次降低。需要说明的是，本申请实施例各应用的优先等级并不限于七个，还可以有更多或更少。
还需要说明的是，本申请实施例各应用的优先等级也可以设置不相同。请参阅图5，图5为本申请实施例提供的第一列表的另一种示意图。在第一列表15中，各应用按照使用时长的长短直接形成优先等级，使用时长最长的应用优先等级设置最高，然后优先等级根据使用时长的减少优先等级逐渐降低。
在一些实施例中，图4和图5中所示出的应用的优先级排列方式也可以根据使用频率的多少、耗电量的多少形成，具体可以参阅图4和图5，在此不再赘述。
在一些实施例中，确定电子设备中通过触控操作启动的应用具体可以先获取第一列表，然后根据第一列表中的标识确定与标识对应的应用。
在步骤S102中，电子设备确定当前后台运行的后台应用。
该电子设备可以直接从其本地确定当前后台运行的后台应用，其可以是多个，可以将当前后台运行的后台应用简称为第一应用，具有可以参阅以上内容，在此不再赘述。
在一些实施例中，电子设备确定当前后台运行的后台应用具体可以先获取与后台运行的后台应用一一对应的标识，然后根据该标识生成第二列表。该第二列表中应用所对应的标识也可以按照不同的优先级进行排列。可以按照第二列表中应用在预设时间内的使用时长、使用频率、耗电量等中的至少一个形成不同的优先级，以形成具有优先等级的排列方式。具体的可以参阅第一列表，在此不再赘述。
在步骤S103中，将后台运行的后台应用与通过触控操作启动的应用进行匹配。
在一些实施例中，可以将后台运行的后台应用与通过触控操作启动的应用进行一一比 对，具体的，将第二列表中的标识与第一列表中的标识进行比对，并形成比对结果，或者说是匹配结果。在比对过程中，若第二列表中的标识未能够在第一列表中匹配到，则匹配失败，表明第一列表中不存在该标识；若第二列表中的标识能够在第一列表中匹配到，则匹配成功，表明第一列表中存在该标识。
在步骤S104中，当后台运行的后台应用中存在匹配失败的第一目标应用时，关闭后台应用中排除通过触控操作启动的应用中的第一目标应用。
本申请实施例中，将后台运行的后台应用和通过触控操作启动的应用匹配过程中，当后台运行的后台应用在通过触控操作启动的应用中未匹配到对应的应用时，也就是后台运行的后台应用存在匹配失败的应用，在此可以定义为第一目标应用，该第一目标应用可以为一个，也可以为多个，关闭匹配失败的应用，也就是关闭匹配失败的第一目标应用。从而，可以减少后台运行的后台应用的个数，有效管控后台运行的后台应用，提升其它未关闭的应用的运行速度，节省电子设备电池的电量。
在一些实施例中，当第一目标应用为多个时，本申请实施例也可以将第一目标应用按照在预设时间内的使用时长、使用频率、耗电量等中的至少一个形成优先级，形成具有优先等级的排列方式，而仅仅关闭一些优先等级较低的第一目标应用。需要说明的是，该第一目标应用的优先级形成方式可以参阅以上内容，在此不再对优先级的形成方式进行赘述。
在一些实施例中，当后台运行的后台应用中存在匹配失败的第一目标应用，则发出提示信息以提示第一目标应用为异常应用，从而便于用户了解到电子设备中存在无需后台运行的后台应用或后台恶意运行的后台应用，以便用户进行管控，可以有效防止后台应用进行恶意行为。该提示信息可以为提示消息、提示语音等等。
需要说明的是，该匹配失败的第一目标应用仅存在于当前后台运行的后台应用中，而不存在于通过触控操作启动的应用，即匹配失败的第一目标应用排除于通过触控操作启动的应用外。
请参阅图6，图6为本申请实施例提供的应用管控方法的另一流程示意图。该应用管控方法还可以包括步骤S105。
在步骤S105中，当后台运行的后台应用中存在匹配成功的应用时，正常运行匹配成功的应用。
本申请实施例中，将后台运行的后台应用和通过触控操作启动的应用匹配过程中，当后台运行的后台应用在通过触控操作启动的应用中匹配到对应的应用时，也就是后台运行的后台应用存在匹配成功的应用，在此可以定义为第二目标应用，该第二目标应用可以为一个，也可以为多个，正常运行匹配成功的应用，也就是不对第二目标应用进行管控。从而，可以确保用户曾经使用过的应用或者说是安全应用可以正常运行。在有效管控后台运行的后台应用，提升其它未关闭的应用的运行速度，节省电子设备电池的电量的同时，提高安全性能。
需要说明的是，匹配成功的应用不仅存在于当前后台运行的后台应用中，而且存在于通过触控操作启动的应用中。
请参阅图7，图7为本申请实施例提供的应用管控方法的另一流程示意图。该应用管控方法包括以下步骤：
在步骤S201中，确定电子设备中通过触控操作启动的应用。
其中，电子设备中通过触控操作启动的应用，主要是电子设备显示界面中通过触控操作启动的应用。该电子设备中通过触控操作启动的应用可以简称为第二应用，其可以包括多个，具体可以参阅以上内容，在此不再赘述。
其中，该电子设备可以从其本地直接确定通过触控操作启动的应用。具体的，请参阅图3，该电子设备10的显示界面13中显示有多个应用，该显示界面13中的所有应用均通过触 控操作启动过，比如应用思博圈12通过触控操作启动。
在一些实施例中，该通过触控操作启动的应用可以是电子设备中所有通过触控操作启动的应用。电子设备可以一直监控其显示界面中应用的触控事件，并统计显示界面中所有通过触控操作启动的应用。具体的，从电子设备监控其显示界面开始，每当显示界面中的应用第一次通过触控操作启动，统计该第一次通过触控操作启动的应用，可以将统计结果存储于电子设备的存储器中，至电子设备确定通过触控操作启动的所有应用止，电子设备可以直接从存储器中获取已经存储的统计结果。
需要说明的是，该通过触控操作启动的应用也可以是在预设时间段内通过触控操作启动的应用。该预设时间段可以为一天、一个星期、一个月、两个月等。比如，电子设备在一个星期内通过触控操作启动的应用。
在一些实施例中，可以根据以上统计结果获取所有通过触控操作启动的应用的标识。其中该标识与所有通过触控操作启动的应用一一对应，比如应用思博圈所对应的标识为“思博圈”，具体可以参阅图3。根据各通过触控操作启动的应用所对应的标识生成第一列表，所有通过触控操作启动的应用对应的标识均在第一列表中。具体的，请参阅图4。
在一些实施例中，第一列表14中应用所对应的标识按照不同的优先级进行排列。可以按照第一列表14中应用在预设时间内的使用时长、使用频率、耗电量等中的至少一个形成不同的优先级，以形成具有优先等级的排列方式。比如：按照在预设时间内的使用时长形成不同的优先级，应用A、应用B和应用C的使用时长大于第一时长，应用A、应用B和应用C形成第一优先级141，该第一优先等级141为最高优先级。应用D和应用E形成第二优先级142；应用F和应用G形成第三优先级143；应用H形成第四优先级144；应用I和应用J形成第五优先级145；应用K形成第六优先级146；应用L形成第七优先级147，该第七优先级147为最低优先级。第一优先级141、第二优先级142、第三优先级143、第四优先级144、第五优先级145、第六优先级146及第七优先级147的优先等级依次降低。需要说明的是，本申请实施例各应用的优先等级并不限于七个，还可以有更多或更少。
还需要说明的是，本申请实施例各应用的优先等级也可以设置不相同。请参阅图5，在第一列表15中，各应用按照使用时长的长短直接形成优先等级，使用时长最长的应用优先等级设置最高，然后优先等级根据使用时长的减少优先等级逐渐降低。
在一些实施例中，图4和图5中所示出的应用的优先级排列方式也可以根据使用频率的多少、耗电量的多少形成，具体可以参阅图4和图5，在此不再赘述。
在一些实施例中，确定电子设备中通过触控操作启动的应用具体可以先获取第一列表，然后根据第一列表中的标识确定与标识对应的应用。
在步骤S202中，电子设备确定当前后台运行的后台应用。
该电子设备可以直接从其本地确定当前后台运行的后台应用，其可以是多个，可以将当前后台运行的后台应用简称为第一应用，具有可以参阅以上内容，在此不再赘述。
在一些实施例中，电子设备确定当前后台运行的后台应用具体可以先获取与后台运行的后台应用一一对应的标识，然后根据标识生成第二列表。该第二列表中应用所对应的标识也可以按照不同的优先级进行排列。可以按照第二列表中应用在预设时间内的使用时长、使用频率、耗电量等中的至少一个形成不同的优先级，以形成具有优先等级的排列方式。具体的可以参阅第一列表，在此不再赘述。
在步骤S203中，将后台运行的后台应用与通过触控操作启动的应用进行匹配。
在一些实施例中，可以将后台运行的后台应用与通过触控操作启动的应用进行一一比对，具体的，将第二列表中的标识与第一列表中的标识进行比对，并形成比对结果，或者说是匹配结果。在比对过程中，若第二列表中的标识未能够在第一列表中匹配到，则匹配失败，表明第一列表中不存在该标识；若第二列表中的标识能够在第一列表中匹配到，则 匹配成功，表明第一列表中存在该标识。
在步骤S204中，当后台运行的后台应用中存在匹配失败的第一目标应用时，判断匹配失败的第一目标应用是否存在关联应用。
其中关联应用与匹配失败的第一目标应用具有关联关系。比如应用1被启动，则应用2根据应用1的启动而启动，然而，应用2并非用户所启动的应用，用户也无需应用2启动，无需应用2在后台运行。尤其是一些恶意应用，常常相互具有关联关系，或者说相互进行绑定、相互关联，一旦其中一个被启动，则与其具有关联关系的应用均可以自动启动，并在后台运行，而后台运行的一些无用的应用或者恶意应用，用户往往无法及时察觉，给用户的使用带来极大的困扰。本申请实施例中，若判断匹配失败的第一目标应用存在关联应用，则进入步骤S205。若判断匹配失败的第一目标应用不存在关联应用，则进入步骤S206。
在步骤S205中，若匹配失败的第一目标应用存在关联应用，则关闭匹配失败的第一目标应用以及关联应用。
本申请实施例中，若匹配失败的第一目标应用存在关联应用，则关闭匹配失败的第一目标应用以及关联应用，从而避免关联应用在后台运行，不仅可以有效管控后台运行的后台应用，大大提高电子设备的运行速度，降低电子设备的耗电量，而且还可以大大提高电子设备的安全性能。
本申请实施例中，将后台运行的后台应用和通过触控操作启动的应用匹配过程中，当后台运行的后台应用在通过触控操作启动的应用中未匹配到对应的应用时，也就是后台运行的后台应用存在匹配失败的应用，在此可以定义为第一目标应用，该第一目标应用可以为一个，也可以为多个，关闭匹配失败的应用，也就是关闭匹配失败的第一目标应用。从而，可以减少后台运行的后台应用的个数，有效管控后台运行的后台应用，提升其它未关闭的应用的运行速度，节省电子设备电池的电量。
在一些实施例中，当第一目标应用为多个时，本申请实施例也可以将第一目标应用按照在预设时间内的使用时长、使用频率、耗电量等中的至少一个形成优先级，形成具有优先等级的排列方式，而仅仅关闭一些优先等级较低的第一目标应用。需要说明的是，该第一目标应用的优先级形成方式可以参阅以上内容，在此不再对优先级的形成方式进行赘述。
在一些实施例中，当后台运行的后台应用中存在匹配失败的匹配失败的应用，则发出提示信息以提示第一目标应用为异常应用，从而便于用户了解到电子设备中存在无需后台运行的后台应用或后台恶意运行的应用，以便用户进行管控，可以有效防止应用进行恶意行为。该提示信息可以为提示消息、提示语音等等。
在步骤S206中，若匹配失败的第一目标应用不存在关联应用，则将匹配失败的第一目标应用放置于缓存器中，并将其冻结。
若该匹配失败的第一目标应用不是恶意应用，则将该第一目标应用放置于电子设备的缓存器中，并将其暂时冻结，在提高电子设备运行速度，节省电子设备电池的电量的前提下，还方便用户在预设时间内启动放置于缓存器中的第一目标应用。若放置于缓存器中的第一目标应用在预设时间内未通过触控操作启动，则关闭放置于缓存器中的第一目标应用。
在步骤S207中，当后台运行的后台应用中存在匹配成功的应用时，正常运行匹配成功的应用。
本申请实施例中，将后台运行的后台应用和通过触控操作启动的应用匹配过程中，当后台运行的后台应用在通过触控操作启动的应用中匹配到对应的周期同步应用时，也就是后台运行的后台应用存在匹配成功的应用，在此可以定义为第二目标应用，该第二目标应用可以为一个，也可以为多个，正常运行匹配成功的应用，也就是不对第二目标应用进行管控。从而，可以确保用户曾经使用过的应用或者说是安全应用可以正常运行。在有效管控后台运行的后台应用，提升其它未关闭的应用的运行速度，节省电子设备电池的电量的 同时，提高安全性能。
需要说明的是，匹配成功的应用不仅存在于当前后台运行的后台应用中，而且存在于通过触控操作启动的应用中。
为便于更好的实施本申请实施例提供的应用管控方法，本申请实施例还提供一种基于应用管控方法的装置。其中名词的含义与上述应用管控方法中的相同，具体实现细节可以参考方法实施例中的说明。
一种应用管控装置，应用于电子设备中，其包括：
第一获取模块，用于确定通过触控操作启动的应用；
第二获取模块，用于确定当前后台运行的后台应用；
匹配模块，用于将所述后台应用与所述通过触控操作启动的应用进行匹配；
管控模块，用于当所述后台应用中存在匹配失败的第一目标应用时，关闭所述后台应用中排除所述通过触控操作启动的应用中的第一目标应用。
在一些实施例中，所述应用管控装置还包括判断模块；
所述判断模块，用于当所述后台应用中存在匹配失败的第一目标应用时，判断所述匹配失败的第一目标应用是否存在关联应用，其中所述关联应用与所述匹配失败的第一目标应用具有关联关系；
所述管控模块，还用于若所述匹配失败的第一目标应用存在关联应用，则关闭所述匹配失败的第一目标应用以及关联应用；
所述管控模块，还用于若所述匹配失败的第一目标应用不存在关联应用，则将所述匹配失败的第一目标应用放置于缓存器中，并将其冻结。
在一些实施例中，所述管控模块，还用于当放置于所述缓存器中的第一目标应用在预设时间内未通过触控操作启动，则关闭放置于所述缓存器中的第一目标应用。
在一些实施例中，所述应用管控装置还包括：
监控模块，用于监控电子设备的显示界面中应用的触控事件；
统计模块，用于统计所有通过触控操作启动的应用。
在一些实施例中，所述应用管控装置还包括第三获取模块和第一生成模块，所述第一获取模块包括第一获取主模块和第一获取子模块；
所述第三获取模块，用于获取所述所有通过触控操作启动的应用的标识，其中所述标识与所述所有通过触控操作启动的应用一一对应；
所述第一生成模块，用于根据所述标识生成第一列表；
所述第一获取主模块，用于获取所述第一列表；
所述第一获取子模块，用于根据所述第一列表中的标识确定与所述标识对应的应用。
在一些实施例中，所述第二获取模块包括第四获取模块和第二生成模块：
所述第四获取模块，用于获取与所述后台应用一一对应的标识；
所述第二生成模块，用于根据所述与所述后台应用一一对应的标识生成第二列表；
所述匹配模块，还用于将所述第二列表中的标识与所述第一列表中的标识进行比对。
请参阅图8，图8为本申请实施例提供的应用管控装置的结构示意图。本申请实施例应用管控装置300包括有第一获取模块301、第二获取模块302、匹配模块303和管控模块304。
其中，第一获取模块301，用于确定电子设备中通过触控操作启动的应用。
其中，电子设备中通过触控操作启动的应用，主要是电子设备显示界面中通过触控操作的应用。该电子设备中通过触控操作启动的应用可以简称为第二应用，其可以包括多个，具体可以参阅以上内容，在此不再赘述。
其中，该第一获取模块301可以从电子设备本地直接确定通过触控操作启动的应用。具体的，请参阅图3，该电子设备10的显示界面13中显示有多个应用，该显示界面13中的所 有应用均通过触控操作启动过，比如应用思博圈12通过触控操作启动。
在一些实施例中，请参阅图9，图9为本申请实施例提供的应用管控装置的另一结构示意图。该应用管控装置300还可以包括监控模块305、统计模块306、第三获取模块307和第一生成模块308。
其中，监控模块305，用于监控电子设备的显示界面中应用的触控事件。
其中，统计模块306，用于统计所有通过触控操作启动的应用。
其中，第三获取模块307，用于获取所有通过触控操作启动的应用的标识，其中该标识与所有通过触控操作启动的应用一一对应。
其中，第一生成模块308，用于根据标识生成第一列表。
在一些实施例中，该通过触控操作启动的应用可以是电子设备中所有通过触控操作启动的应用。监控模块305可以一直监控其显示界面中应用的触控事件，并统计显示界面中所有通过触控操作启动的应用。具体的，从监控模块305监控电子设备显示界面开始，每当显示界面中的应用第一次通过触控操作启动，统计模块306统计该第一次通过触控操作启动的应用，可以将统计结果存储于电子设备的存储器中，至电子设备确定通过触控操作启动的所有应用止，第一获取模块301可以直接从存储器中获取已经存储的统计结果。
需要说明的是，该通过触控操作启动的应用也可以是在预设时间段内通过触控操作启动的应用。该预设时间段可以为一天、一个星期、一个月、两个月等。比如，电子设备在一个星期内通过触控操作启动的应用。
在一些实施例中，第三获取模块307可以根据以上统计结果获取所有通过触控操作启动的应用的标识。其中该标识与所有通过触控操作启动的应用一一对应，比如应用思博圈所对应的标识为“思博圈”，具体可以参阅图3。第一生成模块308根据各通过触控操作启动的应用所对应的标识生成第一列表，所有通过触控操作启动的应用对应的标识均在第一列表中。具体的，请参阅图4。
在一些实施例中，第一列表14中应用所对应的标识按照不同的优先级进行排列。可以按照第一列表14中应用在预设时间内的使用时长、使用频率、耗电量等中的至少一个形成不同的优先级，以形成具有优先等级的排列方式。比如：按照在预设时间内的使用时长形成不同的优先级，应用A、应用B和应用C的使用时长大于第一时长，应用A、应用B和应用C形成第一优先级141，该第一优先等级141为最高优先级。应用D和应用E形成第二优先级142；应用F和应用G形成第三优先级143；应用H形成第四优先级144；应用I和应用J形成第五优先级145；应用K形成第六优先级146；应用L形成第七优先级147，该第七优先级147为最低优先级。第一优先级141、第二优先级142、第三优先级143、第四优先级144、第五优先级145、第六优先级146及第七优先级147的优先等级依次降低。需要说明的是，本申请实施例各应用的优先等级并不限于七个，还可以有更多或更少。
还需要说明的是，本申请实施例各应用的优先等级也可以设置不相同。请参阅图5，在第一列表15中，各应用按照使用时长的长短直接形成优先等级，使用时长最长的应用优先等级设置最高，然后优先等级根据使用时长的减少优先等级逐渐降低。
在一些实施例中，图4和图5中所示出的应用的优先级排列方式也可以根据使用频率的多少、耗电量的多少形成，具体可以参阅图4和图5，在此不再赘述。
在一些实施例中，请参阅图10，图10为本申请实施例提供的第一获取模块的结构示意图。第一获取模块301包括第一获取主模块3011和第一获取子模块3012。
其中，第一获取主模块3011，用于获取所述第一列表。
其中，第一获取子模块3012，用于根据第一列表中的标识确定与标识对应的应用。
具体的，第一获取模块301确定电子设备中通过触控操作启动的应用具体可以先通过第一获取主模块3011获取第一列表，然后通过第一获取子模块3012根据第一列表中的标识 确定与标识对应的应用。
其中，第二获取模块302，用于确定当前后台运行的后台应用。
该第二获取模块302可以直接从电子设备本地确定当前后台运行的后台应用，其可以是多个，可以将当前后台运行的后台应用简称为第一应用，具有可以参阅以上内容，在此不再赘述。
在一些实施例中，请参阅图11，图11为本申请实施例提供的第二获取模块的结构示意图。该第二获取模块302包括第四获取模块3021和第二生成模块3022。
其中，第四获取模块3021，用于获取与所述后台运行的后台应用一一对应的标识。
其中，第二生成模块3022，用于根据该标识生成第二列表。
具体的，第二获取模块302确定当前后台运行的后台应用具体可以通过第四获取模块3021先获取与后台运行的后台应用一一对应的标识，然后通过第二生成模块3022根据该标识生成第二列表。该第二列表中应用所对应的标识也可以按照不同的优先级进行排列。可以按照第二列表中应用在预设时间内的使用时长、使用频率、耗电量等中的至少一个形成不同的优先级，以形成具有优先等级的排列方式。具体的可以参阅第一列表，在此不再赘述。
其中，匹配模块203，用于将后台运行的后台应用与通过触控操作启动的应用进行匹配。
在一些实施例中，匹配模块203可以将后台运行的后台应用与通过触控操作启动的应用进行一一比对，具体的，将第二列表中的标识与第一列表中的标识进行比对，并形成比对结果，或者说是匹配结果。在比对过程中，若第二列表中的标识未能够在第一列表中匹配到，则匹配失败，表明第一列表中不存在该标识；若第二列表中的标识能够在第一列表中匹配到，则匹配成功，表明第一列表中存在该标识。
其中，管控模块304，用于当后台运行的后台应用中存在匹配失败的第一目标应用时，关闭所述后台应用中排除通过触控操作启动的应用中的第一目标应用。
本申请实施例中，匹配模块203将后台运行的后台应用和通过触控操作启动的应用匹配过程中，当后台运行的后台应用在通过触控操作启动的应用中未匹配到对应的应用时，也就是后台运行的后台应用存在匹配失败的应用，在此可以定义为第一目标应用，该第一目标应用可以为一个，也可以为多个，管控模块304关闭匹配失败的应用，也就是关闭匹配失败的第一目标应用。从而，可以减少后台运行的后台应用的个数，有效管控后台运行的后台应用，提升其它未关闭的应用的运行速度，节省电子设备电池的电量。
在一些实施例中，当第一目标应用为多个时，本申请实施例也可以将第一目标应用按照在预设时间内的使用时长、使用频率、耗电量等中的至少一个形成优先级，形成具有优先等级的排列方式，而仅仅关闭一些优先等级较低的第一目标应用。需要说明的是，该第一目标应用的优先级形成方式可以参阅以上内容，在此不再对优先级的形成方式进行赘述。
在一些实施例中，当后台运行的后台应用中存在匹配失败的第一目标应用，管控模块304则发出提示信息以提示第一目标应用为异常应用，从而便于用户了解到电子设备中存在无需后台运行的后台应用或后台恶意运行的后台应用，以便用户进行管控，可以有效防止应用进行恶意行为。该提示信息可以为提示消息、提示语音等等。
需要说明的是，该匹配失败的第一目标应用仅存在于当前后台运行的后台应用中，而不存在于通过触控操作启动的应用，即匹配失败的第一目标应用排除于通过触控操作启动的应用外。
该管控模块304，还用于当后台运行的后台应用中存在匹配成功的应用时，正常运行匹配成功的应用。
本申请实施例中，匹配模块303将后台运行的后台应用和通过触控操作启动的应用匹 配过程中，当后台运行的后台应用在通过触控操作启动的应用中匹配到对应的应用时，也就是后台运行的后台应用存在匹配成功的应用，在此可以定义为第二目标应用，该第二目标应用可以为一个，也可以为多个，管控模块304正常运行匹配成功的应用，也就是不对第二目标应用进行管控。从而，可以确保用户曾经使用过的应用或者说是安全应用可以正常运行。在有效管控后台运行的后台应用，提升其它未关闭的应用的运行速度，节省电子设备电池的电量的同时，提高安全性能。
需要说明的是，匹配成功的应用不仅存在于当前后台运行的后台应用中，而且存在于通过触控操作启动的应用中。
在一些实施例中，请参阅图12，图12为本申请实施例提供的应用管控装置的另一结构示意图。该应用管控装置300还可以包括判断模块309。
其中，判断模块309，用于当后台运行的后台应用中存在匹配失败的第一目标应用时，判断匹配失败的第一目标应用是否存在关联应用，其中关联应用与所述匹配失败的第一目标应用具有关联关系。
其中关联应用与匹配失败的第一目标应用具有关联关系。比如应用1被启动，则应用2根据应用1的启动而启动，然而，应用2并非用户所启动的应用，用户也无需应用2启动，无需应用2在后台运行。尤其是一些恶意应用，常常相互具有关联关系，或者说相互进行绑定、相互关联，一旦其中一个被启动，则与其具有关联关系的应用均可以自动启动，并在后台运行，而后台运行的一些无用的应用或者恶意应用，用户往往无法及时察觉，给用户的使用带来极大的困扰。
在一些实施例中，该管控模块304，还用于若判断模块309判断匹配失败的第一目标应用存在关联应用，则关闭匹配失败的第一目标应用以及关联应用。
具体的，若判断模块309判断匹配失败的第一目标应用存在关联应用，则管控模块304关闭匹配失败的第一目标应用以及关联应用，从而避免关联应用在后台运行，不仅可以有效管控后台运行的后台应用，大大提高电子设备的运行速度，降低电子设备的耗电量，而且还可以大大提高电子设备的安全性能。
在一些实施例中，该管控模块304，还用于若判断模块309判断匹配失败的第一目标应用不存在关联应用，则将匹配失败的第一目标应用放置于缓存器中，并将其冻结。
具体的，若判断模块309判断匹配失败的第一目标应用不是恶意应用，则管控模块304将该应用放置于电子设备的缓存器中，并将其暂时冻结，在提高电子设备运行速度，节省电子设备电池的电量的前提下，还方便用户在预设时间内启动放置于缓存器中的第一目标应用。若放置于缓存器中的第一目标应用在预设时间内未通过触控操作启动，则关闭放置于缓存器中的第一目标应用。
本申请实施例还提供一种电子设备400。该电子设备400可以是智能手机、平板电脑等设备。如图13所示，图13为本申请实施例提供的电子设备的结构示意图，电子设备400包括：处理器401和存储器402。其中，处理器401与存储器402电性连接。
处理器401是电子设备400的控制中心，利用各种接口和线路连接整个电子设备400的各个部分，通过运行或加载存储在存储器402内的应用程序，以及调用存储在存储器402内的数据，执行电子设备400的各种功能和处理数据，从而对电子设备400进行整体监控。
在本实施例中，电子设备400中的处理器401会按照如下的步骤，将一个或一个以上的应用程序的进程对应的指令加载到存储器402中，并由处理器401来运行存储在存储器402中的应用程序，从而实现各种功能：
确定通过触控操作启动的应用；
确定当前后台运行的后台应用；
将后台应用与通过触控操作启动的应用进行匹配；
当后台应用中存在匹配失败的第一目标应用时，关闭后台应用中排除通过触控操作启动的应用中的第一目标应用。
在一些实施例中，所述处理器还用于执行：
当所述后台应用中存在匹配失败的第一目标应用时，判断所述匹配失败的第一目标应用是否存在关联应用，其中所述关联应用与所述匹配失败的第一目标应用具有关联关系；
若所述匹配失败的第一目标应用存在关联应用，则关闭所述匹配失败的第一目标应用以及关联应用；
若所述匹配失败的第一目标应用不存在关联应用，则将所述匹配失败的第一目标应用放置于缓存器中，并将其冻结。
在一些实施例中，所述处理器还用于执行：
当放置于所述缓存器中的第一目标应用在预设时间内未通过触控操作启动，则关闭放置于所述缓存器中的第一目标应用。
在一些实施例中，所述处理器还用于执行：
监控电子设备的显示界面中应用的触控事件；
统计所有通过触控操作启动的应用。
存储器402可用于存储应用程序和数据。存储器402存储的应用程序中包含有可在处理器401中执行的指令。应用程序可以组成各种功能模块。处理器401通过运行存储在存储器402的应用程序，从而执行各种功能应用以及数据处理。
在一些实施例中，请一并参阅图14，图14为电子设备的另一结构示意图，电子设备400还包括：射频电路403、显示屏404、控制电路405、输入单元406、音频电路407、传感器408以及电源409。其中，处理器401分别与射频电路403、显示屏404、控制电路405、输入单元406、音频电路407、传感器408以及电源409电性连接。
射频电路403用于收发射频信号，以通过无线通信网络与服务器或其他电子设备进行通信。
显示屏404可用于显示由用户输入的信息或提供给用户的信息以及终端的各种图形用户接口，这些图形用户接口可以由图像、文本、图标、视频和其任意组合来构成。
控制电路405与显示屏404电性连接，用于控制显示屏404显示信息。
输入单元406可用于接收输入的数字、字符信息或用户特征信息(例如指纹)，以及产生与用户设置以及功能控制有关的键盘、鼠标、操作杆、光学或者轨迹球信号输入。
音频电路407可通过扬声器、传声器提供用户与终端之间的音频接口。
传感器408用于采集外部环境信息。传感器408可以包括环境亮度传感器、加速度传感器、陀螺仪等传感器中的一种或多种。
电源409用于给电子设备400的各个部件供电。在一些实施例中，电源409可以通过电源管理系统与处理器401逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。
尽管图14中未示出，电子设备400还可以包括摄像头、蓝牙模块等，在此不再赘述。
由上可知，本申请实施例电子设备可以关闭一些无需后台运行的后台应用，有效管控后台运行的后台应用，减少电子设备的耗电量，提升电子设备的运行速度。
本申请实施例还提供一种存储介质，该存储介质中存储有多条指令，该指令适于由处理器加载以执行上述任一实施例所述的应用管控方法。
需要说明的是，本领域普通技术人员可以理解上述实施例的各种方法中的全部或部分步骤是可以通过程序来指令相关的硬件来完成，该程序可以存储于计算机可读的介质中，该介质可以包括但不限于：只读存储器(ROM，Read Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁盘或光盘等。
以上对本申请实施例所提供的应用管控方法、装置及电子设备进行了详细介绍，本文中应用了具体个例对本申请的原理及实施方式进行了阐述，以上实施例的说明只是用于帮助理解本申请的方法及其核心思想；同时，对于本领域的技术人员，依据本申请的思想，在具体实施方式及应用范围上均会有改变之处，综上所述，本说明书内容不应理解为对本申请的限制。

Claims (20)

  1. 一种应用管控方法，应用于电子设备中，其包括：
    确定通过触控操作启动的应用；
    确定当前后台运行的后台应用；
    将所述后台应用与所述通过触控操作启动的应用进行匹配；
    当所述后台应用中存在匹配失败的第一目标应用时，关闭所述后台应用中排除所述通过触控操作启动的应用中的第一目标应用。
  2. 根据权利要求1所述的应用管控方法，其中，所述当所述后台应用中存在匹配失败的第一目标应用时，关闭所述后台应用中排除所述通过触控操作启动的应用中的第一目标应用的步骤，包括：
    当所述后台应用中存在匹配失败的第一目标应用时，判断所述匹配失败的第一目标应用是否存在关联应用，其中所述关联应用与所述匹配失败的第一目标应用具有关联关系，与所述第一目标应用具有关联关系的关联应用跟随所述第一目标应用的启动而启动；
    若所述匹配失败的第一目标应用存在关联应用，则关闭所述匹配失败的第一目标应用以及关联应用；
    若所述匹配失败的第一目标应用不存在关联应用，则将所述匹配失败的第一目标应用放置于缓存器中，并将其冻结。
  3. 根据权利要求2所述的应用管控方法，其中，所述将所述匹配失败的第一目标应用放置于缓存器中，并将其冻结的步骤，包括：
    当放置于所述缓存器中的第一目标应用在预设时间内未通过触控操作启动，则关闭放置于所述缓存器中的第一目标应用。
  4. 根据权利要求1所述的应用管控方法，其中，所述确定通过触控操作启动的应用的步骤之前，还包括：
    监控电子设备的显示界面中应用的触控事件；
    统计所有通过触控操作启动的应用。
  5. 根据权利要求4所述的应用管控方法，其中，所述统计所有通过触控操作启动的应用的步骤之后，还包括：
    获取所述所有通过触控操作启动的应用的标识，其中所述标识与所述所有通过触控操作启动的应用一一对应；
    根据所述标识生成第一列表；
    所述确定通过触控操作启动的应用的步骤，包括：
    获取所述第一列表；
    根据所述第一列表中的标识确定与所述标识对应的应用。
  6. 根据权利要求5所述的应用管控方法，其中，所述第一列表中的标识按照预设规则形成具有优先等级的排列方式。
  7. 根据权利要求5所述的应用管控方法，其中，所述确定当前后台运行的后台应用的步骤，包括：
    获取与所述后台应用一一对应的标识；
    根据所述与所述后台应用一一对应的标识生成第二列表；
    所述将所述后台应用与所述通过触控操作启动的应用进行匹配的步骤，包括：
    将所述第二列表中的标识与所述第一列表中的标识进行比对。
  8. 根据权利要求7所述的应用管控方法，其中，所述第二列表中的标识按照预设规则形成具有优先等级的排列方式。
  9. 根据权了要求1所述的应用管控方法，其中，所述当所述后台应用中存在匹配失败 的第一目标应用时，关闭所述后台应用中排除所述通过触控操作启动的应用中的第一目标应用的步骤，包括：
    当第一目标应用为多个时，将所述第一目标应用按照预设规则形成具有优先等级的排列方式，并关闭优先等级低于预设阈值的第一目标应用。
  10. 根据权了要求1所述的应用管控方法，其中，所述当所述后台应用中存在匹配失败的第一目标应用时，关闭所述后台应用中排除所述通过触控操作启动的应用中的第一目标应用的步骤，包括：
    当后台运行的后台应用中存在匹配失败的第一目标应用，发出提示信息以提示所述第一目标应用为异常应用。
  11. 一种应用管控装置，应用于电子设备中，其包括：
    第一获取模块，用于确定通过触控操作启动的应用；
    第二获取模块，用于确定当前后台运行的后台应用；
    匹配模块，用于将所述后台应用与所述通过触控操作启动的应用进行匹配；
    管控模块，用于当所述后台应用中存在匹配失败的第一目标应用时，关闭所述后台应用中排除所述通过触控操作启动的应用中的第一目标应用。
  12. 根据权利要求11所述的应用管控装置，其中，所述应用管控装置还包括判断模块；
    所述判断模块，用于当所述后台应用中存在匹配失败的第一目标应用时，判断所述匹配失败的第一目标应用是否存在关联应用，其中所述关联应用与所述匹配失败的第一目标应用具有关联关系，与所述第一目标应用具有关联关系的关联应用跟随所述第一目标应用的启动而启动；
    所述管控模块，还用于若所述匹配失败的第一目标应用存在关联应用，则关闭所述匹配失败的第一目标应用以及关联应用；
    所述管控模块，还用于若所述匹配失败的第一目标应用不存在关联应用，则将所述匹配失败的第一目标应用放置于缓存器中，并将其冻结。
  13. 根据权利要求12所述的应用管控装置，其中，所述管控模块，还用于当放置于所述缓存器中的第一目标应用在预设时间内未通过触控操作启动，则关闭放置于所述缓存器中的第一目标应用。
  14. 根据权利要求11所述的应用管控装置，其中，所述应用管控装置还包括：
    监控模块，用于监控电子设备的显示界面中应用的触控事件；
    统计模块，用于统计所有通过触控操作启动的应用。
  15. 根据权利要求14所述的应用管控装置，其中，所述应用管控装置还包括第三获取模块和第一生成模块，所述第一获取模块包括第一获取主模块和第一获取子模块；
    所述第三获取模块，用于获取所述所有通过触控操作动的应用的标识，其中所述标识与所述所有通过触控操作启动的应用一一对应；
    所述第一生成模块，用于根据所述标识生成第一列表；
    所述第一获取主模块，用于获取所述第一列表；
    所述第一获取子模块，用于根据所述第一列表中的标识确定与所述标识对应的应用。
  16. 根据权利要求15所述的应用管控装置，其中，所述第二获取模块包括第四获取模块和第二生成模块：
    所述第四获取模块，用于获取与所述后台应用一一对应的标识；
    所述第二生成模块，用于根据所述与所述后台应用一一对应的标识生成第二列表；
    所述匹配模块，还用于将所述第二列表中的标识与所述第一列表中的标识进行比对。
  17. 一种电子设备，其包括处理器和存储器，所述处理器和所述存储器电性连接，所述存储器用于存储指令和数据，所述处理器用于执行以下步骤：
    确定通过触控操作启动的应用；
    确定当前后台运行的后台应用；
    将所述后台应用与所述通过触控操作启动的应用进行匹配；
    当所述后台应用中存在匹配失败的第一目标应用时，关闭所述后台应用中排除所述通过主动触控操作的应用中的第一目标应用。
  18. 根据权利要求17所述的电子设备，其中，所述处理器还用于执行：
    当所述后台应用中存在匹配失败的第一目标应用时，判断所述匹配失败的第一目标应用是否存在关联应用，其中所述关联应用与所述匹配失败的第一目标应用具有关联关系，与所述第一目标应用具有关联关系的关联应用跟随所述第一目标应用的启动而启动；
    若所述匹配失败的第一目标应用存在关联应用，则关闭所述匹配失败的第一目标应用以及关联应用；
    若所述匹配失败的第一目标应用不存在关联应用，则将所述匹配失败的第一目标应用放置于缓存器中，并将其冻结。
  19. 根据权利要求18所述的电子设备，其中，所述处理器还用于执行：
    当放置于所述缓存器中的第一目标应用在预设时间内未通过触控操作启动，则关闭放置于所述缓存器中的第一目标应用。
  20. 根据权利要求17所述的电子设备，其中，所述处理器还用于执行：
    监控电子设备的显示界面中应用的触控事件；
    统计所有通过触控操作启动的应用。
PCT/CN2018/094503 2017-07-31 2018-07-04 应用管控方法、装置及电子设备 WO2019024646A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710643059.6 2017-07-31
CN201710643059.6A CN107402804B (zh) 2017-07-31 2017-07-31 后台进程管控方法、装置、存储介质及电子设备

Publications (1)

Publication Number Publication Date
WO2019024646A1 true WO2019024646A1 (zh) 2019-02-07

Family

ID=60401830

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/094503 WO2019024646A1 (zh) 2017-07-31 2018-07-04 应用管控方法、装置及电子设备

Country Status (2)

Country Link
CN (1) CN107402804B (zh)
WO (1) WO2019024646A1 (zh)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107402804B (zh) * 2017-07-31 2019-12-10 Oppo广东移动通信有限公司 后台进程管控方法、装置、存储介质及电子设备
CN108089935B (zh) * 2017-11-29 2021-04-09 维沃移动通信有限公司 一种应用程序的管理方法及移动终端
CN110018899B (zh) * 2018-01-10 2021-09-07 华为技术有限公司 回收内存的方法及装置
CN108805559B (zh) * 2018-07-25 2023-12-15 努比亚技术有限公司 二维码推送方法、移动终端及计算机可读存储介质
CN110069328B (zh) * 2019-03-25 2021-11-09 维沃移动通信有限公司 应用关闭方法及终端设备

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102196097A (zh) * 2011-05-19 2011-09-21 中兴通讯股份有限公司 移动通信终端后台空闲程序自动关闭的方法及装置
US20120260118A1 (en) * 2011-04-11 2012-10-11 Microsoft Corporation Management of background tasks
CN103914342A (zh) * 2013-01-06 2014-07-09 联想(北京)有限公司 一种电子设备程序控制方法、系统及电子设备
CN106125882A (zh) * 2016-06-15 2016-11-16 深圳市万普拉斯科技有限公司 一种应用程序的管理方法以及电子设备
CN107402804A (zh) * 2017-07-31 2017-11-28 广东欧珀移动通信有限公司 后台进程管控方法、装置、存储介质及电子设备
CN107450952A (zh) * 2017-07-31 2017-12-08 广东欧珀移动通信有限公司 应用管控方法、装置、存储介质及电子设备

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100487700C (zh) * 2006-07-11 2009-05-13 阿里巴巴集团控股有限公司 数据仓库中的数据处理方法及系统
CN101604259B (zh) * 2009-06-10 2011-12-21 深圳市共进电子有限公司 一种基于嵌入式系统的多进程同步调度的方法
CN103327037B (zh) * 2012-03-20 2017-09-29 中兴通讯股份有限公司 数据同步方法及装置
BR112015018368B1 (pt) * 2013-02-27 2022-08-02 Hewlett-Packard Development Company, L.P. Método, sistema e meio legível por computador para sincronizar dados
CN104317843B (zh) * 2014-10-11 2017-08-25 上海瀚之友信息技术服务有限公司 一种数据同步etl系统
CN106933534B (zh) * 2015-12-31 2020-07-28 阿里巴巴集团控股有限公司 一种数据同步方法和装置
CN105978947A (zh) * 2016-04-27 2016-09-28 努比亚技术有限公司 对同一账号登录设备数量控制的方法及移动终端
CN105930493A (zh) * 2016-05-04 2016-09-07 北京思特奇信息技术股份有限公司 一种不同数据库间数据同步的方法和系统
CN105847408B (zh) * 2016-05-05 2019-07-12 北京奇虎科技有限公司 一种数据同步的方法、装置及设备

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120260118A1 (en) * 2011-04-11 2012-10-11 Microsoft Corporation Management of background tasks
CN102196097A (zh) * 2011-05-19 2011-09-21 中兴通讯股份有限公司 移动通信终端后台空闲程序自动关闭的方法及装置
CN103914342A (zh) * 2013-01-06 2014-07-09 联想(北京)有限公司 一种电子设备程序控制方法、系统及电子设备
CN106125882A (zh) * 2016-06-15 2016-11-16 深圳市万普拉斯科技有限公司 一种应用程序的管理方法以及电子设备
CN107402804A (zh) * 2017-07-31 2017-11-28 广东欧珀移动通信有限公司 后台进程管控方法、装置、存储介质及电子设备
CN107450952A (zh) * 2017-07-31 2017-12-08 广东欧珀移动通信有限公司 应用管控方法、装置、存储介质及电子设备

Also Published As

Publication number Publication date
CN107402804A (zh) 2017-11-28
CN107402804B (zh) 2019-12-10

Similar Documents

Publication Publication Date Title
WO2019024646A1 (zh) 应用管控方法、装置及电子设备
CN108702421B (zh) 用于控制应用和组件的电子设备和方法
US20200401419A1 (en) Method for Managing Application Program Use Time Offline, and Terminal Device
US10379696B2 (en) Method and apparatus for displaying popup window message
CN106708734B (zh) 软件异常检测方法及装置
EP3499786B1 (en) Data synchronization method, apparatus, storage medium and electronic device
US10474507B2 (en) Terminal application process management method and apparatus
CN107562539B (zh) 应用程序处理方法和装置、计算机设备、存储介质
US20220191318A1 (en) Recommendation Method and Terminal
US20190349451A1 (en) Objection blocking method, terminal, server, and storage medium
WO2019024641A1 (zh) 数据同步方法、装置、存储介质以及电子设备
CN108615158B (zh) 风险检测方法、装置、移动终端和存储介质
US20190340343A1 (en) Application interface display method, apparatus, and terminal, and storage medium
CN107450952B (zh) 应用管控方法、装置、存储介质及电子设备
WO2019024647A1 (zh) 应用程序处理方法、装置、存储介质及终端
US11150913B2 (en) Method, device, and terminal for accelerating startup of application
WO2017206857A1 (zh) 响应控制方法及移动终端
WO2024199275A1 (zh) 应用管控方法、装置、电子设备及计算机可读存储介质
US20220300328A1 (en) Application optimization method and device, storage medium, and electronic equipment
CN110442310A (zh) 应用数据处理方法、装置、存储介质及终端设备
WO2017215663A1 (zh) 一种音效处理的方法及终端
CN111723163A (zh) 一种信息处理方法、装置及系统
WO2019024643A1 (zh) 数据同步管控方法、装置及电子设备
WO2019128562A1 (zh) 应用冻结方法、装置、终端及计算机可读存储介质
WO2020133437A1 (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: 18841359

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18841359

Country of ref document: EP

Kind code of ref document: A1