Verification task assignment method and device, computer device and storage medium

Abstract

This application discloses a method, apparatus, computer equipment, storage medium, and computer program product for task assignment, relating to the field of big data analytics. The method includes: acquiring suspicious information about a loan event; analyzing the suspicious information to determine its attribute data and verification tasks; determining the verification process for the tasks based on the attribute data; assigning the verification tasks to the processing objects corresponding to the starting verification nodes according to the verification process, with the processing objects verifying the suspicious information based on the corresponding verification dimensions; and when receiving processing feedback from a verification node, if it is determined that there is a next verification node in the verification process, assigning the verification task to the processing object corresponding to the next verification node, until all verification nodes in the verification process are completed. This method can automatically, accurately, and efficiently assign verification tasks to the corresponding processing objects, improving the efficiency of task assignment.

Description

Technical Field

[0001] This application relates to the field of big data analytics, and in particular to a method, apparatus, computer equipment, storage medium, and computer program product for verifying task assignment. Background Technology

[0002] With the development of internet technology, it has been widely applied in various fields, such as the economic and financial sector. The application of internet technology in the economic and financial field has driven the rapid development of the economy and finance. The demand for loans from businesses and individuals has gradually increased, leading to more and more risks throughout the loan cycle. Therefore, loan early warning work is of great significance before, during, and after the loan process.

[0003] Existing loan alerts, which rely on manual alerting by relevant personnel, can increase the accuracy and flexibility of the alerting process, but they are not suitable for large-scale data scenarios. Alternatively, pre-screening of massive amounts of data followed by verification of suspicious information by business personnel results in low efficiency in task allocation for verification. Summary of the Invention

[0004] Therefore, it is necessary to provide a method, apparatus, computer equipment, computer-readable storage medium, and computer program product for assigning verification tasks that can improve the efficiency of verification task assignment, in order to address the above-mentioned technical problems.

[0005] Firstly, this application provides a method for verifying task assignment. The method includes:

[0006] Obtain information about suspicious aspects of the loan incident;

[0007] The suspicious information is analyzed to determine its attribute data and verification tasks.

[0008] The verification process of the verification task is determined based on the attribute data of the suspicious information. The verification process includes at least one verification node, and each verification node of the verification process has at least one different verification dimension.

[0009] According to the verification process, the verification task is assigned to the processing object corresponding to the starting verification node, and the processing object verifies the suspicious information according to the corresponding verification dimensions;

[0010] When the processing feedback of the verification node is received, if it is determined that there is a next verification node in the verification process, the verification task is assigned to the processing object corresponding to the next verification node until all verification nodes in the verification process are completed.

[0011] In one embodiment, analyzing the suspicious information and determining the verification task for the suspicious information includes:

[0012] The suspicious information is analyzed to determine the first identifier of the suspicious information;

[0013] Determine the task generation method parameters that match the first identifier from the preset verification parameter library;

[0014] The task for verifying the suspicious information is generated based on the task generation method parameters.

[0015] In one embodiment, generating a verification task for the suspicious information based on the task generation method parameters includes:

[0016] Determine the verification dimensions corresponding to the task generation method parameters;

[0017] Determine the verification information corresponding to the verification dimension from the suspicious information;

[0018] A verification task is generated based on the verification information.

[0019] In one embodiment, the attribute data includes the type of suspicious event and information about the event initiator. The step of determining the verification process for the verification task based on the attribute data of the suspicious event information includes:

[0020] Determine task assignment parameters that match the type of suspicion and the information of the event initiator from the preset verification parameter library;

[0021] The verification process for the verification task is determined based on the task assignment parameters; the task assignment parameters include at least two verification nodes, and there is a sequential execution order among the verification nodes.

[0022] In one embodiment, according to the verification process, the verification task is assigned to the processing object corresponding to the starting verification node, including:

[0023] Determine the idle processing object of the node to be checked;

[0024] Obtain the event response level and current unprocessed quantity of each idle processing object;

[0025] The processing object is determined from the idle processing objects based on the event response level and the current unprocessed amount;

[0026] The verification task is assigned to the processing object.

[0027] In one embodiment, the method further includes:

[0028] Receive the target verification result fed back by the terminal where the processing object is located;

[0029] If the target verification result is abnormal, risk prediction is performed on the verification task to determine the risk level of the verification task.

[0030] Secondly, this application also provides a verification task assignment device. The device includes:

[0031] The information acquisition module is used to acquire suspicious information about loan events;

[0032] The data processing module is used to analyze the suspicious information, determine the attribute data of the suspicious information, and identify the verification tasks.

[0033] The verification process determination module is used to determine the verification process of the verification task based on the attribute data of the suspicious information. The verification process includes at least one verification node, and each verification node of the verification process has at least one different verification dimension.

[0034] The task assignment module is used to assign the verification task to the processing object corresponding to the starting verification node according to the verification process, and the processing object verifies the suspicious information according to the corresponding verification dimension.

[0035] When the processing feedback of the verification node is received, if it is determined that there is a next verification node in the verification process, the verification task is assigned to the processing object corresponding to the next verification node until all verification nodes in the verification process are completed.

[0036] In one embodiment, the data processing module is further configured to analyze the suspicious information and determine a first identifier of the suspicious information;

[0037] The device further includes:

[0038] The data matching module is used to determine the task generation method parameters that match the first identifier from the preset verification parameter library;

