Method and device for optimizing sleep wake-up of mobile terminal equipment

Abstract

The invention provides an optimization method and device for sleep wake-up of mobile terminal equipment, the mobile terminal equipment is provided with a plurality of applications correspondingly configured with at least one wake-up alarm event, and the optimization method comprises the following steps: determining an event type corresponding to each wake-up alarm event based on a preset configuration parameter of each application; when the mobile terminal equipment is in a dormant state, dynamically updating a merging time step length of an application aiming at the application corresponding to each wake-up alarm event of which the event type is an optimization trigger event to obtain a target merging time step length corresponding to the application; determining a target triggering moment corresponding to each wake-up alarm event under each event type based on the target merging time step length and the initial triggering moment corresponding to each wake-up alarm event; and sequentially triggering each wake-up alarm event according to the target triggering time. By means of the method, the battery energy consumption of the mobile terminal equipment is reduced, and then the user experience of using the mobile terminal equipment is improved.

Description

Technical Field

[0001] This application relates to the technical field of mobile terminal systems, and in particular, to an optimization method and device for the sleep and wake-up of a mobile terminal device. Background Art

[0002] The mobile terminal system can restore the mobile terminal device from the sleep state to the normal state through the set wake-up operations. For example, the wake-up operations can include pressing the power button, incoming calls and text messages, and wake-up alarm events (WAKEUP_ALARM), etc. After the mobile terminal device returns to the normal state, when the system detects that the current system has been in the idle state for a period of time, for example, there is no user interaction for a period of time, the system will automatically turn off the screen and enter the sleep state again. Each time the mobile terminal device wakes up from the sleep state, it will consume additional electrical energy, reducing the battery life of the mobile terminal device.

[0003] Currently, applications in the mobile terminal system can register wake-up alarm events with the system to wake up the system regularly or periodically and perform set operations or actions. However, the wake-up alarm events configured by multiple applications are executed dispersedly, resulting in the mobile terminal device being frequently woken up from the sleep state, increasing the battery energy consumption of the mobile terminal device and reducing the user experience of using the mobile terminal device. Summary of the Invention

[0004] In view of this, the purpose of this application is to provide an optimization method and device for the sleep and wake-up of a mobile terminal device. By determining the event type corresponding to each wake-up alarm event configured by each application, and when the mobile terminal device is in the sleep state, determining the target merging time step for merging the wake-up alarm events with the event type of the optimization trigger event, and based on the target merging time step and the initial trigger moment of the wake-up alarm event, determining the target trigger moment of the wake-up alarm event under each event type, so as to merge multiple wake-up alarm events with similar initial trigger moments to the target trigger moment in a unified time window for triggering, reducing the number of times the mobile terminal device wakes up from the sleep state, reducing the battery energy consumption of the mobile terminal device, and thus improving the user experience of using the mobile terminal device.

[0005] The embodiment of this application provides an optimization method for the sleep and wake-up of a mobile terminal device. The mobile terminal device is installed with multiple applications, and each application is correspondingly configured with at least one wake-up alarm event for waking up the mobile terminal device from the sleep state by performing a preset action. The optimization method includes:

[0006] Determine the event type corresponding to each of the wake-up alert events based on the configuration parameters preset for the application corresponding to each of the wake-up alert events; wherein, the event type at least includes an optimized trigger event that requires merging the event trigger moments and a forced trigger event for which the event trigger moment cannot be adjusted.

[0007] When the mobile terminal device is in the sleep state, for the application corresponding to each of the wake-up alert events with the event type being an optimized trigger event, dynamically update the merging time step included in the configuration parameters preset for the application to obtain the target merging time step corresponding to the application.

[0008] Based on the target merging time step and the initial trigger moment corresponding to each of the wake-up alert events included in the configuration parameters, determine the target trigger moment corresponding to each of the wake-up alert events under each event type.

[0009] Trigger each of the wake-up alert events in sequence according to the target trigger moment corresponding to each of the wake-up alert events.

[0010] Furthermore, the configuration parameters at least include an event trigger type and a restriction permission parameter; wherein, the event trigger type at least includes an exact trigger and a non-exact trigger, and the restriction permission parameter at least includes unrestricted, restrict all, automatically restrict, and only restrict non-exact trigger events.

[0011] The determining the event type corresponding to each of the wake-up alert events based on the configuration parameters preset for the application corresponding to each of the wake-up alert events includes:

[0012] For each of the wake-up alert events, determine whether the restriction permission parameter preset for the application corresponding to the wake-up alert event is restrict all.

[0013] When the restriction permission parameter preset for the application corresponding to the wake-up alert event is restrict all, determine the event type corresponding to the wake-up alert event as an optimized trigger event.

[0014] When the restriction permission parameter preset for the application corresponding to the wake-up alert event is not restrict all, then determine whether the event trigger type preset for the application corresponding to the wake-up alert event is an exact trigger.

[0015] When the event trigger type preset for the application corresponding to the wake-up alert event is an exact trigger, determine the event type corresponding to the wake-up alert event as a forced trigger event.

[0016] When the event trigger type preset by the application corresponding to the wake-up alarm event is imprecise triggering, determine the event type corresponding to the wake-up alarm event according to the restricted permission parameter preset by the application corresponding to the wake-up alarm event and whether the mobile terminal device is in a fast charging state.

[0017] Further, when the event trigger type preset by the application corresponding to the wake-up alarm event is imprecise triggering, determine the event type corresponding to the wake-up alarm event according to the restricted permission parameter preset by the application corresponding to the wake-up alarm event and whether the mobile terminal device is in a fast charging state, including:

[0018] When the event trigger type preset by the application corresponding to the wake-up alarm event is imprecise triggering, determine whether the restricted permission parameter preset by the application corresponding to the wake-up alarm event is unrestricted;

[0019] When the restricted permission parameter preset by the application corresponding to the wake-up alarm event is unrestricted, determine the event type corresponding to the wake-up alarm event as a forced trigger event;

[0020] When the restricted permission parameter preset by the application corresponding to the wake-up alarm event is not unrestricted, determine whether the restricted permission parameter preset by the application corresponding to the wake-up alarm event is only restricting imprecise trigger events;

[0021] When the restricted permission parameter preset by the application corresponding to the wake-up alarm event is only restricting imprecise trigger events, determine the event type corresponding to the wake-up alarm event as an optimized trigger event;

[0022] When the restricted permission parameter preset by the application corresponding to the wake-up alarm event is not only restricting imprecise trigger events, determine that the restricted permission parameter preset by the application corresponding to the wake-up alarm event is automatic restriction, and determine whether the mobile terminal device is in a fast charging state;

[0023] When the mobile terminal device is not in a fast charging state, determine the event type corresponding to the wake-up alarm event as an optimized trigger event, and when the mobile terminal device is in a fast charging state, determine the event type corresponding to the wake-up alarm event as a forced trigger event.

[0024] Further, dynamically updating the combined time step length included in the configuration parameter preset by the application to obtain the target combined time step length corresponding to the application, including:

[0025] Obtain the remaining battery power value corresponding to the mobile terminal device, and determine the interval time step length and time increment corresponding to the remaining battery power value;

[0026] Add the merged time step included in the configuration parameters preset for the application to the time increment to obtain the target merged time step corresponding to the application;

[0027] At every interval time step, add the time increment to the target merged time step to obtain an updated target merged time step, so as to dynamically update the merged time step.

[0028] Further, the determining the target trigger time corresponding to each wake-up alarm event of each event type based on the target merged time step and the initial trigger time corresponding to each wake-up alarm event included in the configuration parameters includes:

[0029] When the event type of the wake-up alarm event is a forced trigger event, determine the initial trigger time included in the configuration parameters preset for the application where the wake-up alarm event is located as the first target trigger time corresponding to the wake-up alarm event;

[0030] When the event type of the wake-up alarm event is an optimization trigger event, determine whether the preset time step is divisible by the target merged time step to obtain a judgment result;

[0031] Based on the judgment result and the target merged time step, determine the combined trigger times of multiple optimization trigger events for combined processing to determine multiple time intervals formed by two adjacent combined trigger times; wherein, the length of each time interval is the target merged time step;

[0032] Determine the time interval to which the initial trigger time corresponding to each wake-up alarm event belongs, and determine whether there is at least one first target trigger time corresponding to the wake-up alarm event of the event type of forced trigger event in the time interval;

[0033] If there is at least one first target trigger time in the time interval, determine the first target trigger time as the second target trigger time corresponding to the wake-up alarm event;

[0034] If there is no first target trigger time in the time interval, based on the time order of the two combined trigger times corresponding to the time interval, determine the combined trigger time of the first time order as the second target trigger time corresponding to the wake-up alarm event.

