Resource transfer method, device and equipment and computer readable storage medium

Abstract

The invention discloses a resource transfer method, device and equipment and a computer readable storage medium, and belongs to the technical field of computers. The method comprises the following steps: receiving a resource transfer request sent by terminal equipment of a resource transfer object, wherein the resource transfer request comprises an object identifier of the resource transfer object, an object identifier of a resource receiving object and a resource transfer numerical value; sending a verification request to a terminal device of a verification object of the resource transfer object, wherein the verification request comprises an object identifier of the resource transfer object; receiving a verification result returned by the terminal equipment of the verification object; and under the condition that the verification result meets the verification requirement, transferring the resource of the resource transfer numerical value from the account of the resource transfer object to the account of the resource receiving object. According to the method, the verification object of the resource transfer object participates in the resource transfer transaction process of the resource transfer object, the risk of an account of the resource transfer object can be reduced, and the security of resource transfer is improved.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a resource transfer method, apparatus, device, and computer-readable storage medium. Background Technology

[0002] With the continuous development of computer technology, resource transfer has become a very common phenomenon in people's daily lives, and more and more applications provide resource transfer functions.

[0003] In related technologies, during the process of transferring resources from a resource transferor to a resource recipient, if the resource transferor's input password is correct, the resource transfer client signs the transaction information using the resource transferor's private key to obtain signed transaction information. This transaction information includes the recipient's object identifier and the transferred resource value. The resource transfer client then sends a transaction request to the server, which includes the resource transferor's object identifier and the signed transaction information. The server receives the transaction request, verifies the signed transaction information using the resource transferor's public key, obtains the transaction information, and then transfers the transferred resource value from the resource transferor's account to the recipient's account.

[0004] However, in the above-mentioned resource transfer methods, resources can still be transferred to the resource recipient even if the private key of the resource transfer recipient is leaked, putting the account of the resource transfer recipient at high risk and resulting in low security for resource transfer. Summary of the Invention

[0005] This application provides a resource transfer method, apparatus, device, and computer-readable storage medium, which can be used to solve the problems of high-risk accounts and low security of resource transfer in related technologies. The technical solution includes the following.

[0006] In a first aspect, embodiments of this application provide a resource transfer method, the method comprising:

[0007] A resource transfer request sent by a terminal device that receives a resource transfer object, wherein the resource transfer request includes the object identifier of the resource transfer object, the object identifier of the resource receiving object, and the resource transfer value;

[0008] Send a verification request to the terminal device of the verification object of the resource transfer object, the verification request including the object identifier of the resource transfer object;

[0009] Receive the verification result returned by the terminal device of the verification object;

[0010] If the verification result meets the verification requirements, the resources of the resource transfer value are transferred from the account of the resource transfer object to the account of the resource receiving object.

[0011] Secondly, embodiments of this application provide a resource transfer method, the method comprising:

[0012] The resource transfer page displays the object identifier of the resource receiving object and the resource transfer value;

[0013] When the resource transfer function is triggered, a resource transfer request is sent to the server. The resource transfer request is used by the server to send a verification request to the terminal device of the verification object of the resource transfer object, receive the verification result returned by the terminal device of the verification object, and if the verification result meets the verification requirements, transfer the resources of the resource transfer value from the account of the resource transfer object to the account of the resource receiving object.

[0014] The resource transfer request includes the object identifier of the resource transfer object, the object identifier of the resource receiving object, and the resource transfer value, and the verification request includes the object identifier of the resource transfer object.

[0015] Thirdly, embodiments of this application provide a resource transfer method, the method comprising:

[0016] Receive a verification request sent by the server, the verification request including the object identifier of the resource transfer object;

[0017] Based on the verification request, a verification page is displayed, which displays the object identifier of the resource transfer object;

[0018] In response to a triggered action on the verification page, obtain the verification result;

[0019] The server sends the verification result, which is used by the server to transfer the resource transfer value from the resource transfer object's account to the resource receiving object's account if the verification result meets the verification requirements.

[0020] Fourthly, embodiments of this application provide a resource transfer apparatus, the apparatus comprising:

[0021] The receiving module is used to receive a resource transfer request sent by the terminal device of the resource transfer object. The resource transfer request includes the object identifier of the resource transfer object, the object identifier of the resource receiving object, and the resource transfer value.

[0022] The sending module is configured to send a verification request to the terminal device of the verification object of the resource transfer object, wherein the verification request includes the object identifier of the resource transfer object;

[0023] The receiving module is also used to receive the verification result returned by the terminal device of the verification object;

[0024] The transfer module is used to transfer the resources of the resource transfer value from the account of the resource transfer object to the account of the resource receiving object when the verification result meets the verification requirements.

[0025] In one possible implementation, the device further includes:

[0026] The determination module is used to determine the risk level of a resource transfer transaction based on at least one of the object identifier of the resource transfer object, the object identifier of the resource receiving object, or the resource transfer value.

[0027] The sending module is used to send a verification request to the terminal device of the verification object of the resource transfer object when the risk level is greater than the level threshold.

[0028] In one possible implementation, the sending module is configured to send a risk warning message to the terminal device of the resource transfer object when the risk level is greater than a level threshold; and to send a verification request to the terminal device of the verification object of the resource transfer object when receiving an indication message returned by the terminal device of the resource transfer object.

[0029] In one possible implementation, the determining module is further configured to: determine a ratio corresponding to the risk level when the risk level is greater than a level threshold, wherein the risk level and the ratio are positively correlated; determine a target quantity based on the number of contact objects of the resource transfer object and the ratio; and determine the verification object among the contact objects, wherein the number of the verification object is the target quantity.

[0030] In one possible implementation, the determining module is configured to sort the contact objects according to a target order based on the response duration of each contact object, and obtain a sorting result. The response duration of any contact object is used to indicate the time between sending a verification request to the contact object and receiving the verification result returned by the contact object. The contact objects that are ranked before the target number in the sorting result are determined as the verification objects.

[0031] In one possible implementation, the receiving module is configured to receive verification information returned by the terminal device of the verification object, the verification information including the object identifier and target information of the verification object, the target information being information obtained by signing the verification result according to the private key of the verification object; determining the public key of the verification object according to the object identifier of the verification object; and verifying the signature of the target information according to the public key of the verification object to obtain the verification result.

[0032] Fifthly, embodiments of this application provide a resource transfer apparatus, the apparatus comprising:

[0033] The display module is used to display the resource transfer page, which displays the object identifier of the resource receiving object and the resource transfer value;

[0034] The sending module is used to send a resource transfer request to the server when the resource transfer function is triggered. The resource transfer request is used by the server to send a verification request to the terminal device of the verification object of the resource transfer object, receive the verification result returned by the terminal device of the verification object, and transfer the resources of the resource transfer value from the account of the resource transfer object to the account of the resource receiving object if the verification result meets the verification requirements.

[0035] The resource transfer request includes the object identifier of the resource transfer object, the object identifier of the resource receiving object, and the resource transfer value, and the verification request includes the object identifier of the resource transfer object.

[0036] In one possible implementation, the display module is further configured to display the homepage of the resource transfer object, wherein the homepage displays a resource transfer control; and to display the resource transfer page in response to a trigger operation on the resource transfer control.

[0037] In one possible implementation, the homepage also displays a contact object control, which is used to obtain the contact object of the resource transfer object;

[0038] The display module is further configured to, in response to a trigger operation on the contact object control, display a contact object page, wherein the contact object page displays an add control; and in response to a trigger operation on the add control, display an add contact object page, wherein the add contact object page displays an object identifier box.

[0039] The device further includes:

[0040] The acquisition module is used to acquire the object identifier of the reference object based on the input operation in the object identifier box;

[0041] The sending module is further configured to send the object identifier of the reference object to the server when the add contact object function is triggered. The object identifier of the reference object is used by the server to use the reference object as the contact object of the resource transfer object.

[0042] In one possible implementation, the sending module is configured to send a first notification message to the terminal device of the reference object when the add function of the contact object is triggered, the first notification message being used to notify the reference object as the contact object of the resource transfer object; and upon receiving a confirmation message sent by the terminal device of the reference object, sending the object identifier of the reference object to the server, the confirmation message being used to instruct the reference object to confirm as the contact object of the resource transfer object.

[0043] In one possible implementation, the device further includes:

[0044] The receiving module is used to receive risk warning information returned by the server when the risk level is greater than the level threshold;

[0045] The display module is also used to display the risk warning information;

[0046] The sending module is further configured to send indication information to the server in response to a triggering operation for the risk warning information, the indication information being used by the server to send a verification request to the terminal device of the verification object.

[0047] In one possible implementation, the sending module is configured to display a resource transfer password interface when the resource transfer function is triggered, the resource transfer password interface being used by the resource transfer object to input a resource transfer password; obtain the resource transfer password based on the input operation in the resource transfer password interface; and send the resource transfer request to the server if the resource transfer password is verified.

[0048] Sixthly, embodiments of this application provide a resource transfer apparatus, the apparatus comprising:

[0049] A receiving module is used to receive a verification request sent by the server, wherein the verification request includes the object identifier of the resource transfer object;

[0050] The display module is used to display a verification page according to the verification request, wherein the verification page displays the object identifier of the resource transfer object;

[0051] The acquisition module is used to acquire the verification result in response to a trigger operation on the verification page;

[0052] The sending module is used to send the verification result to the server. The verification result is used by the server to transfer the resource transfer value from the account of the resource transfer object to the account of the resource receiving object when the verification result meets the verification requirements.

[0053] In one possible implementation, the acquisition module is further configured to sign the verification result based on the private key of the verification object to obtain target information;

[0054] The sending module is used to send verification information to the server. The verification information includes the object identifier of the verification object and the target information. The verification information is used by the server to verify the target information based on the public key of the verification object to obtain the verification result.

[0055] In a seventh aspect, embodiments of this application provide a computer device, the computer device including a processor and a memory, the memory storing at least one piece of program code, the at least one piece of program code being loaded and executed by the processor to enable the computer device to implement any of the resource transfer methods described above.

[0056] Eighthly, a computer-readable storage medium is also provided, wherein at least one piece of program code is stored therein, the at least one piece of program code being loaded and executed by a processor to enable a computer to implement any of the resource transfer methods described above.

[0057] In a ninth aspect, a computer program or computer program product is also provided, wherein the computer program or computer program product stores at least one computer instruction, the at least one computer instruction being loaded and executed by a processor to enable the computer to implement any of the above-described resource transfer methods.

[0058] The technical solution provided in this application has at least the following beneficial effects:

[0059] The technical solution provided in this application, upon receiving a resource transfer request from a resource transfer object, sends a verification request to the verification object of the resource transfer object. This verification object verifies the resource transfer transaction. Only if the verification result of the verification object meets the verification requirements is the resource transferred from the resource transfer object's account to the resource receiving object's account. This method requires the verification object of the resource transfer object to participate in and verify the resource transfer transaction. Even if the private key of the resource transfer object is leaked, any object that obtains the private key and attempts to transfer resources through the resource transfer object's account will still need to be verified by the verification object. This increases the difficulty of successful illegal resource transfers, reduces the success rate of malicious resource transfers, effectively prevents theft of the resource transfer object's account and fraudulent resource transfer transactions, reduces the risk to the resource transfer object's account, and thus improves the security of resource transfers. Attached Figure Description

