CN110618913A - Application use duration segmented statistics method and terminal - Google Patents

Abstract

The invention discloses a method and a terminal for carrying out sectional statistics on application use duration, which are used for providing more detailed use conditions of each application on a mobile terminal and improving the perception experience of a user on application use. The method comprises the following steps: monitoring the state of the application in real time through a monitoring program; when the application state is monitored to be that the application jumps from a background to a foreground, taking the current system time as the starting time of using the application; in the process that the application is in the foreground, periodically updating the use duration information of the application in a database, wherein the use duration information comprises a use date, use duration in a set time period and total use duration; and when the application state is monitored to jump from the foreground to the background, the current system time is taken as the end time of using the application, and the use duration information of the application in the database is updated.

Description

Application use duration segmented statistics method and terminal

Technical Field

The invention relates to the technical field of computers, in particular to a method and a terminal for sectional statistics of application use duration.

Background

With the rapid development of the mobile internet, the rapid coverage of the high-speed broadband wireless network and the rapid popularization of the mobile terminal, the mobile terminal becomes an indispensable communication tool, and a user may use many applications on the mobile terminal every day, but at present, the user can only check how long a certain application is used on the same day, and cannot specifically check how long the application is used in a certain time period.

Taking the android system of the mobile terminal as an example, the android system can only provide a service for viewing the application use duration at present, but for the detailed use condition of the application, for example, the use duration of a certain application in each hour of a day cannot be provided with the viewing service.

Aiming at the defects, the user cannot know the use condition of each application on the mobile terminal more accurately, the user cannot manage each application more accurately, and the perception experience of the user on the use of the application is reduced.

Disclosure of Invention

The invention provides a method and a terminal for carrying out sectional statistics on application use duration, which are used for providing more detailed use conditions of each application on a mobile terminal and improving the use perception experience of a user on each application.

In a first aspect, the present invention provides a method for applying segment statistics on usage duration, the method comprising:

monitoring the state of the application in real time through a monitoring program;

when the application state is monitored to be that the application jumps from a background to a foreground, taking the current system time as the starting time of using the application;

in the process that the application is in the foreground, periodically updating the use duration information of the application in a database, wherein the use duration information comprises a use date, use duration in a set time period and total use duration;

and when the application state is monitored to jump from the foreground to the background, the current system time is taken as the end time of using the application, and the use duration information of the application in the database is updated.

Firstly, the method provided by the invention can monitor the application state in real time, and can ensure the accuracy of the use duration information by periodically updating the use duration information of the application in the database while monitoring, thereby having great real-time performance and accuracy; secondly, the database structure disclosed by the invention has great advantages, the data stored in the database comprises the use date, the use duration in the set time period and the total use duration, the stored data can be periodically updated, and the accuracy of the data stored in the database is ensured; finally, the method disclosed by the invention periodically updates the database, avoids frequent input/output (IO) reading and writing, occupies less resources and has higher efficiency. Therefore, the method provided by the invention can improve the fineness of the use condition of each application program, can ensure the accuracy of the statistical result, and has the advantages of less resource occupation and higher efficiency.

In one possible implementation, the monitoring the state of the application in real time by the monitor includes:

monitoring the stack of an operating system in real time through a monitoring program;

if the stack is changed, acquiring a first application name to which an application component at the top of the stack belongs through the monitor, and acquiring a second application name to which the application component at the top of the stack currently belongs through a component of an operating system;

if the first application name is consistent with the second application name, determining that the application corresponding to the second application name jumps from a background to a foreground;

and if the first application name is inconsistent with the second application name, determining that the application corresponding to the second application name jumps from the foreground to the background.

The method provided by the invention can acquire the change of the application state in real time, namely, the first application name to which the application component at the top end of the stack belongs can be acquired in real time through the monitoring program when the stack changes, and at the moment, the second application name to which the application component at the top end of the stack belongs is acquired through the component of the operating system, so that the time interval between the application names to which the application components at the top end of the stack belong are acquired twice is extremely short, the monitoring can be immediately carried out when the first application exits or the first application is switched to the second application, and the real-time performance of the monitoring is ensured.

In a possible implementation manner, monitoring the state of the application in real time through a monitor, and after the current system time is taken as the end time of using the application and the usage duration information of the application in the database is updated, the method further includes:

and counting the use duration, the total use duration and the average use duration of the application in each set time period in the database according to the set time interval.

Compared with the prior art in which the total use time of the application in one day is only counted, the method and the device for processing the application use data can provide more detailed application use data obviously.

Furthermore, the method and the device can update the use duration information corresponding to each application in the database, namely, the database establishes the association relationship among the application name, the use date, the use duration in the set time period and the total use duration.

In one possible implementation, the method further includes:

and responding to a chart display instruction, and displaying the use duration, the total use duration and the average use duration of the application in each set time period through a chart.

For the convenience of viewing by the user, the data in the database are displayed through a chart, and the usage duration, the total usage duration and the average usage duration of any application in each set period can be displayed, for example, the usage duration in each hour period of a certain date, the total usage duration and the average usage duration in the date can be displayed. The method can be more intuitively convenient for the user to check, and the perception experience of the user on application use is improved.

In one possible implementation, the listener is a service component in an operating system component.

Most of the existing monitoring programs may be an independent monitoring application program, and the running state needs to be kept all the time in the monitoring process, so that the power consumption of the terminal is high.

In a second aspect, the present invention provides a terminal applying segment statistics on usage duration, where the terminal includes: a processor and a memory, wherein the memory stores program code that, when executed by the processor, causes the terminal to perform the following:

monitoring the state of the application in real time through a monitoring program;

when the application state is monitored to be that the application jumps from a background to a foreground, taking the current system time as the starting time of using the application;

in the process that the application is in the foreground, periodically updating the use duration information of the application in a database, wherein the use duration information comprises a use date, use duration in a set time period and total use duration;

and when the application state is monitored to jump from the foreground to the background, the current system time is taken as the end time of using the application, and the use duration information of the application in the database is updated.

In one possible implementation, the processor is specifically configured to:

monitoring the stack of an operating system in real time through a monitoring program;

if the stack is changed, acquiring a first application name to which an application component at the top of the stack belongs through the monitor, and acquiring a second application name to which the application component at the top of the stack currently belongs through a component of an operating system;

if the first application name is consistent with the second application name, determining that the application corresponding to the second application name jumps from a background to a foreground;

and if the first application name is inconsistent with the second application name, determining that the application corresponding to the second application name jumps from the foreground to the background.

In one possible implementation, the processor is specifically further configured to:

and counting the use duration, the total use duration and the average use duration of the application in each set time period in the database according to the set time interval.

In one possible implementation, the processor is specifically further configured to:

and responding to a chart display instruction, and displaying the use duration, the total use duration and the average use duration of the application in each set time period through a chart.

In one possible implementation, the listener is a service component in an operating system component.

In a third aspect, the present invention provides another terminal applying segment statistics on usage duration, where the terminal includes: monitor module, confirm the module at the starting moment, update database module and confirm the module at the ending moment, wherein:

the monitoring module is used for monitoring the state of the application in real time through a monitoring program;

a start time determining module, configured to use the current system time as a start time for using the application when it is monitored that the application jumps from the background to the foreground;

the updating database module is used for periodically updating the use duration information of the application in the database in the process that the application is in the foreground, wherein the use duration information comprises a use date, use duration in a set time period and total use duration;

and the end time determining module is used for taking the current system time as the end time of using the application and updating the use duration information of the application in the database when the condition that the application is jumped from the foreground to the background is monitored.

In a possible implementation manner, the monitoring module is specifically configured to:

monitoring the stack of an operating system in real time through a monitoring program;

if the stack is changed, acquiring a first application name to which an application component at the top of the stack belongs through the monitor, and acquiring a second application name to which the application component at the top of the stack currently belongs through a component of an operating system;

if the first application name is consistent with the second application name, determining that the application corresponding to the second application name jumps from a background to a foreground;

and if the first application name is inconsistent with the second application name, determining that the application corresponding to the second application name jumps from the foreground to the background.

In a possible implementation manner, the terminal further includes a statistics module, specifically configured to:

and counting the use duration, the total use duration and the average use duration of the application in each set time period in the database according to the set time interval.

In a possible implementation manner, the terminal further includes a display module, specifically configured to:

and responding to a chart display instruction, and displaying the use duration, the total use duration and the average use duration of the application in each set time period through a chart.

In one possible implementation, the listener is a service component in an operating system component.

In a fourth aspect, the present invention provides a computer storage medium having stored thereon a computer program which, when executed by a processing unit, performs the steps of the method of the first aspect.

In addition, for technical effects brought by any one implementation manner of the second aspect to the fourth aspect, reference may be made to technical effects brought by different implementation manners of the first aspect, and details are not described here.

Drawings

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

Fig. 1A is a schematic diagram illustrating a view of a usage duration of an application according to an embodiment of the present invention;

FIGS. 1B-1C are schematic diagrams of another viewing application usage duration provided by an embodiment of the invention;

FIG. 2A is a schematic diagram illustrating a current usage duration of an application according to an embodiment of the present invention;

FIG. 2B is a schematic diagram illustrating another example of displaying the usage duration of an application according to the present invention;

FIG. 3 is a flowchart of a method for applying piecewise statistics of usage duration according to an embodiment of the present invention;

FIG. 4 is a flow chart of an implementation of database update according to an embodiment of the present invention;

FIG. 5 is a flowchart illustrating an embodiment of a database update process according to the present invention;

fig. 6 is a schematic structural diagram of a framework for applying piecewise statistics of usage duration according to an embodiment of the present invention;

FIG. 7A is a diagram illustrating a duration of a first display application according to an embodiment of the present invention;

FIG. 7B is a diagram illustrating a duration of a second display application according to an embodiment of the present invention;

FIG. 8A is a diagram illustrating an exemplary usage duration of an application according to an embodiment of the present invention;

FIG. 8B is a schematic diagram illustrating an application lifetime according to another embodiment of the present invention;

FIG. 9 is a block diagram of another framework for applying segment statistics on usage duration according to an embodiment of the present invention;

fig. 10 is a flowchart illustrating an embodiment of a method for applying piecewise statistics of usage duration according to this embodiment;

fig. 11 is a terminal for performing segment statistics on the usage duration of a first application according to an embodiment of the present invention;

fig. 12 is a terminal for performing segment statistics on the usage duration of a second application according to an embodiment of the present invention;

fig. 13 is a third terminal for applying segment statistics on usage duration according to an embodiment of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention clearer, the present invention will be described in further detail with reference to the accompanying drawings, and it is apparent that the described embodiments are only a part of the embodiments of the present invention, not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

Some of the words that appear in the text are explained below:

1. the term "and/or" in the embodiments of the present invention describes an association relationship of associated objects, and indicates that three relationships may exist, for example, a and/or B may indicate: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.

2. The term "terminal", or "terminal device", in the embodiment of the present invention, is a device located at the outermost periphery of a network in a computer network, and can access a wireless local area network WLAN to perform input of user information and output of processing results, and includes a desktop computer, a mobile phone, a notebook, a tablet computer, a POS machine, and a vehicle-mounted computer.

The execution main body of the invention is a terminal which comprises a plurality of application programs APP, and a user can obtain the detailed use duration of each application. In the method for displaying application use duration by a terminal in the prior art, as shown in fig. 1A, a display page of the terminal displays a plurality of application programs APP, and when a user wants to check the use duration of a certain application, an option of "application use duration" in a setting can be clicked as shown in fig. 1B to 1C.

The application scenario described in the embodiment of the present invention is for more clearly illustrating the technical solution of the embodiment of the present invention, and does not form a limitation on the technical solution provided in the embodiment of the present invention, and it can be known by a person skilled in the art that with the occurrence of a new application scenario, the technical solution provided in the embodiment of the present invention is also applicable to similar technical problems. In the description of the present invention, the term "plurality" means two or more unless otherwise specified.

The current application duration statistical scheme only counts the duration of each day when a certain application is used, and a detailed statistical scheme is not used in specific time periods in one day, so that a user cannot specifically check the time periods when the certain application is used, and cannot know the use condition of each application in detail. For the display of the statistical application duration in the prior art, as shown in fig. 2A, all APPs in the display list can display the application duration, and when a display instruction for a WeChat APP is received, the use duration of the APP within 7 days per day is displayed in the display window, as shown in fig. 2B, when a display instruction for another APP is received, the use duration of the APP within 7 days per day is displayed in the display window, but the use duration of the APP within one day can only be displayed no matter which APP is displayed, and the actual use duration of the APP used by the user cannot be displayed.

Aiming at the defects, the invention provides a method for carrying out sectional statistics on the application use duration, which can improve the fineness of the use condition of each application program, can ensure the accuracy of a statistical result, and has the advantages of small resource occupation and high efficiency.

Example 1

The following describes a method for applying the use duration segment statistics according to the present invention by using a specific embodiment.

The method provided by the embodiment of the invention mainly improves the method for counting the application service time in the prior art from three aspects, and on the first aspect, the method can monitor the application state in real time and has great real-time performance; in the second aspect, the accuracy of the use duration information is ensured by periodically updating the use duration information applied in the database while monitoring in real time; in a third aspect, the database structure of the embodiment has great advantages, the data stored in the database comprises the use date, the use time in the set time period and the total use time, the accuracy of the data stored in the database is guaranteed, the stored data can be periodically updated, frequent input/output (IO) reading and writing is avoided while effective updating is guaranteed, the resource occupation is small, and the efficiency is high.

Firstly, simply explaining application components in an Android system:

the four major components of the Android system are respectively: an Activity component for representing a function; a Service component, running a Service in the background, and providing no interface presentation; a Broadcast receiver (Broadcast Receive) component for receiving a Broadcast; the Content Provider (Content Provider) component supports storing and reading data in a plurality of applications, and is equivalent to a database.

The following mainly describes the Activity component and the Service component proposed by the embodiment of the present invention:

the Activity component is a visual interface operated by a user, provides a window for completing operation instructions for the user, and calls a setContentView () method to complete the display of the interface after the Activity is created, so as to provide an interactive entry for the user. An Activity Stack is maintained in an Android system, when a new Activity is created, the Activity is placed on the top of the Stack and is in a running state, when a new Activity is created, the Stack top is pressed again, the previous Activity is under the new Activity, and the previous Activity enters the background.

The stack is a specific memory area or register in the operating system, one end of the stack is fixed, the other end of the stack is floating, the data stored in the memory area has a special data structure, all the data is stored or taken out only at the floating end (namely the top of the stack), and the data is accessed strictly according to the principle of first-in and last-out. An Activity includes four states:

state 1, Running state (Running/Active)

Activity at this point is at the top of the stack, visible on the display interface and can interact with the user.

State 2, pause state (Paused)

When Activity is unable to interact with the user, but is still visible on the display interface, it is in a paused state. For example, a new non-full-screen Activity or a transparent Activity is placed on top of the stack, the Activity is in a paused state; various data of Activity are still maintained at this time; only in the state of extremely low memory in the system, the system will automatically destroy Activity.

State 3, stop state (stop)

When an Activity is completely covered by another Activity, or the Activity is in a stop state when the "HOME key" is clicked to go back to the background.

State 4, destroy state (Detroyed)

When a return key is clicked or the system is insufficient in memory, the Activity is removed from the stack and destroyed, and the Activity is recovered by the system, and then the Activity is in a destroyed state.

The Service component is usually located in the background and runs without interaction with a user, so the Service component has no graphical user interface, is usually used as time-consuming logic for processing in the background and executing tasks which do not need interaction with the user and need to run for a long time, and the Service does not depend on any user interface, so that the Service can still normally run even if the program is switched to the background or the user opens another application program. It should be noted, however, that the service is not run in a separate process, but depends on the application process in which the service was created, and if an application process is removed, all services that depend on the process will stop running.

Specifically, the Service states are divided into two types:

startup state (started): when an application component (e.g., Activity) invokes a startService () method to launch a service, the service is in a launch state, at which point the life cycle of the service is independent of the component that launched it, and the service can run indefinitely in the background, even if the component that launched the service has been destroyed.

Binding status (bound): when an application program component (such as Activity) calls a bindService () method to bind to a service, the service is in a binding state, at this time, the called application program component is bound with the service, and if the called application program component exits, the service is terminated.

In addition, a simple description is given of an MVC (Model View Controller) framework structure of an application program in the Android system:

model layer m (model): the Model layer is the main part of the application program, and all service logic is written in the Model layer, such as: the operation on the database, the operation on the network and the like are all at the Model layer.

View layer v (view): the view layer is a part in the application program responsible for generating a user interface, and is also the only layer which can be seen by a user in the whole MVC framework, and is used for receiving user input and displaying a processing result.

Control layer c (controller): the control layer is the part of the application that handles user interaction, and is typically responsible for reading data from the view layer, controlling user input, and sending data to the model layer.

Activity is mainly used for controlling in an Android system, for example, View to be displayed can be selected, data can be acquired from the View and then transmitted to a model layer for processing, and finally, a processing result is displayed.

As shown in fig. 3, the specific implementation flow of the method for applying the use duration segment statistics provided in this embodiment is as follows:

and 300, monitoring the state of the application in real time through a monitoring program.

As an optional implementation manner, the specific implementation steps of monitoring the state of the application in real time through the monitor are as follows:

1) monitoring the stack of an operating system in real time through a monitoring program;

2) if the stack is changed, acquiring a first application name to which an application component at the top of the stack belongs through the monitor, and acquiring a second application name to which the application component at the top of the stack currently belongs through a component of an operating system;

optionally, the Service component registers the tasksacklistener to monitor the stack of the operating system in real time, and if the stack changes, a result of an ontatskstackchanged callback is received, where the result of the callback includes a first application name to which the application component at the top of the stack belongs, which is acquired by the monitoring program, and at this time, a second application name to which the application component at the top of the stack belongs is acquired through the Activity component of the operating system.

3) If the first application name is consistent with the second application name, determining that the application corresponding to the second application name jumps from a background to a foreground;

and if the first application name is consistent with the second application name, the component of the second application is positioned at the top end of the current stack, the second application is visible in the display interface and can interact with a user, and the second application is determined to jump from the background to the foreground.

4) And if the first application name is inconsistent with the second application name, determining that the application corresponding to the second application name jumps from the foreground to the background.

If the first application name is consistent with the second application name, it is indicated that the component of the second application is not located at the top of the current stack, and the display interface of the second application is invisible, and it is determined that the second application jumps to the background from the foreground, that is, the second application is in a background state, which may be a closed state or a background running state, but none of the first application name and the second application name is interacted with the user.

As an alternative implementation, the listener in this embodiment is a service component in an operating system component. As can be seen from the above description of the service component, the service component is a component that does not interact with the user and runs for performing long-time operations or remote operations in the background, and even if a certain application exits, the process of the service component does not end, but runs in the background, so that the power consumption consumed by the terminal is small while real-time monitoring is ensured.

Step 301, when it is monitored that the application is in a state of jumping from a background to a foreground, taking the current system time as the starting time of using the application.

Step 302, in the process that the application is in the foreground, periodically updating the use duration information of the application in the database, wherein the use duration information comprises a use date, use duration in a set time period and total use duration.

And 303, when the application state is monitored to jump from the foreground to the background, taking the current system time as the end time of using the application, and updating the use duration information of the application in the database.

In the method provided in the embodiment of the present invention, optionally, a database is constructed for storing the usage duration information, and the stored information includes: the "date", the name of the application package (i.e. the application name in the embodiment of the present invention) "package _ name", the total usage time "time _ use", and the usage time "time _ use _ a _ b" in a set period, where the total usage time "time _ use" may be the total usage time in one day, i.e. the total usage time in the above date, a represents the starting time of the set period, and b represents the ending time of the set period, and the set period is a set period in 24h of one day, including but not limited to the following periods:

the point 0 to the point 1 "time _ use _0_ 1", the point 1 to the point 2 "time _ use _1_ 2", the point 2 to the point 3 "time _ use _2_ 3", and the like are sequentially pushed to the point 23 to the point 24 "time _ use _23_ 24".

When the application state is monitored to be the state that the application jumps from the background to the foreground, it can be understood that the application is the state that the application starts to be used at the moment, so that the moment of the current operating system is acquired while the situation that the application jumps from the background to the foreground is monitored, and the moment of the current operating system is used as the starting moment of using the application; in the process that the application is in the foreground, namely in the process that the application is used by a user, as the use duration of the user is not fixed and is random, the use duration information is periodically recorded and updated, optionally, the period is 1 minute, if the period selection is too short, the recording and updating times are frequent, more system resources are occupied, frequent IO reading and writing can be caused, the reasonable utilization of resources is not facilitated, and if the period selection is too long, the recorded use duration information is not accurate enough.

Optionally, the embodiment provides a countdown timer, which updates the usage duration information of the application in the database periodically by means of countdown, and the countdown timer may be set to count down for 1 minute.

When updating the database, 4 pieces of information in the database are mainly updated, namely an application name, a use date, a use duration in a set time period and a total use duration, wherein each piece of information sets a corresponding field, and data stored in each field is updated during updating, and the structure of the database is shown in table 1:

TABLE 1

date	package_name	time_use	time_use_0_1	time_use_a_b	time_use_23_24
						20190710	com.tencent.mm	600	50	…
20190710	com.hmct.xxx	300		…
						20190710	com.android.xxx	188		…
20190711	com.xx.xxx	866		…
						20190711	com.xx.xxx	188		…
…	…	…	…	…	…
						20190716	com.xx.xxx	888	88	…	…

The total usage time "time _ use" in the database field in table 1 is the sum of the usage times "time _ use _ a _ b" in each set period.

As shown in fig. 4, the specific implementation flow of the database update is as follows:

step 400, monitoring the state of the application in real time through a monitor program, and determining that the monitored state of the application is that the application jumps from a background to a foreground;

step 401, starting a countdown timer with a set time length;

alternatively, the set time period shown is 1 minute.

Step 402, judging whether the application is monitored to jump from the foreground to the background within a set time length, if so, executing step 403, otherwise, executing step 404;

step 403, taking the current system time as the end time of using the application, updating the use duration information of the application in the database, and returning to step 400;

step 404, when the set duration is over, updating the use duration information of the application in the database, and returning to step 401.

As shown in fig. 5, the following description of updating the database is made by taking the WeChat application as an example:

500, monitoring that the WeChat application jumps from a background to a foreground through a monitor;

step 501, recording the current system time as 8 points 30 in 7 months, 10 morning and 2019;

step 502, starting a 1 minute countdown timer;

step 503, judging whether the WeChat application is monitored to jump from the foreground to the background in the countdown period, if so, executing step 507, otherwise, executing step 504;

step 504, when 1 minute is finished, namely 8 points and 31 points, updating the database;

the specifically updated use duration information includes: the "date" field is 20190710, the "package _ name" field is com.ent.mm, the "time _ use" field is 60 (unit second), and since the record is 31 minutes from 8 points, the "time _ use _8_ 9" field is 60 (unit second), that is, the time length of the application from 8 points to 9 points is 60 seconds;

step 505, if the WeChat application is not monitored to jump from the foreground to the background, starting a count down timer for the next 1 minute, otherwise, executing step 507;

step 506, if the WeChat application is not monitored to jump from the foreground to the background within the countdown period, updating the database at 8 points and 32 minutes after 1 minute is finished, otherwise, executing step 507;

the specifically updated use duration information includes: the "date" field is 20190710, the "package _ name" field is com.ent.mm, the "time _ use" field is 120 (unit second), and since the record is 8 dots and 32 minutes, the "time _ use _8_ 9" field is 120 (unit second), that is, the time length of the application from 8 dots to 9 dots is 120 seconds;

and 507, taking the system time when the monitored WeChat application jumps from the foreground to the background as the end time of using the WeChat application, and updating the use duration information of the WeChat application in the database.

The specific update mechanism is described above and will not be described herein.

As shown in fig. 6, a framework structure for applying a usage duration segmentation statistic provided by an embodiment of the present invention includes: a listening layer 600, a storage layer 601, wherein:

the monitoring layer 600 is used for monitoring the state of the application in real time through a monitoring program;

the storage layer 601 is configured to store and periodically update the usage duration information of the applications in the database, where the updated usage duration information includes, but is not limited to: application name, use date, use duration in a set period, total use duration.

As an optional implementation manner, after the current system time is taken as the end time of using the application and the usage duration information of the application in the database is updated, the method further includes:

and counting the use duration, the total use duration and the average use duration of the application in each set time period in the database according to the set time interval.

Optionally, the usage duration information of each application in the database is counted every day, and/or the usage duration information of each application in the database is counted every week.

As an optional implementation manner, this embodiment further includes:

and responding to a chart display instruction, and displaying the use duration, the total use duration and the average use duration of the application in each set time period through a chart.

As shown in fig. 7A-7B, after receiving a user click chart display instruction, responding to the chart display instruction, and selecting an application, the usage duration information of the application in one day is displayed in a chart form.

Further, as shown in fig. 8A, the usage duration of a certain application in each set time period on the day and the total usage duration of the day are displayed by a graph; optionally, as shown in fig. 8B, the usage duration of a certain application in each day within 7 days and the average usage duration of the application in each day are displayed through a graph, and meanwhile, the usage duration of a certain application in each set time period and the total usage duration of the application in each day are displayed.

As shown in fig. 9, an embodiment of the present invention further provides a framework structure for applying the usage duration segmentation statistics, including: a listening layer 900, a storage layer 901, a graph layer 902, wherein:

the monitoring layer 900 is configured to monitor the state of the application in real time through a monitor;

the storage layer 901 is configured to store and periodically update the usage duration information of the applications in the database, where the updated usage duration information includes, but is not limited to: application name, use date, use duration in a set period, total use duration.

The chart layer 902 is configured to respond to a chart display instruction, and display, through a chart, the usage duration, the total usage duration, and the average usage duration of the application in each set time period.

Example 2

As shown in fig. 10, a detailed description is given below of a specific implementation flow of the method for applying the usage duration segment statistics according to this embodiment:

step 1000, monitoring the stack of the operating system in real time through a monitoring program;

1001, if the stack is changed, acquiring a first application name to which an application component at the top end of the stack belongs through the monitor, and acquiring a second application name to which the application component at the top end of the stack currently belongs through a component of an operating system;

step 1002, judging whether the first application name is consistent with the second application name, if so, executing step 1003, otherwise, executing step 1004;

step 1003, determining that the application corresponding to the second application name jumps from a background to a foreground, and executing 1005;

step 1004, determining that the application corresponding to the second application name jumps from the foreground to the background, and executing 1007;

step 1005, taking the current system time as the starting time of using the application;

step 1006, periodically updating the use duration information of the application in the database when the application is in the foreground;

step 1007, when the application state is monitored to jump from the foreground to the background, taking the current system time as the end time of using the application, and updating the use duration information of the application in the database;

step 1008, counting the use duration, the total use duration and the average use duration of the application in each set time period in the database according to the set time interval;

and step 1009, responding to the graph display instruction, and displaying the use duration, the total use duration and the average use duration of the application in each set time period through the graph.

Example 3

Based on the same inventive concept, the embodiment of the present invention further provides a first terminal applying the usage duration segmentation statistics, and since the terminal is the terminal in the method in the embodiment of the present invention and the principle of the device for solving the problem is similar to that of the method, the implementation of the device may refer to the implementation of the method, and repeated details are not repeated.

As shown in fig. 11, the terminal includes: a processor 1100 and a memory 1101, wherein the memory 1101 stores program code, and when one or more computer programs stored in the memory 1101 are executed by the processor 1100, the terminal is caused to perform the following processes:

monitoring the state of the application in real time through a monitoring program;

when the application state is monitored to be that the application jumps from a background to a foreground, taking the current system time as the starting time of using the application;

in the process that the application is in the foreground, periodically updating the use duration information of the application in a database, wherein the use duration information comprises a use date, use duration in a set time period and total use duration;

and when the application state is monitored to jump from the foreground to the background, the current system time is taken as the end time of using the application, and the use duration information of the application in the database is updated.

In one possible implementation, the processor 1100 is specifically configured to:

monitoring the stack of an operating system in real time through a monitoring program;

if the stack is changed, acquiring a first application name to which an application component at the top of the stack belongs through the monitor, and acquiring a second application name to which the application component at the top of the stack currently belongs through a component of an operating system;

if the first application name is consistent with the second application name, determining that the application corresponding to the second application name jumps from a background to a foreground;

and if the first application name is inconsistent with the second application name, determining that the application corresponding to the second application name jumps from the foreground to the background.

In a possible implementation manner, the processor 1100 is further specifically configured to:

and counting the use duration, the total use duration and the average use duration of the application in each set time period in the database according to the set time interval.

In a possible implementation manner, the processor 1100 is further specifically configured to:

and responding to a chart display instruction, and displaying the use duration, the total use duration and the average use duration of the application in each set time period through a chart.

In one possible implementation, the listener is a service component in an operating system component.

Example 4

Based on the same inventive concept, the embodiment of the present invention further provides a second terminal applying the usage duration segmentation statistics, and since the terminal is the terminal in the method in the embodiment of the present invention and the principle of the device for solving the problem is similar to that of the method, the implementation of the device may refer to the implementation of the method, and repeated details are not repeated.

As shown in fig. 12, the terminal includes: a monitoring module 1200, a start time determining module 1201, an update database module 1202, and an end time determining module 1203, where:

a monitoring module 1200, configured to monitor the state of the application in real time through a monitor;

a start time determining module 1201, configured to use the current system time as a start time for using the application when it is monitored that the application jumps from the background to the foreground;

the updating database module 1202 is configured to periodically update the use duration information of the application in the database when the application is in the foreground, where the use duration information includes a use date, a use duration in a set time period, and a total use duration;

an end time determining module 1203, configured to, when it is monitored that the state of the application is a jump from the foreground to the background, use the current system time as an end time of using the application, and update the information of the use duration of the application in the database.

In a possible implementation manner, the monitoring module 1200 is specifically configured to:

monitoring the stack of an operating system in real time through a monitoring program;

if the stack is changed, acquiring a first application name to which an application component at the top of the stack belongs through the monitor, and acquiring a second application name to which the application component at the top of the stack currently belongs through a component of an operating system;

if the first application name is consistent with the second application name, determining that the application corresponding to the second application name jumps from a background to a foreground;

and if the first application name is inconsistent with the second application name, determining that the application corresponding to the second application name jumps from the foreground to the background.

In a possible implementation manner, the terminal further includes a statistics module, specifically configured to:

and counting the use duration, the total use duration and the average use duration of the application in each set time period in the database according to the set time interval.

In a possible implementation manner, the terminal further includes a display module, specifically configured to:

and responding to a chart display instruction, and displaying the use duration, the total use duration and the average use duration of the application in each set time period through a chart.

In one possible implementation, the listener is a service component in an operating system component.

Based on the same inventive concept, the embodiment of the present invention further provides a third terminal applying the usage duration segmentation statistics, and since the terminal is the terminal in the method in the embodiment of the present invention and the principle of the device for solving the problem is similar to that of the method, the implementation of the device may refer to the implementation of the method, and repeated details are not repeated.

As shown in fig. 13, the terminal 1300 includes: radio Frequency (RF) circuitry 1310, a power supply 1320, a processor 1330, a memory 1340, an input unit 1350, a display unit 1360, a camera 1370, a communication interface 1380, and a Wireless Fidelity (Wi-Fi) module 1390. Those skilled in the art will appreciate that the configuration of the terminal shown in fig. 13 is not intended to be limiting, and that the terminal provided by the embodiments of the present application may include more or less components than those shown, or some components may be combined, or a different arrangement of components may be provided.

The following describes the components of the terminal 1300 in detail with reference to fig. 13:

the RF circuit 1310 may be used for receiving and transmitting data during a communication or conversation. In particular, the RF circuit 1310 sends downlink data of a base station to the processor 1330 for processing; and in addition, sending the uplink data to be sent to the base station. Generally, the RF circuit 1310 includes, but is not limited to, an antenna, at least one Amplifier, a transceiver, a coupler, a Low Noise Amplifier (LNA), a duplexer, and the like.

In addition, the RF circuit 1310 may also communicate with a network and other terminals through wireless communication. The wireless communication may use any communication standard or protocol, including but not limited to Global System for mobile communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), email, Short Messaging Service (SMS), and the like.

The Wi-Fi technology belongs to a short-distance wireless transmission technology, and the terminal 1300 can be connected to an Access Point (AP) through a Wi-Fi module 1390, thereby implementing Access to a data network. The Wi-Fi module 1390 can be used for receiving and sending data in a communication process.

The terminal 1300 may be physically connected to other terminals via the communication interface 1380. Optionally, the communication interface 1380 is connected to the communication interfaces of the other terminals through a cable, so as to implement data transmission between the terminal 1300 and the other terminals.

In the embodiment of the present application, the terminal 1300 can implement a communication service and send information to other contacts, so the terminal 1300 needs to have a data transmission function, that is, the terminal 1300 needs to include a communication module inside. Although fig. 13 illustrates communication modules such as the RF circuit 1310, the Wi-Fi module 1390, and the communication interface 1380, it is to be understood that at least one of the above components or other communication modules (e.g., bluetooth modules) for enabling communication exist in the terminal 1300 for data transmission.

For example, when the terminal 1300 is a mobile phone, the terminal 1300 may include the RF circuit 1310 and may further include the Wi-Fi module 1390; when the terminal 1300 is a computer, the terminal 1300 may include the communication interface 1380 and may further include the Wi-Fi module 1390; when the terminal 1300 is a tablet computer, the terminal 1300 may include the Wi-Fi module.

The memory 1340 may be used to store software programs and modules. The processor 1330 executes various functional applications and data processing of the terminal 1300 by executing software programs and modules stored in the memory 1340, and when the processor 1330 executes the program codes in the memory 1340, part or all of the processes in embodiment 1 of the present invention can be implemented.

Alternatively, the memory 1340 may mainly include a program storage area and a data storage area. Wherein, the storage program area can store an operating system, various application programs and the like; the storage data area may store data created according to the use of the terminal, such as use duration information of an application, and the like.

Further, the memory 1340 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device.

The input unit 1350 may be used to receive numeric or character information input by a user and generate key signal inputs related to user settings and function control of the terminal 1300.

Alternatively, the input unit 1350 may include a touch panel 1351 and other input terminals 1352.

The touch panel 1351, also called a touch screen, may collect touch operations of a user (such as operations of the user on or near the touch panel 1351 by using a finger, a stylus, or any other suitable object or accessory) thereon or nearby, and drive the corresponding connection device according to a preset program. Alternatively, the touch panel 1351 may include two parts, namely, a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 1330, and can receive and execute commands sent by the processor 1330. In addition, the touch panel 1351 may be implemented by various types, such as resistive, capacitive, infrared, and surface acoustic wave.

Optionally, the other input terminals 1352 may include, but are not limited to, one or more of a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like.

The display unit 1360 may be used to display information input by or provided to a user and various menus of the terminal 1300. The display unit 1360 is a display system of the terminal 1300, and is used for presenting an interface to implement human-computer interaction.

The display unit 1360 may include a display panel 1361. Alternatively, the Display panel 1361 may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-emitting diode (OLED), or the like.

Further, the touch panel 1351 can cover the display panel 1361, and when the touch panel 1351 detects a touch operation thereon or nearby, the touch panel is transmitted to the processor 1330 to determine the type of touch event, and then the processor 1330 provides a corresponding visual output on the display panel 1361 according to the type of touch event.

Although in fig. 13 the touch panel 1351 and the display panel 1361 are implemented as two separate components to implement the input and output functions of the terminal 1300, in some embodiments, the touch panel 1351 and the display panel 1361 can be integrated to implement the input and output functions of the terminal 1300.

The processor 1330 is a control center of the terminal 1300, connects various components using various interfaces and lines, performs various functions of the terminal 1300 and processes data by operating or executing software programs and/or modules stored in the memory 1340 and calling data stored in the memory 1340, thereby implementing various services based on the terminal.

Optionally, the processor 1330 may include one or more processing units. Optionally, the processor 1330 may integrate an application processor, which mainly handles operating systems, user interfaces, applications, etc., and a modem processor, which mainly handles wireless communications. It is to be appreciated that the modem processor described above may not be integrated into the processor 1330.

The camera 1370 is configured to implement a shooting function of the terminal 1300, and shoot pictures or videos. The camera 1370 may also be configured to implement a scanning function of the terminal 1300, and scan a scanned object (two-dimensional code/barcode).

The terminal 1300 also includes a power supply 1320 (e.g., a battery) for powering the various components. Optionally, the power supply 1320 may be logically connected to the processor 1330 through a power management system, so as to implement functions of managing charging, discharging, and power consumption through the power management system.

It should be noted that, the processor 1330 according to the embodiment of the present invention may perform the following steps:

monitoring the state of the application in real time through a monitoring program;

when the application state is monitored to be that the application jumps from a background to a foreground, taking the current system time as the starting time of using the application;

in the process that the application is in the foreground, periodically updating the use duration information of the application in a database, wherein the use duration information comprises a use date, use duration in a set time period and total use duration;

and when the application state is monitored to jump from the foreground to the background, the current system time is taken as the end time of using the application, and the use duration information of the application in the database is updated.

In a possible implementation manner, the processor 1330 is specifically configured to:

monitoring the stack of an operating system in real time through a monitoring program;

if the stack is changed, acquiring a first application name to which an application component at the top of the stack belongs through the monitor, and acquiring a second application name to which the application component at the top of the stack currently belongs through a component of an operating system;

if the first application name is consistent with the second application name, determining that the application corresponding to the second application name jumps from a background to a foreground;

and if the first application name is inconsistent with the second application name, determining that the application corresponding to the second application name jumps from the foreground to the background.

In a possible implementation manner, the processor 1330 is further specifically configured to:

and counting the use duration, the total use duration and the average use duration of the application in each set time period in the database according to the set time interval.

In a possible implementation manner, the processor 1330 is further specifically configured to:

and responding to a chart display instruction, and displaying the use duration, the total use duration and the average use duration of the application in each set time period through a chart.

In one possible implementation, the listener is a service component in an operating system component.

An embodiment of the present invention further provides a computer-readable non-volatile storage medium, which includes program code, and when the program code runs on a computing terminal, the program code is configured to enable the computing terminal to execute the following steps:

monitoring the state of the application in real time through a monitoring program;

when the application state is monitored to be that the application jumps from a background to a foreground, taking the current system time as the starting time of using the application;

in the process that the application is in the foreground, periodically updating the use duration information of the application in a database, wherein the use duration information comprises a use date, use duration in a set time period and total use duration;

and when the application state is monitored to jump from the foreground to the background, the current system time is taken as the end time of using the application, and the use duration information of the application in the database is updated.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.

Claims (10)

1. A method for applying piecewise statistics of usage duration, the method comprising:

monitoring the state of the application in real time through a monitoring program;

when the application state is monitored to be that the application jumps from a background to a foreground, taking the current system time as the starting time of using the application;

in the process that the application is in the foreground, periodically updating the use duration information of the application in a database, wherein the use duration information comprises a use date, use duration in a set time period and total use duration;

and when the application state is monitored to jump from the foreground to the background, the current system time is taken as the end time of using the application, and the use duration information of the application in the database is updated.

2. The method of claim 1, wherein monitoring the status of the application in real time by a monitor comprises:

monitoring the stack of an operating system in real time through a monitoring program;

if the stack is changed, acquiring a first application name to which an application component at the top of the stack belongs through the monitor, and acquiring a second application name to which the application component at the top of the stack currently belongs through a component of an operating system;

if the first application name is consistent with the second application name, determining that the application corresponding to the second application name jumps from a background to a foreground;

and if the first application name is inconsistent with the second application name, determining that the application corresponding to the second application name jumps from the foreground to the background.

3. The method according to claim 1, wherein after the step of using the current system time as the end time of using the application and updating the usage duration information of the application in the database, the method further comprises:

and counting the use duration, the total use duration and the average use duration of the application in each set time period in the database according to the set time interval.

4. The method of claim 3, further comprising:

and responding to a chart display instruction, and displaying the use duration, the total use duration and the average use duration of the application in each set time period through a chart.

5. The method of claim 1, wherein the listener is a service component in an operating system component.

6. A terminal for applying piecewise statistics of usage duration, the terminal comprising: a processor and a memory, wherein the memory stores program code that, when executed by the processor, causes the terminal to perform the following:

monitoring the state of the application in real time through a monitoring program;

when the application state is monitored to be that the application jumps from a background to a foreground, taking the current system time as the starting time of using the application;

in the process that the application is in the foreground, periodically updating the use duration information of the application in a database, wherein the use duration information comprises a use date, use duration in a set time period and total use duration;

and when the application state is monitored to jump from the foreground to the background, the current system time is taken as the end time of using the application, and the use duration information of the application in the database is updated.

7. The terminal of claim 6, wherein the processor is specifically configured to:

monitoring the stack of an operating system in real time through a monitoring program;

if the stack is changed, acquiring a first application name to which an application component at the top of the stack belongs through the monitor, and acquiring a second application name to which the application component at the top of the stack currently belongs through a component of an operating system;

if the first application name is consistent with the second application name, determining that the application corresponding to the second application name jumps from a background to a foreground;

and if the first application name is inconsistent with the second application name, determining that the application corresponding to the second application name jumps from the foreground to the background.

8. The terminal of claim 6, wherein the processor is further specifically configured to:

and counting the use duration, the total use duration and the average use duration of the application in each set time period in the database according to the set time interval.

9. The terminal of claim 8, wherein the processor is further specifically configured to:

and responding to a chart display instruction, and displaying the use duration, the total use duration and the average use duration of the application in each set time period through a chart.

10. The terminal of claim 6, wherein the listener is a service component in an operating system component.