[0035] Further, the determining the combined trigger times of multiple optimization trigger events for combined processing based on the judgment result and the target merged time step includes:

[0036] If the preset time step can be divided evenly by the target merging time step, then, based on the preset whole-hour moment, a merging trigger moment for an optimized trigger event for merging processing is obtained every target merging time step to determine a plurality of such merging trigger moments;

[0037] If the preset time step cannot be divided evenly by the target merging time step, then, based on the preset whole-hour moment, a pending merging trigger moment for an optimized trigger event for merging processing is obtained every target merging time step;

[0038] Determine whether the time step between each pending merging trigger moment and the next whole-hour moment after this pending merging trigger moment is less than the target merging time step;

[0039] When the time step is less than the target merging time step, determine the next whole-hour moment after the pending merging trigger moment as the merging trigger moment to determine a plurality of such merging trigger moments;

[0040] When the time step is equal to the target merging time step, determine the pending merging trigger moment as the merging trigger moment to determine a plurality of such merging trigger moments.

[0041] Further, after triggering each wake-up alarm event at the corresponding target trigger moment according to each target trigger moment corresponding to each wake-up alarm event, the optimization method further includes:

[0042] For each application, determine whether the trigger count corresponding to the wake-up alarm event in this application statistically periodically is greater than a preset threshold, and based on the determination result, increase the target merging time step corresponding to this application to a preset multiple or adjust the event type of the wake-up alarm event.

[0043] Further, the step of, for each application, determining whether the trigger count corresponding to the wake-up alarm event in this application statistically periodically is greater than a preset threshold, and based on the determination result, increasing the target merging time step corresponding to this application to a preset multiple or adjusting the event type of the wake-up alarm event includes:

[0044] For each application, determine whether the first trigger count corresponding to the wake-up alarm event in this application statistically periodically is greater than a first preset threshold;

[0045] When the first trigger count is greater than the first preset threshold, increase the target merging time step corresponding to this application to a preset multiple;

[0046] When the first trigger count is less than or equal to the first preset threshold, count the second trigger count corresponding to the wake-up alert event whose event trigger type in the application is an exact trigger, and determine whether the second trigger count is greater than the second preset threshold;

[0047] When the second trigger count is greater than the second preset threshold, adjust the event type of the wake-up alert event whose event trigger type in the application is an exact trigger to an optimized trigger event.

[0048] Further, when the mobile terminal device is in a non-sleep state, the optimization method further includes:

[0049] Determine whether the initial trigger time corresponding to each untriggered wake-up alert event has expired;

[0050] Immediately trigger each untriggered wake-up alert event whose initial trigger time has expired, and trigger each untriggered wake-up alert event whose initial trigger time has not expired in sequence according to the initial trigger time.

[0051] The embodiment of the present application also provides an optimization device for waking up a mobile terminal device from sleep. The optimization device includes:

[0052] An event classification module, configured to determine the event type corresponding to each wake-up alert event based on the configuration parameters preset for the application corresponding to each wake-up alert event; wherein, the event type at least includes an optimized trigger event that needs to merge the event trigger time and a forced trigger event that cannot adjust the event trigger time;

[0053] A time update module, configured to, when the mobile terminal device is in a sleep state, dynamically update the merge time step included in the configuration parameters preset for the application corresponding to each wake-up alert event whose event type is an optimized trigger event, to obtain the target merge time step corresponding to the application;

[0054] A trigger optimization module, configured to determine the target trigger time corresponding to each wake-up alert event under each event type based on the target merge time step and the initial trigger time corresponding to each wake-up alert event included in the configuration parameters;

[0055] An event trigger module, configured to trigger each wake-up alert event in sequence according to the target trigger time corresponding to each wake-up alert event.

[0056] An embodiment of the present application further provides an electronic device, including: a processor, a memory, and a bus. The memory stores machine-readable instructions executable by the processor. When the electronic device runs, the processor communicates with the memory through the bus. When the machine-readable instructions are executed by the processor, the steps of the optimization method for waking up and sleeping of the mobile terminal device as described above are executed.

[0057] An embodiment of the present application further provides a computer-readable storage medium. A computer program is stored on the computer-readable storage medium. When the computer program is run by a processor, the steps of the optimization method for waking up and sleeping of the mobile terminal device as described above are executed.

[0058] For the optimization method and device for waking up and sleeping of the mobile terminal device provided by the embodiment of the present application, the mobile terminal device is installed with multiple applications, and each application is correspondingly configured with at least one wake-up alarm event for waking up the mobile terminal device from the sleeping state by executing a preset action. The optimization method includes: determining the event type corresponding to each wake-up alarm event based on the configuration parameters preset for the application corresponding to each wake-up alarm event; wherein the event type at least includes an optimization trigger event that needs to merge the event trigger time and a forced trigger event that cannot adjust the event trigger time; when the mobile terminal device is in the sleeping state, for each application corresponding to the wake-up alarm event whose event type is an optimization trigger event, dynamically update the merge time step included in the configuration parameters preset for the application to obtain the target merge time step corresponding to the application; based on the target merge time step and the initial trigger time corresponding to each wake-up alarm event included in the configuration parameters, determine the target trigger time corresponding to each wake-up alarm event under each event type; trigger each wake-up alarm event in sequence according to the target trigger time corresponding to each wake-up alarm event.

[0059] Compared with the method in the prior art where the wake-up alarm events configured by multiple applications are executed dispersedly, resulting in the mobile terminal device being frequently woken up from the sleeping state, by determining the event type corresponding to the wake-up alarm event configured by each application, and when the mobile terminal device is in the sleeping state, determining the target merge time step for merging the wake-up alarm events whose event type is an optimization trigger event, and based on the target merge time step and the initial trigger time of the wake-up alarm event, determining the target trigger time of the wake-up alarm event under each event type, so as to merge multiple wake-up alarm events with similar initial trigger times into the target trigger time in a unified time window for triggering, the number of times the mobile terminal device is woken up from the sleeping state is reduced, the battery energy consumption of the mobile terminal device is reduced, and thus the user experience of using the mobile terminal device is improved.

[0060] To make the above objects, features, and advantages of the present application more obvious and understandable, the following provides preferred embodiments in conjunction with the accompanying drawings and detailed descriptions are as follows. Description of the Drawings

[0061] To more clearly illustrate the technical solutions of the embodiments of the present application, the accompanying drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and should not be regarded as limiting the scope. For those of ordinary skill in the art, without creative efforts, other relevant drawings can also be obtained based on these drawings.

[0062] Figure 1 One of the flowcharts of an optimization method for sleep wake-up of a mobile terminal device provided by an embodiment of the present application;

[0063] Figure 2 Another flowchart of an optimization method for sleep wake-up of a mobile terminal device provided by an embodiment of the present application;

[0064] Figure 3 One of the structural diagrams of an optimization device for sleep wake-up of a mobile terminal device provided by an embodiment of the present application;

[0065] Figure 4 Another structural diagram of an optimization device for sleep wake-up of a mobile terminal device provided by an embodiment of the present application;

[0066] Figure 5 A structural diagram of an electronic device provided by an embodiment of the present application. Detailed Embodiments

[0067] To make the objectives, technical solutions, and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Usually, the components of the embodiments of the present application described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the present application to be protected, but only represents the selected embodiments of the present application. Based on the embodiments of the present application, every other embodiment obtained by those of ordinary skill in the art without creative efforts falls within the scope of protection of the present application.

[0068] It has been found through research that the normal operation of mobile terminal devices depends on the electrical energy provided by the battery. Under the existing battery technology conditions, the electrical energy provided by the battery generally only supports users' normal operation for 1-2 days or even shorter. The operating system of mobile terminal devices needs to optimize battery management and reduce unnecessary power consumption to extend the battery life of mobile terminal devices.

[0069] The systems of mobile terminal devices are all set with a sleep state, that is, a low-power mode. Mobile terminal devices generally enter the sleep state within a certain period of time after the screen is turned off. After entering the sleep state, the mobile terminal system will adopt a series of restrictive measures to restrict application activities to reduce power energy consumption. For example, it will turn off WiFi and Bluetooth, restrict applications from accessing the network, and postpone scheduled tasks to a specific system maintenance time window, etc. Only when the user selects "unrestricted" for the application in the "Battery Management" set in the system will the above restrictions be exempted and not be affected.

[0070] The mobile terminal system can make the mobile terminal device resume from the sleep state to the normal state through the set wake-up operations. For example, the wake-up operations can include pressing the power button, incoming calls and text messages, and wake-up alarm events (WAKEUP_ALARM), etc. After the mobile terminal device resumes to the normal state, when the system detects that the current system has been in an idle state for a long period of time, for example, there is no user interaction for a period of time, the system will automatically turn off the screen and enter the sleep state again. Each time the mobile terminal device wakes up from the sleep state, it will consume additional electrical energy and reduce the battery life of the mobile terminal device.

