Consignment transaction method, transaction device and storage medium

Abstract

The invention provides an entrusted transaction method, transaction equipment and a storage medium, the entrusted transaction method is applied to the transaction equipment, and the entrusted transaction method comprises the following steps: a first transaction application in the transaction equipment responds to a received instruction used for indicating execution of a transaction event, generating a transaction request for instructing a commission to execute the transaction event; judging whether transaction information indicated by the transaction request meets a preset condition or not; and if transaction information indicated by the transaction request satisfies a preset condition, entrusting a second transaction application in the transaction device to perform transaction processing for the transaction event so as to execute the transaction event. According to the method, the practicability and efficiency of the transaction in multiple scenes are improved, and the experience of the user during the transaction is further improved.

Description

Technical Field

[0001] The present application relates to the technical field of electronic currency transaction, and in particular to a commissioned transaction method, transaction equipment and storage medium. Background Art

[0002] There have been many explorations of digital currency in the field of financial payment. However, transactions of digital currency in application scenarios such as public transportation, subways, and small payments are subject to many restrictions on digital currency transactions in application scenarios. For example, the one-card application in business applications is a mainstream transaction application scenario. When users use the one-card application to conduct transactions involving digital currency, such transactions will create transaction barriers.

[0003] At present, if digital currency is to be used in multiple application scenarios, it is usually necessary to transform at least one of the payment equipment, acceptance equipment and back-end systems in the upstream and downstream of the industry. This will result in high transformation costs, resource redundancy and long processing cycles, which will give users a poor experience when conducting transactions, thereby reducing the practicality and efficiency of transactions in multiple scenarios. Summary of the invention

[0004] In view of this, the purpose of the present application is to provide a delegated transaction method, transaction equipment and storage medium. Under the premise of no or little modification to the acceptance end equipment, by supporting a transaction device with multiple transaction applications including digital currency applications or business applications at the same time, when the transaction request generated by the first transaction application in response to the transaction instruction meets the preset conditions, the transaction device can entrust the second transaction application to conduct the transaction through internal interaction without relying on the network, thereby organically combining the two transaction applications in the transaction device, improving the practicality and efficiency of transactions in multiple scenarios, and thus improving the user experience when conducting transactions.

[0005] The present application embodiment provides a commissioned transaction method, which is applied to a transaction device. The commissioned transaction method includes:

[0006] The first transaction application in the transaction device generates a transaction request for instructing an agent to execute the transaction event in response to the received instruction for instructing the execution of the transaction event;

[0007] Determining whether the transaction information indicated by the transaction request meets a preset condition;

[0008] If the transaction information indicated by the transaction request meets the preset condition, then for the transaction event, the second transaction application in the transaction device is entrusted to perform transaction processing to execute the transaction event.

[0009] Furthermore, the first transaction application in the transaction device generates a transaction request for instructing the agent to execute the transaction event in response to the received instruction for instructing the execution of the transaction event, including:

[0010] The first transaction application parses the received instruction for instructing to execute the transaction event, and determines the initialization transaction instruction for instructing to execute the transaction event;

[0011] The first transaction application generates security data for secure access of the transaction device by performing a security check on the initialization transaction instruction, and sends the security data to the acceptance device;

[0012] The first transaction application receives a data cache instruction issued by the acceptance device based on the security data, and generates a transaction request for instructing the agent to execute the transaction event by performing standardized cache processing on the application data included in the data cache instruction.

[0013] Furthermore, the first transaction application generates security data for secure access by the transaction device by performing a security check on the initialization transaction instruction, including:

[0014] The first transaction application determines whether the key index number included in the initialization transaction instruction is supported by data corresponding to the transaction device;

[0015] If the key index number is supported by the data corresponding to the transaction device, the first transaction application determines whether the transaction device is gray-locked;

[0016] If the transaction device is not gray-locked, the first transaction application determines whether the transaction information indicated by the initialization transaction instruction satisfies the transaction requirements of the first transaction application and the second transaction application respectively;

[0017] If the transaction information meets the transaction requirements of the first transaction application and the second transaction application respectively, the first transaction application generates security data for secure access by the first transaction application.

[0018] Furthermore, the first transaction application generates a transaction request for instructing the agent to execute the transaction event by performing standardized cache processing on the application data included in the data cache instruction, including:

[0019] The first transaction application determines whether at least one of the short file identifier, the transaction type identifier, the record number and the data field included in the application data meets the corresponding predetermined specification conditions;

[0020] If so, the first transaction application caches the application data and sends a data cache response generated by the data cache to the receiving device;

[0021] The first transaction application generates a transaction request for instructing an agent to execute the transaction event in response to the instruction issued by the receiving device to accept the data cache response.

[0022] Furthermore, the preset condition includes: the transaction request is valid and the transaction information indicated by the transaction request satisfies at least one of a plurality of predetermined transaction conditions.

[0023] Furthermore, the method further comprises:

[0024] If the transaction information does not meet the preset condition, then for the transaction event, entrust the first transaction application in the transaction device to perform transaction processing to execute the transaction event.

[0025] Furthermore, after executing the transaction event, the method further includes:

[0026] According to the transaction data and the transaction result generated by executing the transaction event, the transaction data and the transaction result are sent to the acceptance device;

[0027] A feedback signal indicating that the transaction result has been verified by the acceptance device is received, and the transaction data and the transaction result are asynchronously sent to a background server corresponding to the transaction device.

[0028] Furthermore, the predetermined specification conditions include at least one of the following items: a record with the same character value as the short file identifier exists in the transaction device, a transaction-specific file with the same character value as the transaction type identifier exists in the transaction device, the lock flag byte corresponding to the record number is not set, and the length of the data field is not greater than the length of the record corresponding to the transaction-specific file in the transaction device.

[0029] Furthermore, the multiple predetermined transaction conditions include: the balance of the first transaction application included in the transaction information is less than or equal to a preset balance threshold, the transaction amount included in the transaction information is greater than a preset transaction threshold, and the transaction method included in the transaction information specifies that the transaction be conducted through a second transaction application.

