Method and apparatus for license distribution

• US 20040172367A1
• Filed: 02/27/2003
• Published: 09/02/2004
• Est. Priority Date: 02/27/2003
• Status: Active Grant

• Current Assignee: Avaya Incorporated
• Original Assignee: Avaya Technology LLC (Avaya Incorporated)
• Inventors: Chavez, David L.
• Granted Patent: US 7,260,557 B2
• Time in Patent Office: Days
• US Class Current: 705/59
• CPC Class Codes: G06F 21/105 Arrangements for software license management or administration, e.g. for managing licenses at corporate level
• CPC Class Codes: G06Q 10/087 Inventory or stock management, e.g. order filling, procurement or balancing against orders

Abstract

A method and apparatus for license distribution are disclosed. An endpoint requests information from a server related to information required for the server to grant a license. The server provides the required information to the endpoint. The endpoint obtains the required information, and forwards the information to the server. The server, upon receiving the information, determines if a license may be granted to the endpoint, and transmits a license authorization to the endpoint, which includes the number of licenses which are granted.

Claims

1. A method for transferring a software license in an enterprise network, comprising:

allocating a first number of licenses to a first site;

allocating a second number of licenses to a second site, the second site being geographically dislocated from the first site;

receiving a license reallocation request;

determining, independently of input from a user, at least one of a third number of licenses for said first site and a fourth number of licenses for said second site based on a total number of available licenses, said third number of licenses being different from said first number of licenses;

communicating a first response to the first site, the first response including said third number of licenses, and communicating a second response to the second site, the second response including said fourth number of licenses; and

thereafter operating the first and second sites subject to the first site being entitled to the third number of licenses and the second site being entitled to the fourth number of licenses.

2. The method for transferring a software license in an enterprise network, as claimed in claim 1, further comprising:

updating a record indicating the third and fourth number of licenses allocated to said first and second sites respectively.

3. The method for transferring a software license in an enterprise network, as claimed in claim 1, wherein said determining step comprises:

calculating a difference between said first number and a requested number of licenses in said reallocation request;

determining an additional number of licenses required for said first site based on said calculating step;

determining said third number as the sum of said first number and said additional number of licenses; and

determining said fourth number by subtracting said additional number of licenses from said second number.

4. The method for transferring a software license in an enterprise network, as claimed in claim 1, wherein said determining step comprises:

accessing a database containing license allocation records to determine said first number and said second number;

calculating a difference between said first number and a requested number of licenses in said reallocation request;

determining an additional number of licenses required for said first site based on said calculating step;

determining said third number as the sum of said first number and said additional number of licenses; and

determining said fourth number by subtracting said additional number of licenses from said second number.

5. The method for transferring a software license in an enterprise network, as claimed in claim 4, wherein said accessing step comprises:

establishing communication with a server; and

accessing the database on the server which contains said license allocation records.

6. The method for transferring a software license in an enterprise network, as claimed in claim 1, wherein said license reallocation request includes a request for additional licenses.

7. The method for transferring a software license in an enterprise network, as claimed in claim 1, wherein said first response includes a plurality of fields, including a version number field, a customer name field, a number of licenses granted field, a use allowed field, and a qualifying field.

8. The method for transferring a software license in an enterprise network, as claimed in claim 1, wherein said license reallocation request includes a plurality of fields including a version number field, a customer name field, a number of licenses requested field, and an authorization field.

9. The method for transferring a software license in an enterprise network, as claimed in claim 1, wherein said receiving and communicating steps are performed using hypertext transfer protocol.

10. The method for transferring a software license in an enterprise network, as claimed in claim 1, wherein said receiving and communicating steps are performed using hyper text transfer protocol over secure socket layer (HTTPS).

11. The method for transferring a software license in an enterprise network, as claimed in claim 2, wherein said updating a record step includes:

accessing a database containing license records; and

updating said records to indicate the third and fourth number of licenses allocated to said first and second sites respectively.

12. The method for transferring a software license in an enterprise network, as claimed in claim 11, wherein said accessing a database step comprises:

establishing communication with a server; and

accessing the database on the server which contains said license allocation records.

13. A method for copying digital content by a digital content receiver, comprising:

displaying digital content;

receiving from a user a request to copy the digital content;

accessing a server which is geographically dislocated from the digital content receiver;

receiving, from said server, a request for license information related to requirements for granting license to copy digital content;

determining said requested license information;

communicating said requested license information to said server;

receiving, from said server, a copy license, including a number of copies which are authorized to be made; and

generating a copy of the digital content when said number of copies is greater than zero.

14. The method for copying digital content by a digital content receiver, as claimed in claim 13, wherein there are no limitations on the viewing of the digital content.