[0039] The data processing module is also used to generate a verification task for the suspicious information based on the task generation method parameters.

[0040] In one embodiment, the data processing module is further configured to determine the verification dimension corresponding to the task generation method parameter;

[0041] Determine the verification information corresponding to the verification dimension from the suspicious information;

[0042] A verification task is generated based on the verification information.

[0043] In one embodiment, the verification process determination module is further configured to determine task assignment parameters that match the type of suspicion and the event initiator information from a preset verification parameter library;

[0044] The verification process for the verification task is determined based on the task assignment parameters; the task assignment parameters include at least two verification nodes, and there is a sequential execution order among the verification nodes.

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

[0046] The idle processing object determination module is used to determine the idle processing object of the starting verification node;

[0047] Obtain the event response level and current unprocessed quantity of each idle processing object;

[0048] The target idle processing object is determined from the idle processing objects based on the event response level and the current unprocessed amount;

[0049] The task assignment module is also used to assign the verification task to the target idle processing object.

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

[0051] The risk prediction module is used to receive the target verification results fed back by the terminal where the processing object is located;

[0052] If the target verification result is abnormal, risk prediction is performed on the verification task to determine the risk level of the verification task.

[0053] Thirdly, this application also provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to perform the following steps:

[0054] Obtain information about suspicious aspects of the loan incident;

[0055] The suspicious information is analyzed to determine its attribute data and verification tasks.

[0056] The verification process of the verification task is determined based on the attribute data of the suspicious information. The verification process includes at least one verification node, and each verification node of the verification process has at least one different verification dimension.

[0057] According to the verification process, the verification task is assigned to the processing object corresponding to the starting verification node, and the processing object verifies the suspicious information according to the corresponding verification dimensions;

[0058] When the processing feedback of the verification node is received, if it is determined that there is a next verification node in the verification process, the verification task is assigned to the processing object corresponding to the next verification node until all verification nodes in the verification process are completed.

[0059] Fourthly, this application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program thereon, which, when executed by a processor, performs the following steps:

[0060] Obtain information about suspicious aspects of the loan incident;

[0061] The suspicious information is analyzed to determine its attribute data and verification tasks.

[0062] The verification process of the verification task is determined based on the attribute data of the suspicious information. The verification process includes at least one verification node, and each verification node of the verification process has at least one different verification dimension.

[0063] According to the verification process, the verification task is assigned to the processing object corresponding to the starting verification node, and the processing object verifies the suspicious information according to the corresponding verification dimensions;

[0064] When the processing feedback of the verification node is received, if it is determined that there is a next verification node in the verification process, the verification task is assigned to the processing object corresponding to the next verification node until all verification nodes in the verification process are completed.

[0065] Fifthly, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, performs the following steps:

[0066] Obtain information about suspicious aspects of the loan incident;

[0067] The suspicious information is analyzed to determine its attribute data and verification tasks.

[0068] The verification process of the verification task is determined based on the attribute data of the suspicious information. The verification process includes at least one verification node, and each verification node of the verification process has at least one different verification dimension.

[0069] According to the verification process, the verification task is assigned to the processing object corresponding to the starting verification node, and the processing object verifies the suspicious information according to the corresponding verification dimensions;

[0070] When the processing feedback of the verification node is received, if it is determined that there is a next verification node in the verification process, the verification task is assigned to the processing object corresponding to the next verification node until all verification nodes in the verification process are completed.

[0071] The aforementioned verification task assignment method, apparatus, computer equipment, storage medium, and computer program product determine suspicious information about an event, analyze this suspicious information to obtain attribute data of the suspicious information and determine the verification tasks for the suspicious information. Based on the attribute data, they determine the verification process for the verification tasks, and based on the verification nodes in the verification process, they determine the processing objects to be assigned to the verification tasks. The suspicious information is then verified hierarchically from the processing objects corresponding to the starting verification node according to the corresponding verification dimensions until all verification nodes in the verification process are completed. Based on the attribute data of suspicious information and the verification process, verification tasks are automatically, accurately, and efficiently assigned to the processing objects within the scope of verification assignment determined by the verification process. This eliminates the need for manual assignment offline, improving the efficiency and accuracy of verification task assignment through online automatic assignment. Furthermore, different types of suspicious information can be identified to obtain different suspicious attribute data. By determining the corresponding attribute data and verification process, different types of suspicious information are hierarchically assigned to the processing objects within the scope of verification assignment. This allows for the assignment of suspicious information in different scenarios and avoids data leakage through online automatic assignment. Attached Figure Description

[0072] Figure 1 This is a diagram illustrating the application environment of the verification task assignment method in one embodiment;

[0073] Figure 2 This is a flowchart illustrating a task assignment verification method in one embodiment;

[0074] Figure 3 This is a flowchart illustrating a method for assigning verification tasks to verification nodes in one embodiment;

[0075] Figure 4 This is a flowchart illustrating the task assignment verification method in another embodiment;

[0076] Figure 5 This is a flowchart illustrating the task assignment verification method in another embodiment;

[0077] Figure 6 This is a flowchart illustrating the task assignment verification method in another embodiment;

[0078] Figure 7 This is a structural block diagram of the verification task assignment device in one embodiment;

[0079] Figure 8 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0080] It should be noted that the acquisition, storage, use, and processing of the data involved in this application (including but not limited to user device information, user personal information, and suspicious information) all comply with the relevant provisions of national laws and regulations.

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

