Methods and apparatus to credit background applications
Methods, apparatus and computer readable storage medium are disclosed to monitor media exposure. Examples disclosed herein include a creditor to determine whether a bandwidth usage pattern of an application is spiked or continuous based on a first event record representative of background execution of the application being started, access a second event record associated with the application, update the second event record to be representative of the background execution of the application being stopped when the bandwidth usage pattern is spiked and a timestamp of the second event record exceeds a temporal activity window, and determine a duration of background execution of the application based on the first event record and the second event record.
1. An apparatus comprising:
a network usage monitor to compare bandwidth usage of an application executing in a background of a device to a threshold to determine a state of the application as one of active or inactive, the threshold based on a bandwidth usage pattern of the application;
a logger to log event records associated with the application, the event records including the state of the application; and
a creditor to:
determine whether the bandwidth usage pattern is spiked or continuous based on a first event record representative of background execution of the application being started;
access a second event record associated with the application;
update the second event record to be representative of the background execution of the application being stopped when the bandwidth usage pattern is spiked and a timestamp of the second event record exceeds a temporal activity window; and
determine a duration of background execution of the application based on the first event record and the second event record.
2. The apparatus of claim 1 , wherein the creditor is to update the second event record to be representative of the background execution of the application being stopped when the bandwidth usage pattern is continuous and the second event record associated with the application indicates application inactivity.
3. The apparatus of claim 1 , wherein the creditor is to reference a table listing applications and associated bandwidth usage patterns when information indicating whether the bandwidth usage pattern is spiked or continuous is not included in the first event record.
4. The apparatus of claim 1 , wherein the network usage monitor is to:
identify the bandwidth usage pattern as spiked when data processed by the application is downloaded in increments for future presentation to a user; and
identify the bandwidth usage pattern as continuous when the data processed by the application is downloaded continuously while the application is presenting to the user in real-time.
5. The apparatus of claim 1 , wherein the network usage monitor is to use the temporal activity window to determine whether the application is active during a time period when the bandwidth usage of the application is below the threshold, the temporal activity window to occur after the time period.
6. The apparatus of claim 1 , wherein when the timestamp of the second event record exceeds the temporal activity window, the creditor is to update the second event record to indicate the background execution of the application stopped at an end of the temporal activity window.
7. The apparatus of claim 1 , wherein when the timestamp of the second event record does not exceed the temporal activity window, the creditor is to reset the temporal activity window to a timestamp of a subsequent third event record associated with the application.
8. The apparatus of claim 7 , wherein when the bandwidth usage pattern is spiked and the timestamp of the second event record does not exceed the temporal activity window, the creditor is to iterate through subsequent ones of the event records associated with the application until a timestamp of a first one of the subsequent ones of the event records exceeds the temporal activity window, the creditor to update the first one of the subsequent ones of the event records to be representative of the background execution of the application being stopped.
9. A method comprising:
comparing, by executing an instruction with a processor, bandwidth usage of an application executing in a background of a device to a threshold to determine a state of the application as one of active or inactive, the threshold based on a bandwidth usage pattern of the application;
logging event records associated with the application, the event records including the state of the application;
determining, by executing an instruction with the processor, whether the bandwidth usage pattern is spiked or continuous based on a first event record representative of background execution of the application being started;
accessing a second event record associated with the application;
updating, by executing an instruction with the processor, the second event record to be representative of the background execution of the application being stopped when the bandwidth usage pattern is spiked and a timestamp of the second event record exceeds a temporal activity window; and
determining a duration of background execution of the application based on the first event record and the second event record.
10. The method of claim 9 , further including updating the second event record to be representative of the background execution of the application being stopped when the bandwidth usage pattern is continuous and the second event record associated with the application indicates application inactivity.
11. The method of claim 9 , further including referencing a table listing applications and associated bandwidth usage patterns when information indicating whether the bandwidth usage pattern is spiked or continuous is not included in the first event record.
12. The method of claim 9 , further including:
identifying the bandwidth usage pattern as spiked when data processed by the application is downloaded in increments for future presentation to a user; and
identifying the bandwidth usage pattern as continuous when the data processed by the application is downloaded continuously while the application is presenting to the user in real-time.
13. The method of claim 9 , further including using the temporal activity window to determine whether the application is active during a time period when the bandwidth usage of the application is below the threshold, the temporal activity window to occur after the time period.
14. The method of claim 9 , wherein when the temporal activity window has been exceeded, updating the second event record to indicate the background execution of the application stopped at an end of the temporal activity window.
15. The method of claim 9 , further including, when the timestamp of the second event record exceeds the temporal activity window, resetting the temporal activity window to a timestamp of a subsequent third event record associated with the application.
16. The method of claim 15 , further including, when the bandwidth usage pattern is spiked and the timestamp of the second event record does not exceed the temporal activity window:
iterating through subsequent ones of the event records associated with the application until a timestamp of a first one of the subsequent ones of the event records exceeds the temporal activity window; and
updating the first one of the subsequent ones of the event records to be representative of the background execution of the application being stopped.
17. A non-transitory computer readable storage medium comprising computer readable instructions that, when executed, cause one or more processors to at least:
compare bandwidth usage of an application executing in a background of a device to a threshold to determine a state of the application as one of active or inactive, the threshold based on a bandwidth usage pattern of the application;
log event records associated with the application, the event records including the state of the application;
determine whether the bandwidth usage pattern is spiked or continuous based on a first event record representative of background execution of the application being started;
access a second event record associated with the application;
update the second event record to be representative of the background execution of the application being stopped when the bandwidth usage pattern is spiked and a timestamp of the second event record exceeds a temporal activity window; and
determine a duration of background execution of the application based on the first event record and the second event record.
18. The storage medium of claim 17 , wherein the instructions, when executed, cause the one or more processors to update the second event record to be representative of the background execution of the application being stopped when the bandwidth usage pattern is continuous and the second event record associated with the application indicates application inactivity.
19. The storage medium of claim 17 , wherein the instructions, when executed, cause the one or more processors to reference a table listing applications and associated bandwidth usage patterns when information indicating whether the bandwidth usage pattern is spiked or continuous is not included in the first event record.
20. The storage medium of claim 17 , wherein the instructions, when executed, cause the one or more processors to:
identify the bandwidth usage pattern as spiked when data processed by the application is downloaded in increments for future presentation to a user; and
identify the bandwidth usage pattern as continuous when the data processed by the application is downloaded continuously while the application is presenting to the user in real-time.