CN113742037A

CN113742037A - Mobile terminal and application control method thereof

Info

Publication number: CN113742037A
Application number: CN202010474718.XA
Authority: CN
Inventors: 姜绍宇; 宋亮; 皮素梅
Original assignee: Hisense Mobile Communications Technology Co Ltd
Current assignee: Hisense Mobile Communications Technology Co Ltd
Priority date: 2020-05-29
Filing date: 2020-05-29
Publication date: 2021-12-03

Abstract

The application discloses a mobile terminal and an application control method thereof, and relates to the technical field of application. When the mobile terminal detects that the application identifier at the stack top of the task stack changes and determines that the target application indicated by the application identifier is the restricted application, the mobile terminal may determine the usage duration of the target application in the statistical period based on the duration that the application identifier of the target application is located at the stack top of the task stack. The use duration of the target application in the statistical period is determined based on the duration that the application identifier of the target application is located at the top of the stack of the task stack, so that the accuracy of the use duration of the target application determined by the method in the statistical period is high, and the reliability of the target application stopping running is ensured.

Description

Mobile terminal and application control method thereof

Technical Field

The present application relates to the field of application technologies, and in particular, to a mobile terminal and an application control method thereof.

Background

In order to enable a user to use an application installed in a mobile terminal more reasonably, the mobile terminal may determine a usage duration of the application after detecting that the application is started, and may close the application when determining that the usage duration is equal to a limited usage duration of the application.

In the related art, the mobile terminal may detect the currently running application every detection period, determine a time when the application is detected to be in a running state for the first time as a starting time of the application, and determine a usage duration of the application based on the starting time.

However, in the related art, the accuracy of the determined start-up time of the application is low, resulting in low accuracy of the counted usage time period.

Disclosure of Invention

The application provides a mobile terminal and an application control method thereof, which can solve the problem that the accuracy of the service life obtained by statistics of the related technology is low. The technical scheme is as follows:

in one aspect, a mobile terminal is provided, the mobile terminal comprising a processor; the processor is configured to:

if the change of an application identifier of the stack top of a task stack of the mobile terminal is detected, determining an application indicated by the application identifier positioned on the stack top as a target application currently running in the mobile terminal, wherein the application identifier of the application in a running state is stored in the task stack;

if the target application is the limited application, counting the use time of the target application in a counting period based on the time length of the application identifier of the target application at the stack top;

and if the service time of the target application in the statistical period is determined to be greater than or equal to the limited service time of the target application in the statistical period, stopping running the target application.

In another aspect, a mobile terminal is provided, the mobile terminal comprising a processor and a display screen;

the display screen is used for: displaying an application restriction interface;

the processor is configured to:

if the service life of the target application in the statistical period is determined to be longer than or equal to the service life of the target application in the statistical period, controlling the display screen to display the application limiting interface, wherein the application limiting interface comprises: exiting the control;

and stopping running the target application in response to the selection operation of the exit control.

Optionally, the application restriction interface further includes: the controls are used for a long time; the processor is further configured to:

and updating the limited use duration of the target application in a statistical period in response to the selection operation of the extended use control.

Optionally, the processor is further configured to:

if the application identifier of the target application is detected to be located at the stack top of the task stack in the counting period, counting down the use limiting time;

if the application identifier of the target application is detected not to be located at the stack top of the task stack, suspending the countdown;

and if the countdown is zero, determining the use time length of the target application in the statistical period to be greater than or equal to the limited use time length of the target application in the statistical period.

Optionally, the processor is further configured to:

and in the process that the application identifier of the target application is positioned at the stack top of the task stack, controlling display notification information of the display screen at intervals of an update period, wherein the notification information is used for notifying the use duration of the target application in the statistical period.

Optionally, the processor is further configured to:

and in the process that the application identifier of the target application is positioned at the stack top of the task stack, if the difference value between the use limiting time length and the use time length in the counting period is determined to be smaller than a difference threshold value, displaying prompt information, wherein the prompt information is used for prompting the difference value.

In another aspect, an application control method of a mobile terminal is provided, the method including:

In another aspect, an application control method for a mobile terminal is provided, where the method includes:

if the detected use duration of the target application in the statistical period is greater than or equal to the limited use duration of the target application in the statistical period, displaying an application limiting interface, wherein the application limiting interface comprises: exiting the control;

Optionally, the application restriction interface further includes: the controls are used for a long time; the method further comprises the following steps:

In still another aspect, a computer-readable storage medium having instructions stored therein, which when run on a computer, cause the computer to execute the application control method of the mobile terminal according to the above aspect.

In yet another aspect, a computer program product containing instructions is provided, which when run on the computer causes the computer to execute the application control method of the mobile terminal according to the above aspect.

The beneficial effect that technical scheme that this application provided brought includes at least:

the application identification of the application identifier is determined to be changed, and the target application indicated by the application identifier is determined to be limited application. The use duration of the target application in the statistical period is determined based on the duration that the application identifier of the target application is located at the top of the stack of the task stack, so that the accuracy of the use duration of the target application determined by the method in the statistical period is high, and the reliability of the target application stopping running is ensured.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is a schematic diagram of a mobile terminal to which an application control method of the mobile terminal is applied according to an embodiment of the present application;

