Targeting energy units in a blockchain

BACKGROUND OF THE INVENTION

0001The present invention relates generally to the field of power metering, and more particularly to blockchain based tracking of power production and consumption.

0002Power metering is the act of tracking power usage for a particular device or household. Power distribution systems, or grids, provide the power and include (i) generators, for producing power, (ii) substations and other power conditioning devices to transmit the power to consumers, and (iii) consumers or end point devices that use the power provided by the power distribution system. Typically, a meter or other power usage monitoring device provides a reading of the amount of power consumed.

0003A blockchain is a list of transactions or entries that are combined into blocks. A cryptographic hash value for each block is determined. Additionally, a hash value of the preceding block of transactions is also included. This recurring operation of cryptographic hashing of each block creates a data structure that cannot be retroactively altered without changing all of the subsequent blocks in the chain. As such, blockchains are often referred to as immutable or unchangeable, since without an adjustment to each subsequent block in the blockchain, any attempt to change even a single entry in the block will alter the hash values and fail verification.

SUMMARY

0004Embodiments of the present invention provide a method, system, and program product to track and target particular energy sources in an electrical grid. A processor stores information regarding units of produced energy as transactions in a blockchain. A processor receives, from an endpoint device of a plurality of endpoint devices connected to a power grid, a request for a unit of energy represented in the blockchain. A processor sends an indication, to the endpoint device, that the endpoint device is permitted to consume the unit of energy from the power grid. A processor updates the blockchain to record the consumption of the unit of energy.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

<figref idref="DRAWINGS">FIG. 1</figref> is a functional block diagram illustrating a networked environment, in accordance with an exemplary embodiment of the present invention.

<figref idref="DRAWINGS">FIG. 2</figref> is a functional block diagram illustrating a power transmission network with power and data communication paths.

<figref idref="DRAWINGS">FIG. 3</figref> illustrates operational processes of a monitoring program on a computing device within the environment of <figref idref="DRAWINGS">FIG. 1</figref>, in accordance with an exemplary embodiment of the present invention.

<figref idref="DRAWINGS">FIG. 4</figref> depicts a block diagram illustrating a blockchain comprising smart contracts.

<figref idref="DRAWINGS">FIG. 5</figref> illustrates operational processes of a metering program on a computing device within the environment of <figref idref="DRAWINGS">FIG. 1</figref>, in accordance with an exemplary embodiment of the present invention.

<figref idref="DRAWINGS">FIG. 6</figref> illustrates operational processes of a generation program on a computing device within the environment of <figref idref="DRAWINGS">FIG. 1</figref>, in accordance with an exemplary embodiment of the present invention.

<figref idref="DRAWINGS">FIG. 7</figref> depicts a block diagram of components of the computing device executing a monitoring program, a metering program or a generation program, in accordance with an exemplary embodiment of the present invention.

DETAILED DESCRIPTION

0012The present invention may be a system, a method, and/or a computer program product at any possible technical detail level of integration. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.

0013The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.

0014Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.

0015Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, configuration data for integrated circuitry, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++, or the like, and procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.

0016Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.

0017These computer readable program instructions may be provided to a processor of a computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.

0018The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

0019The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the blocks may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be accomplished as one step, executed concurrently, substantially concurrently, in a partially or wholly temporally overlapping manner, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.

0020The present invention will now be described in detail with reference to the Figures. <figref idref="DRAWINGS">FIG. 1</figref> is a functional block diagram illustrating networked environment, generally designated <b>100</b>, in accordance with one embodiment of the present invention. Networked environment <b>100</b> includes power devices <b>110</b><i>a</i>-<i>n</i>, endpoint devices <b>120</b><i>a</i>-<i>n</i>, smart power generation and targeting (SPGT) system <b>130</b>, and blockchain members <b>142</b><i>a</i>-<i>n </i>connected over network <b>160</b>. Power devices <b>110</b><i>a</i>-<i>n </i>each include generation program <b>112</b>, post module <b>114</b> and local node <b>146</b><i>a</i>. Endpoint devices <b>120</b><i>a</i>-<i>n </i>each include metering program <b>122</b>, request module <b>124</b> and local node <b>146</b><i>a</i>. SPGT <b>130</b> includes monitoring program <b>132</b>, usage module <b>133</b>, efficiency module <b>134</b>, rate module <b>135</b> and power node <b>146</b>. Blockchain members <b>142</b><i>a</i>-<i>n </i>each include blockchain program <b>144</b> and power node <b>146</b>.

