SOFTWARE OPERABILITY SERVICE

• US 20120272103A1
• Filed: 04/21/2011
• Published: 10/25/2012
• Est. Priority Date: 04/21/2011
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Calinoiu, Silviu C., Matichuk, Chris Ernest, Petruta, Cristian G.
• Application Number:
  US13/091,494
• Publication Number:
  US 20120272103A1
• Time in Patent Office: Days
• US Class Current: 714/47.1
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites

Abstract

In embodiments of a software operability service, activities of software can be monitored to collect software activity data. A software operability signature for the software can then be generated from the software activity data, and the software operability signature indicates an operability of the software. The software operability signature and associated contextual data can then be communicated to a network service that analyzes the software operability signature. In an embodiment, the network service compares the software operability signature to a baseline operability signature to determine whether the software is operating consistent or inconsistent with the baseline operability signature.

Claims

1. A computer-implemented method, comprising:

receiving a software operability signature and associated contextual data from a computing device, the software operability signature indicating an operability of software operating on the computing device; and

comparing the software operability signature to a baseline operability signature of the software to determine whether the software is operating consistent with the baseline operability signature or inconsistent with the baseline operability signature.

2. A computer-implemented method as recited in claim 1, further comprising:

grouping additional software operability signatures received from additional computing devices, each of the additional software operability signatures indicating an operability of the software operating on the additional computing devices and being associated with contextual data that is the same or similar to the contextual data associated with the software operability signature; and

generating the baseline operability signature from the additional software operability signatures, the baseline operability signature indicating normal software operation.

3. A computer-implemented method as recited in claim 2, wherein the software operability signature and the additional software operability signatures are generated from monitoring the same or similar activities of the software.

4. A computer-implemented method as recited in claim 1, further comprising:

determining that the software is operating inconsistent with the baseline operability signature based on the software operability signature;

determining that the software operating inconsistent with the baseline operability signature corresponds to normal software operation; and

generating a new baseline operability signature of the software based on the software operability signature received for the software.

5. A computer-implemented method as recited in claim 1, further comprising:

determining that the software is operating inconsistent with a context of the baseline operability signature based on the software operability signature; and

analyzing the software operability signature to determine an operation failure of the software.

6. A computer-implemented method as recited in claim 5, further comprising:

determining a cause of the operation failure of the software from the comparison of the software operability signature to the context of the baseline operability signature; and

initiating a solution to mitigate the operation failure of the software.

7. A computer-implemented method as recited in claim 1, further comprising:

determining that the software is operating inconsistent with a context of the baseline operability signature based on the software operability signature; and

analyzing the software operability signature to determine an operation regression of the software.

8. A computer-implemented method as recited in claim 7, further comprising:

determining a cause of the operation regression of the software from the comparison of the software operability signature to the context of the baseline operability signature; and

initiating a solution to mitigate the operation regression of the software.

9. A computer-implemented method, comprising:

monitoring activities of software to collect software activity data;

generating a software operability signature for the software from the software activity data, the software operability signature indicating an operability of the software; and

communicating the software operability signature and associated contextual data to a network service that analyzes the software operability signature.

10. A computer-implemented method as recited in claim 9, wherein the software comprises at least one of a device driver, an application, firmware, or microcode, and wherein monitoring the software includes passively monitoring communications between the software and an operating system kernel to collect the software activity data.

11. A computer-implemented method as recited in claim 9, wherein the contextual data identifies an operating environment in which the software activity data is collected.

12. A computer-implemented method as recited in claim 9, wherein the software activity data is collected and the software operability signature is generated responsive to a triggering event.

13. A computer-implemented method as recited in claim 9, wherein the software is one of selected for monitoring based on one or more criteria, or selected for monitoring in response to receiving a request to monitor the software from the network service.

14. A computer-implemented method as recited in claim 9, further comprising receiving a request from the network service to monitor specific activities of the software.

15. A network service, comprising:

a data communication interface configured to receive a software operability signature and associated contextual data from a computing device, the software operability signature indicating an operability of an software operating on the computing device; and

at least a memory and a processor to implement a software operability service configured to compare the software operability signature to a baseline operability signature of the software to determine whether the software is operating consistent with the baseline operability signature or inconsistent with the baseline operability signature.

16. A network service as recited in claim 15, wherein the software operability service is further configured to:

group additional software operability signatures received from additional computing devices, each of the additional software operability signatures indicating an operability of the software operating on the additional computing devices and being associated with contextual data that is the same or similar to the contextual data associated with the software operability signature; and

generate the baseline operability signature from the additional software operability signatures, the baseline operability signature indicating normal software operation.

17. A network service as recited in claim 16, wherein the software operability signature and the additional software operability signatures are generated from monitoring the same or similar activities of the software.

18. A network service as recited in claim 15, wherein the software operability service is further configured to:

determine that the software is operating inconsistent with the baseline operability signature based on the software operability signature;

determine that the software operating inconsistent with the baseline operability signature corresponds to normal software operation; and

generate a new baseline operability signature of the software based on the software operability signature received for the software.

19. A network service as recited in claim 15, wherein the software operability service is further configured to:

determine that the software is operating inconsistent with the baseline operability signature based on the software operability signature; and

analyze the software operability signature to determine an operation failure or an operation regression of the software.

20. A network service as recited in claim 19, wherein the software operability service is further configured to:

determine a cause of the operation failure or the operation regression of the software from the comparison of the software operability signature to the baseline operability signature; and

initiate a solution to mitigate the operation failure or the operation regression of the software.