A method, device and equipment for removing restrictions on an account

Abstract

The embodiments of the present specification disclose a method, apparatus and device for removing restrictions from an account, the method comprising: receiving a restriction removal request for a target account sent by a target terminal, the restriction removal request comprising information of the target account and information of a preset number of user accounts having a specified association relationship with the target account, then generating an account assistance restriction removal notification based on the restriction removal request, and sending the account assistance restriction removal notification to the preset number of user accounts respectively, receiving feedback messages from the preset number of user accounts regarding the account assistance restriction removal notification respectively, and determining whether to remove the account authority restriction corresponding to the restriction removal request for the target account based on the feedback messages.

Description

Technical Field

[0001] This document relates to the field of computer technology, and in particular to a method, device and equipment for removing restrictions on an account. Background Art

[0002] As the risk of telecommunications network fraud becomes more and more serious, the fraud risk control capabilities of many financial institutions are also constantly improving. Usually, the average number of accounts that are audited for fraud risk and restricted can reach nearly 10,000 per day. However, the account unrestriction mechanism often has a low threshold and a low accuracy rate. Often, after the control is unrestricted, a certain number of accounts successfully initiate fraudulent behavior, but the risk prevention fails. The current control mechanism (including restrictions on collection, prohibition of resource withdrawal, permanent or temporary penalty mechanism, etc.) is diverse and flexible, while the relative unrestriction mechanism is relatively single. Multiple different risk types often share a set of unrestriction mechanisms (such as unrestriction mechanisms through face verification, unrestriction mechanisms for uploading handheld commitment letters, unrestriction mechanisms for uploading images of identity documents, unrestriction mechanisms for uploading images of business licenses, or unrestriction mechanisms for uploading transaction vouchers, etc.), which makes the account unrestriction flexibility poor and the unrestriction mechanism weak in differentiation. Therefore, it is necessary to provide an account unrestriction mechanism with better flexibility and stronger differentiation. Summary of the invention

[0003] The purpose of the embodiments of this specification is to provide an account release mechanism with better flexibility and stronger differentiation.

[0004] In order to implement the above technical solution, the embodiments of this specification are implemented as follows:

[0005] An embodiment of the present specification provides a method for removing restrictions on an account, the method comprising: receiving a restriction removal request for a target account sent by a target terminal, the restriction removal request including information of the target account and information of a preset number of user accounts that have a specified association relationship with the target account. Based on the restriction removal request, an account assistance restriction removal notification is generated, and the account assistance restriction removal notification is sent to the preset number of user accounts respectively. Feedback messages from the preset number of user accounts regarding the account assistance restriction removal notification are received respectively, and based on the feedback messages, it is determined whether to remove the account authority restriction corresponding to the restriction removal request for the target account.

[0006] An account unrestriction method provided in an embodiment of the present specification is applied to a blockchain system, the method comprising: obtaining an account unrestriction rule for unrestricting a preset account authority restriction on an account, generating a corresponding first smart contract based on the account unrestriction rule, and deploying the first smart contract in the blockchain system. A target account unrestriction request sent by a target terminal is received, the unrestriction request including information of the target account and information of a preset number of user accounts that have a specified association relationship with the target account. Based on the first smart contract, an account assistance unrestriction notification is generated through the unrestriction request, and the account assistance unrestriction notification is sent to the preset number of user accounts respectively. Based on the first smart contract, feedback messages for the account assistance unrestriction notification are obtained from the preset number of user accounts respectively, and through the feedback messages, it is determined whether to unrestrict the account authority restriction corresponding to the unrestriction request for the target account.

[0007] An embodiment of the present specification provides a device for removing restrictions from an account, the device comprising: a restriction removal request module, which receives a restriction removal request from a target account sent by a target terminal, wherein the restriction removal request includes information about the target account and information about a preset number of user accounts that have a specified association relationship with the target account. An assistance restriction removal notification module, which generates an account assistance restriction removal notification based on the restriction removal request, and sends the account assistance restriction removal notification to the preset number of user accounts respectively. A restriction removal module, which receives feedback messages from the preset number of user accounts regarding the account assistance restriction removal notification respectively, and determines whether to remove the account authority restriction corresponding to the restriction removal request for the target account based on the feedback messages.

[0008] The embodiment of this specification provides an account unrestriction device, the device is a device in a blockchain system, and the device includes: a first contract deployment module, which obtains an account unrestriction rule for removing preset account authority restrictions from an account, and generates a corresponding first smart contract based on the account unrestriction rule, and deploys the first smart contract in the blockchain system. A request receiving module, which receives a target account unrestriction request sent by a target terminal, wherein the unrestriction request includes information about the target account and information about a preset number of user accounts that have a specified association relationship with the target account. A notification module, which generates an account assistance unrestriction notification through the unrestriction request based on the first smart contract, and sends the account assistance unrestriction notification to the preset number of user accounts respectively. A restriction unrestriction module, which obtains feedback messages for the account assistance unrestriction notification from the preset number of user accounts based on the first smart contract, and determines whether to remove the account authority restrictions corresponding to the unrestriction request from the target account through the feedback message.

[0009] An account unrestriction device provided in an embodiment of the present specification includes: a processor; and a memory arranged to store computer executable instructions, wherein when the executable instructions are executed, the processor: receives a target account unrestriction request sent by a target terminal, wherein the unrestriction request includes information of the target account and information of a preset number of user accounts that have a specified association relationship with the target account. Generate an account assistance unrestriction notification based on the unrestriction request, and send the account assistance unrestriction notification to the preset number of user accounts respectively. Receive feedback messages from the preset number of user accounts regarding the account assistance unrestriction notification respectively, and determine whether to remove the account authority restriction corresponding to the unrestriction request for the target account based on the feedback messages.

[0010] An account unrestriction device provided in an embodiment of the present specification is a device in a blockchain system, and the device includes: a processor; and a memory arranged to store computer executable instructions, wherein the executable instructions, when executed, cause the processor to: obtain an account unrestriction rule for unrestricting a preset account authority restriction on an account, and generate a corresponding first smart contract based on the account unrestriction rule, and deploy the first smart contract in the blockchain system. A target account unrestriction request sent by a target terminal is received, wherein the unrestriction request includes information about the target account and information about a preset number of user accounts that have a specified association relationship with the target account. Based on the first smart contract, an account assistance unrestriction notification is generated through the unrestriction request, and the account assistance unrestriction notification is sent to the preset number of user accounts respectively. Based on the first smart contract, feedback messages for the account assistance unrestriction notification are obtained from the preset number of user accounts respectively, and through the feedback message, it is determined whether to unrestrict the account authority restriction corresponding to the unrestriction request for the target account.

[0011] The embodiments of this specification also provide a storage medium, wherein the storage medium is used to store computer executable instructions, and the executable instructions implement the following process when executed: receiving a restriction release request for a target account sent by a target terminal, wherein the restriction release request includes information of the target account and information of a preset number of user accounts that have a specified association relationship with the target account. Based on the restriction release request, an account assistance restriction release notification is generated, and the account assistance restriction release notification is sent to the preset number of user accounts respectively. Feedback messages from the preset number of user accounts regarding the account assistance restriction release notification are received respectively, and based on the feedback messages, it is determined whether to release the account authority restriction corresponding to the restriction release request for the target account.

[0012] The embodiment of the present specification also provides a storage medium, wherein the storage medium is used to store computer executable instructions, and the executable instructions implement the following process when executed: obtain an account unrestriction rule for removing preset account authority restrictions from an account, and generate a corresponding first smart contract based on the account unrestriction rule, and deploy the first smart contract in the blockchain system. Receive a restriction removal request for a target account sent by a target terminal, wherein the restriction removal request includes information about the target account and information about a preset number of user accounts that have a specified association relationship with the target account. Based on the first smart contract, generate an account assistance restriction removal notification through the restriction removal request, and send the account assistance restriction removal notification to the preset number of user accounts respectively. Based on the first smart contract, obtain feedback messages for the account assistance restriction removal notification from the preset number of user accounts respectively, and determine whether to remove the account authority restrictions corresponding to the restriction removal request from the target account through the feedback message. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] In order to more clearly illustrate the embodiments of this specification or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0014] Figure 1A This is an example of an account unblocking method in this specification;

[0015] Figure 1B This is a schematic diagram of the unblocking process of an account in this manual;

[0016] Figure 2 This is a service reminder diagram for an account unblocking process in this manual;

[0017] Figure 3 This is a schematic diagram of an account assistance unblocking notification in an account unblocking process in this manual;

[0018] Figure 4 This is a schematic diagram of the unblocking process of another account in this manual;

[0019] Figure 5 This is another service reminder diagram for account unblocking in this manual;

[0020] Figure 6 This is a schematic diagram of the address book in the account unlocking process of this manual;

[0021] Figure 7 This is another service reminder diagram for account unblocking in this manual;

[0022] Fig. 8A This is another example of an account unblocking method in this specification;

[0023] Figure 8B This is another schematic diagram of the account unblocking process in this manual;

[0024] Fig. 9 This is another schematic diagram of the account unblocking process in this manual;

[0025] Fig.10 This is an embodiment of an account unblocking device of this specification;

[0026] Fig.11 This is another embodiment of the account unblocking device of this specification;

[0027] Fig.12 This is an example of an account unlocking device in this specification. DETAILED DESCRIPTION

[0028] The embodiments of this specification provide a method, device and apparatus for removing restrictions on an account.

[0029] In order to enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the drawings in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this specification.

[0030] Embodiment 1

[0031] like Figure 1A and Figure 1B As shown, the embodiment of this specification provides a method for removing restrictions on an account. The execution subject of the method may be a server, wherein the server may be a server for a certain business (such as a business for conducting transactions or a financial business, etc.). Specifically, the server may be a server for a payment business, or a server for a business related to finance or instant messaging, etc. The method may specifically include the following steps:

[0032] In step S102, a target account unrestriction request sent by a target terminal is received, where the target account unrestriction request includes information of the target account and information of a preset number of user accounts that have a specified association relationship with the target account.

[0033] Among them, the target terminal can be any terminal device, such as a mobile terminal device such as a mobile phone or a tablet computer, or a terminal device such as a personal computer or a laptop computer. The target account can be any account. In actual applications, it can be a corresponding account created for a certain business or multiple different businesses. Each account can have corresponding account permissions, and different accounts can have different account permissions. For example, the account of user 1 has an account permission of a single transfer of up to 500,000 yuan and a daily transfer of up to 1 million yuan, and the account of user 2 has an account permission of a single transfer of up to 50,000 yuan and a daily transfer of up to 500,000 yuan, etc. In addition, depending on the business, the corresponding account permissions may also be different. The information of the target account may include the identification of the target account, the usage status of the target account, the probability of the target account having risks, the relevant information of the user corresponding to the target account (such as the user's name, ID number, etc.), etc., which can be set according to the actual situation, and the embodiments of this specification do not limit this. The specified association relationship can be any specified association relationship, such as a friend relationship, a colleague relationship, etc. In actual applications, the specified association relationship can include one association relationship, or multiple different association relationships, which can be set according to the actual situation, and the embodiments of this specification do not limit this. The preset number can be set according to actual conditions, such as 3, 5 or 7.

[0034] In practice, as the risk of telecommunications network fraud becomes more and more severe, the fraud risk control capabilities of many financial institutions are also constantly improving. Usually, the average daily number of accounts that are audited for fraud risk and restricted can reach nearly 10,000. However, the account unrestriction mechanism often has a low threshold and a low accuracy rate. There are often a certain number of accounts that successfully initiate fraud after the control is unrestricted, but the risk prevention fails. The current control mechanism (including restrictions on collection, prohibition of resource withdrawal, permanent or temporary penalty mechanisms, etc.) is diverse and flexible, while the relative unrestriction mechanism is relatively single. A variety of different risk types often share a set of unrestriction mechanisms (for example, an unrestriction mechanism through face verification, an unrestriction mechanism for uploading a handheld commitment letter, an unrestriction mechanism for uploading an image of an identity document, an unrestriction mechanism for uploading an image of a business license, or an unrestriction mechanism for uploading a transaction voucher, etc.), which makes the account unrestriction flexibility poor and the unrestriction mechanism weak in differentiation. For this reason, it is necessary to provide an account unrestriction mechanism with better flexibility and higher differentiation. The embodiments of this specification provide an achievable technical solution, which may specifically include the following contents:

[0035] The target terminal may be installed with an application for executing a certain business. The user of the target terminal may register a corresponding account (i.e., the target account) in advance through the above application in the target terminal, and the user may use the target account to request the above corresponding business. In the process of using the target account to execute the corresponding business, the user may be captured by the risk control mechanism of the business due to misoperation, certain irregular operating behaviors, or being reported (or complained) by others. In order to protect the security of the user's target account, the risk control mechanism usually restricts the account permissions of the target account, for example, prohibiting the target account from initiating a certain business or business request, etc. At the same time, the application will receive a penalty notice from the target account, for example, Figure 2 As shown in FIG. 1 , the target account is restricted because of a complaint by others regarding fraud in the target account. If the user needs to use the restricted account rights in the target account, the target account can be unrestricted. Specifically, the application can be provided with an entry for unrestricting the account rights of the target account (such as a trigger button, an unrestricting link, or a Figure 2 "View details" etc. shown in the figure), the user can trigger the application through the above-mentioned restriction removal entrance to provide the user with a restriction removal application page, and the restriction removal application page may include an information input box and / or an information selection box, etc. The user can enter the corresponding information in the information input box and / or select the corresponding information in the information selection box in the restriction removal application page, and the information of the target account and the information of a preset number of user accounts that have a specified association relationship with the target account can be obtained through the input and / or selected information. After the user completes the input and selection, the user can click the restriction removal button in the restriction removal application page. At this time, the target terminal can obtain the information of the above-mentioned target account and the information of the preset number of user accounts that have a specified association relationship with the target account, and can generate a restriction removal request through the above-mentioned obtained information, and can send the restriction removal request to the server, so that the server can receive the restriction removal request for the target account sent by the target terminal.

[0036] In step S104, an account assistance unblocking notification is generated based on the unblocking request, and the account assistance unblocking notification is sent to a preset number of user accounts respectively.

[0037] The account assistance unrestriction notification may be a notification message used to assist in unrestricting the account permissions of a certain account. The account assistance unrestriction notification may include an address or operation steps for assisting in unrestriction, for example, Figure 3 As shown, the account assistance unblocking notification includes information such as the address of assistance unblocking, which can be set according to actual conditions, and the embodiments of this specification do not limit this.

[0038] During implementation, when a request for unblocking a target account sent by a target terminal is received, the request for unblocking can be analyzed, and information of the target account and information of a preset number of user accounts that have a specified association with the target account can be extracted therefrom. An account assistance unblocking notification can be generated using the information of the target account and the information of a certain user account, and the account assistance unblocking notification can be sent to the above-mentioned user account. At the same time, an account assistance unblocking notification can be generated again using the information of the target account and the information of another user account, and the account assistance unblocking notification is sent to the user account. In this way, each user account in the preset number of user accounts can correspond to an account assistance unblocking notification, so as to request each user account to assist the target account in unblocking.

[0039] In step S106, feedback messages from a preset number of user accounts regarding the account assistance unblocking notification are received respectively, and based on the feedback messages, it is determined whether to release the account authority restriction corresponding to the unblocking request for the target account.

[0040] In implementation, each user account among a preset number of user accounts can receive an account assistance unblocking notification for the target account. The user corresponding to each user account can view the specific content of the account assistance unblocking notification, and can determine whether it is possible to assist the target account in unblocking based on the specific content. For example, the user corresponding to the user account can determine whether there is an association between the user and the user corresponding to the target account based on the information of the target account in the specific content, and determine whether the unblocking request is a real request made by the user corresponding to the target account. If so, feedback can be given to the account assistance unblocking notification, that is, the user corresponding to the user account agrees to assist the target account in unblocking, and can perform corresponding assistance unblocking operations. After the operation is completed, the terminal device corresponding to the user account can send corresponding feedback information to the server. In the above manner, each user account can perform the above operations. Finally, each user account can send corresponding feedback information to the server.

[0041] Based on the feedback message, it can be determined whether to lift the account authority restriction corresponding to the above-mentioned restriction removal request for the target account. The specific processing may include a variety of different methods. For example, if the feedback information of each user account among the preset number of user accounts indicates that the target account is assisted in removing the restriction, and the user corresponding to each user account has completed the corresponding restriction removal operation, then it can be determined that the account authority restriction corresponding to the above-mentioned restriction removal request can be lifted for the target account, and the target account can be removed. Otherwise, the target account can be refused to be removed. Or, if the feedback information of some user accounts among the preset number of user accounts indicates that the target account is assisted in removing the restriction, the number of some user accounts reaches a preset number threshold, and the users corresponding to some user accounts have completed the corresponding restriction removal operation, then it can be determined that the account authority restriction corresponding to the above-mentioned restriction removal request can be lifted for the target account, and the target account can be removed. Otherwise, the target account can be refused to be removed. In addition to the above-mentioned implementation method, it can also be implemented in a variety of other different ways, which can be set specifically according to actual conditions, and the embodiments of this specification do not limit this.

[0042] The embodiments of the present specification provide a method for removing restrictions from an account, receiving a restriction removal request for a target account sent by a target terminal, wherein the restriction removal request includes information of the target account and information of a preset number of user accounts that have a specified association relationship with the target account, then generating an account assistance restriction removal notification based on the restriction removal request, and sending the account assistance restriction removal notification to the preset number of user accounts respectively, and then respectively receiving feedback messages from the preset number of user accounts regarding the account assistance restriction removal notification, and determining whether to remove the account authority restriction corresponding to the restriction removal request for the target account based on the feedback messages, since it is difficult to forge a user account that has an association relationship with the target account, the discrimination of the restriction removal scheme can be enhanced, and for a normal account, the restriction removal scheme is made simpler and more effective by assisting in the restriction removal with the assistance of the user account that has an association relationship with the target account, but the scheme becomes difficult to implement for an abnormal account, and in addition, the qualification conditions required for restriction removal can also be individually configured, thereby making the account restriction removal more flexible.

[0043] Embodiment 2

[0044] like Figure 4 As shown, the embodiment of this specification provides a method for removing restrictions on an account. The execution subject of the method may be a server, wherein the server may be a server for a certain business (such as a business for conducting transactions or a financial business, etc.). Specifically, the server may be a server for a payment business, or a server for a business related to finance or instant messaging, etc. The method may specifically include the following steps:

[0045] In step S402, a target account unrestriction request sent by a target terminal is received, where the target account unrestriction request includes information of the target account and information of a preset number of user accounts that have a specified association relationship with the target account.

[0046] In implementation, Figure 2 As shown in the figure, the user can click "View Details" and the target terminal can obtain the following information: Figure 5 The service reminder page shown in the figure may include "Please find 3 friends to guarantee that the account is used by you and there is no risk of fraud". After the user of the target terminal views the above service reminder page, he can click "Find friends". At this time, Figure 6 As shown, the target terminal can obtain the address book of the target account and can display the identifier of the user account in the address book (such as Figure 6 The user of the target terminal can select a preset number (3 in this example) of identifiers from the above user account identifiers, and the user account corresponding to the identifier selected by the user can be used as the preset number of user accounts that have a specified association relationship with the target account. After the selection is completed, you can click the OK button. At this time, the target terminal can obtain the information of the target account and the information of the preset number of user accounts that have a specified association relationship with the target account, and can generate a target account unblocking request based on the above information obtained, and can send the target account unblocking request to the server.

[0047] In practical applications, in order to ensure the efficiency and security of unblocking, the selection of target accounts can be limited. An optional processing method is provided below, which may specifically include the following: the target account is an account that meets the preset conditions, and the preset conditions may include one or more of the following: an association relationship intimacy condition used to characterize the degree of intimacy with the target account, a security condition and an activity condition used to characterize the security behavior of the user account, etc.

[0048] Among them, the intimacy condition of the association relationship can be, for example, the intimacy between the target account and the user account is greater than a preset intimacy threshold, and the security condition can be, for example, the security level of the user account is greater than a preset security threshold, and the security level of the target account can be obtained after quantifying the security behavior of the user account. The security behavior may include, for example, whether the user's login location is a common location, whether the login time is a common time period, whether the user has been reported or complained about, whether the association relationship has been removed by a certain number of other accounts within a preset time period, whether there are large differences in business data within a preset time period, etc., which can be set specifically according to actual conditions.

[0049] In implementation, user accounts that are associated with the target account can be screened based on one or more of the above conditions to select user accounts that meet the above conditions. Then, the user corresponding to the target account can select a preset number of user accounts from them, and a release request can be generated based on the information of the selected preset number of user accounts and the information of the target account and sent to the server.

[0050] In actual applications, the closeness of the relationship between the target account and the user account, the security level of the target account, and the activity level of the user account can also be weighted and summed to obtain a corresponding weighted value. User accounts with weighted values ​​greater than a preset threshold can be obtained for selection by the user corresponding to the target account.

[0051] In step S404, an account assistance unblocking notification is generated based on the unblocking request, and the account assistance unblocking notification is sent to a preset number of user accounts respectively.

[0052] Among them, the account assistance unblocking notification may include the information of the target account and the operation guidance information. The operation guidance information is used to guide the user of the user account to guarantee the target account for unblocking. The operation guidance information may include one or more, that is, the operation guidance information can be recorded on the homepage where the account assistance unblocking notification is located, or it can be distributed in multiple different pages, which can be set according to actual conditions.

[0053] In implementation, Figure 3 As shown, the server can generate an account assistance unblocking notification and send it to each user account. After the user account receives the account assistance unblocking notification, the terminal device corresponding to the user account can display the account assistance unblocking notification (such as Figure 3 "Hi, xxx, your friend xxx is appealing and requesting your help. Please confirm your friend's identity and perform the following operations http: / / xxxxxxx"). The user corresponding to the user account can click the above link. Figure 7 As shown, the server can send a service reminder page to the terminal device corresponding to the user account, and the page can include guarantee content, a reject button and an agree button.

[0054] In step S406, feedback messages from a preset number of user accounts regarding the account assistance unblocking notification are received respectively.

[0055] In implementation, Figure 7As shown, after the user corresponding to the user account views the above service reminder page, if he agrees to the guarantee, he can click the "Agree" button; if he disagrees to the guarantee, he can click the "Reject" button. After the user clicks the "Agree" button or the "Reject" button, the terminal device corresponding to the user account can generate a corresponding feedback message for the above account assistance release notification, and can send the feedback message to the server, so that the server can receive a preset number of feedback messages from user accounts for the above account assistance release notification.

[0056] In addition, the server may also send the feedback message to the target account so that the user corresponding to the target account can timely understand the progress of the target account's unblocking.

[0057] In step S408, if the feedback messages from the preset number of user accounts exceeding the preset threshold number indicate that the target account for unblocking is guaranteed, the account authority restriction corresponding to the unblocking request is released for the target account.

[0058] The preset threshold number can be set according to the actual situation. For example, the preset number can be 3, the preset threshold number can also be 3, or the preset number can be 5, the preset threshold number can also be 4 or 3, etc., which can be set according to the actual situation. The account authority restrictions corresponding to the release request may include one or more of the following: restrictions on the number of resource collections (such as restrictions on collection), restrictions on the number of resource extractions (such as prohibition of physical withdrawals), long-term restrictions on the account authority of the target account, or temporary restrictions on the account authority of the target account.

[0059] As time goes by, a large amount of account release relationship data (or it can be called guarantee relationship data) can be obtained through the above method. Other related applications can also be performed on the above release relationship data. An optional application method is provided below. For details, please refer to the processing of wiring harness steps S410 to S414.

[0060] In step S410, information of one or more different first accounts and information of a second account that guarantees each of the first accounts are obtained.

[0061] Among them, one or more different first accounts may include the above-mentioned target account, or may not include the target account, which can be specifically set according to actual conditions.

[0062] In implementation, for the examples in the above steps S402 to S408, if the target account is included in one or more different first accounts, and the three user accounts selected by the user corresponding to the target account in the above example all agree to guarantee the release of the target account, then the target account can be obtained as the first account, and at the same time, the three user accounts selected above can be obtained as the second account to guarantee the target account for release. In the above manner, each first account and the second account to guarantee the release of each first account can be obtained.

[0063] In step S412, a corresponding knowledge graph is constructed based on the information of the first account and the information of the second account, and a risk subgraph with preset risks contained in the knowledge graph is determined.

[0064] Among them, the preset risk can be any risk, such as fraud risk, money laundering risk, etc., which can be set according to actual conditions, and the embodiments of this specification do not limit this.

[0065] In implementation, one or more different first accounts can be obtained through the above method, and each first account can correspond to one or more different second accounts, thereby forming account release relationship data. In order to more intuitively represent the above account release relationship data, the above relationship data can be displayed in the form of a knowledge graph. Specifically, the first account and the second account can be used as nodes in the knowledge graph, and the release relationship (or guarantee relationship) between the accounts can be used as an edge in the knowledge graph, so that the corresponding knowledge graph can be constructed based on the above account release relationship data.

[0066] The knowledge graph obtained above can be analyzed to determine whether there are accounts of risk organizations (or risk groups, such as fraud groups) in the current account. Specifically, accounts with certain risks can be determined based on historical reports or historical complaint data, or currently existing user accounts can be tested through preset risk prevention and control rules to determine accounts with certain risks contained therein, or accounts with certain risks can be determined through other methods. Then, based on the accounts with certain risks determined above and the release relationship (or guarantee relationship) presented in the above knowledge graph, accounts associated with the determined accounts with certain risks can be determined, and then the accounts of risk organizations (or risk groups, such as fraud groups) contained therein can be determined, thereby obtaining a risk subgraph with preset risks contained in the knowledge graph, and determining the corresponding risk organizations (or risk groups).

[0067] In step S414, risk prevention and control processing is performed on the businesses corresponding to the first account and the second account based on the account information included in the risk subgraph.

[0068] In addition, in addition to using the above account release relationship data to determine risk organizations (or risk groups) and then conduct risk prevention and control, the above account release relationship data can also have other application methods. The following provides two optional application methods, which may include:

[0069] Method 1: Set risk control rules based on account release relationship data, such as:

[0070] 1. Assist in unblocking. If the user account of the account initiating the unblocking is detected to have a certain risk, the unblocking initiating account will be restricted in the reverse direction. That is, if an account with a preset risk is detected in the second account, the preset account permissions of the first account corresponding to the detected account will be increased with restrictions that comply with the first preset restriction rules.

[0071] The first preset authority restriction rule may be set according to actual conditions, for example, adding the same account authority restriction as that of the second account to the corresponding first account.

[0072] 2. If the account initiating the restriction is detected to have a certain risk multiple times, the user account of the account initiating the restriction will be restricted to assist in removing the restriction. That is, if the number of times the first account is detected to be an account with risk exceeds the preset number threshold, restrictions that comply with the second preset restriction rules will be added to the second account.

[0073] Among them, the second preset limitation rule can be set according to the actual situation, for example, adding a restriction on prohibiting the second account from receiving money or limiting the amount of money received to not exceed a preset value (such as 10,000 yuan, etc.).

[0074] 3. If the number of times a user account guarantees other accounts for unblocking exceeds a preset guarantee threshold (such as 3 times or 5 times, etc.), the unblocking qualification or unblocking authority of the user account will be cancelled. Based on this, the processing of the following steps A2 and A4 may be included.

[0075] In step A2, the number of times each user account in a preset number of user accounts guarantees other accounts is obtained.

[0076] In step A4, if there is a user account among the preset number of user accounts that has guaranteed other unrestricted accounts more than the preset guarantee number threshold, a user account modification notification is sent to the target terminal, so that the target terminal re-selects a preset number of user accounts that have a specified association relationship with the target account based on the modification notification.

[0077] During implementation, if there is a user account among the preset number of user accounts that has guaranteed other accounts more times than the preset guarantee number threshold, a user account modification notification is sent to the target terminal, and the modification notification may include information on the user account that has guaranteed more than the preset guarantee number threshold, so that the user can change the above-mentioned user account.

[0078] Method 2: Set account unblocking rules based on account unblocking relationship data, such as:

[0079] 1. If the user account of the account initiating the unblocking is detected to have a certain risk, it is necessary to unblock again. Based on this, if the user account of the account initiating the unblocking is detected to have a certain risk, a modification notification of the user account is sent to the target terminal, so that the target terminal re-selects a preset number of user accounts that have a specified association relationship with the target account based on the modification notification.

[0080] 2. If the account initiating the lifting of restrictions is detected to have a certain risk multiple times, it is necessary to re-determine the user account that assists in lifting the restrictions of the account initiating the lifting of restrictions. Based on this, if the user account is detected to have a certain risk multiple times, a modification notification of the user account is sent to the target terminal, so that the target terminal re-selects a preset number of user accounts that have a specified association relationship with the target account based on the modification notification.

[0081] 3. If the account initiating the unblocking is detected to have a certain risk, the user account that meets the specified requirements needs to be unblocked. Based on this, if the target account is an account with a preset risk, the preset number of user accounts with a specified association relationship with the target account includes at least one or more user accounts whose duration exceeds the preset duration threshold (such as one or two years, etc.).

[0082] The embodiments of the present specification provide a method for removing restrictions from an account, receiving a restriction removal request for a target account sent by a target terminal, wherein the restriction removal request includes information of the target account and information of a preset number of user accounts that have a specified association relationship with the target account, then generating an account assistance restriction removal notification based on the restriction removal request, and sending the account assistance restriction removal notification to the preset number of user accounts respectively, and then respectively receiving feedback messages from the preset number of user accounts regarding the account assistance restriction removal notification, and determining whether to remove the account authority restriction corresponding to the restriction removal request for the target account based on the feedback messages, since it is difficult to forge a user account that has an association relationship with the target account, the discrimination of the restriction removal scheme can be enhanced, and for a normal account, the restriction removal scheme is made simpler and more effective by assisting in the restriction removal with the assistance of the user account that has an association relationship with the target account, but the scheme becomes difficult to implement for an abnormal account, and in addition, the qualification conditions required for restriction removal can also be individually configured, thereby making the account restriction removal more flexible.

[0083] Moreover, by assisting in the removal of restrictions and expanding the relationship data of the target accounts, the value of the data related to the removal of restrictions can be increased, and the above-mentioned data related to the removal of restrictions can be used for risk prevention and control and other processing.

[0084] Embodiment 3

[0085] like Fig. 8A and Figure 8B As shown, the embodiment of this specification provides a method for removing restrictions on an account. The execution subject of the method can be a blockchain system, and the blockchain system can be composed of terminal devices or servers, etc., wherein the terminal device can be a mobile terminal device such as a mobile phone, a tablet computer, or a device such as a personal computer. The server can be an independent server or a server cluster composed of multiple servers. The method can specifically include the following steps:

[0086] In step S802, an account release rule for releasing preset account authority restrictions on an account is obtained, and a corresponding first smart contract is generated based on the account release rule, and the first smart contract is deployed in the blockchain system.

[0087] Among them, the first smart contract can be a computer protocol designed to disseminate, verify or execute a contract in an information-based manner. The first smart contract allows trusted interaction without a third party, and the above-mentioned interaction process is traceable and irreversible. The first smart contract includes an agreement on which the contract participants can execute the rights and obligations agreed upon by the contract participants.

[0088] In implementation, in order to make the traceability of account unrestriction better, a designated blockchain system can be created or added, so that a certain account authority restriction can be removed based on the blockchain system. Specifically, a corresponding application can be installed in the blockchain node, and the application can be provided with an input box and / or a selection box for the account unrestriction rule for removing the preset account authority restriction from the account, and the corresponding information can be set in the above input box and / or selection box. Then, the blockchain system can receive the account unrestriction rule for removing the preset account authority restriction from the account. The blockchain system can generate a corresponding first smart contract based on the account unrestriction rule for removing the preset account authority restriction from the account, and can deploy the first smart contract to the blockchain system. In this way, the blockchain system stores the account unrestriction rule and the corresponding smart contract for removing the preset account authority restriction from the account, and other users cannot tamper with the account unrestriction rule and the corresponding smart contract. Moreover, the blockchain system unrestricts a certain account through the first smart contract.

[0089] In step S804, a target account unrestriction request sent by a target terminal is received, where the target account unrestriction request includes information of the target account and information of a preset number of user accounts that have a specified association relationship with the target account.

[0090] In step S806, based on the first smart contract, an account assistance unblocking notification is generated through the unblocking request, and the account assistance unblocking notification is sent to a preset number of user accounts respectively.

[0091] In implementation, the first smart contract may include rule information for generating an account assistance unblocking notification and further processing the account assistance unblocking notification. The account assistance unblocking notification may be generated based on the unblocking request, and the account assistance unblocking notification may be sent to a preset number of user accounts respectively. For details, please refer to the above-mentioned related content, which will not be repeated here.

[0092] In step S808, based on the first smart contract, feedback messages for the account assistance release notification are obtained from a preset number of user accounts respectively, and through the feedback messages, it is determined whether to release the account authority restriction corresponding to the above release request for the target account.

[0093] In implementation, the first smart contract may include rule information for determining whether to lift the account authority restriction corresponding to the above-mentioned release request for the target account based on the feedback message. For details, please refer to the above-mentioned relevant content and will not be repeated here.

[0094] The embodiment of the present specification provides a method for removing restrictions on an account, which is applied to a blockchain system. A corresponding first smart contract is generated based on an acquired account removal rule, and the first smart contract is deployed in the blockchain system. When a restriction removal request of a target account sent by a target terminal is received, an account assistance restriction removal notification is generated through the restriction removal request based on the first smart contract. The restriction removal request includes information of the target account and information of a preset number of user accounts that have a specified association relationship with the target account. The account assistance restriction removal notification is sent to the preset number of user accounts respectively. Feedback messages for the account assistance restriction removal notification are obtained from the preset number of user accounts respectively based on the first smart contract, and it is determined whether to remove the account authority restriction corresponding to the restriction removal request from the target account through the feedback message. Since it is difficult to forge a user account that has an association relationship with the target account, the discrimination of the restriction removal scheme can be enhanced. For a normal account, the restriction removal is assisted by the user account that has an association relationship with the target account, so that the restriction removal scheme is simpler and more effective, but the scheme becomes difficult to implement for an abnormal account. In addition, the qualification conditions required for restriction removal can also be personalized, so that the flexibility of account restriction removal is higher.

[0095] In addition, the use of blockchain systems and smart contracts to unlock accounts can make the data processing process safer, ensure data security, and have strong traceability of data processing.

[0096] Embodiment 4

[0097] like Fig. 9 As shown, the embodiment of this specification provides a method for removing restrictions on an account. The execution subject of the method can be a blockchain system, and the blockchain system can be composed of terminal devices or servers, etc., wherein the terminal device can be a mobile terminal device such as a mobile phone, a tablet computer, or a device such as a personal computer. The server can be an independent server or a server cluster composed of multiple servers. The method can specifically include the following steps:

[0098] In step S902, an account release rule for releasing preset account authority restrictions on an account is obtained, and a corresponding first smart contract is generated based on the account release rule, and the first smart contract is deployed in the blockchain system.

[0099] Among them, the target account is an account that meets the preset conditions, and the preset conditions include one or more of the following: an association relationship intimacy condition used to characterize the degree of intimacy between the account and the target account, a security condition and an activity condition used to characterize the security behavior of the user account.

[0100] In step S904, a target account unrestriction request sent by a target terminal is received, where the target account unrestriction request includes information about the target account and information about a preset number of user accounts that have a specified association relationship with the target account.

[0101] In step S906, based on the first smart contract, an account assistance unblocking notification is generated through the unblocking request, and the account assistance unblocking notification is sent to a preset number of user accounts respectively.

[0102] In step S908, based on the first smart contract, feedback messages for the account assistance release notification are obtained from a preset number of user accounts respectively, and through the feedback messages, it is determined whether to release the account authority restriction corresponding to the above release request for the target account.

[0103] Among them, the account authority restrictions corresponding to the release request may include one or more of the following: restrictions on the number of resource collection, restrictions on the number of resource extraction, long-term restrictions on the account authority of the target account, or temporary restrictions on the account authority of the target account.

[0104] As time goes by, a large amount of account release relationship data (or it can be called guarantee relationship data) can be obtained through the above method. Other related applications can also be performed on the above release relationship data. An optional application method is provided below. For details, please refer to the processing of wiring harness steps S910 to S916.

[0105] In step S910, rule information for risk prevention and control of preset business is obtained, and a corresponding second smart contract is generated based on the rule information, and the second smart contract is deployed in the blockchain system.

[0106] Among them, the rule information for risk prevention and control of preset businesses may include building a corresponding knowledge graph based on corresponding account information and account release relationship data, and then determining the rule information of the risk subgraph with preset risks contained therein.

[0107] In step S912, information of one or more different first accounts and information of a second account that guarantees each of the first accounts are obtained based on the second smart contract.

[0108] In step S914, based on the second smart contract, a corresponding knowledge graph is constructed through the information of the first account and the information of the second account, and a risk subgraph with preset risks contained in the knowledge graph is determined.

[0109] In step S916, based on the account information and the second smart contract included in the risk subgraph, risk prevention and control processing is performed on the businesses corresponding to the first account and the second account.

[0110] In implementation, when the processing of the business initiated by a certain account is received, the relevant information of the account can be obtained, and based on the relevant information of the account, combined with the account information contained in the above-mentioned risk subgraph and the second smart contract, it can be detected whether there is a risk in the business processing. If there is a risk, the account can be refused to execute the business, etc. The specific setting can be based on actual conditions, and the embodiments of this specification are not limited to this.

[0111] In addition, considering that the risk subgraph with preset risks may be constantly changing (for example, the nodes in the risk subgraph may increase or decrease within a certain period of time), the smart contract in the blockchain system for risk prevention and control of preset businesses can be updated regularly or irregularly, and the determination and processing of the risk subgraph with preset risks is set in a device outside the blockchain system. Specifically, it may include the following contents: obtaining information of the risk subgraph with preset risks, and based on the third smart contract pre-deployed in the blockchain system, generating a fourth smart contract for risk prevention and control of preset businesses through the information of the risk subgraph with preset risks, and deploying the fourth smart contract in the blockchain system. The risk subgraph is determined based on the corresponding knowledge graph constructed based on the information of one or more different first accounts and the information of the second account that guarantees the release of each first account.

[0112] In actual applications, whenever a preset cycle is reached, information of a risk subgraph with preset risks can be obtained and used for subsequent processing. Alternatively, information of a risk subgraph with preset risks can be obtained irregularly and used for subsequent processing. The specific setting can be based on actual conditions, and the embodiments of this specification do not limit this.

[0113] The embodiment of the present specification provides a method for removing restrictions on an account, which is applied to a blockchain system. A corresponding first smart contract is generated based on an acquired account removal rule, and the first smart contract is deployed in the blockchain system. When a restriction removal request of a target account sent by a target terminal is received, an account assistance restriction removal notification is generated through the restriction removal request based on the first smart contract. The restriction removal request includes information of the target account and information of a preset number of user accounts that have a specified association relationship with the target account. The account assistance restriction removal notification is sent to the preset number of user accounts respectively. Feedback messages for the account assistance restriction removal notification are obtained from the preset number of user accounts respectively based on the first smart contract, and it is determined whether to remove the account authority restriction corresponding to the restriction removal request from the target account through the feedback message. Since it is difficult to forge a user account that has an association relationship with the target account, the discrimination of the restriction removal scheme can be enhanced. For a normal account, the restriction removal is assisted by the user account that has an association relationship with the target account, so that the restriction removal scheme is simpler and more effective, but the scheme becomes difficult to implement for an abnormal account. In addition, the qualification conditions required for restriction removal can also be personalized, so that the flexibility of account restriction removal is higher.

[0114] In addition, the use of blockchain systems and smart contracts to unlock accounts can make the data processing process safer, ensure data security, and have strong traceability of data processing.

[0115] Embodiment 5

[0116] The above is a method for removing restrictions on an account provided in the embodiments of this specification. Based on the same idea, the embodiments of this specification also provide a device for removing restrictions on an account, such as Fig.10 shown.

[0117] The account unblocking device includes: an unblocking request module 1001, an unblocking assistance notification module 1002 and an unblocking module 1003, wherein:

[0118] The restriction release request module 1001 receives a restriction release request for a target account sent by a target terminal, wherein the restriction release request includes information of the target account and information of a preset number of user accounts that have a specified association relationship with the target account;

[0119] The assistance unblocking notification module 1002 generates an account assistance unblocking notification based on the unblocking request, and sends the account assistance unblocking notification to the preset number of user accounts respectively;

[0120] The restriction removal module 1003 receives feedback messages from the preset number of user accounts regarding the account assistance restriction removal notification, and determines whether to remove the account authority restriction corresponding to the restriction removal request for the target account based on the feedback messages.

[0121] In the embodiment of the present specification, the account assistance unblocking notification includes information of the target account and operation guidance information, wherein the operation guidance information is used to guide the user of the user account to guarantee the target account for unblocking.

[0122] The restriction removal module 1003 removes the account authority restriction corresponding to the restriction removal request from the target account if the feedback messages from the user accounts exceeding the preset threshold number among the preset number of user accounts indicate that the target account for restriction removal is guaranteed.

[0123] In an embodiment of the present specification, the account authority restriction corresponding to the restriction release request includes one or more of the following: restriction on the number of resource collection, restriction on the number of resource extraction, long-term restriction on the account authority of the target account, or temporary restriction on the account authority of the target account.

[0124] In the embodiment of this specification, the device further includes:

[0125] An information acquisition module is configured to acquire information of one or more different first accounts and information of a second account that guarantees each of the first accounts;

[0126] A graph construction module, which constructs a corresponding knowledge graph based on the information of the first account and the information of the second account, and determines a risk subgraph with a preset risk contained in the knowledge graph;

[0127] The risk prevention and control module performs risk prevention and control processing on the business corresponding to the first account and the second account based on the account information included in the risk subgraph.

[0128] In the embodiment of this specification, the device further includes:

[0129] The first authority limiting module adds restrictions that comply with first preset authority limiting rules to the preset account permissions of the first account corresponding to the detected account if an account with preset risks is detected in the second account.

[0130] In the embodiment of this specification, the device further includes:

[0131] The second authority limiting module adds restrictions that comply with second preset authority limiting rules to the second account if it is detected that the number of times the first account is determined as a risky account exceeds a preset number threshold.

[0132] In the embodiment of this specification, the device further includes:

[0133] A times acquisition module is used to acquire the times that each user account in the preset number of user accounts guarantees other accounts that have been released from restrictions;

[0134] The modification notification module sends a user account modification notification to the target terminal if there is a user account among the preset number of user accounts that has guaranteed other accounts for more than a preset guarantee number threshold, so that the target terminal re-selects a preset number of user accounts that have a specified association relationship with the target account based on the modification notification.

[0135] In the embodiment of the present specification, if the target account is an account with a preset risk, the preset number of user accounts that have a specified association relationship with the target account include at least one or more user accounts whose existence duration exceeds a preset duration threshold.

[0136] In an embodiment of the present specification, the target account is an account that meets preset conditions, and the preset conditions include one or more of the following: an association relationship intimacy condition used to characterize the degree of intimacy between the target account and the target account, a security condition and an activity condition used to characterize the security behavior of the user account.

[0137] The embodiments of the present specification provide an account unblocking device, which receives an unblocking request for a target account sent by a target terminal, wherein the unblocking request includes information of the target account and information of a preset number of user accounts that have a specified association relationship with the target account, then generates an account assistance unblocking notification based on the unblocking request, and sends the account assistance unblocking notification to the preset number of user accounts respectively, and then can receive feedback messages from the preset number of user accounts for the account assistance unblocking notification respectively, and based on the feedback messages, determines whether to release the account authority restriction corresponding to the unblocking request for the target account. Since it is difficult to forge a user account that has an association relationship with the target account, the differentiation of the unblocking scheme can be enhanced. For a normal account, unblocking is assisted by the user account that has an association relationship with the target account, making the unblocking scheme simpler and more effective, but the scheme becomes difficult to implement for an abnormal account. In addition, the qualification conditions required for unblocking can also be personalized, thereby making the account unblocking more flexible.

[0138] Embodiment 6

[0139] Based on the same idea, the embodiment of this specification also provides an account unblocking device, which is a device in the blockchain system, such as Fig.11 shown.

[0140] The account unblocking device includes: a first contract deployment module 1101, a request receiving module 1102, a notification module 1103 and a unblocking module 1104, wherein:

[0141] The first contract deployment module 1101 obtains an account restriction removal rule for removing preset account authority restrictions from an account, generates a corresponding first smart contract based on the account restriction removal rule, and deploys the first smart contract in the blockchain system;

[0142] The request receiving module 1102 receives a target account unrestriction request sent by a target terminal, wherein the target account unrestriction request includes information of the target account and information of a preset number of user accounts having a specified association relationship with the target account;

[0143] Notification module 1103, based on the first smart contract, generates an account assistance unblocking notification through the unblocking request, and sends the account assistance unblocking notification to the preset number of user accounts respectively;

[0144] The restriction removal module 1104 obtains feedback messages regarding the account assistance restriction removal notification from the preset number of user accounts based on the first smart contract, and determines whether to remove the account authority restriction corresponding to the restriction removal request for the target account through the feedback messages.

[0145] In the embodiments of this specification, it also includes:

[0146] A second contract deployment module, which obtains rule information for risk prevention and control of preset businesses, generates a corresponding second smart contract based on the rule information, and deploys the second smart contract in the blockchain system;

[0147] an information acquisition module, which acquires information of one or more different first accounts and information of a second account that guarantees each of the first accounts based on the second smart contract;

[0148] A graph construction module, based on the second smart contract, constructs a corresponding knowledge graph through information of the first account and information of the second account, and determines a risk subgraph with preset risks contained in the knowledge graph;

[0149] The risk prevention and control module performs risk prevention and control on the business corresponding to the first account and the second account based on the account information contained in the risk subgraph and the second smart contract.

[0150] In the embodiments of this specification, it also includes:

[0151] The third contract deployment module obtains information of a risk subgraph with preset risks, and based on a third smart contract pre-deployed in the blockchain system, generates a fourth smart contract for risk prevention and control of preset businesses through the information of the risk subgraph with preset risks, and deploys the fourth smart contract in the blockchain system. The risk subgraph is determined by a corresponding knowledge graph constructed based on information of one or more different first accounts and information of a second account that guarantees the release of each of the first accounts.

[0152] The embodiment of the present specification provides an account unrestriction device, which generates a corresponding first smart contract based on an acquired account unrestriction rule, deploys the first smart contract in a blockchain system, and upon receiving an unrestriction request of a target account sent by a target terminal, generates an account assistance unrestriction notification through the unrestriction request based on the first smart contract, wherein the unrestriction request includes information of the target account and information of a preset number of user accounts that have a specified association relationship with the target account, sends the account assistance unrestriction notification to the preset number of user accounts respectively, obtains feedback messages for the account assistance unrestriction notification from the preset number of user accounts respectively based on the first smart contract, and determines whether to release the account authority restriction corresponding to the unrestriction request for the target account through the feedback message. Since it is difficult to forge a user account that has an association relationship with the target account, the differentiation of the unrestriction solution can be enhanced. For a normal account, unrestriction is assisted by a user account that has an association relationship with the target account, making the unrestriction solution simpler and more effective, but the solution becomes difficult to implement for an abnormal account. In addition, the qualification conditions required for unrestriction can also be personalized, thereby making the flexibility of account unrestriction higher.

[0153] In addition, the use of blockchain systems and smart contracts to unlock accounts can make the data processing process safer, ensure data security, and have strong traceability of data processing.

[0154] Embodiment 7

[0155] The above is an account unblocking device provided in the embodiment of this specification. Based on the same idea, the embodiment of this specification also provides an account unblocking device, such as Fig.12 shown.

[0156] The account unblocking device may be the server provided in the above embodiment or a device in the blockchain system, etc.

[0157] The account unblocking device may have relatively large differences due to different configurations or performances, and may include one or more processors 1201 and memory 1202, and the memory 1202 may store one or more storage applications or data. Among them, the memory 1202 may be a temporary storage or a permanent storage. The application stored in the memory 1202 may include one or more modules (not shown in the figure), and each module may include a series of computer executable instructions in the account unblocking device. Furthermore, the processor 1201 may be configured to communicate with the memory 1202, and execute a series of computer executable instructions in the memory 1202 on the account unblocking device. The account unblocking device may also include one or more power supplies 1203, one or more wired or wireless network interfaces 1204, one or more input and output interfaces 1205, and one or more keyboards 1206.

[0158] Specifically in this embodiment, the account delimiting 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 in the account delimiting device, and the one or more programs are configured to be executed by one or more processors, including the following computer executable instructions:

[0159] Receiving a target account unrestriction request sent by a target terminal, wherein the target account unrestriction request includes information of the target account and information of a preset number of user accounts having a specified association relationship with the target account;

[0160] Generate an account assistance unblocking notification based on the unblocking request, and send the account assistance unblocking notification to the preset number of user accounts respectively;

[0161] Feedback messages from the preset number of user accounts regarding the account assistance restriction removal notification are received respectively, and based on the feedback messages, it is determined whether to remove the account authority restriction corresponding to the restriction removal request for the target account.

[0162] In the embodiment of the present specification, the account assistance unblocking notification includes information of the target account and operation guidance information, wherein the operation guidance information is used to guide the user of the user account to guarantee the target account for unblocking.

[0163] The determining, based on the feedback message, whether to release the account authority restriction corresponding to the restriction release request for the target account includes:

[0164] If the feedback messages from the preset number of user accounts exceeding the preset threshold number indicate that the target account for unblocking is guaranteed, the account authority restriction corresponding to the unblocking request is released for the target account.

[0165] In an embodiment of the present specification, the account authority restriction corresponding to the restriction release request includes one or more of the following: restriction on the number of resource collection, restriction on the number of resource extraction, long-term restriction on the account authority of the target account, or temporary restriction on the account authority of the target account.

[0166] In the embodiments of this specification, it also includes:

[0167] Obtaining information of one or more different first accounts and information of a second account that guarantees each of the first accounts;

[0168] Based on the information of the first account and the information of the second account, a corresponding knowledge graph is constructed, and a risk subgraph with a preset risk contained in the knowledge graph is determined;

[0169] Based on the account information included in the risk subgraph, risk prevention and control processing is performed on the business corresponding to the first account and the second account.

[0170] In the embodiments of this specification, it also includes:

[0171] If it is detected that there is an account with a preset risk in the second account, a restriction that complies with a first preset authority limitation rule is added to the preset account authority of the first account corresponding to the detected account.

[0172] In the embodiments of this specification, it also includes:

[0173] If it is detected that the number of times that the first account is determined to be a risky account exceeds a preset number threshold, restrictions that comply with second preset authority limitation rules are added to the second account.

[0174] In the embodiments of this specification, it also includes:

[0175] Obtaining the number of times each user account in the preset number of user accounts has guaranteed other accounts that have been unblocked;

[0176] If there is a user account among the preset number of user accounts that has guaranteed other unrestricted accounts more than the preset guarantee number threshold, a user account modification notification is sent to the target terminal so that the target terminal re-selects a preset number of user accounts that have a specified association relationship with the target account based on the modification notification.

[0177] In the embodiment of the present specification, if the target account is an account with a preset risk, the preset number of user accounts that have a specified association relationship with the target account include at least one or more user accounts whose existence duration exceeds a preset duration threshold.

[0178] In an embodiment of the present specification, the target account is an account that meets preset conditions, and the preset conditions include one or more of the following: an association relationship intimacy condition used to characterize the degree of intimacy between the target account and the target account, a security condition and an activity condition used to characterize the security behavior of the user account.

[0179] In addition, specifically in this embodiment, the account delimiting 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 in the account delimiting device, and the one or more programs are configured to be executed by one or more processors, including the following computer executable instructions:

[0180] Obtaining an account unrestriction rule for unrestricting a preset account authority restriction on an account, generating a corresponding first smart contract based on the account unrestriction rule, and deploying the first smart contract in the blockchain system;

[0181] Receiving a target account unrestriction request sent by a target terminal, wherein the target account unrestriction request includes information of the target account and information of a preset number of user accounts having a specified association relationship with the target account;

[0182] Based on the first smart contract, generate an account assistance unblocking notification through the unblocking request, and send the account assistance unblocking notification to the preset number of user accounts respectively;

[0183] Based on the first smart contract, feedback messages regarding the account assistance unblocking notification are obtained from the preset number of user accounts respectively, and through the feedback messages, it is determined whether to lift the account authority restriction corresponding to the unblocking request for the target account.

[0184] In the embodiments of this specification, it also includes:

[0185] Obtaining rule information for risk prevention and control of preset businesses, generating a corresponding second smart contract based on the rule information, and deploying the second smart contract in the blockchain system;

[0186] Based on the second smart contract, obtain information of one or more different first accounts and information of a second account that guarantees each of the first accounts;

[0187] Based on the second smart contract, a corresponding knowledge graph is constructed through the information of the first account and the information of the second account, and a risk subgraph with a preset risk contained in the knowledge graph is determined;

[0188] Based on the account information included in the risk subgraph and the second smart contract, risk prevention and control processing is performed on the business corresponding to the first account and the second account.

[0189] In the embodiments of this specification, it also includes:

[0190] Obtain information on a risk subgraph with preset risks, and based on a third smart contract pre-deployed in the blockchain system, generate a fourth smart contract for risk prevention and control of preset businesses through the information on the risk subgraph with preset risks, and deploy the fourth smart contract in the blockchain system, wherein the risk subgraph is determined based on a corresponding knowledge graph constructed based on information on one or more different first accounts and information on a second account that guarantees the release of each of the first accounts.

[0191] The embodiments of the present specification provide an account unblocking device, which receives an unblocking request for a target account sent by a target terminal, wherein the unblocking request includes information of the target account and information of a preset number of user accounts that have a specified association relationship with the target account, and then generates an account assistance unblocking notification based on the unblocking request, and sends the account assistance unblocking notification to the preset number of user accounts respectively, and then can respectively receive feedback messages from the preset number of user accounts for the account assistance unblocking notification, and based on the feedback messages, determine whether to release the account authority restriction corresponding to the unblocking request for the target account, because it is difficult to forge a user account that has an association relationship with the target account, and therefore the differentiation of the unblocking scheme can be enhanced, and for a normal account, the unblocking scheme is assisted by the user account that has an association relationship with the normal account, making the unblocking scheme simpler and more effective, but the scheme becomes difficult to implement for an abnormal account, and in addition, the qualification conditions required for unblocking can also be personalized, so that the flexibility of account unblocking is higher.

[0192] In addition, the use of blockchain systems and smart contracts to unlock accounts can make the data processing process safer, ensure data security, and have strong traceability of data processing.

[0193] Embodiment 8

[0194] Furthermore, based on the above Figure 1A and Fig. 9In one embodiment, the present specification further provides a storage medium for storing computer executable instruction information. In a specific embodiment, the storage medium may be a USB flash drive, an optical disk, a hard disk, etc. When the computer executable instruction information stored in the storage medium is executed by the processor, the following process can be implemented:

[0195] Receiving a target account unrestriction request sent by a target terminal, wherein the target account unrestriction request includes information of the target account and information of a preset number of user accounts having a specified association relationship with the target account;

[0196] Generate an account assistance unblocking notification based on the unblocking request, and send the account assistance unblocking notification to the preset number of user accounts respectively;

[0197] Feedback messages from the preset number of user accounts regarding the account assistance restriction removal notification are received respectively, and based on the feedback messages, it is determined whether to remove the account authority restriction corresponding to the restriction removal request for the target account.

[0198] In the embodiment of the present specification, the account assistance unblocking notification includes information of the target account and operation guidance information, wherein the operation guidance information is used to guide the user of the user account to guarantee the target account for unblocking.

[0199] The determining, based on the feedback message, whether to release the account authority restriction corresponding to the restriction release request for the target account includes:

[0200] If the feedback messages from the preset number of user accounts exceeding the preset threshold number indicate that the target account for unblocking is guaranteed, the account authority restriction corresponding to the unblocking request is released for the target account.

[0201] In an embodiment of the present specification, the account authority restriction corresponding to the restriction release request includes one or more of the following: restriction on the number of resource collection, restriction on the number of resource extraction, long-term restriction on the account authority of the target account, or temporary restriction on the account authority of the target account.

[0202] In the embodiments of this specification, it also includes:

[0203] Obtaining information of one or more different first accounts and information of a second account that guarantees each of the first accounts;

[0204] Based on the information of the first account and the information of the second account, a corresponding knowledge graph is constructed, and a risk subgraph with a preset risk contained in the knowledge graph is determined;

[0205] Based on the account information included in the risk subgraph, risk prevention and control processing is performed on the business corresponding to the first account and the second account.

[0206] In the embodiments of this specification, it also includes:

[0207] If it is detected that there is an account with a preset risk in the second account, a restriction that complies with a first preset authority limitation rule is added to the preset account authority of the first account corresponding to the detected account.

[0208] In the embodiments of this specification, it also includes:

[0209] If it is detected that the number of times that the first account is determined to be a risky account exceeds a preset number threshold, restrictions that comply with second preset authority limitation rules are added to the second account.

[0210] In the embodiments of this specification, it also includes:

[0211] Obtaining the number of times each user account in the preset number of user accounts has guaranteed other accounts that have been unblocked;

[0212] If there is a user account among the preset number of user accounts that has guaranteed other unrestricted accounts more than the preset guarantee number threshold, a user account modification notification is sent to the target terminal so that the target terminal re-selects a preset number of user accounts that have a specified association relationship with the target account based on the modification notification.

[0213] In the embodiment of the present specification, if the target account is an account with a preset risk, the preset number of user accounts that have a specified association relationship with the target account include at least one or more user accounts whose existence duration exceeds a preset duration threshold.

[0214] In an embodiment of the present specification, the target account is an account that meets preset conditions, and the preset conditions include one or more of the following: an association relationship intimacy condition used to characterize the degree of intimacy between the target account and the target account, a security condition and an activity condition used to characterize the security behavior of the user account.

[0215] In addition, in another specific embodiment, the storage medium may be a USB flash drive, an optical disk, a hard disk, etc., and the computer executable instruction information stored in the storage medium can implement the following process when executed by the processor:

[0216] Obtaining an account unrestriction rule for unrestricting a preset account authority restriction on an account, generating a corresponding first smart contract based on the account unrestriction rule, and deploying the first smart contract in the blockchain system;

[0217] Receiving a target account unrestriction request sent by a target terminal, wherein the target account unrestriction request includes information of the target account and information of a preset number of user accounts having a specified association relationship with the target account;

[0218] Based on the first smart contract, generate an account assistance unblocking notification through the unblocking request, and send the account assistance unblocking notification to the preset number of user accounts respectively;

[0219] Based on the first smart contract, feedback messages regarding the account assistance unblocking notification are obtained from the preset number of user accounts respectively, and through the feedback messages, it is determined whether to lift the account authority restriction corresponding to the unblocking request for the target account.

[0220] In the embodiments of this specification, it also includes:

[0221] Obtaining rule information for risk prevention and control of preset businesses, generating a corresponding second smart contract based on the rule information, and deploying the second smart contract in the blockchain system;

[0222] Based on the second smart contract, obtain information of one or more different first accounts and information of a second account that guarantees each of the first accounts;

[0223] Based on the second smart contract, a corresponding knowledge graph is constructed through the information of the first account and the information of the second account, and a risk subgraph with a preset risk contained in the knowledge graph is determined;

[0224] Based on the account information included in the risk subgraph and the second smart contract, risk prevention and control processing is performed on the business corresponding to the first account and the second account.

[0225] In the embodiment of this specification, it also includes:

[0226] Obtain information on a risk subgraph with preset risks, and based on a third smart contract pre-deployed in the blockchain system, generate a fourth smart contract for risk prevention and control of preset businesses through the information on the risk subgraph with preset risks, and deploy the fourth smart contract in the blockchain system, wherein the risk subgraph is determined based on a corresponding knowledge graph constructed based on information on one or more different first accounts and information on a second account that guarantees the release of each of the first accounts.

[0227] The embodiment of the present specification provides a storage medium, which receives a restriction release request of a target account sent by a target terminal, wherein the restriction release request includes information of the target account and information of a preset number of user accounts that have a specified association relationship with the target account, and then generates an account assistance restriction release notification based on the restriction release request, and sends the account assistance restriction release notification to the preset number of user accounts respectively, and then can respectively receive feedback messages from the preset number of user accounts for the account assistance restriction release notification, and based on the feedback messages, determine whether to release the account authority restriction corresponding to the restriction release request for the target account, because it is difficult to forge a user account that has an association relationship with the target account, and therefore the differentiation of the restriction release scheme can be enhanced, and for a normal account, the restriction release scheme is made simpler and more effective by assisting in the restriction release with the assistance of the user account that has an association relationship with the target account, but the scheme becomes difficult to implement for an abnormal account, and in addition, the qualification conditions required for the restriction release can also be personalized, so that the flexibility of the account restriction release is higher.

[0228] In addition, the use of blockchain systems and smart contracts to unlock accounts can make the data processing process safer, ensure data security, and have strong traceability of data processing.

[0229] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0230] In the 1990s, improvements to a technology could be clearly distinguished as hardware improvements (for example, improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the method flow). However, with the development of technology, many improvements to the method flow today can be regarded as direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that an improvement in a method flow cannot be implemented using a hardware entity module. For example, a programmable logic device (PLD) (such as a field programmable gate array (FPGA)) is such an integrated circuit whose logical function is determined by the user's programming of the device. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to ask a chip manufacturer to design and produce a dedicated integrated circuit chip. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented by "logic compiler" software, which is similar to the software compiler used when developing and writing programs, and the original code before compilation must also be written in a specific programming language, which is called hardware description language (HDL). There is not only one HDL, but many kinds, 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, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also know that it is only necessary to program the method flow slightly in the above-mentioned hardware description languages ​​and program it into the integrated circuit, and then it is easy to obtain the hardware circuit that implements the logic method flow.

[0231] The controller can be implemented in any appropriate manner, for example, the controller can take the form of a microprocessor or processor and a computer-readable medium storing a computer-readable program code (such as software or firmware) that can be executed by the (micro)processor, a logic gate, a switch, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. Examples of controllers include, but are not limited to, the following microcontrollers: ARC625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art also know that in addition to implementing the controller in a purely computer-readable program code manner, the controller can be implemented in the form of a logic gate, a switch, an application-specific integrated circuit, a programmable logic controller, and an embedded microcontroller by logically programming the method steps. Therefore, this controller can be considered as a hardware component, and the devices included therein for implementing various functions can also be regarded as structures within the hardware component. Or even, the devices for implementing various functions can be regarded as both software modules for implementing the method and structures within the hardware component.

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

[0233] For the convenience of description, the above devices are described in terms of functions and are divided into various units. Of course, when implementing one or more embodiments of this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0234] Those skilled in the art will appreciate that the embodiments of this specification may be provided as methods, systems, or computer program products. Therefore, one or more embodiments of this specification may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, one or more embodiments of this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0235] The embodiments of this specification are described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of this specification. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable fraud case serial and parallel device to produce a machine, so that the instructions executed by the processor of the computer or other programmable fraud case serial and parallel device produce a device for implementing the function specified in one process or multiple processes of the flowchart and / or one box or multiple boxes of the block diagram.