[0060] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0061] Figure 1 This is a schematic diagram of a computer system provided in an embodiment of this application;

[0062] Figure 2 This is a flowchart of a resource transfer method provided in an embodiment of this application;

[0063] Figure 3 This is a schematic diagram showing the homepage of a resource transfer object provided in an embodiment of this application;

[0064] Figure 4 This is a schematic diagram illustrating the display of a resource transfer page provided in an embodiment of this application;

[0065] Figure 5 This is a schematic diagram illustrating another resource transfer page provided in an embodiment of this application;

[0066] Figure 6 This is a schematic diagram illustrating the display of a contact page provided in an embodiment of this application;

[0067] Figure 7 This is a schematic diagram illustrating the display of an "Add Contact" page provided in an embodiment of this application;

[0068] Figure 8This is a schematic diagram of a risk warning page provided in an embodiment of this application;

[0069] Figure 9 This is a schematic diagram showing a verification notification provided in an embodiment of this application;

[0070] Figure 10 This is a schematic diagram illustrating the display of a verification page provided in an embodiment of this application;

[0071] Figure 11 This is a schematic diagram illustrating the display of a notification message page provided in an embodiment of this application;

[0072] Figure 12 This is a flowchart of another resource transfer method provided in the embodiments of this application;

[0073] Figure 13 This is a flowchart of another resource transfer method provided in the embodiments of this application;

[0074] Figure 14 This is a flowchart of yet another resource transfer method provided in the embodiments of this application;

[0075] Figure 15 This is a flowchart of another resource transfer method provided in the embodiments of this application;

[0076] Figure 16 This is a schematic diagram of the structure of a resource transfer device provided in an embodiment of this application;

[0077] Figure 17 This is a schematic diagram of the structure of a resource transfer device provided in an embodiment of this application;

[0078] Figure 18 This is a schematic diagram of the structure of a resource transfer device provided in an embodiment of this application;

[0079] Figure 19 This is a schematic diagram of the structure of a terminal device provided in an embodiment of this application;

[0080] Figure 20 This is a schematic diagram of the structure of a server provided in an embodiment of this application. Detailed Implementation

[0081] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

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

[0083] First, the abbreviations and key terms involved in the embodiments of this application are defined.

[0084] Clients used for resource transfer: Clients that store resources, allowing users to send, receive, and manage their own resources.

[0085] Private key: A security mechanism, it is a string of secret numbers used for signing and ensuring the security of resource transfer.

[0086] Contact objects: During the resource transfer process, the objects that can be verified and confirmed when the risk level is detected to be greater than the level threshold.

[0087] Risk Level Detection: A risk level detection system for resource transfer transactions, used to determine the risk level of resource transfer transactions.

[0088] Signature verification: The process of verifying a digital signature using a public key to ensure that the signature was created by the person holding the corresponding private key, thereby verifying the validity of the resource transfer.

[0089] Figure 1 This is a schematic diagram of a computer system provided in an embodiment of this application, such as... Figure 1 As shown, the computer system includes: a first terminal device 101, a server 102, and a second terminal device 103.

[0090] In this embodiment, both the first terminal device 101 and the second terminal device 103 have a client installed and running for resource transfer. The first terminal device 101 is logged into a resource transfer object 104, and is the terminal device corresponding to the resource transfer object 104. The second terminal device 103 is logged into a verification object 105, and is the terminal device corresponding to the verification object 105. The resource transfer method provided in this application embodiment can be jointly executed by the first terminal device 101, the server 102, and the second terminal device 103; this application embodiment does not limit this.

[0091] Server 102 provides background services for clients performing resource transfers. In one possible implementation, server 102 undertakes the primary computational work, while the first terminal device 101 and the second terminal device 103 undertake secondary computational work. Alternatively, server 102 undertakes secondary computational work, while the first terminal device 101 and the second terminal device 103 undertake the primary computational work. Or, the first terminal device 101, server 102, and second terminal device 103 collaborate using a distributed computing architecture.

[0092] For example, the client used for resource transfer can be any type of client. It can be a client that needs to be downloaded and installed independently, or it can be an embedded program that depends on a host program to run. An embedded program is an application developed using a programming language that depends on a host program to run. Embedded programs do not require downloading and installation; they only need to be dynamically loaded into the host program to run. Embedded programs include, but are not limited to, applets. This application embodiment does not limit the type of client capable of resource transfer. Users can find the embedded program they need through searching, scanning, or other methods, open it, and run it. After use, closing it will not occupy the terminal device's memory, which is very convenient.

[0093] Optionally, the first terminal device 101 (second terminal device 103) can be any electronic device product capable of human-computer interaction with the user through one or more methods such as a keyboard, touchpad, remote control, voice interaction, or handwriting device. For example, the first terminal device 101 (second terminal device 103) can be a smartphone, tablet computer, laptop computer, desktop computer, smart speaker, smartwatch, PC (Personal Computer), mobile phone, PDA (Personal Digital Assistant), wearable device, PPC (Pocket PC), smart car system, smart TV, etc.

[0094] The term "first terminal device 101 (second terminal device 103)" can refer to one of a plurality of terminal devices. This embodiment uses only the first terminal device 101 (second terminal device 103) as an example. Those skilled in the art will understand that the number of the aforementioned first terminal devices 101 (second terminal devices 103) can be more or less. For example, there may be only one first terminal device 101 (second terminal device 103), or there may be dozens or hundreds, or even more, of the aforementioned first terminal devices 101 (second terminal devices 103). This application embodiment does not limit the number or type of the first terminal devices 101 (second terminal devices 103).

[0095] Server 102 can be a single server, a server cluster consisting of multiple servers, or any of the following: a cloud computing platform or a virtualization center. This embodiment of the application does not limit this. Server 102 communicates directly or indirectly with the first terminal device 101 and the second terminal device 103 via wired or wireless communication. Server 102 has data receiving, data processing, and data sending functions. Of course, server 102 may also have other functions, which are not limited in this embodiment of the application.

[0096] In an exemplary embodiment of this application, when the resource transfer object 104 wants to perform a resource transfer, the resource transfer object 104 triggers the client-related information displayed on the display interface of the first terminal device 101, so that the first terminal device 101 displays the homepage 106 of the resource transfer object. The homepage 106 of the resource transfer object displays a resource transfer control 107. The resource transfer object 104 triggers the resource transfer control 107, and then displays the resource transfer page 108. The resource transfer object 104 inputs the object identifier of the resource receiving object and the resource transfer value on the resource transfer page, so that the first terminal device 101 obtains the object identifier of the resource receiving object and the resource transfer value, and then the first terminal device 101 sends a resource transfer request to the server 102.

[0097] After receiving the resource transfer request, server 102 determines the risk level of the resource transfer transaction based on the request. If the risk level is greater than the threshold, server 102 determines the verification object of the resource transfer object and then sends a verification request to the second terminal device 103 corresponding to the verification object of the resource transfer object.

[0098] After receiving the verification request, the second terminal device 103 displays the verification page 109 according to the verification request. Based on the actions of the verification object on the verification page, the second terminal device 103 obtains the verification result. The second terminal device 103 then sends the verification result to the server 102.

[0099] After receiving the verification result, if the verification result meets the verification requirements, server 102 transfers the resource transfer value from the resource transfer object's account to the resource receiving object's account to complete the resource transfer.

[0100] Those skilled in the art should understand that the first terminal device 101, server 102 and second terminal device 103 described above are merely illustrative examples. Other existing or future terminal devices or servers that are applicable to this application should also be included within the scope of protection of this application, and are hereby incorporated by reference.

[0101] This application provides a resource transfer method, which can be applied to the above-mentioned... Figure 1 The computer system shown is, Figure 2 The flowchart shown in this embodiment of the present application illustrates a resource transfer method. This method can be implemented by... Figure 1 The interaction between the first terminal device 101, the server 102, and the second terminal device 103 is implemented. For example... Figure 2 As shown, the method includes the following steps.

[0102] In step 201, the first terminal device displays a resource transfer page, which shows the object identifier of the resource receiving object and the resource transfer value.

[0103] In an exemplary embodiment of this application, the display interface of the first terminal device displays relevant information about the client used for resource transfer. The relevant information about the client may be the client's name, the client's icon, or other information that can uniquely identify the client. This embodiment of the application does not limit this.

[0104] When a resource transfer object wants to transfer resources, it selects relevant client information. The first terminal device receives the selection of relevant client information and displays the resource transfer object's homepage, which contains resource transfer controls. In response to a trigger operation on the resource transfer controls, the resource transfer page is displayed.

[0105] The information related to the selected client by the resource transfer object can be information related to the resource transfer object clicking on the client, or information related to the resource transfer object selecting the client in other ways; this application embodiment does not limit this. The triggering operation for the resource transfer control can be a click operation on the resource transfer control, or other operations on the resource transfer control; this application embodiment also does not limit this.

[0106] Optionally, the process of displaying the homepage of the resource transfer object includes: in response to a selection operation of relevant information for the client, displaying the client's homepage, which displays an account box and a password box. The account box is used to obtain the target account, and the password box is used to obtain the target password. The resource transfer object enters its account in the client's account box and its password in the password box, so that the first terminal device obtains the target account and target password; the first terminal device sends the target account and target password to the server; the server receives the target account and target password, verifies the target account and target password, and if the server verifies that the target account is the account in the client and the target account and target password match, the server sends login permission information to the first terminal device, and then the first terminal device displays the resource transfer object's homepage upon receiving the login permission information.

[0107] This application embodiment does not limit the process by which the server verifies the target account and target password. Optionally, this application embodiment provides a process by which the server verifies the target account and target password, the process including: the server storing accounts in the client, passwords corresponding to each account, and the correspondence between each account and its corresponding password. If the server-stored accounts in the client include the target account, and the password corresponding to the target account is the target password, then the target account is determined to be an account in the client, and the target account and target password match. If the server-stored accounts in the client do not include the target account, then the target account is determined not to be an account in the client. If the server-stored accounts in the client include the target account, but the password corresponding to the target account is not the target password, then the target account is determined to be an account in the client, but the target account and target password do not match.

[0108] like Figure 3 This is a schematic diagram showing the homepage of a resource transfer object provided in an embodiment of this application. Figure 3 The homepage shown contains a resource transfer control 301.

[0109] Optionally, if the server determines that the target account is an account on the client and that the target account and target password match, it can also return the target value to the first terminal device. Then, when the first terminal device displays the homepage, it can also display the target value, which is the value already possessed by the resource transfer object. For example... Figure 3 The 1000000.00 in the figure represents the target value, which means that the resource transfer object already has 1,000,000 resources.