[0071] In addition, the mobile terminal system will periodically exit the sleep state and enter the sleep state again. The time window from when the mobile terminal system automatically exits the sleep state to when it enters the sleep state again is the specific system maintenance time window. This maintenance time window is provided for applications to execute the postponed scheduled tasks, such as synchronizing accounts, refreshing content, etc.

[0072] Currently, applications in the mobile terminal system can wake up the system periodically or at a fixed time by registering wake-up alarm events with the system and execute the set operations or actions. However, the wake-up alarm events configured by multiple applications are executed dispersedly, resulting in the mobile terminal device being frequently woken up from the sleep state, increasing the battery energy consumption of the mobile terminal device and reducing the user experience of using the mobile terminal device.

[0073] Based on this, the embodiments of the present application provide an optimization method for the sleep and wake-up of a mobile terminal device. By determining the event type corresponding to the wake-up alarm event configured for each application, and when the mobile terminal device is in the sleep state, determining a target merging time step for merging the wake-up alarm events with the event type of the optimization trigger event, and based on the target merging time step and the initial trigger moment of the wake-up alarm event, determining the target trigger moment of the wake-up alarm event under each event type, so as to merge multiple wake-up alarm events with similar initial trigger moments to be triggered at the target trigger moment within a unified time window, reducing the number of times the mobile terminal device wakes up from the sleep state, reducing the battery power consumption of the mobile terminal device, and thus enhancing the user experience of using the mobile terminal device.

[0074] Please refer to Figure 1 , Figure 1 which is one of the flowcharts of an optimization method for the sleep and wake-up of a mobile terminal device provided by the embodiments of the present application.

[0075] In the embodiments of the present application, the mobile terminal device refers to an electronic device that supports being held and carried and can access the network at any time to perform activities such as communication, entertainment, and office work. For example, smart phones, tablet computers, laptop computers, smart watches, e-book readers, and handheld game consoles, etc.

[0076] Among them, the mobile terminal device is installed with multiple applications, and each application is correspondingly configured with at least one wake-up alarm event for waking up the mobile terminal device from the sleep state by performing a preset action.

[0077] Here, in the operating system of the mobile terminal device, each application uses the AlarmManager to register alarm events with the system, and the system uses the AlarmManagerService to manage the alarm events. The alarm events include wake-up alarm events (WAKEUP_ALARM) and non-wake-up alarm events (NON-WAKEUP_ALARM).

[0078] Among them, the wake-up alarm event is used to wake up the mobile terminal device from the sleep state by performing a preset action, that is, to forcibly wake up the system and make the system exit the sleep state. For example, actions such as instant message push and emergency notification; the non-wake-up alarm event will not wake up the system, that is, it will not make the system exit the sleep state. For example, actions such as non-real-time data synchronization and log reporting.

[0079] Here, when the system is in the sleep state, non-wake-up alarm events will be triggered by the system with a delay. The actual trigger time of non-wake-up alarm events may be later than the preset trigger time, and the actual trigger time depends on the system wake-up state, that is, when there is a wake-up alarm event triggered, the non-wake-up alarm events that have been delayed and not triggered before will be triggered; in addition, the wake-up alarm events configured by multiple applications generally show a discrete distribution in time, that is, they may be triggered at different time points.

[0080] In the embodiments of the present application, each application can use the alarm manager to register alarm events with the system. During the process of registering alarm events using the alarm management service, first, it is determined whether the alarm event is a wake-up alarm event, and then, only the wake-up alarm events are optimized, while the non-wake-up alarm events are processed according to the system preset policy.

[0081] As Figure 1 shown in

[0082] S100. Based on the configuration parameters preset for each application corresponding to each wake-up alarm event, determine the event type corresponding to each wake-up alarm event.

[0083] Among them, the event type at least includes an optimized trigger event that requires merging the event trigger time and a forced trigger event whose event trigger time cannot be adjusted; here, the event trigger time of the forced trigger event cannot be adjusted.

[0084] For example, assume that the wake-up alarm event A is not a high-priority event for the system, that is, it does not need to be triggered immediately. At this time, the wake-up alarm event A is determined as an optimized trigger event that can be merged; assume that the wake-up alarm event B is a high-priority event for the system and needs to be triggered immediately to ensure the normal operation of the system and give the user a better usage experience. At this time, the wake-up alarm event B is determined as a forced trigger event whose event trigger time cannot be adjusted.

[0085] In the embodiments of the present application, each application has preset configuration parameters in the operating system of the mobile terminal device, and users will also set and modify the configuration parameters of each application according to actual usage needs, that is, each application will preset configuration parameters.

[0086] Among them, the configuration parameters at least include the event trigger type corresponding to the application, the restricted permission parameter, the merge time step, and the initial trigger time of each wake-up alarm event.

[0087] Here, when determining the application's preset event trigger type, restricted permission parameter, and merged time step length, the event trigger type, restricted permission parameter, and merged time step length corresponding to each wake-up alert event configured for the application can be determined.

[0088] In the embodiments of the present application, to prevent applications from abusing wake-up alert events, the event trigger type of the operating system of the mobile terminal device includes at least exact trigger and inexact trigger.

[0089] Among them, the wake-up alert event with an exact trigger is required to trigger at a preset initial trigger moment and is applicable to scenarios with strong timeliness such as instant messaging and alarms; the wake-up alert event with an inexact trigger is allowed to trigger after a delay for a period of time after the preset initial trigger moment and is applicable to non-real-time tasks such as background synchronization.

[0090] Here, the operating system of the mobile terminal device requires the application to apply to the system and then obtain the user's consent to grant the exact trigger permission before using the wake-up alert event with an exact trigger. Otherwise, the application cannot use the wake-up alert event with an exact trigger.

[0091] This will cause the following problems. The permission management of using exact alerts for wake-up alert events with an exact trigger is prone to the "one-size-fits-all" phenomenon. If the user does not agree to grant permission, the "application function cannot be used normally" situation may occur; if the user agrees to grant permission, the problem of application abuse of this permission may not be avoided.

[0092] Furthermore, the restricted permission parameter includes at least unrestricted, restrict all, automatically restrict, and only restrict inexact trigger events.

[0093] Among them, unrestricted means that the application can be processed according to the system's preset policy, and the embodiments of the present application do not optimize the unrestricted applications; automatically restrict means that it is necessary to automatically decide whether to optimize the wake-up alert events of the application in combination with specific scenarios; restrict all means that all wake-up alert events of the application are forcibly optimized; only restrict inexact trigger events means that the inexact trigger wake-up alert events in the application are forcibly optimized.

[0094] In an implementation manner of the present application, in specific implementation, step S100 may include:

[0095] S110. For each of the wake-up alert events, determine whether the preset restricted permission parameter corresponding to the application of the wake-up alert event is restrict all.

[0096] In this step, since the restricted permission parameter is to restrict all wake-up alarm events, regardless of the event trigger type, it is necessary to optimize the wake-up alarm event. That is, it is determined whether the restricted permission parameter preset by the application to which each wake-up alarm event belongs is to restrict all.

[0097] S120. When the restricted permission parameter preset by the application corresponding to the wake-up alarm event is to restrict all, the event type corresponding to the wake-up alarm event is determined as an optimized trigger event.

[0098] In this step, for each wake-up alarm event corresponding to the restricted permission parameter preset by the application being to restrict all, the event type corresponding to the wake-up alarm event is determined as an optimized trigger event to perform combined optimization processing on the trigger moment of the wake-up alarm event.

[0099] S130. When the restricted permission parameter preset by the application corresponding to the wake-up alarm event is not to restrict all, it is determined whether the event trigger type preset by the application corresponding to the wake-up alarm event is an exact trigger.

[0100] In this step, for each wake-up alarm event corresponding to the restricted permission parameter preset by the application not being to restrict all, it is further determined whether the event trigger type corresponding to the wake-up alarm event is an exact trigger to determine whether to optimize it among the wake-up alarm events where the restricted permission parameter is not to restrict all.

[0101] S140. When the event trigger type preset by the application corresponding to the wake-up alarm event is an exact trigger, the event type corresponding to the wake-up alarm event is determined as a forced trigger event.

[0102] In this step, for each wake-up alarm event corresponding to the restricted permission parameter preset by the application not being to restrict all and the event trigger type being an exact trigger, the event type corresponding to the wake-up alarm event is determined as a forced trigger event to forcibly trigger the wake-up alarm event according to the preset initial trigger moment.

[0103] S150. When the event trigger type preset by the application corresponding to the wake-up alarm event is a non-exact trigger, the event type corresponding to the wake-up alarm event is determined according to the restricted permission parameter preset by the application corresponding to the wake-up alarm event and whether the mobile terminal device is in a fast charging state.

