License document interchange format for license management system

• US 5,438,508 A
• Filed: 09/12/1994
• Issued: 08/01/1995
• Est. Priority Date: 06/28/1991
• Status: Expired due to Term

• Current Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Original Assignee: Digital Equipment Corporation (HP Inc.)
• Inventors: Wyman, Robert M.
• Primary Examiner(s): McElheny, Jr., Donald E.
• Application Number:
  US08/304,632
• Time in Patent Office: 323 Days
• Field of Search: 364/401, 364/402, 364/406, 380/4, 380/25, 380/23
• US Class Current: 705/1.1
• 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 2211/007 Encryption, En-/decode, En-/decipher, En-/decypher, Scramble, (De-)compress
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]

Abstract

A distributed computer system employs a license management system to account for software product usage. A management policy having a variety of alternative styles and contexts is provided. Each licensed product upon start-up makes a call to a license server to check on whether usage is permitted, and the license server checks a database of the licenses, called product use authorizations, that it administers. If the particular use requested is permitted, a grant is returned to the requesting user node. The product use authorization is structured to define a license management policy allowing a variety of license alternatives by values called "style", "context", "duration" and "usage requirements determination method". The license administration may be delegated by the license server to a subsection of the organization, by creating another license management facility duplicating the main facility. The license server must receive a license document (a product use authorization) from an issuer of licenses, where a license document generator is provided. A mechanism is provided for one user node to make a call to use a software product located on another user node; this is referred to as a "calling card", by which a user node obtains permission to make a procedure call to use a program on another node. A management interface allows a license manager at a server to modify the license documents in the database maintained by the server, within the restraints imposed by the license, to make delegations, assignments, etc. The license documents are maintained in a standard format referred to as a license document interchange format so the management system is portable and can be used by all adhering software vendors. A feature of the database management is the use of a filter function.

Claims

1. A method operating in a computer system for managing execution of licensed software items in said computer system, comprising the steps of:

maintaining by said computer system a store of license authorizations for said software items;

each license authorization including an indication of license management policy for a software item, said indication being in the format of an encoded document of a data type consisting of an ordered sequence of three elements, the three elements including a document descriptor, a document header and the document content;

accessing by said computer system said store to retrieve information from said license authorization for said software item, in response to a request from a client, and comparing said client request, including identification of said client and said software item, with said retrieved information, to produce a grant or refusal of said request.

2. A method according to claim 1 wherein said document descriptor includes an encoding method version number, an encoder-identifier and an encoder-name.

3. A method according to claim 1 wherein said document header includes a title, an author, a version and a date for the software item.

4. A method according to claim 1 wherein said document content includes at least one of the following:

a product-use-authorization;

a license-use-requirements-table;

a group-definition;

a key-registration;

a delegation.

5. A method according to claim 1 wherein said document content includes a license-data-header, and said license-data-header describes parties to said license authorization, a term of said license authorization and any constraints that have been placed on management of said license authorization.

6. A method according to claim 1 wherein said document content includes management-info, where the management-info includes at least one of the following:

an assignment;

a reservation;

a delegation;

a backup delegation;

an allocation;

a registration date;

a registrar;

a comment;

a termination-date.

7. A method according to claim 1 wherein:

said document descriptor includes an encoding method version number, an encoder-identifier and an encoder-name;

said document header includes a title, an author, a version and a date for the software item;

said document content includes a license-body comprising at least one of the following;

a product-use-authorization, a license-use-requirements-table, a group-definition, a key-registration, and a delegation;

said document content further includes a license-data-header comprising an identification of parties to said license authorization, a term of said license authorization and constraints that have been placed on management of said license authorization; and

said document content further includes management-info comprising at least one of the following;

an assignment, a reservation, a delegation, a backup delegation, an allocation, a registration date, a registrar, and a comment.

8. A method according to claim 1 wherein said store is maintained by a license server, said request is sent to said server, and said accessing and comparing are performed by said server, and wherein said server and said client are nodes on a distributed computer network.