[0110] In one possible implementation, since a resource transfer control is displayed on the homepage, the resource transfer object can transfer resources through the resource transfer control. In response to a trigger operation on the resource transfer control, a resource transfer page is displayed, which displays a resource receiving object box and a resource value box. The resource receiving object box is used to identify the resource receiving object, and the resource value box is used to determine the resource transfer value. Based on the input operation in the resource receiving object box, the object identifier of the resource receiving object is displayed in the resource receiving object box; based on the input operation in the resource value box, the resource transfer value is displayed in the resource value box, thus obtaining a resource transfer page displaying the object identifier of the resource receiving object and the resource transfer value. The object identifier of the resource receiving object can be the account of the resource receiving object in the client, or it can be other things; this embodiment of the application does not limit this.

[0111] The triggering operation for the resource transfer control can be a click operation on the resource transfer control, or it can be other operations on the resource transfer control; this application embodiment does not limit this. The resource transfer object can have its object identifier entered in the resource receiving object box, and the resource transfer value entered in the resource value box.

[0112] like Figure 4 This is a schematic diagram illustrating the display of a resource transfer page provided in an embodiment of this application. Figure 4 The resource transfer page shown contains a resource receiving object box 401 and a resource value box 402.

[0113] like Figure 5 This is a schematic diagram illustrating another resource transfer page provided in an embodiment of this application. Figure 5 The resource transfer page shown displays the object identifier xxxxx of the receiving object in the resource receiving object box and the resource transfer value 1000 in the resource value box. That is, the resource transfer object needs to transfer 1000 resources to the resource receiving object xxxxx.

[0114] In one possible implementation, a resource transfer record control is also displayed on the homepage, such as... Figure 3 302 in the code refers to a resource transfer record control, which is used to retrieve the resource transfer record of a resource transfer object. In response to a trigger operation on the resource transfer record control, a retrieval request is generated, including the object identifier of the resource transfer object; the retrieval request is then sent to the server. The server receives the retrieval request, parses it, and obtains the object identifier of the resource transfer object. The server stores the resource transfer records of each object, as well as the correspondence between the object identifier and the resource transfer record. Based on the object identifier of the resource transfer object, the server retrieves the resource transfer record of the resource transfer object and then returns the resource transfer record of the resource transfer object to the first terminal device, so that the first terminal device receives the resource transfer record of the resource transfer object and displays a resource transfer record page. The resource transfer record page displays information for each resource transfer record of the resource transfer object. The information of any resource transfer record includes, but is not limited to, the object identifier of the receiving object of any resource transfer record, the resource value corresponding to any resource transfer record, and the time of any resource transfer record.

[0115] The homepage can also display contact controls, such as... Figure 3The 303 error refers to the Contact Object control, which is used to obtain the contact object of the resource transfer object. The contact object is the object that needs to be verified for the resource transfer transaction. In response to a triggering operation on the Contact Object control, the Contact Object page is displayed, which includes an Add control. In response to a triggering operation on the Add control, the Add Contact Object page is displayed, which includes an Object Identifier box. Based on the input in the Object Identifier box, the Object Identifier of the Reference Object is obtained. When the Add Contact Object function is triggered, the Object Identifier of the Reference Object is sent to the server. The Object Identifier of the Reference Object is used by the server to designate the Reference Object as the contact object for the resource transfer object.

[0116] like Figure 6 This is a schematic diagram illustrating the display of a contact page provided in an embodiment of this application. Figure 6 The contact page shown displays an add control 601.

[0117] Optionally, the contact object page may also display object identifiers for at least one object, where the at least one object is a contact object for the resource transfer object. The object identifier includes at least one of the following: object name or object account. For example... Figure 6 The system displays object identifiers for three objects. The first object's object name is Zhang San and its object account is 13000000000; the second object's object name is Li Si and its object account is 13000000001; and the third object's object name is Wang Wu and its object account is 13000000002.

[0118] Each object displayed on the contact page also has a corresponding edit control for its object identifier, such as... Figure 6 602 in the code represents the edit control corresponding to the object identifier of the first object. The edit control corresponding to the object identifier of any other object is used to change the object identifier of that object. In response to a trigger operation on the edit control corresponding to the object identifier of any object, the edit page for the object identifier of that object is displayed. The resource transfer page allows modification of the object identifier of any object within the edit page for the object identifier of any object.

[0119] The object identification boxes displayed on the Add Contact page include at least one of the object name box or the object account box. For example... Figure 7 This is a schematic diagram illustrating the display of a page for adding contacts, provided in an embodiment of this application. Figure 7 The "Add Contact" page shows a "Name" box (701) and a "Account" box (702). The user enters "Zhao Liu" in the "Name" box and "13000000003" in the "Account" box, so that the first terminal device can obtain the reference object's name and account.

[0120] Optionally, the "Add Contact" page can also display a save control, such as... Figure 7 703 in the code refers to the save control. In response to the trigger operation on the save control, the add function of the contact object is triggered.

[0121] In one possible implementation, the reference object's consent must be obtained before it can be used as a contact object for the resource transfer object. That is, the reference object can only be used as a contact object for the resource transfer object if it consents. This process includes: when the contact object addition function is triggered, sending a first notification message to the reference object's terminal device to notify the reference object of being designated as a contact object for the resource transfer object; and upon receiving a confirmation message from the reference object's terminal device, sending the reference object's object identifier to the server, with the confirmation message instructing the reference object to confirm its status as a contact object for the resource transfer object.

[0122] Optionally, after receiving the first notification message, the reference object's terminal device displays a notification page, which shows the first notification message and an "agree to add" control. In response to a triggering operation on the "agree to add" control, the reference object's terminal device sends a confirmation message to the first terminal device. Optionally, the notification page may also display an "object to add" control. In response to a triggering operation on the "object to add" control, an objection message is sent to the first terminal device. The objection message indicates that the reference object does not agree to be a contact object as a resource transfer object.

[0123] After receiving the object identifier of the reference object, the server adds the reference object to the contact object of the resource transfer object, so that the reference object serves as the contact object of the resource transfer object.

[0124] In one possible implementation, after the server designates the reference object as the contact object for the resource transfer object, the server sends a second notification message to the first terminal device. This second notification message notifies the contact object that the reference object has been designated as the resource transfer object. Upon receiving the second notification message, the first terminal device displays the object identifier of the reference object on the contact object page. This allows the resource transfer object to know that the reference object has been designated as its contact object.

[0125] In step 202, when the resource transfer function is triggered, the first terminal device sends a resource transfer request to the server.

[0126] The resource transfer request includes the object identifier of the resource transfer object, the object identifier of the resource receiving object, and the resource transfer value. The resource transfer request instructs the server to transfer the resource transfer value from the resource transfer object's account to the resource receiving object's account.

[0127] In one possible implementation, the resource transfer page also displays transfer controls, such as... Figure 5 The 501 error indicates a transfer control. In response to an action triggered on the transfer control, the resource transfer function is activated.

[0128] When the resource transfer function is triggered, the process of the first terminal device sending a resource transfer request to the server includes: displaying a resource transfer password interface when the resource transfer function is triggered, the resource transfer password interface being used for the resource transfer object to enter a resource transfer password; obtaining the resource transfer password based on the input operation in the resource transfer password interface; and sending a resource transfer request to the server when the resource transfer password is successfully verified.

[0129] Optionally, the content entered by the resource transfer recipient in the resource transfer password interface can be used as the resource transfer password. The first terminal device stores the password corresponding to the resource transfer recipient. If the resource transfer password matches the password corresponding to the resource transfer recipient, the resource transfer password verification is successful; otherwise, if the resource transfer password does not match the password corresponding to the resource transfer recipient, the resource transfer password verification fails. The reason for requiring the resource transfer recipient to enter a resource transfer password is to ensure the security of the resource transfer recipient's account and to ensure that the resource transfer recipient's account cannot arbitrarily transfer resources.

[0130] In one possible implementation, if the resource transfer password verification is successful, a biometric feature can also be obtained, and if the biometric feature verification is successful, a resource transfer request can be sent to the server. The biometric feature includes at least one of fingerprint, facial image, or iris scan.

[0131] The first terminal device stores the biometrics corresponding to the resource transfer target. If the acquired biometrics match the biometrics corresponding to the resource transfer target, the biometric verification is deemed successful. Conversely, if the acquired biometrics do not match the biometrics corresponding to the resource transfer target, the biometric verification is deemed unsuccessful. The reason for setting up a biometric matching process is to strengthen the security of the resource transfer target's account.

[0132] Optionally, the process of sending a resource transfer request to the server may be as follows: based on the private key of the resource transfer object, sign the resource transfer amount and the object identifier of the resource receiving object to obtain the signed information, which is the information after signing the resource transfer amount and the object identifier of the resource receiving object; based on the signed information and the object identifier of the resource transfer object, generate a resource transfer request and send the resource transfer request to the server.

[0133] The first terminal device needs to obtain the private key of the resource transfer object. The process of the first terminal device obtaining the private key of the resource transfer object is similar to the process of the second terminal device obtaining the private key of the verification object described below. For details, please refer to the process of obtaining the private key of the verification object below. This application embodiment will not be described again here.

[0134] In step 203, the server receives a resource transfer request and determines the risk level of the resource transfer transaction based on the request.

[0135] In one possible implementation, after receiving a resource transfer request from the first terminal device, the server parses the request to obtain the object identifier of the resource transfer object, the object identifier of the resource receiving object, and the resource transfer value. The process by which the server determines the risk level of the resource transfer transaction based on the resource transfer request includes: determining the risk level of the resource transfer transaction based on at least one of the object identifier of the resource transfer object, the object identifier of the resource receiving object, or the resource transfer value.

[0136] Optionally, the risk level of a resource transfer transaction can be determined in one of the following seven ways, based on at least one of the object identifier of the resource transfer object, the object identifier of the resource receiving object, or the resource transfer value.

[0137] Method 1: Determine the risk level of the resource transfer transaction based on the object identifier of the resource transfer object.

[0138] In implementation method one, the first number of times the resource transfer object transfers resources in the first time period is determined based on the object identifier of the resource transfer object, and the risk level of the resource transfer transaction is determined based on the first number.

[0139] The first time period can be any time period, and this embodiment does not limit it. The process of determining the first number of times a resource transfer object transfers resources within the first time period based on the object identifier of the resource transfer object includes: generating a first number acquisition request, which includes the object identifier of the resource transfer object and the first time period; and sending the first number acquisition request to the server. The server receives the first number acquisition request, parses it to obtain the object identifier of the resource transfer object and the first time period, determines the first number of times the resource transfer object transfers resources within the first time period based on the object identifier, and returns the first number to the first terminal device so that the first terminal device can obtain the first number.

[0140] The process of determining the risk level of a resource transfer transaction based on the first count includes: taking the risk level corresponding to the range of counts in which the first count falls as the risk level of the resource transfer transaction.

[0141] Optionally, the first terminal device stores the correspondence between various frequency ranges and the corresponding risk levels. Table 1 below is a table showing the correspondence between various frequency ranges and the corresponding risk levels provided in an embodiment of this application.

[0142] Table 1

[0143] Number of times range Risk level [0，5) 1 [5，10) 2 [10，15) 3 [15，20) 4 [20，+∞) 5

[0144] As shown in Table 1 above, the risk level corresponding to the frequency range [0, 5) is Level 1, and the risk levels corresponding to other frequency ranges are shown in Table 1 above, which will not be repeated here.

[0145] For example, if the first number is 7, then the risk level of the resource transfer transaction is level 2.