[0030] Further, the transaction communication environment of the transaction device and the acceptance device includes a first transaction communication environment and / or a second transaction communication environment;

[0031] The first transaction communication environment refers to an environment where the network or signal connection between the transaction device and the acceptance device is normal;

[0032] The second transaction communication environment refers to an environment in which the network or signal connection between the transaction device and / or the acceptance device is abnormal; wherein, the connection abnormality means that the network connection between the transaction device and / or the acceptance device is disconnected or the signal strength is unable to support normal communication between the transaction device and / or the acceptance device.

[0033] The embodiment of the present application further provides a transaction device, the transaction device comprising a security unit; the security unit comprises:

[0034] A first transaction application unit, configured to execute the first transaction application in the transaction device to generate a transaction request for instructing an agent to execute the transaction event in response to a received instruction for instructing the execution of the transaction event;

[0035] A determination unit, configured to determine whether the transaction information indicated by the transaction request satisfies a preset condition;

[0036] The second transaction application unit is configured to entrust the second transaction application in the transaction device to perform transaction processing for the transaction event if the transaction information indicated by the transaction request meets a preset condition, so as to execute the transaction event.

[0037] Further, when the first transaction application unit is used to execute the first transaction application in the transaction device in response to the received instruction for instructing to execute the transaction event, generating a transaction request for instructing the agent to execute the transaction event, the first transaction application unit is used to:

[0038] The first transaction application parses the received instruction for instructing to execute a transaction event, and determines an initialization transaction instruction;

[0039] By performing a security check on the initialization transaction instruction, generating security data for secure access of the transaction device, and sending the security data to the acceptance device;

[0040] A data cache instruction issued by the acceptance device based on the security data is received, and a transaction request for instructing the agent to execute the transaction event is generated by performing standardized cache processing on the application data included in the data cache instruction.

[0041] Furthermore, when the first transaction application unit is used to generate security data for secure access by the transaction device by performing a security check on the initialization transaction instruction, the first transaction application unit is used to:

[0042] Determining whether the key index number included in the initialization transaction instruction is supported by data corresponding to the transaction device;

[0043] If the key index number is supported by the data corresponding to the transaction device, it is determined whether the transaction device is gray-locked;

[0044] If the transaction device is not gray-locked, determining whether the transaction information indicated by the initialization transaction instruction satisfies the transaction requirements of the first transaction application and the transaction requirements of the second transaction application respectively;

[0045] If the transaction information satisfies the transaction requirements of the first transaction application and the second transaction application respectively, security data for secure access by the first transaction application is generated.

[0046] Furthermore, when the first transaction application unit is used to generate a transaction request for instructing an agent to execute the transaction event by performing standardized cache processing on the application data included in the data cache instruction, the first transaction application unit is used to:

[0047] Determining whether at least one of the short file identifier, the transaction type identifier, the record number and the data field included in the application data meets corresponding predetermined specification conditions;

[0048] If so, the application data is cached, and a data cache response generated by the data cache is sent to the receiving device.

[0049] In response to the instruction issued by the receiving device accepting the data cache response, a transaction request for instructing the agent to execute the transaction event is generated.

[0050] Furthermore, the second transaction application unit is further used for:

[0051] If the transaction information does not meet the preset condition, then for the transaction event, entrust the first transaction application in the transaction device to perform transaction processing to execute the transaction event.

[0052] Furthermore, the transaction device further includes a communication module, and the communication module is used to:

[0053] According to the transaction data and transaction result generated by executing the transaction event, the transaction data and the transaction result are sent to the acceptance device;

[0054] A feedback signal indicating that the transaction result has been verified by the acceptance device is received, the transaction event is determined to be completed, and the transaction data and the transaction result are asynchronously sent to a background server corresponding to the transaction device.

[0055] Furthermore, the transaction device also includes an MCU module, an NFC communication unit, a power supply system and a USB interface;

[0056] The power supply system is connected to the MCU module, the security unit, the communication module and the USB interface respectively; the NFC communication unit is connected to the communication module; and the USB interface is connected to the communication module.

[0057] An embodiment of the present application also provides an electronic device, comprising: a processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor and the memory communicate through the bus, and when the machine-readable instructions are executed by the processor, the steps of the above-mentioned entrustment transaction method are performed.

[0058] An embodiment of the present application also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the entrustment transaction method as described above are executed.

[0059] The embodiments of the present application provide a delegated transaction method, a transaction device, and a storage medium. The delegated transaction method is applied to a transaction device. The delegated transaction method includes: a first transaction application in the transaction device generates a transaction request for instructing an agent to execute the transaction event in response to a received instruction for instructing the execution of the transaction event; determining whether the transaction information indicated by the transaction request meets a preset condition; if the transaction information indicated by the transaction request meets the preset condition, entrusting a second transaction application in the transaction device to perform transaction processing for the transaction event to execute the transaction event.

[0060] Compared with the prior art method of modifying the payment equipment, acceptance machines or back-end systems of the upstream and downstream industries, under the premise of no or little modification of the acceptance machines, by supporting transaction devices with multiple transaction applications including digital currency applications or business applications at the same time, when the transaction request generated by the first transaction application in response to the transaction instruction meets the preset conditions, the transaction device can entrust the second transaction application to conduct the transaction through internal interaction without relying on the network, thereby organically combining the two transaction applications in the transaction device, improving the practicality and efficiency of transactions in multiple scenarios, and thus improving the user experience when conducting transactions.

[0061] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, preferred embodiments are specifically cited below and described in detail with reference to the attached drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0062] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0063] Figure 1 One of the flow charts of a commission transaction method provided in an embodiment of the present application;

[0064] Figure 2 The second flowchart of a commissioned transaction method provided in an embodiment of the present application;

[0065] Figure 3 One of the structural schematic diagrams of a transaction device provided in an embodiment of the present application;

[0066] Figure 4 This is a second structural diagram of a transaction device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0067] To make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the technical scheme in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. The components of the embodiments of the present application usually described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application claimed for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, each other embodiment obtained by those skilled in the art without making creative work belongs to the scope of protection of the present application.

[0068] Research has found that at present, if digital currency is to be accepted in business applications such as the one-card application, it is usually necessary to transform the payment equipment, acceptance machines or back-end systems upstream and downstream of the industry, which will cause problems such as high transformation costs, resource redundancy and long processing cycles.

[0069] In addition, digital currency payment devices and business application devices cannot be fully compatible with transactions on acceptance machines. For example, in the solution of loading digital currency applications and business applications on a transaction card proposed to address the above problem, each application can only execute transactions in its own application field, making it impossible for digital currency applications and business applications to communicate with each other in terms of accounts and transactions. The user experience when conducting transactions is poor, which reduces the practicality and efficiency of transactions in multiple scenarios.

[0070] Based on this, the embodiment of the present application provides a method for entrusting transactions. Under the premise of not modifying or minimally modifying the acceptance-end equipment, by simultaneously supporting transaction devices including transaction applications such as digital currency applications or business applications, when the transaction request generated by the first transaction application in response to the transaction instruction meets the preset conditions, the transaction device can entrust the second transaction application to conduct the transaction through internal interaction without relying on the network, thereby organically combining the two transaction applications in the transaction device, improving the practicality and efficiency of transactions in multiple scenarios, and thereby improving the user experience when conducting transactions.

[0071] See also Figure 1 , Figure 1 This is one of the flow charts of a commissioned transaction method provided in the embodiment of the present application. Figure 1 As shown in , the entrustment transaction method provided in the embodiment of the present application is applied to a transaction device, including:

[0072] S101. In response to a received instruction for instructing execution of a transaction event, a first transaction application in the transaction device generates a transaction request for instructing an agent to execute the transaction event.

[0073] It should be noted that the transaction device is installed with the first transaction application and the second transaction application, and has transaction permissions for the first transaction application and the second transaction application; the transaction device can control transaction communications between the first transaction application and the second transaction application; exemplarily, the transaction device is suitable for transaction behaviors for various transaction scenarios such as electronic consumer cards, smart cards or electronic certificates.

[0074] Among them, the first transaction application is set in the transaction device and can be applied to the transaction application in the transaction scenario. The first transaction application can include business applications in different scenarios, such as: one-card application, smart card application, electronic certificate application, etc.; specifically, the common one-card application can realize transaction functions such as telephone IC card, identity IC card, transportation IC card, bank transaction card and comprehensive consumption card in multiple scenarios.

[0075] Here, the transaction communication environment of the transaction device or the acceptance device includes a first transaction communication environment or a second transaction communication environment; the first transaction communication environment refers to an environment in which the network or signal connection between the transaction device and the acceptance device is normal; the second transaction communication environment refers to an environment in which the network or signal connection between the transaction device and the acceptance device is abnormal.

[0076] The abnormal connection means that the network connection between the transaction device and / or the acceptance device is disconnected or the signal strength is unable to support the normal communication between the transaction device and / or the acceptance device.

[0077] Here, network connection refers to a method of network communication through the Internet, cellular network, etc., and signal connection refers to a method of network communication through point-to-point short-range communication, such as Bluetooth communication, NFC communication, WIFI communication, two-way mobile communication, etc.

[0078] Specifically, the network connection disconnection between the transaction device and / or the acceptance device means that the mobile Internet connection between the transaction device and / or the acceptance device is in a disconnected state; the signal strength between the transaction device and / or the acceptance device refers to the strength of the signal in the wireless transmission network when the transaction device and / or the acceptance device conducts short-distance communication. Signal connection abnormality may be insufficient signal strength or signal disconnection.

[0079] In one possible implementation of the present application, the second transaction application includes but is not limited to digital currency applications and digital banking applications, etc.; wherein the second transaction application supports dual offline transactions, that is, transaction events can still be executed when the transaction device is in an environment where the network is disconnected or the signal is poor.

[0080] For example, assume that a transaction device has a gas card application (i.e., the first transaction application) and a bank card application (i.e., the second transaction application). The bank card application stores the key that was written into the card when the bank issued the card. When the gas card application receives a recharge command from the bank, it generates a transaction request. To verify the correctness of the transaction request, the bank card application can be entrusted to verify the command through delegated verification, thereby executing the specific instructions of the transaction event.

[0081] Here, after the transaction device receives the instruction for instructing to execute a transaction event, the first transaction application in the transaction device responds to the instruction to perform subsequent operations.

[0082] In this step, the first transaction application in the transaction device serves as the execution subject. First, the first transaction application parses the received instructions for instructing the execution of the transaction event and determines the initialization transaction instruction. Then, by performing a security check on the initialization transaction instruction, security data for secure access by the transaction device is generated, and the security data is sent to the acceptance device. Finally, by performing normalized caching processing on the application data included in the data caching instruction issued by the acceptance device based on the security data, a transaction request for instructing the agent to execute the transaction event is generated.

[0083] In one possible implementation of the present application, transaction events include, but are not limited to, transaction behavior events such as consumption, entrusted signature, signature verification, encryption, decryption, and entrusted transaction.

[0084] In one implementation of the present application, during specific implementation, step S101 may include:

[0085] S1011. The first transaction application parses the received instruction for instructing the execution of a transaction event, and determines an initialization transaction instruction for instructing the execution of a transaction event.

[0086] In this step, the first transaction application in the transaction device acts as the execution subject. The first transaction application parses the received instruction for instructing the execution of the transaction event, determines the initialization transaction instruction for instructing the execution of the transaction event, and continues the transaction event through interaction with the acceptance device terminal.

[0087] Here, the initialization transaction instruction includes a key index number used for secure transactions, a status of a transaction device, transaction information, and the like.

[0088] Among them, the key index number is a unique identifier assigned in the key transaction management system, which is used to manage and track the keys of the transaction process; the status of the transaction device refers to the status information of whether the transaction device is grayed out; transaction information refers to information related to the transaction, such as the transaction object, transaction amount, transaction method, etc.

