Energy trading system and energy trading method

Abstract

To achieve flexible and efficient power transaction.SOLUTION: A power transaction system includes: a token generation unit that issues a power reservation token as a right to use specific power as power obtained by generating electricity using specific kinds of energy; a power supply control unit that supplies power in exchange for the power reservation token; and an actual token issuing unit that issues an actual token indicating use of the specific power supplied in exchange for the power reservation token.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to an energy trading system and an energy trading method. [Background technology]

[0002] Various forms of energy trading have been proposed. Patent Document 1 discloses an energy trading system in which a plurality of user systems, each controlling and managing electricity for each unit of electricity consumption, and an intermediary server that mediates the buying and selling of electricity are connected via a communication network, wherein the user systems include a performance data generation unit that measures the amount of electricity generated or consumed by each user during each power usage period and generates performance data, the intermediary server includes a token issuance unit that issues an energy trading token including an energy usage period, an amount of electricity, and a value based on the performance data, a token cancellation unit that cancels the energy trading token based on the performance data, and a cooperation unit that cooperates with a guarantee system that stores at least a portion of data related to the issuance and cancellation of the energy trading token and records the data related to the issuance and cancellation of the energy trading token, the guarantee system includes a plurality of nodes that store at least a portion of the data generated by the user systems and the intermediary server, the nodes aggregate the stored data at a predetermined timing and convert the stored data into blocks, the blocks are used to form a blockchain, and the blockchain is shared by the plurality of nodes and stored as a distributed ledger. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2020-107200 Summary of the Invention [Problem to be solved by the invention]

[0004] The invention described in Patent Document 1 leaves room for improvement in flexibility of electricity trading. [Means for solving the problem]

[0005] An energy trading system according to a first aspect of the present invention comprises: 1. An energy trading system executed by a plurality of computing devices, comprising: A token generating unit that issues a power reservation token, which is a right to use specific power that is generated using a specific type of energy; The determination is based on the amount of power measured by the smart meter. a power supply control unit that supplies power; and a power supply control unit that controls the specific power supplied in exchange for the power reservation token. A token indicating the actual usage of electricity is issued based on the electricity usage data obtained from the smart meter. and an achievement token issuing unit that performs the execution. A method for energy trading according to a second aspect of the present invention includes: 1. A method of energy trading executed by a plurality of computing devices, comprising: Issuing a power reservation token, which is a right to use specific power that is generated using a specific type of energy, and in exchange for the power reservation token, The determination is based on the amount of power measured by the smart meter. supplying power; and receiving the specified power in exchange for the power reservation token. A token indicating the actual usage of electricity is issued based on the electricity usage data obtained from the smart meter. To do and, Includes. [Effects of the Invention]

[0006] According to the present invention, flexible and efficient energy trading can be realized. [Brief explanation of the drawings]

[0007] [Figure 1] Overall configuration diagram of an energy trading system according to a first embodiment [Figure 2] Hardware configuration diagram of multiple devices [Figure 3] Diagram showing token types [Figure 4] Diagram showing the main components of an energy trading system [Figure 5] FIG. 10 is a diagram illustrating an example of a generated token management table. [Figure 6] FIG. 10 is a diagram showing an example of a reservation token management table. [Figure 7] FIG. 10 is a diagram illustrating an example of a token issuer management table. [Figure 8]FIG. 10 is a diagram illustrating an example of a purchase token management table. [Figure 9] FIG. 10 is a diagram illustrating an example of a demand device control management table. [Figure 10] FIG. 10 is a diagram showing an example of a supply device control management table. [Figure 11] A visual representation of the operation schedule [Figure 12] FIG. 10 is a diagram showing an example of a screen display by a reservation token display program. [Figure 13] Diagram showing the time series process from issuing electricity reservation tokens to settlement [Figure 14] Flowchart showing the schedule creation process by a demand management agent [Figure 15] Flowchart showing short-term demand management processing by a demand management agent [Figure 16] 1 is a flowchart showing a short-term power supply control process performed by a power supply control program. [Figure 17] Flowchart showing the settlement process by the token settlement program [Figure 18] FIG. 10 is a diagram showing an example of an achievement token management table in Modification 2. [Figure 19] Overall configuration diagram of an energy trading system according to a second embodiment [Figure 20] Functional configuration diagram of the evaluation device [Figure 21] 1 is a time chart showing an example of operation timing of the evaluation device; [Figure 22] FIG. 10 is a diagram showing an example of an evaluation table. DETAILED DESCRIPTION OF THE INVENTION

[0008] -First embodiment- A first embodiment of an energy trading system will be described below with reference to FIGS.

[0009] (Definition of terms) In this embodiment, "type of electricity" refers to the type of energy used for power generation, such as solar, wind, wave, geothermal, natural gas, fossil fuel, hydroelectric, and nuclear power. "Type of electricity" is also called "power category" or "power generation category." In this embodiment, the unit time in electricity trading is called "time slot" or "time frame." This unit time is, for example, 15 minutes.

[0010] In this embodiment, a "token" is electronic data that is created in a predetermined format and whose integrity is ensured. The specific method for ensuring the integrity is not limited, and various known methods can be used. In this embodiment, blockchain technology is used to ensure the integrity. However, for the sake of convenience in explanation, this embodiment will be described as if the token is data that can be occupied, and the process of rewriting the ownership of a token from A to B will be described as "A transfers the token to B."

[0011] (Overall composition) FIG. 1 is a diagram showing the overall configuration of an energy trading system S according to a first embodiment. The energy trading system S includes a reservation token generation device 10, a token management device 20, an actual token generation device 30, a power generation system 40, a power storage system 50, and a demand system 60. For convenience of drawing, FIG. 1 shows one of each component, but two or more of each component may exist. In particular, in this embodiment, there are multiple reservation token generation devices 10. The times of all the devices constituting the energy trading system S are synchronized, and the duration and start of the time slots are also common.

[0012] 1, solid lines indicate the flow of power, and dashed lines indicate the flow of information. That is, the components of the above-mentioned energy trading system S are interconnected via a network X. Furthermore, the power generation system 40, the energy storage system 50, and the demand system 60 are interconnected via a power grid G.

[0013] The power generation system 40 includes a supply management agent 41 that handles information and supply devices 42 that supply power. Each supply device 42 is equipped with a smart meter M that can chronologically record the power supplied to the power grid G. The power storage system 50 includes a power storage management agent 51 that handles information and a power storage device 52 that controls power. The demand system 60 includes a demand management agent 61 that handles information and a demand device 62 that consumes power. In this embodiment, the power generation system 40 is linked in advance to one of the reservation token generation devices 10. The linked reservation token generation device 10 sells all of the power generated by a certain power generation system 40, and the linked reservation token generation device 10 can control the power generation system 40 as needed.

[0014] An overview of the operation of each component shown in Fig. 1 will be described. The reservation token generation device 10 issues power reservation tokens and commands the power generation system 40 and the power storage system 50 to supply power corresponding to the issued power reservation tokens. The token management device 20 temporarily acquires the power reservation tokens issued by the reservation token generation device 10 and transfers the power reservation tokens to consumers. The token management device 20 also sends to the consumers an actual result token indicating that the power used by the consumer was the desired type of power.

[0015] The performance token generating device 30 generates performance tokens. Based on a command from the reservation token generating device 10, a supply management agent 41 of the power generation system 40 causes a supply device 42 to generate power and output the power to the power grid G. The supply device 42 is a variety of power generation devices, including, for example, a solar power generation device, a wind power generation device, a wave power generation device, a geothermal power generation device, a thermal power generation device, and a hydroelectric power generation device.

[0016] The power storage management agent 51 of the power storage system 50 outputs the power stored in the power storage device 52 to the power grid G ​​based on a command from the reservation token generation device 10. The power storage management agent 51 of the power storage system 50 may acquire a power reservation token based on its own judgment, for example, the processing result of a predetermined algorithm, and store power in the power storage device 52. The power storage management agent 51 may also store power in the power storage device 52 based on an external command. The power storage device 52 may be a battery that stores power as electric energy, a combination of a dam and a hydroelectric generator that stores electric energy as another type of energy, or the like.

[0017] A demand management agent 61 of the demand system 60 acquires a power reservation token from the token management apparatus 20 based on an operation plan of the demand devices 62. The demand devices 62 receive a supply of power via a power grid G. Each of the demand devices 62 is equipped with a smart meter M that can record the power supplied from the power grid G ​​in chronological order.

[0018] (Hardware configuration) 2 is a hardware configuration diagram of the reservation token generation device 10, the token management device 20, the actual token generation device 30, the supply management agent 41, the power storage management agent 51, and the demand management agent 61. Here, the hardware configuration common to the reservation token generation device 10, the token management device 20, the actual token generation device 30, the supply management agent 41, the power storage management agent 51, and the demand management agent 61 will be described as the configuration of a computing device 900.

[0019] The arithmetic device 900 includes a CPU 910 which is a central processing unit, a ROM 920 which is a read-only storage device, a RAM 930 which is a readable and writable storage device, an input / output device 940, and a communication device 950. The CPU 910 performs the processing described below by loading a program pre-stored in the ROM 920 into the RAM 930 and executing it. The input / output device 940 includes a mouse and a keyboard with which an operator inputs information to the arithmetic device 900, and an LCD display that presents information to the operator. The communication device 950 is a device for communicating with other devices via the network X, such as a network interface card or a wireless communication module.

[0020] The arithmetic device 900 may include a field programmable gate array (FPGA), which is a rewritable logic circuit, or an application specific integrated circuit (ASIC), which is an integrated circuit for a specific application, instead of the combination of the CPU 910, the ROM 920, and the RAM 930. Furthermore, instead of the combination of the CPU 910, the ROM 920, and the RAM 930, the arithmetic device 900 may be realized by a combination of different configurations, for example, a combination of the CPU 910, the ROM 920, the RAM 930, and an FPGA.

[0021] (Token type) 3 is a diagram showing types of tokens in this embodiment. Tokens in this embodiment are roughly divided into power reservation tokens and performance tokens. Performance tokens will be described later.

[0022] Power reservation tokens are classified into limited tokens and general-purpose tokens. Limited tokens are power reservation tokens whose power usage period is limited to specific dates and times. General-purpose tokens are power reservation tokens whose power usage period is not specified and can be used generally. However, for both limited tokens and general-purpose tokens, the length of time during which power can be used is a pre-defined time slot, for example, in units of 15 minutes. General-purpose tokens require activation before use. Furthermore, the amount of power and electrical capacity of both limited tokens and general-purpose tokens are pre-defined.

[0023] Restricted tokens are further classified into "restricted tokens with revocation conditions" and "restricted tokens without revocation conditions" depending on whether they have a revocation condition. Revocation is the forced termination of the contract by the issuer of the restricted token, and if it is revoked, consumers who have acquired that restricted token will be unable to use the electricity. Note that if the issuer revoks a restricted token, compensation to those who have acquired that token will be provided by prior agreement. If you acquire a restricted token with a revocation condition, it may be revoked and you will not be able to use the electricity, or it may not be revoked and you will be able to use the electricity.

[0024] Hereinafter, non-cancellable limited tokens and general-purpose tokens will be collectively referred to as "unconditional tokens," while conversely, conditional limited tokens will be referred to as "conditional tokens." Conditional tokens have uncertain conditions for receiving a supply of electricity, while unconditional tokens can receive a supply of electricity unconditionally.

[0025] An achievement token is information that indicates that a specific type of electricity has been supplied and used. The achievement token is ultimately sent to the consumer who acquired the power reservation token and consumed the electricity. In other words, if a limited token with a cancellation condition is acquired and then cancelled, an achievement token corresponding to the limited token with a cancellation condition will not be issued. Conversely, an achievement token is issued when a general-purpose token is acquired and used, when a limited token without cancellation is acquired, or when a limited token with a cancellation condition is acquired but not cancelled.

[0026] (Detailed configuration) 4 is a diagram showing the main configuration of the energy trading system S. The reservation token generation device 10 includes a token generation program 11, a power supply control program 12, a supply device control management table 14, a generated token management table 13, a device control management table 15, and an extinguishing program 16. Note that hereinafter, the token generation program 11, the power supply control program 12, and the extinguishing program 16 are also referred to as the "token generation unit," the "power supply control unit," and the "extinguishing unit," respectively.

[0027] The generated token management table 13 stores information about the power reservation tokens generated by the token generation program 11. The supply device control management table 14 stores information about the power generation and storage of the supply device 42 and the power storage device 52, which are the facilities for which the token generation program 11 issues power reservation tokens. For example, the stored information for the supply device 42 includes the power generation category, power generation capacity, and power generation cost, and for the power storage device 52 includes the power generation category, discharge capacity, and current amount of stored power.

[0028] The token generation program 11 issues power reservation tokens and sends them to the token management device 20. The power reservation tokens issued by the token generation program 11 may be at least one of limited tokens and general-purpose tokens, and limited tokens may or may not be cancelled. The token generation program 11 may issue power reservation tokens at its own discretion or may issue power reservation tokens based on instructions from _41 or _51. When issuing power reservation tokens, the token generation program 11 issues power reservation tokens according to the power generation capacity of each supply device 42 listed in the supply device control management table 14. For example, for thermal power plants, which can freely control the amount of power generation, power reservation tokens are issued for 70% of their power generation capacity, and for solar power plants and wind power plants, which have power generation capacity limits due to weather or other factors, power reservation tokens are issued for 30% of their power generation capacity. However, the token generation program 11 may also estimate the amount of power generation by solar power plants, wind power plants, etc., by referring to weather forecasts and past statistics, and determine the sum of the power generation capacities of the power reservation tokens to be issued based on this estimate.

[0029] The cancellation program 16 performs cancellation processing as necessary for the power reservation tokens generated by the token generation program 11. Specifically, the cancellation program 16 determines the power reservation tokens to be retired, notifies the token management device 20, and records the cancellation in the generated token management table 13. For example, the cancellation program 16 calculates the power generation capacity using renewable energy in a specified time slot based on the latest weather forecast, and if the total released power generation capacity recorded in the generated token management table 13 exceeds the calculated power generation capacity, cancels the power reservation tokens in excess.

[0030] The power supply control program 12 instructs the supply of power so as to satisfy the total sum of the power capacities of the released power reservation tokens for each time slot and each type of power. For each type of power, the power supply control program 12 calculates the power capacity (hereinafter referred to as the "required power capacity") by subtracting the sum of the power capacities of the restricted tokens cancelled by the cancelation program 16 from the sum of the power capacities of the sold restricted tokens in the specific time slot and the sum of the power capacities of the general-purpose tokens for which usage has been notified. The power supply control program 12 then procures power if the sum of the power generation capacities of the supply devices 42 is less than the required power capacity.

[0031] The token management device 20 includes a reservation token display program 21, a token management program 22, a token clearing program 23, a reservation token management table 24, and a token issuer management table 25. In the following, the reservation token display program 21, the token management program 22, and the token clearing program 23 are also referred to as the "reservation token display unit," the "token management unit," and the "token clearing unit," respectively.

[0032] The reservation token display program 21 is a program that provides information stored in the reservation token management table 24 to an external party. If the information is provided to a computer, it may be provided in a predetermined format, such as XML, to facilitate machine processing, or if the reservation token management table 24 is implemented as a database, it may be provided as an API interface that allows searching the database. If the information is provided to a human, it may be provided as a list of all the information stored in the reservation token management table 24, or as a search interface that allows searching the information stored in the reservation token management table 24 and the search results.

[0033] The token management program 22 receives power reservation tokens from the reservation token generation device 10, allocates the power reservation tokens to the demand management agents 61, and writes them to the reservation token management table 24. The token management program 22 may be configured integrally with the reservation token display program 21. The token clearing program 23 operates after power has been used based on the power reservation token, and finally sends the actual token to the demand management agent 61. The operation of the token clearing program 23 will be described in detail later.

[0034] The demand management agent 61 of the demand system 60 includes a schedule creation program 63, a short-term demand management program 64, a power token management program 65, a purchase token management table 66, a demand device control management table 67, and an operation schedule 68. In the following, the power token management program 65 is also referred to as the "token management unit."

[0035] The schedule creation program 63 secures the minimum required power capacity for the demand device 62 for each time slot and updates the operation schedule 68. The short-term demand management program 64 manages the power demand for a short period of time, specifically within one time slot. Since the schedule creation program 63 manages the power demand over multiple time slots, in comparison with the short-term demand management program 64, the schedule creation program 63 can also be called a "long-term demand management program."

[0036] The power token management program 65 receives the performance token and stores it in a non-volatile storage device. The purchased token management table 66 stores information about purchased power reservation tokens. The demand device control management table 67 stores information about the identifiers and control of the demand devices 62. The operation schedule 68 stores information about the operation of the demand devices 62 for each time slot.

[0037] Fig. 5 is a diagram showing an example of the generated token management table 13. The generated token management table 13 has multiple records, and each record includes information on a token ID, basic token information, token attributes, supply device, cancellation conditions, and allocation. Information transmitted from the token management device 20 is stored in the "allocation" section of the generated token management table 13, and information output by the token generation program 11 is stored in other sections of the generated token management table 13. Because the generated token management table 13 is a horizontally long table, it is written in three columns in Fig. 5 for convenience of drawing, and only the token ID is written in all columns to clearly indicate that it is the same record.

[0038] The "token ID" is written as "Tid" in the drawing for convenience of drawing, and is an identifier that identifies the power reservation token. "Token basic information" includes information on "power usage amount," which is the value obtained by integrating the available power over time, "capacity limit," which is the maximum power consumption, "usage time," which indicates the time slot, and "usage location," which is the power supply area. "Usage time" may be substituted with an identifier that indicates the time slot. "Token attributes" include "power generation category," which indicates the type of electricity, and "environmental value," which indicates value from the perspective of environmental protection.

[0039] When the supply device 42 uses renewable energy, the amount of power generated varies greatly depending on the weather, so the token generation program 11 may set the "power usage amount" and "upper limit capacity" to values ​​smaller than the maximum power generation capacity of the supply device 42. For example, the "environmental value" may be input as either "RE" indicating renewable energy or "NOT" indicating non-renewable energy.

[0040] The "Supply Device" is the identification information of the supply device 42 that supplies the power described in the record. The "Cancellation Conditions" include the "Cancellation Probability" which is an estimate of the probability of cancellation, the "Cancellation Conditions" which are an estimate of the conditions for cancellation, and the "Cancellation Guarantee" which is compensation in the event of cancellation. The token generation program 11 can calculate the "Cancellation Probability" using, for example, past statistics of the supply device 42.

[0041] "Allocation" stores information transmitted from the token management device 20, including the amount of electricity usage, upper limit capacity, usage time, usage location, and owner information. All of these, except for "owner," store the same type of information as the token basic information, and none of the values ​​exceed the token basic information. "Owner" is the identification information of the demand system 60 that obtained the electricity reservation token for that record.

[0042] FIG. 6 is a diagram showing an example of the reservation token management table 24. The reservation token management table 24 has multiple records, and each record includes information such as a token ID, basic token information, token attributes, issuer ID, cancellation conditions, allocation, and token redemption. Because the reservation token management table 24 is a horizontally long table, it is written in four columns in FIG. 6 for ease of drawing, and only the token ID is written in the first column to clearly indicate that it is the same record. The token management program 22 receives information from one record of the generated token management table 13 shown in FIG. 5 as information on a newly created power reservation token from the reservation token generation device 10. However, this received information does not necessarily have to include information on the "supply device." Most of the information shown in FIG. 6 is the same as that shown in FIG. 5, so repeated explanations will be omitted.

[0043] The "issuer ID", which is not included in Figure 5, is an identifier indicating the entity that issued the power reservation token, i.e., the operator of the reservation token generation device 10. However, in this embodiment, the reservation token generation device 10 itself is treated as the operator, i.e., the issuer, so the "issuer ID" is an identifier that identifies the reservation token generation device 10 that issued the power reservation token. The token management program 22 receives the identifier of the reservation token generation device 10 that issued the power reservation token along with information about the power reservation token, and records this value as the "issuer ID".