[0236] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable fraud case serial and parallel device to work in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device, which implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0237] These computer program instructions may also be loaded onto a computer or other programmable fraud case serial and parallel device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more flows of the flowchart and / or one or more blocks of the block diagram.

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

[0239] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0240] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules 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 technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0241] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0242] It should be understood by those skilled in the art that the embodiments of this specification may be provided as methods, systems or computer program products. Therefore, one or more embodiments of this specification may take the form of a complete hardware embodiment, a complete software embodiment or an embodiment combining software and hardware. Moreover, one or more embodiments of this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

[0243] One or more embodiments of the present specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. One or more embodiments of the present specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0244] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0245] The above description is only an embodiment of the present specification and is not intended to limit the present specification. For those skilled in the art, the present specification may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present specification shall be included in the scope of the claims of the present specification.

Claims

1. A method for removing restrictions on an account, the method comprising: Receiving a target account unrestriction request sent by a target terminal, wherein the target account unrestriction request includes information of the target account and information of a preset number of user accounts having a specified association relationship with the target account; Generate an account assistance unblocking notification based on the unblocking request, and send the account assistance unblocking notification to the preset number of user accounts respectively; Receiving feedback messages from the preset number of user accounts in response to the account assistance unrestriction notification respectively, and determining whether to remove the account authority restriction corresponding to the unrestriction request for the target account based on the feedback messages; Obtaining information of one or more different first accounts and information of a second account that guarantees each of the first accounts; Based on the information of the first account and the information of the second account, a corresponding knowledge graph is constructed, and a risk subgraph with a preset risk contained in the knowledge graph is determined; Based on the account information included in the risk subgraph, risk prevention and control processing is performed on the business corresponding to the first account and the second account.