[0104] In an implementation manner of the present application, in specific implementation, for the wake-up alarm event where the event trigger type preset by the application is a non-exact trigger and the restricted permission parameter is not to restrict all, step S150 may include:

[0105] S151. When the preset event trigger type of the application corresponding to the wake-up alarm event is imprecise triggering, determine whether the preset restricted permission parameter of the application corresponding to the wake-up alarm event is unrestricted.

[0106] In this step, since no optimization is performed on unrestricted wake-up alarm events in the embodiments of the present application, it is determined whether the preset restricted permission parameter of the application corresponding to the wake-up alarm event is unrestricted.

[0107] S152. When the preset restricted permission parameter of the application corresponding to the wake-up alarm event is unrestricted, determine the event type corresponding to the wake-up alarm event as a forced trigger event.

[0108] In this step, determine the event type corresponding to the wake-up alarm event with an unrestricted preset restricted permission parameter of the application as a forced trigger event.

[0109] S153. When the preset restricted permission parameter of the application corresponding to the wake-up alarm event is not unrestricted, determine whether the preset restricted permission parameter of the application corresponding to the wake-up alarm event is only for restricting imprecise trigger events.

[0110] In this step, when the restricted permission parameter corresponding to the wake-up alarm event is neither unrestricted nor for restricting all events, the restricted permission parameter corresponding to the wake-up alarm event includes automatic restriction and only for restricting imprecise trigger events. That is, determine whether the preset restricted permission parameter of the application corresponding to the wake-up alarm event is only for restricting imprecise trigger events.

[0111] S154. When the preset restricted permission parameter of the application corresponding to the wake-up alarm event is only for restricting imprecise trigger events, determine the event type corresponding to the wake-up alarm event as an optimized trigger event.

[0112] In this step, determine the event type corresponding to the wake-up alarm event with an imprecise trigger event type and a restricted permission parameter of only for restricting imprecise trigger events as an optimized trigger event.

[0113] S155. When the preset restricted permission parameter of the application corresponding to the wake-up alarm event is not only for restricting imprecise trigger events, determine that the preset restricted permission parameter of the application corresponding to the wake-up alarm event is automatic restriction, and determine whether the mobile terminal device is in a fast charging state.

[0114] In this step, for the wake-up alarm event with an automatic restriction of the restricted permission parameter and an imprecise trigger event type, further determine whether the mobile terminal device is in a fast charging state.

[0115] S156. When the mobile terminal device is not in the fast charging state, determine the event type corresponding to the wake-up alarm event as an optimization trigger event; when the mobile terminal device is in the fast charging state, determine the event type corresponding to the wake-up alarm event as a forced trigger event.

[0116] In this step, when the mobile terminal device is not in the fast charging state, it indicates that the power of the mobile terminal device is relatively tight, and it is necessary to optimize the wake-up alarm event whose restricted permission parameter is automatically restricted and the event trigger type is non-precise trigger. That is, determine the event type of this wake-up alarm event as an optimization trigger event.

[0117] Furthermore, when the mobile terminal device is in the fast charging state, it indicates that the power of the mobile terminal device is relatively sufficient, and there is no need to optimize the wake-up alarm event whose restricted permission parameter is automatically restricted and the event trigger type is non-precise trigger. That is, determine the event type of this wake-up alarm event as a forced trigger event.

[0118] In an embodiment of the present application, when there is an application that is set to "unrestricted" by the user in "Battery Management" when registering a wake-up alarm event, determine the event type of each wake-up alarm event corresponding to the application set to "unrestricted" in "Battery Management" as a forced trigger event.

[0119] S200. When the mobile terminal device is in the sleep state, for each application corresponding to the wake-up alarm event whose event type is an optimization trigger event, dynamically update the merge time step included in the preset configuration parameters of the application to obtain the target merge time step corresponding to the application.

[0120] In this step, in specific implementation, first, detect the state of the mobile terminal device; then, when it is detected that the mobile terminal device is in the sleep state, it is necessary to perform merge optimization processing on each wake-up alarm event whose event type is an optimization trigger event; finally, dynamically update the merge time step included in the preset configuration parameters of each application to which the wake-up alarm event whose event type is an optimization trigger event belongs to obtain the target merge time step corresponding to the application.

[0121] Furthermore, use the dynamically updated target merge time step to perform merge optimization processing on each wake-up alarm event whose event type is an optimization trigger event.

[0122] In an implementation manner of the present application, in specific implementation, the step of dynamically updating the merge time step included in the preset configuration parameters of the application in step S200 to obtain the target merge time step corresponding to the application may include:

[0123] S210. Obtain the remaining battery power value corresponding to the mobile terminal device, and determine the interval time step and time increment corresponding to the remaining battery power value.

[0124] In this step, when dynamically updating the preset merging time step, the interval time step for dynamic update and the time increment for each update are determined according to the remaining battery power value corresponding to the mobile terminal device, that is, obtain the remaining battery power value corresponding to the mobile terminal device, and based on the remaining battery power value, determine the interval time step and time increment correspondingly.

[0125] Specifically, when the remaining battery power value is less than the preset power threshold, determine the first interval time step and the first time increment; when the remaining battery power value is greater than or equal to the preset power threshold, determine the second interval time step and the second time increment.

[0126] In the embodiments of the present application, the preset power threshold is generally set to 60%, the first time increment is greater than the second time increment, and the second interval time step is greater than the first interval time step.

[0127] Exemplarily, the merging time step is generally selected within the time period of 5 minutes to 30 minutes; the first time increment can be set to 5 minutes, the second time increment can be set to 3 minutes; the first interval time step can be set to 0.5 hours, and the second interval time step can be set to 1 hour.

[0128] S220. Add the merging time step included in the configuration parameters preset for the application to the time increment to obtain the target merging time step corresponding to the application.

[0129] In this step, when dynamically updating the merging time step for the first time, add the merging time step preset for each application to the time increment to obtain the target merging time step corresponding to the application.

[0130] S230. Every interval time step, add the time increment to the target merging time step to obtain the updated target merging time step, so as to dynamically update the merging time step.

[0131] In this step, after dynamically updating the merging time step for the first time and obtaining the target merging time step, every interval time step corresponding to the remaining power value, dynamically update the target merging time step, that is, add the time increment to the target merging time step to obtain the updated target merging time step.

[0132] S300. Based on the target merging time step and the initial trigger moment corresponding to each wake-up alarm event included in the configuration parameters, determine the target trigger moment corresponding to each wake-up alarm event under each event type.

[0133] In an embodiment of the present application, for each wake-up alert event under each event type, a target trigger moment corresponding to the wake-up alert event under the event type is determined.

[0134] Specifically, for a wake-up alert event with an event type of a forced trigger event, the target trigger moment corresponding to the wake-up alert event is the preset initial trigger moment of the wake-up alert event; for a wake-up alert event with an event type of an optimized trigger event, the target trigger moment corresponding to the wake-up alert event can be determined based on the target merging time step and the initial trigger moment corresponding to the wake-up alert event.

[0135] For example, assume that the initial trigger moment of wake-up alert event A with an event type of an optimized trigger event is T0, the target merging time step is L, and the preset time step is 60 minutes. Divide 60 minutes evenly with L as a period. If 60 / L cannot be divided evenly, then the last time is directly merged to the integral hour moment corresponding to 60 minutes, and T0 is merged backward to the next nearest integral hour moment that is a multiple of L.

[0136] In addition, if it is found during the merging and optimization process that there is at least one wake-up alert event with an event type of a forced trigger event in this time interval, then T0 is merged backward to the first target trigger moment T1 corresponding to the nearest wake-up alert event with an event type of a forced trigger event, and the second target trigger moment T2 of wake-up alert event A is obtained. The range of T2 is "T0 ≤ T2 ≤ T0 + L".

[0137] In an implementation manner of the present application, during specific implementation, step S300 may include:

[0138] S310. When the event type of the wake-up alert event is a forced trigger event, determine the initial trigger moment included in the configuration parameters preset for the application where the wake-up alert event is located as the first target trigger moment corresponding to the wake-up alert event.

[0139] In this step, for a wake-up alert event with an event type of a forced trigger event, since there is no need to perform merging and optimization processing on the wake-up alert event, that is, determine the initial trigger moment corresponding to the wake-up alert event as the first target trigger moment corresponding to the wake-up alert event.

[0140] S320. When the event type of the wake-up alert event is an optimized trigger event, determine whether the preset time step can be divided evenly by the target merging time step to obtain a judgment result.

