This application is based upon and claims the benefit of priority of the prior Japanese Patent Application No. 2022-149623, filed on Sep. 20, 2022, the entire contents of which are incorporated herein by reference.
Embodiments discussed herein are related to a computer-readable recording medium storing a power transaction program, a power transaction method, and a power transaction apparatus.
In recent years, various services using blockchains (BCs) have been developed, and blockchains have been also applied to power transactions. Blockchains are used in various fields such as ledger management of crypto assets owing to openness of transaction histories and difficulty in falsifying the transaction histories.
As techniques using a blockchain technology for power transactions, techniques have been proposed, for example, for managing transactions of supply and demand of renewable energy and avoiding double counting related to power supply and demand. A technique has been also proposed in which zero-knowledge protocols are used in a blockchain to perform non-interactive privacy-preserving verifications of transactions.
Japanese Laid-open Patent Publication Nos. 2020-107202, 2021-135833, 2022-16506, 2018-78702, and 2021-108525, U.S. Patent Application Publication No. 2018/0267597, and Japanese National Publication of International Patent Application No. 2020-512572 are disclosed as related art.
According to an aspect of the embodiments, there is provided a non-transitory computer-readable recording medium storing a power transaction program for causing a computer to execute processing of storing, in a blockchain, transaction information between a supply side and a demand side of power, the processing including: determining a supply amount by dividing a power resource on the supply side by aggregate period; determining a demand amount of a plurality of customers who demand the power resource on the demand side; determining a surplus power that is a difference between the supply amount and the demand amount; generating, by using zero-knowledge protocol, the transaction information based on the supply amount, the demand amount, to store generated transaction information in the blockchain.
The object and advantages of the invention will be realized and attained by means of the elements and combinations particularly pointed out in the claims.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are not restrictive of the invention.
In transactions of renewable energy power, a transaction record related to supply and demand of a power resource per certain unit transaction time determined in advance, for example, per 30 minutes is recorded in a blockchain every time. In this case, the amount of data is so enormous that a scale problem occurs such as a heavy processing burden applied on the system. To address this, instead of recording a transaction record per 30 minutes in the blockchain every time, it is conceivable to compile transaction records for a certain period such as one month by using, for example, zero-knowledge protocol, thereby guaranteeing the validity of the transactions per 30 minutes. However, in order to avoid double counting of a power resource in a transaction such, for example, as delivering power more than a power generation amount to a customer, processing per unit transaction time of 30 minutes has to be performed, which imposes a processing burden. For this reason, there is a demand for a new method for all power transactions on a blockchain to reduce the burden on transaction management by, for example, making it unnecessary to manage information per unit transaction time, and also to avoid over-counting.
In one aspect, the present disclosure aims to avoid over-counting related to supply and demand of power resources without recording transaction information on power transactions per unit transaction time in a blockchain.
Hereinafter, embodiments of a computer-readable recording medium storing a power transaction program, a power transaction method, and a power transaction apparatus disclosed herein will be described in detail with reference to the drawings.
In the power transaction method in the present example, power transactions are performed among a power station A, a power retailer B, and customers C (a group of customers). The power station A makes a power contract K1 to sell all power resources (electricity) G generated by a designated power plant to the power retailer B. Although there are various contracts between the power station A and the power retailer B in fact, the contract is assumed herein to be the contract to sell all the power generation amount. Each of the customers C makes a power contract K2 to purchase demanded power from the power retailer B.
The power transaction system for power transactions performs the following processing in (1) Step1 to (3) Step3.
Step 1: The Power Retailer B Stores Power Resource Purchase Information
The power station A registers information on a power resource G in the blockchain BC in advance. The power retailer B makes the power contract K1 to receive a transfer of power generated by the power station A. According to this, under the control of the power contract management unit 101, the power transaction apparatus 100 stores, on the blockchain BC, information that a power generation amount of power generated for a contract period is purchased (transferred) as the power resource G. This power resource purchase information preferably carries a signature of the power station A.
In Step1, regarding the contract with the power station A, the power transaction apparatus 100 of the power retailer B records, on the blockchain BC, that part of power resources of the power station A is transferred according to the power contract K1. As a result, the power retailer B is allowed to handle, as their own power resource, the power resource G generated by the power station A.
(2) Step 2: The Power Retailer b Divides the Power Resource by Aggregate Period
The power transaction apparatus 100 of the power retailer B divides information on the power resource G purchased in Step1 by aggregate period into pieces, and stores the divided pieces of information in the blockchain BC. After the transfer of the power resource G is stored in the blockchain BC, the power retailer B divides the power resource G by aggregate period.
Under the control of the power transaction apparatus 100, for example, an unspent transaction output (UTXO) node 151 of the blockchain BC divides the power resource G by aggregate period (for example, one month).
(3) Step 3: The Power Retailer B Aggregates Transaction Information on a Basis Per Power Resource Divided in Step 2
The power transaction apparatus 100 of the power retailer B aggregates the transaction information in the following procedure, and stores power tracking information (a power tracking record TR) as an aggregation result in the blockchain BC.
Step 3.1: Prepare Information for Aggregation
The power transaction apparatus 100 collects an actual power generation amount of power and demand amounts of power demanded by all the customers per 30 minutes (referred to as a unit transaction time) in an aggregate period. Each customer requests power equivalent to a demand amount from a power supply side, and consumes the power of the demand amount. In order that “a supply amount=a demand amount” holds per unit transaction time of 30 minutes, the power transaction apparatus 100 defines “surplus power” as a term for receiving surplus power per 30 minutes. The power station system 110 of the power station A is provided with a smart meter 111, which measures a power generation result GA of a power generation amount of power. The customer system 120 of the customer C is provided with a smart meter 121, which measures a demand result RA of a demand amount of power. The customer system 120 is provided with a power tracking information reference unit 122. The power tracking information reference unit 122 accesses the blockchain BC and refers to the power tracking record TR, which is the aggregation result. The power transaction apparatus 100 collects the power generation result GA and the demand result RA of the smart meters 111 and 121 via Route A and the like. It is noted that the “Route A” is a route described in the ITU-T recommendation titled “ITU-T G.9958(03/2018)”, as one of three service routes in which the data from smart meters can be communicated.
Step 3.2: Prepare Matching Data for the Aggregate Period
The matching unit 102 of the power transaction apparatus 100 generates matching data on power generation and demand from the data processed in Step 3.1. The matching data is a result of matching between the power generation result GA and the demand result RA (including the surplus power) for each aggregate period (one month). In the example illustrated in
Step 3.3: Create a Power Tracking Record According to Zero-Knowledge Protocol
The zero-knowledge proof creation unit 103 of the power transaction apparatus 100 creates a power tracking record TR and a zero-knowledge proof ZC based on the data in Steps 3.1 and 3.2 according to zero-knowledge protocol.
Step 3.4: Store the Aggregation Result in the Blockchain
The power transaction apparatus 100 stores the power tracking record TR and the zero-knowledge proof ZC created in Step 3.3 in the blockchain BC. In this storing, the power transaction apparatus 100 creates a node 152 for supporting the aggregation. This aggregate node 152 is created by using, as inputs, the power resource G, the power tracking record TR, and the zero-knowledge proof ZC for the aggregate period. An output for the aggregate node 152 is unnecessary because all the power resource G is consumed. As a result, the power resource G used in the aggregation is completely consumed, and is not usable in another record.
In the above-described processing for a transaction record per unit transaction time of 30 minutes in order to avoid over-counting such as double counting in power transactions, the power transaction apparatus 100 of the example described above performs power transaction processing of the supply amount versus the sum of the demand amount and the “surplus power”. This setting of “the supply amount (power generation result GA)=the demand amount (demand result RA)+the surplus power” makes it unnecessary to manage the remainder of the power resource G.
For example, in transactions of renewable energy for power, managing transaction records per unit transaction time of 30 minutes in a blockchain is burdensome, and the following configuration is conceivable as a configuration for avoiding double counting. For example, in the course of storing transaction records per unit transaction time of 30 minutes in the blockchain, the transaction records are aggregated as a transaction record for a certain period according to the zero-knowledge protocol. The aggregation of valid pieces of input data makes it unnecessary to disclose the transaction records per unit transaction time of 30 minutes, and guarantees the validity of the aggregation result. In this conceivable configuration, the UTXO node of the blockchain manages a power resource that is not allocated yet, thereby avoiding double counting.
In this case, the UTXO node manages part of a power resource allocated to a customer and the remainder of the power resource in a power tracking record that is the aggregation result. It is considered to avoid double counting of a power resource by creating a power tracking record for each customer for an aggregate period, and together with this creating a UTXO node for allocation of the power resource.
This power transaction method involving the UTXO node compiles pieces of transaction information per unit transaction time for each customer by aggregation according to the zero-knowledge protocol, thereby solving the scale problem. However, this method is able to compile only the transaction information but is unable to compile information on power resources to be used to avoid double counting. The technique to solve the scale problem seems to be completed by aggregating not only the pieces of transaction information but also information for avoiding double counting.
As the transaction information, the information compiled by aggregation is usable. Meanwhile, the information for avoiding double counting has to specify a power resource available per unit transaction time of 30 minutes, but when complied, loses the information specifying the power resource. This does not allow the information for avoiding double counting to be compiled by aggregation according to the zero-knowledge protocol in the same way as in the transaction information. For aggregation, it is desired to make power resource management unnecessary by equalizing the total supply amount and the total demand amount of the power resources to each other per unit transaction time of 30 minutes. Since both the supply amount and the demand amount vary over time, a state where “the supply amount=the demand amount” of power per unit transaction time of 30 minutes is established without generating any surplus power is unachievable in fact. For this reason, in the related art, unspent power resources are not aggregated, but are managed by UTXO (extended UTXO method).
To address the above problem in the related art, the embodiment makes it unnecessary to manage information on the power resource G per unit transaction time of 30 minutes by generating no surplus power in order to enable aggregation of information for avoiding double counting as described above. The UTXO node 151 illustrated in
The smart contract SC illustrated in
1. Power Resource Registration
2. Power Resource Transfer
3. Power Resource Division
4. Power Tracking Information Registration
5. Power Tracking Information Reference
The zero-knowledge proof creation unit 103 creates a power tracking record TR by aggregating the input data according to the zero-knowledge protocol. The zero-knowledge protocol enables the power tracking record TR to be proved to be tracking of the supply and demand for the aggregate period. The zero-knowledge proof creation unit 103 outputs the power tracking record TR as an aggregation result, and a zero-knowledge proof ZC. The power tracking record TR does not hold the transaction information per unit transaction time of 30 minutes, but is proved to be information created with the transaction information per unit transaction time of 30 minutes aggregated on a monthly basis.
Examples of data used in the zero-knowledge protocol will be described with reference to
A specific example of the relationship among the power supply amount, the power demand amount, and the surplus power amount per unit transaction time illustrated in
In the example illustrated in
The power transaction apparatus 100 in the embodiment is enabled to adjust the demand amount by using the method of adding the “surplus power” SU to the demand amount. Providing the surplus power SU as an imbalance receiver on the customer C side makes it possible to record so-called balancing transactions in the blockchain in which “the supply amount=the demand amount” per unit transaction time of 30 minutes holds, and thereby consume all the supply amount. As a result, the aggregation according to the zero-knowledge protocol of the power transaction apparatus 100 makes it possible to consume the supply amount per unit transaction time unit of 30 minutes without excess or deficiency, so that no surplus power resource remains. According to the embodiment, the UTXO node 151 does not have to perform the power resource management for avoiding double counting.
In the processing performed by the power transaction apparatus 100, first, the power resource G of the supply amount is divided by aggregate period into power resources in a completely consumable size. Surplus power may occur due to an excessive supply amount. For the purpose of complete consumption, the power retailer b prepares the “surplus power” SU for receiving the surplus in place of the customers, and receives the surplus to make all the supply amount appear to be consumed.
As illustrated in
(Hardware Configuration Example of Power Transaction Apparatus)
The power transaction apparatus 100 includes a central processing unit (CPU) 1201, a memory 1202, a disk drive 1203, and a disk 1204. The power transaction apparatus 100 includes a communication interface (I/F) 1205, a portable-type recording medium I/F 1206, and a portable-type recording medium 1207. These components are coupled to one another through a bus 1200.
The CPU 1201 functions as a control unit that controls the entire power transaction apparatus 100. The CPU 1201 may include multiple cores. The memory 1202 includes, for example, a read-only memory (ROM), a random-access memory (RAM), a flash ROM, and the like. For example, the flash ROM stores a program of an operating system (OS), the ROM stores application programs, and the RAM is used as a work area of the CPU 1201. The programs stored in the memory 1202 are loaded into the CPU 1201, thereby causing the CPU 1201 to execute the coded processing.
The disk drive 1203 controls reading and writing of data from and to the disk 1204 in accordance with the control of the CPU 1201. The disk 1204 stores data written under the control of the disk drive 1203. Examples of the disk 1204 include a magnetic disk, an optical disk, and the like.
The communication I/F 1205 is coupled to a network NW through a communication line, and is coupled to an external computer and the smart contract SC of the blockchain BC through the network NW. Examples of the external computer include the power station system 110 and the customer system 120 illustrated in
The portable-type recording medium I/F 1206 controls reading and writing of data from and to a portable-type recording medium 1207 in accordance with the control of the CPU 1201. The portable-type recording medium 1207 stores data written under the control of the portable-type recording medium I/F 1206. Examples of the portable-type recording medium 1207 include a compact disc (CD)-ROM, a Digital Versatile Disk (DVD), a Universal Serial Bus (USB) memory, and the like. The CPU 1201 illustrated in
The power station system 110, the customer system 120, and the smart contract SC illustrated in
Next, processing examples of the power transaction apparatus 100 and the systems according to the embodiment will be described. Each of the power transaction apparatus 100, the power station system 110, and the customer system 120 involved in the power transactions illustrated in
Next, the power transaction apparatus 100 creates matching data from the data for the aggregate period (step S1602). Then, the power transaction apparatus 100 creates a power tracking record TR in accordance with the zero-knowledge protocol (step S1603). Subsequently, the power transaction apparatus 100 registers the created power tracking record TR (step S1604), and ends this processing. The power transaction apparatus 100 executes the smart contract SC, and thereby stores the power tracking record TR, which is the aggregation result, in the blockchain BC.
For example, the power transaction apparatus 100 obtains the surplus power amount in accordance with a calculation formula: the surplus power=the total power generation amount−the total demand amount. The total power generation amount is assumed herein to be equal to or larger than the total demand amount.
After the processing in step S1702, the power transaction apparatus 100 returns to the processing in step S1701. If the loop processing per unit transaction time (per 30 minutes) is completed for the aggregate period in step S1701 (step S1701: Yes), the power transaction apparatus 100 ends this processing.
If the loop processing per unit transaction time is not completed for the aggregate period (step S1802: No), the power transaction apparatus 100 distributes the power generation amount per unit transaction time (per 30 minutes) into the demand amount and the surplus power. The power transaction apparatus 100 creates, as matching data per unit transaction time (per 30 minutes), information on whose generated power is allocated to which place (step S1803). In this step, all the power generation amount is allocated because the power generation amount=the demand amount+the surplus power amount holds. After that, the power transaction apparatus 100 returns to the processing in step S1802.
If the loop processing per unit transaction time (per 30 minutes) is completed for the aggregate period in the processing in step S1802 (step S1802: Yes), the power transaction apparatus 100 performs processing in step S1804. In step S1804, the power transaction apparatus 100 creates matching data by merging the matching data per unit transaction time (per 30 minutes) (step S1804). The power transaction apparatus 100 ends this processing.
In step S2003, the power transaction apparatus 100 allocates the power resource G for a demand to the customer C (step S2003). Next, the power transaction apparatus 100 determines whether or not the customer C obtains the power resource G sufficient for the demand (step S2004). If the customer C obtains the power resource G sufficient for the demand (step S2004: Yes), the power transaction apparatus 100 returns to the processing in step S2002. On the other hand, if the customer C does not obtain the power resource G sufficient for the demand (step S2004: No), the power transaction apparatus 100 takes out the next power resource G (step S2005), and returns to the processing in step S2003.
In step S2006, the power transaction apparatus 100 allocates the power resource G to the surplus power (step S2006). After that, the power transaction apparatus 100 sets the allocation result as matching data per unit transaction time (per 30 minutes) (step S2007), and ends this processing.
The power transaction apparatus 100 creates a zero-knowledge proof by setting, as inputs, the data on the supply amount and the demand amount (including the surplus power) and the matching data for the aggregate period prepared in step S2101 and setting an aggregation result (power tracking record TR) as an output (step S2102). The power transaction apparatus 100 ends this processing.
The power station A performs processing of registering a power resource G in the blockchain BC (step S2201). The blockchain BC registers the power resource G of the power station A (step S2202).
The power retailer B makes a power contract K2 for power transactions with the customer C. The power retailer B makes a power contract K1 for power transactions with the power station A. In the blockchain BC, the power retailer B registers information that the power retailer B receives a transfer of the power resource G from the power station A based on the power contract K1 (power resource contract information k1) (step S2203). The blockchain BC registers the transfer of the power resource G for a contract period from the power station A to the power retailer B (step S2204).
Next, the power retailer B divides the power resource G (step S2205). The power retailer B divides the power resource G for the contract period into aggregate units on the blockchain BC (step S2206).
Next, the power retailer B matches the power transactions with the power station A and the customer C, and aggregates the matching data according to the zero-knowledge protocol (step S2207). The power retailer B registers the aggregation result (power tracking record TR) and the zero-knowledge proof ZC in the blockchain BC (step S2208). The blockchain BC registers the aggregation result (power tracking record TR) and the zero-knowledge proof ZC (step S2209).
At a certain timing after that, the customer C requests the aggregation result and the zero-knowledge proof from the blockchain BC (step S2210). The blockchain BC sends a response to the request to the customer C (step S2211). With the response from the blockchain BC, the customer C is allowed to use the aggregation result of the power transactions (step S2212).
The customer C may request the aggregation result and the zero-knowledge proof as illustrated in step S2210 repeatedly during the contract period. Every time the customer C requests the aggregation result and the zero-knowledge proof, the power retailer B performs the processing in step S2207 and the following steps, and makes a response to each request (step S2213).
Next, description will be given of processing examples of the smart contract SC of the blockchain BC that cooperates with the power transaction system described above.
In step S2502, the smart contract SC creates an instance for managing the right, stores transfer information such as parameters in the blockchain BC (step S2502), and ends this processing. As the information on a provider, a right identifier is stored in the case of the transfer from the right holder, and a power generator identifier is stored in the case where there is no right information yet.
It step S2503, the smart contract SC ends this processing because there is no right of transfer (step S2503).
In step S2702, the smart contract SC divides the right into the aggregate units. The smart contract SC creates divided instances, sets the right identifier of a supplier as the supplier, NULL as a supply destination due to an unspent state, and the divided period as the right holding period, stores the divided instances in the blockchain BC (step S2702), and ends the processing. An instance of the “supplier” performs functions equivalent to those of the UTXO node 151.
In step S2703, the smart contract SC ends this processing because there is no right of division (step S2703). In the processing example illustrated in
In the above-described embodiment, the zero-knowledge protocol guarantees the contents of information in a format where pieces of information on multiple customers C are compiled. For this reason, in the above-described embodiment, when a certain customer provides the information with the zero-knowledge proof ZC added to a third party, the certain customer also provides the information on the other customers.
As preliminary preparation for the processing in
A certification key and an authentication key for the zero-knowledge protocol are created and registered. For the zero-knowledge protocol, these keys have to be generated and shared in advance. A logic for the zero-knowledge protocol for extracting power tracking information TRα on a designated customer C (demand α) from the power tracking information is constructed, and the power tracking information TRα is stored in the blockchain BC by using the above smart contracts SC prepared by generating the keys.
Next, via the smart contract SC, the customer system 120 refers to a certification key KZC for the zero-knowledge protocol for extracting the power tracking information TRα on the designated customer C (demand α) (step S3202).
The customer system 120 extracts the power tracking information TRα in an output range of the designated customer C (demand α) from the power tracking information 2900 and the certification key KZC, and creates a proof of the zero-knowledge protocol (step S3203).
After that, the customer system 120 passes, as tracking information, the power tracking information TRα in the designated output range of the designated customer C (demand α) and the zero-knowledge proof ZCα to a third party institution 3100 (step S3204), and ends this processing.
Next, the system of the third party institution 3100 checks the validity of the power tracking information TRα on the designated customer C (demand α) based on the power tracking information TRα and the approval key KB for the zero-knowledge protocol (step S3302). When the power tracking information TRα is valid (step S3303: Yes), the system of the third party institution 3100 performs processing (approval) of confirming the validity of the power tracking information TRα (step S3304), and ends this processing. On the other hand, when the power tracking information TRα is invalid (step S3303: No), the system of the third party institution 3100 ends this processing without performing the processing (approval) on the power tracking information TRa.
The power transaction apparatus 100 of the embodiment described above stores the transaction information between the supply side and the demand side of power in the blockchain. The power transaction apparatus 100 sets, as transaction information, a supply amount obtained by dividing a power resource on a supply side by aggregate period, a demand amount of multiple customers who demand the power resource on a demand side, and surplus power that is a difference between the supply amount and the demand amount. Additionally, the validity of the transaction information may be guaranteed by the zero-knowledge protocol. In this way, the transaction information in which the power supply amount=the demand amount+the surplus power holds is stored in the blockchain BC, thereby leaving no surplus power resource, which makes it unnecessary to perform the power resource management for avoiding over-counting such as double counting.
The power transaction apparatus 100 acquires the power supply amount on the supply side and the power demand amount on the demand side per predetermined unit transaction time, and obtains the surplus power by calculating a difference between the supply amount and the demand amount of power per unit transaction time for the aggregate period. This makes it possible to equalize the supply amount and the demand amount per unit transaction time such as per 30 minutes, so that the supply amount is completely consumed by the demand without leaving any surplus power resource, and thereby to avoid over-counting such as double counting.
In a case where there are multiple power resources on the supply side, the power transaction apparatus 100 creates matching data per unit transaction time specifying which of the multiple power resources provides what supply amount to which of multiple customers. By aggregating the matching data according to the zero-knowledge protocol, the power transaction apparatus 100 creates power tracking information obtained as a result of the aggregation and the zero-knowledge proof as transaction information, and stores the transaction information in the blockchain. Accordingly, in a case where there are multiple resources on the supply side, it is possible to perform tracking identifying which of the resources on the supply side generated power received on the demand side.
The power transaction apparatus 100 performs the processing of dividing the power resource on the supply side by aggregate period by inputting the power resource for the power transaction contract period to the UTXO node on the blockchain via the smart contract. This makes it possible to obtain the output of the power resources divided by aggregate period. As described above, by using the UTXO node on the blockchain, the power resource may be easily divided by aggregate period such as one month.
In referring to the transaction information on a specific customer, the power transaction apparatus 100 extracts the transaction information on the specific customer by using the certification key via the smart contract according to the zero-knowledge protocol using the power tracking information for each of the multiple customers included in the transaction information stored on the blockchain and the certification key and the approval key for transaction information extraction generated and stored in advance. By providing the extracted transaction information and the zero-knowledge proof to a third party, the power transaction apparatus 100 may receive verification of the transaction information using the approval key by the third party. On the blockchain, the zero-knowledge protocol guarantees the contents of information in a format where pieces of transaction information on multiple customers are compiled. For this reason, when a certain customer provides the transaction information to a third party, the certain customer also provides the transaction information on the other customers. To address this, the above-described configuration is able to extract only the transaction information on the desired customer from the transaction information according to the zero-knowledge protocol, and provide a set of the extracted transaction information and the zero-knowledge proof to the third party.
In the case of the power transaction apparatus 100, the transaction information stored in the blockchain contains a resale destination of the surplus power on a per-aggregate period basis. This enables, for example, a power retailer to resell the surplus power for the aggregate period as a renewable energy value, and makes it possible to clearly specify a sale destination of the surplus power in the resale on the blockchain and thereby avoid double counting.
The power transaction apparatus 100 at a power retailer that receives transfers of power resources is able to execute the above-described processing based on the respective power contracts between power stations on a supply side and customers on a demand side. Accordingly, the power retailer is enabled to treat the power resources from the power stations as its own resources, and perform power transactions with the consumers based on the power contracts for power supply.
From the above, according to the embodiment, the power transaction apparatus 100 is able to, instead of recording the transaction information on the supply-demand relationship of the power resources per unit transaction time of 30 minutes, aggregate the transaction information to reduce the information amount, and verify whether or not over-counting of the resources, for example, a transaction of delivering power more than the power generation amount to the customer is performed.
In the related art, a remainder of a power resource allocated to each of the customers is utilized as a next power resource. To avoid double counting, power resource information has to be managed by a UTXO node extended in two dimensions. Thus, there is a scale problem that the power resource information has to be excluded from an aggregation target and increases the amount of data. In contrast, in the embodiment, instead of preparing and processing a power resource for each customer, multiple customers and power resources are collectively aggregated for an aggregate period, while the power resources are completely consumed for each unit transaction time of 30 minutes. By completely consuming the power resources, it is also possible to aggregate the information for avoiding double counting. As a result, it is possible to cut all pieces of information per unit transaction time of 30 minutes, which may cause a scale problem in using a blockchain. Thus, a scale problem that may occur in the related art by handling pieces of information per unit transaction time of 30 minutes, for example, does not occur.
The power transaction method described in the embodiment of the present disclosure may be implemented by causing a processor such as a server to execute a previously prepared program. The program of this method may be recorded on a computer-readable recording medium such as a hard disk, a flexible disk, a compact disc read-only memory (CD-ROM), a Digital Versatile Disk (DVD), or a flash memory, is read from the recording medium by the computer, and is executed by the computer. The program of this method may be distributed via a network such as the Internet.
All examples and conditional language provided herein are intended for the pedagogical purposes of aiding the reader in understanding the invention and the concepts contributed by the inventor to further the art, and are not to be construed as limitations to such specifically recited examples and conditions, nor does the organization of such examples in the specification relate to a showing of the superiority and inferiority of the invention. Although one or more embodiments of the present invention have been described in detail, it should be understood that the various changes, substitutions, and alterations could be made hereto without departing from the spirit and scope of the invention.
Number | Date | Country | Kind |
---|---|---|---|
2022-149623 | Sep 2022 | JP | national |