[0082] The verification task assignment method provided in this application embodiment can be applied to, for example, Figure 1 In the application environment shown, the loan terminal 102, the dispatch terminal 104, and the verification terminal 106 communicate via a network. A data storage system can store the data that the dispatch terminal 104 needs to process. The data storage system can be integrated onto server 104 or placed on a cloud or other network server. The dispatch terminal acquires suspicious information about loan events from the loan terminal; analyzes the suspicious information to determine its attribute data and verification tasks; determines the verification process for the verification tasks based on the attribute data of the suspicious information; and, according to the verification process, dispatches the verification tasks to the verification terminals corresponding to the starting verification nodes, whereby the processing objects verify the suspicious information according to the corresponding verification dimensions. When processing feedback is received from a verification node, if it is determined that there is a next verification node in the verification process, the verification task is dispatched to the verification terminal corresponding to the next verification node, until all verification nodes in the verification process are completed. Among them, the loan terminal 102, the allocation terminal 104 and the verification terminal 106 may be, but are not limited to, various personal computers, laptops, smartphones, tablets, Internet of Things devices and portable wearable devices.

[0083] In one embodiment, such as Figure 2 As shown, a method for task assignment is provided. This embodiment applies this method to... Figure 1 The following example illustrates the method using a dispatch terminal. In this embodiment, the method includes the following steps:

[0084] Step 202: Obtain information on suspicious aspects of the loan incident.

[0085] Loan events include pre-loan, during-loan, and post-loan events. Reviewing these events during loan processing can mitigate risks from multiple perspectives. Pre-loan event review includes a comprehensive review of the loan applicant's information, assessing the compliance, legality, and validity of the borrower. During-loan events include verification of the conduct of the loan approval party's employees. Post-loan events include risk verification after the loan has been approved and disbursed by the bank. Loan types include personal loans, collective enterprise loans, and private enterprise loans, etc. This application does not specify a particular loan type.

[0086] Suspicious information includes loan-related information filtered from the loan database through an early warning model that suggests potential risk. For example, suspicious information could include discrepancies in a borrower's use of quick loans and the flow of funds in their account. The determination of suspicious information can be, but is not limited to, using a risk early warning model. It is understood that different early warning models represent different risk impacts, and each model has a corresponding identifier. For example, early warning model A addresses credit risk issues associated with the loan applicant.

[0087] Step 204: Analyze the suspicious information to determine the attribute data and verification tasks of the suspicious information.

[0088] The attribute data includes the type of suspicious information and the information of the initiator of the event. The suspicious information types include credit risk and regional risk, etc., and the information of the initiator of the event includes the loan agent's information. The verification tasks include a detailed list of tasks to be verified for the suspicious information, such as loan account number, loan type, loan risk type, and relevant information of the loan applicant.

[0089] The verification task includes a detailed list of tasks that need to be verified for suspicious information. The task details can be understood as the verification dimensions. The verification task is determined based on the task generation method parameters of the suspicious information. The task generation methods for different suspicious information are different, but there may also be some similarities.

[0090] Specifically, when suspicious information is detected in a loan event, the suspicious information is identified, analyzed, and relevant parameters are obtained. The attribute data of the suspicious information is determined from the relevant parameters, and the corresponding task generation method parameters are determined according to the identifier of the suspicious information. The corresponding verification information is extracted from the suspicious information according to the task generation method parameters, and a verification task is generated.

[0091] Step 206: Determine the verification process of the verification task based on the attribute data of the suspicious information. The verification process includes at least one verification node, and each verification node in the verification process has at least one different verification dimension.

[0092] The attribute data includes the type of suspicious event, information about the event initiator, and the task level. The task level characterizes the importance of the task; for example, task levels include general, medium, and important. The verification process for the task is determined based on the attribute data in the suspicious event information. Different attribute data leads to different verification processes, which are determined according to the needs of the application scenario, the accuracy and reliability of the verification. Considering the needs of different application scenarios, different attribute data corresponds to different review processes. For example, considering the different levels of review assignment and the granularity of review in different application scenarios, corresponding review processes need to be determined based on different application scenarios.

[0093] The verification process includes at least one verification node. Each verification node in the verification process has at least one different verification dimension. The review process of the verification process ends at the beginning verification node and terminates at the end verification node. The relationships between verification nodes include subordinate and parallel relationships. For example, verification node A corresponds to the first-level review level, and verification node B corresponds to the second-level review level. The second-level review level is subordinate to the first-level review level.

[0094] Step 208: In accordance with the verification process, the verification task is assigned to the processing object corresponding to the starting verification node, and the processing object verifies the suspicious information according to the corresponding verification dimensions.

[0095] Each verification node corresponds to at least one processing object. Having at least one processing object on a verification node improves the processing efficiency of both the node itself and the verification tasks performed on it. Different verification nodes may share the same verification dimensions or have different dimensions. Multiple verifications of data with the same dimensions can be performed to determine the accuracy of the verification. Conversely, different verification nodes may have different verification dimensions, allowing for comprehensive verification of the task and further enhancing the reliability of the verification process.

