Reliable and accurate usage detection of a software application

• US 8,713,535 B2
• Filed: 06/30/2008
• Issued: 04/29/2014
• Est. Priority Date: 06/30/2008
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Malhotra, Nipoon, Viswanathan, Ram, Kakumani, Vikram, Gandhi, Mauktik H., Madakasira, Sarath, Li, Yiming, Sagi, Kiran
• Primary Examiner(s): Rampuria, Satish
• Application Number:
  US12/165,603
• Publication Number:
  US 20090327482A1
• Time in Patent Office: 2,129 Days
• Field of Search: 717104-115, 717124-126, 717168-178, 709201-226, 719311-332
• US Class Current: 717/127
• CPC Class Codes: G06F 11/3003 Monitoring arrangements specially adapted to the computing system or computing system component being monitored
• CPC Class Codes: G06F 11/3082 the data filtering being achieved by aggregating or compressing the monitored data
• CPC Class Codes: G06F 11/3419 by assessing time
• CPC Class Codes: G06F 11/3438 monitoring of user actions tracking the activity of the user H04L67/535
• CPC Class Codes: G06F 11/3466 Performance evaluation by tracing or monitoring
• CPC Class Codes: G06F 15/173 using an interconnection network, e.g. matrix, shuffle, pyramid, star, snowflake
• CPC Class Codes: G06F 2201/86 Event-based monitoring
• CPC Class Codes: G06F 2201/865 Monitoring of software
• CPC Class Codes: G06F 2201/88 Monitoring involving counting

Abstract

Use of software applications is detected by categorizing components of applications into a usage manifest and implementing a usage detection background service on a client PC that monitors the components according to the usage manifest. The application components are categorized based on the mode of user interaction as well as the component'"'"'s correlation to active use of an application. The background service tracks events and activities associated with the application components to generate usage metrics that include the frequency of unique launches of an application and the duration of each unique use. A usage manager for the background service may utilize the usage metrics for a component independently, or combine metrics for multiple components in cases where applications work in an interactive manner (such as a plug-in to a web browser) in order to compute application usage by comparing the metrics against predefined thresholds.

Claims

1. A method for detecting software application usage on a client device, the method comprising the steps of:

categorizing components of applications that are instantiated on the client device, the categorization being performed based on at least one of usage pattern of the components or correlation of the components to active usage, the categorization classifying the components into categories that includes primary processes, user interaction with a user interface and auxiliary processes, wherein primary processes run when the application is being actively used, and terminate when the application is not being actively used, user interaction with a user interface interaction enables detection of the software application usage by monitoring interaction patterns with the user interface, and auxiliary processes run without correlation to application usage;

providing the categorized components as elements in a usage manifest that is published to the client device, the categorized components being respectively monitored by a plurality of usage counters for generating usage metrics based on a frequency of unique launches of an application or a duration of each unique use of an application responsively to the monitoring; and

implementing a software usage detection service on the client device, the software usage detection service arranged for monitoring one or more of the components according to the usage manifest to detect usage of the applications based on the categorization of the one or more components.

2. The method of claim 1 in which the usage pattern comprises one of UI interaction through a window or pop up or silent monitoring of the client device.

3. The method of claim 1 including a further step of arranging the elements in the usage manifest to generate one or more signatures for the applications.

4. The method of claim 1 including a further step of categorizing the components based on an intended purpose of the components.

5. The method of claim 1 including a further step of categorizing the components based on processes operating on the client device.

6. The method of claim 1 including a further step of categorizing the components based on an integration of functionality between applications.

7. The method of claim 1 in which a functionality is provided by one of application plug-in, application add-on, or application extension.

8. A computer-readable medium being distinguishable from a transmission signal and containing instructions which, when executed by one or more processors disposed on an electronic device, implements a software application usage detection service arranged for performing a method comprising the steps of:

implementing a plurality of usage counters that monitor respective components of applications that are instantiated on the electronic device, the components being described by a usage manifest, the usage manifest including elements for categorized components, the categorization being performed based on at least one of usage pattern of the components or correlation of the components to active usage, the categorization classifying the components into categories that includes primary processes, user interaction with a user interface and auxiliary processes, wherein primary processes run when the application is being actively used, and terminate when the application is not being actively used, user interaction with a user interface interaction enables detection of the software application usage by monitoring interaction patterns with the user interface, and auxiliary processes run without correlation to application usage, the usage counters further generating usage metrics based on a frequency of unique launches of an application or a duration of each unique use of an application responsively to the monitoring; and