0021In various embodiments of the present invention, power devices <b>110</b><i>a</i>-<i>n</i>, endpoint devices <b>120</b><i>a</i>-<i>n</i>, smart power generation and targeting (SPGT) system <b>130</b>, and blockchain members <b>142</b><i>a</i>-<i>n </i>are each a computing device that can be a standalone device, a server, a laptop computer, a tablet computer, a netbook computer, a personal computer (PC), or a desktop computer. In another embodiment, power devices <b>110</b><i>a</i>-<i>n</i>, endpoint devices <b>120</b><i>a</i>-<i>n</i>, smart power generation and targeting (SPGT) system <b>130</b>, or blockchain members <b>142</b><i>a</i>-<i>n </i>each represent a computing system utilizing clustered computers and components to act as a single pool of seamless resources. In general, power devices <b>110</b><i>a</i>-<i>n</i>, endpoint devices <b>120</b><i>a</i>-<i>n</i>, smart power generation and targeting (SPGT) system <b>130</b>, and blockchain members <b>142</b><i>a</i>-<i>n </i>each can be any computing device or a combination of devices with access to power node <b>146</b> and local node <b>146</b><i>a </i>and is capable of executing generation program <b>112</b>, metering program <b>122</b>, monitoring program <b>132</b> and blockchain program <b>144</b>. Power devices <b>110</b><i>a</i>-<i>n</i>, endpoint devices <b>120</b><i>a</i>-<i>n</i>, smart power generation and targeting (SPGT) system <b>130</b>, and blockchain members <b>142</b><i>a</i>-<i>n </i>may include internal and external hardware components, as depicted and described in further detail with respect to <figref idref="DRAWINGS">FIG. 7</figref>.

0022In this exemplary embodiment, generation program <b>112</b> is stored on power devices <b>110</b><i>a</i>-<i>n</i>, metering program <b>122</b> is stored on endpoint devices <b>120</b><i>a</i>-<i>n</i>, monitoring program <b>132</b> is stored on SPGT system <b>130</b> and blockchain program <b>144</b> is stored on blockchain members <b>142</b><i>a</i>-<i>n</i>. However, in other embodiments, generation program <b>112</b>, metering program <b>122</b>, monitoring program <b>132</b> and blockchain program <b>144</b> may be stored externally and accessed through a communication network, such as network <b>160</b>. Network <b>160</b> can be, for example, a local area network (LAN), a wide area network (WAN) such as the Internet, or a combination of the two, and may include wired, wireless, fiber optic or any other connection known in the art. In general, network <b>160</b> can be any combination of connections and protocols that will support communications between power devices <b>110</b><i>a</i>-<i>n</i>, endpoint devices <b>120</b><i>a</i>-<i>n</i>, smart power generation and targeting (SPGT) system <b>130</b>, and blockchain members <b>142</b><i>a</i>-<i>n</i>, in accordance with a desired embodiment of the present invention.

0023In various embodiments, power devices <b>110</b><i>a</i>-<i>n </i>and endpoint devices <b>120</b><i>a</i>-<i>n </i>comprise various components and devices that may produce or consume power from an electric power grid. In some embodiments, power devices <b>110</b><i>a</i>-<i>n </i>are power generating devices such as generators of varying types (e.g., solar panels, wind turbines, steam turbines, etc.). In other embodiments, power devices <b>110</b><i>a</i>-<i>n </i>are communicatively coupled to, via network <b>160</b>, various power generating devices and corresponding sensors that report various information regarding power generated by said power generating devices and corresponding sensors. Similarly, in some embodiments, endpoint devices <b>120</b><i>a</i>-<i>n </i>are power consuming devices that require power from the electric power grid to operate. In other embodiments, endpoint devices <b>120</b><i>a</i>-<i>n </i>are communicatively coupled to, via network <b>160</b>, various power consuming devices and corresponding sensors that report various information regarding power consumed by said power consuming devices and corresponding sensors. In further embodiments, a device can be both a device from endpoint devices <b>120</b><i>a</i>-<i>n </i>and a device from power devices <b>110</b><i>a</i>-<i>n</i>. For example, a household may have solar panels installed and contribute power to a power grid (i.e., as a power device from power devices <b>110</b><i>a</i>-<i>n</i>) while also consuming power when the solar panels are not active (i.e., as an endpoint device of endpoint devices <b>120</b><i>a</i>-<i>n</i>). One of ordinary skill in the are will appreciate that power devices <b>110</b><i>a</i>-<i>n </i>and endpoint devices <b>120</b><i>a</i>-<i>n </i>may be the same device (e.g., a smart home controller that is communicatively coupled to both a power generator and a power distributor) or attributed to the same location without deviating from the invention.

0024In various embodiments, power devices <b>110</b><i>a</i>-<i>n </i>include a respective generation program <b>112</b> for collecting information regarding power being generated by the corresponding power device, or devices, associated with power devices <b>110</b><i>a</i>-<i>n</i>. Based on the collected information regarding the power generated by the corresponding power device or devices, post module <b>114</b> of generation program <b>112</b> sends the information to blockchain network <b>140</b> for entry of energy produced into the blockchain ledger of power node <b>146</b>. Power node <b>146</b> has a copy of a blockchain ledger comprising various transactions of power generated by power devices <b>110</b><i>a</i>-<i>n </i>that is maintained by blockchain network <b>140</b>. In some embodiments and scenarios, generation program <b>112</b> posts or requests that an entry be made regarding power generated directly to blockchain network <b>140</b>, as described in further detail regarding <figref idref="DRAWINGS">FIG. 4</figref>. In other embodiments, generation program <b>112</b> sends the request to monitoring program <b>132</b> of smart power generation and targeting (SPGT) system <b>130</b>, which in turn posts the entry to be entered into the blockchain ledger via power node <b>146</b> maintained by blockchain network <b>140</b>.

