Application account processing method and apparatus

Abstract

Embodiments of the present specification provide an application account processing method and device, wherein an application account processing method comprises: receiving an account processing request submitted by a user terminal of an auxiliary user for a target user; in response to the account processing request, checking whether the auxiliary user meets a processing condition of performing account restriction processing on an application account of the target user; if yes, calculating an intimacy between the auxiliary user and the target user based on application interaction records of the auxiliary user and the target user, and determining a verification mode corresponding to the intimacy; and performing identity verification of the target user according to identity information of the target user collected by the user terminal in the verification mode, and performing account restriction processing on the application account after the identity verification passes.

Description

Technical Field

[0001] This document relates to the field of data processing technology, and in particular to an application account processing method and apparatus. Background Technology

[0002] With the development and advancement of the internet and information technology, smart terminals are changing rapidly. Their constantly updated functions and convenience have led to their gradual integration into all aspects of users' lives, making them necessities for modern life and work. However, due to the increased usability of smart terminals, their security has also become a major concern, especially given that many applications installed on smart terminals often involve issues of user privacy and financial security. Summary of the Invention

[0003] This specification provides one or more embodiments of an application account processing method. The application account processing method, applied to a server, includes: receiving an account processing request for a target user submitted by a user terminal of an auxiliary user; in response to the account processing request, verifying whether the auxiliary user meets the processing conditions for account restriction processing of the target user's application account; if so, calculating the intimacy level between the auxiliary user and the target user based on the application interaction records between the auxiliary user and the target user, and determining a verification method corresponding to the intimacy level; verifying the target user's identity based on the identity information of the target user collected by the user terminal according to the verification method, and performing account restriction processing on the application account after successful verification.

[0004] This specification provides one or more embodiments of another application account processing method applied to a user terminal, comprising: submitting an account processing request for the target user to a server according to an account processing instruction submitted for the target user; if the server determines that the identity verification method is an identifier input verification method, collecting identifier keywords input by the target user; submitting the identifier keywords as identity information to the server to verify the identity of the target user, and, upon successful verification, imposing account restrictions on the target user's application account.

[0005] This specification provides one or more embodiments of an application account processing apparatus, running on a server, comprising: a request receiving module configured to receive an account processing request for a target user submitted by a user terminal of an auxiliary user; a condition verification module configured to, in response to the account processing request, verify whether the auxiliary user meets the processing conditions for account restriction processing of the target user's application account; if so, run a verification method determination module, the verification method determination module being configured to calculate the intimacy between the auxiliary user and the target user based on the application interaction records between the auxiliary user and the target user, and determine the verification method corresponding to the intimacy; and an account restriction processing module configured to verify the identity of the target user based on the identity information of the target user collected by the user terminal according to the verification method, and to perform account restriction processing on the application account after the verification is passed.

[0006] This specification provides one or more embodiments of another application account processing device, running on a user terminal, including: a request submission module configured to submit an account processing request for a target user to a server based on an account processing instruction submitted for the target user. If the server determines that the identity verification method is an identifier input verification method, a keyword collection module is run, configured to collect identifier keywords input by the target user. An identity information submission module is configured to submit the identifier keywords as identity information to the server to verify the identity of the target user and, upon successful verification, to restrict the application account of the target user.

[0007] This specification provides one or more embodiments of an application account processing device, including: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: receive an account processing request for a target user submitted by a user terminal of an auxiliary user; in response to the account processing request, verify whether the auxiliary user meets the processing conditions for account restriction processing of the target user's application account; if so, calculate the intimacy between the auxiliary user and the target user based on the application interaction records between the auxiliary user and the target user, and determine a verification method corresponding to the intimacy; verify the identity of the target user according to the identity information of the target user collected by the user terminal according to the verification method, and perform account restriction processing on the application account after the verification is passed.

[0008] This specification provides one or more embodiments of another application account processing device, including: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: submit an account processing request for a target user to a server according to an account processing instruction submitted for a target user; if the server determines that the verification method for identity verification is an identifier input verification method, collect identifier keywords input by the target user; submit the identifier keywords as identity information to the server to verify the identity of the target user and, upon successful verification, restrict the application account of the target user.

[0009] This specification provides one or more embodiments of a storage medium for storing computer-executable instructions, which, when executed by a processor, implement the following process: receiving an account processing request for a target user submitted by a user terminal of an auxiliary user; in response to the account processing request, verifying whether the auxiliary user meets the processing conditions for account restriction processing of the target user's application account; if so, calculating the intimacy between the auxiliary user and the target user based on the application interaction records between the auxiliary user and the target user, and determining the verification method corresponding to the intimacy; verifying the identity of the target user according to the identity information collected by the user terminal according to the verification method, and performing account restriction processing on the application account after the verification is passed.

[0010] This specification provides one or more embodiments of another storage medium for storing computer-executable instructions that, when executed by a processor, implement the following process: Submitting an account processing request for a target user to a server based on an account processing instruction submitted for that target user; If the server determines that the identity verification method is an identifier input verification method, collecting identifier keywords input by the target user; Submitting the identifier keywords as identity information to the server to verify the target user's identity and, upon successful verification, imposing account restrictions on the target user's application account. Attached Figure Description

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

[0012] Figure 1A flowchart illustrating an application account processing method provided in one or more embodiments of this specification;

[0013] Figure 2 A schematic diagram of a processing reminder page provided for one or more embodiments of this specification;

[0014] Figure 3 A schematic diagram of a user selection page provided for one or more embodiments of this specification;

[0015] Figure 4 A first type of function diagram provided for one or more embodiments of this specification;

[0016] Figure 5 A second function diagram provided for one or more embodiments of this specification;

[0017] Figure 6 A schematic diagram of a keyword collection page provided for one or more embodiments of this specification;

[0018] Figure 7 A schematic diagram of a feature acquisition page provided for one or more embodiments of this specification;

[0019] Figure 8 A schematic diagram of an account restriction reminder page provided for one or more embodiments of this specification;

[0020] Figure 9 A schematic diagram of a face image acquisition page provided for one or more embodiments of this specification;

[0021] Figure 10 A schematic diagram of a restriction removal page provided for one or more embodiments of this specification;

[0022] Figure 11 This specification provides a flowchart of an application account processing method for an account loss reporting scenario, which is provided in one or more embodiments of this specification.

[0023] Figure 12 This specification provides a flowchart of an application account processing method for an auxiliary loss reporting scenario, as provided in one or more embodiments.

[0024] Figure 13 A flowchart illustrating another application account processing method provided in one or more embodiments of this specification;

[0025] Figure 14 A schematic diagram of an application account processing device provided for one or more embodiments of this specification;

[0026] Figure 15A schematic diagram of another application account processing device provided for one or more embodiments of this specification;

[0027] Figure 16 A schematic diagram of the structure of an application account processing device provided for one or more embodiments of this specification;

[0028] Figure 17 This is a schematic diagram of the structure of another application account processing device provided in one or more embodiments of this specification. Detailed Implementation

[0029] To enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this specification, and not all of the embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the protection scope of this document.

[0030] This specification provides an example of an application account processing method:

[0031] Reference Figure 1 The application account processing method provided in this embodiment is applied to a server and specifically includes steps S102 to S108.

[0032] Step S102: Receive an account processing request for the target user submitted by the user terminal of the auxiliary user.

[0033] The application account processing method provided in this embodiment involves an auxiliary user's user terminal initiating an account processing request to process the application account of a target user. In response to the request, upon receiving it, the auxiliary user's permission to restrict the application account of the target user is first determined. If the auxiliary user has this permission, the verification method for verifying the auxiliary user's identity in this account processing request is determined by calculating the intimacy level between the auxiliary user and the target user. The target user's identity information is collected according to the determined verification method, and after successful verification of the collected identity information, the application account of the target user is restricted. This method enables account restriction of the target user's application account initiated by the auxiliary user. Furthermore, different verification methods are used to collect the target user's identity information for different intimacy levels, thereby improving the efficiency of the auxiliary restriction process.

[0034] In practical applications, the loss of a target user's smart device or application account poses a significant security risk. Therefore, to protect the target user's privacy information under the application account in the event of a lost device or application account, a user associated with the target user can freeze the application account, i.e., report it lost.

[0035] In this embodiment, the auxiliary user refers to a user who assists the target user in reporting the loss of their account when needed. This includes associated users who are related to the target user. Furthermore, if the target user has multiple user terminals, and one user terminal is lost, the target user can use other user terminals to perform account restriction processing. Therefore, the auxiliary user can also be the target user themselves. The account processing request includes a request submitted by the auxiliary user through a user terminal to report the loss of the target user's application account.

[0036] In practice, when a user learns that a target user with whom they have a close relationship (family or friends, or frequent interactions) has lost their device or account, they can access the account processing service through their device and select the target user for whom account restrictions need to be imposed.

[0037] To improve the efficiency of assistive users in selecting target users during access to account processing services, and to avoid excessively long account restriction processing times due to assistive users' inability to find or remember the target user's user identifier within a short period, which could further compromise the security of data within the target user's application account, this embodiment provides an optional implementation where a recommended list is displayed to the assistive user when accessing the account processing service; the recommended user list is determined in the following manner:

[0038] Obtain the access request for account processing service submitted by the user terminal;

[0039] Based on the access request, a list of recommended users is determined and sent to the user terminal so that the user terminal can display the list of recommended users.

[0040] Specifically, when the auxiliary user's user terminal receives the auxiliary user's access instruction for account processing services, it submits an access request to the server based on the access instruction. After receiving the access request, the server determines the recommended users to recommend to the auxiliary user and generates a recommended user list containing the recommended users, which is then sent to the auxiliary user's user terminal. After receiving the recommended user list, the auxiliary user's user terminal renders and displays the user selection page based on the recommended user list.

