Risk control responsibility judgment method and device

Abstract

The invention provides a risk control responsibility judgment method and device, and the method comprises the steps: collecting data information of a plurality of channels through a third-party data source access unit in a business process execution process; according to the data information of the multiple channels, an acceptance unit is utilized to create an acceptance list according to a first preset rule; and calling a real-time responsibility judgment unit to analyze and evaluate data in the acceptance sheet according to the acceptance sheet so as to obtain a responsibility judgment result. Data information of multiple channels is collected and serves as an important basis for subsequent risk assessment and responsibility judgment, an acceptance list is created according to a first preset rule and serves as a starting point of business data processing, and finally, a real-time responsibility judgment engine applies an advanced algorithm model and a professional risk assessment system, so that the risk assessment efficiency is improved. According to the method, the data in the acceptance form is deeply analyzed, the potential risk is accurately evaluated, and the responsibility attribution is determined according to the established responsibility judgment standard, so that a more comprehensive, more flexible and more automatic risk control responsibility judgment process is realized.

Description

Technical Field

[0001] The present invention relates to the field of Internet technologies, and in particular, to a risk control liability judgment method and device. Background Art

[0002] With the continuous development of process engines, the flexibility and visualization requirements of process engines for complex business scenarios are getting higher and higher. In some scenarios of risk control liability judgment, there will be many series, parallel, and asynchronous process scenarios. Currently, most business processes configure each task node in a series or parallel manner. Taking the series configuration as an example, after the task of node one is configured, the task of node two is configured. This method is single in form, unable to handle complex series-parallel processes or asynchronous processes, and is only applicable to simple business process configurations, and cannot handle the complex business of risk control liability judgment processes. Summary of the Invention

[0003] In view of the above defects of the prior art, the present invention provides a risk control liability judgment method and device to solve the technical problems in the prior art such as inability to handle complex processes, low flexibility, and inconvenient operation.

[0004] To achieve the above object and other related objects, the present invention provides a risk control liability judgment method, including: during the execution of a business process, collecting data information from multiple channels by using a third-party data source access unit; creating an acceptance form according to the data information from the multiple channels by using an acceptance unit according to a first preset rule; and calling a real-time liability judgment unit to analyze and evaluate the data in the acceptance form according to the acceptance form to obtain a liability judgment result.

[0005] In an embodiment of the present invention, calling a real-time liability judgment unit to analyze and evaluate the data in the acceptance form according to the acceptance form to obtain a liability judgment result includes: calling a real-time liability judgment unit to analyze and evaluate the data in the acceptance form according to the acceptance form to determine the data with liability; using a shunt unit to shunt the data with liability according to preset conditions, and creating a liability judgment form for the data with liability that meets the shunt conditions and flowing it into an audit unit; and an auditor auditing the liability judgment form in the audit unit to obtain the liability judgment result.

[0006] In an embodiment of the present invention, after the step of an auditor auditing the liability judgment form in the audit unit to obtain the liability judgment result, it further includes: according to the liability judgment result, using a disposal unit to execute a disposal measure on the corresponding liable entity

[0007] In an embodiment of the present invention, before the step of collecting data information from multiple channels by using a third-party data source access unit during the execution of a business process, the following steps are further included: defining and configuring each node in the risk control liability judgment business process by using a modeling module to generate a business process model; according to the business process model, performing scheduling and execution of the business process by using a business orchestration module, wherein the business orchestration module supports task processing in serial, parallel, nested, and asynchronous modes.

[0008] In an embodiment of the present invention, defining and configuring each node in the risk control liability judgment business process by using a modeling module includes: obtaining a requirements document and a flowchart of the risk control liability judgment business; creating a visual canvas; configuring process information and global parameter variables in the canvas according to the requirements document and the flowchart of the risk control liability judgment business; configuring a first node; configuring a second node and associating the first node and the second node; sequentially configuring and associating subsequent nodes until all nodes are configured and associated.

[0009] In an embodiment of the present invention, each of the nodes is configured according to the following steps: obtaining the type of the node according to the requirements document and the flowchart of the risk control liability judgment business; setting the method, input parameters, and output parameters called by the node according to the type of the node according to a second preset rule, and specifying the association between the node and the risk control liability judgment module.

