INSTRUMENTATION FOR ALARMING A SOFTWARE PRODUCT

• US 20060174346A1
• Filed: 01/31/2005
• Published: 08/03/2006
• Est. Priority Date: 01/31/2005
• Status: Abandoned Application

• Current Assignee: BeyondTrust Software, Inc. (BeyondTrust Corp.)
• Original Assignee: Lieberman Software Corp. (BeyondTrust Corp.)
• Inventors: Carroll, Nicholas M., Lieberman, Philip, Schwartz, Jotham, Fredrickson, Jason A.
• Application Number:
  US10/906,028
• Publication Number:
  US 20060174346A1
• Time in Patent Office: Days
• US Class Current: 726/26
• CPC Class Codes: G06F 21/10 Protecting distributed programs or content, e.g. vending or licensing of copyrighted material protection in video systems or pay television H04N7/16 ; Digital rights management [DRM]
• CPC Class Codes: G06F 21/105 Arrangements for software license management or administration, e.g. for managing licenses at corporate level
• CPC Class Codes: G06F 21/121 Restricting unauthorised execution of programs
• CPC Class Codes: G06F 2221/2101 Auditing as a secondary aspect
• CPC Class Codes: G06F 2221/2135 Metering

Abstract

An instrumentation for alarming a software product (210) that is subject to a license (108). An alarm client (212) is incorporated with the software product to collect usage information about the software product while it runs on a computer. This usage information permits determining whether the software product is being used in accord with the license. The alarm client further communicates an activity message (224) including the usage information to a remote server (214) via a communications network (220).

Claims

1. An instrumentation for alarming a software product that is subject to a license, comprising:

an alarm client incorporated with the software product;

said alarm client to collect usage information about the software product while it runs on a computer, wherein said usage information permits determining whether the software product is being used in accord with the license; and

said alarm client further to communicate an activity message including said usage information to a remote server via a communications network.

2. The instrumentation of claim 1, wherein said alarm client determines whether a selected operation is performed or not performed while the software product runs and said alarm client includes event data about said operation in said activity message.

3. The instrumentation of claim 2, wherein said operation is activation of the software product on said computer.

4. The instrumentation of claim 2, wherein said operation is altering or disabling a portion of the software product or said alarm client.

5. The instrumentation of claim 2, wherein said alarm client includes a unique identifier for said event data in said activity message, thereby permitting correlation of multiple instances of said event data or multiple said activity messages.

6. The instrumentation of claim 1, wherein said alarm client includes in said activity message at least one of a license key under which the software product was activated, user data which the software product was activated, and organization data under which the software product was activated.

7. The instrumentation of claim 1, wherein said alarm client periodically determines activity of the software product on said computer and includes event data about said activity in said activity message.

8. The instrumentation of claim 7, wherein said alarm client includes in said activity message an identifier of at least one of an end-user running the software product and said computer running the software product.

9. The instrumentation of claim 8, wherein said identifier is a login name of said end-user.

10. The instrumentation of claim 8, wherein said identifier is a unique value representing said end-user but not specifically identifying them by name.

11. The instrumentation of claim 1, wherein said alarm client receives an instruction from said server specifying at least one of what said usage information to include in said activity message and how to communicate said activity message via said communications network.

12. The instrumentation of claim 11, wherein said alarm client determines what said usage information to include in said activity message based on a license key under which the software product was activated.

13. The instrumentation of claim 12, wherein said determination is made based on a heuristic or algorithmic analysis of said license key.

14. The instrumentation of claim 1, wherein said alarm client is able to selectively impede or terminate running of the software product.

15. The instrumentation of claim 14, wherein said alarm client receives an instruction from said server specifying that the software product be terminated or impeded.

16. The instrumentation of claim 1, wherein:

said alarm client determines whether an attempt to communicate said activity message was successful; and

if not, said alarm client retries communicating said activity message using at least one of increasing the frequency of efforts to communicate said activity message, using an alternate said server, using an alternate parameter for communicating via said communications network, and using an alternate said communications network.

17. The instrumentation of claim 1, wherein:

said alarm client determines whether an attempt to communicate said activity message was successful; and

if not, said alarm client impedes or terminates running of the software product.

18. A method for monitoring a software product subject to a license, comprising:

collecting usage about the software product while the software product runs on a computer, wherein said usage information permits analysis to determine whether the software product is being used in accord with the license; and

communicating an activity message including said usage information to a remote server via a communications network.

19. The method of claim 18, further comprising:

determining whether a selected operation is performed or not performed while the software product runs; and

including event data about said operation in said activity message.

20. The method of claim 19, wherein said operation is activation of the software product on said computer.

21. The method of claim 19, wherein said operation is altering or disabling a portion of the software product or said instrumentation.

22. The method of claim 19, further comprising including a unique identifier for said event data in said activity message, thereby permitting correlation of multiple instances of said event data or multiple said activity messages.

23. The method of claim 18, further comprising including in said activity message at least one of a license key under which the software product was activated, user data under which the software product was activated, and organization data under which the software product was activated.

24. The method of claim 18, further comprising:

periodically determining activity of the software product on said computer; and

including event data about said activity in said activity message.

25. The method of claim 24, further comprising:

collecting an identifier of at least one of an end-user running the software product and said computer running the software product; and

including said identifier in said activity message.

26. The method of claim 25, wherein said identifier is a login name of said end-user.

27. The method of claim 25, wherein said identifier is a unique value representing said end-user but not specifically identifying them by name.

28. The method of claim 18, further comprising receiving an instruction from said server specifying at least one of what said usage information to include in said activity message and how to communicate said activity message via said communications network.

29. The method of claim 28, further comprising determining what said usage information to include in said activity message based on a license key under which the software product was activated.

30. The method of claim 29, further comprising basing said determination on a heuristic or algorithmic analysis of said license key.

31. The method of claim 18, further comprising selectively impeding or terminating running of the software product.

32. The method of claim 31, further comprising receiving an instruction with a selection from said server.

33. The method of claim 18, further comprising:

determining whether said communicating of said activity message was successful; and

if not, re-communicating said activity message using at least one of increasing the frequency of efforts to communicate said activity message, using an alternate said server, using an alternate parameter for communicating via said communications network, and using an alternate said communications network.

34. The method of claim 18, wherein:

determining whether said communicating of said activity message was successful; and

if not, impeding or terminating running of the software product.