A binding wallet adjustment method and device of a hardware wallet device

Abstract

This invention discloses a method and apparatus for adjusting the bound wallet of a hardware wallet device, relating to the field of digital currency wallet technology. The specific implementation of the method includes: generating an authorization request based on the wallet identity information of a terminal, sending the authorization request to the hardware wallet device, so that the hardware wallet device generates authorization response information based on the authorization request; receiving the authorization response information sent by the hardware wallet device, and sending a binding request to the target operating system associated with the hardware wallet device based on the currently bound wallet identification information in the authorization response information; wherein, the binding request includes hardware wallet identification information and terminal wallet identification information, so that the target operating system binds the hardware wallet identification information with the terminal wallet identification information. This implementation can bind a hardware wallet to a specific user, facilitating the tracing of the hardware wallet's transaction process, thereby constructing transaction network model data and improving user experience.

Description

Technical Field

[0001] This invention relates to the field of digital currency wallet technology, and in particular to a method and apparatus for adjusting the binding wallet of a hardware wallet device. Background Technology

[0002] Existing hardware wallets require users to bind their accounts (such as mobile phone numbers) and other identity information before they can be used. However, for foreigners who have just entered the country, the elderly, and other users who find it inconvenient to bind their identity information, their identity and age restrictions prevent them from binding their accounts with mobile phone numbers and other identity information, making it extremely inconvenient for them to use the wallets. This limits the use cases of hardware wallets and thus restricts the application scenarios of digital currencies. Summary of the Invention

[0003] In view of this, embodiments of the present invention provide a method and apparatus for adjusting the binding wallet of a hardware wallet device, which can bind the hardware wallet to a specific user, facilitate the tracing of the transaction process of the hardware wallet, and thus construct transaction network model data. At the same time, it can meet various transaction needs of users, improve the convenience of user transactions, and enhance the user experience.

[0004] To achieve the above objectives, according to one aspect of the present invention, a method for adjusting the bound wallet of a hardware wallet device is provided, the method being applied to a terminal, the method comprising:

[0005] An authorization request is generated based on the wallet identity information of the terminal, and the authorization request is sent to the hardware wallet device so that the hardware wallet device generates authorization response information based on the authorization request; wherein, the wallet identity information includes the wallet identification information of the terminal, and the authorization response information includes the hardware wallet identification information of the hardware wallet device and the currently bound wallet identification information;

[0006] The system receives authorization response information from the hardware wallet device and, based on the currently bound wallet identification information in the authorization response information, sends a binding request to the target operating system associated with the hardware wallet device. The binding request includes hardware wallet identification information and the wallet identification information of the terminal, so that the target operating system binds the hardware wallet identification information with the wallet identification information of the terminal.

[0007] According to another aspect of the present invention, a method for adjusting the bound wallet of a hardware wallet device is provided, the method being applied to the hardware wallet device, the method comprising:

[0008] The terminal receives an authorization request; wherein the authorization request indicates the terminal's wallet identification information.

[0009] Based on the currently bound wallet identification information and hardware wallet identification information, an authorization response information is generated;

[0010] The authorization response information is sent to the terminal, so that the terminal sends a binding request to the target operating system associated with the currently bound wallet identification information based on the authorization response information, thereby enabling the target operating system to bind the hardware wallet identification information with the wallet identification information of the terminal.

[0011] According to another aspect of the present invention, a method for adjusting the bound wallet of a hardware wallet device is provided, the method being applied to a target operating institution system, the method comprising:

[0012] The receiving terminal sends a binding request; wherein the binding request includes the currently bound wallet identification information of the hardware wallet device;

[0013] When the hardware wallet device is not bound, the hardware wallet identification information is bound to the wallet identification information of the terminal.

[0014] The binding response information is sent to the terminal, so that the terminal sends the binding response information to the hardware wallet device, thereby binding the hardware wallet device with the wallet identification information of the terminal.

[0015] According to another aspect of the present invention, a wallet binding adjustment device for a hardware wallet device is provided, the device comprising:

[0016] The authorization request module is used to generate an authorization request based on the wallet identity information of the terminal, and send the authorization request to the hardware wallet device so that the hardware wallet device generates authorization response information based on the authorization request; wherein, the wallet identity information includes the wallet identification information of the terminal, and the authorization response information includes the hardware wallet identification information of the hardware wallet device and the currently bound wallet identification information;

[0017] The binding request module is used to receive authorization response information sent by the hardware wallet device, and send a binding request to the target operating system associated with the hardware wallet device according to the currently bound wallet identification information in the authorization response information; wherein, the binding request includes hardware wallet identification information and the wallet identification information of the terminal, so that the target operating system binds the hardware wallet identification information with the wallet identification information of the terminal.

[0018] According to another aspect of the present invention, a hardware wallet device is provided, the hardware wallet device comprising:

[0019] A receiving module is used to receive an authorization request sent by a terminal; wherein the authorization request indicates the wallet number information of the terminal;

[0020] The generation module is used to generate authorization response information based on the currently bound wallet identification information and hardware wallet identification information;

[0021] The sending module is used to send the authorization response information to the terminal, so that the terminal sends a binding request to the target operating system associated with the currently bound wallet identification information according to the authorization response information, thereby enabling the target operating system to bind the hardware wallet identification information with the wallet identification information of the terminal.

[0022] According to another aspect of the present invention, a target operating organization system is provided, the target operating organization system comprising:

[0023] A receiving module is used to receive a binding request sent by a terminal; wherein the binding request includes the current bound wallet identification information of the hardware wallet device;

[0024] A binding module is used to bind the hardware wallet identification information to the wallet identification information of the terminal when the binding status of the hardware wallet device is unbound.

[0025] The sending module is used to send binding response information to the terminal, so that the terminal sends the binding response information to the hardware wallet device, thereby binding the hardware wallet device with the wallet identification information of the terminal.

[0026] According to another aspect of the present invention, a digital currency system is provided, wherein the target operating institution system includes: a terminal, a hardware wallet, and the target operating institution system; wherein,

[0027] The terminal's digital currency application generates an authorization request based on the terminal's wallet identity information and sends the authorization request to the hardware wallet; wherein, the wallet identity information includes the terminal's wallet identification information.

[0028] The hardware wallet generates authorization response information based on the hardware wallet identification information and the currently bound wallet identification information;