[0146] Method 2: Determine the risk level of the resource transfer transaction based on the object identifier of the resource recipient.

[0147] In the second implementation method, the second number of times the resource receiving object receives resources in the second time period is determined based on the object identifier of the resource receiving object, and the risk level of the resource transfer transaction is determined based on the second number.

[0148] The second time period can be any time period, and this embodiment does not limit it. The process of determining the second number of times a resource receiving object receives resources in the second time period based on the object identifier of the resource receiving object includes: generating a second number acquisition request, which includes the object identifier of the resource receiving object and the second time period; and sending the second number acquisition request to the server. The server receives the second number acquisition request, parses it to obtain the object identifier of the resource receiving object and the second time period, determines the second number of times the resource receiving object receives resources in the second time period based on the object identifier, and returns the second number to the first terminal device so that the first terminal device can obtain the second number.

[0149] The process of determining the risk level of a resource transfer transaction based on the second number includes: taking the risk level corresponding to the range of times the second number falls within as the risk level of the resource transfer transaction.

[0150] Method 3: Determine the risk level of resource transfer transactions based on the resource transfer values.

[0151] In implementation method three, the first terminal device stores the correspondence between various resource value ranges and the corresponding risk levels for each resource value range. The resource value range containing the resource transfer value is determined, and the risk level corresponding to that resource value range is used as the risk level of the resource transfer transaction.

[0152] Table 2 below shows the correspondence between various resource value ranges and the corresponding risk levels provided in the embodiments of this application.

[0153] Table 2

[0154] Resource value range Risk level [0，1000) 1 [1000，2000) 2 [2000，3000) 3 [3000，4000) 4 [4000，+∞) 5

[0155] As shown in Table 2 above, the risk level corresponding to the resource value range [0, 1000) is Level 1. The risk levels corresponding to other resource value ranges are shown in Table 2 above, and will not be repeated here.

[0156] For example, if the resource transfer value is 2500, then the risk level of the resource transfer transaction is level 3.

[0157] Implementation Method 4: Determine the risk level of the resource transfer transaction based on the object identifier of the resource transfer object and the object identifier of the resource receiving object.

[0158] In implementation method four, the first number of times the resource transfer object transfers resources in the first time period is determined based on the object identifier of the resource transfer object; the second number of times the resource receiving object receives resources in the second time period is determined based on the object identifier of the resource receiving object; and the risk level of the resource transfer transaction is determined based on the first number and the second number. The process of determining the first number has been described in implementation method one above, and the process of determining the second number has been described in implementation method two above, and will not be repeated here in the embodiments of this application.

[0159] Optionally, a target number is determined based on the first and second counts, and the risk level corresponding to the range of counts containing the target number is used as the risk level of the resource transfer transaction. For example, the sum of the first and second counts is used as the target number.

[0160] Implementation Method 5: Determine the risk level of resource transfer transactions based on the object identifier of the resource transfer object and the resource transfer value.

[0161] In implementation method five, the first number of times the resource transfer object transfers resources in the first time period is determined based on the object identifier of the resource transfer object. The risk level of the resource transfer transaction is then determined based on the first number and the value of the transferred resources. The process for determining the first number has already been described in implementation method one above and will not be repeated here.

[0162] This application does not limit the process of determining the risk level of a resource transfer transaction based on the initial number and the resource transfer value. Optionally, a first value is determined based on the initial number, the frequency weight parameter, the resource transfer value, and the value weight parameter; the risk level corresponding to the range of values ​​containing the first value is taken as the risk level of the resource transfer transaction.

[0163] The frequency weight parameter and the numerical weight parameter are set based on experience or adjusted according to the implementation environment, and this application embodiment does not limit this. For example, the frequency weight parameter is 0.3 and the numerical weight parameter is 0.7.

[0164] For example, the first value S1 is determined according to the following formula (1) based on the first number, the frequency weight parameter, the resource transfer value, and the value weight parameter.

[0165] S1=A*α+B*β Formula (1)

[0166] In the above formula (1), A is the first number, α is the number weight parameter, B is the resource transfer value, and β is the value weight parameter.

[0167] Method 6: Determine the risk level of the resource transfer transaction based on the object identifier of the resource recipient and the resource transfer value.

[0168] In implementation method six, the second number of times the resource receiving object receives resources in the second time period is determined based on the object identifier of the resource receiving object. The risk level of the resource transfer transaction is then determined based on the second number and the resource transfer value. The process for determining the second number has already been described in implementation method two above and will not be repeated here.

[0169] This application does not limit the process of determining the risk level of a resource transfer transaction based on the second number and the resource transfer value. Optionally, the second value is determined based on the second number, the frequency weight parameter, the resource transfer value, and the value weight parameter; the risk level corresponding to the range of values ​​containing the second value is taken as the risk level of the resource transfer transaction.

[0170] The frequency weight parameter and the numerical weight parameter are set based on experience or adjusted according to the implementation environment, and this application embodiment does not limit this. For example, the frequency weight parameter is 0.3 and the numerical weight parameter is 0.7.

[0171] For example, the second value S2 is determined according to the following formula (2) based on the second number, the frequency weight parameter, the resource transfer value, and the value weight parameter.

[0172] S2=C*α+B*β Formula (2)

[0173] In the above formula (2), C is the second number, α is the number weight parameter, B is the resource transfer value, and β is the value weight parameter.

[0174] Method 7: Determine the risk level of the resource transfer transaction based on the object identifier of the resource transfer object, the object identifier of the resource receiving object, and the resource transfer value.

[0175] In implementation method seven, the first number of times the resource transfer object transfers resources in the first time period is determined based on the object identifier of the resource transfer object; the second number of times the resource receiving object receives resources in the second time period is determined based on the object identifier of the resource receiving object; and the risk level of the resource transfer transaction is determined based on the first number, the second number, and the resource transfer value. The process for determining the first number has been described in implementation method one above, and the process for determining the second number has been described in implementation method two above, and will not be repeated here.

[0176] In one possible implementation, the process of determining the risk level of a resource transfer transaction based on the first number, the second number, and the resource transfer value includes: determining the target number based on the first number and the second number; determining the third value based on the target number, the number weight parameter, the resource transfer value, and the value weight parameter; and taking the risk level corresponding to the value range of the third value as the risk level of the resource transfer transaction.

[0177] The process of determining the target number of times has been described in the above implementation method four, and will not be repeated here.

[0178] The third value S3 is determined according to the target number, the number weight parameter, the resource transfer value, and the value weight parameter, in accordance with the following formula (3).

[0179] S3=D*α+B*β Formula (3)

[0180] In the above formula (3), D is the target number of times, α is the number of times weight parameter, B is the resource transfer value, and β is the value weight parameter.

[0181] It should be noted that any of the above-mentioned implementation methods can be used to determine the risk level of resource transfer transactions, and the embodiments of this application do not limit this.

[0182] In one possible implementation, the server receives a resource transfer request, parses the request to obtain the object identifier and signed information of the resource transfer object; based on the object identifier, it obtains the public key of the resource transfer object, and verifies the signed information using the public key to obtain the object identifier of the resource receiving object and the resource transfer value. The subsequent process by which the server determines the risk level of the resource transfer transaction based on at least one of the object identifier of the resource transfer object, the object identifier of the resource receiving object, or the resource transfer value has been described in the above steps and will not be repeated here in this embodiment.

[0183] The process by which the server obtains the public key of the resource transfer object is similar to the process by which the server obtains the public key of the verification object, and will not be described again in this embodiment.

[0184] In step 204, if the risk level is greater than the risk level threshold, the server sends a risk warning message to the first terminal device.

[0185] In step 203 above, after the server determines the risk level of the resource transfer transaction, if the risk level is greater than the level threshold, a risk warning message is sent to the first terminal device. The risk warning message indicates that the resource transfer transaction carries a risk. The content of the risk warning message can be arbitrary, and this embodiment does not limit it. For example, the risk warning message might be: "The system has detected a risk in this resource transfer transaction. Please contact the verification object for verification."

[0186] The level threshold is set based on experience or adjusted according to the implementation environment; this application embodiment does not limit this. For example, the level threshold is 3 levels.

[0187] In one possible implementation, if the risk level is no greater than a threshold, the server transfers resources of a specified value from the resource transfer object's account to the resource receiving object's account. After transferring the resources from the resource transfer object's account to the resource receiving object's account, the server can send a notification message to the first terminal device to notify the resource transfer object that the resource transfer transaction has been completed. This process is detailed in step 214 below and will not be repeated here.

[0188] In step 205, the first terminal device receives and displays the risk warning information.

[0189] In one possible implementation, after receiving the risk warning information, the first terminal device displays the risk warning information.

[0190] Optionally, the first terminal device displays a risk warning page, which contains risk warning information. For example... Figure 8 This is a schematic diagram of a risk warning page provided in an embodiment of this application. Figure 8 The risk warning page displays the message: "The system has detected a risk in this resource transfer transaction. Please contact the verification target for verification."

[0191] In step 206, in response to the triggering operation for the risk warning information, the first terminal device sends an instruction message to the server.

[0192] In one possible implementation, the risk warning page also displays a first confirmation control, such as... Figure 8 801 in the code represents the first confirmation control, which instructs the resource transfer object to confirm the request for verification of the resource transfer transaction. Receiving a trigger operation for the first confirmation control is equivalent to receiving a trigger operation for the risk warning information.

[0193] When the first terminal device receives a trigger operation for the risk warning information, the first terminal device sends an instruction to the server. The instruction is used by the server to send a verification request to the terminal device of the verification target.

[0194] In step 207, the server receives the instruction information and determines the verification object of the resource transfer object.

[0195] In one embodiment of this application, after receiving the instruction information sent by the first terminal device, the server determines the contact object of the resource transfer object based on the object identifier of the resource transfer object; and determines the contact object of the resource transfer object as the verification object of the resource transfer object.

[0196] In another embodiment of this application, after receiving the instruction information sent by the first terminal device, the server determines the ratio corresponding to the risk level; determines the target quantity based on the number of contact objects of the resource transfer object and the ratio; and determines the verification object among the contact objects, the number of verification objects being the target quantity.

[0197] Different risk levels correspond to different ratios, and there is a positive correlation between risk level and ratio. That is, the higher the risk level, the larger the corresponding ratio; conversely, the lower the risk level, the smaller the corresponding ratio. This allows for dynamic adjustment of the number of verification objects based on the risk level, making risk management more flexible and effective.

[0198] The process of determining the target quantity based on the number and ratio of the linked entities involved in the resource transfer includes: determining the product between the number and ratio of the linked entities corresponding to the resource transfer; if the product is an integer, determining the product as the target quantity; if the product is not an integer, determining the target quantity by rounding the product. For example, if the product is 3, the target quantity is 3. Another example is if the product is 5.2, the target quantity is 5. Yet another example is if the product is 3.8, the target quantity is 4.

[0199] This application does not limit the process of determining the verification object from the contact objects. Optionally, a target number of contact objects are randomly selected as verification objects. Alternatively, the contact objects can be sorted according to a target order based on their response times, resulting in a sorting result. The response time of any contact object is used to indicate the time between sending a verification request to any contact object and receiving the verification result returned by any contact object. The contact objects that are ranked before the target number in the sorting result are then determined as verification objects.