[0041] Assistant users can select recommended users from the recommended user list on the user selection page as target users and then submit an account processing request. Alternatively, they can enter the user identifier (name, application account identifier, email, or contact information) of the target user on the user selection page to search for users, identify the searched users as target users, and then submit an account processing request.

[0042] like Figure 2 As shown, after the assisted user accesses the account processing service, the assisted user's user terminal displays the following to the assisted user: Figure 2 The processing reminder page shown indicates that if an auxiliary user triggers the process... Figure 2 After configuring the "Select User" control, the user terminal submits an access request to the server. Based on the access request, the server determines the recommended users for the auxiliary user and generates a recommended user list, which is then sent to the user terminal. After receiving the recommended user list, the user terminal generates a list as shown below. Figure 3 The user selection page is shown and displayed. The auxiliary user can select a target user from the recommended user list, and can also enter the target user's contact information or name to search for users. Furthermore, the auxiliary user can view the application friend list within the auxiliary user application through trigger control 301, and select a target user through the application friend list; however, this embodiment does not limit this further.

[0043] It should be noted that in the process of determining the recommended users for the auxiliary user, the frequency of application interaction or the degree of intimacy between the auxiliary user and each application friend in the application friend list can be sorted in descending order to obtain the friend sequence, and the application friends in the friend sequence can be read as recommended users according to a preset number; in addition, other parameters can also be used to determine the recommended users among the application friends, which can be set according to the actual scenario, and this embodiment does not limit it here.

[0044] After the assistant user selects or enters the target user through the user selection page, the assistant user submits an account processing instruction for the target user. After receiving the account processing instruction, the assistant user's user terminal submits an account processing request for the target user to the server based on the account processing instruction submitted by the assistant user for the target user, so that the server can perform account restriction processing on the target user's application account based on the account processing request.

[0045] Step S104: In response to the account processing request, verify whether the auxiliary user meets the processing conditions for account restriction processing of the target user's application account.

[0046] The account restriction processing includes freezing the application account of the target user or reporting the account lost.

[0047] To prevent auxiliary users from unjustifiably restricting the target user's application account, upon receiving an account processing request from the auxiliary user's user terminal, the system verifies the auxiliary user's permission to restrict the target user's application account. This verifies whether the auxiliary user possesses the necessary permissions to restrict the target user's application account, or whether the auxiliary user meets the processing conditions for doing so. These conditions include: the auxiliary user's total number of lost / stolen reports within a preset time interval not exceeding a first number of lost / stolen reports; the auxiliary user's number of lost / stolen reports against the target user within a single time interval not exceeding a second number of lost / stolen reports; and / or, the auxiliary user's historical lost / stolen records against the target user containing records marked as abnormal behavior by the target user.

[0048] In specific implementation, to enhance the credibility of the auxiliary user's assisted account reporting for the target user and to prevent the auxiliary user from making abnormal account reportings (i.e., reporting the target user's application account not when the target user needs it), after receiving the account processing request submitted by the auxiliary user for the target user's application account, the auxiliary user's permission to restrict the target user's application account is verified. This involves checking whether the auxiliary user meets the processing conditions for account permission processing of the target user's application account. In one optional implementation of this embodiment, the following method is used to verify whether the auxiliary user meets the processing conditions for restricting the target user's application account:

[0049] Query the total number of times the auxiliary user reported a loss within a preset time interval in the loss report record table;

[0050] If the total number of reported losses is less than the first number of reported losses, then the historical reported loss records of the auxiliary user for the target user are read from the reported loss record table;

[0051] Calculate the number of times the auxiliary user reported the target user's account loss within the time interval corresponding to the account processing request in the historical loss reporting records; the number of user loss reporting times includes the number of times the auxiliary user reported the target user's account loss in the historical loss reporting records.

[0052] If the number of times the user reports a loss is less than the second number of times the user reports a loss, then the auxiliary user is determined to meet the processing conditions.

[0053] To further enhance the credibility of the assisted user's assistance in reporting the loss of the target user, in an optional implementation of this embodiment, if it is determined that the number of times the assisted user reports the loss of the target user within the time interval corresponding to the account processing request does not exceed the second number of reports, the following operation is also performed to determine whether the assisted user meets the processing conditions:

[0054] Read the loss reporting behavior marker from the historical loss reporting records;

[0055] If there are any historical loss reporting records marked as abnormal, then it is determined that the auxiliary user does not meet the processing conditions.

[0056] Specifically, the fatigue level of the auxiliary user is judged by setting a preset time interval, a first number of loss reports, a loss report time interval, and a second number of loss reports. After obtaining the auxiliary user's account processing request for the target user, the fatigue level of the auxiliary user is judged based on the loss report record table. That is, the total number of loss reports by the auxiliary user within the preset time interval is queried in the loss report record table, and it is checked whether the total number of loss reports is less than the first number of loss reports. If so, the historical loss report records of the auxiliary user for the target user are read in the loss report record table, and based on the historical loss report records, it is determined whether the number of loss reports by the auxiliary user for the target user within the loss report time interval corresponding to the account processing request exceeds the second number of loss reports.

[0057] In other words, after obtaining the target user's application account identifier carried in the auxiliary user's account processing request to the target user, a two-dimensional fatigue assessment is performed: one is that the auxiliary user can only assist in reporting the loss a certain number of times within a preset time interval; the other is that the auxiliary user can only assist in reporting the loss a certain number of times to the target user within the corresponding time interval. If the fatigue assessment passes, it can be determined that the auxiliary user meets the processing conditions.

[0058] For example, if a pre-set time interval M1 = 30 days, the first number of loss reports N1 = 2, the corresponding time interval M2 = 1 day, and the second number of loss reports N2 = 1, after receiving a request from the auxiliary user to report the loss of an associated user's account, the system reads the loss report record table and queries the auxiliary user's total number of loss reports within 30 days. If the total number of loss reports is 2 or greater, the fatigue assessment fails, and a verification failure notification is sent to the auxiliary user's user terminal. If the total number of loss reports is less than 2, the system further determines whether the auxiliary user has reported the loss of an associated user within 1 day. If yes, the fatigue assessment fails, and a verification failure notification is sent to the auxiliary user's user terminal. If no, the fatigue assessment passes.

[0059] If the fatigue level assessment passes, in order to prevent the auxiliary user from maliciously reporting the target user's account as lost and to enhance the protection of the target user's application account, the effectiveness of the auxiliary user's account restriction processing is further verified. After the fatigue level assessment passes, it is checked whether there are any historical loss reporting records in the loss reporting record table with abnormal markings for the auxiliary user by the target user. If there are, it is determined that the auxiliary user does not meet the processing conditions; if there are no, it is determined that the auxiliary user meets the processing conditions.

[0060] In specific implementation, in response to an account processing request, it is verified whether the auxiliary user meets the processing conditions for restricting the target user's application account. If not, it is determined that the auxiliary user does not meet the processing conditions for restricting the target user's application account, and a verification failure reminder is sent to the auxiliary user's user terminal. If yes, the following step S106 is executed: based on the application interaction records between the auxiliary user and the target user, the intimacy between the auxiliary user and the target user is calculated, and the verification method corresponding to the intimacy is determined.

[0061] Step S106: Based on the application interaction records between the auxiliary user and the target user, calculate the intimacy between the auxiliary user and the target user, and determine the verification method corresponding to the intimacy.

[0062] The application interaction records include the interaction records between the auxiliary user and the target user within the application; for example, chat logs and transfer records. The intimacy level includes the intimacy level of the interaction between the auxiliary user and the target user within the application; the more frequent the interaction, the higher the intimacy level.

[0063] In practice, after verifying that the auxiliary user meets the conditions for restricting the target user's application account, it is determined whether the auxiliary user and the target user have a close relationship with frequent interactions, i.e., whether the intimacy level is higher than the intimacy threshold. If so, the target user's identity information only needs to be verified using a simple verification method, and the application account of the target user can be restricted after the verification is passed. If not, the target user needs to undergo biometric verification through the auxiliary user's user terminal, and the application account can be restricted if the verification is passed.

[0064] In one optional implementation of this embodiment, to improve the effectiveness of the calculated intimacy level, the intimacy level between the auxiliary user and the target user is calculated in the following manner:

[0065] (1) Query the application interaction records between the auxiliary user and the target user;

[0066] (2) Determine the frequency of application interactions, transaction amount, and interaction time span between the assisted user and the target user based on the application interaction records;

[0067] To ensure the validity of the calculated intimacy score, it is calculated based on the application interaction records between the auxiliary user and the target user. The calculation uses three parameters: application interaction frequency, interaction amount, and interaction time span. Application interaction frequency includes the number of interactions between the auxiliary user and the target user, such as the number of chat sessions and information sharing. Transaction amount includes the resource amounts involved in resource transactions between the auxiliary user and the target user, such as money transfers, red envelopes, or payments on behalf of others. The interaction time span includes the time difference between the request time corresponding to the account processing request and the interaction time of the last application interaction between the auxiliary user and the target user.

[0068] In one optional implementation of this embodiment, the application interaction frequency, transaction amount, and interaction time span are determined in the following manner:

[0069] The frequency of application interactions between the assisted user and the target user is calculated based on the application interaction records.

[0070] Read the transaction interaction records of the transaction attributes in the application interaction records, and calculate the transaction amount between the auxiliary user and the target user based on the transaction interaction records;

[0071] Calculate the interaction time span between the previous interaction record in the application interaction record and the request time corresponding to the account processing request.

[0072] (3) Input the frequency of application interaction, the amount of transaction and the time span of interaction into the intimacy algorithm to calculate the intimacy and obtain the intimacy.

[0073] The intimacy algorithm described in this embodiment calculates intimacy in the following way:

[0074] Input the application interaction frequency and the transaction amount into the target function, and output the frequency function value and the amount function value;

[0075] Calculate the ratio of the interaction time span to the time decay parameter and take the negative value of the ratio to obtain the time ratio;

[0076] The product of the frequency function value and the frequency weight and the product of the amount function value and the amount weight are calculated, and the product of these products and the power of the time ratio of the preset constant is used as the intimacy.

[0077] Among them, the intimacy level is greater than or equal to zero and less than or equal to 1.

[0078] For example, using formulas Calculate the intimacy level between the assisted user and the target user, where U is the intimacy level, V1 is the application interaction frequency, V2 is the transaction amount, and ω is the intimacy level. f For frequency weights, ωm The weight is the amount. t is the interaction time span, and T is the time decay parameter.

[0079] Among them, w f +w m =1, preferred, w f =0.85, w m =0.15, T=182, meaning that if the assistant user and the target user have not interacted for nearly six months, their intimacy level will decrease to half of its original value. f(x) is a logistic regression fitting function. f(x) is a variant of the sigmoid (sigmoid) function, where the sigmoid function... Image as Figure 4 As shown, the range of the sigmoid function is [0, 1], but when x is greater than 0, the range is [0.5, 1]. Therefore, shifting the entire function downwards yields... Image as Figure 5 As shown.

[0080] Furthermore, to control the curvature of the function, a coefficient 'a' is introduced, resulting in the function...

[0081] Ideally, Figure 5 The curve shown should have a steep slope at the beginning, gradually decreasing in slope later. For example, there should be a significant difference in intimacy between 1 transfer and 10 transfers, while 300 transfers and 400 transfers both indicate a high level of intimacy, and the difference in intimacy should not be significant. Therefore, it is necessary to discard the influence of a portion of long-tail users. Based on this, the 99th percentile is introduced, meaning that the maximum value for 99% of people is 1, at which point the curve slope is close to 0. Initially, the curve slope is close to 1. To characterize this coefficient, the rate of change at the 99th percentile should be one percent of the initial value, which is... This leads to the coefficient 'a'. It should be noted that the 99th percentile is a pre-calculated constant value. Taking the transfer amount as an example, the total transfer amount of all users in a year is sorted from smallest to largest. The 99th percentile refers to the maximum transfer amount of 99% of people in a year. In other words, 1% of people with relatively more resources are removed, and the remaining users are considered as all users.

[0082] After calculating the intimacy level, the corresponding verification method is determined. Specifically, an intimacy threshold is set. If the intimacy level between the assisted user and the target user is equal to or greater than the intimacy threshold, the corresponding verification method is determined to be the identifier input verification method. If the intimacy level is lower than the intimacy threshold, the corresponding verification method is determined to be the feature recognition verification method. In this embodiment, preferably, the intimacy threshold is 0.8.

[0083] Step S108: Based on the identity information of the target user collected by the user terminal according to the verification method, verify the identity of the target user, and after the verification is passed, restrict the application account.

[0084] In practice, in order to ensure the security of identity verification and account processing requests while improving the convenience of identity verification, if the intimacy level is equal to or higher than the intimacy threshold, identity verification will be performed using the identifier input verification method; if the intimacy level is lower than the intimacy threshold, identity verification will be performed using the feature recognition verification method.

[0085] If the verification method corresponding to the intimacy level is the identifier input verification method, in order to improve the convenience and efficiency of identity verification, in an optional implementation method provided in this embodiment, the process of verifying the identity of the target user based on the identity information of the target user collected by the user terminal according to the verification method is implemented in the following way:

[0086] Based on the account information of the application account carried in the account processing request, the user identity identifier of the target user is read;

[0087] The target identity identifier in the user identity identifier is determined and the target identity identifier is masked. The masked user identity identifier is then desensitized and sent to the user terminal so that the user terminal can collect the identifier keywords entered by the assisted user.

[0088] The system obtains the identifier keyword submitted by the user terminal and determines that the verification is successful if the identifier keyword matches the target identity identifier.

[0089] Specifically, firstly, based on the account information of the application account carried in the account processing request, the target user's user identity identifier is queried. Then, the target identity identifier in the user identity identifier is masked, and the masked user identity identifier is anonymized. The anonymized user identity identifier is sent to the auxiliary user's user terminal. After receiving the masked and anonymized user identity identifier sent by the server, the user terminal renders and displays the keyword collection page. After detecting the identifier keyword entered by the auxiliary user through the keyword collection page, the identifier keyword is submitted to the server as identity information so that the server can verify the identity of the target user.

[0090] For example, the server queries the target user's name based on the account identifier of the target user's application account carried in the account processing request, masks the first character of the name, performs de-identification processing on the masked name, and sends the de-identified name to the auxiliary user's user terminal. The auxiliary user's user terminal then generates a name like... Figure 6 The keyword collection page is shown and displayed. After the user terminal detects the identifying keyword entered by the user through the keyword display page, it submits the identifying keyword to the server. The server verifies whether the identifying keyword is consistent with the masked characters in the name. If they are consistent, the identity verification is confirmed to be successful. If they are inconsistent, the verification is confirmed to be unsuccessful, and a failure reminder is sent to the user terminal.

[0091] It should be noted that the blocking process can also completely block the user's identity identifier, allowing an assistant user to enter it.

[0092] If the verification method corresponding to the intimacy level is feature recognition verification, in order to ensure the security of the target user's application account, a biometric feature collection reminder is sent to the auxiliary user's user terminal. After receiving the biometric feature collection reminder, the user terminal renders and displays the feature collection page, and calls the feature collection component configured on the user terminal to collect and upload biometric features, so that the server can perform identity verification based on biometric features.

[0093] For example, if the verification method corresponding to the intimacy level is determined to be feature recognition verification, then a feature collection reminder is sent to the user terminal of the auxiliary user. The user terminal receives the feature collection reminder and renders a message based on the feature collection reminder, such as... Figure 7 The feature acquisition page is shown, which calls the image sensor configured on the user terminal to acquire the target user's facial image and submits it to the server. After receiving the facial image, the server verifies whether the received facial image matches the facial image stored in the target user's application account. If they match, the verification is successful; otherwise, the verification fails.

[0094] After identity verification is successful, the target user's application account is frozen to restrict account access. It should be noted that once the application account is restricted, functions such as login and initial payments will be limited; however, this embodiment does not specify the exact restrictions.

[0095] To improve the management of account restriction processing, this embodiment records the loss report through a loss report form. Optionally, after the account restriction processing is performed, the auxiliary loss report record is updated in the loss report table based on the account restriction processing result.

[0096] The lost status in the auxiliary lost status record is marked as lost status, and after the account restriction of the application account is lifted, the lost status is updated to lost status lifted.

[0097] If an abnormal flag request submitted by the target user is detected, the flag for the lost item in the auxiliary lost item record in the lost item record table will be updated to an abnormal flag.

[0098] The lost item report form is shown in the table below.

[0099] Loss report number Target User ID Auxiliary User ID Loss reporting method Should it be lifted? Loss reporting xxxxxxxx xxxx xxxx Facial recognition verification 0 0 xxxxxxxx xxxx xxxx Name verification 0 0 xxxxxxxx xxxx xxxx Name verification 1 1

[0100] Specifically, if the account restriction on the target user's application account is lifted, the status of "lifted" in the lost account record table will be updated to 1, indicating that the application account can be used normally. Furthermore, to improve the target user's awareness of the account restriction process, after the lost account is lifted, the target user can mark the backstabbing lost account behavior as an anomaly. Upon detecting an anomaly mark submitted by the target user against the auxiliary user, the lost account behavior mark in the lost account record table will be changed to an anomaly mark "1". When the auxiliary user subsequently submits an account processing request to the target user, the anomaly mark will be used to determine that the auxiliary user does not meet the processing conditions for account restriction on the target user's application account.

[0101] It should also be noted that account restriction processing involves updating the account freeze code in the member information table, and then marking the lost and found order number in the member information table to associate it with auxiliary users. In addition, multiple auxiliary users may submit account processing requests to the target user, so the lost and found record table can be idempotently overwritten.

[0102] In one optional implementation method provided in this embodiment, the account restriction is lifted in the following manner:

[0103] Obtain the login request for the application account submitted by the target user terminal of the accessing user;

[0104] Based on the login request, the access user is verified to remove restrictions, and if the verification is successful, the account restrictions on the application account are lifted.

[0105] like Figure 8 As shown, the system obtains the login request submitted by the target user to the application account via the user terminal. If the application account is detected to be restricted, a face verification reminder is sent to the target user's user terminal, causing the target user's user terminal to render as shown. Figure 8 The account restriction alert page shown above, and after detecting that the "Remove Restriction" control on the account restriction alert page is triggered, displays as follows: Figure 9 The system displays the face image capture page and calls the configured image capture component to capture and upload the target user's face image. Upon receiving the face image, the server verifies whether it matches the face image corresponding to the application account. If they match, the restriction is lifted, and the status of the corresponding lost / found record in the lost / found record table is updated from 0 to 1. A successful lifting notification is sent to the target user's terminal. Upon receiving the successful lifting notification, the target user's terminal renders... Figure 10The restriction removal page is shown and displayed; the target user can log in to the application account through the "Complete" button on the restriction removal page, and can also mark the auxiliary user as abnormal through the "Report xxx Abnormal Loss" control.

[0106] The following description uses the application account processing method provided in this embodiment in the scenario of account loss reporting as an example to further illustrate the application account processing method provided in this embodiment. See [link to documentation]. Figure 11 The application account processing method for the scenario of account loss reporting specifically includes steps S1102 to S1116.

[0107] Step S1102: Obtain the account processing request for the associated user submitted by the auxiliary user's user terminal, and read the lost and found record table based on the account processing request.

[0108] Step S1104: Query the total number of times the auxiliary user reports a lost item within a preset time interval in the lost item report record table.

[0109] Step S1106: Determine whether the total number of reported losses is less than the first number of reported losses;

[0110] If so, proceed to step S1108;

[0111] If not, a processing failure notification will be sent to the assistant user.

[0112] Step S1108: Determine whether the number of times the auxiliary user reports the loss of the associated user within the time period corresponding to the account processing request in the loss report record table is less than the second number of loss reports;