[0029] The terminal's digital currency application receives the authorization response information sent by the hardware wallet, and sends the binding request to the target operating institution system associated with the hardware wallet based on the currently bound wallet identification information in the authorization response information;

[0030] When the target operating institution system is not bound to the hardware wallet, it binds the hardware wallet identification information to the wallet identification information of the terminal.

[0031] According to another aspect of the present invention, a hardware wallet device is provided for adjusting the wallet binding electronic device, comprising:

[0032] One or more processors;

[0033] Storage device for storing one or more programs.

[0034] When the one or more programs are executed by the one or more processors, the one or more processors implement the binding wallet adjustment method of the hardware wallet device provided by the present invention.

[0035] According to another aspect of the present invention, a computer-readable medium is provided having a computer program stored thereon, which, when executed by a processor, implements the binding wallet adjustment method of the hardware wallet device provided by the present invention.

[0036] One embodiment of the above invention has the following advantages or beneficial effects: because it adopts the technical means of binding the hardware wallet number information of the hardware wallet device to the user account information of the digital currency application on the terminal, it overcomes the technical problem that the use scenarios of existing hardware wallets are limited, thereby limiting the application scenarios of digital currency. It can then bind the hardware wallet to a specific user, making it easier to trace the transaction process of the hardware wallet, thereby constructing transaction network model data. At the same time, it can meet various transaction needs of users, improve the convenience of user transactions, and enhance the technical effect of user experience.

[0037] The further effects of the aforementioned unconventional alternative methods will be explained below in conjunction with specific implementation methods. Attached Figure Description

[0038] The accompanying drawings are provided to better understand the invention and are not intended to unduly limit the scope of the invention. Wherein:

[0039] Figure 1 This is a schematic diagram of the main process of a method for adjusting the bound wallet of a hardware wallet device according to the first embodiment of the present invention;

[0040] Figure 2 This is a schematic diagram of the main process of a method for adjusting the bound wallet of a hardware wallet device according to a second embodiment of the present invention;

[0041] Figure 3 This is a schematic diagram of the main process of a method for adjusting the bound wallet of a hardware wallet device according to a third embodiment of the present invention;

[0042] Figure 4 This is a schematic diagram of the main modules of the binding wallet adjustment device of the hardware wallet device according to an embodiment of the present invention;

[0043] Figure 5 This is a schematic diagram of the main modules of a hardware wallet device according to an embodiment of the present invention;

[0044] Figure 6 This is a schematic diagram of the main modules of the target operating organization system according to an embodiment of the present invention;

[0045] Figure 7 This is a schematic diagram of a digital currency system according to an embodiment of the present invention;

[0046] Figure 8 This is a schematic diagram of the interaction process of a digital currency system according to an embodiment of the present invention;

[0047] Figure 9 An exemplary system architecture diagram is shown, which illustrates a method for adjusting the bound wallet of a hardware wallet device suitable for application in embodiments of the present invention.

[0048] Figure 10 This is a schematic diagram of the structure of a computer system suitable for implementing terminal devices or servers of the present invention. Detailed Implementation

[0049] The following description, in conjunction with the accompanying drawings, illustrates exemplary embodiments of the present invention, including various details to aid understanding. These details should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the invention. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0050] The embodiments of the present invention provide a method for adjusting the bound wallet of a hardware wallet device. The hardware wallet in the embodiments of the present invention refers to a hardware wallet that is not associated with the user's identity at the time of issuance, but only with the public account of the issuing institution. It has a unique hardware wallet number, stores digital identity credentials in the form of a security chip, and stores the coin string in the back-end system of the operating institution.

[0051] Figure 1 This is a schematic diagram of the main flow of the wallet binding adjustment method of the hardware wallet device according to the first embodiment of the present invention, as shown below. Figure 1 As shown, the method for adjusting the bound wallet of the hardware wallet device of the present invention is applied to a terminal and includes the following steps:

[0052] Step S101: Generate an authorization request based on the terminal's wallet identity information, and send the authorization request to the hardware wallet device so that the hardware wallet device generates authorization response information based on the authorization request; wherein, the wallet identity information includes the terminal's wallet identification information, and the authorization response information includes the hardware wallet identification information of the hardware wallet device and the currently bound wallet identification information.

[0053] Existing hardware wallets require users to bind their mobile phone numbers or other identity information before use. This is extremely inconvenient for newly arrived foreigners, the elderly, and other users who find it difficult to bind their identity information, thus limiting the usage scenarios of hardware wallets. Therefore, this invention provides a hardware wallet binding method that personalizes the hardware wallet, transferring it from a public account to an existing user account within a digital currency application. This allows newly arrived foreigners, the elderly, and others to use the hardware wallet through their existing user accounts in digital currency applications, greatly facilitating these special groups. Furthermore, it allows for the tracking of hardware wallet transactions, thereby constructing transaction network model data.

[0054] In this embodiment of the invention, the wallet carrier of the terminal can be a software wallet or a hardware wallet. The hardware wallet can be in various forms such as a SIM card, IC card, SE chip, bracelet, watch, badge, access card, etc.

[0055] The wallet identity information of the terminal includes wallet identification information, keys, etc. The wallet identification information of the terminal includes wallet number information, user account information, etc. The hardware wallet device is not bound to the user account. In order to facilitate the transaction of the user corresponding to the hardware wallet device, the binding wallet adjustment method of the hardware wallet device of the present invention is used to bind the user account information of the hardware wallet device to the wallet of the terminal. This enables the user of the hardware wallet device to conduct transactions through the digital currency application of the existing user account, which facilitates the tracing of the transaction process of the hardware wallet and thus constructs transaction network model data.

[0056] In this embodiment of the invention, for example, in a real-world scenario, the user corresponding to the hardware wallet device is a special group such as a newly arrived foreigner or an elderly person, while the user corresponding to the terminal wallet is a user who has already bound their account and can conduct transactions through a digital currency application. To bind the hardware wallet device to the user account corresponding to the terminal wallet, the user corresponding to the hardware wallet device can send a request face-to-face to the user corresponding to the terminal wallet. This allows the user corresponding to the terminal wallet to operate through the terminal, and the digital currency application corresponding to the terminal wallet executes the hardware wallet binding adjustment method of the first embodiment of the invention. The terminal's digital currency application communicates with the hardware wallet device via NFC, Bluetooth, or other functions, sending authorization requests to the hardware wallet device.

[0057] Among them, the user account corresponding to the wallet on the terminal can be the user account of a special group. For example, a foreigner who has just entered the country may purchase a hardware wallet device that is bound to a public account (referring to a public account corresponding to the operating institution of the hardware wallet device, such as a bank public account). After the user later applies for a software wallet or hardware wallet with a corresponding personal account, the hardware wallet device can be adjusted to be bound to the personal account. Another example is an elderly person who purchases a hardware wallet device that is bound to a public account and adjusts the hardware wallet device to be bound to the software wallet or hardware wallet of a relative.

[0058] In this embodiment of the invention, the terminal's digital currency application encrypts the authorization request using a key based on its built-in encryption algorithm, determines the corresponding hash value, and sends the encrypted authorization request to the hardware wallet device. Upon receiving the authorization request, the hardware wallet device verifies the key according to the authorization request and generates authorization response information, specifically:

[0059] The hardware wallet device determines the corresponding hash value based on the key indicated in the authorization request and the encryption algorithm built into the hardware wallet device. If the hash value determined by the hardware wallet device matches the hash value determined by the cryptocurrency application, it indicates successful key verification, and the device obtains the relevant information for the authorization request. The hardware wallet device generates authorization response information based on the authorization request. This response information includes the hardware wallet identification information and the currently bound wallet identification information. The hardware wallet identification information includes the hardware wallet number and password, while the currently bound wallet identification information may include the currently bound wallet number and unique mapping information.

[0060] Furthermore, the currently bound wallet number information refers to the wallet number information currently bound to the hardware wallet number information; the unique mapping information refers to the mapping information between the hardware wallet number information and the operating institution system corresponding to the hardware wallet device.

[0061] Step S102: Receive authorization response information sent by the hardware wallet device; based on the currently bound wallet identification information in the authorization response information, send a binding request to the target operating system associated with the hardware wallet device; wherein, the binding request includes hardware wallet identification information and the wallet identification information of the terminal, so that the target operating system binds the hardware wallet identification information with the wallet identification information of the terminal.

[0062] In this embodiment of the invention, before sending the binding request to the target operating system associated with the hardware wallet device, the hardware wallet password information verification request indicated by the authorization response information is processed, specifically:

[0063] Receives a string corresponding to the hardware wallet password information input by the user of the digital currency application on the terminal;

[0064] The string is sent to the target operating system, which then verifies the string based on the hardware wallet password information corresponding to the hardware wallet device.

[0065] Furthermore, the target operating institution's system locally stores the correspondence between the hardware wallet number information and the hardware wallet password information.

[0066] In this embodiment of the invention, the binding status of the hardware wallet device can be stored within the hardware wallet device and / or in the target operating institution system corresponding to the hardware wallet device.

[0067] When the binding status of the hardware wallet device is stored within the hardware wallet device:

[0068] The currently bound wallet identification information includes the currently bound wallet number and unique mapping information. Specifically,

[0069] The terminal's digital currency application determines the binding status of the hardware wallet device based on the currently bound wallet ID information; specifically, if the currently bound wallet ID information is a public account, the binding status of the hardware wallet device is determined to be unbound; if the currently bound wallet ID information is a user account, the binding status of the hardware wallet device is determined to be bound.

[0070] When the hardware wallet device is not bound, the terminal's digital currency application determines the target operating institution system corresponding to the hardware wallet device based on the unique mapping information in the currently bound wallet identification information.

[0071] The terminal's digital currency application sends a binding request to the target operating system associated with the hardware wallet device, so that the target operating system binds the hardware wallet identification information (hardware wallet number) with the user account information (wallet identification information) of the terminal, and generates binding response information based on the binding result.

[0072] When the binding status of the hardware wallet device is stored in the target operator's system:

[0073] The currently bound wallet identification information includes unique mapping information, specifically,

[0074] The terminal's digital currency application uses the unique mapping information in the currently bound wallet identification information to determine the target operating institution system corresponding to the hardware wallet device, and sends the binding request to the target operating institution system associated with the hardware wallet device.

[0075] The target operating institution system determines the binding status of the hardware wallet device based on the binding status information corresponding to the hardware wallet number information of the hardware wallet identification information in the local system.

[0076] When the hardware wallet device is not bound, the target operator system binds the hardware wallet number information of the hardware wallet identification information with the user account information of the wallet identification information of the terminal, and generates binding response information based on the successful binding result.

[0077] If the hardware wallet device is already bound, the target operating system generates a binding response message based on the binding failure result.

[0078] In this embodiment of the invention, after sending the binding request to the target operating system associated with the hardware wallet device, the method further includes:

[0079] Receive binding response information returned by the target operator's system; the binding response information includes the binding result and the adjusted bound wallet identification information;

[0080] When the binding status of the hardware wallet device is stored within the hardware wallet device:

[0081] If the binding result is successful, the binding response information is sent to the hardware wallet device, so that the hardware wallet device stores the adjusted binding wallet identification information corresponding to the hardware wallet device indicated by the binding response information, and sets the binding status to "bound".

[0082] Furthermore, the adjusted bound wallet identification information may include adjusted bound wallet number information, so that the hardware wallet device stores the adjusted bound wallet number information corresponding to the hardware wallet device.

[0083] When the binding status of the hardware wallet device is stored in the target operator's system:

[0084] If the binding result is successful, the target operating institution's system stores the adjusted bound wallet number information of the adjusted bound wallet identification information, and sets the binding status corresponding to the hardware wallet identification information to "bound".

[0085] In this embodiment of the invention, if the binding result is successful, a wallet addition prompt message is output so that the user can trigger an addition request based on the addition prompt message;

[0086] In response to the add request, the hardware wallet number information of the hardware wallet identification information is added to the wallet list corresponding to the user account information of the terminal's wallet identification information, so that the hardware wallet number information of the hardware wallet identification information is bound to the user account information of the terminal's wallet identification information.

[0087] In this embodiment of the invention, an authorization request is generated based on the wallet identity information of the terminal, and the authorization request is sent to a hardware wallet device, so that the hardware wallet device generates authorization response information based on the authorization request. The wallet identity information includes the wallet identification information of the terminal, and the authorization response information includes the hardware wallet identification information of the hardware wallet device and the currently bound wallet identification information. The process involves receiving the authorization response information sent by the hardware wallet device, and based on the currently bound wallet identification information in the authorization response information, sending a binding request to the target operating system associated with the currently bound wallet identification information. The binding request includes the hardware wallet identification information and the wallet identification information of the terminal, so that the target operating system binds the hardware wallet identification information with the wallet identification information of the terminal. These steps enable the binding of a hardware wallet to a specific user, facilitating the tracing of the hardware wallet's transaction process, thereby constructing transaction network model data. Simultaneously, it can meet various transaction needs of users, improve the convenience of user transactions, and enhance the user experience.

[0088] In embodiments of the present invention, such as Figure 2 As shown, the hardware wallet binding method of the second embodiment of the present invention is applied to a hardware wallet device and includes the following steps:

[0089] Step S201: Receive an authorization request sent by the terminal; wherein the authorization request indicates the wallet identification information of the terminal.

[0090] In this embodiment of the invention, the terminal's digital currency application encrypts the authorization request using a key based on its built-in encryption algorithm, determines the corresponding hash value, and sends the encrypted authorization request to the hardware wallet device. Upon receiving the authorization request, the hardware wallet device determines the corresponding hash value based on the key indicated in the authorization request and the encryption algorithm built into the hardware wallet device.

[0091] If the hash value determined by the hardware wallet device is the same as the hash value determined by the digital currency application, it indicates that the key verification is successful, and the hardware wallet device obtains the relevant information of the corresponding authorization request.

[0092] Step S202: Generate authorization response information based on the currently bound wallet identification information and hardware wallet identification information.

[0093] In this embodiment of the invention, the hardware wallet device generates authorization response information based on the currently bound wallet identification information and the hardware wallet identification information. The authorization response information indicates a hardware wallet password information verification request, which enables the digital currency application to receive the string corresponding to the hardware wallet password information input by the user according to the hardware wallet password information verification request, and send the string to the target operating institution system, so that the target operating institution system can verify the string according to the local hardware wallet password information corresponding to the hardware wallet device.

[0094] Step S203: Send the authorization response information to the terminal so that the terminal sends a binding request to the target operating system associated with the currently bound wallet identification information based on the authorization response information, thereby enabling the target operating system to bind the hardware wallet identification information with the wallet identification information of the terminal.

[0095] In this embodiment of the invention, when the binding state of the hardware wallet device is stored within the hardware wallet device:

[0096] The currently bound wallet identification information includes the currently bound wallet number and a unique mapping information, enabling the terminal's digital currency application to determine the binding status of the hardware wallet device based on the currently bound wallet number. If the hardware wallet device is not bound, the terminal's digital currency application determines the target operating system corresponding to the hardware wallet device based on the unique mapping information in the currently bound wallet identification information. The terminal's digital currency application sends a binding request to the target operating system associated with the hardware wallet device, so that the target operating system binds the hardware wallet number information of the hardware wallet identification information with the user account information of the terminal's wallet identification information, and generates binding response information based on the binding result.

[0097] When the binding status of the hardware wallet device is stored in the target operator's system:

[0098] The current bound wallet identification information includes unique mapping information, which enables the terminal's digital currency application to determine the target operating institution system corresponding to the hardware wallet device through the unique mapping information in the current bound wallet identification information, and send the binding request to the target operating institution system associated with the hardware wallet device.

[0099] The system enables the target operator's system to determine the binding status of the hardware wallet device based on the binding status information corresponding to the hardware wallet number information of the hardware wallet identification information. If the binding status of the hardware wallet device is unbound, the target operator's system binds the hardware wallet number information of the hardware wallet identification information with the user account information of the wallet identification information of the terminal, and generates binding response information based on the binding success result. If the binding status of the hardware wallet device is bound, the target operator's system generates binding response information based on the binding failure result.

[0100] In this embodiment of the invention, when the binding state of the hardware wallet device is stored within the hardware wallet device, the method further includes:

[0101] The receiving terminal receives the binding response information sent by the digital currency application;

[0102] The system stores the adjusted bound wallet number information, which corresponds to the adjusted bound wallet identification information of the hardware wallet device, as indicated by the binding response information, and sets the binding status to "bound".

[0103] In this embodiment of the invention, the process involves receiving an authorization request sent by a terminal, wherein the authorization request indicates the terminal's wallet identification information; generating authorization response information based on the currently bound wallet identification information and the hardware wallet identification information; and sending the authorization response information to the terminal so that the terminal sends a binding request to the target operating system associated with the currently bound wallet identification information, thereby enabling the target operating system to bind the hardware wallet identification information with the terminal's wallet identification information. This process allows the hardware wallet to be bound to a specific user, facilitating the tracing of the hardware wallet's transaction process and constructing transaction network model data. Simultaneously, it can meet various user transaction needs, improve transaction convenience, and enhance user experience.

[0104] In embodiments of the present invention, such as Figure 3 As shown, the hardware wallet binding method of the third embodiment of the present invention is applied to the target operating institution system, and includes the following steps:

[0105] In this embodiment of the invention, the target operating institution system is the operating institution system of the issuing institution corresponding to the hardware wallet device. The terminal can communicate directly with the target operating institution system, or the terminal can communicate with the target operating institution system across institutions through interconnection.

[0106] Step S301: Receive a binding request sent by the terminal; wherein the binding request includes the current bound wallet identification information of the hardware wallet device.

[0107] In this embodiment of the invention, when the binding state of the hardware wallet device is stored within the hardware wallet device:

[0108] The currently bound wallet identification information includes the currently bound wallet number and unique mapping information, and receives the binding request sent by the terminal's digital currency application. If the binding status of the hardware wallet device is stored in the hardware wallet device, the terminal's digital currency application determines the binding status of the hardware wallet device based on the currently bound wallet number. Only when the binding status of the hardware wallet device is unbound will the terminal's digital currency application receive the binding request.

[0109] When the binding status of the hardware wallet device is stored in the target operator's system:

[0110] The currently bound wallet identification information includes unique mapping information and a binding request sent by the digital currency application on the receiving terminal.

[0111] Step S302: If the hardware wallet device is not bound, bind the hardware wallet identification information with the wallet identification information of the terminal.

[0112] In this embodiment of the invention, when the binding status of the hardware wallet device is stored in the hardware wallet device, the hardware wallet number information of the hardware wallet identification information is bound to the user account information of the wallet identification information of the terminal.

[0113] Generate binding response information based on the binding result.

[0114] When the binding status of the hardware wallet device is stored in the target operator's system:

[0115] The target operating institution system determines the binding status of the hardware wallet device based on the binding status information corresponding to the hardware wallet number information of the hardware wallet identification information in the local system.

[0116] When the hardware wallet device is not bound, the target operator system binds the hardware wallet number information of the hardware wallet identification information with the user account information of the wallet identification information of the terminal, and generates binding response information based on the successful binding result.

[0117] If the hardware wallet device is already bound, the target operating system generates a binding response message based on the binding failure result.

[0118] Step S303: Send the binding response information to the terminal, so that the terminal sends the binding response information to the hardware wallet device, thereby binding the hardware wallet device with the wallet identification information of the terminal.

[0119] In this embodiment of the invention, when the binding state of the hardware wallet device is stored within the hardware wallet device:

[0120] The binding response information is sent to the digital currency application on the terminal, so that the digital currency application on the terminal sends the binding response information to the hardware wallet device. If the binding result is successful, the hardware wallet device stores the adjusted binding wallet number information corresponding to the adjusted binding wallet identification information indicated by the binding response information, and sets the binding status to "bound".

[0121] When the binding status of the hardware wallet device is stored in the target operator's system:

[0122] If the binding result is successful, the target operating institution's system stores the adjusted bound wallet number information of the adjusted bound wallet identification information, and sets the binding status corresponding to the hardware wallet number information of the hardware wallet identification information to "bound".

[0123] In this embodiment of the invention, by receiving a binding request sent by a terminal, wherein the binding request includes the current bound wallet identification information of the hardware wallet device; when the binding status of the hardware wallet device is unbound, binding the hardware wallet identification information with the wallet identification information of the terminal; sending binding response information to the terminal, so that the terminal sends the binding response information to the hardware wallet device, thereby binding the hardware wallet device with the wallet identification information of the terminal, etc., the hardware wallet can be bound to a specific user, which facilitates the tracing of the hardware wallet's transaction process, thereby constructing transaction network model data. At the same time, it can meet various transaction needs of users, improve the convenience of user transactions, and enhance the user experience.

[0124] When hardware wallet devices designed for specific groups are issued, they are typically linked to a public account associated with the issuing institution. By using the hardware wallet binding adjustment method of this invention, the hardware wallet device can be linked to an existing user account in the digital currency application on the terminal. This can meet the transaction needs of the corresponding user of the hardware wallet device, facilitate the tracing of the hardware wallet's transaction process, and thereby build transaction network model data, thus improving user satisfaction.

[0125] Figure 4 This is a schematic diagram of the main modules of the binding wallet adjustment device of the hardware wallet device according to an embodiment of the present invention, such as... Figure 4 As shown, the binding wallet adjustment device 400 of the hardware wallet device of the present invention includes:

[0126] The authorization request module 401 is used to generate an authorization request based on the wallet identity information of the terminal, and send the authorization request to the hardware wallet device so that the hardware wallet device generates authorization response information based on the authorization request; wherein, the wallet identity information includes the wallet identification information of the terminal, and the authorization response information includes the hardware wallet identification information of the hardware wallet device and the currently bound wallet identification information.

[0127] The binding request module 402 is used to receive authorization response information sent by the hardware wallet device, and send a binding request to the target operating system associated with the hardware wallet device according to the currently bound wallet identification information in the authorization response information; wherein, the binding request includes hardware wallet identification information and the wallet identification information of the terminal, so that the target operating system binds the hardware wallet identification information with the wallet identification information of the terminal.

[0128] In this embodiment of the invention, modules such as the authorization request module and the binding request module can bind the hardware wallet to a specific user, making it easier to trace the transaction process of the hardware wallet and thus construct transaction network model data. At the same time, it can meet various transaction needs of users, improve the convenience of user transactions, and enhance the user experience.

[0129] Figure 5 This is a schematic diagram of the main modules of a hardware wallet device according to an embodiment of the present invention, such as... Figure 5 As shown, the hardware wallet device 500 of the present invention includes:

[0130] The receiving module 501 is used to receive an authorization request sent by the terminal; wherein the authorization request indicates the wallet number information of the terminal.

[0131] The generation module 502 is used to generate authorization response information based on the currently bound wallet identification information and hardware wallet identification information.

[0132] The sending module 503 is used to send the authorization response information to the terminal, so that the terminal sends a binding request to the target operating system associated with the currently bound wallet identification information according to the authorization response information, thereby enabling the target operating system to bind the hardware wallet identification information with the wallet identification information of the terminal.

[0133] In this embodiment of the invention, the hardware wallet can be bound to a specific user through modules such as the receiving module, the generating module, and the sending module, which facilitates the tracing of the hardware wallet's transaction process and the construction of transaction network model data. At the same time, it can meet various transaction needs of users, improve the convenience of user transactions, and enhance the user experience.

[0134] Figure 6This is a schematic diagram of the main modules of the target operating organization system according to an embodiment of the present invention, such as... Figure 6 As shown, the target operating organization system 600 of the present invention includes:

[0135] The receiving module 601 is used to receive a binding request sent by the terminal; wherein the binding request includes the current bound wallet identification information of the hardware wallet device.

[0136] The binding module 602 is used to bind the hardware wallet identification information with the wallet identification information of the terminal when the binding status of the hardware wallet device is unbound.

[0137] The sending module 603 is used to send binding response information to the terminal, so that the terminal sends the binding response information to the hardware wallet device, thereby binding the hardware wallet device with the wallet identification information of the terminal.

[0138] In this embodiment of the invention, the hardware wallet can be bound to a specific user through modules such as the receiving module, the binding module, and the sending module, which facilitates the tracing of the hardware wallet's transaction process and the construction of transaction network model data. At the same time, it can meet various transaction needs of users, improve the convenience of user transactions, and enhance the user experience.

[0139] Figure 7 This is a schematic diagram of a digital currency system according to an embodiment of the present invention, such as... Figure 7 As shown, the digital currency system 700 of the present invention includes:

[0140] Terminal 701, hardware wallet 702, and target operating institution system 703.

[0141] The digital currency application 7011 of terminal 701 generates an authorization request based on the wallet identity information of the terminal and sends the authorization request to the hardware wallet 702; wherein, the wallet identity information includes the wallet identification information of the terminal.

[0142] Hardware wallet 702 generates authorization response information based on hardware wallet identification information and currently bound wallet identification information.

[0143] The digital currency application of terminal 701 receives the authorization response information sent by hardware wallet 702, and sends the binding request to the target operating institution system 703 associated with hardware wallet 702 based on the current bound wallet identification information in the authorization response information.

[0144] When the hardware wallet 702 is not bound, the target operating system 703 binds the hardware wallet identification information with the terminal's wallet identification information.

[0145] Figure 8This is a schematic diagram of the interaction process of a digital currency system according to an embodiment of the present invention, such as... Figure 8 As shown, the interaction process of the digital currency system of the present invention includes:

[0146] The terminal's digital currency application generates an authorization request based on the terminal's wallet identity information.

[0147] The terminal's digital currency application uses a built-in encryption algorithm to encrypt the authorization request with a key, determines the corresponding hash value, and sends the encrypted authorization request to the hardware wallet.

[0148] After receiving an authorization request, the hardware wallet determines the corresponding hash value based on the key indicated in the authorization request and the encryption algorithm built into the hardware wallet.

[0149] If the hash value determined by the hardware wallet is the same as the hash value determined by the digital currency application, the hardware wallet obtains the relevant information for the corresponding authorization request.

[0150] The hardware wallet generates an authorization response based on the authorization request and sends it to the digital currency application on the terminal.

[0151] The terminal's digital currency application receives authorization response information sent by the hardware wallet.

[0152] The digital currency application receives a string corresponding to the hardware wallet password information from the hardware wallet password information verification request entered by the user according to the authorization response information.

[0153] The cryptocurrency application sends a string to the target operating institution's system.

[0154] The target operating institution's system verifies the string based on the local hardware wallet password information corresponding to the hardware wallet.

[0155] The target operating institution's system sends the verification result of the hardware wallet password information to the terminal's digital currency application.

[0156] If the verification result of the hardware wallet password information is successful, it also includes:

[0157] If the binding status of the hardware wallet is stored within the hardware wallet:

[0158] The terminal's digital currency application determines the binding status of the hardware wallet based on the currently bound wallet number information.

[0159] When the hardware wallet is not bound, the terminal's digital currency application determines the target operating institution system corresponding to the hardware wallet based on the unique mapping information in the currently bound wallet identification information.

[0160] The terminal's digital currency application sends the binding request to the target operating institution system associated with the hardware wallet.

[0161] The target operating institution's system binds the hardware wallet identification information (hardware wallet number) with the user account information (wallet identification information) of the terminal, and generates binding response information based on the binding result.

[0162] If the hardware wallet's binding status is stored in the target operator's system:

[0163] The terminal's digital currency application uses the unique mapping information in the currently bound wallet identification information to determine the target operating institution system corresponding to the hardware wallet, and sends the binding request to the target operating institution system associated with the hardware wallet.

[0164] The target operating institution's system determines the binding status of the hardware wallet based on the binding status information corresponding to the hardware wallet number information of the local hardware wallet identification information.

[0165] When the hardware wallet is not bound, the target operator's system binds the hardware wallet number information of the hardware wallet identification information with the user account information of the wallet identification information of the terminal, and generates binding response information based on the successful binding result.

[0166] If the hardware wallet is already bound, the target operating institution's system generates a binding response message based on the binding failure result.

[0167] The terminal's digital currency application receives binding response information returned by the target operating institution's system.

[0168] If the binding status of the hardware wallet is stored within the hardware wallet:

[0169] If the binding result is successful, the terminal's digital currency application will send the binding response information to the hardware wallet.

[0170] The hardware wallet stores the adjusted bound wallet number information corresponding to the hardware wallet as indicated by the binding response information, and sets the binding status to "bound".

[0171] If the hardware wallet's binding status is stored in the target operator's system:

[0172] If the binding result is successful, the target operating institution stores the adjusted bound wallet number information of the adjusted bound wallet identification information and sets the binding status corresponding to the hardware wallet identification information to "bound".

[0173] If the binding result is successful, the terminal's digital currency application will output a notification message to the wallet.

[0174] The terminal's digital currency application receives an add request triggered by the user based on the add prompt information.

[0175] In response to the add request, the terminal's digital currency application adds the hardware wallet number information of the hardware wallet identification information to the wallet list corresponding to the user account information of the terminal's wallet identification information, so as to bind the hardware wallet number information of the hardware wallet identification information to the user account information of the terminal's wallet identification information.

[0176] Figure 9 An exemplary system architecture diagram is shown, which illustrates a method for adjusting the bound wallet of a hardware wallet device suitable for application in embodiments of the present invention, such as... Figure 9 As shown, an exemplary system architecture for the hardware wallet device binding wallet adjustment method of this invention includes:

[0177] like Figure 9 As shown, system architecture 900 may include terminals 901, 902, 903, and 904; hardware wallets 905, 906, 907, and 908; network 909; and target operator system 910. Network 909 serves as the medium for providing communication links between terminals 901, 902, and 903 and target operator system 910. Network 909 may include various connection types, such as wired or wireless communication links or fiber optic cables, etc.

[0178] Users can use terminals 901, 902, 903, and 904 to interact with the target operator's system 910 via network 909 to receive or send messages. Various communication client applications can be installed on terminals 901, 902, 903, and 904, such as cryptocurrency trading applications, shopping applications, web browser applications, search applications, instant messaging tools, email clients, and social media platforms.

[0179] Terminals 901, 902, 903, and 904 can be various electronic devices that have software wallets or hardware wallets and support communication between the software wallets and hardware wallets, including but not limited to smartphones, smart bracelets, SIM cards, tablets, laptops, and desktop computers, etc.

[0180] Users can use hardware wallets 905, 906, 907, and 908 to interact with terminals 901, 902, 903, and 904 to receive or send messages, etc. Hardware wallets 905, 906, 907, and 908 communicate with terminals 901, 902, 903, and 904 via NFC and other methods.

[0181] Hardware wallets 905, 906, 907, and 908 can be various electronic devices that have a hardware wallet and support hardware wallet communication, including but not limited to smartphones, smart bracelets, SIM cards, tablets, laptops, and desktop computers, etc.

[0182] The target operating system 910 can be a server providing various services, such as a backend management server supporting cryptocurrency trading websites browsed by users using terminals 901, 902, 903, and 904. The backend management server can analyze and process received data such as binding requests, and feed back the processing results (such as binding response information) to terminals 901, 902, 903, and 904.

[0183] It should be noted that the wallet binding adjustment method of the hardware wallet device provided in the embodiments of the present invention is generally executed by terminals 901, 902, 903, 904, hardware wallets 905, 906, 907, 908 or target operating institution system 910.

