Blockchain-based license management
Blockchain-based license management provides capabilities for managing licensable aspects of a plurality of IHSs (Information Handling Systems) participating in the blockchain comprised of individual license blocks that record licensing transactions. A licensing authority initiates the blockchain and modifies licensable aspects of a specific participating target IHS by distributing license blocks that include one or more license tokens and license logic specifying instructions for the target's evaluation of the license tokens. Each participating IHS validates the received license blocks and adds them to a local copy of the blockchain. If a participating IHS is the target, that IHS uses the license logic to determine licensing modifications indicated by the licensing token. Licensable aspects of the IHS may then be modified based on the determined licensing modifications. A participating IHSs may directly transfer licenses to another IHS through the transfer of license tokens and the corresponding license logic.
1. A method for managing licensable aspects of a first IHS (Information Handling System) of a plurality of IHSs participating in a blockchain, the method comprising:
receiving a first block of the blockchain that specifies software and hardware components of the first IHS that have been enabled for use, wherein the first block includes one or more encrypted license tokens and further includes license logic, and wherein the license tokens specify the software and hardware components of the first IHS that have been enabled for use, and wherein the license logic provides instructions for determining whether the first block is targeted at the first IHS;
authenticating the received first block;
after the received first block is authenticated, adding the received first blockto a local copy of the blockchain maintainedby the first IHS;
determining, using the license logic included in the first block, the first IHS is a target of the received first block, wherein the first IHS is determined to be the target of the first block by determining the license logic has access to a key that decrypts the license tokens of the first block;
after the first IHS is determined as the target of the received first block, determining, using the license logic included in the first block, one or more modifications to the software and hardware components of the first IHS that are enabled for use based on information specified in the license tokens included in the first block;
generating a second block of the blockchain, wherein the second block comprises a transfer license token corresponding to a transfer of a license from the first IHS to a second IHS of the participating IHSs, and wherein the second block further comprises additional license logic; and
transmitting the second block to the participating IHSs.
2. The method of claim 1 , wherein the received first block is authenticated based on validation of a digital signature included in the received block.
3. The method of claim 1 , wherein each of the license tokens comprises a token balance indicating the duration of a license specified by a respective license token.
4. The method of claim 1 , wherein the key that decrypts the license tokens of the first block comprises a private key of a keypair of the first IHS.
5. The method of claim 1 , wherein the license logic is used to process the license tokens to determine the hardware and software components of the first IHS that are enabled for use by a licensing virtual machine operating on the first IHS.
6. The method of claim 5 , wherein the license logic further comprises instructions directing the licensing virtual machine to issue periodic reports to the licensing authority regarding the hardware and software components of the IHS that are enabled for use.
7. The method of claim 1 , wherein the additional licensing logic is utilized by the second IHS to process the transfer license token to enable one or more components of the second IHS.
8. A first Information Handling System (IHS) of a plurality of IHSs participating in a blockchain, the IHS comprising:
one or more processors;
a baseboard management controller configured to operate a licensing virtual machine for managing licensable aspects of the first IHS, wherein the licensing virtual machine is configured to:
receive a first block of the blockchain, wherein the first block includes one or more encrypted license tokens and further includes license logic, and wherein the license tokens specify software and hardware components of the first IHS that have been enabled for use, and wherein the license logic provides instructions for determining whether the first block is targeted at the first IHS;
authenticate the received first block;
after the received block is authenticated, add the received first blockto a local copy of the blockchain maintainedby the first IHS;
determine, using the license logic included in the first block the first IHS is a target of the received first block, wherein the first IHS is determined to be the target of the first block by determining the license logic has access to a key that decrypts the license tokens of the first block;
after the first IHS is determined as the target of the received first block, determine, using the license logic included in the first block the one or more modifications to the software and hardware components of the first IHS that are enabled for use based on information specified in the license tokens; and
a system memory coupled to the one or more processors, the system memory including program instructions stored thereon that, upon execution by the one or more processors, cause the IHS to:
enable the one or more of the components of the first IHS that are determined by the virtual machine operating o n the baseboard management controller in evaluation of the received first block;
wherein the licensing virtual machine is further configured to:
generate a second block of the blockchain, whereinthe second block comprises a transfer license token corresponding to a transfer of a license from the first IHS to a second IHS of the participating IHSs, and wherein the second block further comprises additional license logic; and
transmit the second block to the participating IHSs.
9. The IHS of claim 8 , wherein each of the license tokens comprises a token balance indicating the duration of a license specified by a respective license token.
10. The IHS of claim 8 , wherein the key that decrypts the license tokens of the first block comprises a private key of a keypair of the first IHS.
11. The IHS of claim 8 , wherein the license logic is used to process the license tokens to determine the hardware and software components of the first IHS that are enabled for use by the licensing virtual machine operating on the first IHS.
12. The IHS of claim 11 , wherein the license logic comprises instructions directing the licensing virtual machine to issue periodic reports to the licensing authority regarding the hardware and software components of the IHS that are enabled for use.
13. The IHS of claim 8 , wherein the additional licensing logic is utilized by the second IHS to process the transfer license token to enable one or more components of the second IHS.
14. The IHS of claim 13 , wherein the licensing virtual machine is further configured to:
authenticate the received first block by validating a digital signature included in the first block.
15. A computer-readable storage device having instructions stored thereon for managing licensable aspects aspect of a first IHS (Information Handling System) of a plurality of IHSs participating in a blockchain, wherein upon execution by one or more processors, the instructions cause the one or more processors to:
receive a first block of the blockchain that specifies software and hardware components of the first IHS that have been enabled for use, wherein the first block includes one or more encrypted license tokens and further includes license logic, and wherein the license tokens specify the hardware and software components of the first IHS that have been enabled for use, and wherein the license logic provides instructions for determining whether the first block is targeted at the first IHS;
authenticating the received first block; after the received first block is authenticated, add the received first blockto a local copy o f the blockchain maintained by the first IHS;
determine, using the license logic included in the first block whether the first IHS is a target of the received first block, wherein the first IHS is determined to be the target of the first block by determining the license logic has access to a key that decrypts the license tokens of the first block; and
after the first IHS is determined as the target of the received first block, determine, using the license logic included in the first block the one or more modifications to the software and hardware components first IHS that are enabled for use based on information specified in the license tokens;
generate a second block of the blockchain, wherein the second block comprises a transfer license token corresponding to a transfer of a license from the first IHS to a second IHS of the participating IHSs, and wherein the secondblock further comprises additional license logic; and
transmit the secondblock to the participating IHSs.
16. The storage device of claim 15 , wherein the received first block is authenticated based on validation of a digital signature included in the received first block.
17. The storage device of claim 15 , wherein each of the license tokens comprises a token balance indicating the duration of a license specified by a respective license token.
18. The storage device of claim 15 , wherein the key that decrypts the license tokens of the first block comprises a private key of a keypair of the first IHS.