Guarantee relationship data processing method, device and equipment

Abstract

The present application provides a method, device and equipment for processing guarantee relationship data. The method includes: obtaining guarantee relationship data to be split from a first database; if the guarantee relationship data to be split includes at least one secured debt and multiple collaterals providing guarantees, then according to the collateral information of each collateral providing guarantees, determine the weight value of each collateral providing guarantees; according to the weight value of each collateral providing guarantees and the debt information of at least one secured debt, split the guarantee relationship data to be split to obtain multiple one-to-one guarantee relationship data corresponding to the guarantee relationship data to be split; each one-to-one guarantee relationship data includes a single debt and a single collateral, which is used to indicate the guarantee resources that a single collateral can provide for a single debt; and store the multiple one-to-one guarantee relationship data corresponding to the guarantee relationship data to be split in a second database. The method of the present application can accurately identify the collateral guarantee capacity and facilitate risk mitigation of debts.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a guarantee relationship data processing method, device and equipment. Background Art

[0002] With the massive increase in bank loan business, banks as lenders (also known as creditors) may face huge risks when borrowers (also known as debtors) fail to fulfill their debts. In order to reduce this risk, creditors generally require debtors to sign a guarantee contract to ensure that the creditor's rights can be realized.

[0003] A guarantee relationship refers to the relationship between the guaranteed debt and the collateral that provides the guarantee. A debt can be guaranteed by only one collateral or by multiple collaterals, and a collateral can be used to guarantee only one debt or multiple debts, thus forming many different types of guarantee relationships.

[0004] However, as the guarantee relationship between debts and collateral becomes more complicated, it is difficult to accurately identify the guarantee capacity that the collateral can provide for each related debt when it is used to guarantee multiple debts at the same time, which is not conducive to risk mitigation of debts. Summary of the invention

[0005] The present application provides a guarantee relationship data processing method, device and equipment to solve the problem that it is difficult to accurately identify the guarantee capacity that collateral that provides guarantees for multiple debts at the same time can provide for each associated debt, which is not conducive to risk mitigation of the debts.

[0006] In a first aspect, the present application provides a guarantee relationship data processing method, comprising:

[0007] Acquire the guarantee relationship data to be split from the first database;

[0008] If the guarantee relationship data to be split includes at least one secured debt and multiple secured collaterals, then determining a weight value of each secured collateral according to the collateral information of each secured collateral;

[0009] According to the weight values ​​of the collaterals provided for guarantee and the debt information of the at least one secured debt, the to-be-split guarantee relationship data are split to obtain a plurality of one-to-one guarantee relationship data corresponding to the to-be-split guarantee relationship data; each of the one-to-one guarantee relationship data includes a single debt and a single collateral, which is used to indicate the guarantee resources that the single collateral can provide for the single debt;

[0010] The multiple one-to-one guarantee relationship data corresponding to the guarantee relationship data to be split are stored in the second database.

[0011] In a second aspect, the present application provides a guarantee relationship data processing device, including:

[0012] An acquisition unit, used for acquiring the guarantee relationship data to be split from the first database;

[0013] a determination unit, configured to determine a weight value of each of the collaterals provided for security according to the collateral information of each of the collaterals provided for security if the to-be-split security relationship data includes at least one secured debt and a plurality of collaterals provided for security;

[0014] a splitting unit, configured to split the to-be-split guarantee relationship data according to the weight values ​​of the collaterals providing the guarantee and the debt information of the at least one secured debt, to obtain a plurality of one-to-one guarantee relationship data corresponding to the to-be-split guarantee relationship data; each of the one-to-one guarantee relationship data includes a single debt and a single collateral, and is configured to indicate the guarantee resources that the single collateral can provide for the single debt;

[0015] The storage unit is used to store a plurality of one-to-one guarantee relationship data corresponding to the guarantee relationship data to be split into a second database.

[0016] In a third aspect, the present application provides an electronic device, comprising: a processor, and a memory communicatively connected to the processor; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory to implement the method described in the first aspect above.

[0017] In a fourth aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, they are used to implement the method described in the first aspect above.

[0018] In a fifth aspect, the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the method described in the first aspect above.

[0019] The guarantee relationship data processing method, device and equipment provided in the present application obtain the guarantee relationship data to be split from the first database; if the guarantee relationship data to be split includes at least one secured debt and multiple collaterals providing guarantees, the weight value of each collateral providing guarantees is determined according to the collateral information of each collateral providing guarantees; according to the weight value of each collateral providing guarantees and the debt information of at least one secured debt, the guarantee relationship data to be split is split to obtain multiple one-to-one guarantee relationship data corresponding to the guarantee relationship data to be split; each one-to-one guarantee relationship data includes a single debt and a single collateral, which is used to indicate the guarantee resources that a single collateral can provide for a single debt; and the multiple one-to-one guarantee relationship data corresponding to the guarantee relationship data to be split are stored in the second database. Accordingly, for collateral that provides security for multiple debts at the same time, by splitting the complex security relationship formed by the collateral and all the related debts into a simple one-to-one security relationship, it is possible to obtain the security resources that the collateral can allocate to each related debt respectively, so as to quickly and accurately identify the security capacity and risk mitigation capacity that the collateral can provide for each related debt respectively, facilitate risk mitigation of the debts, serve pre-loan approval and credit management, and reduce post-loan management risks. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0021] Figure 1 is a flowchart of a guarantee relationship data processing method in an exemplary embodiment;

[0022] Figure 2 A schematic diagram of guarantee relationship grouping in an exemplary embodiment;

[0023] Figure 3 is a flow chart of a method for processing guarantee relationship data in another exemplary embodiment;

[0024] Figure 4 A schematic diagram of calculating the collateral weight value based on a full binary tree in an exemplary embodiment;

[0025] Figure 5 is a flow chart of a method for processing guarantee relationship data in another exemplary embodiment;

[0026] Figure 6 It is a schematic diagram of the structure of a guarantee relationship data processing device in an exemplary embodiment;

[0027] Figure 7 is a schematic structural diagram of an electronic device in an exemplary embodiment;

