License management system and method with license balancing

• US 7,716,348 B1
• Filed: 08/25/2000
• Issued: 05/11/2010
• Est. Priority Date: 09/03/1999
• Status: Active Grant

• Current Assignee: Thales DIS CPL USA, Inc. (Thales SA)
• Original Assignee: SafeNet Incorporated (Thales SA)
• Inventors: Chopra, Sanjay, Handa, Sandeep, Tripathy, Ajay, Duvvoori, Vikram, Ramamoorthy, Shankar, Redding, Mark E., Sharma, Hemant, Badia, Logan A.
• Primary Examiner(s): Blair; Douglas B
• Application Number:
  US09/648,720
• Time in Patent Office: 3,546 Days
• Field of Search: 709/203, 709217-219, 709/223, 709/226, 709/229, 707/10, 707/104.1, 707/103.X, 705/59
• US Class Current: 709/229
• 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 2221/2147 Locking files
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

A system for balancing a distribution of allocations for protected software over a communication network is disclosed. The system is comprised of at least one client computer and a pool of license servers coupled to the communication network. The client computers request authorizations to use the protected software, while a distribution of allocations is managed among the pool of servers for tracking and managing available allocations for using the protected software. One license server in the pool is designated as the current leader server. When a particular license server does not have a selectable minimum amount of available allocations, the current leader server re-assigns, where possible, the allocations within the pool by updating memory containing the distribution tables of license servers in the pool, to give at least one additional allocation to the particular license server.

Claims

1. A system for balancing a distribution of allocations for protected software over a communication network according to a license policy, the system comprising:

at least one client computer coupled to the communication network for requesting authorizations to use the protected software; and

a pool of license servers coupled to the communication network, each license server in the pool is programmed for managing a distribution of allocations for at least one client computer coupled to the communication network to use the protected software;

the pool of license servers including a current leader server programmed for updating the distribution of allocations to add at least one additional allocation to a particular license server if that particular license server has an insufficient number of allocations, wherein each license server in the pool can directly communicate with the at least one client computer coupled to the communication network, and wherein each license server in the pool manages the distribution of allocations substantially in the same manner as the other license servers in the pool;

each license server further including a borrowing threshold and programmed for determining whether the particular license server did not have a sufficient number of allocations by dividing an allocations-in-use value for that particular license server by a total allocation value for that particular license server and determining if a quotient of the division is greater than the borrowing threshold.

2. A system as recited in claim 1, the current leader server further programmed for updating the distribution of allocations to add at least one additional allocation to a particular license server if that particular license server did not have a sufficient number of allocations at any time during processing of a request for authorization from a client computer.

3. A system as recited in claim 1, the current leader server further including memory for storing the distribution of allocations for all license servers in the pool.

4. A system as recited in claim 3, the current leader server further programmed for storing a new distribution of allocations in response to a change distribution criteria message containing the new distribution of allocations communicated to a license server.

5. A system as recited in claim 4:

the license servers that are not the current leader server further programmed for communicating the change distribution criteria message to the current leader server if the license servers that are not the current leader server should receive a change distribution criteria message; and

the current leader server further programmed for communicating the new distribution of allocations in the pool to all functioning license servers in the pool that are not the leader server through a distribution criteria sync message.

6. A system as recited in claim 3, the current leader server further programmed for adding allocations to the pool in response to an add allocations message containing a count of allocations to be added to particular protected software communicated to a license server.

7. A system as recited in claim 6:

the license servers that are not the current leader server further programmed for communicating the add allocations messages to the current leader server if the license servers that are not the current leaders server should receive an add allocations message; and

the current leader server further programmed for communicating an updated distribution of allocations in the pool to all functioning license servers in the pool that are not the leader server through a distribution criteria sync message.

8. A system as recited in claim 3, the current leader server further programmed for adding a new license code to the pool in response to an add license code message containing a license code to be communicated to a license server.

9. A system as recited in claim 8:

the license servers that are not the current leader server-further programmed for communicating the add license code message to the current leader server if the license servers that are not the current leader server should receive an add license code message; and

the current leader server further programmed for communicating an updated distribution table containing the stored license codes and corresponding distribution of allocations in the pool to all functioning license servers in the pool that are not the leader server through a distribution criteria sync message.

10. A system as recited in claim 3, the current leader server further programmed for updating the distribution of allocations to add at least one additional allocation to a particular license server if that particular license server did not have a sufficient number of allocations at any time during the processing of an update message received from at least one client computer operating in fail-over mode.

11. A system as recited in claim 10, wherein if the particular license server determines that it does not have a sufficient number of allocations at any time during the processing of an update message received from at least one client computer operating in fail-over mode, the current leader server is further programmed for:

looking for a source of available allocations by checking a count of available allocations in the leader server, a free pool, and any down license servers; and

decreasing the count of available allocations from the source of available allocations and increasing the count of available allocations for the particular license server if the source of available allocations is found.

12. A system as recited in claim 11, wherein if no source of available allocations is found by checking the count of available allocations in the leader server, the free pool, and any down license servers, the current leader server is further programmed for:

looking for a source of available allocations by checking a count of available allocations in all functioning license servers not designated as the leader server; and

decreasing the count of available allocations from the source of available allocations and increasing the count of available allocations for the particular license server if the source of available allocations is found.

13. A system as recited in claim 1, wherein if the particular license server determines that it does not have a sufficient number of allocations at any time during the processing of a request for authorization received from the client computer, the current leader server is further programmed for:

looking for a source of available allocations by checking a count of available allocations in a free pool, any down license servers, and the leader server; and

decreasing the count of available allocations from the source of available allocations and increasing the count of available allocations for the particular license server if the source of available allocations is found.

