CN110087290B - Power consumption management and control method, terminal and computer readable storage medium - Google Patents
Power consumption management and control method, terminal and computer readable storage medium Download PDFInfo
- Publication number
- CN110087290B CN110087290B CN201910329918.3A CN201910329918A CN110087290B CN 110087290 B CN110087290 B CN 110087290B CN 201910329918 A CN201910329918 A CN 201910329918A CN 110087290 B CN110087290 B CN 110087290B
- Authority
- CN
- China
- Prior art keywords
- application program
- interaction
- application
- condition
- power consumption
- 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
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
- H04W52/0209—Power saving arrangements in terminal devices
- H04W52/0261—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level
- H04W52/0264—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by selectively disabling software applications
-
- 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
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephone Function (AREA)
Abstract
The embodiment of the application discloses a power consumption management and control method, a terminal and a computer readable storage medium, wherein the power consumption management and control method comprises the following steps: under the condition that a first application program runs, starting a second application program for providing services for the first application program; determining whether there is interaction between the first application and the second application if the second application is launched; and logging off the second application program under the condition that no interaction exists between the first application program and the second application program. According to the embodiment of the application, the second application program providing service for the first application program is started through the first application program, and the second application program is logged off when no interaction exists between the first application program and the second application program; the problem that the user experience effect is poor due to the fact that the cruising ability of the mobile terminal is affected by mutual pulling among application programs in the existing mobile terminal is solved; the power consumption of the terminal is reduced, and the user experience is improved.
Description
Technical Field
The embodiment of the application relates to the technical field of terminals, in particular to a power consumption management and control method, a terminal and a computer readable storage medium.
Background
Along with popularization, popularization and development of the mobile terminal, the mobile terminal has more and more functions, stronger performance and richer experience, brings great convenience to life of people, and makes people more and more free. With the increasing average duration of using the mobile terminal by people, the endurance performance of the mobile terminal is also receiving attention of users, and becomes an important factor affecting the use experience of the users.
One important reason for affecting the endurance of a mobile terminal is: the mutual pulling between application programs causes that the application programs or functions which the user does not want to use are operated to perform operations such as networking, positioning, sensor use and the like in the background, so that the faster the electric quantity is consumed. It is currently common practice to limit these applications to launch, but after limiting, certain functions may be rendered unusable, resulting in a poor user experience.
Disclosure of Invention
In view of the above, an object of the embodiments of the present application is to provide a power consumption management and control method, a terminal, and a computer readable storage medium, so as to solve the problem that the user experience effect is poor in the existing mobile terminal due to the influence of the mutual pull between application programs on the endurance of the mobile terminal.
The technical scheme adopted by the embodiment of the application for solving the technical problems is as follows:
according to an aspect of the embodiment of the present application, there is provided a power consumption management and control method for a terminal, the power consumption management and control method including:
under the condition that a first application program runs, starting a second application program for providing services for the first application program;
determining whether there is interaction between the first application and the second application if the second application is launched;
and logging off the second application program under the condition that no interaction exists between the first application program and the second application program.
In a possible implementation manner, the determining whether there is interaction between the first application program and the second application program when the second application program is started further includes:
judging whether the interaction between the first application program and the second application program is malicious or not under the condition that the interaction between the first application program and the second application program exists;
and under the condition that the interaction between the first application program and the second application program is malicious interaction, logging off the second application program.
In one possible implementation manner, the determining whether the interaction between the first application program and the second application program is a malicious interaction in the case that the interaction between the first application program and the second application program is a malicious interaction includes:
under the condition that interaction exists between the first application program and the second application program, acquiring interaction data and interaction frequency between the first application program and the second application program;
and judging whether the interaction between the first application program and the second application program is malicious or not according to the interaction data and the interaction frequency between the first application program and the second application program.
In one possible implementation manner, the determining whether the interaction between the first application program and the second application program is a malicious interaction according to the interaction data and the interaction frequency between the first application program and the second application program includes:
and if the interaction data are null data and the interaction frequency is fixed frequency, judging that the interaction between the first application program and the second application program is malicious interaction.
In a possible implementation manner, the logging off the second application program without interaction between the first application program and the second application program further includes:
acquiring the current battery power or memory of the terminal;
and executing the step of logging out the second application program under the condition that no interaction exists between the first application program and the second application program under the condition that the current battery level of the terminal is lower than a preset battery level threshold value or the current memory of the terminal is lower than a preset memory threshold value.
In one possible implementation, the logging off the second application without interaction between the first application and the second application includes:
recording the time of no interaction between the first application program and the second application program under the condition that no interaction exists between the first application program and the second application program;
and under the condition that the time of no interaction between the first application program and the second application program exceeds the preset time, logging off the second application program.
In one possible implementation manner, the launching the second application program that provides services for the first application program in the case that the first application program runs includes:
detecting a call instruction of the first application program to the second application program under the condition that the first application program runs;
acquiring a package name of the second application program under the condition that a call instruction of the first application program to the second application program is detected;
determining whether the package name of the second application program is in the white list of the first application program;
and starting the second application program under the condition that the package name of the second application program is in the white list of the first application program.
In a possible implementation manner, the determining whether the package name of the second application program is in the white list of the first application program further includes:
and prohibiting the second application program from being started under the condition that the package name of the second application program is not in the white list of the first application program.
According to another aspect of the embodiment of the present application, a terminal is provided, where the terminal includes a memory, a processor, and a power consumption management and control program stored in the memory and capable of running on the processor, and the power consumption management and control program implements the steps of the power consumption management and control method when executed by the processor.
According to another aspect of the embodiments of the present application, there is provided a computer readable storage medium having stored thereon a power consumption management and control program, which when executed by a processor, implements the steps of the power consumption management and control method described above.
According to the power consumption management and control method, the terminal and the computer readable storage medium, a second application program for providing services for the first application program is started through the first application program, and the second application program is logged off when no interaction exists between the first application program and the second application program; the problem that the user experience effect is poor due to the fact that the cruising ability of the mobile terminal is affected by mutual pulling among application programs in the existing mobile terminal is solved; the power consumption of the terminal is reduced, and the user experience is improved.
Drawings
Fig. 1 is a schematic diagram of a hardware structure of a mobile terminal implementing various embodiments of the present application;
fig. 2 is a schematic diagram of a communication network system according to an embodiment of the present application;
FIG. 3 is a flow chart illustrating a power consumption management and control method according to a first embodiment of the present application;
FIG. 4 is a diagram illustrating a call setup interface of a first application according to an embodiment of the present application;
fig. 5 is a schematic diagram of a terminal structure according to a second embodiment of the present application.
The achievement of the objects, functional features and advantages of the present application will be further described with reference to the accompanying drawings, in conjunction with the embodiments.
Detailed Description
In order to make the technical problems, technical schemes and beneficial effects to be solved more clear and obvious, the application is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application.
In the following description, suffixes such as "module", "component", or "unit" for representing elements are used only for facilitating the description of the present application, and have no specific meaning per se. Thus, "module," "component," or "unit" may be used in combination.
The terminal may be implemented in various forms. For example, the terminals described in the present application may include mobile terminals such as cell phones, tablet computers, notebook computers, palm top computers, PDAs (Personal Digital Assistant, personal digital assistants), PMPs (Portable Media Player, portable media players), navigation devices, wearable devices, smart bracelets, pedometers, and fixed terminals such as digital TVs, desktop computers, and the like.
The following description will be given taking a mobile terminal as an example, and those skilled in the art will understand that the configuration according to the embodiment of the present application can be applied to a fixed type terminal in addition to elements particularly used for a moving purpose.
Referring to fig. 1, which is a schematic diagram of a hardware structure of a mobile terminal implementing various embodiments of the present application, the mobile terminal 100 may include: an RF (Radio Frequency) unit 101, a WiFi module 102, an audio output unit 103, an a/V (audio/video) input unit 104, a sensor 105, a display unit 106, a user input unit 107, an interface unit 108, a memory 109, a processor 110, and a power supply 111. Those skilled in the art will appreciate that the mobile terminal structure shown in fig. 1 is not limiting of the mobile terminal and that the mobile terminal may include more or fewer components than shown, or may combine certain components, or a different arrangement of components.
The following describes the components of the mobile terminal in detail with reference to fig. 1:
the radio frequency unit 101 may be used for receiving and transmitting signals during the information receiving or communication process, specifically, after receiving downlink information of the base station, processing the downlink information by the processor 110; and, the uplink data is transmitted to the base station. Typically, the radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio frequency unit 101 may also communicate with networks and other devices via wireless communications. The wireless communication may use any communication standard or protocol, including but not limited to GSM (Global System of Mobile communication, global System for Mobile communications), GPRS (General Packet Radio Service ), CDMA2000 (Code Division Multiple Access, CDMA 2000), WCDMA (Wideband Code Division Multiple Access ), TD-SCDMA (Time Division-Synchronous Code Division Multiple Access, time Division synchronous code Division multiple Access), FDD-LTE (Frequency Division Duplexing-Long Term Evolution, frequency Division Duplex Long term evolution), and TDD-LTE (Time Division Duplexing-Long Term Evolution, time Division Duplex Long term evolution), etc.
WiFi belongs to a short-distance wireless transmission technology, and a mobile terminal can help a user to send and receive e-mails, browse web pages, access streaming media and the like through the WiFi module 102, so that wireless broadband Internet access is provided for the user. Although fig. 1 shows a WiFi module 102, it is understood that it does not belong to the necessary constitution of a mobile terminal, and can be omitted entirely as required within a range that does not change the essence of the application.
The audio output unit 103 may convert audio data received by the radio frequency unit 101 or the WiFi module 102 or stored in the memory 109 into an audio signal and output as sound when the mobile terminal 100 is in a call signal reception mode, a talk mode, a recording mode, a voice recognition mode, a broadcast reception mode, or the like. Also, the audio output unit 103 may also provide audio output (e.g., a call signal reception sound, a message reception sound, etc.) related to a specific function performed by the mobile terminal 100. The audio output unit 103 may include a speaker, a buzzer, and the like.
The a/V input unit 104 is used to receive an audio or video signal. The a/V input unit 104 may include a graphics processor (Graphics Processing Unit, GPU) 1041 and a microphone 1042, the graphics processor 1041 processing image data of still pictures or video obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The processed image frames may be displayed on the display unit 106. The image frames processed by the graphics processor 1041 may be stored in the memory 109 (or other storage medium) or transmitted via the radio frequency unit 101 or the WiFi module 102. The microphone 1042 can receive sound (audio data) via the microphone 1042 in a phone call mode, a recording mode, a voice recognition mode, and the like, and can process such sound into audio data. The processed audio (voice) data may be converted into a format output that can be transmitted to the mobile communication base station via the radio frequency unit 101 in the case of a telephone call mode. The microphone 1042 may implement various types of noise cancellation (or suppression) algorithms to cancel (or suppress) noise or interference generated in the course of receiving and transmitting the audio signal.
The mobile terminal 100 also includes at least one sensor 105, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor and a proximity sensor, wherein the ambient light sensor can adjust the brightness of the display panel 1061 according to the brightness of ambient light, and the proximity sensor can turn off the display panel 1061 and/or the backlight when the mobile terminal 100 moves to the ear. As one of the motion sensors, the accelerometer sensor can detect the acceleration in all directions (generally three axes), and can detect the gravity and direction when stationary, and can be used for applications of recognizing the gesture of a mobile phone (such as horizontal and vertical screen switching, related games, magnetometer gesture calibration), vibration recognition related functions (such as pedometer and knocking), and the like; as for other sensors such as fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc. that may also be configured in the mobile phone, the detailed description thereof will be omitted.
The display unit 106 is used to display information input by a user or information provided to the user. The display unit 106 may include a display panel 1061, and the display panel 1061 may be configured in the form of a liquid crystal display (Liquid Crystal Display, LCD), an Organic Light-Emitting Diode (OLED), or the like.
The user input unit 107 may be used to receive input numeric or character information and to generate key signal inputs related to user settings and function control of the mobile terminal. In particular, the user input unit 107 may include a touch panel 1071 and other input devices 1072. The touch panel 1071, also referred to as a touch screen, may collect touch operations thereon or thereabout by a user (e.g., operations of the user on the touch panel 1071 or thereabout by using any suitable object or accessory such as a finger, a stylus, etc.) and drive the corresponding connection device according to a predetermined program. The touch panel 1071 may include two parts of a touch detection device and a touch controller. The touch detection device detects the touch azimuth of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts it into touch point coordinates, and sends the touch point coordinates to the processor 110, and can receive and execute commands sent from the processor 110. Further, the touch panel 1071 may be implemented in various types such as resistive, capacitive, infrared, and surface acoustic wave. The user input unit 107 may include other input devices 1072 in addition to the touch panel 1071. In particular, other input devices 1072 may include, but are not limited to, one or more of a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, mouse, joystick, etc., as specifically not limited herein.
Further, the touch panel 1071 may overlay the display panel 1061, and when the touch panel 1071 detects a touch operation thereon or thereabout, the touch panel 1071 is transferred to the processor 110 to determine the type of touch event, and then the processor 110 provides a corresponding visual output on the display panel 1061 according to the type of touch event. Although in fig. 1, the touch panel 1071 and the display panel 1061 are two independent components for implementing the input and output functions of the mobile terminal, in some embodiments, the touch panel 1071 may be integrated with the display panel 1061 to implement the input and output functions of the mobile terminal, which is not limited herein.
The interface unit 108 serves as an interface through which at least one external device can be connected with the mobile terminal 100. For example, the external devices may include a wired or wireless headset port, an external power (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The interface unit 108 may be used to receive input (e.g., data information, power, etc.) from an external device and transmit the received input to one or more elements within the mobile terminal 100 or may be used to transmit data between the mobile terminal 100 and an external device.
Memory 109 may be used to store software programs as well as various data. The memory 109 may mainly include a storage program area that may store an operating system, application programs required for at least one function (such as a sound playing function, an image playing function, etc.), and a storage data area; the storage data area may store data (such as audio data, phonebook, etc.) created according to the use of the handset, etc. In addition, memory 109 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device.
The processor 110 is a control center of the mobile terminal, connects various parts of the entire mobile terminal using various interfaces and lines, and performs various functions of the mobile terminal and processes data by running or executing software programs and/or modules stored in the memory 109 and calling data stored in the memory 109, thereby performing overall monitoring of the mobile terminal. Processor 110 may include one or more processing units; preferably, the processor 110 may integrate an application processor that primarily handles operating systems, user interfaces, applications, etc., with a modem processor that primarily handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 110.
The mobile terminal 100 may further include a power source 111 (e.g., a battery) for supplying power to the respective components, and preferably, the power source 111 may be logically connected to the processor 110 through a power management system, so as to perform functions of managing charging, discharging, and power consumption management through the power management system.
Although not shown in fig. 1, the mobile terminal 100 may further include a bluetooth module or the like, which is not described herein.
In order to facilitate understanding of the embodiments of the present application, a communication network system on which the mobile terminal of the present application is based will be described below.
Referring to fig. 2, fig. 2 is a schematic diagram of a communication network system according to an embodiment of the present application, where the communication network system is an LTE system of a general mobile communication technology, and the LTE system includes a UE (User Equipment) 201, an e-UTRAN (Evolved UMTS Terrestrial Radio Access Network ) 202, an epc (Evolved Packet Core, evolved packet core) 203, and an IP service 204 of an operator that are sequentially connected in communication.
Specifically, the UE201 may be the terminal 100 described above, and will not be described herein.
The E-UTRAN202 includes eNodeB2021 and other eNodeB2022, etc. The eNodeB2021 may be connected with other eNodeB2022 by a backhaul (e.g., an X2 interface), the eNodeB2021 is connected to the EPC203, and the eNodeB2021 may provide access from the UE201 to the EPC 203.
EPC203 may include MME (Mobility Management Entity ) 2031, hss (Home Subscriber Server, home subscriber server) 2032, other MMEs 2033, SGW (Serving Gate Way) 2034, pgw (PDN Gate Way) 2035 and PCRF (Policy and Charging Rules Function, policy and tariff function entity) 2036, and so on. The MME2031 is a control node that handles signaling between the UE201 and EPC203, providing bearer and connection management. HSS2032 is used to provide registers to manage functions such as home location registers (not shown) and to hold user specific information about service characteristics, data rates, etc. All user data may be sent through SGW2034 and PGW2035 may provide IP address allocation and other functions for UE201, PCRF2036 is a policy and charging control policy decision point for traffic data flows and IP bearer resources, which selects and provides available policy and charging control decisions for a policy and charging enforcement function (not shown).
IP services 204 may include the internet, intranets, IMS (IP Multimedia Subsystem ), or other IP services, etc.
Although the LTE system is described above as an example, it should be understood by those skilled in the art that the present application is not limited to LTE systems, but may be applied to other wireless communication systems, such as GSM, CDMA2000, WCDMA, TD-SCDMA, and future new network systems.
Based on the above mobile terminal hardware structure and the communication network system, various embodiments of the method of the present application are provided.
First embodiment
As shown in fig. 3, a first embodiment of the present application provides a power consumption management and control method, which is used for a terminal, and the power consumption management and control method includes:
step S31, under the condition that the first application program runs, a second application program for providing services for the first application program is started.
In this embodiment, when the first application program runs, if the service provided by the second application program needs to be used, the second application program is started
In one embodiment, the launching the second application program that provides services to the first application program while the first application program is running includes:
detecting a call instruction of the first application program to the second application program under the condition that the first application program runs;
acquiring a package name of the second application program under the condition that a call instruction of the first application program to the second application program is detected;
determining whether the package name of the second application program is in the white list of the first application program;
and starting the second application program under the condition that the package name of the second application program is in the white list of the first application program.
In this embodiment, the invocation of other applications by the first application may be detected by an API (Application Programming Interface ) of the end system. Wherein the first application and the second application are different applications, for example the first application is a panning application, and the second application is a payment application, a camera application, a text input application, etc.
In this embodiment, the whitelist of the first application may be set by a software manner or set at a setting interface of the terminal, and is not limited herein in particular.
As an example, please refer to fig. 4, in the call setting interface of the first application program, an application program C, F is set to make a call, and an application program A, B, D, E cannot make a call. Thus, when a C or F application is invoked, the C or F application may be launched directly.
In another embodiment, the determining whether the package name of the second application is in the white list of the first application further includes:
and prohibiting the second application program from being started under the condition that the package name of the second application program is not in the white list of the first application program.
Still following the above example, when the A, B, D, E application is invoked, the corresponding application is prohibited from being launched.
Step S32, determining whether there is interaction between the first application program and the second application program in the case where the second application program is started.
In this embodiment, the interaction between the first application and the second application may be performed through application components such as Content Provider, broadcast, and bind Service. The Content Provider can cross-process access data (returned in a Cursor object form) in other application programs, and of course, the Content Provider can also perform addition, deletion and modification operations on the data of other application programs; broadcast can send broadcasts to all applications in the system, while applications requiring cross-process communication can listen to these broadcasts; the bind Service is similar to the Content Provider and can access data in other applications, but the difference is that the Content Provider returns a current object and the bind Service returns a Java object.
In one embodiment, the determining whether there is interaction between the first application and the second application when the second application is started further includes:
judging whether the interaction between the first application program and the second application program is malicious or not under the condition that the interaction between the first application program and the second application program exists;
and under the condition that the interaction between the first application program and the second application program is malicious interaction, logging off the second application program.
In this embodiment, when it is determined that the interaction between the first application program and the second application program is malicious interaction, the second application program is directly logged out, so that the second application program for preventing malicious interaction occupies the memory of the terminal system, and the battery power of the terminal is consumed.
In this embodiment, when there is an interaction between the first application and the second application, determining whether the interaction between the first application and the second application is a malicious interaction includes:
under the condition that interaction exists between the first application program and the second application program, acquiring interaction data and interaction frequency between the first application program and the second application program;
and judging whether the interaction between the first application program and the second application program is malicious or not according to the interaction data and the interaction frequency between the first application program and the second application program.
Specifically, the determining whether the interaction between the first application program and the second application program is malicious according to the interaction data and the interaction frequency between the first application program and the second application program includes:
and if the interaction data are null data and the interaction frequency is fixed frequency, judging that the interaction between the first application program and the second application program is malicious interaction.
And step S33, logging off the second application program under the condition that no interaction exists between the first application program and the second application program.
In this embodiment, when it is determined that there is no interaction between the first application program and the second application program, the second application program is logged out, so that the second application program capable of avoiding malicious interaction occupies the memory of the terminal system, and the battery power of the terminal is consumed.
In one embodiment, said logging off the second application without interaction between the first application and the second application comprises:
recording the time of no interaction between the first application program and the second application program under the condition that no interaction exists between the first application program and the second application program;
and under the condition that the time of no interaction between the first application program and the second application program exceeds the preset time, logging off the second application program.
In this embodiment, when it is determined that the time in which there is no interaction between the first application and the second application exceeds a preset time, the second application is logged off. It is easily conceivable that the interaction is continued if the interaction between the first application and the second application is again performed within a preset time.
In one embodiment, the logging off the second application without interaction between the first application and the second application further comprises:
acquiring the current battery power or memory of the terminal;
and executing the step of logging out the second application program under the condition that no interaction exists between the first application program and the second application program under the condition that the current battery level of the terminal is lower than a preset battery level threshold value or the current memory of the terminal is lower than a preset memory threshold value.
In this embodiment, when it is determined that the current electric quantity is too low or the current memory is insufficient, in order to save the electric quantity and the memory space of the terminal, the second application program may be logged out when there is no interaction between the first application program and the second application program, so as to save the electric quantity and the memory of the terminal. The preset battery power threshold and the preset memory threshold may be set by default or manually by a user, and the embodiment is not limited specifically.
According to the power consumption management and control method, a second application program providing services for the first application program is started through the first application program, and the second application program is logged off when no interaction exists between the first application program and the second application program; the problem that the user experience effect is poor due to the fact that the cruising ability of the mobile terminal is affected by mutual pulling among application programs in the existing mobile terminal is solved; the power consumption of the terminal is reduced, and the user experience is improved.
Second embodiment
As shown in fig. 5, a second embodiment of the present application provides a terminal, the terminal including a memory 41, a processor 42, and a power consumption management program stored in the memory 41 and executable on the processor 42, wherein the power consumption management program is configured to implement the following steps of the power consumption management method when executed by the processor 42:
under the condition that a first application program runs, starting a second application program for providing services for the first application program;
determining whether there is interaction between the first application and the second application if the second application is launched;
and logging off the second application program under the condition that no interaction exists between the first application program and the second application program.
The power consumption management and control program is further configured to implement the following steps of the power consumption management and control method when executed by the processor 42:
and determining whether interaction exists between the first application program and the second application program under the condition that the second application program is started, and then further comprising:
judging whether the interaction between the first application program and the second application program is malicious or not under the condition that the interaction between the first application program and the second application program exists;
and under the condition that the interaction between the first application program and the second application program is malicious interaction, logging off the second application program.
The power consumption management and control program is further configured to implement the following steps of the power consumption management and control method when executed by the processor 42:
the determining whether the interaction between the first application program and the second application program is malicious or not under the condition that the interaction between the first application program and the second application program exists comprises:
under the condition that interaction exists between the first application program and the second application program, acquiring interaction data and interaction frequency between the first application program and the second application program;
and judging whether the interaction between the first application program and the second application program is malicious or not according to the interaction data and the interaction frequency between the first application program and the second application program.
The power consumption management and control program is further configured to implement the following steps of the power consumption management and control method when executed by the processor 42:
the determining whether the interaction between the first application program and the second application program is malicious or not according to the interaction data and the interaction frequency between the first application program and the second application program comprises:
and if the interaction data are null data and the interaction frequency is fixed frequency, judging that the interaction between the first application program and the second application program is malicious interaction.
The power consumption management and control program is further configured to implement the following steps of the power consumption management and control method when executed by the processor 42:
said logging off said second application without interaction between said first application and said second application, further comprising:
acquiring the current battery power or memory of the terminal;
and executing the step of logging out the second application program under the condition that no interaction exists between the first application program and the second application program under the condition that the current battery level of the terminal is lower than a preset battery level threshold value or the current memory of the terminal is lower than a preset memory threshold value.
The power consumption management and control program is further configured to implement the following steps of the power consumption management and control method when executed by the processor 42:
said logging off the second application without interaction between the first application and the second application comprises:
recording the time of no interaction between the first application program and the second application program under the condition that no interaction exists between the first application program and the second application program;
and under the condition that the time of no interaction between the first application program and the second application program exceeds the preset time, logging off the second application program.
The power consumption management and control program is further configured to implement the following steps of the power consumption management and control method when executed by the processor 42:
the method for starting the second application program for providing services for the first application program under the condition that the first application program runs comprises the following steps:
detecting a call instruction of the first application program to the second application program under the condition that the first application program runs;
acquiring a package name of the second application program under the condition that a call instruction of the first application program to the second application program is detected;
determining whether the package name of the second application program is in the white list of the first application program;
and starting the second application program under the condition that the package name of the second application program is in the white list of the first application program.
The power consumption management and control program is further configured to implement the following steps of the power consumption management and control method when executed by the processor 42:
the determining whether the package name of the second application program is in the white list of the first application program further comprises:
and prohibiting the second application program from being started under the condition that the package name of the second application program is not in the white list of the first application program.
According to the terminal provided by the embodiment of the application, the second application program for providing services for the first application program is started through the first application program, and the second application program is logged off when no interaction exists between the first application program and the second application program; the problem that the user experience effect is poor due to the fact that the cruising ability of the mobile terminal is affected by mutual pulling among application programs in the existing mobile terminal is solved; the power consumption of the terminal is reduced, and the user experience is improved.
Third embodiment
A third embodiment of the present application provides a computer-readable storage medium having stored thereon a power consumption management and control program for implementing the steps of the power consumption management and control method described in the first embodiment when the power consumption management and control program is executed by a processor.
It should be noted that, the computer readable storage medium of the present embodiment belongs to the same concept as the method of the first embodiment, the specific implementation process of the computer readable storage medium is detailed in the method embodiment, and the technical features of the method embodiment are correspondingly applicable in the present embodiment, which is not repeated herein.
The computer readable storage medium of the embodiment of the application starts a second application program providing service for the first application program through the first application program, and logs off the second application program when no interaction exists between the first application program and the second application program; the problem that the user experience effect is poor due to the fact that the cruising ability of the mobile terminal is affected by mutual pulling among application programs in the existing mobile terminal is solved; the power consumption of the terminal is reduced, and the user experience is improved.
Those of ordinary skill in the art will appreciate that all or some of the steps, systems, functional modules/units in the apparatus, and methods disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between the functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed cooperatively by several physical components. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as known to those skilled in the art. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer. Furthermore, as is well known to those of ordinary skill in the art, communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media.
The preferred embodiments of the present application have been described above with reference to the accompanying drawings, and thus do not limit the scope of the claims of the present application. Any modifications, equivalent substitutions and improvements made by those skilled in the art without departing from the scope and spirit of the present application shall fall within the scope of the appended claims.
Claims (6)
1. A power consumption management and control method for a terminal, the power consumption management and control method comprising:
under the condition that a first application program runs, starting a second application program for providing services for the first application program;
determining whether there is interaction between the first application and the second application if the second application is launched;
logging off the second application program under the condition that no interaction exists between the first application program and the second application program;
and determining whether interaction exists between the first application program and the second application program under the condition that the second application program is started, and then further comprising:
judging whether the interaction between the first application program and the second application program is malicious or not under the condition that the interaction between the first application program and the second application program exists; logging off the second application program under the condition that the interaction between the first application program and the second application program is malicious interaction;
the determining whether the interaction between the first application program and the second application program is malicious or not under the condition that the interaction between the first application program and the second application program exists comprises:
under the condition that interaction exists between the first application program and the second application program, acquiring interaction data and interaction frequency between the first application program and the second application program; judging whether the interaction between the first application program and the second application program is malicious or not according to the interaction data and the interaction frequency between the first application program and the second application program;
the determining whether the interaction between the first application program and the second application program is malicious or not according to the interaction data and the interaction frequency between the first application program and the second application program comprises:
if the interaction data are null data and the interaction frequency is fixed frequency, judging that the interaction between the first application program and the second application program is malicious interaction;
said logging off the second application without interaction between the first application and the second application comprises:
recording the time of no interaction between the first application program and the second application program under the condition that no interaction exists between the first application program and the second application program; and under the condition that the time of no interaction between the first application program and the second application program exceeds the preset time, logging off the second application program.
2. The power consumption management method according to claim 1, wherein the logging off the second application without interaction between the first application and the second application further comprises:
acquiring the current battery power or memory of the terminal;
and executing the step of logging out the second application program under the condition that no interaction exists between the first application program and the second application program under the condition that the current battery level of the terminal is lower than a preset battery level threshold value or the current memory of the terminal is lower than a preset memory threshold value.
3. The power consumption management method according to claim 1, wherein the launching of the second application program serving the first application program in the case where the first application program is running includes:
detecting a call instruction of the first application program to the second application program under the condition that the first application program runs;
acquiring a package name of the second application program under the condition that a call instruction of the first application program to the second application program is detected;
determining whether the package name of the second application program is in the white list of the first application program;
and starting the second application program under the condition that the package name of the second application program is in the white list of the first application program.
4. The power consumption management method according to claim 3, wherein the determining whether the package name of the second application is in the white list of the first application further comprises:
and prohibiting the second application program from being started under the condition that the package name of the second application program is not in the white list of the first application program.
5. A terminal comprising a memory, a process and a power consumption management program stored on the memory and executable on a processor, which power consumption management program when executed by the processor implements the steps of the power consumption management method according to any of claims 1 to 4.
6. A computer readable storage medium, wherein a power consumption management program is stored on the computer readable storage medium, which when executed by a processor implements the steps of the power consumption management method according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910329918.3A CN110087290B (en) | 2019-04-23 | 2019-04-23 | Power consumption management and control method, terminal and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910329918.3A CN110087290B (en) | 2019-04-23 | 2019-04-23 | Power consumption management and control method, terminal and computer readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110087290A CN110087290A (en) | 2019-08-02 |
| CN110087290B true CN110087290B (en) | 2023-08-11 |
Family
ID=67416192
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910329918.3A Active CN110087290B (en) | 2019-04-23 | 2019-04-23 | Power consumption management and control method, terminal and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110087290B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114666874A (en) * | 2020-12-22 | 2022-06-24 | 华为技术有限公司 | Terminal device and application program interaction method, device and medium thereof |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107181700A (en) * | 2017-07-19 | 2017-09-19 | 努比亚技术有限公司 | Control method, mobile terminal and the storage medium of application program for mobile terminal |
| CN107734616A (en) * | 2017-10-31 | 2018-02-23 | 广东欧珀移动通信有限公司 | Closing application program method, apparatus, storage medium and electronic equipment |
| CN107831886A (en) * | 2017-11-21 | 2018-03-23 | 广东欧珀移动通信有限公司 | Association starts management-control method, device, storage medium and the intelligent terminal of application |
| CN107862203A (en) * | 2017-11-21 | 2018-03-30 | 广东欧珀移动通信有限公司 | Control method, device, storage medium and the terminal of application program |
| CN107861773A (en) * | 2017-11-21 | 2018-03-30 | 广东欧珀移动通信有限公司 | Associate management-control method, device, storage medium and the mobile terminal started |
| CN107943650A (en) * | 2017-11-21 | 2018-04-20 | 广东欧珀移动通信有限公司 | Control method, device, storage medium and the terminal of application program |
| CN107944277A (en) * | 2017-11-21 | 2018-04-20 | 广东欧珀移动通信有限公司 | Using the control method of startup, device, storage medium and intelligent terminal |
| CN107944258A (en) * | 2017-11-21 | 2018-04-20 | 广东欧珀移动通信有限公司 | Start control method, device, storage medium and the terminal of application with method of service |
-
2019
- 2019-04-23 CN CN201910329918.3A patent/CN110087290B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107181700A (en) * | 2017-07-19 | 2017-09-19 | 努比亚技术有限公司 | Control method, mobile terminal and the storage medium of application program for mobile terminal |
| CN107734616A (en) * | 2017-10-31 | 2018-02-23 | 广东欧珀移动通信有限公司 | Closing application program method, apparatus, storage medium and electronic equipment |
| CN107831886A (en) * | 2017-11-21 | 2018-03-23 | 广东欧珀移动通信有限公司 | Association starts management-control method, device, storage medium and the intelligent terminal of application |
| CN107862203A (en) * | 2017-11-21 | 2018-03-30 | 广东欧珀移动通信有限公司 | Control method, device, storage medium and the terminal of application program |
| CN107861773A (en) * | 2017-11-21 | 2018-03-30 | 广东欧珀移动通信有限公司 | Associate management-control method, device, storage medium and the mobile terminal started |
| CN107943650A (en) * | 2017-11-21 | 2018-04-20 | 广东欧珀移动通信有限公司 | Control method, device, storage medium and the terminal of application program |
| CN107944277A (en) * | 2017-11-21 | 2018-04-20 | 广东欧珀移动通信有限公司 | Using the control method of startup, device, storage medium and intelligent terminal |
| CN107944258A (en) * | 2017-11-21 | 2018-04-20 | 广东欧珀移动通信有限公司 | Start control method, device, storage medium and the terminal of application with method of service |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110087290A (en) | 2019-08-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112004173B (en) | Bluetooth headset switching method, mobile terminal and computer readable storage medium | |
| CN109195143B (en) | Network access method, mobile terminal and readable storage medium | |
| CN109195213B (en) | Mobile terminal screen control method, mobile terminal and computer readable storage medium | |
| CN109144705B (en) | Application management method, mobile terminal and computer readable storage medium | |
| CN110187808B (en) | Dynamic wallpaper setting method and device and computer-readable storage medium | |
| CN112689191B (en) | Screen projection control method, terminal and computer readable storage medium | |
| CN110187925B (en) | Desktop pre-starting control method, device and computer readable storage medium | |
| CN110096375B (en) | Method and device for sharing data by application programs and computer readable storage medium | |
| CN112637410B (en) | Method, terminal and storage medium for displaying message notification | |
| CN109766119B (en) | Recovery partition upgrade method, terminal and computer readable storage medium | |
| CN108958936B (en) | Application program switching method, mobile terminal and computer readable storage medium | |
| CN111427709B (en) | Application program splitting control method, device and computer readable storage medium | |
| CN112261535A (en) | Major-minor switching method and device for wireless earphone and readable storage medium | |
| CN109977040B (en) | File read-write permission control method, device, terminal and storage medium | |
| CN109545120B (en) | Screen light sensor adjusting method, mobile terminal and computer readable storage medium | |
| CN108579081B (en) | Event processing method, device and computer storage medium based on game | |
| CN111970738B (en) | Network switching control method, device and computer readable storage medium | |
| CN112866804B (en) | Screen projection self-adaption method, mobile terminal and readable storage medium | |
| CN109388947B (en) | Background management method, device and computer readable storage medium | |
| CN109889660B (en) | Temporary information recording method, storage medium and mobile terminal | |
| CN109684020B (en) | Theme switching method, device and computer readable storage medium | |
| CN109151201B (en) | Anti-addiction method, mobile terminal and computer storage medium | |
| CN110087290B (en) | Power consumption management and control method, terminal and computer readable storage medium | |
| CN110955397A (en) | Method for setting frame rate of game terminal, game terminal and storage medium | |
| CN108040330B (en) | WiFi directional transmission method, mobile terminal and readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |