Transaction security management method and device, computer equipment, storage medium and product

Abstract

The invention relates to a transaction security management method and device, computer equipment, a storage medium and a product, and relates to the technical field of security management. The method comprises the steps of sending a verification request to an intelligent contract under the condition that transaction information of a target transaction operation is received; the verification request is used for indicating that the transaction information is matched with a secure transaction record of a guarded user; when the matching result indicates that the matching fails and a transaction confirmation operation of the guarding user is received, constructing record updating data based on a first hash value corresponding to a locally stored first record updating frequency and the transaction information; sending a record updating request containing record updating data to the smart contract, so that the smart contract updates the secure transaction record of the guarded user based on the transaction information under the condition that the smart contract determines that the first hash value is matched with the second hash value; through the method, the accuracy of transaction operation protection based on the secure transaction record can be guaranteed, and the transaction security of the guarded user is guaranteed.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of security management, and in particular to a transaction security management method, apparatus, computer equipment, storage medium and product. Background Art

[0002] With the continuous intelligence of mobile phones and the rapid development of Internet technology, the problem of illegal calls has become increasingly prominent. For example, illegal persons use telephones, text messages, and various communication apps to deceive victims into performing transactions under various pretexts, causing economic losses. The endless illegal activities have greatly increased the risks of transaction operations.

[0003] In related technologies, various algorithms are used to identify illegal behaviors or mark illegal numbers. When a user may be talking to an illegal person, the user is reminded in various ways to ensure the safety of transaction operations. However, as the illegal behaviors of illegal persons escalate, there will be problems of transaction security risks due to insufficient algorithm recognition capabilities, and transaction security management solutions need to be improved. Summary of the invention

[0004] The embodiments of the present application provide a transaction security management method, apparatus, computer equipment, storage medium and product. In a scenario where a guarding user performs security protection on the transaction operations of a protected user, when it is necessary to update the security transaction records of the protected user, the card application that sends the record update request can be authenticated by using the hash value corresponding to the record update number to ensure the security of the record update, thereby ensuring the accuracy of the transaction operation protection based on the security transaction records, and further ensuring the transaction security of the protected user. The technical solution is as follows.

[0005] On the one hand, a transaction security management method is provided, the method is executed by a first card application corresponding to a guarding user, a guarding relationship is established between the guarding user and the guarded user, the method comprises: Upon receiving the transaction information of the target transaction operation sent by the second card application corresponding to the protected user, sending a verification request to the smart contract; the verification request is used to instruct the smart contract to match the transaction information of the target transaction operation with the security transaction record of the protected user; After the matching result fed back by the smart contract indicates a matching failure and a transaction confirmation operation of the guarding user is received, record update data is constructed based on the first hash value corresponding to the first record update number of the guarded user and the transaction information of the target transaction operation stored locally; A record update request including the record update data is sent to the smart contract, so that the smart contract updates the secure transaction record of the protected user based on the transaction information of the target transaction operation when it is determined that the first hash value extracted from the record update request matches the second hash value; the second hash value is obtained by the smart contract through hash calculation based on the stored number of second record updates of the protected user by the protecting user.

[0006] On the other hand, a transaction security management method is provided, the method being executed by a smart contract, wherein the smart contract stores a guardian relationship between a guardian user and a protected user; the method comprising: Receiving a verification request sent by a first card application corresponding to the guarding user; the verification request includes transaction information of a target transaction operation; the target transaction operation is a transaction operation performed in a second card application corresponding to the guarded user; Matching the transaction information of the target transaction operation with the security transaction record of the protected user based on the verification request to obtain a matching result; Feedback the matching result to the first card application; receiving a record update request including record update data sent by the first card application; the record update data is constructed by the first card application based on a first hash value corresponding to a first record update number of the protected user stored locally and transaction information of the target transaction operation after the matching result indicates a match failure and the first card application receives a transaction confirmation operation of the protected user; Calculate a second hash value based on the number of times the second record of the protected user is updated by the protected user; When it is determined that the first hash value extracted from the record update request matches the second hash value, the secure transaction record of the protected user is updated based on the transaction information of the target transaction operation.

[0007] On the other hand, a transaction security management device is provided, the device is applied in a first card application corresponding to a guarding user, a guarding relationship is established between the guarding user and the guarded user, and the device includes: A first request sending module is used to send a verification request to the smart contract when receiving the transaction information of the target transaction operation sent by the second card application corresponding to the protected user; the verification request is used to instruct the smart contract to match the transaction information of the target transaction operation with the security transaction record of the protected user; A data construction module, configured to construct record update data based on a first hash value corresponding to a first record update number of the protected user and transaction information of the target transaction operation stored locally after the matching result fed back by the smart contract indicates a matching failure and a transaction confirmation operation of the guarding user is received; A second request sending module is used to send a record update request containing the record update data to the smart contract, so that the smart contract updates the secure transaction record of the protected user based on the transaction information of the target transaction operation when it is determined that the first hash value extracted from the record update request matches the second hash value; the second hash value is obtained by the smart contract through hash calculation based on the stored number of times the protecting user updates the second record of the protected user.

[0008] In a possible implementation, the transaction information of the target transaction operation includes information of the user being traded; and the data construction module includes: A first encryption submodule, used to encrypt the traded user information based on a random number sent by the smart contract; A data construction submodule, used to construct update data based on the encrypted traded user information and the first hash value; The second encryption submodule is used to encrypt the update data using a locally stored private key to obtain the record update data.

[0009] In a possible implementation manner, the device further includes: A first receiving module, used to receive the record update result fed back by the smart contract; The data updating module is used to update the first record update number stored locally when the record update result indicates that the record update is successful.

[0010] In a possible implementation, the secure transaction record of the protected user is the intersection of a first transaction record provided by the protected user and a second transaction record provided by the protecting user; the second transaction record is obtained after updating the first transaction record.

[0011] In a possible implementation manner, the device further includes: The first instruction sending module is used to send a transaction permission instruction to the second card application after receiving the transaction confirmation operation of the guardian user, so that the second card application releases the application guardian service; the application guardian service is used to interrupt the target transaction operation when the transaction information of the target transaction operation meets the guardian condition.

[0012] On the other hand, a transaction security management device is provided, which is applied in a smart contract, wherein the smart contract stores a guardian relationship between a guardian user and a protected user; the device comprises: A second receiving module is used to receive a verification request sent by the first card application corresponding to the guarding user; the verification request includes transaction information of a target transaction operation; the target transaction operation is a transaction operation performed in the second card application corresponding to the guarded user; A matching module, configured to match the transaction information of the target transaction operation with the security transaction record of the protected user based on the verification request to obtain a matching result; A result feedback module, used for feeding back the matching result to the first card application; A third receiving module is configured to receive a record update request including record update data sent by the first card application; the record update data is constructed by the first card application based on the first hash value corresponding to the first record update number of the protected user and the transaction information of the target transaction operation stored locally after the matching result indicates a match failure and the first card application receives a transaction confirmation operation of the protected user; A calculation module, configured to calculate a second hash value based on the number of times the second record of the protected user is updated by the protected user; A record update module is used to update the security transaction record of the protected user based on the transaction information of the target transaction operation when it is determined that the first hash value extracted from the record update request matches the second hash value.

[0013] In a possible implementation, the secure transaction records of the protected user are stored in a blockchain, and the matching module includes: A request sending submodule, used to send a matching request to the blockchain based on the verification request; the matching request is used to instruct the blockchain to match the transaction information of the target transaction operation with the security transaction record of the protected user; The result receiving submodule is used to receive the matching result fed back by the blockchain.

[0014] In a possible implementation manner, the device further includes: A data acquisition module, used for acquiring the record update data in the record update request; A decryption module is used to decrypt the record update data through a public key to extract the first hash value; the public key is queried based on the user information of the guardian user included in the record update request.

[0015] In a possible implementation manner, the device further includes: The second instruction sending module is used to send a transaction permission instruction to the second card application when the matching result indicates that the matching is successful, so that the second card application releases the application guard service.

[0016] In a possible implementation, the application guard service includes at least one of the following: turning off the SMS display function, locking the camera, locking the fingerprint sensor, and displaying a full-screen pop-up window.

[0017] On the other hand, a computer device is provided, which includes a processor and a memory, wherein the memory stores at least one computer program, and the at least one computer program is loaded and executed by the processor to implement the above-mentioned transaction security management method.

[0018] On the other hand, a computer-readable storage medium is provided, in which at least one computer program is stored, and the computer program is loaded and executed by a processor to implement the above-mentioned transaction security management method.

[0019] On the other hand, a computer program product is provided, which includes a computer program stored on a non-transitory computer-readable storage medium, and the computer program includes program instructions, which, when executed by a computer, cause the computer to execute to implement the transaction security management method provided in the various optional implementations mentioned above.

[0020] The technical solution provided by this application may have the following beneficial effects: The transaction security management method provided by the embodiment of the present application is that, when a guardian relationship is established between a guardian user and a protected user, the first card application corresponding to the guardian user sends a verification request to the smart contract after receiving the transaction information of the target transaction operation sent by the second card application corresponding to the protected user, so that the smart contract matches the transaction information of the target transaction operation with the security transaction record of the protected user, and feeds back the matching result to the first card application; after the matching result indicates a match failure and the transaction confirmation operation of the guardian user is received, record update data is constructed based on the first hash value corresponding to the first record update number of the protected user stored locally and the transaction information of the target transaction operation, and a record update request containing the record update data is sent to the smart contract, so that when the smart contract determines that the first hash value extracted from the record update request matches the second hash value, the smart contract updates the security transaction record of the protected user based on the transaction information of the target transaction operation. Through the above method, in the scenario where the guarding user performs security protection on the transaction operations of the protected user, when the security transaction record of the protected user needs to be updated, the card application that sends the record update request can be authenticated by using the hash value corresponding to the record update number to ensure the security of the record update, thereby ensuring the accuracy of the transaction operation protection based on the security transaction record, and further ensuring the transaction security of the protected user.

[0021] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0023] Figure 1 A flowchart of a transaction security management method provided by an exemplary embodiment of the present application is shown; Figure 2 A schematic diagram showing a transaction security management system corresponding to a transaction security management method provided by an exemplary embodiment of the present application is shown; Figure 3 A flowchart of a process for establishing a guardian relationship provided by an exemplary embodiment of the present application is shown; Figure 4 A schematic diagram of a card application interface provided by an exemplary embodiment of the present application is shown; Figure 5 A schematic diagram of a guard user input interface provided by an exemplary embodiment of the present application is shown; Figure 6 A schematic diagram of a request prompt pop-up window provided by an exemplary embodiment of the present application is shown; Figure 7 A flowchart of a transaction security management method provided by an exemplary embodiment of the present application is shown; Figure 8 A schematic diagram of an application guard service provided by an exemplary embodiment of the present application is shown; Fig. 9 A schematic diagram of a transaction reminder pop-up window provided by an exemplary embodiment of the present application is shown; Fig.10 An interactive schematic diagram of a transaction security management method provided by an exemplary embodiment of the present application is shown; Fig.11 A schematic diagram showing a secure transaction record update process provided by an exemplary embodiment of the present application is shown; Fig.12 A block diagram of a transaction security management device provided by an exemplary embodiment of the present application is shown; Fig.13 A block diagram of a transaction security management device provided by an exemplary embodiment of the present application is shown; Fig.14 A structural block diagram of a computer device shown in an exemplary embodiment of the present application is shown; Fig.15 A structural block diagram of a computer device shown in an exemplary embodiment of the present application is shown. DETAILED DESCRIPTION

[0024] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0025] In order to ensure transaction security, the embodiment of the present application provides a transaction security management method, by establishing a guardian relationship between a protected user and at least one guardian user, so that the guardian user can make a security judgment on the transaction operation performed by the protected user in the second card application, thereby ensuring the security of the transaction operation performed by the protected user in the second card application; in the embodiment of the present application, the second card application can determine the security of the transaction operation by matching the transaction information of the transaction operation performed in the second card application with the security transaction record of the protected user through a smart contract, therefore, the accuracy and security of the security transaction record are particularly important for the security verification of the transaction operation; the embodiment of the present application provides a transaction security management method, which can ensure the security and accuracy of the security transaction record, thereby improving the accuracy of transaction security management based on the security transaction record; Figure 1A flowchart of a transaction security management method provided by an exemplary embodiment of the present application is shown. The method is executed by a first card application corresponding to a guarding user. A guarding relationship is established between the guarding user and the guarded user. The method includes: Step 110, upon receiving the transaction information of the target transaction operation sent by the second card application corresponding to the protected user, a verification request is sent to the smart contract; the verification request is used to instruct the smart contract to match the transaction information of the target transaction operation with the security transaction record of the protected user.

[0026] In the embodiment of the present application, a guarding relationship is established between the guarding user and the protected user, and the same protected user can establish a guarding relationship with multiple guarding users. Therefore, the guarding user in the present application refers to any guarding user who has established a guarding relationship with the protected user.

[0027] When the second card application corresponding to the protected user determines that the target transaction operation meets the protection conditions, it triggers the application protection service and sends the transaction information of the target transaction operation to the first card application corresponding to the protecting user; accordingly, the first card application corresponding to the protecting user receives the transaction information of the target transaction operation. In principle, the transaction information may include but is not limited to the user information of the protecting user, the user information of the user being traded, the transaction amount, etc.

[0028] The first card application can assemble and generate a verification request based on the transaction information received for the target transaction operation; the verification request may include user information of the protected person, user information of the guardian, and user information of the traded user, etc.; illustratively, card application B of guardian B assembles a verification request, which includes user information corresponding to each of the protected person A, guardian B, and traded user X, wherein the guardianship relationship between the protected person A and guardian B is pre-stored in the smart contract.

[0029] In one possible implementation, in order to ensure the security of user data and improve the credibility of transaction security verification and management, the secure transaction records of the protected user can be stored in the blockchain and maintained jointly by the protecting user and the protected user.

[0030] In one possible implementation, the user's card application can be a SIM card application installed on a super SIM card. The same protected user can establish a guardian relationship with multiple guardian users. When the same protected user has a guardian relationship with multiple guardian users, the first card application corresponding to each guardian user will receive the transaction information of the target transaction operation sent by the second card application, and accordingly, each first card application will perform the above-mentioned verification request assembly process; by establishing a guardian relationship between a protected user and multiple guardian users, it is possible to avoid the situation where the guardian user responds slowly due to accidental factors, thereby affecting the transaction operation of the protected person; in addition, for security transaction records, the security transaction records can be jointly maintained by multiple guardians and the protected person, thereby improving the security of the security transaction records and ensuring the accuracy of security management.

[0031] Step 120, after the matching result fed back by the smart contract indicates a matching failure and the transaction confirmation operation of the guarding user is received, the record update data is constructed based on the first hash value corresponding to the first record update number of the guarded user stored locally and the transaction information of the target transaction operation.

[0032] The first card application sends a verification request to the smart contract. Correspondingly, the smart contract receives the verification request sent by the first card application, and matches the transaction information of the target transaction operation with the security transaction record of the protected user in response to the verification request; when the security transaction record is stored in the blockchain, the smart contract can achieve the matching of the transaction information of the target transaction operation with the security transaction record of the protected user through interaction with the blockchain. In one possible implementation method, the smart contract can send the verification request to the blockchain so that the blockchain performs message matching and feeds back the matching result to the smart contract, and the smart contract then feeds back the matching result to the first card application; or, in another possible implementation method, the smart contract can query the security transaction record of the protected user from the blockchain based on the user information of the protected user in the verification request, obtain the matching result after performing message matching, and feed back the matching result to the first card application.

[0033] Among them, matching the transaction information of the target transaction operation with the security transaction record of the protected user can be to query the user information of the traded user in the security transaction of the protected user. If found, the matching result indicates a successful match, indicating that the traded user of the current protected user is a secure user. In this case, the smart contract can generate a transaction permission instruction and send it to the second card application so that the second card application can continue the transaction operation; if not found, the matching result indicates a failed match, indicating that the user information of the current protected user does not exist in the transaction whitelist with the protected user, that is, it has not passed the verification of the security transaction record.

[0034] When the matching result indicates a match failure, in order to avoid misjudgment caused by the failure to update the security transaction record, the guardian user can further judge the transaction information of the target transaction operation. If the guardian user cancels the transaction, it means that the target transaction operation has not passed the security verification. The second card application can send a transaction risk warning message to the first card application to instruct the protected user to cancel the target transaction operation; if the guardian user confirms the transaction, it means that the target transaction operation has passed the security verification and the user being traded is trustworthy. The second card application can send a transaction permission instruction to the first card application to instruct the first card application to continue the transaction operation.

[0035] When the matching result fed back by the smart contract indicates that the matching has failed and the transaction confirmation operation of the guarding user has been received, it means that the transaction information of the current target transaction operation does not exist in the security transaction record of the guarded user, but the transaction information of the target transaction operation is safe. Therefore, the security transaction record of the guarded user needs to be updated so that security verification can be performed through the security transaction record later. In order to ensure the security of data update and maintenance of the security transaction record, the first card application can construct record update data based on the first hash value corresponding to the number of first record updates of the guarded user stored locally and the transaction information of the target transaction operation; wherein, the first hash value corresponding to the number of first record updates is used for update security verification.

[0036] Step 130, sending a record update request containing record update data to the smart contract, so that the smart contract updates the secure transaction record of the protected user based on the transaction information of the target transaction operation when it determines that the first hash value extracted from the record update request matches the second hash value; the second hash value is obtained by the smart contract based on the hash calculation of the second record update number of the protected user by the stored protecting user.

[0037] The first card application sends a record update request containing record update data to the smart contract, and accordingly, the smart contract receives the record update request; before updating the secure transaction record, in order to ensure the security of the data update, the smart contract can first verify the identity of the card application that sends the record update request to avoid malicious updates by illegal users. In an embodiment of the present application, the smart contract can extract a first hash value from the record update request, and obtain a second hash value based on a hash calculation of the second record update times of the protected user by the locally stored guardian user; the first hash value is matched with the second hash value, and when the two are consistent, it is determined that the match is successful, and it is determined that the first card application that sent the record update request is a legitimate card application, and then the secure transaction record of the protected user is updated based on the transaction information of the target transaction operation in the record update request, for example, the user information of the traded user in the transaction information is added to the secure transaction record of the protected user.

[0038] To summarize, the transaction security management method provided in the embodiment of the present application is that, when a guardian relationship is established between the guardian user and the protected user, the first card application corresponding to the guardian user sends a verification request to the smart contract after receiving the transaction information of the target transaction operation sent by the second card application corresponding to the protected user, so that the smart contract matches the transaction information of the target transaction operation with the security transaction record of the protected user, and feeds back the matching result to the first card application; after the matching result indicates a match failure and the transaction confirmation operation of the guardian user is received, record update data is constructed based on the first hash value corresponding to the first record update number of the protected user stored locally and the transaction information of the target transaction operation, and a record update request containing the record update data is sent to the smart contract, so that when the smart contract determines that the first hash value extracted from the record update request matches the second hash value, the smart contract updates the security transaction record of the protected user based on the transaction information of the target transaction operation. Through the above method, in the scenario where the guarding user performs security protection on the transaction operations of the protected user, when the security transaction record of the protected user needs to be updated, the card application that sends the record update request can be authenticated by using the hash value corresponding to the record update number to ensure the security of the record update, thereby ensuring the accuracy of the transaction operation protection based on the security transaction record, and further ensuring the transaction security of the protected user.

[0039] In one possible implementation, the card application and the third-party platform can exchange information through the TSM (Trusted Service Manager) platform, and the user's secure transaction records are stored in the blockchain. In this case, Figure 2 A schematic diagram of a transaction security management system corresponding to a transaction security management method provided by an exemplary embodiment of the present application is shown. Figure 2 As shown, the transaction security relationship system includes a user terminal device 210, a TSM platform 220, a smart contract 230 and a blockchain 240. Each guarding user and guarded user has a corresponding user terminal device, and each user terminal device has a corresponding card application installed therein.

[0040] In one possible implementation, the card application may be a SIM card application. In this case, the card application may be sent silently to the SIM card installed in the user terminal device 120 through the BIP protocol to implement application installation in the SIM card; wherein the SIM card may be a super SIM card, which is used to provide a card application carrier, receive and execute instructions, and send prompt information and other functions. The user terminal device, as a blockchain node, may access blockchain data.

[0041] The card application is pre-installed in the super SIM card and is used to perform secure operations on user transactions. After activating the "Guardian of Others" function, the transaction behavior of the protected person can be protected by multiple guardians based on smart contracts.

[0042] The TSM platform 220 is a hub between the card application and the third-party platform, used to receive instructions from the card application, provide a callable interface to the third-party platform, and execute the third-party's behavioral instructions; the smart contract 230 is used to match messages in the secure transaction record in the blockchain based on the transaction information of the received transaction operation, and to provide feedback on the matching results. When there is a need to update the secure transaction record, the card application that initiates the record update request is authenticated to ensure the security of the record update operation.

[0043] Blockchain 240 may store secure transaction records of various users maintained by multiple parties.

[0044] In the transaction security management scenario provided by this application, before the guarding user performs security protection on the transaction operations performed by the protected user, a guarding relationship between the guarding user and the protected user must be established. Figure 3 A flowchart of a guardian relationship establishment process provided by an exemplary embodiment of the present application is shown. The method can be executed by the second card application of the protected user, such as Figure 3 As shown, the method includes: Step 310, display the card application interface.

[0045] The card application interface can display a guard status indicator control, a guard relationship establishment control, and a guard information viewing control. Figure 4 A schematic diagram of a card application interface provided by an exemplary embodiment of the present application is shown. Figure 4As shown, the card application interface displays a guard status indication control 410, a guard relationship establishment control 420 and a guard information management control 430. After the security protection function of the current card application is turned on, Figure 4 As shown, the guard status indication control 410 is displayed as "protected". The security protection function is a basic security protection function provided by the card application in addition to the transaction security protection of establishing a guard relationship by guarding the user. The guard relationship establishment control 420 can be implemented as follows Figure 4 The "others guarding" control shown is used to establish a guarding relationship with other users when the current user is the guarded user. The guarding information management control 430 can be implemented as follows Figure 4 The "Protect Others" control shown is used to manage the security transaction records of the corresponding protected users when the current user is the protecting user; when the user has not become a protecting user, the protecting user management control can be in a "grayed out" state, and there is no feedback when the user clicks it. Subsequently, a request for activation is established based on the protecting relationship with the protected user. After activation, the "grayed out" state is canceled, and the user becomes a protecting user. Through the protecting information management control, it is possible to view the historical transaction information of the protected user, set the protecting conditions for the protected user, and delete the protected user, etc.

[0046] The user corresponding to the same card application can be both a protecting user and a protected user.

[0047] Step 320: After receiving a selection operation for establishing a guardian relationship control, a guardian user input interface is displayed.

[0048] When the user selects Figure 4 When the "Others Guardian" control is displayed, the guard user input interface is displayed. Figure 5 A schematic diagram of a guard user input interface provided by an exemplary embodiment of the present application is shown. Figure 5 As shown, the user input interface 510 may include multiple input boxes 520, so that the user can configure multiple users who are to establish a guarding relationship with the guarded user in the interface.

[0049] Step 330, receiving user information of the guarding user input by the guarded user based on the guarding user input interface.

[0050] Illustratively, if the current user is the protected user A, the user information of user B, user C, and user D entered in the protecting user input interface are the users for whom protecting relationships are to be established; optionally, the user information of the protecting user can be the protecting user's identity, communication number, or email address, etc., and this application does not impose any restrictions on this.

[0051] Step 340, sending a relationship establishment request to the first card application corresponding to each protected user through the TSM platform, so that the TSM platform establishes a protection relationship based on the operation information fed back by each first card application based on the relationship establishment request; the relationship establishment request includes the user information of the protected user.

[0052] In a possible implementation, the second card application can send a relationship establishment request to the TSM platform. After receiving the relationship establishment request, the TSM platform parses the user information carried in the relationship establishment request, generates request prompt information and sends it to the first card application of each guardian user; the first card application of each guardian user assembles the active command Displaytext according to the incoming request prompt information, and displays the request prompt information in a pop-up window; Figure 6 A schematic diagram of a request prompt pop-up window provided by an exemplary embodiment of the present application is shown. Figure 6 As shown, the request prompt pop-up window displays request prompt information 610 and operation controls 620 (including cancel controls and confirmation controls). Each first card application feeds back operation information to the TSM platform based on the operation of the corresponding guardian user on the request prompt pop-up window, so that the TSM platform determines whether to establish a guardian relationship between the guardian user and the protected user. Among them, after the guardian user selects the confirmation control, the TSM platform establishes a guardian relationship between the corresponding guardian user and the protected user. If the guardian user selects the cancel control, or if no operation on the request prompt pop-up window is received within the first target time, the TSM platform does not establish a guardian relationship between the corresponding guardian user and the protected user; schematically, if user B clicks confirm, user C clicks cancel, and user D clicks confirm among the guardian users input by the protected user A, the binding relationship established by the TSM platform is: protected user A-guardian user B, protected user A-guardian user D.

[0053] In addition, after completing the relationship establishment, the TSM platform can send an activation instruction to the guardian user's first card application, and the activation instruction is used to activate the guardian information management ("guarding others") function in the guardian user's first card application.

[0054] Step 350: Receive the relationship establishment result fed back by the TSM platform.

[0055] After completing the relationship establishment, the TSM platform can feedback the relationship establishment result to the first card application and the second card application; further, the TSM platform can send the relationship establishment result to the smart contract.

[0056] In another possible implementation, the protected user can sign a contract for the guardian relationship establishment service on the TSM platform and provide the TSM platform with user information of the user to establish a guardian relationship; the TSM platform sends a first activation instruction to the protected user's second card application based on the contract information to indicate that the guardian relationship establishment function in the second card application is passively activated, and after the relationship is established, sends a second activation instruction to each protected user to indicate that the guardian information management function in each first card application is passively activated.

[0057] After the guarding relationship between the guarded user and the guarding user can be established through the above process, the method further includes: Step 360: Generate a first transaction record based on the setting operation of the protected user.

[0058] The first transaction record may be generated based on user information of a user who is subject to a safe transaction input by the user in a record setting interface provided by the second card application. The user information of the user who is subject to a transaction may include but is not limited to account information, communication information, identity information, etc. of the user who is subject to a transaction.

[0059] Step 370, sending the first transaction record to each first card application through the TSM platform; so that each guardian user updates the first transaction record and obtains the corresponding second transaction record.

[0060] Schematically, card application A generates a first transaction record R A , R A Sent to the card application B protecting user B and the card application D protecting user D respectively.

[0061] Taking the guardian user B as an example, the corresponding first card application receives R A After that, it is displayed to Guardian User B in the interface triggered by the transaction information management control, where Guardian User B can A Perform the deletion operation to obtain the second transaction record R corresponding to the guardian user B B , R B Feedback to card application A; Guardian user D similarly feedbacks R to card application A D .

[0062] Step 380: Receive each second transaction record fed back by each first card application through the TSM platform.

[0063] Step 390: determine the intersection of the first transaction record and each second security transaction record as the security transaction record of the protected user.

[0064] Indicatively, card application A receives R B , R DAfter that, R A , R B , R D After taking the intersection, the secure transaction record R0 is obtained, and the secure transaction record R0 is uploaded to the blockchain for storage. In other words, the secure transaction record R0 is the transaction security whitelist for the protected user A.

[0065] Through the above process, the security transaction records of the protected users initially uploaded to the blockchain can be jointly confirmed by multiple parties. Based on the security transaction records, they are subsequently maintained and continuously updated by multiple parties to provide security protection for the transaction operations performed by the protected users based on the updated security transaction records.

[0066] In one possible implementation, all transaction operations performed by the protected user require collaborative security protection by the protecting user, or, in another possible implementation, when the second card application determines that the current transaction operation meets the protecting condition, it determines that the protecting user needs to perform collaborative security protection, wherein the protecting condition can be jointly set by the protected user and each protecting user, for example, the protecting condition can be the union of the triggering conditions set by each user; the protected user can trigger the setting of the protecting condition through the protecting information management control. Schematically, protecting user B clicks the "Protect Others" control in card application B to enter the next level menu, and enters information in the triggering condition: transfer to others is greater than or equal to 1000. After receiving the confirmation operation, card application B sends the data to card application A of protected user A through the TSM platform for storage, so that when the transaction operation in subsequent card application A meets the protecting condition, collaborative security protection can be triggered.

[0067] Figure 7 A flowchart of a transaction security management method provided by an exemplary embodiment of the present application is shown. The method can be executed by a first card application corresponding to the guarding user, a second card application corresponding to the guarded user, and a smart contract, such as Figure 7 As shown, the process can be implemented as: Step 701: The second card application receives a target transaction operation.

[0068] Step 702: When the second card application determines that the target transaction operation meets the guard condition, the second card application triggers the application guard service; the application guard service is used to interrupt the target transaction operation.

[0069] Among them, the guarding condition can be jointly set by the protected user and multiple guarding users. Schematically, when the guarding condition is "transferring to others is greater than or equal to 1,000 yuan", if the target transaction operation is to transfer 2,000 yuan to others, the second card application determines that the target transaction operation meets the guarding condition and triggers the application guarding service.

[0070] The application guard service includes at least one of the following: turning off the SMS display function, locking the camera, locking the fingerprint sensor, and displaying a full-screen pop-up window. Taking the application guard service as an example of displaying a full-screen pop-up window, Figure 8 A schematic diagram of an application guard service provided by an exemplary embodiment of the present application is shown. Figure 8 As shown, when the target transaction operation meets the guarding conditions, a full-screen pop-up window 810 is displayed in the second card application of the protected user. The full-screen pop-up window may display a service trigger prompt message "The current transaction behavior triggers the guarding service, please wait"; optionally, the guarding service has a certain timeliness, that is, if no transaction permission instruction or transaction risk warning information is received within a preset time period, the guarding service will be terminated.

[0071] Step 703: The second card application sends the transaction information corresponding to the target transaction operation to the first card application. Correspondingly, the first card application receives the transaction information of the target transaction operation.

[0072] The transaction information of the transaction operation may include the transaction amount and the user information of the user being traded (such as account information); the second card application sends the transaction information corresponding to the target transaction operation to the first card applications of each guarding user through the TSM platform; accordingly, each first card application receives the transaction information of the second card application, and each first card application assembles a verification request based on the received transaction information of the target transaction operation.

[0073] Step 704: The first card application sends a verification request to the smart contract, and accordingly, the smart contract receives the verification request.

[0074] Each first card application sends its own verification request to the smart contract respectively. Correspondingly, the smart contract can receive the verification requests sent by each first card application and perform information matching based on each verification request.

[0075] Step 705: The smart contract matches the transaction information of the target transaction operation with the secure transaction record of the protected user to obtain a matching result.

[0076] In the embodiment of the present application, the secure transaction record of the protected user is the intersection of the first transaction record provided by the protected user and the second transaction record provided by the protecting user; the second transaction record is obtained by updating the first transaction record. In other words, the secure transaction record of the protected user is jointly maintained by multiple parties.

[0077] In one possible implementation, the protected user's secure transaction records are stored in the blockchain, and the matching process can be implemented as follows: Sending a matching request to the blockchain based on the verification request; the matching request is used to instruct the blockchain to match the transaction information of the target transaction operation with the secure transaction record of the protected user; Receive matching results from blockchain.

[0078] In another possible implementation, when the protected user's security transaction records are stored in the blockchain terminal, the matching process can also be implemented as follows: Send a record retrieval request to the blockchain based on the verification request; Receive the secure transaction records of the protected user based on the blockchain record retrieval request feedback; The transaction information of the target transaction operation is matched with the secure transaction records of the protected user.

[0079] That is to say, the process of message matching can be executed by the blockchain, or it can also be executed by the smart contract, and this application does not limit this. The process of message matching is the process of searching the transaction information of the target transaction operation in the secure transaction record of the protected user for the user information of the traded user. If the information is found, the matching result is a successful match, and if not found, the matching result is a failed match.

[0080] Step 706: When the matching result indicates that the match is successful, the smart contract sends a transaction permission instruction to the second card application, so that the second card application releases the application guard service.

[0081] Indicatively, if the application guard service in the second card application is a full-screen pop-up window, after receiving the transaction permission instruction sent by the smart contract, the second card application can unlock the current full-screen pop-up window, so that the guarded user can continue to perform transaction operations.

[0082] Since the smart contract may send multiple transaction permission instructions to the second card application in response to the verification requests received from different first card applications, in this case, the second card application obtains the service status of the current application guardian service. If the current application guardian service has not been released, the application guardian service is released. If the current application guardian service has been released, no processing is performed.

[0083] Step 707: The smart contract feeds back the matching result to the first card application, and accordingly, the first card application receives the matching result.

[0084] The smart contract can feed back the matching result to each first card application. When the matching result indicates a successful match, each first card application updates the stored historical transaction record of the protected user. When the matching result indicates a failed match, each first card application can send a transaction prompt message to the protected user. Optionally, each first card application can assemble an active command Displaytext based on the received operation information of the target transaction operation, and display the transaction prompt message in a pop-up window. Fig. 9 A schematic diagram of a transaction reminder pop-up window provided by an exemplary embodiment of the present application is shown. Fig. 9 As shown, the transaction prompt pop-up window displays transaction prompt information 910 and operation controls 920 (including cancel controls and confirmation controls). Each first card application feeds back transaction permission instructions or transaction risk warning information to the second card application based on the operation of the corresponding guardian user on the transaction prompt pop-up window; wherein, when the guardian user selects the cancel control, or no operation on the transaction prompt pop-up window is received within the second target time period, the corresponding first card application sends the transaction risk warning information to the second card application through the TSM platform; after the guardian user selects the confirmation control, the corresponding first card application sends the transaction permission instruction to the second card application through the TSM platform, and triggers the update process of the security transaction record of the protected user, so as to store the user information of the traded user corresponding to the current target transaction operation into the security transaction record of the protected user, so that the transaction operation between the protected user and the traded user can be verified later through the protected user's Aquan transaction record, thereby improving the efficiency of subsequent verification.

[0085] Step 708, after determining that the matching result indicates a matching failure and receiving the transaction confirmation operation from the protected user, the first card application sends a transaction permission instruction to the second card application, so that the second card application releases the application protection service, and constructs record update data based on the first hash value corresponding to the first record update number of the protected user stored locally and the transaction information of the target transaction operation.

[0086] In a possible implementation, the process of constructing record update data can be implemented as follows: Encrypt the user information being traded based on the random number sent by the smart contract; Constructing update data based on the encrypted traded user information and the first hash value; After the update data is encrypted using the private key stored locally, the record update data is obtained.

[0087] The random number is sent by the smart contract to the first card application when the matching result indicates a matching failure. The random numbers sent by the smart contract to different first card applications are different. Taking the process of constructing record update data of one of the first card applications as an example, when the matching result of the smart contract indicates a matching failure, a random number v is generated and fed back to the first card application together with the matching result of the matching failure; if the first card application receives a transaction cancellation operation from the guardian user, the random number v is discarded; if the first card application receives a transaction confirmation operation from the guardian user, the encryption parameter m is calculated based on the random number v. , based on the encryption parameter m, the user information X of the traded user is encrypted to obtain the encrypted user information X of the traded user m , where g is a generator of a multiplication cyclic group of prime order; the first card application queries the locally stored first record update number c for the protected user, that is, the first record update number refers to the number of updates of the current card application to the protected user's security transaction record; calculate the first hash value H of the update number c c ; The first card application will be the first hash value H c And the encrypted user information X of the traded user m Combine and construct update data P, , then, through the locally stored private key , encrypt the update data P to obtain the record update data E, 。

[0088] The private key stored in the first card application is a pair of public and private keys pre-generated in the corresponding SIM card, namely, the public key and private key , the card application can use the public key Public on the blockchain, private key Always saved locally on the SIM card, and the private key It is invisible to the outside world, achieving the effect of "the key does not leave the SIM card".

[0089] Step 709: Send a record update request containing record update data to the smart contract. Correspondingly, the smart contract receives the record update request.

[0090] Step 710: The smart contract calculates a second hash value based on the number of times the second record of the protected user is updated by the stored protecting user.

[0091] The smart contract stores the number of times each guardian user corresponding to each first card application updates the security transaction record of the protected user, that is, the number of second record updates corresponding to each first card application. For example, the number of second record updates of the security transaction record of the protected user A by the guardian user B corresponding to card application B is 5 times, and the number of second record updates of the security transaction record of the protected user A by the guardian user B corresponding to card application D is 3 times, etc. After querying the number of second record updates, the smart contract performs hash calculation to obtain the second hash value.

[0092] Step 711, when the smart contract determines that the first hash value extracted from the record update request matches the second hash value, the smart contract updates the secure transaction record of the protected user based on the transaction information of the target transaction operation.

[0093] The process of extracting the first hash value by the smart contract can be implemented as follows: Get the record update data in the record update request; The record update data is decrypted by the public key to extract the first hash value; the public key is queried based on the user information of the guardian user included in the record update request.

[0094] The public key can be obtained by the first card application from the blockchain based on the user information of the guarding user. After the first card application decrypts the record update data E through the public key, it obtains the plaintext update data P, extracts the first hash value from it, compares the first hash value and the second hash value, and when the first hash value matches the second hash value, obtains the encryption parameter m based on the corresponding random number v, and the update data P is encrypted with the encrypted user information X of the transaction user based on the encryption parameter. m After decryption, the user information of the traded user is obtained, and then the user information of the traded user is updated to the secure transaction record of the protected user stored in the blockchain.

[0095] Optionally, after the smart contract completes the update operation of the security transaction record, it can also feedback the record update result to the first card application of the guardian user. Accordingly, the first card application receives the record update result; when the record update result indicates that the record update is successful, the locally stored first record update number is updated. Schematically, after the card application B corresponding to the guardian user B completes the update of the security transaction record of the protected user through the above process, when the received record update result indicates that the record update is successful, it adds 1 to the current first record update number, for example, updating the first record update number 5 to 6.

[0096] Through the above method, the identity of the guardian user who initiates the record update request can be verified based on the hash value of the number of times the guardian user updates the security transaction record of the protected user, thereby avoiding illegal updates by illegal users. In addition, combined with the "key does not come out of the card" capability of the SIM card, the data on the chain can be prevented from being intercepted and tampered with, thereby maintaining the security transaction records of the protected user while ensuring the credibility of the security transaction records of the protected user.

[0097] To summarize, the transaction security management method provided in the embodiment of the present application is that, when a guardian relationship is established between the guardian user and the protected user, the first card application corresponding to the guardian user sends a verification request to the smart contract after receiving the transaction information of the target transaction operation sent by the second card application corresponding to the protected user, so that the smart contract matches the transaction information of the target transaction operation with the security transaction record of the protected user, and feeds back the matching result to the first card application; after the matching result indicates a match failure and the transaction confirmation operation of the guardian user is received, record update data is constructed based on the first hash value corresponding to the first record update number of the protected user stored locally and the transaction information of the target transaction operation, and a record update request containing the record update data is sent to the smart contract, so that when the smart contract determines that the first hash value extracted from the record update request matches the second hash value, the smart contract updates the security transaction record of the protected user based on the transaction information of the target transaction operation. Through the above method, in the scenario where the guarding user performs security protection on the transaction operations of the protected user, when the security transaction record of the protected user needs to be updated, the card application that sends the record update request can be authenticated by using the hash value corresponding to the record update number to ensure the security of the record update, thereby ensuring the accuracy of the transaction operation protection based on the security transaction record, and further ensuring the transaction security of the protected user.

[0098] For example, a protected user establishes a protection relationship with two protecting users. Fig.10 The interactive schematic diagram of a transaction security management method provided by an exemplary embodiment of the present application is shown. The method is interactively executed by the card application B corresponding to the guarding user B, the card application D corresponding to the guarding user D, the card application A corresponding to the guarded user A, the TSM platform, the smart contract and the blockchain, as shown in FIG. Fig.10 As shown, the process may include a guardian relationship establishment phase and a guardian phase; Among them, in the guardian relationship establishment stage: S1001, card application A activates the "Others Guardian" function.

[0099] After activating the "Guardian of Others" function, the protected user can set multiple users as the users to be protected. Fig.10The card applications of the guardian user who has confirmed to establish a guardian relationship with the protected user, namely card application B and card application D, are shown. The card applications of the guardian user who has not confirmed to establish a guardian relationship with the protected user are not shown.

[0100] S1002, card application A sends a guardian relationship establishment request to the TSM platform.

[0101] S1003, the TSM platform sends a guardian relationship establishment request to each card application with which a guardian relationship is to be established.

[0102] S1004, each card application for which a guardian relationship is to be established feeds back operation information to the TSM platform, where the operation information indicates confirmation or cancellation.

[0103] Among them, the operation information fed back by card application B and card application D to the TSM platform indicates confirmation of establishing the guardian relationship.

[0104] S1005, the TSM platform establishes a guardian relationship based on the received confirmation operation information.

[0105] The binding relationships established by the TSM platform are: protected user A-guarding user B, protected user A-guarding user D.

[0106] S1006, the TSM platform sends the established guardian relationship to the smart contract for storage.

[0107] S1007, the TSM platform instructs the card application of the guardian user to activate the "Guard Others" function.

[0108] In the guarding stage, taking the transaction operation performed by the guarded user as transferring money to the traded user and the application protection service as displaying full-screen bullet screen as an example, the process can be implemented as follows: S1008, when the guarding conditions are met, card application A displays a full-screen pop-up window and triggers the "guarding by others" function.

[0109] S1009, card application A sends transfer information to card application B and card application D respectively through the TSM platform.

[0110] S1010, card application B and card application D respectively send a verification request to the smart contract, and the verification request includes the transfer information.

[0111] S1011, the smart contract sends a matching request to the blockchain, and the matching request includes transfer information; The matching request is used to instruct the blockchain to match the transfer information with the protected user's security transaction records.

[0112] S1012, the blockchain feeds back the matching result to the smart contract.

[0113] S1013, when the matching result indicates that the match is successful, the smart contract sends a transaction permission instruction to card application A, and feeds back the matching result to card application B and card application D.

[0114] S1014, when the matching result indicates that the matching fails, the smart contract feeds back the matching result to the card application B and the card application D.

[0115] S1015, card application B and card application D pop up windows and obtain the corresponding pop-up window operation of the guard user.

[0116] Assume that card application B receives the confirmation operation of guardian user B, and card application D does not receive the confirmation operation of guardian user D. The following interaction is performed by card application B.

[0117] S1016, card application B sends a transaction permission instruction to card application A.

[0118] S1017, card application A cancels the full-screen pop-up window.

[0119] S1018, card application B constructs record update data.

[0120] The record update data includes the first hash value of the first record update times of the protected user stored locally by the card application B and the encrypted user information of the current transaction user.

[0121] S1019, card application B sends a record update request containing record update data to the smart contract.

[0122] S1020, the smart contract matches the first hash value with the second hash value.

[0123] The second hash value is obtained by performing a hash calculation on the second record update number of the protected user by the smart contract based on the card application B stored therein.

[0124] S1021, when the first hash value and the second hash value match successfully, the smart contract updates the user information of the traded user contained in the record update data to the secure transaction record of the protected user stored in the blockchain.

[0125] Based on the embodiment shown in the figure, Fig.11 FIG. 1 is a schematic diagram showing a secure transaction record update process provided by an exemplary embodiment of the present application, which process can be interactively executed by a card application B, a smart contract, and a blockchain, such as Fig.11 As shown, the process can be implemented as: S1101, when the matching result indicates a matching failure, the smart contract generates and sends a random number and a matching result to the card application.

[0126] S1102: When the card application B determines that the matching result indicates a matching failure, it displays a transaction prompt pop-up window.

[0127] S1103, after receiving the confirmation operation based on the transaction prompt pop-up window, card application B calculates encryption parameters based on random numbers.

[0128] S1104, card application B encrypts the user information of the transaction user by using encryption parameters to obtain encrypted user information.

[0129] S1105, card application B locally queries the update times of the first record and calculates a first hash value.

[0130] S1106: Card application B combines the first hash value and the encrypted user information to construct update data.

[0131] S1106, card application B uses the locally stored private key to encrypt the update data to obtain record update data.

[0132] S1107, card application B sends the record update data to the smart contract via a record update request.

[0133] S1108, the smart contract decrypts the record update data according to the public key obtained by querying the user information corresponding to the card application B to obtain the updated data.

[0134] S1109, the smart contract queries the second update times of the protected user by the card application B and calculates the second hash value.

[0135] S1110, the smart contract determines whether the first hash value is consistent with the second hash value. If so, execute S1111, otherwise, end the operation.

[0136] S1111, the smart contract decrypts the encrypted user information.

[0137] S1112, the smart contract sends an update request to the blockchain based on the decrypted user information.

[0138] S1113, based on the update request, the blockchain adds the user information of the transacted user to the secure transaction record of the protected user.

[0139] Fig.12 A block diagram of a transaction security management device provided by an exemplary embodiment of the present application is shown. The device is applied in a first card application corresponding to a guarding user. A guarding relationship is established between the guarding user and the guarded user, such as Fig.12 As shown, the device comprises: The first request sending module 1210 is used to send a verification request to the smart contract when receiving the transaction information of the target transaction operation sent by the second card application corresponding to the protected user; the verification request is used to instruct the smart contract to match the transaction information of the target transaction operation with the security transaction record of the protected user; The data construction module 1220 is used to construct record update data based on the first hash value corresponding to the first record update number of the protected user and the transaction information of the target transaction operation stored locally after the matching result fed back by the smart contract indicates a matching failure and the transaction confirmation operation of the guarding user is received; The second request sending module 1230 is used to send a record update request containing the record update data to the smart contract, so that the smart contract updates the security transaction record of the protected user based on the transaction information of the target transaction operation when it is determined that the first hash value extracted from the record update request matches the second hash value; the second hash value is obtained by the smart contract through hash calculation of the second record update number of the protected user based on the stored guarding user.

[0140] In a possible implementation, the transaction information of the target transaction operation includes information of the user being traded; the data construction module 1210 includes: A first encryption submodule, used to encrypt the traded user information based on a random number sent by the smart contract; A data construction submodule, used to construct update data based on the encrypted traded user information and the first hash value; The second encryption submodule is used to encrypt the update data using a locally stored private key to obtain the record update data.

[0141] In a possible implementation manner, the device further includes: A first receiving module, used to receive the record update result fed back by the smart contract; The data updating module is used to update the first record update number stored locally when the record update result indicates that the record update is successful.

[0142] In a possible implementation, the secure transaction record of the protected user is the intersection of a first transaction record provided by the protected user and a second transaction record provided by the protecting user; the second transaction record is obtained after updating the first transaction record.

[0143] In a possible implementation manner, the device further includes: The first instruction sending module is used to send a transaction permission instruction to the second card application after receiving the transaction confirmation operation of the guardian user, so that the second card application releases the application guardian service; the application guardian service is used to interrupt the target transaction operation when the transaction information of the target transaction operation meets the guardian condition.

[0144] To summarize, in the transaction security management device provided by the embodiment of the present application, when a guardian relationship is established between the guardian user and the protected user, the first card application corresponding to the guardian user sends a verification request to the smart contract after receiving the transaction information of the target transaction operation sent by the second card application corresponding to the protected user, so that the smart contract matches the transaction information of the target transaction operation with the security transaction record of the protected user, and feeds back the matching result to the first card application; after the matching result indicates a match failure and the transaction confirmation operation of the guardian user is received, record update data is constructed based on the first hash value corresponding to the first record update number of the protected user stored locally and the transaction information of the target transaction operation, and a record update request containing the record update data is sent to the smart contract, so that when the smart contract determines that the first hash value extracted from the record update request matches the second hash value, the smart contract updates the security transaction record of the protected user based on the transaction information of the target transaction operation. Through the above-mentioned device, in a scenario where the guarding user performs security protection on the transaction operations of the protected user, when the security transaction records of the protected user need to be updated, the card application that sends the record update request can be authenticated by using the hash value corresponding to the record update number to ensure the security of the record update, thereby ensuring the accuracy of the transaction operation protection based on the security transaction records, and further ensuring the transaction security of the protected user.

[0145] Fig.13 A block diagram of a transaction security management device provided by an exemplary embodiment of the present application is shown, and the device is applied in a smart contract, and the smart contract stores the guardianship relationship between the guardian user and the protected user; Fig.13 As shown, the device comprises: The second receiving module 1310 is used to receive a verification request sent by the first card application corresponding to the guarding user; the verification request includes transaction information of a target transaction operation; the target transaction operation is a transaction operation performed in the second card application corresponding to the guarded user; A matching module 1320, configured to match the transaction information of the target transaction operation with the security transaction record of the protected user based on the verification request to obtain a matching result; A result feedback module 1330, configured to feed back the matching result to the first card application; The third receiving module 1340 is used to receive a record update request including record update data sent by the first card application; the record update data is constructed by the first card application based on the first hash value corresponding to the first record update number of the protected user and the transaction information of the target transaction operation stored locally after the matching result indicates a match failure and the first card application receives a transaction confirmation operation of the protected user; A calculation module 1350, configured to calculate a second hash value based on the stored number of times the guarding user updates the second record of the guarded user; The record update module 1360 is used to update the security transaction record of the protected user based on the transaction information of the target transaction operation when it is determined that the first hash value extracted from the record update request matches the second hash value.

[0146] In a possible implementation, the protected user's security transaction record is stored in a blockchain, and the matching module 1320 includes: A request sending submodule, used to send a matching request to the blockchain based on the verification request; the matching request is used to instruct the blockchain to match the transaction information of the target transaction operation with the security transaction record of the protected user; The result receiving submodule is used to receive the matching result fed back by the blockchain.

[0147] In a possible implementation manner, the device further includes: A data acquisition module, used for acquiring the record update data in the record update request; A decryption module is used to decrypt the record update data through a public key to extract the first hash value; the public key is queried based on the user information of the guardian user included in the record update request.

[0148] In a possible implementation manner, the device further includes: The second instruction sending module is used to send a transaction permission instruction to the second card application when the matching result indicates that the matching is successful, so that the second card application releases the application guard service.

[0149] In a possible implementation, the application guard service includes at least one of the following: turning off the SMS display function, locking the camera, locking the fingerprint sensor, and displaying a full-screen pop-up window.

[0150] To summarize, in the transaction security management device provided by the embodiment of the present application, when a guardian relationship is established between the guardian user and the protected user, the first card application corresponding to the guardian user sends a verification request to the smart contract after receiving the transaction information of the target transaction operation sent by the second card application corresponding to the protected user, so that the smart contract matches the transaction information of the target transaction operation with the security transaction record of the protected user, and feeds back the matching result to the first card application; after the matching result indicates a match failure and the transaction confirmation operation of the guardian user is received, record update data is constructed based on the first hash value corresponding to the first record update number of the protected user stored locally and the transaction information of the target transaction operation, and a record update request containing the record update data is sent to the smart contract, so that when the smart contract determines that the first hash value extracted from the record update request matches the second hash value, the smart contract updates the security transaction record of the protected user based on the transaction information of the target transaction operation. Through the above-mentioned device, in a scenario where the guarding user performs security protection on the transaction operations of the protected user, when the security transaction records of the protected user need to be updated, the card application that sends the record update request can be authenticated by using the hash value corresponding to the record update number to ensure the security of the record update, thereby ensuring the accuracy of the transaction operation protection based on the security transaction records, and further ensuring the transaction security of the protected user.

[0151] Fig.14 The structural block diagram of a computer device 1400 shown in an exemplary embodiment of the present application is shown. The computer device can be implemented as the TSM platform in the above-mentioned solution of the present application. The computer device 1400 includes a central processing unit (CPU) 1401, a system memory 1404 including a random access memory (RAM) 1402 and a read-only memory (ROM) 1403, and a system bus 1405 connecting the system memory 1404 and the central processing unit 1401. The computer device 1400 also includes a large-capacity storage device 1406 for storing an operating system 1409, an application program 1410, and other program modules 1411.

[0152] Without loss of generality, the computer-readable medium may include computer storage media and communication media. Computer storage media include volatile and non-volatile, removable and non-removable media implemented by any method or technology for storing information such as computer-readable instructions, data structures, program modules or other data. Computer storage media include RAM, ROM, Erasable Programmable Read Only Memory (EPROM), Electronically-Erasable Programmable Read-Only Memory (EEPROM) flash memory or other solid-state storage technology, CD-ROM, Digital Versatile Disc (DVD) or other optical storage, tape cassettes, tapes, disk storage or other magnetic storage devices. Of course, those skilled in the art will know that the computer storage medium is not limited to the above. The above-mentioned system memory 1404 and mass storage device 1406 can be collectively referred to as memory.

[0153] According to various embodiments provided by the embodiments of the present application, the computer device 1400 can also be connected to a remote computer on the network through a network such as the Internet. That is, the computer device 1400 can be connected to the network 1408 through the network interface unit 1407 connected to the system bus 1405, or the network interface unit 1407 can be used to connect to other types of networks or remote computer systems (not shown).

[0154] The memory also includes at least one instruction, at least one program, code set or instruction set, and the at least one instruction, at least one program, code set or instruction set is stored in the memory. The central processing unit 1401 implements all or part of the steps in the transaction security management method shown in the above-mentioned embodiments by executing the at least one instruction, at least one program, code set or instruction set.

[0155] Fig.15 The following is a block diagram of a computer device 1500 according to an exemplary embodiment of the present application. The computer device 1500 may be implemented as the above-mentioned user terminal device, in which a SIM card is configured, and a card application for security protection is installed in the SIM card. For example, the user terminal device may be implemented as a smart phone, a tablet computer, a laptop computer, a desktop computer, etc. The computer device 1500 may also be referred to as a user device, a portable terminal, a laptop terminal, a desktop terminal, or other names.

[0156] Typically, the computer device 1500 includes a processor 1501 and a memory 1502 .

[0157] In some embodiments, the computer device 1500 may also optionally include: a peripheral device interface 1503 and at least one peripheral device. The processor 1501, the memory 1502 and the peripheral device interface 1503 may be connected via a bus or a signal line. Each peripheral device may be connected to the peripheral device interface 1503 via a bus, a signal line or a circuit board. Specifically, the peripheral device includes: at least one of a radio frequency circuit 1504, a display screen 1505, a camera assembly 1506, an audio circuit 1507 and a power supply 1508.