[0113] If so, proceed to step S1110;

[0114] If not, a processing failure notification will be sent to the assistant user.

[0115] Step S1110: Determine whether there is an abnormal identifier for the auxiliary user by the associated user in the lost and found record table;

[0116] If so, send a processing failure notification to the assisting user;

[0117] If not, proceed to steps S1112 to S1116.

[0118] Step S1112: Calculate the intimacy between the auxiliary user and the associated user based on the auxiliary user's application interaction records.

[0119] Step S1114: If the intimacy level is greater than the intimacy threshold, collect the identifier keywords of the associated user according to the identifier input verification method.

[0120] Step S1116: Verify the identity of the associated user based on the identifier keyword, and report the application account of the associated user as lost after the verification is successful.

[0121] The following description uses the application account processing method provided in this embodiment as an example in an auxiliary loss reporting scenario to further illustrate the application account processing method provided in this embodiment. (See also...) Figure 12 The application account processing method applied to auxiliary loss reporting scenarios includes the following steps.

[0122] Step S1204: Perform fatigue verification on the user based on the account processing request submitted by the user terminal.

[0123] In this process, the user terminal submits an account processing request to the server based on the account processing instructions submitted by the assistant user for the target user.

[0124] Step S1206: If the fatigue test passes, check whether there is any abnormal marking of the target user on the assistant user;

[0125] If so, proceed with steps S1208 to S1216 and S1224;

[0126] If not, send a processing failure notification to the user terminal.

[0127] Step S1208: Calculate the intimacy between the auxiliary user and the target user based on the application interaction records between the auxiliary user and the target user.

[0128] Step S1210: Determine the verification method corresponding to the intimacy level.

[0129] Step S1212: If the verification method is the identifier input verification method, then query the target user's user identity identifier based on the account identifier carried in the account processing request.

[0130] Step S1214: Mask the target identity in the user identity identifier to obtain the masked identity identifier.

[0131] Step S1216: Desensitize the masked identity identifier to obtain a desensitized identity identifier.

[0132] The user terminal obtains the de-identified identity identifier issued by the server, renders and displays the keyword collection page based on the de-identified identity identifier, obtains the identifier keywords entered by the user based on the keyword collection page, and submits them to the server.

[0133] Step S1224: Verify whether the identifier keywords are consistent with the masked identity identifier;

[0134] If they match, proceed to step S1226;

[0135] If there is a discrepancy, a processing failure notification will be sent to the user terminal.

[0136] Step S1226: Report the target user's application account as lost.

[0137] Another example of an application account processing method provided in this specification:

[0138] Reference Figure 13 The application account processing method provided in this embodiment is applied to a user terminal and specifically includes steps S1302 to S1306.

[0139] Step S1302: Submit an account processing request for the target user to the server according to the account processing instruction submitted for the target user.

[0140] The application account processing method provided in this embodiment improves the efficiency of auxiliary restriction of the application account of the target user by submitting an account processing request to the server and cooperating with the server to perform identity verification before account restriction processing.

[0141] In practical applications, the loss of a target user's smart device or application account poses a significant security risk. Therefore, to protect the target user's privacy information under the application account in the event of a lost device or application account, a user associated with the target user can freeze the application account, i.e., report it lost.

[0142] In this embodiment, the user terminal is a user terminal of an auxiliary user who assists the target user in handling account restriction processing. The auxiliary user is a user who assists the target user in reporting the loss of their account when needed, including associated users related to the target user. Furthermore, if the target user has multiple user terminals, and one user terminal is lost, the target user can use other user terminals to handle account restriction processing. Therefore, the auxiliary user can also be the target user themselves. The account processing request includes a request submitted by the auxiliary user through the user terminal to report the loss of the target user's application account.

[0143] In practice, when a user learns that a target user with whom they have a close relationship (family or friends, or frequent interactions) has lost their device or account, they can access the account processing service through their device and select the target user for whom account restrictions need to be imposed.

[0144] To improve the efficiency of assisting users in selecting target users during the account processing service process, and to avoid excessively long account restriction processing times due to assisting users' inability to find the target user or forget the target user's user identifier in a short time, which could further affect the security of the data in the target user's application account, in an optional implementation of this embodiment, the following operation is performed before submitting the account processing request to the server:

[0145] Obtain the user's access instruction for account processing services, and submit an access request to the server based on the access instruction;

[0146] Receive the recommended user list sent by the server based on the access request, and render and display the user selection page based on the recommended user list.

[0147] When assisting a user in accessing account processing services, a recommended list is displayed to the assisting user; the recommended user list is determined in the following way:

[0148] Obtain the access request for account processing service submitted by the user terminal;

[0149] Based on the access request, a list of recommended users is determined and sent to the user terminal so that the user terminal can display the list of recommended users.

[0150] Specifically, when the auxiliary user's user terminal receives the auxiliary user's access instruction for account processing services, it submits an access request to the server based on the access instruction. After receiving the access request, the server determines the recommended users to recommend to the auxiliary user and generates a recommended user list containing the recommended users, which is then sent to the auxiliary user's user terminal. After receiving the recommended user list, the auxiliary user's user terminal renders and displays the user selection page based on the recommended user list.

[0151] Assistant users can select recommended users from the recommended user list on the user selection page as target users and then submit an account processing request. Alternatively, they can enter the user identifier (name, application account identifier, email, or contact information) of the target user on the user selection page to search for users, identify the searched users as target users, and then submit an account processing request.

[0152] like Figure 2 As shown, after the assisted user accesses the account processing service, the assisted user's user terminal displays the following to the assisted user: Figure 2 The processing reminder page shown indicates that if an auxiliary user triggers the process... Figure 2After configuring the "Select User" control, the user terminal submits an access request to the server. Based on the access request, the server determines the recommended users for the auxiliary user and generates a recommended user list, which is then sent to the user terminal. After receiving the recommended user list, the user terminal generates a list as shown below. Figure 3 The user selection page is shown and displayed. The auxiliary user can select a target user from the recommended user list, and can also enter the target user's contact information or name to search for users. Furthermore, the auxiliary user can view the application friend list within the auxiliary user application through trigger control 301, and select a target user through the application friend list; however, this embodiment does not limit this further.

[0153] It should be noted that in the process of determining the recommended users for the auxiliary user, the frequency of application interaction or the degree of intimacy between the auxiliary user and each application friend in the application friend list can be sorted in descending order to obtain the friend sequence, and the application friends in the friend sequence can be read as recommended users according to a preset number; in addition, other parameters can also be used to determine the recommended users among the application friends, which can be set according to the actual scenario, and this embodiment does not limit it here.

[0154] After the assistant user selects or enters the target user through the user selection page, the assistant user submits an account processing instruction for the target user. After receiving the account processing instruction, the assistant user's user terminal submits an account processing request for the target user to the server based on the account processing instruction submitted by the assistant user for the target user, so that the server can perform account restriction processing on the target user's application account based on the account processing request.

[0155] After receiving an account processing request, the server responds by verifying whether the auxiliary user meets the processing conditions for account restriction processing of the target user's application account. The account restriction processing includes freezing the target user's application account or reporting the account lost.

[0156] To prevent auxiliary users from unjustifiably restricting the target user's application account, the server, upon receiving an account processing request from the auxiliary user's user terminal, verifies the auxiliary user's authorization to restrict the target user's application account. Specifically, it verifies whether the auxiliary user possesses the necessary authorization to restrict the target user's application account, or whether the auxiliary user meets the processing conditions for doing so. These conditions include: the auxiliary user's total number of lost / loss reports within a preset time interval not exceeding a first number of lost / loss reports; the auxiliary user's number of lost / loss reports against the target user within a single time interval not exceeding a second number of lost / loss reports; and / or, the auxiliary user's historical lost / loss report records against the target user containing records marked as abnormal behavior by the target user.

[0157] In practice, to enhance the credibility of the auxiliary user's assisted account suspension for the target user and prevent abnormal suspensions (i.e., assisted suspension of the target user's application account when not requested by the target user), the server verifies the auxiliary user's authority to restrict the target user's application account after receiving the account processing request submitted by the auxiliary user. This involves verifying whether the auxiliary user meets the processing conditions for restricting the target user's application account. In this embodiment, the server uses the following method to verify whether the auxiliary user meets the processing conditions for restricting the target user's application account:

[0158] Query the total number of times the auxiliary user reported a loss within a preset time interval in the loss report record table;

[0159] If the total number of reported losses is less than the first number of reported losses, then the historical reported loss records of the auxiliary user for the target user are read from the reported loss record table;

[0160] Calculate the number of times the auxiliary user reported the target user's account lost within the time interval corresponding to the account processing request in the historical loss reporting records;

[0161] If the number of times the user reports a loss is less than the second number of times the user reports a loss, then the auxiliary user is determined to meet the processing conditions.

[0162] To further enhance the credibility of the assisted user's assistance in reporting the loss of the target user, in this embodiment, if the server determines that the number of times the assisted user reports the loss of the target user within the time interval corresponding to the account processing request does not exceed the second number of reports, the server further performs the following operation to determine whether the assisted user meets the processing conditions:

[0163] Read the loss reporting behavior marker from the historical loss reporting records;

[0164] If there are any historical loss reporting records marked as abnormal, then it is determined that the auxiliary user does not meet the processing conditions.

[0165] Specifically, the server assesses the fatigue level of the auxiliary user by setting a preset time interval, a first number of reported losses, a reporting time interval, and a second number of reported losses. After receiving an account processing request from the auxiliary user for the target user, the server assesses the auxiliary user's fatigue level based on the reported loss record table. Specifically, the server queries the reported loss record table to check the total number of reported losses by the auxiliary user within the preset time interval and verifies whether the total number of reported losses is less than the first number of reported losses. If so, the server reads the historical reported loss records of the auxiliary user for the target user from the reported loss record table and determines whether the number of reported losses by the auxiliary user for the target user within the reported loss time interval corresponding to the account processing request exceeds the second number of reported losses.

