Method and system for single reactivation of software product licenses

• US 7,379,918 B2
• Filed: 07/30/2004
• Issued: 05/27/2008
• Est. Priority Date: 07/30/2004
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Hatlelid, Kristjan, Liu, Yue, Pandya, Ravindra Nath, Hughes, Aidan T., Gunyakti, Caglar, Tan, Xiaoxi
• Primary Examiner(s): ELISCA, PIERRE E
• Application Number:
  US10/903,942
• Publication Number:
  US 20060026604A1
• Time in Patent Office: 1,397 Days
• Field of Search: 726/28, 705/59, 705/64, 705/67
• 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]
• CPC Class Codes: G06Q 20/3674 involving authentication
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction

Abstract

A method for reactivation of software products includes activating a first software product associated with a reactivation policy group. A hardware identifier derived from the computer hardware configuration is bound with the first software product activation. A second software product is activated having an associated reactivation binding list. Reactivation is requested for the first software product and an updated hardware identifier is associated with a reactivation policy group of the first software product. The second software product may be spared the request for reactivation if the second product can be associated with the reactivation of the first software product given the binding list is compatible with the reactivation policy group.

Claims

1. A method for reactivation of software products, the method comprising:

requesting activation of a first software product, wherein the first software product hosts a reactivation policy group;

associating a first hardware identifier with the first software product;

requesting activation of a second software product, wherein the second software product has a binding list;

associating the second software product with the first hardware identifier if the binding list of the second software product indicates a compatibility with the first software product, wherein associating the second software product with the first hardware identifier comprises a binding list indicating compatibility with at least one of the reactivation policy group and the first software product;

requesting a reactivation event of the first software product;

ascribing the reactivation event of the first software product to the second software product, thereby avoiding a request for reactivation event of the second software product;

wherein compatibility with the reactivation policy group is indicated by comparison of a current hardware identifier with the first hardware identifier against a hardware change tolerance associated with the reactivation policy group.

2. The method of claim 1, wherein requesting activation of a first software product further comprises requesting activation of a first software product on a computer, the computer having the first hardware identifier stored in memory.

3. The method of claim 2, wherein the hardware identifier comprises a representation of a hardware configuration at a time of activation of the first software product.

4. The method of claim 3, wherein the representation comprises a hash value of component identifiers installed on the computer.

5. The method of claim 1, wherein a reactivation policy group identifier is stored in memory in association with the first hardware identifier.

6. A method for reactivation of software products, the method comprising:

requesting activation of a first software product, wherein the first software product hosts a reactivation policy group;

associating a first hardware identifier with the first software product;

requesting activation of a second software product, wherein the second software product has a binding list;

associating the second software product with the first hardware identifier if the binding list of the second software product indicates a compatibility with the first software product;

requesting a reactivation event of the first software product;

ascribing the reactivation event of the first software product to the second software product, thereby avoiding a request for reactivation event of the second software product;

wherein requesting activation of the first software product further comprises hosting the reactivation policy group comprising a hardware change tolerance which triggers a reactivation event if the hardware change tolerance is exceeded and the first software product is accessed.

7. The method of claim 6, further comprising associating a second hardware identifier with the reactivation policy group after reactivation the first software product.

8. The method of claim 6, wherein the second hardware identifier represents a hardware configuration at the time of the reactivation of the first software product.

9. A method for reactivation of software products, the method comprising:

requesting activation of a first software product, wherein the first software product hosts a reactivation policy group;

associating a first hardware identifier with the first software product;

requesting activation of a second software product, wherein the second software product has a binding list;

associating the second software product with the first hardware identifier if the binding list of the second software product indicates a compatibility with the first software product;

accessing the first software application;

comparing a current hardware identifier against the first hardware identifier to produce a hardware difference indication;

requesting a reactivation data transaction if the hardware difference indication is greater than a hardware change tolerance associated with the reactivation policy group; and

ascribing the reactivation event of the first software product to the second software product, thereby avoiding a request for reactivation event of the second software product.

10. A method to reactivate multiple software applications, the method comprising:

requesting an activation of a first application and associating a first hardware identifier with a reactivation policy group, the first application owning the reactivation policy group;

