Method, system, and apparatus for providing custom product support for a software program based upon states of program execution instability

• US 7,681,181 B2
• Filed: 09/30/2004
• Issued: 03/16/2010
• Est. Priority Date: 09/30/2004
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Coon, Thomas Scott, LeVine, Eric, Canning, Benjamin Elliott, Erlandson, Aaron Everett, White, Christopher Cameron, Greenberg, Steven Miles
• Primary Examiner(s): Zhen; Wei Y
• Assistant Examiner(s): Chen; Qing
• Application Number:
  US10/955,421
• Publication Number:
  US 20060070037A1
• Time in Patent Office: 1,993 Days
• Field of Search: 717124-135, 714/37, 714/38
• US Class Current: 717/127
• CPC Class Codes: G06F 11/34 Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
• CPC Class Codes: G06F 2201/865 Monitoring of software

Abstract

A method and apparatus are provided for providing custom product support for a computer program based on levels of execution instability. The execution of a software program is monitored over a period of time to determine the execution stability of the program. Based upon the monitoring and upon one or more threshold levels of instability, the execution stability of the program is categorized. Based upon the categorization, custom program support may be provided for a user of the computer system executing the program. For instance, based on the categorization free or reduced fee product support may be provided.

Claims

1. A method for providing custom product support for a software program based on states of program execution instability, the method comprising:

receiving a remote control file, the remote control file comprising at least one threshold level of program execution instability and at least one expiration date associated with the at least one threshold level of program execution instability;

monitoring, by a computing system comprising a processor coupled to a memory storage, execution of the software program over a period of time to determine execution stability of the software program by;

generating a session entry in a log each time the software program is executed, the session entry comprising data identifying the software program and a length of time the software program was executed,

periodically analyzing the log to generate at least one statistic that describes the execution stability of the software program according to the session entry, and

indicating whether the execution of the software program was terminated one of;

normally and abnormally, wherein an abnormal termination comprises at least one of;

a program crash, a program hang, and an abnormal program termination;

determining whether the at least one expiration date associated with the at least one threshold level of program execution instability has not passed;

in response to determining whether the at least one expiration date associated with the at least one threshold level of program execution instability has not passed, categorizing, by the computing system, the execution stability of the software program based on the at least one threshold level of program execution instability by comparing the at least one statistic to a corresponding threshold to categorize the execution stability of the software program into one of a plurality of states of program execution instability;

identifying, by the computing system, a previously established diagnostic state of the software program; and

providing the custom product support for the software program based upon the categorization and the previously established diagnostic state of the software program.

2. The method of claim 1, wherein analyzing the log to generate the at least one statistic that describes the execution stability of the software program comprises generating the at least one statistic comprising a number of abnormal terminations per number of program executions.

3. The method of claim 2, wherein analyzing the log to generate the at least one statistic that describes the execution stability of the software program further comprises generating the at least one statistic comprising the number of abnormal terminations per number of minutes of program execution.

4. The method of claim 1, wherein receiving the remote control file comprises receiving the remote control file containing data identifying the at least one threshold level of program execution instability for at least one version of the software program, and wherein the method further comprises determining whether the remote control file contains thresholds for the at least one version of the software program prior to categorizing the execution stability of the software program.

5. The method of claim 4, wherein providing the custom product support for the software program comprises directing a user of the software program to an information resource having one of:

free and reduced fee product support for the software program based upon the categorization.

6. The method of claim 4, wherein providing the custom product support for the software program comprises directing a user of the software program to an information resource identified based upon the categorization.

7. The method of claim 4, wherein providing the custom product support for the software program comprises executing a diagnostic program based upon the categorization.

8. A system for providing custom product support for a software program based on threshold levels of program execution instability, the system comprising:

a client computer operative to;

receive a remote control file from a server computer containing data identifying at least one threshold level of program execution instability for at least one version of the software program and at least one expiration date associated with the at least one threshold level of program execution instability,

monitor execution of a software program over a period of time to determine execution stability of the software program by;

generating a session entry in a log stored at the client computer each time the software program is executed, the session entry comprising data identifying the software program and a length of time the software program was executed,

periodically analyzing the log at the client computer to generate at least one statistic that describes the execution stability of the software program according to the session entry, and

indicating whether the execution of the software program was terminated one of;

normally and abnormally, wherein an abnormal termination comprises at least one of;

a program crash, a program hang, and an abnormal program termination,

determine whether the at least one expiration date associated with the at least one threshold level of program execution instability has not passed,

in response to determining whether the at least one expiration date associated with the at least one threshold level of program execution instability has not passed, categorize the execution stability of the software program based on the at least one threshold level of program execution instability contained in the remote control file by comparing the at least one statistic to a corresponding threshold to categorize the execution stability of the software program into one of a plurality of states of program execution instability,

identify a previously established diagnostic state of the software program, and

provide the custom product support for the software program based upon the categorization and the previously established diagnostic state of the software program.

9. The system of claim 8, wherein the at least one statistic comprises a number of abnormal terminations per number of program executions.

10. The system of claim 9, wherein the at least one statistic further comprises a number of abnormal terminations per number of minutes of program execution.

11. The system of claim 10, wherein the client computer being operative to provide the custom product support for the software program comprises the client computer being operative to direct a user to an information resource providing one of:

free and reduced fee product support depending on the at least one threshold level of program execution instability.

12. The system of claim 10, wherein the client computer being operative to provide the custom product support for the software program comprises the client computer being operative to direct a user of the client computer to an information resource, the information resource is determined based on the at least one threshold level of program execution instability.

13. The system of claim 10, wherein the client computer being operative to provide the custom product support for the software program comprises the client computer being operative to execute a diagnostic program on the client computer to diagnose problems with the software program.

14. A computer-readable storage medium having computer executable instructions stored thereon which, when executed by a computer, cause the computer to:

receive a remote control file, the remote control file comprising at least one threshold level of program execution instability and at least one expiration date associated with the at least one threshold level of program execution instability;

monitor execution of a software program over a period of time to determine execution stability of the software program by;

generating a session entry in a log each time the software program is executed, the session entry comprising data identifying the software program and a length of time the software program was executed,

periodically analyzing the log to generate at least one statistic that describes the execution stability of the software program according to the session entry, and

indicating whether the execution of the software program was terminated one of;

normally and abnormally, wherein an abnormal termination comprises at least one of;

a program crash, a program hang, and an abnormal program termination;

determine whether the at least one expiration date associated with the at least one threshold level of program execution instability has not passed;

in response to determining whether the at least one expiration date associated with the at least one threshold level of program execution instability has not passed, categorize the execution stability of the software program based on the at least one threshold level of program execution instability by comparing the at least one statistic to a corresponding threshold to categorize the execution stability of the software program into one of a plurality of states of program execution instability;

identify a previously established diagnostic state of the software program; and

provide custom product support for the software program based upon the categorization and the previously established diagnostic state of the software program.

15. The computer-readable storage medium of claim 14, wherein the at least one statistic comprises a number of abnormal terminations per number of program executions.

16. The computer-readable storage medium of claim 14, wherein the at least one statistic further comprises a number of abnormal terminations per number of minutes of program execution.

17. The computer-readable storage medium of claim 14, wherein the computer executable instructions further comprise instructions to execute a diagnostic program on the computer to diagnose problems with the software program.