[0166] In other words, after the server obtains the target user's application account identifier carried in the auxiliary user's request to process the target user's account, it performs a two-dimensional fatigue assessment: one is that the auxiliary user can only assist in reporting the first number of lost items within a preset time interval, and the other is that the auxiliary user can only assist in reporting the second number of lost items for the target user within the corresponding time interval. If the fatigue assessment passes, it can be determined that the auxiliary user meets the processing conditions.

[0167] For example, if the preset time interval M1 = 30 days, the first number of loss reports N1 = 2, the corresponding time interval M2 = 1 day, and the second number of loss reports N2 = 1, after the server receives the auxiliary user's request to report the loss of the associated user's account, it reads the loss report record table and queries the auxiliary user's total number of loss reports within 30 days. If the total number of loss reports is 2 or greater, the fatigue assessment fails, and a verification failure reminder is sent to the auxiliary user's user terminal. If the total number of loss reports is less than 2, it further determines whether the auxiliary user has reported the loss of the associated user within 1 day. If so, the fatigue assessment fails, and a verification failure reminder is sent to the auxiliary user's user terminal. If not, the fatigue assessment passes.

[0168] If the fatigue level assessment passes, in order to prevent the auxiliary user from maliciously reporting the target user's account as lost and to enhance the protection of the target user's application account, the effectiveness of the auxiliary user's account restriction processing is further verified. After the fatigue level assessment passes, it is checked whether there are any historical loss reporting records in the loss reporting record table with abnormal markings for the auxiliary user by the target user. If there are, it is determined that the auxiliary user does not meet the processing conditions; if there are no, it is determined that the auxiliary user meets the processing conditions.

[0169] In practice, in response to an account processing request, the server verifies whether the auxiliary user meets the processing conditions for restricting the target user's application account. If not, it determines that the auxiliary user does not meet the processing conditions for restricting the target user's application account and sends a verification failure reminder to the auxiliary user's user terminal. If yes, it executes the steps of calculating the intimacy between the auxiliary user and the target user based on the application interaction records between the auxiliary user and the target user, and determining the verification method corresponding to the intimacy.

[0170] The application interaction records include the interaction records between the auxiliary user and the target user within the application; for example, chat logs and transfer records. The intimacy level includes the intimacy level of the interaction between the auxiliary user and the target user within the application; the more frequent the interaction, the higher the intimacy level.

[0171] In practice, after verifying that the auxiliary user meets the conditions for restricting the target user's application account, the server determines whether the auxiliary user and the target user have a close relationship with frequent interactions, i.e., whether the intimacy level is higher than the intimacy threshold. If so, the server only needs to verify the target user's identity information using a simple verification method, and can restrict the target user's application account after the verification is successful. If not, the target user needs to perform biometric verification through the auxiliary user's user terminal, and the application account will be restricted if the verification is successful.

[0172] In this embodiment, to improve the effectiveness of the calculated intimacy level, the server calculates the intimacy level between the auxiliary user and the target user in the following way:

[0173] (1) Query the application interaction records between the auxiliary user and the target user;

[0174] (2) Determine the frequency of application interactions, transaction amount, and interaction time span between the assisted user and the target user based on the application interaction records;

[0175] To ensure the validity of the calculated intimacy score, it is calculated based on the application interaction records between the auxiliary user and the target user. The calculation uses three parameters: application interaction frequency, interaction amount, and interaction time span. Application interaction frequency includes the number of interactions between the auxiliary user and the target user, such as the number of chat sessions and information sharing. Transaction amount includes the resource amounts involved in resource transactions between the auxiliary user and the target user, such as money transfers, red envelopes, or payments on behalf of others. The interaction time span includes the time difference between the request time corresponding to the account processing request and the interaction time of the last application interaction between the auxiliary user and the target user.

[0176] In this embodiment, the frequency of application interactions, transaction amounts, and interaction time spans are determined as follows:

[0177] The frequency of application interactions between the assisted user and the target user is calculated based on the application interaction records.

[0178] Read the transaction interaction records of the transaction attributes in the application interaction records, and calculate the transaction amount between the auxiliary user and the target user based on the transaction interaction records;

[0179] Calculate the interaction time span between the previous interaction record in the application interaction record and the request time corresponding to the account processing request.

[0180] (3) Input the frequency of application interaction, the amount of transaction and the time span of interaction into the intimacy algorithm to calculate the intimacy and obtain the intimacy.

[0181] The intimacy algorithm described in this embodiment calculates intimacy in the following way:

[0182] Input the application interaction frequency and the transaction amount into the target function, and output the frequency function value and the amount function value;

[0183] Calculate the ratio of the interaction time span to the time decay parameter and take the negative value of the ratio to obtain the time ratio;

[0184] The product of the frequency function value and the frequency weight and the product of the amount function value and the amount weight are calculated, and the product of these products and the power of the time ratio of the preset constant is used as the intimacy.

[0185] Among them, the intimacy level is greater than or equal to zero and less than or equal to 1.

[0186] For example, using formulas Calculate the intimacy level between the assisted user and the target user, where U is the intimacy level, V1 is the application interaction frequency, V2 is the transaction amount, and ω is the intimacy level. f For frequency weights, ω m The weight is the amount. t is the interaction time span, and T is the time decay parameter.

[0187] Among them, w f +w m =1, preferred, w f =0.85, w m =0.15, T=182, meaning that if the assistant user and the target user have not interacted for nearly six months, their intimacy level will decrease to half of its original value. f(x) is a logistic regression fitting function. f(x) is a variant of the sigmoid (sigmoid) function, where the sigmoid function... Image as Figure 4 As shown, the range of the sigmoid function is [0, 1], but when x is greater than 0, the range is [0.5, 1]. Therefore, shifting the entire function downwards yields... Image as Figure 5 As shown.

[0188] Furthermore, to control the curvature of the function, a coefficient 'a' is introduced, resulting in the function...

[0189] Ideally, Figure 5 The curve shown should have a steep slope at the beginning, gradually decreasing in slope later. For example, there should be a significant difference in intimacy between 1 transfer and 10 transfers, while 300 transfers and 400 transfers both indicate a high level of intimacy, and the difference in intimacy should not be significant. Therefore, it is necessary to discard the influence of a portion of long-tail users. Based on this, the 99th percentile is introduced, meaning that the maximum value for 99% of people is 1, at which point the curve slope is close to 0. Initially, the curve slope is close to 1. To characterize this coefficient, the rate of change at the 99th percentile should be one percent of the initial value, which is... This leads to the coefficient 'a'. It should be noted that the 99th percentile is a pre-calculated constant value. Taking the transfer amount as an example, the total transfer amount of all users in a year is sorted from smallest to largest. The 99th percentile refers to the maximum transfer amount of 99% of people in a year. In other words, 1% of people with relatively more resources are removed, and the remaining users are considered as all users.

[0190] After calculating the intimacy level, the corresponding verification method is determined. Specifically, an intimacy threshold is set. If the intimacy level between the assisted user and the target user is equal to or greater than the intimacy threshold, the corresponding verification method is determined to be the identifier input verification method. If the intimacy level is lower than the intimacy threshold, the corresponding verification method is determined to be the feature recognition verification method. In this embodiment, preferably, the intimacy threshold is 0.8.

[0191] Step S1304: If the server determines that the identity verification method is the identifier input verification method, collect the identifier keywords input by the target user.

[0192] In one optional implementation of this embodiment, after receiving the account processing request, the server determines the verification method in the following manner:

[0193] Verify whether the auxiliary user meets the processing conditions for account restriction processing of the application account;

[0194] If so, calculate the intimacy level between the auxiliary user and the target user based on their application interaction records;

[0195] The verification method is determined based on the degree of intimacy.

[0196] Step S1306: Submit the identifier keyword as identity information to the server to verify the identity of the target user and, after successful verification, restrict the application account of the target user.

[0197] In practice, in order to ensure the security of identity verification and account processing requests while improving the convenience of identity verification, if the intimacy level is equal to or higher than the intimacy threshold, the server uses the identifier input verification method for identity verification; if the intimacy level is lower than the intimacy threshold, the server uses the feature recognition verification method for identity verification.

[0198] If the verification method corresponding to the intimacy level is the identifier input verification method, in order to improve the convenience and efficiency of identity verification, in this embodiment, the server performs the identity verification of the target user based on the identity information of the target user collected by the user terminal according to the verification method in the following manner:

[0199] Based on the account information of the application account carried in the account processing request, the user identity identifier of the target user is read;

[0200] The target identity identifier in the user identity identifier is determined and the target identity identifier is masked. The masked user identity identifier is then desensitized and sent to the user terminal so that the user terminal can collect the identifier keywords entered by the assisted user.

[0201] The system obtains the identifier keyword submitted by the user terminal and determines that the verification is successful if the identifier keyword matches the target identity identifier.

[0202] Specifically, the server first queries the target user's identity identifier based on the application account information carried in the account processing request. Then, it masks the target identity identifier in the user identity identifier and performs de-identification processing on the masked user identity identifier. The de-identified user identity identifier is then sent to the auxiliary user's user terminal. After receiving the masked and de-identified user identity identifier sent by the server, the user terminal renders and displays the keyword collection page. After detecting the identifier keyword entered by the auxiliary user through the keyword collection page, it submits the identifier keyword as identity information to the server so that the server can verify the identity of the target user.

[0203] In one optional implementation of this embodiment, the following operation is performed before collecting the identifying keywords:

[0204] Receive the user identity identifier that has been masked and de-identified by the server;

[0205] The keyword collection page is rendered and displayed based on the user's identity identifier.

