Digital currency hard wallet and plug-in application system and control method thereof

Abstract

The embodiment of the invention provides a plug-in application system for a digital currency hard wallet, the system comprises a shared interface and a hard wallet plug-in application, the shared interface is configured to provide an external access entry for accessing the hard wallet plug-in application, receive parameter information transmitted from a hard wallet logic application, and send the parameter information to the hard wallet logic application; the hard wallet logic application receives parameter information and transmits the parameter information to the hard wallet plug-in application, the parameter information is associated with a digital currency instruction received by the hard wallet logic application, and the digital currency instruction comprises a transaction instruction and an operation instruction; and the hard wallet plug-in application is configured to identify and call a function module of the corresponding wallet capability according to the parameter information, process the parameter information based on a preset processing logic in the function module, and return a processing result to the hard wallet logic application through the shared interface. Compared with an existing hard wallet application system, the plug-in application system is lower in scheme cost, core logic and sensitive information in application are invisible to the outside, and safety is better.

Description

Technical Field

[0001] Embodiments of the present disclosure relate to a digital currency hard wallet and a plug-in application system and control method thereof. Background Art

[0002] With the development of digital currency technology, hard wallet products have emerged, such as digital currency hard wallets that can provide digital currency transaction services.

[0003] At present, each hard wallet manufacturer develops and designs hard wallet applications with these functions according to the actual functional requirements of the hard wallet, and fixes the hard wallet application into the hard wallet when the hard wallet leaves the factory. However, this method requires each manufacturer to have software development capabilities, and when new functions of the hard wallet need to be added, more manpower development costs must be invested, resulting in higher costs for hard wallets.

[0004] Therefore, it is necessary to provide a new type of hard wallet application system that can effectively reduce the cost of hard wallets, and the applications involving core logic and sensitive data within the system are not visible to the outside and have good security performance. Summary of the invention

[0005] At least one embodiment of the present disclosure provides a plug-in application system for a digital currency hard wallet, the system comprising a shared interface and a hard wallet plug-in application, wherein: the shared interface is configured to provide an external access entry for accessing the hard wallet plug-in application, receive parameter information input from the hard wallet logic application, and transmit the parameter information to the hard wallet plug-in application, wherein the parameter information is associated with the digital currency instructions received by the hard wallet logic application, and the digital currency instructions include transaction instructions and operation instructions; the hard wallet plug-in application is configured to identify and call a functional module of the corresponding wallet capability according to the parameter information, process the parameter information based on the processing logic preset in the functional module, and return the processing result to the hard wallet logic application via the shared interface.

[0006] For example, according to the plug-in application system of at least one embodiment of the present disclosure, the functional modules include at least one of the following: a first module for generating an offline payment code, a second module for generating and / or verifying a digital currency string, and a third module for verifying identity information.

[0007] For example, according to at least one embodiment of the plug-in application system of the present disclosure, the functional module is configured to determine whether the parameter format of the parameter information is correct, and if correct, execute a preset processing logic to process the parameter information.

[0008] For example, according to the plug-in application system of at least one embodiment of the present disclosure, the first module is configured to execute the following preset processing logic to generate an offline payment code: using a set algorithm, combined with a random factor, the key factor, the calculation factor, the time factor, the event factor, the operation factor and the code information in the parameter information are operated to generate an offline payment code.

[0009] For example, according to the plug-in application system of at least one embodiment of the present disclosure, the second module is configured to execute the following preset processing logic to generate a digital currency coin string: use the preset key to decrypt the encrypted coin string in the parameter information, and verify the correctness of the decrypted coin string format; after the verification, use its own private key and the payer identification and transaction amount in the parameter information to generate a coin string sub-chain and generate a new coin string, and encrypt the new coin string.

[0010] For example, according to the plug-in application system of at least one embodiment of the present disclosure, the second module is configured to execute the following preset processing logic to verify the digital currency coin string: use the preset key to decrypt the encrypted coin string in the parameter information, and verify the correctness of the decrypted coin string format; after the verification is passed, verify the authenticity of the coin string.

[0011] For example, according to the plug-in application system of at least one embodiment of the present disclosure, the third module is configured to execute the following preset processing logic to verify the identity information: use its own private key to sign the parameter information, and return the signature result and its own public key certificate to the hard wallet logic application via the shared interface.

[0012] For example, according to the plug-in application system of at least one embodiment of the present disclosure, the third module is configured to execute the following preset processing logic to verify the identity information: compare the PIN code in the parameter information with the pre-stored PIN code, and determine whether the verification is successful based on the comparison result.

[0013] For example, according to the plug-in application system of at least one embodiment of the present disclosure, the third module is configured to execute the following preset processing logic to verify identity information: obtain the pre-stored fingerprint information ciphertext and decrypt it, compare the fingerprint information in the parameter information with the decrypted fingerprint information, and determine whether the verification is successful based on the comparison result.

[0014] For example, according to the plug-in application system of at least one embodiment of the present disclosure, the shared interface is also configured with a shared storage area, and the shared storage area stores parameter information passed in by the hard wallet logic application and the processing results returned by the hard wallet plug-in application.

[0015] At least one embodiment of the present disclosure provides a digital currency hard wallet, including: a plug-in application system provided according to at least one embodiment of the present disclosure; and a hard wallet logic application, configured to receive digital currency instructions and pass parameter information associated with the digital currency instructions to a shared interface of the plug-in application system, the digital currency instructions including transaction instructions and operation instructions.

[0016] At least one embodiment of the present disclosure provides an application control method for a digital currency hard wallet, wherein the hard wallet includes a hard wallet logic application and a plug-in application system having a shared interface and a hard wallet plug-in application, the method comprising: the hard wallet logic application receives a digital currency instruction, and transmits associated parameter information to the shared interface according to the digital currency instruction, wherein the digital currency instruction includes a transaction instruction and an operation instruction; the shared interface provides an external access entry for accessing the hard wallet plug-in application, receives the parameter information transmitted by the hard wallet logic application, and transmits the parameter information to the hard wallet plug-in application; the hard wallet plug-in application identifies and calls a functional module of the corresponding wallet capability according to the parameter information, processes the parameter information based on the processing logic preset in the functional module, and returns the processing result to the hard wallet logic application via the shared interface.

