System and Method for Auditing Software Usage

• US 20100325149A1
• Filed: 06/18/2010
• Published: 12/23/2010
• Est. Priority Date: 06/22/2009
• Status: Abandoned Application

• Current Assignee: Uniloc Luxembourg S.à r.l. (f/k/a Uniloc Luxembourg S.A.) (Uniloc Corporation Pty. Limited)
• Original Assignee: Uniloc Luxembourg S.à r.l. (f/k/a Uniloc Luxembourg S.A.) (Uniloc Corporation Pty. Limited)
• Inventors: Etchegoyen, Craig Stephen
• Application Number:
  US12/819,017
• Publication Number:
  US 20100325149A1
• Time in Patent Office: Days
• US Class Current: 707/769
• CPC Class Codes: G06F 11/3409 for performance assessment
• CPC Class Codes: G06F 11/3466 Performance evaluation by tracing or monitoring
• CPC Class Codes: G06F 11/3495 for systems
• CPC Class Codes: G06F 21/12 Protecting executable software
• CPC Class Codes: G06F 2201/815 Virtual
• CPC Class Codes: G06F 2201/86 Event-based monitoring
• CPC Class Codes: G06F 2201/865 Monitoring of software
• CPC Class Codes: G06F 2201/885 Monitoring specific for caches
• CPC Class Codes: G06F 2221/2101 Auditing as a secondary aspect

Abstract

A system for auditing the use of software on a computing device comprises a data collection server. In response to a communication link being available between the data collection server and the computing device, the data collection server is configured to: (1) receive from the computing device, via the communication link, data including (a) a software identifier identifying the software, (b) a device identifier identifying the computing device, and (c) an event identifier identifying a usage event performed by the software; (2) access a database storing previously received software identifiers, device identifiers, and event identifiers; and (3) update the database to include the received data. A method for auditing the use of software on a computing device is also disclosed.

Claims

1. A system for auditing the use of software on a computing device, the system comprising:

a data collection server which, in response to a communication link being available between the data collection server and the computing device, is configured to;

receive from the computing device, via the communication link, data including (a) a software identifier identifying the software, (b) a device identifier identifying the computing device, and (c) an event identifier identifying a usage event performed by the software;

access a database storing previously received software identifiers, device identifiers, and event identifiers; and

update the database to include the received data.

2. The system of claim 1, wherein the software identifier comprises at least one of a product identifier, a software signature, a software version number, and a license identifier.

3. The system of claim 1, wherein the event identifier includes a time stamp indicating a usage event time.

4. The system of claim 1, wherein the usage event comprises one of an initialization event, an upgrade event, a licensing event, and a restricted feature event.

5. The system of claim 4, wherein following the upgrade event, the data further includes a software version identifier.

6. The system of claim 4, wherein following the licensing event, the data further includes a license identifier.

7. The system of claim 1, wherein, to update the database, the data collection server is further configured to:

compare the received device identifier and software identifier with the device identifiers and software identifiers, respectively, stored within the database;

update records within the database to reflect the received data where at least one of the received device identifier and software identifier is already stored within the database; and

add a record to the database to reflect the received data where neither of the received device identifier and software identifier is already stored within the database.

8. A method for auditing the use of software on a computing device, the method comprising:

establishing a communication link between a data collection server and the computing device;

receiving at the data collection server from the computing device, via the communication link, data including (a) a software identifier identifying the software, (b) a device identifier identifying the computing device, and (c) an event identifier identifying a usage event performed by the software;

accessing a database storing previously received and associated software identifiers, device identifiers, and event identifiers; and

updating the database to include the received data.

9. The method of claim 8, wherein the software identifier comprises at least one of a product identifier, a software signature, a software version number, and a license identifier.

10. The method of claim 8, wherein the event identifier includes a time stamp indicating a usage event time.

11. The method of claim 8, wherein the usage event comprises one of an initialization event, an upgrade event, a licensing event, and a restricted feature event.

12. The method of claim 11, wherein following the upgrade event, the data further includes a software version identifier.

13. The method of claim 11, wherein following the licensing event, the data further includes a license identifier.

14. The method of claim 8, further comprising querying the database to identify device identifiers associated with each of an initialization event, a licensing event, and a restricted feature event.

15. The method of claim 8, further comprising querying the database to identify device identifiers associated with each of an initialization event and a restricted feature event, but not a licensing event.

16. The method of claim 8, further comprising querying the database to identify device identifiers associated with each of an initialization event and a substantially contemporaneous licensing event.

17. The method of claim 8, wherein updating the database includes:

comparing the device identifier and software identifier in the received data with the device identifiers and software identifiers, respectively, stored within the database;

updating records within the database to reflect the received data where at least one of the device identifier and software identifier in the received data is already included in the database;

adding a record to the database to reflect the received data where neither of the device identifier and software identifier in the received data is already included in the database.