[0206] For example, the server queries the target user's name based on the account identifier of the target user's application account carried in the account processing request, masks the first character of the name, performs de-identification processing on the masked name, and sends the de-identified name to the auxiliary user's user terminal. The auxiliary user's user terminal then generates a name like... Figure 6 The keyword collection page is shown and displayed. After the user terminal detects the identifying keyword entered by the user through the keyword display page, it submits the identifying keyword to the server. The server verifies whether the identifying keyword is consistent with the masked characters in the name. If they are consistent, the identity verification is confirmed to be successful. If they are inconsistent, the verification is confirmed to be unsuccessful, and a failure reminder is sent to the user terminal.

[0207] It should be noted that the blocking process can also completely block the user's identity identifier, allowing an assistant user to enter it.

[0208] In one optional implementation of this embodiment, if the server determines that the verification method for identity verification is the feature recognition verification method, then the feature collection reminder issued by the server is received.

[0209] Based on the aforementioned feature acquisition reminder, a feature acquisition page is rendered and displayed;

[0210] The system calls the acquisition component configured on the user terminal to collect the detected biometric information and submits the biometric information as identity information to the server.

[0211] If the verification method corresponding to the intimacy level is feature recognition verification, in order to ensure the security of the target user's application account, the server sends a biometric feature collection reminder to the auxiliary user's user terminal; after receiving the biometric feature collection reminder, the user terminal renders and displays the feature collection page, and calls the feature collection component configured on the user terminal to collect and upload biometric features, so that the server can perform identity verification based on biometric features.

[0212] For example, if the verification method corresponding to the intimacy level is determined to be feature recognition verification, the server sends a feature collection reminder to the user's terminal. The user terminal receives the feature collection reminder and renders a message based on it. Figure 7The feature acquisition page is shown, which calls the image sensor configured on the user terminal to acquire the target user's facial image and submits it to the server. After receiving the facial image, the server verifies whether the received facial image matches the facial image stored in the target user's application account. If they match, the verification is successful; otherwise, the verification fails.

[0213] After identity verification is successful, the server freezes the target user's application account to restrict account access. It should be noted that once the application account is restricted, functions such as login and initial payments will be limited; however, this embodiment does not specify the exact restrictions.

[0214] To improve the management of account restriction processing, this embodiment records the loss report through a loss report form. After the account restriction processing is carried out, the auxiliary loss report record is updated in the loss report table based on the account restriction processing result.

[0215] The lost status in the auxiliary lost status record is marked as lost status, and after the account restriction of the application account is lifted, the lost status is updated to lost status lifted.

[0216] If an abnormal flag request submitted by the target user is detected, the flag for the lost item in the auxiliary lost item record in the lost item record table will be updated to an abnormal flag.

[0217] Specifically, if the account restriction on the target user's application account is lifted, the status of "lifted" in the lost account record table will be updated to 1, indicating that the application account can be used normally. Furthermore, to improve the target user's awareness of the account restriction process, after the lost account is lifted, the target user can mark the backstabbing lost account behavior as an anomaly. Upon detecting an anomaly mark submitted by the target user against the auxiliary user, the lost account behavior mark in the lost account record table will be changed to an anomaly mark "1". When the auxiliary user subsequently submits an account processing request to the target user, the anomaly mark will be used to determine that the auxiliary user does not meet the processing conditions for account restriction on the target user's application account.

[0218] It should also be noted that account restriction processing involves updating the account freeze code in the member information table, and then marking the lost and found order number in the member information table to associate it with auxiliary users. In addition, multiple auxiliary users may submit account processing requests to the target user, so the lost and found record table can be idempotently overwritten.

[0219] In this embodiment, the server removes account restrictions in the following manner:

[0220] Obtain the login request for the application account submitted by the target user terminal of the accessing user;

[0221] Based on the login request, the access user is verified to remove restrictions, and if the verification is successful, the account restrictions on the application account are lifted.

[0222] like Figure 8 As shown, the server receives the login request submitted by the target user to the application account via the user terminal. If the application account is detected to be restricted, a face verification reminder is sent to the target user's user terminal, causing the target user's user terminal to render as shown. Figure 8 The account restriction alert page shown above, and after detecting that the "Remove Restriction" control on the account restriction alert page is triggered, displays as follows: Figure 9 The system displays the face image capture page and calls the configured image capture component to capture and upload the target user's face image. Upon receiving the face image, the server verifies whether it matches the face image corresponding to the application account. If they match, the restriction is lifted, and the status of the corresponding lost / found record in the lost / found record table is updated from 0 to 1. A successful lifting notification is sent to the target user's terminal. Upon receiving the successful lifting notification, the target user's terminal renders... Figure 10 The restriction removal page is shown and displayed; the target user can log in to the application account through the "Complete" button on the restriction removal page, and can also mark the auxiliary user as abnormal through the "Report xxx Abnormal Loss" control.

[0223] The following description uses the application account processing method provided in this embodiment as an example in an auxiliary loss reporting scenario to further illustrate the application account processing method provided in this embodiment. (See also...) Figure 12 The application account processing method applied to auxiliary loss reporting scenarios includes the following steps.

[0224] Step S1202: Submit an account processing request to the server based on the account processing instructions submitted by the assistant user for the target user.

[0225] The server performs fatigue verification on the auxiliary user based on the account processing request submitted by the user terminal. If the fatigue verification passes, it checks whether there is any abnormal marking of the auxiliary user by the target user. If so, it calculates the intimacy between the auxiliary user and the target user based on the application interaction records between the auxiliary user and the target user, determines the verification method corresponding to the intimacy, and if the verification method is the identifier input verification method, it queries the user identity identifier of the target user based on the account identifier carried in the account processing request, masks the target identity identifier in the user identity identifier to obtain the masked identity identifier, and desensitizes the masked identity identifier to obtain the desensitized identity identifier.

[0226] Step S1218: Obtain the de-identified identity identifier issued by the server.

[0227] Step S1220: Render and display the keyword collection page based on the de-identified identity identifier.

[0228] Step S1222: Obtain the identifying keywords entered by the auxiliary user based on the keyword collection page and submit them to the server.

[0229] If the server verifies whether the keyword of the identifier matches the identity identifier of the blocked user, it will report the target user's application account as lost; if they do not match, it will send a processing failure reminder to the user's terminal.

[0230] This specification provides an example of an application account processing device as follows:

[0231] In the above embodiments, an application account processing method for a server is provided, and correspondingly, an application account processing device running on a server is also provided, which will be described below with reference to the accompanying drawings.

[0232] Reference Figure 14 The diagram shows an application account processing device provided in this embodiment.

[0233] Since the apparatus embodiments correspond to the method embodiments, the descriptions are relatively simple. For relevant parts, please refer to the corresponding descriptions of the method embodiments provided above. The apparatus embodiments described below are merely illustrative.

[0234] This embodiment provides an application account processing device, including:

[0235] The request receiving module 1402 is configured to receive account processing requests for a target user submitted by the user terminal of the auxiliary user.

[0236] The condition verification module 1404 is configured to, in response to the account processing request, verify whether the auxiliary user meets the processing conditions for account restriction processing of the target user's application account.

[0237] If so, the verification method determination module 1406 is run. The verification method determination module 1406 is configured to calculate the intimacy between the auxiliary user and the target user based on the application interaction records between the auxiliary user and the target user, and determine the verification method corresponding to the intimacy.

[0238] The account restriction processing module 1408 is configured to verify the identity of the target user based on the identity information of the target user collected by the user terminal according to the verification method, and to restrict the application account after the verification is passed.

[0239] Another embodiment of the application account processing device provided in this specification is as follows:

[0240] In the above embodiments, an application account processing method for a user terminal is provided, and correspondingly, an application account processing device running on a user terminal is also provided, which will be described below with reference to the accompanying drawings.

[0241] Reference Figure 15 The diagram shows an application account processing device provided in this embodiment.

[0242] Since the apparatus embodiments correspond to the method embodiments, the descriptions are relatively simple. For relevant parts, please refer to the corresponding descriptions of the method embodiments provided above. The apparatus embodiments described below are merely illustrative.

[0243] This embodiment provides an application account processing device, including:

[0244] The request submission module 1502 is configured to submit an account processing request for the target user to the server based on the account processing instruction submitted for the target user.

[0245] If the server determines that the identity verification method is the identifier input verification method, the keyword collection module 1504 is run. The keyword collection module 1504 is configured to collect identifier keywords input by the target user.

[0246] The identity information submission module 1506 is configured to submit the identification keyword as identity information to the server to verify the identity of the target user and, after successful verification, to restrict the application account of the target user.

[0247] This specification provides the following embodiment of an application account processing device:

[0248] Corresponding to the application account processing method for servers described above, based on the same technical concept, one or more embodiments of this specification also provide an application account processing device for executing the application account processing method provided above. Figure 16 This is a schematic diagram of the structure of an application account processing device provided for one or more embodiments of this specification.

[0249] This embodiment provides an application account processing device, including:

[0250] like Figure 16As shown, the application account processing device can vary considerably due to differences in configuration or performance. It may include one or more processors 1601 and memory 1602, and the memory 1602 may store one or more application programs or data. The memory 1602 may be temporary or persistent storage. The application programs stored in the memory 1602 may include one or more modules (not shown), each module may include a series of computer-executable instructions from the application account processing device. Furthermore, the processor 1601 may be configured to communicate with the memory 1602 and execute the series of computer-executable instructions in the memory 1602 on the application account processing device. The application account processing device may also include one or more power supplies 1603, one or more wired or wireless network interfaces 1604, one or more input / output interfaces 1605, one or more keyboards 1606, etc.

[0251] In one specific embodiment, the application account processing device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the application account processing device, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following:

[0252] Receive account processing requests for the target user submitted by the user terminal of the auxiliary user;

[0253] In response to the account processing request, verify whether the auxiliary user meets the processing conditions for account restriction processing of the target user's application account;

[0254] If so, based on the application interaction records between the auxiliary user and the target user, calculate the intimacy between the auxiliary user and the target user, and determine the verification method corresponding to the intimacy;

