METHODS FOR CONTROLLING SOFTWARE USAGE

• US 20130339251A1
• Filed: 06/14/2013
• Published: 12/19/2013
• Est. Priority Date: 06/15/2012
• Status: Active Grant

• Current Assignee: Infosys Limited
• Original Assignee: Infosys Limited
• Inventors: Saxena, Ashutosh, Ponnapalli, Harigopal K. B., Gorantla, Malakondayya Choudary, Jain, Ina
• Granted Patent: US 9,792,417 B2
• Time in Patent Office: Days
• US Class Current: 705/59
• 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]

Abstract

Methods for controlling software usage are described. Methods comprise receiving a request for at least one software application license, wherein the request comprises a user count, generating, by the computing apparatus, one or more sets of license data in response to the request, wherein a set of license data comprises at least one of the user count and a corresponding sequence number, signing each of the one or more sets of license data digitally with a private key, embedding a set of signed license data into the software application, receiving user identification data from a user through an input interface associated with the computing apparatus, and validating the user identification data. Additional embodiments incorporate mechanisms for license renewal, user registration and user authentication by means of associating a range of user identification data with the license data.

Claims

1. A computer implemented method for controlling software usage, the method comprising:

receiving a request for at least one software application license by a computing apparatus comprising at least one processor and a readably coupled memory, wherein the request comprises a user count;

generating, by the computing apparatus, one or more sets of license data in response to the request, wherein a set of license data comprises at least one of the user count and a corresponding sequence number;

signing each of the one or more sets of license data digitally with a private key;

embedding a set of signed license data into the software application;

receiving user identification data from a user through an input interface associated with the computing apparatus; and

validating the user identification data.

2. The computer implemented method as claimed in claim 1, further comprising renewing the license data, wherein renewing comprises:

receiving a request comprising an additional user count for at least one license;

updating the one or more sets of license data with the additional user count;

signing each of the one or more sets of updated license data digitally with a private key; and

embedding a set of signed updated license data into the software application.

3. The computer implemented method as claimed in claim 1, further comprising checking for the availability of a license, wherein checking comprises comparing the sequence number with user count on receiving a request.

4. The computer implemented method as claimed in claim 3, further comprising transmitting a non-availability message to a user by means of an output interface associated with the computing apparatus if the sequence number matches the user count.

5. The computer implemented method as claimed in claim 4, further comprising associating a user with the software application, wherein associating comprises:

generating a first number;

validating the set of signed license data embedded in the software application against a retrieved set of signed license data;

generating user identification data, wherein user identification data includes a user group attribute and a user identification number attribute; and

mapping the first number and user identification data to the set of signed license data.

6. The computer implemented method as claimed in claim 5, further comprising encrypting the first number and user identification data and storing the encrypted data in a database.

7. The computer implemented method as claimed in claim 6, wherein validating comprises comparing the received user identification data with the user identification data.

8. The computer implemented method as claimed in claim 1, further comprising deassociating a user from the software application, wherein deassociating comprises deleting the user identification data.

9. The computer implemented method as claimed in claim 8, further comprising restoring a deassociated user, wherein restoring comprises:

receiving user identification data;

checking for license availability;

generating a second number and assigning the second number to the user identification data received if a license is available; and

storing the user identification data in a database.

10. A non-transitory computer readable storage medium having stored thereon computer executable instructions for performing a method for controlling software usage, the method comprising:

receiving a request for at least one software application license by a computing apparatus comprising at least one processor and a readably coupled memory, wherein the request comprises a user count;

generating, by the computing apparatus, one or more sets of license data in response to the request, wherein a set of license data comprises at least one of the user count and a corresponding sequence number;

signing each of the one or more sets of license data digitally with a private key;

embedding a set of signed license data into the software application;

receiving user identification data from a user through an input interface associated with the computing apparatus; and

validating the user identification data.

11. The method as claimed in claim 10, further comprising renewing the license data, wherein renewing comprises:

receiving a request comprising an additional user count for at least one license;

updating the one or more sets of license data with the additional user count;

signing each of the one or more sets of updated license data digitally with a private key; and

embedding a set of signed updated license data into the software application.

12. The method as claimed in claim 10, further comprising checking for the availability of a license, wherein checking comprises comparing the sequence number with user count on receiving a request.

13. The method as claimed in claim 12, further comprising transmitting a non-availability message to a user by means of an output interface associated with the computing apparatus if the sequence number matches the user count.

14. The method as claimed in claim 13, further comprising associating a user with the software application, wherein associating comprises:

generating a first number;

validating the set of signed license data embedded in the software application against a retrieved set of signed license data;

generating user identification data, wherein user identification data includes a user group attribute and a user identification number attribute; and

mapping the first number and user identification data to the set of signed license data.

15. The method as claimed in claim 14, further comprising encrypting the first number and user identification data and storing the encrypted data in a database.

16. The method as claimed in claim 15, wherein validating comprises comparing the received user identification data with the user identification data.

17. The method as claimed in claim 10, further comprising deassociating a user from the software application, wherein deassociating comprises deleting the user identification data.

18. The method as claimed in claim 17, further comprising restoring a deassociated user, wherein restoring comprises:

receiving user identification data;

checking for license availability;

generating a second number and assigning the second number to the user identification data received if a license is available; and

storing the user identification data in a database.