[0096] Specifically, after determining the verification process for suspicious information verification tasks, during task verification, the verification tasks are automatically assigned to the corresponding verification nodes according to their verification order, eliminating the need for manual assignment. That is, following the verification process, the verification tasks are assigned to the user terminals where the processing objects reside at the starting verification node. The processing objects trigger verification commands on the user terminals, which then respond to the commands and perform verification by matching or judging the data in the verification task against the data in the database based on the verification dimensions carried in the commands. This separation of task assignment and task verification avoids problems such as data leakage, incorrect allocation, and inefficient allocation.

[0097] Step 210: When the processing feedback of the verification node is received, if it is determined that there is a next verification node in the verification process, the verification task is assigned to the processing object corresponding to the next verification node until all verification nodes in the verification process are completed.

[0098] Specifically, following the verification process, verification tasks are assigned to user terminals where the processing objects at the initial verification node reside. The processing objects trigger verification commands on their user terminals. The user terminals respond to these commands, performing verification by matching or judging the data in the verification task against the data in the database based on the verification dimensions specified in the command. When processing feedback is received from a verification node, if it is determined that there is a next verification node in the verification process, the verification task is assigned to the processing object corresponding to that next verification node. Each verification node is executed sequentially until all verification nodes in the verification process are completed, obtaining the verification status of each node. Based on the verification status of each node, it can be determined whether the suspicious information is abnormal. When an abnormality is found, a loan event warning is issued, for example, generating a loan event warning prompt.

[0099] In the above-described method for assigning verification tasks, suspicious information about an event is identified, analyzed to obtain attribute data of this information, and then the verification tasks are determined. Based on the attribute data, the verification process for each task is established, and the processing objects to be assigned to each task are determined based on the verification nodes in the process. The suspicious information is then verified hierarchically, starting from the processing object corresponding to the initial verification node and proceeding according to the corresponding verification dimensions, until all verification nodes in the process are completed. Based on the attribute data of suspicious information and the verification process, verification tasks are automatically, accurately, and efficiently assigned to the processing objects within the scope of verification assignment determined by the verification process. This eliminates the need for manual assignment offline, improving the efficiency and accuracy of verification task assignment through online automatic assignment. Furthermore, different types of suspicious information can be identified to obtain different suspicious attribute data. By determining the corresponding attribute data and verification process, different types of suspicious information are hierarchically assigned to the processing objects within the scope of verification assignment. This allows for the assignment of suspicious information in different scenarios and avoids data leakage through online automatic assignment.

[0100] In one embodiment, when assigning verification tasks, considering the processing efficiency of each verification node, it is necessary to obtain the actual processing status of each verification node and assign tasks based on the processing status of each object on each verification node, thereby improving the verification efficiency of the verification tasks. Figure 3 As shown, a method for assigning verification tasks to various verification nodes is provided, including the following steps:

[0101] Step 302: Determine the idle processing objects of the node to be checked.

[0102] It is understood that the verification process includes at least one verification node. Verification tasks begin at the start verification node and end at the end verification node. In this embodiment, the assignment of verification tasks to the start verification node is used for illustration; however, this method also applies to assignment to other verification nodes. An idle processing object refers to an object whose current state is not processing, at which point there may be at least one unprocessed verification task.

[0103] Step 304: Obtain the event response level and current unprocessed amount for each idle processing object.

[0104] The event response level is determined based on the historical processing efficiency of the object being processed.

[0105] Step 306: Determine the processing object from the idle processing objects based on the event response level and the current unprocessed amount.

[0106] Specifically, the event response level and current unprocessed amount of each processing object at the verification node are obtained. After determining the processing object with the highest event response level, the object with the fewest unprocessed amounts is selected from the current unprocessed amounts to obtain the final determined processing object. For example, taking a bank as an example, the determined processing object is the verification personnel in the corresponding position within the corresponding verification institution.

[0107] Step 308: Assign the verification task to the processing object.

[0108] Among them, assignment can be performed by executing the assignment function to assign the verification task to the corresponding processing object.

[0109] In the above-mentioned verification task assignment, when assigning verification tasks to corresponding verification nodes, the idle processing objects on each verification node are determined, and the event response level and current unprocessed amount of each verification object are obtained. Based on the event response level and current unprocessed amount, processing objects are selected from the idle processing objects. This avoids the accumulation of the same processing object on verification nodes, preventing verification tasks from being processed in a timely manner. To a certain extent, this meets the processing requirements of verification tasks and improves the processing efficiency, assignment efficiency, and security of verification tasks. In another embodiment, as... Figure 4 As shown, a method for task assignment is provided. This embodiment applies this method to... Figure 1 The following example illustrates the method using a dispatch terminal. In this embodiment, the method includes the following steps:

[0110] Step 402: Obtain information on suspicious aspects of the loan incident.

[0111] Step 404: Analyze the suspicious information and determine the first identifier and attribute data of the suspicious information.

[0112] The process involves analyzing suspicious information and configuring its parameters. From these parameters, the primary identifier and attribute data of the suspicious information are determined. The configured parameters include suspicious type, event initiator information, early warning model identifier, task level, task assignment parameters, and task generation method parameters. Task generation method parameters include dimensions such as the handling bank, model, and partner. Task assignment parameters include the task assignment institution level, which can be understood as a verification node, representing the institution at which the verification task is initially assigned and ultimately assigned, including branches and sub-branches. The attribute data includes the suspicious type and event initiator information; the primary identifier is used to mark different types of suspicious information, and there is a corresponding relationship between the primary identifier and the task generation method parameters.

