Method of verifying initiator or benefit and electronic device performing same
By generating and matching hash values of the initiator and beneficiary for authentication, the authentication problem during virtual asset transfer is solved, security and reliability are improved, and information leakage risks are reduced.
Patent Information
- Application Number
- CN202380029688.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-10-21
- Filing Date
- 2023-03-22
- Publication Date
- 2024-11-12
AI Technical Summary
In the process of transferring virtual assets, it is difficult to effectively verify the identities of the initiator and beneficiary in the process of virtual asset transfer, and there are problems of information leakage and insufficient security.
By generating hash values of the initiator and beneficiary’s full names and date of birth, matching verification is performed to ensure that virtual assets are transferred only when the identities of both parties are matched and personal information is technically protected.
It improves the security and reliability of virtual asset transfers, reduces the risk of personal information leakage, and prevents unintentional mismatch caused by differences in naming rules.
Smart Images

Figure CN118946899A_ABST
Abstract
Description
Technical Field
[0001] Example embodiments relate to a method for authenticating an originator and / or a beneficiary when transferring virtual assets and an electronic device performing the method. Background Art
[0002] With the development of blockchain technology, virtual assets represented by Bitcoin are considered to be borderless assets, and the number of places where Bitcoin can be used (for example, offline stores and online stores) is also increasing. Virtual assets are sometimes exchanged with physical assets, and their value fluctuates from time to time. In addition, the types of virtual assets are also diversified, and virtual asset service providers (VASPs) that act as agents for virtual asset transactions and manage virtual asset transactions are also increasing.
[0003] In this regard, reference may be made to the prior art Korean Patent Publication No. 10-2022-0025634A. Summary of the invention
[0004] Technical Solution
[0005] One aspect provides a method for verifying an initiator and / or a beneficiary and an electronic device for executing the method. More specifically, when transferring virtual assets, one aspect provides a method for verifying that an initiator and / or a beneficiary complies with the obligation to provide information when transferring virtual assets and technically protects personal information, and an electronic device for executing the method.
[0006] The technical problems to be solved by the present application are not limited to the above-mentioned technical problems, and other technical problems can be inferred from the following example implementations. BRIEF DESCRIPTION OF THE DRAWINGS
[0007] These and / or other aspects, features and advantages of the present invention will become apparent and more readily understood through the following description of example embodiments in conjunction with the accompanying drawings, in which:
[0008] Figure 1 A system according to an example implementation is shown;
[0009] Figure 2A and Figure 2B is a flowchart for explaining a process of verifying a beneficiary or an initiator by an electronic device according to an example embodiment;
[0010] Figure 3A and Figure 3B is a flowchart for explaining a process of verifying a beneficiary or an initiator by an electronic device according to an example embodiment;
[0011] Figure 4A and Figure 4Bis a flowchart for explaining a process of verifying a beneficiary or an initiator by an electronic device according to an example embodiment;
[0012] Figure 5A and Figure 5B An example of a verification request message according to an example implementation is shown;
[0013] Figure 6 shows an example of a response message according to an example implementation;
[0014] 7A to 7H is a diagram for explaining a process in which a VASP server identifies whether a hash value of a full name matches according to an example embodiment;
[0015] Figure 8 is a flowchart for explaining a process of verifying a beneficiary by an electronic device according to an example embodiment;
[0016] Fig. 9 is a flowchart for explaining a process of authenticating an initiator by an electronic device according to an example embodiment;
[0017] Fig.10 is a flowchart for explaining a process of verifying a beneficiary by an electronic device according to an example embodiment;
[0018] Fig.11 is a flowchart for explaining a process of authenticating an initiator by an electronic device according to an example embodiment;
[0019] Fig.12 is a flow chart of a method of authenticating a beneficiary performed by an electronic device according to an example embodiment;
[0020] Fig.13 is a flowchart of a method of authenticating an initiator performed by an electronic device according to an example embodiment; and
[0021] Fig.14 is a block diagram of an electronic device according to an example embodiment. DETAILED DESCRIPTION
[0022] According to one aspect, a method for verifying a beneficiary performed by an electronic device is provided, the method comprising: identifying information about the transfer of virtual assets, the information including the full name data of the initiator, the date of birth (DOB) data of the initiator, and the beneficiary virtual asset address; identifying a hash value set of the initiator's full name generated based on the initiator's full name data and a hash value set of the initiator's DOB generated based on the initiator's DOB data; sending a verification request message to a beneficiary server, the verification request message including the hash value set of the initiator's full name, the hash value set of the initiator's DOB, and the beneficiary virtual asset address; and, receiving a response message from the beneficiary server, the response message including verification result information generated based on the verification request message regarding whether the initiator matches the beneficiary, wherein, based on the verification result information, determining whether to transfer the virtual asset from the initiator's virtual asset address of the initiator to the beneficiary virtual asset address.
[0023] According to an example embodiment, the verification request message may also include at least one of the following: a value representing the type of the verification target, a value representing the type of the virtual asset, an auxiliary virtual asset address according to the type of the virtual asset, or a hash salt value associated with at least one of a set of hash values of the initiator's full name or a set of hash values of the initiator's DOB.
[0024] According to an example embodiment, the verification result information may include at least one of the following information: information indicating that an address matching the beneficiary virtual asset address or the auxiliary virtual asset address is not identified in the virtual asset addresses associated with the beneficiary server; information about a mismatch between a set of hash values of the initiator's full name and a set of hash values of the beneficiary's full name generated based on the beneficiary's full name data corresponding to the beneficiary virtual asset address, or information about a mismatch between a set of hash values of the initiator's DOB and a set of hash values of the beneficiary's DOB generated based on the beneficiary's DOB data, or information indicating that the beneficiary is verified to match the initiator.
[0025] According to an example embodiment, in a case where the response message includes information indicating that the beneficiary is verified as matching the initiator, it can be determined to execute the transfer of virtual assets, and in a case where the response message includes one of the following information, it can be determined to prevent the transfer of virtual assets: information indicating that an address matching the beneficiary virtual asset address or the auxiliary virtual asset address is not identified in the virtual asset addresses associated with the beneficiary server, information regarding a mismatch between a set of hash values for the initiator's full name and a set of hash values for the beneficiary's full name generated based on the beneficiary's full name data corresponding to the beneficiary's virtual asset address, or information regarding a mismatch between a set of hash values for the initiator's DOB and a set of hash values for the beneficiary's DOB generated based on the beneficiary's DOB data.
[0026] According to an example implementation, identifying the set of hash values for the originator's full name and the set of hash values for the originator's DOB may include removing spaces from the originator's full name data.
[0027] According to an example implementation, identifying the set of hash values of the initiator's full name and the set of hash values of the initiator's DOB may include changing letter case of characters included in the initiator's full name data to a configured letter case.
[0028] According to an example embodiment, the set of hash values of the initiator's full name may include at least one of the following hash values: a first hash value generated based on the initiator's full name information consisting of a single entry in the order of a first name and a last name; a second hash value generated based on the initiator's full name information consisting of a single entry in the order of a last name and a first name; or a third hash value generated based on the initiator's full name information consisting of multiple entries including a last name, a first name, and at least one middle name.
[0029] According to an example embodiment, in a case where any hash value included in a set of hash values of the beneficiary's full name generated based on the beneficiary's full name data corresponding to the beneficiary's virtual asset address does not match any one of the first hash value, the second hash value, and the third hash value, the verification result information may include information about the mismatch between the set of hash values of the initiator's full name and the set of hash values of the beneficiary's full name.
[0030] According to an example embodiment, the set of hash values of the beneficiary's full name generated based on the full name data of the beneficiary corresponding to the beneficiary's virtual asset address may include at least one of the following hash values: a fourth hash value, which is generated based on the beneficiary's full name information consisting of a single entry in the order of first name and last name; a fifth hash value, which is generated based on the beneficiary's full name information consisting of a single entry in the order of last name and first name; or a sixth hash value, which is generated based on the beneficiary's full name information consisting of multiple entries including a last name, a first name and at least one middle name.
[0031] According to an example embodiment, in a case where any hash value included in the hash value set of the initiator's full name does not match any hash value of the fourth hash value, the fifth hash value, and the sixth hash value, the verification result information may include information of the mismatch between the hash value set of the initiator's full name and the hash value set of the beneficiary's full name.
[0032] According to an example embodiment, regarding the beneficiary virtual asset address, regardless of whether at least one character included in the beneficiary virtual asset address is a lowercase letter or an uppercase letter, it can be identified whether there is an address matching the beneficiary virtual asset address in the database of the beneficiary server.
[0033] According to example embodiments, regarding the beneficiary virtual asset address, a configuration prefix included in the beneficiary virtual asset address may be removed, and it may be identified whether there is an address matching the beneficiary virtual asset address in a database of the beneficiary server.
[0034] According to another aspect, a method for verifying an initiator performed by an electronic device is provided, the method comprising: identifying a transferred virtual asset and a beneficiary virtual asset address; identifying the full name data of the beneficiary corresponding to the beneficiary virtual asset address and the DOB data of the beneficiary; identifying a hash value set of the beneficiary's full name generated based on the beneficiary's full name data and a hash value set of the beneficiary's DOB generated based on the beneficiary's DOB data; sending a verification request message to an initiator server, the verification request message including a hash value set of the beneficiary's full name, a hash value set of the beneficiary's DOB and the beneficiary virtual asset address; and, receiving a response message from the initiator server, the response message including verification result information generated based on the verification request message regarding whether the beneficiary matches the initiator.
[0035] According to an example embodiment, the verification request message may also include at least one of the following: a transaction identification value corresponding to the transfer of the virtual asset, a value indicating the type of the verification target, a value indicating the type of the virtual asset, an auxiliary virtual asset address according to the type of the virtual asset, and a hash salt value associated with at least one of a set of hash values of the beneficiary's full name and a set of hash values of the beneficiary's DOB.
[0036] According to an example embodiment, the verification result information may include at least one of the following information: information indicating that a value matching the transaction identification value is not identified in the transaction identification value associated with the initiator server, information indicating that an address matching the beneficiary's virtual asset address or the auxiliary virtual asset address is not identified in the virtual asset address associated with the initiator server, information about a mismatch between a set of hash values of the beneficiary's full name and a set of hash values of the initiator's full name generated based on the initiator's full name data corresponding to the beneficiary's virtual asset address or the transaction identification value, or information about a mismatch between a set of hash values of the beneficiary's DOB and a set of hash values of the initiator's DOB generated based on the initiator's DOB data, or information indicating that the initiator is verified as matching the beneficiary.
[0037] According to an example embodiment, the method may further include: when the verification result information includes information indicating that the initiator is verified to match the beneficiary, reflecting the virtual asset to the balance of the beneficiary's virtual asset address based on the transaction identification value at each configuration time.
[0038] According to an example embodiment, regarding the transaction identification value, whether at least one character included in the transaction identification value is a lowercase letter or an uppercase letter, it may be identified whether there is a value matching the transaction identification value in the database of the initiator server.
[0039] According to an example embodiment, regarding the transaction identification value, when the type of the transaction identification value includes an identifier type and a hash value type, the hash value type transaction identification value may be used to identify whether there is a value matching the transaction identification value in the database of the initiator server.
[0040] According to an example embodiment, regarding the transaction identification value, the transaction identification value including a leading zero may be used to identify whether there is a value matching the transaction identification value in the database of the initiator server.
[0041] According to another aspect, an electronic device is provided, which includes one or more processors and a memory for storing one or more instructions executed by the one or more processors, wherein the one or more processors are configured by executing the one or more instructions to: identify information about the transfer of virtual assets, the information including the full name data of the initiator, the date of birth (DOB) data of the initiator, and the virtual asset address of the beneficiary; identify a hash value set of the initiator's full name generated based on the full name data of the initiator and a hash value set of the initiator's DOB generated based on the DOB data of the initiator; send a verification request message to a beneficiary server, the verification request message including the hash value set of the initiator's full name, the hash value set of the initiator's DOB, and the virtual asset address of the beneficiary; and receive a response message from the beneficiary server, the response message including verification result information generated based on the verification request message about whether the initiator matches the beneficiary, wherein, based on the verification result information, it is determined whether to transfer the virtual asset from the initiator's virtual asset address of the initiator to the beneficiary virtual asset address.
[0042] According to another aspect, an electronic device is provided, which includes one or more processors and a memory for storing one or more instructions executed by the one or more processors, wherein the one or more processors are configured by executing the one or more instructions to: identify the transferred virtual assets and the beneficiary virtual asset address; identify the full name data of the beneficiary corresponding to the beneficiary virtual asset address and the DOB data of the beneficiary; identify a hash value set of the beneficiary's full name generated based on the beneficiary's full name data and a hash value set of the beneficiary's DOB generated based on the beneficiary's DOB data; send a verification request message to an initiator server, the verification request message including the hash value set of the beneficiary's full name, the hash value set of the beneficiary's DOB and the beneficiary virtual asset address; and receive a response message from the initiator server, the response message including verification result information generated based on the verification request message on whether the beneficiary matches the initiator.
[0043] According to another aspect, there is provided a computer-readable non-transitory recording medium having a program implementing the method executed by an electronic device.
[0044] Additional aspects of example embodiments are set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the disclosure.
[0045] According to example embodiments, when transferring virtual assets, the initiator and / or beneficiary can be effectively verified while complying with the obligation to provide information when transferring virtual assets and technically protecting personal information. More specifically, since the initiator VASP server and / or the beneficiary VASP server sends hashed personal information (e.g., name or date of birth) instead of the original personal information, the risk of exposing the personal information of the initiator and / or the beneficiary can be reduced. In addition, it is possible to verify whether the initiator matches the beneficiary without sending the personal information of the initiator and / or the beneficiary.
[0046] According to example embodiments, since virtual assets are transferred only when it is verified that the initiator and the beneficiary match (eg, the initiator and the beneficiary are the same person), the security and reliability of the virtual asset transfer may be improved.
[0047] According to an example embodiment, since virtual assets are reflected in the balance of the beneficiary's virtual asset address only when it is verified that the initiator and the beneficiary match (for example, the initiator and the beneficiary are the same person), the security and reliability of virtual asset transfer can be improved.
[0048] According to example embodiments, in the process of verifying an initiator and / or a beneficiary, an unintentional mismatch that may occur due to the absence of a standard naming convention that may reflect the reality of local full names for each country may be technically prevented.
[0049] According to example embodiments, in the process of verifying an originator and / or a beneficiary, it is technically possible to prevent an unintentional mismatch that may occur in the absence of a standard name of a value or symbol representing the type of a virtual asset.
[0050] The technical benefits of the present invention are not limited thereto, and those skilled in the art will clearly understand other technical benefits not described based on the description in the specification and claims.
[0051] Invention Mode
[0052] When considering the functions in the present disclosure, the terms used in the example embodiments are selected from the general terms currently widely used, where possible. However, these terms may vary according to the intentions of those skilled in the art or precedents, the emergence of new technologies, etc. In addition, in some cases, there are also terms arbitrarily selected by the applicant, and in these cases, the meaning will be described in detail in the corresponding description. Therefore, the terms used in the present disclosure should be defined based on the meaning of the term and the content of the present disclosure rather than the simple name of the term.
[0053] Throughout the specification, when a part is described as “including” or “comprising” or “having” a certain component, it does not exclude other components but may further include other components unless otherwise stated.
[0054] The expression “at least one of a, b, and c” described throughout the specification may include “a alone,” “b alone,” “c alone,” “a and b,” “a and c,” “b and c,” or “all of a, b, and c.”
[0055] In the present disclosure, a "terminal" may be implemented as, for example, a computer or portable terminal capable of accessing a server or other terminal through a network. Here, a computer may include, for example, a notebook, a desktop computer, and / or a laptop computer equipped with a web browser. A portable terminal may be a wireless communication device that ensures portability and mobility, including (but not limited to) any type of handheld wireless communication device, such as a tablet PC, a smart phone, a communication-based terminal (such as International Mobile Telecommunications (IMT)), code division multiple access (CDMA), W-code division multiple access (W-CDMA), long term evolution (LTE), etc.
[0056] Hereinafter, example embodiments will be described in detail with reference to the accompanying drawings so that those skilled in the art to which the present disclosure pertains can easily practice the present disclosure. However, example embodiments in the present disclosure may be implemented in many different forms and are not limited to the example embodiments described herein.
[0057] In the present disclosure, a virtual asset is an electronic token with economic value that can be electronically traded or transferred, or can indicate rights associated with it. However, a virtual asset may be referred to as a digital asset, digital currency, virtual currency, or cryptocurrency, but is not limited thereto.
[0058] In this disclosure, VASP refers to a person and / or entity that conducts business in any of the following 1) to 6) related to virtual assets:
[0059] 1) Purchase or sale of virtual assets;
[0060] 2) The act of exchanging virtual assets for other virtual assets;
[0061] 3) Acts of transferring virtual assets specified by presidential decree;
[0062] 4) Acts of storing or managing virtual assets;
[0063] 5) the act of acting as an agent or arranging or acting as an agent for the acts of 1) and 2); and
[0064] 6) Other acts that are likely to be used for money laundering and financing of public intimidation related to virtual assets as specified by the Presidential Decree.
[0065] However, the actions that a VASP can perform in virtual asset-related businesses are not limited to these.
[0066] In the present disclosure, a virtual asset address refers to a unique identification number electronically generated to manage the transfer records and storage details of virtual assets. However, a virtual asset address may be referred to as a wallet address, an electronic wallet address, or a virtual asset wallet address, and is not limited thereto.
[0067] In the present disclosure, the auxiliary virtual asset address is a unique identifier for distinguishing a user account, and the existence of the auxiliary virtual asset address may be different depending on the type of virtual asset. In other words, the auxiliary virtual asset address may be used to distinguish different virtual asset types of the same user's account. For example, depending on the type of virtual asset owned by the user, there may be one or more auxiliary virtual asset addresses corresponding to one account of the user. However, the auxiliary virtual asset address may be referred to as a secondary address, a destination tag, a tag, a memo, or a message, and the auxiliary virtual asset address is not limited thereto.
[0068] Hereinafter, example embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.
[0069] Figure 1 A system according to an example implementation is shown.
[0070] Reference Figure 1The system may include at least one of an electronic device 100, a beneficiary VASP server 120, a remittance VASP server 140, a user terminal 160, or a network 180. Figure 1 In the system shown, only the elements related to the exemplary embodiments of the present disclosure are shown. Therefore, those skilled in the art can understand that, except for Figure 1 In addition to the elements shown, other common elements may also be included.
[0071] The electronic device 100 may be used as an intermediary to verify the initiator of the virtual asset transfer or the beneficiary of the virtual asset reception. For example, the electronic device 100 may send a verification request message including a hash value of the full name, a hash value of the DOB, and a verification request message of the beneficiary's virtual asset address to the beneficiary VASP server 120 or the initiator VASP server 140. Alternatively, the electronic device 100 may receive a response message including verification result information generated based on the verification request message from the beneficiary VASP server 120 or the initiator VASP server 140, and may send the response message to the initiator VASP server 140 or the beneficiary VASP server 120.
[0072] In addition, the electronic device 100 may include at least one of an enclave server existing inside the VASP or an application programming interface (API) server existing outside the VASP. Alternatively, the electronic device 100 may include an integrated server existing inside the VASP, but is not limited thereto. Alternatively, the electronic device 100 may be implemented as a single entity combined with the beneficiary VASP server 120 or the initiator VASP server 140.
[0073] The beneficiary VASP server 120 is a server existing inside the beneficiary VASP, and the beneficiary VASP server 120 can provide services related to selling, purchasing or transferring virtual assets to the user. For example, regarding the service of transferring virtual assets, the beneficiary VASP server 120 can send a verification request for the initiator to the electronic device 100, or can send a beneficiary verification result to the electronic device 100.
[0074] The initiator VASP server 140 is a server existing inside the initiator VASP, and the initiator VASP server 140 can provide services related to selling, purchasing or transferring virtual assets to the user. For example, regarding the service of transferring virtual assets, the initiator VASP server 140 can send a verification request for the beneficiary to the electronic device 100, or send a verification result for the initiator to the electronic device 100.
[0075] However, beneficiary VASP server 120 may represent a server or entity that exists solely external to the beneficiary VASP, and originator VASP server 140 may represent a server or entity that exists solely external to the originator VASP.
[0076] The user terminal 160 is a terminal used by each user, and the user can use each user terminal 160 to access the beneficiary VASP or services provided by the beneficiary VASP through the network 180. For example, the user can use the application installed on its corresponding user terminal 160 to sell, buy or transfer virtual assets.
[0077] The electronic device 100, the beneficiary VASP server 120, the initiator VASP server 140 and the user terminal 160 can communicate with each other within the network 180. The network 180 includes a local area network (LAN), a wide area network (WAN), a value-added network (VAN), a mobile radio communication network, a satellite communication network and a combination thereof. The network is a comprehensive data communication network that enables Figure 1 Each network component entity shown can communicate smoothly with each other, and may include wired Internet, wireless Internet, and mobile wireless communication networks. Wireless communication is, for example, wireless LAN (Wi-Fi), Bluetooth, low-power Bluetooth, Zigbee, WFD (Wi-Fi Direct), ultra-wideband (UWB), infrared data association (IrDA), and near field communication (NFC), but is not limited thereto.
[0078] Figure 2A and Figure 2B is a flowchart for explaining a process of authenticating a beneficiary or an initiator by the electronic device 100 according to an example embodiment.
[0079] According to an example embodiment, a user may transfer virtual assets in his / her wallet managed by an initiator VASP to a user wallet managed by a beneficiary VASP using a user terminal 160. In other words, an account of the initiator VASP that transfers the virtual assets (e.g., the initiator's account) and an account of the beneficiary VASP that receives the virtual assets (e.g., the beneficiary's account) may correspond to the same person.
[0080] Figure 2AThe process of verifying a beneficiary by an electronic device 100 according to an example embodiment is shown. Here, the electronic device 100 may refer to a server present inside an initiator VASP. For example, the electronic device 100 may be implemented as an entity physically coupled to an initiator VASP server 140 inside an initiator VASP. In this case, the electronic device 100 and the initiator VASP server 140 may be functionally or logically separated. For another example, the electronic device 100 and the initiator VASP server 140 exist inside the initiator VASP, but may be implemented as physically different entities and functionally or logically different entities.
[0081] In operation S200, according to an example embodiment, the electronic device 100 may receive information about the transfer of the virtual asset from the initiator VASP server 140. For example, the initiator VASP server 140 may receive at least some of a value representing the type of virtual asset that the user wishes to transfer, information about the beneficiary VASP, and a beneficiary virtual asset address from the user terminal 160. Thereafter, the initiator VASP server 140 may send at least some of a value representing the type of virtual asset, information about the beneficiary VASP, a beneficiary virtual asset address, the initiator's full name data, and the initiator's DOB data to the electronic device 100. Here, the initiator VASP server 140 may send an auxiliary virtual asset address to the electronic device 100 according to the type of the virtual asset.
[0082] In operation S205, according to an example embodiment, the electronic device 100 may identify a hash value of the full name of the originator and a hash value of the DOB of the originator. For example, the electronic device 100 may generate a hash value of the full name of the originator and a hash value of the DOB of the originator by hashing each of the full name data of the originator and the DOB data of the originator received from the originator VASP server 140. Here, the electronic device 100 may use a KECCAK-256 algorithm as a hash function or a hash algorithm, but the hash algorithm used is not limited thereto.
[0083] Furthermore, the electronic device 100 may identify the hash value of the initiator's full name and the hash value of the initiator's DOB by identifying the hash value of the initiator's full name and the hash value of the initiator's DOB, or may obtain the hash value of the initiator's full name and the hash value of the initiator's DOB.
[0084] According to an example embodiment, the electronic device 100 may generate a hash value set of the initiator's full name including one or more hash values of the initiator's full name by hashing the initiator's full name data. For example, the electronic device 100 may generate a hash value by hashing the initiator's full name information consisting of a single entry in the order of the first name and the last name, or by hashing the initiator's full name information consisting of a single entry in the order of the last name and the first name. Alternatively, the electronic device 100 may generate a hash value by hashing the initiator's full name in Korean, or by hashing the initiator's full name in English. This will be described below with reference to 7A to 7D This is described in detail.
[0085] In operation S210, according to an example embodiment, the electronic device 100 may send a verification request message to the beneficiary VASP server 120. For example, the electronic device 100 may send a verification request message to the beneficiary VASP server 120, the verification request message including at least some of an identification value of the verification request message, a value indicating the type of the verification target, a value indicating the type of the virtual asset, information about the initiator VASP, a beneficiary virtual asset address, a hash value of the initiator's full name, a hash value of the initiator's DOB, and a hash salt value. Here, the electronic device 100 may also send an auxiliary virtual asset address to the beneficiary VASP server 120 according to the type of the virtual asset. Figure 5A and Figure 5B Details of the values included in the authentication request message are described in detail.
[0086] In operation S215, according to an example embodiment, the beneficiary VASP server 120 may verify whether the initiator and the beneficiary match. Meanwhile, the case where the initiator and the beneficiary match may include the case where the initiator and the beneficiary are the same person.
[0087] For example, the beneficiary VASP server 120 may identify the full name data of the beneficiary and the DOB data of the beneficiary corresponding to the beneficiary virtual asset address, may hash each of the full name data of the beneficiary and the DOB data of the beneficiary, and may generate a hash value of the full name of the beneficiary and a hash value of the DOB of the beneficiary. Here, the beneficiary VASP server 120 may identify whether the hash value of the full name of the initiator received from the electronic device 100 matches the hash value of the full name of the beneficiary, and may identify whether the hash value of the DOB of the initiator received from the electronic device 100 matches the hash value of the DOB of the beneficiary.
[0088] According to an example embodiment, the beneficiary VASP server 120 may identify whether there is an address that matches the beneficiary virtual asset address or the auxiliary virtual asset address. For example, the beneficiary VASP server 120 may identify whether there is an address in the database that is the same as the beneficiary virtual asset address received from the electronic device 100. Alternatively, if the beneficiary VASP server 120 also receives the auxiliary virtual asset address from the electronic device 100, the beneficiary VASP server 120 may identify whether there is an address in the database that matches the beneficiary virtual asset address and the auxiliary virtual asset address.
[0089] According to an example embodiment, regardless of whether at least one character included in the beneficiary virtual asset address or the auxiliary virtual asset address is a lowercase letter or an uppercase letter, the beneficiary VASP server 120 can identify whether there is an address that matches the beneficiary virtual asset address or the auxiliary virtual asset address. Therefore, an unintentional mismatch that may be caused by distinguishing uppercase letters from lowercase letters can be prevented.
[0090] According to an example embodiment, the beneficiary VASP server 120 may remove a configuration prefix included in the beneficiary virtual asset address, and may identify whether there is an address that matches the beneficiary virtual asset address. For example, the beneficiary VASP server 120 may remove prefixes such as "Bitcoin Cash" and "Electronic Cash" included in the beneficiary virtual asset address, and may identify whether there is an address that matches the beneficiary virtual asset address. Therefore, an unintentional mismatch between a VASP that stores the beneficiary virtual asset address after the prefix is removed according to the VASP's policy and a VASP that stores the beneficiary virtual asset address including the prefix according to the VASP's policy can be prevented.
[0091] According to an example embodiment, the beneficiary VASP server 120 may identify the full name data of the beneficiary and the DOB data of the beneficiary. For example, if it is identified that there is an address in the database that matches the beneficiary virtual asset address received from the electronic device 100, the beneficiary VASP server 120 may identify the full name data of the beneficiary and the DOB data of the beneficiary corresponding to the beneficiary virtual asset address.
[0092] According to an example embodiment, the beneficiary VASP server 120 may identify whether a hash value of one or more names of the initiator matches a hash value of one or more names of the beneficiary. For example, the beneficiary VASP server 120 may receive a hash value of the full name of the initiator from the electronic device 100, and may identify whether the hash value of the full name of the initiator matches a hash value of the full name of the beneficiary. Alternatively, the beneficiary VASP server 120 may receive a set of hash values of the full names of the initiator including the hash values of the one or more full names of the initiator from the electronic device 100, and may identify whether the hash value of the full name of the beneficiary matches any one of the hash values of the one or more full names of the initiator. The beneficiary VASP server 120 may receive a hash value of the full name of the initiator from the electronic device 100, and may identify whether the hash value of the full name of the initiator matches any one of the hash values of the one or more full names of the beneficiary. The following will refer to 7A to 7D This is described in detail.
[0093] According to an example embodiment, the method of verifying the beneficiary may be performed based on a hash value of information other than the DOB. For example, the electronic device 100 may identify a hash value of the mobile phone number of the initiator generated based on the mobile phone number data of the initiator, and the beneficiary VASP server 120 may identify whether the mobile phone number of the beneficiary matches the hash value. However, the type of information that can be used to verify the beneficiary is not limited thereto.
[0094] According to an example embodiment, the beneficiary VASP server 120 can verify whether the initiator matches the beneficiary, regardless of the type of the virtual asset. For example, if the value representing the type of the virtual asset included in the verification request message is LUNA2, and if the type of the virtual asset held by the beneficiary VASP server 120 is LUNA, there may not be a value matching LUNA2. In this case, the beneficiary VASP server 120 can skip the process of identifying whether there is a value that is the same as the value representing the type of the virtual asset, and can verify whether the initiator and the beneficiary match. Therefore, unintentional mismatches that may occur due to the absence of a standard naming convention for a value or symbol representing the type of a virtual asset can be prevented.
[0095] In operation S220, according to an example embodiment, the electronic device 100 may receive a response message including verification result information generated based on the verification request message from the beneficiary VASP server 120. For example, the electronic device 100 may receive a response message from the beneficiary VASP server 120, the response message including at least some of the following information: information indicating that an address matching the beneficiary virtual asset address or the auxiliary virtual asset address is not identified, information regarding a mismatch between a hash value of the initiator's full name and a hash value of the beneficiary's full name, information regarding a mismatch between a hash value of the initiator's DOB and a hash value of the beneficiary's DOB, and information indicating that the beneficiary is verified to match the initiator. This will refer to Figure 6 Detailed description.
[0096] In operation S225, according to an example embodiment, the electronic device 100 may transmit a response message to the originator VASP server 140. For example, the electronic device 100 may transmit the response message received from the beneficiary VASP server 120 to the originator VASP server 140.
[0097] In operation S230, the initiator VASP server 140 may transfer the virtual asset to the beneficiary virtual asset address based on the verification result information included in the received response message. For example, if the response message received from the electronic device 100 includes information indicating that the beneficiary is verified as matching the initiator, the initiator VASP server 140 may transfer the virtual asset to the beneficiary virtual asset address according to the information received from the user terminal 160. Alternatively, if the response message received from the electronic device 100 includes information other than the information indicating that the beneficiary is verified as matching the initiator (e.g., information indicating that an address matching the beneficiary virtual asset address or the auxiliary virtual asset address is not identified, information about a mismatch between a hash value of the initiator's full name and a hash value of the beneficiary's full name, and information about a mismatch between a hash value of the initiator's DOB and a hash value of the beneficiary's DOB), at least some of the information), the initiator VASP server 140 may not transfer the virtual asset to the beneficiary virtual asset address.
[0098] In this way, when the initiator VASP server sends hashed personal information (name or date of birth) instead of original personal information, the risk of exposing the initiator's personal information can be reduced. In addition, it is possible to verify whether the initiator matches the beneficiary without sending the initiator's personal information.
[0099] In this way, since the virtual assets are transferred only when it is verified that the initiator and the beneficiary match (for example, the initiator and the beneficiary are the same person), the security and reliability of the virtual asset transfer can be improved.
[0100] Figure 2B The process of verifying the initiator by the electronic device 100 according to an example embodiment is shown. Here, the electronic device 100 may refer to a server existing inside the beneficiary VASP. For example, the electronic device 100 may be implemented as an entity physically coupled to the beneficiary VASP server 120 inside the beneficiary VASP. In this case, the electronic device 100 and the beneficiary VASP server 120 may be functionally or logically separated. For another example, the electronic device 100 and the beneficiary VASP server 120 exist inside the beneficiary VASP, but may be implemented as physically different entities and functionally or logically different entities. Figure 2B In the description, the Figure 2A Description of duplicate description.
[0101] In operation S250, according to an embodiment, the beneficiary VASP server 120 may identify the virtual asset transferred to the beneficiary virtual asset address. For example, the beneficiary VASP server 120 may identify the deposit or virtual asset transferred to the beneficiary virtual asset address by the initiator VASP server 140. However, before the initiator's verification is completed, the beneficiary VASP server 120 may not reflect the transferred virtual asset in the beneficiary's balance status that the beneficiary can check through the beneficiary's account.
[0102] In operation S255, according to an example embodiment, the electronic device 100 may receive information about the transfer of the virtual asset from the beneficiary VASP server 120. For example, the electronic device 100 may receive at least some of a value indicating the type of the virtual asset, information about the beneficiary VASP, a beneficiary virtual asset address, a full name data of the beneficiary, and DOB data of the beneficiary from the beneficiary VASP server 120. Here, the beneficiary VASP server 120 may also send an auxiliary virtual asset address to the electronic device 100 according to the type of the virtual asset.
[0103] In operation S260, according to an example embodiment, the electronic device 100 may identify a hash value of the full name of the beneficiary and a hash value of the DOB of the beneficiary. For example, by hashing each of the full name data of the beneficiary and the DOB data of the beneficiary received from the beneficiary VASP server 120, the electronic device 100 may generate a hash value of the full name of the beneficiary and a hash value of the DOB of the beneficiary.
[0104] According to an example embodiment, the electronic device 100 may generate a hash value set of the beneficiary's full name including one or more hash values of the beneficiary's full name by hashing the beneficiary's full name data. For example, the electronic device 100 may generate a hash value by hashing the beneficiary's full name information consisting of a single entry in the order of first name and last name, or may generate a hash value by hashing the beneficiary's full name information consisting of a single entry in the order of last name and first name. Alternatively, the electronic device 100 may generate a hash value by hashing the beneficiary's full name in Korean, or may generate a hash value by hashing the beneficiary's full name in English. This will refer to 7A to 7D Detailed description.
[0105] In operation S265, according to an example embodiment, the electronic device 100 may send a verification request message to the initiator VASP server 140. For example, the electronic device 100 may send a verification request message to the initiator VASP server 140, the verification request message including at least some of an identification value of the verification request message, a value indicating the type of the verification target, a value indicating the type of the virtual asset, information about the beneficiary VASP, a beneficiary virtual asset address, a hash value of the beneficiary's full name, a hash value of the beneficiary's DOB, a transaction identification value corresponding to the transfer of the virtual asset, and a hash salt value. Here, the electronic device 100 may also send an auxiliary virtual asset address to the initiator VASP server 140 according to the type of the virtual asset. Reference will be made to Figure 5A and Figure 5B Detailed Description Details of the values included in the authentication request message are described in detail.
[0106] In operation S270, according to an example embodiment, the initiator VASP server 140 may verify whether the beneficiary and the initiator match. Meanwhile, the case where the beneficiary and the initiator match may include the case where the beneficiary and the initiator are the same person.
[0107] For example, the initiator VASP server 140 may identify the initiator's full name data and the initiator's DOB data corresponding to the beneficiary virtual asset address or the transaction identification value, may hash each of the initiator's full name data and the initiator's DOB data, and may generate a hash value of the initiator's full name and a hash value of the initiator's DOB. Thereafter, the initiator VASP server 140 may identify whether the hash value of the beneficiary's full name received from the electronic device 100 matches the hash value of the initiator's full name, and whether the hash value of the beneficiary's DOB received from the electronic device 100 matches the hash value of the initiator's DOB.
[0108] According to an example embodiment, the initiator VASP server 140 may identify whether there is a value matching the transaction identification value. For example, the initiator VASP server 140 may identify whether there is a value identical to the transaction identification value received from the electronic device 100 in the database.
[0109] According to an example embodiment, regardless of whether at least one character included in the transaction identification value is a lowercase letter or an uppercase letter, the initiator VASP server 140 can identify whether there is a value matching the transaction identification value. Therefore, an unintentional mismatch that may be caused by distinguishing uppercase letters from lowercase letters can be prevented.
[0110] According to an example embodiment, if the type of the transaction identification value includes an identifier type and a hash value type, the initiator VASP server 140 can identify whether there is a value matching the transaction identification value by using the transaction identification value of the hash value type. For example, if the transaction identification value of the identification type is different from the transaction identification value of the hash value type, the initiator VASP server 140 can identify whether there is a value matching the transaction identification value by using the transaction identification value of the hash value type. Therefore, an unintentional mismatch between the VASP requesting verification and the VASP performing verification can be prevented.
[0111] According to an example embodiment, the initiator VASP server 140 can identify whether there is a value matching the transaction identification value by using the transaction identification value including the leading zero value. For example, if the identification value of the transaction is 0.0.15852-1648154322-083000000, the initiator VASP server 140 can identify whether there is a value matching the transaction identification value by using the transaction identification value including 83000000. Therefore, an unintentional mismatch that may occur between a VASP that removes the leading zero value for data storage according to the policy of the VASP and a VASP that includes the leading zero value for data storage can be prevented.
[0112] According to an example embodiment, the initiator VASP server 140 may identify whether there is an address that matches the beneficiary virtual asset address or the auxiliary virtual asset address. For example, the initiator VASP server 140 may identify whether there is an address in the database that is the same as the beneficiary virtual asset address received from the electronic device 100. Alternatively, if the initiator VASP server 140 also receives the auxiliary virtual asset address from the electronic device 100, the initiator VASP server 140 may identify whether there is an address in the database that matches the beneficiary virtual asset address and the auxiliary virtual asset address.
[0113] According to an example embodiment, the initiator VASP server 140 may identify the initiator's full name data and the initiator's DOB data. For example, if it is identified that there is a value matching the transaction identification value received from the electronic device 100 and an address matching the beneficiary virtual asset address in the database, the initiator VASP server 140 may identify the initiator's full name data and the initiator's DOB data corresponding to the transaction identification value or the beneficiary virtual asset address.
[0114] According to an example embodiment, the initiator VASP server 140 may identify whether a hash value of one or more names of a beneficiary matches a hash value of one or more names of the initiator. For example, the initiator VASP server 140 may receive a hash value of a full name of the beneficiary from the electronic device 100, and may identify whether the hash value of the full name of the beneficiary matches a hash value of a full name of the initiator. Alternatively, the initiator VASP server 140 may receive a set of hash values of the full names of the beneficiaries including hash values of one or more full names of the beneficiaries from the electronic device 100, and may identify whether the hash value of the full name of the initiator matches any one of the hash values of the one or more full names of the beneficiaries. The initiator VASP server 140 may receive a hash value of a full name of the beneficiary from the electronic device 100, and may identify whether the hash value of the full name of the initiator matches any one of the hash values of the one or more full names of the initiator. This will refer to 7A to 7D Detailed description.
[0115] According to an example embodiment, the method of verifying the initiator may be performed based on a hash value of information other than the DOB. For example, the electronic device 100 may identify a hash value of the mobile phone number of the beneficiary generated based on the mobile phone number data of the beneficiary, and the initiator VASP server 140 may identify whether the mobile phone number of the initiator matches the hash value. However, the type of information that can be used to verify the initiator is not limited thereto.
[0116] According to an example embodiment, the initiator VASP server 140 can verify whether the beneficiary matches the initiator, regardless of the type of the virtual asset. For example, if the value indicating the type of the virtual asset included in the verification request message is LUNA, and if the type of the virtual asset held by the initiator VASP server 140 is LUNA2, there may not be a value that matches LUNA. In this case, the initiator VASP server 140 can skip the process of identifying whether there is a value that matches the value representing the type of the virtual asset, and can verify whether the beneficiary and the initiator match. Therefore, unintentional mismatches that may occur due to the absence of a standard naming convention for a value or symbol representing the type of a virtual asset can be prevented.
[0117] In addition, according to an example embodiment, the initiator VASP server 140 may use the initiator virtual asset address instead of the transaction identification value or the beneficiary virtual asset address to identify the initiator's full name data and the initiator's DOB data. For example, in operation S250, after identifying the transferred virtual asset, the beneficiary VASP server 120 may identify the initiator virtual asset address. In operation S255, the beneficiary VASP server 120 may send information about the transfer of the virtual asset including the initiator virtual asset address to the electronic device 100, and in operation S265, the electronic device 100 may send a verification request message including the initiator virtual asset address to the initiator VASP server 140. The initiator VASP server 140 may identify the initiator's full name data and the initiator's DOB data corresponding to the received initiator virtual asset address.
[0118] In operation S275, according to an example embodiment, the electronic device 100 may receive a response message from the initiator VASP server 140 that includes verification result information generated based on the verification request message. For example, the electronic device 100 may receive a response message from the initiator VASP server 140 that includes at least some of the following information: information indicating that a value matching the transaction identification value is not identified, information indicating that an address matching the beneficiary virtual asset address or the auxiliary virtual asset address is not identified, information regarding a mismatch between a hash value of the beneficiary's full name and a hash value of the initiator's full name, information regarding a mismatch between a hash value of the beneficiary's DOB and a hash value of the initiator's DOB, and information indicating that the initiator is verified to match the beneficiary. This will refer to Figure 6 Detailed description.
[0119] In operation S280, according to an example embodiment, the electronic device 100 may transmit a response message to the beneficiary VASP server 120. For example, the electronic device 100 may transmit the response message received from the initiator VASP server 140 to the beneficiary VASP server 120.
[0120] In operation S285, according to an example embodiment, the beneficiary VASP server 120 may reflect the virtual assets transferred to the beneficiary's virtual asset address on the balance of the beneficiary's virtual asset address based on the verification result information included in the response message. For example, if the response message received from the electronic device 100 includes information indicating that the initiator is verified as matching the beneficiary, the beneficiary VASP server 120 may reflect the transferred virtual assets on the balance of the beneficiary's virtual asset address at each configuration time or whenever a response message is received. Alternatively, if the response message received from the electronic device 100 includes information in addition to information indicating that the originator is verified as a match to the beneficiary (for example, at least some of information indicating that a value matching the transaction identification value is not identified, information indicating that an address matching the initiator's virtual asset address or the auxiliary virtual asset address is not identified, information regarding a mismatch between a hash value of the initiator's full name and a hash value of the beneficiary's full name, and information regarding a mismatch between a hash value of the initiator's DOB and a hash value of the beneficiary's DOB), the beneficiary VASP server 120 may not reflect the transferred virtual assets on the balance of the beneficiary's virtual asset address.
[0121] In this way, when the beneficiary VASP server sends hashed personal information (name or date of birth) instead of original personal information, the risk of exposing the beneficiary's personal information can be reduced. In addition, it is possible to verify whether the beneficiary matches the initiator without sending the beneficiary's personal information.
[0122] In this way, since the virtual assets are only reflected in the balance of the beneficiary's virtual asset address when it is verified that the initiator and the beneficiary match (for example, the initiator and the beneficiary are the same person), the security and reliability of the virtual asset transfer can be improved.
[0123] Figure 3A and Figure 3B 1 is a flowchart for explaining a process of verifying a beneficiary or an initiator by the electronic device 100 according to an example embodiment. Figure 3A and Figure 3B , will briefly describe or omit Figure 2A and Figure 2B Description of duplicate description.
[0124] According to an example embodiment, a user may transfer virtual assets in his / her wallet managed by an initiator VASP to a wallet of the user managed by a beneficiary VASP using the user terminal 160. In other words, the account of the initiator VASP that transfers the virtual assets (e.g., the account of the initiator) and the account of the beneficiary VASP that receives the virtual assets (e.g., the account of the beneficiary) may correspond to the same person.
[0125] Figure 3A The process of verifying a beneficiary by the electronic device 100 according to an example embodiment is shown. Here, the enclave server 102 can communicate with the API server 104, which is a server existing inside the initiator VASP, and the API server 104 can be a server existing outside the initiator VASP and can act as a message broker. In addition, the electronic device 100 can instruct the enclave server 102 or the API server 104.
[0126] In operation S300, according to an example embodiment, the enclave server 102 may receive information about the transfer of the virtual asset from the initiator VASP server 140. For example, the initiator VASP server 140 may receive at least some of a value indicating the type of virtual asset that the user wishes to transfer, information about the beneficiary VASP, and a beneficiary virtual asset address from the user terminal 160. Hereinafter, the initiator VASP server 140 may send at least some of a value indicating the type of virtual asset, information about the beneficiary VASP, a beneficiary virtual asset address, the initiator's full name data, and the initiator's DOB data to the enclave server 102. Here, the initiator VASP server 140 may also send an auxiliary virtual asset address to the enclave server 102 according to the type of the virtual asset.
[0127] In operation S305, according to an example embodiment, the enclave server 102 may identify a hash value of the originator's full name and a hash value of the originator's DOB. For example, the enclave server 102 may hash each of the originator's full name data and the originator's DOB data received from the originator VASP server 140 to generate a hash value of the originator's full name and a hash value of the originator's DOB.
[0128] In operation S310, according to an example embodiment, the enclave server 102 may send a beneficiary verification request and related information to the API server 104. For example, the enclave server 102 may send at least some of a value indicating the type of the verification target, a value indicating the type of the virtual asset, information about the beneficiary VASP, a beneficiary virtual asset address, a hash value of the initiator's full name, a hash value of the initiator's DOB, and a hash salt value to the API server 104. Here, the enclave server 102 may also send an auxiliary virtual asset address to the API server 104 according to the type of the virtual asset.
[0129] In operation S315, according to an example embodiment, the API server 104 may send a verification request message to the beneficiary VASP server 120. For example, the API server 104 may send a verification request message to the beneficiary VASP server 120, the verification request message including the API access key, the identification value of the verification request message, the value indicating the type of the verification target, the value indicating the type of the virtual asset, information about the initiator VASP, the beneficiary virtual asset address, the hash value of the initiator's full name, the hash value of the initiator's DOB, and at least some of the hash salt value. Here, the API server 104 may also send an auxiliary virtual asset address to the beneficiary VASP server 120 according to the type of the virtual asset. Figure 5A and Figure 5B Describes the details of the values included in the authentication request message.
[0130] In operation S320, according to an example embodiment, the beneficiary VASP server 120 may verify whether the initiator and the beneficiary match. For example, the beneficiary VASP server 120 may identify the full name data of the beneficiary and the DOB data of the beneficiary corresponding to the beneficiary virtual asset address, may hash each of the full name data of the beneficiary and the DOB data of the beneficiary, and may generate a hash value of the full name of the beneficiary and a hash value of the DOB of the beneficiary. Thereafter, the beneficiary VASP server 120 may identify whether the hash value of the full name of the initiator received from the API server 104 matches the hash value of the full name of the beneficiary, and whether the hash value of the DOB of the initiator received from the API server 104 matches the hash value of the DOB of the beneficiary. More specific operations of the beneficiary VASP server 120 to verify whether the initiator and the beneficiary match are repeated with the description of operation S215 of FIG. 2 and are therefore omitted.
[0131] In operation S325, according to an example embodiment, the API server 104 may receive a response message including verification result information generated based on the verification request message from the beneficiary VASP server 120. For example, the API server 104 may receive a response message from the beneficiary VASP server 120, the response message including at least some of the following information: information indicating that an address matching the beneficiary virtual asset address or the auxiliary virtual asset address is not identified, information about a mismatch between a hash value of the initiator's full name and a hash value of the beneficiary's full name, information about a mismatch between a hash value of the initiator's DOB and a hash value of the beneficiary's DOB, and information indicating that the beneficiary is verified to match the initiator. This will refer to Figure 6 Detailed description.
[0132] In operation S330, according to an example embodiment, the API server 104 may send a response message to the enclave server 102. For example, the API server 104 may send a response message received from the beneficiary VASP server 120 to the enclave server 102.
[0133] In operation S335, according to an example embodiment, the enclave server 102 may send a response message to the originator VASP server 140. For example, the enclave server 102 may send the response message received from the API server 104 to the originator VASP server 140.
[0134] In operation S340, the initiator VASP server 140 may transfer the virtual asset to the beneficiary virtual asset address based on the verification result information included in the received response message. For example, if the response message received from the enclave server 102 includes information indicating that the beneficiary is verified as matching the initiator, the initiator VASP server 140 may transfer the virtual asset to the beneficiary virtual asset address according to the information received from the user terminal 160. Alternatively, if the response message received from the enclave server 102 includes information other than the information indicating that the beneficiary is verified as matching the initiator, the initiator VASP server 140 may not transfer the virtual asset to the beneficiary virtual asset address.
[0135] Figure 3B The process of verifying the initiator by the electronic device 100 according to an example embodiment is shown. Here, the enclave server 106 can communicate with the API server 108, which is a server existing inside the beneficiary VASP, and the API server 108 can be a server existing outside the beneficiary VASP and can act as a message broker. At the same time, the electronic device 100 can instruct the enclave server 106 or the API server 108.
[0136] In operation S350, according to an example embodiment, the beneficiary VASP server 120 may identify the virtual assets transferred to the beneficiary virtual asset address. For example, the beneficiary VASP server 120 may identify the virtual assets or deposits transferred by the initiator VASP server 140 to the beneficiary virtual asset address.
[0137] In operation S355, according to an example embodiment, the enclave server 106 may receive information about the transfer of the virtual asset from the beneficiary VASP server 120. For example, the enclave server 106 may receive at least some of a value indicating the type of the virtual asset, information about the beneficiary VASP, a beneficiary virtual asset address, a full name data of the beneficiary, and DOB data of the beneficiary from the beneficiary VASP server 120. Here, the beneficiary VASP server 120 may also send an auxiliary virtual asset address to the enclave server 106 according to the type of the virtual asset.
[0138] In operation S360, according to an example embodiment, the enclave server 106 may identify a hash value of the full name of the beneficiary and a hash value of the DOB of the beneficiary. For example, the enclave server 106 may hash the full name data of the beneficiary and the DOB data of the beneficiary received from the beneficiary VASP server 120 to generate a hash value of the full name of the beneficiary and a hash value of the DOB of the beneficiary.
[0139] In operation S365, according to an example embodiment, the enclave server 106 may send an initiator verification request and related information to the API server 108. For example, the enclave server 106 may send at least some of a value indicating the type of the verification target, a value indicating the type of the virtual asset, information about the beneficiary VASP, a beneficiary virtual asset address, a hash value of the beneficiary's full name, a hash value of the beneficiary's DOB, a hash salt value, and a transaction identification value corresponding to the transfer of the virtual asset to the API server 108. Here, the enclave server 106 may also send an auxiliary virtual asset address to the API server 108 according to the type of the virtual asset.
[0140] In operation S370, according to an example embodiment, the API server 108 may send a verification request message to the initiator VASP server 140. For example, the electronic device 100 may send a verification request message to the initiator VASP server 140, the verification request message including an API access key, an identification value of the verification request message, a value indicating the type of the verification target, a value indicating the type of the virtual asset, information about the beneficiary VASP, a beneficiary virtual asset address, a hash value of the beneficiary's full name, a hash value of the beneficiary's DOB, a hash salt value, and at least some of the transaction identification values corresponding to the transfer of the virtual asset. Here, the API server 108 may also send an auxiliary virtual asset address to the initiator VASP server 140 according to the virtual asset type. Reference will be made to Figure 5A and Figure 5B Detailed Description Details of the values included in the authentication request message are described in detail.
[0141] In operation S375, according to an example embodiment, the initiator VASP server 140 may verify whether the beneficiary and the initiator match. For example, the initiator VASP server 140 may identify the initiator's full name data and the initiator's DOB data corresponding to the beneficiary virtual asset address or the transaction identification value, may hash each of the initiator's full name data and the initiator's DOB data, and may generate a hash value of the initiator's full name and a hash value of the initiator's DOB. Thereafter, the initiator VASP server 140 may identify whether the hash value of the beneficiary's full name received from the electronic device 100 matches the hash value of the initiator's full name, and whether the hash value of the beneficiary's DOB received from the electronic device 100 matches the hash value of the initiator's DOB. More specific operations of the initiator VASP server 140 to verify whether the beneficiary and the initiator match are repeated with the description of operation S270 of FIG. 2 and are therefore omitted.
[0142] Meanwhile, according to an example embodiment, the initiator VASP server 140 may use the initiator virtual asset address instead of the transaction identification value or the beneficiary virtual asset address to identify the initiator's full name data and the initiator's DOB data. For example, in operation S350, after identifying the virtual asset to be transferred, the beneficiary VASP server 120 may identify the initiator virtual asset address for transmission. In operation S355, the beneficiary VASP server 120 may send information about the transfer of the virtual asset including the initiator virtual asset address to the enclave server 106, and in operation S365, the enclave server 106 may send relevant information including the initiator virtual asset address to the API server 108. The initiator VASP server 140 may receive a verification request message including the initiator virtual asset address from the API server 108, and may identify the initiator's full name data and the initiator's DOB data corresponding to the received initiator virtual asset address.
[0143] In operation S380, according to an example embodiment, the API server 108 may receive a response message from the initiator VASP server 140 that includes verification result information generated based on the verification request message. For example, the API server 108 may receive a response message from the initiator VASP server 140 that includes at least some of the following information: information indicating that a value matching the transaction identification value is not identified, information indicating that an address matching the beneficiary virtual asset address or the auxiliary virtual asset address is not identified, information regarding a mismatch between a hash value of the beneficiary's full name and a hash value of the initiator's full name, information regarding a mismatch between a hash value of the beneficiary's DOB and a hash value of the initiator's DOB, and information indicating that the initiator is verified to match the beneficiary. This will refer to Figure 6 Detailed description.
[0144] In operation S385, according to an example embodiment, the API server 108 may send a response message to the enclave server 106. For example, the API server 108 may send the response message received from the initiator VASP server 140 to the enclave server 106.
[0145] In operation S390, according to an example embodiment, the enclave server 106 may send a response message to the beneficiary VASP server 120. For example, the enclave server 106 may send the response message received from the API server 108 to the beneficiary VASP server 120.
[0146] In operation S395, according to an example embodiment, based on the verification result information included in the response message, the beneficiary VASP server 120 may reflect the virtual assets transferred to the virtual asset address of the beneficiary on the balance of the beneficiary virtual asset address. For example, if the response message received from the enclave server 106 includes information indicating that the initiator is verified as matching the beneficiary, the beneficiary VASP server 120 may reflect the transferred virtual assets on the balance of the beneficiary virtual asset address at each configured time or whenever the response message is received. Alternatively, if the response message received from the enclave server 106 includes information other than the information indicating that the initiator is verified as matching the beneficiary, the beneficiary VASP server 120 may not reflect the transferred virtual assets on the balance of the receiving virtual address.
[0147] Figure 4A and Figure 4B 1 is a flowchart for explaining a process of verifying a beneficiary or an initiator by the electronic device 100 according to an example embodiment. Figure 4A and Figure 4B , will briefly describe or omit Figure 2A and Figure 2B Description of duplicate description.
[0148] According to an example embodiment, a user can transfer virtual assets in his / her wallet managed by an initiator VASP to another person's wallet managed by a beneficiary VASP using the user terminal 160. In other words, the initiator of the transfer of virtual assets and the beneficiary receiving the virtual assets may be different.
[0149] Figure 4A The process of verifying a beneficiary by the electronic device 100 according to an example embodiment is shown. Here, the electronic device 100 may refer to a server existing inside the initiator VASP.
[0150] In operation S400, according to an example embodiment, the initiator VASP server 140 may identify information about the transfer of the virtual asset. For example, the initiator VASP server 140 may receive from the user terminal 160 at least some of a value indicating the type of virtual asset that the user wishes to transfer, information about the beneficiary VASP, a beneficiary virtual asset address, a beneficiary's full name data, and a beneficiary's DOB data.
[0151] In operation S405, according to an example embodiment, the electronic device 100 may receive information about the transfer of the virtual asset from the initiator VASP server 140. For example, the initiator VASP server 140 may send at least some of a value representing the type of the virtual asset, information about the beneficiary VASP, a beneficiary virtual asset address, a full name data of the beneficiary, and DOB data of the beneficiary to the electronic device 100. Here, the initiator VASP server 140 may also send an auxiliary virtual asset address to the electronic device 100 according to the type of the virtual asset.
[0152] In operation S410, according to an example embodiment, the electronic device 100 may identify a hash value of the full name of the beneficiary and a hash value of the DOB of the beneficiary. For example, the electronic device 100 may hash each of the full name data of the beneficiary and the DOB data of the beneficiary received from the initiator VASP server 140 to generate a hash value of the full name of the beneficiary and a hash value of the DOB of the beneficiary.
[0153] In operation S415, according to an example embodiment, the electronic device 100 may send a verification request message to the beneficiary VASP server 120. For example, the electronic device 100 may send a verification request message to the beneficiary VASP server 120, the verification request message including at least some of an identification value of the verification request message, a value indicating the type of the verification target, a value indicating the type of the virtual asset, information about the initiator VASP, a beneficiary virtual asset address, a hash value of the beneficiary's full name, a hash value of the beneficiary's DOB, and a hash salt value. Here, the electronic device 100 may also send an auxiliary virtual asset address to the beneficiary VASP server 120 according to the type of the virtual asset. Figure 5A and Figure 5B Describes the details of the values included in the authentication request message.
[0154] In operation S420, according to an example embodiment, the beneficiary VASP server 120 may verify whether the beneficiary matches. More specifically, the beneficiary VASP server 120 may verify whether the hash value of the beneficiary (or the first beneficiary) received from the electronic device 100 matches the hash value of the beneficiary (or the second beneficiary) corresponding to the received virtual address.
[0155] For example, the beneficiary VASP server 120 may identify the full name data of the second beneficiary and the DOB data of the second beneficiary corresponding to the beneficiary virtual asset address, may hash the full name data of the second beneficiary and the DOB data of the second beneficiary, respectively, and may generate a hash value of the full name of the second beneficiary and a hash value of the DOB of the second beneficiary. Here, the beneficiary VASP server 120 may identify whether the hash value of the full name of the first beneficiary received from the electronic device 100 matches the hash value of the full name of the second beneficiary, and whether the hash value of the DOB of the first beneficiary received from the electronic device 100 matches the hash value of the DOB of the second beneficiary.
[0156] According to an example embodiment, the beneficiary VASP server 120 may identify whether there is an address that matches the beneficiary virtual asset address or the auxiliary virtual asset address. For example, the beneficiary VASP server 120 may identify whether there is an address in the database that is the same as the beneficiary virtual asset address received from the electronic device 100. Alternatively, if the beneficiary VASP server 120 also receives the auxiliary virtual asset address from the electronic device 100, the beneficiary VASP server 120 may identify whether there is an address in the database that matches the beneficiary virtual asset address and the auxiliary virtual asset address.
[0157] According to an example embodiment, the beneficiary VASP server 120 may identify the full name data of the second beneficiary and the DOB data of the second beneficiary. For example, if it is identified that there is an address in the database that matches the beneficiary virtual asset address received from the electronic device 100, the beneficiary VASP server 120 may identify the second beneficiary full name data and the second beneficiary DOB data corresponding to the beneficiary virtual asset address.
[0158] According to an example embodiment, the beneficiary VASP server 120 may identify whether a hash value of one or more full names of a first beneficiary matches a hash value of one or more full names of a second beneficiary. For example, the beneficiary VASP server 120 may receive a hash value of a full name of a first beneficiary from the electronic device 100, and may identify whether the hash value of the full name of the first beneficiary matches a hash value of a full name of a second beneficiary. Alternatively, the beneficiary VASP server 120 may receive a set of hash values of the full name of the first beneficiary including hash values of multiple full names of the first beneficiary from the electronic device 100, and may identify whether the hash value of the full name of the second beneficiary matches any one of the hash values of the multiple full names of the first beneficiary. The beneficiary VASP server 120 may receive a hash value of a full name of a first beneficiary from the electronic device 100, and may identify whether the hash value of the full name of the first beneficiary matches any one of the hash values of the multiple full names of the second beneficiary. This will refer to FIG. 7E to FIG. 7H Detailed description.
[0159] In operation S425, according to an example embodiment, the electronic device 100 may receive a response message including verification result information generated based on the verification request message from the beneficiary VASP server 120. For example, the electronic device 100 may receive a response message from the beneficiary VASP server 120, the response message including at least some of information indicating that an address matching the beneficiary virtual asset address or the auxiliary virtual asset address is not identified, information about a mismatch in a hash value of the beneficiary's full name, information about a mismatch in a hash value of the beneficiary's DOB, and information indicating that the beneficiaries are verified to be the same. This will refer to Figure 6 Detailed description.
[0160] In operation S430, according to an example embodiment, the electronic device 100 may transmit a response message to the originator VASP server 140. For example, the electronic device 100 may transmit the response message received from the beneficiary VASP server 120 to the originator VASP server 140.
[0161] In operation S435, the initiator VASP server 140 may transfer the virtual asset to the beneficiary virtual asset address based on the verification result information included in the received response message. For example, if the response message received from the electronic device 100 includes information indicating that the beneficiary is verified to be the same, the initiator VASP server 140 may transfer the virtual asset to the beneficiary virtual asset address according to the information received from the user terminal 160. Alternatively, if the response message received from the electronic device 100 includes information other than the information indicating that the beneficiary is verified to be the same, the initiator VASP server 140 may not transfer the virtual asset to the beneficiary virtual asset address.
[0162] Figure 4B The process of authenticating a beneficiary by the electronic device 100 according to an example embodiment is shown. Here, the electronic device 100 may refer to a server existing inside a beneficiary VASP.
[0163] In operation S450, according to an example embodiment, the beneficiary VASP server 120 may identify the virtual assets transferred to the beneficiary virtual asset address. For example, the beneficiary VASP server 120 may identify the virtual assets or deposits transferred by the initiator VASP server 140 to the beneficiary virtual asset address.
[0164] In operation S455, according to an example embodiment, the electronic device 100 may receive information about the transfer of the virtual asset from the beneficiary VASP server 120. For example, the electronic device 100 may receive at least some of a value indicating the type of the virtual asset, information about the beneficiary VASP, a beneficiary virtual asset address, a full name data of the beneficiary, and DOB data of the beneficiary from the electronic beneficiary VASP server 120. Here, the beneficiary VASP server 120 may also send an auxiliary virtual asset address to the electronic device 100 according to the type of the virtual asset.
[0165] In operation S460, according to an example embodiment, the electronic device 100 may identify a hash value of the full name of the beneficiary and a hash value of the DOB of the beneficiary. For example, the electronic device 100 may hash each of the full name data of the beneficiary and the DOB data of the beneficiary received from the beneficiary VASP server 120 to generate a hash value of the full name of the beneficiary and a hash value of the DOB of the beneficiary.
[0166] In operation S465, according to an example embodiment, the electronic device 100 may send a verification request message to the initiator VASP server 140. For example, the electronic device 100 may send a verification request message to the initiator VASP server 140, the verification request message including at least some of an identification value of the verification request message, a value indicating the type of the verification target, a value indicating the type of the virtual asset, information about the beneficiary VASP, a beneficiary virtual asset address, a hash value of the beneficiary's full name, a hash value of the beneficiary's DOB, a hash salt value, and a transaction identification value corresponding to the transfer of the virtual asset. Here, the electronic device 100 may also send an auxiliary virtual asset address to the beneficiary VASP server 120 according to the type of the virtual asset. Reference will be made to Figure 5A and Figure 5B Describes the details of the values included in the authentication request message.
[0167] In operation S470, according to an example embodiment, the initiator VASP server 140 may verify whether the beneficiary matches. More specifically, the initiator VASP server 140 may verify whether the hash value of the beneficiary (or the first beneficiary) received from the electronic device 100 matches the hash value of the beneficiary (or the second beneficiary) corresponding to the beneficiary virtual asset address or the transaction identification value.
[0168] For example, the initiator VASP server 140 may identify the full name data of the second beneficiary and the DOB data of the second beneficiary corresponding to the beneficiary virtual asset address or the transaction identification value, may hash the full name data of the second beneficiary and the DOB data of the second beneficiary, respectively, and may generate a hash value of the full name of the second beneficiary and a hash value of the DOB of the second beneficiary. Here, the initiator VASP server 140 may identify whether the hash value of the full name of the first beneficiary received from the electronic device 100 matches the hash value of the full name of the second beneficiary, and whether the hash value of the DOB of the first beneficiary received from the electronic device 100 matches the hash value of the DOB of the second beneficiary.
[0169] Here, the initiator VASP server 140 may receive the full name data of the second beneficiary and the DOB data of the second beneficiary from the user terminal 160 before transferring the virtual asset and store them in the database. More specifically, the user terminal 160 may obtain a user input for inputting the full name data and DOB data of the beneficiary corresponding to the beneficiary virtual asset address to which the initiator intends to transfer the virtual asset, and may send the obtained full name data and DOB data of the beneficiary to the initiator VASP server 140. Thereafter, the initiator VASP server 140 may store the received full name data of the second beneficiary and the DOB data of the second beneficiary in the database, and may generate a hash value of the full name of the second beneficiary and a hash value of the DOB of the second beneficiary by hashing the data.
[0170] According to an example embodiment, the initiator VASP server 140 may identify whether there is a value matching the transaction identification value. For example, the initiator VASP server 140 may identify whether there is a value identical to the transaction identification value received from the electronic device 100 in the database.
[0171] According to an example embodiment, the initiator VASP server 140 may identify whether there is an address that matches the beneficiary virtual asset address or the auxiliary virtual asset address. For example, the initiator VASP server 140 may identify whether there is an address in the database that is the same as the beneficiary virtual asset address received from the electronic device 100. Alternatively, if the initiator VASP server 140 also receives the auxiliary virtual asset address from the electronic device 100, the initiator VASP server 140 may identify whether there is an address in the database that matches the beneficiary virtual asset address and the auxiliary virtual asset address.
[0172] According to an example embodiment, the initiator VASP server 140 may identify the full name data of the second beneficiary and the DOB data of the second beneficiary. For example, if it is recognized that there is a value matching the transaction identification value received from the electronic device 100 and an address matching the beneficiary virtual asset address in the database, the initiator VASP server 140 may identify the full name data of the second beneficiary and the DOB data of the second beneficiary corresponding to the transaction identification value or the beneficiary virtual asset address.
[0173] According to an example embodiment, the initiator VASP server 140 may identify whether a hash value of one or more full names of a first beneficiary matches a hash value of one or more full names of a second beneficiary. For example, the initiator VASP server 140 may receive a hash value of a full name of a first beneficiary from the electronic device 100, and identify whether the hash value of the full name of the first beneficiary matches a hash value of a full name of the second beneficiary. Alternatively, the initiator VASP server 140 may receive a set of hash values of the full name of the first beneficiary including hash values of multiple full names of the first beneficiary from the electronic device 100, and may identify whether the hash value of the full name of the second beneficiary matches any one of the hash values of the multiple full names of the first beneficiary. The initiator VASP server 140 may receive a hash value of a full name of a first beneficiary from the electronic device 100, and may identify whether the hash value of the full name of the first beneficiary matches any one of the hash values of the multiple full names of the second beneficiary. This will refer to FIG. 7E to FIG. 7H Detailed description.
[0174] In operation S475, according to an example embodiment, the electronic device 100 may receive a response message including verification result information generated based on the verification request message from the initiator VASP server 140. For example, the electronic device 100 may receive a response message from the initiator VASP server 140, the response message including at least some of the following information: information indicating that a value matching the transaction identification value is not identified, information indicating that an address matching the beneficiary virtual asset address or the auxiliary virtual asset address is not identified, information regarding a mismatch in a hash value of the beneficiary's full name, information regarding a mismatch in a hash value of the beneficiary's DOB, and information indicating that the beneficiaries are verified to be the same. This will refer to Figure 6 Detailed description.
[0175] In operation S480, according to an example embodiment, the electronic device 100 may transmit a response message to the beneficiary VASP server 120. For example, the electronic device 100 may transmit the response message received from the initiator VASP server 140 to the beneficiary VASP server 120.
[0176] In operation S485, according to an example embodiment, based on the verification result information included in the response message, the beneficiary VASP server 120 may reflect the virtual assets transferred to the virtual asset address of the beneficiary on the balance of the beneficiary virtual asset address. For example, if the response message received from the electronic device 100 includes information indicating that the beneficiary is verified as the same, the beneficiary VASP server 120 may reflect the transferred virtual assets on the balance of the beneficiary virtual asset address at each configured time or whenever a response message is received. Alternatively, if the response message received from the electronic device 100 includes information other than the information indicating that the beneficiary is verified as the same, the beneficiary VASP server 120 may not reflect the transferred virtual assets on the balance of the receiving virtual address.
[0177] Figure 5A and Figure 5B Examples of authentication request messages 500 and 550 are shown according to example implementations.
[0178] According to an example embodiment, the verification request messages 500 and 550 may include query parameters 510 and 560, headers 520 and 570, and bodies 530 and 580. Here, the data included in the query parameters 510 and 560, the headers 520 and 570, and the bodies 530 and 580 may be represented in a string type based on a javascript object notation (json) format, but is not limited thereto.
[0179] According to an example implementation, query parameters 510 and 560 may include identification values of authentication request messages 500 and 550 .
[0180] According to an example embodiment, the identification value "reqID" of the verification request messages 500 and 550 may refer to a unique identification value assigned to each request message for reconciliation. For example, the identification value of the verification request messages 500 and 550 may be assigned to each of the verification request messages 500 and 550 sent by the electronic device 100, and may be used to distinguish the verification request messages 500 and 550.
[0181] According to an example embodiment, the headers 520 and 570 may include at least some of a value indicating a content type, an API access key, and information about a beneficiary VASP or an initiator VASP.
[0182] According to an example embodiment, a value "Content-Type" indicating a content type may indicate a format of data included in the verification request messages 500 and 550. For example, the value indicating the content type may be set to "application / json".
[0183] According to an example embodiment, the API access key "VASP-API-Key" may represent a token sent by the electronic device 100 for approval when calling an API. For example, the electronic device 100 may request the API access key while requesting the VASP server to register the IP address of the endpoint of the electronic device 100. Therefore, the electronic device 100 may receive the API access key from the VASP server and generate a VASP code.
[0184] According to an example embodiment, the information about the beneficiary VASP or the initiator VASP may indicate the code "VASP-Counterpart-Code" of the counterpart VASP. For example, the VASP code is a unique identification value for distinguishing the VASP and may be registered in the system of the electronic device 100 in the process of receiving the API access key.
[0185] According to an example embodiment, the bodies 530 and 580 may include at least some of a value indicating the type of the verification target, a value indicating the type of the virtual asset, a beneficiary virtual asset address, a hash value of the full name of the initiator, a hash value of the DOB of the initiator, and a hash salt value. Alternatively, the bodies 530 and 580 may include a transaction identification value corresponding to the transfer of the virtual asset according to the type of the verification target, and may include an auxiliary virtual asset address according to the type of the virtual asset.
[0186] According to an example embodiment, the value "verificationType" indicating the type of the verification target may indicate whether the verification target is an initiator or a beneficiary. For example, if the verification target is an initiator, the value indicating the type of the verification target may include "VerifyOriginator", and if the verification target is a beneficiary, the value indicating the type of the verification target may include "VerifyBeneritary". Figure 2A In the embodiment, the electronic device 100 can send verification request messages 500 and 550 including "VerifyBeneritary" to the beneficiary VASP server 120, and Figure 2B In the example, the electronic device 100 may send verification request messages 500 and 550 including “VerifyOriginator” to the initiator VASP server 140 .
[0187] According to an example embodiment, the transaction identification value "txID" corresponding to the transfer of the virtual asset can represent a unique identification number assigned to each transfer of the virtual asset. For example, the transaction identification value can be used to identify the initiator, beneficiary, or beneficiary virtual asset address corresponding to the transfer of the virtual asset.
[0188] Meanwhile, whether the transaction identification value is included in the verification request messages 500 and 550 may be determined according to the type of the verification target. More specifically, if verification is performed after the virtual asset is transferred, the transaction identification value may be included in the verification request messages 500 and 550.
[0189] For example, when the initiator of transferring virtual assets and the beneficiary of receiving virtual assets are the same, if the type of the verification target is the initiator, the verification request messages 500 and 550 may include a transaction identification value. Alternatively, when the initiator of transferring virtual assets and the beneficiary of receiving virtual assets are different, if the initiator VASP server 140 verifies the beneficiary, the verification request messages 500 and 550 may include a transaction identification value.
[0190] For another example, when the initiator of transferring virtual assets and the beneficiary of receiving virtual assets are the same, if the type of the verification target is the beneficiary, the verification request messages 500 and 550 may not include the transaction identification value. Alternatively, when the initiator of transferring virtual assets and the beneficiary of receiving virtual assets are different, if the beneficiary VASP server 120 verifies the beneficiary, the verification request messages 500 and 550 may not include the transaction identification value. According to an example embodiment, the value "symbol" representing the type of virtual asset may represent an abbreviation or symbol of a unique name assigned to identify the virtual asset, and may be used with a token ticker. For example, the value representing the type of virtual asset may include "BTC", "ETH" or "XRP" according to the type of virtual asset.
[0191] According to an example embodiment, the beneficiary virtual asset address "address" may indicate a wallet address to which the virtual assets managed by the beneficiary VASP are transferred. Here, regardless of whether the type of the verification target is a beneficiary or an initiator, the verification request messages 500 and 550 may include the beneficiary virtual asset address.
[0192] According to an example embodiment, the auxiliary virtual asset address "tag" may represent a secondary virtual asset address managed by a beneficiary VASP to which the virtual asset is transferred. Here, regardless of whether the type of the verification target is a beneficiary or an initiator, the verification request messages 500 and 550 may include the auxiliary virtual asset address.
[0193] In addition, whether the auxiliary virtual asset address is included in the verification request messages 500 and 550 may be determined according to the type of the virtual asset. For example, if the type of the virtual asset is Ripple's "XRP", the auxiliary virtual asset address as the name of the destination tag may be included in the verification request messages 500 and 550. Alternatively, if the type of the virtual asset is EOS, Stellar Lumens' XLM, or MediBloc's MED, the auxiliary virtual asset address may be included in the verification request messages 500 and 550 as the name of the memorandum. If the type of the virtual asset is XEM or Stellar Lumens' XLM, the auxiliary virtual asset address may be included in the verification request messages 500 and 550 as the name of the memorandum.
[0194] According to an example embodiment, the hash salt value "hashSalt" may represent any string used as an additional input when hashing the full name data or the DOB data. Here, the hash salt value should be a universal unique identifier (UUID) value randomly generated for each request. For example, when hashing the full name data or the DOB data, the electronic device 100 may generate a hash value of the full name or a hash value of the DOB by hashing after appending the hash salt value to each of the full name data and the DOB data.
[0195] According to an example embodiment, the hash value "dobHash" of the DOB may indicate a value generated by hashing the DOB data of the beneficiary or the initiator. For example, the electronic device 100 may hash the DOB data in the format of "${YYYY}-${MM}-${DD},${hashSalt}" and generate a hash value of the DOB in a string type of 64 characters in hexadecimal encoding. Here, in the case of a company account, the DOB may be set in the form of "0000-00-00".
[0196] According to an example embodiment, the hash value "nameHashes" of the full name may represent a value generated by hashing the full name data of the beneficiary or the initiator. For example, if the full name data is expressed in English, the electronic device 100 may hash the full name data in the format of "${lowercase (first name)}${lowercase (last name)}, ${hash salt}" to generate a hash value of a DOB string type with a length of 64 characters encoded in hexadecimal. Alternatively, if the full name data is expressed in a local language, the electronic device 100 may hash the full name data in the format of "${first name}${last name}, ${hash salt}" to generate a DOB hash value of a string with a length of 64 characters encoded in hexadecimal. Here, the electronic device 100 may hash the full name data after removing spaces included in the full name data and converting at least one character included in the full name data into lowercase letters.
[0197] Meanwhile, when the electronic device 100 converts the data of the full name into various forms and then hashes it, the hash value of the full name may indicate a hash value set of the full name including one or more hash values. For example, the electronic device 100 may generate a hash value by hashing the full name information consisting of a single entry in the order of the first name and the last name, or may generate a hash value by hashing the full name information consisting of a single entry in the order of the last name and the first name. Alternatively, the electronic device 100 may generate a hash value by hashing the Korean full name, or may generate a hash value by hashing the English full name. This will refer to 7A to 7H Detailed description.
[0198] Figure 5A An authentication request message 500 is shown according to an example implementation.
[0199] According to an example embodiment, the verification request message 500 may include "UPBT001 KR" as a code of the counterpart VASP.
[0200] According to an example embodiment, the verification request message 500 may include "VerifyOriginator" as a value indicating the type of the verification target, and thus, the verification request message 500 may include a transaction identification value corresponding to the transfer of the virtual asset.
[0201] According to an example embodiment, the verification request message 500 may include 'EHT' as a value indicating the type of the virtual asset, and thus, the verification request message 500 may not include the auxiliary virtual asset address.
[0202] According to an example embodiment, the authentication request message 500 may include four hash values as full name hash values.
[0203] Figure 5BAn authentication request message 550 is shown according to an example implementation.
[0204] According to an example embodiment, the verification request message 550 may include "UPBT001KR" as a code of the counterpart VASP.
[0205] According to an example embodiment, the verification request message 550 may include "VerifyOriginator" as a value indicating the type of the verification target, and thus, the verification request message 550 may include a transaction identification value corresponding to the transfer of the virtual asset.
[0206] According to an example embodiment, the verification request message 550 may include "XRP" as a value indicating the type of the virtual asset, and thus, the verification request message 550 may include "76188721" as the secondary virtual asset address.
[0207] According to an example embodiment, the verification request message 550 may include four hash values as full name hash values.
[0208] Figure 6 An example of a response message 600 is shown according to an example implementation.
[0209] According to an example embodiment, the response message may include a header 620 or a body 640. Here, data included in the header 620 and the body 640 may be represented as a string type based on the json format, but is not limited thereto.
[0210] According to an example embodiment, the header 620 may include a value indicating the content type.
[0211] According to an example embodiment, the value "Content-Type" indicating the content type may indicate the format of the data included in the verification request message. For example, the value indicating the content type may be set to "application / json".
[0212] According to an example embodiment, the body 640 may include verification result information.
[0213] According to an example embodiment, the verification result information "VerificationResult" may indicate a verification determination value of the initiator or beneficiary generated based on the verification request message. For example, the verification result information may include a value "TXID-NOT-FOUND" indicating that a value matching the transaction identification value is not identified, a value "MISMATCH-ADDRESS" indicating that an address matching the beneficiary virtual asset address or the auxiliary virtual asset address is not identified, a value "MISMATCH-NAME" indicating that the hash value of the full name does not match, a value "MISMATCH-DOB" indicating that the hash value of the DOB does not match, and / or a value "VERIFIED" indicating that the initiator or beneficiary is verified.
[0214] Here, if one or more mismatches are identified, the verification result information may include a value indicating the one or more mismatches. For example, the verification result information may include "MISMATCH-NAME" and "MISMATCH-DOB".
[0215] Reference Figure 6 According to an example embodiment, the response message 600 may include “VERIFIED” as the verification result information.
[0216] 7A to 7H is a diagram for explaining a process in which the VASP servers 120 and 140 identify whether hash values of full names match according to an example embodiment.
[0217] Reference Fig. 7A According to an example embodiment, the VASP servers 120 and 140 may identify whether a hash value of a full name of the initiator matches a hash value of a full name of the beneficiary. For example, the electronic device 100 or the VASP servers 120 and 140 may generate a hash value of a full name of the initiator by hashing after converting the full name data of the initiator in a configuration method. In addition, the VASP servers 120 and 140 or the electronic device 100 may generate a hash value of a full name of the beneficiary by hashing after converting the full name data of the beneficiary in a configuration method. Thereafter, if the hash value of a full name of the initiator matches the hash value of a full name of the beneficiary, the VASP servers 120 and 140 may identify that the name of the beneficiary matches the name of the initiator.
[0218] According to an example embodiment, the electronic device 100 or the VASP servers 120 and 140 may convert the full name data according to a common method and then hash the data. For example, the electronic device 100 or the VASP servers 120 and 140 may remove spaces included in the full name data, convert at least one character included in the full name data into lowercase letters, and hash the full name data. Alternatively, the electronic device 100 or the VASP servers 120 and 140 may convert the full name data into English and then hash the data. If the full name data includes a middle name, the electronic device 100 or the VASP servers 120 and 140 may remove the middle name, convert to the order of the first name and the last name, and then hash the data. However, the method by which the electronic device 100 or the VASP servers 120 and 140 converts the full name data to hash the full name data is not limited to the above method.
[0219] Furthermore, the operation of hashing the full name data may correspond to Figure 2A In operation S205, the electronic device 100 performs a hash operation on the full name data of the initiator, Figure 2A In operation S215, the beneficiary VASP server 120 performs a hash operation on the beneficiary's full name data. Figure 2B In operation S260, the electronic device 100 performs a hash operation on the full name data of the beneficiary, or Figure 2B In operation S270 of the initiator VASP server 140, the initiator's full name data is hashed. In addition, the operation of hashing the full name data may correspond to the operation of Figure 3A In operation S305 of the enclave server 102, the full name data of the initiator is hashed. Figure 3A In operation S320, the beneficiary VASP server 120 performs a hash operation on the beneficiary's full name data. Figure 3B The enclave server 106 performs a hash operation on the full name data of the beneficiary in operation S360, or Figure 3B In operation S375, the initiator's VASP server 140 hashes the initiator's full name data.
[0220] Reference Figure 7BAccording to an example embodiment, the VASP servers 120 and 140 may identify whether a hash value of a full name of a beneficiary matches one of the hash values of a plurality of full names of an initiator. For example, the electronic device 100 or the VASP servers 120 and 140 may generate a hash value set of a full name of an initiator including hash values of a plurality of full names of an initiator by converting and hashing the full name data of the initiator in various ways. In addition, the electronic device 100 or the VASP servers 120 and 140 may generate a hash value of a full name of a beneficiary by hashing after converting the full name data of the beneficiary in a configuration method. Thereafter, if the hash value of a full name of a beneficiary matches one of the hash values of a plurality of full names of an initiator, the VASP servers 120 and 140 may identify that the full name of the beneficiary matches the full name of the initiator.
[0221] According to an example embodiment, the electronic device 100 or the VASP servers 120 and 140 may perform hashing after converting the full name data of the initiator in various ways. For example, the electronic device 100 or the VASP servers 120 and 140 may convert the full name data of the initiator into a single entry in the order of the first name and the last name, and may perform hashing after removing at least some of the configuration characters including spaces or hyphens (-) included in the full name data. Alternatively, the electronic device 100 or the VASP servers 120 and 140 may convert the full name data of the initiator into a plurality of entries including a last name, a first name, and at least one middle name, and may perform hashing after converting the letter case of at least one character included in the full name data into the configuration case (lowercase letters or uppercase letters). However, the method of converting the full name data by the electronic device 100 or the VASP servers 120 and 140 to hash the full name data of the initiator is not limited to the above method.
[0222] At the same time, the operation of hashing the initiator's full name data may correspond to Figure 2A In operation S205, the electronic device 100 performs a hash operation on the full name data of the initiator, Figure 2B The operation of hashing the full name data of the originator in operation S270 of the originator VASP server 140, Figure 3A In operation S305 of the enclave server 102, the full name data of the initiator is hashed, or in Figure 3B In operation S375, the initiator's VASP server 140 hashes the initiator's full name data.
[0223] Reference Figure 7CAccording to an example embodiment, the VASP servers 120 and 140 may identify whether a hash value of one full name of the initiator matches one of the hash values of multiple full names of the beneficiary. For example, the electronic device 100 or the VASP servers 120 and 140 may generate a hash value set of the full name of the beneficiary including the hash values of multiple full names of the beneficiary by converting and hashing the full name data of the beneficiary in various ways. In addition, the electronic device 100 or the VASP servers 120 and 140 may generate a hash value of one full name of the initiator by hashing after converting the full name data of the initiator in a configuration method. Thereafter, if the hash value of one full name of the initiator matches one of the hash values of multiple full names of the beneficiary, the VASP servers 120 and 140 may identify that the name of the beneficiary matches the name of the initiator.
[0224] According to an example embodiment, the electronic device 100 or the VASP servers 120 and 140 may perform hashing after converting the full name data of the beneficiary in various ways. For example, the electronic device 100 or the VASP servers 120 and 140 may convert the full name data of the beneficiary into a single entry in the order of the last name and the first name, and may remove spaces included in the full name data, convert at least one character included in the full name data into lowercase letters, and then hash the data. Alternatively, the electronic device 100 or the VASP servers 120 and 140 may combine the last name, the first name, and at least one middle name included in the full name data of the beneficiary in various orders and convert them into a plurality of separate entries, and perform hashing after converting at least one character included in the full name data into lowercase letters. However, the conversion method by which the electronic device 100 or the VASP servers 120 and 140 hashes the full name data of the beneficiary is not limited thereto.
[0225] At the same time, the operation of hashing the full name data of the beneficiary can correspond to Figure 2A In operation S215, the beneficiary VASP server 120 performs a hash operation on the beneficiary's full name data. Figure 2B In operation S260, the electronic device 100 performs a hash operation on the full name data of the beneficiary, Figure 3A In operation S320, the beneficiary VASP server 120 performs a hash operation on the beneficiary's full name data, or Figure 3B In operation S360, the enclave server 106 performs a hashing operation on the full name data of the beneficiary.
[0226] Reference Fig.7DAccording to an example embodiment, the VASP servers 120 and 140 may identify whether one of the hash values of the multiple full names of the initiator matches one of the hash values of the multiple full names of the beneficiary. For example, the electronic device 100 or the VASP servers 120 and 140 may perform hashing after converting the full name data of the initiator in various ways, and generate a hash value set of the full name of the initiator including the hash values of the multiple names of the initiator. In addition, the electronic device 100 or the VASP servers 120 and 140 may perform hashing after converting the full name data of the beneficiary in various ways, and generate a hash value set of the full name of the beneficiary including the hash values of the multiple full names of the beneficiary. Thereafter, if the hash values of the multiple full names of the initiator and the hash values of the multiple full names of the beneficiary are greater than or equal to the configured value, the VASP servers 120 and 140 may identify that the name of the beneficiary matches the name of the initiator.
[0227] According to an example embodiment, the electronic device 100 or the VASP servers 120 and 140 may perform hashing after converting the full name data of the originator or the full name data of the beneficiary in various ways. A more detailed operation of hashing the full name data by the electronic device 100 or the VASP servers 120 and 140 will be omitted because it is related to 7A to 7C The description is repeated.
[0228] At the same time, the operation of hashing the initiator's full name data may correspond to Figure 2A In operation S205, the electronic device 100 performs a hash operation on the full name data of the initiator, Figure 2B The operation of hashing the full name data of the initiator of the initiator VASP server 140 in operation S270, Figure 3A In operation S305 of the enclave server 102, the full name data of the initiator is hashed, or in Figure 3B In operation S375 of the initiator VASP server 140, the initiator's full name data is hashed. In addition, the operation of hashing the beneficiary's full name data may correspond to the operation of Figure 2A In operation S215, the beneficiary VASP server 120 performs a hash operation on the beneficiary's full name data. Figure 2B In operation S260, the electronic device 100 performs a hash operation on the full name data of the beneficiary, Figure 3A In operation S320, the beneficiary VASP server 120 performs a hash operation on the beneficiary's full name data, or Figure 3B In operation S360, the enclave server 106 performs a hashing operation on the full name data of the beneficiary.
[0229] Reference Fig. 7EAccording to an example embodiment, the VASP servers 120 and 140 may identify whether a hash value of a full name of a first beneficiary matches a hash value of a full name of a second beneficiary. For example, the electronic device 100 may generate a hash value of a full name of a first beneficiary by performing hashing after converting the full name data of the first beneficiary in a configuration method. In addition, the VASP servers 120 and 140 may generate a hash value of a full name of a second beneficiary by performing hashing after converting the full name data of the second beneficiary in a configuration method. Thereafter, if the hash value of a full name of a first beneficiary matches the hash value of a full name of a second beneficiary, the VASP servers 120 and 140 may identify that the full names of the beneficiaries match.
[0230] According to an example embodiment, the electronic device 100 or the VASP servers 120 and 140 may perform hashing after converting the full name data according to a common method. A more detailed operation of hashing the full name data by the electronic device 100 or the VASP servers 120 and 140 will be omitted because it is related to 7A to 7C The description is repeated.
[0231] At the same time, the operation of hashing the full name data can correspond to Figure 4A In operation S410, the electronic device 100 performs a hash operation on the full name data of the beneficiary, Figure 4A In operation S420, the beneficiary VASP server 120 performs a hash operation on the beneficiary's full name data. Figure 4B The operation of hashing the full name data of the beneficiary by the electronic device 100 in operation S460, or Figure 4B In operation S470, the initiator VASP server 140 performs a hashing operation on the full name data of the beneficiary.
[0232] Reference Figure 7F According to an example embodiment, the VASP servers 120 and 140 may identify whether a hash value of a full name of the second beneficiary matches one of the hash values of the multiple full names of the first beneficiary. For example, the electronic device 100 may generate a set of hash values of the full name of the first beneficiary including the hash values of the multiple full names of the first beneficiary by converting and hashing the full name data of the first beneficiary in various ways. In addition, the VASP servers 120 and 140 may generate a hash value of a full name of the second beneficiary by hashing after converting the full name data of the second beneficiary in a set manner. Thereafter, if the hash value of the full name of the second beneficiary matches one of the hash values of the multiple full names of the first beneficiary, the VASP servers 120 and 140 may identify that the full names of the beneficiaries match.
[0233] According to an example embodiment, the electronic device 100 may convert the full name data of the first beneficiary according to various methods and then hash the data. A more detailed operation of hashing the full name data by the electronic device 100 will be omitted because it is similar to FIG. 7A to FIG. 7C The description is repeated.
[0234] Meanwhile, the operation of hashing the full name data of the first beneficiary may correspond to Figure 4A The electronic device 100 performs a hash operation on the full name data of the beneficiary in operation S410, or Figure 4B In operation S460, the electronic device 100 performs a hashing operation on the full name data of the beneficiary.
[0235] Reference Figure 7G According to an example embodiment, the VASP servers 120 and 140 may identify whether a hash value of a full name of a first beneficiary matches one of the hash values of a plurality of full names of a second beneficiary. For example, the VASP servers 120 and 140 may hash the full name data of the second beneficiary after converting it in various ways, and generate a hash value set of the full name of the second beneficiary including the hash values of the plurality of full names of the second beneficiary. Further, after converting the full name data of the first beneficiary in a configuration method, the electronic device 100 may hash the data, and may generate a hash value of a full name of the first beneficiary. Thereafter, if the hash value of a full name of the first beneficiary matches one of the hash values of the plurality of full names of the second beneficiary, the VASP servers 120 and 140 may identify that the full names of the beneficiaries match.
[0236] According to an example embodiment, the VASP servers 120 and 140 may convert the full name data of the second beneficiary according to various methods and then hash the data. A more specific operation of hashing the full name data by the VASP servers 120 and 140 will be omitted because it is related to FIG. 7A to FIG. 7C The description is repeated.
[0237] At the same time, the operation of hashing the full name data of the second beneficiary may correspond to Figure 4A In operation S420, the beneficiary VASP server 120 performs a hash operation on the beneficiary's full name data, or in Figure 4B In operation S470, the initiator VASP server 140 hashes the full name data of the beneficiary.
[0238] Reference Figure 7HAccording to an example embodiment, the VASP servers 120 and 140 may identify whether one of the hash values of the first beneficiary's multiple full names matches one of the hash values of the second beneficiary's multiple full names. For example, the electronic device 100 may convert the first beneficiary's full name data in various ways, then hash the data, and generate a set of hash values of the first beneficiary's full name including the hash values of the first beneficiary's multiple full names. In addition, after converting the second beneficiary's full name data in various ways, the VASP servers 120 and 140 may hash the data and generate a set of hash values of the second beneficiary's full name including the hash values of the second beneficiary's multiple full names. Thereafter, if the number of matches among the hash values of the first beneficiary's multiple full names and the hash values of the second beneficiary's multiple full names is greater than or equal to a configured value, the VASP servers 120 and 140 may identify that the beneficiary's full names match.
[0239] According to an example embodiment, after converting the full name data of the first beneficiary or the full name data of the second beneficiary in various ways, the electronic device 100 or the VASP servers 120 and 140 may perform hashing. A more specific operation of hashing the full name data by the VASP servers 120 and 140 will be omitted because it is related to FIG. 7A to FIG. 7C The description is repeated.
[0240] Meanwhile, the operation of hashing the full name data of the first beneficiary may correspond to Figure 4A The electronic device 100 performs a hash operation on the full name data of the beneficiary in operation S410, or Figure 4B In operation S460 of the present invention, the electronic device 100 performs a hash operation on the full name data of the beneficiary. In addition, the operation of hashing the full name data of the second beneficiary may correspond to the operation of performing a hash operation on the full name data of the second beneficiary. Figure 4A In operation S420, the beneficiary VASP server 120 performs a hash operation on the beneficiary's full name data, or in Figure 4B In operation S470, the initiator VASP server 140 hashes the full name data of the beneficiary.
[0241] Figure 8 1 is a flowchart for explaining a process of authenticating a beneficiary by the electronic device 100 according to an exemplary embodiment. Here, the electronic device 100 may refer to a server existing inside an initiator VASP.
[0242] According to an example embodiment, a user can transfer virtual assets in his / her wallet managed by an initiator VASP to a user wallet managed by a beneficiary VASP using a user terminal 160. In other words, the initiator transferring the virtual assets and the beneficiary receiving the virtual assets can be the same.
[0243] In operation S800, according to an example embodiment, the user terminal 160 may obtain information about a beneficiary VASP and a beneficiary virtual asset address. For example, the user terminal 160 may obtain user input related to information about a beneficiary virtual asset address to which a virtual asset is to be transferred and a beneficiary VASP that manages the beneficiary virtual asset address.
[0244] In operation S805, according to an example embodiment, the electronic device 100 may receive information about a beneficiary VASP and a beneficiary virtual asset address from the user terminal 160. For example, the user terminal 160 may send information about a beneficiary virtual asset address input by a user and a beneficiary VASP that manages the beneficiary virtual asset address to the electronic device 100.
[0245] In operation S810, according to an example embodiment, the electronic device 100 may send a request for a hash value of the beneficiary's full name and a beneficiary's virtual asset address to the beneficiary VASP server 120. For example, when sending the beneficiary's virtual asset address to the beneficiary VASP server 120, the electronic device 100 may request the beneficiary VASP server 120 to send a hash value of the beneficiary's full name corresponding to the beneficiary's virtual asset address.
[0246] In operation S815, according to an example embodiment, the electronic device 100 may receive from the beneficiary VASP server 120 whether the beneficiary virtual asset address is held and a hash value of the beneficiary's full name. For example, the beneficiary VASP server 120 may identify whether there is an address that matches the beneficiary virtual asset address. Thereafter, the beneficiary VASP server 120 may identify the beneficiary full name data corresponding to the beneficiary virtual asset address, hash the beneficiary full name data, and generate a hash value of the beneficiary's full name. The beneficiary VASP server 120 may send to the electronic device 100 whether there is an address that matches the beneficiary virtual asset address and a hash value of the beneficiary's full name.
[0247] According to an example embodiment, the beneficiary VASP server 120 may identify whether there is an address that matches the beneficiary virtual asset address or the auxiliary virtual asset address. For example, the beneficiary VASP server 120 may identify whether there is an address in the database that is the same as the beneficiary virtual asset address received from the electronic device 100. Alternatively, if the beneficiary VASP server 120 also receives the auxiliary virtual asset address from the electronic device 100, the beneficiary VASP server 120 may identify whether there is an address in the database that matches the beneficiary virtual asset address and the auxiliary virtual asset address.
[0248] According to an example embodiment, the beneficiary VASP server 120 may identify the full name data of the beneficiary. For example, if an address matching the beneficiary virtual asset address is identified in the database, the beneficiary VASP server 120 may identify the full name data of the beneficiary corresponding to the beneficiary virtual asset address.
[0249] According to an example embodiment, the beneficiary VASP server 120 may generate a hash value of one or more full names of the beneficiary. More detailed operations of the beneficiary VASP server 120 to generate the hash value of one or more full names of the beneficiary are omitted because it is not related to the 7A to 7H The description is repeated.
[0250] In operation S820, according to an example embodiment, the electronic device 100 may verify whether the initiator and the beneficiary match. For example, the electronic device 100 may identify the full name data of the initiator, hash the full name data of the initiator, and generate a hash value of the full name of the initiator. Thereafter, the electronic device 100 may identify whether the hash value of the full name of the beneficiary received from the beneficiary VASP server 120 matches the hash value of the full name of the initiator. A more detailed operation of the electronic device 100 verifying whether the initiator and the beneficiary match will be omitted because it is related to the FIG. 7A to FIG. 7H The description is repeated.
[0251] In operation S825, according to an example embodiment, if the initiator and the beneficiary match, the electronic device 100 may send a request for a one-time password (OTP) to the beneficiary VASP server 120. Alternatively, according to an example embodiment, if the initiator and the beneficiary do not match, the electronic device 100 may send a request to re-enter the beneficiary virtual asset address to the user terminal 160. However, OTP is only an example, and it is obvious to those skilled in the art that various types of passwords may be used.
[0252] In operation S830, according to an example embodiment, the electronic device 100 may obtain an OTP. For example, if the initiator and the beneficiary match, the beneficiary VASP server 120 may issue an OTP and provide the OTP to the user's beneficiary VASP account. Thereafter, the user may input the issued OTP into the user terminal 160.
[0253] In operation S835, according to an example embodiment, the electronic device 100 may receive an OTP from the user terminal 160. For example, the user terminal 160 may transmit the OTP input by the user to the electronic device 100.
[0254] In operation S840, according to an example embodiment, the electronic device 100 may transmit the OTP to the beneficiary VASP server 120. For example, the electronic device 100 may transmit the OTP received from the user terminal 160 to the beneficiary VASP server 120.
[0255] In operation S845, the beneficiary VASP server 120 may verify the OTP. For example, the beneficiary VASP server 120 may identify whether the OTP issued by itself matches the OTP input by the user.
[0256] In operation S850, the electronic device 100 may receive an OTP verification result from the beneficiary VASP server 120. For example, the electronic device 100 may receive from the beneficiary VASP server 120 a value (true) indicating that the OTP issued by the beneficiary VASP server 120 matches the OTP input by the user, or a value (false) indicating that the OTP issued by the beneficiary VASP server 120 does not match the OTP input by the user.
[0257] In operation S855, according to an example embodiment, if the OTP issued by the beneficiary VASP server 120 matches the OTP input by the user, the electronic device 100 may transfer the virtual asset. Alternatively, according to an example embodiment, if the OTP issued by the beneficiary VASP server 120 does not match the OTP input by the user, the electronic device 100 may send a request for OTP re-entry to the user terminal 160.
[0258] In operation S860, according to an example embodiment, if the electronic device 100 transfers the virtual asset, the electronic device 100 may transmit the identification value of the transaction to the beneficiary VASP server 120. For example, the electronic device 100 may transmit the identification value of the transaction corresponding to the transfer of the virtual asset to the beneficiary VASP server 120. However, operation S860 may be omitted.
[0259] In operation S865, according to an example embodiment, the beneficiary VASP server 120 may reflect the transferred virtual assets to the balance of the beneficiary virtual asset address. For example, based on the transaction identification value, the beneficiary VASP server 120 may reflect the transferred virtual assets to the balance of the beneficiary virtual asset address at each configured time or whenever a response message is received.
[0260] Fig. 9 1 is a flowchart for explaining a process of verifying an initiator by the electronic device 100 according to an exemplary embodiment. Here, the electronic device 100 may refer to a server existing inside a beneficiary VASP.
[0261] According to an example embodiment, a user can transfer virtual assets in his / her wallet managed by an initiator VASP to a user wallet managed by a beneficiary VASP using a user terminal 160. In other words, the initiator transferring the virtual assets and the beneficiary receiving the virtual assets can be the same.
[0262] In operation S900, according to an example embodiment, the user terminal 160 may obtain information about a beneficiary VASP and a beneficiary virtual asset address. For example, the user terminal 160 may obtain user input related to information about a beneficiary virtual asset address to which a virtual asset is to be transferred and a beneficiary VASP that manages the beneficiary virtual asset address.
[0263] In operation S905, according to an example embodiment, the initiator VASP server 140 may receive information about the beneficiary VASP and the beneficiary virtual asset address from the user terminal 160. For example, the user terminal 160 may send information about the beneficiary virtual asset address input by the user and the beneficiary VASP that manages the beneficiary virtual asset address to the initiator VASP server 140.
[0264] In operation S910, according to an example embodiment, the electronic device 100 may receive a hash value of the beneficiary virtual asset address and the initiator's full name from the initiator VASP server 140. For example, the initiator VASP server 140 may generate a hash value of the initiator's full name by hashing the initiator's full name data. Thereafter, the initiator VASP server 140 may send the hash value of the beneficiary virtual asset address and the initiator's full name to the electronic device 100.
[0265] According to an example embodiment, the originator VASP server 140 may generate a hash value of the originator's full name or names. A more detailed operation of the originator VASP server 140 to generate the hash value of the originator's name or names is omitted because it is not related to the 7A to 7H The description is repeated.
[0266] In operation S915, according to an example embodiment, the electronic device 100 may verify whether the initiator and the beneficiary match. For example, the electronic device 100 may identify whether there is an address that matches the beneficiary virtual asset address. Thereafter, the electronic device 100 may identify the full name data of the beneficiary corresponding to the beneficiary virtual asset address, hash the full name data of the beneficiary, and generate a hash value of the full name of the beneficiary. The electronic device 100 may identify whether the hash value of the full name of the beneficiary matches the hash value of the full name of the initiator.
[0267] According to an example embodiment, the electronic device 100 may identify whether there is an address matching the beneficiary virtual asset address or the auxiliary virtual asset address. For example, the electronic device 100 may identify whether there is an address matching the beneficiary virtual asset address received from the initiator VASP server 140 in the database. Alternatively, if the electronic device 100 also receives the auxiliary virtual asset address from the initiator VASP server 140, the electronic device 100 may identify whether there is an address matching the beneficiary virtual asset address and the auxiliary virtual asset address in the database.
[0268] According to an example embodiment, the electronic device 100 may identify the full name data of the beneficiary. For example, if it is identified that there is an address matching the beneficiary virtual asset address in the database, the electronic device 100 may identify the full name data of the beneficiary corresponding to the beneficiary virtual asset address.
[0269] According to an example embodiment, the electronic device 100 may generate a hash value of one or more full names of the beneficiary. A more specific operation of the electronic device 100 generating a hash value of one or more full names of the beneficiary is omitted because it is not related to the 7A to 7H The description is repeated.
[0270] According to an example embodiment, the electronic device 100 may identify whether the hash value of the one or more full names of the beneficiary matches the hash value of the one or more full names of the initiator. A more specific operation of the electronic device 100 to verify whether the initiator matches the beneficiary will be omitted because it is not related to the FIG. 7A to FIG. 7H The description is repeated.
[0271] In operation S920, the electronic device 100 may send the verification result to the initiator VASP server 140. For example, the electronic device 100 may send a value indicating that there is no address matching the beneficiary virtual asset address or the auxiliary virtual asset address to the initiator VASP server 140. Alternatively, the electronic device 100 may send a value indicating that the hash value of the initiator's full name matches the hash value of the beneficiary's full name (true) or a value indicating that the hash value of the initiator's full name does not match the hash value of the beneficiary's full name (false) to the initiator VASP server 140.
[0272] In operation S925, according to an example embodiment, if the initiator and the beneficiary match, the electronic device 100 may receive a request for an OTP from the initiator VASP server 140. Alternatively, according to an example embodiment, if the initiator and the beneficiary do not match, the initiator VASP server 140 may send a request to re-enter the beneficiary virtual asset address to the user terminal 160. However, this is an example, and it will be apparent to those skilled in the art that various types of passwords may be used.
[0273] In operation S930, according to an example embodiment, the electronic device 100 may obtain an OTP. For example, if the initiator and the beneficiary match, the electronic device 100 may issue an OTP and provide the OTP to the user's beneficiary VASP account. Thereafter, the user may input the issued OTP into the user terminal 160.
[0274] In operation S935, according to an example embodiment, the originator VASP server 140 may receive an OTP from the user terminal 160. For example, the user terminal 160 may send the OTP input by the user to the originator VASP server 140.
[0275] In operation S940, according to an example embodiment, the electronic device 100 may receive an OTP from the originator VASP server 140. For example, the originator VASP server 140 may transmit the OTP received from the user terminal 160 to the electronic device 100.
[0276] In operation S945, the electronic device 100 may verify the OTP. For example, the electronic device 100 may identify whether the OTP issued by the electronic device 100 itself matches the OTP input by the user.
[0277] In operation S950, the electronic device 100 may send the OTP verification result to the initiator VASP server 140. For example, the electronic device 100 may send to the initiator VASP server 140 a value (true) indicating that the OTP issued by the electronic device 100 itself matches the OTP input by the user, or a value (false) indicating that the OTP issued by the electronic device 100 itself does not match the OTP input by the user.
[0278] In operation S955, according to an example embodiment, if the OTP issued by the electronic device 100 and the OTP input by the user match, the originator VASP server 140 may transfer the virtual asset. Alternatively, according to an example embodiment, if the OTP issued by the electronic device 100 and the OTP input by the user do not match, the originator VASP server 140 may send a request for OTP re-entry to the user terminal 160.
[0279] In operation S960, according to an example embodiment, if the initiator VASP server 140 transfers the virtual asset, the electronic device 100 may receive an identification value of the transaction from the initiator VASP server 140. For example, the electronic device 100 may receive an identification value of the transaction corresponding to the transfer of the virtual asset from the initiator VASP server 140. However, operation S960 may be omitted.
[0280] In operation S965, according to an example embodiment, the electronic device 100 may reflect the transferred virtual assets to the balance of the beneficiary's virtual asset address. For example, based on the transaction identification value, the electronic device 100 may reflect the transferred virtual assets to the balance of the beneficiary's virtual asset address at each configuration time or whenever a response message is received.
[0281] Fig.10 1 is a flowchart for explaining a process of authenticating a beneficiary by the electronic device 100 according to an exemplary embodiment. Here, the electronic device 100 may refer to a server existing inside an initiator VASP.
[0282] According to an example embodiment, a user can transfer virtual assets in his / her wallet managed by an initiator VASP to a user wallet managed by a beneficiary VASP using a user terminal 160. In other words, the initiator transferring the virtual assets and the beneficiary receiving the virtual assets can be the same.
[0283] In operation S1000, according to an example embodiment, the user terminal 160 may obtain a public key and a beneficiary virtual asset address. For example, the user terminal 160 may obtain a user input regarding the public key from a generated public key and private key pair. Alternatively, the user terminal 160 may obtain a user input regarding information regarding a beneficiary virtual asset address to which the virtual asset will be transferred and a beneficiary VASP that manages the beneficiary virtual asset address.
[0284] In operation S1005, according to an example embodiment, the electronic device 100 may receive a public key, a beneficiary virtual asset address, and a request to transfer a virtual asset to the beneficiary virtual asset address from the user terminal 160. For example, when the public key and the beneficiary virtual asset address are sent to the electronic device 100, the user terminal 160 may request to transfer the virtual asset to the beneficiary virtual asset address.
[0285] In operation S1010, according to an example embodiment, the electronic device 100 may transfer a virtual asset and identify a transaction identification value. For example, the electronic device 100 may send the virtual asset to a beneficiary virtual asset address and identify a transaction identification value corresponding to the transfer of the virtual asset.
[0286] In operation S1015, according to an example embodiment, the electronic device 100 may encrypt the transaction identification value. For example, the electronic device 100 may encrypt the transaction identification value using the public key received from the user terminal 160 and obtain an encryption result or ciphertext.
[0287] In operation S1020, according to an example embodiment, the electronic device 100 may upload the paired transaction identification value and the encryption result to an open server. For example, the electronic device 100 may upload the paired transaction identification value and the encryption result to a web server accessible to all VASP servers.
[0288] In operation S1025, according to an example embodiment, the beneficiary VASP server 120 may identify the virtual assets transferred to the beneficiary virtual asset address. For example, the beneficiary VASP server 120 may identify the virtual assets or deposits transferred by the electronic device 100 to the beneficiary virtual asset address.
[0289] In operation S1030, according to an example embodiment, the beneficiary VASP server 120 may send a request for a private key to the user terminal 160. For example, the beneficiary VASP server 120 may request the user terminal 160 to obtain and send a private key.
[0290] In operation S1035, according to an example embodiment, the user terminal 160 may obtain a private key. For example, the user terminal 160 may display a pop-up window for inputting a private key on a display of the user terminal 160 and obtain a user input for writing the private key.
[0291] In operation S1040, according to an example embodiment, the beneficiary VASP server 120 may receive a private key from the user terminal 160. For example, the user terminal 160 may transmit the private key input by the user to the beneficiary VASP server 120.
[0292] Meanwhile, it is described that operations S1025 to S1040 are performed after operations S1015 and S1020, but this is an example. For example, operations S1015 and S1020 and operations S1025 to S1040 may be performed in parallel, or operations S1015 and S1020 may be performed after operations S1025 to S1040 are performed.
[0293] In operation S1045, according to an example embodiment, the beneficiary VASP server 120 may obtain a transaction identification value. For example, the beneficiary VASP server 120 may load the transaction identification value based on the beneficiary virtual asset address.
[0294] In operation S1050, according to an example embodiment, the beneficiary VASP server 120 may obtain a pair of transaction identification values and encryption results from an open server. For example, the beneficiary VASP server 120 may retrieve the obtained transaction identification value from a web server and load the pair of transaction identification value and encryption results.
[0295] Meanwhile, it is described that operations S1030 to S1040 are performed, and then operations S1045 and S1050 are performed, but this is an example. For example, operations S1030 to S1040 and operations S1045 and S1050 may be performed in parallel, or operations S1030 to S1040 may be performed after operations S1045 and S1050 are performed.
[0296] In operation S1055, according to an example embodiment, the beneficiary VASP server 120 may decrypt the encryption result. For example, the beneficiary VASP server 120 may decrypt the encryption result using the obtained private key.
[0297] In operation S1060, according to an example embodiment, the beneficiary VASP server 120 may identify whether the decryption result matches the transaction identification value.
[0298] at the same time, Fig.10 It is shown that the electronic device 100 or the beneficiary VASP server 120 encrypts or decrypts the transaction identification value and identifies a match / non-match, but it is an example and is not limited to the above example. Fig.10 In the embodiment, the electronic device 100 or the beneficiary VASP server 120 can encrypt or decrypt the full name data or DOB data and identify a match / no match.
[0299] In operation S1065, according to an example embodiment, the beneficiary VASP server 120 may reflect the transferred virtual assets to the balance of the beneficiary virtual asset address. For example, based on the transaction identification value, the beneficiary VASP server 120 may reflect the transferred virtual assets to the balance of the beneficiary virtual asset address at each configured time or whenever a response message is received.
[0300] Fig.11 1 is a flowchart for explaining a process of verifying an initiator by the electronic device 100 according to an exemplary embodiment. Here, the electronic device 100 may refer to a server existing inside a beneficiary VASP.
[0301] According to an example embodiment, a user can transfer virtual assets in his / her wallet managed by an initiator VASP to a user wallet managed by a beneficiary VASP using a user terminal 160. In other words, the initiator transferring the virtual assets and the beneficiary receiving the virtual assets can be the same.
[0302] In operation S1100, according to an example embodiment, the user terminal 160 may obtain a public key and a beneficiary virtual asset address. For example, the user terminal 160 may obtain a user input regarding the public key from the generated public key and private key pair. In addition, the user terminal 160 may obtain a user input regarding information regarding the beneficiary virtual asset address to which the virtual asset is to be transferred and the beneficiary VASP that manages the beneficiary virtual asset address.
[0303] In operation S1105, according to an example embodiment, the initiator VASP server 140 may receive a public key, a beneficiary virtual asset address, and a request to transfer a virtual asset to the beneficiary virtual asset address from the user terminal 160. For example, upon sending the public key and the beneficiary virtual asset address to the initiator VASP server 140, the user terminal 160 may request to transfer the virtual asset to the beneficiary virtual asset address.
[0304] In operation S1110, according to an example embodiment, the initiator VASP server 140 may transfer the virtual asset and identify the transaction identification value. For example, the initiator VASP server 140 may transfer the virtual asset to the beneficiary virtual asset address and may identify the transaction identification value corresponding to the transfer of the virtual asset.
[0305] In operation S1115, according to an example embodiment, the initiator VASP server 140 may encrypt the transaction identification value. For example, the initiator VASP server 140 may encrypt the transaction identification value by using the public key received from the user terminal 160 and obtain an encryption result or ciphertext.
[0306] In operation S1120, according to an example embodiment, the initiator VASP server 140 may upload the paired transaction identification value and the encryption result to an open server. For example, the initiator VASP server 140 may upload the paired transaction identification value and the encryption result to a web server accessible to all VASP servers.
[0307] In operation S1125, according to an example embodiment, the electronic device 100 may identify the virtual assets transferred to the beneficiary virtual asset address. For example, the electronic device 100 identifies the virtual assets or deposits transferred to the beneficiary virtual asset address by the initiator VASP server 140.
[0308] In operation S1130, according to an example embodiment, the electronic device 100 may send a request for a private key to the user terminal 160. For example, the electronic device 100 may request the user terminal 160 to obtain and send a private key.
[0309] In operation S1135, according to an example embodiment, the user terminal 160 may obtain a private key. For example, the user terminal 160 may display a pop-up window for inputting a private key on a display of the user terminal 160 and obtain a user input for writing the private key.
[0310] In operation S1140, according to an example embodiment, the electronic device 100 may receive a private key from the user terminal 160. For example, the user terminal 160 may transmit the private key input by the user to the electronic device 100.
[0311] Meanwhile, it is described that operations S1125 to S1140 are performed after operations S1115 and S1120 are performed, but this is an example. For example, operations S1115 and S1120 and operations S1125 to S1140 may be performed in parallel, or operations S1115 and S1120 may be performed after operations S1125 to S1140 are performed.
[0312] In operation S1145, according to an example embodiment, the electronic device 100 may obtain a transaction identification value. For example, the electronic device 100 may load the transaction identification value based on the beneficiary virtual asset address.
[0313] In operation S1150, according to an example embodiment, the electronic device 100 may obtain a pair of transaction identification value and encryption result from an open server. For example, the electronic device 100 may retrieve the obtained transaction identification value from a web server and load the pair of transaction identification value and encryption result from the web server.
[0314] Meanwhile, it is described that operations S1130 to S1140 are performed, and then operations S1145 and S1150 are performed, but this is an example. For example, operations S1130 to S1140 and operations S1145 and S1150 may be performed in parallel, or operations S1130 to S1140 may be performed after operations S1145 and S1150 are performed.
[0315] In operation S1155, according to an example embodiment, the electronic device 100 may decrypt the encryption result. For example, the electronic device 100 may decrypt the encryption result using the obtained private key.
[0316] In operation S1160, according to an example embodiment, the electronic device 100 may identify whether the decryption result and the transaction identification value match.
[0317] at the same time, Fig.11It is shown that the electronic device 100 or the initiator VASP server 140 encrypts or decrypts the transaction identification value and identifies a match / non-match, but this is an example and is not limited to the above example. Fig.11 , the electronic device 100 or the initiator VASP server 140 can encrypt or decrypt the full name data or DOB data and identify a match / no match.
[0318] In operation S1165, according to an example embodiment, the electronic device 100 may reflect the transferred virtual assets to the balance of the beneficiary's virtual asset address. For example, based on the transaction identification value, the electronic device 100 may reflect the transferred virtual assets to the balance of the beneficiary's virtual asset address at each configuration time or whenever a response message is received.
[0319] At the same time, in order to more strictly verify the sending and receiving, the electronic device 100, the beneficiary VASP server 120, the initiator VASP server 140 and the user terminal 160 can simultaneously execute the above FIG. 2A to FIG. 4B and Figures 8 to 11 For example, the electronic device 100, the beneficiary VASP server 120, the initiator VASP server 140 and the user terminal 160 may be as described in Figure 2A Identify whether the hash value of the full name matches the hash value of the DOB as described, and then Figure 8 Alternatively, the electronic device 100, the beneficiary VASP server 120, the initiator VASP server 140 and the user terminal 160 may be configured as described above. Fig.11 Identify whether the transaction identification value matches as described, and then Figure 2B In addition, the electronic device 100, the beneficiary VASP server 120, the initiator VASP server 140 and the user terminal 160 may combine the above-mentioned hash value of the full name with the hash value of the DOB in different ways. Figures 2A to 4B and Figures 8 to 11 Describes the operations to authenticate a beneficiary or initiator.
[0320] Fig.12 is a flow chart of a method of authenticating a beneficiary performed by an electronic device according to an example embodiment. For repeated descriptions, the above descriptions may apply.
[0321] In operation S1200, the electronic device may identify information about the transfer of the virtual asset, the information including the full name data of the initiator, the DOB data of the initiator, and the beneficiary virtual asset address.
[0322] In operation S1220, the electronic device may identify a set of hash values of the full name of the initiator generated based on the full name data of the initiator and a set of hash values of the DOB of the initiator generated based on the DOB data of the initiator.
[0323] According to an example embodiment, when identifying a set of hash values of the full name of the initiator and a set of hash values of the DOB of the initiator, the electronic device may remove configuration characters including a space from the full name data of the initiator.
[0324] According to an example embodiment, when identifying a hash value set of the initiator's full name and a hash value set of the initiator's DOB, the electronic device may convert letter cases of characters included in the initiator's full name data into configured cases.
[0325] According to an example embodiment, the set of hash values of the initiator's full name may include at least one of a first hash value generated based on the full name of the initiator's information consisting of a single entry in the order of a first name and a last name, a second hash value generated based on the full name of the initiator's information consisting of a single entry in the order of a last name and a first name, and a third hash value generated based on the full name information of the initiator consisting of multiple entries including a last name, a first name, and at least one middle name.
[0326] According to an example embodiment, a set of hash values of the beneficiary's full name generated based on the full name data of the beneficiary corresponding to the beneficiary's virtual asset address may include at least one of a fourth hash value generated based on the beneficiary's full name information consisting of a single entry in the order of first name and last name, a fifth hash value generated based on the beneficiary's full name information consisting of a single entry in the order of last name and first name, and a sixth hash value generated based on the beneficiary's full name information consisting of multiple entries including a last name, a first name, and at least one middle name.
[0327] In operation S1240, the electronic device may send a verification request message to the beneficiary server, the verification request message including a hash value set of the initiator's full name, a hash value set of the initiator's DOB, and a beneficiary virtual asset address.
[0328] According to an example embodiment, the verification request message may also include a value representing the type of the verification target, a value representing the type of the virtual asset, an auxiliary virtual asset address according to the virtual asset type, and at least one of a hash salt value associated with at least one of a set of hash values of the initiator's full name or a set of hash values of the initiator's DOB.
[0329] In operation S1260, the electronic device may receive a response message from the beneficiary server, the response message including verification result information generated based on the verification request message regarding whether the initiator and the beneficiary match.
[0330] According to an example embodiment, based on the verification result information, it can be determined whether to execute the virtual asset from the initiator virtual asset address of the initiator to the beneficiary virtual asset address. For example, if the response message contains information indicating that the beneficiary is verified to match the initiator, it can be determined that the transfer of the virtual asset is executed. Alternatively, if the response message contains one of the following information, it can be determined that the transfer of the virtual asset is blocked: information indicating that an address matching the beneficiary virtual asset address or the auxiliary virtual asset address is not identified in the beneficiary virtual asset address associated with the beneficiary server, information about the hash value set of the initiator's full name and the hash value set of the beneficiary's full name generated based on the beneficiary's full name data corresponding to the beneficiary virtual asset address, and information about the hash value set of the initiator's DOB and the hash value set of the beneficiary's DOB generated based on the beneficiary's DOB data.
[0331] According to an example embodiment, the verification result information may include at least one of the following information: information indicating that an address matching the beneficiary virtual asset address or the auxiliary virtual asset address is not identified in the beneficiary virtual asset address associated with the beneficiary server, information about a mismatch between a set of hash values of the initiator's full name and a set of hash values of the beneficiary's full name generated based on the beneficiary's full name data corresponding to the beneficiary virtual asset address, information about a mismatch between a set of hash values of the initiator's DOB and a set of hash values of the beneficiary's DOB generated based on the beneficiary's DOB data, or information indicating that the beneficiary is verified to match the initiator.
[0332] According to an example embodiment, if any hash value included in the hash value set of the beneficiary's full name generated based on the beneficiary's full name data corresponding to the beneficiary's virtual asset address does not match any hash value of the first hash value, the second hash value, and the third hash value, the verification result information may include information about the mismatch between the hash value set of the initiator's full name and the hash value set of the beneficiary's full name.
[0333] According to an example embodiment, if any hash value included in the hash value set of the initiator's full name does not match any hash value of the fourth hash value, the fifth hash value, and the sixth hash value, the verification result information may include information that the hash value set of the initiator's full name does not match the hash value set of the beneficiary's full name.
[0334] According to an example embodiment, with respect to the beneficiary virtual asset address, regardless of whether at least one character included in the beneficiary virtual asset address is a lowercase letter or an uppercase letter, it is possible to identify whether there is an address matching the beneficiary virtual asset address in the database of the beneficiary server. Alternatively, with respect to the beneficiary virtual asset address, a configuration prefix included in the beneficiary virtual asset address may be removed, and it is possible to identify whether there is an address matching the virtual asset address in the database of the beneficiary server.
[0335] Fig.13 is a flowchart of a method of authenticating an initiator performed by an electronic device according to an example embodiment. For repeated description, the above description may apply.
[0336] In operation S1300, the electronic device may identify the transferred virtual assets and the beneficiary virtual asset address.
[0337] In operation S1320, the electronic device may identify the full name data of the beneficiary and the DOB data of the beneficiary corresponding to the beneficiary virtual asset address.
[0338] In operation S1340, the electronic device may identify a hash value set of the full name of the beneficiary generated based on the full name data of the beneficiary and a hash value set of the DOB of the beneficiary generated based on the DOB data of the beneficiary.
[0339] According to an example embodiment, when identifying a set of hash values of the full name of the beneficiary and a set of hash values of the DOB of the beneficiary, the electronic device may remove configuration characters including a space from the full name data of the beneficiary.
[0340] According to an example embodiment, when identifying a hash value set of the beneficiary's full name and a hash value set of the beneficiary's DOB, the electronic device may convert letter cases of characters included in the beneficiary's full name data into configured cases.
[0341] According to an example embodiment, the set of hash values of the full name of the beneficiary may include at least one of the following hash values: a first hash value generated based on the full name information of the beneficiary consisting of a single entry in the order of the first name and the last name, a second hash value generated based on the full name information of the beneficiary consisting of a single entry in the order of the last name and the first name, or a third hash value generated based on the full name information of the beneficiary consisting of multiple entries including the last name, the first name, and at least one middle name.
[0342] According to an example embodiment, a set of hash values of the initiator's full name corresponding to a beneficiary's virtual asset address or a transaction identification value may include a fourth hash value generated based on the full name of the initiator's information consisting of a single entry in the order of first name and last name, a fifth hash value generated based on the initiator's full name information consisting of a single entry in the order of last name and first name, and a sixth hash value generated based on the initiator's full name information consisting of multiple entries including a last name, a first name, and at least one middle name.
[0343] In operation S1360, the electronic device may send a verification request message including a hash value set of the full name of the beneficiary, a hash value set of the DOB of the beneficiary, and a virtual asset address of the beneficiary to the initiator server.
[0344] According to an example embodiment, the verification request message may also include at least one of the following: a transaction identification value corresponding to the transfer of a virtual asset, a value indicating the type of a verification target, a value indicating the type of a virtual asset to be transferred, an auxiliary virtual asset address according to the type of the virtual asset, or a hash salt value associated with at least one of a set of hash values of the beneficiary's full name or a set of hash values of the beneficiary's DOB.
[0345] In operation S1380, the electronic device may receive a response message from the initiator server, the response message including verification result information generated based on the verification request message regarding whether the beneficiary and the initiator match.
[0346] According to an example embodiment, the verification result information may include one of the following information: information indicating that a value matching the transaction identification value is not identified in the transaction identification value associated with the initiator server; information indicating that an address matching the beneficiary virtual asset address or the auxiliary virtual asset address is not identified in the virtual asset address associated with the initiator server; information about a mismatch between a set of hash values of the beneficiary's full name and a set of hash values of the initiator's full name generated based on the initiator's full name data corresponding to the beneficiary virtual asset address or the transaction identification value; information about a mismatch between a set of hash values of the beneficiary's DOB and a set of hash values of the initiator's DOB generated based on the initiator's DOB data; and information indicating that the initiator is verified as matching the beneficiary.
[0347] According to an example embodiment, if a hash value of any one of a set of hash values of the initiator's full name corresponding to the beneficiary's virtual asset address or transaction identification value does not match any one of the first hash value, the second hash value, and the third hash value, the verification result information may include information that the set of hash values of the beneficiary's full name does not match the set of hash values of the initiator's full name.
[0348] According to an example embodiment, if a hash value of any one of the hash value sets of the beneficiary's full name does not match any one of the fourth hash value, the fifth hash value, and the sixth hash value, the verification result information may include information that the hash value set of the beneficiary's full name does not match the hash value set of the initiator's full name.
[0349] According to an example embodiment, if the verification result information includes information indicating that the initiator is verified to match the beneficiary, the virtual asset may be reflected in the balance of the beneficiary's virtual asset address at each configuration time based on the transaction identification value.
[0350] According to an example embodiment, with respect to the beneficiary virtual asset address, regardless of whether at least one character included in the beneficiary virtual asset address is a lowercase letter or an uppercase letter, it is possible to identify whether there is an address matching the beneficiary virtual asset address in the database of the initiator server. Alternatively, with respect to the beneficiary virtual asset address, a configuration prefix included in the beneficiary virtual asset address may be removed, and it is possible to identify whether there is an address matching the beneficiary virtual asset address in the database of the initiator server.
[0351] According to an example embodiment, with respect to the transaction identification value, regardless of whether at least one character in the transaction identification value is a lowercase letter or an uppercase letter, it can be recognized that a value matching the transaction identification value exists in the database of the initiator server. Alternatively, with respect to the transaction identification value, if the type of the transaction identification value includes an identifier type and a hash value type, a transaction identification value of the hash value type can be used to determine whether a value matching the transaction identification value exists in the database of the initiator server. With respect to the transaction identification value, a transaction identification value including a leading zero value can be used to recognize whether a value matching the transaction identification value exists in the database of the initiator server.
[0352] Fig.14 is a block diagram of an electronic device 100 according to an example embodiment.
[0353] According to an example embodiment, the electronic device 100 may include a memory 1400 and one or more processors 1450. Fig.14 In the electronic device 100 shown, only elements related to the exemplary embodiment are shown. Therefore, those skilled in the art can understand that, except for Fig.14 In addition to the elements shown, other common elements may also be included.
[0354] For example, according to an example embodiment, the electronic device may include a communication device (not shown). The communication device is a device for performing wired / wireless communication and can communicate with an external electronic device. The external electronic device may be a terminal or a server. In addition, the communication technology used by the communication device may include a global system for mobile communications (GSM), code division multiple access (CDMA), long term evolution (LTE), 5G, wireless LAN (WLAN) and wireless fidelity (Wi-Fi), Bluetooth, radio frequency identification (RFID), infrared data association (IrDA), ZigBee and near field communication (NFC).
[0355] The one or more processors 1450 may control the overall operation of the electronic device 100 and process data and signals. The one or more processors 1450 may be composed of at least one hardware unit. In addition, the one or more processors 1450 may be operated by one or more software modules generated by executing one or more instructions stored in the memory 1400.
[0356] One or more processors 1450 may be configured to identify information about the transfer of virtual assets including the initiator's full name data, the initiator's DOB data, and the beneficiary's virtual asset address, identify a hash value set of the initiator's full name generated based on the initiator's full name data and a hash value set of the initiator's DOB generated based on the initiator's DOB data, send a verification request message including the hash value set of the initiator's full name, the hash value set of the initiator's DOB, and the beneficiary's virtual asset address to a beneficiary server, and receive a response message from the beneficiary server including verification result information generated based on the verification request message.
[0357] One or more processors 1450 may be configured to identify the transferred virtual assets and the beneficiary's virtual asset address, identify the beneficiary's full name data and the beneficiary's DOB data corresponding to the beneficiary's virtual asset address, identify a hash value set of the beneficiary's full name generated based on the beneficiary's full name data and a hash value set of the beneficiary's DOB generated based on the beneficiary's DOB data, send a verification request message including the hash value set of the beneficiary's full name, the hash value set of the beneficiary's DOB, and the beneficiary's virtual asset address to an initiator server, and receive a response message from the initiator server including verification result information generated based on the verification request message.
[0358] The electronic device according to the above-mentioned example embodiment may include a processor, a memory for storing and executing program data, a permanent memory such as a disk drive and / or a user interface device such as a communication port, a touch panel, a key and / or a button for communicating with an external device. The method implemented as a software module or an algorithm can be stored in a computer-readable recording medium as a computer-readable code or program instruction that can be executed on a processor. Here, a computer-readable recording medium includes a magnetic storage medium (e.g., ROM, RAM, a floppy disk and a hard disk) and an optically readable medium (e.g., CD-ROM and DVD). The computer-readable recording medium can be distributed between network-connected computer systems so that the computer-readable code can be stored and executed in a distributed manner. The medium can be read by a computer, stored in a memory, and executed on a processor.
[0359] Example implementations can be represented by functional block elements and various processing steps. Functional blocks can be implemented with any number of hardware and / or software configurations that perform specific functions. For example, example implementations can use integrated circuit configurations that can perform various functions by controlling one or more microprocessors or other control devices, such as memory, processing, logic and / or lookup tables. Similar to the element can be implemented as software programming or software elements, example implementations can be implemented with programming or scripting languages such as C, C++, Java, assemblers, etc., including various algorithms implemented as a combination of data structures, processes, routines or other programming constructs. Functional aspects can be implemented in algorithms running on one or more processors. In addition, example implementations can use prior art to perform electronic environment settings, signal processing and / or data processing. Terms such as "mechanism", "element", "device" and "configuration" can be used extensively and are not limited to mechanical and physical elements. These terms can include the meaning of a series of software routines associated with processors, etc.
[0360] The above-described exemplary embodiments are merely examples, and other embodiments may be implemented within the scope of the claims described later.
[0361] In light of the above detailed description, these and other changes can be made to the embodiments. In general, in the appended claims, the terms used should not be interpreted to limit the claims to the specific embodiments disclosed in the specification and claims, but should be interpreted to include all possible embodiments and the full range of equivalents to which such claims are entitled. Therefore, the claims are not limited by the disclosure.
Claims
1. A method for verifying a beneficiary performed by an electronic device, the method comprising: identifying information regarding the transfer of a virtual asset, the information including the full name data of the originator, the date of birth (DOB) data of the originator, and the beneficiary virtual asset address; identifying a set of hash values of the initiator's full name generated based on the full name data of the initiator and a set of hash values of the initiator's DOB generated based on the DOB data of the initiator; Sending a verification request message to the beneficiary server, the verification request message including a hash value set of the initiator's full name, a hash value set of the initiator's DOB, and the beneficiary's virtual asset address; as well as receiving a response message from the beneficiary server, the response message including verification result information generated based on the verification request message regarding whether the initiator matches the beneficiary, Wherein, based on the verification result information, it is determined whether to transfer the virtual asset from the initiator virtual asset address of the initiator to the beneficiary virtual asset address.
2. The method according to claim 1, wherein the verification request message further includes at least one of the following: A value representing the type of the verification target; a value representing the type of the virtual asset; an auxiliary virtual asset address according to the type of the virtual asset; or A hash salt value associated with at least one of the set of hash values of the originator's full name or the set of hash values of the originator's DOB.
3. The method according to claim 2, wherein the verification result information includes at least one of the following information: information indicating that no address matching the beneficiary virtual asset address or the auxiliary virtual asset address was identified among the virtual asset addresses associated with the beneficiary server; Information about a mismatch between a set of hash values of the initiator's full name and a set of hash values of the beneficiary's full name generated based on the beneficiary's full name data corresponding to the beneficiary's virtual asset address, or information about a mismatch between a set of hash values of the initiator's DOB and a set of hash values of the beneficiary's DOB generated based on the beneficiary's DOB data; or Information indicating that the beneficiary is verified to match the initiator.
4. The method according to claim 3, wherein: In a case where the response message includes information indicating that the beneficiary is verified as matching the initiator, determining to perform the transfer of the virtual asset; as well as It is determined that the transfer of the virtual asset is blocked when the response message includes one of the following information: information indicating that an address matching the beneficiary virtual asset address or the auxiliary virtual asset address is not identified in the virtual asset addresses associated with the beneficiary server, information about a mismatch between a set of hash values of the initiator's full name and a set of hash values of the beneficiary's full name generated based on the beneficiary's full name data corresponding to the beneficiary virtual asset address, or information about a mismatch between a set of hash values of the initiator's DOB and a set of hash values of the beneficiary's DOB generated based on the beneficiary's DOB data.
5. The method of claim 1 , wherein identifying the set of hash values of the full name of the originator and the set of hash values of the DOB of the originator comprises: Remove spaces from the originator's full name data.
6. The method of claim 1 , wherein identifying the set of hash values of the full name of the originator and the set of hash values of the DOB of the originator comprises: The letter case of the characters included in the full name data of the initiator is changed to the configured letter case.
7. The method according to claim 1, wherein: The set of hash values of the full name of the initiator includes at least one of the following hash values: a first hash value generated based on full name information of the originator consisting of a single entry in order of first name and last name; a second hash value generated based on full name information of the originator consisting of a single entry in the order of the last name and the first name; or A third hash value is generated based on the initiator's full name information consisting of a plurality of entries including the last name, the first name, and at least one middle name.
8. The method according to claim 7, wherein, in a case where any hash value included in the hash value set of the beneficiary's full name generated based on the full name data of the beneficiary corresponding to the beneficiary's virtual asset address does not match any hash value of the first hash value, the second hash value and the third hash value, the verification result information includes information about the mismatch between the hash value set of the initiator's full name and the hash value set of the beneficiary's full name.
9. A method for verifying an initiator performed by an electronic device, the method comprising: Identify the virtual assets being transferred and the virtual asset address of the beneficiary; Identify the full name data of the beneficiary corresponding to the beneficiary's virtual asset address and the DOB data of the beneficiary; identifying a set of hash values of the full name of the beneficiary generated based on the full name data of the beneficiary and a set of hash values of the DOB of the beneficiary generated based on the DOB data of the beneficiary; Sending a verification request message to the initiator server, the verification request message including a hash value set of the full name of the beneficiary, a hash value set of the DOB of the beneficiary, and the virtual asset address of the beneficiary; as well as A response message is received from the initiator server, the response message including verification result information generated based on the verification request message regarding whether the beneficiary matches the initiator.
10. The method according to claim 9, wherein the verification request message further includes at least one of the following: A transaction identification value corresponding to the transfer of virtual assets; A value representing the type of the verification target; A value representing the type of the virtual asset; an auxiliary virtual asset address according to the type of the virtual asset; and A hash salt value associated with at least one of the set of hash values of the full name of the beneficiary or the set of hash values of the DOB of the beneficiary.
11. The method according to claim 10, wherein the verification result information includes at least one of the following information: information indicating that no value matching the transaction identification value is identified among the transaction identification values associated with the initiator server; information indicating that no address matching the beneficiary virtual asset address or the auxiliary virtual asset address was identified among the virtual asset addresses associated with the initiator server; Information about a mismatch between a set of hash values of the beneficiary's full name and a set of hash values of the initiator's full name generated based on the beneficiary's virtual asset address or the initiator's full name data corresponding to the transaction identification value, or information about a mismatch between a set of hash values of the beneficiary's DOB and a set of hash values of the initiator's DOB generated based on the initiator's DOB data; or Information indicating that the initiator is verified to match the beneficiary.
12. The method according to claim 11, further comprising: In a case where the verification result information includes information indicating that the initiator is verified to match the beneficiary, the virtual asset is reflected to the balance of the beneficiary's virtual asset address based on the transaction identification value at each configured time.
13. A computer-readable recording medium having a program for executing the method of claims 1 to 12 on a computer.
14. An electronic device, comprising: one or more processors; as well as a memory for storing one or more instructions to be executed by the one or more processors, The one or more processors are configured to: identifying information regarding the transfer of a virtual asset, the information including the full name data of the originator, the date of birth (DOB) data of the originator, and the beneficiary virtual asset address; identifying a set of hash values of the initiator's full name generated based on the full name data of the initiator and a set of hash values of the initiator's DOB generated based on the DOB data of the initiator; Sending a verification request message to the beneficiary server, the verification request message including a hash value set of the initiator's full name, a hash value set of the initiator's DOB, and the beneficiary's virtual asset address; as well as receiving a response message from the beneficiary server, the response message including verification result information generated based on the verification request message regarding whether the initiator matches the beneficiary, Wherein, based on the verification result information, it is determined whether to transfer the virtual asset from the initiator virtual asset address of the initiator to the beneficiary virtual asset address.
15. An electronic device, comprising: one or more processors; as well as a memory for storing one or more instructions to be executed by the one or more processors, The one or more processors are configured to: Identify the virtual assets being transferred and the virtual asset address of the beneficiary; Identify the full name data of the beneficiary corresponding to the beneficiary's virtual asset address and the DOB data of the beneficiary; identifying a set of hash values of the full name of the beneficiary generated based on the full name data of the beneficiary and a set of hash values of the DOB of the beneficiary generated based on the DOB data of the beneficiary; Sending a verification request message to the initiator server, the verification request message including a hash value set of the full name of the beneficiary, a hash value set of the DOB of the beneficiary, and the virtual asset address of the beneficiary; as well as A response message is received from the initiator server, the response message including verification result information generated based on the verification request message regarding whether the beneficiary matches the initiator.