[0017] At least one embodiment of the present disclosure provides an electronic device, comprising: one or more processors; a memory storing one or more computer program modules; wherein the one or more computer program modules are configured to be executed by the one or more processors to implement a method provided according to at least one embodiment of the present disclosure.

[0018] At least one embodiment of the present disclosure provides a computer-readable medium storing computer-executable instructions, wherein the computer-executable instructions, when executed by one or more processors, implement a method provided according to at least one embodiment of the present disclosure.

[0019] The plug-in application system for a digital currency hard wallet of the disclosed embodiment provides a new type of hard wallet application system with a plug-in framework. Compared with the existing hard wallet application system, the plug-in application system has a lower solution cost, and the core logic and sensitive information in the application are not visible to the outside, so the security is better. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings of the embodiments of the present disclosure are briefly introduced below. Obviously, the drawings in the following description only relate to some embodiments of the present disclosure, and are not intended to limit the present disclosure.

[0021] Figure 1 A structural block diagram of a digital currency hard wallet according to at least one embodiment of the present disclosure is shown;

[0022] Figure 2AAn architectural block diagram of an application plug-in system for a digital currency hard wallet according to at least one embodiment of the present disclosure is shown;

[0023] Figure 2B A flow chart showing a method for controlling an application of a digital currency hard wallet according to at least one embodiment of the present disclosure is shown;

[0024] Figure 3 A functional block diagram of a hard wallet plug-in application according to at least one embodiment of the present disclosure is shown;

[0025] Figure 4 A schematic diagram of a method flow of generating an offline payment code by a first module according to at least one embodiment of the present disclosure is shown;

[0026] Figure 5A and Figure 5B Schematic diagrams of the method flow of generating a coin string and verifying a coin string by the second module according to at least one embodiment of the present disclosure are respectively shown;

[0027] Figure 6 A schematic diagram of a method flow of verifying identity information by a third module according to at least one embodiment of the present disclosure is shown;

[0028] Fig. 7A , Figure 7B and Figure 7C Schematic diagrams of processes of example application scenarios according to at least one embodiment of the present disclosure are respectively shown;

[0029] Figure 8 A schematic diagram showing an electronic device according to at least one embodiment of the present disclosure;

[0030] Fig. 9 A schematic diagram of a computer-readable medium according to at least one embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0031] In order to make the purpose, technical solution and advantages of the embodiments of the present disclosure clearer, the technical solution of the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings of the embodiments of the present disclosure. Obviously, the described embodiments are part of the embodiments of the present disclosure, not all of the embodiments. Based on the described embodiments of the present disclosure, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present disclosure.

[0032] Unless otherwise defined, the technical terms or scientific terms used herein should be understood by people with ordinary skills in the field to which the present disclosure belongs. "First", "second" and similar words used in the present disclosure do not indicate any order, quantity or importance, but are only used to distinguish different components. Similarly, "include" or "comprise" and similar words mean that the elements or objects appearing before the word cover the elements or objects listed after the word and their equivalents, without excluding other elements or objects. "Connect" or "connected" and similar words are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. "Up", "down", "left", "right" and the like are only used to indicate relative positional relationships. When the absolute position of the described object changes, the relative positional relationship may also change accordingly.

[0033] Note that the examples to be introduced below are only specific examples, and are not intended to limit the embodiments of the present disclosure to the specific shapes, hardware, connection relationships, operations, values, conditions, data, sequences, etc. shown and described. Those skilled in the art can apply the concepts of the present disclosure to construct more embodiments not mentioned in the present description by reading the present description.

[0034] The terms used in the present disclosure are those common terms currently widely used in the art in consideration of the functions of the present disclosure, but these terms may vary according to the intention of a person of ordinary skill in the art, precedents, or new technologies in the art. In addition, specific terms may be selected by the applicant, and in this case, their detailed meanings will be described in the detailed description of the present disclosure. Therefore, the terms used in the specification should not be understood as simple names, but rather as an overall description based on the meaning of the terms and the present disclosure.

[0035] Flowcharts are used in this disclosure to illustrate the operations performed by the system according to the embodiments of the present disclosure. It should be understood that the preceding or following operations are not necessarily performed precisely in order. On the contrary, various steps may be processed in reverse order or simultaneously as required. At the same time, other operations may also be added to these processes, or one or more operations may be removed from these processes.

[0036] It should be noted that the collection, collection, updating, analysis, processing, use, transmission, storage and other aspects of user personal information involved in the technical solution disclosed in this disclosure are in compliance with the provisions of relevant laws and regulations, are used for legitimate purposes, and do not violate public order and good morals. Necessary measures are taken for user personal information to prevent illegal access to user personal information data and maintain the security of user personal information, network security and national security.

[0037] Existing digital currency hard wallet manufacturers all independently develop their own hard wallet applications, resulting in high hard wallet development costs. In order to solve the above problems, at least one embodiment of the present disclosure provides a new plug-in application system for digital currency hard wallets, which can reduce the cost of hard wallets, and the application involves sensitive information and core computing logic, such as offline payment code generation, coin string generation verification, and identity verification, which are not open to the outside world and have high security.

[0038] In the disclosed embodiment, the hard wallet may be a visual card hard wallet with display capability, including a security element (SE chip) and a near field communication (NFC) card chip. For example, the hard wallet may be a portable terminal that supports NFC payment function, and performs payment or communication by using NFC. In the case of using NFC to perform payment or communication, the built-in application may be driven and used. In the disclosed embodiment, the hard wallet also supports the code scanning transaction mode, and may also use the built-in application to generate a dynamic offline payment code, and the acceptance terminal completes the digital currency transaction by scanning the payment code.

[0039] Figure 1 A structural block diagram of a digital currency hard wallet according to at least one embodiment of the present disclosure is shown. Figure 1 The embodiment of the hard wallet 100 shown is for illustration only, and other embodiments of the hard wallet may be used without departing from the scope of the present disclosure. Figure 1 As shown, the hard wallet 100 is a visual card, which includes a security element 1021, a display 1022, a power module 1023, an input element 1024, a controller 1025, a communication module 1026 and a biometric information collection module 1027.