[0200] Since the sorting is based on response time, the shorter the response time, the shorter the verification time for resource transfer transactions. Therefore, the target order can be from small to large.

[0201] In step 208, the server sends a verification request to the second terminal device.

[0202] After the server determines the verification object of the resource transfer object in step 207 above, the server sends a verification request to the second terminal device corresponding to the verification object. The verification request includes the object identifier of the resource transfer object.

[0203] Optionally, the verification request may also include the resource transfer value and the object identifier of the resource receiving object.

[0204] In step 209, the second terminal device receives the verification request and displays the verification page.

[0205] In one possible implementation, the process of the second terminal device receiving a verification request from the server and displaying a verification page according to the verification request includes: displaying a verification notification according to the verification request, the verification notification indicating that a verification request has been received; and displaying a verification page in response to a triggering operation on the verification notification, the verification page displaying a verification message including the object identifier of the resource transfer object.

[0206] If the verification request also includes the resource transfer value and the object identifier of the resource receiving object, the verification message will also include the resource transfer value and the object identifier of the resource receiving object.

[0207] like Figure 9 This is a schematic diagram showing a verification notification provided in an embodiment of this application.

[0208] like Figure 10 This is a schematic diagram of a verification page provided in an embodiment of this application. Figure 10 The verification page displayed the verification message: "The system has detected that Zhang San is conducting a resource transfer transaction of 1,000 yuan. Please confirm whether there is any risk in this resource transfer transaction."

[0209] In step 210, in response to the triggering operation on the verification page, the second terminal device obtains the verification result.

[0210] After the verification page is displayed, since the verification page displays the object identifier of the resource transfer object, the verification object can contact the resource transfer object to confirm whether this resource transfer transaction is in progress. After receiving the reply from the resource transfer object, the verification result can be obtained through the verification page based on the reply from the resource transfer object.

[0211] Optionally, the verification page also displays agree and disagree controls, such as... Figure 10In the diagram, 1001 represents the "agree" control, and 1002 represents the "disagree" control. When the resource transfer object's response indicates that it is initiating a resource transfer transaction, the verification object selects the "agree" control on the verification page, and the second terminal device receives a verification result indicating agreement to the resource transfer transaction. When the resource transfer object's response indicates that it is not initiating a resource transfer transaction, the verification object selects the "disagree" control on the verification page, and the second terminal device receives a verification result indicating opposition to the resource transfer transaction.

[0212] In step 211, the second terminal device signs the verification result based on the private key of the verification object to obtain the target information.

[0213] After the second terminal device obtains the verification result, it signs the verification result according to the private key of the verification object to obtain the target information, which is the signed verification result.

[0214] Before signing the verification result based on the verification object's private key, the second terminal device needs to obtain the verification object's private key. In one embodiment of this application, the second terminal device stores the verification object's private key in its storage space, and the second terminal device obtains the verification object's private key from its own storage space.

[0215] In another embodiment of this application, the physical device stores the private key of the verification object, and the second terminal device obtains the private key of the verification object through interaction with the physical device. The physical device can be a security token. The physical device provides a physical layer of security, making the storage of the verification object's private key more secure.

[0216] In another embodiment of this application, the private key of the verification object is stored in a distributed storage manner. That is, the private key of the verification object is divided into multiple parts, each stored in a different device. The second terminal device obtains the private key of the verification object by interacting with the different devices. By using distributed storage to store the private key of the verification object, the storage of the private key of the verification object becomes more secure.

[0217] In step 212, the second terminal device sends verification information to the server.

[0218] After obtaining the target information in step 211 above, verification information is generated based on the target information and the object identifier of the verification object. The verification information includes the object identifier of the verification object and the target information. The second terminal device then sends the verification information to the server.

[0219] In step 213, the server receives the verification information and obtains the verification result based on the verification information.

[0220] In one possible implementation, the server receives verification information sent by the second terminal device, parses the verification information to obtain the object identifier and target information of the verification object. Based on the object identifier, the server obtains the public key of the verification object; then, it verifies the target information using the public key to obtain the verification result. If the verification object's public key successfully verifies the target information and obtains a verification result, it indicates that the target information was sent by the verification object itself.

[0221] The server stores the mapping between object identifiers and public keys for each object. The server retrieves the public key of the object being verified based on its object identifier and the mapping between these identifiers and public keys.

[0222] In step 214, if the server determines that the verification result meets the verification requirements, it transfers the resource transfer value from the resource transfer object's account to the resource receiving object's account.

[0223] In this context, "the verification result meets the verification requirements" means that the verification result indicates agreement to proceed with the resource transfer transaction. If the verification result meets the verification requirements, the server transfers the resource value of the resource transfer object from the resource transfer object's account to the resource receiving object's account.

[0224] If the verification result does not meet the verification requirements, the server returns a third notification message to the first terminal device. This third notification message indicates that the verification object of the resource transfer object opposes the resource transfer transaction. Here, "verification result does not meet the verification requirements" means that the verification result indicates opposition to the resource transfer transaction.

[0225] In one possible implementation, after the server transfers the resource transfer value from the resource transfer object's account to the resource receiving object's account, the server may also send a fourth notification message to the first terminal device. This fourth notification message indicates that the resource transfer transaction has been completed. Optionally, the fourth notification message may also include the object identifier of the verification object, so that the resource transfer object knows which objects are verifying the resource transfer transaction. The fourth notification message can contain any content, and this embodiment does not limit its content. For example, the fourth notification message might be "A and B agree to this resource transfer transaction, and the resource transfer transaction has been completed." From the fourth notification message, it can be seen that the verification objects of the resource transfer transaction are object A and object B.

[0226] After receiving the fourth notification message, the first terminal device displays a notification message page, which shows the fourth notification message. For example... Figure 11 This is a schematic diagram of a notification message page provided in an embodiment of this application. Figure 11 The notification message page shown contains a fourth notification message.

[0227] Optionally, a second confirmation control is also displayed on the notification message page, such as... Figure 11 1101 in the code represents the second confirmation control. In response to a trigger operation on the second confirmation control, the first terminal device cancels the display of the notification message page.

[0228] When the above method receives a resource transfer request from a resource transfer object, the server sends a verification request to the verification object of the resource transfer object. This verification object then verifies the resource transfer transaction. Only if the verification result meets the verification requirements will the resources of the specified value be transferred from the resource transfer object's account to the resource receiving object's account. This method requires the verification object of the resource transfer object to participate in and verify the resource transfer transaction. Even if the private key of the resource transfer object is leaked, any object that obtains the private key and attempts to transfer resources through the resource transfer object's account will still need to be verified by the verification object. This increases the difficulty of successful unauthorized resource transfers, reduces the success rate of malicious resource transfers, effectively prevents theft of resource transfer object accounts and fraudulent resource transfer transactions, reduces the risk to resource transfer object accounts, and thus improves the security of resource transfers.

[0229] Furthermore, by dynamically assessing the risk level of resource transfer transactions and introducing a verification process involving verification objects, the risk management mechanism for resource transfer transactions becomes more flexible and robust. This allows for adjustments to the number of verification objects based on the risk level of the resource transfer transaction, further enhancing the security of resource transfers.

[0230] Furthermore, by introducing a process for verifying resource transfer transactions through verification objects, the transparency and credibility of resource transfers are increased. When a resource transfer transaction is verified by multiple verification objects, the legality and security of the transaction are naturally recognized by all participating verification objects. This increased trust not only benefits the resource transfer objects but also makes a positive contribution to the entire resource system, helping to promote the widespread acceptance and use of resources.

[0231] Figure 12 This is a flowchart of a resource transfer method provided in an embodiment of this application. The method can be... Figure 1 The server 102 in the computer system shown executes the method, which includes the following steps.

[0232] In step 1201, a resource transfer request is sent by the terminal device receiving the resource transfer object. The resource transfer request includes the object identifier of the resource transfer object, the object identifier of the resource receiving object, and the resource transfer value.

[0233] In one possible implementation, the process of receiving a resource transfer request sent by the terminal device that receives the resource transfer object has been described in step 203 above, and will not be repeated here.

[0234] In step 1202, a verification request is sent to the terminal device of the verification object of the resource transfer object. The verification request includes the object identifier of the resource transfer object.

[0235] In one possible implementation, the process of sending a verification request to the terminal device of the verification object of the resource transfer object has been described in steps 204 to 208 above, and will not be repeated here.

[0236] In step 1203, the verification result returned by the terminal device of the verification object is received.

[0237] In one possible implementation, the process of receiving the verification result returned by the terminal device of the verification object has been described in step 213 above, and will not be repeated here.

[0238] In step 1204, if the verification result meets the verification requirements, the resource transfer value is transferred from the resource transfer object's account to the resource receiving object's account.

[0239] In one possible implementation, if the verification result meets the verification requirements, the process of transferring the resource transfer value from the resource transfer object's account to the resource receiving object's account has been described in step 214 above, and will not be repeated here.

[0240] When the above method receives a resource transfer request from a resource transfer object, the server sends a verification request to the verification object of the resource transfer object. This verification object then verifies the resource transfer transaction. Only if the verification result meets the verification requirements will the resources of the specified value be transferred from the resource transfer object's account to the resource receiving object's account. This method requires the verification object of the resource transfer object to participate in and verify the resource transfer transaction. Even if the private key of the resource transfer object is leaked, any object that obtains the private key and attempts to transfer resources through the resource transfer object's account will still need to be verified by the verification object. This increases the difficulty of successful unauthorized resource transfers, reduces the success rate of malicious resource transfers, effectively prevents theft of resource transfer object accounts and fraudulent resource transfer transactions, reduces the risk to resource transfer object accounts, and thus improves the security of resource transfers.

[0241] Figure 13 This is a flowchart of a resource transfer method provided in an embodiment of this application. The method can be... Figure 1The method is executed by the first terminal device 101 in the computer system shown, and includes the following steps.

[0242] In step 1301, a resource transfer page is displayed, which shows the object identifier of the resource receiving object and the resource transfer value.

[0243] In one possible implementation, the process of displaying the resource transfer page has been described in step 201 above and will not be repeated here.

[0244] In step 1302, when the resource transfer function is triggered, a resource transfer request is sent to the server. The resource transfer request is used by the server to send a verification request to the terminal device of the verification object of the resource transfer object, receive the verification result returned by the terminal device of the verification object, and if the verification result meets the verification requirements, transfer the resource transfer value from the account of the resource transfer object to the account of the resource receiving object.

[0245] The resource transfer request includes the object identifier of the resource transfer object, the object identifier of the resource receiving object, and the resource transfer value, while the verification request includes the object identifier of the resource transfer object.

[0246] In one possible implementation, the process of sending a resource transfer request to the server when the resource transfer function is triggered has been described in step 202 above and will not be repeated here.