[0158] In some embodiments, the computer device 1500 further includes one or more sensors 1509 , including but not limited to: an acceleration sensor 1510 , a gyroscope sensor 1511 , a pressure sensor 1512 , an optical sensor 1513 , and a proximity sensor 1514 .

[0159] Those skilled in the art will understand that Fig.15 The structure shown in the figure does not constitute a limitation on the computer device 1500, and the computer device 1500 may include more or less components than shown in the figure, or combine some components, or adopt a different arrangement of components.

[0160] In an exemplary embodiment, a computer-readable storage medium is also provided, in which at least one computer program is stored, and the computer program is loaded and executed by a processor to implement all or part of the steps in the above transaction security management method. For example, the computer-readable storage medium can be a read-only memory (ROM), a random access memory (RAM), a compact disc (CD-ROM), a magnetic tape, a floppy disk, an optical data storage device, etc.

[0161] In an exemplary embodiment, a computer program product is also provided, the computer program product comprising a computer program stored on a non-transitory computer-readable storage medium, the computer program comprising program instructions, when the program instructions are executed by a computer, the computer is executed to implement the above Figure 1 , Figure 3 , Figure 7 , Fig.10 or Fig.11 All or part of the steps of the illustrated embodiment.

[0162] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary techniques in the art that are not disclosed in the present application. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the claims.

[0163] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A transaction security management method, characterized in that: The method is executed by a first card application corresponding to a guarding user, a guarding relationship is established between the guarding user and the guarded user, and the method includes: Upon receiving the transaction information of the target transaction operation sent by the second card application corresponding to the protected user, sending a verification request to the smart contract; the verification request is used to instruct the smart contract to match the transaction information of the target transaction operation with the security transaction record of the protected user; After the matching result fed back by the smart contract indicates a matching failure and a transaction confirmation operation of the guarding user is received, record update data is constructed based on the first hash value corresponding to the first record update number of the guarded user and the transaction information of the target transaction operation stored locally; A record update request including the record update data is sent to the smart contract, so that the smart contract updates the secure transaction record of the protected user based on the transaction information of the target transaction operation when it is determined that the first hash value extracted from the record update request matches the second hash value; the second hash value is obtained by the smart contract through hash calculation based on the stored number of second record updates of the protected user by the protecting user.

2. The method according to claim 1, characterized in that The transaction information of the target transaction operation includes the traded user information; the first Hash value of the first record update number of the protected user stored locally and the transaction information of the target transaction operation are used to construct the record update data, including: Encrypting the traded user information based on the random number sent by the smart contract; Constructing update data based on the encrypted traded user information and the first hash value; The record update data is obtained by encrypting the update data using a private key stored locally.

3. The method according to claim 2, characterized in that The method further comprises: Receive the record update result fed back by the smart contract; When the record update result indicates that the record update is successful, the first record update number stored locally is updated.

4. The method according to claim 1, characterized in that: The secure transaction record of the protected user is the intersection of a first transaction record provided by the protected user and a second transaction record provided by the protecting user; the second transaction record is obtained after updating the first transaction record.

5. The method according to claim 1, characterized in that The method further comprises: After receiving the transaction confirmation operation from the guardian user, a transaction permission instruction is sent to the second card application so that the second card application releases the application guardian service; the application guardian service is used to interrupt the target transaction operation when the transaction information of the target transaction operation meets the guardian condition.

6. A transaction security management method, characterized in that: The method is executed by a smart contract, in which the guardianship relationship between the guardian user and the protected user is stored; the method comprises: Receiving a verification request sent by a first card application corresponding to the guarding user; the verification request includes transaction information of a target transaction operation; the target transaction operation is a transaction operation performed in a second card application corresponding to the guarded user; Matching the transaction information of the target transaction operation with the security transaction record of the protected user based on the verification request to obtain a matching result; Feedback the matching result to the first card application; receiving a record update request including record update data sent by the first card application; the record update data is constructed by the first card application based on a first hash value corresponding to a first record update number of the protected user stored locally and transaction information of the target transaction operation after the matching result indicates a match failure and the first card application receives a transaction confirmation operation of the protected user; Calculate a second hash value based on the number of times the second record of the protected user is updated by the protected user; When it is determined that the first hash value extracted from the record update request matches the second hash value, the secure transaction record of the protected user is updated based on the transaction information of the target transaction operation.

7. The method according to claim 6, characterized in that The secure transaction record of the protected user is stored in the blockchain, and the transaction information of the target transaction operation based on the verification request is matched with the secure transaction record of the protected user to obtain a matching result, including: Sending a matching request to the blockchain based on the verification request; the matching request is used to instruct the blockchain to match the transaction information of the target transaction operation with the secure transaction record of the protected user; Receive the matching result fed back by the blockchain.

8. The method according to claim 6, characterized in that The method further comprises: Obtaining the record update data in the record update request; The record update data is decrypted by a public key to extract the first hash value; the public key is queried based on the user information of the guardian user included in the record update request.

9. The method according to claim 6, characterized in that The method further comprises: When the matching result indicates that the match is successful, a transaction permission instruction is sent to the second card application, so that the second card application releases the application guard service.

10. The method according to claim 9, characterized in that The application guard service includes at least one of the following: turning off the SMS display function, locking the camera, locking the fingerprint sensor, and displaying a full-screen pop-up window.

11. A transaction security management method, characterized in that: The device is applied in the first card application corresponding to the guarding user, and a guarding relationship is established between the guarding user and the guarded user. The device includes: A first request sending module is used to send a verification request to the smart contract when receiving the transaction information of the target transaction operation sent by the second card application corresponding to the protected user; the verification request is used to instruct the smart contract to match the transaction information of the target transaction operation with the security transaction record of the protected user; A data construction module, configured to construct record update data based on a first hash value corresponding to a first record update number of the protected user and transaction information of the target transaction operation stored locally after the matching result fed back by the smart contract indicates a matching failure and a transaction confirmation operation of the guarding user is received; A second request sending module is used to send a record update request containing the record update data to the smart contract, so that the smart contract updates the secure transaction record of the protected user based on the transaction information of the target transaction operation when it is determined that the first hash value extracted from the record update request matches the second hash value; the second hash value is obtained by the smart contract through hash calculation based on the stored number of times the protecting user updates the second record of the protected user.

12. A transaction security management device, characterized in that: The device is applied in a smart contract, and the smart contract stores the guardianship relationship between the guardian user and the protected user; the device includes: A second receiving module is used to receive a verification request sent by the first card application corresponding to the guarding user; the verification request includes transaction information of a target transaction operation; the target transaction operation is a transaction operation performed in the second card application corresponding to the guarded user; A matching module, configured to match the transaction information of the target transaction operation with the security transaction record of the protected user based on the verification request to obtain a matching result; A result feedback module, used for feeding back the matching result to the first card application; A third receiving module is configured to receive a record update request including record update data sent by the first card application; the record update data is constructed by the first card application based on the first hash value corresponding to the first record update number of the protected user and the transaction information of the target transaction operation stored locally after the matching result indicates a match failure and the first card application receives a transaction confirmation operation of the protected user; A calculation module, configured to calculate a second hash value based on the number of times the second record of the protected user is updated by the protected user; A record update module is used to update the security transaction record of the protected user based on the transaction information of the target transaction operation when it is determined that the first hash value extracted from the record update request matches the second hash value.

13. A computer device, characterized in that: The computer device includes a processor and a memory, the memory stores at least one computer program, and the at least one computer program is loaded and executed by the processor to implement the transaction security management method as described in any one of claims 1 to 10.

14. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores at least one computer program, and the computer program is loaded and executed by a processor to implement the transaction security management method according to any one of claims 1 to 10.

15. A computer program product, characterized in that The computer program product includes a computer program stored on a non-transitory computer-readable storage medium, and the computer program includes program instructions. When the program instructions are executed by a computer, the computer is caused to execute to implement the transaction security management method as described in any one of claims 1 to 10.

Images