Configuration of distributed processing system and asset transaction method

Abstract

The present invention relates to a configuration of a distributed processing system and an asset transaction method and, more specifically, to a configuration of a distributed processing system and an asset transaction method, wherein asset transactions of users are processed using a plurality of distributed ledgers, so as to significantly improve data processing performance, asset transactions between users belonging to different groups are provided in a transparent and consistent method through a delegator, and all necessary transactions are recorded in a double-entry bookkeeping manner to ensure completeness and accuracy of asset transaction records.

Description

Distributed processing system configuration and asset transaction method

[0001] The present invention relates to a configuration of a distributed processing system and an asset transaction method, and more specifically, to a configuration of a distributed processing system and an asset transaction method that improves scalability and performance for processing large-scale data by dividing users' asset transactions into multiple distributed ledgers and processing them in parallel, and maintains transparency and consistency of transactions by processing asset transactions between users belonging to different groups through delegates.

[0002] Distributed ledger technology is a technology that allows distributed network participants to jointly manage a ledger that verifies and agrees on transaction information using cryptographic technology.

[0003] This distributed ledger technology limits the use of a central administrator or central data storage, and to ensure the reliability of data management, all participants (peers) within the distributed network must attach an electronic signature to transactions, and after going through a process of reaching an agreement on the contents, they replicate and share them with each other.

[0004] Representative examples of distributed ledger technology include blockchain and directed acyclic graph (DAG), which connects transactions like a net.

[0005] While blockchain only allows for a single block connection through pruning, DAG distributed ledger technology allows for simultaneous connection of events originating from network participants.

[0006] Blockchain platforms include Ethereum and Hyperledger, and DAG distributed ledgers include Germany's IOTA (Internet of Things Application) project Hashgraph.

[0007] Meanwhile, distributed ledger technology is considered a promising technology for reducing the cost of trust. However, it still falls significantly short of existing centralized systems in areas such as confidentiality, scalability, and interoperability. These issues increase system construction and operating costs, thus offsetting the benefits.

[0008] In particular, conventional blockchains have limited processing speeds and are difficult to scale, making them difficult to apply to large-scale services for enterprises or public institutions that require efficient processing of large volumes of transactions.

[0009] [Prior Art Literature]

[0010] [Patent Document]

[0011] Korean Patent No. 10-2460432, 'RDBMS-based Distributed Ledger Management System and Method'

[0012] Korean Patent No. 10-2097995, "Electronic Payment System and Payment Method for Preventing Double Payments"

[0013] Korean Patent No. 10-2511570, 'Method, device, system, method, and computer-readable storage medium for processing blockchain network processes.'

[0014] The present invention has been devised to solve the above-described problems, and the purpose of the present invention is to provide a configuration of a distributed processing system and an asset transaction method that can significantly improve the scalability and performance of distributed processing compared to a single distributed ledger by dividing the distributed ledger into multiple shards and processing them in parallel.

[0015] In addition, another object of the present invention is to provide a configuration of a distributed processing system and an asset transaction method that can maintain the transparency and consistency of transactions by processing asset transactions between users belonging to different groups through a delegate.

[0016] In addition, another object of the present invention is to provide a configuration of a distributed processing system and an asset transaction method that ensures the integrity, reliability, transparency, and processing efficiency of asset transactions by recording all transactions using double-entry bookkeeping.

[0017] In order to achieve the above object, the present invention provides a distributed processing system for recording and processing asset transaction (hereinafter, 'remittance') details for a plurality of users in a distributed ledger format, and an asset transaction method, comprising: a) a step of grouping the users by classification criteria including the region of residence, age, or reception location, and dividing the distributed ledger for each group to form a divided distributed ledger; b) a step of forming distributed ledger networks composed of a plurality of nodes that record each divided distributed ledger as an identical copy; c) a step of designating and forming a consensus node for each distributed ledger network that assigns a transaction order to transaction messages generated within the distributed ledger networks and distributes them equally to each node; d) a step of forming a delegate node so as to record remittance details between different distributed ledger networks; e) a step of forming a distributed ledger network group in which all distributed ledger networks are connected; And f) a step of configuring a distributed processing system and an asset transaction method with improved performance compared to a single distributed ledger network, including a step of configuring a user to perform in-house transactions (transactions with users within the same group) and out-house transactions (transactions with users in different groups) through a distributed ledger network of the group to which the user belongs.

