CN107277905B - System management method and device - Google Patents

System management method and device Download PDF

Info

Publication number
CN107277905B
CN107277905B CN201710534956.3A CN201710534956A CN107277905B CN 107277905 B CN107277905 B CN 107277905B CN 201710534956 A CN201710534956 A CN 201710534956A CN 107277905 B CN107277905 B CN 107277905B
Authority
CN
China
Prior art keywords
idle
application
power
consumption event
broadcast
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
Application number
CN201710534956.3A
Other languages
Chinese (zh)
Other versions
CN107277905A (en
Inventor
刘鸣
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Xiaomi Mobile Software Co Ltd
Original Assignee
Beijing Xiaomi Mobile Software Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Xiaomi Mobile Software Co Ltd filed Critical Beijing Xiaomi Mobile Software Co Ltd
Priority to CN201710534956.3A priority Critical patent/CN107277905B/en
Publication of CN107277905A publication Critical patent/CN107277905A/en
Application granted granted Critical
Publication of CN107277905B publication Critical patent/CN107277905B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

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/0251—Power saving arrangements in terminal devices using monitoring of local events, e.g. events related to user activity
    • H04W52/0258—Power saving arrangements in terminal devices using monitoring of local events, e.g. events related to user activity controlling an operation mode according to history or models of usage information, e.g. activity schedule or time of day
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • 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/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0248—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal dependent on the time of the day, e.g. according to expected transmission activity
    • 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

Abstract

The present disclosure provides a system management method and device, the system management method comprising: setting an idle running port of the system, wherein the idle running port is used for being called to process a high-power-consumption event when the system meets an idle condition; monitoring whether the system accords with an idle condition, and if so, sending idle time broadcast to an application which is registered to receive the idle time broadcast; and the application receiving the idle broadcast calls a system idle running port to process the high-power-consumption event. The high-power-consumption event processing is carried out when the system is idle, the normal use of a user is not influenced, and the insufficient electric quantity of equipment when the user wants to use is avoided.

Description

System management method and device
Technical Field
The present disclosure relates to the field of electronic communications technologies, and in particular, to a system management method and device.
Background
When a user uses a system management device, various Applications (APPs) are usually installed to meet various requirements, such as a chat Application, a taxi-taking Application, a browser Application, and the like. These applications may start on their own at irregular times, network detect messages, exchange data, etc. When the application installed on the system management equipment is started by itself to perform data transmission, such as downloading, updating and upgrading the application, the power consumption of the system management equipment is high, and if the application installed on the system management equipment is downloaded, updated or upgraded when a user is using the system management equipment, the system management equipment generates heat and the electric quantity is insufficient, so that the normal use of the user is influenced.
Disclosure of Invention
The embodiment of the disclosure provides a system management method and equipment. The technical scheme is as follows:
according to a first aspect of the embodiments of the present disclosure, there is provided a system management method applied to a system management device, the method including:
setting an idle running port of the system, wherein the idle running port is used for being called to process a high-power-consumption event when the system meets an idle condition;
monitoring whether the system accords with an idle condition, and if so, sending idle time broadcast to an application which is registered to receive the idle time broadcast;
and the application receiving the idle broadcast calls a system idle running port to process the high-power-consumption event.
The high-power-consumption event processing is carried out when the system is idle, the normal use of a user is not influenced, and the insufficient electric quantity of equipment when the user wants to use is avoided.
In one embodiment, the method further comprises:
receiving a registration request of an application with a large power consumption event processing requirement for idle broadcast reception; the application is recorded in an application list broadcast on the fly.
The applications with the high-power-consumption event processing requirements are recorded in an application list broadcasted during idle receiving in advance, the applications can be directly started to process the high-power-consumption events when the system is idle, and the normal use of a user cannot be influenced.
In one embodiment, if an application having a high power consumption event processing requirement is recorded in an application list received from an idle-time broadcast, the application received from the idle-time broadcast calls a system idle-time operation port to perform high power consumption event processing, including:
and awakening the application which receives the idle broadcast, and calling a system idle running port to load and process the high-power-consumption event to be processed.
In one embodiment, if a to-be-processed high power consumption event of an application is recorded in an application list received from an idle-time broadcast, the application receiving the idle-time broadcast calls a system idle-time running port to perform high power consumption event processing, including:
and the application receiving the idle broadcast calls a system idle running port to process the registered high-power-consumption event to be processed.
In one embodiment, the method further comprises:
and after the high-power-consumption event is processed, clearing the record corresponding to the processed high-power-consumption event in the registered items.
In one embodiment, the method further comprises:
if a high-power-consumption event processing request of a user is received and a function of processing the high-power-consumption event in idle time is started, an application of the high-power-consumption event to be processed sends a registration request for broadcasting in idle time;
and executing a registration request of the application with the large-power-consumption event processing requirement for idle broadcasting, and recording the application in an application list for receiving the idle broadcasting.
When the user actively controls and processes the high-power-consumption event, the processing time is still controlled through idle broadcasting, and the high-power-consumption event processing is ensured to be carried out when the system meets the idle condition.
In one embodiment, determining whether the monitoring system meets an idle condition comprises:
and when the time condition, the electric quantity condition, the networking condition and/or the operation condition are judged to be met, determining that the system meets the idle condition.
When the time condition, the power condition, the networking condition and/or the operation condition are met, the started application or process is less, and at the moment, the user is not using the system, and the system can be determined to be in accordance with the idle condition.
In one embodiment, the method further comprises:
if the fact that the process of the running high-power-consumption event exists when the system is monitored not to meet the idle condition, ending the process, and recording the high-power-consumption event in an idle broadcast list;
and if the execution monitoring system meets the idle condition, transmitting idle time broadcast to the application which is registered to receive the idle time broadcast.
If the system is not in accordance with the idle condition, the running process of the high power consumption event is ended so as to avoid influencing the use of the user, and the user experience is further improved.
According to a second aspect of embodiments of the present disclosure, there is provided a system management apparatus, including: the device comprises a setting module, a monitoring module and a processing module;
the setting module is used for setting an idle running port of the system, and the idle running port is used for being called to process a high-power-consumption event when the system meets an idle condition;
the monitoring module is used for monitoring whether the system meets the idle condition or not, and if the system meets the idle condition, the monitoring module sends idle time broadcast to the application which is registered to receive the idle time broadcast;
and the processing module is used for receiving the application of the idle broadcast and calling the system idle running port to process the high-power-consumption event.
In one embodiment, the system management apparatus further includes: a registration module;
the registration module is used for receiving a registration request which is received by an application with a large power consumption event processing requirement for idle broadcast; the application is recorded in an application list broadcast on the fly.
In one embodiment, if an application with a large power consumption event processing requirement is recorded in an application list broadcasted in idle time, the processing module comprises an application awakening sub-module;
and the application awakening submodule is used for receiving the application broadcasted in idle time and awakening, calling a system idle time operation port to load and process the high power consumption event to be processed.
In one embodiment, if a high power consumption event to be processed of an application is recorded in an application list broadcasted in an idle state, the processing module comprises an event processing submodule;
and the event processing submodule is used for receiving the idle-time broadcast and calling the idle-time running port of the system to process the registered high-power-consumption event to be processed.
In one embodiment, the registration module is further configured to clear the record corresponding to the processed high power consumption event in the registered event after the high power consumption event is processed.
In one embodiment, the registration module includes a request submodule and a record submodule;
the request submodule is used for sending a registration request for idle broadcast by an application of a high-power-consumption event to be processed when receiving a high-power-consumption event processing request of a user and starting a function of processing the high-power-consumption event in idle;
and the recording submodule is used for executing a registration request of the application with the large power consumption event processing requirement for idle broadcasting and recording the application in an application list for receiving the idle broadcasting.
In one embodiment, the monitoring module includes a judgment sub-module;
and the judgment submodule is used for determining that the system meets the idle condition when judging that the time condition, the electric quantity condition, the networking condition and/or the operation condition are met.
In one embodiment, the system management device further comprises a process management module;
the process management module is used for ending the process when the process of the running high-power-consumption event exists when the system is monitored not to conform to the idle condition, and recording the high-power-consumption event in an idle broadcast list; and if the execution monitoring system meets the idle condition, transmitting idle time broadcast to the application which is registered to receive the idle time broadcast.
According to a third aspect of the embodiments of the present disclosure, there is provided a system management apparatus, including:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to:
setting an idle running port of the system, wherein the idle running port is used for being called to process a high-power-consumption event when the system meets an idle condition;
monitoring whether the system accords with an idle condition, and if so, sending idle time broadcast to an application which is registered to receive the idle time broadcast;
and the application receiving the idle broadcast calls a system idle running port to process the high-power-consumption event.
In one embodiment, the processor may be further configured to:
receiving a registration request of an application with a large power consumption event processing requirement for idle broadcast reception; the application is recorded in an application list broadcast on the fly.
In one embodiment, if an application with a large power consumption event processing requirement is recorded in the idle-time broadcast receiving application list, the processor may be further configured to:
and awakening the application which receives the idle broadcast, and calling a system idle running port to load and process the high-power-consumption event to be processed.
In one embodiment, if the pending high power consumption event of the application is recorded in the idle-time broadcast application list, the processor may be further configured to:
and the application receiving the idle broadcast calls a system idle running port to process the registered high-power-consumption event to be processed.
In one embodiment, the processor may be further configured to:
and after the high-power-consumption event is processed, clearing the record corresponding to the processed high-power-consumption event in the registered items.
In one embodiment, the processor may be further configured to:
if a high-power-consumption event processing request of a user is received and a function of processing the high-power-consumption event in idle time is started, an application of the high-power-consumption event to be processed sends a registration request for broadcasting in idle time;
and executing a registration request of the application with the large-power-consumption event processing requirement for idle broadcasting, and recording the application in an application list for receiving the idle broadcasting.
In one embodiment, the processor may be further configured to:
and when the time condition, the electric quantity condition, the networking condition and/or the operation condition are judged to be met, determining that the system meets the idle condition.
In one embodiment, the processor may be further configured to:
if the fact that the process of the running high-power-consumption event exists when the system is monitored not to meet the idle condition, ending the process, and recording the high-power-consumption event in an idle broadcast list;
and if the execution monitoring system meets the idle condition, transmitting idle time broadcast to the application which is registered to receive the idle time broadcast.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure.
FIG. 1 is a flow diagram illustrating a system management method in accordance with an exemplary embodiment;
FIG. 2 is a flow diagram illustrating a system management method in accordance with an exemplary embodiment;
FIG. 3 is a block diagram of a system management device shown in accordance with an exemplary embodiment;
FIG. 4 is a block diagram of a system management device shown in accordance with an exemplary embodiment;
FIG. 5 is a block diagram of a system management device shown in accordance with an exemplary embodiment;
FIG. 6 is a block diagram of a system management device shown in accordance with an exemplary embodiment;
FIG. 7 is a block diagram of a system management device shown in accordance with an exemplary embodiment;
FIG. 8 is a block diagram of a system management device shown in accordance with an exemplary embodiment;
FIG. 9 is a block diagram of a system management device shown in accordance with an exemplary embodiment;
FIG. 10 is a block diagram of a system management device shown in accordance with an exemplary embodiment;
fig. 11 is a block diagram of a terminal device shown according to an example embodiment.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.
When the application installed on the system management equipment is started by itself to perform data transmission, such as downloading, updating and upgrading the application, the power consumption of the system management equipment is high, and if the application installed on the system management equipment is downloaded, updated or upgraded when a user is using the system management equipment, the system management equipment generates heat and the electric quantity is insufficient, so that the normal use of the user is influenced. According to the technical scheme provided by the embodiment of the disclosure, a system idle running port is set, and the idle running port is used for being called to process a high-power-consumption event when the system meets an idle condition; monitoring whether the system accords with an idle condition, and if so, sending idle time broadcast to an application which is registered to receive the idle time broadcast; and the application receiving the idle broadcast calls a system idle running port to process the high-power-consumption event. The high-power-consumption event processing is carried out when the system is idle, the normal use of a user is not influenced, and the insufficient electric quantity of equipment when the user wants to use is avoided.
Fig. 1 is a flowchart illustrating a system management method according to an exemplary embodiment, where the system management method includes steps 101 and 103:
in step 101, a system idle run port is set.
The idle-time operation port is used for being called to process a large power consumption event when the system accords with an idle condition.
The high power consumption event refers to an event that the data processing amount is larger than the preset data amount, for example, downloading, updating, upgrading and the like, and when the high power consumption event is processed, the system management device generates heat and the power consumption speed is high.
In step 102, it is monitored whether the system meets an idle condition, and if the system meets the idle condition, the idle broadcast is sent to an application registered to receive the idle broadcast.
Whether the detection system meets the idle condition or not can be monitored periodically, and also can be monitored at a plurality of preset time points or periodically within a preset time period, and the specific form of monitoring is not limited in the disclosure.
In one embodiment, determining whether the monitoring system meets the idle condition includes, but is not limited to:
and when the time condition, the electric quantity condition, the networking condition and/or the operation condition are/is judged to be met, determining that the system meets the idle condition and the like. In practical application, the idle condition may be determined according to a determination principle set, may be determined according to the system memory occupancy rate when one or more of a time condition, an electric quantity condition, a networking condition, and an operating condition is satisfied, and may be specifically set according to an actual requirement, which is not limited herein. The time condition is to determine whether a predetermined time period, such as night (1: 00-5: 00), is satisfied. The charge condition is to determine whether the charge is sufficient, such as the charge of the mobile phone is greater than 80%, and/or the mobile phone is being charged. The networking condition is to determine whether the network is connected or whether the traffic is sufficient, such as wifi connection. The operation status is to determine the operation status of the mobile phone by the user, and may be selected when the user does not operate the mobile phone, for example, when the screen is locked for more than 30 minutes.
When the time condition, the power condition, the networking condition and/or the operation condition are met, the started application or process is less, and at the moment, the user is not using the system, and the system can be determined to be in accordance with the idle condition. Here, three examples are listed to illustrate how to specifically determine whether the system management device is in an idle state, which is, of course, merely an exemplary illustration and is not meant to limit the present disclosure thereto:
in a first embodiment, monitoring whether the system meets an idle condition includes: and when the memory occupancy rate of the system exceeds the preset occupancy rate, determining that the system meets the idle condition.
The low system memory occupancy rate indicates that the number of started applications or processes is small, and at the moment, the user is not using the system, so that the system can be determined to be in accordance with the idle condition.
In a second embodiment, monitoring whether the system meets an idle condition includes: determining whether the time length of continuous screen locking exceeds a preset time length; and when the time length of the continuous screen locking exceeds the preset time length, determining that the system meets the idle condition.
Generally, a user locks a screen of the system management device when the user does not use the system management device, and if the screen locking time length of the system management device is long, it indicates that the user is likely not to use the system management device for a long time, and at this time, it may be determined that the system management device is in an idle state. Taking a smart phone as an example, when a user does not use the smart phone, the user usually actively locks the screen, and many users can set automatic screen locking, so that when the screen locking time of the smart phone is long, the user can be determined that the user does not use the smart phone.
In a third embodiment, monitoring whether the system meets an idle condition includes: determining whether the current time belongs to a preset time period; and when the current time belongs to the preset time period, determining that the system meets the idle condition.
The user typically does not use the system management device for some preset periods of time, e.g., some users do not use the system management device during working hours and some users do not use the system management device during nighttime. Therefore, at the time of the preset time period, it can be determined that the system management device is in the idle state. For example, the preset time period may be 1:00 to 5:00 a.m. a period of time during which the user is sleeping and not using the mobile phone.
It should be noted that, several conditions of time condition, power condition, networking condition, and operation condition may be combined at will, for example, the system may be determined to be in the idle condition when all of these conditions are met, such as at night (1: 00-5: 00), and when the mobile phone is charging and wifi is connected, and the power of the mobile phone is > 80%, and the screen lock is more than 30 minutes, the system may be determined to be in the idle condition.
In one embodiment, the method further comprises: if the fact that the process of the running high-power-consumption event exists when the system is monitored not to meet the idle condition, ending the process, and recording the high-power-consumption event in an idle broadcast list; and if the execution monitoring system meets the idle condition, transmitting idle time broadcast to the application which is registered to receive the idle time broadcast.
If the system is not in accordance with the idle condition, the running process of the high power consumption event is ended so as to avoid influencing the use of the user, and the user experience is further improved.
In step 103, the application receiving the idle broadcast calls the system idle running port to perform the high power consumption event processing.
The application broadcasted at idle is started and then is subjected to high-power-consumption event processing, the application can be started in various ways, for example, a smart phone with an android system is taken as an example, in one embodiment, a preset application can be started in a system Broadcast (english: Broadcast), and can also be started in a service start (english: Startservice), which is only for example and is not limited to this disclosure.
In one embodiment, if an application having a high power consumption event processing requirement is recorded in an application list received from an idle-time broadcast, the application received from the idle-time broadcast calls a system idle-time operation port to perform high power consumption event processing, including: and awakening the application which receives the idle broadcast, and calling a system idle running port to load and process the high-power-consumption event to be processed.
The following is illustrated for the upper content in combination with the actual application scenario:
1) the system provides an idle running broadcast interface, and any application can register to receive the idle broadcast
2) When the night (1: 00-5: 00) when the mobile phone is charged and connected with wifi, the electric quantity of the mobile phone is greater than 80%, and the screen locking time exceeds 30 minutes, the system sends idle broadcast to the applications registered with the broadcast in a broadcast manner of android standard, and awakens the applications;
3) when the condition of 2 is not satisfied (e.g. time is not met, the mobile phone lights up the screen, etc.), checking whether the applications still survive, and if the applications still run in the background, ending the application process.
In another embodiment, if the to-be-processed high power consumption event of the application is recorded in the application list received from the idle-time broadcast, the application received from the idle-time broadcast calls the system idle-time running port to perform the high power consumption event processing, including: and the application receiving the idle broadcast calls a system idle running port to process the registered high-power-consumption event to be processed.
The following is illustrated for the upper content in combination with the actual application scenario:
1) the system provides an idle running interface, any application can be called, and a service program service (namely a to-be-processed high-power-consumption event of a certain application) needing to be started is transmitted;
2) when the night (1: 00-5: 00) when the mobile phone is charged and connected with wifi, the electric quantity of the mobile phone is greater than 80%, and the screen locking time exceeds 30 minutes, the system starts the application service registered in the step 1 once through a startService mode of the android standard;
3) emptying the registered application list after starting;
4) when the condition of 2 is not met (such as time inconsistency, mobile phone screen lighting and the like), checking whether the started service still survives, and if the started service still runs in the background, ending the process.
In one embodiment, the method further comprises: and after the high-power-consumption event is processed, clearing the record corresponding to the processed high-power-consumption event in the registered items.
In one embodiment, the user may actively control whether to handle the power-hungry event, and the method further comprises: if a high-power-consumption event processing request of a user is received and a function of processing the high-power-consumption event in idle time is started, an application of the high-power-consumption event to be processed sends a registration request for broadcasting in idle time;
and executing a registration request of the application with the large-power-consumption event processing requirement for idle broadcasting, and recording the application in an application list for receiving the idle broadcasting.
When the user actively controls and processes the high-power-consumption event, the processing time is still controlled through idle broadcasting, and the high-power-consumption event processing is ensured to be carried out when the system meets the idle condition.
It should be noted that, furthermore, a large power consumption event can be handled in a case where the power is sufficient. For example, when the power amount is greater than the preset power amount, a high power consumption event is processed. The preset electric quantity may be a percentage value, and when the electric quantity of the system management device is greater than the preset electric quantity, it indicates that the electric quantity of the system management device is sufficient. For example, the preset power amount may be 80% of power amount, and when the power amount of the system management device exceeds 80%, it is determined that the power amount of the system management device is greater than the preset power amount, and at this time, the power amount of the system management device is sufficient.
The system management method provided by the embodiment of the disclosure sets an idle running port of a system, wherein the idle running port is used for being called to process a high-power-consumption event when the system meets an idle condition; monitoring whether the system accords with an idle condition, and if so, sending idle time broadcast to an application which is registered to receive the idle time broadcast; and the application receiving the idle broadcast calls a system idle running port to process the high-power-consumption event. The high-power-consumption event processing is carried out when the system is idle, the normal use of a user is not influenced, and the insufficient electric quantity of equipment when the user wants to use is avoided.
Based on the system management method provided in the embodiment corresponding to fig. 1, fig. 2 is a flowchart of a system management method according to an exemplary embodiment, where in this embodiment, a system management device is a smart phone, for example, and referring to fig. 2, the system management method provided in this embodiment includes steps 201 and 205:
in step 201, a system idle run port is set.
The idle-time operation port is used for being called to process a large power consumption event when the system accords with an idle condition.
In step 202, an application having a high power consumption event processing requirement receives a registration request for broadcasting at idle.
The registration of idle Broadcast reception may be performed in various ways, for example, in an android system, an application may be started in a Broadcast or startservices manner, the system may provide a corresponding preset interface, the application may be registered in the corresponding manner, the registered application may be started when the system is started in the Broadcast or startservices preset interface, and the application that is not registered may not be started.
In step 203, the application is recorded in an application list broadcast on the fly.
The applications with the high-power-consumption event processing requirements are recorded in an application list broadcasted during idle receiving in advance, the applications can be directly started to process the high-power-consumption events when the system is idle, and the normal use of a user cannot be influenced.
It should be noted that, a user may also input a list of applications that are determined to receive idle broadcasts by himself, the user determines which applications need to be started in an idle state by himself, the applications are recorded in a registration list, the applications selected to be started by different users are different, the applications that the user wants to be started in different scenes may also be changed, and preset applications may be started according to the registration list determined by the user in the idle state, so that different requirements of the user are met, and the method is very flexible.
In step 204, it is monitored whether the system meets an idle condition.
Determining whether the system management device is in the idle state may include a number of conditions, and in one embodiment, satisfying the conditions in the idle state may include the following five:
the method comprises the following steps that firstly, whether the memory occupancy rate of the system exceeds a preset occupancy rate or not is judged;
secondly, the time length of continuous screen locking exceeds the preset time length;
thirdly, the current time belongs to a preset time period;
and the condition four is that Wireless Fidelity (WiFi) is connected.
The condition five is that the electric quantity is greater than the preset electric quantity;
when one or more of the above five conditions are satisfied, the system is determined to be in accordance with the idle condition.
Preferably, in one embodiment, the idle condition is met when the above five conditions are met simultaneously. When the condition one is met, the system memory occupancy rate is low; the condition II is met, that is, the screen locking time is long, and the user does not use the screen locking device for a long time; a third condition is met, which indicates that the current time is a preset time period, and the user is unlikely to use the system management equipment; if the condition four is met, the data flow of the user cannot be consumed if tasks such as downloading and updating exist, and if the condition five is met, the electric quantity is sufficient, and the subsequent use of the user cannot be influenced. When the five conditions are met simultaneously, the preset application is started, and the normal use of the system management equipment by the user is not influenced.
When the system meets the idle condition, step 205 and step 207 are executed, and when the system does not meet the idle condition, step 208 and step 209 are executed:
in step 205, the idle broadcast is transmitted to the application registered to receive the idle broadcast.
In step 206, the application receiving the idle broadcast calls the system idle running port to perform the high power consumption event processing.
If a high-power-consumption event processing request of a user is received and a function of processing the high-power-consumption event in idle time is started, an application of the high-power-consumption event to be processed sends a registration request for broadcasting in idle time;
and executing a registration request of the application with the large-power-consumption event processing requirement for idle broadcasting, and recording the application in an application list for receiving the idle broadcasting.
In step 207, after the handling of the high power consumption event is completed, the record corresponding to the processed high power consumption event is cleared in the registered transaction.
For example, the record of the processed power-consuming events is cleared in the application list broadcast when receiving idle.
In step 208, it is checked whether there is a process running a power intensive event.
In step 209, when there is a process of a running power-intensive event, the process is ended.
The system management method provided by the embodiment of the disclosure sets an idle running port of a system, wherein the idle running port is used for being called to process a high-power-consumption event when the system meets an idle condition; monitoring whether the system accords with an idle condition, and if so, sending idle time broadcast to an application which is registered to receive the idle time broadcast; and the application receiving the idle broadcast calls a system idle running port to process the high-power-consumption event. The high-power-consumption event processing is carried out when the system is idle, the normal use of a user is not influenced, and the insufficient electric quantity of equipment when the user wants to use is avoided.
The following are embodiments of the disclosed apparatus that may be used to perform embodiments of the disclosed methods.
Fig. 3 is a block diagram illustrating a system management device according to an exemplary embodiment, which may be implemented by software, hardware or a combination of the two as part or all of a system management device for executing the system management method described in the embodiment corresponding to fig. 1-2. As shown in fig. 3, the system management apparatus 30 includes: a setting module 301, a monitoring module 302 and a processing module 303;
the setting module 301 is configured to set an idle running port of the system, where the idle running port is used to be called to process a high power consumption event when the system meets an idle condition;
a monitoring module 302, configured to monitor whether a system meets an idle condition, and if the system meets the idle condition, send an idle broadcast to an application registered to receive the idle broadcast;
the processing module 303 is configured to receive the application in idle broadcast and invoke the system idle running port to perform high power consumption event processing.
In one embodiment, as shown in fig. 4, the system management device 30 further includes: a registration module 304;
a registration module 304, configured to receive a registration request that is broadcast and received when idle by an application that has a large power consumption event processing requirement; the application is recorded in an application list broadcast on the fly.
In an embodiment, if an application with a large power consumption event processing requirement is recorded in the application list broadcasted during idle time, as shown in fig. 5, the processing module 303 includes an application wake-up sub-module 3031;
and the application awakening submodule 3031 is configured to awaken the application which is broadcast when the system is idle, call a system idle running port to load, and process a to-be-processed high-power-consumption event.
In one embodiment, as shown in fig. 6, if a to-be-processed high power consumption event of an application is recorded in an application list broadcast during idle reception, the processing module 303 includes an event processing sub-module 3032;
and the event processing submodule 3032 is configured to receive an idle-time broadcast application call system idle-time running port and process the registered to-be-processed high-power-consumption event.
In one embodiment, the registration module 304 is further configured to clear the record corresponding to the processed high power consumption event in the registered transaction after the high power consumption event is processed.
In one embodiment, as shown in FIG. 7, registration module 304 includes a request submodule 3041 and a record submodule 3042;
a request submodule 3041, configured to, when receiving a large power consumption event processing request from a user and starting a function of processing a large power consumption event in idle, send a registration request for an idle broadcast by an application of the large power consumption event to be processed;
the recording sub-module 3042 is configured to execute a registration request of an application receiving a high power consumption event processing requirement for idle broadcast, and record the application in an application list receiving the idle broadcast.
In one embodiment, as shown in FIG. 8, the monitoring module 302 includes a decision sub-module 3021;
the judging submodule 3021 is configured to determine that the system meets the idle condition when it is judged that the time condition, the power condition, the networking condition, and/or the operating condition are/is met.
In one embodiment, as shown in FIG. 9, system management device 30 further includes a process management module 305;
the process management module 305 is configured to, when it is monitored that a process of a running high power consumption event exists when the system does not meet the idle condition, end the process, and record the high power consumption event in an idle broadcast list; and if the execution monitoring system meets the idle condition, transmitting idle time broadcast to the application which is registered to receive the idle time broadcast.
The system management device provided by the embodiment of the disclosure sets a system idle running port, wherein the idle running port is used for being called to process a high-power-consumption event when the system meets an idle condition; monitoring whether the system accords with an idle condition, and if so, sending idle time broadcast to an application which is registered to receive the idle time broadcast; and the application receiving the idle broadcast calls a system idle running port to process the high-power-consumption event. The high-power-consumption event processing is carried out when the system is idle, the normal use of a user is not influenced, and the insufficient electric quantity of equipment when the user wants to use is avoided.
Fig. 10 is a block diagram illustrating a system management device according to an exemplary embodiment, which may be implemented by software, hardware or a combination of the two as part or all of a system management device for performing the system management method described in the embodiments corresponding to fig. 1-2. As shown in fig. 10, the system management apparatus 100 includes:
a processor 1001;
a memory 1002 for storing instructions executable by the processor 1001;
wherein the processor 1001 is configured to:
setting an idle running port of the system, wherein the idle running port is used for being called to process a high-power-consumption event when the system meets an idle condition;
monitoring whether the system accords with an idle condition, and if so, sending idle time broadcast to an application which is registered to receive the idle time broadcast;
and the application receiving the idle broadcast calls a system idle running port to process the high-power-consumption event.
In one embodiment, the processor 1001 may be further configured to:
receiving a registration request of an application with a large power consumption event processing requirement for idle broadcast reception; the application is recorded in an application list broadcast on the fly.
In one embodiment, if an application with a large power consumption event processing requirement is recorded in the idle-time broadcast application list, the processor 1001 may be further configured to:
and awakening the application which receives the idle broadcast, and calling a system idle running port to load and process the high-power-consumption event to be processed.
In one embodiment, if a pending high power consumption event of an application is recorded in the idle broadcast application list, the processor 1001 may be further configured to:
and the application receiving the idle broadcast calls a system idle running port to process the registered high-power-consumption event to be processed.
In one embodiment, the processor 1001 may be further configured to:
and after the high-power-consumption event is processed, clearing the record corresponding to the processed high-power-consumption event in the registered items.
In one embodiment, the processor 1001 may be further configured to:
if a high-power-consumption event processing request of a user is received and a function of processing the high-power-consumption event in idle time is started, an application of the high-power-consumption event to be processed sends a registration request for broadcasting in idle time;
and executing a registration request of the application with the large-power-consumption event processing requirement for idle broadcasting, and recording the application in an application list for receiving the idle broadcasting.
In one embodiment, the processor 1001 may be further configured to:
and when the time condition, the electric quantity condition, the networking condition and/or the operation condition are judged to be met, determining that the system meets the idle condition.
In one embodiment, the processor 1001 may be further configured to:
if the fact that the process of the running high-power-consumption event exists when the system is monitored not to meet the idle condition, ending the process, and recording the high-power-consumption event in an idle broadcast list;
and if the execution monitoring system meets the idle condition, transmitting idle time broadcast to the application which is registered to receive the idle time broadcast.
The system management device provided by the embodiment of the disclosure sets a system idle running port, wherein the idle running port is used for being called to process a high-power-consumption event when the system meets an idle condition; monitoring whether the system accords with an idle condition, and if so, sending idle time broadcast to an application which is registered to receive the idle time broadcast; and the application receiving the idle broadcast calls a system idle running port to process the high-power-consumption event. The high-power-consumption event processing is carried out when the system is idle, the normal use of a user is not influenced, and the insufficient electric quantity of equipment when the user wants to use is avoided.
The system management device provided in the embodiment of the present disclosure may be a terminal device as shown in fig. 11, fig. 11 is a block diagram of a terminal device shown according to an exemplary embodiment, the terminal device 110 may be a smart phone, a tablet computer, and the like, and the terminal device 110 is configured to execute the system management method described in the embodiment corresponding to fig. 1 to fig. 2.
Terminal device 110 may include one or more of the following components: processing component 1101, memory 1102, power component 1103, multimedia component 1104, audio component 1105, input/output (I/O) interface 1106, sensor component 1107, and communication component 1108.
The processing component 1101 generally controls the overall operation of the terminal device 110, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 1101 may include one or more processors 11011 to execute instructions to perform all or part of the steps of the methods described above. Further, the processing component 1101 can include one or more modules that facilitate interaction between the processing component 1101 and other components. For example, the processing component 1101 can include a multimedia module to facilitate interaction between the multimedia component 1104 and the processing component 1101.
Memory 1102 is configured to store various types of data to support operation at terminal device 110. Examples of such data include instructions for any application or method operating on terminal device 110, contact data, phonebook data, messages, pictures, videos, and so forth. The Memory 1102 may be implemented by any type or combination of volatile and non-volatile Memory devices, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read Only Memory (EEPROM), Erasable Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), magnetic Memory, flash Memory, magnetic disk, or optical disk.
Power supply component 1103 provides power to the various components of terminal device 110. Power components 1103 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for terminal device 110.
The multimedia component 1104 includes a screen that provides an output interface between the terminal device 110 and the user. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 1104 includes a front facing camera and/or a rear facing camera. The front camera and/or the rear camera may receive external multimedia data when the terminal device 110 is in an operation mode, such as a shooting mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.
Audio component 1105 is configured to output and/or input audio signals. For example, audio component 1105 may include a Microphone (MIC) configured to receive external audio signals when terminal device 110 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may further be stored in memory 1102 or transmitted via communications component 1108. In some embodiments, audio component 1105 further includes a speaker for outputting audio signals.
The I/O interface 1106 provides an interface between the processing component 1101 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to: a home button, a volume button, a start button, and a lock button.
Sensor component 1107 includes one or more sensors to provide various aspects of state estimation for terminal device 110. For example, sensor component 1107 may detect the open/closed state of terminal device 110, the relative positioning of components, such as a display and keypad of terminal device 110, sensor component 1107 may also detect a change in the position of terminal device 110 or a component of terminal device 110, the presence or absence of user contact with terminal device 110, orientation or acceleration/deceleration of terminal device 110, and a change in the temperature of terminal device 110. Sensor assembly 1107 may include a proximity sensor configured to detect the presence of a nearby object in the absence of any physical contact. Sensor assembly 1107 may also include a photosensor, such as a Complementary Metal Oxide Semiconductor (CMOS) or Charge Coupled Device (CCD) image sensor, for use in imaging applications. In some embodiments, the sensor assembly 1107 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
Communication component 1108 is configured to facilitate communications between terminal device 110 and other devices in a wired or wireless manner. Terminal device 110 may access a Wireless network based on a communication standard, such as Wireless-Fidelity (WiFi), 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 1108 receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the Communication component 1108 also includes a Near Field Communication (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, Infrared Data Association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
In an exemplary embodiment, the terminal Device 110 may be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components, for performing the system management methods described in the embodiments corresponding to fig. 1-2.
In an exemplary embodiment, a non-transitory computer readable storage medium is also provided, such as the memory 1102, comprising instructions executable by the processing component 1101 of the terminal device 110 to perform the above-described method. For example, the non-transitory computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like. When executed by the processing component 1101 of the terminal device 110, the instructions in the storage medium enable the terminal device 110 to perform the system management method described in the corresponding embodiments of fig. 1-2 above, the method including:
setting an idle running port of the system, wherein the idle running port is used for being called to process a high-power-consumption event when the system meets an idle condition;
monitoring whether the system accords with an idle condition, and if so, sending idle time broadcast to an application which is registered to receive the idle time broadcast;
and the application receiving the idle broadcast calls a system idle running port to process the high-power-consumption event.
In one embodiment, the method further comprises:
receiving a registration request of an application with a large power consumption event processing requirement for idle broadcast reception; the application is recorded in an application list broadcast on the fly.
In one embodiment, if an application having a high power consumption event processing requirement is recorded in an application list received from an idle-time broadcast, the application received from the idle-time broadcast calls a system idle-time operation port to perform high power consumption event processing, including:
and awakening the application which receives the idle broadcast, and calling a system idle running port to load and process the high-power-consumption event to be processed.
In one embodiment, if a to-be-processed high power consumption event of an application is recorded in an application list received from an idle-time broadcast, the application receiving the idle-time broadcast calls a system idle-time running port to perform high power consumption event processing, including:
and the application receiving the idle broadcast calls a system idle running port to process the registered high-power-consumption event to be processed.
In one embodiment, the method further comprises:
and after the high-power-consumption event is processed, clearing the record corresponding to the processed high-power-consumption event in the registered items.
In one embodiment, the method further comprises:
if a high-power-consumption event processing request of a user is received and a function of processing the high-power-consumption event in idle time is started, an application of the high-power-consumption event to be processed sends a registration request for broadcasting in idle time;
and executing a registration request of the application with the large-power-consumption event processing requirement for idle broadcasting, and recording the application in an application list for receiving the idle broadcasting.
In one embodiment, determining whether the monitoring system meets an idle condition comprises:
and when the time condition, the electric quantity condition, the networking condition and/or the operation condition are judged to be met, determining that the system meets the idle condition.
In one embodiment, the method further comprises:
if the fact that the process of the running high-power-consumption event exists when the system is monitored not to meet the idle condition, ending the process, and recording the high-power-consumption event in an idle broadcast list;
and if the execution monitoring system meets the idle condition, transmitting idle time broadcast to the application which is registered to receive the idle time broadcast.
The terminal device provided by the embodiment of the disclosure sets a system idle running port, wherein the idle running port is used for being called to process a high-power-consumption event when the system meets an idle condition; monitoring whether the system accords with an idle condition, and if so, sending idle time broadcast to an application which is registered to receive the idle time broadcast; and the application receiving the idle broadcast calls a system idle running port to process the high-power-consumption event. The high-power-consumption event processing is carried out when the system is idle, the normal use of a user is not influenced, and the insufficient electric quantity of equipment when the user wants to use is avoided.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims (11)

1. A method of system management, the method comprising:
setting an idle running port of a system, wherein the idle running port is used for being called to process a high-power-consumption event when the system meets an idle condition;
monitoring whether the system accords with an idle condition, and if so, sending idle time broadcast to an application which is registered to receive the idle time broadcast;
receiving an idle broadcast application and calling the system idle running port to process a high-power-consumption event;
the method further comprises the following steps: receiving a registration request of an application with a large power consumption event processing requirement on idle-time broadcasting, and recording the application in an application list for receiving the idle-time broadcasting;
if the application which is recorded in the application list for receiving the idle broadcast has a high power consumption event processing requirement, the application for receiving the idle broadcast calls the system idle running port to perform high power consumption event processing, and the method comprises the following steps:
the application which receives the idle broadcast is awakened, and the system idle running port is called to load and process the high power consumption event to be processed;
if the to-be-processed high-power-consumption event of the application is recorded in the application list for receiving the idle broadcast, the application for receiving the idle broadcast calls the system idle running port to perform high-power-consumption event processing, and the processing comprises the following steps:
and calling the system idle running port by the application receiving the idle broadcast to process the registered high-power-consumption event to be processed.
2. The method of claim 1, further comprising:
if a high-power-consumption event processing request of a user is received and a function of processing the high-power-consumption event in idle time is started, an application of the high-power-consumption event to be processed sends a registration request for broadcasting in idle time;
and executing the registration request of the application receiving the large-power-consumption event processing requirement on idle broadcasting, and recording the application in an application list receiving the idle broadcasting.
3. The method of claim 1, further comprising:
and after the high-power-consumption event is processed, clearing the record corresponding to the processed high-power-consumption event in the registered items.
4. The method of claim 1, wherein determining whether the monitoring system meets an idle condition comprises:
and when the time condition, the electric quantity condition, the networking condition and/or the operation condition are judged to be met, determining that the system meets the idle condition.
5. The method according to any one of claims 1-4, further comprising:
if the fact that the process of the running high-power-consumption event exists when the system is monitored not to meet the idle condition, ending the process, and recording the high-power-consumption event in an idle broadcast list;
and executing whether the monitoring system meets the idle condition, and if so, sending idle time broadcast to the application which is registered to receive the idle time broadcast.
6. A system management device, comprising: the device comprises a setting module, a monitoring module and a processing module;
the setting module is used for setting an idle running port of the system, and the idle running port is used for being called to process a high-power-consumption event when the system meets an idle condition;
the monitoring module is used for monitoring whether the system meets the idle condition or not, and if the system meets the idle condition, the monitoring module sends idle time broadcast to the application which is registered to receive the idle time broadcast;
the processing module is used for receiving the application broadcasted in idle time and calling the system idle time running port to process the high-power-consumption event;
the system management device further includes: a registration module;
the registration module is used for receiving a registration request which is received by an application with a large power consumption event processing requirement and broadcast in idle time; recording the application in an application list broadcasted at idle time;
if the applications with the large power consumption event processing requirements are recorded in the idle-time broadcast receiving application list, the processing module comprises an application awakening sub-module;
the application awakening submodule is used for receiving the application which is broadcasted in idle time and awakening, calling the system idle time operation port to load and processing the high power consumption event to be processed;
if the large power consumption event to be processed of the application is recorded in the idle-time broadcast receiving application list, the processing module comprises an event processing submodule;
and the event processing submodule is used for receiving the idle-time broadcast and calling the system idle-time running port to process the registered high-power-consumption event to be processed.
7. The apparatus of claim 6, wherein the registration module comprises a request submodule and a record submodule;
the request submodule is used for sending a registration request for idle broadcast by an application of a high-power-consumption event to be processed when receiving a high-power-consumption event processing request of a user and starting a function of processing the high-power-consumption event in idle;
the recording sub-module is configured to execute a registration request of the application receiving the high power consumption event processing requirement on the idle broadcast, and record the application in an application list receiving the idle broadcast.
8. The apparatus of claim 6,
and the registration module is also used for clearing the record corresponding to the processed high power consumption event in the registered items after the high power consumption event is processed.
9. The apparatus of claim 6, wherein the monitoring module comprises a determination sub-module;
and the judgment submodule is used for determining that the system meets the idle condition when judging that the time condition, the electric quantity condition, the networking condition and/or the operation condition are met.
10. The apparatus according to any one of claims 6 to 9, wherein the system management apparatus further comprises: a process management module;
the process management module is used for ending a process when the process of a running high-power-consumption event exists when the system is monitored not to conform to an idle condition, and recording the high-power-consumption event in an idle broadcast list; and executing whether the monitoring system meets the idle condition, and if so, sending idle time broadcast to the application which is registered to receive the idle time broadcast.
11. A system management device, comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to:
setting an idle running port of a system, wherein the idle running port is used for being called to process a high-power-consumption event when the system meets an idle condition; monitoring whether the system accords with an idle condition, and if so, sending idle time broadcast to an application which is registered to receive the idle time broadcast;
receiving an idle broadcast application and calling the system idle running port to process a high-power-consumption event;
the processor is further configured to: receiving a registration request of an application with a large power consumption event processing requirement on idle-time broadcasting, and recording the application in an application list for receiving the idle-time broadcasting;
the processor is further configured to: if the application which has the high-power-consumption event processing requirement is recorded in the idle-time broadcast receiving application list, the idle-time broadcast receiving application is awakened, and the system idle-time running port is called to load and process the high-power-consumption event to be processed; if the to-be-processed high power consumption event of the application is recorded in the idle-time broadcast receiving application list, the to-be-processed high power consumption event which is registered is processed by the idle-time broadcast receiving application calling the system idle-time running port.
CN201710534956.3A 2017-07-03 2017-07-03 System management method and device Active CN107277905B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201710534956.3A CN107277905B (en) 2017-07-03 2017-07-03 System management method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201710534956.3A CN107277905B (en) 2017-07-03 2017-07-03 System management method and device

Publications (2)

Publication Number Publication Date
CN107277905A CN107277905A (en) 2017-10-20
CN107277905B true CN107277905B (en) 2021-03-30

Family

ID=60069804

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201710534956.3A Active CN107277905B (en) 2017-07-03 2017-07-03 System management method and device

Country Status (1)

Country Link
CN (1) CN107277905B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108829732B (en) * 2018-05-16 2021-10-19 创新先进技术有限公司 Data processing method and device

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102799447A (en) * 2012-06-19 2012-11-28 优视科技有限公司 Method and system for updating internal software of mobile terminal
CN105045639A (en) * 2015-08-25 2015-11-11 广东欧珀移动通信有限公司 Mobile terminal downloading method and device and mobile terminal
CN105786560A (en) * 2016-01-25 2016-07-20 广东小天才科技有限公司 Upgrading method for application programs and upgrading system for application programs of terminal
CN105824660A (en) * 2015-08-10 2016-08-03 维沃移动通信有限公司 Application program updating method and terminal
CN106533763A (en) * 2016-11-17 2017-03-22 广州优视网络科技有限公司 Method and device for downloading application update package and user terminal
CN106598646A (en) * 2016-11-14 2017-04-26 深圳市金立通信设备有限公司 Program update method and terminal

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9032385B2 (en) * 2011-12-28 2015-05-12 Lg Electronics Inc. Mobile terminal and control method thereof

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102799447A (en) * 2012-06-19 2012-11-28 优视科技有限公司 Method and system for updating internal software of mobile terminal
CN105824660A (en) * 2015-08-10 2016-08-03 维沃移动通信有限公司 Application program updating method and terminal
CN105045639A (en) * 2015-08-25 2015-11-11 广东欧珀移动通信有限公司 Mobile terminal downloading method and device and mobile terminal
CN105786560A (en) * 2016-01-25 2016-07-20 广东小天才科技有限公司 Upgrading method for application programs and upgrading system for application programs of terminal
CN106598646A (en) * 2016-11-14 2017-04-26 深圳市金立通信设备有限公司 Program update method and terminal
CN106533763A (en) * 2016-11-17 2017-03-22 广州优视网络科技有限公司 Method and device for downloading application update package and user terminal

Also Published As

Publication number Publication date
CN107277905A (en) 2017-10-20

Similar Documents

Publication Publication Date Title
EP3188066A1 (en) A method and an apparatus for managing an application
EP2993584B1 (en) Method and device for controlling background application
RU2653238C1 (en) Application update method, device and system
EP3200483B1 (en) Method and device for acquiring location information
CN108334651B (en) Method, device and storage medium for collecting user side data to realize preset requirements
CN105677460A (en) Application processing method and apparatus
CN105979088B (en) Message pushing method and device
EP3112979B1 (en) Method and device for waking up mcu
CN109050470B (en) Automatic locking method and device for vehicle, server and storage medium
EP3382527A1 (en) Method and apparatus for managing a shared storage system
US20160121246A1 (en) Method and device for reminding user about smart water purifier
CN112037787A (en) Wake-up control method, device and computer readable storage medium
EP3474088A1 (en) Method and apparatus for controlling alarm clock
CN107885307B (en) Equipment control method and device
US11800435B2 (en) System message transmission method and device, and system message reception method and device
CN109522058B (en) Wake-up method, device, terminal and storage medium
CN109062625B (en) Application program loading method and device and readable storage medium
CN108347718B (en) Method, device and storage medium for monitoring communication packet
CN107436782B (en) Application silent installation method and device
CN106990984B (en) Method and device for updating system
CN107277905B (en) System management method and device
EP3188566B1 (en) Application management method and device
CN114158018A (en) Data transmission method and device, Bluetooth slave device and Bluetooth master device
CN108989457B (en) Information processing method, server and terminal
CN109450032B (en) Wireless charging processing method, device and equipment

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