[0113] Step 406: Determine the task generation method parameter that matches the first identifier from the preset verification parameter library.

[0114] Step 408: Generate a verification task for suspicious information based on the task generation method parameters.

[0115] The generated verification task includes at least one of the following: basic information of the suspicious loan, information of the assigning institution, task number, and verification identifier. The information of the assigning institution includes the verification node to be assigned, etc. The task number is an identifier automatically generated when the verification task is generated, which is used to distinguish verification tasks with different suspicious information. The verification identifier is used to indicate whether it has been verified. For example, a verification identifier of 1 means that it has been verified, and a verification identifier of 0 means that it has not been verified.

[0116] Specifically, based on the task generation method parameters, information corresponding to the verification dimensions is extracted from the suspicious information to generate a verification task for the suspicious information. Further, when generating the verification task for the suspicious information, the verification dimensions corresponding to the task generation method parameters are determined; the verification information corresponding to the verification dimensions is determined from the suspicious information; and the verification task is generated based on the verification information.

[0117] Step 410: Determine the task assignment parameters that match the type of suspicion and the information of the event initiator from the preset verification parameter library.

[0118] Step 412: Determine the verification process for the verification task based on the task assignment parameters; the task assignment parameters include at least two verification nodes, and there is a sequential execution order between the verification nodes.

[0119] Step 414: In accordance with the verification process, the verification task is assigned to the processing object corresponding to the starting verification node, and the processing object verifies the suspicious information according to the corresponding verification dimensions.

[0120] Step 416: When the processing feedback of the verification node is received, if it is determined that there is a next verification node in the verification process, the verification task is assigned to the processing object corresponding to the next verification node until all verification nodes in the verification process are completed.

[0121] In the above-described method for assigning verification tasks, suspicious information about an event is identified, analyzed to obtain attribute data of this information, and then the verification tasks are determined. Based on the attribute data, the verification process for each task is established, and the processing objects to be assigned to each task are determined based on the verification nodes in the process. The suspicious information is then verified hierarchically, starting from the processing object corresponding to the initial verification node and proceeding according to the corresponding verification dimensions, until all verification nodes in the process are completed. Based on the attribute data of suspicious information and the verification process, the system automatically, accurately, and efficiently assigns verification tasks to the processing objects within the scope determined by the verification process. This eliminates the need for manual offline assignment, improving both efficiency and accuracy. Furthermore, it allows for the identification of different types of suspicious information, obtaining different suspicious attribute data. By determining the corresponding attribute data and verification process, different types of suspicious information are hierarchically assigned to the processing objects within the verification scope. This enables the assignment of suspicious information in different scenarios and avoids data leakage through online automation. It is understood that the verification task assignment method in this application can also be applied to scenarios such as debt collection task assignment and pre-loan task assignment.

[0122] In another embodiment, while verifying the verification task, if a new verification dimension is detected in the next verification node, the verification task needs to be packaged and summarized at multiple levels for verification. That is, when the verification dimension of a verification node in the verification process is updated, the verification task of the corresponding verification node is updated.

[0123] like Figure 5 As shown, a method for task assignment is provided. This embodiment applies this method to... Figure 1 The following example illustrates the method using a dispatch terminal. In this embodiment, the method includes the following steps:

[0124] Step 502: Obtain information on suspicious aspects of the loan incident.

[0125] Step 504: Analyze the suspicious information to determine the attribute data and verification tasks of the suspicious information.

[0126] Step 506: Determine the verification process of the verification task based on the attribute data of the suspicious information. The verification process includes at least one verification node, and each verification node in the verification process has at least one different verification dimension.

[0127] Step 508: In accordance with the verification process, the verification task is assigned to the processing object corresponding to the starting verification node, and the processing object verifies the suspicious information according to the corresponding verification dimensions.

[0128] Step 510: When the processing feedback from the verification node is received, if it is determined that there is a next verification node in the verification process, the verification task is assigned to the processing object corresponding to the next verification node.

[0129] Step 512: If the verification dimension of the processing object corresponding to the next verification node is different from the verification dimension of the previous verification node, determine to add a new verification dimension.

[0130] Step 514: If the verification task of the previous verification node does not have any new verification dimensions, update the verification task of the previous verification node according to the verification information of the new verification dimensions, until all verification nodes in the verification process are completed.

[0131] Specifically, the process involves generating verification tasks for suspicious information and determining the verification flow for these tasks. Following the flow, verification tasks are assigned to the processing objects corresponding to the starting verification node. These processing objects then verify the suspicious information according to the corresponding verification dimensions. When processing feedback is received from a verification node, if it's determined that a next verification node exists in the verification flow, and the verification dimensions of the next node differ from those of the previous node (i.e., when the verification dimensions of the previous node are updated, resulting in a new dimension), the verification task of the previous node is updated based on the verification information corresponding to the new dimension. The verification task is then assigned to the processing object corresponding to the next node, continuing until all verification nodes in the verification flow are completed. The new verification dimension can be, but is not limited to, the verification result dimension of the previous node. In other words, the verification result and the verification task of the previous node are summarized and packaged to obtain a new verification task.