[0044] "Token Clearing", which is specific to Figure 6 and not included in Figure 5, is written in the clearing phase. "Token Clearing" includes the total issued amount, the amount used, the amount expired, and the actual token fulfillment rate. "Total issued amount" is the amount of power listed in the issued power reservation token, and is the same as the "power usage amount" in the "token basic information". "Usage amount" is the amount of power actually supplied by the supply device 42 in the corresponding time slot, and the output of the smart meter M is used. "Expiration amount" is the value obtained by subtracting "usage amount" from "total issued amount". "Actual token fulfillment rate" is the ratio of power supplied to the demand device 62, and is calculated as the ratio of "usage amount" to "total issued amount".

[0045] 7 is a diagram showing an example of the token issuer management table 25. The token issuer management table 25 has multiple records, and each record includes an issuer ID, issuer information, total issued amount, total used amount, cancellation information, and actual token fulfillment rate. Because the token issuer management table 25 is a horizontally long table, it is written in two columns in FIG. 5 for convenience of drawing, and only the issuer ID is written in the first column to clearly indicate that it is the same record.

[0046] The "issuer ID" is an identifier that identifies the issuer of the power reservation token, which in this embodiment is the reservation token generation device 10. The "issuer information" includes the "organization name" which is the name of the issuer, "contact information" such as a telephone number and email address, and "address" which is the location. The "total issued amount" is the total amount of power usage of the power reservation tokens that have been issued by the issuer to date. The "total usage amount" is the total amount of power that has been supplied by the issuer to date and used by each demand system 60.

[0047] The "extinction information" includes the extinction amount, the pre-proposed amount, and the ex-post ratio. The "extinction amount" is the total amount of electricity that the issuer has extinguished to date. The "pre-proposed amount" is the average value of the "extinction probability" that the issuer has proposed to date. The "ex-post ratio" is the average value of the ratio of electricity that the issuer has actually extinguished to date. The "actual token fulfillment rate" is the ratio between the amount of electricity used minus the amount of electricity extinguished and the amount of electricity actually supplied by the supply device 42. In the example of token ID "001" shown in Figure 6, 100 kWh should have been supplied, but only 80 kWh was actually supplied, so the "actual token fulfillment rate" was calculated as "80%." In this case, no extinguishing was performed before the start of the corresponding time slot.

[0048] FIG. 8 is a diagram showing an example of the purchased token management table 66. The purchased token management table 66 is made up of multiple records, and each record includes a token ID, usage time, and purchased token quantity. The token ID and usage time have been explained above, so a detailed explanation will be omitted here. The purchased token quantity includes "available" which is electricity that can be used with certainty and has no possibility of being destroyed, "conditional" which is electricity that may be destroyed, "canceled" which indicates electricity that has already been destroyed among "conditional" tokens, and "general-purpose tokens" which have been purchased and are not restricted tokens.

[0049] The first record shown in Figure 8 has a token ID of "011," and includes 50 kWh of electricity that may be destroyed between times "T1" and "T2," but has not yet been destroyed. The second record shown in Figure 8 has a token ID of "012," and the same usable period as the first record, from "T1" to "T2," includes 100 kWh of electricity from the limited token that will not be destroyed. In other words, in the example shown in Figure 8, it can be seen that 150 kWh is currently available between times "T1" and "T2." Furthermore, a 100 kWh general-purpose token is listed on the far right, and this electricity can also be used if necessary.

[0050] The third and fourth records shown in Figure 8 contain information about the tokens acquired between time "T2" and "T3", and the conditional electricity has already been cancelled. Therefore, only the unconditional 120 kWh can be used between time "T2" and "T3".

[0051] FIG. 9 is a diagram showing an example of the demand device control management table 67. The demand device control management table 67 contains information related to the control and management of the demand device 62. The demand device control management table 67 is made up of multiple records, and each record includes an identifier, a power meter, detailed device information, and a control option. "Identifier" is the identifier of the demand device 62 described in that record. "Power meter" is the identifier of the power meter that measures the power used by the demand device 62 described in that record.

[0052] "Device detail information" includes a device type and an access method. "Device type" is the type of the demand device 62 described in the record. "Access method" is the access method for controlling the demand device 62, such as the IP address of the demand device 62.

[0053] "Control options" include controllability, control mode, and cost. "Controllability" indicates whether the control of the demand device 62 can be changed. "Control mode" is a list of control modes that can be set for the demand device 62. For convenience of drawing, only two control modes are shown in Figure 9, but three or more may be listed. "Cost" is the cost for executing the corresponding "control mode." The first record shown in Figure 9 indicates that control mode "AAA" requires a cost of "50" and control mode "BBB" requires a cost of "40."

[0054] 10 is a diagram showing an example of the supply device control management table 14. The supply device control management table 14 will be explained mainly by focusing on the differences from the demand device control management table 67. Compared to the demand device control management table 67, the supply device control management table 14 further includes a "maximum capacity" field. The "maximum capacity" is the maximum capacity that the supply device 42 can supply.

[0055] FIG. 11 is a diagram visually illustrating the operation schedule 68. In FIG. 11, the horizontal axis represents time and the vertical axis represents the amount of power. The operation schedule 68 stores, for each time slot, the amount of power required by a job and information about the power reservation tokens that have been acquired. Furthermore, each job includes information about whether execution is mandatory, and power reservation tokens are distinguished by whether or not they have a cancellation condition.

[0056] In Figure 11, jobs that must be executed are indicated by hatching, while jobs that are not required to be executed are indicated without hatching. The height of the bar graph representing each job indicates the amount of energy required. As the legend in the upper right corner of Figure 11 shows, the energy consumption of unconditional tokens, i.e., general-purpose tokens activated with a specified time and non-cancellable limited tokens, is represented by a solid line, while the energy consumption of conditional tokens, i.e., limited tokens with a cancellation condition, is represented by a dashed line.

[0057] In the example shown in Figure 11, information about four time slots is shown, and in each time slot, only job A must be executed. In the time slot from time t1 to t2, the amount of power reserved in advance by tokens is less than the total amount of power required by jobs A to C. However, this is not a problem because the amount of power reserved by unconditional tokens is greater than the amount of power required by job A, whose execution is mandatory. In the time slot from time t2 to t3, the amount of power reserved in advance by tokens is greater than the total amount of power required by jobs A, B, and D. However, the amount of power reserved by unconditional tokens is less than the amount of power required by job A, whose execution is mandatory, so some action is required.

[0058] (Management screen) 12 is a diagram showing an example of a screen display by the reservation token display program 21. As described above, the reservation token display program 21 provides information stored in the reservation token management table 24. For example, the reservation token display program 21 identifies the demand management agent 61 that has accessed the token management device 20, and displays a list of power reservation tokens that the demand management agent 61 has purchased in a "My Token" tab, and displays newly transferable tokens in a "Tokens for Sale" tab. Furthermore, the reservation token display program 21 may be configured to allow the user to input or select "filter conditions" that define the conditions for the power reservation tokens to be displayed.

[0059] (Time chart) 13 is a diagram showing the time-series processing from issuance to settlement of an energy reservation token. This time-series processing is executed in the order of a transaction phase, a cancellation phase, a usage phase, and a settlement phase.

[0060] In the transaction phase, first, the token generation program 11 of the reservation token generation device 10 issues a new power reservation token and sends it to the token management device 20 (S811). When the token management device 20 receives the power reservation token, the token management program 22 adds information about the received power reservation token to the reservation token management table 24. The reservation token display program 21 of the token management device 20 provides the information stored in the reservation token management table 24 to the demand management agent 61, and the demand management agent 61 requests one of the power reservation tokens (S812). The token management program 22 provides the power reservation token in response to a request from the demand management agent 61 (S813). This completes the transaction phase.

[0061] In the cancellation phase, the cancellation program 16 of the reservation token generation device 10 determines whether each limited token needs to be cancelled, and transmits information about the limited token to be cancelled to the token management device 20 (S821). At this time, the cancellation program 16 writes information about the cancelled limited token to the generated token management table 13. The token management device 20 writes the received information about the limited token to be cancelled to the reservation token management table 24, and notifies the demand management agent 61 that owns the limited token that the limited token will be cancelled (S822). Upon receiving this information, the demand management agent 61 updates the purchase token management table 66. This completes the cancellation phase.

[0062] In the usage phase, the first two processes are required when a general-purpose token is used. That is, when a general-purpose token is used, the demand management agent 61 sends an activation notification to the token management device 20 to activate the general-purpose token (S831). This activation notification includes the token identifier and information on the time when use will begin. Upon receiving the activation notification, the token management device 20 writes the information into the reservation token management table 24 and sends the same activation notification to the reservation token generation device 10 (S832).

[0063] The reservation token generation device 10 first records the received validation notification in the generated token management table 13. Next, the power supply control program 12 of the reservation token generation device 10 extracts the restricted token for which the current time slot is set as the usage time and the general-purpose token for which the validation notification has been sent for the current time slot. The power supply control program 12 then instructs the supply management agent 41 corresponding to the extracted restricted token and general-purpose token to discharge (S833).

[0064] In the settlement phase, steps S841 to S842 and steps S843 to S845 proceed in parallel. For example, the supply management agent 41 transmits an achievement token issuance request to the achievement token generation device 30 every time a time slot ends (S841). This achievement token issuance request includes the identifier of the power reservation token and the amount of power supplied.

[0065] Upon receiving the achievement token issuance request, the achievement token generation device 30 issues an achievement token after confirming that power has been supplied (S842). For example, the achievement token generation device 30 refers to the time-series data of the smart meter M attached to the supply device 42 corresponding to the supply management agent 41, and confirms that the declared power has been supplied. The achievement token includes the token ID of the corresponding power reservation token, an issuer ID which is an identifier that identifies the reservation token generation device 10 that issued the power reservation token, the type of power, the time slot or date and time when the power was supplied, and information on the amount of power. The achievement token generation device 30 queries the token management device 20 using the identifier of the power reservation token included in the received achievement token issuance request, identifies the issuer and the type of power, and uses them to issue an achievement token.

[0066] For example, the demand management agent 61 transmits a token clearing request to the token management device 20 each time a time slot ends (S843). This token clearing request includes the identifier of the power reservation token and the amount of power usage. Upon receiving the token clearing request, the token management device 20 searches the reservation token management table 24 using the identifier of the power reservation token included in the received token clearing request, and identifies the reservation token generation device 10 that generated the power reservation token. The token management device 20 then transfers the received token clearing request to the identified reservation token generation device 10 (S844).

[0067] The reservation token generation device 10, which has received the token clearing request, searches the reservation token management table 24 using the identifier of the power reservation token included in the received token clearing request, and identifies the supply management agent 41 that was scheduled to supply the power corresponding to the power reservation token.The token management device 20 then forwards the received token clearing request to the identified supply management agent 41 (S845).

[0068] When both S842 and S845 are completed, the supply management agent 41 transmits the result token to the token management device 20 (S846). The token management device 20, which has received the result token, transmits the result token to the demand management agent 61. This completes the process of the settlement phase.

[0069] (flowchart) 14 is a flowchart showing the schedule creation process that the demand management agent 61 executes after the transaction phase is completed and before the utilization phase is initiated. In step S701, the demand management agent 61 references the operation schedule 68 and extracts time slots for which no schedule has been created within the schedule creation target period, for example, within 24 hours from the current time. Hereinafter, a time slot for which no schedule has been created within the schedule creation target period will be referred to as a "target time slot."

[0070] In the next step S702, the demand management agent 61 predicts the jobs to be executed in the target time slot, whether execution of each job is essential, and the amount of power required for each job. This prediction can be made using various known methods, and for example, the execution history and power consumption of jobs at the same time one day prior may be referenced.

[0071] In the next step S703, the demand management agent 61 determines whether the amount of power required in the target timeslot exceeds the amount of available tokens. Specifically, the demand management agent 61 compares the amount of power expected to be used by jobs that must be executed in the target timeslot with the amount of power of unconditional tokens in the target timeslot, and determines whether the former exceeds the latter. If the demand management agent 61 determines yes, it proceeds to step S704 to make up for the shortfall, and if it determines no, it proceeds to step S705.

[0072] In step S704, the demand management agent 61 purchases additional unconditional tokens or activates general-purpose tokens so that the number of available tokens in the target time slot exceeds the required power. In the following step S705, the demand management agent 61 creates a power usage plan schedule for the target time slot. Specifically, the demand management agent 61 writes the prediction results of step S702 and information about the power reservation tokens into the operation schedule 68. In the following step S706, the demand management agent 61 determines whether all schedules for the target schedule creation period have been created. If it determines that there are schedules that have not been created, the process returns to step S701. If it determines that all schedules have been created, the process ends with the processing in FIG. 14.

[0073] 15 is a flow chart showing the short-term demand management process that the demand management agent 61 executes after S833 in the usage phase. In this short-term demand management process, the demand device 62 secures the power it needs, focusing on the current time slot. In step S711, the demand management agent 61 reads the purchase token management table 66. In the following step S712, the demand management agent 61 obtains from the smart meter M the amount of power used so far in the current time slot. In the following step S713, the demand management agent 61 predicts the total amount of power to be used in the current time slot. Various known methods can be used for this prediction; for example, the total amount of power usage at the time the time slot ends can be calculated by extrapolation using statistics on power usage in the current time slot.

[0074] In the next step S714, the demand management agent 61 determines whether the predicted value is greater than the available amount. Specifically, the demand management agent 61 compares the predicted value calculated in step S713 with the total amount of power of unconditional tokens in the current time slot read in step S711. If the demand management agent 61 determines that the predicted value is greater than the available amount, it proceeds to step S715, and if it determines that the predicted value is equal to or less than the available amount, it proceeds to step S717.

[0075] In step S715, the demand management agent 61 calculates the control cost of controlling the demand devices 62, the cost of purchasing a restricted token, and the cost of purchasing or activating a general-purpose token so that the predicted value is equal to or less than the available amount. In this step, the control cost of the demand devices 62 stored in the demand device control management table 67 is referenced. In the following step S716, the demand management agent 61 adopts and executes the cheapest option based on the calculation results in step S715. For example, if the demand management agent 61 determines that purchasing and activating a general-purpose token is the cheapest, it communicates with the token management device 20 to purchase the general-purpose token and then performs activation processing in the current time slot.

[0076] In step S717, the demand management agent 61 determines whether the time has come for the current time slot to end. If the demand management agent 61 determines that the current time slot has not ended, it returns to step S712, and if it determines that the current time slot has ended, it ends the processing shown in FIG.

[0077] 16 is a flowchart showing the short-term power supply control process that the power supply control program 12 starts executing immediately after S833. This short-term power supply control process focuses on the current time slot and realizes the power supply instructed by the reservation token generation device 10. In step S721, the power supply control program 12 reads the generated token management table 13 and obtains the amount of tokens already sold in the current time slot, specifically the total amount of power. Note that this total includes the amount of power of general-purpose tokens validated for the current time slot.

[0078] In the next step S722, the power supply control program 12 acquires information on the current amount of power generation from the demand management agent 61. In the next step S723, the power supply control program 12 predicts the total amount of power generation in the current time slot. Various known methods can be used for this prediction, and for example, the total amount of power generation at the time the time slot ends may be calculated by extrapolation using statistics on the amount of power generation in the current time slot, or if the supply device 42 uses renewable energy, the total amount of power generation may be calculated based on a weather forecast.

[0079] In the next step S724, the power supply control program 12 determines whether the predicted value is greater than the amount of sold tokens. Specifically, the power supply control program 12 compares the predicted value calculated in step S723 with the amount of sold power in the current time slot read in step S721. If the power supply control program 12 determines that the predicted value is less than the amount of sold tokens, it proceeds to step S725, and if it determines that the predicted value is equal to or greater than the amount of sold power, it proceeds to step S727.

[0080] In step S725, the power supply control program 12 calculates the control cost of controlling the supplying device 42, the cost of purchasing a limited token from the token management device 20, and the cost of purchasing or activating a general-purpose token from another token management device 20 so that the predicted value is equal to or greater than the sales volume. In this step, the control costs of the supplying device 42 stored in the supplying device control management table 14 are referenced. In the following step S726, the power supply control program 12 selects and executes the cheapest option based on the calculation results in step S725. For example, if the power supply control program 12 determines that purchasing and activating a general-purpose token is the cheapest option, it communicates with the token management device 20 to purchase the general-purpose token and then performs activation processing for the current time slot. In this case, power is supplied from a supplying device 42 managed by another reservation token generation device 10.

[0081] In step S727, the power supply control program 12 determines whether the time for the current time slot to end has arrived. If the power supply control program 12 determines that the current time slot has not ended, it returns to step S721, and if it determines that the current time slot has ended, it ends the processing shown in FIG.

[0082] 17 is a flowchart showing the settlement process executed by the token clearing program 23 of the token management device 20 between S846 and S847 of the settlement phase. In step S731, the token clearing program 23 receives an actual performance token from the supply management agent 41. In the following step S732, the token clearing program 23 searches for a corresponding reservation token by referring to the reservation token management table 24. In this step, the token clearing program 23 searches for information stored in the reservation token management table 24 using the token ID of the power reservation token included in the actual performance token.

[0083] In the following step S733, the token clearing program 23 determines whether or not a record meeting the conditions has been found by the search in step S732. Specifically, the token clearing program 23 determines whether or not the combination of the token ID, issuer ID, and time slot included in the performance token matches the information stored in the reservation token management table 24. If the token clearing program 23 determines that a record meeting the conditions exists, it proceeds to step S734, and if it determines that a record meeting the conditions does not exist, it proceeds to step S735.

[0084] In step S734, the token redemption program 23 transmits the performance token received in step S731 to the purchaser of the power reservation token, and ends the processing shown in Fig. 17. In step S735, the token redemption program 23 returns the performance token received in step S731 to the sender, and ends the processing shown in Fig. 17.

[0085] According to the first embodiment described above, the following advantageous effects can be obtained. (1) The energy trading method performed in the energy trading system S includes the reservation token generation device 10 issuing an energy reservation token, which is the right to use specific energy generated using a specific type of energy; the reservation token generation device 10 supplying energy in exchange for the energy reservation token; and the performance token generation device 30 issuing an performance token indicating the use of the specific energy supplied in exchange for the energy reservation token. This enables flexible and efficient energy trading. Specifically, power generation companies can sell energy in advance without bearing the risk of power generation instability, which is unavoidable when using renewable energy. Consumers can purchase energy that meets their needs from a variety of power generation products and can further schedule their demand by reserving energy in advance. As the energy system as a whole, supply and demand can be matched in advance, enabling efficient operation.

[0086] (2) The performance token includes an identifier that identifies a specific type of energy, the time when the specific power was used, and the amount of the specific power used. Therefore, the performance token can be used to trace the power.

[0087] (3) Power reservation tokens include restricted tokens with pre-designated dates and times for using specific power, and general-purpose tokens with no pre-designated dates and times for using specific power, ensuring diversity in power products and providing a wide range of options for both power producers and consumers.

[0088] (4) Restricted tokens include those with a conditional cancellation that prevent the supply of electricity under certain conditions, and those without a conditional cancellation that allow the supply of electricity regardless of the conditions. This ensures diversity in electricity products and provides a wide range of options for both power producers and consumers.

[0089] (5) The electricity provided in exchange for the electricity reservation token can be used at any receiving point via the electricity grid G. Therefore, any type of electricity can be used from various locations.

[0090] (6) The specific types of energy include at least one of solar, wind, wave, geothermal, natural gas, fossil fuels, hydroelectric, and nuclear power, so that various types of electricity can be traded in advance.

[0091] (Variation 1) In the first embodiment described above, the token management program 22 transfers to the demand system 60 the power reservation token generated by the reservation token generation device 10. However, the token management program 22 may arbitrarily divide the power reservation token and transfer it to two or more entities. In this case, however, the total amount of available power in the divided power reservation tokens is limited to the amount of available power in the power reservation token before division. Furthermore, the token management program 22 cannot change the time slot of the limited token.

[0092] According to this modification, the following advantageous effects can be obtained in addition to the advantageous effects of the first embodiment described above. (7) A power reservation token includes an amount of available energy. The token management program 22 can divide a power reservation token and transfer it to two or more entities. The total amount of available energy in the divided power reservation tokens is equal to or less than the amount of available energy in the power reservation token before division. This allows for more flexible trading of power reservation tokens.

[0093] (Variation 2) The performance token generating device 30 may understand the origin of the electricity stored in the power storage device 52 and issue a performance token including the origin of the electricity to a demand system 60 that uses the electricity output by the power storage device 52.

[0094] FIG. 18 is a diagram showing an example of the achievement token management table 31 stored in the achievement token generation device 30. The achievement token management table 31 includes multiple records, and each record has fields for a token ID, basic token information, total power generation amount, origin, and token allocation. The "token basic information" includes a supply device ID that identifies the source of the power supply, an equipment type that indicates the type of equipment indicated by the ID, and a time slot that indicates the time period during which the power was supplied. The "origin" is information that identifies the token from which the power described in the record is derived. The "token allocation" includes an "allocation destination" that is the identifier of the device to which the token is allocated, and an "allocation amount" that is the amount of power allocated.

[0095] The first record in Figure 18 is information about token ID "901," indicating that a supply device that uses solar power supplied "100 kWh" to "D1." The second record in Figure 18 is information about token ID "902," indicating that device "D1" supplied "100 kWh" to "D34," and that this power originated from token ID "901." That is, in this example, device "D1" discharged the power it accumulated from time T1 to T2 between times T5 and T6, and since the accumulated power was obtained by solar power generation, "D34," who used this power, is issued an achievement token indicating that it used power obtained by solar power generation.

[0096] (Variation 3) The cancellation program 16 may create conditions for determining whether or not each restricted token needs to be cancelled, instead of determining whether or not it needs to be cancelled. The cancellation program 16 may send the created conditions to the token management device 20, which then determines whether or not it needs to be cancelled. In this case, however, the token management device 20 notifies not only the demand management agent 61 but also the reservation token generation device 10 of whether or not the token needs to be cancelled. When the reservation token generation device 10 receives notification from the token management device 20 regarding the cancellation of a restricted token, it updates the generated token management table 13 with that information.

[0097] (Variation 4) The issuance of the power reservation token and the control of the power supply may be performed by different entities. For example, the token generation program 11, the power supply control program 12, and the extinguishing program 16 shown in Figure 4 may be installed in different devices.

[0098] (Variation 5) The power reservation tokens are traded in exchange for money, and when a restricted token with an extinguishment condition is extinguished, a security may be paid to the demand management agent 61 from the token liquidation program 23 of the token management device 20. However, the "money" or "security" may be any of cash, installment payments, points, foreign currency, etc.

[0099] --Second embodiment-- A second embodiment of an energy trading system will be described with reference to Figures 19 to 22. In the following description, the same components as those in the first embodiment are denoted by the same reference numerals, and differences will be mainly described. Points that are not particularly described are the same as those in the first embodiment. This embodiment differs from the first embodiment mainly in that the reservation token generation device is evaluated.

[0100] FIG. 19 is a diagram showing the overall configuration of an energy trading system S according to the second embodiment. The energy trading system S according to the second embodiment differs from the first embodiment in that it includes an evaluation device 70 in addition to the configuration according to the first embodiment. The configuration of the evaluation device 70 will be mainly described below, and descriptions of the configuration and operation that are the same as those of the first embodiment will be omitted. The evaluation device 70 is connected to other devices via a network X. The hardware configuration of the evaluation device 70 is the same as that of the reservation token generation device 10, so a description thereof will be omitted.

[0101] 20 is a functional configuration diagram of the evaluation device 70. The evaluation device 70 has an evaluation program 71 and an evaluation table 72. The evaluation program 71 evaluates each reservation token generation device 10 and writes the evaluation results in the evaluation table 72. The token IDs of the power reservation tokens generated by each reservation token generation device 10 are also written in the evaluation table 72. Therefore, it can be said that each power reservation token is evaluated via the reservation token generation device 10 that generated it.

[0102] Various methods can be used for evaluation by the evaluation program 71. Here, two examples, evaluation method A and evaluation method B, are explained. Evaluation method A evaluates based on power generation capacity, while evaluation method B evaluates based on past performance. For ease of explanation, the evaluation is given on a five-point scale from 1 to 5, with higher numbers indicating higher evaluations and "1" being the lowest rank. The evaluation program 71 may use the evaluation results of any one of the multiple evaluation methods, or may use the average of the evaluation values ​​obtained by the multiple evaluation methods.

[0103] (Evaluation Method A) In this embodiment, each reservation token generation device 10 is linked to a specific supply device 42. The type and maximum capacity of power supplied by the supply device 42 are recorded in the supply device control management table 14, as described in the first embodiment. In evaluation method A, the evaluation program 71 first adds up the maximum capacities of each type of power of all the supply devices 42 linked to each reservation token generation device 10. The evaluation program 71 then compares the sum of these maximum capacities with the sum of the maximum capacities for each time slot of the issued restricted tokens to determine the evaluation.

[0104] For example, if the reservation token generation device 10 has issued limited tokens that exceed the sum of the maximum capacities of the supply devices 42 for any one type of electricity, the evaluation program 71 will assign the lowest evaluation of "1" to that reservation token generation device 10. Also, if the reservation token generation device 10 does not limit the evaluation to "1" and has issued limited tokens that exceed 90% of the sum of the maximum capacities of the supply devices 42 for electricity using any renewable energy, the evaluation program 71 will assign the reservation token generation device 10 an evaluation of "2." The above is an example of evaluation method A.

[0105] (Evaluation Method B) Evaluation method B uses the "token clearing" information in the reservation token management table 24. Specifically, the evaluation program 71 identifies the token ID of an electricity reservation token previously issued by the reservation token generation device 10 to be evaluated, and the higher the actual token fulfillment rate corresponding to that token ID, the higher the evaluation value. For example, the evaluation program 71 may evaluate the average actual token fulfillment rate, or may evaluate the lowest actual token fulfillment rate among all actual token fulfillment rates. For example, the evaluation program 71 can assign the highest rating of "5" if the actual token fulfillment rate of all power reservation tokens issued in the past by a certain reservation token generation device 10 is "100%", and can assign a rating of "4" if the average actual token fulfillment rate is "80%" or greater but less than "100%". This is an example of evaluation method B.

[0106] FIG. 21 is a time chart showing an example of the timing at which the evaluation device 70 operates. In the second embodiment, when the reservation token generation device 10 issues a new power reservation token, it transmits an evaluation request to the evaluation device 70. Upon receiving this evaluation request, the evaluation device 70 starts operation and transmits the evaluation result and an identifier for identifying the reservation token generation device 10 being evaluated to the token management device 20. The token management device 20 adds the evaluation information received from the evaluation device 70 to the information on the power reservation token received from the reservation token generation device 10, and records the added information in the reservation token management table 24. That is, in this embodiment, a field for an evaluation value is added to the reservation token management table 24. The evaluation value information is provided to the demand management agent 61.

[0107] FIG. 22 is a diagram showing an example of the evaluation table 72. The evaluation table 72 is made up of multiple records. Each record in the evaluation table 72 includes a generation device ID, which is the identifier of the reservation token generation device 10, a list of token IDs of the power reservation tokens generated by that reservation token generation device 10, the evaluation method used, and the evaluation result. For example, in the example shown in FIG. 22, the reservation token generation device 10 with identifier "X1" has an evaluation result of "4" by evaluation method A and an evaluation result of "5" by evaluation method B, and it can be seen that token IDs "001" and "002" have these evaluations.

[0108] According to the second embodiment described above, the following advantageous effects can be obtained. (8) The energy trading system S in the second embodiment includes an evaluation device 70 evaluating the reservation token generation device 10 and assigning to the energy reservation token an evaluation of the reservation token generation device 10 that generated the energy reservation token. This allows consumers to be provided with additional information for selecting an energy reservation token.

[0109] (9) Evaluation method A, which is one of the evaluations of the reservation token generation device 10 by the evaluation device 70, is based on the power generation capacity of the supply device 42 and the total amount of power issued by the reservation token generation device 10 on the same date and time of use, i.e., in the same time slot. Therefore, the power reservation token can be evaluated based on the information supporting the issuance of the power reservation token.

[0110] (10) Evaluation method B, which is one of the evaluations of the reservation token generation device 10 by the evaluation device 70, is based on the track record of supplying electricity in exchange for the generated electricity reservation token. Therefore, electricity reservation tokens can be evaluated based on the past track record of the issuer of the electricity reservation token.

[0111] In each of the above-described embodiments and modifications, the functional block configurations are merely examples. Some functional configurations shown as separate functional blocks may be configured as an integrated unit, or a configuration shown in a single functional block diagram may be divided into two or more functions. Furthermore, some of the functions of each functional block may be provided by other functional blocks.

[0112] The above-described embodiments and modifications may be combined with each other. Although various embodiments and modifications have been described above, the present invention is not limited to these. Other embodiments conceivable within the scope of the technical concept of the present invention are also included within the scope of the present invention. [Explanation of symbols]

[0113] 10...Reservation token generator 11...Token generation program 12...Power supply control program 16...Incineration Program 20...Token management device 22...Token Management Program 23…Token Liquidation Program 30...Achievement token generator 40...Power generation system 41...Supply Management Agent 42...Supply device 50...Energy storage system 51...Energy storage management agent 52...Electricity storage device 60...Demand System 61...Demand Management Agent 62...Demand devices 63...Schedule creation program 68...Operation schedule 70...Evaluation device

Claims

1. An energy trading system executed by a plurality of computing devices, comprising: a token generating unit that issues a power reservation token, which is a right to use specific power that is power obtained by generating power using a specific type of energy; a power supply control unit that supplies the specified power based on the amount of power measured by a smart meter in exchange for the power reservation token; An energy trading system including an actual usage token issuing unit that issues actual usage tokens indicating the actual usage of the specific energy supplied in exchange for the energy reservation token based on energy usage data obtained from a smart meter.

2. 2. The energy trading system according to claim 1, An energy trading system, wherein the performance token includes an identifier for identifying the specific type of energy, the time when the specific power was used, and the amount of the specific power used.

3. 2. The energy trading system according to claim 1, An energy trading system in which the energy reservation tokens include restricted tokens for which the dates and times when the specific energy can be used are specified in advance, and general-purpose tokens for which the dates and times when the specific energy can be used are not specified in advance.

4. 4. The energy trading system according to claim 3, An energy trading system, wherein the restricted tokens include restricted tokens with cancellation conditions that do not allow the supply of electricity under specified conditions, and restricted tokens without cancellation that allow the supply of electricity regardless of the specified conditions.

5. 2. The energy trading system according to claim 1, An energy trading system further comprising an evaluation unit that evaluates the token generation unit and assigns an evaluation of the token generation unit that generated the energy reservation token to the energy reservation token.

6. 6. The energy trading system according to claim 5, a supply device that generates electricity is linked to the token generation unit; The power reservation token includes a restriction token that specifies in advance a usage date and time when the specific power can be used and an amount of available power, An energy trading system, wherein the evaluation unit evaluates the token generation unit based on the power generation capacity of the supply device and the total amount of energy issued by the token generation unit on the same usage date and time.

7. 6. The energy trading system according to claim 5, An energy trading system, wherein the evaluation unit evaluates the token generation unit based on the performance of the energy supply control unit in supplying energy in exchange for the generated energy reservation token.

8. 2. The energy trading system according to claim 1, the power reservation token includes an amount of available power; a token management unit that divides the power reservation token and transfers it to two or more entities; An energy trading system, wherein a total amount of available energy in the divided energy reservation tokens is equal to or less than the amount of available energy in the energy reservation tokens before the division.

9. 2. The energy trading system according to claim 1, An energy trading system that can be used at any power receiving point.

10. 2. The energy trading system according to claim 1, An electricity trading system, wherein the specific type of energy includes at least one of solar, wind, wave, geothermal, natural gas, fossil fuels, hydroelectric, and nuclear.

11. 5. The energy trading system according to claim 4, The power reservation token is traded in exchange for monetary payment, The energy trading system further includes a token liquidation unit that pays a security to a purchaser of the revocable limited token if the supply of electricity is not received in exchange for the revocable limited token.

12. 2. The energy trading system according to claim 1, An electricity trading system including a demand system that acquires the electricity reservation token and receives a supply of the specified electricity in exchange for the electricity reservation token.

13. A method of energy trading executed by a plurality of computing devices, comprising: Issuing a power reservation token, which is a right to use specific power, which is power obtained by generating power using a specific type of energy; supplying the specified power in exchange for the power reservation token based on the amount of power measured by a smart meter; and issuing an actual usage token indicating the actual usage of the specific electricity supplied in exchange for the electricity reservation token based on electricity usage data obtained from a smart meter.

Images