[0184] It should be understood that Figure 9 The number of terminals, hardware wallets, networks, and target operator systems shown is merely illustrative. Any number of terminals, hardware wallets, networks, and target operator systems can be included depending on implementation needs.

[0185] Figure 10 This is a schematic diagram of the structure of a computer system suitable for implementing the embodiments of the present invention, such as... Figure 10 As shown, the computer system 1000 of the terminal or server in this embodiment of the invention includes:

[0186] The central processing unit (CPU) 1001 can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 1002 or programs loaded from storage section 1008 into random access memory (RAM) 1003. RAM 1003 also stores various programs and data required for the operation of system 1000. CPU 1001, ROM 1002, and RAM 1003 are interconnected via bus 1004. Input / output (I / O) interface 1005 is also connected to bus 1004.

[0187] The following components are connected to I / O interface 1005: an input section 1006 including a keyboard, mouse, etc.; an output section 1007 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 1008 including a hard disk, etc.; and a communication section 1009 including a network interface card such as a LAN card, modem, etc. The communication section 1009 performs communication processing via a network such as the Internet. A drive 1010 is also connected to I / O interface 1005 as needed. A removable medium 1011, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on drive 1010 as needed so that computer programs read from it can be installed into storage section 1008 as needed.

[0188] In particular, according to the embodiments disclosed in this invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this invention include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 1009, and / or installed from removable medium 1011. When the computer program is executed by central processing unit (CPU) 1001, it performs the functions defined in the system of this invention.

[0189] It should be noted that the computer-readable medium shown in this invention can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this invention, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this invention, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0190] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0191] The modules described in the embodiments of this invention can be implemented in software or hardware. These modules can also be housed in a processor; for example, a processor may include an authorization request module and a binding request module. The names of these modules do not necessarily limit the functionality of the module itself.

[0192] For example, the binding request module can also be described as "a module that sends a binding request to the target operator system associated with the hardware wallet device".

[0193] In another aspect, the present invention also provides a computer-readable medium, which may be included in the device described in the above embodiments; or it may exist independently and not assembled into the device. The computer-readable medium carries one or more programs that, when executed by the device, cause the device to include: generating an authorization request based on the wallet identity information of a terminal; sending the authorization request to a hardware wallet device, causing the hardware wallet device to generate authorization response information based on the authorization request; wherein the wallet identity information includes the wallet identification information of the terminal, and the authorization response information includes the hardware wallet identification information of the hardware wallet device and the currently bound wallet identification information; receiving the authorization response information sent by the hardware wallet device; and sending a binding request to a target operating system associated with the hardware wallet device based on the currently bound wallet identification information in the authorization response information; wherein the binding request includes the hardware wallet identification information and the wallet identification information of the terminal, causing the target operating system to bind the hardware wallet identification information with the wallet identification information of the terminal.

[0194] According to the technical solution of the present invention, a hardware wallet can be bound to a specific user, which facilitates the tracing of the transaction process of the hardware wallet and thus constructs transaction network model data. At the same time, it can meet various transaction needs of users, improve the convenience of user transactions, and enhance user experience.

[0195] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can occur depending on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A method for adjusting the bound wallet of a hardware wallet device, characterized in that, The method is applied to a terminal, and the method includes: An authorization request is generated based on the wallet identity information of the terminal, and the authorization request is sent to the hardware wallet device so that the hardware wallet device generates authorization response information based on the authorization request; wherein, the wallet identity information includes the wallet identification information of the terminal, and the authorization response information includes the hardware wallet identification information of the hardware wallet device and the currently bound wallet identification information; wherein, the hardware wallet is a hardware wallet that is not associated with the user's identity at the time of issuance, but is only associated with the public account of the issuing institution. The system receives authorization response information from the hardware wallet device and, based on the currently bound wallet identification information in the authorization response information, sends a binding request to the target operating system associated with the hardware wallet device. The binding request includes hardware wallet identification information and the terminal's wallet identification information, enabling the target operating system to bind the hardware wallet identification information with the terminal's wallet identification information, thereby transferring the hardware wallet from its original public account to an existing user account within the digital currency application.

2. The method of claim 1, wherein, The currently bound wallet identification information indicates the binding status of the hardware wallet device. Before sending the binding request to the target operating system associated with the currently bound wallet identification information, the method further includes: The binding status of the hardware wallet device is determined based on the currently bound wallet identification information; If the hardware wallet device is not bound, the binding request is sent to the target operating system associated with the hardware wallet device so that the target operating system binds the hardware wallet identification information with the wallet identification information of the terminal.

3. The method of claim 2, wherein, Also includes: Receive binding response information returned by the target operating institution's system; wherein, the binding response information includes the binding result; If the binding result is successful, the binding response information is sent to the hardware wallet device, so that the hardware wallet device stores the adjusted binding wallet identification information corresponding to the hardware wallet device indicated by the binding response information, and sets the binding status to "bound".

4. The method of claim 1, wherein, Also includes: The system receives binding response information returned by the target operating institution system. This binding response information is generated by the target operating institution system after determining the binding status of the hardware wallet device based on local binding status information corresponding to the hardware wallet identification information; wherein: When the hardware wallet device is not bound, the target operating institution system binds the hardware wallet identification information with the wallet identification information of the terminal, and generates the binding response information based on the successful binding result; When the hardware wallet device is in a bound state, the target operating institution system generates the binding response information based on the binding failure result.

5. The method of claim 4, wherein, The binding response information indicates the adjusted binding wallet identification information corresponding to the hardware wallet device, so that the target operating institution system stores the adjusted binding wallet identification information and sets the binding status corresponding to the hardware wallet identification information to "bound".

6. The method of claim 1, wherein, The wallet identity information includes a key, so that the hardware wallet device can generate the authorization response information after verifying the key according to the authorization request.

7. The method of claim 1, wherein, The hardware wallet identification information includes hardware wallet password information, and before sending the binding request to the target operating system associated with the currently bound wallet identification information, it also includes: Receive a string input by the user that corresponds to the password information of the hardware wallet; The string is sent to the target operating institution system, so that the target operating institution system verifies the string based on the hardware wallet password information corresponding to the hardware wallet device on its local machine.

8. The method according to claim 3 or 4, characterized in that, Also includes: If the binding result is successful, a wallet addition prompt message is output so that the user can trigger an addition request based on the addition prompt message; In response to the add request, the hardware wallet identification information is added to the wallet list corresponding to the wallet identification information of the terminal, so that the hardware wallet identification information is bound to the wallet identification information of the terminal. 9.A method for adjusting a bound wallet of a hardware wallet device, characterized by, The method is applied to a hardware wallet device, including: The terminal receives an authorization request; wherein the authorization request indicates the terminal's wallet identification information. Based on the currently bound wallet identification information and hardware wallet identification information, an authorization response information is generated; wherein, the hardware wallet is a hardware wallet that is not associated with the user's identity at the time of issuance, but is only associated with the public account of the issuing institution; The authorization response information is sent to the terminal, so that the terminal sends a binding request to the target operating system associated with the currently bound wallet identification information based on the authorization response information, thereby enabling the target operating system to bind the hardware wallet identification information with the wallet identification information of the terminal; so as to adjust the hardware wallet from the original public account to the existing user account in the digital currency application.

10. The method of claim 9, wherein, The authorization request indicates the terminal's wallet identity information, which includes a key, and before generating the authorization response information, it also includes: The key is verified according to the authorization request.

11. The method according to claim 9 or 10, characterized in that, Also includes: Receive binding response information returned by the terminal; wherein, the binding response information includes the binding result; If the binding result is successful, the adjusted bound wallet identification information corresponding to the hardware wallet device indicated by the binding response information is stored, and the binding status of the hardware wallet device is set to "bound". 12.A method for adjusting a bound wallet of a hardware wallet device, characterized by, The method is applied to the target operating organization system, including: The receiving terminal sends a binding request; wherein the binding request includes the current bound wallet identification information of the hardware wallet device; wherein the hardware wallet is a hardware wallet that is not associated with the user's identity at the time of issuance, but is only associated with the public account of the issuing institution; When the hardware wallet device is not bound, the hardware wallet identification information is bound to the wallet identification information of the terminal; The binding response information is sent to the terminal, so that the terminal sends the binding response information to the hardware wallet device, thereby binding the hardware wallet device with the wallet identification information of the terminal; so as to adjust the hardware wallet from the original public account to the existing user account in the digital currency application.

13. The method of claim 12, wherein, The binding request also includes the hardware wallet identification information of the hardware wallet device; and also includes: The binding status of the hardware wallet device is determined based on the local binding status information corresponding to the hardware wallet identification information. When the hardware wallet device is not bound: The hardware wallet identification information is bound to the terminal's wallet identification information. Generate binding response information based on the successful binding result.

14. The method of claim 13, wherein, If the hardware wallet device is already bound, the following is also included: The binding response information is generated based on the binding failure result.

15. The method of claim 13, wherein, If the binding result is successful, the binding response information indicates the adjusted bound wallet identification information corresponding to the hardware wallet device, and also includes: Store the adjusted wallet identification information and set the binding status corresponding to the hardware wallet identification information to "bound".

16. A bound wallet adjustment apparatus of a hardware wallet apparatus, characterized by, include: An authorization request module is used to generate an authorization request based on the terminal's wallet identity information and send the authorization request to a hardware wallet device, so that the hardware wallet device generates authorization response information based on the authorization request; wherein, the wallet identity information includes the terminal's wallet identification information, and the authorization response information includes the hardware wallet identification information of the hardware wallet device and the currently bound wallet identification information; wherein, the hardware wallet is a hardware wallet that is not associated with the user's identity at the time of issuance, but is only associated with the public account of the issuing institution; The binding request module is used to receive authorization response information sent by the hardware wallet device, and send a binding request to the target operating system associated with the hardware wallet device based on the currently bound wallet identification information in the authorization response information; wherein, the binding request includes hardware wallet identification information and the wallet identification information of the terminal, so that the target operating system binds the hardware wallet identification information with the wallet identification information of the terminal; thereby adjusting the hardware wallet from the original public account to an existing user account in the digital currency application.

17. A hardware wallet device, characterized in that, include: A receiving module is used to receive an authorization request sent by a terminal; wherein the authorization request indicates the wallet number information of the terminal; The generation module is used to generate authorization response information based on the currently bound wallet identification information and the hardware wallet identification information; wherein, the hardware wallet is a hardware wallet that is not associated with the user's identity at the time of issuance, but is only associated with the public account of the issuing institution; The sending module is used to send the authorization response information to the terminal, so that the terminal sends a binding request to the target operating system associated with the currently bound wallet identification information according to the authorization response information, thereby enabling the target operating system to bind the hardware wallet identification information with the wallet identification information of the terminal; so as to adjust the hardware wallet from the original public account to the existing user account in the digital currency application.

18. A target operating agency system, characterized by, include: A receiving module is used to receive a binding request sent by a terminal; wherein the binding request includes the current bound wallet identification information of the hardware wallet device; A binding module is used to bind the hardware wallet identification information to the wallet identification information of the terminal when the binding status of the hardware wallet device is unbound; wherein, the hardware wallet is a hardware wallet that is not associated with the user's identity at the time of issuance, but is only associated with the public account of the issuing institution; The sending module is used to send the binding response information to the terminal, so that the terminal sends the binding response information to the hardware wallet device, thereby binding the hardware wallet device with the wallet identification information of the terminal; so as to adjust the hardware wallet from the original public account to the existing user account in the digital currency application.

19. A digital currency system characterized in that, include: Terminals, hardware wallets, and target operating institution systems; among them, The digital currency application of the terminal generates an authorization request based on the terminal's wallet identity information and sends the authorization request to the hardware wallet; wherein, the wallet identity information includes the terminal's wallet identification information, and the hardware wallet is a hardware wallet that is not associated with the user's identity at the time of issuance, but is only associated with the public account of the issuing institution; The hardware wallet generates authorization response information based on the hardware wallet identification information and the currently bound wallet identification information; The terminal's digital currency application receives the authorization response information sent by the hardware wallet, and sends the binding request to the target operating institution system associated with the hardware wallet based on the currently bound wallet identification information in the authorization response information; When the target operating institution system is not bound to the hardware wallet, it binds the hardware wallet identification information with the wallet identification information of the terminal to adjust the hardware wallet from the original public account to the existing user account in the digital currency application.

20. A hardware wallet-bound electronic device, the device comprising: include: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-15.

21. A computer readable medium having stored thereon a computer program, characterized in that, When the program is executed by the processor, it implements the method as described in any one of claims 1-15.

Images