[0247] The above method involves the resource transfer object sending a resource transfer request to the server when transferring resources. The server then sends a verification request to the verification object of the resource transfer object, enabling the verification object to verify the resource transfer transaction. Only if the verification result of the verification object meets the verification requirements will the server transfer the resources of the transferred value from the resource transfer object's account to the resource receiving object's account. This method requires the verification object of the resource transfer object to participate in and verify the resource transfer transaction. Even if the private key of the resource transfer object is leaked, any object that obtains the private key and attempts to transfer resources through the resource transfer object's account will still need to be verified by the verification object. This increases the difficulty of successful unauthorized resource transfers, reduces the success rate of malicious resource transfers, effectively prevents theft of the resource transfer object's account and fraudulent resource transfer transactions, reduces the risk to the resource transfer object's account, and thus improves the security of resource transfers.

[0248] Figure 14 This is a flowchart of a resource transfer method provided in an embodiment of this application. The method can be... Figure 1The second terminal device 102 in the computer system shown executes the method, which includes the following steps.

[0249] In step 1401, a verification request sent by the server is received. The verification request includes the object identifier of the resource transfer object.

[0250] In one possible implementation, the process of receiving the verification request sent by the server has been described in step 209 above, and will not be repeated here.

[0251] In step 1402, a verification page is displayed according to the verification request, and the verification page displays the object identifier of the resource transfer object.

[0252] In one possible implementation, the process of displaying the verification page based on the verification request has been described in step 209 above and will not be repeated here.

[0253] In step 1403, in response to the triggering operation on the verification page, the verification result is obtained.

[0254] In one possible implementation, the process of obtaining the verification result has been described in step 210 above, and will not be repeated here.

[0255] In step 1404, a verification result is sent to the server. The verification result is used by the server to transfer the resource transfer value from the resource transfer object's account to the resource receiving object's account if the verification result meets the verification requirements.

[0256] In one possible implementation, the process of sending the verification result to the server has been described in steps 211 to 212 above, and will not be repeated here.

[0257] The above method, upon receiving a verification request from the server, involves the verification object verifying the resource transfer transaction and sending the verification result to the server. If the verification result meets the verification requirements, the server transfers the resource value from the resource transfer object's account to the resource receiving object's account. This method requires the verification object of the resource transfer object to participate in and verify the resource transfer transaction. Even if the private key of the resource transfer object is leaked, any object that obtains the private key and attempts to transfer resources through the resource transfer object's account will still need to be verified by the verification object. This increases the difficulty of successful unauthorized resource transfers, reduces the success rate of malicious resource transfers, effectively prevents theft of the resource transfer object's account and fraudulent resource transfer transactions, reduces the risk to the resource transfer object's account, and thus improves the security of resource transfers.

[0258] Figure 15 This is a flowchart illustrating a resource transfer method provided in an embodiment of this application. The method can be implemented through interaction between a resource transfer object, a first terminal device corresponding to the resource transfer object, a server, and a second terminal device corresponding to the verification object. The method includes three processes: the first process involves the resource transfer object logging into a client and accessing its homepage; the second process involves the resource transfer object adding a contact object; and the third process involves the resource transfer object initiating a resource transfer transaction. Figure 15 As shown, the first process includes steps 1 to 4 as follows.

[0259] 1. The resource transfer target opens the client and enters the target account and target password so that the first terminal device can obtain the target account and target password.

[0260] 2. The first terminal device sends the target account and target password to the server.

[0261] 3. The server verifies the target account and target password. If the target account is the same as the account in the client and the target account and target password are verified, the server returns the target value of the resources owned by the resource transfer object to the first terminal device.

[0262] 4. The first terminal device displays the homepage of the resource transfer object.

[0263] The second process includes steps 5 through 13 as follows.

[0264] 5. Select the object control for resource transfer.

[0265] 6. The first terminal device displays the contact information page.

[0266] 7. Select the resource transfer object and add controls.

[0267] 8. The first terminal device displays the "Add Contact" page.

[0268] 9. Input the object identifier of the reference object for the resource transfer object.

[0269] 10. The first terminal device sends the object identifier of the reference object to the server.

[0270] 11. The server uses the reference object as the contact object for the resource transfer object.

[0271] 12. The server sends a second notification message to the first terminal device.

[0272] 13. The first terminal device displays the object identifier of the reference object on the contact object page.

[0273] The third process includes steps 14 to 27 as follows.

[0274] 14. Input the object identifier and resource transfer value of the resource receiving object to enable the first terminal device to obtain the object identifier and resource transfer value of the resource receiving object.

[0275] 15. The first terminal device sends a resource transfer request to the server.

[0276] 16. The server determines the risk level of resource transfer transactions.

[0277] 17. If the risk level is greater than the risk level threshold, the server sends a risk warning message to the first terminal device.

[0278] 18. Risk warning information when selecting a resource transfer target.

[0279] 19. The first terminal device sends an instruction message to the server.

[0280] 20. The first terminal device sends a verification request to the server.

[0281] 21. The second terminal device obtains the verification results.

[0282] 22. The second terminal device signs the verification result based on the private key of the verification object to obtain the target information.

[0283] 23. The second terminal device sends verification information to the server.

[0284] The verification information includes the object identifier and target information of the object being verified.

[0285] 24. The server verifies the target information using the public key of the verification object and obtains the verification result.

[0286] 25. If the verification result meets the verification requirements, the server transfers the resource transfer value from the resource transfer object's account to the resource receiving object's account.

[0287] 26. The server sends a fourth notification message to the first terminal device so that the first terminal device displays the fourth notification message, thereby informing the resource transfer object that the resource transfer transaction has been completed.

[0288] 27. If the risk level is not greater than the risk level threshold, transfer the resource transfer value from the resource transfer recipient's account to the resource receiving recipient's account.

[0289] Figure 16 The diagram shown is a structural schematic of a resource transfer device provided in an embodiment of this application. Figure 16 As shown, the device includes:

[0290] The receiving module 1601 is used to receive a resource transfer request sent by the terminal device of the resource transfer object. The resource transfer request includes the object identifier of the resource transfer object, the object identifier of the resource receiving object, and the resource transfer value.

[0291] Sending module 1602 is used to send a verification request to the terminal device of the verification object of the resource transfer object. The verification request includes the object identifier of the resource transfer object.

[0292] The receiving module 1601 is also used to receive the verification result returned by the terminal device of the verification object;

[0293] The transfer module 1603 is used to transfer resources of the resource transfer value from the account of the resource transfer object to the account of the resource receiving object when the verification result meets the verification requirements.

[0294] In one possible implementation, the device further includes:

[0295] The determination module is used to determine the risk level of a resource transfer transaction based on at least one of the object identifier of the resource transfer object, the object identifier of the resource receiving object, or the resource transfer value.

[0296] The sending module 1602 is used to send a verification request to the terminal device of the verification object of the resource transfer object when the risk level is greater than the level threshold.

[0297] In one possible implementation, the sending module 1602 is used to send risk warning information to the terminal device of the resource transfer object when the risk level is greater than the level threshold; and to send a verification request to the terminal device of the verification object of the resource transfer object when receiving the indication information returned by the terminal device of the resource transfer object.

[0298] In one possible implementation, the determining module is further configured to determine the ratio corresponding to the risk level when the risk level is greater than the level threshold, wherein the risk level and the ratio are positively correlated; determine the target quantity based on the number of contact objects of the resource transfer object and the ratio; and determine the verification object among the contact objects, wherein the number of verification objects is the target quantity.

[0299] In one possible implementation, a determining module is used to sort the contact objects according to the target order based on the response time of each contact object, and obtain a sorting result. The response time of any contact object is used to indicate the time between sending a verification request to any contact object and receiving the verification result returned by any contact object. The contact objects that are ranked before the target number in the sorting result are determined as verification objects.

[0300] In one possible implementation, the receiving module 1601 is used to receive verification information returned by the terminal device of the verification object. The verification information includes the object identifier and target information of the verification object. The target information is the information obtained after signing the verification result according to the private key of the verification object. The public key of the verification object is determined according to the object identifier of the verification object. The target information is verified and signed according to the public key of the verification object to obtain the verification result.

[0301] When the aforementioned device receives a resource transfer request from a resource transfer target, the server sends a verification request to the resource transfer target's verification object. This verification object verifies the resource transfer transaction. Only if the verification result meets the verification requirements will the resource transfer value be transferred from the resource transfer target's account to the resource receiving target's account. Because the verification object of the resource transfer target is required to participate in and verify the resource transfer transaction, even if the resource transfer target's private key is leaked, any object that obtains the private key and attempts to transfer resources through the resource transfer target's account will still need to be verified by the resource transfer target's verification object. This increases the difficulty of successful unauthorized resource transfers, reduces the success rate of malicious resource transfers, effectively prevents theft of resource transfer target accounts and fraudulent resource transfer transactions, reduces the risk to resource transfer target accounts, and thus improves the security of resource transfers.

[0302] Figure 17 The diagram shown is a structural schematic of a resource transfer device provided in an embodiment of this application. Figure 17 As shown, the device includes:

[0303] Display module 1701 is used to display the resource transfer page, which displays the object identifier of the resource receiving object and the resource transfer value.

[0304] The sending module 1702 is used to send a resource transfer request to the server when the resource transfer function is triggered. The resource transfer request is used by the server to send a verification request to the terminal device of the verification object of the resource transfer object, receive the verification result returned by the terminal device of the verification object, and transfer the resource transfer value from the account of the resource transfer object to the account of the resource receiving object if the verification result meets the verification requirements.

[0305] The resource transfer request includes the object identifier of the resource transfer object, the object identifier of the resource receiving object, and the resource transfer value, while the verification request includes the object identifier of the resource transfer object.

[0306] In one possible implementation, the display module 1701 is further configured to display the homepage of the resource transfer object, which displays a resource transfer control; and to display the resource transfer page in response to a trigger operation on the resource transfer control.

[0307] In one possible implementation, a contact object control is also displayed on the homepage, which is used to obtain the contact object of the resource transfer object;

[0308] Display module 1701 is also used to display a contact object page in response to a trigger operation on the contact object control, wherein the contact object page displays an add control; and to display an add contact object page in response to a trigger operation on the add control, wherein the add contact object page displays an object identifier box.

[0309] The device also includes:

[0310] The acquisition module is used to obtain the object identifier of the reference object based on the input operation in the object identifier box;

[0311] The sending module 1702 is also used to send the object identifier of the reference object to the server when the add function of the contact object is triggered. The object identifier of the reference object is used by the server to treat the reference object as a contact object for resource transfer.

[0312] In one possible implementation, the sending module 1702 is used to send a first notification message to the terminal device of the reference object when the add function of the contact object is triggered. The first notification message is used to notify the reference object of the contact object as the resource transfer object. When the confirmation message sent by the terminal device of the reference object is received, the sending module 1702 sends the object identifier of the reference object to the server. The confirmation message is used to instruct the reference object to confirm the contact object as the resource transfer object.

[0313] In one possible implementation, the device further includes:

[0314] The receiving module is used to receive risk warning information returned by the server when the risk level is greater than the risk level threshold.

[0315] Display module 1701 is also used to display risk warning information;

[0316] The sending module 1702 is also used to send instruction information to the server in response to the triggering operation of the risk warning information. The instruction information is used by the server to send a verification request to the terminal device of the verification object.