[0028] Figure 8is a block diagram of an electronic device in an exemplary embodiment.

[0029] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

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

[0031] First, the terms involved in this application are explained:

[0032] One-to-one guarantee: refers to a situation where a piece of collateral (the collateral in this article can be a pledge, a deposit, a guarantor or any other object that can provide a guarantee) only guarantees one debt, and the debt is not guaranteed by other collateral.

[0033] Many-to-one guarantee: refers to a situation where one collateral is used to guarantee multiple debts at the same time, and there is no other guarantee relationship under the guaranteed debt.

[0034] One-to-many guarantee: refers to a situation where there are multiple collateral guarantees under one debt, and these collaterals only guarantee this debt.

[0035] Many-to-many guarantees: refers to the situation where there are multiple collateral guarantees under one debt, and these collaterals also guarantee other debts at the same time.

[0036] Collateral ratio: refers to the ratio of the remaining principal amount to the collateral valuation.

[0037] The specific application scenario of this application is the bank risk management system. The bank risk management system can obtain business data from the bank's business system, identify guarantee relationship data from the business data, and determine the guarantee capacity and risk mitigation capacity that the collateral can provide for the associated debts based on the guarantee relationship data, which can be used as a reference for risk management.

[0038] However, as the guarantee relationship between debts and collateral becomes more complicated, it is difficult to accurately identify the guarantee capacity that the collateral can provide for each related debt when it is used to guarantee multiple debts at the same time, which is not conducive to risk mitigation of debts.

[0039] The guarantee relationship data processing method, device and equipment provided in this application are intended to solve the above technical problems in the prior art.

[0040] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0041] In the embodiments of the present application, the collection, storage, use, processing, transmission, provision and disclosure of user personal information involved are in compliance with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0042] Figure 1 is a flowchart of a method for processing guarantee relationship data according to an exemplary embodiment. Figure 1 As shown, the method includes:

[0043] S101, obtaining guarantee relationship data to be split from a first database.

[0044] The execution subject of this embodiment may be a server, a terminal, or a system including a server and a terminal, and there is no limitation on this. This embodiment is introduced with the execution subject being the server where the bank risk management and control system is located.

[0045] The first database may be a backend database of a banking system, which is used to record and store source data related to banking business. The source data includes guarantee-related data, such as guarantee methods and guarantee contract information. Guarantee methods include mortgage, pledge, deposit, single guarantee, multi-person reinsurance, multi-person joint guarantee, credit and other methods. Guarantee contract information includes debt information of the guaranteed debt, collateral information of the collateral provided for guarantee and other information.

[0046] The guarantee relationship between debt and collateral includes four types: one-to-one guarantee, many-to-one guarantee, one-to-many guarantee and many-to-many guarantee. The guarantee relationship data to be split refers to the guarantee relationship data between debt and collateral that forms many-to-one guarantee, one-to-many guarantee or many-to-many guarantee.

[0047] Specifically, the server first obtains the original data from the first database, and extracts the basic indicators (debts and collateral) required for subsequent processing from the original data. Optionally, the server preprocesses the original data, and the preprocessing includes data verification, such as cleaning up redundant data and erroneous data to narrow the calculation scope and improve efficiency; preprocessing can also include data fault-tolerant processing, such as enriching and supplementing the simple recorded information that cannot meet the data requirements for subsequent processing to generate complete data that meets the requirements.

[0048] After preprocessing the original data, the server processes the data based on the basic indicators and the preprocessed data to obtain the guarantee relationship data, which includes the collateral information associated with each debt item and the debt item information associated with each collateral. Then, based on the relationship between the debt item and the collateral, the server identifies the guarantee relationship in the guarantee relationship data as one-to-one guarantee, many-to-one guarantee, one-to-many guarantee, and many-to-many guarantee. The server groups the guarantee relationship data according to the guarantee relationship type, with each group corresponding to one guarantee relationship type, and adds a corresponding type identifier to each group of guarantee relationship data.

[0049] Figure 2 is a schematic diagram of guarantee relationship grouping according to an exemplary embodiment. Figure 2 The left side shows the collateral associated with each debt and the debt associated with each collateral. Figure 2 The right side shows the four types of grouped guarantee relationships. For example, debt 4 is guaranteed by collateral 4 and collateral 5, and collateral 4 and collateral 5 both guarantee debt 5, so debt 4, debt 5, collateral 4 and collateral 5 form a many-to-many guarantee relationship.

[0050] S102: If the guarantee relationship data to be split includes at least one guaranteed debt item and a plurality of collaterals providing guarantees, a weight value of each collateral providing guarantees is determined according to collateral information of each collateral providing guarantees.

[0051] The guarantee relationship data to be split includes at least one guaranteed debt and multiple collaterals providing guarantees, indicating that the guarantee relationship between the debt and the collateral in the guarantee relationship data to be split is a one-to-many guarantee or a many-to-many guarantee. The weight value of the collateral is used to characterize the guarantee capacity of the collateral. The higher the weight value of the collateral, the stronger the guarantee capacity of the collateral, and thus the stronger the ability of the collateral to achieve credit risk mitigation.

[0052] S103, splitting the guarantee relationship data to be split according to the weight value of each collateral providing guarantee and the debt information of at least one secured debt, and obtaining a plurality of one-to-one guarantee relationship data corresponding to the guarantee relationship data to be split; each one-to-one guarantee relationship data includes a single debt and a single collateral, which is used to indicate the guarantee resources that a single collateral can allocate to a single debt.

[0053] The one-to-one guarantee relationship data includes a single debt item and a single collateral, indicating that the guarantee relationship between the debt item and the collateral in the one-to-one guarantee relationship data is a one-to-one guarantee, and indicating the guarantee resources that the single collateral can allocate to the single debt item.