[0010] In an embodiment of the present invention, the types of the nodes include a start node, an end node, a judgment node, an automatic node, a script node, a sub-process node, a comment node, a loop node, a loop interruption node, a break-out-of-loop node, and a wait-for-event node.

[0011] In an embodiment of the present invention, each of the nodes is associated according to the following steps: setting a mapping relationship in the global parameter variables according to the association relationship between the output parameters of the foregoing node and the input parameters of the subsequent node; connecting the foregoing node and the subsequent node in the canvas and setting an association condition.

[0012] In an embodiment of the present invention, after obtaining the liability judgment result, the following steps are further included: storing the business process model, the execution data of the business process, and the acceptance form by using a storage module; providing a running state feedback and an exception handling mechanism for each of the nodes by using a process monitoring module.

[0013] To achieve the above object and other related objects, the present invention further provides a risk control liability judgment device, including: a third-party data source access unit for collecting data information from multiple channels during the execution of a business process; an acceptance unit for creating an acceptance form according to the data information from the multiple channels according to a first preset rule; and a real-time liability judgment unit for analyzing and evaluating the data in the acceptance form according to the acceptance form to obtain a liability judgment result.

[0014] Advantages of the present invention: A risk control liability judgment method and device proposed by the present invention collect data information from multiple channels, which serves as an important basis for subsequent risk assessment and liability judgment. An acceptance form is created according to the first preset rule as the starting point for business data processing. Finally, through a real-time liability judgment engine that uses advanced algorithm models and a professional risk assessment system, the data in the acceptance form is deeply analyzed to accurately evaluate potential risks, and the liability attribution is clarified based on the established liability judgment criteria, thereby realizing a more comprehensive, flexible, and automated risk control liability judgment process. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings required for the description of the embodiments or the prior art. Obviously, the drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, without creative efforts, other drawings can be obtained based on these drawings.

[0016] Figure 1 The first flowchart of the risk control liability judgment method provided by an embodiment of the present invention;

[0017] Figure 2 The detailed flowchart of step S330 provided by an embodiment of the present invention;

[0018] Figure 3 The second flowchart of the risk control liability judgment method provided by an embodiment of the present invention;

[0019] Figure 4 The third flowchart of the risk control liability judgment method provided by an embodiment of the present invention;

[0020] Figure 5 The definition and configuration flowchart of the node provided by an embodiment of the present invention;

[0021] Figure 6 The detailed configuration flowchart of the node provided by an embodiment of the present invention;

[0022] Figure 7 The detailed association flowchart of the node provided by an embodiment of the present invention;

[0023] Figure 8 The first arrangement method of the process nodes provided by an embodiment of the present invention;

[0024] Figure 9 The second arrangement method of the process nodes provided by an embodiment of the present invention;

[0025] Figure 10The third arrangement method of process nodes provided by an embodiment of the present invention;

[0026] Figure 11 The fourth arrangement method of process nodes provided by an embodiment of the present invention;

[0027] Figure 12 The fifth arrangement method of process nodes provided by an embodiment of the present invention;

[0028] Figure 13 The fourth flowchart of the risk control liability judgment method provided by an embodiment of the present invention;

[0029] Figure 14 The structural schematic diagram of the risk control liability judgment device provided by an embodiment of the present invention.

[0030] Explanation of reference numerals: 101, third-party data source access unit; 102, acceptance unit; 103, real-time liability judgment unit. Detailed implementation manners

[0031] The following describes the implementation manners of the present invention through specific specific examples. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification. It should be noted that, without conflict, the following examples and the features in the examples can be combined with each other. In addition to the specific methods, devices, and materials used in the examples, according to the knowledge of those skilled in the art in the technical field and the records of the present invention, any methods, devices, and materials similar to or equivalent to those described in the embodiments of the present invention can also be used to implement the present invention.

[0032] It should be understood that the terms used in the embodiments of the present invention are for the purpose of describing specific specific implementation manners, rather than for limiting the protection scope of the present invention. Unless otherwise defined, all technical and scientific terms used in the present invention have the same meaning as commonly understood by those skilled in the technical field of the present invention.

[0033] In the following description, a large number of details are discussed to provide a more thorough explanation of the embodiments of the present invention. However, it is obvious to those skilled in the art that the embodiments of the present invention can be implemented without these specific details. In some of these embodiments, well-known structures and devices are shown in the form of block diagrams rather than in detail to avoid making the embodiments of the present invention difficult to understand.

[0034] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functions, and operations that the methods and computer program products according to various embodiments disclosed in the present invention may implement. In this regard, each block in the flowchart or block diagram may represent a module, a program segment, or a part of code, which contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than that marked in the accompanying drawings. For example, two consecutive blocks shown may actually be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and / or flowchart, as well as the combination of blocks in the block diagram and / or flowchart, may be implemented by a dedicated hardware-based system that performs the specified functions or operations, or may be implemented by a combination of dedicated hardware and computer instructions.

[0035] Please refer to Figure 1 , Figure 1 A risk control liability judgment method provided by an embodiment of the present invention is applied to a risk control liability judgment module, which includes a third-party data source access unit, an acceptance unit, and a real-time liability judgment unit. The method includes steps S310 to S330.

[0036] Step S310: During the execution of the business process, use the third-party data source access unit to collect data information from multiple channels. The risk control liability judgment module will first establish connections with various third-party data sources and widely collect relevant data information from different channels. These data are important bases for subsequent risk assessment and liability determination.

[0037] Step S320: According to the data information from multiple channels, use the acceptance unit to create an acceptance form according to the first preset rule. The various types of accessed data are then transmitted to the acceptance unit. The acceptance unit will comprehensively and carefully receive and sort out these data, and create a corresponding acceptance form according to the established first preset rule and format, which serves as the starting mark for processing the business data of this transaction.

[0038] Step S330: According to the acceptance form, call the real-time liability judgment unit to analyze and evaluate the data in the acceptance form to obtain a liability judgment result. After the acceptance is completed, the call to the real-time liability judgment engine is automatically triggered. The real-time liability judgment engine uses advanced algorithm models and professional risk assessment systems to deeply analyze the data in the acceptance form, accurately evaluate potential risks, and clarify the liability attribution according to the established liability judgment criteria, thereby obtaining a liability judgment result.

[0039] Please refer to Figure 2, the above liability judgment result is automatically determined. To further ensure the accuracy of the liability judgment result, manual review can be introduced. In a specific embodiment of the present invention, the risk control liability judgment module further includes a shunting unit and a review unit, and step S330 includes steps S331 to S333.

[0040] Step S331: According to the acceptance form, call the real-time liability judgment unit to analyze and evaluate the data in the acceptance form to determine the data with liability.

[0041] Step S332: Use the shunting unit to shunt the data with liability according to preset conditions, and create a liability judgment form for the data with liability that meets the shunting conditions and flow it into the review unit. The preset conditions can be, for example, business type, driver portrait, user portrait, city, etc. Using the preset conditions, targeted shunting processing can be carried out on the data with liability. These preset conditions are carefully formulated based on business requirements and risk prevention and control strategies, aiming to ensure that different types of liable data can be properly processed subsequently. When creating the liability judgment form, key information such as the specific result of the liability judgment, relevant basis, and involved business details can be recorded. For the data that does not meet the shunting conditions, the entire business process will terminate here.

[0042] Step S333: The review personnel review the liability judgment form in the review unit to obtain the liability judgment result. In the review unit, professional review personnel will conduct strict and detailed reviews on the submitted liability judgment forms. The review process not only includes verifying the rationality and accuracy of the liability judgment result, but also examines the integrity of relevant evidence and data to ensure the fairness and reliability of the liability judgment result.

[0043] Please refer to Figure 3 , in a specific embodiment of the present invention, the risk control liability judgment module further includes a disposal unit. After step S330, it further includes: S340: According to the liability judgment result, use the disposal unit to execute disposal measures on the corresponding liable subject. For example, taking the risk control liability judgment of a freight platform as an example, after review, for the drivers finally determined to be liable, corresponding measures will be taken according to the severity of the liability. For minor violations, reminder messages will be sent to the drivers, informing them of the violations and possible consequences, and urging them to correct in a timely manner. For serious violations, corresponding penalties will be imposed on the drivers according to the established penalty mechanism, such as deducting behavior points, freezing cash withdrawals, freezing driver level rights and interests, etc., to play a role in punishing and regulating the market order.