[0040] For example, the input element 1024 may include components such as a touch screen or a keypad, configured to detect user input and obtain the detected trigger information, and send the detected trigger information to the security element 1021 or the controller 1025. For example, the input element 1024 may be a "soft switch", and an identification bit is recorded as a "switch" in the software program of the security element, and the identification bit is used to identify or control the opening or closing of a certain function or operation. The functions involved in the embodiments of the present disclosure may include: (1) control of all NFC functions (such as transaction functions and management functions); (2) control of NFC transaction functions, and non-control of management functions. These functions are controlled by the security element 1021. After the security element 1021 receives the control instruction sent by the controller 1025, the security element 1021 executes the corresponding function opening / closing.

[0041] For example, in at least one embodiment of the present disclosure, the input element 1024 detects user input including detecting a long press input or a short press input. "Long press input" means that the switch needs to be pressed continuously for a period of time (e.g., 3 seconds) to trigger the circuit to open and close, and the corresponding signal will be output only when the long press voltage value reaches a set value. In this way, the operation can be performed according to the user's intention to prevent the occurrence of misoperation. For example, the user can send a signal to the device by long pressing the button to perform a digital currency transaction intention of scanning code payment or NFC payment, or switch the visual card, etc. "Short press input" is a circuit that can be triggered by a short press, thereby triggering a corresponding signal. In this way, a quick response can be achieved, and the execution is convenient and quick. For example, a short press of the button can be used to send a signal to the device to switch the display content such as offline payment code and class balance information (e.g., wallet balance, transaction amount, transaction time, reminder to check the balance, transaction time).

[0042] The communication module 1026 is mainly connected to the acceptance terminal through communication methods such as Bluetooth, NFC, WIFI, UWB, and mobile network. In some examples, the communication module 1026 also communicates with the digital currency backend system through a secure channel to receive the same key factors and operation factors stored in the backend system.

[0043] In some examples, the communication module 1026 includes a near field communication circuit (not shown), which is configured to detect the acceptance terminal and send a transaction instruction to the acceptance terminal through the near field communication method during the activation of the NFC payment mode. Specifically, when the user is making a payment transaction, if the user chooses to use the NFC payment mode, the hard wallet is placed close to the acceptance terminal with the NFC sensing area of ​​the tag, so that the acceptance terminal can be detected, and then the near field communication circuit sends the transaction instruction to the acceptance terminal through the near field communication method, so that a short-distance contactless transaction can be realized.

[0044] The "secure channel" mentioned above can be a network channel between two entities (such as the backend and the hard wallet), which allows the two entities to communicate with each other through a secure channel without being eavesdropped by a third entity or disguised as one of the two expected entities participating in the secure communication by a third entity. By establishing a secure channel, sensitive information such as keys and operating factors can be securely transmitted between the two entities.

[0045] In some examples, the "secure channel" between the digital currency background system and the hard wallet 100 (communication module 1026) can be a communication channel that uses the acceptance terminal as the transmission medium to implement integrity protection of the key factor and the operation factor during the information transmission process. In other examples, the communication module 1026 of the hard wallet 100 can also include modules that support multiple communication network standards, such as 2G (GSM / GPRS), 3G (WCDMA / CDMA2000 / TD-SCDMA), 4G (LTE) and 5G and other different mobile communication network standards, so that the hard wallet can directly establish a communication channel with the digital currency background system, and during the transmission process, the key factor and the operation factor are also integrity protected. Of course, other "secure channel" methods can also be used, and this disclosure is not limited to this. "Integrity protection" can use the communication key agreed by both parties to sign or MAC calculation of the transmitted data, such as using the SM4 communication key to perform MAC protection on the data to be transmitted, so that the security of the transmitted data can be guaranteed. Of course, other methods can also be used to achieve integrity protection, and the embodiments of this disclosure are not limited.

[0046] For example, the power module 1023 can provide power for the hard wallet 100 and can be a lithium-ion battery or a metal-air battery, such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc.

[0047] For example, the biometric information collection module 1027, for example, includes a fingerprint module, which collects and / or stores fingerprint data of the wallet user through fingerprint collection technology. When verifying the user identity information, the collected fingerprint data can be sent to the sharing interface as parameter information.

[0048] For example, the controller 1025 may be a microcontroller unit (MCU) or a processor, configured to generate corresponding control instructions according to its internal control logic based on the information sent by the security element 1021 or the input element 1024. For example, the controller 1025 may call the display interface to display the payment code and transaction amount / balance information on the display 1022 through the control instructions.

[0049] In some examples, the display 1022 may be a visualization device equipped separately for the hard wallet, or a visualization device (such as a mobile phone screen, a tablet screen, etc.) provided by a carrier medium used as the hard wallet. The visualization device may be in the form of a screen, such as an electronic screen (such as a segment screen, a dot matrix screen, etc.), an ink screen, etc., as a part of the hard wallet.

[0050] For example, in at least one embodiment of the present disclosure, in addition, the display 1022 is configured to display the offline payment code, balance, current transaction amount, transaction time, and remaining power according to the control signal sent by the controller 1025.

[0051] like Figure 1 As shown, the security element 1021 includes a hard wallet logic application 110 and a plug-in application system 120 having a shared interface 122 and a hard wallet plug-in application 124. In this example, the software involved in the hard wallet is divided into two types of applications: the hard wallet logic application 110 and the hard wallet plug-in application 124. Among them, the hard wallet logic application 110 is used to execute the logic of digital currency instructions (such as transaction instructions or operation instructions), and is mainly configured to identify digital currency instructions and determine corresponding parameter information, call the shared interface 122 in the hard wallet plug-in application system 120, and pass the relevant parameter information to the hard wallet plug-in application 124. In addition, it is also responsible for the management of digital currency payment behavior, such as reading and writing account personalized information, wallet management, wallet transactions and wallet queries. The hard wallet plug-in application 124 includes multiple functional modules for executing wallet capabilities. In this plug-in application, it is mainly used to perform core calculations and store sensitive data.

[0052] As the demand for hard wallets increases, the hard wallet plug-in application will gradually enhance its wallet capabilities and develop new versions through developers. When a new version of the hard wallet plug-in application is installed in the hard wallet, the hard wallet logic application will automatically detect the new version of the hard wallet plug-in application and call the new version of the hard wallet plug-in application 124 for parameter calculation when executing transaction-related instructions.

[0053] Figure 2A The following is a block diagram of the plug-in application system for a digital currency hard wallet according to an embodiment of the present disclosure. The architecture is applicable to various types of hard wallets, such as a visual card hard wallet. Figure 2A To illustrate the composition of the application system of the digital currency hard wallet.

[0054] like Figure 2A As shown, the digital currency hard wallet 100 includes a hard wallet logic application 110 and a plug-in application system 120. The hard wallet logic application 110 and the plug-in application system 120 enhance or replace the basic hard wallet application in the traditional hard wallet. The hard wallet logic application 110 is connected to the shared interface 122 of the plug-in application system 120. The hard wallet plug-in application 124 is a plug-in built by the developer according to the actual needs of the hard wallet to realize various wallet capabilities of the hard wallet. Figure 3The three functional modules of the hard wallet plug-in application 124 are described in the figure, but it is understandable that there may be more, fewer or other functional modules. In one example, the functional modules in the plug-in application system define different implementation class functions. In order to adapt the hard wallet logic application 110 and the plug-in application system 120, the hard wallet logic application 110 needs to meet the calling rules of the implementation class functions of the plug-in application when designing and developing it.

[0055] For example, in some embodiments of the present disclosure, the hard wallet logic application 110 is configured to receive digital currency instructions and pass parameter information associated with the digital currency instructions to the shared interface 122 of the plug-in application system, wherein the digital currency instructions include transaction instructions and operation instructions.

[0056] For example, the hard wallet logic application 110 can be a hard wallet application, a wallet application used to manage and trade digital currency, mainly judging the received digital currency instructions and selecting the parameter information that needs to be passed to the shared interface 122. The transaction instructions and operation instructions generally involve instructions involved in the digital currency transaction process, mainly related to the capabilities of the hard wallet, such as payment code generation instructions in offline transaction mode, coin string generation and verification instructions in coin string transaction scenarios, and identity authentication instructions in transactions. These instructions can come from external devices, such as coin string mode collection instructions (an example of transaction instructions) and identity authentication instructions (an example of operation instructions) issued by the transaction counterpart (acceptance terminal, verification terminal), or they can be operation instructions issued by the hard wallet itself, such as instructions for obtaining offline payment codes. After obtaining these instructions, the logic application 110 first performs instruction recognition, separates the instruction name and parameter information (which can be in list form). Generally, different instructions may require different numbers and types of parameters. The separated parameters are then passed to the plug-in application 124 through the shared interface 122.

[0057] In addition, the hard wallet logic application 110 can also process the wallet user's personalized data. For example, after the user enters the PIN code through the input element 1024, the hard wallet logic application 110 stores the input PIN code in the data storage area of ​​the security element 1021, or after the user enters the fingerprint information through the biometric information collection module 1027, the hard wallet logic application 110 encrypts the input fingerprint information and also stores it in the data storage area of ​​the security element 1021. When the identity authentication is performed later, the pre-stored PIN code and fingerprint information ciphertext are obtained from the data storage area.

[0058] For example, in some embodiments of the present disclosure, the shared interface 122 is configured to provide an external access entry to the hard wallet plug-in application 124, receive parameter information passed in from the hard wallet logic application 110, and transmit the parameter information to the hard wallet plug-in application 124, wherein the parameter information is associated with the digital currency instruction received by the hard wallet logic application 110. The hard wallet plug-in application 124 is configured to identify and call the function module of the corresponding wallet capability according to the parameter information, process the parameter information based on the processing logic preset in the function module, and return the processing result to the hard wallet logic application 110 via the shared interface 122.

[0059] In addition, in some embodiments of the present disclosure, the shared interface 122 may also be configured with a shared storage area (not shown), which stores the parameter information passed in by the hard wallet logic application 110 and the processing results returned by the hard wallet plug-in application 124. By storing these data in the shared storage area, the shared interface can complete the two-way transmission of the parameter information and the processing result data, that is, the parameter information is transmitted to the hard wallet plug-in application 124 and the processing result is returned to the hard wallet logic application 110, and at the same time, the effective isolation of the hard wallet logic application 110 and the hard wallet plug-in application 124 can be ensured.

[0060] The hard wallet logic application 110 accesses the hard wallet plug-in application 124 through the pre-set shared interface 122, and the hard wallet plug-in application 124 implements wallet capabilities such as generating offline payment code information, generating and verifying coin strings, and verifying identity information. Through the shared interface 122, the logic application 110 and the plug-in application 120 are isolated from each other, ensuring that the core processing logic and sensitive data of the plug-in application 120 are invisible to the logic application 110. Moreover, after downloading and using a new version of the hard wallet plug-in application, the hard wallet logic application 110 does not need to perform special processing, and the previous information flow is still maintained, that is, the hard wallet logic application 110 transmits parameter information to the shared interface 122, and the new version of the hard wallet plug-in application identifies and calls the functional module of the corresponding wallet capability according to the parameter information, so that the complexity of the hard wallet logic application design is not increased.

[0061] It is easy to understand that the hard wallet plug-in application disclosed in this article is usually reusable. When different applications need the same or similar functions, the plug-in application can be used directly without redevelopment. Moreover, through the shared interface, the hard wallet plug-in application can be more easily integrated by different applications, thereby avoiding the situation of repeated development of the same function. This new hard wallet plug-in application solution with a plug-in framework can effectively reduce the cost of the hard wallet and improve the use value of the hard wallet.

[0062] In addition, in the disclosed embodiment, the hard wallet plug-in application 124, for example, implements class functions and adopts a modular design to divide different functional logics into independent modules, such as Figure 3 The first module 124A for generating an offline payment code, the second module 124B for generating and / or verifying a digital currency string, and the third module 124C for verifying identity information shown may also include modules for implementing other wallet capabilities, such as a functional module for generating identity information, which is not limited in the embodiments of the present disclosure. These functional modules are defined with different types of interfaces, and their internal processing logic is executed by calling these interfaces. Each functional module further has basic functions such as encryption processing, data conversion, and format checking, and the wallet capability processing logic of each module is implemented through these basic functions.

[0063] For example, in some embodiments of the present disclosure, these functional modules are configured to first determine whether the parameter format of the parameter information is correct after receiving the parameter information. If correct, the preset processing logic is executed to process the parameter information. For example, the parameter format includes length, tag value, BCD format and Hex format. After determining that the received parameter information meets the format requirements, the processing begins. If the parameter information does not meet the requirements, an error prompt code is returned to the logic application 110. With such a setting, it is important to verify whether the parameter format is a format supported by each functional module before continuing to execute the subsequent processing logic. This ensures that each functional module only processes data that meets expectations, avoiding abnormal application behavior due to data in the wrong format, and can also effectively defend against external attacks and enhance security.

[0064] For example, in some embodiments of the present disclosure, the first module 124A executes the following preset processing logic to generate an offline payment code: using a set algorithm, combined with a random factor, the key factor, calculation factor, time factor, event factor, operation factor and code information in the parameter information are operated to generate an offline payment code.

[0065] Figure 4 A schematic diagram of a method flow chart of generating an offline payment code by a first module according to at least one embodiment of the present disclosure is shown below. Figure 4 Of course, this method is just an example, and other processing logics can be used to generate offline payment codes, which is not limited in the present disclosure.

[0066] Step S310: The first module 124A receives parameter information associated with generating an offline payment code transmitted through the shared interface 122, wherein the parameter information includes a calculation factor associated with the first element, an operation factor associated with the second element, a key factor, a current time factor (UTC time) of the hard wallet, an event factor, and code information.

[0067] Among them, the event factor can be, for example, wallet account information, the calculation factor is set for different hard wallets, and the operation factor is set for different operating institutions (digital currency backend system). The random factor can be generated by the plug-in application according to the random number algorithm. By adding the random factor to calculate the payment code, different payment codes can be dynamically generated in the same step. In addition, the above factors involved in the calculation can be more or less, which is not limited in the embodiment of the present disclosure.

[0068] Step S320: The first module 124A determines whether the received parameter information is correct according to the set parameter format requirements, that is, whether the parameter information meets various formats, such as Hex format, BCD format, Tag format, and the set format length. If it meets, step S330 is executed, otherwise an error prompt code is returned.

[0069] Step S330: The first module 124A divides the UTC time in the parameter by the set step size (eg, 60 seconds) to obtain a time factor T for calculating the payment code.

[0070] Step S340: Utilize the set algorithm and combine the random factor to calculate the key factor, calculation factor, time factor T, event factor, operation factor and code information in the parameters to generate an offline payment code.

[0071] Specifically, in one example, based on encryption algorithms such as SM2, SM3, and SM4, the calculation factor, random factor, and time factor T are encrypted using a key factor to obtain a check code; the check code and the calculation factor are calculated to obtain a summary value, and the summary value is calculated with the event factor (such as an XOR operation) to obtain a user index; in a set order, the user index, code information, and check code are concatenated to obtain a string of offline payment codes as the code information of the offline payment code. Among them, the summary algorithm includes various existing algorithms, such as the MD5 algorithm, the SHA-2 algorithm, the MAC algorithm, and the SM3 algorithm. It is easy to understand that other algorithm processes can also be used to generate offline payment codes. The above is just an example.

[0072] Step S350: The first module 124A returns the generated offline payment code information to the shared interface 122, and the shared interface 122 further returns it to the hard wallet logic application 110. The hard wallet logic application 110 monitors the data returned by the shared interface 122. When an error prompt code is monitored, it indicates that the payment code generation fails. When a successful response code is monitored, the display interface is called to display the payment code.

[0073] For example, in some embodiments of the present disclosure, the second module 124B executes the following preset processing logic to generate a digital currency coin string: use a preset key to decrypt the encrypted coin string in the parameter information, and verify the correctness of the decrypted coin string format; after the verification, use its own private key and the payer identifier (generally the hard wallet identifier) ​​and transaction amount in the parameter information to generate a coin string sub-chain and generate a new coin string, and encrypt the new coin string.

[0074] For example, in some embodiments of the present disclosure, the second module 124B executes the following preset processing logic to verify the digital currency coin string: use the preset key to decrypt the encrypted coin string in the parameter information, and verify the correctness of the decrypted coin string format; after the verification is passed, the authenticity of the coin string is verified.

[0075] Figure 5A and Figure 5B Schematic diagrams of the method flow of generating coin string information and verifying coin string information by the second module according to at least one embodiment of the present disclosure are respectively shown.

[0076] like Figure 5A As shown, the method for the second module 124B to generate coin string information includes the following steps.

[0077] Step S410: The second module 124B receives parameter information transmitted by the hard wallet logic application 110 through the shared interface 122, where the parameter information includes transaction amount, acceptance terminal number, random number, payee ID, payee ID, encrypted currency string and other information.

[0078] Step S420: After receiving the parameter information, the second module 124B uses a preset key (such as SM4 key) to decrypt the encrypted coin string. Of course, before decrypting the coin string, it is possible to verify whether the format of the parameter information meets the requirements. For details, please refer to the above content and will not be repeated here.

[0079] Step S430: The second module 124B determines whether the format of the decrypted coin string information is correct. For example, the format determination of the coin string information may include: length, TLV format, signature and balance information. If the format is determined to be correct, step S440 is executed.

[0080] Step S440: The second module 124B uses its own public key to verify the authenticity of the coin string, and executes step S450 when the authenticity is verified. For example, the public key includes the public key (certificate) of this level and the public key (certificate) of the superior level. The public key of the superior level can verify the authenticity of the public key of this level. For example, the public key of this level is the public key of the user, and the public key of the superior level is the public key of the institution. At the same time, the public key of this level and the public key of the superior level can verify the corresponding signature in the coin string. The authenticity of the coin string can be verified by the public key of this level first, and then the authenticity of the coin string can be verified by the public key of the superior level. When both verifications are successful, it is determined that the coin string is authentic.

[0081] Step S450: The second module 124B generates a sub-chain signature using its own private key and the transaction amount and payer ID in the parameter information, and combines the sub-chain signature with the remaining parameter information (acceptance terminal number, random number, payee ID) to generate a new coin string information.

[0082] Step S460: The second module 124B returns the newly generated coin string information to the hard wallet logic application 110 through the shared interface 122.

[0083] like Figure 5B As shown, the method for the second module 124B to verify the coin string information includes the following steps.

[0084] Step S410: The second module 124B receives parameter information transmitted by the hard wallet logic application 110 through the shared interface 122, where the parameter information at least includes encrypted coin string information.

[0085] Step S420: After receiving the parameter information, the second module 124B uses a preset key (such as the SM4 key) to decrypt the encrypted coin string.

[0086] Step S430: The second module 124B determines whether the format of the decrypted coin string information is correct. For example, the format determination of the coin string information may include: length, TLV format, signature and balance information. If the format is determined to be correct, step S440 is executed.

[0087] Step S440: The second module 124B uses its own public key to verify the authenticity of the coin string, and executes step S550 if the verification is authentic.

[0088] Step S550: the second module 124B returns the verification result to the shared interface 122, and the hard wallet logic application 110 obtains the verification result through the shared interface 122.

[0089] For example, in some embodiments of the present disclosure, the third module 124C is configured to execute the following preset processing logic to verify the user identity information: use its own private key to sign the parameter information, and return the signature result and its own public key to the hard wallet logic application via the shared interface.

[0090] Figure 6 A schematic flow chart of a method for verifying identity information in a third module according to at least one embodiment of the present disclosure is shown.

[0091] Step S510: The third module 124C receives parameter information transmitted by the shared interface 122, and the parameter information includes: a random number of an acceptance terminal, an acceptance terminal identifier, a current time, and a hard wallet identifier.

[0092] Step S520: The third module 124C determines whether the parameter format is correct, including determining the correctness of the length and encoding format of the parameter information. If the determination is correct, step S530 is executed.

[0093] Step S530: The third module 124C signs the input parameters using its own private key (such as SM2 private key signature).

[0094] Step S540: The third module 124C returns the signature result and its own public key certificate to the hard wallet logic application 110 through the shared interface 122.

[0095] For example, in some embodiments of the present disclosure, the third module 124C is configured to execute the following preset processing logic to verify the identity information: compare the PIN code in the parameter information with the pre-stored PIN code, and determine whether the verification is successful based on the comparison result. In one example, the PIN code in the parameter information can be input by an external command or obtained by inputting an input element of the device itself (such as a digital key of a visual card).

[0096] For example, in some embodiments of the present disclosure, the third module 124C is configured to execute the following preset processing logic to verify the identity information: obtain the fingerprint information ciphertext stored in advance (for example, stored in the data storage area of ​​the security element) and decrypt it, compare the fingerprint information in the parameter information with the decrypted fingerprint information, and determine whether the verification is passed according to the comparison result. For example, the fingerprint information ciphertext can be pre-stored in the fingerprint module in the security element, and the fingerprint module can directly communicate internally with the plug-in application 124. The third module 124C in the plug-in application first decrypts the fingerprint information ciphertext, and then compares the decrypted fingerprint information with the fingerprint information in the input parameter to verify the authenticity of the identity information.

[0097] Figure 2B The process of the application control method of the digital currency hard wallet is also shown. Figure 2BAs shown, the control method includes the following steps.

[0098] First, the hard wallet logic application 110 receives the digital currency instruction, calls the shared interface 122, and transmits the associated parameter information to the shared interface 122 according to the digital currency instruction.

[0099] Next, the shared interface 122 provides an external access entry to the hard wallet plug-in application 124 , receives parameter information passed in by the hard wallet logic application 110 , and transmits the parameter information to the hard wallet plug-in application 124 .

[0100] Finally, the hard wallet plug-in application 124 identifies and calls the function module of the corresponding wallet capability according to the parameter information, processes the parameter information based on the processing logic preset in the function module, and returns the processing result to the hard wallet logic application 110 via the shared interface 122.

[0101] Figure 2B The method flow shown is basically similar to the aforementioned embodiment of the plug-in application system for a digital currency hard wallet, so it will not be repeated here. For relevant details, please refer to the description of the system embodiment part.

[0102] In order to better illustrate the embodiments of the present disclosure, the following describes the application scenario of a hard wallet with this new plug-in framework in actual digital currency transactions.

[0103] Fig. 7A A flowchart of an example application scenario according to at least one embodiment of the present disclosure is shown, specifically for an application scenario in which a hard wallet displays a payment code. The main execution subject is a hard wallet 100, which includes a control display module (consisting of a controller and a display) 130, a logic application 110, an access interface (shared interface) 122, and a plug-in application 124.

[0104] First, the visual hard wallet is triggered by buttons, fingerprints, touch screens, etc. to send a trigger message to display the payment code.

[0105] Then, after receiving the trigger information, the hard wallet controller sends a payment code acquisition instruction to the digital currency logic application 110 in the security chip SE, and operates the logic application 110 through the interface instruction to pass the required parameters (including calculation factors, operation factors, related keys, event factors, code information, etc.) to the plug-in application 124 by calling the pre-set payment code acquisition sharing interface 122. The plug-in application 124 calculates the incoming parameter information through its own internal payment code generation algorithm (such as SM2, SM3, SM4 and obfuscation algorithm, etc.) to generate a payment code, and adds random factors for calculation, so that different payment codes can be dynamically generated in the same step time.

[0106] Finally, the digital currency logic application 110 monitors the data returned by the access interface 122. When an error prompt code (such as 6A80) is obtained, it indicates that the response failed and no payment code was generated. When a successful response code (such as 9000) is obtained, the display interface is called to display the payment code.

[0107] Figure 7B The flowchart of an example application scenario according to at least one embodiment of the present disclosure is shown, and the scenario is for a hard wallet coin string transaction. In addition to the hard wallet 100, the main execution body also includes an acceptance terminal 200 and a backend 300.

[0108] First, the acceptance terminal 200 sends a selection instruction for the hard wallet application and feature negotiation (such as negotiating a transaction model with a coin string), and the hard wallet 100 returns a negotiation result according to the negotiation parameters.

[0109] Then, when the negotiation result is successful (the hard wallet is identified to support coin-string transactions), the acceptance terminal 200 initiates a payment instruction supporting coin-string transactions, and the payment instruction includes information such as the transaction amount, terminal number, random number, and payee identification;

[0110] Next, when the hard wallet 100 receives a transaction request, it identifies it as a transaction model with a coin string, and uses the transaction amount, terminal number, random number, payee ID, its own payer ID, encrypted coin string and other information as parameters to call the plug-in application 124 through the access interface 122.

[0111] Afterwards, when the plug-in application 124 receives the parameter information, it uses the preset key (such as the SM4 key) to decrypt the encrypted coin string and verify the correctness of the coin string format (such as length, TLV format, signature, balance). After the verification is passed, it uses its own private key to generate a coin string subchain and generate a new coin string, and uses the preset key to encrypt the coin string, and returns it to the logic application 110 through the access interface 122;

[0112] Finally, the logic application 110 returns the generated new coin string to the acceptance terminal 200, and the acceptance terminal 200 initiates a transaction to the backend 300, and the transaction backend 300 uses the same preset key as the plug-in application 124 to decrypt the coin string and complete the payment transaction;

[0113] The above transactions can also be completed by the acceptance terminal 200 and the hard wallet plug-in application 124 generating temporary encryption and decryption keys to complete offline transactions between the acceptance terminal 200 and the hard wallet 100. For example, the two parties exchange public key certificates and verify the legitimacy of the other party's public key certificate, encrypt random data with the other party's public key and pass it to the other party, each uses the private key to decrypt the received encrypted random number, and finally combines the decrypted random number and other information into a temporary key, and then uses the temporary key to encrypt and transmit transaction data to complete the transaction.

[0114] Figure 7C The flowcharts of the example application scenarios according to at least one embodiment of the present disclosure are respectively shown, and the scenario is for hard wallet identity verification. In addition to the hard wallet 100, the main execution body also includes a verification terminal 400.

[0115] First, the verification terminal 400 sends a selection instruction for the hard wallet application and feature negotiation, and the hard wallet 100 returns the negotiation result according to the negotiation parameters. If the hard wallet is identified to support identity authentication, the verification terminal 400 sends a verification instruction. The hard wallet 100 receives the identity authentication instruction, and the instruction content includes the terminal random number, terminal identification, current time, etc.

[0116] Then, the hard wallet logic application 110 passes the terminal random number, the terminal identifier, the current time, and the hard wallet identifier as parameters to the plug-in application 124 by calling the shared interface 122 .

[0117] Next, the plug-in application 124 determines the correctness of the length and encoding format of the passed in parameters, signs the passed in parameters using its own private key (such as SM2 private key signature), and returns the signature result and its own public key certificate to the logic application 110 through the access interface 122 .

[0118] Afterwards, the logic application 110 returns the parameters, public key certificate, and signature to the verification terminal 400 that sent the instruction.

[0119] Finally, the verification terminal 400 verifies the returned public key certificate using the superior public key. After the verification is successful, the public key in the public key certificate is used to verify the signature returned by the instruction. After both the certificate and the signature are verified, the identity authentication is successful.

[0120] It should be noted that the above application scenarios are merely exemplary, in order to facilitate description of one or more aspects of the present disclosure in specific scenarios, but these aspects are not necessary, and various modifications may be made to the application scenarios, which are not limited to the embodiments of the present disclosure.

[0121] At least some embodiments of the present disclosure also provide an electronic device. Figure 8 A schematic diagram of an electronic device 700 according to at least one embodiment of the present disclosure is shown.

[0122] like Figure 8As shown, the electronic device 700 includes one or more processors 710 and a memory 720. The memory 720 includes one or more computer program modules 721. The one or more computer program modules 721 are stored in the memory 720 and are configured to be executed by the processor 710. The one or more computer program modules 721 include instructions for executing the method according to at least one embodiment of the present disclosure and its additional aspects. When it is executed by the processor 710, one or more steps of the method according to at least one embodiment of the present disclosure and its additional aspects can be executed. The memory 720 and the processor 710 can be interconnected through a bus system and / or other forms of connection mechanisms (not shown). For example, the bus can be a peripheral component interconnect standard (PCI) bus or an extended industrial standard architecture (EISA) bus, etc. The communication bus can be divided into an address bus, a data bus, a control bus, etc.

[0123] Exemplarily, the processor 710 may be a central processing unit (CPU), a digital signal processor (DSP), or other forms of processing units having data processing capabilities and / or program execution capabilities, such as a field programmable gate array (FPGA), etc. The processor 710 may be a general-purpose processor or a dedicated processor, and may control other components in the electronic device 700 to perform desired functions.

[0124] Exemplarily, the memory 720 may include any combination of one or more computer program products, and the computer program product may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. Volatile memory may include, for example, random access memory (RAM) and / or cache memory (cache), etc. Non-volatile memory may include, for example, read-only memory (ROM), hard disk, erasable programmable read-only memory (EPROM), portable compact disk read-only memory (CD-ROM), USB memory, flash memory, etc. One or more computer program modules 721 may be stored on the computer-readable storage medium, and the processor 710 may run one or more computer program modules 621 to implement various functions of the electronic device 700. The computer program module includes a plurality of computer-executable instructions. Various applications and various data, as well as various data used and / or generated by the application, etc. may also be stored in the computer-readable storage medium.

[0125] For example, the electronic device 700 may also include input devices such as a touch screen, a touchpad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; output devices such as a liquid crystal display, a speaker, a vibrator, etc.; storage devices such as a magnetic tape, a hard disk (HDD or SDD), etc.; and communication devices such as a network interface card such as a LAN card, a modem, etc. may also be included. The communication device may allow the electronic device 700 to communicate with other devices wirelessly or by wire to exchange data, and perform communication processing via a network such as the Internet. The drive is connected to the I / O interface as needed. Removable storage media, such as a disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., are installed on the drive as needed so that the computer program read therefrom is installed into the storage device as needed.

[0126] For example, the electronic device 700 may further include an external device interface (not shown in the figure), etc. The external device interface may be various types of interfaces, such as a USB interface, a lightning interface, etc. The communication device may communicate with a network and other devices through wireless communication, such as the Internet, an intranet and / or a wireless network such as a cellular phone network, a wireless local area network (LAN), and / or a metropolitan area network (MAN). Wireless communication may use any of a variety of communication standards, protocols, and technologies, including but not limited to a global system for mobile communications (GSM), an enhanced data GSM environment (EDGE), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wi-Fi (e.g., based on IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, and / or IEEE 802.11n standards), voice transmission over Internet protocol (VoIP), Wi-MAX, protocols for email, instant messaging, and / or short message service (SMS), or any other suitable communication protocol.

[0127] The electronic device 700 may be, for example, a system on a chip (SOC) or a device including the SOC, for example, a mobile phone, a tablet computer, a laptop computer, an e-book, a game console, a television, a digital photo frame, a navigator, a home appliance, a communication base station, an industrial controller, a server, or any other device, or a combination of any data processing device and hardware, which is not limited by the embodiments of the present disclosure. The specific functions and technical effects of the electronic device 700 may refer to the description of the method and its additional aspects according to at least one embodiment of the present disclosure, and will not be repeated here.