implementing a usage manager that is configured for receiving the usage metrics, from one or more of the usage counters, and for computing application usage by comparing the received usage metrics against one or more predetermined thresholds.

9. The computer-readable medium of claim 8 in which the usage metrics include frequency of unique launches of an application.

10. The computer-readable medium of claim 8 in which the usage metrics include duration of each unique use of an application.

11. The computer-readable medium of claim 8 including a further step of configuring the usage counters to perform the monitoring using polling or to perform the monitoring in response to events generated by the applications.

12. The computer-readable medium of claim 8 in which the usage metrics from a single usage counter are utilized independently to compute the application usage.

13. The computer-readable medium of claim 8 in which the usage metrics from a plurality of usage counters are combined to compute the application usage.

14. A method for measuring usage of a composite software application, the method comprising the steps of:

identifying components in the application by the components'"'"' correlation with active user interaction and further by a mode of interaction of the components in order to derive usage patterns for the components;

classifying the components by the usage patterns into categories that include primary processes, user interaction with a user interface and auxiliary processes, wherein primary processes run when the application is being actively used, and terminate when the application is not being actively used, user interaction with a user interface interaction enables detection of the software application usage by monitoring interaction patterns with the user interface, and auxiliary processes run without correlation to application usage, the classified components being respectively monitored by a plurality of usage counters for generating usage metrics based on a frequency of unique launches of an application or a duration of each unique use of an application responsively to the monitoring;

implementing one or more monitoring techniques that are specific to each of the classified components;

collecting usage metrics from the monitoring for each classification of the components; and

computing a usage for the application based on the usage metrics with the usage counter of the application.

15. The method of claim 14 in which the components comprise a primary process that runs when the application is being actively used, and terminates when the application is not being actively used.

16. The method of claim 14 in which the components comprise a UI window which is open or which receives focus when the application is being actively used.

17. The method of claim 14 in which the components comprise a browser add-on or application extension that is loaded when the application is being actively used.

18. The method of claim 14 in which the components comprise a process that opens a network port or exchanges data over a network.

19. The method of claim 14 in which the components comprise an auxiliary process that does not have an explicit correlation with usage of the application.

20. A client device configured for detecting software application usage comprising:

a user interface;

a network port configured for data packet exchange with a network that is external to the client device; and

a software detection background service configured for

categorizing components of applications that are instantiated on the client device, the categorization being performed based on at least one of usage pattern of the components or correlation of the components to active usage, the categorization classifying the components into categories that includes primary processes, user interaction with a user interface and auxiliary processes, wherein primary processes run when the application is being actively used, and terminate when the application is not being actively used, user interaction with a user interface interaction enables detection of the software application usage by monitoring interaction patterns with the user interface, and auxiliary processes run without correlation to application usage,

providing the categorized components as elements in a usage manifest that is published to the client device, the categorized components being respectively monitored by a plurality of usage counters for generating usage metrics based on a frequency of unique launches of an application or a duration of each unique use of an application responsively to the monitoring, and

implementing a software usage detection service on the client device, the software usage detection service arranged for monitoring one or more of the components according to the usage manifest to detect usage of the applications based on the categorization of the one or more components.

21. The client device of claim 20 in which the usage pattern comprises one of UI interaction through a window or pop up or silent monitoring of the client device,

22. The client device of claim 20 in which the software detection background service is further configured for arranging the elements in the usage manifest to generate one or more signatures for the applications.

23. The client device of claim 20 in which the software detection background service is further configured for categorizing the components based on an intended purpose of the components.

24. The client device of claim 20 in which the software detection background service is further configured for categorizing the components based on processes operating on the client device.

25. The client device of claim 20 in which the software detection background service is further configured for categorizing the components based on an integration of functionality between applications.

26. The client device of claim 20 in which a functionality is provided by one of application plug-in, application add-on, or application extension.