[0044] The above steps S310 - S340 and steps S331 - S333 can be summarized as step S300. During the execution of the business process, risk assessment and responsibility determination are carried out through the risk control and responsibility judgment module to obtain the responsibility judgment result. The risk control and responsibility judgment module calls the real-time engine in real time during the execution of the business process to evaluate risks and determine responsibilities. When a risk or abnormal situation is detected, a corresponding responsibility judgment form is generated for use during the review by the review unit.

[0045] Please refer to Figure 4 , in a specific embodiment of the present invention, before the above step S300, steps S100 and S200 are further included.

[0046] Step S100: Use the modeling module to define and configure each node in the risk control and responsibility judgment business process to generate a business process model. By using the modeling module, a visual graphical interface can be provided to facilitate the definition and configuration of each node in the process.

[0047] Please refer to Figure 5 , in a specific embodiment of the present invention, using the modeling module to define and configure each node in the risk control and responsibility judgment business process includes steps S120 - S160.

[0048] Step S110: Obtain the requirement document and flowchart of the risk control and responsibility judgment business. The risk control and responsibility judgment business refers to the business activities of identifying, analyzing, and handling risk events or violations during the risk management process. Its core goal is to clarify the responsible entity, evaluate the degree of responsibility, and take corresponding measures to prevent and resolve risks through the investigation, analysis, and judgment of risk events, ensuring business compliance and risk controllability. To implement an automated risk control and responsibility judgment method, it is necessary to first clarify the specific requirements and judgment process of the risk control and responsibility judgment business, and this information can be obtained through the requirement document and flowchart of the risk control and responsibility judgment business.

[0049] Step S120: Create a visual canvas. The visual canvas is mainly to facilitate the definition and configuration of nodes, reduce the difficulty of modeling, and improve the convenience of modeling.

[0050] Step S130: According to the requirement document and flowchart of the risk control and responsibility judgment business, configure the process information and global parameter variables in the canvas. The process information can be, for example, node type, node attributes, etc. Global parameter variables refer to variables defined in the process that can be shared and passed between multiple nodes. They are usually used to store and transfer data required during the execution of the process.

[0051] Step S140: Configure the first node. In the modeling module, the first node can be dragged to the canvas in a drag-and-drop manner, and then the first node is clicked for configuration.

[0052] Step S150: Configure the second node and associate the first node with the second node. The configuration process of the second node is the same. The difference is that for the newly added second node, it needs to be associated with other nodes.

[0053] Step S160: Configure and associate subsequent nodes in sequence until all nodes are configured and associated.

[0054] Please refer to Figure 6 , in a specific embodiment of the present invention, each node is configured according to the following steps: S141: Obtain the type of the node according to the requirement document and flowchart of the risk control responsibility judgment service; S142: Set the method, input parameters, and output parameters called by the node according to the type of the node according to the second preset rule, and specify the association between the node and the risk control responsibility judgment module. Different types of nodes require different configuration information. Therefore, multiple types of nodes can be preset, and the information required for each type of node can be predefined, so as to obtain the second preset rule. When configuring the nodes subsequently, only need to determine the type of the node and configure the node according to the second preset rule. When configuring, it should be noted that some nodes need to be associated with the risk control responsibility judgment module to trigger the risk control responsibility judgment process.

[0055] In a specific embodiment of the present invention, the types of nodes include start node, end node, judgment node, automatic node, script node, sub - process node, annotation node, loop node, loop interruption node, break - out - of - loop node, and wait - for - event node. Among them, the start node and the end node correspond to the starting point and the ending point of the entire process respectively, and other types of nodes correspond to the intermediate nodes in the process.

[0056] The custom attributes of the judgment node can include, for example, judgment conditions. According to the judgment conditions, determine the input of the judgment node, the node flow direction, and the number of node flow directions. The custom attributes of the automatic node can include, for example, executing a piece of logic. The custom attributes of the script node can include, for example, a script that can be directly run, and obtain a specified result through the directly run script. The custom attributes of the sub - process node include the nested use of the process, and simplify the main process by abstracting the sub - process into a fixed node. The custom attributes of the annotation node can include, for example, descriptions of the functions of each node, descriptions of the links pointed to by each node, descriptions of the functions of the main process, and descriptions of the functions of the sub - process, etc. The custom attributes of the loop node, loop interruption node, and break - out - of - loop node can include, for example, the loop entry for a certain process, determining the moment of loop interruption and the moment of breaking out of the loop according to the loop conditions, and determining the flow direction of the loop node. The custom attributes of the wait - for - event node can include, for example, waiting for the completion of a certain process and following asynchronous logic, such as waiting to obtain a certain piece of data before proceeding with the subsequent responsibility judgment process. In addition to these nodes, other types of nodes can also be preset.

