Method for electronically documenting license information

Abstract

In a method for electronically documenting license information via the granting of a license and the use of said license in a network of several electronic data processing devices, the license information is added with a new transaction block to a decentralized transaction database and is managed using blockchain technology. When a license is granted to a licensee, a licensor generates new license information with a licensing input, the licensing input contains at least one license identification, and before, during or after use of the license granted by the licensor the licensee generates new license information with a license use input, and the license use input contains at least the license identification of the licensing input and a use identification. The licensing input can contain a license key encrypted with a public key of the licensee, with which the licensor and the licensee can generate and decrypt encrypted information.

Claims

1. A method for the electronic documentation of license information items about a granting of a license and a utilization of that license in a network of a plurality of electronic data processing devices that are connectable to one another in a data-transferring manner, wherein the license information items are managed in a decentralized transaction database (18) using blockchain technology, wherein the transaction database (18) contains a chain of transaction blocks (19, 20), and wherein new license information items are able to be added to the transaction database (18) in new transaction blocks (17) by a block generation method, wherein in the block generation method first, an output block information item generated with information items about a previous transaction block (19) of the transaction database (18) and an integrity criterion for the addition of the new transaction block (17) to the transaction database (18) is obtained from the network, wherein subsequently, a new transaction block (17) is generated, which meets the integrity criterion and which contains at least the output block information item, the new license information item and an integrity information item, and wherein finally, the new transaction block (17) is added to the transaction database (18), wherein a licensor (1), when granting a license to a licensee (5), generates a new license information item with a licensing entry (6), which is added to the transaction database (18) in a new transaction block (17) using the block generation method, wherein the licensing entry (6) contains at least one license identification (7), and wherein the licensee (5) generates a new license information item with a license usage entry (25) before, during or after use of the license of the licensor (1), which license usage entry is added to the transaction database (18) in a new transaction block (17) using the block generation method, wherein the license usage entry (25) contains at least the license identification (7) of the licensing entry (6) and a usage identification, wherein the license usage entry (25) contains a license usage information item, and wherein the license usage information item in the license usage entry (25) contains a unique usage serial number (23), and wherein the licensing entry (6) contains a license key (15) encrypted with a public key of the licensee (5), so that the licensor (1) and the licensee (5) can generate and decrypt encrypted information items using the license key (13), and wherein the license usage information item in the license usage entry (25) is encrypted using the license key (13).

2. The method according to claim 1, wherein the licensing entry (6) contains a usage restriction information item (8).

3. The method according to claim 1, wherein the usage serial number (23) is encrypted using the license key (13).

4. The method according to claim 1, wherein the licensee (5) additionally adds a further license information item (26) to the transaction database (18) for each license usage entry (25), wherein the further license information item (26) includes a license serial number entry which contains at least the licensee identification (10) and the unencrypted unique usage serial number (23).

5. The method according to claim 1, wherein each new transaction block (17) containing a licensing entry (6) or a license usage entry (25) is added to the transaction database (18) with the aid of a software module running on a data processing system, wherein the software module automatically verifies whether the licensing entry (6) is initiated by the licensor (1) or the license usage entry (25) by the licensee (5), and whether the license usage entry (25) relates to a previous licensing entry (6).

6. The method according to claim 1, wherein the license authorizes the licensee to manufacture a product or provide a service, and wherein the unique usage serial number (23) is used to mark the product or the service.

7. A method for the electronic documentation of license information items about a granting of a license and a utilization of that license in a network of a plurality of electronic data processing devices that are connectable to one another in a data-transferring manner, wherein the license information items are managed in a decentralized transaction database (18) using blockchain technology, wherein the transaction database (18) contains a chain of transaction blocks (19, 20), and wherein new license information items are able to be added to the transaction database (18) in new transaction blocks (17) by a block generation method, wherein in the block generation method first, an output block information item generated with information items about a previous transaction block (19) of the transaction database (18) and an integrity criterion for the addition of the new transaction block (17) to the transaction database (18) is obtained from the network, wherein subsequently, a new transaction block (17) is generated, which meets the integrity criterion and which contains at least the output block information item, the new license information item and an integrity information item, and wherein finally, the new transaction block (17) is added to the transaction database (18), wherein a licensor (1), when granting a license to a licensee (5), generates a new license information item with a licensing entry (6), which is added to the transaction database (18) in a new transaction block (17) using the block generation method, wherein the licensing entry (6) contains at least one license identification (7), and wherein the licensee (5) generates a new license information item with a license usage entry (25) before, during or after use of the license of the licensor (1), which license usage entry is added to the transaction database (18) in a new transaction block (17) using the block generation method, wherein the license usage entry (25) contains at least the license identification (7) of the licensing entry (6) and a usage identification, wherein the license usage entry (25) contains a license usage information item, and wherein the license usage information item in the license usage entry (25) contains a unique usage serial number (23), and wherein the license authorizes the licensee to manufacture a product, and wherein the unique usage serial number (23) is used to mark the product with a barcode or alphanumeric character string.

8. The method according to claim 7, wherein the licensing entry (6) has a data format other than the license usage entry (25).

9. The method according to claim 7, wherein the licensing entry (6) contains a license key (15) encrypted with a public key of the licensee (5), so that the licensor (1) and the licensee (5) can generate and decrypt encrypted information items using the license key (13).

10. The method according to claim 9, wherein the license usage information item in the license usage entry (25) is encrypted using the license key (13).

11. The method according to claim 9, wherein the licensing entry (6) contains a file information item (11) representing a usage data file (2).

12. The method according to claim 11, wherein the file information item (11) is encrypted using the license key (13).

13. The method according to claim 11, wherein the licensing entry (6) contains a licensor identification (9) and a licensee identification (10).

14. The method according to claim 13, wherein only the licensee (5) identified by the licensee identification (10) receives an authorization to generate a permissible license usage entry (25).

15. The method according to claim 14, wherein the authorization of the licensee (5) to generate a permissible license usage entry (25) automatedly is verified when generating a new transaction block (17) and the generation is denied if, when verifying the licensee identification (10), no authorization can be proven.

16. The method according to claim 13, wherein the license identification (7) is a hash value calculated using a hash algorithm, which has been determined on the basis of at least the licensor identification (9), the licensee identification (10) and the file information item (11).

17. A method for use in a data processing device of a utilization device connectable to the network, wherein a release authorization for an authorization request is derived from an electronic documentation of license information items, which is managed using the method described in claim 5, wherein, in an authorization query step, in the transaction database (18) those license information items are determined and read as authorization information items, which are associated with the usage data file (2) to be released via the file information item (11), or which contain a license identification (7) previously stored in the data processing device of the utilization device, and wherein, in a subsequent authorization verification step, an authorization release is determined by verifying whether the authorization request relates to a use of the usage data file that is not excluded by the usage restriction information item or has already been performed and exhausted on the basis of the license usage information items, and the usage data file is released for use with the utilization device, if the authorization release is determined.

18. The method according to claim 17, wherein a new license information item is generated with a license usage entry (25) using the utilization device before, during or after a use of the license of the licensor (1), which license usage entry is added into a new transaction block (17) using the block generation method of the transaction database (18), wherein the license usage entry (25) contains at least the license identification (7) of the licensing entry (6) and a usage identification.

19. The method according to claim 17, wherein a product is manufactured using the utilization device, wherein a unique usage serial number (23) is generated before or during the manufacture of the product, wherein the product is marked with the usage serial number (23) and wherein the licensee (5) adds a license usage entry (25) and additionally a further license information item (26) to the transaction database (18), wherein the further license information item (26) includes a license serial number entry containing at least the licensee identification (10) and the unique usage serial number (23).

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) FIG. 1 is a schematic representation of an initial situation of a licensing agreement between a licensor and a licensee, wherein the license granted by the licensor includes the manufacture of four product units which are to be manufactured by the licensee in accordance with the specifications of the licensor.

(2) FIG. 2 is a schematic representation of a licensing entry generated by the licensor.

(3) FIG. 3 is a schematic representation of a licensing entry generated differing from the licensor, in which the file information item was encrypted with a license key.

(4) FIG. 4 is a schematic representation of individual information items generated by the licensor for the licensing entry.

(5) FIG. 5 is a schematic representation of how the individual information items can be transferred from the licensor into the licensing entry.

(6) FIG. 6 is a schematic representation of a licensing entry generated by the licensor, which includes additional information items for the licensee, and its transfer into a new transaction block, which is added to a transaction database using a block generation method.

(7) FIG. 7 is a schematic representation of how the licensor and the licensee can exchange a usage data file with the information items contained in the licensing entry, which usage data file is required for the utilization of the licenses granted by the licensor.

(8) FIG. 8 is a schematic representation of how the licensee generates a license usage entry and a further license information item using the block generation method, and adds it to the decentralized transaction database.

(9) FIG. 9 is a schematic representation of how the licensee determines a first information item for the license usage entry generated by him.

(10) FIG. 10 is a schematic representation of how the licensee determines a second information item for the license usage entry generated by him.

(11) FIG. 11 is a schematic representation of a license usage entry and of a further license information item that can be generated by the licensee and stored as electronic documentation in the transaction database.

(12) FIG. 12 is a schematic representation of the publicly visible information items and of a licensing entry, of a license usage entry and of a further a further license information item that can be generated by the licensor and licensee and stored as electronic documentation in the transaction database.

(13) FIG. 13 is a schematic representation of an examination process in which a third party can determine, starting from a license serial number reproduced on a product by a verification of the decentralized transaction database, whether or that, for this license serial number, a license information item is stored in the transaction database.

DETAILED DESCRIPTION

(14) In the starting situation illustrated by way of example in FIG. 1, the licensor 1, also referred to below as “Alice”, is in possession of a usage data file 2 designated as “Part001.prn” which contains machine-readable information items with which several copies 4 of a product can be generated with the aid of a 3D printer 3. The licensee 5, referred to below as “Bob”, is the owner of the 3D printer 3. The licensor 1 and the licensee 5 conclude a license agreement which is to enable the licensee 5 to manufacture four copies 4 of the product defined by the usage data file 2 using his 3D printer 3 using the usage data file 2. Both the granting of the license by the licensor 1 and the respective utilization of the license by the licensee 5 is to be electronically documented as license information items.

(15) FIG. 2 schematically shows that a licensing entry 6 generated by the licensor 1 can be composed of a plurality of information items. The licensing entry 6 shown schematically in FIG. 2 has a license identification 7 and a usage restriction information item 8. The license identification 7 is composed of a licensor identification 9, a licensee identification 10 and a file information item 11. The file information item 11 is represented by a hash value 12 calculated using a hash algorithm, which is calculated using a suitable hash algorithm from the usage data file 2. The licensor identification 9 and the licensee identification 10 can each correspond to a public key of the licensor 1 or of the licensee 5, also referred to as a “public key”. For the respective public key, the licensor 1 and the licensee 5 each have a private key, also referred to as a “personal key” or “private key”. The public key and the private key can be used with an asymmetric encryption procedure.

(16) The license identification 7, which the licensor 1 generates in the embodiment illustrated in FIG. 2, consists of a hash value which is calculated using a hash algorithm from the licensor identification 9, the licensee identification 10 and the hash value 12 of the file information item 11. The usage restriction information item 8 is unencrypted and readably recorded in the licensing entry 6 in plain text.

(17) For reasons of security and in view of the fact that the licensor 1 and the licensee 5 may wish to treat information items about the concluded license agreement as confidential, it can be expedient for the file information item 11 to be additionally encrypted before the file information item 11 is recorded in the licensing entry 6. A corresponding embodiment is shown by way of example in FIG. 3. An encrypted file information item 11 can be generated by encrypting the hash value 12 of the usage data file 2 using a previously provided license key 13 and generating an encrypted hash value 14. The encrypted hash value 14 can be recorded as an encrypted file information item 11 in the license identification 7 and combined into a licensing entry 6 having changed content.

(18) The license key 13 is provided for use with a symmetric encryption procedure and is specified by the licensor 1. FIG. 4 shows how the licensor 1 encrypts the hash value 12 from the usage data file 2 using the license key 13 and thereby generates the encrypted hash value 14. The license key 13 must be made available to the licensee 5 so that the licensee 5 can decrypt the encrypted hash value 14. For this purpose, the licensor 1 encrypts the license key 13 using the public key of the licensee 5, which in this embodiment corresponds to his licensee identification 10, and generates a license key 15 encrypted for the licensee 5, which is also identified in FIG. 4 as an “encrypted license key (Copy Bob)”. The license key 15 encrypted for the licensee 5 must be made available to the licensee 5.

(19) FIG. 5 schematically shows a licensing entry 6 provided with further information items. Licensor 1 generates, in addition to the information items already described, a license number 16, which is recorded unencrypted in licensing entry 6 and represents one of each recognizable reference to the underlying license agreement.

(20) The licensing entry 6 is converted into a new transaction block 17 in a block generation method and added to a decentralized transaction database 18, also referred to as a “blockchain”. In this case, the new transaction block 17 is linked to exactly one previous transaction block 19 of the transaction database 18, so that the transaction database 18 is formed by a chain of transaction blocks 17, 19, 20. In addition, the licensor 1 can also store and archive the license information items generated by him in an electronic database 21 managed by the licensor 1. These aspects of the method are shown schematically in FIG. 6. In this case, the information items required for the licensing entry 6 and further information items from the licensor 1 are transmitted to a software module 27 with which the validity of the licensing entry 6 and the authorization of the licensor 1 to add this licensing entry 6 to the transaction database 18 are verified automatically. Thus, it can be verified using the software module 27, whether the information items in the licensing entry 6 match with the licensor identification 9 and the licensor 1 initiates the licensing entry 6.

(21) FIG. 7 schematically shows that no direct communication between the licensor 1 and the licensee 5 is required for the transmission of the usage data file 2, which in turn would involve a considerable effort with regard to the desired security and confidentiality. The usage data file 2 can be stored by the licensor 1 on an external storage device 22 managed or hosted by a third party. The storage device 22 can be designed and operated as a secure exchange platform. The licensee 5 only receives access to the usage data file 2 when he is properly identified and his authorization for retrieval of the usage data file 2 has been verified and confirmed. The licensee 5 can then use the usage data file 2 to manufacture the copies 4 of the licensed product in accordance with the license with the aid of his 3D printer 3.

(22) In this case, the licensee 5 generates a usage serial number 23 for each copy 4 of the product manufactured in accordance with the license and a usage serial number 24 encrypted using the license key 13. The licensee 5 then generates a first license usage entry 25 for the licensor 1 using the method and a second license usage entry 26 using a further license information item intended for third parties, as shown schematically in FIG. 8. The first license usage entry 25 contains the license number 16 generated by the licensor 1 and the encrypted usage serial number 24. Since the encrypted usage serial number 24 was encrypted using the license key 13 known only to the licensor 1 and the licensee 5, only the licensor 1 can determine the usage serial number 23 from the license usage entry 25 and assign it to the underlying license agreement via the license number. The licensee 5 can also use the public key of the licensor 1 to encrypt the usage serial number 23.

