WO2022225022A1 - 電子通貨管理システム - Google Patents

電子通貨管理システム Download PDF

Info

Publication number
WO2022225022A1
WO2022225022A1 PCT/JP2022/018452 JP2022018452W WO2022225022A1 WO 2022225022 A1 WO2022225022 A1 WO 2022225022A1 JP 2022018452 W JP2022018452 W JP 2022018452W WO 2022225022 A1 WO2022225022 A1 WO 2022225022A1
Authority
WO
WIPO (PCT)
Prior art keywords
token
area network
issuer
additional area
electronic currency
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/JP2022/018452
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
健一 清水
和幸 辻
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Decurret Dcp Inc
Original Assignee
Decurret Dcp Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Decurret Dcp Inc filed Critical Decurret Dcp Inc
Priority to CN202280030292.6A priority Critical patent/CN117396907A/zh
Priority to EP22791793.7A priority patent/EP4328832A4/en
Publication of WO2022225022A1 publication Critical patent/WO2022225022A1/ja
Priority to US18/490,943 priority patent/US20240046251A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
    • G06Q20/367—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes involving electronic purses or money safes
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/04—Payment circuits
    • G06Q20/06—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
    • G06Q20/065—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash
    • G06Q20/0655—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash e-cash managed centrally
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/085—Payment architectures involving remote charge determination or related payment systems
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/381—Currency conversion
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
    • G06Q20/3821—Electronic credentials
    • G06Q20/38215—Use of certificates or encrypted proofs of transaction rights
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/389—Keeping log of transactions for guaranteeing non-repudiation of a transaction
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/42—Confirmation, e.g. check or permission by the legal debtor of payment
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/02—Banking, e.g. interest calculation or account maintenance
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q2220/00—Business processing using cryptography

Definitions

  • the present invention relates to an electronic currency management system.
  • Patent Literature 1 discloses a system for validating virtual currency transfers (transactions).
  • the present invention has been made in view of the above-mentioned problems, and aims to provide a technology that allows businesses wishing to issue electronic currency to easily manage the electronic currency.
  • an electronic currency management system is a common domain blockchain network that operates coins associated with cash currency; a first additional domain blockchain network that operates a first token associated with the coin; a first issuing means for issuing the coin to the common area blockchain network; granting means for associating the coin issued by the first issuing means with the first additional area blockchain network; a second issuing means for issuing the first token to the first additional area blockchain network based on the amount of the coins associated by the granting means; characterized by comprising
  • FIG. 2 is a diagram showing a hardware configuration of an issuer device, an operator device, a user device, and a relay device in FIG. 1; The figure which shows the issue processing of a token.
  • a conceptual diagram of a two-tier electronic currency The figure which shows an example of transfer of the value between additional area networks. The figure which shows an example of transfer of the value between additional area networks. The figure which shows the application example of an additional area network. The figure which shows an example of settlement between banks. The figure which shows an electronic currency management system.
  • FIG. 1 is a diagram showing a hardware configuration of an issuer device, an operator device, a user device, and a relay device in FIG. 1; The figure which shows the issue processing of a token.
  • a conceptual diagram of a two-tier electronic currency The figure which shows an example of transfer of the value between additional area networks.
  • the figure which shows an example of transfer of the value between additional area networks The figure which shows the application example of an additional area network.
  • FIG. 4 shows the process of registering an issuer device;
  • FIG. 10 is a diagram showing processing for registering an operator device;
  • FIG. 4 is a diagram showing a process of registering a user device;
  • the figure which shows a deposit process The figure which shows a deposit process.
  • the figure which shows the electronic currency management system after coin issuance The figure which shows the registration process of a token.
  • the figure which shows the issue processing of a token A diagram showing an electronic currency management system after token issuance.
  • FIG. 14 is a diagram showing the hardware configuration of the management server of FIG. 13;
  • the electronic currency management system 1 includes a common area network 10, issuer devices 11A, 11B, and 11C (hereinafter sometimes referred to as issuer devices 11 without distinction), relay devices 21A, 21B, and 21C ( Additional area networks 30A, 30B and 30C (hereinafter sometimes referred to as additional area network 30 without distinction), operator apparatuses 31A, 31B and 31C ( and user devices 41A, 41B and 41C (hereinafter sometimes referred to as user devices 41) and 42A, 42B and 42C (hereinafter referred to as operator device 31 without distinction) , may be referred to as user device 42 without distinction).
  • the common area network 10 is, for example, a distributed ledger network such as a blockchain, and is composed of nodes that operate a distributed ledger system including the issuer device 11.
  • the common area network 10 is used to execute operations such as transfer of electronic currencies (coins) 101 to 104 linked to the currency operated by the issuer device 11 .
  • the issuer device 11 is a device used by a company such as a bank that has an electronic currency issuance license.
  • the additional domain network 30 is, for example, a distributed ledger network such as a block chain, and is composed of nodes that operate a distributed ledger system including an operator device 31 and user devices 41 and 42 .
  • the additional area network 30 is used to provide operations such as transfer of tokens operated by the operator device 31 .
  • coin or token operations include issuance, transfer, redemption, and exchange.
  • the additional area network 30 is created for each individual use case according to the business needs of companies and the like.
  • 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 according to token operations in the additional area network 30. Also, the token of the additional area network 30 is operated according to the operation of the coin in the common area network 10 .
  • the operator device 31 is a device of a business entity that manages tokens in the additional area network 30 .
  • User devices 41 and 42 are devices of users who receive services provided in additional areas using tokens.
  • the issuer device 11A which is a bank, withdraws an existing bank deposit of 1 billion yen from the customer's bank account based on a request from the customer, the operation business operator 31A, who wants to issue 1 billion yen worth of electronic currency. , 1,000,000,000 Yen worth of white coins 101 are issued without specifying in which additional area they will be used.
  • the operator uses the application provided by the common area network 10 to allocate 200 million yen worth of white coins out of the 1 billion issued white coins 101 to the coins 102 associated with the additional area.
  • it issues an issue instruction to the additional area network 30A to issue a token (for example, a power token) corresponding to the coin 102.
  • a token for example, a power token
  • 200 million out of 1 billion white coins can only be used in the additional area network 30A (for example, additional area for power trading).
  • each additional area network 30 is assigned (locked) to the additional area. You can secure the value of your share. Also, at the moment of designation, a token is issued to the additional area network 30 as if it were issued with currency. This is not the substance of the electronic currency itself, but something like a proof of instruction that gives instructions to operate it.
  • the token issued by the additional area network 30A which is actually a "shadow of electronic currency" is moved on the additional area network 30A to circulate value.
  • the content of circulating circulation in the additional area network 30A is to asynchronously coordinate the operation of the coin 102 and the token in the additional area network 30A and the common area network 10.
  • the bank issues a white coin that does not specify which additional area to use, and specifies to use it in additional area 1.
  • Issuer device 11 includes processor 201 , memory 202 , storage 203 , network interface (I/F) 204 , and input/output I/F 205 .
  • the processor 201 is a control unit that controls the issuer device 11 as a whole.
  • the processor 201 includes at least one of a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), and a microcontroller that executes programs or an operating system (OS) stored in the storage 203 .
  • the memory 202 is composed of DRAM (Dynamic Random Access Memory), SRAM (Static Random Access Memory), etc. used as a work memory of the processor 201 .
  • the storage 203 includes an HDD (Hard Disk Drive) and an SSD (Solid State Drive) that store at least one of the programs executed by the processor 201, the OS, and data tables and setting values used by the programs.
  • the input/output I/F 205 is a user interface including an input device including at least one of a keyboard, a touch panel, and a microphone for accepting user operations, and an output device including at least one of a display, a speaker, and an LED.
  • the relay device 21 , the operator device 31 , and the user devices 41 and 42 are also explained as having the same hardware configuration as the issuer device 11 .
  • At least one of the issuer device 11, the relay device 21, the operator device 31, and the user devices 41 and 42 may not have the input/output I/F 205. At least one of the issuer device 11, the relay device 21, the operator device 31, and the user devices 41 and 42, which do not have an output I/F 205, receives operation instructions via the network I/F 204, Operation results may be output.
  • the operator pays the collateral to the issuer by sending collateral money 301 related to token management to the issuer's bank account.
  • the issuer device 11 issues an electronic currency (coin) 302 equivalent to collateral over the common area network 10 .
  • the coin 302 issued here is a white coin that indicates that the issuer is the issuer device 11 but is not associated with a token.
  • the white coin transfer instruction cannot be issued by the operator device 31 and can be issued only by the issuer device 11 .
  • the user of the additional area network notifies the bank, which is the issuer of the electronic currency, of the type and quantity of tokens to be issued, the identifier of the operator, etc., for example, through the application system of the bank.
  • the issuer device 11 associates the white coin 302 with the token 303 (colored) coin 304. can be transferred as
  • the relay device 21 monitors the common area 10 and can transfer the token 304 linked to the token 303 by detecting transfer in the additional area.
  • the relay device 21 that has detected 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.
  • the 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 the specified additional area network 30 is the sender or destination. Transfer is possible only for transactions that do, and transfer is not performed unless an instruction is received from a device in the additional area network 30 .
  • the additional area network 30 holds tokens embodying the reality of the electronic currency.
  • Electronic currency issued in the common area will be organized as a deposit.
  • tokens are issued as certificates that represent exchange transactions that transfer (substantial) electronic currency in the common area. Since the electronic currency itself is a deposit, it is possible to operate and consume the electronic currency.
  • digital currency transfer across additional areas can be realized without issuing and redeeming as follows.
  • the token of the additional area network 30A is reduced by the transfer amount.
  • FIG. 5 shows the processing of value transfer between different additional areas, with user device 41A and user device 41B associated with the same user as the remittance source and remittance destination.
  • user device 41A and user device 41B associated with the same user as the remittance source and remittance destination.
  • the common area only the additional area network to which the coin associated with the user changes, but the total amount of value does not change. Therefore, bank deposits will not be transferred.
  • electronic currency transfer across additional areas is realized between different users by the following procedure without issuing and redeeming.
  • 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.
  • the relay device 21A instructs the common area network 10 to transfer the electronic currency converted into white coins in (1) from the user A to the user B.
  • Whitecoin is associated with user B, and relay device 21B gives the token of additional area network 30B to user device 41B corresponding to user B;
  • a single common area network can support different additional area networks such as power trading platform (PF), retail platform, and electronic currency as additional areas.
  • PF power trading platform
  • retail platform e.g., a single common area network
  • electronic currency e.g., a single common area network
  • issuers can share the operation of a common area among multiple issuers, and can use electronic currency to transfer money between banks. Also, interoperability between additional area networks can be improved.
  • issuer Transfers will be made across 801A and 801B banks.
  • the issuer 801A reduces the deposit of the user 811A, and the issuer 801B increases the deposit of the user 811B, so that the settlement between the users 811A and 811B is carried out. That is, when the issuer 801A is instructed by the depositor to transfer the deposit across banks, the issuer 801A performs interbank settlement with the issuer 811B. In this case, due to the large amount of money involved in interbank settlement, banks rarely settle settlements with other banks in cash, and usually use deposits (in many cases, the bank's current account at the central bank) to make a transfer. Make interbank payments.
  • the issued electronic currency is withdrawn from the deposit of the user 811A, transferred to the account of the issuer 801A, and the electronic currency is issued to the user 811A. Subsequently, electronic currency transfer is performed from user 811A to 811B. At this point, only the liability of Issuer 801A has been transferred to Issuer 801B.
  • issuer 801A and 801B liquidation is required to balance assets and liabilities between issuers 801A and 801B.
  • Ordinary remittances are made by transferring funds from current accounts at the Bank of Japan.
  • Issuer 801B's assets and issuer 801A's liability electronic currency for interbank settlement are issued based on the credit of issuers 801A and 801B. It is possible to net settlement transactions between issuers 801A and 801B. It is possible to net settlement transactions between
  • FIG. 9 the electronic currency management system according to this embodiment will be described with reference to FIGS. 9 to 21.
  • FIG. 9 the electronic currency management system according to this embodiment will be described with reference to FIGS. 9 to 21.
  • the electronic currency management system 1 includes a common area network 10, issuer devices 11A, 11B, and 11C (hereinafter sometimes referred to as issuer devices 11 without distinction), relay devices 21A, 21B, and 21C ( Additional area networks 30A, 30B and 30C (hereinafter sometimes referred to as additional area network 30 without distinction), operator apparatuses 31A, 31B and 31C ( User devices 41A, 41B, and 41C (hereinafter, sometimes referred to as user devices 41 without distinction), and 42A, 42B, and 42C (hereinafter, referred to as operator device 31 without distinction) may be referred to as user device 42 without distinction), and management server 50 . Since the common area network 10, the issuer apparatus 11, the relay apparatus 21, the additional area network 30, the operator apparatus 31, and the user apparatuses 41 and 42 have already been described with reference to FIG. 1, the description thereof will be omitted.
  • the electronic currency is illustrated as existing in each issuer device 11 so that the management entity of the issued electronic currency is clear.
  • the common area network 10 is a blockchain network
  • electronic currency may be managed on a distributed ledger managed by multiple issuer devices 11 .
  • the electronic currency data itself is stored in the management server 50, and the issuer device 11 only has the operation authority to set attributes of the electronic currency. That is, in FIGS. 1 and 9, the electronic currency is only illustrated to show the correspondence with the issuer device that manages the electronic currency, and the device that stores the electronic data of the electronic currency is limited. not a thing
  • 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. Also, as the additional area network 30 is newly created, the relay device 21 is registered.
  • Management server 50 includes processor 201 , memory 202 , storage 203 , network interface (I/F) 204 , and input/output I/F 205 , similar to issuer device 11 , operator device 31 , and user device 41 . Since the processor 201, memory 202, storage 203, network interface (I/F) 204, and input/output I/F 205 have the same configuration as in FIG. 2, detailed description thereof will be omitted.
  • FIG. 10A The processing executed by the electronic currency management system 1 will be described below with reference to FIGS. 10A to 20.
  • FIG. 10A The processing executed by the electronic currency management system 1 will be described below with reference to FIGS. 10A to 20.
  • the issuer concludes a platform usage contract with the management company of the management server 50 .
  • the management business operator of the management server 50 registers management account information for using the electronic currency management system in the management server 50 (S1001).
  • the management server 50 notifies the issuer device 11 of the management account including the ID of the user account (S1002).
  • the issuer device 11 instructs the management server 50 to create an issuer account having coin issuance authority (S1003).
  • the management server 50 creates an issuer account by registering the account information in the issuer database (S1004), and transmits the issuer ID to the issuer device 11 (S1005).
  • the operating business makes a platform usage contract with the management business of the management server 50 .
  • the management company of the management server 50 registers management account information corresponding to the operation company in the management server 50 (S1021).
  • the management server 50 notifies the operator's device 31 of the user account (S1022).
  • the operation business operator device 31 instructs the management server 50 to create an operation business operator account that has token issuance authority (S1023).
  • the management server 50 transmits the operator ID corresponding to the account of the operator to the operator device 31 (S1024).
  • the user concludes a platform usage contract with the management company of the management server 50 .
  • the management business operator of the management server 50 registers management account information corresponding to the user in the management server 50 (S1041).
  • the management server 50 notifies the user devices 41 and 42 of the user account (S1042).
  • the user device 31 instructs the management server 50 to create a user account that has authority to purchase, remit, and receive tokens (S1043).
  • the management server 50 transmits the user ID corresponding to the user's account to the user devices 41 and 42 (S1044).
  • the issuer device 11 registers the deposit information in the management server 50 (S1101).
  • the registered deposit information includes the issuer ID and the collateral amount.
  • the coin ID associated with the issuer ID may be registered as the deposit information.
  • the management server 50 registers the deposit information in the deposit information database (S1102).
  • the identifier (deposit information ID) in the deposit information database corresponding to the registered deposit is transmitted to the issuer device 11 (S1103).
  • the deposit information database may also manage the remaining amount of deposit. As a result, even if a smaller quantity of coins than the quantity that can be issued by depositing is issued after a predetermined amount of money has been deposited, the amount corresponding to the quantity of issued coins will remain in the deposit. By reducing the amount, it is possible to manage the remaining number of coins that can be issued.
  • the management server 50 transmits a response to the issuer device 11 (S1123).
  • the deposit processing shown in FIG. 11A may not be necessary.
  • the issuer device 11 is operated by a company different from the bank company, such as a fund transfer company, the deposit processing shown in FIG. 11A may be necessary. That is, whether or not issuer device 11 performs the deposit process may be determined according to the regulations to which the issuer complies, such as the operator of issuer device 11 .
  • the issuer device 11 transmits a coin issuance request to the management server 50 .
  • the coin issue request includes the issuer ID, coin ID, and issue quantity.
  • the management server 50 uses the issuer ID included in the coin issuance request to acquire the deposit information with the matching issuer ID from the deposit information registered in the deposit information database (S1202). Subsequently, the collateral amount is specified from the deposit information, and the number of coins that can be issued is determined (S1203). As described above, when the deposit information includes the remaining amount of deposit, the number of coins that can be issued may be determined based on the remaining amount of deposit.
  • the management server 50 issues coins to the wallet of the issuer on the common area network 10 of the issuer device 11 (S1204). . Subsequently, the issue amount is notified to the issuer device 11 (S1205).
  • FIG. 13 the state of the wallet after coin issuance will be described.
  • the issuer device 11A issues coins and no other coins are issued.
  • description will be given assuming that there are two additional area networks.
  • the coin issued in S1204 of FIG. 12 is the 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.
  • 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 that backs up the value of the token (backing coin).
  • the management server 50 stores the operator ID, token name, token symbol, and backing coin included in the token registration request in the token database as the token ID. They are associated and registered (S1402).
  • the registered token ID is transmitted to the operator device 31 as a response to the registration request (S1403).
  • the operator can issue, depreciate, and transfer the token corresponding to the token ID.
  • the operator 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.
  • the operator device 31 sends the token to the issuer device 11 without going through the relay device 21 . You may send a request for issuance.
  • the token issuance request includes the token ID and token quantity.
  • the issuer device 11 transmits a token issue 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 the token quantity included in the token issuance instruction can be issued (S1504). Determining whether or not tokens corresponding to the token quantity can be issued may include determining whether issuer device 11 has white coins corresponding to the token quantity in the wallet of issuer device 11 . Alternatively, it may include determining whether the issuer holds financial assets corresponding to the token quantity to be issued to the operator's account.
  • the management server 50 determines that the token included in the token issuance instruction can be issued, the management server 50 transmits an issuance notification to the issuer device 11 (S1505), and the additional area network 30 corresponding to the token ID. A token is issued to the wallet of the operator 31 (S1506).
  • the issuer device 11 Upon receiving the issue notification, the issuer device 11 links the white coins held in the wallet of the issuer device 11 to the additional area network 30 (S1507). If an attribute tag can be attached to the coin, the attribute tag, which is not set at the time of issuance, is set to the ID of the operator, etc., so that the coin is associated with the additional area network 30 (colored). Can be converted into coins. In the present embodiment, by associating the attribute tag of the coin with the additional area network 30, for example, when the operation business operator device 31 has a wallet in the common area network 10, the wallet of the issuer device 11 is sent to the operation business operator device 31. Coins may be associated with the additional area network 30 by transferring coins corresponding to the number of tokens held by the operation business operator device 31 to the wallet.
  • the owner of the coin is set to the operator device 31.
  • colored coins can be changed in ownership, but must be converted to white coins in order to be transferred or depreciated.
  • each additional area network 30 By designating the quantity of tokens desired to be issued and allocating (locking) each additional area network 30 as indicated by coins 103 and 104 in the common area network 10, the value of the additional area can be secured. . Also, at the moment of designation, a token is issued to the additional area network 30 as if it were issued with currency. This is not the substance of the electronic currency itself, but something like a proof of instruction that gives instructions to operate it. Coins issued to the common area network 10 are locked by specifying the identifier of the additional area network 30 used by the user, and only transactions with the specified additional area network 30 as the sender or destination can be transferred, and No relocation takes place without an instruction from a device in the additional area network 30 .
  • FIG. 16 shows a case where the additional area network 30A issues tokens with the issuer 11A as the issuer after FIG.
  • the issuer 11A has a wallet of the issuer 11A on the common area network 10 and holds the white coin 1301.
  • the colored coin 1601 corresponding to the additional area network 30A is held, and the coin 1601 can only be used for exchanging tokens with the additional area network 30A as the remittance source or remittance destination.
  • the operator device 31A has an issued token 1611 .
  • the user device 41A transmits to the relay device 21A a token purchase request including the user ID of the token, the type of token to be purchased, the quantity of tokens to be purchased, and payment information specifying the payment method.
  • a token purchase request is transferred to the provider device 31A (S1701).
  • Payment information may include the method of payment, such as direct debit, and the type of payment, such as whether the payment is 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 sends the token to the operator device 31A without going through the relay device 21A. You may submit a purchase request.
  • the operator device 31A determines whether or not to transfer the tokens according to the purchase request based on the payment information and the type and quantity of the tokens (S1702). When the operation business operator device 31A determines that the token included in the purchase request can be purchased with the payment included in the payment information, the operation business operator device 31A purchases the specified token in the specified quantity from the wallet of the operation business operator device 31A.
  • a transfer instruction to transfer only to the wallet of the user device 41A is sent to the additional area network 30A.
  • a token transfer instruction is sent to the issuer device 11A (S1703).
  • the token transfer instruction includes the transfer source, transfer destination, token type, and token quantity.
  • the relay device 21A When the transfer instruction is transmitted over the additional area network 30A, the relay device 21A detects the transfer instruction (S1704) and identifies the transfer source and transfer destination of the token (S1705). Once specified, 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 tokens converted into cash currency and the value of coins converted into cash currency, issuer device 11A is instructed to transfer coins for the value of tokens to be transferred converted into cash currency.
  • the issuer device 11A which has received the transfer instruction from the relay device 21A, designates the owner of the coin owned by the operation operator device 31 of the transfer source among the colored coins 102 corresponding to the additional area 1 as the transfer destination. is set in the person's device 41A (S1707). If the common area network 10 is a block chain network, it transmits a coin transfer instruction from the transfer source to the transfer destination. As a result, the value can be transferred even on the common area network 10 that secures the value.
  • payment processing from the user device 41A to the operator device 31A is separately performed. This may be done before purchasing the tokens or after the token transfer is completed.
  • FIG. 18 is a diagram showing a situation in which the user device 41A purchases tokens from the operator device 31A after FIG.
  • the issuer 11A has a wallet of the issuer 11A on the common area network 10 and holds the white coin 1301. It 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.
  • tokens 1611 and 1812 are held in the wallets of operator device 31A and user device 41A of additional area network 30A.
  • token transfer processing example 1 Also in the token transfer instruction, value can be transferred by linking the common area network 10 and the additional area network 30 in the same manner as in the above-described token purchase process.
  • the user device 41A transmits a transfer instruction with the user device 42A as the transfer destination (S1901).
  • the transfer instruction will be described as an order for transactions to the additional area network 30A, which is a block chain network. may be transmitted to the operator device 31A.
  • the token transfer instruction includes the transfer source, transfer destination, token type, and token quantity.
  • the relay device 21A detects the transmitted transfer instruction (S1902), and based on the transfer source, transfer destination, token type, and token quantity, description will be made with reference to FIG. In the same way as the above, a transfer instruction is transmitted to the issuer device 11A (S1903).
  • the issuer device 11A sets the user device 42A as the owner of the colored coins 1802 linked to the additional area network 30A.
  • Token transfer processing example 2 Next, an example of transferring a token from the user device 42A of the additional area network 30A to the user device 42B of the additional area network 30B will be described with reference to FIG. In the example of FIG. 20, the token is transferred between the user devices of different users. It is the same.
  • the user device 42A instructs the additional area network 30A to transfer the token from the user device 42A of the additional area network 30A to the user device 42B of the additional area network 30B (S2001).
  • the relay device 21A instructs the issuer device 11A to transfer coins from the additional area network 30A to the additional area network 30B (S2003).
  • the issuer device 11A converts coins corresponding to the number of tokens to be transferred into white coins (S2004), and transfers the converted white coins to the issuer device 11B. Move (S2005). Further, the issuer device 11A instructs the issuer device 11B to set the owner of the coins corresponding to the tokens of the transferred quantity in the user device 41B and associate them with the additional area 30B. Issuer device 11B associates the transferred white coin with additional area network 30B and sets the owner to user device 41B (S2006).
  • the relay device 21B which has detected the instruction from the issuer device 11A to the issuer device 11B, transmits the transfer of the token corresponding to the additional region network 30B from the user device 42A to 42B on the additional region network 30B. do. This allows the token to be transferred to the wallet of the user device 42B.
  • the relay device 21 detects a transfer in the common area network 10 and transfers the token on the additional area network 30 according to the detected transfer. This enables token transfers between additional area networks by transferring coins on the common area network 10 .
  • the additional area networks 30A and 30B are associated with different issuer apparatuses 11A and 11B.
  • additional area networks 30A, 30B may be associated with the same issuer device 11A.
  • the issuer device 11A is associated with the additional area network 30A, and after the owner converts the colored coins of the issuer device 11A into white coins, the converted white coins are associated with the additional area network 30B. allows the transfer of tokens between additional domain networks.
  • the common area network 10 and the additional area network 30 are circulated through the additional area network 30A. Cooperate asynchronously.
  • the electronic currency issued to the common area network is arranged as a deposit.
  • tokens are issued as certificates that represent exchange transactions that transfer (substantial) electronic currency in the common area. Since the electronic currency itself is a deposit, it is possible to operate and consume the electronic currency.
  • a token is an example of electronic currency whose value is secured by electronic currency.
  • tokens may be treated for incentive purposes, such as points used for specific services from the user's point of view.
  • a program that implements one or more functions of each of the above-described embodiments is supplied to a system or device via a network or storage medium, and one or more processors in the computer of the system or device read and execute the program. processing is also feasible.
  • 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

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Technology Law (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Security & Cryptography (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
PCT/JP2022/018452 2021-04-22 2022-04-21 電子通貨管理システム Ceased WO2022225022A1 (ja)

Priority Applications (3)

Application Number Priority Date Filing Date Title
CN202280030292.6A CN117396907A (zh) 2021-04-22 2022-04-21 电子货币管理系统
EP22791793.7A EP4328832A4 (en) 2021-04-22 2022-04-21 ELECTRONIC MONEY MANAGEMENT SYSTEM
US18/490,943 US20240046251A1 (en) 2021-04-22 2023-10-20 Electronic currency management system

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
JP2021072732 2021-04-22
JP2021-072732 2021-04-22
JP2021-136647 2021-08-24
JP2021136647A JP7089143B1 (ja) 2021-04-22 2021-08-24 電子通貨管理システム

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/490,943 Continuation US20240046251A1 (en) 2021-04-22 2023-10-20 Electronic currency management system

Publications (1)

Publication Number Publication Date
WO2022225022A1 true WO2022225022A1 (ja) 2022-10-27

Family

ID=82115461

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2022/018452 Ceased WO2022225022A1 (ja) 2021-04-22 2022-04-21 電子通貨管理システム

Country Status (5)

Country Link
US (1) US20240046251A1 (https=)
EP (1) EP4328832A4 (https=)
JP (3) JP7089143B1 (https=)
CN (1) CN117396907A (https=)
WO (1) WO2022225022A1 (https=)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4435699A1 (en) * 2023-03-21 2024-09-25 Giesecke+Devrient advance52 GmbH Secure transaction unit, token reference register, electronic payment transaction system and method for registering of token

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP7525099B2 (ja) * 2021-07-05 2024-07-30 株式会社デジタルアセットマーケッツ サービストークン取引支援プラットフォーム
JP7847099B2 (ja) * 2023-03-22 2026-04-16 株式会社日立製作所 管理システム、管理方法、及び管理プログラム
WO2025239348A1 (ja) * 2024-05-14 2025-11-20 パナソニックＩｐマネジメント株式会社 情報処理方法、情報処理装置、および、プログラム

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2017097812A (ja) * 2015-11-28 2017-06-01 ソフトバンク株式会社 仮想通貨システム
JP6521421B1 (ja) 2018-07-03 2019-05-29 スタンダードトランザクション株式会社 通貨情報処理装置および通貨情報処理システム
JP2019212256A (ja) * 2018-06-01 2019-12-12 ウィズダム インターナショナル コー． リミテッドＸＷＩＳＤＯＭ Ｉｎｔｅｒｎａｔｉｏｎａｌ Ｃｏ． Ｌｔｄ． 仮想通貨と法定通貨のサービス統合プラットフォーム
JP2021012460A (ja) * 2019-07-04 2021-02-04 三菱Ｕｆｊ信託銀行株式会社 トークン発行信託システム
JP2021072732A (ja) 2019-10-31 2021-05-06 アイシン・エィ・ダブリュ株式会社 ロータの製造方法
JP2021136647A (ja) 2020-02-28 2021-09-13 日本電波工業株式会社 計測装置

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10812274B2 (en) * 2015-05-07 2020-10-20 Blockstream Corporation Transferring ledger assets between blockchains via pegged sidechains
US11727391B2 (en) 2016-04-11 2023-08-15 Nchain Licensing Ag Computer-implemented methods and systems for validating tokens for blockchain-based cryptocurrencies
US10929842B1 (en) * 2018-03-05 2021-02-23 Winklevoss Ip, Llc System, method and program product for depositing and withdrawing stable value digital assets in exchange for fiat
US11416931B2 (en) * 2018-03-16 2022-08-16 Salt Blockchain Inc. Investment fund token ownership
US20200013027A1 (en) * 2018-07-06 2020-01-09 Decentralized Finance Labs, Inc. Hybrid proof of work and proof of stake consensus to reduce circulating tokens in a blockchain system
WO2020240771A1 (ja) 2019-05-30 2020-12-03 日本電気株式会社 仮想通貨システム、端末、サーバ、仮想通貨の取引方法及びプログラム
US11080687B2 (en) * 2019-07-15 2021-08-03 BlocX LLC Systems and methods for blockchain-based transaction settlement
MX2022002685A (es) * 2019-09-06 2022-06-02 Bosonic Inc Sistema y método para proporcionar un proceso de registro basado en una cadena de bloques.
KR102157171B1 (ko) * 2020-04-07 2020-09-17 송은하 소유권자 불특정 공동자산에 대한 블록체인기반 지분 실거래 시스템 및 그 방법
JP6738113B1 (ja) 2020-05-20 2020-08-12 ゼン グローバル リミテッドＺＥＮ Ｇｌｏｂａｌ Ｌｉｍｉｔｅｄ 金銭管理システム、金銭管理方法、寄付管理システム、寄付管理方法及びプログラム

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2017097812A (ja) * 2015-11-28 2017-06-01 ソフトバンク株式会社 仮想通貨システム
JP2019212256A (ja) * 2018-06-01 2019-12-12 ウィズダム インターナショナル コー． リミテッドＸＷＩＳＤＯＭ Ｉｎｔｅｒｎａｔｉｏｎａｌ Ｃｏ． Ｌｔｄ． 仮想通貨と法定通貨のサービス統合プラットフォーム
JP6521421B1 (ja) 2018-07-03 2019-05-29 スタンダードトランザクション株式会社 通貨情報処理装置および通貨情報処理システム
JP2021012460A (ja) * 2019-07-04 2021-02-04 三菱Ｕｆｊ信託銀行株式会社 トークン発行信託システム
JP2021072732A (ja) 2019-10-31 2021-05-06 アイシン・エィ・ダブリュ株式会社 ロータの製造方法
JP2021136647A (ja) 2020-02-28 2021-09-13 日本電波工業株式会社 計測装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4328832A4

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4435699A1 (en) * 2023-03-21 2024-09-25 Giesecke+Devrient advance52 GmbH Secure transaction unit, token reference register, electronic payment transaction system and method for registering of token

Also Published As

Publication number Publication date
EP4328832A4 (en) 2024-03-06
US20240046251A1 (en) 2024-02-08
EP4328832A1 (en) 2024-02-28
JP2022167892A (ja) 2022-11-04
JP7578300B2 (ja) 2024-11-06
CN117396907A (zh) 2024-01-12
JP7089143B1 (ja) 2022-06-22
JP2022167763A (ja) 2022-11-04
JP7169420B1 (ja) 2022-11-10
JP2022167748A (ja) 2022-11-04

Similar Documents

Publication Publication Date Title
JP7089143B1 (ja) 電子通貨管理システム
US11386493B2 (en) System and method for cryptocurrency trading
US20250005540A1 (en) Intelligent payment routing and payment generation
JP2019506075A (ja) ブロックチェーンベースのトークナイゼーションを用いた交換
JP2019506074A (ja) ブロックチェーンを使用してピアツーピア分散型台帳におけるエンティティを効率的な移転のための方法およびシステム
US20090012899A1 (en) Systems and methods for generating and managing a linked deposit-only account identifier
US20230041182A1 (en) Transaction Delegation Method, Transaction Delegation System, and Computer Readable Medium
JP7326536B1 (ja) 情報処理装置、情報処理方法及び情報処理プログラム
TW202011314A (zh) 用於管理來自複數個使用者之通訊請求的方法、系統、及裝置
CN110689350A (zh) 电子平台供应链金融流转方法、系统、终端设备及介质
JP2024035056A (ja) 情報処理装置、情報処理方法及び情報処理プログラム
CN118056215A (zh) 加密货币的综合地址生成和自动转换
JP2022512074A (ja) 購入管理システムおよび方法
CN107527225A (zh) 用于高效处理资源在账户之间的大规模传播的系统和方法
JP7660912B2 (ja) 情報処理装置および情報処理方法
JP7796684B2 (ja) 情報処理装置、情報処理方法及び情報処理プログラム
CN119948514A (zh) 用于商业交易支付的系统
CN117337440A (zh) 信息处理装置及信息处理方法
JP7623755B1 (ja) デジタルアセット管理システムおよびその制御方法
JP7695643B2 (ja) 情報処理システム、情報処理方法、およびプログラム
US20240152910A1 (en) Systems and methods for use in token management
JP7140900B1 (ja) 情報処理装置、情報処理方法及び情報処理プログラム
JP2024134964A (ja) 管理システム、管理方法、及び管理プログラム
JP2024140176A (ja) 情報処理装置、情報処理方法及び情報処理プログラム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22791793

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202280030292.6

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 2022791793

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2022791793

Country of ref document: EP

Effective date: 20231122