[0057] Please refer to Figure 7 In a specific embodiment of the present invention, the nodes are associated according to the following steps: S151. Set the mapping relationship in the global parameter variable according to the association relationship between the output parameters of the foregoing node and the input parameters of the subsequent node. For example, if the input parameter of the second node is associated with the output parameter of the first node, it is necessary to set it in the global variable; S152. Connect the foregoing node and the subsequent node in the canvas and set the association condition, so that it can be realized that the process can flow downward when the condition is met.

[0058] Step S200. According to the business process model, use the business orchestration module to schedule and execute the business process. Among them, the business orchestration module supports task processing in serial, parallel, nested, and asynchronous modes. In this step, the general node module is used to generate the connection relationship of each process node according to the node input, node flow direction, and the number of flow directions of each process node through the lightweight business orchestration business process model, and execute according to the defined scheduling strategy. Figures 8 to 12 Different process node orchestration methods are respectively illustrated, and each orchestration method will be described below with reference to the accompanying drawings.

[0059] Please refer to Figure 8 which illustrates the serial method. The different process nodes A, B, and C are executed serially. After A is executed, B is executed, and after B is executed, C is executed. The execution result of A directly or indirectly affects the execution of B, and so on for the subsequent nodes.

[0060] Please refer to Figure 9 which illustrates the parallel method. The different process nodes B, C, and D are executed in parallel. The execution processes of B, C, and D do not affect each other and are carried out simultaneously to meet the requirement of the shortest execution time.

[0061] Please refer to Figure 10 which illustrates the serial-parallel method. The different process nodes B, C, and D are executed in parallel and then serially connected with nodes A and E, and then serially connected with nodes F, G, and H in parallel, and finally serially connected with node I. This method is suitable for more complex process orchestration methods. For example, in the risk control and liability judgment process, the data required for liability judgment is obtained in parallel, and then the real-time liability judgment engine is called for liability judgment, and then the results are obtained for splitting, and whether secondary human review is required and other processes are determined according to the splitting results. This method can be used for orchestration.

[0062] Please refer to Figure 11 which illustrates the nested method. For nodes A, B, and C, node B contains a serial-parallel process of sub-process nodes E, H, F, and G, which is embedded in the process of nodes A, B, and C in a nested manner to simplify the main process.

[0063] Please refer to Figure 12, which indicates an asynchronous mode. After nodes A, B, and C execute the process until node C, an asynchronous message is sent and the process ends. Node E executes the serial-parallel process of nodes E, H, F, and G after receiving the message sent by node C, achieving the asynchronization of the process.

[0064] In the above embodiments, the visual modeling module, the lightweight business orchestration module, and the risk judgment and responsibility module cooperate to complete risk control judgment and responsibility determination.

[0065] The modeling module provides the logical blueprint of the business process for the entire system. Users define process nodes (such as risk identification and responsibility determination nodes) in the graphical interface and specify the association between these nodes and the risk control judgment and responsibility module (for example, calling the real-time judgment and responsibility engine at a certain node); the modeling module outputs a structured business process model (such as a JSON configuration file), clearly marking which nodes need to trigger the risk control judgment logic.

[0066] The lightweight business orchestration module is the core driver for process execution. Based on the business process model generated by the modeling module, it executes node logic sequentially or conditionally. When it executes to the preset "risk control judgment and responsibility node", it actively calls the risk control judgment and responsibility module, transmits relevant data (such as order information and user behavior data), and receives the judgment result of the risk control judgment and responsibility module (such as risk level and responsibility attribution), and dynamically adjusts the subsequent process path according to the result (for example, a high-risk event triggers the manual review branch).

[0067] The risk control judgment and responsibility module is the execution unit of the business logic, which is triggered by the lightweight orchestration module during the process execution and is responsible for real-time risk assessment and responsibility determination. It depends on the rules preset by the visual modeling module (such as shunting conditions and threshold parameters) and may combine external data sources (such as credit investigation systems and blacklist libraries) for comprehensive analysis. It returns the judgment result (such as a judgment form and a risk score) to the lightweight orchestration module to drive the next action of the process.