2. The method according to claim 1, wherein the account assistance unblocking notification includes information of the target account and operation guidance information, wherein the operation guidance information is used to guide the user of the user account to guarantee the target account for unblocking. The determining, based on the feedback message, whether to release the account authority restriction corresponding to the restriction release request for the target account includes: If the feedback messages from the preset number of user accounts exceeding the preset threshold number indicate that the target account for unblocking is guaranteed, the account authority restriction corresponding to the unblocking request is released for the target account.

3. According to the method described in claim 2, the account authority restriction corresponding to the restriction release request includes one or more of the following: restriction on the amount of resource collection, restriction on the amount of resource extraction, long-term restriction on the account authority of the target account, or temporary restriction on the account authority of the target account.

4. The method according to claim 1, further comprising: If it is detected that there is an account with a preset risk in the second account, a restriction that complies with a first preset authority limitation rule is added to the preset account authority of the first account corresponding to the detected account.

5. The method according to claim 1, further comprising: If it is detected that the number of times that the first account is determined to be a risky account exceeds a preset number threshold, restrictions that comply with second preset authority limitation rules are added to the second account.

6. The method according to claim 1, further comprising: Obtaining the number of times each user account in the preset number of user accounts has guaranteed other accounts that have been unblocked; If there is a user account among the preset number of user accounts that has guaranteed other unrestricted accounts more than the preset guarantee number threshold, a user account modification notification is sent to the target terminal so that the target terminal re-selects a preset number of user accounts that have a specified association relationship with the target account based on the modification notification.