fig. 2 is a flowchart of an application control method of a mobile terminal according to an embodiment of the present application;

fig. 3 is a flowchart of an application control method of another mobile terminal according to an embodiment of the present application;

fig. 4 is a flowchart of an application control method of a mobile terminal according to another embodiment of the present application;

fig. 5 is a schematic diagram of an application interface of a client having an application restriction function according to an embodiment of the present application;

fig. 6 is a schematic interface diagram of a mobile terminal displaying notification information according to an embodiment of the present application;

fig. 7 is a schematic interface diagram of a mobile terminal displaying prompt information according to an embodiment of the present application;

FIG. 8 is a schematic diagram of an application restriction interface provided by an embodiment of the present application;

FIG. 9 is a schematic diagram of another application restriction interface provided by embodiments of the present application;

fig. 10 is a schematic structural diagram of a mobile terminal according to an embodiment of the present application;

fig. 11 is a block diagram of a software structure of a mobile terminal according to an embodiment of the present application.

Detailed Description

To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.

Fig. 1 is a schematic diagram of a mobile terminal to which an application control method of the mobile terminal according to an embodiment of the present application is applied. Referring to fig. 1, a plurality of applications may be installed in the mobile terminal 110, and the plurality of applications may include: applications for entertaining users, such as reading, music, chatting, and games, and applications for providing basic services to users, such as conversation, short message, address book, calendar, and settings. As can also be seen from fig. 1, the mobile terminal 110 may also display the current time, as well as the current weather.

Optionally, the mobile terminal may be a smart phone, a tablet computer, or a wearable device. For example, referring to fig. 1, the mobile terminal may be a smartphone. The operating system of the mobile terminal can be an Android (Android) operating system.

The embodiment of the present application provides an application control method of a mobile terminal, which may be applied to a mobile terminal, such as the mobile terminal 110 shown in fig. 1. Referring to fig. 2, the method may include:

step 201, if it is detected that the application identifier at the stack top of the task stack of the mobile terminal changes, determining the application indicated by the application identifier at the stack top as a target application currently running in the mobile terminal.

The task stack stores application identifiers of applications in a running state.

Step 202, if the target application is the restricted application, counting the use duration of the target application in the counting period based on the duration of the application identifier of the target application at the top of the stack.

After determining the application identifier located at the top of the stack, the mobile terminal may detect whether the application identifier matches an identifier in the restricted application identifier set. If the application identifier is detected to be matched with a certain identifier in the restricted application identifier set, it may be determined that the target application indicated by the application identifier is a restricted application. Then, the mobile terminal may count the usage duration of the target application in the counting period based on the duration of the application identifier of the target application at the top of the stack.

And 203, stopping running the target application if the service time of the target application in the statistical period is detected to be greater than or equal to the limited service time of the target application in the statistical period.

After determining that the usage duration of the target application in the statistical period is greater than or equal to the display usage duration of the target application in the statistical period, the mobile terminal may determine that the usage duration of the target application has reached the usage upper limit, and may stop running the target application.

To sum up, the embodiment of the present application provides an application control method for a mobile terminal, where the mobile terminal detects that an application identifier at a stack top of a task stack changes and determines that a target application indicated by the application identifier is a restricted application, and may determine a usage duration of the target application in a statistical period based on a duration that the application identifier of the target application is located at the stack top of the task stack. The use duration of the target application in the statistical period is determined based on the duration that the application identifier of the target application is located at the top of the stack of the task stack, so that the accuracy of the use duration of the target application determined by the method provided by the embodiment of the application is higher in the statistical period, and the reliability of stopping running the target application is ensured.

Fig. 3 is a flowchart of another application control method of a mobile terminal according to an embodiment of the present disclosure, where the method may be applied to a mobile terminal, such as the mobile terminal 110 shown in fig. 1. Referring to fig. 3, the method may include:

step 301, if it is detected that the application identifier at the stack top of the task stack of the mobile terminal changes, determining the application indicated by the application identifier at the stack top as the currently running target application in the mobile terminal.

Step 302, if the target application is the restricted application, counting the use duration of the target application in the counting period based on the duration of the application identifier of the target application at the top of the stack.

And 303, if the service time of the target application in the statistical period is detected to be greater than or equal to the limited service time of the target application in the statistical period, displaying an application limiting interface.

After determining that the use duration of the target application in the statistical period is greater than or equal to the display use duration of the target application in the statistical period, the mobile terminal may determine that the use duration of the target application has reached the use upper limit, and may display an application restriction interface. Wherein, the application restriction interface may include: and exiting the control.

And 304, in response to the selection operation of the exit control, stopping running the target application.

The mobile terminal can stop running the target application in response to the selection operation of the user for the exit control in the application restriction interface.

In the embodiment of the application, after determining that the target application is the restricted application, the mobile terminal may count the use duration of the target application in a counting period in a forward timing manner in the process that the application identifier of the target application is located at the top of the stack. Or, the mobile terminal may count the usage duration of the target application in the counting period in a countdown manner. The embodiment of the present application takes a countdown manner as an example, and exemplifies an application control method of a mobile terminal provided by the present application. Referring to fig. 4, the method may include:

step 401, if it is detected that the application identifier at the stack top of the task stack of the mobile terminal changes, determining the application indicated by the application identifier at the stack top as a target application currently running in the mobile terminal.

In this embodiment of the application, when detecting that an application identifier at the top of a task stack of the mobile terminal changes, that is, when an application installed in the mobile terminal starts to run or stops running, the mobile terminal may determine the application identifier located at the top of the task stack, and determine the application indicated by the application identifier as a target application currently running in the mobile terminal. The task stack stores application identifiers of applications in a running state. The application in the running state may include: an application running in the background of the mobile terminal, and an application running in the foreground of the mobile terminal (i.e., the target application). Wherein, the application identification of the application running in the foreground is positioned at the top of the stack of the task stack.

Optionally, a task stack monitoring (tasksacklistener) component may be installed in the mobile terminal, and the task stack monitoring component may monitor a change of the task stack. If the task stack monitoring component monitors that the task stack changes, the mobile terminal may call a callback method (ontaskestackchanged), the callback method may call a running task (getsuningtask) method in an interface manager (ActivityManager), the getsuningtask method may obtain an application identifier located at the top of the task stack, and the corresponding mobile terminal may obtain the application identifier located at the top of the task stack. Then, the mobile terminal may determine the application indicated by the application identifier as the target application currently running in the foreground of the mobile terminal.

The application identifier may be a package name (package name) of the application. The task stack changing may include: the application identification is popped or pushed. The application identifier popping is the application that the mobile terminal stops running the application identifier indication, and the application identifier popping is the application that the mobile terminal starts running the application identifier indication.

Step 402, detecting whether the target application is a restricted application.

If the mobile terminal determines that the target application is a restricted application, step 403 is executed. If the target application is determined not to be the restricted application, the subsequent flow need not be executed.

In the embodiment of the application, after acquiring the application identifier of the stack top, the mobile terminal may further match the application identifier with a pre-stored restricted application identifier set. If it is determined that the same identifier as the application identifier exists in the restricted application identifier set, the target application may be determined to be a restricted application, and then step 403 is performed. If it is determined that the same application identifier as the application identifier does not exist in the restricted application identifier set, that is, any application identifier in the restricted application identifier combination is different from the application identifier, it may be determined that the target application is not the restricted application, and then step 403 and subsequent processes need not be executed.

Wherein the restricted application identification set may include application identifications of at least one restricted application, and the at least one restricted application may be determined by the mobile terminal in response to an operation of the user.

For example, assume that restricting the set of application identifications includes: and A, B, C, D and E, wherein the application identifier of the target application is A, and the mobile terminal can determine that the target application is the restricted application because the same application identifier as the application identifier A exists in the restricted application identifier set. Assuming that the application identifier of the target application is F, since F is different from any application identifier in the restricted application identifier set, the mobile terminal may determine that the target application is not a restricted application.

Optionally, a client having an application restriction function may be installed in the mobile terminal, where the application restriction function is a function of restricting the use duration of the application. The mobile terminal can respond to the touch operation of the user for the application icon of the client to operate the client. After the client is started, an application interface of the client can display a switch control of an application limit function and an application list. The application list may include an application name, an application icon, and a restriction setting control for each of a plurality of applications installed in the mobile terminal. The touch operation can be a click operation.

Then, the client may start the application restriction function in response to a touch operation of the user for the switch control. Thereafter, the client may determine at least one application as a restricted application in response to a user selection operation of a restriction setting control of the at least one application of the plurality of applications, and store an application identification (e.g., a package name) of the at least one application in a local database to form a restricted application identification set.

For example, it is assumed that after the client starts, the application interface of the client may display the interface shown in fig. 5. As can be seen from fig. 5, the application interface displays icons and restriction setting controls 01 of applications such as reading, calling, gallery, address book, and chat. The restriction setting control 01 may also display the restriction status of the application. As can be seen from fig. 5, the applications displayed by the current application interface are all in an unrestricted state, i.e., a state in which no restriction is set.

As shown in fig. 5, the application interface may further display text information 02 for explaining the application restriction function: the daily time limit can be set for the application needing management, and the prompt can be sent out when the available time reaches the upper limit.

As can be seen from fig. 5, the switch control 03 of the application restriction function is currently in an on state, so that the user can click the restriction setting control 01 of the application that needs to be restricted from being used. Assuming that the user clicks the reading and chatting restriction setting control 01, the client may store the reading and chatting application identifications in the local database as a restriction application identification set in response to the clicking operation of the user.

And step 403, acquiring the limited use time of the target application.

After determining that the target application is the restricted application, the mobile terminal may further obtain the restricted use duration of the target application based on the application identifier of the target application and the corresponding relationship between the application identifier and the restricted use duration.

In this embodiment of the application, for each application in the at least one application, the mobile terminal may display a restriction operation interface in response to a selection operation of a user on a restriction setting control of the application. Then, the mobile terminal may display a setting interface for limiting the duration of use in response to a touch operation for a time-limiting control in the operation-limiting interface, where the setting interface may display a plurality of candidate durations. The mobile terminal may determine, in response to a selection operation of a user for a target duration of the multiple candidate durations, the target duration as a limit duration (limit _ time) of the application, and may store a correspondence between an application identifier of the application and the limit duration in a local database. The unit of the limited use duration stored in the database may be seconds(s).

For example, assuming that the application interface displays an application list as shown in fig. 5, the user needs to limit the use duration of reading. Assuming that the user clicks the restriction setting control 01 read in fig. 5, the client may display a restriction operation interface including a restriction operation box 04, and a cancel control 05, see fig. 5. The restrict operation box 04 may include an application name (i.e., read), a set restrict time control 041 and a cancel restrict control 042. If the user clicks the cancel restriction control 042 or cancel control 05, the previous interface may be returned.

Assuming that the user clicks the set time limit control 041, the client may display a set interface for limiting the usage time period as shown in fig. 5, which may display a set time limit box 05, in response to the user clicking the control 041. The set limit time box 05 may be displayed with a plurality of alternative time durations, and as can also be seen in fig. 5, the set limit time box 05 may further include a cancel control 051 and a determine control 052.

Assuming that the user wants to set the usage time period of reading within the statistical period to 2 hours (h), the user can slide the number corresponding to "hour" to 2, slide the data corresponding to "minute" to 00, and click on decision control 052. Accordingly, the mobile terminal may determine that the reading limited use duration is 2h (i.e., 7200s) in response to the sliding operation of the user for the number and the clicking operation of the determination control 052, and store the corresponding relationship between the read application identifier and the limited use duration in the local database. Assuming that the user clicks the cancel control 051, the client can respond to the operation of the click cancel control 051 and return to the previous interface.

And step 404, counting down the limited use time.

In the process that the application identifier of the target application is located at the top of the stack, the mobile terminal can count down the limited time length of the target application after acquiring the limited time length of the target application.

Alternatively, the mobile terminal may create a countdown timer (countdown timer) after determining that the target application is the restricted application. And after the limited use time of the target application is obtained, counting down the limited use time. The unit of the countdown may be s.

In the embodiment of the application, in the countdown process, the mobile terminal may further count the usage duration of the target application in the counting period, and display notification information for notifying the usage duration of the target application in the counting period. The mobile terminal may determine the difference between the usage-limited duration and the current countdown as the usage duration of the target application in the statistical period.

In addition, in the process that the application identifier of the target application is located at the top of the task stack, that is, in the process that the target application runs in the foreground, the mobile terminal may count the use duration of the target application every other update period and display the use duration. I.e. the usage duration of the display can be updated by the mobile terminal every update period. The timing unit of the mobile terminal may be s.

Alternatively, the update period may be 1 minute (min), i.e., 60s, and the statistical period may be 1 day, i.e., 86400 s.

For example, assuming that the name of the client is "mobile phone is used healthily", the target application is reading, the use time of reading determined by the mobile terminal in the statistical period is 10 minutes, and the statistical period is 1 day, the mobile terminal may display the notification information 06 shown in fig. 6: reading today is used for 10 minutes. As can be seen from fig. 6, the notification message 06 may also include the limited usage duration of the application (e.g., the reading limited usage duration is 2 h).

Step 405, detecting whether the application identifier of the target application is located at the top of the task stack.

In the foreground running process of the mobile terminal, the user may click the application icon of other application, and the mobile terminal may respond to the click operation to run the other application in the foreground. Accordingly, the application identifier located at the top of the task stack of the mobile terminal may change. Therefore, in order to ensure the accuracy of the usage duration of the target application counted by the mobile terminal in the counting period, the mobile terminal needs to detect whether the target application identifier is located at the top of the task stack. For example, the mobile terminal may detect whether the target application identifier is located at the top of the task stack when detecting that the task stack is changed. If the mobile terminal detects that the application identifier of the target application is not located at the top of the task stack, step 406 is executed. If the mobile terminal detects that the application identifier of the target application is located at the top of the task stack, step 407 is executed.

Optionally, the task stack monitoring component in the mobile terminal may determine whether the application identifier of the target application is located at the top of the task stack based on the application identifier located at the top of the task stack and returned by the received callback function when monitoring that the task stack changes. If the task stack monitoring component determines that the application identifier currently located at the top of the task stack is different from the application identifier of the target application, it may determine that the application identifier of the target application is not located at the top of the task stack, and then may execute step 406. If the task listening component determines that the application identifier currently located at the top of the task stack is the same as the application identifier of the target application, it may determine that the application identifier of the target application is located at the top of the task stack, and then may execute step 407.

Step 406, suspend the countdown.

If the mobile terminal detects that the application identifier of the target application is not located at the top of the task stack, that is, the foreground of the mobile terminal runs another application, the countdown can be suspended.

It should be noted that, after the mobile terminal times out and counts down, the usage duration of the target application in the statistical period may be determined based on the current countdown, so that the mobile terminal may accurately determine whether the total usage duration of the target application is greater than or equal to the limited usage duration in the statistical period, that is, whether the usage duration of the target application reaches the usage upper limit, based on the single usage duration of the target application running in the foreground of the mobile terminal each time in the statistical period after the target application runs in the foreground of the mobile terminal again.

Or after the mobile terminal suspends the countdown, the use limit duration in the statistical period can be updated based on the current countdown, namely, the use limit duration of the target application is updated to the duration indicated by the current countdown. Therefore, if the subsequent target application runs in the foreground of the mobile terminal again, the mobile terminal can directly count down based on the updated limited use duration so as to accurately determine whether the use duration of the target application in the statistical period reaches the use upper limit.

It should be further noted that, for a scenario in which the usage-limited duration in the statistical period of the target application is updated based on the duration indicated by the current countdown, the mobile terminal needs to update the usage-limited duration to the usage duration initially set by the user every statistical period. For example, if the counting period is 1 day and the usage limit duration initially set by the user is 7200s, the mobile terminal may update the usage limit duration to 7200s at 0 point every morning.

Step 407, check if the countdown is zero.

In this embodiment of the application, when detecting that the application identifier of the target application is located at the top of the task stack, the mobile terminal may continue to count down the limited use duration of the target application, and detect whether the count down is zero.

If the mobile terminal determines that the countdown is zero, that is, the usage duration of the target application in the statistical period is greater than or equal to the limited usage duration of the target application in the statistical period, step 408 may be executed. If the mobile terminal determines that the countdown is not zero, that is, the usage duration of the target application in the statistical period is less than the usage-limited duration of the target application in the statistical period, the target application may continue to run, and step 405 is executed.

For example, assuming that the limited use duration of the target application is 7200s and the current countdown is 3600s, since the countdown is not 0, the mobile terminal may determine that the use duration of the target application in the statistical period is less than the limited use duration of the target application in the statistical period, and may continue to run the target application. Assuming that the current countdown is 0, the mobile terminal may determine that the usage duration of the target application within the statistical period has reached the upper usage limit, and may perform step 408.

It should be noted that, in the process that the application identifier of the target application is located at the stack top of the task stack, if the mobile terminal determines that the countdown is not zero, the mobile terminal may further display a prompt message when it is determined that the difference between the usage-limited duration of the target application and the usage duration in the statistical period is smaller than the difference threshold, where the prompt message is used to prompt the user that the usage duration of the target application in the statistical period is about to reach the usage upper limit.

Optionally, if it is determined that the current countdown is less than the difference threshold, the mobile terminal may determine that the difference between the usage-limited duration of the target application and the usage duration in the statistical period is less than the difference threshold. Wherein, the difference threshold may be 5min (i.e. 300 s).

For example, assuming that the difference threshold is 300s, and the current countdown of reading is determined by the mobile terminal to be less than 300s, it may be determined that the difference between the limited usage duration of the target application and the usage duration in the statistical period is less than 300s, so that the prompt message 07 shown in fig. 7 may be displayed: the reading will reach the upper use limit after 5 minutes. As can also be seen in FIG. 7, the interface displaying the reminder information may also include a "I know" no more reminder control 08. If the user clicks the no-more-prompt control 08, the mobile terminal may respond to the touch operation of the user for the no-more-prompt control 08, and no longer display the prompt information.

And step 408, displaying an application limiting interface.

In this embodiment of the application, if it is detected that the countdown is zero, that is, it is determined that the usage duration of the target application in the statistical period is greater than or equal to the limited usage duration of the target application in the statistical period, the mobile terminal may display an application restriction interface, that is, the application restriction interface covers the application interface of the target application. The application restriction interface may include: exit controls and extended use controls.

Optionally, the extended use control may include: a first duration extension control and a second duration extension control. I.e., the extended use control may carry an extended length of time. The first duration and the second duration may be different.

For example, assuming that the target application is reading, the name of the client with the application restriction function is healthy use mobile phone. When the mobile terminal detects that the countdown is zero, the application restriction interface shown in fig. 8 may be displayed. As can be seen from fig. 8, the application restriction interface may display information 09 that the application usage duration has exceeded the restricted usage duration: and (5) forbidding when time is out, wherein the reading use time length reaches the upper limit.

Referring to fig. 8, the application restriction interface may also display a control 10 that adjusts the length of the restriction. If the user clicks the control 10, the mobile terminal may start a mobile phone client for healthy use, and display an application interface shown in fig. 5, so that the user can adjust the use-limited duration of the application. As can also be seen in FIG. 8, the application restriction interface may also include an extended use control 11 and an exit control 12.

Or, assuming that the first duration is 15min and the second duration is unlimited, when the mobile terminal detects that the countdown is zero, the application restriction interface shown in fig. 9 may be displayed. In contrast to the interface shown in FIG. 8, the extended-use control 11 in FIG. 9 includes: a 15 minute extended use control 111, and an indefinite duration extended use control 112.

It should be noted that, if the usage duration of a certain application in the statistical period is greater than or equal to the usage-limited duration of the application, the mobile terminal may display the application-limited interface first after receiving the touch operation of the user on the application icon of the application.

And step 409, responding to the selection operation aiming at the quit control, and stopping running the target application.

In the embodiment of the application, if the user does not use the target application within the statistical period, the user may click an exit control in the application restriction interface. Correspondingly, the mobile terminal can respond to the touch operation of the user for the quit control, display the desktop, and stop running the target application, namely close the process of the target application.

And step 410, responding to the selection operation aiming at the extended use control, and updating the limited use duration of the target application in the statistical period.

If the user still needs to use the target application within the statistical period, the user can click the extended use control in the application restriction interface. Correspondingly, the mobile terminal can respond to the touch operation of the user for the prolonged use control, continue to run the target application, and update the limited use duration of the target application in the statistical period.

Optionally, if the extended use control in the application restriction interface does not carry the extended duration, the mobile terminal may display an extended time selection box after responding to the touch operation of the user on the extended use control, where the selection box may include at least one duration control. The mobile terminal can respond to the selection operation for the target duration control in the at least one duration control, and the limited use duration of the target application in the statistical period is prolonged by the target duration. If the extended use control in the application limiting interface carries the extended time, the mobile terminal responds to the touch operation of the user for the extended use control, and then the limited use time of the target application in the statistical period is extended by the extended time carried by the extended use control.

For example, referring to fig. 8, when the user clicks the extended use control 11, the mobile terminal may limit the extended time selection box 13 in response to the touch operation. As can be seen from fig. 8, the time selection box 13 may include: a 15min duration control 131 and an indefinite duration control 132. If the user clicks the unlimited duration control 132, the mobile terminal may update the limited duration of the target application in the current statistical period in response to the touch operation of the user on the unlimited duration control 132, so that the duration of the target application in the current statistical period is not limited.

In the embodiment of the application, for each restriction application, the local database of the mobile terminal may further store a cancellation restriction identifier in a statistical period or an extended restriction use duration in the statistical period corresponding to the restriction application. That is, for each restricted application, the database stores the corresponding relationship between the statistical period (data), the package name, the restricted use duration, the cancellation restriction flag (limit _ cancel _ today) and the extended restricted use duration (limit _ delay) of the restricted application.

Wherein, the default value of the cancellation limitation flag in the statistical period is 0, which indicates that the limitation is not cancelled in the statistical period. The default value of the extended use-limiting duration in the statistical period is 0, which indicates that the use-limiting duration is not extended in the statistical period. The unit for extending the limited use period may be s.

After the usage duration of the target application reaches the upper limit, the mobile terminal may update the cancellation limit identifier in the statistical period or the extended usage duration in the statistical period corresponding to the target application stored in the local database in response to a selection operation of the user for the extended usage control in the application restriction interface.

For example, assume that the statistical period of the target application is 1 day, the date of the statistical period is 25 days 5 months 2020, the package name of the target application is com, and the limited-use duration of the target application is 7200 s. If the user clicks the duration control 132 shown in fig. 8, the mobile terminal may respond to the click operation, and update the statistical period, the package name, the usage-limited duration, the cancellation-limitation identifier in the statistical period, and the cancellation-limitation identifier in the statistical period in the corresponding relationship of the usage-limited duration. The updated corresponding relationship can be shown in table 1, and as can be seen from table 1, the cancellation limitation flag in the statistical period is updated to 1, so as to indicate that the usage duration of the target application in 5, 25 and 25 days in 2020 is not limited.

TABLE 1

data	package name	limit_time(s)	limit_cancel_today	limit_delayed(s)
					20200525	com.****	7200	1	0

If the user clicks the 15-minute duration control 131 shown in fig. 8, the updated corresponding relationship of the mobile terminal may be as shown in table 2, and as can be seen from table 2, the extended duration in the statistical period is updated to 15min, that is, 900 s.

TABLE 2

data	package name	limit_time(s)	limit_cancel_today	limit_delayed(s)
					20200525	com.****	7200	0	900

It should be noted that, for a scenario in which the mobile terminal updates the cancellation limitation identifier in the statistical period or the value of the extended use limit duration in the statistical period corresponding to the target application stored in the local database in response to the selection operation of the user on the extended use control in the application limitation interface, the mobile terminal needs to update the cancellation limitation identifier in the statistical period and the extended use limit duration in the statistical period to default values every statistical period.

And when the application does not run for the first time in the statistical period, the mobile terminal can detect the value of the restriction identifier in the statistical period based on the packet name of the application, and if the value is determined to be 1, it is determined that the use duration of the application does not need to be restricted in the statistical period, and then the subsequent processes such as countdown do not need to be executed.

It should be further noted that, the order of the steps of the application control method of the mobile terminal provided in the embodiment of the present application may be appropriately adjusted, and the steps may also be increased or decreased according to the situation. For example, steps 408 to 410 may also be deleted according to the situation, that is, the mobile terminal may directly stop running the target application when detecting that the countdown is zero. Any method that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application is covered by the protection scope of the present application, and thus the detailed description thereof is omitted.

An embodiment of the present application provides a mobile terminal, and referring to fig. 10, the mobile terminal 110 includes a processor 1101. The processor 1101 may be configured to:

if the change of the application identifier of the stack top of the task stack of the mobile terminal is detected, determining the application indicated by the application identifier positioned on the stack top as a target application currently running in the mobile terminal, wherein the application identifier of the application in a running state is stored in the task stack;

if the target application is the limited application, counting the use time of the target application in a counting period based on the time length of the application identifier of the target application at the top of the stack;

and if the use time of the target application in the statistical period is determined, stopping running the target application when the use time is greater than or equal to the limited use time of the target application in the statistical period.

To sum up, the embodiment of the present application provides a mobile terminal, where the mobile terminal detects that an application identifier at a stack top of a task stack changes, and determines that a target application indicated by the application identifier is a restricted application, and may determine a usage duration of the target application in a statistical period based on a duration that the application identifier of the target application is located at the stack top of the task stack. The use duration of the target application in the counting period is determined based on the duration that the application identifier of the target application is located at the top of the stack of the task stack, so that the accuracy of the use duration of the target application determined by the mobile terminal in the counting period is high, and the reliability of the target application stopping running is ensured.

As shown in fig. 10, the mobile terminal 110 may further include: a display screen 131. The display screen 131 may be used to: an application restriction interface is displayed. The mobile terminal 110

The mobile terminal 110 may include a processor 1101 configured to:

if the service time of the target application in the statistical period is determined to be longer than or equal to the limited service time of the target application in the statistical period, controlling the display screen to display an application limiting interface, wherein the application limiting interface comprises: exiting the control;

As shown in fig. 10, the mobile terminal 110 may further include: a display unit 130, a memory 140, a Radio Frequency (RF) circuit 150, an audio circuit 160, a wireless fidelity (Wi-Fi) module 170, a bluetooth module 180, a power supply 190, a camera 121, and a processor 1101.

The camera 121 may be used to capture still pictures or video, among other things. The object generates an optical picture through the lens and projects the optical picture to the photosensitive element. The photosensitive element may be a Charge Coupled Device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The light sensitive elements convert the light signals into electrical signals which are then passed to the processor 1101 for conversion into digital picture signals.

The processor 1101 is a control center of the mobile terminal 110, connects various parts of the entire terminal using various interfaces and lines, and performs various functions of the mobile terminal 110 and processes data by running or executing software programs stored in the memory 140 and calling data stored in the memory 140. In some embodiments, processor 1101 may include one or more processing units; the processor 1101 may also integrate an application processor, which mainly handles operating systems, user application interfaces, application programs, etc., and a baseband processor, which mainly handles wireless communications. It will be appreciated that the baseband processor described above may not be integrated into the processor 1101. In this application, the processor 1101 may run an operating system and an application program, may control display of a user application interface, and may implement the application control method of the mobile terminal provided in this application embodiment. Additionally, processor 1101 is coupled to input unit and display unit 130.

The display unit 130 may be used to receive input numeric or character information and generate signal inputs related to user settings and function control of the mobile terminal 110, and optionally, the display unit 130 may also be used to display Graphical User Interface (GUI) information input by or provided to the user and various menus of the mobile terminal 110. The display unit 130 may include a display screen 131 disposed on the front surface of the mobile terminal 110. The display screen 131 may be configured in the form of a liquid crystal display, a light emitting diode, or the like. The display unit 130 may be used to display various graphical user application interfaces described herein.

The display unit 130 includes: a display screen 131 and a touch screen 132 disposed on the front of the mobile terminal 110. The display screen 131 may be used to display preview pictures. Touch screen 132 may collect touch operations on or near by the user, such as clicking a button, dragging a scroll box, and the like. The touch screen 132 may be covered on the display screen 131, or the touch screen 132 and the display screen 131 may be integrated to implement the input and output functions of the mobile terminal 110, and after the integration, the touch screen may be referred to as a touch display screen for short.

Memory 140 may be used to store software programs and data. The processor 1101 executes various functions of the mobile terminal 110 and data processing by executing software programs or data stored in the memory 140. The memory 140 may include high speed random access memory and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device. Memory 140 stores an operating system that enables mobile terminal 110 to operate. The memory 140 may store an operating system and various application programs, and may also store codes for executing the application control method of the mobile terminal provided in the embodiments of the present application.

The RF circuit 150 may be used for receiving and transmitting signals during information transmission and reception or during a call, and may receive downlink data of a base station and then deliver the received downlink data to the processor 1101 for processing; the uplink data may be transmitted to the base station. Typically, the RF circuitry includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.

Audio circuitry 160, speaker 161, and microphone 162 may provide an audio interface between a user and mobile terminal 110. The audio circuit 160 may transmit the electrical signal converted from the received audio data to the speaker 161, and convert the electrical signal into a sound signal for output by the speaker 161. The mobile terminal 110 may also be configured with a volume button for adjusting the volume of the sound signal. On the other hand, the microphone 162 converts the collected sound signal into an electrical signal, converts the electrical signal into audio data after being received by the audio circuit 160, and then outputs the audio data to the RF circuit 150 to be transmitted to, for example, another terminal or outputs the audio data to the memory 140 for further processing. In this application, the microphone 162 may capture the voice of the user.

Wi-Fi belongs to a short-distance wireless transmission technology, and the mobile terminal 110 may help a user to send and receive e-mails, browse webpages, access streaming media, and the like through the Wi-Fi module 170, which provides a wireless broadband internet access for the user.

And the Bluetooth module 180 is used for performing information interaction with other Bluetooth devices with Bluetooth modules through a Bluetooth protocol. For example, the mobile terminal 110 may establish a bluetooth connection with a wearable electronic device (e.g., a smart watch) also equipped with a bluetooth module through the bluetooth module 180, so as to perform data interaction.

Mobile terminal 110 also includes a power supply 190 (e.g., a battery) that powers the various components. The power supply may be logically coupled to the processor 1101 through a power management system to manage charging, discharging, and power consumption functions through the power management system. The mobile terminal 110 may also be configured with a power button for powering on and off the terminal, and locking the screen.

The mobile terminal 110 may include at least one sensor 1110, such as a motion sensor 11101, a distance sensor 11102, a fingerprint sensor 11103, and a temperature sensor 11104. Mobile terminal 110 may also be configured with other sensors such as gyroscopes, barometers, hygrometers, thermometers, and infrared sensors.

It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the mobile terminal and each device described above may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

Fig. 11 is a block diagram of a software structure of a mobile terminal according to an embodiment of the present application. The layered architecture divides the software into several layers, each layer having a clear role and division of labor. The layers communicate with each other through a software interface. In some embodiments, the android system is divided into four layers, an application layer, an application framework layer, an android runtime (android runtime) and system library, and a kernel layer from top to bottom.

The application layer may include a series of application packages. As shown in fig. 11, the application package may include applications such as camera, gallery, calendar, phone call, map, navigation, WLAN, bluetooth, music, video, short message, etc. The application framework layer provides an Application Programming Interface (API) and a programming framework for the application program of the application layer. The application framework layer includes a number of predefined functions.

As shown in FIG. 11, the application framework layers may include a window manager, content provider, view system, phone manager, resource manager, notification manager, and the like.

The window manager is used for managing window programs. The window manager can obtain the size of the display screen, judge whether a status bar exists, lock the screen, intercept the screen and the like.

The content provider is used to store and retrieve data and make it accessible to applications. The data may include video, pictures, audio, calls made and received, browsing history and bookmarks, phone books, etc.

The view system includes visual controls such as controls to display text, controls to display pictures, and the like. The view system may be used to build applications. The display application interface may be composed of one or more views. For example, the display application interface including the sms notification icon may include a view for displaying text and a view for displaying a picture.

The phone manager is used to provide communication functions of the mobile terminal 110. Such as management of call status (including on, off, etc.).

The resource manager provides various resources for the application, such as localized strings, icons, pictures, layout files, video files, and the like.

The notification manager enables the application to display notification information in the status bar, can be used to convey notification-type messages, can disappear automatically after a short dwell, and does not require user interaction. Such as a notification manager used to inform download completion, message alerts, etc. The notification manager may also be a notification that appears in the form of a chart or scroll bar text at the top status bar of the system, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialog window. For example, text information is prompted in the status bar, a prompt tone is given, the communication terminal vibrates, and an indicator light flashes.

The android runtime comprises a core library and a virtual machine. The android runtime is responsible for scheduling and management of the android system.

The core library comprises two parts: one part is a function which needs to be called by java language, and the other part is a core library of android.

The application layer and the application framework layer run in a virtual machine. And executing java files of the application program layer and the application program framework layer into a binary file by the virtual machine. The virtual machine is used for performing the functions of object life cycle management, stack management, thread management, safety and exception management, garbage collection and the like.

The system library may include a plurality of functional modules. For example: surface managers (surface managers), media libraries (media libraries), three-dimensional graphics processing libraries (e.g., openGL ES), 2D graphics engines (e.g., SGL), and the like.

The surface manager is used to manage the display subsystem and provide fusion of 2D and 3D layers for multiple applications.

The media library supports a variety of commonly used audio, video format playback and recording, and still picture files, etc. The media library may support a variety of audio-video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

The three-dimensional graphic processing library is used for realizing three-dimensional graphic drawing, picture rendering, synthesis, layer processing and the like.

The 2D graphics engine is a drawing engine for 2D drawing.

The kernel layer is a layer between hardware and software. The inner core layer at least comprises a display driver, a camera driver, an audio driver and a sensor driver.

An embodiment of the present application provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the computer-readable storage medium runs on a computer, the computer is caused to execute an application control method of a mobile terminal, such as the method shown in any one of fig. 2 to 4, provided by the foregoing embodiment.

Embodiments of the present application further provide a computer program product including instructions, which, when the computer program product runs on a computer, causes the computer to execute the application control method of the mobile terminal provided in the foregoing method embodiments, for example, the method shown in any one of fig. 2 to 4.

It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.

The above description is only exemplary of the present application and should not be taken as limiting the present application, and any modifications, equivalents, improvements and the like that are made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims

1. A mobile terminal, characterized in that the mobile terminal comprises a processor; the processor is configured to:

2. A mobile terminal, characterized in that the mobile terminal comprises a processor and a display screen;

the processor is configured to:

3. The mobile terminal of claim 2, wherein the application restriction interface further comprises: the controls are used for a long time; the processor is further configured to:

4. The mobile terminal of any of claims 1 to 3, wherein the processor is further configured to:

5. The mobile terminal of any of claims 1 to 3, wherein the processor is further configured to:

6. The mobile terminal of any of claims 1 to 3, wherein the processor is further configured to:

7. An application control method of a mobile terminal, the method comprising:

and if the service time of the target application in the statistical period is detected to be longer than or equal to the limited service time of the target application in the statistical period, stopping running the target application.

8. An application control method of a mobile terminal, the method comprising:

9. The method of claim 8, wherein the application restriction interface further comprises: the controls are used for a long time; the method further comprises the following steps:

10. The method according to any one of claims 7 to 9, further comprising: