Migration method, system, device and equipment of hardware wallet and storage medium

Abstract

The application discloses a kind of migration methods, systems, devices and storage medium of hardware wallet, it is related to computer technical field, can improve the security of hardware wallet under abnormal condition.The specific embodiment mode of the application includes: first proxy terminal sends migration request information to wallet management server;Migration request information is used to request the hardware wallet data deployed in first equipment is migrated to second equipment;The wallet management server responds to migration request information, and sends migration confirmation information to first proxy terminal;First proxy terminal responds to migration confirmation information, and sends configuration request information for requesting configuration hardware wallet data to application management server;Application management server responds to configuration request information, obtains hardware wallet data from wallet management server, and sends data configuration instruction to second equipment by first proxy terminal;Second equipment responds to data configuration instruction, and configuration hardware wallet data.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a method, system, apparatus, device, and storage medium for migrating a hardware wallet. Background Technology

[0002] With the development of digital currency technology, hardware wallet products have emerged. Hardware wallets can provide digital currency transaction services based on stored digital currency balances and other data.

[0003] If a hardware wallet is lost, damaged, or abandoned, the data in the hardware wallet may be lost or leaked, resulting in low security. Summary of the Invention

[0004] This application provides a method, system, apparatus, device, and storage medium for migrating hardware wallets, to at least improve the technical problem of low security in hardware wallets under abnormal conditions. The technical solution of this application is as follows:

[0005] According to a first aspect of the embodiments of this application, a method for migrating a hardware wallet is provided, comprising:

[0006] The first agent terminal sends a migration request to the wallet management server; the migration request is used to request the migration of hardware wallet data deployed on the first device to the second device.

[0007] In response to the migration request, the wallet management server sends a migration confirmation message to the first agent terminal.

[0008] In response to the migration confirmation information, the first agent terminal sends a configuration request to the application management server to request the configuration of hardware wallet data.

[0009] In response to the configuration request information, the application management server obtains hardware wallet data from the wallet management server and sends data configuration instructions to the second device through the first agent terminal;

[0010] The second device responds to the data configuration command and configures the hardware wallet data.

[0011] In one possible implementation, the migration request information includes a first association code corresponding to the first device and device information of the second device; before sending migration confirmation information to the first agent terminal, it also includes:

[0012] The wallet management server determines whether to allow the first device to configure hardware wallet data based on the hardware wallet status corresponding to the first association code, the device information of the first device, and the device information of the second device.

[0013] In one possible implementation, before sending the migration confirmation information to the first agent terminal, the process also includes:

[0014] When it is determined that the first device is allowed to configure hardware wallet data, the wallet management server sends migration permission information to the first agent terminal;

[0015] In response to the migration permission information, the first agent terminal obtains identity information from the second device and sends an authentication request carrying the identity information to the wallet management server;

[0016] The wallet management server responds to the authentication request, verifies the identity information, and when the identity information is successfully verified, updates the hardware wallet status to the pending migration status and establishes the correspondence between the second device and the second association code.

[0017] In one possible implementation, before obtaining hardware wallet data from the wallet management server and sending data configuration instructions to the second device via the first agent terminal, the process further includes:

[0018] The application management server sends a data query command to the second device through the first proxy terminal; the data query command is used to determine whether any hardware wallet data has been configured.

[0019] The second device responds to the data query command, determines the data query result, and sends the data query result to the application management server through the first agent terminal.

[0020] In one feasible approach, the hardware wallet migration method also includes:

[0021] When the data query result is that any hardware wallet has been configured, the application management server sends a clearing instruction message to the second device through the first agent terminal.

[0022] In response to the clearing instruction, the second device generates a prompt message to clear any configured hardware wallet data.

[0023] In one possible approach, hardware wallet data is obtained from a wallet management server, including:

[0024] When the data query result is that no hardware wallet data is configured, the application management server sends a data request message carrying the first association code and the device information of the second device to the wallet management server.

[0025] When the hardware wallet corresponding to the first association code is in a state of pending migration, and the device information of the second device corresponds to the second association code, the wallet management server responds to the data request information and sends the hardware wallet data deployed on the first device to the application management server.

[0026] In one possible approach, after configuring the hardware wallet data, the following is also included:

[0027] The first agent terminal sends a status update request to the second device;

[0028] In response to the status update request, the second device determines the verification data used to characterize the integrity of the hardware wallet data, and sends a status update instruction carrying the verification data to the wallet management server through the first agent terminal.

[0029] In response to the status update instruction, the wallet management server verifies the verification data. When the verification data is successfully verified, the first association code is updated to an invalid state, and the second association code is updated to an effective state. The server then sends an update success message to the second device through the first agent terminal.

[0030] In response to the successful update information, the second device generates a message indicating that the hardware wallet data has been successfully configured.

[0031] In one feasible approach, the hardware wallet migration method also includes:

[0032] The first device sends a data clearing request to the application management server through the second agent terminal;

[0033] In response to the data clearing request, the application management server, after determining that the first device has the permission to clear the hardware wallet data, sends a data clearing instruction to the first device through the second proxy terminal.

[0034] The first device responds to the data clearing command and clears the hardware wallet data.

[0035] In one feasible approach, determining that the first device has permission to clear hardware wallet data includes:

[0036] The application management server sends an access permission command to the first device through the second proxy terminal;

[0037] In response to the permission acquisition command, the first device sends permission indication information to the application management server through the second agent terminal; the permission indication information is used to indicate that the first device has the permission to clear hardware wallet data.

[0038] In response to the permission instruction information, the application management server sends permission instruction information to the wallet management server;

[0039] The wallet management server responds to the permission instruction information. When it determines that the permission instruction information is correct, the first association code is invalid, and the second association code is effective, it sends permission confirmation information to the application management server.

[0040] The application management server responds to the permission confirmation information and determines that the first device has the permission to clear the hardware wallet data.

[0041] According to a second aspect of the embodiments of this application, a method for migrating a hardware wallet is provided, applied to a first proxy terminal, comprising:

[0042] Send a migration request to the wallet management server; the migration request is used to request the migration of hardware wallet data deployed on the first device to the second device.

[0043] In response to the migration confirmation information from the wallet management server, a configuration request information is sent to the application management server to request the configuration of hardware wallet data;

[0044] In response to the data configuration command from the application management server, a data configuration command is sent to the second device to enable the second device to configure hardware wallet data.

[0045] In one possible approach, before sending the migration request information to the wallet management server, the following steps are also included:

[0046] Send a data query request to the second device to check whether any hardware wallet data has been configured;

[0047] In response to the data query result of the second device, a first prompt message is generated; when the data query result indicates that any hardware wallet data has been configured, the first prompt message is used to prompt the clearing of any hardware wallet data, or to stop migrating the hardware wallet data deployed on the first device to the second device; when the data query result indicates that no hardware wallet data has been configured, the first prompt message is used to prompt the start of migrating the hardware wallet data deployed on the first device to the second device.

[0048] In one feasible approach, the hardware wallet migration method also includes:

[0049] In response to a user's edit operation on the parent wallet information, a wallet information request is sent to the wallet management server; the wallet information request is used to obtain the hardware wallet information associated with the parent wallet information; the hardware wallet information includes the association code of at least one hardware wallet.

[0050] Receive hardware wallet information from the wallet management server;

[0051] In response to the user's selection operation, the association code of the hardware wallet corresponding to the selection operation in the hardware wallet information is determined as the first association code corresponding to the first device.

[0052] According to a third aspect of the embodiments of this application, a method for migrating a hardware wallet is provided, applied to a wallet management server, comprising:

[0053] In response to the migration request information from the first agent terminal, a migration confirmation information is sent to the first agent terminal; the migration request information is used to request the migration of hardware wallet data deployed on the first device to the second device;

[0054] In response to a data retrieval request from the application management server, hardware wallet data deployed on the first device is sent to the application management server.

[0055] In one feasible approach, the hardware wallet migration method also includes:

[0056] In response to a status update indication carrying verification data from the first agent terminal, the verification data is verified; the verification data is used to characterize the integrity of the hardware wallet data.

[0057] When the verification data is successfully verified, the first association code corresponding to the first device will be updated to an invalid state, and the second association code corresponding to the second device will be updated to an effective state.

[0058] Send an update success message to the first agent terminal.

[0059] In one feasible approach, the hardware wallet migration method also includes:

[0060] In response to the permission indication information from the application management server, when it is determined that the permission indication information is correct, the first association code is invalid, and the second association code is effective, permission confirmation information is sent to the application management server.

[0061] According to a fourth aspect of the embodiments of this application, a method for migrating a hardware wallet is provided, applied to an application management server, comprising:

[0062] In response to the configuration request information from the first agent terminal, a data acquisition request is sent to the wallet management server; the configuration request information is used to request the hardware wallet data deployed on the first device to be configured to the second device;

[0063] Receive hardware wallet data from the wallet management server;

[0064] The first agent terminal sends a data configuration command to the second device to enable the second device to configure hardware wallet data.

[0065] In one feasible approach, the hardware wallet migration method also includes:

[0066] In response to the data clearing request from the second agent terminal, a permission acquisition instruction is sent from the second agent terminal to the first device;

[0067] In response to the permission instruction information sent by the first device through the second proxy terminal, a permission instruction information is sent to the wallet management server; the permission instruction information is used to indicate that the first device has the permission to clear the hardware wallet data;

[0068] In response to the permission confirmation information from the wallet management server, a data clearing command is sent to the first device through the second agent terminal, so that the first device clears the hardware wallet data.

[0069] According to a fifth aspect of the embodiments of this application, a hardware wallet migration system is provided, comprising: a first agent terminal, a wallet management server, an application management server, a second device, and a first device;

[0070] The first agent terminal is configured to send a migration request to the wallet management server; the migration request is used to request the migration of hardware wallet data deployed on the first device to the second device.

[0071] The wallet management server is configured to respond to the migration request information and send migration confirmation information to the first agent terminal.

[0072] The first agent terminal is also configured to respond to the migration confirmation information by sending a configuration request to the application management server to request configuration hardware wallet data.

[0073] The application management server is configured to respond to configuration request information, obtain hardware wallet data from the wallet management server, and send data configuration instructions to the second device through the first agent terminal.

[0074] The second device is configured to execute data configuration instructions to configure hardware wallet data.

[0075] In one possible implementation, the migration request information includes a first association code corresponding to the first device and device information of the second device;

[0076] The wallet management server is also configured to determine whether to allow the first device to configure hardware wallet data based on the hardware wallet status corresponding to the first association code, the device information of the first device, and the device information of the second device.

[0077] In one possible implementation, the wallet management server is also configured to send migration permission information to the first agent terminal when it is determined that the first device is allowed to configure hardware wallet data;

[0078] The first agent terminal is also configured to respond to migration permission information, obtain identity information from the second device, and send an authentication request carrying the identity information to the wallet management server;

[0079] The wallet management server is also configured to respond to authentication requests, verify identity information, and when the identity information is successfully verified, update the hardware wallet status to a pending migration status and establish a correspondence between the second device and the second association code.

[0080] In one possible implementation, the application management server is also configured to execute a data query command sent to the second device via the first proxy terminal; the data query command is used to determine whether any hardware wallet data has been configured.

[0081] The second device is also configured to execute a response to a data query command, determine the data query result, and send the data query result to the application management server through the first agent terminal.

[0082] In one possible implementation, the application management server is also configured to send a clearing instruction to the second device via the first agent terminal when the data query result is data from an arbitrary hardware wallet that has been configured.

[0083] The second device is also configured to respond to the clearing instruction information by generating a prompt message to clear any configured hardware wallet data.

[0084] In one possible implementation, the application management server is also configured to send a data request message carrying a first association code and device information of a second device to the wallet management server when the data query result is that no hardware wallet data is configured.

[0085] The wallet management server is also configured to respond to data request information and send hardware wallet data deployed on the first device to the application management server when the hardware wallet corresponding to the first association code is in a state of pending migration and the device information of the second device corresponds to the second association code.

[0086] In one possible implementation, the first agent terminal is also configured to send a status update request to the second device;

[0087] The second device is also configured to perform a response to a state update request, determine verification data to characterize the integrity of the hardware wallet data, and send a state update indication carrying the verification data to the wallet management server via the first agent terminal.

[0088] The wallet management server is also configured to respond to the status update indication, verify the verification data, and when the verification data is successfully verified, update the first association code to the invalid state and the second association code to the effective state, and send the update success information to the second device through the first agent terminal;

[0089] The second device is also configured to respond to the update success message by generating a notification message indicating that the hardware wallet data has been successfully configured.

[0090] In one possible implementation, the hardware wallet migration system further includes: a first device and a second agent terminal;

[0091] The first device is configured to send a data clearing request to the application management server via the second agent terminal;

[0092] The application management server is also configured to respond to a data clearing request and, if it is determined that the first device has the permission to clear the hardware wallet data, send a data clearing instruction to the first device through a second proxy terminal.

[0093] The first device is also configured to execute a data clearing command to clear hardware wallet data.

[0094] In one possible implementation, the application management server is also configured to execute permission acquisition instructions sent to the first device via a second proxy terminal;

[0095] The first device is also configured to execute a permission acquisition command by sending permission indication information to the application management server through the second agent terminal; the permission indication information is used to indicate that the first device has the permission to clear hardware wallet data;

[0096] The application management server is also configured to respond to permission instruction information by sending permission instruction information to the wallet management server;

[0097] The wallet management server is also configured to respond to permission indication information and send permission confirmation information to the application management server when it is determined that the permission indication information is correct, the first association code is invalid, and the second association code is effective.

[0098] The application management server is also configured to respond to permission confirmation information to determine whether the first device has permission to clear hardware wallet data.

[0099] According to a sixth aspect of the embodiments of this application, a hardware wallet migration device is provided, applied to a first proxy terminal, comprising: a sending unit;

[0100] The sending unit is configured to send migration request information to the wallet management server; the migration request information is used to request the migration of hardware wallet data deployed on the first device to the second device.

[0101] The sending unit is also configured to execute a migration confirmation message in response to the wallet management server and send a configuration request message to the application management server to request configuration of hardware wallet data.

[0102] The sending unit is also configured to execute data configuration instructions in response to the application management server, sending data configuration instructions to the second device to enable the second device to configure hardware wallet data.

[0103] In one possible implementation, the hardware wallet migration device further includes: a generation unit;

[0104] The sending unit is also configured to execute a data query request sent to the second device to inquire whether any hardware wallet data has been configured;

[0105] The generation unit is configured to generate a first prompt message in response to the data query result of the second device. When the data query result indicates that any hardware wallet data has been configured, the first prompt message prompts the user to clear any hardware wallet data or stop migrating the hardware wallet data deployed on the first device to the second device. When the data query result indicates that no hardware wallet data has been configured, the first prompt message prompts the user to start migrating the hardware wallet data deployed on the first device to the second device.

[0106] In one possible implementation, the hardware wallet migration device further includes: a receiving unit and a determining unit;

[0107] The sending unit is also configured to perform a wallet information request in response to a user-executed parent wallet information editing operation by sending a wallet information request to the wallet management server; the wallet information request is used to obtain hardware wallet information associated with the parent wallet information; the hardware wallet information includes at least one hardware wallet association code;

[0108] The receiving unit is configured to receive hardware wallet information from the wallet management server;

[0109] The determining unit is configured to perform a selection operation in response to the user's action, and determine the association code of the hardware wallet corresponding to the selection operation in the hardware wallet information as the first association code corresponding to the first device.

[0110] According to a seventh aspect of the embodiments of this application, a hardware wallet migration apparatus is provided, applied to a wallet management server, comprising: a receiving unit and a sending unit;

[0111] The receiving unit is configured to receive migration request information from the first agent terminal;

[0112] The sending unit is configured to send migration confirmation information to the first agent terminal in response to the migration request information received by the receiving unit; the migration request information is used to request the migration of hardware wallet data deployed on the first device to the second device;

[0113] The receiving unit is also configured to receive data retrieval requests from the application management server;

[0114] The sending unit is also configured to send hardware wallet data deployed on the first device to the application management server in response to a data acquisition request received by the receiving unit from the application management server.

[0115] In one possible implementation, the hardware wallet migration device further includes: a verification unit and an update unit;

[0116] The verification unit is configured to execute a status update indication carrying verification data in response to a first agent terminal, and to verify the verification data; the verification data is used to characterize the integrity of the hardware wallet data.

[0117] The update unit is configured to update the first association code corresponding to the first device to an invalid state and update the second association code corresponding to the second device to an active state when the verification data is successfully verified.

[0118] The sending unit is also configured to send an update success message to the first agent terminal.

[0119] In one possible implementation, the sending unit is also configured to respond to the permission indication information of the application management server, and send permission confirmation information to the application management server when it is determined that the permission indication information is correct, the first association code is in an invalid state, and the second association code is in an effective state.

[0120] According to an eighth aspect of the embodiments of this application, a hardware wallet migration apparatus is provided, applied to an application management server, comprising: a sending unit and a receiving unit;

[0121] The sending unit is configured to execute a configuration request message in response to the first agent terminal and send a data acquisition request to the wallet management server; the configuration request message is used to request the hardware wallet data deployed on the first device to be configured to the second device;

[0122] The receiving unit is configured to receive hardware wallet data from the wallet management server;

[0123] The sending unit is also configured to execute a data configuration instruction to be sent to the second device via the first agent terminal, so that the second device configures hardware wallet data.

[0124] In one possible implementation, the sending unit is further configured to execute a data clearing request in response to the second agent terminal, sending an access permission instruction to the second agent terminal for the first device;

[0125] The sending unit is also configured to send permission indication information to the wallet management server in response to permission indication information sent by the first device through the second proxy terminal; the permission indication information is used to indicate that the first device has the permission to clear hardware wallet data;

[0126] The sending unit is also configured to execute a data clearing command to the first device via the second agent terminal in response to the permission confirmation information of the wallet management server, so that the first device clears the hardware wallet data.

[0127] According to a ninth aspect of the embodiments of this application, an electronic device is provided, the electronic device comprising:

[0128] processor;

[0129] Memory used to store processor-executable instructions;

[0130] The processor is configured to execute instructions to implement a hardware wallet migration method executed by a first agent terminal as described in any of the first to fourth aspects, or a hardware wallet migration method executed by a wallet management server as described in any of the first to fourth aspects, or a hardware wallet migration method executed by an application management server as described in any of the first to fourth aspects.

[0131] According to a tenth aspect of the embodiments of this application, a computer-readable storage medium is provided, on which instructions are stored.

[0132] When the instructions in the computer-readable storage medium are executed by the processor of the first agent terminal, the first agent terminal is able to execute the hardware wallet migration method executed by the first agent terminal as in any of the first to fourth aspects.

[0133] Alternatively, when the instructions in the computer-readable storage medium are executed by the processor of the wallet management server, the wallet management server is enabled to perform a hardware wallet migration method performed by the wallet management server as described in any of the first to fourth aspects.

[0134] Alternatively, when the instructions in the computer-readable storage medium are executed by the processor of the application management server, the application management server is able to execute a hardware wallet migration method executed by the application management server as described in any of the first to fourth aspects.

[0135] According to the eleventh aspect of the embodiments of this application, a computer program product is provided, including a computer program that, when executed by a first proxy terminal, implements any one of the hardware wallet migration methods executed by the first proxy terminal in the first to fourth aspects; or, when executed by a wallet management server, the computer program implements any one of the hardware wallet migration methods executed by the wallet management server in the first to fourth aspects; or, when executed by an application wallet management server, the computer program implements any one of the hardware wallet migration methods executed by the application management server in the first to fourth aspects.

[0136] The first aspect of the technical solution provided by the embodiments of this application brings at least the following beneficial effects: This application provides a method for migrating a hardware wallet. A first agent terminal can send migration request information to a wallet management server to request the migration of hardware wallet data deployed on a first device to a second device. The wallet management server can respond to the migration request information by sending migration confirmation information to the first agent terminal. The first agent terminal can respond to the migration confirmation information by sending configuration request information to an application management server to request the configuration of the hardware wallet data. The application management server can respond to the configuration request information by obtaining the hardware wallet data from the wallet management server and sending a data configuration instruction to the second device through the first agent terminal. The second device can respond to the data configuration instruction by configuring the hardware wallet data.

[0137] Based on the interaction process of the above multiple devices, this application can migrate hardware wallet data deployed on the first device to the second device, and then re-enable the hardware wallet data deployed on the first device on the second device, avoiding the loss of hardware wallet data deployed on the first device. The second device can support business operations such as transaction record querying and single-connection transactions. Therefore, this application can be used to improve the technical problem of low security of hardware wallets under abnormal conditions.

[0138] It should be noted that the technical effects of any of the implementation methods in the second to eleventh aspects can be found in the technical effects of the corresponding implementation methods in the first aspect, and will not be repeated here.

[0139] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0140] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application, and do not constitute an undue limitation of this application.

[0141] Figure 1 This is a schematic diagram illustrating an implementation architecture according to an embodiment of this application;

[0142] Figure 2 This is a flowchart illustrating a hardware wallet migration method according to an embodiment of this application;

[0143] Figure 3 This is a flowchart illustrating another hardware wallet migration method shown in an embodiment of this application;

[0144] Figure 4 This is a flowchart illustrating another hardware wallet migration method shown in an embodiment of this application;

[0145] Figure 5 This is a flowchart illustrating another hardware wallet migration method shown in an embodiment of this application;

[0146] Figure 6 This is a flowchart illustrating another hardware wallet migration method shown in an embodiment of this application;

[0147] Figure 7 This is a flowchart illustrating another hardware wallet migration method shown in an embodiment of this application;

[0148] Figure 8 This is a flowchart illustrating another hardware wallet migration method shown in an embodiment of this application;

[0149] Figure 9 This is a flowchart illustrating another hardware wallet migration method shown in an embodiment of this application;

[0150] Figure 10 This is a flowchart illustrating another hardware wallet migration method shown in an embodiment of this application;

[0151] Figure 11 This is a schematic diagram illustrating a migration process according to an embodiment of this application;

[0152] Figure 12 This is a block diagram of a hardware wallet migration system shown in an embodiment of this application;

[0153] Figure 13 This is a block diagram illustrating a hardware wallet migration device according to an embodiment of this application;

[0154] Figure 14 This is a block diagram of another hardware wallet migration device shown in the embodiments of this application;

[0155] Figure 15 This is a block diagram of another hardware wallet migration device shown in the embodiments of this application;

[0156] Figure 16 This is a block diagram illustrating an electronic device according to an embodiment of this application. Detailed Implementation

[0157] To enable those skilled in the art to better understand the technical solutions of this application, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0158] It should be noted that the terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0159] Before providing a detailed introduction to the hardware wallet migration method provided in this application, let's briefly introduce the application scenarios and implementation environment involved in this application.

[0160] With the development of digital currency technology, hardware wallet products have emerged. Hardware wallets can provide digital currency transaction services based on stored digital currency balances and other data. The activation process of a hardware wallet in a digital currency account model generally includes device storage space authorization, hardware wallet application installation, writing wallet data, and hardware wallet status changes. Information such as the digital currency balance and usage limits of the hardware wallet is generally stored in the backend of the management institution (also known as a wallet management server). Hardware wallets typically employ a two-tier operating system and can provide single-connection transaction capabilities.

[0161] If an abnormal situation occurs during the use of a hardware wallet, such as loss, damage, or abandonment, and the old device (also known as the original device) deployed as the hardware wallet is no longer used, the data in the hardware wallet may be lost or leaked, resulting in low security of the hardware wallet.

[0162] To address the aforementioned issues, this application provides a method for migrating hardware wallets.

[0163] The first agent terminal can send a migration request to the wallet management server to request the migration of hardware wallet data deployed on the first device to the second device. In response to the migration request, the wallet management server can send a migration confirmation to the first agent terminal. In response to the migration confirmation, the first agent terminal can send a configuration request to the application management server to request the configuration of the hardware wallet data. In response to the configuration request, the application management server can retrieve the hardware wallet data from the wallet management server and send data configuration instructions to the second device through the first agent terminal. The second device can then configure the hardware wallet data in response to the data configuration instructions.

[0164] Based on the interaction process of the above multiple devices, this application can migrate hardware wallet data deployed on the first device to the second device, and then re-enable the hardware wallet data deployed on the first device on the second device, avoiding the loss of hardware wallet data deployed on the first device. The second device can support business operations such as transaction record querying and single-connection transactions. Therefore, this application can be used to improve the technical problem of low security of hardware wallets under abnormal conditions.

[0165] Figure 1 This is an implementation architecture diagram of this application. (For example...) Figure 1 As shown in the illustration, the hardware wallet migration system 100 provided in this application embodiment may include a second device 101, a first proxy terminal 102, a wallet management server 103, an application management server 104, a first device 105, and a second proxy terminal 106. The first proxy terminal 102 can communicate with the second device 101, the wallet management server 103, and the application management server 104 respectively. The second proxy terminal 106 can communicate with the second device 105, the wallet management server 103, and the application management server 104 respectively. The wallet management server 103 can communicate with the application management server 104.

[0166] In one feasible way Figure 1 The second device 101 and the first device 105 can be configured with a hardware wallet application and hardware wallet data. In this case, Figure 1 The second device 101 and the first device 105 can also be called hardware wallets, which can store digital currency strings.

[0167] In one feasible way Figure 1 The second device 101 and the first device 105 can also be configured with a short-range communication module to enable secure payment interaction within a trusted and controllable communication distance.

[0168] In one possible approach, the short-range communication module can be a communication module supporting Bluetooth communication, a communication module supporting Wi-Fi wireless network communication technology, a communication module supporting Near Field Communication (NFC), a communication module supporting Ultra Wide Band (UWB) communication, or a communication module supporting wired communication. This application does not limit this approach.

[0169] Optionally, the physical form of the second device 101 and the first device 105 can be a mobile terminal, a card, or a wearable device, such as a visual card wallet, a watch, or a bracelet. Figure 1 This is an example of one device configuration for the second device 101 and the first device 105. The embodiments in this application are not limited to this.

[0170] Optionally, the first agent terminal 102 and the second agent terminal 106 can be other virtual devices with data processing capabilities, or other electronic devices with data processing capabilities. The electronic device can be a terminal, a server, or other types of electronic devices.

[0171] In one possible approach, the first agent terminal 102 and the second agent terminal 106 can be two independently configured devices, or they can be functional modules integrated into the same device.

[0172] For ease of understanding, this application uses the first agent terminal 102 and the second agent terminal 106 as two independently configured devices as examples for illustration.

[0173] Optionally, when the first proxy terminal 102 is a virtual device, it can be a proxy application configured on the second device 101. This proxy application can assist the second device 101 in interacting with the wallet management server 103 and the application management server 104 to obtain hardware wallet data. This proxy application can be directly configured by the user in the second device 101, or it can be configured in a card writing device connected to the second device 101.

[0174] Similarly, when the second proxy terminal 106 is a virtual device, it can also be a proxy application configured on the first device 105. This proxy application can assist the first device 105 in interacting with the wallet management server 103 and the application management server 104 to complete the clearing of hardware wallet data. This proxy application can be directly configured by the user on the first device 105, or it can be configured on a card writing device connected to the first device 105.

[0175] Optional, when Figure 1 When the first agent terminal 102 and the second agent terminal 106 are electronic devices, the second device 101 and the first agent terminal 102 can be functional modules integrated into the same device, or they can be two independently set devices. Figure 1 The first device 105 and the second agent terminal 106 can be functional modules integrated into the same device, or they can be two independently configured devices. This disclosure does not impose any limitations on this.

[0176] It is easy to understand that when the second device 101 and the first agent terminal 102 are functional modules integrated within the same device, the communication method between the second device 101 and the first agent terminal 102 is the communication between modules within the device. In this case, the communication process between the two is the same as that between the second device 101 and the first agent terminal 102 when they are set up independently.

[0177] When the first device 105 and the second agent terminal 106 are functional modules integrated within the same device, the communication method between the first device 105 and the second agent terminal 106 is the communication between modules within the device. In this case, the communication process between the two is the same as the communication process between the first device 105 and the second agent terminal 106 when they are set up independently.

[0178] For ease of understanding, this disclosure is mainly illustrated by the example of the second device 101 and the first agent terminal 102 being set up independently of each other, and the first device 105 and the second agent terminal 106 being set up independently of each other.

[0179] When the second device 101, the first device 105, the second device 101, and the first agent terminal 102 are mobile terminals, the mobile terminal can be a mobile phone, tablet computer, desktop computer, laptop computer, handheld computer, notebook computer, augmented reality (AR) device, virtual reality (VR) device, or other device that can install and use applications. Furthermore, the mobile terminal can also interact with the user through one or more methods such as a keyboard, touchpad, touchscreen, remote control, voice interaction, or handwriting device. This disclosure does not impose any special limitations on the specific form of the mobile terminal.

[0180] In one feasible way Figure 1 The wallet management server 103 in the system can belong to a hardware wallet management institution and is used to store information such as the digital currency balance, usage limit, association code, and payment key of the hardware wallet. The hardware wallet management institution can be a commercial bank responsible for providing digital currency exchange and other services to the public.

[0181] In one feasible way Figure 1 The application management server 104 may belong to the trusted service management system of the regulatory agency, and is used to store various applications from application providers and send various applications to various terminals (such as new device 101 and original device 102).

[0182] Optionally, the second device 101, the first agent terminal 102, the wallet management server 103, and the application management server 104 can be servers. The server can be a single server, or it can be a server cluster consisting of multiple servers. In some embodiments, the server cluster can also be a distributed cluster. This disclosure does not limit the specific implementation of the server.

[0183] For ease of understanding, the following section, in conjunction with the accompanying drawings, provides a detailed description of the hardware wallet migration method provided in this application.

[0184] Figure 2 This is a flowchart illustrating a hardware wallet migration method according to an exemplary embodiment, the hardware wallet migration method being applied to... Figure 1 The hardware wallet migration system 100 in the middle. For example... Figure 2 As shown, the migration method for this hardware wallet includes: S201-S205.

[0185] S201, the first agent terminal sends a migration request to the wallet management server. The migration request is used to request the migration of hardware wallet data deployed on the first device to the second device.

[0186] In one possible approach, a user's cryptocurrency can typically be stored in a master wallet that the user has registered. To facilitate cryptocurrency transactions, users can also apply for one or more hardware wallets from a cryptocurrency operator (also known as a hardware wallet management organization) and transfer a portion of their cryptocurrency from their master wallet to the hardware wallet.

[0187] A hardware wallet can be an account-based hardware wallet used to store digital currencies in the form of tokens, enabling users to conduct digital currency transactions. A hardware wallet can possess a unique identification code, which allows it to interact with a wallet management server belonging to the digital currency operator to synchronize wallet data. Therefore, the hardware wallet and the wallet management server can store the same wallet data. Wallet data may include digital currency balances in token form, payment limit information, payment history information, and deposit history information, etc.

[0188] In one possible approach, after deploying the hardware wallet data of a hardware wallet on a device, that device can be considered as that hardware wallet. If the hardware wallet data deployed on that device is migrated to another device, that other device can also be considered as that hardware wallet. This process can be called the hardware wallet data migration process, or simply the hardware wallet migration process.

[0189] Optionally, the association code of the hardware wallet can be a globally unique identifier (GUID), a universally unique identifier (UUID), or other forms of unique identification information.

[0190] In one possible approach, if a user loses, decides to abandon, or damages a hardware wallet during its use, that hardware wallet can be considered the primary device.

[0191] To prevent data loss or leakage from the original device, consider migrating the hardware wallet data deployed on the first device to the second device. Then, disable the hardware wallet data on the first device and re-enable it on the second device. After the data migration is complete, users can use the second device to query cryptocurrency transaction records and conduct one-to-one cryptocurrency transactions.

[0192] In one possible approach, in order to migrate hardware wallet data to a second device in the event of loss or damage to the first device, the second device could be instructed to retrieve the hardware wallet data from the wallet management server.

[0193] In one possible approach, the second device can obtain hardware wallet data from the wallet management server via a first proxy terminal.

[0194] In one possible approach, the first agent terminal can be configured with an input module such as a keyboard or touchscreen. Users can also use the input module on the first agent terminal to edit the parent wallet information, inputting this information into the first agent terminal. Based on this, the first agent terminal can obtain information about one or more hardware wallets associated with the user-edited parent wallet information from the wallet management server. For example, the hardware wallet information could include the hardware wallet's name and association code.

[0195] Furthermore, users can perform selection operations (such as clicking the name of the hardware wallet) through the input module configured on the first agent terminal. In response to this selection operation, the first agent terminal can identify the hardware wallet corresponding to the selection operation as the first device. Users can also perform data migration operations (such as clicking the migration button) through the input module configured on the first agent terminal.

[0196] In response to this data migration operation, the first agent terminal can send a migration request to the wallet management server. Correspondingly, the wallet management server can receive the migration request from the first agent terminal.

[0197] S202. In response to the migration request information, the wallet management server sends migration confirmation information to the first agent terminal.

[0198] In one possible approach, after receiving the migration request from the first agent terminal, the wallet management server can set the hardware wallet data deployed on the first device to a frozen or pending migration state, indicating that the hardware wallet is in a non-transferable state and avoiding migration failures caused by sending payment or recharge transactions during the migration process. Furthermore, the wallet management server can send a migration confirmation message to the first agent terminal to indicate that data migration can begin.

[0199] S203. In response to the migration confirmation information, the first agent terminal sends a configuration request to the application management server to request the configuration of hardware wallet data.

[0200] In one possible approach, to enhance wallet data security, the application management server, which belongs to a trusted service management system under a regulatory agency, could obtain the hardware wallet data from the wallet management server. In this case, the first agent terminal could send a configuration request to the application management server to request the hardware wallet data.

[0201] S204. In response to the configuration request information, the application management server obtains hardware wallet data from the wallet management server and sends data configuration instructions to the second device through the first agent terminal.

[0202] In one possible approach, the application management server can receive configuration request information from the first agent terminal and, in response to the configuration request information, obtain hardware wallet data from the wallet management server.

[0203] Specifically, the configuration request information may include a first association code corresponding to the first device. The application management server can parse the configuration request information to obtain the first association code and send a data retrieval request carrying the first association code to the wallet management server to retrieve the hardware wallet data deployed on the first device from the wallet management server.

[0204] In one possible approach, the application management server can send data configuration instructions to the second device through the first agent terminal after obtaining hardware wallet data from the wallet management server.

[0205] The application configuration instructions may include the hardware wallet application, hardware wallet data, and a second association code. The application configuration instructions may also include data such as the key corresponding to the second association code. The second association code may be an association code corresponding to a second device.

[0206] In one possible approach, after receiving hardware wallet data and a second association code from the wallet management server, the application management server can generate application configuration instructions and send them to the first agent terminal. The first agent terminal can then forward the application configuration instructions to the second device, enabling the second device to receive the application configuration instructions from the application management server.

[0207] In one possible approach, there can be multiple application configuration instructions. Each application configuration instruction may include a portion of data from the hardware wallet application, hardware wallet data, and a second association code. The application management server can send multiple application configuration instructions to the second device in a specific order to complete the data configuration.

[0208] S205, the second device responds to the data configuration command and configures the hardware wallet data.

[0209] In one possible approach, the second device can respond to a data configuration instruction by executing an application configuration instruction to configure the hardware wallet application and configure the wallet data and the second association code in the hardware wallet application, thereby configuring the hardware wallet data.

[0210] Based on this, the first agent terminal can send a migration request to the wallet management server to request the migration of hardware wallet data deployed on the first device to the second device. In response to the migration request, the wallet management server can send a migration confirmation to the first agent terminal. In response to the migration confirmation, the first agent terminal can send a configuration request to the application management server to request the configuration of the hardware wallet data. In response to the configuration request, the application management server can obtain the hardware wallet data from the wallet management server and send a data configuration command to the second device through the first agent terminal. The second device can then configure the hardware wallet data in response to the data configuration command.

[0211] Based on the interaction process of the above multiple devices, this application can migrate hardware wallet data deployed on the first device to the second device, and then re-enable the hardware wallet data deployed on the first device on the second device, avoiding the loss of hardware wallet data deployed on the first device. The second device can support business operations such as transaction record querying and single-connection transactions. Therefore, this application can be used to improve the technical problem of low security of hardware wallets under abnormal conditions.

[0212] In one embodiment, combined with Figure 2 ,like Figure 3 As shown, before the wallet management server sends migration confirmation information to the first agent terminal, the hardware wallet migration method provided in this application embodiment further includes: S301.

[0213] S301. The wallet management server determines whether to allow the first device to configure hardware wallet data based on the hardware wallet status corresponding to the first association code, the device information of the first device, and the device information of the second device.

[0214] In one possible approach, cryptocurrency operators can impose restrictions on devices configured to run hardware wallet applications, such as transmission protocol versions, communication functions, device types, and memory space, to improve the security and efficiency of cryptocurrency transactions.

[0215] Furthermore, hardware wallet applications can also have multiple versions to support the configuration requirements of different types of devices. In this case, before deploying hardware wallet data to a second device, it can be determined whether the second device meets various restrictions and whether it supports configuring some of the hardware wallet data generated by the first device.

[0216] Based on this, the migration request information may include a first association code corresponding to the first device and device information of the second device. The device information of the second device may include information such as the transmission protocol version, communication function, device type, and memory space.

[0217] In one possible approach, after receiving the migration request information, the wallet management server can parse the migration request information to obtain the first association code and the device information of the second device.

[0218] Furthermore, the wallet management server can also be used to store device information of the first device deployed with the first association code. The wallet management server can determine whether the device information of the second device meets the restrictions preset by the digital currency operator, and can compare the device information of the second device with the device information of the first device to determine whether the second device supports configuring some hardware wallet data generated by the first device, obtain the device verification result, and thus determine whether the second device is allowed to configure hardware wallet data.

[0219] Furthermore, if it is determined that the second device is allowed to configure hardware wallet data, the wallet management server can generate a second association code to further establish the correspondence between the hardware wallet data and the second association code. The second association code and the first association code are different association codes.

[0220] The second association code is the association code assigned to the second device by the wallet management server when the hardware wallet data is deployed on the second device; it is also the second device's association code. Once the second association code is updated to an active state, it can be used for interaction between the second device and the wallet management server.

[0221] In one possible approach, the wallet management server, when generating the second association code, can also generate a key corresponding to the second association code. This key can be a encrypted key, i.e., a key that the second device cannot read, to avoid the risk of data leakage that could easily occur if the key is exposed in plaintext to the second device. The key corresponding to the second association code is different from the key corresponding to the first association code.

[0222] In one possible approach, if the wallet management server determines that the second device is not allowed to configure hardware wallet data, it can send a migration rejection message to the first agent terminal, so that the first agent terminal can generate a prompt message to indicate that the device does not meet the requirements, so as to remind the user to replace it with another device.

[0223] In one embodiment, combined with Figure 3 ,like Figure 4 As shown, before the wallet management server sends migration confirmation information to the first agent terminal, the hardware wallet migration method provided in this application embodiment further includes: S401-S403.

[0224] S401. When it is determined that the first device is allowed to configure hardware wallet data, the wallet management server sends migration permission information to the first agent terminal.

[0225] Among them, migration permission information can be used to characterize whether a second device is allowed to configure hardware wallet data.

[0226] In one possible approach, once it is determined that the first device is permitted to configure hardware wallet data, the wallet management server can send migration permission information to the first agent terminal. Accordingly, the first agent terminal can receive the migration permission information from the wallet management server. Subsequently, the first agent terminal can continue to guide the user through the hardware wallet data migration process.

[0227] In one possible approach, the first agent terminal may, in response to migration permission information, obtain identity information from the second device and send an authentication request carrying the identity information to the wallet management server.

[0228] S402. In response to the migration permission information, the first agent terminal obtains identity information from the second device and sends an authentication request carrying the identity information to the wallet management server.

[0229] In one possible approach, to enhance the security of cryptocurrency transactions, further verification of the user's identity is considered. In this case, when the second device is allowed to configure hardware wallet data, the first agent terminal can send a first prompt message to the second device. Furthermore, the second device can also be equipped with a display module such as an LCD screen to display the first prompt, prompting the user to begin identity verification.

[0230] Optionally, the first prompt message can be used to prompt the user to enter a payment password or a reserved verification password, or to prompt the user to start facial recognition verification, or to prompt the user to enter their resident ID card information for verification, etc.

[0231] In one possible approach, the second device may send identity information to the first agent terminal in response to an identity information editing operation performed by the user.

[0232] Specifically, the user can view the first prompt information through the display module configured on the second device, and perform an identity information editing operation through the input module configured on the second device. In response to the user's identity information editing operation, the second device can generate identity information corresponding to the identity information editing operation and send the identity information to the first agent terminal.

[0233] Correspondingly, the first agent terminal can receive identity information from the second device and send an authentication request carrying the identity information to the wallet management server.

[0234] S403. The wallet management server responds to the authentication request, verifies the identity information, and when the identity information is successfully verified, updates the hardware wallet status to the pending migration status and establishes the correspondence between the second device and the second association code.

[0235] In one possible approach, the wallet management server may also store user-pre-stored verification information. The wallet management server can also be used to verify identity information based on this verification information, update the target hardware wallet's status to a pending migration state when verification is successful, establish a second association code and a mapping between the second device, and send a verification success message to the second device.

[0236] Optionally, the verification information can be a payment password or a pre-reserved verification password, facial data, or resident ID card information.

[0237] In one possible approach, the wallet management server can receive an authentication request from the first agent terminal, parse the authentication request to obtain the identity information, and read the stored verification information to further compare the identity information and the verification information.

[0238] If the identity information and verification information do not match, the wallet management server can determine that the identity verification has failed. In this case, the wallet management server can send a verification failure message to the first agent terminal. Accordingly, the first agent terminal can receive the verification failure message from the wallet management server and prompt the user to restart the identity verification or stop data configuration.

[0239] If the identity information and verification information match, the wallet management server can determine that the identity verification was successful. In this case, the wallet management server can send a verification success message to the first agent terminal. Correspondingly, the first agent terminal can receive the verification success message from the wallet management server and continue to guide the user through the hardware wallet data configuration process.

[0240] In one possible approach, when a successful verification message is received from the wallet management server, the first agent terminal can generate a second prompt message and display the second prompt message through a configured display module to indicate that hardware wallet data is being configured.

[0241] In one possible approach, the wallet management server can update the hardware wallet status to a "pending migration" state. Since the hardware wallet supports cryptocurrency transactions, deposits, and queries when in a normal state, updating it to "pending migration" will disable these operations, ensuring the hardware wallet data remains unchanged and improving the stability of the data configuration process.

[0242] If the hardware wallet is in a pending migration state, the wallet management server can return a failure response when it receives a business operation request related to the hardware wallet. This failure response can be used to notify the user to stop the ongoing data migration before initiating a business operation request through the first device, or to complete the ongoing data migration before initiating a business operation request through the second device.

[0243] Furthermore, the wallet management server can also establish a second association code and a correspondence between the second device and the second device to support the configuration of hardware wallet data on the second device and restrict the configuration of hardware wallet data on devices other than the second device, thereby improving the security of wallet data.

[0244] In one embodiment, combined with Figure 2 ,like Figure 5 As shown, before the application management server obtains hardware wallet data from the wallet management server and sends data configuration instructions to the second device through the first agent terminal, the hardware wallet migration method provided in this application embodiment further includes: S501-S502.

[0245] S501, the application management server sends a data query command to the second device through the first agent terminal.

[0246] The data query command is used to determine whether any hardware wallet data has been configured.

[0247] In one possible approach, if the second device contains arbitrary hardware wallet data, configuring the hardware wallet data deployed on the first device on the second device could cause data overwrite issues, leading to the loss of that arbitrary hardware wallet data. To avoid this data overwrite problem, it's advisable to pre-determine whether the second device contains any arbitrary hardware wallet data before configuring it. If the second device does contain arbitrary hardware wallet data, the user can be prompted to transfer that data or replace the second device with another device.

[0248] Based on this, after receiving the configuration request information from the first proxy terminal, the application management server can send a data query command to the second device through the first proxy terminal. Correspondingly, the second device can receive the data query command sent by the application management server through the first proxy terminal.

[0249] In one possible approach, the data query command can be used to identify high-security wallet data such as encrypted keys to determine whether any hardware wallet data is configured in the second device.

[0250] S502, the second device responds to the data query command, determines the data query result, and sends the data query result to the application management server through the first agent terminal.

[0251] In one possible approach, after receiving a data query instruction from the application management server, the second device can execute the instruction and obtain the query result. The query result can be used to indicate whether the second device stores any hardware wallet data or not.

[0252] In one possible approach, after obtaining the data query results, the second device can send the data query results to the application management server through the first proxy terminal. Correspondingly, the application management server can receive the data query results sent by the second device through the first proxy terminal.

[0253] In one embodiment, combined with Figure 5 ,like Figure 6 As shown, before the application management server obtains hardware wallet data from the wallet management server and sends data configuration instructions to the second device through the first agent terminal, the hardware wallet migration method provided in this application embodiment further includes: S601-S602.

[0254] S601. When the data query result is that any hardware wallet has been configured, the application management server sends a clearing instruction to the second device through the first agent terminal.

[0255] The clearing instruction information can be used to instruct the generation of information that prompts the clearing of data from any hardware wallet.

[0256] When the data query results are used to characterize the data of any configured hardware wallet, the application management server can send a clearing instruction to the second device through the first agent terminal.

[0257] S602, In response to the clearing instruction information, the second device generates a prompt message to prompt the clearing of any configured hardware wallet data.

[0258] In one possible approach, the second device can receive a clearing instruction sent by the application management server through the first proxy terminal, and generate information prompting the user to clear any hardware wallet data. The second device can also display this information via a configured display module, allowing the user to understand that any hardware wallet data needs to be cleared.

[0259] In one embodiment, combined with Figure 5 ,like Figure 7 As shown, when the application management server obtains hardware wallet data from the wallet management server, this application embodiment provides an optional implementation method, including: S701-S702.

[0260] S701. When the data query result is that no hardware wallet data is configured, the application management server sends a data request message carrying the first association code and the device information of the second device to the wallet management server.

[0261] When the data query result indicates that the second device is not configured with any hardware wallet data, the application management server can send a data request message to the wallet management server. This data request message may carry a first association code and device information for the second device.

[0262] Correspondingly, the wallet management server can receive data request information from the application management server and parse the data request information to obtain the first association code and the device information of the second device.

[0263] S702. When the hardware wallet corresponding to the first association code is in a state of pending migration and the device information of the second device corresponds to the second association code, the wallet management server responds to the data request information and sends the hardware wallet data deployed on the first device to the application management server.

[0264] In one possible approach, the wallet management server can determine whether the hardware wallet corresponding to the first association code is in a state awaiting migration, and whether the device information of the second device included in the data request information is consistent with the device information corresponding to the second association code.

[0265] If the hardware wallet corresponding to the first association code is not in a state of pending migration, or if the device information of the second device included in the data request information is inconsistent with the device information corresponding to the second association code, the wallet management server can determine that the hardware wallet data is not allowed to be sent to the application management server in order to be configured for other devices.

[0266] If the hardware wallet corresponding to the first association code is in a pending migration state, and the device information of the second device included in the data request information is consistent with the device information corresponding to the second association code, then the wallet management server can determine that the hardware wallet data is allowed to be sent to the application management server for configuration on the second device. In this case, the wallet management server can send the hardware wallet data deployed on the first device, the second association code, the key corresponding to the second association code, and other data to the application management server, and update the hardware wallet status to a migration state.

[0267] In one embodiment, combined with Figure 2 ,like Figure 8 As shown, after the second device configures the hardware wallet data, the hardware wallet migration method provided in this application embodiment further includes: S801-S804.

[0268] S801, the first agent terminal sends a status update request to the second device.

[0269] In one possible approach, after the first agent terminal forwards the data configuration instructions from the application management server to the second device, it can send a status update request to the second device to confirm whether the second device has completed the data configuration. Correspondingly, the second device can receive the status update request from the first agent terminal.

[0270] S802, the second device responds to the status update request, determines the verification data used to characterize the integrity of the hardware wallet data, and sends a status update instruction carrying the verification data to the wallet management server through the first agent terminal.

[0271] The status update indication may include a second association code, a first association code, and verification data used to characterize the integrity of the hardware wallet data.

[0272] In one possible approach, the data configuration instructions may include an application with verification capabilities. This verification function can generate verification data based on algorithms such as the simplest checksum, parity check, or hash check. Therefore, when the second device configures the hardware wallet application and configures the wallet data and the second associated code within it, the application with verification capabilities can generate verification data to characterize the integrity of the hardware wallet data, thereby determining whether the hardware wallet data is configured correctly.

[0273] In one possible approach, after receiving a status update request from the first agent terminal, the second device, upon generating verification data to characterize the integrity of the hardware wallet data, can send a status update instruction carrying the verification data to the wallet management server through the first agent terminal to confirm the completion of data configuration.

[0274] S803, the wallet management server responds to the status update instruction, verifies the verification data, and when the verification data is successfully verified, updates the first association code to the invalid state and the second association code to the effective state, and sends the update success information to the second device through the first agent terminal.

[0275] In one possible approach, considering that hardware wallets typically interact with the wallet management server based on an association code, the first association code (i.e., the association code of the first device) can be set to an invalid state, thereby invalidating the data in the first device. The wallet management server can then update the second association code to an active state, thereby making the data in the second device active.

[0276] In one possible approach, the wallet management server can receive a status update indication sent by the second device through the first agent terminal, and parse the status update indication to obtain a second association code, a first association code, and verification data used to characterize the integrity of the hardware wallet data.

[0277] Furthermore, the wallet management server can verify the verification data. If the verification data passes, it indicates that the second device has correctly configured the hardware wallet data. In this case, the wallet management server can update the second association code to an active state, update the first association code to an invalid state, update the target hardware wallet's status to a normal state, and send an update success message to the second device through the first agent terminal, so that the second device can indicate that it can start business operations.

[0278] Based on this, this application can disable the first device by updating the first association code used for deployment in the first device to an invalid state, thereby setting the hardware wallet data corresponding to the first association code deployed in the first device to an invalid state, and thus avoiding the security problem caused by data loss or leakage in the first device. Therefore, this application can be used to improve the technical problem of low security of hardware wallets under abnormal conditions.

[0279] If the verification data fails, it indicates that the second device has not correctly configured the hardware wallet data. In this case, the wallet management server can send a configuration failure message to the second device through the first proxy terminal. Correspondingly, the second device can receive the configuration failure message from the wallet management server. Subsequently, the data migration process can be restarted to reconfigure the data.

[0280] S804. In response to the successful update information, the second device generates a prompt message to indicate that the hardware wallet data has been successfully configured.

[0281] In one possible approach, after the second device receives the update success information from the wallet management server through the first agent terminal, it can generate a prompt message indicating successful configuration of the hardware wallet data. This prompt message is then displayed through a configured display module, allowing the user to understand that the second device has been configured with hardware wallet data and can support various business operations.

[0282] In one embodiment, such as Figure 9 As shown, the hardware wallet migration method provided in this application embodiment also includes: S901-S903.

[0283] S901, The first device sends a data clearing request to the application management server through the second agent terminal.

[0284] In one possible scenario, due to the high level of security of the stored wallet data, the first device may not have the permission to perform data processing such as reading or editing.

[0285] In one possible approach, after configuring the hardware wallet data on the second device, the user can perform a data clearing operation (e.g., clicking the clear button) through the input module configured on the first device to delete the relevant data on the first device, thereby preventing data loss and leakage. In response to the user's data clearing operation on the hardware wallet data, the first device can send a data clearing request to the application management server through the second agent terminal.

[0286] Correspondingly, the application management server can receive a data clearing request sent by the first device through the second proxy terminal.

[0287] S902. In response to the data clearing request, the application management server, after determining that the first device has the authority to clear the hardware wallet data, sends a data clearing instruction to the first device through the second agent terminal.

[0288] In one possible approach, after receiving a data clearing request from the first device via a second proxy terminal, the application management server can respond to the request and determine whether the first device has the permission to clear the hardware wallet data. Specifically, the application management server can send a permission acquisition command to the first device via the second proxy terminal, causing the first device to execute the permission acquisition command. Based on the execution result of the permission acquisition command, the server can then determine whether the first device has the permission to clear the hardware wallet data.

[0289] In one possible approach, the application management server can send a data clearing command to the first device through a second proxy terminal, provided that the first device has the permission to clear the hardware wallet data, thereby indicating that the first device is permitted to clear the hardware wallet data.

[0290] S903, the first device responds to the data clearing command and clears the hardware wallet data.

[0291] In one possible approach, the first device can execute a data clearing command to clear the hardware wallet data, thereby preventing data loss and leakage, providing security for the wallet data, and freeing up device space to prevent impact on subsequent use.

[0292] In one embodiment, such as Figure 10 As shown, when the application management server determines that the first device has the permission to clear hardware wallet data, this application embodiment provides an optional implementation method, including: S1001-S1005.

[0293] S1001, The application management server sends an access permission command to the first device through the second agent terminal.

[0294] In one possible approach, the application management server can generate permission acquisition instructions. When these instructions are executed, they can retrieve data related to the hardware wallet (such as keys).

[0295] In one possible approach, after the application management server generates a permission acquisition instruction, it can send the generated instruction to the first device via a second proxy terminal. Correspondingly, the first device can receive the permission acquisition instruction sent by the application management server through the second proxy terminal.

[0296] S1002. In response to the permission acquisition command, the first device sends permission instruction information to the application management server through the second agent terminal.

[0297] The permission indication information can be used to indicate that the first device has the permission to clear hardware wallet data. The permission indication information may include the target hardware wallet's first association code, payment key, and information authentication code, among other things.

[0298] In one possible approach, the first device can execute a permission acquisition command to obtain permission indication information. Based on this, the first device can send the obtained permission indication information to the application management server through a second proxy terminal. Correspondingly, the application management server can receive the permission indication information sent by the first device through the second proxy terminal.

[0299] S1003. In response to the permission instruction information, the application management server sends permission instruction information to the wallet management server.

[0300] In one possible approach, the application management server may respond to the permission instruction information by sending permission instruction information to the wallet management server, so that the wallet management server can determine whether the permission instruction information is correct.

[0301] S1004. In response to the permission indication information, when the wallet management server determines that the permission indication information is correct, the first association code is in an invalid state, and the second association code is in an effective state, it sends permission confirmation information to the application management server.

[0302] In one possible approach, the wallet management server can receive permission indication information from the application management server and, in response to the permission indication information, determine whether the permission indication information is correct (e.g., whether the first association code and the payment key match), whether the first association code is invalid, and whether the second association code corresponding to the hardware wallet data is valid.

[0303] In one possible approach, if the wallet management server determines that the permission indication information is incorrect, or the first association code is not invalid, or the second association code corresponding to the hardware wallet data is not active, it can send a permission error message corresponding to the permission indication information to the application management server, indicating that the deletion of the relevant data in the first device is not permitted. Correspondingly, the application management server can receive the permission error message from the wallet management server and send a denial-of-deletion command to the first device through the second proxy terminal to prevent the data from being mistakenly deleted.

[0304] In one possible approach, if the wallet management server determines that the permission indication information is correct, the first association code is invalid, and the second association code corresponding to the hardware wallet data is valid, then the wallet management server can send permission confirmation information corresponding to the permission indication information to the application management server to indicate that the relevant data in the first device can be cleared.

[0305] S1005, The application management server responds to the permission confirmation information and determines that the first device has the permission to clear the hardware wallet data.

[0306] In one possible approach, the application management server can receive permission confirmation information from the wallet management server and, in response to the permission confirmation information, send a data clearing instruction to the first device via the second proxy terminal, instructing the first device to clear the relevant data.

[0307] In one embodiment, the hardware wallet migration method provided in this application, when applied to a first agent terminal, further includes: S1101-S1103.

[0308] S1101, The first agent terminal sends a migration request to the wallet management server.

[0309] Among them, the migration request information can be used to request the migration of hardware wallet data deployed on the first device to the second device.

[0310] S1102. In response to the migration confirmation information from the wallet management server, the first agent terminal sends a configuration request to the application management server to request the configuration of hardware wallet data.

[0311] S1103, the first agent terminal responds to the data configuration instruction of the application management server and sends a data configuration instruction to the second device so that the second device can configure hardware wallet data.

[0312] In one embodiment, before the first agent terminal sends migration request information to the wallet management server, the hardware wallet migration method provided in this application embodiment further includes: S1201-S1202.

[0313] S1201, The first agent terminal sends a data query request to the second device to check whether any hardware wallet data has been configured.

[0314] In one possible approach, the first agent terminal can possess device attribute determination functionality and be configured with data query capabilities. The device attribute determination functionality can be used to determine whether the current device is a second device or a first device. If the current device is determined to be a second device, the first agent terminal can call relevant interfaces to execute the data query function to determine whether the second device has been configured with any hardware wallet data. If the current device is determined to be a first device, the first agent terminal can generate a prompt message indicating that the second device needs to be operated for data migration, and that other business operations must be suspended during the migration process.

[0315] In one possible approach, the user can perform a data migration operation (e.g., clicking a migration button) through the input module configured on the first agent terminal. In response to this data migration operation, before sending the migration request information to the wallet management server, the first agent terminal can generate a data query request using its configured data query function to check whether any hardware wallet data has been configured, and send this request to the second device to determine whether the second device has been configured with any hardware wallet data, thereby avoiding data overwrite issues.

[0316] S1202, the first agent terminal responds to the data query result of the second device and generates a first prompt message.

[0317] In one possible approach, the second device may respond to a data query request from the first agent terminal, determine whether any hardware wallet data has been configured, and generate a first prompt message.

[0318] Specifically, when the data query result is used to represent the configured arbitrary hardware wallet data, the first prompt message can be used to prompt the clearing of arbitrary hardware wallet data, or to stop the migration of hardware wallet data deployed on the first device to the second device.

[0319] When the data query results are used to indicate that no hardware wallet data has been configured, the first prompt message can be used to prompt the user to start migrating the hardware wallet data deployed on the first device to the second device, so that the user can understand that the hardware wallet data configuration process can begin.

[0320] In one embodiment, the hardware wallet migration method provided in this application further includes: S1301-S1303.

[0321] S1301, In response to the user's operation of editing the parent wallet information, the first agent terminal sends a wallet information request to the wallet management server.

[0322] The wallet information request can be used to obtain hardware wallet information associated with the parent wallet information. The hardware wallet information may include the association code of at least one hardware wallet.

[0323] In one possible approach, the wallet management server can store information on multiple hardware wallets, each corresponding one-to-one with a master wallet. Users can edit the master wallet information via an input module configured on the first agent terminal. In response to the user's edit operation, the first agent terminal can send a wallet information request to the wallet management server.

[0324] Correspondingly, the wallet management server can receive wallet information requests from the first agent terminal, parse the wallet information requests to obtain the parent wallet information corresponding to the parent wallet information editing operation, and further determine the hardware wallet information corresponding to the parent wallet information corresponding to the parent wallet information editing operation, and send the determined hardware wallet information to the first agent terminal.

[0325] S1302, The first agent terminal receives hardware wallet information from the wallet management server.

[0326] In one possible approach, the hardware wallet information may also include at least one wallet name that corresponds one-to-one with at least one hardware wallet.

[0327] In one possible approach, the first agent terminal can receive hardware wallet information from the wallet management server and display at least one wallet name corresponding to at least one hardware wallet through a configured display module.

[0328] S1303, In response to the selection operation performed by the user, the first agent terminal determines the association code of the hardware wallet corresponding to the selection operation in the hardware wallet information as the first association code corresponding to the first device.

[0329] In one possible approach, the user can learn about at least one wallet name that corresponds one-to-one with at least one hardware wallet through the display module configured on the first agent terminal. Furthermore, the user can perform a selection operation through the input module configured on the first agent terminal.

[0330] In response to a user's selection action, the first agent terminal can determine the wallet name corresponding to the selection action, identify the hardware wallet corresponding to the wallet name in the hardware wallet information as the target hardware wallet, and determine the association code corresponding to the target hardware wallet as the first association code. Furthermore, the first agent terminal can send a migration request to the wallet management server.

[0331] In one embodiment, the hardware wallet migration method provided in this application is applied to a wallet management server and includes: S1401-S1402.

[0332] S1401, The wallet management server responds to the migration request information of the first agent terminal and sends migration confirmation information to the first agent terminal.

[0333] Among them, the migration request information can be used to request the migration of hardware wallet data deployed on the first device to the second device.

[0334] S1402, The wallet management server responds to the data acquisition request from the application management server and sends the hardware wallet data deployed on the first device to the application management server.

[0335] In one embodiment, the hardware wallet migration method provided in this application further includes: S1501-S1503.

[0336] S1501, The wallet management server responds to the status update instruction carrying verification data from the first agent terminal and verifies the verification data.

[0337] Among them, the verification data can be used to characterize the integrity of the hardware wallet data.

[0338] S1502. When the verification data is successfully verified, the wallet management server updates the first association code corresponding to the first device to an invalid state and updates the second association code corresponding to the second device to an effective state.

[0339] S1503, The wallet management server sends an update success message to the first agent terminal.

[0340] In one embodiment, the hardware wallet migration method provided in this application further includes: S1601.

[0341] S1601. The wallet management server responds to the permission instruction information from the application management server. When it is determined that the permission instruction information is correct, the first association code is invalid, and the second association code is effective, the wallet management server sends permission confirmation information to the application management server.

[0342] In one embodiment, the hardware wallet migration method provided in this application is applied to an application management server and includes: S1701-S1703.

[0343] S1701, The application management server responds to the configuration request information from the first agent terminal and sends a data acquisition request to the wallet management server.

[0344] The configuration request information can be used to request the configuration of hardware wallet data deployed on the first device to the second device.

[0345] S1702, The application management server receives hardware wallet data from the wallet management server.

[0346] S1703. The application management server sends a data configuration command to the second device through the first agent terminal, so that the second device can configure hardware wallet data.

[0347] In one embodiment, the hardware wallet migration method provided in this application further includes: S1801-S1803.

[0348] S1801, In response to the data clearing request from the second agent terminal, the application management server sends a permission acquisition instruction to the second agent terminal to the first device.

[0349] S1802, In response to the permission instruction information sent by the first device through the second proxy terminal, the application management server sends permission instruction information to the wallet management server. The permission instruction information indicates that the first device has the permission to clear hardware wallet data.

[0350] S1803, In response to the permission confirmation information from the wallet management server, the application management server sends a data clearing command to the first device through the second agent terminal, so that the first device clears the hardware wallet data.

[0351] In one embodiment, such as Figure 11 The diagram shown illustrates a hardware wallet migration process according to an embodiment of this application. Users can initiate a data migration request through a proxy application and select the attributes of the current device.

[0352] If the current device is designated as the first device, the first agent terminal can prompt the user to initiate a data migration request using the second device. During the data migration process, other business operations cannot be performed. The user can choose to clear residual data or cancel based on the prompts from the second device. If the user chooses to clear data, the first device can send a data clearing request to the application management server. If the user chooses to cancel, the user can continue using the first device.

[0353] If the current device is classified as a second device, the first agent terminal can query whether any hardware wallet data has been configured on the second device. If it has, the first agent terminal can prompt the user to clear the data or end the data migration. If it has not been configured, the first agent terminal can send a migration request to the wallet management server.

[0354] After receiving the migration request, the wallet management server can determine whether the migration conditions are met based on the hardware wallet status, the device information of the second device, and the device information of the first device. If not, the wallet management server can send an error code to the second device through the first proxy terminal. Upon receiving the error code, the second device can prompt to end the data migration. If the conditions are met, the wallet management server can send a verification success message to the first proxy terminal. Upon receiving the verification success message, the first proxy terminal can send its identity information to the wallet management server.

[0355] After successful identity verification, the first agent terminal can send a configuration request to the application management server. The application management server can then determine whether the second device meets the migration conditions, specifically whether the second device is configured with arbitrary hardware wallet data. If the second device is configured with arbitrary hardware wallet data, the migration conditions are not met, and the application management server can instruct the first agent terminal to send an error code to the second device. Upon receiving the error code, the second device can prompt to end the data migration.

[0356] If the second device is not configured with any hardware wallet data, the migration conditions are met, and the application management server can obtain the target hardware wallet's wallet data, second association code, and key from the wallet application management server. If data retrieval fails, the application management server can send an error code to the second device through the first proxy terminal. Upon receiving the error code, the second device can prompt to end the data migration.

[0357] If data acquisition is successful, the application management server can generate application configuration instructions. Further, the application management server can send these instructions to the second device via the first proxy terminal in a specific order. After completing the data configuration, the second device can obtain permission indication information based on the permission acquisition instructions and send update indication information to the wallet management server via the first proxy terminal.

[0358] The wallet management server can receive update instructions and verify the verification data in the update instructions. If the verification fails, the wallet management server can delete the migration process data and send an error code to the second device through the first agent terminal. The second device can then notify the user that the migration failed and that they can retry or continue using the first device.

[0359] If the verification is successful, the wallet management server can update the second association code to an active state, update the first association code to an invalid state, and update the target hardware wallet's status to a normal state. The second device can then notify the user that the hardware wallet data has been configured, the first device has become invalid, and any residual data on the first device can be cleared.

[0360] Based on this, the first agent terminal can send a migration request to the wallet management server to request the migration of hardware wallet data deployed on the first device to the second device. In response to the migration request, the wallet management server can send a migration confirmation to the first agent terminal. In response to the migration confirmation, the first agent terminal can send a configuration request to the application management server to request the configuration of the hardware wallet data. In response to the configuration request, the application management server can obtain the hardware wallet data from the wallet management server and send a data configuration command to the second device through the first agent terminal. The second device can then configure the hardware wallet data in response to the data configuration command.

[0361] Based on the interaction process of the above multiple devices, this application can migrate hardware wallet data deployed on the first device to the second device, and then re-enable the hardware wallet data deployed on the first device on the second device, avoiding the loss of hardware wallet data deployed on the first device. The second device can support business operations such as transaction record querying and single-connection transactions. Therefore, this application can be used to improve the technical problem of low security of hardware wallets under abnormal conditions.

[0362] The foregoing primarily describes the solutions provided by the embodiments of this application from a methodological perspective. To achieve the aforementioned functions, the hardware wallet migration device or electronic device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0363] This application embodiment can, based on the above method, exemplarily divide the first agent terminal, second agent terminal, second device, first device, wallet management server, or application management server into functional modules. For example, the first agent terminal may include each functional module corresponding to each functional division, or two or more functions may be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division; in actual implementation, there may be other division methods.

[0364] For example, embodiments of this application also provide a hardware wallet migration device.

[0365] Figure 12 This is a block diagram illustrating a hardware wallet migration system according to an exemplary embodiment. (Refer to...) Figure 12 The migration system for the hardware wallet includes: a first agent terminal 1901, a wallet management server 1902, an application management server 1903, a second device 1904, and a first device 1905;

[0366] The first agent terminal 1901 is configured to send migration request information to the wallet management server 1902; the migration request information is used to request the migration of hardware wallet data deployed on the first device 1905 to the second device 1904;

[0367] Wallet management server 1902 is configured to respond to migration request information by sending migration confirmation information to first agent terminal 1901;

[0368] The first agent terminal 1901 is also configured to respond to the migration confirmation information by sending a configuration request message to the application management server 1903 to request the configuration of hardware wallet data.

[0369] Application management server 1903 is configured to respond to configuration request information, obtain hardware wallet data from wallet management server 1902, and send data configuration instructions to second device 1904 through first agent terminal 1901.

[0370] The second device 1904 is configured to execute a data configuration command to configure hardware wallet data.

[0371] In one possible implementation, the migration request information includes a first association code corresponding to the first device 1905 and device information of the second device 1904;

[0372] Wallet management server 1902 is also configured to determine whether to allow the first device 1905 to configure hardware wallet data based on the hardware wallet status corresponding to the first association code, the device information of the first device 1905, and the device information of the second device 1904.

[0373] In one possible implementation, when it is determined that the first device 1905 is allowed to configure hardware wallet data, the wallet management server 1902 is also configured to send migration permission information to the first agent terminal 1901.

[0374] The first agent terminal 1901 is also configured to respond to the migration permission information, obtain identity information from the second device 1904, and send an authentication request carrying the identity information to the wallet management server 1902.

[0375] Wallet management server 1902 is also configured to respond to authentication requests, verify identity information, and when the identity information is successfully verified, update the hardware wallet status to the pending migration status and establish a correspondence between the second device 1904 and the second association code.

[0376] In one possible implementation, the application management server 1903 is also configured to execute a data query command sent to the second device 1904 via the first proxy terminal 1901; the data query command is used to determine whether any hardware wallet data has been configured.

[0377] The second device 1904 is also configured to execute a response to a data query command, determine the data query result, and send the data query result to the application management server 1903 through the first agent terminal 1901.

[0378] In one possible implementation, when the data query result is data of an arbitrary hardware wallet that has been configured, the application management server 1903 is also configured to send a clearing instruction message to the second device 1904 through the first agent terminal 1901.

[0379] The second device 1904 is also configured to generate a prompt message in response to the clearing instruction message, indicating that any configured hardware wallet data should be cleared.

[0380] In one possible implementation, when the data query result is no hardware wallet data configured, the application management server 1903 is also configured to send a data request message to the wallet management server 1902 carrying the device information of the first association code and the second device 1904.

[0381] Wallet management server 1902 is also configured to respond to data request information and send hardware wallet data deployed on first device 1905 to application management server 1903 when the hardware wallet corresponding to the first association code is in a state of pending migration and the device information of second device 1904 has a corresponding relationship with the second association code.

[0382] In one possible implementation, the first agent terminal 1901 is also configured to send a status update request to the second device 1904;

[0383] The second device 1904 is also configured to perform a response to a state update request, determine verification data to characterize the integrity of the hardware wallet data, and send a state update indication carrying the verification data to the wallet management server 1902 via the first agent terminal 1901.

[0384] The wallet management server 1902 is also configured to perform a response to a status update instruction, verify the verification data, and when the verification data is successfully verified, update the first association code to an invalid state and the second association code to an active state, and send an update success message to the second device 1904 through the first agent terminal 1901.

[0385] The second device 1904 is also configured to generate a message in response to a successful update, indicating that the hardware wallet data has been successfully configured.

[0386] In one possible implementation, the hardware wallet migration system also includes: a second agent terminal 1906;

[0387] The first device 1905 is configured to send a data clearing request to the application management server 1903 via the second agent terminal 1906;

[0388] Application management server 1903 is also configured to respond to data clearing requests and, if it is determined that the first device 1905 has the authority to clear hardware wallet data, send a data clearing command to the first device 1905 through the second proxy terminal 1906.

[0389] The first device 1905 is also configured to execute a data clearing command to clear hardware wallet data.

[0390] In one possible implementation, the application management server 1903 is also configured to execute an instruction to send an access control request to the first device 1905 via the second proxy terminal 1906;

[0391] The first device 1905 is also configured to execute a permission acquisition command by sending permission indication information to the application management server 1903 through the second agent terminal 1906; the permission indication information is used to indicate that the first device 1905 has the permission to clear hardware wallet data.

[0392] Application management server 1903 is also configured to respond to permission instruction information by sending permission instruction information to wallet management server 1902;

[0393] Wallet management server 1902 is also configured to respond to permission indication information and send permission confirmation information to application management server 1903 when it is determined that the permission indication information is correct, the first association code is in an invalid state, and the second association code is in an effective state.

[0394] Application management server 1903 is also configured to execute a response to permission confirmation information to determine that the first device 1905 has permission to clear hardware wallet data.

[0395] Figure 13 This is a block diagram illustrating a hardware wallet migration device according to an exemplary embodiment. (Refer to...) Figure 13 The migration device for the hardware wallet can be applied to the first agent terminal, including: a sending unit 2001;

[0396] Sending unit 2001 is configured to send migration request information to the wallet management server; the migration request information is used to request the migration of hardware wallet data deployed on the first device to the second device.

[0397] The sending unit 2001 is also configured to execute a migration confirmation message in response to the wallet management server and send a configuration request message to the application management server to request configuration of hardware wallet data.

[0398] The sending unit 2001 is also configured to execute a data configuration instruction in response to the application management server, and send a data configuration instruction to the second device to enable the second device to configure hardware wallet data.

[0399] In one possible implementation, the hardware wallet migration device further includes: a generation unit 2002;

[0400] The sending unit 2001 is also configured to execute a data query request sent to the second device to query whether any hardware wallet data has been configured;

[0401] The generation unit 2002 is configured to generate a first prompt message in response to the data query result of the second device. When the data query result indicates that any hardware wallet data has been configured, the first prompt message prompts the user to clear any hardware wallet data or stop migrating the hardware wallet data deployed on the first device to the second device. When the data query result indicates that no hardware wallet data has been configured, the first prompt message prompts the user to start migrating the hardware wallet data deployed on the first device to the second device.

[0402] In one possible implementation, the hardware wallet migration device further includes: a receiving unit 2003 and a determining unit 2004;

[0403] The sending unit 2001 is also configured to perform a wallet information request in response to a user-executed parent wallet information editing operation by sending a wallet information request to the wallet management server; the wallet information request is used to obtain hardware wallet information associated with the parent wallet information; the hardware wallet information includes at least one hardware wallet association code;

[0404] The receiving unit 2003 is configured to receive hardware wallet information from the wallet management server;

[0405] The determining unit 2004 is configured to perform a selection operation in response to the user's action, and determine the association code of the hardware wallet corresponding to the selection operation in the hardware wallet information as the first association code corresponding to the first device.

[0406] Figure 14 This is a block diagram illustrating a hardware wallet migration device according to an exemplary embodiment. (Refer to...) Figure 14 The hardware wallet migration device, applied to a wallet management server, includes: a receiving unit 2101 and a sending unit 2102;

[0407] The receiving unit 2101 is configured to receive migration request information from the first agent terminal;

[0408] Sending unit 2102 is configured to send migration confirmation information to the first agent terminal in response to the migration request information received by receiving unit 2101; the migration request information is used to request the migration of hardware wallet data deployed on the first device to the second device.

[0409] The receiving unit 2101 is also configured to receive a data acquisition request from the application management server;

[0410] The sending unit 2102 is also configured to send hardware wallet data deployed on the first device to the application management server in response to the data acquisition request received by the receiving unit 2101 from the application management server.

[0411] In one possible implementation, the hardware wallet migration device further includes: a verification unit 2103 and an update unit 2104;

[0412] Verification unit 2103 is configured to execute a status update indication carrying verification data in response to a first agent terminal, and to verify the verification data; the verification data is used to characterize the integrity of the hardware wallet data.

[0413] The update unit 2104 is configured to update the first association code corresponding to the first device to an invalid state and update the second association code corresponding to the second device to an active state when the verification data is successfully verified.

[0414] The sending unit 2102 is also configured to send an update success message to the first agent terminal.

[0415] In one possible implementation, the sending unit 2102 is further configured to respond to the permission indication information of the application management server, and send permission confirmation information to the application management server when it is determined that the permission indication information is correct, the first association code is in an invalid state, and the second association code is in an effective state.

[0416] Figure 15 This is a block diagram illustrating a hardware wallet migration device according to an exemplary embodiment. (Refer to...) Figure 15 The hardware wallet migration device is applied to the application management server and includes: a sending unit 2201 and a receiving unit 2202;

[0417] The sending unit 2201 is configured to execute a configuration request message in response to the first agent terminal and send a data acquisition request to the wallet management server; the configuration request message is used to request the hardware wallet data deployed on the first device to be configured to the second device;

[0418] The receiving unit 2202 is configured to receive hardware wallet data from the wallet management server;

[0419] The sending unit 2201 is also configured to execute a data configuration instruction to be sent to the second device through the first agent terminal, so that the second device configures hardware wallet data.

[0420] In one possible implementation, the sending unit 2201 is further configured to execute a data clearing request in response to the second agent terminal, sending an access permission instruction to the second agent terminal for the first device;

[0421] The sending unit 2201 is also configured to send permission indication information to the wallet management server in response to the permission indication information sent by the first device through the second proxy terminal; the permission indication information is used to indicate that the first device has the permission to clear hardware wallet data;

[0422] The sending unit 2201 is also configured to execute a data clearing instruction sent to the first device via the second agent terminal in response to the permission confirmation information of the wallet management server, so that the first device clears the hardware wallet data.

[0423] Figure 16 This is a block diagram illustrating an electronic device according to an exemplary embodiment. The electronic device may be the second device described above, the first device described above, or the wallet management server or application management server described above.

[0424] like Figure 16 As shown, the electronic device 200 includes, but is not limited to, a processor 210 and a memory 220.

[0425] The memory 220 described above is used to store the executable instructions of the processor 210. It is understood that the processor 210 is configured to execute instructions to implement the hardware wallet migration method in the above embodiment.

[0426] It should be noted that those skilled in the art will understand that Figure 16 The electronic device structure shown does not constitute a limitation on the electronic device; the electronic device may include, but is not limited to, other electronic devices. Figure 16 This may indicate more or fewer components, or combinations of certain components, or different component arrangements.

[0427] Processor 210 is the control center of the electronic device. It connects various parts of the electronic device via various interfaces and lines. By running or executing software programs and / or modules stored in memory 220, and by calling data stored in memory 220, it performs various functions and processes data, thereby providing overall monitoring of the electronic device. Processor 210 may include one or more processing units; optionally, processor 210 may integrate an application processor and a modem processor. The application processor mainly handles the operating system, user interface, and applications, while the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into processor 210.

[0428] The memory 220 can be used to store software programs and various data. The memory 220 may primarily include a program storage area and a data storage area, wherein the program storage area may store the operating system, applications required by at least one functional module, etc. Furthermore, the memory 220 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0429] In an exemplary embodiment, a computer-readable storage medium including instructions is also provided, such as a memory 220 including instructions, which can be executed by a processor 210 of an electronic device 200 to implement the hardware wallet migration method in the above embodiments.

[0430] Optionally, the computer-readable storage medium may be a non-transitory computer-readable storage medium, such as a read-only memory (ROM), random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device.

[0431] In an exemplary embodiment, this application also provides a computer program product including one or more instructions, which can be executed by the processor 210 of the electronic device 200 to complete the hardware wallet migration method in the above embodiments.

[0432] It should be noted that when one or more instructions in the computer-readable storage medium or computer program product are executed by the processor 210 of the electronic device 200, they implement the various processes of the above-described hardware wallet migration method embodiment and can achieve the same technical effect as the above-described hardware wallet migration method. To avoid repetition, they will not be described again here.

[0433] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0434] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another apparatus, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0435] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the classified units can be selected to achieve the purpose of this embodiment, depending on actual needs.

[0436] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0437] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, essentially, or the parts that contribute to general technology, or the entirety or portion of the technical solution, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute the entirety or portion of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0438] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for migrating a hardware wallet, characterized in that, include: The first agent terminal sends a migration request to the wallet management server; The migration request information is used to request the migration of hardware wallet data deployed on the first device to the second device; the migration request information includes a first association code corresponding to the first device and device information of the second device; In response to the migration request information, the wallet management server determines whether to allow the first device to configure the hardware wallet data based on the hardware wallet status corresponding to the first association code, the device information of the first device, and the device information of the second device. When it is determined that the first device is allowed to configure the hardware wallet data, the wallet management server sends migration permission information to the first agent terminal; In response to the migration permission information, the first agent terminal obtains identity information from the second device and sends an authentication request carrying the identity information to the wallet management server; The wallet management server responds to the identity verification request, verifies the identity information, and when the identity information is successfully verified, updates the hardware wallet status to a pending migration status and establishes a correspondence between the second device and the second association code. The wallet management server sends migration confirmation information to the first agent terminal; In response to the migration confirmation information, the first agent terminal sends a configuration request to the application management server to request the configuration of the hardware wallet data. In response to the configuration request information, the application management server obtains the hardware wallet data from the wallet management server and sends a data configuration instruction to the second device through the first agent terminal. The second device, in response to the data configuration instruction, configures the hardware wallet data.

2. The hardware wallet migration method according to claim 1, characterized in that, Before obtaining the hardware wallet data from the wallet management server and sending the data configuration command to the second device through the first proxy terminal, the method further includes: The application management server sends a data query instruction to the second device through the first proxy terminal; the data query instruction is used to determine whether any hardware wallet data has been configured. The second device responds to the data query instruction, determines the data query result, and sends the data query result to the application management server through the first agent terminal.

3. The hardware wallet migration method according to claim 2, characterized in that, Also includes: When the data query result is that any hardware wallet has been configured, the application management server sends a clearing instruction to the second device through the first proxy terminal; In response to the clearing instruction, the second device generates a prompt message to clear the configured data of any hardware wallet.

4. The hardware wallet migration method according to claim 2, characterized in that, The step of obtaining the hardware wallet data from the wallet management server includes: When the data query result is that no hardware wallet data is configured, the application management server sends a data request message carrying the first association code and the device information of the second device to the wallet management server. When the hardware wallet corresponding to the first association code is in a state of pending migration, and the device information of the second device has a corresponding relationship with the second association code, the wallet management server responds to the data request information and sends the hardware wallet data deployed on the first device to the application management server.

5. The hardware wallet migration method according to claim 1, characterized in that, After configuring the hardware wallet data, the following is also included: The first agent terminal sends a status update request to the second device; In response to the status update request, the second device determines verification data to characterize the integrity of the hardware wallet data, and sends a status update indication carrying the verification data to the wallet management server through the first agent terminal. In response to the status update instruction, the wallet management server verifies the verification data. When the verification data is successfully verified, the first association code is updated to an invalid state, and the second association code is updated to an effective state. The server then sends an update success message to the second device through the first agent terminal. In response to the update success information, the second device generates a prompt message indicating that the hardware wallet data has been successfully configured.

6. The hardware wallet migration method according to claim 1, characterized in that, Also includes: The first device sends a data clearing request to the application management server through the second proxy terminal; In response to the data clearing request, if the application management server determines that the first device has the permission to clear the hardware wallet data, it sends a data clearing instruction to the first device through the second proxy terminal. The first device responds to the data clearing command by clearing the hardware wallet data.

7. The hardware wallet migration method according to claim 6, characterized in that, The step of determining that the first device has permission to clear the hardware wallet data includes: The application management server sends a permission acquisition command to the first device through the second proxy terminal; In response to the permission acquisition command, the first device sends permission indication information to the application management server through the second proxy terminal; the permission indication information is used to indicate that the first device has the permission to clear the hardware wallet data; In response to the permission instruction information, the application management server sends the permission instruction information to the wallet management server; In response to the permission indication information, when the wallet management server determines that the permission indication information is correct, the first association code is invalid, and the second association code is effective, it sends permission confirmation information to the application management server. In response to the permission confirmation information, the application management server determines that the first device has the permission to clear the hardware wallet data.

8. A method for migrating a hardware wallet, characterized in that, Applied to the first agent terminal, including: Send a migration request to the wallet management server; the migration request is used to request the migration of hardware wallet data deployed on the first device to the second device; the migration request includes a first association code corresponding to the first device and device information of the second device; Receive migration permission information from the wallet management server; In response to the migration permission information, identity information is obtained from the second device, and an authentication request carrying the identity information is sent to the wallet management server; The wallet management server responds to the identity verification request, verifies the identity information, and when the identity information is successfully verified, updates the hardware wallet status to the pending migration status and establishes the correspondence between the second device and the second association code. Receive migration confirmation information from the wallet management server; In response to the migration confirmation information from the wallet management server, a configuration request is sent to the application management server to request the configuration of the hardware wallet data. In response to the data configuration instruction from the application management server, a data configuration instruction is sent to the second device to enable the second device to configure the hardware wallet data.

9. The hardware wallet migration method according to claim 8, characterized in that, Before sending the migration request information to the wallet management server, the process also includes: Send a data query request to the second device to check whether any hardware wallet data has been configured; In response to the data query result of the second device, a first prompt message is generated; when the data query result indicates that the arbitrary hardware wallet data has been configured, the first prompt message is used to prompt the clearing of the arbitrary hardware wallet data, or to stop migrating the hardware wallet data deployed on the first device to the second device; when the data query result indicates that the arbitrary hardware wallet data has not been configured, the first prompt message is used to prompt the start of migrating the hardware wallet data deployed on the first device to the second device.

10. The hardware wallet migration method according to claim 8, characterized in that, Also includes: In response to the user's edit operation on the parent wallet information, a wallet information request is sent to the wallet management server; The wallet information request is used to obtain hardware wallet information associated with the parent wallet information; the hardware wallet information includes at least one hardware wallet association code; Receive the hardware wallet information from the wallet management server; In response to a selection operation performed by the user, the association code of the hardware wallet corresponding to the selection operation in the hardware wallet information is determined as the first association code corresponding to the first device.

11. A method for migrating a hardware wallet, characterized in that, Used in wallet management servers, including: The system receives a migration request from a first agent terminal; the migration request is used to request the migration of hardware wallet data deployed on a first device to a second device; the migration request includes a first association code corresponding to the first device and device information of the second device. Based on the hardware wallet status corresponding to the first association code, the device information of the first device, and the device information of the second device, determine whether to allow the first device to configure the hardware wallet data; When it is determined that the first device is allowed to configure the hardware wallet data, a migration permission message is sent to the first agent terminal. Receive an authentication request from a first agent terminal; the authentication request carries identity information obtained by the first agent terminal from the second device; In response to the identity verification request, the identity information is verified, and when the identity information is successfully verified, the hardware wallet status is updated to a pending migration status, and a correspondence between the second device and the second association code is established. Send migration confirmation information to the first agent terminal; In response to a data retrieval request from the application management server, the hardware wallet data deployed on the first device is sent to the application management server.

12. The hardware wallet migration method according to claim 11, characterized in that, Also includes: In response to a status update indication carrying verification data from the first agent terminal, the verification data is verified. The verification data is used to characterize the integrity of the hardware wallet data; When the verification data is successfully verified, the first association code corresponding to the first device is updated to an invalid state, and the second association code corresponding to the second device is updated to an active state. Send an update success message to the first agent terminal.

13. The hardware wallet migration method according to claim 11, characterized in that, Also includes: In response to the permission indication information from the application management server, when it is determined that the permission indication information is correct, the first association code is invalid, and the second association code is effective, permission confirmation information is sent to the application management server.

14. A method for migrating a hardware wallet, characterized in that, Used in application management servers, including: Receive configuration request information from the first agent terminal; the configuration request information is used to request that the hardware wallet data deployed on the first device be configured to the second device; In response to the configuration request information from the first agent terminal, a data retrieval request is sent to the wallet management server; Receive hardware wallet data from the wallet management server; The first agent terminal sends a data configuration command to the second device, so that the second device can configure the hardware wallet data. The first agent terminal is configured to send migration request information to the wallet management server; the migration request information includes a first association code corresponding to the first device and device information of the second device. Receive migration permission information from the wallet management server; In response to the migration permission information, identity information is obtained from the second device, and an authentication request carrying the identity information is sent to the wallet management server; The wallet management server responds to the identity verification request, verifies the identity information, and when the identity information is successfully verified, updates the hardware wallet status to the pending migration status and establishes the correspondence between the second device and the second association code. Receive migration confirmation information from the wallet management server; In response to the migration confirmation information from the wallet management server, a configuration request is sent to the application management server to request the configuration of the hardware wallet data.

15. The hardware wallet migration method according to claim 14, characterized in that, Also includes: In response to the data clearing request from the second agent terminal, a permission acquisition command is sent to the first device through the second agent terminal; In response to the permission acquisition instruction, the first device sends permission indication information to the application management server through the second proxy terminal. The permission indication information is used to indicate that the first device has the permission to clear the hardware wallet data. Send the permission instruction information to the wallet management server; In response to the permission confirmation information from the wallet management server, a data clearing command is sent to the first device through the second agent terminal, so that the first device clears the hardware wallet data.

16. A hardware wallet migration system, characterized in that, include: First agent terminal, wallet management server, application management server, second device and first device; The first agent terminal is configured to send migration request information to the wallet management server; the migration request information is used to request the migration of hardware wallet data deployed on the first device to the second device; the migration request information includes a first association code corresponding to the first device and device information of the second device. The wallet management server is configured to respond to the migration request information and determine whether to allow the first device to configure the hardware wallet data based on the hardware wallet status corresponding to the first association code, the device information of the first device, and the device information of the second device. When it is determined that the first device is allowed to configure the hardware wallet data, a migration permission message is sent to the first agent terminal. The first agent terminal is configured to, in response to the migration permission information, obtain identity information from the second device and send an authentication request carrying the identity information to the wallet management server; The wallet management server is also configured to, in response to the authentication request, verify the identity information, and when the identity information is successfully verified, update the hardware wallet status to a pending migration status, establish the correspondence between the second device and the second association code, and send migration confirmation information to the first agent terminal; The first agent terminal is also configured to respond to the migration confirmation information by sending a configuration request to the application management server to request the configuration of the hardware wallet data. The application management server is configured to respond to the configuration request information, obtain the hardware wallet data from the wallet management server, and send data configuration instructions to the second device through the first proxy terminal; The second device is configured to execute the data configuration instruction to configure the hardware wallet data.

17. A hardware wallet migration device, characterized in that, Applied to the first agent terminal, it includes: a sending unit and a receiving unit; The sending unit is configured to send migration request information to the wallet management server; the migration request information is used to request the migration of hardware wallet data deployed on the first device to the second device; the migration request information includes a first association code corresponding to the first device and device information of the second device; The receiving unit is configured to receive migration permission information from the wallet management server; The sending unit is further configured to, in response to the migration permission information, obtain identity information from the second device and send an authentication request carrying the identity information to the wallet management server; The wallet management server is configured to: in response to the identity verification request, verify the identity information, and when the identity information is successfully verified, update the hardware wallet status to a pending migration status and establish a correspondence between the second device and the second association code; The sending unit is also configured to send configuration request information for requesting configuration of the hardware wallet data to the application management server in response to the migration confirmation information of the wallet management server. The sending unit is further configured to execute a data configuration instruction in response to the application management server, sending a data configuration instruction to the second device to enable the second device to configure the hardware wallet data.

18. A hardware wallet migration device, characterized in that, Applied to wallet management servers, it includes: a receiving unit and a sending unit; The receiving unit is configured to receive migration request information from a first agent terminal; the migration request information is used to request the migration of hardware wallet data deployed on the first device to a second device; the migration request information includes a first association code corresponding to the first device and device information of the second device; The sending unit is configured to determine whether to allow the first device to configure the hardware wallet data based on the hardware wallet status corresponding to the first association code, the device information of the first device, and the device information of the second device; when it is determined that the first device is allowed to configure the hardware wallet data, it sends migration permission information to the first agent terminal. The receiving unit is further configured to receive an authentication request from the first proxy terminal; the authentication request carries identity information obtained by the first proxy terminal from the second device; The sending unit is configured to, in response to the authentication request, verify the identity information, and when the identity information is successfully verified, update the hardware wallet status to a pending migration status and establish a correspondence between the second device and the second association code; and send migration confirmation information to the first agent terminal; the receiving unit is further configured to execute a data acquisition request to receive data from the application management server; The sending unit is further configured to send the hardware wallet data deployed on the first device to the application management server in response to the data acquisition request received by the receiving unit from the application management server.

19. A hardware wallet migration device, characterized in that, Applied to application management servers, it includes: a sending unit and a receiving unit; The receiving unit is configured to receive configuration request information from the first agent terminal; the configuration request information is used to request that hardware wallet data deployed on the first device be configured to the second device. The sending unit is configured to execute a configuration request in response to the first agent terminal and send a data acquisition request to the wallet management server. The receiving unit is also configured to receive hardware wallet data from the wallet management server; The sending unit is further configured to execute a data configuration instruction to be sent to the second device through the first proxy terminal, so that the second device configures the hardware wallet data; The first agent terminal is configured to: send migration request information to the wallet management server; the migration request information includes a first association code corresponding to the first device and device information of the second device; receive migration permission information from the wallet management server; in response to the migration permission information, obtain identity information from the second device and send an authentication request carrying the identity information to the wallet management server; in response to the authentication request, the wallet management server verifies the identity information, and when the identity information is successfully verified, updates the hardware wallet status to a pending migration status and establishes a correspondence between the second device and the second association code; receive migration confirmation information from the wallet management server; and in response to the migration confirmation information from the wallet management server, send configuration request information to the application management server to request configuration of the hardware wallet data.

20. An electronic device, characterized in that, The electronic device includes: processor; Memory used to store the processor's executable instructions; The processor is configured to execute the instructions to implement the hardware wallet migration method as described in any one of claims 1-15.

21. A computer-readable storage medium storing instructions thereon, characterized in that, When the instructions in the computer-readable storage medium are executed by a processor, the processor is able to perform the hardware wallet migration method as described in any one of claims 1-15.

Images