requesting an activation of at least one additional application and associating the at least one additional application with the first hardware identifier if the at least one additional application is compatible with the reactivation policy group, wherein associating the at least one additional application with the first hardware identifier further comprises using a reactivation binding list to associate the at least one additional application with the first application if a current hardware configuration identifier is within a tolerance of the first hardware identifier wherein the tolerance is associated with the reactivation policy group;

requesting a reactivation of any one of the applications; and

determining that the reactivation of remaining applications is unnecessary if the remaining applications are associated with the reactivation policy group.

11. The method of claim 10, further comprising:

associating a second hardware identifier with the reactivation policy group after reactivation of any one of the applications.

12. A system comprising:

a processor having access to memory, the memory having instructions which, when executed, perform the method comprising;

comparing a current hardware identifier against a first hardware identifier when a first software application is accessed, the first hardware identifier associated with a reactivation policy group upon activation of the first software application;

requesting a reactivation of the first application if the current hardware identifier exceeds a threshold of difference from the first hardware identifier;

associating the current hardware identifier with the reactivation policy group;

determining that the reactivation of at least one other software application is unnecessary if the at least one other software application is bound with the reactivation policy group via a bonding list of the at least one other software application, the bonding list associating the at least one other software application with a first software application if a comparison of a current hardware identifier with the first hardware identifier is within a hardware change tolerance associated with the reactivation policy group.

13. The system of claim 12, wherein the first hardware identifier is stored in a trusted store.

14. The system of claim 12, wherein the first hardware identifier comprises a hash value.

15. The system of claim 12, wherein the binding list of the at least one other software application lists a first software application identifier.

16. A computer-readable medium having computer-executable instructions for performing a method, the method comprising:

requesting activation of a first software product, wherein the first software product hosts a reactivation policy group comprising a hardware change tolerance which triggers a reactivation event if the hardware change tolerance is exceeded and the first software product is accessed;

associating a first hardware identifier with the first software product;

requesting activation of a second software product, wherein the second software product has a binding list;

associating the second software product with the first hardware identifier if the binding list of the second software product indicates a compatibility with the first software product;

requesting a reactivation event of the first software product;

ascribing the reactivation event of the first software product to the second software product, thereby avoiding a request for reactivation event of the second software product.

17. The computer-readable medium of claim 16, wherein the step of associating the second software product with the first hardware identifier comprises a binding list indicating compatibility with at least one of the reactivation policy group and the first software product.

18. The computer-readable medium of claim 16, further comprising the step of associating a second hardware identifier with the reactivation policy group after reactivation the first software product.

19. The computer-readable medium of claim 18, wherein the second hardware identifier represents a hardware configuration at the time of the reactivation of the first software product.

20. A computer-readable medium having computer-executable instructions for performing a method, the method comprising:

requesting activation of a first software product, wherein the first software product hosts a reactivation policy group;

associating a first hardware identifier with the first software product;

requesting activation of a second software product, wherein the second software product has a binding list;

associating the second software product with the first hardware identifier if the binding list of the second software product indicates a compatibility with the first software product;

accessing the first software application;

comparing a current hardware identifier against the first hardware identifier to produce a hardware difference indication;

requesting a reactivation data transaction if the hardware difference indication is greater than a hardware change tolerance associated with the reactivation policy group; and

ascribing the reactivation event of the first software product to the second software product, thereby avoiding a request for reactivation event of the second software product.

21. A computer-readable medium having computer-executable instructions for performing a method, the method comprising:

requesting an activation of a first application and associating a first hardware identifier with a reactivation policy group, the first application owning the reactivation policy group;

requesting an activation of at least one additional application and associating the at least one additional application with the first hardware identifier if the at least one additional application is compatible with the reactivation policy group, and using a reactivation binding list to associate the at least one additional application with the first application if a current hardware configuration identifier is within a tolerance of the first hardware identifier wherein the tolerance is associated with the reactivation policy group;

requesting a reactivation of any one of the applications; and

determining that the reactivation of remaining applications is unnecessary if the remaining applications are associated with the reactivation policy group.

22. The computer-readable medium of claim 21, further comprising the step of:

associating a second hardware identifier with the reactivation policy group after reactivation of any one of the applications.