9. A method according to claim 1 wherein said request is in the form of a remote procedure call, and said grant or refusal sent to said client is a return of said procedure call.

10. A method according to claim 8 wherein said license authorization is received by said server from an issuer.

11. A method according to claim 1 including the steps of:

sending a request by a client to obtain permission to use one of said software item;

said request identifying a user and said software item;

sending said grant or refusal to said client.

12. Apparatus operating in a computer system for managing execution of licensed software items in said computer system, comprising:

means for maintaining a store of license authorizations for said software items;

each license authorization including an indication of license management policy for a software item, said indication being in the format of an encoded document of a data type consisting of an ordered sequence of three elements, the three elements including a document descriptor, a document header and the document content;

means for sending a request by a client to obtain permission to use one of said software items;

said request providing an identification of said client and said software item;

means for accessing said store to retrieve information from said license authorization for said software item, in response to said request, and comparing said client request, including identification of said client and said software item with said retrieved information, to produce a grant or refusal of said request;

means for sending said grant or refusal to said client.

13. Apparatus according to claim 12 wherein said document descriptor includes an encoding method version number, an encoder-identifier and an encoder-name.

14. Apparatus according to claim 12 wherein said document header includes a title, an author, a version and a date for the software item.

15. Apparatus according to claim 12 wherein said document content includes at least one of the following:

a product-use-authorization;

a license-use-requirements-table;

a group-definition;

a key-registration;

a delegation.

16. Apparatus according to claim 12 wherein said document content includes a license-data-header, and said license-data-header describes parties to said license authorization, a term of said license authorization and constraints that have been placed on management of said license authorization.

17. Apparatus according to claim 12 wherein said document content includes management-info, where the management-info includes at least one of the following:

an assignment;

a reservation;

a delegation;

a backup delegation;

an allocation;

a registration date;

a registrar;

a comment;

a termination-date.

18. Apparatus according to claim 12 wherein:

said document descriptor includes an encoding method version number, an encoder-identifier and an encoder-name;

said document header includes a title, an author, a version and a date for the software item;

said document content includes a license-body comprising at least one of the following;

a product-use-authorization, a license-use-requirements-table, a group-definition, a key-registration, and a delegation;

said document content further includes a license-data-header comprising an identification of parties to said license authorization, a term of said license authorization and constraints that have been placed on management of said license authorization; and

said document content further includes management-info comprising at least one of the following;

an assignment, a reservation, a delegation, a backup delegation, an allocation, a registration date, a registrar, and a comment.

19. Apparatus according to claim 12 wherein said store is maintained by a license server, said request is sent to said server, and said accessing and comparing are performed by said server.

20. Apparatus according to claim 12 wherein said request is in the form of a remote procedure call, and said grant or refusal sent to said client is a return of said procedure call.

21. Apparatus according to claim 12 wherein said license authorization is received by said maintaining means from an issuer.

22. Apparatus according to claim 12 wherein said server and said client are nodes on a computer network.

23. A method of storing software license documents by a server for a software license management system, comprising the steps of:

maintaining a store of license documents for software items;

each license document including an indication of license management policy for a corresponding one of said software items, said indication being in the format of an encoded document of a data type consisting of an ordered sequence of three elements, the three elements including a document descriptor, a document header and the document content;

accessing said store to retrieve information from one of said license documents corresponding to one of said software items selected in response to a request, and referencing said indication of license management policy, to produce a grant or refusal of said request.

24. A method according to claim 23 wherein said document descriptor includes an encoding method version number, an encoder-identifier and an encoder-name.

25. A method according to claim 23 wherein said document header includes a title, an author, a version and a date for the software item.

26. A method according to claim 23 wherein said document content includes at least one of the following:

a product-use-authorization;

a license-use-requirements-table;

a group-definition;

a key-registration;

a delegation.