0025In various embodiments, generation program <b>112</b> posts to power node <b>146</b> of blockchain network <b>140</b> information regarding power being generated by the corresponding power device, or devices, associated with power devices <b>110</b><i>a</i>-<i>n</i>. Blockchain network <b>140</b> includes various blockchain members <b>142</b><i>a</i>-<i>n</i>. Power node <b>146</b> contains a data structure that is shared among blockchain members <b>142</b><i>a</i>-<i>n</i>. For example, the blocks of the blockchain ledger are a listing of various entries regarding power generated previously by power devices <b>110</b><i>a</i>-<i>n</i>. Each blockchain member of blockchain members <b>142</b><i>a</i>-<i>n </i>includes an instance of blockchain program <b>144</b>. When a request to post power information is received, each instance of blockchain program <b>144</b> of the blockchain members <b>142</b><i>a</i>-<i>n </i>process the request to post the power information to the blockchain. Once a majority of the blockchain programs of the blockchain members <b>142</b><i>a</i>-<i>n </i>reach a consensus, power information is added the blockchain ledger. For example, consensus is reached based on a consensus protocol such as the Practical Byzantine Fault Tolerance (PBFT) consensus model. One of ordinary skill in the art will appreciate that any methodology or model for determining consensus among blockchain members <b>142</b><i>a</i>-<i>n </i>may be used without deviating from the invention.

0026In various embodiments and scenarios, blockchain network <b>140</b> stores the posted power generation information in an ordered list stored as a block of power node <b>146</b>. As one of ordinary skill in the art will appreciate, blockchains possess many important qualities. For each item or entry added to power node <b>146</b>, the blockchain program <b>144</b> that reached consensus among blockchain members <b>142</b><i>a</i>-<i>n </i>solve or generate cryptographic hash values that not only satisfy the current entry's information, but also the previous entries or blocks in the ledger of power node <b>146</b>. Any attempt to change the entries would result in different hash values which would cascade or further alter any subsequent entries. As such, blockchains possess a property referred to as immutability, an ability that does not allow changes to consensus entries made by the blockchain members <b>142</b><i>a</i>-<i>n</i>, which provides traceability and accountability for transactions recorded by the blockchain.

0027In various embodiments, metering program <b>122</b> of an endpoint device of endpoint devices <b>120</b><i>a</i>-<i>n </i>identifies power usage request for one or more devices that consume power. Based on criteria regarding the sourcing of said requested power, request module <b>124</b> of metering program <b>122</b> identifies entries in the ledger on node power node <b>146</b> or local node <b>146</b><i>a </i>for power generated by power devices <b>110</b><i>a</i>-<i>n </i>that match the criteria. For example, metering program <b>122</b> has identified that an associated endpoint device has criteria to source power from power devices <b>110</b><i>a</i>-<i>n </i>that produce electricity from solar cells. In this example, request module <b>124</b> identifies entries in the ledger contained by local node <b>146</b><i>a </i>that have been indicated to be generated from solar sources. Upon identification of a power generated entry in the blockchain ledger that matches the criteria, request module <b>124</b> of metering program <b>122</b> posts an entry of energy consumed on the ledger indicating the usage of the power. One of ordinary skill in the art of power distribution will recognize that the actual power generated from power devices <b>110</b><i>a</i>-<i>n </i>is not directly delivered or routed to endpoint devices <b>120</b><i>a</i>-<i>n</i>. However, as discussed herein smart power generating and targeting (SPGT) system <b>130</b> monitors and tracks entries in the blockchain to attribute and provide reporting of such usage.

0028In some embodiments, metering program <b>122</b> is provided, by a user, one or more rules regarding how energy and power is to be sourced or attributed to when indicated by the entries in the ledge of power node <b>146</b>. For example, one rule indicates that power is preferred to be sourced from renewable sources. In other examples, a preferred rate for energy consumption may be in a user-configured rule. In another example, a user-configured rule may indicate a geo-fence or nearby area to source energy from. During long distance transmission, power loss may occur, leading to inefficiencies during power delivery. One of ordinary skill in the art will appreciate that any number and type of rules may be provided by a user to source energy and attribute usage to certain power devices <b>110</b><i>a</i>-<i>n </i>based on a variety of user preferences, without deviating from the invention.

0029In various embodiments, monitoring program <b>132</b> of SPGT system <b>130</b> tracks various entries on the blockchain and provides reports regarding power generated by power devices <b>110</b><i>a</i>-<i>n </i>and power used by endpoint devices <b>120</b><i>a</i>-<i>n</i>. Due to the immutability of blockchains, monitoring program <b>132</b> does not need to verify nor authorize power generation and consumption by participating devices upon consensus of blockchain network <b>140</b>. However, in some embodiments, monitoring program <b>132</b> of SPGT system <b>130</b> receives information from post module <b>114</b> of various power devices <b>110</b><i>a</i>-<i>n </i>and from request module <b>124</b> of endpoint devices <b>120</b><i>a</i>-<i>n </i>regarding various entries to the blockchain ledger. Previous discussions and embodiments, where any device can post to a blockchain, are referred to as permissionless or public blockchains. In other embodiments, such as where monitoring program <b>132</b> of SPGT system <b>130</b> receives request to post to power node <b>146</b>, such configurations are referred to as permissioned or private blockchains. One of ordinary skill in the art will recognize that either public or private blockchains may be utilized without deviating from the invention.