[0068] The three cooperate through a standardized interface and an event-driven mechanism to form a "definition-execution-feedback" closed loop, ensuring the flexibility, real-time nature, and maintainability of the risk control judgment and responsibility process.

[0069] Please refer to Figure 13 , in a specific embodiment of the present invention, after obtaining the judgment result, it further includes step S400 and step S500.

[0070] Step S400: Use the storage module to store the business process model, the execution data of the business process, and the acceptance form. The storage module adopts a distributed storage architecture to store business process definitions, instance data, execution logs, and risk control liability judgment records, ensuring data consistency, durability, and scalability. When selecting a database type and designing the architecture, for example, the following methods can be referred to: (1) Use a relational database as the main one, such as MySQL, to store core structured data; (2) Use a non-relational database as the auxiliary, such as Redis, to store some semi-structured or unstructured data; (3) Build a data warehouse, such as a data warehouse platform based on Hive, to integrate data from relational databases and non-relational databases, and perform data cleaning, transformation, and summarization to meet the needs of data analysis and report generation.

[0071] Step S500: Use the process monitoring module to provide the operation status feedback and exception handling mechanism for each node. The process monitoring module provides real-time feedback on the operation status of process nodes and an exception handling mechanism. For example, the monitoring objectives can be set as follows: (1) Keep track of the execution progress of the risk control liability judgment process in real time to ensure that each link is completed within the specified time; (2) Accurately track the transfer path of risk events in the process, and clarify the processing results and data changes of each node; (3) Discover abnormal situations in the process in a timely manner, such as delays, incorrect liability judgments, data loss, etc., and give early warnings; (4) Provide data support and decision-making basis for subsequent process optimization and risk prevention and control strategy adjustment.

[0072] In the present invention, the modeling module is combined with the risk control liability judgment business to establish a visual, efficient, convenient, flexible, and intuitive liability judgment business process. It supports serial-parallel, embedded, and asynchronous methods through lightweight business orchestration. The lightweight architecture reduces the demand for system resources and can stably operate in an environment with limited resources (such as small enterprise servers, mobile devices, etc.) while ensuring the integrity of the risk control liability judgment function. This breaks the limitation that traditional risk control systems can only run on large server clusters and provides the possibility for risk control applications in more scenarios. With the help of process engine technology, the dynamic adjustment of the risk control liability judgment process is realized. When business rules, risk types, or regulatory requirements change, there is no need to re-develop the entire system. Only by modifying the process nodes, flow directions, and logics in the visual interface can the new situation be quickly adapted to. Compared with traditional hard-coded risk control processes, this method greatly shortens the business adjustment cycle and improves the timeliness of enterprises in dealing with risks. Moreover, the modeling module supports the definition of various types of risk control liability judgment processes and can easily handle both simple single-link risk assessments and complex multi-step, multi-condition risk determination processes.

[0073] Generally speaking, visual modeling improves the intuitiveness and convenience of process definition; lightweight business orchestration enhances the efficiency and flexibility of system execution; and real-time risk control and liability determination during the execution of business processes can be achieved.

[0074] It should be noted that the step division of the above various methods is only for clear description. When implemented, they can be combined into one step or some steps can be split into multiple steps. As long as the same logical relationship is included, they are all within the protection scope of this application; adding insignificant modifications to the algorithm or process or introducing insignificant designs, but not changing the core design of its algorithm and process, are all within the protection scope of this patent.

[0075] Please refer to Figure 14 , Figure 14 A risk control and liability determination device based on process engine technology provided by an embodiment of the present invention includes a third-party data source access unit 101, an acceptance unit 102, and a real-time liability determination unit 103. Among them, the third-party data source access unit 101 is used to collect data information from multiple channels during the execution of the business process; the acceptance unit 102 is used to create an acceptance form according to the data information from multiple channels according to a first preset rule; the real-time liability determination unit 103 is used to analyze and evaluate the data in the acceptance form according to the acceptance form to obtain a liability determination result.

[0076] It should be noted that the risk control and liability determination device in this embodiment is a device corresponding to the above risk control and liability determination method, and the functional modules in the risk control and liability determination device respectively correspond to the corresponding steps in the risk control and liability determination method. The risk control and liability determination device in this embodiment can be implemented in cooperation with the risk control and liability determination method. That is, without conflict, the relevant technical details mentioned in the risk control and liability determination method in the above embodiment can also be applied to the risk control and liability determination device in this embodiment.

[0077] The above embodiments only illustratively explain the principles and effects of the present invention, rather than limiting the present invention. Any person familiar with this technology can modify or change the above embodiments without departing from the spirit and scope of the present invention. Therefore, all equivalent modifications or changes completed by those with ordinary knowledge in the technical field without departing from the spirit and technical idea disclosed by the present invention should still be covered by the claims of the present invention.

Claims

1. A risk control accountability method, characterized in that: include: During the execution of business processes, use third-party data source access units to collect data information from multiple channels; Based on the data information of the multiple channels, using the acceptance unit to create an acceptance form according to a first preset rule; According to the acceptance form, the real-time accountability unit is called to analyze and evaluate the data in the acceptance form to obtain an accountability result.

2. The risk control accountability method according to claim 1, characterized in that: According to the acceptance form, a real-time accountability unit is called to analyze and evaluate the data in the acceptance form to obtain an accountability result, including: According to the acceptance form, calling the real-time responsibility determination unit to analyze and evaluate the data in the acceptance form to determine the data for which there is responsibility; Using the diversion unit, the data with responsibility is diverted according to preset conditions, and a judgment sheet is created for the data with responsibility that hits the diversion conditions and flows into the review unit; The auditor reviews the accountability sheet in the audit unit to obtain the accountability result.

3. The risk control accountability method according to claim 2, characterized in that: After the step of the auditor reviewing the judgment sheet in the review unit to obtain the judgment result, the method further includes: According to the judgment result, the disposal unit is used to execute disposal measures on the corresponding responsible party.

4. The risk control accountability method according to claim 1, characterized in that: During the execution of the business process, the step of using the third-party data source access unit to collect data information from multiple channels also includes: Use the modeling module to define and configure each node in the risk control and accountability business process to generate a business process model; According to the business process model, a business orchestration module is used to schedule and execute the business process, wherein the business orchestration module supports task processing in serial, parallel, nested and asynchronous modes.

5. The risk control accountability method according to claim 4, characterized in that: Use the modeling module to define and configure each node in the risk control and accountability business process, including: Obtain the requirements documents and flow charts for risk control and accountability services; Create a visualization canvas; According to the requirements document and flow chart of the risk control and accountability business, configure the process information and global parameter variables in the canvas; Configure the first node; configuring a second node, and associating the first node with the second node; Configure and associate subsequent nodes in sequence until all nodes are configured and associated.

6. The risk control accountability method according to claim 5, characterized in that: Configure each of the nodes as follows: According to the requirements document and flow chart of the risk control and accountability business, the type of the node is obtained; According to the type of the node, the method, input parameters and output parameters called by the node are set according to the second preset rule, and the association between the node and the risk control responsibility module is specified.

7. The risk control accountability method according to claim 6, characterized in that: The types of nodes include start nodes, end nodes, judgment nodes, automatic nodes, script nodes, sub-process nodes, comment nodes, loop nodes, loop interrupt nodes, loop exit nodes and wait event nodes.

8. The risk control accountability method according to claim 5, characterized in that: Follow the steps below to associate the nodes: According to the association relationship between the output parameter of the aforementioned node and the input parameter of the subsequent node, a mapping relationship is set in the global parameter variable; The aforementioned node and the subsequent node are connected in the canvas, and an association condition is set.

9. The risk control accountability method according to claim 4, characterized in that: After receiving the judgment, it also includes: Using a storage module to store the business process model, business process execution data and the acceptance form; The process monitoring module is used to provide operation status feedback and exception handling mechanism of each node.

10. A risk control and accountability device, characterized in that: include: The third-party data source access unit is used to collect data information from multiple channels during the execution of business processes; An acceptance unit, configured to create an acceptance form according to the data information of the plurality of channels and in accordance with a first preset rule; as well as The real-time accountability unit is used to analyze and evaluate the data in the acceptance form according to the acceptance form to obtain an accountability result.

Images