KR20210110056A - Layer Blockchain System for Large Information Sharing - Google Patents

Abstract

The present invention relates to a layer blockchain system for sharing large-capacity information. According to an embodiment of the present invention, a layer blockchain system for sharing large-capacity information comprises: a main ledger including an initial main block and one or more main block chains; a sub-ledger including an initial sub-block and one or more sub-blockchains; nodes including at least one first node created to be connected to the main ledger, sharing the main ledger, and a second node created to be connected to the sub-ledger, sharing the sub-ledger; and one or more entities connected to the sub-ledger to record transaction or event information included in the sub-blockchains, and for sharing the transaction address function of the sub-blockchains and the sub-blockchains. Accordingly, the layer blockchain system can verify the total amount of events or transactions of an operator that have occurred within the timeslot period included in the main ledger, even if the blockchain belonging to the sub-ledger is corrupted or deleted, and can determine security information including reliability or threat, or determine file backup and user behavior logs, based on a large amount of data.

Description

Layer Blockchain System for Large Information Sharing

The present invention relates to a hierarchical blockchain system for large-capacity information sharing. More specifically, it relates to hierarchical blockchain technology that records program and network behavior records and threat information.

With the advent of blockchain-applied Bitcoin, it has been demonstrated that the sharing of all participating members of signed data, which was technically and theoretically possible but not attempted, is sufficiently operable with current network and computer performance.

Verifies the integrity of data blocks accumulated on the basis of digital signatures in the shared ledger, and proves that defense and judgment against malicious information tampering through the consensus process of all network participants are adequately protected and operated to meet economic expectations As a result, many services related to the creation of virtual currency such as Bitcoin and virtual currency were created.

In addition, the Bitcoin block chain technology, which was inextricably linked with virtual currency, has disadvantages such as the use of PC resources with many Proof of Work used in the consensus process and restrictions on transaction types, which can be converted into a programmable transaction format under specific conditions. Various altcoins and altchain technologies have been born, such as the Proof of Stake method, which expands to smart contracts and enables network consensus with fewer resources.

Typically, the technology used in the most platforms and related technologies is the blockchain technology applied to Ethereum, which is used for various services by constructing a very flexible and expandable public and private chain (patents). It will be described in detail with reference to Document 1) as follows.

(Patent Document 1) relates to a double security blockchain authentication system and a method therefor. According to this, transactions can be performed only through a smart node with a client key activated, and the generated block is double verified through a megablock to secure security We are launching a dual security blockchain electronic transaction authentication system that can strengthen the

However, in the aforementioned (Patent Document 1), it is cumbersome to backtrack data distributed to one or more nodes, and through the transaction contents described in the first block, resource consumption and increase in the shared block chain in the consensus process such as proof of work Due to this, there is a problem in that the shared data between participating nodes increases exponentially.

Republic of Korea Patent Publication No. 10-1918446

The purpose of the present invention is to have a hierarchical structure in which one or more sub-blockchains are formed in the main block chain, and only refined information is shared between nodes participating in the network, and information is collected by recording a large amount of actions in a short time, It aims to provide a hierarchical blockchain system for sharing a large amount of information to share the collected information.

In order to solve the above problem,

A hierarchical block chain system for sharing large-capacity information according to an embodiment of the present invention includes a main ledger including an initial main block and one or more main block chains;

Sub Ledger containing the initial sub-block and one or more sub-blockchains;

a node including at least one first node that is created to be connected with the main ledger and shares the main ledger and a second node that is created to be connected with the lower ledger and shares the lower ledger;

one or more entities connected to the lower ledger to record transaction or event information included in the lower block chain and sharing the transaction address function of the lower block chain and the lower block chain;

may include.

In addition, in the hierarchical block chain system for sharing large-capacity information according to an embodiment of the present invention, a manual method that allows a new subject to participate in the block chain only when an approved transaction or event is generated through the electronic signature of the subject; and

an active method in which a self-generated subject including a public key can participate in the main block chain together with the sub block chain generation; includes,

The first main block may create the subject through either the passive method or the active method.

In addition, in the hierarchical block chain system for sharing large-capacity information according to an embodiment of the present invention, when the subject generates a specific event transaction, the lower block chain is detailed based on the nature and transaction type of the event. Sub-block transactions that create transaction records; and

a sub-block header capable of confirming the accumulated result values of transactions and events that have occurred between objects based on detailed information on one or more of the sub-block transactions and summary information on accumulated events or total transactions;

