Method, apparatus, and system for verifying real-name state, server, and storage medium

Abstract

The application relates to a method, device, system, server and storage medium for verifying a real-name state. The method comprises the following steps: receiving a real-name verification request generated based on a resource transfer-in request sent by a service server; searching for real-name state information of a resource transfer-in party in an in-memory database according to the real-name verification request; if the real-name state information of the resource transfer-in party is not found, forwarding the real-name verification request to an authentication server, collecting real-name authentication information of the resource transfer-in party when the authentication server determines that the resource transfer-in party has not been authenticated, and storing real-name state information generated based on the real-name authentication information in the in-memory database; and if the real-name state information of the resource transfer-in party is found, returning confirmation information of having been authenticated to the service server, so that the service server transfers into resources specified by the resource transfer-in request. The method can improve the efficiency of real-name state verification.

Description

Technical Field

[0001] This application relates to the field of blockchain technology, and in particular to a method, apparatus, system, server, and storage medium for verifying real-name status. Background Technology

[0002] With the continuous development of Internet technology, more and more users are handling various businesses through smart terminals. For example, in some application scenarios, users may transfer some numerical resources to other users or receive some numerical resources transferred from other users.

[0003] When a user receives numerical resources transferred from other users, the business server typically initiates a remote procedure call (RPC) request to the verification server to verify whether the user has completed real-name authentication. The verification server then forwards the RPC request to a third-party authentication server, which determines whether the user has been authenticated. However, if there are many users transferring numerical resources, verifying real-name status using this method will significantly reduce the efficiency of real-name authentication, thus affecting the efficiency of resource transfer. Summary of the Invention

[0004] Therefore, it is necessary to provide a method, apparatus, system, server, and storage medium for verifying real-name status to address the aforementioned technical problems and improve the efficiency of real-name status verification.

[0005] A method for verifying real-name status, the method comprising:

[0006] Receive the real-name verification request generated based on the resource transfer request sent by the business server;

[0007] In the in-memory database, the real-name status information of the resource transferee is retrieved based on the real-name verification request;

[0008] If the real-name status information of the resource transferee is not found, the real-name verification request is forwarded to the authentication server. When the authentication server determines that the resource transferee has not been real-name authenticated, the real-name authentication information of the resource transferee is collected and the real-name status information generated based on the real-name authentication information is stored in the memory database.

[0009] If the real-name status information of the resource transferee is found, a confirmation message indicating that the real-name authentication has been completed is returned to the business server, so that the business server can transfer the resource specified in the resource transfer request.

[0010] A device for verifying real-name status, the device comprising:

[0011] The receiving module is used to receive real-name verification requests generated based on resource transfer requests sent by the business server;

[0012] The lookup module is used to search the real-name status information of the resource transferee in the in-memory database based on the real-name verification request.

[0013] The verification module is used to forward the real-name verification request to the authentication server if the real-name status information of the resource transferee is not found, and when the authentication server determines that the resource transferee has not been real-name authenticated, it collects the real-name authentication information of the resource transferee and stores the real-name status information generated based on the real-name authentication information in the memory database.

[0014] The sending module is used to return a confirmation message indicating that the resource transferee has been verified to the business server if the real-name status information of the resource transferee is found, so that the business server can transfer the resource specified in the resource transfer request.

[0015] In one embodiment, the verification module is further configured to send first feedback information to the business server to prompt real-name authentication when the authentication server determines that the resource transferee has not been real-name authenticated, so that the business server initiates a real-name authentication request to the terminal of the resource transferee to collect the real-name authentication information of the resource transferee; and receive real-name authentication information for the resource transferee from the business server.

[0016] In one embodiment, the device further includes:

[0017] The first storage module is used to store the verified information as transaction information in a relational database if the real-name status information of the resource transferee is found; if the real-name status information of the resource transferee is not found and the business server initiates a real-name authentication request to the terminal of the resource transferee, the real-name authentication request is stored as transaction information in the relational database.

[0018] In one embodiment, the device further includes:

[0019] The first acquisition module is used to acquire the real-name authentication information of all resource transferors who received resource transfer requests within a specified time period on the authentication server when a preset reconciliation time is reached or a reconciliation instruction is received; and to read the transaction information of all resource transferors from the relational database.

[0020] The comparison module is used to compare the read transaction information with the real-name status information to find the target resource transfer party that has not performed real-name authentication on the authentication server but has not initiated the real-name authentication request to request real-name authentication.

[0021] The sending module is further configured to send a second feedback message to the business server; the second feedback message is configured to instruct the business server to initiate a real-name authentication request in order to collect the real-name authentication information of the target resource transferee.

[0022] In one embodiment, the second feedback information is further used to instruct the business server to intercept the resource transfer operation corresponding to the resource transfer request when the business server receives a resource transfer request from the target resource transferee.

[0023] In one embodiment, the device further includes:

[0024] The second acquisition module is used to acquire real-name authentication information from the authentication server when the authentication server determines that the resource transferee has been real-name authenticated.

[0025] The second storage module is used to generate real-name status information based on the real-name authentication information and store it in the memory database.

[0026] In one embodiment, the receiving module is further configured to receive a real-name verification request sent by a client in the business server; wherein the real-name verification request is a remote procedure call request for requesting real-name verification generated by the business terminal in the business server based on the resource transfer request.

[0027] In one embodiment, the client in the business server is configured to send the real-name verification request when the number of real-name verification requests generated by the business terminal does not reach the business degradation condition; and to stop sending the real-name verification request when the number of real-name verification requests generated by the business terminal reaches the business degradation condition.

[0028] A system for verifying real-name status, the system comprising:

[0029] The business server is used to generate a real-name verification request based on the resource transfer request and send the real-name verification request to the verification server.

[0030] The verification server is configured to receive the real-name verification request sent by the business server; search for the real-name status information of the resource transferee in the memory database according to the real-name verification request; if the real-name status information of the resource transferee is not found, forward the real-name verification request to the authentication server.

[0031] The authentication server is used to send a confirmation message of non-real-name authentication to the verification server when it determines that the resource transferor has not been real-name authenticated.

[0032] The verification server is also used to collect the real-name authentication information of the resource transferee and store the real-name status information generated based on the real-name authentication information in the memory database; if the real-name status information of the resource transferee is found, the server returns a confirmation message that the real-name authentication has been completed to the business server.

[0033] The business server is also used to transfer the resource specified in the resource transfer request.

[0034] In one embodiment, the verification server includes a server-side component; the server-side component is configured to send first feedback information to the business server to prompt real-name authentication when the authentication server determines that the resource transferee has not undergone real-name authentication, so that the business server initiates a real-name authentication request to the terminal of the resource transferee to collect the real-name authentication information of the resource transferee; and to receive real-name authentication information for the resource transferee from the business server.

[0035] In one embodiment, the server is further configured to, if the real-name status information of the resource transferee is found, store the confirmed real-name authentication information as transaction information in a relational database; if the real-name status information of the resource transferee is not found, and the business server initiates a real-name authentication request to the terminal of the resource transferee, store the real-name authentication request as transaction information in the relational database.

[0036] In one embodiment, the server is further configured to, when a preset reconciliation time is reached or a reconciliation instruction is received, obtain the real-name authentication information of all resource transferors who received resource transfer requests within a specified time period on the authentication server; read the transaction information of all resource transferors from the relational database; compare the read transaction information with the real-name status information to identify the target resource transferor that has not performed real-name authentication on the authentication server but has not initiated the real-name authentication request to request real-name authentication; and send a second feedback message to the business server.