7. According to the method of claim 1, if the target account is an account with a preset risk, the preset number of user accounts that have a specified association relationship with the target account include at least one or more user accounts whose duration exceeds a preset duration threshold.

8. According to the method described in claim 1, the target account is an account that meets preset conditions, and the preset conditions include one or more of the following: an association relationship intimacy condition used to characterize the degree of intimacy between the target account and the user account, a security condition and an activity condition used to characterize the security behavior of the user account.

9. A method for removing restrictions on an account, applied to a blockchain system, the method comprising: Obtaining an account unrestriction rule for unrestricting a preset account authority restriction on an account, generating a corresponding first smart contract based on the account unrestriction rule, and deploying the first smart contract in the blockchain system; Receiving a target account unrestriction request sent by a target terminal, wherein the target account unrestriction request includes information of the target account and information of a preset number of user accounts having a specified association relationship with the target account; Based on the first smart contract, generate an account assistance unblocking notification through the unblocking request, and send the account assistance unblocking notification to the preset number of user accounts respectively; Based on the first smart contract, respectively obtain feedback messages regarding the account assistance unblocking notification from the preset number of user accounts, and determine whether to release the account authority restriction corresponding to the unblocking request for the target account through the feedback messages; Obtaining rule information for risk prevention and control of preset businesses, generating a corresponding second smart contract based on the rule information, and deploying the second smart contract in the blockchain system; Based on the second smart contract, obtain information of one or more different first accounts and information of a second account that guarantees each of the first accounts; Based on the second smart contract, a corresponding knowledge graph is constructed through the information of the first account and the information of the second account, and a risk subgraph with a preset risk contained in the knowledge graph is determined; Based on the account information contained in the risk subgraph and the second smart contract, perform risk prevention and control on the business corresponding to the first account and the second account; Obtain information on a risk subgraph with preset risks, and based on a third smart contract pre-deployed in the blockchain system, generate a fourth smart contract for risk prevention and control of preset businesses through the information on the risk subgraph with preset risks, and deploy the fourth smart contract in the blockchain system, wherein the risk subgraph is determined based on a corresponding knowledge graph constructed based on information on one or more different first accounts and information on a second account that guarantees the release of each of the first accounts.