[0317] In one possible implementation, the sending module 1702 is used to display a resource transfer password interface when the resource transfer function is triggered. The resource transfer password interface is used for the resource transfer object to input a resource transfer password. Based on the input operation in the resource transfer password interface, the resource transfer password is obtained. If the resource transfer password is verified, a resource transfer request is sent to the server.

[0318] When a resource transfer object performs a resource transfer, the aforementioned device sends a resource transfer request to the server. The server then sends a verification request to the verification object of the resource transfer object, enabling the verification object to verify the resource transfer transaction. Only if the verification result of the verification object meets the verification requirements will the server transfer the resource value from the resource transfer object's account to the resource receiving object's account. Because the verification object of the resource transfer object is required to participate in and verify the resource transfer transaction, even if the private key of the resource transfer object is leaked, any object that obtains the private key and attempts to transfer resources through the resource transfer object's account will still need to be verified by the verification object. This increases the difficulty of successful unauthorized resource transfers, reduces the success rate of malicious resource transfers, effectively prevents theft of resource transfer object accounts and fraudulent resource transfer transactions, reduces the risk to resource transfer object accounts, and thus improves the security of resource transfers.

[0319] Figure 18 The diagram shown is a structural schematic of a resource transfer device provided in an embodiment of this application. Figure 18 As shown, the device includes:

[0320] The receiving module 1801 is used to receive a verification request sent by the server. The verification request includes the object identifier of the resource transfer object.

[0321] Display module 1802 is used to display a verification page according to the verification request, wherein the verification page displays the object identifier of the resource transfer object;

[0322] The acquisition module 1803 is used to obtain the verification result in response to a trigger operation on the verification page;

[0323] The sending module 1804 is used to send the verification result to the server. The verification result is used by the server to transfer the resource transfer value from the resource transfer object's account to the resource receiving object's account if the verification result meets the verification requirements.

[0324] In one possible implementation, the acquisition module 1803 is also used to sign the verification result based on the private key of the verification object to obtain the target information;

[0325] The sending module 1804 is used to send verification information to the server. The verification information includes the object identifier and target information of the verification object. The server uses the verification information to verify the target information based on the public key of the verification object and obtain the verification result.

[0326] The above method, upon receiving a verification request from the server, involves the verification object verifying the resource transfer transaction and sending the verification result to the server. If the verification result meets the verification requirements, the server transfers the resource value from the resource transfer object's account to the resource receiving object's account. Because the verification object is required to participate in and verify the resource transfer transaction, even if the resource transfer object's private key is leaked, any object that obtains the private key and attempts to transfer resources through the resource transfer object's account will still need to undergo verification by the verification object. This increases the difficulty of unauthorized resource transfers, reduces the success rate of malicious resource transfers, effectively prevents account theft and fraudulent resource transfer transactions, lowers the risk to the resource transfer object's account, and thus improves the security of resource transfers.

[0327] It should be understood that the above-described apparatus is only illustrated by the division of the functional modules described above when implementing its functions. In practical applications, the functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the apparatus and method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.

[0328] Figure 19 This illustration shows a structural block diagram of a terminal device 1900 provided in an exemplary embodiment of this application. The terminal device 1900 can be any electronic device product capable of human-computer interaction with a user through one or more methods such as a keyboard, touchpad, remote control, voice interaction, or handwriting device. Examples include PCs (Personal Computers), mobile phones, smartphones, PDAs (Personal Digital Assistants), wearable devices, PPCs (Pocket PCs), tablet computers, smart car systems, smart TVs, smart speakers, and smartwatches.

[0329] Typically, terminal device 1900 includes a processor 1901 and a memory 1902.

[0330] Processor 1901 may include one or more processing cores, such as a quad-core processor, an octa-core processor, etc. Processor 1901 may be implemented using at least one hardware form selected from DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). Processor 1901 may also include a main processor and a coprocessor. The main processor, also known as a CPU (Central Processing Unit), is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, processor 1901 may integrate a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content required to be displayed on the screen. In some embodiments, processor 1901 may also include an AI (Artificial Intelligence) processor, which is used to handle computational operations related to machine learning.

[0331] The memory 1902 may include one or more computer-readable storage media, which may be non-transitory. The memory 1902 may also include high-speed random access memory and non-volatile memory, such as one or more disk storage devices or flash memory devices. In some embodiments, the non-transitory computer-readable storage media in the memory 1902 is used to store at least one instruction, which is executed by the processor 1901 to implement the present application. Figure 13 The resource transfer method provided in the illustrated embodiment, or the implementation of the method described in this application, is a method for transferring resources. Figure 14 The resource transfer method provided in the illustrated embodiment.

[0332] In some embodiments, the terminal device 1900 may also optionally include a peripheral device interface 1903 and at least one peripheral device. The processor 1901, memory 1902, and peripheral device interface 1903 can be connected via a bus or signal line. Each peripheral device can be connected to the peripheral device interface 1903 via a bus, signal line, or circuit board. Specifically, the peripheral device includes at least one of the following: radio frequency circuitry 1904, display screen 1905, camera assembly 1906, audio circuitry 1907, and power supply 1909.

[0333] Peripheral interface 1903 can be used to connect at least one I / O (Input / Output) related peripheral device to processor 1901 and memory 1902. In some embodiments, processor 1901, memory 1902 and peripheral interface 1903 are integrated on the same chip or circuit board; in some other embodiments, any one or two of processor 1901, memory 1902 and peripheral interface 1903 can be implemented on separate chips or circuit boards, which is not limited in this embodiment.

[0334] The radio frequency (RF) circuit 1904 is used to receive and transmit RF (Radio Frequency) signals, also known as electromagnetic signals. The RF circuit 1904 communicates with communication networks and other communication devices via electromagnetic signals. The RF circuit 1904 converts electrical signals into electromagnetic signals for transmission, or converts received electromagnetic signals back into electrical signals. Optionally, the RF circuit 1904 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a user identity module card, etc. The RF circuit 1904 can communicate with other terminal devices through at least one wireless communication protocol. This wireless communication protocol includes, but is not limited to: the World Wide Web, metropolitan area networks, intranets, various generations of mobile communication networks (2G, 3G, 4G, and 5G), wireless local area networks, and / or WiFi (Wireless Fidelity) networks. In some embodiments, the RF circuit 1904 may also include circuitry related to NFC (Near Field Communication), which is not limited in this application.

[0335] Display screen 1905 is used to display a UI (User Interface). This UI may include graphics, text, icons, videos, and any combination thereof. When display screen 1905 is a touch display screen, it also has the ability to collect touch signals on or above its surface. These touch signals can be input as control signals to processor 1901 for processing. In this case, display screen 1905 can also be used to provide virtual buttons and / or a virtual keyboard, also known as soft buttons and / or a soft keyboard. In some embodiments, there may be one display screen 1905, disposed on the front panel of terminal device 1900; in other embodiments, there may be at least two display screens, disposed on different surfaces of terminal device 1900 or in a folded design; in still other embodiments, display screen 1905 may be a flexible display screen, disposed on a curved or folded surface of terminal device 1900. Furthermore, display screen 1905 may also be configured as a non-rectangular, irregular shape, i.e., a non-rectangular screen. The display screen 1905 can be made of materials such as LCD (Liquid Crystal Display) and OLED (Organic Light-Emitting Diode).

[0336] The camera assembly 1906 is used to acquire images or videos. Optionally, the camera assembly 1906 includes a front-facing camera and a rear-facing camera. Typically, the front-facing camera is located on the front panel of the terminal device 1900, and the rear-facing camera is located on the back of the terminal device 1900. In some embodiments, there are at least two rear-facing cameras, which are any one of a main camera, a depth-sensing camera, a wide-angle camera, and a telephoto camera, to achieve background blurring by fusion of the main camera and the depth-sensing camera, panoramic shooting by fusion of the main camera and the wide-angle camera, VR (Virtual Reality) shooting, or other fusion shooting functions. In some embodiments, the camera assembly 1906 may also include a flash. The flash can be a single-color temperature flash or a dual-color temperature flash. A dual-color temperature flash refers to a combination of a warm light flash and a cool light flash, which can be used for light compensation at different color temperatures.

[0337] The audio circuit 1907 may include a microphone and a speaker. The microphone is used to collect sound waves from the user and the environment, converting them into electrical signals that are input to the processor 1901 for processing, or to the radio frequency circuit 1904 for voice communication. For stereo sound acquisition or noise reduction purposes, multiple microphones may be used, each located at a different part of the terminal device 1900. The microphone may also be an array microphone or an omnidirectional microphone. The speaker is used to convert electrical signals from the processor 1901 or the radio frequency circuit 1904 into sound waves. The speaker may be a conventional diaphragm speaker or a piezoelectric ceramic speaker. When the speaker is a piezoelectric ceramic speaker, it can convert electrical signals not only into audible sound waves but also into inaudible sound waves for purposes such as distance measurement. In some embodiments, the audio circuit 1907 may also include a headphone jack.

[0338] Power supply 1909 is used to power the various components in terminal device 1900. Power supply 1909 can be AC ​​power, DC power, a disposable battery, or a rechargeable battery. When power supply 1909 includes a rechargeable battery, the rechargeable battery can be a wired rechargeable battery or a wireless rechargeable battery. A wired rechargeable battery is a battery that is charged via a wired line, and a wireless rechargeable battery is a battery that is charged via a wireless coil. The rechargeable battery can also be used to support fast charging technology.

[0339] In some embodiments, the terminal device 1900 further includes one or more sensors 1910. The one or more sensors 1910 include, but are not limited to: an acceleration sensor 1911, a gyroscope sensor 1912, a pressure sensor 1913, an optical sensor 1915, and a proximity sensor 1916.

[0340] Accelerometer 1911 can detect the magnitude of acceleration along the three coordinate axes of a coordinate system established by terminal device 1900. For example, accelerometer 1911 can be used to detect the components of gravitational acceleration along the three coordinate axes. Processor 1901 can control display screen 1905 to display the user interface in either a landscape or portrait view based on the gravitational acceleration signal acquired by accelerometer 1911. Accelerometer 1911 can also be used for games or for acquiring user motion data.

