Information processing device and information processing method

Abstract

To provide a technology that enables businesses wishing to operate electronic currency to easily do so. [Solution] An information processing device operated by an operating company that operates tokens comprises a receiving means for receiving a payment instruction instructing the transfer of a coin associated with cash currency from a first user to a second user, and a transmitting means for transmitting a transfer instruction instructing the transfer of a token associated with the coin in accordance with the payment instruction received by the receiving means to an electronic currency management system, and the electronic currency management system comprises a coin blockchain network that operates the coins, a token blockchain network that operates the tokens, and a transfer means for transferring a coin associated with the token in the coin blockchain network in accordance with the transfer of the token in the token blockchain network.

Description

[Technical field]

[0001] The present invention relates to Electronic Currency Management System Regarding. [Background technology]

[0002] Up until now, multiple businesses have operated electronic payment systems for multiple electronic currencies, virtual currencies, etc. For example, Patent Literature 1 discloses a system for validating transfers (transactions) of virtual currencies. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 6521421 Summary of the Invention [Problem to be solved by the invention]

[0004] The present invention has been made in consideration of the above-mentioned problems, and has an object to provide a technique that enables business operators who wish to operate electronic currency to easily operate electronic currency. [Means for solving the problem]

[0005] According to one aspect of the present invention, there is provided an information processing device comprising: 1. An electronic currency management system, comprising: A common area blockchain network that operates a first coin associated with a cash currency and a second coin associated with the cash currency and different from the first coin; A first additional domain blockchain network that operates a token associated with the first coin; a first transfer means for transferring, in response to a transfer of a predetermined amount of the tokens from a first user to a second user in the first additional domain blockchain network, a first coin corresponding to the predetermined amount in the common domain blockchain network from the first user to the second user; a second transfer means for transferring the second coins corresponding to the predetermined amount from a first issuer associated with the first user to a second issuer associated with the second user; The present invention is characterized by comprising: Effect of the Invention

[0006] According to the present invention, it is possible to provide a technique that enables business operators who wish to operate electronic currency to easily operate electronic currency. [Brief description of the drawings]

[0007] [Figure 1] FIG. 1 is a diagram showing an electronic currency management system according to an embodiment of the present invention. [Diagram 2] FIG. 2 is a diagram showing the hardware configurations of the issuer device, the operator device, the user device, and the relay device in FIG. [Diagram 3] FIG. 13 is a diagram showing a token issuing process. [Figure 4] A conceptual diagram of a two-tiered electronic currency. [Diagram 5] FIG. 13 is a diagram showing an example of value transfer between additional domain networks. [Figure 6] FIG. 13 is a diagram showing an example of value transfer between additional domain networks. [Figure 7] FIG. 1 shows an example application of an additional area network. [Figure 8] FIG. 1 is a diagram showing an example of inter-bank settlement. [Figure 9] A diagram showing an electronic currency management system. [Figure 10] FIG. 2 is a diagram showing a process for registering an issuer device, an operator device, and a user device. [Figure 11] FIG. [Figure 12] FIG. 13 is a diagram showing a coin issuing process. [Figure 13] A diagram showing the electronic currency management system after coins are issued. [Figure 14] FIG. 4 is a diagram showing a token registration process. [Figure 15] FIG. 13 is a diagram showing a token issuing process. [Figure 16] A diagram showing the electronic currency management system after token issuance. [Figure 17] FIG. 13 is a diagram showing a token purchasing process. [Figure 18] A diagram showing the electronic currency management system after token purchase. [Figure 19] FIG. 1 shows an example of token transfer. [Figure 20] FIG. 1 shows an example of token transfer. [Figure 21] FIG. 14 is a diagram showing the hardware configuration of the management server of FIG. 13. [Figure 22] FIG. 13 is a diagram showing an example of a payment process in the additional area. [Diagram 23] FIG. 13 is a diagram showing an example of a payment process in the additional area. [Figure 24] FIG. 13 is a diagram showing an example of a remittance process in a common area. [Diagram 25] FIG. 13 is a diagram showing an example of a payment process in the additional area. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] Hereinafter, the embodiments will be described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the invention according to the claims, and not all combinations of features described in the embodiments are essential to the invention. Two or more features among the multiple features described in the embodiments may be arbitrarily combined. In addition, the same reference numbers are used for the same or similar configurations, and duplicated descriptions are omitted.

[0009] The electronic currency management system according to the present embodiment will be described below. The electronic currency management system 1 according to the present embodiment includes a common area network 10, issuer devices 11A, 11B, and 11C (hereinafter, sometimes referred to as issuer device 11 without distinction), relay devices 21A, 21B, and 21C (hereinafter, sometimes referred to as relay device 21 without distinction), additional area networks 30A, 30B, and 30C (hereinafter, sometimes referred to as additional area network 30 without distinction), operator devices 31A, 31B, and 31C (hereinafter, sometimes referred to as operator device 31 without distinction), and user devices 41A, 41B, and 41C (hereinafter, sometimes referred to as user device 41 without distinction) and 42A, 42B, and 42C (hereinafter, sometimes referred to as user device 42 without distinction).

[0010] The common area network 10 is a distributed ledger network such as a blockchain, and is composed of nodes that operate a distributed ledger system including an issuer device 11. The common area network 10 is used to execute operations such as the transfer of electronic currencies (coins) 101 to 104 linked to the currency operated by the issuer device 11.

[0011] The issuer device 11 is a device used by a company, such as a bank, that has a license to issue electronic currency.

[0012] The additional domain network 30 is a distributed ledger network such as a blockchain, and is composed of nodes that operate a distributed ledger system including an operator device 31 and user devices 41 and 42. The additional domain network 30 is used to provide operations such as transfer of tokens operated by the operator device 31. In this embodiment, operations of coins or tokens include issuance, transfer, redemption, and exchange. The additional domain network 30 is created for each individual use case according to the business needs of a company or the like.

[0013] The relay device 21 monitors the common area network 10 and the additional area network 30, and operates coins in the common area network 10 in response to token operations in the additional area network 30. It also operates tokens in the additional area network 30 in response to coin operations in the common area network 10. The operator device 31 is a device of a business entity that operates tokens in the additional area network 30. The user devices 41 and 42 are devices of users who receive services in the additional area using tokens.

[0014] For example, based on a request from a customer, the operating company 31A, who wishes to issue 1 billion yen worth of electronic currency, the issuer device 11A, which is a bank, withdraws 1 billion yen from the customer's existing bank deposit from the bank account and issues 1 billion yen worth of white coins 101 with no specification of which additional area they will be used in.

[0015] After that, the operating company allocates 200 million yen worth of white coins out of the 1 billion issued white coins 101 using the application provided by the common area network 10 to the coins 102 associated with the additional area, and issues an issuance instruction to the additional area network 30A to issue tokens (e.g., electricity tokens) corresponding to the coins 102. At this timing, 200 million of the 1 billion white coins can only be used in the additional area network 30A (e.g., the additional area for energy trading).

[0016] Similarly, the amount of tokens desired to be issued in each of the other additional areas can be designated and allocated (locked) to each additional area network 30 as shown by coins 103 and 104 in the common area network 10, thereby ensuring the value of the additional area. Also, the moment the designation is made, a token that gives the impression that currency has been issued is issued in the additional area network 30. This is not the actual electronic currency itself, but is like an instruction certificate that gives instructions to move it, and from the viewpoint of the operating company, it looks as if electronic currency has been issued in the additional area.

[0017] When a transaction is made in the additional area network 30A, a token issued in the additional area network 30A, which is in reality a "shadow of electronic currency," is moved in the additional area network 30A to circulate value. The content of the circulation in the additional area network 30A is to asynchronously link the operation of the coin 102 and the token in the additional area network 30A and the common area network 10. In other words, value is transferred in the form of actual electronic currency (coins) 102-104 in the common area network 10 in synchronization with the circulation of the token in the additional area network 30A.

[0018] The electronic currency issued in the common area will be legally treated as a deposit, and will represent a deposit claim rather than an asset that requires a normal deposit. Banks will transfer the actual electronic currency as part of their exchange operations.

[0019] First, the bank issues a white coin without specifying which additional area it will be used in, and specifies that it will be used in additional area 1.

[0020] A function will be provided to change this back to a white coin, remove the additional area designation, return it to a white coin, and specify that it will be used in a different additional area. For example, this will remove the electronic currency designated for electricity trading and specify that it will be used as retail electronic currency, making it possible to transfer the currency without having to go to the trouble of returning it to a bank deposit.

[0021] Next, the configurations of the issuer device 11, relay device 21, operation provider device 31, and user devices 41 and 42 will be described with reference to Fig. 2. The issuer device 11 includes a processor 201, a memory 202, a storage 203, a network interface (I / F) 204, and an input / output I / F 205.

[0022] The processor 201 is a control unit that controls the entire issuer device 11. The processor 201 includes at least one of a central processing unit (CPU), a graphics processing unit (GPU), and a microcontroller that executes a program or an operating system (OS) stored in the storage 203. The memory 202 is composed of a dynamic random access memory (DRAM), a static random access memory (SRAM), etc. that are used as a working memory for the processor 201.

[0023] The storage 203 includes a hard disk drive (HDD) and a solid state drive (SSD) that store the programs executed by the processor 201, the OS, and at least one of data tables and setting values ​​used by the programs. The input / output I / F 205 is a user interface that includes input devices including at least one of a keyboard, a touch panel, and a microphone for receiving user operations, and output devices including at least one of a display, a speaker, and an LED. In this specification, the relay device 21, the operator device 31, and the user devices 41 and 42 will be described as having the same hardware configuration as the issuer device 11. In one example, at least one of the issuer device 11, relay device 21, operation provider device 31, and user devices 41 and 42 may not have an input / output I / F 205, and in this case, at least one of the issuer device 11, relay device 21, operation provider device 31, and user devices 41 and 42 that do not have an input / output I / F 205 may accept operation instructions and output operation results via the network I / F 204.

[0024] Next, the flow of processing in the electronic currency management system 1 according to this embodiment will be described with reference to FIG.

[0025] First, the operator pays the issuer a security by transferring security money 301 relating to the token operation to the issuer's bank account or the like.

[0026] Next, the issuer device 11 issues electronic currency (coins) 302 equivalent to the collateral in the common area network 10. The coins 302 issued here indicate that the issuer is the issuer device 11, but are white coins that are not associated with tokens. In addition, the transfer instruction for the white coins cannot be given by the operator device 31, but can only be given by the issuer device 11.

[0027] Next, the user of the additional area network notifies the bank, which is the issuer of the electronic currency, of the type, quantity, and operator identifier of the token to be issued, for example, through the bank's application system.

[0028] When a bank receives notification of the token issuance, it instructs the issuer device 11 to issue a token for a specific additional area, which enables the issuer device 11 to transfer the white coin 302 as a (colored) coin 304 linked to the token 303.

[0029] The relay device 21 monitors the common area 10 and can transfer the coin 304 linked to the token 303 by detecting a transfer in the additional area.

[0030] The relay device 21, which detects the transfer of the token, instructs the common area network 10 to transfer the coin. The relay device 21 instructs the common area network 10 to change the owner of the coin linked to the token from the transfer source to the transfer destination.

[0031] As shown in FIG. 4, electronic currency issued to the common area network 10 is locked by specifying the identifier of the additional area network 30 used by the user, and can only be transferred in transactions in which the specified additional area network 30 is the sender or destination, and transfers cannot be made without receiving instructions from a device within the additional area network 30.

[0032] That is, the substance of the electronic currency exists in the common domain network 10. And the additional domain network 30 holds the tokens that embody the substance of the electronic currency.

[0033] Electronic currency issued in the common area is organized as a deposit. In the additional area, tokens are issued as certificates representing exchange transactions that transfer electronic currency (as an entity) in the common area. Since the electronic currency itself is treated as a deposit, it becomes possible to manage and consume the electronic currency.

[0034] It will be possible to provide a new payment platform that uses highly reliable electronic currency backed by the existing legal tender system, with as little reliance as possible on old legacy systems, and by achieving interoperability with commercial flows through programmability, etc., it will be possible to provide highly convenient services.

[0035] In addition, as shown in Figure 5, digital currency transfer across additional domains can be realized without issuance and redemption as follows. (1) The designation of the token received in the additional area network 30A is cancelled, and the coin associated with the additional area 30A in the common area network 10 is made into a white coin. Accordingly, the token in the additional area network 30A is reduced by the transfer amount. (2) The white coin electronic currency is associated with the additional area network 30B, and the tokens of the additional area network 30B are increased by the transfer amount.

[0036] This completes the transfer of electronic currency between the additional area networks.

[0037] In the example of Fig. 5, a process of value transfer between different additional domains is shown, with user device 41A and user device 41B associated with the same user as the remittance source and the remittance destination. In this case, in the common domain, the coins associated with the user only change the additional domain network to which they belong, and the total amount of value does not change. Therefore, the bank deposit is not transferred.

[0038] In addition, as shown in Figure 6, the following procedure enables electronic currency transfer across additional domains between different users without issuance or redemption. (1) The user device 41A corresponding to the user A of the additional area network 30A cancels the designation of the electronic currency associated with the token on the additional area network 30A and converts it into a white coin. (2) The relay device 21A instructs the common area network 10 to transfer the electronic currency that was converted into a white coin in (1) from user A to user B. (3) The white coin is associated with user B, and the relay device 21B grants the token of the additional area network 30B to the user device 41B corresponding to user B.

[0039] In the example of FIG. 6, since value is transferred from user device 41A belonging to additional area network 30A to user device 41B belonging to additional area network 30B, coins are also transferred in common area network 10.

[0040] Also, as shown in FIG. 7, different additional domain networks, such as an energy trading platform (PF), a retail platform, and electronic currency, can be supported by one common domain network.

[0041] This allows applications using additional domain networks to be easily launched, improving the convenience of operators. In addition, issuers can share the operation of a common domain among multiple issuers, and transfers between banks can be made using electronic currency. In addition, interoperability between additional domain networks can be improved.

[0042] When transferring (transferring) electronic currency across banks, it is necessary to consider settlement between banks, just as with normal remittances. As with normal interbank remittances, the settlement balance may be transferred from the Bank of Japan's current account, but the customer remittance must go through the Zengin System. For this reason, the electronic currency management system of this embodiment issues electronic currency for interbank settlement so that the settlement can be completed as much as possible on the electronic currency platform. This eliminates the need to go through the Zengin System when the customer remittance is made. Furthermore, even if a central bank digital currency (CBDC) is issued in the future and a wholesale CBDC for interbank settlements is introduced, a smooth transition will be possible.

[0043] For example, as shown in FIG. 8, if user 811A has a deposit account with issuer 801A and user 811B has a deposit account with issuer 801B, when user 811A transfers money to user 811B, the money will be transferred across the banks of issuers 801A and 801B.

[0044] Settlement between users 811A and 811B is carried out when issuer 801A reduces the deposit of user 811A and issuer 801B increases the deposit of user 811B. In other words, when issuer 801A receives an instruction from a depositor to transfer deposits across banks, issuer 801A carries out interbank settlement with issuer 811B. In this case, since the amount of interbank settlement is large, banks almost never settle with other banks in cash, and usually carry out interbank settlement by transferring deposits (in most cases, the bank's current account at the central bank).

[0045] In the common area of ​​the two-tiered electronic currency platform, in order to complete the interbank settlement processing described above on the PF without using central bank current accounts, wholesale electronic currency will be issued to carry out the interbank settlement described above, and the finality of settlement associated with the transfer of electronic currency will be guaranteed by netting the interbank settlement processing.

[0046] Specifically, the amount of electronic currency to be issued is withdrawn from the deposit of user 811A and transferred to the account of issuer 801A, and electronic currency is issued to user 811A. Next, electronic currency is transferred from user 811A to 811B. At this point, only the liabilities of issuer 801A have been transferred to issuer 801B.

[0047] Also, settlement is required to balance the assets and liabilities between issuers 801A and 801B. Regular remittances are made by transfer of current accounts at the Bank of Japan. Electronic currency for interbank settlement (wholesale electronic currency), which is the asset of issuer 801B and the liability of issuer 801A, is issued based on the credit of issuers 801A and 801B, making it possible to net settlement processing between issuers 801A and 801B.

[0048] Next, the electronic currency management system according to this embodiment will be described with reference to FIGS.

[0049] The electronic currency management system 1 according to the present embodiment includes a common area network 10, issuer devices 11A, 11B, and 11C (hereinafter, sometimes referred to as issuer device 11 without distinction), relay devices 21A, 21B, and 21C (hereinafter, sometimes referred to as relay device 21 without distinction), additional area network 30A, 30B, and 30C (hereinafter, sometimes referred to as additional area network 30 without distinction), operator devices 31A, 31B, and 31C (hereinafter, sometimes referred to as operator device 31 without distinction), user devices 41A, 41B, and 41C (hereinafter, sometimes referred to as user device 41 without distinction) and 42A, 42B, and 42C (hereinafter, sometimes referred to as user device 42 without distinction), and a management server 50. The common area network 10, issuer device 11, relay device 21, additional area network 30, operator device 31, and user devices 41 and 42 have been described with reference to FIG. 1, and therefore will not be described here.

[0050] In addition, in FIG. 1 and FIG. 9, electronic currency is illustrated as existing in each issuer device 11 so as to clarify the management entity of the issued electronic currency. However, when the common area network 10 is a blockchain network, electronic currency may be managed in a distributed ledger managed by multiple issuer devices 11. In addition, the data of the electronic currency itself may be stored in the management server 50, and the issuer device 11 may only have operational authority such as setting attributes of the electronic currency. That is, in FIG. 1 and FIG. 9, the electronic currency is illustrated only to show the correspondence with the issuer device that manages the electronic currency, and does not limit the device that stores the electronic data of the electronic currency.

[0051] The management server 50 registers the issuer device 11, the operator device 31, and the user device 41 in the common area network 10 and the additional area network 30. In addition, when a new additional area network 30 is created, the management server 50 registers the relay device 21.

[0052] Next, the configuration of the management server 50 will be described with reference to Fig. 21. The management server 50 includes a processor 201, a memory 202, a storage 203, a network interface (I / F) 204, and an input / output I / F 205, similar to the issuer device 11, the operator device 31, and the user device 41. The processor 201, the memory 202, the storage 203, the network interface (I / F) 204, and the input / output I / F 205 have the same configuration as in Fig. 2, so detailed description will be omitted.

[0053] Hereinafter, the processing executed by the electronic currency management system 1 will be described with reference to Figs.

[0054] (Registration process of issuer device 11) The process in which the issuer device 11 joins the common area network 10 will be described with reference to FIG. 10(A).

[0055] First, the issuer concludes a platform usage contract with the management company of the management server 50. In response to this, the management company of the management server 50 registers management account information for using the electronic currency management system in the management server 50 (S1001).

[0056] Next, the management server 50 notifies the issuer device 11 of a management account including the ID of the user account (S1002). The issuer device 11 instructs the management server 50 to create an issuer account that has the authority to issue coins (S1003). The management server 50 registers the account information in an issuer database to create an issuer account (S1004), and transmits the issuer ID to the issuer device 11 (S1005).

[0057] (Registration process of operator device 31) Next, a process in which the operator device 31 participates in the additional area network 30 will be described with reference to FIG. 10(B).

[0058] First, the operating company concludes a platform usage contract with the management company of the management server 50. As a result, the management company of the management server 50 registers management account information corresponding to the operating company in the management server 50 (S1021).

[0059] Next, the management server 50 notifies the operation provider device 31 of the account to be used (S1022). The operation provider device 31 instructs the management server 50 to create an operation provider account that has the authority to issue tokens (S1023). The management server 50 transmits an operation provider ID corresponding to the operation provider account to the operation provider device 31 (S1024).

[0060] (Registration process of user devices 41 and 42) Next, a process in which the user devices 41 and 42 join the additional area network 30 will be described with reference to FIG. 10(C).

[0061] First, the user makes a platform usage contract with the management company of the management server 50. In response to this, the management company of the management server 50 registers management account information corresponding to the user in the management server 50 (S1041).

[0062] Next, the management server 50 notifies the user devices 41 and 42 of the accounts to be used (S1042). The user device 41 instructs the management server 50 to create a user account with authority to purchase, send, and receive tokens (S1043). The management server 50 transmits a user ID corresponding to the user's account to the user devices 41 and 42 (S1044).

[0063] (Deposit Processing) Next, a process for making a deposit required for the issuer device 11 to issue coins will be described with reference to Fig. 11(A). It is assumed that the operating company provides a security to the issuer by transferring a security deposit for the operation of the token to the issuer's bank account or the like.

[0064] The issuer device 11 registers the deposit information in the management server 50 (S1101). Here, the registered deposit information includes the issuer ID and the collateral amount. In another example, the ID of the coin linked to the issuer ID may be registered as the deposit information. Next, the management server 50 registers the deposit information in the deposit information database (S1102). Then, the management server 50 transmits an identifier (deposit information ID) in the deposit information database corresponding to the deposit for which registration has been completed to the issuer device 11 (S1103).

[0065] In addition to the deposit information described above, the deposit information database may also manage the remaining amount of the deposit. This makes it possible to manage the remaining number of coins that can be issued by a single deposit, even if a certain amount of coins is deposited and a smaller number of coins are issued than can be issued by a single deposit, by reducing the remaining amount of the deposit by the amount corresponding to the number of issued coins.

[0066] When updating the deposit information that has already been registered by making an additional deposit, as shown in Fig. 11(B), the deposit information to be updated is sent to the management server 50 together with the deposit information ID (S1121), and the management server 50 updates the data in the deposit information database (S1122). When the management server 50 confirms the deposit, it sends a response to the issuer device 11 (S1123).

[0067] In addition, when the issuer device 11 is operated by a banking company, the deposit process shown in Fig. 11(A) may not be necessary. On the other hand, when the issuer device 11 is operated by a company other than a banking company, such as a funds transfer company, the deposit process shown in Fig. 11(A) may be required. In other words, whether or not the issuer device 11 performs the deposit process may be determined according to regulations that the issuer complies with, such as the operator of the issuer device 11.

[0068] (Coin issuing process) Next, with reference to FIG. 12, a process in which the issuer device 11 issues coins linked to cash currency will be described.

[0069] First, in S1201, the issuer device 11 transmits a coin issuance request to the management server 50. The coin issuance request includes an issuer ID, a coin ID, and an issuance quantity.

[0070] The management server 50 uses the issuer ID included in the coin issuance request to acquire deposit information with a matching issuer ID from the deposit information registered in the deposit information database (S1202). Next, the management server 50 specifies the collateral amount from the deposit information and determines the number of coins that can be issued (S1203). As described above, if the deposit information includes the remaining amount of the deposit, the number of coins that can be issued may be determined based on the remaining amount of the deposit.

[0071] As a result of the determination, if it is determined that the issuance quantity of coins included in the issuance request can be issued, the management server 50 issues the coins to the issuer's wallet on the common area network 10 of the issuer device 11 (S1204). Next, the management server 50 notifies the issuer device 11 of the issuance quantity (S1205).

[0072] Here, the state of the wallet after coin issuance will be described with reference to Fig. 13. In the example of Fig. 13, for ease of explanation, it is assumed that the issuer device 11A issues coins, and that no other coins are issued. Also, in Fig. 13, it is assumed that there are two additional area networks.

[0073] At the time of issuing the coin, the coin is not associated with any additional area network 30. In other words, the coin issued in S1204 of Fig. 12 is a white coin 101. The white coin 101 is set in the issuer device 11A issued by the owner, and processing such as transfer can be performed only by the issuer device 11A.

[0074] (Token registration process) Next, a process of newly registering a token to be circulated on the additional area network 30 will be described with reference to Fig. 14. It is assumed that the issuer and the operating company make a contract regarding the operation of the token to be circulated on the additional area network 30, and the operating company device 31 has acquired the issuer ID of the issuer device 11.

[0075] The operator device 31 transmits a token registration request to the management server 50 (S1401). The token registration request includes information indicating the operator ID, token name, token symbol, and coin (backing coin) backing the value of the token. The management server 50 registers the operator ID, token name, token symbol, and backing coin included in the token registration request in the token database in association with the token ID based on the operator ID included in the token registration request (S1402). Then, the management server 50 transmits the registered token ID to the operator device 31 as a response to the registration request (S1403). This allows the operator to perform processes such as issuing, redeeming, and transferring the token corresponding to the token ID.

[0076] (Token issuing process) Next, a process of newly issuing a token to be circulated on the additional area network 30 will be described with reference to FIG.

[0077] In the following description, it is assumed that the operating company has an account corresponding to the operating company under the control of the issuer, which is a bank.

[0078] First, the operation provider device 31 transmits a token issuance request to the relay device 21, and the relay device 21 transmits the token issuance request to the issuer device 11, whereby the issuer device 11 acquires the token issuance request (S1501). If the operation provider device 31 is configured to be able to transmit the token issuance request directly to the issuer device 11, the operation provider device 31 may transmit the token issuance request to the issuer device 11 without going through the relay device 21. The token issuance request includes a token ID and a token quantity. Upon receiving the issuance request, the issuer device 11 transmits a token issuance instruction including the issuer ID, token ID, and token quantity to the management server 50 (S1502). The management server 50 acquires deposit information from the deposit information database based on the issuer ID (S1503), and determines whether or not it is possible to issue tokens for the number of tokens included in the token issuance instruction (S1504). The determination of whether or not it is possible to issue tokens in the token quantity may include a determination of whether or not the issuer device 11 holds white coins corresponding to the token quantity in the wallet of the issuer device 11. Alternatively, it may include a determination of whether or not the issuer holds financial assets corresponding to the token quantity to be issued in the account of the operating company.

[0079] If the management server 50 determines that the token included in the token issuance instruction can be issued, the management server 50 sends an issuance notification to the issuer device 11 (S1505) and issues the token to the wallet of the operator 31 of the additional area network 30 corresponding to the token ID (S1506).

[0080] When the issuer device 11 receives the issuance notification, it links the white coins held in the wallet of the issuer device 11 to the additional area network 30 (S1507). In the case where an attribute tag can be assigned to the coin, the coin can be converted into a colored coin associated with the additional area network 30 by setting an attribute tag that is not set at the time of issuance to the ID of the operator or the like. In this embodiment, by associating the attribute tag of the coin with the additional area network 30, for example, when the operator device 31 has a wallet in the common area network 10, the coin may be associated with the additional area network 30 by transferring coins corresponding to the number of tokens held by the operator device 31 from the wallet of the issuer device 11 to the wallet of the operator device 31.

[0081] In S1507, the owner of the coin is set to the operating company device 31. Although the owner of a colored coin can be changed, it is necessary to convert it into a white coin in order to transfer or redeem it.

[0082] The value of the additional area can be guaranteed by designating the number of tokens to be issued and allocating (locking) them to each additional area network 30 as shown by coins 103 and 104 in the common area network 10. In addition, at the moment of designation, a token that gives the impression of currency being issued is issued in the additional area network 30. This is not the actual entity of electronic currency, but is like a proof of instruction to move it, and from the viewpoint of the operating company, it looks as if electronic currency was issued in the additional area network. The coins issued to the common area network 10 are locked by designating the identifier of the additional area network 30 used by the user, and only transactions in which the specified additional area network 30 is the sender or destination can be transferred, and the transfer is not performed unless an instruction is received from a device in the additional area network 30.

[0083] Next, the electronic currency management system 1 after the issuance of the token will be described with reference to Fig. 16. Fig. 16 is a diagram showing a case where the additional area network 30A issues a token with the issuer 11A as the issuer after Fig. 13.

[0084] The issuer 11A has a wallet of the issuer 11A on the common area network 10, and holds a white coin 1301. It also holds a colored coin 1601 corresponding to the additional area network 30A, and the coin 1601 can only be used for token transactions with the additional area network 30A as the remitter or remitter. The operator device 31A also holds an issued token 1611.

[0085] (Token purchase process) Next, with reference to FIG. 17, an example will be described in which a user pays currency to an operating company and obtains a token circulating in the additional area network 30A.

[0086] The user device 41A transmits a token purchase request including the user ID of the token, the type of token to be purchased, the number of tokens, and payment information specifying the payment method to the relay device 21A, and the relay device 21A transfers the token purchase request to the operator device 31A (S1701). The payment information may include the payment method, such as direct debit, and the payment type, such as whether the payment is made in cash or electronic currency. If the user device 41A1 is configured to be able to transmit a token purchase request directly to the operator device 31A, the user device 41A may transmit the token purchase request to the operator device 31A without going through the relay device 21A.

[0087] The operator device 31A judges whether to transfer the tokens according to the purchase request from the type and quantity of tokens based on the payment information (S1702). If the operator device 31A judges that the tokens included in the purchase request can be purchased with the payment included in the payment information, the operator device 31A transmits a transfer instruction to the additional area network 30A to transfer the specified number of tokens from the wallet of the operator device 31A to the wallet of the user device 41A. The token transfer instruction is transmitted to the issuer device 11A (S1703). The token transfer instruction includes the transfer source, transfer destination, token type, and token quantity.

[0088] When the transfer instruction is transmitted onto the additional area network 30A, the relay device 21A detects the transfer instruction (S1704) and identifies the source and destination of the token (S1705). Upon identification, the relay device 21A transmits a coin transfer instruction corresponding to the token transfer instruction to the issuer device 11A corresponding to the additional area network 30A (S1706). For example, based on the value and quantity of the token converted into cash currency and the value of the coin converted into cash currency, the relay device 21A instructs the issuer device 11A to transfer coins equivalent to the value of the token to be transferred converted into cash currency.

[0089] The issuer device 11A, which has received the transfer instruction from the relay device 21A, sets the owner of the coins owned by the operation company device 31 of the transfer source, among the colored coins 102 corresponding to the additional area 1, to the user device 41A of the transfer destination (S1707). If the common area network 10 is a blockchain network, a transfer instruction for the coins from the transfer source to the transfer destination is transmitted. This allows the transfer of value to be performed even on the common area network 10, which guarantees the value.

[0090] Although not shown in Fig. 17, a payment process is performed separately from the user device 41A to the operator device 31A. This may be performed before the purchase of the tokens or after the transfer of the tokens is completed.

[0091] Next, the state after the purchase of the token will be described with reference to Fig. 18. Fig. 18 is a diagram showing the state after Fig. 16 in which the user device 41A purchases a token from the operation provider device 31A.

[0092] The issuer 11A has a wallet of the issuer 11A on the common area network 10, and holds a white coin 1301. The issuer 11A also holds colored coins 1601 and 1802 corresponding to the additional area network 30A. The owner of the colored coin 1601 is set to the operator device 31A, and the owner of the colored coin 1802 is set to the user device 41A. In addition, tokens 1611 and 1812 are held in the wallets of the operator device 31A and the user device 41A of the additional area network 30A corresponding to the colored coins 1601 and 1802.

[0093] (Token transfer processing example 1) In the token transfer instruction, as in the token purchase process described above, the common area network 10 and the additional area network 30 can be linked to transfer value.

[0094] An example of transferring tokens between users in the same additional area network 30A will be described with reference to FIG.

[0095] The user device 41A transmits a transfer instruction with the user device 42A as the transfer destination (S1901). In this embodiment, the transfer instruction is described as an order for a transaction to the additional area network 30A, which is a blockchain network, but if the operator device 31A manages the additional area network 30A, the transfer instruction may be transmitted to the operator device 31A. The token transfer instruction includes the transfer source, transfer destination, token type, and token quantity.

[0096] When a transfer instruction is transmitted onto the additional area network 30A, the relay device 21A detects the transmitted transfer instruction (S1902) and transmits a transfer instruction to the issuer device 11A based on the transfer source, transfer destination, token type, and token quantity (S1903) in a manner similar to that described with reference to FIG. 17.

[0097] Based on the transfer instruction, the issuer device 11A sets the owner of the colored coins 1802 linked to the additional area network 30A by the transfer source user device 41A to the user device 42A.

[0098] This allows the transfer of coins corresponding to the cash currency along with the transfer of tokens, thereby ensuring value.

[0099] (Token transfer processing example 2) Next, an example of transferring a token from a user device 42A in the additional area network 30A to a user device 42B in the additional area network 30B will be described with reference to Fig. 20. In the example of Fig. 20, a token is transferred between user devices of different users, but the same applies to an exchange in which user devices of the same user exchange tokens on different additional area networks 30.

[0100] The user device 42A instructs the additional area network 30A to transfer tokens from the user device 42A of the additional area network 30A to the user device 42B of the additional area network 30B (S2001). When the relay device 21A detects the transfer instruction from the user device 42A (S2002), it instructs the issuer device 11A to transfer coins from the additional area network 30A to the additional area network 30B (S2003).

[0101] The issuer device 11A converts the colored coins 102 associated with the additional area network 30A, which correspond to the number of tokens to be transferred, into white coins (S2004), and transfers the converted white coins to the issuer device 11B (S2005). The issuer device 11A also instructs the issuer device 11B to set the owner of the coins corresponding to the number of tokens to be transferred to the user device 41B and associate them with the additional area 30B. The issuer device 11B associates the transferred white coins with the additional area network 30B and sets the owner to the user device 41B (S2006). Next, the relay device 21B, which has detected the instruction from the issuer device 11A to the issuer device 11B, transmits a transfer of the tokens corresponding to the additional area network 30B from the user device 42A to 42B on the additional area network 30B. This allows the tokens to be transferred to the wallet of the user device 42B.

[0102] In this way, the relay device 21 detects a transfer in the common area network 10 and transfers a token on the additional area network 30 in response to the detected transfer. This enables the transfer of tokens between additional area networks by transferring coins on the common area network 10.

[0103] In the example of FIG. 20, the additional area networks 30A and 30B are associated with different issuer devices 11A and 11B in the common area 10. However, the additional area networks 30A and 30B may be associated with the same issuer device 11A. In this case, the issuer device 11A is associated with the additional area network 30A, and after the owner converts the colored coin of the issuer device 11A into a white coin, the converted white coin is associated with the additional area network 30B, thereby allowing the transfer of tokens between the additional area networks.

[0104] In this embodiment, the common area network 10 and the additional area network 30 are circulated through the additional area network 30A, and the operations of the coins 102 and tokens are coordinated synchronously or asynchronously between the additional area network 30A and the common area network 10.

[0105] In addition, according to this embodiment, electronic currency issued in the common area network is organized as a deposit. In the additional area, a token is issued as a certificate representing an exchange transaction that transfers electronic currency (as an entity) in the common area. Since the electronic currency itself is a deposit, it becomes possible to manage and consume the electronic currency.

[0106] It will be possible to provide a new payment platform that uses highly reliable electronic currency backed by the existing legal tender system, with as little reliance as possible on old legacy systems, and by achieving interoperability with commercial flows through programmability, etc., it will be possible to provide highly convenient services.

[0107] (Operator equipment) Next, the operation provider device 31 according to this embodiment will be described. The operation provider device 31 is an information processing device that manages the additional area 30, and issues tokens to the above-mentioned user device 41 and manages the transfer of tokens between multiple user devices 41. As will be described later, the operation provider device 31 can provide additional services such as matching users who can provide goods or services with users who wish to provide the goods or services.

[0108] ((Processing Example 1)) Next, an example of a payment process will be described with reference to Fig. 22. In the example of Fig. 22, a token is transferred from user A to user B, and remittance is performed from user A to user B.

[0109] 22, the account in the additional area associated with user device 41A of user A is additional area account 2202A, and the account in the additional area associated with user device 42A of user B is additional area account 2202B. Also, the account in the common area corresponding to additional area account 2202A is common area account 2212A, and the account in the common area corresponding to additional area account 2202B is common area account 2212B.

[0110] First, the operation provider device 31 according to this embodiment receives a remittance instruction (remittance instruction) from the remittance source user device 41A (S2251). The remittance instruction includes information indicating the source, destination, and amount of tokens to be transferred.

[0111] Next, the operator device 31 transmits a token transfer on the additional area network 30 based on the received remittance instruction (S2252). Next, when the relay device 21 detects the token transfer (S2253), it transmits a coin transfer on the common area network 10 (S2254).

[0112] This transfers coins from common area account 2212A to 2212B. In one example, user B operates user device 42A to send an account information request specifying additional area account 2202B to operator device 31, and obtains balance information to check the balance of additional area account 2202B, or obtains remittance information to check that remittance from user A has been made.

[0113] Next, user B operates user device 42A to send a withdrawal request to operation provider device 31 (S2255). The withdrawal request includes the target account and the withdrawal amount. When operation provider device 31 accepts the withdrawal request, if the balance of the target account is equal to or greater than the withdrawal amount, it reduces the withdrawal amount from the balance of the target account and transmits a withdrawal instruction to additional area 30 (S2256). Relay device 21 detects the withdrawal instruction (S2257) and transmits a withdrawal instruction corresponding to the detected withdrawal instruction to common area 10 (S2258). The withdrawal instruction transmitted by relay device 21 specifies user B's common area account 2212B and the withdrawal amount. When issuer device 11, which manages the wallet of common area account 2212B, accepts the withdrawal instruction, it reduces the withdrawal amount from the balance of the corresponding common area account 2212B and transfers legal tender corresponding to the withdrawal amount to user B's bank account. This allows User B to receive token payment in fiat currency.

[0114] In one example, a remittance from user A to user B can be used to pay for a product or service provided by user B. For example, when user B is a sales store and user A is a customer, user A may remit a token as payment from user A to user B in exchange for a product.

[0115] In this processing example, the remittance source user A is described as sending the remittance instruction. In one example, the remittance destination user B may send a remittance instruction requesting remittance. In this case, user B may include information on user A's additional area account 2202A and a one-time password provided by the user device 41A in the remittance instruction by a predetermined communication, and the operation provider device 31 may verify the validity of the remittance instruction from user B. In addition, the operation provider device 31 may perform the remittance when it receives a remittance request from the remittance source user A and a receipt request from the remittance destination user B. In this case, in order to determine whether the remittance request and the receipt request are for the same remittance process, the remittance request and the receipt request may include identification information indicating that they are the same remittance process.

[0116] ((Processing Example 2)) Next, an example of a payment process will be described with reference to Fig. 23. In the example of Fig. 23, an operation company mediates a commercial transaction between user A and user B, and transfers a token from user A to user B as payment for the commercial transaction.

[0117] 23, the account in the additional area associated with user device 41A of user A is additional area account 2302A, and the account in the additional area associated with user device 42A of user B is additional area account 2302B. Also, the account in the common area corresponding to additional area account 2302A is common area account 2312A, and the account in the common area corresponding to additional area account 2302B is common area account 2312B.

[0118] First, the operator device 31 according to this embodiment functions as a trading platform, and matches, for example, a user (provider) who provides a product or service with a user (recipient) who desires the product or service. For example, the trading platform operates an electronic commerce website and manages information on the product or service provided by the provider. The recipient can obtain information on the product or service provided by the provider and the provider's account information by accessing the electronic commerce website. Therefore, the recipient can request the provision of the product or service based on the provider's account information.

[0119] In another example, for example, a provided person registers information about a desired product or service and the provided person's account information, and when a provider decides to provide the product or service, the product or service can be provided based on the provided person's account information. In the example of Fig. 23, user B is a provider who provides a product or service, and user A is a provided person who desires the product or service, and user A pays a token as a consideration for the product or service.

[0120] First, in S2351, the operator device 31 detects that a commercial transaction between the provider and the provided party has been concluded. For example, the operator device 31 accepts the purchase of a product sold by user B by user A on an electronic commerce website. When the commercial transaction is concluded, the operator device 31 accepts a remittance instruction (remittance instruction) in the additional area 30 from the user device 41A (S2352). The remittance instruction includes information indicating the source, destination, and amount of tokens to be transferred. Note that, in the example of FIG. 23, the notification of the establishment of the contract in S2351 and the remittance instruction in S2352 are illustrated as being performed separately, but the operator device 31 may accept a message including the notification of the establishment of the contract and the remittance instruction from the user device 41A of user A, and the operator device 31 may transmit the transfer of the token to the additional area network 30.

[0121] Next, the operator device 31 transmits a token transfer on the additional area network 30 based on the received remittance instruction (S2353). Next, when the relay device 21 detects the token transfer (S2354), it transmits a coin transfer on the common area network 10 (S2355).

[0122] This transfers coins from common area account 2312A to 2312B. In one example, user B operates user device 42A to send an account information request specifying additional area account 2302B to operator device 31, and obtains balance information to check the balance of additional area account 2302B, or obtains remittance information to check that remittance from user A has been made.

[0123] User B may operate user device 42A to send a withdrawal request to operation provider device 31. The withdrawal request includes the target account and the withdrawal amount. When operation provider device 31 accepts the withdrawal request, if the balance of the target account is equal to or greater than the withdrawal amount, it subtracts the withdrawal amount from the balance of the target account and sends a withdrawal instruction to additional area 30. The subsequent processing is similar to S2255 to S2258 described in processing example 1, and therefore description thereof will be omitted. This allows user B to receive token payment in legal tender.

[0124] In the above example, it has been described that user A proceeds to make payment after the commercial transaction is concluded. However, in one example, user A can make payment when the provision of a product or service from user B is completed, such as when the product is delivered from user B. In this case, the operation provider device 31 may make payment when a delivery completion notice is received from user A, user B, or the delivery company.

[0125] As described above, in processing examples 1 and 2, the operator of the additional area network transfers the token in the additional area in response to an exchange instruction from the user. Then, the relay device that detects the token transfer transfers the coin in the common area. Therefore, the action taken by the operator corresponds to the transmission of the exchange instruction from the user. Then, the relay device 21 further issues an exchange instruction, and the transfer of the coin, i.e., the exchange, is performed by the issuer device 11 operated by the issuer. This allows even an operator that is not legally able to perform exchange actions to operate electronic currency by simply managing the transfer of the token.

[0126] (Account Permissions Settings) The issuer device 11, the operator device 31, and the user devices 41 and 42 according to this embodiment can realize their roles by setting authority for each account.

[0127] For example, the user devices 41 and 42 have the authority (user authority) to make a request to transfer or purchase a token in the additional area network 30 to which the user account belongs.

[0128] The operator device 31 has the authority (validator authority) to actually transmit a token transfer instruction based on a request in the additional area network 30 to which the operator account belongs. It also has the authority (provider authority) to instruct the creation of a token.

[0129] The issuer device 11 has the authority (validator authority) to send a coin remittance instruction to the common area network 10 in the common area to which the issuer account belongs. The issuer device 11 also has the authority (issuer authority) to issue and redeem digital currency, and the authority (user authority) to make deposit and remittance requests in the common area network 10.

[0130] The management server 50 has the authority to create a common area (administrator authority), the authority to create additional areas (provider authority), the authority to create accounts, and the authority to grant authority to each account.

[0131] The relay device 21 has authority (validator authority) to transmit a coin remittance instruction to the common area network 10 in the common area to which the relay device 21 belongs.

[0132] The authority settings can be appropriately designed by the system. This allows an account spanning the common area 10 and the additional area network 30 to be created by, for example, granting the authority of the issuer device 11 and the authority of the operator device 31 to one account. In addition, the authority of the operator device 31 may be assigned to multiple accounts, and the authority of the issuer device 11 may be assigned to multiple accounts. This allows the common area and the additional area to be operated by multiple accounts.

[0133] This enables, for example, as shown in FIG. 24, a transfer to be made from user A's account 2400A, which is managed by issuer device 11A corresponding to user A, to user B's account 2400B, which is managed by issuer device 11B corresponding to user B.

[0134] (Verifying payment transactions using signature information) A payment process using signature information according to this embodiment will be described with reference to Fig. 25. Note that Fig. 25 describes a process for making a payment from user A to user B, similar to the process example 1.

[0135] Before transmitting a payment instruction, the user device 41A of user A acquires signature information of user A from the issuer device 11 corresponding to user A (S2551). In this embodiment, the signature information is described as a signature key such as an electronic seal, but it may be an encryption key generated based on the account of user A or a one-time password.

[0136] The user device 41A that has acquired the signature information adds the signature information and transmits a payment instruction from user A to user B to the operation provider device 31 (S2552). The operation provider device 31 that has accepted the payment instruction transmits an instruction to transfer the token to the additional area network 30 using the signature information included in the accepted payment instruction (S2553). The subsequent processing from S2554 to S2555 is the same as S2253 to S2254, and therefore the explanation will be omitted.

[0137] In addition, the relay device 21 may transmit the signature information contained in the detected token transfer instruction to an electronic payment agent, request verification of the signature information, and transmit a remittance instruction to the common area network 10 using the signature key of the electronic payment agent that is transmitted if the signature information is determined to be valid.

[0138] (Setting transfer conditions) The payment instructions sent by the user devices 41, 42 according to the present embodiment can include information specifying the conditions for the token transfer. The operator device 31 can then automatically execute the token transfer instructions by means of a smart contract.

[0139] For example, the smart contract may include information specifying the time when the token transfer is to be performed. This allows the user devices 41 and 42 to set payment instructions so that the token transfer and coin transfer are performed by specifying the remittance time, such as two weeks later. Note that since the token transfer instruction sent by the operator device 31 is sent to the additional area network 30, the relay device 21 can send a remittance instruction to the common area network 10 so that the coin transfer is performed at the remittance time defined in the smart contract. In one example, the relay device 21 may send a transfer instruction specifying the conditions for the coin transfer based on the smart contract.

[0140] In another example, as a smart contract, information on the fluctuation rate of the price may be obtained from an external device and the actual price may be changed. In this case, the amount of tokens to be transferred may be determined by the operator device 31. For example, when the external device is the user device 42A of the payment destination and the seller provides a discount according to an event such as a time sale, the operator device 31 can obtain the discount rate from the user device 42A and change the amount of tokens to be transferred according to the discount rate. This makes it possible to adjust the supply and demand balance by setting a high discount rate for products in excess and transferring a small amount of money.

[0141] In another example, in a transaction of a non-fungible token (NFT), it is possible to specify that the transfer of the NFT is performed in conjunction with the transfer of the token as a smart contract. In this case, the smart contract includes an NFT identifier, and the operator device 31 may transmit a token transfer instruction to the additional area network 30 and transmit to an external network or the additional area network 30 to transfer the NFT based on the NFT identifier. This allows the smart contract to realize DvP (Delivery versus Payment) of the NFT.

[0142] <Other embodiments> In this embodiment, the token is an example of an electronic currency whose value is secured by electronic currency. However, the token may be treated as an incentive for users, such as points to be used for a specific service.

[0143] It is also possible to realize a process in which a program that realizes one or more functions of each of the above-mentioned embodiments is supplied to a system or device via a network or a storage medium, and one or more processors in a computer of the system or device read and execute the program. [Explanation of symbols]

[0144] 1: Electronic currency management system, 10: Common area network, 30: Additional area network, 11: Issuer device, 21: Relay device, 31: Operator device, 41: User device, 50: Management server

Claims

1. An electronic currency management system, comprising: A common area blockchain network that operates a first coin associated with a cash currency and a second coin associated with the cash currency and different from the first coin; A first additional domain blockchain network that operates a token associated with the first coin; a first transfer means for transferring, in response to a transfer of a predetermined amount of the tokens from a first user to a second user in the first additional domain blockchain network, a first coin corresponding to the predetermined amount in the common domain blockchain network from the first user to the second user; a second transfer means for transferring the second coins corresponding to the predetermined amount from a first issuer associated with the first user to a second issuer associated with the second user; An electronic currency management system comprising:

2. The electronic currency management system of claim 1, characterized in that the second transfer means transfers the second coin corresponding to the specified amount from the first issuer to the second issuer in response to the transfer of the first coin from the first user to the second user within the common area blockchain network.

3. The electronic currency management system of claim 1, characterized in that when the first transfer means transfers the first coins corresponding to the second predetermined amount from the third user associated with the first issuer to the fourth user associated with the second issuer in the common area blockchain network in response to a transfer of a second predetermined amount of the tokens from the third user associated with the first issuer to the fourth user associated with the second issuer in the first additional area blockchain network, the second transfer means transfers the second coins corresponding to the sum of the predetermined amount and the second predetermined amount from the first issuer to the second issuer.

4. The electronic currency management system of claim 1, characterized in that the second coin is a wholesale electronic currency for interbank payments.

Images