10. A device for removing restrictions from an account, the device comprising: a restriction release request module, receiving a restriction release request of a target account sent by a target terminal, wherein the restriction release request includes information of the target account and information of a preset number of user accounts having a specified association relationship with the target account; an assistance unblocking notification module, which generates an account assistance unblocking notification based on the unblocking request, and sends the account assistance unblocking notification to the preset number of user accounts respectively; a restriction removal module, receiving feedback messages from the preset number of user accounts in response to the account assistance restriction removal notification, and determining whether to remove the account authority restriction corresponding to the restriction removal request for the target account based on the feedback messages; An information acquisition module is configured to acquire information of one or more different first accounts and information of a second account that guarantees each of the first accounts; A graph construction module, which constructs a corresponding knowledge graph based on the information of the first account and the information of the second account, and determines a risk subgraph with a preset risk contained in the knowledge graph; The risk prevention and control module performs risk prevention and control processing on the business corresponding to the first account and the second account based on the account information included in the risk subgraph.

11. A device for removing restrictions from an account, applied to a blockchain system, comprising: A first contract deployment module, which obtains an account restriction removal rule for removing preset account authority restrictions from an account, generates a corresponding first smart contract based on the account restriction removal rule, and deploys the first smart contract in the blockchain system; a request receiving module, receiving a target account unrestriction request sent by a target terminal, wherein the unrestriction request includes information of the target account and information of a preset number of user accounts having a specified association relationship with the target account; a notification module, based on the first smart contract, generating an account assistance unblocking notification through the unblocking request, and sending the account assistance unblocking notification to the preset number of user accounts respectively; a restriction removal module, which obtains feedback messages regarding the account assistance restriction removal notification from the preset number of user accounts based on the first smart contract, and determines whether to remove the account authority restriction corresponding to the restriction removal request for the target account through the feedback messages; A second contract deployment module, which obtains rule information for risk prevention and control of preset businesses, generates a corresponding second smart contract based on the rule information, and deploys the second smart contract in the blockchain system; an information acquisition module, which acquires information of one or more different first accounts and information of a second account that guarantees each of the first accounts based on the second smart contract; A graph construction module, based on the second smart contract, constructs a corresponding knowledge graph through information of the first account and information of the second account, and determines a risk subgraph with preset risks contained in the knowledge graph; a risk prevention and control module, which performs risk prevention and control processing on the business corresponding to the first account and the second account based on the account information contained in the risk subgraph and the second smart contract; The third contract deployment module obtains information of a risk subgraph with preset risks, and based on a third smart contract pre-deployed in the blockchain system, generates a fourth smart contract for risk prevention and control of preset businesses through the information of the risk subgraph with preset risks, and deploys the fourth smart contract in the blockchain system. The risk subgraph is determined by a corresponding knowledge graph constructed based on information of one or more different first accounts and information of a second account that guarantees the release of each of the first accounts.