[0255] Based on the identity information of the target user collected by the user terminal according to the verification method, the identity of the target user is verified, and the application account is restricted after the verification is passed.

[0256] Another example of an application account processing device provided in this specification is as follows:

[0257] Corresponding to the application account processing method for a user terminal described above, based on the same technical concept, one or more embodiments of this specification also provide an application account processing device for executing the application account processing method provided above. Figure 17This is a schematic diagram of the structure of an application account processing device provided for one or more embodiments of this specification.

[0258] This embodiment provides an application account processing device, including:

[0259] like Figure 17 As shown, the application account processing device can vary considerably due to differences in configuration or performance. It may include one or more processors 1701 and memory 1702, and the memory 1702 may store one or more application programs or data. The memory 1702 may be temporary or persistent storage. The application programs stored in the memory 1702 may include one or more modules (not shown), each module may include a series of computer-executable instructions from the application account processing device. Furthermore, the processor 1701 may be configured to communicate with the memory 1702 and execute the series of computer-executable instructions in the memory 1702 on the application account processing device. The application account processing device may also include one or more power supplies 1703, one or more wired or wireless network interfaces 1704, one or more input / output interfaces 1705, one or more keyboards 1706, etc.

[0260] In one specific embodiment, the application account processing device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the application account processing device, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following:

[0261] Based on the account processing instructions submitted for the target user, submit an account processing request for the target user to the server;

[0262] If the server determines that the identity verification method is the identifier input verification method, it collects the identifier keywords input by the target user.

[0263] The identified keywords are submitted to the server as identity information to verify the identity of the target user and, upon successful verification, to restrict the application account of the target user.

[0264] This specification provides an example of a storage medium as follows:

[0265] In accordance with the application account processing method for servers described above, and based on the same technical concept, one or more embodiments of this specification also provide a storage medium.

[0266] The storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed by a processor, implement the following process:

[0267] Receive account processing requests for the target user submitted by the user terminal of the auxiliary user;

[0268] In response to the account processing request, verify whether the auxiliary user meets the processing conditions for account restriction processing of the target user's application account;

[0269] If so, based on the application interaction records between the auxiliary user and the target user, calculate the intimacy between the auxiliary user and the target user, and determine the verification method corresponding to the intimacy;

[0270] Based on the identity information of the target user collected by the user terminal according to the verification method, the identity of the target user is verified, and the application account is restricted after the verification is passed.

[0271] It should be noted that the embodiments concerning storage media and the embodiments concerning application account processing methods in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding methods described above, and the repeated parts will not be described again.

[0272] Another embodiment of the storage medium provided in this specification is as follows:

[0273] In accordance with the application account processing method for user terminals described above, and based on the same technical concept, one or more embodiments of this specification also provide a storage medium.

[0274] The storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed by a processor, implement the following process:

[0275] Based on the account processing instructions submitted for the target user, submit an account processing request for the target user to the server;

[0276] If the server determines that the identity verification method is the identifier input verification method, it collects the identifier keywords input by the target user.

[0277] The identified keywords are submitted to the server as identity information to verify the identity of the target user and, upon successful verification, to restrict the application account of the target user.

[0278] It should be noted that the embodiments concerning storage media and the embodiments concerning application account processing methods in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding methods described above, and the repeated parts will not be described again.

[0279] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0280] In the 1930s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many improvements to the methodology today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that an improvement to the methodology cannot be implemented using a hardware physical module. For example, a Programmable Logic Device (PLD) (e.g., a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program a digital system themselves to "integrate" it onto a PLD, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0281] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, ASICs, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0282] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0283] For ease of description, the above apparatus is described by dividing it into various functional units. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in one or more software and / or hardware.

[0284] Those skilled in the art will understand that one or more embodiments of this specification can be provided as a method, system, or computer program product. Therefore, one or more embodiments of this specification may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this specification may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0285] This specification is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this specification. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create a machine for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0286] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0287] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0288] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0289] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0290] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0291] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0292] One or more embodiments of this specification can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a particular task or implement a particular abstract data type. One or more embodiments of this specification can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0293] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

[0294] The above description is merely an embodiment of this document and is not intended to limit the scope of this document. Various modifications and variations can be made to this document by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this document should be included within the scope of the claims of this document.

Claims

1. An application account processing method, applied to a server, comprising: Receive an account processing request for the target user submitted through the user terminal by the auxiliary user after entering the target user's user identifier on the user selection page; In response to the account processing request, the total number of times the auxiliary user reported loss within a preset time interval is queried in the loss reporting record table and it is verified whether it is less than the first number of loss reporting. If so, the historical loss reporting records of the auxiliary user for the target user are read from the loss reporting record table, and based on the historical loss reporting records, it is determined whether the number of times the auxiliary user reported loss to the target user for the user within the loss reporting time interval corresponding to the account processing request exceeds the second number of loss reporting. If not, check whether the auxiliary user has a lost record marked as abnormal behavior by the target user in the lost record table. If it does, determine that the auxiliary user does not meet the processing conditions and send a verification failure reminder to the user terminal. If not, calculate the intimacy between the auxiliary user and the target user based on their application interaction records, and determine the verification method corresponding to the intimacy; the intimacy includes the intimacy of the interaction between the auxiliary user and the target user within the application; Based on the identity information of the target user collected by the user terminal according to the verification method, the identity of the target user is verified, and the application account is restricted after the verification is passed. If an abnormal flag request submitted by the target user is detected, the loss behavior flag in the auxiliary loss record in the loss record table is updated to an abnormal flag. The verification method includes the corresponding identifier input verification method when the intimacy is equal to or higher than the intimacy threshold. The account restriction processing includes the account freezing processing of the application account of the target user.

2. The application account processing method according to claim 1, wherein calculating the intimacy between the auxiliary user and the target user based on the application interaction records between the auxiliary user and the target user includes: Query the application interaction records between the auxiliary user and the target user; Based on the application interaction records, determine the frequency of application interactions, transaction amount, and interaction time span between the assisted user and the target user; The frequency of application interactions, the amount of transactions, and the duration of interactions are input into the intimacy algorithm to calculate the intimacy level.

3. The application account processing method according to claim 2, wherein determining the frequency of application interactions, transaction amount, and interaction time span between the auxiliary user and the target user based on the application interaction records includes: The frequency of application interactions between the assisted user and the target user is calculated based on the application interaction records. Read the transaction interaction records of the transaction attributes in the application interaction records, and calculate the transaction amount between the auxiliary user and the target user based on the transaction interaction records; Calculate the interaction time span between the previous interaction record in the application interaction record and the request time corresponding to the account processing request.

4. The application account processing method according to claim 2, wherein the intimacy algorithm comprises: Input the application interaction frequency and the transaction amount into the target function, and output the frequency function value and the amount function value; Calculate the ratio of the interaction time span to the time decay parameter and take the negative value of the ratio to obtain the time ratio; The product of the frequency function value and the frequency weight and the product of the amount function value and the amount weight are calculated, and the product of these products and the power of the time ratio of the preset constant is used as the intimacy.

5. The application account processing method according to claim 1, wherein if the verification method corresponding to the intimacy is an identifier input verification method, the step of verifying the identity of the target user based on the identity information of the target user collected by the user terminal according to the verification method includes: Based on the account information of the application account carried in the account processing request, the user identity identifier of the target user is read; The target identity identifier in the user identity identifier is determined and the target identity identifier is masked. The masked user identity identifier is then desensitized and sent to the user terminal so that the user terminal can collect the identifier keywords entered by the assisted user. The system obtains the identifier keyword submitted by the user terminal and determines that the verification is successful if the identifier keyword matches the target identity identifier.

6. The application account processing method according to claim 1, after the step of verifying the identity of the target user based on the identity information of the target user collected by the user terminal according to the verification method, and performing account restriction processing on the application account after the verification is passed, further comprising: Obtain the login request for the application account submitted by the target user terminal of the accessing user; Based on the login request, the access user is verified to remove restrictions, and if the verification is successful, the account restrictions on the application account are lifted.

7. The application account processing method according to claim 1, wherein after performing account restriction processing, the auxiliary loss reporting record is updated in the loss reporting record table based on the account restriction processing result; The lost status in the auxiliary lost record is marked as lost status, and after the account restriction of the application account is lifted, the lost status is updated to lost status lifted.

8. The application account processing method according to claim 1, before the step of receiving the account processing request for the target user submitted by the user terminal of the auxiliary user is executed, it further includes: Obtain the access request for account processing service submitted by the user terminal; Based on the access request, a list of recommended users is determined and sent to the user terminal so that the user terminal can display the list of recommended users.

9. An application account processing method, applied to a user terminal, comprising: Based on the account processing instruction for the target user submitted by the assistant user after entering the target user's user identifier on the user selection page, an account processing request for the target user is submitted to the server. If the server determines that the identity verification method is the identifier input verification method, it collects the identifier keywords input by the target user. The verification method is determined based on the intimacy between the auxiliary user and the target user. The identifier input verification method is determined when the intimacy is equal to or greater than the intimacy threshold. The intimacy includes the interaction intimacy between the auxiliary user and the target user within the application. The intimacy is determined by querying the lost and found record table to find that the total number of lost and found attempts by the auxiliary user within a preset time interval is less than the first number of lost and found attempts. The server also reads the historical lost and found records of the auxiliary user against the target user from the lost and found record table. Based on the historical lost and found records, the server determines that the number of lost and found attempts by the auxiliary user against the target user within the lost and found time interval corresponding to the account processing request does not exceed the second number of lost and found attempts. The server calculates the results after confirming that there are no lost and found records in the lost and found record table where the auxiliary user is marked as having abnormal behavior by the target user. If such records exist, the server receives a verification failure notification. The identifier keyword is submitted to the server as identity information to verify the identity of the target user and, after successful verification, to restrict the application account of the target user; the account restriction includes freezing the application account of the target user.