[0141] In an embodiment of the present application, for a wake-up alarm event with an event type of an optimization trigger event, it is necessary to merge multiple wake-up alarm events with similar initial trigger times into a unified time interval, and then determine a second target trigger time corresponding to the wake-up alarm event within the time interval.

[0142] In an embodiment of the present application, the preset time step can generally be set to 60 minutes.

[0143] Among them, the time interval includes two types of target trigger times. One is the integral hour moment corresponding to the preset time step, and the other is the first target trigger time corresponding to a wake-up alarm event with an event type of a forced trigger event existing within the time interval.

[0144] In this step, for a wake-up alarm event with an event type of an optimization trigger event, it is determined whether the preset time step can be divided evenly by the target merge time step of the application to which the wake-up alarm event belongs, and a judgment result is obtained.

[0145] S330. Based on the judgment result and the target merge time step, determine the merge trigger times of multiple optimization trigger events for merge processing to determine multiple time intervals formed by two adjacent merge trigger times.

[0146] Among them, the length of each time interval is the target merge time step.

[0147] In an implementation manner of the present application, in specific implementation, step S330 may include:

[0148] S331. If the preset time step can be divided evenly by the target merge time step, then based on the preset integral hour moment, obtain a merge trigger time of an optimization trigger event for merge processing every target merge time step to determine multiple merge trigger times.

[0149] In an embodiment of the present application, the preset time step can generally be set to 60 minutes; the preset integral hour moment represents the integral hour from 0 to 24 hours, such as 1 o'clock, 2 o'clock, 13 o'clock, and 15 o'clock.

[0150] In this step, when the preset time step can be divided evenly by the target merge time step, it indicates that an integer number of target merge time steps can be divided in a preset time step. Then, based on the preset integral hour moment, incrementally add the target merge time step to the integral hour moment to obtain multiple merge trigger times of optimization trigger events for merge processing.

[0151] Exemplarily, when the preset time step is set to 60 minutes and the target merging time step is 10 minutes, assuming 13:00 as the reference point, 6 merging trigger moments can be determined within one preset time step, including 13:10, 13:20, 13:30, 13:40, 13:50, and 14:00.

[0152] S332. If the preset time step is not divisible by the target merging time step, starting from the preset whole-hour moment as the reference, obtain a pending merging trigger moment for the optimized trigger event for merging processing at intervals of the target merging time step.

[0153] In this step, when the preset time step is not divisible by the target merging time step, it indicates that an integer number of target merging time steps cannot be divided within one preset time step. That is, when determining the last merging trigger moment, the time step from this moment to the next whole-hour moment is less than the target merging time step. Starting from the preset whole-hour moment as the reference, obtain a pending merging trigger moment for the optimized trigger event for merging processing at intervals of the target merging time step, and further perform a judgment process on the pending merging trigger moment.

[0154] S333. Determine whether the time step between each pending merging trigger moment and the next whole-hour moment after this pending merging trigger moment is less than the target merging time step.

[0155] In this step, for the problem that an integer number of target merging time steps cannot be divided within one preset time step, determine whether the time step between each pending merging trigger moment and the next whole-hour moment after this pending merging trigger moment is less than the target merging time step.

[0156] S334. When the time step is less than the target merging time step, determine the next whole-hour moment after this pending merging trigger moment as the merging trigger moment to determine multiple merging trigger moments.

[0157] In this step, when there is a pending merging trigger moment whose time step with the next whole-hour moment after it is less than the target merging time step, delay this pending merging trigger moment to the next whole-hour moment, that is, determine the next whole-hour moment after this pending merging trigger moment as the merging trigger moment to determine multiple merging trigger moments.

[0158] Exemplarily, when the preset time step is set to 60 minutes and the target merging time step is 8 minutes, assuming 13:00 as the reference point, 7 pending merging trigger times can be determined within one preset time step, including 13:08, 13:16, 13:24, 13:32, 13:40, 13:48, and 13:56. Among them, the time step between the pending merging trigger time 13:56 and the next whole-hour moment 14:00 after 13:56 is 4 minutes, which is less than the target merging time step of 8 minutes. That is, the pending merging trigger time 13:56 is adjusted to the merging trigger time 14:00.

[0159] S335. When the time step is equal to the target merging time step, determine the pending merging trigger time as the merging trigger time to determine multiple merging trigger times.

[0160] In this step, when the time step between each pending merging trigger time and the next whole-hour moment after this pending merging trigger time is equal to the target merging time step, determine the pending merging trigger time as the merging trigger time to determine multiple merging trigger times.

[0161] Exemplarily, when the preset time step is set to 60 minutes and the target merging time step is 8 minutes, assuming 13:00 as the reference point, 7 pending merging trigger times can be determined within one preset time step, including 13:08, 13:16, 13:24, 13:32, 13:40, 13:48, and 13:56. Also determine 13:08, 13:16, 13:24, 13:32, 13:40, and 13:48 as the merging trigger times.

[0162] S340. Determine the time interval to which the initial trigger time of each wake-up alarm event belongs, and determine whether there is at least one first target trigger time corresponding to the wake-up alarm event whose event type is a forced trigger event in the time interval.

[0163] In this step, in specific implementation, first, determine multiple time intervals formed by two adjacent merging trigger times; then, based on the multiple time intervals, determine the time interval to which the initial trigger time of each wake-up alarm event belongs; finally, determine whether there is at least one first target trigger time corresponding to the wake-up alarm event whose event type is a forced trigger event in the time interval to which the initial trigger time of each wake-up alarm event belongs.

[0164] Exemplarily, when the preset time step is set to 60 minutes and the target merged time step is 10 minutes, assuming 13:00 as the reference, 6 merge trigger moments can be determined, including 13:10, 13:20, 13:30, 13:40, 13:50, and 14:00, and 5 time intervals can be determined, including 13:10 - 13:20, 13:20 - 13:30, 13:30 - 13:40, 13:40 - 13:50, and 13:50 - 14:00.

[0165] Further, for example, assuming that the first target trigger moment corresponding to a wake - up alarm event of a certain event type being a forced trigger event is 13:56, it is determined that there is the first target trigger moment corresponding to this wake - up alarm event in the time interval 13:50 - 14:00.

[0166] S350: If there is at least one of the first target trigger moments in the time interval, then determine the first target trigger moment as the second target trigger moment corresponding to the wake - up alarm event.

[0167] In this step, when there is at least one first target trigger moment corresponding to a wake - up alarm event of an event type being a forced trigger event in the time interval where the initial trigger moment of a wake - up alarm event of an event type being an optimized trigger event is located, determine this first target trigger moment as the second target trigger moment corresponding to the wake - up alarm event of an event type being an optimized trigger event.

[0168] For example, assuming that the initial trigger moment of a wake - up alarm event A of an event type being an optimized trigger event is 13:52, and the first target trigger moment of a wake - up alarm event B of an event type being a forced trigger event is 13:56, it is determined that there are wake - up alarm event A and wake - up alarm event B in the time interval 13:50 - 14:00, that is, determine the second target trigger moment corresponding to wake - up alarm event A as 13:56.

[0169] S360: If there is no such first target trigger moment in the time interval, then based on the time sequence of the two merge trigger moments corresponding to the time interval, determine the merge trigger moment with the first time sequence as the second target trigger moment corresponding to the wake - up alarm event.

[0170] In this step, when there is no first target trigger moment corresponding to a wake - up alarm event of an event type being a forced trigger event in the time interval where the initial trigger moment of a wake - up alarm event of an event type being an optimized trigger event is located, determine the merge trigger moment with a later time among the two merge trigger moments corresponding to the time interval as the second target trigger moment corresponding to the wake - up alarm event of an event type being an optimized trigger event.

[0171] For example, assume that the initial trigger time corresponding to a wake-up alert event A of a certain event type being an optimization trigger event is 13:52. It is determined that there is a wake-up alert event A within the time interval 13:50 - 14:00, and there is no wake-up alert event of the event type being a forced trigger event. That is, the second target trigger time corresponding to the wake-up alert event A is determined to be 14:00.

[0172] S400. Trigger each of the wake-up alert events in sequence according to the target trigger time corresponding to each wake-up alert event.

[0173] In this step, after the mobile terminal device is in the sleep state and the target trigger time corresponding to each wake-up alert event is determined, each wake-up alert event corresponding to the target trigger time is triggered in the order of the target trigger time.

[0174] Optionally, please refer to Figure 2 , Figure 2 which is the second flowchart of an optimization method for sleep wake-up of a mobile terminal device provided by an embodiment of the present application.

[0175] As Figure 2 shown, in addition to steps S100 to S400, the optimization method for sleep wake-up of a mobile terminal device provided by an embodiment of the present application further includes step S500. Specifically, step S500 is used to illustrate a method for statistically determining whether the trigger times corresponding to the wake-up alert events in each application are greater than a preset threshold and adjusting the target merge time step or the event type of the wake-up alert event after triggering each wake-up alert event in sequence according to the target trigger time corresponding to each wake-up alert event, so as to improve the stability of the mobile terminal device.