12. A device for removing restrictions on an account, the device comprising: processor; as well as a memory arranged to store computer executable instructions which, when executed, cause the processor to: Receiving a target account unrestriction request sent by a target terminal, wherein the target account unrestriction request includes information of the target account and information of a preset number of user accounts having a specified association relationship with the target account; Generate an account assistance unblocking notification based on the unblocking request, and send the account assistance unblocking notification to the preset number of user accounts respectively; Receiving feedback messages from the preset number of user accounts in response to the account assistance unrestriction notification respectively, and determining whether to remove the account authority restriction corresponding to the unrestriction request for the target account based on the feedback messages; Obtaining information of one or more different first accounts and information of a second account that guarantees each of the first accounts; Based on the information of the first account and the information of the second account, a corresponding knowledge graph is constructed, and a risk subgraph with a preset risk contained in the knowledge graph is determined; Based on the account information included in the risk subgraph, risk prevention and control processing is performed on the business corresponding to the first account and the second account.

13. A device for removing restrictions from an account, the device being a device in a blockchain system, the device for removing restrictions from an account comprising: processor; as well as a memory arranged to store computer executable instructions which, when executed, cause the processor to: Obtaining an account unrestriction rule for unrestricting a preset account authority restriction on an account, generating a corresponding first smart contract based on the account unrestriction rule, and deploying the first smart contract in the blockchain system; Receiving a target account unrestriction request sent by a target terminal, wherein the target account unrestriction request includes information of the target account and information of a preset number of user accounts having a specified association relationship with the target account; Based on the first smart contract, generate an account assistance unblocking notification through the unblocking request, and send the account assistance unblocking notification to the preset number of user accounts respectively; Based on the first smart contract, respectively obtain feedback messages regarding the account assistance unblocking notification from the preset number of user accounts, and determine whether to release the account authority restriction corresponding to the unblocking request for the target account through the feedback messages; Obtaining rule information for risk prevention and control of preset businesses, generating a corresponding second smart contract based on the rule information, and deploying the second smart contract in the blockchain system; Based on the second smart contract, obtain information of one or more different first accounts and information of a second account that guarantees each of the first accounts; Based on the second smart contract, a corresponding knowledge graph is constructed through the information of the first account and the information of the second account, and a risk subgraph with a preset risk contained in the knowledge graph is determined; Based on the account information contained in the risk subgraph and the second smart contract, perform risk prevention and control on the business corresponding to the first account and the second account; Obtain information on a risk subgraph with preset risks, and based on a third smart contract pre-deployed in the blockchain system, generate a fourth smart contract for risk prevention and control of preset businesses through the information on the risk subgraph with preset risks, and deploy the fourth smart contract in the blockchain system, wherein the risk subgraph is determined based on a corresponding knowledge graph constructed based on information on one or more different first accounts and information on a second account that guarantees the release of each of the first accounts.