0030In various embodiments, usage module <b>133</b> of monitoring program <b>132</b> generates reports regarding various fulfilled requests for sourcing power to endpoint devices <b>120</b><i>a</i>-<i>n</i>. In some scenarios, usage reports generated by usage module <b>133</b> are provided to one or more operators of power devices <b>110</b><i>a</i>-<i>n </i>regarding the amount of power, type of power requested and other metrics regarding the usage of power among endpoint devices <b>120</b><i>a</i>-<i>n</i>. In various embodiments, usage module <b>133</b> of monitoring program <b>132</b> generates reports regarding that ability of one or more power devices <b>110</b><i>a</i>-<i>n </i>to fulfill or meet various request from endpoint devices <b>120</b><i>a</i>-<i>n </i>based on source of power as well as any other criteria endpoint devices <b>120</b><i>a</i>-<i>n</i>. Such reports provide participating power devices <b>110</b><i>a</i>-<i>n </i>to analyze fulfillment metrics and determine trends as well as unmet demands made by endpoint devices <b>120</b><i>a</i>-<i>n</i>. In various embodiments, rate module <b>135</b> of monitoring program <b>132</b> generates reports regarding the rates and amounts of usage various endpoint devices <b>120</b><i>a</i>-<i>n </i>have indicated as being utilized when posting usage information to power node <b>146</b>. In some embodiments and scenarios, monitoring program <b>132</b> generates billing reports and statement that may be used for collections by operators of power devices <b>110</b><i>a</i>-<i>n. </i>

0031In various embodiments, power node <b>146</b> is replicated and shared across multiple devices (i.e., power devices <b>110</b><i>a</i>-<i>n</i>, endpoint devices <b>120</b><i>a</i>-<i>n </i>and SPGT <b>130</b>). In some scenarios, the blockchain of local nodes <b>146</b><i>a </i>may be permissioned or otherwise restrict access to entries in the blockchain ledger of power node <b>146</b>. Additionally, some device, such as power devices <b>110</b><i>a</i>-<i>n </i>and endpoint devices <b>120</b><i>a</i>-<i>n</i>, may have limited memory and storage characteristics. In such scenarios, local node <b>146</b><i>a </i>may be stored locally on such devices. While <figref idref="DRAWINGS">FIG. 1</figref> depicts power devices <b>110</b><i>a</i>-<i>n</i>, endpoint devices <b>120</b><i>a</i>-<i>n </i>and SPGT <b>130</b> as not part of blockchain network <b>140</b>, some embodiments may include any one of, or subset thereof, power devices <b>110</b><i>a</i>-<i>n</i>, endpoint devices <b>120</b><i>a</i>-<i>n </i>and SPGT <b>130</b> as part of blockchain network <b>140</b>. For example, in a public, permissionless blockchain network any device from power devices <b>110</b><i>a</i>-<i>n </i>or endpoint devices <b>120</b><i>a</i>-<i>n </i>may participate as a blockchain member of blockchain network <b>140</b> that contributes to the act of consensus for the addition of entries to the ledger of power node <b>146</b>. Additionally, in both permissioned and permissionless blockchains SPGT <b>130</b> may participate as a blockchain member of blockchain network <b>140</b> that contributes to the act of consensus for the addition of entries to a node. One of ordinary skill in the art will appreciate that any configuration of participating blockchain members <b>142</b><i>a</i>-<i>n </i>the comprises any combination of power devices <b>110</b><i>a</i>-<i>n</i>, endpoint devices <b>120</b><i>a</i>-<i>n </i>and SPGT <b>130</b> may be utilized without deviating from the invention.

0032<figref idref="DRAWINGS">FIG. 2</figref> is a functional block diagram illustrating a power transmission network, generally designated as <b>200</b>, with power delivery paths and data communication paths. <figref idref="DRAWINGS">FIG. 2</figref> includes SPGT <b>130</b> and blockchain network <b>140</b>, power devices (PD) <b>110</b><i>a</i>-<i>c</i>, power grid <b>220</b>, endpoint devices (ED) <b>120</b><i>a</i>-<i>c </i>and network-enabled power unit (NEPU) <b>234</b>. The power delivery paths are indicated as solid connecting lines and the data communication paths are indicated as dashed lines.

0033Power devices <b>110</b><i>a</i>-<i>c </i>are power generating devices that provide power to power grid <b>220</b>. Power grid <b>220</b> is a power distribution system that provides power to endpoint devices (ED) <b>120</b><i>a</i>-<i>c</i>. One of ordinary skill in the art will appreciate that power grid <b>220</b> may be of any size and complexity without deviating from the invention. For example, power grid <b>220</b> may be a national or large-scale power distribution system. As another example, power grid <b>220</b> may be a smaller city or community-based power distribution system, such as a microgrid. In various embodiments, power grid <b>220</b> may be any power distribution system that transports and conditions electrical power for delivery to endpoint devices (ED) <b>120</b><i>a</i>-<i>c. </i>

0034In various embodiments, power devices (PD) <b>110</b><i>a</i>-<i>c </i>generate electricity for delivery by power grid <b>220</b>. As discussed herein, when power devices (PD) <b>110</b><i>a</i>-<i>c </i>generate electricity, the corresponding generation program <b>112</b> posts information regarding the power generated to blockchain network <b>140</b>. Depending on the configuration of power node <b>146</b> and blockchain network <b>140</b>, the corresponding generation program <b>112</b> may directly send the information regarding the power generated to power node <b>146</b> or blockchain network <b>140</b> or the information may be sent to SPGT <b>130</b>, which posts the information to blockchain network <b>140</b>. In either scenario, blockchain network <b>140</b> reaches consensus and enters the information the blockchain ledger.

0035In various embodiments, the ledger of power node <b>146</b> includes information indicating one of more of (i) the amount of power generated, (ii) the manner in which the power was generated (e.g., solar, wind, coal, and the like) and (iii) a rate or monetary amount for usage of the power as entries or blocks in the ledger of power node <b>146</b>. In some embodiments, power node <b>146</b> includes entries with information regarding the power generated by power devices (PD) <b>110</b><i>a</i>-<i>c </i>as smart contracts, as depicted and described in further detail with respect to <figref idref="DRAWINGS">FIG. 3</figref>.

0036In some embodiments, power devices (PD) <b>110</b><i>a</i>-<i>c </i>includes various power granting devices utilized by utilities or organization to supply power to power grid <b>220</b>. In some embodiments and scenarios, devices from both endpoint devices (ED) <b>120</b><i>a</i>-<i>c </i>and from power devices (PD) <b>110</b><i>a</i>-<i>c </i>may be associated with the same location, and some instances, may be the same computing device. For example, a household with solar panels may, at times, provide power to power grid <b>220</b> and then at other times request power from power grid <b>220</b>. As discussed herein, endpoint devices (ED) <b>120</b><i>a</i>-<i>c </i>and power devices (PD) <b>110</b><i>a</i>-<i>c </i>may be discussed as separate entities in various scenarios and examples. One of ordinary skill in the art will appreciate that such discussion is provided for illustrative purposes and that the various embodiments discussed herein may also include embodiments where endpoint devices (ED) <b>120</b><i>a</i>-<i>c </i>and power devices (PD) <b>110</b><i>a</i>-<i>c </i>may be the same computing device or may be located at the same location or endpoint for power consumption, as well as power generation.

0037In various embodiments, endpoint devices (ED) <b>120</b><i>a</i>-<i>c </i>are network-enabled devices that consume power, such as a smart or network enabled device that regulates power (e.g., a smart plug), or distributes power to other devices via local power delivery paths, such as a breaker box for home power distribution (i.e., network-enabled power unit (NEPU) <b>234</b>). In various scenarios, endpoint devices <b>120</b><i>a</i>-<i>c</i>, or NEPU <b>234</b>, identify a request for power from power consuming devices connected to endpoint devices <b>120</b><i>a</i>-<i>c </i>or NEPU <b>234</b>. In some scenarios, a request may be received as a packet of information sent locally, where the power consuming device is network-enabled. In other scenarios, based on a load or current draw being applied to the endpoint devices <b>120</b><i>a</i>-<i>c </i>or NEPU <b>234</b>, the endpoint devices <b>120</b><i>a</i>-<i>c </i>or NEPU <b>234</b> identify a request for power, with the amount of power identified based on known or historic usage parameters of connected devices. As discussed herein, endpoint devices <b>120</b><i>a</i>-<i>c </i>or NEPU <b>234</b> request power based on criteria associated with the connected devices and preferences of a user or administrator of the location or devices. The endpoint devices <b>120</b><i>a</i>-<i>c </i>or NEPU <b>234</b> send the request to SPGT <b>130</b>. Based on the criteria, SPGT <b>130</b> identifies an entry in the ledger on power node <b>146</b> that matches the request, marks the power for the entry to be used, fully of partially, and sends an indication to the requesting endpoint devices <b>120</b><i>a</i>-<i>c </i>or NEPU <b>234</b> of the fulfillment, at which point the endpoint devices <b>120</b><i>a</i>-<i>c </i>or NEPU <b>234</b> draws power from power grid <b>220</b> commensurate to request.

0038In some scenarios and embodiments, one or more data communication paths are utilized to provide communication between power devices (PD) <b>110</b><i>a</i>-<i>c</i>, endpoint devices (ED) <b>120</b><i>a</i>-<i>c</i>, NEPU <b>234</b>, SPGT <b>130</b>, and blockchain network <b>140</b> regarding the various embodiments discussed in <figref idref="DRAWINGS">FIG. 1</figref>. For example, a wireless data communication path may be utilized between NEPU <b>234</b> and endpoint devices (ED) <b>120</b><i>b</i>-<i>c</i>. However, in some embodiments and scenarios, both the data communication paths and power delivery paths depicted in <figref idref="DRAWINGS">FIG. 2</figref> share the same medium. In some scenarios, the data communication path utilized between NEPU <b>234</b> and endpoint devices (ED) <b>120</b><i>b</i>-<i>c </i>is the power delivery paths. For example, NEPU <b>234</b> and endpoint devices (ED) <b>120</b><i>b</i>-<i>c </i>communicate via the power lines utilized in power delivery through such protocols or standards such as Broadband over Power Lines (BPL) or power-line communication (PLC) protocol that can utilize the power delivery paths for power distribution as well as the communication paths.

0039<figref idref="DRAWINGS">FIG. 3</figref> illustrates operational processes, generally designated as <b>300</b> of monitoring program <b>132</b>. In the following, SPGT <b>130</b> is indicated as the origination of posting entries on the ledger to power node <b>146</b> (i.e., processes <b>304</b> and <b>312</b>). As discussed herein, some scenarios and embodiments of the invention provide that other devices depicted in <figref idref="DRAWINGS">FIG. 1</figref> may post to blockchain network <b>140</b>. In process <b>302</b>, monitoring program <b>132</b> receives information regarding the power generated by a power device of power devices <b>110</b><i>a</i>-<i>n</i>. Either during operation or at predetermined intervals, generation program <b>112</b> of the power device sends information regarding the power generated by the power device to monitoring program <b>132</b>. Example information regarding the power generated by the power device includes, but is not limited to, (i) an amount of energy generated, or portion thereof; (ii) a source or type of generator used in power generation; and (iii) a rate or cost to utilize the power generated by the power device.

0040In process <b>304</b>, monitoring program <b>132</b> posts the information regarding the power generated by the power device to the blockchain network <b>140</b>. In some scenarios, such as in a public blockchain, the power device may post the information regarding the power generated by the power device to the blockchain network <b>140</b>. In various embodiments, blockchain members <b>142</b><i>a</i>-<i>n </i>add the entry to power node <b>146</b> after reaching consensus regarding the corresponding cryptographic hashes to maintain the properties of the ledger on power node <b>146</b> (e.g., such that immutability of the blockchain is maintained). In process <b>306</b>, monitoring program <b>132</b> broadcasts one or more blocks of the blockchain to the power consuming endpoint devices <b>120</b><i>a</i>-<i>n</i>. In some scenarios, monitoring program <b>132</b> sends new transaction to be posted to power node <b>146</b>. In other scenarios, monitoring program <b>132</b> sends transaction in grouping at predetermined intervals (e.g., after a pre-determined interval of time or after a predetermined number of blocks have been posted to power node <b>146</b>). In various embodiments, both power devices <b>110</b><i>a</i>-<i>n </i>and endpoint devices <b>120</b><i>a</i>-<i>n </i>store a copy of the broadcasted block to a local node <b>146</b><i>a. </i>

0041In process <b>308</b>, monitoring program <b>132</b> receives a request from an endpoint device of endpoint devices <b>120</b><i>a</i>-<i>n </i>that request a particular energy entry in power node <b>146</b>. In some embodiments and scenarios, endpoint devices <b>120</b><i>a</i>-<i>n </i>maintain a copy of the ledger on local node <b>146</b><i>a</i>. In such scenarios, metering program <b>122</b> of the requesting endpoint device identifies an entry on the ledger that matches one or more criteria. Once found, metering program <b>122</b> sends identifying information for the endpoint device, to monitoring program <b>132</b>. In other embodiments and scenarios, metering program <b>122</b> sends the one or more criteria for power selection to monitoring program <b>132</b>. In such embodiments and scenarios, monitoring program <b>132</b> identifies a block or entry of energy produced that matches the one or more criteria.

0042In process <b>310</b>, monitoring program <b>132</b> sends instructions to the requesting endpoint device indicating that the request is fulfilled. Based on the matched or identified entry in the ledger on the blockchain, the instructions will indicate the endpoint devices allotted energy or time to access power from power grid <b>220</b>. In process <b>312</b>, monitoring program <b>132</b> posts to blockchain network <b>140</b> a new entry indicating the previous entry has been utilized and no longer offered, attributing the unit of power to be “consumed” by the endpoint device. For example, the new entry may include an address of the available energy indicated in process <b>304</b>, binding the two entries for later usage reporting as discussed herein.

0043<figref idref="DRAWINGS">FIG. 4</figref> depicts a block diagram, generally designated as <b>400</b>, illustrating power node <b>146</b> comprising smart contracts <b>410</b><i>a</i>-<i>c</i>. As discussed herein, blockchains are a series of entries in a ledger that are cryptographically dependent on the preceding entry. In some embodiments, each entry includes an address along with information regarding power generated, for posts by power devices <b>110</b><i>a</i>-<i>n</i>, or power consumed, for posts from endpoint devices <b>120</b><i>a</i>-<i>n</i>. <figref idref="DRAWINGS">FIG. 4</figref> includes embodiments where in addition to such information, each entry is presented as a smart contract. Smart contracts are a particular feature of blockchain that also include conditions, requirements and instructions for the entry to be used or utilized. In some embodiments, the entries power node <b>146</b> contain smart contracts <b>410</b><i>a</i>-<i>c </i>that include various requirements and instructions for accepting the entry for power delivery or sourcing. For example, given a known power delivery standard (e.g., 120V at 60 Hz.) and current draw of the endpoint device, the instructions include an active time the endpoint may draw power from power grid <b>220</b> such that the amount of energy consumed matches that which was associated with the blockchain entry. Additionally, smart contracts <b>410</b><i>a</i>-<i>c </i>include one or more conditions for negotiating the requirements to fulfill and entry, such as a range of acceptable rates. In some embodiments and scenarios, users of endpoint devices <b>120</b><i>a</i>-<i>n </i>may request a unit of energy from the blockchain with an offered price or rate. In this example, smart contracts <b>410</b><i>a</i>-<i>c </i>include acceptable rates that operators of power devices <b>110</b><i>a</i>-<i>n </i>are willing to accept.

0044<figref idref="DRAWINGS">FIG. 5</figref> illustrates operational processes, generally designated <b>500</b>, of metering program <b>122</b>. In process <b>502</b>, metering program <b>122</b> receives a power delivery request from a connected endpoint device. In some embodiments and scenarios, the endpoint device is network-enabled and communicates to metering program <b>122</b> over a data communication path. In other scenarios, metering program <b>122</b> detects a load or current draw from the connected device to indicate a power delivery request. In process <b>504</b>, metering program <b>122</b> identifies power delivery criteria associated with the received power delivery request. In some embodiments, a user provides metering program <b>122</b> with one or more preferred criteria for power sourcing and delivery such as (i) the type of generator used or energy used to generate electrical power (e.g., solar cells, coal-burning, wind turbines, natural gas, geothermal, or nuclear reactor), (ii) a preferred rate or cost to be incurred for sourcing electrical power from a providing power device, and (iii) an amount to be used during delivery of the power to the endpoint device.

0045In decision process <b>506</b>, metering program <b>122</b> identifies a matching entry in the ledger on power node <b>146</b>. In some embodiments, metering program <b>122</b> utilizes local node <b>146</b><i>a </i>in process <b>506</b>. If a matching power entry on the blockchain is identified (YES branch of process <b>506</b>), then metering program <b>122</b> post to power node <b>146</b> that the associated smart contract is to be fulfilled. In scenarios where blockchain network <b>140</b> is permissioned, metering program <b>122</b> sends a request to monitoring program <b>132</b> of SPGT <b>130</b>, which in turn posts the indication that the smart contract will be fulfilled to power node <b>146</b>. If no match can be identified (NO Branch of process <b>506</b>), then metering program <b>122</b> identifies a matching smart contract based on one or more rules associated with the endpoint. For example, metering program <b>122</b> includes user provided rules for a hierarchical preference from which power may be sourced. For example, metering program <b>122</b> first attempts to find smart contracts that originate from renewable energy sources, then proceeds to non-renewable sources if no match is found. Another example includes rules for acceptable rates by the user of the endpoint device such as a range of values for rates. Additionally, metering program <b>122</b> may include rules for endpoints indicating the criticality of the operation of the device. If a device is marked as critical for operation, then metering program <b>122</b> will always identify a smart contract to fulfil the power delivery request in process <b>502</b>. If a device is marked as non-critical, then metering program <b>122</b> may not find an alternative smart contract if none that match either the criteria or rules for the endpoint device. In process <b>512</b>, upon identification and posting to power node <b>146</b> of a fulfilled smart contract, metering program <b>122</b> delivers power to the endpoint device based on the terms of the fulfilled smart contract. For example, where the smart contract has a pre-determined amount of energy, metering program <b>122</b> monitors the power drawn by the device until the total amount of energy is used.

0046In some embodiments for process <b>502</b>, metering program <b>122</b> determines an amount of power needed based on a device requesting power. The device requesting power is a smart-enabled device that, based on received commands from the user, identifies an amount of power that is necessary to perform the received commands. For example, a user instructs a smart oven to operate for 30 minutes at 350° F. Based on the operational characteristics of the oven, an expected amount of energy to be consumed is identified. In such embodiments, metering program <b>122</b> determines an amount of power needed based on the request and includes in decision process <b>506</b> the expected energy needed in the criteria and request for souring energy in the blockchain nodes.

0047<figref idref="DRAWINGS">FIG. 6</figref> illustrates operational processes, generally designated <b>600</b>, of generation program <b>112</b>. In process <b>602</b>, generation program <b>112</b> identifies information power regarding that is generated and supplied to power grid <b>220</b>. For example, sensors such as internet of things (IoT) devices connected to a line or connection between the power generating device of power devices <b>110</b><i>a</i>-<i>n </i>and power grid <b>220</b> record the amount of power generated by the device. Additionally, the information regarding manner in which the power was generated (e.g., solar, wind, coal, and the like) and a rate or monetary amount for usage of the power are also collected. In process <b>604</b>, generation program <b>112</b> post to power node <b>146</b> a smart contract including the gathered information regarding the power generated. In some embodiments and scenarios, generation program <b>112</b> posts to power node <b>146</b> at regular intervals. In other embodiments, generation program <b>112</b> posts to power node <b>146</b> based on denominations of energy (e.g., for a uniform denomination, each contract is for 1 kWh of energy, or varied denominations, various contracts in denominations of 1 kWh, 2 kWh and 5 kWh). One of ordinary skill in the art will appreciate that process <b>604</b> may be done continuously over the operation of the power generating device of power devices <b>110</b><i>a</i>-<i>n </i>or at set intervals or times without deviating from the invention.

0048<figref idref="DRAWINGS">FIG. 7</figref> depicts a block diagram, <b>700</b>, of components of power devices <b>110</b><i>a</i>-<i>n</i>, endpoint devices <b>120</b><i>a</i>-<i>n</i>, smart power generation and targeting (SPGT) system <b>130</b>, and blockchain members <b>142</b><i>a</i>-<i>n</i>, in accordance with an illustrative embodiment of the present invention. It should be appreciated that <figref idref="DRAWINGS">FIG. 7</figref> provides only an illustration of one implementation and does not imply any limitations with regard to the environments in which different embodiments may be implemented. Many modifications to the depicted environment may be made.

0049Power devices <b>110</b><i>a</i>-<i>n</i>, endpoint devices <b>120</b><i>a</i>-<i>n</i>, smart power generation and targeting (SPGT) system <b>130</b>, and blockchain members <b>142</b><i>a</i>-<i>n </i>each include communications fabric <b>702</b>, which provides communications between computer processor(s) <b>704</b>, memory <b>706</b>, persistent storage <b>708</b>, communications unit <b>710</b>, and input/output (I/O) interface(s) <b>712</b>. Communications fabric <b>702</b> can be implemented with any architecture designed for passing data and/or control information between processors (such as microprocessors, communications and network processors, etc.), system memory, peripheral devices, and any other hardware components within a system. For example, communications fabric <b>702</b> can be implemented with one or more buses.

0050Memory <b>706</b> and persistent storage <b>708</b> are computer-readable storage media. In this embodiment, memory <b>706</b> includes random access memory (RAM) <b>714</b> and cache memory <b>716</b>. In general, memory <b>706</b> can include any suitable volatile or non-volatile computer-readable storage media.

0051Generation program <b>112</b>, metering program <b>122</b>, monitoring program <b>132</b> and blockchain program <b>144</b> are stored in persistent storage <b>708</b> for execution and/or access by one or more of the respective computer processors <b>704</b> via one or more memories of memory <b>706</b>. In this embodiment, persistent storage <b>708</b> includes a magnetic hard disk drive. Alternatively, or in addition to a magnetic hard disk drive, persistent storage <b>708</b> can include a solid state hard drive, a semiconductor storage device, read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, or any other computer-readable storage media that is capable of storing program instructions or digital information.

0052The media used by persistent storage <b>708</b> may also be removable. For example, a removable hard drive may be used for persistent storage <b>708</b>. Other examples include optical and magnetic disks, thumb drives, and smart cards that are inserted into a drive for transfer onto another computer-readable storage medium that is also part of persistent storage <b>708</b>.

0053Communications unit <b>710</b>, in these examples, provides for communications with other data processing systems or devices, including resources of network <b>160</b>. In these examples, communications unit <b>710</b> includes one or more network interface cards. Communications unit <b>710</b> may provide communications through the use of either or both physical and wireless communications links. Generation program <b>112</b>, metering program <b>122</b>, monitoring program <b>132</b> and blockchain program <b>144</b> may be downloaded to persistent storage <b>708</b> through communications unit <b>710</b>.

0054I/O interface(s) <b>712</b> allows for input and output of data with other devices that may be connected to power devices <b>110</b><i>a</i>-<i>n</i>, endpoint devices <b>120</b><i>a</i>-<i>n</i>, smart power generation and targeting (SPGT) system <b>130</b>, or blockchain members <b>142</b><i>a</i>-<i>n</i>. For example, I/O interface <b>712</b> may provide a connection to external devices <b>718</b> such as a keyboard, keypad, a touch screen, and/or some other suitable input device. External devices <b>718</b> can also include portable computer-readable storage media such as, for example, thumb drives, portable optical or magnetic disks, and memory cards. Software and data used to practice embodiments of the present invention, e.g., generation program <b>112</b>, metering program <b>122</b>, monitoring program <b>132</b> and blockchain program <b>144</b>, can be stored on such portable computer-readable storage media and can be loaded onto persistent storage <b>708</b> via I/O interface(s) <b>712</b>. I/O interface(s) <b>712</b> also connect to a display <b>720</b>.

0055Display <b>720</b> provides a mechanism to display data to a user and may be, for example, a computer monitor, or a television screen.

0056The programs described herein are identified based upon the application for which they are implemented in a specific embodiment of the invention. However, it should be appreciated that any particular program nomenclature herein is used merely for convenience, and thus the invention should not be limited to use solely in any specific application identified and/or implied by such nomenclature.