15. The method for copying digital content by a digital content receiver, as claimed in claim 13, wherein said requested license information includes a plurality of fields, including a content name field, a customer name field, a number of copies requested field, and a payment field.

16. The method for copying digital content by a digital content receiver, as claimed in claim 15, wherein said payment field includes a requirement for credit card information.

17. The method for copying digital content by a digital content receiver, as claimed in claim 13, wherein said copy license includes a plurality of fields including a content name field, a customer name field, a number of licenses granted field, a use allowed field, and a qualifying field.

18. The method for copying digital content by a digital content receiver, as claimed in claim 17, wherein said qualifying field includes authentication information.

19. The method for copying digital content by a digital content receiver, as claimed in claim 17, wherein said qualifying field includes a decryption key.

20. The method for copying digital content by a digital content receiver, as claimed in claim 13, wherein said accessing and communicating steps are performed using hyper text transfer protocol (HTTP).

21. The method for copying digital content by a digital content receiver, as claimed in claim 13, wherein said accessing and communicating steps are performed using hyper text transfer protocol over secure socket layer (HTTPS).

22. The method for copying digital content by a digital content receiver, as claimed in claim 13, wherein said generating a copy step includes:

verifying that said number of copies is greater than zero;

verifying that a valid qualifying field is present in said copy license;

generating a copy of the digital content when said number of copies is greater than zero and said valid qualifying field is present; and

decrementing said number of copies.

23. A method for granting a license to copy digital content, comprising:

receiving, from a digital content receiver, a request for license information fields;

communicating said license information fields to said digital content receiver over a network connection;

receiving license information from said digital content receiver over the network connection;

determining the availability of a copy license based on said license information; and

communicating a license, including a number of copies which the digital content receiver is authorized to make, to said digital content receiver over the network connection.

24. The method for granting a license to copy digital content, as claimed in claim 23, wherein said determining step comprises:

verifying copy license availability for a content title requested to be copied;

verifying a proper payment; and

determining said number of copies based on said payment and said copy license availability.

25. The method for granting a license to copy digital content, as claimed in claim 23, wherein said determining step comprises:

accessing a database containing copy license permissions to determine if copy licenses are available for said digital content;

verifying a proper payment; and

determining said number of copies based on said payment and said copy license availability.

26. The method for granting a license to copy digital content, as claimed in claim 25, wherein said accessing step comprises:

establishing communication with a server; and

accessing a database on the server which contains said copy license availability.

27. The method for granting a license to copy digital content, as claimed in claim 23, wherein said license information includes a request to copy digital content.

28. The method for granting a license to copy digital content, as claimed in claim 23, wherein said license information fields include a plurality of fields, including a content name field, a customer name field, a number of licenses requested field, and a payment field.

29. The method for granting a license to copy digital content, as claimed in claim 23, wherein said copy license includes a plurality of fields including a content name field, a customer name field, a number of licenses granted field, a use allowed field, and a qualifying field.

30. The method for granting a license to copy digital content, as claimed in claim 29, wherein said qualifying field includes authentication information.

31. The method for granting a license to copy digital content, as claimed in claim 29, wherein said qualifying field includes a decryption key.

32. The method for granting a license to copy digital content, as claimed in claim 23, wherein said receiving and communicating steps are performed using hyper text transfer protocol (HTTP).

33. The method for granting a license to copy digital content, as claimed in claim 23, wherein said receiving and communicating steps are performed using hyper text transfer protocol over secure socket layer (HTTPS).

34. An apparatus for transferring a software license in an enterprise network, comprising:

a server operable to reallocate licenses upon receiving a license reallocation request from a first endpoint;

a database in communication with said server, operable to store license data and total number of available licenses for an enterprise;

wherein upon receiving said license reallocation request, said server is operable to access said database and determine, independently of input from a user, at least one of a first number of licenses for the first endpoint and a second number of licenses for a second endpoint based on said total number of available licenses, the first and second endpoints being geographically dislocated, and said server is operable to communicate a first response to the first endpoint, the first response including said first number of licenses, and communicate a second response to the second endpoint, the second response including said second number of licenses, and wherein the first and second endpoints operate subject to the first endpoint being entitled to the first number of licenses and the second site being entitled to the second number of licenses.

35. The apparatus for transferring a software license in an enterprise network, as claimed in claim 34, wherein said server updates a record in said database indicating the first and second number of licenses allocated to said first and second endpoints respectively.

36. The apparatus for transferring a software license in an enterprise network, as claimed in claim 34, wherein when making said determination, said server is operable to:

calculate a difference between a previous number of licenses allocated to said first endpoint, and a requested number of licenses in said reallocation request;