[0128] Fig. 9 A schematic diagram of a computer-readable medium 800 is shown, in accordance with at least one embodiment of the present disclosure.

[0129] like Figure 8 As shown, a computer readable medium 800 stores computer instructions 810, which, when executed by a processor, perform one or more steps of the method described above and its additional aspects.

[0130] Exemplarily, when the program code is read by a computer, the computer may execute the program code stored in the computer storage medium to implement, for example, one or more steps of the method according to at least one embodiment of the present disclosure and additional aspects thereof.

[0131] Exemplarily, the computer-readable medium may include a memory card of a smart phone, a storage component of a tablet computer, a hard disk of a personal computer, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a portable compact disk read-only memory (CD-ROM), flash memory, and other computer-readable media or any combination thereof.

[0132] At least some of the embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the embodiments can be referenced to each other.

[0133] It should be noted that, in this article, relational terms such as first, second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. The terms "include", "comprises", or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article, or device including a series of elements includes not only those elements, but also further includes other elements not explicitly listed, or further includes elements inherent to such process, method, article, or device. In the absence of further restrictions, the elements defined by the statement "includes..." do not exclude the presence of other identical elements in the process, method, article, or device including the elements.

[0134] There are a few points to note about this disclosure:

[0135] (1) The drawings of the embodiments of the present disclosure only relate to the structures related to the embodiments of the present disclosure, and other structures may refer to the general design.

[0136] (2) In the absence of conflict, the embodiments of the present disclosure and the features therein may be combined with each other to obtain new embodiments.

[0137] The above description is merely an exemplary embodiment of the present disclosure and is not intended to limit the protection scope of the present disclosure. The protection scope of the present disclosure is determined by the appended claims.

Claims

1. A plug-in application system for a digital currency hard wallet, the system comprising a shared interface and a hard wallet plug-in application, wherein: The shared interface is configured to provide an external access entry to the hard wallet plug-in application, receive parameter information passed in from the hard wallet logic application, and transmit the parameter information to the hard wallet plug-in application, wherein the parameter information is associated with a digital currency instruction received by the hard wallet logic application, and the digital currency instruction includes a transaction instruction and an operation instruction; The hard wallet plug-in application is configured to identify and call a functional module of a corresponding wallet capability according to the parameter information, process the parameter information based on a processing logic preset in the functional module, and return a processing result to the hard wallet logic application via the shared interface.

2. The plug-in application system according to claim 1, wherein: The functional modules include at least one of the following: a first module for generating an offline payment code, a second module for generating and / or verifying a digital currency string, and a third module for verifying identity information.

3. The plug-in application system according to claim 2, wherein: The functional module is configured to determine whether the parameter format of the parameter information is correct, and if correct, execute a preset processing logic to process the parameter information.

4. The plug-in application system according to claim 2, wherein: The first module is configured to execute the following preset processing logic to generate an offline payment code: using a set algorithm, combined with a random factor, a key factor, a calculation factor, a time factor, an event factor, an operation factor and code information in the parameter information are operated to generate an offline payment code.

5. The plug-in application system according to claim 2, wherein: The second module is configured to execute the following preset processing logic to generate a digital currency string: decrypt the encrypted coin string in the parameter information using a preset key, and verify the correctness of the format of the decrypted coin string; After verification, the coin string subchain is generated using its own private key and the payer identification and transaction amount in the parameter information, and a new coin string is generated, and the new coin string is encrypted.

6. The plug-in application system according to claim 2 or 5, wherein: The second module is configured to execute the following preset processing logic to verify the digital currency coin string: use the preset key to decrypt the encrypted coin string in the parameter information, and verify the correctness of the decrypted coin string format; after the verification is passed, verify the authenticity of the coin string.

7. The plug-in application system according to claim 2, wherein: The third module is configured to execute the following preset processing logic to verify the identity information: use its own private key to sign the parameter information, and return the signature result and its own public key certificate to the hard wallet logic application via the shared interface.

8. The plug-in application system according to claim 2 or 7, wherein: The third module is configured to execute the following preset processing logic to verify the identity information: The PIN code in the parameter information is compared with the pre-stored PIN code, and whether the verification is successful is determined based on the comparison result.

9. The plug-in application system according to claim 2, 7 or 8, wherein: The third module is configured to execute the following preset processing logic to verify the identity information: The pre-stored fingerprint information ciphertext is obtained and decrypted, the fingerprint information in the parameter information is compared with the decrypted fingerprint information, and whether the verification is passed is determined according to the comparison result.

10. The plug-in application system according to claim 1, wherein: The shared interface is also configured with a shared storage area, which stores parameter information passed in by the hard wallet logic application and processing results returned by the hard wallet plug-in application.

11. A digital currency hard wallet, comprising: The plug-in application system as claimed in any one of claims 1 to 10; as well as The hard wallet logic application is configured to receive digital currency instructions and pass parameter information associated with the digital currency instructions to the shared interface of the plug-in application system, wherein the digital currency instructions include transaction instructions and operation instructions.

12. A method for controlling an application of a digital currency hard wallet, wherein the hard wallet comprises a hard wallet logic application and a plug-in application system having a shared interface and a hard wallet plug-in application, the method comprising: The hard wallet logic application receives a digital currency instruction, and transmits associated parameter information to the shared interface according to the digital currency instruction, wherein the digital currency instruction includes a transaction instruction and an operation instruction; The shared interface provides an external access entry to the hard wallet plug-in application, receives parameter information passed in by the hard wallet logic application, and transmits the parameter information to the hard wallet plug-in application; The hard wallet plug-in application identifies and calls a functional module of the corresponding wallet capability according to the parameter information, processes the parameter information based on a processing logic preset in the functional module, and returns a processing result to the hard wallet logic application via the shared interface.

13. An electronic device comprising: one or more processors; a memory storing one or more computer program modules, The one or more computer program modules are configured to be executed by the one or more processors to implement the method according to claim 12.

14. A computer-readable medium storing computer-executable instructions, wherein: When the computer executable instructions are executed by one or more processors, the method according to claim 12 is implemented.

Images