(23) The second license usage entry 26 contains the usage serial number 23 in plain text and the licensee identification 10. Third parties can identify the second license usage entry 26 in the transaction database 18 on the basis of the usage serial number 23 reproduced on the copy 4 of the product manufactured by the licensee 5 and thereby determine that a second license usage entry 26 is stored in the transaction database 18. In addition, third parties can record contact with the licensee 5 via the licensee identification 10 and obtain additional information items on the copy 4 of the product manufactured in accordance with the license.

(24) The first license usage entry 25 and the second license usage entry 26 are also transmitted by the licensee 5 to the software module 27 together with further information items with which it is verified via validity verifications stored there on whether the license usage entries 25, 26 relate to a previous licensing entry 6 and whether the license usage entries 25, 26 are initiated by the licensee 5. In this case, the software module 27 can also verify, for example, whether the license identification 7 originally calculated by the licensor 1 can be calculated from the available information items and matches it. The license usage entries 25, 26 are only entered into the transaction database 18 when all validity verifications performed by the software module 27 were performed without error.

(25) FIGS. 9 and 10 show schematically how the licensee 5 can generate the encrypted usage serial number 24 and the encrypted hash value 14 of the usage data file 2 from the information items provided to him by the licensor 1 and from his private key 28 designated as “personal key of Bob” with the aid of the license key 13.

(26) According to FIG. 11, the first license usage entry 25 generated by the licensee 5 contains as a license identification the license number 16 specified by the licensor 1 and the encrypted usage serial number 24, which were determined by the licensee 5 from the information items known to him. Only a single copy 4 is assigned to the first license usage entry 25, so that this corresponds to a license usage information item of “1” and the licensor 1 is informed that a copy 4 has been manufactured. Several copies 4 could also each be gathered in the first and second license usage entry 25, 26, in which case a corresponding license usage information item is assigned.

(27) The licensor identification 9, the licensee identification 10 and the encrypted hash value 14 of the file information item 11 are each transmitted by the licensee 5 to the software module 27 and used to pass the validity verification performed automatically by the software module 27. The first license usage entry 25 of the licensee 5 includes the license number 16 as a license identification and the encrypted usage serial number 24, so that the licensor 1 can read the usage serial number 23 in plain text after a decryption performed by him using the license key 13. No third party can extract the usage serial number 23 in plain text from the first license usage entry 25, since the required license key 13 required for it is not known.

(28) The second license usage entry 26 contains no license agreement and the licensor 1, but the licensee identification 10 and the usage serial number 23 in plain text. Each third-party having access to the transaction database 18 can identify the second license usage entry 26 on the basis of the usage serial number 23.

(29) FIG. 12 schematically shows the publicly visible information items and the licensing entry 6 generated by the licensor 1 and the first license usage entry 25 generated by the licensee 5 and the second license usage entry 26.

(30) FIG. 13 schematically shows only that any third party can procure information items on the basis of the usage serial number 23, which is reproduced, for example, on copy 4 manufactured by licensee 5 and it is thus identifiable to the third party that a license agreement for this copy 4 exists. For this purpose, the third party must review the entire transaction database 18 with the individual transaction blocks of the transaction database 18 and identify a second license usage entry 26 in which the usage serial number 23 is stored in plain text. When such a license usage entry 26 with the searched usage serial number 23 is present, proof is provided that the usage serial number 23 belongs to a legitimate license. The licensee identification 10 is also stored in this second license usage entry 26, so that the third party can contact the licensee 5 and retrieve further information items.

LIST OF REFERENCE CHARACTERS

(31) 1. licensor 2. usage data file 3. 3D printer 4. copy of a product 5. licensee 6. licensing entry 7. license identification 8. usage restriction information item 9. licensor identification 10. licensee identification 11. file information item 12. hash value of the usage data file 13. license key 14. encrypted hash value 15. encrypted license key 16. license number 17. new transaction block 18. transaction database 19. previous transaction block 20. old transaction block 21. database of the licensor 22. external storage device 23. usage serial number 24. encrypted usage serial number 25. first license usage entry 26. second license usage entry 27. software module 28. private key of the licensor