[0037] The business server is used to initiate a real-name authentication request when it receives the second feedback information, so as to collect the real-name authentication information of the target resource transferee.

[0038] In one embodiment, the service server is configured to intercept the resource transfer operation corresponding to the resource transfer request when it receives a resource transfer request from the target resource transferee.

[0039] In one embodiment, the client in the business server is further configured to, after sending the remote procedure call request to the verification server, collect statistics on the verification server's response information to the remote procedure call request; and when it is determined from the response information that the verification server's response rate is lower than a preset response rate, stop sending remote procedure call requests to the verification server.

[0040] In one embodiment, the client in the business server is configured to stop sending the real-name verification request to the target verification server when it is determined that the target verification server among the at least two verification servers has an abnormal response.

[0041] A verification server includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to perform the following steps:

[0042] Receive the real-name verification request generated based on the resource transfer request sent by the business server;

[0043] In the in-memory database, the real-name status information of the resource transferee is retrieved based on the real-name verification request;

[0044] If the real-name status information of the resource transferee is not found, the real-name verification request is forwarded to the authentication server. When the authentication server determines that the resource transferee has not been real-name authenticated, the real-name authentication information of the resource transferee is collected and the real-name status information generated based on the real-name authentication information is stored in the memory database.

[0045] If the real-name status information of the resource transferee is found, a confirmation message indicating that the real-name authentication has been completed is returned to the business server, so that the business server can transfer the resource specified in the resource transfer request.

[0046] A computer-readable storage medium having a computer program stored thereon, the computer program performing the following steps when executed by a processor:

[0047] Receive the real-name verification request generated based on the resource transfer request sent by the business server;

[0048] In the in-memory database, the real-name status information of the resource transferee is retrieved based on the real-name verification request;

[0049] If the real-name status information of the resource transferee is not found, the real-name verification request is forwarded to the authentication server. When the authentication server determines that the resource transferee has not been real-name authenticated, the real-name authentication information of the resource transferee is collected and the real-name status information generated based on the real-name authentication information is stored in the memory database.

[0050] If the real-name status information of the resource transferee is found, a confirmation message indicating that the real-name authentication has been completed is returned to the business server, so that the business server can transfer the resource specified in the resource transfer request.

[0051] The aforementioned method, apparatus, system, server, and storage medium for verifying real-name status, upon receiving a real-name verification request generated based on a resource transfer request, first search for the real-name status information of the resource transferee in the memory database. Only when the real-name status information of the resource transferee is not found, i.e., it is uncertain whether the resource transferee has performed real-name authentication, will the real-name verification request be forwarded to the authentication server to request verification. This significantly reduces the amount of interaction between the verification server and the authentication server, improving the efficiency of real-name status verification and resource transfer. Furthermore, if the real-name status information of the resource transferee is found, it indicates that the resource transferee has performed real-name authentication. In this case, a confirmation message of real-name authentication is directly returned to the business server, allowing the business server to transfer the resource specified in the resource transfer request without interacting with the authentication server, thus improving the efficiency of resource transfer. Attached Figure Description

[0052] Figure 1 This is an application environment diagram of a method for verifying real-name status in one embodiment;

[0053] Figure 2 This is a flowchart illustrating a method for verifying real-name status in one embodiment;

[0054] Figure 3 This is a schematic diagram of the interface for sending red envelopes by the sending end in one embodiment;

[0055] Figure 4 This is a flowchart illustrating the application scenario of verifying real-name status in receiving red envelopes, as shown in one embodiment.

[0056] Figure 5 This is a flowchart illustrating the steps of identifying the target resource recipient and making a real-name authentication request in one embodiment.

[0057] Figure 6 This is a flowchart illustrating the client's degradation and load balancing steps in one embodiment.

[0058] Figure 7This is a schematic diagram illustrating the structure between the business side, the client side, and the server side in one embodiment.

[0059] Figure 8 This is a flowchart illustrating a method for verifying real-name status in another embodiment;

[0060] Figure 9 This is a structural block diagram of a device for verifying real-name status in one embodiment;

[0061] Figure 10 This is a structural block diagram of a device for verifying real-name status in another embodiment;

[0062] Figure 11 This is a diagram of the internal structure of a server in one embodiment. Detailed Implementation

[0063] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0064] The method for verifying real-name status provided in this application can be applied to a system for verifying real-name status, which can be a distributed system formed by multiple terminals and multiple nodes connected through network communication.

[0065] Taking a distributed system as an example, see blockchain system. Figure 1 , Figure 1 This is an optional structural diagram of a distributed system applied to a blockchain system according to an embodiment of the present invention. It consists of two terminals and multiple nodes: a first terminal 102, a business server 104, a verification server 106, an authentication server 108, and a second terminal 110. The business server 104, verification server 106, and authentication server 108 are nodes in the blockchain. These nodes form a peer-to-peer (P2P) network. The P2P protocol is an application layer protocol running on top of the Transmission Control Protocol (TCP).

[0066] The first terminal 102 can act as the resource transferor (i.e., the sending end) to perform resource transfer operations, such as sending a red envelope or initiating a transfer. The second terminal 110 can act as the resource transferee (i.e., the receiving end) to perform resource transfer operations, such as clicking on a red envelope or transfer message sent by the first terminal 102 to receive the corresponding red envelope or transfer. The first terminal 102 and the second terminal 110 can be smartphones, tablets, laptops, desktop computers, smart speakers, smartwatches, etc., but are not limited to these. The resource transferor is the user transferring the resources, and the resource transferee is the user receiving the resources transferred from the resource transferor.

[0067] The business server 104 receives resource transfer-out requests initiated by the first terminal 102, which are equivalent to resource transfer-in requests for the second terminal 110. Upon receiving the resource transfer-in request, the business server 104 generates a real-name verification request based on the request and sends it to the verification server 106 to verify whether the resource transferee has completed real-name authentication. If it is determined that the resource transferee has completed real-name authentication, the resources specified in the resource transfer-in request are transferred to the resource transferee's resource account.

[0068] Verification server 106, upon receiving a real-name verification request, searches its in-memory database for the real-name status information of the resource transferee. If no real-name status information is found, it forwards the real-name verification request to authentication server 108, allowing authentication server 108 to verify whether the resource transferee has undergone real-name authentication. If the real-name status information is found, it returns a confirmation message indicating real-name authentication to business server 104, enabling business server 104 to transfer the resource specified in the resource transfer request.

[0069] The authentication server 108 is used to store the real-name authentication information of each user (including the resource transferor and the resource transferor). After receiving the real-name verification request forwarded by the verification server 106, it performs real-name verification on the resource transferor, that is, verifies whether the resource transferor has performed real-name authentication.

[0070] The aforementioned business server 104, verification server 106, and authentication server 108 can be independent physical servers or a server cluster consisting of multiple physical servers.

[0071] In one embodiment, such as Figure 2 As shown, a method for verifying real-name status is provided, which can be applied to... Figure 1 Taking the verification server in the example, the following steps are included:

[0072] S202, Receive the real-name verification request generated based on the resource transfer request sent by the business server.

[0073] The business server can be a server used to process resource transfer services, which include receiving red envelopes or money transfers.