[0132] If the verification dimension of the next verification node is the same as that of the previous verification node, then there is no need to update the verification task. The verification task is then assigned to the processing object corresponding to the next verification node, until all verification nodes in the verification process are completed. For example, in a loan application scenario, the verification dimensions in the previous verification node (e.g., a primary bank) include loan completion status and basic information. The verification dimensions of the next verification node (e.g., a secondary bank) will include the task assignment dimension in addition to basic information, i.e., which primary bank assigned the task. The verification dimensions of the next verification node (e.g., a tertiary bank) will also include the assignment information from the previous two verification nodes (e.g., primary and secondary banks).

[0133] In the above-described method for assigning verification tasks, suspicious information about an event is identified, analyzed to obtain attribute data, and verification tasks are determined. The verification process for each task is then established based on the attribute data, and the processing objects to be assigned to each task are determined based on the verification nodes in the process. Suspicious information is then verified hierarchically from the processing objects corresponding to the initial verification node according to the corresponding verification dimensions. If an update to the verification dimension of a corresponding verification node is detected during assignment, the verification task of the previous node is updated based on the newly added dimension until all verification nodes in the process are completed. This method automatically, accurately, and efficiently assigns verification tasks to the processing objects within the scope determined by the verification process, based on the attribute data of the suspicious information and the verification process. The assigned tasks are also hierarchically packaged and summarized. This eliminates the need for manual offline assignment, improving the efficiency and accuracy of verification task assignment through online automation.

[0134] Optionally, in one embodiment, according to the verification process, the verification task is assigned to the processing object corresponding to the starting verification node, and the processing object verifies the suspicious information according to the corresponding verification dimension; when processing feedback is received from the verification node, if it is determined that there is a next verification node in the verification process, the verification task is assigned to the processing object corresponding to the next verification node, until all verification nodes in the verification process are completed, and the target verification result is obtained from the terminal where the processing object is located; if the target verification result is abnormal, risk prediction is performed on the verification task, the risk level of the verification task is determined, and it is sent to the processing object for review. Figure 6 As shown, a method for task assignment is provided. This embodiment applies this method to... Figure 1 The following example illustrates the method using a dispatch terminal. In this embodiment, the method includes the following steps:

[0135] Step 602: Obtain information on suspicious aspects of the loan incident.

[0136] Step 604: Analyze the suspicious information to determine the attribute data and verification tasks of the suspicious information.

[0137] Step 606: Determine the verification process of the verification task based on the attribute data of the suspicious information. The verification process includes at least one verification node, and each verification node in the verification process has at least one different verification dimension.

[0138] Step 608: In accordance with the verification process, the verification task is assigned to the processing object corresponding to the starting verification node, and the processing object verifies the suspicious information according to the corresponding verification dimensions.

[0139] Step 610: When the processing feedback of the verification node is received, if it is determined that there is a next verification node in the verification process, the verification task is assigned to the processing object corresponding to the next verification node until all verification nodes in the verification process are completed.

[0140] Step 612: Receive the target verification result from the terminal where the object to be processed is located.

[0141] Step 614: If the target verification result is abnormal, perform risk prediction on the verification task and determine the risk level of the verification task.

[0142] Specifically, risk prediction for target verification results involves inputting the verification results into an early warning model corresponding to suspicious information to predict the risk level of the verification task and issue an early warning. This allows for monitoring of verification tasks and ensures safe and controllable task assignment. For example, in loan processing, if the target verification result is abnormal, it is forwarded to the relevant party for review, preventing losses due to untimely or erroneous verification in the early stages.

[0143] The aforementioned task assignment method identifies suspicious information about an event, analyzes this information to obtain attribute data, and determines the verification tasks. Based on the attribute data, it establishes the verification process for each task and identifies the processing objects to be assigned to each task based on the verification nodes in the process. By performing hierarchical verification of the suspicious information according to the corresponding verification dimensions, starting from the processing objects corresponding to the initial verification node, the method continues until all verification nodes in the process are completed. Risk prediction is then performed based on the target verification results fed back from the terminal to determine the risk level of each task. Based on the risk level, it is determined whether a review is required. By automatically assigning verification tasks online and reviewing them based on their risk levels, the efficiency, accuracy, and reliability of task assignment are improved.

[0144] Optionally, in one embodiment, a verification task assignment system is provided. The backend of the verification task assignment system obtains suspicious information about loan events; analyzes the suspicious information to determine the attribute data of the suspicious information and the verification tasks; determines the verification process of the verification tasks based on the attribute data of the suspicious information, the verification process includes at least one verification node, and each verification node in the verification process has at least one different verification dimension; according to the verification process, the verification tasks are assigned to the processing objects corresponding to the starting verification node, and the processing objects verify the suspicious information according to the corresponding verification dimensions; when processing feedback is received from the verification node, if it is determined that there is a next verification node in the verification process, the verification task is assigned to the processing object corresponding to the next verification node, until all verification nodes in the verification process are completed, thereby realizing automatic assignment of verification tasks.

[0145] The front-end interface of the verification task assignment system includes controls for querying suspicious information, querying task details, performing task verification operations, and displaying task status. This interface is designed and implemented using Java with the SpringMVC and Mybatis framework. By clicking on these controls, users can obtain information such as suspicious information, detailed verification tasks, and the progress and processing status of each task. The task assignment process is visualized, allowing users to quickly track the progress of the assignment.

[0146] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0147] Based on the same inventive concept, this application also provides a verification task assignment apparatus for implementing the verification task assignment method described above. The solution provided by this apparatus is similar to the implementation scheme described in the above method; therefore, the specific limitations in one or more verification task assignment apparatus embodiments provided below can be found in the limitations of the verification task assignment method described above, and will not be repeated here.