[0054] For example, the guarantee relationship data to be split includes debt 4, debt 5, collateral 4 and collateral 5. Debt 4 is jointly guaranteed by collateral 4 and collateral 5. At the same time, collateral 4 and collateral 5 both provide guarantees for debt 5, so debt 4, debt 5, collateral 4 and collateral 5 form a many-to-many guarantee relationship. By splitting the guarantee relationship data to be split, one-to-one guarantee relationship data between debt 4 and collateral 4, one-to-one guarantee relationship data between debt 4 and collateral 5, one-to-one guarantee relationship data between debt 5 and collateral 4, and one-to-one guarantee relationship data between debt 5 and collateral 5 can be obtained.

[0055] For example, when a debt is secured by multiple collaterals, the question of which collateral to split first arises during the splitting process. Based on the weights of the collaterals providing guarantees, collateral with higher weights can be split first to cover the debt risk exposure.

[0056] S104, storing a plurality of one-to-one guarantee relationship data corresponding to the guarantee relationship data to be split in the second database.

[0057] The second database may be a backend database of a bank's risk management system, which is used to record and store one-to-one guarantee relationship data between debts and collateral, so as to facilitate quick access to guarantee resources that can be allocated to each associated debt by each collateral.

[0058] Optionally, the one-to-one guarantee relationship data identified from the source data is also stored in the second database. Thus, the one-to-one guarantee relationship data stored in the second database includes not only the one-to-one guarantee relationship data obtained after splitting the guarantee relationship data to be split, but also the one-to-one guarantee relationship data identified from the source data, so that the data storage is more complete and it is convenient to carry out risk management in a unified manner.

[0059] In this embodiment, the guarantee relationship data to be split are obtained from the first database; if the guarantee relationship data to be split include at least one secured debt and multiple collaterals providing guarantees, the weight value of each collateral providing guarantees is determined according to the collateral information of each collateral providing guarantees; according to the weight value of each collateral providing guarantees and the debt information of at least one secured debt, the guarantee relationship data to be split are split to obtain multiple one-to-one guarantee relationship data corresponding to the guarantee relationship data to be split; each one-to-one guarantee relationship data includes a single debt and a single collateral, which is used to indicate the guarantee resources that a single collateral can provide for a single debt; the multiple one-to-one guarantee relationship data corresponding to the guarantee relationship data to be split are stored in the second database. Accordingly, for collateral that provides security for multiple debts at the same time, by splitting the complex security relationship formed by the collateral and all the related debts into a simple one-to-one security relationship, it is possible to obtain the security resources that the collateral can allocate to each related debt respectively, so as to quickly and accurately identify the security capacity and risk mitigation capacity that the collateral can provide for each related debt respectively, facilitate risk mitigation of the debts, serve pre-loan approval and credit management, and reduce post-loan management risks.

[0060] Figure 3 is a flowchart of a method for processing guarantee relationship data according to an exemplary embodiment. Figure 3 As shown, the method includes:

[0061] S301, obtaining guarantee relationship data to be split from the first database.

[0062] Exemplarily, the implementation of step S301 is similar to that of step S101 and will not be described in detail here.

[0063] S302: If the guarantee relationship data to be split includes at least one secured debt and multiple collaterals provided as security, then in response to a detection trigger instruction, for any collateral provided as security, detect whether the collateral information of the collateral provided as security meets a preset condition, obtain a detection result of the collateral provided as security, and determine a weight value of each collateral provided as security according to the detection result of each collateral provided as security.

[0064] The detection trigger instruction is used to trigger the execution of the detection of whether the collateral information meets the preset conditions. Optionally, the staff can initiate the detection trigger instruction by performing the corresponding trigger operation on the terminal page running the bank risk management system; after receiving the detection trigger instruction, the server of the bank risk management system detects whether the collateral information of each collateral provided for guarantee meets the preset conditions and obtains the detection results of each collateral provided for guarantee.

[0065] Exemplarily, the preset condition includes a plurality of conditions with priorities; for any collateral provided as security, the step of detecting whether the collateral information of the collateral provided as security meets the preset condition and obtaining the detection result of the collateral provided as security may specifically include the following steps:

[0066] Step 1: sort the multiple conditions in descending order of priority, and use the first-ranked condition as the current condition.

[0067] You can set a priority for each condition in advance. The higher the priority, the greater the impact of the condition on the collateral guarantee capacity. Sort multiple conditions in descending order of priority. The first condition is the condition with the highest priority. Check in order whether the collateral information of the collateral provided for guarantee meets each condition.

[0068] Exemplarily, the preset conditions include, but are not limited to: being in the credit risk mitigation tool pool, belonging to the main guarantee, meeting the guarantee conditions, and the collateral category belonging to the high guarantee capacity category. The higher the priority or the more conditions that the collateral information of the collateral meets, the stronger the guarantee capacity of the collateral.

[0069] Step 2: Check whether the collateral information of the collateral provided for guarantee meets the current condition. If so, determine that the detection value of the current condition is a first value; if not, determine that the detection value of the current condition is a second value; wherein the second value is smaller than the first value.

[0070] For example, assuming that the current condition is "in the credit risk mitigation tool pool", if it is determined based on the collateral information that the collateral is in the credit risk mitigation tool pool, then it is determined that the current condition is met, that is, the current condition test passes; if it is determined based on the collateral information that the collateral is not in the credit risk mitigation tool pool, then it is determined that the current condition is not met, that is, the current condition test fails.

[0071] The second value is smaller than the first value, so that the detection value corresponding to the current condition test passing is greater than the detection value corresponding to the current condition test failing, and the larger the corresponding detection value, the stronger the guarantee ability. Exemplarily, the first value and the second value are both integer values. Optionally, the first value is 1 and the second value is 0. For example, for a certain collateral 1, if the collateral information of collateral 1 meets the current condition (the current condition at this time is the first-order condition), the detection value of collateral 1 under the first-order condition is 1.

[0072] Step 3: Take the next highest condition under the current condition as the new current condition and return to step 2 until the detection values ​​of all conditions are determined.