determine an additional number of licenses required for said first endpoint based on said calculated difference; and

determine said first number as the sum of said previous number of licenses and said additional number of licenses.

37. The apparatus for transferring a software license in an enterprise network, as claimed in claim 34, wherein when making said determination, said server is operable to:

access said database to determine a previous number of licenses allocated to said first endpoint;

calculate a difference between said previous number of licenses and a requested number of licenses in said reallocation request;

determine an additional number of licenses required for said first site based on said calculated difference; and

determine said first number as the sum of said previous number of licenses and said additional number of licenses.

38. The apparatus for transferring a software license in an enterprise network, as claimed in claim 34, wherein said server is operable to:

establish communication with a database server; and

access the database on the database server which contains said license allocation records.

39. The apparatus for transferring a software license in an enterprise network, as claimed in claim 34, wherein said license reallocation request includes a request for additional licenses.

40. The apparatus for transferring a software license in an enterprise network, as claimed in claim 34, wherein said license reallocation request includes a plurality of fields including a version number field, a customer name field, a number of licenses requested field, and an authorization field.

41. The apparatus for transferring a software license in an enterprise network, as claimed in claim 34, wherein said server is operable to communicate with said database and the endpoints using hypertext transfer protocol.

42. The apparatus for transferring a software license in an enterprise network, as claimed in claim 34, wherein said server is operable to communicate with said database and the endpoints using hyper text transfer protocol over secure socket layer (HTTPS).

43. An apparatus for transferring a software license in an enterprise network, comprising:

a first endpoint and a second endpoint, each of said endpoints operably interconnected to said enterprise network; and

a server operably interconnected to said enterprise network, which is geographically dislocated from said first and second endpoints,

wherein said first endpoint is operable to receive a request to reallocate a number of licenses associated with the first endpoint, and upon receiving said request communicates a license reallocation request to said server, and receives a revised number of licenses from said server in response to said license reallocation request, and thereafter operates according to the revised number of licenses.

44. An apparatus for transferring a software license in an enterprise network, as claimed in claim 43, wherein said license reallocation request includes a plurality of fields, including a version number field, a customer name field, a number of licences requested field, and an authorization field.

45. An apparatus for transferring a software license in an enterprise network, as claimed in claim 43, wherein said endpoints communicate over the enterprise network using hyper text transfer protocol (HTTP).

46. An apparatus for transferring a software license in an enterprise network, as claimed in claim 43, wherein said endpoints communicate over the enterprise network using hyper text transfer protocol over secure socket layer (HTTPS).

47. An apparatus for transferring a software license in an enterprise network, comprising:

a first endpoint and a second endpoint, each of said endpoints operably interconnected to said enterprise network; and

a server operably interconnected to said enterprise network, which is geographically dislocated from said first and second endpoints,

wherein said first endpoint is operable to receive a request to reallocate a number of licenses associated with the first endpoint, and upon receiving said request communicates a license reallocation information request to said server, and receives license reallocation information from said server in response to said license reallocation information request, and thereafter communicates a license reallocation request to said server, the server upon receiving said license reallocation request determines a revised number of licenses available to said first endpoint and second endpoint, communicates the revised license information including a revised number of licenses to each of said first and second endpoints, and the endpoints thereafter operate according to the revised number of licenses.

48. An apparatus for transferring a software license in an enterprise network, as claimed in claim 47, further comprising:

a database operably interconnected to said server, said database operable for storage and retrieval of license information related to each of said first and second endpoints.

49. An apparatus for transferring a software license in an enterprise network, as claimed in claim 48, wherein said server is operable to update a record located in said database to indicate the revised number of licenses allocated to said first and second sites respectively.

50. An apparatus for transferring a software license in an enterprise network, as claimed in claim 47, wherein upon receiving said license reallocation request, said server is operable to:

calculate a difference between an original number of licenses for said first endpoint and a requested number of licenses in said reallocation request;

determine an additional number of licenses required for said first endpoint based on said calculated difference;

determine said revised number of licenses for said first endpoint as the sum of said original number and said additional number of licenses; and

determine said revised number of licenses for said second endpoint by subtracting said additional number of licenses from the original number of licenses allocated to said second endpoint.

51. An apparatus for transferring a software license in an enterprise network, as claimed in claim 48, wherein, upon receiving said license reallocation request, said server is operable to:

access said database are receive license allocation records related to said first and said second endpoints, said license allocation records including a first number of licenses for said first endpoint and a second number of licenses for said second endpoint;

calculate a difference between said first number and a requested number of licenses in said reallocation request;

determine an additional number of licenses required for said first endpoint based on said calculated difference;

determine a third number as the sum of said first number and said additional number of licenses; and

determine a fourth number of licenses by subtracting said additional number of licenses from said second number.

52. An apparatus for transferring a software license in an enterprise network, as claimed in claim 51, wherein, when accessing said database, said server is operable to:

establish communication with a server; and

access the database on the server which contains said license allocation records.

53. An apparatus for transferring a software license in an enterprise network, as claimed in claim 47, wherein said license reallocation request includes a request for additional licenses.

54. An apparatus for transferring a software license in an enterprise network, as claimed in claim 47, wherein said license reallocation information includes a plurality of fields, including a version number field, a customer name field, a number of licenses granted field, a use allowed field, and a qualifying field.

55. An apparatus for transferring a software license in an enterprise network, as claimed in claim 47, wherein said license reallocation request includes a plurality of fields including a version number field, a customer name field, a number of licenses requested field, and an authorization field.

56. An apparatus for transferring a software license in an enterprise network, as claimed in claim 47, wherein said server is operable to communicate to said endpoints using hypertext transfer protocol.

57. An apparatus for transferring a software license in an enterprise network, as claimed in claim 47, wherein said server is operable to communicate to said endpoints using hypertext transfer protocol over secure socket layer (HTTPS).

58. A computer readable medium containing instructions for directing a computer to perform a method for granting a license to copy digital content to a digital content receiver which is geographically dislocated from said computer, comprising:

receiving, from the digital content receiver, a request for license information fields;

communicating said license information fields to the digital content receiver;

receiving license information from the digital content receiver;

determining the availability of a copy license based on said license information; and

communicating a license, including a number of copies which the digital content receiver is authorized to make, to the digital content receiver.

59. The computer readable medium of claim 58, wherein said determining step comprises:

verifying copy license availability for a content title requested to be copied;

verifying a proper payment; and

determining said number of copies based on said payment and said copy license availability.

60. The computer readable medium of claim 58, wherein said determining step comprises:

accessing a database containing copy license permissions to determine if copy licenses are available for said digital content;

verifying a proper payment; and

determining said number of copies based on said payment and said copy license availability.

61. The computer readable medium of claim 60, wherein said accessing step comprises:

establishing communication with a server; and

accessing a database on the server which contains said copy license availability.

62. The computer readable medium of claim 58, wherein said license information includes a request to copy digital content.

63. The computer readable medium of claim 58, wherein said license information fields include a plurality of fields, including a content name field, a customer name field, a number of licenses requested field, and a payment field.

64. The computer readable medium of claim 58, wherein said copy license includes a plurality of fields including a content name field, a customer name field, a number of licenses granted field, a use allowed field, and a qualifying field.

65. The computer readable medium of claim 58, wherein said qualifying field includes authentication information.

66. The computer readable medium of claim 58, wherein said qualifying field includes a decryption key.

67. The computer readable medium of claim 58, wherein said receiving and communicating steps are performed using hyper text transfer protocol (HTTP).

68. The computer readable medium of claim 58, wherein said receiving and communicating steps are performed using hyper text transfer protocol over secure socket layer (HTTPS).

69. A computer readable medium containing instructions for directing a digital content receiver to perform a method copying digital content, comprising:

displaying digital content;

receiving from a user a request to copy the digital content;

accessing a server which is geographically dislocated from the digital content receiver;

receiving, from said server, a request for license information related to requirements for granting license to copy digital content;

determining said requested license information;

communicating said requested license information to said server;

receiving, from said server, a copy license, including a number of copies which are authorized to be made; and

generating a copy of the digital content when said number of copies is greater than zero.

70. The computer readable medium of claim 69, wherein said requested license information includes a plurality of fields, including a content name field, a customer name field, a number of copies requested field, and a payment field.

71. The computer readable medium of claim 70, wherein said payment field includes a requirement for credit card information.

72. The computer readable medium of claim 69, wherein said copy license includes a plurality of fields including a content name field, a customer name field, a number of licenses granted field, a use allowed field, and a qualifying field.

73. The computer readable medium of claim 72, wherein said qualifying field includes authentication information.

74. The computer readable medium of claim 72, wherein said qualifying field includes a decryption key.

75. The computer readable medium of claim 69, wherein said accessing and communicating steps are performed using hyper text transfer protocol (HTTP).

76. The computer readable medium of claim 69, wherein said accessing and communicating steps are performed using hyper text transfer protocol over secure socket layer (HTTPS).

77. The computer readable medium of claim 69, wherein said generating a copy step includes:

verifying that said number of copies is greater than zero;

verifying that a valid qualifying field is present in said copy license;

generating a copy of the digital content when said number of copies is greater than zero and said valid qualifying field is present; and

decrementing said number of copies.