[0089] For example, a user needs to use a transaction device to implement a transaction event in which a public transportation IC card is used for consumption at a subway station. At this time, the first transaction application in the transaction device may generate an initialization transaction instruction in response to the transaction event received by the transaction device. The initialization transaction instruction may include a key index number, status information on whether the transaction device is locked, a transaction object (in this example, the subway station), and a transaction amount. Here, the transaction object and transaction amount are transaction information.

[0090] S1012. The first transaction application generates security data for secure access by the transaction device by performing a security check on the initialization transaction instruction, and sends the security data to the acceptance device.

[0091] Here, the security check on the initialization transaction instruction includes the first transaction application checking whether the data corresponding to the transaction device is supported by the key index number included in the initialization transaction instruction, the first transaction application performing a gray lock status check on the transaction device status represented by the transaction device information included in the initialization transaction instruction, and the first transaction application determining whether the transaction information indicated by the initialization transaction instruction meets the transaction requirements of the first transaction application and the transaction requirements of the second transaction application respectively.

[0092] In this step, after the first transaction application verifies the step of performing security check and passes the verification, the first transaction application generates security data for the first transaction application to perform secure access.

[0093] In one implementation of the present application, during specific implementation, step S1012 may include:

[0094] S10121. The first transaction application determines whether the key index number included in the initialization transaction instruction is supported by data corresponding to the transaction device.

[0095] In this step, when it is specifically implemented, first, the first transaction application in the transaction device determines the key index number included in the initialization transaction instruction; then, the supportable key index number corresponding to the transaction event is determined in the security key data corresponding to the transaction device; finally, it is determined whether the key index number matches the supportable key index number corresponding to the transaction event, so as to determine whether the key index number is supported by the data corresponding to the transaction device. If they match, the key index number is supported by the data corresponding to the transaction device; if they do not match, the key index number is not supported by the data corresponding to the transaction device.

[0096] For example, the key index number included in the initialization transaction instruction is YKT35H807. If the YKT-type security data corresponding to the transaction device includes YKT35H807, the key index number is supported by the data corresponding to the transaction device.

[0097] S10122: If the key index number is supported by data corresponding to the transaction device, the first transaction application determines whether the transaction device is gray-locked.

[0098] Here, the gray lock refers to a special application temporary lock of the transaction device. Under this special temporary application lock, the transaction device refuses to perform any transaction operation that may cause changes in the transaction security content in the first transaction application until the transaction device successfully releases the gray lock.

[0099] In this step, if the key index number included in the initialization transaction instruction is supported by the data corresponding to the transaction device, the first transaction application in the transaction device determines whether the transaction device is gray-locked according to the status information of whether the transaction device is gray-locked included in the initialization transaction instruction.

[0100] For example, the trading device will indicate whether it is in gray lock state in the initialization trading instruction. If the gray lock state code is 1, the trading device is gray locked; if the gray lock state code is 0, the trading device is not gray locked.

[0101] Furthermore, if the key index number included in the initialization transaction instruction is not supported by the data corresponding to the transaction device, the transaction event will be terminated immediately to ensure the security and reliability of the transaction.

[0102] S10123. If the transaction device is not gray-locked, the first transaction application determines whether the transaction information indicated by the initialization transaction instruction meets the transaction requirements of the first transaction application and the second transaction application respectively.

[0103] It should be noted that this step is used to determine whether the transaction information meets the transaction requirements of the transaction application. Since the transaction device supports transactions of two transaction applications, when the executed transaction information is smart card consumption, the consumption transaction amount value needs to be compared with the balance value corresponding to the first transaction application and the balance value corresponding to the second transaction application, respectively.

[0104] In this step, if the transaction device is judged to be not gray-locked, the first transaction application in the transaction device compares the transaction information indicated by the initialization transaction instruction with the transaction requirements of the first transaction application and the transaction requirements of the second transaction application respectively, and then determines whether the transaction amount value indicated by the initialization transaction instruction meets the transaction requirements of the first transaction application and the transaction requirements of the second transaction application respectively based on the comparison result.

[0105] Exemplarily, when the executed transaction behavior is smart card consumption, the transaction requirements of the first transaction application and the second transaction application are that the transaction amount value must be greater than or equal to the balance value corresponding to the first transaction application and the balance value corresponding to the second transaction application.

[0106] For example, if the transaction amount is 20 yuan, the balance value corresponding to the first transaction application is 15 yuan, and the balance value corresponding to the second transaction application is 22 yuan, then the transaction amount judgment condition is not met; if the transaction amount is 10 yuan, the balance value corresponding to the first transaction application is 15 yuan, and the balance value corresponding to the second transaction application is 22 yuan, then the transaction amount judgment condition is met.

[0107] Furthermore, if the transaction device is determined to be gray-locked, the transaction event will be terminated immediately.

[0108] S10124. If the transaction information satisfies the transaction requirements of the first transaction application and the second transaction application respectively, the first transaction application generates security data for secure access by the first transaction application.

[0109] In this step, if the transaction information meets the transaction requirements of the first transaction application and the second transaction application respectively, the first transaction application in the transaction device generates security data for secure access by the first transaction application; after the security data is generated, the first transaction application sends the security data to the acceptance device terminal.

[0110] As an example, the security data used for secure access by the first transaction application includes a pseudo-random number and a process key; here, the pseudo-random number refers to a pseudo-random number calculated using a deterministic algorithm and used for secure access or verification; the process key refers to a key used in the process of data transmission or information processing to ensure the security and confidentiality of data transmission or processing.

[0111] S1013. The first transaction application responds to the received data cache instruction issued by the acceptance device based on the security data by performing normalized cache processing on the application data included in the data cache instruction to generate a transaction request for instructing the agent to execute the transaction event.

[0112] It should be noted that data cache instructions refer to instructions in computer instructions for managing data cache; application data is data that needs to be verified and checked and securely cached when conducting transactions, and the application data includes application data used by the first transaction application and the second transaction application in the transaction device when conducting transactions.

[0113] In one possible implementation of the present application, the application data includes at least one of a short file identifier, a transaction type identifier, a record number, and a data field.