[0176] S500. For each application, determine whether the trigger times corresponding to the wake-up alert events in this application statistically obtained periodically are greater than a preset threshold, and according to the judgment result, increase the target merge time step corresponding to this application to a preset multiple or adjust the event type of the wake-up alert event.

[0177] In an embodiment of the present application, after the target merge time step corresponding to this application is increased to a preset multiple or the event type of the wake-up alert event is adjusted, a notification of the adjustment is sent to the user of the mobile terminal device, so that the user can select whether to continue to perform "merge optimization" or "no optimization" on this application in the "Standby Wake-up Management" in the operating system of the mobile terminal device.

[0178] In an implementation manner of the present application, in specific implementation, step S500 may include:

[0179] S510. For each of the said applications, determine whether the first trigger count corresponding to the wake-up alert event in this application statistically cyclically is greater than a first preset threshold.

[0180] In this step, when the mobile terminal device is in a sleep state and triggers each wake-up alert event in sequence according to the target trigger moment corresponding to each wake-up alert event, statistically cyclically every preset period whether the first trigger count corresponding to the wake-up alert event in each application is greater than a first preset threshold.

[0181] In the embodiments of the present application, the preset period and the first preset threshold can be determined respectively according to the specific content of the application and the specific configuration of the mobile terminal device.

[0182] S520. When the first trigger count is greater than the first preset threshold, increase the target merge time step corresponding to this application to a preset multiple.

[0183] In this step, when the first trigger count corresponding to the wake-up alert event in each application is greater than the first preset threshold, it indicates that there are too many events for waking up the device, and it is necessary to enlarge the window for merging processing, and increase the target merge time step corresponding to this application to a preset multiple.

[0184] For example, assume that the target merge time step corresponding to application A is L, the preset period is 10 minutes, and the first preset threshold is 10 times. When the first trigger count corresponding to the wake-up alert event in application A statistically in 10 minutes is 12 times, adjust the target merge time step corresponding to application A to 2L.

[0185] S530. When the first trigger count is less than or equal to the first preset threshold, statistically count the second trigger count corresponding to the wake-up alert event whose event trigger type is precise trigger in this application, and determine whether the second trigger count is greater than a second preset threshold.

[0186] In this step, when the first trigger count corresponding to the wake-up alert event in each application is less than or equal to the first preset threshold, statistically count the second trigger count corresponding to the wake-up alert event whose event trigger type is precise trigger in this application, and further determine whether the second trigger count is greater than a second preset threshold.

[0187] In the embodiments of the present application, the second preset threshold can be determined according to the specific content of the application and the specific configuration of the mobile terminal device.

[0188] Furthermore, when the second trigger count corresponding to the wake-up alert event whose event trigger type is precise trigger is less than or equal to the second preset threshold, no adjustment is made.

[0189] S540. When the second trigger count is greater than the second preset threshold, adjust the event type of the wake-up alert event with an accurate trigger event type in this application to an optimized trigger event.

[0190] In an embodiment of the present application, when the second trigger count is greater than the second preset threshold, it is necessary to further determine whether this application is a user interaction type application. When this application is not a user interaction type application, adjust the event type of the wake-up alert event with an accurate trigger event type in this application.

[0191] Specifically, when the second trigger count is greater than the second preset threshold and this application is not a user interaction type application, adjust the event type of the wake-up alert event with an accurate trigger event type in this application to an optimized trigger event.

[0192] Here, when adjusting the event type of the wake-up alert event with an accurate trigger event type in this application to an optimized trigger event, the restricted permission parameter of this application will be adjusted, that is, adjust the restricted permission parameter of this application from automatically restricted or only restricted non-accurate events to restricted all.

[0193] Further, as Figure 2 shown, in addition to steps S100 to S500, the optimized method for the mobile terminal device to sleep and wake up provided by the embodiment of the present application further includes steps S600 and S700. Specifically, steps S600 to S700 are used to illustrate the optimized method when the mobile terminal device is in a non-sleep state.

[0194] S600. Determine whether the initial trigger time corresponding to each untriggered wake-up alert event has expired.

[0195] In this step, when the mobile terminal device is in a non-sleep state, traverse all wake-up alert events, and based on the current time, determine whether the initial trigger time corresponding to each untriggered wake-up alert event has expired.

[0196] S700. Immediately trigger each untriggered wake-up alert event whose initial trigger time has expired, and trigger each untriggered wake-up alert event whose initial trigger time has not expired in sequence according to the initial trigger time.

[0197] In this step, control each untriggered wake-up alert event whose initial trigger time has expired to be triggered immediately.

[0198] Further, for each untriggered wake-up alert event whose initial trigger time has not expired, trigger this wake-up alert event in sequence according to the initial trigger time.

[0199] The optimization method for the sleep wake-up of a mobile terminal device provided by the embodiments of the present application determines the event type corresponding to the wake-up alert event configured for each application, and when the mobile terminal device is in the sleep state, determines a target merging time step for merging the wake-up alert events with the event type of the optimization trigger event, and based on the target merging time step and the initial trigger moment of the wake-up alert event, determines the target trigger moment of the wake-up alert event under each event type, so as to merge multiple wake-up alert events with similar initial trigger moments to be triggered at the target trigger moment in a unified time window, reducing the number of times the mobile terminal device wakes up from the sleep state, reducing the battery power consumption of the mobile terminal device, and thus improving the user experience of using the mobile terminal device.

[0200] Please refer to Figure 3 、 Figure 4 , Figure 3 which is one of the structural schematic diagrams of an optimization device for the sleep wake-up of a mobile terminal device provided by the embodiments of the present application. Figure 4 which is the second structural schematic diagram of an optimization device for the sleep wake-up of a mobile terminal device provided by the embodiments of the present application.

[0201] As shown in Figure 3 , the optimization device 300 includes:

[0202] An event classification module 310, configured to determine the event type corresponding to each wake-up alert event based on the configuration parameters preset for the application corresponding to each wake-up alert event; wherein, the event type at least includes an optimization trigger event that requires merging the event trigger moment and a forced trigger event that cannot adjust the event trigger moment.

[0203] A time update module 320, configured to, when the mobile terminal device is in the sleep state, dynamically update the merging time step included in the configuration parameters preset for the application corresponding to each wake-up alert event with the event type of the optimization trigger event, to obtain the target merging time step corresponding to the application.

[0204] A trigger optimization module 330, configured to determine the target trigger moment corresponding to each wake-up alert event under each event type based on the target merging time step and the initial trigger moment corresponding to each wake-up alert event included in the configuration parameters.

[0205] An event trigger module 340, configured to trigger each wake-up alert event in sequence according to the target trigger moment corresponding to each wake-up alert event.

[0206] Further, when the event classification module 310 is used to determine the event type corresponding to each wake-up alert event based on the configuration parameters preset for the application corresponding to each wake-up alert event, the event classification module 310 is used to:

[0207] For each wake-up alert event, determine whether the preset restricted permission parameter for the application corresponding to the wake-up alert event restricts all;

[0208] When the preset restricted permission parameter for the application corresponding to the wake-up alert event restricts all, determine the event type corresponding to the wake-up alert event as an optimization trigger event;

[0209] When the preset restricted permission parameter for the application corresponding to the wake-up alert event does not restrict all, determine whether the preset event trigger type for the application corresponding to the wake-up alert event is an exact trigger;

[0210] When the preset event trigger type for the application corresponding to the wake-up alert event is an exact trigger, determine the event type corresponding to the wake-up alert event as a forced trigger event;

[0211] When the preset event trigger type for the application corresponding to the wake-up alert event is a non-exact trigger, determine the event type corresponding to the wake-up alert event based on the preset restricted permission parameter for the application corresponding to the wake-up alert event and whether the mobile terminal device is in a fast charging state.

[0212] Further, when the event classification module 310 is used to determine the event type corresponding to the wake-up alert event based on the preset restricted permission parameter for the application corresponding to the wake-up alert event and whether the mobile terminal device is in a fast charging state when the preset event trigger type for the application corresponding to the wake-up alert event is a non-exact trigger, the event classification module 310 is used to:

[0213] When the preset event trigger type for the application corresponding to the wake-up alert event is a non-exact trigger, determine whether the preset restricted permission parameter for the application corresponding to the wake-up alert event is unrestricted;

[0214] When the preset restricted permission parameter for the application corresponding to the wake-up alert event is unrestricted, determine the event type corresponding to the wake-up alert event as a forced trigger event;