[0018] In a preferred embodiment, the method comprises the steps of: creating a shard map for managing which distributed ledger network each user belongs to in each node of all distributed ledger networks; a step for a user to access a specific distributed ledger network and request registration including personal information; a step for grouping users by specific categories (such as region, age, or reception center) and recording which group each user belongs to in the shard map; and a step for replicating the ledger map information of the user newly recorded in the shard map to all nodes of all distributed ledger networks.

[0019] In a preferred embodiment, the segmented distributed ledger is composed of a current transaction ledger that records the history of asset movement within the distributed ledger network to which the user belongs, and a third-party deposit ledger that records the history of asset movement to another distributed ledger network to which the user does not belong, and the current transaction ledger includes a transaction identifier that distinguishes whether it is a current transaction or a third-party transaction, a group to which the sender belongs, the sender account, the remittance amount, the group to which the recipient belongs, the recipient account, etc., and is recorded in a double-entry bookkeeping format, and when the transaction identifier is a third-party transaction (when the recipient belongs to a different distributed ledger network), a delegator account is additionally recorded, and the third-party deposit ledger always records the delegator account, and is recorded in a double-entry bookkeeping format including the group to which the sender belongs, the sender account, the remittance amount, the group to which the recipient belongs, the recipient account, etc., and the current transaction ledger and the third-party deposit ledger separately calculate and record the final balance of the account when each transaction occurs.

[0020] In a preferred embodiment, the consensus node provided for each distributed ledger network assigns a transaction order to transaction messages (performs consensus) only for transactions of the partitioned distributed ledger that must be processed in the distributed ledger network to which it belongs, and propagates (replicates) the transaction messages to nodes in the distributed ledger network to which it belongs, thereby allowing the consensus execution of the consensus node to be processed in parallel.

[0021] In a preferred embodiment, the system grants the delegatee the authority to process delegated transactions, the delegatee creates his / her own account on all distributed ledger networks, and deposits a deposit on all distributed ledger networks that allows him / her to perform delegated transactions.

[0022] In a preferred embodiment, the method comprises the steps of: a user composing a remittance message through a user terminal and submitting the remittance message to a distributed ledger network to which the user belongs; a node receiving the remittance message transmitting the remittance message to a consensus node designated to perform consensus in the distributed ledger network to which the node belongs; a consensus node collecting the remittance message determining whether the collected remittance message originated from the distributed ledger network to which it is designated; a step of assigning (agreeing on) a transaction order and disseminating the same to all nodes through a message distributor if the remittance message transmitted to the consensus node originated from the distributed ledger network to which it is designated; and a step of the node receiving the remittance message with the assigned transaction order recording the remittance message in a transaction ledger.

[0023] In a preferred embodiment, when composing a remittance message, if the recipient belongs to the same distributed ledger network as the sender, the transaction identifier is indicated as the current bank, and if the recipient belongs to a different distributed ledger network, the transaction identifier is indicated as another bank, and the remittance message is submitted to the distributed ledger network, and a node receives a transaction message with transaction sequence information from a consensus node and records it in the current bank transaction ledger through a data manager, and the data manager updates the accumulated balance data so that the sender's balance decreases and the receiver's balance increases when the transaction identifier of the transaction message is the current bank, and updates the accumulated balance data so that the sender's balance decreases and the delegator's balance increases when the transaction identifier is another bank.

[0024] In a preferred embodiment, the method comprises the steps of: a delegator searching for a new transaction in the current transaction ledger in which the transaction identifier is another bank and the delegator account is his / her own; a delegator generating a delegation transaction message by referencing group information to which the sender belongs in the searched transaction; a delegator submitting the generated delegation transaction message to a distributed ledger network to which the sender belongs; a node receiving the delegation transaction message transmitting the delegation transaction message to a designated consensus node; a consensus node determining whether the received delegation transaction message originated from the distributed ledger network to which it is designated; a consensus node assigning (agreeing on) a transaction order to the delegation transaction message and disseminating it to all nodes through a message distributor; a node receiving the delegation transaction message from the consensus node recording the message in the other bank deposit ledger through a data manager; and a data manager determining that the message is a delegation transaction message, decreasing the delegator's balance, and updating the accumulated balance data so that the recipient's balance increases.

[0025] The present invention has the following excellent effects.

[0026] First, according to the configuration of the distributed processing system and the asset transaction method of the present invention, the distributed ledger is divided (sharded) into groups of different categories and processed in parallel, thereby greatly improving the speed of distributed processing compared to a single distributed ledger.

[0027] In addition, according to the configuration of the distributed processing system and the asset transaction method of the present invention, there is an advantage in that asset transactions between different groups can be performed transparently and safely through a delegate.

[0028] In addition, according to the configuration of the distributed processing system and the asset transaction method of the present invention, since the current bank remittance and other bank deposit can be recorded in double-entry bookkeeping format, the balance of each account and the total balance can be accumulated and managed whenever a transaction occurs, so there is an advantage of simplifying the calculation of the balance and increasing the operation speed.

[0029] Figure 1 is a drawing showing the configuration of a distributed processing system according to one embodiment of the present invention;

[0030] FIG. 2 is a drawing for explaining a shard map of a distributed processing system according to one embodiment of the present invention.

[0031] FIG. 3 is a drawing for explaining the creation of a delegate account in a distributed processing system according to one embodiment of the present invention;

[0032] FIG. 4 is a drawing for explaining the current transaction ledger of a distributed processing system according to one embodiment of the present invention;

[0033] FIG. 5 is a drawing for explaining a deposit ledger of a distributed processing system according to one embodiment of the present invention.

[0034] FIG. 6 is a diagram for explaining a process of calculating the balance per account and the total balance in the current transaction ledger of a distributed processing system according to one embodiment of the present invention.

[0035] FIG. 7 is a diagram for explaining a process of calculating the balance per account and the total balance in the current bank transaction ledger and the other bank deposit ledger of a distributed processing system according to one embodiment of the present invention.

[0036] <Explanation of symbols>

[0037] 1000: Distributed Processing System 1100: Distributed Ledger Network Group

[0038] 1110: Distributed Ledger Network 1120: Node

[0039] 1121: Message Collector 1122: Message Subscriber

[0040] 1123: Data Manager 1124: Ledger Allocation Table

[0041] 1125: Distributed Ledger 1126: Current Transaction Ledger

[0042] 1127: Other Bank Transaction Ledger 1128: Balance Accumulation Data

[0043] 1200: User group 1210: User terminal

[0044] 1211: User Registration Manager 1212: Remittance Message Manager

[0045] 1300: Consensus Node Group 1310: Consensus Node

[0046] 1311: Single Message Collector 1312: Consensus Generator

[0047] 1313: Transaction message with transaction order assigned 1314: Message distributor

[0048] 1400: Delegate Group 1410: Delegate Node

[0049] 1411: Transaction Inquirer 1412: Delegated Message Manager

[0050] The terms used in the present invention are selected from the most widely used general terms as much as possible, but in certain cases, there are terms arbitrarily selected by the applicant. In such cases, the meaning of the terms should be understood by considering the meaning described or used in the detailed description of the invention, rather than the simple name of the term.

[0051] Hereinafter, the technical configuration of the present invention will be described in detail with reference to preferred embodiments illustrated in the attached drawings.

[0052] However, the present invention is not limited to the embodiments described herein and may be embodied in other forms. Like reference numbers designate like elements throughout the specification.

[0053]

[0054] FIG. 1 is a drawing showing the configuration of a distributed processing system according to one embodiment of the present invention.

[0055] Referring to FIG. 1, a distributed processing system (1000) according to one embodiment of the present invention is a system capable of distributing and parallel processing of users' asset transactions through a distributed ledger (1125) divided by group, and has the advantage of being able to significantly increase processing speed by using a distributed ledger (1125) divided by group compared to a system that performs asset transactions using a conventional single distributed ledger.

[0056] In addition, the distributed processing system (1000) includes a distributed ledger network group (1100), a consensus node group (1300), and a delegate group (1400), and a user group (1200) accesses the distributed ledger network group (1100) to perform asset transactions.

[0057] The above distributed ledger network group (1100) is composed of multiple distributed ledger networks (1110) that are interconnected and classify users into specific categories (classification criteria).

[0058] In addition, the above categories are classification criteria such as the region where users live, age, or reception location, and may include various classification criteria such as the date of registration in addition to the examples mentioned above.

[0059] Referring to FIG. 2, a detailed description is provided. FIG. 2 is for explaining a ledger allocation table (1124) of the distributed ledger network (1110). When users register for a transaction, they are grouped by classification criteria such as region, age, or reception location to form a ledger allocation table (1125a, 1125b, 1125c).

[0060] However, in addition to the above-mentioned category examples, a segmented ledger allocation table can be created by classifying groups based on various classification criteria, such as the year of subscription to the service.

[0061] Here, the term 'group' means a set of users to be processed within the same distributed ledger network, and is distinct from the 'group' of a distributed ledger network group (1100) formed by a collection of distributed ledger networks (1110).

[0062] Also, when grouping users by region, users residing in Seoul can be classified as 'group 1' and users residing in Gyeonggi-do can be classified as 'group 2'. When grouping by age, users born in that year can be grouped together, and when grouping by application location, people who applied through that bank can be grouped together.

[0063] Additionally, asset transactions of users of different groups in the above-mentioned ledger allocation table (1125a, 1125b, 1125c) are processed through the distributed ledger (1125) of different distributed ledger networks (1110).

[0064] For example, users who applied through Bank A can be grouped into 'group1', and users who applied through Bank B can be grouped into 'group2' and processed on different distributed ledger networks.

[0065] That is, the distributed ledgers (1125) between the distributed ledger networks are different from each other, and the ledger allocation table (1124) is the same.

[0066] This configuration is the biggest difference compared to a conventional single distributed ledger network, as it allows each group to have a different, partitioned distributed ledger, which can improve transaction processing capacity.

[0067] Additionally, each of the above distributed ledger networks (1110) is composed of multiple nodes (1120) that record copies of the same distributed ledger.

[0068] In other words, nodes in a single distributed ledger network record copies of the same distributed ledger, ensuring that the distributed ledger has the same information when trading assets.

[0069] Additionally, a ledger allocation table (1124) is created in each node (1120) to manage which distributed ledger network the users belong to, and the ledger allocation tables (1124) created in each node of all distributed ledger network groups are identical to each other.

[0070] In addition, the above-mentioned ledger allocation table (1124) and the above-mentioned distributed ledger (1125) are managed by a data manager (1123) of a node (1120), and the above-mentioned distributed ledger (1125) is composed of a current transaction ledger (1126) that records the history of asset movement within the distributed ledger network to which it belongs, and a foreign deposit ledger (1127) that records the history of asset movement to another distributed ledger network to which it does not belong.

[0071] In addition, Fig. 4 is a drawing for explaining the current transaction ledger (1126) and shows one example (1126a) of the current transaction ledger. Referring to Fig. 4, the current transaction ledger (1126) includes a transaction identifier (transaction identifier) ​​that distinguishes whether an asset transaction is a current transaction within the same group, a group to which the sender who remits the asset belongs (sender distributed ledger identifier), the sender account, the remittance amount, the group to which the receiver who receives the asset belongs (receiver distributed ledger identifier), and the receiver account are recorded in a single ledger in a double-entry bookkeeping format.

[0072] Here, double-entry bookkeeping refers to a form in which the sender's account, recipient's account, and remittance amount are recorded on a single line.

[0073] In addition, the above transaction ledger (1126) further includes a delegate account item that records the account of the designated delegate when the group to which the sender belongs and the group to which the recipient belongs are different (see transaction ID '2').

[0074] Additionally, the above delegate account entry is recorded only when there is a delegate, and if the transaction type is a current transaction, it is recorded as 'none' (null).

[0075] Additionally, since each delegate has its own account created on each distributed ledger network, it can access the distributed ledger and check whether transactions delegated to it exist.

[0076] In addition, Fig. 5 is a drawing for explaining the interbank deposit ledger (1127) and shows an example (1127a) of the interbank deposit ledger. Referring to Fig. 5, the interbank deposit ledger (1127) records the group to which the sender belongs (sender distributed ledger identifier), the sender account, the delegate account, the remittance amount, the group to which the recipient belongs (recipient distributed ledger identifier), and the recipient account. The most important thing here is that the delegate account must be recorded.

[0077] In addition, the above-mentioned deposit ledger (1127) also records the sender's account, recipient's account, and remittance amount in a single row in double-entry bookkeeping format.

[0078] In addition, the distributed ledger (1125) is equipped with balance accumulation data (1128) that separately calculates and records the balance of each account, and the balance accumulation data is configured to calculate and store the final balance of the account when each transaction occurs.

[0079] In order to calculate the balance in a double-entry ledger, the debit and credit amounts must be calculated for every transaction of each account, so there is a problem that the calculation speed slows down as the amount of transaction history increases. Therefore, in the present invention, this problem is solved by calculating the balance for each transaction, accumulating it, and then storing it.

[0080] The above consensus node group (1300) is composed of multiple consensus nodes (1310), and each consensus node (1310) assigns a transaction order to transaction messages to be processed by each node (1120) of the distributed ledger network (1110). Here, assigning a transaction order is also referred to as consensus execution, and serves to prevent non-transfer or duplicate transmission due to errors in the transaction order at each node (1120).

[0081] In addition, the above consensus node (1310) is created to be matched one-to-one with each distributed ledger network, and only grants transaction order to transactions of the divided distributed ledger that must be processed in the distributed ledger network to which it belongs.

[0082] In addition, the consensus node (1310) can further improve transaction processing capacity by allowing the consensus execution of the consensus node to be processed in parallel by propagating (replicating) transaction messages only to each node of the distributed ledger network to which it belongs.

[0083] Additionally, multiple consensus nodes for different distributed ledger networks form a consensus node group (1300).

[0084] The above delegate group (1400) is composed of a plurality of delegate nodes (1410), and each delegate node (1410) is configured to perform asset transactions between different distributed ledger networks and record remittance details in the distributed ledger.

[0085] In addition, asset transactions cannot be made between distributed ledger networks (1110) having different distributed ledgers as in the present invention because the user information of the distributed ledgers is different. Such transactions are performed by the delegate nodes (1410), ensuring transparency and safety of asset transactions.

[0086] In addition, the delegate account used by the delegate node (1410) is recorded in the ledger allocation table (1124) of each node (1120) of all distributed ledger networks (1110), and is authorized in the system to access the distributed ledger (1125) of each node (1120).

[0087] In addition, FIG. 3 is a drawing for explaining the creation of the delegate account. Referring to FIG. 3, when a delegate accesses the distributed ledger network (1100) and requests delegate registration, a delegate account (1124d) is created in all distributed ledger networks (1100) divided by category and a delegate ID is assigned.

[0088] That is, the delegate can access all distributed ledger networks (1110) and perform asset transactions between different distributed ledger networks (1110).

[0089] Additionally, the delegate account must have sufficient funds to perform delegated transactions, and delegates with insufficient funds will not be assigned delegated transactions.

[0090] Once the distributed processing system is configured, asset transactions can be made between actual users.

[0091] Below we explain in detail the asset trading method.

[0092] First, when a user accesses the distributed ledger network (1100) through the user registration manager (1211) of the user terminal (1210) and registers as a user, the user is classified according to the set classification criteria and is included in the classified group.

[0093] Next, the user terminal (1210) constructs a remittance message through the remittance message manager (1212) and submits the remittance message to the distributed ledger network (1110) to which it belongs.

[0094] Next, the distributed ledger network (1110) collects remittance messages through the message collector (1121) of the node (1120) and transmits the remittance messages to the consensus node (1310) matched with it.

[0095] Then, the single message collector (1311) of the consensus node (1310) receives the remittance message, determines whether the received remittance message originated from the distributed ledger network (1110) to which it is assigned, and if the received remittance message originated from the distributed ledger network (1110) to which it is assigned, assigns (agrees on) a transaction order through the consensus generator (1312), generates a transaction message (1313) to which the transaction order is assigned, and propagates the generated message to all nodes of the distributed ledger network (1110) through the message distributor (1314).

[0096] Next, each node (1120) receives a remittance message with a transaction order through a message subscriber (1122) and records it in the current transaction ledger (1126) of the distributed ledger (1125).

[0097] Here, the remittance message with the transaction order is recorded identically in all nodes belonging to the distributed ledger network (1110).

[0098] In addition, in the above-mentioned current transaction ledger (1126), if the recipient is a user belonging to the same distributed ledger network as the sender, as in the transaction ID '1' of FIG. 4, the transaction identifier is recorded as current, the remittance amount '1,000' won is decreased in the sender's account 'user_a_account', and '1,000' won is increased in the recipient's account 'user_b_account', and the above-mentioned accumulated balance data (1128) is updated.

[0099] However, in transactions between different distributed ledger networks, such as transaction ID '2' in Fig. 4, where the sender belongs to 'group 1' and the recipient belongs to 'group 2', the transaction identifier is recorded as a third-party transaction. In such a third-party transaction, the asset transaction is made through the delegator, so the money is not transferred to the recipient immediately, and the sender's balance is reduced by the amount of the transfer, while the delegator's balance is increased.

[0100] In addition, in this outbound transaction, a delegate is necessarily designated and the delegate account is recorded. In the example of Fig. 4, transaction ID '2' is an outbound transaction and 'delegatee_a_account' is designated as the delegate.

[0101] Next, the delegate checks the transaction inquiry (1411) of the delegate node (1400) to see if there is a new transaction in the current transaction ledger (1126) for which he or she is designated as the delegate.

[0102] In the example of Fig. 4, when a new transaction exists, such as transaction ID '2', a delegation transaction message is created through the delegation message manager (1412) by referencing 'group2', which is the group information to which the recipient belongs.

[0103] Next, the generated delegated transaction message is submitted to the distributed ledger network (group 2) to which the sender belongs.

[0104] Next, the node (1120) that received the delegation transaction message transmits the delegation transaction message to the designated consensus node (1310), and the consensus node (1310) determines whether the delegation transaction message originated from the designated distributed ledger network.

[0105] If it is a delegated transaction message generated in a designated distributed ledger network, a transaction order is assigned to the delegated transaction message (agreement is made) and the delegated transaction message with the transaction order is propagated to all nodes of the designated distributed ledger network through the message distributor (1314).

[0106] Then, each node records the delegated transaction information in the deposit ledger (1127) through the data manager (1123).

[0107] In addition, the above delegated transaction information includes a sender distributed ledger identifier (group1), a sender account (user_a_account), a delegate account (delegatee_a_account), a remittance amount (1,000), a recipient distributed ledger identifier (group2), and a recipient account (user_c_account), as in the example of FIG. 5.

[0108] In addition, this delegated transaction information is recorded together in the interbank deposit ledger of the distributed ledger to which the sender belongs and the interbank deposit ledger of the distributed ledger to which the recipient belongs. In the distributed ledger to which the sender belongs, the sender's balance is decreased by the amount of remittance and the delegator's balance is increased by the amount of remittance to update the accumulated balance data. In the distributed ledger to which the recipient belongs, the delegator's balance is decreased by the amount of remittance and the recipient's balance is increased by the amount of remittance to update the accumulated balance data, and then the transaction ends.

[0109] Below, a method for performing balance calculation of the above balance accumulation data (1128) is described in detail with reference to FIGS. 6 and 7.

[0110] Figure 6 is a diagram for explaining the process of calculating the balance by account and total balance in the current transaction ledger (1126b).

[0111] Referring to FIG. 6, in transaction '1', 'ISSUER', a currency issuing institution, transfers '5,000' won to 'user_a_account' of 'group1', in transaction '2', 'user_a_account' of 'group1' transfers '3,000' won to 'user_b_account' of 'group2' via delegatee 'delegatee_a_account', in transaction '3', 'user_a_account' within the same group transfers '1,000' won to 'user_c_account', and in transaction '4', 'user_c_account' within the same group transfers '1,000' won to 'user__account'.

[0112] This transaction is calculated cumulatively each time a transaction occurs, and in transaction '5', a transfer request of '100' was made from 'user_b_account' to 'user_a_account', but the balance of 'user_b_account' is not confirmed, so the transaction is not completed.

[0113] Also, the balance of 'user_a_account' is '1,500' won when the '3,000' won and '1,000' won that he sent are subtracted from the '5,000' won and '3,000' won that he received. If the balance of 'user_b_account' is calculated in the same way, the balance is '0' won, and the balance of 'user_c_account' is '500' won. The total balance is the sum of the balances of each account, so it is '2,000' won.

[0114] In addition, Figure 7 is a drawing for explaining the process of calculating the balance by account and the total balance in the current bank transaction ledger (1126c) and the other bank deposit ledger (1127b).

[0115] Referring to Figure 7, the current bank transaction ledger (1126c) records transactions between accounts within the same 'group2', and the other bank deposit ledger (1127b) records that '3,000' is transferred from 'user_a_account' of 'group1' to 'user_b_account' of 'group2' via delegatee 'delegatee_a_account'.

[0116] In this case, the balances of 'user_a_account' and 'user_c_account' can be calculated in the same way using the balance calculation method described above, and the balance of 'user_a_account' becomes '1,600' and the balance of 'user_c_account' becomes '500' won.

[0117] However, in the case of 'user_b_account', since there is a transaction with another bank, the balance is calculated as the balance of 'user_b_account' by adding '3,000' won received by the user in the current bank transaction ledger (1126c) and '3,000' received by the user in the other bank deposit ledger (1127b), and subtracting '100' won sent by the user in the current bank transaction ledger (1126c), so that the total balance of '5,900' won is calculated as the balance of 'user_b_account'.

[0118] Additionally, all balances of 'group2' are the balances of 'user_a_account', 'user_b_account', and 'user_c_account', which are combined to a single value of '8,000'.

[0119]

[0120] As described above, the present invention has been illustrated and described with reference to preferred embodiments, but is not limited to the above embodiments, and various changes and modifications may be made by a person skilled in the art to which the invention pertains within a scope that does not depart from the spirit of the present invention.

Claims

1. A composition of a distributed processing system and an asset transaction method that records and processes asset transaction (hereinafter, “remittance”) details for multiple users in a distributed ledger format. a) A step of grouping the above users by classification criteria including the region of residence, age, or reception location, and dividing the distributed ledger by each group to form a divided distributed ledger; b) A step of constructing a distributed ledger network consisting of a plurality of nodes that record each partitioned distributed ledger as an identical copy; c) A step of designating and configuring a consensus node for each distributed ledger network that assigns a transaction order to transaction messages occurring within the distributed ledger networks and distributes them equally to each node; d) A step of configuring a delegate node to record remittance history between different distributed ledger networks; e) a step of forming a distributed ledger network group in which all distributed ledger networks are connected; and f) A step of configuring a distributed processing system with improved performance compared to a single distributed ledger network and a method for asset transactions, including a step of configuring a system to enable a user to perform in-house transactions (transactions with users within the same distributed ledger network) and out-of-house transactions (transactions with users within different distributed ledger networks) through the distributed ledger network to which the user belongs.

2. In paragraph 1, A step of creating a ledger allocation table for each node of all distributed ledger networks to manage which distributed ledger networks users belong to; A step where a user accesses a specific distributed ledger network and requests registration, including personal information; A step of grouping users by specific categories (region, age, reception center, etc.) and recording in the ledger allocation table which group the user belongs to; and A method for configuring a distributed processing system and trading assets, characterized in that it includes a step of replicating the ledger allocation information of a user newly recorded in the above ledger allocation table to all nodes of all distributed ledger networks.

3. In paragraph 2, The above-mentioned divided distributed ledger is composed of a current transaction ledger that records the history of asset transfers within the distributed ledger network to which the user belongs, and a foreign deposit ledger that records the history of asset transfers transferred to the user from another distributed ledger network to which the user does not belong. The above transaction ledger records the transaction identifier that distinguishes whether it is a transaction with the bank or another bank, the group to which the sender belongs, the sender's account, the remittance amount, the group to which the recipient belongs, the recipient's account, etc. in the form of double-entry bookkeeping. If the above transaction identifier is a cross-border transaction (the recipient belongs to a different distributed ledger network), the delegate account is further recorded. The above-mentioned deposit ledger must record the account of the agent, and is recorded in double-entry bookkeeping format, including the group to which the sender belongs, the sender's account, the remittance amount, the group to which the recipient belongs, the recipient's account, etc. A distributed processing system configuration and asset transaction method characterized in that the above-mentioned current transaction ledger and the above-mentioned inter-bank deposit ledger separately calculate and record the final balance of the account when each transaction occurs.

4. In paragraph 3, The consensus node equipped in each distributed ledger network assigns the transaction order of transaction messages (performs agreement) only for the transactions of the divided distributed ledger that must be processed in the distributed ledger network to which it belongs. A configuration of a distributed processing system and an asset transaction method characterized by allowing the execution of consensus by consensus nodes to be processed in parallel by having transaction messages propagate (replicate) to nodes belonging to the distributed ledger network to which the system belongs.

5. In paragraph 3, The system grants the delegatee the authority to process transactions on behalf of others. Create your own account on any distributed ledger network, A method for configuring a distributed processing system and trading assets, characterized by depositing a deposit that allows one to perform delegated transactions in all distributed ledger networks.

6. In paragraph 5, A step in which a user composes a remittance message through a user terminal and submits the remittance message to a distributed ledger network to which the user belongs; A step in which a node that has received a remittance message transmits the remittance message to a consensus node designated to perform consensus in the distributed ledger network to which it belongs; The consensus node that collected the remittance message determines whether the collected remittance message originated from the distributed ledger network designated by it; If the remittance message transmitted to the consensus node originates from the designated distributed ledger network, the step of assigning (agreeing on) the transaction order and disseminating it to all nodes through the message distributor; and A configuration of a distributed processing system and an asset transaction method, characterized in that the node receiving the remittance message with the transaction order includes a step of recording the remittance message in the current transaction ledger.

7. In paragraph 6, When composing a remittance message, if the recipient belongs to the same distributed ledger network as the sender, the transaction identifier is indicated as this bank, and if the recipient belongs to a different distributed ledger network, the transaction identifier is indicated as another bank and the remittance message is submitted to the distributed ledger network. The node receives a transaction message with transaction order information from the consensus node and records it in the current transaction ledger through the data manager. A distributed processing system configuration and asset transaction method characterized in that the data manager updates the balance accumulation data to decrease the sender's balance and increase the receiver's balance when the transaction identifier of the transaction message is the current bank, and updates the balance accumulation data to decrease the sender's balance and increase the delegate's balance when the transaction identifier is another bank.

8. In paragraph 7, The step where the principal searches for a new transaction in the current bank's ledger where the transaction identifier is another bank and the principal's account is his / her own; The delegate creates a delegate transaction message by referencing the group information to which the sender belongs in the searched transaction; The delegate submits the generated delegate transaction message to the distributed ledger network to which the sender belongs; A step in which a node receiving a delegation transaction message transmits the delegation transaction message to a designated consensus node; A step for a consensus node to determine whether a delegated transaction message received originated from the distributed ledger network to which it was assigned; The step where the consensus node assigns (agrees on) a transaction order to the delegated transaction message and broadcasts it to all nodes through the message distributor; The node that received the delegated transaction message from the consensus node records it in the deposit ledger through the data manager; and A method for asset trading and a configuration of a distributed processing system, characterized in that the data manager determines that the message is a delegated transaction message, decreases the delegater's balance, and updates the accumulated balance data so that the recipient's balance increases.

Images