[0074] This resource transfer request is directed to the receiving end (i.e., the terminal of the resource transferee), indicating that the business server has received a resource transfer request to transfer resources to the receiving end.

[0075] This real-name verification request can be used to verify whether the resource transfer recipient has completed real-name authentication. For example, the business server sends this real-name verification request to the verification server, which then uses this request to verify whether the resource transfer recipient has completed real-name authentication. For instance, in a scenario involving receiving red envelopes (digital cash gifts), when the business server receives a red envelope receiving request from user A, it will generate a real-name verification request based on the request to verify whether user A has completed real-name authentication.

[0076] In one embodiment, when the business server receives resource transfer requests from various senders, it first determines the number of resource transfer requests received. If the number of resource transfer requests reaches a preset threshold, it stops sending real-name verification requests to the verification server and directly transfers the resources specified in the resource transfer request to the resource recipient's resource account. If the number of resource transfer requests does not reach the preset threshold, it sends a real-name verification request to the verification server to verify whether the resource recipient has completed real-name authentication. This embodiment can avoid the problem of abnormal resource transfers caused by too many resource transfers in a short period of time during peak resource transfer periods such as holidays.

[0077] S204, in the in-memory database, look up the real-name status information of the resource transferee based on the real-name verification request.

[0078] In-memory databases refer to databases that store real-name status information in memory for direct manipulation. In practical applications, this in-memory database can be a Redis database, which is used to store non-relational data. Data reads occur entirely in memory, resulting in fast read speeds.

[0079] The resource recipient is the user receiving the resources transferred from the resource sender. This real-name status information can indicate that the resource recipient has completed real-name authentication, and may include the resource recipient's real-name authentication information (such as ID card number and facial image). Furthermore, this real-name status information may also include status information generated based on the real-name authentication information, indicating that real-name authentication has been completed. This can be represented by numbers, characters, or a combination of numbers and characters, such as 1 indicating real-name authentication completed, and 0 or empty (i.e., no real-name status information) indicating no real-name authentication completed.

[0080] In one embodiment, the verification server reads the resource transferor's identification information from the real-name verification request and searches for the resource transferor's real-name status information in the in-memory database based on the identification information in the real-name verification request. When the resource transferor's real-name status information is found, it indicates that the resource transferor has completed real-name authentication; when the resource transferor's real-name status information is not found, it indicates that the verification server is unsure whether the resource transferor has completed real-name authentication. In this case, a real-name verification request needs to be sent to the authentication server so that the authentication server can determine whether the resource transferor has completed real-name authentication. Through this embodiment, the real-name verification request is only forwarded to the authentication server when the verification server is unsure whether the resource transferor has completed real-name authentication, thereby greatly reducing the amount of interaction between the verification server and the authentication server, improving the efficiency of real-name status verification, and also improving the efficiency of resource transfer.

[0081] S206 If the real-name status information of the resource transferee is not found, forward the real-name verification request to the authentication server. When the authentication server determines that the resource transferee has not been real-name authenticated, collect the real-name authentication information of the resource transferee and store the real-name status information generated based on the real-name authentication information in the memory database.

[0082] The real-name authentication information can be the identity information of the resource transferee uploaded by the resource transferee through the receiving end, such as at least one of the resource transferee's name, address, ID card image, ID card number, facial image, and fingerprint.

[0083] In one embodiment, the step of collecting the real-name authentication information of the resource transferee when the authentication server determines that the resource transferee has not been real-name authenticated may specifically include: when the authentication server determines that the resource transferee has not been real-name authenticated, the verification server sends a first feedback message to the business server to prompt real-name authentication, so that the business server initiates a real-name authentication request to the terminal of the resource transferee (hereinafter referred to as the receiving end) to collect the real-name authentication information of the resource transferee; and receives the real-name authentication information for the resource transferee from the business server.

[0084] The authentication server can determine whether the resource transferor has completed real-name authentication by checking if it stores the resource transferor's real-name authentication information. This first feedback information can be used to prompt the resource transferor to complete real-name authentication. For example, when the business server receives this first feedback information, it sends a real-name authentication request carrying the first feedback information to the receiving end, so that the receiving end can display the first feedback information after receiving the real-name authentication request, thus prompting the resource transferor to complete real-name authentication before receiving the resources.

[0085] When the resource transferee uploads real-name authentication information through the receiving end, the verification server receives the uploaded real-name authentication information. Firstly, it verifies the real-name authentication information to determine if it represents the resource transferee's genuine information. Secondly, if the real-name authentication information is confirmed to be genuine, it generates real-name status information for that resource transferee based on the real-name authentication information and stores this real-name status information in an in-memory database. Furthermore, when storing the real-name status information, the resource transferee's index identifier can also be stored, such as their ID card number, name, or contact number.

[0086] In another embodiment, when the authentication server determines that the resource transferee has been verified with its real name, it obtains the verified real name authentication information from the authentication server; based on the real name authentication information, it generates real name status information and stores it in an in-memory database. Therefore, when the server receives a real name verification request from the resource transferee again, it can retrieve the resource transferee's real name status information from the in-memory database.

[0087] In one embodiment, if the real-name status information of the resource transferee is not found, and the business server initiates a real-name authentication request to the resource transferee's terminal, the real-name authentication request is stored as transaction log information in a relational database. When reconciliation is required, the transaction log information stored in this relational database is compared with the real-name authentication information stored in the authentication server to identify the abnormal resource transferee. For example, if the authentication server has not performed real-name authentication for a resource transferee but has not initiated a real-name authentication request, it indicates that the real-name authentication information of that resource transferee in the verification server is inaccurate. It should be noted that whether a resource transferee is real-name authenticated is usually determined by the verification result of the authentication server. The relational database can be SQL Server, MySQL, or Oracle, etc.

[0088] S208 If the real-name status information of the resource transferee is found, return the real-name authentication confirmation information to the business server so that the business server can transfer the resource specified in the resource transfer request.

[0089] If the real-name status information of the resource transferee is found, it means that the resource transferee has completed real-name authentication, and there is no need to send a real-name verification request to the authentication server.

[0090] Specifically, if the real-name status information of the resource transferee is found, the verification server returns confirmation information to the business server that the resource transferee has completed real-name authentication, so that the business server can transfer the resources specified in the resource transfer request to the resource transferee's resource account.

[0091] In one embodiment, if the real-name status information of the resource transferee is found, the confirmed information of the real-name authentication is stored as transaction information in a relational database. When reconciliation is required, the transaction information stored in the relational database is compared with the real-name authentication information stored in the authentication server to find the resource transferee that has an anomaly.

[0092] To better understand the methods for verifying real-name status, we will illustrate them using a specific scenario of receiving red envelopes, as follows:

[0093] like Figure 3 As shown, when the resource sender triggers the red envelope sending operation through the sending end (i.e., the resource sender's terminal), that is, by triggering the operation of sending a red envelope to Xiaoming through the "red envelope" button in the conversation page of the social application, the sending end will generate a red envelope sending request and send it to the business server. In this case, when Xiaowang sends a red envelope to Xiaoming, the red envelope sending request received by the business server is, for Xiaoming, a red envelope sending request is a red envelope receiving request.

[0094] like Figure 4 As shown, Figure 4 The process of verifying the identity of the recipient before they can receive a red envelope is as follows:

[0095] S402, the sending end sends a request to the business server to receive a red envelope for Xiaoming.

[0096] S404, the business server generates a real-name verification request based on the red envelope receiving request.

[0097] S406, the business server sends a real-name verification request to the verification server.

[0098] S408: After receiving the real-name verification request, the verification server checks in the memory server whether Xiaoming's real-name status information exists.

[0099] S410 If Xiaoming's real-name status information is found, transfer the amount in the red envelope to Xiaoming's resource account.

[0100] S412 If Xiaoming's real-name status information is not found, forward the real-name verification request to the authentication server.

[0101] S414. If the authentication server does not store Xiaoming's real-name authentication information, it is determined that Xiaoming has not been real-name authenticated.

[0102] S416, when it is determined that Xiaoming has not been real-name authenticated, the verification server sends a real-name authentication request carrying feedback information to the receiving end.

[0103] S418: After receiving the real-name authentication request, the receiving end displays feedback information to prompt Xiaoming to perform real-name authentication.

[0104] S420: After obtaining Xiaoming's real-name authentication information, the receiving end uploads the real-name authentication information to the authentication server and the verification server.

[0105] After receiving Xiaoming's real-name authentication information, the verification server generates real-name status information about Xiaoming based on the real-name authentication information and stores the real-name status information in an in-memory database.

[0106] S422, after confirming that Xiaoming has completed real-name authentication, the business server transfers the amount from the red envelope to Xiaoming's resource account.

[0107] Specifically, the amount specified in the red envelope receiving request will be transferred to Xiaoming's resource account.

[0108] Through the above embodiments, upon receiving a real-name verification request generated based on a resource transfer request, the system first searches for the real-name status information of the resource transferee in the memory database. Only when the real-name status information of the resource transferee is not found, i.e., it is uncertain whether the resource transferee has performed real-name authentication, will the real-name verification request be forwarded to the authentication server to request verification. This significantly reduces the amount of interaction between the verification server and the authentication server, improving the efficiency of real-name status verification and resource transfer. Furthermore, if the real-name status information of the resource transferee is found, it indicates that the resource transferee has performed real-name authentication. In this case, a confirmation message of real-name authentication is directly returned to the business server, allowing the business server to transfer the resource specified in the resource transfer request without interacting with the authentication server, thus improving the efficiency of resource transfer.

[0109] In one embodiment, the verification server can also reconcile transaction logs in the relational database with real-name status information on the authentication server to identify the recipient of the abnormal resource transfer. For example... Figure 5 As shown, the method also includes:

[0110] S502: When the preset reconciliation time is reached or a reconciliation instruction is received, obtain the real-name authentication information of all resource transferors who received resource transfer requests within the specified time period on the authentication server.

[0111] The preset reconciliation time can be a pre-set trigger signal used to periodically initiate reconciliation, such as midnight (00:00) every day. The specified time period can be a fixed time period, such as the period from 00:00 to 23:59 every day.

[0112] S504 reads the flow information of all resource transfer recipients from a relational database.

[0113] The transaction information includes confirmation that the resource transferee has completed real-name authentication, and a real-name authentication request sent by the resource transferee due to failure to complete real-name authentication. This real-name authentication request indicates that the resource transferee has not completed real-name authentication and that the verification server requires the resource transferee to complete real-name authentication.

[0114] S506 compares the read transaction information with the real-name status information to identify the target resource transferor that has not performed real-name authentication on the authentication server but has not initiated a real-name authentication request to request real-name authentication.

[0115] In this case, the recipient of the target resource did not perform real-name authentication on the authentication server, indicating that the recipient did not actually perform real-name authentication. However, the verification server did not send a real-name authentication request to the recipient's terminal, causing a problem with the transaction record information stored on the verification server side. In other words, the transaction record information confirming that the recipient has performed real-name authentication is problematic. In reality, the recipient has not performed real-name authentication, and a real-name authentication request needs to be sent to the recipient's terminal to enable the recipient to perform real-name authentication.

[0116] The real-name authentication information stored on the authentication server can be used as a reference to determine whether the resource transfer recipient has been real-name authenticated. By comparing the real-name authentication information on the authentication server with the transaction information read from the relational database, it can be determined whether the transaction information in the relational database is accurate.

[0117] S508 sends a second feedback message to the business server; the second feedback message is used to instruct the business server to initiate a real-name authentication request in order to collect the real-name authentication information of the target resource transferee.

[0118] Specifically, by sending a second feedback message to the business server, the business server initiates a real-name authentication request carrying the second feedback message to the terminal of the target resource initiator. The terminal displays the second feedback message, prompting the target resource initiator to perform real-name authentication, thereby obtaining the real-name authentication information of the target resource transferee.

[0119] Furthermore, this second feedback information is also used to instruct the business server to intercept the resource transfer operation corresponding to the resource transfer request when it receives a resource transfer request from the target resource transferee. This ensures that the target resource transferee will intercept the resource transfer operation the next time it receives resources and require the target resource transferee to perform real-name authentication.

[0120] In the above embodiments, by comparing the transaction log information of the resource transferor in the relational database with the real-name status information of the resource transferor on the authentication server, it is possible to find target resource transferors who have not performed real-name authentication on the authentication server and have not initiated a real-name authentication request to request real-name authentication. The transaction log information of the target resource transferor in the relational database has problems, and a real-name authentication request should be initiated to the target resource transferor to ensure that the target resource transferor performs real-name authentication before receiving resources, thereby improving the security of resource transfer.

[0121] Since the real-name verification request can be sent by a client on the business server, it is a remote procedure call request generated by the business side on the business server based on a resource transfer request for real-name verification. Furthermore, the client on the business server is used to send a real-name verification request when the number of real-name verification requests generated by the business side has not reached the business degradation condition; and to stop sending real-name verification requests when the number of real-name verification requests generated by the business side reaches the business degradation condition. In addition, the client on the business server can also be used to stop sending real-name verification requests to the target verification server when it is determined that the target verification server's response is abnormal among at least two verification servers. Therefore, as... Figure 6 As shown, the method may further include:

[0122] S602, the business end in the business server receives the resource transfer request sent by the sending end.

[0123] The service end can be an application that handles resource transfers, such as processing the receipt of red envelopes or money transfers. The sending end can be a terminal that sends resource transfer requests, such as a terminal that sends red envelopes or money transfers.

[0124] S604, the business side in the business server generates a real-name verification request based on the resource transfer request.

[0125] The real-name verification request can be a remote procedure call request used to request real-name verification.

[0126] S606: When it is determined that the target verification server in the verification server has an abnormal response, the client stops sending real-name verification requests to the target verification server.

[0127] The verification server can be a cluster of multiple servers used to verify real-name status. The client can read the IP (Internet Protocol) address of the verification server from the configuration file, and then randomly send a real-name verification request to one of them.

[0128] In one embodiment, the client also records the response information of the verification server each time it receives a real-name verification request, determines invalid responses from the verification server based on this response information, and records the number of invalid responses. When the number of invalid responses from the target verification server exceeds a preset invalid response threshold, the client stops sending real-name verification requests to the target verification server.

[0129] In addition, when the target verification server returns to normal, the client will gradually send real-name verification requests to the target verification server and gradually restore the original request traffic, thereby improving availability.

[0130] S608: When the number of real-name verification requests generated by the business side reaches the business degradation condition, the client stops sending real-name verification requests to the verification server.

[0131] Among them, business degradation can refer to stopping the sending of real-name verification requests to the verification server when the number of real-name verification requests is too large. As a result, when the business receives a resource transfer request, it does not need to verify whether the resource transferee has been real-name authenticated, and can directly transfer the resource to the resource account specified in the resource transfer request.

[0132] In one embodiment, the client reads the configuration file. When the configuration file is configured with a degradation function, it can determine whether the number of real-name verification requests generated by the business side has reached the business degradation condition. If it has, the client stops sending real-name verification requests to the verification server.

[0133] Furthermore, when a degradation function is configured in the configuration file, the client can also determine the business type targeted by the degradation function. If the resource transfer business corresponding to the real-name verification request belongs to that business type, and the number of real-name verification requests reaches the business degradation condition, the client will stop sending real-name verification requests to the verification server. By configuring the degradation business type in the configuration file, such as only degrading specific businesses while other businesses are processed normally, the flexibility of business processing is improved. For example, during holidays, only the red envelope receiving business can be degraded, thus ensuring that the resource transfer recipient can receive the transferred red envelopes immediately.

[0134] S610: When the number of real-name verification requests generated by the business side does not meet the business degradation conditions, the client sends a real-name verification request to the verification server.

[0135] The verification server receives the real-name verification request sent by the client in the business server, and then performs the subsequent real-name status verification process.

[0136] In one embodiment, when the degradation function is configured in the configuration file, it can be determined whether the number of real-name verification requests generated by the business side has reached the business degradation condition. If not, a real-name verification request is sent to the verification server.

[0137] In addition, when the degradation function is configured in the configuration file, the client can also determine the business type targeted by the degradation function. When the resource transfer business corresponding to the real-name verification request belongs to the business type, but the number of real-name verification requests does not reach the business degradation condition, a real-name verification request is sent to the verification server.

[0138] In the above embodiments, when it is determined that the target verification server in the verification server is responding abnormally, sending real-name verification requests to the target verification server is stopped. This avoids the problem of being unable to verify the real-name status due to sending real-name verification requests to the abnormal target verification server, thus improving the availability of the verification server. Furthermore, when the number of resource transfer requests is large, resulting in a large number of real-name verification requests, forwarding real-name verification requests to the verification server is stopped. This reduces the service pressure on the verification server, ensuring that previously sent real-name verification requests can be processed normally. Moreover, when the number of real-name verification requests is small, real-name verification requests are sent to the verification server, ensuring that the current real-name verification requests are processed in real time.

[0139] This application also provides an application scenario for receiving red envelopes, which applies the aforementioned method for verifying real-name status. Before describing the method for verifying real-name status, the business side, Client, and Server (corresponding to the verification server in the above embodiments) will be explained first:

[0140] like Figure 7 As shown, the business side can be used to receive red envelopes or transfers. After receiving a red envelope or transfer from the user, it sends an RPC (Remote Procedure Call) request to the client for real-name verification.

[0141] Both the client and the business side are applications for the business server. The following section will focus on introducing the functions of the client, which are as follows:

[0142] (1) Degradation function

[0143] This involves reading a configuration file to determine whether to initiate an RPC request to the server. During peak holiday periods like Chinese New Year, the client reads the published configuration file and, based on that, decides not to initiate an RPC request to the server, thus ensuring the rapid receipt of red envelopes and transfers. The configuration file can be configured with a percentage to control the degradation rate. For example, configuring 50% of transfers or red envelopes to not require real-name verification means that after receiving 50% of transfers or red envelopes, no further RPC requests will be initiated to the server.

[0144] In addition to configuring the degradation ratio, the configuration file can also configure the type of business to be downgraded, such as only downgrading the red envelope business while other businesses (such as transfer business) are processed normally, thus improving flexibility.

[0145] (2) Addressing function

[0146] The client also has addressing capabilities, that is, it can randomly send RPC requests to the server's IP address by reading the server's IP address in the configuration file.

[0147] (3) Load balancing

[0148] The client is responsible for recording the server's response status and the number of responses. If a server has a low response rate, its IP address is removed, thus ensuring that all servers receiving RPC requests are working properly.

[0149] In addition, once the server returns to normal, traffic will be gradually restored proportionally to prevent a cascading failure and improve availability.

[0150] Next, we will introduce the server side. This server side can provide services to the outside world, respond to RPC requests initiated by the client, determine whether the user who receives the red envelope or transfer (i.e., the receiving user) has been real-name authenticated, and then return whether the receiving user is required to perform real-name authentication.

[0151] In addition, the server also has a degradation function, which can be referred to in the client degradation function mentioned above. Moreover, the server also has a traffic routing function, such as deciding whether to initiate an RPC request to the server of a third-party organization (CFT) (corresponding to the authentication server in the above embodiment) based on the actual situation.

[0152] like Figure 8 As shown, the application of this method for verifying real-name status in this application scenario is as follows:

[0153] S1: The business unit sends a query to the client, specifically asking whether the receiving user has completed real-name authentication.

[0154] In this case, whether the user needs to be verified is determined based on whether the receiving user has already completed real-name authentication.

[0155] S2, the client sends an RPC request to the server to inquire whether the receiving user has been verified with their real name.

[0156] S3, the server queries the Redis database for the real-name status information of the receiving user.

[0157] S4. If the Redis records the real-name status information of the receiving user, confirming that the receiving user has been real-name authenticated, the server will send a confirmation message to the client that the receiving user does not need to be real-name authenticated.

[0158] S5: The client returns confirmation information to the business side that the receiving user does not need to be verified with their real name.

[0159] S6, the server obtains the transaction information for this transaction and writes it to MySQL.

[0160] The transaction information includes whether the user has undergone real-name authentication, whether a bank card has been linked, whether real-name authentication is required for the receiving user, and the type and parameters of the RPC request.

[0161] S7. If the real-name status information of the receiving user is not recorded in Redis, it is determined that the receiving user has not been real-name authenticated. The server sends an RPC request to the CFT server to inquire whether the receiving user has been real-name authenticated, thereby determining whether the receiving user needs to be real-name authenticated for receiving a red envelope or transfer this time.

[0162] S8. If the CFT server reports that the recipient has been verified with their real name, the server writes the verified real name status information of the recipient to the Redis database, indicating that the recipient has been verified with their real name.

[0163] S9, the server sends a confirmation message to the client that the recipient does not need to undergo real-name authentication this time.

[0164] S10, the server writes the transaction information to MySQL.

[0165] S11, the client returns a confirmation message to the business side indicating that no real-name authentication is required.

[0166] S12, the business side completes the accounting operation.

[0167] S13, if the CFT server reports that the payee has not been verified with their real name, the server will send feedback to the client that the payee needs to be verified with their real name.

[0168] S14, the server writes the transaction information to MySQL.

[0169] S15, the client returns feedback information to the business side that the receiving user needs to undergo real-name authentication.

[0170] In the steps described above, a traffic splitting operation was implemented by introducing a Redis database. Specifically, if the real-name authentication information of the receiving user is stored in the Redis database, the server no longer sends RPC requests to the CFT server. This offloading of RPC request traffic reduces the computational load on the CFT server and improves system availability. Simultaneously, the extremely fast read and write speed of the Redis database reduces background processing time.

[0171] Furthermore, as can be seen from the above process, MySQL records the transaction information of each receiving user, including whether the user has been real-name authenticated. This transaction information can be reconciled with the user's real-name authentication information on the CFT side to find the violating user. Then, the request of the violating user to receive red envelopes can be intercepted, and the user can be required to re-authenticate.

[0172] The above embodiments can achieve the following technical effects:

[0173] 1) By introducing configuration files on the client side, the degradation strategy can be flexibly controlled;

[0174] 2) Clients improve system availability through load balancing;

[0175] 3) The server introduces a Redis database to reduce the computational pressure on the CFT side by offloading data, thereby improving system availability and reducing backend processing time.

[0176] 4) By reconciling accounts, we can prevent the emergence of non-compliant users and further improve the compliance rate.

[0177] It should be understood that, although Figure 2 , 4 The steps in flowcharts 5, 6, and 8 are shown sequentially as indicated by the arrows; however, these steps are not necessarily executed in the exact order indicated by the arrows. Unless explicitly stated herein, there is no strict order requirement for the execution of these steps, and they can be performed in other orders. Furthermore, Figure 2 , 4 At least some of the steps in 5, 6, and 8 may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but may be executed at different times. The execution order of these steps or stages is not necessarily sequential, but may be executed in turn or alternately with other steps or at least some of the steps or stages in other steps.

[0178] In one embodiment, such as Figure 9As shown, a device for verifying real-name status is provided. This device can be a software module, a hardware module, or a combination of both integrated into a server. Specifically, the device includes: a receiving module 902, a searching module 904, a verification module 906, and a sending module 908, wherein:

[0179] The receiving module 902 is used to receive the real-name verification request generated based on the resource transfer request sent by the business server;

[0180] The lookup module 904 is used to look up the real-name status information of the resource transferee in the in-memory database based on the real-name verification request.

[0181] The verification module 906 is used to forward a real-name verification request to the authentication server if the real-name status information of the resource transferee is not found, and when the authentication server determines that the resource transferee has not been real-name authenticated, it collects the real-name authentication information of the resource transferee and stores the real-name status information generated based on the real-name authentication information in the memory database.

[0182] The sending module 908 is used to return a confirmation message of real-name authentication to the business server if the real-name status information of the resource transferee is found, so that the business server can transfer the resource specified in the resource transfer request.

[0183] In one embodiment, the verification module 906 is further configured to send first feedback information to the business server to prompt real-name authentication when the authentication server determines that the resource transferee has not been real-name authenticated, so that the business server initiates a real-name authentication request to the terminal of the resource transferee to collect the real-name authentication information of the resource transferee; and receive the real-name authentication information for the resource transferee from the business server.

[0184] In one embodiment, such as Figure 10 As shown, the device also includes:

[0185] The first storage module 910 is used to store the real-name authentication confirmation information as transaction information in a relational database if the real-name status information of the resource transferee is found; if the real-name status information of the resource transferee is not found and the business server initiates a real-name authentication request to the terminal of the resource transferee, the real-name authentication request is stored as transaction information in a relational database.

[0186] In the above embodiments, upon receiving a real-name verification request generated based on a resource transfer request, the system first searches for the real-name status information of the resource transferee in the memory database. Only when the real-name status information of the resource transferee is not found, i.e., it is uncertain whether the resource transferee has performed real-name authentication, will the real-name verification request be forwarded to the authentication server to request the authentication server to perform verification. This greatly reduces the amount of interaction between the verification server and the authentication server, improves the efficiency of real-name status verification, and also improves the efficiency of resource transfer. Furthermore, if the real-name status information of the resource transferee is found, it indicates that the resource transferee has performed real-name authentication. At this time, a confirmation message of real-name authentication is directly returned to the business server, allowing the business server to transfer the resource specified in the resource transfer request without interacting with the authentication server, thus improving the efficiency of resource transfer.

[0187] In one embodiment, such as Figure 10 As shown, the device also includes:

[0188] The first acquisition module 912 is used to acquire the real-name authentication information of all resource transferors who received resource transfer requests within a specified time period on the authentication server when the preset reconciliation time is reached or a reconciliation instruction is received; and to read the transaction information of all resource transferors from the relational database.

[0189] The comparison module 914 is used to compare the read transaction information with the real-name status information in order to find the target resource transfer party that has not performed real-name authentication on the authentication server but has not initiated a real-name authentication request to request real-name authentication.

[0190] The sending module 908 is also used to send a second feedback message to the business server; the second feedback message is used to instruct the business server to initiate a real-name authentication request in order to collect the real-name authentication information of the target resource transferee.

[0191] In one embodiment, the second feedback information is further used to instruct the business server to intercept the resource transfer operation corresponding to the resource transfer request when the business server receives a resource transfer request from the target resource transferee.

[0192] In the above embodiments, by comparing the transaction log information of the resource transferor in the relational database with the real-name status information of the resource transferor on the authentication server, it is possible to find target resource transferors who have not performed real-name authentication on the authentication server and have not initiated a real-name authentication request to request real-name authentication. The transaction log information of the target resource transferor in the relational database has problems, and a real-name authentication request should be initiated to the target resource transferor to ensure that the target resource transferor performs real-name authentication before receiving resources, thereby improving the security of resource transfer.

[0193] In one embodiment, such as Figure 10 As shown, the device also includes:

[0194] The second acquisition module 916 is used to obtain the real-name authentication information of the real-name authenticated party from the authentication server when the authentication server determines that the resource transferee has been real-name authenticated.

[0195] The second storage module 918 is used to generate real-name status information based on real-name authentication information and store it in an in-memory database.

[0196] In one embodiment, the receiving module 902 is further configured to receive a real-name verification request sent by a client in the business server; wherein the real-name verification request is a remote procedure call request generated by the business end in the business server based on a resource transfer request for requesting real-name verification.

[0197] In one embodiment, the client in the business server is configured to send a real-name verification request when the number of real-name verification requests generated by the business side does not reach the business degradation condition; and to stop sending real-name verification requests when the number of real-name verification requests generated by the business side reaches the business degradation condition.

[0198] In the above embodiments, when it is determined that the target verification server in the verification server is responding abnormally, sending real-name verification requests to the target verification server is stopped. This avoids the problem of being unable to verify the real-name status due to sending real-name verification requests to the abnormal target verification server, thus improving the availability of the verification server. Furthermore, when the number of resource transfer requests is large, resulting in a large number of real-name verification requests, forwarding real-name verification requests to the verification server is stopped. This reduces the service pressure on the verification server, ensuring that previously sent real-name verification requests can be processed normally. Moreover, when the number of real-name verification requests is small, real-name verification requests are sent to the verification server, ensuring that the current real-name verification requests are processed in real time.

[0199] For specific limitations regarding the device for verifying real-name status, please refer to the limitations on the method for verifying real-name status above, which will not be repeated here. Each module in the aforementioned device for verifying real-name status can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of the server in hardware form or independently of it, or stored in the memory of the server in software form, so that the processor can call and execute the operations corresponding to each module.

[0200] In one embodiment, a system for verifying real-name status is provided, such as Figure 1 As shown, the system includes:

[0201] Business server 104 is used to generate a real-name verification request based on the resource transfer request and send the real-name verification request to verification server 106.

[0202] Verification server 106 is used to receive real-name verification requests sent by business server 104; in the memory database, it searches for the real-name status information of the resource transferee according to the real-name verification request; if the real-name status information of the resource transferee is not found, it forwards the real-name verification request to authentication server 108.

[0203] The authentication server 108 is used to send a confirmation message of non-real-name authentication to the verification server 106 when it determines that the resource transferee has not been real-name authenticated.

[0204] The verification server 106 is also used to collect the real-name authentication information of the resource transferee and store the real-name status information generated based on the real-name authentication information in the memory database; if the real-name status information of the resource transferee is found, the server returns the confirmation information that the real-name authentication has been completed to the business server 104.

[0205] Business server 104 is also used to transfer the resource specified in the transfer request.

[0206] In one embodiment, the verification server 106 includes a server; the server is configured to send a first feedback message to the business server 104 to prompt real-name authentication when the authentication server 108 determines that the resource transferee has not been real-name authenticated, so that the business server 104 initiates a real-name authentication request to collect the real-name authentication information of the resource transferee; and to receive the real-name authentication information for the resource transferee from the business server 104.

[0207] In one embodiment, the server is further configured to, if the real-name status information of the resource transferee is found, store the confirmed real-name authentication information as transaction information in a relational database; if the real-name status information of the resource transferee is not found, and the business server 104 collects the real-name authentication information, store the real-name authentication request as transaction information in a relational database.

[0208] In one embodiment, the server is further configured to, when a preset reconciliation time is reached or a reconciliation instruction is received, obtain the real-name status information of all resource transferors who received resource transfer requests within a specified time period on the authentication server 108; read the transaction information of all resource transferors from the relational database; compare the read transaction information with the real-name status information to find the target resource transferor that has not performed real-name authentication on the authentication server 108 but has not initiated a real-name authentication request to request real-name authentication; and send a second feedback message to the business server 104.

[0209] Business server 104 is used to initiate a real-name authentication request when it receives the second feedback information in order to collect the real-name authentication information of the target resource transferee.

[0210] In one embodiment, when the business server 104 receives a resource transfer request from the target resource transferee, it intercepts the resource transfer operation corresponding to the resource transfer request.

[0211] In one embodiment, the service server 104 includes a service side and a client side;

[0212] On the business side, it is used to generate a real-name verification request based on the resource transfer request; the real-name verification request is a remote procedure call request used to request real-name verification.

[0213] The client is used to send a real-name verification request to the verification server 106.

[0214] In one embodiment, the client is also configured to forward remote procedure call requests to the verification server 106 when the number of real-name verification requests generated by the business side does not meet the business degradation condition.

[0215] The client is also used to stop forwarding remote procedure call requests to the verification server 106 when the number of real-name verification requests generated by the business reaches the business degradation condition.

[0216] In one embodiment, the client is further configured to, after sending a remote procedure call request to the verification server 106, collect statistics on the response information of the verification server 106 to the remote procedure call request; and when it is determined from the response information that the response rate of the verification server 106 is lower than a preset response rate, stop sending remote procedure call requests to the verification server 106.

[0217] In one embodiment, a server is provided, the internal structure of which can be shown as follows: Figure 11 As shown, the server includes a processor, memory, and a network interface connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The server's database stores real-name status information. The server's network interface is used to communicate with external terminals via a network connection. When the computer program is executed by the processor, it implements a method for verifying real-name status.

[0218] Those skilled in the art will understand that Figure 11The structure shown is merely a block diagram of a portion of the structure related to the solution of this application and does not constitute a limitation on the server to which the solution of this application is applied. A specific server may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0219] In one embodiment, a server is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above method embodiments.

[0220] In one embodiment, a computer-readable storage medium is provided storing a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0221] In one embodiment, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A server's processor reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the server to perform the steps described in the method embodiments above.

[0222] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the methods described above. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, or optical storage, etc. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc.

[0223] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0224] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the invention patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims

1. A method for verifying real-name status, characterized in that, The method is applied to a verification server, and the method includes: The system receives a real-name verification request generated based on a resource transfer request from a business server. The real-name verification request is sent when the number of resource transfer requests received by the business server has not reached a preset threshold. If the number of resource transfer requests received by the business server reaches the preset threshold, the resource specified in the resource transfer request is transferred. The resource transfer request includes a red envelope receiving request. In the in-memory database, the real-name status information of the resource transferee is retrieved based on the real-name verification request; If the real-name status information of the resource transferee is not found, the real-name verification request is forwarded to the authentication server. When the authentication server determines that the resource transferee has not been real-name authenticated, the real-name authentication information of the resource transferee is collected through the terminal of the resource transferee, and the real-name status information is generated based on the real-name authentication information. The generated real-name status information is stored in the memory database. If the real-name status information of the resource transferee is found, a confirmation message indicating that the real-name authentication has been completed is returned to the business server, so that the business server can transfer the resource specified in the resource transfer request.

2. The method according to claim 1, characterized in that, When the authentication server determines that the resource transferor has not undergone real-name authentication, collecting the real-name authentication information of the resource transferor through the resource transferor's terminal includes: When the authentication server determines that the resource transferee has not been real-name authenticated, it sends a first feedback message to the business server to prompt the resource transferee to perform real-name authentication, so that the business server initiates a real-name authentication request to the terminal of the resource transferee in order to collect the real-name authentication information of the resource transferee. Receive real-name authentication information for the resource transfer recipient from the business server.

3. The method according to claim 2, characterized in that, The method further includes: If the real-name status information of the resource transferee is found, the confirmed real-name authentication information is stored as transaction information in a relational database. If the real-name status information of the resource transferee is not found, and the business server initiates a real-name authentication request to the terminal of the resource transferee, the real-name authentication request is stored as transaction information in the relational database.

4. The method according to claim 3, characterized in that, The method further includes: When the preset reconciliation time is reached, or when a reconciliation instruction is received, the real-name authentication information of all resource transferors who received resource transfer requests within the specified time period on the authentication server is obtained. Read the transaction log information of all resource recipients from the relational database; The read transaction information is compared with the real-name status information to identify the target resource transfer party that has not performed real-name authentication on the authentication server but has not initiated the real-name authentication request to request real-name authentication. Send a second feedback message to the business server; the second feedback message is used to instruct the business server to initiate a real-name authentication request in order to collect the real-name authentication information of the target resource transferee.

5. The method according to claim 4, characterized in that, The second feedback information is also used to instruct the business server to intercept the resource transfer operation corresponding to the resource transfer request when the business server receives a resource transfer request from the target resource transferee.

6. The method according to claim 1, characterized in that, The method further includes: When the authentication server determines that the resource transferee has been real-name authenticated, it obtains the real-name authentication information from the authentication server. Real-name status information is generated based on the real-name authentication information and stored in the memory database.

7. The method according to claim 1, characterized in that, The real-name verification request generated based on the resource transfer request sent by the receiving service server includes: Receive real-name verification requests sent by clients in the business server; The real-name verification request is a remote procedure call request generated by the business side in the business server based on the resource transfer request, which is used to request real-name verification.

8. The method according to claim 7, characterized in that, The client in the business server is configured to send the real-name verification request when the number of real-name verification requests generated by the business terminal does not reach the business degradation condition; and to stop sending the real-name verification request when the number of real-name verification requests generated by the business terminal reaches the business degradation condition.

9. The method according to any one of claims 1 to 8, characterized in that, The method is applied to at least two verification servers; the client in the business server is used to stop sending the real-name verification request to the target verification server when it is determined that the target verification server responds abnormally among the at least two verification servers.

10. A device for verifying real-name status, characterized in that, The device is used in a verification server, and the device includes: The receiving module is used to receive a real-name verification request generated based on a resource transfer request sent by the business server. The real-name verification request is sent when the number of resource transfer requests received by the business server has not reached a preset threshold. If the number of resource transfer requests received by the business server reaches the preset threshold, the resource specified in the resource transfer request is transferred. The resource transfer request includes a red envelope receiving request. The lookup module is used to search the real-name status information of the resource transferee in the in-memory database based on the real-name verification request. The verification module is used to forward the real-name verification request to the authentication server if the real-name status information of the resource transferee is not found, and when the authentication server determines that the resource transferee has not been real-name authenticated, it collects the real-name authentication information of the resource transferee through the terminal of the resource transferee, generates the real-name status information based on the real-name authentication information, and stores the generated real-name status information in the memory database. The sending module is used to return a confirmation message indicating that the resource transferee has been verified to the business server if the real-name status information of the resource transferee is found, so that the business server can transfer the resource specified in the resource transfer request.

11. The apparatus according to claim 10, characterized in that, The verification module is further configured to, when the authentication server determines that the resource transferee has not performed real-name authentication, send a first feedback message to the business server to prompt for real-name authentication, so that the business server initiates a real-name authentication request to the terminal of the resource transferee to collect the real-name authentication information of the resource transferee; and receive the real-name authentication information for the resource transferee from the business server.

12. The apparatus according to claim 11, characterized in that, The device further includes: The first storage module is used to store the verified information as transaction information in a relational database if the real-name status information of the resource transferee is found; if the real-name status information of the resource transferee is not found and the business server initiates a real-name authentication request to the terminal of the resource transferee, the real-name authentication request is stored as transaction information in the relational database.

13. The apparatus according to claim 12, characterized in that, The device further includes: The first acquisition module is used to acquire the real-name authentication information of all resource transferors who received resource transfer requests within a specified time period on the authentication server when a preset reconciliation time is reached or a reconciliation instruction is received; and to read the transaction information of all resource transferors from the relational database. The comparison module is used to compare the read transaction information with the real-name status information to find the target resource transfer party that has not performed real-name authentication on the authentication server but has not initiated the real-name authentication request to request real-name authentication. The sending module is further configured to send a second feedback message to the business server; the second feedback message is configured to instruct the business server to initiate a real-name authentication request in order to collect the real-name authentication information of the target resource transferee.

14. The apparatus according to claim 13, characterized in that, The second feedback information is also used to instruct the business server to intercept the resource transfer operation corresponding to the resource transfer request when the business server receives a resource transfer request from the target resource transferee.

15. The apparatus according to claim 10, characterized in that, The device further includes: The second acquisition module is used to acquire real-name authentication information from the authentication server when the authentication server determines that the resource transferee has been real-name authenticated. The second storage module is used to generate real-name status information based on the real-name authentication information and store it in the memory database.

16. The apparatus according to claim 10, characterized in that, The receiving module is further configured to receive a real-name verification request sent by a client in the business server; wherein the real-name verification request is a remote procedure call request generated by the business terminal in the business server based on the resource transfer request for requesting real-name verification.

17. The apparatus according to claim 16, characterized in that, The client in the business server is configured to send the real-name verification request when the number of real-name verification requests generated by the business terminal does not reach the business degradation condition; and to stop sending the real-name verification request when the number of real-name verification requests generated by the business terminal reaches the business degradation condition.

18. The apparatus according to any one of claims 10 to 17, characterized in that, The device is applied to at least two verification servers; the client in the business server is used to stop sending the real-name verification request to the target verification server when it is determined that the target verification server responds abnormally among the at least two verification servers.

19. A system for verifying real-name status, characterized in that, The system includes: A business server is used to generate a real-name verification request based on a resource transfer request and send the real-name verification request to a verification server. The real-name verification request is sent when the number of resource transfer requests received by the business server has not reached a preset threshold. If the number of resource transfer requests received by the business server reaches the preset threshold, the resource specified in the resource transfer request is transferred. The resource transfer request includes a red envelope receiving request. The verification server is configured to receive the real-name verification request sent by the business server; search for the real-name status information of the resource transferee in the memory database according to the real-name verification request; if the real-name status information of the resource transferee is not found, forward the real-name verification request to the authentication server. The authentication server is used to send a confirmation message of non-real-name authentication to the verification server when it determines that the resource transferor has not been real-name authenticated. The verification server is also used to collect the real-name authentication information of the resource transferee through the resource transferee's terminal, generate the real-name status information based on the real-name authentication information, and store the generated real-name status information in the memory database; if the real-name status information of the resource transferee is found, return the real-name authentication confirmation information to the business server. The business server is also used to transfer the resource specified in the resource transfer request.

20. The system according to claim 19, characterized in that, The business server includes a business side and a client side; The business unit is used to generate the real-name verification request based on the resource transfer request; the real-name verification request is a remote procedure call request used to request real-name verification. The client is used to send the real-name verification request to the verification server.

21. The system according to claim 20, characterized in that, The client is also configured to forward the remote procedure call request to the verification server when the number of real-name verification requests generated by the business terminal does not meet the business degradation condition; The client is also configured to stop forwarding the remote procedure call request to the verification server when the number of real-name verification requests generated by the business terminal reaches the business degradation condition.

22. The system according to claim 19, characterized in that, The verification server includes a server-side component. The server is configured to send a first feedback message to the business server to prompt real-name authentication when the authentication server determines that the resource transferee has not been real-name authenticated, so that the business server initiates a real-name authentication request to the terminal of the resource transferee to collect the real-name authentication information of the resource transferee; and to receive the real-name authentication information for the resource transferee from the business server.

23. The system according to claim 22, characterized in that, The server is further configured to, if the real-name status information of the resource transferee is found, store the confirmed real-name authentication information as transaction information in a relational database; if the real-name status information of the resource transferee is not found, and the business server initiates a real-name authentication request to the terminal of the resource transferee, store the real-name authentication request as transaction information in the relational database.

24. The system according to claim 23, characterized in that, The server is also used to obtain the real-name authentication information of all resource transferors who received resource transfer requests within a specified period on the authentication server when a preset reconciliation time is reached or a reconciliation instruction is received. Read the transaction log information of all resource recipients from the relational database; The read transaction information is compared with the real-name status information to identify the target resource transfer party that has not performed real-name authentication on the authentication server but has not initiated the real-name authentication request to request real-name authentication. Send a second feedback message to the service server; The business server is used to initiate a real-name authentication request when it receives the second feedback information, so as to collect the real-name authentication information of the target resource transferee.

25. The system according to claim 24, characterized in that, The business server is used to intercept the resource transfer operation corresponding to the resource transfer request when it receives a resource transfer request from the target resource transferee.

26. The system according to claim 19, characterized in that, The client in the business server is also used to collect statistics on the response information of the verification server to the remote procedure call request after sending the remote procedure call request to the verification server; when it is determined from the response information that the response rate of the verification server is lower than a preset response rate, the client stops sending remote procedure call requests to the verification server.

27. The system according to claim 26, characterized in that, The client in the business server is used to stop sending the real-name verification request to the target verification server when it is determined that the target verification server responds abnormally among at least two verification servers.

28. A verification server, comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 9.

29. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 9.

30. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 9.

Images