CN106201710B - Method and device for freezing application - Google Patents
Method and device for freezing application Download PDFInfo
- Publication number
- CN106201710B CN106201710B CN201610495643.7A CN201610495643A CN106201710B CN 106201710 B CN106201710 B CN 106201710B CN 201610495643 A CN201610495643 A CN 201610495643A CN 106201710 B CN106201710 B CN 106201710B
- Authority
- CN
- China
- Prior art keywords
- application
- target
- freezing
- target application
- application information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- 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/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
-
- 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/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5011—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resources being hardware resources other than CPUs, Servers and Terminals
- G06F9/5016—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resources being hardware resources other than CPUs, Servers and Terminals the resource being the memory
-
- 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/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
-
- 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/50—Allocation of resources, e.g. of the central processing unit [CPU]
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
- Information Transfer Between Computers (AREA)
- Computer And Data Communications (AREA)
Abstract
The application provides a method and a device for freezing an application, which are applied to a terminal, wherein the terminal is provided with a first system and a second system, and target application information shared by the first system and the second system is preset, and the method comprises the following steps: and when the target system is the first system, freezing the application needing to be frozen in the system space of the second system based on the target application information, and responding to the operation of a user on any application in the system space of the first system. After the system currently applied by the terminal is determined, the application needing to be frozen in the system space of the other system is frozen based on the preset target application information, on one hand, the memory is saved for the current system space, the starting speed of the application in the current system space is increased, the smooth operation of the current system is ensured, the satisfaction degree of a user for operating the terminal is obviously increased, and on the other hand, the power consumption of the terminal is reduced.
Description
Technical Field
The invention relates to the technical field of software, in particular to a method and a device for freezing an application.
Background
At present, an application freezing technology is implemented in an existing intelligent terminal, and a typical application is that a mobile phone is provided with a refrigerating chamber to realize a refrigerating application, namely, an application which is not frequently used is added into the refrigerating chamber of the mobile phone to be refrigerated, and is unfrozen when the application is needed.
Therefore, in the process of using the intelligent terminal, two operations of freezing and unfreezing exist, so that the complexity of using the mobile intelligent terminal by a user is increased to a certain extent, and the user experience is influenced. At present, some terminals have dual systems, in which case, two systems need to be respectively frozen and correspondingly thawed, which undoubtedly makes the operation of the user more cumbersome, and especially in an emergency situation, brings a very poor satisfaction experience to the user.
Disclosure of Invention
In view of this, the present invention provides a method and an apparatus for freezing an application, so as to solve the problems of complex operation and poor user experience when using an application freezing function in the prior art, and the technical scheme is as follows:
a method for freezing an application is applied to a terminal, the terminal is provided with a first system and a second system, target application information shared by the first system and the second system is preset, and the method for freezing the application comprises the following steps:
determining a target system currently applied by the terminal, wherein the target system is the first system or the second system;
freezing an application in a system space of the second system based on the target application information when the target system is the first system;
responding to a user operation on any application in the system space of the first system.
Wherein the target application information is information of an application which does not need to be frozen;
the preset target application information shared by the first system and the second system specifically comprises: adding the target application information to a white list shared by the first system and the second system in advance;
freezing an application in a system space of the second system based on the target application information when the target system is the first system, comprising:
and when the target system is the first system, freezing the applications except the target application corresponding to the target application information in the system space of the second system.
The target application information is information of an application needing to be frozen;
the preset target application information shared by the first system and the second system specifically comprises: adding the target application information to a blacklist shared by the first system and the second system in advance;
freezing an application in a system space of the second system based on the target application information when the target system is the first system, comprising:
and when the target system is the first system, freezing a target application corresponding to the target application information in the system space of the second system.
Wherein the target application information is information of an application which does not need to be frozen;
the preset target application information shared by the first system and the second system specifically comprises: adding first target application information corresponding to the first system and second target application information corresponding to the second system on a white list shared by the first system and the second system in advance;
freezing an application in a system space of the second system based on the target application information when the target system is the first system, including:
when the target system is the first system, second target application information corresponding to the second system is obtained from the white list;
freezing applications in the system space of the second system except for the target application corresponding to the second target application information.
The target application information is information of an application needing to be frozen;
the preset target application information shared by the first system and the second system specifically comprises: adding first target application information corresponding to the first system and second target application information corresponding to the second system on a blacklist shared by the first system and the second system in advance;
freezing an application in a system space of the second system based on the target application information when the target system is the first system, including:
when the target system is the first system, second target application information corresponding to the second system is obtained from the blacklist;
freezing a target application in the system space of the second system corresponding to the second target application information.
Wherein the method for freezing the application further comprises:
when the system currently applied by the terminal is switched from the first system to the second system, freezing the application in the system space of the first system based on the target application information;
responding to the operation of the user on any application in the system space of the second system.
An apparatus for freezing an application, applied to a terminal having a first system and a second system, the apparatus for freezing an application comprising: the device comprises a setting module, a determining module, a freezing module and a processing module;
the setting module is used for presetting target application information shared by the first system and the second system;
the determining module is configured to determine a target system currently applied by the terminal, where the target system is the first system or the second system;
the freezing module is configured to freeze an application in a system space of the second system based on the target application information set by the setting module when the determining module determines that the target system is the first system;
the processing module is used for responding to the operation of a user on any application in the system space of the first system.
Wherein the target application information is information of an application which does not need to be frozen;
the setting module is specifically configured to add the target application information to a white list shared by the first system and the second system in advance;
the freezing module is specifically configured to freeze, when the determining module determines that the target system is the first system, applications in the system space of the second system except for the target application corresponding to the target application information.
The target application information is information of an application needing to be frozen;
the setting module is specifically configured to add the target application information to a blacklist shared by the first system and the second system in advance;
the freezing module is specifically configured to freeze the target application corresponding to the target application information in the system space of the second system when the determining module determines that the target system is the first system.
Wherein the target application information is information of an application which does not need to be frozen;
the setting module is specifically configured to add first target application information corresponding to the first system and second target application information corresponding to the second system to a white list shared by the first system and the second system in advance;
the freezing module includes: a first acquisition submodule and a first freezing submodule;
the first obtaining sub-module is configured to obtain, when the target system is the first system, second target application information corresponding to the second system from the white list;
the first freezing module is configured to freeze applications in the system space of the second system, except for the target application corresponding to the second target application information acquired by the first acquiring submodule.
The target application information is information of an application needing to be frozen;
the setting module is specifically configured to add first target application information corresponding to the first system and second target application information corresponding to the second system to a blacklist shared by the first system and the second system in advance;
the freezing module comprises a second obtaining submodule and a second freezing submodule:
the second obtaining sub-module is configured to, when the target system is the first system, obtain second target application information corresponding to the second system from the blacklist;
the second freezing submodule is configured to freeze a target application corresponding to the second target application information acquired by the second acquiring submodule in the system space of the second system.
The freezing module is further configured to freeze an application in a system space of the first system based on the preset target application information when the system currently applied by the terminal is switched from the first system to the second system;
the processing module is further used for responding to the operation of the user on any application in the system space of the second system.
The technical scheme has the following beneficial effects:
the method and the device for freezing the application can freeze the application needing to be frozen in the system space of the other system based on the preset target application information shared by the two systems after the system currently applied by the terminal is determined, so that on one hand, the memory is saved for the system space of the current system, the starting speed of the application in the current system space is increased, the smooth running of the application in the current system space is ensured, the satisfaction degree of a user for operating the mobile intelligent terminal is obviously increased, and on the other hand, the power consumption of the terminal is reduced.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a schematic flow chart of a method for freezing an application according to an embodiment of the present invention;
fig. 2 is a schematic flowchart of a specific implementation manner of a method for freezing an application according to an embodiment of the present invention;
fig. 3 is a schematic flowchart of another specific implementation manner of a method for freezing an application according to an embodiment of the present invention;
fig. 4 is a schematic flowchart of another specific implementation manner of the method for freezing an application according to the embodiment of the present invention;
fig. 5 is a flowchart illustrating a further specific implementation manner of a method for freezing an application according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of an apparatus for freezing an application according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
An embodiment of the present invention provides a method for freezing an application, which is applied to a terminal, where the terminal may be, but is not limited to, a PC, a PAD, a mobile phone, and the like, the terminal has a first system and a second system, and target application information shared by the first system and the second system is preset, please refer to fig. 1, which shows a flowchart of the method for freezing an application according to the embodiment of the present invention, and may include:
step S101: and determining a target system currently applied by the terminal.
Wherein the target system is a first system or a second system.
In a possible implementation manner, whether the system currently applied by the terminal is the first system or the second system is determined through the system identifier of the system currently applied by the terminal.
Step S102: and when the target system is the first system, freezing the application in the system space of the second system based on preset target application information.
Step S103: in response to a user operating any of the applications in the system space of the first system.
The user can operate any application in the first system space, namely the user can freely operate the system application in the system space of the current system without influencing the receiving of the unfrozen application information in the system space of the other system.
Illustratively, the terminal has a common system and a security system, the first system may be the common system or the security system, if the first system is the common system, the second system is the security system, at this time, the application in the system space of the security system is frozen based on the preset target application information, if the first system is the security system, the second system is the common system, at this time, the application in the system space of the common system is frozen based on the preset target application information.
According to the method for freezing the application, after the system currently applied by the terminal is determined, the application needing to be frozen in the system space of the other system is frozen based on the preset target application information shared by the two systems, so that on one hand, the memory is saved for the system space of the current system, the starting speed of the application in the current system space is increased, the smooth operation of the current system is ensured, the satisfaction degree of a user for operating the terminal is obviously increased, and on the other hand, the power consumption of the terminal is reduced.
Referring to fig. 2, a flowchart of a specific implementation manner of the method for freezing an application according to the embodiment of the present invention is shown, in the implementation manner, target application information is added to a whitelist shared by a first system and a second system of a terminal in advance, and a specific implementation process may include:
step S201: and judging whether the system currently applied by the terminal is the first system, executing the step S202a when the system currently applied by the terminal is the first system, and otherwise executing the step S202 b.
In this embodiment, whether the system currently applied by the terminal is the first system may be determined by the system identifier of the system currently applied by the terminal.
Step S202 a: freezing applications in the system space of the second system other than the target application corresponding to the target application information.
The target application information may be, but is not limited to, an application identifier of the target application.
In this embodiment, the target application may be the most important and most core application, such as telephone, short message, address book, WeChat, etc. These most important and most core applications may be added to the white list in advance, and when freezing an application in the second system space, the freezing of applications other than these most important and most core applications is performed, so that even if the currently applied system is the first system, the reception of these most important and most core application information in the system space of the second system is not affected.
Step S203 a: responding to the operation of the user on any application in the system space of the first system.
The user can operate any application in the first system space, namely the user can freely operate the system application in the system space of the current system without influencing the receiving of the unfrozen application information in the system space of the other system.
When the currently applied system is not the first system, i.e. the second system, the following steps S202b-S203b are performed:
step S202 b: freezing applications in the system space of the first system other than the target application corresponding to the target application information.
Step S203 b: responding to the operation of the user on any application in the system space of the second system.
The user can operate any application in the system space of the second system, namely, the user can freely operate the system application in the system space of the current system without influencing the receiving of the unfrozen application information in the system space of the other system.
Illustratively, the first system is a common system, the second system is a security system, the target applications on the white list shared by the two systems are a telephone application, a short message application and a WeChat application, if the currently applied system is the common system, other applications except the telephone application, the short message application and the WeChat application in the system space of the security system are frozen, namely the telephone application, the short message application and the WeChat application in the system space of the security system can continue to receive information, and a user can operate freely in the system space of the common system; if the currently applied system is a security system, the applications except the telephone application, the short message application and the WeChat application in the system space of the ordinary system are frozen, namely the telephone application, the short message application and the WeChat application in the system space of the ordinary system can continue to receive information, and a user can operate freely in the system space of the security system. In the embodiment, the white list shared by the two systems is used for freezing the application in the system space which is not currently applied so as to achieve the purpose of ensuring the smooth operation of the application in the system space which is currently applied.
In addition, if the system currently applied by the terminal is the first system, when the system currently applied by the terminal is switched from the first system to the second system, the applications except the target application corresponding to the target information on the white list in the system space of the first system are frozen, and the operation of the user on any application in the second system space is responded. Similarly, if the system currently applied by the terminal is the second system, when the system currently applied by the terminal is switched from the second system to the first system, the applications in the system space of the second system except the target application corresponding to the target information on the white list are frozen, and the operation of the user on any application in the first system space is responded.
According to the method for freezing the application, provided by the embodiment of the invention, the target application is added in advance on the white list shared by the two systems, and after the system currently applied by the terminal is determined, the application except the application on the white list in the system space of the other system is frozen, so that on one hand, the memory is saved for the current system space, the starting speed of the application in the current system space is increased, the smooth operation of the application in the system space of the current system is ensured, the satisfaction degree of a user for operating the terminal is obviously increased, and on the other hand, the power consumption of the terminal is reduced. In addition, freezing the application in the system space can also ensure that the corresponding application is used more safely, and the problem that data or information is leaked due to networking behavior in the using process of the terminal is prevented.
Referring to fig. 3, a schematic flow chart of another specific implementation manner of the method for freezing an application according to the embodiment of the present invention is shown, in which target application information is added to a blacklist shared by a first system and a second system of a terminal in advance, and a specific implementation process may include:
step S301: and judging whether the system currently applied by the terminal is the first system, executing the step S302a when the system currently applied by the terminal is the first system, and otherwise executing the step S302 b.
In this embodiment, whether the system currently applied by the terminal is the first system may be determined by the system identifier of the system currently applied by the terminal.
Step S302 a: and freezing the target application corresponding to the target application information in the system space of the second system.
The target application information may be, but is not limited to, an application identifier of the target application.
In the present embodiment, the target application may be an application having a low degree of importance and a low frequency of use. These applications with low importance and low frequency of use can be added to the black list in advance, and when freezing the applications in the second system space, these applications with low importance and low frequency of use are frozen, so that other applications in the system space of the second system can still receive information.
Step S303 a: in response to a user operating any of the applications in the system space of the first system.
The user can operate any application in the first system space, namely the user can freely operate the system application in the system space of the current system without influencing the receiving of the unfrozen application information in the system space of the other system.
Step S302 b: and freezing the target application corresponding to the target application information in the system space of the first system.
Step S303 b: in response to a user operation of any application in the system space of the second system.
The user can operate any application in the second system space, namely, the user can freely operate the system application in the system space of the current system without influencing the receiving of the unfrozen application information in the system space of the other system.
Illustratively, the first system is a common system, the second system is a security system, the target applications on the blacklist shared by the two systems are a video application, a memo application and a recording application, if the currently applied system is the common system, the video application, the memo application and the recording application in the system space of the security system are frozen, that is, other applications in the system space of the security system can continue to receive information, and the user can operate freely in the system space of the common system; if the currently applied system is the security system, the video application, the memo application and the recording application in the system space of the ordinary system are frozen, namely other applications in the system space of the ordinary system can continue to receive information, and a user can operate freely in the system space of the security system. In the embodiment, the blacklist shared by the two systems is used for freezing the application on the blacklist in the system space which is not currently applied so as to achieve the purpose of ensuring the smooth operation of the application in the system space which is currently applied.
In addition, if the system currently applied by the terminal is the first system, when the system currently applied by the terminal is switched from the first system to the second system, the target application corresponding to the target information on the blacklist in the system space of the first system is frozen, and the operation of the user on any application in the second system space is responded. Similarly, if the system currently applied by the terminal is the second system, when the system currently applied by the terminal is switched from the second system to the first system, the target application corresponding to the target information on the blacklist in the system space of the second system is frozen, and the operation of the user on any application in the first system space is responded.
According to the method for freezing the application, provided by the embodiment of the invention, the target application is added in advance on the blacklist shared by the two systems, and after the system currently applied by the terminal is determined, the application on the blacklist in the system space of the other system is frozen, so that on one hand, the memory is saved for the current system space, the starting speed of the application in the current system space is increased, the smooth operation of the application in the system space of the current system is ensured, the satisfaction degree of a user for operating the terminal is obviously increased, and on the other hand, the power consumption of the terminal is reduced. In addition, freezing the application in the system space can also ensure that the corresponding application is used more safely, and the problem that data or information is leaked due to networking behavior in the using process of the terminal is prevented.
It should be noted that, in the two specific implementations, regardless of whether the white list or the black list is shared by the two systems, the target application information on the white list or the black list is common to the two systems, that is, regardless of which system the current system is, when freezing an application in the system space of the other system, the frozen application is the same target application. However, in some cases, a user may want to freeze different applications for different systems, and based on this consideration, another specific implementation of the method for freezing an application is provided in the embodiment of the present invention, please refer to fig. 4, which shows a flowchart of the specific implementation, in which first target application information corresponding to a first system and second target application information corresponding to a second system are added in advance to a whitelist shared by the first system and the second system of the terminal, and the specific implementation process may include:
step S401: and judging whether the system currently applied by the terminal is the first system, executing the step S402a when the system currently applied by the terminal is the first system, and otherwise executing the step S402 b.
In this embodiment, whether the system currently applied by the terminal is the first system may be determined by the system identifier of the system currently applied by the terminal.
Step S402 a: and acquiring second target application information corresponding to the second system from the white list.
The target application information may be, but is not limited to, an application identifier of the target application.
In one possible implementation, the information on the white list may include a system identifier of the first system and first target application information corresponding to the system identifier of the first system, and a system identifier of the second system and second target application information corresponding to the system identifier of the second system.
If the currently applied system is judged to be the first system, the corresponding second target application information can be obtained from the white list based on the system identification of the second system. Similarly, if the currently applied system is determined to be the second system, the corresponding first target application information may be obtained from the white list based on the system identifier of the first system.
Step S403 a: freezing applications in the system space of the second system other than the target application corresponding to the second target application information.
Step S404 a: in response to a user operating any of the applications in the system space of the first system.
The user can operate any application in the first system space, namely the user can freely operate the system application in the system space of the current system without influencing the receiving of the unfrozen application information in the system space of the other system.
When it is determined that the currently applied system is not the second system, i.e., the second system, the following steps S402b-S404b are performed:
step S402 b: and acquiring first target application information corresponding to the first system from the white list.
Step S403 b: freezing applications in the system space of the first system other than the target application corresponding to the first target application information.
Step S404 b: in response to a user operation of any application in the system space of the second system.
The user can operate any application in the system space of the second system, namely, the user can freely operate the system application in the system space of the current system without influencing the receiving of the unfrozen application information in the system space of the other system.
Illustratively, the first system is a common system, the second system is a security system, the applications corresponding to the security system on the white list shared by the two systems are application a and application b, and the applications corresponding to the common system are application a, application b and application c: if the currently applied system is a common system, freezing other applications except the application a and the application b in the system space of the security system, namely the application a and the application b in the system space of the security system can still receive information, and a user can operate freely in the system space of the common system; if the currently applied system is a security system, the applications except the application a, the application b and the application c in the system space of the ordinary system are frozen, namely the application a, the application b and the application c in the system space of the ordinary system can continue to receive information, and a user can operate freely in the system space of the security system. In the embodiment, the white list shared by the two systems is used for freezing the application in the system space which is not currently applied so as to achieve the purpose of ensuring the smooth operation of the application in the system space which is currently applied.
In addition, if the system currently applied by the terminal is the first system, when the system currently applied by the terminal is switched from the first system to the second system, the applications except the target application corresponding to the first target application information on the white list in the system space of the first system are frozen, and the operation of the user on any application in the second system space is responded. Similarly, if the system currently applied by the terminal is the second system, when the system currently applied by the terminal is switched from the second system to the first system, the applications in the system space of the second system except the target application corresponding to the second target application information on the white list are frozen, and the operation of the user on any application in the first system space is responded.
In the method for freezing the application, the first target application corresponding to the first system and the second target application corresponding to the second system are respectively added to the white lists shared by the two systems, so that the application requirements of a user on different systems can be met, and after the system of the current application of the terminal is determined, the applications except the target application corresponding to the system on the white list in the system space of the other system are frozen, so that on one hand, the memory is saved for the current system space, the starting speed of the applications in the current system space is increased, the smooth running of the applications in the system space of the current system is ensured, the satisfaction degree of the user for operating the terminal is obviously increased, and on the other hand, the power consumption of the terminal is reduced. In addition, freezing the application in the system space can also ensure that the corresponding application is used more safely, and the problem that data or information is leaked due to networking behavior in the using process of the terminal is prevented.
Referring to fig. 5, a flowchart of another specific implementation manner of the method for freezing an application according to the embodiment of the present invention is shown, in which first target application information corresponding to a first system and second target application information corresponding to a second system are added to a blacklist shared by the first system and the second system of a terminal in advance, and a specific implementation process may include:
step S501: and judging whether the system currently applied by the terminal is the first system, if so, executing the step S502a, otherwise, executing the step S502 b.
In this embodiment, whether the system currently applied by the terminal is the first system may be determined by the system identifier of the system currently applied by the terminal.
Step S502 a: and acquiring second target application information corresponding to the second system from the blacklist.
The target application information may be, but is not limited to, an application identifier of the target application.
In one possible implementation, the information on the blacklist may include a system identifier of the first system and first target application information corresponding to the system identifier of the first system, and a system identifier of the second system and second target application information corresponding to the system identifier of the second system.
If the current system is judged to be the first system, the corresponding second target application information can be obtained from the blacklist based on the system identification of the second system. Similarly, if the current system is determined to be the second system, the corresponding first target application information may be obtained from the blacklist based on the system identifier of the first system.
Step S503 a: and freezing the target application corresponding to the second target application information in the system space of the second system.
Step S504 a: in response to a user operating any of the applications in the system space of the first system.
The user can operate any application in the first system space, namely the user can freely operate the system application in the system space of the current system without influencing the receiving of the unfrozen application information in the system space of the other system.
When the currently applied system is determined not to be the first system, i.e. the second system, the following steps S502b-S504b are executed:
step S502 b: and acquiring first target application information corresponding to the first system from the blacklist.
Step S503 b: and freezing a target application corresponding to the first target application information in the system space of the first system.
Step S504 b: responding to the operation of the user on any application in the system space of the second system.
The user can operate any application in the system space of the second system, namely the user can freely operate the system application in the system space of the current application without influencing the receiving of the unfrozen application information in the system space of the other system.
Illustratively, the first system is a common system, the second system is a security system, the applications corresponding to the security system on the blacklist shared by the two systems are application a, application b, application c and application d, and the applications corresponding to the common system are application a, application b and application c, application e and application f: if the currently applied system is a common system, freezing the application a, the application b, the application c and the application d in the system space of the security system, namely, the applications except the application a, the application b, the application c and the application d in the system space of the security system can still receive information, and a user can operate freely in the system space of the common system; if the currently applied system is a security system, the application a, the application b and the application c, and the application e and the application f in the system space of the ordinary system are frozen, namely, the applications except the application a, the application b and the application c, and the application e and the application f in the system space of the ordinary system can still continue to receive information, and a user can freely operate in the system space of the security system. In the embodiment, the blacklist shared by the two systems is used for freezing the application in the system space which is not currently applied, so that the purpose of ensuring the smooth operation of the application in the system space which is currently applied is achieved.
In addition, if the system currently applied by the terminal is the first system, when the system currently applied by the terminal is switched from the first system to the second system, the target application corresponding to the first target application information on the blacklist in the system space of the first system is frozen, and the operation of the user on any application in the second system space is responded. Similarly, if the system currently applied by the terminal is the second system, when the system currently applied by the terminal is switched from the second system to the first system, the target application corresponding to the second target application information on the blacklist in the system space of the second system is frozen, and the operation of the user on any application in the first system space is responded.
In the method for freezing the application, the first target application corresponding to the first system and the second target application corresponding to the second system are respectively added to the blacklists shared by the two systems, so that the application requirements of a user on different systems can be met, and after the system currently applied by the terminal is determined, the target application corresponding to the system on the blacklist in the system space of the other system is frozen, so that on one hand, the memory is saved for the current system space, the starting speed of the application in the current system space is increased, the smooth operation of the application in the system space of the current system is ensured, the satisfaction degree of the user for operating the terminal is remarkably increased, and on the other hand, the power consumption of the terminal is reduced. In addition, freezing the application in the system space can also ensure that the corresponding application is used more safely, and the problem that data or information is leaked due to networking behavior in the using process of the terminal is prevented.
An embodiment of the present invention further provides an apparatus for freezing an application, which is applied to a terminal, where the terminal has a first system and a second system, please refer to fig. 6, which shows a schematic structural diagram of the apparatus for freezing an application provided in the embodiment of the present invention, and the apparatus may include: a setting module 600, a determining module 601, a freezing module 602, and a processing module 603.
The setting module 600 is configured to preset target application information shared by the first system and the second system.
The determining module 601 is configured to determine a target system currently applied by the terminal, where the target system is a first system or a second system.
A freezing module 602, configured to freeze an application in a system space of a second system based on target application information preset by the setting module 600 when the determining module 601 determines that the target system currently applied by the terminal is the first system.
The processing module 603 is configured to respond to a user's operation on any application in the system space of the first system.
According to the device for freezing the application, after the system currently applied by the terminal is determined, the application needing to be frozen in the system space of the other system is frozen based on the preset target application information, so that on one hand, the memory is saved for the system space of the current system, the starting speed of the application in the current system space is increased, the smooth operation of the current system is ensured, the satisfaction degree of a user for operating the mobile terminal is obviously increased, and on the other hand, the power consumption of the terminal is reduced. In addition, freezing the application in the system space can also ensure that the corresponding application is used more safely, and the problem that data or information is leaked due to networking behavior in the using process of the terminal is prevented.
In a possible implementation manner, the target application information in the above embodiment is information of an application that does not need to be frozen.
The setting module is specifically configured to add the target application information to a white list shared by the first system and the second system in advance.
Correspondingly, the freezing module is specifically configured to freeze applications in the system space of the second system except the target application corresponding to the target application information when the determining module determines that the target system currently applied by the terminal is the first system.
In another possible implementation, the target application information is information of an application that needs to be frozen.
The setting module is specifically configured to add the target application information to a blacklist shared by the first system and the second system in advance.
Correspondingly, the freezing module is specifically configured to freeze the target application corresponding to the target application information in the system space of the second system when the determining module determines that the target system currently applied by the terminal is the first system.
In yet another possible implementation, the target application information is information of an application that does not need to be frozen.
The setting module is specifically configured to add first target application information corresponding to the first system and second target application information corresponding to the second system to a white list shared by the first system and the second system in advance.
Accordingly, the freezing module comprises: a first acquisition submodule and a first freezing submodule. Wherein:
and the first obtaining sub-module is used for obtaining second target application information corresponding to the second system from the white list when the target system currently applied by the terminal is the first system.
And the first freezing module is used for freezing the applications except the target application corresponding to the second target application information acquired by the first acquisition submodule in the system space of the second system.
In yet another possible implementation manner, the target application information in the above embodiment is information of an application that does not need to be frozen.
The setting module is specifically configured to add first target application information corresponding to the first system and second target application information corresponding to the second system to a blacklist shared by the first system and the second system in advance.
Correspondingly, the freezing module comprises a second obtaining submodule and a second freezing submodule. Wherein:
the second obtaining sub-module is used for obtaining second target application information corresponding to a second system from the blacklist when a target system currently applied by the terminal is the first system;
and the second freezing submodule is used for freezing the target application corresponding to the second target application information acquired by the second acquisition submodule in the system space of the second system.
In the apparatus for freezing an application provided in any of the embodiments above, the freezing module is further configured to freeze an application in a system space of the first system based on preset target application information when a system currently applied by the terminal is switched from the first system to the second system.
Correspondingly, the processing module is further configured to respond to a user's operation of any application in the system space of the second system.
The method and the device for freezing the application provided by the embodiment of the invention can ensure that after the system of the current application is determined, the application of the white list or the black list based on the dual system sharing in the system space of the other system is frozen, the good experience of the user on the intelligent terminal is greatly met, particularly the efficient switching between the two systems is realized, moreover, the double-system white list or black list freezing application mechanism can well meet the operation requirement of the user on the double systems, meanwhile, the memory is saved for the current system space, the application starting speed is improved, the operation requirement of a user on the system smoothness is improved, the memory occupation caused by the large operation of the dual systems is prevented, the current system jam phenomenon in the use process is reduced, the invention has strong practicability and can obviously improve the satisfaction degree of the user operating the terminal.
The embodiments in the present description are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.
In the several embodiments provided in the present application, it should be understood that the disclosed method, apparatus, and device may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of devices or units through some communication interfaces, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment. In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (12)
1. A method for freezing an application is applied to a terminal, the terminal is provided with a first system and a second system, the method is characterized in that target application information shared by the first system and the second system is preset, and the method for freezing the application comprises the following steps:
determining a target system currently applied by the terminal, wherein the target system is the first system or the second system;
freezing an application in a system space of the second system based on the target application information when the target system is the first system;
responding to a user operation on any application in the system space of the first system.
2. A method for freezing an application according to claim 1, wherein the target application information is information of an application that does not need to be frozen;
the preset target application information shared by the first system and the second system specifically comprises: adding the target application information to a white list shared by the first system and the second system in advance;
freezing an application in a system space of the second system based on the target application information when the target system is the first system, comprising:
and when the target system is the first system, freezing the applications except the target application corresponding to the target application information in the system space of the second system.
3. The method of claim 1, wherein the target application information is information of an application that needs to be frozen;
the preset target application information shared by the first system and the second system specifically comprises: adding the target application information to a blacklist shared by the first system and the second system in advance;
freezing an application in a system space of the second system based on the target application information when the target system is the first system, comprising:
and when the target system is the first system, freezing a target application corresponding to the target application information in the system space of the second system.
4. A method for freezing an application according to claim 1, wherein the target application information is information of an application that does not need to be frozen;
the preset target application information shared by the first system and the second system specifically comprises: adding first target application information corresponding to the first system and second target application information corresponding to the second system on a white list shared by the first system and the second system in advance;
freezing an application in a system space of the second system based on the target application information when the target system is the first system, including:
when the target system is the first system, second target application information corresponding to the second system is obtained from the white list;
freezing applications in the system space of the second system except for the target application corresponding to the second target application information.
5. A method for freezing an application according to claim 1, wherein the target application information is information of an application that needs to be frozen;
the preset target application information shared by the first system and the second system specifically comprises: adding first target application information corresponding to the first system and second target application information corresponding to the second system on a blacklist shared by the first system and the second system in advance;
freezing an application in a system space of the second system based on the target application information when the target system is the first system, including:
when the target system is the first system, second target application information corresponding to the second system is obtained from the blacklist;
freezing a target application in the system space of the second system corresponding to the second target application information.
6. A method of freezing an application according to any of claims 1-5, further comprising:
when the system currently applied by the terminal is switched from the first system to the second system, freezing the application in the system space of the first system based on the target application information;
responding to the operation of the user on any application in the system space of the second system.
7. An apparatus for freezing an application, applied to a terminal having a first system and a second system, the apparatus for freezing an application comprising: the device comprises a setting module, a determining module, a freezing module and a processing module;
the setting module is used for presetting target application information shared by the first system and the second system;
the determining module is configured to determine a target system currently applied by the terminal, where the target system is the first system or the second system;
the freezing module is configured to freeze an application in a system space of the second system based on the target application information set by the setting module when the determining module determines that the target system is the first system;
the processing module is used for responding to the operation of a user on any application in the system space of the first system.
8. An apparatus for freezing an application according to claim 7, wherein the target application information is information of an application that does not need to be frozen;
the setting module is specifically configured to add the target application information to a white list shared by the first system and the second system in advance;
the freezing module is specifically configured to freeze, when the determining module determines that the target system is the first system, applications in the system space of the second system except for the target application corresponding to the target application information.
9. An apparatus for freezing an application according to claim 7, wherein the target application information is information of an application that needs to be frozen;
the setting module is specifically configured to add the target application information to a blacklist shared by the first system and the second system in advance;
the freezing module is specifically configured to freeze the target application corresponding to the target application information in the system space of the second system when the determining module determines that the target system is the first system.
10. An apparatus for freezing an application according to claim 7, wherein the target application information is information of an application that does not need to be frozen;
the setting module is specifically configured to add first target application information corresponding to the first system and second target application information corresponding to the second system to a white list shared by the first system and the second system in advance;
the freezing module includes: a first acquisition submodule and a first freezing submodule;
the first obtaining sub-module is configured to obtain, when the target system is the first system, second target application information corresponding to the second system from the white list;
the first freezing module is configured to freeze applications in the system space of the second system, except for the target application corresponding to the second target application information acquired by the first acquiring submodule.
11. An apparatus for freezing an application according to claim 7, wherein the target application information is information of an application that needs to be frozen;
the setting module is specifically configured to add first target application information corresponding to the first system and second target application information corresponding to the second system to a blacklist shared by the first system and the second system in advance;
the freezing module comprises a second obtaining submodule and a second freezing submodule:
the second obtaining sub-module is configured to, when the target system is the first system, obtain second target application information corresponding to the second system from the blacklist;
the second freezing submodule is configured to freeze a target application corresponding to the second target application information acquired by the second acquiring submodule in the system space of the second system.
12. The apparatus for freezing an application according to any one of claims 7-11, wherein the freezing module is further configured to freeze the application in the system space of the first system based on the preset target application information when the system currently applied by the terminal is switched from the first system to the second system;
the processing module is further used for responding to the operation of the user on any application in the system space of the second system.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610495643.7A CN106201710B (en) | 2016-06-29 | 2016-06-29 | Method and device for freezing application |
| PCT/CN2016/092530 WO2018000506A1 (en) | 2016-06-29 | 2016-07-31 | Method of freezing application, and device utilizing same |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610495643.7A CN106201710B (en) | 2016-06-29 | 2016-06-29 | Method and device for freezing application |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106201710A CN106201710A (en) | 2016-12-07 |
| CN106201710B true CN106201710B (en) | 2020-08-04 |
Family
ID=57462420
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610495643.7A Active CN106201710B (en) | 2016-06-29 | 2016-06-29 | Method and device for freezing application |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN106201710B (en) |
| WO (1) | WO2018000506A1 (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113630751B (en) * | 2020-05-06 | 2023-10-20 | 成都鼎桥通信技术有限公司 | Bluetooth using method and device based on dual systems |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105468426A (en) * | 2016-01-05 | 2016-04-06 | 珠海市魅族科技有限公司 | Application freezing method and terminal |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102736945B (en) * | 2011-03-31 | 2016-05-18 | 国际商业机器公司 | A kind of method and system of the Multi-instance running application |
| JP6098251B2 (en) * | 2013-03-14 | 2017-03-22 | 日本電気株式会社 | Redundant system |
| CN103763322A (en) * | 2014-01-23 | 2014-04-30 | 宇龙计算机通信科技(深圳)有限公司 | Method and device for controlling process of software and terminals |
| CN104881299A (en) * | 2014-02-28 | 2015-09-02 | 可牛网络技术（北京）有限公司 | Application program freezing method and apparatus |
| WO2015139246A1 (en) * | 2014-03-19 | 2015-09-24 | 华为终端有限公司 | Method and device for synchronizing application data |
| US20160055031A1 (en) * | 2014-11-13 | 2016-02-25 | Mediatek Inc. | Dual-System Architecture With Fast Recover And Switching Of Operating System |
| CN104407892A (en) * | 2014-11-24 | 2015-03-11 | 南京酷派软件技术有限公司 | System switching method, system switching device and terminal |
| CN104680090A (en) * | 2015-02-06 | 2015-06-03 | 西安酷派软件科技有限公司 | Application hiding control method, device and mobile terminal |
-
2016
- 2016-06-29 CN CN201610495643.7A patent/CN106201710B/en active Active
- 2016-07-31 WO PCT/CN2016/092530 patent/WO2018000506A1/en active Application Filing
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105468426A (en) * | 2016-01-05 | 2016-04-06 | 珠海市魅族科技有限公司 | Application freezing method and terminal |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2018000506A1 (en) | 2018-01-04 |
| CN106201710A (en) | 2016-12-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102883449B (en) | A kind of realize the method for data sharing, associated terminal and system | |
| KR20220140606A (en) | DATA TRANSMISSION METHOD AND DATA TRANSMISSION APPARATUS | |
| CN107748685B (en) | Application program starting control method and device, terminal equipment and storage medium | |
| CN104853422B (en) | A kind of method and device of electricity saving of mobile terminal | |
| EP2849474A1 (en) | Information processing method and terminal | |
| US9066292B2 (en) | System and method for polling a network service | |
| EP3544344A1 (en) | Operation mode switching method and user equipment | |
| CN106022101A (en) | Application management method and terminal | |
| US20160028832A1 (en) | Methods and systems for efficient discovery of devices in a peer-to-peer network | |
| CN110740088B (en) | Method, device, terminal and medium for recommending and adding social resources | |
| CN112083988A (en) | Screen refresh rate control method, mobile terminal and computer readable storage medium | |
| CN110741684A (en) | Information sending method and device, network selection method and device and base station | |
| WO2018014424A1 (en) | Method for setting authority for information pushing, and mobile terminal | |
| EP3486823A1 (en) | System notification service control method, apparatus, terminal device, and storage medium | |
| CN106231051B (en) | Video decoding test method and related equipment | |
| CN106201710B (en) | Method and device for freezing application | |
| US10164701B2 (en) | Antenna allocation method and terminal | |
| CN109257806B (en) | Carrier aggregation mode setting method for communication terminal, communication terminal and medium | |
| CN104010353B (en) | A kind of information processing method and electronic equipment | |
| CN104202833A (en) | Signal strength display method, signal strength display device and base station | |
| JP4723643B2 (en) | Communication method of wireless communication device | |
| CA2814292C (en) | System and method for polling a network service | |
| CN115699903A (en) | Paging cycle configuration method, base station, terminal and storage medium | |
| CN112351465B (en) | Network mode switching method and device | |
| CN114615454B (en) | Message prompting method, device, terminal and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |