KR20220086135A - Block chain-based power transaction operation system - Google Patents

Abstract

The present invention relates to a power transaction operating system in which power transaction-related data is managed with a block chain. A block chain-based power transaction operating system according to a preferred embodiment of the present invention includes: a client module for receiving power transaction related data from at least one or more local terminals; a member management module that authenticates the client module by a preset authentication method, and allows access to the blockchain network only to the authenticated client module; an encryption module for receiving client information from the member management module and generating an encryption key corresponding to the received client information; and a block chain that receives data from the client module authenticated through the member management module, generates a block corresponding to the received data, and connects only blocks agreed upon through validation of the generated block to the chain. .

Description

Block chain-based power transaction operation system

The present invention relates to a power transaction operating system in which power transaction-related data is managed with a block chain.

Recently, the introduction of an energy prosumer system, in which individuals and institutions directly produce and consume electricity, and trade surplus electricity directly with each other, is actively discussed, unlike the conventional unilateral method of purchasing and using electricity from a power generation company. is becoming

The energy prosumer system is a technology that enables direct electricity trade between prosumers without a trading intermediary (KEPCO, Korea Power Exchange).

However, there is a problem in that the power transaction between energy prosumers without the intervention of an institution with public trust is weak in security.

Korean Patent Registration No. 10-1979586 (Registered on May 15, 2019) Korean Patent Publication No. 10-2018-0113786 (published on October 17, 2018)

An object of the present invention is to provide a blockchain-based power transaction operating system with improved security in an energy prosumer system environment.

A block chain-based power transaction operating system according to a preferred embodiment of the present invention includes: a client module for receiving power transaction related data from at least one or more local terminals; a member management module that authenticates the client module by a preset authentication method, and allows access to the blockchain network only to the authenticated client module; an encryption module for receiving client information from the member management module and generating an encryption key corresponding to the received client information; and a block chain that receives data from the client module authenticated through the member management module, generates a block corresponding to the received data, and connects only blocks agreed upon through validation of the generated block to the chain. .

Here, the block chain may generate power transaction-related data received from the electricity transaction seller and the electricity transaction consumer in one block for the same electricity transaction.

The present invention can prevent forgery and falsification of data from memory loss or external software attack by generating an encryption key corresponding to client information by separating the encryption module from the software-based block chain network, and managing the generated encryption key. may have an effect.

In addition, by managing the buyer-side data and the seller-side data that can verify the power transaction between the power transaction company as a single block, the reliability of the power transaction proof data can be increased.

1 is a schematic diagram of a blockchain-based power transaction operating system according to a preferred embodiment of the present invention.
FIG. 2 is a functional block diagram of the client module of FIG. 1 .
FIG. 3 is a functional block diagram of the member management module of FIG. 1 .
4 is a functional block diagram of the encryption module of FIG.
5 is a functional block diagram of the block chain of FIG.

Since the present invention can have various changes and can have various embodiments, specific embodiments are illustrated in the drawings and described in detail in the detailed description. However, this is not intended to limit the present invention to specific embodiments, and it should be understood to include all modifications, equivalents, and substitutes included in the spirit and scope of the present invention.

In describing each figure, like reference numerals have been used for like elements. In describing the present invention, if it is determined that a detailed description of a related known technology may obscure the gist of the present invention, the detailed description thereof will be omitted.

Terms such as first, second, etc. may be used to describe various elements, but the elements should not be limited by the terms. The above terms are used only for the purpose of distinguishing one component from another.

For example, without departing from the scope of the present invention, a first component may be referred to as a second component, and similarly, a second component may also be referred to as a first component.

and/or includes a combination of a plurality of related listed items or any of a plurality of related listed items.

The terms used in the present application are only used to describe specific embodiments, and are not intended to limit the present invention.

The singular expression includes the plural expression unless the context clearly dictates otherwise. In the present application, terms such as “comprise” or “have” are intended to designate that a feature, number, step, operation, component, part, or combination thereof described in the specification exists, but one or more other features It should be understood that this does not preclude the existence or addition of numbers, steps, operations, components, parts, or combinations thereof.

Unless defined otherwise, all terms used herein, including technical and scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs.

Terms such as those defined in a commonly used dictionary should be interpreted as having a meaning consistent with the meaning in the context of the related art, and should not be interpreted in an ideal or excessively formal meaning unless explicitly defined in the present application. does not

Hereinafter, a block chain-based power transaction operating system according to a preferred embodiment of the present invention will be described with reference to the accompanying FIGS. 1 to 5 . Hereinafter, in order to clarify the gist of the present invention, descriptions of previously known matters will be omitted or simplified.

Referring to FIG. 1 , the block chain-based power transaction operating system 1 according to an embodiment of the present invention allows access to the block chain network only to the authenticated client module, and according to the defined authority of the client module By processing data sensed from a local terminal, it is possible to provide a new method for efficiently managing the power transaction operating system 1 . The block chain-based power transaction operating system 1 may include a client module 100 , a member management module 200 , an encryption module 300 , and a block chain 400 .

The client module 100 may receive data sensed from at least one or more local terminals 10 . Here, the received sensing data may be a power transmission amount on the side of the power seller and/or the amount of power received on the side of the power purchaser that can prove the power transaction. During the electricity transaction time, the electricity seller side can transmit power to the power distribution network connected to the electricity transaction buyer side, and during the electricity transaction time, the electricity transaction buyer side receives power through the distribution network connected to the electricity seller side. .

The local terminal 10 may communicate with the client module 100 through an Internet of Thing (IOT) network. When limited to power transaction, the local terminal 10 may be a smart meter capable of communication and measuring the amount of power.

Referring to FIG. 2 , the client module 100 may include a data receiver 110 and a controller 120 .

The data receiver 110 may receive power transaction related data from at least one or more local terminals 10 . Here, the power transaction-related data may be the amount of power transmitted on the side of the power seller and the amount of power received on the side of the power purchaser, as described above. The power seller-side local terminal may transmit the power transaction identification code and power transmission amount to the data receiver 110 as power transaction related data. The power purchaser-side local terminal may transmit the power transaction identification code and the amount of power received as data related to the power transaction to the data receiver 110 .

An agent device (not shown) that matches a power seller and a power buyer for power transaction may interwork with the block chain-based power transaction operating system 1 of the present invention. When the power transaction between the power seller and the power purchaser is matched, the agent device may transmit a power transaction identification code for identifying the matched power transaction to the power seller and the power purchaser.

The control unit 120 may receive basic information and command signals from the client, and control the operation of the local terminal 10 in response to the received basic information and command signals and at the same time participate in the block chain network 1000 can do the action. That is, the control unit 120 receives basic information such as name, affiliation, IP (Internet Protocol), etc. from the client, and operates such as a member registration request and an access request to participate in the block chain network 1000 in response to a command signal can be performed. Here, the basic information is described as the client's name, affiliation, IP (Internet Protocol), etc., but it is not limited as long as the member management module 200 recognizes and defines the client. The command signal may be a signal for the client to participate in the blockchain network 1000 through the client module 100, and may be a signal for management of the local terminal 10 (eg, a measurement data request signal). .

Also, the control unit 120 may receive a member ID corresponding to the member registration request from the member management module 200 , and may request access to the member management module 200 using the received member ID. In this case, the client module 100 may access the member management module 200 and transmit data by allowing the member management module 200 to authenticate the member ID and allow access in response to the defined authority of the client.

Referring to FIG. 3 , the member management module 200 may authenticate the client module 100 by a preset authentication method, and only the authenticated client module 100 may allow access to the blockchain network 1000 . have.

In addition, the member management module 200 allows access to the blockchain network 1000 only to the authenticated client module 100 , but can be accessed with the client module 100 in response to the authority of the client module 100 . . That is, the member management module 200 can receive basic information of the client from the client module 100 to recognize the client, define the recognized client's access right, etc., and the client module ( 100) may allow access to the blockchain network 1000 corresponding to the access right. Here, the access right may be a right corresponding to the role of the client, for example, a reader, a writer, an administrator, and the like, and the preset authentication method may be described by the authenticator 240 to be described below.

Subsequently, the member management module 200 may transmit the basic information received from the client module 100 and the authorization information of the client to the encryption module 300 . At this time, the encryption module 300 may generate an encryption key corresponding to the received basic information and the client's authorization information, that is, a public key and a private key, and the generated private key is stored in the storage unit 320, and public The key may be transmitted to the member management module 200 .

Subsequently, the member management module 200 may use the public key received from the encryption module 300 to encrypt the client's basic information and the client's authorization information, and generate a member ID through encryption, and the generated member The ID may be transmitted to the client module 100 . At this time, the client module 100 may become a member of the blockchain network 1000 by the member management module 200 , and is authenticated by a preset authentication method through the member management module 200 to access the block chain according to the access authority. It is possible to access the network 1000 and perform actions such as reading, writing, and management.

The member management module 200 may include a recognition unit 210 , an authority control unit 220 , a member management unit 230 , and an authentication unit 240 .

The recognition unit 210 may recognize the client by using the basic information of the client provided from the client module 100 , and may provide the recognized basic information of the client to the authority control unit 220 .

The authority control unit 220 may define a client recognized by the recognition unit 210 , and define the client's access authority to the blockchain network 1000 using the client basic information provided from the recognition unit 210 . can Here, the access right may be a right for the role of the client, for example, a reader, a writer, an administrator, etc., and a right for the related block chain network 1000 channel may be assigned in response to the affiliation of the client.

The member management unit 230 may transmit the basic information and authorization information of the client to the encryption module 300, and receive the public key generated from the encryption module 300 to encrypt the basic information and authorization information of the client and at the same time to encrypt the basic information and authorization information of the member An ID may be generated and the generated member ID may be transmitted to the client module 100 . That is, the member management unit 230 requests the encryption key generation to the encryption module 300 and at the same time transmits the basic information of the client recognized by the recognition unit 210 and the authorization information of the client defined by the authorization control unit 220 to the encryption module 300, and receives only the public key of the encryption key generated from the encryption module 300, that is, the public key and the private key, to encrypt the client's basic information and the client's authorization information, and at the same time, the member ID can be created to register the client module 100 as a member.

The authenticator 240 may recognize the member ID of the client module 100 provided from the client module 100 , and transmit the recognized member ID to the encryption module 300 , and decrypted by the encryption module 300 . The member ID may be authenticated by receiving the client information corresponding to the member ID and comparing it with the client information before encryption. That is, the authentication unit 240 compares and matches the client information encrypted using the public key received from the encryption module 300 and the client information decrypted by the encryption module 300 using the private key to match the member ID. can be authenticated. Here, encryption may be to convert information into cipher text using a public key (a specific bit string), and decryption may be to restore original information using a private key.

Referring to FIG. 4 , the encryption module 300 may receive client information from the member management module 200 and may generate an encryption key corresponding to the received client information. That is, the encryption module 300 may receive the client's basic information and authorization information from the member management module 200, and may generate and manage an encryption key using the received client's basic information and authorization information. . Here, the encryption key may be a public key and a private key.

In addition, the encryption module 300 may generate an encryption key corresponding to the client information, and transmit the public key to the member management module.

In addition, the encryption module 300 generates an encryption key corresponding to the client information, the secret key may be stored and managed in the storage unit 320 .

In addition, the cryptographic module 300 may be an independent device formed based on hardware by being separated from the block chain network 1000 formed based on software, and may be implemented as an information device such as an appliance. Accordingly, even if the client information received in the member management module 200 is hacked by memory loss or external software attack, the encryption key for performing the preset authentication method, that is, the secret key capable of restoring the encrypted member ID, is a member Because the encrypted member ID cannot be restored by being managed separately from the management module 200, the preset authentication method cannot be performed, thereby preventing the forgery and falsification of data from memory loss of the member management module 200 or external software attacks can do. Here, the block chain network 1000 may be a process in which the member management module 200 and the block chain 400 are formed based on software.

The encryption module 300 may include an encryption key generation unit 310 , a storage unit 320 , and an authentication support unit 330 .

The encryption key generation unit 310 may receive the client's basic information and authority information from the member management module 200 to generate an encryption key corresponding to the client's information, and use the public key among the generated encryption keys to the member management module (200) can be transmitted. Here, the encryption key may be a public key and a private key.

The storage unit 320 may store a secret key among the encryption keys generated by the encryption key generation unit 310 , and may provide the stored secret key to the authentication support unit 330 .

The authentication support unit 330 may support a preset authentication method of the member management module 200 , receives a member ID from the member management module 200 , extracts a secret key corresponding to the received member ID, and extracts the extracted secret By decrypting the encrypted member ID using the key, the restored client information may be transmitted to the member management module 200 .

Referring to FIG. 5 , the block chain 400 may receive data from the authenticated client module 100 through the member management module 200 , and generate a block in response to the received data, and Only blocks that have been agreed upon through validation can be connected to the chain. Here, the data may be power transaction related data.

In the case of the power seller side, the power transaction related data may be the amount of power transmission and the power transaction identification code of the power seller side described above.

In the case of the power purchaser, the power transaction related data may be the amount of power received and the power transaction identification code of the power purchaser described above.

The block chain 400 may include a block management unit 310 , a consensus unit 320 , and a block control unit 330 .

The block management unit 310 may receive data transmitted from the client module 100 through the member management module 200 , and may generate a block using the received data. Here, the block may be generated by a hash function that converts data having an arbitrary size into data having a predetermined size, for example, a hash function selected as needed, such as MD5, SHA1, SHA2, etc. may be used. , but is not limited thereto.

The block management unit 310 may generate power transaction-related data having the same power transaction identification code as one block.

The consensus unit 320 may verify the validity of the block generated by the block management unit 310 , and may provide only the blocks agreed upon through the validity verification to the block control unit 330 . Here, the consensus algorithm for validation may be an algorithm defined to perform at least one of validation of blocks and transactions, ordering of blocks and transactions, and creation of new blocks, for example, proof-of-work ( Proof-of Work (POW) algorithm, Proof-of-Stake (POS) algorithm, Practical Byzantine Fault Tolerance (PBFT) algorithm, Proof of Elapsed Time (PoET) algorithm, etc. may be used, but is not limited thereto.

The block control unit 330 may receive a block agreed upon through validation from the consensus unit 320 , and may connect the received block to a chain. Here, each block may be connected in the form of a hash chain. That is, the nth block stores the hash value of the n-1th block. Accordingly, a change in the information of one block causes a change in the hash value of the corresponding block calculated from the corresponding block, which results in a change in the contents of the next block. Since it is impossible to do this, the reliability of the data of the blocks connected to the chain can be guaranteed.

1: Blockchain-based power transaction operating system
10: local terminal
100 : client module
110: data receiving unit
120: control unit
200: member management module
210: recognition unit
220: authority control unit
230: member management department
240: authentication unit
300: encryption module
310: encryption key generation unit
320: storage
330: authentication support department
400: Blockchain
410: block management unit
420: consensus
430: block control unit
1000: Blockchain Network

Claims (2)

a client module for receiving power transaction-related data from at least one or more local terminals;
a member management module that authenticates the client module by a preset authentication method, and allows access to the blockchain network only to the authenticated client module;
an encryption module for receiving client information from the member management module and generating an encryption key corresponding to the received client information; and
Receiving data from the client module authenticated through the member management module, generating a block corresponding to the received data, and including a block chain that connects only blocks agreed upon through validation of the generated block to the chain A blockchain-based power transaction operating system featuring. The method of claim 1,
A block chain-based power transaction operating system, characterized in that for the same electricity transaction, electricity transaction-related data received from the electricity transaction seller and the electricity transaction consumer side is generated in one block.

Images