[0073] After the current condition (the current condition at this time is the condition of the first priority) is detected, the condition of the next priority under the current condition (i.e., the condition of the second priority) is used as the new current condition, and step 2 is returned to execute, i.e., whether the collateral information of the collateral provided for guarantee meets the current condition, if so, the detection value of the current condition is determined to be the first value, if not, the detection value of the current condition is determined to be the second value. For example, for a certain collateral 1, if the collateral information of collateral 1 meets the current condition (the current condition at this time is the condition of the second priority), the detection value of collateral 1 under the condition of the second priority is 1. And so on, until the detection values ​​of all conditions are determined. For example, if the preset conditions include N conditions, N detection values ​​can be obtained, where N is a positive integer.

[0074] Step 4: Combine the test values ​​of all determined conditions to obtain the test results of the collateral provided for guarantee.

[0075] Exemplarily, there are four preset conditions, and the detection values ​​of the collateral obtained in order of priority from high to low under each condition are 1, 1, 1, 1 respectively, then the detection result of the collateral is 1111, and then the weight value of the collateral can be determined to be 1111. After obtaining the detection result of the collateral, the detection result of the collateral is used as the weight value of the collateral.

[0076] In one example, the weight of the collateral is calculated based on a full binary tree. In a full binary tree, except for the last layer of nodes, all nodes on each layer have two child nodes. Based on the full binary tree calculation method, the weight of the collateral or debt in the guarantee relationship can be quantified, which can more objectively and accurately reflect the guarantee capacity of the collateral or the risk of the debt, and has better versatility.

[0077] Figure 4 is a schematic diagram showing a method of calculating a collateral weight value based on a full binary tree according to an exemplary embodiment. Figure 4 As shown, risk factor 1, risk factor 2, risk factor 3 and risk factor 4 represent the preset conditions in the above embodiment, and the priority is reduced in sequence. First, the operation of risk factor 1 is performed, and a pass is recorded as 1, and a fail is recorded as 0. The operation here is to detect whether the collateral information of the collateral meets the corresponding risk factor; based on the operation of risk factor 1, the operation of risk factor 2 is performed, and a pass is recorded as 1, and a fail is recorded as 0; based on the operation of risk factor 2, the operation of risk factor 3 is performed, and a pass is recorded as 1, and a fail is recorded as 0; based on the operation of risk factor 3, the operation of risk factor 4 is performed, and a pass is recorded as 1, and a fail is recorded as 0. By analogy, after completing 4 risk factor operations, 16 weight values ​​with binary codes of 0000-1111 will be generated.

[0078] After obtaining the weight value of each collateral through risk factor calculation, the collateral is sorted in order from high to low in terms of weight value to obtain the initial sorting result of the collateral. For example, if some of the sorting values ​​in the initial sorting result are the same, the collateral is sorted again according to other factors such as the pledge rate and the collateral revaluation rate. For example, when other conditions are the same, the higher the pledge rate or collateral revaluation rate of the collateral is, the higher its ranking is.

[0079] S303, in response to the first split trigger instruction, sort the collaterals provided for guarantee in descending order of weight value, and use the collateral with the first priority as the current collateral.

[0080] The first split trigger instruction is used to trigger the execution of splitting the collateral so as to allocate its guarantee resources to the associated debt items. Optionally, the staff can initiate the first split trigger instruction by performing a corresponding trigger operation on the terminal page running the bank risk management system; after the server of the bank risk management system receives the first split trigger instruction, it starts to split the collateral.

[0081] The collaterals are sorted in order from high to low according to the weight value. The first collateral is the collateral with the highest weight value, and each collateral is split in order.

[0082] S304: judging whether the current collateral meets the full coverage condition based on the debt information of at least one secured debt and the collateral information of the current collateral, and obtaining a judgment result of the current collateral.

[0083] Exemplarily, the full coverage condition includes the following two conditions: the current collateral guarantee amount is greater than or equal to the sum of the debt item balances of the debt exposure details associated with the current collateral; the guarantee contract amount of the guarantee contract where the current collateral is located is greater than or equal to the sum of the debt item balances of the debt exposure details of the guarantee contract. If the current collateral satisfies both of the above conditions, it is determined that the current collateral satisfies the full coverage condition; if the current collateral does not satisfy both of the above conditions, it is determined that the current collateral does not satisfy the full coverage condition.

[0084] S305, using a splitting strategy corresponding to the judgment result of the current collateral, allocating the guarantee resources of the current collateral to each secured debt item, and obtaining one-to-one guarantee relationship data corresponding to the current collateral.

[0085] The judgment results of the current collateral include two situations: the current collateral meets the full coverage conditions and the current collateral does not meet the full coverage conditions. Different situations correspond to different splitting strategies.

[0086] In one example, if the judgment result indicates that the current collateral meets the full coverage condition, the guarantee resources of the current collateral are allocated to each guaranteed debt item in proportion, and multiple one-to-one guarantee relationship data corresponding to the current collateral are obtained.

[0087] The guarantee resources include distributable value and guarantee amount; the guarantee resources of the current collateral are distributed to each secured debt in proportion, including: for any debt, the to-be-distributed ratio of the debt is obtained based on the ratio of the exposed balance of the debt to the sum of the exposed balances of all debts; the to-be-distributed value of the debt is obtained based on the product of the to-be-distributed ratio of the debt and the distributable value of the current collateral, and the to-be-distributed value is distributed to the debt; the to-be-distributed guarantee amount of the debt is obtained based on the product of the to-be-distributed value of the debt and the pledge rate of the current collateral, and the to-be-distributed guarantee amount is distributed to the debt.

[0088] For any debt exposure item i associated with the current collateral, the proportion of debt exposure item i to be allocated Wi = Yi / SumY, where Yi represents the exposure balance of debt exposure item i, and SumY represents the sum of the exposure balances of all debt exposure items. The value to be allocated Vi of debt exposure item i = Wi*V, where V represents the distributable value of the current collateral. The amount of collateral to be allocated Ei of debt exposure item i = Vi*k, where k represents the pledge ratio of the current collateral. The coverage amount of debt exposure item i Fi = Yi.

[0089] In one example, if the judgment result indicates that the current collateral does not meet the full coverage condition, the guarantee resources of the current collateral are allocated to each guaranteed debt item in order from high to low debt risk, and the one-to-one guarantee relationship data corresponding to the current collateral is obtained.

[0090] Exemplarily, based on the preset ranking factors and ranking rules, the risks of the debts associated with the current collateral are ranked. A priority can be set in advance for each ranking factor, and the higher the priority, the greater the impact of the ranking factor on the debt risk. Optionally, the ranking factors may include but are not limited to factors such as loan contracts, loan certificates, risk exposure types, loan amounts, and repayment periods.

[0091] For example, assuming there are M ranking factors, the order of debt m and debt n can be determined by the following conditions: compare whether the ranking factor 1 of debt m is the same as the ranking factor 1 of debt m, if not, sort according to ranking factor 1; if so, compare whether the ranking factor 2 of debt m is the same as the ranking factor 2 of debt m, if not, sort according to ranking factor 2; if so, compare whether the ranking factor 3 of debt m is the same as the ranking factor 3 of debt m, and so on; and so on, to obtain the risk ranking of all debts associated with the current collateral.

[0092] In order of the risk of the debt item from high to low, the collateral resources of the current collateral are allocated to the debt exposure details under each debt item one by one. Optionally, when the last debt exposure detail is allocated, regardless of whether the remaining allocable value of the collateral can cover the risk exposure of the detail, the remaining allocable value of the collateral will be allocated to the current debt exposure detail.

[0093] S306, taking the collateral that is next in rank to the current collateral as the new current collateral, and returning to the step of determining whether the current collateral meets the full coverage condition based on the debt information of at least one secured debt and the collateral information of the current collateral, until a plurality of one-to-one guarantee relationship data corresponding to all the collaterals are obtained.

[0094] After the current collateral (the current collateral at this time is the collateral of the first priority) is split, the collateral of the next priority of the current collateral (i.e. the collateral of the second priority) is used as the new current collateral, and the process returns to step S304 to step S305 to obtain the one-to-one guarantee relationship data corresponding to the collateral of the second priority. This process is repeated in this way until multiple one-to-one guarantee relationship data corresponding to all collaterals are obtained.

[0095] S307, obtaining multiple one-to-one guarantee relationship data corresponding to the guarantee relationship data to be split according to the multiple one-to-one guarantee relationship data corresponding to all the collaterals obtained; each one-to-one guarantee relationship data includes a single debt item and a single collateral, which is used to indicate the guarantee resources that a single collateral can allocate to a single debt item.

[0096] For example, the guarantee relationship data to be split includes debt 4, debt 5, collateral 4 and collateral 5. Debt 4 is jointly guaranteed by collateral 4 and collateral 5, and collateral 4 and collateral 5 both provide guarantees for debt 5, so that debt 4, debt 5, collateral 4 and collateral 5 form a many-to-many guarantee relationship. By splitting collateral 4, one-to-one guarantee relationship data between debt 4 and collateral 4 and one-to-one guarantee relationship data between debt 5 and collateral 4 can be obtained; by splitting collateral 5, one-to-one guarantee relationship data between debt 4 and collateral 5 and one-to-one guarantee relationship data between debt 5 and collateral 5 can be obtained. The multiple one-to-one guarantee relationship data corresponding to the guarantee relationship data to be split include the one-to-one guarantee relationship data between debt 4 and collateral 4, between debt 5 and collateral 4, between debt 4 and collateral 5, and between debt 5 and collateral 5.

[0097] S308, storing a plurality of one-to-one guarantee relationship data corresponding to the guarantee relationship data to be split in the second database.

[0098] Exemplarily, the implementation of step S308 is similar to that of step S104 and will not be described in detail here.

[0099] Figure 5is a flowchart of a method for processing guarantee relationship data according to an exemplary embodiment. Figure 5 As shown, the method includes:

[0100] S501, obtaining guarantee relationship data to be split from the first database.

[0101] Exemplarily, the implementation of step S501 is similar to that of step S101 and will not be described in detail here.

[0102] S502, if the guarantee relationship data to be split includes multiple guaranteed debts and one collateral provided as guarantee, then in response to the second split trigger instruction, based on the debt information of the multiple guaranteed debts and the collateral information of the collateral provided as guarantee, it is determined whether the collateral provided as guarantee meets the full coverage condition, and a determination result of the collateral provided as guarantee is obtained.

[0103] The guarantee relationship data to be split includes multiple guaranteed debts and one collateral providing guarantee, indicating that the guarantee relationship between the debts and the collateral in the guarantee relationship data to be split is a many-to-one guarantee.

[0104] The second split trigger instruction is used to trigger the execution of splitting the collateral provided for guarantee, so as to allocate the guarantee resources of the collateral to the associated debt items. Optionally, the staff can initiate the second split trigger instruction by performing a corresponding trigger operation on the terminal page of the bank risk management system; after receiving the second split trigger instruction, the server of the bank risk management system starts to split the collateral.

[0105] For example, the full coverage condition includes the following two conditions: the collateral guarantee amount is greater than or equal to the sum of the debt item balances of the debt exposure items associated with the collateral; the guarantee contract amount of the guarantee contract where the collateral is located is greater than or equal to the sum of the debt item balances of the debt exposure items of the guarantee contract. If the collateral meets the above two conditions at the same time, it is determined that the collateral meets the full coverage condition; if the collateral does not meet the above two conditions at the same time, it is determined that the collateral does not meet the full coverage condition.

[0106] S503, using a splitting strategy corresponding to the judgment result of the collateral provided for guarantee, allocating the guarantee resources of the collateral provided for guarantee to each secured debt, and obtaining a plurality of one-to-one guarantee relationship data corresponding to the guarantee relationship data to be split.

[0107] The judgment results of the collateral include two situations: the collateral meets the full coverage conditions and the collateral does not meet the full coverage conditions. Different situations correspond to different splitting strategies.

[0108] In one example, if the judgment result indicates that the collateral meets the full coverage condition, the collateral's guarantee resources are allocated proportionally to each secured debt, and multiple one-to-one guarantee relationship data corresponding to the collateral are obtained, that is, multiple one-to-one guarantee relationship data corresponding to the guarantee relationship data to be split are obtained. The implementation method of proportional allocation is similar to the previous embodiment and will not be repeated here.