14. A system as recited in claim 13, the current leader server further programmed for communicating the updated distribution of allocations in the pool to all functioning license servers in the pool that are not the current leader server through a distribution criteria sync message.

15. A system as recited in claim 1, wherein each license server that is programmed for managing a distribution of allocation comprises a license server programmed to receive a request for authorization to use the protected software from at least one client computer and to allocate authorization for each client computer from which a request is received and for which an authorization is available.

16. A system as recited in claim 1, wherein each license server is programmed to receive a request for authorization to use the protected software from at least one client computer and, if an insufficient number of allocations are available, for obtaining at least one allocation from the lead server.

17. A system as recited in claim 1, wherein:

each license server in the pool is assigned an initial distribution of zero or more available allocations for using the protected software by the at least one client computer; and

the current leader server is programmed to re-distribute one or more available allocations among the license servers in the pool.

18. A system as recited in claim 1, wherein:

each license server in the pool is associated with a data storage device for storing a record of the number of allocations presently managed by that license server;

the current leader server is programmed to request a transfer of at least one allocation from a first license server to a second license server in the pool, in the event that the second license server is managing an insufficient number of available allocations; and

each license server in the pool are programmed to update the record of the number of allocations presently managed by the license server, following a transfer of at least one allocation from a first license server to a second license server.

19. A method for balancing a distribution of allocations for using protected software by at least one client computer coupled to a communication network, the method comprising the steps of:

coupling a pool of license servers to the communication network;

assigning a distribution of allocations to the pool;

programming each license server to the pool to manage the distribution of allocations including processing requests for authorization to use the protected software from at least one client computer coupled to the communications network;

designating a current leader server from the license servers in the pool and programming the current leader for updating the distribution of allocations to add at least one additional allocation to a particular license server if that particular license server has an insufficient number of allocations in response to a request for authorization received from a client computer,

wherein each license server in the pool can communicate directly with the at least one client computer coupled to the communication network,

wherein each license server in the pool manages the distribution of allocations substantially in the same manner as the other license servers in the pool, and

wherein updating the distribution of allocations includes;

assigning a borrowing threshold to each license server; and

determining whether the particular license server did not have a sufficient number of allocations by dividing an allocations-in-use value for that particular license server by a total allocations value for that particular license server and determining if a quotient of the division is greater than the borrowing threshold.

20. A method as recited in claim 19, wherein updating the distribution of allocations includes:

selecting one of the license servers in the pool as a current leader server for storing the distribution of allocations for all license servers in the pool and for managing a re-assignment of allocations to give at least one additional allocation to a particular license server if that particular license server did not have a sufficient number of allocations at any time during processing of a request for authorization received from the client computer.

21. A method as recited in claim 20, wherein when it is determined that the particular license server did not have sufficient number of allocations during the processing of a request for authorization received from the client computer, the method further includes:

looking for a source of available authorizations by checking a count of available authorizations in a free pool, any down license servers, and the current leader server; and

decreasing the count of available allocations from the source of available allocations and increasing the count of available allocations for the particular license server if the source of available allocations is found.

22. A method as recited in claim 21, further including:

communicating the updated distribution of allocations in the pool to all functioning license servers in the pool that are not the current leader server through a distribution criteria sync message.

23. A method as recited in claim 20, further including:

updating the distribution of allocations by communicating a change distribution criteria message containing a new distribution of allocations to at least one license server.

24. A method as recited in claim 23, wherein updating the distribution of allocations by communicating a change distribution criteria message further includes:

communicating the change distribution criteria message to the current leader server;

updating the distribution of allocations in the pool in the current leader server; and

communicating the updated distribution of allocations in the pool to all other functioning license servers in the pool that are not the current leader server through a distribution criteria sync message.

25. A method as recited in claim 20, further including:

adding allocations to the pool by communicating an add allocations message containing a count of allocations to be added to particular protected software to at least one license server.

26. A method as recited in claim 25, wherein adding allocations to the pool by communicating an add allocations message further includes:

communicating the add allocations message to the current leader server;

updating the distribution of allocations in the pool in the current leader server; and

communicating the updated distribution of allocations in the pool to all other functioning license servers in the pool that are not the current leader server through a distribution criteria sync message.

27. A method as recited in claim 20, further including:

adding a new license code for protected software to the pool by communicating an add license code message containing a license code to be added to at least one license server.

28. A method as recited in claim 27, wherein adding a license code for protected software to the pool by communicating an add license code message further includes:

communicating the add license code message to the current leader server;

updating a distribution table containing the stored license codes and corresponding distribution of allocations in the pool in the current leader server; and

communicating the updated distribution table to all other functioning license servers in the pool that are not the current leader server through a distribution criteria sync message.

29. A method as recited in claim 20, further including:

updating the distribution of allocations to add at least one additional allocation to a particular license server if that particular license server did not have a sufficient number of allocations during the processing of an update message received from at least one client computer operating in fail-over mode.

30. A method as recited in claim 29, wherein when it is determined that the particular license server did not have a sufficient number of allocations during the processing of an update message received from at least one client computer operating in fail-over mode, the method further includes:

looking for a source of available allocations by checking a count of available allocations in the current leader server, a free pool, and any down license servers; and

decreasing the count of available allocations from the source of available allocations and increasing the count of available allocations for the particular license server if the source of available allocations is found.

31. A method as recited in claim 30, wherein if no source of available allocations is found by checking the count of available allocations in the current leader server, the free pool, and any down license servers, the method further includes:

looking for a source of available allocations by checking a count of available allocations in all functioning license servers not designated as the current leader server; and

decreasing the count of available allocations from the source of available allocations and increasing the count of available allocations for the particular license server if the source of available allocations is found.