14. A storage medium for storing computer executable instructions, wherein the executable instructions implement the following process when executed: Receiving a target account unrestriction request sent by a target terminal, wherein the target account unrestriction request includes information of the target account and information of a preset number of user accounts having a specified association relationship with the target account; Generate an account assistance unblocking notification based on the unblocking request, and send the account assistance unblocking notification to the preset number of user accounts respectively; Receiving feedback messages from the preset number of user accounts in response to the account assistance unrestriction notification respectively, and determining whether to remove the account authority restriction corresponding to the unrestriction request for the target account based on the feedback messages; Obtaining information of one or more different first accounts and information of a second account that guarantees each of the first accounts; Based on the information of the first account and the information of the second account, a corresponding knowledge graph is constructed, and a risk subgraph with a preset risk contained in the knowledge graph is determined; Based on the account information included in the risk subgraph, risk prevention and control processing is performed on the business corresponding to the first account and the second account.

15. A storage medium for storing computer executable instructions, wherein the executable instructions implement the following process when executed: Obtaining an account unrestriction rule for unrestricting a preset account authority restriction on an account, generating a corresponding first smart contract based on the account unrestriction rule, and deploying the first smart contract in a blockchain system; Receiving a target account unrestriction request sent by a target terminal, wherein the target account unrestriction request includes information of the target account and information of a preset number of user accounts having a specified association relationship with the target account; Based on the first smart contract, generate an account assistance unblocking notification through the unblocking request, and send the account assistance unblocking notification to the preset number of user accounts respectively; Based on the first smart contract, respectively obtain feedback messages regarding the account assistance unblocking notification from the preset number of user accounts, and determine whether to release the account authority restriction corresponding to the unblocking request for the target account through the feedback messages; Obtaining rule information for risk prevention and control of preset businesses, generating a corresponding second smart contract based on the rule information, and deploying the second smart contract in the blockchain system; Based on the second smart contract, obtain information of one or more different first accounts and information of a second account that guarantees each of the first accounts; Based on the second smart contract, a corresponding knowledge graph is constructed through the information of the first account and the information of the second account, and a risk subgraph with a preset risk contained in the knowledge graph is determined; Based on the account information contained in the risk subgraph and the second smart contract, perform risk prevention and control on the business corresponding to the first account and the second account; Obtain information on a risk subgraph with preset risks, and based on a third smart contract pre-deployed in the blockchain system, generate a fourth smart contract for risk prevention and control of preset businesses through the information on the risk subgraph with preset risks, and deploy the fourth smart contract in the blockchain system, wherein the risk subgraph is determined based on a corresponding knowledge graph constructed based on information on one or more different first accounts and information on a second account that guarantees the release of each of the first accounts.

Images