[0148] In one embodiment, such as Figure 7 As shown, a verification task assignment device is provided, including: an information acquisition module 702, a data processing module 704, a verification process determination module 706, and a task assignment module 708, wherein:

[0149] The information acquisition module 702 is used to acquire suspicious information about loan events.

[0150] The data processing module 704 is used to analyze suspicious information, determine the attribute data of suspicious information, and perform verification tasks.

[0151] The verification process determination module 706 is used to determine the verification process of the verification task based on the attribute data of the suspicious information. The verification process includes at least one verification node, and each verification node of the verification process has at least one different verification dimension.

[0152] The task assignment module 708 is used to assign verification tasks to the processing objects corresponding to the starting verification node according to the verification process, and the processing objects verify the suspicious information according to the corresponding verification dimensions.

[0153] When processing feedback is received from a verification node, if it is determined that there is a next verification node in the verification process, the verification task is assigned to the processing object corresponding to the next verification node, until all verification nodes in the verification process are completed.

[0154] The aforementioned task assignment device identifies suspicious information about an event, analyzes this information to obtain attribute data and determine the verification tasks. Based on the attribute data, it establishes the verification process for each task and identifies the processing objects to be assigned to each task based on the verification nodes in the process. The suspicious information is then verified hierarchically, starting from the processing object corresponding to the initial verification node and proceeding according to the corresponding verification dimensions, until all verification nodes in the process are completed. Based on the attribute data of suspicious information and the verification process, verification tasks are automatically, accurately, and efficiently assigned to the processing objects within the scope of verification assignment determined by the verification process. This eliminates the need for manual assignment offline, improving the efficiency and accuracy of verification task assignment through online automatic assignment. Furthermore, different types of suspicious information can be identified to obtain different suspicious attribute data. By determining the corresponding attribute data and verification process, different types of suspicious information are hierarchically assigned to the processing objects within the scope of verification assignment. This allows for the assignment of suspicious information in different scenarios and avoids data leakage through online automatic assignment.

[0155] In another embodiment, a verification task assignment device is provided, which, in addition to including an information acquisition module 702, a data processing module 704, a verification process determination module 706, and a task assignment module 708, further includes: a data matching module, an idle processing object determination module, and a risk prediction module, wherein:

[0156] The data processing module 704 is also used to analyze the suspicious information and determine the first identifier of the suspicious information.

[0157] The data matching module is used to determine the task generation method parameters that match the first identifier from the preset verification parameter library;

[0158] The data processing module 704 is also used to generate verification task dimensions for suspicious information based on the task generation method parameters.

[0159] Data processing module 704 is also used to determine the verification dimensions corresponding to the task generation method parameters;

[0160] Identify the verification information corresponding to the verification dimensions from the suspicious information;

[0161] Verification tasks are generated based on the verification information.

[0162] The verification process determination module 706 is also used to determine task assignment parameters that match the type of suspicion and the information of the event initiator from the preset verification parameter library;

[0163] The verification process for the verification task is determined based on the task assignment parameters; the task assignment parameters include at least two verification nodes, and there is a sequential execution order between the verification nodes.

[0164] The idle processing object determination module is used to determine the idle processing object of the node to be checked.

[0165] Get the event response level and current unprocessed amount of each idle processing object;

[0166] The target idle processing object is determined from the idle processing objects based on the event response level and the current unprocessed amount;

[0167] The task assignment module 708 is also used to assign verification tasks to target idle processing objects.

[0168] The risk prediction module is used to receive the target verification results from the terminal where the object being processed is located;

[0169] If the target verification result is abnormal, risk prediction is performed on the verification task to determine the risk level of the verification task.

[0170] Each module in the aforementioned verification task assignment device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of a computer device in hardware form or independent of it, or stored in the memory of a computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0171] In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 8 As shown, the computer device includes a processor, memory, communication interface, display screen, and input devices connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements a verification task assignment method. The display screen can be an LCD screen or an e-ink screen. The input devices can be a touch layer covering the display screen, buttons, a trackball, or a touchpad mounted on the computer device casing, or an external keyboard, touchpad, or mouse.

[0172] Those skilled in the art will understand that Figure 8 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

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

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

[0175] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0176] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

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

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

Claims

1. A method of verifying task assignment, the method comprising: The method comprises: obtaining suspicious information of a loan event, the suspicious information comprising information related to the loan and existing risks screened from a loan database through a pre-warning model; analyzing the suspicious information to determine attribute data and a verification task of the suspicious information, the attribute data comprising suspicious type, event initiator information and task level; the verification task being determined according to a task generation mode parameter of the suspicious information, the task generation mode parameter comprising an agent bank dimension, a model dimension or a cooperative party dimension; determining a verification process of the verification task according to the attribute data of the suspicious information, each verification node of the verification process having at least one different verification dimension, and the relationship between each verification node comprising a parallel relationship; assigning the verification task to a processing object corresponding to a starting verification node according to the verification process, and verifying the suspicious information according to a corresponding verification dimension by the processing object; the assigning of the verification task to the processing object corresponding to the starting verification node according to the verification process comprises: determining idle processing objects of the starting verification node; obtaining an event response level and a current unprocessed amount of each idle processing object, wherein the event response level is determined according to the historical processing efficiency of the processing object; determining a processing object from the idle processing objects according to the event response level and the current unprocessed amount; and assigning the verification task to the processing object; when receiving processing feedback of the verification node, if it is determined that there is a next verification node on the verification process, if there is a new verification dimension, updating the verification task of the verification node according to the verification information corresponding to the new verification dimension, and assigning the verification task to a processing object corresponding to the next verification node, if there is no new verification dimension, assigning the verification task to a processing object corresponding to the next verification node; until all verification nodes of the verification process are verified, wherein if the verification dimension between the verification node and the next verification node is different, it is determined that there is a new verification dimension, and the new verification dimension is the verification result dimension of the verification node.