[0341] The gyroscope sensor 1912 can detect the orientation and rotation angle of the terminal device 1900. The gyroscope sensor 1912 can work in conjunction with the accelerometer sensor 1911 to collect 3D motion data from the user on the terminal device 1900. Based on the data collected by the gyroscope sensor 1912, the processor 1901 can perform the following functions: motion sensing (e.g., changing the UI based on the user's tilt), image stabilization during shooting, game control, and inertial navigation.

[0342] The pressure sensor 1913 can be disposed on the side bezel of the terminal device 1900 and / or on the lower layer of the display screen 1905. When the pressure sensor 1913 is disposed on the side bezel of the terminal device 1900, it can detect the user's grip signal on the terminal device 1900, and the processor 1901 can perform left / right hand recognition or quick operation based on the grip signal collected by the pressure sensor 1913. When the pressure sensor 1913 is disposed on the lower layer of the display screen 1905, the processor 1901 can control the operable controls on the UI interface based on the user's pressure operation on the display screen 1905. The operable controls include at least one of button controls, scroll bar controls, icon controls, and menu controls.

[0343] An optical sensor 1915 is used to collect ambient light intensity. In one embodiment, the processor 1901 can control the display brightness of the display screen 1905 based on the ambient light intensity collected by the optical sensor 1915. Specifically, when the ambient light intensity is high, the display brightness of the display screen 1905 is increased; when the ambient light intensity is low, the display brightness of the display screen 1905 is decreased. In another embodiment, the processor 1901 can also dynamically adjust the shooting parameters of the camera assembly 1906 based on the ambient light intensity collected by the optical sensor 1915.

[0344] The proximity sensor 1916, also known as a distance sensor, is typically located on the front panel of the terminal device 1900. The proximity sensor 1916 is used to detect the distance between the user and the front of the terminal device 1900. In one embodiment, when the proximity sensor 1916 detects that the distance between the user and the front of the terminal device 1900 is gradually decreasing, the processor 1901 controls the display screen 1905 to switch from a screen-on state to a screen-off state; when the proximity sensor 1916 detects that the distance between the user and the front of the terminal device 1900 is gradually increasing, the processor 1901 controls the display screen 1905 to switch from a screen-off state to a screen-on state.

[0345] Those skilled in the art will understand that Figure 19 The structure shown does not constitute a limitation on the terminal device 1900, and may include more or fewer components than shown, or combine certain components, or use different component arrangements.

[0346] Figure 20This is a schematic diagram of the server structure provided in the embodiments of this application. The server 2000 can vary considerably due to different configurations or performance. It may include one or more Central Processing Units (CPUs) 2001 and one or more memories 2002, wherein the one or more memories 2002 store at least one line of program code, which is loaded and executed by the one or more processors 2001 to implement the above-mentioned... Figure 12 The resource transfer method provided in the illustrated embodiment is as follows. Of course, the server 2000 may also have wired or wireless network interfaces, a keyboard, and input / output interfaces for input / output. The server 2000 may also include other components for implementing device functions, which will not be elaborated upon here.

[0347] In an exemplary embodiment, a computer-readable storage medium is also provided, which stores at least one piece of program code that is loaded and executed by a processor to enable a computer to implement any of the resource transfer methods described above.

[0348] Optionally, the aforementioned computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a compact disc read-only memory (CD-ROM), magnetic tape, floppy disk, and optical data storage device, etc.

[0349] In an exemplary embodiment, a computer program or computer program product is also provided, which stores at least one computer instruction that is loaded and executed by a processor to enable the computer to implement any of the resource transfer methods described above.

[0350] It should be noted that all information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, stored data, displayed data, etc.), and signals involved in this application have been authorized by the user or fully authorized by all parties, and the collection, use, and processing of related data must comply with the relevant laws, regulations, and standards of the relevant countries and regions. For example, the object identifiers, object information, and various pages involved in this application were obtained with full authorization.

[0351] It should be understood that "multiple" as used in this article refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0352] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0353] The above description is merely an exemplary embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the principles of this application should be included within the protection scope of this application.

Claims

1. A resource transfer method, characterized in that, The method includes: A resource transfer request sent by a terminal device that receives a resource transfer object, wherein the resource transfer request includes the object identifier of the resource transfer object, the object identifier of the resource receiving object, and the resource transfer value; Send a verification request to the terminal device of the verification object of the resource transfer object, the verification request including the object identifier of the resource transfer object; Receive the verification result returned by the terminal device of the verification object; If the verification result meets the verification requirements, the resources of the resource transfer value are transferred from the account of the resource transfer object to the account of the resource receiving object.

2. The method according to claim 1, characterized in that, Before sending a verification request to the terminal device of the verification object of the resource transfer object, the method further includes: The risk level of the resource transfer transaction is determined based on at least one of the object identifier of the resource transfer object, the object identifier of the resource receiving object, or the resource transfer value. Sending a verification request to the terminal device of the verification object of the resource transfer object includes: If the risk level is greater than the level threshold, a verification request is sent to the terminal device of the verification object of the resource transfer object.

3. The method according to claim 2, characterized in that, When the risk level is greater than the risk level threshold, sending a verification request to the terminal device of the verification object of the resource transfer object includes: If the risk level is greater than the risk level threshold, a risk warning message is sent to the terminal device of the resource transfer target; Upon receiving the instruction information returned by the terminal device of the resource transfer object, a verification request is sent to the terminal device of the verification object of the resource transfer object.

4. The method according to claim 2, characterized in that, Before sending a verification request to the terminal device of the verification object of the resource transfer object, the method further includes: When the risk level is greater than the risk level threshold, the ratio corresponding to the risk level is determined, and the risk level and the ratio are positively correlated. The target quantity is determined based on the number of connected objects of the resource transfer object and the ratio. The verification object is determined from the contact objects, and the number of the verification objects is the target number.

5. The method according to claim 4, characterized in that, Determining the verification object from the contact objects includes: Based on the response time of each contact, the contact objects are sorted according to the target order to obtain the sorting result. The response time of any contact object is used to indicate the time between sending a verification request to the contact object and receiving the verification result returned by the contact object. The contact objects that appear before the target number in the sorting results are identified as the verification objects.

6. The method according to any one of claims 1 to 5, characterized in that, The verification result returned by the terminal device receiving the verification object includes: The terminal device receiving the verification information includes the object identifier and target information of the verification object, wherein the target information is information obtained by signing the verification result according to the private key of the verification object; The public key of the verification object is determined based on the object identifier of the verification object; The target information is verified using the public key of the verification object to obtain the verification result.

7. A resource transfer method, characterized in that, The method includes: The resource transfer page displays the object identifier of the resource receiving object and the resource transfer value; When the resource transfer function is triggered, a resource transfer request is sent to the server. The resource transfer request is used by the server to send a verification request to the terminal device of the verification object of the resource transfer object, receive the verification result returned by the terminal device of the verification object, and if the verification result meets the verification requirements, transfer the resources of the resource transfer value from the account of the resource transfer object to the account of the resource receiving object. The resource transfer request includes the object identifier of the resource transfer object, the object identifier of the resource receiving object, and the resource transfer value, and the verification request includes the object identifier of the resource transfer object.

8. The method according to claim 7, characterized in that, Before displaying the resource transfer page, the method further includes: The homepage of the resource transfer object is displayed, and the homepage displays resource transfer controls; In response to a triggered operation on the resource transfer control, the resource transfer page is displayed.

9. The method according to claim 8, characterized in that, The homepage also displays a contact object control, which is used to obtain the contact object of the resource transfer object; the method further includes: In response to a trigger operation on the contact object control, the contact object page is displayed, and the contact object page displays an add control; In response to the triggering operation of the added control, the Add Contact Object page is displayed, in which an object identification box is displayed; Based on the input operation in the object identifier box, obtain the object identifier of the reference object; When the add contact object function is triggered, the object identifier of the reference object is sent to the server. The object identifier of the reference object is used by the server to use the reference object as the contact object of the resource transfer object.

10. The method according to claim 9, characterized in that, When the function to add a contact object is triggered, sending the object identifier of the reference object to the server includes: When the add contact object function is triggered, a first notification message is sent to the terminal device of the reference object. The first notification message is used to notify the reference object as the contact object of the resource transfer object. Upon receiving a confirmation message from the terminal device of the reference object, the object identifier of the reference object is sent to the server. The confirmation message is used to instruct the reference object to confirm the contact object as the resource transfer object.

11. The method according to any one of claims 7 to 10, characterized in that, After sending the resource transfer request to the server, the method further includes: Receive risk warning information returned by the server when the risk level is greater than the risk level threshold; Display the aforementioned risk warning information; In response to the triggering operation of the risk warning information, an instruction information is sent to the server, which is used by the server to send a verification request to the terminal device of the verification object.

12. The method according to any one of claims 7 to 10, characterized in that, When the resource transfer function is triggered, sending a resource transfer request to the server includes: When the resource transfer function is triggered, a resource transfer password interface is displayed, which is used by the resource transfer object to enter the resource transfer password. The resource transfer password is obtained based on the input operation in the resource transfer password interface; If the resource transfer password verification is successful, the resource transfer request is sent to the server.

13. A resource transfer method, characterized in that, The method includes: Receive a verification request sent by the server, the verification request including the object identifier of the resource transfer object; Based on the verification request, a verification page is displayed, which displays the object identifier of the resource transfer object; In response to a triggered action on the verification page, obtain the verification result; The server sends the verification result, which is used by the server to transfer the resource transfer value from the resource transfer object's account to the resource receiving object's account if the verification result meets the verification requirements.

14. The method according to claim 13, characterized in that, After obtaining the verification result, the method further includes: The verification result is signed based on the private key of the verification object to obtain the target information; Sending the verification result to the server includes: The server sends verification information, which includes the object identifier of the verification object and the target information. The verification information is used by the server to verify the target information based on the public key of the verification object, and obtain the verification result.

15. A resource transfer device, characterized in that, The device includes: The receiving module is used to receive a resource transfer request sent by the terminal device of the resource transfer object. The resource transfer request includes the object identifier of the resource transfer object, the object identifier of the resource receiving object, and the resource transfer value. The sending module is configured to send a verification request to the terminal device of the verification object of the resource transfer object, wherein the verification request includes the object identifier of the resource transfer object; The receiving module is also used to receive the verification result returned by the terminal device of the verification object; The transfer module is used to transfer the resources of the resource transfer value from the account of the resource transfer object to the account of the resource receiving object when the verification result meets the verification requirements.

16. A resource transfer device, characterized in that, The device includes: The display module is used to display the resource transfer page, which displays the object identifier of the resource receiving object and the resource transfer value; The sending module is used to send a resource transfer request to the server when the resource transfer function is triggered. The resource transfer request is used by the server to send a verification request to the terminal device of the verification object of the resource transfer object, receive the verification result returned by the terminal device of the verification object, and transfer the resources of the resource transfer value from the account of the resource transfer object to the account of the resource receiving object if the verification result meets the verification requirements. The resource transfer request includes the object identifier of the resource transfer object, the object identifier of the resource receiving object, and the resource transfer value, and the verification request includes the object identifier of the resource transfer object.

17. A resource transfer device, characterized in that, The device includes: A receiving module is used to receive a verification request sent by the server, wherein the verification request includes the object identifier of the resource transfer object; The display module is used to display a verification page according to the verification request, wherein the verification page displays the object identifier of the resource transfer object; The acquisition module is used to acquire the verification result in response to a trigger operation on the verification page; The sending module is used to send the verification result to the server. The verification result is used by the server to transfer the resource transfer value from the account of the resource transfer object to the account of the resource receiving object when the verification result meets the verification requirements.

18. A computer device, characterized in that, The computer device includes a processor and a memory, the memory storing at least one line of program code, the at least one line of program code being loaded and executed by the processor to enable the computer device to implement the resource transfer method as described in any one of claims 1 to 14.

19. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores at least one piece of program code, which is loaded and executed by a processor to enable the computer to implement the resource transfer method as described in any one of claims 1 to 14.

20. A computer program product, characterized in that, The computer program product stores at least one computer instruction, which is loaded and executed by a processor to enable the computer to implement the resource transfer method as described in any one of claims 1 to 14.

Images