[0109] In one example, if the judgment result indicates that the collateral does not meet the full coverage condition, the collateral resources are allocated to each secured debt item in order of high to low debt risk, and the one-to-one guarantee relationship data corresponding to the collateral is obtained, that is, multiple one-to-one guarantee relationship data corresponding to the guarantee relationship data to be split are obtained. The implementation method of allocating in order of high to low debt risk is similar to the previous embodiment and will not be repeated here.

[0110] S504: Store multiple one-to-one guarantee relationship data corresponding to the guarantee relationship data to be split into a second database.

[0111] Exemplarily, the implementation of step S504 is similar to that of step S104 and will not be described in detail here.

[0112] Through the above embodiments, the complex guarantee relationship between debt and collateral is split into a simple one-to-one relationship, and the distributable value of the collateral (or the guarantee liability provided by the guarantor) is allocated to the risk exposure of the debt associated with it, so as to achieve the risk mitigation effect of these debts, and the collateral with the strongest credit risk mitigation ability can be preferentially used to cover the debt exposure with the highest risk level, so as to minimize the risk-weighted capital.

[0113] Figure 6 is a schematic diagram of the structure of a guarantee relationship data processing device according to an exemplary embodiment. The device can be a software module or a hardware module, or a combination of the two to form a part of a computer device, such as Figure 6 As shown, the device 600 includes:

[0114] The acquisition unit 610 is used to acquire the guarantee relationship data to be split from the first database.

[0115] The determination unit 620 is configured to determine a weight value of each collateral provided for security according to the collateral information of each collateral provided for security if the security relationship data to be split includes at least one secured debt item and a plurality of collateral provided for security.

[0116] The splitting unit 630 is used to split the guarantee relationship data to be split according to the weight value of each collateral provided for guarantee and the debt information of at least one secured debt, so as to obtain multiple one-to-one guarantee relationship data corresponding to the guarantee relationship data to be split; each one-to-one guarantee relationship data includes a single debt and a single collateral, which is used to indicate the guarantee resources that a single collateral can allocate to a single debt.

[0117] The storage unit 640 is used to store the multiple one-to-one guarantee relationship data corresponding to the guarantee relationship data to be split into the second database.

[0118] In one example, when determining the weight value of each collateral provided by security according to the collateral information of each collateral provided by security, the determination unit 620 is specifically used to: in response to a detection trigger instruction, for any collateral provided by security, detect whether the collateral information of the collateral provided by security meets a preset condition, and obtain a detection result of the collateral provided by security; and determine the weight value of each collateral provided by security according to the detection result of each collateral provided by security.

[0119] In one example, the preset condition includes a plurality of conditions with priorities; when the determination unit 620 detects whether the collateral information of the collateral provided for security meets the preset condition and obtains the detection result of the collateral provided for security, it is specifically used to: sort the plurality of conditions in descending order of priority, and use the condition with the first priority as the current condition; detect whether the collateral information of the collateral provided for security meets the current condition, and if so, determine that the detection value of the current condition is a first value, and if not, determine that the detection value of the current condition is a second value; wherein the second value is less than the first value; use the condition with the next priority under the current condition as the new current condition, and return to the step of detecting whether the collateral information of the collateral provided for security meets the current condition, until the detection values ​​of all conditions are determined; and combine the determined detection values ​​of all conditions to obtain the detection result of the collateral provided for security.

[0120] In one example, when the splitting unit 630 splits the guarantee relationship data to be split according to the weight value of each collateral provided for guarantee and the debt information of at least one secured debt, and obtains a plurality of one-to-one guarantee relationship data corresponding to the guarantee relationship data to be split, the splitting unit 630 is specifically used to: in response to the first splitting trigger instruction, sort the collaterals provided for guarantee in descending order of weight value, and use the collateral with the first priority as the current collateral; judge whether the current collateral meets the full coverage condition according to the debt information of at least one secured debt and the collateral information of the current collateral, and obtain the judgment result of the current collateral. ; adopting a splitting strategy corresponding to the judgment result of the current collateral, allocating the guarantee resources of the current collateral to each secured debt, and obtaining one-to-one guarantee relationship data corresponding to the current collateral; taking the collateral of the next highest rank of the current collateral as the new current collateral, and returning to the step of judging whether the current collateral meets the full coverage condition according to the debt information of at least one secured debt and the collateral information of the current collateral, until obtaining multiple one-to-one guarantee relationship data corresponding to all the collaterals; obtaining multiple one-to-one guarantee relationship data corresponding to the guarantee relationship data to be split according to the obtained multiple one-to-one guarantee relationship data corresponding to all the collaterals.

[0121] In one example, when the splitting unit 630 adopts a splitting strategy corresponding to the judgment result of the current collateral, allocates the guarantee resources of the current collateral to each secured debt, and obtains one-to-one guarantee relationship data corresponding to the current collateral, it is specifically used to: if the judgment result indicates that the current collateral meets the full coverage condition, then allocate the guarantee resources of the current collateral to each secured debt in proportion, and obtain multiple one-to-one guarantee relationship data corresponding to the current collateral; if the judgment result indicates that the current collateral does not meet the full coverage condition, then allocate the guarantee resources of the current collateral to each secured debt in sequence according to the order of debt risk from high to low, and obtain multiple one-to-one guarantee relationship data corresponding to the current collateral.

[0122] In one example, the guarantee resources include distributable value and guarantee amount; when the splitting unit 630 distributes the guarantee resources of the current collateral to each secured debt item in proportion, it is specifically used to: for any debt item, obtain the to-be-distributed proportion of the debt item according to the ratio of the exposed balance of the debt item to the sum of the exposed balances of all debt items; obtain the to-be-distributed value of the debt item according to the product of the to-be-distributed proportion of the debt item and the distributable value of the current collateral, and distribute the to-be-distributed value to the debt item; obtain the to-be-distributed guarantee amount of the debt item according to the product of the to-be-distributed value of the debt item and the pledge rate of the current collateral, and distribute the to-be-distributed guarantee amount to the debt item.