10. The application account processing method according to claim 9, wherein if the verification method determined by the server is the identifier input verification method, before the step of collecting the identifier keyword input by the target user is executed, the method further includes: Receive the user identity identifier that has been masked and de-identified by the server; The keyword collection page is rendered and displayed based on the user's identity identifier.

11. The application account processing method according to claim 9, further comprising: If the server determines that the identity verification method is feature recognition verification, then the server will send a feature collection reminder. Based on the aforementioned feature acquisition reminder, a feature acquisition page is rendered and displayed; The system calls the acquisition component configured on the user terminal to collect the detected biometric information and submits the biometric information as identity information to the server.

12. The application account processing method according to claim 9, further comprising, before the step of submitting an account processing request for the target user to the server based on the account processing instruction submitted by the assisted user after entering the user identifier of the target user on the user selection page: Obtain the user's access instruction for account processing services, and submit an access request to the server based on the access instruction; Receive the recommended user list sent by the server based on the access request, and render and display the user selection page based on the recommended user list.

13. The application account processing method according to claim 9, wherein after receiving the account processing request, the server determines the verification method in the following manner: Verify whether the auxiliary user meets the processing conditions for account restriction processing of the application account; If so, calculate the intimacy level between the auxiliary user and the target user based on their application interaction records; The verification method is determined based on the degree of intimacy.

14. An application account processing device, operating on a server, comprising: The request receiving module is configured to receive an account processing request for the target user submitted through the user terminal by the auxiliary user after entering the target user's user identifier on the user selection page. The condition verification module is configured to, in response to the account processing request, query the total number of times the auxiliary user has reported loss within a preset time interval in the loss record table and verify whether it is less than the first number of loss reports. If so, read the historical loss report records of the auxiliary user for the target user in the loss record table, and determine whether the number of times the auxiliary user has reported loss to the target user for the target user within the loss report time interval corresponding to the account processing request exceeds the second number of loss reports. If not, check whether the auxiliary user has a lost record marked as abnormal behavior by the target user in the lost record table. If it does, determine that the auxiliary user does not meet the processing conditions and send a verification failure reminder to the user terminal. If not, the verification method determination module is run. The verification method determination module is configured to calculate the intimacy between the auxiliary user and the target user based on the application interaction records between the auxiliary user and the target user, and determine the verification method corresponding to the intimacy. The intimacy includes the interaction intimacy between the auxiliary user and the target user within the application. The account restriction processing module is configured to verify the identity of the target user based on the identity information of the target user collected by the user terminal according to the verification method, and to restrict the application account after the verification is successful. If an abnormal flag request submitted by the target user is detected, the loss behavior flag in the auxiliary loss record in the loss record table is updated to an abnormal flag. The verification method includes the identifier input verification method corresponding to the intimacy level being equal to or higher than the intimacy threshold. The account restriction processing includes account freezing processing of the target user's application account.

15. An application account processing device, operating on a user terminal, comprising: The request submission module is configured to submit an account processing request for the target user to the server based on the account processing instruction for the target user submitted by the auxiliary user after entering the target user's user identifier on the user selection page; If the server determines that the identity verification method is the identifier input verification method, the keyword collection module is run. The keyword collection module is configured to collect identifier keywords input by the target user. The verification method is determined based on the intimacy between the auxiliary user and the target user. The identifier input verification method is determined when the intimacy is equal to or greater than an intimacy threshold. The intimacy includes the interaction intimacy between the auxiliary user and the target user within the application. The intimacy is determined by querying the lost and found record table to find that the total number of lost and found attempts by the auxiliary user within a preset time interval is less than the first number of lost and found attempts. The historical lost and found records of the auxiliary user against the target user are read from the lost and found record table. Based on the historical lost and found records, it is determined that the number of lost and found attempts by the auxiliary user against the target user within the lost and found time interval corresponding to the account processing request does not exceed the second number of lost and found attempts. The calculation is performed after confirming that there are no lost and found records in the lost and found record table where the auxiliary user is marked as having abnormal behavior by the target user. If such records exist, a verification failure reminder is received from the server. The identity information submission module is configured to submit the identifier keyword as identity information to the server to verify the identity of the target user and, after successful verification, to restrict the application account of the target user; the account restriction processing includes freezing the application account of the target user.

16. An application account processing device, comprising: processor; as well as, A memory configured to store computer-executable instructions, which, when executed, cause the processor to: Receive an account processing request for the target user submitted through the user terminal by the auxiliary user after entering the target user's user identifier on the user selection page; In response to the account processing request, the total number of times the auxiliary user reported loss within a preset time interval is queried in the loss reporting record table and it is verified whether it is less than the first number of loss reporting. If so, the historical loss reporting records of the auxiliary user for the target user are read from the loss reporting record table, and based on the historical loss reporting records, it is determined whether the number of times the auxiliary user reported loss to the target user for the user within the loss reporting time interval corresponding to the account processing request exceeds the second number of loss reporting. If not, check whether the auxiliary user has a lost record marked as abnormal behavior by the target user in the lost record table. If it does, determine that the auxiliary user does not meet the processing conditions and send a verification failure reminder to the user terminal. If not, based on the application interaction records between the auxiliary user and the target user, calculate the intimacy between the auxiliary user and the target user, and determine the verification method corresponding to the intimacy; the intimacy includes the intimacy of the interaction between the auxiliary user and the target user within the application; Based on the identity information of the target user collected by the user terminal according to the verification method, the identity of the target user is verified, and the application account is restricted after the verification is passed. If an abnormal flag request submitted by the target user is detected, the loss behavior flag in the auxiliary loss record in the loss record table is updated to an abnormal flag. The verification method includes the corresponding identifier input verification method when the intimacy is equal to or higher than the intimacy threshold. The account restriction processing includes the account freezing processing of the application account of the target user.

17. An application account processing device, comprising: processor; as well as, A memory configured to store computer-executable instructions, which, when executed, cause the processor to: Based on the account processing instruction for the target user submitted by the assistant user after entering the target user's user identifier on the user selection page, an account processing request for the target user is submitted to the server. If the server determines that the identity verification method is the identifier input verification method, it collects the identifier keywords input by the target user. The verification method is determined based on the intimacy between the auxiliary user and the target user. The identifier input verification method is determined when the intimacy is equal to or greater than the intimacy threshold. The intimacy includes the interaction intimacy between the auxiliary user and the target user within the application. The intimacy is determined by querying the lost and found record table to find that the total number of lost and found attempts by the auxiliary user within a preset time interval is less than the first number of lost and found attempts. The server also reads the historical lost and found records of the auxiliary user against the target user from the lost and found record table. Based on the historical lost and found records, the server determines that the number of lost and found attempts by the auxiliary user against the target user within the lost and found time interval corresponding to the account processing request does not exceed the second number of lost and found attempts. The server calculates the results after confirming that there are no lost and found records in the lost and found record table where the auxiliary user is marked as having abnormal behavior by the target user. If such records exist, the server receives a verification failure notification. The identifier keyword is submitted to the server as identity information to verify the identity of the target user and, after successful verification, to restrict the application account of the target user; the account restriction includes freezing the application account of the target user.

18. A storage medium for storing computer-executable instructions, which, when executed by a processor, perform the following process: Receive an account processing request for the target user submitted through the user terminal by the auxiliary user after entering the target user's user identifier on the user selection page; In response to the account processing request, the total number of times the auxiliary user reported loss within a preset time interval is queried in the loss reporting record table and it is verified whether it is less than the first number of loss reporting. If so, the historical loss reporting records of the auxiliary user for the target user are read from the loss reporting record table, and based on the historical loss reporting records, it is determined whether the number of times the auxiliary user reported loss to the target user for the user within the loss reporting time interval corresponding to the account processing request exceeds the second number of loss reporting. If not, check whether the auxiliary user has a lost record marked as abnormal behavior by the target user in the lost record table. If it does, determine that the auxiliary user does not meet the processing conditions and send a verification failure reminder to the user terminal. If not, based on the application interaction records between the auxiliary user and the target user, calculate the intimacy between the auxiliary user and the target user, and determine the verification method corresponding to the intimacy; the intimacy includes the intimacy of the interaction between the auxiliary user and the target user within the application; Based on the identity information of the target user collected by the user terminal according to the verification method, the identity of the target user is verified, and the application account is restricted after the verification is passed. If an abnormal flag request submitted by the target user is detected, the loss behavior flag in the auxiliary loss record in the loss record table is updated to an abnormal flag. The verification method includes the corresponding identifier input verification method when the intimacy is equal to or higher than the intimacy threshold. The account restriction processing includes the account freezing processing of the application account of the target user.

19. A storage medium for storing computer-executable instructions, which, when executed by a processor, perform the following process: Based on the account processing instruction for the target user submitted by the assistant user after entering the target user's user identifier on the user selection page, an account processing request for the target user is submitted to the server. If the server determines that the identity verification method is the identifier input verification method, it collects the identifier keywords input by the target user. The verification method is determined based on the intimacy between the auxiliary user and the target user. The identifier input verification method is determined when the intimacy is equal to or greater than the intimacy threshold. The intimacy includes the interaction intimacy between the auxiliary user and the target user within the application. The intimacy is determined by querying the lost and found record table to find that the total number of lost and found attempts by the auxiliary user within a preset time interval is less than the first number of lost and found attempts. The server also reads the historical lost and found records of the auxiliary user against the target user from the lost and found record table. Based on the historical lost and found records, the server determines that the number of lost and found attempts by the auxiliary user against the target user within the lost and found time interval corresponding to the account processing request does not exceed the second number of lost and found attempts. The server calculates the results after confirming that there are no lost and found records in the lost and found record table where the auxiliary user is marked as having abnormal behavior by the target user. If such records exist, the server receives a verification failure notification. The identifier keyword is submitted to the server as identity information to verify the identity of the target user and, after successful verification, to restrict the application account of the target user; the account restriction includes freezing the application account of the target user.

Images