may include.

In addition, in the hierarchical block chain system for sharing large-capacity information according to an embodiment of the present invention, a timeslot for generating a block in which an event or transaction is recorded for a certain period of time during which a transaction with the same transaction target subject is maintained in the lower block chain The sub-block transaction can be created with a star generation rule.

In addition, in the hierarchical block chain system for sharing large-capacity information according to an embodiment of the present invention, when an event or transaction for each other subject occurs in the lower block transaction, a block in which the event or transaction is recorded for each subject is generated. creation rules for each transaction entity; includes,

The lower block transaction may generate a block based on the generation rule for each time slot, but may generate the block including the generation rule for each transaction subject.

In addition, in the hierarchical block chain system for sharing large-capacity information according to an embodiment of the present invention, the lower block transaction includes version information, the total length of the lower block header, each subject identification ID, transaction ID, and detailed transaction information. includes,

The detailed transaction information may include a transaction date and time, a transaction value, an event or transaction type, and event or transaction information.

In addition, in the hierarchical block chain system for sharing large-capacity information according to an embodiment of the present invention, when one or more of the lower initial blocks individually configured from the node are generated, the generation rule for each timeslot among the generated lower block transactions The lower initial block including the detailed transaction information equal to the timeslot period based on is generated as the lower block transaction,

The lower initial block including the detailed transaction information that is not the same as the timeslot period may be withheld and reviewed at a subsequent timeslot period.

In addition, in the hierarchical block chain system for sharing large-capacity information according to an embodiment of the present invention, at least one or more of the data included in the detailed transaction information needs to be connected to the outside, or at least one of the sub-block transactions is When more than a certain amount of data is stored, it may be stored in an interplanetary file system or a database (DB).

In addition, in the hierarchical block chain system for sharing large-capacity information according to an embodiment of the present invention, after being stored in the distributed file structure or database, the lower block transaction is a peer to the stored distributed file structure or database. ), an access path including an address, URI, and URL can be recorded in the detailed transaction information.

In addition, in the hierarchical block chain system for sharing large-capacity information according to an embodiment of the present invention, the lower block header includes version information, the total length of the lower block header, and the previous lower block transaction and the current lower block transaction. It includes hash verification value for ID, hash value of all fields constituting the sub block header, hash value for sub block transaction ID, detailed information and summary information,

The summary information may include a summary value of the total of events or transactions that have occurred cumulatively in the detailed information.

In addition, in the hierarchical block chain system for sharing large-capacity information according to an embodiment of the present invention, the detailed information includes a Merkle Root ID, the ID of the principal entity and the target entity, and the transaction included in the lower block transaction. It can include the number, the creation timestamp of the sub-block transaction, and the timeslot value.

In addition, in the hierarchical block chain system for sharing large-capacity information according to an embodiment of the present invention, the main block chain includes a main block transaction provided with a lower block header included in the lower block chain; and

a main block header capable of receiving a part of detailed information included in the main block transaction and checking the accumulated result values of transactions and events occurring between the lower block headers based on this;

may include.

In addition, in the hierarchical block chain system for sharing large-capacity information according to an embodiment of the present invention, the main block header includes version information, the total length of the main block header, each subject identification ID, transaction ID, and detailed transaction information. includes,

The detailed transaction information may include a transaction date and time, a transaction value, an event or transaction type, and event or transaction information.

In addition, in the hierarchical block chain system for sharing large-capacity information according to an embodiment of the present invention, the main block transaction includes version information, a hash verification value for IDs of the previous main block transaction and the current main block transaction, and the main block transaction. The hash value of all fields constituting the block transaction, the hash value of the ID of the lower block transaction included in the lower block chain, detailed information, summary information, and the total length of the detailed information may be included.

In addition, in the hierarchical block chain system for sharing large-capacity information according to an embodiment of the present invention, the detailed information includes a Merkle Root ID, the number of transactions included in the main block transaction, and generation of the main block transaction. It may include a timestamp and timeslot value.

In addition, in the hierarchical block chain system for sharing large-capacity information according to an embodiment of the present invention, the search method of the lower block transaction included in the lower block chain provides the node and the subject with the transaction information to be searched through the protocol. Indirect lookup method to lookup;

a direct inquiry method in which the main blockchain requests transaction information from one or more subjects connected to the sub-blockchain to directly inquire detailed transaction details; and

a partial inquiry method of inquiring partially occurring transactions by inquiring the transaction count and timeslot included in the summary information of the lower block header;

may include.

In addition, in the hierarchical block chain system for sharing large-capacity information according to an embodiment of the present invention, the indirect inquiry method is a specific event of the main block chain that the first node wants to inquire about and the subject included in the transaction. It is possible to verify the ID and the target ID, to check the total number of events and the total amount of transactions summarized in the event and transaction to collect the above information, and to provide the collected information to the first node requesting inquiry.

In addition, in the hierarchical block chain system for sharing large-capacity information according to an embodiment of the present invention, the direct inquiry method requests one or more of the subjects connected to the lower block chain to request a lower block transaction to inquire, and The detailed transaction details requested in the block transaction can be provided to the subject.

In addition, in the hierarchical block chain system for sharing large-capacity information according to an embodiment of the present invention, the first main block generates the subject including authentication information, and generates the first sub-block based on the subject and the subject can create the sub-blockchain based on the first sub-block.

In addition, in the hierarchical block chain system for sharing large-capacity information according to an embodiment of the present invention, when a sub-subject for the first sub-block is created, the first sub-block is recognized as the first main block, and , the first sub-block recognized as the first main block may generate a second initial sub-block based on the sub-subject.

These solutions will become more apparent from the following detailed description of the invention based on the accompanying drawings.

Prior to this, the terms or words used in the present specification and claims should not be construed in their ordinary and dictionary meanings, and the inventor may properly define the concept of the term in order to best describe his invention. It should be interpreted as meaning and concept consistent with the technical idea of the present invention based on the principle that it is possible.

According to an embodiment of the present invention, even if the block chain belonging to the lower ledger is errored or deleted, the total amount of events or transactions of the subject that occurred within the timeslot period included in the upper ledger can be verified, and based on a vast amount of data security information including reliability or threat, or file backup and user behavior log.

In addition, according to an embodiment of the present invention, it is possible to maximize reliability by securing the integrity of information in a distributed environment even for security threat information, trust information, and security log information, which is unavoidable in most centralized information collection due to the collection of a large amount of data. have.

In addition, according to an embodiment of the present invention, it is possible to share a large amount of data and original data, and in a structure in which the integrity of the hierarchical summary of each data and the integrity of individual data can be extended and verified, the sharing and It is possible to use

1 is a block diagram showing the components of a hierarchical block chain system for sharing large-capacity information according to an embodiment of the present invention.
2 is a relationship diagram showing the generation state of the first main block and the first sub-block of the hierarchical block chain system for sharing large-capacity information according to an embodiment of the present invention.
3A and 3B are block diagrams showing a record structure of a lower block transaction and a lower block header of a hierarchical block chain system for sharing large-capacity information according to an embodiment of the present invention.
4 is a block diagram illustrating a block generation rule of a hierarchical block chain system for sharing large-capacity information according to an embodiment of the present invention.
5A and 5B are block diagrams showing a record structure of a main block transaction and a main block header of a hierarchical block chain system for sharing large-capacity information according to an embodiment of the present invention.
6 and 7 are flowcharts illustrating a method of searching for a lower block transaction of a hierarchical block chain system for sharing large-capacity information according to an embodiment of the present invention.
8 is a relationship diagram showing the structure of a hierarchical block chain of the first main block and the first sub-block of the hierarchical block chain system for sharing large-capacity information according to an embodiment of the present invention.

The specific aspects and specific technical features of the present invention will become more apparent from the following detailed description and embodiments in conjunction with the accompanying drawings. In the present specification, in adding reference numerals to the components of each drawing, it should be noted that the same components are given the same reference numerals as possible even though they are indicated on different drawings. In addition, in describing an embodiment of the present invention, if it is determined that a detailed description of a related well-known configuration or function may obscure the gist of the present invention, the detailed description thereof will be omitted.

In addition, in describing the components of the present invention, terms such as first, second, A, B, (a), (b), etc. may be used. These terms are only for distinguishing the elements from other elements, and the essence, order, or order of the elements are not limited by the terms. When a component is described as being “connected”, “coupled” or “connected” to another component, the component may be directly connected to or connected to the other component, but another component may exist between each component. It should be understood that elements may be “connected,” “coupled,” or “connected.”

Hereinafter, an embodiment of the present invention will be described in detail based on the accompanying drawings.

1 and 2, the hierarchical block chain system for sharing large-capacity information according to an embodiment of the present invention is a main ledger ( 1 ; Main Ledger), a sub-ledger (2 ; Sub Ledger) containing the first sub-block 20 and one or more sub-blockchains 21, and are connected to the main ledger (1) and sub-ledger (2), respectively. It includes a node (3; Node) that shares information and a subject (4; Entity) connected with the lower ledger 2 to record transaction or event information included in the lower block chain 21 .

The main ledger 1 consists of an initial main block 10 and one or more main block chains 11, and has a structure that is connected to the first node 3 in the initial main block (and main block chain 11), respectively. can be done

The first main block 10 is a block first generated in the block chain, and includes authentication information including the signature and public key of the first generated subject 4, and is the first generated block after being generated in the first main block 10 The subject (4) can define the form or event and ID of the subject that can be created in advance through the digital signature, and through this, the ID (or address) of the subjects corresponding to the components of the block chain. can be verified.

This initial main block 10 can create the subject 4 through either a passive method or an active method.

The passive method is a method that allows participation in the recently created block chain of the subject 4 only when an approved transaction or event is generated through the electronic signature of the subject 4, and the active method is a method in which the self-generated subject 4 including the public key can participate in the main block chain 11 along with the creation of the sub block chain 21 .

When the first main block 10 is created by selecting either the passive method or the active method, the ID of the subject 4 designated in advance can be specified by the subject 4 created first by signing the subject 4 in advance. and may include the internal network IP band of a specific organization or the ID of an employee registered in advance. Based on elements such as files, users, and PCs, it is possible to participate in the sub-ledger 2 through the approved verification transaction of the first main block 10 in the ecology mapped to the IP, which is the subject ID.

In addition, in both passive and active methods, when there is a non-reliable malicious attack from the trusted subject (4), system reliability can be secured for less than 51% tampering like general BFT (Byzantine Fault Tolerance) verification. , when using points, mileage, and virtual currency according to the transaction type, the creation of a new subject can be created without limitation, including the initially created subject 4 and the authentication value of the block connected thereto.

The sub-ledger 2 includes the first sub-block 20 and one or more sub-block chains 21 as described above, and the sub-block generated in the sub-ledger 2 is defined as the first sub-block 20 When an event or transaction is completed in the sub-block 20, or an event or transaction occurs from a new subject 4, the existing first sub-block 20 is changed to the lower block chain 21, and the new first sub-block 20 ) can be created.

At this time, the sub-ledger 2 is connected to the second node 5, and the data stored in the sub-ledger 2 can be stored in IFS or DB (6, 30), and the data stored in the second node (5) is It can act as a node.

This sub-block chain 21 is a sub-block transaction 23 and one or more sub-block transactions that generate detailed transaction records based on the nature and transaction type of the event when the subject 4 generates a transaction of a specific event. It includes a lower block header 22 that can check the accumulated result values of transactions and events that have occurred between objects based on detailed information on (23) and summary information on the sum of accumulated events or transactions.

As shown in FIG. 3A , the lower block transaction 23 includes version information, the overall length of the lower block header 22, the identification ID of each subject 4, transaction ID, and detailed transaction information, and detailed transaction information may be created in the form of a record including the transaction date and time, transaction value, event or transaction type, and event or transaction information. Additional executable scripts may be included.

In addition, when at least one or more of the data included in the detailed transaction information needs to be connected to an external IP or equipment, or when one or more sub-block transactions 23 are stored for a certain amount or more and more than a certain amount of data is stored, the distributed file structure (IFS ; Interplanetary File System) or a database (DB) can be stored separately.

In addition, if it is necessary to back up a part of the detailed transaction information included in the sub-block transaction 23, or if it is determined that somewhat complicated and detailed information is important, it may be stored and stored in the above IFS or DB (6, 30), An access path including a peer address, a uniform resource locator (URL), and a uniform resource identifier (URI) may be recorded in the transaction information of the detailed transaction information.

As shown in Fig. 3b, the lower block header 22 includes version information, the total length of the lower block header 22, hash verification values for the IDs of the previous lower block transaction 23 and the current lower block transaction, It may include hash values of all fields constituting the lower block header 22, hash values for the lower block transaction 23 ID, detailed information, and summary information.

In the summary information, information including a summary value of the total of events or transactions that have occurred cumulatively in the detailed information may be recorded.

Detailed information includes information including Merkle Root ID, ID of the original entity (4) and target entity (4), the number of transactions included in the sub-block transaction, the creation timestamp of the sub-block transaction, and the timeslot value. can be recorded.

That is, when a large amount of sub-block transactions 23 are generated, the summary information of the corresponding event may be configured differently depending on the type (transaction or event) of the subject 4, and the total number of events or the transaction amount The total may be recorded in the summary information.

Even within the period of the timeslot, if different subjects (or events) occur in the sub-block transaction 23, the sub-block chain 21 generates detailed transactions between the same subjects based on the block generation rule as one sub-block chain 21, A lower block header 22 included in the block chain 21 may be additionally created. Among the above contents, the block generation rules will be described in detail with the accompanying drawings.

As shown in Fig. 4a, the block generation rule is based on the generation rule for each time slot that creates a block (sub-block transaction) in which an event or transaction is recorded for a certain period of time during which a transaction with the same transaction target subject is maintained in the lower block chain. blocks can be created.

In addition, the generation rule for each time slot indicates that the information recorded in the lower block transaction 23 is transferred to the lower block chain ( 21), and thereafter, it can be divided and recorded into the lower block header 22 and the lower block transaction 23.

In addition, the block generation rule is a basic rule as a generation rule for each time slot, but additional blocks can be additionally generated through the generation rule for each transaction subject.

When a block is created according to the generation rule for each timeslot described above, the period of the timeslot designated in the first main block 10 is differentially generated according to the generation time of the node 3 generating the lower block chain 21, When the transaction of the block chain 21 is transmitted to the main block chain 11, the configuration time and included transactions of the nodes constituting the first main block 10 may be generated differently depending on the network location and configuration.

In addition, the initial main block 10 corresponds to the error tolerance standard by preferentially adopting the lower block header 22 included in the lower block chain 21 that contains a large amount of transactions compared to the timeslot based on key validity. reliability can be ensured.

As shown in Fig. 4b, the creation rule for each transaction subject is a rule that creates a block in which an event or transaction is recorded for each subject when an event or transaction for each other subject occurs in a sub-block transaction, and is based on the creation rule for each time slot. This is an additional rule that can be applied.

That is, the block generation rule in the present invention can generate a block only with the generation rule for each time slot, and can generate a block with a rule to which the generation rule for each time slot and the generation rule for each transaction subject are applied together.

1 to 4, when one or more individually configured first sub-blocks 20 are generated from the node 3, the time based on the generation rule for each time slot among the generated sub-block transactions 23 It is generated as a lower block transaction 23 including the same detailed transaction information as the slot period, and detailed transaction information not identical to the timeslot period is withheld from the lower initial block including the detailed transaction information, and in the subsequent timeslot period It can be re-examined to determine whether it is the same as the timeslot period or not.

On the other hand, as shown in FIGS. 1 and 2 , the main block chain 11 is the main block transaction 13 and the main block transaction 13 provided with the lower block header included in the lower block chain 21 . It may include a main block header 12 capable of receiving a part of detailed information included in , and confirming accumulated result values of transactions and events occurring between the lower block headers 22 based on this.

As shown in FIG. 5A , the main block transaction 13 receives the information of the lower block header 22 and records the information of the lower block header 22 , in detail, the subject connected to the lower block header 22 . Information recorded in the lower block header 22 may be transmitted through (4) and the node (3).

Specifically, the main block transaction 13 includes version information, hash verification values for IDs of the previous main block transaction and the current main block transaction 13, hash values of all fields constituting the main block transaction 13, Information including a hash value, detailed information, summary information, and the total length of the detailed information for the ID of the lower block transaction 23 included in the lower block chain 21 may be recorded.

In addition, as the summary information, information including a summary value of the total of events or transactions that have occurred cumulatively in the detailed information may be recorded.

Detailed information includes information including Merkle Root ID, ID of the original entity (4) and target entity (4), the number of transactions included in the sub-block transaction, the creation timestamp of the sub-block transaction, and the timeslot value. can be recorded.

This main block transaction 13 can be provided through the node 3 connected to the lower block header 22, and the node that has received the transaction of the lower block header 22 to be delivered to the main block chain 11 (3) The total number of transactions of one or more sub-block transactions 23 included in the sub-block header 22 and the IDs of the transactions can be traced back to inquire the transaction details, and whether there are actual transactions through extraction of the entire hash And it is possible to verify the reliability and integrity of the lower block header 22 for a rather complex transaction or event, such as content integrity and whether there is a transaction using the Merkle tree.

Among the above methods, the main block transaction (or sub-block header) with an error in integrity may be excluded.

That is, the main block transaction 13 records the information of the lower block header 22 of the lower block chain 21, even if the lower block chain 21 is abnormal or file corruption occurs due to an error occurring from the outside. Transactions of the lower block chain 21 can be searched through detailed information and summary information of the main block transaction.

As shown in FIG. 5B , in the main block header 12, information including version information, the total length of the main block header 12, identification ID of each subject, transaction ID, and detailed transaction information may be recorded.

In the detailed transaction information, a transaction date and time, transaction value, event or transaction type, event or transaction information may be recorded.

As shown in FIGS. 6A and 6B , the search method of the lower block transaction 23 included in the lower block chain 21 inquires the node 3 and the subject 4 for transaction information to be searched through the protocol. It may include an indirect inquiry method and a direct inquiry method in which the main block chain 11 requests transaction information from one or more subjects 4 connected to the lower block chain 21 to directly inquire detailed transaction details.

First, the indirect inquiry method will be described in detail with reference to FIG. 6A. When detailed information of the corresponding event and transaction is required for the main block chain 11, the subject 4 corresponding to the ID is detailed through the corresponding transaction ID. Request information, and the subject 4 inquires detailed transaction information in the lower block chain 21 .

At this time, if there is an externally stored DB or IFS(6,30) file, the above-mentioned subject inquires the externally stored DB or IFS(6,30) information, and sends the information required for inquiry to the requesting node ( 3) is provided.

As described above, the indirect inquiry method is not a direct inquiry request to the lower block chain 21, but a method of receiving information through a protocol to a node and a subject.

The direct inquiry method will be described in detail with reference to FIG. 6b. When detailed information of the corresponding event and transaction is required for the main block chain 11, the subject 4 corresponding to the ID of the main block chain 11 is provided. The transaction ID is inquired, and the sub-blockchain 21 corresponding to the detailed information is specified and inquired based on the inquired ID.

At this time, if an externally stored file (IFS) or DB (6, 30) exists, the node (3) can directly inquire the file and DB information, and can inquire through the protocol of the second node (3). have.

As described above, the direct inquiry method minimizes indirect communication with the node 3 and the subject 4, and asks each subject to inquire the initial main block 10 and the sub-block chain 21 by itself. By requesting and receiving (21), the detailed transaction details can be directly inquired.

In the case of inquiring a partial transaction rather than a method that requires the entire transaction summary information of the lower block chain 21, such as the indirect inquiry method and the direct inquiry method, as shown in FIG. 7, the corresponding transaction ID through the partial inquiry method You can extract some of them.

In the partial inquiry method, the transaction count and timeslot included in the summary information of the lower block header 22 are inquired, and the transaction ID of the timeslot period in which the time difference from the previous lower block header 22 occurs based on the time at which the transaction occurred is retrieved. It is a method of inquiring and collecting the inquired transaction ID through the protocol.

1 and 8, the structure of the hierarchical block chain including the main block chain 11 and the lower block chain 21 will be described in more detail.

The first main block 100 generates a subject 4 including authentication information, and based on the created subject 4, the first sub-block 200 can be created, and the first sub-block 200 is a subject. When the transaction or event carried out from (4) ends, the first sub-block 200 may be recorded as the sub-block chain 210 .

The information of the sub-block chain 210 is complicated or information that needs to be backed up can store the sub-block transactions included in the sub-block chain 210 by interworking with the external system 400, and the external system 400 is the IFS It refers to an external storage server including (Interplanetary File System) or DB (Data Base).

Here, the subject 4 generated from the first main block 100 may generate the subject 4 by selecting either a passive method or an active method, and the subject 4 generated from the first sub-block 200 also It can be produced in one of the ways described above.

In addition, in the first main block 100, when a transaction or event from the subject 4 is terminated and another subject 4 is generated for the first main block 100, the block generation rules (generation rules for each time slot) Alternatively, another initial sub-block 201 may be generated based on the generation rule for each transaction subject).

Another first sub-block 201 is created in the same structure as the first sub-block 200 described above, and when a transaction or event with the first sub-block 201 is ended, the first sub-block 201 is a sub-block chain 220 can be changed to

For example, when the subject 4 is generated in the first sub-block 201, the second initial sub-block 300, which is a sub-block of the first sub-block 201, may be generated, and in this case, the first sub-block 201 is the second 2 It can be recognized as an upper block from the first lower block 300 . That is, from the perspective of the second initial sub-block 300, the first sub-block 201 may be recognized as the main block chain.

The second first sub-block 300 is recorded as the second sub-block chain 301 when the transaction or event with the subject is terminated, and the second sub-block header 302 included in the second sub-block chain 301 is It can be recorded as the lower block transactions 223 and 302 of the lower block chain 220 .

The second lower block chain 301 is a so-called hierarchical block chain structure in which information is recorded in the lower block chain 220 of the upper block, and the lower block chain 220 is recorded in the main block chain 101. is done

That is, even if the block chain belonging to the lower ledger is errored or deleted, the total amount of events or transactions of the subject that occurred within the timeslot cycle included in the upper ledger can be verified. Information can be determined, or file backup and user action logs can be determined.

Although the present invention has been described in detail through one embodiment, this is for describing the present invention in detail, and the hierarchical block chain system for sharing large-capacity information according to the present invention is not limited thereto. And, terms such as "include", "comprise", or "have" described above mean that the component may be embedded unless otherwise stated, so excluding other components is It should be construed as being able to further include other components rather than other components, and all terms including technical or scientific terms are generally understood by those of ordinary skill in the art to which the present invention belongs, unless otherwise defined. has the same meaning as being

In addition, the above description is merely illustrative of the technical idea of the present invention, and various modifications and variations are possible by those skilled in the art to which the present invention pertains without departing from the essential characteristics of the present invention. Accordingly, one embodiment disclosed in the present invention is not intended to limit the technical spirit of the present invention, but to explain, and the scope of the technical spirit of the present invention is not limited by this one embodiment. The protection scope of the present invention should be construed by the following claims, and all technical ideas within the scope equivalent thereto should be construed as being included in the scope of the present invention.

1 - Primary Ledger 2 - Sub Ledger
3 - first node (node) 4 - principal
5 - 2nd node 6 - IFS/DB
10 - first main block 11 - main block chain
12 - main block header 13 - main block transaction
14 - Main block transaction 20 - First sub-block
21 - sub block chain 22 - sub block header
23 - Sub-block transaction 30 - IFS / DB
100 - first main block 101 - main block chain
102 - main block header 103 - main block transaction
104 - Main block transaction 200 - First sub-block
201 - first sub-block 210 - sub-blockchain
220 - sub block chain 221 - sub block header
222 - sub-block transaction 223 - sub-block transaction
300 - 2nd first sub-block 301 - 2nd sub-blockchain
302 - 2nd sub-block header 303 - 2nd sub-block transaction
400 - IFS/DB

Claims (20)

Main Ledger containing the original main block and one or more main blockchains;
Sub Ledger containing the initial sub-block and one or more sub-blockchains;
a node including at least one first node that is created to be connected with the main ledger and shares the main ledger and a second node that is created to be connected with the lower ledger and shares the lower ledger;
one or more entities connected to the lower ledger to record transaction or event information included in the lower block chain and sharing the transaction address function of the lower block chain and the lower block chain;
A hierarchical blockchain system for sharing large amounts of information, including
The method of claim 1 .
A manual method that allows a new subject to participate in the blockchain only when an approved transaction or event is generated through the subject's electronic signature; and
an active method in which a self-generated subject including a public key can participate in the main block chain together with the sub block chain generation; includes,
The first main block is a hierarchical block chain system for large-capacity information sharing that creates the subject through either the passive method or the active method.
The method according to claim 1,
The sub-block chain includes a sub-block transaction that generates a detailed transaction record based on the nature and transaction type of the event when the subject generates a specific event transaction; and
a sub-block header capable of confirming the accumulated result values of transactions and events that have occurred between objects based on detailed information on one or more of the sub-block transactions and summary information on accumulated events or total transactions;
A hierarchical blockchain system for sharing large amounts of information, including
4. The method according to claim 3,
A hierarchical block chain system for large-capacity information sharing that generates the sub-block transaction with a time slot-specific generation rule that creates a block in which an event or transaction is recorded for a certain period of time during which a transaction with the same transaction target subject is maintained in the sub-block chain.
5. The method according to claim 4,
a generation rule for each transaction entity that generates a block in which an event or transaction is recorded for each entity when an event or transaction for each other entity occurs in the sub-block transaction; includes,
In the lower block transaction, a block is generated based on the generation rule for each time slot, and the block is generated including the generation rule for each transaction subject.
4. The method according to claim 3,
The sub-block transaction includes version information, the total length of the sub-block header, each subject identification ID, transaction ID, and detailed transaction information,
The detailed transaction information is a hierarchical block chain system for sharing large-capacity information including transaction date and time, transaction value, event or transaction type, and event or transaction information.
7. The method according to claim 5 and 6,
When one or more individually configured lower initial blocks are generated from the node, the lower initial block including the detailed transaction information equal to the timeslot period based on the generation rule for each timeslot from among the generated lower block transactions is set to the lower level. It is created by block transaction,
A hierarchical block chain system for sharing large-capacity information in which the lower initial block including the detailed transaction information that is not the same as the timeslot period is withheld and reviewed at a subsequent timeslot period.
7. The method of claim 6,
When at least one or more of the data included in the detailed transaction information needs to be connected to the outside, or if more than a certain amount of data of one or more sub-block transactions is stored, an Interplanetary File System or a database (DB) ), a hierarchical blockchain system for sharing large amounts of information.
9. The method of claim 8,
After storing in the distributed file structure or database, the sub-block transaction is a large-capacity information sharing that records an access path including a peer address, URI, and URL to the stored distributed file structure or database in the detailed transaction information hierarchical blockchain system for
4. The method according to claim 3,
The lower block header includes version information, the total length of the lower block header, hash verification values for IDs of previous and current lower block transactions, hash values of all fields constituting the lower block header, and lower block transactions. Includes hash value, detailed information and summary information for ID,
The summary information is a hierarchical block chain system for sharing large-capacity information including a summary value of the total sum of events or transactions that have occurred accumulated in the detailed information.
11. The method of claim 10,
The detailed information is a layer for sharing large-capacity information including Merkle Root ID, IDs of the principal and target subjects, the number of transactions included in the sub-block transaction, the creation timestamp of the sub-block transaction, and the timeslot value. blockchain system.
The method according to claim 1,
The main block chain includes a main block transaction provided with a lower block header included in the lower block chain; and
a main block header capable of receiving a part of detailed information included in the main block transaction and checking the accumulated result values of transactions and events occurring between the lower block headers based on this;
A hierarchical blockchain system for sharing large amounts of information, including
13. The method of claim 12,
The main block header includes version information, the total length of the main block header, each subject identification ID, transaction ID, and detailed transaction information,
The detailed transaction information is a hierarchical block chain system for sharing large-capacity information including transaction date and time, transaction value, event or transaction type, and event or transaction information.
13. The method of claim 12,
The main block transaction includes version information, hash verification values for IDs of previous and current main block transactions, hash values of all fields constituting the main block transaction, and sub-block transactions included in the sub-block chain. A hierarchical blockchain system for sharing large-capacity information including hash values for IDs, detailed information, summary information, and the total length of the detailed information.
15. The method of claim 14,
The detailed information includes a Merkle Root ID, the number of transactions included in the main block transaction, a creation timestamp of the main block transaction, and a timeslot value. A hierarchical block chain system for sharing large amounts of information.
The method according to claim 1,
The search method of the lower block transaction included in the lower block chain includes an indirect inquiry method of inquiring the transaction information to be searched for through a protocol to the node and the subject;
a direct inquiry method in which the main blockchain requests transaction information from one or more subjects connected to the sub-blockchain to directly inquire detailed transaction details; and
a partial inquiry method of inquiring partially occurring transactions by inquiring the transaction count and timeslot included in the summary information of the lower block header;
A hierarchical blockchain system for sharing large amounts of information, including
17. The method of claim 16,
The indirect inquiry method verifies the ID and target ID of the subject included in the specific event and transaction of the main block chain that the first node wants to inquire, and displays the total number of events and total transaction summed up in the event and transaction. A hierarchical blockchain system for large-capacity information sharing that confirms, collects the above information, and provides the collected information to the first node that requested inquiry.
17. The method of claim 16,
The direct inquiry method is a hierarchical block chain system for large-capacity information sharing that requests a sub-block transaction to be inquired from one or more of the subjects connected to the sub-block chain, and provides detailed transaction details requested in the sub-block transaction to the subject. .
3. The method according to claim 1 and 2,
The first main block creates the subject including authentication information, creates the first sub-block based on the subject, and the subject creates the sub-block chain based on the first sub-block. hierarchical blockchain system for
20. The method of claim 19,
In the first sub-block, when a sub-subject for the first sub-block is generated, the first sub-block is recognized as the first main block, and the first sub-block recognized as the first main block is the second first based on the sub-subject A hierarchical blockchain system for sharing large amounts of information that creates sub-blocks.

Images