[0123] In one example, the splitting unit 630 is also used for: if the guarantee relationship data to be split includes multiple secured debts and one collateral for providing guarantee, then in response to the second split trigger instruction, judging whether the collateral for providing guarantee meets the full coverage condition according to the debt information of the multiple secured debts and the collateral information of the collateral for providing guarantee, and obtaining the judgment result of the collateral for providing guarantee; adopting a splitting strategy corresponding to the judgment result of the collateral for providing guarantee, allocating the guarantee resources of the collateral for providing guarantee to each secured debt, and obtaining multiple one-to-one guarantee relationship data corresponding to the guarantee relationship data to be split.

[0124] Figure 7 It is a structural diagram of an electronic device according to an exemplary embodiment, which includes: a processor 701, and a memory 702 communicatively connected to the processor 701; the memory 702 stores computer execution instructions; the processor 701 executes the computer execution instructions stored in the memory 702 to implement the guarantee relationship data processing method provided in the above embodiment.

[0125] The electronic device further includes a receiver 703 and a transmitter 704. The receiver 703 is used to receive instructions and data sent by an external device, and the transmitter 704 is used to send instructions and data to the external device.

[0126] Figure 8 It is a block diagram of a terminal device according to an exemplary embodiment. The device may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.

[0127] The device 800 may include one or more of the following components: a processing component 802 , a memory 804 , a power component 806 , a multimedia component 808 , an audio component 810 , an input / output (I / O) interface 812 , a sensor component 814 , and a communication component 816 .

[0128] The processing component 802 generally controls the overall operation of the device 800, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 802 may include one or more processors 820 to execute instructions to complete all or part of the steps of the above-mentioned method. In addition, the processing component 802 may include one or more modules to facilitate the interaction between the processing component 802 and other components. For example, the processing component 802 may include a multimedia module to facilitate the interaction between the multimedia component 808 and the processing component 802.

[0129] The memory 804 is configured to store various types of data to support operations on the device 800. Examples of such data include instructions for any application or method operating on the device 800, contact data, phone book data, messages, pictures, videos, etc. The memory 804 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0130] The power supply component 806 provides power to the various components of the device 800. The power supply component 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device 800.

[0131] The multimedia component 808 includes a screen that provides an output interface between the device 800 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 808 includes a front camera and / or a rear camera. When the device 800 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

[0132] The audio component 810 is configured to output and / or input audio signals. For example, the audio component 810 includes a microphone (MIC), and when the device 800 is in an operating mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in the memory 804 or sent via the communication component 816. In some embodiments, the audio component 810 also includes a speaker for outputting audio signals.

[0133] I / O interface 812 provides an interface between processing component 802 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include but are not limited to: home button, volume button, start button, and lock button.

[0134] The sensor assembly 814 includes one or more sensors for providing various aspects of status assessment for the device 800. For example, the sensor assembly 814 can detect the open / closed state of the device 800, the relative positioning of components, such as the display and keypad of the device 800, the sensor assembly 814 can also detect the position change of the device 800 or a component of the device 800, the presence or absence of user contact with the device 800, the orientation or acceleration / deceleration of the device 800 and the temperature change of the device 800. The sensor assembly 814 can include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 814 can also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 814 can also include an accelerometer, a gyroscope sensor, a magnetic sensor, a pressure sensor or a temperature sensor.

[0135] The communication component 816 is configured to facilitate wired or wireless communication between the device 800 and other devices. The device 800 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 816 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 816 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0136] In an exemplary embodiment, the apparatus 800 may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors or other electronic components to perform the above method.

[0137] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 804 including instructions, and the instructions can be executed by the processor 820 of the device 800 to perform the above method. For example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0138] An embodiment of the present application also provides a non-temporary computer-readable storage medium. When the instructions in the storage medium are executed by a processor of a computer device, the computer device is enabled to execute the method provided in any of the above embodiments.

[0139] An embodiment of the present invention also provides a computer program product, which includes: a computer program, the computer program is stored in a readable storage medium, at least one processor of a computer device can read the computer program from the readable storage medium, and at least one processor executes the computer program so that the computer device executes the method provided in any of the above embodiments.

[0140] It should be understood that the terms "first", "second", etc. in the above embodiments are only used for descriptive purposes and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. In addition, in the description of this application, unless otherwise specified, the meaning of "multiple" refers to at least two.

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

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

Claims

1. A method for processing guarantee relationship data, characterized in that: The method comprises: Acquire the guarantee relationship data to be split from the first database; If the guarantee relationship data to be split includes at least one secured debt and multiple secured collaterals, then determining a weight value of each secured collateral according to the collateral information of each secured collateral; According to the weight values ​​of the collaterals provided for guarantee and the debt information of the at least one secured debt, the to-be-split guarantee relationship data are split to obtain a plurality of one-to-one guarantee relationship data corresponding to the to-be-split guarantee relationship data; each of the one-to-one guarantee relationship data includes a single debt and a single collateral, and is used to indicate the guarantee resources that the single collateral can allocate to the single debt; storing a plurality of one-to-one guarantee relationship data corresponding to the guarantee relationship data to be split into a second database; According to the weight values ​​of the collaterals provided for guarantee and the debt information of the at least one secured debt, the guarantee relationship data to be split are split to obtain a plurality of one-to-one guarantee relationship data corresponding to the guarantee relationship data to be split, including: In response to the first split trigger instruction, the collaterals provided for guarantee are sorted in descending order of weight value, and the collateral with the first priority is used as the current collateral; According to the debt information of the at least one secured debt and the collateral information of the current collateral, determine whether the current collateral meets the full coverage condition, and obtain the determination result of the current collateral; wherein the full coverage condition includes the following two conditions: the current collateral guarantee amount is greater than or equal to the sum of the debt item balances of the debt exposure details associated with the current collateral; the guarantee contract amount of the guarantee contract where the current collateral is located is greater than or equal to the sum of the debt item balances of the debt exposure details of the guarantee contract; If the judgment result indicates that the current collateral meets the full coverage condition, the guarantee resources of the current collateral are allocated to each of the guaranteed debts in proportion, and a plurality of one-to-one guarantee relationship data corresponding to the current collateral are obtained; If the judgment result indicates that the current collateral does not meet the full coverage condition, the guarantee resources of the current collateral are allocated to each of the guaranteed debts in order from high to low risk of the debts, and a plurality of one-to-one guarantee relationship data corresponding to the current collateral are obtained; The collateral with the next highest priority of the current collateral is used as the new current collateral, and the step of judging whether the current collateral meets the full coverage condition according to the debt information of the at least one secured debt and the collateral information of the current collateral is returned until a plurality of one-to-one guarantee relationship data corresponding to all the collaterals are obtained; According to the obtained multiple one-to-one guarantee relationship data corresponding to all collaterals, multiple one-to-one guarantee relationship data corresponding to the guarantee relationship data to be split are obtained.