[0215] When the preset restricted permission parameter for the application corresponding to the wake-up alert event is not unrestricted, determine whether the preset restricted permission parameter for the application corresponding to the wake-up alert event restricts only non-exact trigger events;

[0216] When the preset restricted permission parameter of the application corresponding to the wake-up alert event is to restrict only non-exact trigger events, determine the event type corresponding to the wake-up alert event as an optimized trigger event;

[0217] When the preset restricted permission parameter of the application corresponding to the wake-up alert event is not to restrict only non-exact trigger events, determine that the preset restricted permission parameter of the application corresponding to the wake-up alert event is automatic restriction, and determine whether the mobile terminal device is in a fast charging state;

[0218] When the mobile terminal device is not in a fast charging state, determine the event type corresponding to the wake-up alert event as an optimized trigger event, and when the mobile terminal device is in a fast charging state, determine the event type corresponding to the wake-up alert event as a forced trigger event.

[0219] Further, when the time update module 320 is used to dynamically update the combined time step included in the configuration parameter preset by the application to obtain the target combined time step corresponding to the application, the time update module 320 is used to:

[0220] Obtain the remaining battery power value corresponding to the mobile terminal device, and determine the interval time step and time increment corresponding to the remaining battery power value;

[0221] Add the combined time step included in the configuration parameter preset by the application to the time increment to obtain the target combined time step corresponding to the application;

[0222] Every interval time step, add the time increment to the target combined time step to obtain an updated target combined time step, so as to dynamically update the combined time step.

[0223] Further, when the trigger optimization module 330 is used to determine the target trigger time corresponding to each wake-up alert event under each event type based on the target combined time step and the initial trigger time corresponding to each wake-up alert event included in the configuration parameter, the trigger optimization module 330 is used to:

[0224] When the event type of the wake-up alert event is a forced trigger event, determine the initial trigger time included in the configuration parameter preset by the application where the wake-up alert event is located as the first target trigger time corresponding to the wake-up alert event;

[0225] When the event type of the wake-up alert event is an optimized trigger event, determine whether the preset time step is divisible by the target combined time step to obtain a judgment result;

[0226] Based on the determination result and the target merging time step, determine the merging trigger moments of multiple optimization trigger events for merging processing, so as to determine multiple time intervals formed by two adjacent merging trigger moments; wherein, the length of each time interval is the target merging time step;

[0227] Determine the time interval to which the initial trigger moment corresponding to each wake-up alarm event belongs, and determine whether there is at least one first target trigger moment corresponding to the wake-up alarm event of which the event type is a forced trigger event in the time interval;

[0228] If there is at least one first target trigger moment in the time interval, determine the first target trigger moment as the second target trigger moment corresponding to the wake-up alarm event;

[0229] If there is no first target trigger moment in the time interval, based on the time order of the two merging trigger moments corresponding to the time interval, determine the merging trigger moment of the first time order as the second target trigger moment corresponding to the wake-up alarm event.

[0230] Further, when the trigger optimization module 330 is used to determine the merging trigger moments of multiple optimization trigger events for merging processing based on the determination result and the target merging time step, the trigger optimization module 330 is used for:

[0231] If the preset time step is divisible by the target merging time step, taking the preset whole-hour moment as a benchmark, obtain a merging trigger moment of an optimization trigger event for merging processing every target merging time step, so as to determine multiple merging trigger moments;

[0232] If the preset time step is not divisible by the target merging time step, taking the preset whole-hour moment as a benchmark, obtain a pending merging trigger moment of an optimization trigger event for merging processing every target merging time step;

[0233] Determine whether the time step between each pending merging trigger moment and the next whole-hour moment after the pending merging trigger moment is less than the target merging time step;

[0234] When the time step is less than the target merging time step, determine the next whole-hour moment after the pending merging trigger moment as the merging trigger moment, so as to determine multiple merging trigger moments;

[0235] When the time step is equal to the target merging time step, determine the pending merging trigger moment as the merging trigger moment, so as to determine multiple merging trigger moments.

[0236] Further, as shown in Figure 4 , the optimization device 300 further includes an optimization adjustment module 350, and the optimization adjustment module 350 is configured to:

[0237] For each of the applications, determine whether the number of trigger times corresponding to the wake-up alarm event in the application statistically periodically is greater than a preset threshold, and according to the determination result, increase the target merge time step corresponding to the application to a preset multiple or adjust the event type of the wake-up alarm event.

[0238] Further, when the optimization adjustment module 350 is configured to, for each of the applications, determine whether the number of trigger times corresponding to the wake-up alarm event in the application statistically periodically is greater than a preset threshold, and according to the determination result, increase the target merge time step corresponding to the application to a preset multiple or adjust the event type of the wake-up alarm event, the optimization adjustment module 350 is configured to:

[0239] For each of the applications, determine whether the first number of trigger times corresponding to the wake-up alarm event in the application statistically periodically is greater than a first preset threshold;

[0240] When the first number of trigger times is greater than the first preset threshold, increase the target merge time step corresponding to the application to a preset multiple;

[0241] When the first number of trigger times is less than or equal to the first preset threshold, statistically count the second number of trigger times corresponding to the wake-up alarm event whose event trigger type in the application is precise trigger, and determine whether the second number of trigger times is greater than a second preset threshold;

[0242] When the second number of trigger times is greater than the second preset threshold, adjust the event type of the wake-up alarm event whose event trigger type in the application is precise trigger to an optimized trigger event.

[0243] Further, as shown in Figure 4 , the optimization device 300 further includes an event processing module 360, and the event processing module 360 is configured to:

[0244] Determine whether the initial trigger time corresponding to each untriggered wake-up alarm event has expired;

[0245] Immediately trigger each untriggered wake-up alarm event whose initial trigger time has expired, and trigger each untriggered wake-up alarm event whose initial trigger time has not expired in sequence according to the initial trigger time.

[0246] The optimization device for the sleep wake-up of a mobile terminal device provided by an embodiment of the present application determines the event type corresponding to the wake-up alert event configured for each application, and when the mobile terminal device is in the sleep state, determines a target merging time step for merging the wake-up alert events with the event type of the optimization trigger event, and based on the target merging time step and the initial trigger moment of the wake-up alert event, determines the target trigger moment of the wake-up alert event under each event type, so as to merge multiple wake-up alert events with similar initial trigger moments to be triggered at the target trigger moment in a unified time window, reducing the number of times the mobile terminal device wakes up from the sleep state, reducing the battery power consumption of the mobile terminal device, and thus enhancing the user experience of using the mobile terminal device.

[0247] Please refer to Figure 5 , Figure 5 which is a schematic structural diagram of an electronic device provided by an embodiment of the present application. As Figure 5 shown in

[0248] the electronic device 500 includes a processor 510, a memory 520, and a bus 530. Figure 1 and Figure 2 When the electronic device 500 runs, the processor 510 communicates with the memory 520 through the bus 530. When the machine-readable instructions stored in the memory 520 are executed by the processor 510, the steps of the optimization method for the sleep wake-up of the mobile terminal device in the method embodiments as described above

[0249] can be executed. For the specific implementation manner, reference can be made to the method embodiments, and details are not described herein again. Figure 1 and Figure 2 When the computer program stored on the computer-readable storage medium provided by an embodiment of the present application is run by a processor, the steps of the optimization method for the sleep wake-up of the mobile terminal device in the method embodiments as described above

[0250] can be executed. For the specific implementation manner, reference can be made to the method embodiments, and details are not described herein again.

[0251] In several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For another example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed coupling or direct coupling or communication connection between each other can be through some communication interfaces. The indirect coupling or communication connection of the device or unit can be in an electrical, mechanical, or other form.

[0252] The units described as separate components may or may not be physically separated. The components displayed as units may or may not be physical units, that is, they can be located in one place or distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0253] In addition, in each embodiment of the present application, the functional units can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit.

[0254] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a non-volatile computer-readable storage medium executable by a processor. Based on such an understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or a part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in each embodiment of the present application. The foregoing storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical discs that can store program codes.

[0255] Finally, it should be noted that the above-described embodiments are only specific implementation manners of the present application, used to illustrate the technical solutions of the present application, rather than limiting it. The protection scope of the present application is not limited thereto. Although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that any person skilled in the art within the technical scope disclosed by the present application can still modify the technical solutions recorded in the foregoing embodiments, or can easily think of changes, or perform equivalent replacements on some of the technical features; and these modifications, changes or replacements do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be covered within the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. An optimization method for the sleep wake-up of a mobile terminal device, characterized in that, The mobile terminal device is installed with multiple applications, and each application is correspondingly configured with at least one wake-up alert event for waking up the mobile terminal device from the sleep state by performing a preset action. The optimization method includes: Based on the configuration parameters preset for each application corresponding to each wake-up alert event, determine the event type corresponding to each wake-up alert event; wherein, the event type at least includes an optimization trigger event that requires merging processing of the event trigger moment and a forced trigger event with an unadjustable event trigger moment; When the mobile terminal device is in the sleep state, for each application corresponding to the wake-up alert event with the event type of optimization trigger event, dynamically update the merging time step included in the configuration parameters preset for the application to obtain the target merging time step corresponding to the application; Based on the target merging time step and the initial trigger moment corresponding to each wake-up alert event included in the configuration parameters, determine the target trigger moment corresponding to each wake-up alert event under each event type; Trigger each wake-up alert event in sequence according to the target trigger moment corresponding to each wake-up alert event.