[0114] In this step, during the specific implementation, first, after the acceptance device terminal receives the security data, it generates a data cache instruction based on the security data and sends the data cache instruction to the transaction device; then, after the transaction device receives the data cache instruction, the first transaction application in the transaction device performs standardized cache processing on the application data included in the data cache instruction; finally, the first transaction application generates a transaction request for instructing the agent to execute the transaction event.

[0115] Here, executing a transaction event on behalf of another means that when a transaction application in a transaction device executes a transaction event, the first transaction application entrusts the second transaction application to execute the transaction event on behalf of another.

[0116] In one embodiment of the present application, in a specific implementation, the step of generating a transaction request for instructing the agent to execute the transaction event by performing normalized cache processing on the application data included in the data cache instruction in step S1013 may include:

[0117] S10131. The first transaction application determines whether at least one of the short file identifier, transaction type identifier, record number and data field included in the application data meets corresponding predetermined specification conditions.

[0118] Here, the predetermined specification conditions include at least one of the following items: there exists a record with the same character value as the short file identifier in the transaction device, there exists a transaction-specific file with the same character value as the transaction type identifier in the transaction device, the lock flag byte corresponding to the record number is not set, and the length of the data field is not greater than the length of the record corresponding to the transaction-specific file in the transaction device.

[0119] Specifically, it is possible to judge from different angles whether at least one of the short file identifier, transaction type identifier, record number and data field corresponds to or complies with predetermined specification conditions. For example, it is possible to judge based on the identifier in the transaction file whether there is a record with the same character value as the short file identifier included in the application data, and it is possible to judge based on the data in the transaction file whether the length of the data field is not greater than the length of the corresponding record of the transaction-specific file in the transaction device.

[0120] Specifically, the first transaction application in the transaction device can respectively determine whether there is a record with the same character value as the short file identifier in the transaction device, whether there is a transaction-specific file with the same character value as the transaction type identifier in the transaction device, whether the lock flag byte corresponding to the record number is not set, and whether the length of the data field is not greater than the length of the record corresponding to the transaction-specific file in the transaction device.

[0121] S10132: If yes, the first transaction application caches the application data and sends a data cache response generated by the data cache to the receiving device.

[0122] In this step, if at least one of the short file identifier, transaction type identifier, record number and data field included in the application data meets the corresponding predetermined specification conditions, the first transaction application in the transaction device performs data cache processing on the application data; thereafter, the transaction device generates a data cache response based on the data cache, and sends the data cache response to the receiving device.

[0123] Furthermore, if at least one of the short file identifier, transaction type identifier, record number and data field included in the application data does not meet the corresponding predetermined specification conditions, the transaction event will be terminated immediately.

[0124] S10133. The first transaction application generates a transaction request for instructing an agent to execute the transaction event in response to the instruction issued by the receiving device to accept the data cache response.

[0125] Here, before the transaction device responds to the instruction sent by the acceptance device, the acceptance device receives the data cache response sent by the transaction device, verifies the data cache response, and sends an instruction to the transaction device indicating acceptance of the data cache response if the data cache response passes the verification.

[0126] In this step, the first transaction application in the transaction device responds to the instruction issued by the receiving device to accept the data cache response, and generates a transaction request for instructing the agent to execute the transaction event based on the security check and the data obtained through the data cache processing.

[0127] In one possible implementation mode of the present application, a transaction request is a transaction request issued by a transaction device to conduct a formal transaction with an acceptance device terminal after a security check is performed on an initialization transaction instruction and after data caching is processed; it should be noted that when the transaction device conducts a transaction, the transaction request supports both a first transaction application transaction and a second transaction application transaction.

[0128] Specifically, in one possible implementation of the present application, the transaction request includes but is not limited to a first message authentication code, a transaction device offline transaction sequence number, and a transaction process key.

[0129] S102: Determine whether the transaction information indicated by the transaction request meets a preset condition.

[0130] In this step, the transaction device determines whether the transaction request is valid and whether the transaction information indicated by the transaction request satisfies at least one of a plurality of predetermined transaction conditions.

[0131] Here, the preset condition includes: the transaction request is valid and the transaction information indicated by the transaction request satisfies at least one of a plurality of predetermined transaction conditions.

[0132] Furthermore, whether the transaction request is valid can be determined by the following steps; specifically, by comparing the first message authentication code included in the transaction request with the valid message authentication code in the transaction database to verify the first message authentication code, so as to determine whether the first message authentication code included in the composite application transaction instruction is valid.

[0133] Here, the message authentication code is a cryptographic authentication code used to verify the integrity of the instruction message and the identity of the sender. It verifies the integrity and authenticity of the instruction message by performing a hash operation on the instruction message and appending a key to generate a tag of a fixed length.

[0134] Furthermore, if the transaction request is valid, the transaction device may perform subsequent transaction operations; if the transaction request is valid, the transaction device terminates the transaction event.

[0135] Furthermore, the following steps may be used to determine whether the transaction information indicated by the transaction request satisfies at least one of multiple predetermined transaction conditions; for example, the first transaction application balance, transaction amount and transaction method in the transaction information indicated by the transaction request are respectively compared with multiple predetermined transaction conditions to determine whether the transaction information indicated by the transaction request satisfies at least one of the multiple predetermined transaction conditions.

[0136] In one possible implementation of the present application, the multiple predetermined transaction conditions include but are not limited to: the balance of the first transaction application included in the transaction information is less than or equal to a preset balance threshold, the transaction amount included in the transaction information is greater than a preset transaction threshold, and the transaction method included in the transaction information is to specify that the transaction be conducted through a second transaction application.

[0137] Among them, the preset balance threshold and the preset transaction threshold can be selected according to the actual transaction scenario. The preset balance threshold and the preset transaction threshold can be any balance threshold and transaction threshold that meet the scenario requirements, and this application does not limit them here.

[0138] For example, when the transaction scenario is a one-card consumption, the predetermined transaction conditions are that the balance of the first transaction application included in the transaction information is less than or equal to the preset balance threshold, the transaction amount included in the transaction information is greater than the preset transaction threshold, and the transaction method included in the transaction information is to specify the transaction through the second transaction application. If the balance of the one-card application included in the first transaction application included in the transaction information is 50 yuan, and the preset balance threshold is set to 60 yuan, the transaction amount is set to 40 yuan, and the preset transaction threshold is set to 30 yuan, then the transaction information meets the above two predetermined transaction conditions. In addition, if the transaction device sets the transaction device to use the second transaction application to conduct transactions according to the scenario or the user's instructions, it is determined that the predetermined transaction conditions are met.

[0139] S103: If the transaction information indicated by the transaction request meets a preset condition, entrusting a second transaction application in the transaction device to perform transaction processing for the transaction event to execute the transaction event.

[0140] In this step, if the transaction information indicated by the transaction request meets the preset conditions, the second transaction application in the transaction device is determined as the execution subject, and the second transaction application performs transaction processing for the transaction event. Specifically, the transaction device entrusts the second transaction application in the transaction device to perform transaction processing to execute the transaction event.

[0141] For example, if the balance of the first transaction application included in the transaction information is 50 yuan, and the preset balance threshold is 60 yuan, the predetermined transaction condition in the above-mentioned preset conditions is met. Therefore, according to the indication of the transaction event, the transaction device can entrust the second transaction application in the transaction device to deduct money to execute the transaction event.

[0142] Optionally, see Figure 2 , Figure 2 The second flowchart of a commissioned transaction method provided in the embodiment of the present application. Figure 2 As shown in, in addition to the entrustment transaction method described in steps S101 to S103, it also includes step S104. Specifically, step S104 is used to illustrate the method of entrusting the first transaction application to conduct a transaction if the transaction information indicated by the transaction request does not meet the preset conditions, so as to improve the practicality and universality of the transaction device when conducting transactions.

[0143] S104: If the transaction information does not meet the preset condition, entrusting the first transaction application embedded in the transaction device to perform transaction processing for the transaction event to execute the transaction event.

[0144] In this step, if the transaction information indicated by the transaction request does not meet the preset conditions, the first transaction application in the transaction device is determined as the execution subject, and the first transaction application as the execution subject performs transaction processing for the transaction event; specifically, the transaction device entrusts the first transaction application in the transaction device to perform transaction processing to execute the transaction event.

[0145] For example, if the balance of the first transaction application is 70 yuan, the preset balance threshold is 60 yuan; the transaction amount is 20 yuan, the preset transaction threshold is 30 yuan; the transaction method does not specify that the transaction be conducted through the second transaction application, that is, it is determined that the predetermined transaction conditions in the preset conditions are not met, and according to the instructions of the transaction event, the transaction device entrusts the first transaction application in the transaction device to deduct money to execute the transaction event.

[0146] Alternatively, if Figure 2 As shown in , in addition to the entrustment transaction method described in steps S101 to S104, it also includes steps S105 to S106. Specifically, steps S105 to S106 are used to illustrate a method for ensuring the integrity of transaction data and results after executing a transaction event.

[0147] S105. According to the transaction data and the transaction result generated by executing the transaction event, the transaction data and the transaction result are sent to the acceptance device.

[0148] It should be noted that when executing a transaction request, the trading device will synchronously generate transaction data to ensure that the consumption, generation of transaction flow and generation of transaction application transaction data included in the transaction are carried out in the same transaction, thereby realizing the atomic operation of transaction events on the trading device.

[0149] In this step, during the specific implementation, first, the transaction device, as the execution subject, determines the transaction data generated by the execution of the transaction event; then, determines the transaction result generated by the transaction; finally, sends the transaction data and the transaction result to the acceptance device terminal, so that the acceptance device terminal verifies and provides feedback on the transaction result.

[0150] S106: receiving a feedback signal indicating that the transaction result has been verified by the acceptance device, and asynchronously sending the transaction data and the transaction result to a background server corresponding to the transaction device.

[0151] In this step, during the specific implementation, first, the acceptance device terminal receives the transaction result and verifies whether the transaction result is passed; then, if the verification is passed, a feedback signal representing that the acceptance device terminal has verified the transaction result is sent to the transaction device; finally, after receiving the feedback signal, the transaction device asynchronously sends the transaction data and transaction result to the background server corresponding to the transaction device to complete the overall process of executing the transaction event.

[0152] Furthermore, in addition to executing the above-mentioned entrusted transaction method, the transaction device also includes executing an automatic loading method; specifically, the automatic loading method includes: the transaction device automatically initiates a loading preset condition check; when the loading preset condition is met, generates an initial loading response message, and sends the initial loading response message to the business background system; receives a loading instruction generated by the business background system through verification processing of the initial loading response message; according to the loading amount value indicated by the loading instruction, deducts the loading amount value from the second transaction application, and adds it to the balance value corresponding to the first transaction application.

[0153] The entrustment transaction method provided in the embodiment of the present application is applied to a transaction device, including: the first transaction application in the transaction device generates a transaction request for instructing the agent to execute the transaction event in response to the received instruction for instructing the execution of the transaction event; determines whether the transaction information indicated by the transaction request meets the preset conditions; if the transaction information indicated by the transaction request meets the preset conditions, then entrusts the second transaction application in the transaction device to perform transaction processing for the transaction event to execute the transaction event. Without modifying or less modifying the acceptance terminal equipment, by simultaneously supporting a transaction device including a plurality of transaction applications such as digital currency applications or business applications, when the transaction request generated by the first transaction application in response to the transaction instruction meets the preset conditions, the transaction device can entrust the second transaction application to perform the transaction through internal interaction without relying on the network, thereby organically combining the two transaction applications in the transaction device, improving the practicality and efficiency of transactions in multiple scenarios, and thereby improving the user experience when conducting transactions.

[0154] See also Figure 3 , Figure 4 , Figure 3 This is one of the structural diagrams of a transaction device provided in an embodiment of the present application. Figure 4 This is a second structural diagram of a transaction device provided in an embodiment of the present application. Figure 3 As shown in FIG. 3 , the transaction device 300 includes a security unit 320; the security unit 320 includes:

[0155] A first transaction application unit 321, configured to execute the first transaction application in the transaction device to generate a transaction request for instructing an agent to execute the transaction event in response to a received instruction for instructing the execution of the transaction event;

[0156] The judging unit 322 is used to judge whether the transaction information indicated by the transaction request meets the preset conditions;

[0157] The second transaction application unit 323 is configured to entrust the second transaction application in the transaction device to perform transaction processing for the transaction event if the transaction information indicated by the transaction request meets a preset condition, so as to execute the transaction event.

[0158] Further, when the first transaction application unit 321 is used to execute the first transaction application in the transaction device in response to the received instruction for instructing to execute the transaction event, generating a transaction request for instructing the agent to execute the transaction event, the first transaction application unit 321 is used to:

[0159] The first transaction application parses the received instruction for instructing to execute a transaction event, and determines an initialization transaction instruction;

[0160] By performing a security check on the initialization transaction instruction, generating security data for secure access of the transaction device, and sending the security data to the acceptance device;

[0161] A data cache instruction issued by the acceptance device based on the security data is received, and a transaction request for instructing the agent to execute the transaction event is generated by performing standardized cache processing on the application data included in the data cache instruction.

[0162] Furthermore, when the first transaction application unit 321 is used to generate security data for secure access of the transaction device by performing a security check on the initialization transaction instruction, the first transaction application unit 321 is used to:

[0163] Determining whether the key index number included in the initialization transaction instruction is supported by data corresponding to the transaction device;

[0164] If the key index number is supported by the data corresponding to the transaction device, it is determined whether the transaction device is gray-locked;

[0165] If the transaction device is not gray-locked, determining whether the transaction information indicated by the initialization transaction instruction satisfies the transaction requirements of the first transaction application and the transaction requirements of the second transaction application respectively;

[0166] If the transaction information satisfies the transaction requirements of the first transaction application and the second transaction application respectively, security data for secure access by the first transaction application is generated.

[0167] Furthermore, when the first transaction application unit 321 is used to generate a transaction request for instructing the agent to execute the transaction event by performing standardized cache processing on the application data included in the data cache instruction, the first transaction application unit 321 is used to:

[0168] Determining whether at least one of the short file identifier, the transaction type identifier, the record number and the data field included in the application data meets corresponding predetermined specification conditions;

[0169] If so, the application data is cached, and a data cache response generated by the data cache is sent to the receiving device.

[0170] In response to the instruction issued by the receiving device accepting the data cache response, a transaction request for instructing the agent to execute the transaction event is generated.

[0171] Furthermore, the second transaction application unit is further used for:

[0172] If the transaction information does not meet the preset condition, then for the transaction event, entrust the first transaction application in the transaction device to perform transaction processing to execute the transaction event.

[0173] Further, such as Figure 4 As shown in , the transaction device 300 further includes a communication module 330, and the communication module 330 is used to:

[0174] According to the transaction data and transaction result generated by executing the transaction event, the transaction data and the transaction result are sent to the acceptance device;

[0175] A feedback signal indicating that the transaction result has been verified by the acceptance device is received, the transaction event is determined to be completed, and the transaction data and the transaction result are asynchronously sent to a background server corresponding to the transaction device.

[0176] Further, such as Figure 4 As shown in , the transaction device 300 further includes an MCU module 310, an NFC communication unit 350, a power system 340 and a USB interface 360;

[0177] The power supply system 340 is connected to the MCU module 310 , the security unit 320 , the communication module 330 and the USB interface 360 ​​, respectively; the NFC communication unit 350 is connected to the communication module 330 ; and the USB interface 360 ​​is connected to the communication module 330 .

[0178] Furthermore, the power system 340 includes a battery, a low dropout voltage regulator and a charging management module.

[0179] Specifically, in one possible implementation of the present application, the battery provides continuous power supply for the transaction device so that the transaction device can have power support to actively complete some tasks; the low-dropout voltage regulator is used to reduce the voltage of the battery to a range allowed by the security unit and the medium and long-distance communication chip so that it can work normally; the charging management module is used for parameter management during charging, for example, controlling the charging current and automatically stopping charging after full charge and other management operations.

[0180] Furthermore, the communication module may use the communication service provided by the operator.

[0181] Furthermore, the USB interface 360 ​​is used as an interface for data transmission and device charging.

[0182] The transaction device provided in the embodiment of the present application, the first transaction application in the transaction device generates a transaction request for instructing the agent to execute the transaction event in response to the received instruction for instructing the execution of the transaction event; determines whether the transaction information indicated by the transaction request meets the preset conditions; if the transaction information indicated by the transaction request meets the preset conditions, then entrusts the second transaction application in the transaction device to perform transaction processing for the transaction event to execute the transaction event. Without or with little modification to the acceptance terminal equipment, by simultaneously supporting a transaction device with multiple transaction applications including digital currency applications or business applications, when the transaction request generated by the first transaction application in response to the transaction instruction meets the preset conditions, the transaction device can entrust the second transaction application to perform the transaction through internal interaction without relying on the network, thereby organically combining the two transaction applications in the transaction device, improving the practicality and efficiency of transactions in multiple scenarios, and thus improving the user experience when conducting transactions.

[0183] The present application also provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the computer program can execute the above-mentioned Figure 1 as well as Figure 2 The specific implementation of the steps of the entrustment transaction method in the method embodiment shown can be found in the method embodiment, which will not be repeated here.

[0184] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0185] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, and the indirect coupling or communication connection of devices or units can be electrical, mechanical or other forms.

[0186] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0187] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0188] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a non-volatile computer-readable storage medium that is executable by a processor. Based on this understanding, the technical solution of the present application can essentially be embodied in the form of a software product, or in other words, the part that contributes to the prior art or the part of the technical solution. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0189] Finally, it should be noted that the above-described embodiments are only specific implementation methods of the present application, which are used to illustrate the technical solutions of the present application, rather than to limit them. The protection scope of the present application is not limited thereto. Although the present application is described in detail with reference to the above-mentioned embodiments, ordinary technicians in the field should understand that any technician familiar with the technical field can still modify the technical solutions recorded in the above-mentioned embodiments within the technical scope disclosed in the present application, or can easily think of changes, or make equivalent replacements for some of the technical features therein; and these modifications, changes or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.

Claims

1. A method for entrusting a transaction, characterized in that: Applied to a trading device, the entrustment trading method includes: The first transaction application in the transaction device generates a transaction request for instructing an agent to execute the transaction event in response to the received instruction for instructing the execution of the transaction event; Determining whether the transaction information indicated by the transaction request meets a preset condition; If the transaction information indicated by the transaction request meets the preset condition, then for the transaction event, the second transaction application in the transaction device is entrusted to perform transaction processing to execute the transaction event.

2. The method according to claim 1, characterized in that The first transaction application in the transaction device generates a transaction request for instructing an agent to execute the transaction event in response to the received instruction for instructing the execution of the transaction event, including: The first transaction application parses the received instruction for instructing to execute the transaction event, and determines the initialization transaction instruction for instructing to execute the transaction event; The first transaction application generates security data for secure access of the transaction device by performing a security check on the initialization transaction instruction, and sends the security data to the acceptance device; The first transaction application responds to the received data cache instruction issued by the acceptance device based on the security data, and generates a transaction request for instructing the agent to execute the transaction event by performing normalized cache processing on the application data included in the data cache instruction.

3. The method according to claim 2, characterized in that The first transaction application generates security data for secure access by the transaction device by performing a security check on the initialization transaction instruction, including: The first transaction application determines whether the key index number included in the initialization transaction instruction is supported by data corresponding to the transaction device; If the key index number is supported by the data corresponding to the transaction device, the first transaction application determines whether the transaction device is gray-locked; If the transaction device is not gray-locked, the first transaction application determines whether the transaction information indicated by the initialization transaction instruction satisfies the transaction requirements of the first transaction application and the second transaction application respectively; If the transaction information meets the transaction requirements of the first transaction application and the second transaction application respectively, the first transaction application generates security data for secure access by the first transaction application.

4. The method according to claim 2, characterized in that: The first transaction application generates a transaction request for instructing the agent to execute the transaction event by performing standardized cache processing on the application data included in the data cache instruction, including: The first transaction application determines whether at least one of the short file identifier, the transaction type identifier, the record number and the data field included in the application data meets the corresponding predetermined specification conditions; If so, the first transaction application caches the application data and sends a data cache response generated by the data cache to the receiving device; The first transaction application generates a transaction request for instructing an agent to execute the transaction event in response to the instruction issued by the receiving device to accept the data cache response.

5. The method according to claim 1, characterized in that The preset condition includes: the transaction request is valid and the transaction information indicated by the transaction request satisfies at least one of a plurality of predetermined transaction conditions.

6. The method according to claim 1 or 5, characterized in that: The method further comprises: If the transaction information does not meet the preset condition, then for the transaction event, entrust the first transaction application in the transaction device to perform transaction processing to execute the transaction event.

7. The method according to claim 1 or 5, characterized in that: After executing the transaction event, the method further includes: According to the transaction data and transaction result generated by executing the transaction event, the transaction data and the transaction result are sent to the acceptance device; A feedback signal indicating that the transaction result has been verified by the acceptance device is received, and the transaction data and the transaction result are asynchronously sent to a background server corresponding to the transaction device.

8. The method according to claim 4, characterized in that The predetermined standard conditions include at least one of the following items: there exists a record with the same character value as the short file identifier in the transaction device, there exists a transaction-specific file with the same character value as the transaction type identifier in the transaction device, the lock flag byte corresponding to the record number is not set, and the length of the data field is not greater than the length of the record corresponding to the transaction-specific file in the transaction device.

9. The method according to claim 5, characterized in that The multiple predetermined transaction conditions include: the balance of the first transaction application included in the transaction information is less than or equal to a preset balance threshold, the transaction amount included in the transaction information is greater than a preset transaction threshold, and the transaction method included in the transaction information specifies that the transaction be conducted through a second transaction application.

10. The method according to any one of claims 1-4, 8-9, characterized in that: The transaction communication environment of the transaction device and the acceptance device includes a first transaction communication environment and / or a second transaction communication environment; The first transaction communication environment refers to an environment where the network or signal connection between the transaction device and the acceptance device is normal; The second transaction communication environment refers to an environment in which the network or signal connection between the transaction device and / or the acceptance device is abnormal; wherein, the connection abnormality means that the network connection between the transaction device and / or the acceptance device is disconnected or the signal strength is unable to support normal communication between the transaction device and / or the acceptance device.

11. A transaction device, characterized in that: The transaction device comprises a security unit; the security unit comprises: A first transaction application unit, configured to execute the first transaction application in the transaction device to generate a transaction request for instructing an agent to execute the transaction event in response to a received instruction for instructing the execution of the transaction event; A determination unit, configured to determine whether the transaction information indicated by the transaction request satisfies a preset condition; The second transaction application unit is configured to entrust the second transaction application in the transaction device to perform transaction processing for the transaction event if the transaction information indicated by the transaction request meets a preset condition, so as to execute the transaction event.

12. The transaction device according to claim 11, characterized in that: The transaction device further comprises a communication module, wherein the communication module is used for: According to the transaction data and transaction result generated by executing the transaction event, the transaction data and the transaction result are sent to the acceptance device; A feedback signal indicating that the transaction result has been verified by the acceptance device is received, the transaction event is determined to be completed, and the transaction data and the transaction result are asynchronously sent to a background server corresponding to the transaction device.

13. The transaction device according to claim 11, characterized in that: The transaction device also includes an MCU module, an NFC communication unit, a power supply system and a USB interface; The power supply system is connected to the MCU module, the security unit, the communication module and the USB interface respectively; the NFC communication unit is connected to the communication module; and the USB interface is connected to the communication module.

14. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the entrusted transaction method according to any one of claims 1 to 10 are executed.

Images