2. The method according to claim 1, characterized in that Determining the weight value of each of the collaterals provided for security according to the collateral information of each of the collaterals provided for security, including: In response to the detection trigger instruction, for any of the collateral provided as security, detecting whether the collateral information of the collateral provided as security meets a preset condition, and obtaining a detection result of the collateral provided as security; According to the detection results of each of the collaterals provided as security, a weight value of each of the collaterals provided as security is determined.

3. The method according to claim 2, characterized in that The preset conditions include a plurality of conditions with priorities; Detecting whether the collateral information of the collateral provided for guarantee meets a preset condition and obtaining the detection result of the collateral provided for guarantee includes: Sorting the plurality of conditions in descending order of priority, and taking the first-ranked condition as the current condition; Detecting whether the collateral information of the collateral provided for guarantee meets the current condition, and if so, determining that the detection value of the current condition is a first value, and if not, determining that the detection value of the current condition is a second value; wherein the second value is less than the first value; Taking the next-highest condition under the current condition as the new current condition, returning to the step of detecting whether the collateral information of the collateral provided for guarantee meets the current condition, until the detection values ​​of all conditions are determined; The test values ​​of all determined conditions are combined to obtain the test result of the collateral provided for guarantee.

4. The method according to claim 1, characterized in that The security resources include distributable value and security amount; Allocate the collateral resources of the current collateral to each of the secured debts in proportion, including: For any of the debt items, the proportion of the debt item to be distributed is obtained based on the ratio of the exposure balance of the debt item to the sum of the exposure balances of all debt items; Obtain the value of the debt to be distributed according to the product of the proportion of the debt to be distributed and the distributable value of the current collateral, and distribute the value to be distributed to the debt; The guarantee amount to be allocated of the debt is obtained according to the product of the value to be allocated of the debt and the pledge rate of the current collateral, and the guarantee amount to be allocated is allocated to the debt.

5. The method according to claim 1, characterized in that: Also includes: If the to-be-split guarantee relationship data includes a plurality of secured debts and a collateral for providing security, in response to the second split trigger instruction, judging whether the collateral for providing security meets the full coverage condition according to the debt information of the plurality of secured debts and the collateral information of the collateral for providing security, and obtaining a judgment result of the collateral for providing security; A splitting strategy corresponding to the judgment result of the collateral provided for guarantee is adopted to allocate the guarantee resources of the collateral provided for guarantee to each of the secured debts, and obtain a plurality of one-to-one guarantee relationship data corresponding to the guarantee relationship data to be split.

6. A guarantee relationship data processing device, characterized in that: The device comprises: An acquisition unit, used for acquiring the guarantee relationship data to be split from the first database; a determination unit, configured to determine a weight value of each of the collaterals provided for security according to the collateral information of each of the collaterals provided for security if the to-be-split security relationship data includes at least one secured debt and a plurality of collaterals provided for security; a splitting unit, configured to split the to-be-split guarantee relationship data according to the weight values ​​of the collaterals provided for guarantee and the debt information of the at least one secured debt, to obtain a plurality of one-to-one guarantee relationship data corresponding to the to-be-split guarantee relationship data; each of the one-to-one guarantee relationship data includes a single debt and a single collateral, and is configured to indicate the guarantee resources that the single collateral can allocate to the single debt; A storage unit, used for storing a plurality of one-to-one guarantee relationship data corresponding to the guarantee relationship data to be split into a second database; In response to the first split trigger instruction, the collaterals provided for guarantee are sorted in descending order of weight value, and the collateral with the first priority is used as the current collateral; According to the debt information of the at least one secured debt and the collateral information of the current collateral, determine whether the current collateral meets the full coverage condition, and obtain the determination result of the current collateral; wherein the full coverage condition includes the following two conditions: the current collateral guarantee amount is greater than or equal to the sum of the debt item balances of the debt exposure details associated with the current collateral; the guarantee contract amount of the guarantee contract where the current collateral is located is greater than or equal to the sum of the debt item balances of the debt exposure details of the guarantee contract; If the judgment result indicates that the current collateral meets the full coverage condition, the guarantee resources of the current collateral are allocated to each of the guaranteed debts in proportion, and a plurality of one-to-one guarantee relationship data corresponding to the current collateral are obtained; If the judgment result indicates that the current collateral does not meet the full coverage condition, the guarantee resources of the current collateral are allocated to each of the guaranteed debts in order from high to low risk of the debts, and a plurality of one-to-one guarantee relationship data corresponding to the current collateral are obtained; The collateral with the next highest priority of the current collateral is used as the new current collateral, and the step of judging whether the current collateral meets the full coverage condition according to the debt information of the at least one secured debt and the collateral information of the current collateral is returned until a plurality of one-to-one guarantee relationship data corresponding to all the collaterals are obtained; According to the obtained multiple one-to-one guarantee relationship data corresponding to all collaterals, multiple one-to-one guarantee relationship data corresponding to the guarantee relationship data to be split are obtained.

7. An electronic device comprising: A processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the method according to any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 5 when executed by a processor.

Images