2. The method according to claim 1, characterized in that, The configuration parameters at least include an event trigger type and a restricted permission parameter; wherein, the event trigger type at least includes precise trigger and imprecise trigger, and the restricted permission parameter at least includes unrestricted, restrict all, automatic restriction, and only restrict imprecise trigger events; The determining the event type corresponding to each wake-up alert event based on the configuration parameters preset for each application corresponding to each wake-up alert event includes: For each wake-up alert event, determine whether the restricted permission parameter preset for the application corresponding to the wake-up alert event is restrict all; When the restricted permission parameter preset for the application corresponding to the wake-up alert event is restrict all, determine the event type corresponding to the wake-up alert event as an optimization trigger event; When the restricted permission parameter preset for the application corresponding to the wake-up alert event is not restrict all, then determine whether the event trigger type preset for the application corresponding to the wake-up alert event is precise trigger; When the event trigger type preset for the application corresponding to the wake-up alert event is precise trigger, determine the event type corresponding to the wake-up alert event as a forced trigger event; When the event trigger type preset for the application corresponding to the wake-up alert event is imprecise trigger, determine the event type corresponding to the wake-up alert event according to the restricted permission parameter preset for the application corresponding to the wake-up alert event and whether the mobile terminal device is in the fast charging state.

3. The method according to claim 2, wherein The determining the event type corresponding to the wake-up alert event according to the restricted permission parameter preset for the application corresponding to the wake-up alert event and whether the mobile terminal device is in the fast charging state when the event trigger type preset for the application corresponding to the wake-up alert event is imprecise trigger includes: When the preset event trigger type of the application corresponding to the wake-up alarm event is non-precise triggering, determine whether the preset restricted permission parameter of the application corresponding to the wake-up alarm event is unrestricted; When the preset restricted permission parameter of the application corresponding to the wake-up alarm event is unrestricted, determine the event type corresponding to the wake-up alarm event as a forced triggering event; When the preset restricted permission parameter of the application corresponding to the wake-up alarm event is not unrestricted, determine whether the preset restricted permission parameter of the application corresponding to the wake-up alarm event is only restricting non-precise triggering events; When the preset restricted permission parameter of the application corresponding to the wake-up alarm event is only restricting non-precise triggering events, determine the event type corresponding to the wake-up alarm event as an optimized triggering event; When the preset restricted permission parameter of the application corresponding to the wake-up alarm event is not only restricting non-precise triggering events, determine that the preset restricted permission parameter of the application corresponding to the wake-up alarm event is automatically restricted, and determine whether the mobile terminal device is in a fast charging state; When the mobile terminal device is not in a fast charging state, determine the event type corresponding to the wake-up alarm event as an optimized triggering event, and when the mobile terminal device is in a fast charging state, determine the event type corresponding to the wake-up alarm event as a forced triggering event.

4. The method according to claim 1, characterized in that The dynamically updating the merging time step length included in the configuration parameter preset for the application to obtain the target merging time step length corresponding to the application includes: Obtain the remaining battery power value corresponding to the mobile terminal device, and determine the interval time step length and time increment corresponding to the remaining battery power value; Add the merging time step length included in the configuration parameter preset for the application to the time increment to obtain the target merging time step length corresponding to the application; Every interval time step length, add the time increment to the target merging time step length to obtain the updated target merging time step length, so as to dynamically update the merging time step length.

5. The method according to claim 1, wherein The determining the target trigger time corresponding to each wake-up alarm event under each event type based on the target merging time step length and the initial trigger time corresponding to each wake-up alarm event included in the configuration parameter includes: When the event type of the wake-up alarm event is a forced triggering event, determine the initial trigger time included in the configuration parameter preset by the application where the wake-up alarm event is located as the first target trigger time corresponding to the wake-up alarm event; When the event type of the wake-up alarm event is an optimized triggering event, determine whether the preset time step length is divisible by the target merging time step length to obtain a judgment result; Based on the judgment result and the target merging time step length, determine the combined trigger times of multiple optimized triggering events for combined processing to determine multiple time intervals formed by two adjacent combined trigger times; wherein, the length of each time interval is the target merging time step length; Determine the time interval to which the initial trigger time corresponding to each of the wake-up alarm events belongs, and determine whether there is at least one first target trigger time corresponding to the wake-up alarm event whose event type is a forced trigger event in the time interval; If there is at least one first target trigger time in the time interval, determine the first target trigger time as the second target trigger time corresponding to the wake-up alarm event; If there is no first target trigger time in the time interval, based on the time order of the two combined trigger times corresponding to the time interval, determine the combined trigger time with the first time order as the second target trigger time corresponding to the wake-up alarm event.

6. The method according to claim 5, wherein The determining, based on the judgment result and the target combined time step, multiple combined trigger times for optimized trigger events for combined processing includes: If the preset time step is divisible by the target combined time step, taking the preset whole-hour moment as a reference, obtain a combined trigger time for an optimized trigger event for combined processing every target combined time step to determine multiple combined trigger times; If the preset time step is not divisible by the target combined time step, taking the preset whole-hour moment as a reference, obtain a pending combined trigger time for an optimized trigger event for combined processing every target combined time step; Determine whether the time step between each pending combined trigger time and the next whole-hour moment after the pending combined trigger time is less than the target combined time step; When the time step is less than the target combined time step, determine the next whole-hour moment after the pending combined trigger time as the combined trigger time to determine multiple combined trigger times; When the time step is equal to the target combined time step, determine the pending combined trigger time as the combined trigger time to determine multiple combined trigger times.

7. The method according to claim 1, characterized in that After sequentially triggering each of the wake-up alarm events at the target trigger time corresponding to each wake-up alarm event, the optimization method further includes: For each application, determine whether the trigger count corresponding to the wake-up alarm event in the application statistically periodically is greater than a preset threshold, and according to the judgment result, increase the target combined time step corresponding to the application to a preset multiple or adjust the event type of the wake-up alarm event.

8. The method according to claim 7, wherein The for each application, determining whether the trigger count corresponding to the wake-up alarm event in the application statistically periodically is greater than a preset threshold, and according to the judgment result, increasing the target combined time step corresponding to the application to a preset multiple or adjusting the event type of the wake-up alarm event includes: For each application, determine whether the first trigger count corresponding to the wake-up alarm event in the application statistically periodically is greater than a first preset threshold; When the first trigger count is greater than the first preset threshold, increase the target combined time step corresponding to the application to a preset multiple; When the first trigger count is less than or equal to the first preset threshold, count the second trigger count corresponding to the wake-up alert event with the event trigger type of precise trigger in the application, and determine whether the second trigger count is greater than the second preset threshold; When the second trigger count is greater than the second preset threshold, adjust the event type of the wake-up alert event with the event trigger type of precise trigger in the application to an optimized trigger event.

9. The method according to claim 1, characterized in that, When the mobile terminal device is in a non-sleep state, the optimization method further includes: Determine whether the initial trigger time corresponding to each untriggered wake-up alert event has expired; Immediately trigger each untriggered wake-up alert event whose initial trigger time has expired, and sequentially trigger each untriggered wake-up alert event whose initial trigger time has not expired according to the initial trigger time.

10. An optimization device for the sleep and wake-up of a mobile terminal device, characterized in that, The optimization device includes: An event classification module, configured to determine the event type corresponding to each wake-up alert event based on the configuration parameters preset for the application corresponding to each wake-up alert event; wherein, the event type at least includes an optimized trigger event that requires merging the event trigger time and a forced trigger event that cannot adjust the event trigger time; A time update module, configured to, when the mobile terminal device is in a sleep state, dynamically update the merging time step included in the configuration parameters preset for the application corresponding to each wake-up alert event with the event type of optimized trigger event, to obtain the target merging time step corresponding to the application; A trigger optimization module, configured to determine the target trigger time corresponding to each wake-up alert event under each event type based on the target merging time step and the initial trigger time corresponding to each wake-up alert event included in the configuration parameters; An event trigger module, configured to sequentially trigger each wake-up alert event according to the target trigger time corresponding to each wake-up alert event.

Images