2. The method of claim 1, wherein, analyzing the suspicious information to determine the verification task of the suspicious information comprises: analyzing the suspicious information to determine a first identifier of the suspicious information; determining a task generation mode parameter matched with the first identifier from a preset verification parameter library; generating the verification task of the suspicious information according to the task generation mode parameter.

3. The method of claim 2, wherein, generating the verification task of the suspicious information according to the task generation mode parameter comprises: determining a verification dimension corresponding to the task generation mode parameter; determining verification information corresponding to the verification dimension from the suspicious information; generating a verification task according to the verification information.

4. The method of claim 1, wherein, the attribute data comprises suspicious type and event initiator information, and determining a verification process of the verification task according to the attribute data of the suspicious information comprises: determining a task assignment parameter matched with the suspicious type and the event initiator information from a preset verification parameter library; Determine a verification procedure of the verification task according to the task assignment parameter; the task assignment parameter includes at least two verification nodes, and the verification nodes have an execution sequence.

5. The method according to any one of claims 1 to 4, characterized in that, The method further includes: Receiving a target verification result fed back by a terminal where the processing object is located; If the target verification result is abnormal, predicting a risk of the verification task and determining a risk level of the verification task.

6. A task assignment apparatus for verifying, comprising: The device includes: An information acquisition module, configured to acquire suspicious information of a loan event, the suspicious information including information related to a loan and having a risk, which is filtered from a loan database through a warning model; A data processing module, configured to analyze the suspicious information, determine attribute data and a verification task of the suspicious information, the attribute data including suspicious types, event initiator information, and task levels; the verification task is determined according to a task generation mode parameter of the suspicious information, the task generation mode parameter including an agent bank dimension, a model dimension, or a cooperative party dimension; A verification procedure determination module, configured to determine a verification procedure of the verification task according to the attribute data of the suspicious information, the verification procedure including at least one verification node, each verification node of the verification procedure having at least one different verification dimension, and a relationship between each verification node including a parallel relationship; A task assignment module, configured to assign the verification task to a processing object corresponding to a starting verification node according to the verification procedure, and have the processing object verify the suspicious information according to a corresponding verification dimension; An idle processing object determination module, configured to determine idle processing objects of the starting verification node, acquire event response levels and current unprocessed amounts of each idle processing object, and determine a target idle processing object from the idle processing objects according to the event response levels and the current unprocessed amounts; The task assignment module is further configured to assign the verification task to the target idle processing object. When receiving processing feedback of the verification node, if it is determined that there is a next verification node in the verification procedure of the verification node, if there is a new verification dimension, update the verification task of the verification node according to verification information corresponding to the new verification dimension, and assign the verification task to a processing object corresponding to the next verification node; if there is no new verification dimension, assign the verification task to a processing object corresponding to the next verification node; until all verification nodes of the verification procedure are verified, wherein, if verification dimensions between the verification node and the next verification node are different, it is determined that there is a new verification dimension, and the new verification dimension is a verification result dimension of the verification node.

7. The apparatus of claim 6, wherein, The data processing module is further configured to analyze the suspicious information and determine a first identifier of the suspicious information; The device further includes: A data matching module, configured to determine a task generation mode parameter matched with the first identifier from a preset verification parameter library; The data processing module is further configured to generate a verification dimension of the verification task of the suspicious information according to the task generation mode parameter.

8. The apparatus of claim 6, wherein, The data processing module is further configured to determine a verification dimension corresponding to the task generation mode parameter; determine verification information corresponding to the verification dimension from the suspicious information; generate a verification task according to the verification information.

9. The apparatus of claim 6, wherein, The verification process determination module is further configured to determine a task assignment parameter matching the suspicious type and the event initiator information from a preset verification parameter library; determine a verification process of the verification task according to the task assignment parameter; The task assignment parameter includes at least two verification nodes, and there is an execution sequence between the verification nodes.

10. The apparatus of claim 6, wherein, The device further includes: a risk prediction module configured to receive a target verification result fed back by a terminal where the processing object is located; if the target verification result is abnormal, perform risk prediction on the verification task, and determine a risk level of the verification task. 11.A computer device, comprising a memory and a processor, wherein the memory stores a computer program, and the computer device is configured to perform the method according to any one of claims 1-10. The processor executes the computer program to implement the steps of the method in any one of claims 1 to 5.

12. A computer readable storage medium having stored thereon a computer program, characterized in that, The computer program is executed by the processor to implement the steps of the method in any one of claims 1 to 5.

13. A computer program product comprising a computer program, characterized in that, The computer program is executed by the processor to implement the steps of the method in any one of claims 1 to 5.

Images